• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] Warp locked up and now continous restarts

ok, flashed back to the stock recovery to test some things... basically found out that if you didn't have usb debugging checked last time your phone worked, you have no way to use adb that I know of, which means you can't flash cwm recovery.

So that's the question of the day, did you have usb debugging checked (settings/applicaions/development/usb debugging)

if you did, there may be hope for flashing cwm, otherwise if the zte warp update tool doesn't work you are probably looking at needing to get a new phone. (zte has a one year warranty so this would be a real legit reason to call them up and claim it).

if you did have usb debugging checked, you can try some commands from the command prompt from the ultimate warp drive folder:

shut down the phone and plug it into your computer.
Open command prompt in the ultimate warp drive folder
make sure you see a file called fastboot.exe in that folder
from the command prompt type adb reboot bootloader, don't hit enter yet
power on the phone and as soon as you see the boost mobile animation hit enter
if it says waiting for devices, try typing it again and hit enter, try this a few times while it bootloops

If by some miracle the boot stops and it goes to the green android logo type fastboot devices, you should see something like ? fastboot

if you see that, we can flash the cwm recovery, let me know if you get that far...

if you type fastboot devices and enter and nothing is listed you are screwed as far as trying to install cwm.

Also, if it doesn't go back to the green android logo when you do the reboot bootloader command you didn't have usb debugging selected and we can't do adb/fastboot.
 
SelfElevated2 said:
No but you can use android commander. Google android commander and download it to your computer. You could actually install a new rom threw it
Click to expand...

same dilemma I am afraid, android commander requires root access as well as usb debugging enabled, neither of which you have as far as I know.
 
OK I see fastboot in the ultimate drive folder. should there be a command prompt in that folder or should i just open up a regular command prompt?

I have tried typing adb reboot bootloader at a regular command prompt and hit enter at different times of boot up and I am still getting no device found.

I also downloaded android commander and cant seem to get it to recognize the phone either.

Thanks again for all the help.



MrBobo said:
ok, flashed back to the stock recovery to test some things... basically found out that if you didn't have usb debugging checked last time your phone worked, you have no way to use adb that I know of, which means you can't flash cwm recovery.

So that's the question of the day, did you have usb debugging checked (settings/applicaions/development/usb debugging)

if you did, there may be hope for flashing cwm, otherwise if the zte warp update tool doesn't work you are probably looking at needing to get a new phone. (zte has a one year warranty so this would be a real legit reason to call them up and claim it).

if you did have usb debugging checked, you can try some commands from the command prompt from the ultimate warp drive folder:

shut down the phone and plug it into your computer.
Open command prompt in the ultimate warp drive folder
make sure you see a file called fastboot.exe in that folder
from the command prompt type adb reboot bootloader, don't hit enter yet
power on the phone and as soon as you see the boost mobile animation hit enter
if it says waiting for devices, try typing it again and hit enter, try this a few times while it bootloops

If by some miracle the boot stops and it goes to the green android logo type fastboot devices, you should see something like ? fastboot

if you see that, we can flash the cwm recovery, let me know if you get that far...

if you type fastboot devices and enter and nothing is listed you are screwed as far as trying to install cwm.

Also, if it doesn't go back to the green android logo when you do the reboot bootloader command you didn't have usb debugging selected and we can't do adb/fastboot.
Click to expand...
 
if you get no device found while it's bootlooping you most likely didn't have usb debugging enabled, everything relies on that as far as rooting/cwm are concerned as well as the program, if it's not on, we can not talk to the phone from usb without advanced software and commands that probably only zte would know about...

it's probably not impossible but googling and looking around the forums I don't think we have a tool to solve this.

Your only hope is the zte update tool and ftm mode.

I am assuming you were using the zte update tool to try to get back to stock when you say it only got to 7%, right?

Did you make sure it's not a dead battery causing it to die at that point? You can check the battery with a voltometer, it should be 3.7 volts dc.

Kinda running out of ideas if it's not a dead battery causing it to not make it through the update.
 
Or internal memory error. If it hit a certain block of memory that was damaged it would cause the same symptoms. Only speaking from computer repair experience. Never had that issue on phone, just wanted to make that clear ;)
 
Pretty sure it's not a battery issue. It will sit here for hours with the boost mobile logo resetting itself. Also I have tried the FTM mode without the battery installed and it still gets to the same 7% and reboots.





MrBobo said:
if you get no device found while it's bootlooping you most likely didn't have usb debugging enabled, everything relies on that as far as rooting/cwm are concerned as well as the program, if it's not on, we can not talk to the phone from usb without advanced software and commands that probably only zte would know about...

it's probably not impossible but googling and looking around the forums I don't think we have a tool to solve this.

Your only hope is the zte update tool and ftm mode.

I am assuming you were using the zte update tool to try to get back to stock when you say it only got to 7%, right?

Did you make sure it's not a dead battery causing it to die at that point? You can check the battery with a voltometer, it should be 3.7 volts dc.

Kinda running out of ideas if it's not a dead battery causing it to not make it through the update.
Click to expand...
 
I agree with down then, it does sound like a memory error in the phone's hardware, sorry to hear that though for your sake... any chance you can warranty it out, sounds like a lemon to me.
 
You must log in or register to reply here.
Back
Top Bottom