So I've done some searching, and have yet to find a solution to the issue I'm having. GF's phone is the HTC Incredible as you can probably already guess by what subforum this is posted in. It's been running the CyanogenMod 7.1.0 Rom for quite some time alright. From everything I've seen, most people that have had issues with bootloops is because they have been flashing to a new rom/radio and skipped something/pulled the battery/or something along those lines. This phone has been running fine, and then out of nowhere I guess, started to restart itself continuously yesterday. I can get into HBOOT no problem, but that's about it. When I try to select Recovery, it just kicks right back into the bootloop. Anyone have any suggestions??? Phone isn't under warranty anymore, and her contract ends in a month and a half, so we don't want to have to buy a new phone before then if at all possible.
try reflashing recovery.
first start with a freshly formatted FAT32 sd card, download this file and place it on it
http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
this should be the only file on your SD card. now turn off your phone and put the sd card in. now boot into hboot (vol down+power) and it should prompt you to update by pressing vol up. do this and when it boots back into hboot, remove the sd card and delete the file. then try booting into recovery
Tried it and still no change
there was a similar situation (stangely similar ) here
http://forum.xda-developers.com/showthread.php?t=1628585
both cases happened to be running cm 7 too...and randomly started boot looping and stuck with no recovery.
i would read through that thread and see if any of the steps will help you
Just read threw it all, and everything sounds exactly like it does in my case. That one ended up not so well. Do I just assume that this one is done as well???
downwardzspiral said:
Just read threw it all, and everything sounds exactly like it does in my case. That one ended up not so well. Do I just assume that this one is done as well???
Click to expand...
Click to collapse
you can try doing the steps in that thread. you may have better luck. Perhaps someone else on this board knows of another method that may help
Just because it didnt work for that guy, dosent mean it wont work for you. Are you s-off? Have you tried reflashing recovery yet?
it's S-Off and I've tried to reflash recovery
How about an ruu?
tried that. tried through the pc and the computer wouldn't recognize it. tried by updating it in HBOOT, and after the update, it would still just bootloop
Sounds like another possible hardware failure. My only other sugestion would be to try the fastboot flash of the misc img, but it probably wont work either. Its very strange, i have seen this 4 or 5 times now in the past couple months, all on cm7, and all unfixable. I dont want to start a war, but mabey something with cm7 or cm7 and a certain program or combination of programs, is causing this. Or mabey its just cause these phones are getting up there in age.
i too find it odd each one is cm7..
Well thanks for all the help anyways. A new phone it is I guess
the basic problem is CM 7 (for the Dinc). it is extremely common. i have seen it happen to so many people now. it drives me insane when i see people suggesting CM 7 "stable" to others (for the Dinc). i have tried to communicate this here and other places too... i have given up hope of people ever accepting this obvious situation. the "stable" version of CM 7 is simply not stable.
however...
a reflash of clockwork recovery has always gotten people out of the CM 7 bootloop. then they are able to get a working rom installed.
i don't understand why you can't get a recovery re-flashed.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
Related
Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...
2) Anyone know how to turn S-(back)ON in my current situation?
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )
First...... Wrong subforum. Try Q and A.
Second, in all your rom flashing, did you maybe forget to wipe, and re-wipe before your rom install?
Ah piss. I'll move subforums. Also, the last flash I ran (from Evervolv Gingerbread -> MIUI 1.1.07) I am quite certain I wiped. I may be mistaken, but non-wiped user data shouldn't bork recovery.
Happened to me when trying to root my brothers Evo. (Already had mine rooted). I thought the phone was bricked because there was no recovery installed and all that worked was hboot. I tried several different versions of PC36IMG.zip until 1 finally worked.
Cheers
Yes! try updating with PCM36IMG.zip ROm that should help you out, ex "Sprint lovers". Good luck.
sidiasus said:
Ah piss. I'll move subforums. Also, the last flash I ran (from Evervolv Gingerbread -> MIUI 1.1.07) I am quite certain I wiped. I may be mistaken, but non-wiped user data shouldn't bork recovery.
Click to expand...
Click to collapse
Recovery thing confused me a little bit. I didnt get in your post where that became a problem. If a phone bootloops all on its own, its usually due to wiping either not being done, or a certain recovery not wiping it correctly. At least that's what ive seen in all my reading. Hope you get this ironed out.
Mikedick said:
Recovery thing confused me a little bit. I didnt get in your post where that became a problem. If a phone bootloops all on its own, its usually due to wiping either not being done, or a certain recovery not wiping it correctly. At least that's what ive seen in all my reading. Hope you get this ironed out.
Click to expand...
Click to collapse
No problem, I tried to write in a more humorous style than the other "HALP" threads, and my ability to clearly relate the important details suffered. Thanks for the good wishes!
Etiquette question: I've duplicated this thread in Q & A, should I just delete this one?
Also, thanks to all for the lightning fast responses, trying more PC36IMG'ses.
Nah, just let it die.
Found like you're radio fried, it's a well known defect on some evos and incredibles. Try to put it in the fridge while turned off and afterward it may run for long enough to turn s-on.
Sent from my PC36100 using XDA App
T-Mobile G2 Bootloop
I have a T-Mobile G2 which is bootlooping on CM7 and Virtuous GLite 1.0.1. I have been running CM7 without problems since it was released. The bootloop started during the night without any prior symptoms. I have searched the xda and other sites extensively for days and tried so many things to fix this, some of which I was unsure about, but figured 'what the hey' since I had such limited success reflashing roms, clearing data, dalvik cache, etc...
Here is some information:
If I immediately put the phone in airplane mode upon bootup while running CM 7.03 it will not go into bootloop. I can use it indefinitely in this state (it seems) but there is only so much fun you can have in airplane mode...
With CM7.03 installed, here is the info from my 'about phone' section:
Model: HTC Vision, Android Version: 2.3.3, Baseband Version: 12.28b.60.140eU_26.03.02.26_M, Kernel Version: 2.6.32.40-cyanogenmod [email protected] #1, Mod Version: CyanogenMod-7.0.3-vision, Build Number: GRI40
I have Rom Manager v4.2.0.2
-----
Some other information:
I am, however, able to run another mod, Stock w/root (http://forum.xda-developers.com/showthread.php?t=836042) which I was able to flash, along with pershoot's kernel (http://forum.xda-developers.com/showthread.php?t=847672). When I run this mod I am not able to activate WiFi. I click to enable it and after a few seconds I get an error and it turns itself off.
Interesting to note- the first boot-up after flashing CM7 I get about 20-30 seconds before it starts bootlooping. During this time I tried to quickly activate WiFi and it errored out the same way is it did running the "Stock w/root" mod listed above.
This made me think (in my limited knowledge) that it could be related to a radio issue... so I tried to flash a couple different radios claiming to be for the G2/desire. No luck there.
-------
I am able to access recovery mode, flash roms, restore roms, etc...
-------
The bottom line for me, I want to run CM7... I know it works(ed) on my phone. How many layers do I have to strip away to get to the point that whatever bad thing is causing my phone to do this with multiple roms is gone?
Rom? Kernel? Radio? what else is there to fix? Any suggestions on where I go from here? What about the no WiFi issue?
I have already searched the forums as I stated, so linking the first 'G2 bootlooping solved' thread you can find probably wont help me. Maybe understanding more about what could be causing this so I can have a direction to persue this further would be most helpful.
Thanks very much!
Did you wipe your phone before applying CM7?
re: did you wipe your phone
blackknightavalon said:
Did you wipe your phone before applying CM7?
Click to expand...
Click to collapse
Yes- in recovery mode I performed a wipe, then cleared cache and dalvik cache before flashing.
---------
Also, to add more info to the original bit of information I shared- last night I flashed CM6 without any bootlooping issues, but the WiFi problem is still there.
Is it possible to set a radio image to read only so that a recovery wipe/dalvik cache clear will not have permission to clear it? If so, maybe when I flashed a radio before I set it that way without knowing (I honestly can't remember, but I do know that at one point a guide had me flashing something using fastboot and setting chmod something-or-other).
^ I guess I can just press Vol down and Power to check my radio version to see what one I am running and check if it is compatible with CM7.
Any suggestions?
Crazy coincidence.. This morning at 7:45 am my wifes G2 started boot looping. I know it was 7:45, because it was about the time the alarm was supposed to go off.
Hers appears to be a bit worse off, as while I can get into hboot, it won't let me into recovery (and it boot loops before i see cyanogen logo).
I curious to see if anyone else is seeing this, and what the fix might be. I haven't really tried much except getting into recovery since I'm cautious to screw it up further.
Anyone have any ideas?
I now firmly hold the hypothesis that my individual bootloop problem is being caused by my wifi adapter. I am able to flash any rom that doesn't use a kernel based on CM7. On every rom that works ('Stock w/root', Cyanogen6, GingerSense) the WiFi is the only problem. On CM7 and another rom I flashed which was based on the CM7 kernel it bootloops.
So, I am convinced that something in the CM7 kernel polls my wifi adapter when it starts up, figures out that it is borked and then craps out and goes into a bootloop. To further reinforce this idea, as I mentioned in an earlier post- I can boot into CM7 based roms while in airplane mode and use them indefinitely that way. As soon as airplane mode is disabled it goes bonkers.
I'm done t/s this issue for my problem, going to replace the device.
sgshanaf said:
...I can get into hboot, it won't let me into recovery (and it boot loops before i see cyanogen logo).
Click to expand...
Click to collapse
What happens when you select recovery from hboot? If nothing, what about trying a factory reset from hboot? I neither work you should have access to fastboot, but I understand your hesitation if that is the only option you have. Some things I have come across in my searches that could cause bootloops were sim cards, sd cards, and a mess of other things. You can try pulling out the two of those one at a time and doing a normal startup to see if anything changes. Let me know how far you get with the HBoot options and I will try and suggest some other things based on that.
Thanks for responding. I spent a lot of time reading all the different posts I could find with similar issues and decided to take the plunge on this solution:
http://forum.xda-developers.com/showthread.php?t=912399&page=4
and it worked for me.
**UPDATE: below I was having a problem not being able to instal a rom. For whatever reason CM 6.1.1 worked fine. I was then able to go into rom manager and update that way to CM 7.03, and that time it worked. No clue what happened, maybe a bad rom .zip, maybe my SD card is getting flakey. /Shrug
The Phone is booting into that rom fine. Interestingly, while the phone now has eng hboot and working CWM recovery (in addition to still reporting S-OFF), I can't get past the "HTC" splashscreen after installing cyanogen 7 update.zip for the phone. GAPPS or not. I am doing the cache and data wipes
I can get back into recovery fine, but it's just not taking the rom install.
Scott
greenguitar28 said:
What happens when you select recovery from hboot? If nothing, what about trying a factory reset from hboot? I neither work you should have access to fastboot, but I understand your hesitation if that is the only option you have. Some things I have come across in my searches that could cause bootloops were sim cards, sd cards, and a mess of other things. You can try pulling out the two of those one at a time and doing a normal startup to see if anything changes. Let me know how far you get with the HBoot options and I will try and suggest some other things based on that.
Click to expand...
Click to collapse
Ok... here's the deal. I just decided to switch roms finally to see what is new out there. I had been running an old version of Uber Kingdom. Here is the problem I am having. It is boot looping. Relatively simple problem to fix usually. But wait, there's more! It is boot looping in every single rom I install. Sometimes it won't boot to clockwork properly either and I have to pull the battery. Is there someway I can fix this? Or is this a hardware problem (which I kind of doubt)? I just don't understand what the heck is going on. I have been flashing different roms left and right for the past few hours trying to get this thing to stabilize. Sometimes it will boot up into the rom, I will get mostly through the google accounts setup, and then it will restart, and then loop. Other times it won't even get past the white incredible screen, and then sometimes it will make it into the rom splash screen. I have attempted to install CM7 nightly, Uber kingdom, and Synergy so far. I can flash the new rom, I can mount the SD card in clockwork, but then it begins to loop again as soon as I leave clockwork.
Let me know if you need any other information.
Is there a way to just completely redo EVERYTHING, clockwork, rom, everything, just to make sure I have a nice clean slate?
Thanks a ton for reading through this novel. I am extremely frustrated.
~Will
PS, I may not get back to this thread until morning. I have to get to sleep for work. Sorry if I don't respond right away to information requests. Thanks again!
If you can mount the SD card, download the stock RUU from www.dougpiston.com, put it on the root of the SD card named exactly PB31IMG.zip, and boot into hboot to install it. Your phone should be restored to stock, a clean slate.
Tried a different SD?
Sent from my ADR6300 using XDA Premium App
How are you downloading and flashing the ROM? I had this problem when trying to do everything through Rom Manager. Even trying to flash in recovery with a ROM downloaded through ROM Manager would loop.
Update
Well, I was just getting ready to flash the original RUU when I tried one last time to restore my old Uber rom setup and it worked (whereas the last 3 times of doing exactly the same process didn't). It stopped looping at least, even though I am still running the same rom I was before. I think tonight I am still going to attempt to flash the RUU anyway and start over anew.
To answer the questions before, No, I did not try a different SD. I didn't know it could make that much difference. Still on the original one that came with the phone.
As the downloading and flashing process goes, I was downloading direct from the XDA forums on my laptop, then transferring the files via USB. I have never really liked using the Rom Manager. It cuts me out of the XDA loop and I don't get to see all the bleeding edge discussions, etc...
So I will try to flash everything new tonight, and then post my results for anyone who is curious. Thanks for the help guys!
I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Drake13 said:
I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Click to expand...
Click to collapse
sorry but you're pretty much S O L on this, has something to do with a bad boot.img and you can't get it to take another one might as well file a lost phone claim and pay the $100 and get a new one thats what i had to do and they just happened to have sent me the 3d instead so i guess i got a bit lucky.
i still have my evo 4g and still working on it but its been about a month and i haven't had any luck with it.
Sounds like you have no recovery or not completely rooted. You could try to put a recovery CWM or Amon-Ra file renamed PC36IMG.zip onto your sd card from your computer, put card back into phone then go in to hboot see if it will flash you a recovery then try to go into it
If that doesn't work search for a stock ruu file for the Evo, rename PC36IMG.zip, place on your card, put card back in phone, flash through hboot. This will return your phone to stock unrooted, then you try the process again
Sent from my PC36100 using XDA Premium App
That's what happened to my phone also..It just happened out of nowhere..
I tried everything and in the end I had to file an insurance claim.
And once again, a phone running CM7 goes into this mysterious unfixable bootloop.
What is up with that?
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
HipKat said:
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
Click to expand...
Click to collapse
Most of those phones from the 'CM Scare" had bad nand blocks, and it had to be replaced. They had them frothe very beginning, but just decided to act up then. It also happen to some users using MIUI.
Okay my speaker got distorted so I decided to unrooted to take it in for service. Now the phone is unrooted but theres only one problem! Now the phone will boot up to the normal home screen but within 2 to five minutes, it shuts itself down and boot back up to home screen again and the cycle starts again. I have reset few times but same ting' happens. Now sprint is ordering a new phone for me hope its not the 3D i don't think I like it. So now I have my evo still but will give it to sprint once my new phone is in at the sprint store tuesday! Oh by the way, beside the speaker problem the phone was working fine as normal before the unrooting. thx
teh roxxorz said:
t also happen to some users using MIUI.
Click to expand...
Click to collapse
No! Don't say that!!
tony_2018 said:
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
Click to expand...
Click to collapse
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Concordium said:
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Click to expand...
Click to collapse
No one ever said every install of CM7 will lead to this bootloop, but almost every case of this bootloop, the user was running CM7
HipKat said:
No! Don't say that!!
Click to expand...
Click to collapse
Miui is based of cm's fixes and what not right?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
No, MIUI is not based on CM. It's a completely different ROM
Yeah but I'm pretty sure they use their fixes since its a port
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
It's true that most of the cases happened on CM7, but from what I understand it can happen on any rom... and has happened on Sense and AOSP.
There's no known fix. You can try to RUU, but even if the RUU flashes properly, the phone will never boot. You're eternally stuck with hboot/fastboot. File an insurance claim, that's about all you can do. I had a similar problem with a stock, never-been-rooted Evo. I got a replacement through insurance without paying the deductible, but I was s-on.
Hopefully I don't get slammed for suggesting this, but if you don't want to pay the deductible for a "lost" phone, you can flash a radio through hboot and pull the battery. If you do it at the right time, the phone will completely brick and never turn on again. It may take a few tries. Then you can take it in and you shouldn't have to pay the deductible, as long as you play dumb of course.
I think this happens due to bad nand blocks on your boot partition, so the main cause is hardware. Something in the rom triggers the never-ending splashscreen bootloop (I'm assuming something related to the boot.img). I could be entirely wrong about this though.
You can't live in fear, if it happens it happens. It's one of the risks you take when rooting and flashing. The number of cases is small compared to the number of people with rooted Evos, especially considering only a portion of people are active on this site, and a lot of the reports come from members that wouldn't post or even be a member if they didn't have the problem. I wouldn't let the possibility deter you from running whatever rom you want.
Sent from my Evo + MIUI using Tapatalk!
I myself am stuck with same issue. Nothing takes. So where does hboot reside when loaded? I also have looked in vain for diagnostic flashes....
Now one thing I noticed is that I installed PDAnet and it shows it installed an app to the phone, however I cant connect. I think cause I cant boot the phone and enable what it telling me to...so how is it this software can load an apk and I cant?
Overall, I am now however learning and it has become a hobby.
Theres an answer somewhere I would think. Thinking maybe its time to tear apart and look for jtag points....
I have had this happen to me a few times, I leave the RUU on the sd card and when this happens and do what bimmerman7 wrote on the first page. This has always worked for me when I get stuck in a bootloop when trying to access recovery.
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.