As a beginner, I quickly got in over my head with all of this flashing and rooting business on my new phone. Don't panic, here are a few things I learned to help you fix it:
1: Backup your data. I was using a factory fresh phone, otherwise I would have lost everything. Also, write down your IMEI and unlock code in case you should need them again while the phone won't boot.
2: Download Xperia Companion when your phone asks you to, it will come in handy later.
3: Make sure you phone is fully-charged before attempting any flashing. If worst comes to worst and you need to factory reset your phone, the Xperia companion tool will not work with a battery under 50%. If you can't read and/or don't listen and your phone runs low on battery while attempting to use the Xperia Companion software repair tool, you will be stuck in a boot loop with a locked, corrupted phone.
4: If stuck in a boot loop with low battery, use the factory charger and cable. Plug in the phone and let it be stuck in an infinite boot loop. The phone charges faster than the system can use the battery. There will be no battery indicator, so leave it attached for a few hours to charge before attempting to reuse the software repair function.
5: If all else fails, just reset it and try again! Ask questions if you have to, the devs and modders work hard so we don't have to and like to see others using their tools and methods to succeed
Your post is pretty old now I know but if your trying to root and it gets stuck in a bootloop just flash the stock boot.img instead of having to lose everything and reflash the whole firmware
Related
So today, While I was using it my phone suddently rebooted. Since then it could not boot back to android and is stuck at the google logo. I can still access CWM but even data wipe did'nt do any good.
Is there any way to save my phone ?
Kalak35 said:
So today, While I was using it my phone suddently rebooted. Since then it could not boot back to android and is stuck at the google logo. I can still access CWM but even data wipe did'nt do any good.
Is there any way to save my phone ?
Click to expand...
Click to collapse
Yes, definitely. If you're able to access download mode or the custom recovery, the device is easily recoverable. By easily, I mean most users are able to complete the steps although some users require more time and labor than others.
When the device hangs at the initial boot logo screen, in your case the Google logo, this generally indicates an issue with either the kernel or the ramdisk. The simpliest solution is generally to flash a known good kernel which is compatible with the currently loaded ROM.
If you have a nandroid on hand of a previously known good working state, that would be the easiest to restore. If not, you'll want to find a known good working kernel which is compatiable with the currently loaded ROM. If you're unable to find this combination, a ROM and compatible kernel will need to be loaded.
The odd part of the situation is how it seemed to "randomly" reboot and encounter this issue. Without knowning the details of the custom software loaded, difficult to accurately speculate the root cause.
Hope that helps point in the right direction!
Thank you.
Since I didn't know how to push files from my computer to my phone and had already done a full wipe I flashed google factory image and it worked!!
Now evrithing is good.
Thank you one more time, it realymade me freak out...
you wont't brick your phone unless you somehow brick the bootloader, even then you might be able to recover
Good After Noon,
Recently LG Released a new android update, (6.0.0) The phone will send you a prompt that says. "ANDRIOD UPDATE 6.0.0"
Before I get into explaining this major issue I'm going to give you guys a run through on what android updates go through before it finally reaches your device.
Lets begin. The update is developed by android, then this update has to go through several inspections before it can be sent off to the service providers.
Once the update passes all of its required inspections it is sent out to each phone brand, HTC, SAMSUNG, LG, & so on and so forth, once the phone brands receives
the update, they edit the released android update to fit there devices expectations. Once each phone brand completes editions, then they send the updates to each service provider
that sells there phone brand, that's a lot of sending.
Now the major issue!
Hopefully you have read everything mentioned above to help you understand the cause of the Bootloop.
The way you could tell if the bootloop issue was caused by the update is if the bootloop started occurring shortly after updating to 6.0.0, & if your reading this because you are experiencing bootloop issues at this moment after doing the update then try this method to see if the phone will completely boot, Just simply plug you phone into the wall charger, now once you do this if the LG G3 comes out of bootloop and boots up normally then the culprit was the update, now to be sure if the update was the culprit, just simply unplug your LG G3 from the charger, now if it goes back into a non-stop bootloop. the Update was your culprit!
The reason this bootloop happened is because the android update 6.0.0 had a major corrupted file, how did this corrupted file end up in the update, well it's pretty simple, once the update was sent to the phone brand (LG) they went in and edited the update to there likings and at some point in that process they miscoded a file or wrote over a file which in result caused the phone to bootloop, Which tells me that the file that was miscoded or wrote over could have possibly been the file that prompts the phone to boot up, the boot up process takes the most power usage then any other process a phone is able to do, which means the phone will pull power from the battery until all files have been successfully complete, if the file is corrupted then the phone will boot until it receives the corrupted file then it will shut down and keep repeating that process, then the battery gets a memory and all it know to do is boot reboot boot reboot, which is known as bootloop. the way to fix this problem is to order a replacement battery, then the phone will boot normally. just be sure before putting the new battery in, plug the phone in the wall while still using the bad battery, backup all of your, and do a factory reset, this will put the phone back to normal and it will delete the corrupted file, the phone will work perfect. I put money on it.
Expert advice needed please. This is a puzzle that someone might enjoy solving.
Although I have a fair bit of experience with flashing, I tried to flash my 8.0 for the first time and it has dramatically failed. It was probably my fault - not an uncommon story.
What is less common is that I am struggling to figure out how to undo the damage I've done. What's really making this difficult is that no computer recognises the device as USB any more so I can't use Odin, Kies, etc to repair or return to stock. I have tried everything I can think of to deal with the USB issue, the usual cable, driver, port nonsense. I don't think the USB problem is Windows now.
I suspect one of these things may have happened:
The USB port just went bad coincidentally during this flash process (charge, no data). I have ordered a new port but it will take weeks to arrive.
Has the device come out of Developer/USB debugging mode somehow? I can't tell because I can't boot to an OS.
I wonder if the ROM flash has corrupted the firmware the deals with USB - is that possible? Where is the devices USB drivers located? Is it in the bootloader, something like BIOS?
I'm suspicious of the bootloader, as the screen is weirdly corrupted now when I turn on or reboot the device - fuzzy white lines rather than a logo - but that disappears when OS tries to load, or I go into Recovery/Download.
I actually did do a backup of the original ROM to the SD card; but restoring it doesn't work, just produces an endless Samsung boot, even if I then wipe and reset.
I can get into Download mode, and a Recovery (Philz for N5120) but since I can't connect to the devise with USB in any way, it's very hard to get the Recovery to flash anything new and useful. I did put my SD Card in another phone and copied over the stock ROM zip from Samsung, but it refuses to flash - I think because it doesn't like Philz Recovery? I can't think how to replace Philz Recovery with another by flashing, without USB.
I may have to wait to replace the USB port, but I fear that won't fix it. Until then, I can only think of one other thing to try, and that is to copy a ROM onto the SD Card through another phone, and try to flash it. Lineage doesn't flash, and nor does the stock zip I got from Samsung. Would anything else work?
Can I flash an alternative recovery from within the recovery? Philz only lets me flash zips, not img or tars.
So it's quite a mess, but if anyone has a brilliant idea of how to get out of this, I'd love to hear it.
THANK YOU if you have a genius idea.
So after a few days of working on this, I did manage to resolve it, and I thought I'd just add a note about how I escaped this obscure problem.
The device went bad because I stupidly flashed an incompatible Recovery to the device and somewhere between doing this, backup and restoring and flashing, it corrupted mostly everything including something in the bootloader.
Oddly enough, the solution seemed to be to mess up the Recovery even more by flashing something even more random - it seems this provoked the device into restoring its own basic Recovery. Using this to wipe and reset the device somehow enabled Download mode's USB interface to start working again so I was able to use Kies to return to stock, which repaired everything including the bootloader.
Finally, I flashed the correct Recovery for this device, and then managed to flash the ROM I wanted. A happy ending to a stressful story; the device now works better than it ever has done before.
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.
Hi Guys,
As the title says my S20 Ultra has managed to get itself stuck in a boot loop as of last night. I can boot into recovery mode, download mode and safe mode. When booted into safe mode it will stay on the home screen fine. However if i try to unlock the phone to use it, it crashes and reboots into a bootloop.
If I just plug in a usb to access the files via usb in safe mode before the phone is unlocked the phone is not detected (device manager detects a samsung device but nothing in file explorer most likely because the usb services haven't started up yet and won't until the phone is unlocked).
Im sure a factory reset will solve the bootloop issue but I don't want to lose the date on the phone until it's backed up (recently renovated our house and I have pictures on there of before and afters I would like to keep).
Is there a method I could use to get the data back other then sending the phone off to a recovery service? Maybe something that doesn't void the warranty of the phone but if there is no other choice I would consider voiding the warranty. I used to install custom roms on all my old android phones but never felt the need to on this one. I'm fairly tech savvy so am Just looking for ideas.
Cheers
Coddeh said:
Hi Guys,
As the title says my S20 Ultra has managed to get itself stuck in a boot loop as of last night. I can boot into recovery mode, download mode and safe mode. When booted into safe mode it will stay on the home screen fine. However if i try to unlock the phone to use it, it crashes and reboots into a bootloop.
If I just plug in a usb to access the files via usb in safe mode before the phone is unlocked the phone is not detected (device manager detects a samsung device but nothing in file explorer most likely because the usb services haven't started up yet and won't until the phone is unlocked).
Im sure a factory reset will solve the bootloop issue but I don't want to lose the date on the phone until it's backed up (recently renovated our house and I have pictures on there of before and afters I would like to keep).
Is there a method I could use to get the data back other then sending the phone off to a recovery service? Maybe something that doesn't void the warranty of the phone but if there is no other choice I would consider voiding the warranty. I used to install custom roms on all my old android phones but never felt the need to on this one. I'm fairly tech savvy so am Just looking for ideas.
Cheers
Click to expand...
Click to collapse
Try flashing the same firmware you're currently running using Odin and HOME_CSC to keep your data, possible it will replace and fix the corrupted files causing the bootloop
So last night I tried what you have mentioned. It didn't change anything unfortunately.
I then thought it might be worth trying an older firmware. I tried rolling back to the previous firmware and then to android 10. Both of these ended up making things worse and it would boot loop at the android startup screen.
Luckily I managed to get back into Odin mode and put the current firmware back on and I'm now back to square one.
OK so I have had a thought. I've seen that some people have managed to establish a USB connection to thier device through TWRP and managed to backup their data through that. I've also seen that on older phones you can use odin to only flash TWRP and then boot into it. I'm not sure if things have changed drastically and you are unable to do that on the S20 ultra now. After my data (pictures and videos) was backed up I could then reflash the recovery back to stock and do a factory reset to fix the bootloop.
Does this seem plausible?