I have the HTC M8 Dev edition. My bootloader is unlocked, I'm S-ON, and I previously had installed TWRP.
I wanted to go back to stock recovery to download OTA updates.
Went to the collection thread (found here) and downloaded the 1.54.1540.9 recovery, as it perfectly matches mine.
I used the Hasoon2000 All-in-one toolkit to flash the recovery after renaming it to recovery.img. Now when I boot to recovery I get the red triangle/exclamation point error.
What should I do to get the recovery working properly? I'm not too experienced with ADB, but I have rooted and flashed recoveries before (using tools/toolkits for the most part).
Thanks in advance!
EDIT:
Whoops, it probably worked the first time, but the triangle/! didn't appear to mean anything. I waited a couple seconds after flashing with CMD/fastboot only and stock recovery came up. Sorry for the n00bery. Kit Kat update installing. Thanks all! Learn from my mistakes if you googled this.
Related
Here is what I did
I unlocked the bootloader
I installed CWM
I used CWM to flash superuser
I flashed a ROM (latest MIUI to be specific)
S is also ON. I know it should be off, how can I turn it off at this point?
I can get into recovery, I can install ROMs but the phone will not boot past the HTC logo... help
got a rom to start but now the keyboard keeps crashing :-\
I am wondering if I can get s-off from here? I'm on bootloadeer .98 btw
So, there's two things you can do. You can go back to recovery and download a ROM that's not the current MIUI, which is really buggy. Then, follow my guide #6 in the directory for how to flash ROMs after doing the HTC unlock.
The problem I am having is that I have a custom Recovery installed with S-ON. I need to turn S-Off before I can do any of that. I followed your guide in 6 which links me to a post on installing the recovery, however those instructions state that S must be off. The only ROMs that work are those that resemble stock or install a boot.img in recovery
Hello there,
I might have ****ed up.
I was on ViperOne 1.8.0 for a long time, but decided to wait for L which is now here.
As I know, I need a new firmware flashed, but as I wasn't on s-off, every method failed (FUU flasher and also flashing via adb, it rejected the file)
So I decided to give sunshine a shot to s-off my phone, but dang, it didn't want to as I am not on a stock boot img.
So, what was the logical step? Flash a stock boot img, the newest one. boot_3.28.401.9.img it was.
Now I am stuck on the white htc boot screen, combination for recovery (power+voldown) is not working. Can't switch the phone off or anything, it just is stuck there. Well actually it runs, I get message notifications and the LED blinks and I can also connect via USB but I just don't get into the user interface.
I can however reboot it by pressing power+volup, but it just gets stuck in the white screen again respectively is running but stuck in the whitescreen.
Installing RUU does not work. Phone is not recognized albeit being accessible in Windows Explorer.
adb is not working, doesn't recognize the phone so also no way to get into recovery or bootloader.
How am I supposed to flash stock img now to get it back to life?
Okay, got into bootloader now by pressing Power+VolUp and then VolDown.
I tried to flash 4.16.401.10-Firmware.zip from http://forum.xda-developers.com/showthread.php?t=2701376
but it says signature verify fail
So how can I get a valid firmware on my phone so I can flash TWRP and Viper and be happy?
What could be possible is to flash the ViperOne's boot.img (of the one I have installed) but that won't help me get newest firmware and lollipop.
Trying the old fashioned way now... got myself a TWRP backup of the stock image that corresponds to my firmware. Hopefully it will install and boot through. Then I just let it OTA all the way up until I got the newest version, then firmware and everything should be right and I can flash Viper. Hope that works.
After you flash the TWRP backup you will need to restore the stock recovery as OTA updates won't work with TWRP
Yup, did that. Thank god, it boots now.
I am on a super old System now of course, like last June or something.
But all I should do now is let it OTA all the way up to lollipop, right? Then I'll have firmware and everything up to date so I just unlock again, flash TWRP, flash my Rom and be done?
Probably easier to connect in fastboot and use fastboot getvar all to give more details on your details (remove your IMEI and serial number)
Hello guys,
Just got my m9 a few hours ago, decided to root,s-off etc
Anyway, I did something stupid and Im stuck on the android logo.
Here is what I did.
-I updated the device through the stock recovery, there was another update but I didnt install i.
- unlocked the bootloader, phone rebooted and was working fine
-installed costume recovery(TWRP), I didnt boot into it because there wasnt and option like in the m8 to boot in recovery from bootloader.
-I reset the device and installed the update(stupid move I knew the stock recovery is not there)
- I got into TWRP and the updated failed so I had the SUbinary.zip so I plashed it and decided to reboot
-Here I got a note that theres no OS installed so I installed android Revolution, I placed it in the sdcard prior
- after flashing it I pressed on reboot yet I get no OS installed and now im stuck on the HTC logo.
BTW I can boot into boot loader but it says sd card not mounted (64GB)
Edit:
I entered into recovery, flashed AR again,its installs everything normally but I realized on the installation log last line : set_metadata_recursive: some changes failed
still I get no OS installed
I got it working now. Anyone whos having this problem just use the beta recovery because the official one is broken
here's a like https://basketbuild.com/devs/Captain_Throwback/One (M9)/Recovery
just flash it normally and install the rom again.
now i will have to go back to stock recovery and download the OTA the flash TWRP again -.-
will the OTA work on the ARHD and stock recovery or thats not possible?
mr.dj26 said:
Hello guys,
I got it working now. Anyone whos having this problem just use the beta recovery because the official one is broken
here's a like https://basketbuild.com/devs/Captain_Throwback/One (M9)/Recovery
just flash it normally and install the rom again.
now i will have to go back to stock recovery and download the OTA the flash TWRP again -.-
will the OTA work on the ARHD and stock recovery or thats not possible?
Click to expand...
Click to collapse
I dont think the OTA will work.
either find the latest full RUU and flash it, or an older RUU, flash it, then do all the available OTAs.
Then redo TWRP and ARHD.
x51 said:
I dont think the OTA will work.
either find the latest full RUU and flash it, or an older RUU, flash it, then do all the available OTAs.
Then redo TWRP and ARHD.
Click to expand...
Click to collapse
hey there, thanks for the reply.
I think ill do the s-off first then ill download the RUU like this guy http://forum.xda-developers.com/one-m9/help/tut-ota-successfully-1-32-401-15-to-1-t3091911
i wish i updated before
I did the same thing twrp no OS installed and restarted now I am stuck at the htc logo and I can't get it to restart. Please help?
I tried power and volume down and it's not responding.
edit:
pressed all the buttons and got into recovery. went into download mode and updated twrp and reflashed android hd. working now.
thunderwolf333 said:
I did the same thing twrp no OS installed and restarted now I am stuck at the htc logo and I can't get it to restart. Please help?
I tried power and volume down and it's not responding.
edit:
pressed all the buttons and got into recovery. went into download mode and updated twrp and reflashed android hd. working now.
Click to expand...
Click to collapse
Thats good to hear, sometimes TWRP will say that there isn't any OS installed but actually there is just reboot the device.
After updating through the OTA I installed ARHD and I got the same error again with the latest recovery. I think its because when I did wipe the data there root directory is changing make the phone unable to boot or there is a problem with the rom although it flashed before the update.
Here is a fix http://forum.xda-developers.com/one...h-recovery-t3066720/post59934542#post59934542
If it didn't work try to format data in the recovery and reboot. Make sure you have a ROM or back up on an SD card.
Since your phone is running I would suggest you to S-off because from what I understand is RUU (for Europe) will only work with S-off
http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
hope this helps others
Hello all!
I recently flashed the 4.16.xx firmware to my device. I am now stuck on the Bliss Rom bootscreen for some reason. Booting into recovery takes me to stock recovery and the phone isn't being recognized through ADB on several different PC's.
Am I screwed here? Any options?
Thanks for any input.
Try going into the fastboot option from the hboot (or called bootloader to many people. To get to hboot, do power and volume down when the phone is booting up. ) and try flashing your TWRP recovery from there. Also make sure your drivers are working.
If you don't know how to flash recovery just Google it, you should be fine.
Dw, dont panic, it'll be fine xD
Zomb!e said:
I recently flashed the 4.16.xx firmware to my device. I am now stuck on the Bliss Rom bootscreen for some reason. Booting into recovery takes me to stock recovery and the phone isn't being recognized through ADB on several different PC's.
Click to expand...
Click to collapse
Stock recovery is the logical result for flashing firmware, unless the firmware was hacked to remove stock recovery.
adb not working, is also normal. You need to be in OS or recovery to use adb commands (and I don't know whether you can with stock recovery). adb does not work in bootloader.
If you flashed an official firmware with s-on, then not boot is also the expected result.
You need to unlock the bootloader again, flash TWRP back onto the phone, and flash a ROM.
redpoint73 said:
Stock recovery is the logical result for flashing firmware, unless the firmware was hacked to remove stock recovery.
adb not working, is also normal. You need to be in OS or recovery to use adb commands (and I don't know whether you can with stock recovery). adb does not work in bootloader.
If you flashed an official firmware with s-on, then not boot is also the expected result.
You need to unlock the bootloader again, flash TWRP back onto the phone, and flash a ROM.
Click to expand...
Click to collapse
Hey thanks for the reply!
I figured it out finally and forgot to update the post. I ended up finding and flashing a Lollipop RUU from the SDcard and that got me booted up. Then I just had to re-flash TWRP, re-root and flash a new rom.
All is well now. Thanks for trying to help out.
So, I was attempting to root my phone(CanvasA1- 4GB) today running stock android marshmallow(6.0.1) , I successfully unlocked the boot loader in fastboot using adb, after which I flashed TWRP recovery, Which was successful but then, When I rebooted into recovery, I saw my old stock google's recovery running , I tried 2-3 more times flashing the recovery in fastboot but the probem was still the same :crying:. Then I came to know that we have to flash a special type of boot img of some 17.5mb approx, When I attempted to flash this "boot" image, I received an error saying file size too large, Hence I couldn't flash it, I am still running the stock recovery, With my bootloader unlocked, I need to root my phone, Please help someone, Thanks in advance .
http://forum.xda-developers.com/cro...-master-tool-unlock-bootloader-t2997696/page1 use this tool and flash custom recovery simple
You can search for Android One Toolkit. Iwas encountering the same problem but this app solved my Problem.
Sorry dont have Link for the Same.
Same here. I unlocked the bootloader successfully and flashed TWRP recovery. But it shows system/default recovery only. Now stuck in bootloop.
Tried clearing cache/date etc. nothing worked. Don't know what to do.