Related
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
I had much the same problem with my cdma, hboot 1.5, S-On shooter. When I was S-On none of the ICS roms would work. The all bootlooped on me. If you follow the rooting method found here on xda, it will get you back to a stock Rooted GB Rom.
go into hboot -> fastboot USB-> run command dos -> fastboot cwm-4.0.1.4-shooter.IMG -> flash the 2.17 firmware-> enjoy.
I had to S-off with Juopunutbear, then re-run that root/flash to get past the bootloops.
Sent from my Shooter using xda app-developers app
Unfortunately I have tried that and it still is not working.
My only suggestion would be to try it a few times, other then that, its above my head.
Sent from my shooter using xda app-developers app
rookiemistake said:
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
Click to expand...
Click to collapse
Have you tried one of the ruu exe files that you run from your computer? If you are trying to go stock, you should be able to relock the bootloader and run the ruu and that's it.
Sent from my ICS 3VO with Tapatalk 2
First of all I want to thank everyone that has been attempting to assist me with my problem. I have tried to relock since I am on htcdev unlock and then run an ruu force via my computer. I get an installation aborted error when trying to flash pg86img via recovery. I don't know what else to say.
You can't flash a bootloader zip from recovery. You have to flash it from hboot. Also make sure the zip is named correctly "PG86IMG.zip" without the quotes. Also make sure the zip is on the root of your sd as in not in any folders. Once you've named the zip correctly and placed it correctly then power off the phone. Hold down the volume down button and tap the power button. You should boot into the bootloader wait until the phone recognizes the zip and follow the on screen instructions. Hopefully this helps.
#Root-Hack_Mod*Always\=LTE
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
rookiemistake said:
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
Click to expand...
Click to collapse
To get the ota release (if it ever comes ) I do believe you will need to be locked and running the existing gingerbread rom. While I am not positive, I think the system uses the props file to determine if an update is applicable, and it will likely not recognize the teamgenesis rom version as being upgradeable.
Now I will likely get flames for saying this, but if you want to put the meanrom v2.4 of ICS on the phone, it can be done with s-on, you just need to follow the correct process. I ran that rom for a while, and it is very stock like, stable, and has a few enhancements that you will not find on a non-rooted stock rom. I never found anything wrong or not working with that rom.
To get it to load, first I downloaded flashimagegui from market, put the meanrom zip file on the sd card and made sure I had a recovery that I could get into. I am using TWRP v2.1.1, lots of folks talk about others like ext4, and I am only going to say use whichever you like, after all it is your phone.
Then with the phone unlocked via the htc method, I started the flashimage app, and browsed to the meanrom file. It extracted the kernel and flashed it. Once that was done, with clear cache buttons selected, rebooted to recovery, and used the install menu selection of TWRP to again flash the same rom file. Once it flashed the file, selected clear cache and dalvik just to be safe, selected reboot system, and it worked great.
Have a great weekend.
So, apparently I am still doing something wrong. I have put the pg86img on the root, relocked to the bootloader, and let it run it's course. However, it will get through with reading it and stops and does not finish anything with loading the system information. I have also tried to run the ruu via usb connection. I keep running into a c++ issue saying runtime error. I have wiped everything and thankfully I did make a backup of the rom and other information that I was runing so I can currently fall back on that.
I am on hboot 1.5, 2.17, and teamgenesis ICS rom for evo 3d.
Apparently there have been rumors that Sprint has finally released the ICS OTA, not that it really matters anymore, but I have run into a few interesting glitches, such as WIFI not staying connected while asleep or disconnecting.
If I have to I am willing to pay to do a netmeeing with someone in order to be able to fix this.
Sorry if it sounds like I am getting frustrated, but I have tried every walkthrough that I have found and have not had any luck with any of them.
Please help.
I forgot to say I am s-on
So I have Scott's CleanROM GBE 1.7.5 on my phone. I was wandering through my phone's settings, and accidentally hit something in the update area. I do not know what I was thinking, but I know I expected it to ask me if I was sure I wanted to update. So far it has only done the first part where it prepares the phone for the update. I do not know when the other part is coming but I assume it is automatic. I was planning on updating to a rooted ICS once I felt comfortable with it (just seemed a little harder than my original flash of rooted GB). So if it would be easier to just update to ICS some way now, I would be very willing to do that. I am s-on, I believe I installed Amon Ra, but I am not sure how to check and not sure if I have an actual recovery rom or not.
I checked around and found similar problems, but nothing really like mine since my update has not gone all the way thru yet. If anyone could help, it would be greatly appreciated. THank you.
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok just to make sure I know and don't mess anything else up. I relock (should be easy to.find a guide) . Then run the update on my phone? Then unlock thru HTC again, and flash the actual amon or CWM to my phone? And from there I will be able to flash any ICS Rom with more ease?
And thank you for the quick reply.
Edit: I searched the internet more for less-similar situations. I think all I have to do is re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Also,nothing I have to do as far as unrooting?
malignancyy said:
Also,nothing I have to do as far as unrooting?
Click to expand...
Click to collapse
Nope just relock the bootloader
AshtonTS said:
Nope just relock the bootloader
Click to expand...
Click to collapse
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
malignancyy said:
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Click to expand...
Click to collapse
Then you just have to press continue when it tells you to.
PS: Another way to get to the bootloader is to use adb (make sure USB debugging is enabled on your phone)
Command:
adb reboot bootloader
I find it easier than holding down buttons for a long time, but that's just my personal preference.
(Also, most custom ROMs can reboot to bootloader from within the ROM. I forget if CleanROM GBE includes the advanced power menu.)
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good advise, and if he RUUs to ICS, then he should not even get asked to install the update because it will already be installed on his phone.
Also RUU twice. Just reboot into bootloader right away and install the RUU a second time. Then boot up normally and remove the zip file from the sdcard.
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
malignancyy said:
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
Click to expand...
Click to collapse
The jbear hboot might have failed because you are on the newest global update with 2.27 hboot, and I believe the controlbear tool still has the 2.25 hboot. (someone correct me if I'm wrong)
I think there is an unguarded 2.27 hboot somewhere, so you should flash that manually.
Sent from my NeoMax Rezound
Right now, like I said the hboot says at the top 2.27.0000
When I reboot from there, or boot it regularly it goes to a JuopunutBear, black and green writing screen.
I have tried to install this forum.xda-developers.com/showthread.php?t=1843030 ([HBOOT] HBoot 2.27 (from 4.03.605 OTA) Unlocked) from both, but cannot figure out how to do so.
edit: within JuopunutBear, wiping says "can't open" and applying update gives "failed to open loopdevice" and "failed to mount /sdcard" when I try to update.
Within the regular hboot, I get "no image" as it searches for files.
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
A little more info on this. Windows tries installing QHUSB_DLOAD driver for it when plugged in, but unsuccessfully. The charging indicator does not come on either. Have tried to turn it on plugged in with battery out, and battery in both ways.
malignancyy said:
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
Click to expand...
Click to collapse
Depending on what caused the brick, it may be recoverable.
Check out the unbricking thread in the dev section.
Sent from my NeoMax Rezound
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
malignancyy said:
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
Click to expand...
Click to collapse
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
wlmeng11 said:
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
Click to expand...
Click to collapse
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
malignancyy said:
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
Click to expand...
Click to collapse
That QA is outdated.
It was referring to using the 3.14.605.07 kernel as opposed to the then-most-recent 3.14.605.10
Back then those two builds were similar enough that they could mix n match without issues.
Between 3.14.605.12 and 4.03.605.1 is a lot of changes. (whole number change to represent it) Specifically, new hboot and radios. Therefore, it is incompatible with the older kernels.
When you're S-ON you can't touch the radios except through an official RUU.
Even with s-off I doubt you can flash radios from recovery (not sure on this one), and NeoMax doesn't have any radio files anyway. (nor does any rom I know for this phone)
If you haven't yet updated to 4.03.605.1 then I recommend that you stay on 3.14.605.12 until Neo updates the ROM.
If you already updated, it is still possible to run NeoMax. You just have to manually flash the new 4.03.605.1 kernel after installing the ROM.
Sent from my NeoMax Rezound
Let me start off by saying that I'm a complete idiot and wasn't being very careful.
I have several problems with my Rezound right now and I'll try to be clear and concise. My internal SD card won't mount in the recovery menu, nor HBOOT, therefore I cannot flash PH98img.zip in HBOOT. My external SD will mount, but I'm not sure if the PH98img.zip will work from the external SD because it doesn't show up in HBOOT. My HBOOT reads as follows:
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.10.00000
eMMC-boot
OCT 5 2011,21:18:48
And also, here's a weird thing: My phone will show up in adb devices only when the phone is off or when I'm in the Recovery menu. My phone won't appear in adb devices when I'm in HBOOT menu. I'm running ClockworkMod Recovery v6.0.2.3.
I have tried using a few different ROMs to no avail. I think my main problem as of now is that I cannot access my internal SD card. Before I install a ROM I wipe everything I can think to wipe, cache, dalvik cache, factory reset. Some of the ROMs have the Aroma installer where it asks if I want to wipe on those and I say yes every time. I cannot start my phone because I'm stuck on HTC white screen whenever I try to boot the phone. I've tried using the Old_Firmware_Patch.zip and the GB Firmware Patch.zip. I have had no luck so far. Again, I'm sorry that I'm not exactly sure what I'm doing and I need a bit of help. Thank you and I appreciate any help that you can give.
Additional Information
Prior to this complete failure in my phone I was using an early leak of ICS, one of Newts ROMs. His ROM didn't support 4G and had trouble with a few other things including stock wifi settings. Every time I tried to go to wifi settings the "com.settings.htc" or some such process would crash. So I wanted to update to a newer ICS ROM that hopefully supported 4G and didn't have problems with wifi settings. I thought it would be as simple as loading a ROM onto the external SD and loading it from recovery, but it wasn't that easy. Because I'm S-ON I apparently missed a few steps and forgot that I have to flash PH98img.zip. But now that I cannot access my internal SD card, I cannot flash PH98img.zip as far as I know.
First thing you want to do is get off of Clockwork Mod recovery. It doesn't play well with the Rezound. Go grab Amon Ra and flash v3.16.
Secondly, you can flash a PH98IMG file off the external sd, providing you can read it of course.
I think you are still on GB firmware based on your hboot, not completely sure about that. But it's def an old hboot.
So actually, I would run the RUU and update all your firmware, don't bother flashing Amon Ra first, do that after the RUU. Find it here:
http://androidfiles.org/ruu/?dir=Vigor
Top one, 3.14.605.12. Then after you run that, you can check for and accept the latest OTA that came out a couple weeks ago and then you'll be up to date with the official updates.
You'll need to relock the phone before running the RUU
fastboot oem lock
And save everything you need from the phone first since this will wipe everything and get you back to factory stock.
Then to run the RUU attach the phone to your pc and double click on the exe RUU file. It will do it's thing. Or you can use the following commands in fastboot to get it going:
fastboot oem rebootRUU
fastboot flash zip NameOfZip.zip
Make sure you let it go all the way through. I ran the global RUU and the screen went black for a while then it goes back to finishing up, so if that happens just let it keep going. I think you end up in bootloader when it's done, and it'll ask you if you want to reboot. You should go ahead and boot up and make sure it's working okay.
After you run the RUU you will need to unlock again. Then flash Amon Ra, flash superSU for root (though I think you can just get root via Amon Ra again now) and make a nandroid of stock so you can always go back to this when you run into trouble, then flash a custom ROM if you choose.
That should sort everything out since like I said, it'll be a clean start and you'll get everything updated.
Oh, and the PH98IMG.zip file you have to flash because of being s-on is the kernel for the ROM you are flashing. So know that each PH98IMG.zip file is not the same as the other, the ROM makes the one you need using the kernel that is specifically for that ROM. So you'll either need to pull it out of the ROM and flash via fastboot, download the separate PH98IMG file if there is one in the ROM's thread, or the ROM may make one during the flash and leave the PH98IMG file on your SD card in which case you go to bootloader and accept the update, which will be the kernel.
If you don't flash the kernel then the phone won't boot, it'll just get stuck.
One last thing, I would grab CleanWipe from the Dev section and use that for wiping whenever you change ROMs. It'll really get the job done.
Back to stock now
You, feralicious, are a beautiful person for replying so detailed lol. I got my phone to start up gladly. I just now read your post. Earlier I got it working by following a thread which basically said exactly what you said: relock using fastboot oem lock and then do the lastest RUU. It was a thing of beauty. I as so lost prior to that.
It's good to know that each PH98IMG.zip is different per rom. I had no idea. I'm going to stay stock for a while. It's just nice to finally see that 4g up on the top of my phone after having dealt with 3g only for like 6 months. I'll definitely come back to this site if I have an trouble while attempting to re-root the phone. Thanks so much for your excellent reply.
Howdy,
I've currently got an Evo 3D CDMA on Sprint, Revolutionary S-Off and downgraded HBoot. I'm experiencing issues when I try to run any ROM that isn't Sense-based, or any Jelly Bean ROM, I'm not sure. I've tried several of the "current" ROMs out there (Dirty Unicorns, PACMan, Wild for the Night, etc.) that have 4.2 and none of them allow me to receive SMS or MMS, or place or receive phone calls. I can apparently send SMS correctly, however, which is interesting. I've tried (and am currently using) booting up a Sense ROM just so I can update my profile and radios and all that jazz, but even after verifying my network settings are correct, once I go back to anything nonSenseical, I lose all my phone's capabilities.
I posted this over in the general forum, but nobody had anything intelligent to say. I'd really appreciate suggestions - anything helps!
I hate doing it, but bump for great justice. I know this isn't exactly the most pressing issue in the whole wide world, but I'd love an answer...
You never mentioned flashing a firmware.
It sounds like a radio issue.
Find your relevant firmware here:
http://forum.xda-developers.com/showthread.php?t=1447839
Make sure you have a ROM ready to flash and a backup of any important files before proceeding. Can't remember if it wipes phone or not.
-----------------------
Facebook: http://www.Facebook.com/d3xp2pc
Google+: http://gplus.to/d3xp2pc
d3xp2pc said:
You never mentioned flashing a firmware.
It sounds like a radio issue.
Find your relevant firmware here:
http://forum.xda-developers.com/showthread.php?t=1447839
Make sure you have a ROM ready to flash and a backup of any important files before proceeding. Can't remember if it wipes phone or not.
Click to expand...
Click to collapse
These are just RUUs, yes? I did flash several RUUs as part of this process, are these different? Also, won't these re-upgrade my HBoot?
DavisJ3608 said:
These are just RUUs, yes? I did flash several RUUs as part of this process, are these different? Also, won't these re-upgrade my HBoot?
Click to expand...
Click to collapse
Nope RUUs and radios are different.
Flashing a radio won't upgrade your Hboot.
RUUs are rom packages from HTC which can for example upgrade your version of android, hboot etc
Radios refer to the android radio layer which is responsible for data connection, voice etc. Just make sure you flash the right radio for your location etc.
If in doubt which one to flash then ask. Flashing the wrong radio can brick your device.
-----------------------
Download G Cloud Backup for Android, up to 8 GB Free.Use this code: [KWLYRO] at signup and we'll both earn space: https://play.google.com/store/apps/details?id=com.genie9.gcloudbackup
-----------------------
Copy: get 20GB free permanent cloud storage. For every person you get to sign-up earn another 5GB https://copy.com?r=m3asrR
d3xp2pc said:
Nope RUUs and radios are different.
Flashing a radio won't upgrade your Hboot.
RUUs are rom packages from HTC which can for example upgrade your version of android, hboot etc
Radios refer to the android radio layer which is responsible for data connection, voice etc. Just make sure you flash the right radio for your location etc.
If in doubt which one to flash then ask. Flashing the wrong radio can brick your device.
Click to expand...
Click to collapse
Makes sense. However, when I downloaded the correct file from the link you provided, it flashed what very much appeared to be an RUU (trying to update my system, bootloader, recovery, etc.), and now my phone freezes at the HTC logo when it tries to turn on, and I don't have 4EXT installed on my device anymore. I'm currently trying to run the file through again, but it gets stuck at SYSTEM, unzipping and updating over and over again.
EDIT: All right, it now says OK on every bit except for "SYSTEM" where I see "Fail-UZ", and the 1st "TP" where it says "Bypassed."
All right, here's where I'm at now. After flashing this file to my device, my phone lost its recovery software and wouldn't boot, as well as not telling me "Locked," "Unlocked," "Relocked," or "Revolutionary" as it had before. I thought I might need to HTC unlock my device again, but flashing my unlock token didn't work, and I got an error when trying to install recovery software that the phone wouldn't allow it. I ended up flashing a 1.13 RUU simply to have something that works for now - currently when I boot into Fastboot I see HBOOT 1.40.0000 (which I had before), RADIO 0.97.10.0530, and I've got Gingerbread installed as my ROM. I'm going to try to reinstall CWM or 4EXT and put ICS back on at the very least.
EDIT: OK, when I try to flash Recovery I'm still seeing the same message "FAILED (remote: not allowed)." Apparently I've lost Root?
This is a strange one but from what your describing it seems that you have lost root.
If you can get an ICS RUU flashed and rooted you shouldn't have any problems with JB roms.
Edit: been doing some further research, these links may help.
HBOOT: http://forum.xda-developers.com/showthread.php?t=1817513
Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 10-13-12
Firmware: http://d-h.st/A4q
-----------------------
Download G Cloud Backup for Android, up to 8 GB Free.Use this code: [KWLYRO] at signup and we'll both earn space: https://play.google.com/store/apps/details?id=com.genie9.gcloudbackup
-----------------------
Copy: get 20GB free permanent cloud storage. For every person you get to sign-up earn another 5GB https://copy.com?r=m3asrR
So I ran a 1.13 RUU to get myself back to a working state, re-ran Revolutionary to get my "Revolutionary" banner back, and flashed a recovery. Then I flashed the 2.95 radios, and finally cleared everything and installed a 4.2 ROM with the latest gapps. Everything seems to be working, I can apparently call and text no problem - thanks for the tip on updating my radios.
Hey everyone. After 22 logged hours of work on this phone and looking everywhere on XDA and AndroidForums I could really use some help guys. :crying: Since I cannot post links, please bear with my references.
HTC Evo 3D Shooter s-on hboot 1.58.0000 | device:HT17JHX02410 cid:SPCS_001 [sprint] mainver:2.95.651.6
Current status: stock rom successfully reloaded, relocked w/ security warning, stock rom stopped loading after relock. I can access 4ext as well as make commands from adb.
My goal is to flash PACMAN v 23.0.0 rom to my phone. I believe pacman uses Android 4.3. I tried flashing with 4ext, cwm, and twrp. As I recall the problem was an "error 7" across the board. Trying to solve this has lead me down the rabbit hole. I'm not even sure I'm on the right track anymore. I tried deleting the "assert getprop" lines from the beginning of the updater-script file as suggested by several users here, but that lead only to abortions. It may have something to do with 7zip asking whether to overwrite already existing files during extraction? I'm currently trying to return the phone to stock condition so I can downgrade to hboot 1.4 and get s-off, thus allowing me to flash PACMAN. This method was obtained from Unknownforce, Closeone, and RamJet73 all found on XDA.
Returning the phone to stock [in order to brick it via Unknownforce] has been a hassle because every tutorial requires that I lock the phone and then run the RUU update utility. I have tried several versions of this utility and they all drop the connection to my phone after restarting bootloader with an Error 170 [or 171]. There are several reasons for this error and one possible reason is that the software is incompatible. I think this is due to my mainver being 2.95 as opposed to 2.89 or lower. This is why I needed to find a .zip for the stock rom that would work, flash SetMainVersionLow, flash the rom zip, and then lock, bringing me to where I am now, which is a phone that will boot to bootloader and nothing more. This final method with setmainversionlow was obtained from remanifest on AndroidForums.com and I began using it because they mentioned something about 2.95 compatibility or something.
I can still lock/unlock the phone easily and flash any rom i wish, providing it is compatible. Where have I gone wrong? Is the PACMAN rom worth all of this!?
Thanks, all help is greatly appreciated.
-a
Update progress...
i can no longer get a recovery to load [4ext, twrp, cwm] and i think this is because i used a wonky verson of CWM. some have said CWM and htc 3vo don't play nicely together. all i have now is bootloader and adb. no rom loads either, just white screen with green HTC logo until battery dies. recovery programs flash successfully from adb but do not start.
my mainver has been reset to 1.00.000.0 and phone is relocked so i was trying to forget about the recovery and run a RUU. according to RamJet these are the two required items for running RUU. i've tried a 1.13 version as well as a 2.89 version. both of them act the same way as before -- immediately after the phone comes back and the program reads "erase user data" for one second, it fails and give me a 171 error.
please help. i'm a noob but i've looked EVERYWHERE for answers to these problems. if you have links to solutions i would appreciate that as well but i'd put money down that i've been there before.
i will never accept an OTA update again! all i need is hboot 1.4 and i'll be golden! how frustrating
Did you unlock again before trying to flash a recovery?
AFAIK there is no ruu that'll work for your phone until you get s off.
Sent from my Evo 3D CDMA using xda app-developers app
---------- Post added at 06:27 PM ---------- Previous post was at 06:25 PM ----------
Short story
You need to get recovery
Then you need to flash a ROM that works on 1.58 or 1.4/1.50 and then you can get s off and downgrade your hboot and flash pac
This is more updated
http://forum.xda-developers.com/showthread.php?t=2539241
Sent from my Evo 3D CDMA using xda app-developers app
it was a good call, but after unlocking again, recovery will still not start. i tried to erase the recovery flash partition but adb said that was not allowed. I have bootloader and adb, the ability to lock/unlock the phone, and flash recoveries unsuccessfully it would seem. there's got to be something that will fix this...
hanger-on said:
it was a good call, but after unlocking again, recovery will still not start. i tried to erase the recovery flash partition but adb said that was not allowed. I have bootloader and adb, the ability to lock/unlock the phone, and flash recoveries unsuccessfully it would seem. there's got to be something that will fix this...
Click to expand...
Click to collapse
The 1.58 bootloader apparently changes some formats in an incompatible way (I'm sure purely by chance and not to mess with custom roms).
This is what I did, alternatively there's this thread with alternate methods (more designed for windows I think).
Normal disclaimer: This is (to the best of my recent memory) what I did after mucking up my E3D. Follow at your own risk, my memory, your phone, or anything else could be faulty and you could permanently brick your phone trying the following steps.
Assuming you're CMDA and S-ON still:
If you need to fix your hboot/etc download the latest (2.89) PG86IMG.zip
Download the 1.13 PG86IMG.zip
Download SetMainVersionLow.zip (I think you already have that).
Make sure you have adb and fastboot installed and working.
Make sure you're at a stable hboot with a custom recovery.
If not flash the 2.89 RUU (see flashing RUU below).
Reunlock and apply custom recovery if needed.
Run SetMainVersionLOW.zip from a custom recovery.
Before downgrading your hboot you should be (hboot 1.89, custom recovery, "fastboot getvar mainver" = 1.00.0000)
Downgrade your hboot to 1.4.something (Possibly like this)
Flash the 1.13 RUU to get a bootable system
Optionally, Revolutionary to get Revolutionary S-OFF
Optionally (CDMA ONLY), if you got S-OFF you may update the radio (the 1.13 RUU downgraded the radio too). I used the 1.06 version, the 1.09 may work as well but IIRC it was a VM leak so I just stuck with what I think is the latest Sprint image.
From here you should be able to install whatever recovery and ROM (As well as any other partition like radio, hboot, etc) that you like. Good luck.
Flashing RUU
Either use the windows exe (requires windows and a phone that boots correctly), or:
get to your fastboot/bootloader (vol down + power or "adb reboot bootloader")
fastboot oem rebootRUU
fastboot flash zip RUUFile.zip
fastboot reboot (back to bootloader if you want to).
OR
Put the zip on the root directory of the sdcard
Make sure it's named PG86IMG.zip (CaSe sEnSiTiVe)
reboot to a locked/relocked bootloader and apply the zip
Lots of credit to all the devs that made the tools, without whom I'd have been stuck on boring, outdated stock roms.
These steps collected from various xda posts and pieced together for my particular situation, including but not limited to:
http://forum.xda-developers.com/showthread.php?t=1563342
http://forum.xda-developers.com/showthread.php?t=1547695
http://forum.xda-developers.com/showthread.php?t=1889438
http://forum.xda-developers.com/showthread.php?t=1193101
http://forum.xda-developers.com/showthread.php?t=2074181
http://forum.xda-developers.com/showthread.php?t=1447839
http://forum.xda-developers.com/showthread.php?t=1627917
http://forum.xda-developers.com/showthread.php?t=1653777
These guides should provide more background on why/how to do certain steps, as long as being better formatted and complete.
Thanks and Thanks
btharper said:
The 1.58 bootloader apparently changes some formats in an incompatible way (I'm sure purely by chance and not to mess with custom roms).
Click to expand...
Click to collapse
Thank you SO MUCH for your time and effort! After four or five weeks of making my phone worse, I was planning on giving up at the end of this week. I will thoroughly read and then try your suggestions in the morning and update you as to what happens. I hope flashing the RUU as you have suggested works because at this point I cannot flash a recovery.
This is very much appreciated!
-a
hanger-on said:
Thank you SO MUCH for your time and effort! After four or five weeks of making my phone worse, I was planning on giving up at the end of this week. I will thoroughly read and then try your suggestions in the morning and update you as to what happens. I hope flashing the RUU as you have suggested works because at this point I cannot flash a recovery.
This is very much appreciated!
-a
Click to expand...
Click to collapse
No problem, having had the same thing happen I know the frustration, and while there are several, slightly different S-OFF guides, there are fewer guides for what to do when **** hits the fan. As long as your hboot works you can still flash signed RUU.zip files as above, and even the emmc recovery if it's bricked, a little more care is required once you get S-OFF though.
310 26345564
btharper said:
No problem, having had the same thing happen I know the frustration, and while there are several, slightly different S-OFF guides, there are fewer guides for what to do when **** hits the fan. As long as your hboot works you can still flash signed RUU.zip files as above, and even the emmc recovery if it's bricked, a little more care is required once you get S-OFF though.
Click to expand...
Click to collapse
last time i worked on the phone bootloader was working but not the recovery. now that the phone has been off for several days, spent the last day on the charger in anticipation of working on it this morning, and now it won't boot into bootloader [vol down + pwr]. the trouble began weeks ago after flashing a CWM recovery. everything i've done since then to recover the phone has made it worse.
i'm going to leave it charging for several more hours and come back to it later. if it won't boot into bootloader, is it bricked?
CURRENT STATUS: red charge light stays on indefinitely after unplugging; light goes out if battery removed; same reactions if charging via USB on computer or from AC adapter; charge light reanimates when plugged back in; will not boot; will not boot into bootloader; will not respond to ADB [device not found].
hanger-on said:
last time i worked on the phone bootloader was working but not the recovery. now that the phone has been off for several days, spent the last day on the charger in anticipation of working on it this morning, and now it won't boot into bootloader [vol down + pwr]. the trouble began weeks ago after flashing a CWM recovery. everything i've done since then to recover the phone has made it worse.
i'm going to leave it charging for several more hours and come back to it later. if it won't boot into bootloader, is it bricked?
CURRENT STATUS: red charge light stays on indefinitely after unplugging; light goes out if battery removed; same reactions if charging via USB on computer or from AC adapter; charge light reanimates when plugged back in; will not boot; will not boot into bootloader; will not respond to ADB [device not found].
Click to expand...
Click to collapse
What were the last few steps you had done? The only time my hboot didn't come on was when I had my case on slightly off and the buttons didn't hold down correctly (try reseating your case as a last resort and make sure you can feel the buttons being pressed), at one point during the process you have to intentionally brick your phone as noted to corrupt the hboot, as long as you're S-ON it's okay and there are plenty of warnings that you must be S-ON, and one point right after recovering from that step where it's noted that you have to give it some time (I eventually just went to bed for the night because it wasn't working and I wasn't lucid enough to get it anywhere else). So probably just try pulling/replacing the battery and booting up hboot again and hopefully it works. If the red charging light is solid and dimly illuminated when plugged in then the hboot is corrupt and you can proceed to that part of the guide anyway http://forum.xda-developers.com/showthread.php?t=1547695
As well, adb only works when booted to recovery or once the normal system is booted, fastboot only works during hboot or right after rebootRUU (which is actually a part of the hboot, at least on the shooter), and emmc_recovery (used during hboot downgrade)/ultimate recovery tool should work and be able to unbrick the phone. Failing that are you on windows or linux? (revolutionary and some of the hboot downgrade steps require or work best on linux, there's a livedisc (bootable CD/USB stick that won't reset anything on your computer) you can use for the process made by closeone for the hboot downgrade process but you can use for the full process I would think (I did the whole thing on linux since that's my OS of choice) http://forum.xda-developers.com/showthread.php?t=1563342
They replaced my phone. :laugh: At the risk of sounding like a lunatic, I still would like this phone's hboot downgraded with s-off. What I ultimately want is Android 4.1 so I can use the Themer app, or at least some ROM that is similarly simplistic. Speedy and Simple, isn't that what everybody wants? haha! HTC Sense is a fugly abomination as I'm sure many would agree, and the bloatware is simply maddening!
CURRENT STATUS: mainver 2.95.651.6 710RD | Android 4.0.3 | Factory Locked | hboot 1.58.0000 | s-on | no recovery | stock rom
brand new, basically
Would you suggest I begin with this tutorial by UnknownForce along with this toolkit by CloseOne? I collected hundreds of links and plenty of downloads for the previous phone and became lost in the woods with that.
hanger-on said:
They replaced my phone. :laugh: At the risk of sounding like a lunatic, I still would like this phone's hboot downgraded with s-off. What I ultimately want is Android 4.1 so I can use the Themer app, or at least some ROM that is similarly simplistic. Speedy and Simple, isn't that what everybody wants? haha! HTC Sense is a fugly abomination as I'm sure many would agree, and the bloatware is simply maddening!
CURRENT STATUS: mainver 2.95.651.6 710RD | Android 4.0.3 | Factory Locked | hboot 1.58.0000 | s-on | no recovery | stock rom
brand new, basically
Would you suggest I begin with this tutorial by UnknownForce along with this toolkit by CloseOne? I collected hundreds of links and plenty of downloads for the previous phone and became lost in the woods with that.
Click to expand...
Click to collapse
Good luck with it, my advice is lots of nandoid backups and make sure you've got all the tools you need ready. The whole process can be done with linux tools (including the RUU flash). Feel free to let me know if you have any more questions.
Any luck?
Any luck on the new phone?
btharper said:
Any luck on the new phone?
Click to expand...
Click to collapse
I've just been using a themer called Homepack Buzz, Go SMS Pro, and other assorted apps. The embedded Sprint apps are really annoying, and the interface of HTC sense is ugly and inefficient, but I'm switching to Verizon in a couple of months and getting a galaxy 4 anyway, so I'll just wait and toy with it instead.
I realized that this HTC is not worth my time and effort, as it's main function is portable music player. Thanks for checking back in
I'm not sure if Sprint is going to let me keep the phone, but if they do I'll probably post it on Ebay, as it is brand new.
hanger-on said:
I've just been using a themer called Homepack Buzz, Go SMS Pro, and other assorted apps. The embedded Sprint apps are really annoying, and the interface of HTC sense is ugly and inefficient, but I'm switching to Verizon in a couple of months and getting a galaxy 4 anyway, so I'll just wait and toy with it instead.
I realized that this HTC is not worth my time and effort, as it's main function is portable music player. Thanks for checking back in
I'm not sure if Sprint is going to let me keep the phone, but if they do I'll probably post it on Ebay, as it is brand new.
Click to expand...
Click to collapse
If you pay all the fees/fines you can keep the phone. If not the esn will be marked as bad and it wont work on sprint.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Oh. Thanks for the heads up.