[Q] Boot loop issues on various ROM's - Epic 4G Q&A, Help & Troubleshooting

I don't know what to do. I'm having this issue with a couple ROM's.
First happened after installing the latest version of Baked Snack (2.3 - EB13-based). Flashed according to instructions, ran fine for a few days, started acting a little laggy one day so I shut it down and started it back up. Once it started back up, it started boot looping. Only thing that worked was to wipe and start over.
I thought it might be a no-journaling data corruption thing, so I decided to try the journaled version of midnight 5.1 (which I think is based off of Bonsa 4.0.1). Used odin to go back to stock, rooted with cw3.0.0.6/ext4, etc. flashed ROM according to instructions. Again worked great for a few days, then after shutting my phone down tonight and restarting it a few minutes later, boot loops. Reverting to an earlier nandroid backup worked, and I'm assuming wiping and reflashing would work, but I gotta get to the bottom of this.
What's baffling to me is that everything works fine for a few days. I'm shutting the phone down normally, I'm not doing anything strange before shutting down. In both cases I was using setCPU, but with very conservative settings (200min 1000max, conservative or on demand). I can't think of what else I may be doing to cause these problems.
Anyone else run into this?

rsage said:
I don't know what to do. I'm having this issue with a couple ROM's.
First happened after installing the latest version of Baked Snack (2.3 - EB13-based). Flashed according to instructions, ran fine for a few days, started acting a little laggy one day so I shut it down and started it back up. Once it started back up, it started boot looping. Only thing that worked was to wipe and start over.
I thought it might be a no-journaling data corruption thing, so I decided to try the journaled version of midnight 5.1 (which I think is based off of Bonsa 4.0.1). Used odin to go back to stock, rooted with cw3.0.0.6/ext4, etc. flashed ROM according to instructions. Again worked great for a few days, then after shutting my phone down tonight and restarting it a few minutes later, boot loops. Reverting to an earlier nandroid backup worked, and I'm assuming wiping and reflashing would work, but I gotta get to the bottom of this.
What's baffling to me is that everything works fine for a few days. I'm shutting the phone down normally, I'm not doing anything strange before shutting down. In both cases I was using setCPU, but with very conservative settings (200min 1000max, conservative or on demand). I can't think of what else I may be doing to cause these problems.
Anyone else run into this?
Click to expand...
Click to collapse
Sounds like you got everything covered. The only thing I can think of is do you have a lot of apps on your SD card? Could be the card is starting to get corrupted. Backup everything on the card to a computer and reformat the card and restore the data.

kennyglass123 said:
Sounds like you got everything covered. The only thing I can think of is do you have a lot of apps on your SD card? Could be the card is starting to get corrupted. Backup everything on the card to a computer and reformat the card and restore the data.
Click to expand...
Click to collapse
Thanks I'll try that. The first time, I did have a ton of apps on the sd card. Second time, I didn't really reinstall many apps because I was a little gunshy from what happened, then it happened again anyway. I'll try this tonight.

rsage said:
Thanks I'll try that. The first time, I did have a ton of apps on the sd card. Second time, I didn't really reinstall many apps because I was a little gunshy from what happened, then it happened again anyway. I'll try this tonight.
Click to expand...
Click to collapse
Formatting your SD card is always a good step when ROMs don't seem to flash right.
Also, Baked Snack is not/will never be supported here.

k0nane said:
Formatting your SD card is always a good step when ROMs don't seem to flash right.
Also, Baked Snack is not/will never be supported here.
Click to expand...
Click to collapse
Thanks k0nane, reformatting as I type this, hopefully this works as I'm out of ideas.
And yes, wasn't asking for support for BS, but for a general issue I'm having with all ROM's at the moment. From now on if I ever have to refer to that ROM, I will call it "the ROM that shall not be named"...

rsage said:
Thanks k0nane, reformatting as I type this, hopefully this works as I'm out of ideas.
And yes, wasn't asking for support for BS, but for a general issue I'm having with all ROM's at the moment. From now on if I ever have to refer to that ROM, I will call it "the ROM that shall not be named"...
Click to expand...
Click to collapse
While you are working on your phone, if you are going to stick with midNIGHT, I suggest you move to 5.2, 5.1 was a little goofy for some and 5.2 seems to have fixed any issues it had.

budderocks said:
While you are working on your phone, if you are going to stick with midNIGHT, I suggest you move to 5.2, 5.1 was a little goofy for some and 5.2 seems to have fixed any issues it had.
Click to expand...
Click to collapse
I'd love to, but the 5.2 update is only available for the no journaling version

rsage said:
I'd love to, but the 5.2 update is only available for the no journaling version
Click to expand...
Click to collapse
You are in luck, it is updated now. I believe he is uploading it as I type this
Sent from my SPH-D700 using XDA App

budderocks said:
You are in luck, it is updated now. I believe he is uploading it as I type this
Click to expand...
Click to collapse
Yep, XDA thread not updated yet but I see the upload on his site, thanks for the heads up! Hopefully the card reformat and ROM update will resolve the situation.

Related

[Q] freezing problem

Hi everyone!
first, happy new year!
I have a problem with my desire...it freezes in a way that the pulling the battery out is the only thing that helps...it doesn't respond to any button, the screen os off and I can't wake it up
it's rooted with unrevoked, clockwork recovery
tried different roms, the best for me is baadnwz dhd port...
been on that for a while and didn't have the freezing problem, then I flashed the miui..
went back to baadnwz and it started to freeze...a few times a day
then I reflashed it, uninstalled the font changer and that helped...for two days(thought that was the problem) but tonight(~36h from the clean install of the rom) it froze again...
so, I don't think it's the rom, obviously it is not the font changer...
why is this happening, has anyone encounter this before, is there a solution?
please advise, what should I do?
thank you
For what it's worth...
If you can get it back to stock ROM, then do so. Then take it back to the place you bought it and demand a brand new replacement. I would even go so far as to note/print a few pages of some the forums as evidence of the widespread problem.
If my (and many other people's experiences) on here are anything to go by, then your problem will only get worse...and let's face it, whoever has heard of a electronic non-software related problem getting better on it's own? Having read just about every available post on the subject I've concluded that no amount of flashing/reflashing/fiddling is going to fix it.
Sorry to be negative about it, but them is just the facts as I see them.
hmm...so it's like that huh?
what do you mean "if" I can go to the stock rom?
can't I flash the original rom, or ruu or something?(I don't know, never tried something like that)
but then again, I'm not sure that it isn't a software problem...I'm just lurking around to see if anyone has encountered this before and solved it....
if all else fails, I'll flash a clean rom without restorin my apps and see how it goes from there...
just my experience
trikpa said:
hmm...so it's like that huh?
what do you mean "if" I can go to the stock rom?
can't I flash the original rom, or ruu or something?(I don't know, never tried something like that)
but then again, I'm not sure that it isn't a software problem...I'm just lurking around to see if anyone has encountered this before and solved it....
if all else fails, I'll flash a clean rom without restorin my apps and see how it goes from there...
Click to expand...
Click to collapse
In all honesty, you may be able to reflash back to stock ROM. It may well depend on what firmware you have on your phone and whether your phone is branded (mine is T-Mobile UK). I know when I originally got mine and rooted it, it was hboot 0.83. It went wrong (external speaker stopped working). I was able to flash it back to stock ROM and I sent it back to HTC. When I finally got it back after 8 weeks (long story involving HTC incompetence and bad luck/incompetence with UPS), it was on hboot 0.93.0001. I rooted it with Unrevoked and installed LeeDroid 2.2f ROM. Shortly afterwards, it started to freeze/reboot. However, everything I've read so far leads me to believe LeeDroid wasn't the cause of the freeze/reboot fault. The problem is far too widespread (just Google 'HTC Desire reboot freeze problem') for it to be caused by a particular custom ROM.
Anyway, the upshot for me is that no matter what I've tried, I haven't been able to get it back to stock ROM and therefore, can't send it back for repair/replacement.
I sincerely hope you have better luck than me.
well, I'll see how it goes..
thank you for your answers
is there a way that I can make a log or something to see whether an application is doing this or something else?
well, I think I solved my problem, and for further reference here's a post that I did in another thread where this was disccused..
trikpa said:
just to let you guys know, I don't have any more freezes
some say it's because of the sense rom, some it's the dhd rom, others told me it's the radio or the ril files....
tried all of that plus few more things and nothing...
well, it turned out to be my backup(or an app in it..)
I always backed my apps and data with my backup pro, very nice app that restores everything....but the last rom flash I did, I didn't restored my apps&data and started fresh installs...and no freezing
I don't know what exactly caused problems, but one more thing that may be responsible...I flashed "font changer" and changed system fonts on my phone...and then backed my apps...maybe that's he deal...dunno...
anyways, I'm back with a killer phone with the best rom out there - baadnewz's
Click to expand...
Click to collapse
hope that will help someone
cheers
Do you still have any issues with the phone freezing sometimes when charging from A/C?
Mine doesn't freeze as much as it used to since updating the RIL files but being left charging seems to upset it
w0mbat said:
Do you still have any issues with the phone freezing sometimes when charging from A/C?
Mine doesn't freeze as much as it used to since updating the RIL files but being left charging seems to upset it
Click to expand...
Click to collapse
no freezes whatsoever
trikpa said:
no freezes whatsoever
Click to expand...
Click to collapse
OK, that sounds good. I only usually recover a few items using Titanium backup but next time that I flash a ROM update. I'll start it all from scratch and hope to get the same result as you.
I don't know, maybe it was a specific app but I don't have the time nor the will to test each one of them
I've got the same problem. Now that I read your post it makes sense.
Restored my apps trough titanium backup and 5 hours later my phones freezes.
Can u make list off apps that you have ?
mine (those that I restored)
vandaag 24
teamviewer
circel widget battery
dropspace
handcent
sdwatch
adfree
advanced task killer
fotmob
gridcalendar
applanet
astro
barcode scanner
cardio trainer
compass 2.1
gouden gids
gowalla
shazam
flitz said:
I've got the same problem. Now that I read your post it makes sense.
Restored my apps trough titanium backup and 5 hours later my phones freezes.
Can u make list off apps that you have ?
mine (those that I restored)
vandaag 24
teamviewer
circel widget battery
dropspace
handcent
sdwatch
adfree
advanced task killer
fotmob
gridcalendar
applanet
astro
barcode scanner
cardio trainer
compass 2.1
gouden gids
gowalla
shazam
Click to expand...
Click to collapse
well, it's been a while since then and I don't know what apps I used back then...but I can tell you what apps I used that you use
from your list I used
handcent
adfree
applanet
astro
barcode scanner
and maybe the compass
hope it helps, but my advice, do a fresh install
tnx, Ill keep ya posted
flitz said:
tnx, Ill keep ya posted
Click to expand...
Click to collapse
any news?
my phone started to freeze again
and I didn't restore backup, did a full fresh install...
don't know what to do
Yes, I've solved my problem by buying a new SD card.
This time from Kinsgstond instead of Sandisk.
Hope it solves your problem too.
My phone freeze after charfing while its off. I noticed that it freezes when it says "preparing SD card". This happened twice so far
Sent from my HTC Desire using XDA App
flitz said:
Yes, I've solved my problem by buying a new SD card.
This time from Kinsgstond instead of Sandisk.
Hope it solves your problem too.
Click to expand...
Click to collapse
well, I did buy a new 8GB card, but it never occured to me that it could be the problem....I think it didn't freeze right after I switched cards...
for now I flashed a newer version of the rom I'm using and will see how it goes...if not, I'll switch cards again
thanks for your answer
Yann2011 said:
My phone freeze after charfing while its off. I noticed that it freezes when it says "preparing SD card". This happened twice so far
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
well, sd card could be the problem in your case too, try another one...and post here with results
I'm curious
Well so far I have reflash the phone after a factory reset + wipe with no app restored via backup. It is performing ok so far. Last freeze was 2 days ago. I will wear down the battery to get a chance to charge it up this afternoon. I will see if it freezes again.

[Q] Constant Reboots...

Hello everyone. I have not been too particularly active here mainly because I have had no real reason to post. I give thanks when needed, but don't really post. Well, now I am having an issue that I genuinely cannot figure out. I recently dropped my phone and the digitizer cracked big-time. When I went to replace it, the connector for the ribbon cable broke. So instead of buying a new logic board, I just decided to buy a new Evo. However, I couldn't afford the approx. $600 for the "without a contract" price. So I went to a local Sprint dealer in my town and bought a factory refurbished Evo. Here is where the problems start.
I have been having reboots constant with this phone. I knew that there were some issues with the Evo randomly rebooting, but I have never seen something like this. It happens about every minute or so. Sometimes sooner. Sometimes I luck out and it doesn't reboot for a few hours. I notice that it does not reboot at all while it is in recovery, which is a great thing. I have tried multiple different ROMs and each one does it. I am completely out of ideas. I don't necessarily want to take it back, mainly because returning it to stock would be a pain. However, it is looking like I have to. Does anyone have any idea? It is obvious that it is not a bootloop, because I am able to actually get into the launcher. However, within a minute, it reboots. Can old radios cause it to reboot like this? It did this even with stock unrooted.
If any information is needed, please let me know. I really want to get this working without returning.
Thanks
StompySan
EDIT: It would seem that flashing my Nandroid backup of stock rooted seems to stop the rebooting issues. Could the ROMs I am installing be conflicting with the radios, causing it to reboot?
If I were you, without unrooting, I would flash the RUU for your phone. Then flash the pc36img for Amon Ra.
Before all that, I'd also back up your SD Card, then reformat it, so you are basically starting from scratch. A good idea, before you restore everything to your SD Card, but after you flash Amon Ra, is to partition it for EXT3. ( http://themikmik.com/showthread.php?5669-GUIDE-TUTORIAL-Apps2SD-Guide&highlight=partition+sdcard )
A lot of the ROMS now will take advantage of that. Once that's done, you can restore your SD Card backup to your phone.
Then I'd make a nandroid of that stock/rooted ROM, so you can always go back to it if you need to. When I nandroid, I backup everything except cache.
Figure out which ROM you want, put it on your card along with DT A2SD and the kernel you want to use. Make sure it's a kernel for the type of ROM you want, either AOSP or Sense. Personally, I keep the best rated kernel for each on mine.
Go to Wipe in Recovery and wipe everything, EVERYTHING, except the SD Card, then flash your ROM, and in the same recovery session, flash DT A2SD.
Let it boot up and let it settle in before you do anything. For me, that means once the screen shuts itself off.
Back to recovery, wipe Cache and Dalvik-Cache, then flash your kernel, reboot and let it settle in again.
THEN setup your Google accounts and preferences.
For me, I'd go back to recovery and nandroid that setup, before you've restored your apps, and make another nandroid, so you have one of your ROM's Base.
Then, reboot and see if the problem is fixed. If it is, restore your apps and see how it goes. If it starts rebooting, you know it's in your apps, so you can go back to the nandroid you made and start form there, installing a few apps at a time
Thanks for your reply HipKat.
I followed your tutorial step-by-step. However, after flashing A2SD and rebooting, it bootlooped (not like what I was getting, but an actual no boot logo bootloop). I am assuming that the ROM that I flashed didn't like the A2SD. So I restarted the tutorial, skipping the part where you flash the A2SD script. It seems like it is doing great now! I have no clue what I was doing wrong. I was using CWM. Maybe that was the problem. Could it have not been wiping it properly?
Thanks again for the quick response!
1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
2. Before flashing new roms, wipe everything is absolutely required, otherwise strange problems will keep coming out.
What I comprehend is that flash roms on phone is like upgrading OS on your computer, you can't run windows7 with XP's configuration, right?
Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk
plainjane said:
Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
You're right! I keep overlooking that because I never flash unless I'm fully charged.
My mistake on those posts. Thanks!
I was still getting reboots after doing all of that. I thought it went away, but it didnt.
79x1 said:
1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
Click to expand...
Click to collapse
This has to be it. I changed the speed to 1.15GHz in SetCPU and it has not done it since. Thanks!
EDIT: Well, it was OK, but it has started again. I have no clue why it is doing it again...
Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours.
And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.
79x1 said:
And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.
Click to expand...
Click to collapse
It doesn't matter what speed I set it to. I had it at 998 before and it still rebooted.
79x1 said:
Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours
Click to expand...
Click to collapse
I am going to flash Synergy real quick. I have already tried the following:
EVOlvedROM r3chargeD
Cyanogenmod
Are there any other ROMs I should try?
EDIT: I recorded a video of exactly what it is doing. I am currently encoding it. I will throw a YouTube link up soon.
Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/showthread.php?t=1180048
Here is the video of the rebooting problem. Sorry it is so long. It seems like the one time I want it to reboot it took forever for it to. lol.
79x1 said:
Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/show....php?t=1180048
Click to expand...
Click to collapse
I will try this ROM later tonight. I probably won't be able to reply tomorrow, because I have to work from 10AM to 10PM (I hate long days, lol), but will reply as soon as possible.
MIUI, for the win, man!
OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.
It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it
stompysan said:
OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.
Click to expand...
Click to collapse
You can flash S-On.zip directly from the recovery, I suggest you try out the method I mentioned in the previous post, before you go doing something drastic.
prometh1us said:
It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it
Click to expand...
Click to collapse
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.
stompysan said:
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.
Click to expand...
Click to collapse
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.
HipKat said:
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.
Click to expand...
Click to collapse
Yeah. That's what I was reading. Plus, I rooted with Revolutionary, which doesn't have a method to enable S-On.
Last night I flashed the latest stock ROM. As soon as it booted up and got to the lockscreen, it restarted. I can't see it not being a hardware problem. I am going to return it today. Hopefully they don't notice that it is S-Off. Any suggestions on what to say if they do?
same issue
i have an old evo that is doing the same thing, i flashed the original ruu and it still does it. i just reported it lost.

Undo ICS leaked firmware

Is there a way to undo the leaked ICS firmware I've flashed? I've been hit with the post viper CM10 lag that seems to be going around and I thought I'd try everything to get rid of it.
Have you tried chilly's super wipe? There is a thread for it.
Sent from my Incredible 2 using xda app-developers app
Same here. I super wiped two days ago and formatted my sd card. I thought I had it and my phone ran fine for a day. I charged it over night and when I took it off the charger, it was shot again today. When it actually boots, I can't get past the unlock screen. It holds there for about a minute before going into a boot loop. I didn't even think of the ics firmware. Maybe I'll try going back to stock tomorrow and then reflashing cm10.
Sent from my A500 using xda app-developers app
I don't know if it's the firmware or not, but I thought it was worth a shot. I have used chilly's wipe and I have gotten the huge lag since then. I'm running his PAC rom now and I used his wipe twice before I installed. I've also v6 supercharged so I'm waiting to see if it happens again. Is there a copy of the old firmware that is flashable like the new one?
Baloeb said:
I don't know if it's the firmware or not, but I thought it was worth a shot. I have used chilly's wipe and I have gotten the huge lag since then. I'm running his PAC rom now and I used his wipe twice before I installed. I've also v6 supercharged so I'm waiting to see if it happens again. Is there a copy of the old firmware that is flashable like the new one?
Click to expand...
Click to collapse
There at threads for different ruu's. I'm not sure which one you need. Search through those. Also, when your phone starts lagging try connecting to a computer in adb I think, someone posted that that fixed theirs temporarily. I think they narrowed it down to the SD card being bad and with it connected it dismounts the SD card and doesn't have the problem. That might help.
Sent from my Incredible 2 using xda app-developers app
NeverSeparate said:
There at threads for different ruu's. I'm not sure which one you need. Search through those. Also, when your phone starts lagging try connecting to a computer in adb I think, someone posted that that fixed theirs temporarily. I think they narrowed it down to the SD card being bad and with it connected it dismounts the SD card and doesn't have the problem. That might help.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I'll give that a shot next time. Usually I just pull the battery and install cm7 so I have a working phone.
Okay, 1st you need to return to stock:
http://forum.xda-developers.com/showthread.php?t=1599767
After this process you need to flash cwm and superuser:
I believe this thread http://forum.xda-developers.com/showthread.php?t=1751796 has all the files (including adb) set up in one .zip under "TACOROOT"
Or just download them from here:
https://dl.dropbox.com/u/77740451/recovery-clockwork-5.0.2.0-vivow.img
https://dl.dropbox.com/u/77740451/Superuser-3.0.7-efgh-signed.zip
This is what I did to remove the firmware. I didn't have the lag, but I was hoping to solve camera issues.
SkinnyT said:
Same here. I super wiped two days ago and formatted my sd card. I thought I had it and my phone ran fine for a day. I charged it over night and when I took it off the charger, it was shot again today. When it actually boots, I can't get past the unlock screen. It holds there for about a minute before going into a boot loop. I didn't even think of the ics firmware. Maybe I'll try going back to stock tomorrow and then reflashing cm10.
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
Just a quick note...When I was running CM10 I would get the boot loops at the lock screen, but if I just let it alone, it would loop 2-3 times and then settle in. It took a while, and I avoided rebooting my phone at all costs, but have you just let it sit for about 10 minutes to see if it pulls out of the boot loop? Mine usually came out in less than 5, but you never know. After it booted up it settled down and ran fine. I've never used the Venom rom or super wipe though, so ymmv.
gtdtm said:
Just a quick note...When I was running CM10 I would get the boot loops at the lock screen, but if I just let it alone, it would loop 2-3 times and then settle in. It took a while, and I avoided rebooting my phone at all costs, but have you just let it sit for about 10 minutes to see if it pulls out of the boot loop? Mine usually came out in less than 5, but you never know. After it booted up it settled down and ran fine. I've never used the Venom rom or super wipe though, so ymmv.
Click to expand...
Click to collapse
Mine doesn't boot loop, it runs great for a few days then starts to lag so bad it's unusable.
Baloeb said:
Mine doesn't boot loop, it runs great for a few days then starts to lag so bad it's unusable.
Click to expand...
Click to collapse
Some have reported that it's linked to a usb / sdcard / storage issue. Lag starts after connecting.
Sent from PAC-land

Storage issues help

I'm suddenly having storage issues with every ROM that I flash after running a ROM with some script that isn't widely used.
First I'll give you a brief idea of my problem. I"m running out of storage and get notifications from the market saying as much after I download and reasonable amount of apps. The thing is... It show's I have used 738MB of ext4 out of 1.5 so that isn't the issue. The problem is internal memory. My phone won't move dalvik cache for some reason. When I run any ROM with a2sd or m2sd they both say that there is a problem and leave the dalvik cache where it is.
I think my internal folders are jacked up from 40ad2sdx or a zip that was used to clear memory before the ROM. There was a ext4 superwipe cleaner to load before the ROM. I did that without researching first. When I did go looking for the thread about it, it plainly said that it was for one phone only, and it wasn't my phone. I believe it was the Galaxy S3, but I can't be certain. It was a week ago. It was advised not to use it on any other phone because part of what it did was reset the internal folders. Does this mean I can now flash a ROM for the galaxy s3? Lol Just kidding.... Seriously, the second part is all my speculation and I have been wrong many times concerning android. Will somebody help me get my phone back in oem condition please?
Okay, I'm not even sure what you did here, because not knowing the script, anything could have happened.
Try wiping everything and flashing stock rooted here, then go from there with other roms after that.
If that doesn't work. Here's what I would do. It might be a major pain, but it is almost a surefire fix.
Unroot and return to stock, then root again.
[UNROOT]
[ROOT]
For future reference, NEVER flash anything that is meant for another device. (Obviously, if it's a port then you're ok.)
ALSO EXTREMELY IMPORTANT: Backup your SD card, and wipe that puppy clean!! Only partition using Amon-RA recovery, otherwise it will screw you up quite often. I repeat, if you do not have the partition done correctly, then odds are that A2SD or equivalent won't work.
nate234 said:
Okay, I'm not even sure what you did here, because not knowing the script, anything could have happened.
Try wiping everything and flashing stock rooted here, then go from there with other roms after that.
If that doesn't work. Here's what I would do. It might be a major pain, but it is almost a surefire fix.
Unroot and return to stock, then root again.
[UNROOT]
[ROOT]
For future reference, NEVER flash anything that is meant for another device. (Obviously, if it's a port then you're ok.)
ALSO EXTREMELY IMPORTANT: Backup your SD card, and wipe that puppy clean!! Only partition using Amon-RA recovery, otherwise it will screw you up quite often. I repeat, if you do not have the partition done correctly, then odds are that A2SD or equivalent won't work.
Click to expand...
Click to collapse
I did the wipe and flash to stock earlier today, then flashed the Pac man ROM but the issue is still there. I had looked at unrooting my phone earlier today also. I'm glad to read this because it lets me know that I do have some idea of what to do. Thanks for the reply. I'll post here again with the results. Check back soon.
EDIT----> Man, my phone is okay. I loaded up a fairly recent ROM by Tronit, and it worked fine. It was the ROMs. Just to be sure, I went back to the last two ROMs just to see, and they did the same thing again. Now I'm on the AOKP Unnoffical and it's working just fine. The a2sd is working perfectly like it should, and my dalvik cache is moving to ext4. It was just coincidental that the last three ROM's I loaded all have issue with the a2sd. It's funny how nobody else see's problems but me. I looked in the bin file of one of them and it's missing part of the a2sd file. The other two have weird init.d files that I don't know anything about. I'm assuming the a2sd problem is related to that. It's funny how I see lots of problems, and report them, but I get blown off by some people as a noob who is making mistakes. I am a noob, and I do make mistakes, but I know some of my theories about problems are correct...... I gotta get me some respect by compiling my own ROMs.
Status update..... My phone is jacked up for sure. It does work with the AOKP Unofficial by Tronit, but this morning when I cleared my cache with Smelkus Recovery, it had major problems with almost every app. Clearing the cache in recovery is something I've done with every ROM and this has never happened. I uninstalled all the apps and reinstalled them. Got them working again. Everything seemed to be okay. However, when I cleared my cache with Android Tuner, again it ruined every app. I've used android tuner every day for two months to clear the cache and never had problems like this. Something is very wrong.
*****edited and deleted for the sake of peace*****
Long story short, I flashed something made for another phone. I can't explain why I did this without taking up lots of pages, and it doesn't even matter really. Lets just focus on the solution. Here is the link. I flashed both of the zips in the link.
http://forum.xda-developers.com/showthread.php?t=1477955
So I think my permissions for the files on my phone are out of whack. Is that what I"m reading is the possible outcome of flashing these if your phone is not the one listed? Please post your thoughts. I need them.
Try backing up your SD card on a computer and format you SD card and repartion it
Sent from my PC36100 using Tapatalk 2
g2435 said:
Try backing up your SD card on a computer and format you SD card and repartion it
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
I did that. Both with Smelkus, and Mini partition wizard. Same problems. I just tried to fix permissions with smelkus 4.3 on the AOKP Unofficial ROM and it took a minute for it to do it's thing. The line of dots was two full rows. So when It loaded back up, I suddenly see the same disk Icon in my notification bar, and now this ROM says it it out of memory. Man, it was working fine. I had twenty more apps on it too and I uninstalled them. It was working fine then, so with twenty less apps, it shouldn't suddenly say "Running out of Storage space."
I have told you this already: Please do not flash things meant for other phones, it could mess up. If it's meant for another device, it might screw yours up. To stay on the safe side: If it's not generic (works for every Android phone) or phone specific (exclusive to the Evo 4G) then don't flash it.
nate234 said:
I have told you this already: Please do not flash things meant for other phones, it could mess up. If it's meant for another device, it might screw yours up. To stay on the safe side: If it's not generic (works for every Android phone) or phone specific (exclusive to the Evo 4G) then don't flash it.
Click to expand...
Click to collapse
I flashed this about a eek ago, when I was looking for the ext4 wipe. I thought it was the same thing as another zip despite what it said. Stupid... I know. I think this may be the cause of my problems, but I can't be sure. I don't know at all really. Just speculations. I reflashed the CWM touch and used to flash a stock ROM. Gonna try that again. I ran the test on CWM touch and it said that the
/sys/class/android_usb/android0 was missing and unable to perform the test. Can this be the cause of my problems?
Don't beat yourself up man, it was an honest mistake, just learn from it and you'll be alright.
Now the optimal recovery for this device would be the Amon-RA recovery, and I recommend redoing what I said in my first post once you have Amon-RA installed. Amon-RA is an awesome recovery, and it's super easy to install. Check out this easy-to-follow video on how to install by clicking here.
Do that, then do what I said in the previous posts. Let me know what happens, because I'm almost certain this should work.
nate234 said:
Don't beat yourself up man, it was an honest mistake, just learn from it and you'll be alright.
Now the optimal recovery for this device would be the Amon-RA recovery, and I recommend redoing what I said in my first post once you have Amon-RA installed. Amon-RA is an awesome recovery, and it's super easy to install. Check out this easy-to-follow video on how to install by clicking here.
Do that, then do what I said in the previous posts. Let me know what happens, because I'm almost certain this should work.
Click to expand...
Click to collapse
I tried loading the Pacman ROM again with CWM and it wouldn't even load. It gets stuck in a bootloop. After that I flashed smelkus and went back to the Stock Rom.
*****edited and deleted for the sake of peace****
RADIO EDIT------
Sent from my PG86100 using xda app-developers app
edited and deleted for the sake of peace
As I stated in my pm give me a day or so till I get back home and I will check into a fix for you. Only don't expect any one on one help. If the fix works cool if not I will dig further. TNN strives to help with any issue no matter who is at fault. I will look at the wipe script you flashed and see if it can be undone. Just be prepared of the possibility that your phone may never work correctly again.
Sent from my PG86100 using xda app-developers app
I was finally able to get my phone straightened out. I loaded up a stock ROM then decided to use my SD Maid to look around. I found a file with completely different dates on it, but it wouldn't let me remove it. I ended up copying everything else in the subfolder and then deleted the parent folder. Then added everything else back. Wah lah.... magic. I don't know what that file was or where it came from but it was killing my internal memory. I'm wondering how it stayed from ROM to ROM. I dunno, but it's gone, and the Pacman ROM is lovely now. BOOM!!!!
jlmancuso said:
As I stated in my pm give me a day or so till I get back home and I will check into a fix for you. Only don't expect any one on one help. If the fix works cool if not I will dig further. TNN strives to help with any issue no matter who is at fault. I will look at the wipe script you flashed and see if it can be undone. Just be prepared of the possibility that your phone may never work correctly again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Whatever I did only fixed part of the issue. I'm left with in a situation where every time I go into recovery my downloaded apps stop working. It is cutting part of them off whether I clear cache or not. All I have to do is power off into recovery, and when I reboot, all of my downloaded apps begin giving messages that "Unfortuately such ans such has stopped." My phone becomes inoperable. The only way I can keep it working is to send a new launcher to my phone from the market, let it install, then open it up and uninstall all the downloaded apps. I'm pretty sure this is an easy fix for someone like you Mancuso. I have a logcat and it show LOTS of errors that I have never seen before on any of my other logcats. What are my options? Tell me what to do to get my phone back to absolute OEM and then I'll reroot. UNLESS you know of some fix.
I've supplied a logcat from Catlog if you or anybody else wants to have a look. I'd really appreciate some help here. I love my Evo and I love learning this stuff. If somebody can help me positively identify the problem, I can most likely figure it out from there. Please give me your suggestions here. I'm nothing without some guidance on this. It's way out of my scope.
I've included a link to the ext4 script wipe that I used. How I got to this page, I do not know. However, I ran it because this page said it COULD POSSIBLY work on other phones despite the fact that it was made for another phone.
http://www.xda-developers.com/android/darkside-super-wipe-easily-wipe-partitions-when-flashing-roms/
And I flashed both zips from the thread that the story links users to. Here is the link for the two zips.
http://forum.xda-developers.com/showthread.php?t=1477955
I'm not sure this is the problem. I'll try to find the Vold.fstat thread that I tried on my own before you came up with the 40ad2sdx solution for the MIUI ROM.
This is the memory fix I tried as mentioned above.
http://forum.xda-developers.com/showthread.php?t=2246909
Please note that you see before and after pics of sd storage. You can see that my pics clearly resemble the after pics shown in this thread. I believe this is my problem. How can I undo this?
This post reflects the only things I did outside of normal flashing. My problem is here somewhere...
The fix you used is for samsung devices. That could have caused your problems.

desire bootlooping excessively

someone please please help me.....
I flashed nikez's rom a month back, and this week it started bootlooping on it's own. random reboots and constant bootlooping. but today, it went completely off the hinges, so i decided to reflash it after full wipe, but now it's even worse. now no other rom boots, it just bootloops. i have tried to flash vj's roms, pa and nikez today, but none of them make it past the boot animation.
PS, i'm not new to flashing, but this phone is very very very precious to me... someone please help me ...............
The Andy Girl said:
someone please please help me.....
I flashed nikez's rom a month back, and this week it started bootlooping on it's own. random reboots and constant bootlooping. but today, it went completely off the hinges, so i decided to reflash it after full wipe, but now it's even worse. now no other rom boots, it just bootloops. i have tried to flash vj's roms, pa and nikez today, but none of them make it past the boot animation.
PS, i'm not new to flashing, but this phone is very very very precious to me... someone please help me ...............
Click to expand...
Click to collapse
You are doing a full wipe before flashing right? Try some gingerbread roms as well, and see if they work.
If youre still having problems, it could be your sdcard. Try doing a full reformat of the card. If even after that its not working, it could be a hardware fault in the card...try a different sdcard. Did you do anything that caused this, or it just suddenly started?
Chromium_ said:
You are doing a full wipe before flashing right? Try some gingerbread roms as well, and see if they work.
If youre still having problems, it could be your sdcard. Try doing a full reformat of the card. If even after that its not working, it could be a hardware fault in the card...try a different sdcard. Did you do anything that caused this, or it just suddenly started?
Click to expand...
Click to collapse
it started a couple of weeks ago. just random reboots and stuff. yes, it corrupted my sd card too. now i have a newly formatted sdcard, with some songs that run ok on my other mobile, and all roms on it that i flashed. but this isn't just working. roms flashes ok, then i reboot device 9in cwm) but then after a few seconds, it bootloops. doesn't even start the rom, then stays stuck at htc logo.
First of all, you should be sleeping
Secondly, you were warned, weren't you? About the consequences?
Thirdly, try wiping your sdcard in cwm, then put on a rom. After flashing the rom, pull out your sdcard, then check if it boots. If that doesn't work, try wiping battery stats too, That's sure as hell gonna solve your problem.
alicarbovader said:
First of all, you should be sleeping
Secondly, you were warned, weren't you? About the consequences?
Thirdly, try wiping your sdcard in cwm, then put on a rom. After flashing the rom, pull out your sdcard, then check if it boots. If that doesn't work, try wiping battery stats too, That's sure as hell gonna solve your problem.
Click to expand...
Click to collapse
Yep, I posted and went to sleep.
I did the wiping in cwm and put cm7.2 on it. During flashing it stopped, and stuck there until I pulled out the battery and did the procedure again, albeit after a bit of time. This time it flashed okay, but the same bootlooping.
I pulled out the battery, and let it be for some time. then I put it in and the ROM started (viola!)
But this didn't remain for long since as I tried to meddle with settings a bit, like turning off mobile data, it did the bootlooping again.
I pulled out the battery again, and in morning repeated the procedure, but the same happens. after little use, it goes bootlooping again.
The Andy Girl said:
Yep, I posted and went to sleep.
I did the wiping in cwm and put cm7.2 on it. During flashing it stopped, and stuck there until I pulled out the battery and did the procedure again, albeit after a bit of time. This time it flashed okay, but the same bootlooping.
I pulled out the battery, and let it be for some time. then I put it in and the ROM started (viola!)
But this didn't remain for long since as I tried to meddle with settings a bit, like turning off mobile data, it did the bootlooping again.
I pulled out the battery again, and in morning repeated the procedure, but the same happens. after little use, it goes bootlooping again.
Click to expand...
Click to collapse
I think there is a problem with your motherboard heating up. Your motherboard is faulty.... It's okay when cool, but not so okay when warm, and that's when bootloops happen. Try freezing your phone, and if it works that way, then you have your solution in front of you. Carry around a minifridge with you.
alicarbovader said:
Try freezing your phone, and if it works that way, then you have your solution in front of you. Carry around a minifridge with you.
Click to expand...
Click to collapse
Hahaha best solution ever
alicarbovader said:
Carry around a minifridge with you.
Click to expand...
Click to collapse
Stealing my technique?
http://forum.xda-developers.com/showthread.php?t=2428600
Sent using xda-developers app
Chromium_ said:
Stealing my technique?
http://forum.xda-developers.com/showthread.php?t=2428600
Sent using xda-developers app
Click to expand...
Click to collapse
Hehe
Chromium_ said:
Stealing my technique?
http://forum.xda-developers.com/showthread.php?t=2428600
Sent using xda-developers app
Click to expand...
Click to collapse
seemed legit a while ago

Categories

Resources