Hi,
I want to send my HTC One in for repair, so first I need to restore it to stock.
However, I recently updated my firmware (and hboot) to the new 4.4.3 base (http://forum.xda-developers.com/showthread.php?t=2793539) so right now I am (s-off) on hboot 1.57.0000... Is this a problem when sending it in since this firmware isn't officially released yet (or is it)? And if it is, is it possible to downgrade my hboot?
Also, must I flash the firmware WITH the red warning before going S-on and locking the bootloader again?
I have flashed the stock odexed ROM, boot.img and recovery from the ARHD site (http://android-revolution-hd.blogspot.nl/p/android-revolution-hd-mirror-site-var.html).
Thanks in advance for any help!
No that firmware isn't officially released yet, it's still in testing stages so you will have to downgrade your firmware to 5.??.401.? Lucky for you this firmware comes with hboot 1.57 however if you have flashed a modded hboot/firmware ie to remove red text, then you will need to flash an official one, just find the official firmware package and use that, it comes with the hboot inside it, if you s-on with modded firmware or hboot you will have an instant brick.
The arhd site your got the Rom from should have the firmware package too.
Seanie280672 said:
No that firmware isn't officially released yet, it's still in testing stages so you will have to downgrade your firmware to 5.??.401.? Lucky for you this firmware comes with hboot 1.57 however if you have flashed a modded hboot/firmware ie to remove red text, then you will need to flash an official one, just find the official firmware package and use that, it comes with the hboot inside it, if you s-on with modded firmware or hboot you will have an instant brick.
The arhd site your got the Rom from should have the firmware package too.
Click to expand...
Click to collapse
Great, thanks! I will flash the original firmware in a sec, but the most recent RUU I can find is this one: http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
And I am not sure if that is also based on hboot 1.57 and because of that, if I am able to flash this RUU. Currently I am downloading it but the download speed is terrible, I will report back after I tried.
Or are you saying that I can flash the stock firmware 5.xx.401.xx on top of the current 6.xx firmware? I thought that wouldn't be possible because I'm currently on a higher firmware version but I'll give it a shot!
If you are s-off, you can flash or downgrade anything, however I would personally flash the matching firmware to the ruu that you are downloading, however, the firmware and hboot will be included in the ruu and be downgraded when you run the ruu, so just run it, once it's finished and you boot the phone, you can ota up to the latest version.
Seanie280672 said:
If you are s-off, you can flash or downgrade anything, however I would personally flash the matching firmware to the ruu that you are downloading, however, the firmware and hboot will be included in the ruu and be downgraded when you run the ruu, so just run it, once it's finished and you boot the phone, you can ota up to the latest version.
Click to expand...
Click to collapse
Ah I see, thanks a lot! Still waiting for the RUU to finish, I'll download the corresponding firmware and flash it before I start the RUU. Thanks again!
WiiiLDFARMER said:
Ah I see, thanks a lot! Still waiting for the RUU to finish, I'll download the corresponding firmware and flash it before I start the RUU. Thanks again!
Click to expand...
Click to collapse
You may have to remove the TAMPERED flag before running the ruu and also lock your bootloader, not relocked as the ruu will replace which ever recovery you ha e on your phone for the stock one, sometimes the ruu requires a locked bootloader whether s-off or s-on.
Once it's finished, boot the phone once and then back into bootloader and check the hboot version, if it is lower than the version you have on there now then you'll know you have stock hboot and should be safe to s-on, however like I said before, make sure your locked and tampered has gone before setting s-on (not sure if s-on is required for warranty)
Seanie280672 said:
You may have to remove the TAMPERED flag before running the ruu and also lock your bootloader, not relocked as the ruu will replace which ever recovery you ha e on your phone for the stock one, sometimes the ruu requires a locked bootloader whether s-off or s-on.
Click to expand...
Click to collapse
At the moment I don't have a tampered flag, it only says 'unlocked'. I'll try to lock the bootloader before starting the RUU. Do you know if the Tampered flag will return if I S-ON my M7 after completing the RUU?
WiiiLDFARMER said:
At the moment I don't have a tampered flag, it only says 'unlocked'. I'll try to lock the bootloader before starting the RUU. Do you know if the Tampered flag will return if I S-ON my M7 after completing the RUU?
Click to expand...
Click to collapse
Unfortunately I don't know that, there's been some reports it comes back after you s-on not after the ruu, I think it's HTC 's way of catching you out, others say it's been fine, are you sending it to HTC or your operator ?
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
However , if you've had s-off with that phone before, chances are you'll get it again, you'll just have to do whatever you did before to get it, then go back to stock again, and send it s-off.
WiiiLDFARMER said:
Hi,
I want to send my HTC One in for repair, so first I need to restore it to stock.
However, I recently updated my firmware (and hboot) to the new 4.4.3 base (http://forum.xda-developers.com/showthread.php?t=2793539) so right now I am (s-off) on hboot 1.57.0000... Is this a problem when sending it in since this firmware isn't officially released yet (or is it)? And if it is, is it possible to downgrade my hboot?
Also, must I flash the firmware WITH the red warning before going S-on and locking the bootloader again?
I have flashed the stock odexed ROM, boot.img and recovery from the ARHD site (http://android-revolution-hd.blogspot.nl/p/android-revolution-hd-mirror-site-var.html).
Thanks in advance for any help!
Click to expand...
Click to collapse
Try this guide:
http://forum.xda-developers.com/showthread.php?t=2541082
It worked for me, returned full stock!
Related
Is there anyway to downgrade to older version of hboot?
Now, i am on hboot 1.25.My phone is thailand region.
I cant install stock ruu.i have 140 error all the time.
I think RUU is too old but i dont know where to find a newer version.
I download ruu from stickied topic in development forum.
http://forum.xda-developers.com/showthread.php?t=1317895
I think that is the only ruu for thailand region. Anyone can help?
Many thanks.
Btw, my phone is still s-on and i think i cant s-off because i still want a warranty(that is why i am trying to go back to stock rom). Please help.
Sorry for my English. I am not good at English(I am Thai).
KazumaSaruwatari said:
Is there anyway to downgrade to older version of hboot?
Now, i am on hboot 1.25.My phone is thailand region.
I cant install stock ruu.i have 140 error all the time.
I think RUU is too old but i dont know where to find a newer version.
I download ruu from stickied topic in development forum.
http://forum.xda-developers.com/showthread.php?t=1317895
I think that is the only ruu for thailand region. Anyone can help?
Many thanks.
Btw, my phone is still s-on and i think i cant s-off because i still want a warranty(that is why i am trying to go back to stock rom). Please help.
Sorry for my English. I am not good at English(I am Thai).
Click to expand...
Click to collapse
There are only 2 versions of Hboot -> 1.25 and 1.28, there are no official older versions, maybe beta or engineering ones that were not released publicly.
You can S-OFF with unprotected Hboot, but this is not needed for you, check your CID from your phone and flash the according RUU for it, if not, take this tool and flash the S-OFF for 1.25 and after that you can flash any RUU you want as it bypasses that (as far as i know), after the RUU flashing, the HBOOT will be overwrited as well, so you will end up with a stock, locked, S-ON device with the region-stock ROM of your choice, hope this helps
Lexmazter said:
There are only 2 versions of Hboot -> 1.25 and 1.28, there are no official older versions, maybe beta or engineering ones that were not released publicly.
You can S-OFF with unprotected Hboot, but this is not needed for you, check your CID from your phone and flash the according RUU for it, if not, take this tool and flash the S-OFF for 1.25 and after that you can flash any RUU you want as it bypasses that (as far as i know), after the RUU flashing, the HBOOT will be overwrited as well, so you will end up with a stock, locked, S-ON device with the region-stock ROM of your choice, hope this helps
Click to expand...
Click to collapse
I just did what you say.
I S-OFF my phone.
I relock bootloader.
Then, I install RUU. It seems to run smoothly but in the end error 140 came up and my phone is S-ON again with still old custom rom.
What should I do?
KazumaSaruwatari said:
I just did what you say.
I S-OFF my phone.
I relock bootloader.
Then, I install RUU. It seems to run smoothly but in the end error 140 came up and my phone is S-ON again with still old custom rom.
What should I do?
Click to expand...
Click to collapse
Well, as far as i know, you unlock the bootloader again, S-OFF, and after that you flash the RUU, i didn't install any RUU's until now, you should check the guide from stona15 that can be found here, There are more details about what to do and what you want.
Hope this helps
I updated firmware to 2.24.401(s-off),but now I have a camera issue,I want to go back to 1.29.708.16(I can't find this firmware) then turn to s-on for warranty,there isn't update to 4.2 in HK(where I bought the phone),so how can I downgrade firmware to 1.29,and can I change the firmware number by change "mainver" in android-info.txt ?
dingnangen said:
I updated firmware to 2.24.401(s-off),but now I have a camera issue,I want to go back to 1.29.708.16(I can't find this firmware) then turn to s-on for warranty,there isn't update to 4.2 in HK(where I bought the phone),so how can I downgrade firmware to 1.29,and can I change the firmware number by change "mainver" in android-info.txt ?
Click to expand...
Click to collapse
If you are returning your phone for service then you can run an RUU if your phone has one.
It will reset everything back to stock, even the firmware. Check here:
http://forum.xda-developers.com/showthread.php?p=39588860
crushalot said:
If you are returning your phone for service then you can run an RUU if your phone has one.
It will reset everything back to stock, even the firmware. Check here:
http://forum.xda-developers.com/showthread.php?p=39588860
Click to expand...
Click to collapse
can 2.24 firmware use 1.29 ruu?how to do it ?
dingnangen said:
can 2.24 firmware use 1.29 ruu?how to do it ?
Click to expand...
Click to collapse
If your s-off then a RUU can downgrade your firmware. (I did this on a phone I returned for service without issues) If you are still s-on I don't think it will.
You just download the RUU.exe and run it on your PC and it guides you through resetting everything on the phone.
crushalot said:
If your s-off then a RUU can downgrade your firmware. (I did this on a phone I returned for service without issues) If you are still s-on I don't think it will.
You just download the RUU.exe and run it on your PC and it guides you through resetting everything on the phone.
Click to expand...
Click to collapse
thank you very much,i'll try it.if there aren't my ruus of region,I use other region ruu,can I get warranty?
That depends on the carrier/vendor. If you don't have a RUU you could also run an RUU for another area (Since your S-off) to downgrade the firmware and then root it and use one of the posted stock nandroids to restore to your proper areas stock config. Then do the stuff to re-lock your bootloader. http://forum.xda-developers.com/showthread.php?p=43458497
crushalot said:
That depends on the carrier/vendor. If you don't have a RUU you could also run an RUU for another area (Since your S-off) to downgrade the firmware and then root it and use one of the posted stock nandroids to restore to your proper areas stock config. Then do the stuff to re-lock your bootloader. http://forum.xda-developers.com/showthread.php?p=43458497
Click to expand...
Click to collapse
I can back to stock rom,but firmware version can't change,because there aren't ruu of HongKong,any ideas to change firmware version?
Since your S-off you can change your CID to use another RUU like this one:
http://bugsylawson.com/files/file/1...14325013-1033115001-release-311678-signedexe/
The RUU will set the device firmware back to stock. Then restore your stock ROM and you should be ok.
Also if you have it stock rom and setup now, you may just want to put S-on so that it says Locked and S-on on bootloader and your vendor will probably not care about the firmware version.
crushalot said:
Since your S-off you can change your CID to use another RUU like this one:
http://bugsylawson.com/files/file/1...14325013-1033115001-release-311678-signedexe/
The RUU will set the device firmware back to stock. Then restore your stock ROM and you should be ok.
Also if you have it stock rom and setup now, you may just want to put S-on so that it says Locked and S-on on bootloader and your vendor will probably not care about the firmware version.
Click to expand...
Click to collapse
thank you ,downing ruu now . is there Hboots red warning by using ruu back to stock?
dingnangen said:
thank you ,downing ruu now . is there Hboots red warning by using ruu back to stock?
Click to expand...
Click to collapse
The red warning in hboot is from being unlocked. Once you have back to stock (especially recovery) then the red warning will be gone. For sure after re-locking.
crushalot said:
Since your S-off you can change your CID to use another RUU like this one:
http://bugsylawson.com/files/file/1...14325013-1033115001-release-311678-signedexe/
The RUU will set the device firmware back to stock. Then restore your stock ROM and you should be ok.
Also if you have it stock rom and setup now, you may just want to put S-on so that it says Locked and S-on on bootloader and your vendor will probably not care about the firmware version.
Click to expand...
Click to collapse
how to backup my stock recovery,because I must flash custom recovery to restore my rom,then back to the stock recovery.
dingnangen said:
how to backup my stock recovery,because I must flash custom recovery to restore my rom,then back to the stock recovery.
Click to expand...
Click to collapse
Sorry, I'm not sure I understand what you are asking here.
crushalot said:
Sorry, I'm not sure I understand what you are asking here.
Click to expand...
Click to collapse
how can I backup stock recovery?
because there are not ruu of HK,so I should use TWRP to restore nandroid backup from HK htc one. then back to stock recovery .
Yes you would TWRP to restore and then flash the stock recovery and relock.
Here is a post where I helped another and it has the stock recovery and instructions for flashing if needed.
http://forum.xda-developers.com/showpost.php?p=43625746&postcount=17
Just an FYI that this method will not downgrade the firmware, but just get you back to locked and a stock look, but with the newer firmware.
Let me know if you need something else.
I have a HTC One on the EE network in the UK and I am still currently on Android 4.3 and Sense 5.5, they haven't bothered to release Android 4.4 yet and I have no hope that they will release Sense 6.
So, I would like to know how to go about changing my EE branded phone into an Unlocked International Version so that I can receive OTA updates direct from HTC.
Current CID: ORANG001
Current Hboot: 1.55
Current Software Number: 3.63.61.1
Radio: 4A.21.3263.04
Locked Bootloader with S-On
I would very much appreciate any help you can give.
Thank-You
rh92 said:
I have a HTC One on the EE network in the UK and I am still currently on Android 4.3 and Sense 5.5, they haven't bothered to release Android 4.4 yet and I have no hope that they will release Sense 6.
So, I would like to know how to go about changing my EE branded phone into an Unlocked International Version so that I can receive OTA updates direct from HTC.
Current CID: ORANG001
Current Hboot: 1.55
Current Software Number: 3.63.61.1
Radio: 4A.21.3263.04
Locked Bootloader with S-On
I would very much appreciate any help you can give.
Thank-You
Click to expand...
Click to collapse
first of all you need to unlock your bootloader and s-off your phone, debrand is not possible with s=on
the you would need to change your cid to something like HTC__001 or developer edition cid, one fastboot command required to do this.
and then run the correct RUU for those cid's and your done.
its quite easy to do, the hardest part is getting s-off, however you may be ok on 1.55 hboot, try rumrunner, read the instructions and download the required file here: http://rumrunner.us/
Seanie280672 said:
first of all you need to unlock your bootloader and s-off your phone, debrand is not possible with s=on
the you would need to change your cid to something like HTC__001 or developer edition cid, one fastboot command required to do this.
and then run the correct RUU for those cid's and your done.
its quite easy to do, the hardest part is getting s-off, however you may be ok on 1.55 hboot, try rumrunner, read the instructions and download the required file here: http://rumrunner.us/
Click to expand...
Click to collapse
Do I need custom recovery? If so which is best.
And do I need to have a custom ROM installed to gain s-off or can s-off be achieved on my current EE branded ROM?
Thanks
rh92 said:
Do I need custom recovery? If so which is best.
And do I need to have a custom ROM installed to gain s-off or can s-off be achieved on my current EE branded ROM?
Thanks
Click to expand...
Click to collapse
nope its not required for either, you should be able to s-off on stock rom, if you get an error or for some reason it fails, then you MAY have to flash a custom recovery and custom rom / kernel.
The RUU's will put you back to fully stock anyway in the end.
Seanie280672 said:
nope its not required for either, you should be able to s-off on stock rom, if you get an error or for some reason it fails, then you MAY have to flash a custom recovery and custom rom / kernel.
The RUU's will put you back to fully stock anyway in the end.
Click to expand...
Click to collapse
If the s-off does cause an error or it fails, can this cause my device to get bricked?
And by fully stock do you mean that the RUU turns s-on and locks my boot loader? (just in case I need to send my phone in for repair).
Thanks
rh92 said:
If the s-off does cause an error or it fails, can this cause my device to get bricked?
And by fully stock do you mean that the RUU turns s-on and locks my boot loader? (just in case I need to send my phone in for repair).
Thanks
Click to expand...
Click to collapse
no your phone wont brick
and no the ruu wont turn your phone s-on, you will need to lock your bootloader before running the RUU, but that's one simple command too, but only after s-off.
all you need right now is to make sure you have the drivers installed and that your device is detected in windows both when booted into a rom and on the bootloader screen.
Seanie280672 said:
no your phone wont brick
and no the ruu wont turn your phone s-on, you will need to lock your bootloader before running the RUU, but that's one simple command too, but only after s-off.
all you need right now is to make sure you have the drivers installed and that your device is detected in windows both when booted into a rom and on the bootloader screen.
Click to expand...
Click to collapse
After installing the RUU how would I get s-on?
Thanks
rh92 said:
After installing the RUU how would I get s-on?
Thanks
Click to expand...
Click to collapse
don't s-on, never s-on simple as that.
Seanie280672 said:
don't s-on, never s-on simple as that.
Click to expand...
Click to collapse
Ok, I was just asking in case I needed to send my phone in for repair in the future.
rh92 said:
Ok, I was just asking in case I needed to send my phone in for repair in the future.
Click to expand...
Click to collapse
not really something they will check to be honest, but if you s-on and you've played about with your phone down the line, like flashed a modified firmware or hboot, you will get an instant brick, if your hboot version is too high you will get the tampered flag back, or if you make a mistake along the way and the fix requires s-off, it will be very difficult to get again.
Seanie280672 said:
not really something they will check to be honest, but if you s-on and you've played about with your phone down the line, like flashed a modified firmware or hboot, you will get an instant brick, if your hboot version is too high you will get the tampered flag back, or if you make a mistake along the way and the fix requires s-off, it will be very difficult to get again.
Click to expand...
Click to collapse
So, is the following step by step list correct.
1. Unlock boot loader
2. Get s-off via rumrunner
3. Change CID
4. Lock boot loader
5. Run RUU
And, I am currently on 4.3 and Sense 5.5, so can I go straight to the sense 6 and Android 4.4 RUU, or do I have to install the sense 5.5 and Android 4.4 RUU first.
Thanks
rh92 said:
So, is the following step by step list correct.
1. Unlock boot loader
2. Get s-off via rumrunner
3. Change CID
4. Lock boot loader
5. Run RUU
And, I am currently on 4.3 and Sense 5.5, so can I go straight to the sense 6 and Android 4.4 RUU, or do I have to install the sense 5.5 and Android 4.4 RUU first.
Thanks
Click to expand...
Click to collapse
yup that's the correct order, and you will have to use this RUU as its the only full RUU available, everything else is just OTA's
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Seanie280672 said:
yup that's the correct order, and you will have to use this RUU as its the only full RUU available, everything else is just OTA's
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Click to expand...
Click to collapse
And after installing this RUU I can just download Sense 6 via OTA.
rh92 said:
And after installing this RUU I can just download Sense 6 via OTA.
Click to expand...
Click to collapse
yes, just accept the ota's one at a time.
Seanie280672 said:
yes, just accept the ota's one at a time.
Click to expand...
Click to collapse
Thanks for your help
I have an PN07200, how can I get sense 6, which will be the best RUU and CID?.... Thanks!
Enviado desde mi HTC One X+ mediante Tapatalk
is it possible to re-apply the branding?
i.e.
RUU
change cid
OTA with brand change
gwaitsi said:
is it possible to re-apply the branding?
i.e.
RUU
change cid
OTA with brand change
Click to expand...
Click to collapse
yup, change your cid to its original one, and find your service providers RUU and flash it.
Hi all.
Last week, after i soft bricked my phone (HTC ONE M7 EU with no carrier , bough directly from ) trying to update it to the latest version (i had mine unlocked and rooted to solve previous battery problems), i finally fixed it with the help of an user of this community
I have now an S-off HTC One GPE with 4.4.4 (via OTA update after flashing a RUU zip)
I kinda not like GPE and i think i should back to Sense .
Can anyone point me to the correct RUU thread and/or instructions or presequisites i shoult take account to do this process?
Thanks in advance
diesalher said:
Hi all.
Last week, after i soft bricked my phone (HTC ONE M7 EU with no carrier , bough directly from ) trying to update it to the latest version (i had mine unlocked and rooted to solve previous battery problems), i finally fixed it with the help of an user of this community
I have now an S-off HTC One GPE with 4.4.4 (via OTA update after flashing a RUU zip)
I kinda not like GPE and i think i should back to Sense .
Can anyone point me to the correct RUU thread and/or instructions or presequisites i shoult take account to do this process?
Thanks in advance
Click to expand...
Click to collapse
here are some links, if you're going to use a signed/encryped ruu, then you'll need to downgrade hboot first https://www.androidfilehost.com/?fid=23329332407580580
http://androidruu.com/getdownload.p...31.27_10.31.1131.05_release_310878_signed.exe
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
http://androidruu.com/getdownload.p...50.13_10.33.1150.01_release_316789_signed.zip
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
https://www.androidfilehost.com/?fid=23329332407584993
Thanks. Whats the difference between signed and unsigned?
diesalher said:
Thanks. Whats the difference between signed and unsigned?
Click to expand...
Click to collapse
considering you are s-off,
very little, but even with s-off, you will first need to downgrade hboot to same or lower version than the signed ruu.exe/ruu.zip
on the other hand, a decrypted ruu.zip doesn't have that restriction
a small chart is here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
under Not So FAQ #2
nkk71 said:
considering you are s-off,
very little, but even with s-off, you will first need to downgrade hboot to same or lower version than the signed ruu.exe/ruu.zip
on the other hand, a decrypted ruu.zip doesn't have that restriction
a small chart is here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
under Not So FAQ #2
Click to expand...
Click to collapse
So my process will be...
1. Downgrade hboot to 1.44
2. Change back my cid to HTC__002 (when i flashed the RUU from the GPE i changed it to GOOGL001)
3. Flash the RUU zip
Is that right?
diesalher said:
So my process will be...
1. Downgrade hboot to 1.44
2. Change back my cid to HTC__002 (when i flashed the RUU from the GPE i changed it to GOOGL001)
3. Flash the RUU zip
Is that right?
Click to expand...
Click to collapse
you don't have to go back to hboot 1.44
If your RUU is 4.xx flash a 3.xx firmware first
or 3.xx RUU a 3.xx or 2.xx firmware will work.
you may also need the MID change tool if you changed it also
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634
clsA said:
you don't have to go back to hboot 1.44
If your RUU is 4.xx flash a 3.xx firmware first
or 3.xx RUU a 3.xx or 2.xx firmware will work.
you may also need the MID change tool if you changed it also
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634
Click to expand...
Click to collapse
Ok, i'm confused,
The RUU i'g gonna flass is this
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-zip/
I'm not sure what is the version . I have installed a 4.4.4 GPE (via OTA Updates)
What should i do. downgrade the bootloader or not. Flash a firmware or not.
sorry , but i'm a bit newbie and dont want to mess up.
diesalher said:
Ok, i'm confused,
The RUU i'g gonna flass is this
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-zip/
I'm not sure what is the version . I have installed a 4.4.4 GPE (via OTA Updates)
What should i do. downgrade the bootloader or not. Flash a firmware or not.
sorry , but i'm a bit newbie and dont want to mess up.
Click to expand...
Click to collapse
The 1.28.401.7 is Jelly Bean it's equal to a 3.xx.xxx.x RUU
So the Firmware you would want is this http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/2.24.401.8.zip
Hi!
I've already read like a million tutorials on how to do that, but I think they won't work on my phone. I have the international unlocked version that I later converted to Google Play Edition. So now I have a GPE bootloader, TWRP recovery and root. Below I include a picture of my bootloader. My hboot is 1.54 so I can't use revone to relock the bootloader and make it s-on again, right? I really need you help guys, what should I do?
Edit: I downloaded this RUU "RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1 " - will it work on my phone? I'm not doing anything yet, because I don't want to brick it.
Edit 2: I downgraded my hboot to 1.44 and my phone still hasn't blown up so I guess that's a good sign.
seklerek said:
Hi!
I've already read like a million tutorials on how to do that, but I think they won't work on my phone. I have the international unlocked version that I later converted to Google Play Edition. So now I have a GPE bootloader, TWRP recovery and root. Below I include a picture of my bootloader. My hboot is 1.54 so I can't use revone to relock the bootloader and make it s-on again, right? I really need you help guys, what should I do?
Edit: I downloaded this RUU "RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1 " - will it work on my phone? I'm not doing anything yet, because I don't want to brick it.
Edit 2: I downgraded my hboot to 1.44 and my phone still hasn't blown up so I guess that's a good sign.
Click to expand...
Click to collapse
if your phone was on a x.xx.401.x version originally, then use the 1.28.401.7 ruu, then remove *tampered* and *relocked* banner using guru bootloader reset tool by booting a custom recovery using "fastboot boot recovery.img". You can then turn back s-on and send your phone. Everything is described in nkk71's guide linked in my signature.
Don't forget to set back your original CID and MID if you have changed them to convert your phone to GPE before running the ruu
Can't I use the RUU I downloaded? It's 4.19.401.9. I'm not sure what the original number was, but according to the download page it's compatible with my MID and CID.
seklerek said:
Can't I use the RUU I downloaded? It's 4.19.401.9. I'm not sure what the original number was, but according to the download page it's compatible with my MID and CID.
Click to expand...
Click to collapse
not for warranty purpose cause you must be on hboot 1.44 or 1.54 to remove the "tampered" and "relocked" flags form bootloader.
4.x.401.x ruu is hboot 1.55
1.x.401.x ruu is hboot 1.44
@alray I didn't know RUUs could also update hboot. Thank you for the information. So the 1.x.401.x files are Jelly Bean RUUs, but I'll be able to update to kitkat over the air when I'm done restoring to stock?
seklerek said:
@alray I didn't know RUUs could also update hboot. Thank you for the information. So the 1.x.401.x files are Jelly Bean RUUs, but I'll be able to update to kitkat over the air when I'm done restoring to stock?
Click to expand...
Click to collapse
Ruu update everything, firmware and software.
Yes you'll be able to take ota update after but don't update before you have removed tampered and relocked from the bootloader. Follow instructions in the guide.
@alray Alright, thank you very much. Will I be able to return to a full GPE after I receive it back from the service?
seklerek said:
@alray Alright, thank you very much. Will I be able to return to a full GPE after I receive it back from the service?
Click to expand...
Click to collapse
If you are able to achieve s-off again yes.
They will probably update your phone so it might be more difficult to achieve when it comes back.
@alray I'm having a problem with the guide you linked. It says to enter CWM recovery and use adb commands to remove flags and lock the bootloader, but I can't use any adb commands inside CWM. How do I fix this?
Edit: OK, I fixed this by using TWRP instead of CWM. Can I leave S-OFF and update the device normally, then restore it to GPE after I receive it back from service?
seklerek said:
@alray I'm having a problem with the guide you linked. It says to enter CWM recovery and use adb commands to remove flags and lock the bootloader, but I can't use any adb commands inside CWM. How do I fix this?
Edit: OK, I fixed this by using TWRP instead of CWM. Can I leave S-OFF and update the device normally, then restore it to GPE after I receive it back from service?
Click to expand...
Click to collapse
do not update the phone now, just turn back s-on and send it for repair. Its easier to get back s-off on lower version so better not to take any ota, however they will maybe update your phone at the service center (hopefully not).