[q] stock unrooted bootloop?? - Moto G Q&A, Help & Troubleshooting

i dont use this forum as i have a different phone and i dont particularly want to sift through every thread to find an answer so i thought id ask to find out for myself
my partner owns a stock unrooted totally unmolestered original moto g running android lollipop and earlier today it started to lag and flashed up with an error she didnt have time to read, not long after it completely froze so i tried to turn it off and on again. after trying to turn it on again it has gone in to a bootloop and will not start properly.
any help on a solution would be much appreciated if anyone can help me ASAP.
cheers

Boot to recovery and try wiping cache. If that doesn't work, you may have to do a full wipe which means losing all files on the phone.

audit13 said:
Boot to recovery and try wiping cache. If that doesn't work, you may have to do a full wipe which means losing all files on the phone.
Click to expand...
Click to collapse
any guides on how to wipe the cache without rooting it? im assuming id have to use fastboot or adb or whatever but the internet hasnt exactly helped me with any solutions

Just wipe by booting into stock recovery.
http://www.android.gs/enter-recovery-mode-motorola-moto-g/

Related

[Q] reboot loop

My g2x keeps rebooting over and over again! This happened after i mounted it to my pc. it tries to read my sd card then just reboots over and over again. I have nv flash and tried to restore old back up but still does it. can any one help im thinking i need to flash stock.
you need to do a factory reset if your nandroid backup doesn't work. if that doesn't work reflash the rom.
I already did a factory reset and wipe and tried to re install the rom. it just continues to reboot. It starts up and if quick i can get into my lock screen and access things but within seconds it reboots and continues to do that
What rom are you using?
jcbofkc said:
What rom are you using?[/QUOTE
I was on a stock rooted rom when the problem happened. so i then i did a restore. when that didnt work i reflashed the stock rom that was posted on forum. i think it has something to do with my internal memory which i cannot access. this all happened when i was trying to back up my sd card while in usb and it just got an error when i unplugged it enless reboot.
Click to expand...
Click to collapse
I was hoping it was something simple like undervolting with a custom rom. I wish I could help. It sounds like you tried everything I would recomend. Maybe one of the real Android techie type guys can help you. I am still learning myself.
jcbofkc said:
I was hoping it was something simple like undervolting with a custom rom. I wish I could help. It sounds like you tried everything I would recomend. Maybe one of the real Android techie type guys can help you. I am still learning myself.
Click to expand...
Click to collapse
Thanks anyway! I even when as far as to re-flash stock recovery and then try to factory reset it but still did not work. I just dont know what the heck happened. So today I went to t-mobile and they r sending me a new phone and for know I have a loaner 10 days until I get the new phone they said it was backordered. oh well

Htc one s bootloop

Hi iv got a HTC ONE S, it is stuck on boot loop is there any way i can get my pictures and data off my phone? thanks
Can you get into the recovery? And are you running a custom recovery?
If you can get into your recovery(cwm or twrp) you can plug it into usb and mount it as usb storage.
If I helped in any way please hit thanks
Just fix the bootloop. Sounds like you gave up on it. Can you get into the bootloader? Hold volume down and power. Till the device shuts off. Then redo that method and poof. Hboot. If you can. What hboot version are you on?
Sent from my HTC One S using xda app-developers app
I have the same problem, phone keep reboot and will not turn on, i can get into recovery, but can not get contact via USB, what am i doing wrong?
Any step by step how to get out pictures before setting it back to factory settings
recovery loop
Just rooted HTC One S TMOUS using Hasoon 2000's tool. tried CWM backup of rooted stock, then followed instructions for PA 2.52 + gapps. Got stuck on PA boot screen. Won't boot all way up.
Phone will only boot into recovery. adb reboot bootloader goes into recovery. can't get into hboot to restore stock using RUU.
Advice?
Thanks kindly.
Same Problem here.
I wanted to join a wifi-network, then the htc freezed and now it's in bootloop.
I still read some oder threads in the internet but not realy good ideas I like.
Does anyone know whats happening in HBoot when I use "Clear Storage"? Does he clear the phone-memory or the SD-Memory? Or anything else?
Bond246 said:
Same Problem here.
I wanted to join a wifi-network, then the htc freezed and now it's in bootloop.
I still read some oder threads in the internet but not realy good ideas I like.
Does anyone know whats happening in HBoot when I use "Clear Storage"? Does he clear the phone-memory or the SD-Memory? Or anything else?
Click to expand...
Click to collapse
did anyone solve this? I have an unbranded unrooted HTC One S that is also stuck in a bootloop. I was just scanning the WIFI networks from settings and then the phone started looping by itself and only stopped after the battery was empty.
The phone is not modified in any way. I can get into hboot with power-volume down but then what? I don't really feel like doing a factory reset. Is there any other way out? Does the factory reset help?
Hi
I had the same problem and fixed it.
I made factory reset, then when i configured my Google account i disables the "sync Internet" Option.
Sent from my HTC One S using xda app-developers app
gingi007 said:
Hi
I had the same problem and fixed it.
I made factory reset, then when i configured my Google account i disables the "sync Internet" Option.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ya seen someone say that not sure if it was you but also some people have found having to many saved hotspots can also send you into a bootloop.
in my case for sure it was the google account cause i did factory reset, and had no saved hotspots and still it happened when i switched the wifi on\off after the factory reset(i mead got into boot-loop and needed a factory reset).
it is a serious bug\problem - i can't believe this can happen because of such a silly configuration.
the OS of HTC is not stabled at all!
If your bootloader is locked, then you dont have too many options re getting information off of your phone. Someone else may be able to post ideas. A factory reset may be your only option..
If you have already unlocked your bootloader, my suggestion would be to flash the latest TWRP Custom Recovery (google it). You can connect to your computer via usb through TWRP and access your sd card to get pictures, videos etc off of it.
Through TWRP you can also have access to adb.exe (ie using adb.exe commands and not just fastboot.exe commands, and thereby access all sorts of adb related commands (backups, linux shell, etc).
In order to actually fix the bootloop, well, usualy I find this is due to issues with the Kernel and custom ROM you are flashing (either one or the other), and so would reflash whatever worked before (ie a previous ROM or previous kernel).
But if this is all happening on a device you have not rooted nor flashed anything custom... Well, then that is a good question!
AKToronto
gingi007 said:
in my case for sure it was the google account cause i did factory reset, and had no saved hotspots and still it happened when i switched the wifi on\off after the factory reset(i mead got into boot-loop and needed a factory reset).
it is a serious bug\problem - i can't believe this can happen because of such a silly configuration.
the OS of HTC is not stabled at all!
Click to expand...
Click to collapse
Ya I'm not saying what you said is wrong or didn't work for you but I do think I could be right about kongo09 and Bond246 issue since it did happen when dealing with wifi and seen a few people say the same thing.
I am in a bootloop. What i did to get the phone start is just press first down volume button then power button (keep holding them until the phone goes oof). Inmediatily when the phone go off, stop pressing anything. ANYTHING, BE FAST, and it will boot normally. I am now tryying to get the stock recovery to avoid this sht.
gingi007 said:
Hi
I had the same problem and fixed it.
I made factory reset, then when i configured my Google account i disables the "sync Internet" Option.
Click to expand...
Click to collapse
Did the factory reset make you lose all your data? As in: pictures etc? I have read varying stories regarding this, some say you lose it all, some say you don't.
I have some recordings of interviews on there that I really(!!!) cannot lose. Does anyone know if HTC has the possibility to recover files from a phone in this condition?
jazzmijnhv said:
Did the factory reset make you lose all your data? As in: pictures etc? I have read varying stories regarding this, some say you lose it all, some say you don't.
I have some recordings of interviews on there that I really(!!!) cannot lose. Does anyone know if HTC has the possibility to recover files from a phone in this condition?
Click to expand...
Click to collapse
If you unlocked the bootloader then you could flash TWRP which will let you mount SD for the PC.
Darknites said:
If you unlocked the bootloader then you could flash TWRP which will let you mount SD for the PC.
Click to expand...
Click to collapse
Unfortunately not... Unrooted, stock bootloader and all... I spent all day reading threads on different forums, but so far it seems that there is no other solution to this bootloop problem than just doing a factory reset. But like I said, I have some very important recordings on my phone and before I give up on them I want to make sure I tried everything.
If anyone knows of a way to root and flash a new bootloader without wiping all my data in the process, that would be highly appreciated.
Or if anyone knows whether it is possible to somehow approach the storage (maybe through Linux) while the phone is bootlooping (not normally recognized by computer).
But also: I would very much like to hear from people who have done a factory reset from the stock boot loader: has it wiped just your apps and app data? Or has it wiped your files as well (photos, music, recordings etc)?
Like I said: any info would be much appreciated...
jazzmijnhv said:
Unfortunately not... Unrooted, stock bootloader and all... I spent all day reading threads on different forums, but so far it seems that there is no other solution to this bootloop problem than just doing a factory reset. But like I said, I have some very important recordings on my phone and before I give up on them I want to make sure I tried everything.
If anyone knows of a way to root and flash a new bootloader without wiping all my data in the process, that would be highly appreciated.
Or if anyone knows whether it is possible to somehow approach the storage (maybe through Linux) while the phone is bootlooping (not normally recognized by computer).
But also: I would very much like to hear from people who have done a factory reset from the stock boot loader: has it wiped just your apps and app data? Or has it wiped your files as well (photos, music, recordings etc)?
Like I said: any info would be much appreciated...
Click to expand...
Click to collapse
Not much you can do then because even unlocking could wipe SD.
Not sure if its possible with a locked bootloader but you may want to try getting into your bootloader then try typing fastboot boot <working kernel file>
Replace the phrase "<working kernel file>" with a stock boot.img that you know works.
As you can see this command is different from fastboot flash boot <working kernel file>.
This may get you out of the bootloop if you had kernel issues, and may allow you to load a kernel temporarily. Not sure if it works on locked bootloaders but it might.
If all you can access is the bootloader and fastboot, then you really have to play around with fastboot commands. See http://android-dls.com/wiki/index.php?title=Fastboot for the list.
Good luck!
jazzmijnhv said:
Unfortunately not... Unrooted, stock bootloader and all... I spent all day reading threads on different forums, but so far it seems that there is no other solution to this bootloop problem than just doing a factory reset. But like I said, I have some very important recordings on my phone and before I give up on them I want to make sure I tried everything.
If anyone knows of a way to root and flash a new bootloader without wiping all my data in the process, that would be highly appreciated.
Or if anyone knows whether it is possible to somehow approach the storage (maybe through Linux) while the phone is bootlooping (not normally recognized by computer).
But also: I would very much like to hear from people who have done a factory reset from the stock boot loader: has it wiped just your apps and app data? Or has it wiped your files as well (photos, music, recordings etc)?
Like I said: any info would be much appreciated...
Click to expand...
Click to collapse
Stock bootloader, same bootloop scenario - factory reset wiped everything including photos, music, other files. Clear storage seems to keep everything except the installed apps and configuration. It's the 4th time I'm doing it unfortunately :

T-Mobile LG Mytouch Q

Ok so I'm relatively new at trying to root and hack phones as well as adding custom roms. I searched all over the forums but could barely find anything related to my problem, and if I'm wrong i do apologize for re-posting. Anyways I rooted the phone using superoneclick and it all went fine. So i then decided to try and install a custom called CyanogenMod 9 onto the phone with Rom Manager. I'm guessing I did not do an extremely important step and now i fear my phone is bricked. I put the ROM into the root of the SD card, went into ROM manager, and trid installing the ROM. It all failed and now my phone is stuck on the same screen on the bootup where it keeps restarting itself telling me Failed installation factory reset failed and it restarts factory reset. The phone is from T-mobile and its a Mytouch Q. Any help would be very wonderful!
DashyStabby said:
Ok so I'm relatively new at trying to root and hack phones as well as adding custom roms. I searched all over the forums but could barely find anything related to my problem, and if I'm wrong i do apologize for re-posting. Anyways I rooted the phone using superoneclick and it all went fine. So i then decided to try and install a custom called CyanogenMod 9 onto the phone with Rom Manager. I'm guessing I did not do an extremely important step and now i fear my phone is bricked. I put the ROM into the root of the SD card, went into ROM manager, and trid installing the ROM. It all failed and now my phone is stuck on the same screen on the bootup where it keeps restarting itself telling me Failed installation factory reset failed and it restarts factory reset. The phone is from T-mobile and its a Mytouch Q. Any help would be very wonderful!
Click to expand...
Click to collapse
Hi, Are you able to get into the CWM menu? If so, Do a "Factory reset" clearing all data. Then clear the /cache partition and the davlik cache in the "advanced" menu. Then flash the rom again. If that doesnt work try clearing everything again and installing the default android 2.3.6 LG rom and take off again from there. My end advice? Dont flash this phone, its a peice of absolute crap
Yoyomah20 said:
Hi, Are you able to get into the CWM menu? If so, Do a "Factory reset" clearing all data. Then clear the /cache partition and the davlik cache in the "advanced" menu. Then flash the rom again. If that doesnt work try clearing everything again and installing the default android 2.3.6 LG rom and take off again from there. My end advice? Dont flash this phone, its a peice of absolute ****
Click to expand...
Click to collapse
Thanks worked like a charm . Wasn't able to get into CWM but I did get to install the default. This phon ebeing so bad is exactly why i wanted to try and see if flashing it would make it better haha

[Q] Recovery is broken??? I Don't Know.. Please Help

So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
alexdzk said:
So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
Click to expand...
Click to collapse
Did you wipe data and cache before flashing the new rom?
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
jd1639 said:
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
I'll try this then if it doesnt work ill try the factory reset/ relock whatever, thanks.
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
no its CWM
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
housry23 said:
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. I said it in my post.
alexdzk said:
Yes, I did. I said it in my post.
Click to expand...
Click to collapse
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
housry23 said:
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
alexdzk said:
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
Click to expand...
Click to collapse
Good. Glad you got it worked out. Was probably an old build of whatever recovery and because of the way KitKat changed things, there were a lot of problems wiping when the phone first came out. If you find any more good deals on your local Craigslist, PM me. I want a black n5 instead of my white one.
Sent from my Nexus 5 using Tapatalk

Somebody PLZ help Me revive this Phone

im new to all this rooting and flashing stuff and i did search quite thoroughly before resorting to posting on here. Ok so somehow i rooted and took the system app TextNow off of the phone since then ive tried hard resetting but now all the phone does after booting it has a little txt box that pops up over and over so much so that its impossible to do anything but power down and it reads" unfortunately TextNowOOBE has stopped...... Ok" . How can i fix this.... Ive reset the phone through recovery and cache partition both have been wiped. Plz someone help me
sjrjr4364 said:
im new to all this rooting and flashing stuff and i did search quite thoroughly before resorting to posting on here. Ok so somehow i rooted and took the system app TextNow off of the phone since then ive tried hard resetting but now all the phone does after booting it has a little txt box that pops up over and over so much so that its impossible to do anything but power down and it reads" unfortunately TextNowOOBE has stopped...... Ok" . How can i fix this.... Ive reset the phone through recovery and cache partition both have been wiped. Plz someone help me
Click to expand...
Click to collapse
#1 rule make a backup in recovery before tinkering
Aside from restoring a backup, the easiest way to get your phone working again would be to flash a fresh ROM. For example, Albertos AOSP is quite stable and up to date. You will need that ROM.zip and a compatible gapps.zip. wipe everything clean and flash those in recovery.
You will lose all your data.
I do not know what TextNow is, but if you need the "stock ROM" you may need to restore factory firmware via PC- you will lose all your data
What exactly are you trying to do?

Categories

Resources