Related
Okay, i'm new here but reading all of your threads is just confusing me.. there is so much conflicting information.
To begin, I bought my phone at the sprint store before i was even considering this thing called "rooting". I did the OTA update, didnt know any better at the time... however I did toast's root and I honestly have no idea if i got it to work or not but I was able to do the ad blocking thing and what not.....
I started having an Sd card error on my camera, telling me i had "insufficient rights" to the card...
and the video camera in Qik simply didnt acknowledge that there was a card at all and to insert one.
Now. I attempted the OTA, to fix the SD card, and i thought it worked at first but then it acted up again.....
Now i'm hearing this thing about Unrevoked?? if i have already done it toasts' way can i still run unrevoked or is it advised that i flash it back to stock rom and wipe all my data AGAIN....
anyways heres the funny thing...
i had an extra 8GB micro sd card from my Touch Pro 2, and I put in my EVO and formatted it... and.... now everything works fine....
my version is still 1.32.651.1
What should I do now? Since im not having any problems since i changed the card...
is there data on that card is necessary? or that i can just transfer over?
I dont want to perform the OTA again, but i know if i did it would answer alot of questions based on the result...
I need advice...
Moved as not Android Development.
Was messing around with Kernel Manager Lite and tried to flash some kernel that looked interesting (didn't do any research or anything to see if it was compatible like the giant noob I am) but it said something about not having enough space and to reboot after I had more. I went and moved some apps to my SD card, rebooted, and now I'm stuck in that bootloader screen (fastboot, recovery, etc.). Phone isn't recognized by my computer.
Any way my idiotic self can fix this? Or am I screwed?
Running RC 4 of CyanogenMod.
Can you boot into recovery? If so, do you have any ROMs saved on your SD card? or possibly a nandroid of your current (pre-kernel testing) rom?
Vinchenzop said:
Can you boot into recovery? If so, do you have any ROMs saved on your SD card? or possibly a nandroid of your current (pre-kernel testing) rom?
Click to expand...
Click to collapse
No. It just goes back to the bootloader.
Bullonie said:
No. It just goes back to the bootloader.
Click to expand...
Click to collapse
well if u can go to bootloader ur not bricked so if u like u can just run a pc36img
in bootloader to go to stock
do you have a micro sd card reader that your card can be inserted into so that it can be read from your computer without being in your phone?
Bullonie said:
No. It just goes back to the bootloader.
Click to expand...
Click to collapse
If your bootloader still shows Ship S off, then try reflashing your recovery. I'm not sure whiich one you're used to using, but I'm going to attatch a PC36IMG of amon ra v2.3. Put the file on the main directory of your sd card, then boot to your bootloader. WHen it asks you to update, say yes. Once it finishes, you should then have recovery back and be able to start fresh with a new rom. BTW, if you were using clockwork before, do not attempt to restore any backups made with clockwork while you're using amon ra. It'll break a lot of stuff most likely.
If you're bootloader for whatever reason shows Ship S on, then I would run an RUU and flash back to stock, then start again.
But if his phone isn't recognized by his computer, and he doesn't have a micro sd card converter for his computer...he can't exactly put that pc36img on his card...
Vinchenzop said:
But if his phone isn't recognized by his computer, and he doesn't have a micro sd card converter for his computer...he can't exactly put that pc36img on his card...
Click to expand...
Click to collapse
Well, you're right. I guess I forget that every one might not have one. I have like 5 laying around here for some reason, haha. They're everywhere. If he had another phone with an sd card slot, he could swap the card into that other phone for a sec to move the file.
And sorry if I missed it, but does fastboot recognize the device?
TO the OP:
Edit: do you see anything in your device manager when you select 'hboot' usb from the bootloader screen?
Ah, we're good, booting into a ROM now. Thankfully I just got a card reader a couple days before this happened!
Thank you all for the help! Would have been stuck like this if it hadn't been for you guys.
I too have a few laying around, mostly from old phones (using one from my old samsung instinct as we speak lol), but from what he said, his phone isn't reconized at all by his computer.
You're welcome, even though, it was probably k2buckley's advice that fixed you.
Happy Flashing
One last thing, I can restore my apps right?
Vinchenzop said:
You're welcome, even though, it was probably k2buckley's advice that fixed you.
Happy Flashing
Click to expand...
Click to collapse
now thats modesty both u guys are awesome great work guys keeping a fellow evo owner from being bricked
u can restore if u backed them up
lcorona056248 said:
now thats modesty both u guys are awesome great work guys keeping a fellow evo owner from being bricked
Click to expand...
Click to collapse
We're just passing on the advice/tips we've been given by other great people on XDA
One last thing, I can restore my apps right?
Click to expand...
Click to collapse
as long as you backed them up with Titanium backup...which backs them up to your SD card, you should be able to restore them...if you haven't done that...nor have you made a recent nandroid backup, then you'll have to re-download those apps...
I'm having the exact same problem sorta. I got careless and deleted all my old recovery backups but one and I got what I deserved when I rebooted. The rom i was using didn't flash and now when i select recovery from bootloader screen it just kicks me right back to start. I've got titanium bu for my apps, but wtf cares if I can get back going again. This is first time i've really got in problem. I've always used clockworkmod as recovery because it was easy and in rom manager when I started. Ok so I can put pc36img on my sd card and then reboot correct? I have more than one sd card, so any tips for best way to go about this like that file and anything else? And where is best place to get a zip file that is best to use? Rooted with unrevoked, clockworkmod and 0003 is phone model. I've got a blank 8g card, 16 and 32 both have stuff on them. Music, rom zips etc.....any help would be greatly appreciated i'm in deep water and just learned how to swim lol.
Put the file pc36img.zip on the root of your sd card...reboot into bootloader...when it asks if you'd like to update, say yes...this will flash amon_ra recovery.
Then flash a new rom.
Id suggest using amon_ra, as I've never had a problem with it...not to bash on clockwork, but I see more people have problems clockwork not functioning correctly...
It's nice to use with rom manager, but convenience can come at a cost...
Sent from my PC36100 using XDA Premium App
Yeah I can tell that almost all the advanced guys use that. I been meaning to switch anyways just kinda like cleaning the gutters on your house. Easy to put off until it causes problem. I been using clockwordmod simply cause that was most simple fix when I first rooted cpl months ago. Now that i've flashed several roms and kernals etc i feel comfortable with trying. This is only time i've been like uh oh wtf do i do now? Lol you would think that doing a backup and making sure they are secure would not be such secret! I mean i've only been warned 1000 times yall really meant that huh....lesson learned and no more short cuts i swear if i can just get out this jam. thanks.....gonna go download rename and put it on sd card.
Live and learn brother lol.
Good luck, keep me posted
Sent from my PC36100 using XDA Premium App
And from what it looks like, you shouldn't have to rename the file that buck put up in the first page...
Just put that file, as is, on that root of your sd card...boot into the bootloader (not recovery) and follow the on screen prompts to update from that file
Sent from my PC36100 using XDA Premium App
Hi Everyone
I was hoping someone would be able to help me out as I’m a total Noob!
I have an HTC Desire on the Orange network in the UK. I started to get a few problems with my phone shutting down and restarting, my GF’s brother had been recommending that I root and flash a different rom for a while, and seeing as he has a Desire on the T-Mobile network and had never had any trouble with rooting his phone or any of the roms he used I decided to give it a shot.
I followed everything in Linkslovesandroid’s noob thread found here:
http://forum.xda-developers.com/showthread.php?t=1016084
I first tried CyanogenMod7 on GF’s brother’s recommendation, worked ok for a bit but I had problems with constant shutting down and restarting over and over again, is this called bootlooping? The only way to stop it was to remove the battery, even then it was no guarantee. Other things were going wrong like the screen freezing, certain buttons were unpressable etc.
I gave my phone to him and he couldn’t explain why such weird things were happening as his Desire experienced no problems at all. He suggested I try something different like GingerVillain. GV never loaded or booted up for me, I wiped data / factory reset, wiped cache, wiped dalvik, installed zip from SD, the rom would then install okay but when I rebooted the phone never ever got past the Alpha Rev S-off screen. This happened when I tried to install GV 2.5 and 2.6, I see that 2.7 has just been released but don’t see the point in trying seeing as the other 2 versions wouldn’t work.
I then tried Oxygen, again, worked ok for a while but started giving me random shut downs and restarts. Once I was driving down the motor way using sat nav software and the phone just shut down! I had to find somewhere to pull over to restart the sat nav software and again it restarted itself! Lol!
One day my phone went into an endless bootloop, no matter how many times I took the battery out the phone just wouldn’t stay on, I had to flash a new rom just to get the phone to fully boot up! I went back to CM7 but have the same old problems, so now I’m using MIUI and I’m still getting shutdowns!
What is wrong with my phone? If anyone has any ideas what I might’ve done wrong, or whats causing problems please offer your suggestions! I don’t really like the sense Roms, I’d like to try GingerVillain but I could never get it to install! I just need my phone to be stable enough to know I can send an SMS to someone without it restarting! If you need to know about Kernels or radios or anything please just ask me (and tell me where I can find out!) Like I said, I’m a noob when it comes to phones!
Same kind of problems here. Random restarts (no shutdowns) on various roms, including the original stock froyo. Happens mostly while installing stuff from the market.
Any ideas?
Sounds like the motherboard is faulty/hardware error. Send back to repair. Usually the kernel can cause problems and OCing (restarting), but you said, that it happens randomly on every ROM, so that means it is more likely a hardware problem.
I had this too, same symptoms sent it back to HTC, duff motherboard, back in 14 days and all working fine.
Only thing is it got reset to original contract so had to pay to unlock it and then root etc.
But well worth it!
Hi Guys
Thanks for your replies so far!
So is it likely that my motherboard was faulty all along? I used to get random restarts sometimes when I was on the sense that came pre-installed on the phone, but nowhere near as often as I get now I've rooted and flashed new roms.
Is it possible that I've damaged it in some way? That could get me in some trouble because when I rooted I'd have voided my warranty, if I send it back to Orange as faulty now they'll know and could pretty much tell me tough luck!
I've heard you can unroot and put your phone back to how it was, but they'd still be able to tell wouldn't they?
Has anyone ever sent a phone back for repair through Orange UK?
Thanks again for your responses so far guys!
For me it turned out that the SD card was corrupt in some way. Repartitioned and reformatted it, and this does help for now. Might try that first, before sending into repair.
Good luck!
reynard80 said:
For me it turned out that the SD card was corrupt in some way. Repartitioned and reformatted it, and this does help for now. Might try that first, before sending into repair.
Good luck!
Click to expand...
Click to collapse
I agree. If you have system files on your SD and if the SD gets corrupted you might get the result you've described.
That's interesting, the other night when I had such a severe bootloop that I had to flash a new rom just to get the phone to fully boot up, it only booted after I'd removed the SD card.
To begin with I was very happy because I thought I'd solved the problem and all I'd need was to buy a new SD card, however a short while later it happened again with no SD card inside at all!
I decided to give Ginger Villain another go hoping that removing the SD card after "install zip from SD card > reboot" would allow it to boot up, it didn't. Never got past the alpha rev screen.
How will I know if I have system files on the SD card? Should I maybe try the G-Parted stage of the noob guide again to reformat the card and create the ext-4 partition?
Thanks again for your time and help by the way!
dellaclearing said:
That's interesting, the other night when I had such a severe bootloop that I had to flash a new rom just to get the phone to fully boot up, it only booted after I'd removed the SD card.
To begin with I was very happy because I thought I'd solved the problem and all I'd need was to buy a new SD card, however a short while later it happened again with no SD card inside at all!
I decided to give Ginger Villain another go hoping that removing the SD card after "install zip from SD card > reboot" would allow it to boot up, it didn't. Never got past the alpha rev screen.
How will I know if I have system files on the SD card? Should I maybe try the G-Parted stage of the noob guide again to reformat the card and create the ext-4 partition?
Thanks again for your time and help by the way!
Click to expand...
Click to collapse
If your rom requires an sd-ext partition than it stores system files on the SD. Try a rom that doesn't require that. I would go as far as bringing the phone to stock just to verify if it's the phone or the SD. Bringing it back to stock is a requirement for you to return it for servicing if you realize that it's a problem with the phone not the SD.
paul.c said:
If your rom requires an sd-ext partition than it stores system files on the SD. Try a rom that doesn't require that. I would go as far as bringing the phone to stock just to verify if it's the phone or the SD. Bringing it back to stock is a requirement for you to return it for servicing if you realize that it's a problem with the phone not the SD.
Click to expand...
Click to collapse
Hi Paul, is it only stock roms that don't store system files on the SD or can you recommend a rom that doesn't require an ext partition as I'm not too sure what I'm looking for? I realise that I'll have to unroot before I can return the handset but if there's another custom rom out there I can test before unrooting that'd be good!
However, if you fully recommend returning the phone to stock to test then that's what I'll do!
dellaclearing said:
Hi Paul, is it only stock roms that don't store system files on the SD or can you recommend a rom that doesn't require an ext partition as I'm not too sure what I'm looking for? I realise that I'll have to unroot before I can return the handset but if there's another custom rom out there I can test before unrooting that'd be good!
However, if you fully recommend returning the phone to stock to test then that's what I'll do!
Click to expand...
Click to collapse
This ROM http://forum.xda-developers.com/showthread.php?t=896213 doesn't require SD for system files.
I'd first try the complete stock rom with a completely formatted SD card. You can be completely sure that there isn't a software problem with a custom rom.
If this doesn't work, try replacing the SD card. This did help for me.
If still no succes, send it for repairs.
paul.c said:
This ROM http://forum.xda-developers.com/showthread.php?t=896213 doesn't require SD for system files.
Click to expand...
Click to collapse
Thanks for linking me to that rom.
I did a bit of reading about roms that use ext sd partitions and have so far concluded that its for A2SD so an entire app can be run from the sd card instead of internal memory.
So anyway, I've just installed the Redux rom you linked me to that doesn't store sytem files on the sd, first 2 boots had a sudden shutdown and restart! I'm on the 3rd boot now, it's holding okay but I need to put it through its paces to see how long it can go and what sort of performance it will allow before it starts shutting down on me!
reynard80 said:
I'd first try the complete stock rom with a completely formatted SD card. You can be completely sure that there isn't a software problem with a custom rom.
If this doesn't work, try replacing the SD card. This did help for me.
If still no succes, send it for repairs.
Click to expand...
Click to collapse
Hi Reynard. If the Redux rom I've just flashed (less than 10 minutes ago) doesn't use the sd for system files, then if it keeps rebooting on me would that diagnose a faulty motherboard as reliably as using a stock rom?
I'm gonna unroot and flash a stock rom soon anyway, that way I can be sure before I send it back to Orange for repair, although apparently there isn't an official Orange UK stock rom available so I'm just gonna have to get as close as I can and hope they don't notice!
dellaclearing said:
Hi Reynard. If the Redux rom I've just flashed (less than 10 minutes ago) doesn't use the sd for system files, then if it keeps rebooting on me would that diagnose a faulty motherboard as reliably as using a stock rom?
I'm gonna unroot and flash a stock rom soon anyway, that way I can be sure before I send it back to Orange for repair, although apparently there isn't an official Orange UK stock rom available so I'm just gonna have to get as close as I can and hope they don't notice!
Click to expand...
Click to collapse
Probably there is a ROM just that it hasn't been leaked so I hope you won't get in trouble.
paul.c said:
Probably there is a ROM just that it hasn't been leaked so I hope you won't get in trouble.
Click to expand...
Click to collapse
Haha! Me too!
Dayamn! I didn't have a reboot all day on Redux, got home from work and installed Sygic sat nav software and the phone rebooted 3 times just while downloading the map! I had to remove the battery once as well.
Decided I'd just test Google maps navigation while driving to pick up the Mrs from work and it shut down on me
If I can get hold of another sd card to test I'll see if it makes a difference, but there's not really a lot more I can do now other than unroot and send it back to Orange. The strange thing is that it never used to reboot half as much on the stock rom the phone came with, and it never did it while I was sat nav'ing ever. It just used to happen randomly when I was texting or web browsing. Odd.
Where might be the best place to find the closest to stock rom for Desire Orange UK?
Just wanted to update you all.
I found my original SD card that came with the phone, I fully formatted it and then did a completely fresh install of Redux and performed the same tests and got the same results. Still crashed and rebooted! So that tells me it's the phone and not the card!
I'll be restoring to stock and calling Orange tomorrow to get a replacement / repair.
Thanks to everyone who helped me out along the way, your time and effort is very much appreciated!
Hi guys,
I made a goldcard and tried installing the stock ruu, it seemed to work but when I hold vol down and power on it still says:
AlphaRev
BRAVO PVT1 SHIP S-OFF
HBOOT 6.93.1002
I read on the Alpharev website that recent versions of Alpharev aren't overwritten by stock ruu's hboot so it must first be downgraded. I used android flasher to flash the Alpharev downgrader, then it just froze at the "why so serious" screen. I was advised to flash the stock bravo hboot found on the alpharev website, which I did and then I was finally able to install the ruu. Obviously I've done something wrong and I'm guessing its flashing the stock bravo hboot...
Would it be okay to use android flasher again to run just the downgrader image, and then using fastboot flash the ruu again?
Any ideas? I don't want to risk sending my phone back for repair still saying S-Off!
Okay, I kept reading through XDA and found a post by Dzumagos advising someone to do exactly what I just asked, use Android Flasher to run the Alpharev downgrader image and then reflash stock ruu, so I grew a set and tried it myself!
Bravo PVT1 SHIP S-ON
HBOOT-0.93.001
Voila! I'm now back to S-ON, so now I feel I'm ready to call Orange and tell them about the constant shutdowns and restarts, which have still been happening on stock btw, the phone also feels really hot too!
I just hope the replacement they send me is issue free!
Thanks again to everyone who helped out in this thread and in the orange uk ruu thread!
Cheers everyone!
Ok, so I have a my touch 3G slide. I bought my first one a year ago and it just had to be sent back for a hardware issue. I rooted it and LOVED it. So I get my new phone and root it. Difference is, it came with the new froyo, so it has not cooperated like the first phone. Here is my issue. I know it's rooted, but for the life of me I can't install a new rom! I tried rom mananger and it's like a dead fish. I can download a rom, but nothing happens when I try to install it. If I try from recovery, I get error messages. Like it won't read the zip files on my sd card. oh, and what happened to apps2sd??? I can't even find it in market now. Is my sd card bad? Do I need to unlock boot loader? Is it because I rooted with froyo? I even tried to unroot and i get the same error message. Something about image not found??? Pleased help! I've been searching for hours and have gotten no where.
I believe that you are not rooted. You can't root a MT3GS with froyo on it. You have to downgrade to 2.1 for it to be successful. Also apps2sd is not on the market because most devs don't agree with theirs apps being moved to the sd card so it became virtually useless. You could try the easiest thing which is to get the stock 2.1 rom and just flash it with recovery. Remember to put it on the root of the sd card or it wont be found.
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