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!
Related
Ever since I flashed LeeDroid 1.8b, I've been having this odd problem. I've wiped the phone since and have flashed Open Desire 3.1.0 and I love it but I'm terrified to reboot my phone.
The phone will boot and freeze at the HTC white screen. This happens even if I try to boot into Recovery, (I can hold down vol+down and power button) but as soon as I select Recovery, it will freeze there at the HTC screen.
The only solution I have is to pull the battery and try again. It will do it around 2 - 3 times before it finally boots into Clockwork Recovery Mod SLCD or boot into Open Desire if I don't boot into recovery. This is the same if I decide to REBOOT the phone or power down and boot up.
This problem never happened when I originally flashed Cyanogen. I'm thinking there's still some files or something left that causes this freezing.. I also did a wipe and delete cache before flashing a new rom.
Does anyone else have this problem or help me sort it out?
Edit: Ah shoot.. wrong forum My bad..
no one?
Although Lee newer acknowledged it, I think it has to do with his ROM. I experienced the same issue while running 1.8b, with 1.8c I haven't rebooted by now, but still I have experienced this only after switching to his ROM and I noticed I am not alone on the ROM thread (other people are complaining too about getting stuck at the bootscreen).
I have changed many ROMs (generic 2.1, generic 2.2, pays, adamg ROM...) and never had such an issue, that is why I think it has to do something with lee's ROM.
If you have OpenDesire I would suggest to reboot it just to see how it will go.
Thanks for your response man! The problem is that I've wiped and everything and flashed Open Desire and I'm still experiencing the issue. Is there another way I can completely delete/format any traces of any previous ROM? I believe there's still some sort of remnants of his files left that are causing this!
THanks,
JD
A full wipe can never hurt.
As for freezing at the HTC screen when trying to boot into recovery, I experience this too. What I have found is that if I press no buttons after booting into HBOOT, until HBOOT has tried to load from the SDCard, and THEN selecting Recovery, Recovery boots every time.
However, if I push a button before HBOOT has loaded from the SDCard, I will freeze on the HTC screen regularly.
TheLastOne said:
A full wipe can never hurt.
As for freezing at the HTC screen when trying to boot into recovery, I experience this too. What I have found is that if I press no buttons after booting into HBOOT, until HBOOT has tried to load from the SDCard, and THEN selecting Recovery, Recovery boots every time.
However, if I push a button before HBOOT has loaded from the SDCard, I will freeze on the HTC screen regularly.
Click to expand...
Click to collapse
I will definitely try that.. do you ever have problems booting though? I freeze on the HTC screen during boot up as well and have to do 2 - 3 battery pulls before it finally decides to boot!
I do not, but hopefully a full wipe (data, cache, dalvik, etc) will solve that. Have you tried wiping everything?
I have, but the only wipe I perform is the one in the Clockwork Recovery. Also deleted the cache, but never have deleted or wiped dalvik cache?
I will try this later today and see what happens.. thanks!
TheLastOne said:
I do not, but hopefully a full wipe (data, cache, dalvik, etc) will solve that. Have you tried wiping everything?
Click to expand...
Click to collapse
Just sayin' I've not ever had a boot problem like this with LeeDrOiD. Running 1.8c at the moment.
Ditto.. No issues, its not a rom issue, you may have bad blocks on your nand.
Sent from my HTC Desire using XDA App
Tawm said:
Just sayin' I've not ever had a boot problem like this with LeeDrOiD. Running 1.8c at the moment.
Click to expand...
Click to collapse
I believe it was an issue with 1.8b..
LeeDroid said:
Ditto.. No issues, its not a rom issue, you may have bad blocks on your nand.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Hmm.. anyway to confirm this? It's a brand new device, barely two weeks old and never had this issue until I flashed 1.8b.. I'm going to try to wipe it completely and go from there, hopefully that solves the issue.
What's a nand?
Hi Quazis,
I have had a very similar problem with my Telstra desire after rooting and installing a Lee based rom called NexTSense. After that I installed Open Desire and experienced the same problems.
I am just now re-rooting my phone and going to install Pinky.
Just out of interest are you running on the 850mhz Rogers network? If so have you updated to the latest radios (5.09.20 I think?)? Telstra runs off this frequency also and I think it may have something to do with incompatible radios. -- Can anyone confirm this?
If this is the case maybe try Open Desire without updating the radios?
Hey,
We got the A8182 version of the Desire which has 850/1900 (I believe), so both bands that run on 3G.
Before I flashed LeeDroid, I had updated the radio (.20) and was on Cyanogen nightly build. I had no booting problems with that ROM, but I wanted something a little more stable. I modded it as well and the phone booted up no problem, also into recovery.
Once I flashed LeeDroid, that's when my problems arose. I only wiped/formated data and the cache.. I never formated that dalvik cache. I will wait until Open Desire 3.2.0 releases today and try that a full wipe/format.
Another member said he doesn't touch anything on the phone when he boots into recovery until the phone does the SD card check.. I tried it once and it went into recovery with no issues so maybe pressing buttons before the SD check does something??
I don't, but I did a full flash, and used my separate test sd card.
plasmafire said:
I don't, but I did a full flash, and used my separate test sd card.
Click to expand...
Click to collapse
I'm going to do this.. thankfully I have't customized my phone a lot so I'm going to format both the FAT32 and EXT3 partitions and full wipe.. to do a full wipe.. there's only data/factory, cache, davlik cache and battery stats correct? If I wipe those 4 items in Clockwork, that's considered a full wipe?
JD
Full flash wont help. I know because I did it.
I am to lazy from installing different ROMs, resetting my device, etc... so I will leave it as it is for now (LeeDroid 1.8c), and will try to reboot it as rare as possible (bootscreen takes a while, bootloop is possible too). But when I'll have some more time I will re-root and install another ROM and I am sure the issue will be gone.
Lee, nothing personal (in the end, I am using your ROM right now) but I think you should read more carefully the thread about LeeDroid. You will see many people get stuck at the booscreen and/or their devices keep rebooting with this ROM.
I don't have this issue with the same ROM as you.
-----------------------------------
- Sent via my HTC Desire -
Yes, not everyone has that problem (in that case we wouldn't need to talk about it - we would KNOW it). Just some people have this issue with that ROM. I would say 5% of the people have the bootloop problem, and 10% of the people have longer-than-average the bootscreen.
Still, it worths taking a look since 3-4 people from 10 participants on this thread say they have this problem with -this- ROM.
My 2 cents.
ljesh said:
Full flash wont help. I know because I did it.
I am to lazy from installing different ROMs, resetting my device, etc... so I will leave it as it is for now (LeeDroid 1.8c), and will try to reboot it as rare as possible (bootscreen takes a while, bootloop is possible too). But when I'll have some more time I will re-root and install another ROM and I am sure the issue will be gone.
Lee, nothing personal (in the end, I am using your ROM right now) but I think you should read more carefully the thread about LeeDroid. You will see many people get stuck at the booscreen and/or their devices keep rebooting with this ROM.
Click to expand...
Click to collapse
Why won't a full flash help? I don't have LeeDroid anymore, I had it for about 10 minutes because I didn't like it. I've since gone to Open Desire and the issue still persisted.. but it never happened when I had Cyanogen installed.
I'm scared to re-root because it requires a reboot and sometimes the HTC screen never goes away.. lol
hey there, its intresting to see that you have the same problem as me,
http://forum.xda-developers.com/showthread.php?t=755835&highlight=Recovery+Issue
the people who are saying they dont have a problem, i'd like to know what recovery you are using?
and what hboot you orignally came from, i.e. do you have a SLCD screen? and how did you root?
because it is now becoming obvious that leedroid rom is causing this issue as a lot of people are having problems.
during the weekend i will try flash the RUU for WWE with the hboot 0.83 included (using gold card)
and start from scratch and flash another.
no disprespect to the developer of leedroid, his work is good. just a lot of people on hboot 0.83 with the SLCD screen have issues.
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!
So I was running Synergy + God Mode and today my phone decided to reboot itself. Well not it keeps locking up at the htc EVO 4G white screen or sometimes will get as far as the Synergy splash screen but will just loop.
So to back up a bit I previously had moved the Dalvik cache to the sd card as well as most all apps. This has been running fine for weeks.
I was able to get it to boot once after I removed the sd card but now it won't even with that. I tried wiping the phone from recovery and still nothing.
Any ideas? this is annoying. I've never run into an issue this bad before. I've always been able to repair either with a nandroid backup or just a wipe.
I tried restoring a nandroid backup and it just sat there with the lines getting longer and longer 1 dot at a time. Actually filled the whole screen and never actually finished.
Try a RRU
Sent from my PC36100 using XDA App
I would try an RUU.exe
Which HBOOT do you have? If you can get to HBOOT, then you should be able to go back to stock and solve most problems
I'm running the 0.76.200 HBOOT.
I will probably end up having to go back to stock but would like to keep that as a last resort.
I think I narrowed down my problem. Anytime I go into recovery and try and wipe anything that has to do with the ext3 partition it either locks up or for instance I'm now trying to repair the ext3 partition and it just keeps adding dots. Just keeps working and seems to get nowhere.
I can still access everything else on the SD card just errors of sorts when dealing with the ext partition.
well got it working after RUU but i still wish I knew what caused it in the first place
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
Okay this is really getting on my nerves and I've never had this much problem from a phone. I've been modding and helping develop for years, but I've never had this issue. So for five days now, I've been playing around with my old DINC that my daughter messed up somehow, and I can't install a ROM and make it work to save my life. I've run countless ROM's on this thing in the past with no issues. The problem now is, no matter what recovery I use or what I wipe, all of the old apps keep showing up on boot and crashes the phone. Meaning while it says "Android is upgrading" it shows every app that has ever been installed on this phone, even though I wipe and format every partition, and I haven't installed a single app. Heck... I can't even get into the system to install an app. The furthest I've gotten on a clean install is to pick a launcher in Carbon, but then it reboots.
Someone please help with a solution if you know one. I would hate to make a mess on the concrete outside with this phone, but I'm almost to that point. Thank you in advance!
ludeawakening said:
Someone please help with a solution if you know one. I would hate to make a mess on the concrete outside with this phone, but I'm almost to that point. Thank you in advance!
Click to expand...
Click to collapse
What recovery are you running?
I've been using CWM 5.0.2.0 since 2011 and haven't had an issue, and I still flash things on it. I found an active mediafire link with it from a post on Rootzwiki that is flashable through HBOOT. Just put it on the root/top level of an SD card formatted FAT32 and it will load the recovery image, press volume up to flash it, then you should be on an up to date recovery and you can try wiping from there. I had issues with some of the older ones and TWRPs earlier versions.
I'd also recommend CyanogenMod 7.2 stable, but that's just what I've ran the last few years. Never had an issue with it and it is stable as can be. Always a good start. In fact, it's more stable than stock on my phone, plus I over clock a bit.
It's a good device to have around when you have to send in your current device for exchange or damage it etc. I used it full time not long ago while exchanging my M8.
BrettApple said:
What recovery are you running?
I've been using CWM 5.0.2.0 since 2011 and haven't had an issue, and I still flash things on it. I found an active mediafire link with it from a post on Rootzwiki that is flashable through HBOOT. Just put it on the root/top level of an SD card formatted FAT32 and it will load the recovery image, press volume up to flash it, then you should be on an up to date recovery and you can try wiping from there. I had issues with some of the older ones and TWRPs earlier versions.
I'd also recommend CyanogenMod 7.2 stable, but that's just what I've ran the last few years. Never had an issue with it and it is stable as can be. Always a good start. In fact, it's more stable than stock on my phone, plus I over clock a bit.
It's a good device to have around when you have to send in your current device for exchange or damage it etc. I used it full time not long ago while exchanging my M8.
Click to expand...
Click to collapse
I've tried every recovery you can think of for this device. All versions of the CWM and TWRP touch and non-touch, including CWM 5.0.2.0. And I use HBOOT to flash all of the recoveries. It doesn't matter what ROM or recovery I flash, I still get the same results. And the ROM I used the most on this phone was Condemned CM7.2, but like I said, it won't matter how stable a ROM is, I can't get it to boot to even use it now. For some reason there is a partition somewhere that will not wipe. I've used VR Superwipe, which was recommended on some ROM's in the past, but it doesn't help at all either. No matter what, while booting for the first time, it still shows every app that has ever been installed to this device over the years, which causes everything to crash or just immediately reboot. All of the apps crash even if I go back completely stock by flashing a PB31IMG of stock firmware with HBOOT. That includes trying it with S-ON and S-OFF. As you can tell, this isn't my first rodeo at all. Lol
I've been doing this for years and have helped develop ROM's on a couple of sites, but I've never seen or heard of anything like this. Thanks for the input though.
I guess I'll risk completely bricking it, and manually re-partition the device and push the bootloader and everything else to it with ADB Shell. I've got nothing to lose, it's already a paperweight that just lights up. Haha
ludeawakening said:
No matter what, while booting for the first time, it still shows every app that has ever been installed to this device over the years, which causes everything to crash or just immediately reboot.
Click to expand...
Click to collapse
Sounds like a bad NAND to me (like one partition is fried and is now read-only). Good luck with the repartitioning. If you're feeling adventurous, you could try this. If you're feeling really adventurous, I seem to remember reading a post from someone who had actually unsoldered the NAND chip and got the phone to boot using only an sdcard. I can't find the post right now though.