Hi,
I followed this guide on how to root the pixel 2: "androidcentral.com/how-root-google-pixel-2" and finished all the steps. But when running step 11 it got stuck in a boot loop due to some software issues with the patched image I assume.
I've tried opening the phone in fastboot mode and then connecting with ADB, but it seems I cannot find my device since USB-debugging is not turned on.
Any ideas of how this can be solved? Or am I screwed?
Try rebooting into recovery. When you see the Android laying down and I believe it says no command, press the up button. This should bring you to another menu where ADB sideload is an option. you could then download the appropriate OTA from Google and sideload it to the phone.
Larzzzz82 said:
Try rebooting into recovery. When you see the Android laying down and I believe it says no command, press the up button. This should bring you to another menu where ADB sideload is an option. you could then download the appropriate OTA from Google and sideload it to the phone.
Click to expand...
Click to collapse
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
helpless_user said:
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
Click to expand...
Click to collapse
when in Bootloader mode (where it shows your "baseband version" and such), you actually use the volume button to change around the different options to boot, and then the "on/off" button to select.
But it looks like you get it to show the red "recovery mode" and, I imagine, you intuitively pressed the "on/off button" to select it, but in the unlikelihood that that is the case, make sure you are not holding or pressing or "....clicking volume up" button while it's booting; that's probably where you're going wrong....
only once you're in the stock recovery mode -- with the android lying down, dead, and a red exclamation point coming out of it -- is where you press the "volume up" and power button together to see the options...
good luck and hope this helps....
simplepinoi177 said:
when in Bootloader mode (where it shows your "baseband version" and such), you actually use the volume button to change around the different options to boot, and then the "on/off" button to select.
But it looks like you get it to show the red "recovery mode" and, I imagine, you intuitively pressed the "on/off button" to select it, but in the unlikelihood that that is the case, make sure you are not holding or pressing or "....clicking volume up" button while it's booting; that's probably where you're going wrong....
only once you're in the stock recovery mode -- with the android lying down, dead, and a red exclamation point coming out of it -- is where you press the "volume up" and power button together to see the options...
good luck and hope this helps....
Click to expand...
Click to collapse
I tried this and I never get to the dead android screen. I just get to a screen that says that my bootloader is unlocked and then the Google logo is showing.
helpless_user said:
I tried this and I never get to the dead android screen. I just get to a screen that says that my bootloader is unlocked and then the Google logo is showing.
Click to expand...
Click to collapse
Hmmmm...it sounds like something's wrong with your boot partition, then -- that's where the recovery resides. I suggest re-downloading the latest Full Factory image (from Google's developers site), editing flash-all to remove the "-w" and "exit" at the end, then running the flash-all once again on your device.
....after reading your OP, one key thing to keep in mind is that, in Bootloader Mode, you use "fastboot" commands while you use "adb" commands when within the OS or recovery....
And, for future reference, it would be better (most likely) if you wish to root the taimen for you to follow THIS GUIDE: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 .
helpless_user said:
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
Click to expand...
Click to collapse
In fastboot you can boot to a recovery.img; fastboot boot twrp.img
Download TWRP .img here.
(that recovery menu allows adb mode also).
Here you can(re)flash zip/image etc.
Format /data to ensure it is not encrypted.
For example, flash the extracted images of the OTA images from Google.
simplepinoi177 said:
Hmmmm...it sounds like something's wrong with your boot partition, then -- that's where the recovery resides. I suggest re-downloading the latest Full Factory image (from Google's developers site), editing flash-all to remove the "-w" and "exit" at the end, then running the flash-all once again on your device.
....after reading your OP, one key thing to keep in mind is that, in Bootloader Mode, you use "fastboot" commands while you use "adb" commands when within the OS or recovery....
And, for future reference, it would be better (most likely) if you wish to root the taimen for you to follow THIS GUIDE: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 .
Click to expand...
Click to collapse
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
helpless_user said:
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
Click to expand...
Click to collapse
I'm real happy you got it back up and running!
Yeah, I'm not agreeing with all of what Google's doing now (in concerns with the Pixel 4 [i.e. removing unlimited original quality storage]), but they really did well with the whole "Bootloader Mode" where you can feel a bit more secure and confident that, as long as you have access to Bootloader Mode and can successfully connect your device, you're not too far gone and definitely bricked beyond hope! It's not so hopeless as with devices before and what the term "bricking" truly applies to....
Happy to have helped!
Not able to figure out the exact fix
helpless_user said:
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
Click to expand...
Click to collapse
@OP, I am still stuck with the exact same issue. How did you exactly fix it? After running the solution given, I'm back at the infinite logo screen again.
Edit: It worked, thank you so much! This is a life saver.
simplepinoi177 said:
I'm real happy you got it back up and running!
Yeah, I'm not agreeing with all of what Google's doing now (in concerns with the Pixel 4 [i.e. removing unlimited original quality storage]), but they really did well with the whole "Bootloader Mode" where you can feel a bit more secure and confident that, as long as you have access to Bootloader Mode and can successfully connect your device, you're not too far gone and definitely bricked beyond hope! It's not so hopeless as with devices before and what the term "bricking" truly applies to....
Happy to have helped!
Click to expand...
Click to collapse
Hi i have the same issue with different device lenovo tab m10 tbx605L and i cant boot the recovery.img it throws me this error.Can u give me any ideas?
helpless_user said:
Hi,
I followed this guide on how to root the pixel 2: "androidcentral.com/how-root-google-pixel-2" and finished all the steps. But when running step 11 it got stuck in a boot loop due to some software issues with the patched image I assume.
I've tried opening the phone in fastboot mode and then connecting with ADB, but it seems I cannot find my device since USB-debugging is not turned on.
Any ideas of how this can be solved? Or am I screwed?
Click to expand...
Click to collapse
Did you install TWRP before rooting? If you did, that is the source of the bootloop. Our root guides here are much simpler than the one you provided the address to. The article in question is also out of date. Current versions of TWRP and Magisk don't play nice together. You need to BOOT TWRP using fastboot instead of installing it.
Copying the latest Magisk package to your internal storage, then renaming it to uninstall.zip and flashing it through TWRP should remove Magisk and resolve the bootloop. If that doesn't work, flashing the last stock package should.
EDIT: Quoted the wrong poster. My reply is an answer to the quoted poster instead of the poster who revived a dead thread with a question for a totally different device.
Strephon Alkhalikoi said:
Did you install TWRP before rooting? If you did, that is the source of the bootloop. Our root guides here are much simpler than the one you provided the address to. The article in question is also out of date. Current versions of TWRP and Magisk don't play nice together. You need to BOOT TWRP using fastboot instead of installing it.
Copying the latest Magisk package to your internal storage, then renaming it to uninstall.zip and flashing it through TWRP should remove Magisk and resolve the bootloop. If that doesn't work, flashing the last stock package should.
Click to expand...
Click to collapse
unfortunately there is not an exact version of twrp recovery available for my device lenovo (tbx605L) even when i try to boot the stock recovery.img , it says FAILED (remote : unknown command) do you know what is causing this error??
safaan0313 said:
unfortunately there is not an exact version of twrp recovery available for my device lenovo (tbx605L) even when i try to boot the stock recovery.img , it says FAILED (remote : unknown command) do you know what is causing this error??
Click to expand...
Click to collapse
I didn't realize you had replied to a thread that was two years old AND for the wrong device. Ask in the Lenovo section. This is the Pixel 2 XL section and advice given here is not applicable to you.
Strephon Alkhalikoi said:
I didn't realize you had replied to a thread that was two years old AND for the wrong device. Ask in the Lenovo section. This is the Pixel 2 XL section and advice given here is not applicable to you.
Click to expand...
Click to collapse
Hmm well thanks for your indirect F**k off
safaan0313 said:
Hmm well thanks for your indirect F**k off
Click to expand...
Click to collapse
I'm not sure you're aware of this, but not all devices are the same. Case in point: Samsung. How do you use fastboot commands on a Samsung device? Answer: You can't as Samsung doesn't support fastboot.
But thank you for making your expectations clear. Apparently, according to you, I should be able to figure out your problem despite not owning your device. It doesn't work that way. The only reason I know the answer to the question I posted in the previous paragraph is because I own a Samsung device.
Seriously, you getting bent out of shape at me because of your own screw-up is laughable.
Strephon Alkhalikoi said:
I'm not sure you're aware of this, but not all devices are the same. Case in point: Samsung. How do you use fastboot commands on a Samsung device? Answer: You can't as Samsung doesn't support fastboot.
But thank you for making your expectations clear. Apparently, according to you, I should be able to figure out your problem despite not owning your device. It doesn't work that way. The only reason I know the answer to the question I posted in the previous paragraph is because I own a Samsung device.
Seriously, you getting bent out of shape at me because of your own screw-up is laughable.
Click to expand...
Click to collapse
Right I knew that.I am sorry.I was so damn angry at my own mistake.I AM S O R R Y.But off the record I just repaired my tab
Related
I have a Galaxy Nexus, GSM version. It was working fine about ~3 weeks ago. I turned it off and removed the SIM card as I upgraded to a new phone.
Now I've turned it on and it just hangs on boot showing the animated X.
I tried recovery mode and get a "No Command" error.
I've never done anything to this phone before, in other words it's just running standard Android. Any advice? I've looked through some past posts but it seems like a lot of people have rooted the phone with custom OS, etc. I've never done any of that. So trying to figure out what the issue is with this phone. Any advice would be appreciated.
Thanks,
GR
<BUMP> sorry for pinging on this again but haven't seen any replies and I'm stuck... not able to get the phone to start. Any help would be much appreciated. Not sure if anyone else has had this problem? Thanks so much. GR
GR5000 said:
I have a Galaxy Nexus, GSM version. It was working fine about ~3 weeks ago. I turned it off and removed the SIM card as I upgraded to a new phone.
Now I've turned it on and it just hangs on boot showing the animated X.
I tried recovery mode and get a "No Command" error.
I've never done anything to this phone before, in other words it's just running standard Android. Any advice? I've looked through some past posts but it seems like a lot of people have rooted the phone with custom OS, etc. I've never done any of that. So trying to figure out what the issue is with this phone. Any advice would be appreciated.
Thanks,
GR
Click to expand...
Click to collapse
GR5000 said:
<BUMP> sorry for pinging on this again but haven't seen any replies and I'm stuck... not able to get the phone to start. Any help would be much appreciated. Not sure if anyone else has had this problem? Thanks so much. GR
Click to expand...
Click to collapse
when you see this "no command", press power + volume up to see the recovery menu
Thank you so much for the info. I'm trying this when I see the no command screen but nothing happens. The phone is just completely locked / frozen. I have to remove the battery. Any additional help would be much appreciated!
Thanks,
GR
samersh72 said:
when you see this "no command", press power + volume up to see the recovery menu
Click to expand...
Click to collapse
Maybe you don't even have a custom recovery installed yet? Not necessary, but since custom recovery are far more convenient than the stock one, you might wanna give it a try.
Sent from Google Nexus 4 @ CM11
The phone is completely stock. I've never done anything to it so not sure why I'm having this issue to begin with. But what custom recovery would you recommend I try? Is there a link that you can send me? And how would I install it given that I cannot even get the phone to boot?
Thank you
AndyYan said:
Maybe you don't even have a custom recovery installed yet? Not necessary, but since custom recovery are far more convenient than the stock one, you might wanna give it a try.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
GR5000 said:
And how would I install it given that I cannot even get the phone to boot?
Click to expand...
Click to collapse
Hold both VOLUME+ and VOLUME- keys, and while holding, long press POWER key. Do you see a green Android robot with its lids open? If yes, you're in fastboot mode, from which you can flash recovery, stock ROM, etc. (but if no...)
I'm on the phone now and can't provide links... Just first tell us whether you could boot into fastboot, will catch up later depending on your answer.
Sent from Google Nexus 4 @ CM11
When the phone is off, if I turn it on it just hangs at the animated X.
When the phone is off, if I press volume up/down + power then yes I see the screen that you're talking about. So I can boot into fastboot. When I choose Recovery Mode it restarts and that's when I get the No Command error.
Thank you so much for your help.
GR
AndyYan said:
Hold both VOLUME+ and VOLUME- keys, and while holding, long press POWER key. Do you see a green Android robot with its lids open? If yes, you're in fastboot mode, from which you can flash recovery, stock ROM, etc. (but if no...)
I'm on the phone now and can't provide links... Just first tell us whether you could boot into fastboot, will catch up later depending on your answer.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
GR5000 said:
When the phone is off, if I turn it on it just hangs at the animated X.
When the phone is off, if I press volume up/down + power then yes I see the screen that you're talking about. So I can boot into fastboot. When I choose Recovery Mode it restarts and that's when I get the No Command error.
Thank you so much for your help.
GR
Click to expand...
Click to collapse
Install the correct ADB and fastboot drivers and files on your PC (I can't help you with this).
When your GNex is in fastboot, connect it to your PC, wait for it to get recognized.
Download CWM recovery here: http://www.clockworkmod.com/rommanager - you'll have to choose your device variant (GSM/Verizon/Sprint), and choose if you want touch or not. Downloaded file should be an *.img file.
Open a command prompt window on your PC, enter "fastboot flash recovery *PATH-TO-YOUR-RECOVERY*.img" (no quotes). After flashing completes, just boot into recovery and do what you should do.
Sent from Google Nexus 4 @ CM11
Just want to thank everyone for all of the help. I really appreciate it. Andy, I did try several of the steps that you mentioned but for some reason the PC just wouldn't recognize the phone in fastboot mode. I tried both the Google and Samsung drivers.
In my searching I found this post though:
http://forum.xda-developers.com/nexus-4/help/nexus-4-stock-recovery-command-issue-t2113478/page2
And realized that I should check samer's advice again. Turns out that I just wasn't pressing those two buttons in the correct sequence. I was doing it simultaneously and I guess you have to do it serially. At any rate was able to restore factory and now the phone is booting. Wow. What a pain. Still not sure what caused the phone to blow up in the first place.
At any rate really appreciate everyone's help.
Warm regards,
GR
AndyYan said:
Install the correct ADB and fastboot drivers and files on your PC (I can't help you with this).
When your GNex is in fastboot, connect it to your PC, wait for it to get recognized.
Download CWM recovery here: http://www.clockworkmod.com/rommanager - you'll have to choose your device variant (GSM/Verizon/Sprint), and choose if you want touch or not. Downloaded file should be an *.img file.
Open a command prompt window on your PC, enter "fastboot flash recovery *PATH-TO-YOUR-RECOVERY*.img" (no quotes). After flashing completes, just boot into recovery and do what you should do.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
Hello friends, im writing because today I screwed my nexus 5x downgrading from oreo to nougat because the phone was getting too hot and I was worried that it would have the famous bootlop.
I don't know what happened, but when I tried to enter the recovery after flashing it, following instructions, the recovery now have a flashing "no command" logo and force entering the bootloader mode Its impossible because the vol down key is damaged. Now everytime I restart the phone it goes straight to recovery mode.
Can I do something? this is the so called bootloop? there's another way to enter bootloader mode?
Thanks for answering
Psicovirus said:
Hello friends, im writing because today I screwed my nexus 5x downgrading from oreo to nougat because the phone was getting too hot and I was worried that it would have the famous bootlop.
I don't know what happened, but when I tried to enter the recovery after flashing it, following instructions, the recovery now have a flashing "no command" logo and force entering the bootloader mode Its impossible because the vol down key is damaged. Now everytime I restart the phone it goes straight to recovery mode.
Can I do something? this is the so called bootloop? there's another way to enter bootloader mode?
Thanks for answering
Click to expand...
Click to collapse
Hold Volume and Power Up while in the stock recovery aka "no command" screen. You should fully enter stock recovery now. You F you can boot up, then you can issue this command "adb reboot bootloader" while in Android and connected to a computer.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Hold Volume and Power Up while in the stock recovery aka "no command" screen. You should fully enter stock recovery now. You F you can boot up, then you can issue this command "adb reboot bootloader" while in Android and connected to a computer.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you for answering friend.
When I do the combo vol up and power, it just reboots to the bugging recovery.
If i try to start up in any way, it will go straight to recovery.
I just managed to enter a "download mode" but i don't know if that coul be useful.
Psicovirus said:
Thank you for answering friend.
When I do the combo vol up and power, it just reboots to the bugging recovery.
If i try to start up in any way, it will go straight to recovery.
I just managed to enter a "download mode" but i don't know if that coul be useful.
Click to expand...
Click to collapse
Connect it to your computer and try to do adb reboot bootloader from the "no command" screen.
Nicktheprofessor said:
Connect it to your computer and try to do adb reboot bootloader from the "no command" screen.
Click to expand...
Click to collapse
Hey friend.
In recovery mode, the pc doesn´t recognize the phone at all, so I cannot reboot to bootloader.
Thanks for answering.
Psicovirus said:
Hey friend.
In recovery mode, the pc doesn´t recognize the phone at all, so I cannot reboot to bootloader.
Thanks for answering.
Click to expand...
Click to collapse
Something has gone seriously wrong here, you can't even use the LGUP tool to recover from whatever happened there I suspect. I think your best bet would be to open it up (unless it's under warranty) and short the vol down button to get into bootloader mode.
Nicktheprofessor said:
Something has gone seriously wrong here, you can't even use the LGUP tool to recover from whatever happened there I suspect. I think your best bet would be to open it up (unless it's under warranty) and short the vol down button to get into bootloader mode.
Click to expand...
Click to collapse
I just used LGUP tool and phone is in Google logo for too long, shutted it off so it can cool down (LGUP relocks bootloader?)
Thanks for the suggestion!!
Edit: Now the phone is stuck at google logo, should i wait for it to boot or assume it is damaged?
Psicovirus said:
I just used LGUP tool and phone is in Google logo for too long, shutted it off so it can cool down (LGUP relocks bootloader?)
Thanks for the suggestion!!
Edit: Now the phone is stuck at google logo, should i wait for it to boot or assume it is damaged?
Click to expand...
Click to collapse
Is it recognized at all by the computer? I really know nothing about Windows and how this works on Windows so perhaps someone else who does can help you.
If you have access to Linux, is it present in /dev/block?
Nicktheprofessor said:
Is it recognized at all by the computer? I really know nothing about Windows and how this works on Windows so perhaps someone else who does can help you.
If you have access to Linux, is it present in /dev/block?
Click to expand...
Click to collapse
No, it can't be recognized by my pc, but i can still get to download mode, i think the problem it that the tot file that is available, is from an earlier version from android an it doesn't include several partitions, so the bootloader (now locked) doesn't let it start up, i think the solution is try to get to recovery or bootloader and sideload an recent OTA file, but i don't know if i can because i can't get to recovery.
There's any way in which i can get to install a more recent image via download mode?
Any suggestion is welcome, thanks to you all.
Psicovirus said:
No, it can't be recognized by my pc, but i can still get to download mode, i think the problem it that the tot file that is available, is from an earlier version from android an it doesn't include several partitions, so the bootloader (now locked) doesn't let it start up, i think the solution is try to get to recovery or bootloader and sideload an recent OTA file, but i don't know if i can because i can't get to recovery.
There's any way in which i can get to install a more recent image via download mode?
Any suggestion is welcome, thanks to you all.
Click to expand...
Click to collapse
Well you can't sideload anything without getting into recovery and it doesn't sound to me that you used a correct file if it has fewer partitions.
There are probably .tot files floating around if you search this N5X forum, or you might be able to find one here: http://www.lgbbs.com.cn/forum-109-1.html
Best of luck.
Nicktheprofessor said:
Well you can't sideload anything without getting into recovery and it doesn't sound to me that you used a correct file if it has fewer partitions.
There are probably .tot files floating around if you search this N5X forum, or you might be able to find one here: http://www.lgbbs.com.cn/forum-109-1.html
Best of luck.
Click to expand...
Click to collapse
Sorry for the inconvenience, but i've installed the only tot file that there is around. I have been reading and here in the forum, people says that "This TOT file only contains GPT partition table, boot, recovery, system, modem", and we need to flash a full factory image so the rest of the partitions are in the same page. do you think that with LGUP's option "Upgrade FOTA" i can achieve this?
Many thanks in advance.
Psicovirus said:
Sorry for the inconvenience, but i've installed the only tot file that there is around. I have been reading and here in the forum, people says that "This TOT file only contains GPT partition table, boot, recovery, system, modem", and we need to flash a full factory image so the rest of the partitions are in the same page. do you think that with LGUP's option "Upgrade FOTA" i can achieve this?
Many thanks in advance.
Click to expand...
Click to collapse
What that tells you is that you now have a GPT that is correct and you can now fastboot flash a correct image BUT it has replaced your recovery which should allow you to enter recovery properly.
From there you can sideload a full OTA image that will restore the other partitions.
Oh an don't worry, if I stop responding I'm trying to find something and if I cannot help you further I'll just tell you that.
Nicktheprofessor said:
What that tells you is that you now have a GPT that is correct and you can now fastboot flash a correct image BUT it has replaced your recovery which should allow you to enter recovery properly.
From there you can sideload a full OTA image that will restore the other partitions.
Oh an don't worry, if I stop responding I'm trying to find something and if I cannot help you further I'll just tell you that.
Click to expand...
Click to collapse
I didn't quite catch that, what I should do now? my phone still doesn't want to enter recovery mode, and bootloader is out of the picture for now because the broken button.
Should i try to flash the OTA via the "FOTA UPGRADE" option from LGUP?.
Im grateful that you are taking the time to answering me.
Edit: Tried to install the OTA via LGUP and gives error, so is a no.
Edit2: Seems like i screwed up stalling stock recovery on top of twrp, sahme on me. How can i short the volume down button?
Psicovirus said:
I didn't quite catch that, what I should do now? my phone still doesn't want to enter recovery mode, and bootloader is out of the picture for now because the broken button.
Should i try to flash the OTA via the "FOTA UPGRADE" option from LGUP?.
Im grateful that you are taking the time to answering me.
Edit: Tried to install the OTA via LGUP and gives error, so is a no.
Click to expand...
Click to collapse
Reboot to recovery, use adb to sideload the OTA.
Reply to edit2: open it up, find the leads on the circuit board that go up to the vol down circuit breaker, use two needles and insert them into the solder where the breaker connects and while crossing the needles so they connect push power.
OR, fix the broken breaker, most of the time it's just a broken off brass dome that needs realigning, you'll need to fixate it which is just a needle's head worth of superglue on one side and a soldering on the other side (reflowing by heating the dome with a soldering iron usually works).
Your problem was that your recovery was shot, it should now be restored since that partition along with the GPT (the partition table) has been rewritten when you flashed the TOT file.
If you still cannot enter recovery or use adb reboot bootloader from whatever stage you can get into you'll have to open it up and short out the leads to vol down to get it into bootloader but even then you're probably SOL since it sounds like your emmc isn't working correctly. That is a hardware error though so depending on where you live that might buy you another two years of warranty.
Nicktheprofessor said:
Reboot to recovery, use adb to sideload the OTA.
Your problem was that your recovery was shot, it should now be restored since that partition along with the GPT (the partition table) has been rewritten when you flashed the TOT file.
If you still cannot enter recovery or use adb reboot bootloader from whatever stage you can get into you'll have to open it up and short out the leads to vol down to get it into bootloader but even then you're probably SOL since it sounds like your emmc isn't working correctly. That is a hardware error though so depending on where you live that might buy you another two years of warranty.
Click to expand...
Click to collapse
Friend, what is SOL? how do you know it is a emmc error if it was me that damaged the software? I cannot enter recovery, so ill try the short, any recommendation tha you can give me about that?
Psicovirus said:
Friend, what is SOL? how do you know it is a emmc error if it was me that damaged the software? I cannot enter recovery, so ill try the short, any recommendation tha you can give me about that?
Click to expand...
Click to collapse
SOL=Sh*t Out of Luck.
You flashed a tot file that rewrite the partition table (GPT) as well as installed a recovery partition and the stock recovery (whatever version it was should work fine). That it didn't tells me that something is awry with your emmc.
See my edit of my previous post, shorting it out is a piece of cake, fixing the breaker is a bit more work but if you have a soldering iron and super glue as well as a steady hand and good eye sight you'll be able to fix it.
Don't go nuts with the superglue though, as I said, a needles head worth is plenty. You'll know what I'm talking about regarding the brass dome (sometimes it's copper and sometimes it's zink, zink doesn't work with the superglue so you'll have to use special glue for that) when you see it, it's like a little dome resting on top of the leads, pushing it down shorts them out.
I'd do the needle thing first though, just to see if it works at all, no need fixing the button if the emmc is dead.
Nicktheprofessor said:
SOL=Sh*t Out of Luck.
You flashed a tot file that rewrite the partition table (GPT) as well as installed a recovery partition and the stock recovery (whatever version it was should work fine). That it didn't tells me that something is awry with your emmc.
See my edit of my previous post, shorting it out is a piece of cake, fixing the breaker is a bit more work but if you have a soldering iron and super glue as well as a steady hand and good eye sight you'll be able to fix it.
Don't go nuts with the superglue though, as I said, a needles head worth is plenty. You'll know what I'm talking about regarding the brass dome (sometimes it's copper and sometimes it's zink, zink doesn't work with the superglue so you'll have to use special glue for that) when you see it, it's like a little dome resting on top of the leads, pushing it down shorts them out.
I'd do the needle thing first though, just to see if it works at all, no need fixing the button if the emmc is dead.
Click to expand...
Click to collapse
Im trying to do that, i already have the phone open, sewing needles will do?
Psicovirus said:
Im trying to do that, i already have the phone open, sewing needles will do?
Click to expand...
Click to collapse
Anything with a sharp point made of metal will do, as long as you can penetrate the solder with the tip and get a lead it will work.
All you need is to short it out for a few seconds while you use the power button to enter bootloader.
My guess is that you won't be able to enter the bootloader mode either though. The bootloader is read from a partition on the emmc.
I really hope you do prove me wrong on this though, that would be awesome.
Nicktheprofessor said:
Anything with a sharp point made of metal will do, as long as you can penetrate the solder with the tip and get a lead it will work.
All you need is to short it out for a few seconds while you use the power button to enter bootloader.
My guess is that you won't be able to enter the bootloader mode either though. The bootloader is read from a partition on the emmc.
I really hope you do prove me wrong on this though, that would be awesome.
Click to expand...
Click to collapse
I tried that and didn't work, but maybe im doing something wrong, the sadness hit me hard and I rather try again when im more clear headed.
I still fail to see how the emmc is failing, should have entered recovery mode more easily? Flashing software somehow made it more prone to fail?
Many thanks, friend, you've been really helpful.
Psicovirus said:
I tried that and didn't work, but maybe im doing something wrong, the sadness hit me hard and I rather try again when im more clear headed.
I still fail to see how the emmc is failing, should have entered recovery mode more easily? Flashing software somehow made it more prone to fail?
Many thanks, friend, you've been really helpful.
Click to expand...
Click to collapse
You can use a q tip and some acetone to clear eventual lacquer from the solder points but the thing is, it's probably the emmc that is shot.
Your emmc obviously doesn't accept what the recovery the LGUP wrote to it. If it did, you'd be flashing the OTA right now. Why? I have no idea, I'd need to take the phone to the lab to examine what caused the degradation and even then I probably couldn't tell you much more about the actual cause.
And don't worry about it, your case is interesting and not easy to solve by simply doing a search, you weren't an arse about anything either and that is unusual and welcome.
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
If it still boots into the boot loader you're fine and fixable.
Phalanx7621 said:
If it still boots into the boot loader you're fine and fixable.
Click to expand...
Click to collapse
Well that's good news at least!
What can I do?
Prosis said:
Well that's good news at least!
What can I do?
Click to expand...
Click to collapse
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Phalanx7621 said:
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Prosis said:
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Click to expand...
Click to collapse
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Phalanx7621 said:
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Click to expand...
Click to collapse
Yeah I tried that but the dead android never appears. It reacts the same way it does when I try to boot into the system, which is just a white flicker that appears and disappears on the top of the screen. It's like it's trying to load the white screen with the Google logo but it can't.
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Phalanx7621 said:
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Click to expand...
Click to collapse
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Prosis said:
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Click to expand...
Click to collapse
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Phalanx7621 said:
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Click to expand...
Click to collapse
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Prosis said:
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Click to expand...
Click to collapse
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Phalanx7621 said:
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Click to expand...
Click to collapse
Yeah I did. I even tried several tools that are supposed to be able to help but without having Allow OEM Unlock enabled nothing works :/
After maybe 2 hours left alone charging now it's not even booting into the booloader anymore...
Are you going to be able to RMA it? Is it still under warranty?
Phalanx7621 said:
Are you going to be able to RMA it? Is it still under warranty?
Click to expand...
Click to collapse
I'm waiting for my seller to give me the original order number (which seems like forever right now given the situation). Then Google will be able to tell me if it's still under warranty. If not then, according to the authorized repair center, it's either the battery, the port or the motherboard which means it's probably the end for this phone as prices range from less than $100 to nearly $400. :crying:
Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Homeboy76 said:
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Click to expand...
Click to collapse
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Prosis said:
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Click to expand...
Click to collapse
Good news! I got an RMA!!
Thanks for your help everyone!
Hello,
This is the third time I've asked you for help. This time it is, it always concerns google pixel C. Everything worked so well. But today, by simply taking a picture, the device turns off and on again on the google logo. Then the android robot with a red alert appears. the word "No command" just below. I can navigate the recovery. But impossible to go into "android recovery" with the menus to apply sideload ota.... I sincerely think it is brick and I'm really very afraid that I won't be able to use the guarantee despite having locked the bootloader before. I was on the official Android 7.1.2 software. The adb and fastboot commands detect the tablet. But I can't unlock the bootloader or flash... I have no idea what to do, I could use your help please!!!!!!!!
Hawkeye5 said:
Hello,
This is the third time I've asked you for help. This time it is, it always concerns google pixel C. Everything worked so well. But today, by simply taking a picture, the device turns off and on again on the google logo. Then the android robot with a red alert appears. the word "No command" just below. I can navigate the recovery. But impossible to go into "android recovery" with the menus to apply sideload ota.... I sincerely think it is brick and I'm really very afraid that I won't be able to use the guarantee despite having locked the bootloader before. I was on the official Android 7.1.2 software. The adb and fastboot commands detect the tablet. But I can't unlock the bootloader or flash... I have no idea what to do, I could use your help please!!!!!!!!
Click to expand...
Click to collapse
Have you tried this?
"Turn off GOOGLE PIXEL C. Press and hold together : Power Button + Volume Down until Logo appear at LCD screen. If we see the menu at LCD screen, choose Wipe Data/Factory Reset with Volume Button to select and use Power Button to ok or enter."
Are you sure I can do that? Because I had downgraded Android from version 8.1.0 to 7.1.2 because I had a problem with 8.1.0. Therefore I had unlocked the bootloader etc.... So the data had been erased! If I do a wipe data/Factory reset will it work at least at 90/95% ? Despite having only installed the Factory image (without OTA) can it work without doing a bootloop or other...?
braunie said:
Have you tried this?
"Turn off GOOGLE PIXEL C. Press and hold together : Power Button + Volume Down until Logo appear at LCD screen. If we see the menu at LCD screen, choose Wipe Data/Factory Reset with Volume Button to select and use Power Button to ok or enter."
Click to expand...
Click to collapse
Well, I tried and I always fall back on the page with the robot and the inscription "no command" just below. I'm sad ?
If the bootloader is unlocked you maybe have a chance by install TWRP and then install LineageOS 15.1 (wich is much better than stock).
braunie said:
If the bootloader is unlocked you maybe have a chance by install TWRP and then install LineageOS 15.1 (wich is much better than stock).
Click to expand...
Click to collapse
The bootloader is locked. This is the end. Is there any advice I can try to send it to the after-sales service?
braunie said:
If the bootloader is unlocked you maybe have a chance by install TWRP and then install LineageOS 15.1 (wich is much better than stock).
Click to expand...
Click to collapse
Tell me, the OTA file is used to apply an update, right? Because I tried to do this manipulation but by downloading Exactly the same software and it didn't work. So if I try with a more recent version of Android, it should work, right?
Hawkeye5 said:
Tell me, the OTA file is used to apply an update, right? Because I tried to do this manipulation but by downloading Exactly the same software and it didn't work. So if I try with a more recent version of Android, it should work, right?
Click to expand...
Click to collapse
Sorry, but I don't know this. If the bootloader is locked I have no further idea.
Maybe somebody else has an idea???
braunie said:
Sorry, but I don't know this. If the bootloader is locked I have no further idea.
Maybe somebody else has an idea???
Click to expand...
Click to collapse
Okay, I found the solution. The OTA image had to be installed. I am happy. Everything seems to be working for now. And yes, the ota image can be installed without unlocking the bootloader!
Perfect!
---------- Post added at 03:20 PM ---------- Previous post was at 03:20 PM ----------
Hawkeye5 said:
Okay, I found the solution. The OTA image had to be installed. I am happy. Everything seems to be working for now. And yes, the ota image can be installed without unlocking the bootloader!
Click to expand...
Click to collapse
So I may ask you for help if I have the same problem
Hawkeye5 said:
Okay, I found the solution. The OTA image had to be installed. I am happy. Everything seems to be working for now. And yes, the ota image can be installed without unlocking the bootloader!
Click to expand...
Click to collapse
How did you fix it
I had the same exact same fault in December and couldn't work out how to fix. I thought my tablet was just a paperweight now but would be so happy if i could fix it.
do you have a link to the method you used or can you provide more details on how to fix?
what do you mean by the OTA image had to be installed?
Each time I tried to copy the image from my computer to the tablet it failed.
would be grateful for any help.
thanks
Jmash79 said:
How did you fix it
I had the same exact same fault in December and couldn't work out how to fix. I thought my tablet was just a paperweight now but would be so happy if i could fix it.
do you have a link to the method you used or can you provide more details on how to fix?
what do you mean by the OTA image had to be installed?
Each time I tried to copy the image from my computer to the tablet it failed.
would be grateful for any help.
thanks
Click to expand...
Click to collapse
Hi, if your device is a C pixel, you can try to check it out here: https://developers.google.com/android/ota
To sum up, my problem was the following: suddenly, my tablet could no longer boot on android but on the page where the robot was displayed with a red panel and the indication "no command".
And the solution was the following: being on Android 7.1.2 I had to download Android 8.1.0 for the "update" to work. So I followed all the steps indicated by the site I provided you. That is, having Fastboot and adb working, then putting the.Zip file of your android in the same folder as adb and Fastboot. Then you follow the different steps shown on the site to download the ota image. My explanation is not great so if you have a question about something specific let me know. And if you can send screenshots of your worries it will help.
Good luck with that!
Jmash79 said:
How did you fix it
I had the same exact same fault in December and couldn't work out how to fix. I thought my tablet was just a paperweight now but would be so happy if i could fix it.
do you have a link to the method you used or can you provide more details on how to fix?
what do you mean by the OTA image had to be installed?
Each time I tried to copy the image from my computer to the tablet it failed.
would be grateful for any help.
thanks
Click to expand...
Click to collapse
Hi, if your device is a C pixel, you can try to check it out here: https://developers.google.com/android/ota
To sum up, my problem was the following: suddenly, my tablet could no longer boot on android but on the page where the robot was displayed with a red panel and the indication "no command".
And the solution was the following: being on Android 7.1.2 I had to download Android 8.1.0 for the "update" to work. So I followed all the steps indicated by the site I provided you. That is, having Fastboot and adb working, then putting the.Zip file of your android in the same folder as adb and Fastboot. Then you follow the different steps shown on the site to download the ota image. My explanation is not great so if you have a question about something specific let me know. And if you can send screenshots of your worries it will help.
Good luck with that!
Translated with www.DeepL.com/Translator
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