Hello,
Actually I was planning to update my flyer from GB -> HC or ICS (alpha) but there some problem which i thought needs to be discussed before proceding so I may not land up bricking up my device..
My bought my flyer.. with GB 2.3 3g version... at that time i didnt noticed the hboot version ... I ran revolutionary and got CWM installed then installed Flyhigh rom on it...
Now, when i was about to update to HC ... I noticed a couple of things about my HBoot...
My HBoot version is 6.10.1002 but on revolutionary website says that it supports HBoot 1.XX.XXXX ... So how come it got installed upon my device...!!
My fastboot getvar all log :
C:\android-sdk-windows\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.10.1002
(bootloader) version-baseband: 3809.05.04.10_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0850
(bootloader) version-main: 1.56.720.2
(bootloader) serialno: HT15WT401753
(bootloader) imei: 354672040795088
(bootloader) product: flyer
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG4110000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader:
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.006s
Click to expand...
Click to collapse
Neways thats not the problem but a question instead !!
Now I want to go to HC ..
Steps are here
http://forum.xda-developers.com/showthread.php?t=1358758
Understood them... BUT
Ques.1) Is my HBoot compatible with the HC update? and if yes then my HBoot will get changed
THEN...
If I need to downgrade to GB and re-gain the S-On for warrenty ...
http://forum.xda-developers.com/showpost.php?p=19339909&postcount=1
Here the HBoot but there is no version mentioned... maybe 1.XX.XXXX then
Ques.2)Where should I Find 6.10.1002 Hboot...
Need help on this please..
Thanks in advance... ( maybe i didn't confused you)
when you run revolutionary it changes your hboot to what you have currently. Revolutionary list compatability with stock hboots which it replaces. You need to run Revolutionary first prior to attempting globatrons hc update which is what you linked. When you run his update it will change your hboot again to a hc compatable s-off hboot. You can use this hboot to run ICS. My suggestion is the first thing yiou do is a nandroid of your HC setup. When you flash ICS, after you are done playing as it is not really ready to be used as a daily driver, just restore your nand back up of hc.
so, if you are s-off on gingerbread you can proceed to hc s-off update.
ohk thanks mate... so when I downgrade i will get back to stock HBoot ... right? so how would I know that what was my stock HBoot version?
first off why would you downgrade? second you need to find the stock RUU for your device. The ruu will have the appropriate hboot. If downgrading from Gingerbread s-off there is a thread that details how to go about it, and links how to figure out your stock ruu if you do not know it
Related
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
Trying to get an RUU to run to update the HTC One M7 from T-Mobile. I've tried both the 3.24 that the phone has, and the 4.xx new one from the Original Android Dev forum. Both of them fail. 3.xx when trying to verify information, and 4.xx after step 1/5 pushing boot. 4.xx gives error 171 USB issue. I've got the drivers installed, as well as ADB and Fastboot. It connects to the phone and the RUU file reboots it, but instead of going to bootloader it goes to a black screen with HTC in silver, then the RUU on the computer fails.
Any ideas what I might be doing wrong? I have fastboot/bootloader access, but can't boot past the HTC O1ne screen.
Edit: I GOT IT!!! If you're in the same spot as me, make sure to put the RUU in your ADB directory. It wasn't working for me, moved it, worked like a charm.
detox702 said:
Trying to get an RUU to run to update the HTC One M7 from T-Mobile. I've tried both the 3.24 that the phone has, and the 4.xx new one from the Original Android Dev forum. Both of them fail. 3.xx when trying to verify information, and 4.xx after step 1/5 pushing boot. 4.xx gives error 171 USB issue. I've got the drivers installed, as well as ADB and Fastboot. It connects to the phone and the RUU file reboots it, but instead of going to bootloader it goes to a black screen with HTC in silver, then the RUU on the computer fails.
Any ideas what I might be doing wrong? I have fastboot/bootloader access, but can't boot past the HTC O1ne screen.
Click to expand...
Click to collapse
Are you S-On or S-Off? Do you have stock recovery? Is your MID and CID the same as the RUU? Is your bootloader "Locked"? Do you have the stock hboot for the RUU you are trying to run? The hboot has to be the same or lower than hboot in the RUU!
majmoz said:
Are you S-On or S-Off? Do you have stock recovery? Is your MID and CID the same as the RUU? Is your bootloader "Locked"? Do you have the stock hboot for the RUU you are trying to run? The hboot has to be the same or lower than hboot in the RUU!
Click to expand...
Click to collapse
Everything is stock. The co-worker never bothered with rooting/etc. S-On. T-Mo phone using a T-Mo RUU. Locked bootloader. Pretty sure the hboot is the same as well.
detox702 said:
Everything is stock. The co-worker never bothered with rooting/etc. S-On. T-Mo phone using a T-Mo RUU. Locked bootloader. Pretty sure the hboot is the same as well.
Click to expand...
Click to collapse
Reboot to bootloader (FASTBOOT USB), then run the command: fastboot getvar all This will tell you the id information about the phone. There may be some light shed on the status of the phone.
majmoz said:
Reboot to bootloader (FASTBOOT USB), then run the command: fastboot getvar all This will tell you the id information about the phone. There may be some light shed on the status of the phone.
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4312mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
C:\adb>
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
C:\adb>[/QUOTE]
First of all please remove the serialno and imei from your original post. Nothing looks out of the order. Could the RUU be corrupt? Check the MD5 checksum just to be sure. Or download another RUU from a different site. I have used this site's RUU in the past.
majmoz said:
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
C:\adb>
Click to expand...
Click to collapse
First of all please remove the serialno and imei from your original post. Nothing looks out of the order. Could the RUU be corrupt? Check the MD5 checksum just to be sure. Or download another RUU from a different site. I have used this site's RUU in the past.[/QUOTE]
I apparently got it. Moved the file from C:\Downloads to C:\adb, ran it, success. Thanks for the pointers, though.
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.
Hey guys I tried to root my phone a while back and something happened and now its stuck on the HTC logo. I can still access bootloader alright though. This is what my phone says while in bootloader:
***TAMPERED***
***UNLOCKED***
ZARA_UL PVT SHIPS S-ON RL
HBOOT-2.22.0000
RADIO-1.26.40E.00.14
OpenDSP-v18.2.0268.0925
OS-2.14.661.3
eMMC-boot 1024MB
FEB 26 2014 12:27:49.0
how can I get out of it ?
c:\Fastboot>fastboot getvar all
< waiting for any device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: 1.26.40e.00.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.661.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid:
(bootloader) product: zara_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: 0P4E23000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4255mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Looks like you just need to try relocking the bootloader
Code:
fastboot oem lock
That will be the fastboot command you use.
MeniscusKing said:
Looks like you just need to try relocking the bootloader
Code:
fastboot oem lock
That will be the fastboot command you use.
Click to expand...
Click to collapse
I tried this maneuver to install the original ruu like indicated in this topic : http://forum.xda-developers.com/desire-601/general/collection-kitkat-ruu-t3228817 but unfortunately there's no ruu available for my version (2.14.661.3) and as my phone is S-ON I cannot downgrade or flash a different ruu.
Also I tried to restore a rom by twrp using this methode : http://forum.xda-developers.com/showpost.php?p=55220726&postcount=2 but it failed too.
Now I dunno if any custom rom for zara ul can be installed with S-ON, it seems the last hope
Nexting said:
I tried this maneuver to install the original ruu like indicated in this topic : http://forum.xda-developers.com/desire-601/general/collection-kitkat-ruu-t3228817 but unfortunately there's no ruu available for my version (2.14.661.3) and as my phone is S-ON I cannot downgrade or flash a different ruu.
Also I tried to restore a rom by twrp using this methode : http://forum.xda-developers.com/showpost.php?p=55220726&postcount=2 but it failed too.
Now I dunno if any custom rom for zara ul can be installed with S-ON, it seems the last hope
Click to expand...
Click to collapse
Have you tried installing this using TWRP?
I've used this one before just to have root and it's Zara UL
MeniscusKing said:
Have you tried installing this using TWRP?
I've used this one before just to have root and it's Zara UL
Click to expand...
Click to collapse
I finally get out of this by installing the same stock wit PhilZ Touch, although I guess the installation of STOCK_ODEX_ROOT_HTC_ZARA_UL_601_2.14.1401.86_v.1.0.1.zip before using TWRP was necessary for me
Now I got S-OFF using rumrunner and a new RUU moving to supercid :good:
Thank's for your help
Nexting said:
I tried this maneuver to install the original ruu like indicated in this topic : http://forum.xda-developers.com/desire-601/general/collection-kitkat-ruu-t3228817 but unfortunately there's no ruu available for my version (2.14.661.3) and as my phone is S-ON I cannot downgrade or flash a different ruu.
Also I tried to restore a rom by twrp using this methode : http://forum.xda-developers.com/showpost.php?p=55220726&postcount=2 but it failed too.
Now I dunno if any custom rom for zara ul can be installed with S-ON, it seems the last hope [/Q]
Have you by any chance managed to get S-OFF while your phone was bricked?
Click to expand...
Click to collapse
I need a rom 2.15.557.3 Zara_cl
hey! I need a rom 2.15.557.3 Zara_cl
But I can not find it on the internet! Can someone please upload it? My zara_cl is without OS, S-ON and I can not flash any other.