Hi'
My mother have a nexus 5X,
This morning Phone loopboot ... (phone start : google logo after boot animation and it stays that way )
Since this morning I read everything, and I do not know how to do it anymore
Download mode,ADB, Lg flash tool ,phone in the freezer, disassembled the phone ....
My priority is to try to save data as picture (Yes I know ... it's not easy )
What should I start in this situation ?What is the order of the method to use?
Thank you for your help,
About this phone:
this phone is not rooted
this phone use the latest version of android available (I think android 8.1 )(but the last update is several day/weeks / months ago : this bootloop does not arrive just after an update )
this problem occurs 2 days after the end of warranty #Unlucky
(ps: sorry for my English , It's not my main language )
As far as I know, you need OEM unlock to be on (under developer settings) to flash a new boot/recovery image, if you didn't do that then you need to get the device to load into Android at least 1 time, at least for 2-3 minutes so you can quickly turn this option on (unlocked).
From my experience, it's possible even if you stuck in a boot loop for 1-2 hours, to eventually load into Android without heating/cooling the device - give it a shot.
After you unlock the OEM, follow the instructions and flash a boot and recovery image that fits your currently installed version.
K285490 said:
As far as I know, you need OEM unlock to be on (under developer settings) to flash a new boot/recovery image
Click to expand...
Click to collapse
@BobJellyBeans - Do not attempt to OEM unlock your phone if you are trying to save data. This forces the phone to wipe as a "safety measure".
Related
I own a N5x 16gb (h790 with Android N DP2)
Yesterday I was opening Inbox by Gmail and I get some FC after open some mails so I started to get more FC from other apps (It was a webview beta problem https://goo.gl/k4SZ6i) so I tried to reflash Android N and I get bootloop on boot animation (that with colored points), I tried to flash MDB08I and MHC19J and occur the same bootloop.
After some trys the bootloader goes locked and now i cant unlock it
here some links i've tried:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
http://forum.xda-developers.com/nexus-5x/help/constructing-16gb-tot-file-t3337443
http://forum.xda-developers.com/nexus-5x/help/device-locked-t3355549/page4
Any ideas?
vinaaa said:
I own a N5x 16gb (h790 with Android N DP2)
Yesterday I was opening Inbox by Gmail and I get some FC after open some mails so I started to get more FC from other apps (It was a webview beta problem https://goo.gl/k4SZ6i) so I tried to reflash Android N and I get bootloop on boot animation (that with colored points), I tried to flash MDB08I and MHC19J and occur the same bootloop.
After some trys the bootloader goes locked and now i cant unlock it
here some links i've tried:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
http://forum.xda-developers.com/nexus-5x/help/constructing-16gb-tot-file-t3337443
http://forum.xda-developers.com/nexus-5x/help/device-locked-t3355549/page4
Any ideas?
Click to expand...
Click to collapse
The bootloader just cant magically lock itself. Anyway, try following the instructions HERE to sideload the N ota. Once in Android go to developer options and allow OEM unlocking and unlock your bootloader. Then reflash the latest marshmallow images and dont mess with your phone anymore.
PiousInquisitor said:
The bootloader just cant magically lock itself. Anyway, try following the instructions HERE to sideload the N ota. Once in Android go to developer options and allow OEM unlocking and unlock your bootloader. Then reflash the latest marshmallow images and dont mess with your phone anymore.
Click to expand...
Click to collapse
I already tried this two or three times, it remains on boot animation
mine to , when i was using it for chatting the phone starts freezing , and it's dead
i can't boot it up and can't go to recovery , even i did flashing manually with ADB / NRT same problem still can't boot up , don't know what happen , can't go to download mode to
This happened to me as well
I recently bought a used 5x on eBay, the H790 model. It was cheap.
Everything was fine until I ran through the updates., and was downloading apps from the Play store.
Since then, the phone would unpredictably reboot no matter what ROM was installed. The logcat logs didn't show anything helpful. Typically it didn't take too much longer than 60 seconds for the phone to reboot itself.
I messed with it every way I've seen published, including the links you included. I'm having to send the phone back. Thankfully, for a full refend.
I will note that the LG G4 had a hardware bootloop problem. I don't know if it's at all similar to this issue. My other thought is it could be faulty RAM but I don't know how to do a memory check on Android.... maybe LG had a bad batch of 5x's that got out there.
Couple of days ago I got this OTA notification that Android 7.1 preview is available for update. As my phone is rooted I started the manual update procedure. After the flashing was finished, I restarted the phone and then I saw it was stuck at the Google screen. Just stuck, no response. Seemed unusual to me.
Let me tell you that I have been modding my Nexus 5 for about two years. I am familiar with most of the tweaks that can be done to a Nexus device. Nexus 5 served me amazingly. I bought Nexus 5x 3 months ago.
So, after it was stuck I restarted. Still stuck. I will tell you step by step what I did then:
1. Flashed the OS 7.1 again (I dunno why, the flash.all script doesn't work for me, so I always do that manually) - result is the same.
2. Last October update (NBD90W) was available in the folder so I flashed that - same result.
3. I downloaded the previous one (NRD90S) and flashed that - same result.
4. I locked the phone and unlocked again to erase everything (not sure if that's a good idea), then flashed the OS again - same result.
5. Then I tried LGUP and the tot files to give it the factory version. LGUP detects the phone, started installing. When the installation is finished and the phone restarted - same result.
6. Now that I gave it the factory version the phone got locked!
7. I searched google for hours but couldn't find a way to unlock it as the OS is not booting and I cannot turn USB debugging on!
8. Then I tried the default recovery mode (Android recovery, from the recovery screen Power + volume up) as it doesn't require unlocking the device. Wiped the cache and restarted - same result.
9. My phone is detected by the pc and ADB. So, I wiped everything and tried ADB sideload and get this error E: footer is wrong
10. I tried Nexus root toolkit. It detects the phone in fastboot mode, then restarts it and then it again is stuck on the Google screen.
I am extremely depressed!
I am from Bangladesh and there is no authorized LG servicing center here. So, I can't ask for there help.
All that I did over the past two years was the awesome threads of xdadevelopers. So, a big thumbs up for you guys :good:.
I learnt from the web that phone can be hard bricked if a wrong bootloader is flashed. That's impossible for me as I always remove the factory image extracted files after flashing is done from the ADB>platform-tools folder.
Now, is the phone hard-bricked? If it is, what to do with it? Any kind of suggestion will be very much appreciated.
Hi everybody,
tried to look for soulutions but without any luck...
I wanted to go back to Android 7 from the 8 (because i had the feeling the 8 is much slower).
I couldn't manage to flash the 7 as long as the phone would lock itself everytime while starting the downgrade so i flashed the N2G47Z 4 core image file on top of the Stock 8.1. I know, i should have used a 4CoreOreo....
Result: i'm an idiot with a phone in bootloop. Cannot go into recovery or anything. i manage to see the Google word and the warning that i should lock the bootloader and go to website g.co/ABH
I will wait until the battery drains and try to switch it on again but than what is the right procedure to follow in order to fix it? (if any)
thank you
Pippolinus said:
Hi everybody,
i flashed the N2G47Z 4 core image file on top of the Stock 8.1. I know, i should have used a 4CoreOreo....[/U]
I will wait until the battery drains and try to switch it on again but than what is the right procedure to follow in order to fix it? (if any)
thank you
Click to expand...
Click to collapse
UPDATE
i put the phone in the freezer (couldn' t wait the battery to drain) and i discover that if it is switched off you can enter in fastboot mode for one time (than you go back to bootloop)
I flashed the 4CoreOreo and now i get the same warning and error but after 30 seconds it goes off and it start to load the system.
However it doesn't finish to load it becasue it says Android is corrupted and a full wipe is suggested. I did the full wipe but nothing changed.
So now i'm stuck but in a kind of "light bootloop". I tried to updload Android 7 following the procedure through ADB but it doesn't work.
Try to go to fastboot and flash factory image of 7 from official site, and use the flash_all.sh / flash_all.bat. While you're doing that instead of flashing boot.img from the factory. Use the 4 core for 7 from the https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199 thread. Use the nougat boot.img. That's it. You'll be back on track.
Pippolinus said:
i put the phone in the freezer
Click to expand...
Click to collapse
Literally one of the worst things you could do to a smartphone(or any other type of electronics).
Your phone is probably begging for a motherboard replacement right now...
Danish Fayaz said:
Try to go to fastboot and flash factory image of 7 from official site, and use the flash_all.sh / flash_all.bat. While you're doing that instead of flashing boot.img from the factory. Use the 4 core for 7 from the https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199 thread. Use the nougat boot.img. That's it. You'll be back on track.
Click to expand...
Click to collapse
Hi, thank you for the answer.
I' ll try again changing the boot.img inside the folder ... when i tried yesterday (i tried to flash the 7 and the 8 even with the Nexus toolkit) it was not possible because everytime i unlock it (throught ADB for example) at the first reboot goes back to locked automatically, so the process stops showing some errors.
Changing that .img the problem goes away?
Pippolinus said:
Hi, thank you for the answer.
I' ll try again changing the boot.img inside the folder ... when i tried yesterday (i tried to flash the 7 and the 8 even with the Nexus toolkit) it was not possible because everytime i unlock it (throught ADB for example) at the first reboot goes back to locked automatically, so the process stops showing some errors.
Changing that .img the problem goes away?
Click to expand...
Click to collapse
If your bootloader automatically locks itself, that's a hardware issue. While booted in the bootloader, you should see "No RPMB" along one of the lines. This means that Your motherboard was replaced.
Sent from my Nexus 5X using Tapatalk
hello, i was hoping to get some help with my device not being rootable.
i followed these two guides word for word i cant post links because im new here but i followed the naldotech twrp + root s9 guide and the highonandroid s9 root guide.
tried both reinstalled OS with csc and home-csc twice for each one when my phone was stuck in a loop so i can make sure that its back to factory before i try another method. my phone it either gets stuck at samsung logo or just reboots to recovery never goes to samsung logo my oem unlock button always stays off even though i follow the steps and it says under it that bootloader already unlocked and it never goes blue and oem lock: off in download mode, i did not setup my samsung or google accounts in any of those resets that way no settings get synced.
i really need the help i have been trying this for the past month and a half and i have tried everything i could think off and nothing is working.
current software installed: G960FXXU2CRLI_G960FOXM2CRLI_XSG
Model: SM-G960F/DS
OS: 9.0.0
chriskay525 said:
hello, i was hoping to get some help with my device not being rootable.
i followed these two guides word for word i cant post links because im new here but i followed the naldotech twrp + root s9 guide and the highonandroid s9 root guide.
tried both reinstalled OS with csc and home-csc twice for each one when my phone was stuck in a loop so i can make sure that its back to factory before i try another method. my phone it either gets stuck at samsung logo or just reboots to recovery never goes to samsung logo my oem unlock button always stays off even though i follow the steps and it says under it that bootloader already unlocked and it never goes blue and oem lock: off in download mode, i did not setup my samsung or google accounts in any of those resets that way no settings get synced.
i really need the help i have been trying this for the past month and a half and i have tried everything i could think off and nothing is working.
current software installed: G960FXXU2CRLI_G960FOXM2CRLI_XSG
Model: SM-G960F/DS
OS: 9.0.0
Click to expand...
Click to collapse
Did u fix it ? Cos I have similar issue but on my phone it says the bootloader is locked and the OEM unlock option never turns on , when I turn it on it does factory reset and reboot the device but the option stays off
Akhayev said:
Did u fix it ? Cos I have similar issue but on my phone it says the bootloader is locked and the OEM unlock option never turns on , when I turn it on it does factory reset and reboot the device but the option stays off
Click to expand...
Click to collapse
no fix yet and same thing is happening to me the OEM options always stays off and that's even after a clean firmware install i really hope we can find a way to fix this
chriskay525 said:
no fix yet and same thing is happening to me the OEM options always stays off and that's even after a clean firmware install i really hope we can find a way to fix this
Click to expand...
Click to collapse
Did u wait for 7 days ?
I recently found a moto g5 in one of my fellow "old tech" drawers and decided to turn it on, it was on the
1. May 2018
Security patch on nougat, I decided to use the inbuilt system updater to go to Oreo, and now....it crashes during flashing process after about 25-30% completion,
Now im guessing boot or System is not properly installed due to the zip file having aborted mid-flash
Recovery doesn't properly boot as that is used to install the update and thus imidiately goes to doing that
Also, it hang up during installation on random times, it basically has a record of 2mins of not crashing whilst still being stuck on 30%
I got it to "boot" when trying factory mode, yeah it crashed mid boot animation...not a help
Any suggestions? EDL mode maybe?
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
TheFixItMan said:
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
Click to expand...
Click to collapse
SOMEHOW it just decided to boot, I have never seen such behaviour, even on my g5s which I had for a while, (and am currently daily driving to school if it wasn't closed....NEVER
Maybe I'll unlock it and try somehow recreating it? Well it's in physically rough shape but all components inside are fine...so that can't be the reason....?
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
anonymous724 said:
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
Click to expand...
Click to collapse
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
riyan65 said:
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
Click to expand...
Click to collapse
no luck on this front, gets to the passcode screen, write in passcode then motorola logo shows and screen keeps on turning off and on.
Thanks for the effort though, much appreciated
Mine is similar to yours. Initially was on permanent loop of the following:
1. Boot to moto g splash screen... Repeat
2. Boot to lock screen then usually a few loops of 1. (after entering the patter or left Idle)
The phone initially didnt have any developer options enabled.
I wiped cache using recovery mode. Restarted and pretty much the same thing except that it would on rare occasions actually fully boot up usually only last a few minutes before cycling between steps 1 and 2 above.
I used those rare boot ups to backup all files and enable any USB debugging /oem unlock (incase I need to use a solution dependent on these being enabled.)
Factory resetted it and its still the same with the random successful boot amongst the numerous failed ones.
I managed to hook it up to Lenovo's Lmsa and flash the latest ROM. Now I get a lot more successful boots but still loops every so often. The downside is that I can no longer do any functions that make use of the audio/ mic/ video (can take pictures). If I do then it will crash and loop.
The hardware test on the LMSA passed for every component before flashing to the latest version. Post update it predictably fails on the audio/ mic components.
I guess I'll have to go back to the old version to see I get the audio back.