Related
Hey guys,
I have just download 1.28.401.7 RUU to flash on my htc one.
MY htc one Product code is m7_ul and cid is htc_001 and mid is PN710000.
when the ruu is flashing it shows a error and says there is a diff. bootloader version.
What am i doing wrong??
Most likely the current version of a bootloader is newer than that which contains in RUU .To you it is necessary to flash RUU under s-off.
exactly the same ,i desperately need to get back to stock to send phone away,what can we do to to rectify this please PLEASE
tash2013 said:
Most likely the current version of a bootloader is newer than that which contains in RUU .To you it is necessary to flash RUU under s-off.
Click to expand...
Click to collapse
To do S-off do we need to be rooted?
udimars30 said:
To do S-off do we need to be rooted?
Click to expand...
Click to collapse
NOT need!
this is what i get in getver
bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.61.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA33VW903941
(bootloader) imei: 354436050514510
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3964mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.691s
westentertainer said:
this is what i get in getver
bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.61.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA33VW903941
(bootloader) imei: 354436050514510
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3964mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.691s
Click to expand...
Click to collapse
You need
1) Get S-OFF
2) Change CID to unbranded one (HTC__001 for example)
3) Flash the European RUU 1.28.401.7
4) Recieve OTA to latest firmware
if you want to remain on ORANGE, it is necessary to find RUU for orange and you don't need to change CID
anyone please i need to post this phone today or at the latest this weekend,,,because i have relocked the bootloader i can not get out of fast boot screen bahhhh
tash2013 said:
NOT need!
Click to expand...
Click to collapse
i have done to 1st part of S-off but on second it is showing "the system cannot find the specific path"
any thing i'm doing wrong??
edit done and i have s-off now yay
tash2013 said:
NOT need!
Click to expand...
Click to collapse
can i flash the ruu on unlocked bootloader??
udimars30 said:
can i flash the ruu on unlocked bootloader??
Click to expand...
Click to collapse
Under s-off you can flash RUU and then receive OTA with unlocked bootloader.
When got S-ON you need relocked (locked) bootloader to receive OTA correctly.
anyone please i need to post this phone today or at the latest this weekend,,,because i have relocked the bootloader i can not get out of fast boot screen bahhhh
Click to expand...
Click to collapse
Was unlocked with HTCdev? and then relocked? just type "fastboot oem unlock"
tash2013 said:
Under s-off you can flash RUU and then receive OTA with unlocked bootloader.
When got S-ON you need relocked (locked) bootloader to receive OTA correctly.
ok i'll flash right now and then tell you
thanks btw
Click to expand...
Click to collapse
tash2013 said:
Under s-off you can flash RUU and then receive OTA with unlocked bootloader.
When got S-ON you need relocked (locked) bootloader to receive OTA correctly
One more thing, note can I change my cid and update to that version??
Sent from my Nexus 10 using Tapatalk 4 Beta
Click to expand...
Click to collapse
udimars30 said:
Under s-off you can flash RUU and then receive OTA with unlocked bootloader.
When got S-ON you need relocked (locked) bootloader to receive OTA correctly
One more thing, note can I change my cid and update to that version??
Sent from my Nexus 10 using Tapatalk 4 Beta
Click to expand...
Click to collapse
For change cid type "fastboot oem writecid XXXXXXXX"
XXXXXXXX - cid to change
You have HTC__001 CID? If yes, you don't need change cid for 1.28.401.7 RUU.
tash2013 said:
For change cid type "fastboot oem writecid XXXXXXXX"
XXXXXXXX - cid to change
You have HTC__001 CID? If yes, you don't need change cid for 1.28.401.7 RUU.
Click to expand...
Click to collapse
yes i have the same and i just want 4.2.2 so should i change my cid??
tash2013 said:
You need
1) Get S-OFF
2) Change CID to unbranded one (HTC__001 for example)
3) Flash the European RUU 1.28.401.7
4) Recieve OTA to latest firmware
if you want to remain on ORANGE, it is necessary to find RUU for orange and you don't need to change CID
Click to expand...
Click to collapse
thanks for reply
how do i get s off
when it states orange ,i actually had the phone from t mobile but unlocked it with a code that i purchased ,i am really panicking now been up all night trying to do this any help would be very appreciated
To get OTAs you will need to change your mid if your going from "Tmobile" to "Dev Edition" make sure your mid and cid matches the RUU
Sent from my HTC One using xda app-developers app
pulling my hair out now i will never ever flash a custom rom again!!!!
You should of made a stock Nandroid backup before you decided to flash roms...have a ladder before you dig a whole thats hard to get out!!
Sent from my HTC One using Xparent BlueTapatalk 2
handman29 said:
You should of made a stock Nandroid backup before you decided to flash roms...have a ladder before you dig a whole thats hard to get out!!
Sent from my HTC One using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
i did do a back up
Hi, i seem to have gotten a problem with my phone jumping to car mode randomly, even when its plugged in, so guess it is in need of a service.
After reading some guides about going back to stuff, i just have to get confirmation that i have understood it correctly.
The only process i need to do is the following (I have s-off and hboot 1.44, latest firmware):?
1. Change the SID back to stock
2. Run the RUU.exe
3. Make it s-off again and remove tampered with revone?
Is that all or am i forgetting something crucial?
raysv said:
Hi, i seem to have gotten a problem with my phone jumping to car mode randomly, even when its plugged in, so guess it is in need of a service.
After reading some guides about going back to stuff, i just have to get confirmation that i have understood it correctly.
The only process i need to do is the following (I have s-off and hboot 1.44, latest firmware):?
1. Change the SID back to stock
2. Run the RUU.exe
3. Make it s-off again and remove tampered with revone?
Is that all or am i forgetting something crucial?
Click to expand...
Click to collapse
1- change CID back to stock
2- remove TAMPERED using either revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- change to LOCKED using either revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- AFTER ABOVE use the correct RUU.exe for your phone; you will not loose S-Off because of the RUU.
nkk71 said:
1- change CID back to stock
2- remove TAMPERED using either revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- change to LOCKED using either revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- AFTER ABOVE use the correct RUU.exe for your phone; you will not loose S-Off because of the RUU.
Click to expand...
Click to collapse
Thanks for the reply.
Did all the things, but it refuses to flash the ruu.. when running the ruu.exe its returning error 155 after awhile Any idea of what might be wrong?
are you using the right CID for the RUU?
stovie_steve said:
are you using the right CID for the RUU?
Click to expand...
Click to collapse
Yes I changed my CID back to the original CID, and the RUU i downloaded said on the download page that this was for this CID HTC__Y13.
My bootloader also says LOCKED
raysv said:
Yes I changed my CID back to the original CID, and the RUU i downloaded said on the download page that this was for this CID HTC__Y13.
My bootloader also says LOCKED
Click to expand...
Click to collapse
Did u also check MID?
I thought 155 was because of an unlocked bootloader, does it give any information more than 155? Maybe also try to find the log (should be somewhere in temp on ur pc)
I'll be online later today, and will check back.
Sent from my HTC One using Tapatalk
I also had that error before when I was on a later hboot (1.54 and 1.55) and would only work if I had hboot 1.44
Can you post your fastboot getvar all removing S/N and IMEI?
stovie_steve said:
I also had that error before when I was on a later hboot (1.54 and 1.55) and would only work if I had hboot 1.44
Can you post your fastboot getvar all removing S/N and IMEI?
Click to expand...
Click to collapse
Here is my getvar:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4273mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
Have tried downgrading the firmware also by "unlocking" the bootloader again as described in the post over (not the revone way but the other). and try and flash the hboot 1.44.. but now it seems that I'm just getting remote denied when trying to flash.. Dosn't that indicate that the bootloader is still locked?
Have managed to downgrade the hboot and firmware... Will try the ruu again and see if it works if i can get it to stay connected to the computer via USB... Right now it just plings for 2 sekunds, and then loosing the connection again..
Thanks alot guys for the help.
Seems like it was my hboot messing up, once i downgraded the firmaware and zip before trying the ruu it seems to work Atleast no 155 error or problems arised so faar, just the green progress bar *keeps his fingers crossed*
Again, great help Now its time to ship it to service
BTW: anyone know if they are actually able to fix the usb plug since its unibody design? Or will it most likly be a replacement?
Hi Guys i am following this guide to restore my phone to stock for HTC repair (camera issue)
http://forum.xda-developers.com/showthread.php?t=2358738
do I need to make the phone s-on and lock the bootloader?
it mentions that can brick if has a modified HBOOT when re-locking the bootloader
so my main question is this "is the Stock HBOOT included in RUU?
Dynomutt said:
Hi Guys i am following this guide to restore my phone to stock for HTC repair (camera issue)
http://forum.xda-developers.com/showthread.php?t=2358738
do I need to make the phone s-on and lock the bootloader?
it mentions that can brick if has a modified HBOOT when re-locking the bootloader
so my main question is this "is the Stock HBOOT included in RUU?
Click to expand...
Click to collapse
you might wanna check my guide: http://forum.xda-developers.com/showthread.php?t=2541082
thanks so much
Dynomutt said:
thanks so much
Click to expand...
Click to collapse
no problem, please follow instruction 1, then 2 then 3, etc.
s-on is OPTIONAL, it's up to YOU to decide that
still having trouble, found my original stock backup of 4.2.2, but now have HBOOT 1.44, i really need a full Vodafone UK RUU the .exe version would probably be best but just cant find anywhere, cant even flash the OTA RUU probably because I have mismatched firmware, recovery and HBOOT now,
well UPS is picking it up tomorrow so i'll just have to hope they don't refuse repair due to software not being 100% stock especially as the issue is a hardware fault
wish me luck and thanks for you help
Dynomutt said:
still having trouble, found my original stock backup of 4.2.2, but now have HBOOT 1.44, i really need a full Vodafone UK RUU the .exe version would probably be best but just cant find anywhere, cant even flash the OTA RUU probably because I have mismatched firmware, recovery and HBOOT now,
well UPS is picking it up tomorrow so i'll just have to hope they don't refuse repair due to software not being 100% stock especially as the issue is a hardware fault
wish me luck and thanks for you help
Click to expand...
Click to collapse
can u post a "fastboot getvar all" (remove IMEI and s/n)
nkk71 said:
can u post a "fastboot getvar all" (remove IMEI and s/n)
Click to expand...
Click to collapse
sure will thanks, whats ODD is that the CID does not match my CID in bootloader, in bootloader it says VODAP001 is my CID,
EDIT: just check it and it is HTC__001 changing back to VODAP001 and trying OTA again
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3984mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.087s
Dynomutt said:
sure will thanks, whats ODD is that the CID does not match my CID in bootloader, in bootloader it says VODAP001 is my CID
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: SHxxxxxxxxxxxxxx
(bootloader) imei: 3xxxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3984mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.087s
Click to expand...
Click to collapse
1- you might wanna edit your post and remove IMEI and s/n
2- from above getvar, you look like you followed the first part of my guide an now your phone, is an European unbranded phone.
3- so quick quick question, you wanna go back to "VODAP001" (do you really need to?) ? is there a nandroid backup out there?
nkk71 said:
1- you might wanna edit your post and remove IMEI and s/n
2- from above getvar, you look like you followed the first part of my guide an now your phone, is an European unbranded phone.
3- so quick quick question, you wanna go back to "VODAP001" (do you really need to?) ? is there a nandroid backup out there?
Click to expand...
Click to collapse
Yeah sorry I noticed edited post now, ive changed my CID back to VODAP001, I have my original 4.2.2 stock rom flashed hopefully be able to pull to 4.3 OTA once im back up and running, thanks for you help mate
thanks again for your help, OTA is now downloading and i should be back to fully stock soon and can send for repair worry free.
Dynomutt said:
Yeah sorry I noticed edited post now, ive changed my CID back to VODAP001, I have my original 4.2.2 stock rom flashed hopefully be able to pull to 4.3 OTA once im back up and running, thanks for you help mate
Click to expand...
Click to collapse
don't forget you need "stock recovery" for OTA to update correctly, and do not go from s-off to s-on on 4.3 (hboot 1.55) it will most likely trigger a "tamper detected"!!
if you did get hboot 1.55 just keep s-off, otherwise you're gonna be back on square 1.
I have to sign off now, but you can PM me if anything comes up before tomorrow.
if my guide did help you in any way, i would appreciate it if you posted your details, in my thread (whenever you get a chance), it will be helpful to others.
and hit the thanks button in the guide
good luck :fingers-crossed:
Yeah I flashed my original stock backup, flashed stock recovery and locked bootloader , I had forgot to change my CID back, it wasn't till u advised that I post my " getvar all" that I noticed, I haven't checked if my HBOOT is still 1.44 or updated to 1.55 yet, I left s-off hope it still is, again many thanks mate
Sent from my HTC One using xda app-developers app
Yeah I'm on HBOOT 1.55 now but still s-off, I take it if I s-on again I won't be able to get it back, I used rumrunner s-off last time but I that was on HBOOT 1.54 iirc, not that it matter now anyway
Sent from my HTC One using xda app-developers app
Dynomutt said:
Yeah I'm on HBOOT 1.55 now but still s-off, I take it if I s-on again I won't be able to get it back, I used rumrunner s-off last time but I that was on HBOOT 1.54 iirc, not that it matter now anyway
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Keep s-off, otherwise u may end up having to start at square 1, and if I read correctly, u have to send it off in the morning.
UK repair centers seem quite decent, and they can't really prove it wasnt s-off to begin with.
"what's s-what anyways, hmm, no clue what u talking about"
Sent from my HTC One using Tapatalk
nkk71 said:
Keep s-off, otherwise u may end up having to start at square 1, and if I read correctly, u have to send it off in the morning.
UK repair centers seem quite decent, and they can't really prove it wasnt s-off to begin with.
"what's s-what anyways, hmm, no clue what u talking about"
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
ha ha yeah, weirdly though this morning I still had root, is this normal after OTA?
I recently tried to revert back from CM 10 to stock on my HTC one.
Everything seemed to be going fine, I found what I believed to be the right RUU(I couldnt find it in a .exe, only .zip) .
And I successfully used revone to get s-off, remove tampered and change unlocked to locked in the bootloader.
But when changing s-off back to s-on the security warning banner showed up in the bootloader and for some reason I couldn’t get into the OS anymore, it just went straight to the bootloader. I didn’t bother thinking about it since I was going to install the RUU either way. But I get the same error every time I try to install it: FAILED (remote: 12 signature verify fail). Also I couldn’t get into recovery, it just shot be back straight into the bootloader.(Correct me if i'm wrong but did the ruu.zip fail because you have to have s-off for it to work? Would make sense.) On top of that I couldn’t just get s-off again because for some reason i can only use adb commands when the phone is in the actual OS, it doesn't seem recognize it when its in bootloader/fastboot/recovery, fastboot commands work fine tho.
I was able to unlock the bootloader again using htcdev and I can now access twrp, but I can't seem to be able to factory reset, it just says: Unable to mount /data and unable to mount internal storage. The mount option in twrp does not seem to work either, trying to check data makes nothing happen. Also instead of it just launching to the bootloader directly on startup, it now gets stuck in a bootloop until you make it go into the bootloader.
As you can see i'm in quite the pickle and absolutely any help on either getting back to a functional CM or stock would be much appreciated.
The getvar all info:
(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.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W903347
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4065mV
(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.045s
If any more info is needed just ask
victor_021 said:
I recently tried to revert back from CM 10 to stock on my HTC one.
Everything seemed to be going fine, I found what I believed to be the right RUU(I couldnt find it in a .exe, only .zip) .
And I successfully used revone to get s-off, remove tampered and change unlocked to locked in the bootloader.
But when changing s-off back to s-on the security warning banner showed up in the bootloader and for some reason I couldn’t get into the OS anymore, it just went straight to the bootloader. I didn’t bother thinking about it since I was going to install the RUU either way. But I get the same error every time I try to install it: FAILED (remote: 12 signature verify fail). Also I couldn’t get into recovery, it just shot be back straight into the bootloader.(Correct me if i'm wrong but did the ruu.zip fail because you have to have s-off for it to work? Would make sense.) On top of that I couldn’t just get s-off again because for some reason i can only use adb commands when the phone is in the actual OS, it doesn't seem recognize it when its in bootloader/fastboot/recovery, fastboot commands work fine tho.
I was able to unlock the bootloader again using htcdev and I can now access twrp, but I can't seem to be able to factory reset, it just says: Unable to mount /data and unable to mount internal storage. The mount option in twrp does not seem to work either, trying to check data makes nothing happen. Also instead of it just launching to the bootloader directly on startup, it now gets stuck in a bootloop until you make it go into the bootloader.
As you can see i'm in quite the pickle and absolutely any help on either getting back to a functional CM or stock would be much appreciated.
The getvar all info:
(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.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W903347
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4065mV
(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.045s
If any more info is needed just ask
Click to expand...
Click to collapse
Where did you get the RUU from? It should work even if S-ON as long as the version of the RUU is the same as or newer than your current version.
EDIT: Did it say it was Encrypted or Decrypted? It needs to have an Encrypted Signature or else you'll get the Remote 12 error.
victor_021 said:
I recently tried to revert back from CM 10 to stock on my HTC one.
Everything seemed to be going fine, I found what I believed to be the right RUU(I couldnt find it in a .exe, only .zip) .
And I successfully used revone to get s-off, remove tampered and change unlocked to locked in the bootloader.
But when changing s-off back to s-on the security warning banner showed up in the bootloader and for some reason I couldn’t get into the OS anymore, it just went straight to the bootloader. I didn’t bother thinking about it since I was going to install the RUU either way. But I get the same error every time I try to install it: FAILED (remote: 12 signature verify fail). Also I couldn’t get into recovery, it just shot be back straight into the bootloader.(Correct me if i'm wrong but did the ruu.zip fail because you have to have s-off for it to work? Would make sense.) On top of that I couldn’t just get s-off again because for some reason i can only use adb commands when the phone is in the actual OS, it doesn't seem recognize it when its in bootloader/fastboot/recovery, fastboot commands work fine tho.
I was able to unlock the bootloader again using htcdev and I can now access twrp, but I can't seem to be able to factory reset, it just says: Unable to mount /data and unable to mount internal storage. The mount option in twrp does not seem to work either, trying to check data makes nothing happen. Also instead of it just launching to the bootloader directly on startup, it now gets stuck in a bootloop until you make it go into the bootloader.
As you can see i'm in quite the pickle and absolutely any help on either getting back to a functional CM or stock would be much appreciated.
The getvar all info:
(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.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W903347
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4065mV
(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.045s
If any more info is needed just ask
Click to expand...
Click to collapse
Never Go S-ON !!!!
flash this with TWRP
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Thanks for the replies but after a few hours of nonstop research i managed to fix the problem. I simply installed CWM because TWRP had totally crapped out on me. From there I just simply sideloaded a Viperone 4.4.2 rom and everything is working fine, don't really feel the need to return to stock anymore. Can't believe how simple that turned out to be, anyway thanks for the replies and hopefully this might help other people in the same situation.
stuck
hlo sir,I m really depressed these days bcz I can't finf ruu for my htc one as it shows
TAMPERED RELOCKED SECURITY WARNING.. my cid is VODAP021 and mied is PN071400 hboot
is 1.54 and os is 2.24.980.3... I tried to flash a guru reset with same cid no. but with slight
difference in os it was 2.24.980.2 and it showed signature verify fail......so plzzzz helpppp
meee....suggest me the perfect ruu
jaspreet4140 said:
hlo sir,I m really depressed these days bcz I can't finf ruu for my htc one as it shows
TAMPERED RELOCKED SECURITY WARNING.. my cid is VODAP021 and mied is PN071400 hboot
is 1.54 and os is 2.24.980.3... I tried to flash a guru reset with same cid no. but with slight
difference in os it was 2.24.980.2 and it showed signature verify fail......so plzzzz helpppp
meee....suggest me the perfect ruu
Click to expand...
Click to collapse
Guru reset is a rom not a ruu, so you must be bootloader unlocked to flash it via custom recovery (twrp 2.6.3.3 preferred)
stuck
@aray ,sir thnx for the quik reply....sir but I m stuck can't unlock bootloader I m s-on plz tell with which ruu I would flash my phone..send link....I would really appreciate that
jaspreet4140 said:
@aray ,sir thnx for the quik reply....sir but I m stuck can't unlock bootloader I m s-on plz tell with which ruu I would flash my phone..send link....I would really appreciate that
Click to expand...
Click to collapse
No need to use ''sir''
You can unlock bootloader, it has nothing to do with being s-on! Get you identifier token then submit it to htcdev. They will instantly send you an e-mail with your unlock_code.bin. Flash it and you'll be unlocked.
Video tutorial here
And there is no RUU for your phone so the guru reset rom is the best option.
Video tutorial to use a guru reset rom here
re
@alray,thx for showing concern n my problem...when I use command 'fastboot oem get_indentifier_token' I get msg of command error.....help
jaspreet4140 said:
@alray,thx for showing concern n my problem...when I use command 'fastboot oem get_indentifier_token' I get msg of command error.....help
Click to expand...
Click to collapse
do you have your htc drivers correctly installed on your computer and the android sdk?
When you go in windows devices manager, do you see you your phone as ''My HTC'' ?
in command prompt when you do ''fastboot devices'' does it reply your phone s/n + fastboot ?
ya I downloaded htc driveres frm xda only...but I don't hve android sdk.....
but on running fastboot devices it shows my phone serial....
stuck
@alray plzz reply me........n help mee
jaspreet4140 said:
ya I downloaded htc driveres frm xda only...but I don't hve android sdk.....
but on running fastboot devices it shows my phone serial....
Click to expand...
Click to collapse
jaspreet4140 said:
@alray plzz reply me........n help mee
Click to expand...
Click to collapse
hlo sir,I m really depressed these days bcz I can't find ruu for my htc one as it shows TAMPERED RELOCKED SECURITY WARNING.. my cid is VODAP021 and mied is PN071400 hboot is 1.54 and os is 2.24.980.3... I tried to flash a guru reset with same cid no. but with slight difference in os it was 2.24.980.2 and it showed signature verify fail......so plzzzz helpppp meee....suggest me the perfect ruus
Click to expand...
Click to collapse
could i ask you to go to your other post: http://forum.xda-developers.com/showpost.php?p=52109146&postcount=41 and remove it. (EDIT and just but "deleted" as text), let's keep it here
you can get the mini-sdk from here: http://www.androidfilehost.com/?fid=23329332407585867
extract it and put the files in a simple folder, maybe something like C:\ADB\
then you need to get bootloader unlocked using HTCdev: http://www.htcdev.com/bootloader/
i want to flash stock rom for my htc one m7. i have an unlocked bootloader.I have read that to flash the stock ruu files(.exe) [not the .zip files], we need to lock the bootloader.Is it true?what will happen if i flash the ruu while having my bootloader unlocked?
*i dont want to relock my bootloader because i will root my phone again after having everything back to stock.i have the proper ruu file for my phone.Please do reply!
$urajM said:
i want to flash stock rom for my htc one m7. i have an unlocked bootloader.I have read that to flash the stock ruu files(.exe) [not the .zip files], we need to lock the bootloader.Is it true?what will happen if i flash the ruu while having my bootloader unlocked?
*i dont want to relock my bootloader because i will root my phone again after having everything back to stock.i have the proper ruu file for my phone.Please do reply!
Click to expand...
Click to collapse
If your phone is S-ON you must relock the BL to flash a RUU. What will happen if you don't? SImple, the RUU won't flash. Just unlock the BL again after flashing the RUU.
I forgot to mention i have s-off. Can i flash the .exe ruu with an unlocked bootloader then? I just wondered why these files dont flash with an unlocked bootloader..
alray said:
If your phone is S-ON you must relock the BL to flash a RUU. What will happen if you don't? SImple, the RUU won't flash. Just unlock the BL again after flashing the RUU.
Click to expand...
Click to collapse
I have s-off
$urajM said:
I forgot to mention i have s-off. Can i flash the .exe ruu with an unlocked bootloader then? I just wondered why these files dont flash with an unlocked bootloader..
Click to expand...
Click to collapse
If your phone is S-OFF you don't need to relock the bootloader to flash a RUU (exe or zip).
When S-On you can only flash signed file and this signature verification can only be done by your phone with a locked (or relocked) bootloader hence the requirement to relock the BL if your phone is S-ON.
alray said:
If your phone is S-OFF you don't need to relock the bootloader to flash a RUU (exe or zip).
When S-On you can only flash signed file and this signature verification can only be done by your phone with a locked (or relocked) bootloader hence the requirement to relock the BL if your phone is S-ON.
Click to expand...
Click to collapse
Thanxks ,it ihelped a lot.
By the way do i need to have a superCID to flash rom or ruu of any region or is having an unlocked botloader with s-off sufficient?
$urajM said:
By the way do i need to have a superCID to flash rom or ruu of any region or is having an unlocked botloader with s-off sufficient?
Click to expand...
Click to collapse
Both CID and MID must be compatible for the RUU. CID and MID can be changed with S-OFF.
You can also decrypt the RUU and change the android-info.txt file so it match your CID/MID
alray said:
Both CID and MID must be compatible for the RUU. CID and MID can be changed with S-OFF.
You can also decrypt the RUU and change the android-info.txt file so it match your CID/MID
Click to expand...
Click to collapse
Thanks
alray said:
If your phone is S-OFF you don't need to relock the bootloader to flash a RUU (exe or zip).
When S-On you can only flash signed file and this signature verification can only be done by your phone with a locked (or relocked) bootloader hence the requirement to relock the BL if your phone is S-ON.
Click to expand...
Click to collapse
The links you have provided for htc one m7_u ,the one for my phone is not there. My OS is 7.21.707.151.
Can you provide me link? Also my bootloader info for more info-
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA^%$&*%#04
(bootloader) imei: 354435(*&^@
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4093mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
$urajM said:
The links you have provided for htc one m7_u ,the one for my phone is not there.
Click to expand...
Click to collapse
What links? I dont remember providing you with any link.
My OS is 7.21.707.151. Can you provide me link?
Click to expand...
Click to collapse
This is the RUU for 7.21.707.151
https://androidfilehost.com/?fid=312968873555002347
Also my bootloader info for more info-
Click to expand...
Click to collapse
You said at post #4 your phone was S-OFF but your "fastboot-getvar all" output is clearly showing that your phone is S-ON. Not really a problem but you'll need to relock bootloader before flashing, just so you know.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA^%$&*%#04
(bootloader) imei: 354435(*&^@
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4093mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
alray said:
What links? I dont remember providing you with any link.
This is the RUU for 7.21.707.151
https://androidfilehost.com/?fid=312968873555002347
You said at post #4 your phone was S-OFF but your "fastboot-getvar all" output is clearly showing that your phone is S-ON. Not really a problem but you'll need to relock bootloader before flashing, just so you know.
Click to expand...
Click to collapse
The thing is in every post tat the bottom there is a tab that says says show hidden contents and there were some ruu links for htc one m7.Anyways, the thing is I brought my phone back to s-on as I was having a hard time finding the correct ruu for my phone and when you s-on the phone only the correct and latest ruu can be flushed .What I mean is that no wrong ruu can be flushed.But as soon as I s-on ed my phone ,I paniced as I was having a very hard time finding the latest ruu .So I posted the same things in both the threads in a panic which I am sorry for .I didn't know about that rule.Basiclly in this thread I wanted the latest ruu link for my phone. What I meant in the other thread was for someone to explain the version of my phone for the getvar all command so that I could identify my ruu easily.i was confused in many terms like "wwwe", .zip and .ruu. I will change my question in the other thread.
Anyways thanks for replying and giving the link.I just wanted to confirm that the link you provided will work for my indian edition ,right?Also, not that I am complaing but do you happen to know the link for the .ruu ( not the .zip) for the same? Thanks.
$urajM said:
The thing is in every post tat the bottom there is a tab that says says show hidden contents and there were some ruu links for htc one m7.
Click to expand...
Click to collapse
I Forgot about these links, they are added to all my posts automatically
Anyways, the thing is I brought my phone back to s-on as I was having a hard time finding the correct ruu for my phone and when you s-on the phone only the correct and latest ruu can be flushed .
Click to expand...
Click to collapse
I understand what you mean but it's always a bad idea to go back S-On, it can even brick your phone in the some situations (I.e going back S-On with an unsigned bootloader will brick)
Anyways thanks for replying and giving the link.I just wanted to confirm that the link you provided will work for my indian edition ,right?Also, not that I am complaing but do you happen to know the link for the .ruu ( not the .zip) for the same? Thanks.
Click to expand...
Click to collapse
This ruu is the only one that should work on your phone now that it's back S-On. If this one doesn't work, you're SOL (because S-On).
Ruu are rarely available in exe file, most of them are zip file and they must be flashed using htc_fastboot.exe from a Windows pc with the phone booted in RUU mode:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip your_ruu_file_name.zip
htc_fastboot reboot
pl don t panic. it is easy
I showed you 4.4.3 but as my idea latest build is better than old
https://forum.xda-developers.com/htc-one/development/help-selecting-correct-stock-rom-t3879097/page2
S-off
I can no longer s-off using rumrunner. I did some research and found that htc patched hboot 1.56 and above.The only solution i found is sunshine. ALso i found some posts saying that they were able to s-off by using custom roms with unsecure kernels and unsecure boot img. So just wanted to know whether they work for hboot 1.61 or do i use sunshine if i want to s-off again?
I mean is there even a slight chance that using unsecured kernels and boot imgs i can get s-off or are all of those posts lies?
$urajM said:
I can no longer s-off using rumrunner. I did some research and found that htc patched hboot 1.56 and above.The only solution i found is sunshine. ALso i found some posts saying that they were able to s-off by using custom roms with unsecure kernels and unsecure boot img. So just wanted to know whether they work for hboot 1.61 or do i use sunshine if i want to s-off again?
I mean is there even a slight chance that using unsecured kernels and boot imgs i can get s-off or are all of those posts lies?
Click to expand...
Click to collapse
You don't need s-off to flash the latest ruu version matching your cid/mid (the one linked in my last post), you only need s-off if you want to downgrade or if you want to convert your phone to another carrier/region version.
Only sunshine will hboot 1.57/1.61 security to off (s-off)
And FYI, "boot" = "kernel" these are not 2 different things