Develop Bugs

Unfixable boot loop... Help?

Hey everyone,
So this is my last ditch effort to attempt to save my device. I would really prefer not to perform another warranty exchange given that I am not under insurance, but I'm afraid I have no choice.
My phone was rooted and I was using Darkside without issues, as I had been for the past two weeks. I am always careful when I flash roms and I made sure to follow every possible protocol. That's the background information.
My battery life was running at approximately 6 percent yesterday and I sent a text message as normal, and it was stuck at sending. I tried turning wireless data off from the toggles in the pull-down and it was unresponsive. When I went to Wireless Network in the settings option, my phone rebooted. Once it started up again, my service would not come back, and the phone would continually bootloop once it got past the traditional "media scanner running", etc. My window of opportunity to do anything was really slim.
I charged my phone to see if it made a difference, but it didn't. Tried with my SIM card removed and it still bootlooped. I was able to get to CWM from the advanced power menu before it rebooted again and I fixed permissions and cleared cache and dalvik. Now the phone wouldn't even get past the boot animation before rebooting.
I put the phone into download mode and reverted back to stock using Odin. The phone now got past the boot animation in stock mode, but was unable to find service and after about 10 seconds fell into the same bootloop pattern. I tried removing the SD card but that didn't help either. Using Odin again, I reflashed recovery, followed by root and tried reinstalling a rom through CWM (I have only used regular CWM, not the touch version) with a superwipe to ensure a clean flash. Once again, it wouldn't make it past the boot animation before bootlooping. I reverted back to stock using Odin, and this is where I stand.
I have tried all traditional methods to salvage the phone and, for the life of me, I cannot understand what happened. The only thing I notice is that regardless of how long the phone stays on before rebooting, it is never able to find service. It's like the radio or modem broke and the phone has no other choice but to restart forever. But reflashing the stock UVKL1 should also reflash the proper modem and radio, right?
Has this ever happened to anyone? Any suggestions (aside from the typical reverting to stock) as to how I might be able to stop it? I searched but haven't been able to find a situation quite like this one. Thanks in advance for your help.

Really sorry to hear about your problem. Assuming the 2.3.6 stock image you flashed via Odin is the one provided by Przekret and that that didn't work, then I'd try one or both of these two longshots to try to clear possible corruption problems in either the kernel or modem spaces:
For each of the following wipe cache and Dalvik cache in CWM before flashing and again wipe Dalvik afterwards and also fix permissions:
1) Format system (do this 3x) under mounts & storage in CWM. Flash the standalone Darkside kernel X v1 final immediately after flashing, e.g., the current Darkside rom. (You'll need to wipe data, too, if not coming from a Darkside rom. Do not do any Superwipe - neither the standalone version nor using a flag.)
2) Flash the KID modem (do this 3x). Both Odin- and CWM-flashable versions are available. (You can always flash back to KL1 if the problem is fixed.)
Hope this is clear. It's late! These are both things that have helped get my phone out of troubles, though not as bad as yours. Good luck!
Sent from my SGH-T989 using XDA App

Also if u used the one from przekret then I'm almost positive that Odin package flashes the new radio too. If memory serves me right. Op let us know what happened

Thanks for your help. Unfortunately, nothing has worked. I'm on the phone with T-Mobile, I see no other solution but to get it exchanged under warranty and it's not getting here until March 15th, according to the representative. I suppose I'll just use a replacement phone in the meantime. It's just really weird and frustrating... I could understand a bad flash or something similar, but I followed every step accurately as I always have and everything was working just fine until it randomly decided to die without warning.

Well since you're getting another one anyways I would continue trying to fix this one, just in case you come up with a solution and for another worst case scenario for your new phone.
Powered by the SGSII....

I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA

shehrammajid said:
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Forgive me for asking, but what is the EFS folder?

My phone randomly freezes, and then thinks the battery completely drained...

My phone seems to freeze randomly when I'm using it and when I try to reboot it, it says the battery is completely drained even when it clearly isn't. I then have to boot it up plugged it in to a charger then it'll either charge quickly starting from 0% or it'll jump right back to the percentage it was at when it froze.
This started happening when I flashed from cm9 alpha 6 the cm10 ROM. I thought that the freezing was just caused from the ROM, so I put cm9 back on it, and it continued to do this. I flashed the beta 1 version hoping that would fix it, but the freezing still occurs. Has anyone else experienced something similar to this? Could it be caused by the kernel or modem that I have installed on my phone?

freeze issue
htb723 said:
My phone seems to freeze randomly when I'm using it and when I try to reboot it, it says the battery is completely drained even when it clearly isn't. I then have to boot it up plugged it in to a charger then it'll either charge quickly starting from 0% or it'll jump right back to the percentage it was at when it froze.
This started happening when I flashed from cm9 alpha 6 the cm10 ROM. I thought that the freezing was just caused from the ROM, so I put cm9 back on it, and it continued to do this. I flashed the beta 1 version hoping that would fix it, but the freezing still occurs. Has anyone else experienced something similar to this? Could it be caused by the kernel or modem that I have installed on my phone?
Click to expand...
Click to collapse
Did you do a clean install? I.e. factory reset/wipe all or agats format all then wipe d catche and catche. Then flash cm10 then gaps? Are you using op gaps?

emottau said:
Did you do a clean install? I.e. factory reset/wipe all or agats format all then wipe d catche and catche. Then flash cm10 then gaps? Are you using op gaps?
Click to expand...
Click to collapse
Yes, clean install. Didn't use agats format all though. Wiped both cache. Then flashed the ROM then gapps. Yes, I'm using the op gapps. The ICS ones didn't cause any issues before my phone started freezing up on me.
I'm not running any tweaks or mods. I just load up the ROM for the first time after a fresh install, and it freezes right away.

Just a cache wipe would certainly leave lots behind.
sent from my BAD A$$ Epic touch

That's the ics power save mode, while phones frozen you don't use any battery. Now that's genius .
Pp. .....LoL.
Sent from my ginger infused Mayan calculator.

Odin back to el26 and then flash CM10 with an unlocked recovery. Just make sure to fully wipe when switching roms
Sent from my SPH-D710 using XDA

patrao_n said:
Just a cache wipe would certainly leave lots behind.
sent from my BAD A$$ Epic touch
Click to expand...
Click to collapse
I formatted /data as well...Is this not enough? Is there a more proper way to wipe the phone?
J_Whit85 said:
Odin back to el26 and then flash CM10 with an unlocked recovery. Just make sure to fully wipe when switching roms
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Does a full wipe consist of more than formatting data, cache and d cache?
I've used calk's format all and it is still freezing up on me.

htb723 said:
My phone seems to freeze randomly when I'm using it and when I try to reboot it, it says the battery is completely drained even when it clearly isn't. I then have to boot it up plugged it in to a charger then it'll either charge quickly starting from 0% or it'll jump right back to the percentage it was at when it froze.
This started happening when I flashed from cm9 alpha 6 the cm10 ROM. I thought that the freezing was just caused from the ROM, so I put cm9 back on it, and it continued to do this. I flashed the beta 1 version hoping that would fix it, but the freezing still occurs. Has anyone else experienced something similar to this? Could it be caused by the kernel or modem that I have installed on my phone?
Click to expand...
Click to collapse
Hi htb,
I replied to your post in the CM10 thread with the following:
I had the exact same issue and it happened about the time I tried a new ROM. For me it was a bad battery. It was physically swollen and obviously bad. My nearest Sprint store have me a new one free.
If you're able, ODIN back to stock and take it in.
If not, a new battery is about $12 on Amazon.
Take out your battery and set in on a flat table. If it's bulged out at all, it's probably bad. It shouldn't spin like a top.
What you're describing is the exact same problem I had. I've tried two other batteries now and the problem seem fixed. No issues with ICS whatsoever. Good Luck!

MoMatt said:
Hi htb,
I replied to your post in the CM10 thread with the following:
I had the exact same issue and it happened about the time I tried a new ROM. For me it was a bad battery. It was physically swollen and obviously bad. My nearest Sprint store have me a new one free.
If you're able, ODIN back to stock and take it in.
If not, a new battery is about $12 on Amazon.
Take out your battery and set in on a flat table. If it's bulged out at all, it's probably bad. It shouldn't spin like a top.
What you're describing is the exact same problem I had. I've tried two other batteries now and the problem seem fixed. No issues with ICS whatsoever. Good Luck!
Click to expand...
Click to collapse
This was going to be my next step. I've got to complete stock and back, and I still get the freezing. Thanks for the advice, I'll definitely do that today. Hopefully this is the cause, because I don't know what else it could be.

htb723 said:
I formatted /data as well...Is this not enough? Is there a more proper way to wipe the phone?
Does a full wipe consist of more than formatting data, cache and d cache?
I've used calk's format all and it is still freezing up on me.
Click to expand...
Click to collapse
Wipe it manual through the recovery then flash calks format all then there is no question if it got wiped or not
Sent from my SPH-D710 using XDA

Sorry I only saw you said you wiped cache. Yes the battery is bad from my understanding.
sent from my BAD A$$ Epic touch

[HELP] Phone reboots or shutdown itself

Hi all, as the title, i have a big problem with my wonder. from 2 weeks my phone shuts down or reboots with apparently no reason. after the reboot/shutdown the battery is discharged. i had the cyano 10, then i used odin to set the stock rom. this did not solve the iussue.
i don't think that is a software problem, because i set the stock rom and did not solved. (tried also obviusly factory reset) i tried also to put some paper between the bottom of the battery for don't moving it (i thouth that there might be a contact). no result.
Any help will be appreciated, and sorry for my bad english

Try reflashing the CM ROM then the stock ROM again... Hope it helps
Sent from my GT-I8150 using xda app-developers app

TiTAN-O-One said:
Try reflashing the CM ROM then the stock ROM again... Hope it helps
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
already done but no result, thanks anyway

Let's see. Try getting your phone into CWM recovery. Given that you already have custom ROM of your choice stored in external storage.
Backup everything first. This is important. If better backup into external storage.
Then go to storage and mountings, wipe everything except external storage.
Then wipe cache, wipe dalvik and finally factory reset.
Do these accordingly, then flash custom ROM of your choice and with its Gapps(if required).
Then fix permissions.
Basically, just go Pristine. (a more detailed thread in the General Section)
If problem still persists. Go to SSC. Its hardware related.

i've tried all with no result, i will go to assistance for buying a new battery thank you all anyway for help

My friend had a similar problem on his S2, check if your battery looks/feels normal(like no bumps on its surface) the every time a battery I had goes like that it ends with exploding. My psp battery exploded, my friend's S2 battery exploded(luckily for him he had no cover on, otherwise it could've affected his phone) so check the battery and it's go buy a new one ASAP
Sent from my GT-I8150 using xda app-developers app

thank you, tomorrow i will go to a samsung store for buying a new one or for send the phone to assistance

[Q] Note II dying, Please help!

Hey guys.
This has only started to happen since I installed a rom that seemed to come with twrp and has removed my cwm..
My phone now seems to be very laggy when scrolling, even the notification noise lags and when it goes to into standby nothing happens it just goes off and the only way I can use the phone again is by taking the battery out.
I've tried flashing a new rom but thats not making a difference and i'm at a loss at what to do now....
Thanks for reading and any advice is appreciated.
*Forgot to mention, when being attached to pc via usb its not being recognised as being there, doesn't show as attached, just does nothing*

mrkupochan said:
Hey guys.
This has only started to happen since I installed a rom that seemed to come with twrp and has removed my cwm..
My phone now seems to be very laggy when scrolling, even the notification noise lags and when it goes to into standby nothing happens it just goes off and the only way I can use the phone again is by taking the battery out.
I've tried flashing a new rom but thats not making a difference and i'm at a loss at what to do now....
Thanks for reading and any advice is appreciated.
*Forgot to mention, when being attached to pc via usb its not being recognised as being there, doesn't show as attached, just does nothing*
Click to expand...
Click to collapse
Could you please specify what Rom and version that you flashed?
Sent from the rabbit hole.

Did you install one of the other custom recoveries manually yet? Btw. IMHO TWRP is the best anyways. Did you do a full wipe before installing new ROM? what kernel/version are you on?

I went from using the Android revolution HD 10.0 version with stock kernel, I changed to AllianceROM N7100 XXDMA6 JB V1.0 but didn't find it smooth enough so I swapped back to Revolution, thats when I found twrp had installed.
I've tried flashing the stock recovery and i'm still getting the same issue.
I've since reflashed cwm but this hasn't solved the problem unfortunatley.....No idea what to do

You should at least wipe cache/dalvik, or even after doing a backup with TB, a fullwipe.

Martux76 said:
You should at least wipe cache/dalvik, or even after doing a backup with TB, a fullwipe.
Click to expand...
Click to collapse
All done, several times, no difference

Have you considered it could be sudden death syndrome?
You should have nothing to worry about in terms of it dying, since you have a very recent base rom (dma6), which include safeguards against it.
When it freezes, have you tried waiting to see if the phone responds after you press the Home Button?
I ask this because I've read reports of people waiting for over 20 minutes for the phone to become responsive again after pressing the home button when in standby.
Another thing: have you ever flashed a full stock rom after DLL7 (including DMA6)? I ask this because DLL7 and later include a new bootloader that *supposedly* helps address the sudden death issue. It doesn't hurt to try anyway.
Sent from my GT-N7100

If ur pc recognises ur phone in download mode seaech the forum for rescue firmware (it comes with pit file) and flash it with odin..u should be sorted then.
Sent from my GT-N7100 using Tapatalk 2

[Q] Any possible ways to unbrick a softbricked SGH-I747

So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.

Re: [Q] Any possible ways to unbrick a softbricked SHGI747
MeatwadGetTheHunniesG said:
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Click to expand...
Click to collapse
This one should be easy, if you got a pass in ODIN, the hard part is over.
Go into stock recovery, wipe cache and perform factory reset. Reboot and report back. This generally fixes that bug. Its very common after an ODIN flash.
Sent from my SGH-I747 using xda app-developers app

RPelham said:
This one should be easy, if you got a pass in ODIN, the hard part is over.
Go into stock recovery, wipe cache and perform factory reset. Reboot and report back. This generally fixes that bug. Its very common after an ODIN flash.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Oh wow, thank you so much. That worked and everything is as it should be, just like when I got it out of the box. I thought I was screwed for a moment, I even had an upgrade and got a HTC One VX a couple days ago haha. Wow. Again, thank you. :highfive:

MeatwadGetTheHunniesG said:
Oh wow, thank you so much. That worked and everything is as it should be, just like when I got it out of the box. I thought I was screwed for a moment, I even had an upgrade and got a HTC One VX a couple days ago haha. Wow. Again, thank you. :highfive:
Click to expand...
Click to collapse
No problem at all =) Its pretty hard to completely brick your device unless you flash something made for a different phone lol. As long as your phone can see any signs of life (even a faint vibration), let us know and we are more than happy to help!
Sent from my SGH-I747 using xda app-developers app

I once spent four hours trying to hard brick a Galaxy S2 phone (science experiment).
I'd flash ROM's for other phones.
Kernel's.
Recoveries.
Took forever to finally hard brick it.

S.O.S. Phone is completely wiped only dowload mode and recovery work.
Okay so I think I kind of put myself in a sticky situation. I tried to flash a custom rom onto my phone but in the process deleted my modem file everything worked fine except for the fact that I couldnt make calls or text messages. Basically a $400 dollar multimedia device. At this point I just want to put my phone back to the way it was when I got it at the AT&T store. My phone model is SGH-i747 Galaxy S3 that came with JB 4.1.1 pre installed.

I once spent four hours trying to hard brick a Galaxy S2 phone (science experiment).
I'd flash ROM's for other phones.
Kernel's.
Recoveries.
Took forever to finally hard brick it.
Click to expand...
Click to collapse
Out of curiosity, how did you finally manage to brick it?
Sent from my Nexus 7 using xda app-developers app

solution
MeatwadGetTheHunniesG said:
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Click to expand...
Click to collapse
There's another thread called stuck on boot screen with same issue. Had same issue with simular Rom had to boot in recovery and clear cache and user settings. And no longer an issue

Soft bricked...
I'm currently dealing with a soft brick that I can't unbrick either. Got a replacement Sgh-i747 thru insurance. Rooted and decided to try twrp instead of cwm. Went to flash the ROM and didn't realize twrp didn't read ext SD cards until after i wiped my phone and OS. Tried reverting back to stock but Odin fails on the stock firmware every time. Tried flashing cwm and flashing a ROM but keep getting error 7 and no Roms flash. Any ideas as to where to start over with?

kinjo1023 said:
I'm currently dealing with a soft brick that I can't unbrick either. Got a replacement Sgh-i747 thru insurance. Rooted and decided to try twrp instead of cwm. Went to flash the ROM and didn't realize twrp didn't read ext SD cards until after i wiped my phone and OS. Tried reverting back to stock but Odin fails on the stock firmware every time. Tried flashing cwm and flashing a ROM but keep getting error 7 and no Roms flash. Any ideas as to where to start over with?
Click to expand...
Click to collapse
I think I did someting like that too nd now I cant install any ROM and TWRP complains that I have no OS inside the phone.I tried modifying the assert-script file but it then eventually ends up at STATUS 6 and not status 7 again.Pls and Pls help us

You have to be on twrp 2.7.x to install any kk ROMs.
Sent from my SGH-I747 using Tapatalk