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
Related
Okay! SOoooo Im going to apolagize if this is the wrong sport for this! I couldnt quite find a spot that hit everything i was trying to figure out!
SO heres the deal, was looking to upgade my phone! Found an HTC one on ebay SUPER cheap guy selling it tried to root it and got it stuck in a boot cycle..... Easy enough to fix right?! *or so it would have been on a Samsung! thats what im used to working with*
so i get the phone and play a little bit, I load into the bootloader and do a factory reset! the phone restarted and went right to the main set up page! as soon as i get to the end it says Unfortunatly Set up has stopped. *UGH* still im thinking super easy to fix! Just gotta flash Stock rom! so i head in that direction everything im finding says need to S-off the phone. so i start researching! ThinI started with the boot loader, got it unlocked *thats what all the post were saying to do* then went to move on to S-off, heres where it gets messy.... long story short..... the program freaks out gives me some error then starts in to loading CWM and then everything just crashes! Phone, Computer..... everything!
I get the phone back into boot mode, NOW it sats Tampered on the top, I cant get back to the set, Recovery doent work, factory reset doent work..... again long story short after researching it turns out i wiped EVERYTHING.
I can still get to the phone VIA command promts, I can get it to load in to the black HTC screen hell i can even relock and unlock the phone..... But I think where the issue is, the phone is still S-on..... when following all the step to fix this I cant get the ADB to see that my device is connected I can- But i can acces it through other commands..... Hopefully I havent lost everyone!!
Please tell me im not completely screwed....
Post fastboot getvar all - minus your imei and serial no
Sent from my HTC One_M8 using Tapatalk
clsA said:
Post fastboot getvar all - minus your imei and serial no
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Sorry, while im not a complete noob with this stuff im still learning. what do you want me to do?
clsA said:
Post fastboot getvar all - minus your imei and serial no
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Never mind! figured it out haha
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(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: 4248mV
(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.060s
GNote4Ever said:
Never mind! figured it out haha
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(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: 4248mV
(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.060s
Click to expand...
Click to collapse
You can run a RUU to get you phone working
lock the bootloader
fastboot oem lock
then run this RUU to get up to android 4.3
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
if you having problems with your drivers install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
clsA said:
You can run a RUU to get you phone working
lock the bootloader
fastboot oem lock
then run this RUU to get up to android 4.3
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
if you having problems with your drivers install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
Click to expand...
Click to collapse
The RUU wont work in this case. I did as you said*just to be sure.* But the RUU can cacess the phone in boot mode and because the phone get stuck on the "HTC quietly brilliant" screen its not loaded far enough to engage the USB connection. All I get is USB Connection Error when running the RUU
clsA said:
You can run a RUU to get you phone working
lock the bootloader
fastboot oem lock
then run this RUU to get up to android 4.3
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
if you having problems with your drivers install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
Click to expand...
Click to collapse
think I got it. Loaded to the Black HTC screen using fastboot oem rebootRUU- then ran the RUU it is "updating boot" as we speak.
GNote4Ever said:
think I got it. Loaded to the Black HTC screen using fastboot oem rebootRUU- then ran the RUU it is "updating boot" as we speak.
Click to expand...
Click to collapse
Next time, an easier method would be to flash a custom recovery (fastboot flash recovery *recovery of your choice*) and then install a new ROM. You put the ROM on an external USB and flash it, or you can ADB push the ROM into the phone.
When running S-Off (rumrunner or firewater) I recommend to always run it from a stock ROM.
So if I get these drivers, and my computer WILL NOT recognize my device, how am I supposed to reapply them to the phone?
I just need to get the drivers back on my phone so I can work on the recovery. I'll probably have more questions about that later.. lol
Hey guys,
My HTC One(ATT) is stuck in the HTC One logo screen. This happened earlier as well but fixed it through RUU. Since then i got upgrade from at&t to the latest 5.12.502.2 with Sense 6.
Tried with the earlier RUU but didnt work. So i am looking for RUU for the latest att update.
Can you please help me with this !!!
Thanks!!!
diganthshah said:
Hey guys,
My HTC One(ATT) is stuck in the HTC One logo screen. This happened earlier as well but fixed it through RUU. Since then i got upgrade from at&t to the latest 5.12.502.2 with Sense 6.
Tried with the earlier RUU but didnt work. So i am looking for RUU for the latest att update.
Can you please help me with this !!!
Thanks!!!
Click to expand...
Click to collapse
I haven't seen an RUU for 5.12.502.2 available anywhere yet. The last official RUU from AT&T was 3.17.502.3. The 4.18.502.7 RUU that's floating around apparently wasn't an official release and many people were having problems with it. If you are S-Off, use the 3.14.502.3 RUU then you can OTA up to the latest version.
sharksfan7 said:
I haven't seen an RUU for 5.12.502.2 available anywhere yet. The last official RUU from AT&T was 3.17.502.3. The 4.18.502.7 RUU that's floating around apparently wasn't an official release and many people were having problems with it. If you are S-Off, use the 3.14.502.3 RUU then you can OTA up to the latest version.
Click to expand...
Click to collapse
I will give the official one a shot and see if it works.. will update the results soon..
sharksfan7 said:
I haven't seen an RUU for 5.12.502.2 available anywhere yet. The last official RUU from AT&T was 3.17.502.3. The 4.18.502.7 RUU that's floating around apparently wasn't an official release and many people were having problems with it. If you are S-Off, use the 3.14.502.3 RUU then you can OTA up to the latest version.
Click to expand...
Click to collapse
I tried 3.17.502.3 .. doesn't work..
Below is the info of my device.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502&2
(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: 4226mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I am not sure if this doesnt work as it is S-ON.
Original issue was "STUCK AT HTC ONE LOGO SCREEN" .. how can i proceed next ??
Thanks!!
First off. Edit your post above and remove the serial# & imei.
The RUU isn't working b/c you're S-On and on an HBOOT higher than the one in the RUU. You need to be S-OFF to downgrade. Your bootloader is locked as well. Have you ever unlocked the bootloader and flashed a custom recovery? If not, I guess the next thing to try is to do a factory reset from HBOOT. You'll lose all your data but I don't think there is a way around that at this point. But since you were trying to run the RUU I guess you've already resigned yourself to that.
Another route to take is to unlock your bootloader, flash a custom recovery, then a custom ROM.
You might want to wait for other people to chime in. Perhaps they'll have other ideas.
diganthshah said:
I tried 3.17.502.3 .. doesn't work..
Below is the info of my device.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(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
I am not sure if this doesnt work as it is S-ON.
Original issue was "STUCK AT HTC ONE LOGO SCREEN" .. how can i proceed next ??
Thanks!!
Click to expand...
Click to collapse
I just saw this are you still stuck ?
The easy answer is to unlock the bootloader and flash TWRP 2.6.3.3 and flash my Guru_ reset being your already on the current firmware.
If you don't want to flash the recovery again after the reset just choose no to installing stock recovery and radio and Yes to Root
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload the Rom to your phone
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
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.
Hi all,
I have refrained from posting because I thought I would just read, but now I'm at the end of my rope. I just got my ATT htc one m8. I am on T-Mobile, but the price was right for this one.
Anyway I converted my phone right out of the box literally to GPE. I also used sunshine to unlock, and s-off. Both of these seemed to go off with little trouble.
BTW: ADB fastboot, drivers and such are installed correctly.
Things were fine, so I decided to play around some more. I preceded to revert back to sense so, I could play with more roms.
Needless to say I have done a lot of trial and error, so I will tell you what's going on now. Hopefully I didn't brick anything, and hopefully it's an easy fix.
I am s-off
Here is a Getvar all. My phone is no longer seen by adb, so commands do nothing I got this read out by using the toolkit, but prefer manual.
Also I have absolutely no ROM installed so I can not enable debugging mode, I cant do anything. Is there an easy way to re-unlock the boot loader? I don't want to go through htcdev seeing as I went with sunshine.
Sorry if this is noob, but I have struggled for like the last 20 hours trying to figure this out on my own.
Bootloader says relocked (relocked due to trying to go back)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43SWM04814
(bootloader) imei: 358718050247696
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.015s
>
This should be in Q&A thread....
TireIron431 said:
Here is a Getvar all. My phone is no longer seen by adb, so commands do nothing I got this read out by using the toolkit, but prefer manual.
Also I have absolutely no ROM installed so I can not enable debugging mode, I cant do anything. Is there an easy way to re-unlock the boot loader? I don't want to go through htcdev seeing as I went with sunshine.
>
Click to expand...
Click to collapse
fastboot oem unlock
Sorry I messed up. If you just updated your firmware, then you will need to get new token from HTCdev. The /fastboot oem unlock/ only works with GPE hboot. My guess is that each hboot version comes with different unlocktoken. I just updated my firmware and had to grab a new unlock token as well (coming back from GPE).
:fingers-crossed:
TireIron431 said:
Hi all,
I have refrained from posting because I thought I would just read, but now I'm at the end of my rope. I just got my ATT htc one m8. I am on T-Mobile, but the price was right for this one.
Anyway I converted my phone right out of the box literally to GPE. I also used sunshine to unlock, and s-off. Both of these seemed to go off with little trouble.
BTW: ADB fastboot, drivers and such are installed correctly.
Things were fine, so I decided to play around some more. I preceded to revert back to sense so, I could play with more roms.
Needless to say I have done a lot of trial and error, so I will tell you what's going on now. Hopefully I didn't brick anything, and hopefully it's an easy fix.
I am s-off
Here is a Getvar all. My phone is no longer seen by adb, so commands do nothing I got this read out by using the toolkit, but prefer manual.
Also I have absolutely no ROM installed so I can not enable debugging mode, I cant do anything. Is there an easy way to re-unlock the boot loader? I don't want to go through htcdev seeing as I went with sunshine.
Sorry if this is noob, but I have struggled for like the last 20 hours trying to figure this out on my own.
Bootloader says relocked (relocked due to trying to go back)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43SWM04814
(bootloader) imei: 358718050247696
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.015s
>
Click to expand...
Click to collapse
I can help you with this...don't try anything else to your phone you will just make it harder to fix. question how did you try to convert back I need to know what all u did?
I don't remember everything I don't think.. All I did was chamge the cid a few times. I tried to install stock recoveries, I tried install anything I could. Everything seemed to fail. After I changed the cid to stock the pc stopped seeing it from what I remember. Right now all I know is that these is no recovery on it, so no twrp, and no os...and I cant get the pc to see it. I will try to get it recognized by the pc but that's all til I hear back.
abd will not work in fastboot environment. As long as your phone says "Fastboot USB connected," you are still good to go. You must grab a new unlock token from htcdev and then proceed, because it seems that each new hboot has new unlock token. Otherwise you could unlock bootloader the S-off way, which I am not aware of (my phone is S-on) :fingers-crossed:
TireIron431 said:
I don't remember everything I don't think.. All I did was chamge the cid a few times. I tried to install stock recoveries, I tried install anything I could. Everything seemed to fail. After I changed the cid to stock the pc stopped seeing it from what I remember. Right now all I know is that these is no recovery on it, so no twrp, and no os...and I cant get the pc to see it. I will try to get it recognized by the pc but that's all til I hear back.
Click to expand...
Click to collapse
I have s-off through sunshine, do I have to go through htc, or is there a way to do it again with sunshine? My phone still says fastboot usb, but commands don't work.
TireIron431 said:
I have s-off through sunshine, do I have to go through htc, or is there a way to do it again with sunshine? My phone still says fastboot usb, but commands don't work.
Click to expand...
Click to collapse
You got sdcard an can boot to bootloader rt ? If so we will install twrp like that first off
Yes I have sd card, and am at the fastboot usb screen
TireIron431 said:
Yes I have sd card, and am at the fastboot usb screen
Click to expand...
Click to collapse
Perfect. Hit me up on hangouts I should be able to get u up an running might be a very a long process. Did one last night took 4 hours. But dude is up an running. I'm going to pm you my hangouts email now.
Got it all sorted out thanks to Tigerstown. Man that was a mess lol. I appreciate the assist.
Now to try some not so stupid things. lol
TireIron431 said:
Got it all sorted out thanks to Tigerstown. Man that was a mess lol. I appreciate the assist.
Now to try some not so stupid things. lol
Click to expand...
Click to collapse
Just glad to help an glad your phone is backing in working order
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).