Related
This assumes you:
- Have the latest FROYO OTA installed 3.70.651.1
- Have some experience working with flashing things in recovery
- Have NOT deleted/uninstalled ANYTHING in /system
- Have defrosted any bloat you froze with Bloat Freezer or Ti Backup Pro
- Have S-OFF (Used Unrevoked Forever or a version of Unrevoked3 that includes Forever)
OK now let us get to it.
1. Go ahead and download the OTA like normal on your phone, but DO NOT install it.
2. Using a file manager copy the OTA zip file from /cache to /sdcard
3. Using Rom Manager, flash Amon RA Recovery 2.3 (Down at the bottom)
4. In Rom Manager, click the Reboot into Recovery button.
5. Select apply zip from SD Card and flash the OTA zip file that you put in /sdcard
--10 Minutes later.....you now have the UNROOTED OTA installed just as if you installed it normally--
6. Download the 2.6.0.1 ClockWorkMod Recovery zip from here and place it in the root of your SD card
7. Under settings > applications > disable FastBoot (re-enable this when you are done with the whole process)
8. Power off and reboot holding Volume down. The bootloader will scan and then will and ask you to press Volume up to install. Reboot.
9. Delete the PC36IMG.zip file from your SD card and place the attachment below in the root of the SD card.
10. Power off and reboot holding Volume down and then select recovery to start CWM recovery.
11. Choose apply zip from sd card. Choose select zip on sd card. You will see the SU file on the list, flash it to root your phone. Reboot.
You should now be rooted and can upgrade the recovery now to whatever style and version you want!
Enjoy! Please click the THANKS button if it worked for you!
----------------------------------------
Developer of Bloat Freezer - Freeze Your Pre Installed System Apps in One Click
Bloat Freezer - Android Market Link
Very cool!!
Great info ..hey if I follow these steps and skip the last part will my phone be stock / uprooted and good to go.for a trade in or repair? I've been trying to figure out the best way to unrest when.e3d comes out
I never updated to 3.70. I'm assuming I can do that the same way, root again, download the gingerbread, and root again?
I'm thinking it might just be easier to flash the rooted ROM and radios, but I'm not sure what's best.
if you have amon ra recovery (and a stock rom), you can simply download and click install.
I clicked install, amonra booted up, detected and ran update, click reboot, then the stock recovery will be active and updates the radios, once back in to sense, you can reinstall amonra or clockwork, then SU
worked for me.
http://forum.xda-developers.com/showthread.php?t=1109230
im curious why the title says "WITHOUT flashing a new ROM" yet you are clearly flashing the rom in amon ra. sorry just got to nit pick
what happens if you have deleted some system apps. Such as nova and blockbuster. I saved the APKS on the SD card however but I did delete them?
JMQUINT00 said:
what happens if you have deleted some system apps. Such as nova and blockbuster. I saved the APKS on the SD card however but I did delete them?
Click to expand...
Click to collapse
Well I wouldn't want to try it unless your prepared to do a full ruu reset if it fails.
the OTA is like a patcher, it deletes unneeded files, adds new files, and updates existing files... if its not completely stock it may (or may not) cause an error which the updater can't handle, and then you may be left with a half upgraded system.
if you nandroid *before* downloading the ota, you should always be able to go back, assuming you have perm soff from unrevoked forever.
it should run whether you have removed files or not. if it tries to delete a file that does not exist the script will just skip it. op i think you have bit of confusion going on though. you were only able to reattain root because you are s-off from unrevoked forever. if you are not s-off and do your method, which is no different then just excepting the ota and letting it do its thing btw, you will loose root until this new ota is cracked. just fwi, there was no "magic" from you flashing manually, the same script is ran and the same files are moved and patches are made regardless.
cant I reinstall the apps and put the apks in their original system folder?
DomSim said:
it should run whether you have removed files or not. if it tries to delete a file that does not exist the script will just skip it. op i think you have bit of confusion going on though. you were only able to reattain root because you are s-off from unrevoked forever. if you are not s-off and do your method, which is no different then just excepting the ota and letting it do its thing btw, you will loose root until this new ota is cracked. just fwi, there was no "magic" from you flashing manually, the same script is ran and the same files are moved and patches are made regardless.
Click to expand...
Click to collapse
Lol OK so which one is it? Can n just accept the ota and run? I'm rooted on stock rom, but I deleted nova and blockbuster from the system? I know I will loose root which I got by using unrevoked 3, but I just want to know if I can do it without bricking the phone. Ty
JMQUINT00 said:
Lol OK so which one is it? Can n just accept the ota and run? I'm rooted on stock rom, but I deleted nova and blockbuster from the system? I know I will loose root which I got by using unrevoked 3, but I just want to know if I can do it without bricking the phone. Ty
Click to expand...
Click to collapse
shouldn't be any worry about bricking but make 100% sure you are s-off from unrevoked forever and you should be able to re-root pretty much how the op outlined.
im currently running cm7. if i go back to a rooted stock froyo rom, will this work???
confused. I just don't understand why you wouldn't download the rooted version of the ROM from here on XDA and just flash it like a normal rom. Maybe I'm overtired and missing the point.
To me, its like this. If you're rooted, and want an OTA update, just wait for the devs at XDA to go through it and root it, and make it available for download. Then just download it and flash it. You get the same exact update that way, as if you took the OTA from sprint. Except this way you don't risk losing root, and your good to go.
If you're not rooted and your phone is stock, accept OTA like normal.
I don't understand why all this extra stuff needs to be done, and add more to the confusion. If your rooted, updating to the latest is simple. Download it and flash it in recovery.
DaEXfactoR said:
im currently running cm7. if i go back to a rooted stock froyo rom, will this work???
Click to expand...
Click to collapse
Just download the update from here http://forum.xda-developers.com/showthread.php?t=1038701
Do a full wipe and flash like any other rom you've ever flashed before. You'll then be on the latest and greatest . (you'll probably be going right back to CM)
EDIT: and to the OP, sorry that I don't agree with you. I just find it more confusing that way, and I guess that whatever the point of doing it that way is, is sailing miles above my head.
k2buckley said:
confused. I just don't understand why you wouldn't download the rooted version of the ROM from here on XDA and just flash it like a normal rom. Maybe I'm overtired and missing the point.
To me, its like this. If you're rooted, and want an OTA update, just wait for the devs at XDA to go through it and root it, and make it available for download. Then just download it and flash it. You get the same exact update that way, as if you took the OTA from sprint. Except this way you don't risk losing root, and your good to go.
If you're not rooted and your phone is stock, accept OTA like normal.
I don't understand why all this extra stuff needs to be done, and add more to the confusion. If your rooted, updating to the latest is simple. Download it and flash it in recovery.
Click to expand...
Click to collapse
I see your point. I guess I am anxious. So there will be a stock ROM that is rooted, thats what I was wondering. I wasnt sure if every ROM would be customized somewhat...Thanks
DaEXfactoR said:
I see your point. I guess I am anxious. So there will be a stock ROM that is rooted, thats what I was wondering. I wasnt sure if every ROM would be customized somewhat...Thanks
Click to expand...
Click to collapse
That link I supplied a couple posts up is a completely 100% stock and rooted version of the OTA update.
This is from the first paragraph of the first post of that thread.
"Stock 4.22.651.2 ROM, rooted and ready for your flashing pleasures. This is a completely stock ROM that has had nothing done to it outside of rooting & deodexing, it's not even zip aligned yet (sorry DrMacinyasha)
As always make sure your wipe your dalvik and create a nandroid before flashing."
k2buckley said:
That link I supplied a couple posts up is a completely 100% stock and rooted version of the OTA update.
This is from the first paragraph of the first post of that thread.
"Stock 4.22.651.2 ROM, rooted and ready for your flashing pleasures. This is a completely stock ROM that has had nothing done to it outside of rooting & deodexing, it's not even zip aligned yet (sorry DrMacinyasha)
As always make sure your wipe your dalvik and create a nandroid before flashing."
Click to expand...
Click to collapse
thanks for your insight. only thing I am confused on at this point is why there are kernels listed to flash from May just below it? wouldnt the htc stock kernel from the ota be in this rom already? seems like alot of folks are looking for newer kernels to flash after flashing xhaus rom. Any insight would be great. thanks again!
rileyd5 said:
thanks for your insight. only thing I am confused on at this point is why there are kernels listed to flash from May just below it? wouldnt the htc stock kernel from the ota be in this rom already? seems like alot of folks are looking for newer kernels to flash after flashing xhaus rom. Any insight would be great. thanks again!
Click to expand...
Click to collapse
I was a little curious about why those kernels were linked there too. I honestly haven't really kept up with thread, because I don't have an interest in flashing the update to begin with. I noticed those kernels are from May 4th, so it doesn't seem like they'd be the most current one. Without reading that thread, I first would've presumed that the kernel that comes with the rom would be the one to use. So, you've read through the thread and you're seeing that people are having trouble with the kernel that the rom comes with?? I'll take a gander over in the thread in a few minutes and see what I make out of it.
Well I f'd up and installed the latest update straight from sprint, instead of waiting for the rooted version to come out. I guess I thought I would find something exciting, but now I would realize it was kind of worthless and want to go back to a different rom like miui or vaelpak. I am s-off with unrevoked. Is there some combination of the steps listed I can use to back out of this?
Let me take a guess...did this update my radios and hboot to a version that would be incompatible with these roms?
So, I had some trouble unrooting my Evo 4G today because I wanted to bring my phone in for a replacement. It's been awhile since I last rooted the device so I figured I could just download the appropriate zip files and get on with it. I ran into a few snags.
A little background of the phone:
-Rooted via Unrevoked 3
-Running the latest Radio 2.15.00.05.02
-S-OFF
So, this method works if you rooted your phone via Unrevoked3 or Unrevoked Forever. I was reading all over and many people flashed to sense ROMs and did many steps that weren't really needed. The way I did was very simple.
**If you did not root your phone via Unrevoked skip to Step 7.
1. Downgrade your Radio to 2.15.00.07.28 (Anything earlier than the previous update should work) at http://forum.xda-developers.com/showthread.php?t=7154 All the radios should be located at the previous link.
2. Download the Unrevoked Forever S-ON zip file that is provided.
3. Move the S-ON zip file to the root of your SD card.
4. Flash the zip file so that your device now reads S-ON, NOT S-OFF.
5. Wipe Cache, Dalvik Cache, and Data.
6. Reboot into Bootloader and verify that you are now S-ON.
7. Download the PC36IMG.zip from http://www.4shared.com/file/5U4M4eVi/PC36IMG.html?cau2=403tNull
8. Move the PC36IMG zip file to the root of your SD card.
9. Reboot into Bootloader and the phone should recognize the PC36IMG and begin to finish the UNROOT process.
10. Follow on-screen instructions and apply the update and reboot the phone.
11. You are now UNROOTED!!!
I hope this little tutorial helped. It definitely is nice to finally unroot the device after all the problems I was running into.
NOW sticky it. lol
Does this enable S-On ?
nyc_zx10 said:
Does this enable S-On ?
Click to expand...
Click to collapse
Step six...
Unroot for repair
Just in case anyone doing this for the first time, I recently took my evo in and exchanged for another. Make sure you remove all evidence of root from your sd card i.e. root explorer, my back up root TI(any root programs) and get the pc36img off there too. Now depending how cool your Sprint techs are they might not care. My particular store said they would blacklist my phone if they suspected it of root. That will ruin your plans of getting any service in the future, let alone the reason you came in. Their little "diagnostics" term to me says,"Let me check if I am going to dash your hopes of repair today." Or to be safer you could just pull the sd. Hopefully if you do forget you have cool techs that appreciate what we do here.
Just a heads up, the radio link is broken. I've been using the same one as well in my bookmarks. That thread is apparently no longer there?
when i try to flash the radio is comes up with a message saying something about "it was necessary to remove it when upgrading to the CWM 3.0 gingerbread based recovery, please switch to edify scripting" do i have to downgrade my CWM?
I'll give this process a 7 on the pucker scale, but it does work
I downgraded my cm image before I started just so I wouldn't have to deal with any errors
I then flashed the 2.15.00.07.28 radio
then flashed the s-on tool
then applied the pc36img.zip in bootloader
took a while but I am back up, and running unrooted
[email protected] said:
All this does is change S-OFF to S-ON. I still have SuperUser and can still run root apps with ease. I assume this hack is just for taking the phone in?
Click to expand...
Click to collapse
Actually, after flashing the PC36IMG, that removes the root and puts the phone back to the initial state. It does put the phone to S-ON and remove SuperUser.
tkdkicker04 said:
Actually, after flashing the PC36IMG, that removes the root and puts the phone back to the initial state. It does put the phone to S-ON and remove SuperUser.
Click to expand...
Click to collapse
If you do take it in do not let them update anything. I even signed a paper saying I didn't want a hard reset.
Sent from my PG86100 using XDA Premium App
Will this wipe all my contacts, messages, and apps? What app should I use to back everything up (Mybackup Pro, or Titanium Backup)?
Yes you will lose everything. Google should save your contacts to the cloud. Any installed apps can be redownloaded. You will lose any saved messages/text/etc.
Keep in mind "S-OFF" and having root privileges are two different things. You can be rooted and be S-ON, and S-OFF and not rooted (which would mean you flashed a ROM that didn't have the su binary which almost doesn't exist outside of stock).
Why is it necessary to downgrade the radio? Just curious. Mine is currently running 2.15.00.11.19.
Question two... is that PC36IMG linked the stock 2.3.3?
Here is the post containing the Radios and more...
[ Radios ][ 7-4 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions
For anyone having trouble flashing the Radios using ClockworkMod either:
1) Downgrade your CWM to 2.5.0.7 (within ROM Manager)
or
2) Using ROM Manager (or manually) Flash Alternative [Recovery] [09-Feb-2011] RA-supersonic-v2.3
To be able to use CWM nandroids in Amon_RA's Recovery you need to:
1) Make a folder on the root of your SD Card called Nandroid
2) Create a Nandroid using Amon_RA
3) Amon_RA will create another folder inside Nandroid
4) Place your nandroid that you made in CMW inside the folder that Amon_RA creates along with that nandroid too
Hope this helps people... If in fact it does please leave a thanks
Warning warning warning proceed at own risk etc etc
I used these instructions but in a different way.
1) I downgraded the radio. I still don't know why, it wasn't stated, but I went ahead and did it.
2) I downloaded the new radio and the unrevoked s-on tool (since I used unrevoked to root this phone in the first place)
3) I copied both the radio and s-on to my sd card while Evo was plugged into my PC via Disk Storage
4) On Amon's 2.3 recovery, I flashed the radio, let it do its thing and reboot and do its next lil thing it wants to do
5) Flashed the s-on. After it was done, I went back to the main menu of Amon's recovery and selected power off
6) Holding VOL+D and power, booted into the bootloader and saw it was S-ON.
7) Went through hboot to boot into recovery, then power off
8) Pulled battery to get to the sd card and put it into my PC so I could copy the PC36IMG.zip to it. Im really not convinced that its a big deal to copy this zip along with the radio and unrevoked s-on tool at the same time, except that it might idiot-proof flashing the pc36img prematurely. Then again, the instructions state to move it to the sd card...how? It can be done over ADB but theres not instructions given.
9) Put Sd card with PC36img copied to it onto the Evo, held VOL+D and power, booted into bootloader, it found PC36img, applied update and rebooted.
The linked PC36img is to android 2.2, on which im now unrooted.
cabbieBot said:
Warning warning warning proceed at own risk etc etc
I used these instructions but in a different way.
1) I downgraded the radio. I still don't know why, it wasn't stated, but I went ahead and did it.
2) I downloaded the new radio and the unrevoked s-on tool (since I used unrevoked to root this phone in the first place)
Click to expand...
Click to collapse
I think that the reason why you need an older radio is because if they saw that you had the newest radio released w/ the 2.3.3 and your on 2.2 it might look a little funny... this is my educated guess
.torrented said:
I think that the reason why you need an older radio is because if they saw that you had the newest radio released w/ the 2.3.3 and your on 2.2 it might look a little funny... this is my educated guess
Click to expand...
Click to collapse
that makes sense. so there isnt a 2.3.3 image to flash? or is there a reason to not want to do it if there it is?
cabbieBot said:
that makes sense. so there isnt a 2.3.3 image to flash? or is there a reason to not want to do it if there it is?
Click to expand...
Click to collapse
well when sprint released the latest OTA its a packaged deal you get all of the stuff (radio hboot PRI/NV ect.) well if you only have 1 of the many different things like the latest radio but not the latest hboot or w/e then i would assume that the phone has been rooted. so you wouldnt want the 4.24 software update and have all of the older firmware... im really not too sure and i could be wrong but this would seem pretty logic (to me)
oh and flashing the 2.3.3 image would render it unrootable
cabbieBot said:
Warning warning warning proceed at own risk etc etc
I used these instructions but in a different way.
1) I downgraded the radio. I still don't know why, it wasn't stated, but I went ahead and did it.
2) I downloaded the new radio and the unrevoked s-on tool (since I used unrevoked to root this phone in the first place)
3) I copied both the radio and s-on to my sd card while Evo was plugged into my PC via Disk Storage
4) On Amon's 2.3 recovery, I flashed the radio, let it do its thing and reboot and do its next lil thing it wants to do
5) Flashed the s-on. After it was done, I went back to the main menu of Amon's recovery and selected power off
6) Holding VOL+D and power, booted into the bootloader and saw it was S-ON.
7) Went through hboot to boot into recovery, then power off
8) Pulled battery to get to the sd card and put it into my PC so I could copy the PC36IMG.zip to it. Im really not convinced that its a big deal to copy this zip along with the radio and unrevoked s-on tool at the same time, except that it might idiot-proof flashing the pc36img prematurely. Then again, the instructions state to move it to the sd card...how? It can be done over ADB but theres not instructions given.
9) Put Sd card with PC36img copied to it onto the Evo, held VOL+D and power, booted into bootloader, it found PC36img, applied update and rebooted.
The linked PC36img is to android 2.2, on which im now unrooted.
Click to expand...
Click to collapse
To answer your first question, after doing my research and by trial and error, I ran into several errors and problems having the latest radios and HBOOT. The alternative to fix this problem was to downgrade the radio.
The reason why it's easier to move the PC36IMG after you are S-ON is to make sure that you do not make the mistake of updating prematurely. Mistakes can happen and if you move too fast, accidents may happen. This was done to insure that needless accidents don't happen. The way you move the file to the SD card is by enabling USB mode while in recovery mode (Amon RA and Clockwork). The disk drive appears on your computer, and you click and drag the files just like normal.
The PC36IMG contains Android 2.2
.torrented said:
Here is the post containing the Radios and more...
[ Radios ][ 7-4 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions
For anyone having trouble flashing the Radios using ClockworkMod either:
1) Downgrade your CWM to 2.5.0.7 (within ROM Manager)
or
2) Using ROM Manager (or manually) Flash Alternative [Recovery] [09-Feb-2011] RA-supersonic-v2.3
To be able to use CWM nandroids in Amon_RA's Recovery you need to:
1) Make a folder on the root of your SD Card called Nandroid
2) Create a Nandroid using Amon_RA
3) Amon_RA will create another folder inside Nandroid
4) Place your nandroid that you made in CMW inside the folder that Amon_RA creates along with that nandroid too
Hope this helps people... If in fact it does please leave a thanks
Click to expand...
Click to collapse
Thanks for this man. I was having trouble finding a working link.
I just manually checked for software updates and got the new 2.11.605.5 OTA, and am installing now. I'm not sure when VZW might push it out to devices, but it should be available for stock users going through the Settings > Software Update option. I was on the pulled GB release prior to this.
Downloading now... is this just a radio or something else too?
http://support.verizonwireless.com/pdf/system_update/thunderbolt.pdf
If you're stock, then yet, its a radio and the gingerbread update, if you're not stock (don't install it here, install a rooted), its the same radio as the .3 leak.
Okay, I think my phone is messed up now, I had a HBOOT on it and the update seem to be stuck on that sad picture with blue droid and exclamation mark...
Were you rooted before? And if so, revolutionary method, or downgrade method?
nbdysreal said:
Were you rooted before? And if so, revolutionary method, or downgrade method?
Click to expand...
Click to collapse
Revolutionary... I can still boot into HBOOT or Recovery or normally, just the update is not... updating
Sob.. sob.. I want my Gingerbread... sob..
No problems. Calm down! haha. Download a ROOTED 605.5 update from here on the forum. You'll probably have to do all of the normal wipes, meaning lose data. Cache and dalvik definitely have to wipe. Install from recovery. Profit. Don't forget that depending on what you are coming off of, you will have to have a gingerbread capable radio. MR2+. That will you put on the root of your sd card and install through hboot.
nbdysreal said:
No problems. Calm down! haha. Download a ROOTED 605.5 update from here on the forum. You'll probably have to do all of the normal wipes, meaning lose data. Cache and dalvik definitely have to wipe. Install from recovery. Profit. Don't forget that depending on what you are coming off of, you will have to have a gingerbread capable radio. MR2+. That will you put on the root of your sd card and install through hboot.
Click to expand...
Click to collapse
As someone else has just pointed out in my other thread in Q&A - I still have a Froyo radio which, in most cases, will be incompatible with GB. SO which radio should I have there? Obviously, Verizon is updating both radio and ROM, so is there an extracted radio that goes with rooted 605.5 ?
Straight from the vz support doc "Baseband: 1.48.00.0906w_1, 0.01.78.0906w_2"
Here is the link from Android Police for the radio http://lts.cr/xRR
Gingerbread 2.11.605.3 Radio (MD5: b1e10920c1f191561fd05f1e9c445482)
Again, the 605.3 is the same radio as the 605.5, so there ya go! I generally flash before my rom flashing, but you can before or after. Radio through hboot, room through recovery. Good luck.
I backed out of update
Let me know whats broken
Sent from my ADR6400L using xda premium
nbdysreal said:
Straight from the vz support doc "Baseband: 1.48.00.0906w_1, 0.01.78.0906w_2"
Here is the link from Android Police for the radio
Gingerbread 2.11.605.3 Radio (MD5: b1e10920c1f191561fd05f1e9c445482)
Again, the 605.3 is the same radio as the 605.5, so there ya go! I generally flash before my rom flashing, but you can before or after. Radio through hboot, room through recovery. Good luck.
Click to expand...
Click to collapse
This may be a stupid question, but since I can't access the phone's home screen, ihow do I get the zip onto the phone's SD card so I can flash it from CWR?
Fastlivin said:
This may be a stupid question, but since I can't access the phone's home screen, ihow do I get the zip onto the phone's SD card so I can flash it from CWR?
Click to expand...
Click to collapse
a card reader is probably your best bet. or another phone, if you have access to one you could put your sd in it and place the file then put it back in your TB.
Pender1 said:
a card reader is probably your best bet. or another phone, if you have access to one you could put your sd in it and place the file then put it back in your TB.
Click to expand...
Click to collapse
Actually, turns out I was able to accidentally solve the problem by wiping a bunch of stuff in ClockworkMod recovery.
http://forum.xda-developers.com/showpost.php?p=18794700&postcount=15
nbdysreal said:
No problems. Calm down! haha. Download a ROOTED 605.5 update from here on the forum. You'll probably have to do all of the normal wipes, meaning lose data. Cache and dalvik definitely have to wipe. Install from recovery. Profit. Don't forget that depending on what you are coming off of, you will have to have a gingerbread capable radio. MR2+. That will you put on the root of your sd card and install through hboot.
Click to expand...
Click to collapse
I have rooted via Revolutionary. Running stock Froyo. So I downloaded the latest rooted stock (Gingerbread 605.5), renamed it to PG05IMG.zip and copied it to SD root directory. Booted into bootloader with Power/Vol-DN, and it picked up that file, and started decompressing it. Then it was over, and I am on the screen where I can go to fastboot, recovery, etc. So I go to fastboot and rebooted. I am still on Froyo, so the update to Gingerbread did not happen.
Any idea what went wrong? Does rooted via Revolutionary prevent updating the rooted stock Gingerbread update? Do I need to unroot, and go the OTA update route? TIA.
Fastlivin said:
Actually, turns out I was able to accidentally solve the problem by wiping a bunch of stuff in ClockworkMod recovery.
http://forum.xda-developers.com/showpost.php?p=18794700&postcount=15
Click to expand...
Click to collapse
glad it worked out
to explain what you did:
MattBeyers said:
Dalvik: 1. (n.) A virtual machine designed by Google for use in the Android operating system. Sometimes shortened to DVM or DalvikVM. 2. (n.) Dalvik [Cache]: A cache of small .dex files which are used to quickly and efficiently load applications. Basically, when Android starts up, the DalvikVM scans through all of your applications (files with .apk extensions) and application framework. It then optimizes the bytecode (tiny code commonly used for efficient software execution) for each application into a .dex file and stores that file in the Dalvik Cache. The applications are then run using the .dex file (optimized bytecode). By doing this, Android is able to speed up to execution of applications by loading them from smaller .dex files instead of larger .apk files. This is why when you install a new ROM, it takes longer to boot for the first time (because the DalvikVM is scanning and optimizing each application/framework). Every time an application (or framework library) changes or is installed, it’s re-optimized into a .dex file and the cache is updated.
1u. Dalvik is named after a fishing village in Iceland.
2u. Many custom ROMs give you the ability to clear your Dalvik cache at any time.
Click to expand...
Click to collapse
terms found here: http://forum.xda-developers.com/showthread.php?t=1143188
chungylau said:
I have rooted via Revolutionary. Running stock Froyo. So I downloaded the latest rooted stock (Gingerbread 605.5), renamed it to PG05IMG.zip and copied it to SD root directory. Booted into bootloader with Power/Vol-DN, and it picked up that file, and started decompressing it. Then it was over, and I am on the screen where I can go to fastboot, recovery, etc. So I go to fastboot and rebooted. I am still on Froyo, so the update to Gingerbread did not happen.
Any idea what went wrong? Does rooted via Revolutionary prevent updating the rooted stock Gingerbread update? Do I need to unroot, and go the OTA update route? TIA.
Click to expand...
Click to collapse
If you're updating using the rooted version, it has to be done in recovery, not hboot. You will do the radio in hboot.
Sent from my ADR6400L using XDA App
nbdysreal said:
If you're updating using the rooted version, it has to be done in recovery, not hboot. You will do the radio in hboot.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Got it, thanks!
Pender1 said:
glad it worked out
to explain what you did:
terms found here: http://forum.xda-developers.com/showthread.php?t=1143188
Click to expand...
Click to collapse
The dictionary clears up so much. Thank you.
Hi all,
I have a problem with my Sensation due to my own fault.
I want to flash ARHD ICS rom to my phone, and I started with rooting my Sensation. I followed all instruction til installing the Recovery (PG58IMG).
I downloaded two versions of PG58IMG (one for ICS and one for the other), but I copied the firmware for ICS version to my SD card and already installed it. Now, my phone already S-off but cannot reboot into homescreen. It keeps rebooting it self in white hTC screen (after I installed the ICS firmware).
I don't know how to fix. I tried to read the troubleshoot in the post but I still cannot fix it. Does anyone have a solution??
Thanks in advance
chuz said:
Hi all,
I have a problem with my Sensation due to my own fault.
I want to flash ARHD ICS rom to my phone, and I started with rooting my Sensation. I followed all instruction til installing the Recovery (PG58IMG).
I downloaded two versions of PG58IMG (one for ICS and one for the other), but I copied the firmware for ICS version to my SD card and already installed it. Now, my phone already S-off but cannot reboot into homescreen. It keeps rebooting it self in white hTC screen (after I installed the ICS firmware).
I don't know how to fix. I tried to read the troubleshoot in the post but I still cannot fix it. Does anyone have a solution??
Thanks in advance
Click to expand...
Click to collapse
If I understand you correctly you flashed the firmware upgrade BEFORE you flashed the new ICS rom? If so you'll need to get your sdcard card out (and get your computer to read it) so you can rename the PG85img on your sdcard so you can get back into recovery so you can flash the new ICS rom.
runderekrun said:
If I understand you correctly you flashed the firmware upgrade BEFORE you flashed the new ICS rom? If so you'll need to get your sdcard card out (and get your computer to read it) so you can rename the PG85img on your sdcard so you can get back into recovery so you can flash the new ICS rom.
Click to expand...
Click to collapse
Yes, I flashed the upgraded firmware before not only I flashed ICS rom, but also I get rooted. Now, I can't flash any rom as well as su-2.3.6.1-ef-signed.zip or su-2.3.6.3-efgh-signed.zip.
It still keep bootlooping. I tried to flash the other firmware, but it showed 'CID incorrect'. I don't know how to fix now
Did you check MD5 Sums before you flashed the ROM because it sounds like a bad download so re-download the ROM and reflash
Jonny said:
Did you check MD5 Sums before you flashed the ROM because it sounds like a bad download so re-download the ROM and reflash
Click to expand...
Click to collapse
I did check MD5 sums for all files I downloaded and it is corrected.
Now, I'm curious that whether it is possible to flash the upgraded firmware before being rooted.
And of course you need to be using the right version of the firmware for the rom you want to flash. Mike's latest uses 3.24 per here. http://forum.xda-developers.com/showthread.php?t=1459767
I don't know if you can get into fastboot or not, but you should be able to check the CID of your phone there, and download the right firmware for your phone. If your phone is carrier independent (i.e. didn't get on contract) then the HTC__xxx variety should be good.
airzone said:
And of course you need to be using the right version of the firmware for the rom you want to flash. Mike's latest uses 3.24 per here. http://forum.xda-developers.com/showthread.php?t=1459767
I don't know if you can get into fastboot or not, but you should be able to check the CID of your phone there, and download the right firmware for your phone. If your phone is carrier independent (i.e. didn't get on contract) then the HTC__xxx variety should be good.
Click to expand...
Click to collapse
Thank you so much for your link. I can boot my Sensation into the homescreen now. For my problem, I have to download and flash the older version (3.17) to fix it.
Thanks all of you for your reply again.
+1 for me, solve with a new download .
Just flash the Mod, the bootloop is normal.
I got the same problem, before i flashed Revolution Rom i used that radio package. After the radio package flash, my phone wass stuck in a bootloop.
I took the memory card out en removed the zip file en flashed the revolution rom. After that my phone started normal.
SOrry for the bad enlgish.
Good luck mate.
hey, guys i just had the same problem, kinda. lol
anyways my phone is rooted, s-off and superCID
when i went to install the new ics rom i did everything this thread http://forum.xda-developers.com/showthread.php?t=1459767
said to do and when the new root booted up for the first time, it would go up to the beats audio logo,( the ics rom with beats audio (xe)) then like restart back to the htc startup logo, then beats again then htc again, it just kept doing this..??
so i just deleated everything and restored back to origional backup rom.
so what did i do wrong?
a bad download link/file? can u give me a good one?
thanks, any help is greatly appreciated as iam totally lost right now...
edit:
also do i even need this file (PG58IMG.zip.) to flash the ics rom if my phone is superCID ??? iam confused on that part.
nevermind, figured it out and got it work! the new ics is pretty sweet!!
thanks for everything- towards all the developers and testers on here
Cool. The answer is yes of course. The firmware file contains a specific radio / hboot / etc version. The ROM you download and install is dependent on certain combinations of the firmware versions you have. The super cid just allows you to flash any of the firmwares available here... Otherwise you have to find the specific one for your region and/or carrier.
Also, don't forget you can use an adb logcat while your phone is booting to see if you can diagnose any boot-looping issues. Just run that command on your PC with your phone attached via USB cable
Kawirider594 said:
hey, guys i just had the same problem, kinda. lol
anyways my phone is rooted, s-off and superCID
when i went to install the new ics rom i did everything this thread http://forum.xda-developers.com/showthread.php?t=1459767
said to do and when the new root booted up for the first time, it would go up to the beats audio logo,( the ics rom with beats audio (xe)) then like restart back to the htc startup logo, then beats again then htc again, it just kept doing this..??
so i just deleated everything and restored back to origional backup rom.
so what did i do wrong?
a bad download link/file? can u give me a good one?
thanks, any help is greatly appreciated as iam totally lost right now...
edit:
also do i even need this file (PG58IMG.zip.) to flash the ics rom if my phone is superCID ??? iam confused on that part.
Click to expand...
Click to collapse
To do so,
1. Download the correct firmware version ( PG58IMG.zip V3.24 ) and copy it to the root of your SDCARD.
Be 200% sure that the downloaded zip file is not corrupted. ( Check the MD5 checksum after you download)
2. Pull Back the battery and wait for a minute.
3. Put the battery and press POWER+VOLUME Down Key together.
4. Your phone will detect the firmware.
5. Follow the screen and complete the flashing.
6. Download the ICS based ROM of your favor.
7. Boot into recovery and flash your rom.
Kawirider594 said:
hey, guys i just had the same problem, kinda. lol
anyways my phone is rooted, s-off and superCID
when i went to install the new ics rom i did everything this thread http://forum.xda-developers.com/showthread.php?t=1459767
said to do and when the new root booted up for the first time, it would go up to the beats audio logo,( the ics rom with beats audio (xe)) then like restart back to the htc startup logo, then beats again then htc again, it just kept doing this..??
so i just deleated everything and restored back to origional backup rom.
so what did i do wrong?
a bad download link/file? can u give me a good one?
thanks, any help is greatly appreciated as iam totally lost right now...
edit:
also do i even need this file (PG58IMG.zip.) to flash the ics rom if my phone is superCID ??? iam confused on that part.
Click to expand...
Click to collapse
No you didn't do everything the thread said to do because you're stuck in a bootloop. And yes, you must have correct firmware to run any ICS ROM.
1. SuperCID.
2. Load correct firmware for ROM version you wish to flash (there are 3 different firmwares, 3.06, 3.12 and 3.24. Make sure you've got the right one.
Put PG58IMG.zip on the root of your damn SD card.
Put the ROM you want on the root of your damn SD card.
Put a wipe or superwipe script on the root of your damn SD card.
So far it's easy, no?
Boot to bootloader, select FASTBOOT, select yes to update.
Watch the phone. You should see it flash some partitions, reboot itself, then flash the radio and some other crap.
When done you should be at correct HBOOT and radio.
Now, pull the battery. Pull the SD card.
Insert the battery. Start the phone with power + Volume down.
Move cursor to recovery.
Insert SD card and select recovery.
Flash the wipe script, flash the ROM.
Now if you did everything exactly like this, you will boot to normal phone in about 10 minutes or so.
This has been spelled out 50 times in 50 threads, including threads devoted to nothing but this procedure.
Your phone is a machine. It can only do what you tell it to do. If you screw up, it's screwed up. If you do everything exactly right, in the right order, carefully checking each step, your phone will behave.
Try again.
Do it right. Do it carefully.
P.
I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
fashofasho said:
I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
Click to expand...
Click to collapse
when you did S-OFF in order to install Cyanogen JB first you had to flash the latest fw version and then the rom
the rom you tried to install requires the latest fw version
now are you still s-off?
what is now your hboot version?
what is your fw version?
I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
Click to expand...
Click to collapse
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
Skipjacks said:
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
Click to expand...
Click to collapse
i got confused
.i think your answer is going for fashofasho
Skipjacks said:
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
Click to expand...
Click to collapse
Thanks for the reply. Okay so here is where I am currently at. I haven't done anything since I reflashed stock ROM throguh RUU after the fail cyanogen flash. On this stock ROM whenever I load into bootloader it still says s-off 1.17 but I did lose my clockworkmod. So according to your instructions I should either clockworkmod again or 4ext now, that's okay right? If so, going to flash firmware then cyanogen!! Or is there a problem that I have s-off but not recovery.
P.s. there is no point in running revolutionary and have it s-off again when I already have it right, just thought it might be necessary to make things fresh
If you have a bootable phone right now this is easy as you may not need adb or fast boot or anything.
First off you will need to install 4ext. Get the app from the Play Store. Then run it and let it install its recovery module. (You may need to be rooted to do thus, which your stock rom is not. Im not sure if you can flash the recovery without root or not because Ive never tried without root. If so, then you will have to install Superuser via fastboot I think. You any guide for rooting to get instructions on this. Its easy.)
You may also find a way to install 4ext recovery via flashing from bootloader, but you will have to search for that. You MAY even be able to install it with the firmware upgrade. You will have to see if that is an available option.
Get your firmware from this thread...
forum.xda-developers.com/showthread.php?t=1459767
Follow the instructions to update. Once you have 3.3x firmware and 4ext simply boot to recovery, do a full wipe, and flash cm10 (make sure cm10 is on your sd card. You can download it from your currently working gingerbread rom so you have it available)
You have like 15-20 minutes worth of work to do, so its not a monumental obstacle to overcome. It just seems like alot
Sent from my HTC Sensation using xda app-developers app
Skipjacks said:
If you have a bootable phone right now this is easy as you may not need adb or fast boot or anything.
First off you will need to install 4ext. Get the app from the Play Store. Then run it and let it install its recovery module. (You may need to be rooted to do thus, which your stock rom is not. Im not sure if you can flash the recovery without root or not because Ive never tried without root. If so, then you will have to install Superuser via fastboot I think. You any guide for rooting to get instructions on this. Its easy.)
You may also find a way to install 4ext recovery via flashing from bootloader, but you will have to search for that. You MAY even be able to install it with the firmware upgrade. You will have to see if that is an available option.
Get your firmware from this thread...
forum.xda-developers.com/showthread.php?t=1459767
Follow the instructions to update. Once you have 3.3x firmware and 4ext simply boot to recovery, do a full wipe, and flash cm10 (make sure cm10 is on your sd card. You can download it from your currently working gingerbread rom so you have it available)
You have like 15-20 minutes worth of work to do, so its not a monumental obstacle to overcome. It just seems like alot
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I am not rooted but am S-off. So my next step would be to root. I am suppose to have Clockworkmod to root AND 4EXT after right? Its not one or the other? I keep reading that people recommend 4ext is better than CWM but in order to root su-2.3.6.3-ef-signed.zip I need CWM first correct?
fashofasho said:
I am not rooted but am S-off. So my next step would be to root. I am suppose to have Clockworkmod to root AND 4EXT after right? Its not one or the other? I keep reading that people recommend 4ext is better than CWM but in order to root su-2.3.6.3-ef-signed.zip I need CWM first correct?
Click to expand...
Click to collapse
flash su-2.3.6.3-ef-signed.zip first and then install 4ext recovery
You're over engineering this. You don't need to root your current ROM first. That's an extra step since you're s-off.
If you are s-off it's really simple to get 4EXT recovery.
First, download this and put it on the root directory of your SD Card (meaning not in a folder, just on the SD Card. Do not rename it)
http://d-h.st/qnm
I got this download link from here...
http://forum.xda-developers.com/showthread.php?p=21989107
Click Thanks for Joaquinf in that thread. He made the 4EXT zip that's flashable through the bootloader.
That is 4EXT made into a zip file that's flashable via the bootloader, which you can do when you are S-off.
So put that file on the SD card, power the phone off, pull the battery out for a second and put it back in (this stops fastboot so you can get back to the bootloader). Then hold volume down and power at the same time. You have to hit both buttons at the same time. If it goes to the splash screen, pull the battery and try again.
When the bootloader loads up it will immediately find the PM58IMG.zip file. It will ask you if you want to install the update. Say yes by hitting volume up I think (it will tell you how to say yes)
Put the phone down and don't touch it until it tells you it's done. Should just take a second. But seriously don't touch it. Leave it alone.
If that works, you've just flashed 4EXT. You can check it by pulling the SD card out (so it doesn't try to flash the PM58IMG again) and rebooting to the bootloader and selecting 'recovery' from the menu. 4EXT should boot up.
This entire process so far shouldn't take more than 3 minutes total. It just sounds like a lot.
To see this detailed out by someone else in case you want to check what I'm saying, read steps 4 and 5 of the first post in this thread.
http://forum.xda-developers.com/showpost.php?p=21989063&postcount=1
Give the author 'thanks' again because he's awesome and deserves it.
Now you've got 4EXT installed. Great. You're 1/3rd of the way home.
Now you need to update your firmware. Delete the PM58IMG.zip file you used to flash 4EXT off the SD card (use a card reader or boot the phone up and delete it, whatever works. You can also use 4EXT as a card reader now too by choosing USB storage from inside 4EXT. It will give you access toteh SD card on your computer now)
Now get new Firmware from this thread.
http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
try the 3.33 firmware universal. First download link in post 2 of the thread above.
CHECK THE MD5 SUM!!!! I'M NOT PLAYING AROUND HERE!!! You are worried about bricking your phone, this is where you can do it if the firmware .zip is bad.
Put that PM58IMG file on your SD and flash it in the bootloader the same way you flashed 4EXT recovery a minute ago. (If you're still in 4EXT recovery you can use it's power menu to reboot into bootloader easily.)
This will take a minute. The phone will shut off and go black in the middle of this process. Your heart will skip a beat. Relax. It'll come back on. Again, put the phone down and walk away while it does it's thing and don't touch it until it says it's done.
Delete the PM58IMG file from your SD card.
You are now 2/3 of the way there. Your phone WILL NOT boot up right now because your ROM is not compatible with your firmware. Relax. That's supposed to happen.
Now you can flash CM10. Make sure you have the CM10.zip file on your SD card nad GApps. (Bruce has Gapps in his downloads page). Delete the PM58IMG firmware file from your SD card (that's important)
Pull the battery again so you can get back into bootloader. Get into bootloader (power + volume down)
Select Recovery
4EXT should boot up.
Go to the Wipe menu. Wipe all partitions except SD card. (Old ROM is now gone)
Go back to the main menu.
Install from SD
Find the CM10.zip file you should have downloaded and put onto the SD card. Flash it.
This will take about 3 minutes. 4EXT will flash it and ask if you want to reboot. You do not yet. Not you need to flash Gapps the same way you flashed the ROM.
When that's done, now you can reboot. You shoudl see the CyanogenMod boot animation after the splash screen. Give it a few minutes to boot up this first time. Once it boots, set it up the way you like it. If you enjoy it, donate a few bucks to the developer, Bruce.
You don't have to root CM10. It's already rooted when you boot it up the first time.