Related
Hey people!
I read a few posts dealing with same error below, but the descriptions of the problem was a bit different so I wanted to be sure.
I'm quite new to this so bear with me. I got an EVO last month (dec 24) and have since wanted to root. I've been reading up on it, and finally decided to root using Unrevoked earlier today. The root process worked perfectly, so I proceeded to create a nand backup and flashed the CM6 Mod using Clockworkmod rom manager app.
I was a bit excited played around with it a bit, and decided to flash the Miui ROM. I placed it on the root of my SD card, and this is where I lost control. I tried to flash using the ROM manager and it never completed, citing an error. I tried to reboot phone but I didnt get past the white HTC EVO 4G screen. I entered bootloader, and I tried to restore my original Nand backup but I keep getting this error, "Error while flashing boot image."
What would be the appropriate (or least risky) course of action? I can mount my SD card on computer through ClockworkMod recovery, should I try placing stock ROM zip or cm6 zip file and try to flash?
I do not think this is a battery issue, I had my phone plugged to charger while trying to flash nand.
I appreciate the help, I know I probably sound like a noob, but for almost a month I was reading, learning and trying to be careful (obviously not enough), once I rooted I got overzealous.
MOD Version is 2.5.0.1
Thanks for all your help,
DJ
I flashed a the recovery, after a few issues...my phone is back up and running...DISREGARD. Sorry for the noob ?.
Please be nice to me.....I am a newbie, very bold and out of the box and living dangerous with this rooting and ROM flashing. I am addicted but do not know a lot. I am not techno stupid but I get excited and dont think sometimes (was before I took my A.D.D. meds so I was being impulsive) anyhow for some stupid reason I didnt run a nandroid backup. I have a backup but for some reason it wont boot to it. What happened was after flashing 7 the other day, I loved it but market kept force closing all my apps and I couldnt figure it out so I restored back to mod6. was up all night playing around trying to learn all this lingo blingo ROM crudola...........anyhow saw the 7nightly so I flashed it while driving to work (bet yall think im really dumb now) LOL and it boots and gets to the Android screen where it says touch the Android to begin......NOTHING HAPPENS. Rebooted 3 times no worky. So I figure well go back to Mod6 and have a phone until 7 is stable. Cant do that so Im not sure what to do now. I tried flashing a Full Mod6 but to no worky I am at a LOSS. Figured I would ask the experts to please help with ideas. Hugs from Texas girl
Currently backing up my SD card in case I need to.
Have you been wiping in-between flashes? If not:
1. get into recovery
2. wipe everything except battery and rotate stats. Wipe it all again.
3. Flash the Rom of your choice.
4. ???
5. Profit (hopefully)
cm7 nightlys
nicolemiles said:
Please be nice to me.....I am a newbie, very bold and out of the box and living dangerous with this rooting and ROM flashing. I am addicted but do not know a lot. I am not techno stupid but I get excited and dont think sometimes (was before I took my A.D.D. meds so I was being impulsive) anyhow for some stupid reason I didnt run a nandroid backup. I have a backup but for some reason it wont boot to it. What happened was after flashing 7 the other day, I loved it but market kept force closing all my apps and I couldnt figure it out so I restored back to mod6. was up all night playing around trying to learn all this lingo blingo ROM crudola...........anyhow saw the 7nightly so I flashed it while driving to work (bet yall think im really dumb now) LOL and it boots and gets to the Android screen where it says touch the Android to begin......NOTHING HAPPENS. Rebooted 3 times no worky. So I figure well go back to Mod6 and have a phone until 7 is stable. Cant do that so Im not sure what to do now. I tried flashing a Full Mod6 but to no worky I am at a LOSS. Figured I would ask the experts to please help with ideas. Hugs from Texas girl
Currently backing up my SD card in case I need to.
Click to expand...
Click to collapse
Btw cm7 nightlys #7 is working fine I have no issues other than I think I might be having radio issues but that has nothing todo with cm7.
First you have to wipe and partition all data on your phone inrecovery mode. Cache dalve calche and do a full system wipe. Get yourself one of those minisd to sd card adapters to format your sd. Erase all data by formatting the sd the copy and paste your working rom zip back on the sd. Put it back in your fone and reboot into recovery. From there id do one more factory reset just to be sure then flash the zip. You should be good. Sounds to me you flashed to many roms on top of eachother without wiping prior installments.
Omg thanks
Wiping Data was the ticket.......DUH to me! you guys are awesome. Im in and just logged in and setting it up now. EXCITED!
tejasrichard said:
Have you been wiping in-between flashes? If not:
1. get into recovery
2. wipe everything except battery and rotate stats. Wipe it all again.
3. Flash the Rom of your choice.
4. ???
5. Profit (hopefully)
Click to expand...
Click to collapse
Gotta love the underwear gnomes
Hi,
I need some help please. Running CM7 7.0.0, using RomManager and ClockworkMod 3.0.0.5. I've been very busy with work and school so have not had much time to play with the phone, so two days ago I wanted to checkout one of the nightlies and installed nightly#101. Then I thought I haven't updated the PRL in a while and dowloaded the stock odexed version 4.20 from RomManager. I updated and then went back to the nightly#101.
This time though everytime I tried to make a phone call I would get a "Call has been lost" message. I figured must be a bug in this nightly or something. So using clockworkmod went back to CM7 7.0.0 backup. That's where my problems started. When the phone came on it was not reading the SD card (I tested it in my girlfriend's phone and it is good, I borrowed hers and the evo didn't read it), I could not turn on the bluetooth and when I rebooted it vibrated 5X and then the green light would blink. I though maybe the battery is dead, so I let it charge for 30 mins and the phone came on. I tried to reboot into recovery so I could reinstall the backup, but it would vibrate and blink, and sometimes it would come on and others not, almost randomly it seems.
Today, I found this fix for the SD card http://forum.xda-developers.com/showthread.php?t=1017387 and it worked.
However, the bluetooth is still not working and can't go into recovery. It seems that the only time I can get the phone to turn on and vibrate and blink is if I 1)put the battery in, 2)Press the power button and 3)plug the power in. Don't know why that works.
Any help would be greatly appreciated!
Recovery works now!
So I turned the phone on, went to RomManager and reflashed clockworkmod and tried to go into recovery from there, but it vibrated and blinked. I took the battery out, put it back in pressed power and vol down together and selected recovery and it didn't work (by the way, hboot.97 and it says s-on even though I had rooted with unrevoked and it was s-off).
I turned the phone back on figured let me try amon-ra since I have an amon-ra created backup in my computer. I turned the phone off, turned on with power+vol down, went to recovery and clockworkmod 3.0.0.5 loaded up.
I tried the reflash my backup and then once it completed, i hit reboot and it vibrated and blinked. Took battery out and put back in procedure again. went back to clockworkmod wiped cache and dalvik (not sure if needed, but figure it can't hurt). Rebooted from Cwm, but vibrated and blinked, and I did my boot up procedure again.
Bluetooth still not working, wifi works, wimax works.
I think maybe I should unroot go back to stock and see if that works. If it doesn't at least I can bring it to sprint and get a replacement.
I love CM7 and don't like Sense or Sprint bloatware.
I see 2 of your problems right off hand; Rom Manager and Clockwork Mod.
Get rid of RM and switch to Amon Ra.
HipKat said:
I see 2 of your problems right off hand; Rom Manager and Clockwork Mod.
Get rid of RM and switch to Amon Ra.
Click to expand...
Click to collapse
i second that!!!
to the OP....what I would try (as a last resort) is factory reset your phone and unroot (run the 2.2 RUU or any other method that unroots), then try to reroot your phone....and flash Amon_RA as opposed to RM and CWM. then reflash the rooted 4.22 ROM, do your updates of radios, prls, etc. and then CM7....that might do the trick. I'm suggesting this cause you said:
topollillo said:
by the way, hboot.97 and it says s-on
Click to expand...
Click to collapse
and question for ya....you had used Amon_RA but then went to RM and CWM?? why???
I rooted with unrevoked and then installed rommanager. i had then installed amonra, because of what i had read about CWM and the rsa keys backups. but went back because of the convenience when flashing roms.
So now i have discovered that the Usb is not working. I tried the fix in the same thread as the sd card fix, but it did not work.
I'm going to go back to 2.2 see if that fixes it and then follow your steps.
If it doesn't fix then will go to sprint for a new phone
Will report back on what happens. Thanks.
do u have an sd card reader
and yeah amon ra is way better than clockwordmod
back to 2.2 bluetooth not working, usb not working, vibration + light still happening.
If I call sprint to get a replacement phone, they will prob ask me to make sure I have the latest software. should I just accept the OTA and see what happens, or am I risking losing root? Does it not matter?
I don't have an sd card reader, downloaded to phone over wifi.
how can s-on happen automatically. I had rooted and had s-off with unrevoked forever?
Apparently you messed something up, because with s-on, you aren't rooted. I would boot into the bootloader, do a clear storage [factory reset], then try unrevoked again. Make sure you have the hboot drivers, installed then uninstalled htc sync.
Went to the Sprint store after an unpleasant phone chat with sprint support. They tried to force the phone to update, that didn't work. So they gave me a new phone.
So I don't mess up this one, could someone give me a recommendation as to how I should go about rooting and installing CM7. Use unrevoked, install amon-ra, flash to my heart's content. Avoid Rom manager. Please fill in some blanks for me, if you have a link to a good guide it would be great. I know there are a lot of great guides here, unfortunately with work, school and the wife I don't have the time I used to have to enjoy my day reading up on the forums.
All your help was greatly appreciated.
Sent from my PC36100 using XDA App
topollillo said:
Went to the Sprint store after an unpleasant phone chat with sprint support. They tried to force the phone to update, that didn't work. So they gave me a new phone.
So I don't mess up this one, could someone give me a recommendation as to how I should go about rooting and installing CM7. Use unrevoked, install amon-ra, flash to my heart's content. Avoid Rom manager. Please fill in some blanks for me, if you have a link to a good guide it would be great. I know there are a lot of great guides here, unfortunately with work, school and the wife I don't have the time I used to have to enjoy my day reading up on the forums.
All your help was greatly appreciated.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yup, that is fine. Though if the new phone has 2.3 on it, you can't root it yet; if still on 2.2, use unrevoked and good to go.
I had the same blinking light and vibrating probelms on my evo. Mine was overheating really bad. It would run at a constant 102 degrees and when it hit 104 it would shutdown. I called sprint and told them what was happeningand without any questions or problems they sent me a brand new one in the box(non refurbished)
Sent from my PC36100 using XDA App
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
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
My girlfriend had the same issue with her second evo. She had the Black Evo at first than a friend of hers swapped her to the white Evo. She had the issue only on the white evo. She ended up having to replace the phone with another one. That one did the same thing for awhile so we thought it was an issue with an app she was running. I have the black evo and made a exact copy of her phone. I never once had the issue.
Sprint ended up replacing it agian with a line that something was different in the white Evo from the black one that was causing the issue. Ever since that day she hasn't had a problem with her phone. I just rooted and did her rom last night.
My question would be does the phone get hot? Or feel hot? The reason I ask is that the phones processor may restart the phone (in effort to cool it down) randomly. That is something to consider.
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
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