Related
UPDATE: Solution below!
There is a chance the OTA will fail, as this have happened to some users already:
http://forum.xda-developers.com/nexus-9/general/nexus-9-android-n-preview-t3332715
You might be able to recover if you have USB Debugging turned on PRIOR to performing the OTA update. (Will need to flash factory image).
The problem is the factory image will require you to unlock the bootloader to flash it. To unlock the bootloader, you need to enable USB Debugging. BUT if the OTA fails, you can't boot into the OS to enable USB Debugging. You will end up with a brick.
Here's my experience:
I enrolled my Nexus 9 in the Android N Beta Preview program, and a minute later I got a notification that I have a system update. I went through with the update like any other update. I got to the part where you see an Android laying on it's back and it says "updating system" (or something to that effect) and it has a progress bar. After a few minutes, I see the same Android on it's back, but with an exclamation mark and the words "ERROR!". It would then reboot itself after a few minutes later, but get stuck at the Google logo.
If you leave everything stock, unrooted, and bootloader locked (like a good user), don't try to get the preview via OTA without enabling USB Debugging first! This way, you can at least be able to flash the factory image if the OTA takes a dive.
Since I bought the tablet on Amazon, Google is washing their hands from tech support. Instead, they gave me HTC's support line (which is currently closed). I don't know what I will have to face tomorrow morning when I call.
UPDATE: Google posted signed OTA zips that can be used to recover from this situation. You can now use adb sideload to side load the full OS in OTA form. Go to https://developer.android.com/preview/download-ota.html to download.
Will I be able to recover if this happens by unlocking the bootloader and enabling USB debugging then install Android N preview? I'm feel for you. Good luck.
kalinskym said:
Will I be able to recover if this happens by unlocking the bootloader and enabling USB debugging then install Android N preview? I'm feel for you. Good luck.
Click to expand...
Click to collapse
If you unlock the bootloader and enable USB debugging prior to installing the Android N preview (via OTA), you should be fine. You're essentially leaving yourself a backdoor to flash the factory image should the OTA fails.
Yes, I wish I know this earlier, and now I have a bricked Nexus 9 with me. :sad
Ouch, had that issue and went here looking for help. Should have waited before I tried it ?
THIS IS CRAZY! OTA should work :-\
So crazy to hear that you are all having the same issue with the Android N Developer Preview on Nexus 9!
I have had exactly the same experience today when I enrolled my device for the OTA. It downloaded and started to install fine, but got stuck with the android on his back with the red exclamation mark. It then rebooted and is now stuck on the Google logo. I have tried using adb to push files, factory reset/wipe cache & nexus root toolkit. However, I had NEVER set the OEM unlock option and that seems to have left me stuck!
I'm hoping someone will figure out an amazing fix! Just in case no one does, I called Google and as I purchased it from the play store they have offered me a replacement. Sadly I'm living in Thailand and they can only arrange it to my home country, Australia. So sorry they wouldn't help you Naddie
I didn't unlock the bootloader and I'm also facing exact same issue, my tablet is now almost bricked .
I can go to "recovery" mode, so I tried to do "adb sideload" with OTA image for MMB29V from MMB29R (got from gist.github.com/jduck/744a6c8a9042e9c792b7), but my device is already at MMB29V so it complains with below error:
"system partition has unexpected contents"
Will I be able to flash OTA image through recovery once we get it for MMB29V to AndroidN_version? And where should I get it from?
What other option do I have to recover the device?
sashinde said:
I didn't unlock the bootloader and I'm also facing exact same issue, my tablet is now almost bricked .
I can go to "recovery" mode, so I tried to do "adb sideload" with OTA image for MMB29V from MMB29R (got from gist.github.com/jduck/744a6c8a9042e9c792b7), but my device is already at MMB29V so it complains with below error:
"system partition has unexpected contents"
Will I be able to flash OTA image through recovery once we get it for MMB29V to AndroidN_version? And where should I get it from?
What other option do I have to recover the device?
Click to expand...
Click to collapse
Gee, I hope we're still on MMB29V... But since the OTA seemed to have failed during the update, the system partition may be partially whatever build this Android N preview is and partially MMB29V - which is to say ... It's completely borked for ANY OTA update to fix it via side loading.
Does anyone even have the OTA zip for MMB29V to N preview for we poor souls to try?
Sent from my iPad using Tapatalk
Hello. Sorry for my english. The same from here. I called Google and they offered me a replacement. I said yes. Waiting for a new Nexus 9. I hope you will find the solution.
Enviado desde mi Nexus 6P mediante Tapatalk
Naddie, have you contacted HTC or Google yet about getting a replacement?
My update failed too and I cannot boot. I did not have the OEM unlock switch flipped, so I can't unlock my bootloader. I chatted with Google last night and since I didn't buy it from the Google Store, they wouldn't replace it. They gave me the HTC phone number instead. I haven't tried calling them yet.
I tried updating via the beta program, but there was an error and now my Nexus 9 is softbricked. I can get to fastboot and recovery, but can't boot into Android. And, worst of all, I don't have USB debugging enabled, so I can't do an ADB flash or even OEM unlock.
Can anyone help me out?
naddie said:
There is a chance the OTA will fail, as this have happened to some users already:
http://forum.xda-developers.com/nexus-9/general/nexus-9-android-n-preview-t3332715
You might be able to recover if you have USB Debugging turned on PRIOR to performing the OTA update. (Will need to flash factory image).
The problem is the factory image will require you to unlock the bootloader to flash it. To unlock the bootloader, you need to enable USB Debugging. BUT if the OTA fails, you can't boot into the OS to enable USB Debugging. You will end up with a brick.
Here's my experience:
I enrolled my Nexus 9 in the Android N Beta Preview program, and a minute later I got a notification that I have a system update. I went through with the update like any other update. I got to the part where you see an Android laying on it's back and it says "updating system" (or something to that effect) and it has a progress bar. After a few minutes, I see the same Android on it's back, but with an exclamation mark and the words "ERROR!". It would then reboot itself after a few minutes later, but get stuck at the Google logo.
If you leave everything stock, unrooted, and bootloader locked (like a good user), don't try to get the preview via OTA without enabling USB Debugging first! This way, you can at least be able to flash the factory image if the OTA takes a dive.
Since I bought the tablet on Amazon, Google is washing their hands from tech support. Instead, they gave me HTC's support line (which is currently closed). I don't know what I will have to face tomorrow morning when I call.
Click to expand...
Click to collapse
Nexus 9 is FAMOUS for OTA's failing and leaving you with a "brick".
The good news is that the sky IS NOT falling, even with the bootloader locked and debugging OFF, you can still recover it. All you need to do is reboot into recovery, and "adb sideload" the update.zip again.
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
greiland said:
My update failed too and I cannot boot. I did not have the OEM unlock switch flipped, so I can't unlock my bootloader. I chatted with Google last night and since I didn't buy it from the Google Store, they wouldn't replace it. They gave me the HTC phone number instead. I haven't tried calling them yet.
Click to expand...
Click to collapse
The switch unflips every reboot anyway, so that wouldn't have helped you to begin with.
What "Update" would I sideload? I did my original update via OTA.
Fixed Brick on Nexus 9 OTA Android N update
I had the same problem yesterday with a failed OTA update.
I solved it by booting into Fastboot ( hold down volume up and power button until you see Fastboot options). Then choose recovery. The Nexus 9 should try to reinstall the update.
For me this worked and I now have a working Nexus 9 on Android N beta.
Hope this works for you folks !
Good to know. I just signed up for the beta program. My bootloader is unlocked from day one because I always flash the stock image of the security updates. The USB debugging is on
Sent from my Nexus 6 using Tapatalk
inthelandofnod said:
I had the same problem yesterday with a failed OTA update.
I solved it by booting into Fastboot ( hold down volume up and power button until you see Fastboot options). Then choose recovery. The Nexus 9 should try to reinstall the update.
For me this worked and I now have a working Nexus 9 on Android N beta.
Hope this works for you folks !
Click to expand...
Click to collapse
Can you please explain more detailed? Are you sure it's volume up because recovery is volume down. And what to do then in recovery?
Please, give us more info!!!!
Enviado desde mi Nexus 6P mediante Tapatalk
I am on MMB29V with unlocked bootloader, TWRP recovery, rooted. I opted in for OTA. It downloaded and seemed to install. After restart it booted to recovery and nothing else happened. When I restarted to system I was still on 6.0.1. No errors, nothing! Any clue?
So this might be resolvable if someone has found the Android N OTA...
srideep said:
I am on MMB29V with unlocked bootloader, TWRP recovery, rooted. I opted in for OTA. It downloaded and seemed to install. After restart it booted to recovery and nothing else happened. When I restarted to system I was still on 6.0.1. No errors, nothing! Any clue?
Click to expand...
Click to collapse
OTAs won't apply if you don't have stock recovery.
Hi everyone,
I bought axon 7 (A2017) Chinese version from aliexpress. It's on B07 version, when trying to check OTA updates - it says no updates. If I understood correctly, that's because seller flashed gapps. No problems, I thought, I can do this myself... After 2 days of reading, downloading malware and even trying to register on chinese zte forums I give up.
-Tried simply putting update files on sd card and updating - no luck. Most probably because I can't find b08/b09 updates for straight A2017 (without U or G), have the last two only.
-Installed drivers, tried unlocking bootloader -failed. Adb works, detects device, however after rebooting to edl - adb does not detect any devices (enabled usb debugging and oem unlocking.
-tried flashing with MiFlash - errors "[2,07 COM6]:cannot receive hello packet,MiFlash is trying to reset status!"
-tried rebooting to edl manually (up/down+power) - boots, but adb does not detect devices (MiFlash sees it as com6 though)
-tried using axon7tool and minimal_adb_fastboot_v1.4 - same, detects while on, reboots to edl and nothing
-tried sideloading twrp through the adb sideload - says signatures are bad...
Oh, as a bonus, recovery is in Chinese, so I have to guess what's what
What could be the issue? Drivers, device itself? Owner? I don't want to be on the damn 6.0.1 - my nexus 5 was on that. plus zte skin is awful, I would want to flash cyanogenmod or at least a newer version that does not have the damn bell icon, or permanently stuck sms that I can't delete or mark as read
Is there a way to flash US or EU firmware? Any ideas would be welcome. And sorry for writing here - as a new user I'm unable to reply on the dev posts
Hi I have the same problem can anyone help on this issue to resolve
My unit is from aliexpress also but it was B11 when i received it. What i did was enabled usb debugging and oem unlock from dev options. Then boot in stock recovery and format the phone. I think it was the option above the choices where there is 'sd' written. Then installed the update via sd for b13.
otaconremo said:
My unit is from aliexpress also but it was B11 when i received it. What i did was enabled usb debugging and oem unlock from dev options. Then boot in stock recovery and format the phone. I think it was the option above the choices where there is 'sd' written. Then installed the update via sd for b13.
Click to expand...
Click to collapse
I finally managed to do this via this method
https://forum.xda-developers.com/axon-7/how-to/guide-b13-chinese-a2017-root-unlock-t3549873
and now I run lineageOS
you will need a laptop that you have admin access to, which allows you to disable your antivirus though.. which was my main problem
Moderators, if any, you can lock the thread
Hi man I hope you're OK. Today I was on A2017V2.1.1B07(MM) and I just downloaded B11(third one) from this link (http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78]) and put it on SD card and updated and installed it from settings(although I downloaded and put B11 on sd card, it showed B13 ROM update in settings). Then when It was finished , I got B15 Nougat OTA in settings and downloaded and installed it then again I've got B16 OTA in settings and installed it and now everything is okay. But I wanna ask you if I did it all correctly???(because I downloaded B11 Rom(not b13 rom from that link above) but I got B13 when I put that B11 on sd card and went to the setting)and Did you do the same???
Hi,
To be honest, I don't remember the actual steps. I followed this threadhttps://forum.xda-developers.com/axon-7/how-to/guide-b13-chinese-a2017-root-unlock-t3549873 and finally did it =)But I don't think I was able to get and instal OTA updates =) I'm on US B25 version now, and every time I update I basically use DrakenFX's builds. How do you like your axon mate?
build 16 is latest so you are up to date
First excuse me for opening an other thread like this, i think i have read all other threats regarding my problem, but none have the same situation
My Huawei M3 Wifi (BTV-W09) seems semi bricked after installation of Nougat Update.
The Installation (Force Install with dload) gave me an error and also while boot i got the error message: "Your device has failed verification and may not work properly."
I have the option to press "Powerbutton" and the device will boot up. I checked the Version and it showed android 7 + EMUI 5. The only problem was that almost every system app was missing, like keyboard, calendar etc. (playstore was there)
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error. I have ADB/Fastboot installed and tried some different things like flashing/unbricking it with "Huawei Multitool" where you can extract like boot.img or recovery.img and try to flash it.
Also getting an error. I can access eRecovery witout problems, the option to fix it by itself by wifi doesn`t work. I can´t access "normal" recovery and i think there is the problem (may got bricked while flashing Nougat?) I think its recovery problem, cause when i boot it up to the "half-installed" Android and go into setting "hard-reset" option i know it would boot up intoi recovery and would erease everything, while bootup it shows error "reset failed".
In fastbootmode i see bootloader: unlocked FRM: unlocked
I tried to install TWRP recovery with adb but get error: adb remote command not allowed
I downloaded like 15 different Android Versions 6+7 Emui 4.1+5 to try with force update but none worked, may i have to flash special version of recovery first?
I just want a normal version of android 6 or 7 i dont mind but at the moment with half working 7 "without" systemapps its a hardtime.
I hope someone can help me.
This isnt my first android device and im not a total noob i unlocked bootloader and flashed kernels on many other phones but with the W-09 where i did nothing special i dont get why "recovery got broken"
Thanks in advance
You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.
nicolap8 said:
You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.
Click to expand...
Click to collapse
thanks for your anwser, i read that so i also tried unlocking it "again" and it quotet it is also unlocked in adb. I also know that there are 2 packages. That you need TWRP i didnt know thanks so i am a bit smater now. I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.
kivi90 said:
I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.
Click to expand...
Click to collapse
This is nonsense. Unlock, install the right TWRP then install the second zip package.
nicolap8 said:
This is nonsense. Unlock, install the right TWRP then install the second zip package.
Click to expand...
Click to collapse
i cant unlock cause i dont have the code, on the huawei page i try do make an account and get the code by providing the necessary information.
I just uploaded a picture, i choose "before EMUI5" cause this is the only option i can choose "tablets". --> i choose "tablet wifi" , enter product model "BTV-W09" then the serialnumber i can see in setting: 28D6R17316XXXXXX but then i have the problem to input product id, it say i can get it through "Dialer" app (which i dont have in wifi model ) or the calculator. Problem is in my damaged installation there is no huawei calc, other calcs from store dont work (read that problem in other threats) I tried many apps from appstore to get a product ID but huawei site keeps saying wrong product ID =/
With the program DC Unlocker i am able to see a MEID i dont know if its the right one, i tried my luck with the Product ID Generator from Huawei but it doenst work. (device not supported)
It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!
nicolap8 said:
It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!
Click to expand...
Click to collapse
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.
Did you ever find a fix
Did you ever find a way to fix this. I'm in the same situation. I even did a VPN on my router to give me a Hong Kong address for erecovery and that still didn't work. I have the exact same product. Like you I tried to various attempts to download a new recovery, but nothing works. Nice hardware, but some of the worst software/firmware I have ever dealt with since starting with the first release of Android on the HTC Hero.
kivi90 said:
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.
Click to expand...
Click to collapse
I had mostly the same problem. I rolled back to 4.1 using the rollback and the actual 4.1 update.app. I think that puts you on C100 if I remember right. Tablet I have is C128 (USA) but no problem for this step. Get the Product ID from the calculator. Allow OEM unlock in the settings, then unlock it using the unlock code. Email yourself the unlock code because who knows if their website will even be functional next time. Alternatively you can extract the stock calculator from the update_data_usa.zip or whatever and try to use DC with 5.0. That second update zip does not install properly via the dload method, so a bunch of stock apps don't get installed. You can kind of hack it and flash it via TWRP but I didn't do it that way.
Or...you can use firmware finder to force an OTA from 4.1 right up to 5.0 (350), then take that last partial OTA to 351 after as well. The way to do that is via DNS in firmware finder. Find the Full OTA in firmware finder you want, send it to the updater by changing your DNS the way it tells you to, and when it does the OTA, everything will be properly installed basically the official way. Good as new. Flash TWRP to recovery2 and replace the erecovery. Keep the stock recovery as is. Install magisk. Golden.
---------- Post added at 03:36 AM ---------- Previous post was at 03:26 AM ----------
kivi90 said:
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error.
Click to expand...
Click to collapse
Also, as far as the rollback, you need to do the first one (the C900 which is just a compatibility fix to allow rollback, previously used by beta testers I believe). Then you need to do the second one, the C100. If it is getting stuck, try downloading it again and be sure you don't have anything else in the /dload directory on either internal or the sd card. I had one on both at one point so maybe that happened to you. The C900 should be very quick but the C100 will slowly progress after 5% all the way around in several minutes.
When you get to updating back to 5.0, you can choose whichever region you want as long as it is a full OTA. C128 is USA and that's what I bought so that's what I picked. That gets you back in the right OTA update channel after that.
Hi guys,
I started as a novice and have learnt the hard way.
Has anyone tried rollback to EMUI 4.1 EU version on a US device (W09) and are there any problems I should be aware of?
I have had the exact same problem shared in this thread and have gone through the pain of finding a solution. My last resort is to rollback to 4.1 and restart the whole process.
@deV14nt: you suggested that when updating back to EMUI 5.0, I can choose the region even if my EMUI4.1 is EU version. How does this work?
Thanks in advance for your help.
Hello, I really messed this up... I haven't rooted a phone in over 5 years, but just ordered a moto g7 from google fi because I wanted to play around with rooting and rooted apps again.
Setup:
-got moto drivers, adb, set developer mode, unlocked bootloader
I had tried to just root using the "simple?" method of using Magisk with the lolinet firmware files. I used the PPO files in the Official/FI dir. I thought that I had seen an error when flashing the magisk modified boot.img that there was an issue or that it wasn't valid, I (stupidly) assumed that this was like the notification you get after unlocking bootloader about invalid key or whatever. When trying to boot up it would just keep boot looping, and I went into hard panic mode... I saw other people had mentioned using retail or retus firmware on the google fi variant, so I proceeded to try to just flash those stock boot.img files after the fi one hadn't worked. I then finally got it to boot up fully, I don't even remember which firmware it was (retail maybe) and felt a little bit better about it, but had also seen that some people had said it wouldn't have the full functionality of network switching if I wasn't using the fi firmware. So... back to the fi firmware...
I was able to get it booting up on stock fi firmware, and to be honest I should have stopped there and given up on root, because I'm guessing I would have been perfectly fine up to that point... I again tried magisk modified fi firmware to no avail, and was having trouble getting back on stock fi for some reason... I followed a post to reset to stock and relock bootloader ***I'm guessing this was my major fault***, I must not have been paying enough attention to the command prompts doing this, but I think this is where I messed something up royally. It was able to boot, but then it said it had updated software to the 'PPOS' variant which I thought was strange... After attempting to reflash stock fi and then magisk fi boot.img it is failing and won't even get to boot loop.... when trying the slew of commands to flash full stock firmware I keep getting issues with the "_a" partition being not found.
At this point I can't get to recovery, or boot after attempting to flash a number of times. Any help would be appreciated, even if it is just a confirmation that I f'd this device and to stop wasting my time and give up on ever having a rooted device again lol.
Thanks for your time, and let me know if there is additional info to provide that may help.
Edit: Current status:
"Start Up Failed: Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the software Repair Assistant."
in Bootloader logs, but I don't know what software repair assistant it is referring to, i have tried connecting to pc.
Edit 2: Or I'm just a complete idiot and needed to re-unlock bootloader with the code like previous... which I totally should have known, but again, I'm an idiot...
So, now that I've got it booting up, do I attempt reflashing a magisk img or just admit I'm too stupid to do this? Or should I go with twrp which seemed like more steps and potentially more issues to run into?
Sorry for the scare and immense stupidity!
OK so I need some help...
When I originally purchased my LG G6 in June of 2019, I made sure it was a US997 model, but I ended up getting a BRIGHTPOINT version during my purchase. I went through the website to check the imei and the device ID and it gave me the not unlockable status.
After that, I went and decided to update the software manually to US99721e since it wouldn't OTA it and have been on that ever since. Now, I just recently tried while on the 21e software and I was given an unlock.bin code!
So if someone could help me out:
IF you're on a US997 BRIGHTPOINT G6:
-Download LG UP and UpperCut
-Download US997_21e_01_0211-UCL.kdz at lg-firmwares.com (this is the one I'm on, try this one first!)
-Once it's done, enable developer mode, adb debugging, and OEM unlock
-Go through the unlocking process
Please let me know what you find out!!
Is that only for us cellular?
Sent from my V60 ThinQ using XDA Labs
I have a brightpoint LG G6, which I bought as the seller claimed it was an unlocked US997, failing to share it was a OEM phone. I don't understand how this works please can you clarify? I tried the unlocking process and I have to supply my phone information to LG. Their database says it is a brightwell phone and so they won't release the unlock. Are you saying that after installing this ROM I don't need the key from LG to unlock the bootloader?
I have installed Uppercut and LGUP (1.14 as newer versions don't seem to work). I downloaded the ROM and I have the LGUP loaded. It shows the phone using US99721a. I have 4 process options, Refurbish, Upgrade, FOTA upgrade or Phonesettings which is the one to use?
It works! At least I obtained an unlock.bin file from LG. I need to work out which is the best LG G6 US997 ROM and how to load it when my SD card doesn't work. Any help or pointers to useful information much appreciated. For anyone else trying this here is what I found. I downloaded the LG windows drivers and LGUP 1.14 (There are newer versions but these don't work with uppercut. I downloaded Uppercut from XDA website and then you run Uppercut not LGUP. This immediately caused my virus checked to block it as it contains a trojan. I didn't like that but googled to find others had the same issue. There seems to be a way to load the correct file to get LGUP to work directly and I would recommend researching that but I disabled the virus software and proceeded. I used the UPGRADE option in LGUP - you need to reboot your phone into download mode. To do so, disconnect USB cable then Power off the phone completely. Now hold Volume Up then plug in USB cable at the same time. Make sure that LGUP is NOT running when you connect the USB cable and start it once you are in download mode. It loads the ROM very quickly and takes a bit longer to reboot and then it needs time to upgrade android as you have a 6 months newer version of Android 8. Then follow direction on the LG unlock site https://developer.lge.com/resource/mobile/RetrieveBootloader.dev. You will need to install ADK https://developer.android.com/studio/releases/platform-tools unzip after you download. LG emailed my unlock code immediately.
Yes, I can confirm that it works with the US997 model now. I already was at version US99721e so I didn't have to jump through the hoops to load this version. I went through the steps to unlock the bootloader via the LG developer website and voila, got sent the unlock.bin file, too.
Now I am pretty sure that I tried that in past perhaps 1-2 years ago and it didn't work, so perhaps LG has secretly flipped a few bits in their database to allow unlocking for these not quite brand new devices.
I just applied the unlock.bin and got the "cannot check for corruption" warning on the boot screen. So this is working - fantastic!
Now have to restore my device from the LG Backup I made before and put on the SD card.
I had tried the unlock last year but I didn't retry before I updated so it may have worked anyway and the update of the ROM wasn't needed. I unlocked the phone and installed Sky Hawk recovery but when that starts it asks for a deception password and nothing I have tried works. I'm not sure if that is a real issue or I can continue safely with flashing a new ROM. Has anyone worked through this issue?
challenger07 said:
I had tried the unlock last year but I didn't retry before I updated so it may have worked anyway and the update of the ROM wasn't needed. I unlocked the phone and installed Sky Hawk recovery but when that starts it asks for a deception password and nothing I have tried works. I'm not sure if that is a real issue or I can continue safely with flashing a new ROM. Has anyone worked through this issue?
Click to expand...
Click to collapse
First, when you're in Adroid remove all screen lock mechanisms, you can re-enable it later.
Enable USB debugging, do adb reboot bootloader and fastboot flash recovery with this recovery instead (rel_o2):
https://forum.xda-developers.com/lg-g6/development/recovery-twrp-3-2-1-unofficial-fixes-t3722199
Do the button combo to launch recovery. If you're in recovery, first reformat /data (you have to enter "yes") to get rid of encrption and after that flash the anti-root removal tool mentioned in the post. Then reboot into recovery and then flash Magisk and/or your ROM of choice. Note that I have only used this with stock ROM and Magisk and not tried any custom ROMs, but the thread has plenty of people having also tried other ROMs.
How do you even know if you have a Brightpoint device?
I found out when I tried to unlock. http://mobile.developer.lge.com/
Thanks for the info. I'll dig into this once I know for sure that a version of Android 10 is available to load into the phone.
What I've been dealing with so far keeps asking for a 15 digit IMEI number. My phone only has a 14 digit value.
I pulled box (yes I kept it) and discovered that the IMEI is 15 digits. No idea why the value is the phone truncates the last digit. The site that checks IMEI numbers says that it is the platinum edition: US997PL. Gee, the box says that.