Database Develop

[Q] Bricked Phone

Hi,
I recently got asked by a friend to flash his google nexus one phone. like a mug i said yes and now i have a issue where it turns on, vibrates 7 times and stays at the splash screen with the x on it. I can boot into the fast boot / recovery mode but nothing works.
this happened after i tried to root the phone, it said waiting for device and didnt do anything so i killed the app (Superoneclick) the phone disappeared from device manager and now wont go past the splash screen.
Does anyone have any idea how i can get it back? .. thanks in advance for any help.
James

I'm guessing, since you used S-O-C, the bootloader is not unlocked. The only way I know how to fix it is if you OEM unlock it. You'll need fastboot and your Android SDK setup correctly.
Once you have the setup done, change directories to the tools folder, wherever you put your sdk. Boot your phone into fastboot by holding the trackball while powering it on.
Code:
cd C:\asdk\tools\
Plug your phone into USB, and check if the computer sees it
Code:
fastboot devices
Unlock the bootloader (THERE IS NO GOING BACK! You can never re-lock a Nexus)
Code:
fastboot oem unlock
Now you can flash a boot.img and system.img (preferably pre-rooted) from fastboot, and it should boot normally. If the phone boots, the phone is perma-rooted, and won't need any other rooting procedure (you just need to flash a rooted rom). Next time, be a little more careful

Hi wdfowty
at running the risk of asking for more help and making you cross could you post some links to these downloads?
I am a total newbie to these phones and want to make sure i have the right apps.
thanks again for the help and the quick response... and if i manage to get this phone back believe me it will be the last one i try to flash !!
cheers
James

Nah, you've got me wrong. I'm all about helping people that are willing and able to be helped.
Follow this guide, it'll walk you through the steps to set up your sdk and unlock the bootloader. The guide is a little dated, so the info might not be 100%, but it's generally everything you'll need to know. If you get stuck, feel free to ask.

Hi again,
when i run the command fastboot devices i get an error AdbWinApi.dll is missing.
it tells me to reinstall the app but i have done that and also run all the updates and i still get the same error?
Interstingly i also get the phone to fastboot and it says in red text on the phone fastboot.usb but i cant see anything in device manager that says Nexus one etc?
any more help appreciated.... worst case you dont fancy a christmas break over in England do you?
cheers
james

jamesabennett said:
Hi again,
when i run the command fastboot devices i get an error AdbWinApi.dll is missing.
it tells me to reinstall the app but i have done that and also run all the updates and i still get the same error?
Interstingly i also get the phone to fastboot and it says in red text on the phone fastboot.usb but i cant see anything in device manager that says Nexus one etc?
any more help appreciated.... worst case you dont fancy a christmas break over in England do you?
cheers
james
Click to expand...
Click to collapse
With the latest version of the SDK tools, they changed the directory for adb and fastboot. Unfortunately I'm not on my Windows machine... but check in the directory where you have the SDK extracted to and look for a platform-tools directory (iirc). From there, you should see fastboot.
So basically where it says this "Type: cd C:\android-sdk-windows\tools" change it to "C:\android-sdk-windows\platform-tools". Keep in mind that directory name may change... again, I'm not on my Windows machine right now.

Hi again,
thanks for the continued help. I have managed to get past that, i have OEM unlocked the phone and managed to copy the flash image to the device using the commands in the link you sent me.
problem i have now is when i go into recovery the phone again just pulls up the splash screen and vibrates 7 times.
i believe what should happen according to the link is to follow the 6 steps below.. even i can do that, but the phone doesnt get that far
//Turn phone off -> Hold Volume Down, hold Power button
//Press Volume Down to highlight Recovery -> press Power to select Recovery
//Backup/Restore -> Nand backup
//Wipe -> Wipe data/factory reset
//Wipe -> Dalvik Cache
//Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
another point is it runs a couple of lines of blue txt relating to the sd card, but it flashes up and dissapears too quickly for me to be able to read it and send across to you.
thanks again and if you can work this out i owe you a beer !!
James

jamesabennett said:
Hi again,
thanks for the continued help. I have managed to get past that, i have OEM unlocked the phone and managed to copy the flash image to the device using the commands in the link you sent me.
problem i have now is when i go into recovery the phone again just pulls up the splash screen and vibrates 7 times.
i believe what should happen according to the link is to follow the 6 steps below.. even i can do that, but the phone doesnt get that far
//Turn phone off -> Hold Volume Down, hold Power button
//Press Volume Down to highlight Recovery -> press Power to select Recovery
//Backup/Restore -> Nand backup
//Wipe -> Wipe data/factory reset
//Wipe -> Dalvik Cache
//Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
another point is it runs a couple of lines of blue txt relating to the sd card, but it flashes up and dissapears too quickly for me to be able to read it and send across to you.
thanks again and if you can work this out i owe you a beer !!
James
Click to expand...
Click to collapse
Have you flashed the recovery image using fastboot, or did you only copy the recover image to the sdcard? Step IV in that guide.

It sounds like you need to reinstall your recovery.
Download the recovery found here: http://forum.xda-developers.com/showthread.php?t=611829
Rename that file to recovery.img and place it somewhere you can remember
Boot the phone into fastboot by holding down the trackball and pressing power button.
Code:
fastboot devices
Code:
fastboot flash recovery C:\path\to\recovery.img
If all went well, there should be no errors. On the phone, use the volume keys to select "Bootloader". It will take you to a white screen with the blue text (ignore it, it's looking for update files like "PASSIMG.zip"). Select recovery, and it'll boot into recovery. If you see menu items, you are good!

I ran the fastboot command and used the flash image ending 2.0.0
this is driving me round the bend !!

What happened when you used the fastboot flash command? Did you see a bar on the top right of the phone?

wdfowty said:
It sounds like you need to reinstall your recovery.
Download the recovery found here: http://forum.xda-developers.com/showthread.php?t=611829
Rename that file to recovery.img and place it somewhere you can remember
Boot the phone into fastboot by holding down the trackball and pressing power button.
Code:
fastboot devices
Code:
fastboot flash recovery C:\path\to\recovery.img
If all went well, there should be no errors. On the phone, use the volume keys to select "Bootloader". It will take you to a white screen with the blue text (ignore it, it's looking for update files like "PASSIMG.zip"). Select recovery, and it'll boot into recovery. If you see menu items, you are good!
Click to expand...
Click to collapse
i do that and it accepts the recovery file and the progress bar goes up on the right hand side and the cmd prompt says its all good. then when i select recovery the phone goes to the black background with the four coloured cross and the unlocked padlock, vibrates 7 times and just hangs on that screen
beleive it or not it booted up a moment ago and the phone worked like it did before with v2.2 on it. so i am happy now it can be recovered... i just dont know what to do to straighten it out!

yes. the bar goes up on the right hand side of the phone. and i have definitely unlocked it as it now says unlocked at the top of the menu.

Have you tried to reimage the phone with the passimg method? Directions are provided in the wiki, under the unlock/restore heading:
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Follow PASSIMG method (filename is case sensitive).
The link to the files is on the word "here" on step 2.
Use FRG33.
Sent from my Nexus One using XDA App

Down vol rocker broke, can't enter nvflash/smartflash/recovery?

Great, i tried to flash Hellfire's ICS rom, and for some freakin' reason, the phone got stuck at the hellfire loading screen and won't boot.
The problem is, my down vol button broke quite some time ago, and i can't use the power+vol down in order to save my phone. any ideas?

SoloSkull said:
Great, i tried to flash Hellfire's ICS rom, and for some freakin' reason, the phone got stuck at the hellfire loading screen and won't boot.
The problem is, my down vol button broke quite some time ago, and i can't use the power+vol down in order to save my phone. any ideas?
Click to expand...
Click to collapse
If you're lucky then it boots up enough to load adb.
Attach the usb cable, boot, open cmd and try if you find a device with adb devices
If yes you can easily tell it to reboot to recovery with reboot recovery and flash a new ROM.
Edit: As Hellfire is an ICS ROM you might need to use my modded adb drivers: http://forum.xda-developers.com/showthread.php?t=1752074

From what i know smathflash needs VOL UP to be used.

tonyp said:
If you're lucky then it boots up enough to load adb.
Attach the usb cable, boot, open cmd and try if you find a device with adb devices
If yes you can easily tell it to reboot to recovery with reboot recovery and flash a new ROM.
Edit: As Hellfire is an ICS ROM you might need to use my modded adb drivers: http://forum.xda-developers.com/showthread.php?t=1752074
Click to expand...
Click to collapse
I'm sorry, but i'm not really familiar on how ADB works..
Can you help me out? I'm not sure what am i supposed to do to tell it to reboot to recovery.
P.S. Well, i tried booting up my phone today and it's now stuck at the second LG logo (the one with a blue hue).

Man, if you really can't use adb why are you modding your phone?
I will supply you with adb when I come from work.
Sent from LG 2X using Tapatalk 3 Beta
EDit: I am not sure than this is all needed files to run, but you should be able to do your things by runnig CMD line in folder with adb tools unpacked from this archieve.

[Q] Htc One BRICKED.

After only four day of having this phone i managed to brick it. I would really like to know if its fixable or if i have a really nice paper weight. Im stuck on a boot loop, I was half way through flashing a rom when it suddenly shut off. Now it will not boot up. I can load into the bootlader but when i try to go into recovery it just sends me to fastboot. When i restart the phone i can see the old recovery (TWRP)for just an instant but then the screen goes completely black. If i plug in to my pc, nothing happens my computer detects it but it says y device is damaged nd it cant identify it. PLEASE HELP Am i out of luck?
Ive looked around but i couldnt seem to find anyone with the same problem as me (Sprint Variant)

Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help

There's a Sprint One forum as well, so hopefully you found a ROM on there!
http://forum.xda-developers.com/forumdisplay.php?f=2215

jaythenut said:
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
Click to expand...
Click to collapse
I really hope so because on a college budget i cant afford another phone D:

Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.

wnp_79 said:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
Click to expand...
Click to collapse
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!

i suggest you contact with HTC customservices to repair this problem.

Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock

Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.

DynamicRam said:
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Click to expand...
Click to collapse
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.

Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
dont give up
Sent from my HTC One

Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
Edit: Just got done typing the stuff below and saw you can't connect to your device in fastboot? What do you mean by re-installed driver?
Don’t worry, as long as you can still get into hboot your phone is not completely bricked!
The fastboot commands I referred to need to be carried out on your laptop/pc when you phone is connected in fastboot.
Can I assume that as you have already unlocked bootloader and flashed a custom recovery you are already familiar with this and have your computer set up for fastboot commands?
(Apologies if you already know some of this, best not to skip parts out though!)
I’d start with downloading a fresh version of your chosen recovery, and place it in your fastboot directory ready. I’d also do the same with your ROM.
Like you have already done, boot into fastboot. Connect your phone to your pc, and the red text should change to ‘Fastboot USB’.
Then open up command prompt and get to your fastboot directory. (On Windows 7 you just find that folder in Explorer, hold shift and right-click, then choose ‘Open command window here’.)
To check your pc is talking to your phone, type ‘fastboot devices’. You should get a device serial number back if all is well.
Then type ‘fastboot erase cache’ and hit enter.
Then type ‘fastboot erase recovery’ and hit enter.
Then type ‘fastboot flash recovery [name of recovery].img’ and hit enter.
Then type ‘fastboot reboot recovery’ and hit enter.
Hope fully you should successfully boot into recovery now. Once in recovery, mount USB storage and copy over your fresh ROM. Choose to do a full wipe including cache and dalvik, then reflash your ROM.
Reboot.
Let me know how this goes.

cronus101 said:
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
Click to expand...
Click to collapse
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:

Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app

Muquita said:
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Click to expand...
Click to collapse
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html

Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck

wnp_79 said:
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Click to expand...
Click to collapse
(Win8 but the procces is identical.) All my drivers are up to date. Still no love.

On the dev forum is a thread that includes all the latest drivers (including an app to remove older drivers.)
Find that thread, download the drivers and bmp and driver removal tool. Remove drivers with tool, install the new drivers, reboot, connect phone and see if 'adb devices' finds anything.
Also make sure you're using the latest adb.
Sent from my HTC One using xda app-developers app

thneed said:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Click to expand...
Click to collapse
This actually sounds really similar to my situation.. Would you care to be a little more specific on the procedure? noob here.

Tabtoub said:
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
Click to expand...
Click to collapse
My pc will not recognize my phone. The drivers are up to date but when i plug it in it says something malfunctioned ?

Solution for Android Kit Kat OTA update boot loop problems

To anyone who has had the issue of installing the OTA Kit Kat update and ended up with an error, followed by bootloop "No Command" screen, here's the fix and how to save your data. I was unable to successfully get the image flashed using adb sideload, but I will mention it as others apparently have.
When attempting to install over the air update on Nexus 7 2012, Wifi edition, about 25% into the install I received an error screen. Upon restarting device, the Nexus would load the Google splash screen, followed by a "No Command" screen. To those that have encountered this and are worried about losing your data, follow these instructions. I am using Ubuntu so you will have to do a little research on downloading the tools for Windows and how to use them. I have a ton of computers to work on and don't have much time to type out a long guide, and I have never used either of these tools on a Windows machine.
Download the factory image for Kit Kat from here: https://dl.google.com/dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
Tools needed:
Drivers for your Nexus (Windows only)
Fastboot
ADB
Fastboot and adb are packed together in the Android SDK, or other sources have them. Using ubuntu, run "sudo apt-get install android-tools-fastboot" and "sudo apt-get install android-tools-adb" in your command line.
If you want to use adb sideload, check to make sure you device is recognized in "70-android.rules" or "51-android.rules" by running:
Code:
adb devices
If you get "?????????" then you better edit your android rules file by typing:
Code:
gksudo gedit /etc/udev/rules.d/70-android.rules
Note that your android file could use the number 51 or 99 also, so I would recommend performing this step 3 times with 70-android.rules, 51-android.rules, and 99-android.rules.
Add the following:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666", GROUP="adbusers" #regular/debug
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666", GROUP="adbusers" #fastboot
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666", GROUP="plugdev" #regular/debug
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666", GROUP="plugdev" #fastboot
Save this file and exit your editor. Now, extract your image you downloaded from Google. You should see a file named "image-nakasi-krt16s.zip." Copy this somewhere easily accessible, such as /home/<your username>/ANDROID.
Open command prompt and enter the following:
Code:
cd /home/<your username>/ANDROID
adb sideload image-nakasi-krt16s.zip
If all goes well, this should install and reboot. If not, you may get errors such as "E:signature verification failed" or something about unexpected files. I had about 4 different errors trying this, so continue reading to fix this using fastboot.
Extract all of the contents of the downloaded image file to the /ANDROID directory we created earlier.
Power off the device. Press and hold on to the Volume down and power key altogether until you see the bootloader screen. This screen is what we know as bootloader mode or fastboot mode. Connect the device to the PC via USB cable
Open your command prompt and head to the /ANDROID directory. In case you forgot:
Code:
cd /home/<your username>/ANDROID/
Next, run the following commands in order.
Code:
fastboot erase boot
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot erase system
Now we need to reflash the bootloader:
Code:
fastboot flash bootloader bootloader-grouper-4.23.img
Reboot the bootloader:
Code:
fastboot reboot-bootloader
Flash the 4.4 Factory Image, type:
Code:
fastboot update image-nakasi-krt16s.zip
Now sit and wait while your tablet is updated. It will restart and your apps will be optimized. Good luck!

I have the very same issue after the 4.4 OTA. When I tried to connect, my nexus is only getting listed under the fastboot devices (Drivers installed by the WUG toolkit/in device manager can be seen as Google Nexus 7 BootLoader Interface) and I have no adb connection (probably I had USB debugging deactivated. Is there anything I can do or do you think I'm screwed and have to erase everything?
Update: just executing the fastboot steps worked just fine (without any ADB sideload), many thanks for this solution

Thank you for your very usefoul post greg but how does one go about doing the same procedure without Linux ?

Redzo said:
Thank you for your very usefoul post greg but how does one go about doing the same procedure without Linux ?
Click to expand...
Click to collapse
I did it using windows: I've installed the android sdk for windows and used the wugfresh toolkit to update my nexus 7 drivers - then booted into fastboot mode and executed the fasboot... commands listed

Yeah, there is really no need for the adb, and I had no luck with it. I was thinking fastboot would wipe my user data, but I just didn't run any commands that would wipe my data and it seemed to work fine. On Windows, I would just download the SDK and then get your tablet connected and the fastboot commands are all the same. The problem I have is I can never get Windows to work right with and of my Android gadgets and I am not as good with the Windows command line. But if you have trouble connecting to Windows, just go to the Ubuntu site and throw the live version on a flash drive, run the sudo apt-get android-tools-fastboot command, and you should be good to go.

Redzo said:
Thank you for your very usefoul post greg but how does one go about doing the same procedure without Linux ?
Click to expand...
Click to collapse
If you are still having issues, pm me and I would walk you through it.

greg_gorrell said:
If you are still having issues, pm me and I would walk you through it.
Click to expand...
Click to collapse
Thank you very much greg for your kind offer but i have managed to solve the issue

A bundle of thanks to @greg_gorrell! Always making things easy for us
I have successfully updated my Nexus 7 (2012) from 4.3. Though I will have to root the device again
I am curious though. Why the OTA update always fails on our rooted devices? Its been going on since 4.2.2 I think while previously we used to update to OTA just fine even when we had out devices rooted (personally done that). Any possible explanation for this issue?

abobobilly said:
A bundle of thanks to @greg_gorrell! Always making things easy for us
I have successfully updated my Nexus 7 (2012) from 4.3. Though I will have to root the device again
I am curious though. Why the OTA update always fails on our rooted devices? Its been going on since 4.2.2 I think while previously we used to update to OTA just fine even when we had out devices rooted (personally done that). Any possible explanation for this issue?
Click to expand...
Click to collapse
You're welcome! But I have been looking into it and it seems that it isn't just rooted tablets that cause the update to fail. On another site, I believe Android Police, I noticed some had completely stock devices that failed.

This sux...
I had same thing happen on my nexus 10 doing ota from 4.4 to 4.4.2 on my stock rooted N10.

notfaded1 said:
I had same thing happen on my nexus 10 doing ota from 4.4 to 4.4.2 on my stock rooted N10.
Click to expand...
Click to collapse
I am not able to do anything as my Nexus is in bootloop, it is constantly rebooting so I have no access to anything. Cannot get into recovery mode at all. Any help would be nice.

Was that caused by the rom update? And did you let it die and then try to boot into recovery immediately after charging?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

greg_gorrell said:
Was that caused by the rom update? And did you let it die and then try to boot into recovery immediately after charging?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
After month keeping device disconnected from battery I recharged it and tried to get into recovery mode. It doesn't worked, still stuck in constant loop showing Google logo and ClockworkMod Recovery v6.0.4.3. I recorded video so you guys can see what exactly I mean.

PCFixYa said:
After month keeping device disconnected from battery I recharged it and tried to get into recovery mode. It doesn't worked, still stuck in constant loop showing Google logo and ClockworkMod Recovery v6.0.4.3. I recorded video so you guys can see what exactly I mean.
Click to expand...
Click to collapse
Just boot into Bootloader and reflash the the whole ROM. Start from there.

khaytsus said:
Just boot into Bootloader and reflash the the whole ROM. Start from there.
Click to expand...
Click to collapse
I cannot boot into anything! It is constant bootloop.

PCFixYa said:
I cannot boot into anything! It is constant bootloop.
Click to expand...
Click to collapse
Bootloop implies that it's trying to boot into the ROM, which means you're not trying to get into the Bootloader which is where you need to be.
Hold power until you see the Google logo, then press and hold Vol down. If it powers back off/reboots, let go of the Power button sooner but keep holding the volume button.

khaytsus said:
Bootloop implies that it's trying to boot into the ROM, which means you're not trying to get into the Bootloader which is where you need to be.
Hold power until you see the Google logo, then press and hold Vol down. If it powers back off/reboots, let go of the Power button sooner but keep holding the volume button.
Click to expand...
Click to collapse
It doesn't work, every action I tried ended up with this bootloop which you can see few posts above... Thanks for trying to help btw

System Recovery Access & Options

For what its worth-
I can boot into Android system recovery <3e> for Android 5.1.1 build # A1PV1.0.0B17 by powering off and pressing power and volume up at the same time then releasing when the Android appears. Pressing the volume key down instead takes you to Factory Test Mode. The following options are available in recovery:
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply update from cache.

Unfortunately there seems to be no way to get into the bootloader. Hitting "reboot to bootloader" just reboots the phone back to android. One of these days someone will crack this phone. Just hoping we get some people with some development experience on board with this phone.

There was a post that I saw that said that ZTE phones come with the bootloader already unlocked, but I haven't found a way to check it. Has anyone tried to see if the Factory Test is just their fancy way of saying that it's in bootloader mode?

For fastboot: If you have ADB you have fastboot, even if you don't know it yet. Make sure adb sees you device by running the following:
Code:
adb devices
Code:
adb reboot bootloader
Your device will have a RED light at the top, and your screen will be black. Make sure Windows Update can get drivers for you, and it'll install it.

http://forum.xda-developers.com/showpost.php?p=48319535&postcount=29

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

http://cellphonetipsandtrickss.blogspot.com/2013/10/the-super-secret-codes-fr-zte.html

Sebring5 said:
For fastboot: If you have ADB you have fastboot, even if you don't know it yet. Make sure adb sees you device by running the following:
Code:
adb devices
Code:
adb reboot bootloader
Your device will have a RED light at the top, and your screen will be black. Make sure Windows Update can get drivers for you, and it'll install it.
Click to expand...
Click to collapse
I've tried this and it simply reboots my Axon Pro (model A1P). Where are you getting the drivers from? (Besides windows update and Install mode when you connect the Axon to your PC.)

I use a Mac. No drivers needed.

Sebring5 said:
I use a Mac. No drivers needed.
Click to expand...
Click to collapse
That..doesn't exactly help..

Archfeind2 said:
That..doesn't exactly help..
Click to expand...
Click to collapse
http://forum.xda-developers.com/zte-axon/help/zte-axon-drivers-adb-t3173020

Sebring5 said:
http://forum.xda-developers.com/zte-axon/help/zte-axon-drivers-adb-t3173020
Click to expand...
Click to collapse
Already checked that thread out and the ZTE or the google drivers doesn't allow me to get to fastboot. After putting in "adb reboot bootloader" it just reboots the phone.
I also see that whenever you install the drivers from the phone, it installs only adb with a bunch of other ZTE programs for adb with no fastboot in sight.

Archfeind2 said:
Already checked that thread out and the ZTE or the google drivers doesn't allow me to get to fastboot. After putting in "adb reboot bootloader" it just reboots the phone.
I also see that whenever you install the drivers from the phone, it installs only adb with a bunch of other ZTE programs for adb with no fastboot in sight.
Click to expand...
Click to collapse
Try this: http://www.downloads.techdiscussion.in/smartphones/zte-axon-pro-pc-suite-and-usb-driver/

Okay cool. I'll check it out in a couple of minutes.
Edit:
It didn't work it was the same as the axon installer unfortunately. Maybe I'll have to virtual machine either mac or Linux, again >.<
I really want this phone's bootloader unlocked xD