Related
Can someone please help. I'm getting desperate now. I flashed a Nougat build a little while ago but had some issues with Bluetooth and NFC so I flashed back to the original firmware using the dload folder and 3 button method. The installation seemed to go through fine but get's stuck booting at the vodafone logo. It then takes me into eRecovery where it attempts to download latest version over wifi but fails. I don't really know where to go from here because I can't access the internal sd card because the phone won't boot. I can access fastboot but don't really know what to do from there.
stevemacer10 said:
Can someone please help. I'm getting desperate now. I flashed a Nougat build a little while ago but had some issues with Bluetooth and NFC so I flashed back to the original firmware using the dload folder and 3 button method. The installation seemed to go through fine but get's stuck booting at the vodafone logo. It then takes me into eRecovery where it attempts to download latest version over wifi but fails. I don't really know where to go from here because I can't access the internal sd card because the phone won't boot. I can access fastboot but don't really know what to do from there.
Click to expand...
Click to collapse
Stevemacer10 Hello, I hope to be keen to help, because it happened to me the same thing, with two days of stomach ache for it. In wanting to load Android on my Nougat Huawei P9 Plus VIE-C02, with VIE-L09C605B354 and VIE-L29C185B320 I went into semi-brick or brick, or was only in bootloader, the screen with the green man to speak. No avail various ways, including via microSD-Fastboot or ADB to do restart your phone. Then, to my previous experience with a Huawei tablet, I logged on to the 'https://www.dc-unlocker.com/' site, and essend already registered, I bought 15 credits (15 Euros), for the 'option' DC Phoenix Firmware write ', valid for 72 hours, in addition to the program and downloaded the' DC program Phonix v29 '(https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial) following the related tutorial. Obviously procured the original firmware 'VIE-L09C02B133' or even lower versions, you'll have to unpack in a folder of your preference. Unfortunately, despite having used with DC Phoenix the original firmware was always also blocked me. At that point I wanted groped with a firmware that you can find on the same site of the DC-Unlocker (https://files.dc-unlocker.com/user.html?v=files/57694006a60d7) by downloading the firmware 'VIE_AL10B_M00A063_Factory_firmware_China_Nonspecific_Android_6.0_EMUI_4.1 .dgtks', which I loaded with DC-Phoenix on the phone. Rebooting of a minimal mode of andorid, I did not see well either. I went back into bootloader, as well as devone be made the previous steps that I have already described to you, and this time with DC-Phoenix I loaded on the phone firmware L09C02B128 and everything went well. Attention and keep in mind that just as I happened to me, the serial number of your phone is changed, to me has happened in '0123456789ABCDEF' and there was no way to change it, so as, while having the unlocked bootloader can not longer charge the TWRP recovery in order to then have root permissions. Until reading the paragraph '(Optional) Phone numbers REPAIR', I went to that point on the site 'http://hcu-client.com/'. Also here are sadly bought 8 credits (8,00 Euro) in order to work with the program 'HCU-Client v1.0.0.0115', you need to download and unpack, then follow the various instructions, which are not difficult when you have to be walked through the modding, otherwise you do even more damage. Let me know what you did and how it went to the method. I hope also good for you. In summary we want Euro 15 for Phoenix whose duration of operations applies to 72 hours and 8 Euro per HCU-Client, it can only use this for 24 hours.
P.S .: Obviously if you follow my instructions and all these signs you do so at your own risk, esonerandomi from every possible and accidental deterioration of the situation and the damage to your phone. Sorry for my English, whose translation has made Google translator.
---------- Post added at 12:59 AM ---------- Previous post was at 12:33 AM ----------
I wanted to say that the change of the serial number does not work well. The serial number has been changed from what I've shown you above, but was not put one I added that I had from the sales box. I write support and maybe let you know what they tell me. See you soon.
Hi Grlshia,
Thanks for getting back to me. It's such a minefield playing with all these different regional variants. I have though, managed to get it completely fixed. I just gave in and took it into the local Vodafone store and fortunately there happened to be one of the tech experts in there that owned a P9. He took it off me and within about 5 minutes he had completely restored it. He told me he just did a factory reset by holding down vol+ and power. I'm sure I had tried this myself to no avail previously but that's what he said he did.
stevemacer10 said:
Hi Grlshia,
Thanks for getting back to me. It's such a minefield playing with all these different regional variants. I have though, managed to get it completely fixed. I just gave in and took it into the local Vodafone store and fortunately there happened to be one of the tech experts in there that owned a P9. He took it off me and within about 5 minutes he had completely restored it. He told me he just did a factory reset by holding down vol+ and power. I'm sure I had tried this myself to no avail previously but that's what he said he did.
Click to expand...
Click to collapse
Stevemacer10 hello, I'm glad you've solved the problem. Unfortunately I'm still fighting because, for now I can only and even to load its firmware, but if you want to try to load the TWRP recovery for later obtain root permissions, it always fails. From what seems to understand me and certainly due to the fact that the bootloader unlock code now is different from what I have, because as I told you the serial number has changed and if I request a new unlock code, it stops notiziandomi the procedure that there is inconsistency between this number and the IMEI. For now I do not know what to do and how to proceed. I hope that over time can still solve my problem. A good evening to you :good:
i'v been throw it
after updating my p9 plus with a firmware that is not sutable to my area
my phone restarted and ask for an account wich ok but the problem was that the software not working properly and missing a keyboard.
and will not go to recovery mode to try another software.
this sloved by downloading a sutable correct software and unzip it into an SD card folder (i create) called dload, then swich off the device and turn it back on while holding three bottons (power+v up+v down) 10 to 15 sec. and the phone directly read from the SD card and start updating a new firmwarw.
try it.
it success with me , hope it work wth u
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
tolerant said:
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
Click to expand...
Click to collapse
dmccort said:
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
Click to expand...
Click to collapse
Good luck, i did read that it might be possible to install the base firmware back to it and then update again.
Im sure we are not the only people this has happened to and if you succesfully do this, maybe consider making a full step by step guide so to help others.
Fingers crossed
:good:
Will do my best.. So far it's been a major. I've managed to flash a working stock ROM and boot up. But there are a few things to smooth out. Such as, I have no IMEI number now and the build is C900, also the bootloader is modified.
To get it to boot I had to use DC- Phoenix to flash a factory firmware(Chinese) which I had to pay for. Then I flashed a stock vie-l09c432b181 ROM over the top.
To repair the IMEI I'll have to use HCU, which I'll have to pay for as well. But that's ok. If I can get my original IMEI back, I can use the original unlock code I got earlier this year, otherwise I'll have to get a new one based on a new IMEI.
I can repair the bootloader and region code using twrp etc. so that's not a problem.
I'm actually using the phone to write his reply, so I can at least use it.
Once I have it all 100% working I'll try to put together a full step by step.
Cheers.
Well, I have a working phone. But, it'snot stable. Having trouble with mobile connection, sms, mms, 4g etc not staying connected. So wont be doing any write-ups just yet.
Not until it's stable.
I'm wanting to return it to complete stock now. And that requires trying to find an oeminfo file for C706 (New Zealand).
Will add more as I get there. Sorry.
I had the same problems. All I did is updated the phone with the firmware you want via Twrp . Be warned that it will replace the recovery back to stock. Also clear the cache and etc.
I had a similar issue with SRK tool, bootlooping, won't flash new firmwares, lost all the stock apps and diagnostic tools.
I'm now stuck on a TEST-KEYS build with no NFC or Bluetooth.
My solution was to throw the piece of junk in a drawer, forget about it and I went and bought a Pixel XL instead - a phone that is properly supported and gets updates quickly.
After much messing and a headache I finally got to c432b370
And everything back to normal
tolerant said:
After much messing and a headache I finally got to c432b370
And everything back to normal
Click to expand...
Click to collapse
How did you succeed?
I am stuck on TEST-KEYS but I am not able to flash other roms on it. When I go to recovery, the update process stops after a while
Sent from my VIE-L09 using Tapatalk
Hey all- after noticing my Netflix wouldn't work despite being a WW plastered phone, I discovered that my phone was actually a flashed CN version. I noticed that I can't receive updates- security or otherwise, which was a big motivating factor for me to try and fix it.
Eventually, I posted on Reddit because I was fed up
My build is (was) - WW_16.0650.1908.12_0
One dude sent me to this video- and since I have dealt with rooting before on my Nexus 4 I decided to try it out.
"
ASUS ROG 2 FULLY CONVERTED GLOBAL ROM WITH WORKING THEMES AND UPDATES"
I can't post links because my account is currently too new.
I followed the guide exactly, but when I got to the part where it said to use ADB, my attempt to boot the rootww190812.img failed- someone said to try on B instead, that also failed. It said it "failed to load/authenticate boot image.
From now it has been bootlooping into the Qualcomm
"qualcomm crash dump mode"
"waiting for flashing ramdump"
And I can not boot the device. I can still reach Fastboot, but that is all.
How can I fix my phone- preferably including continuing the boot process but at this point i'd be happy just to have a working phone again.
Edit: I have found factory reset- but i'm not sure if I should do it, or if I risk simply undoing and having to re-do the initial global reflash.
Edit 2: factory reset says WW_I001D and says it will go back to 1908.12. it should be safe I assume-
Edit 3: changing back to A allowed it to boot without factory reset- but it still won't root, build is now WW_16.0640.1908.12_0
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279
This guide ended up helping me- I got it fixed, delete this post if you want.
I was happily use my Note 9 N960N(Korean set) after I rooted it about a year ago. Few days ago I saw a new ver of Magisk(old ver 17.2 flashed w/TWRP) at Magisk manager and wanted to update but hesitate. I backup a few important file like whatsapp, SMS & contact list before I carry on further. Today I decided to update the Magisk and my fear was right, after it reboot my Note 9 stuck at "Samsung" logo. I let it there initially and after a while it remains at same place. I tried to switch it off by press the power button but no response. It won't switch off after I tried, 10, 20 and 30 seconds. I found out there is a way to reboot it by holding "power + volume down". I successfully got it boot to recovery to TWRP.
I thought it maybe the Magisk was corruptted during update so I download the Magisk zip v19.3. Then I booted to TWRP and installed the Magisk zip. I reboot the Note 9 after Magisk installed. Again I was stuck at Samsung logo. I thought maybe the sequence was not correct; beside the Magisk there maybe need few more so I followed the root sequence(skip root); 1. Magisk 2. no-verity-opt-encrypt-6.0 3. RMM-State_Bypass_Mesa_v2
Same problem, I stuck at Samsung logo. As early problem, I couldn't switch it off by pressed the power switch. I have to reboot to TWRP and use its interface to power off the phone. I have new problem this time; once I pressed the power button to power on the phone, it will goes to TWRP straight away. Tried few times and it remain the same problem. The last action what i did is flashed a new TWRP v3.3.1-0-crownlte and it didn't help either.
My Note 9 has 2 problems;
1. go to TWRP recovery straight after press power button to power up the phone.
2. stuck at samsung logo after user TWRP to reboot.
There is one more thing I didn't pay attention previously, the "mount" in the TWRP what is supposed to mount? It "mount" the SD card when it last to flash zip files.
Appreciated anyone can helps, thanks.
Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.
If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?
user109 said:
If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?
Click to expand...
Click to collapse
Phone will factory reset after flash stock regardless odin or smartswitch. Of course you can still flash oreo. But flashing stock should be the last resort.
Rosli59564 said:
Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.
Click to expand...
Click to collapse
You did mention to flash a different kernel, what will it be the most suitable?
I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:
user109 said:
I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:
Click to expand...
Click to collapse
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!
N1NJATH3ORY said:
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!
Click to expand...
Click to collapse
Hi N1NJATH3ORY, I did google around the screenlock loop problems and most of them done with 1) simple reboot 2) boot to safe mode 3) use "samsung "findmymobile". A most common solution; "wipe". A few issues raised at Samsung forum but not helpful; "call Samsung support".. There was an interesting article which suggested the problem is from google itself. Here is the link; https://www.androidpolice.com/2019/12/12/google-pixel-pin-lock-screen-loop-help/
"If the encryption of the "Synthetic Password Key blob", which needs to be decrypted in order for the unlock process to be resolved, is not able to retrieve a stored decryption key if it was corrupted." from the article. I'm not sure if this is the cause but from logic point of view it's possible. I believe the bloody Samsung knew this problem since day one but because it's not a"common" issue Samsung just swipe under the carpet.
What I did on my note 9 last action was reflash the oreo, if in the process of flashing the "Synthetic Password Key blob" has been wiped out then it may explain this screenlock loop problem, which I hope not to happen. I'll be screwed if it did. :crying:
I'll wait its battery to drain out to see what happen even though I doubt if any change..
As expected, the drained out of battery did not help, my note 9 remains locked. The only way is to try out new method and with high risk which will wipe out my data. Fortunately the new method work! Not only it overwrite the lock screen loop and also disable the google device lock.(One of the method I tried during my lockscreen loop which is useless. It creates an extra problem on top of the problem) I got all my data intact and allow me to do all backup. :highfive:
summary: update Magisk is not a full proof. The risk is 50% it will brick the phone. My advise is to backup every dan internal data before finger press the Magisk "update" especially it remaps the image! Manager APK is okay to update. I learned from the hard way and almost lost the whole dan data in my Note. You have been warned!
Gdhhs
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.