Related
Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?
Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.
BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.
beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link
Hi hope you can help, I'm trying to fix my sisters phone that has developed a software fault. The phone is completely stock, never rooted and I believe its on lollipop but cant switch on to be sure. Her fault happened when on snap chat to a friend and the phone just cut off and kept boot looping to the lg logo.
I have tried booting it into android recovery by holding the power and volume down button together, the re applying this when the logo appears, instead it just shows the battery charging.
Tried opening it through sdk manager in a cmd command of "adb reboot recovery" and still nothing.
When plugged into my pc it tried to install the drivers but stops after 2 mines and reboots.
Is their any way around this issue or to at least boot into recovery? its the LG G4 H815 model.
Thanks
Didn't it just bootloop? XD it's typical issue for 2015 G4s???
Wysłane z mojego LG-H815 przy użyciu Tapatalka
no its stuck bootlooping if you try to turn it on, what's the cure?
Thanks
morgiee said:
no its stuck bootlooping if you try to turn it on, what's the cure?
Thanks
Click to expand...
Click to collapse
Search for boot loop over here there are multiple threads!
If your serial (sticker behind the battery ) starts with 5xx you have the hardware issue hundreds other have. Repairing is the only option to fix.
.
steadfasterX said:
Search for boot loop over here there are multiple threads!
If your serial (sticker behind the battery ) starts with 5xx you have the hardware issue hundreds other have. Repairing is the only option to fix.
.
Click to expand...
Click to collapse
Thanks for that here is a picture of the sticker under the battery. I think it does is this one of the hardware effected ones?
see attachments for photo
Thanks
Yes you have a 505 and so it seems you have the infamous bootloop.
As long as you have warranty send it to LG for repairing
There are guides here how to backup with the freezer method of you want to.
.
steadfasterX said:
Yes you have a 505 and so it seems you have the infamous bootloop.
As long as you have warranty send it to LG for repairing
There are guides here how to backup with the freezer method of you want to.
.
Click to expand...
Click to collapse
Thanks you have been a great help, its my sisters phone so the freeze backup would be perfect as she has photos on their she wants to backup. Have you got a link to the best guide to follow? Also final question. If it is under warranty for them to fix she has smashed the phone screen and has been cracked for almost a year (don't ask why she is living with a cracked screen because even I don't know haha). It still displays and responds to touch (prior to bootloop failure) and the intention was to get her phone up and running then replace her screen for her. Even if the damaged screen has nothing to do with the cause of the bootloop screen will LG dismiss this and refuse repair because of a faulty screen? In which case am I best replacing the screen first then shipping the phone off to LG repair that way they cant dismiss the screen as a cause.
Thanks
morgiee said:
Hi hope you can help, I'm trying to fix my sisters phone that has developed a software fault. The phone is completely stock, never rooted and I believe its on lollipop but cant switch on to be sure. Her fault happened when on snap chat to a friend and the phone just cut off and kept boot looping to the lg logo.
I have tried booting it into android recovery by holding the power and volume down button together, the re applying this when the logo appears, instead it just shows the battery charging.
Tried opening it through sdk manager in a cmd command of "adb reboot recovery" and still nothing.
When plugged into my pc it tried to install the drivers but stops after 2 mines and reboots.
Is their any way around this issue or to at least boot into recovery? its the LG G4 H815 model.
Thanks
Click to expand...
Click to collapse
Cab you just boot into the recovery and clean the cache partition and see if it reboots successfully.
Sent from my XT1033 using XDA-Developers mobile app
shibaa987 said:
Cab you just boot into the recovery and clean the cache partition and see if it reboots successfully.
Sent from my XT1033 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the suggestion but sadly tried that with no look. her battery isn't great either doesn't hold much of a charge. Phone is in a mess really and trying to fix it for her rather than a shop or company charging her an arm and a leg. It just goes to the LG logo then the battery logo then nothing.
morgiee said:
Thanks for the suggestion but sadly tried that with no look. her battery isn't great either doesn't hold much of a charge. Phone is in a mess really and trying to fix it for her rather than a shop or company charging her an arm and a leg. It just goes to the LG logo then the battery logo then nothing.
Click to expand...
Click to collapse
This can not be solved with deleting cache.
Google is your friend!! Here is the"link". :
http://lmgtfy.com/?q=XDA+g4+freezer+backup
Besides that check my signature... the first line. Really.. :silly:
Well to be honest if you can I would replace the screen first just to be sure that this will make no trouble when sending it to LG. Jm5c
.
please help my oneplus 3 can't boot to system or recovery after unbricking with mega unbrick method 1 and 2
the phone boot to black screen and led notification shining white
i try unbricking method again and flash recovery from fastboot dosn't work
sorry my english
Did you solved? I have the same issue ... No ideea what to do... How did you solved?
bibiii79 said:
Did you solved? I have the same issue ... No ideea what to do... How did you solved?
Click to expand...
Click to collapse
If you follow the instructions for method 2, and repeatedly do it a few times, you can succeed. The important thing is to follow the instructions strictly, however silly they may look like.
I did several times, double checking all steps, still boot loop. After apply the method 2 , is doing a boot loop. Than I tried to apply again method 2 I have the successful download with green ...than I go in recovery and flash over adb sideload oos 3.2.8 ...than I start , no more boot loop, but after Oneplus logo goes into black screen with a withe stable notification led turned on ....I left over night ... But it keep staying like that until I force to power off by pressing and holding power button( after I want to turn off i cannot only going into bootloader and from there I choose power of, because is automatically turning on if I press and hold only the power button in order to turn off the device).
Pfiu difficult... I am thinking, some files are missing, this , and where I go in bootloader in missing the values on. Bootloader version- , and baseband version- ....
bibiii79 said:
I did several times, double checking all steps, still boot loop. After apply the method 2 , is doing a boot loop. Than I tried to apply again method 2 I have the successful download with green ...than I go in recovery and flash over adb sideload oos 3.2.8 ...than I start , no more boot loop, but after Oneplus logo goes into black screen with a withe stable notification led turned on ....I left over night ... But it keep staying like that until I force to power off by pressing and holding power button( after I want to turn off i cannot only going into bootloader and from there I choose power of, because is automatically turning on if I press and hold only the power button in order to turn off the device).
Pfiu difficult... I am thinking, some files are missing, this , and where I go in bootloader in missing the values on. Bootloader version- , and baseband version- ....
Click to expand...
Click to collapse
The bootloader and baseband versions were missing when i bought the phone new and are still blank today after flashing a few ROMs and Recoveries/Firmware and modems. So that is not an issue.
Are you downloading the correct files?
tnsmani said:
The bootloader and baseband versions were missing when i bought the phone new and are still blank today after flashing a few ROMs and Recoveries/Firmware and modems. So that is not an issue.
Are you downloading the correct files?
Click to expand...
Click to collapse
Yes, I am using the unbrick method with msm download tool, using the Method 2, after apply, installing all's the Qualcomm drivers 9008 , drivers signature off in windows.... The unbrick tool is passed with the green message .... Reversing back to oos 3.1.2 Android 6.0.1 ..stock, I have recovery working and bootloader also working, bootloader is locked ....so I cannot do too mutch. I start the device right away after unbrick tool and still boot to op logo that is going to vibrate as restart .... And stays in boot loop. Next step I go into recovery , and do over sideload an update with a full ROM, oos 4.0.1 , also tried with full ROM 3.2.8 ...I can sideload the whole ROM , than i start the device and after op logo goes in black screen and white motivation led lighted .... I leave it for 30 min, and still in the same, now I force turn off by going into bootloader and power off. Notice that after this sideload flash I cannot access the recovery. So I need to apply back the unbrick msm download tool for op3.
I tried also to flash over sideload a signed script from Ahmed , unified toolkit , to activate the USB debugging, but gives an error.
I run out of ideas .....any help is welcome ....
Thanks
bibiii79 said:
Yes, I am using the unbrick method with msm download tool, using the Method 2, after apply, installing all's the Qualcomm drivers 9008 , drivers signature off in windows.... The unbrick tool is passed with the green message .... Reversing back to oos 3.1.2 Android 6.0.1 ..stock, I have recovery working and bootloader also working, bootloader is locked ....so I cannot do too mutch. I start the device right away after unbrick tool and still boot to op logo that is going to vibrate as restart .... And stays in boot loop. Next step I go into recovery , and do over sideload an update with a full ROM, oos 4.0.1 , also tried with full ROM 3.2.8 ...I can sideload the whole ROM , than i start the device and after op logo goes in black screen and white motivation led lighted .... I leave it for 30 min, and still in the same, now I force turn off by going into bootloader and power off. Notice that after this sideload flash I cannot access the recovery. So I need to apply back the unbrick msm download tool for op3.
I tried also to flash over sideload a signed script from Ahmed , unified toolkit , to activate the USB debugging, but gives an error.
I run out of ideas .....any help is welcome ....
Thanks
Click to expand...
Click to collapse
Hi bro, did you solved it? Im facing the same problem here
bluuquthug said:
Hi bro, did you solved it? Im facing the same problem here
Click to expand...
Click to collapse
Unfortunately not yet ... Yes I solve it, I bought a Moto Z with dual SIM and snapdragon 820 and 64 GB and SD card with 280 euro .... I am disappointed at the moment about Oneplus 3 , I was a Nexus fan and switched to oneplus ... I thought will be opensource ... But way to expensive repair this done in service , Easter to buy another one ... You save time .. you cannot save money on it ..
bibiii79 said:
Unfortunately not yet ... Yes I solve it, I bought a Moto Z with dual SIM and snapdragon 820 and 64 GB and SD card with 280 euro .... I am disappointed at the moment about Oneplus 3 , I was a Nexus fan and switched to oneplus ... I thought will be opensource ... But way to expensive repair this done in service , Easter to buy another one ... You save time .. you cannot save money on it ..
Click to expand...
Click to collapse
Had the same problem with my oneplus x.
P
oneszero said:
Had the same problem with my oneplus x.
Click to expand...
Click to collapse
And what was the end of your story with Oneplus x?
bibiii79 said:
P
And what was the end of your story with Oneplus x?
Click to expand...
Click to collapse
RMA'd it to a service center for repair, after two tech support calls. They actually told me that they couldn't repair it due to "water damage." Funny thing is, that phone was never dropped in or on anything, let alone in WATER. Then to add insult to injury they refused to send it back to me stating that I had to pay for return shipping. My wife got on the phone with them and by the end of the phone call they said that they would send it back for free. HAHA. So I bought a Oneplus 3 after that whole ordeal. All the while the Oneplus X sat in the box on my desk for about 5 months. Last week I decided to pick it up and tinker with it some more. I scoured the net trying to find any other programs or solutions that I hadn't tried prior to sending it off. I came across somethings that I hadn't seen before. https://forum.xda-developers.com/oneplus-x/help/fastboot-mode-available-stuck-kindly-t3387918. http://rootmygalaxy.net/oneplus-x-s...w.pickmod.com/rom/4187/coloros-for-oneplus-x/. Ended up flashing Color OS via msm tool. Wouldn't load OS, but i didn't end up with a black screen and white LED, it just sat there. So right after I flashed Color OS, i Flashed the mini unbrick tool by Naman, and BOOM it booted into OS. Hope this helps.
I tried to root my phone last night, but I stop midway of the process because of some problems like "phone not turning on with no vibrate at all when I restart after its stuck to inverted white screen, when I luckily turn it back on but it bootloops".
Heres the details:
I run unlock.bat then after its done it reboots with inverted white screen with logo then I run restore.bat and after it restart there is no sign of warning "failed verification" until it fully loads up, I go back to fastboot again to flash TWRP after running twrp.bat it says "flash succesfully" and the program closed by itself, then I go to recovery mode after rebooting I saw android error just like how it use to be. I press power button + volume up then release the volume up then I see the stock recovery (which it should be TWRP since I've done flashing it).
I think that my bootloader is still locked since there's no warning display of "failed verification". So I repeat the steps again after running unlock.bat, it reboots and the screen is inverted but it's stuck up to white logo, I waited for a while but nothing happens so I tried to reboot my phone "holding power button (power off)" when power on, it wont turn on, no vibration just a sound on laptop "connected sound and disconnected sound" I tried to power it on many times but still no luck I got panicked, jittery walking back and forth :crying:. Then I disconnect the usb cable and I tried to turn it on and suddenly I feel the vibration on my phone then it boots up but still stuck in white screen then it restart after keeping it for too long (while watching videos related to my problem)...
then my friend here said "ohh it bootloop" he read the instruction and he said to try this
"FAQ 1. Stuck at white screen with asus logo?
Sol. a) White screen means you are unlocked (action of unlock.bat), so you may give a try to restore.bat in fastboot mode."
and it solve my problem my phone is working again ... But I want to continue to root it but I'm afraid which steps I should go next, I still don't see the warning "failed verification" after my phone boots up and works again... I need HELP thank you
I also got question: is my bootloader unlock since it inverted white screen? or it still locked since there no sign of warning "failed verification"?
@PrinceLys
What is your build number in settings ,about phone ?
timbernot said:
@PrinceLys
What is your build number in settings ,about phone ?
Click to expand...
Click to collapse
ahmm I think this?
model number: ASUS_Z00AD
android version: 6.0.1
software information: WW_4.21.40.223_20161216
P.S my phone is back on working state.
I just don't know if I can proceed to root after the incident. I don't know, I just want to make sure that my bootloader is still unlocked after what I've done (it did white screen with black asus logo) or.... it doesn't unlocked at all since I don't see this warning "your device has failed verification and may not work properly." (I've attach screenshot from the video tutorial)
I tried to manualy check if my bootloader is really on unlock state but I can't using these methods
method 1: on device’s dialer dial *#*#7378423#*#* (failed)
method 2: fastboot oem device-info (failed)
my recovery it still on stock recovery even after I flash twrp
btw guide source: https://forum.xda-developers.com/zenfone2/general/root-install-xposed-marshmallow-6-0-1-t3456443
Q: should I still continue to flash twrp until it install?
Theres 2 bootloader unlock tools in general section , one is automatic
Read this from start to finish before doing anything.. also have on another device to refer to as you are doing the steps also download the ROM and gapps you want and put on SD card before you start even if you have to download them and move them from PC to SD card. https://plus.google.com/113955136844726294013/posts/aLJdNZN3g8q
Sent from my ASUS_Z00A using Tapatalk
timbernot said:
Theres 2 bootloader unlock tools in general section , one is automatic
Click to expand...
Click to collapse
I'm going to look for it... thanks
musicman5844 said:
Read this from start to finish before doing anything.. also have on another device to refer to as you are doing the steps also download the ROM and gapps you want and put on SD card before you start even if you have to download them and move them from PC to SD card. https://plus.google.com/113955136844726294013/posts/aLJdNZN3g8q
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I've haven't fully read the instruction maybe tomorrow I will read it.
I just downloaded the files early and look into it... it seems like the versions are kinda latest (I don't know much about the droidboot ver. but I just look at the number on it "the higher the latest /heh") also the twrp is 3.0.3.
the ones that I used are all in package and it was 3.0.2 so I kinda go for the link you gave me
Thanks :good:
Hi,I've had the same situation,but it is solved now.If you have any problem,maybe I can help you .
nanobrain---- said:
Hi,I've had the same situation,but it is solved now.If you have any problem,maybe I can help you .
Click to expand...
Click to collapse
(I've finally think my bootloader is unlock after all.)
btw, did you succesfylly flash twrp?
Mine didn't flash (using twrp.bat), I guess I will try it again tonight if it fails again im gonna dl twrp from official and manually flash it.
I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy
Perchy35 said:
I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy
Click to expand...
Click to collapse
Just use my guide, at the bottom of it it has everything you need to reflash stock firmware hold the power and volume down button until you get to the fastboot/ bootloader screen, also since you replaced the battery and did your own repair we still might not be able to help you because there's to many variables of user interference now, and yes Google kind of has made it a bit more complicated to root devices now unfortunately
Thanks for the reply, please can you put a link to your guide?
Perchy35 said:
Thanks for the reply, please can you put a link to your guide?
Click to expand...
Click to collapse
https://forum.xda-developers.com/g6-play/how-to/guide-t3929928
Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.
Perchy35 said:
Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.
Click to expand...
Click to collapse
Yes. Hold power and volume down, it'll look a few times and catch, you'll see fastboot. The Android guy and red and white text. May take a few loops
sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?
Perchy35 said:
sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?
Click to expand...
Click to collapse
Whats the carrier?
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Here you go. Amazon Jeter Firmware. That's the main folder.
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Spaceminer is correct, once you catch that sweet spot with the phone to get it in bootloader/fastboot mode just flash the firmware and you should hopefully be good to go, if you want it rooted my guide covers that to but let's just get you a working phone first before you try to root lol
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
You can either flash 8 or 9, what I would do is flash 8 then update it to 9 then if you want it rooted root it
Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hey so out of curiosity did you get it fixed and working?
ninjakira said:
Hey so out of curiosity did you get it fixed and working?
Click to expand...
Click to collapse
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
Also can I check that without USB debugging selected this method will override and flash still?
Perchy35 said:
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
I am having issue with the last part, getting "The credentials you provided cannot be determined to be authentic" ?
Also can I check that without USB debugging selected this method will override and flash still?
Click to expand...
Click to collapse
Wait what are you needing your Moto id for? The links for the stock firmware are in my guide, just follow the bottom section of it
Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..
Perchy35 said:
Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
Click to expand...
Click to collapse
If you don't have the bootloader unlocked then that is something you can do if you want the phone rooted if not you don't have to unlock the bootloader to flash stock firmware
Perchy35 said:
ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..
Click to expand...
Click to collapse
You either didn't install adb minimal or you have a bad cord, type fastboot devices and if nothing pops up saying you have a device in fastboot then it's one of the 2 things I said, extract the contents from the rar or zip file you got from adb minimal download, then install what you extracted
I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.
Perchy35 said:
I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.
Click to expand...
Click to collapse
Sorry been at work and I'm ona break, I totally forgot though you can use Moto smart Assistant for pc to fix this more than likely, so download and useMoto smart Assistant