As the title says, here's the Rom.zip extracted from RUU_Hero_C_Sprint_2.31.651.7_signed_release.exe for those that don't use Windows, or prefer to have their RUU in zip format.
This will flash your phone to 2.31.651.7 STOCK.
http://www.mediafire.com/?m6x4sr682ruk027
Simply rename this to HERCIMG.zip and place on the root of your SDCard.
Power your phone completely off.
Press and Hold VOL DOWN and POWER until your phone boots into HBoot mode.
Wait for it to verify the zip, then click <ACTION> (Trackball) to update, or <SEND> (Green Call) to cancel.
Enjoy!
Here's my guide to rooting .7:
http://forum.xda-developers.com/showthread.php?t=804296
Personally..I want to say THANK YOU, THANK YOU, THANK YOU.
I have spent the last four hours searching for this. This needs to be stickied. I'm bookmarking it for sure. This got my phone unbricked..I thought all hope was lost and I would have to call in for warranty support (I got mine refurbed through Sprint last October..so I don't even know if I would still have any warranty support), and see if I could try my luck and getting it replaced, since that is what others have said to do as apparently this file from OP, did not exist.
And so for future reference, so that others don't go mindlessly searching through the forums.
If you
a.) Managed to overwrite your Recovery some how or completely delete it. (I did..and from searching this and many other forums over the past couple hours..I can see I wasn't the only one), and also have no boot (or a corrupted boot loop)
b.) Still have S-ON (You can find this out by powering off your phone and then pressing and holding the power button and the lower volume button), I recommend you turn S-Off for future reference if you're going to be dealing with customer ROMs a lot (so you don't have to go through the hell I just did..). See here..
http://forum.xda-developers.com/showthread.php?t=759955
c.) Have an updated Hboot (1.47) (you can also find this info. in part b.)
....then you KNOW that you are stuck. Because you
a.) Cannot flash a ROM in Recovery because you cannot access it.
b.) You cannot access ADB because your phone won't go that far and will only go into fastboot..
c.) But even though you have access to fastboot you can't do ANYTHING like flash a recovery image or a ROM..or anything for that matter..because S is still ON. (this is the "not allow" messages you will see pop up.)
d.) You have bootloader 1.47 so if you for example, were like me couldn't use this file here.. (http://forum.xda-developers.com/showthread.php?t=657086), because it would say there was a newer version and wouldn't install it.
So this file right here..was the only thing getting my phone back to a usable state. And considering that my searches have shown to pretty much give up all hope and have it sent it for warranty repair, then I think this thread deserves a bump for all those that have screwed up.
Yeah..I have to start ALL OVER now from a stock ROM (thank god for nandroid), but at least my phone isn't a dead brick.
Just thought this needed a well deserved bump.
I wonder if there is a RUU for the latest .2?
Wanted to say BIG THANKS. This worked like a charm to update prl/profile. Keeping two copies of this one on the sd and on the laptop. Thanks again.
Yea it's me Again. With the
Modified .HERO.
laie1472 said:
Wanted to say BIG THANKS. This worked like a charm to update prl/profile. Keeping two copies of this one on the sd and on the laptop. Thanks again.
Yea it's me Again. With the
Modified .HERO.
Click to expand...
Click to collapse
Forgive me for seeming NOOBish... but I can use this to do the same, then restore Nandroid back and it will keep the PRL/Profile update?
Just wondering... lolz, thanks!
Yup But you will have to reroot. This takes root from you. You will have to reroot with the Hero rooter from Reg or Z4 or one click root. But read read read. And as far as the prl/profile yup it will stick. When your phone boots up after running this just go into settings and updates and choose update profile and update prl don't update firmware. I repeat don't update firmware. After that just reboot and check your prl should be 60675. After that reroot, then flash a recovery and then nand restore. Hope this helps good luck
Remember this returns you to stock you will loose root and recovery..
Yea it's me Again. With the
Modified .HERO.
Why don't you guys just flash NFX's or LS's already rooted and way faster stock sense ROM to update PRL, etc?
Running stock ROM has to be one of the worst things ever after being on custom ROMs for so long.
I tried flashing almost ever sense rom on here pmgrands port, ninfintes stock odex and deodex and his apps 2 sd builds he has like 4 or 6 different builds. Tried flashing liquids builds beta and stable. All gave me a error. So I had to use this. I couldn't flash any sense rom
and it was easier to use this than try to figure out y. If he can flash a sense rom then yea that's the easier way but if not this is a for sure way to get back to stock.
Yea it's me Again. With the
Modified .HERO.
laie1472 said:
I tried flashing almost ever sense rom on here pmgrands port, ninfintes stock odex and deodex and his apps 2 sd builds he has like 4 or 6 different builds. Tried flashing liquids builds beta and stable. All gave me a error. So I had to use this. I couldn't flash any sense rom
and it was easier to use this than try to figure out y. If he can flash a sense rom then yea that's the easier way but if not this is a for sure way to get back to stock.
Yea it's me Again. With the
Modified .HERO.
Click to expand...
Click to collapse
I still have my original nandroid from before I flashed any ROMs and it takes me back to stock Sprint, where I do my updating. Is this faster than that?
jckeyser said:
I still have my original nandroid from before I flashed any ROMs and it takes me back to stock Sprint, where I do my updating. Is this faster than that?
Click to expand...
Click to collapse
Yup. That's way better and faster. Just go into settings / updates. Then just update prl and profile. Don't update firmware. After you confirm that your updated just nand restore and you should be good.
Edit not sure if you would have to reroot.
Yea it's me Again. With the
Modified .HERO.
Thanks for the reply's all... I like Sense and have NFX rom on my Hero, loaded a few ROMS but they won't update, so no worries, when I have some free time I'll sit and do it then. I don't like the one click rooters nor the clockwork recovery, I guess I'm old school and do it the hard way, lol, but thanks for letting me know it'll work (prl update) and stay on the handset!
Regards!
Without opening a huge can of worms I would like to know whats the best newest rom out there with sense I just searched for like 3 hours and lot of threads are old and I want what ever is new with sense also would like to upgrade to 2.2 im on Honeybun v.-2 lite firmware 2.1 update1
Gelladuga69 said:
Why don't you guys just flash NFX's or LS's already rooted and way faster stock sense ROM to update PRL, etc?
Running stock ROM has to be one of the worst things ever after being on custom ROMs for so long.
Click to expand...
Click to collapse
you got a link ? Im searching now
laie1472 said:
Yup. That's way better and faster. Just go into settings / updates. Then just update prl and profile. Don't update firmware. After you confirm that your updated just nand restore and you should be good.
Edit not sure if you would have to reroot.
Yea it's me Again. With the
Modified .HERO.
Click to expand...
Click to collapse
No need to reroot because it was a nandroid. Can't make a nandroid if you're not rooted.
Sent from my HTC Hero CDMA running Android 2.3
Does anybody have the original MD5 checksum for this file? I wanna make sure this file downloaded properly. Thanks in advance!
EDIT: efa439da700b5fad7ea49915ef7d2866
Sent from my HTC Hero CDMA running Android 2.3
does this work with any version of HBOOT? The phone I am dealing with has stock 1.5
mrtimo said:
does this work with any version of HBOOT? The phone I am dealing with has stock 1.5
Click to expand...
Click to collapse
What? Is your phone even rooted? Sprint upgraded to 2.1 a LONG time ago, the update is available at www.htc.com
It worked for me a while ago, but my dad just got a new hero so I tried using this, and it wouldn't recognize the image file.. any thoughts?
systemshock869 said:
It worked for me a while ago, but my dad just got a new hero so I tried using this, and it wouldn't recognize the image file.. any thoughts?
Click to expand...
Click to collapse
yeah, this only works if he has an S-off bootloader, which he doesn't have if it's a new hero.
il Duce said:
yeah, this only works if he has an S-off bootloader, which he doesn't have if it's a new hero.
Click to expand...
Click to collapse
According to the OP this one was extracted from the RUU, so it *should* work S-ON.
Related
Hello
THIS THREAD IS OBSOLETE. PLEASE CLOSE.
YOU SHOULD BE ABLE TO ROOT DIRECTLY FROM 1.32.651.6 WITHOUT DOWNGRADING.
EDIT:
This is only confirmed to work with 1.32.651.6.
Refer to toast's reply below to understand why it might not work with other versions.
STEPS IF YOU WANT TO DOWNGRADE FROM STOCK .6 to STOCK .1 (NO ROOT)
1. I installed the latest RUU 1.32.651.6 found in this thread:
http://forum.xda-developers.com/showthread.php?t=695604
2. And I was able to downgrade back to the original one found here:
http://forum.xda-developers.com/showthread.php?t=685835
IF YOU WANT TO ROOT YOUR STOCK .6, JUST DO THE FOLLOWING:
3. Then did toast's root tutorial and got to the recovery and everything:
http://forum.xda-developers.com/showthread.php?t=690762
4. And am back to the rooted 1.32.651.1 with the ability to get to recovery and flash roms:
http://forum.xda-developers.com/showthread.php?t=693980
On step 2, the RUU was not able to reboot my device into the bootloader. So I booted into the bootloader myself (hold vol down + power on) then plug in the usb, select fastboot and then start the RUU from the PC. It installed like a champ and brought me back to 1.32.651.1.
Hope this helps everyone who decided to upgrade.
perfect!!! thanks for doing all this, testing and documenting your process. i was concerned with being limited between which versions, root process, recovery versions, etc.
this is great to know and should remove any doubts/concerns anybody has about jumping into the fray of flashing/experimenting/developing!
Yeah I had the ota RUU 1.32.651.6 installed, then found a method close to toasts method, rooted, flashes flipz stock rom, flash radio update, back to 1.32.651.1 with the radio update, still rooted!!! I even tried the froyo rom and thought it was cool, but waiting on more functionality version, so flashed back to stock rom, still rooted! Even thing works great (no 4g in my area so dont know about that.)
It's not that the current ruus won't allow u to downgrade. It's that every time u flash a newer ruu, u are gambling with root. Go look at the Eris and hero forums and u will see. I'm not gonna promote the flashing of ruus because I know what can happen. I have a eng ruu that is older and it can not be flashed because the mainversion is lower then the current mainversion. My goal is to inform everyone of the risks involve in flashing the newer ruus. The fact of not being able to downgrade isn't something I made up. U are just lucky that the newest ruus don't set the mainversion past the bootloader limit for downgrading.
Re: [howto] downgrade from OTA 1.32.651.6
I remember we were told excessives flashes can cause problems but with my htc diamond for the past year i was ruu updating weekly using different roms with their latest releases on my diamond is still going strong.. i like to say its user specific but i could be wrong
-------------------------------------
Sent via the XDA Tapatalk App
toastcfh said:
U are just lucky that the newest ruus don't set the mainversion past the bootloader limit for downgrading.
Click to expand...
Click to collapse
appreciate your feedback, knowledge and experience toast.
seems like the most accurate way to state this is flashing a newer RUU puts the EVO at risk of not being able to downgrade (or use root, wifi tether, custom ROMs, etc)
hopefully we will be able to detect when this change takes place, by md5sum on hboot.img and compare to previous versions. it didnt seem to change between .1 and .6 . hopefully it wont change in the future! once the md5sum changes, i'd say the risk of not being able to downgrade increases significantly!
although, ive only had an HTC phone with android for 3 days now, i could def be wrong in my analysis ...
I mean it could be the .1 and .6 doesn't matter. But idk
joeykrim said:
appreciate your feedback, knowledge and experience toast.
seems like the most accurate way to state this is flashing a newer RUU puts the EVO at risk of not being able to downgrade (or use root, wifi tether, custom ROMs, etc)
hopefully we will be able to detect when this change takes place, by md5sum on hboot.img and compare to previous versions. it didnt seem to change between .1 and .6 . hopefully it wont change in the future! once the md5sum changes, i'd say the risk of not being able to downgrade increases significantly!
although, ive only had an HTC phone with android for 3 days now, i could def be wrong in my analysis ...
Click to expand...
Click to collapse
I flashed the .6 through running ruu .exe,I havn't root my phone yet,can I run the unrevoke.apk to root then install wifi tether pre14 ?will this work?thanks.
So, semi-floating off topic. It turns out that ultimately the unrevoked root doesn't really do much, and apparently isn't enough for custom roms... if I was going to want to flash something custom, would I need to FIRST follow this guide to downgrade, THEN perform toasts root?
tl;dr - does toasts root work on .6?
2kmy477 said:
I flashed the .6 through running ruu .exe,I havn't root my phone yet,can I run the unrevoke.apk to root then install wifi tether pre14 ?will this work?thanks.
Click to expand...
Click to collapse
yes, it work for me.
tkhan02 said:
yes, it work for me.
Click to expand...
Click to collapse
Thank you.Will try when I get hone from work tonite.
Re: [howto] downgrade from OTA 1.32.651.6
FuManChuu said:
So, semi-floating off topic. It turns out that ultimately the unrevoked root doesn't really do much, and apparently isn't enough for custom roms... if I was going to want to flash something custom, would I need to FIRST follow this guide to downgrade, THEN perform toasts root?
tl;dr - does toasts root work on .6?
Click to expand...
Click to collapse
Yeah - if you are on .6, just do steps 2 and 3 then flash whatever rom u want using toast's recovery
Sent from my PC36100 using Tapatalk
I installed Sprint's official .6 by mistake, but was able to do steps 1 and 2 of your guide. I can see I'm in version .1 in my phone settings. However, when trying to follow toast's instructions from your step 3, I can't even do "adb push". When I do "adb devices", it doesn't see the phone. So I manually copied the PC36IMG.zip to the SD by mounting the USB and went into Fastboot. It did see the ZIP file and scanned (blue progress bar on the right). It actually looked like it scanned it twice, but, at the end, I didn't get an option to flash it. It just went back to the original 4-option fastboot menu. What am I doing wrong?
Re: [howto] downgrade from OTA 1.32.651.6
Sounds like it fails when it checks the rom. Make sure htc sync is installed on your pc then boot the phone, connect it and instead of charge only, select htc sync. Then, do the adb push stuff and try again.
And dont go to fastboot this time, just boot and wait and it should ask you whether to flash or not
Sent from my PC36100 using Tapatalk
Ok so I haven't rooted yet, but installed the OTA .6 update...can I still back up and get my root abilities back?
Can I ?
I have a stock Sprint Evo no root no nothing. Ive notice horrible battery life with .6 OTA.. Can I do step 2 without being rooted? I just want the original sprint before OTA.. Sorry for the ignorant question
xavier1022 said:
I have a stock Sprint Evo no root no nothing. Ive notice horrible battery life with .6 OTA.. Can I do step 2 without being rooted? I just want the original sprint before OTA.. Sorry for the ignorant question
Click to expand...
Click to collapse
Yes you can -- the 4 steps are independent of each other.
I am having issues with applying the RUUs, when I connect it via USB, do I choose USB or Charge only? Sorry.
engagedtosmile said:
I am having issues with applying the RUUs, when I connect it via USB, do I choose USB or Charge only? Sorry.
Click to expand...
Click to collapse
Choose HTC Sync
Re: [howto] downgrade from OTA 1.32.651.6
I have a stock Sprint Evo no root no nothing. Ive notice horrible battery life with .6 OTA.. Can I do step 2 without being rooted? I just want the ori
Click to expand...
Click to collapse
Yes you can -- the 4 steps are independent of each other.
Click to expand...
Click to collapse
Thanks will give it a go.. I was a windows mobile flash aholic...still scared to jump to flashing on android..
-------------------------------------
Sent via the XDA Tapatalk App
Sorry guys if this was posted already. I had been searching for a way to unroot totally back to factory and the RUUs were giving me all sorts of errors... 171, 170 etc. So I finally found a way to actually make it work.
** If you are rooted and have the 1.47 update and cannot unroot with the RUU you were in my boat. Here's what I did:
1 - Download the ROOTED 1.32.651.1 from http ://geekfor.me/evo/rom/Supersonic_1.32.651.1_rooted .zip
(Remove the spaces from the url)
2 - Put that zip in the root of your SD card and then boot into recovery and flash it.
3 - Download the official 1.47 RUU and it should work on your device with no problems.
I am sorry if this guide was elsewhere but this is what I came up with on my own and I wanted to share it in case there wasn't a working unroot guide out.
bman789 said:
Sorry guys if this was posted already. I had been searching for a way to unroot totally back to factory and the RUUs were giving me all sorts of errors... 171, 170 etc. So I finally found a way to actually make it work.
** If you are rooted and have the 1.47 update and cannot unroot with the RUU you were in my boat. Here's what I did:
1 - Download the ROOTED 1.32.651.1 from http ://geekfor.me/evo/rom/Supersonic_1.32.651.1_rooted .zip
(Remove the spaces from the url)
2 - Put that zip in the root of your SD card and then boot into recovery and flash it.
3 - Download the official 1.47 RUU and it should work on your device with no problems.
I am sorry if this guide was elsewhere but this is what I came up with on my own and I wanted to share it in case there wasn't a working unroot guide out.
Click to expand...
Click to collapse
Has the 1.47 RUU been released?
kpoz said:
Has the 1.47 RUU been released?
Click to expand...
Click to collapse
Yes. http://www.shipped-roms.com/shipped/Supersonic/
the ruu does not restore the PRI to 1.40 if you have the engineering boot.
From what I can tell, there is no way to restore back to 1.40 pri.
Can someone post the stock 1.47.651.1 in a zipped image format for the bootloader??
My USB port broke, so Im trying to return to unrooted stock to send my phone back to sprint, but since the USB port is broken i can only do it through the SD card..
Thanks,
TurboX2 said:
Can someone post the stock 1.47.651.1 in a zipped image format for the bootloader??
My USB port broke, so Im trying to return to unrooted stock to send my phone back to sprint, but since the USB port is broken i can only do it through the SD card..
Thanks,
Click to expand...
Click to collapse
There are adapters and you can also put the card in another phone.
I will look for the image
Download to root of sd and rename to PC36IMG
http://www.mattwhitlock.com/PC36IMG-1.47.651.1_eng-hboot_RA-1.7.0.1.zip
They do not check for root and to be honest its perfectly LEGAL now to root a phone so no WORRYS leave it as is
thanks again for the really quick response.. I have a mircoUSB adaptor that i use, and my roomate has the same phone as me so i can get my battery charged.
i may just do as you say and go with the sprint stock rooted rom.. kuz this is proving to be more of a hassle than i thought it would be.
thanks
It's still void the warranty even tho its legal so save yourself a potential hassle and unroot
Sent from my PC36100 using XDA App
spencelk said:
It's still void the warranty even tho its legal so save yourself a potential hassle and unroot
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
In the MOST EXTREME case but its highly doubtful and has been proven over and over. I for one agree you should unroot it as best you can so it doesnt allow the carrier or htc to figure out the root method etc but if you can't I wouldnt worry one single bit. Good luck let me know if I can be of anymore help
hmm.. okay.. so that zip file that was there.. i already had, and i already tried flashing that.. and it didnt work last time, nor did it work this time
i have hboot 0.79.000
i have radio 1.39.00.05.31
and i flashed to a rooted 1.32 rom like it said i had to do.
Im using clockworkmod recovery 2.5.0.1
When i go to install zip from sd card>choose zip> and select the file attached, it just tries to open it and within a few miliseconds its back to the screen i was just at.
if i were to rename it to PC36IMG.zip and let bootloader load it, it will say 'wrong or no image'
I think im going to give up..
i found this. i will give it a try i suppose:
http://forum.xda-developers.com/showthread.php?t=701835
EDIT: NVM i forgot my USB doesnt work. lol.. oh well.. i dont think sprint will do anything.. its a sprint rom anyways.. Ive replaced hard-spl'd winmo phones throu att before
arrrg.. windows mobile made more sense to me.
TurboX2 said:
hmm.. okay.. so that zip file that was there.. i already had, and i already tried flashing that.. and it didnt work last time, nor did it work this time
i have hboot 0.79.000
i have radio 1.39.00.05.31
and i flashed to a rooted 1.32 rom like it said i had to do.
Im using clockworkmod recovery 2.5.0.1
When i go to install zip from sd card>choose zip> and select the file attached, it just tries to open it and within a few miliseconds its back to the screen i was just at.
if i were to rename it to PC36IMG.zip and let bootloader load it, it will say 'wrong or no image'
I think im going to give up..
i found this. i will give it a try i suppose:
http://forum.xda-developers.com/showthread.php?t=701835
EDIT: NVM i forgot my USB doesnt work. lol.. oh well.. i dont think sprint will do anything.. its a sprint rom anyways.. Ive replaced hard-spl'd winmo phones throu att before
arrrg.. windows mobile made more sense to me.
Click to expand...
Click to collapse
You arent nand unlocked just bring it back do a full system wipe
It also doesnt hurt to try again make sure that you download a fresh version of the file and wipe the sd card of any other files if possible if at least make sure there arent any other pcimg files there
rjmjr69 said:
In the MOST EXTREME case but its highly doubtful and has been proven over and over. I for one agree you should unroot it as best you can so it doesnt allow the carrier or htc to figure out the root method etc but if you can't I wouldnt worry one single bit. Good luck let me know if I can be of anymore help
Click to expand...
Click to collapse
Cause HTC's employee's are incapable of finding public forums such as this.
topdnbass said:
Cause HTC's employee's are incapable of finding public forums such as this.
Click to expand...
Click to collapse
And that means what? I dont understand?. we all know they are here some even post from time to time
rjmjr69 said:
You arent nand unlocked just bring it back do a full system wipe
It also doesnt hurt to try again make sure that you download a fresh version of the file and wipe the sd card of any other files if possible if at least make sure there arent any other pcimg files there
Click to expand...
Click to collapse
No files found in the under the nandroid option..
nothing is really flashing except for custom rooted roms
rjmjr69 said:
And that means what? I dont understand?. we all know they are here some even post from time to time
Click to expand...
Click to collapse
The person he was quoting was implying that we should unroot so that Sprint / HTC don't figure out how we were able to root.
devin.slick said:
The person he was quoting was implying that we should unroot so that Sprint / HTC don't figure out how we were able to root.
Click to expand...
Click to collapse
OIC ok thank you
rjmjr69 said:
In the MOST EXTREME case but its highly doubtful and has been proven over and over. I for one agree you should unroot it as best you can so it doesnt allow the carrier or htc to figure out the root method etc but if you can't I wouldnt worry one single bit. Good luck let me know if I can be of anymore help
Click to expand...
Click to collapse
Umm.. to find out the root method can't 'the carrier or htc' just use google and these forums?
I snaged the update file before it updated my phone. If anyone wants the file let me know I will post the file on a server for people to snag.
File that came accross over wifi update.
OTA_Bravo_Froyo_TELUS_WWE_2.25.661.2-1.29.661.1_R_release_Pf7sjzjrgcmpsve12.zip
I'd like to keep a copy just in case I need to return my phone. What radio version does it install?
This is pretty useless, as you have to run stock for it to work, it's not a RUU.
Here is the link to the update: http://fotadl.htc.com/OTA_Bravo_Fro....2-1.29.661.1_R_release_Pf7sjzjrgcmpsve12.zip
ajanu said:
I'd like to keep a copy just in case I need to return my phone. What radio version does it install?
Click to expand...
Click to collapse
Agreed. Please post a copy.
damn, just checked the HTC site and there is no RUU posted. thats bad news...they posted it for the Hero last week though...? wonder why they decided not to post it for the desire.
peytral said:
This is pretty useless, as you have to run stock for it to work, it's not a RUU.
Click to expand...
Click to collapse
The only thing useful in there is the radio. I'm running it
I did the OTA update this morning on a different Desire (from rooted 2.1) and the file it downloaded has a different ending number, I wonder if it matters, I saved the file to my laptop. The "Pf7sjzjrgcmpsve12" is what of concern, would that work on any other Desires?
Nevermind, I think they're the same number.
i would like if there was a RUU for this. Is there a way to make an RUU out of the files it has so i can do a clean install and wipe my desire? by the way how did you find that link off the htc website for the update?
Since I have a backup of 2.1 just after I rooted, I should be able to install that then use this zip correct? What radio version is included?
Here is a link to the RUU named properly that I used to fix a non-bootable phone.
PB99IMG.zip
marinierb said:
The only thing useful in there is the radio. I'm running it
Click to expand...
Click to collapse
Does the new radio provide much better signal?
Im running the stock 2.2 that was available for the A8181 a few months back. My phone isnt rooted and i used to gold card method to get it installed.
Is there a way for me to get this new radio?
Thanks for the file.. its nice to be able to revert to stock without having to run the RUU. I appreciate the work you did making this!
peytral said:
This is pretty useless, as you have to run stock for it to work, it's not a RUU.
Here is the link to the update
Guys on Leedroid right now. But really want to go back to my Telus froyo as 3g tethering is acting up. I tried installing this in the boot menu but I cannot what am I doing wrong? Please help?
Click to expand...
Click to collapse
So I can't figure out how to fix this, and have a completely useless phone at the moment, unfortunately.
I wanted to install Virtuous Inquisition. I was coming from ARHD 4.1.10 Gingerbread. This is the process I followed:
1. Downloaded Firmware and ROM from website.
2. Loaded both onto SDCard
3. Rebooted into recovery, PG58IMG did it's work.
4. Formatted / Wiped all Data
5. Installed Virtuous Inquisition
At this point I was thrown into a continuous boot loop. Read up on the forums, apparently Virtuous is only tested for CWM.
Tried installing CWM - downloaded the zip, renamed it PG58IMG.zip, tossed it onto the phone, gets stuck at "Parsing," and fails.
Tried reinstalling firmware again - Creates error "Wrong CID"
Tried installing CWM from the 1st post of the Sensation Rooting Thread, said "Wrong Version."
Completely confused as to how to fix my phone now.
Please, PLEASE help.
Thanks XDA.
Delete all pg58img.zip from SD card, try to reboot and post result.
Leaving the firmware zip in SD root after update causes boot loops.
Sent from my Pyramid-T
Unfortunately I still get the boot loops -
I get the Virtuous Boot Animation, then it just kills itself.
OK does fastboot work?
Sent from my Pyramid-T
gotpriest said:
Unfortunately I still get the boot loops -
I get the Virtuous Boot Animation, then it just kills itself.
Click to expand...
Click to collapse
Try the virtuous 2.23 thread. It's a 2.3.4 Rom but it comes with its own firmware. See if that boots up before trying anything else.
stringer7 said:
OK does fastboot work?
Sent from my Pyramid-T
Click to expand...
Click to collapse
Unfortunately I'm rather unfamiliar with this term - if you mean can I get into the bootloader, yes, and I can get into 4EXT.
I vaguely remember when rooting my phone that I had to connect it to the computer to do some adb things, but have not tried / done that since.
Currently I have a spare SDCard, and am trying the entire process over real quick, then going to try TC's idea.
Update: Loading the Firmware again still gave me the "CID Incorrect!" error in the bootloader.
Update 2:
tropical cactus said:
Try the virtuous 2.23 thread. It's a 2.3.4 Rom but it comes with its own firmware. See if that boots up before trying anything else.
Click to expand...
Click to collapse
Going to that thread points you to the Virtuous Site - 2.2.0 Rom is Listed, but the Firmware is not bundled. Trying it anyway right now.
gotpriest said:
Unfortunately I'm rather unfamiliar with this term - if you mean can I get into the bootloader, yes, and I can get into 4EXT.
I vaguely remember when rooting my phone that I had to connect it to the computer to do some adb things, but have not tried / done that since.
Currently I have a spare SDCard, and am trying the entire process over real quick, then going to try TC's idea.
Update: Loading the Firmware again still gave me the "CID Incorrect!" error in the bootloader.
Click to expand...
Click to collapse
If you can get into recovery, then all's not lost.
Edit: sounds like you haven't super cided.
gotpriest said:
1. Downloaded Firmware and ROM from website.
2. Loaded both onto SDCard
3. Rebooted into recovery, PG58IMG did it's work.
4. Formatted / Wiped all Data
5. Installed Virtuous Inquisition
Tried reinstalling firmware again - Creates error "Wrong CID"
Click to expand...
Click to collapse
First and foremost, did you do a nandroid backup before you did any of this? If so just revert back.
Next, in step 3, you said you booted into recovery to flash the PG58IMG. You plain can't do that. All firmware updates are done through the bootloader not recovery.
And you also mentioned, wrong CID. Do you recall ever doing a superCID on your phone? If not, read through http://forum.xda-developers.com/showthread.php?t=1459767 to get the correct firmware. IF you go there for the firmware (I suggest 3.24), you do not need superCID on your phone.
GL
Sorry, wrong wording, I did originally do the PG58IMG through Bootloader.
Quite, *quite* stupidly, I only did a Titanium backup, not a nandroid backup.
I have not done SuperCID on my phone.
Working on multiple options you guys have posted at the moment, y'all type too fast for my SDCard switching speeds!
As a side question at the moment, the Virtuous website mentioned that it has only tested through CWM. I was under the impression that 4EXT, while a different interface, behaved and functioned no differently than CWM. I may be wrong on this, but either way, I cannot get CWM to take control. It won't flash in the bootloader (gets stuck at "Parsing") and installing a Zip of it through 4EXT opens it, but does not make it the primary Recovery method
Update: The T-Mobile specific firmware is successfully installing at the moment. Will remind self to SuperCID ASAP :/
While talking earlier about nandroid backups, I was curious - I thought nandroid only backed up certain things, IE: Not the firmware. Am I incorrect?
Update 2: The Virtuous Boot animation has gotten far enough for the V to begin pulsing. It has never gotten this far. I think it may actually be going through the "initial" boot up sequence. May take a few minutes.
gotpriest said:
Sorry, wrong wording, I did originally do the PG58IMG through Bootloader.
Quite, *quite* stupidly, I only did a Titanium backup, not a nandroid backup.
I have not done SuperCID on my phone.
Working on multiple options you guys have posted at the moment, y'all type too fast for my SDCard switching speeds!
As a side question at the moment, the Virtuous website mentioned that it has only tested through CWM. I was under the impression that 4EXT, while a different interface, behaved and functioned no differently than CWM. I may be wrong on this, but either way, I cannot get CWM to take control. It won't flash in the bootloader (gets stuck at "Parsing") and installing a Zip of it through 4EXT opens it, but does not make it the primary Recovery method
Click to expand...
Click to collapse
I use 4ext for my recovery and works just as well. Just use the firmware in that thread I mentioned. That thread is a great one to read up on. Especially for people who are new to CID terminologies.
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
gotpriest said:
Update: The T-Mobile specific firmware is successfully installing at the moment. Will remind self to SuperCID ASAP :/
While talking earlier about nandroid backups, I was curious - I thought nandroid only backed up certain things, IE: Not the firmware. Am I incorrect?
Click to expand...
Click to collapse
The only thing Nandroids do not back up are radios, SD stuff, kernels,firmware and RIL files. The RIL and Radio's are bundled in the rom itself. So essentially the nandroid backs up the ROM itself. Hope that makes sense.
Hope its working now? My thought was the problem was firmware you flashed originally not supported by your CID = boot loop.
SupwrCID def recommended!
Sent from my Pyramid-T
Jesus Joseph and Mary you guys saved my Bacon. Working Phone. Thanks to all, particularly kpjimmy for the right firmware link!
Lessons Learned:
1. Don't be an Idiot.
2. Murphy is an Asshole
3. Do nandroid backups
4. SuperCID my phone.
5. Stop trying to Flash ROMS on my phone when I haven't slept in 24 hours.
6. Don't be an Idiot.
stringer7 said:
Hope its working now? My thought was the problem was firmware you flashed originally not supported by your CID = boot loop.
SupwrCID def recommended!
Sent from my Pyramid-T
Click to expand...
Click to collapse
Correct, you were on the right track. I have not done SuperCID, so when I installed the Firmware straight from Virtuous, it wasn't T-Mo specific.
gotpriest said:
Update: The T-Mobile specific firmware is successfully installing at the moment. Will remind self to SuperCID ASAP :/
While talking earlier about nandroid backups, I was curious - I thought nandroid only backed up certain things, IE: Not the firmware. Am I incorrect?
Update 2: The Virtuous Boot animation has gotten far enough for the V to begin pulsing. It has never gotten this far. I think it may actually be going through the "initial" boot up sequence. May take a few minutes.
Click to expand...
Click to collapse
Happy for you. We've all been to hell and back before.
tropical cactus said:
Happy for you. We've all been to hell and back before.
Click to expand...
Click to collapse
It actually scared the crap out of me. I switched back and forth between about 5 AOSP ROMS on my MyTouch back in the day, and have done countless ones on my Senny. This was my first firmware update though, so clearly that was the issue - but I should really learn to stop doing these things on weekdays when I urgently need my phone...
Glad it worked. Enjoy VI 3.5. I know I am
gotpriest said:
It actually scared the crap out of me. I switched back and forth between about 5 AOSP ROMS on my MyTouch back in the day, and have done countless ones on my Senny. This was my first firmware update though, so clearly that was the issue - but I should really learn to stop doing these things on weekdays when I urgently need my phone...
Click to expand...
Click to collapse
Been there and done that. Leave the high for the weekend.
So I have used TMOUS rom for ALONG time and recently decided to switch to use Cyanogen being a fan of it form other platforms.
While on the TMOUS rom I had 4g connectivity in my area about 90% of the time with the occasional drop into 3g here and there. It always displayed a 4g image in the top.
When I switched to Cyanogen that pretty much stoped. It always says 3g and is slow as hell. every once in awhile it will say H+ but not for long. MOST of the time it is constantly switching between 3g/4g/edge then shutting off.
Now im not sure if its a rom problem or not, but its making me want to switch back to a TMOUS rom.
Any suggestions would be great!
Edit: Just for clairification, I am S-On
I have this problem as well. I even ran the ruu back to stock and it is still happening. Please and thank you!
cp101 said:
I have this problem as well. I even ran the ruu back to stock and it is still happening. Please and thank you!
Click to expand...
Click to collapse
Damn, this scares me.... any solution anyone?
I'm thinking it might be a hardware error at this point. I might just "lose my phone" or just flash to stock and return it, this is preposterous.
cp101 said:
I'm thinking it might be a hardware error at this point. I might just "lose my phone" or just flash to stock and return it, this is preposterous.
Click to expand...
Click to collapse
Unfortunately, it doesn't seem to be a hardware problem
I have been trolling the net for weeks but have not found a solution yet.
I've posted in threads here but no solution.....
My issues started when I went to CM ROM - I used to have great 4g all the time before I went to custom rom (I was on stock TMO US) .. Now no matter what I do, I am not able to get 4G again.... it's really irritating...
I've tried a bunch of custom ROMS.. I am on 1.13 HBOOT and S-ON .. .. CID = HTC__001 (originally my CID was stock TMO US CID whatever that is but now its not that.. I don't wan to run RUU because I don't have TMO US CID and dont want to brick my phone)
You can set your CID back easily with the All in One ToolKit found here.http://www.hasoon2000.info/getdownload.php?file=One%20S/One_S_All-In-One_Kit_v4.0.rar
That is not the problem, unfortunately. It just doesn't make much sense, whatever the problem is; and especially considering after a full RUU restock. That has always fixed whatever mess I have created in the past.
This rom should fix your problem. Dont forget to clear storage from bootloader. It will erase everything thoug. And follow the steps under show contents link.
http://forum.xda-developers.com/showthread.php?t=2250573
cp101 said:
You can set your CID back easily with the All in One ToolKit found here.http://www.hasoon2000.info/getdownload.php?file=One%20S/One_S_All-In-One_Kit_v4.0.rar
That is not the problem, unfortunately. It just doesn't make much sense, whatever the problem is; and especially considering after a full RUU restock. That has always fixed whatever mess I have created in the past.
Click to expand...
Click to collapse
I not sure if its a CID problem. The only thing I ever did was upgrade to the newest Hboot and load in the CM rom. even going back to the TMOUS rom does not fix the problem.
Its so bad, and never on 4g that im considering getting a new phone.
bnd10706 said:
I not sure if its a CID problem. The only thing I ever did was upgrade to the newest Hboot and load in the CM rom. even going back to the TMOUS rom does not fix the problem.
Its so bad, and never on 4g that im considering getting a new phone.
Click to expand...
Click to collapse
I'm in the same boat, friend. I've tried literally everything suggested, I'm just wondering what exactly happened in the flashing of the Maximus rom. The worst part being is that I GET 3g/H and then it drops back to E. It's so strange. The only thing I've not done is contact Tmobile about it, and i highly doubt that they would throttle my bandwidth without contacting me in some form or fashion.
cp101 said:
I'm in the same boat, friend. I've tried literally everything suggested, I'm just wondering what exactly happened in the flashing of the Maximus rom. The worst part being is that I GET 3g/H and then it drops back to E. It's so strange. The only thing I've not done is contact Tmobile about it, and i highly doubt that they would throttle my bandwidth without contacting me in some form or fashion.
Click to expand...
Click to collapse
my phone is still under warrenty. Im wondering if i am able to revert back to stock without them knowing if I can get a phone replacement.
From what I've read, it's doable; even with an unlocked phone. But I'd really like to know what in the dev's source code made this happen... it's a bit ridiculous.
jenenser83 said:
This rom should fix your problem. Dont forget to clear storage from bootloader. It will erase everything thoug. And follow the steps under show contents link.
http://forum.xda-developers.com/showthread.php?t=2250573
Click to expand...
Click to collapse
I just wanted to say, that I did this and it worked!
I did this the first time, but i just flashed the rom with a full wipe.
This time what I did was go into TWRP and erased everything....and I mean everything except TWRP.
After that i flashed the rom and boot.img and everything works great. 4g all the time again!
Sucks that im back on an older version of jellybean, but oh well
bnd10706 said:
I just wanted to say, that I did this and it worked!
I did this the first time, but i just flashed the rom with a full wipe.
This time what I did was go into TWRP and erased everything....and I mean everything except TWRP.
After that i flashed the rom and boot.img and everything works great. 4g all the time again!
Sucks that im back on an older version of jellybean, but oh well
Click to expand...
Click to collapse
Can you take me through the steps you took to achieve all of this? Thanks.
cp101 said:
Can you take me through the steps you took to achieve all of this? Thanks.
Click to expand...
Click to collapse
So what I did first was go into TWRP and selected wipe. Inside wipe i selected EVERYTHING, every little box. Then Wiped it.
This left nothing on the phone but the recovery. I then loaded on SuperSU from TWRP. I download the stock TMOUS rom that was posted earlier in this post.
In TWRP I mounted it and hooked it to computer and transfered the rom over.
Once the rom was on I did the install of the rom.
I rebooted the rom into bootloader.
Once in bootloader i put it into fastboot.
I had previous extracted the boot.img from the rom.
I sent the boot.img over via fastboot which restarted the phone.
Once it got all started up. No issues. I am on 4g 99% of the time now.
Im thinking the issue was definatly based in the CM rom.
Since this worked I wanted to test things out since my phone was pretty much stripped of everything.
I tried out Viper rom and a couple of other non CM based roms, and I have had no issues.
IM back on teh TMOUS rom though. Wifi calling will win over when i go overseas.
Thanks, but it did not work for me. It is a hardware issue on mine. Thanks again
cp101 said:
Thanks, but it did not work for me. It is a hardware issue on mine. Thanks again
Click to expand...
Click to collapse
Must be.
I did find something out though doing all my research. Did you ever at any point update the radio? TMobile uses some frequencies that some companies dont use.
It is my understanding that some of these roms are packed with radios that are generic and thus ment for multi carriers.
Not sure if thats your issue, but might want to look into.
Its nice being back on 4g though.