Related
So I never rooted, I have been waiting for the Over the Air.
If I root now, when I get the OTA will I still be rooted? And if so, what steps should be taken?
I know there are two unrevoked applications that need to be run...the first for root...the second for s-off (which I am still not entirely sure what this is)....
I have also seen that unrevoked is much simpler on a Mac and thankfully I just got one.......
So if rooting now and getting the OTA and keeping root is possible.... is there a step by step of the order I should do this in? (please don't flame and say I can search...I did...couldn't find.. I did however find a ton of threads where people say to search.......if you need to flame me can you at least post a link to where I was stupid enough to miss it)
Thanks
I am wondering the same. I have rooted with unrevoked3 and forever but have not touched the radio. Will I receive the OTA like this? If not what do I have to do to get the OTA and then get root back ?
Assuming you have a truly stock Incredible (meaning you didn't force any third party roms or leaked radios), then you follow this order:
1. Unrevoked Flash/Recovery - Adds Clockwork Mod and Superuser permissions to your phone
2. Unrevoked Forever - Adds S-OFF functionality, which means that the HBOOT startup will no longer check for updates that are signed with HTC's super secret signature... Meaning you can flash anything to the phone.
3. Flash Original Stock Recovery - Removes the Clockwork Mod recovery console. Since you have S-OFF, you can return CWM to the phone whenever you damn well please. The original stock recovery is necessary for the OTA to commence, because it is developed to rely on the stock recovery console.
4. Wait for OTA
5. Upon receiving OTA, flash Clockwork Mod to the phone via HBOOT (using a PB31IMG.zip containing it)
6. Flash the root payload via Clockword Mod recovery console.
7. Go to bed and make love to your wife after beating on your chest in victory like tarzan.
8. Reboot phone, bask in Official Froyo coupled with Superuser permissions.
9. Download the busybox installer from the market and install busybox to the system.
10. Make love to your wife again.
UPDATED: with slightly better instructions
Note: If u are s-off and on a custom rom, or have already s-off and customized your current rom you can start at step 3. make sure u have s-off by checking hboot. i put this in because many people asked me what to do if they ddnt start in a stock state.
This process is for people with a fully stock phone who want to apply the stock 2.2 update and maintain root.
I just went through this process.
(sd card must be formatted to fat32. without that most of this will fail.)
Step 1: do this -> http://unrevoked.com/recovery/
(this will root your phone and flash clockworkmod recovery.)
Step 2: do this -> http://unrevoked.com/forever/
(this will use clockworkmod recovery to permanently unlock the nand, also known as s-off.)
-- To backup apps that you want after the phone is fully updated at this point download titanium backup and backup whatever apps u need. make sure u take the backup folder from the sd card and store it on ur pc for later use.
Note: Titanium is probably going to tell u that it couldnt get root. that is because busybox is missing. hit the problems button on titanium and upgrade busybox. this will upgrade busybox if ur using an older version, or download the right version if u dont have one. this should take care of all busybox needs.
Step 3: do this -> http://forum.xda-developers.com/showthread.php?t=756850
(put into sd card and hboot apply)
(this will restore the recovery back to stock as it is needed for the RUU)
now u have an s-off phone with everything else stock.
Step 4: now either get the RUU -> http://forum.xda-developers.com/showthread.php?t=765596
or wait for OTA
(install htc sync to be able to run this. the RUU will load the stock 2.2 rom 2.15 radio that is needed. everything will be wiped, but that is a good thing imo.)
once u have updated ur phone fullly
Step 5: get recovery here http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
put in sd card and hboot apply
(this will load clockworkmod recovery on your phone so that u can apply updates.)
Step 6: put in sd card -> http://forum.xda-developers.com/attachment.php?attachmentid=388592&d=1282834695
and
http://bit.ly/su234ef
and use recovery to install both those zips.
(clockworkmod recovery allows u to apply .zip files, use that option to do this.)
(this will re-root the newly updated phone and install the superuser.apk.)
congratulations now u have an OTA/RUU applied phone with root.
-- If you had titanium backups you want to restore, paste the folder u saved on the desktop back here, re-install titanium from the market and restore apps. It is recommended to redownload the app from the market and just restore the data for the app if possible.
Note: Titanium is probably going to tell u that it couldnt get root. that is because busybox is missing. hit the problems button on titanium and upgrade busybox. this will upgrade busybox if ur using an older version, or download the right version if u dont have one. this should take care of all busybox needs.
notes:
* to enter hboot turn off phone then hold vol down and power till hboot appears.
* to enter recovery, enter hboot and select recovery.
* to check if nand is unlocked, hboot must read S-OFF
* you only need stock recovery to load the RUU, so if you have flashed a different rom, simply revert to the stock recovery and apply the RUU
* all links are property of their original creators, thanks to all of them.
EDIT: and yes please make love multiple times.
Wow... Thanks... This should definitely be stickied as a guide!
Sent from my HTC Incredible
No prob, if you need any help when you are getting to the nitty gritty pm me and I'll give you a phone number to call me at, I love doing this stuff.
Thanks... Will probably wait til the phone starts nagging me to update (from other phones I have seen its pretty persistent). This way in case anything new pops up I can add it to the process.
Also its 2 AM in New York right now, I have never rooted, let alone do everything to get ready for the OTA (definitely waiting for the push... Not applying it manually).... I'd probably frak it up at this hour!
Sent from my HTC Incredible
Thanks rdmerck and k.electron...very helpful and exactly what I've been looking for. After waiting a while, I finally decided to root tonight prior to the impending OTA update.
One cautious newbie question for step 3 (Flashing The Original Stock Recovery). Once in hboot (I entered this by holding down the volume down while powering up, right?), how do you know it will be running the PB31IMG.zip file (Stock Rom)? I didn't see it listed anywhere on the screen and it only offers the option of running recovery or not. I want to make sure that it's running off the correct .zip file. It lists:
INCREDIBLE XC SHIP S-OFF
HBOOT-0.77.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-1.00.03.04.06
Mar 23 2010,19:26:22
HBOOT
Parsing...[SD ZIP]
[1] RECOVERY
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
Just wanted to be sure before running the update. I assume you can delete the unrevoked-forever.zip once it's run, but can you delete the "update.zip" that appeared on the sdcard after running unrevoked?
Thanks in advance for any and all help!
chaint said:
Thanks rdmerck and k.electron...very helpful and exactly what I've been looking for. After waiting a while, I finally decided to root tonight prior to the impending OTA update.
One cautious newbie question for step 3 (Flashing The Original Stock Recovery). Once in hboot (I entered this by holding down the volume down while powering up, right?), how do you know it will be running the PB31IMG.zip file (Stock Rom)? I didn't see it listed anywhere on the screen and it only offers the option of running recovery or not. I want to make sure that it's running off the correct .zip file. It lists:
INCREDIBLE XC SHIP S-OFF
HBOOT-0.77.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-1.00.03.04.06
Mar 23 2010,19:26:22
HBOOT
Parsing...[SD ZIP]
[1] RECOVERY
Do you want to start update?
Yes
No
Just wanted to be sure before running the update. I assume you can delete the unrevoked-forever.zip once it's run, but can you delete the "update.zip" that appeared on the sdcard after running unrevoked?
Thanks in advance for any and all help!
Click to expand...
Click to collapse
I just went through doing the same thing. I deleted the update.zip from my SD card just to make sure there was no confusion. Then I clicked yes when it asked to apply the update. Also, after this, if you boot into recovery ( its a couple options down in hboot, move with your volume button) you should get a red caution sign after a few seconds. Apparently this means you are back to stock. All credit goes to someone who helped me in another thread but I cannot find it right now.
chaint said:
Thanks rdmerck and k.electron...very helpful and exactly what I've been looking for. After waiting a while, I finally decided to root tonight prior to the impending OTA update.
One cautious newbie question for step 3 (Flashing The Original Stock Recovery). Once in hboot (I entered this by holding down the volume down while powering up, right?), how do you know it will be running the PB31IMG.zip file (Stock Rom)? I didn't see it listed anywhere on the screen and it only offers the option of running recovery or not. I want to make sure that it's running off the correct .zip file. It lists:
INCREDIBLE XC SHIP S-OFF
HBOOT-0.77.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-1.00.03.04.06
Mar 23 2010,19:26:22
HBOOT
Parsing...[SD ZIP]
[1] RECOVERY
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
Just wanted to be sure before running the update. I assume you can delete the unrevoked-forever.zip once it's run, but can you delete the "update.zip" that appeared on the sdcard after running unrevoked?
Thanks in advance for any and all help!
Click to expand...
Click to collapse
Yes, where it says
Parsing...[SD ZIP]
[1] RECOVERY
It is informing you that the only thing contained in the PB31IMG.zip file is a recovery image to be flashed. In this case, it is the stock Android 2e recovery that you will need. Press the volume up key to flash it, and then you can boot into the recovery console to verify that it works.
When you see a black screen, with a phone and a triangle with an exclamation point, you are in Android 2e recovery (your goal all along), press power+plus volume up, and you will see a meaningless error message and then a menu will appear at the top of the screen.
The first option will be to reboot the system, make sure it is selected and press the power button again. When you do, it will bring you back into your operating system.
Wait. I went out of order and started with the love making. That's as far as I got....
Sent from my ADR6300 using XDA App
amdpimp said:
Wait. I went out of order and started with the love making. That's as far as I got....
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
what? nooooo.... rooted 2.2 is the main thing your wife is interested in.. and your incredible too..
amdpimp said:
Wait. I went out of order and started with the love making. That's as far as I got....
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I most certainly hope you bricked lol
Sent from my ADR6300 using XDA App
When I do this method (and waiting for the OTA) do I need to back up anything? Or does it leave my apps and data untouched?
Sent from my HTC Incredible
Format FAT32 required on storage card
I'd like to point out that step 3 REQUIRES your storage card to be formatted FAT32. Clockwork will not update to "[Recovery] Stock 2.1 Recovery Image for DI" without you having first formatted your storage card to FAT32. This may be common sense but for a first rooter like myself, I figured it out by trial and error.
k.electron said:
I just went through this process.
first do this -> http://unrevoked.com/recovery/
then do this -> http://unrevoked.com/forever/
then do this -> http://forum.xda-developers.com/showthread.php?t=756850
(put into sd card and hboot apply)
now u have an s-off phone with everything else stock.
now either get the RUU -> http://forum.xda-developers.com/showthread.php?t=765596
or wait for OTA
once u have updated ur phone fullly
get recovery here http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
put in sd card and hboot apply
put in sd card -> http://forum.xda-developers.com/attachment.php?attachmentid=388592&d=1282834695
and
http://bit.ly/su234ef
and use recovery to install both those zips.
congratulations now u have an OTA/RUU applied phone with root.
EDIT: and yes please make love multiple times.
Click to expand...
Click to collapse
NYC Coyote said:
When I do this method (and waiting for the OTA) do I need to back up anything? Or does it leave my apps and data untouched?
Sent from my HTC Incredible
Click to expand...
Click to collapse
It will leave all data and apps untouched but get in the habit of backups ALWAYS. You never know when playing around like this. You may do one thing wrong and will be wishing you had taken 5 minutes to do a backup.
anothen said:
I'd like to point out that step 3 REQUIRES your storage card to be formatted FAT32. Clockwork will not update to "[Recovery] Stock 2.1 Recovery Image for DI" without you having first formatted your storage card to FAT32. This may be common sense but for a first rooter like myself, I figured it out by trial and error.
Click to expand...
Click to collapse
thank you and yes fat32 for all things sd card related.
anothen said:
It will leave all data and apps untouched but get in the habit of backups ALWAYS. You never know when playing around like this. You may do one thing wrong and will be wishing you had taken 5 minutes to do a backup.
Click to expand...
Click to collapse
frankly its much better to just use the ruu and have it update everything and wipe the phone. 2.1->2.2 app and data moving can sometimes leave behind some stale stuff that u dont want.
before i did the RUU i installed titanium and saved any apps that had states that i needed, like games. then after i installed the RUU and reinstalled the apps from the market, i just titanium restored the data for the app so it still had the latest app, but my save games were back in. that will give u a good factory like device but with whatever data you find necessary.
i also mounted system in recovery after the whole process and removed things like cityid, vzwnav, stocks etc.
k.electron said:
frankly its much better to just use the ruu and have it update everything and wipe the phone. 2.1->2.2 app and data moving can sometimes leave behind some stale stuff that u dont want.
Click to expand...
Click to collapse
If you ran the RUU straight up were you rooted before hand with S-off? Then you ran the full RUU and retained root?
I currently have root, stock radio and no s-off yet. and want to update and retain root.
Thanks.
-Lil'
rdmerck said:
Yes, where it says
Parsing...[SD ZIP]
[1] RECOVERY
It is informing you that the only thing contained in the PB31IMG.zip file is a recovery image to be flashed. In this case, it is the stock Android 2e recovery that you will need. Press the volume up key to flash it, and then you can boot into the recovery console to verify that it works.
When you see a black screen, with a phone and a triangle with an exclamation point, you are in Android 2e recovery (your goal all along), press power+plus volume up, and you will see a meaningless error message and then a menu will appear at the top of the screen.
The first option will be to reboot the system, make sure it is selected and press the power button again. When you do, it will bring you back into your operating system.
Click to expand...
Click to collapse
Thanks rdmerck. I didn't see the phone and triangle when flashing, however. When I originally pressed volume up to flash, it took just a few seconds, then prompted me to reboot which I did, then it loaded the OS as normal. Not sure if I needed to do something else, or if there's a way to check to see if it worked (I still see SU Permissions in my apps). Should I just try again? Any thoughts. Thanks, and sorry for these newbie questions!
Help a noob out
OK can someone help out ANOTHER noob here?
I have been following this thread among 30 others since yesterday and there seems to be a ton of different ways to go about getting the same results, which for me is the new leaked build with root. I am hoping someone can set me straight as I have info overload right now.
I am currently running stock 2.1 and used unrevoked to root.
I have not done anything else at this point. No radio update, no s-off, no roms.. nothing. I do not mind wiping the phone and reinstalling all my apps and probably would want to start fresh with the new install.
Someone made a reference a few post up about just running the RUU. Can I do that without losing root? Do I need to update my radio first? Should I installed 'forever' s-off before hand?
Any help would be greatly appreciated. I basically want to install what seems to be the official OTA/RUU and retain my root access so I can run wireless tether and remove bloat I dont want. Once some of the roms get cooked with the new build I can full around with them. Just need some help getting over the hump right now, so I can be running some Froyo goodness.
Thanks so much for any help you can lend.
-Lil
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
garaxiel said:
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
Click to expand...
Click to collapse
You're problem is ClockworkMod. Version 5 is a steaming heap of crap that's caused this sort of problem, not only for dInc users, but Tbolt and other device users. The solution seems to be flashing back to an older recovery. And if it works, don't fix. I'm still running version 3.something on my Tbolt and have no plans to change that. I NEVER use ROM Manager and recommend nobody ever touch it except for a few things. I almost never have it installed on any device.
OK then dumb question but if RomManager FC's on me, how do i flash back to a working version or to an alternate version entirely? i have been unable to find other ways of flashing outside of RomManager
Older Recovery versions are available on "dougpiston.com" just follow the directions.
www.dougpiston.com has what you're looking for under "recoveries". They're flashed in hboot like a radio, RUU, splash screen, etc.
Also if that doesn't work, which it probably will, you can also flash a PB31IMG which essentially is the RUU but you do not need a PC. You put that on the root of the SD (as in, not in any folders. Probably know that already...) and reboot into HBOOT (Power and volume down) and itll load it up.
Note: Make sure the file is PB31IMG.zip and not PB31IMG.zip.zip
Ha!!! got it back (well on the road to back anyways)
Was able to find a PB31IMG on dougpiston.com and hboot flashed it in (3.0.0.8). I had one on my PC but it must have been corrupt because it didn't work before. once that was working i was able to get into recovery get a restore back to my 175 nightly and am in the process now of flashing nightly 181 on there cleanly and rebuild the whole phone from scratch. damn i hope this works thanks all for help and ideas.
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
pete_kowalski83 said:
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
No idea...are you using ROM Manager?
Sorry if it has been answered elsewhere, but I have a migraine and am going for now. I just wanted to post really fast. I rooted my phone recently and have CM 7.2 on my Dinc. Now it suddenly seems that programs seem to think it isn't. Programs such as Titanium Backup won't work saying there is no root. Same with BusyBox and so on. Anyone had any issues like this? Any ideas as to what is next? I am somewhat new to this and would appreciate the help.
Tried to just reroot, but can't seem to get DooMLord's thing to work. Can't get the ADB drivers since, for some reason the Android SDK thingy WILL NOT download the Google USB driver packages. Tried about 6 different times and it just will not download and install them. HELP?
BuffaloChips said:
Sorry if it has been answered elsewhere, but I have a migraine and am going for now. I just wanted to post really fast. I rooted my phone recently and have CM 7.2 on my Dinc. Now it suddenly seems that programs seem to think it isn't. Programs such as Titanium Backup won't work saying there is no root. Same with BusyBox and so on. Anyone had any issues like this? Any ideas as to what is next? I am somewhat new to this and would appreciate the help.
Tried to just reroot, but can't seem to get DooMLord's thing to work. Can't get the ADB drivers since, for some reason the Android SDK thingy WILL NOT download the Google USB driver packages. Tried about 6 different times and it just will not download and install them. HELP?
Click to expand...
Click to collapse
Open the superuser app and hit menu and select preferences. Scroll to the bottom and tap check for updates. If it says you have the latest update then hit the update anyways button. Also make sure you have the latest version of busybox installed. Then see if apps can get root. If not post back with your info.
S-off / s-on (can be found at the top of the hboot screen)
Android version (menu settings about phone software information)
Hboot version (found on hboot screen)
Radio (baseband) version. (also on hboot screen)
Also you can get the adb files and drivers here http://dinc.does-it.net/ADB
Tried that and it said d'ling manifest ... okay, parsing manifest ... okay, checking installed version = 3.0.3.2 . I clicked update anyway and got ,,, d'ling custom busybox ... okay, checking md5sum... FAIL! Tried the update fixer and it doesn't work either.Says no problems detected. In the little window it says checking signatures...ok! I click force and fix and get, extracting tiny busybox...fail! It says something about trying to download update.zip from somewhere but I cant see the rest.
My phone is s-off
Android version says 2.3.7
hboot 0.92.0000
radio 2.15.00.07.28
Now all I need are some good drugs so I can sleep. Migraines suck! It won't even let me do that.
BuffaloChips said:
Tried that and it said d'ling manifest ... okay, parsing manifest ... okay, checking installed version = 3.0.3.2 . I clicked update anyway and got ,,, d'ling custom busybox ... okay, checking md5sum... FAIL! Tried the update fixer and it doesn't work either.Says no problems detected. In the little window it says checking signatures...ok! I click force and fix and get, extracting tiny busybox...fail! It says something about trying to download update.zip from somewhere but I cant see the rest.
My phone is s-off
Android version says 2.3.7
hboot 0.92.0000
radio 2.15.00.07.28
Now all I need are some good drugs so I can sleep. Migraines suck! It won't even let me do that.
Click to expand...
Click to collapse
Try flashing these thru recovery.
http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip, and http://dinc.does-it.net/BusyBox/Busybox_1.19.4_Flashable.zip, then boot and see if your apps can get root.
Flashed them but no good. Still says no root with programs requiring it.
Was going to go nuts and shoot for flashing Condemned CM7.2 to see if I brick my phone or not, but after d'ling the ROM, I'm not sure what I'm supposed to do next.
BuffaloChips said:
Flashed them but no good. Still says no root with programs requiring it.
Was going to go nuts and shoot for flashing Condemned CM7.2 to see if I brick my phone or not, but after d'ling the ROM, I'm not sure what I'm supposed to do next.
Click to expand...
Click to collapse
If you want to flash a new rom, download the roms zip to your sdcard. Go to recovery and go to advanced and wipe dalvik-cache. Go to mounts and storage and format everything in there except sdcard and emmc. Then go to install zip from sdcard, internal sdcard, and choose the rom zip you downloaded, and select yes to flash it.
Are you sure that you have superuser app set to allow, and not deny these root apps. Try opening superuser app ad removing the root apps from the list. Then try using the root apps and see if it propmpts for and allows root.
I have super user set to prompt me every time and I click on allow. And yes, I have deleted and retried them so many times I want to rip out what is left of my hair.
OK, after flashing Condemnedsoul's cm7.2 (post says v12 but in about phone I get v10, go figure) nothing had changed. I got the ROM manager updated and clicked fix permissions and it went through a bunch of stuff. Now, before it wouldn't do anything through the ROM manager and recovery would do nothing either. Guess I found the culprit here. This is the bad thing about not being able to remove and reinstall these little items. Makes you really crazy at times as you are not necessarily sure that it is really the issue and if it is.... it requires a bit of extra work to fix. Live and learn.
Thanks for trying hard to help me though. It is greatly appreciated.
Oh, thanks for reminding me I am an idiot for not realizing one CAN flash ROM's straight from a .zip through recovery. LMAO! (this is meant as self-deprecating and not as an insult to you)
BuffaloChips said:
I have super user set to prompt me every time and I click on allow. And yes, I have deleted and retried them so many times I want to rip out what is left of my hair.
OK, after flashing Condemnedsoul's cm7.2 (post says v12 but in about phone I get v10, go figure) nothing had changed. I got the ROM manager updated and clicked fix permissions and it went through a bunch of stuff. Now, before it wouldn't do anything through the ROM manager and recovery would do nothing either. Guess I found the culprit here. This is the bad thing about not being able to remove and reinstall these little items. Makes you really crazy at times as you are not necessarily sure that it is really the issue and if it is.... it requires a bit of extra work to fix. Live and learn.
Thanks for trying hard to help me though. It is greatly appreciated.
Oh, thanks for reminding me I am an idiot for not realizing one CAN flash ROM's straight from a .zip through recovery. LMAO! (this is meant as self-deprecating and not as an insult to you)
Click to expand...
Click to collapse
Yeah it is recomended not to use rom manager for flashing things, but to go straight to recovery to do it. The only thing i use rom manager for is so that i get notified about new versions of cwm recovery.
If flashing new roms dosent fix the issue there are always ruu's which will put your phone back to complete stock except for still having s-off, making it easy to root again.
Great! Wi-Fi doesn't want to work now! Crap! Gets as far as trying to obtain an IP address from my router and then says out of range while I am about ten feet from the router and the strength meter is showing full...! It just gets better and better some days.
BuffaloChips said:
Great! Wi-Fi doesn't want to work now! Crap! Gets as far as trying to obtain an IP address from my router and then says out of range while I am about ten feet from the router and the strength meter is showing full...! It just gets better and better some days.
Click to expand...
Click to collapse
Sounds like you need to just ruu and start over fresh. Seems something is seriously buggy with your setup. Are you using a custom kernel, or one that came with the rom?
Well, Wi-Fi was working with the original CM7.2. Just seems that it isn't with Condemned's. And I am using the kernel that came with the ROM.
To be honest, I haven't a clue about doing an RUU install.
BuffaloChips said:
Well, Wi-Fi was working with the original CM7.2. Just seems that it isn't with Condemned's. And I am using the kernel that came with the ROM.
To be honest, I haven't a clue about doing an RUU install.
Click to expand...
Click to collapse
Ruus are pretty simple. Make positive you are s-off before doing this, or rerooting will be a lot harder.
Download the ruu http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip
Do not rename it just stick it on the root (in no folders) of your sdcard.
Boot into recovery (if entering recovery thru hboot select no when prompted to update) wipe dalvik-cache in the advanced menu, and format everything in mounts and storage except emmc and sdcard.
Power off the phone and boot to hboot. (hold vol down plus power till a white screen pops up) Hboot will find the ruu automaticly and prompt you to press vol up to update. Do so and let it do its thing, note it will reboot once durring the ruu, be patient and do not interupt it. When done press vol up to reboot. You are now stock.
Do the setup on the phone and then go to menu - settings - applications, and uncheck fastboot. Use a file explorer or pc to remove the PB31IMG.zip from your sdcard.
Power off the phone and boot to hboot again. From the hboot menu select factory reset. This will ensure all corrupt data is gone. After it finishes the phone should boot again. Once again do the setup and uncheck fastboot again.
Download these two files:
http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip
Do not rename them and place them on the root of your sdcard.
Power off the phone and boot to hboot. It will find the PB31IMG.zip file (cwm recovery) and prompt to press vol up to update. Do so. When asked to reboot press vol down no.
Select recovery from the hboot menu. Once in recovery select install zip from sdcard - internal sdcard- and select the Superuser_3.0.7.zip. Select yes when prompted.
Reboot thr phone and go to the market and download the busybox app. Open busybox and install it. Go to your sdcard and delete or rename the clockwork PB31IMG.zip.
Thats it you should be stock rooted. From here you can stick with stock, or flash a rom of your choosing.
I have a PB31IMG.zip file that is 176,626kb with 8 "files" in it. It has andriod-info.txt, hboot_8x50_0.92.0000_100723nb0, radio.img, boot.img, recovery.img system.img splash1.nb0 and nv_MFG_VZW_1.70_0825_PRL58006.img in it. Any idea what the hell this is for? I thought about trying to use it, but I can't even remember what the hell it is. Sad, I know. I should have renamed it so I would know.
Live and learn ......
BuffaloChips said:
I have a PB31IMG.zip file that is 176,626kb with 8 "files" in it. It has andriod-info.txt, hboot_8x50_0.92.0000_100723nb0, radio.img, boot.img, recovery.img system.img splash1.nb0 and nv_MFG_VZW_1.70_0825_PRL58006.img in it. Any idea what the hell this is for? I thought about trying to use it, but I can't even remember what the hell it is. Sad, I know. I should have renamed it so I would know.
Live and learn ......
Click to expand...
Click to collapse
That is an ruu. Not sure which version, but definitley an ruu.
PB31IMG.zip files can be ruu's, radios, splash screens, recoveries, hboots, or a combination of them.
I was trying to install a new rom on my Desire Z, following the directions here, but something went wrong somewhere and now I can't mount /data. I don't want to go any further in the rom installation process, as I'm afraid to brick my phone. The same thing happened to me while upgrading my Windows 6.5 phone (unexpected problem during rom install) and I ended up with a brick (corrupt bootloader).
I have found several threads here discussing the same problem. However, all of them use highly technical language and seem to be advice from experts to other experts. There are a lot of terms I don't understand or only understand partially, like nandroid, parted, hboot, and so on. Everyone assumes too much. Can anyone explain the procedure in terms a novice can understand?
gromky said:
I was trying to install a new rom on my Desire Z, following the directions here, but something went wrong somewhere and now I can't mount /data. I don't want to go any further in the rom installation process, as I'm afraid to brick my phone. The same thing happened to me while upgrading my Windows 6.5 phone (unexpected problem during rom install) and I ended up with a brick (corrupt bootloader).
I have found several threads here discussing the same problem. However, all of them use highly technical language and seem to be advice from experts to other experts. There are a lot of terms I don't understand or only understand partially, like nandroid, parted, hboot, and so on. Everyone assumes too much. Can anyone explain the procedure in terms a novice can understand?
Click to expand...
Click to collapse
"Mount" data to flash a rom? You sure? Looking at the link you provided just says place on sd, wipe, flash. Where exactly are you stuck or am i just missing the obvious.
The /data corruption occurred halfway through the upgrade process. I'm not sure what to do, so I stopped and asked for advice. I kept going the last time I had a problem, and got a bricked phone for my trouble.
The only "data" I see in that guide (Same one I used in fact), is the comment bout doing a "Factory Reset/Wipe Data" which is what it says, says nothing about /data/ partition, just to do a full wipe.
Naturally you do this from recovery, not from within an app or while the phone is still booted into normal usage.
So, wiping the phone will fix everything? And then install cyanogen? Sorry, just want to be totally completely sure.
Aye, indeeed, as KB said, full wipe, then flash new rom.
OK, thanks! I was just reeeealy nervous about the "wipe the phone" part. My phone still sort of works now, most programs not available, but Google Maps and the telephone still work...the most important parts of the phone as I travel a lot.
gromky said:
OK, thanks! I was just reeeealy nervous about the "wipe the phone" part. My phone still sort of works now, most programs not available, but Google Maps and the telephone still work...the most important parts of the phone as I travel a lot.
Click to expand...
Click to collapse
Factory Reset/Wipe will only clear the internal partitions ( /system /data /cache ) , and additionally if you choose Dalvik Cache, then that as well is usually good to do with a brand new rom.
It will not wipe your radio, hboot, recovery, etc, just the system-related areas for roms.
Generally speaking:
Factory Reset + Wipe Cache/Dalvik Cache
Flash CyanogenMod
Flash the Google Apps Zip specific to that CM version (as CM doesn't come with Google Apps by default)
Reboot
Just remember that doing a backup before doing anything to your phone like above is available, as a factory reset and such will wipe contacts and settings and so forth unless you got a google account setup to restore them (or using something like Titanium Backup on an already rooted phone).
OK, I was following the rooting guide, as that must be done before installing cyanogen. I performed all the steps to "reboot". Md5 #2 & md5 #3 matched. Upon rebooting, I can't use su from the terminal (permission denied). I also tried "cd /sdcard && ./su" and got the same thing. Does this mean the rooting didn't work? Or can I proceed with wiping the device regardless? After I wipe the device I won't be able to perform the rooting steps again...and will likely have a brick...just totally paranoid here.
gromky said:
OK, I was following the rooting guide, as that must be done before installing cyanogen. I performed all the steps to "reboot". Md5 #2 & md5 #3 matched. Upon rebooting, I can't use su from the terminal (permission denied). I also tried "cd /sdcard && ./su" and got the same thing. Does this mean the rooting didn't work? Or can I proceed with wiping the device regardless?
Click to expand...
Click to collapse
I followed that one as well. And I assume you rebooted after that point.
Did you continue forth and factory-reset/wipe and then install CM7 over your stock install?
Basically the downgrading/etc makes the phone exploitable, and then the rooting portion puts you back up to a engineering hboot and such that is unlocked with S-OFF, from there you either flash a pre-rooted ROM (i.e.: CM7 etc), or you root an existing stock (which would have gotten wiped from the hboot replacement).
If you already flashed CM and can't do su via adb then it's possible that under "Security" or "Development" in your phones system memory that su is restricted to "app only" and you may need to change that to "app and adb".
You shouldn't be running su from /sdcard (since that's not a linux style partition, and /sdcard is a no exec area). The su binary should already be installed to system in CM.
Clarification If you did not yet reboot (i.e.: Step #7 and onward), and then wipe/flash cyanogenmod (or another pre-rooted custom rom), then proceed with the steps, otherwise you're just working with a half-processed phone and naturally nothing would work in that state.
kbeezie said:
I followed that one as well. And I assume you rebooted after that point.
Click to expand...
Click to collapse
Yes.
Did you continue forth and factory-reset/wipe and then install CM7 over your stock install?
Click to expand...
Click to collapse
You mean hold "down" and boot into recovery, and immediately do these steps? No, I did not. I let the phone boot as normal, to try to run su to verify if the rooting process worked or not.
I suppose my question should be: how can I verify that the rooting process worked, and I'm ready to wipe? The su on /sdcard was pushed there by adb and used during the procedure. From the guide:
adb push su /sdcard/
adb push Superuser.apk /sdcard/
Basically the downgrading/etc makes the phone exploitable, and then the rooting portion puts you back up to a engineering hboot and such that is unlocked with S-OFF, from there you either flash a pre-rooted ROM (i.e.: CM7 etc), or you root an existing stock (which would have gotten wiped from the hboot replacement).
Click to expand...
Click to collapse
I didn't downgrade, I still have my stock rom (phone bought from Hong Kong so it's one of the Asia roms) which temprooted just fine with visionary.
gromky said:
Yes.
You mean hold "down" and boot into recovery, and immediately do these steps? No, I did not. I let the phone boot as normal, to try to run su to verify if the rooting process worked or not.
I suppose my question should be: how can I verify that the rooting process worked, and I'm ready to wipe? The su on /sdcard was pushed there by adb and used during the procedure. From the guide:
adb push su /sdcard/
adb push Superuser.apk /sdcard/
I didn't downgrade, I still have my stock rom (phone bought from Hong Kong so it's one of the Asia roms) which temprooted just fine with visionary.
Click to expand...
Click to collapse
Don't use Visionary unless for some strange reason your phone came with Froyo (2.2) on it (it's an outdated method, and has a high brick rate). Given that you may have an asian rom etc, I would just go ahead and do a factory reset /wipe via recovery, and flash CM7 or a pre-rooted stock rom found here on the XDA forum for the best result.
I think even one of the AOKP or Adromudus comes with Pinyin input support already if you need it.
It did have Froyo. I have uninstalled visionary per instructions before performing all these steps. But since I only get one shot at rooting correctly, I want to make absolutely positively sure the process worked before I do something irrevocable like wiping the entire phone, only to discover I can't install a new rom because the phone isn't rooted.
I use third-party programs (GO keyboard) for all of my Chinese needs, and they've worked fine so far.
gromky said:
It did have Froyo. I have uninstalled visionary per instructions before performing all these steps. But since I only get one shot at rooting correctly, I want to make absolutely positively sure the process worked before I do something irrevocable like wiping the entire phone, only to discover I can't install a new rom because the phone isn't rooted.
I use third-party programs (GO keyboard) for all of my Chinese needs, and they've worked fine so far.
Click to expand...
Click to collapse
Rooting is at the rom/kernel level. But in order to flash a new custom kernel would need an unlocked bootloader which you already did with S-OFF.
So you would either flash a pre rooted rom like almost everything available via the developer section here (via recovery not hboot) or a stock rom then root that.
If you do everything via recovery you are less likely to accidentally lock/unroot the phone since recovery normally deals with the rom/kernel /cache and not hboot.
Sent from my T-Mobile G2
It worked - thanks! I was so concerned about bricking the thing. The whole process was easy...now that I've done it. Cyanogen came up in Chinese...couldn't figure out how to change it to English for a while. I suppose there's some setting in my phone that tells it to default to Chinese. It also appears to be locking up frequently on my phone - but at least I got the software on there, and now I can play with other mods. Thanks again!
gromky said:
It worked - thanks! I was so concerned about bricking the thing. The whole process was easy...now that I've done it. Cyanogen came up in Chinese...couldn't figure out how to change it to English for a while. I suppose there's some setting in my phone that tells it to default to Chinese. It also appears to be locking up frequently on my phone - but at least I got the software on there, and now I can play with other mods. Thanks again!
Click to expand...
Click to collapse
If I had to make a guess, I would probably say you flashed Cyanogenmod onto the phone WITHOUT first doing a factory-reset/wipe, in which case you probably broke it (hence the language and freezing) by merging cyanogenmod on top of the pre-existing rom.
No, I definitely wiped the phone first. I got a few lockups in cyanogen so I went to install another rom. Now I'm getting "E:error in /cache/recovery/log" and "E:can't open /cache/recovery/log". When I install a new rom, it won't take and boots into cyanogen. It was in a reboot loop for a while but now it has booted into cyanogen again. Sigh. This is what I was afraid of.
Boot into boot and write down everything on that screen (power+volume down) just to check all is well, what is your recovery?
Search out two things (just use search function in g2 xda threads)
1 superwipe+ext4.zip
2 elitemod cm7
Boot into recovery and flash the super wipe like you did the from
Now flash elitemod
Is all well at this point?
Sent from my GT-I9100 using xda premium
Actually the phone seems to be working with cyanogen now. I suspect the internal memory is corrupt somehow, and that's a problem that can't be fixed. I'm going to stop messing with it before I brick it. If any more problems I'll revive the thread. Thanks so much to everyone who helped. I really can't afford a new phone right now and cyanogen seems to have fixed the problems I was having with the stock rom.
gromky said:
Actually the phone seems to be working with cyanogen now. I suspect the internal memory is corrupt somehow, and that's a problem that can't be fixed. I'm going to stop messing with it before I brick it. If any more problems I'll revive the thread. Thanks so much to everyone who helped. I really can't afford a new phone right now and cyanogen seems to have fixed the problems I was having with the stock rom.
Click to expand...
Click to collapse
If the emmc is faulty then it's going to eventually brick itself, and should probably be sent in for warranty if available.
DISCLAIMER: I'm completely lost, so please break things down into bite-size steps or at least expect some follow-up questions on my part. I'm one of those desperate guys who is attempting to just have a working phone tomorrow. Any help will get as many presses of the thank button as I can possible give.
After several hours of plodding and poking and searching I've managed to do some possibly irreparable damage to my htc one v. Whenever I try to boot the phone it starts up with the htc developer red text "development use only" etc etc. I can access the bootloader and recovery thankfully, so I guess there's hope.
I think the source of my troubles is what's addressed by the essential reading at the top of this sub-forum, ie distinguishing between GSM and CDMA. I think (and this is an assumption here) that despite being in the USA on virgin, the fact that I can shove a sd-card in there means it's GSM (correct me if I'm wrong. please). EDIT: It seems that the phone only works with the CDMA version of TWRP, so I guess that might be an indicator.
Info: htc one v, virgin USA, using TWRP 2.3.3.0, attempted to flash Rom using various versions of Paranoid Android
What I've done thus far:
1. Unlocked bootloader
2. Flashed recovery
2.5. Created backup
3. rooted device (I downloaded rootchecker or somesuch app and was able to confirm that I had rooted my device)
4. Wiped cache and dalvik cache (I think that's what it's called).
5. Attempted to do a factory reset (failed).
6. Attempted to flash ROM (failed)
7. Restarted Device (got stuck on dev screen for the first time).
8. Tried recovering using backup created earlier (which just booted me into the dev screen of doom again).
9. Tried partitioning sd card in an attempt to perform a factory reset (wiped everything including backup).
10. Factory Reset failed with a message about not being able to mount /sd-ext.
11. Tried flashing rom again with different version of PA for shiggles (it worked! oh frabjous day!)
12. Rebooted phone only to get stuck on the dev screen again.
Guides I've used/perused/glanced at:
1. http://forum.xda-developers.com/showthread.php?t=2154635
2. http://forum.xda-developers.com/showthread.php?t=1598964
3. http://www.idroidspace.com/jelly-bean-4-2-2-paranoid-android-custom-rom-for-htc-one-v/
4. http://techmell.net/android-tips/ho...paranoid-android-4-1-2-jelly-bean-custom-rom/
5. http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
6. http://www.youtube.com/watch?v=a3pof_WSEEI
I've been at this for nigh on 7 hours and all I have to show for it is a phone I can't use. Help.
Let's try this in order: if you are with Virgin Mobile, it is a CDMA. GSM phones take a sim card, both versions accept an sd card for storage.
Everything looks good until:
#5 The failed warning is due to lack of a SD EXT partition on your sd card. If you didn't re-partition it, you will get that failed warning. No big deal as it is wiping everything else correctly.
#6 You also need to wipe system prior to flashing your new rom.
After flash your new rom, you will need to connect to your pc and boot into bootloader. Make sure it says "Fastboot USB" at the top your phone screen. You have to flash the boot.img for the specific rom you are trying to install. See the rom thread for the correct method.
Check your radio and Hboot version in bootloader. If you have the newer radio (xxx.xxx.928) and Hboot (1.57), you are limited on the roms that will actually work. Check the CDMA development thread for roms that specify OTA compatible.
Good luck. If you have any more questions, feel free to ask.
pedantfool said:
DISCLAIMER: I'm completely lost, so please break things down into bite-size steps or at least expect some follow-up questions on my part. I'm one of those desperate guys who is attempting to just have a working phone tomorrow. Any help will get as many presses of the thank button as I can possible give.
After several hours of plodding and poking and searching I've managed to do some possibly irreparable damage to my htc one v. Whenever I try to boot the phone it starts up with the htc developer red text "development use only" etc etc. I can access the bootloader and recovery thankfully, so I guess there's hope.
I think the source of my troubles is what's addressed by the essential reading at the top of this sub-forum, ie distinguishing between GSM and CDMA. I think (and this is an assumption here) that despite being in the USA on virgin, the fact that I can shove a sd-card in there means it's GSM (correct me if I'm wrong. please). EDIT: It seems that the phone only works with the CDMA version of TWRP, so I guess that might be an indicator.
Info: htc one v, virgin USA, using TWRP 2.3.3.0, attempted to flash Rom using various versions of Paranoid Android
What I've done thus far:
1. Unlocked bootloader
2. Flashed recovery
2.5. Created backup
3. rooted device (I downloaded rootchecker or somesuch app and was able to confirm that I had rooted my device)
4. Wiped cache and dalvik cache (I think that's what it's called).
5. Attempted to do a factory reset (failed).
6. Attempted to flash ROM (failed)
7. Restarted Device (got stuck on dev screen for the first time).
8. Tried recovering using backup created earlier (which just booted me into the dev screen of doom again).
9. Tried partitioning sd card in an attempt to perform a factory reset (wiped everything including backup).
10. Factory Reset failed with a message about not being able to mount /sd-ext.
11. Tried flashing rom again with different version of PA for shiggles (it worked! oh frabjous day!)
12. Rebooted phone only to get stuck on the dev screen again.
Guides I've used/perused/glanced at:
1. http://forum.xda-developers.com/showthread.php?t=2154635
2. http://forum.xda-developers.com/showthread.php?t=1598964
3. http://www.idroidspace.com/jelly-bean-4-2-2-paranoid-android-custom-rom-for-htc-one-v/
4. http://techmell.net/android-tips/ho...paranoid-android-4-1-2-jelly-bean-custom-rom/
5. http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
6. http://www.youtube.com/watch?v=a3pof_WSEEI
I've been at this for nigh on 7 hours and all I have to show for it is a phone I can't use. Help.
Click to expand...
Click to collapse
Which ROM you have flashed?
Did you install boot.IMG according to your ROM?
Sent from my HTC T320e
If you're restoring "stock" sense 4.0 ROM, you need to flash a kernel that will work with it. Try Titanium-KISS or Stock. The stock one should have been kernel should have been backed up, it's labeled boot.IMG in the backup folder. EDIT: Since you are CDMA, you need to flash this kernel in Fastboot to get it to boot: http://forum.xda-developers.com/showthread.php?t=2024758. Be sure you flashed the CDMA ParanoidAndroid as well, and not the GSM one.
followup
FIRST: Just thought of something that might be very important, I only had a version of android 4.0 installed on my phone. Will that make a difference when installing roms intended for later versions of android? If so, I feel like a huge knuckle-dragging fool.
Update: Was able to install and boot using PACman, but ran into a boot-loop.
But to follow up to your questions:
MameTozhio said:
If you're restoring "stock" sense 4.0 ROM, you need to flash a kernel that will work with it. Try Titanium-KISS or Stock. The stock one should have been kernel should have been backed up, it's labeled boot.IMG in the backup folder. EDIT: Since you are CDMA, you need to flash this kernel in Fastboot to get it to boot: http://forum.xda-developers.com/showthread.php?t=2024758. Be sure you flashed the CDMA ParanoidAndroid as well, and not the GSM one.
Click to expand...
Click to collapse
I'll admit I've had a hard time find a definitive version of PA or really any other Rom. I've tried going through their thread here and downloading one of the "stables" (http://goo.im/devs/gannon5197/paranoid/primoc/stables/). I've also used other unofficial versions of PA (http://forum.xda-developers.com/showthread.php?t=1799372). I'm currently downloading PACman to see if that will make any difference.
[email protected]@ said:
Which ROM you have flashed?
Did you install boot.IMG according to your ROM?
Sent from my HTC T320e
Click to expand...
Click to collapse
I did flash my boot.img using the method explained here:
Copy the kernel image (boot.img file you have extracted from zip file of ROM) to folder in which you have kept your fastboot files.
In the same folder, right click while holding shift button and select ‘Open command window here’.
A command window will appear on your screen. In command window type ‘fastboot flash boot boot.img’ and press enter.
On your screen you will get message ’OKAY/Finished’. You have successfully flashed kernel. Now you can disconnect your phone from computer.
http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
riggerman0421 said:
#5 The failed warning is due to lack of a SD EXT partition on your sd card. If you didn't re-partition it, you will get that failed warning. No big deal as it is wiping everything else correctly.
Click to expand...
Click to collapse
I'd like to think I'd partitioned it properly, but I keep getting a "unable to mount sd-ext" or "unable to wipe sd-ext" message when I attempt a factory reset. I've tried formatting the the mini sd and set the file type to FAT32, but to no avail as the errors persist. I know you said not to be too concerned, but I keep failing the system wipe from your next suggestion because of that error.
#6 You also need to wipe system prior to flashing your new rom.
After flash your new rom, you will need to connect to your pc and boot into bootloader. Make sure it says "Fastboot USB" at the top your phone screen. You have to flash the boot.img for the specific rom you are trying to install. See the rom thread for the correct method.
Click to expand...
Click to collapse
Now how important is it that I flash the boot.img after I have flashed the rom? I've been doing it beforehand, but does doing it afterward make a difference?
Check your radio and Hboot version in bootloader. If you have the newer radio (xxx.xxx.928) and Hboot (1.57), you are limited on the roms that will actually work. Check the CDMA development thread for roms that specify OTA compatible.
Click to expand...
Click to collapse
Those both match my radio and bootloader, what does that imply? I'm planning on flashing this rom: http://forum.xda-developers.com/showthread.php?t=1948034
Will that work?
No, it won't. You have the newer updated hboot and radio. That is the source of your boot loops. The only compatible roms at this time are MyOneV, ExtremeSemse, and RhythmicRom. You can also use Cyanprimo, but you'll have flash the boot.img from RhythmicRom.
Now I've downloaded RythmicRom and I'm still stuck in a boot loop. I'm sorry for being a bit thick, but could you link some roms that would be compatible or explain what I need to be looking for?
Version I downloaded: http://forum.xda-developers.com/showthread.php?t=2147407
You'll need to download the 1.2 update, then extract the boot.img from that. The boot.img in the Rom doesn't work with the new update.
So I've been reading up on the issue over here: http://forum.xda-developers.com/showthread.php?t=2018518&page=14
and while I don't claim to understand it all, I believe I get the gist of it.
I also've managed to get RythmicRom working thanks to riggerman. I guess I'll just play the waiting game until someone rolls out a fix or just replace my phone (though that's very much in the long-run).
Once again, thanks to everyone and hopefully this will be the last we see of this mess.
Glad you got it running, and glad I could help.