Stuck. Can't flash Stock OTA. - G2 and Desire Z Q&A, Help & Troubleshooting

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.

Related

[Q] Need to Unroot

Theres a new OTA of course that includes gingerbread but I need to download 3.7 in order to get to that. That of course means I need to unroot and thats my problem. I cannot get rid of clockwork recovery and have tried all day to. (Havent showered). I have s-on and used unrevoked 3 to root. Please help me get rid of clockwok recovery.
Why not just flash a rooted version of the update there are a few good ones out and once you unroot it will be harder to root after the update.
Sent from my PC36100 using XDA App
If you don't ever want to root again, or if you don't mind waiting awhile, just run an RUU from your computer or flash a PC36IMG of the RUU through the bootloader. This will get rid of your recovery.
If you want to stay rooted, don't accept the update. If you can still get into recovery, flash unrevoked forever through recovery. Or just run unrevoked from your computer. Then download a stock rooted rom from here and flash that. Do a nandroid backup before flashing. Accepting the OTA while s-on will leave you without root until someone finds a new root method for the latest update.
(from... Evo/MIUI/Tapatalk)
I tried a PC36IMG and they sad they were invalid. I also tried an RUU and all it did was wipe my phone storage.

[Q]Installing custom ROM with stock Recovery?

Hey XDA-Dudes,
I just got my Desire HDand I wanted to put a custom ROM on it because the stock ROM is pretty crappy.
Now I saw in the recovery that this Phone is alread S-Off and the lazy noob I am I don't want to downgrad and root my phone just to install clockwork recovery (I'm on 2.2.1 Build 1,75,xxxxxx).
So can I use my stock recovery to flash a third party ROM?
And how do I do it?
Edit: I want to flash to CM7 if it's important.
gingerbreak is able to perm root your build. (install it from your sd card, and then run it)
it may error out and say something went wrong, its ok, reboot the device, and you're now probably rooted.
download rom manager from market and if the perm. root succeeded then use it to flash cwm recovery.
Did it but after the reboot I get stuck on this screen...
abload.de/img/img_0165xe4s.jpg
Edit: Pretty sure I'm S-Off:
abload.de/img/img_0166lekn.jpg
Ryu77 said:
Did it but after the reboot I get stuck on this screen...
abload.de/img/img_0165xe4s.jpg
Edit: Pretty sure I'm S-Off:
abload.de/img/img_0166lekn.jpg
Click to expand...
Click to collapse
you have radio S-Off, not ENG S-Off.
where it says "SHIP" it should say "ENG" instead.
Only then will you be able to flash cwm recovery.
Right now all you can do is flash different stock roms using the RUU via the pc, or PD98IMG off the sd.
Okay thanks,
I'll guess I'll go 1.32 and root afterwards to install crm.

S-Off but on 6.16hboot w/o root access?

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

4.4 OTA bricked me - HELP

I had used rumrunner when I first got the phone with 4.2. S-off, unlocked, root, TWRP. Wanted to take OTA, so I flashed stock recovery and took 4.3 which went fine. Then I took 4.4 and now I'm in a perpetual reboot between the red exclamation triangle and HTC logo screen. Never getting anywhere. What to do?
So your still s-off? If so just do an ruu.
cmlusco said:
So your still s-off? If so just do an ruu.
Click to expand...
Click to collapse
I was hoping to not lose my sh!t that's still on it. I do have nandroid backups from right before I started the whole upgrade process. Since I still have s-off, can I flash the original firmware and stock software, followed by TWRP and then restore the nandroid backups?
Btw, is the reason why the OTA failed due to the unlocked bootloader?
The following post says:
"when you choose to install the stock recovery you will then be able to get OTA updates after locking your bootloader."
http://forum.xda-developers.com/showthread.php?t=2471869
I have taken otas while s-off and unlocked so that shouldnt be the issue.
Yes you can flash ota, then fastboot flash twrp and restore your backup. That is if the backup is saved on your pc. The sdcard will be wiped from the ota.

M9 soft bricked after 7.0 update

Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
ruubs said:
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
Click to expand...
Click to collapse
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
computerslayer said:
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
Click to expand...
Click to collapse
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
ruubs said:
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
Click to expand...
Click to collapse
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
computerslayer said:
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
Click to expand...
Click to collapse
The phone status is indeed unlocked.
I didn't know I could flash TWRP or a ROM. I thought I needed S-OFF for that.
I want my phone to be as stock as possible. Can I flash a stock ROM or does it have to be a custom one.
And do i need to flash TWRP in order to flash a ROM?
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
ruubs said:
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
Click to expand...
Click to collapse
That's the route I would take too. The readme thread has a section dedicated to changing your SKU in order to use other RUUs.

Categories

Resources