Last week I manually flashed 5.1 on my Nexus 5, because it was rooted an OTA update didn't work. It was working just fine, till yesterday. It's not rooted and it doesn't have custom recovery installed. My battery died and phone turned off. I charged it over night and turned it on in the morning. The phone was booting longer than usual so I left it and came back 2 hours later. It was still displaying boot animation. It's not restarting or anything, it just shows boot animation. I restarted it to bootloader, flashed 5.1 with Nexus Root Toolkit, the phone again stopped at boot animation. Then I went to cmd, used fastboot and erased partitions, flashed it again, it still didn't work. Then I flashed 5.0.1, it still stopped at boot animation. Then I flashed 4.4.4, it booted, play store didn't work, but I managed to install 5.0.1, this time over OTA. After it rebooted, guess what happened. It still stopped at boot animation. After that I installed TWRP, went to recovery, wiped ALL partitions and used TWRP partition repair function, rebooted to bootloader, manually flashed 5.1 AGAIN and my Nexus is still stuck at boot animation. I even tried erasing partitions, still didn't work. All flashings were done without any error reported. Any ideas what might be wrong? Bootloader and Recovery are fine, It boots without problems on KitKat. But I was using Lolipop without any problems for a few months now. Suggestions?
This is a strange issue. I did not found any solutions for that. What I have in mind is that backing up modemst1, modemst2, persist and misc partition then erase the whole emmc with boarddiag tool. This is a bit risky because if this error caused by a faulty emmc we may cannot reflash the bootloader after the emmc is erased because it will fail on some I/O error.
Related
A customer (I kinda do this for work) brought to me about 8 months ago a MZ604 full stock. I rooted, enabled BigPart, flashed CM11, customer happy. Yesterday he called me because the tablet boots to Android and immediately reboots. Easy, wipe, reflash, done.
Nope. Wiped data, rebooted. All the same. Wiped SYSTEM, I mean, deleting the ROM, all the same. It's like the memory is freezed (like on Windows when you reboot and everything you did in that session resets).
Tried RSD, stock ICS. No avail. RSD reports the flashing was succesful, but everytime I boot I get the same CyanogenMod animation. ROM boots, works for a few secs, and then reboots again.
I HAVE NOT A CLUE. Whatever I do, no change. Noting happens.
Also, when trying to change the recovery via fastboot, it reports it flashed correctly, but the recovery stays the same version.
I've got quite a peculiar problem with my Nexus 5.
Last night, I left my phone on charge. It was working normally and the software was functional etc. However, once I woke up, the phone was constantly restarting itself, and wouldn't load past the boot animation. I tried to load up fastboot to enter the TWRP recovery, however, the phone froze on the load screen. I should also add that my custom boot animation was replaced by the CyanogenMod mascot.
This problem has never occurred before, and I really haven't got a clue how to fix it. I tried to use WugFresh's NRT to flash a factory image of Android 6, however, the command terminal indicated that each process had failed. This did not restore the phone to its original condition.
I should also point out that I have been running a CM 12.1 nightly, which has been very stable and I have been using this nightly, without major problems (bar the infrequent system UI crashes) for a couple of months. It is obviously rooted and I have a Nandroid backup, which I can't access for aforementioned reasons.
Please could you help me with resurrecting my phone? I would be happy to clarify and elaborate upon any point of information.
Kind regards,
Sami
Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?
audit13 said:
Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?
Click to expand...
Click to collapse
I actually have tried to flash stock Android ROMs, from KitKat to Marshmallow, however, this didn't work as there was a 'write failure' and CyanogenMod wasn't removed. I did erase the cache, but to no luck.
Sounds like the memory module on the phone is defective. I had a Nexus 5 that would constantly re-lock the bootloader after I reboot. I had another N5 where the bootloader remains unlocked and a full wipe in recovery would finish in about 3 seconds which is far too short.
I could only solve both problems by replacing the motherboard.
Last night, I downloaded the 6.0 update, copied the .zip to external storage, rebooted to CWM, and flashed it (successfully), then flashed SuperSU over it, cleared dalvik, and rebooted.
Since then, I'm stuck with the Nvidia boot screen. I can use Power/Vol Up to get in to fastboot, but when I try to boot back into recovery, the screen goes black, but goes back to the Nvidia boot screen instead of booting to recovery, even after flashing a recovery image to it via fastboot.
I can probably fix this with enough time and tinkering, but I just came back from a two week from vacation at work and don't have the time to futz around with this. Posting here in case someone already has an idea on what the problem is/how to fix this.
Update: I was able to get back into recovery using TWRP referenced in http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541. Direct link is https://www.androidfilehost.com/?fid=24345424848487676.
I'm thinking this is a kernel issue.
This was a kernel issue. Flashing a older OTA (http://ota.nvidia.com/ota/data/post...wf-full_ota-36442_589.1541.20150826095201.zip) and booting normally, then rebooting to bootloader and fastbooting the CWM image worked. I'm restoring from a backup I took before flashing the update last night, then flashing TWRP, backing up, and trying this all over again.
Thank you, I was having the same issue :good:
Have the exact same issue, except that now, for some reason, I can't even get the device to turn on!
About a year ago, a friend gave me his Moto G so that I rooted it for him. On the system settings it showed as "falcon", XT1032. Everything was working fine. Then, he got a Moto G3, and gave his old Moto G to his young brother. After about two months, my friend told me that the old Moto G was in a bootloop, so I fixed it. Two weeks later, he told me the phone was no longer booting (it could barely boot into fastboot) and gave it to me again. Obviously, his young brother did something, but I don't know what, oh and also both times the battery was completely discharged when I received it.
So, I thought "Easy, just flash stock image and it will boot again". So I downloaded XT1032's stock image (5.1, as that was the version installed) and tried to flash it. Got many errors, both on PC fastboot/mfastboot and phone's fastboot. Also I couldn't boot or flash TWRP recovery, everything was broken. So I checked the model number on the battery, and it said it was XT1039, the 4G, peregrine version. So I downloaded peregrine's stock, and tried to flash it. Still got lots of errors (image size is too large, boot hab failed or something like that, I can't remember it clearly) but at least now I was able to boot TWRP recovery, but I still couldn't permanently flash it. There I checked the partitions, and they were corrupted, so I fixed them. Tried to flash again with no luck. Booted TWRP, tried to flash LineageOS, and got an error saying that the phone is the Falcon version! So, downloaded Falcon's Lineage, flashed it successfully, but the system won't boot, instead it will default to stock recovery (which was previously not working). AGAIN tried to flash Falcon's stock, now I'm back to the begining...
A solution I thought was intentionally bricking the phone completely and blank flash it, but I'm unsure how to do it, and I don't think is the best option...
BTW if someone could tell me how every partition is originally formatted so I can be sure all of them are fine, thanks.
So today I decided I wanted to root my nord, so I downloaded Magisk and a boot.img file but the boot.img was the wrong version. It installed okay at first. It rebooted and everything worked, but Magisk said that it hadn't been rooted fully and to restart, and this is where the problems began. I got stuck in a boot loop, so I went to recovery and factory reset it. When it was booted up, the wifi wasn't working at all. I restarted the phone and nothing happened, so I reset it again and had the same result. Then I thought to have a look at the files I used and finally realized that my boot image was two updates behind. I then got the boot image from the latest release on oneplus website and flashed it, but had the same result. The device is not currently rooted after I installed the stock image but wifi problems are still persisting. I tried relocking the bootloader, but it said my device is corrupt so it couldn't boot. So I unlocked the bootloader again and this is where I am now. Any advice/ help would be hugely appreciated.
Spinningtop22 said:
So today I decided I wanted to root my nord, so I downloaded Magisk and a boot.img file but the boot.img was the wrong version. It installed okay at first. It rebooted and everything worked, but Magisk said that it hadn't been rooted fully and to restart, and this is where the problems began. I got stuck in a boot loop, so I went to recovery and factory reset it. When it was booted up, the wifi wasn't working at all. I restarted the phone and nothing happened, so I reset it again and had the same result. Then I thought to have a look at the files I used and finally realized that my boot image was two updates behind. I then got the boot image from the latest release on oneplus website and flashed it, but had the same result. The device is not currently rooted after I installed the stock image but wifi problems are still persisting. I tried relocking the bootloader, but it said my device is corrupt so it couldn't boot. So I unlocked the bootloader again and this is where I am now. Any advice/ help would be hugely appreciated.
Click to expand...
Click to collapse
Reflash the rom but erase everything then flash.
Spinningtop22 said:
So today I decided I wanted to root my nord, so I downloaded Magisk and a boot.img file but the boot.img was the wrong version. It installed okay at first. It rebooted and everything worked, but Magisk said that it hadn't been rooted fully and to restart, and this is where the problems began. I got stuck in a boot loop, so I went to recovery and factory reset it. When it was booted up, the wifi wasn't working at all. I restarted the phone and nothing happened, so I reset it again and had the same result. Then I thought to have a look at the files I used and finally realized that my boot image was two updates behind. I then got the boot image from the latest release on oneplus website and flashed it, but had the same result. The device is not currently rooted after I installed the stock image but wifi problems are still persisting. I tried relocking the bootloader, but it said my device is corrupt so it couldn't boot. So I unlocked the bootloader again and this is where I am now. Any advice/ help would be hugely appreciated.
Click to expand...
Click to collapse
You needs msmtool to restore the phone to a stock image. Search in xda and follow the steps, its easy