There is no ruu for my phone (02___001) so now I have s off I was going to run a stock ruu and update to the latest firmware. If I send the phone back for repair and change my cid to HTC_001 would HTC know I have changed my cid even if I s on?
Anyone help me at all?
stovie_steve said:
Anyone help me at all?
Click to expand...
Click to collapse
Two things:
1- I dont know if they keep a record of IMEI (or s/n) <--> carrier, but I think they have to and do.
2- the CID is stored in several partitions, not only the one you change with fastboot writecid.
HOWEVER, it really depends on how far they're going to dig into this, if they are going to check their IMEI database or check the different partitions on the phone, just to "prove you wrong", I guess they could.
But then again, would it be worth all that hassle for them?
I dont have any experience with repair centers or how far they would go to prove that you changed something on your phone, and it's really quite country (and HTC people) dependent; for some they have no problem with an unlocked or relocked phone, and other even have a problem with S-Off (though they can't prove the phone didn't ship that way in the first place)
Better have someone from your region (O2 so UK?) post their experience(s)
Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?
stovie_steve said:
Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?
Click to expand...
Click to collapse
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.
nkk71 said:
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.
Click to expand...
Click to collapse
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!
stovie_steve said:
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!
Click to expand...
Click to collapse
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.
nkk71 said:
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.
Click to expand...
Click to collapse
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?
stovie_steve said:
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
Click to expand...
Click to collapse
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
stovie_steve said:
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
Click to expand...
Click to collapse
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
stovie_steve said:
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?
Click to expand...
Click to collapse
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).
nkk71 said:
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).
Click to expand...
Click to collapse
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner
stovie_steve said:
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner
Click to expand...
Click to collapse
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.
nkk71 said:
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.
Click to expand...
Click to collapse
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho
stovie_steve said:
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho
Click to expand...
Click to collapse
Ok, my thoughts, in a nutshell
1. Unlock bootloader via HTC dev <- YES
2----- try rumrunner 3.62
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off <- Ok, try, if it fails use above rumrunner 3.62
Once S-Off:
--- remove tampered: revone or http://forum.xda-developers.com/showthread.php?t=2477792
5. Restore nandroid backup for my 02 version 1.28.206.7
--- set phone to LOCKED, using revone (or http://forum.xda-developers.com/showthread.php?t=2475914)
------- you will need to have SU privileges which you can get using revone or flashing SuperSU; if you do flash SuperSU, uninstall it after getting LOCKED
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match) <- Yep
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Once you have your bootloader "LOCKED", no TAMPERED, no red text on bootup, do "fastboot oem writesecureflag 3"
reboot three times and see if everything sticks, and don't take any other OTAs.
Hit me with a thanks if this was useful
So you think I shouldn't upgrade to the latest OTA once I get s on?
stovie_steve said:
So you think I shouldn't upgrade to the latest OTA once I get s on?
Click to expand...
Click to collapse
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )
nkk71 said:
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )
Click to expand...
Click to collapse
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either
stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.
nkk71 said:
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.
Click to expand...
Click to collapse
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?
stovie_steve said:
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either
Click to expand...
Click to collapse
the touchscreen drivers were part of the 2.xx firmware package, not hboot, so if you don't use a full RUU, it will break the touchscreen drivers, but you can use an OTG cable + mouse.
stovie_steve said:
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?
Click to expand...
Click to collapse
Unfortunately you can't (anymore), but this one should be close enough: http://d-h.st/users/guich/?fld_id=25920#files, or the best thing is to get a hold of the OTA 3.62.206.1 file and extract it from it.
Anyway, in my humble opinion, first things first: unlock using HTCdev and see if you can get rumrunner to S-Off on 3.62.
Related
Hi guys.
First time posting, but have used the site extensively over the past 6-8 months. I have an AT&T HTC One. I had unlocked it, s-off, rooted, installed GPe, and decided to go back. The ROM I went back to was supposed to be MY stock ROM, but it turns out it was unbranded 4.2.2. I thought nothing of it, and as of yesterday, had sold my phone on ebay. I decided to wipe my phone to get ready to ship. I locked my bootloader and went to s-on, but when I went to factory reset, I got a "security warning" and it won't reboot into recovery. I've tried everything- tried to re-unlock it with htcdev, which freezes at the bootloader. I've tried to unlock via revone, since I still have root (root checker verified this to be the case), but get the -6 error when using terminal emulator in ROM Toolbox, and get the same error when doing it via adb commands. I've tried probably 50 different things about 10 different times, and am about to pull my hair out! I've read and searched probably hundreds of threads over the past 24 hours. Trying to flash stock RUU (the exe) just freezes as well. Any help would be appreciated! Let me know what info you need from me.
Android 4.2.2
Hboot 1.44
Software number 2.24.401.8
HTC SDK API level 5.34
Kernel version 3.4.10-g28df0d6 [email protected] #1 SMP PREEMPT
Baseband version 4A.18.3263.15_10.38h.1157.04L
Build number 2.24.401.8 CL235216 release-keys
Thanks guys! Awesome community!
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
but also Read Mike 1986's Return to stock Guide before - this will ensure you are aware of what needs doing before you start to do it
http://forum.xda-developers.com/showthread.php?t=2265618
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
The search option would have found these for you and saved some time and heartache :highfive:
L0rdNels0n said:
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Click to expand...
Click to collapse
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads (every RUU I've tried fails miserably, and extracted rom.zips don't work either). It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
AndyM3 said:
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads. It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
Click to expand...
Click to collapse
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
nkk71 said:
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
Click to expand...
Click to collapse
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
nkk71 said:
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
Click to expand...
Click to collapse
I downloaded a 1.20.401 RUU (should be 4.1.2, probably), and I am on mike1986's odexed ROM right now. I'd downgrade, but how? I can't install a custom recovery.
Edit: RUU exited with a "bootloader version error". Could I have downloaded a corrupt HBOOT or something? revone gave success messages about five times now, but the bootloader still says "LOCKED" and "S-ON".
AndyM3 said:
the bootloader still says "LOCKED" and "S-OFF".
Click to expand...
Click to collapse
So S-Off achieved great.
What's still the problem?
nkk71 said:
So S-Off achieved great.
What's still the problem?
Click to expand...
Click to collapse
Typo, sorry. It's S-ON.
AndyM3 said:
Typo, sorry. It's S-ON.
Click to expand...
Click to collapse
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
nkk71 said:
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
Click to expand...
Click to collapse
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
AndyM3 said:
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
Click to expand...
Click to collapse
Sometimes a factory reset can help with the unlock token, but since you're on 1.54 now it would make little difference.
Sorry & good luck
Sent from my HTC One using xda app-developers app
Yep. I'm in exactly the same boat. Actually, I am on 1.44 HBOOT, dated May 3rd, and none of the available options worked. And yes, I've tried the links included in subsequent posts. And I'm "locked" via same way as above. Since I was selling the phone and trying to revert to stock, my only option was to manually erase everything and send it off. I couldn't do a factory reset, because it just kicked me to bootloader with a "security warning" error. Couldn't install older RUU, as it would just hang at the HTC black screen with no green progress bar.
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
Same problem
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
PlaviiCZ said:
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
Sorry for my bad english, but I hope hope you'll understand.
Click to expand...
Click to collapse
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
clsA said:
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
Click to expand...
Click to collapse
Yeah, I'm dumbass...Yes, I did, and nothing...just "failed" in cmd. Should I try again to tell you, what is in cmd exactly written?
EDIT: Please help (
No one knows anything?
Guys pls help, I need to unroot and relock my HTC One device for repair purposes.. I want to send it back to HTC Service Center and claim back the warranty to fix the camera problem. Thanks alot
[SOLVED]
Fully stock and downgraded to H-Boot 1.44 Android 4.1.2
Thanks to @nkk71
mctodd said:
Guys pls help, I need to unroot and relock my HTC One device for repair purposes.. I want to send it back to HTC Service Center and claim back the warranty to fix the camera problem. Thanks alot
Click to expand...
Click to collapse
Their are guides and even Youtube videos that give you step by step directions on how to accomplish this. Just check the threads and or Youtube
blakphoenix said:
Their are guides and even Youtube videos that give you step by step directions on how to accomplish this. Just check the threads and or Youtube
Click to expand...
Click to collapse
Thanks for the reply, but mostly in youtube where out of date..
mctodd said:
Thanks for the reply, but mostly in youtube where out of date..
Click to expand...
Click to collapse
mctodd said:
Hi nkk71, I know it's a bit annoying to have someone bothering you but seems like your the one the good guys that can patiently help some one frustrated on going back to stock (like brand new). I am having a problem on going back to stock. Here is my spec on Bootloader mode.
M7_U Htc One model
Hboot-1.54.0000
Radio-4A.17.3250.14
OpebDSP-v31.120.272.0617
OS-2.24.707.3
EMMC-boot
HTC_044
One of my problem also is i rooted it with mac and there is no unrooting instructions for mac.. Pls help if you have any idea, i just have to send it back to repair. Thanks.
P. S i am willing to pay via paypal if necessary
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (and remove IMEI and s/n before posting)
Also what ROM are you on now?
EDIT: payment will not be necessary, all I ask is if I helped you hit the thanks button
nkk71 said:
can you post a "fastboot getvar all" (and remove IMEI and s/n before posting)
Also what ROM are you on now?
EDIT: payment will not be necessary, all I ask is if I helped you hit the thanks button
Click to expand...
Click to collapse
I am not in my computer at the moment cuz im at work im just using my One, the Rom that i am using at the moment is Android Revolution HD 13.1. Is it ok to fastboot through fx app so i can send you the info..
mctodd said:
I am not in my computer at the moment cuz im at work im just using my One, the Rom that i am using at the moment is Android Revolution HD 13.1. Is it ok to fastboot through fx app so i can send you the info..
Click to expand...
Click to collapse
No worries, do it later, as I'm not on s computer either for the time being. I'll be on again later, but only for an hour or two, so it might have to wait till tomorrow anyway.
Sent from my HTC One using Tapatalk
This your firmware ? 2.24.707.3
Do you have a nandroid backup of it ?
What does it say on your bootloader ?
also, on a mac you will need to type the following before any command:
./
so ./adb devices
./fastboot devices
mctodd said:
I am not in my computer at the moment cuz im at work im just using my One, the Rom that i am using at the moment is Android Revolution HD 13.1. Is it ok to fastboot through fx app so i can send you the info..
Click to expand...
Click to collapse
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Thanks for yours patient on making this replies and research man.. i really do appreciate it.
Heres the screen shot that you requested earlier.
I am a bit confused with this OS-2.24.707.3 and build number 2.24.401.8 Which one is really my ROm version?? Any idea?
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Hi nkk71, I am confused which version of ROM that i have.. Im afraid to download it might be a wrong one.
In bootloader Mode I can see this O.S-2.24.707.3
but in settings i can see a build number 2.24.401.8 CL235216 release keys which one will i download for RUU Stock
mctodd said:
Hi nkk71, I am confused which version of ROM that i have.. Im afraid to download it might be a wrong one.
In bootloader Mode I can see this O.S-2.24.707.3
but in settings i can see a build number 2.24.401.8 CL235216 release keys which one will i download for RUU Stock
Click to expand...
Click to collapse
Bootloader shows the "more" correct version x.xx.707.x
In settings it only shows the ROM you are based on.
Go for the RUU with .707. in it.
Keep s-off for the time being, that will allow u to change in case u need to. I have to sign off for today...
Sent from my HTC One using Tapatalk
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
nkk71 said:
Bootloader shows the "more" correct version x.xx.707.x
In settings it only shows the ROM you are based on.
Go for the RUU with .707. in it.
Keep s-off for the time being, that will allow u to change in case u need to. I have to sign off for today...
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks alot man.. Your such a help..
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Hi nkk71, is it possible to flash the ruu that you linked above to back to stock so i'll be able to run rumrunner S-off.. Cuz i tried in ARHD 13.1 didnt work after 8 pouring it says "please wait 30 seconds and run rumrunner again,press enter to exit" I had multiple attempts already and never worked..
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Hi there nkk71, did you see my new THREAD?? Pls help me man im in big trouble now. cannot flash a rom. Even though its successfully installed keeps bringing me back to recovery. thanks in advance
mctodd said:
Hi there nkk71, did you see my new THREAD?? Pls help me man im in big trouble now. cannot flash a rom. Even though its successfully installed keeps bringing me back to recovery. thanks in advance
Click to expand...
Click to collapse
I'll get back to u in an hour or two...
Sent from my HTC One using Tapatalk
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
At number 4. Did mean that i have to manually downgrade or it is automatic??
mctodd said:
At number 4. Did mean that i have to manually downgrade or it is automatic??
Click to expand...
Click to collapse
It's automatic. If there's an error let me know
Keep S-Off !!
nkk71 said:
It's automatic. If there's an error let me know
Keep S-Off !!
Click to expand...
Click to collapse
I did run the RUU 2.26.707.5, it didnt succeed..I says wrong MID..!!Could i change MID since im S-Off at the moment? but my bootloader is already locked.
mctodd said:
I did run the RUU 2.26.707.5, it didnt succeed..I says wrong MID..!!Could i change MID since im S-Off at the moment? but my bootloader is already locked.
Click to expand...
Click to collapse
my bad, didnt check your MID, anyway instead of changing it download this: http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
for simplicity, rename the file to "ruu.zip" and place it in your adb folder.
it's a RUU zip file not exe, so you need to flash it:
so get to bootloader/FASTBOOT USB (either using "adb reboot bootloader" or POWER + VOLDOWN buttons)
then:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes twice, the first time it will come back with "failed flush again", the second time it should report success
fastboot reboot-bootloader
fastboot getvar all <- to confirm it downgraded
nkk71 said:
my bad, didnt check your MID, anyway instead of changing it download this: http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
for simplicity, rename the file to "ruu.zip" and place it in your adb folder.
it's a RUU zip file not exe, so you need to flash it:
so get to bootloader/FASTBOOT USB (either using "adb reboot bootloader" or POWER + VOLDOWN buttons)
then:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes twice, the first time it will come back with "failed flush again", the second time it should report success
fastboot reboot-bootloader
fastboot getvar all <- to confirm it downgraded
Click to expand...
Click to collapse
Once it succeeded it is ready for service repair to claim warranty? Thanks
Hello everyone,
This is my fisrt time writing in this forum, hope you guys can share some knowledge with me. Here is my issue:
I bought a HTC One to a guy a few weeks ago with barely no use. The thing is that I didn´t know at that time that the device was rooted with the MaximusHD. When I realized about it I reset my phone to factory settings and the new 4.3 3.22.1540.1 got installed. Thought it was ok but it is still doing some weird things so I decided to unroot the device to stock, also for warranty porpuses.
The problem comes when I try to download the RUU for my device due to I cannot find it. Should I do it through other method? Do I have to S-off to downgrade and install the RUU 1.29?
My phone is the following:
M7_UL PVT Ship S-On RH
Baseband 4A.17.3250.14
Hboot 1.54.0000
OpenDSP v31.120.274.0617
It is the european unlocked/international version bought in Spain.
I would really appreciate if someone could give a hand on this and guide me in through this process. I was an iPhone guy and now I'm freaking lost.
Thanks so much!
kikinhorap said:
Hello everyone,
This is my fisrt time writing in this forum, hope you guys can share some knowledge with me. Here is my issue:
I bought a HTC One to a guy a few weeks ago with barely no use. The thing is that I didn´t know at that time that the device was rooted with the MaximusHD. When I realized about it I reset my phone to factory settings and the new 4.3 3.22.1540.1 got installed. Thought it was ok but it is still doing some weird things so I decided to unroot the device to stock, also for warranty porpuses.
The problem comes when I try to download the RUU for my device due to I cannot find it. Should I do it through other method? Do I have to S-off to downgrade and install the RUU 1.29?
My phone is the following:
M7_UL PVT Ship S-On RH
Baseband 4A.17.3250.14
Hboot 1.54.0000
OpenDSP v31.120.274.0617
It is the european unlocked/international version bought in Spain.
I would really appreciate if someone could give a hand on this and guide me in through this process. I was an iPhone guy and now I'm freaking lost.
Thanks so much!
Click to expand...
Click to collapse
Your bootloader should already be unlocked, so simply get S-OFF using Rumrunner, then follow this guide.
Answer
attanasi0 said:
Your bootloader should already be unlocked, so simply get S-OFF using Rumrunner, then follow this guide.
Click to expand...
Click to collapse
Thanks for the reply. I've tried to s-off my htc but it hasnt worked. So I downloaded the recovery stock version and after installing it, the device told me that my phone doesnt appear to be rooted and if i wanted to install supersu, i declined and then made a recovery. Phone looks like unrooted, although within the bootloader it still shows "tampered" and "Unlocked". The recovery mode that the phone had installed has disappeared so I dont know what to do now, should I continue to s-off the device and then put it down to hboot 1.44 and follow the unroot guide???
I would like to make sure my device is unrooted in order to gain warranty privilages just in case i need to send out my phone to htc...
Thanks!
kikinhorap said:
Thanks for the reply. I've tried to s-off my htc but it hasnt worked. So I downloaded the recovery stock version and after installing it, the device told me that my phone doesnt appear to be rooted and if i wanted to install supersu, i declined and then made a recovery. Phone looks like unrooted, although within the bootloader it still shows "tampered" and "Unlocked". The recovery mode that the phone had installed has disappeared so I dont know what to do now, should I continue to s-off the device and then put it down to hboot 1.44 and follow the unroot guide???
I would like to make sure my device is unrooted in order to gain warranty privilages just in case i need to send out my phone to htc...
Thanks!
Click to expand...
Click to collapse
You don't really have a choice, unless you have the RUU for your phone. Can you post the results of "fastboot getvar all" so we can try to figure out what to do.
A
attanasi0 said:
You don't really have a choice, unless you have the RUU for your phone. Can you post the results of "fastboot getvar all" so we can try to figure out what to do.
Click to expand...
Click to collapse
I've attached the results in a jpg file. The only thing that has changed is the baseband...it went up to 4A.20.3263.16
kikinhorap said:
I've attached the results in a jpg file. The only thing that has changed is the baseband...it went up to 4A.20.3263.16
Click to expand...
Click to collapse
Just a quick note here, "version-main: <blank>" I never like that.
BTW, when posting "fastboot getvar all" it's preferably to remove IMEI and s/n; we don't need to see that.
You should probably get s-off as @attanasi0 suggested and then run a "HTC__304" downgrade RUU. (You can only downgrade if you're S-Off)
Just my two cents
nkk71 said:
Just a quick note here, "version-main: <blank>" I never like that.
BTW, when posting "fastboot getvar all" it's preferably to remove IMEI and s/n; we don't need to see that.
You should probably get s-off as @attanasi0 suggested and then run a "HTC__304" downgrade RUU. (You can only downgrade if you're S-Off)
Just my two cents
Click to expand...
Click to collapse
Im sorry about the pic, I'll edit my msg later. Im trying to s-off but it fails everytime. Dunno what to try now...
In regards to the "version main", I tried lots of times but it was blank all of them, dunno why. Some of you guys know what the reason could be?
kikinhorap said:
Im sorry about the pic, I'll edit my msg later. Im trying to s-off but it fails everytime. Dunno what to try now...
In regards to the "version main", I tried lots of times but it was blank all of them, dunno why. Some of you guys know what the reason could be?
Click to expand...
Click to collapse
When you boot to bootloader does it also show nothing in OS (7th line down or so)? Can you remember the last OTA you took?
nkk71 said:
When you boot to bootloader does it also show nothing in OS (7th line down or so)? Can you remember the last OTA you took?
Click to expand...
Click to collapse
Right, it shows just OS- but nothing else...when i bought it the guy had installed the MaximusHD 13 and I updated through OTA to the MaximusHD 20 but wasnt going smooth so I reset it to factory settings and It installed the JB 4.3 (3.22.1540.1).
Today after trying to s-off without success, I downloaded the recovery stock version for the rom I had and flashed it and the recovery mode that I had before disappeared and the baseband upgraded to 4A.20...instead of the 4A.17 that I had before that. Did the guy who sold me the htc messed it up? is there anything I can do to set my device to factory settings?
Thanks for the help guys! I appreciate it!
kikinhorap said:
Right, it shows just OS- but nothing else...when i bought it the guy had installed the MaximusHD 13 and I updated through OTA to the MaximusHD 20 but wasnt going smooth so I reset it to factory settings and It installed the JB 4.3 (3.22.1540.1).
Today after trying to s-off without success, I downloaded the recovery stock version for the rom I had and flashed it and the recovery mode that I had before disappeared and the baseband upgraded to 4A.20...instead of the 4A.17 that I had before that. Did the guy who sold me the htc messed it up? is there anything I can do to set my device to factory settings?
Thanks for the help guys! I appreciate it!
Click to expand...
Click to collapse
Well from the information available, you have
- hboot 1.54
- m7_ul
- PN0710000
- CID HTC__304
this would lead me to assume you have a 2.24.401.x based phone.
I would try to get one of the following Guru Reset ROM:
2.24.401.8 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
2.24.401.1 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
flash one of them in recovery, then follow the rumrunner steps to try to achieve S-Off.
If that is successful, then you can downgrade back to stock, using this RUU (exe): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
check your "fastboot getvar all" after that.
Once you've done all that you can use revone (or http://forum.xda-developers.com/showthread.php?t=2477792) to remove "TAMPERED"
and also revone (or http://forum.xda-developers.com/showthread.php?t=2475914) to get you're phone "LOCKED" if you so wish
Keep S-Off !!
PS: hit the thanks button if someone has helped you
Awaiting your feedback
nkk71 said:
Well from the information available, you have
- hboot 1.54
- m7_ul
- PN0710000
- CID HTC__304
this would lead me to assume you have a 2.24.401.x based phone.
I would try to get one of the following Guru Reset ROM:
2.24.401.8 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
2.24.401.1 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
flash one of them in recovery, then follow the rumrunner steps to try to achieve S-Off.
If that is successful, then you can downgrade back to stock, using this RUU (exe): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
check your "fastboot getvar all" after that.
Once you've done all that you can use revone (or http://forum.xda-developers.com/showthread.php?t=2477792) to remove "TAMPERED"
and also revone (or http://forum.xda-developers.com/showthread.php?t=2475914) to get you're phone "LOCKED" if you so wish
Keep S-Off !!
PS: hit the thanks button if someone has helped you
Awaiting your feedback
Click to expand...
Click to collapse
Thanks for the help. I have downloaded the Rom you gave me the link for but I dunno how to flash it due to I lost access to the teamwin recovery mode and when I click recovery onto the bootloader it goes to a black screen with a caution simbol in red and I have to reboot it.
I have tried with the goomanager to flash that rom but it doesnt let me. Any advice in this regard? I can tell goomanager to find an open recovery script (openrecovery-twrp-2.6.1.0-m7.img), should i do this? Or Im gonna end up with a bricked phone?
Thanks!
kikinhorap said:
Thanks for the help. I have downloaded the Rom you gave me the link for but I dunno how to flash it due to I lost access to the teamwin recovery mode and when I click recovery onto the bootloader it goes to a black screen with a caution simbol in red and I have to reboot it.
I have tried with the goomanager to flash that rom but it doesnt let me. Any advice in this regard? I can tell goomanager to find an open recovery script (openrecovery-twrp-2.6.1.0-m7.img), should i do this? Or Im gonna end up with a bricked phone?
Thanks!
Click to expand...
Click to collapse
"black screen with a caution simbol in red" that's stock recovery, you need to flash back a custom recovery. download (if you dont have one) from the xda threads, then enter bootloader (shut off phone, hold POWER + VOLDOWN) enter FASTBOOT, connect to PC and it should change to FASTBOOT USB
then
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
then "install ZIP" in Aroma, deselect "stock recovery" so you don't need to flash it again.
nkk71 said:
"black screen with a caution simbol in red" that's stock recovery, you need to flash back a custom recovery. download (if you dont have one) from the xda threads, then enter bootloader (shut off phone, hold POWER + VOLDOWN) enter FASTBOOT, connect to PC and it should change to FASTBOOT USB
then
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
then "install ZIP" in Aroma, deselect "stock recovery" so you don't need to flash it again.
Click to expand...
Click to collapse
Is the one I posted it before (openrecovery-twpr-2.6....img) ok? or should I install a different one?
Thanks for the help man, I would be even more lost than Im now without your help!
kikinhorap said:
Is the one I posted it before (openrecovery-twpr-2.6....img) ok? or should I install a different one?
Thanks for the help man, I would be even more lost than Im now without your help!
Click to expand...
Click to collapse
No problem, TWRP you mentioned should work just fine. It's the same as installing a custom ROM. I havent used TWRP but it should say something like "install zip", then find the zip and flash away.
Hopefully, that will give you a chance to successfully run rumrunner; remember to read and follow the instructions to the letter!
Good luck and keep us posted (fingers crossed)
nkk71 said:
No problem, TWRP you mentioned should work just fine. It's the same as installing a custom ROM. I havent used TWRP but it should say something like "install zip", then find the zip and flash away.
Hopefully, that will give you a chance to successfully run rumrunner; remember to read and follow the instructions to the letter!
Good luck and keep us posted (fingers crossed)
Click to expand...
Click to collapse
Well I installed the custom recovery, then flashed the stock rom 2.24.401.8 as you told me. Once I did that I ran rumrunner successfully gainning S-off.
Now I have to run the RUU but the one you suggested me is the "RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878" but my radio is 4A.17.3250.14_10.39.1150.04L. Should I try to install it anyways? I've taken a look at the rest of RUUs and none fits my features...
btw every time I flash the stock version at the end it tells me that my phone doesnt appear to be rooted and if i want to install supersu, i always say no and after that my recovery always goes to stock, i guess it is normal, isnt it?
kikinhorap said:
Well I installed the custom recovery, then flashed the stock rom 2.24.401.8 as you told me. Once I did that I ran rumrunner successfully gainning S-off.
Click to expand...
Click to collapse
Excellent :good:
kikinhorap said:
btw every time I flash the stock version at the end it tells me that my phone doesnt appear to be rooted and if i want to install supersu, i always say no and after that my recovery always goes to stock, i guess it is normal, isnt it?
Click to expand...
Click to collapse
That's normal, dont worry about it.
kikinhorap said:
Now I have to run the RUU but the one you suggested me is the "RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878" but my radio is 4A.17.3250.14_10.39.1150.04L. Should I try to install it anyways? I've taken a look at the rest of RUUs and none fits my features...
Click to expand...
Click to collapse
Go ahead and flash it, it will downgrade everything (now possible thanks to S-Off), and you will then receive the latest OTA package(s) to get to the most current version including radio.
nkk71 said:
Excellent :good:
That's normal, dont worry about it.
Go ahead and flash it, it will downgrade everything (now possible thanks to S-Off), and you will then receive the latest OTA package(s) to get to the most current version including radio.
Click to expand...
Click to collapse
Done!!!!! Sweet!! it worked just fine! Tampered disappeared and bootloader only shows unlocked. I have to relock it, havent I? That wouldnt mess up with my carrier right? It is just for locking the bootloader, isnt it?
Well many many thanks for your help, I couldnt have done it without it and I have learnt so much through the process Soon I'll be ready to re-root the phone again and try some custom roms hehe
Peace and greetings from Spain!
kikinhorap said:
Done!!!!! Sweet!! it worked just fine! Tampered disappeared and bootloader only shows unlocked. I have to relock it, havent I? That wouldnt mess up with my carrier right? It is just for locking the bootloader, isnt it?
Well many many thanks for your help, I couldnt have done it without it and I have learnt so much through the process Soon I'll be ready to re-root the phone again and try some custom roms hehe
Peace and greetings from Spain!
Click to expand...
Click to collapse
you should set it to LOCKED not RELOCKED using revone or http://forum.xda-developers.com/showthread.php?t=2475914
keep S-Off !!
anyway, don't why anybody would want to be on stock ROM
nkk71 said:
you should set it to LOCKED not RELOCKED using revone or http://forum.xda-developers.com/showthread.php?t=2475914
keep S-Off !!
anyway, don't why anybody would want to be on stock ROM
Click to expand...
Click to collapse
Hey! I have tried to lock it but after typing adb shell I get this "[email protected]:\ $" instead of the # that you are getting. I've tried to type "su" after that but it says that the command cannot be found. Also, when I type the code "echo -ne..." it says that I have permission denied so dunno what to do now...
Im asking in the lock/unlock threat but they just told me that its because im not rooted and that i have to install a recovery and install superuser in order to be able to introduce the code, dont really understand why I have to root it afer unrooted it :S
kikinhorap said:
Hey! I have tried to lock it but after typing adb shell I get this "[email protected]:\ $" instead of the # that you are getting. I've tried to type "su" after that but it says that the command cannot be found. Also, when I type the code "echo -ne..." it says that I have permission denied so dunno what to do now...
Im asking in the lock/unlock threat but they just told me that its because im not rooted and that i have to install a recovery and install superuser in order to be able to introduce the code, dont really understand why I have to root it afer unrooted it :S
Click to expand...
Click to collapse
You should have LOCKED it before running the RUU, because that's what made you loose root.
So before proceeding, can you give me an update of your status:
bootloader: locked/relocked/unlocked?
tampered?
ROM?
"fastboot getvar all" (remove IMEI and s/n)
Hello,
probably silly question and you will order me to study xda.
Unfortunately, i have came through almost every single topic, and can't get to "move" from my situation.
I received Htc One with Hboot v 1.54.000, locked bootloader - S-ON.
Software number 2.24.111.5 (android 4.2.2 with Sense 5). My cid (read through CidGetter from playstore) - T-MOB101.
I am trying to avoid unlocking bootloader via htc-dev, as afaik it voids the warranty.
I am not interested in custom roms. Rather, i would like to "fool" the phone and make it like it was European distribution, with no branding, so i would receive OTA as anyone else with unbranded phone.
If i understood correctly, to achieve this, basically i need to change my CID to european or supercid, which will enable to install any ruu from htc. But european otas would be enough for me. To change cid, i need S-OFF, right ?
There are basically three methods, if i read correctly, right ?
1, Revone - doesn't work with Hboot 1.54
2, Moonshine - Works without htc-dev unlocking, but installs custom bootloader, which will disable otas to install.
3, Rumrunner - Works with 1.54 bootloader, but i need to htc dev unlock ?
So, am i understanding correctly, that as long as i dont want to htc dev unlock, i am stuck to my cid, and dependent from german t-mobile ? So i can only hope, some dev will find exploit in Hboot 1.54 ?
Isn't there any miracle, that could help to solve my problem ?
Thanks
Rumrunners is the only solution with an htc dev unlock...
If you will remove the cid and put an european is the best thing to do.
You can always put the locked string
Yes,
but Htc will know, that i requested unlock keys.
Won't be that problem ?
Also, does htc-dev unlock automatically mean warranty void ?
remusator said:
Yes,
but Htc will know, that i requested unlock keys.
Won't be that problem ?
Also, does htc-dev unlock automatically mean warranty void ?
Click to expand...
Click to collapse
Yeah, i know that htc will know, but i never had a problem.
When i had the Evo 3D i unlocked with htcdev and after s-offed, so i relocked and s-on for warranty e no prob
MY friends with this phone didn't had any problem with warranty also with an unlocked with htcdev...
Remusator - I'm looking for the same thing: I have UK orange firmware, and was hoping to get stock/unbranded CID so I can get regular OTAs. Please let me know if you figure it out
Desperately waiting and hoping for some dev to soff without dev.
Today an arcticle came through my hands, saying "Unlocked htc one - kitkat till end of the month". Still don't have even Jelly :/
Is someone working on this ? Please
Guich said:
Yeah, i know that htc will know, but i never had a problem.
When i had the Evo 3D i unlocked with htcdev and after s-offed, so i relocked and s-on for warranty e no prob
MY friends with this phone didn't had any problem with warranty also with an unlocked with htcdev...
Click to expand...
Click to collapse
Hello, thanks for answer. :good:
If i agree to unlock my bootloader, could i achieve things mentioned in first post ?
Could you please give me some more detailed guide (alternatively steps with topic links), which i need to proceed ?
Al i need is to fool the phone to think, that it's unlocked and receive ota's like any other european unlocked htc one.
Thanks
remusator said:
Hello, thanks for answer. :good:
If i agree to unlock my bootloader, could i achieve things mentioned in first post ?
Could you please give me some more detailed guide (alternatively steps with topic links), which i need to proceed ?
Al i need is to fool the phone to think, that it's unlocked and receive ota's like any other european unlocked htc one.
Thanks
Click to expand...
Click to collapse
OK, European unbranded:
1- get s-off: http://rumrunner.us/ (follow instructions !)
2- change CID to European unbranded such as HTC__001
fastboot oem writecid HTC__001 <- two underscores
3- I assume your model number (MID) is already PN0710000
4- remove TAMPERED, and set your phone back to LOCKED, you can use this tool from within CWM recovery: http://forum.xda-developers.com/showthread.php?t=2527194
5- Run the following RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
after the above, your phone will not be fooled into thinking it's European unbranded, it will be European unbranded, and you'll receive the OTAs.
Let me know if you need more explanations, and hit the thanks button if I've helped
Hello, thanks.
However, i am completely stock. So i don't have CWM recovery yet.
In which step will i get it ? Or am i missing something ?
Also, CID change - is it really so easy ? I have seen some guides where people needed to download, edit and then flash some hex files.
remusator said:
Hello, thanks.
However, i am completely stock. So i don't have CWM recovery yet.
In which step will i get it ? Or am i missing something ?
Also, CID change - is it really so easy ? I have seen some guides where people needed to download, edit and then flash some hex files.
Click to expand...
Click to collapse
OK, so before point 1 above:
a) use HTCdev to unlock
b) download CWM http://forum.xda-developers.com/showthread.php?t=2173863 and flash it in bootloader/FASTBOOT USB:
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
--> enter recovery
c) for rumrunner to work, you need a close to stock rom with root access, so get one from here: http://www.htc1guru.com/downloads/stock-rom-downloads/, probably this one should work: http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/
you need to push that to your phone:
adb push <name of rom>.zip /data/media/ <- this will take 5 to 10 minutes without any progress bar, then report success
d) in CWM recovery, now select "install zip" -> "choose zip" and flash the rom
If you're using the Guru Reset ROM, then select WIPE, select ROOT, unselect "stock recovery"
and then proceed to rumrunner
"Also, CID change - is it really so easy ?" <- yes with S-off, it is easy, and you wont have any hex-editing to do, now or in future OTAs
Hit the thanks button if i've helped
Thanks, and what will be my phone status after this procedure ?
What hboot version, son/soff, unlocked/locked.
And what recovery ? Original, or cwm ?
remusator said:
Thanks, and what will be my phone status after this procedure ?
What hboot version, son/soff, unlocked/locked.
And what recovery ? Original, or cwm ?
Click to expand...
Click to collapse
the phone will be unTAMPERED, LOCKED (not relocked), 100% out-of-the box European unbranded, HTC Sense 5 ROM v1.28.401.7, but you'll receive OTAs up to 4.3 I think.
recovery will be stock recovery not CWM, so you can receive OTA
The phone will remain S-Off, and I suggest keeping it, if YOU INSIST on going S-On you can do so after running the RUU, but before taking any OTAs, by using "fastboot oem writesecureflag 3"
nkk71 said:
the phone will be unTAMPERED, LOCKED (not relocked), 100% out-of-the box European unbranded, HTC Sense 5 ROM v1.28.401.7, but you'll receive OTAs up to 4.3 I think.
recovery will be stock recovery not CWM, so you can receive OTA
The phone will remain S-Off, and I suggest keeping it, if YOU INSIST on going S-On you can do so after running the RUU, but before taking any OTAs, by using "fastboot oem writesecureflag 3"
Click to expand...
Click to collapse
Ok, just to make sure.
When will be CWM recovery replaced with original one ? After running RUU ?
I definitely don't insist on S-ON. My warranty will be void anyways because of htc-dev unlock. And in case my phone would break down, i need S-OFF to restore everything to original.
Are there any security risks when i'm S-OFF ? Such as malware android applications etc ? As i have understood, no.
Can / should i take some full backup of my original rom, device, bootloader, recovery in case that something goes totally wrong ?
Many many thanks
What you gave me here is most complete tutorial imho
remusator said:
Ok, just to make sure.
When will be CWM recovery replaced with original one ? After running RUU ?
Click to expand...
Click to collapse
Exactly after running the RUU.exe it will restore EVERYTHING back to stock: hboot, recovery, firmware, kernel, ROM, radio
remusator said:
I definitely don't insist on S-ON. My warranty will be void anyways because of htc-dev unlock. And in case my phone would break down, i need S-OFF to restore everything to original.
Click to expand...
Click to collapse
I don't know much about warranty and what IS and IS NOT allowed, every users experience seems different, just read one today: he sent it s-off, rooted, custom rom, etc. but the blown speakers were fixed, and no questions asked.
remusator said:
Are there any security risks when i'm S-OFF ? Such as malware android applications etc ? As i have understood, no.
Click to expand...
Click to collapse
No security issues whatsoever, S-Off will only allow you to write to certain partitions you can't with S-On. The ROM (Android 4.x.x) is responsible for the malware etc.
remusator said:
Can / should i take some full backup of my original rom, device, bootloader, recovery in case that something goes totally wrong ?
Click to expand...
Click to collapse
Sure, backups are always good.
And I just checked, there's also a Guru Reset here: http://www.htc1guru.com/downloads/stock-rom-downloads/ (not your version but close enough)
And there are a couple of nandroids around as well.
remusator said:
Many many thanks
What you gave me here is most complete tutorial imho
Click to expand...
Click to collapse
You're welcome, you can always press that little THANKS button to say I was helpful
I will definitely give you thx-es
One last question.
Do i need the root ? Do i need root for rumrunner to work ?
Can't I just insted running programs from htcguru use these commands ?
http://forum.xda-developers.com/showthread.php?t=2477792 ?
Will it be the same ?
Aand how can i make full backup of whole phone ? Without installing CWM recovery and then nandroid.
remusator said:
I will definitely give you thx-es
One last question.
Do i need the root ? Do i need root for rumrunner to work ?
Can't I just insted running programs from htcguru use these commands ?
http://forum.xda-developers.com/showthread.php?t=2477792 ?
Will it be the same ?
Aand how can i make full backup of whole phone ? Without installing CWM recovery and then nandroid.
Click to expand...
Click to collapse
Yeah, su is required for rumrunner.
Yes, htcguru file use that command.
After the flash of recovery, a nandroid will backup only the OS.
For the sd you've to copy it into your pc.
remusator said:
I will definitely give you thx-es
One last question.
Do i need the root ? Do i need root for rumrunner to work ?
Can't I just insted running programs from htcguru use these commands ?
http://forum.xda-developers.com/showthread.php?t=2477792 ?
Will it be the same ?
Aand how can i make full backup of whole phone ? Without installing CWM recovery and then nandroid.
Click to expand...
Click to collapse
Guich said:
Yeah, su is required for rumrunner.
Yes, htcguru file use that command.
After the flash of recovery, a nandroid will backup only the OS.
For the sd you've to copy it into your pc.
Click to expand...
Click to collapse
Guich beat me to it
1- Yes you need root
2- the link you provided only works if you are S-Off already
3- backup everything to PC (pics, music, etc)
4- use Call Logs Backup & Restore and SMS Backup & Restore if you need them (free apps in Play Store)
5- use Helium for apps+data, since you can't use Titanium
6- backup ROM using nandroid
7- dont worry too much about the nandroid, there are ones on @crushalots site
nkk71 said:
--> enter recovery
c) for rumrunner to work, you need a close to stock rom with root access, so get one from here: http://www.htc1guru.com/downloads/stock-rom-downloads/, probably this one should work: http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/
you need to push that to your phone:
adb push <name of rom>.zip /data/media/ <- this will take 5 to 10 minutes without any progress bar, then report success
Click to expand...
Click to collapse
Hello, i cannot get through this point. I have installed HTC Sync, then uninstalled, so only drivers remained on my system.
I can use adb when the phone is normally booted, but then i don't have permission to write to that location.
When i reboot to recovery, adb devices shows empty list. Also that funny thing in windows taskbar starts spinning, finds "One", but fail to install driver.
Update1:
Ok, i managed to update adb driver to Android one. (http://forum.xda-developers.com/showthread.php?t=1830108 device manager section)
Now i'm at next step. I pushed zip to /data/media/, but after choosing install zip, there is none on sdcard.
Trying to push that again.
Update2:
File appeared after second push. Installing right now. Hope phone will wake after this procedure. Fingers crossed, holding breath.
Update3
Ok, i flashed RUU, everything is fine until now.
Slovak language / Slovakia as location is missing. Should / can i change my CID for something and install corresponding RUU for that CID, so i would have Slovak Language ? I also get red text saying "THIS IS TEST DEVICE...."
I think, the correct CID for my region is HTC__032 - East Europe
What is the language dependent on ? Because the same RUU you recommended for me is also for HTC__032. Is the file same and languages are allowed based on CID, or how does this work ?
Also HTC_001 is in the first wave of updates ?
Thanks
delete pls
remusator said:
Hello, i cannot get through this point. I have installed HTC Sync, then uninstalled, so only drivers remained on my system.
I can use adb when the phone is normally booted, but then i don't have permission to write to that location.
When i reboot to recovery, adb devices shows empty list. Also that funny thing in windows taskbar starts spinning, finds "One", but fail to install driver.
Update1:
Ok, i managed to update adb driver to Android one. (http://forum.xda-developers.com/showthread.php?t=1830108 device manager section)
Now i'm at next step. I pushed zip to /data/media/, but after choosing install zip, there is none on sdcard.
Trying to push that again.
Update2:
File appeared after second push. Installing right now. Hope phone will wake after this procedure. Fingers crossed, holding breath.
Update3
Ok, i flashed RUU, everything is fine until now.
Slovak language / Slovakia as location is missing. Should / can i change my CID for something and install corresponding RUU for that CID, so i would have Slovak Language ? I also get red text saying "THIS IS TEST DEVICE...."
I think, the correct CID for my region is HTC_032 - East Europe
Click to expand...
Click to collapse
Been gone for a while, so what's your status now? How far did you get.
Alright, I've been through thread after thread and plenty of pages found on google.
Some say to Lock the bootloader BEFORE using the RUU and some say to lock it AFTER or you'll brick the phone?
I've got a T-mobile Variant of the HTC one M7 It's rooted, SuperCID and obviously the bootloader is unlocked.... I think it's on 1.55, not exactly sure, I'm currently backing up all my data.
I've got the new 5.14.531.1 RUU straight from the HTC website.
Since it's a Tmobile rom, I'm guessing resetting the CID to T-MOB010 before installing would be a good idea?
And what of the bootloader? running the RUU should install the new Hboot correct? from there I would just need to relock it or am I not understanding this?
~Out of all my phones I've NEVER returned one to stock, so this is all kinda new to me.
Vonrottes said:
I've got the new 5.14.531.1 RUU straight from the HTC website.
Click to expand...
Click to collapse
SuperCID means you're S-Off, so no need to lock/relock bootloader, but where did you get that RUU from? link please, cause I don't think it's an RUU (how big is the file??)
nkk71 said:
SuperCID means you're S-Off, so no need to lock/relock bootloader, but where did you get that RUU from? link please, cause I don't think it's an RUU (how big is the file??)
Click to expand...
Click to collapse
Doesn't exactly answer the question... I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
Also the link, right from HTC
http://dl3.htc.com/application/RUU_M7UL_TMOUS_5.14.531.1_With Partial.exe
it's a whooping 1.49GB
Vonrottes said:
Doesn't exactly answer the question... I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
Also the link, right from HTC
http://dl3.htc.com/application/RUU_M7UL_TMOUS_5.14.531.1_With Partial.exe
it's a whooping 1.49GB
Click to expand...
Click to collapse
ah ok, 1.49GB sounds good for an RUU
and to answer your question differently, if you are S-Off, then you do not need to lock/relock bootloader; the RUU should work fine with unlocked bootloader
refer to "Not so FAQ #2": http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
and remember to stay S-Off
nkk71 said:
ah ok, 1.49GB sounds good for an RUU
and to answer your question differently, if you are S-Off, then you do not need to lock/relock bootloader; the RUU should work fine with unlocked bootloader
refer to "Not so FAQ #2": http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
and remember to stay S-Off
Click to expand...
Click to collapse
Jolly good, I didn't even see that Not so FAQ.
So basically I just run the RUU according to the instructions on the HTC page ( http://www.htc.com/us/support/news.aspx?p_id=630&p_name=htc-one-t-mobile ) and I should be good?
Vonrottes said:
Jolly good, I didn't even see that Not so FAQ.
So basically I just run the RUU according to the instructions on the HTC page ( http://www.htc.com/us/support/news.aspx?p_id=630&p_name=htc-one-t-mobile ) and I should be good?
Click to expand...
Click to collapse
hmm, i can't seem to be able open that web page, but if the file is a full RUU (I'm downloading it, but with my connection it's gonna take quite a while), then hook up the phone, and run the RUU and all should be good.
Remember an RUU will fully wipe your phone (including sdcard/internal storage), and if for whatever reason you want to change bootloader to the original LOCKED (not relocked),
you can use this tool: http://forum.xda-developers.com/showthread.php?t=2527194
(though I don't see any reason to do it )
as long as you stay S-Off, you can easily get it unlocked again anytime
out of curiosity, any particular reason you're doing this?
nkk71 said:
hmm, i can't seem to be able open that web page, but if the file is a full RUU (I'm downloading it, but with my connection it's gonna take quite a while), then hook up the phone, and run the RUU and all should be good.
Remember an RUU will fully wipe your phone (including sdcard/internal storage), and if for whatever reason you want to change bootloader to the original LOCKED (not relocked),
you can use this tool: http://forum.xda-developers.com/showthread.php?t=2527194
(though I don't see any reason to do it )
as long as you stay S-Off, you can easily get it unlocked again anytime
out of curiosity, any particular reason you're doing this?
Click to expand...
Click to collapse
I know, that's why I'm currently backing up everything important on Google Drive.
I was just looking at Scotty1223's threads with the ADB commands to remove tampered flag and reset locked.
and like I said in my second post
I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
So to go back stock with no need to ever unlock or root again,
I'll be fine LOCKING the bootloader and resetting the CID to T-MOB010 Before running the RUU?
Vonrottes said:
I know, that's why I'm currently backing up everything important on Google Drive.
I was just looking at Scotty1223's threads with the ADB commands to remove tampered flag and reset locked.
and like I said in my second post
I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
So to go back stock with no need to ever unlock or root again,
I'll be fine LOCKING the bootloader and resetting the CID to T-MOB010 Before running the RUU?
Click to expand...
Click to collapse
I understood the part about upgrading your phone, but seeing your signature, you're running a custom ROM and kernel, so i'm not clear what you mean by upgrading
Anyway, if you are going back to stock, here's what I personally would do:
1- stay S-OFF
2- change CID back to original
3- remove TAMPERED and set LOCKED (using scotty1223's commands, or the Guru Bootloader Reset tool) not because it's necessary, just aesthetically more stock
4- run the RUU
5- stay S-OFF
nkk71 said:
I understood the part about upgrading your phone, but seeing your signature, you're running a custom ROM and kernel, so i'm not clear what you mean by upgrading
Anyway, if you are going back to stock, here's what I personally would do:
1- stay S-OFF
2- change CID back to original
3- remove TAMPERED and set LOCKED (using scotty1223's commands, or the Guru Bootloader Reset tool) not because it's necessary, just aesthetically more stock
4- run the RUU
5- stay S-OFF
Click to expand...
Click to collapse
Upgrading as in:
http://www.t-mobile.com/phone-upgrade.html
To get an HTC One M8 I have turn in my Current M7... Which has to be stock...as far as the T-mobile store tech needs to know.... I guess?
Vonrottes said:
Upgrading as in:
http://www.t-mobile.com/phone-upgrade.html
To get an HTC One M8 I have turn in my Current M7... Which has to be stock...as far as the T-mobile store tech needs to know.... I guess?
Click to expand...
Click to collapse
gotcha :good:
that's a completely different kind of upgrade, i thought you meant software
Do they care about S-OFF?? because if you intend on going S-ON, then I would highly recommend a 1.xx ruu, nothing higher.
because going from S-Off to S-On on hboot 1.55+, has been known to trigger "tamper detected - rebooting" and TAMPERED is back in bootloader screen.
nkk71 said:
gotcha :good:
that's a completely different kind of upgrade, i thought you meant software
Do they care about S-OFF?? because if you intend on going S-ON, then I would highly recommend a 1.xx ruu, nothing higher.
because going from S-Off to S-On on hboot 1.55+, has been known to trigger "tamper detected - rebooting" and TAMPERED is back in bootloader screen.
Click to expand...
Click to collapse
Yeah, it's gonna need to be S-on when I take it into the store...
Pretty sure they check the bootloader for S-ON, ***TAMPERED*** and ***LOCKED***
Is it just the 1.55+ Hboot that throws the tampered when locked?
If so Can I flash the 1.54.401.5 Hboot from Firewater and proceed like that?
Can't do the 1.44, My PC is running 8.1 and I've not played with Linux since 2009
Vonrottes said:
Yeah, it's gonna need to be S-on when I take it into the store...
Pretty sure they check the bootloader for S-ON, ***TAMPERED*** and ***LOCKED***
Click to expand...
Click to collapse
In that case, I recommend you use a 1.xx RUU
(check my guide in my signature)
Vonrottes said:
Is it just the 1.55+ Hboot that throws the tampered when locked?
Click to expand...
Click to collapse
Unknown when/what exactly triggers the "tamper detected" or some people have been able to S-On and not get that, others have not, so I can't say if it will happen or not. but if you wanna play it safe, go for 1.xx ruu.
Vonrottes said:
If so Can I flash the 1.54.401.5 Hboot from Firewater and proceed like that?
Click to expand...
Click to collapse
brick alert: Definitely NOT, that is a custom HBOOT, if you actually manage to S-On it with an unsigned hboot, you'll have an paperweight on your hands!! stay away from that.