Related
Ok, this is hard to explain.
My phone was original a honor 8 from china, then 2 years back I made the rebrand to european version lrd09 6.0 , then I flash to emui 5.0 nougat. I was perfectly fine with that over 2 years, I live in argentina and it never ask me for update.
Now I am on vacation on italy (europe), and one update was available, I update my device, first update 400 mg file, all ok. Then a next update was available of 700mg, I did not thought it could have been a problem because my phone had a european version, so I did it.. and it enter in boot loop until it enters the recovery, I try to download latest version and recovery but it does not work.
How can I recover my phone? I guess I let one image version of emu5 when everything worked fine in my computer and not sure if in my phone too.
But now I dont have twrp working, only the original huawei recovery, it has bootloader and I guess the rebrand stays.
I love my pictures with this phone, and this was my first day from my vacation, I want to cry
The only solution that I can think off, is to buy a new honor8 or something with similar good camera and price, then use that and back into argentina try to recover my phone and sell one of the two.
There is another solution?
AngelLestat said:
Ok, this is hard to explain.
My phone was original a honor 8 from china, then 2 years back I made the rebrand to european version lrd09 6.0 , then I flash to emui 5.0 nougat. I was perfectly fine with that over 2 years, I live in argentina and it never ask me for update.
Now I am on vacation on italy (europe), and one update was available, I update my device, first update 400 mg file, all ok. Then a next update was available of 700mg, I did not thought it could have been a problem because my phone had a european version, so I did it.. and it enter in boot loop until it enters the recovery, I try to download latest version and recovery but it does not work.
How can I recover my phone? I guess I let one image version of emu5 when everything worked fine in my computer and not sure if in my phone too.
But now I dont have twrp working, only the original huawei recovery, it has bootloader and I guess the rebrand stays.
I love my pictures with this phone, and this was my first day from my vacation, I want to cry
The only solution that I can think off, is to buy a new honor8 or something with similar good camera and price, then use that and back into argentina try to recover my phone and sell one of the two.
There is another solution?
Click to expand...
Click to collapse
Generally... A factory reset after the update if there is a bootloop solves the problem for me
boris dmello said:
Generally... A factory reset after the update if there is a bootloop solves the problem for me
Click to expand...
Click to collapse
Wow, that it would be way more simple that I imagine, thanks for answer.
So.. I need to do this?
https://www.youtube.com/watch?v=jFM64qW7Wsw
What it does the option wipe cache partition does? it may help?
If I wipe data, I lose my pictures located in the main memory card? Or these remain in the dcim folder?
Or for that I need Android Data Recovery and cross fingers?
If i make a factory reset, then I can update my honor in europe to emui5 without this happening to me again?
The fact that it has the bootloader, it may block me to do this?
boris dmello said:
Generally... A factory reset after the update if there is a bootloop solves the problem for me
Click to expand...
Click to collapse
Ok, I tested, it complete the factory reset to the 100%, then I reboot, but the boot loop continues
The factory reset I did, it is possible that the smartphone have go back to the chinese lrd 00 version? impossible I guess, it should have returned to the factory european version that it had with emui4...
So not sure why this did not work.
I have heard that the Chinese variants which are rebranded to L09 gets stuck in a bootloop after a certain EMUI 5 update. I guess the same has happened with you. Before I can help you any further, can you confirm if your bootloader is unlocked. To check it, if your device is powered off, hold down your volume down button and immediately plug the device to a computer. If you're in a bootloop, hold the power button for a force reboot and as soon as the screen goes black hold down volume down and connect your device to PC.
hackslash said:
I have heard that the Chinese variants which are rebranded to L09 gets stuck in a bootloop after a certain EMUI 5 update. I guess the same has happened with you. Before I can help you any further, can you confirm if your bootloader is unlocked. To check it, if your device is powered off, hold down your volume down button and immediately plug the device to a computer. If you're in a bootloop, hold the power button for a force reboot and as soon as the screen goes black hold down volume down and connect your device to PC.
Click to expand...
Click to collapse
Hi, thanks for helping me, ok. I did what you ask me.
After doing that, it show me a white screen with the android robot image and it said:
FastBoot Rescue Mode
Please connect usb to your computer and open hisuite (i dont have hisuite in this notebook)
In red: Phone Unlocked
FRP unlock.
I want to tell you that I check the memory flash card that I have in the honor 8, and like I thought, there is an image that I did with the twrp, but I guess I dont have twrp anymore.
Maybe many things that you told me, I will not be able to do it until I return from my vacation, because in this PC, I dont have android studio, or hisuite, or all the plugins that I remember to use when I rebrand this phone.
But maybe I can do it anyway. I dont remember if I have to download the whole android studio to install TWRP.
AngelLestat said:
Hi, thanks for helping me, ok. I did what you ask me.
After doing that, it show me a white screen with the android robot image and it said:
FastBoot Rescue Mode
Please connect usb to your computer and open hisuite (i dont have hisuite in this notebook)
In red: Phone Unlocked
FRP unlock.
I want to tell you that I check the memory flash card that I have in the honor 8, and like I thought, there is an image that I did with the twrp, but I guess I dont have twrp anymore.
Maybe many things that you told me, I will not be able to do it until I return from my vacation, because in this PC, I dont have android studio, or hisuite, or all the plugins that I remember to use when I rebrand this phone.
But maybe I can do it anyway. I dont remember if I have to download the whole android studio to install TWRP.
Click to expand...
Click to collapse
Nah, you don't need to install the whole Android Studio just for ADB/Fastboot. Grab the installer (I made) from here: https://github.com/hackslashX/ADB-F...ster/versions/adb_fastboot_installer-1.0s.exe
Get Huawei 32-bit drivers: https://github.com/hackslashX/ADB-F...master/versions/drivers/huawei-drivers-32.zip
Get Huawei 64-bit drivers: https://github.com/hackslashX/ADB-F...master/versions/drivers/huawei-drivers-64.zip
(You only need one of the above drivers)
With all utilities installed, you can now easily flash TWRP.
For firmware, please tell me the complete build number for your device i.e. FRD-L09XXX (what are those three Xs).
hackslash said:
Nah, you don't need to install the whole Android Studio just for ADB/Fastboot. Grab the installer (I made) from here: https://github.com/hackslashX/ADB-F...ster/versions/adb_fastboot_installer-1.0s.exe
Get Huawei 32-bit drivers: https://github.com/hackslashX/ADB-F...master/versions/drivers/huawei-drivers-32.zip
Get Huawei 64-bit drivers: https://github.com/hackslashX/ADB-F...master/versions/drivers/huawei-drivers-64.zip
(You only need one of the above drivers)
With all utilities installed, you can now easily flash TWRP.
For firmware, please tell me the complete build number for your device i.e. FRD-L09XXX (what are those three Xs).
Click to expand...
Click to collapse
Thanks for the links and info.
Although I am not sure how to know the build number, I guess the update to emu5 was something like 431.. or something like that, but I am not sure, I did this two years ago.
I need to know the build number to install TWRP or recover my phone?
If it is bricked, not sure how I can access to the build number.
Hi guys, good evening from the Philippines.
This is my first time making a thread here at xda but ever since, I have been visiting this site for the past years and the guides here are pretty helpful. Let me cut the chase. Guys, I really need your help.
I just rooted my huawei gr5 2017 and installed twrp to downgrade the firmware. I wiped all the partitions as usual and started flashing the firmware. Installing firmware is really time consuming and I fell asleep during the process (Well I am just a normal college student so i assume you know how tiring the whole day is) so I was really upset when I booted my phone in the morning and got stuck to your device is unlocked and can't be trusted. I tried reviving my phone by reflashing the firmware but it wont go to twrp. eRecovery only pops up with the download and restore recovery option. I tried fastboot but then it wont engage. I think everything was literally wiped, the whole system gone and my phone is like in a coma state. Please respond asap if you have any ideas regarding this matter.
*apologies if I can't send a picture of it but please do share your ideas if you have one
charles.darryl said:
Hi guys, good evening from the Philippines.
This is my first time making a thread here at xda but ever since, I have been visiting this site for the past years and the guides here are pretty helpful. Let me cut the chase. Guys, I really need your help.
I just rooted my huawei gr5 2017 and installed twrp to downgrade the firmware. I wiped all the partitions as usual and started flashing the firmware. Installing firmware is really time consuming and I fell asleep during the process (Well I am just a normal college student so i assume you know how tiring the whole day is) so I was really upset when I booted my phone in the morning and got stuck to your device is unlocked and can't be trusted. I tried reviving my phone by reflashing the firmware but it wont go to twrp. eRecovery only pops up with the download and restore recovery option. I tried fastboot but then it wont engage. I think everything was literally wiped, the whole system gone and my phone is like in a coma state. Please respond asap if you have any ideas regarding this matter.
*apologies if I can't send a picture of it but please do share your ideas if you have one
Click to expand...
Click to collapse
Can you boot into fastboot? To do so plug the USB into the phone and computer. Then hold power and volume down. As soon as screen goes black let go of power but keep holding volume down. It should boot into fastboot. From there tell me the status of Phone and FRP. Is it locked or unlocked. Next, was your phone in EMUI 8 before or 5? And to which version were you trying to downgrade to?
Hi everyone,
I'm having an issue with my 7 pro (1911). This is my 1st Oneplus as I used a Mi 5 before, the flash procedure was much easier without this A/B mess.
So I somehow messed up a new install of pixel experience with blu_spark kernel and twrp and found myself with the qualcomm crash error. Trying to get back into fastboot with the button combination (was able to save it once in it) the phone restarts and got stuck in edl mode. I noticed it's recognized as 9008 in the PC so I said okey this is nothing I'll just use the MSMTool to get it back on again.
Went through the xda Mega thead procedure, had no problem getting the phone to connect to the tool, however, first unexpected thing I encounter is the fact it stops with a SHA256 doesn't match error, and fails to send op2.img. I verified the ops file to make sure it has no errors and it was good. I then checked "disable sha256" box and it goes normally with the flash this time. Except in the end instead of restarting into the system it restarts into edl mode again and if the cable is still attached starts flashing again. This loop keeps going on forever.
I checked everywhere the only other thing I found that hints at a possible solution was doing an SMT download (based on this thread from OP6). Having an EFS backup already in one of my TWRP backups I went ahead with the procedure. Everything goes normally with the sha256 box disabled. it takes longer than upgrade mode (it flashes also to b slot), it finishes fine till the end. I disconnect the phone to boot it but it's still stuck in EDL mode!!! pressing any combination of button only keeps restarting the phone in EDL; when connected to the pc you see it going off then on in device manager.
The only idea I have left is waiting for battery to die, which could take forever and I have no idea if that'll work
Things I tried/used :
Qualcomm drivers are the latest from microsoft server v2.1.2.2. Tried some other ones but no change.
Pressing any combination of buttons (up + down + power, up + power, down + power) for multiple minutes doesn't change anything (it only hurts your fingers lol)
Before the issue the phone was at around 40%, I don't think the problem was battery charge, but I still tried connecting to official charger for some time but no boot.
I tried using multiple cables, ports (usb 3 and 2 from front of pc), tried on a laptop with both usb 2 and 3, all give me the same results, sha256 fails, without the check it flashes but no boot or response.
I redownloaded the MSMTool multiple times from both the Mega thread and newer one with oos 10 images, even the chinese image, all of them give the exact same issue. The only one that didn't work was the TMobile image, saying it's the wrong image (tried it just to be sure my phone wasn't originally a TMO converted, as it's 2nd hand).
Tried starting a normal flash in MSMTool and leaving it on that loop (flash, finish, restart again in EDL, flash...) all night but still found it flashing in the morning, never booted to system.
I found some people in the forums having the same symptomes (but quite rare compared to others), only 2 said they found a solution:
OP7P (this guy fixed the issue by charging his phone) https://forum.xda-developers.com/showpost.php?p=80329855&postcount=83
OP6T (this guy discharged his phone completely then connected it and it booted) https://forum.xda-developers.com/showpost.php?p=79079192&postcount=5
OP7 https://forum.xda-developers.com/showpost.php?p=81183765&postcount=41
OP7 https://forum.xda-developers.com/showpost.php?p=81185793&postcount=43
OP6 https://forum.xda-developers.com/showpost.php?p=81308571&postcount=88
OP6 https://forum.xda-developers.com/showpost.php?p=79445923&postcount=203
I'm making this thread maybe someone who had the same issue can show me how he solved it, or if not and my last resort works (complete battery discharge) hopefully stays as a helpful history to someone else.
Thanks.
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Click to expand...
Click to collapse
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
ANY NEWS>?
i also have an OP6T
used MsmDownloadTool V4.0_factory_mcl_op1_patched
with
rev_OverSeas_181226_1920_release_disable_OTA-BLOCK_Signed_fp1812260627_cve2018-12-01_ufs_9.0.11
and
fajita_41_O.18_181226.ops
phone was stock.
Proceeded to flash custom rom etc.
Now since then i decided i wanted stock again to try new custom rom etc. and,
i booted twrp and just wiped everything like a mad man.
i have had this happen before.
Currently, it will and can boot into any mode such as fastboot recovery(TWRP) edl and device state/secureboot are both unlocked/enabled
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
from there i booted twrp
(was my reccovery still)
mind that i wiped everything like a mad man and i lost my ADB AND FASTBOOT AND AS WELL AS MY EDL MODE PRIVILEGES(2 PCs, a couple cables tried and the phone is still not being recognized in any of the mentioned modes ), and after doing what i mention if you can get into fastboot mode you may be in luck, however if you can get back into any other mode.(Or fastboot flash a stock rom, adb sideload etc)
im still here waiting my usb otg type c because the usb wont recognize with the adapter to micro usb. Now ive never had a usb otg type c adapter before, but i know i could never get the micro usb (universal) to adapt my otg with a, "type C" type adapter and see the storage device(usb) being recognized by android. So i will reply when it arrives and i can attempt to flash stock again via otg twrp with oos zip. (THIS HAS TO BE AN A10 ISSUE WITH TWRP BEING FAIRLY RECENT IN RELEASES AND CAUSING IT TO NOT BE RECOGNIZED AFTER PERFORMING A, "FULL WIPE")
hopefully the otg for usb c is going to be recognized by twrp still.
if all else fails and your still under contract warranty, just light the **** on fire and run it over and pay the $40 deductable and take it as a $40 lesson and have them send you a new one(or upgrade depending on eligibility etc.)
---------- Post added at 10:06 PM ---------- Previous post was at 10:00 PM ----------
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
agree
im using a tmoblie variant with msm from above
---------- Post added at 10:27 PM ---------- Previous post was at 10:06 PM ----------
https://twitter.com/NTAuthority/status/1115496145051164672
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
No still stuck in EDL mode.
Johndoesmoked said:
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
Click to expand...
Click to collapse
I don't know if you saw my last comment but I had even opened the phone up to disconnect the battery ribbon, hoping that would get it out of EDL but it didn't. However I didn't do the trick with the buttons when connecting it, I'll try this after disconnecting the battery. Also if that didn't work I'll leave it on rubber bands like you said, nothing to lose anyway. Thanks for the tips. I'll let you know what's up.
How did you know when the phone was dead while on rubber bands, do you verify if it still gets detected on the PC ?
Yeah i had did the rubberbands for a lil more than couple days and like i said i let it sit for about a day without the bands on after i had a good 20+ hours with em on then reapplied bands for about 20 hours.my phone was completely discharged during that process( OP6T).
Upon doing this i lost access to my recovery img.
Phone only boots fastboot (even if i choose recovery, it was previously working)
So now i still cant recognize in fastboot or edl.
GOT my OTG type c and put oos on usb, but as i said now my twrp isnt booting, so i shouldnt have depleted the battery as now i have no possible recovery access modes . Aside from that, im trying to figure out more info on the device and will reply in a day with what i may come to find out.
My phone did get detected because it started up as soon as i plugged into pc.
battery seems un-accessible but may have to take this apart.
I am figuring this out and i will get back to you. I need more tech assistance from a friend in the repair industry to disassemble without destroying it tomorrow or sometime friday.
This is going to have to be some sort of an intricate process to diagnose this supposed "HARD BRICK"
:Have to correct myself
talked to my brody at tmobile to see wassup with the warrenty etc.
basically its not covered under warrenty when you mess with software, blah blah i figured anyway, and he basically advises (OR more so "i didnt tell you anything like that!"- laughing) to literally run it over with your car or just smash the screen, and file the claim without issue...
BUT THE ISSUE IS ITS GONN COST YOU $99 to get a new OP6T via Assurant
your device might be the same, or even more costly,
i would prefer to avoid all costs, spending more money, not trying to..
Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Click to expand...
Click to collapse
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Lefren said:
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Click to expand...
Click to collapse
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
thedeadfish59 said:
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
Click to expand...
Click to collapse
Yeah so sad, probably the internal memory has a slight % chance it gets corrupted or something...
Since my story in the OP I bought a used 1913 that's a bit cheaper coz of external scratches and took its motherboard for my cleaner original phone. It's been working like a charm since.
hi everyone last night i plug my phone for charging after a while i came back and see crash dump mode i switch off the and try to unbrick via msm tool 1st attempt everything fine auto reboot after progress complete it stuck in oneplus logo after that i tried to redo all thing now i faced this error on MSM TOOL PLEASE HELP ME I CHANGED THE CABLE USB PORTS DRIVER REINSTALL BUT STUCK AT THIS POINT. when i uncheck sha256 downloading start but it does not stop again and phone did not auto reboot help please
My Google Pixel 2 (running May version already) was working fine until last week. I don't recall if my memory ran out, but I don't think so. After using it for a while, I drove home, and when I got home, the phone was off. Thinking that the battery was just dead, I plugged it into a charger , turned it on, and didn't think too much about it. When I next looked at my phone, it was stuck on the G logo with a loading bar under there.
I tried turning the phone off, charging it more, etc.
I contacted google support and they told me that the only way is to factory reset (i want to keep my data, though). I began looking online and came across sideloading OTA, which seemed to be the only way to save my data. I am not that tech savvy and wasn't sure how to do it, so for a second time I contacted google support, they told me that for sideloading, I should go to a UBreakIFix, an authorized Google repair place. I made an appointment and when I got there, I asked them to help do a sideload of the OTA or more information about it, and the technician didn't even seem to know what that is. Then after a long diagnosis, they also told me that i have to factory reset and wanted to charge me $80 to do so...
I decided to come home and try to sideload myself.
Techno Bill had some very detailed explanations on how to do it, and some of the google support threads also gave other suggestions as well. I appreciate all of them and went through everything.
While trying to sideload, I came across a few issues:
- First, I tried to sideload from my laptop (windows 10), which only has USB C ports. Apparently, this sideload doesn't work when you use USBC to USBC cables, so it kept getting stuck at verifying update package.
- Then, when I realized that, I switched to a desktop running windows 7. And my USB C to USB A cable. But my computer wasn't able to read my Pixel 2. Thinking that it was that my computer was too old, I went to my parents house. (I later found out that it was my USB C- USB A cable that didn't work)
- Then at my parents house running Windows 8, my sideload worked, but at 94%, it always said completed with Status 0. Then it would prompt me to reboot, which it did, but the it keeps getting stuck on the G loading screen.
- Then I tried going to a friend's house, windows 10, and tried the same, and every time, it would complete with status 0 at 94%. but it continues to get stuck at the G loading screen
Then I kept searching and tried different OTAs like P version or previous versions, etc. and they would usually say "installation aborted" because the version is a downgrade. Also tried powering off and on 7 times,
I thought that maybe I needed to use a new version of Google OTA, which just released this week (June version), but for some reason, it still tells me that it's a downgrade, when my phone's current version is the May version.
Does anyone have any idea what I should do at this point?
I would really like to keep my data.
Thanks in advance.
wallychang said:
My Google Pixel 2 (running May version already) was working fine until last week. I don't recall if my memory ran out, but I don't think so. After using it for a while, I drove home, and when I got home, the phone was off. Thinking that the battery was just dead, I plugged it into a charger , turned it on, and didn't think too much about it. When I next looked at my phone, it was stuck on the G logo with a loading bar under there.
I tried turning the phone off, charging it more, etc.
I contacted google support and they told me that the only way is to factory reset (i want to keep my data, though). I began looking online and came across sideloading OTA, which seemed to be the only way to save my data. I am not that tech savvy and wasn't sure how to do it, so for a second time I contacted google support, they told me that for sideloading, I should go to a UBreakIFix, an authorized Google repair place. I made an appointment and when I got there, I asked them to help do a sideload of the OTA or more information about it, and the technician didn't even seem to know what that is. Then after a long diagnosis, they also told me that i have to factory reset and wanted to charge me $80 to do so...
I decided to come home and try to sideload myself.
Techno Bill had some very detailed explanations on how to do it, and some of the google support threads also gave other suggestions as well. I appreciate all of them and went through everything.
While trying to sideload, I came across a few issues:
- First, I tried to sideload from my laptop (windows 10), which only has USB C ports. Apparently, this sideload doesn't work when you use USBC to USBC cables, so it kept getting stuck at verifying update package.
- Then, when I realized that, I switched to a desktop running windows 7. And my USB C to USB A cable. But my computer wasn't able to read my Pixel 2. Thinking that it was that my computer was too old, I went to my parents house. (I later found out that it was my USB C- USB A cable that didn't work)
- Then at my parents house running Windows 8, my sideload worked, but at 94%, it always said completed with Status 0. Then it would prompt me to reboot, which it did, but the it keeps getting stuck on the G loading screen.
- Then I tried going to a friend's house, windows 10, and tried the same, and every time, it would complete with status 0 at 94%. but it continues to get stuck at the G loading screen
Then I kept searching and tried different OTAs like P version or previous versions, etc. and they would usually say "installation aborted" because the version is a downgrade. Also tried powering off and on 7 times,
I thought that maybe I needed to use a new version of Google OTA, which just released this week (June version), but for some reason, it still tells me that it's a downgrade, when my phone's current version is the May version.
Does anyone have any idea what I should do at this point?
I would really like to keep my data.
Thanks in advance.
Click to expand...
Click to collapse
You might make sure you have the most current Android platform tools.
Ermmm, just the same issue as mine, my memory just a little ran out. Google's June's Full OTA for pixel 2 is a broken one, as I posted in the google forum thread 50683931 (I can't post link for now, sorry), but not replies.
So, you can do the factory reset now (via official recovery) or maybe you need to wait for July's Full OTA, unless Google guys fixed June's pixel2 full OTA time issue, it's a log time already .
BTW, I am still waiting for the fix.
wallychang said:
My Google Pixel 2 (running May version already) was working fine until last week. I don't recall if my memory ran out, but I don't think so. After using it for a while, I drove home, and when I got home, the phone was off. Thinking that the battery was just dead, I plugged it into a charger , turned it on, and didn't think too much about it. When I next looked at my phone, it was stuck on the G logo with a loading bar under there.
I tried turning the phone off, charging it more, etc.
I contacted google support and they told me that the only way is to factory reset (i want to keep my data, though). I began looking online and came across sideloading OTA, which seemed to be the only way to save my data. I am not that tech savvy and wasn't sure how to do it, so for a second time I contacted google support, they told me that for sideloading, I should go to a UBreakIFix, an authorized Google repair place. I made an appointment and when I got there, I asked them to help do a sideload of the OTA or more information about it, and the technician didn't even seem to know what that is. Then after a long diagnosis, they also told me that i have to factory reset and wanted to charge me $80 to do so...
I decided to come home and try to sideload myself.
Techno Bill had some very detailed explanations on how to do it, and some of the google support threads also gave other suggestions as well. I appreciate all of them and went through everything.
While trying to sideload, I came across a few issues:
- First, I tried to sideload from my laptop (windows 10), which only has USB C ports. Apparently, this sideload doesn't work when you use USBC to USBC cables, so it kept getting stuck at verifying update package.
- Then, when I realized that, I switched to a desktop running windows 7. And my USB C to USB A cable. But my computer wasn't able to read my Pixel 2. Thinking that it was that my computer was too old, I went to my parents house. (I later found out that it was my USB C- USB A cable that didn't work)
- Then at my parents house running Windows 8, my sideload worked, but at 94%, it always said completed with Status 0. Then it would prompt me to reboot, which it did, but the it keeps getting stuck on the G loading screen.
- Then I tried going to a friend's house, windows 10, and tried the same, and every time, it would complete with status 0 at 94%. but it continues to get stuck at the G loading screen
Then I kept searching and tried different OTAs like P version or previous versions, etc. and they would usually say "installation aborted" because the version is a downgrade. Also tried powering off and on 7 times,
I thought that maybe I needed to use a new version of Google OTA, which just released this week (June version), but for some reason, it still tells me that it's a downgrade, when my phone's current version is the May version.
Does anyone have any idea what I should do at this point?
I would really like to keep my data.
Thanks in advance.
Click to expand...
Click to collapse
lonelinsky said:
Ermmm, just the same issue as mine, my memory just a little ran out. Google's June's Full OTA for pixel 2 is a broken one, as I posted in the google forum thread 50683931 (I can't post link for now, sorry), but not replies.
So, you can do the factory reset now (via official recovery) or maybe you need to wait for July's Full OTA, unless Google guys fixed June's pixel2 full OTA time issue, it's a log time already .
BTW, I am still waiting for the fix.
Click to expand...
Click to collapse
I don't know about the OTA but there's nothing wrong with the full system zip.
OP, did you ever get this resolved? Either getting the phone booted or getting access to your data?
My phone is in a similar boat, stuck at G logo and empty loading bar.
Some updated was downloaded and the phone requested for a restart, restarted and now stuck at G logo.
I have tried to flash the OTA, but stuck at verify package, tried on two different Windows 10 machine, latest platform tools from Google, two different usb A to C cable, but same behaviour.
There are some valuable data I would like to retrieve. Does anyone have and suggestion on what I should do next?
You can try to flash the last Android 9 OTA, then the first Android 10 OTA, and then the latest OTA on Google's website. That should fix the issue.
The above doesn't work, as old OTAs fail. Every single Android 10 OTA failed for me, or worked/installed ok as sideload (July and Aug since they weren't older) but gave me the G logo for hours. The Android 11 beta 3 preview DID WORK: developer.android.com/preview/download-ota Clearly a software bug.
*If you get this bug please try the Android 11 OTA *
For reference, I got the G logo/boot fail situation not after updating but after my battery drained entirely, phone shut down, i plugged in phone and booted and then it sat there. So battery related software bug (???)
For fixes like what you all are attempting, you shouldn't be using OTAs. In fact, if you are rooted, it's best to never use OTAs and always update with the latest full system image.
Go to Google's site for Pixel factory images and download the latest image for your device, make sure you have the latest version of platform-tools on your computer, then follow my instructions from this thread:
https://forum.xda-developers.com/showpost.php?p=83009945&postcount=2
Whenever it asks if you want to unlock or wipe data, press N (no).
If all the previous failed attempts haven't somehow corrupted or already wiped your data, you should be able to boot back into your phone normally.
"If you are rooted"
Yeah, if i had root or even an unlocked bootloader I would have had five thousand other options.
jallenhayslett said:
For fixes like what you all are attempting, you shouldn't be using OTAs. In fact, if you are rooted, it's best to never use OTAs and always update with the latest full system image.
Go to Google's site for Pixel factory images and download the latest image for your device, make sure you have the latest version of platform-tools on your computer, then follow my instructions from this thread:
https://forum.xda-developers.com/showpost.php?p=83009945&postcount=2
Whenever it asks if you want to unlock or wipe data, press N (no).
If all the previous failed attempts haven't somehow corrupted or already wiped your data, you should be able to boot back into your phone normally.
Click to expand...
Click to collapse
Unlocked bootloader + Magisk + TWRP + custom kernel here, I've always used OTAs without a problem. Just have to use fastboot to boot the TWRP image and reinstall after an update. Flashing radio and bootloader are easy too.
its not the usual reboot loop, it gets not even that far, its stuck to the "this phone is jailbroken,hit power to pause" after that it just reboots,while empty.
i tried to switch it off, to ensure loading, but keeping the powerbutton 10sec pressed,is impossible,there is not enough time.
i tried to switch into the bootloader, and say switch off, well it goes back into the loop 2sec later,since it got a bit power, it tries its nonsense.
i tried differend loading methods, pc usb, usb pure (2.1mAh), and the oneplus speedloader adapter with the red cable.
what happend before, well it got empty, and switched off,the apps and such didnt change for about a year, it worked, and thats it.
the accu cell got changed about a year ago, by my insurance company, the old one balooned. so they changed it,meaning its not even a old cell.
trying fastload in bootloader,didnt help getting it charged,anything else just relooped.
iam open for suggestions.
thanks and regards
Noal
I think ur phone might be soft bricked or idk. But I'm pretty sure the problems didn't caused by the new battery.
Seems the phone didn't recognize the /system/ or something on twrp that says "There's no system installed" coz i've faced that (no system installed) before.
If u can manage boot into bootloader, try to fastboot a twrp.img and flash a stock firmware.
If u can't, or let's just say you really feel ur phone in fked up state, try to reflash everything with MSM Download Tool.
Here's some threads I found :
Soft Bricked?
I apologize as I've been out of flashing ROMs for over 4 years now. I unlocked my OP6 bootloader, added TWRP, the flashed Lineage 11. One of my apps wont play nice with root so I tried to go back to stock. I tried to use TWRP 3.5.2_9-0 to...
forum.xda-developers.com
[OP6][LATEST 10.3.8] Collection of unbrick tools
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Credits goes to them.
Hope it helped.
NoalFey said:
its not the usual reboot loop, it gets not even that far, its stuck to the "this phone is jailbroken,hit power to pause" after that it just reboots,while empty.
i tried to switch it off, to ensure loading, but keeping the powerbutton 10sec pressed,is impossible,there is not enough time.
i tried to switch into the bootloader, and say switch off, well it goes back into the loop 2sec later,since it got a bit power, it tries its nonsense.
i tried differend loading methods, pc usb, usb pure (2.1mAh), and the oneplus speedloader adapter with the red cable.
what happend before, well it got empty, and switched off,the apps and such didnt change for about a year, it worked, and thats it.
the accu cell got changed about a year ago, by my insurance company, the old one balooned. so they changed it,meaning its not even a old cell.
trying fastload in bootloader,didnt help getting it charged,anything else just relooped.
iam open for suggestions.
thanks and regards
Noal
Click to expand...
Click to collapse
It is much better to state the status of your device briefly. Like are you on OOS or custom ROM, unlocked bootloader, with custom recovery installed, magisk installed, etc. Then tell the story on what you did or what happen before your phone got the issue you stated. Then maybe someone can help you in more specific way.
Like Azhar_Fahry recommended, I also recommend using MSM tool and revert back to original state like you first bought your device.