Related
Well I decided to sell this Atrix HD I just recently acquired and of course because I have no luck at all not even 5 mins after posting the ad on craigslist I ended up potentially bricking it, sadly. I've spent the better part of the past 2 hours scouring threads and posts hoping for a solution but so far I've had no luck so I'll take this last step and ask if anyone might have any advice or solutions. Here's the situation:
- Atrix HD, originally with JB 4.1.1 on it (pre-final AT&T update, mind you)
- rooted with motochopper then bootloader unlocked with motopocalypse, no issues over the past 10 days or so that I've owned this AHD at all)
- was running CM11 nightly without issues (installed with CWM 6.0.5.1, had flashed several ROMs over the past 10 days including CM12, the Mexican retail ROM, and then back to pure AT&T several times, actually
- about 2 hours before making this post I listed it on craigslist and then used Myth Tools to go back to stock (stock being MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27)
- no issues with the flashing process, booted up as expected, worked fine for a few mins then I connected to Wi-Fi and grabbed the final JB update released by AT&T, when it finished I clicked "Install now" to do the reboot and install it
- rebooted into the install and seemed to finish ok, didn't glitch or error out in any respect
- somewhere in the middle of the final reboot after the upgrade it crapped out and then went into the bootloader loop to AP Fastboot (S) mode
- got the following error (which is known to a few other members in the past based on postings I located):
Code:
(typical info at the top of the screen)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup:0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
usb connected
As stated, this AHD was bootloader unlocked without any issues but for whatever is now showing as LOCKED. The thing that concerns me is that if I use fastboot devices it doesn't show the proper info as it used to (the typical TA00etcetcetc model number) - it's showing an 8 digit alphanumeric number I've never seen before so that's a big red flag right there.
I've attempted every process I can locate so far and had zero success at all - only one single fastboot command gives me an OKAY message and that's fastboot oem fb_mode_clear. Every other fastboot command offers up a FAILED (remote failure) error, all of them and I've tried pretty much all of them.
I cannot flash anything to the AHD it seems so I'm guessing that means it's 100% "bricked" in the sense that it's powering up, can be seen from the PC/laptop using fastboot devices, but that's it just not actually there at all for whatever reason.
I've attempted to use 2 different laptops, 1 desktop, multiple various USB ports, cables, you name it I'm pretty confident I've attempted to use it in some respect and still nada, zip, zilch, nothing has come from my efforts. If it's totally bricked then so be it, I'll live, but I keep holding out hope that something I missed will help but it's starting to look like this is beating a dead horse now.
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
So apparently for whatever reason the final JB update pooched this device (even in spite of it not doing it in the past week when I rolled back to stock at least 3 prior times in testing). I'm suspecting - but can't say for certain - that potentially the CWM 6.0.5.1 which I just installed like 2 days ago could be the culprit here; previously using 6.0.4.4 I had no issues whatsoever and that is the only variable that's changed in my flashing process that I can recall.
Anyway, that pretty much covers the situation - if anyone has any advice that might bring this AHD back to life I'm definitely interested in hearing it. I don't have JTAG hardware, don't have a factory cable (if one is required), don't have anyone in the area that does that I'm aware of, etc. Basically if I can't get it resolved on my own then it's a dead device I'll toss in a drawer till that miracle comes along...
Thanks for reading, regardless.
br0adband said:
Well I decided to sell this Atrix HD I just recently acquired and of course because I have no luck at all not even 5 mins after posting the ad on craigslist I ended up potentially bricking it, sadly. I've spent the better part of the past 2 hours scouring threads and posts hoping for a solution but so far I've had no luck so I'll take this last step and ask if anyone might have any advice or solutions. Here's the situation:
- Atrix HD, originally with JB 4.1.1 on it (pre-final AT&T update, mind you)
- rooted with motochopper then bootloader unlocked with motopocalypse, no issues over the past 10 days or so that I've owned this AHD at all)
- was running CM11 nightly without issues (installed with CWM 6.0.5.1, had flashed several ROMs over the past 10 days including CM12, the Mexican retail ROM, and then back to pure AT&T several times, actually
- about 2 hours before making this post I listed it on craigslist and then used Myth Tools to go back to stock (stock being MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27)
- no issues with the flashing process, booted up as expected, worked fine for a few mins then I connected to Wi-Fi and grabbed the final JB update released by AT&T, when it finished I clicked "Install now" to do the reboot and install it
- rebooted into the install and seemed to finish ok, didn't glitch or error out in any respect
- somewhere in the middle of the final reboot after the upgrade it crapped out and then went into the bootloader loop to AP Fastboot (S) mode
- got the following error (which is known to a few other members in the past based on postings I located):
Code:
(typical info at the top of the screen)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup:0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
usb connected
As stated, this AHD was bootloader unlocked without any issues but for whatever is now showing as LOCKED. The thing that concerns me is that if I use fastboot devices it doesn't show the proper info as it used to (the typical TA00etcetcetc model number) - it's showing an 8 digit alphanumeric number I've never seen before so that's a big red flag right there.
I've attempted every process I can locate so far and had zero success at all - only one single fastboot command gives me an OKAY message and that's fastboot oem fb_mode_clear. Every other fastboot command offers up a FAILED (remote failure) error, all of them and I've tried pretty much all of them.
I cannot flash anything to the AHD it seems so I'm guessing that means it's 100% "bricked" in the sense that it's powering up, can be seen from the PC/laptop using fastboot devices, but that's it just not actually there at all for whatever reason.
I've attempted to use 2 different laptops, 1 desktop, multiple various USB ports, cables, you name it I'm pretty confident I've attempted to use it in some respect and still nada, zip, zilch, nothing has come from my efforts. If it's totally bricked then so be it, I'll live, but I keep holding out hope that something I missed will help but it's starting to look like this is beating a dead horse now.
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
So apparently for whatever reason the final JB update pooched this device (even in spite of it not doing it in the past week when I rolled back to stock at least 3 prior times in testing). I'm suspecting - but can't say for certain - that potentially the CWM 6.0.5.1 which I just installed like 2 days ago could be the culprit here; previously using 6.0.4.4 I had no issues whatsoever and that is the only variable that's changed in my flashing process that I can recall.
Anyway, that pretty much covers the situation - if anyone has any advice that might bring this AHD back to life I'm definitely interested in hearing it. I don't have JTAG hardware, don't have a factory cable (if one is required), don't have anyone in the area that does that I'm aware of, etc. Basically if I can't get it resolved on my own then it's a dead device I'll toss in a drawer till that miracle comes along...
Thanks for reading, regardless.
Click to expand...
Click to collapse
Did you edit the script when flashing the stock JB with Mythtools or RSD lite?
Sent from my ATRIX-RAZR HD using XDA Free mobile app
Yep, it even states that in my post:
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
Click to expand...
Click to collapse
Nothing will flash to the device which is the biggest issue of all; if I could flash the gpt_main0.bin file I'd be getting somewhere (since as I understand it that sets the partition layout for the partition img's that will follow in the flashing process).
As stated, the only thing that works in terms of a fastboot command is fb_mode_clear which gets an OKAY response (although fb_mode_set does too, actually). But no other fastboot commands are functional - I tried fastboot -w and get:
Code:
D:\motopocalypse\motopocalypse>fastboot -w
erasing 'userdata'...
Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.140s
so then I try:
Code:
D:\motopocalypse\motopocalypse>fastboot erase userdata
erasing 'userdata'...
Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.141s
and so on and so forth. No attempts to erase data nor write it in any manner are successful. RSD Lite basically is useless as well (pic attached below). Since I can't write any data to the device at all then as I've said, it's dead in the water unless a miracle comes along. Was looking at eBay in the hopes of finding a busted/broken AHD (damaged glass, etc) and swapping the mobo from that one back into my housing but they're a bit expensive for busted ones at the moment, guess I'll just keep hoping for that miracle.
I've never used a JTAG or factory cable on any devices I've ever owned but I have to wonder if such a contraption might get this back to a working state. Suppose I'll need to do some research into things - I tried to contact Motorola about it but of course since the AHD is so old now and I'm not the original owner, even though I registered the device in my name they won't honor the warranty without a proof of purchase (meaning the retail one years ago when it was new).
Out of over 100 smartphones and other devices I've owned over the decades this is the first time one's actually up and died on me and go figure: it died when doing an OTA update on a clean stock ROM installation.
How ironic...
Have you tried this http://forum.xda-developers.com/showthread.php?t=2259661
Sent from my LG-D850 using XDA Free mobile app
bmatney said:
Have you tried this http://forum.xda-developers.com/showthread.php?t=2259661
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Yep, it's all the same basic process whether it's done scripted or manually, same result: as stated, nothing will flash to the AHD and kicks back the same error each time (partition errors). I have no idea what that damned OTA did but it totally wrecked the whole thing...
Even tried doing this under Linux - the issue isn't with fastboot or the builds, it's with the AHD itself because it's not writing anything I'm trying to flash to the device and I'm confident it's because the partition structure is pooched for whatever reason.
I'm still wondering about using a factory cable (will have to buy one off eBay I suppose) will make any difference at all, I just have no experience using them and if the phone isn't flashing/writing data to the device because the partitions are pooched, I can't imagine using a different albeit specific cable will make that much of a difference.
Bleh... I hate it when crap goes wrong, I really do.
Hey ,
seems like you guys are my last chance. I will try to explain my situation:
So today I was just messaging when suddenly some process.google.media (cant recall exactly) error was spamming my phone. I restarted the phone and then the problems started happening. The moto X was stuck in the boot screen.
I read that i should install TWRP and factory reset. So after doing that I was pretty much stuck in recovery.
Whenever i turned the phone on, It was immediately booting the TWRP.
So I thought fine, I will probably have to install a ROM, so it can actually boot something.
I went for the xt1052 Lollipop 5.1 untouched EU version of the forum. Still It somehow didnt boot.
Next I came across the following youtube video: youtube /watch? v=ne46LQ3n7nA
(cant post url)
Followed all the instructions in the video and it actually got my phone to work.
I thought that now everything would be just like when I bought my phone.
So I installed the official lollipop update which popped up on my screen.
And now Im stuck again...
Im sitting in Fastboot Mode and get the following error:
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
Dont know how many threads I read by now on here to find a solution but I cant find any..
I installed RSDLite, but Im not sure which version to use to flash now.
Tried two zip folders, but apparently the xml file was missing.
Im kinda scared to use the wrong zip anyways and screw my phone completely if it isnt already.
Id really appreciate any help since im currently clueless.
Thanks boys!
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
This is likely your problem and the result of flashing a lower version onto your Moto x. I would start looking how/if you can recover from a downgrade.
I might add some additional error description to make ppl find this thread in the future :
Stuck in bootloader - Fastboot - cant enter recovery - when choosing any options from fastboot: Load kernel (boot) failed
-----------------------------------------------------------------------------------------------------------------------------------------
Alright seems like i got it working again.
Since this forum helped me so much I want to contribute something to it by giving u guys my solution.
So I stumbled across alot of threads with @KidJoe replying. He really knows his stuff, when it comes to the MotoX.
I dont know how to quote off of other threads, but this quote of KidJoe got me on the right track:
" GPT.BIN is the partition table. Its important. When GPT.BIN and MOTOBOOT.IMG are mismatched from the rom on your phone you could brick when taking an upgrade.
In most cases, the GPT.BIN has matched from model to model when on the same rom (i.e. GPT.BIN from XT1060 4.4.4 rom has matched GPT.BIN of XT1053 4.4.4 rom).
However, try Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and see what happens. "
Alright so, here is what I grasped:
before things went bad for my phone, I was already on lollipop. Following the youtube video I downgraded it from 5.1 to 4.4.4.
While downgrading I already noticed that some commands failed, which was the gpt.bin stuff.
So after my phone was working on 4.4.4 and I used the Motorola Upgrade to 5.1 , there must have been a problem with the gpt.bin and motoboot.img , just like KidJoe said. Hence why I got stuck in Fastboot.
As I said in the first post, I had to find the right image for my phone.
In the Fastboot mode I saw that I was on 30.BE, and from what I understand that means im on lollipop and since I cant downgrade, I had to find the right lollipop version for my device.
Im also german, so I found this version:
XT1052_GHOST_RETDE_5.1_LPA23.12-15.5_cid7_CFC.xml.zip
KEEP IN MIND, my problem was having the wrong version all along, so you have to find the right version for your smartphone, dont make the same mistake I did!
I found my file on filefactory through this link here:
http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
(EDIT: I recommend using something like jdownloader to manage the download)
After I had the right version, I used rsdlite, chose my new file and my phone was working again.
However, I noticed that even tho my phone was working, the rsdlite actually failed somewhere between the lines. (I think it was step 7 or 9)
I was really happy to see my device boot up again, but wasnt happy with those errors and followed this link:
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Option 5.
Now finally all the commands went OKAY in my cmd window.
After the motorola took some time to boot up again, I performed a factory reset via settings.
Just to make sure its fine and it seems like it is.
To end this thread off, I hope KidJoe will read this post.
Big thanks to you, your the man!
And even tho on some posts you came along a bit harsh, which really got me worried my phone would be completely dead, I wish you a nice christmas time dude!
I get this error on my moto x dev edition with verizon xt1060 in fastboot. i cant flash any images. i was told to use rsd lite but it doesnt detect my phone.
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
RandyThor said:
I get this error on my moto x dev edition with verizon xt1060 in fastboot. i cant flash any images. i was told to use rsd lite but it doesnt detect my phone.
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
Click to expand...
Click to collapse
Do you install Motorola drivers..?
Salik Iqbal said:
Do you install Motorola drivers..?
Click to expand...
Click to collapse
yes the newest drivers are installed. It shows up in device manager as "MOT Single ADB Interface". I can also detect it in fastboot, though most commands won't work.
i had a similar kind of problem on my ghost. Firmware crash, due to which phone was stuck at the bootloader. No recovery nor did any fastboot worked at that time. I referred this and this. It worked for me.
varunpilankar said:
i had a similar kind of problem on my ghost. Firmware crash, due to which phone was stuck at the bootloader. No recovery nor did any fastboot worked at that time. I referred this and this. It worked for me.
Click to expand...
Click to collapse
when following the second link steps i get stuck at step 8. Im not sure what he means by click on the device. does he mean the 'Mot Single ADB Interface' device? i clicked properties on that then i clicked update and i selected the folder where i kept the signed sys files. there was nothing about QHSUSB_DLOAD as it said in the tutorial though. anyway afterwards there was no port called Qualcomm HS-USB QDLoader 9008 so i couldn't get a portnumber to continue the process.
The other link you gave i assumed id go to Moto X BE\1_Repair_Boot (RSD Lite)\1060 and flash the gpt.bin and the motoboot.img but i got this error:
C:\Users\Jake\Desktop\New folder\Moto X BE\1_Repair_Boot (RSD Lite)\1060>mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.290s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.210s
C:\Users\Jake\Desktop\New folder\Moto X BE\1_Repair_Boot (RSD Lite)\1060>mfastboot flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.420s]
writing 'motoboot'...
Motoboot: Unknown partition name
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.700s
I'm in basically the same situation with my XT1060 Developer Edition. Tried a long list of fixes, none has done the trick. All I have available is the fastboot menu. Phone won't boot into OS, won't go into recovery, hasn't accepted any flashes or erases. This happened because after downgrading to 4.4.4 I allowed an OTA update to 5.1. Phone rebooted and hasn't left the flashboot menu since. I, too, am looking for any help I can get on the matter.
Just like you, I tried that trick involving the fancy drivers, but my phone shows up as "Mot Single ADB Interface" in device manager, so that fix doesn't apply. If my phone reported as QHSUSB_DLOAD in device manager, it would be a different story. Though my phone was rooted and unlocked before downgrading to 4.4.4, at this point it's locked (happened without my knowledge), which I believe is why I can't reflash a recovery image.
It seems pretty clear to me that the phone has either an absent or corrupted partition scheme, as gpt.bin won't flash AND my phone doesn't acknowledge the existence of partitions. I suspect my phone began writing the 5.1 OTA update before erroring out, thus leaving me in a limbo mode halfway between 5.1 and 4.4.4. If anyone out there has experience with this seemingly unique brick situation, I would appreciate it. OP, good luck with your phone.
OrlandoAlex said:
I'm in basically the same situation with my XT1060 Developer Edition. Tried a long list of fixes, none has done the trick. All I have available is the fastboot menu. Phone won't boot into OS, won't go into recovery, hasn't accepted any flashes or erases. This happened because after downgrading to 4.4.4 I allowed an OTA update to 5.1. Phone rebooted and hasn't left the flashboot menu since. I, too, am looking for any help I can get on the matter.
Just like you, I tried that trick involving the fancy drivers, but my phone shows up as "Mot Single ADB Interface" in device manager, so that fix doesn't apply. If my phone reported as QHSUSB_DLOAD in device manager, it would be a different story. Though my phone was rooted and unlocked before downgrading to 4.4.4, at this point it's locked (happened without my knowledge), which I believe is why I can't reflash a recovery image.
It seems pretty clear to me that the phone has either an absent or corrupted partition scheme, as gpt.bin won't flash AND my phone doesn't acknowledge the existence of partitions. I suspect my phone began writing the 5.1 OTA update before erroring out, thus leaving me in a limbo mode halfway between 5.1 and 4.4.4. If anyone out there has experience with this seemingly unique brick situation, I would appreciate it. OP, good luck with your phone.
Click to expand...
Click to collapse
For both of you.. @RandyThor and @OrlandoAlex check thread after 12hrs.. i have something for you which may hopefully fix thay issue.
I'm in the same boat. At least I've finally learned why I always refuse OTA updates (until now it hadn't really dawned on me that I had to blankflash because I downgraded after having updated official firmware).
A solution would be much appreciated, as nothing I've done has worked to this point. I'll read more on here to see whether someone has already posted a solution, and I should be able to check back on this thread in a couple of hours.
EDIT:
It does not look like there is a common solution, from what I can tell in the Q&A. Will search elsewhere next.
PiArc said:
I'm in the same boat. At least I've finally learned why I always refuse OTA updates (until now it hadn't really dawned on me that I had to blankflash because I downgraded after having updated official firmware).
A solution would be much appreciated, as nothing I've done has worked to this point. I'll read more on here to see whether someone has already posted a solution, and I should be able to check back on this thread in a couple of hours.
EDIT:
It does not look like there is a common solution, from what I can tell in the Q&A. Will search elsewhere next.
Click to expand...
Click to collapse
Was busy and forgot that sorry, i put alarm for that now will update this thread in some hours.
Salik Iqbal said:
Was busy and forgot that sorry, i put alarm for that now will update this thread in some hours.
Click to expand...
Click to collapse
No worries. Whenever you get the chance.
RandyThor said:
No worries. Whenever you get the chance.
Click to expand...
Click to collapse
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
@Salik Iqbal, you've done it! Can you tell me exactly why that worked? Which version of the bootloader was that? Also, THANK YOU!
PiArc said:
@Salik Iqbal, you've done it! Can you tell me exactly why that worked? Which version of the bootloader was that? Also, THANK YOU!
Click to expand...
Click to collapse
It was from att latest firmware gpt and aboot.
Salik Iqbal said:
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Click to expand...
Click to collapse
you are the GOAT my friend
Salik Iqbal said:
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Click to expand...
Click to collapse
One last thing. The phone is working fine now but recovery doesn't seem to work. I've tried reflashing it and it works but when i enter recovery i just get that dead android guy with the error symbol. Any ideas?
RandyThor said:
One last thing. The phone is working fine now but recovery doesn't seem to work. I've tried reflashing it and it works but when i enter recovery i just get that dead android guy with the error symbol. Any ideas?
Click to expand...
Click to collapse
Oh nevermind i apologize. My recovery was working fine i forgot i have to hold vol up and tap power to get to the recovery options...
Anyway thanks again you're a life saver!!!!!
RandyThor said:
Oh nevermind i apologize. My recovery was working fine i forgot i have to hold vol up and tap power to get to the recovery options...
Anyway thanks again you're a life saver!!!!!
Click to expand...
Click to collapse
So lets close the thread by requesting moderator..
Salik Iqbal said:
So lets close the thread by requesting moderator..
Click to expand...
Click to collapse
do i have to do that lol? im a noob
Hello all,
First of all I looked for a (sub) forum for the P10 Lite, but I can't seem to find it. If a admin/mod thinks this post should be placed elsewhere, feel free to move it.
Ok, now on to the problem I'm having with my P10 Lite (WAS-LX1A model)...
The phone is running the stock B102 firmware, I've unlocked the bootloader with the code I got from Huawei, installed TWRP and rooted the phone, all was working just fine.
Then, last saturday (June 24, 2017) there was an OTA update to B131 available, tried to install it but it failed (nothing was installed btw, it never got to then point where the OTA did anything, phone would just reboot).
So after some searching and in a lapse of judgement I decided to (re)lock the bootloader thinking that was what kept the update from installing (command: sudo fastboot oem relock <code>).
And that's where my problem gets in.
Now I have a phone which only can only get into:
1.) Huawei eRecovery: Only options I have in eRecovery are: "Download latest version and recovery", "Reboot" and "Shutdown". No option to reset to factory or anything like that. "Download latest version and recovery" fails everytime, stating: "Failed to get package info from server". Gave my phone a static DHCP lease and even put it in DMZ on the router (just in case NAT/firewall was interfering), but that didn't help at all. Rebooting or shutdown will just put the phone back into eRecovery as soon as it's booted.
2.) Emergency/EDL: This is the mode where you're supposed to put the firmware you want to flash in the "dload" folder on sd-card. Tried that too, but it gets to about 5% and fails (tried B120, B123 and B131 update files, none work). When the phone gets into this mode it's also available to ADB. However, something seems to have changed dramaticly as I no longer seem to have any permissions on the phone. "adb devices" shows my phone but it also says "unauthorised". As soon as I try to do anything that requires root priviledges (like: "adb root" or "adb shell") I get an error stating: "This adb server's $ADB_VENDOR_KEYS is not set". Clearly that means there's an issue regarding the .pub keys on client/host side not being the same. Since I cannot pull anything from, or push anything to, my phone I don't know how I can fix this... And since I'm getting this message on the same machine that I used to flash TWRP on the phone earlier (which worked just fine), it seems to me this problem exists on the phone-side.
3.) Fastboot & rescue: fastboot finds my phone just fine, yet it flatout refuses all meaningful commands (only basic commands like reboot work) with the error: "FAILED (remote: Command not allowed)". Some searching tells me this is because the bootloader is locked and that's exactly what my phone shows on it's screen when it's in fastboot mode: "PHONE Relocked" and "FRP Lock". However fastboot command: "fastboot oem get-bootinfo" returns: "(bootloader) unlocked". This confuses me, a lot; if the bootloader is unlocked then what is preventing me from flashing anything? Trying to unlock the bootloader again through fastboot (fastboot oem unlock <code> / fastboot oem unlock "<code>") gives the "FAILED (remote: Command not allowed)" error. Trying to lock the bootloader again (fastboot oem relock <code> / fastboot oem relock "<code>") gives error: "FAILED (remote: stat not match)". Obviously I cannot flash anything from fastboot anymore.
Tried all I can think of on 2 linux machines and 1 Windows 7 machine, all 64-bit, allthough 1 of the linux machine is multi-architecture so it runs 32-bit too (not related to this issue, needed 32-bit for WINE). This just to rule out an issue with my machine. All 3 machines act exactly the same though which makes me (strongly) believe the issue resides on the phone.
Trying to recovery in HiSuite (newest version) doesn't work either, it just tells my my phone isn't supported, even though it does detect my phone when it's in fastboot mode.
Nothing has been flashed, so this is not a case of a flash gone wrong, it just looks like I'm locked out of my own phone and for the life of me I cannot figure out how to get back in. And there's no way to boot into system anymore, so I cannot check/change "OEM Unlock" and "ADB Debugging" settings in the phone developers options
.
Any help/advice would be greatly appreciated! I'm stuck, Huawei customer service only tells me to do a factory reset, which I can't, and when I tell them that's not possible all becomes awfully quiet on their end (they don't respond to my mails anymore). I simply can't think of anything I could try to fix this, spend the last 5 days searching the web but nothing seems to work. Maybe some Android-guru's have some suggestions (I'm certainly open to suggestions! ).
Thanks in advance.
Info:
- phone: Hauwei P10 Lite, model: WAS-LX1A, firmware: WAS-LX1AC432B102
- (main) laptop: HP Probook running Arch linux (64bit), uname: "Linux probook 4.11.6-3-ARCH #1 SMP PREEMPT Thu Jun 22 12:21:46 CEST 2017 x86_64 GNU/Linux".
- Android SDK version 26. Package named: "aur/android-sdk-platform-tools r26.0.0-1 (1155, 9.20)" Which can be found on Arch's AUR. (I am aware I need to run fastboot as "sudo", fastboot cannot do anything without sudo priviledges).
Edit: Tried some fastboot commands with regards to "FRP Unlock", command: "sudo fastboot oem frp-unlock" returns: "FAILED (remote: oem_frp_check_password failed! Error = -1)" not sure what password is required here to be honest and "sudo fastboot oem frp-erase" returns: "FAILED (remote: Command not allowed!)".
OTA update didn't install because of custom recovery, not because bootloader was unlocked. You can unlock bootloader again and try again.. Dload for some reason won't work anymore on newer firmwares.. At the end you can always restore phone with DC-Phoenix tool, just flash stock firmware you had on the phone.
MobileTechArena said:
OTA update didn't install because of custom recovery, not because bootloader was unlocked. You can unlock bootloader again and try again.. Dload for some reason won't work anymore on newer firmwares.. At the end you can always restore phone with <snip> cannot post URL's yet <snip> tool, just flash stock firmware you had on the phone.
Click to expand...
Click to collapse
Thank you, MobileTechArena, for your time/effort,
That's what I thought regarding bootloader/recovery, however I thought of it too late.
Unlocking to bootloader again doesn't work (command: sudo fastboot oem unlock "16-digit-code"), I get the "FAILED (remote: Command not allowed)" error. Tried it with bootloader code as a string, and as "code". Both don't work, on the same machine I used previously to unlock the bootloader in the first place. The unlocking working but after giving the relock command everything seems to get blocked, even though "sudo fastboot oem get-bootinfo" still tells me the bootloader is unlocked.
With regards to DC-Unlocker, I don't have a stock B102 firmware, it simply cannot be found anywhere online. I managed to get a full TWRP backup of the B102 firmware from some helpful people on this site (on someone else's thread), but seeing as how I'm no longer able to boot into TWRP, I don't think that TWRP backup is going to do me any good. Oldest firmware I can find online is B120, which is newer than the firmware on my phone.
Read somewhere on Huawei Q&A section that they removed the "dload" method because of security risks, so yeah that method is DOA. Really sad they did this, feels like that could've saved me.
Also gave Huawei's Fastboot erase tool (version: 1006) a try. It detects my phone just fine but it cannot unlock FRP. If I use the tool to erase FRP it reboots the phone -> fails. doesn't make any changes.
Am I right in thinking it's Huawei's FRP that's preventing fastboot/adb commands?
GuessThisIsMe said:
Thank you, MobileTechArena, for your time/effort,
That's what I thought regarding bootloader/recovery, however I thought of it too late.
Unlocking to bootloader again doesn't work (command: sudo fastboot oem unlock "16-digit-code"), I get the "FAILED (remote: Command not allowed)" error. Tried it with bootloader code as a string, and as "code". Both don't work, on the same machine I used previously to unlock the bootloader in the first place. The unlocking working but after giving the relock command everything seems to get blocked, even though "sudo fastboot oem get-bootinfo" still tells me the bootloader is unlocked.
With regards to DC-Unlocker, I don't have a stock B102 firmware, it simply cannot be found anywhere online. I managed to get a full TWRP backup of the B102 firmware from some helpful people on this site (on someone else's thread), but seeing as how I'm no longer able to boot into TWRP, I don't think that TWRP backup is going to do me any good. Oldest firmware I can find online is B120, which is newer than the firmware on my phone.
Read somewhere on Huawei Q&A section that they removed the "dload" method because of security risks, so yeah that method is DOA. Really sad they did this, feels like that could've saved me.
Also gave Huawei's Fastboot erase tool (version: 1006) a try. It detects my phone just fine but it cannot unlock FRP. If I use the tool to erase FRP it reboots the phone -> fails. doesn't make any changes.
Am I right in thinking it's Huawei's FRP that's preventing fastboot/adb commands?
Click to expand...
Click to collapse
I think it is because of locked FRP, you can still try with DC-Phoenix with newer firmware. I had the same problem on P8 Lite 2017, Couldn't find B106 that i had on the phone anywhere, but successfully flashed B110.
EDIT: also check under filelist of the firmware that firmware for sure is for your region.
MobileTechArena said:
I think it is because of locked FRP, you can still try with DC-Phoenix with newer firmware. I had the same problem on P8 Lite 2017, Couldn't find B106 that i had on the phone anywhere, but successfully flashed B110.
EDIT: also check under filelist of the firmware that firmware for sure is for your region.
Click to expand...
Click to collapse
Thank you for the info, shall have another look at the firmware (or more precisely, it's region). It's the EU version I'll need that much I know.
Also did some looking into why Huawei's eRecovery isn't working, so I turned on my Kali Linux machine and did some 'wiresharking'.
Seems eRecovery is looking for something at ip: 54.229.89.249.
A Whois query shows this ip belongs to Amazon's AWS.
However, pinging the IP shows that it's not online, so no wonder why eRecovery isn't working (nice one Huawei! ).
GuessThisIsMe said:
Thank you for the info, shall have another look at the firmware (or more precisely, it's region). It's the EU version I'll need that much I know.
Also did some looking into why Huawei's eRecovery isn't working, so I turned on my Kali Linux machine and did some 'wiresharking'.
Seems eRecovery is looking for something at ip: 54.229.89.249.
A Whois query shows this ip belongs to Amazon's AWS.
However, pinging the IP shows that it's not online, so no wonder why eRecovery isn't working (nice one Huawei! ).
Click to expand...
Click to collapse
Yes, if it's eu then eu firmware is what you need. As for the eRecovery i have no idea why its looking for something on that ip. Huawei definitely need's to make restoring devices simpler.
---------- Post added at 09:36 PM ---------- Previous post was at 09:19 PM ----------
Can you connect device with HiSuite in fastboot mode? You could use this REDLOTUS tool to bypass eRecovery and flash firmware.
MobileTechArena said:
Yes, if it's eu then eu firmware is what you need. As for the eRecovery i have no idea why its looking for something on that ip. Huawei definitely need's to make restoring devices simpler.
---------- Post added at 09:36 PM ---------- Previous post was at 09:19 PM ----------
Can you connect device with HiSuite in fastboot mode? You could use this <snip> tool to bypass eRecovery and flash firmware.
Click to expand...
Click to collapse
Ok, l did get the right firmware (EU region), so that wasn't the issue.
Tried the REDLOTUS tool (thanks for that link btw, seems like a promising project), but alas it doesn't seem to work for me.
Got node js/npm installed just fine, it works, manages to get the firmware and everything, listens for HiSuite and manages to point HiSuite to local host to look for firmware there (like it should according to REDLOTUS' Readme).
Unfortunately, HiSuite doesn't give me the option to update firmware, only the systemrecovery button isn't greyed out, and systemrecovery tells me my device isn't supported. I can see on my phone's screen "rescue mode enter..." when I select systemrecovery in HiSuite, but nothing else happens.
Seems like REDLOTUS might work for me once the author manages to get it to work with eRecovery instead of HiSuite (apparantly that's being worked on atm).
hi i'm from france and i have exactly the same problem as you
the only difference is that i've "PHONE Unlocked" and "FRP Unlock" but not all of the fastboot commands works
i'm trying just right now to flash BOOT.img, RECOVERY.img and SYSTEM.img
hope it will work, sorry for my bad english
Radnaksi98 said:
hi i'm from france and i have exactly the same problem as you
the only difference is that i've "PHONE Unlocked" and "FRP Unlock" but not all of the fastboot commands works
i'm trying just right now to flash BOOT.img, RECOVERY.img and SYSTEM.img
hope it will work, sorry for my bad english
Click to expand...
Click to collapse
If your phone reads "PHONE Unlocked" and "FRP Unlock", then lucky for you, you don't have anything near my problem.
First of, if you do a: 'fastboot devices' command, does it show your phone?
Can you tell me if the following commands work, and what they return?
- fastboot oem get-bootinfo
- fastboot oem get-lock-state
- fastboot oem lock-state info
If you run Linux you'll need to "sudo" the fastboot commands.
You have enabled ADB-debugging on the phone right?
Edit: Can you still get into the stock recovery? To get there first turn the phone completely off. Then hold Volume Down (-) and Power buttons till you see the Huawei logo, then release both buttons. From stock recovery you could try a factory reset (DO NOT DO THIS IF YOU HAVE TWRP INSTALLED!!!).
hi, the phone shows me "FRP Unlock", but when i've done all the commands u gave me and there's an FB Lockstate on: LOCKED
Idk what it is
EDIT: ADB-debugging isn't enabled because i can't boot the phone, and when it started to bootloop that was when i've unlocked the bootloader and someone told me to factory reset the phone, so i think the ADB-debugging isn't enabled anymore
EDIT2: Stock recovery is working
does anyone have a twrp backup for the p10 lite ? it would be faster ....
oh and i have installed the revolution recovery, now i have the mtp and adb functionning, adb shell too, but i still cannot mount /data or /system
looks like /data is empty and unmoutable idk what to do
i can't change fs or wipe the partition pls help
Radnaksi98 said:
does anyone have a twrp backup for the p10 lite ? it would be faster ....
oh and i have installed the revolution recovery, now i have the mtp and adb functionning, adb shell too, but i still cannot mount /data or /system
looks like /data is empty and unmoutable idk what to do
i can't change fs or wipe the partition pls help
Click to expand...
Click to collapse
You can find a full TWRP backup of the B102 firmware in the thread called -> Root p10 "lite" , on page 11 user: stefanwe92 posted a link to it.
Good luck!
Thank you for answering me !
But i've the LX1A, so can i use it ?
Radnaksi98 said:
Thank you for answering me !
But i've the LX1A, so can i use it ?
Click to expand...
Click to collapse
Did/does it have a firmware like: WAS-LX1AC432B102? (the C432 is the important part). If so, then yes you should be fine.
Now beware I base this solely on the fact that there isn't any firmware on HWMT's site for the WAS-LX1C*, only for the WAS-LX1AC*. Google "hwmt" and have a look for yourself (it's in russian, so Google translate will definately help).
If you want to be absolutely sure, I'd suggest contacting user "stefanwe92", he has the phone and has uploaded the firmware, so he should be able to give you the information you need.
I wish I could've tried the TWRP myself, but my phone refuses to load the bootloader, so I can't :crying:
GuessThisIsMe said:
Did/does it have a firmware like: WAS-LX1AC432B102? (the C432 is the important part). If so, then yes you should be fine.
Now beware I base this solely on the fact that there isn't any firmware on HWMT's site for the WAS-LX1C*, only for the WAS-LX1AC*. Google "hwmt" and have a look for yourself (it's in russian, so Google translate will definately help).
If you want to be absolutely sure, I'd suggest contacting user "stefanwe92", he has the phone and has uploaded the firmware, so he should be able to give you the information you need.
I wish I could've tried the TWRP myself, but my phone refuses to load the bootloader, so I can't :crying:
Click to expand...
Click to collapse
I don't really know, on the box it's written WAS-LX1A
But i'm gonna make a backup first with twrp (yes i've successfully unbricked the phone by myself ! It work by half but man it Was hard ! I will try to makes a tutorial for you in french as soon as i can because it's hard for me to speak in english lol, so use a translator !) and then flash the backup you gave me !
I will do this tomorrow because it's late in France and it took me an entier afternoon to semi-unbrick this phone ^^
I will contact you tomorrow with good news i hope !
Radnaksi98 said:
I don't really know, on the box it's written WAS-LX1A
But i'm gonna make a backup first with twrp (yes i've successfully unbricked the phone by myself ! It work by half but man it Was hard ! I will try to makes a tutorial for you in french as soon as i can because it's hard for me to speak in english lol, so use a translator !) and then flash the backup you gave me !
I will do this tomorrow because it's late in France and it took me an entier afternoon to semi-unbrick this phone ^^
I will contact you tomorrow with good news i hope !
Click to expand...
Click to collapse
command: "fastboot oem get-build-number" should tell you exactly which firmware your phone is running.
Congrats on your success!
Regarding your English, it seems just fine to me, I understand you well. And for sure it's better than my French (dropped that subject as quickly as I could in high school ).
Hope to hear from you soon, with a working phone!
Sleep well, btw I live in the same timezone as you (I'm Dutch).
Phone has been brought back to life with the excellent help from the DC-Unlocker team.
MobileTechArena was absolutely right, only DC-Phoenix can save you in a circumstance such as the one I found myself in.
15 bucks well spent, can definately recommend it!!!
Problem solved
GuessThisIsMe said:
Phone has been brought back to life with the excellent help from the DC-Unlocker team.
MobileTechArena was absolutely right, only DC-Phoenix can save you in a circumstance such as the one I found myself in.
15 bucks well spent, can definately recommend it!!!
Problem solved
Click to expand...
Click to collapse
I fixed my bootloop that lasted for almost an month with help of MobileTechArena without DC-Phoenix so I guess we both gonna thank him :laugh:
Carkai said:
I fixed my bootloop that lasted for almost an month with help of MobileTechArena without DC-Phoenix so I guess we both gonna thank him :laugh:
Click to expand...
Click to collapse
Agreed!
Nice people those Irish, some of them like their whiskey a bit too much , but all of the Irish folk I've met in my life have been nothing but kind human beings.
Knew one Irish lad who thought nothing of starting to drink at 8 in the morning, I tell you the drive back home was very interesting (and not at all dangerous :silly.
Radnaksi98 said:
does anyone have a twrp backup for the p10 lite ? it would be faster ....
oh and i have installed the revolution recovery, now i have the mtp and adb functionning, adb shell too, but i still cannot mount /data or /system
looks like /data is empty and unmoutable idk what to do
i can't change fs or wipe the partition pls help
Click to expand...
Click to collapse
I have a identical problem... my phone is stuck in "Huawei eRecovery" screen. Same situation that you had reported (connection fail).
I found a solution to enter in FASTBOOT & RESCUE MODE and i posted in:
https://forum.xda-developers.com/general/general/solution-huawei-p10-lite-alternative-to-t3637311
I also have a TWRP backup... but my problem started when i used it to restore my phone. So i believe that it will not help you. But if you want I can send it to you. My model is a WAS-LX1A (Portugal).
Have you found a solution to your problem?
Hello all fellow pixelers
After upgrading to 11 i am faxing a ton of issues with my pixel 4 xl such as "clean the top bar", phone calls going to speakerphone etc.
I have tried multiple factory resets with CMD but one thing i am experienced and have never had before is that whenever i am almost done with the reset option via CMD, the message i get is:
E: (libfs_mgr) failed to mount / metadata; formatting: Invalid argument
E: (libfs_mgr) fs_mgr_do_format: Format /dev/block/by-name/metadata as "ext4|""
E: (libfs_mgr) make2fs returned 255
E: (libfs_mgr)failed to format /metadata: Permission denied
E: Cannot mount /metadata/ota
formating /data...
formatting /metadata...
Wiping Titan M..
E:can"t send spi message: Try again
it repeats for 30 times
Data wipe complete
This being said i sure hope someone can and will help me solve this issue as it is becoming a pain, i thank you all in advance for your efforts
It sounds like you're only trying factory resets at the moment. I don't know how to fix this issue, so the only suggestion I have is to try flashing the factory image (which includes a userdata wipe). Don't do the OTA update method. I've been able to fix all my phone problems by flashing the factory image. If that still doesn't work, then I'm thinking there's something physically wrong with the phone.
Colonel_Kosova said:
Hello all fellow pixelers
After upgrading to 11 i am faxing a ton of issues with my pixel 4 xl such as "clean the top bar", phone calls going to speakerphone etc.
I have tried multiple factory resets with CMD but one thing i am experienced and have never had before is that whenever i am almost done with the reset option via CMD, the message i get is:
E: (libfs_mgr) failed to mount / metadata; formatting: Invalid argument
E: (libfs_mgr) fs_mgr_do_format: Format /dev/block/by-name/metadata as "ext4|""
E: (libfs_mgr) make2fs returned 255
E: (libfs_mgr)failed to format /metadata: Permission denied
E: Cannot mount /metadata/ota
formating /data...
formatting /metadata...
Wiping Titan M..
E:can"t send spi message: Try again
it repeats for 30 times
Data wipe complete
This being said i sure hope someone can and will help me solve this issue as it is becoming a pain, i thank you all in advance for your efforts
Click to expand...
Click to collapse
Have you tried factory resetting the phone? You do not need a computer. If you do factory reset you'll lose all your data.
Hey there Neo
Thnx for the reply and yes I flashed the phone 4 times now with cmd. I get all the bugs and the messages only when I am flashing Android 11.
I reverted once to 10 I had no issues whatsoever, once I upgraded to 11 again both with cmd and ota I get the same issue.
It is really really is a nuisance, was hoping maybe someone can finde a fix?
Just got the darn phone saved up most a year just to get it, what a dissapointment.
Again thank u
Homeboy76 said:
Have you tried factory resetting the phone? You do not need a computer. If you do factory reset you'll lose all your data.
Click to expand...
Click to collapse
I did and it didn't help, just feel mad I hate to have to sell this phone.
Thank you for the reply
Colonel_Kosova said:
I did and it didn't help, just feel mad I hate to have to sell this phone.
Thank you for the reply
Click to expand...
Click to collapse
Do you have the latest Android SDK Platform-tools r34.0.4?
What cmd are you using to flash the phone?
Guide
This Factory Reset: Settings -> System-> Advanced->Reset options-> Erase all data (factory reset)
Homeboy76 said:
Do you have the latest Android SDK Platform-tools r34.0.4?
What cmd are you using to flash the phone?
Guide
This Factory Reset: Settings -> System-> Advanced->Reset options-> Erase all data (factory reset)
Click to expand...
Click to collapse
Yes I do all the latest versions
I use this as a guide
https://youtu.be/cKXa5iL1kfQ
Ok, Hopefully, someone has a solution to this problem.
Your error messages seem like it's somehow incompatible or you're not allowed to flash. So that made me wonder if you're downloading the right factory image for the right phone variant. (I think I only saw one variant for the android 11; can't recall at the moment.)
From your responses, it sounds like you're using the ota image. I've had problems with ota in the past, so my suggestion is to flash the factory image instead, which is different from ota. (I've had the pixel 4 xl for a year and never had issues with flashing.)
I also don't input the cmd commands manually. I run the "flash all.bat" which comes with the factory image and it does everything for me.
Colonel_Kosova said:
Hey there Neo
Thnx for the reply and yes I flashed the phone 4 times now with cmd. I get all the bugs and the messages only when I am flashing Android 11.
I reverted once to 10 I had no issues whatsoever, once I upgraded to 11 again both with cmd and ota I get the same issue.
It is really really is a nuisance, was hoping maybe someone can finde a fix?
Just got the darn phone saved up most a year just to get it, what a dissapointment.
Again thank u
Click to expand...
Click to collapse
Neo thank you very much for the reply and the hints.
Could you please maybe find and link the right file for me!?
I have never used the method with flash all bat file, this being said i would really appreciate if you could do me that favor and maybe guide me on how to.
I really love my 4 xl and hate the fact that I have these issues, I have been using it like this for some days hoping a fix will pop out there before I install everything back again.
I sincerely thank you for the effort and time
QUOTE=neo_lithic3K;83692801]Your error messages seem like it's somehow incompatible or you're not allowed to flash. So that made me wonder if you're downloading the right factory image for the right phone variant. (I think I only saw one variant for the android 11; can't recall at the moment.)
From your responses, it sounds like you're using the ota image. I've had problems with ota in the past, so my suggestion is to flash the factory image instead, which is different from ota. (I've had the pixel 4 xl for a year and never had issues with flashing.)
I also don't input the cmd commands manually. I run the "flash all.bat" which comes with the factory image and it does everything for me.[/QUOTE]
Opps! Wrong thread, stay safe.
Sorry @neo_lithic3K.
Check to make sure your proximity sensor is working. Mine quit working some time around 11 beta 3 and flashing back to 10 stopped the clean the top bar thing but not the speakerphone problem (screen was staying on up against my ear) Google replaced mine under warranty
(1a) First, here are the preliminary steps. There are alot of instructions at the top of Google's page at: https://developers.google.com/android/images
I assume that you've already followed all those instructions .... especially unlocking your bootloader, enabling USB Debugging from Developer Options, and adding fastboot to your PATH environment variable (and then rebooting your PC).
***NOTE: There are better guides on xda that give you more thorough instructions, so you may want to check those out instead of reading mine below.***
(1b) I assume that you have an unlocked Pixel 4 XL and that you purchased google's version of the phone from the Google Store. I don't know all the different ways someone can buy the Pixel 4 XL. For example, I think Verizon used to sell it but I don't know if Verizon variants can be flashed. If you didn't buy the phone from the US Google store or you bought the phone from another country, then there could be restrictions there that I don't know about.
(1c) I also assume you have a Windows PC. I've never flashed from other types of operating systems.
(2) Download the latest android 11 'coral' factory image at: https://dl.google.com/dl/android/aosp/coral-rp1a.201005.004-factory-1eb5827f.zip
That link is for the file posted on google's webpage for this version: 11.0.0 (RP1A.201005.004, Oct 2020) 1eb5827f98ec68b71bfd651d667a7cf557832f2e2850540d322d2a3a6fcc07a8
(3) Connect your computer to your phone using the usb cable. I assume your phone's usb debugging is already enabled & fastboot is already in your PATH environment variables as mentioned in the instructions earlier. You may get a pop up on your phone to trust the PC. I don't remember the exact wording but you should accept or trust it.
(4) After you download the zip file, unzip it somewhere (preserve the folder structure). You'll find the flash-all.bat located at: \coral-rp1a.201005.004-factory-1eb5827f\coral-rp1a.201005.004\flash-all.bat
(5) NOTE that everything on your phone will be wiped so first backup anything you need.
(6) Boot your phone to the bootloader using the hardware buttons (or you can use the cmd command: adb reboot bootloader).
While your phone is still connected to your PC, run flash-all.bat. (I usually just double-click on the bat file from my Windows PC)
(7) The cmd window will run through a series of commands and your phone screen may change or reboot. At one point (on the fastbootd phone screen), it will look like your phone is not doing anything or waiting for something. Don't do anything.... just wait. You'll know the flashing is done when the cmd window says "Press any key to exit..."
(8) When it's all done, your phone should automatically boot into android and you should see the pixel setup screen.
(9) This resets your phone to factory image. You'll need to follow other steps to root your phone.
Colonel_Kosova said:
Neo thank you very much for the reply and the hints.
Could you please maybe find and link the right file for me!?
I have never used the method with flash all bat file, this being said i would really appreciate if you could do me that favor and maybe guide me on how to.
I really love my 4 xl and hate the fact that I have these issues, I have been using it like this for some days hoping a fix will pop out there before I install everything back again.
I sincerely thank you for the effort and time
QUOTE=neo_lithic3K;83692801]Your error messages seem like it's somehow incompatible or you're not allowed to flash. So that made me wonder if you're downloading the right factory image for the right phone variant. (I think I only saw one variant for the android 11; can't recall at the moment.)
From your responses, it sounds like you're using the ota image. I've had problems with ota in the past, so my suggestion is to flash the factory image instead, which is different from ota. (I've had the pixel 4 xl for a year and never had issues with flashing.)
I also don't input the cmd commands manually. I run the "flash all.bat" which comes with the factory image and it does everything for me.
Click to expand...
Click to collapse
[/QUOTE]
Colonel_Kosova said:
Neo thank you very much for the reply and the hints.
Could you please maybe find and link the right file for me!?
I have never used the method with flash all bat file, this being said i would really appreciate if you could do me that favor and maybe guide me on how to.
I really love my 4 xl and hate the fact that I have these issues, I have been using it like this for some days hoping a fix will pop out there before I install everything back again.
I sincerely thank you for the effort and time
Click to expand...
Click to collapse
I know it's been 4-5 days since you last responded, but I'm going to assume you still need help. Flashing a full factory image (Not OTA) using the included flash-all.bat script will return your phone to "out of the box" condition. It's a fool proof way to get the phone completely factory stock, so you can then test your hardware (proximity sensor). Instructions can be found on the image download page. It's possible you have a sensor issue, but flashing the full image is the first step. Best of luck and be sure to come back and let us know how it went.
Hello, everyone.
I have a similar issue, though nothing related to the bootloader. I did flash the entire factory image and the process went smoothly until the very end where it showed:
Erasing 'userdata'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata'
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting
Finished. Total time 253.513s
Press any key to exit...
The phone booted up just fine but I can't stop being worried something might eventually not work properly because of this.
Is there anything else I can try?
Rocio19 said:
Hello, everyone.
I have a similar issue, though nothing related to the bootloader. I did flash the entire factory image and the process went smoothly until the very end where it showed:
Erasing 'userdata'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata'
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting
Finished. Total time 253.513s
Press any key to exit...
The phone booted up just fine but I can't stop being worried something might eventually not work properly because of this.
Is there anything else I can try?
Click to expand...
Click to collapse
No. You used the flash-all without removing the -w. That is the reason your userdata was erased. You're good!
Homeboy76 said:
No. You used the flash-all without removing the -w. That is the reason your userdata was erased. You're good!
Click to expand...
Click to collapse
Thank you very much for your reply. My main concern is the part about not being able to format it. Is that normal?
Rocio19 said:
Thank you very much for your reply. My main concern is the part about not being able to format it. Is that normal?
Click to expand...
Click to collapse
Yes! I don't think you'll have any problems.
Homeboy76 said:
Yes! I don't think you'll have any problems.
Click to expand...
Click to collapse
Phew! That's a relief. I just got the phone yesterday and I was so worried I had blessed it up somehow :crying:
Think I'll stay with stock for a while before I attempt any more flashing lol. Thank you!
I got tired of dealing with face unlock being broken and other issues related to the proximity sensor (screen wouldn't light up during a call if i moved it away from my face).
So I decided to flash back to the latest Android 10 image prior to 11 coming out. Everything is back to working buttery smooth.
If anyone else wants to do this and needs help let me know.
A few tips:
I used https://flash.android.com to perform the factory flash
I used this build 10.0.0 (QQ3A.200805.001, Aug 2020)
After flashing, the phone wants you to upgrade to Android 11, but you can enable developer options and turn off Android System Update notifications.