Okay, I have what looks to be like a very nice stock gingerbread HTC flyer with Demo.apk and DemoRecovery.apk installed to it. (No, you can't just uninstall them**.) The long and short of this is that no matter what you do to this thing, as soon as it reboots, it wipes out all changes and restores it to the original stock gingerbread with demo. I'll put all the Flyer specifics at the bottom of the post, but here's a short list of what I've tried so far (there's more; this is just the big stuff):
Revolutionary: works fine until the very last step, which is a reboot. Then fails. As I understand it, I can't install CWM recovery until I'm s-off.
Running the stock Bightstar RUU: Copies over fine, says it's rebooting to do the actual flash, and boots directly into Android, wipes out all the files and fails.
HTC bootunlocker fails with a command error (and since I copied and pasted it into the command line, I'm pretty sure I got that part right).
I have adb and fastboot working.
Before I waste any more time trying to reinvent the wheel, I'm just going to ask. Is there any way to flash this thing without rebooting it at any point before it completely finishes? I'll take any help offered because at this point, it's a very pretty paperweight.
Specs:
CID: BS_US001
Flyer PVT Ship S-on RL
HBOOT: 1.10.0000
Microp: 0850
Radio: 3809.85.04.10_m
eMMC: boot
May 4 2011, 11:04:45
**There is a way to stop the demo from starting automatically, but it a) requires a phone keyboard and b) apparently doesn't do a thing to reverse the changes made when you install the demorecovery.apk.
Well you could go through the process of rooting and installing cwm to it and upgrading to HoneyComb. Also if you can get it rooted you could delete the demo.apk and demorecovery.apk from system files.
Related
Sorry for long post but I've tried to provide a sufficient level of detail. If the answer is in another thread let me know. I've read quite a few of them now!
I've had my flyer for a short time and was loving it until I tried to mod it.
I installed CWM and Superuser root and had it "S-Off". I tried to flash the Leedroid HC rom. It seemed to be dead on re-boot just the HTC screen. I did a restore from CWM and got Gingerbread back. Some apps like default browser did not work though.
Now I had a mostly working system I followed the O'brian (think' that correct name) including using official HTC unlocker as was in instructions. Tried to use another HC rom and the ARU wizard. I got an error 155 and an RUU failure msg on device. Not sure what to do know. I have download this file "Best RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204108_signed". Nothing much happens when I run it other than seeing the install screen, then it exits. I really need some help to get back to some kind of working system.
Been through thread "[GUIDE][Flyer+View]Gingerbread S-
OFF/Recovery/Permaroot"
Can't follow post 17 to get S-Off as device will not boot into android!
From CWM Backup, the external SD card I used seem to have got corrupted. This could have been root of problems
data.img - file error
cache.img - file error
nandroid.md5 - file error
Boot.img, recovery.img and system.img files seem ok...
Got this msg from "revolutionary.exe" when tried to get -"S-Off" again.
Found your device: /sbin/sh: getprop: not found (/sbin/sh: getprop: not-/sbin/sh
: getprop: not, Android: /sbin/sh: getprop: not, ROM version: /sbin/sh
Your device: /sbin/sh: getprop: not, with HBOOT /sbin/sh: getprop: not is
not supported at this time.
Here are my device details:
INFOversion: 0.5
INFOversion-bootloader: 1.11.0011
INFOversion-baseband: 3822.10.08.07_M
INFOversion-cpld: None
INFOversion-microp: 0950
INFOversion-main: 2.23.405.4
INFOserialno: HT15WT403213
INFOimei: xxxxxxxxxxxxxxxx
INFOproduct: flyer
INFOplatform: HBOOT-7230
INFOmodelid: PG4110000
INFOcidnum: HTC__054
INFObattery-status: good
INFObattery-voltage: 4143mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: f0e1145e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
I have hboot 1.11.0011 with CWM and access via ADB
Your help appreciated, at end of my tether!
allot to take in but best I could tell you were on gingerbread and maybe tried to flash Lee Droid HC version so that would not work. So then you followed an old thread to update to HC using Paul Obrien's method whcih requires HTC Dev unlock of the boot loader. At this point in time you can not flash any roms via recovery and your system will not boot into android.
Please confirm if I am following what happened to you and if while in your hboot screen it says Unlock up top.
Thanks for replying.
In summary that's correct.
If I hold down the vol-down button I get the screen that says:
"*** UNLOCKED ***"
"flyer PVT SHIP S-ON RL
HBOOT-1.11.0011
Micro P-0950
Radio 3822.10.08.07_M
eMMc-Boot
I still have USB access to it via fastboot I think
ok so here we go
no hc rom will just directly flash and boot because you can not overwrite the boot.img via recovery with HTC dev unlock. If you wanted to flash say Leedroid you would have to pull the boot.img from the rom package then fastboot flash it first then back to recovery and flash the rom. This is a hacky way to do it and to be honest every time you flashed a rom you would have to do the same. Here is what I suggest:
follow this thread here to downgrade
http://forum.xda-developers.com/showthread.php?t=1307759
you may likely be able to skip the misc version part. Hopefully you are aware of what your stock ruu is. If you tried running it before and it failed it was because you did not relock the boot loader prior to trying as is described in the thread I linked
Once, hopefully, you are back on GB, I would run this method to get to HC
http://forum.xda-developers.com/showthread.php?t=1358758
now, if you flashed a hc rom on your device and it will not boot, just as mentioned flash the boot.img via fastboot from the rom and it should boot. This is if you are looking for the easy fix, and assuming I understand everythign you have done to this point
I have downloaded this file to use as my stock RUU
"RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_relea
se_204108_signed.exe".
I will go through steps 1 to 8 of the thread and the rest if I can. I am not sure about step 8, it says boot to android. Are you saving if I managed to get that far I will have some kind of working system back before I proceed further?
I will have a go now and let you know how I get get long.
Cheers!
as I stated you may not need to do the misc version part. and you do not need to flash recovery and su if you already have both
I followed the steps and apllied the HTC unlocker again, then flashed the recover.img with no error messages and put the Super User zip on my external SD card. I used the CWM install from zip option, seemed to proceed, no errors reported. When I re-booted the tablet I just have an empty black screen and nothing else. Should I proceed with the RUU or stop and try something else?? If I turn it off it immediately comes back on again to blank screen. The only way to keep it turned off is to use the power down option on hboot menu.
you were unlocked
you already had recovery
you already had super user
you did not have to repeat any of these steps
if you can get into hboot then follow the instructions to revert assuming you have the three things mentioned above. You can likely skip the misc-version step. If you get a message while flashing the ruu that states older version you will have to do the misc-version step which since you can not boot into android can be done in recovery as adb will see your device in recovery
I do not really think you are in too bad of a way right now, but without meaning to offend you, you scare me with not paying attention to what is being said. One concern I have is to make sure you have enough battery life left. If you hit less than 30% you will not be able to run the RUU. If you are confident that you have that much continue. If not power down through fastboot and charge for a couple of hours.
Please read, read, read, and do nothing unless you are atleast 50% confident that you understand
Hi
I really appreciate the help you are giving me. The only did all the steps just in case as I am paranoid about missing something important. I do think I have enough battery so I will see if I can use the RUU I downloaded
Thanks
I am now running the RUU, it says "updating rom image". It is showing a black screen with the letters HTC in white in the middle. I hope this works.
Thanks for your help.
Comment has been edited, sorry for silly question, answered in thread you mentioned
that is normal
My god, I am so relieved. To tired to be estatic. It's taken me 24 hours and only two hours sleeps to get back to Stock! You save my bacon Mcord! The battery after flashing was nearly 100%. Thankfully I kept it charging even though it was bricked in an attempt to increase the rescue time I had. The only downside is I missed a ski class I'd paid for and having to pay the "Filefactory" company for a subscription so I could reliably download the RUU.
I've learnt the hard way for sure. Anybody else reading this don't assume that just reading the instructions is enough. My SD Card had corrupt backup recovery files on it. How often do we double-check the integrity of our backups? the SD card may have also mean that the rom loaded onto it was corrupt as well. I should have checked the MD5 of all the files.
Thanks again!! I think I'll pause a bit before Honeycomb and def backup!
happy your back up and running. your problem was just not fully understanding the differences between GB and HC and S off and HTC Dev unlock. the thread I linked you is the one to use going forward if moving to HC and looking to run custom roms. As I mentioned before read, read, read.
What if in addition adb don't work ?
Hello,
I tried to downgrade, but the adb command don't work : device not found response...
So I connot follow the process explained http://forum.xda-developers.com/showthread.php?t=1307759
Second the CWN is broken too... Is that a problem ?
Thanks
Just decided to root my Rezound mostly because of the need for wireless tether. I'm fairly new to this method of rooting, but have rooted an HTC EVO 4G about a year ago and that went much smoother. After trying to figure out the order of things (which i'm not sure i did correctly), I finally started the process I followed which i've outlined below. I successfully rooted, but once i updated to the most recent RUU (3.14.605.5) and semi-successfully S-OFF (i'll explain below), i noticed that i no longer have root access. Tried to re-root, but nothing has worked... Anything i can do??
Here is the process I took (mainly tried to follow this a playlist on youtube i found - sorry can't post a URL):
1. Unlocked Bootloader via HTCDev
2. Tried to perform root with OneClickRoot 1.1, this didn't work.
3. Googled other ways to root the rezound
4. Found rEZoundRoot 1.5 - Tried it and obtained root.
5. Updated SuperUser app, verified root access worked
6. Installed clockwork touch recovery as per the video playlist above
7. At this point i kept reading about all the ICS ROMs out there and decided that's what i was going to update. Noticed that it looked just easier to update the firmware and S-OFF before putting a custom ROM on
8. downloaded the RUU 3.14.605.5. and flashed to phone.
9. during this process i had to relock the bootloader, so i had to unlock again.
10. The RUU also updated firmware
11. Followed the S-OFF directions by running ControlBear for 3.14.605.5
12. Here's where it gets weird. First of all it took me about 10 times to get the wire trick down. but once i finally did, the phone jacked up? along the way (not sure what happened, but there was a picture of a phone with a red triangle with an exclamation point in it). By the time this showed up, ControlBear had timed out. I then pulled battery and restarted. checked bootloader and it's showing S-OFF now. Fully booted phone and it started just fine. Figured everything was OK and continued on
13. After the phone booted i noticed superuser was no longer installed (since the RUU update) I redownloaded. Tried to update, and that's where it failed gaining root access. I then tried to re-root with rEZoundRoot 1.5 and that didn't work (still no root access). Then tried with OneClickRoot 1.1, this time it did much more than the first time, appearing to work. Phone rebooted but still no root.
This is now where i'm at... Stuck with S-OFF and RUU 3.14.605.5 and NO ROOT. Anyone have any ideas??
This is what my hboot says:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
The "TAMPERED" was never there until one of the final steps above. Not sure if that has something to do with it or not.
Basically all i want to do is have rooted phone with the newest firmware and S-OFF. Then apply any custom ROMs from there as I see fit.
If anyone can help, it'd be greatly appreciated! Thanks in advance.
biscuitgod said:
Just decided to root my Rezound mostly because of the need for wireless tether. I'm fairly new to this method of rooting, but have rooted an HTC EVO 4G about a year ago and that went much smoother. After trying to figure out the order of things (which i'm not sure i did correctly), I finally started the process I followed which i've outlined below. I successfully rooted, but once i updated to the most recent RUU (3.14.605.5) and semi-successfully S-OFF (i'll explain below), i noticed that i no longer have root access. Tried to re-root, but nothing has worked... Anything i can do??
Here is the process I took (mainly tried to follow this a playlist on youtube i found - sorry can't post a URL):
1. Unlocked Bootloader via HTCDev
2. Tried to perform root with OneClickRoot 1.1, this didn't work.
3. Googled other ways to root the rezound
4. Found rEZoundRoot 1.5 - Tried it and obtained root.
5. Updated SuperUser app, verified root access worked
6. Installed clockwork touch recovery as per the video playlist above
7. At this point i kept reading about all the ICS ROMs out there and decided that's what i was going to update. Noticed that it looked just easier to update the firmware and S-OFF before putting a custom ROM on
8. downloaded the RUU 3.14.605.5. and flashed to phone.
9. during this process i had to relock the bootloader, so i had to unlock again.
10. The RUU also updated firmware
11. Followed the S-OFF directions by running ControlBear for 3.14.605.5
12. Here's where it gets weird. First of all it took me about 10 times to get the wire trick down. but once i finally did, the phone jacked up? along the way (not sure what happened, but there was a picture of a phone with a red triangle with an exclamation point in it). By the time this showed up, ControlBear had timed out. I then pulled battery and restarted. checked bootloader and it's showing S-OFF now. Fully booted phone and it started just fine. Figured everything was OK and continued on
13. After the phone booted i noticed superuser was no longer installed (since the RUU update) I redownloaded. Tried to update, and that's where it failed gaining root access. I then tried to re-root with rEZoundRoot 1.5 and that didn't work (still no root access). Then tried with OneClickRoot 1.1, this time it did much more than the first time, appearing to work. Phone rebooted but still no root.
This is now where i'm at... Stuck with S-OFF and RUU 3.14.605.5 and NO ROOT. Anyone have any ideas??
This is what my hboot says:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
The "TAMPERED" was never there until one of the final steps above. Not sure if that has something to do with it or not.
Basically all i want to do is have rooted phone with the newest firmware and S-OFF. Then apply any custom ROMs from there as I see fit.
If anyone can help, it'd be greatly appreciated! Thanks in advance.
Click to expand...
Click to collapse
There are stock rooted versions of the leak, it would be easiest to just flash one on your phone. Scott has them posted and the PKMN Team for Sense 4.0 is amazing!
If you really want to root it yourself first (which isn't necessary) you could use Amon Ra install SU, and flatest binaries zip for SU. That's what I did at first so I could take a stab at customizing and designing.
biscuitgod said:
Just decided to root my Rezound mostly because of the need for wireless tether. I'm fairly new to this method of rooting, but have rooted an HTC EVO 4G about a year ago and that went much smoother. After trying to figure out the order of things (which i'm not sure i did correctly), I finally started the process I followed which i've outlined below. I successfully rooted, but once i updated to the most recent RUU (3.14.605.5) and semi-successfully S-OFF (i'll explain below), i noticed that i no longer have root access. Tried to re-root, but nothing has worked... Anything i can do??
Here is the process I took (mainly tried to follow this a playlist on youtube i found - sorry can't post a URL):
1. Unlocked Bootloader via HTCDev
2. Tried to perform root with OneClickRoot 1.1, this didn't work.
3. Googled other ways to root the rezound
4. Found rEZoundRoot 1.5 - Tried it and obtained root.
5. Updated SuperUser app, verified root access worked
6. Installed clockwork touch recovery as per the video playlist above
7. At this point i kept reading about all the ICS ROMs out there and decided that's what i was going to update. Noticed that it looked just easier to update the firmware and S-OFF before putting a custom ROM on
8. downloaded the RUU 3.14.605.5. and flashed to phone.
9. during this process i had to relock the bootloader, so i had to unlock again.
10. The RUU also updated firmware
11. Followed the S-OFF directions by running ControlBear for 3.14.605.5
12. Here's where it gets weird. First of all it took me about 10 times to get the wire trick down. but once i finally did, the phone jacked up? along the way (not sure what happened, but there was a picture of a phone with a red triangle with an exclamation point in it). By the time this showed up, ControlBear had timed out. I then pulled battery and restarted. checked bootloader and it's showing S-OFF now. Fully booted phone and it started just fine. Figured everything was OK and continued on
13. After the phone booted i noticed superuser was no longer installed (since the RUU update) I redownloaded. Tried to update, and that's where it failed gaining root access. I then tried to re-root with rEZoundRoot 1.5 and that didn't work (still no root access). Then tried with OneClickRoot 1.1, this time it did much more than the first time, appearing to work. Phone rebooted but still no root.
This is now where i'm at... Stuck with S-OFF and RUU 3.14.605.5 and NO ROOT. Anyone have any ideas??
This is what my hboot says:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
The "TAMPERED" was never there until one of the final steps above. Not sure if that has something to do with it or not.
Basically all i want to do is have rooted phone with the newest firmware and S-OFF. Then apply any custom ROMs from there as I see fit.
If anyone can help, it'd be greatly appreciated! Thanks in advance.
Click to expand...
Click to collapse
When you flashed the RUU, you lost root and should have rerooted before running the controlbear. The controlbear requires root and maybe that is what led to your problem. I s-offed first and then updated the firmware. I then had to flash Amon-RA recovery in a PH98IMG file and install SU (through the recovery's advanced menu) to regain root. Finally was able to flash the ROM of my choice.
Thanks for the replies! I actually found a fix LATE last night which worked great. I would've posted the URLs for reference, but I can't... So here's a snipit of that post:
I went back to unlimited dot io, downloaded the ICS hboot package for vigor, and followed the instructions:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
I also had to:
fastboot reboot
That last line was left out of the instructions. Good thing I found that in some random forum thread, because I thought something had failed: the progress bar on the HTC screen during 'flash zip' just sits there at like 3/4 full. Anyway, once I did that, I rebooted back to fastboot and was able to flash Amon Ra. Then I booted to Amon Ra recovery, mounted the external SD card over USB and copied up the SuperUser zip package at androidsu dot com, unmounted USB, went to flash zip menu, and installed that. Rebooted to Android and I now have root.
Click to expand...
Click to collapse
Following all of that seemed to work in my case, but now seeing what TopGun wrote, I just had the order of things wrong... Good to know for next time and just happy I got it taken care of!
Thanks for the replies everyone.
I have an Evo3d through Sprint and about a month ago they started sending me notifications to upgrade to Ice cream sandwich. I did such and immediately my touchscreen started going crazy. If I used the keypad in either position it would just randomly add letters all over the place, the home row would just stop working, and the phone would occasionally appear to lock up. I took the phone into the Sprint repair center and they told me they would not do anything with it because there is a incredibly small dent along the bezel that happened when I dropped the phone over 1 year ago. It has worked for at least a year on Gingerbread with 0 issues. I was then left to my own devices and after looking at several guides finally decided on a guide video to use for flashing to a custom rom, which I was hoping would fix the problem.
I unlocked the phone, simple enough, and from what I could find came to the conclusion that the guide which was for HBOOT-1.50 S-ON was the same image and process for my phone which is HBOOT-1.58 S-ON. I then used the cwm-4.0.1.4-shooter image to load into a "revolution" menu which allowed me to select the ROM which I had previously loaded onto the phone in the sdcard root directory. I selected MeanROM-v45 as per the video's recommendation and it told me it installed. I then rebooted the phone and saw the fancy new loading animation, then I saw the phone background, then I saw the unlock ring, then the phone rebooted in a never ending cycle. After reading the countless threads on what could be wrong, I tired MeanRom-v4.1, and the stock rom which I was led to believe was "Kingdom_Sprint_WWE-0.81.651.0_Radio_1.05.00.0429_NV-SPCS_2.25_0429_PRL21078_test_188785" and it gave me an error when trying to install. I then did more reading and found a new boot image which is "recovery-clockwork-5.0.2.0-shooter" and another rom which claimed to be stock which was "Shooter_S_Sprint_WWE_2.17651.5_odex". This rom reset the boot animation to the stock Sprint one, but alas all my phone does is constantly reboot, except I did notice it says "Safe Mode" in the lower right hand corner of the background before it reboots. I then tried to use the "RUU_Shooter_ICS_35_S_Sprint_WWE_2.89...." application which I was linked to from one forum post or another, and it gives me an error 155, then gives me another error when it tries to recover. Does anyone know how to correct what I apparently messed up? Sometimes some of the instructions are filled with lingo that i don't quite understand, but i can follow directions if they are sufficiently given.
joebandli said:
I have an Evo3d through Sprint and about a month ago they started sending me notifications to upgrade to Ice cream sandwich. I did such and immediately my touchscreen started going crazy. If I used the keypad in either position it would just randomly add letters all over the place, the home row would just stop working, and the phone would occasionally appear to lock up. I took the phone into the Sprint repair center and they told me they would not do anything with it because there is a incredibly small dent along the bezel that happened when I dropped the phone over 1 year ago. It has worked for at least a year on Gingerbread with 0 issues. I was then left to my own devices and after looking at several guides finally decided on a guide video to use for flashing to a custom rom, which I was hoping would fix the problem.
I unlocked the phone, simple enough, and from what I could find came to the conclusion that the guide which was for HBOOT-1.50 S-ON was the same image and process for my phone which is HBOOT-1.58 S-ON. I then used the cwm-4.0.1.4-shooter image to load into a "revolution" menu which allowed me to select the ROM which I had previously loaded onto the phone in the sdcard root directory. I selected MeanROM-v45 as per the video's recommendation and it told me it installed. I then rebooted the phone and saw the fancy new loading animation, then I saw the phone background, then I saw the unlock ring, then the phone rebooted in a never ending cycle. After reading the countless threads on what could be wrong, I tired MeanRom-v4.1, and the stock rom which I was led to believe was "Kingdom_Sprint_WWE-0.81.651.0_Radio_1.05.00.0429_NV-SPCS_2.25_0429_PRL21078_test_188785" and it gave me an error when trying to install. I then did more reading and found a new boot image which is "recovery-clockwork-5.0.2.0-shooter" and another rom which claimed to be stock which was "Shooter_S_Sprint_WWE_2.17651.5_odex". This rom reset the boot animation to the stock Sprint one, but alas all my phone does is constantly reboot, except I did notice it says "Safe Mode" in the lower right hand corner of the background before it reboots. I then tried to use the "RUU_Shooter_ICS_35_S_Sprint_WWE_2.89...." application which I was linked to from one forum post or another, and it gives me an error 155, then gives me another error when it tries to recover. Does anyone know how to correct what I apparently messed up? Sometimes some of the instructions are filled with lingo that i don't quite understand, but i can follow directions if they are sufficiently given.
Click to expand...
Click to collapse
Well since you are S-on and unlocked you have to relock your bootloader to run ruu files. Fastboot oem lock is the command you run in fastboot. Also with older ruu files they only work with older roms and such. as for newer ones like the ics ruu, ics roms such as meanrom ics v2.6 works with only hboot 1.58 and newer firmware. I understand that sometimes these guides and tutorials are not clear enough. That's why you got to ask questions. We are here to help so you can get the best out of your experience with your evo 3d. I would not rely on sprint techs too much because sometimes they will just tell you to do a factory reset. Your phone should be fine. Just relock your bootloader and run the file from the bootloader screen and everything should be peachy. If you want to flash a custom rom after you do the update just unlock your bootloader again. Flash 4ext recovery for your device and do some research on what roms and kernels are compatible with S-on unlocked bootloaders. Fyi 4ext recovery has this thing called the smart flash option that allows you to flash kernels through their recovery without having to do through fastboot. Or try Joeykrims Flash Gui Image. All in all, gaining s-off is the best route to solve most of your problems and makes it easier to flash roms and kernels. There is a method for gaining s-off with the ics ota and hboot 1.58. Just do your research. Best of luck to you.
Oh yeah don't forget to hit the thanks button if I helped you out at all.
Jsparta26 said:
Your phone should be fine. Just relock your bootloader and run the file from the bootloader screen and everything should be peachy.
Click to expand...
Click to collapse
Which file are you reffering to from the bootloader screen?
When I Vol Down + Power On this is what I see
***RELOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012,15:06:44
HBOOT
Now that I have relocked the phone it tries to load PG86DIAG.zip (No Image!), PG86DIAG.nbh (No Image!), PG86DIAG.zip (No Image or wrong image!), PG86IMG.zip, and then it does "Checking..[PG86IMG.zip]" and returns Main Version is Older! Update Fail! Press <Power> to reboot.
I know several of the tutorials and even the "How to Fix" guides I was trying to use to restore the phone has me copy PG86IMG.zip to the sdcard root, so I am guessing I need a different image. Now the only problem is that I have to re unlock the phone so I can "fastboot boot cwm-4.0.1.4-shooter.img" so that I can mount the phone and transfer files to and from it (unless there is another method I can use other than adb, because it does not see it as an attached device)
So what I should do is:
1, Unlock the phone again
2, fastboot boot cwm-4.0.1.4-shooter.img
3, Mount the phone, and copy a file named "PG86IMG.zip" (Which I need to obtain the correct one)
4, Unmount the phone and then relock it?
What would the next step be and do you know where I can get the correct file?
I appreciate the response, I am at my wits end and was about to go waste some cash buying a new phone.
joebandli said:
What would the next step be and do you know where I can get the correct file?
I appreciate the response, I am at my wits end and was about to go waste some cash buying a new phone.
Click to expand...
Click to collapse
Forget about PG86IMG.zip files. Since you are S-ON they have to be signed by HTC and there are very few of those around.
You need the 2.89 RUU.exe from one of the links in this post. Flash that from Windows, then HTC unlock again and follow the guides to flash a custom recovery and then root the stock ROM or a rooted custom ROM.
ramjet73
ramjet73 said:
Forget about PG86IMG.zip files. Since you are S-ON they have to be signed by HTC and there are very few of those around.
You need the 2.89 RUU.exe from one of the links in this post. Flash that from Windows, then HTC unlock again and follow the guides to flash a custom recovery and then root the stock ROM or a rooted custom ROM.
ramjet73
Click to expand...
Click to collapse
Thank a ton, that worked to put my phone back to "working" icecream sandwich.
The back story...
I had to ditch Verizon. I didn't want to fork over $300 for a Republic Wireless phone only to be stuck with their crappy ROM, and the only 4G LTE android phone supported by Ting is the Evo 4G LTE; picked one up for $50 on ebay. I installed Cyanogenmod on a half dozen devices, newer and older than this phone, and thought this HTC Evo 4G LTE would be as easy as they were to unlock, root, S-OFF and flash. I've been more wrong before, but not without resulting in bodily harm. A hearty 'get stuffed' to HTC for this, and a plea for future rooters to have a concise guide on how to repair their phone under these circumstances.
The flawed process...
I went through HTC's unlock method to unlock the phone. Then I installed the latest TWRP via fastboot command line (2.7.1.0b as I found in a thread somewhere). No problems so far... I then went to install the latest CM build for Jewel (10.2.0 ) through TWRP 2.7.1.0b and it failed. This marked the first time I'd ever seen a fail message in TWRP. I thought no big deal, I'll restore the backup... The backup was gone. Now we have problems; phone is stuck in a bootloop. After reading many threads stating that S-OFF is required to flash their ROM, I tried to achieve that in Windows 7 to no avail through all available means. I then tried the closest RUU for my phone, and it failed. I then tried every RUU I could find, all failed. I tried a full firmware update to 4.13 via PJ75IMG.zip on the SD card, which failed.
The repair process that worked for my situation...
Once I focused on the HBOOT as a potential issue, I found this thread: http://forum.xda-developers.com/showthread.php?p=40848479#post40848479
Quite simply, MeanBean 3.09 worked as advertised, and my phone has booted into a ROM for the first time in days! A HUGE thanks to both Magnum_Enforcer and mikeyxda.
Specific phone information
TAMPERED
UNLOCKED
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.13.11.0830
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012, 15:46:20
IMAGE CRC
rpm: 0xBC1CB8D
sbl1: 0x507A9B32
sbl2: 0xEAF345D0
sbl3: 0xD5BB18AD
tz: 0xFB084399
radio: 0xC78A66EB
boot: 0xB683E2D
recovery: 0xB47A92E4
system: 0x376A0C9B
Software Version Reported by RUU: 3.17.651.5
Glad to help:thumbup:
Sent from my HTC device
I'm going to keep this log going, since I think quite a few people will follow a similar path as I'm following.
Just tried to achieve S-OFF with the new MeanBean ROM I'm running.
First attempt: Firewater
All of the steps went exactly as expected. The command line dialog was amusing, and ended in "nasty, needs a chaser" or something and rebooted to the ROM. Once rebooted into recovery to verify s-off status, S-ON is reported.
Second attempt: Rumrunner
More interesting dialog in the process, and it, too, went smoothly. Rebooted into bootloader and voila...S-OFF achieved.
Installed Dirty Unicorns 4.4.4
So, after the first day's use I've come to realize that my PRL needs updating and the Dirty Unicorn 4.4.4 ("du_jewel_4.4.4_20140621-0657") ROM doesn't have a 'Update PRL' function as far as I can tell. I backed up DU 4.4.4 and restored MeanBean, updated the PRL, and restored back into DU 4.4.4 with ease.
After using DU for a week, I've come to realize it's fairly unstable. I'll be looking for a different rom soon.
OMG!!!! FINALLY!!!
I've been reading and reading and pulling my hair out for 3 days after attempting to load a custom Rom on my Evo 4G LTE.
I have almost exactly the same situation/experience as you did. I was able to get the CyanogenMod to load but for the life of I can't get any gapps installed. I've tried loading from TWRP and the SDcard to no avail. It looks like it flashes fine but when I reboot the phone no apps are installed. I like CM 10.2.0 but I need the Google apps. Right now I'm missing so many things like contacts, etc. I've tried to install Google Play and just download each app individually but it crashes on start. I'm really feeling lost here and helpless. I never had problems like this with my original EVO or EVO 3D. Tried to go back to stock using Sprint RUU's but nothing works...
I've highlighted my differences in RED.
Is there anyway you could explain your method to get your EVO S-off in more detail? Is this the problem?
SethW said:
The flawed process...
I went through HTC's unlock method to unlock the phone. Then I installed the latest TWRP via fastboot command line (2.7.1.0b as I found in a thread somewhere) (I loaded TWRP 2.7.1.0 which seemed to work) . No problems so far... I then went to install the latest CM build for Jewel (10.2.0 ) through TWRP 2.7.1.0b and it failed (I was able to load CM 10.2.0 through Fast Boot boot.img command) . This marked the first time I'd ever seen a fail message in TWRP. I thought no big deal, I'll restore the backup... The backup was gone (Same here, Backup gone). Now we have problems; phone is stuck in a bootloop (I watched the CyanogenMod screen spin for 2 hours). After reading many threads stating that S-OFF is required to flash their ROM, I tried to achieve that in Windows 7 to no avail through all available means (same here, tried several ways but nothing worked for Windows 7). I then tried the closest RUU for my phone, and it failed (same here). I then tried every RUU I could find, all failed. ( I tried a full firmware update to 4.13 via PJ75IMG.zip on the SD card, which failed.
Specific phone information My Info is exactly the same
TAMPERED
UNLOCKED
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.13.11.0830
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012, 15:46:20
Software Version Reported by RUU: 3.17.651.5
Click to expand...
Click to collapse
airdog99 said:
Is there anyway you could explain your method to get your EVO S-off in more detail? Is this the problem?
Click to expand...
Click to collapse
I just ran the program as it specified. Make sure your drivers are installed correctly... that step usually caught me up because some Android device drivers conflicted with some of my other Android device drivers.
Hello All,
I've spent hours on this forum and other, reading related subject, and I've tried so much things (probably some of them worsening my situation) so I'm asking for help now. I'm kind of a newbie so please be comprehensive.
So I've an HTC Desire X and thanks to Hasoon2000's Desire X All-In-One Kit v1.1 I've unlocked bootloader and flashed clockworkmod 6.1.5.
My phone worked perfectly until there was an official update for my android version, and it was impossible to install it.
So i needed to go back to stock basically. And that's where i screwed.
Obviously i didn't make a backup or nandroid before starting to play around.
I think i might have install kernel and recovery from earlier version that the one i had and this caused the problem? any way now the status is:
I cannot start my phone normally. I can only start it in fastboot mode. When i want to reboot it in recovery the HTC screen with "starting recovery" appears for 1 sec and then i've got a black screen and the only way out is reboot it to fastboot mode again.
when connected to my computer i can load boot.img or recovery.img via fastboot in cmd; but it doesn't change the situation.
I think the problem may come from the fact that when i cmd "adb devices", he cannot find any device. Even though i've installed the HTC drivers!
Details:
PROTO PVT SHIP S-ON RL
HBOOT-1.25.0002
RADIO-1.15.40.04
eMMC-boot
Apr 3 2013, 15:50:50:0
my CID is HTC__E11
So then in order to fix that i've tried to RUU using the only RUU availables (with relocked bootloader): RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed
RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed
but it doesn't work: a part from the fact that there's a blank after "From: Image version: ", when i try to update to image version 1.14.401.1, during the install it stop with ERROR 158 : IMAGE ERROR , telling me that i've to find a ROM that is adapted for me.
Well. Somebody have any idea how i can get my phone functionning again?
chirou321 said:
Hello All,
I've spent hours on this forum and other, reading related subject, and I've tried so much things (probably some of them worsening my situation) so I'm asking for help now. I'm kind of a newbie so please be comprehensive.
So I've an HTC Desire X and thanks to Hasoon2000's Desire X All-In-One Kit v1.1 I've unlocked bootloader and flashed clockworkmod 6.1.5.
My phone worked perfectly until there was an official update for my android version, and it was impossible to install it.
So i needed to go back to stock basically. And that's where i screwed.
Obviously i didn't make a backup or nandroid before starting to play around.
I think i might have install kernel and recovery from earlier version that the one i had and this caused the problem? any way now the status is:
I cannot start my phone normally. I can only start it in fastboot mode. When i want to reboot it in recovery the HTC screen with "starting recovery" appears for 1 sec and then i've got a black screen and the only way out is reboot it to fastboot mode again.
when connected to my computer i can load boot.img or recovery.img via fastboot in cmd; but it doesn't change the situation.
I think the problem may come from the fact that when i cmd "adb devices", he cannot find any device. Even though i've installed the HTC drivers!
Details:
PROTO PVT SHIP S-ON RL
HBOOT-1.25.0002
RADIO-1.15.40.04
eMMC-boot
Apr 3 2013, 15:50:50:0
my CID is HTC__E11
So then in order to fix that i've tried to RUU using the only RUU availables (with relocked bootloader): RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed
RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed
but it doesn't work: a part from the fact that there's a blank after "From: Image version: ", when i try to update to image version 1.14.401.1, during the install it stop with ERROR 158 : IMAGE ERROR , telling me that i've to find a ROM that is adapted for me.
Well. Somebody have any idea how i can get my phone functionning again?
Click to expand...
Click to collapse
i'm not sure if you're able to install a ics-ruu when you're on hboot for jellybean (1.25).
get twrp-recovery for jellybean, install it via fast boot and install a jellybean rom via recovery, like the stock one
http://forum.xda-developers.com/showpost.php?p=36714573&postcount=2
http://forum.xda-developers.com/showthread.php?t=2239511
btw. using adb in bootloader doenst work, so its no surprise it doesnt find any device.
Worked out perfectly! My phone is working again!
Thank you so much realCyphox !
:good:
Now I'll try to see if it's possible to install the official updates.