I downloaded the December factory image and updated the same way I always do:
fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img
fastboot reboot-bootloader
fastboot flash radio radio-walleye-g8998-00253-1809191716.img
fastboot reboot-bootloader
fastboot update image-walleye-pq1a.181205.002.zip
After the standard update flow, the device rebooted and gave me the usual verified boot Orange warning screen, then I pressed power twice to move past it and the device loaded into the bootloader with "ERROR: LoadImageAndAuth Failed: Load Error" at the bottom.
Now when I try to boot, I don't get the verified boot screen, just the bootloader with "ERROR: Slot Unbootable: Load Error"
The bootloader no longer enumerates as a USB device, so I can't try reflashing the bootloader or flashing it to slot B (I am on slot A) or anything else. It does still say "Device State: unlocked" but I can't seem to do anything else.
I have tried multiple USB A->C cables and a USB C->C cable and multiple host machines, but none of them will get the Pixel 2 to show up in Device Manager.
Have I had a hardware failure? Is this any kind of known issue and is there any way to recover it?
Thanks.
same here. found any fix?
I also had the same issue. I have not yet been able to find a solution, tried multiple PCs and even tried booting into Linux and still got nothing. I talked to google support and they are cross-shipping me a replacement device right now. However, if anyone found a fix that would be great so I don't lose the data on my old phone (yes I know I should've been doing backups).
Edit: Was on a Google Pixel 2, going from September to December security patch. Tried updating using the flash-all.bat without the -w flag set. Completely stock except for a Magisk install.
Never found a fix, but once I described the symptoms Google was very quick to offer a warranty replacement. I was upgrading from the August image to the December image.
Hi! Just for info - I got to same situation, but I was able to fix it but I don't know, how I did it I was trying to fix it all evening, but without success. So I let phone turned on till morning. Phone was totally discharged at morning, only notification LED was blinking red, when I was trying to turn phone on. So I chared it with original charger about half hour, then connect it to PC and it was detected, so reflash update and my phone is alive again...
Maybe this will help to someone
To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.
I'm in the same boat, tried flashing dec factory image over my october install (failed on step 4/5) now fastboot is broken and I have the same "ERROR:Slot unbootable: Load Error".
drmason said:
I'm in the same boat, tried flashing dec factory image over my october install (failed on step 4/5) now fastboot is broken and I have the same "ERROR:Slot unbootable: Load Error".
Click to expand...
Click to collapse
Does your desktop/ laptop recognize your Pixel 2 in bootloader mode?
If it does, then there is almost 99% chance you can get it to boot up with some flashing.
If it doesn't there's literally no way for us to recover it.
yuva_cool said:
Does your desktop/ laptop recognize your Pixel 2 in bootloader mode?
If it does, then there is almost 99% chance you can get it to boot up with some flashing.
If it doesn't there's literally no way for us to recover it.
Click to expand...
Click to collapse
yeah i guessed so, so i initiated a replacement with the google support, went without an issue. Flashing stuff for years, but this is the first that went down.
Also tried to deplete the battery, didn't work for me... won't turn on at all anymore.
I too have been flashing since the last 2 years. But this was the first time everything went to hell. I mean this is ridiculous. And as far as I have noticed many people are facing this issue after flashing the December patches. I'm guessing something on the Google's end messed up things.
I applied for a repair and they picked up my device. Will know in a few days if they are kind enough to repair it for free.
yuva_cool said:
I too have been flashing since the last 2 years. But this was the first time everything went to hell. I mean this is ridiculous. And as far as I have noticed many people are facing this issue after flashing the December patches. I'm guessing something on the Google's end messed up things.
I applied for a repair and they picked up my device. Will know in a few days if they are kind enough to repair it for free.
Click to expand...
Click to collapse
Kind? I hope it's not a thing of kindness. As far as I know a unlocked bootloader doesn't void warranty... and they provide 24 month of warranty so I expect a free replacement.
My replacement should be arriving soon and if they will charge me the full price again this will be my last pixel I guess. Also they didn't argue or asked more questions at all on the hotline after I told them it died after flashing december patch. I guess they know whats going on...
See here:
https://forum.xda-developers.com/pixel-2/help/bricked-pixel-2-locked-bootloader-t3876792
or here:
https://forum.xda-developers.com/pixel-2/help/slot-unbootable-load-error-device-locked-t3842095
my mobile is bricked too! This seems to be a horrible problem for a few of us
I got mine completely repaired for free. They couldn't recover my data but they did get it up amd running. They even changed my display as it was very muched burned in and also changed the smi tray. I didn't even report these 2 issues. Im actually very happy with their response. Got the device back in 8 days. Loving the Pixel team.
same thing happen to me just now, currently my pc cant detect the phone, seems like dead end.
koax88 said:
same thing happen to me just now, currently my pc cant detect the phone, seems like dead end.
Click to expand...
Click to collapse
Claim for an RMA. They are approving for bootloop issues. I guess December patches screwed up things for a lot of us.
yuva_cool said:
Claim for an RMA. They are approving for bootloop issues. I guess December patches screwed up things for a lot of us.
Click to expand...
Click to collapse
the thing is, i bought it from 3rd party seller, because google not selling pixel in my country. is there any other way for me to fix this phone? or let google fix it for me?
tried linux, and multiple setup of usb cables, still nothing.. and i havent sleep yet.. any advice? is there any other way to force pc to recognized pixel bootloader? im at lost now
I have the same problem after flashing the Dec factory image on my pixel 2.
And Here is a detail that is not mentioned above. The 'flash-all' script failed and show:
Sending 'vendor_a' (359956 KB) FAILED (Write to device failed in SendBUffer() (Unknown error))
and now your phone still can be recognized by windows or not?
koax88 said:
the thing is, i bought it from 3rd party seller, because google not selling pixel in my country. is there any other way for me to fix this phone? or let google fix it for me?
Click to expand...
Click to collapse
They do rma even you dont bought it in Google store.
In my case they asked me several things about the failure, rooting and all that stuft. After proofing my words with my imei and online logged in data the gave me a RMA.
Thanks to Google. Best support for me.
Related
I flashed the Google assistant some time ago and everything was fine but yesterday I decided to do some minor build prop edits and accidentally bricked my phone. Now that's fine because they have multiple ways of unbricking the T-Mobile LG v20. But when I tried to unbricking it using LGup nothing works because it registers my phone as a pixel and now my phone can't be restored. So take it from me..Don't do it!!! It isn't worth the loss. I have a brick now. An official lg v20 brick. Sigh
EDIT:
IM EDITING THIS TO ADD WHAT I DID.
Here's the story
I was trying to revert to stock with the build prop so I could upgrade my phone. so I edited the prob and removed the lines I added to get Google assistant in the first place but it crashed and when I entered TWRP to push the build prop. When that didn't work I flashed the stock tot file which got my phone working but I wanted to upgrade so I found the page in XDA to flash the kdz with LGup which I was doing but half way through it failed and Twrp was gone which started this snow ball effect.
Do you not have TWRP you can reboot into, and re-flash a backup or new ROM?
CharlzO_2000 said:
Do you not have TWRP you can reboot into, and re-flash a backup or new ROM?
Click to expand...
Click to collapse
Nope, the only thing my phone does it boot into the mode where it says "Firmware update" mode. I really think I destroyed my phone.
remix435 said:
Nope, the only thing my phone does it boot into the mode where it says "Firmware update" mode. I really think I destroyed my phone.
Click to expand...
Click to collapse
Take it to the store and tell them it happend when the phone was updating.
slayerh4x said:
Take it to the store and tell them it happend when the phone was updating.
Click to expand...
Click to collapse
That's actually a pretty good idea. I'm going as soon as TMobile opens.
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
Leonarddale said:
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
Click to expand...
Click to collapse
This.
remix435 said:
I flashed the Google assistant some time ago and everything was fine but yesterday I decided to do some minor build prop edits and accidentally bricked my phone. Now that's fine because they have multiple ways of unbricking the T-Mobile LG v20. But when I tried to unbricking it using LGup nothing works because it registers my phone as a pixel and now my phone can't be restored. So take it from me..Don't do it!!! It isn't worth the loss. I have a brick now. An official lg v20 brick. Sigh*
Click to expand...
Click to collapse
That is very strange, I recently bricked my phone to the point where I didn't have a system at all on it. When you boot to firmware update mode (power + volume up) and pluged it in LGUp recognized it instantly. You have the correct DLL for your device right?
shadowxaero said:
That is very strange, I recently bricked my phone to the point where I didn't have a system at all on it. When you boot to firmware update mode (power + volume up) and pluged it in LGUp recognized it instantly. You have the correct DLL for your device right?
Click to expand...
Click to collapse
My issue was that when I flashed the assistant mod it turned my device name into " google pixel" so when I hooked it up to lgup it read it as a pixel and failed the restore every time. That was the issue I couldnt change the name of my devixe back to the v20.
Leonarddale said:
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
Click to expand...
Click to collapse
I disnt have anything on my phone. No twrp and I couldnt install it. The assistant mod changed my device name to PIXEL and when id connect it to the pc it read as a pixel and failed every update I LG V20 I pushed to it..that was a new type of brick lol. But I told t mobile that if I what happened and I got another one.
These old assistant mods would be taken down. The only thing needed to enable it without spoofing a phone as a Pixel is adding "ro.opa.eligible_device=true" to build.prop, and the Google app updated via Play Store.
remix435 said:
My issue was that when I flashed the assistant mod it turned my device name into " google pixel" so when I hooked it up to lgup it read it as a pixel and failed the restore every time. That was the issue I couldnt change the name of my devixe back to the v20.
Click to expand...
Click to collapse
That's the thing my phone didn't have a system on it at all and LGUp read it as what it was. When you on the firmware screen it should read based on hardware ID right? Have you tried using LG bridge? Are you on the T-Mobile variant?
This is a contributing factor in why these companies lock bootloaders. People do stupid things because they don't know what they're doing and then others encourage them to just return it and get a new one and lie. Not cool at all. How about don't root your phone if you don't know what you're doing.
markbencze said:
This is a contributing factor in why these companies lock bootloaders. People do stupid things because they don't know what they're doing and then others encourage them to just return it and get a new one and lie. Not cool at all. How about don't root your phone if you don't know what you're doing.
Click to expand...
Click to collapse
WTF! With your logic no one would learn anything.
My phone was rooted just fine. How was I suppose to know that after I flashed the stock build prop my phone was going to stay as a pixel device?? That wasn't stupid of me that was trial and error. Something stupid is if I did it again. No one specified that my phone would stay as a pixel device, go read the instructions and tell me where it says that. Also, I have "Jump on demand" so I used one of my jumps to get a brand new phone..So I paid a price for it. It wasn't just "me lying and getting a free phone" I still paid for it I paid for my mistake and Yes initially I lied but still paid and am still paying for this phone. Plus I have an s7 edge and a Huawei honor note 8 all rooted and have never ran into any issues. Why?? Because I never did what people instructions told me not to do. I always follow instructions. I've been rooting phones since I was a milk drinker all the way back to the G1 days. I'm very careful but if instructions don't cover all the basis then what?? PEOPLE, including me should continue to root and try new things. But you can't blame them if YOU(not you in particular but in general) as a developer make something and can't catch all the bugs(it isn't The developers/modders fault either)..Modding is a giant community of trial and error. The only people at fault are idiots who don't read and do some ****. Other than that we are all out here finding our way with these new devices. So yes, I have a new v20 that I paid for with MY "Jump on demand" plan that is now rooted and unlocked. Now am I going to use the Google assistant mod again?? No, because that would be stupid of me. Now get off my post.
I was just warning people so they wouldn't make the same mistake as me.
Whats the stupid part is how you managed to erase TWRP and lose access to fastboot on your device. Not that your changed something in build.prop. His logic is not flawed, whatever you did to lose access to the two essential parts of having a rooted phone is the flaw here.
Also simply doing build.prop edits should not make you lose access to TWRP nor being able to access fastboot - or did you relock your bootloader?
twistedvip said:
Whats the stupid part is how you managed to erase TWRP and lose access to fastboot on your device. Not that your changed something in build.prop. His logic is not flawed, whatever you did to lose access to the two essential parts of having a rooted phone is the flaw here.
Also simply doing build.prop edits should not make you lose access to TWRP nor being able to access fastboot - or did you relock your bootloader?
Click to expand...
Click to collapse
In stead of assuming what happened with my device how about y'all ask me the details first. But coming off the bat assuming that I just did foolishness is asinine.
I was trying to revert to stock with the build prop so I could upgrade my phone. so I edited the prob and removed the lines I added to get Google assistant in the first place but it crashed and when I entered TWRP to push the build prop. When that didn't work I flashed the stock tot file which got my phone working but I wanted to upgrade so I found the page in XDA to flash the kdz with LGup which I was doing but half way through it failed and Twrp was gone which started this snow ball effect.
So once again where's the stupidity on my part when I didn't know that my phone was still going to be labeled a a pixel after a factory reset? Please, both of you have several seats in the back.
All I'm doing is warning people about what could possibly happen. Y'all can miss me with your unnecessary opinions and comments.
No I appreciate you wanting to warn the community, but you most certainly did not post that story. You posted saying you got bricked from doing edits to your build.prop and then because of using a Google assitant mod you are hard bricked. Post that entire story as a warning because even having your phone appear as a Pixel won't do any harm - but flashing a .kdz and having it fail midway may indeed cause harm. Lack of details causes much misinformation to spread around quickly
twistedvip said:
No I appreciate you wanting to warn the community, but you most certainly did not post that story. You posted saying you got bricked from doing edits to your build.prop and then because of using a Google assitant mod you are hard bricked. Post that entire story as a warning because even having your phone appear as a Pixel won't do any harm - but flashing a .kdz and having it fail midway may indeed cause harm. Lack of details causes much misinformation to spread around quickly
Click to expand...
Click to collapse
My bad I'll edit it. And apologies for the response tone.
It's called taking responsibility. You had a phone with root and did something stupid. Instead of taking responsibility you lie and tell them the phone is defective. That is 100% your fault. I bet it worked fine before you started messing with it. Whatever man I'm gonna let this be but you can bet that when these companies look at the supposed drfrctive returned phones and see they have been tamperred with and that people are being dishonest to get a new phone when they're the sole reason the phone stopped working, eventually they will all say screw it and just lock everything down.
Hopefully you learned from this.
markbencze said:
It's called taking responsibility. You had a phone with root and did something stupid. Instead of taking responsibility you lie and tell them the phone is defective. That is 100% your fault. I bet it worked fine before you started messing with it. Whatever man I'm gonna let this be but you can bet that when these companies look at the supposed drfrctive returned phones and see they have been tamperred with and that people are being dishonest to get a new phone when they're the sole reason the phone stopped working, eventually they will all say screw it and just lock everything down.
Hopefully you learned from this.
Click to expand...
Click to collapse
Actually the phone had a few random rebootsa and use to freeze on stock. I decided to keep it because of the note 7 fiasco and I was too frustrated and pissed to return it and then they ran out. So this was well over due. But once again you know nothing Jon snow. And yes I did lie but this device already had issues. Soooo???
I bought the original Pixel from Verizon and that was a complete waste. Then the Pixel2 was released, and I bought it online (directly from Google). I've had it for a long while.
The first thing I did was oem unlock and flash twrp, Magisk, and Elemental X. I was running the stock rom and just let all of the updates slip past (updating the kernel of course) and had a few issues so I thought I'd factory reset and update the phone.
But I didn't take the sim card out...
When the phone rebooted it behaved *exactly* like the original Pixel if you had the sim card in. It specifically sets up according to what Verizon wants on the phone.
Now, when I go into the developer settings, the oem unlock is greyed out!!!
Does Verizon lock Pixel phones regardless of its origin?
I'm not completely stupid, this just doesn't make sense... Anyone else have this issue?
Honestly, I didn't think something like that was possible. Can anyone here confirm the hardware is the exact same? Is it possible Verizon signing keys can overwrite default/official Google keys?
Or will the phone behave as normal if I reset without the sim in?
Gonna try it and report back after work (gotta wait another 8 hours or so as of writing this).
Exactly how did you update it, and I mean every step you took?
The steps, specifically as possible:
downloaded the original image from Google (https://developers.google.com/android/images)
I grabbed [8.1.0 (OPM1.171019.013, Jan 2018] as that was the version I was running
Extracted zip, extracted the zip inside the zip (to get boot.img)
flashed stock recovery to boot_a and boot_b (using instructions found at https://www.androidexplained.com/pixel-2-restore-stock-recovery/
Reboot
Checked phone to see if it worked fine
Rebooted to [stock] recovery to see if it would load
This is where things get a little sketchy, as I could only confirm the stock recovery was in place. I only saw dead Andy with "No Command"
Reboot to system- everything looks okay so far...
Let phone automagically download and install any/all updates through the System Settings.
Make sure I want to- and then actually, factory reset phone (I did *not* remove the sim card)
Went through the initial setup
wait for it...
At this point, all Verizon default apps were installed on phone during the initial setup (not at user request/Google Play Store):
MyVerizon, Messages+, etc.
Raised an eyebrow, went to settings, enabled Developer Options, checked OEM unlock...
As of this point I have not been able to check if I can [fastboot oem unlock]
Another thing is that the flash-all.sh script refused to work properly, even with a root shell. I made sure to double check usb debug was enabled, udev rules in place, and checked, double checked cables and ports.
I can, however, confirm that I am on OPM2.171026.006.C1
I haven't memorized the list at the Google Images (*.img type) link above, but I'm pretty sure this one is listed as the generic Pixel 2 and not the Verizon variant. I will still attempt to unlock using the fastboot method... let's hope it still works...
Anywho, I work nights so, I won't be able to test anything out until after work, waffle house, and a nap. But I will indeed be back to keep this updated.
allcaps33 said:
The steps, specifically as possible:
downloaded the original image from Google (https://developers.google.com/android/images)
I grabbed [8.1.0 (OPM1.171019.013, Jan 2018] as that was the version I was running
Extracted zip, extracted the zip inside the zip (to get boot.img)
flashed stock recovery to boot_a and boot_b (using instructions found at https://www.androidexplained.com/pixel-2-restore-stock-recovery/
Reboot
Checked phone to see if it worked fine
Rebooted to [stock] recovery to see if it would load
This is where things get a little sketchy, as I could only confirm the stock recovery was in place. I only saw dead Andy with "No Command"
Reboot to system- everything looks okay so far...
Let phone automagically download and install any/all updates through the System Settings.
Make sure I want to- and then actually, factory reset phone (I did *not* remove the sim card)
Went through the initial setup
wait for it...
At this point, all Verizon default apps were installed on phone during the initial setup (not at user request/Google Play Store):
MyVerizon, Messages+, etc.
Raised an eyebrow, went to settings, enabled Developer Options, checked OEM unlock...
As of this point I have not been able to check if I can [fastboot oem unlock]
Another thing is that the flash-all.sh script refused to work properly, even with a root shell. I made sure to double check usb debug was enabled, udev rules in place, and checked, double checked cables and ports.
I can, however, confirm that I am on OPM2.171026.006.C1
I haven't memorized the list at the Google Images (*.img type) link above, but I'm pretty sure this one is listed as the generic Pixel 2 and not the Verizon variant. I will still attempt to unlock using the fastboot method... let's hope it still works...
Anywho, I work nights so, I won't be able to test anything out until after work, waffle house, and a nap. But I will indeed be back to keep this updated.
Click to expand...
Click to collapse
USB debugging is only for ADB, and has nothing to do with fastboot commands. When you attempted to run the flash-all script, were you in ADB or bootloader? In ADB it will fail, because it doesn't recognize fastboot commands. However, in the bootloader, if it's not recognizing fastboot commands, that's a whole different animal. OTAs, when it comes to VZW are dangerous, so it's always best to just sideload them via stock recovery. They should come straight from Google, but I'm afraid that something that you did in the entire process broke that.
In all honesty, all you really needed to do was unzip the latest factory image, run the flash-all script while you were still unlocked, and be done with it. The -w in the script would have taken care of the factory reset for you, as it's a full wipe.
Let us know if what you tried worked, and best of luck ?
I was in the bootloader, I realize adb and fastboot are 2 different entities.... thus far, I'm still locked out... working it now...
An update to this mess:
Still working with known exploits to try and get back to where I was. Looks like I'm gonna have to pull from CVE or ExDB.
Any suggestions from the pros?
allcaps33 said:
I was in the bootloader, I realize adb and fastboot are 2 different entities.... thus far, I'm still locked out... working it now...
Click to expand...
Click to collapse
I do apologize for underestimating your knowledge. That being said, an OTA can't re-lock the bootloader without permission, as that would completely wipe userdata. And, neither can the presence of a SIM card. I fear that, with everything that you did, as far as getting your phone as clean as possible, you may have put the device in limbo, so to speak, and the OTAs, combined with vzw's penchant for locking bootloaders, may have made it susceptible to becoming a Verizon device. Just a thought.
I totally agree with you.
I'm just completely confused how this happened...
As you said, with an unlocked bootloader, it *might* have been possible that through some kind of bug it may have taken something VZW specific... But... The OTA packages don't actually contain the entire ROM do they?
From what I noticed, they're almost all under 80 MB, while the actual ROM packages are (on average) 1.5 GB.
At what point could this crossover happen?
(The reason I bring up package sizes is that would be the most likely reason for an overwrite... I think...)
Can I probe you for more theories? Out of the box solutions never work, perhaps you might trigger ideas within the community.
Thank you very much @DuckRuckus for your help!
Still to this point attempting anything within fastboot seems to just not work...
I can get "fastboot devices" and "fastboot reboot bootloader" to work. But that's about it. No other commands issued get so as a response.
Just picked this up for the significant other's bday. Bootloader unlocked it with the instructions from @ipdev, and can report that method works. Can't get root.
Does anyone have this device and have achieved root? I'm a bit perplexed, even flashing a patched boot img isn't getting Magisk on there the way that it should.
Thanks!
Important to Note that the 460 has the exact same EVERYTHING as the 450, including build #s. They just gave it double the internal space is the only difference I've seen.
UPDATE: Just bricked the lil' guy. Since the device is encrypted with every system file having a -sign behind it, I went and frolicked around trying to get Magisk on there via ADB. The only way to do that was to patch the boot-sign .img and since I got the new Magisk, I let it patch, flashed, and now voila, nothing but a bootloop. Off to DM Verity my way out of it lol.
Articul8Madness said:
Just picked this up for the significant other's bday. Bootloader unlocked it with the instructions from @ipdev, and can report that method works. Can't get root.
Does anyone have this device and have achieved root? I'm a bit perplexed, even flashing a patched boot img isn't getting Magisk on there the way that it should.
Thanks!
Important to Note that the 460 has the exact same EVERYTHING as the 450, including build #s. They just gave it double the internal space is the only difference I've seen.
UPDATE: Just bricked the lil' guy. Since the device is encrypted with every system file having a -sign behind it, I went and frolicked around trying to get Magisk on there via ADB. The only way to do that was to patch the boot-sign .img and since I got the new Magisk, I let it patch, flashed, and now voila, nothing but a bootloop. Off to DM Verity my way out of it lol.
Click to expand...
Click to collapse
If it is close enough to 450, and you can get into fastboot, you can try and boot the linked boot.img
fastboot boot m19_ST16C7BNv205.img
Same modifications I had to use to get the first boot image I found to work with BNTV450.
avb, mtk type and signature removed.
Also patched with Magisk 19 (canary release)
For good measure.
https://drive.google.com/open?id=1LgtB2JKCKwLJ64mUlij5Cb_cJrBi8Av1
PS.
Tested above modified v2.0.5 boot.img on BNTV450 running v1.0.2, so it should work on BN v1.0.2 and up.
Good Luck.
Cheers.
PPS.
Just ordered one. (Should show up in 2-3 days.)
Hey @ipdev make sure you get the insurance for 2 years. Shouldn't be more than 6-8 bucks. You're going to need it.
I went ahead and tried all the versions that you posted on your OP for flashing; only one was successful - the rest softbricked on the flash. When I went back and flashed the 460 stock on it, it was a different stock and never did run back right - kept getting the blinking red border ring and unfortunately lost the serial #, flash, and every possible entry on the "About Nook" tab - essentially glitching it out. Since I''d only had it for 12 hours, I took it back and swapped it out for a fresh one
So the issues I'm seeing so far are:
1. It's encrypted and says as such - this is what is causing the probs later in flashing and you can't deactivate it from what I see so far without a custom recovery.
2. Patching the boo img via MagiskManager will softbrick it, and I tried with both 18 & 19 inase there were issues with one over another.
3. The device will try to auto update ASAP OTA so make sure you don't connect it to the internet before you disable that function.
4. There is no "official firmware" you can download - B&N will only let you direct download the firmware through notifications. Granted, if you want the only one I was able to find I can post it (it says its Oreo 8.1.0 but it looks different than what comes on the device and its running a crappy Android Go)
5. Its easy to unlock the bootloader per your instructions but after you get the Orange State it takes an awful long time for basic boot (which is more of a personal irritant than a problem, lol)
6. If you patch and flash the boot img with Magisk, you will completely lose the screen. Keep in mind though, if you plug it into the computer you will keep hearing the connect/disconnect chimes. It will keep doing that and neither adb or fastboot will function (even though you can fastboot devices command and it will show a Daemon output).
7. Booting into recovery becomes harder and harder from adb and fastboot once you unlock the bootloader - pressing volume rocker and power does not do it at all.
I'll try your new files and see what happens...I think the guy got a hell of a lot of potential and needs a nice streamlined rom or at the very least root to get the bloat off so its faster. But I think it says something on its crippled nature when the guys at B&N say it ain't worth it in the long run - apparently they aren't as great as even the nook HD line.
Articul8Madness said:
Hey @ipdev make sure you get the insurance for 2 years. Shouldn't be more than 6-8 bucks. You're going to need it.
I went ahead and tried all the versions that you posted on your OP for flashing; only one was successful - the rest softbricked on the flash. When I went back and flashed the 460 stock on it, it was a different stock and never did run back right - kept getting the blinking red border ring and unfortunately lost the serial #, flash, and every possible entry on the "About Nook" tab - essentially glitching it out. Since I''d only had it for 12 hours, I took it back and swapped it out for a fresh one
So the issues I'm seeing so far are:
1. It's encrypted and says as such - this is what is causing the probs later in flashing and you can't deactivate it from what I see so far without a custom recovery.
2. Patching the boo img via MagiskManager will softbrick it, and I tried with both 18 & 19 inase there were issues with one over another.
3. The device will try to auto update ASAP OTA so make sure you don't connect it to the internet before you disable that function.
4. There is no "official firmware" you can download - B&N will only let you direct download the firmware through notifications. Granted, if you want the only one I was able to find I can post it (it says its Oreo 8.1.0 but it looks different than what comes on the device and its running a crappy Android Go)
5. Its easy to unlock the bootloader per your instructions but after you get the Orange State it takes an awful long time for basic boot (which is more of a personal irritant than a problem, lol)
6. If you patch and flash the boot img with Magisk, you will completely lose the screen. Keep in mind though, if you plug it into the computer you will keep hearing the connect/disconnect chimes. It will keep doing that and neither adb or fastboot will function (even though you can fastboot devices command and it will show a Daemon output).
7. Booting into recovery becomes harder and harder from adb and fastboot once you unlock the bootloader - pressing volume rocker and power does not do it at all.
I'll try your new files and see what happens...I think the guy got a hell of a lot of potential and needs a nice streamlined rom or at the very least root to get the bloat off so its faster. But I think it says something on its crippled nature when the guys at B&N say it ain't worth it in the long run - apparently they aren't as great as even the nook HD line.
Click to expand...
Click to collapse
If you just need a temporary root, I put up this guide a few minutes ago since there was no definite resource about rooting this device. https://forum.xda-developers.com/nook-7/how-to/how-to-temporary-root-bntv460-t3963304
turtleletortue said:
If you just need a temporary root, I put up this guide a few minutes ago since there was no definite resource about rooting this device. https://forum.xda-developers.com/nook-7/how-to/how-to-temporary-root-bntv460-t3963304
Click to expand...
Click to collapse
I appreciate it, but I've since taken it back. Tell you what though, maybe I'll pick up a used one on ebay and try it
Hello Guys,
i had bought an Huawei P20 about an year ago. Now you know with all of this "USA-Huawei" Trouble going on, the thought came to my mind that i better start unlocking bootloader and be prepared to flash custom rom if worst come to worst. so far, so good.
now i started looking around if there is an easy method of getting the bootloader unlocked. but oh my, the huawei company is very friendly to us users and say "no, you wont get any unlock code from us anymore". so screw that.
now i want to try some experimental stuff. it looks like this:
my Smartphone has currently the version EML-L29 8.1.0.168(C432). I bought some Credits (i think it is that thing for $4) from DC-Unlocker. Yeah yeah i know, there they say "no support for Huawei P20!!!". But i still want to try. Well i tried, but it doesnt work - what you should expect.
now i read from some other website that there is another way of unlocking it. i only read it diagonal but the one thing i read was the information "unlocking bootloader is only possible till firmware version june 2018". so i jumped to an maaybe interesting conclusion about unlocking the phone with DC-Unlocker or HCU (whatever, i guess maybe both use the same method anyway).
if i do an rollback to the old firmware version *before* June 2018 on the device, wouldnt it be possible to do the unlock? Because the security patches that preventing it unlocked arent on the device then.
So what i have done so far is loading the old firmware version 8.1.0.128(C432). But the source is saying that it is coming from "Asia" but in the next line it reads "Asia, Europe" etc. - do they mean that this version is universal or do i run in trouble if i install one that is having the wrong area?
the next thing that kinda baffles me... all guides are sayin "copy the extracted dload folder to your sd-card". even the p20 guides do that. but.. well you know, the p20 device doesnt even have sd-card support. so how are you intended to use it then? i wonder about that a bit.
i dont think that without unlocked bootloader, flashing an original OTA full update would be impossible. but im not really sure how. there is this shady menu you can reach if you call this strange numbercode. but im very unsure if that will really work out. the phone (it is still a phone without SD-Card-Support) even has the option "apply update from sd-card". so im wondering how this feature they implemented in the original software is intended to use at all. maybe i should push the dload folder on the internal storage? i dunno.
i read about another possibilty of flashing stock roms. they say you can do it per adb command. so no problems would be here, i have adb and the hisuite and all already set. but i have absolutely no idea if that is possible without unlocked bootloader. so the questions arose from my mind are those:
- does an stock rom image from possibly/maybe asia would do any harm to my device like it is getting unbootable or anything like that?
- is it possible to flash an image older android stock rom with methods like this special menu on the device or the adb load?
- do you all think that my plan of downgrading the phone in order to get the bootloader code would work?
i'm looking very forward to your answers )
no_monday said:
Bootloader Unlocking through Downgrade possible?
Click to expand...
Click to collapse
No. Sorry. There's no solution. Reason: It would appear in this forum within minutes and thousands of people would be happy to unlock their bootloaders. Many Huawei-Owners here on XDA invested a lot of brain power to find a way. Noone succeeded. No bootloader code, no unlock.
If you still want to play around with firmwares, please inform us about any progress.
Jan Philipp said:
No. Sorry. There's no solution. Reason: It would appear in this forum within minutes and thousands of people would be happy to unlock their bootloaders. Many Huawei-Owners here on XDA invested a lot of brain power to find a way. Noone succeeded. No bootloader code, no unlock.
If you still want to play around with firmwares, please inform us about any progress.
Click to expand...
Click to collapse
okay so there are basically no real information. look, i dont expect anyone to say like "oh there is an easy method xy" because i know it doesnt exist on this moment in time.
however i made an percent of an progress, it is more a thing for other interested custom rom modders out there.
i downloaded this update.zip and there are all kinds of howtos on the internet about it. the one thing i did is basically create the dload folder. then i put the extracted update.app in there. i rebooted the phone with power, vol down + vol up. i released the power button after the vibrating. the flashing screen indeed appeared! but something very strange has happened and i have no explanation what have happend.
so the emui updater appeared. there was this emui logo in the middle, the circle building up around it. but then it stopped at 5%. i really got panicked that im about to brick my device. so in an mad attempt i wanted to stop the update and power off the phone. glad i didnt do it. the phone always said if i tried to press the power button long enough "the system will crash if it is powered down". i stopped - but i tried it serveral times to stop.
now the strange thing is.. it stuck relatively long on this screen. but after a while (i guess it was 5-6 minutes) it suddenly got dark. and the battery was at 100%, so it wasnt a faulty battery. i just wondered. the phone - other than i would expect - rebooted. after a short while of the logo flashing (for about an half minute) it finally started. first i didnt have any connect to GSM Network. but after a short while that was okay too. all apps are still there. i looked at "about" and the version is still the same as before.
do someone have any imagination what has happened there? so apparently the phone *does* try to install something on this method, but the method seemed to fail. or is there any knowledge out yet for update logs that are getting generated by this process? i try to find any hint in order to tackle this problem atm.
and one thing is still on my mind.. could it be that the update is already through and i just didnt realized it yet because these other custom files werent changed? i mean that could be an possibility to say the least. anyway, i will try to use hcu now if maybe sth has changed. and i give kingoroot as well a shot if this buddy finds everything about rooting the device. maybe with root rights through exploit i can get further.
no_monday said:
okay so there are basically no real information. look, i dont expect anyone to say like "oh there is an easy method xy" because i know it doesnt exist on this moment in time.
however i made an percent of an progress, it is more a thing for other interested custom rom modders out there.
i downloaded this update.zip and there are all kinds of howtos on the internet about it. the one thing i did is basically create the dload folder. then i put the extracted update.app in there. i rebooted the phone with power, vol down + vol up. i released the power button after the vibrating. the flashing screen indeed appeared! but something very strange has happened and i have no explanation what have happend.
so the emui updater appeared. there was this emui logo in the middle, the circle building up around it. but then it stopped at 5%. i really got panicked that im about to brick my device. so in an mad attempt i wanted to stop the update and power off the phone. glad i didnt do it. the phone always said if i tried to press the power button long enough "the system will crash if it is powered down". i stopped - but i tried it serveral times to stop.
now the strange thing is.. it stuck relatively long on this screen. but after a while (i guess it was 5-6 minutes) it suddenly got dark. and the battery was at 100%, so it wasnt a faulty battery. i just wondered. the phone - other than i would expect - rebooted. after a short while of the logo flashing (for about an half minute) it finally started. first i didnt have any connect to GSM Network. but after a short while that was okay too. all apps are still there. i looked at "about" and the version is still the same as before.
do someone have any imagination what has happened there? so apparently the phone *does* try to install something on this method, but the method seemed to fail. or is there any knowledge out yet for update logs that are getting generated by this process? i try to find any hint in order to tackle this problem atm.
and one thing is still on my mind.. could it be that the update is already through and i just didnt realized it yet because these other custom files werent changed? i mean that could be an possibility to say the least. anyway, i will try to use hcu now if maybe sth has changed. and i give kingoroot as well a shot if this buddy finds everything about rooting the device. maybe with root rights through exploit i can get further.
Click to expand...
Click to collapse
It seems you have a couple of questions, pal, I answered to the first one (Bootloader Unlocking through Downgrade possible?). All I said is that it's impossible to unlock the bootloader through a downgrade. If you read all the how-to's you should have noticed that FirmwareFinder doesn'st work anymore since EMUI 9.0. This Information simply means Huawei doesn't allow us to flash updates on our own anymore like we did before. For sure there are some guides how to rollback to Android 8 but even this changes nothing to the bootloader.
Sadly I have no answer to the other questions about the strange behavior, it sounds pretty odd. Never heared something like this. But good luck fixing your phone anyway.
well i found out a couple of things now.
first thing: you know the service menu when you try to apply a zip archive from sd card? well you wont be able to use it UNTIL you use an usb-otg cable and an exFat formatted USB-Stick. Next thing to know is, you have to use the right images. there seem to be an kind of rule how this images are supposed to be and the image i found was from an russian firmware download site it was linked here in the forum in a thread. so i did choose "apply zip from sdcard" and .. IT DOES! the device rebooted, the stick flashed and the flashing process occured! and guys, im back to Version EML-L29 8.1.0.128(C432)! it is clearly stated in the build version view in settings. so.. i guess you *can* roll back even without firmware updater.
so far so good. but lets get back to the problem with the Bootloader. sadly Jan Philipp was totally right.. the bootloader cant be unlocked even in this version with the security patch of 5. may 2018. that is kinda sad. even kingoroot is still no different from before. i guess i have to search now for an way to get the system rooted. however, it must be easier on an earlier security update stage like now instead of the future versions of emui 8.1.
edit: another strange thing i discovered so far is that after this restore.. the play store wasnt able to connect to the google server until i gave permission to a few google processes to calendar and file access (i wonder what that is all about). maybe it has something to do with incompatibilities in the rom versions but now it works just fine as it should).
"unlocking bootloader with exploit is only possible till firmware version june/july 2018" does not apply to 2018's devices with kirin970, kirin980 & kirin710.
You are with kirin970.
So to unlock your kirin970, the only way for now is to wait for 3rd party seller to hypotheticaly start back their dervice:
- In the last 6 months there was only 2 'windows' which lasted 3 or 4 days where you could order your bootloader's unlock code by imei (from 5 to 124 us$).
GuestD0711 said:
another strange thing i discovered so far is that after this restore.. the play store wasnt able to connect to the google server until i gave permission to a few google processes to calendar and file access (i wonder what that is all about). maybe it has something to do with incompatibilities in the rom versions but now it works just fine as it should).
Click to expand...
Click to collapse
Google Play services require all permissions, otherwise won't work.
I also been searching on how to unlock the bootloader and found no solution or hope. I guess we are stuck with EMUI forever.
Reply from Huawei:
You can roll back to earlier versions of EMUI software, but you have to roll back one version at a time. However, our earlier phones operate exclusively on Google Mobile Services so removing it would limit the functionality extremely, however, we do have a range of new devices that no longer rely on Google Mobile Services and use Huawei Mobile Services instead - such as our P40 series.
Here are the instructions for rolling back software:
[Rollback Guideline] EMUI 9.1 (Android 9) Rollback to EMUI 9.0 (Android 9) Operation Instruction
EMUI 9.1 (Android 9) can now be rolled back to the official version of EMUI 9.0 (Android 9) using HiSuite, without downloading any intermediate packages. To ensure that the rollback succeeds, read the instructions carefully and perform the steps as instructed.
1. The following are precautions for roll-back.
a. Rolling back to an earlier version will erase all data on your device. Use an SD card, computer, or Cloud storage to back up all important data before rolling back your phone, and make sure all backed up content is complete and effective.
b. Use a computer running a Windows operating system to visit http://consumer.huawei.com/minisite/HiSuite_en/index.html and download the latest version of HiSuite. If HiSuite is installed on your computer, click the version number in the lower left corner of the page to check if it is the latest version. Make sure HiSuite version is 9.1.0.303 _OVE or above.
c. Before rolling back the phone, make sure your phone has not been upgraded using non-official updates. Otherwise, the roll-back may fail and unknown issues may be introduced. If you have used non-official packages to upgrade your phone, it is recommended that you go to an after-sales service center to roll back your phone.
d. Before rolling back your phone, make sure that your phone system has not been unlocked or rooted. If the system has been unlocked or rooted, it is recommended that you go to an after-sales service center to roll back your phone.
e. Before the roll-back, restore the phone to factory settings to make sure there is enough storage space.
f. Make sure the battery level is more than 50%.
Hi All,
I need assistance to update my EML L29 Huawei P20 phone.
The phone is Locked and FRP Lock
Issue the phone is always booting into recovery mode and not into the main screen.
I tired flashing via CMD using twrp.img file but its not writing.
Need help
I decided to load gsi via dsu loader in the settings app, I had oem unlocking enabled, and then I installed one of the gsi--it was random, I don't know too much about these types of things, like arm64 or something, at the time, so I just did the arm64 so for a bit, it was done downloading, all I needed to do was restarting the device, and then, after restarting it, it had this boot messages that says "dm-verity corruption. Your device is corrupt. It can't be trusted and may not work properly. Or, the device will power off in 5s". The device was working correctly except it just had that message everytime it boots, and it was still android 11 as normal instead of loading android 13 gsi. I tried to fix this dm-verity problems, with everything I can: I used adb and used the dm verity command (adb reboot dm-verity enforcing, adb reboot, fastboot set active other), I also did factory reset but that doesn't work, I contacted the customer services and they said as of right now, they don't provide roms or software to end user, and the only way to fix the devices with them is to send it to them and it cost 30 dollars, so i declined instead. I found these two application while on my way to research on fixing the devices: Unlocktools, and rom2box, but I am skeptical of them. I didn't found the firmware for this specific devices, but it did gave me hope that the only thing that came close is blu g91. I don't know what else to do besides use unlock tools, or rom2box, but I don't want to get my computer in danger, so I don't have that much choice.
Does anyone have a firmware file for BLU F91 5G though? I just founded one, but I can't download them, because I had to log in, but the website (Halabtech) seems kinda odd though, so I haven't log it in yet.
Nvm, I guess I'll just flash different gsi for different type of processor or something.
I Did same thing few weeks ago on my s91pro. Got same response from Blu and I can't seem to find a trusted place to get Firmware either. Sadly I don't have a pc to flash with but soon as I get my one plus device back I can try to sideload maybe.
Curios with your idea to flash again? If that works let me know please and good luck!!
My first idea was to use the dsu sideloading/vegebobo and shizuku for using gsi, my 2nd idea was to sue adb and fastboot, I would need to get gsi file, I could load either vb.meta, or just the system one instead. It took me a while because I was using outdated drivers, outdate adb, or just incorrect command. At first before all of this, I just wanna flash normal firmware, but I guess ill do that. It worked out for me, but I had problems with scren recording and wifi related in different gsi
btw, If u thinking of flash custom gsi on ur blu phone (in case if u don'twant to, I don't wanna force u or anything, just saying, so u don't have to deal with the burden) , I don't recommend using cdroid, in my expriences, wifi connected but doesn't work, and even using mobile data doesn't work either, lineageos was less worse.
Honestly with all the hassel it seems to cause I don't see it worth it. Hell even trying to fix the issue I have already seems to be a pain. I'm gonna just leave it be. Doesn't seem to cause any real issues other than the annoying warning during boottup. Which I just press the power one time and use phone as normal.
I am only using the Blu phone till I get my one plus back from warranty service. Then it's just a back up and alternate account I use for games.