We expect a complete change after “flash all”. The phone should go back to “factory” … that is no hint of anything “Custom” should remain.
I know that…
Im just saying l had first the recovery mode then the corruption warning then google starting and finally twrp
Not normal at all
You saw all this today ?
Not since l did what you asked this morning
./flash-all.sh
Now from start button
Corruption warning
Google a few seconds
Black
From start & volume down
Recovery mode
Start button
Corruption warning
Google a few seconds
No command ( last photo)
Are you able to power down then boot into recovery ?
If you can reach recovery can your PC reach the phone with
adb devices
You not helping
I know lm not a pro like you but please if l upset you please do not read me…
$ adb devices
- daemon not running; starting now at tcp:5037
- daemon started successfully
List of devices attached
cate@cate-1011PX:~/Downloads/Bull/bullhead-opm7.181205.001-factory-5f189d84/bullhead-opm7.181205.001$
I guess I should ask first … had you seen a Google recovery screen before
adb devices
You might spend a bit more time to see how predictable is each boot.
I wonder if boot is being prevented by corrupted userdata
again. Maybe (if it seems right to you)
fastboot erase userdata
$ fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
Erasing ‘userdata’ OKAY [ 0.571s]
Finished. Total time: 0.598s
i try…
un Licol et une selle ont des fonctions différentes…
.
This :
is stock Gogol recovery mode.
.
This :
is bootloader / fastboot mode, proposing to boot into recovery mode
Je comprends
Les grosses lettres et les ! n’aident pas… je n’essaierai jamais de mettre une selle sur une tête mais là il faut admettre que c’est tout pareil c’est sur un ecran dans un terminal et avec un clavier…
J’essaie de suivre au mieux aibd et c’est déja pas facile…
But it does not
Only start is green
Recovery and bootloader are red and gets me nowhere
I think I asked this before but got no failed to understand the answer, in the case of this;
is there any reaction to pressing the Up + Down volume keys. This looks like a menu where you can use the keys to change your intended destination and press the Power key to change mode.
Does it work like this for you ?
Yes
There are 4 different menus
But its not working
Only Start and Power off works
Start (green)
Restart Bootloader ( red)
Recovery mode (red)
Power off (white)
I guess we could try to fine tune our interventions but I suspect the phone does have the issue I already quoted Resurrecting a bootlooped Nexus 5X | tony is coding.
The manufacturing issue involved has its own Wikipedia page LG smartphone bootloop issues - Wikipedia
- LG stated that it was caused by a “loose contact between components”
- Android Authority explained that "a loose connection between power supply or memory components could certainly cause a phone to fail to boot up properly, due to a lack of system stability or not being able to access vital memory.
- This could be down to important setup communications not being sent or received between peripherals correctly.
- Nexus 5X In September 2016, reports began to circulate that similar failures were being encountered with the Nexus 5X manufactured for Google by LG, particularly whilst upgrading to Android 7.0 “Nougat”
The above has also been called Bootloop of Death (BLOD). There is an XDA tool to try to fix it https://xdaforums.com/t/tool-how-to-nexus-5x-bootloop-of-death-blod-workaround-flashable-zip.3819497/.
It amounts to a two stage job,
- a special (reduced load) TWRP
twrp-3-2-1-0-fbe-4core-bullhead-img
- then flashing AnyKernel3 zip via TWRP.
One then hopes that the Stock ROM will boot. It is noted
- Reflashing the BLOD AK3 zip will likely be required after anything that could modify the boot.img or recovery.img, including (but not limited to): ROM updates, custom kernel updates, custom recovery updates.
Id like to try that.
If its not a succes l am okay to stop there…
If there is a loose connection then it could be not fixable and we’ll have to let it be broken
We can try tomorrow evening if suitable
For now
Goodnight
Let me just review 3 things we can possibly do with TWRP.
a) Use TWRP without install, my words “on the fly”.
My intention in my “Simplified proposal” in Post#149
fastboot boot recovery-filename.img
b) Regular TWRP install
fastboot flash recovery recovery-filename.img
Now reboot into recovery to verify the installation this essential step is needed to change the “flashed” TWRP to “installed” TWRP.
c) TWRP flash for repair and leave.
It is most likely that if one does only
fastboot flash recovery recovery-filename.img
… makes some filesystem changes then Reboot system now …then a working TWRP will not survive on the device.
From https://xdaforums.com/t/tool-how-to-nexus-5x-bootloop-of-death-blod-workaround-flashable-zip.3819497/ you can find the required source files in the Attachments section
When downloaded to your working directory Bull
they should look like
@piero has also pointed out the merit of a Full OTA image for the phone. Here is the link
This is the version Oreo 2018, December ROM (note same date as the previously used Factory image). It will have the advantage of being installable by TWRP.
From what you have told us, it is difficult to tell how “broken” the phone is right now.
An OTA update file is expected installable fairly easily, no need to keep swapping back to fastboot.
Please can you download this also to your working directory Bull
.
Edit I deleted my early proposal for how best to use TWRP.
List of files for next stage
The files should not be unzipped.
twrp-3.2.1-0-fbe-4core-bullhead.img
N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip
bullhead-ota-opm7.181205.001-b1af2457.zip
Hello
Today and before anytning l press start button and then l get
Corruption warning
Google
Erasing circle a while longer than ever
Android starting a while longer l almost believed it would start properly
By android l mean that: same on my tv
But then all went black again…
I am not going to follow steps yet because l must go but l am going to dowload the files you asked
Talk later…