now i am about to send my phone to fix the camera issues
so i restored a stock nandroid backup of mine of 4.2.2 now my device is s-off
does updating to 4.3 will revert it to s-on ?
how to restore stock recovery ?
how to update to 4.3 without updating hboot to 1.55 ?
if i am stock rom , kernel , recovery , cid but s-off and unlocked and removed tampered am i good to go or there is other thing to do more than the above ?
please help people i am sending it by tomorrow .. i need help asap
Nightf0x_007 said:
please help people i am sending it by tomorrow .. i need help asap
Click to expand...
Click to collapse
if it was so asap a little searching on your part and you would have found this and no it does not make you s-on to turn secure flag back on look in the thread of the s-off method you used
http://forum.xda-developers.com/showthread.php?t=2358738
jerrycoffman45 said:
if it was so asap a little searching on your part and you would have found this and no it does not make you s-on to turn secure flag back on look in the thread of the s-off method you used
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
ok , i want to update to 4.3 without updating my hboot to 1.55 ?
Nightf0x_007 said:
ok , i want to update to 4.3 without updating my hboot to 1.55 ?
Click to expand...
Click to collapse
only way to do that as far as i know is to flash a custom rom any reason why you dont want that hboot i am using it no problem
this might do what you want looks like it does not flash hboot http://forum.xda-developers.com/showthread.php?t=2471869
Related
Can anyone help me find this stock recovery as i want to unroot and update my rom then re-root
mimicuk said:
Can anyone help me find this stock recovery as i want to unroot and update my rom then re-root
Click to expand...
Click to collapse
No resolution for this?
I'm S-ON, hboot 1.54, CID=VODAP001.
As I understand things, i cant S-OFF because i'm on hboot 1.54 and Revone doesnt work on 1.54.
I cant use SuperCID because i'm S-ON
I cant flash any firmware unless the CID=VODAP001
(and now I wont get any OTA's as i went ahead an flashed a new ROM)
So i'm slightly stuck until either someone finds a way to S-OFF the hboot 1.54 or we track down a nandroid backup or RUU for CID=VODAP001
smithbill said:
No resolution for this?
I'm S-ON, hboot 1.54, CID=VODAP001.
As I understand things, i cant S-OFF because i'm on hboot 1.54 and Revone doesnt work on 1.54.
I cant use SuperCID because i'm S-ON
I cant flash any firmware unless the CID=VODAP001
(and now I wont get any OTA's as i went ahead an flashed a new ROM)
So i'm slightly stuck until either someone finds a way to S-OFF the hboot 1.54 or we track down a nandroid backup or RUU for CID=VODAP001
Click to expand...
Click to collapse
i have same problem did u sort it iut
Grathite said:
i have same problem did u sort it iut
Click to expand...
Click to collapse
Yes I did.
You want to use Rumrunner to achieve S-OFF (assuming you are on hboot 1.54 and S-ON like I was).
Full details are available at:
http://forum.xda-developers.com/showthread.php?t=2488772
Make sure to pay attention to the various requirements. It does work. I am now S-OFF, hboot 1.55 and SuperCID and have been able to flash new Firmware without issues.
Bill
Grathite said:
i have same problem did u sort it iut
Click to expand...
Click to collapse
for hboot 1.54 and 1.55:
http://forum.xda-developers.com/showthread.php?t=2487888 and http://rumrunner.us/
Hi Guys, been trawling the forum but not a great deal of info on this new firmware. I've updated the firmware to 2.24.401.1 using Mikes Guide BUT.. I WAS S-On AT the time! Is it possible to downgrade the firmware from the latest bootloader 1.54.0000 back to 1.44.0000.
I'm wanting to return to stock to receive OTAs but I have a feeling at the moment with the new firmware and S-On I cant do this?
Any advice appreciated
You could try and see if revone somehow works, however i dont think it does with the 1.54 hboot. Why didnt you get S-OFF before the update.
Yeah I don't think you can downgrade Hboot with S-On. Might have to wait until a method is realeased for the 1.54 Hboot.
nintendolinky said:
You could try and see if revone somehow works, however i dont think it does with the 1.54 hboot. Why didnt you get S-OFF before the update.
Click to expand...
Click to collapse
At the time I didnt think it was necessary. I thought wrong, failed my homework ! Thanks for the clarification :good:. I can wait.
I made the mistake of upgrading to 4.2.2 (Hboot 1.54.0000) now I can't s-off arghhh!!!!!!
same here...
is there anyway to go back to 100% stock?? there dont seem to be a 2.24.xx RUU...
Hi Guys,
I'm trying to get back to 100% stock so I can send my phone back for replacement/repair. There was no RUU so I used some kindly donated nandroid back ups and OTA firmware to get back to what should be my current stock 2.29.980.2 (Australian Unbranded HTC__039). Ive got stock recovery back on and OTA's are working. I'm still S-Off and boot loader unlocked.
The last think i need to do is get S-on and relock the bootloader. But in flashing the current firmware, HBoot is at 1.54.
Before I do any brash, does anyone know if revone one will still work to allow me to relock the bootloader and S-on?
If not will I have to downgrade Hboot to 1.44 and get S-On back on then reflash the firmware to upgrade HBoot back to 1.54?
I've also read that if there is anything other than stock HBoot and S-On you can brick the phone. But I take if the Hboot has upgraded from the OTA firmware this should be fine?
Thanks
Ali Baba 84 said:
Hi Guys,
I'm trying to get back to 100% stock so I can send my phone back for replacement/repair. There was no RUU so I used some kindly donated nandroid back ups and OTA firmware to get back to what should be my current stock 2.29.980.2 (Australian Unbranded HTC__039). Ive got stock recovery back on and OTA's are working. I'm still S-Off and boot loader unlocked.
The last think i need to do is get S-on and relock the bootloader. But in flashing the current firmware, HBoot is at 1.54.
Before I do any brash, does anyone know if revone one will still work to allow me to relock the bootloader and S-on?
If not will I have to downgrade Hboot to 1.44 and get S-On back on then reflash the firmware to upgrade HBoot back to 1.54?
I've also read that if there is anything other than stock HBoot and S-On you can brick the phone. But I take if the Hboot has upgraded from the OTA firmware this should be fine?
Thanks
Click to expand...
Click to collapse
noooooooooooooo, don't s-on with 1.54.
criszz said:
noooooooooooooo, don't s-on with 1.54.
Click to expand...
Click to collapse
You might want to be a bit more helpful and actually tell him why not
I would also advise against reverting to S on, because you won't be able to regain S off again, at least currently with 1.54 hboot.
If you wish to send for repair, my advice would be ensure you have stock recovery and stock Rom.
Use revone to remove tampered, and also relock bootloader .
No real need to revert to S on, as Soff doesn't indicate that you tampered with your device as a small number of HTC One were sold with S off
Sent from my HTC One using xda app-developers app
Ali Baba 84 said:
Hi Guys,
I'm trying to get back to 100% stock so I can send my phone back for replacement/repair. There was no RUU so I used some kindly donated nandroid back ups and OTA firmware to get back to what should be my current stock 2.29.980.2 (Australian Unbranded HTC__039). Ive got stock recovery back on and OTA's are working. I'm still S-Off and boot loader unlocked.
The last think i need to do is get S-on and relock the bootloader. But in flashing the current firmware, HBoot is at 1.54.
Before I do any brash, does anyone know if revone one will still work to allow me to relock the bootloader and S-on?
If not will I have to downgrade Hboot to 1.44 and get S-On back on then reflash the firmware to upgrade HBoot back to 1.54?
I've also read that if there is anything other than stock HBoot and S-On you can brick the phone. But I take if the Hboot has upgraded from the OTA firmware this should be fine?
Thanks
Click to expand...
Click to collapse
I am on the same boat with you. unbranded Aussie One..
I had my own backup 1.29.980.17 from TWRP and restoring from my backup made my screen not working at all..
I have 1.54 hboot as well. Does 1.54 hboot and 4.1.2 doesnt work together? Isnt backup from xda is also 4.1.2 as well?
Sorry about asking question in your thread, but I just want to do same thing like you and I failed..
paul_59 said:
I would also advise against reverting to S on, because you won't be able to regain S off again, at least currently with 1.54 hboot.
If you wish to send for repair, my advice would be ensure you have stock recovery and stock Rom.
Use revone to remove tampered, and also relock bootloader .
No real need to revert to S on, as Soff doesn't indicate that you tampered with your device as a small number of HTC One were sold with S off
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I didnt think revone was compatable with 4.2.2?
i too am needing to remove TAMPERED from mine on 4.2.2 i have the stock rom and recovery now.
rotten.monkey said:
I didnt think revone was compatable with 4.2.2?
i too am needing to remove TAMPERED from mine on 4.2.2 i have the stock rom and recovery now.
Click to expand...
Click to collapse
It says tampered because you have some unsigned software installed. Probably hboot or recovery.
Hi,
I was going to update the rom on my HTC One and add the most recent luna kernel but when i download it i didn't look at where the thread was coming from and i think i downloaded to another device. Now, im still able to flash any rom but the SIM Card isn't detected. I've tried a nadroid backup but when i flash the rom i had i get the same issue, no SIM card.
Terramoto said:
Hi,
I was going to update the rom on my HTC One and add the most recent luna kernel but when i download it i didn't look at where the thread was coming from and i think i downloaded to another device. Now, im still able to flash any rom but the SIM Card isn't detected. I've tried a nadroid backup but when i flash the rom i had i get the same issue, no SIM card.
Click to expand...
Click to collapse
Try flashing latest radio and maybe firmware, this will generally fix. Worst case you would need to backup and ruu.
Sent from my HTC One on some Awesome Rom..
Hey,
I was able to S-ON my device but now i don't know what to do. My HBoot is 1.44 could someone point me in the right direction? Im currently downloading RUU 3.04.651.2 which is the one i get from getvar version-main.
Terramoto said:
Hey,
I was able to S-ON my device but now i don't know what to do. My HBoot is 1.44 could someone point me in the right direction? Im currently downloading RUU 3.04.651.2 which is the one i get from getvar version-main.
Click to expand...
Click to collapse
... buddy why did you go for s-on is out of my understanding. people yearn to get s-off and you did the opposite. its ok. you can s-off later. Now relock your bootloader and run RUU. your phone will be up and running. then again go for s-off after unlocking bootloader and flashing custom recovery and root ...
Devilish_Angel said:
... buddy why did you go for s-on is out of my understanding. people yearn to get s-off and you did the opposite. its ok. you can s-off later. Now relock your bootloader and run RUU. your phone will be up and running. then again go for s-off after unlocking bootloader and flashing custom recovery and root ...
Click to expand...
Click to collapse
Its all good now , I did S-Off because i read on flashing RUU tutorials that i needed to be S-Off before i run RUU
Terramoto said:
Its all good now , I did S-Off because i read on flashing RUU tutorials that i needed to be S-Off before i run RUU
Click to expand...
Click to collapse
.. you got it all wrong. its not necessary to be s-on to run RUU. RUU will do good on both s-on and s-off. its the bootloader which matters and that too when s-on. In simple words, if device is s-on you HAVE to relock bootloader to RUU and if device is s-off, no need to bother about bootloader status ...
Devilish_Angel said:
.. you got it all wrong. its not necessary to be s-on to run RUU. RUU will do good on both s-on and s-off. its the bootloader which matters and that too when s-on. In simple words, if device is s-on you HAVE to relock bootloader to RUU and if device is s-off, no need to bother about bootloader status ...
Click to expand...
Click to collapse
Yeah! I just learned something today, thanks!!
Currently I have an M7 UL on 4.4.2 with Sense 5.5. Its rooted and the bootloader is HTC Dev unlocked. I tried to S-OFF with firewater but I keep getting infinite lines so I gave up and I'm still S-ON
I'm not really bothered about the S-OFF anymore but would like to remove the ***TAMPERED*** bit thats there.
Also I have a few questions:
1) As I didn't try to do anything else my phone should be fine, right?
2) I want to install the ElementalX Kernel, Is it possible with S-OFF?
3) Can I still update using OTA's?
4) What are the methods to revert completely to stock with no root or unlock?
Since I'm new I hope you can help me with these questions. Thanks.
ss4adib said:
Currently I have an M7 UL on 4.4.2 with Sense 5.5. Its rooted and the bootloader is HTC Dev unlocked. I tried to S-OFF with firewater but I keep getting infinite lines so I gave up and I'm still S-ON
I'm not really bothered about the S-OFF anymore but would like to remove the ***TAMPERED*** bit thats there.
Also I have a few questions:
1) As I didn't try to do anything else my phone should be fine, right?
2) I want to install the ElementalX Kernel, Is it possible with S-OFF?
3) Can I still update using OTA's?
4) What are the methods to revert completely to stock with no root or unlock?
Since I'm new I hope you can help me with these questions. Thanks.
Click to expand...
Click to collapse
Removing ***TAMPERED*** requires S-OFF!
Going back to stock: (100% Stock also requires S-OFF)
http://forum.xda-developers.com/showthread.php?t=2358738
http://forum.xda-developers.com/showthread.php?t=2541082
You can still receive OTAs, but must be on STOCK Recovery.
Waiting4MyAndroid said:
Removing ***TAMPERED*** requires S-OFF!
Going back to stock:
http://forum.xda-developers.com/showthread.php?t=2358738
You can still receive OTAs, but must be on STOCK Recovery.
Click to expand...
Click to collapse
Thanks for the reply. How do I go S-OFF then?
ss4adib said:
Currently I have an M7 UL on 4.4.2 with Sense 5.5. Its rooted and the bootloader is HTC Dev unlocked. I tried to S-OFF with firewater but I keep getting infinite lines so I gave up and I'm still S-ON
I'm not really bothered about the S-OFF anymore but would like to remove the ***TAMPERED*** bit thats there.
Also I have a few questions:
1) As I didn't try to do anything else my phone should be fine, right?
2) I want to install the ElementalX Kernel, Is it possible with S-OFF?
3) Can I still update using OTA's?
4) What are the methods to revert completely to stock with no root or unlock?
Since I'm new I hope you can help me with these questions. Thanks.
Click to expand...
Click to collapse
ss4adib said:
Thanks for the reply. How do I go S-OFF then?
Click to expand...
Click to collapse
Try Rumrunner. Also try Firewater again make sure you follow directions. Rumrunner worked for me.
http://forum.xda-developers.com/showthread.php?t=2488772
ss4adib said:
Thanks for the reply. How do I go S-OFF then?
Click to expand...
Click to collapse
what's your phone hboot version ?
yatindroid said:
what's your phone hboot version ?
Click to expand...
Click to collapse
It's 1.56
try different roms and different kernals to get s-off, some people get it on stock, others don't, some have reported first try, other say they had to flash 10 different rom and kernel combinations.
Myself, I did it in one swift move by java card which I had to pay for.