Develop Bugs

Help, bootloop and i can't enter to recovery!!

Just install a .zip, following the tutorial, of ICS animations, I did everything exactly as shown (http://forum.xda-developers.com/showthread.php?t=1342117), then reboot and get stuck on the screen Motorola, forcing me to install the previous framework, reboot, still M screen, forcing me again, to reinstall the CM7.1, but still no results, stuck on the M screen. Now i flash CEE, but when it starts does not exceed 2 seconds on the display of "android" and starts again and again, I can't enter to recovery, I get no blue light when it starts, I can only enter the screen to flash a new firmware, but i flash twice.
Help me please, i don't know what to do...

Bleak3993 said:
Just install a .zip, following the tutorial, of ICS animations, I did everything exactly as shown (http://forum.xda-developers.com/showthread.php?t=1342117), then reboot and get stuck on the screen Motorola, forcing me to install the previous framework, reboot, still M screen, forcing me again, to reinstall the CM7.1, but still no results, stuck on the M screen. Now i flash CEE, but when it starts does not exceed 2 seconds on the display of "android" and starts again and again, I can't enter to recovery, I get no blue light when it starts, I can only enter the screen to flash a new firmware, but i flash twice.
Help me please, i don't know what to do...
Click to expand...
Click to collapse
have you wiped data/cache yet? looks like you havent, because if you did, you wouldnt get bootloop after flashing an sbf. enter stock recovery (when switched off, hold volume down, and then press the power button. hold them down till the m logo shows up. after that, a triangle with an android figure will show up, press vol up and vol down az the same time), wipe cache/data, and try again!

zakoo2 said:
have you wiped data/cache yet? looks like you havent, because if you did, you wouldnt get bootloop after flashing an sbf. enter stock recovery (when switched off, hold volume down, and then press the power button. hold them down till the m logo shows up. after that, a triangle with an android figure will show up, press vol up and vol down az the same time), wipe cache/data, and try again!
Click to expand...
Click to collapse
IT WORKS!!!!, ohhh, i totally forgot how to enter the stock recovery and the wipe after flash an sbf, thanks you, really.

Phone keeps rebooting and not going into os

Flashed a new kernel with aokp jb with the lastest update, and when I went to fix permission it look an accessive amount of time so I waited and waited until I restarted the phone. Now the phone just boot loops, as soon as it hits the aokp animation. Held down the menu and volume button on boot and it brought me to an area where if I press the volume up button I can "install a customer os" then it brings me to "ODIN MODE" and has the andriod dude pic and says downloading do not turn off target..... however it just hangs there and hasn't done anything past that point.. Any ideas?

You need to hold menu and vol+
Sent from my SGH-I747 using xda premium

Steve_Maio said:
Flashed a new kernel with aokp jb with the lastest update, and when I went to fix permission it look an accessive amount of time so I waited and waited until I restarted the phone. Now the phone just boot loops, as soon as it hits the aokp animation. Held down the menu and volume button on boot and it brought me to an area where if I press the volume up button I can "install a customer os" then it brings me to "ODIN MODE" and has the andriod dude pic and says downloading do not turn off target..... however it just hangs there and hasn't done anything past that point.. Any ideas?
Click to expand...
Click to collapse
vol + and menu for recovery mode
vol - and menu for download mode
if fixing the permissions don't fix the problem, check if you pick a kernel for ICS or JB. If you have the right kernel, perform a full wipe and flash your rom again and see if it boots.

Reinstall aokp and full wipe. Let it boot once before installing a custom kernel. Its a common occurrence and a known "problem." Just let it boot once as stock aokp and you should be fine.

partial boot, power off
I have a similar problem, I have an At&t samsung galaxy s3 I had flashed a Rom that I didn't like and was restoring from previous back up, I didnt want to re load all the apps and data I had on that restore as I was running low on device memory so I went to "advanced restore" and there were 4 options to choose, I chose the top option. I don't recall what it is because I cant get into recovery now doing the menu volume+ or using the jig I have to get into Download mode and start over completely. When I power on it flashed Samsung, then Samsung galaxy s3 then screen goes black and powers off. I am assuming when I chose the 1st option I restored the OS but not the bootloaders. I have read previously how to load them from the sd card but can't find that post. Any help would be greatly appreciated.

CM10 Boot Loop? Help!

I rooted my phone to a stock root on my Jelly Bean Galaxy S3. I then installed ClockworkMod through ROM Manager, then CM10. It installed OK, now stuck in a boot loop. No big deal, I'll reinstall to my Kies backup. Doesn't work, I can't seem to get into recovery mode. I hold the buttons, it vibrates, and the screen stays black until I let go at which point it boots to that horrendous boot loop. I really need my phone back!
P.S. Please explain as if I am five years old.

Flightfreak said:
I rooted my phone to a stock root on my Jelly Bean Galaxy S3. I then installed ClockworkMod through ROM Manager, then CM10. It installed OK, now stuck in a boot loop. No big deal, I'll reinstall to my Kies backup. Doesn't work, I can't seem to get into recovery mode. I hold the buttons, it vibrates, and the screen stays black until I let go at which point it boots to that horrendous boot loop. I really need my phone back!
P.S. Please explain as if I am five years old.
Click to expand...
Click to collapse
Download mode couldnt get any simpler bud
Edit: just incase if you dont know its down home power button to get to it, find your galaxy s3 firnware (ATT/Bell etc...) and your back stock nonrooted. And then you can root againif you wanna

While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.

mrhaley30705 said:
While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.
Click to expand...
Click to collapse
Did you read the question bro.. he said he CAN'T go to recovery mode only other option is download mode

No, the option is to boot into recovery and perform a factory reset (which may fix his problem). IF that doesn't fix his problem, he can flash a different ROM from recovery, provided he had custom recovery.
The only difference in getting to download as opposed to recovery is which volume button you use. Chances are if he can't 3 button into recovery, download will be the same result.

Thanks
Got it fixed guys, thanks for the help, now I'm back at Stock Rooted 4.1.1, but am still on the quest for a deodexed rom!

Excellent suggestion - it worked for me
mrhaley30705 said:
While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.
Click to expand...
Click to collapse
I got a Galaxy S III on 23rd Dec 2012 with Ice Cream Sandwich installed. A couple of weeks later it updated itself with a little help from me to the latest Jelly Bean. Since then it's gone into the reboot loop 3 times without any provocation; i.e. I get it out of my pocket and it's in a reboot loop but it had been fine the last time I used it. I tried pressing various buttons alone and in combination and eventually it came out of the loop. At no time did I have to remove the battery. The only mod I've made to it is the addition of a 64GByte SD card, apart from the upgrade to Jelly Bean. I've seen many posts on this problem but yours is the first that confirms my solution for getting out of it. It's obviously a common problem so somewhere there must be a description of what causes it and, hopefully, how to prevent it as it's a real nuisance when you want to use your phone and it's in a reboot loop. If and when I find a definitive article I'll post here again.
Thanks MrHaley.

[Q] Bricked Samsung Galaxy Nexus I9250

i seem to have hard bricked the device and i have been attempting to find a way i can fix it for hours.. i seem to be stuck. Its stuck on the boot animation cyanogenMod logo. I am unable to get into the recovery mode, as well as fast boot mode. i let it sit on that boot logo for hours without anything at all happening. No progress what so ever. Now the biggest thing i am trying to figure out is how i even managed to get this to happen. there was a software update notification that i received, so i figured it may have been the Android L update or something, so without taking into considering what exactly i was agreeing to i accepted, and continued. Let it reboot, and thats how i got to come across this issue. Any suggestions.

So if you hold down "volume up", "volume down", and then press and hold the power button, does it not boot into the bootloader? You may have to hold all three down for 15 seconds or so... Based on the fact that you can see the boot animation, it tells me that your bootloader is indeed functional, so, once booted into the bootloader, you can easily flash the factory images (as per this) and restore your device to working condition.

efrant said:
So if you hold down "volume up", "volume down", and then press and hold the power button, does it not boot into the bootloader? You may have to hold all three down for 15 seconds or so... Based on the fact that you can see the boot animation, it tells me that your bootloader is indeed functional, so, once booted into the bootloader, you can easily flash the factory images (as per this) and restore your device to working condition.
Click to expand...
Click to collapse
Yeah ive tried that, and nothing is working it just keeps going back to that same boot animation & im out of ideas. Iknow there has to be a way though.

Jewelzxo said:
Yeah ive tried that, and nothing is working it just keeps going back to that same boot animation & im out of ideas. Iknow there has to be a way though.
Click to expand...
Click to collapse
What I find strange is that it boots to the boot animation -- that means the bootloader has loaded up the kernel and Android is attempting to start. The bootloader loads up before anything, so it is obviously working. Don't know why you can't access its menu though with the 3-key press. Maybe one of your volumes keys is not working properly? By holding those three keys down, it should not boot to the boot animation...
Can you get into download mode? Hold only volume down and press and hold power. If so, then you can use Odin and flash a stock ROM as per this thread.
In any case, if you can't get into the bootloader or download mode, then your only option is using OMAPFlash (as per this thread). That will re-flash your bootloader. If you still can't get into the bootloader menu after that, then there is a hardware issue.

Boot Loop

Ok I feel stupid. I have been this stuff for a while but I just got a new in box Note 4 to play with and trying to root. CID is 15 and it came with 6.0.1 and I just Odin to 5.1.1 and it just boot loops. I tried running the Odin several times and same thing.
I flashed this file 5.1.1 N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar
What am I missing here?

Not alot of help in this Note 4 area... You all are to quiet. LOL It seems like the rooting community is going away. I myself will not own a phone that is not rooted. Running the Moto X Pre as my daily driver and it's an awesome phone.
So I will post what I did to fix this Boot Loop Issue after trying to downgrade firmware to 5.1.1 from 6.0.1. I picked up the Note 4 from a local sell new in box for 100 bucks I figured what the hell kool phone to play with.
Ok I just flashed this official verizon 5.1.1 firmware N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar with Odin 3.12 again
So After I got done flashing this firmware I did these steps.
1. Turn phone off completely.
2. To start the phone, press the following keys simultaneously: Power Button, Home Button, Volume +
3. When the first logo can be seen on the screen, release the power button, but hold the Home button and the Volume + button pressed
4. It now appears on the screen of your phone, a small menu. Navigate with the Volume + and Volume - keys. An entry is selected by the Power Button
5. Select in this menu now "Wipe Cache Partition".
6. After you have selected the entry the Wipe cache is flushed. This takes a few seconds. Then it automatically returns to the small menu.
7. Now select the top entry with "Reboot Now"
Also while I was in that menu area I went ahead and did a factory reset wipe all data.
My Verizon Note 4 is now on 5.1.1 and works.
Now I will continue to root this thing.

kendive said:
Not alot of help in this Note 4 area... You all are to quiet. LOL It seems like the rooting community is going away. I myself will not own a phone that is not rooted. Running the Moto X Pre as my daily driver and it's an awesome phone.
So I will post what I did to fix this Boot Loop Issue after trying to downgrade firmware to 5.1.1 from 6.0.1. I picked up the Note 4 from a local sell new in box for 100 bucks I figured what the hell kool phone to play with.
Ok I just flashed this official verizon 5.1.1 firmware N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar with Odin 3.12 again
So After I got done flashing this firmware I did these steps.
1. Turn phone off completely.
2. To start the phone, press the following keys simultaneously: Power Button, Home Button, Volume +
3. When the first logo can be seen on the screen, release the power button, but hold the Home button and the Volume + button pressed
4. It now appears on the screen of your phone, a small menu. Navigate with the Volume + and Volume - keys. An entry is selected by the Power Button
5. Select in this menu now "Wipe Cache Partition".
6. After you have selected the entry the Wipe cache is flushed. This takes a few seconds. Then it automatically returns to the small menu.
7. Now select the top entry with "Reboot Now"
Also while I was in that menu area I went ahead and did a factory reset wipe all data.
My Verizon Note 4 is now on 5.1.1 and works.
Now I will continue to root this thing.
Click to expand...
Click to collapse
so the bootloop was caused by ? im gonna guess dmverity but it could also just been misflashed ....failing to uncheck the reboot upon flash option for example . powering the phone all the way down then into recovery ....id like to go with misflash if you had failed dmverity you would have seen a red message in recovery stating that was the case

Boot Loop help or can I pay someone to fix?
So my wife's Note 4, not rooted. Must have failed during a forced update. It's gone into 2 types of boot loops. Either it says 'Recovery boot' only, with no recovery menu, followed by the 'Galaxy' screen, and then back to the boot loop. Or it shows the Galaxy screen, and just barely begins to initialize the 'Samsung' logo with the 'S' first, and then back to boot loop.
I've tried about 3 different firmwares through Odin, including successful ones that 'Pass'. And it still exhibits the same loops. I've tried bootloaders in Odin, about anything you can imagine. It's clearly not bricked, but I cannot for the life of me make progress.
The old battery I thought was going bad (a lot of bad battery problems with loops), and I bought a new battery. But given it will only loop (outside of the download screen), I can't even get the batteries to charge because it's either looping or on download screen.
Any questions or ideas? Or is there a user who is an expert I can ship and pay to fix?
I'm a novice in large part. Thanks guys.

geigercounter said:
So my wife's Note 4, not rooted. Must have failed during a forced update. It's gone into 2 types of boot loops. Either it says 'Recovery boot' only, with no recovery menu, followed by the 'Galaxy' screen, and then back to the boot loop. Or it shows the Galaxy screen, and just barely begins to initialize the 'Samsung' logo with the 'S' first, and then back to boot loop.
I've tried about 3 different firmwares through Odin, including successful ones that 'Pass'. And it still exhibits the same loops. I've tried bootloaders in Odin, about anything you can imagine. It's clearly not bricked, but I cannot for the life of me make progress.
The old battery I thought was going bad (a lot of bad battery problems with loops), and I bought a new battery. But given it will only loop (outside of the download screen), I can't even get the batteries to charge because it's either looping or on download screen.
Any questions or ideas? Or is there a user who is an expert I can ship and pay to fix?
I'm a novice in large part. Thanks guys.
Click to expand...
Click to collapse
Hi when in odin ensure you untick reboot after flash . Power it all the way off upon sucessful flash then power it back on into recovery (hold up volume power home) wipe cache wipe dalvik reboot system. The power off is absolutely crucial and the most common flash error. If this doesnt work repost shouldnt be too hard to fix things is damn near unbrickable

If you change from 6.0 to old 5.1.1 firmware with Odin it will go into bootloop. You must do factory reset, than use Odin to flash 5.1.1 and than do another factory reset.