Related
Please help me, i really need to downgrade hboot 1.54 to 1.44 with s-on?
I would really approciate any idea
Not possible
and is there any way to install PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio _4A.14.3250.13_10.33.1150.01_release_318486_signed _2_4.zip ? i'm trying to install this rom by using fastboot, but when it's checking HBOOT, it says error wrong bootloader required 1.44.00..., but i've got 1.54 at this time
way how to install this RUU or different one for international device without error caused by wrong HBOOT version?
Spartn said:
and is there any way to install PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio _4A.14.3250.13_10.33.1150.01_release_318486_signed _2_4.zip ? i'm trying to install this rom by using fastboot, but when it's checking HBOOT, it says error wrong bootloader required 1.44.00..., but i've got 1.54 at this time
way how to install this RUU or different one for international device without error caused by wrong HBOOT version?
Click to expand...
Click to collapse
Nope, not possible unless you have S-Off.
i wish i had known that security is better to leave off
thanks guys i think i just have to wait for s off which will work on new hboot 1.54..
will flashing stock ruu work to downgrade hboot?
djcoolguyno1 said:
will flashing stock ruu work to downgrade hboot?
Click to expand...
Click to collapse
That has been answered here already - no
EddyOS said:
That has been answered here already - no
Click to expand...
Click to collapse
How did you get s-off on 1.54?
sopaj96 said:
How did you get s-off on 1.54?
Click to expand...
Click to collapse
He probably got while still on hboot 1.44 (pre June 2013), and then just upgraded the firmware (including hboot to 1.54), that would not change S-Off status.
nkk71 said:
He probably got while still on hboot 1.44 (pre June 2013), and then just upgraded the firmware (including hboot to 1.54), that would not change S-Off status.
Click to expand...
Click to collapse
Exactly that ^
bobs ur uncle, fanny's ur aunt etc..........................
I guess it would be a good idea to post some pointers regarding this issue.
If you're s-on and on fw 1.54, you can't use revone to s-off.
Since you can't s-off, you are limited to flashing only RUUs that are compatible with your CID AND same or higher fw than you currently have on your device.
So to sum it all up, if you are on a higher fw than 1.44 and s-on, you are stuck there. The only possible way to s-off might be using a java card but I personally wouldn't go that way, even if you found some place that can do it.
makbil said:
So to sum it all up, if you are on a higher fw than 1.44 and s-on, you are stuck there.
Click to expand...
Click to collapse
So if going from 1.55 back to 1.44 is not possible. And Getting S-OFF with 1.55 is not possible.
Would Sprint be able to reflash my phone with either a working 1.55 or 1.44?
Spartn said:
Please help me, i really need to downgrade hboot 1.54 to 1.44 with s-on?
I would really approciate any idea
Click to expand...
Click to collapse
Try to s-off your phone with hboot 1.54 using rumrunner.
I found the RUU in http : / / www . htcdev.com/devcenter/downloads and tought if is possible do it.
Regards
only if your s-off
Victor Potasso said:
I found the RUU in http : / / www . htcdev.com/devcenter/downloads and tought if is possible do it.
Regards
Click to expand...
Click to collapse
Like I said in your previous thread http://forum.xda-developers.com/showthread.php?t=2552669
You might want to read this: http://forum.xda-developers.com/showthread.php?t=2541082
If you read, then you will understand that the RUU you want to execute need to be compatible with both your CID, MID and hboot version.
So yes its possible, but you need to be s-off to change CID/MID and to downgrade hboot if required.
and please don't start 2 different threads for relatively the same questions.
Hope it help
alray said:
Like I said in your previous thread http://forum.xda-developers.com/showthread.php?t=2552669
You might want to read this: http://forum.xda-developers.com/showthread.php?t=2541082
If you read, then you will understand that the RUU you want to execute need to be compatible with both your CID, MID and hboot version.
So yes its possible, but you need to be s-off to change CID/MID and to downgrade hboot if required.
and please don't start 2 different threads for relatively the same questions.
Hope it help
Click to expand...
Click to collapse
Can I set my device to s-off?
Victor Potasso said:
Can I set my device to s-off?
Click to expand...
Click to collapse
yes, use revone tool for hboot 1.44 or use rumrunner tool for hboot 1.54 and 1.55
This is the first thing listed in the thread I linked above.....
First you need to be S-Off, this will NOT work with S-On!!!
A) If you’re on hboot 1.44 use revone to get S-Off: http://forum.xda-developers.com/show....php?t=2314582
B) If you’re on hboot 1.54/1.55 use rumrunner to get S-Off: http://rumrunner.us/ and http://forum.xda-developers.com/show....php?t=2487888
Click to expand...
Click to collapse
---------- Post added at 02:38 AM ---------- Previous post was at 02:31 AM ----------
if you need to change cid:
Code:
fastboot oem writecid GOOGL01
where ''GOOGL01'' is the GPE cid
If you need to change MID:
http://forum.xda-developers.com/showthread.php?t=2322820
alray said:
yes, use revone tool for hboot 1.44 or use rumrunner tool for hboot 1.54 and 1.55
This is the first thing listed in the thread I linked above.....
---------- Post added at 02:38 AM ---------- Previous post was at 02:31 AM ----------
if you need to change cid:
Code:
fastboot oem writecid GOOGL01
where ''GOOGL01'' is the GPE cid
If you need to change MID:
http://forum.xda-developers.com/showthread.php?t=2322820
Click to expand...
Click to collapse
My hboot is 1.55 and I tried rumrunner but It got unsuccess. It stops when chilling... Do u think it happens because I have to change my MID
Victor Potasso said:
My hboot is 1.55 and I tried rumrunner but It got unsuccess. It stops when chilling... Do u think it happens because I have to change my MID
Click to expand...
Click to collapse
I can't answer that cause I'm not familiar with rumrunner since I s-off'd my One when it was on 1.44 hboot with revone. In theory rumrunner 0.5.0 should work on all international variant with hboot 1.54 and up except verizon model that need a different version of rumrunner. Maybe you should ask help directly on rumrunner thread for that step or search the forum for similar issue with s-off on 1.55. Hope you will find out.
alray said:
I can't answer that cause I'm not familiar with rumrunner since I s-off'd my One when it was on 1.44 hboot with revone. In theory rumrunner 0.5.0 should work on all international variant with hboot 1.54 and up except verizon model that need a different version of rumrunner. Maybe you should ask help directly on rumrunner thread for that step or search the forum for similar issue with s-off on 1.55. Hope you will find out.
Click to expand...
Click to collapse
Thanks mate, but I can't because I just Signed Up. I Can't write something in that threads yet :crying:
Cheers mate
Victor Potasso said:
Thanks mate, but I can't because I just Signed Up. I Can't write something in that threads yet :crying:
Cheers mate
Click to expand...
Click to collapse
I went back and forth with rumrunner and moonshine while using a rom 4.3 GPE ROM with twrp and it kept failing. ultimately installed a 4.1.2 stock then used revone and it worked wonderfully. I was able to remove the tampered flag, unlock the stock bootloader and flash the GPE 4.3 and receive the updates. I also only have a mac so i was limited in not being able to run .exe's.
swag1981 said:
I went back and forth with rumrunner and moonshine while using a rom 4.3 GPE ROM with twrp and it kept failing. ultimately installed a 4.1.2 stock then used revone and it worked wonderfully. I was able to remove the tampered flag, unlock the stock bootloader and flash the GPE 4.3 and receive the updates. I also only have a mac so i was limited in not being able to run .exe's.
Click to expand...
Click to collapse
I'm using Parallels Desktop as Virtual Machine. I use to run Win8 and Ubuntu with it. It works very well.
:good: w w w . parallels.com/products/desktop/
Sorry mate, I'm a bit noob. I got the TAMPERED FLAG when I tried to get S-OFF with rumrunner. What does it means?
I tried moonshine as well but it doesn't start
I've tried to get 4.1.2 stock as well but my device has to be S-OFF :crying:
Regards
Victor Potasso said:
I'm using Parallels Desktop as Virtual Machine. I use to run Win8 and Ubuntu with it. It works very well.
:good: w w w . parallels.com/products/desktop/
Sorry mate, I'm a bit noob. I got the TAMPERED FLAG when I tried to get S-OFF with rumrunner. What does it means?
I tried moonshine as well but it doesn't start
I've tried to get 4.1.2 stock as well but my device has to be S-OFF :crying:
Regards
Click to expand...
Click to collapse
Tampered flag is just that, a flag. It doesnt hinder anything, just a pop up for "Warranty" purposes. The flag pops up when you unlock the bootloader but when you get S-Off you can remove the flag.
Since you have access to windows i would go to http://forum.xda-developers.com/showthread.php?t=2428276 and find the .exe RUU for your area. Just get into your bootloader, select fastboot usb and run the .exe. Pick the lowest firmware available so you can ensure that you get the 1.44 hboot.
swag1981 said:
Tampered flag is just that, a flag. It doesnt hinder anything, just a pop up for "Warranty" purposes. The flag pops up when you unlock the bootloader but when you get S-Off you can remove the flag.
Since you have access to windows i would go to http://forum.xda-developers.com/showthread.php?t=2428276 and find the .exe RUU for your area. Just get into your bootloader, select fastboot usb and run the .exe. Pick the lowest firmware available so you can ensure that you get the 1.44 hboot.
Click to expand...
Click to collapse
swag1981 my hboot is 1.55
Is the process with .zip and .exe different? Maybe if I run .exe it can work with S-ON? :victory:
Victor Potasso said:
swag1981 my hboot is 1.55
Is the process with .zip and .exe different? Maybe if I run .exe it can work with S-ON? :victory:
Click to expand...
Click to collapse
The zip can only be used with S-Off where as the exe is designed to be used to return a phone to stock with S-On.
Just get into fastboot and run the exe, it should do the rest for you. It will wipe the entire phone, but as far as I'm concerned, a blank phone is better than an unusable one.
I'm not sure if the hboot makes a difference, but mine downgraded when I flashed an older RUU.
Once you get the older hboot and firmware, you may have to unlock your bootloader again through HTC Dev, then S-Off. Once your S-Off unlocking your bootloader is much easier.
Sent from my HTC One using Tapatalk
Whoo ho! Nice mate. I wanna to get it.
I'll try this soon. Thanks again mate. You've been helping me a lot.
Cheers
Whoo ho! Nice mate. I wanna to get it.
I'll try this soon. Thanks again mate. You've been helping me a lot.
:cheers:
Give this site a read over too when you get a chance http://www.htc1guru.com/downloads/
Sent from my HTC One using Tapatalk
swag1981 said:
The zip can only be used with S-Off where as the exe is designed to be used to return a phone to stock with S-On.
Just get into fastboot and run the exe, it should do the rest for you. It will wipe the entire phone, but as far as I'm concerned, a blank phone is better than an unusable one.
I'm not sure if the hboot makes a difference, but mine downgraded when I flashed an older RUU.
Once you get the older hboot and firmware, you may have to unlock your bootloader again through HTC Dev, then S-Off. Once your S-Off unlocking your bootloader is much easier.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
If you want to run a GPE RUU.exe your phone MUST have CID compatible (BS_US0001) with GPE and MID: PN0712000
you can check that with this command:
Code:
fastboot oem readcid
fastboot oem readmid
if they doesn't match, you MUST be S-OFF to change them
If your device is currently a DEV edition, you should already have PN0712000 as MID so the only concern is that CID need to match GPE RUU
You should post your
Code:
fastboot getvar-all
and remove imei and sn so it will be easier to see what options you have.
swag1981 said:
The zip can only be used with S-Off where as the exe is designed to be used to return a phone to stock with S-On.
Just get into fastboot and run the exe, it should do the rest for you. It will wipe the entire phone, but as far as I'm concerned, a blank phone is better than an unusable one.
I'm not sure if the hboot makes a difference, but mine downgraded when I flashed an older RUU.
Once you get the older hboot and firmware, you may have to unlock your bootloader again through HTC Dev, then S-Off. Once your S-Off unlocking your bootloader is much easier.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I just tried run this .exe but I got this error http://imgur.com/rYvIdBd
I downloaded RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe but my current ROM is Android 4.3 version 3.22.1540.1. I suppose I got this error because I tried to install a oldest version in my device. Does it make any ****ing sense?
I'm downloading the .exe for 3.22.1540.1 and than try to install it.
Regards
alray said:
If you want to run a GPE RUU.exe your phone MUST have CID compatible (BS_US0001) with GPE and MID: PN0712000
you can check that with this command:
Code:
fastboot oem readcid
fastboot oem readmid
if they doesn't match, you MUST be S-OFF to change them
If your device is currently a DEV edition, you should already have PN0712000 as MID so the only concern is that CID need to match GPE RUU
You should post your
Code:
fastboot getvar-all
and remove imei and sn so it will be easier to see what options you have.
Click to expand...
Click to collapse
Yep, my device has MID as PN0712000 and CID BS_US001
I tried run RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe from HTC1GURU byt i got this error http://imgur.com/rYvIdBd
My current software version is 3.22.1540.1.
@alray and @swag1981
I followed this thread http://forum.xda-developers.com/showthread.php?p=46046898
If I have a hboot S-ON it has to be LOCKED or RE-LOCKED. It'll never work with hboot UNLOCK. So if your hboot is S-OFF it not matter.
Thank u mates. You were friggin' awesome.
Regards
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!
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).
hello guys, i am having some problem manually updating my htc one to lollipop
my phone is locked , S-ON
while running the RUU it detect the device at first then after starting looking for bootloader it give me an error usb not connected , and i repeat it several times .
my question is do i have to be unlocked and s-off to update through RUU ?
ali.nour85 said:
hello guys, i am having some problem manually updating my htc one to lollipop
my phone is locked , S-ON
while running the RUU it detect the device at first then after starting looking for bootloader it give me an error usb not connected , and i repeat it several times .
my question is do i have to be unlocked and s-off to update through RUU ?
Click to expand...
Click to collapse
You only have to be s-off and unlocked if the ruu doesn't match the your phone info, you can't install ota manually if your s-on, so which ruu are you trying to use ? And what does your version main / os version number say at the moment.
Seanie280672 said:
You only have to be s-off and unlocked if the ruu doesn't match the your phone info, you can't install ota manually if your s-on, so which ruu are you trying to use ? And what does your version main / os version number say at the moment.
Click to expand...
Click to collapse
im using this ruu
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2
i got this ruu from htc website
my software number is 6.15.599.101 and my CID is HTC 332
ali.nour85 said:
im using this ruu
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2
i got this ruu from htc website
my software number is 6.15.599.101 and my CID is HTC 332
Click to expand...
Click to collapse
Yup, I figured you were trying to use that ruu, look at the 3rd set of numbers, yours is 599 and that ruu is 1540, it won't work, you would need s-off, change cid, change mid, flash firmware and then run the ruu, you will have to do that or wait to get the update for your device.
S-off for your phone will cost $25 through sunshine s-off tool and is the only way to s-off your 6xxxxxxxx firmware which you are currently on.
Seanie280672 said:
Yup, I figured you were trying to use that ruu, look at the 3rd set of numbers, yours is 599 and that ruu is 1540, it won't work, you would need s-off, change cid, change mid, flash firmware and then run the ruu, you will have to do that or wait to get the update for your device.
S-off for your phone will cost $25 through sunshine s-off tool and is the only way to s-off your 6xxxxxxxx firmware which you are currently on.
Click to expand...
Click to collapse
ok thanks for explanation