I'm a nitwit and tried to install a rom with s-on. I now get stuck on the HTC loading/boot screen and never leave it. I can access the bootloader, fastboot, and recovery fine however. Is there a way for me to get either s-off or boot my phone again?
Thanks
This is assuming that you're S-on and running Windows.
You need to install adb. After it is installed, open the command prompt and navigate to where you installed adb.
Ex: d:\phones\rezound\bootloader\andriod\
Next, open up your ROM and extract the boot.img file to where you installed adb.
Then, boot your phone into the bootloader and connect your USB cable.
Once you have fastboot usb displayed on the phone, enter this command into the command prompt and hit enter: fastboot flash boot boot.img
At that point, reboot the phone (fastboot reboot).
Or just use adb/fastboot and boot into recovery, extract the recovery.img file from your recovery of choice (Amon Ra, TWRP, CWM) and place it in the adb directory, then type "fastboot boot recovery.img" and flash the ROM again... doing fastboot boot recovery.img is in some ways giving you temporary S-OFF and will allow the rom to flash with the boot image. Also remember that on first boot, many roms will appear to freeze for 2-3 minutes or even longer in the boot process, make sure to give the initial boot at least 10 minutes before concluding something failed.
Hello,
I am using Asus Zenfone 5 T100J. I have rooted my phone and run the TWRP 2.8.7.0 custom recovery in it. The Rom running the phone is Resurrection Remix 5.5.8. Today I tried to flash a custom kernel in my phone and accidentally typed "fastboot flash fastboot boot.img" instead of "fastboot flash boot boot.img" . yea I override the stock fastboot with a kernel! My mistake!!
Now the issue is that I cant access the fastboot. I can switch On the phone, use recovery (thanks to Advanced Reboot) and phone works fine. But cant use adb since there is NO fastboot.
There is no point in pressing Vol Up + Power since the actual fastboot may be corrupted, thanks to myself.
guys please help me get my droidboot back... I cant even sideload using TWRP (Device not detected when sideloading, otherwise device is visible). I badly want droidboot to flash using adb. Kindly help. Thanks in advance..
I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
xavier55 said:
I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
Click to expand...
Click to collapse
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
thanks you saved me
baymon said:
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
Click to expand...
Click to collapse
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
soltheman said:
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
Click to expand...
Click to collapse
Thanks for the follow up! No the phone would not boot at all and kept stuck at boot loop. I ended up just doing the OEM Lock and call it a day, the old device just won't boot to anything at this point.
I tried fastboot flash recovery recovery.img but it's giving some kinda kernel panic message and I was never able to get into recovery. This reminds me of the time when my Note 3 eMMC was fried, it wouldn't give a device ID to adb.
I think I am in the same boat too. I've been OEM unlocked yet recently my phone won't keep the TWRP recovery and keeps putting me into bootloop. I can't install a ROM and only thing I can do is fastboot mode. What did you do OEM lock the device? I am hoping that solution will get rid of that message bootloader unlocked during the bootloop and then I can try and get it serviced.
Hello!
Now I have a trouble with my Nokia 7.1.
When I try to boot twrp or another kernel (boot.img) it stuck. I do '"fastboot boot twrp.img" or "fastboot boot boot.img" and my phone frozes on Android One logo.
And if problem with twrp can be solved (first enter "fastboot flash recovery twrp.img" and only than "fastboot boot twrp.img"), problem with boot.img is still relevant.
I noticed, that after "fastboot boot ..." phone restarts into download mode.
My phone is unlocked.
Thank
Hi, before any boot command, you'll need to do that flash recovery counterpart. You can do it on a standard boot image as well, not just TWRP. There's no recovery partition, so, nothing gets flashed. But it somehow allows us to boot our bootable img files.
So,
Code:
fastboot flash recovery boot.img
fastboot boot boot.img
singhnsk said:
Hi, before any boot command, you'll need to do that flash recovery counterpart. You can do it on a standard boot image as well, not just TWRP. There's no recovery partition, so, nothing gets flashed. But it somehow allows us to boot our bootable img files.
So,
Code:
fastboot flash recovery boot.img
fastboot boot boot.img
Click to expand...
Click to collapse
Yes! Thank you.
I recently came to this conclusion, but what is it?
Does it bootloader bug or anything else?
i have similar problems and just started a new request
I have bricked my X3 SZ and worked 1 week to get it unbricked (bricked after update of Android 11) myself, even the service centre not able to restore it and told me that may be Motherboard Problem. Finally by flashing Android 11 Stock images (created using OFP to CMD file converter), I restore the phone. I tried with unlocked Bootloader mode, don't know about locked bootloader state.
Simply download the stock images from the link and boot into bootloader mode, connect to PC, open Minimal ADB Fastboot and flash with fastboot commands. Required USB, Realme, Android Drivers to be installed in the PC. All your data will be lost and do it at your own risk.
Download all the images (userdata, recovery, boot, vbmeta & dtbo) and copy to the Minimal ADB Fastboot folder, run the CMD prompt and run the following commands:
fastboot devices (to check whether phone connected successfully or not)
fastboot erase userdata
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash userdata userdata.img
fastboot flash dtbo dtbo.img
fastboot reboot
Done.. your X3 SZ must reboot and starts, if not you need to work around or contact SC.. Good Luck
Link Deleted
Thx
EDIT: Very informative and useful!
Cant get magisk_boot.img to work. Going to try orangefox recovery to install Magisk (root).
Tried numerous times to install it (here) took 3-4 hours to get Python to work in windows 7 (cus missing libraries, and newer version dont work). Its bricked the phone 3 times now.
I tried to install TWRP but failed, after I tried Orangefox, successfully installed but not able to boot, rebooting into recovery only, then I flashed only boot image using fastboot and able to boot but lost Custom Recovery. After all I stopped trying anything on X3 SZ
please provide new link