I bought my sequent about a month ago and so excited to find out im able to root and add custom roms and such i got right to work. i tried a few different things trying to get y drivers right and i think it was a success see as i was able to root and use su and explore y phones internal folders. only problem i having now is that when i try to hold the down and power i get an android /red led and it will not enter into ftm mode. I'm not sure what to do now. i tried the update tool but it cant update without being in ft mode. please help! i don't wanna have to go back to bestbuy and pay the insurance again if i can get this back up and headed toward custom roms
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root What to do i you are stuck with an android and red led/no ftm mode
- Thread starter WesTCB
- Start date
-
- Tags
- zte warp sequent
D
Deleted User
Guest
Volume up and power?
at one point it would start up normally and in the bottom left id see safemode but now i get same thing weather i use up or down + power. tried useing a few one click programs like easy adb but it fails to load stock.img and leaves me with the android screen again
peasarecool
Well-Known Member
to get into ftm when this happened to me, i had to restore original recovery first then ftm and update tool worked.
if you have access to adb use fastboot and flash the stock recovery. Im going to make this as simple as I can.
1. Put recovery.img in same folder as adb.
2. adb reboot bootloader
3. fastboot flash recovery recovery.img
4. fastboot reboot, you should be able to boot into stock recovery now.
5. wipe data and phone will be stock but will be fixed.
6. follow instructions thoroughly on getting and root and all that.
http://d-h.st/Eot Stock recovery
1. Put recovery.img in same folder as adb.
2. adb reboot bootloader
3. fastboot flash recovery recovery.img
4. fastboot reboot, you should be able to boot into stock recovery now.
5. wipe data and phone will be stock but will be fixed.
6. follow instructions thoroughly on getting and root and all that.
http://d-h.st/Eot Stock recovery
I had an issue like this on the warp1, sadly I wasn't able to recover from it and had to claim the insurance. the update tool will not read the phone if you dont have ftm mode. It is advised that no one install CWM until it is fully functional. Especially if you are trying to modify something on your device. At least that way you have a fail safe in case something happens (FTM Mode).
Is there no way to add the files for recovery or ftm mode directly to the device using root explorer or something? i do have root and access to all the folders within the device if someone could rar the needed files it would be worth my time to try it out. i really dont wanna pay the insurance if i can find a way to fix it.
kingjay2012
Android Enthusiast
hey shinru, the ftm mode might not work but the cwm recovery backup does, almost a fatal attempt to modify my phone that i discovered this... but it works.
kingjay2012
Android Enthusiast
doesnt work, it doesnt wipe anything or clear the data, because the stock recovery you posted is the unstable CWM 4.0.1.5. we need the actual stock recovery that came with the phone in order for it to work.
kingjay2012
Android Enthusiast
its in the wrong system file on the computer it has to be where ever adb is located on your computer which should be in your c:\ drive.
What OS are you on? Windows 7 should install the drivers automatically.
junkie2100
Android Expert
yea umm, i can take this one shinru
if you boot into bootloader mode and type adb devices it wont show you anything
adb only works with the phone fully on and usb debugging enabled or with the cwm running
try
fastboot devices
that is the only way to see it in bootloader mode, and if that shows nothing then chances are your computer just doesnt have usb 2.0 which as it turns out is a requirement, i had to use someone elses computer to flash mine because i only have usb 1.1
if you boot into bootloader mode and type adb devices it wont show you anything
adb only works with the phone fully on and usb debugging enabled or with the cwm running
try
fastboot devices
that is the only way to see it in bootloader mode, and if that shows nothing then chances are your computer just doesnt have usb 2.0 which as it turns out is a requirement, i had to use someone elses computer to flash mine because i only have usb 1.1
junkie2100
Android Expert
if you want to try and manually put the drivers in be my guest, but if they dont install automatically chances are your computer is just incapable of supporting fastboot mode
there is an issue with the lower power output of the 1.x specification that screws things up
C:\Program Files\ZTE 3GPhone USB Driver\Drivers\32bit
C:\Program Files(x86)\ZTE 3GPhone USB Driver\Drivers\64bit
those should be your driver locations though for manual installation and its the one that says kernel debug driver or something along those lines, its the only one that has the word kernel in it i know that much for a fact.
if you put that driver in and it gives you some crap about device cant be started well youre gonna have to use a newer computer just like me
there is an issue with the lower power output of the 1.x specification that screws things up
C:\Program Files\ZTE 3GPhone USB Driver\Drivers\32bit
C:\Program Files(x86)\ZTE 3GPhone USB Driver\Drivers\64bit
those should be your driver locations though for manual installation and its the one that says kernel debug driver or something along those lines, its the only one that has the word kernel in it i know that much for a fact.
if you put that driver in and it gives you some crap about device cant be started well youre gonna have to use a newer computer just like me