Database Users

How to get into Download Mode

Samsung Vibrant Download Mode
Method 1 (without ADB):
1. Take out battery, put it back in. (to turn the phone fully off)
2. Don't turn it the phone on!
3. Plug the phone into your PC, do not hit the power button!
4. See if the phone shows anything on the screen (screen turns on when plugged in) EX: Shows a battery, shows error messages if bricked, etc. Shows anything.
IF the phone screen does 'turn on' after being plugged in without you hitting the power button, so far so good.
5. Now while it's on like this, hold both the volume up and volume down buttons.
6. Hold the power button as well as the volume buttons until the screen goes black.
7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons!
This is how I got into download mode to fix my 'odd' brick.
Method 2 (with ADB):
1. Turn your phone on
2. Go to Settings -> Application Settings
3. Enable Debug Mode
4. Plug your phone into your PC
5. Install Android SDK
6. Open Command Prompt
7. Type: cd C:\android-sdk-windows\tools
8. Type: adb reboot download
Either of these methods *should* get you into Download mode. After that you should be able to use Odin to revert to stock, tar and instructions here:
http://forum.xda-developers.com/showthread.php?t=734475
Or flash anything with Odin.

I am in a situation where I rooted my phone but never made a recovery and now I did a factory reset and I only get a force close loop when booting and cannot do anything. I am not able to get into debugging mode to use ADB and the hardware buttons are not working any suggestions on how I can fix this
The only thing i did was remove some bloatware which is why I did not do a recovery since I wasnt removing anything important. Phone worked fine until I tried to do the factory reset now everything just force closes and cannot do anything

I turned my phone on then removed battey. hold vol up and down together then plug the phone in via usb to pc, should enter download mode after a few seconds (don't press the power button at all)I use odin to flash back to stock.

THANKS!
This saved my ass lol I was lookin at it like wtf? cuz odin failed and then when i reloaded and tried again nothing happened so i unplugged. I don't know what I was thinking when I did it, but I did lol.
Thanks again bro

sparks.calvin said:
I am in a situation where I rooted my phone but never made a recovery and now I did a factory reset and I only get a force close loop when booting and cannot do anything. I am not able to get into debugging mode to use ADB and the hardware buttons are not working any suggestions on how I can fix this
The only thing i did was remove some bloatware which is why I did not do a recovery since I wasnt removing anything important. Phone worked fine until I tried to do the factory reset now everything just force closes and cannot do anything
Click to expand...
Click to collapse
just Odin back to stock and start over there is realy no other way to fix fc

OP: what youre doing in your hardware button combinajtion method is lettinf it boot, then pressing the up+down vol and doing a hardware reset (by holding power key). You can cut oout a step by holding tthe up down keys when you plug in. It should boot to download automatically.
Also, you should mention in your post that the button combination is different for people who flashed gingerbread bootloaders..
Another thing, i believe the newer android sdk moved the adb package to C:/android-sdk/platform-tools/ ..
To tthe person with the force close issue, read the OP, go into download mode and use odin to flash to stock.
Sent from my SGH-T959 using XDA App

F**king vibrant

Ok I've looked everywhere, maybe not well enough but I have and I can't find the answer to my question. I installed the new official 2.2 on the 10th when it came out in canada here. My phone has worked "ok" for the past 2 days. (lots of new force closes and some major lag in some spots that didn't happen in 2.1) but that's besides the point. Today i was trying to set up a new wallpaper and all of a sudden the screen started flashing on and off. I couldn't do anything to stop it except pull the battery. Now when I turn on the phone it just flashes the opening screen that says "Galaxy S blah blah". and the only way I can stop that is pull the batt. I've tried hard resetting and all that but it always gets stuck at the openning screen. Now I'm still noobish to android stuff. Was too scared to flash anything before the official so if you have any advice that involves other programs/pc i'd appreciate a point in the direction of a walkthrough.
I'd hate to have to send it in and wait the 2 months it takes samsung canada to get it back to me.
Thanks.

http://forum.xda-developers.com/showthread.php?t=732458

tried that, can't get into download mode. as soon as i plug it in it starts looping the boot screen.

canadianrider said:
tried that, can't get into download mode. as soon as i plug it in it starts looping the boot screen.
Click to expand...
Click to collapse
Look up the "jig" solution. That will be guaranteed to set your device on Download Mode.

It was the same problem with my Vibrant. Solved with JTAG controller. But you'll waste your warranty in that way. Try jig solution first

Adb?
Sent from my SGH-T959 using XDA App

ok i have android sdk/adb from when i pulled screen shots with 2.1 ... how could i use that to try and boot my phone

canadianrider said:
ok i have android sdk/adb from when i pulled screen shots with 2.1 ... how could i use that to try and boot my phone
Click to expand...
Click to collapse
option 1
METHOD 2: STUCK AT VIBRANT SCREEN:
(and are not able to use vol+ vol- methods to access downloader/recovery)
You will need the samsung ADB drivers installed for your phone as well as ADB...
ACCESS DOWNLOAD MODE
1) remove back cover and take our sim card and sd-card.
2) take out the battery
3) hold ALL 3 buttons down at the same time. (Vol +, Vol -, Power)
4) while holding down those 3 buttons put the battery back in
5) continue holding all 3 buttons until the vibrant disappears and reappears... once it reappears, release all 3 buttons
6) Setup ODIN and get it all setup and ready... (if you are flashing your phone via odin)
6) now connect your phone to your pc via USB cable
7) open a cmd prompt and navigate to the folder with ADB and type ADB REBOOT DOWNLOAD
8) Your phone will reboot into the download screen... go back to ODIN - A com port should now appear for your phone...
9) Click start and wait for your phone to do its thing
Option 2
***First you must have ROOT***
Download Terminal Emulator from the Market
open terminal emulator
**you may need to change to default android keyboard for proper inputting
1.) type "su" and press enter
a dialog box will appear asking for root access and say yes (obviously)
2.) type "reboot recovery" and press enter
at that moment, ur phone should reboot into Download Mode to load Alternate firmwares for like Eugene's Vibrant4 ROM etc......
this it what it should look like...
#su
#reboot download
Option 3
or you can download and install quick boot from the market which you then can make a shortcut to reboot into recovery with just one click

Sometimes it takes more than one try to get into download mode. I just take the battery out for a little while. Put it back in and hold only the volume up and down buttons while it is off and plug in the USB cable.
One thing though, when holding down the up and down volume buttons, it is very easy to mistakenly press the power button because it is exactly opposite of it.

[Q] Possible Brick. Please help!

Hello,
I tried installing a ROM (Axura) for the first time on my Vibrant. This is what I did:
1. Rooted using z4root's app.
2. Backed up installed ROM (stock 2.1 update 1) using ROM Manager app.
3. Installed CWM.
4. Downloaded Axura v2.3.0.0 from their forum.
5. Placed it in internal SD and renamed to update.zip (backed up the original on my external SD). <-- Possibly the cause of my dismay.
6. Installed it through CWM.
It was installing fine till it got stuck at the fourth "copying file..." line. Was there for over an hour. Now, every time I boot my device it shows Vibrant splash screen and goes to Android System Recovery instead of loading up.
Can anyone please help me out? I think it's a soft brick, since recovery is still being loaded up. Please!
NOTE:
1. reinstall packages gives this error:
E:Can't open /sdcard/update.zip
(bad)
2. abd displays: "error: device not found".

1st you should not have changed auxura to update.zip
You need to odin back to stock.

I might be wrong
But changing name doesnt really matter. It look like u just got a bad download. Odin back and redownload the Rom.
bionix 1.2.1 with adw launcher ex

Yes odin back to stock. Then Root, then get CWM and install. Do not rename the Axura or any custom rom,, this will make it hard for you keeping track. THen after root go to recovery >install rom on sd card> choose> then find the one you want and click that one and you are good to go.

thanks for all the responses! I tried ODIN, but the issue is I can never get into download mode. If I press vol+/- and power I get into recovery. When I try the same with USB connected, the screen keeps looping at the charge screen.
ODIN was able to detect the device in recovery mode at times. but if I try recovery it gives cannot open port.
I'm following the steps (and the required files) from androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/

Turn the phone off hold up & down on the vibrant volume then plug the usb in while holding it down. Make sure odin is open first. No need to touch the power button.
Sent from my SGH-T959 using XDA App

When I try vol+/- and then plugging in the usb (not pressing power at all), it still brings me to recovery screen. the only difference is it skips the "Vibrant SAMSUNG" splash screen.
Also, i realized tht connecting to a different usb port, the command "adb devices" lists the device in recovery. but "adb reboot download" (or any othr reboot command) simply hangs thr, until break command is given..
Any help to get me into download mode? it's been only 4 months, I don't want to discard the device so soon.

azoicwight said:
When I try vol+/- and then plugging in the usb (not pressing power at all), it still brings me to recovery screen. the only difference is it skips the "Vibrant SAMSUNG" splash screen.
Also, i realized tht connecting to a different usb port, the command "adb devices" lists the device in recovery. but "adb reboot download" (or any othr reboot command) simply hangs thr, until break command is given..
Any help to get me into download mode? it's been only 4 months, I don't want to discard the device so soon.
Click to expand...
Click to collapse
Did you try pulling your battery. then press vol + - while holding the power button while inserting the battery?

[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.

I only can reach the Bootmenu. Bricked? What can I do?

Hi,
I'm not very experienced with those root things and followed a tutorial to do so.
I unlocked the bootloader, had TWRP installed and root. This worked. Now I wanted to remove Root and TWRP and go back to the original state. I couldn't find the stock recovery file, so I installed the P996A04V1.3.0B13_MR2_sd_ssl.zip via TWRP from the SD Card. Till here it worked. I could enter the stock recover and boot the phone.
Then Android wanted to install a security update. I allowed it and this is where the problem started.
The install process stood still on 25% for minutes. I thought it stuck and pressed and hold the power button to reboot that I can wipe the memory. But nothing happened. But the installation Process continued suddenly. I had the feeling that this power key worked like a skip key. So maybe it didn't install a file where it was stuck.
After the installation reached 100% the screen switched to black and nothing worked anymore. I couldn't restart the phone or anything but I think the phone was doing something cause it consumed electricity. When I checked the phone hours later I noticed it was empty.
I can reach the unlocked bootloader now, but none of the selections works. Doing nothing to boot or select Recovery lead to black screen and stuck. Then I have to wait until the battery is empty again. Fastboot, Power Off just restart the phone and I end in the Bootmenu again. I can't even fully charge the phone. As soon as it has enough power to start the Bootmenu appears. So I don't see the display of the charging process.
I don't understand how this could happen. I tried different key combinations when the phone had enough electricty to start. The phone always restarts and end in the bootmenu. Only when I press all three keys it's standing still on the ZTE Logo screen but as soon as I release the keys I end again in the bootmenu.
How can I force another Update?
regards

Let' start with the basic questions:
Do you have proper backup of your data?
Which Android Version did your Axon had before it went unusable?
You could try to reflash TWRP.
Boot your phone into bootmode.
Download a proper TWRP Image on your PC (https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Open a cmd shell (press the windows key and type 'cmd' -> press enter)
Navigate to the folder where the TWRP Image is stored ('
Code:
cd C:\Users\[I]YOUR_USER_NAME[/I]\Downloads\
')
Type: '
HTML:
fastboot flash recovery [I]TWRP_IMG_NAME.img[/I]
'
Afterwards you could try to reboot into recovery mode.

I don't have a backup. But there isn't something imortant on the phone that I want to keep. I can do a full reset and reinstall, too.
Android must have been the latest offical availabe what's in the file. Was it Android 8? V1.3.0B13
The fastboot mode doesn't work. The screen turns black and the LED blinks red but only for a moment. Then the phone restarts and I'm in the bootmenu again. Windows doesn't recognize it as device.
Is there a way to force it to do an update from my SDCard without it needed to be connected to a PC?

Stevie123 said:
I don't have a backup. But there isn't something imortant on the phone that I want to keep. I can do a full reset and reinstall, too.
Android must have been the latest offical availabe what's in the file. Was it Android 8? V1.3.0B13
The fastboot mode doesn't work. The screen turns black and the LED blinks red but only for a moment. Then the phone restarts and I'm in the bootmenu again. Windows doesn't recognize it as device.
Is there a way to force it to do an update from my SDCard without it needed to be connected to a PC?
Click to expand...
Click to collapse
I don't know of any.
But you could boot into EDL Mode (Press and hold Both Volume button and then press the power button) and flash a Stock EDL rom from the Download Center i have linkd before.

It's not visible for the PC. The only thing I see is the charging screen when its total empty and you can't even boot as. As soon as it has enough power to switch to the normal screen the bootloader appears and when I do nothing the screen turns black and nothing happens. I don't even know if it is charging. The LED is off.

Follow this guide to unbrick it and then use MiFlash and flash an EDL ROM
https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229