I have an unlocked bootloader. I flashed the factory images. The MD5 sum matched that on Google's download page. After it does the automatic reboot, my phone just stays at the boot animate and never actually boots. I've let it sit for about 10 minutes.
I've flashed factory images many times, including on this Nexus 5, and never had this happen before.
I'm using the USB cable that came with the Nexus 5.
I can boot back into fastboot, and everything works. I even flashed TWRP and can boot into TWRP. But in TWRP I can't mount anything, and if I try to do a system wipe, it fails.
Any thoughts? Has something somehow gone wrong while flashing the factory images? Help appreciated.
Edit: Booted into Stock Recovery and wiped cache and did a factory reset. Then rebooted from recovery and let it sit for awhile. It finally booted all the way up. Absolutely no idea what was going on there. Anybody else had a similar experience?
Doing a factory reset in the stock recovery almost always gets your past a boot loop.
Sent from my Nexus 5 using XDA Free mobile app
Related
Hello all,
I recently botched the install to the Nightly 1.3 (or 13) Cyanogen Mod 7, and when performing a factory reset, the phone simply boots back to CM7. Is there a way to completely erase everything and start back with stock Froyo/Android 2.2?
As it stands, I can't even go into recovery mode from Rom Manager for some reason. It either freezes upon boot, shows an "unpacking" image and goes nowhere, or simply shuts down the phone.
Thank you in advance for your help.
You'll have to flash a different ROM, a factory reset just wipes data.
Sent from my Nexus S 4G using XDA App
you can use odin and your into download mode
tick re-partition、Auto Reboot、F.Reset Time to flash
Have an XT926 Maxx with an unlocked bootloader. I can wipe partitions and flash custom ROMs just fine. I can also fastboot back to stock images. But for some reason, I can't get past the boot animation. For example, on the stock rom, it'll display the 'DROID' image upon boot and play the 'DROID' sound but then suddenly freezes, then reboots (over and over again). I've gone into factory recovery and wiped data/cache and still have the same issue.
I've searched the forums and was not able to find anyone with the same issue.
Any suggestions? Am I screwed? Perfectly good phone otherwise!
TWong1200 said:
Have an XT926 Maxx with an unlocked bootloader. I can wipe partitions and flash custom ROMs just fine. I can also fastboot back to stock images. But for some reason, I can't get past the boot animation. For example, on the stock rom, it'll display the 'DROID' image upon boot and play the 'DROID' sound but then suddenly freezes, then reboots (over and over again). I've gone into factory recovery and wiped data/cache and still have the same issue.
I've searched the forums and was not able to find anyone with the same issue.
Any suggestions? Am I screwed? Perfectly good phone otherwise!
Click to expand...
Click to collapse
If all you're doing is wiping data/cache, there's a possiblity that there might be some bad data in there still. I would also format data, as this will get rid of everything. Wiping data doesn't always get rid of everything. If you are fastbooting stock ROMs, always FDR after you flash, prior to booting into OS. Also, since your BL is unlocked, you need to load up an aftermarket recovery like CWM or TWRP. None of the new ROMs will work on stock recovery.
RikRong said:
If all you're doing is wiping data/cache, there's a possiblity that there might be some bad data in there still. I would also format data, as this will get rid of everything. Wiping data doesn't always get rid of everything. If you are fastbooting stock ROMs, always FDR after you flash, prior to booting into OS. Also, since your BL is unlocked, you need to load up an aftermarket recovery like CWM or TWRP. None of the new ROMs will work on stock recovery.
Click to expand...
Click to collapse
Thanks for the reply.
Yes, I know about the need for TWRP/CWR when flashing custom ROMs. I reverted back to stock recovery when I fastbooted the factory images. Using stock recovery, I wiped Data and Cache so not sure what you mean. What's FDR?
Sent from my LG-VS980 using Tapatalk
TWong1200 said:
Thanks for the reply.
Yes, I know about the need for TWRP/CWR when flashing custom ROMs. I reverted back to stock recovery when I fastbooted the factory images. Using stock recovery, I wiped Data and Cache so not sure what you mean. What's FDR?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
FDR is Factory Data Reset. It's generally a good idea to boot back into recovery and FDR after fastbooting.
RikRong said:
FDR is Factory Data Reset. It's generally a good idea to boot back into recovery and FDR after fastbooting.
Click to expand...
Click to collapse
Ah, yes....I've done that numerous times. Still will not boot. Is there a way to erase the partitions and rewrite them? Perhaps they're corrupted or something.
Sent from my LG-VS980 using Tapatalk
I was, for some reason, able to get it to boot up once today. I was able to get to the 'Power off and Insert SIM' screen. After powering off, though, it would no longer fully boot into the OS. Still bootlooping.
Less than an hour later, i got it to boot up yet again. Not sure how, but it's booted up and now with my SIM installed. I know if I reboot, it'll happen again.
Anyone have a clue what it could be? Anything I can do before shutting it down that could help?
TWong1200 said:
Ah, yes....I've done that numerous times. Still will not boot. Is there a way to erase the partitions and rewrite them? Perhaps they're corrupted or something.
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
you can re-write the partitions using this tool, for the 926 only
https://www.dropbox.com/s/bpjghbbv0v6r4v5/DROID_RAZR_HD_Utility_1.3.gpt fix.rar
Ok I just got my brand new OnePlus One in the mail today. Opened the box, loved the design and build quality, etc... Powered it up for the first time all good, played around with it for a few minutes, liking everything. An update option popped up for 38r, I did the update, maybe I shouldn't have., but too late. I did the update, then phone rebooted, and everything good again
So then time to root this beast. I went through the typical steps, all good, got TWRP Recovery installed easily, then flashed SuperSU.zip in Recovery, it said successful, I pressed Reboot System, and here's the issue, the phone is just stuck on the boot animation screen. I see the Octagon CM animation spinning, but it just spins, and spins, and spins, not going any further.
So now what ?
What I'd do is to install a custom ROM but I'm pretty sure if you perform a factory reset it would boot back up. Also try wiping the cache. This is what I'd do but there might be alternative solutions out there.
Yuvin said:
What I'd do is to install a custom ROM but I'm pretty sure if you perform a factory reset it would boot back up. Also try wiping the cache. This is what I'd do but there might be alternative solutions out there.
Click to expand...
Click to collapse
I went into TWRP Recovery did a Factory Reset, then reboot system, and IT WORKED
No idea I had to do a factory reset in Recovery to make it work.
Zorachus said:
I went into TWRP Recovery did a Factory Reset, then reboot system, and IT WORKED
No idea I had to do a factory reset in Recovery to make it work.
Click to expand...
Click to collapse
That's great! Enjoy your rooted OPO!
Let me start form the beginning.:-
My bootloader was locked and I was on stock 4.4.4 . I faced no problems at that time. I saw OTA notification for lollipop 5.0.2 update, downloaded it, installed it, device gets restarted, I saw new bootlogo and then bootanimation. Just after the bootanimation, the screen goes blank(back-light is still on). I waited for about 40-50 minutes, but the screen is still blank with backlight on. Tried rebooting 3-4 times but stuck after bootanimation. 1 time it booted successfully and I was presented with the lockscreen. I swiped unlock the screen but suddenly services was stopping one by one and various applications also getting force closes, even the launcher also got force closed. So I rebooted again, and again got stuck after bootanimation, getting only a blank screen with backlight on.
Now I booted my phone into recovery, factory reset it(also wiped cache manually) and then booted into system, still no good. I was getting the same blank screen after bootanimation. I tried rebooting 4-5 times and at one time, it got past the bootanimation. There I saw that the device didn't get factory reset(wallpaper, home screen icons were at that place only where it was before). Now again service got stopped and apps got force closed.
Now, I downloaded stock firmware images from here on xda and flashed it from bootloader. I was still getting blank sceen after bootanimation and occasionally it got booted and everything force closes again.
After trying everything, I unlocked my bootloader and tried flashing a custom recovery (so that i can try installing custom roms). But after successfully flashing custom recovery, I booted into recovery and find that it didn't got flashed (I was still on stock recovery). I tried flashing different custom recoveries 7-8 times, but the stock recovery persists!.
So, now the bootloader is unlocked, stock recovery is persisting after flashing any custom recovery, even the user data is persisting after factory reset, and I am unable to boot to system properly. I don't know what to do after this. Please let me know if this all means that some part of the hardware is failing in my moto g or if it can ever be come back to life.
Edit:- I have just booted into twrp Recovery(not flashed, only booted) and found that I am unable to wipe internal storage. Everything else like, dalvik cache, data, cache and system do not give error on wiping. Also, I am unable to delete any file or folder using twrp file manager
Thank you.
Hi, so short story is.
1. I had a backup of my stock rom that i did using twrp.
2. I flashed Franco Kernel for COS 13 downloaded from his website (https://kernels.franco-lnx.net/OnePlusOne/6.0.1/anyKernel/)
3. When i flashed i performed a Wipe dalvik cache from recovery
4. Reboted phone, and started optimizing apps but suddenly it rebooted.
5. Started optimizing apps but when it showed optimizing app 1 of 103 the phone keept restarting.
6. I decided to restore my backup made from TWRP, but then phone got stuck and restated everytime from the CYANOGENOS logo.
7. Since it was not booting, i decided to install from fastboot a clean CM13.
8. Flashed, finished and then the phone restarted, but heeey, again stuck in the CYANOGENOS Logo and restarting when the logo shows up.
9. I freak out and I don't know what to do.
So far:
fastboot is working
Cyanogen Recovery is Working ( tried the wipe from that, but still no luck)
When I plug the device directly to my PC, it shows "QHSUSB_BULK", but as i say: fastboot and COS recovery are working.
Can you guys help me, please
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
leokook said:
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
Click to expand...
Click to collapse
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Mr.Ak said:
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Click to expand...
Click to collapse
Lesson learned.