I have a bit of a problem. I am on a moto g sold in the UK with Vodafone. I followed all the steps posted by root junkie on his youtube video in an attempt to install cyanogen, however cyanogen was taking a long time to load(30 mins without loading). So i went back into cwm to wipe data, this process stalled, so i pressed volume down and power to to go back to fast boot mode.Now when i go to recovery instead of loading into cwm my phone stalls at the white screen which says "warning bootloader unlocked". I have tried reinstalling cwm which seems to install fine, however when i click recovery it goes back to the warning screen. I have also tried reinstalling the stock firmware, however the same problem occurs.
Do you have any suggestions?
Thanks
andy07070 said:
I have a bit of a problem. I am on a moto g sold in the UK with Vodafone. I followed all the steps posted by root junkie on his youtube video in an attempt to install cyanogen, however cyanogen was taking a long time to load(30 mins without loading). So i went back into cwm to wipe data, this process stalled, so i pressed volume down and power to to go back to fast boot mode.Now when i go to recovery instead of loading into cwm my phone stalls at the white screen which says "warning bootloader unlocked". I have tried reinstalling cwm which seems to install fine, however when i click recovery it goes back to the warning screen. I have also tried reinstalling the stock firmware, however the same problem occurs.
Do you have any suggestions?
Thanks
Click to expand...
Click to collapse
I have sorted this now.
How did you solve it, I have the exact same problem except I was reinstalling the stock android.
Related
So ive been running CM 10.1 with CWM v6.0.4.3 for several months without major issue until last night. I went to send a text message to someone, and right as i went back to my home screen, the phone froze, rebooted, and when it finished rebooting, the deice would freeze again as soon as the lock screen was reached, and reboot again. Cue repeated circle of freeze, reboot, finish rebooting, freeze, reboot.
I turned the phone off by taking out the battery, put it back in and charged it overnight without booting it up. Went to start the phone today, same issue still. I would boot into recovery and try to re-flash the OS, and it would give me a status 7 error. After re-downloading everything into my sd card, i was eventually able to get the system to re-install cm10.1.3, and it booted up normally. I downloaded and installed ROM Manager, and installed the newest version of CWM Touch, version 6.0.4.5, and then tried to boot into recovery to install CM11. It showed the CWM Hat icon in the middle of the screen, with the version on the bottom of the screen, then rebooted on its own without showing any menu options.
Now if i try to boot into recovery, it just shows the icon and version again, then reboots, and wont go past the CM loading screen with the spinning cyanogenmod icon.
Not sure what to do at this point, i cant get into recovery to try and flash something new, and i cant get past the CM loading screen to actually use my phone. Any ideas? I have zero experience with adb, so im stumped.
UPDATE: Solved, i flashed TWRP over CWM using Odin, and was from there able to re-install the OS. Things seem to be working fine for the most part, with the exception of one random reboot last night.
Salomon3068 said:
So ive been running CM 10.1 with CWM v6.0.4.3 for several months without major issue until last night. I went to send a text message to someone, and right as i went back to my home screen, the phone froze, rebooted, and when it finished rebooting, the deice would freeze again as soon as the lock screen was reached, and reboot again. Cue repeated circle of freeze, reboot, finish rebooting, freeze, reboot.
I turned the phone off by taking out the battery, put it back in and charged it overnight without booting it up. Went to start the phone today, same issue still. I would boot into recovery and try to re-flash the OS, and it would give me a status 7 error. After re-downloading everything into my sd card, i was eventually able to get the system to re-install cm10.1.3, and it booted up normally. I downloaded and installed ROM Manager, and installed the newest version of CWM Touch, version 6.0.4.5, and then tried to boot into recovery to install CM11. It showed the CWM Hat icon in the middle of the screen, with the version on the bottom of the screen, then rebooted on its own without showing any menu options.
Now if i try to boot into recovery, it just shows the icon and version again, then reboots, and wont go past the CM loading screen with the spinning cyanogenmod icon.
Not sure what to do at this point, i cant get into recovery to try and flash something new, and i cant get past the CM loading screen to actually use my phone. Any ideas? I have zero experience with adb, so im stumped.
Click to expand...
Click to collapse
You can try to reflash CWM with Odin, if that not working, you could try to Odin back to stock.
buhohitr said:
You can try to reflash CWM with Odin, if that not working, you could try to Odin back to stock.
Click to expand...
Click to collapse
I figured it out yesterday actually and forgot to update! Indeed I was able to flash TWRP with odin, since CWM seemed to be blocking me from doing anything. Once that was up and running, things went back to normal, i was able to flash CM 10.2.1 and things seem to be working now.
One thing though, while playing skyrim last night i had it on the charger next to me, and the phone randomly rebooted without any interaction from me. Was odd, but it hasnt done it since. Keeping an eye on it still.
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?
vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
with wugfresh nexus root toolkit click on the button "soft-bricked"(flash stock + unroot) or something like that to restore the phone. After that try another time to unlock and root with a custom recovery (for example twrp).
When nexus root toolkit installing the original lollipop rom, look the "dos window" to see if the software shows errors, because sometimes the process ends without a real restore.
If you have other problems, please post a screenshot.
Fenix46 said:
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?
Click to expand...
Click to collapse
Yes I was using a custom rom, but I not even reached the step where a was supposed to use the rom, I was steel still cleaning the divece.
Here is a photo from the screen I'm stuck in:
eeee.... I'll find a wint to send the photo to this forum ^^" wait
Hello Everyone,
I have been trying to help my friend with his soft-bricked G3. He wasn't rooted and had never even played with flashing anything, it just stopped booting one day and would display the "LG Life's Good" boot screen for a few seconds before going black and then just repeating this endlessly. I was able to get into recovery and download mode so I used the tot method to flash back to stock after a hard reset just produced the same results.
When I flashed the stock firmware, everything appeared to work fine, it went through the MiniOS bootup and everything, said success, gave me the hard reset status screen so when it finished I pulled the battery as instructed and rebooted but the phone still has the same issue. I have tried to run factory reset through recovery now that I flashed the new firmware and it still does the same thing, just hangs at the boot screen for a few seconds before going black and then trying again, endlessly.
Has anyone encountered this before? Is it bricked?
Thanks.
The_mamba said:
Hello Everyone,
I have been trying to help my friend with his soft-bricked G3. He wasn't rooted and had never even played with flashing anything, it just stopped booting one day and would display the "LG Life's Good" boot screen for a few seconds before going black and then just repeating this endlessly. I was able to get into recovery and download mode so I used the tot method to flash back to stock after a hard reset just produced the same results.
When I flashed the stock firmware, everything appeared to work fine, it went through the MiniOS bootup and everything, said success, gave me the hard reset status screen so when it finished I pulled the battery as instructed and rebooted but the phone still has the same issue. I have tried to run factory reset through recovery now that I flashed the new firmware and it still does the same thing, just hangs at the boot screen for a few seconds before going black and then trying again, endlessly.
Has anyone encountered this before? Is it bricked?
Thanks.
Click to expand...
Click to collapse
Pretty common prob plug it in to the wall charge see if it boots sometimes it still wont but most of the time it will the battery quality on the g3 is crap they last at most a year with a few exceptions i would first order a battery.
Hey guys,
Sorry if the answer to this found somewhere else, tried searching but foud nothing for my situation.
My buddy, who is a super basic user and was not attempting to do anything with his phone, has a G4 that suddenly stopped working and went into a boot loop.
We tried factory resetting it and it got about half way through the apps before stopping, going back into a boot loop and was unable to get back to the same point in the factory reset.
I tried flashing the ROM using LGUP to H811-20o and it said that it went successfully on LGUP as well as the phone itself, but after it rebooted it went back into a boot loop.
Now the boot loop goes faster but is still looping and we cannot get back into download mode to try again or potentially try a different ROM. It goes to the first screen of download mode with the 5 blue dots but doesn't get past that, I've removed the battery waited for a while in between attempts and still nothing.
We can get to the factory reset screen and click yes, it will then go to the green android guy with his cog wheels exposed but then immediately goes back into a boot loop.
Any help is appreciated, even if its just a confirmation of being SOL.
Hi
a helpful thread may be found here
https://forum.xda-developers.com/tmobile-g4/general/lg-g4-h811-complete-unbrick-guide-100-t3461629
Ok I will admit it, I screwed up royally this time. My SM-N9150 (Hong Kong version) was slowing down and draining the battery fast. I could not get the downloader of a new stock ROM to work in Sammobile (tried multiple times, with adblock off but no go) and so I bit the bullet and used Kies to upgrade to Marshmallow. Of course this lost root but I figured I could just re-root (I had rooted using Odin with my old phone, but this one I had rooted using KingoRoot). However, none of the 1-click systems like KingoRoot worked, and neither did Chainfire via Odin (which caused problems on its own). So I flashed the latest CWM via ODIN. It said pass, so I went into recovery, did a backup, then did factory reset, installed SuperSu, wiped the caches and rebooted.
I kept getting weird errors where it would not let me boot into recovery or boot at all. so I thought that maybe CWM was not a good choice. I tried the newest version of TWRP but that gave me the "recovery is not seandroid enforcing" error. So I went back the CWM and tried wiping again.
After a very long Samsung logo bootloop, it eventually showed gearings turning but with instructions in Chinese. It then showed the logo again for long time and then showed something that had only 1 English word "system" and the rest in Chinese. There seemed to be 2 choices at the bottom of the dialog box. When I chose the one of the right, the phone showed a grey progress bar with Chinese letters above, but then went back into a bootloop; when I chose the one on the left, the phone turned off for a long time then restarted but again seems to be stuck at the Samsung logo screen before returning to the message with the word "system".
After it going into a bootloop that lasted over 1 hour, I pulled the battery and then went into recovery and tried restoring the backup I had made at the start. That just left me in the endless Samsung logo bootloop. I left it plugged in overnight hoping it would do something but nada. At one pint I did get a message "unfortunately, the system UI has stopped working" but screen was unresponsive to press OK, and it just went back into the bootloop.
I realize I did not do anything to unlock the bootloader. Would using KIES have locked the bootloader again? Could this be my problem, and if so, how do I fix it?