how do i discover the ruu i need somehoiw i lost my OS and can only load into bootloader now so how do i find out the ruu to fix this
plook11 said:
how do i discover the ruu i need somehoiw i lost my OS and can only load into bootloader now so how do i find out the ruu to fix this
Click to expand...
Click to collapse
branded with rogers
im located in canada
original os was 4.2.2 if im not mistaken
Bootloader unlocked? S-Off?
Load fastboot and give us the output of
Code:
fastboot oem getvar all
mrplowdan said:
Bootloader unlocked? S-Off?
Load fastboot and give us the output of
Code:
fastboot oem getvar all
Click to expand...
Click to collapse
Tampored
relocked
securitywarning
zara ul pvt ship s on rl
hboot 2.22.0000
radio 1.26.40e.00.14
opendsp v18.2
os 2.14.631.3
eMMCboot 1024mb
and when i run that code i receive
Code:
C:\Users\Curtis\Desktop\hack dat phone\platform-tools>fastboot devices
HT3AJWK01609 fastboot
C:\Users\Curtis Spence\Desktop\hack dat phone\platform-tools>fastboot oem getvar
all
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.019s
C:\Users\Curtis\Desktop\hack dat phone\platform-tools>
i lost my OS somehow i think becuase i cannot boot normaly only to fastboot and bootloader and all options return me to them
my bad, the command should have been
Code:
fastboot getvar all
You're going to have to unlock your bootloader again unless you already have twrp installed. Flash the kitkat twrp recovery, then you can restore the telus 4.4.2 twrp backup in my sig or flash the insertcoin rom.
You won't be able to use the Telus RUU unless you're s-off since you'll need to change your mid to match telus's as well and downgrade your hboot
mrplowdan said:
my bad, the command should have been
Code:
fastboot getvar all
You're going to have to unlock your bootloader again unless you already have twrp installed. Flash the kitkat twrp recovery, then you can restore the telus 4.4.2 twrp backup in my sig or flash the insertcoin rom.
You won't be able to use the Telus RUU unless you're s-off since you'll need to change your mid to match telus's as well and downgrade your hboot
Click to expand...
Click to collapse
ok well with the new code i get this
Code:
< waiting for 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.631.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3AJWK01609
(bootloader) imei: 357601050043342
(bootloader) meid:
(bootloader) product: zara_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: 0P4E20000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(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!
finished. total time: 0.168s
yup, looks good, you were updated to kitkat so my twrp kk backup should work. If you want back to complete stock (telus) you'll need to s-off once you get the phone working again. Don't worry the telus radio is exactly the same as the rogers one.
mrplowdan said:
yup, looks good, you were updated to kitkat so my twrp kk backup should work. If you want back to complete stock (telus) you'll need to s-off once you get the phone working again. Don't worry the telus radio is exactly the same as the rogers one.
Click to expand...
Click to collapse
ok so what file exactly from yours do i need and im actualy after unlocking my phone to virgin mobile if possible and s off is the reason my phone keeps relockign becuase i try the aahk
plook11 said:
ok so what file exactly from yours do i need and im actualy after unlocking my phone to virgin mobile if possible and s off is the reason my phone keeps relockign becuase i try the aahk
Click to expand...
Click to collapse
You need to unlock your bootloader, which is unrelated to unlocking your network for virgin. Your HBoot says your relocked so its been unlocked before so I'm assuming you know how to use htcdev.com to do it
Then flash TWRP recovery for kitkat
http://forum.xda-developers.com/des...recovery-twrp-2-7-1-0-touch-recovery-t2804520
Then flash InsertCoin rom from here
http://forum.xda-developers.com/des...-2-7-1-0-touch-recovery-t2804520/post54488916
mrplowdan said:
You need to unlock your bootloader, which is unrelated to unlocking your network for virgin. Your HBoot says your relocked so its been unlocked before so I'm assuming you know how to use htcdev.com to do it
Then flash TWRP recovery for kitkat
http://forum.xda-developers.com/des...recovery-twrp-2-7-1-0-touch-recovery-t2804520
Then flash InsertCoin rom from here
http://forum.xda-developers.com/des...-2-7-1-0-touch-recovery-t2804520/post54488916
Click to expand...
Click to collapse
ok i unlocked and flashed openrecovery-twrp-2.7.1.1-zaracl.img but i dont see the insertcoin rom on that link and after i do find it and do it what will i do
plook11 said:
ok i unlocked and flashed openrecovery-twrp-2.7.1.1-zaracl.img but i dont see the insertcoin rom on that link and after i do find it and do it what will i do
Click to expand...
Click to collapse
oops heres the link
http://forum.xda-developers.com/des...om-insertcoin-3-0-6-zaraul-m7-port-5-t2819869
just download the UL version and the dialer fix, flash both from twrp's install zip function
mrplowdan said:
oops heres the link
http://forum.xda-developers.com/des...om-insertcoin-3-0-6-zaraul-m7-port-5-t2819869
just download the UL version and the dialer fix, flash both from twrp's install zip function
Click to expand...
Click to collapse
so i need to place them both on my sd card in that case?
yup
mrplowdan said:
yup
Click to expand...
Click to collapse
ok i have to step out for a while but when i get bakc i will do that and with that done will this phone once again be bootable? and what would my next step be towards the end goal of disabling the carrier lock
plook11 said:
ok i have to step out for a while but when i get bakc i will do that and with that done will this phone once again be bootable?
Click to expand...
Click to collapse
Yup
plook11 said:
and what would my next step be towards the end goal of disabling the carrier lock
Click to expand...
Click to collapse
As far as I know there is no known way to network unlock for free on our phones. You may be able to call Rogers and request an unlock code but I'm not sure of their policies, call them up and ask. I ended up using cellunlocker.net to unlock it for $15
mrplowdan said:
Yup
As far as I know there is no known way to network unlock for free on our phones. You may be able to call Rogers and request an unlock code but I'm not sure of their policies, call them up and ask. I ended up using cellunlocker.net to unlock it for $15
Click to expand...
Click to collapse
ok ill use cell unlocker becuase i called rogers originaly and they wanted $50 thats how i ended up here
$50?! what are they smoking?
mrplowdan said:
$50?! what are they smoking?
Click to expand...
Click to collapse
its crazy i know and now i tried the files but e unable to mount i had this before but forget how i fixed it any ideas?
mrplowdan said:
$50?! what are they smoking?
Click to expand...
Click to collapse
ok i finished the rooting of it but on boot it boots as a htc one but does load except atm it loads to a screen with background image but nothing else is there
mrplowdan said:
$50?! what are they smoking?
Click to expand...
Click to collapse
i must of taen the wrong file
Related
LOOKS LIKE S-OFF FOR 1.54 HAS HAPPENED. NO NEED TO DOWNGRADE CHECK THE POST HERE
MODS Lock This One Up!!!
I was about to give up on s-off since I got the OTA update but there is hope.
I got s-off doing the following:
1.) Unlock your device via HTCDev
2.) Download and flash CWM Recovery
3.) Flash the stock nandroid for your phone...
a. TWRP Nandroid AT&T Thanks JEANRIVERA
b. TWRP Nandroid AT&T Thanks JEANRIVERA
c. TWRP Nandroid AT&T Thanks cschmitt​If any one has other links to other devices let me know... I think this will work on all of the variants.:laugh:
Please note that this nandroid was made with TWRP and may need to be restored with TWRP.
On a side note... The original nandroid that I had linked was also created with TWRP and as I was unable to locate the restore function in my TWRP I did restore with CWM.
4.) then relock your device
Code:
fastboot oem lock
5.) grab 1847-ruu-m7-ul-jb-50-cingular-12650212.exe here and run it... Thanks cschmitt
6.) goto the tutorial here... and follow the directions...
This has worked for me... and I hope this will help someone else. All the information came from other people, I just happened to put it in the right order.
If this did not work for you there are New instructions here... Thanks domohan
IT IS IMPORTANT TO DO ALL THE STEPS IN ORDER...
I take no responsibility for anything you do with this information.
If I forgot to mention your name specifically... I'm Sorry and Thanks!
If I helped you hit the thank you button.
I see, new hboot. Downgrading it is then. Interesting that they haven't forced htc to shut off the unlocking service.
worked as advertised
Thanks a lot. A process for sure but worked for me following the ATT OTA update to .15. Although, I went on to follow the guide at wonderhowto dot com for installing the ASOP Google Edition. Thanks again.
Yeah that was the update that got me ... I am really glad that it worked for someone else... :laugh:
I am having trouble flashing the nandroid. I have tried to both flash the zip as well as unpack it and try to do a restore. Any thoughts?
---------- Post added at 06:33 PM ---------- Previous post was at 05:38 PM ----------
Ok, I actually flashed this one http://forum.xda-developers.com/showthread.php?t=2252959
Then ran the .12 RUU and am now S-OFF. Thanks for this!
well i am glad you got that working... The way i did the nandroid was by extracting the zip to clockworkmod\backups ... then choosing restore... I had TWRP but could not find the restore Nandroid option.
The only way I see this actually working is that the RUU just checks the HBOOT version, and not the build date. Otherwise, the .12 RUU would fail to install because the OTA HBOOT has a newer build date.
If this is true, then all AT&T users better get S-OFF now (if they know what S-OFF does). I have a feeling the 4.2.2 update will come out with a newer HBOOT with a higher number. Then surely, any 4.1.2 RUU will not work.
In any case, it seems to be working for those of us who weren't paying attention and downloaded the OTA... But the message is still S-OFF now while you can, 'cause they will patch the thing eventually.
I was getting Error = -6 codes and this method worked perfectly for me! Thanks so much!
This did not work for my situation...
I had S-OFF, set my CID to 11111111 and installed the latest GE rom. I decided to go back to stock, and made the mistake of S locking without knowing that I could not go back on HBOOT 1.54. Now I'm S-ON with CID 11111111, HBOOT 1.54 and Radio 4A.18
I tried this fix... I get stuck on the RUU, it show sending... but after about 5min it errors out...
Is there any hope for my situation?
This was what in my RUU log...
<T171817><DEBUG><OUT>sending 'zip'... (1029872 KB) FAILED (data transfer failure (Too many links))</OUT>
i used this and it worked flawlessly for me, great looking out man. im now s-off with tampered removed
TabascoJoe said:
This did not work for my situation...
I had S-OFF, set my CID to 11111111 and installed the latest GE rom. I decided to go back to stock, and made the mistake of S locking without knowing that I could not go back on HBOOT 1.54. Now I'm S-ON with CID 11111111, HBOOT 1.54 and Radio 4A.18
I tried this fix... I get stuck on the RUU, it show sending... but after about 5min it errors out...
Is there any hope for my situation?
This was what in my RUU log...
<T171817><DEBUG><OUT>sending 'zip'... (1029872 KB) FAILED (data transfer failure (Too many links))</OUT>
Click to expand...
Click to collapse
I'm not totally sure...
1.) do you have unlock from htcdev?
2.) can you flash a recovery?
a. if so there is hope to get back to at least a working phone till a new exploit for 1.54 is found.
b. Are you sure you re-locked your phone...
Code:
fastboot oem lock
c. SUPER CID - (allows you to flash ANY ROM to the device regardless of the carrier. Just click RUU.EXE) So make sure the phone is locked and flash an older RUU. Then revone and you should be good to go my friend.
let me know if this works!
...and remember to hit the thank you button!
INeFFeCTiVE said:
I'm not totally sure...
1.) do you have unlock from htcdev?
2.) can you flash a recovery?
a. if so there is hope to get back to at least a working phone till a new exploit for 1.54 is found.
b. Are you sure you re-locked your phone...
Code:
fastboot oem lock
c. SUPER CID - (allows you to flash ANY ROM to the device regardless of the carrier. Just click RUU.EXE) So make sure the phone is locked and flash an older RUU. Then revone and you should be good to go my friend.
let me know if this works!
...and remember to hit the thank you button!
Click to expand...
Click to collapse
I have a working phone. I have an unlock from htcdev. i have locked it, i can flash roms and recovery in twrp.
Its when I try an RUU it get suck on sending.... and errors out
Could it be my Main Version? I used misc tool to try to get back to 1.26.502.10, but can never get it to write the last digit correctly. Here is my getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.010
(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: 3999mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I guess I was wrong on being SuperCID. Using the misctool what should I change my main version to, and how?
Thanks
Here are the steps I did to unlock bootloader, root and acquire s-off:
I went back to fully stock unrooted s-on to get the OTA just to b on the safe side. This is where I knew the update screwed up the current s-off method so I unlocked the bootloader using HTCDev. Then proceed to root and pushed the revone file to the appropriate folder location. I followed all the commands from revone up to where u Chmod 755 revone. After that since I already had root, I simply type su then proceeded with the s-off and unlock command. Removed tampered label and voila!!! Back in business with latest software.
Sent from my HTC One using xda premium
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
I think what happened was the new update screwed up the motochopper temp root exploit and that's y I think u can't s-off with the updated software. But there is always a way...
Sent from my HTC One using xda premium
TabascoJoe said:
I have a working phone. I have an unlock from htcdev. i have locked it, i can flash roms and recovery in twrp.
Its when I try an RUU it get suck on sending.... and errors out
Could it be my Main Version? I used misc tool to try to get back to 1.26.502.10, but can never get it to write the last digit correctly. Here is my getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.010
(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: 3999mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I guess I was wrong on being SuperCID. Using the misctool what should I change my main version to, and how?
Thanks
Click to expand...
Click to collapse
You can't use the AT&T RUU because your HBOOT is higher than the one in the RUU. S-ON is preventing any older HBOOT to be flashed.
Hi guys, will this work on T-Mobile HTC ONE? I updated not knowing they blocked from s-off.
Thanx,
Vinny
It would certainly be worth a try. The hardware is the same, so I don't see why not... as long as your boot loader is 1.44.00000 (not sure on the amount of zero's) this should work.
I'm pretty sure there are nandroid images for TMO out there so give it a try.
vinny.1967 said:
Hi guys, will this work on T-Mobile HTC ONE? I updated not knowing they blocked from s-off.
Thanx,
Vinny
Click to expand...
Click to collapse
let me know if it's work with you
me_rashad said:
let me know if it's work with you
Click to expand...
Click to collapse
Hey me_rashad, it's a no go. I also flash tmobile nand still no go. from what i research on difference forum is because tmobile update did a patch to the 1.44 HBoot so i guess we have to wait till revone or monshine dev find the way.
vinny.1967 said:
Hey me_rashad, it's a no go. I also flash tmobile nand still no go. from what i research on difference forum is because tmobile update did a patch to the 1.44 HBoot so i guess we have to wait till revone or monshine dev find the way.
Click to expand...
Click to collapse
I did get the OTA too and having the same pesky error -6. The bootloader version still says 1.44.0000, how do we know if its patched or not? Shouldn't the version number increase? What is your version?
Hey guys, So I got a new phone and I was looking to unroot this one.
Currecntly my device is
Tampered
Unlocked
m7_ul PVT Ship s-on RH
HBOOT-1.44. 0000
radio-4a.14.3250. 13
eMMC-boot
What is the easiest way to return to stock.
I found Guru_Reset_M7_3.62.401.1.zip
But I was unsure if that was the correct one.
Thanks
derik123derik123 said:
Hey guys, So I got a new phone and I was looking to unroot this one.
Currecntly my device is
Tampered
Unlocked
m7_ul PVT Ship s-on RH
HBOOT-1.44. 0000
radio-4a.14.3250. 13
eMMC-boot
What is the easiest way to return to stock.
I found Guru_Reset_M7_3.62.401.1.zip
But I was unsure if that was the correct one.
Thanks
Click to expand...
Click to collapse
not enough info
their are 2 good guides for returning to stock
http://forum.xda-developers.com/showthread.php?t=2541082
and
http://forum.xda-developers.com/showthread.php?t=2358738
clsA said:
not enough info
their are 2 good guides for returning to stock
http://forum.xda-developers.com/showthread.php?t=2541082
and
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
What other information do you need?
The second would not work because I am s-on.
derik123derik123 said:
What other information do you need?
The second would not work because I am s-on.
Click to expand...
Click to collapse
fastboot getvar all (minus your serial no and IEMI)
clsA said:
fastboot getvar all (minus your serial no and IEMI)
Click to expand...
Click to collapse
Code:
(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.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3850mV
(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.044s
How would I go about getting this device back to stock.
Thank you for your support.
Your firmware is stock flash the latest AT&T RUU from htc1guru
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
if you want the easy s-off with revone use this android 4.1.2 RUU instead
http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
Sent from my HTC One using Tapatalk
clsA said:
Your firmware is stock flash the latest AT&T RUU from htc1guru
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply,
The link above takes to Cingular US, is that what I want? Its an ATT phone.
derik123derik123 said:
Thanks for the reply,
The link above takes to Cingular US, is that what I want? Its an ATT phone.
Click to expand...
Click to collapse
yep those are the AT&T RUU
clsA said:
Your firmware is stock flash the latest AT&T RUU from htc1guru
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
if you want the easy s-off with revone use this android 4.1.2 RUU instead
http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
is there a more up to date version this program can flash? like our phone's are 4.3 out of the box is there a 4.3 ruu?
rummrunner is a good sorce? we've talked about my device im getting it fixed tomorrow. so all i need to do is unlock the bootloader agian, and use rum runner to get s off?
vividblu2020 said:
is there a more up to date version this program can flash? like our phone's are 4.3 out of the box is there a 4.3 ruu?
rummrunner is a good sorce? we've talked about my device im getting it fixed tomorrow. so all i need to do is unlock the bootloader agian, and use rum runner to get s off?
Click to expand...
Click to collapse
The top link is the most current AT&T Ruu android 4.3
clsA said:
The top link is the most current AT&T Ruu android 4.3
Click to expand...
Click to collapse
flash those with rum runner?
vividblu2020 said:
flash those with rum runner?
Click to expand...
Click to collapse
you don't flash it .. it's an executable file that resets your phone to factory, out of the box condition. It most likely will fail on your windows 8.1 PC because of no fastboot driver support for your phone (yet)
Rumrunner is a method to gain s-off on your phone nothing more, nothing less
clsA said:
yep those are the AT&T RUU
Click to expand...
Click to collapse
I downloaded it and ran it. My phone is stuck on the HTC logo and the RUU said it could not update my rom please get the correct something or another.Going to let my phone sit at the HTC logo and see if it starts.
That ruu did have a error recovery steps, I'll try that.
Any insight?
EDIT: rebooted the phone and It's running like normal(Nothing was deleted etc..)
derik123derik123 said:
I downloaded it and ran it. My phone is stuck on the HTC logo and the RUU said it could not update my rom please get the correct something or another.Going to let my phone sit at the HTC logo and see if it starts.
That ruu did have a error recovery steps, I'll try that.
Any insight?
EDIT: rebooted the phone and It's running like normal(Nothing was deleted etc..)
Click to expand...
Click to collapse
what is your OS ?
do you have htc drivers installed
did you lock the bootloader ?
fastboot oem lock
did you follow the instructions here >> http://www.htc.com/us/support/htc-one-att/news/
clsA said:
what is your OS ?
do you have htc drivers installed
did you lock the bootloader ?
fastboot oem lock
did you follow the instructions here >> http://www.htc.com/us/support/htc-one-att/news/
Click to expand...
Click to collapse
drivers are installed.
This is what fastboot says.
HTML:
Tampered
Unlocked
m7_ul PVT Ship s-on RH
HBOOT-1.44. 0000
radio-4a.14.3250. 13
eMMC-boot
Ran the ruu again. This is what I get.
http://imgur.com/a/CSs6P
Followed instructions on that page as well.
derik123derik123 said:
drivers are installed.
This is what fastboot says.
HTML:
Tampered
Unlocked
m7_ul PVT Ship s-on RH
HBOOT-1.44. 0000
radio-4a.14.3250. 13
eMMC-boot
Ran the ruu again. This is what I get.
http://imgur.com/a/CSs6P
Followed instructions on that page as well.
Click to expand...
Click to collapse
lock the bootloader
fastboot oem lock
then run the RUU
do you want the instructions for RUU flashing the rom.zip
clsA said:
lock the bootloader
fastboot oem lock
then run the RUU
Click to expand...
Click to collapse
Yup.. That's it. It had to be something simple. Thanks alot for your help! you're awesome!
Does anyone know if a fix has been implemented for the failure to unlock of bootloader 1.54 and above yet? I have had a htc one not working for over a month now and no one can seem to help me and it seems many others have the same problem. Can someone either please help or point me in the direction of someone who would be willing to help? I think I may have found a solution myself that just needs a little more work.... Thank you!
bda714 said:
Does anyone know if a fix has been implemented for the failure to unlock of bootloader 1.54 and above yet? I have had a htc one not working for over a month now and no one can seem to help me and it seems many others have the same problem. Can someone either please help or point me in the direction of someone who would be willing to help? I think I may have found a solution myself that just needs a little more work.... Thank you!
Click to expand...
Click to collapse
You got the unlock_code.bin from htcdev? and flashed it with fastboot? ' fastboot flash unlocktoken Unlock_code.bin ' and it didn't work?
If you don't have the unlock_code you may have to revert with an RUU, you can't lock and change kernels and then unlock again with standard commands(edit: if you changed kernels/flashed anything), need that unlock_code.bin if you did so. Thought I screwed myself but re-downloaded the unlock_code.bin and it unlocked no problems regardless..
bda714 said:
Does anyone know if a fix has been implemented for the failure to unlock of bootloader 1.54 and above yet? I have had a htc one not working for over a month now and no one can seem to help me and it seems many others have the same problem. Can someone either please help or point me in the direction of someone who would be willing to help? I think I may have found a solution myself that just needs a little more work.... Thank you!
Click to expand...
Click to collapse
Hello,
I will need more information regarding your device to better assist you:
-HBOOT current version
-Firmware version
-Currently installed ROM, and version
-Carrier
-CID number
-Model ID
Device info
I had previously received the google edition update to 4.4 and I have been told that google implemented some new security which no longer allows users of their rom to unlock through htc dev website. Not sure if it makes a difference but my device is a m7-ul. Is that not supposed to be a developers edition? If I put the flash unlock token in the first time it says flash success but no splash screen no change. if I put the oem unlock command in first it says remote fail. if I put flash unlock token command immediately followed by oem unlock command I get a failure to load custom splash screen error, seems it would work if I hadn't erased the files that contain the custom splash unlock screen right? Is there any way to get those back on the phone even with an otg cable or I have an mini sd card reader that I can plug in to the phone. Will read the sd card in recovery.
anyway here is the getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(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: 3929mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
bda714 said:
I had previously received the google edition update to 4.4 and I have been told that google implemented some new security which no longer allows users of their rom to unlock through htc dev website. Not sure if it makes a difference but my device is a m7-ul. Is that not supposed to be a developers edition? If I put the flash unlock token in the first time it says flash success but no splash screen no change. if I put the oem unlock command in first it says remote fail. if I put flash unlock token command immediately followed by oem unlock command I get a failure to load custom splash screen error, seems it would work if I hadn't erased the files that contain the custom splash unlock screen right? Is there any way to get those back on the phone even with an otg cable or I have an mini sd card reader that I can plug in to the phone. Will read the sd card in recovery.
anyway here is the getvar all
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
finished. total time: 0.031s
Click to expand...
Click to collapse
1- M7_UL could be any edition not necessarily Dev Edition (which is modelid: PN0712000 and cid: BS_US001)
2- fastboot oem unlock, only works on GPE hboots (and I think only on 1.54)
3- are you on a GPE bootloader (dark one), or the HTC bootloader (white one)?
nkk71 said:
1- M7_UL could be any edition not necessarily Dev Edition (which is modelid: PN0712000 and cid: BS_US001)
2- fastboot oem unlock, only works on GPE hboots (and I think only on 1.54)
3- are you on a GPE bootloader (dark one), or the HTC bootloader (white one)?
Click to expand...
Click to collapse
I was on the dark bootloader when it first happened but on my first post looking for help it was actually yourself and sahlizz who recommended that I flash the dev edition firmware from this link:
~~ORIG POST TEXT: @nkk71, do you think he can flash the Dev edition firmware 4.06.1540.x and unlock the bootloader? CID/MID already matches..
Dev firmware listed here: http://arhd.onedroid.net/db_mirror/F..._One/1540/
RE:
if it is a GPE phone, then maybe (yes long shot), "fastboot oem unlock"
otherwise get a new token and try again.
bda714 said:
I was on the dark bootloader when it first happened but on my first post looking for help it was actually yourself and sahlizz who recommended that I flash the dev edition firmware from this link:
~~ORIG POST TEXT: @nkk71, do you think he can flash the Dev edition firmware 4.06.1540.x and unlock the bootloader? CID/MID already matches..
Dev firmware listed here: http://arhd.onedroid.net/db_mirror/F..._One/1540/
RE:
if it is a GPE phone, then maybe (yes long shot), "fastboot oem unlock"
otherwise get a new token and try again.
Click to expand...
Click to collapse
sorry you got stuck, but I didnt come up with the idea of flashing a Dev Edition firmware on non-dev phone.
Here's what I recommend: is the ATT OTA to 4.x out yet (which matches your MID and CID)? if so go find it, ask for it, or wait for it and post a request for the original OTA file.
once you have your hands on that, extract "firmware.zip" from it and flash your phone back to ATT firmware, then the HTCdev unlock should work.
nkk71 said:
sorry you got stuck, but I didnt come up with the idea of flashing a Dev Edition firmware on non-dev phone.
Here's what I recommend: is the ATT OTA to 4.x out yet (which matches your MID and CID)? if so go find it, ask for it, or wait for it and post a request for the original OTA file.
once you have your hands on that, extract "firmware.zip" from it and flash your phone back to ATT firmware, then the HTCdev unlock should work.
Click to expand...
Click to collapse
I wasn't trying to place blame at all sorry if I implied that. was just trying to explain the chain of events. anyway thank you very much for your help but I am pretty sure that the ota isn't out yet. thanks again and let me know if you find anything else
bda714 said:
I wasn't trying to place blame at all sorry if I implied that. was just trying to explain the chain of events. anyway thank you very much for your help but I am pretty sure that the ota isn't out yet. thanks again and let me know if you find anything else
Click to expand...
Click to collapse
no worries, i am sorry you got stuck though.
Anyway, looks like you're right OTA not available, but shouldn't be too long: http://www.htc.com/us/go/htc-software-updates/
Once it's out, make sure to get your hands on it, good luck
Hey, I don't know where to start from...
I just bought a Sprint HTC One Max yesterday and I was happy to S-Off and Root it, so I followed this guide... http://forum.xda-developers.com/showthread.php?t=2550559
I followed every instruction all the way down the Step 4c. At Step 4d I got confused and skipped to 4f which is "Issue the command fastboot flash boot boot.img" after that my phone went from the HTC logo starting over and over to it being stuck in bootloader mode. Now I can't do a Factory Reset or a Recovery.
I've tried to go back to stock and flash this RUU file: 0P3PIMG_T6_WHL_JB43_SENSE55_SPCS_Sprint_WWE_1.14.651.1_Radio_1.30.50.1022_NV_SPCS_4.50_003_release_338466_signed_2.zip
During the flashing process, I got two errors
FAILED (remote: 43 main version check fail)
FAILED (remote: 12 singature verify fail)
I am new to this and something told me to just wait but I didn't listen. If anyone could help me, I would really appreciate it, I just got this phone yesterday and I didn't even get to use any features, because I was too eager to S-OFF and Root. All I want to do is go back to stock, play games on my new phone and never attempt to root or S-Off again. =,(
Thanks!
-----------------------------------------------------------------------------------
If this helps, my bootloader screen says this:
***TAMPERED***
***RELOCKED***
***Security Warning***
T6WHL PVT SHIP S-ON RH
HBOOT-2.46.0000
RADIO-v33.120.274_T6.0829
QSC-
OS-1.16.651.4
eMMC-boot 2048MB
Nov 6 2013,17:04:11.0
------------------------------------------------------------------------------------
My fastboot getvar all results
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.46.0000
(bootloader) version-baseband: 1.35.50.1106
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.16.651.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 99000428505809
(bootloader) product: t6whl
(bootloader) platform: HBOOT-8064
(bootloader) modelid: 0P3P70000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4118mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-70784205
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
You should have used firewater. Look that up, it's quick, easy, and you don't need HTCdev.
Sent from my HTC One Max using Tapatalk!
gimmeitorilltell said:
You should have used firewater. Look that up, it's quick, easy, and you don't need HTCdev.
Sent from my HTC One Max using Tapatalk!
Click to expand...
Click to collapse
I wanted to but I didn't want to know where to start, so I just went ahead and used Punk9's guide.
This forum is for the Sprint HTC One . This belongs in the HTC one max forum
Sent from my HTCONE using xda app-developers app
pelon90005 said:
This forum is for the Sprint HTC One . This belongs in the HTC one max forum
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Sorry, how do I move it to the HTC One Max section?
You can message a moderator and ask that it be moved to the one max q&a thread.
Sent from my HTC One Max using Tapatalk!
Can someone tell me what RUU file I need to download?
Jet_Life said:
Can someone tell me what RUU file I need to download?
Click to expand...
Click to collapse
It looks like you had the right RUU file... But anyways you can get to your bootloader so you aren't bricked.. I believe if you search around someone posted all the phones image files ex: system.img recovery.img boot.img etc etc.. Grab those and fastboot them back to the phone. It already sounds like your terminal talks to your boot loader via fastboot so it would be "fastboot devices" make sure you get your devices serial number then "fastboot flash boot boot.img" fastboot flash recovery recovery.img" "fastboot flash system system.img" etc etc hit me up if you need some help
Murrda said:
It looks like you had the right RUU file... But anyways you can get to your bootloader so you aren't bricked.. I believe if you search around someone posted all the phones image files ex: system.img recovery.img boot.img etc etc.. Grab those and fastboot them back to the phone. It already sounds like your terminal talks to your boot loader via fastboot so it would be "fastboot devices" make sure you get your devices serial number then "fastboot flash boot boot.img" fastboot flash recovery recovery.img" "fastboot flash system system.img" etc etc hit me up if you need some help
Click to expand...
Click to collapse
For some reason, I unlocked my bootloader and my phone started right up, so I finished Punk9's guide and now I am ROOTED & have S-OFF. Thanks for the help though!!!
Is there an RUU for Verizon One Max?
I saw a pointer for Sprint and Intl, but not for
Verizon. I asked HTC support, they said
VZW wont let them distribute it.
Thanks
fuzzynco said:
I saw a pointer for Sprint and Intl, but not for
Verizon. I asked HTC support, they said
VZW wont let them distribute it.
Thanks
Click to expand...
Click to collapse
Distribute what? If your talking bout vzw Ruu there is one.
Sent from my HTC6600LVW using XDA Premium 4 mobile app
yes, that is what I meant
thayl0 said:
Distribute what? If your talking bout vzw Ruu there is one.
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Do you have a link to the post or the download?
fuzzynco said:
Do you have a link to the post or the download?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2587336
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Thanks... got it.
Murrda said:
It looks like you had the right RUU file... But anyways you can get to your bootloader so you aren't bricked.. I believe if you search around someone posted all the phones image files ex: system.img recovery.img boot.img etc etc.. Grab those and fastboot them back to the phone. It already sounds like your terminal talks to your boot loader via fastboot so it would be "fastboot devices" make sure you get your devices serial number then "fastboot flash boot boot.img" fastboot flash recovery recovery.img" "fastboot flash system system.img" etc etc hit me up if you need some help
Click to expand...
Click to collapse
Sorry to bother you, but, you would happen to know how to flash to Cricket from Sprint would you?
Guys,
Usually I am pretty good at this stuff, but I am banging my head against the wall trying to figure out how to get an RUU to flash to get stock AT&T firmware back on this HTC One I have to send back for warranty exhange. Keep getting Error 155 on the RUU.
Thanks,
Y2J
y2jdmbfan said:
Guys,
Usually I am pretty good at this stuff, but I am banging my head against the wall trying to figure out how to get an RUU to flash to get stock AT&T firmware back on this HTC One I have to send back for warranty exhange. Keep getting Error 155 on the RUU.
Thanks,
Y2J
Click to expand...
Click to collapse
If it is an AT&T phone then just take it to an AT&T service center. They will exchange it even if it has been rooted, s-offed/on, different ROM, it does not matter. HTC will not touch it but AT&T has no issues. You do not need to go through all the trouble of changing it back. Read later post in this thread
http://forum.xda-developers.com/showthread.php?t=2333894
It confirms what i am saying...
Solarenemy68 said:
If it is an AT&T phone then just take it to an AT&T service center. They will exchange it even if it has been rooted, s-offed/on, different ROM, it does not matter. HTC will not touch it but AT&T has no issues. You do not need to go through all the trouble of changing it back. Read later post in this thread
http://forum.xda-developers.com/showthread.php?t=2333894
It confirms what i am saying...
Click to expand...
Click to collapse
Unfortunately I already have the replacement device from HTC...
Just flash an ATT stock rom, then restore the stock recovery. Done.
cschmitt said:
Just flash an ATT stock rom, then restore the stock recovery. Done.
Click to expand...
Click to collapse
Via RUU? I've tried a bunch of times with the RUU's that are out there and keep getting error 155.
y2jdmbfan said:
Via RUU? I've tried a bunch of times with the RUU's that are out there and keep getting error 155.
Click to expand...
Click to collapse
No, via CWM/TWRP like this rom. Then flash the stock recovery in fastboot pulled from the 4.18.502.7 firmware.zip from here.
cschmitt said:
No, via CWM/TWRP like this rom. Then flash the stock recovery in fastboot pulled from the 4.18.502.7 firmware.zip from here.
Click to expand...
Click to collapse
Where do I get the stock recovery? Not sure which file in the list of the link you provided has the recovery.img.
Thanks!
y2jdmbfan said:
Where do I get the stock recovery? Not sure which file in the list of the link you provided has the recovery.img.
Thanks!
Click to expand...
Click to collapse
Here's the signed firmware.zip from the OTA: firmware_4.18.502.7.zip
You can flash it in fastboot with
Code:
fastboot oem rebootRUU
fastboot flash zip firmware_4.18.502.7.zip
fastboot flash zip firmware_4.18.502.7.zip (yes, twice!)
fastboot erase cache
fastboot reboot
This will give you the stock recovery, radio, hboot, etc.
cschmitt said:
Here's the signed firmware.zip from the OTA: firmware_4.18.502.7.zip
You can flash it in fastboot with
Code:
fastboot oem rebootRUU
fastboot flash zip firmware_4.18.502.7.zip
fastboot flash zip firmware_4.18.502.7.zip (yes, twice!)
fastboot erase cache
fastboot reboot
This will give you the stock recovery, radio, hboot, etc.
Click to expand...
Click to collapse
Now I am getting this error...I am S-On BTW if that makes a difference...
C:\platform-tools>fastboot flash zip firmware_4.18.502.7.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47880 KB)...
OKAY [ 3.170s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 3.415s
Post the output of fastboot getvar all minus IMEI and S/N.
cschmitt said:
Post the output of fastboot getvar all minus IMEI and S/N.
Click to expand...
Click to collapse
C:\platform-tools>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(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: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.069s
I think the issue is that you can't downgrade firmware from 4.19 to 4.18 with s-on. Was the phone s-off at one time?
cschmitt said:
I think the issue is that you can't downgrade firmware from 4.19 to 4.18 with s-on. Was the phone s-off at one time?
Click to expand...
Click to collapse
Yes it was. I accidentally put back s-on before I flashed the RUU. The phone had s-off and a custom software when I purchased it. The phone was acting up so I called HTC and got an advanced replacement and already have the replacement. I wanted to flash back to a stock firmware and remove s-off and lock the bootloader before I send the old phone back to HTC.
Unless you are willing to s-off again you're stuck with that firmware. The stock recovery can be pulled from the zip and flashed separately with fastboot though.
cschmitt said:
Unless you are willing to s-off again you're stuck with that firmware. The stock recovery can be pulled from the zip and flashed separately with fastboot though.
Click to expand...
Click to collapse
Oh I would s-off again no problem, but I can't get rumrunner or firewater to work...Any hints would be great based on the getvar I posted above.
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
C:\platform-tools>
Anyone have any ideas to get firewater working?
I have flashed Android Revolution HD 52.0 and then tried to do firewater, but it kicks me back to the command prompt after the initial chugging...