As the title suggests I am stock gingerbread (the one pushed then oulled back). I would like to remain this way until cm7 has become official for the thunderbolt or at least until it has a few of the bugs ironed out in the rom so we don't have to flash fixes.
Anyway I am familiar with the method of renaming otacerts.zip to otacerts.zip.bak and I have done that.
I wonder if others have had success blocking ota's with that method?
Is anyone familiar with a better method?
recDNA said:
As the title suggests I am stock gingerbread (the one pushed then oulled back). I would like to remain this way until cm7 has become official for the thunderbolt or at least until it has a few of the bugs ironed out in the rom so we don't have to flash fixes.
Anyway I am familiar with the method of renaming otacerts.zip to otacerts.zip.bak and I have done that.
I wonder if others have had success blocking ota's with that method?
Is anyone familiar with a better method?
Click to expand...
Click to collapse
well, renaming files at least works for boot animations & such, so i don't see why it wouldn't work for that ota file. normally, if it's something i don't want/need, i'll either freeze it or remove it entirely. try 'Anttek App Manager'(it's free).
additionally, i wouldn't wait around on an "official" CM7 for the Thunderbolt as that may never happen. i find at least that the latest 'SHIFTAO5P" roms that dhacker is now working on are the most stable ones and seem to have everything working ok.
recDNA said:
As the title suggests I am stock gingerbread (the one pushed then oulled back). I would like to remain this way until cm7 has become official for the thunderbolt or at least until it has a few of the bugs ironed out in the rom so we don't have to flash fixes.
Anyway I am familiar with the method of renaming otacerts.zip to otacerts.zip.bak and I have done that.
I wonder if others have had success blocking ota's with that method?
Is anyone familiar with a better method?
Click to expand...
Click to collapse
Has anyone actually tried the method I mentioned
Did it work
Now that an ota IS being pushed I guess i'll find out the hard way unless someone can help me out?
I got a OTA request right before I updated from Stock Rooted Gingerbread to the current stock rooted.
Now I'm on the current version same as OTA but rooted, renamed otacert.zip.bak but still had in the software update "deferred update pending".
Not sure how to stop this. Any help appreciated.
Can't u accept the OTA n just reinstall Superuser as long as ur S-Off? Been awhile so I can't remember.
Sent from my ADR6400L using xda premium
I accepted the OTA this evening & now I'm stuck. It shut down to then reboot & I ended up stuck at the triangle ! screen for over an hour.
Removing the battery & turning it on allows me to get it back, but as soon as the system is loaded it powers down again to complete the update...
Rooted via Revolutionary method & I'm stuck until someone with more xp comes along & can point me in the correct direction.
My bad.
Tantalin said:
I accepted the OTA this evening & now I'm stuck. It shut down to then reboot & I ended up stuck at the triangle ! screen for over an hour.
Removing the battery & turning it on allows me to get it back, but as soon as the system is loaded it powers down again to complete the update...
Rooted via Revolutionary method & I'm stuck until someone with more xp comes along & can point me in the correct direction.
My bad.
Click to expand...
Click to collapse
Rev method copies its own version of hboot and does not allow an OTA to copy over its own version. I could be completely wrong since i didnt use Revo to root my phone but you may want to try powering to hboot menu if you can power on you can get there, and try flashing the rooted version after full system wipe.
If I helped you in any way please use the thank you button
Could you just restore a nandroid?
I noticed when I updated manually (with help from mike and grlantern) that the file I had renamed otacerts.zip.bak is now back to otacerts.zip. I don't know if the update process created a new version or what but the date next to the zip folder is August, not October.
Is it possible for you to get to hboot by holding volume down as you push power key, then choose recovery, then restore to a nandroid (assuming you ever backed up your rooted rom).
I'm not sure if recovery will still be available though if the update made you s-on.
I'm no expert so perhaps you may want to wait for grlantern to chime in.
recDNA said:
I noticed when I updated manually (with help from mike and grlantern) that the file I had renamed otacerts.zip.bak is now back to otacerts.zip. I don't know if the update process created a new version or what but the date next to the zip folder is August, not October.
Is it possible for you to get to hboot by holding volume down as you push power key, then choose recovery, then restore to a nandroid (assuming you ever backed up your rooted rom).
I'm not sure if recovery will still be available though if the update made you s-on.
I'm no expert so perhaps you may want to wait for grlantern to chime in.
Click to expand...
Click to collapse
1. Have you ever looked at other files in there or files in windows. They don't update files that don't need updates so some files could be from launch of Thunderbolt if the file did not need an update.
2. Revo protects you from an RUU gaining S-On with its version of Hboot. I think the process of returning to stock by flashing an RUU is just for the ADB method which is what I used. I think Revo has to use a different method to regain stock.
If I helped you in any way please use the thank you button
You realize I was trying to give tanalin an idea of how to get his phone working again right?
I just thought he might be able to get into recovery and restore a nandroid or even wipe everything and install a custom rom? Of course I don't know if he can get into cwm.
recDNA said:
You realize I was trying to give tanalin an idea of how to get his phone working again right?
I just thought he might be able to get into recovery and restore a nandroid or even wipe everything and install a custom rom? Of course I don't know if he can get into cwm.
Click to expand...
Click to collapse
I was answering your file question while telling him why his OTA didn't work cause of the hboot problem
If I helped you in any way please use the thank you button
Grnlantern79 said:
1. Have you ever looked at other files in there or files in windows. They don't update files that don't need updates so some files could be from launch of Thunderbolt if the file did not need an update.
2. Revo protects you from an RUU gaining S-On with its version of Hboot. I think the process of returning to stock by flashing an RUU is just for the ADB method which is what I used. I think Revo has to use a different method to regain stock.
If I helped you in any way please use the thank you button
Click to expand...
Click to collapse
I'm in the same pickle as tantalin. Let me ask some dumb questions:
- I can get to the CWM recovery screen. Are you saying I could do a factory re-set, then restore the ROM pre-update? Would I have to have backed up before the OTA (which I didn't, as I only rooted yesterday...argh).
Thanks for your help.
Keep in mind Im a beginner too so you may want to wait for someone with more experience.
CHECK WITH AN EXPERIENCED USER BEFORE FOLLOWING MY DIRECTIONSDIRECTIONS
Yes, you would have had to have a rom to restore to. You could try wiping data, cache, and dalvik cache but I don't know whether phone would boot.
Another alternative would be to shut off phone, take out flash card, copy a custom rom like bamf forever 1.0.8 or the rooted version of the update on the sdcard. Put sdcard back in phone, turn on phone whole holding volume key down. Go to recovery. Wipe data, wipe cache, wipe dalvik cache (under advanced choices)Choose instal from sdcard. Browse to custom rom you put on sdcard. Choose it and install.
Keep in mind Im a beginner too so you may want to wait for someone with more experience.
TOTALLY INADVERTENT SUCCESS!!
I booted into clockworkmod recovery, deleted the cache partition, then under "advanced", I deleted the dalvik cache. I have literally no idea what either of these two things are, but since a factory reset was my worst case scenario, jimmy cracked corn and I didn't care.
Rebooted recovery (accidentally), then rebooted the phone. An error message saying the update failed! Happy day!
Now I can back the phone up properly, and go forward. So worried I'd lose all my apps and information not backed up to my Exchange server! Phew!!!!
If you have a rooted stock phone, and then you accept an OTA or load an RUU, you WILL lose root and the custom recovery program. But you SHOULD still be S-Off. If you are in that position right now, you need to re-flash the custom recovery to be able reload the SU app to regain root.
If you are actually back in S-on, you need to restart the root process from the beginning.
THEN BACK UP IMMEDIATELY BEFORE YOU DO ANYTHING ELSE....
---------- Post added at 03:57 PM ---------- Previous post was at 03:55 PM ----------
Fastlivin said:
TOTALLY INADVERTENT SUCCESS!!
Click to expand...
Click to collapse
Good job.
Fastlivin said:
TOTALLY INADVERTENT SUCCESS!!
I booted into clockworkmod recovery, deleted the cache partition, then under "advanced", I deleted the dalvik cache. I have literally no idea what either of these two things are, but since a factory reset was my worst case scenario, jimmy cracked corn and I didn't care.
Rebooted recovery (accidentally), then rebooted the phone. An error message saying the update failed! Happy day!
Now I can back the phone up properly, and go forward. So worried I'd lose all my apps and information not backed up to my Exchange server! Phew!!!!
Click to expand...
Click to collapse
Excellent! I know that phew feeling all to well!
Now please, PLEASE READ THIS THREAD (You'll be glad you did!)
http://forums.androidcentral.com/showthread.php?p=829066
Grnlantern79 said:
Rev method copies its own version of hboot and does not allow an OTA to copy over its own version. I could be completely wrong since i didnt use Revo to root my phone but you may want to try powering to hboot menu if you can power on you can get there, and try flashing the rooted version after full system wipe.
If I helped you in any way please use the thank you button
Click to expand...
Click to collapse
I was able to get to HBOOT & I followed the steps in the 3rd post of this thread starting at step 5.
I didn't wipe anything (Wipe data, cache, and dalvik), so I don't know what the short term or long term effects are.
I used TiBup & My Backup Pro to restore my SMS/MMS...I don't really want to go any further until I know if I should go back & wipe those things & then do it over...anyone?
I ended up in the exact situation as the op. I went back to stock rooted with perm S-Off and the update got pushed to my phone.
When I noticed the phone trying to update but stuck at the screen you are describing I pulled the battery and went into recovery from hboot. In recovery under mounts there is an option to turn on sd storage or something like that. I've used it before so I knew it would allow me to access the sd card from pc. I then downloaded the rooted rom of the ota. Then I unmounted the phone from pc, rebooted recovery, and went through the normal rom installation.
Sent from my ADR6400L using xda premium
The only issue to me seems if you have something on the phone not backed up you want to keep. Even if the update installs and it updates the bootloader back to s-on, revolutionary root still works so you cam just re-root.
Edit: I recommend you head over to thunderboltforums to at least restore the bootloader to stock s-off if you want to accept the update and re-root.
Sent from my ADR6400L using Tapatalk
Related
OK I have never posted anything on this site so I hope this is the right section.
Anyway to get to the point, I believe I bricked my Thunderbolt.
I went from Bamf Remix 1.6 to Cubed Rom and then upgraded to Das Bamf 2.0 after I upgraded my Radio to the Gingerbread one I believe. It booted up fine and I love the 2.0 update but it ran too slowly and I could literally see my battery life draining so I decided to switch back to my backup of my 1.6 but when i tried to boot into recovery, it auto loaded the radio update and i must of clicked the power because it redid that. after that my TB would only get to a black screen but I could tell it was on cause my computer detected it and i could see the backlight on. so then i loaded my other microSD into it and tried to restore with a backup from there but now it will only rebooot to the white screen with the 4 options and no way to get to recovery. Am I bricked or am i overreacting. Thanks in advance for ur guys help. love this site!
you have to downgrade back to a froyo radio if you reverted back from gingerbread. Get the one listed in the radio thread on the developers forum or rooting thread how-to that mentions it's for s-off and modified to have root permissions allowed.
You can stick it on your sd card from clockwork recovery by mounting your sd card via usb.
Also, that white screen with the options you see is the bootloader. If you read the options, the bootloader has an option to boot into recovery.
Take a deep breath, relax and hold your panicking for a while and try again
Also here's the radio from the restore to stock thread (this will fully restore to stock and all data not on the sdcard, but with s-off still so you can flash again):
http://www.multiupload.com/26WG1UZCXR (md5sum: abda920f3e159fb05c00d8c54a5b8768)
That is fricken ridiculously awesome man. A 12 minute reply at this time. Thank you so much man. I will try this and hope that it works. I will get back to ASAP! THANKS!
Ok I downloaded the file you linked me and put it on the root of my microSD card. but when i boot up my phone it only goes to the white bootloader screen and there is no recovery option any advice?
can try while its rebooting adb reboot recovery
then wipe cache factory rest wipe dalvik then fresh install das bamf 1.6
worst case senario as it sounds ull have to ruu back to stock and re-root ull have to bit of searching for this info cant remeber where i found Ruu but ya it turns s-on so make sure u read alot and pay complete attention to what you do also make sure ur not on the GB leak radio cause wont work with froyo unless u use MR2 that might be step 2 in this senario after u try to get into recovery via adb.
Sorry, I don't really have anything to contribute to your solution, RUU/reroot is nearly always a surefire solution...
however, let this be a warning to others, this is why one of the last steps in a radio flash is
DELETE PG05IMG.zip FROM YOUR SDCARD.
itsdubai said:
Ok I downloaded the file you linked me and put it on the root of my microSD card. but when i boot up my phone it only goes to the white bootloader screen and there is no recovery option any advice?
Click to expand...
Click to collapse
rename the radio from PG05IMG_MR1_upgrade.zip to PG05IMG.zip, then stick it on the card just as you did when you rooted to begin with (basically you are doing the same steps you did for rooting, just not reverting to the old radio, since you already have s-off.
AFTER YOUR DONE AND EVERYTHING WORKS, REMOVE PG05IMG.zip FROM YOUR SDCARD (youll wish you had of if you didnt eventually).
itsdubai said:
Ok I downloaded the file you linked me and put it on the root of my microSD card. but when i boot up my phone it only goes to the white bootloader screen and there is no recovery option any advice?
Click to expand...
Click to collapse
It sounds like it may be coming up in fastboot mode in which case there should be a button in the menu list for bootloader. Select bootloader and it ought to bring up additional options including recovery.
Sent from my ADR6400L using XDA App
yareally said:
rename the radio from PG05IMG_MR1_upgrade.zip to PG05IMG.zip, then stick it on the card just as you did when you rooted to begin with (basically you are doing the same steps you did for rooting, just not reverting to the old radio, since you already have s-off.
AFTER YOUR DONE AND EVERYTHING WORKS, REMOVE PG05IMG.zip FROM YOUR SDCARD (youll wish you had of if you didnt eventually).
Click to expand...
Click to collapse
This method worked for me when I reverted. Everything will be deleted but you should be back to working, then get Rom manager, and restore your backup. I did it twice yesterday bouncing between BAMF 1.7 and 2.whatever.
So here's the situation. I've been running NoSensi 1.0.4 ROM w/o problems for the past month but all of a sudden tonight my phone started to freeze up. I would take the battery out and turn it back on but after a few minutes the phone would freeze up again. So I decided to try to flash the new version on NoSensi (1.0.8) and the first step was to flash the NoSensi_EXT4_Wipe and it was almost complete in CWM when it froze up and wouldn't respond. Waited a few more minutes to be sure it wasn't just taking a while so I took the battery out and went back into recovery. In CWM, I see the menu options but when I try to select install from SD, the CWM menu would reset every few seconds and leave me at the main screen.
So now I'm stuck with a phone that won't boot cause I don't have a proper ROM on and can't install a new ROM cause CWM is messed up.
Any ideas on how I can reinstall CWM or something?
First off, can you boot to hboot? And next do you have adb set up on your PC or Mac?
I'm gonna be honest with you, I can't really help you all the way but can give you the things you need to get started. And if anyone reads this and knows more about this please help thanks
Sent from my CM7 Nightly HTC Desire HD
Yes, I believe I can get into HBOOT, I get the white screen where the option of going into recovery of HBOOT. I do have adb on my PC, but don't know how to use it unless I have instructions.
Okay I remember going through the threads and saw something on using the PD98 img that has the recovery img inside instead of the system img. Ill look around but probably in the morning since its almost 2 for me. Or if someone knows what I'm talking that'd be great
Sent from my CM7 Nightly HTC Desire HD
bluizzo said:
Okay I remember going through the threads and saw something on using the PD98 img that has the recovery img inside instead of the system img. Ill look around but probably in the morning since its almost 2 for me. Or if someone knows what I'm talking that'd be great
Sent from my CM7 Nightly HTC Desire HD
Click to expand...
Click to collapse
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Gene Poole said:
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Click to expand...
Click to collapse
Got CWM back with this, thanks so much! I tried doing the same method that was mentioned in this thread http://forum.xda-developers.com/showthread.php?t=1019868 but kept having issues with CWM resetting every 2 seconds which didn't allow me to use it at all. Your file worked and am flashing a ROM on now. Hopefully the random freezing was just random so I'm just going to do a fresh install of a ROM
Gene Poole said:
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Click to expand...
Click to collapse
Yay that's what I was looking for, thanks soo much
Sent from my CM7 Nightly HTC Desire HD
so it seems it may be a hardware issue after all... sigh. Going to look to see if I can pick up another one for cheap on craigslist or something now cause mine was also used of CL about 5 months ago.
dtothesquare said:
so it seems it may be a hardware issue after all... sigh. Going to look to see if I can pick up another one for cheap on craigslist or something now cause mine was also used of CL about 5 months ago.
Click to expand...
Click to collapse
HTC warranties the device for a year. I don't think any Inspire is a year old yet so you might want to call them first. Even if not covered by warranty, HTC is pretty reasonable on repairs.
Gene Poole said:
HTC warranties the device for a year. I don't think any Inspire is a year old yet so you might want to call them first. Even if not covered by warranty, HTC is pretty reasonable on repairs.
Click to expand...
Click to collapse
Cool, thanks for the tip, i'll try to get stock by on then call them up
So I'm trying to run the PD98IMG image in HBoot, but its not auto-running anymore. Any ideas on how to manually have it run?
- EDIT: Nvm, it was due to bad sdcard
Gene Poole said:
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Click to expand...
Click to collapse
So I tried reverting back to stock via the PD98IMG method with both the gingerbread and complete stock in the post you mentioned. Both them it updates fine but on the reboot it just hangs on the white htc screen. Any recommendations? Would HTC warranty if it's stuck like that?
It sounds like a hardware problem to me. The first and most obvious sign that a phone has been rooted is the S-OFF in the HBOOT screen. They probably won't warranty it if this is still set. Unfortunately, you need a functioning phone to get to the point that you can re-apply S-ON. I'm really not sure what advice I can give you at this point.
Gene Poole said:
It sounds like a hardware problem to me. The first and most obvious sign that a phone has been rooted is the S-OFF in the HBOOT screen. They probably won't warranty it if this is still set. Unfortunately, you need a functioning phone to get to the point that you can re-apply S-ON. I'm really not sure what advice I can give you at this point.
Click to expand...
Click to collapse
I figured as much. Oh well, going to miss the Inspire, really did like it except for that stupid battery door. Picked up a used captivate for cheap to hold me over until my next phone. Thanks for your help!
Missing CWM / No Recovery
Through a long string of mistakes, I'm stuck with an Inspire that will not load Recovery (just get black screen with phone icon and red exclamation point).
This thread was the best match I could find. I used the method above (renamed Gene Pool's file to PD98IMG.zip, placed on SD root), but HBOOT does not seem to find it during the startup scan.
Here is what I've got:
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
I've tried 2 different SD cards - I got into this mess because radio updates were not being found in PD98IMG.zip files either, so feel like its an HBOOT problem.
Any ideas?
ctownj30 said:
Through a long string of mistakes, I'm stuck with an Inspire that will not load Recovery (just get black screen with phone icon and red exclamation point).
This thread was the best match I could find. I used the method above (renamed Gene Pool's file to PD98IMG.zip, placed on SD root), but HBOOT does not seem to find it during the startup scan.
Here is what I've got:
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
I've tried 2 different SD cards - I got into this mess because radio updates were not being found in PD98IMG.zip files either, so feel like its an HBOOT problem.
Any ideas?
Click to expand...
Click to collapse
If you are sure you renamed it correctly (Windows didn't mangle the name with its stupid "hide extensions" feature) and you are S-OFF, then the only other thing it could be is a bad or weak SD Card. Do you have a spare to try?
I solved this. Figured it was not reading my SD cards so I reformatted one (FAT32), redid everything, and was able to re-flash CWM. Bizarre, since the same card has been used successfully several times on this phone.
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.
I used revolution to root my phone, I think it work (havent put any type of rom in it yet); but then i decided to upgrade it to ice cream sandwich. and when i tried to install ice cream i am getting this blank black screen with white triangle sign and yellow exclamation mark + blue droid robot. Any idea what going on? If the operating system is installing properly, how long should I be seeing this screen? I read somewhere that this is a system loading sign, but how long is it going to be like this (must be at least 40 minutes already)
>> download root checker to find out if have or have not root your phone.
-So first question would be, if the phone is root. Can I upgrade it to ice cream sandwich like normal? Or I have to do something else.
>> while doing rooting, dont mess around with OTA update
-I am in a sorta of limbo right now, because i havent figure out what rom to put in. And then opt to upgrade instead. What my best option?.
>>very helpful
http://forum.xda-developers.com/showthread.php?t=1192300
http://forum.xda-developers.com/showthread.php?t=1472298
http://lifehacker.com/5853519/how-do-i-fix-my-bricked-android-phone
-I got revolution to work, install clockworkmod recovery...but not much else. Anything else I need to press forward, or go backward (I have yet to backup my data/phone numbers...)
>>just backup everything and pray! j/k
do everything twice if you have too, and make all the mistakes along the way; that how some of us sorta learn.
Please help ASAP. My phone is in limbo right now!
>>not anymore, , thank you everyone for contributing!
and if at some moments you feel this is sorta over your head, try to get a hold of one of those experts who do up these ROM. They should know these things inside out.
Thank you
daitka said:
I used revolution to root my phone, I think it work (havent put any type of rom in it yet); but then i decided to upgrade it to ice cream sandwich. and when i tried to install ice cream i am getting this blank black screen with white triangle sign and yellow exclamation mark + blue droid robot. Any idea what going on? If the operating system is installing properly, how long should I be seeing this screen? I read somewhere that this is a system loading sign, but how long is it going to be like this (must be at least 40 minutes already)
-So first question would be, if the phone is root. Can I upgrade it to ice cream sandwich like normal? Or I have to do something else.
-I am in a sorta of limbo right now, because i havent figure out what rom to put in. And then opt to upgrade instead. What my best option?.
-I got revolution to work, install clockworkmod recovery...but not much else. Anything else I need to press forward, or go backward (I have yet to backup my data/phone numbers...)
Please help ASAP. My phone is in limbo right now!
Thank you
Click to expand...
Click to collapse
Do you mean OTA ICS or a custom Rom ICS?
Hmm if it is the SECOND one you should try booting into recovery via the hboot screen. From there you can wipe data and restart. If the fault occurs again well I have no idea
If you meant an ICS update from HTC then you need to redlash the stock recovery.
Sent from my Sensation using XDA
answer
Do you mean OTA ICS or a custom Rom ICS?
Hmm if it is the SECOND one you should try booting into recovery via the hboot screen. From there you can wipe data and restart. If the fault occurs again well I have no idea
If you meant an ICS update from HTC then you need to redlash the stock recovery.
>> Hi, I meant the first option. OTA ICS. I think I make a mistake of trying to do update while not finishing rooting my phone in the first place.
how do i go about reflash to stock recovery?, i dont want to lose my data/contact...
have you flashed 3.32 firmware and super Cid?
this is required for ICS.
Beamed from my Senny..
Sindroid said:
have you flashed 3.32 firmware and super Cid?
this is required for ICS.
Beamed from my Senny..
Click to expand...
Click to collapse
>> uhm no. should i be doing that? i thought rooting the phone/adding a new rom should be pretty straightforward. now it's getting pretty complicated!
daitka said:
>> uhm no. should i be doing that? i thought rooting the phone/adding a new rom should be pretty straightforward. now it's getting pretty complicated!
Click to expand...
Click to collapse
It's not that bad, you only have to supercid then flash new firmware once when going to ics. Then its just wiping and flashing
Sent from my sensational sensation 4g
I wish I can say I understand these steps, but it is getting more and more convoluted! any link to a page with steps by steps instruction? kinda feel like i am going into unchart water.
Most Ics Roms require 3.32 firmware and gb Roms require a different firmweare. Most people prefer Ics which is Android 4.0.3 . Once you have the correct firmware is quite a straight forward process. If your S off, you will place the Rom at the root of your sd card. I do this buy downloading to my computer, using my phone as a removable disk drive and copying the file to my device. It goes directly to root not into a folder. Then I enter into my recovery, i love 4ext touch recovery because it has more options and is easy to use. I do a nandroid backup of my current rom, incase something goes wrong. I. Use 4 ext for the backup also. Then I do a full wipe usually wipe data factory reset, then I wipe cash and dalvick cash then I install zip from sd card and reboot. This is how I install a Rom. After flashing it WILL take some time for the first boot so don't worry if it takes a few minutes sometimes. Then it will say Android is upgrading then it will boot into your new rom
I hope this helps you some in the steps to flashing a rom.please remember firmware is very important. Have fun flashing.
Sent from my Sensation 4G using xda premium
Your very welcome, remember this is just the steps to rom flashing. You FIRST must be rooted and S Off to use the procedures. Don't worry too much because once rooted and S off if you get in a pinch flashing you have your backup. But remember correct firmweare is very very important. Hope I've helped you out a bit in the rom flashing area
Sent from my Sensation 4G using xda premium
You should READ and understand this procedure : Click!
Everything you need to know to succeed is in that thread. If you have question after that come back and ask.
Oups! Forgot this link too.... Click!
realsis said:
Your very welcome, remember this is just the steps to rom flashing. You FIRST must be rooted and S Off to use the procedures. Don't worry too much because once rooted and S off if you get in a pinch flashing you have your backup. But remember correct firmweare is very very important. Hope I've helped you out a bit in the rom flashing area
Sent from my Sensation 4G using xda premium
Click to expand...
Click to collapse
i believe i am already root and s-off. when you said i have a backup? what backup?!
how do i figure out what firmware i got, and which version is the correct one?.
i think i am going with the ICS route.
Here's some more information:
I downloaded a ROM Manager through marketplace, and when I tried to run it. I get the following error message: "You must root your phone for ROM Manager to function. Superuser was not found at '/system/bin/su' or '/system/xbin/su'. Use google search on your computer to find instructions to root your phone"
I also downloaded Superuser app, and when i click on it, it open up but it said 'no apps in list'!
I downloaded Titanium backup, but when I tried to run it. I get the following error message :"Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted and include BusyBox, and try again. This attempt was made using the 'su' command"
I download the ruu file ('RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed) , tried to run it; and the computer ask what program should i use to open it!?
thanks.
You can download root checker to verify your root it will let you know if root was successful. Ics uses 3.32 firmware. I aquire backup by going into 4ext recovery, manage backup, new backup, backup system. What recovery are you using ? Usually you can backup from recovery. You can download correct firmware in search or usually the rom site will also have the firmware in Android development. Hope this answers some of your questions.
Sent from my Sensation 4G using xda premium
realsis said:
You can download root checker to verify your root it will let you know if root was successful. Ics uses 3.32 firmware. I aquire backup by going into 4ext recovery, manage backup, new backup, backup system. What recovery are you using ? Usually you can backup from recovery. You can download correct firmware in search or usually the rom site will also have the firmware in Android development. Hope this answers some of your questions.
Sent from my Sensation 4G using xda premium
Click to expand...
Click to collapse
so i just ran root checker and the result is : " Sorry, this device does not have proper root access"
so now what?!
OK...
Pull out the battery...
Replace battery
Hold Volume Down and press power button while still holding volume down.
That will give you the fastboot menu.
Write down what is written in upper left of your screen. (Or take photo).
EDIT :
See attachment, this is what you must have before going a step ahead.
Lucky Thirteen said:
OK...
Pull out the battery...
Replace battery
Hold Volume Down and press power button while still holding volume down.
That will give you the fastboot menu.
Write down what is written in upper left of your screen. (Or take photo).
Click to expand...
Click to collapse
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT - 1.17.1111
RADIO – 10.14.9035.01_M
eMMC-boot
Jun 2 2011, 22:31:39
Ok now this is fine.
You don't have root, usually when the line Openxxx is missing it's because you don't have root privileges.
Now download this recovery Recovery PG58IMG.zip
Copy the PG58IMG file into the Root folder of your SD card.
Turn off your phone by removing again the battery and reboot into the Bootloader/HBOOT screen like you just did to gave me your infos.
Press Volume up to Accept when it asks" Do you want to start the update" DON'T STOP the processus until it give you the option to reboot.
Press Power to Reboot
Delete PG58IMG from your memory card.
Lucky Thirteen said:
Ok now this is fine.
You don't have root, usually when the line Openxxx is missing it's because you don't have root privileges.
Now download this recovery http://www.multiupload.nl/ECVA5V4ED3
Copy the PG58IMG file into the Root folder of your SD card.
Turn off your phone by removing again the battery and reboot into the Bootloader/HBOOT screen like you just did to gave me your infos.
Press Volume up to Accept when it asks" Do you want to start the update" DON'T STOP the processus until it give you the option to reboot.
Press Power to Reboot
Delete PG58IMG from your memory card.
Click to expand...
Click to collapse
hi, would the file, recovery-clockwork-touch-5.8.0.9-pyramid work? i already got that downloaded in the past!
also, where is the root folder on my sd card.? if i dont have one; should i be creating it?
daitka said:
hi, would the file, recovery-clockwork-touch-5.8.0.9-pyramid work? i already got that downloaded in the past!
also, where is the root folder on my sd card.? if i dont have one; should i be creating it?
Click to expand...
Click to collapse
No. Please take the file from the multiupload link I just gave you. Take this one : http://forum.xda-developers.com/showpost.php?p=17173579&postcount=86
The root of your SD card is the very first view you see when you open the SD card e.g. path of SDcard -> E:\PG58IMG.zip (don't create a file just paste the file there)
This is the root of your SD card.
what the point of downloading this img file and running it?
what do i do after this?
Sorry I felt asleep at the computer...
This PG58IMG is for installing the Recovery.
I know this isn't technically the right section for this but I put it here in hopes more people would see it. This is very important for anyone rooting using the dirtysanta method and perhaps other methods as well. It would be nice if this could get a sticky because people need to see this or this problem is going to keep occurring. I'm seeing it all over the threads.
DO NOT FACTORY RESET FROM INSIDE THE ROM. DO NOT USE LG's BUILT IN FACTORY RESET IN THE PHONE OR YOU WILL GET STUCK IN RECOVERY. Use the factory reset option inside of TWRP if you want to do a factory reset.
There have been many people (myself included even though I knew better and told myself not to do it before I did) who have got stuck in recovery because of this and it's not common sense to get out of it. I've been rooting and messing with this stuff for over 5 years and for 2 hours tried every trick I knew and nothing worked. What did finally end up working for me personally is this:
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power (hold them down), as soon as you see the LG logo let go of power for a brief moment and continue to press and hold both buttons until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount storage button, and reboot system.
lol this is only because it give you your stock boot.img. So if you factory reset, you have to flash SuperSU, no need to freak out.
If you format /system, you will need to flash a ROM, if the ROM does not flash SuperSU, you will h ave to flash it.
That's all folks!
That said, who wants a VZW Custom ROM and Kernel? Making the thread now. Identical to my H918 5.1 MOD ROM
Tilde88 said:
lol this is only because it give you your stock boot.img. So if you factory reset, you have to flash SuperSU, no need to freak out.
If you format /system, you will need to flash a ROM, if the ROM does not flash SuperSU, you will h ave to flash it.
That's all folks!
That said, who wants a VZW Custom ROM and Kernel? Making the thread now. Identical to my H918 5.1 MOD ROM
Click to expand...
Click to collapse
I tried flashing supersu.zip but that wouldn't work either. I challenge you to factory reset in the rom and then once stuck in recovery flash a new rom and the supersu zip and see if that works. I did this several times and it wouldn't work. I tried it with flashing a rom, and after restoring a backup. What appears to be happening is the system isn't mounting and it doesn't recognise that you have a ROM installed.
Not freaking out either, just trying to let people know not to factory reset inside the rom but use TWRP. There have been many people with this issue.
imucarmen said:
I tried flashing supersu.zip but that wouldn't work either. I challenge you to factory reset in the rom and then once stuck in recovery flash a new rom and the supersu zip and see if that works. I did this several times and it wouldn't work. I tried it with flashing a rom, and after restoring a backup. What appears to be happening is the system isn't mounting and it doesn't recognise that you have a ROM installed.
Not freaking out either, just trying to let people know not to factory reset inside the rom but use TWRP. There have been many people with this issue.
Click to expand...
Click to collapse
Oh, sorry. I overlooked something. That you had in huge bold caps the words IN THE ROM lol, my bad. I've never factory reset from within the ROM.
But my post stands when factory resetting from TWRP.
Tilde88 said:
Oh, sorry. I overlooked something. That you had in huge bold caps the words IN THE ROM lol, my bad. I've never factory reset from within the ROM.
But my post stands when factory resetting from TWRP.
Click to expand...
Click to collapse
Yea I knew better too, that's the bad part. In 5+ years I've never factory reset while in a rom when I have root and TWRP installed. Before I did it I even told myself it was probably a bad idea and I should just use TWRP. But my lazy conscience said "ahhh what the heck! just do it, it's too much trouble to boot into TWRP and besides, it might work ok" I hate my lazy consicence :'(
Exactly what I did and exactly what happened.
Gonna try this in the AM. One question...
If I'm able to flash back to "stock" using a deoxed stock rom, how can I then get rid of the boot warning so I can return this device to T-Mobile?
mrbigdrawsz said:
Exactly what I did and exactly what happened.
Gonna try this in the AM. One question...
If I'm able to flash back to "stock" using a deoxed stock rom, how can I then get rid of the boot warning so I can return this device to T-Mobile?
Click to expand...
Click to collapse
You'll need to return to full stock. I can't verify it works but this thread here claims to have a method for returning to stock.
imucarmen said:
You'll need to return to full stock. I can't verify it works but this thread here claims to have a method for returning to stock.
Click to expand...
Click to collapse
Well pray for me. Downloading now and will try first thing tomorrow.
mrbigdrawsz said:
Well pray for me. Downloading now and will try first thing tomorrow.
Click to expand...
Click to collapse
Did it work for you? Also since there is no t mobile rom there what did you use?
thegameksk said:
Did it work for you? Also since there is no t mobile rom there what did you use?
Click to expand...
Click to collapse
I used this guide https://goo.gl/ZHZPfO and it worked perfectly. Had a little stress when attempting to flash the stock recovery, but after installing two again, I was able to revert back to stock. Locked bootloader and it's as if I never did anything but boot up the stock OS.
Returning to T-Mobile today and just waiting on my Oneplus 3T to ship (granted I'm pissed off because the 128gb version is out of stock).
mrbigdrawsz said:
I used this guide https://goo.gl/ZHZPfO and it worked perfectly. Had a little stress when attempting to flash the stock recovery, but after installing two again, I was able to revert back to stock. Locked bootloader and it's as if I never did anything but boot up the stock OS.
Returning to T-Mobile today and just waiting on my Oneplus 3T to ship (granted I'm pissed off because the 128gb version is out of stock).
Click to expand...
Click to collapse
Glad you got it fixed.
Just for the record, this thread isn't for helping people get back to stock, its main focus is to warn people not to factory reset inside the rom. Then I just shared the method that worked for me to get out of being stuck in TWRP. Not saying you implied any different, I'm just clarifying for anyone that may read in the future. It's awesome return to stock methods are now popping up which are usually good for fixing all sorts of issues.
Enjoy your OnePlus 3T