Hello,
my Moto G6 is stuck during the boot-up. It goes to the phase where the background colors switch but after a while goes back to the blue android screen, followed by the switching colors again and so on. I have recently installed a security update and have already tried wiping the cache partition. I don't want to do a factory reset right now, as I have a lot of data on the phone that I need. Does anyone have an idea how I can recover the data? One reason why this might happen is that the storage was close to maxed out. I had the same issue yesterday and after a while letting it try to reboot it did work fine actually, but this time it has been stuck for hours and no progress. What might complicate the issue is that I currently don't have access to a Windows PC, only Mac.
Best,
Johannes
Related
I absolutely hate creating yet another thread, but I've tried everything I can and I'm stuck. I was up until 4am (no lie) last night and been at it again for hours tonight. So... here are the symptoms.
Multiple bootloops/reboots at any of the following points:
1) "Preparing device" with the "Please wait" animation.
2) Force close: Unfortunately, Setup has stopped.
3) Force close: process.com.android.systemui has stopped.
4) Force close: Google search has stopped.
5) Bootloop at the bootloader warning message
Usually, the boot animation doesn't even start. Often, I'll see the "Bootloader Unlocked" warning message, then the Moto logo, then it cycles back through any of the above fail points. Sometimes, it'll stay on the bootloader warning message the whole time and then jump directly to the lock screen.
All of this started after unlocking my brand new Moto X Pure Edition and then attempting to use the "Multi-tool" to root. Or...maybe it was after trying to root using one of the Chainfire images. I can't recall. After doing so, wifi stopped working (wouldn't turn on). So, I tried (using the tool again) to flash back to stock. At that point things strange things started happening (force closes). I then tried flashing to stock and immediately flashing the OTA (all via fastboot). When I booted up, Lollipop setup wouldn't load, it'd bootloop, come back and maybe I could get to the next screen, but wifi would be dead. Or I'd get wifi to work, but it'd crash after accepting Google privacy terms.
So, after all of that, I decided I would just revert back to stock. At that point I tried a number of options including what I think is the likely best bet, @SolarTrans guide here. Oh, and somewhere along the line I flashed TWRP 2.8.3 and flashed one of the custom ROMs (LiquidSmooth). It booted, but was very unstable and also threw the same/similar systemui force close messages, occasionally would lose wifi or begin force closing like crazy. Makes me think I have a bigger issue since it happens regardless of ROM/firmware. I also tried graffixnyc's images. So... yeah... just want to get back to stock.
I've been doing this stuff with Android for many years. Not a newbie by any means. Completely comfortable using fastboot or adb command line. I'm just at a loss and feel that it's likely I'll have to send it back to Motorola. I can get into the bootloader no problem. Everything else is a toss up. The last time I flashed files via the SolarTrans guide, it eventually loaded up the home screen (after many bootloops), but wifi wasn't working and I got a strange Moto message about reverting the sensors firmware or update. I rebooted and it never booted again, so I erased cache and userdata via fastboot. That didn't help. I just flashed the original firmware again and it spent a good 20/30 minutes bootlooping before getting to the setup screens. I skipped everything. Then it bootlooped at the home screen.
Open to suggestions!
Edit 1:
Pretty much anything causes the phone to bootloop, but I was able to get a screenshot of the baseband, kernel, build, etc. It bootlooped, but worked the second time around. I think I just made things way worse by trying to turn on bluetooth. It's just bootlooping over and over. Gonna try and get some sleep!
So, before bed, I flashed the OTA from the SolarTrans thread. It booted up, threw some errors and then once I connected to wifi it bootlooped. It did this for at least 10 minutes before I plugged the phone in and went to bed. When I woke up this morning, it was sitting on the setup screen. No errors. I signed in to my Google account and it restored all my apps. I rebooted. Still no problems. Just before leaving for work, I noticed that Dropbox wasn't installed. I installed it, signed in and then it bootlooped. After that...no luck. Kept rebooting. So, I brought the phone to work and left it on my desk for a few hours. It bootlooped or hung on the bootloader unlocked warning screen for at least 3 hours. I wiped cache. Same thing. Just now, I wiped userdata and rebooted. It went through the setup process without errors. Began restoring my apps and then froze. I manually restarted and now... no dice. Bizarre.
mercado79 said:
So, before bed, I flashed the OTA from the SolarTrans thread. It booted up, threw some errors and then once I connected to wifi it bootlooped. It did this for at least 10 minutes before I plugged the phone in and went to bed. When I woke up this morning, it was sitting on the setup screen. No errors. I signed in to my Google account and it restored all my apps. I rebooted. Still no problems. Just before leaving for work, I noticed that Dropbox wasn't installed. I installed it, signed in and then it bootlooped. After that...no luck. Kept rebooting. So, I brought the phone to work and left it on my desk for a few hours. It bootlooped or hung on the bootloader unlocked warning screen for at least 3 hours. I wiped cache. Same thing. Just now, I wiped userdata and rebooted. It went through the setup process without errors. Began restoring my apps and then froze. I manually restarted and now... no dice. Bizarre.
Click to expand...
Click to collapse
So, what was the problem then? The Dropbox app? Why is that?
No. Don't think so. It was just the trigger. I'm convinced any app would have eventually caused the bootloop.
I tried one more clean install of the official image straight from Motorola last night. Same results. So, I've initiated a return/repair.
Sent from my Moto X
Have they accepted repairing your device even with unlocked bootloader and root?
Sent from my XT1097 using XDA Free mobile app
They acknowledged that I'd unlocked the phone (it was logged in the record when they looked up my phone by IMEI), though I said I did so while trying to fix it (in order to wipe partitions and flash images which I also requested via their developer resources page).
They're sending a replacement phone without any push back at all. Honestly, I expected to send it in for repair. The rep said the standard protocol was to issue me a pin to order a new phone (mine is a customized Moto Maker model with a bamboo back).
Just so you're aware, unlocking the bootloader on Pure Edition phones does not void the warranty.
So, a replacement should be in my hands in about a week, I'm told. The phone was still within the initial month and so they're sending a brand new phone.
Sent from my Moto X
Hi all. So here's the skinny:
I've got a Verizon nexus 6, unlocked boot loader and rooted running 5.1.
No other mod except for the net tethering provision.
I did a factory reset this morning because my device wasn't showing up on ADM. It shows up in Google play via the website, and I'm able to install apps to it from there.
I have gone through all the basic troubleshooting steps Googling could afford me. After the factory reset, it showed up in ADM. But when I checked again just now, it's gone again. That was one of the primary reasons I did the reset (which was a pain in the butt by the way because I had a pin-at-boot and even after telling the phone to do a factory reset twice, it didn't go away until telling it to in the boot loader menu).
I'm pretty frustrated now, because I went through a lot of hassle to fix it... And with no SD card, titanium backup is out the window too.
Does anybody have a solution or has someone else experienced this?
So I bought a LG G2 today and all was fine until it asked if I wanted to do an OTA. I figured, why not its COMPLETELY stock. The only thing I did to the phone was a factory reset when I bought it then connected to my wifi and updated all the stock apps to the updated version. At that point it asked me if I wanted to perform the OTA so I hit Install now. It went through 1/2 with no problem but on 2/2 of the update it gets to 13% and brings me to a screen with a blue line over about 1/4 inch of the top of the screen and gives about 15 lines of files or directories that are not found. It acts like a bad flash. I have tried a hard reset and still brings me to the update screen after I select Yes twice. My pc's (yes multiple) will not even acknowledge its there. How can this happen on a completely stock verizon phone with a factory verizon OTA?? Any insight would be greatly appreciated!
10 of the errors start with FOTAFS_Open /system/lib/librs.
There different from there on. The rest of the errors are the cache partition.
Like I said to me it sounds like a bad flash but what now? I'm stumped!
I have a stock AT&T G6, got it when the phone first came out, and I haven't touched the firmware. Update after update, no problems.
Finally this morning my phone had enough - I performed a system update. However during the reboot, the phone froze for 30 minutes on the AT&T logo. Nothing changed.
Reset phone, nothing changed, 15 minutes no change. Reset phone to recovery mode - wipe cache - reset phone. Same thing - stuck at AT&T logo.
Finally I had enough - I did a full Factory reset. AT LAST! After 8 painful minutes stuck at the AT&T logo, my phone came to life and welcomed me to my new phone (FML).
So here I am with a freshly loaded copy of my new Nougat 7.0 software on my AT&T Build ( NRD90M.G920AUCS6EQF1 ) and I am desperately trying to run every possible data recovery option possible.
I WANT to recover my photos and SMS messages before I start using my phone. But I can't - every app I've run shows no results. Everything I'm seeing shows I need to root this phone to make it work.
Unfortunately I have no clue htf to do that. Every instruction I find online does not include my build version. My phone is turned off and not used until I recover this data. I would appreciate any help I can get in recovering this data!
Cassetti said:
I have a stock AT&T G6, got it when the phone first came out, and I haven't touched the firmware. Update after update, no problems.
Finally this morning my phone had enough - I performed a system update. However during the reboot, the phone froze for 30 minutes on the AT&T logo. Nothing changed.
Reset phone, nothing changed, 15 minutes no change. Reset phone to recovery mode - wipe cache - reset phone. Same thing - stuck at AT&T logo.
Finally I had enough - I did a full Factory reset. AT LAST! After 8 painful minutes stuck at the AT&T logo, my phone came to life and welcomed me to my new phone (FML).
So here I am with a freshly loaded copy of my new Nougat 7.0 software on my AT&T Build ( NRD90M.G920AUCS6EQF1 ) and I am desperately trying to run every possible data recovery option possible.
I WANT to recover my photos and SMS messages before I start using my phone. But I can't - every app I've run shows no results. Everything I'm seeing shows I need to root this phone to make it work.
Unfortunately I have no clue htf to do that. Every instruction I find online does not include my build version. My phone is turned off and not used until I recover this data. I would appreciate any help I can get in recovering this data!
Click to expand...
Click to collapse
No known root for current builds to my knowledge. Don't know if anyone is still picking away at it, but I wouldn't hold my breath. Development on this device has been almost silent for many months.
dandrumheller said:
No known root for current builds to my knowledge. Don't know if anyone is still picking away at it, but I wouldn't hold my breath. Development on this device has been almost silent for many months.
Click to expand...
Click to collapse
Pretty much what I've figured. Sounds like I'll just have accept they're lost and move on. Thx
TL : DR - My phone won't boot because of low disk space, how can I free up memory?
Greetings,
Project FI purchased Moto X4 running BONE STOCK and absolutely ZERO CUSTOMIZATION. If I can get access to my pics taken via the camera I'm ok with wiping the phone and starting over. Screenshots folder access would be cool too but not life necessary... Wait there has to be a way to make a dump of all this data somehow, somewhere right?
Last night I was on 15% or less battery life and less than 100mb's of disk space left. (i know, i know, i'm a dummy head)
I heard about PLEX running no problem on mobile Browser and decided to test it out and sure enough it worked fine. Was test streaming a few movies out when my PHONE DIED. I thought, oh man, thats probably not the best since it died and it was low on space but yeah I threw it on the charger and went to bed....
This morning, I confirmed it was charged 100% but when I turn it on, the phone will not boot past the AndroidOne screen. Left it there for 40mins and no change, AndroidOne displays and the rainbow colored bars at bottom are frozen(don't scroll) and screen flashes off/on every 30 secs to that same AndroidOne screen.
However I can boot into Bootloader with no issues, and into Recovery mode as well, but there is not a WIPE CACHE option on this device... Obviously the Wipe data/factory reset option is there...
BUT BEFORE WE GET TO THAT POINT, WHaT GIVES? Anyone have any ideas?
few ?'s
#1 - In the Bootloader menu, What is this RESTART BOOTLOADER option for, what does it do?
#2 - Is there any way I can free up some space from Bootloader/Recovery as I'm pretty sure thats the cause of this problem I'm having. I was intending to do that today actually, was going to dump all my pics from the phone to a computer. ..
#3 - Is there any way I can see if my pic's backed up somewhere? New to the Google ecosystem...
#4 - Is there any way I can read or access the phones data via a computer, then perhaps I can delete a few pics to free up memory or better yet, wipe app caches to clear up memory instantly? PERHAPS even command line ????
Any and all other inputs and suggestions greatly appreciated before I take that step of wiping the device(which assumes I can start over with a working phone by doing that but not a guarantee).
Please ADVISE
much appreciated!
oNe
@Sean Price
Go to photos.google.com with the account you signed into your phone to see if they were backed-up.
jhedfors said:
@Sean Price
Go to photos.google.com with the account you signed into your phone to see if they were backed-up.
Click to expand...
Click to collapse
Thanks for the reply, so Google says I have backup turned off but my photos are in the timeline.. SO I just manually downloaded them all as a backup/pre-caution.
any other suggestions before I attempt the WIPE data/factory reset option from Bootloader > Recovery?
I can boot up fine into Bootloader and Recovery.
I can access the logs via . Bootloader > Recovery > View Recovery Logs
last line states the following: I:[libfs_mgr]fs_mgr_read_fstab_dt(): failed to read fstab from dt
please advise,
oNe
the internet failed, I found nothing on this issue and since I got 90% of my photos recovered via Google photos..
long story short, from Bootloader/Recovery I did the WIPE data/factory reset and i'm good to go now.
even updated my phone to all the latest android and moto updates, feels and seems like a totally new phone.. at a cost of 15gbs!! 15/32gbs used jus for the AndroidONE o/s, am I missing something?
oNe
Sean Price said:
the internet failed, I found nothing on this issue and since I got 90% of my photos recovered via Google photos..
long story short, from Bootloader/Recovery I did the WIPE data/factory reset and i'm good to go now.
even updated my phone to all the latest android and moto updates, feels and seems like a totally new phone.. at a cost of 15gbs!! 15/32gbs used jus for the AndroidONE o/s, am I missing something?
oNe
Click to expand...
Click to collapse
Not missing anything the OS takes up a lot of space. I am using a Pie ROM right now and system takes up 12GB.
johnjingle said:
Not missing anything the OS takes up a lot of space. I am using a Pie ROM right now and system takes up 12GB.
Click to expand...
Click to collapse
gotcha.. so basically 32gb's is the new 8gb
moving forward I'll try to stick to 64gb phone's and up..
oNe