I have read several other threads but no one ever quite seemed to resolve the problem. Shortly after i unlocked my phone (freegee method) i decided to switch back from aosp to stock. after it connected to wifi or data network my phone reboots every time it connects. i tried using a teeny bin but it changes my bootloader and i think thats whats causing my bootloops when i try to provision it. flashing a full stock bin isnt helping either because my phone refuses to fully boot up its just hanging at the bootanimation.
so essentially i can flash myself into a stock based rom but i cant provision anything or switch roms because ill have to repeat the whole process.
oliverpuczyk2 said:
I have read several other threads but no one ever quite seemed to resolve the problem. Shortly after i unlocked my phone (freegee method) i decided to switch back from aosp to stock. after it connected to wifi or data network my phone reboots every time it connects. i tried using a teeny bin but it changes my bootloader and i think thats whats causing my bootloops when i try to provision it. flashing a full stock bin isnt helping either because my phone refuses to fully boot up its just hanging at the bootanimation.
so essentially i can flash myself into a stock based rom but i cant provision anything or switch roms because ill have to repeat the whole process.
Click to expand...
Click to collapse
you need to do a full wipe. This happened to me as well before. This is how I fixed it
in TWRP, go to advance wipe, and wipe system along with data, davilk, an cache. This will fully wipe your rom so be prepared to install a rom afterwards. It will not wipe your sdcard.
Th a t was the first thing i tried. I would like to just be able to flash a full bin at this point. Im really not sure why its not booting fully after flashing and i havent even been able to get a bugreport. If anyone knows how to pull apart one of the bins and all the partitions of this phone ill just do everything 1 by 1
Lngpst to stock (unrooted and locked), root it, use the freegee special sbl unlock method, then flash. I have the sane thing happen every time I try to come back to a stock based ROM after going aosp based. Reboots on any data connectivity.
Sent from my LG-LS970 using xda app-developers app
Every time I try to restore with lgnpst it'll hang up at the boot animation and refuse to fully boot. I used the full zvb to try it. Ive already downloaded it twice in case I had a bad file. Right now I kinda want to know why our phone s do this.
oliverpuczyk2 said:
I have read several other threads but no one ever quite seemed to resolve the problem. Shortly after i unlocked my phone (freegee method) i decided to switch back from aosp to stock. after it connected to wifi or data network my phone reboots every time it connects. i tried using a teeny bin but it changes my bootloader and i think thats whats causing my bootloops when i try to provision it. flashing a full stock bin isnt helping either because my phone refuses to fully boot up its just hanging at the bootanimation.
so essentially i can flash myself into a stock based rom but i cant provision anything or switch roms because ill have to repeat the whole process.
Click to expand...
Click to collapse
1. How and/or what is being changed on the bootloader? Do you mean recovery?
2. When you flash back to stock from ASOP, is it hanging at the 4GLTE screen? If that's what you mean then:
3. If you're stuck at the 4glte screen: To get to stock recovery - Power off phone. You need to hold power button for about 20 sec to get it to turn off. Then press and hold vol down+power - The LG logo will come on, then the capacitive lights. Immediatly let go when the capacitive lights turn on. It takes a few seconds to work. Data wipe/Factory reset. Reboot.
Related
Ok, so here is my story:
I rooted way back in July right after I got my Evo, so I started on Android 2.1. I flashed and used OMJ's ROM for quite a while until I discovered Cyanogen mod, which I switched to after trying OMJ's 2.2 ROM.
I used CM6 for a long time, eventually flashing some nightly builds, culminating in nightly build number 140. At some point in this process, I started having real trouble with bootlooping CONSTANTLY (and I couldn't even make a nandroid backup because it would reboot inside the backup process). I eventually got it to stop bootlooping after many many reboots and wipes (full wipe, cache wipe, dalvik wipe) and restarts and got CM to boot.
I just now flashed CM6.1 and started getting constant bootloops again. I assumed it was a problem with CM, so I decided eff it, I'm going with a different ROM and downloaded Calkulin's EViO 1.5 rom to try, but it can't boot either.
I can get to the android screen, which displays no signal, then it reboots. I can't get out of this cycle. When I was on CM, I had issues with starting up - I had to hold down the power button quickly and press airplane mode, then it would reboot again, but it would come all the way up. Then once it was fully booted I could disable airplane mode and it would stay online. After that point, I just decided never to reboot the phone, but this is a huge problem that I can't figure out how to fix.
I have tried wiping using Clockwork and Amon Ra, but neither makes a difference.
Any help would be GREATLY appreciated. Thanks!!!
it reboots while making nandroid? So even if you hold vol down + power and go to the recovery from there it is rebooting?
xHausx said:
it reboots while making nandroid? So even if you hold vol down + power and go to the recovery from there it is rebooting?
Click to expand...
Click to collapse
Correct, I hold volume down + power to get into recovery, then choose nandroid and backup, then while it is creating a nandroid backup, it reboots.
Does anyone have any ideas? At this point, I have no clue what to do, and I can't boot into any ROM.
If you Google it you'll see its an incredibly common problem not just with those of us who have modded our phones but those with stock roms who have never done so it happened to me when I originally flashed cm6 to my phone as well but it eventually fixed itself if you can get it to boot try factory reset it may help
Sent from my PC36100 using XDA App
hackulous said:
If you Google it you'll see its an incredibly common problem not just with those of us who have modded our phones but those with stock roms who have never done so it happened to me when I originally flashed cm6 to my phone as well but it eventually fixed itself if you can get it to boot try factory reset it may help
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Factory reset just wipes your data using your recovery doesn't it? Either way, I've tried that, and no dice.
I mean, I guess at the very least I could try to bring the phone into Sprint... is there a shipped RUU I can flash so they can look at it?
edit: found the latest RUU (http://forum.xda-developers.com/showthread.php?p=8474707)
I'm gonna try this and see what happens.
http://www.google.com/m/url?client=...IQFjAA&usg=AFQjCNHQ2016xLF_DLz7uVoilk8Hm1EsRg
Sent from my PC36100 using XDA App
same problem. no solution. i am now fully bricked, aka i reboot before i can pull down lockscreen (rom changes, unroot, nothing works) return before it gets so bad you cant unroot.
No good man I hope you got insurance
Sent from my PC36100 using XDA App
Ewe, thats no good. I would use the ruu but Do Not Use The Newest One. You will lose root and the new 3.30 people are having trouble rooting
Sent from my PC36100 using XDA App
same thing happening to me. Stuck in bootloop now, started out as just a random reboot that would boot than reboot than hold for a while. Right now im completely stuck in bootloop =(.
Is there a way to put a stock rom on my phone with just booting to recovery?
These sound like hardware issues but if your recovery is working fine then it may be something else. Did you try the RUU while in the recovery?
Just don't use the newest one
Sent from my PC36100 using XDA App
dkdude36 said:
same problem. no solution. i am now fully bricked, aka i reboot before i can pull down lockscreen (rom changes, unroot, nothing works) return before it gets so bad you cant unroot.
Click to expand...
Click to collapse
I was finally able to get to a point where I could get it to boot - here is what I did.
I wiped everything using amon ra's recovery, then flashed the latest cyanogen mod from here: http://mirror.teamdouche.net/get/supersonic/update-cm-6.1.0-RC1-Supersonic-signed.zip, then when it booted, it would get constant bootloops, but it would get to the home screen for a few seconds each time.
You have to click through the intro menus reaaaallly freakin fast so you see the desktop with the live wallpaper. DON'T sign into a google account. It will probably bootloop again, and if it doesn't, quickly hold down the power button and select airplane mode. If it reboots again, it will power up completely successfully in airplane mode. Then make sure you're in an area of good signal and disable airplane mode until you have 3G, and then sign into a google account. If it starts bootlooping again, quickly hold the power button and press airplane mode - you can always boot successfully in airplane mode for some reason...
xHausx said:
These sound like hardware issues but if your recovery is working fine then it may be something else. Did you try the RUU while in the recovery?
Just don't use the newest one
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It could be hardware related, but I'm not 100% sure at this point...
The reboots seem to be correlated with signal strength. If I have 1 bar of signal (in CM, so not cell signal), it will reboot before it gets to 3G.
Also any flash on a website reboots the phone for some reason. I don't know if that's common or not.
For the past several months my phone would restart randomly when I used 3G, GPS or sometime just from heavy usage. It would turn off, boot to the white HTC screen but then the screen went black and it would vibrate 3 times and a led would blink. At that point the only way to turn it back on was to pull the battery and power on (although that usually didn't work until after a few tries or letting it sit for a while).
It has done this with both CM7.1 and decks 1.3 and with the Tiamat 3.3.7 & 4.1 kernels. I flashed Mason .14 on Tuesday hoping it might fix the problem. It did at first but after 24 hours it was back to restarting randomly, only this time it was worse. I was also getting a lot of force closes and it would restart even it was sitting unused. It would take hours until I could get it to successfully boot again. I attempted to do a full wipe and install CM7.2 yesterday only to find out I can not boot into recovery, attempting to do so causes the phone to turn off (I tried both through holding the power button and selecting recovery and through the bootloader).
As of right now my phone will not turn back on at all (going on 4 hours), I've had it successfully boot twice only to immediately turn off, other times it gets stuck on the white HTC screen.
I am still able to access the bootloader so I'm thinking my best option may be to place a PC36IMG.zip on my sdcard and see if I can't flash back to stock and then load CM7.2. My concerns are a) not sure if that will even work b) if the phone were to turn off in the middle of that would it completely brick my phone?
Sorry for the long post but I just wanted to provide as much info as possible. Any thoughts/suggestions would be greatly appreciated.
Can't boot into recovery? Have you tried reflashing your recovery? Get a PC36IMG file of your desired recovery (preferably amonRA, or drellisdee) and flash it thru bootloader. It only takes a second to flash, so I wouldn't be too worried about it shutting off while flashing it.
That's all I got.
Sent from my PC36100 using xda premium
scottspa74 said:
Can't boot into recovery? Have you tried reflashing your recovery? Get a PC36IMG file of your desired recovery (preferably amonRA, or drellisdee) and flash it thru bootloader. It only takes a second to flash, so I wouldn't be too worried about it shutting off while flashing it.
That's all I got.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Unfortunately that doesn't work. Flashes the recovery just fine but I still can't access it. I did manage to get my phone to boot into android after trying, not sure if that's a coincidence or not.
So I'm left with my original option, flashing a stock PC36IMG.zip. Also this might be a dumb question but can I rename anything PC36IMG.zip and flash? If so I could just rename Calkulin's format all, flash that and then repeat the process with CM7.2. Anyone know if this will work?
Edit: Should probably also ask if anyone knows what is causing this, is it a kernel issue?
Just a thought, maybe a bad battery or a bad usb?
Did you try the battery in another phone? Or, another battery in your phone?
Sounds like it may also be going for the reboot of death... If your recovery is corrupted and getting random reboots, maybe your internal storage is going bad...
Sent from my PC36100 using xda premium
imheroldman said:
Just a thought, maybe a bad battery or a bad usb?
Did you try the battery in another phone? Or, another battery in your phone?
Sounds like it may also be going for the reboot of death... If your recovery is corrupted and getting random reboots, maybe your internal storage is going bad...
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I was able to flash back to stock and it is still having similar problems. Turns off during any sort of data usage both 3g and Wifi. The fact that it has happened on multiple ROMs, multiple kernels, and multiple radios makes me think it is something hardware related. I guess I will talk to sprint and see what they can do.
BTW does anyone know of a method to flash an S-On zip file as a PC36IMG in the bootloader? I am still S-Off because I can't go into recovery to flash.
mcotter said:
BTW does anyone know of a method to flash an S-On zip file as a PC36IMG in the bootloader? I am still S-Off because I can't go into recovery to flash.
Click to expand...
Click to collapse
Well after going back to stock but still being S-Off I decided to try reflashing Amon_RA and I eventually got it to boot into recovery. It was similar to booting into the OS, I just had to pull the battery and wait 30+ mins before trying and then boot into bootloader and select recovery. It was a PITA since I needed flash a couple things but it worked. Got it back to S-On and took it to Sprint. Of course they didn't bother checking for any of that haha but I was able to get a replacement EVO.
I just tried to load a new rom on to my phone. I used twrp to do a factory reset and now it wont turn on, at all. I wont even get to the splash screen. I've tried removing the battery and then turning on, no luck. I've also tried holding the keys to get into recovery mode, nothing works!!
Please tell me its not a brick!
which rom where you running
which rom are you trying to load
kingskater said:
I just tried to load a new rom on to my phone. I used twrp to do a factory reset and now it wont turn on, at all. I wont even get to the splash screen. I've tried removing the battery and then turning on, no luck. I've also tried holding the keys to get into recovery mode, nothing works!!
Please tell me its not a brick!
Click to expand...
Click to collapse
It really helps to know what ROM you were flashing, what method you used to flash, i/e ODIN flash then TWRP wipe, or TWRP zip install and wipe.
I would highly bet that you flashed an incompatible ROM, that was meant for another version of the S III, which would cause you to be in this current state. Which best case scenario you take it back to AT&T and tell them you were in the middle of using KIES to upgrade to the new OFFICIAL Jellybean, and your computer froze during the install, after which your phone never turned back on.
Second case scenario, you call up Samsung and get an RMA from them, wait 2-4 weeks and get your phone back, often times not having to pay the "fee" for repairing it.
Worst case scenario, you have a nice shiny new beer coaster. In which case you could mail to me and I could use it as such, as I am currently out of coasters.
Try using Odin to fix
1. Download Odin and stock ROM rooted
2. Put phone in Download mode (not recovery) by pressing and holding Vol Down + Home + Power
3. Open Odin on computer and load the ROM
4. Hit Start
Refer to the following thread for a more in-depth guide:
http://forum.xda-developers.com/showthread.php?t=1739426
I got it fixed. I had to pay some kid to JTAG repair it.
I've got a Galaxy Tab P5210 that's stuck in a constant boot loop. I flashed it with the correct stock firmware from SamMobile using Odin, but it fails to boot properly. It automatically boots to the stock recovery screen, but the problem is it will instantly reboot as soon as it reaches this screen. I see the dead android with the red triangle and exclamation point for just a second, and it instantly reboots. Is that normal? I don't think that's normal. From what I've been reading, this screen is supposed to stay there until you push the volume keys to bring up a menu, but it reboots so fast that I don't have a chance to even push anything.
I've tried flashing it with other recovery images. I tried using CWM, and it almost worked. With that, as soon as the tablet booted, I'd see the CWM splash screen, and it would instantly reboot. Similarly to how it's booting now but with stock recovery.
I'd like to point out that I've never messed with anything like this before. I work in a computer/small electronic repair shop and a customer brought it to me. She ended up getting into stock recovery and a friend of hers did some serious damage in there which prevented it from booting properly. Normally we don't mess with things like this but, with it being how it was, I figured there was no way I could make it even worse than it already is by working on it. I thought if I flashed the original stock firmware back to it, it would fix it, but that looks like a no-go since it's still booting the same way it was when she first brought it to me.
Is this thing completely broken or is there still hope for it?
No - it should be recoverable. However - any data will most likely be lost.
When you flash with Odin, make sure only F. Reset Time is checked. Use Odin 3.07. Make sure again that firmware is correct before you flash. After it flashes, power off and then on again
Latest KK firmware for the US version of the 5210 is P5210UEU0CNK1_P5210XAR0CNK1_HOME.TAR
Good luck. If you're trying to root, then there are threads in the 10.1 Dev section that should help
M,
this firmware was always my goto for device recovery/restoration https://www.androidfilehost.com/?fid=23060877490005046
posted by user chpettit , flash with odin 3.07
m
OKAstro said:
No - it should be recoverable. However - any data will most likely be lost.
When you flash with Odin, make sure only F. Reset Time is checked. Use Odin 3.07. Make sure again that firmware is correct before you flash. After it flashes, power off and then on again
Latest KK firmware for the US version of the 5210 is P5210UEU0CNK1_P5210XAR0CNK1_HOME.TAR
Good luck. If you're trying to root, then there are threads in the 10.1 Dev section that should help
Click to expand...
Click to collapse
Not interested in rooting, just wanna get the stock firmware back on. Maintaining data isn't a necessity, the customer just wants it back in working order. I tried using that firmware, but I had Auto-Reboot checked.
EDIT
Yeah, it's still doing the same thing. When I first boot it up post-firmware flash I see an Android with a loading bar underneath it, and then it reboots. When it boots again, I see the same Android and then it suddenly changes to the dead one with the red triangle. Maybe I'm just doing something wrong here with the button presses following the flash?
EDIT2
It looks to me like the stock recovery image is just broken, since the tablet just automatically reboots the instant it attempts to load it up. Flashing a new firmware replaces that though, so I don't know how or why it would even be corrupted. Odin reports no errors, so I don't know what's going on. And every guide I'm reading with fixing bootloops all say "go into stock recovery and clear the cache", but I can't even boot into stock recovery. It's like it's not even there. And I know it's not a power button issue causing it to shut down, I can power the device off fully with it, and it will stay off until I press it again. I'm banging my head against the desk here.
What if you flashed a TWRP recovery in Odin. Then if that's successful, boot into recovery and wipe/format everything except ext SD, Then try the ODIN flash again with filr your stock tar
I'm having the same problem and that didn't work for me. It shows the twrp splash screen and reboots. I'm looking for the .pit file it has to be the recovery partition right?
Sent from my LG-D851 using Tapatalk
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
atlJE said:
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
Click to expand...
Click to collapse
I have the same issue. I suspect the person I let use it tried to use the options menu to reset the phone back to factory specs, which I was warned on here that would brick it, so mine is stuck in the round and round boot screen for CM. I think you're supposed to use the factory reset in CWM to delete personal stuff. I'm trying to figure out how to fix it and if I come up with something I'll let you know.
flash back to stock rom
atlJE said:
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
Click to expand...
Click to collapse
Good thing is you are not "hard bricked" just "soft bricked." Press the power button and volume up and hold till your phone reboots then immediately press the volume button and power down button to enter recovery.Then do a complete wipe, factory reset, then and only then reflash your stock CWM backup of your stock Rom . Just guessing mind you ,because I do not know every single thing you did before trying to return to stock but you should always do a full Wipe or factory reset before flashing between different roms. If your trying to flash a stock image, not a CWM backup, of your firmware you'll need to first reflash your stock recovery and relock your boot loader.
Is your phone a single SIM or dual SIM? Dual SIM phones have allot more issues on Cyanogenmod . If yours is dual SIM I'd stick to stock Rom or sense based custom roms made for our device. By the way what didn't you like about CM if your on a single SIM phone? It had a few issues but with a few tweaks you can get it working great and it's alot less bloated than stock lollipop. I'm on unofficial 12.1 CM with the a5_chl single SIM and it's fine. Having said that I had to tweak several things and I exempt dual SIM versions from my reasons for me liking this Rom. I get that it's sadly alot buggier for those phones . Let me know how things go in fixing your issue and best of luck.
---------- Post added at 10:43 PM ---------- Previous post was at 10:02 PM ----------
Ddreth said:
I have the same issue. I suspect the person I let use it tried to use the options menu to reset the phone back to factory specs, which I was warned on here that would brick it, so mine is stuck in the round and round boot screen for CM. I think you're supposed to use the factory reset in CWM to delete personal stuff. I'm trying to figure out how to fix it and if I come up with something I'll let you know.
Click to expand...
Click to collapse
First thing, some friendly advice and I truly do mean friendly, not accusing, but you should never let anyone else touch your device when it's in custom recovery. They can seriously mess it up not just"soft brick" it like yours is now.
2nd thing is the factory reset in your custom recovery doesn't have anything to do with your personal files. It's to clean your system and its data so that you can do a fresh install of a different Rom. It's called a "clean flash." A dirty flash is when your upgrading the same custom Rom and you just flash it over the previous version without wiping then clear your Dalvik cache and reboot. These wipes leave your personal files on your internal and external SD card intact unless you specifically wipe then in your custom recovery . They just call it factory reset to make it familiar to the stock Roms use of the term in my opinion. When you have this"soft brick" you can press your power button and volume up to reboot then quickly press power button and volume down to enter recovery. Then factory reset or wipe Dalvik cache if not wanting to reset and reboot one or the other should get you back into your rom.
Hope this helps and good luck plus let me know if this works to resolve your issue. Be happy to help in any way because I have been there myself in the past. Bootloops, soft bricks,etc etc................... If you can name it, I've messed it up.