Help with unroot/root s-off - Verizon Droid Incredible 2

I'm having difficulties getting s-off on my device. I had my dinc 2 rooted with s-off awhile back, but then decided to go back to stock (not sure why). Anyways, I did the OTA update to the latest version that breaks the old vivow root/s-off method. So in the meantime, I used HTC dev unlock bootloader and installed MIUI 12.9. The problem is, I still have S-on from htc dev unlock and I can't just go into CWM and flash a different kernel to fix the low call volume. So I tried going through the tacoroot method, but I can't get my phone to show up in the bootloader or fastboot usb screen when I do adb devices. Commands such as fastboot reboot work, but trying to do "adb push blah blah" just gives a device not found error. Since I had to relock my device with htc dev and I have MIUI installed, I can't boot the phone up because it just says *security warning* after locking it. How do I flash the stock rom back to the device so I can boot the phone after doing the HTC dev relock or get the phone to show up in adb devices while in the bootloader/fastboot usb screen?
Thanks!

dtbingle said:
I'm having difficulties getting s-off on my device. I had my dinc 2 rooted with s-off awhile back, but then decided to go back to stock (not sure why). Anyways, I did the OTA update to the latest version that breaks the old vivow root/s-off method. So in the meantime, I used HTC dev unlock bootloader and installed MIUI 12.9. The problem is, I still have S-on from htc dev unlock and I can't just go into CWM and flash a different kernel to fix the low call volume. So I tried going through the tacoroot method, but I can't get my phone to show up in the bootloader or fastboot usb screen when I do adb devices. Commands such as fastboot reboot work, but trying to do "adb push blah blah" just gives a device not found error. Since I had to relock my device with htc dev and I have MIUI installed, I can't boot the phone up because it just says *security warning* after locking it. How do I flash the stock rom back to the device so I can boot the phone after doing the HTC dev relock or get the phone to show up in adb devices while in the bootloader/fastboot usb screen?
Thanks!
Click to expand...
Click to collapse
you'll have to use fastbootusb in bootloader or remove card from phone, use your computer to put the PG13IMG, On your card then put back in phone and boot into bootloader

Aldo101t said:
you'll have to use fastbootusb in bootloader or remove card from phone, use your computer to put the PG13IMG, On your card then put back in phone and boot into bootloader
Click to expand...
Click to collapse
I've tried this, but after the phone recognizes the PG32IMG.zip when it goes into the bootloader, it loads it and then nothing really happens and it just gives me the options like fastboot, recovery, etc (all the normal options). I know before usually it loads and then asks if I want to proceed with the update. Using an older version (Froyo RUU) it said main version is older, but after downloading a gingerbread one, it just loads and then never asks to update and gives no error. Am I doing something wrong here or using the wrong PG32IMG file?

dtbingle said:
I've tried this, but after the phone recognizes the PG32IMG.zip when it goes into the bootloader, it loads it and then nothing really happens and it just gives me the options like fastboot, recovery, etc (all the normal options). I know before usually it loads and then asks if I want to proceed with the update. Using an older version (Froyo RUU) it said main version is older, but after downloading a gingerbread one, it just loads and then never asks to update and gives no error. Am I doing something wrong here or using the wrong PG32IMG file?
Click to expand...
Click to collapse
When you get the options try scrolling to fast boot and selecting that.
Sent from Kangdemnation

CondemnedSoul said:
When you get the options try scrolling to fast boot and selecting that.
Click to expand...
Click to collapse
Tried this with multiple PG32IMG.zip files and a message briefly flashes something about incorrect or missing zip file. Anyway I found an old CWM backup of a stock Froyo setup and since I was still unlocked from HTC Dev's tool, I restored to that, relocked from htcdev unlock, then ran the vivow downgrade script followed by revolutionary's s-off. Working rooted/s-off with MIUI 12.9 and aeroevan .7 bfs kernel!

Related

Bricked my phone badly

ok so i wanted to get a custom rom my desire hd 2.3.5
at start i have tryed the old way thats in the sticky but that was for 2.3.4 so that didnt work.
what did work was unlocking the bootloader via htc dev site. after that i was clueless.
I've found AAK to root my phone and downgrade so i had used that, but i forgot that the phone was unlocked and it said it had to be locked.
and now the phone is bricked i've tried all possible ways with wiping data and cache but it doesnt work.
i wanted to relock the bootloader with fastboot.
i had entered this command:
fastboot oem lock
but that gave this error
FAILED (status malformed (1 bytes))
so my phone hangs on the boot screen and i cant do anything?
can you guys please help me?
The fact you can get to the bootloader is a great sign, so don't worry! The only time you need to properly panic is when you can't get anything on the screen or even a charge light.
---Double check with someone else that this is correct, but I think this is what you need to do ---
Do you have a custom recovery (i.e clockworkmod)? Can you boot into recovery? Use the volume keys to select recovery, then press the power button. If you get options like "reboot now" and "install zip from sd card" then flash a rom like Android Revolution HD.
If you get a red triangle, find a zip you want to flash and name it "PD98IMG.zip" then put it on the root of the SD card. Reboot to bootloader and it should flash.
If you truly want to relock the bootloader, flash an RUU and it will restore you to stock.
Tamen said:
If you get a red triangle, find a zip you want to flash and name it "PD98IMG.zip" then put it on the root of the SD card. Reboot to bootloader and it should flash.
If you truly want to relock the bootloader, flash an RUU and it will restore you to stock.
Click to expand...
Click to collapse
Simply renaming a ROM PD98IMG.zip wont work it needs to be formatted in a certain way, but if the phone is S-OFF, which wasn't mentioned there are certainly PD98IMG's about for a variety of ROMs. But I suspect Tamens suggestion of flashing the appropriate RUU and starting from scratch is going to be quickest way to get sorted
I had this same problem with mine it got stuck trying to boot up but I had no boot loader or I couldn't get into recovery.so download a took called ANDROID FLASHER and reflash the radio ect.my desire hd is now fine.
Sent from my HTC Sensation XL with Beats Audio X315e using XDA App
well i have tried to flash the ruu but without succes.
ive loaded the PD98IMG.zip on the sd and let the bootloader use it. nothing happened.
also my phone is s-on and could not find a way to go to s-off in recovery mode or boatloader.
Down load the tool above Android flasher.from the tool u can enable fast boot ect from your PC and loads of other stuff.it is a very simple to use and it has loads of folders for recovery, boot loader ect let it do every thing for u.that was the only thing that worked for me
Sent from my HTC Sensation XL
I've tried it but it doesn't work because my phone is s-on...
the description of that utility said that s-off is essential
i am really running out of options..
in short my phone has a unlocked bootloader and after that i've used AAK.
the result is bricked phone with s-on and unlocked bootloader

[Q] Problems with installing blackout ics ROM Desire HD

So I decided to root my android desire hd phone and avail the benefits of blackout ics rom on my phone.
This is how I approached.
I unlocked the bootloader from HTC Dev.
I have the adb with me, adb devices, adb restart bootloader are working absolutely fine and cell phone was detectable.
I downloaded the aahk and blackout rom from xda forums.
But I am not able to use the aahk properly. It says in instruction to do a fastboot flash boot boot.img from command prompt with the source being the place where aahk is placed on the PC. But it still doesn't work, and probably this is the root cause of the issues I am facing.
I tried downloading the CWM to boot into recovery, but that also gave me an error stating cannot find the adbwinapi.dll file.
So after that, I did a factory reset of my cellphone and truly I got my first success and I was able to get into the bootloader and recovery.
I can reach to the bootloader screen (white screen+3 andro dummies), but when I select the fastboot option It says cannot find image(which image, is it referring to boot.img). I deleted the cache on my cell phone, but again things are pending from here on.
The description on this screen says S-ON and some other things. Does that mean the security is still on?
I have the rom loaded on the sd card with renamed to update.zip, but when I select update option from the recovery it again says cannot find image, rebooting!(what image this is referring to).
And after all this sequence I am down with a cellphone now degraded to froyo from ginger bread and back to stone age!
Please advise.
TH3_M0Nk said:
So I decided to root my android desire hd phone and avail the benefits of blackout ics rom on my phone.
This is how I approached.
I unlocked the bootloader from HTC Dev.
I have the adb with me, adb devices, adb restart bootloader are working absolutely fine and cell phone was detectable.
I downloaded the aahk and blackout rom from xda forums.
But I am not able to use the aahk properly. It says in instruction to do a fastboot flash boot boot.img from command prompt with the source being the place where aahk is placed on the PC. But it still doesn't work, and probably this is the root cause of the issues I am facing.
I tried downloading the CWM to boot into recovery, but that also gave me an error stating cannot find the adbwinapi.dll file.
So after that, I did a factory reset of my cellphone and truly I got my first success and I was able to get into the bootloader and recovery.
I can reach to the bootloader screen (white screen+3 andro dummies), but when I select the fastboot option It says cannot find image(which image, is it referring to boot.img). I deleted the cache on my cell phone, but again things are pending from here on.
The description on this screen says S-ON and some other things. Does that mean the security is still on?
I have the rom loaded on the sd card with renamed to update.zip, but when I select update option from the recovery it again says cannot find image, rebooting!(what image this is referring to).
And after all this sequence I am down with a cellphone now degraded to froyo from ginger bread and back to stone age!
Please advise.
Click to expand...
Click to collapse
You have not done anything fine...anything at all. My advice is that you'd better start reading hard buddy or you will end up with a 300 bucks paperweight.
Use the guide in my signature to start.
Tip 1:If you really downgrade to froyo and you were running gingerbread, you might have messed the bootloader..can you boot in hboot in normal times or takes ages?
Tip 2:The Hack Kit can not be run with an unlocked bootloader...that is what the manual says. The manual is there just to avoid this.
If your bootloader is still unlocked, then you have to install CWM recovery, put the rom in the sdcard (no rename is necessary) and then flash the boot.img from where that file is located (I usually put in the PC desktop) and not from the Hack Kit folder.
Then, from CWM flash the rom normally and you will be up and running.
Unlocking the bootloader will not give you S-OFF....
glevitan said:
You have not done anything fine...anything at all. My advice is that you'd better start reading hard buddy or you will end up with a 300 bucks paperweight.
Use the guide in my signature to start.
Tip 1:If you really downgrade to froyo and you were running gingerbread, you might have messed the bootloader..can you boot in hboot in normal times or takes ages?
Tip 2:The Hack Kit can not be run with an unlocked bootloader...that is what the manual says. The manual is there just to avoid this.
If your bootloader is still unlocked, then you have to install CWM recovery, put the rom in the sdcard (no rename is necessary) and then flash the boot.img from where that file is located (I usually put in the PC desktop) and not from the Hack Kit folder.
Then, from CWM flash the rom normally and you will be up and running.
Unlocking the bootloader will not give you S-OFF....
Click to expand...
Click to collapse
I had this tutorial open side by side in your signature while I was doing it. (the noob one)
I can go into Hboot normal times.
I am writing it down here from the main website from where I downloaded the aahk. And it says
Unlock the bootloader using the HTC DEV bootloader unlock process.
Download att-ace-30-isboot.zip and unzip it (don’t forget to check MD5)
fastboot flash boot boot.img
relock bootloader
But just now you told me that it should not be run on an unlocked bootloader! I am a little confused.
TH3_M0Nk said:
I had this tutorial open side by side in your signature while I was doing it. (the noob one)
I can go into Hboot normal times.
I am writing it down here from the main website from where I downloaded the aahk. And it says
Unlock the bootloader using the HTC DEV bootloader unlock process.
Download att-ace-30-isboot.zip and unzip it (don’t forget to check MD5)
fastboot flash boot boot.img
relock bootloader
But just now you told me that it should not be run on an unlocked bootloader! I am a little confused.
Click to expand...
Click to collapse
Yeah, but also says this: "...No Temproot for Inspire Build 3.20.502.52..." But you have a Desire HD, haven't you? And your build is not that one, is it?
glevitan said:
Yeah, but also says this: "...No Temproot for Inspire Build 3.20.502.52..." But you have a Desire HD, haven't you? And your build is not that one, is it?
Click to expand...
Click to collapse
Yeah.
I think i found the answers I was looking for and since I used the bugger HTC dev unlocker (which I shouldn't have used), I have to come down a step and start over again.
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
This made me realize deep down search is more important. Thanks
TH3_M0Nk said:
Yeah.
I think i found the answers I was looking for and since I used the bugger HTC dev unlocker (which I shouldn't have used), I have to come down a step and start over again.
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
This made me realize deep down search is more important. Thanks
Click to expand...
Click to collapse
No problem. Get a working phone and then you can try to run the Hack Kit...but it has to be stock or otherwise will not work. :good:
glevitan said:
No problem. Get a working phone and then you can try to run the Hack Kit...but it has to be stock or otherwise will not work. :good:
Click to expand...
Click to collapse
I am not sure if you are on right now, but i am giving a try to the steps mentioned by that gentlemen above in the link.
the phone is now stuck at signature verification. I reasearched for it but could not find a viable solution or an exploit that can overcome it(though everyone seems to be suggesting to install CWM recovery)
Not taking any chances to convert my phone into a brick! Whats the best way.
TH3_M0Nk said:
I am not sure if you are on right now, but i am giving a try to the steps mentioned by that gentlemen above in the link.
the phone is now stuck at signature verification. I reasearched for it but could not find a viable solution or an exploit that can overcome it(though everyone seems to be suggesting to install CWM recovery)
Not taking any chances to convert my phone into a brick! Whats the best way.
Click to expand...
Click to collapse
ok, Have you managed to unlock the bootloader? if you are already unlocked, do you mind if I have a look at it over teamviewer?
glevitan said:
ok, Have you managed to unlock the bootloader? if you are already unlocked, do you mind if I have a look at it over teamviewer?
Click to expand...
Click to collapse
I am following the steps sequentially as mentioned in that link by sashank. The bootloader is partially unlocked due to the HTCDEV process.
Couple of other things that I noticed. The android version is still at 2.3.5 however the device was shipped with Froyo. My mistake to have said that it is downgraded to froyo when I did the factory reset.
The facebook for HTC Sense thing is jacked up big time, I cannot find that in peoples app.
The device has (believe me) gained speed. pretty strange.
Once I reach home 3 hours from now, i'll update this thread and we can connect through Teamviewer so that you can have a look.hope thats cool!
Thanks
TH3_M0Nk said:
I am following the steps sequentially as mentioned in that link by sashank. The bootloader is partially unlocked due to the HTCDEV process.
Couple of other things that I noticed. The android version is still at 2.3.5 however the device was shipped with Froyo. My mistake to have said that it is downgraded to froyo when I did the factory reset.
The facebook for HTC Sense thing is jacked up big time, I cannot find that in peoples app.
The device has (believe me) gained speed. pretty strange.
Once I reach home 3 hours from now, i'll update this thread and we can connect through Teamviewer so that you can have a look.hope thats cool!
Thanks
Click to expand...
Click to collapse
Ok, just let me know when you are online and be arrange it.
glevitan said:
Ok, just let me know when you are online and be arrange it.
Click to expand...
Click to collapse
Yes I am online now. Let me know how to proceed.
TH3_M0Nk said:
Yes I am online now. Let me know how to proceed.
Click to expand...
Click to collapse
download the teamviewer: http://www.teamviewer.com
Get the ID and PASS and send them over a Private Message, NOT HERE

[Q] Dinc 2 stuck in bootloop, can't flash PB32IMG.ZIP

I've been trying to get this Dinc 2 to work for sometime now. I bought it used so I don't know what version of software it has.
It displays the white "HTC" screen for a few seconds, then goes dark. A few seconds later the white HTC screen shows, etc etc etc. I can get into FASTBOOT with PWR/Vol-.
I've tried flashing various versions of the ROM (saving the file as PB32IMG.ZIP on the SD card). It seems to read the file but then comes up with the "wrong image" message.
The previous owner says he unlocked the the phone using the online HTC unlock, and it does say "UNLOCKED" at the top of the FASTBOOT screen. I read someplace that you had to relock the phone in order to flash the PB32IMG.ZIP file but I don't know how to do this.
I can't use ADB because I can't get my computer to recognize the phone.
Any suggestions would be greatly welcomed!
are you s-off??
tgreenstein said:
I've been trying to get this Dinc 2 to work for sometime now. I bought it used so I don't know what version of software it has.
It displays the white "HTC" screen for a few seconds, then goes dark. A few seconds later the white HTC screen shows, etc etc etc. I can get into FASTBOOT with PWR/Vol-.
I've tried flashing various versions of the ROM (saving the file as PB32IMG.ZIP on the SD card). It seems to read the file but then comes up with the "wrong image" message.
The previous owner says he unlocked the the phone using the online HTC unlock, and it does say "UNLOCKED" at the top of the FASTBOOT screen. I read someplace that you had to relock the phone in order to flash the PB32IMG.ZIP file but I don't know how to do this.
I can't use ADB because I can't get my computer to recognize the phone.
Any suggestions would be greatly welcomed!
Click to expand...
Click to collapse
are you s-off? If not then you cannot flash PG32IMG.zip (it has to be PG32IMG.zip not PB32IMG.zip) try installing these drivers: https://www.dropbox.com/s/kg37o7tsn3dq1nt/HTCDriver3.0.0.007.exe
then boot into fastboot and connect your phone to pc. the phone should display fastboot usb from there you can flash rom via adb.
remember if you don't have s-off and bootloader says unlocked then refer to this guide for flashing roms : http://forum.xda-developers.com/showthread.php?t=1435228
EDIT: did you flash a rom which caused bootlooping??
ArslanQureshi said:
are you s-off? If not then you cannot flash PG32IMG.zip (it has to be PG32IMG.zip not PB32IMG.zip) try installing these drivers: https://www.dropbox.com/s/kg37o7tsn3dq1nt/HTCDriver3.0.0.007.exe
then boot into fastboot and connect your phone to pc. the phone should display fastboot usb from there you can flash rom via adb.
remember if you don't have s-off and bootloader says unlocked then refer to this guide for flashing roms : http://forum.xda-developers.com/showthread.php?t=1435228
EDIT: did you flash a rom which caused bootlooping??
Click to expand...
Click to collapse
I'm S-on.
ADB doesn't work. I can't boot into Android.
I didn't flash a rom on this phone; I can't get past the bootlooping. I doubt the previous owner flashed a rom, either.
tgreenstein said:
I'm S-on.
ADB doesn't work. I can't boot into Android.
I didn't flash a rom on this phone; I can't get past the bootlooping. I doubt the previous owner flashed a rom, either.
Click to expand...
Click to collapse
in that case you can try to install an ruu.......... (I think I told you this before also) www.androidruu.com/getdownload.php?...ivo_W_Gingerbread_S_VERIZON_WWE_5.10.605.9_Ra dio_1.09.01.1111_NV_VZW1.92_release_225831_signed.exe just boot into fastboot and run this exe
ArslanQureshi said:
in that case you can try to install an ruu.......... (I think I told you this before also) www.androidruu.com/getdownload.php?...ivo_W_Gingerbread_S_VERIZON_WWE_5.10.605.9_Ra dio_1.09.01.1111_NV_VZW1.92_release_225831_signed.exe just boot into fastboot and run this exe
Click to expand...
Click to collapse
Nope. Apparently version 6.04.605.07 is installed, and the bootloader won't let me install an older version. And there apparently is not an RUU for 6.04.605.07 (if anybody knows of one, please let me know).

Is My Phone Bricked?

Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Swazi Samurai said:
Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Click to expand...
Click to collapse
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
S1L3nTShaDoWz said:
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
Click to expand...
Click to collapse
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Swazi Samurai said:
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Click to expand...
Click to collapse
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
S1L3nTShaDoWz said:
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
Click to expand...
Click to collapse
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Swazi Samurai said:
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Click to expand...
Click to collapse
I formatted my SD card and was finally able to transfer the RUU. The bootloader begins to run the 0P6BIMG file, but it fails right after it starts parsing. I tried running it several times and the results were the same.
I really wish I could get ADB to recognize my phone so I can flash a custom recovery... When I plug my phone into a USB port, my computer makes a noise, the phone says "USB" next to Fastboot, and HTC Sync Manager begins to load. When HTC Sync Manager comes up, it says "HTC Sync Manager couldn't connect to your phone." Windows Device Manager also does not have anything listed for an Android device.
I've noticed when the phone is not powered on and simply charging from the USB port, an "HTC MTP Device" driver tries to install, but fails. Could this be the problem? I've tried plugging the phone into 3 different computers and they all get the MTP failure.
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not specifically trying to install the GPE RUU at the moment. I had the stock GSM recovery installed based on my original CID and I'm trying to load the associated RUU.
I originally loaded GPE 4.4.3 with TWRP and downloaded the 4.4.4 update OTA from Google. Before restarting my phone and installing the update, I flashed the stock GSM recovery for CID CWS_001. This may have been what caused the issue initially when the phone tried to apply the update if it was looking for a GPE recovery.
I know I cannot install the GPE RUU because I'm S-ON and ADB does not recognize my device so I cannot change the MID or CID. At this point, I'm really just trying to get back to stock so I can start fresh.
Is it possible that when the 4.4.4 update tried to run, it associated my recovery with GPE and now that's why it will not install the stock RUU due to a mismatch? I'm really just guessing at this point.
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
I'll give that a try and report back. Thanks for the input.
3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
You are the freakin man!!! I edited the template from the post you suggested, added my MID/CID, and packaged it with the TWRP image. Booted right from the SD and I now have custom recovery! I wish I could buy you a beer!
No problem mate. Glad I could help. :thumbup::thumbup::beer:
Sent from my HTC One_M8 using XDA Free mobile app

Bricked my HTC 10, What to do next?

Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Have you tried doing a factory reset using the stock recovery?
See if you can get a system.img to flash manually. If you can get an OS boot you should be able to fix your device.
tkoreaper said:
Have you tried doing a factory reset using the stock recovery?
Click to expand...
Click to collapse
Using the adb shell command (recovery --wipe_data)? Yeah I've tried that, but I get a device not found error. adb isn't working right now, however I am still able to get fastboot commands, and the phone recognizing them at least. Otherwise, no I haven't what would I need to do?
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
5m4r7ph0n36uru said:
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
tw1tch175 said:
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
Click to expand...
Click to collapse
Yes. I just figured that out while searching haha. I did go through and use the UI, but I had no luck. I am looking for an img like you said but I am not having luck so far. Is there one of the Stock guide on my original post?
Ok so for ALL HTC the only proper way to s-on is to use fastboot/download and for oem writesecureflag 3, you should NEVER EVER EVER us echo/dd /hexeditor to go s-on.
For 2016+ phones, you should use sunshine or another tool to go from unlock/relocked to lock, do NOT use anything not designed for the phone in question, or attempt to do it manually. I can only vouch for SunShine's capability to safely change the bootloader status, I can't vouch for any other method or tool. I know SunShine does it right.
See http://forum.xda-developers.com/htc-10/how-to/psa-htc-10-s-off-s-lock-unlock-t3371264 for my PSA on the subject.
If the phone won't flash with a proper RUU, well you need to find someone with a EMMC write tool to rewrite all your firmware, this is probably going to run $100-200.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
bob3rt said:
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
Click to expand...
Click to collapse
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
5m4r7ph0n36uru said:
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Ah gotcha. That makes sense. Wouldn't have been the only thing that slipped my mind. I lost access to my Steam authenticator too. I was able to get the zip from the exe file like you said, after I put that on an SD card and boot to download mode do I just fastboot flash zip?
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
tkoreaper said:
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
Click to expand...
Click to collapse
That is in regards to wiping data, earlier versions of sunshien wiped data on all htc 10 going s-off, thats not the issue here. Issue here is he improperly set the phone lock/s-on. Gotta use sunshine to set it locked, and fastboot to set s-on.
Hey Everyone just wanted to give an update since yesterday evening.
Just wanted to give out some props to @5m4r7ph0n36uru . Following his advice of extracting the Rom.zip from RUU .exe I was able to run it in download mode and loaded up an OS on the phone. So Now I am unbricked! Yay. I had to find out how to do that using process monitor and everything, but it was a success. and I can breathe easy. Thankfully doing that was easier that doing the Database call handler stuff from today at work XD
Thankfully my lesson is learned and I'll flash correctly to full stock next time. Thank you all for your help in the matter.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
Hello,
Just to inform that if I try to run RUU.exe from PC when the phone is in bootloader menu, I get battery low error. However, if I "boot to download mode" in the bootloader menu, I can run the RUU.exe from the computer without any error.

Categories

Resources