Hi Guys.
I replaced a screen of a D5503. Knew the pattern to unlock the phone (friends) but messed up and thought it does not matter if it resets to factory settings after 7 attempts.. But Bootloop. Country choice appears shortly and screen goes to grey. Repair with companion gives no change. Sometimes it is possible to select country and go one screen further and then it goes grey again. Is this bootloop ?
searched web and forum for similar problems and decided finally it must be bootloop?
Of course i did not make a back up.. phone is coupled to google account of friend , so if I can get the screen to normalize and not disappear that would also be an option.
i downloaded Flashtool Emma. Most links are dead. For neccesary files, unlocking etc.
I have a sony unlock code.
(locked bootloader)
The firmware is (1279-1792) 14.6A.1.236-R2D
Can anybody direct me to the right link to follow ?
Or commands are not downloadable anymore, or I don't know what tft file to use etc.
Can anybody direct me in the right direction ? Please?
Help is appreciated. I flashed and rooted a Z1 mini once before. years back.
If you can flash stock firmware with sony compagnon with sucess 100%, it means that it's not a firmware problem.
Are you sure new screen is good? Did you replace touchscreen and LCD or only one of them?
did you test with old screen to check if system boot is ok?
I replaced both in one. Screen with digitizer asssembly. And initially the phone booted fine to lockscreen with pattern. So screen is working fine.
I messed up trying 7 times the pattern upon which the phone by itsself booted to factory settings. Since then the phone is stuck. I tried repair with companion but that made no difference.
But the adb commands to unlock bootloader don't seem to be downloadable anymore. Not even from the link provided from the sony site. from which I optained the unlock key.
Can you boot phone in recovery mode ?
foxyone0809 said:
Can you boot phone in recovery mode ?
Click to expand...
Click to collapse
Yes ; if I hold the volume button up when phone is powered off, and connect the usb to the phone the powerled goes blue and the pc gives a messaga that fastboot is on. Phonescreen stays black.
pinkeltje2 said:
Yes ; if I hold the volume button up when phone is powered off, and connect the usb to the phone the powerled goes blue and the pc gives a messaga that fastboot is on. Phonescreen stays black.
Click to expand...
Click to collapse
I don't talk about fastboot mode.
I talk about stock recovery mode, where you can reset system to factory
foxyone0809 said:
I don't talk about fastboot mode.
I talk about stock recovery mode, where you can reset system to factory
Click to expand...
Click to collapse
If the phone boots up, for a second the language choice screen pops up and screen goes to grey. I cannot acces anything on the phone itsself.
pinkeltje2 said:
If the phone boots up, for a second the language choice screen pops up and screen goes to grey. I cannot acces anything on the phone itsself.
Click to expand...
Click to collapse
Do you know the keys to boot automatic in recovery mode ?
foxyone0809 said:
Do you know the keys to boot automatic in recovery mode ?
Click to expand...
Click to collapse
well, it should be volume up and power button. But that only gets me to fastboot. No lights blincking at the supposed ledlight at all.
So the screen freezes at language choice page. that only appears shortly. sometimes just long enough to make a choice and then the screen goes grey. The only option to communicate seems to be fastboot. Since the pc recognices the phone as being in fastboot.
So how to proceed ?
pinkeltje2 said:
well, it should be volume up and power button. But that only gets me to fastboot. No lights blincking at the supposed ledlight at all.
So the screen freezes at language choice page. that only appears shortly. sometimes just long enough to make a choice and then the screen goes grey. The only option to communicate seems to be fastboot. Since the pc recognices the phone as being in fastboot.
So how to proceed ?
Click to expand...
Click to collapse
Try to flash firmware.tft file with flashtool for xperia devices
It seems you have lock bootloader.
---------- Post added at 04:07 PM ---------- Previous post was at 04:02 PM ----------
http://www.flashtool.net/downloads.php
Or
https://github.com/Androxyde/Flashtool
Here is a list of FTF files of official firmwares for the Sony Z1c:
https://boycracked.com/2019/10/08/official-sony-xperia-z1-compact-d5503-stock-rom-ftf-for-flashtool/
Latest version ever released is 14.6.A.1.236; Download a FTF and flash it with Flashtool from www.flashtool.net;
Make sure the ticks to wipe data and cache are enabled when you flash the firmware.
marsa47 said:
Here is a list of FTF files of official firmwares for the Sony Z1c:
https://boycracked.com/2019/10/08/official-sony-xperia-z1-compact-d5503-stock-rom-ftf-for-flashtool/
Latest version ever released is 14.6.A.1.236; Download a FTF and flash it with Flashtool from www.flashtool.net;
Make sure the ticks to wipe data and cache are enabled when you flash the firmware.
Click to expand...
Click to collapse
Tnx. back when this was still somewhat a current model I knew what version it contained and with patience I rooted and flashed a X1c. Got a Flashtool download now branded Emma. . Looks weird in my eyes. But the .net page gives a virus error in the torrentfiles still being used in those days. Hence my loss. ? Emma version did give detailed info about the phone and the firmware and that bootloader is locked. Then can get unlock key from sony site, but adb files I can't get. And when I finallly can get them I am asked for admistrator password,. My stupid attempt to make an offline non google account pc, the other way around. And while only a few days ago I forgot that password hahaha. Dont't ask. strangers in tha house Gonna see if I have the old files still on the old brick (pc) and see if I can manage from there. -) tnx for answering and patience. I have a few bricks. maybe first create a dualboot. and be sure.
I'll report back if I get that old fart to life again thanks to your input.
Thanks again and enjoy and have fun
pinkeltje2 said:
Tnx. back when this was still somewhat a current model I knew what version it contained and with patience I rooted and flashed a X1c. Got a Flashtool download now branded Emma. . Looks weird in my eyes. But the .net page gives a virus error in the torrentfiles still being used in those days. Hence my loss. ? Emma version did give detailed info about the phone and the firmware and that bootloader is locked. Then can get unlock key from sony site, but adb files I can't get. And when I finallly can get them I am asked for admistrator password,. My stupid attempt to make an offline non google account pc, the other way around. And while only a few days ago I forgot that password hahaha. Dont't ask. strangers in tha house Gonna see if I have the old files still on the old brick (pc) and see if I can manage from there. -) tnx for answering and patience. I have a few bricks. maybe first create a dualboot. and be sure.
I'll report back if I get that old fart to life again thanks to your input.
Thanks again and enjoy and have fun
Click to expand...
Click to collapse
So ? Do you succeed to boot system ?
This guy seams to be mad.... Lol
Related
Hi Guys
So heres what happened. I rooted my phone and installed the Beats Audio Driver from the Fantastic Audio Installer by motioncoding from the play store. It came to my understanding that the beats driver did not properly install. I opened the app and pressed install and the phone is now in a constant boot loop This is where the phone can boot into the lockscreen but then it automatically restarts and the whole cycle repeats over and over again.
Currently i can only get my phone into flash mode but not fastboot.
-The phone has had its network unlocked. 2 days ago i typed in a network unlock pin into the phone
-The sony flashtool (emma) doesnt work because i have a unlockable bootloader
-I did not install CWM because i only rooted my phone 3 hours ago and i did not know at the time
Does anyone know if flashtool by bin4ry will help me get out of the bootloop in my case
Thanks
itsbighead said:
Hi Guys
So heres what happened. I rooted my phone and installed the Beats Audio Driver from the Fantastic Audio Installer by motioncoding from the play store. It came to my understanding that the beats driver did not properly install. I opened the app and pressed install and the phone is now in a constant boot loop This is where the phone can boot into the lockscreen but then it automatically restarts and the whole cycle repeats over and over again.
Currently i can only get my phone into flash mode but not fastboot.
-The phone has had its network unlocked. 2 days ago i typed in a network unlock pin into the phone
-The sony flashtool (emma) doesnt work because i have a unlockable bootloader
-I did not install CWM because i only rooted my phone 3 hours ago and i did not know at the time
Does anyone know if flashtool by bin4ry will help me get out of the bootloop in my case
Thanks
Click to expand...
Click to collapse
Yes. It will save your phone.
skywalkerdroid said:
Yes. It will save your phone.
Click to expand...
Click to collapse
do i have to wipe my phone or can i just revert the system folder back to original?
itsbighead said:
do i have to wipe my phone or can i just revert the system folder back to original?
Click to expand...
Click to collapse
It's best to wipe everything in this case, wipe dalvik's cache too, make a clean install.
itsbighead said:
Hi Guys
So heres what happened. I rooted my phone and installed the Beats Audio Driver from the Fantastic Audio Installer by motioncoding from the play store. It came to my understanding that the beats driver did not properly install. I opened the app and pressed install and the phone is now in a constant boot loop This is where the phone can boot into the lockscreen but then it automatically restarts and the whole cycle repeats over and over again.
Currently i can only get my phone into flash mode but not fastboot.
-The phone has had its network unlocked. 2 days ago i typed in a network unlock pin into the phone
-The sony flashtool (emma) doesnt work because i have a unlockable bootloader
-I did not install CWM because i only rooted my phone 3 hours ago and i did not know at the time
Does anyone know if flashtool by bin4ry will help me get out of the bootloop in my case
Thanks
Click to expand...
Click to collapse
Just use flashtool with flashmode....
1.Press lightning icon on flashtool and select your rom.....
2.If you want to keep your data uncheck it in the selection menu.
3.Switch off your phone.Plug your phone with volume down key pressed..A green led should light up and flashtool will show your device
connected...
4. Flashing would start....
5.Wait for the rom to be flashed...
6. Device will reboot and it could take upto 2-5 mins approx..
THAT'S IT.....YOU NOW HAVE YOUR PHONE AS IT WAS..:highfive:
AND LET ME KNOW PLS..
HIT THANKS IF I HELPED YOU
A CLICK FOR YOU BUT REP FOR ME.......
XPERIA LT 26I
ROOTED WITH LOCKED BL...
Just to clarify to anyone who reads this thread in the future, you can use flashtool by bin4ry to unbrick your phone
1.Press lightning icon on flashtool and select your rom.....
2.If you want to keep your data uncheck it in the selection menu.
3.Switch off your phone. Plug your phone with volume down key pressed..A green led should light up and flashtool will show your device connected...
4. Flashing would start....
5. The device will reboot and the orange light will light up
6. Unplug the USB Cable and plug in your phone with volume down key pressed. A green led should light up and flashtool will show your device connected...
6.Wait for the rom to be flashed...
7. Device will reboot and it could take upto 2-5 mins approx..
Yeah ? LOL We know that already, your post is off topic, he knows how to flash, as we all do, his question was, well read again his post.Don't come in here and give us lessons on how to flash, smart ass. Are you clarified now?
skywalkerdroid said:
Yeah ? LOL We know that already, your post is off topic, he knows how to flash, as we all do, his question was, well read again his post.Don't come in here and give us lessons on how to flash, smart ass. Are you clarified now?
Click to expand...
Click to collapse
thank you everyone for your help. I got it fixed and i installed cwm recovery before doing anything else
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 was so excited to buy a Z5 quite cheap from online store (GumTree Australia). Received it and went to turn it on, it was locked to someone's account (not the last owner I assumed). No biggee I thought, so I did a bit of research to find out how to factory reset wipe my phone and find the Sony app 'EMMA'. Booted my phone into that app and it showed that this phone was locked and I couldn't do anything other than visit a couple links it suggested to update my phone or contact Sony to unlock my bootloader. I did all that it suggested waiting on Sony to no reply.
3 months later, I decided to give this phone another go and came looking at XDA. Impatiently wanting to unlock, I found a flashtool on XDA https://forum.xda-developers.com/z5-premium/general/firmware-32-3-0-372-certified-android-7-t3537948 and decided to wing it with this image https://redirect.viglink.com/?format=go&jsonp=vglnk_14958424411279&key=f0a7f91912ae2b52e0700f73990eb321&libId=j36hx1cx01000n4o000DAnhl9jzwv&loc=https%3A%2F%2Fforum.xda-developers.com%2Fz5-premium%2Fgeneral%2Ffirmware-32-3-0-372-certified-android-7-t3537948&v=1&out=https%3A%2F%2Fdrive.google.com%2Fdrive%2Ffolders%2F0B9es25_rAF5bbnhPZ2pLQjQyd2M%3Fusp%3Dsharing&ref=https%3A%2F%2Fforum.xda-developers.com%2Fz5-premium&title=Firmware%20Android%20N%207.0%2032.3.A.2.33%20link%20.ftf%E2%80%A6%20%7C%20Sony%20Xperia%20Z5%20Premium&txt=https%3A%2F%2Fdrive.google.com%2Fdrive%2Ffolde...2M%3Fusp%3Dsharing.
Long story short, my impatience and winging it after following onscreen instructions from the tool has now made the phone unbootable. Screen turns on but it's all black. I plug my phone in to the computer and it is recognised by EMMA and Windows. But I can't do the recovery boot with volume down.
I just want to put it back to how it was with a simple wipe. Is there a way I can get it back to just "normal" please.
My excitement has now left me with anxiety issues lol. Please help....
Use flashtool and go to XperiFirm and download the full ROM by browsing to the correct phone model and country (Use somewhere like Custom Indonesia, Custom UK, Custom Germany, etc.)
Then simply click flash button, choose the ROM, make some checkbox such that it flashes absolutely everything, and then follow on-screen instruction to do a full flash. Volume Up and Power force turns your phone off, and then plug the USB and press the instructed volume button right away to enter into flash mode, and then things will work on its own.
I would just use XperiFirm to download the ROM image. But do make sure you're downloading the ROM for the correct phone model.
DarkSilentSC said:
Then simply click flash button, choose the ROM, make some checkbox such that it flashes absolutely everything, and then follow on-screen instruction to do a full flash. Volume Up and Power force turns your phone off, and then plug the USB and press the instructed volume button right away to enter into flash mode, and then things will work on its own.
I would just use XperiFirm to download the ROM image. But do make sure you're downloading the ROM for the correct phone model.
Click to expand...
Click to collapse
Life saver!! Thank you so much. I've got the phone working now and I understand how XperiFirm works.... sort of.
I'm now stuck on FRP lock where I have to enter the last email used to sync the device. I've tried the instructions from this thread and watched the video and mine doesn't do what is shown on the video to get into the settings to switch users.
https://forum.xda-developers.com/z5-premium/general/how-to-tottaly-unlock-xperia-z5-premium-t3585640#post72448042
I'm gonna keep reading and see if there's another way around. But if anyone is reading this, please feel free to guide me.
Thanking you DarkSilent again.
UPDATE
Found this video and it helped me to bypass FRP.
Thank you once again. I'm very happy now.
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!
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