Hello,
I am having trouble returning my M8 back to stock. I am following this guide: http://www.droidviews.com/restore-att-htc-one-m8-stock-firmware/
I was able to flash RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2.exe without any issues, and then proceeded to unlock the bootloader successfully as well.
My issue is getting into TWRP after flashing. I issue the commands:
Code:
adb fastboot reboot
fastboot erase cache
fastboot flash recovery twrp-3.0.0-1-m8.img
And it says that the write is successful, but when I go back to HBOOT to boot into recovery, It gets stuck with the "htc" logo and a pink text "Entering Recovery..." at the top of the screen. If I do an
Code:
adb devices
, it shows my phone and status "recovery".
I'm thinking that the recovery flash isn't sticking or maybe I have the wrong version (I believe I flashed the latest). Or maybe its entirely something else but I'm starting to run out of options. I've also tried rebooting into the bootloader after flashing recovery and just doing "fastboot reboot" and then trying to go back into recovery from a powered-off state but I still get stuck.
Here is my current fastboot Info:
Code:
***UNLOCKED***
M8_UL_CA PVT SHIP S-OFF
CID-CWS__001 ;;I recently flashed this from Super CID
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.58.502.1
eMMC-boot 2048MB
Apr 18, 2014,16:06:33.24624
Thank you in advance for your help.
- Kristian
The RUU you used is far too old to work with the TWRP version 3.0.0.0. Mixing old/new hboot, OS versions with new recovery versions is usually a bad idea.
The fact the guide you are using is from 2014 (!) is doing you no favors. That RUU is 3 Android versions obsolete. Relock the bootloader, than run the (current latest) 4.28.502 RUU as linked in my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
What is your intent in returning to stock? That guide is far too complicated for most purposes, aside from returning to HTC for warranty (for which, most M8 devices no longer have valid warranty).
For most purposes, relocking the bootloader and RUU is good enough.
@redpoint73
Thanks for replying. I was able to successfully go back to stock for the most part. I wanted to do a factory reset to see if it would fix my camera issue (auto-focus was broken and constantly re-focusing). Anyway, it didn't immediately help, but somewhere along the lines the camera fixed itself. Thanks again!
Related
I have the security warning error on my Thunderbolt. I need the files to fix it, maybe the instructions too if they changed from the post by jcase.
Here's what I have.
*** Security Warning ***
MECHA XD SHIP S-ON
HBOOT-1.05.0000
MICROP-/
RADIO-1.48.00.0906W_1
eMMC-boot
The rest is unknown.
Edit* I unlocked the bootloader, and I can now get into clockwork.
My new problem is that now I am not getting past the splash screen.
Okay. I have fixed the problem. Here's what I did.
1. I unlocked the bootloader via the official method at htcdev.com.
That removed the security warning and allowed me to access recovery. However, I had flashed clockworkmod recovery and nothing I did with any version of clockwork or Amon Ra would allow me to boot up past the HTC splash screen.
2. I erased the recovery partition and restored the original recovery via fastboot.
3. I rebooted into the stock recovery. It did something and rebooted, but still not past the splash screen.
4. Back to fastboot. I used fastboot commands to boot clockworkmod recovery without installing it. I then used clockwork to restore my original nandroid backup, and reboot.
Still not booting past the splash screen, but I did gain ADB access.
5. I decided that had everything back to stock, I would try revolutionary again. It actually worked this time. When it finished, I had S-off and a custom clockwork-mod recovery. With S-off, I was able to flash a rom of my choosing after wiping data and both caches.
That is all it took to go from an expensive paperweight to a fully functioning Thunderbolt.
Hey,
I'm lost in the process of freeing my HTC Sensation. I bought it used and it's T-Mobile branded (cidnum: T-MOB101) and came with hboot 1.18.0000 and some 2.3 firmware.
After revolutionary did not work, I unlocked the bootloader with htcdev.com/bootloader. The installation of some "ClockworkMod Recovery v5.8.0.9" (with touch enabled) via "fastboot flash recovery" worked flawlessly.
I tried flashing several ICS images, to get one of it booting and saw bootloops and the phone being stuck. The CyanogenMod 9 nightly finally booted, after manually flashing the boot.img from the zip file with "fastboot flash boot". The setup wizard is shown after boot but freezes when tapping to select the language or to continue. After some seconds, the phone reboots and behaves like before (freezes, reboots).
With flashing SuperSU from CWM Recovery I got root.
Since in the thread for the CyanogenMod 9 nightlies it's stated, that the latest firmware (3.32) is required, I will have to update to an unlocked (S-OFF) hboot and current radio image, I presume. But how is this possible? I could not get it to work with
* a PG58IMG.zip (for cidnum: T-MOB101) on sdcard and booting into the bootloader,
* "fastboot flash hboot $path" (or "fastboot flash radio $path"),
* "flash_image hboot $path" (from booted CM9).
Step 4 in this guide did not work, because I get no confirmation to update. The bootloader just unpacks, parses end returns to the menu.
Changing the cidnum with "fastboot oem writecid 11111111" did not work.
Does somebody know, how to navigate out of this labyrinth?
Thanks in advance!
henning
phects said:
Hey,
I'm lost in the process of freeing my HTC Sensation. I bought it used and it's T-Mobile branded (cidnum: T-MOB101) and came with hboot 1.18.0000 and some 2.3 firmware.
After revolutionary did not work, I unlocked the bootloader with htcdev.com/bootloader. The installation of some "ClockworkMod Recovery v5.8.0.9" (with touch enabled) via "fastboot flash recovery" worked flawlessly.
I tried flashing several ICS images, to get one of it booting and saw bootloops and the phone being stuck. The CyanogenMod 9 nightly finally booted, after manually flashing the boot.img from the zip file with "fastboot flash boot". The setup wizard is shown after boot but freezes when tapping to select the language or to continue. After some seconds, the phone reboots and behaves like before (freezes, reboots).
With flashing SuperSU from CWM Recovery I got root.
Since in the thread for the CyanogenMod 9 nightlies it's stated, that the latest firmware (3.32) is required, I will have to update to an unlocked (S-OFF) hboot and current radio image, I presume. But how is this possible? I could not get it to work with
* a PG58IMG.zip (for cidnum: T-MOB101) on sdcard and booting into the bootloader,
* "fastboot flash hboot $path" (or "fastboot flash radio $path"),
* "flash_image hboot $path" (from booted CM9).
Step 4 in this guide did not work, because I get no confirmation to update. The bootloader just unpacks, parses end returns to the menu.
Changing the cidnum with "fastboot oem writecid 11111111" did not work.
Does somebody know, how to navigate out of this labyrinth?
Thanks in advance!
henning
Click to expand...
Click to collapse
You need to S Off first to be able to flash boot.
Go to the tool in my signature. Check your PMs.
kgs1992 said:
You need to S Off first to be able to flash boot.
Go to the tool in my signature. Check your PMs.
Click to expand...
Click to collapse
Looks like this only works on Windows. Sorry, forgot to say, I'm on Linux. I will try to understand what you did there and transfer it to Linux.
Thanks!
Tried to root and unlock HTC Rezound from 2.3.4 and then flash CounterShrike 2.3 following the Unlockr instructions. Seemed to be going well until it bootlooped at the cyanogen mod screen.
When I connect the phone to the PC and start adb, it only sees the phone in fastboot. What's my best course of action?
Try to flash the kernel off an SD card out of hboot?
Wipe the Countershrike ROM and try to flash the stock ICS?
I've followed the instructions from the developers forum to relock via fastboot, but since I can't access the phone with the adb devices command, I'm hesitant to proceed. Any advice?
Thanks.
Forgot to post the info about the phone from the Fastboot screen:
***Relocked***
Vigor PVT SHIP S-ON RL
HBOOT- 2.11.0000
RADIO- 0.95.00.118r/0.95.00.1223r
OpenDSP- v.10.6.0.7611.00.0919
eMMC-boot
Oct 6 2011, 15:43:22
purchased the phone of eBay. It was on 2.3.4, so I did a factory reset and was trying to get it rooted and on ICS before activating it.
STEP 2:
Opened command prompt from my platform tools & tried to flash AmonRa recovery via fastboot ("fastboot boot rezound-recovery.img") but received an error message:
downloading 'boot.img'...
OKAY [ 1.49s]
booting...
FAILED <remote:not allowed>
finished.total time 1.525s
can you post the link to the instructions you followed?
instructions followed
The original set of instructions I followed to root & unlock the phone were @ Unlockr.
I'm currently running through NilsP's protocol:
Latest RUU Leak and Installation Instructions
NOTE: This is only needed if you want the latest ICS Firmware (Good Idea)
Quote:
Download the 4.03.605.2 Global RUU: >> Here. MD5 = bcdd450501e390ce323a46b396cd0a49
Rename the RUU to "PH98IMG.zip". Just remove everything in the name before the PH
Copy the renamed ipdate to the root of your external SD Card.
Re-lock the bootloader. Skip this if S-OFF
Open a DOS prompt and change directory to the folder where you have fastboot.exe
Reboot to bootloader
Type "fastboot oem lock" (No Quotes) while you are in bootloader (fastboot usb).
Reboot to bootloader again via recovery menu.
The bootloader should find the PH98IMG.zip file and scan it.
Scanning will take awhile so be patient. When it prompts you say yes. The update will make the first pass. This will take awhile so just watch the progress bar on the right The phone will reboot and sit on the white HTC screen. This could be awhile so be patient and don't get nervous. When it is done it will reboot back to bootloader to run the second pass of the install. Again, this will take some time so just watch the progress bar and OK's on the list. When it is done it will say "press power to reboot" so do it. Now it will boot into the leaked Update.
Once booted skip everything in setup. If you plan to run it stock then just get it set up to your liking
Install Amon Ra recovery version 3.15 (My Preference) If hboot will show tampered at the top but that is normal
Flash my ROM using the instructions in post 1
It's alive running stock...phwew! since I bought it for my wife to replace her DINC that's acting up.:highfive:
Your issue earlier was that you were on gingerbread firmware trying to run an ICS rom. Updating to the newest RUU updated you to ICS firmware.
Sent from my GT-P1010 using Tapatalk 2
Hello,
I have a US 3G Flyer that my friend messed up while trying to root and reflash it. He asked me to revive it.
The device was stuck at the HTC logo during boot.
It must have had HC since the HBOOT is 1.11.0011. It was unlocked through HTCDev since it says UNLOCKED in the bootloader. However, it still has S-ON. The device has Revolutionary CWM 4.0.1.4 flashed as a recovery.
I tried to follow the instructions by globatron in http://forum.xda-developers.com/showthread.php?p=18508210 to downgrade to GB in order to run Revolutionary and get S-OFF.
fastboot getvar cid gives HTC__102
However, I do not have permission to read the thread that has the download links to the RRU: http://forum.xda-developers.com/showthread.php?t=1062184
So I went ahead and tried to flash DextersJB18 because it seemed from the thread http://forum.xda-developers.com/showthread.php?t=1795342 that some people flashed it sucessfully with HTCDev unlocked S-ON devices.
I downloaded the ROM zip file and gapps-jb-20121212-signed.zip, put that on the SD card, booted into CWM v4 and flashed this way:
1. Wipe factory data/reset
2. Wipe cache
3. Go into mounts and storage
4. Format /system
5. Format /data
6. Format /cache
7. Enter advanced
8. Wipe dalvik
9. Flash ROM (including wipe all) then flashed gapps
10. Booted to fastboot then "fastboot flash boot boot.img" (taken from DextersJB18.zip)
After I reboot, it never goes past the HTC logo. If I hold the power key, it shutdowns but reboots immediately. I know I go to the bootloader and say power off to prevent draining the battery.
Can someone please provide some insight into how I can get the device up and running again? Thanks. I really appreciate it.
Resolved
Well after another day of trying various things I finally got the device back up and running.
I figured out that for the HTC__102 model device I could use RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.089BU_3809.05.04.10_M_release_194964_signed.exe to downgrade to Gingerbread. I googled that and found it on a random site.
After I found the correct RUU, I was able to follow globatron's instructions in http://forum.xda-developers.com/showthread.php?p=18508210 to downgrade to stock Gingerbread. The device booted OK into Gingerbread.
I then got S-OFF with Revolutionary and upgraded to Honeycomb by running ARUWizard.exe in RUU_3G_B09.zip. The device then booted OK into Honeycomb.
I then flashed DextersJB18 and gapps-jb-20120726-signed.zip from CWM recovery. Initially I had weird issues like the keyboard crashing because I used gapps-jb-20121011-signed.zip, which is ONLY for Android Jelly Bean 4.1.2, not 4.1.1. After flashing the correct gapps, things were OK.
The device now boots into Jelly Bean! Yea!
help, cant get boot or recovery
Hi hope you can help.
I have been running my flyer rooted on stock honeycomb with no trouble. I wanted to install Dexters JB18 rom, something went wrong after the install and now i can only access hboot screens, flyer wont boot, and recovery (was cwm with no issues) just brings up htc screen with nothing else.
I have tried flashing several recovery/boot images via fastboot, without any noticable effect. I get the messages saying image is written okay from command prompt but rebooting device or attempting to enter recovery just brings me white htc screen.
I have run getvar cid and got the result htc001, but attempting to reboot using adb gives the result device not found.
this is the info on the hboot screen
****unlocked****
flyer pvt ship s-on
hboot-1.11.0011
microp-0950
radio-3822.10.08.07_m
emmc-boot
A few threads here look promising, but i cant access them to be sure or find the right links, such as finding RUU type etc altho I dont think Im that far along until i can flash and get in to a workable recovery?
---------- Post added at 12:32 PM ---------- Previous post was at 12:14 PM ----------
Hi hope you can help.
I have been running my flyer rooted on stock honeycomb with no trouble. I wanted to install Dexters JB18 rom, something went wrong after the install and now i can only access hboot screens, flyer wont boot, and recovery (was cwm with no issues) just brings up htc screen with nothing else.
I have tried flashing several recovery/boot images via fastboot, without any noticable effect. I get the messages saying image is written okay from command prompt but rebooting device or attempting to enter recovery just brings me white htc screen.
I have run getvar cid and got the result htc001, but attempting to reboot using adb gives the result device not found.
this is the info on the hboot screen
****unlocked****
flyer pvt ship s-on
hboot-1.11.0011
microp-0950
radio-3822.10.08.07_m
emmc-boot
A few threads here look promising, but i cant access them to be sure or find the right links, such as finding RUU type etc altho I dont think Im that far along until i can flash and get in to a workable recovery?
adb driver?
ok, i think my issue is with adb.
with flyer in hboot so options are
fastboot
recovery
factory reset
clear storage
simlock
image crc
when i check device manager, it is listed as ADB interface, expand that and you get 'bootloader interface'
put flyer in fastboot mode, i see
bootloader
reboot reboot bootloader
power down
and the device is gone from device manager completely.
in either mode, when in adb running command 'adb devices' i get nothing, although running commands such as 'fastboot flash boot boot.img/recovery.img i get a success message after writing. 'fastboot reboot' will successfully reboot the device but it still does not boot up or enter recovery when attempted.
am i missing an adb driver or something?
Jelly Bean 1.8 No Wifi
I did the Same like you.
The device now boots into Jelly Bean! But i dont have wirless connection. It searches for wifi but dont find nothing.What should i do?
Where to download DextersJB18?
Hi, right now it's impossible to download DextersJB18 from dev-host, do you know any mirror link? Or kindly upload your saved ROM to other cloud storage? Thanks!
Better late than never...
I have been looking for dexterjb for a while now, thought I would search for it tonight and voila! There it is at
hmm, can't post external links. I could have sworn I was able to before...
?fid=746163614322263502 after androidfilehost.com/
Hi folks, have TWRP installed, rooted, wanted to get the OTA, but can't b/c of twrp being installed.
I have the OTA d/led from at&t. Can I load the firmware.zip from that with
fastboot oem rebootRUU
and then
fastboot flash zip firmware.zip ?
( both of which are from godfirst' post here http://forum.xda-developers.com/showthread.php?t=2419699 )
and is that the 'stock recovery"?
Or is that JUST the new firmware? (as in the BIOS for the phone, to make a pc analogy.)
More info, from bootloader screen:
tampered
unlocked
m7_UL pvt ship s-on rh
hboot-1.44.0000
radio-4a.14.3250.13
opendsp-v26.120.274.0202
emmc-boot
mar 18 2013
rhousedorf1 said:
Hi folks, have TWRP installed, rooted, wanted to get the OTA, but can't b/c of twrp being installed.
I have the OTA d/led from at&t.3
Click to expand...
Click to collapse
You can't flash the firmware with unlocked bootloader (edit: unless you have s-off.)
Open the firmware.zip with 7-zip, etc. and extract recovery.img, then 'fastboot flash recovery recovery.img'. (No need to rebootRUU.)
opened it with 7z.
going to try it shortly, once i remove htc sync........ ugh.
Gets to 25% and stops. Not sure if it's hung or still going, but I've waited 18 minutes so far.
I can power it off, then boot it again, and it hangs with red triangle exclamation.
One more power off/on and I'm back in the OS with a fail message.
Are there logs placed anywhere that I can look at?
Anyone get this and get past it?
Thx in advance for any thoughts.