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.
Related
Hi,
I rooted my DHD today and tried to flash the CyanogenMod-7 for Desire HD & Inspire. It seemed to work but now keeps re-booting every couple of seconds. It won't actually stay on long enough to put another ROM on. Can anyone help? This is the first time I've done something like this and it seemed to be going so well!
Thanks!
Pull the battery for about 10 seconds. Then hold the vol- button down and power your device on. Now you should see a white screen with some text on it. Navigate to recovery and press the power button. Now it should boot into recovery.
In the recovery choose wipe data/factory reset ald let it finish. Once its finished choose wipe cache partition.
Then go to install .zip from sd and then choose zip from sd. Now search for your rom and reinstall it
Tapatalked with Tapatalk from my Desire HD using Tapatalk.
This is common. Simply wait for it to boot and power off or use the power button to select reboot. You only have to do it once.
The instructions for installing CM7 all say to install ROM then reboot after first complete start up. Shouldn't need to reinstall anything.
Having been left alone for a few hours it seems to have sorted itself out. Thanks! I just wasn't expecting it to spend quite so long re-booting.
I guess you have enabled wi-fi just after flash cm7. Seems like there is a bug or whatever, all you need is re-boot device after first boot.
And about the re-boot loop, just remove battery to turn off you device then turn it on, enter recovery and flash cm7 again WITHOUT do wipe operation. OK, In this time remember to re-boot after first boot.
I got a bit trigger happy and tried to flash Android Revolution HD 3.3. I did a full wipe from ClockworkMod Recovery and tried to install the zip, exactly like I did for the previous ROM. That kept aborting the installation so I mounted the phone and re-downloaded and copied it onto the SD card again. Same problem. I then tried to re-install cm7 and that also kept aborting.
I now have the message "Back menu button disabled" and if I use the power button to select anything it goes straight to a white triangle with an explanation and the Droid, which I think is stock recovery? I'm getting there from what I think is Clockwork though. Is this recoverable or have I managed to brick it?
I had a similar issue a few days ago - it turned out that the battery stats were screwed up so a fix for me was to boot into recovery and then wiping the battery stats.
Everything was fine after that.
How do I do that? I don't want to reboot out of Clockwork as I'm not 100% sure I actually have a ROM at the moment.
Can boot into menu. Highlight recovery. Press power button. Powers down, not completely though. Screen stays on slightly. When waiting 5 minutes and press power button boots into loop again.
mdaigt said:
Can boot into menu. Highlight recovery. Press power button. Powers down, not completely though. Screen stays on slightly. When waiting 5 minutes and press power button boots into loop again.
Click to expand...
Click to collapse
open recovery, goto advanced and wipe battery stats
Going to leave battery out for the night as read in other posts. Fixes the problem of not totally shutting down for some. Thanks.
Well leaving battery out didn't help. Continuous boot loop. Put on charger after turning off orange light came on and didn't go to green after 10 hours. Restarted when I got home and boot loop again. Had CoreDroid ROM installed. Working fine than tried to load Kalagas Mixed Theme and that is where I am now. Looping.
Even a blind squirrel will find a nut now and then. During HTC Hboot menu, noticed it was looking for PD98IMG zip. So I shut phone down. Inserted card with it on it and it restored to original firmware. PHEW. Hope this might help someone else.
Oh my I think i screwed my phone up
I tried flashing ZenSeries 6.42 kernal (wipe cache and davlik) and everything seemed fine. Went to boot up and i get passed the splash screen, but the phones stays stuck on with the google nexus logo and never boots to my lock screen. I tried taking out the battery and going into recovery but it's a no go. I press volume down and power and i go into "odin mode" and it's telling me it's "downloading" then if I hit the power button it takes me back to boot loop. I've been away from the scene due to new marriage, school and work so I'm not sure if i lost touch and forgot how to use my phone like a hacker should anyone know how i can fix this?
cyaiphone said:
Oh my I think i screwed my phone up
I tried flashing ZenSeries 6.42 kernal (wipe cache and davlik) and everything seemed fine. Went to boot up and i get passed the splash screen, but the phones stays stuck on with the google nexus logo and never boots to my lock screen. I tried taking out the battery and going into recovery but it's a no go. I press volume down and power and i go into "odin mode" and it's telling me it's "downloading" then if I hit the power button it takes me back to boot loop. I've been away from the scene due to new marriage, school and work so I'm not sure if i lost touch and forgot how to use my phone like a hacker should anyone know how i can fix this?
Click to expand...
Click to collapse
Volume Up & down + power to boot into the bootloader & then use the volume keys to change "start" to "recovery"
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.
I've got a sprint GS3 that is rooted and has the clockwork recovery mod on it, but was otherwise running stock OS. It had been acting up, hanging, that kind of thing so I decided to go ahead and accept the download new software prompt I've had for the last year or so. When it went to the bootimage(?) menu it asked if I wanted to install this untrusted image. That gave me pause, so I selected no. The little android icon got a red X-ish thing on it's chest and it rebooted. And sat at the samsung galaxy s3 screen for about a half an hour. I pulled the power and it kept going between hanging at that screen, or hanging at random points (app 6, 8, 9, 11) of an "upgrading android" screen I have never seen before. I tried going into the recovery mode but when I follow the instructions (up vol, home and power, when it vibrates for power release the power button) but that doesn't work at all. It just sits there. I'm 100% certain it's not a button/physical issue. I decided to try the download option and can get to a screen that warns me about custom rom. I've tried both installing (let it go for over an hour, gave up) and hitting cancel, to no avail. Before I take this as a sign from the android gods that it's time to go get a GS5, does anyone have any ideas/advice? TIA.
Wrong section.. Report it yourself and adj a mod to move it to correct section..
Sent from my GT-I9300 using xda app-developers app
Have you tried to plug the phone in with the USB cable into the computer?
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.