Database Users

WARNING - Do not use OTA to get Android N Beta Preview before reading this!

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.

Axon from aliexpress - update issues

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

No Sim Detected

Hey all......I created a thread awhile back when I borked my phone trying out a new treble rom that was supposed to be so easy even a nOOb could flash it, and it ended up messing up my phone to the point where the only way for me to get it back was to follow the thread to disassemble the phone and short the chip out.
Then, the screen was not responsive on ANY rom I flash except for MM and it worked with any up to B29. I tried a few times to upgrade all in vain but I was always able to flash MM B29 and have it work again.
Flash forward to last night and my itchy trigger upgrade finger did it again and I attempted to flash the Oreo from ZTE. It flashed fine but, again, no responsive screen. I thought well, maybe I could try Nougat again and I flash many different versions and in different ways (used miFlash, EDL tool, MiFavor recovery, twrp) and all resulted in the screen not being responsive. Sigh, so I flashed MM B29 but now it will not detect any sim or even allow wifi to be turned on.
I have tried multiple times to reflash MM B29 using all the different ways above and even went back and forth between roms. I tried the original way most of us first unlocked the bootloader and flashed through all those stepped zip packages from B20 to B29 and still nothing. I finally used twrp to erase/format all data and made certain the partitions were formatted as ext4 and tried again, still no sim.
I realize that my imei is not showing and even tried a program to flash? that to the phone.
NOW, what needs to be said is during ALL of this flashing the phone signal/sim DID show......yes.......the sim DID WORK......when I flashed anything other than MM B29. LOL. Of course, the issue is none of those roms allow the screen to work.
Please, if anyone can help I would appreciate it very much. I'm thinking by flashing the Oreo from ZTE it may have changed something that the MM B29 rom is not changing to allow the phone to read the imei/sims.

I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps ?

Syberclone said:
I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps
Click to expand...
Click to collapse
I appreciate the suggestions. Unfortunately, the DFU tool doesn't seem to work for me as it remains listed as Disconnected even after choosing the correct port.
I have always flashed the MM B29 EDL rom (A2017U_B29_MARSHMALLOW_FULL_EDL) that contains the correct modem. As I said, it always worked before.
As far as checking APN/network settings, well, there are none to check because the sim is not detected so all of those choices are greyed out. The signal bars fr both sims are blank in the notification area and of course wifi does not turn on.
I just finished another round of trying different roms to flash including LOS 15. LOS came up to the welcome screen (just like all the others) AND the AT&T logo with LTE full signal bars showing. Again, the screen does not respond to touch so it's all useless. I am at a loss as to why flashing MM B29 is no longer working for me.

Stop using guides mentioned in Axon7 thread,or stop listening to other users.Only thing i see here are bricks.
Probably you have hardware fault

The Axon 7 has been the worst phone for being bricked.
I've flashed ROMs on HTC's, Motorola and Google phones all without problems.
There are way too many packages and bootstacks etc, etc that cause problems and confusion.
So I wouldn't say don't follow threads or users advice.
My advice is research, research and research some more.

Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?

djprez said:
Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?
Click to expand...
Click to collapse
Did you installed a vendor partition?

Predatorhaze said:
Did you installed a vendor partition?
Click to expand...
Click to collapse
I am not certain. If the Oreo update that I downloaded directly off the ZTE site has one, then yes. If that is the cause, how would I modify it?

@djprez: To my knowledge, ZTE's official B12/B20 do not have a vendor partition. ZTE will almost certainly never add Treble support for the A7, if they are going to do so then now is an ideal time, since the A7 is an end-of-life device and no longer being manufactured.

Lgg6 stuck in download mode

Hi Guys, i've tried to install Pie update to my G6(H870) via LGUP.
Didnt worked for me, got an error trough the installation, and now my phone stucked in download mode.
I can get into fastboot, was able to do factory reset, but the only thing changed, is now my computer cant see my phone via USB
Any one could help me please?
Thanks

evilchef said:
Hi Guys, i've tried to install Pie update to my G6(H870) via LGUP.
Didnt worked for me, got an error trough the installation, and now my phone stucked in download mode.
I can get into fastboot, was able to do factory reset, but the only thing changed, is now my computer cant see my phone via USB
Any one could help me please?
Thanks
Click to expand...
Click to collapse
Restart PC and try again
LG-H870 V30a

slavomes said:
Restart PC and try again
LG-H870 V30a
Click to expand...
Click to collapse
Did a couple of times, nothing happened... I also tried with different pc. All drivers installed. Can't get any USB connection.

evilchef said:
Did a couple of times, nothing happened... I also tried with different pc. All drivers installed. Can't get any USB connection.
Click to expand...
Click to collapse
Did you tried LGBridge trough Update Error Recoevery?

slavomes said:
Did you tried LGBridge trough Update Error Recoevery?
Click to expand...
Click to collapse
Yes I did, after the recovery reached 19% it said "phone cannot be updated" now I don't know what to do... ? Can't even get a connection between the phone and the pc now

Someone can help me please????

I've got literally the exact same problem...
I've tried everything that is possible, it was working perfectly with twrp, magisk root and even had edxposed (stock android, safetynet pass, Google pay working). I wanted finally the pie, kdz file has shown up so I wanted to update it as always (with twrp I could only update via LGUP) stopped at 10% and the it shown an error and turned off. Once I disconnected my cable while updating but was able to reconnect and relaunch update without any issue or losing data! Now I didn't know what to do so I gave it to a service, 2 and half week passes, they arek still working on it, if I have anything after that and my phone connects to pc or boots to android I will tell.

AdurVonRob said:
I've tried everything that is possible, it was working perfectly with twrp, magisk root and even had edxposed (stock android, safetynet pass, Google pay working). I wanted finally the pie, kdz file has shown up so I wanted to update it as always (with twrp I could only update via LGUP) stopped at 10% and the it shown an error and turned off. Once I disconnected my cable while updating but was able to reconnect and relaunch update without any issue or losing data! Now I didn't know what to do so I gave it to a service, 2 and half week passes, they arek still working on it, if I have anything after that and my phone connects to pc or boots to android I will tell.
Click to expand...
Click to collapse
Try this version of LGUP:
https://drive.google.com/open?id=1Zh2oboeMDn-QXrWbuMwN4PcOgCeBDU6C
Matt.

matthew33 said:
Try this version of LGUP
Matt.
Click to expand...
Click to collapse
After I get back my phone I will try it, but as the phone wasn't seen by laptop after connecting it then using another lg up wouldn't have any sense. There may be two problems, or I ****ed up something while trying to update to pie or the kdz file isn't good. The servise told me today that there is a problem with the first partition, that's why the phone isn't seen after connecting. If I hadn't root my phone I could send it to lg because I'd still have my warranty, but now I'm waiting so they tell me how much it'll cost to use a special device that connects to the motherboard or something like that to get the first partition installed. So evilchef...
evilchef said:
Hi Guys, i've tried to install Pie update to my G6(H870) via LGUP.
Didnt worked for me, got an error trough the installation, and now my phone stucked in download mode.
I can get into fastboot, was able to do factory reset, but the only thing changed, is now my computer cant see my phone via USB
Any one could help me please?
Thanks
Click to expand...
Click to collapse
You are having the same problem as me, if you still have your warranty, then you can send your phone to an lg service, if not do it on your own money. After I get my phone back I will tell you if it still has all the data on it, but I'm more than sure that it has lost it. If in any way I get back then I can suggest you to get it repaired if you haven't got any backup done, if not it might be better to buy a new phone.

Help: My LG H990 DS only enters Fastboot and now the device changes to US996

Hi, I get a notification to update magisk. then I update it and use the recommended action to update it. After that it asks me to reboot the device. After rebooting the device it goes to fastboot only. And I see the device now changes to US996 while what I have is H990DS.
Can someone explain to me what's wrong and how to fix it without losing all my data?
thanks...

Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope

aliks00 said:
Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope
Click to expand...
Click to collapse
It's common knowledge that if you root your phone you never apply an OTA
Sent from my LG-H910 using XDA Labs

cnjax said:
It's common knowledge that if you root your phone you never apply an OTA
Click to expand...
Click to collapse
Thanks, but who said I ever applied an OTA? It was magisk that wanted to update itself, I've been performing magisk updates regularly for quite some time and never had a problem, in fact I can't even perform an OTA phone update as I have AT&T variant but with a different sim...
Other times, when updating magisk, I lost root but never lost the ability to boot...
I was running alpha-omega oreo with mk2000 kernel and updating rom, kernel and magisk regularly through TWRP (or direct install in case of magisk though magisk app) and never had this problem before... at least I can manage to boot from recovery/TWRP so hopefully I will soon manage to get things working again... that is, if I can copy some images to my SD card that windows insists that is corrupted but that's another story...

I ended up flashing whole rom again and everything is back to normal