Related
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Sticky this. In big bolt capital letters. I've seen this happen once already, and just saved another phone from this headache.
More people need to know about the DON'T-FLASH-PC10IMG.ZIP
dyndragon said:
Sticky this. In big bolt capital letters. I've seen this happen once already, and just saved another phone from this headache.
More people need to know about the DON'T-FLASH-PC10IMG.ZIP
Click to expand...
Click to collapse
When u say u saved a phone. Do u mean u stopped someone before they did it, or you mean u have a working fix. Pls post fix if u have one. I will post mine as soon as I confirm it.
Btw- I have seen 5 happen in the last 3 days. As I haven't gave up on any yet, some are worse off then others and only 2 have a possible fix in the am, well a fix I know of.
After I permarooted, I decide to flash a Z ROM. I did, and I didn't care for Sense, so I flashed PC10 and didn't have any issues. Mind you, I didn't flash the OTA at that point either. Phone booted up without an issue, I got the OTA almost immediately, and I permarooted again.
Basically, if you applied the OTA, don't flash PC10 to get stock again.
So does that mean the instructions for how to Un-Root are no good?
KronicAnarchy said:
So does that mean the instructions for how to Un-Root are no good?
Click to expand...
Click to collapse
I unrooted my phone, no problems.
No the instructions to unroot are correct because at the beginning you flash an alternate misc.img to change the main version number. I got stuck the other day because my phone wouldnt boot and i couldn't flash the ota because i had removed google goggles and some other system apps so i tried to downgrade using PC10IMG.zip and it cancelled during installation just as stated in the op and i was somehow able to flash the misc.img through fastboot and reflash with PC10IMG.zip
sethrd said:
After I permarooted, I decide to flash a Z ROM. I did, and I didn't care for Sense, so I flashed PC10 and didn't have any issues. Mind you, I didn't flash the OTA at that point either. Phone booted up without an issue, I got the OTA almost immediately, and I permarooted again.
Basically, if you applied the OTA, don't flash PC10 to get stock again.
Click to expand...
Click to collapse
If you did not flash the stock rom before you flashed the pc10, you got lucky. When it reboots half way though, it does a version check, and the rom version you happened to be running must have been an older base. If your phone is bootable and you flash the pc10 OUT OF ORDER it will lock you down that way, ie locked on sense. If anyone wants to go back to stock, just flash one of the stock w/root roms in recovery or via rom manager... trust me on this, there are more people screwing up there phone because of this then anything, just not posting about it. I've been up all hours of the night, helping differnt people the last few days.
KronicAnarchy said:
So does that mean the instructions for how to Un-Root are no good?
Click to expand...
Click to collapse
No the unroot guide is ok. If you notice, the first thing it has you flash is the stock w/root rom. Like I said if you follow proven instructions to a T, you will be ok. That is if you want to go back to non-root only though. If you just want stock with root, flash a stock with root rom via RECOVERY or ROM MANAGER.
Im not to sure how it all works and i just got up a little bit ago .
but since s-off doesnt check the sign couldnt we unpack and repack pc10img with the hboot with s-off?
fastludeh22 said:
Like I said if you follow proven instructions to a T, you will be ok.
Click to expand...
Click to collapse
Well he's edited his post now, and people have followed his instuctions and bricked their phones.
So just to confirm before I brick mine: The instructions in their current form will not brick my phone, right?
I had s-off when running baconbits. I tried to revert back to stock but couldn't. I then flashed pauls prerooted phone rom and tried to install the stock rom back onto the phone. I seems to have removed the s-off and now displays s-on. I am permanently rooted, but fastboot still shows s-on. Was this caused because I tried to flash the pc10img.zip? Now how do i revert back to stock? I don't have a nandroid backup for the stock rom, just paul's which after a recovery still displays s-on. It doesn't loop, I just can't install anything else on there.
I flashed pc10 and it turned S-ON. But when I booted it up I still had root acess, so it was like a temp root but where I could not write to the system. I took the ko file from the perm root and hex edited it to match the kernal on my phone.. boom rooted again and I was able to flash recovery and do a nand restore
I tested it out again by hbooting pc10.. and I was able to obtain s-off by changing the kernal number in the ko file
Sent from my T-Mobile G2 using XDA App
So let me get this straight, in order to flash pc10 safely we MUST have an existing PreRooted STOCK ROM?
No all you have to do is run hexeditor to change build number then you can flash pc10img
Sent from my T-Mobile G2 using Tapatalk
marc91988 said:
No all you have to do is run hexeditor to change build number then you can flash pc10img
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
Exactly. If you actually follow the directions in the thread you will be fine. I've done it more than a few times and have not had any problems yet.
I have also updated the instruction on the unroot guide aswell.
I was running the original Sense rom that was loaded via hboot which kept me at s-off. I was able to revert back to stock using the PC10 zip from here http://forum.xda-developers.com/showthread.php?t=831398 At the time I had no clockwork recovery. Was what I unsafe?
Thanks for the piece of mind. I don't want to unroot just yet, I'm running pretty much the stock rom w/ ota and bacon bits anyway, so........ Still it's nice to know that I can get back to stock should I NEED to.
Okay so I did this and I didn't brick my phone...and still have root/s-off
Did an ota update, after I found out there was perm root I perm root g2 s-off, then I went and downloaded clockwork/rom manager
Created a backup of the current g2, and did a wipe
Then hboot to sense ui (still have root). I went into clockwork create another backup. Played around with desire z rom.
After I decided to go back to stock 2.2 performed a restore with clockwork and now I am back to my original g2 stock.
So am I missing something here?
fryrice8850 said:
Okay so I did this and I didn't brick my phone...and still have root/s-off
Did an ota update, after I found out there was perm root I perm root g2 s-off, then I went and downloaded clockwork/rom manager
Created a backup of the current g2, and did a wipe
Then hboot to sense ui (still have root). I went into clockwork create another backup. Played around with desire z rom.
After I decided to go back to stock 2.2 performed a restore with clockwork and now I am back to my original g2 stock.
So am I missing something here?
Click to expand...
Click to collapse
These people didnt nand back before messing around with stuff
Sent from my T-Mobile G2 using XDA App
Not sure how he rooted his phone [method], but he flashed the PC10.img.
The phone boots but still has CM7 with root enabled, while bootloader still says that it is S-Off. Also, recovery is still Clockwork Mod. When trying to flash OTA via Recovery it says there's an error from build.prop. Bootloader doesn't let PC10.img flash again.
Again, sorry if its a dumb situation, but this isn't my phone, and flashing the PC10.img could be 'dangerous'.
What are you trying to accomplish? Are you trying to unroot or get to stock 2.2 rooted?
If you're tryin to unroot and go back to stock with S-ON, follow the wiki:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock
Tried that, however even after changing the version # , bootloader says that main version is older. Probably because PC10.img has already been flashed, and it didn't change the system files.
God damn it, I think I messed up here. I got a replacement G2 since mine has gone bananas! So I got Rooted with S-Off but I think I flashed the DesireZ PC10IMG.zip since I wanted to install doubleshot roms and so on. However after I flashed it my phone gets stuck at the HTC screen now?
When I try to boot into Recovery it's still under Recovery v3.0.2.4 so I can't even restore my phone to a previous back up since these back ups were created with the latest Recovery version.
I went ahead and downloaded the stock G2 Rom from here: http://forum.xda-developers.com/showthread.php?t=788489
However, when I renamed it to PC10IMG and put it on the the root of the SD-Card Bootloader will not flash the .zip and I get some sort parsing message and I get right back to the Bootloader screen.
I also can't follow the guide here: http://forum.xda-developers.com/showthread.php?t=999796 - to restore the stock H-Boot since I can't even boot the damn thing!
HELP!
Flash a new rom in recovery, or if you have eng hboot, flash latest recovery, restore nandroid.
-Nipqer
What does it say when you go into the bootloader? There should be a hboot version towards the top of the screen?
Also, have you tried flashing a rom using recovery? It sounds like it is working- just get a normal rom, nothing that is named PC10IMG.zip. Maybe try one of the CM stable releases.
Nipqer said:
Flash a new rom in recovery, or if you have eng hboot, flash latest recovery, restore nandroid.
-Nipqer
Click to expand...
Click to collapse
Now see....... Why didn't I think of that?..... FAIL!
okay so i updated to the new rom by ruu method and i was already rooted when i did it. So here is the deal now, im trying to use root required apps and its telling me im not rooted the su binary is not installed or it is in the wrong directory so i click okay and i launch my phone into bootloader mode and it shows revolutionary s-off hb6.16.00 and i am not able to get into recovery mode. So am i really not rooted? Did the update only make ir look like my s is off?
what i want to do? I want to be on s-off and rooted for reals instead of fakey.
First download and flash amon RA FNMA thru bootloader. In that recovery you can flash superuser and binaries. There is an option for it. U are already s-off so you r almost there.
Support TrevE !!
Hey,
Did you install a recovery when you turned s-off? I had it happen once when switching roms that something must have went wrong between the rom and super user and I had to run recovery to get it back to a previous version of super user in order for it to work and be able to manage root, even though I already had s-off.
and if you didnt flash the recovery then:
defiantly listen to the post before me, go flash the amon recovery!
Good luck let us know how you do!
Your right steve i didnt flash a recovery but because i thought i could do it in my recovery after the ruu install but it turns out that the ruu must have taken it off because i have never really use ruu just zips so is there a clockworkmod file that i can change use in the bootloader flash update method?
Where can i find that other recovery program 2nd poster?
grabbed that recovery here
http://forum.xda-developers.com/showthread.php?t=705026
then usb toggle through recovery to get the su flashed and good to go.
thank you
actually no bueno!! su app still wont update says root access failed when i try to update it and also busy box not installed and also i dl an app to check root access and it says root is not on device so what i have is a supersonic device with s-off and custom recovery working and also was able to flas su through recovery yet i still get messages from apps saying device is not rooted??? I guess i spoke to soon.
Im just going to try and flash a custom rom from recovery and hopefully the system files will load correctly i will do a nand back up for this one first of course.. ill be back.
i used energys newest release and holy kentucky durby batman it works my system files are back to root access.Maybe has to do with something then from the stock ruu bacause i went to the bootloader after putting energy back on and it says hb6.16.1002 which is what i got with the stock ruu i used, and s-off still and root access available. awsome.
popasmurfn23 said:
okay so i updated to the new rom by ruu method and i was already rooted when i did it. So here is the deal now, im trying to use root required apps and its telling me im not rooted the su binary is not installed or it is in the wrong directory so i click okay and i launch my phone into bootloader mode and it shows revolutionary s-off hb6.16.00 and i am not able to get into recovery mode. So am i really not rooted? Did the update only make ir look like my s is off?
what i want to do? I want to be on s-off and rooted for reals instead of fakey.
Click to expand...
Click to collapse
Keep in mind that having S-OFF and having root access are two different things even though they are usually together: S-OFF allows you to flash whatever you want on to the phone while having root access means that you have access to basically every aspect of the phone (application-wise) on that specific ROM. For example, it is possible to flash stock (which has no root access) and keep S-OFF which will allow you to flash anything else whenever.
When flashing the RUU it overwrites the custom recovery ( Ra - TWRP ) and also removes the ability for Superuser to do its job. So you broke your " root " .
I don't know if it will work in your case but try to re-run whatever method you used to gain root access in the first place. See if you can find a PC36IMG.zip that is already rooted. and then a PC36IMG.zip of a recovery.
You can flash both by booting into the bootloader. Remember to remove / delete the first ( rooted rom ) image from the SD card before you run the recovery PC36IMG.zip.
Man I hope that all made sense !
hboot 6.16/s-off revolutionary/stock recovery/no root
I had the same issue. hboot 6.16 revolutionary s-off but i was not rooted and on the stock recovery. i thought i was a goner because no pc36img i downloaded would flash in bootloader and ruu's wouldn't flash. I just recently started revolutionary and when i plugged my phone in revolutionary said 'you are already s-off, do you want to flash revolutionary clockwork recovery?' Once I hit Y (yes) it flashed the recovery and i was rooted again. this took a whole lot of guessing and checking so hopefully this helps someone
Hey all,
So I upgraded to a Droid DNA a couple of months ago, so I decided to root my OG Droid Incredible (SLCD).
I followed the guide here: (http://forum.xda-developers.com/showthread.php?t=1488351) to the letter. When I got to the step where I ran unrevoked, it flashed ClockWorkMod recovery, but didn't finish the process. So what happened is now I have ClockWorkMod recovery, and a Stock ROM that doesn't have Root access. (I downloaded a couple of different root checkers from the market and I got "no root access" results".
I tried flashing the stock recovery using the PB31IMG.zip method, but in HBOOT my phone won't recognize the file on my Micro SDcard, even though it's on the root, and properly named.
Can anyone help me get my phone completely rooted, or at least back to stock-stock so I can use a different method?
P.S I did check all MD5 sums, and the phone still works perfectly....it's just in a weird "limbo" state of rooted or not.
Thanks!
FCO2011 said:
Hey all,
So I upgraded to a Droid DNA a couple of months ago, so I decided to root my OG Droid Incredible (SLCD).
I followed the guide here: (http://forum.xda-developers.com/showthread.php?t=1488351) to the letter. When I got to the step where I ran unrevoked, it flashed ClockWorkMod recovery, but didn't finish the process. So what happened is now I have ClockWorkMod recovery, and a Stock ROM that doesn't have Root access. (I downloaded a couple of different root checkers from the market and I got "no root access" results".
I tried flashing the stock recovery using the PB31IMG.zip method, but in HBOOT my phone won't recognize the file on my Micro SDcard, even though it's on the root, and properly named.
Can anyone help me get my phone completely rooted, or at least back to stock-stock so I can use a different method?
P.S I did check all MD5 sums, and the phone still works perfectly....it's just in a weird "limbo" state of rooted or not.
Thanks!
Click to expand...
Click to collapse
If you have cwm flashed then just flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip, thru cwm. Then you will be rooted. Also remember to install busybox from the market.
Alternativley you could just flash a rom of your choosing, as roms come pre rooted and with busybox.
cmlusco said:
If you have cwm flashed then just flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip, thru cwm. Then you will be rooted. Also remember to install busybox from the market.
Alternativley you could just flash a rom of your choosing, as roms come pre rooted and with busybox.
Click to expand...
Click to collapse
Alrighty,
So I tried this just now, and it still didn't work. It flashed SU successfully, but two different root checkers I DL'd told me I still don't have root access. I'm also s-on still, I forgot to mention. Busybox was also telling me it didn't have proper access.
FCO2011 said:
Alrighty,
So I tried this just now, and it still didn't work. It flashed SU successfully, but two different root checkers I DL'd told me I still don't have root access. I'm also s-on still, I forgot to mention. Busybox was also telling me it didn't have proper access.
Click to expand...
Click to collapse
Strange, is the superuser app in the app drawer? Your bootloader is unlocked right? You may need to do an ruu and start over.
cmlusco said:
Strange, is the superuser app in the app drawer? Your bootloader is unlocked right? You may need to do an ruu and start over.
Click to expand...
Click to collapse
Yeah Superuser is in my app drawer. I'm not sure about the bootloader. How can I check? I've tried doing an RUU, didn't work either of the times I tried to.
FCO2011 said:
Yeah Superuser is in my app drawer. I'm not sure about the bootloader. How can I check? I've tried doing an RUU, didn't work either of the times I tried to.
Click to expand...
Click to collapse
Boot to hboot (vol down + power), it should say at the top. Give me all the info there. You may need to reformat your sdcard fat32 to get the ruu to work. Try going to menu settings applications manage applications all tab find superuser and clear its data. Then open superuser go to preferences and select binary update.
cmlusco said:
Boot to hboot (vol down + power), it should say at the top. Give me all the info there. You may need to reformat your sdcard fat32 to get the ruu to work. Try going to menu settings applications manage applications all tab find superuser and clear its data. Then open superuser go to preferences and select binary update.
Click to expand...
Click to collapse
This is the information from hboot:
LOCKED (OOW)
INCREDIBLE XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16AC
RADIO-2.15.10.07.07
DEC 12 2011,23:37:16
I'm guessing my bootloader is still locked then.
I've did reformat my sdcard when I was going to do the RUU but it still didn't work , but I will try that again anyway.
Cleared SU's data and did the binary update, no change. Doesn't recognize that busybox is installed, even though it's installed. Does BB have to be flashed? Because I DL'd busybox from the market.
Thanks for all the help so far!
EDIT:
I was able to RUU, using the most recent GB OTA RUU from here: http://pvillecomp.com/?page_id=22 Didn't look like anything changed. I also tried flashing the stock recovery through HBOOT but I got this message:
Main Version is older!
Update Fail!
Do you want to reboot device?
<VOL UP> Yes
<VOL DOWN> No
ok first of yu should unlock ur bootloader via htcdev unlock method...then downgrade bak to froyo gingerbread for what i remember didn't allow us to have soff via unrevoked. what android version are yu running? try to ruu via desktop if nothing works :/
Typed from my broken Typewriter!!!
elzimmer said:
ok first of yu should unlock ur bootloader via htcdev unlock method...then downgrade bak to froyo gingerbread for what i remember didn't allow us to have soff via unrevoked. what android version are yu running? try to ruu via desktop if nothing works :/
Typed from my broken Typewriter!!!
Click to expand...
Click to collapse
Would the HTCdev method work even though I'm running CWM recovery?
I'm running 2.3.4 stock nonrooted
Tried RUU'ing already, didn't work, at least it didn't change anything.
so u can downgrade to froyo u have to follow a different guide to downgrade soff root upgrade to gingerbread (if thats ur preferred rom) or because if ur son u cant flash the boot.img in any rom and will be needed if u wanna flash something like cm or any thing else
Typed from my broken Typewriter!!!
elzimmer said:
so u can downgrade to froyo u have to follow a different guide to downgrade soff root upgrade to gingerbread (if thats ur preferred rom) or because if ur son u cant flash the boot.img in any rom and will be needed if u wanna flash something like cm or any thing else
Typed from my broken Typewriter!!!
Click to expand...
Click to collapse
Alright, so you're saying I should downgrade to froyo first, then achieve s-off and root?
FCO2011 said:
Alright, so you're saying I should downgrade to froyo first, then achieve s-off and root?
Click to expand...
Click to collapse
You need to unlock the bootloader, fastboot flash cwm , flash superuser thru cwm, fastboot flash froyo misc img thru hboot, flash froyo ruu thru hboot, reunlock bootloader, fastbootflash cwm, flash superuser or a rom of your choosing. Follow this guide http://forum.xda-developers.com/showthread.php?t=1506258.
cmlusco said:
You need to unlock the bootloader, fastboot flash cwm , flash superuser thru cwm, fastboot flash froyo misc img thru hboot, flash froyo ruu thru hboot, reunlock bootloader, fastbootflash cwm, flash superuser or a rom of your choosing. Follow this guide http://forum.xda-developers.com/showthread.php?t=1506258.
Click to expand...
Click to collapse
Haha, I actually just found your guide too, right before I checked this thread. Alrighty, going to go through this guide.
Quick question, since I already have CWM recovery, do I need to reflash it? it is the same version (5.0.2.0). I also flashed the super user zip you posted earlier. should I reflash the one in the guide?
Thanks again so much for your help!
FCO2011 said:
Haha, I actually just found your guide too, right before I checked this thread. Alrighty, going to go through this guide.
Quick question, since I already have CWM recovery, do I need to reflash it? it is the same version (5.0.2.0). I also flashed the super user zip you posted earlier. should I reflash the one in the guide?
Thanks again so much for your help!
Click to expand...
Click to collapse
I would reflash it as it may not be complete do to not being unlocked. It only takes a few secs anyways.
cmlusco said:
I would reflash it as it may not be complete do to not being unlocked. It only takes a few secs anyways.
Click to expand...
Click to collapse
Thanks! Will do.
cmlusco said:
I would reflash it as it may not be complete do to not being unlocked. It only takes a few secs anyways.
Click to expand...
Click to collapse
Alright,
So I unlocked successfully, flashed su.zip, reflashed CWM recovery, and got to the busy box step.
I'm using jrummy's installer from the market, and it's telling me I have root access. But when I try to install it, it doesn't work. It just sits there "installing busybox". I also used a rootchecker app and that one says I still don't have root access, even though the busybox installer says I do. Superuser also tells me I don't have root access when I go to update the binaries.
FCO2011 said:
Alright,
So I unlocked successfully, flashed su.zip, reflashed CWM recovery, and got to the busy box step.
I'm using jrummy's installer from the market, and it's telling me I have root access. But when I try to install it, it doesn't work. It just sits there "installing busybox". I also used a rootchecker app and that one says I still don't have root access, even though the busybox installer says I do. Superuser also tells me I don't have root access when I go to update the binaries.
Click to expand...
Click to collapse
Try doing a full wipe and then flashing a rom.
cmlusco said:
Try doing a full wipe and then flashing a rom.
Click to expand...
Click to collapse
oh, nevermind, busy box installed. It just took a really, really, really long time. Thanks though!