Related
Ok so
Rooted
S-off
hboot 1.12.2222
was running Mean-rom 4.4
Then tried to install the new apk fix for ringtones
http://forum.xda-developers.com/showthread.php?t=1900629
Phone rebooted then then continues to be stuck in boot loop.
What I have tried:
Factory reset in bootloader
clear storage in bootloader
reinstall TWRP to get in recovery as if I choose recover in bootloader it just boot loops.
Tried to install the RUU but it can not connect during boot loops and errors out.
Any ideas?
Thanks in advance
Try fastboot wipe recovery then fastboot flash recovery recovery.img, if recovery loops back to bootloader then it's corrupt. Make sure you flash the latest twrp
om4 said:
Try fastboot wipe recovery then fastboot flash recovery recovery.img, if recovery loops back to bootloader then it's corrupt. Make sure you flash the latest twrp
Click to expand...
Click to collapse
All I see in fastboot option on bootloader is
bootloader
reboot
reboot bootloader
powerdown
am I missing something?
Those are fastboot commands, you use the terminal
fastboot wipe recovery
fastboot flash recovery recovery.img
You should be able to boot into recovery afterwards
What terminal? I'm a bit lost here
Do you have adb tools or Android SDK?
C:\android-sdk-windows
Open cmd prompt by opening SDK folder and then hold shift and right click, it will say open cmd prompt or something similar I don't recall if adb is in separate folder but I don't think so. From there you can plug in the phone in fastboot and type fastboot devices, it will tell you if you are connected or not. Download twrp and place it in the same folder. Then you can use the commands I listed earlier
om4 said:
Open cmd prompt by opening SDK folder and then hold shift and right click, it will say open cmd prompt or something similar I don't recall if adb is in separate folder but I don't think so. From there you can plug in the phone in fastboot and type fastboot devices, it will tell you if you are connected or not. Download twrp and place it in the same folder. Then you can use the commands I listed earlier
Click to expand...
Click to collapse
Get an error see attached
Now that I am in fasboot usb on the bootloader the RUU can connect to phone via USB.
If I just flashed that and started all over would that work and do I need to unroot and relock before doing the RUU?
Still not having any luck on terminal so far.
Sorry I was busy arguing with gf, it seems you aren't where you need to be if fastboot isn't recognized, I haven't had access to my own pc in quite a while so I'm having trouble remembering if there is another directory
om4 said:
Sorry I was busy arguing with gf, it seems you aren't where you need to be if fastboot isn't recognized, I haven't had access to my own pc in quite a while so I'm having trouble remembering if there is another directory
Click to expand...
Click to collapse
got fastboot working but get this with your first command
That's because I haven't used wipe in fastboot in quite a while, I'm sure I'm just confused on wipe and erase but you shouldn't need it, the first command should be fastboot erase recovery but like I said you shouldn't really have to, it's just like formatting before flashing the recovery, just fastboot flash recovery openrecovery.img or what ever the name is for the twrp file
Ran
C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7356 KB)...
OKAY [ 1.112s]
writing 'recovery'...
OKAY [ 1.796s]
finished. total time: 2.912s
Hit recovery and we we still are in boot loop
Relock bootloader and run ruu fastboot oem lock
copc said:
All I see in fastboot option on bootloader is
bootloader
reboot
reboot bootloader
powerdown
am I missing something?
Click to expand...
Click to collapse
select bootloader the recovery as soon you have recovery up wipe and reflash the rom
HTC EVO LTE
luisrod03 said:
select bootloader the recovery as soon you have recovery up wipe and reflash the rom
HTC EVO LTE
Click to expand...
Click to collapse
Thanks recovery just loops, could never get in.
Ok this is where I am at (see OP)
We tried flashing TWRP and original recovery via ADB
We tried running RUU
I'm still stuck in a boot loop....
I am having a similar problem stuck in bootloader. I relocked to go to the new firmware and now am stuck in the bootloader. I can access adb but can't access recovery. I am now relocked. Can I unlock again with a fastboot command?
If you unlocked manually, HTC sends the unlock code code just use fastboot to flash, if you used regawmod, just run it again. I don't know if regawmod will recognize the phone in boot loader though
Sorry, this is likely a noob question. I am working to flash a new rom on my ATT HTC One (cant stand all the ATT BS). I was trying to get the Android_Revolution_HD-One_12.0 working. I have unlocked the phone, and flashed a custom recovery image (stock image linked here http://forum.xda-developers.com/showthread.php?t=2224752) The boot loader now shows unlocked and tampered. Next I attempted to enter the recovery mode, when I select it the phone appears to reboot then shows me a pic of a phone with the green circle of arrows on it for a few secs then pic of a phone with a red exclamation mark. After a few minutes the phone will then reboot and run normally.
I have tried:
1) 'fastboot erase cache' prior to entering recovery
2) adb reboot recovery command
3) GooManager to load TWRP, which it did, but it will not load a rom (says its starting then nothing happens) or reboot into recovery (nothing happens)
All of these result in nothing happening or the same phone with green circle, then phone with red exclamation... I have not been able to access the recovery menu... any other ideas, or am I missing something
Thanks
T
bluecoller33 said:
Sorry, this is likely a noob question. I am working to flash a new rom on my ATT HTC One (cant stand all the ATT BS). I was trying to get the Android_Revolution_HD-One_12.0 working. I have unlocked the phone, and flashed a custom recovery image (stock image linked here http://forum.xda-developers.com/showthread.php?t=2224752) The boot loader now shows unlocked and tampered. Next I attempted to enter the recovery mode, when I select it the phone appears to reboot then shows me a pic of a phone with the green circle of arrows on it for a few secs then pic of a phone with a red exclamation mark. After a few minutes the phone will then reboot and run normally.
I have tried:
1) 'fastboot erase cache' prior to entering recovery
2) adb reboot recovery command
3) GooManager to load TWRP, which it did, but it will not load a rom (says its starting then nothing happens) or reboot into recovery (nothing happens)
All of these result in nothing happening or the same phone with green circle, then phone with red exclamation... I have not been able to access the recovery menu... any other ideas, or am I missing something
Thanks
T
Click to expand...
Click to collapse
I think your trying to flash the stock recovery image. You need to flash either TWRP or CWM custom recoveries. GO to this link and at the bottom it will show the commands to install TWRP from fastboot. It will also give you the link for the newest version of twrp, which is 2.6.0.0 i believe,
http://forum.xda-developers.com/showpost.php?p=42556698&postcount=24958
Hope it helps
Jmarv said:
I think your trying to flash the stock recovery image. You need to flash either TWRP or CWM custom recoveries. GO to this link and at the bottom it will show the commands to install TWRP from fastboot. It will also give you the link for the newest version of twrp, which is 2.6.0.0 i believe,
http://forum.xda-developers.com/showpost.php?p=42556698&postcount=24958
Hope it helps
Click to expand...
Click to collapse
Exactly as he said above. Download twrp (I stuck with 2.3.3.1 bc 2.5 was having problems flashing ROMs)
Put the twrp file in your folder that has fastbootand launch a CMD window (hold shift and right click, there will be an option to launch a CMD window)
Boot into the bootloader and then fastboot (be sure your phone says Fastboot USB)
on the command terminal type:
fastboot devices -- to make sure your device is being recognized (should say HTXXXXXXXXXXXXXX)
fastboot erase cache -- clears cache
fastboot flash recovery recovery.img (recovery.img is the name of the twrp file you downloaded EXACTLY)
Worked like a Champ, thanks for the help. I loaded twrp and the rom installed without a hitch. This phone us definitely faster now that all of the att crappie is gone.
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.
Thought I'd dust off my old TF201 (rooted) and put the KatKiss Nougat ROM on to see how it performs; was previously running CromiX.
I booted into TWRP recovery and did a full wipe and format of /data, then upgraded TWRP to 2.8.7.0 using the kang flashable zip. So far so good. Rebooted into the new TWRP and tried to upgrade TWRP further by loading a TWRP 2.8.7.2 image file via the TWRP settings. Rebooting recovery now fails - I get an error message in bootloader that there was an "unrecoverable bootloader error (0x00000000)" and it locks up.
I've tried reloading TWRP 2.8.7.0 via fastboot using
Code:
fastboot -i 0x0B05 flash recovery <image_file>
; this appeared to work, but rebooting into recovery now either gives the bootloader error message above, or else it briefly flashes the screen, restarts the bootloader and the cursor flashes over the Android icon and can't be moved with the volume down switch. If I select this option with volume up, I get four penguins followed by a "preinit starting" message and then a bunch of "=" symbols before it locks up again.
Rebooting into fastboot allows me to send fastboot commands from my PC, but adb commands fail with "no devices/emulators found".
I've reached the end of my experience and have no idea what to try next. Could someone please offer some advice on how to proceed?
Thanks!
Solution found
If anyone's interested in such an ancient tablet... post #12 in the TF300 support thread held the answer. They are generic fastboot commands, so the model of the tablet really doesn't matter.
I'm now back to stock 4.1 and ready to start over.
I was attempting to unlock my bootloader and managed to fat finger one of the critical pieces. When typing fastboot -i 0x1949 erase aboot, I typed in fastboot -i 0x1949 erase boot. Which erased by boot partition. Now my device dutifully sits at the grey Kindle Fire logo, but never boots. I haven't otherwise done anything to this device, and it was running on a fresh installation of 4.5.5.3.
I can still access fastboot via a fastboot cable. I attempted to fix the issue by loading the boot partition with the boot.img found in the latest Amazon update files, but it didn't seem to have any effect.
I also attempted to boot into bulk mode, but issuing the command to erase the aboot partition returns a message that there is no aboot partition?
Is this a recoverable situation?
leeharrison1984 said:
I was attempting to unlock my bootloader and managed to fat finger one of the critical pieces. When typing fastboot -i 0x1949 erase aboot, I typed in fastboot -i 0x1949 erase boot. Which erased by boot partition. Now my device dutifully sits at the grey Kindle Fire logo, but never boots. I haven't otherwise done anything to this device, and it was running on a fresh installation of 4.5.5.3.
I can still access fastboot via a fastboot cable. I attempted to fix the issue by loading the boot partition with the boot.img found in the latest Amazon update files, but it didn't seem to have any effect.
I also attempted to boot into bulk mode, but issuing the command to erase the aboot partition returns a message that there is no aboot partition?
Is this a recoverable situation?
Click to expand...
Click to collapse
@draxie - thoughts?
I managed to get back in to TWRP by manually installing it via fastboot.
dl.twrp.me/soho/
However, my real problem was I was using my Soho KF, not a Thor/Apollo variant.
I managed to get things sorted and unbricked the Soho, thanks for showing up though!