I just got a new replacement Evo and rooted it yesterday. I installed miui 11.19 rom and set it up. I was planning to use a new memory card, so I inserted it and through amon recov, chose wipe partion, but I don't think that's where the problem happened. At the same time, I went to flash a new kernel the invisible one and also wiped cache/dalvik. After I do that, my phone just stays at the white screen upon reboot. I went back into recovery and tried to reflash the same rom but I was getting a weird error "failed... error at line 4". I put in my old memory card, but had the same problem. I had an old rom that was already on the card that somehow happened to work. I wiped all before I did that.
After that flashed successfully, I tried to flash Myn's RLS4, but it gave me a different E: error. Once again I had to flash an old rom. I don't think it is the memory card that is the problem, but maybe... possibly something to do with the way MIUI is installed maybe? Do I need to reformat? But it did it on a fresh memory card as well. Possibly something went wrong in the rooting process?
What do you guys think?
Wish I could help you on this but I am still new to ROOTing and I dont want to say some thing about something I know nothing about, But I can offer a few suggestions. Try to restore your old ROM. See if you still have the same problems and if you DO, Then logic deduction would lead me to think that its the miui ROM... maybe that ROM and your kernel are not compatible?
Did you flash a kernel or theme before you let the Rom load up or is this happening with just the Rom?
Sent from my EVO at the edge of Hell
If its a newer evo, late 003 or 004 version than your unit has the new camera hardware and will require the latest htc kernel. If the rom you are flashing doesn't use the stock kernel then your phone may not boot up properly or hang at the first screen.
Related
Ok, so I did unrevoked and have an unrooted phone. Started to get bored with the stock 2.2 and wanted better battery life.
My Dinc has an SLCD screen. So, when I go into the standard clockwork recovery, it goes to a black screen with white bars on the side. I had to do a custom flash recovery for my phone through unrevoked/flash. I then did a nand backup.
Tonight, I downloaded MIUI and attempted to install through the recovery flash. I ended up getting errors. So, I then thought that I needed to go through the ROM Manager app.... when I tried to flash the ROM, it automatically switched my recovery back to the Clockworks recovery..... then tried to go into the recovery portion of the ROM flash. Needless to say, I had to do a battery pull. Now when I try to do a normal boot, the phone freezes at the white screen that reads "HTC Incredible". If I boot into recovery... I can get to the hboot screen with the three droids at the bottom, but a script comes up on the screen and I think that it says something about no image... from there I can navigate around the recovery menue, but nothing works for me getting past this. If I go to recovery, it just keeps going to the black screen with the two white bars.
Is there anything that I can do. I am wondering if it is trying to flash the ROM everytime it comes on.... but this recovery method is not working on my phone.
Any help would be greatly appreaciated!
I believe you need a special clockwork recovery for SCLD screens. Not exactly sure where to find it on here, but it should be hanging around somewhere. I hope I helped ya out a bit, good luck.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.
OK, so I was working a 24 hour shift yesterday when I posted this... unable to download any zip or exe file (damn firewalls)... This morning I was able to remove the miui zip from the root of the sd card via card reader. I then copied the PPB31IMG.zip to the root of my sd card. Then booted into recovery. I asked if I wanted to flash this file, I said yes and then it gave me the correct recovery menue. from there I was able to choose the recovery image that I had created yesterday. It seemed as though it was going to work, booted up to a stock rom that required manual setup (like on a new phone). Then I started to get FC's all over the place. I was able to find on my sd card two other nandroids that were saved in a different place than the only one that recovery allowed me to choose from. I moved the newly found recovery folders to the same location as the first and now I had those recovery options listed. I chose one from last week and thankfully my phone is restored and working.
I am not sure if this information will help anyone with an SLCD Dinc. There seems to be a huge difference in how these phones react to roms and tweaks. I am very hesitant to attempt any other ROMs at this time. On my eris, I flashed about 30 different ROMs and about 5 differnet radios. I am not new to this, but this SLCD Dinc has been a headache.
Any Aosp rom on an Slcd takes a different kernel. Get yourself the koush test#2 kernel and just keep it on your sd card. Flash it everytime you do a AOSP rom.
Sense based roms all seem to be ok as the kernel was built with Slcd in mind.
Well I'm glad you got it back up and running. I've heard about them not working well with some roms, I didn't know it was with all asop roms.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.
doug piston said:
Any Aosp rom on an Slcd takes a different kernel. Get yourself the koush test#2 kernel and just keep it on your sd card. Flash it everytime you do a AOSP rom.
Sense based roms all seem to be ok as the kernel was built with Slcd in mind.
Click to expand...
Click to collapse
Thanks for the info on the AOSP roms. I did not know either. I wonder if there is a way to make the AOSP roms to support it by providing the new kernal in the flash or at least making a note on the AOSP ROM forum page that states the issues with SLCD Dinc's and what needs to be done to avoid problems. I would venture to say that anyone new to this stuff and was feeling brave would not be able to figure out how to restore there phone when it was acting the way mine was. Just my 2 cents.
Thanks again for the info.
Hey guys, I was wondering if you all could help me with an issue I've been having lately.
For some reason, I can't flash any ROMs. When I do, it hangs and hangs and hangs on the Splash Screen. It hasn't always been this way, everything worked just fine until last month I flashed MIUI. It worked, but after I decided I didn't like it, I couldn't flash any new ROM, and none of my backups worked until I wiped data and what not.
I've reformated my SD card, and I still can't flash any new ROMs. Help?
I'm kind of worried that if I decide to flash the stock 2.3 update when it comes, I'll brick my phone.
I struggled with my phone for three days trying to flash roms recently. At one point I went to an older version of CWM 3.0.0.5 and it worked once, but then it stopped flashing again.
Tried Amon_Ra and didnt have any luck either due to signatures or something. Went back to CWM 3.0.0.8 and havent had any problems since. CWM must be messing up every once in a while or something.
Good Luck
Sorrows said:
Hey guys, I was wondering if you all could help me with an issue I've been having lately.
For some reason, I can't flash any ROMs. When I do, it hangs and hangs and hangs on the Splash Screen. It hasn't always been this way, everything worked just fine until last month I flashed MIUI. It worked, but after I decided I didn't like it, I couldn't flash any new ROM, and none of my backups worked until I wiped data and what not.
I've reformated my SD card, and I still can't flash any new ROMs. Help?
I'm kind of worried that if I decide to flash the stock 2.3 update when it comes, I'll brick my phone.
Click to expand...
Click to collapse
I've had the same problem then someone suggested I flash a temporary 2.x clockworkmod to whipe bc clockworkmod 3.x has reported issues of not wiping completely.
Here's the zip I used, flashing will temporarily give 2.5.1.2. When you reboot, it will be back to whatever you had before. Also try repeatedly wiping data, cache, dalvik 3x or more. Hope this helps
http://forum.xda-developers.com/attachment.php?attachmentid=549325&d=1300835217
MojoRisin011 said:
I've had the same problem then someone suggested I flash a temporary 2.x clockworkmod to whipe bc clockworkmod 3.x has reported issues of not wiping completely.
Here's the zip I used, flashing will temporarily give 2.5.1.2. When you reboot, it will be back to whatever you had before. Also try repeatedly wiping data, cache, dalvik 3x or more. Hope this helps
http://forum.xda-developers.com/attachment.php?attachmentid=549325&d=1300835217
Click to expand...
Click to collapse
And that could cause it to hang on the Splash Screen?
Sorrows said:
And that could cause it to hang on the Splash Screen?
Click to expand...
Click to collapse
I'm just speaking from personal experience.. it can't hurt.
Is your hboot version .92?
Sent from my ADR6300 using XDA App
INCREDIBLEC XD SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.07.28
And it could hurt actually, because it is incredibly difficult for my phone to restore even.
Also, I can't flash the alternate recovery for some reason. Every time I try, it says there was an error.
Sorrows said:
INCREDIBLEC XD SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.07.28
And it could hurt actually, because it is incredibly difficult for my phone to restore even.
Also, I can't flash the alternate recovery for some reason. Every time I try, it says there was an error.
Click to expand...
Click to collapse
You know.. its interesting that you mention this..
I have been following the CM7 nightlies for a while, and got fed up at one point and just stuck with one of there nightlies. Well... I noticed I couldn't flash ANYTHING at one point. Couldn't upgrade the kernel, radio, ROM... it would all cause it to hang up at the boot screen. I had to get EVERYTHING back to exactly how it was and then restore the most recent image I had created. It's the only thing that will work on my phone as of now. I wonder what happened, I feel like the phone lost its writing ability or something..
I had a similar problem a while back. I had a 2GB laying around as a spare, made sure it was formatted on my comp FAT32 and then put whatever ROM I wanted on it and tried it from there. It stopped the looping issues I was having. So I saved all my stuff from my daily SD card (16GB) and formatted that and put it back in the Inc and I haven't had a problem since. Maybe try a new SD?
Hypcrsy said:
I had a similar problem a while back. I had a 2GB laying around as a spare, made sure it was formatted on my comp FAT32 and then put whatever ROM I wanted on it and tried it from there. It stopped the looping issues I was having. So I saved all my stuff from my daily SD card (16GB) and formatted that and put it back in the Inc and I haven't had a problem since. Maybe try a new SD?
Click to expand...
Click to collapse
Your right, I think I'm going to try another SD card... or back this one up and format it...
But the weird thing is I can flash tweaks to the ROM, but I can't change kernels, ROM, radio.... without it getting stuck on the splash screen...
But I'm gonna go ahead and try another SD, because I had another SD that messed up on me, and it gave me similar issues. I just haven't had any problems with this one... so yeah.
If that doesn't work, you might try doing an RUU completely back to stock. then try flashing a new ROM.
Good luck!
As title says,
Htc evo
0003
Android version 2.2
Baseband 2.15.00.11.19
Kernal 2.6.32.15 netrchy-toastmod -4.1.9.1
Rom myns warm twopointtwo rls5
Was running android 2.3
With miui rom 1.7.8
With shell 3d
Woke up this morning, went to turn on wifi and nothing happened.
Went to homescreen, pressed menu , settings, wirless, wifi , checked the box
It tried to turn on for ten seconds or so and then said error right under the wifi box.
Made me go
Went to rom manager, loaded last back up (clear dalvik and cache)
No dice..
Flashed new miui rom
Then cm7
Then older miui
Then older cm7....
Then warm....
Flashed 2 dif kernals to fix the problem,
Still, no dice...
Checked xda, android forums, google, craigslist...
I give up
Any help would be greatly appreciated
Just relized bluetooth no worky either
Maybe it's time to try a 100% clean wipe and re-flash.
Give Synergy a shot, because it's awesome (link below) and while you're at it, format and partition your SD card. This will ensure a very clean wipe of the SD (make sure you back up important files onto your computer, like your nandroid backups or CM backups). Wipe the usual cache/dalvik and everything else 3 or 4 times, and then load the ROM up. See if it fixes it.
Synergy: http://forum.xda-developers.com/showthread.php?t=1144447
Formatting/partitioning procedure: http://forum.xda-developers.com/showthread.php?t=1158993
Sell it. Get an HTC HD2.
just did 2 100% clean wiped, i manually wiped everything...
cache
davlik
data
then again manually in recovery settings
flashed said synergy rom,
which by the way is slow,
running an older version of android...
and old sense..
anyhoo, still,, when i check the box for wifi, it tries, then says error..
just tried timat kernal with miui rom<--by far best romm m
next is stock rom and stock kernal, which i cant find :/ go figure
eyeisdasteve said:
Sell it. Get an HTC HD2.
Click to expand...
Click to collapse
post whoreing my thread steve?
Do you have an old nand backup you could restore to? That might be worth a shot.
Both of those issues happened to me once when I used an incompatible kernel with one of my roms, but as soon as I did a nand backup, I was fine.
bradleyw801 said:
Do you have an old nand backup you could restore to? That might be worth a shot.
Both of those issues happened to me once when I used an incompatible kernel with one of my roms, but as soon as I did a nand backup, I was fine.
Click to expand...
Click to collapse
i don't , wish i did...
im stuck...
just put it all to stock and cracked a beer , your move evo
So I was having issues with MikG and my settings.... Reinstalled aosp system apps by accident over sense system apps and it kept popping up with error messages....
So I wiped everything and reflashed MikG 3.xx and it boots up... But all I see is the wallpaper and status bar. I see no clock/apps, and am never prompted with entering my google info and whatnot.
I also deleted the ROM and put it on again thinking it might be corrupt but I still get this problem. Wtf just happened? Did I just brick my phone?
Gonna try and flash my old Deck 1.3d rom and post back with results
Naturesretard said:
So I was having issues with MikG and my settings.... Reinstalled aosp system apps by accident over sense system apps and it kept popping up with error messages....
So I wiped everything and reflashed MikG 3.xx and it boots up... But all I see is the wallpaper and status bar. I see no clock/apps, and am never prompted with entering my google info and whatnot.
I also deleted the ROM and put it on again thinking it might be corrupt but I still get this problem. Wtf just happened? Did I just brick my phone?
Gonna try and flash my old Deck 1.3d rom and post back with results
Click to expand...
Click to collapse
did you factory reset wipe?
I factory reset from within amon ra and wiped each thing individually as well. Flashed the full wipe version of MikG 3.11 and it proceeded to wipe everything again. Everything installs fine, but when it boots, it just shows the MikG walpaper, and the notification bar. No apps, no clock, no new user "welcome to android" prompt either. All I can do is turn the screen on and off.... I have to pull the battery to turn the phone off.
Putting my Deck 1.3d nandroid on my sd card as I type and am going to flash in just a minute to test and see if I can even boot anything...
Naturesretard said:
I factory reset from within amon ra and wiped each thing individually as well. Flashed the full wipe version of MikG 3.11 and it proceeded to wipe everything again. Everything installs fine, but when it boots, it just shows the MikG walpaper, and the notification bar. No apps, no clock, no new user "welcome to android" prompt either. All I can do is turn the screen on and off.... I have to pull the battery to turn the phone off.
Putting my Deck 1.3d nandroid on my sd card as I type and am going to flash in just a minute to test and see if I can even boot anything...
Click to expand...
Click to collapse
You sure you got the FULL WIPE version? If you flashed the UPDATE version you will get these exact same problem.
I got both.... originally thinking it was an update TO the ROM itself. (idk why lol) Decided to keep it for if I ever have to reflash the main rom due to a user error....
But no, I made sure I was flashing the full wipe version. You think I should redownload again and try it out? I had the file saved on my friends laptop and hadn't touch it since I put it on my SD card so.... figured I could just delete the one on my SD card and retransfer
Just restored my Deck 1.3d and its booting as I type. Will post back with details.
Naturesretard said:
I got both.... originally thinking it was an update TO the ROM itself. (idk why lol) Decided to keep it for if I ever have to reflash the main rom due to a user error....
But no, I made sure I was flashing the full wipe version. You think I should redownload again and try it out? I had the file saved on my friends laptop and hadn't touch it since I put it on my SD card so.... figured I could just delete the one on my SD card and retransfer
Click to expand...
Click to collapse
I'd do a complete wipe on everything and start from scratch. I just got a new SDcard and formatted it and did a fresh install of MikG 3.11 and it runs like no other.
Back up your SDcard to a PC and format and start fresh. I noticed a HUGE difference in function and performance although it sucked loading almost 10gigs of music back on.....lol
you think it might be an error on the sd card like a bad sector?
Just booted back into Decks.... Although the backup of my sd:ext didn't take apparently and it's stock Decks.... Kinda odd; No apps or anything. Or is that supposed to happen? Same wallpaper though....
Gonna try and reflash MikG and if it still doesnt work I'll follow your method. Would rather not as I did that a few months ago when I partitioned my SD card for a2sd lol...
Will post back with results
Redownloaded and flashed MikG full wipe. Its good now. Thanks to you anyway.
I just flashed the newest version of the codename rom (JustLoveCodename-Android-(Alpha1)2.0.0-RC to my epic 4g touch. I also flashed the Google apps pack that comes with it. It seemed nice at first, but then I tried using the market and it just kept telling me there was a server error. I tried re-downloading it from third party sites but nothing was working. So I went to flash back to Calkulins rom. As I got into recovery mode, it seems the phone somehow changed itself to another recovery system (It might've been CWM) instead of the rogue one I had prior from the initial root process. I tried flashing anyway and the a picture of a dead android with his front opened up and a red exclamation popped up. I rebooted the phone to see what would happen. It brought me right back to Code name's rom. I tried it 3 more times yet the same thing happened every time. I also tried a battery pull. It did not work. I am thinking of doing one of two things: I am going to either go through the initial root stages again or I am going to try to delete the Codename rom from my SD card and try flashing another rom (preferably Calkulin). Please tell me if this is the right thing to do or if there is another method of fixing this problem. Thank you for taking time to read this. I really appreciate any help. FYI: My phone is still in working condition, but I am stuck using the Codename rom which I really do not want to use anymore. I just was able to get ES file manager working and i checked my external sd folder, but there is nothing in it. When i look at my storage from system settings, it says i still have the memory on it. So why is ES not displaying it? =( I re-installed rogue cwm and flashed calkulin's rom again and everything is fine. Heed my advice and be wary of the Codename Rom. Editor's, you can delete this thread if you wish. =)
Gzerner said:
I just flashed the newest version of the codename rom (JustLoveCodename-Android-(Alpha1)2.0.0-RC to my epic 4g touch. I also flashed the Google apps pack that comes with it. It seemed nice at first, but then I tried using the market and it just kept telling me there was a server error. I tried re-downloading it from third party sites but nothing was working. So I went to flash back to Calkulins rom. As I got into recovery mode, it seems the phone somehow changed itself to another recovery system (It might've been CWM) instead of the rogue one I had prior from the initial root process. I tried flashing anyway and the a picture of a dead android with his front opened up and a red exclamation popped up. I rebooted the phone to see what would happen. It brought me right back to Code name's rom. I tried it 3 more times yet the same thing happened every time. I also tried a battery pull. It did not work. I am thinking of doing one of two things: I am going to either go through the initial root stages again or I am going to try to delete the Codename rom from my SD card and try flashing another rom (preferably Calkulin). Please tell me if this is the right thing to do or if there is another method of fixing this problem. Thank you for taking time to read this. I really appreciate any help. FYI: My phone is still in working condition, but I am stuck using the Codename rom which I really do not want to use anymore. I just was able to get ES file manager working and i checked my external sd folder, but there is nothing in it. When i look at my storage from system settings, it says i still have the memory on it. So why is ES not displaying it? =( I re-installed rogue cwm and flashed calkulin's rom again and everything is fine. Heed my advice and be wary of the Codename Rom. Editor's, you can delete this thread if you wish. =)
Click to expand...
Click to collapse
K. The reason you aren't getting to the old version of CWM is because you flashed Codename. Codename is an AOSP ROM which has been known to cause bricks when flashing with Rogue. Because if the bricks the developers opted to but include CWM of any kind in the kernel. What you need to do is find a replacement ROM and download it. Once you've downloaded it you need to flash the EL26 stock CWM (you can find it in the OP of the link below) then use it to flash your new ROM.
http://forum.xda-developers.com/showthread.php?p=295021
Well you're at it is suggest reading the How Not To Brick Your Phone thread in general.
Good luck!
Codename rom is an AOSP rom so your external SD storage will be under /emmc and not /sdcard/externalsd. That's why it wasn't showing up. Same thing with CM9 and AOKP, not because it doesn't work. Also I wouldn't recommend flashing anything ICS related from rogue recovery, js.
And recoveries changed because with our phones, the recovery is packed into the kernel itself so when you flashed Codename, the recovery changed to the stock recovery included with the roms kernel. Hope that clears it up lol.
Sent from my SPH-D710 using Tapatalk
If you want a fresh install, the best way is to Odin the el29 kernal. From there, get into your recovery and wipe and flash away.
Sent from my SPH-D710 using XDA