Related
I was trying to obtain S-off through Juopunut Bear, but after it finds my device and tries to reboot it into its program, it simply doesn't reboot. The phone then will not start at all unless I pull the battery and boot into Hboot. From there I flashed my backup img through fastboot and I was good. I found this thread that said I need to ICS 3.32 firmware. On my phone I noticed I am on Software number 3.26.502.56, so I tried to flash the provided download of 3.32 using fastboot. And it did the same exact thing! Would not reboot, and had to battery-pull and re-flash my backup to get it to work.
What is my problem here?
I am on a unlocked and rooted HTC Vivid running stock ICS and stock Kernel.
I really hope I am not committing a stupid error and wasting everyone's time, but it is possible. Thanks in advance for any help!
lonehunter65 said:
I was trying to obtain S-off through Juopunut Bear, but after it finds my device and tries to reboot it into its program, it simply doesn't reboot. The phone then will not start at all unless I pull the battery and boot into Hboot. From there I flashed my backup img through fastboot and I was good. I found this thread that said I need to ICS 3.32 firmware. On my phone I noticed I am on Software number 3.26.502.56, so I tried to flash the provided download of 3.32 using fastboot. And it did the same exact thing! Would not reboot, and had to battery-pull and re-flash my backup to get it to work.
What is my problem here?
I am on a unlocked and rooted HTC Vivid running stock ICS and stock Kernel.
I really hope I am not committing a stupid error and wasting everyone's time, but it is possible. Thanks in advance for any help!
Click to expand...
Click to collapse
If you can get hboot relock the bootloader and run the stock ruu file seems to work for ant errors I've ever gotten , then just go back and redo every thing but s off it should stay off .
Bigtjmc said:
If you can get hboot relock the bootloader and run the stock ruu file seems to work for ant errors I've ever gotten , then just go back and redo every thing but s off it should stay off .
Click to expand...
Click to collapse
Not sure I'm completely understanding you. I need to relock and run stock ruu, then redo everything except s-off? That kind of defeats the purpose, I am trying to s-off
lonehunter65 said:
Not sure I'm completely understanding you. I need to relock and run stock ruu, then redo everything except s-off? That kind of defeats the purpose, I am trying to s-off
Click to expand...
Click to collapse
Yes if you are having problems after any mod to the os just relock the bootloader and run the stock ruu file and it will fix the issue , then go back after you got the phone working right and then unlock the bootloader , flash recovery , root , ect .
But the s-off should stay off and you won't have to redo that step .
So basically you will be on a stock ics with s-off
Then just redo the process to get it where you want it .
Bigtjmc said:
Yes if you are having problems after any mod to the os just relock the bootloader and run the stock ruu file and it will fix the issue , then go back after you got the phone working right and then unlock the bootloader , flash recovery , root , ect .
But the s-off should stay off and you won't have to redo that step .
So basically you will be on a stock ics with s-off
Then just redo the process to get it where you want it .
Click to expand...
Click to collapse
I'm sorry but this just doesn't make sense, the phone is automatically S-On not S-Off, so it won't 'stay s-off'. You understand what I mean?
lonehunter65 said:
I'm sorry but this just doesn't make sense, the phone is automatically S-On not S-Off, so it won't 'stay s-off'. You understand what I mean?
Click to expand...
Click to collapse
did you succeed s-off ?
if you did the s-off procedure via " wire trick " was successful the relocking the boot loader will not change the s-off it will stay off ,
Then relock. Run ruu now you are stock ics with the s-off still , and all the errors should be fixed .
Then just re unlock bl , flash recovery , root , flash New custom Rom / kernel, ect.
All I'm saying is if you have s-off then your good ,
To fix all the errors run the ruu , only reason you need to relock bl is the ruu will reject the install if you are unlocked .
Bigtjmc said:
did you succeed s-off ?
if you did the s-off procedure via " wire trick " was successful the relocking the boot loader will not change the s-off it will stay off ,
Then relock. Run ruu now you are stock ics with the s-off still , and all the errors should be fixed .
Then just re unlock bl , flash recovery , root , flash New custom Rom / kernel, ect.
All I'm saying is if you have s-off then your good ,
To fix all the errors run the ruu , only reason you need to relock bl is the ruu will reject the install if you are unlocked .
Click to expand...
Click to collapse
Oh, we are talking past each other. I did not succeed s-off, when it reboots my phone via Control Bear it does not boot into the Juopunut program, and I have never had a chance to do the wire trick! Thanks for the help though.
lonehunter65 said:
Oh, we are talking past each other. I did not succeed s-off, when it reboots my phone via Control Bear it does not boot into the Juopunut program, and I have never had a chance to do the wire trick! Thanks for the help though.
Click to expand...
Click to collapse
I had trouble on my first S-OFF attempt. I had made a mistake (I missed one of the S-OFF prep steps in section 2 of the SuperGuide, which is at http://forum.xda-developers.com/showthread.php?t=1416836 ).
If you want to try again?
-If you have relocked your bootloader, flash your phone stock using your appropriate RUU while phone is in Fastboot mode.
*** If you haven't relocked bootloader yet, you can do it first via fastboot ("fastboot oem lock")
-Start at section 1 of the superguide (unlocking the bootloader, yeah it sucks to do the process again but thankfully htc makes it easy!)
-And then you can try S-OFF process again (section 2 in superguide)
I know this is for the Vivid but I have the same problem with my EVO 3D. And Can get any help from anyone over there. I just relocked the evo but dont know the next step. Can anybody help me here?
gaarak54 said:
I know this is for the Vivid but I have the same problem with my EVO 3D. And Can get any help from anyone over there. I just relocked the evo but dont know the next step. Can anybody help me here?
Click to expand...
Click to collapse
Download the ruu from HTC or you should be able to download it from the EVO 3d forum while in fastboot mode hook you phone up to your computer fastboot should change to fastbootusb then double click on the ruu and let it do its thing do not unplug till it is finished then you will be out of box stock
Sent from my HTC PH39100 using Tapatalk 2
Hi guys,
just one quick question. I have my phone stuck in S-ON after upgrading into new firmware (HBOOT 1.54). It is clear that revone (the one I used to S-OFF the first time) is currently unable to S-OFF my phone right now. Therefore now I'm considering S-OFF through HTC Dev. Will HTC Dev S-OFF work with 1.54 HBOOT?
Another question would be, apart from getting wiped and lose some application, what disadvantage will S-OFF through HTC Dev brings?
Thanks for the help
you can unlock the bootloader and install custom roms/kernels but no s-off, which might be a problem if you need to send your phone to warranty because they could deny warranty on the re/unlocked status of the bootloader.
flamechamp said:
Hi guys,
just one quick question. I have my phone stuck in S-ON after upgrading into new firmware (HBOOT 1.54). It is clear that revone (the one I used to S-OFF the first time) is currently unable to S-OFF my phone right now. Therefore now I'm considering S-OFF through HTC Dev. Will HTC Dev S-OFF work with 1.54 HBOOT?
Another question would be, apart from getting wiped and lose some application, what disadvantage will S-OFF through HTC Dev brings?
Thanks for the help
Click to expand...
Click to collapse
Why did you s-on in the first place? You can't s-off, you're stuck for now. HTC Dev can only unlock your bootloader.
redbull123 said:
Why did you s-on in the first place? You can't s-off, you're stuck for now. HTC Dev can only unlock your bootloader.
Click to expand...
Click to collapse
I didn't S-ON it on purpose. It went S-ON automatically after firmware update and few resets. I have no slightest idea why it went S-ON. So... it seems I'm doomed for now...
godutch said:
you can unlock the bootloader and install custom roms/kernels but no s-off, which might be a problem if you need to send your phone to warranty because they could deny warranty on the re/unlocked status of the bootloader.
Click to expand...
Click to collapse
how am I suppose to install custom ROMs when I'm S-On now? I can't even flash custom recovery right?
flamechamp said:
how am I suppose to install custom ROMs when I'm S-On now? I can't even flash custom recovery right?
Click to expand...
Click to collapse
with htc dev unlock bootloader method you can, you dont need s-off to flash custom recovery and roms.
I know that could be somewhat confusing, but seems like you did not read enough
flamechamp said:
Hi guys,
just one quick question. I have my phone stuck in S-ON after upgrading into new firmware (HBOOT 1.54). It is clear that revone (the one I used to S-OFF the first time) is currently unable to S-OFF my phone right now. Therefore now I'm considering S-OFF through HTC Dev. Will HTC Dev S-OFF work with 1.54 HBOOT?
Another question would be, apart from getting wiped and lose some application, what disadvantage will S-OFF through HTC Dev brings?
Thanks for the help
Click to expand...
Click to collapse
Yeah the word is devs are workingbpn that but I heard still long time away
SLver said:
with htc dev unlock bootloader method you can, you dont need s-off to flash custom recovery and roms.
I know that could be somewhat confusing, but seems like you did not read enough
Click to expand...
Click to collapse
Any links maybe? Because as far as I know I need custom recovery to flash ROMs and to install custom recovery S-OFF is needed.
99piotrek said:
Yeah the word is devs are workingbpn that but I heard still long time away
Click to expand...
Click to collapse
I do hope the REVOLUTIONARY team finishes their work quickly...
flamechamp said:
Any links maybe? Because as far as I know I need custom recovery to flash ROMs and to install custom recovery S-OFF is needed.
Click to expand...
Click to collapse
With the HTC ONE toolkit you can unlock your bootloader and flash a custom recovery.
Very easy. I'm in the same situation at this moment. hboot 1.54.
I also got a question about this.
When I'm in the toolkit and I want to use the mainver error fix I always get Device not Found. Is this also because i'm on hboot 1.54 or maybe not a correct setting somwhere (adb?).
haenraets said:
With the HTC ONE toolkit you can unlock your bootloader and flash a custom recovery.
Very easy. I'm in the same situation at this moment. hboot 1.54.
I also got a question about this.
When I'm in the toolkit and I want to use the mainver error fix I always get Device not Found. Is this also because i'm on hboot 1.54 or maybe not a correct setting somwhere (adb?).
Click to expand...
Click to collapse
Oh but I must unlock my RELOCKED bootloader to install the recovery right?
flamechamp said:
Oh but I must unlock my RELOCKED bootloader to install the recovery right?
Click to expand...
Click to collapse
Yes... That is correct and once you unlock it you can use the all in one kit to flash a recovery and then you can flash the rom of your choice
Sent from my ViperOne
flamechamp said:
Oh but I must unlock my RELOCKED bootloader to install the recovery right?
Click to expand...
Click to collapse
Yes, and you can do this with the toolkit.
leohdz148 said:
Yes... That is correct and once you unlock it you can use the all in one kit to flash a recovery and then you can flash the rom of your choice
Sent from my ViperOne
Click to expand...
Click to collapse
haenraets said:
Yes, and you can do this with the toolkit.
Click to expand...
Click to collapse
But through the toolkit, the unlocking process will use the HTC Dev method which erases the phone's internal memory and some part which contains some apps right? Any other cons which shouldn't I unlock through HTC Dev?
Here it is but be careful
flamechamp said:
Any links maybe? Because as far as I know I need custom recovery to flash ROMs and to install custom recovery S-OFF is needed.
Click to expand...
Click to collapse
Go there, register an account
http://www.htcdev.com/
after that click on the "developer center" button and right in the middle you will find a "unlock bootloader" button
click on it, follow instructions, but make sure you have a full backup of your storage cause it will be erased
S-OFF is a security flag that gives you permission to "play" with organic partitions of the devices system in a way
you don't need it for having custom recovery, after you unlock you can flash a recovery the exact same way you did with S-OFF or restore a backup you did before reverting to complete stock
S-OFF for most users is only a solution to not losing warranty after unlocking as unlocking actually voids your software warranty and in a way the hardware warranty as HTC can claim that the unofficial software you used actually damaged the device.
If I helped to make you understand in any way I am glad but please if you don't understand what these procedures do or how they work in a general sense it's better not to use/perform them, if you are in any way like me who spent the better part of a salary to buy this phone it would be a shame wasting all that money bricking it out of ignorance, if not, it's still a shame.
flamechamp said:
But through the toolkit, the unlocking process will use the HTC Dev method which erases the phone's internal memory and some part which contains some apps right? Any other cons which shouldn't I unlock through HTC Dev?
Click to expand...
Click to collapse
Yea it wipes everything so I suggest you back up anything important to you before you unlock... And there aren't any other cons except the fact that it will wipe EVERYTHING (apps, contacts synced with phone, music, pictures, etc.), thats the only con to it
Sent from my ViperOne
I think there is some confusion here for the OP.
First, S-off and unlocking your bootloader are 2 completely different things. To install custom recoveries, and therefore custom Roms and kernels, you need an unlocked bootloader (I am not sue what all the talk of relocking was about). The only way for you to unlock at this point is with HTCdev, and this will wipe your device unfortunately. Their are guides to unlocking and rooting your phone in this very forum
dgtiii said:
I think there is some confusion here for the OP.
First, S-off and unlocking your bootloader are 2 completely different things. To install custom recoveries, and therefore custom Roms and kernels, you need an unlocked bootloader (I am not sue what all the talk of relocking was about). The only way for you to unlock at this point is with HTCdev, and this will wipe your device unfortunately. Their are guides to unlocking and rooting your phone in this very forum
Click to expand...
Click to collapse
Yes, I got things mixed up. I got so frustrated with S-ON such that I forgot that the real problem is the RELOCKED status of my phone. Thanks for reminding me
But i do need S-OFF to flash splash screen right?
flamechamp said:
Yes, I got things mixed up. I got so frustrated with S-ON such that I forgot that the real problem is the RELOCKED status of my phone. Thanks for reminding me
Click to expand...
Click to collapse
No problem, glad to help.....
flamechamp said:
Yes, I got things mixed up. I got so frustrated with S-ON such that I forgot that the real problem is the RELOCKED status of my phone. Thanks for reminding me
Click to expand...
Click to collapse
??? There was no talk from anyone about 'relocking'. You were told about 5 times you had to unlock your bootloader.
Sent from my HTC One using xda premium 4
redbull123 said:
??? There was no talk from anyone about 'relocking'. You were told about 5 times you had to unlock your bootloader.
Sent from my HTC One using xda premium 4
Click to expand...
Click to collapse
no, I got it relocked to update my firmware last time. But can't have it unlocked now. But now I know that using HTC Dev method, it will be solved.
But I do need S-OFF to flash splash screen right?
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
htc one m7 said:
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
Click to expand...
Click to collapse
I am in exactly the same boat
here is my setup
HBOOT: 1.54.0000
OS: 2.24.401.1
Looking for the correct RUU to flash. any help is appreciated
winwiz said:
I am in exactly the same boat
here is my setup
HBOOT: 1.54.0000
OS: 2.24.401.1
Looking for the correct RUU to flash. any help is appreciated
Click to expand...
Click to collapse
this will be my last and first HTC to root
i had gs3 i flash a home rom any second i wanted im searching for that RUU from 1 month ago i dint find it
htc customer services and htc dev both sucks
htc one m7 said:
this will be my last and first HTC to root
i had gs3 i flash a home rom any second i wanted im searching for that RUU from 1 month ago i dint find it
htc customer services and htc dev both sucks
Click to expand...
Click to collapse
I realised that I took a nandroid backup of the original firmware, so I have been successful in returning to stock.
When I boot to the bootloader, I see TAMPERED AND UNLOCKED. I guess this is to to a custom recovery and also unlocked bootloader. Any ideas how I can get this back to normal? Am I then back to stock fully?
winwiz said:
I realised that I took a nandroid backup of the original firmware, so I have been successful in returning to stock.
When I boot to the bootloader, I see TAMPERED AND UNLOCKED. I guess this is to to a custom recovery and also unlocked bootloader. Any ideas how I can get this back to normal? Am I then back to stock fully?
Click to expand...
Click to collapse
me i have my stuck rom running also nandroid pulled by cmd
but no chance for me
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
AllAboutTheCore said:
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Click to expand...
Click to collapse
thanks next time when i need a root i will get s-off before that .now my chance is getting s-off wich is not available now
if u dint tell me dont search i would search for ever XD
iElvis said:
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
Click to expand...
Click to collapse
i just want to get updates from htc
AllAboutTheCore said:
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Click to expand...
Click to collapse
Noobs are what this thread is for. Why are you flaming and complaining in a Q&A thread anyway? If you're not going to help, get out of the way and flame on elsewhere.
htc one m7 said:
i just want to get updates from htc
Click to expand...
Click to collapse
Then you should've left the phone stock
htc one m7 said:
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
Click to expand...
Click to collapse
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Edit: Finally, have you tried unrooting through the SU app itself?
kibmikey1 said:
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. If you used the revone method to root, it should take care of it. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Click to expand...
Click to collapse
I've personally managed to get it back to stock, and even got an OTA update. The only issue I have is that in the bootloader it's saying TAMPERED and RELOCKED
I guess there is not much I can do about this,
Any above all, thank you for your help. You have been helpful unlike the others with a snobbish attitude
winwiz said:
I've personally managed to get it back to stock, and even got an OTA update. The only issue I have is that in the bootloader it's saying TAMPERED and RELOCKED
I guess there is not much I can do about this,
Any above all, thank you for your help. You have been helpful unlike the others with a snobbish attitude
Click to expand...
Click to collapse
You could run the all in one toolkit and remove the tampered and relocked flags.
---------- Post added at 02:06 AM ---------- Previous post was at 01:17 AM ----------
iElvis said:
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
Click to expand...
Click to collapse
This thread is open for questions like these. Flame on elsewhere.
kibmikey1 said:
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Edit: Finally, have you tried unrooting through the SU app itself?
Click to expand...
Click to collapse
unrooting thrrough su app dint work and that tool kit s wont work for 1.54 hboot im so unlucky
htc one m7 said:
unrooting thrrough su app dint work and that tool kit s wont work for 1.54 hboot im so unlucky
Click to expand...
Click to collapse
If your phone was 2.24 out of the box and you never went s-off, you don't need a ruu because your firmware would not have changed. So you just need to restore stock recovery and stock system files, then relock. Flash a stock rom, flash stock recovery in fastboot, and unroot through the superuser app. Then relock in fastboot.
The AIO toolkits will not help with relocked and tampered on 1.54 because they require s-off, which is not available on that hboot. Also, factory reset won't unroot you; it may remove the superuser.apk but will not remove root access.
kibmikey1 said:
Noobs are what this thread is for. Why are you flaming and complaining in a Q&A thread anyway? If you're not going to help, get out of the way and flame on elsewhere.
Click to expand...
Click to collapse
Who's flaming and complaining, and I did help ... I wouldn't help you now but that's another story. As for noobs, If you can't be bothered to read and search then that says something about you. For starters, even though you were wrong (and not the OP) I did help, I have also spent more time helping on here than I have posting anything else, so if you don't like it, you know what you can do.
You might want to give correct advice aswell, if he's on Hboot 1.54 then he'd need S-Off to flash an older Hboot, which he cannot do. Thanks
iElvis said:
If your phone was 2.24 out of the box and you never went s-off, you don't need a ruu because your firmware would not have changed. So you just need to restore stock recovery and stock system files, then relock. Flash a stock rom, flash stock recovery in fastboot, and unroot through the superuser app. Then relock in fastboot.
The AIO toolkits will not help with relocked and tampered on 1.54 because they require s-off, which is not available on that hboot. Also, factory reset won't unroot you; it may remove the superuser.apk but will not remove root access.
Click to expand...
Click to collapse
when i red your reply it seemed too easy but no
stuck recovery when you mean that ''fastboot flash recovery recovery.img'' pulled from nandroid back up ? yes ur right i manged to do that it was succesful but no change even a systim rom is not available getting signature failure 'seems promising yah
i know my thing is hard but it shouldnt be like that right im runing a rom now 4.3 im fine with it but i really want to F*** htcdev members :v
I mean stock recovery, which you can pull from the firmware file for your phone. Find the recovery.img file in the zip and use that.
Stop trying to flash ruus and firmware packages in fastboot; you may screw up your phone doing it.
Just get a stock rom that correspond to the firmware package from the development forum and flash in custom recovery. Then flash the stock recovery in fastboot. Once that's done, you should be able to get OTAs.
iElvis said:
I mean stock recovery, which you can pull from the firmware file for your phone. Find the recovery.img file in the zip and use that.
Stop trying to flash ruus and firmware packages in fastboot; you may screw up your phone doing it.
Just get a stock rom that correspond to the firmware package from the development forum and flash in custom recovery. Then flash the stock recovery in fastboot. Once that's done, you should be able to get OTAs.
Click to expand...
Click to collapse
if you want to help me help me now
i have my reovery.img and it flashes perfectly
how to get stuck rom ?
you mean the file with date it is bout 1.8GB named 2013-08-27.19.58.35 that i should put it in supfic folder do i can flash it with recovery cwm ?
since i have my back up and since it is S-on i wont mind flashing any thing
Hey guys,
I've been rocking my Canadian, Bell HTC One for a little over 5 months. It's a great phone, but as any tinkerer knows... You don't get the full power of a device till your root it.
I've been meaning to root my device, but I am afraid of having to take it back for warranty reasons. I am paying an additional $7/month for those extended warranty services.
I came across a thread the other day that suggests that you can go back 100% stock if you have S-off.
I guess you can see why I want to examine this option further.
Apparently I'm lucky, I've got hboot version 1.44 and s-off should be pretty simple.
The reason I bring this up now, and not later/earlier, is because the 4.3 update has just been pushed to my device. I have not yet accepted the update as I'm afraid that my hboot will update along with the OS, therefore making it more difficult to go s-off and rooting.
How difficult is to go s-off?
Is it necessary to go S-off to make the device look 100% stock to the manufacturer incase anything happens?
Would accepting the OTA update update my hboot version?
I understand going s-off isn't for the faint of heart, and that the slightest mistake I make will brick my device. But if it gives me the option of going back to stock 100%, it's a risk I'm willing to take.
Hasoon2000's software/guide makes the rooting and S-OFF process very simple. Check out the link below, and as always read as much as possible before ever modifying your phone. Good luck!
http://forum.xda-developers.com/showthread.php?t=2183942
Sent from my HTC One using Tapatalk 4
WolfDale7 said:
Hey guys,
I've been rocking my Canadian, Bell HTC One for a little over 5 months. It's a great phone, but as any tinkerer knows... You don't get the full power of a device till your root it.
I've been meaning to root my device, but I am afraid of having to take it back for warranty reasons. I am paying an additional $7/month for those extended warranty services.
I came across a thread the other day that suggests that you can go back 100% stock if you have S-off.
I guess you can see why I want to examine this option further.
Apparently I'm lucky, I've got hboot version 1.44 and s-off should be pretty simple.
The reason I bring this up now, and not later/earlier, is because the 4.3 update has just been pushed to my device. I have not yet accepted the update as I'm afraid that my hboot will update along with the OS, therefore making it more difficult to go s-off and rooting.
How difficult is to go s-off?
Is it necessary to go S-off to make the device look 100% stock to the manufacturer incase anything happens?
Would accepting the OTA update update my hboot version?
I understand going s-off isn't for the faint of heart, and that the slightest mistake I make will brick my device. But if it gives me the option of going back to stock 100%, it's a risk I'm willing to take.
Click to expand...
Click to collapse
Hi!
I will advice you to go in S-OFF.
It's easy and you can restore to 100% stock your phone in case of warranty
You can do the S-OFF with the revone tool.
After the S-OFF you can get the OTA and you will update your hboot, but, if you want my advice, don't use the OTA from your carrier.
Is better flash a stock rom with the new firmware from Bell.
In case of warranty, you can use a ruu for porting your phone to stock or using a nandroid backup that you can make after the s-off and the flash of a custom recovery
Thrashlord said:
Hasoon2000's software/guide makes the rooting and S-OFF process very simple. Check out the link below, and as always read as much as possible before ever modifying your phone. Good luck!
http://forum.xda-developers.com/showthread.php?t=2183942
Click to expand...
Click to collapse
As you can see, the Link for the download was removed and the thread is closed.
And any link at the tool isn't accepted here
Good looks Guich, thank you for the correction!
Sent from my HTC One using Tapatalk 4
Guich said:
Hi!
I will advice you to go in S-OFF.
It's easy and you can restore to 100% stock your phone in case of warranty
You can do the S-OFF with the revone tool.
After the S-OFF you can get the OTA and you will update your hboot, but, if you want my advice, don't use the OTA from your carrier.
Is better flash a stock rom with the new firmware from Bell.
In case of warranty, you can use a ruu for porting your phone to stock or using a nandroid backup that you can make after the s-off and the flash of a custom recovery
As you can see, the Link for the download was removed and the thread is closed.
And any link at the tool isn't accepted here
Click to expand...
Click to collapse
Thrashlord said:
Good looks Guich, thank you for the correction!
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Thanks guys!!
Just another question (might have a lot more as I go through the process), if I were to root, go s-off, then have the screen cracked and have to take it back to my carrier, I would then go back stock, s-on, then unroot, would they be able to tell that I messed with it?
I have previously heard of the bootloader status change fro "locked" to "relocked". Any way to avoid that?
WolfDale7 said:
Thanks guys!!
Just another question (might have a lot more as I go through the process), if I were to root, go s-off, then have the screen cracked and have to take it back to my carrier, I would then go back stock, s-on, then unroot, would they be able to tell that I messed with it?
I have previously heard of the bootloader status change fro "locked" to "relocked". Any way to avoid that?
Click to expand...
Click to collapse
If you will broke your screen you can return to 100% stock with a ruu
For the locked line: revone tool, this can do this too
Guich said:
If you will broke your screen you can return to 100% stock with a ruu
For the locked line: revone tool, this can do this too
Click to expand...
Click to collapse
Thanks for everything!
I am, however, stuck on step 6.
After completing step 11 (run command: ./revone -s 0 -u), I get error code = -1. Can't seem to find much on that specific error. I've been at it for a little over an hour. I've tried starting over, I've tried holding the power button for 15 seconds after I hit restart (after./revone -P). Everything reads success till that step 11..
At one point earlier on, though, it did say that revone was successful. Upon rebooting my device and checking to see if it was s-off, I saw the s-on tag... Odd .
I'm confused as to how I should proceed.. I'm not rooted and don't intend on rooting just yet (am not ready to have all my data wiped). If only there's a reliable way to get all my apps, app settings, app data, and everything else mirrored on my computer so I can mirror them back after root/unlocked bootloader.
Wow, I came home and tried again. Guess it needed some time!
Thanks =] S-off and unlocked!
Sent from my HTC One using XDA Premium 4 mobile app
Guich said:
If you will broke your screen you can return to 100% stock with a ruu
Click to expand...
Click to collapse
Assuming there is an RUU for the OPs handset. You can't just shove any old RUU on it as HTC will know it's not the original ROM
hi everyone, i have a question and hopefully someone can help me here, i am following this guide: http://forum.xda-developers.com/showthread.php?t=2358738 and i already flashed the ruu and i am back to stock as it should be, but i am stuck the the steps 1 and 2. after flashing the ruu, it says "Before you can proceed with the 2 following threads for removing Tampered and then Locking you need to have Superuser installed. There are links to how to do this in each thread. You can also use this toolkit. Just remember to delete the SuperUser and busybox apk if installed before you return the phone."
my problem is that even when i go to those threads i get stuck, i am not sure what to do, ofcourse after running the ruu, i don't have SU, so do i need to root the stock rom? do i need to install a recovery? If someone could help i would immensely appreciate it, I got a replacement and i need to return the old phone.
by the way, I am s-off and hboot 1.55
juanshop said:
hi everyone, i have a question and hopefully someone can help me here, i am following this guide: http://forum.xda-developers.com/showthread.php?t=2358738 and i already flashed the ruu and i am back to stock as it should be, but i am stuck the the steps 1 and 2. after flashing the ruu, it says "Before you can proceed with the 2 following threads for removing Tampered and then Locking you need to have Superuser installed. There are links to how to do this in each thread. You can also use this toolkit. Just remember to delete the SuperUser and busybox apk if installed before you return the phone."
my problem is that even when i go to those threads i get stuck, i am not sure what to do, ofcourse after running the ruu, i don't have SU, so do i need to root the stock rom? do i need to install a recovery? If someone could help i would immensely appreciate it, I got a replacement and i need to return the old phone.
by the way, I am s-off and hboot 1.55
Click to expand...
Click to collapse
if you're returning it you don't want root or custom recovery
juanshop said:
hi everyone, i have a question and hopefully someone can help me here, i am following this guide: http://forum.xda-developers.com/showthread.php?t=2358738 and i already flashed the ruu and i am back to stock as it should be, but i am stuck the the steps 1 and 2. after flashing the ruu, it says "Before you can proceed with the 2 following threads for removing Tampered and then Locking you need to have Superuser installed. There are links to how to do this in each thread. You can also use this toolkit. Just remember to delete the SuperUser and busybox apk if installed before you return the phone."
my problem is that even when i go to those threads i get stuck, i am not sure what to do, ofcourse after running the ruu, i don't have SU, so do i need to root the stock rom? do i need to install a recovery? If someone could help i would immensely appreciate it, I got a replacement and i need to return the old phone.
by the way, I am s-off and hboot 1.55
Click to expand...
Click to collapse
you should go read nkk71's guide linked in my signature. Take time to read post #1 carefully and completely.
alray said:
you should go read nkk71's guide linked in my signature. Take time to read post #1 carefully and completely.
Click to expand...
Click to collapse
thank you very much, this guide is much clear. i really appreciate it very much!
alray said:
you should go read nkk71's guide linked in my signature. Take time to read post #1 carefully and completely.
Click to expand...
Click to collapse
nevermind.
juanshop said:
thank you very much, this guide is much clear. i really appreciate it very much!
Click to expand...
Click to collapse
Don't thanks me thanks nkk71 for his awesome guide!
alray said:
Don't thanks me thanks nkk71 for his awesome guide!
Click to expand...
Click to collapse
thanks for guiding me there! ahahaha, one question though, since i am in hboot 1.55, will the tampered thing will appear? that is a given? i really need to get s-on so i can send the device back to tmobile. would i need to downgrade to 1.44? or what can i do in that aspect?
edit: once again never mind, i downgraded to 1.44 no problem. i am a happy camper and can send the phone on its way
juanshop said:
thanks for guiding me there! ahahaha, one question though, since i am in hboot 1.55, will the tampered thing will appear? that is a given? i really need to get s-on so i can send the device back to tmobile. would i need to downgrade to 1.44? or what can i do in that aspect?
edit: once again never mind, i downgraded to 1.44 no problem.
Click to expand...
Click to collapse
Exactly don't turn security on with hboot 1.55 or the tampered flag will come after a few reboot. Do it on hboot 1.44 or 1.54
Click to expand...
Click to collapse