Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(bootloader) imei: **************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3909mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
bzowk said:
Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(bootloader) imei: **************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3909mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
Click to expand...
Click to collapse
The Guru Reset would put you back at stock if you so choose. You are given the option in Aroma to "root", chose that option since you are going on to flash ViperOne.
The Guru Reset should have the same firmware in Aroma check that you want the stock radio this will help in ViperOne. I believe the issue you had earlier was the result of incompatible firmware/radio.
Purple haze issue is more likely hardware, but there has been a lot of pseudo fixes.
Thanks for your reply! Just finished backup so starting on it now. Wish me luck!
OK - Already have a small question...
I started the Guru flash and went through the first couple of screens. On the "What to flash," it gives me the option to perform "Stock Recovery" and/or "Radio." I wanted to flash Radio due to my errors - but - on this screen it describes Radio as "Version 4M.27.3218.14 - Original Radio from the Stock ROM."
My phone, however, had the Radio listed as "4A.19.3263.13." Is this still ok or no? The Guru Flash I'm using is "Guru_Reset_M7_5.12.502.2_clsA"
I plan to stay at this screen for a few minutes so that hopefully I'll have a reply by then.
Thanks Again!
bzowk said:
OK - Already have a small question...
I started the Guru flash and went through the first couple of screens. On the "What to flash," it gives me the option to perform "Stock Recovery" and/or "Radio." I wanted to flash Radio due to my errors - but - on this screen it describes Radio as "Version 4M.27.3218.14 - Original Radio from the Stock ROM."
My phone, however, had the Radio listed as "4A.19.3263.13." Is this still ok or no? The Guru Flash I'm using is "Guru_Reset_M7_5.12.502.2_clsA"
I plan to stay at this screen for a few minutes so that hopefully I'll have a reply by then.
Thanks Again!
Click to expand...
Click to collapse
The radio (4A) is the older radio the newer version is 4M. Like I mentioned before you want to the new radio to try to solve your communication issues. Sorry for the late reply but I don't monitor this site.
majmoz said:
The radio (4A) is the older radio the newer version is 4M. Like I mentioned before you want to the new radio to try to solve your communication issues. Sorry for the late reply but I don't monitor this site.
Click to expand...
Click to collapse
Hey - I toitally understand. I just appreciate that you replied when you did. After reading your message, I had an idea. Perhaps the Phone app wouldn't open because the Radio was on such an old build. I went ahead and downloaded the newest compatible radio I could find - 4T.24.3218.09 from here. I booted to Recovery then applied the radio alone.
After reboot, it worked! I can now get into my Phone app! Since I've already set this build up, I think I'll leave it for now.
I learned a lot about radios today - Thanks again for your help!
bzowk said:
Hey - I toitally understand. I just appreciate that you replied when you did. After reading your message, I had an idea. Perhaps the Phone app wouldn't open because the Radio was on such an old build. I went ahead and downloaded the newest compatible radio I could find - 4T.24.3218.09 from here. I booted to Recovery then applied the radio alone.
After reboot, it worked! I can now get into my Phone app! Since I've already set this build up, I think I'll leave it for now.
I learned a lot about radios today - Thanks again for your help!
Click to expand...
Click to collapse
You are welcome, glad that you are back up and running! :good:
bzowk said:
Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(bootloader) imei: **************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3909mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
Click to expand...
Click to collapse
Theirs one big Flaw in your method DO NOT SKIP from 3.x firmware to 5.x firmware .. you'll end up in QHSUSB_DLOAD mode and that's No fun at all.
The correct way to get to the 5.x firmware is
3.x.502 RUU to 4.x.502 Firmware to 5.x.502 firmware
then the Guru reset
Related
okay,
I've unlocked the bootloader, rooted it, it's s-on and installed cm11. After less than a day, I've decided to go back to stock. Unfortunately, because cm11 is kitkat 4.4 it seems I can't even use an ruu, as they'll only go to 4.3 (which it seems i can't use because with s-on, I can't downgrade firmwares).
I've used Twrp 2.6.3.3 for recovery.
i've tried to use moonshine and rum runner, but they both fail, presumably because i've got cm11 installed. Also, when I connect to the pc, it only comes up as a media player or camera (depending on the settings in cyanogenmod), I've got debugging on and i believe everything else I should have.
In device manager, it calls itself "My HTC", yet in utorrent "HTC Aria"
When running (in cmd) "adb devices" it shows my phone, but when I do "fastboot devices" nothing comes up.
i've tried installing htc drivers, but nothing seems to change it. Some have mentioned forcing drivers but I don't know where to get the specific htc one driver.
in the bootloader this is what comes up:
hboot 1.44
m7ul pvt ship s-on rh
radio 4A.12.3750.20
open dsp v31.120.274.0617
eMMC-boot
what are my next steps/options?
damiancds said:
okay,
I've unlocked the bootloader, rooted it, it's s-on and installed cm11. After less than a day, I've decided to go back to stock. Unfortunately, because cm11 is kitkat 4.4 it seems I can't even use an ruu, as they'll only go to 4.3 (which it seems i can't use because with s-on, I can't downgrade firmwares).
I've used Twrp 2.6.3.3 for recovery.
i've tried to use moonshine and rum runner, but they both fail, presumably because i've got cm11 installed. Also, when I connect to the pc, it only comes up as a media player or camera (depending on the settings in cyanogenmod), I've got debugging on and i believe everything else I should have.
In device manager, it calls itself "My HTC", yet in utorrent "HTC Aria"
When running (in cmd) "adb devices" it shows my phone, but when I do "fastboot devices" nothing comes up.
i've tried installing htc drivers, but nothing seems to change it. Some have mentioned forcing drivers but I don't know where to get the specific htc one driver.
in the bootloader this is what comes up:
hboot 1.44
m7ul pvt ship s-on rh
radio 4A.12.3750.20
open dsp v31.120.274.0617
eMMC-boot
what are my next steps/options?
Click to expand...
Click to collapse
cm 11 did'nt update your firmware
what's your results for fastboot getvar all
run it from the bootloader screen / fastboot usb (remove your serial no and iemi)
all it says is "< waiting for device >"
this leads me to believe there's a driver error?
Sorry, I'm an idiot
C:\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.056s
damiancds said:
all it says is "< waiting for device >"
this leads me to believe there's a driver error?
Sorry, I'm an idiot
C:\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.056s
Click to expand...
Click to collapse
this is the last AT&T RUU it will update you to android 4.3 >>
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
if that link is slow you can get it directly from HTC here >>
http://www.htc.com/us/support/htc-one-att/news/
you'll have to relock your bootloader
fastboot oem lock
then run the RUU with your phone sitting at the fastboot usb screen
Worked beautifully. Thank You.
there's only two niggling things. when you pull down for your notifications, in the top right used to be settings, now it's quick tiles like cm11.
Also, in my computer, the device shows up as portable media player, where it used to just show up as htc one and an icon that looked like it. (from quick reading, it seems this is normal.)
Thanks again for all your help
damiancds said:
Worked beautifully. Thank You.
there's only two niggling things. when you pull down for your notifications, in the top right used to be settings, now it's quick tiles like cm11.
Also, in my computer, the device shows up as portable media player, where it used to just show up as htc one and an icon that looked like it. (from quick reading, it seems this is normal.)
Thanks again for all your help
Click to expand...
Click to collapse
yeah welcome to android 4.3 .. it's different, wait till you get sense 5.5 in the kitkat update
clsA said:
yeah welcome to android 4.3 .. it's different, wait till you get sense 5.5 in the kitkat update
Click to expand...
Click to collapse
I know now, a rough search turned up the same....
One last question,
I'm sticking with stock, but i want to root it, everything i've done has been unsuccessful, where before first time and it was done, I was reading the guide over here, http://forum.xda-developers.com/showthread.php?t=2273376&page=2 , and it mentions that I can't root a stock rom? that means I would need to grab one of the rooted ones then, correct? I know I've seen a link to them around here, but can't seem to find it, let alone which one I should use.
damiancds said:
I know now, a rough search turned up the same....
One last question,
I'm sticking with stock, but i want to root it, everything i've done has been unsuccessful, where before first time and it was done, I was reading the guide over here, http://forum.xda-developers.com/showthread.php?t=2273376&page=2 , and it mentions that I can't root a stock rom? that means I would need to grab one of the rooted ones then, correct? I know I've seen a link to them around here, but can't seem to find it, let alone which one I should use.
Click to expand...
Click to collapse
after running the RUU your starting from scratch
1.unlock bootloader at HTCDEV.com
2. Flash custom recovery I recommend TWRP 2.6.3.3
How to flash?
1) Download your recovery
2) Put it on your adb/fastboot folder
3) Rename it to recovery.img
4) Open a CMD/Teminal windows on adb folder
5) Put your phone in fastboot
6) Flash the recovery with the command:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
3. flash custom rom 3.17.502.3 Stock Rooted
That should do it if your Root needs updated
download and flash this same as a rom
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
i'd installed cm11 via installer but now i wanna go back to sense
i'd installed cm11 via cm installer but now i wanna go back to stock sense,sadly i couldnt find the suitable RUU for my device.Since im really new to this android system i dont have any ideas bout flashing or locking the devices,could u guys please help me out?
i'd tried turning S off with rumrunner but at the end i was struck on an error.
here are my devices details.
m7_U S on
Hboot 1.56
CID : htc__038
version : 4.20.707.7
THANKS.
After the ota update to 4.4.2, my phone will only let me make 1 or 2 calls when on 4g and then I can no longer make/receive any calls (until I remove the sim card or sometimes just resetting the radio or clearing the dialer app data then maybe I'll get another call or 2 if I'm lucky).
I'm looking for any help or suggestions. I'm stock, S-On, etc. I've already tried a hard reset... I also reflashed the ota firmware, but had no change.
I found a temporary fix by changing to "gsm only" in the *#*#4636#*#* menu. However, that resets every reboot, and I don't want to be stuck on edge forever.
I would prefer to stay stock, S-On, but I'll take any suggestions...
Thanks in advance
In case it is helpful:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4270mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
UPDATE: I have a few more details: I tried to call my phone, LTE turns off (which is normal), but it never rings then the 4g icon disappears for a minute like it crashed somehow.
Well without achieving s off you are limited to running the ruu for your device. I suggest doing that first and if that don't help you might want to look Into s off for you can flash whatever you want.
"Coming to you live from my Straight Talk LTE One"
enigma2446 said:
Well without achieving s off you are limited to running the ruu for your device. I suggest doing that first and if that don't help you might want to look Into s off for you can flash whatever you want.
"Coming to you live from my Straight Talk LTE One"
Click to expand...
Click to collapse
I ran the ruu for the 4.18.502.7, but there was no change. Do you think there is any chance that it'll work if I flash something different, or is it a hardware issue?
As far as flashing is concerned: I've only done it before on my Galaxy S2 and it was fairly easy/straight-forward. Would you say it's the same for this phone? And is it easy to return to stock when I'm ready to trade-in?
G8trBryant said:
I ran the ruu for the 4.18.502.7, but there was no change. Do you think there is any chance that it'll work if I flash something different, or is it a hardware issue?
As far as flashing is concerned: I've only done it before on my Galaxy S3 and it was fairly easy/straight-forward. Would you say it's the same for this phone? And is it easy to return to stock when I'm ready to trade-in?
Click to expand...
Click to collapse
After u run RUU you must do a Factory Reset* or phone reset from stock recovery or setting
This will reset your radios and every setting to factory state.
finanandroid said:
After u run RUU you must do a Factory Reset* or phone reset from stock recovery or setting
This will reset your radios and every setting to factory state.
Click to expand...
Click to collapse
Still no luck. I think the ruu did a complete wipe too, but I tried anyways.
I have a few more details: I tried to call my phone, LTE turns off (which is normal), but it never rings then the 4g icon disappears for a minute like it crashed somehow.
G8trBryant said:
Still no luck. I think the ruu did a complete wipe too, but I tried anyways.
I have a few more details: I tried to call my phone, LTE turns off (which is normal), but it never rings then the 4g icon disappears for a minute like it crashed somehow.
Click to expand...
Click to collapse
easy way..... get a new SIM Card*
Hey All,
To get things started I was just looking to root/rom my friends phone to get him the wifi hotspot among some other goodies associated with custom roms. I have a good amount of experience regarding flashing, rooting, command line, etc.. I change my S4 rom weekly, and have had some experience with HTC recoveries dating back to my old, old, (OLD) HTC Apache (Yeah that was windows mobile 5). More recently I've worked with a HTC EVO.
Here's where I stand with this HTC EVO 4g LTE.
I originally tried to flash a RUU that was 'one click' thinking that it would be similar to the 1-Click Root and Recovery found for Samsung Devices, I was wrong. I know now that I needed S-OFF for this particular file and well, things didnt go well. The RUU froze (guessing because of the security reasons).
So the device now only boots to the HTC Splash indefinately or I can get it into the bootloader.
In an attempt to road of recovery, I have:
Installed TWRP v2.6.1.0 - Leaving **TAMPERED**, (I suspect)
HTCDev unlocked - Leaving **UNLOCKED**
I'd be happy to just get this thing to boot stock rom, from there I think I can S-OFF and get a custom rom on. But one step at at time.
I've tried running RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.17.651.4_Radio_1.13.11.0830_NV_3.02_003_PRL25007_release_334470_signed.zip as an attempt to recover stock, I've read reports that I might need to relock the phone to get this to work. Is this true?
I've read and read and read and tried and tried to no avail, just looking for a little pointer to get me in the right direction.
Included is my fastboot getvar all:
Code:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.10.0000
(bootloader) version-baseband: 1.13.11.0830
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.651.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT27FS401770
(bootloader) imei: 990000667854337
(bootloader) product: jewel
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ7510000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b28ce9b8
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you so much in advance for any advice or guidance.
ragnsep said:
Hey All,
To get things started I was just looking to root/rom my friends phone to get him the wifi hotspot among some other goodies associated with custom roms. I have a good amount of experience regarding flashing, rooting, command line, etc.. I change my S4 rom weekly, and have had some experience with HTC recoveries dating back to my old, old, (OLD) HTC Apache (Yeah that was windows mobile 5). More recently I've worked with a HTC EVO.
Here's where I stand with this HTC EVO 4g LTE.
I originally tried to flash a RUU that was 'one click' thinking that it would be similar to the 1-Click Root and Recovery found for Samsung Devices, I was wrong. I know now that I needed S-OFF for this particular file and well, things didnt go well. The RUU froze (guessing because of the security reasons).
So the device now only boots to the HTC Splash indefinately or I can get it into the bootloader.
In an attempt to road of recovery, I have:
Installed TWRP v2.6.1.0 - Leaving **TAMPERED**, (I suspect)
HTCDev unlocked - Leaving **UNLOCKED**
I'd be happy to just get this thing to boot stock rom, from there I think I can S-OFF and get a custom rom on. But one step at at time.
I've tried running RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.17.651.4_Radio_1.13.11.0830_NV_3.02_003_PRL25007_release_334470_signed.zip as an attempt to recover stock, I've read reports that I might need to relock the phone to get this to work. Is this true?
I've read and read and read and tried and tried to no avail, just looking for a little pointer to get me in the right direction.
Included is my fastboot getvar all:
Code:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.10.0000
(bootloader) version-baseband: 1.13.11.0830
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.651.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT27FS401770
(bootloader) imei: 990000667854337
(bootloader) product: jewel
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ7510000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b28ce9b8
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you so much in advance for any advice or guidance.
Click to expand...
Click to collapse
Yes, relock the bootloader and try the official RUU again. fastboot oem lock.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I get [Error 158] IMAGE ERROR after **RELOCKING** the bootloader. Do I need any firmware zips on my sdcard renamed to P175xxx or whatever is specified for other RUUs?
ragnsep said:
I get [Error 158] IMAGE ERROR after **RELOCKING** the bootloader. Do I need any firmware zips on my sdcard renamed to P175xxx or whatever is specified for other RUUs?
Click to expand...
Click to collapse
Try running the RUU found here:
http://forum.xda-developers.com/showthread.php?t=2653730
Bottom of the first post, is the most recent HTC RUU.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Evolution_Freak said:
Try running the RUU found here:
http://forum.xda-developers.com/showthread.php?t=2653730
Bottom of the first post, is the most recent HTC RUU.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, I noticed this is a different image version...
Out of curiosity, was the partition table on this RUU very different from the previous one? And was that the issue?
ragnsep said:
Thanks, I noticed this is a different image version...
Out of curiosity, was the partition table on this RUU very different from the previous one? And was that the issue?
Click to expand...
Click to collapse
This one has the partition set up the way it should have been from the start. More space internal for apps and such. Did it work?
Sent from my EVO using XDA Premium 4 mobile app
Have you tried flashing a custom recovery then flashing a sense Rom (you're on 3.17 so anything based on that or 3.16 will be compatible with the version your log says you're on)? If that works then at least you can go for s off before trying anything else.
Sent from my 831C using xda app-developers app
I recently found out that the only way to obtain S-Off now is to pay $25. Before I do this I'm curious to know if I even need to do that before I flash a ROM. I'm already rooted. Can't I just load the ROM onto my phone, go into recovery and flash from their? Do I really need to pay the $25?
sock00 said:
I recently found out that the only way to obtain S-Off now is to pay $25. Before I do this I'm curious to know if I even need to do that before I flash a ROM. I'm already rooted. Can't I just load the ROM onto my phone, go into recovery and flash from their? Do I really need to pay the $25?
Click to expand...
Click to collapse
You dont have to pay to obtain S-Off unless youre already on 4.4.3 in which case you'd need sunshine, just read around the forum and you can figure out how to with firewater. Its not hard you just have to do a little research. But to answer the question, yes you have to be S-Off to install custom ROMs. Here is a link to firewater http://forum.xda-developers.com/showthread.php?t=2708464
S-ON and Custom ROM's
CavyS said:
You dont have to pay to obtain S-Off unless youre already on 4.4.3 in which case you'd need sunshine, just read around the forum and you can figure out how to with firewater. Its not hard you just have to do a little research. But to answer the question, yes you have to be S-Off to install custom ROMs. Here is a link to firewater http://forum.xda-developers.com/showthread.php?t=2708464
Click to expand...
Click to collapse
I'm new to modding, and definitely still learning but am unclear on your above statement, I have HTC One (M8) 2014. Rooted SuperSu running Android Revolution HD 8.1 custom ROM. It seems I am S-ON because I am not able to flash my hboot (to remove red development text). I receive FAILED (remote: 99 unknown fail). Based on what I'm reading I am S-ON and running a custom ROM. AR HD 8.1 is based on kitkat 4.4.2. Joined today and searching for more answers. Thanks and Cheers!
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
shadowsports said:
I'm new to modding, and definitely still learning but am unclear on your above statement, I have HTC One (M8) 2014. Rooted SuperSu running Android Revolution HD 8.1 custom ROM. It seems I am S-ON because I am not able to flash my hboot (to remove red development text). I receive FAILED (remote: 99 unknown fail). Based on what I'm reading I am S-ON and running a custom ROM. AR HD 8.1 is based on kitkat 4.4.2. Joined today and searching for more answers. Thanks and Cheers!
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Click to expand...
Click to collapse
You have to be S-Off to flash hboot. Also make sure your modid and cid match up to the hboot you are flashing.
CavyS said:
You have to be S-Off to flash hboot. Also make sure your modid and cid match up to the hboot you are flashing.
Click to expand...
Click to collapse
My mod and cid both match. My issue is indeed my S-ON status. My comment was in regards to your statement that you must be S-OFF to flash custom ROMs which does not appear to be true.
I unlocked my device using HTCdev unlock. I'm still running stock FW which is why (I believe) I am S-ON. I thought unlocking my device would provide S-OFF but that does not appear to be the case as "get var" tells the story. Thanks for the reply.
shadowsports said:
My mod and cid both match. My issue is indeed my S-ON status. My comment was in regards to your statement that you must be S-OFF to flash custom ROMs which does not appear to be true.
I unlocked my device using HTCdev unlock. I'm still running stock FW which is why (I believe) I am S-ON. I thought unlocking my device would provide S-OFF but that does not appear to be the case as "get var" tells the story. Thanks for the reply.
Click to expand...
Click to collapse
Ah, yeah I was wrong in that case. I though I read while flashing VenomOne that you had to be S-Off to use it. Now that I look at it though, its only certain ROMs you have to S-Off for since when you flash VenomOne it also flashes HBoot.
CavyS said:
Now that I look at it though, its only certain ROMs you have to S-Off for since when you flash VenomOne it also flashes HBoot.
Click to expand...
Click to collapse
You sure about that? It would be highly unusual (and actually a little scary) for any ROM to touch hboot. I don't follow ViperOne closely (Venom is the team, Viper is the ROM) so maybe I'm missing something. Can you link where you see that ViperOne does something to hboot?
---------- Post added at 10:01 AM ---------- Previous post was at 09:54 AM ----------
shadowsports said:
I unlocked my device using HTCdev unlock. I'm still running stock FW which is why (I believe) I am S-ON. I thought unlocking my device would provide S-OFF but that does not appear to be the case as "get var" tells the story.
Click to expand...
Click to collapse
Bootloader unlock has nothing to do with s-off. They are completely different things. Bootloader unlock allows install of custom recovery, flashing ROMs, kernels, root, and some other things.
S-off is needed to modify hboot, radio, and some other partitions. It means "all security off" so in many cases it also bypasses bootloader unlock, and other checks. You need to either use firewater or sunshine methods to get s-off. Most likely sunshine, as most folks have not had success with firewater; except mostly on older M8's (where fireware still worked fine). Although there have been some isolated cases of newer devices working with firewater, which is free so its worth a try (and it takes about 5 or 10 minutes to try if you are already rooted and have adb setup).
You don't need s-off to flash custom ROMs. Meaning the ROMs will still flash fine. But there is a slight caveat, in that if you are on old firmware (hboot, radio, plus other modules like WiFi, Bluetooth, media and others) from 1.xx based OS software, and try to use a 2.xx based ROM, they will not play together well and you will suffer some serious issues including long boot times (5-10 min), or broken WiFi or Bluetooth.
So while a 2.xx ROM will flash fine with s-on (in literal terms), you most likely will get some issues (maybe even making the ROM not usable) unless you update the firmware (which does require s-off).
You can update the firmware either by "unofficial" means with s-off and flashing an updated firmware. Or you with s-on, you can install the 2.23 AT&T OTA or RUU.
I have an AT&T HTC One M8 (US) and am having some issues. So I was running Android Revolution 39.0 (I think) for about a year and decided to just to do a full fresh install of Android Revolution 43.0. This flashed and booted fine, but my wifi wasn't working, so I realized that I needed to update the firmware as well. I did some reading and it seemed that for an S-ON phone, I just needed to find a firmware that matched my modelid and cidnum and then I wouldn't have to worry about changing to S-OFF. I ended up flashing firmware with version 3.11.1700.5 because its info matched my phone (I now know that this firmware is meant for GPE). I then reflashed Android Revolution 43.0 because I read somewhere that I would need to do that after a firmware flash. Now when I reboot my phone, it shows the white HTC boot screen for about 30 seconds, reboots, shows the boot screen again for about 5 seconds, and then boots straight into recovery.
Here is the getvars all output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT445WM02341
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any ideas?
Find the ATT RUU floating around here, make sure to follow directions on what needs to be done.
http://forum.xda-developers.com/att-htc-one-m8/general/lollipop-ota-twrp-backup-firmware-t3075835
hack14u said:
Find the ATT RUU floating around here, make sure to follow directions on what needs to be done.
http://forum.xda-developers.com/att-htc-one-m8/general/lollipop-ota-twrp-backup-firmware-t3075835
Click to expand...
Click to collapse
I had tried this many times before, but I guess I just hadn't found the correct firmware yet. I followed this link found on the post you linked to and downloaded the Lollipop firmware and it worked. I then just used the RUU from HTC's website and all is well. Thanks!
poozer42zer said:
I have an AT&T HTC One M8 (US) and am having some issues. So I was running Android Revolution 39.0 (I think) for about a year and decided to just to do a full fresh install of Android Revolution 43.0. This flashed and booted fine, but my wifi wasn't working, so I realized that I needed to update the firmware as well. I did some reading and it seemed that for an S-ON phone, I just needed to find a firmware that matched my modelid and cidnum and then I wouldn't have to worry about changing to S-OFF. I ended up flashing firmware with version 3.11.1700.5 because its info matched my phone (I now know that this firmware is meant for GPE).
Click to expand...
Click to collapse
I know you sorted it out. But to clarify: You needed Lollipop firmware to support a LP based ROM. You flashed a 3.xx firmware, which is not Lollipop, its Kitkat (Android 4.4.4).
Further, the GPE version does not have the same CID and MID as the ATT version. So it shouldn't have flashed, especially with s-on. Therefore, I'm questioning whether the firmware even flashed properly or not (even though it shows the GPE firmware number in main version in your getvar output).