Firstly the flash-all.bat wouldn't work, it kept failing at the boot.img, saying it wasn't in the file. I extracted all the parts of the zip and flashed them manually, and I got a bootloop. I flashed TWRP and did a factory reset from the recovery, it then booted into Android 5.0, but with no home keys at the bottom of the screen. I did a factory reset from inside 5.0, but it didn't fix it.
I then flashed a factory image of 4.4.4, got the same boot.img and had to manually flash all the parts. the flashed 5.0 over the top of the factory image, again with the boot.img is missing error, and again the home keys were missing.
I did another factory reset t see if it would fix it, but I still had no home buttons, so I ended up reverting back to 4.4.4, but when flashing that, I got the same boot.img error message, again. I had to manually flashed it and it booted into 4.4.4, and all is working.
Question is how do I get to 5.0 with home keys and not get the boot.img error message?
I had the same problem
unzipping the zip inside the tar.gz and following http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1"]efrant's guide (flashing all img's individually and in the proper order) worked for me.
Related
I'm having a problem getting into my recovery. I have the D800. It started out I sideloaded cwr thru twrp. And it said it flashed fine. I selected to reboot back into recovery and got a fastboot error. So i tried just rebooting and couldnt get passed the splash image. So I did the whole flash stock firmware. And after i got done with that, I think I did the ota update, And I got my phone rerooted. But still no recovery, it loads to a black screen and my pc says I have to format drives from like u-z but one has a folder titled image with these files. I've tried adb pusing and flashy and nothin,.Please help
never mind I got it fixed I think. Please delete post
I updated to Lollipop using adb and stock recovery. That worked great. Then I flashed TWRP and made a nandroid backup. I have not rooted again since I'm switching to Nexus 9. So I want to reflash stock recovery, but I didn't save it.
I have the original stock recovery from the mantaray-lrx21p factory image, but when I flash it and boot into recovery, it's just blank screen. I'm assuming the OTA update also updated recovery? Does anyone have a copy of stock recovery after the OTA Nexus 10 update I could borrow?
Thanks,
Steve
Interestingly, I find that if I flash the stock recovery from mantaray-ktu84p, then it works. So it's the stock recovery in mantaray-lrx21p that just shows blank screen...
Same issue here to? Fix
Galaxy 6s Os 6.2.8▪Ss° Pen
I think the fix is we need to get someone with the latest Lollipop patch to extract and give us the recovery.img?
When blank screen appears, press power button for few seconds until the green robot appears, then press power + volume up ( or down ). the stock recovery menu will show up
I don't get any robot when pushing power button on blank screen. After 10 secs, device reboots. Are you sure it works like this now?
Well this is strange. I started all over with ktu84p, then applied the OTA lrx21p update. After the update, the recovery still says ktu84p so it did not get updated by applying the OTA update. Is that what everyone else sees as well? If I flash the recovery.img from the lrx21p factory image, then I get the blank screen instead of robot.
So I'm stuck in boot loop and have been attempting to flash a factory image. I've downloaded the factory image from google, extracted it and ran flash-all. This however fails at the end when it attempts to flash the system.img. I then just flash the system.img by it self and it does successfully flash. however i'm still in boot loop.
Any ideas? Got the device yesterday and i'm softbricked already :crying::crying::crying:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Steeleio said:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Click to expand...
Click to collapse
Just restore the last stable nandroid you made.
What about fastboot
Steeleio said:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Click to expand...
Click to collapse
Are you using the new SuperSU beta? The play store / alpha version of supersu is not compatible with MM. I suggest more reading, specifically this thread: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page425
Also, because you did not fastboot flash the LP modem after returning to stock, your radio/wifi will not work. It's not an issue with the phone, but rather user-error. Fortunatally, it is a simple matter of getting you working again.
My advice is: Flash the stock unrooted MM TWRP backup (you should already be on the MM modem) and you should be able to start over. Just be sure to use the appropriate supersu beta, and DO NOT modify the boot image.
I attempted to update to '2PS6IMG_Sprint_2.51.651.22_signed_firmware' tonight (the 64mb zip file) and it said it worked, then powered off leading into a bootloop. It wiped twrp and I can access stock recovery, but I can't seem to flash anything, it gives me errors about signature verification. A factory reset yielded nothing but back to boot looping. I tried to re-do back to '2PS6IMG_2.42.651.63_RUU' (S-off) but it gave same errors. Any way to fix?
edit: disregard, RUU exe fixed it.