[Q] Carrier Wipe on Rooted Phone? From Sprint to Ting, using CyanogenMod 7.2

[Q] Carrier Wipe on Rooted Phone? From Sprint to Ting, using CyanogenMod 7.2 - EVO 4G Q&A, Help & Troubleshooting

The short version: I need to know how to do a carrier wipe on my Evo running CM 7.2, because ##72786# doesn't work.
The longer version: I've been trying to get my Evo activated on Ting since last Friday. It's been sitting around for about 2 years, and it was on an older version of CyanogenMod. Ting said I was all set, and to dial ##72786#, and then enter my MSL. When I do that, I get a message saying that my account could not be validated.
Over the weekend, I kept trying, but eventually decided to switch to a different ROM. That's been very frustrating, because I can't find working download links for the versions I want, and of the several others that I have tried, I can't get the phone to boot, after, at least not beyond the white screen. So, I put my PC36IMG on, and even that wouldn't do the trick. I thought maybe I'd bricked it, because it took 2 tries to get CM 7.2 going again, after all of that.
So, does anyone have any idea how to do a carrier wipe on CM7? From what I read, I have to do it differently, but using the stars in that code doesn't change anything. I tried a calculator hack, but that won't work for me, because the calculator it comes with doesn't have scientific mode. (Although I will now go try downloading one, to see if it works).
I'm at my wits end! I never had any problems during the 6 months or so using CM with Sprint, before I moved on to another phone. I've looked at hundreds of pages, mostly forum threads, and it seems so odd to me that I'm the only one with this problem.
One weird thing, on Sunday, Ting shows me as having downloaded a couple MBs of data, but to my knowledge, this has never successfully connected to their network. Perhaps I managed to get data to connect, when I wasn't aware? I never have even tried the steps to get data switched, since I can't get the carrier wipe done.

New number
If it matters, I didn't port my number, I'm getting a new number with this account.

Stars in Code Got Closer
So, I can use the dialer codes with stars in them. Or rather, some of them work. For example, *#*#33284#*#* will get me to a debug menu. When I try *#*#72786#*#* it reacts, but not like it should. The code I've been typing in disappears from the screen, as though it's been recognized as a valid code, but then nothing else happens, I don't get a menu, or anything.
I finally got another ROM flashed, and I was able to boot, but then the screen doesn't respond to my swipes, so I can't even unlock it. I'll be trying yet another ROM, but this is SO frustrating.

You need a sense ROM. Use captain throwbacks rooted stock. A sense ROM is the only tried and true way.
http://forum.xda-developers.com/showthread.php?p=26516892

Thanks for the reply! I believe I've tried that ROM, but I will give it another go.

The few roms I made from ctb base all have no problems using any codes, feel free to try one to program your phone, and if you do let me know if it worked.
I like to keep tabs on my work.
Sent from my PC36100 using Tapatalk 2

That ROM (captain throwback's 5.07.651.6 Stock Rooted - Deodexed) was already on my phone, so it was one I had tried. I went ahead and flashed it again, though. Pretty much anytime I flash a ROM, when my phone reboots, it stays on the white boot screen forever. I once let it go for 24 hours. I know it did it the very first time I rooted this phone, when I flashed the ROM. I eventually pull the battery, and most of the time, when I turn it on again after that, it boots normally. Some of the ROMs I've tried flashing in the last week won't boot at all, and I have to flash something else to get the phone going. I'm not sure now what the result of the first time I flashed this ROM was, but it's been sitting for about 30 minutes, now. I'm not sure how long I should let it go, before it's safe to pull the battery, so I'll probably wait until I run some errands, and come back to it in a few hours.
I'd be interested to know why the phone doesn't boot on the first try, after flashing, though. I wonder if that's why I've had no success with any of the ROMs I've tried, except for CM.
vinman, I will check yours out, if this isn't successful. I'm guessing the links in your signature will lead me to info?

Ok just to be clear, your rooted, s off, have a custom recovery like Amon 2.34 or smelks.
Do a back up of your sd card on your PC.
Now in recovery wipe everything,
Now format the sd card to 1024
Swap size 0
Upgrade Ext 2 to ext 3 or 4 if using a ROM with support for it, which mine has.
Now put your sd backup from your PC back on your phone sdcard
Now while still in recovery flash the ROM.
If your using mine it will reboot 3 times and take about 5 to 10 min to boot up do to the a2sd. Once it boots let it sit for 5 min to settle in.
Set up your google account
Now from dialer enter your codes you want it should work as I have a older version on my build just so you can use the codes.
Hope this works.
Sent from my PC36100 using Tapatalk 2
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
vinman12 said:
Ok just to be clear, your rooted, s off, have a custom recovery like Amon 2.34 or smelks.
Do a back up of your sd card on your PC.
Now in recovery wipe everything,
Now format the sd card to 1024
Swap size 0
Upgrade Ext 2 to ext 3 or 4 if using a ROM with support for it, which mine has.
Now put your sd backup from your PC back on your phone sdcard
Now while still in recovery flash the ROM.
If your using mine it will reboot 3 times and take about 5 to 10 min to boot up do to the a2sd. Once it boots let it sit for 5 min to settle in.
Set up your google account
Now from dialer enter your codes you want it should work as I have a older version on my build just so you can use the codes.
Hope this works.
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
Just make sure you have all your Ting info in case you wipe it all.
Sent from my PC36100 using Tapatalk 2

So, this has been a pain, I'll put some detail here, in case someone else could use the info.
I backed the SD card up (again, again), and then from Recovery, I did a wipe (Wipe ALL userdata/factory reset). Then a Partition, where it asked the swap size first, which I set to 0. Then for Ext2-size, I set to 1024 MB. It then said FAT32-size would be remainder.
Back under partition, I did "SD:ext2 to ext3". There was an option to do "SD:ext3 to ext4", but I didn't do that. (Info on partitioning here, if anyone needs it)
Those took maybe a few minutes each. I then rebooted the phone normally, and turned on USB Storage, and copied just the clockworkmod folder over, so I'd have the the ROMs, that were saved there.
Nothing worked, so I started over. By nothing worked, I couldn't get it to boot to any of the ROMs I had, even the CM7 that had previously been working. It would just site at the white boot screen, and never would get to the CM7 screen, or whatever one was with the ROM I was trying, even when I'd let it sit for hours. Since I first rooted this phone a couple of years ago, it would often not boot after flashing a ROM, and just sit there at the white boot screen, but when the flash was successful, I'd have to pull the battery, and the 2nd time it would boot properly. I might not be cautious enough now, but I tend to not wait more than 30 minutes before pulling the battery. Also, in the past, I've flashed a ROM, and it wouldn't boot, so I'd repeat flashing that same ROM, and it would work the 2nd time. So, this whole thing has required a lot of patience and even more time. I typically walk through flashing a ROM, wait for it to not boot past the boot screen, reboot, and if it doesn't work I still wait a while, then lather, rinse, and repeat. Just trying to get this phone going in the last month, I've probably actively spent a good 15 hours, and that doesn't count when I just walk away and leave it plugged in, hoping time will help.
Anyway, I realized that that I had made a silly mistake, and that hadn't saved the PC36IMG_Supersonic_Radio_2.15.00.01.15.zip file as just PC36IMG.zip. So I did a wipe, and then partition.
When I partitioned the SD card again, I set swap to 0, and 2048 for the Ext 2, and the remainder for FAT32.
I tried pulling the SD card, using a reader, and copying the files over, but something was wrong, and my laptop wouldn't recognize the card. I'm fairly certain that the reader is broken, and doesn't work with micro SDs anymore, so I just put it back in the phone and tried to reboot.
First time booting, it stuck on the white boot screen again, so I gave it 10+ minutes then pulled the battery, and tried booting once more. Still no go, so wiped and tried again. Still no, 2nd reboot, still no. Tried ext 3, no go.
So, I finally got to the store, since I couldn't find my other Micro SD adapter that works, to get another, and put the PC36IMG file on. I booted to recovery, it found the file, installed it, and rebooted. It stuck on the white boot screen, as expected, so I gave it some time, pulled the battery, and rebooted again.
I've been at this for the last week, and although I was able to get the CM7 ROM going a couple of times, I can't get it going now. And the PC36IMG isn't going, after the 2nd reboot. I have hope, but it's waning. I'll be doing some additional research, in between other stuff, this afternoon. But, I thought I'd go ahead and post this, since I've been writing down what I've done as I go this time, just in case someone stumbles along and knows what I'm doing wrong.

So, I followed some of the advice from the Rooting for Dummies guide and I wiped the Dalvik Cache a couple of times, and then decided to go ahead and Wipe All a couple of times. Then I partitioned the SD card (0, 2048), followed by upgrading ext2 to ext3. I copied PC36IMG back over, and tried that again. I then decided to figure out what the ext2 thing was, and found this question about ext2, ext3, and ext4, which says that it doesn't hurt to go to ext4, that the older ROMs will convert it back, if needed. So, I did that.
Of note, when I rebooted, to try for the PC36IMG again, I noticed that it can't find what I think says PC36IMG.diag, although otherwise it always seems successful, other than not booting past the white boot screen.
I'm waiting to see if it gets past the boot screen, now. Assuming this doesn't work, I'll repeat with the ROMs that I have, and hope that will work. Probably won't post again today, unless I get somewhere new.

Wow, I finally got it going! Notes are below for reference. I tried the deoxed ROM mentioned at the end of my notes. (can't paste right on mobile) but only the 3rd try, it worked. The only thing different was that I didn't have it plugged into the wall when I ran through the flash and reboot, this time. Does anyone know if that would make a difference, or if it's coincidence? Anyway, next I'll want to go back to CM7, but I'll wait till tomorrow, after I backup, and have time.
Here are my unedited notes, in case it might help someone else...
Wiped, partitioned, enabled USB-MS, created a "clockworkmod" folder on the empty SD card, then copied the oldest folder I have handy, "2013-07-13-16.11.44" over. Then exited USB, and selected "backup/restore" and then "restore nandroid", intending to select that backup.
Of course, when I tried to mount the USB, my laptop refused to recognize it, so I had to reboot my laptop, before continuing with that step. This is kind of how every step along the way has gone. Rebooting didn't help, and I though tht worked!
at this might be why my laptop stopped seeing the card through the phone before, and I tried upgrading ext3 to ext 4, which I had skipped this time. That didn't work, so I went ahead and powered the phone off, and used the micro SD card reader to transfer those files over.
Of course, restoring the nandroid didn't work. Apparently, even though I put it back in the folder it came from, Nandroid expects it to be in a different folder. So, I created a "nandroid" folder, to put the files in. It needed them in appropriate subdirectories, so that didn't work.
Next, I pulled out my backup drive, and looked for my original Evo backups, from a couple of years ago.*
I found a nandroid folder that had the device name and then a backup folder with the expected type of name. I got that on the card, put it in, did the recovery, and this time, it was recognized, and the restore started. It took I'd say 20 minutes to complete. When I had it reboot, I walked away, and when I came back it had rebooted to recovery, which was unexpected. I had it power off, and then turned it back on. That repeated when I turned it off and on, so I guess that I've finally hit my first boot loop.
I did a wipe, moved PC36IMG to the root, and tried that. Rebooting gave me the white boot screen, then it went dark, rebooted and went to Recovery. I tried rebooting again, same thing. I did a wipe, then rebooted. It did the dark screen, then rebooted to Recovery. I tried again with the*5.07.651.6_stock_rooted_deodexed_CPTB ROM

I'm having the same exact issue.
Hi all,
I'm having the same exact problems described here, and for the same exact reason. I'm switching from Sprint to Ting, though I ported my number, too.
I've spent all afternoon trying to restore stock roms so I can input the ##72584# number or whatever it is and activate my service, but I can't get any roms to work right now. I'm going to try the recommended DEOX version mentioned in this thread now. Just putting in my note so others can see they're not alone.
If I get it working, I'll mention how.

Good luck. I'd be happy to help, however I can.
Given that sometimes I've had to install a ROM twice to get it to take, I'm really wondering if the phone being plugged into power (not even a PC) might have affected something. It would seem like a really weird thing, but that's the only thing that was different the last time I tried to install that ROM, and it was at least the 2nd time in a row, if not the 3rd. So, try multiple times, until you get it going.

Should not be this hard to flash a sense Rom and enter service programing codes. Simple thing is just back up your SD card to pc,
Then partition your SD card ext 2 is fine for stock gb Rom. So after partition put your backed up SD card back on your SD.
Wipe the phone 3 times except for SD. Flash Rom. Should work fine

What I had to do
In brief what worked for me is that I needed to install a stock rom without the custom recovery to allow the ## commands to work from the dial pad. You do not need to go all the way to S-ON.
Step 1 - Upgrade your custom recovery and have an image of your custom recovery for you to re-install. I use Clockwork Mod. You can get it here:
http://forum.xda-developers.com/showthread.php?t=1473525 Save PC36IMG.zip of your custom recovery on your PC for later.
Step 2 - Boot into your custom recovery and make a backup.
Step 3 - Download and save PC36IMG.zip of the STOCK ROM from here: http://forum.xda-developers.com/showthread.php?t=780141 You do not need the S-ON.
Step 4 - Reboot your EVO 4G into HBOOT with power and vol-down and let it install the stock ROM. THIS WILL OVERWRITE YOUR CUSTOM RECOVERY. You have your custom recovery saved from step 1, right?
Step 5 - Reboot and then use the keypad to do your carrier wipe from this page: https://help.ting.com/entries/22935397-Activation-for-your-HTC-Device Let it reboot several times.
Step 6 - Copy the PC36IMG.zip from step 1 onto your SD card.
Step 7 - Reboot using power vol-down into hboot again and let it install your custom recovery.
Step 8 - Reboot into your custom recovery and restore your backup image onto your phone.
Edited to add, I did not have to wipe my SD card, but your mileage may vary.

use sprint base sense Rom
use s sense base sprint Rom.
you can try digitalkarmav9
it worked for me.
best thing about Ting, you don't have to mess with flashing. and they are resonable if you don't use data.also unlike boost or virgin they toss over to verozon when you roam

Related

Constant boot loop, all ROMs...

My phone is mullered :-(
Whenever I flash a new ROM, all I get is a constant boot loop on first boot.
Flashing a different ROM results in the same behaviour.
The only way out of it is to re-root, taking me back to version 1.15 or something, and then if i try to flash a new ROM - you guessed it, boot loop....
This first started when I had OpenDesire installed, which was fine to begin with, but then it randomly rebooted and started boot looping.
Since then I've tried about 4 or 5 different ROMs and nothing changes.
Any ideas as to what's wrong/a solution?

Just to add, I have one the lastest radios (.08) when I try and flash.
Perhaps flashing the radio after might help?

After much struggling, I've managed to sort it.
Ended up clearing storage in recovery, which helped so long as there was no SD card in it. Had to format and repartition the card, and fingers crossed, all seems well now.

Whenever you change between diferent ROMs it is a good practice to do a full wipe via recovery. 90 to 99% of the boot-loops can be fixed doing it...

The strange thing is that I did wipe between ROMs. I'm not sure why I had a problem this time round, as I haven't had with the previous 10 flashes...
Still, it's sorted now

Funny.. found this thread via google.
I'm having the exact same issue where no matter what rom I flash it gets stuck on bootloops during the startup animation and never makes it into the rom.
NANDroid backups are perfectly fine to restore, just unable to flash any new roms. Spent all last night trying everything from swapping recoveries, to re-rooting, flashing multiple roms, urgh.
Only thing I didn't try is re-formatting the SD card so gonna give that a go now (thanks to this thread) and report back later.
Annoying to say the least.

Well what do you know... a 'partition my SD card' through rom manager (after copying said contents to my computer) worked a charm.
Most interesting......... Praise this thread and any others that gain help from it.

Did you update your radio ?
Sent from my spectrum zx

Man i'm lucky. Two hugely annoying problems in one go.
First up, yes I have replaced my radio, many times The SD card was obviously not too happy with its ext partition, so repartitioning that worked.
I also had another issue crop up straight away that was probably caused by unhappy sdcard, where when restoring apps via titanium backup, phone would reset.
After running a RRU, re-rooting, all the full works.. I find that some of the apk backups are 1kb... Which is not normal. There were about 15 apps like this. I had a backup of these apps from a week or so ago and copied those to the titanium backup directory, restored, no problemo.
Even more annoyingly TB has a verrify backups option which reported all was well. FML.
Well that was a fun morning. Time to finally get back on track *sighface*

Rooted, Flashed Evo Classic, Loved it... now it keeps rebooting!

I rooted my Evo for the first time today using the Revolutionary method. Everything went smoothly following the instructions. I downloaded and flashed the latest Evo Classic ROM and I was loving it. It seems to be an awesome ROM. I have 200 MB free space instead of 46MB with all of my apps installed. Everything was great until I went to go to bed. I put the phone on the stock HTC charger and climbed in bed. Less than a minute later it rebooted. The phone has always done that at random times so I didn't think anything of it. Shortly after it booted it rebooted again. It just keeps rebooting over and over as long as it's on the charger! Now it even reboots when it's not charging but the interval is as long as 10 minutes instead of 1.
Has anyone else had this issue? I spent HOURS getting everything just right and customizing settings after flashing this ROM and I really don't want to have to do it all over again. I followed the instructions for flashing the ROM. I cleared the cache and wiped all data. I backed up my apps with Titanium Backup and restored a select number of them. My phone is my alarm clock. Now I can't trust it to wake me up in the morning to go to work!
EDIT: I just restored from my stock NAND backup and it is working fine for tonight. I'm guessing I need to just start from scratch and reflash Evo Classic? I can't seem to find anyone else that had this problem so I assume it was something with my flash or an app I had installed?

I flashed a fresh Evo Classic ROM and started over. Everything was great. I got it all setup and restore my apps. No rebooting problems. Put it on the charger. Worked fine. As a troubleshooting step I opened Sleep, my alarm clock app, and within 30 seconds it rebooted. Obviously something with that app triggered it. I uninstalled it. About a minute later it started a reboot loop in one minute intervals.
Apparently no one has any ideas or I am invisible. I can't post in the Evo Classic thread because I don't have enough posts to earn me the privilege.

Did you wipe dalvik? And what recovery are you using?

I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions.
I only see two options:
Wipe Data/Factory Reset
Clear Cache Partition
I have done both of these each time I flashed. I just flashed again and installed only the Sleep As An Droid app fresh from the market. I opened it and within one minute it rebooted. Obviously this app doesn't agree with this ROM or something isn't going right during the wipe and/or flash.
Any other suggestions for a stable ROM that has the new Sense notification bar with quick settings?
EDIT: I found the Dalvik Cache wipe option under advanced. Doing it now and will reflash and try again.
EDIT 2: Well that failed. I wiped data, cache partition, and dalvik and flashed the ROM. I logged into my Google account, downloaded the app from the market, put the phone on the charger, opened the app, and it rebooted.

Is it rebooting if you don't use that particular app at all?

Evo450 said:
I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions..
Click to expand...
Click to collapse
That recovery is called clockwork. You might think about changing your recovery to amon ra since some people have issues with clockwork because it doesn't properly wipe cache and dalvik

Hey there! Sorry about your issues. I don't always check the q&a, so you are usually better off posting on my thread or pm. I just happened to peep on here today
First. Use this. It's the second step on my instructions to flash Classic. Not necessary, but recommended. http://forum.xda-developers.com/showthread.php?t=705026
Second, don't use titanium backup. Instead, use mybackup root (free in market and included with my Rom). Not to bash tb, but mybackuproot has never given me issues while I've heard stories about tb.
Third, once you get amon ra installed, boot into recovery and wipe everything but your sdcard.
Fourth, download a fresh copy of classic from a reliable network, like home computer. Downloading from a phone is bad news (just a tip since you're newly rooted )
Fifth, flash and enjoy!
Please let me know how it goes for you.
Truly,
Tommy
tapatalk signature here. lovely.

Thank you very much for the reply! I will try your suggestions some time this weekend. I need my phone to work 100% as I am traveling so maybe Sunday I will try again.

I followed all of your suggestions and redownloaded the ROM, installed RA Recovery, cleared all data, cache, and dalvik several times, and reflashed the ROM.
I restored my apps and data using MyBackup Root and it took over 2 hours! I opened my alarm app and... reboot. Back to the same old reboot over and over.
I think I'll just go back to the stock ROM and remove the bloatware and call it good.

Theirs one obvious thing nobody mentioned. Google how to check a md5 sum do that with every rom you download and if it does not say its right don't flash, redownload and check again. Also restore as little as possible through mybackup and if you are restoring things like your alarms or any system settings don't.
As for good roms with quick settings like r2r going green lightning fast, or unleashed r6.
Ps I would suggest useing r2r superwipe before whatever you may flash n wipe both caches a few times first it might help
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Also id recommend copying all contents of SD card to computer and wipe SD card then reload everything back onto SD card. I know sometimes the SD card can become corrupt and cause bootloops and random reboots

I checked the Md5 sums of everything I downloaded. I only restored my apps, text messages, and Bluetooth pairings. I even ended up buying a new, larger SD card yesterday and I formated and used it when I flashed.
This afternoon I flashed my latest backup of my stock ROM and used Titanium Backup to removed all of the Sprint bloatware. My phone is running very fast now with over 110 MB of internal memory available so I can't complain.
Maybe next weekend I will try another ROM but for now I need me phone to be working since I do not have a land line and I rely on my phone for work.

You said this happened before you ever rooted? Maybe its a factory defect if u got a.warrenty I would suggest unrooting and sending to them.
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.

Its not normal they keep giveing you defects... I have never heard of.this problem anyway... I would take it bac
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Glad I got the black
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
I kept getting the same thing when i flashed classic. I went back to shooter port which runs butter smooth and is fantastic looking with sense 3.0.
DO THIS TO TRY TO GET EVERYTHING WORKING (no more soft reboot)
-connect your sd card to your computer
-copy contents to your computer for a backup
-copy PC36IMG.zip to your sd card make sure it is on root of sd card(attached to message)
-disconnect usb cable then pull battery
-enter bootloader (vol down + power)
-when it asks if you want to install the new update select yes
-after thats done pull the battery again
-enter bootloader then select recovery ( you should now have amonRa 2.3 )
-flash zip from sd card (vrsuperwipe.zip *thanks to virus*)
-go back and go into wipe menu, wipe dalvik-cache, wipe sdext, battery stats, and rotate settings.
-go to partition sd card and partition for a gingersense rom if you have not done so already. (0 swap, 1024 or 2048 ext2, remaining FAT)
ABOVE PROCESS COULD TAKE SOME TIME, MAKE SURE YOUR SD CARD IS MOSTLY EMPTY BEFORE YOU DO THIS (ONLY HAVE PC36IMG.ZIP ON IT)
-select usb mass toggle and connect to computer
-copy over your choice of rom, i suggest the shooter e3d port by team nocturnal.
-flash rom
-go to flash zip from sd card again this time select TeamNocturnal folder and pick a kernel to flash (try all of them if you would like, some phones run better with different kernels. mine runs well with HDMwIn kernel.
-wipe dalvik-cache one more time and you are ready to reboot with no more random restarts hopefully.
good luck - and please hit the thanks button if any of this works for you

[Q] Epic Failure... Any ideas?

Okay, so here's what happened:
I was minding my own business, listening to Pandora at work. Out of nowhere, the music had an increasing amount of pauses due to bad music loading, or so I though. I figured it was just the crappy Sprint network around here, but I figured I would restart it and hope it would work again.
Boy, was I wrong. At the first reboot, it got stuck in a bootloop where it would start my boot animation all the way from the start after it got into it's little animation loop for a while. So I pulled the battery and tried it again. This time, it made it through and loaded up to the lock screen.
Once I unlocked it, I got an error message that said something along the lines of "hardware UIC doesn't match, please wipe your data partition" (can't pull the exact wording out of it anymore, I can't reproduce it) I acknowledged that message and then I got a ****LOAD of FC's left and right for just about everything under the sun, and then some. All of my system apps were FC'ing, and it was just one after the other after the other, and it would even loop them around and the same system apps would pop up FC's again.
Okay...maybe I can fix this by wiping my data like it said. Nope. Maybe I can flash my ROM again and fix it... Nope. Now it loads up to the setup screens, and then about halfway through, the sytem just locks up on me.
****. Alright, let's try flashing a stock ROM back to it. Well, this doesn't work either. Same results.
I have no idea why it started doing this, and I really don't want to have to go get myself another phone, since I don't have any kind of warranty on my phone.
So does anybody out there have any other ideas on what I can try to do to fix this? It's been driving me crazy all night.

Run stock ruu
Sent from my nike hating evo!

Before you run the RUU, reformat your SD Card, I don't know what recovery you have, but use Amon Ra to wipe EVERYTHING Except the option for SDCard:, dalvik cache and cache 2 times, then flash your ROM in recovery.
If that doesn't work, try running RUU

Additional details about my phone:
HBOOT 6.16.1002
ClockworkMod Recovery v5.0.2.2
Also, I can't seem to find an RUU that my phone will take... They've so far been failing on me, but I'll keep looking...
Also, wiping, flashing ROMs, wiping again, has not produced anything fruitful. Will be going the RUU route. I seem to have found one that *should* take, fingers crossed.

Problem number 1. Clockwork Recovery Mod. Get rid of it and get Amon Ra and do as I posted above.
Here, download this, rename it to PC36IMG.zip, out it on the root of your SD Card, not in any folders, and reboot to Hboot (Vol dwn-pwr til hboot comes up).
It'll scan and ask you to update, say yes, it will flash Amon Ra. Now go back to Recovery, go to Wipe and do as I said above.
http://www.mediafire.com/download.php?v453e5wg0on3pzt

[RESOLVED] [Q] Epic failure... Any ideas?
CM REcovery hasn't led me wrong yet, but I have tried both of them... Personal preference, I think.
The RUU took and the phone is usable again for the most part. The only issue I have now is an error that pops up after every boot... "SD card unexpectedly removed" But I'll be digging around to figure that one out.
Thank you guys for your help, I was beginning to think it was a hardware issue for a while there.

CWM is leading you wrong and you just don't know it. For one, you can't do a proper wipe before flashing a new ROM. Also, there are issues with flashing Radios, if you ever need to upgrade.
There's a reason why the majority of users use Amon Ra. Your choice, though.
Maybe you need to reformat that card, or try a different card.

Wound up going back to work before I could finish everything I wanted to, however I was able to get S-OFF, and I went and flashed RA Recovery. The sd card issue was caused due to a bad sd card. Unfortunately I was unable to save everything from it, but I should be able to get most of my files back relatively quickly. Should be able to have Synergy flashed on it again before I go home in the morning.
Sent from my PC36100 using XDA App

[Q] Evo vibrates 5 times on boot, only hboot accessible

A few days ago while flashing a new rom, my Evo quit booting. I wouldn't consider myself a n00b, but I'm out of ideas. Here is what I have done:
* used unrevoked3 and unrevoked-forever to obtain root and s-off at least a year ago
* used CM7.1 stable as my daily driver
* used stock to update radios around the time CM7.1 went to stable
* flashed deck's ICS preview4 to test an app on 4.0, after doing a nandroid and wiping in cwm 5.0.22 (I think that was the version)
* the phone refused to boot, vibrating 5 times and flashing the green notification light
* going into hboot, s-on is back somehow
* recovery could only be reached if the usb was plugged in
* recovery could not mount the sdcard, so no nandroid restore
* tried several stock PC36IMG.zip until 4.24.651.1 finally flashed in hboot
* the phone still won't boot, either vibrating 5 times or showing the red ! triangle
* the 4.24.651.1 RUU tells me my battery is < 30% even though I let my phone charge all night
Any ideas would be greatly appreciated. I don't really want to pay $450 for a new Evo. Thanks in advance.

Custom rom name it the same as img and see if that works if all else fails ruu and revolutionary
Sent from my PC36100 using Tapatalk

VaughnOnix said:
A few days ago while flashing a new rom, my Evo quit booting. I wouldn't consider myself a n00b, but I'm out of ideas. Here is what I have done:
* used unrevoked3 and unrevoked-forever to obtain root and s-off at least a year ago
* used CM7.1 stable as my daily driver
* used stock to update radios around the time CM7.1 went to stable
* flashed deck's ICS preview4 to test an app on 4.0, after doing a nandroid and wiping in cwm 5.0.22 (I think that was the version)
* the phone refused to boot, vibrating 5 times and flashing the green notification light
* going into hboot, s-on is back somehow
* recovery could only be reached if the usb was plugged in
* recovery could not mount the sdcard, so no nandroid restore
* tried several stock PC36IMG.zip until 4.24.651.1 finally flashed in hboot
* the phone still won't boot, either vibrating 5 times or showing the red ! triangle
* the 4.24.651.1 RUU tells me my battery is < 30% even though I let my phone charge all night
Any ideas would be greatly appreciated. I don't really want to pay $450 for a new Evo. Thanks in advance.
Click to expand...
Click to collapse
I had this happen to me a little less than a month ago and it ruined my weekend. I fortunately have a repair plan with Sprint as a "just incase" practice, so I just flashed stock and removed root, then brought in my phone claiming it just "restarted" and the software crashed, breaking my USB and SD card controller. The people at Sprint thought it was just "lint in my MicroUSB port," I laugh and told them to turn it on and they looked at my with a puzzled "wtf did you do to it!?" look.
What caused my problem was my SD card was full when I attempted to backup my ROM. This caused CWM fail at a backup and bricked my phone. Is this what happened to you by any chance?
I never did "fix" my phone's usb/SD management issue, but was able to temporarily boot it, but was plagued with random restarts. I'd like to throw in some links but I'm pinched for time seeing as I need to leave for work. (Search XDA) There was a Android 2.2 image that was I able to flash in the bootloader that let boot fully. But it will erase all traces of root. - Before you try and do anything else, research into if there is ANYTHING you can do with adb over WiFi, because that was the one thing that I didn't try. What I'm saying is to do a lot of reading before you start flashing anything, plan out your attack before you execute it. Because I ended up digging myself a deep hole by just randomly flashing images.
Wish you luck man, sorry I wasn't of much help.

nrm5110 said:
Custom rom name it the same as img and see if that works if all else fails ruu and revolutionary
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Hboot finds the renamed CM7.1 zip and checks it, but does not offer to flash it. I assume this is because s-on is back. Also, I mentioned that RUU is claiming my battery is too low to flash.

OMGWTF_BBQ said:
I had this happen to me a little less than a month ago and it ruined my weekend. I fortunately have a repair plan with Sprint as a "just incase" practice, so I just flashed stock and removed root, then brought in my phone claiming it just "restarted" and the software crashed, breaking my USB and SD card controller. The people at Sprint thought it was just "lint in my MicroUSB port," I laugh and told them to turn it on and they looked at my with a puzzled "wtf did you do to it!?" look.
What caused my problem was my SD card was full when I attempted to backup my ROM. This caused CWM fail at a backup and bricked my phone. Is this what happened to you by any chance?
I never did "fix" my phone's usb/SD management issue, but was able to temporarily boot it, but was plagued with random restarts. I'd like to throw in some links but I'm pinched for time seeing as I need to leave for work. (Search XDA) There was a Android 2.2 image that was I able to flash in the bootloader that let boot fully. But it will erase all traces of root. - Before you try and do anything else, research into if there is ANYTHING you can do with adb over WiFi, because that was the one thing that I didn't try. What I'm saying is to do a lot of reading before you start flashing anything, plan out your attack before you execute it. Because I ended up digging myself a deep hole by just randomly flashing images.
Wish you luck man, sorry I wasn't of much help.
Click to expand...
Click to collapse
My sdcard has over 4gb available space. I flashed stock 2.3 in the bootloader but it still refuses to boot (as mentioned in the original post). As far as I know, you need to be able to boot to use adb. The only images I have tried to flash are stock images and CM7.1.
This is starting to look bleak...

I appologize I didn't see it man
Sent from my PC36100 using Tapatalk

VaughnOnix said:
My sdcard has over 4gb available space. I flashed stock 2.3 in the bootloader but it still refuses to boot (as mentioned in the original post). As far as I know, you need to be able to boot to use adb. The only images I have tried to flash are stock images and CM7.1.
This is starting to look bleak...
Click to expand...
Click to collapse
Sorry, my previous post was in a rush. (As is this one, lol)
Really? So your phone just screwed up out of no where while flashing the ICS alpha4 rom? Were you using CWM? Because if so, I'm switching to Amon RA asap.
Moving on, I know how you're feeling right now. But, I still have hope.
As previously stated, after ruining my EVO I was able to flash a PC36IMG.zip that allowed me to boot my EVO. I had to do some serious digging, but I found the thread I used with the ROM that worked http://forum.xda-developers.com/showthread.php?t=884060.
None of the old Megaupload links work, but this filesonic one does. Download it and flash it in your bootloader. Its signed, it should work. Try to flash it twice if anything. If it still doesn't work, try one of the newer ROMs. I'm only guessing that's the one that worked for me.
The only problem is that I don't think that's a 2.3 ROM, and we need a 2.2 ROM. Because the only root method that doesn't use a USB/SD Card is this: http://forum.xda-developers.com/showthread.php?t=701004 If you can get
If you can get your EVO rooted again with S-Off, follow this guide here: http://forum.xda-developers.com/showthread.php?t=695243 (Original) and you might be home free. But as of now, your goal is to find a stock 2.2 PC36IMG. Hopefully someone else can help here.
I sadly have to get to bed. Just got off work and I need to get some rest, another long day tomorrow. Good luck! I'll be back here next chance I get.

Same thing here
I'm having the exact same issue - flashed ICS alpha 4, now I can't mount my SD card. I don't have the red triangle of death, but I am getting the 5 vibrations on trying to boot - can get to hboot, and was able to *almost* get the SD card to mount using this:
http://forum.xda-developers.com/showthread.php?t=695243
but that only yielded ICS "preparing SD card" and "checking SD card for errors" indefinitely. I backed up and formatted my SD card, and this at least let me browse the empty sd card in Clockwork Recovery - I am in the process of copying my cwm backups back to the sd card in the hopes of being able to restore them from cwm. I'll keep you posted on what happens, and will most likely try to RUU when I get home from work. Puzzling that my s turned back on again as well, it's been off for well over a year...

Update on previous post
spoonydx said:
I'm having the exact same issue - flashed ICS alpha 4, now I can't mount my SD card. I don't have the red triangle of death, but I am getting the 5 vibrations on trying to boot - can get to hboot, and was able to *almost* get the SD card to mount using this:
http://forum.xda-developers.com/showthread.php?t=695243
but that only yielded ICS "preparing SD card" and "checking SD card for errors" indefinitely. I backed up and formatted my SD card, and this at least let me browse the empty sd card in Clockwork Recovery - I am in the process of copying my cwm backups back to the sd card in the hopes of being able to restore them from cwm. I'll keep you posted on what happens, and will most likely try to RUU when I get home from work. Puzzling that my s turned back on again as well, it's been off for well over a year...
Click to expand...
Click to collapse
*** Update ***
Ok, so after all that, I was able to restore my backup from within recovery, copy all of my data back to the sd card, and now I'm back in business...mostly. I still get the 5 vibrations on boot *unless* i'm plugged into the computer, and even then it's not a sure thing (usually takes 3 or 4 tries to get it to boot). At least I have a functioning phone again. Next step - RUU and factory reset, and see what happens. Again, I'll post back with my results. Hope this helps someone

[Q] Completed Factory Reset (MIUI) and SDCard format and now soft-bricked!

Hey folks,
Thanks for taking the time to read/assist. I don't typically do these kinds of posts and am at my wit's end!
Phone's Previous Setup - MIUI Gingerbread, Rooted (but with S-ON after the fact).
What happened:
My HTC Incredible finally got to the point of being practically unuseable with laggy behavior and random restarts and the like, so I decided to complete a reset to factory settings or wipe.
I completed my backups using Titanium (apps) and ClockworkMod Recovery (full backup). After this, I went ahead and opened up Settings and directed the phone to complete a Reset to Factory Settings. It ran through the process, rebooted, and came up jelly. While no custom apps were installed (expected), my folder settings on my main home page were saved, along with some previous text messages. I was pleasantly surprised.
From here, I wished to wipe the SD Card so as to make sure it was clean of any residual folders/files that might cause conflict down the road (based on advice from others). So, headed to the SD card part of the settings. Had to unmount the SD card to format, proceeded to do so.
Here's where things went wonky: Despite receiving a confirmation that the SD card format had proceeded, nothing else ever happened. I attempted to mount the card again w/o luck (kept getting a msg that it was now unmounted). Eventually, I decided to go ahead and restart the phone and see if that helps. Big mistake.
From this point forward, the phone refuses to fully start up into any Android ROM. Initially, it hung on the white HTC Incredible splash screen (yes, even w/ giving it an hour+ of time). I tried wiping and reflashing different ROMS over the period of the day yesterday to no avail.
Doing a full recovery via ClockworkMod (from my backup that I made before and copied back onto the SD card via USB) leaves me stuck on the HTC Incredible white splash screen.
MIUI - 2.2.10
Hangs on white splash screen
No go w/ or w/o SD card installed
MIUI - 2.2.17
Loads past white and MIUI splash screens
Instead of loading into Android homescreen, immediately loads up "Encryption" error and directs to "reset phone."
Repeated restart and attempts of resetting phone don't work
No go w/ or w/o SD card installed.
MIUI - 1.12.9
Hangs on white splash screen.
No go w/ or w/o SD card installed.
CM - 7.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
CM - 6.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
I looked into HBOOT options, getting PB31IMG.ZIP and PG86IMG.ZIP.img thinking maybe I could try reverting to stock at a friend's suggestion. HBOOT sees the files and "checks" them, even briefly showing a small vertical blue loading bar at the top-right corner, but never attempts to run/update them as I am lead to expect from all the instructions/encounters I've found on the net suggest. The screen info flashes by so quickly, I can barely read it, but I confirmed that it said "checking" and not updating or such. x.x
I considered trying to flash an updated copy of ClockworkMod Recovery, but I cannot do that w/o being able to load up the phone into Android.
I cannot run anything desktop-side, like ADB, as they all require the phone started up and put into USB-debugging mode.
I've looked into and tried all this and more, but nothing seems to be working.
My next idea is to try to forcibly downgrade the phone. Reasoning being that I read that the HBOOT will not try to update if it senses that the ROM is newer than its default settings(?). So, I need a good choice of "old" ROM that I can attempt to install via the HBOOT or CWM Recovery, and verify I have the correct files for HBOOT to try updating/running.
Again, this is a speculative attempt, but I'm willing to try whatever might work! Otherwise, I've got a fancy brick and my well-being on the line w/ no $$ to replace the phone. x.x
Thanks again for reading and hopefully offering some wonderful assistance! Sorry it's so long!
Feel free to ask Qs if you need clarification on stuff.

wigmuke said:
Hey folks,
Thanks for taking the time to read/assist. I don't typically do these kinds of posts and am at my wit's end!
Phone's Previous Setup - MIUI Gingerbread, Rooted (but with S-ON after the fact).
What happened:
My HTC Incredible finally got to the point of being practically unuseable with laggy behavior and random restarts and the like, so I decided to complete a reset to factory settings or wipe.
I completed my backups using Titanium (apps) and ClockworkMod Recovery (full backup). After this, I went ahead and opened up Settings and directed the phone to complete a Reset to Factory Settings. It ran through the process, rebooted, and came up jelly. While no custom apps were installed (expected), my folder settings on my main home page were saved, along with some previous text messages. I was pleasantly surprised.
From here, I wished to wipe the SD Card so as to make sure it was clean of any residual folders/files that might cause conflict down the road (based on advice from others). So, headed to the SD card part of the settings. Had to unmount the SD card to format, proceeded to do so.
Here's where things went wonky: Despite receiving a confirmation that the SD card format had proceeded, nothing else ever happened. I attempted to mount the card again w/o luck (kept getting a msg that it was now unmounted). Eventually, I decided to go ahead and restart the phone and see if that helps. Big mistake.
From this point forward, the phone refuses to fully start up into any Android ROM. Initially, it hung on the white HTC Incredible splash screen (yes, even w/ giving it an hour+ of time). I tried wiping and reflashing different ROMS over the period of the day yesterday to no avail.
Doing a full recovery via ClockworkMod (from my backup that I made before and copied back onto the SD card via USB) leaves me stuck on the HTC Incredible white splash screen.
MIUI - 2.2.10
Hangs on white splash screen
No go w/ or w/o SD card installed
MIUI - 2.2.17
Loads past white and MIUI splash screens
Instead of loading into Android homescreen, immediately loads up "Encryption" error and directs to "reset phone."
Repeated restart and attempts of resetting phone don't work
No go w/ or w/o SD card installed.
MIUI - 1.12.9
Hangs on white splash screen.
No go w/ or w/o SD card installed.
CM - 7.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
CM - 6.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
I looked into HBOOT options, getting PB31IMG.ZIP and PG86IMG.ZIP.img thinking maybe I could try reverting to stock at a friend's suggestion. HBOOT sees the files and "checks" them, even briefly showing a small vertical blue loading bar at the top-right corner, but never attempts to run/update them as I am lead to expect from all the instructions/encounters I've found on the net suggest. The screen info flashes by so quickly, I can barely read it, but I confirmed that it said "checking" and not updating or such. x.x
I considered trying to flash an updated copy of ClockworkMod Recovery, but I cannot do that w/o being able to load up the phone into Android.
I cannot run anything desktop-side, like ADB, as they all require the phone started up and put into USB-debugging mode.
I've looked into and tried all this and more, but nothing seems to be working.
My next idea is to try to forcibly downgrade the phone. Reasoning being that I read that the HBOOT will not try to update if it senses that the ROM is newer than its default settings(?). So, I need a good choice of "old" ROM that I can attempt to install via the HBOOT or CWM Recovery, and verify I have the correct files for HBOOT to try updating/running.
Again, this is a speculative attempt, but I'm willing to try whatever might work! Otherwise, I've got a fancy brick and my well-being on the line w/ no $$ to replace it. x.x
Thanks again for reading and hopefully offering some wonderful assistance! Sorry it's so long!
Feel free to ask Qs if you need clarification on stuff.
Click to expand...
Click to collapse
You need to gain s-off again before flashing with clockwork. How come you turned it back on?
"In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag."
edit:
gain s=off boot into CMW wipe data, and factory reset. Flash a new rom of your choice and then boot. should get you back to a working phone.

synisterwolf said:
You need to gain s-off again before flashing with clockwork. How come you turned it back on?
"In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag."
edit:
gain s=off boot into CMW wipe data, and factory reset. Flash a new rom of your choice and then boot. should get you back to a working phone.
Click to expand...
Click to collapse
The first time my phone was rooted/flashed, my bf did it for me. He used Unrevoked to root it and install CWM Recovery (v2.5.1.2 presently). I recall conversation being that having S-On would be better security with regards to the cell carrier (e.g., good to leave on, bad if off as they can see you rooted). So I agreed to having it put back to S-On, which I understood he then took care of.
Fast-forward a year and he now tells me he didn't actually end up running the other Unrevoked (Forever) tool to put S-On back in place, but that it simply *was*, so he left it that way. o.o;
Keep in mind, I've flashed 3 different ROMs since he originally rooted and flashed, w/o issues.
I pulled up everything to try re-rooting it again (to gain S-Off), but the instructions required having the phone loaded up and in debugging mode, which I cannot do as I cannot start up the phone past recovery in the first place.
Did I miss something that allows it via recovery? Going to check again in the meantime.

wigmuke said:
The first time my phone was rooted/flashed, my bf did it for me. He used Unrevoked to root it and install CWM Recovery (v2.5.1.2 presently). I recall conversation being that having S-On would be better security with regards to the cell carrier (e.g., good to leave on, bad if off as they can see you rooted). So I agreed to having it put back to S-On, which I understood he then took care of.
Fast-forward a year and he now tells me he didn't actually end up running the other Unrevoked (Forever) tool to put S-On back in place, but that it simply *was*, so he left it that way. o.o;
Keep in mind, I've flashed 3 different ROMs since he originally rooted and flashed, w/o issues.
I pulled up everything to try re-rooting it again (to gain S-Off), but the instructions required having the phone loaded up and in debugging mode, which I cannot do as I cannot start up the phone past recovery in the first place.
Did I miss something that allows it via recovery? Going to check again in the meantime.
Click to expand...
Click to collapse
actually its better to keep it s=off so this type of situation wont happen. Your carrier cant see your hboot from my understanding on how this phone works. They dont care if you have root or not, unless you are trying to exchange the phone for another one from them or for insurance reasons. With root you only void your warranty on the phone and not your contract or anything to do with VZW. S=off is just a NAND lock, meaning you cant add your own custom recover to the phone, and you are limited to builds that come from VZW themselves (ie the security signature check).
If you ever want to take the phone back to them because its defective or call insurance then you need to remove root and S=on. but thats the only time you need to toggle the NAND lock.
ok so you will need to ruu to stock, downgrade then gain s=off over again:
for the ruu for GB:
http://forum.xda-developers.com/showthread.php?t=1227279
a guide to do this all after you ruu:
http://forum.xda-developers.com/showthread.php?t=1306400

OMG I may've gotten it!
So I decided to give things another go with attempting to revert to stock again, as at this point, nothing is going to work other than via HBOOT.
I completed another reformat of the SD Card (Fat32) to be on the overcautious side and copied over ONLY the PB32IMG.zip file and restarted into HBOOT.
(Ah.. new user, so not allowed to post the link of where I got it.)
This time, much like before, it scanned, found the file, and did a parsing/loading. However, THIS TIME it actually prompted me to update! I chose yes (Vol+) and let it do its thing.
At this time, I am happy to announce that it actually is back up stock!
Wooohoo! Now to get it back to how I like it again. XD
If nothing else, hope this information helps someone else later on.

wigmuke said:
OMG I may've gotten it!
So I decided to give things another go with attempting to revert to stock again, as at this point, nothing is going to work other than via HBOOT.
I completed another reformat of the SD Card (Fat32) to be on the overcautious side and copied over ONLY the PB32IMG.zip file and restarted into HBOOT.
(Ah.. new user, so not allowed to post the link of where I got it.)
This time, much like before, it scanned, found the file, and did a parsing/loading. However, THIS TIME it actually prompted me to update! I chose yes (Vol+) and let it do its thing.
At this time, I am happy to announce that it actually is back up stock!
Wooohoo! Now to get it back to how I like it again. XD
If nothing else, hope this information helps someone else later on.
Click to expand...
Click to collapse
You might have lost root if you did the ruu from hboot. to check download the app "super user" from market that will tell you if you still have root or not.

Alright, now that I'm back to stock and runnin' smoothly, I need to figure out what route to take for rooting and flashing. Everyone talks about Unrevoked3, but I've heard there're other newer tools, too.
What would you recommend?
....also, sorry for the weird delay/disjointed/incomplete responses. I keep forgetting that XDA severely limits my posting capabilities. I wanted to say super thanks wolf, for all your help and sticking with me! Your input is appreciated. And yes, I'm pretty sure I lost all root, etc. It is back to "out-of-the-box" stock as far as I can tell.

wigmuke said:
Alright, now that I'm back to stock and runnin' smoothly, I need to figure out what route to take for rooting and flashing. Everyone talks about Unrevoked3, but I've heard there're other newer tools, too.
What would you all recommend?
Click to expand...
Click to collapse
unrevoked3 is the easiest way. but you will need to downgrade to android 2.2 for the security exploit.
http://forum.xda-developers.com/showthread.php?t=1306400
Edit: fixed link
---------- Post added at 10:44 AM ---------- Previous post was at 10:35 AM ----------
wigmuke said:
....also, sorry for the weird delay/disjointed/incomplete responses. I keep forgetting that XDA severely limits my posting capabilities. I wanted to say super thanks wolf, for all your help and sticking with me! Your input is appreciated. And yes, I'm pretty sure I lost all root, etc. It is back to "out-of-the-box" stock as far as I can tell.
Click to expand...
Click to collapse
lol now worries. easiest way to get to the 10 limit is just pad the count in here. ie just say something 10 times and you are good to go.

synisterwolf said:
unrevoked3 is the easiest way. but you will need to downgrade to android 2.2 for the security exploit.
http://forum.xda-developers.com/showthread.php?t=1306400
Edit: fixed link
Click to expand...
Click to collapse
Good news, I'm on 2.2 stock right now (just checked to confirm). So should be able to just go ahead and run Unrevoked3 then.
Also, the most popular recovery I'm aware of is ClockworkMod Recovery. I found that it's up to version 5.0.2.0. Would you recommend anything else or know of a newer version?
Figure if I'm going to do this, might as well do it right.

wigmuke said:
Good news, I'm on 2.2 stock right now (just checked to confirm). So should be able to just go ahead and run Unrevoked3 then.
Also, the most popular recovery I'm aware of is ClockworkMod Recovery. I found that it's up to version 5.0.2.0. Would you recommend anything else or know of a newer version?
Figure if I'm going to do this, might as well do it right.
Click to expand...
Click to collapse
Nope I'm RunNing that one and it works well.
Sent from my sexy assistant. (AMOLED HTC Incredible)

Develop Bugs

welcome