Database Users

Lg G Tab 10.1 Vk700 Root Method Confirmed!

This Has been confirmed to work on VzTab May not work when lolipop comes. So i found this on accident and tryed these two methods together to get the end desired result. Root Access! The first thing to adress is if your using windows 7 or 8 its a bitc# to get adb to recognize that your devices is connected. So if this becomes a problem i can find the link i used to address it. So you will download all the required files that go along with this 1st method contained here.
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
Along with the lg drivers youll need the tablet to install the verizon software upgrade assistant too.
Fallow all of the processes until you reach the download mode. I could not figure out how to manually push buttons to make it into download mode so use this next link and run all the procedures till its in download mode.
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Now you have the desired screen fallow the rest of the instructions from the first tut. Then press and hold power and volume buttons to reset. Since you cant take battery out or command it to reset. The Downloader will indicate 0% still so dont think it failed if it doesnt say 100%.

and too root the lollipop update download the files off rootjunkys site awesome work lol yes it was originally for the note 4 but shush it works
install kingroot (yes its in chinese dont worry we will be installing supersu very soon)
make sure adb is working and usb debugging is enabled which if you are on here i safely assume you are
extract the supersume zip (1 or 2 i couldnt see a diff)
and run the superme bat file (it will walk you through it )
itll soft reboot when done and you are solid and it will hold root
yes the bat will say disableing knox again it was for the note 4 but works fine ive done this
link to get files : http://rootjunkysdl.com/?device=Gala...=Kitkat Root

I don't have this tablet but replacing kinguser with supersu should be doable on this tablet as well (I did it on my forge tv)
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
all you do is install terminal emulator and copy files and run the command.

So now i cant upgrade to lolipop im guessing due to the fact it knows its modified now it will give error at 1% anyone have the factory image and how would i go about recoving it to stock image would i need cwm recovery to accomplish this? I really just want to upgrade so maybe the bluetooth stack has been fixed so i can use my wii mote to play games.

Alpha_wolf said:
and too root the lollipop update download the files off rootjunkys site awesome work lol yes it was originally for the note 4 but shush it works
install kingroot (yes its in chinese dont worry we will be installing supersu very soon)
make sure adb is working and usb debugging is enabled which if you are on here i safely assume you are
extract the supersume zip (1 or 2 i couldnt see a diff)
and run the superme bat file (it will walk you through it )
itll soft reboot when done and you are solid and it will hold root
yes the bat will say disableing knox again it was for the note 4 but works fine ive done this
link to get files :
Click to expand...
Click to collapse
Thanks for the timely post of this.
Don't know if it's something on my end but the link gives 'access denied', fortunately you had said it was for a note4 so I just looked for that and came up with the right files, just thought you might want to know.
One minor hiccup, and I'm not sure where to post it, so I'll post it here: SuperSu took 5 tries, finally got success, but now it keeps wanting to update the su binary again, it's definitely rooted, and the binary's already updated so...[shrugs]. The app said if there were any problems with it to post it to xda, soooo, here it is, sorry if this is the wrong place to put it.
Other than that tho, it worked great, thanks again!

laperro said:
Thanks for the timely post of this.
Don't know if it's something on my end but the link gives 'access denied', fortunately you had said it was for a note4 so I just looked for that and came up with the right files, just thought you might want to know.
One minor hiccup, and I'm not sure where to post it, so I'll post it here: SuperSu took 5 tries, finally got success, but now it keeps wanting to update the su binary again, it's definitely rooted, and the binary's already updated so...[shrugs]. The app said if there were any problems with it to post it to xda, soooo, here it is, sorry if this is the wrong place to put it.
Other than that tho, it worked great, thanks again!
Click to expand...
Click to collapse
idk i got that once and i updated it and it was fine so idk sorry tho

Alpha_wolf said:
and too root the lollipop update download the files off rootjunkys site awesome work lol yes it was originally for the note 4 but shush it works
install kingroot (yes its in chinese dont worry we will be installing supersu very soon)
make sure adb is working and usb debugging is enabled which if you are on here i safely assume you are
extract the supersume zip (1 or 2 i couldnt see a diff)
and run the superme bat file (it will walk you through it )
itll soft reboot when done and you are solid and it will hold root
yes the bat will say disableing knox again it was for the note 4 but works fine ive done this
link to get files : http://rootjunkysdl.com/?device=Gala...=Kitkat Root
Click to expand...
Click to collapse
Thank you thank you!!!
This worked...had to fight a few areas but it all worked...
Is it possible to get custom recovery like TWRP?

parcou said:
Thank you thank you!!!
This worked...had to fight a few areas but it all worked...
Is it possible to get custom recovery like TWRP?
Click to expand...
Click to collapse
not that i know of the device is still pretty new

I found this method incredibly easy: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
I just had to put it on PTP instead of MTP. And after the reboot, I had to manually boot it on download mode (following the software's directions).
It's working flawlessly.

Root H830 running 20A and 20C [Nougat] AutoMagically (Custom Easy Recowvery Script)

I posted this as a reply originally. Then thought it probably should be a thread so it can help as many people as possible! Let's get the custom kernels and ROMs going for this beautiful device!
You will need to already have Android 20A (C should be fine as well) stock image installed, and the bootloader unlocked [Plenty of easy help via Google won't cover that here]
You can use the Recowvery Method on 20A (Nougat) (again this should be the same for 20C) with the H830. Below is the script I used with supersu and no-verity script included. Plug-in the device to your Windows machine. Install LG drivers, and remember to unlock screen and authorize the computer via the Device's screen so ADB commands can run (unnecessary tech note: you could open command prompt cd to where this is and use it's ADB to run adb devices (if you don't understand that no worries skip it)). After that just run the script and follow the menus. Answer yes when asked if you're sure you wish to continue, and done. I hope you find my work helpful .
I used this guy's script [Easy Recowvery ALL CREDITS TO THE AUTHOR I'M JUST SUPPLYING AN H830 SPECIFIC PACK WITH NEEDED FILES THAT I VERIFIED FULLY WORK. PLEASE GO RATE HIS THREAD AND CLICK THANKS IF THIS WORKS FOR YOU!]: http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
DON'T FORGET
This should work granted you have the drivers installed, and Windows has finished installing them, you tapped the prompt on your device screen to allow the adb connection, and you run script as administrator, and you restart the computer if you run adb commands yourself and aren't comfortable checking task manager to kill any and all running adb instances (could also issue the stop server command too), but if unsure of any or all of that last statement, restart
Of note answer yes when it says this isn't a V20 are you sure you wish to continue?. Also, as stated in notes I had to actually run it twice for it to stick for me (I'm sure I rushed the first time or something).
I took the time to create an H830 package of the script version with the files that worked for me. Out of respect I changed nothing aside from adding the needed files and throwing quick notes in the readme.md (bottom of file) file. (PLEASE read it, if you have issues read it you missed something). You will also still need to type yes when it states this is not a V20; Do you wish to continue? <Yes>.
. I used this package to root my H830 after the Nougat OTA killed my root access so
SHOULD WORK ON ANY H830 RUNNING STOCK 20A (should work with 20C) [NOUGAT] Read the following paragraph if you skip the rest
Read the readme.md file found in root of archive (see bottom of file).
Start it up hit like 5 for TWRP and supersu (or there's another menu option for just supersu or just TWRP whatever you desire).
Answer yes to the prompt to continue.
Now wait for the magic (again not mine this is the authors work)).
Once done you can download a reboot to recovery app or widget (or root checker) and verify that you're good to go.
If it doesn't take the first time you may need to run it again. DON'T FREAK OUT, RUN SCRIPT AGAIN IT CAN TAKE MULTIPLE RUNS.
Don't forget to install BusyBox (Stericson installer recommended and I use /su/bin personally (/su/xbin should also be fine) Since we're talking stock here generally I like to minimize any changes to /system if it can be helped personally; so I haven't tried running BusyBox from any /system mount) as this is a stock ROM.
Kernel Adiutor works and yes I recommend leaving thermald enabled as your thermal governor unless you flash a custom kernel (not included)
Manual Boot to Recovery:
Start With phone off (pinch battery button and re-insert battery if you can't otherwise shut it down or are lazy like me )
Hold both Power AND Volume Down at same time
1-2 seconds in to seeing LG Logo release and hold power button while continuing to hold volume down the entire time...
Release once you see white screen prompting yes or no to wipe user data (don't freak) ¹
use volume key to highlight yes
Hit Power key (think enter)
¹(If you have factory recovery this WILL format all user data and settings you've been warned. Only way to boot to stock recovery is to use app, widget, or terminal/adb command (reboot recovery). I don't know of any manual physical button methods to access stock recovery directly.).
You should now see TWRP Loading and can release any keys if you're holding any down still (once white wipe screen is seen you should release the keys)
Sweet, the file is small enough to be attached to this post directly, Enjoy! Also it's a 7-zip archive. It's available for every OS. For Android if you use ES File Explorer the first time you try to use a 7z file it'll offer to download plug-in, and you're good to read/write 7z archives (best compression almost always imho).

It doesn't seem to work for me, it reboots and the little android says No Command. Any suggestions?

well I ran the script ,Im afraid what was happening earlier is happening here to,when the script tries to flash Supersu it reboots to Firmware Update screen,Im fairly certain thats not right...am I correct? Gonna try to pull out (lol) before that screen loads like I did with the other method...

Ahhh I miss being able to root without a PC. I don't own one ?

Can anyone confirm this works fine? I won't have time for troubleshooting if it doesn't..

Jonathanpeyton said:
well I ran the script ,Im afraid what was happening earlier is happening here to,when the script tries to flash Supersu it reboots to Firmware Update screen,Im fairly certain thats not right...am I correct? Gonna try to pull out (lol) before that screen loads like I did with the other method...
Click to expand...
Click to collapse
Sounds like your hope would be if someone made a tot with root for 20A

shaneg79 said:
Sounds like your hope would be if someone made a tot with root for 20A
Click to expand...
Click to collapse
unfortunatley, I think that may be the only way Ill ever get my oddball device to accept TWRP....

WiiR0cKz said:
It doesn't seem to work for me, it reboots and the little android says No Command. Any suggestions?
Click to expand...
Click to collapse
same issue i turned off integrety check and ran it again it worked fine

Alpha_wolf said:
same issue i turned off integrety check and ran it again it worked fine
Click to expand...
Click to collapse
Where did you find integrety check
Sent from my LG-H830 using Tapatalk

Hi, thanks you for this post. I tried to use this script and I got an error saying that I am missing files in the "exploit" directory...please see the attached screenshot. Any ideas? Thanks.

famous145 said:
Where did you find integrety check
Sent from my LG-H830 using Tapatalk
Click to expand...
Click to collapse
hit 5 in the main screen it should be there

Can someone please help me unlock my bootloader now that I am running nougat! TIA fellow peeps!

Is this working for everyone / anyone? Most posts so far seem to have issues...

Alpha_wolf said:
hit 5 in the main screen it should be there
Click to expand...
Click to collapse
I did this but am still getting the no command issue

This method worked for me after about 5 failed attempts. The OP guide is not very clear, I might write my own and post it today.

aanonymoushuman said:
This method worked for me after about 5 failed attempts. The OP guide is not very clear, I might write my own and post it today.
Click to expand...
Click to collapse
Please!
When you say failed, did you get the no command issue as well,or something different?

Dumboguy03 said:
Please!
When you say failed, did you get the no command issue as well,or something different?
Click to expand...
Click to collapse
I did get the no command issue in recovery, the first time I did it, disabling integrity verification solved the problem when I did my next time, but I got some other issues before this solution worked.

My problem is, i am on Mac in parallels i can't list my phone in adb devices command. it shows as empty. Installed every possible app scenarios but still looks empty

Check out my guide on rooting Nougat, https://forum.xda-developers.com/lg-g5/how-to/guide-root-stock-n-using-jcadduonos-t3529093

Can confirm this does work. Took me 30 tries but it worked!

Stuck at fastboot/LG Logo

I was having some issue with a rom and figured it was time to reflash/flash a new one. I started the process in TWRP and Aroma froze half way through. I had to reboot. Unfortunately I had already wiped my rom. I can get to fastboot, but I cannot get anywhere else at all. Can anyone point me to a way to get back into recovery?
Should have mentioned, H918.

codman2728 said:
I was having some issue with a rom and figured it was time to reflash/flash a new one. I started the process in TWRP and Aroma froze half way through. I had to reboot. Unfortunately I had already wiped my rom. I can get to fastboot, but I cannot get anywhere else at all. Can anyone point me to a way to get back into recovery?
Should have mentioned, H918.
Click to expand...
Click to collapse
Download adb to your computer. Connect the phone to the computer. Open cmd and use cd or pushd to point cmd to the directory where adb is. Once you are in that directory (from cmd), use " adb reboot recovery "

If what jinkerz9430 suggests doesn't work,
You may have to go back to stock. Here is how to do it for 10j:
https://forum.xda-developers.com/sho...80&postcount=8
Then you reroot as before.

Fixed!
jinkerz9430 said:
Download adb to your computer. Connect the phone to the computer. Open cmd and use cd or pushd to point cmd to the directory where adb is. Once you are in that directory (from cmd), use " adb reboot recovery "
Click to expand...
Click to collapse
Thanks for the response. I ended up rooting around for a long while after this post and settled on using LGUP and found the correct files to reflash to stock. Adb would not work at all. I could get fastboot access, but that is gimped. No driver update would fix the adb problem. I've never had this issue before, with any phone. LG seems to make things more difficult than necessary. I miss Samsung.

Thanks
androiddiego said:
If what jinkerz9430 suggests doesn't work,
You may have to go back to stock. Here is how to do it for 10j:
https://forum.xda-developers.com/sho...80&postcount=8
Then you reroot as before.
Click to expand...
Click to collapse
That link seems to 404. I'd be interested in reading that though, if it isn't actually a 404. I believe what you are referring to is what I did though LOL. I found the kdz and dll, and used LGUP to get flashed back to stock. I'll never let it out of my sight again.

codman2728 said:
Thanks for the response. I ended up rooting around for a long while after this post and settled on using LGUP and found the correct files to reflash to stock. Adb would not work at all. I could get fastboot access, but that is gimped. No driver update would fix the adb problem. I've never had this issue before, with any phone. LG seems to make things more difficult than necessary. I miss Samsung.
Click to expand...
Click to collapse
If you flashed stock with lgup then everything is back to factory settings. Is this is the case, then the autorization you gave to your computer via usb debbug (where the prompt appears if the device is connected to a other device without authorization asking you whether you want to authorize it or not). Is also back to factory settings. Which means not even developer mode is on. But after you turn developer mode on and usb debbug then connect the phone to the computer and it will ask you once again for authorization

[/B]
codman2728 said:
That link seems to 404. I'd be interested in reading that though, if it isn't actually a 404. I believe what you are referring to is what I did though LOL. I found the kdz and dll, and used LGUP to get flashed back to stock. I'll never let it out of my sight again.
Click to expand...
Click to collapse
That's it!

Hi! New to LG; some basic ROM questions

Hi All,
My wife is headed to Italy at the end of the month, and I purchased an unlocked Verizon VS995 V20 off ebay for her.
She is running a stock ROM Galaxy Note 2 (she likes things the way they are on KitKat , but that's another story ).
I've rooted Samsung, HTC and Moto phones in the past, but this is my first LG. From what I can tell, the V20 is a solid phone!
I tried looking online but am not finding clear answers yet, so here's my basic questions:
1. since the phone is supposedly unlocked, is there a specific ADB command I can use to verify it? Or should I go through a root process to be sure?
2. we are on T-Mobile, so I'd like to go to a stock AOSP Android 7 ROM with no carrier bloat. If the phone is unlocked, or if I do root, would there be any issues since this is a Verizon-branded phone?
3. not trying to start any bickering, but any recommendations for a stock vanilla Nougat ROM?
My phone info:
Build # NRD90M
Config ver B26.LGE.VS995.0
Software ver VS99513A
I appreciate any replies and thoughts, and I'm looking forward to seeing what this phone can do!
regards,
motionmonk

First, this post belongs in the Q&A section, hopefully a mod will move it.
Second, what security patch version are you on. It is listed in software info. If it is anything later than Dec 2016, then you can't root (yet).

My apologies to the Mods; I wasn't sure which section this should go in.
The Security Patch Level is dated Dec 1, 2016. Would that still work?

Wrong thread

Yes, you can root. Before you do, find the patched LG UP thread and do a dump of your entire phone. If you ever want to go back to stock, you will have the files. Also, it is good to have a full backup of your phone as it currently is.
I don't have a VS995, but I am willing to offer all the help I can.
-- Brian

runningnak3d said:
Yes, you can root. Before you do, find the patched LG UP thread and do a dump of your entire phone. If you ever want to go back to stock, you will have the files. Also, it is good to have a full backup of your phone as it currently is.
I don't have a VS995, but I am willing to offer all the help I can.
-- Brian
Click to expand...
Click to collapse
Thank you very much for the offer of help. It's sincerely appreciated.
I have some more research to do today, and then I'll reach out with more specifics.
And to all, sorry for posting in the wrong area... it looks like the Mods moved this to the Q&A area overnite.
-motionmonk

Ok, I think I have everything now.
I am using the Dirty Santa setup, and have installed the Terminal Emulator to the V20, loaded the twrp image to my SD card, and have the Required Files from the c20-root.zip loaded on the desktop.
Inside Win7 I installed the minimal package for ADB and Fastboot, and then connected the V20 as a device. Double-clicking on RUNMEFIRST.bat briefly shows a window, but it auto closes itself. I tried running the adb shell and doing "adb devices", but nothing is showing up. Doing adb logcat says it's waiting for devices too.
I feel I've already missed a step...

You enabled USB debugging?

runningnak3d said:
You enabled USB debugging?
Click to expand...
Click to collapse
Interesting... no, it's greyed out. I did the 7x tap to get Developer Options before I started, and thought I had checked it.
I have the phone set for File Transfer when connected to the Computer... but I don't think that would effect this setting.
Any ideas?

motionmonk said:
Interesting... no, it's greyed out. I did the 7x tap to get Developer Options before I started, and thought I had checked it.
I have the phone set for File Transfer when connected to the Computer... but I don't think that would effect this setting.
Any ideas?
Click to expand...
Click to collapse
The USB mode setting has no effect on adb. Also how is it greyed out? Can't say I've ever heard of something like that before.

Thisisabadname said:
The USB mode setting has no effect on adb. Also how is it greyed out? Can't say I've ever heard of something like that before.
Click to expand...
Click to collapse
I certainly can't claim to know much about this process, but I've never seen it before either on any other phone I've rooted.
I'll try and upload a shot of the Developer Option screen to this msg. I haven't done that yet here.
Weird, huh?

motionmonk said:
I certainly can't claim to know much about this process, but I've never seen it before either on any other phone I've rooted.
I'll try and upload a shot of the Developer Option screen to this msg. I haven't done that yet here.
Weird, huh?
Click to expand...
Click to collapse
Did you try unplugging it before trying to turn it on? It might be blocked cause it's currently connected

Thisisabadname said:
Did you try unplugging it before trying to turn it on? It might be blocked cause it's currently connected
Click to expand...
Click to collapse
I think I understand what you are asking...
-disconnect phone from computer
-restart phone
-reboot Windows
-phone is up; check Dev Options-- no joy.
-connect phone to Windows, VS995 is recognized. Type adb devices... nothing listed.

Latest Update
<I messed up this post, so I'd like to take it back>

While booted into the OS, you have to authorize it. Plug in the USB cable, and a prompt will come up.

Can't open /system
Ok, I'm stuck on Step 1 (which is farther than I've been till now; don't laugh)...
Just before the start of Step2.bat instructions, I need to applypatch after checking with Terminal Emulator that I have an untrusted_app.
I copy/pasted the applypatch instructions, and it reports:
elsa:/ # applypatch /system/bin/atd /storage/emulated/0/dirtysanta
could not open /system/bin/atd
This one I can't figure out. Have I missed something?

Install a terminal on your phone. That command goes into a terminal on your phone, not on your PC.

Ack. It even says so
I started Step2, and as a Verizon phone, the vibrator is going off, which is recognized in the instructions.
How long does Step2 take? I've been going for almost an hour.
On Terminal Emulator, it reports:
[1140] Fastboot mode started

Does your PHONE say fastboot? It should not take more than a few minutes.
-- Brian

runningnak3d said:
Does your PHONE say fastboot? It should not take more than a few minutes.
-- Brian
Click to expand...
Click to collapse
I thought I sent a reply but I guess it didn't go through.
-Yes, the Phone screen does say FASTBOOT MODE in Red, then multiple spec lines of Product Name, HW Version, Serial number, then at the end it says [1140] Fastboot mode started.
Back from lunch. Should I pull the battery and restart from Step1? Or can I continue from Step2?
I don't know why the root is so confusing for me. Thank you again for all your help Brian!

A2017G - Updates don't appear to be working. Still stuck on 6.0.1.

Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.

Neskobar said:
Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.
Click to expand...
Click to collapse
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.

Choose an username... said:
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.
Click to expand...
Click to collapse
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?

Neskobar said:
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?
Click to expand...
Click to collapse
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.

raystef66 said:
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.
Click to expand...
Click to collapse
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.

Neskobar said:
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.
Click to expand...
Click to collapse
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?

raystef66 said:
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?
Click to expand...
Click to collapse
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
edit - I renamed the zip to "update.up" and couldn't get that to work either. It's not detected in the update section of settings, and I still get the same "Sorry, you can't sdcard upgrade" message.
edit #2 - I tried naming it to "update.up.zip" and it detected it this time, trying to run the update now.

Neskobar said:
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up, when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
Click to expand...
Click to collapse
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)

raystef66 said:
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)
Click to expand...
Click to collapse
Ah, I should have mentioned that. This is the message I'm getting when I try that:
C:\adb>adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Click to expand...
Click to collapse
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.

Neskobar said:
Ah, I should have mentioned that. This is the message I'm getting when I try that:
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.
Click to expand...
Click to collapse
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.

raystef66 said:
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.
Click to expand...
Click to collapse
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.

Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.

raystef66 said:
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.
Click to expand...
Click to collapse
Ok, I attached it to this post, hope it works.

Neskobar said:
Ok, I attached it to this post, hope it works.
Click to expand...
Click to collapse
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.

Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?

Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless

lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.

raystef66 said:
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.
Click to expand...
Click to collapse
Yes, that's what I was concerned about. The very first update i tried to install was N-B09, and everything else has been an older update after that, so maybe it won't overwrite the newer files, or something? Or possibly something else went wrong in the first update, so everything else just wouldn't work because of that?
I'm putting N-B01 onto my SD card right now, so I'll test that, and if it doesn't work I'll wipe the phone and start again. If I do need to wipe the phone, however, which update would you recommend trying first? N-B09? That might confirm if it was just bad luck on the first try, or whatever.
RobboW said:
Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?
Click to expand...
Click to collapse
Agreed, that sounds like a possibility to me. I'll probably end up wiping and starting over.
Choose an username... said:
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless
Click to expand...
Click to collapse
Yes the tab autocomplete works on the "u" of update.zip and "o" of ota.zip, when I tried both. I have to admit, I was quite excited to see your suggestion there, as I thought that would be a really easy way to confirm if something isn't right with adb, but never mind.
I still don't understand why it gives me this error then, though: * cannot read 'update.zip' *.
ramnkc said:
lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.
Click to expand...
Click to collapse
Thanks for the suggestion, and yes, I did confirm that I renamed the right zip file. That would have been easy thing to fix though, sadly.
edit - I tried the same adb commands with windows powershell too, and got exactly the same error messages.

What ROM was on it before you flashed B09?

Updating to N-B01 worked! I've no idea why this happened the way it did, nor why adb didn't work for sideloading, but I'm really glad that it finally worked.
The order of events:
1) Installed N-B09 via transfer to SD using the android updater, no difference in android version, but appeared in update history.
2) Installed MM-B11, same as above.
3) Tried various methods of installing MM-B11, including:
- SD transfer
- recovery mode SD update (which the phone wouldn't let me do, saying, "Sorry, you can't sdcard upgrade").
- ADB sideload (which never worked even slightly. I always got the message, * cannot read 'update.zip'/'ota.zip'/'update.up.zip' *)
- Tried the above methods with variously named zip files, including "update, ota, and update.up".
- Tried the above methods, but wiping the cache in between processes.​4) Installed N-B01 via transfer to SD using the android updater. This time the process took a lot longer and after rebooting the phone, went through the process of optimizing apps, which it had never done before.
Ok, I think that's everything.
The only theory I can come up with is that: Something (I have no idea what, though) went wrong with the first update attempt and every subsequent attempt to update to an older version didn't work because it didn't want to overwrite newer android version files? That doesn't seem quite right to me, though, as I would assume that whatever is in the update.zip would just overwrite everything as standard, because the assumption would always be that these files are newer than the existing ones.
What would you recommend that I do next? Should I try to push through the latest N update now, then? Has this outcome helped you figure out what the problem was/is?
Whatever the case, I'm happy to finally get an update working. Thanks very much for all your help and suggestions, guys. It was much appreciated!