I changed overclock settings on my player 4.0 now its stuck in a boot loop. I am not sure how to undo the settings because it wont boot. I reflashed Steves custom rom and kernel but nothing happened. What do I do????
coley909 said:
I changed overclock settings on my player 4.0 now its stuck in a boot loop. I am not sure how to undo the settings because it wont boot. I reflashed Steves custom rom and kernel but nothing happened. What do I do????
Click to expand...
Click to collapse
Explain what you did exactly. "Changed overlock settings" is a bit too vague.
Ok it wasn't a set over clock it was where you could adjust voltage and change the overclock to 2.0 ghz which I didn't do but I did change it to 1.5 with setting the voltage correctly
It was in the tegrak overclock app I accidently hit apply.is there a reset like back when I was oc computers you viukd just pull the cmos battery but I doubt there is something similar
Sorry I keep remembering things I forgot to mention. Its stuck in a boot loop on the Samsung screen
Enter stock recovery and "wipe data/factory reset"
how do i do that?
I figured out the key combo to get into clock work recovery I wiped everything I could still boot looping though. I don't know how to get into the normal recovery but so far no good.
Anyone? I just need to know what to do starting to panic a tad.
Tried reflash wiped all data odin with back up rom from forum wiped Steve's custom rom everything Idk what to do any suggestions please
Sent from my Incredible 2 using XDA App
I was stuck in a boot loop too. For details see this thread.
The advice I got was to reflash to stock ROM and stock kernel, then go into stock recovery (with 3 button combo) and choose "wipe data/factory reset" and then "wipe cache".
This seemed to get me out of the boot loop. Of course, all my data was wiped too.
Hope this helps.
ill try it but I dont know the 3 button combo is it by chance home volume up and power?
nothing I think it will have to be sent back
update, it was under warrenty at best buy so it was replaced
Related
ok im stuck on my boot logo for my motorola droid 2. its a liberty logo, no the original M logo, ive held in x when it starts up and then it takes me to the triangle and then i hold the search button down and then it takes me to a menu saying this:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
ive already tried just rebooting it and then it does the same thing again and just gets stuck at the boot logo, so please help. thanks!
Have you tried pulling the battery out for about 15 seconds?
See if that clears it up.
with it unplugged and turned off?
Yes Sir. Unlug it and turn it off.
yes i just did that and it didnt work, its still at the boot logo, the only thing i can do is go to that recovery menu that i said about in my 1st post, but idk what to do when i get there?
Try wipe data/factory reset.
Obviously you're gonna have to tweak your settings again.
okay, is there anyway i can get my settings back like a recovery? or something
Well, you might want to head in to the Droid 2 forums to get better responses related to your phone.
Here is a link to start with.
As far as recovery goes, I don't think you have a custom recovery installed. Sounds like you have a stock phone. So, there's no way of backing your stuff up.
i have it rooted and a rom on it but nothing custom, but thanks for all your help
Zimm814 said:
i have it rooted and a rom on it but nothing custom, but thanks for all your help
Click to expand...
Click to collapse
If you have it rooted, did you ever perform a Nandroid backup ?
Do you have a non standard recovery installed?
EDIT: Sorry re-read last few post and come to conclusion that you probably don't.
sorry but doesnt rds lite 4.8 and the correct sbf file let u flash back to stock?
If your phone is rooted then you have changed your kernal.It might be a fault with the kernal.I had a similar thing happen in an SGS.It was rooted and when i flashed the kernal againh via CWM it also got stuck on the same as you.The only way to solve it was boot to download mode and flash via odin again.
As the thread title states...I was on 7.1 and downloaded/updated it to 7.2 Now the phone doesn't boot up and all I get is the Kernel Panic Upload Mode.
Anyway I can fix this? And if so, is there a way of doing it without completely formatting my phone and losing all my apps?
Oh and if it makes any difference I had to install that Siyah Kernel or whatever it was called to get out of the bootloop issue that I had with CM7.1. I'm thinking that that may be causing the problem....? But then again what do I know
wipe cache only.
valentinrascu said:
wipe cache only.
Click to expand...
Click to collapse
How? I've been trying [Power+Volume Up+Home] and it hasn't been doing anything. Can I do it through download mode somehow?
Had this problem when i flashed Lite'ning rom. Had to go into download and flash stock with odin. Took me a few tries to actually get the rom to work. As far as I know, that'd be your only option, seeing as recovery doesn't work for you.
take a deep breath and read, there is a very small chance of bricking your phone just so you know. Flash back original with Odin and start everything again
thanks for the replies...looks like i'm gonna flash the stock firmware back and see what i can do about getting to CM7.2 to work. hopefully flashing stock firmware is enough. I can't imagine how this would completely brick my phone and render it unusable.
As an aside...wtf is the point of this "recovery mode" when the thing doesn't even work half the time?
Anywho...downloading the stock .exe file now from here: http://devsrom4android.blogspot.ca/2011/10/samsung-galaxy-s2-firmwares-bell-canada.html[/url
Ok so I flashed the stock rom and now I'm in Android system recovery: Should I just reboot system now or do I wipe data/factory reset or wipe cache partition??
nubreed000 said:
Ok so I flashed the stock rom and now I'm in Android system recovery: Should I just reboot system now or do I wipe data/factory reset or wipe cache partition??
Click to expand...
Click to collapse
If you flashed stock, you should be fine just rebooting.
Its stuck on the boot screen. I tried just rebooting, then wiping/factory reset, then both wipes...reinstalled stock a few times and nothing worked each time. I'm suck on the Samsung Galaxy SII GT-I9100 screen
:-\...when I go into recovery, I get a ton of red messages/errors
I'm gonna try somethig other than stock firmware see if that helps.
edit Ok so I rooted the phone and it got past the first boot screen and now appears to be stuck on the "animated S" boot screen...progress!!
nubreed000 said:
thanks for the replies...looks like i'm gonna flash the stock firmware back and see what i can do about getting to CM7.2 to work. hopefully flashing stock firmware is enough. I can't imagine how this would completely brick my phone and render it unusable.
As an aside...wtf is the point of this "recovery mode" when the thing doesn't even work half the time?
Anywho...downloading the stock .exe file now from here: http://devsrom4android.blogspot.ca/...msung and their changes to Android framework.
Click to expand...
Click to collapse
Ok everything back to somewhat normal. Stock ROM didn't work but 2.3.6 did, so I'm on that. Now do I wanna go back to CM is the question...
Either way, thanks again for all the replies and helping me out with this. Greatly appreciated!
I recently got a galaxy player 5 international with froyo. I rooted it with no problems, but when I tried to flash a kernel with cwm recovery it would get stuck in a boot loop unless i went into the cwm recovery mode. I noticed that the kernel I used, rumirand's r14, was based off of GB and thought that might be my problem. I tried updating my firmware to GB using WT Ho's custom rom, and now it just hangs on the samsung logo, but I can still get into cwm. I made sure to wipe both caches and wipe data before installing the rom. Is this fixable or have I turned it into an expensive paperweight?
Did you try a factory reset?
I am not expert but i tried the same with R14 kernel and bricked but done the same with R13 and it worked .
Chris4evernoob said:
Did you try a factory reset?
Click to expand...
Click to collapse
Now or before installing the rom? I did a factory reset before installing, but I haven't done one since.
DZonikg said:
I am not expert but i tried the same with R14 kernel and bricked but done the same with R13 and it worked .
Click to expand...
Click to collapse
I just flashed the R13 kernel, but I'm still in the same situation.
Instead of flashing a new kernel there should be factory reset option on the first set you have or in "mounts and storage"
I had this problem once and I managed to solve it flashing a full rom (like 2.3.5 rooted and with rj kernel). It seems some users are having problems when flashing only the kernel. After you solve the problem, flash back group rom.
I just tried the rom+kernel. It said it was successful but it must not have been because it was hanging on boot again, and now it won't respond to the power button. If I plug it in to the computer it gets an image of a battery turns off and repeats.
jnmaster said:
I just tried the rom+kernel. It said it was successful but it must not have been because it was hanging on boot again, and now it won't respond to the power button. If I plug it in to the computer it gets an image of a battery turns off and repeats.
Click to expand...
Click to collapse
Can you go back to CWM after flashing rom+kernel? If yes, usually it is a matter of wiping the data and Dalvik cache. Which ROM+Kernel did you flashed?
WT Ho said:
Can you go back to CWM after flashing rom+kernel? If yes, usually it is a matter of wiping the data and Dalvik cache. Which ROM+Kernel did you flashed?
Click to expand...
Click to collapse
No, I'm not able to get a response from the power button.
I used the ROM + kernel you posted http://forum.xda-developers.com/showthread.php?t=1446774
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
nathan101 said:
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
Click to expand...
Click to collapse
Your phone is not bricked. When the phone is stuck on the droid eye, hold the power button and the volume down key at the same time until it reboots. This will get you into bootloader mode. Press the volume down key to highlight recovery and press the power button to enter it. Once you're in recovery go ahead and restore a backup or reflash something new. Either way make sure to do a full wipe.
Sent from my HTC6435LVW using xda app-developers app
klarson said:
Your phone is not bricked. When the phone is stuck on the droid eye, hold the power button and the volume down key at the same time until it reboots. This will get you into bootloader mode. Press the volume down key to highlight recovery and press the power button to enter it. Once you're in recovery go ahead and restore a backup or reflash something new. Either way make sure to do a full wipe.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
thats what i did i restored my backup and this is what happens. and i cannot push any files over to the phone because usb debugging is not enabled so there is no communication between the phone and computer at all
boot into recovery then use "adb push <path to rom> /mnt/sdcard/" to put a rom on the sd then install. Make sure you use a boot.img that came with the rom if it has one as it may cause problems if you don't.
Edit: you will need another rom for this and I would recommend reflashing a boot.img
Jmlannan said:
boot into recovery then use "adb push <path to rom> /mnt/sdcard/" to put a rom on the sd then install. Make sure you use a boot.img that came with the rom if it has one as it may cause problems if you don't.
Edit: you will need another rom for this and I would recommend reflashing a boot.img
Click to expand...
Click to collapse
the problem im having is the phone is not being recongnized by the adb so there for i can not push anything to the phone.i have no communication with the phone at all so i cant push any files at all.im looking for a way around this
nathan101 said:
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
Click to expand...
Click to collapse
USB debugging has nothing to do with ADB in recovery, recovery basically has its own kernel and ADB is always enabled. Are you saying ADB doesn't work in recovery? If so, it is probably a driver problem with your computer. Also, some phones randomly get corrupt /data/ partitions (mine used to get them until I started using DSB's stock kernel with system write) and the only way to fix it is to do a factory reset or restore a backup. This might be what happened to you. If so just do a factory restore and see if it will boot.
Perhaps reflashing recovery? Worth a try if ur still having problems, also try installing then uninstalling htcs sync app.
nathan101 said:
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
Click to expand...
Click to collapse
Try restoring back to stock with the Droid DNA RUU, i had issues with it locking up and freezing and i couldnt do a thing with it. i stumbled on the RUU and followed the instructions and re-stocked it. then just root and flash again. worked for me and im now running the Battery Plus ROM and have no issues yet. good luck
Just be sure to re lock before you flash the ruu
Sent from my HTC6435LVW using xda premium
Howdy partners, not sure if I should have started my own thread...let me know if that is proper procedure please. I've already read the recent boot loop thread by vlmaadir t=2558286, but I'm unsure as to the applicability of the solutions in that thread to my problem.
I'm in a similar situation as the vlmaadir, except I've been running the most recent stock ROM (UCMD8) and have rooted via framaroot and flashed the AJKv4.9 - NoSwap Kernal successfully around 12/5/2013. Of course I've yet to do a backup of the OS or apps, but pics/vids/contacts were all recently backed up.
About two weeks ago I started noticing random reboots, but wasn't really sure what to make of that, never any boot looping though. Well this morning the phone was working when i woke (phone alarm raised me from the dead on time) and had approx. 70% battery, but by the time I got to work, the phone had apparently powered off.
When I powered it back on, it took a several minutes to boot up (normally around 45sec-1min), once booted the battery showed about 10-15% (in the red). The few apps I opened worked (naked browser, outlook), but were a bit laggy. I decided to restart the phone from the regular power menu to see if that would help the laggy/battery issue, and upon restart I am now solidly stuck in my 1st android boot loop!!!
I can boot into CWM recovery, but have yet to do any wiping as I wanted to seek a bit of advice here 1st.
If anyone has any pointers, I'm listening.
Thanks!
I would 1st try a wipe cache and wipe dalvik cache from cwm recovery and see if it will reboot.
If it doesn't then u will probably have to wipe data/factory reset from cwm recovery and then reboot.
If ya have been runnin good for a while with AJ's kernel, then a rogue app may be the cause of ur problem.
R u tweakin anything in the kernel through stweaks apk ?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
4-2ndtwin said:
I would 1st try a wipe cache and wipe dalvik cache from cwm recovery and see if it will reboot.
If it doesn't then u will probably have to wipe data/factory reset from cwm recovery and then reboot.
If ya have been runnin good for a while with AJ's kernel, then a rogue app may be the cause of ur problem.
R u tweakin anything in the kernel through stweaks apk ?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Thanks 4-2.
If I have to go wipe data/factory reset, should i have to re-flash the rom and kernel?
I've been running the AJK for about a month, no tweaks. Like I said in the OP, I had noticed some random reboots in the past few weeks and at some point over Christmas day, when I was doing a good bit of pic/video work on my phone, it came up with a message that the internal storage memory was low. I knew this wasn't the case, at least as far as the entire internal memory, which had around 3 gigs free. Just a few strange things I've noticed since having AJK in place.
Are there any other good kernels for stock 4.1.2? AJK seemed to be the go-to of main stock and custom ROM folks.
I did a cache wipe, but when I enter the dalvik wipe confirm menu, the output shows
E:unknown volume for path [/sd-ext]
and when I confirm yes, wipe dalvik, the screen goes black, then the phone restarts into the boot loop.
Any one know what is up here?
^^
Doing and wipe data/factory reset in the cwm recovery will just return the Stock MD8 to just full stock, as if u first installed it through Odin or att official, Except u will still have the AJ kernel. There is no need to reflash the rom as u say.
But if u cannot find an app that is causing the problem, then a complete Odin flash to Stock MD8 should help in the troubleshooting.
---------- Post added at 07:40 PM ---------- Previous post was at 07:37 PM ----------
wolfboogie said:
I did a cache wipe, but when I enter the dalvik wipe confirm menu, the output shows
E:unknown volume for path [/sd-ext]
and when I confirm yes, wipe dalvik, the screen goes black, then the phone restarts into the boot loop.
Any one know what is up here?
Click to expand...
Click to collapse
The "E:unknown volume for path [/sd-ext]" is the norm from what i remember.
But not sure why choosing to wipe dalvik cache resulted in a bootloop.
Have ya tried the wipe data/factory reset yet ?
Just did a wipe data/factory reset and I got out of the boot loop! Now I just have to set the phone up like I had it once again! Boo!
Thanks for the input 4-2!!!
Glad ya got it going. :good:
If any other problems arise, just let us know. There are several good members around that are glad to help.