Related
Okay so i was going to sell my phone so i want to unroot(not go back to s-on just unroot) so i did that but my friend ended up buying it from me instead and asked me to root it for him....How would i go about doing that since i already have s-off.
i tried just flashing su but got an error, i also tried using to revolution tool but that was a no go either....
Any help with this is much appreciated
Follow the instructions exactly: http://forum.xda-developers.com/showthread.php?t=1286324
after i flashed the stock unrooted ROM, i was unable to flash CWM Recovery, so i ran Revolutionary again. it gave an error saying something like communication has stopped, please try again later.... but it had already reflashed the bootloader, so all was well after that, i was able to flash CWM and root like usual.
Today I went to reclock my bootloade on my evo design 4g. After it was locked I get a Security warning. The only way to get to the phone is to unlock it again.. Now I have a custom recovery installed CWM 5.0.2.7 installed. Now I was trying to but back stock recovery so I can get the new ics update when it come out.. But everything I have tried as failed in trying to reinstall stock recover or get future ota updates.. I hear I need to push it to the phone using adb, but not sure how it is done.. Can someone please post instructions on how this is done.. This is the second phone with the security warning issue I have had since unlocking the bootloader, and no one knows why it happens even HTC.
This thread can be closed. I solved my problem sort of. I managed to flash my stock recovery with bootloader still unlocked. Next was able to download and install OTA updates with bootloader still unlocked.. Now have all files necessary incase I run into same issue again.. So no need for this thread to stay open..
Some months ago I followed guides here to SuperCID, s-off and install a custom ROM. The past few days my touch screen has become unresponsive, at first this was fixed by reflashing the ROM, but now, nothing will fix it, and the touch screen is completely unresponsive. So it seems I will have to return it to the shop to send off for repair. Of course I don't want them to have any reason to say it was the custom ROM that has caused it, warranty void blah blah so need to restore it to stock.
So far I have re-flashed with a stock ROM and changed the CID to what it was, and s-on. I can't remember whether I changed the MID, currently it is PG58*****, though I believe it should be PG5813001, and I'm not sure how to go about changing this (or if it needs changing, will they look into that?)
Another thing I'm unsure of, I downloaded the ROM from here: http://forum.xda-developers.com/showthread.php?t=1074559 I don't know if these ROMs are rooted or not? Is there any way to tell? Or is it a safe assumption they are not?
And finally, hboot, before flashing the stock ROM, this was 1.17, now it is 1.18. Is there anything in here that might suggest the phone has been tinkered with in ways they don't like? I just want to make sure I have covered everything so they don't immediately refuse to repair. If I have missed anything else please let me know.
Thanks.
Edit: I've also read about flashing stock recovery, though this may be included in the the stock ROM RUU I used, can someone confirm?
None of the 130 viewers have any advice on this one?
HB489 said:
Some months ago I followed guides here to SuperCID, s-off and install a custom ROM. The past few days my touch screen has become unresponsive, at first this was fixed by reflashing the ROM, but now, nothing will fix it, and the touch screen is completely unresponsive. So it seems I will have to return it to the shop to send off for repair. Of course I don't want them to have any reason to say it was the custom ROM that has caused it, warranty void blah blah so need to restore it to stock.
So far I have re-flashed with a stock ROM and changed the CID to what it was, and s-on. I can't remember whether I changed the MID, currently it is PG58*****, though I believe it should be PG5813001, and I'm not sure how to go about changing this (or if it needs changing, will they look into that?)
Another thing I'm unsure of, I downloaded the ROM from here: http://forum.xda-developers.com/showthread.php?t=1074559 I don't know if these ROMs are rooted or not? Is there any way to tell? Or is it a safe assumption they are not?
And finally, hboot, before flashing the stock ROM, this was 1.17, now it is 1.18. Is there anything in here that might suggest the phone has been tinkered with in ways they don't like? I just want to make sure I have covered everything so they don't immediately refuse to repair. If I have missed anything else please let me know.
Thanks.
Edit: I've also read about flashing stock recovery, though this may be included in the the stock ROM RUU I used, can someone confirm?
Click to expand...
Click to collapse
To Flash stock recovery read 2 in HERE I believe these ROMs are not rooted, to check just look for SuperSU or Superuser app, if it is not installed you are not rooted. Don't worry at all they'll never find out you rooted your phone, usually they never check. Read THIS guide it has the answer to all your questions regarding revert to stock
elvisypi said:
To Flash stock recovery read 2 in HERE I believe these ROMs are not rooted, to check just look for SuperSU or Superuser app, if it is not installed you are not rooted. Don't worry at all they'll never find out you rooted your phone, usually they never check. Read THIS guide it has the answer to all your questions regarding revert to stock
Click to expand...
Click to collapse
Thanks, though unfortunately I can't check what apps are installed due to the touch screen being unresponsive. But if that's not something they'll look into then fair enough.
The second thread doesn't quite answer everything (whether the ROMs are rooted for example), however, the first thread details extracting stock recovery from an RUU, so I guess that means I don't need to worry about that as it would have been flashed with the ROM.
One other thing - do they require the SD card to be sent also? Is there anything on there that should be removed? Any data relating to apps that use root privileges might raise an eyebrow; is it safe to do a reformat of the SD card? I'm not sure how much is on there that is vital the system.
Thanks for your answer.
HB489 said:
Thanks, though unfortunately I can't check what apps are installed due to the touch screen being unresponsive. But if that's not something they'll look into then fair enough.
The second thread doesn't quite answer everything (whether the ROMs are rooted for example), however, the first thread details extracting stock recovery from an RUU, so I guess that means I don't need to worry about that as it would have been flashed with the ROM.
One other thing - do they require the SD card to be sent also? Is there anything on there that should be removed? Any data relating to apps that use root privileges might raise an eyebrow; is it safe to do a reformat of the SD card? I'm not sure how much is on there that is vital the system.
Thanks for your answer.
Click to expand...
Click to collapse
No the ROMs in the second post are not rooted they are stock. The whole point of the post is to restore stock( read 3. RUU to restore stock). Stock recovery is smth else from stock ROM. You also need stock recovery to install OTA updates from google. Use Android Recovery Manager to download and install your stock recovery. Than in fastboot the stock recovery.img. I can't assure you that they won't notice you were rooted, but they usually don't. Keep in mind that when you unlocked your bootloader you accepted to void your warranty, and your serial number is in HTCs website. (theoretically) you can never be sure they won't discover you, but practically installing stock ROM, stock recovery, locking bootloader and getting back to s-on is enough to not get spotted
And you can format the SD Card if you want, you made a fresh install so there shouldn't be any files regarding it, just the files from the old system, but do a backup first just in case
elvisypi said:
No the ROMs in the second post are not rooted they are stock. The whole point of the post is to restore stock( read 3. RUU to restore stock). Stock recovery is smth else from stock ROM. You also need stock recovery to install OTA updates from google. Use Android Recovery Manager to download and install your stock recovery. Than in fastboot the stock recovery.img. I can't assure you that they won't notice you were rooted, but they usually don't. Keep in mind that when you unlocked your bootloader you accepted to void your warranty, and your serial number is in HTCs website. (theoretically) you can never be sure they won't discover you, but practically installing stock ROM, stock recovery, locking bootloader and getting back to s-on is enough to not get spotted
And you can format the SD Card if you want, you made a fresh install so there shouldn't be any files regarding it, just the files from the old system, but do a backup first just in case
Click to expand...
Click to collapse
Thanks again. If I recall correctly I used revolutionary, not HTC dev so I don't think they'll have my imei? Android recovery manager doesn't have the correct version for my phone, but further down the post it another method is extracting the recovery from the RUU, which is why I assumed stock recovery would have been installed when I flashed the RUU. I guess there is no harm in manually flashing the recovery to be sure though.
HB489 said:
Thanks again. If I recall correctly I used revolutionary, not HTC dev so I don't think they'll have my imei? Android recovery manager doesn't have the correct version for my phone, but further down the post it another method is extracting the recovery from the RUU, which is why I assumed stock recovery would have been installed when I flashed the RUU. I guess there is no harm in manually flashing the recovery to be sure though.
Click to expand...
Click to collapse
No HTCdev is not a recovery, it's the only way of unlocking your bootloader, which you have done for sure. But don't worry I assure you they don't go so deep. There's nothing wrong in flashing manually the recovery. Good luck
Alright, I have looked and tried almost everything I could find to help me on this but nothing has worked yet, my problem is my screen gets stuck in the HTC boot screen and won't move any further, what I did to get it to this is I got my shift rooted though the htcdev site, but it is not s-off, I wanted to install a cyanogen mod, the 7.2 one on it, well i went to CWM and said install aborted so I tried to reboot my phone and now stuck, i can still get into the CWM recovery but nothing has helped yet,I have tried to push several boot.img files, and tried to downgrade to 2.2 and nothing...I am all up for ideas.
EDIT: I have done some tweaking with restoring my old back up and I have come to the conclusion that my /system folder is corrupt, i know a few ways to fix that but anyone one the best way and maybe a 2.3.4 system folder to use?
EDIT2: I replaced my system folder with one that i have and now it gets past the white htc screen but will loop the sprint 4g screens.
FIXED IT,\: what I did was I managed to RUU back to 2.2 through this thread, now I am on 2.2 and will continue to get an s-off root, thank you for all your help
11telisz said:
Alright, I have looked and tried almost everything I could find to help me on this but nothing has worked yet, my problem is my screen gets stuck in the HTC boot screen and won't move any further, what I did to get it to this is I got my shift rooted though the htcdev site, but it is not s-off, I wanted to install a cyanogen mod, the 7.2 one on it, well i went to CWM and said install aborted so I tried to reboot my phone and now stuck, i can still get into the CWM recovery but nothing has helped yet,I have tried to push several boot.img files, and tried to downgrade to 2.2 and nothing...I am all up for ideas.
Click to expand...
Click to collapse
Can you get into bootloader? If so, what is your hboot version and software version?
Just in case you don't know how, to get into bootloader, you need to power off or pull battery, then press and hold VolDown+Power until the white bootloader screen comes up
At the top it tells you the hboot version
Sent from my PG06100 using xda premium
I can get into bootloader.
hboot-0.99.0001
radio-1.08.01.0111
thats all I can get about my version
11telisz said:
Alright, I have looked and tried almost everything I could find to help me on this but nothing has worked yet, my problem is my screen gets stuck in the HTC boot screen and won't move any further, what I did to get it to this is I got my shift rooted though the htcdev site, but it is not s-off, I wanted to install a cyanogen mod, the 7.2 one on it, well i went to CWM and said install aborted so I tried to reboot my phone and now stuck, i can still get into the CWM recovery but nothing has helped yet,I have tried to push several boot.img files, and tried to downgrade to 2.2 and nothing...I am all up for ideas.
Click to expand...
Click to collapse
When you went through HTC-Dev.com you did not Root the Device. All you can do at the site is Unlock the Bootloader. To resolve the issue you can try a Factory Data Restore in Bootloader, but you are going to lose all the current Data on the Device. It may or may not work. If it does not then, you may have to run an RUU. To do the Factory Restore pull the Battery on the device. Then put the Battery back in. Hold Volume Button down , now at the same time press the Power Button. It will boot into Bootloader. Once it is in Bootloader use the Volume Rockers to toggle Up, or Down. Then choose Factory Restore by pressing the Pwer Button. Since your not rooted that's your only option that I know of other than an RUU. If that does get you out of the White Screen I would suggest finding out your Android version. Then following the correct process to attain Full Root.
Maybe I was a bit unclear, I went though the htcdev site to unlock the bootloader, then i moved clockworkmod recovery instead of the stock recovery, i then installed superuser through Clockworkmod, so i had root though that, but not an s-off root, so I then installed ROM manager and thought the cyanogen 7.2 rom would be a cool one to have, I forgot it was not an s-off root, so i went ahead with downloading it though Rom manager and it prompted me to install the new rom, and brought me to clockworkmod recovery and said the install was aborted, and i rebooted and then it got stuck at the htc screen, I can get into bootloader and clockworkmod recovery, I have a backup of my stock rom on my computer and put it onto my sd card hoping i can restore to that one, but i get the md5 mismatch error, working on fixing that now.
I still believe that most of the issue is that you are not Fully Rooted. What version of Android where you on when you started ? The reason I ask is because the method you used is a bit unorthodox, so I doubt your Rooted. I would still suggest doing a factory Restore. But you can look HERE on how to fix the MD5 mismatch error.
Yeah, if you only unlocked bootloader, thats not a full root, you still have a ways to go
The best thing would be to just RUU and start over using VICODAN's method, which covers 2.2 all the way up to 2.3.4
Sent from my PG06100 using xda premium
The method i used for rooting was though this post, I got up to the step downgrading from 2.3.4 to 2.2 till about step 17 of the 2.3.4, I wasn't sure if it acutally downgraded to 2.2 because I am unable to check my version though the bootloader or clockworkmod recovery, so I most likely am still on 2.3.4
11telisz said:
The method i used for rooting was though this post, I got up to the step downgrading from 2.3.4 to 2.2 till about step 17 of the 2.3.4, I wasn't sure if it acutally downgraded to 2.2 because I am unable to check my version though the bootloader or clockworkmod recovery, so I most likely am still on 2.3.4
Click to expand...
Click to collapse
Ok so your defiantly not on 2.2 . The question is what version of 2.3.4 are you on ? Go into HBoot and go to System Info. What is the OS Ver. ? Have you tried doing a Factory Reset just to see if it will Boot back up ?
prboy1969 said:
Ok so your defiantly not on 2.2 . The question is what version of 2.3.4 are you on ? Go into HBoot and go to System Info. What is the OS Ver. ? Have you tried doing a Factory Reset just to see if it will Boot back up ?
Click to expand...
Click to collapse
There is no system info tab in my hboot menu, but i believe i know what is wrong, somehow my /system folder got corrupt, so i have to replace my /system folder with a new one, i know a few methods but what is the best method to going about that with an s-on?
11telisz said:
There is no system info tab in my hboot menu, but i believe i know what is wrong, somehow my /system folder got corrupt, so i have to replace my /system folder with a new one, i know a few methods but what is the best method to going about that with an s-on?
Click to expand...
Click to collapse
The only way I know how to do it would be using adb and just flashing all the images through that.
Sent from my PG06100 using xda premium
Hi,
I rooted using the wug tool and have had to unrrot.
I bought my Nexus from CEX and its started getting screen bleed around all edges so I'm going to take it back to CEX and their warranty says if a phones ever had custom ROM or anything installed it invalidates the 2 year warranty and they thoroughly check the phone when you take it back.
Unroot and relocking the bootloader worked fine but when I went in to stock recovery and check recovery logs there was cache/recovery/last_log.1 which when read you can tell that it's had twrp installed and uninstalled and that the bootloader has been relocked.
I've used stock recovery from bootloader to wipe cache etc and done a reset again but cache/recovery/last_log.1 is still there but now with cache/recovery/last_log showing the log of stock recovery reset.
I don't mind cache/recovery/last_log showing as that's standard but cache/recovery/last_log.1 clearly shows that I'd had a custom rom (lineage) flashed and unflashed and relocked bootloader.
I'm happy to root again, I know doing that I'll be able to delete the cache/recovery/last_log.1 possibly but when I unroot and relock I'm guessing that it'll make another log showing that's happened.
Bootloader shows its locked but the recovery logs will be a problem if CEX check them, I doubt they will fix or refund me the price I paid because it clearly shows its been rooted. Wipe cache doesn't get rid of the log and 2 stock resets didn't get rid off the log, just created cache/recovery/last_log.
I did search but can't find any way to get rid of that log or to unroot and relock without another log being made.
I hope someone can help?
randoms123 said:
Hi,
I rooted using the wug tool and have had to unrrot.
I bought my Nexus from CEX and its started getting screen bleed around all edges so I'm going to take it back to CEX and their warranty says if a phones ever had custom ROM or anything installed it invalidates the 2 year warranty and they thoroughly check the phone when you take it back.
Unroot and relocking the bootloader worked fine but when I went in to stock recovery and check recovery logs there was cache/recovery/last_log.1 which when read you can tell that it's had twrp installed and uninstalled and that the bootloader has been relocked.
I've used stock recovery from bootloader to wipe cache etc and done a reset again but cache/recovery/last_log.1 is still there but now with cache/recovery/last_log showing the log of stock recovery reset.
I don't mind cache/recovery/last_log showing as that's standard but cache/recovery/last_log.1 clearly shows that I'd had a custom rom (lineage) flashed and unflashed and relocked bootloader.
I'm happy to root again, I know doing that I'll be able to delete the cache/recovery/last_log.1 possibly but when I unroot and relock I'm guessing that it'll make another log showing that's happened.
Bootloader shows its locked but the recovery logs will be a problem if CEX check them, I doubt they will fix or refund me the price I paid because it clearly shows its been rooted. Wipe cache doesn't get rid of the log and 2 stock resets didn't get rid off the log, just created cache/recovery/last_log.
I did search but can't find any way to get rid of that log or to unroot and relock without another log being made.
I hope someone can help?
Click to expand...
Click to collapse
Why don't you just flash the stock factory image with fastboot. Then lock the bootloader afterwards?
Sent from my [device_name] using XDA-Developers Legacy app
I'd just done that then seen your reply. Thanks :good:
Must have been something to do with the way the Wugfresh tool unroots and relocks the bootloader.
One of the reasons I don't like tool kits.
Sent from my [device_name] using XDA-Developers Legacy app