Database Users

[Q] Bricked my nexus 10! [Solved]

Please I really need some help! I think I've totally killed my nexus 10
I can get to fast boot but cannot flash anything. As soon as I try and say flash TWRP I get "FASTBOOT STATUS - DATA005fe000".
I've tried using the stock firmware and using flash-all.bat but get the same issue. The erase commands work, but then command to flash the boot loader gets the same issue.
I'm hoping I'm going to get flamed for not searching, 'cause that means I've missed something, but I've tried to search to no avail.
PLEASE HELP!!!!

kipperfish said:
Please I really need some help! I think I've totally killed my nexus 10
I can get to fast boot but cannot flash anything. As soon as I try and say flash TWRP I get "FASTBOOT STATUS - DATA005fe000".
I've tried using the stock firmware and using flash-all.bat but get the same issue. The erase commands work, but then command to flash the boot loader gets the same issue.
I'm hoping I'm going to get flamed for not searching, 'cause that means I've missed something, but I've tried to search to no avail.
PLEASE HELP!!!!
Click to expand...
Click to collapse
How did you got to that "state"? You should try using WugFresh toolkit.

lKBZl said:
How did you got to that "state"? You should try using WugFresh toolkit.
Click to expand...
Click to collapse
That's how I got into this mess! I tried to unlock and then root my tablet.
It rebooted and wouldn't pass the nexus X logo.
Now I can't flash anything.

In the Nexus Root Toolkit it says that if all goes wrong try Odin.
I've downloaded a version (I'm familiar with it from my Galaxy S), and got the drivers working... does anyone know where I can download the tar files?

kipperfish said:
That's how I got into this mess! I tried to unlock and then root my tablet.
It rebooted and wouldn't pass the nexus X logo.
Now I can't flash anything.
Click to expand...
Click to collapse
Did you get a chance to do the first twrp factory data reset? If not you may be able to boot into recovery mode and try a manual factory reset..
If your tablet is on, power it off.
Press and hold Volume Up + Volume Down + Power until the device powers on. You should see an image of an Android lying on its back.
Press Volume Down twice, until the screen says "Recovery mode."
Press Power to restart into "Recovery mode." You should see an image of an Android with a Red triangle after a few minutes.
While holding down Power, tap Volume Up
Use the volume keys to scroll to "wipe data/factory reset" and press Power to select it
Scroll down to "Yes - erase all user data" and press Power to select it
for some reason with wugfresh the first twrp factory reset failed on 2 out of 3 tests. I had do just do the manual factory reset above and all was well. Good luck! :good:

midgetzombiekiller said:
Did you get a chance to do the first twrp factory data reset? If not you may be able to boot into recovery mode and try a manual factory reset..
If your tablet is on, power it off.
Press and hold Volume Up + Volume Down + Power until the device powers on. You should see an image of an Android lying on its back.
Press Volume Down twice, until the screen says "Recovery mode."
Press Power to restart into "Recovery mode." You should see an image of an Android with a Red triangle after a few minutes.
While holding down Power, tap Volume Up
Use the volume keys to scroll to "wipe data/factory reset" and press Power to select it
Scroll down to "Yes - erase all user data" and press Power to select it
for some reason with wugfresh the first twrp factory reset failed on 2 out of 3 tests. I had do just do the manual factory reset above and all was well. Good luck! :good:
Click to expand...
Click to collapse
+1, exactly what I was thinking, you have to do a wipe data after unlocking in some cases.

Press and hold Volume Up + Volume Down + Power until the device powers on. You should see an image of an Android lying on its back.
Click to expand...
Click to collapse
Yes
Press Volume Down twice, until the screen says "Recovery mode.
Click to expand...
Click to collapse
Yes
Press Power to restart into "Recovery mode." You should see an image of an Android with a Red triangle after a few minutes.
Click to expand...
Click to collapse
I just get a black screen
While holding down Power, tap Volume Up
Use the volume keys to scroll to "wipe data/factory reset" and press Power to select it
Scroll down to "Yes - erase all user data" and press Power to select it
Click to expand...
Click to collapse
By using 4.2.0 (rather than 4.2.2) and trying the flash stock and unroot option I can now install CWM or TWRP as a boot loader.
I installed CWM and did a factory reset, then retried the above. This got the data error when installing system and then when finished got a file veririfcation error in the fastboot status. When I reboot I just get the Google logo and the unlock at the bottom.

kipperfish said:
Yes
Yes
I just get a black screen
By using 4.2.0 (rather than 4.2.2) and trying the flash stock and unroot option I can now install CWM or TWRP as a boot loader.
I installed CWM and did a factory reset, then retried the above. This got the data error when installing system and then when finished got a file veririfcation error in the fastboot status. When I reboot I just get the Google logo and the unlock at the bottom.
Click to expand...
Click to collapse
Wow i haven't had my n10 long enough to help you much more. Sounds like you might have some corrupt files from wugrfresh download/install? Maybe download from another mirror and try again? good luck !!!! Keep me posted!

Re: [Q] Bricked my nexus 10!
Not to be rude or anything but toolkits are the devil when it comes to Nexus devices. They are so easy to root and ROM that anyone can do it. Toolkits encourage ignorance to what and how things are getting done.
For starters go Google the fastboot files for the Nexus 10. Google Fastboot.exe and add it to your system folder on windows if you are using such.
Extract the downloaded "manta....." File and then extract the zip file contained.
From here make sure you are in your boot loader and type "fastboot devices" ensure your serial shows.
Then one by one go into the extracted folder and erase then flash each partition EXCEPT the bootloader. Don't mess with that at this point. After flashing the recovery, system, boot and data files reboot into the recovery and perform a factory reset. It should boot from this point.
On Manta, you MUST do a factory reset after flashing the data partition or unlocking the device. For some reason it fails to boot without performing that step.
Sent from my Nexus 10 using Tapatalk HD

altimax98 said:
Not to be rude or anything but toolkits are the devil when it comes to Nexus devices. They are so easy to root and ROM that anyone can do it. Toolkits encourage ignorance to what and how things are getting done.
For starters go Google the fastboot files for the Nexus 10. Google Fastboot.exe and add it to your system folder on windows if you are using such.
Extract the downloaded "manta....." File and then extract the zip file contained.
From here make sure you are in your boot loader and type "fastboot devices" ensure your serial shows.
Then one by one go into the extracted folder and erase then flash each partition EXCEPT the bootloader. Don't mess with that at this point. After flashing the recovery, system, boot and data files reboot into the recovery and perform a factory reset. It should boot from this point.
On Manta, you MUST do a factory reset after flashing the data partition or unlocking the device. For some reason it fails to boot without performing that step.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Yeah after my experience with toolkits I have leaned that the google sdk fastboot is the best method and you also learn the fastboot/adb commands and what's actually happening step by step.

midgetzombiekiller said:
Wow i haven't had my n10 long enough to help you much more. Sounds like you might have some corrupt files from wugrfresh download/install? Maybe download from another mirror and try again? good luck !!!! Keep me posted!
Click to expand...
Click to collapse
Ok, given all the feedback, especially with regards to corrupt items, I dug out an old laptop and was still getting the same problems, re-downloaded the 4.2.2 image and tried again.... and was more patient this time, and voila! back up and running!
Thanks to everyone who replied, I would not have persevered without your comments.
Lessons learned:
1) On Manta, you MUST do a factory reset after flashing the data partition or unlocking the device. For some reason it fails to boot without performing that step.
2) For me the downloads seem to have been unreliable, try, re-try, cry, weep, try again, punch the desk until your knuckles bleed, try some more and eventually you'll get there!
3) Be VERY patient. I was less patient than my normal impatient self when I saw how super lightning fast the N10 is.
Thanks again to everyone.

kipperfish said:
Ok, given all the feedback, especially with regards to corrupt items, I dug out an old laptop and was still getting the same problems, re-downloaded the 4.2.2 image and tried again.... and was more patient this time, and voila! back up and running!
Thanks to everyone who replied, I would not have persevered without your comments.
Lessons learned:
1) On Manta, you MUST do a factory reset after flashing the data partition or unlocking the device. For some reason it fails to boot without performing that step.
2) For me the downloads seem to have been unreliable, try, re-try, cry, weep, try again, punch the desk until your knuckles bleed, try some more and eventually you'll get there!
3) Be VERY patient. I was less patient than my normal impatient self when I saw how super lightning fast the N10 is.
Thanks again to everyone.
Click to expand...
Click to collapse
Glad to hear it worked out. I found out that wipe step the hard way.
Use the MD5 to verify your downloads if you have any doubts, i personally haven't had any failures

Sweet!
Sent from my Nexus 10 using xda premium

[Q] Please help guys

I have installed 4.2.2 on nexus 7. As I had skipped account login at welcome screen, i could not login the account. I altered the apk of login. After factory reset my device has hanged on setup on welcome screen. I tried installing custom rom through stock bootloader but the bootloader says installation failed. How do I solve thia problem guys???

subin.nexus7 said:
don't know the exact steps, but i got it out of the APX mode and into the bootloader.
1. Tablet plugged into computer.
2. Held Volume Down + Volume Up + Power (simultatenously) for three seconds
3. And then released all, and pressed Power again.
4. Tablet booted into bootloader.
I thought that unlocking the bootloader ALWAYS voided the warranty, but in anycase I flashed reflashed ALL stock and locked the bootloader. Will be sending it to ASUS now. Thanks again!
EDIT:
So I wanted to verify that it was a CPU problem, and I downloaded StabilityTest again and ran the CPU load test. It crashed within two minutes, and went into AXP mode again. To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures.
Click to expand...
Click to collapse
Very helpful! I don't have a problem but I've read about others stuck in APX mode. This should be pinned if it works for those stuck in APX. Maybe you should change the thread title to something about APX solution so it draws some attention.

kieso said:
Very helpful! I don't have a problem but I've read about others stuck in APX mode. This should be pinned if it works for those stuck in APX. Maybe you should change the thread title to something about APX solution so it draws some attention.
Click to expand...
Click to collapse
Well... being stuck in APX doesn't necessarily mean your hardbricked. (Corrupt or erased bootloader).
But being hardbricked DOES mean your device will default to APX mode.
To use a mathematical metaphor, one is a SUBSET of the other.
-------
bftb0 has posted an exhaustive list of Nexus 7 button press combos here...
http://forum.xda-developers.com/showthread.php?t=2133986
... which includes how to pro-actively get into APX mode... although until somebody figures how to nvFlash the N7, APX is sort of redundant.
Rgrds,
Ged.

Delete

subin.nexus7 said:
I have installed 4.2.2 on nexus 7. As I had skipped account login at welcome screen, i could not login the account. I altered the apk of login. After factory reset my device has hanged on setup on welcome screen. I tried installing custom rom through stock bootloader but the bootloader says installation failed. How do I solve thia problem guys???
Click to expand...
Click to collapse
I'm sort of confused about the relationship between your edited post and what (apparently ?) kieso quoted, but I'll throw out a few suggestions:
1) AFAIK, there is no way to flash a dev ROM using fastboot (only the boot image of a dev ROM can be flashed this way). You said "bootloader", not "custom recovery" ... so that implies using fastboot. If that is not the case, then your use of terminology is not correct. (It's a computer - reporting details correctly is incredibly important).
2) If you bypass the WiFi login, an account can be added at any time later using the settings menu or simply by launching the Google Play (market) app - there is no need to "alter the apk of login", whatever that means.
3) I would recommend at this point that you start completely over by flashing a factory ROM using fastboot - see the sticky thread about returning to stock using fastboot. If you already have the 4.18 bootloader installed, I recommend you avoid like the plague any operation involving flashing the bootloader.
4) It should be obvious from the trouble that you got yourself into that you should learn what nandroid backups are and that you START USING THEM. The first thing you do after rooting is "make a backup", not "flash a ROM"
good luck

Thanq so much.But still some clarification needed
Now What do I do? My nexus 7 can't pass through at welcome screen saying saying unfortunately setup wizard has stopped. and in recovery{i have no custom recovery, I use bootloader 4.18} i cant flash any rom. I just want to start device any how.. any way.. Is there any way??

subin.nexus7 said:
Now What do I do? My nexus 7 can't pass through at welcome screen saying saying unfortunately setup wizard has stopped. and in recovery{i have no custom recovery, I use bootloader 4.18} i cant flash any rom. I just want to start device any how.. any way.. Is there any way??
Click to expand...
Click to collapse
I guess I am having trouble understanding the sum total of information you have provided - I guess you have omitted some information or mis-stated something. No custom recovery sort of implies a full stock device, but yet you previously mentioned modifying/changing an .apk in /system... normally that would be possible only with a rooted ROM or a custom recovery to do that.
If your tablet is 100% stock, a factory reset of the tablet should allow you to boot once again - at the cost of deleting everything you put on the device, including all files you put on the (pseudo-) SD card.
If that is the case:
- press and hold power+vol-down until the bootloader screen shows up
- use vol-up/vol-down to select "start recovery" and press the power button
- an android lying on it's back should show up; this is the stock recovery splash screen, so
- press power+vol-up simultaneously for about one second - the stock recovery menu should show up
- select factory reset (with vol-up/vol-down) and press the power button.
good luck

bftb0 said:
I guess I am having trouble understanding the sum total of information you have provided - I guess you have omitted some information or mis-stated something. No custom recovery sort of implies a full stock device, but yet you previously mentioned modifying/changing an .apk in /system... normally that would be possible only with a rooted ROM or a custom recovery to do that.
If your tablet is 100% stock, a factory reset of the tablet should allow you to boot once again - at the cost of deleting everything you put on the device, including all files you put on the (pseudo-) SD card.
If that is the case:
- press and hold power+vol-down until the bootloader screen shows up
- use vol-up/vol-down to select "start recovery" and press the power button
- an android lying on it's back should show up; this is the stock recovery splash screen, so
- press power+vol-up simultaneously for about one second - the stock recovery menu should show up
- select factory reset (with vol-up/vol-down) and press the power button.
good luck
Click to expand...
Click to collapse
when you say at the cost of deleting everything, does this include deleting everything in the bootloader because thats what I did when I used the command "fastboot erase bootloader"

[TUTORIAL][CM11][4.4.2] CyanogenMod Tutorial for Sony Xperia Tablet Z (pollux)

I went through a lot of searching and trouble to install CM11 on my Xperia Tablet Z, and I'd like to share a tutorial I made for anyone who is also wanting to accomplish this.
All links are in Dark Green because I cannot post links yet.
1. Download and extract the ADB+Fastboot+Drivers zip (alexpja.com/sony/adb-fastboot-win.zip)
2. Now we’ll unlock the bootloader.
a. If you do not have a Phone app (like I don’t on the SGP351), you can either get the IMEI from About -> Status in the settings OR you can find the IMEI right after the IC code, nearby the barcode on the bottom of the tablet.
b. If you do have a Phone app, enter *#06# to retrieve the IMEI.
c. Save this for later use.​3. Place the tablet into fastboot mode and connect it to the computer.
a. Power off the device
b. Connect USB to computer
c. While plugging in the other side of the USB cable into the tablet, hold down the Vol + button.
d. If your speakers are on, you should a sound.
e. We have to install the drivers for fastboot. Open devmgmt.msc via the Run window or in the Start menu and in Other Devices section, you should see S1 Service or S1 Fastboot (anything containing S1).
i. If it is showing a yellow exclamation mark: Follow 3.e.i.1. If it is not, continue to 3.f.
1. We need to download Flashtool and use the driver setup. Download Flashtool (unrestrict.li/flashtool) and install it.
2. Find cmd.exe, right click it, and select Run as administrator.
a. Type in
Code:
bcdedit /set testsigning on
and press enter.
b. Reboot your computer.​3. Once you have rebooted the computer, open the folder where you installed Flashtool (default: C:\Flashtool).
4. Open up the drivers folder and open Flashtool-drivers.exe.
5. Select the first two driver choices (Flashmode and Fastboot) and select “Xperia Tablet Z Drivers” and continue.
6. A new window will appear, continue on with that.
7. A window like this may appear a few times, just press Install this driver software anyway.
8. Run 3.e.2. again and run
Code:
bcdedit /set testsigning off
. Reboot your PC now or after the tutorial.​f. The LED pulse light above it should be emitting a blue-ish color. The screen will be dark.​4. Now we’ll verify if you have fastboot running.
a. Open the tools folder that was extracted from the ADB ZIP and double-click on START.cmd to open Command Prompt in the current directory (all it does is literally open cmd.exe, you can edit the script to verify).
b. Run the command
Code:
fastboot -i 0x0fce getvar version
. If you get
Code:
<waiting for device>
, then you did something wrong. Retrace your steps! (For example, I get
Code:
version: 0.5
)​5. Go to (unlockbootloader.sonymobile.com) and continue until you reach the screen where you put type in the IMEI and an email address. Type in the first 14 digits of the IMEI (remove the last one) and your email address (not sure if name is required). You should get an email instantly with the key.
6. In the Command Prompt, run
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY is the key you received in the email from Sony.
7. Download whatever release you would like to use on the tablet (I’m using CM 11 nightly) from (download.cyanogenmod.org/?device=pollux)
a. Optional: Also download gapps for Google apps such as Gmail, Google Play Services, etc. (wiki.cyanogenmod.org/w/Google_Apps)​8. Extract the ZIP file (but don’t delete it either) and copy boot.img to the tools folder.
9. If your device is still turned off, turn it on and enable USB storage mode. Copy the CM zip to either the internal storage (sdcard) or, if one is inserted, the microSD card (sdcard1).
10. Place it into fastboot mode again (#3).
11. Go back into the Command Prompt and enter:
a.
Code:
fastboot -i 0xfce flash boot boot.img
b.
Code:
fastboot -i 0xfce reboot
c. Enter recovery.
1. Once it shuts down, rapidly tap the Vol + button in order to get into the recovery.
2. Grep_The_Truth's tip: Look at the LED. It will turn orange and afterwards it'll turn purple. You want to press Vol+ as soon as it changes colors.​12. Select “wipe data/factory reset” and wipe it. Afterwards, go back to main menu.
13. Select “Install zip” and either select “Choose zip from /sdcard” (internal storage) or “Choose zip from /storage/sdcard1” (microSD card).
I’ve had varying experience with installing from the /sdcard because sometimes it doesn’t want to mount /data while wiping (/data/media which is /sdcard is safe in wipe) the tablet, so if you were to install the zip from /sdcard with the error present, it would screw things up. I prefer the microSD card route (/storage/sdcard1), and you don’t even need a big one. 512MB works just fine. The actual path would be /sdcard/0/ when looking for the cm.zip in the internal storage.
14. When you have chosen to install from either /sdcard or /storage/sdcard1, select the cm.zip and install it.
a. If you downloaded gapps.zip, install it the same way as you did with the cm.zip.​15. Go back to the main menu now and select “reboot system now”
a. Once, I had the option to install root access before rebooting, I declined (was planning on rooting after tutorial) but it gave me root anyway.​
That’s it! You can now use CyanogenMod with the Sony Xperia Tablet Z.

Getting in to recopvery
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
c. Once it shuts down, rapidly tap the
Code:
Vol +
button in order to get into the recovery.
Click to expand...
Click to collapse
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.

Grep_The_Truth said:
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Click to expand...
Click to collapse
I'll add it along with mine, because I can do it with no problem.

alexpja said:
I'll add it along with mine, because I can do it with no problem.
Click to expand...
Click to collapse
alexpja Thanks for your tutorial, this is very detailed and easy to follow.
my Xperia is SGP321.
I put it into practice and the results it gives me the "oem unlock" is:
FAILED: (remote: Command nor allowed).
I guess you should treat my tablet has the bootloader locked and not allowed (for now??) the unlocked.
I hope someone gives us the opportunity to unlock the devices and in the future can be unlocked.

I had the same experience where at times the steps were a little confusing, especially for a beginner. Each set of instructions would either leave something out or skim over it as if everyone already knew it. That's understandable since they were probably written for that audience. I soft-bricked my SGP311 at least 10 times.
I was even going to write something like this but I got lazy.
One suggestion I would offer is to request the bootloader unlock key first since it sometimes takes a little while and a person can reduce the possibility of having to stop and wait just when they are making progress.
And for anyone going this route for the first time, don't make my mistake - flash exactly what the instructions say to flash, particularly boot.img. Once you have that recovery flashed you have a lot more control over your device. If something goes wrong in a following step like getting boot loops you can still fix it. But if you get annoyed and start poking at it then you can mess up the recovery. Then you have to reset everything to stock and just about start over.
While I don't want to say something stupid like claiming the tablet is indestructible, I found that whether I got stuck in a boot loop I couldn't get out of or screwed it up so bad that all I could get from the tablet was an occasional LED flash, I could always restore it using Emma. It's annoying to have to start all over but it's a huge relief when it boots normally.

for me flashing was fine and without any error but my Tab doesn't boot up with CM flashed...any idea?

Hanging at reboot
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.

Guess my bootloader won't be unlocked. This is A lot of work. Good job on the write up though maybe one day I'll tackle it.

BOOT LOOP Step 9
All was going well, but step 9 powering on device, now its looping.....Ill use flash tools to put jelly bean on and try again, since i was trying with kitkat...why i suspect kitkat is the issue, before i used to be able to unlock and lock boot-loader with jelly bean but with kitkat it didn't work, which i then forced it via cmd

No GPS
I used the tutorial for my Pollux Windy (WiFi Only) and used the latest nightly. everything went well but my GPS is now broken. Is this a known issue?

kevinsickles said:
Is this a known issue?
Click to expand...
Click to collapse
yep! use search to find out more.

mulebreath said:
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Click to expand...
Click to collapse
Hi,
I've been trying with my Xperia Tablet Z Wi-Fi SGP311. Ran into the same problem. On reboot command the LED was stuck on red for 10 minutes and the cmd window was still open. I unplugged the USB and the LED would not turn off. Tried some things, I don't remember specifically what, but it got the LED to turn off. Now my device can't be detected. I've downloaded Emma and it is not recognising my tablet. I've tried to plug the USB in while hold Vol +, Vol -, and the Power button. No detection for any. All I can do with my tablet is make the LED flash white, purple and red in rapid succession by holding Vol + and Power for 5 seconds.
Anyone know what's happened? I suspect I've completely bricked it :L
EDIT: Apparently there are different modes which you can cycle through. If you hold down Vol + and Power for 5 seconds, the LED will flash according to which mode the tablet is in. The different modes give these flashes:
- 1 White flash
- 3 Rapid which flashes
- A white, purple and red flash in quick succession
To switch between the modes, I hold down Vol+ and Power, and after 5 seconds it will take around 3 more seconds to change modes. One of these modes will not appear unless plugged into a PC. What do these mean and can I do anything with it? Tablet is still bricked.
EDIT2: I've managed to get Emma to recognise my tablet. Turns out the modes do have different purposes. I should be fine now, problem solved. I will just leave the solution here in case anyone runs into the same problem.
Unplug your device and hold Vol + and Power for 10 seconds. At the 5 second mark your LED should flash white ONCE. Keep both buttons held and within 5 more seconds, your LED will flash white THREE times consecutively. This will allow you to enter Flashmode (plug in USB while holding Vol -) and Fastboot (plug in USB while holding Vol +). For Emma to recognise your device, enter Flashmode and you can restore and try again.

Bootloop
I've tried many times to flash cyanogenmod onto my Xperia Tablet Z (SGP311). This is a Wi-Fi only tablet and I have downloaded the versions of CM from (download.cyanogenmod.org/?device=pollux_windy) I've followed all of the steps and tried all of the versions of CM down to 10.2 (I used GApps10.2 for CM10.2). Each version gets stuck in bootloop. I've cleared all data (in CWM - wipe data/factory reset, wipe cache partition, wipe delvik cache) before flashing CM and GApps; however, when I try to clear data I get an error. This is what the tablet says:
-- Wiping Data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cacha
Formatting /sd-ext...
Formatting /sdcard/.android_secure!
Skiiping format...
Data wipe complete.
Click to expand...
Click to collapse
I'm thinking the "Error mounting /data" is the problem, but I'm not entirely sure, nor am I sure of how to fix it.
Any suggestions?
EDIT: Turns out I'm just really bad with Android stuff. I ended up flashing the original Xperia software, unlocking the bootloader (according to this tutorial's instructions), then I downgraded to 4.1.2, rooted my tablet (forum.xda-developers.com/showpost.php?p=53063218&postcount=14) and installed the PhilZ and TWRP custom recoveries. I didn't get to use them in the end. For some reason CWM kept coming up no matter what combination of buttons I pressed while rebooting. After downgrading and rebooting, I followed the rest of the instructions on this tutorial (from step 7). This time I got no errors while cleaning the disk, cache and delvik cache. Flashed the zip files, rebooted the device and voila, Cyanogenmod11!
Again, I'll leave this edit here in case someone runs into a similar problem. I couldn't get any version of CM until I rooted first.

I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!

tp_88 said:
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
Click to expand...
Click to collapse
download a proper stock (not bricked) firmware for your device and flash with flashtool.

Rootk1t said:
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Click to expand...
Click to collapse
What makes you think that the stock firmwares I've tried are bricked? I've since my post tried one which I downloaded through Flashtool - same result.

How to rollback from Lollipop to KitKat (ME176C/CX)

How to rollback to KitKat from Lollipop​FIRST OF ALL:
Make sure that ADB Asus drivers and Intel USB Drivers are installed on your computer
Download this archive with all required files
IMPORTANT!​
IF YOU HAVE UNLOCKED BOOTLOADER AND PERMANENT TWRP - RECOVER STOCK ESP AND RECOVERY
I'm not responsible for all problems, if they will happen with your tablet
Instruction:
Unpack WW_ME176C_V12.10.1.17-userdebug-201505051557-rawdata.zip from archive
Connect via USB-cable, press and hold Volume Up + Volume Down + Power Key for 3-5 seconds, you'll get smth like "Fastboot starting..."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If Android robot doesn't appears - launch debrick-flashall-FW-no_wipe.cmd
If Android robot appears - launch debrick-flashall-no_wipe.cmd
Check firmware version in setting, it must be like here
Unpack FWI_to_UEFI_ME176C.7z
Launch flash_ME176C_IFWI.cmd
After completing plug off USB-cable and turn off tablet
Press and hold Volume Up + Volume Down + Power Key for 3-5 seconds, you'll get ASUS logo
Plug in USB-cable, copy debrick-flashall-FW-no_wipe.cmd from FWI_to_UEFI_ME176C.7z
to WW-ME176C-3.2.23.201-release-user-20150115-signed.zip. Launch .cmd
Done...
Credits to AKASer and Skyrimus from 4pda
IF YOU HAVE GOOGLE SERVICES CRASHES - DELETE 9.9.56 VERSION AND INSTALL 9.9.55

I want to help here. I made the process a little bit diferent. To connecting the tablet to the pc i enter fastbot mode. Press power+Vol down until the robot appear.
Then launch 4- not 3-.
In the same way launched every step that the tablet needed to be connected to pc, like 7-.
In step 9- pressed Vol up+ power to enter droidboot then do 10, were it sais launch cmd you have to launch debrick-flashall-FW-no_wipe.cmd in the new location.
The tablet works excelent, very happy here, thanks!!
---------- Post added at 08:09 AM ---------- Previous post was at 08:00 AM ----------
Ok, it was not easy to root .201, stuck in demo mode like 3 times. This is the correct way:
-Download this version of root zenfone:https://cloudup.com/files/ivrnLUAwMDS/download
-Download supersu from the playstore and install it.
-Install and open root zenfone, let the app run and don't put OK when it enter demo mode. Let it run for 15 seconds and just restart the tablet without pressing anything.
-If everything is ok you will be rooted.
-In case things go wrong and you enter demo mode, you have to press back button for 10 seconds, then it will ask you for a code, put 741603 and confirm. It will factory reset your tablet and demo will be gone. In case it not enter factory reset you will need to do it manually, after puting de code.
For me google play service bug dissapear when disabled google as device administrator of the device.
This tablet work 10 times better with Kitkat, it doesn't restart, it is stable, a lot better ram manager. The only problem i figure out ia battery stats, it's very buggie. I can use the tablet 1 hour with 1% of the battery, it happen to me with this tablet in all version since i buy it, maybe my battery is wrong...

Please. I lost the stock ESP and recovery. can someone upload the two files here? I have me176c ww version. I do not want to suffer more random reboots.

HELP!
I did all that and it stuck in the bootloop. Can't get in to fastboot or boot menu either.
OK... The only thing seems to be working is droidboot. When I try to go in to recovery then it will show belly up droid.
-------------------------------------
Edit: Alrighty mighty... I did it.
I consider my self and Android idiot cuz I've managed to f*ed up 2 devices beyond repair and even I am able to do this.
My K013 was latest Lollipop update .36, rooted, exposed, striped off system apps to bare minimum.
Here's what I did, step by step.
0. Pre-flight check.
Install ASUS_Android_USB_drivers_for_Windows downloaded from here> https://www.asus.com/support/Download/39/1/0/6/32/
Once you got the zip, unzip it then go to extracted folder > Windows_XP_VISTA_7_8_8.1 > Android, right click on android_winusb and click Install.
Install Intel USB Driver for Android downloaded from here> https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
This one is install shell, easy.
1. Turn off the tablet.
2. Hold volume down and power until you see Asus logo, now you can release power button but sill hold the volume down button. This will get you in to fastboot.
3. Plug in the USB cable.
4. Unpack WW_ME176C_V12.10.1.17-userdebug-201505051557-rawdata.zip then do #4 in tutorial.
5. When finished, unplug the USB and let it boot. Go and check as step 5.
6. Turn on developer mode by go to Settings > About > Software Information and rapidly tap "Build number" until you see the message "You are now a developer!".
7. Go to Developer options and turn on USB debugging. Then plug in the USB cable.
8. Do step 6 and 7.
9. When finished, unplug the USB cable and turn off the tablet.
From here on are what I find tricky-----------------------------------
10. Unpack WW-ME176C-3.2.23.201-release-user-20150115-signed then copy debrick-flashall-FW-no_wipe.cmd from from FWI_to_UEFI_ME176C folder and put it in the extracted folder.
11. Hold volume up and power buttons until you see Asus logo then release both buttons. It will enter droidboot like in this picture.
12. Plug in USB cable, run debrick-flashall-FW-no_wipe.cmd from WW-ME176C-3.2.23.201-release-user-20150115-signed folder.
13. When it reach this part
Do not close this window yet. You have to go in to droidboot again (otherwise it will go in to bootloop just as mine did).
What I did was unplug it, turn it off and repeat my step 11. Then plug in the USB and it will resume installing new.... old.... I mean 4.4.2. This will take some time, just don't let you PC go in to sleep or accidentally disconnect the USB.
Once it finish, unplug the USB cable and let it boot up. Now, go enjoy your K013 running 4.4.2.

Thanks
thegreatn_ said:
How to rollback to KitKat from Lollipop​FIRST OF ALL:
Make sure that ADB Asus drivers and Intel USB Drivers are installed on your computer
Download this archive with all required files
IMPORTANT!​
IF YOU HAVE UNLOCKED BOOTLOADER AND PERMANENT TWRP - RECOVER STOCK ESP AND RECOVERY
I'm not responsible for all problems, if they will happen with your tablet
Instruction:
Unpack WW_ME176C_V12.10.1.17-userdebug-201505051557-rawdata.zip from archive
Connect via USB-cable, press and hold Volume Up + Volume Down + Power Key for 3-5 seconds, you'll get smth like "Fastboot starting..."
If Android robot doesn't appears - launch debrick-flashall-FW-no_wipe.cmd
If Android robot appears - launch debrick-flashall-no_wipe.cmd
Check firmware version in setting, it must be like here
Unpack FWI_to_UEFI_ME176C.7z
Launch flash_ME176C_IFWI.cmd
After completing plug off USB-cable and turn off tablet
Press and hold Volume Up + Volume Down + Power Key for 3-5 seconds, you'll get ASUS logo
Plug in USB-cable, copy debrick-flashall-FW-no_wipe.cmd from FWI_to_UEFI_ME176C.7z
to WW-ME176C-3.2.23.201-release-user-20150115-signed.zip. Launch .cmd
Done...
Credits to AKASer and Skyrimus from 4pda
IF YOU HAVE GOOGLE SERVICES CRASHES - DELETE 9.9.56 VERSION AND INSTALL 9.9.55
Click to expand...
Click to collapse
Thanks dude, this helped a lot! Now I don't have to use sluggish Lollipop

Are really necesary the stock esp and recovery? I missed that.

Ok. I take the esp.img and recovery.img from WW_ME176C_V12.10.1.17-userdebug-201505051557-rawdata.zip and flash this like in the bootloader unlock tutorial.
---------- Post added at 04:32 PM ---------- Previous post was at 04:28 PM ----------
Beaver_XT said:
HELP!
I did all that and it stuck in the bootloop. Can't get in to fastboot or boot menu either.
OK... The only thing seems to be working is droidboot. When I try to go in to recovery then it will show belly up droid.
-------------------------------------
Edit: Alrighty mighty... I did it.
I consider my self and Android idiot cuz I've managed to f*ed up 2 devices beyond repair and even I am able to do this.
My K013 was latest Lollipop update .36, rooted, exposed, striped off system apps to bare minimum.
Here's what I did, step by step.
0. Pre-flight check.
Install ASUS_Android_USB_drivers_for_Windows downloaded from here> https://www.asus.com/support/Download/39/1/0/6/32/
Once you got the zip, unzip it then go to extracted folder > Windows_XP_VISTA_7_8_8.1 > Android, right click on android_winusb and click Install.
Install Intel USB Driver for Android downloaded from here> https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
This one is install shell, easy.
1. Turn off the tablet.
2. Hold volume down and power until you see Asus logo, now you can release power button but sill hold the volume down button. This will get you in to fastboot.
3. Plug in the USB cable.
4. Unpack WW_ME176C_V12.10.1.17-userdebug-201505051557-rawdata.zip then do #4 in tutorial.
5. When finished, unplug the USB and let it boot. Go and check as step 5.
6. Turn on developer mode by go to Settings > About > Software Information and rapidly tap "Build number" until you see the message "You are now a developer!".
7. Go to Developer options and turn on USB debugging. Then plug in the USB cable.
8. Do step 6 and 7.
9. When finished, unplug the USB cable and turn off the tablet.
From here on are what I find tricky-----------------------------------
10. Unpack WW-ME176C-3.2.23.201-release-user-20150115-signed then copy debrick-flashall-FW-no_wipe.cmd from from FWI_to_UEFI_ME176C folder and put it in the extracted folder.
11. Hold power up and power buttons until you see Asus logo then release both buttons. It will enter droidboot like in this picture.
12. Plug in USB cable, run debrick-flashall-FW-no_wipe.cmd from WW-ME176C-3.2.23.201-release-user-20150115-signed folder.
13. When it reach this part
Do not close this window yet. You have to go in to droidboot again (otherwise it will go in to bootloop just as mine did).
What I did was unplug it, turn it off and repeat my step 11. Then plug in the USB and it will resume installing new.... old.... I mean 4.4.2. This will take some time, just don't let you PC go in to sleep or accidentally disconnect the USB.
Once it finish, unplug the USB cable and let it boot up. Now, go enjoy your K013 running 4.4.2.
Click to expand...
Click to collapse
This works for me. Thanks!!!
*in step 11. is Hold volume up...

Oops. Thanks for correction.

at step 7 (flash_ME176C_IFWI.cmd) i can't go further, error 123 when trying to start demon, but i have usb debogging activated, what am i missing (i am on windows 10 anniversary update , i have disactivated drivers signature verification but i can't download intel drivers, the url can't seem to allow me the download).

I had this error too.... You must copy the extracted folders on a other place! On the Desktop works for me... I think theres read/write restrictions from the system....
I flashed succesfully with windows 10....

idoetzchen said:
I had this error too.... You must copy the extracted folders on a other place! On the Desktop works for me... I think theres read/write restrictions from the system....
I flashed succesfully with windows 10....
Click to expand...
Click to collapse
thought so but wasn't sure, i tried from the download folder in a folder with russian caracters on a french windows 10 x64, so i was thinking it was a name issue, will retry from another folder on root and use a simpler folder name.

moving and renaming the folder did the trick, my me176cx just did it's first 4.4.2 boot in a while.

NahuelMS said:
I want to help here. I made the process a little bit diferent. To connecting the tablet to the pc i enter fastbot mode. Press power+Vol down until the robot appear.
Then launch 4- not 3-.
In the same way launched every step that the tablet needed to be connected to pc, like 7-.
In step 9- pressed Vol up+ power to enter droidboot then do 10, were it sais launch cmd you have to launch debrick-flashall-FW-no_wipe.cmd in the new location.
The tablet works excelent, very happy here, thanks!!
---------- Post added at 08:09 AM ---------- Previous post was at 08:00 AM ----------
Ok, it was not easy to root .201, stuck in demo mode like 3 times. This is the correct way:
-Download this version of root zenfone:https://cloudup.com/files/ivrnLUAwMDS/download
-Download supersu from the playstore and install it.
-Install and open root zenfone, let the app run and don't put OK when it enter demo mode. Let it run for 15 seconds and just restart the tablet without pressing anything.
-If everything is ok you will be rooted.
-In case things go wrong and you enter demo mode, you have to press back button for 10 seconds, then it will ask you for a code, put 741603 and confirm. It will factory reset your tablet and demo will be gone. In case it not enter factory reset you will need to do it manually, after puting de code.
For me google play service bug dissapear when disabled google as device administrator of the device.
This tablet work 10 times better with Kitkat, it doesn't restart, it is stable, a lot better ram manager. The only problem i figure out ia battery stats, it's very buggie. I can use the tablet 1 hour with 1% of the battery, it happen to me with this tablet in all version since i buy it, maybe my battery is wrong...
Click to expand...
Click to collapse
A way easyer (and definitive) solution to root the tab is to use the tethered recovery and flash supersu, worked for me

Well new problem, i don't remember how to properly install xposed on kitkat on this tab. Tried the official installer but the settings in gravity box for kitkat are ignored.

@Saarge
Hi,
i use the 2.7 experimental version but gravity box won't work but hk theme engine works good for changing icons and other theme stuff but it doesn't change the homescreen/settings screen backgrounds for this i use holo background themer.
To change the softbar buttons i use another theme engine mod.So with this three modules one can customize the tab pretty well.But i didn't found a mod to change the quick menu settings yet.

can i do this for the android 5.1.1 version? quote me so i know someone replied to me

Kennii said:
can i do this for the android 5.1.1 version? quote me so i know someone replied to me
Click to expand...
Click to collapse
There is no 5.1.1 for this tablet. Last firmware is 5.0.1 lollipop .36 and you can rollback to kitkay in any lollipop version.

Hello,
Thanks for your great post !
I have a problem after step 4, my tablet reboot but after ASUS LOGO, my screen still black !

Thanks, i did it in my Linux box, everything worked fine. Now the tablet is usable again!

black screen
im getting black screen after step 4

Axon 7 bricked and I'm in a very tight situation. Any quick solution?

To sum it up quickly, I put my Axon 7 up for sale on ebay. 5 day listing. It currently has ~24 hours left on it and plenty of bidders. ZTE Gladly offered a replacement but it would take 10 or more days. I had previously rooted the phone, and wanted to send it as though it came from the factory. I went into fastboot, did 'fastboot oem lock' over the fastboot shell, and it said successful. The device "rebooted" into a black screen. The device now appears to be bricked. It will show a ZTE logo for about a second when I hold the power button and then no more. I cannot seem to get it respond to a charge, go into fastboot, recovery, or anything else except what I described. It sounds hopeless to me, but maybe someone here is a miracle worker. Thank you very much.

for starters which model to you have?

You were completely stock, not rooted before locking?

lafester said:
You were completely stock, not rooted before locking?
Click to expand...
Click to collapse
I had flashed CM to it previously but when I did a relock I had reflashed stock MiFavor found here on XDA.
Edit: TWRP official a2017u was on the device, and I may have flashed supersu as well during the stock reflash. It was almost a week ago, I can't remember.
DrakenFX said:
for starters which model to you have?
Click to expand...
Click to collapse
A2017U

erer1243 said:
I had flashed CM to it previously but when I did a relock I had reflashed stock MiFavor found here on XDA.
A2017U
Click to expand...
Click to collapse
If you can boot to recovery you can try using ZTE B20 file, look here https://www.zteusa.com/axon-7#support under SOFTWARE UPDATES
* Move that file to your SDCard ,
* Boot to your recovery and flash that file.

DrakenFX said:
If you can boot to recovery you can try using ZTE B20 file, look here https://www.zteusa.com/axon-7#support under SOFTWARE UPDATES
* Move that file to your SDCard ,
* Boot to your recovery and flash that file.
Click to expand...
Click to collapse
I cannot boot into recovery. I cannot do anything except what I described, the quick ZTE logo, and then nothing. The computer does recognize that there is a device plugged in though, but ADB and fastboot will not see it.

erer1243 said:
I cannot boot into recovery. I cannot do anything except what I described, the quick ZTE logo, and then nothing. The computer does recognize that there is a device plugged in though, but ADB and fastboot will not see it.
Click to expand...
Click to collapse
not even Manual boot to recovery?
Press & Hold Volume Up + Power till menu kicks in.
you other option booting to EDL and use @tennear or tenfar tool to flash TWRP ONLY and flash that file or my B29.MergeBootstack and StockSystem files

DrakenFX said:
not even Manual boot to recovery?
Press & Hold Volume Up + Power till menu kicks in.
you other option booting to EDL and use @tennear or tenfar tool to flash TWRP ONLY and flash that file or my B29.MergeBootstack and StockSystem files
Click to expand...
Click to collapse
Nothing happens. It will not go into fastboot or recovery, no matter what I hold, for how long, anything. I believe it is either trying to display the "Your device cannot be trusted" screen and fails or is trying to do some other thing during pre-boot and is stuck in a loop. I don't know what EDL is but I'd be willing to tear this phone a new asshole if I can fix it within 24 hours. Happy to try anything, it seems like it can't get any worse than this.

erer1243 said:
I believe it is either trying to display the "Your device cannot be trusted"
Click to expand...
Click to collapse
this means, you still UNLOCK, when you are there and i mean when that message shows up, press any of the volume key and will give you a menu, from there you can boot to recovery - fastboot - bootloader.
if you see that menu, BOOT to BOOTLOADER and tell me the status.

DrakenFX said:
this means, you still UNLOCK, when you are there and i mean when that message shows up, press any of the volume key and will give you a menu, from there you can boot to recovery - fastboot - bootloader.
if you see that menu, BOOT to BOOTLOADER and tell me the status.
Click to expand...
Click to collapse
Well I just successfully locked it before making the thread... So it is not unlocked any longer. That was just speculation. I have no menus, holding down volume buttons and power does not do anything, I cannot get into fastboot, recovery, etc at all.

erer1243 said:
Well I just successfully locked it before making the thread... So it is not unlocked any longer. That was just speculation. I have no menus, holding down volume buttons and power does not do anything, I cannot get into fastboot, recovery, etc at all.
Click to expand...
Click to collapse
you know how to manually boot to EDL? so you can use any of the tool to flash TWRP.
manually booting to EDL and to make sure is in EDL mode CONNECT your device to your PC/Laptop and open DEVICE MANAGER now just Hold & Press Vol. Up and Down and make sure you are pressing both , if you are using case take the phone out of the case so you can really do it. Once you are pressing and holding both volume keys, press Power and check Device Manager for Qualcomm Port your device is using.
after that just proceed with the rest.

Just to make it a little clearer, to go to EDL mode. Phone must be off when you connect to PC, you hold both volume up/down and then touch power. It will still remain off BUT should now be recognized by the PC's device Manager.

I was in the same situation before. Using tenfar's tool to flash tenfar's TWRP (not official TWRP) the phone will boot TWRP with a locked bootloader. Then, go https://www.zteusa.com/axon-7 there and click the Support tab, then the Software Updates subsection. Download that, it could take a while though.
Once that's done, open the update.zip in something like 7-Zip and navigate to META-INF\com\google\android and extract the file updater-script. Open it with Notepad++ (not Notepad) or, if you're not on Windows, the text editor of your choice.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On line 2, which is highlighted, delete that line. If you don't do this, it won't flash in TWRP. Don't worry though, it won't mess anything up. After saving, drag the extracted updater-script back into the zip file and confirm that you want to replace it.
Then, once your phone is in TWRP, copy the update.zip to your phone and flash it. For me, it took about 7 or 8 minutes to flash.
This part is the most important, absolutely do not skip this:
Before you reboot go back to the main TWRP menu and open the Mount menu. Uncheck system and then reboot. This is because TWRP installs a survival script in /system if it can, because otherwise TWRP will be changed to stock recovery. In this case though, it's what we want. This way OTA updates will successfully install. Stock recovery checks for any changes to /system and refuses to work if it sees any change at all, like the one TWRP makes unless you unmount system before you reboot.
After rebooting, you should update your phone from B20 to B27 and then from B27 to B29 to be up to date.
Also, this will re-lock your bootloader!
If you have any questions please ask, hopefully that helped you and maybe others too

RainofOranges said:
I was in the same situation before. Using tenfar's tool to flash tenfar's TWRP (not official TWRP) the phone will boot TWRP with a locked bootloader.
Click to expand...
Click to collapse
Maybe I just haven't looked hard enough... but I can't find any working instructions on how to flash/boot to a recovery. When I go by his instructions, nothing seems to work. I have, in the same folder as axon7root.exe, a recovery.img that is tenfar's twrp release. I have installed the driver he linked. I run axon7root -p 4 -r (yes, my phone is connected to the COM4 port) and the program just prints his little copyright splash screen and nothing happens. I have left it for ~half an hour, so it's obviously not just taking it's time. When I unplug the phone, it tells me my horse is dead (lmao someone get on translation) so it obviously knows the phone is there, but it just cannot do anything. Also, I cancelled the ebay listing a few minutes before seeing your post, disappointingly. Hopefully I can revive my horse and relist it.

erer1243 said:
Maybe I just haven't looked hard enough....
Click to expand...
Click to collapse
Are you sure your phone is in EDL mode? Did you try running it through a command promp as Administrator?

RainofOranges said:
Are you sure your phone is in EDL mode? Did you try running it through a command promp as Administrator?
Click to expand...
Click to collapse
I will try running it as admin. I am unsure how to tell if my phone is in EDL mode. I have reason to believe that it is stuck in a silent boot loop and maybe I can't get it into EDL/any other mode but I am just speculating there. I think that because 1, it won't respond to a charge and 2, I have to hold down the power button much longer than usual to make the ZTE logo pop up; It's as though I had to force shut down the phone and then boot it again in the 1 press.

erer1243 said:
Maybe I just haven't looked hard enough... but I can't find any working instructions on how to flash/boot to a recovery. When I go by his instructions, nothing seems to work. I have, in the same folder as axon7root.exe, a recovery.img that is tenfar's twrp release. I have installed the driver he linked. I run axon7root -p 4 -r (yes, my phone is connected to the COM4 port) and the program just prints his little copyright splash screen and nothing happens. I have left it for ~half an hour, so it's obviously not just taking it's time. When I unplug the phone, it tells me my horse is dead (lmao someone get on translation) so it obviously knows the phone is there, but it just cannot do anything. Also, I cancelled the ebay listing a few minutes before seeing your post, disappointingly. Hopefully I can revive my horse and relist it.
Click to expand...
Click to collapse
Mine did that - unplug phone, restart computer, hold both volume buttons and plug phone back in.

erer1243 said:
I will try running it as admin. I am unsure how to tell if my phone is in EDL mode. I have reason to believe that it is stuck in a silent boot loop and maybe I can't get it into EDL/any other mode but I am just speculating there. I think that because 1, it won't respond to a charge and 2, I have to hold down the power button much longer than usual to make the ZTE logo pop up; It's as though I had to force shut down the phone and then boot it again in the 1 press.
Click to expand...
Click to collapse
You can't tell that the phone is in EDL mode on the phone itself. You can only tell by trying the tool. If I remember right the button combination to get into EDL mode is both volume buttons held down and the power button also held down for 2 seconds or so at the same time.

tabletalker7 said:
Mine did that - unplug phone, restart computer, hold both volume buttons and plug phone back in.
Click to expand...
Click to collapse
No dice. As admin, computer restarted, I tried holding both volume buttons while plugging in.

update from my last post: I got tenfar's tool to upload his TWRP to the phone (sent it to the horse o.o) but it still will not boot anywhere. The phone has not changed at all.