Hi people
I rooted my phone a couple of days back and tried a few ROMs. But I want to go back to my stock ROM (Sense 4.3) in such a way that I can still get OTA updates. Is that possible? I have a US 32 GB Unlocked HTC One.
Thanks!
Do you have s-off?
If no, which version of hboot do you have, which cid and which version main?
Use the command:
Code:
fastboot getvar all
and post here the log
p.s. Remove your imei and serial number of your phone
Guich said:
Do you have s-off?
If no, which version of hboot do you have, which cid and which version main?
Use the command:
Code:
fastboot getvar all
and post here the log
p.s. Remove your imei and serial number of your phone
Click to expand...
Click to collapse
Unfortunately, I didn't pay much attention didn't s-off when I had the time.
So that's a no for s-off. hboot - 1.55 (the latest one). CID - BS_US001. I'm afraid I'm not sure what 'version main' is!
Boot in fastboot and from pc type:
Code:
fastboot getvar version-main
.
I will advice you to flash this ruu.
Theoretically this ruu will work, but you have to check the version main.
P.s. for flash a ruu, you need a locked bootloader
Duplicate post. Sorry.
Guich said:
Boot in fastboot and from pc type:
Code:
fastboot getvar version-main
.
I will advice you to flash this ruu.
Theoretically this ruu will work, but you have to check the version main.
P.s. for flash a ruu, you need a locked bootloader
Click to expand...
Click to collapse
I'm on a mac right now and cant really set up ADB/Fastboot on it. So i'll get to PC tomorrow and run that command and see the version. Thanks for your help!
Related
I'm S-OFF. My device is recently unrooted, and my version is 1.28.771.10 on the THREE 3 UK network. It seems there isn't an RUU for my phone released by three. Is there any way that I can return to stock so that my phone is as new? Step by step instructions would be appreciated as i'm very new to this. My bootloader is also locked.
I am on 3 UK also.
Have done this many times .
As you have S off you can change your cid (customer or carrier id) from H3G__001 (which is 3 UK)
to so called super cid which is
11111111 (eight 1's)
When in bootloader fastboot usb mode
C:\adb> fastboot oem writecid 11111111
This will allow you to use any version RUU for your model.
Best one is WWE version which has 401 in the place where yours had 771.
I have always been unlocked when doing this. As you have got S off I will assume you can unlock bootloader.
Then download to your pc the appropriate ruu, I would suggest file (very long filename, I will just list first part of filename - will edit post to add download link)
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7
Download this to your pc
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
It's a large file 990 MB .
The following will delete all your data, photos, video, music, txt , etc (phone number should remain in SIM ) so BE SURE TO COPY FROM PHONE TO PC ANYTHING YOU WANT TO KEEP.
Then connect your HTC One to your pc with usb cable (usb 2, preferably) and simply run the program you've just downloaded .
Your phone can be either in fastboot mode or with android running, doesn't matter which .
Follow on screen instructions, ticking boxes as appropriate.
Total process takes approximately ten minutes from starting the program to finish.
When finished you will be on stock 1.28.401.6 which is original Android 4.1.1
However if you wish you can easily update Ota (over the air) through successive versions up to 4.2 by entering settings then about then software updates then check now
Hope this helps
Sent from my HTC One using xda app-developers app
paul_59 said:
I am on 3 UK also.
Have done this many times .
As you have S off you can change your cid (customer or carrier id) from H3G__001 (which is 3 UK)
to so called super cid which is
11111111 (eight 1's)
When in bootloader fastboot usb mode
C:\adb> fastboot oem writecid 11111111
This will allow you to use any version RUU for your model.
Best one is WWE version which has 401 in the place where yours had 771.
I have always been unlocked when doing this. As you have got S off I will assume you can unlock bootloader.
Then download to your pc the appropriate ruu, I would suggest file (very long filename, I will just list first part of filename - will edit post to add download link)
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7
Download this to your pc
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
It's a large file 990 MB .
The following will delete all your data, photos, video, music, txt , etc (phone number should remain in SIM ) so BE SURE TO COPY FROM PHONE TO PC ANYTHING YOU WANT TO KEEP.
Then connect your HTC One to your pc with usb cable (usb 2, preferably) and simply run the program you've just downloaded .
Your phone can be either in fastboot mode or with android running, doesn't matter which .
Follow on screen instructions, ticking boxes as appropriate.
Total process takes approximately ten minutes from starting the program to finish.
When finished you will be on stock 1.28.401.6 which is original Android 4.1.1
However if you wish you can easily update Ota (over the air) through successive versions up to 4.2 by entering settings then about then software updates then check now
Hope this helps
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hey buddy, I know this is an old threat but you're on the exact same network as me and such.
I managed to get back to stock, and i'm on android version 4.1.2... but i can't seem to find any OTA android updates? Which is the main reason why I unrooted my phone. Tried the google framework fix too. Got any ideas?
tomquartey said:
Hey buddy, I know this is an old threat but you're on the exact same network as me and such.
I managed to get back to stock, and i'm on android version 4.1.2... but i can't seem to find any OTA android updates? Which is the main reason why I unrooted my phone. Tried the google framework fix too. Got any ideas?
Click to expand...
Click to collapse
If you are supercid (11111111) you will not get ota. You must change cid to one that match you OS base.
alray said:
If you are supercid (11111111) you will not get ota. You must change cid to one that match you OS base.
Click to expand...
Click to collapse
I had to SUPER CID to flash this particular RUU.
If I change my CID back now, will this mean my RUU is redundant and then brick my phone?
And the original CID was H3G_001. Do I need to go back to this one?
tomquartey said:
I had to SUPER CID to flash this particular RUU.
If I change my CID back now, will this mean my RUU is redundant and then brick my phone?
And the original CID was H3G_001. Do I need to go back to this one?
Click to expand...
Click to collapse
no its safe to change CID, you will never get OTA with supercid from this carrier
change back your cid to H3G__001 (2 lower case H3G _ _001)
Code:
fastboot oem writecid H3G__001 [COLOR="SeaGreen"]---> cid change[/COLOR]
fastboot reboot-bootloader [COLOR="SeaGreen"]--> reboot and go back to fastboot usb[/COLOR]
fastboot oem readcid [COLOR="SeaGreen"]--->confirm cid is now H3G__001[/COLOR]
fastboot reboot [COLOR="SeaGreen"]--->reboot to system[/COLOR]
then install ota
alray said:
no its safe to change CID, you will never get OTA with supercid from this carrier
change back your cid to H3G__001 (2 lower case H3G _ _001)
Code:
fastboot oem writecid H3G__001 [COLOR="SeaGreen"]---> cid change[/COLOR]
fastboot reboot-bootloader [COLOR="SeaGreen"]--> reboot and go back to fastboot usb[/COLOR]
fastboot oem readcid [COLOR="SeaGreen"]--->confirm cid is now H3G__001[/COLOR]
fastboot reboot [COLOR="SeaGreen"]--->reboot to system[/COLOR]
then install ota
Click to expand...
Click to collapse
Thank you buddy, will try this soon.
tomquartey said:
I had to SUPER CID to flash this particular RUU.
If I change my CID back now, will this mean my RUU is redundant and then brick my phone?
And the original CID was H3G_001. Do I need to go back to this one?
Click to expand...
Click to collapse
alray said:
no its safe to change CID, you will never get OTA with supercid from this carrier
change back your cid to H3G__001 (2 lower case H3G _ _001)
Code:
fastboot oem writecid H3G__001 [COLOR="SeaGreen"]---> cid change[/COLOR]
fastboot reboot-bootloader [COLOR="SeaGreen"]--> reboot and go back to fastboot usb[/COLOR]
fastboot oem readcid [COLOR="SeaGreen"]--->confirm cid is now H3G__001[/COLOR]
fastboot reboot [COLOR="SeaGreen"]--->reboot to system[/COLOR]
then install ota
Click to expand...
Click to collapse
1- easy on the double posting , then make up your mind, where you wanna post, so people can actually help
2- what ruu are you referring to?
3- no just changing CID back to original (H3G__001) does not mean you're going to get any OTA if the ^^ ruu is not H3G
nkk71 said:
1- easy on the double posting , then make up your mind, where you wanna post, so people can actually help
2- what ruu are you referring to?
3- no just changing CID back to original (H3G__001) does not mean you're going to get any OTA if the ^^ ruu is not H3G
Click to expand...
Click to collapse
I was told to change my RUU to a particular RUU from another user who is on the same network as me.
tomquartey said:
I was told to change my RUU to a particular RUU from another user who is on the same network as me.
Click to expand...
Click to collapse
well if you are on CID H3G_001 then this "change my RUU to a particular RUU" (there is no particular RUU) makes no sense at all, if you are S-Off:
1- you can change CID to unbranded and use an unbranded RUU
2- you can use one of the guides around here to go back to H3G stock
I'm very confused why I'm missing so many commands from my hboot.
Do I just need to upgrade to a different hboot? I heard 1.44 was super safe though.
I need the writeserialno command (even though getvar works) so that I can restore this phone to the serialno on the sim tray because it's all zeros now for some reason!
Is there an hboot I can just grab and install the zip straight up with TWRP that has these in it?
Thanks in advance!
Hey, I was stupid and missed up my phone. I wanted to update my phone, but because It was rooded I wasn't able to do it. So I decided to begin from start. So I downgraded my Hboot to 1.44 and also stupid to set s-on again. But then I could not install the stock rom 1.29.651.10. So I decided to try a custom rom. So I would be able to set s-off again. But non of them worked. I think that the old Hboot 1.44 is why the roms didn't work. But I can't change my Hboot before my device is s-off.
I'm able to use adb sideload and twrp recovery
Bootloader information
Tampered
Unlocked
M7_WLS PTV SHIP S-ON RH
HBOOT-1.44.0000
OpenDSP-v32.120.274.0909
eMMC-boot
May 8 2013.16:30:08:-1
Does any one have any suggestions ?
If I remember right, the older s-off techniques like rumrunner should still work with that hboot. I'd look into those first.
coal686 said:
If I remember right, the older s-off techniques like rumrunner should still work with that hboot. I'd look into those first.
Click to expand...
Click to collapse
I've have already tried rumrunner, but it didn't work for me. I was able to get Viberone 8 to work, but it was very slow. Tried to get s-off but did't work with the Viberone rom. So now i'm trying another one to see if it will allow me to get the phone s-off. But thx for your respond
1.29.401.12. is not a Sprint rom.
BD619 said:
1.29.401.12. is not a Sprint rom.
Click to expand...
Click to collapse
Sorry ment 1.29.651.10
christian8220 said:
Sorry ment 1.29.651.10
Click to expand...
Click to collapse
While booted to fastbootusb open a cmd window (from your platform tools folder) and type:
Code:
fastboot getvar all
Then copy and paste the results here...make sure you remove your IMEI from the results.
BD619 said:
While booted to fastbootusb open a cmd window (from your platform tools folder) and type:
Code:
fastboot getvar all
Then copy and paste the results here...make sure you remove your IMEI from the results.
Click to expand...
Click to collapse
Here you go
christian8220 said:
Here you go
Click to expand...
Click to collapse
Re-lock your bootloader and use the 1.29.651.10 RUU then give revone a try it should work to get you s-off again
BD619 said:
Re-lock your bootloader and use the 1.29.651.10 RUU then give revone a try it should work to get you s-off again
Click to expand...
Click to collapse
Thx it worked for me. First I replaced the TWRP recovery with the stock recovery 1.29.651.10. After that I relocked my bootloader "fastboot oem lock" and the device rebooted. I used the 1.29.651.10 RUU exe. and it worked. So thank you, have a nice day
Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,
BorisZX6R said:
Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,
Click to expand...
Click to collapse
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
alray said:
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
Click to expand...
Click to collapse
Thank you for your time and response. I will think about what RUU is best for me. I am currently on the T-Mobile network with this phone and so far there is no indicator that will change anytime soon. I will try and post my response.
Thank you again!
alray said:
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
Click to expand...
Click to collapse
Unfortunately I am still hunting for an RUU that will bring the hboot to version 1.57. All the ones I tried either fail with error 155 or they leave me on the same version of hboot. Trouble finding an appropriate RUU... If you know where I can get one that will upgrade the hboot to 1.57 please guide me in the right direction.
Thank you!
BorisZX6R said:
Unfortunately I am still hunting for an RUU that will bring the hboot to version 1.57. All the ones I tried either fail with error 155 or they leave me on the same version of hboot. Trouble finding an appropriate RUU... If you know where I can get one that will upgrade the hboot to 1.57 please guide me in the right direction.
Thank you!
Click to expand...
Click to collapse
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
alray said:
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
Click to expand...
Click to collapse
Thank you very much, I will attempt to do this and I will post my results once I had a chance to try it.
One more thing, isn't having a super CID an advantage?! Is 11111111 a super CID?!
Thank you!
BorisZX6R said:
Thank you very much, I will attempt to do this and I will post my results once I had a chance to try it.
One more thing, isn't having a super CID an advantage?! Is 11111111 a super CID?!
Thank you!
Click to expand...
Click to collapse
Yes, supercid is 11111111 so your CID isn't a problem. Just make sure that your MID also match the ruu you want to use (or change it if needed). If you MID is still the original, it should be PN0712000 so you can either use an AT&T or Developer Edition RUU (x.xx.1540.x). Otherwise if you want to use the WWE version (x.xx.401.x) You'll have to change your MID to PN0710000.
alray said:
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
Click to expand...
Click to collapse
It worked. For a moment the output in the command window seemed like it was giving errors (unfortunately it was very late and I did not copy the output) but in the end I realized it updated the hboot and I was able to flash a different RUU.
Thank you for all your help!
hello guys.
i had an htc one m7 ul for a while and all was great until the network stopped working.
so i decided to flash an RUU exe for my device which is HTC___J15
the process did not finish and it gave the error "failed zip" on the fastboot screen.
i rebooted the phone and it went back to the fastboot screen and it never got back in the system, this was two days ago.
yesterday i tried to flash the htc___j15 ruu zip file and it gave me the signature verification failed error.
it says tampered and reclocked *security warning* and my hboot version is 1.61 and os-7.19.401.51
after some reaserch im discovering it says s-on .
is there any way to put it to s-off or downgrade the hboot from 1.61
tried revone,rumrunner and all those did not work
reealumni said:
hello guys.
i had an htc one m7 ul for a while and all was great until the network stopped working.
so i decided to flash an RUU exe for my device which is HTC___J15
the process did not finish and it gave the error "failed zip" on the fastboot screen.
i rebooted the phone and it went back to the fastboot screen and it never got back in the system, this was two days ago.
yesterday i tried to flash the htc___j15 ruu zip file and it gave me the signature verification failed error.
it says tampered and reclocked *security warning* and my hboot version is 1.61 and os-7.19.401.51
after some reaserch im discovering it says s-on .
is there any way to put it to s-off or downgrade the hboot from 1.61
tried revone,rumrunner and all those did not work
Click to expand...
Click to collapse
If your version main is 7.19.401.51 then the only RUU you can flash is the 7.19.401.51 version. You don't need S-OFF to flash this RUU and fyi, S-OFF can only be acheived using the Sunshine S-OFF exploit on this hboot version. Hboot can only be downgraded when already S-OFF.
If you need more help, pleas post the output of "fastboot getvar all" with your next post (hide imei/serial)
The 7.19.401.51 RUU can be found here at post #2 and instruction how to flash at post #1.
alray said:
If your version main is 7.19.401.51 then the only RUU you can flash is the 7.19.401.51 version. You don't need S-OFF to flash this RUU and fyi, S-OFF can only be acheived using the Sunshine S-OFF exploit on this hboot version. Hboot can only be downgraded when already S-OFF.
If you need more help, pleas post the output of "fastboot getvar all" with your next post (hide imei/serial)
The 7.19.401.51 RUU can be found here at post #2 and instruction how to flash at post #1.
Click to expand...
Click to collapse
i will try use the exact OS from your given link. and how do i use SUnshine for S-OFF
reealumni said:
i will try use the exact OS from your given link. and how do i use SUnshine for S-OFF
Click to expand...
Click to collapse
At first you need a running system cause sunshine is an app based service. After that you can download the latest sunshine app and install it, then the app will test your device if it is possible to make it s-off. If it can, in the second step you have to buy a license for your device within sunshine (about 20€/25$). After sucessfully payment your device will reboot and sunshine will set it to s-off.(The license is bind to your device and you can use it on this device as often as you want, for other devices you need to buy another license)
http://theroot.ninja/
phone is now working but...
so guys i flashed the zip using htc-fastboot and the phone is back to normal but with unkown imei and baseband. Thats basically no network
how to fix that now?
reealumni said:
so guys i flashed the zip using htc-fastboot and the phone is back to normal but with unkown imei and baseband. Thats basically no network
how to fix that now?
Click to expand...
Click to collapse
If after flashing the RUU your problem isn't fixed, it's probably an hardware problem.
reealumni said:
so guys i flashed the zip using htc-fastboot and the phone is back to normal but with unkown imei and baseband. Thats basically no network
how to fix that now?
Click to expand...
Click to collapse
Reflash ruu
Or
If you have backup of partition 2,3,4,5. You can restored the partitions that have phone info like imei and serial no with TWRP by if=dd
KARIM9377 said:
Reflash ruu
Or
If you have backup of partition 2,3,4,5. You can restored the partitions that have phone info like imei and serial no with TWRP by if=dd
Click to expand...
Click to collapse
will try reflash the RUU. i do not have any backups of the partitions :crying: