Related
Hi everyone I'n not technically new here, I have used this forum for anything android related from my first android phone, However I have never posted here so bare with me please if it is in the wrong section.
So my story is this, I have had another galaxy s3 before this one which i hard brick because a rom on another website was listed wrong and i installed the international version. After receive my new S3 from Verizon i learned very quickly that I couldn't live without root. So i followed the newest guide to rooting. After I followed the guide completely I ended up with a rooted phone that has No Lockscreen. What i mean by that is when i press the power button to turn the screen off and when it is turned back on it goes straight to the home screen. Even alternatives like (Holo locker and Go Locker) don't work. Also when the phone is factory rest it doesn't bring me to the welcome screen where I'm suppose to set up a new phone with my username and password. The final problem is that it is always in Factory Mode. I have followed guides that require you to run some SU terminal commands and they have not work. Everytime a boot my phone it is still in factory mode.
I have googled endlessly for a solution and found nothing. Can you please help me?
-Mike
For Tab 2 P3100:
I'm a stranger to flashing Android ROMs, and it's hardly a surprise that after 2 hours of struggling with my rooting and then flashing, Cyanogenmod gets stuck on the blue-circles load screen.
Cause of the problem would likely be that I unknowingly flashed in the newest nightly release, which was unstable. All stock roms I've encountered either don't allow me to load it from Odin because it's not a .md5, or it takes hours to download (and the server likely cuts me off before I'm done).
I've been roaming these boards (and others) for a long while, but there's been no easy way to unscrew the Cyanogenmod up without those stock roms that have to be downloaded from failing servers with terrible download rates and cut me off. Any help on how to easily recover it with any working ROM in any way (even if it unroots the device) would be appreciated. (Got to lower my standards by now!)
Alternatively, are there any custom ROMs out there that flash straight from Odin instead of from ROM Manager (I don't know how to make Cyanogenmod flash from Odin)? With the OS stuck in boot I obviously can't open ROM Manager app to flash a new one...
Side note: Clockwork Recovery is definitely on my Tab, but using Vol.Up and Power buttons won't conjure it (although Vol.Down and Power does conjure my Odin). Therefore my plight.
icehawk_1995 said:
For Tab 2 P3100:
Side note: Clockwork Recovery is definitely on my Tab, but using Vol.Up and Power buttons won't conjure it (although Vol.Down and Power does conjure my Odin). Therefore my plight.[/I]
Click to expand...
Click to collapse
Make sure you hold the Power and vol + until you see the Samsung Tab2 and then keep holding the vol+ a little longer till Recovery starts to load.
Here is a good video on installing CM 10.2 with download links in the description area.
https://www.youtube.com/watch?v=uooLuG0Ydr8
Try wiping data from recovery.
You know, it's a sad day when your cellular service is faster than your home broadband.
Hi, thanks for your replies.
I've made some progress, because I could load my default ROM again via Odin, so I can sustainably retry different Cyanogenmod builds.
Sadly, I've tried the latest nightly build, release candidate and stable release, and ALL of them have gotten stuck during booting (at the cyanogenmod spinning circle).
I have since tried to reformat the device and clear the cache, but that apparently hasn't been working as well.
Regarding the YouTube tutorial video shared above, I tried following the steps exactly, but it appears that my Clockworkmod Recovery mode screen looks quite different from the one in the video, and mine doesn't have some of the options it has. (I did use ROM Manager to automatically download CWM Recovery, not sure what is wrong with that). In any case, I still can't conjure Recovery mode from Vol.Up + Power button--I can only access it by using the ROM Manager app and clicking restart into Recovery.
Is there a similar error to what I'm experiencing? Because so far I still haven't found a thread that has a resolved issue with my device's symptoms.
Thanks for any help again!
Thanks for your help, particularly the YouTube tutorial video link that concisely showed me how the successful install looks like.
Turns out the CWM Recovery that ROM Manager automatically downloaded and flashed for me the first couple of times was an outdated/screwed up one that didn't work properly (ie. couldn't follow every step in the video because some features required in the video's steps were unavailable).
For future reference, if anyone encounters the same problem I did, it's something wrong with the Clockworkmod Recovery version, no doubt. For some reason, one fine instance like any other, ROM Manager finally got it right and installed the right version of CWM Recovery and I can now access all the features, and pressing Vol.Up + Power does conjure the Recovery Mode now.
Thanks for helping me fix my tablet, guys. I kinda absolutely hate TouchWiz UI and Cyanogenmod is indeed miles ahead. Happily running the latest nightly build of 10.2, loving it.
Cyanegonmod stuck
I cant reboot system , I have tried everything but wipe data/system restore. everytime it goes back to same screen. Now I am getting error messages while back and restoring image of data. I my be just not familiar but it shows my recovery files dated back to 2000 and 2010. How could the date change.
I'm really stupid.
I started when I flashed Cyanogenmod from 10.1 to 10.2 and started getting random resets. After getting impatient, I stupidly tried to downgrade back to 10.1 without a factory reset which caused the bootlooping. Then I tried going going into recovery mode and tried to restore with cwm recovery but my phone just randomly shutdown.
tl;dr Now I can't enter into recovery mode at all (I can see the blue words then it shuts off), can enter download mode for maybe 4-6 sec before it shuts off, and my phone still bootloops if I try to properly turn it on.
Can anyone help me?
john2166 said:
I'm really stupid.
I started when I flashed Cyanogenmod from 10.1 to 10.2 and started getting random resets. After getting impatient, I stupidly tried to downgrade back to 10.1 without a factory reset which caused the bootlooping. Then I tried going going into recovery mode and tried to restore with cwm recovery but my phone just randomly shutdown.
tl;dr Now I can't enter into recovery mode at all (I can see the blue words then it shuts off), can enter download mode for maybe 4-6 sec before it shuts off, and my phone still bootloops if I try to properly turn it on.
Can anyone help me?
Click to expand...
Click to collapse
take out batter for couple mins .put it back in . pres hold power home vol up .. sometimes takes couple tries to get into recovery mode . factory reset flash rom correct gapps ..first boot sometimes takes couple mins . remember nightlies are betas not all play well
twistedillutions said:
take out batter for couple mins .put it back in . pres hold power home vol up .. sometimes takes couple tries to get into recovery mode . factory reset flash rom correct gapps ..first boot sometimes takes couple mins . remember nightlies are betas not all play well
Click to expand...
Click to collapse
Thanks for trying to help, but it didn't work. Tried it many times, but I did get to the "Samsung Galaxy S III" logo after recovery mode.
Also to clarify, I wasn't a nightly it was a stable version of Cyanogen. It's just that your not suppose to directly downgrade a Cyanogenmod without a factory reset or it could cause problems, which I found out later.
Edit: It's getting late so I'm going to check back in the morning. Thanks.
john2166 said:
Thanks for trying to help, but it didn't work. Tried it many times, but I did get to the "Samsung Galaxy S III" logo after recovery mode.
Also to clarify, I wasn't a nightly it was a stable version of Cyanogen. It's just that your not suppose to directly downgrade a Cyanogenmod without a factory reset or it could cause problems, which I found out later.
Edit: It's getting late so I'm going to check back in the morning. Thanks.
Click to expand...
Click to collapse
You said you could enter download mode and stay there? If so i highly suggest you go and ODIN your phone back to stock re-root, install recovery then go ahead and install CyanogenMod. This most likely ill fix your problems, but only do it if your phone can go into download mode and stay there!
Mtsprite said:
You said you could enter download mode and stay there? If so i highly suggest you go and ODIN your phone back to stock re-root, install recovery then go ahead and install CyanogenMod. This most likely ill fix your problems, but only do it if your phone can go into download mode and stay there!
Click to expand...
Click to collapse
No unfortunately my phone can't stay in download mode. At least not long enough to use odin.
john2166 said:
No unfortunately my phone can't stay in download mode. At least not long enough to use odin.
Click to expand...
Click to collapse
If you remove the battery and put it back in does it auto turn on?
I am curious to see what others here think, but in my limited experience with embedded devices, this is almost sounding like a hardware problem.
The phone was randomly rebooting before -- I don't think it was established earlier that recovery and download modes were solidly working when the conditions started. From your description, the symptoms appear sometime after the CM 10.2 upgrade, but that does not mean the upgrade or downgrade caused this issue.
It sounds odd to me that the phone would go into download mode, and then just sporadically reset. Perhaps others here can comment if this behavior in download mode has been observed with other botched software flashing.
I am just curious, and just verified on my S3. Try the following:
- boot into download mode, but leave the warning screen active. See how long that lasts or if you get reset quickly
- Plug the phone into a power source, boot into download mode, confirm, immediately remove the battery, and let the phone sit to see if it resets.
What I am looking to see is if a steady power supply here helps keeping download mode active; maybe your battery is shot and causing erratic behavior. Also, try to make a careful inspection of the phone, especially if all the screws are tight, the battery compartment doesn't have anything loose or funny looking, power button seems to be snappy and crisp (not mushy or sticking), etc.
Good luck.
ThePagel said:
If you remove the battery and put it back in does it auto turn on?
Click to expand...
Click to collapse
Kind of. It shows the Samsung logo when I put it it in. It only goes into a bootloop if I hold the power button for a few seconds.
vax1170 said:
I am curious to see what others here think, but in my limited experience with embedded devices, this is almost sounding like a hardware problem.
The phone was randomly rebooting before -- I don't think it was established earlier that recovery and download modes were solidly working when the conditions started. From your description, the symptoms appear sometime after the CM 10.2 upgrade, but that does not mean the upgrade or downgrade caused this issue.
It sounds odd to me that the phone would go into download mode, and then just sporadically reset. Perhaps others here can comment if this behavior in download mode has been observed with other botched software flashing.
I am just curious, and just verified on my S3. Try the following:
- boot into download mode, but leave the warning screen active. See how long that lasts or if you get reset quickly
- Plug the phone into a power source, boot into download mode, confirm, immediately remove the battery, and let the phone sit to see if it resets.
What I am looking to see is if a steady power supply here helps keeping download mode active; maybe your battery is shot and causing erratic behavior. Also, try to make a careful inspection of the phone, especially if all the screws are tight, the battery compartment doesn't have anything loose or funny looking, power button seems to be snappy and crisp (not mushy or sticking), etc.
Good luck.
Click to expand...
Click to collapse
Thanks. I've tried what you asked with and without the battery, and the warning screen stays on for about 3-7 secs for both circumstances. I also tried replacing my battery with another one lying in my house. The battery compartment and the power button is seemingly normal.
Doesn't help ... but this other thread sounds a little bit similar to your download mode issue ... http://forum.xda-developers.com/showthread.php?t=2608201
Sounds like you have a very small window of opportunity before the download mode reboots. Maybe try this just to see:
- make sure your windows (assuming) drivers are all set up. Hopefully if you had ODIN working already, then you are set
- get a copy of heimdall command line version
- get the command ready to execute: heimdall print-pit --no-reboot
- In the small window of opportunity you have ... enter download mode, confirm, press enter on heimdall command and see if anything interesting happens
See if you get anything. If you do you might try to quickly use up-arrow on the CMD line to recall that command and run it again. If you know anything about windows batch scripting, you might try scripting the heimdall command above in a loop.
My thought here is that if heimdall cannot initiate anything useful, then your software is probably lost. If heimdall can output the PIT data, could be that download mode software is good, but the hardware is bad. If rapidly executing heimdall keeps your device active longer than usual, that might be an interesting tid-bit to know.
I am no expert here, so please seek other's more expert advice before trying anything. If your boot mode is screwed, perhaps the thread on [GUIDE] Debrick your bricked s3! [BOOTLOADER/HARDBRICK] might work, but again unless someone else confirms this, I would not try that until you are about ready to accept total loss.
My phone didn't charge during the night as it came unplugged somehow and it got thrown into a bootloop which essentially show the LG boot screen and then restarts again and again in the same fashion. 2 seconds of black screen and 9 seconds of LG screen then bam, restart over. I have booted into the factory reset screen and when I click yes twice, it just reboots right back into the loop. So what I am hoping I can do is flash the rom to an older firmware perhaps. I am not sure what is going on with it, but I can't afford to replace it and I have no warranty.
The issue I am having is I do not see an up-to-date current guide on how to go about flashing to stock rom for the LG stylo H631. The last tutorial I could find was a video from march and that was in a different language so no dice. I have found guides all over the internet from various periods of times that all point in different directions. Some say use LG flashtoolkit. Some say use LGbridge, some say LGup works. None of these are detecting my phone due to it being a bootloop and can't make it into the actual phone. I know how to get to download mode on my phone, but what to use to get the firmware and flash the phone to stock, I do not have a clue.
The last firmware I remembering it having was Lollipop. So overwhelmed with this and lost. Can someone please point me in the right direction on some kind of up-to-date guide with what current software to use and what to do. Thank you as it's much appreciated sooooo much!
UPDATE: Well I just found out that I can get into the downlod mode screen where it says press and hold volume up to continue to download screen, but it doesn't get to the download screen, instead it just goes to reboot back into the same loop from hell. Any ideas guys? From all the research I have done all night, it looks like it could possibly be a battery issue also doesn't help that I know that the battery did completely drain. It seems like buying a new battery may be an answer? Still confused and overwhelmed..
Hi,
Apologies if this has been asked before, but I've done a relatively thorough search and I can't find a solution to this problem.
I have an S6 (SM-G920F), It was playing up for a few weeks before this, not charging well, and what not, thought it was a cable/hardware issue. Then it stopped working entirely. Initially when it was plugged into the wall it would say it was 91% charged, but if you tried to turn it on it would turn off, and reboot into the charging screen.
I've done quite alot of reading and I've ended up flashing it with Odin (I have a single .md5 file, which i've loaded onto the phone via AP) using the most recent FIrmware UK EE for the SM-G20F. This was successful, however now it only loads the Black screen with white text Samsung S6 powered by android screen and then goes blank and back to the white text screen.
I downloaded an alternative firmware (the one previous version), but this has had the same effect. I've tried to repartition with odin, but this fails.
1.) Is there anyway I can fix this?
2.) If not Is there anyway to remove files whilst in downlod mode?
3.) If I cannot fix it or recover my data, is there anyway to wipe the data securely from my phone so I can sell it for parts?
At present, I can't access recovery mode, only download mode. But whilst Odin communicates with the phone in download mode, I can't seem to access my files from explorer?
1. I would say you'd have to clear cache, immediately after flashing the firmware with Odin, but to do that, you'd have to get to Recovery Mode first...
Why can't you get to it? Does it just start trying to boot nornally? Because if so, it's just a matter of timing it. What I do is... hold power+home+voldown to get to the screen that asks me if I want to get into Download Mode, I press cancel, and immediately start holding power+home+volup until I see the bootsplash screen, and release the power button but keep holding home+volup, and it gets me to Recovery every time, even when I have difficulties such as this.
2. Not that I'm aware of. BUT you could flash TWRP with Odin, and if you then can manage to get to Recovery, you just need to plug your phone into a computer, and your phone will show up in the computer as a device/disk and you can freely remove stuff from it.
If... IF this were to work, I would suggest downloading a stock-based ROM and flashing it. It's far more likely to work properly and bootup without issue than the firmwares you can get, and it's far less much of a headache to do.
3. Nope. There are apps that can wipe data securely (such as Shreddit which does it according to military standards), but it can't be done from Download Mode. There may be some script that could do it in Recovery Mode, but I doubt it.
I mean... technically... you could flash TWRP, go to Recovery, move to your PC all the stuff you want to keep, select the wipe option in TWRP and then transfer randomly generated data from your PC to your phone until it's full - there are many apps that can generate such data. It's not something you could pass off as very very secure, but it should suffice.
I seem to always keep going to trying TWRP - so, you know, give it a shot.
King-V said:
1. I would say you'd have to clear cache, immediately after flashing the firmware with Odin, but to do that, you'd have to get to Recovery Mode first...
Why can't you get to it? Does it just start trying to boot nornally? Because if so, it's just a matter of timing it. What I do is... hold power+home+voldown to get to the screen that asks me if I want to get into Download Mode, I press cancel, and immediately start holding power+home+volup until I see the bootsplash screen, and release the power button but keep holding home+volup, and it gets me to Recovery every time, even when I have difficulties such as this.
2. Not that I'm aware of. BUT you could flash TWRP with Odin, and if you then can manage to get to Recovery, you just need to plug your phone into a computer, and your phone will show up in the computer as a device/disk and you can freely remove stuff from it.
If... IF this were to work, I would suggest downloading a stock-based ROM and flashing it. It's far more likely to work properly and bootup without issue than the firmwares you can get, and it's far less much of a headache to do.
3. Nope. There are apps that can wipe data securely (such as Shreddit which does it according to military standards), but it can't be done from Download Mode. There may be some script that could do it in Recovery Mode, but I doubt it.
I mean... technically... you could flash TWRP, go to Recovery, move to your PC all the stuff you want to keep, select the wipe option in TWRP and then transfer randomly generated data from your PC to your phone until it's full - there are many apps that can generate such data. It's not something you could pass off as very very secure, but it should suffice.
I seem to always keep going to trying TWRP - so, you know, give it a shot.
Click to expand...
Click to collapse
Thanks for your reply! So after flashing it goes straight back into the boot loop. Weirdly if its plugged into my laptop it spend about a second or two on the "Samsung Galaxy S6: Powered by Android" screen before plunging into darkness and shortly after repeating the same message. However if I plug it into the wall it spend over twice as long on that screen before repeating the cycle. It never goes any further.
I've tried your suggestion about perhaps its timing for recovery mode, but even if I go straight from cancelling download mode to trying the power, up and home key it doesn't go to recovery. I've tried a variety of timings both plugged into my laptop and plugged into the wall to no avail. If the phone isn't plugged in, it literally won't do anything whatsoever, won't even hint at turning on.
So Next I tried flashing it with TWRP via Odin and nothings changed, exactly the same bootloop and I still can't get into recovery mode.
I'm starting to think that sadly this phone my be beyond repair! Thanks for your help though, much appreciated.
Hi! I usually run out of my bootloops like this:
try this:
1: go to download mode, and press Power + home + volume —
2: As soon as the screen turns black, continue pressing Power and home, quickly release "volume —" and press "volume +". This will get you into recovery mode.
It always worked for me, so I wish the same for you. Good luck! (And sorry for my bad english)
vinicius_guerra said:
Hi! I usually run out of my bootloops like this:
try this:
1: go to download mode, and press Power + home + volume —
2: As soon as the screen turns black, continue pressing Power and home, quickly release "volume —" and press "volume +". This will get you into recovery mode.
It always worked for me, so I wish the same for you. Good luck! (And sorry for my bad english)
Click to expand...
Click to collapse
Hi Vinicius,
Thanks for the suggestion. Unfortunately it didn't work, I even tried flashing it back to a standard ROM from TWRP, but it still didn't do anything, just back to the Samsung logo and the loop continues ever more!
Hi, I have this problem as well.
Originally I had TWRP and root flashed into my phone but for reasons I needed to remove root.
So I followed the Odin route stated here "Mobikin how to remove root from android" (I can't post links but this should be the top result when googling)
However I didn't know if the recovery/boot should have went into AP or BL on the Odin menu and googling didn't give me any answers so I may have tried both....
Right now I tried flashing TWRP and I can't seem to boot into TWRP as well.
I was able to get into recovery mode but clearing data/cache didn't fix it for me.
EDIT: I managed to flash in another stock rom and it boots into the SAMSUNG logo but gets stuck there. I already went into recovery mode to delete data and cache partition but it still doesn't boot.
Melioetta Zyguard said:
Hi, I have this problem as well.
Originally I had TWRP and root flashed into my phone but for reasons I needed to remove root.
So I followed the Odin route stated here "Mobikin how to remove root from android" (I can't post links but this should be the top result when googling)
However I didn't know if the recovery/boot should have went into AP or BL on the Odin menu and googling didn't give me any answers so I may have tried both....
Right now I tried flashing TWRP and I can't seem to boot into TWRP as well.
I was able to get into recovery mode but clearing data/cache didn't fix it for me.
EDIT: I managed to flash in another stock rom and it boots into the SAMSUNG logo but gets stuck there. I already went into recovery mode to delete data and cache partition but it still doesn't boot.
Click to expand...
Click to collapse
Same experience. For all those 6 years that I used this device, the wifi was okay until now. It (wifi) is very buggy (turning on and off, and sometimes won't turn on at all) so I restarted the device, then bootloop happens. I flashed the stock rom via odin and clear data and cache. But it is still bootlooping. I think this is the sign that I need to replace my phone IF I couldn't find a fix to this.