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
Related
I really hope someone can help me out. I think I bricked my phone.
I tried to recover my phone back to stock with stock recovery so I can send it in for repair. When I installed 2.3.4 OTA update through zip, I accidentally clicked yes for updating 2.3.6. I didn't know, went to washroom and my phone won't boot. I thought no worries I'll install the zip again. Going into recovery, there's an android picture with an exclamation mark. I can't boot into phone and cannot load recovery. Someone please help >_<
download CWM and try to flash it through fastboot, and use that to flash a new img. im assuming you've done this before, having a custom recovery before now. if not, make sure you have fastboot setup, and if you don't go look through a rooting guide how to set it up then once you have it set up, move the new recovery you downloaded to the same folder as fastboot, then type
fastboot flash recovery name_of_recovery
of course replace the name_of_recovery with the exact filename of the recovery you downloaded. you can get the ClockworkMod recovery I think at www.clockworkmod.com
then boot into the new recovery and go to Mounts and Storage and Mount USB, and take the update.zip that you have and load it onto your SD Card, then go into the recovery and do as you would to flash the zip
Problem is, I don't think usb debugged was enabled. I tried to lock bootloader so I can just take it back to my carrier and say phone is screwed up, but when I tried, it said device not found.
The only way I think is using odin.
Bottom half of the screen is cracked which makes it very difficult to " swipe to" do anything in TWRP. I locked my device and was unable to unlock with backup pin because the keyboard does not function properly. So I rebooted into recovery and accidentally wiped Calvin Cache, System, Data, Internal Storage and Cache. Rebooted phone and it's stuck in a boot loop. I tried using adb but I could not get it to swipe into adb sideload. I found that connecting the phone to my PC does open up /SDCARD/TWRP but there are no other folders in /SDCARD. I moved a ROM from my PC to the TWRP folder and was able to flash it but got stuck in boot loop. Tried flashing a different ROM and it shows a new loading screen but still stuck in boot loop. No other folders are being created to SDCARD.. Haven't had this pphone for more than a week.... Was thinking I could maybe flash a non touch TWRP or CWM to avoid having to swipe to get things done and use the hardware keys.. but why is it being stuck in boot loop after it says it successfully flashed the ROM.
I did flash the 30b file it says to flash prior to flashing the 2 custom lollipop ROMs in the tmo dev forum. Any help, links, advise would be much appreciated. Thanks.
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 had my phone rooted on old Oreo version and wanted to reinstall the latest factory image. While I was doing this my laptop got a BSOD and the installation didn't fully finish. I redid the install but now my phone is in a bootloop. It will go past the Google logo but afterwards will loop on the dead Android guy with the ''No command'' message, same happens when I try to enter recovery mode. Is there something I can do?
I would flash TWRP and try wiping all including internal. Sounds like one of the partions is corrupted. You could do it with fastboot in bootloader mode but not sure of the commands.
teunnk said:
I had my phone rooted on old Oreo version and wanted to reinstall the latest factory image. While I was doing this my laptop got a BSOD and the installation didn't fully finish. I redid the install but now my phone is in a bootloop. It will go past the Google logo but afterwards will loop on the dead Android guy with the ''No command'' message, same happens when I try to enter recovery mode. Is there something I can do?
Click to expand...
Click to collapse
You're probably not used to the stock recovery. The no command droid is normal. Watch this video, and see if you can get to recovery or bootloader.
Hello,
First to get this out of the way i have searched the topic and there were several "solutions" none worked for me.
How it started, I downloaded the latest LieneageOS update as always, set the phone to do it's thing, came back and the phone was stucked on OP log, tried a little reboot, nothing.
No access to recovery or fastboot.
computer wouldn't recognize device even after installing drivers, this guide helped me a little https://forums.oneplus.com/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
found tools got fastboot back and original recovery.
via fastboot attempted to installed TWRP
fastboot flash recovery twrp****.img
and then tried to boot into recovery
fastboot boot twrp****.img
Not able to boot into twrp
after all that my phone still stucked on the boot OP logo
any help would be greatly appreciated.
Anyone has any idea, sorry I have been scouring and reading everywhere, but I can't find a solution.
Thank you
So i have been trying many things and finally getting somewhere. I apologize for the long post, but i have been trying so many things to get this device back to speed.
So flashing TWRP newer version for some reason is not letting me boot into recovery.
I have flashed twrp-2.8.7.0 and i am able to boot into recovery, however when trying to install the ROM (LineageOS 16) i get error E3004.
Searching the web i find that the correction is to that error is to update TWRP, thus i have tried flashing
twrp-3.2.1-0 and twrp-3.1.1-0 and once installed i am not able to boot into recovery again.
I flashed 2.8.7.0 and i was able to get in, thus from inside TWRP i did an image install of twrp-3.1.1-0 and rebooted, recovery won't load. I proceeded to repeat this until i get a result.
I flashed twrp-3.0.2-0 and be able to boot. However still not able to install LOS.
Once i tried flashing twrp-3.0.2-1, recovery won't load.
For sake of argument i flashed twrp-3.0.2-0 and attempted a image install for twrp-3.0.2-1, but the system still won't boot to recovery.
I have completely formatted the phone.
I hope someone could give me a little advice . Thank you.