So I'm in the process of trying to Root my ZTE Smarttab 10 on firmware v03b.
Ive been following instructions on the following pages:
http://forum.xda-developers.com/showthread.php?t=1629630
http://forum.xda-developers.com/showthread.php?t=1473555
The instructions are spread out across those threads and my problem starts kind of early in the process.
My goal is to use ADB to boot in to the Bootloader and then use a recovery rom to use TWRP to install a rom.
What i have done:
I have installed the ZTE Drivers
I have installed the SDK tools and updated it.
Now when the tablet is running normally I can see it in ADB and is able to run the command.
ADB Reboot Bootloader
This reboots the devices to a black screen (I assume this is the bootloader) and windows recognizes that a device is there.
The problem is that when I try to see this from ADB i cannot see the device when running ADB Devices.
This makes the next step impossible as I need to use ADB to boot a recovery rom.
So I would have posted in the development treads listed above but as I dont have 10 posts (this being my first post) I cannot post in the threads above.
I'm confident that this is a driver problem and I have uninstalled and re-installed all the drivers related to this including SDK.
But no luck yet.
Where other people say they have succeeded is when in the device manager they have ADB interface and ZTE Handset ADB interface listed.
This is the state where I'm at but I still cannot see the device in ADB.
Anyone have any insight on this kind of problem and can offer any help for a solution or direction to get to the solution.
Thank you for your help and attention!
//Nagarutu
Vodafone (ZTE) SmartTab10 3.2 HoneyComb
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
matt4321 said:
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
Click to expand...
Click to collapse
Thank you for the help ! it cleared things up for me.
Now the trouble's continue.
With the firmware im on (v03b) you cannot use the fastboot flash method but only fastboot.
And they way it is supposed to be done is that you run
fastboot boot recovery.img (recovery being a twrp recovery for my device)
When its booted to TWRP i should be able to see it in ADB to be able to run the following commands to it:
--> adb remount
--> adb shell
--> ln -s /system/xbin/su /system/bin/su
However I cannot get it to show in ADB (or fastboot) when its booted in to TWRP.
Any ideas?
I managed to solve the last bit to.
Now it was actually a driver problem, so i just updated the driver in device manager and located the ADB driver from ZTE and it worked to boot in to TWRP and then to flash the device.
Now I have CM10 installed and is smiling!
Took me 4 days but damn it its done!
Thanks for the help!
Glad you've figured it out
1a
2a
3a
4a
5a
Good Afternoon Everyone !
I'm new to the XDA , but not a Newbie in the delevoping section.
Because of a hardware problem when i changed the display of my phone
my volume keys aren't working anymore.
Today I flashed the Beanstalk ROM from the user TH3Bill, but unusally it won't start.
So i got the problem right now that it wont boot and I'm stuck with the Motorola Logo,
because I can' get into recovery. Is there any option to get into recovery without the volume
buttons or fastboot ?
PS : sry for the bad english
If you can access adb you can type "adb reboot recovery"
jorno88 said:
If you can access adb you can type "adb reboot recovery"
Click to expand...
Click to collapse
tried it, but it just says that now device was found , but the device is listet in the device manager as adb device interface.
that seems correct, only way to go into recovery without volume is adb or fastboot or ofcourse rebooting into recovery...(as far is i know)
do you know how to use adb?
can you see your device listed when you type adb devices?
jorno88 said:
that seems correct, only way to go into recovery without volume is adb or fastboot or ofcourse rebooting into recovery...(as far is i know)
do you know how to use adb?
can you see your device listed when you type adb devices?
Click to expand...
Click to collapse
Not really, my firstime , but i used fastboot before . but for fastboot you have to go into the fastboot mode, and without wokring volume keys that isnt possible.
No when i type in adb devices, there is no device listed at all , just the line " List of all ADB devices"
First you have to activate android debugging in settings for adb to show ur device.
Secondly, even if u boot into recovery, u cannot use recovery without volume buttons unless you flash a touch recovery, for which I think u need to boot into fastboot which again needs volume buttons...
any other solution anyone?
Sent from my cm_tenderloin using xda app-developers app
sa.guly10 said:
First you have to activate android debugging in settings for adb to show ur device.
Secondly, even if u boot into recovery, u cannot use recovery without volume buttons unless you flash a touch recovery, for which I think u need to boot into fastboot which again needs volume buttons...
any other solution anyone?
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
I cant activate anything, i flashed a new Rom and then I got into a Boot Loop, and yes i have a touch recovery
Edit: I found some threads using adb in a Boot loop, is it possible that i have the wrong drivers ? i used two different mehtods but i can't update the adb interface driver
look
Method 1 :hxxp://atrix4ghacks.com/atrix-4g-hacks/how-to-install-atrix-4g-drivers/ this is where i got stuck
I also found a second with a package to extract which was accesable from the cmd, adb started but the phone wasn't rechable
Edit Edit: It worked with the officila motorola drivers, and the normal adb-tools , thx for your support
Hello all
I have installed the paranoid android 3+ rom but now I cannot access TWRP or the bootloader screen. Android boots normally and the tablet is perfectly functional. When the tablet is off, there is no way to get to TWRP using the keys (power on with Vol- pressed etc. I have used all possible combinations). Also, there is no option to boot into recovery mode from the menu in "Backup & reset". Also, when I try to boot into recovery through a terminal emulator it again boots into andoid normally as if I just did a normal reboot. The "reboot recovery" command issued from the terminal emulator does not boot into TWRP. Trying to boot into recovery mode from within Phoenix Suite again boots the machine normally rather than in recovery mode. It's driving me nuts. Could it be a corrupt/locked bootloader? Is it something else? It seems to me that the only possible path for the bootloader is to load Android.
Is there any way to blind flash the bootloader again? It seems that this is the culprit since I can copy TWRP to nandg through the terminal emulator ("cat /extsd/recovery.img > /dev/block/nandg; sync; sync ;sync" but then again rebooting goes into android rather than recovery mode. Could there be a similar solution like "cat /extsd/boot.img > /dev/block/nanda" for example?).
The tablet connects normally through USB to my PC and adb sees it properly.
Any ideas?
Thanks in advance
Nobody?
Try it via adb.
Command: adb reboot bootloader
It works for me.
Sent from my PC36100
merden765 said:
Try it via adb.
Command: adb reboot bootloader
It works for me.
Sent from my PC36100
Click to expand...
Click to collapse
Whatever I tried it does not boot into the bootloader, be it adb, Phoenix suite, or the terminal emulator. Is there any way to write the original booloader raw to the respective nand partition? And where can I get the original bootloader?
tzoykas said:
Whatever I tried it does not boot into the bootloader, be it adb, Phoenix suite, or the terminal emulator. Is there any way to write the original booloader raw to the respective nand partition? And where can I get the original bootloader?
Click to expand...
Click to collapse
I have same your problem and now i use goomanager this app can bring you to recovery mode or install in to your tablet.
So recently, I downgraded to 13.3.1.0, and installed Safestrap (not the one for later versions). However, after restarting and adding a ROM slot, it wouldn't let me do anything with stock.
I restored stock, but still nothing.
The odd thing is, whenever I press the power button, it will still make noise.
I can access fastboot, Safestrap, and the default recovery.
What do I do?
Bump, need help ASAP
Alex311360 said:
So recently, I downgraded to 13.3.1.0, and installed Safestrap (not the one for later versions). However, after restarting and adding a ROM slot, it wouldn't let me do anything with stock.
I restored stock, but still nothing.
The odd thing is, whenever I press the power button, it will still make noise.
I can access fastboot, Safestrap, and the default recovery.
What do I do?
Click to expand...
Click to collapse
If you can enter safestrap recovery, check if you can establish adb access:
so enter safestrap and connect kindle to your pc or laptop. Then start cmd window or terminal if you using linux, and try:
adb devices
it should return:
list of devices attached
xxxxxxxxx recovery
if you can achieve that your kindle in safestrap recovery is recognized by win/linux, you can try this:
1. Download this 13.3.1.0 (Kindle HDX 7") update - pure amazon FireOS so OTA updates enabled - do not connect to wifi/register your kindle if you want root and use of custom recovery after flashing this
A. Now, since I am not expert for adb installing pushing repairing etc., read this thread [HOWTO] Unbrick your device
B. If that for whatever reason wont work, you can try sideload update-kindle-13.3.1.0_user_310079820.bin (rename .bin to .zip before sideloading) through safestrap recovery, but because Safestrap is only TWRP "based", I cant guarantee that this will work either (it should, but this is one way ticket, your working safestrap recovery will be destroyed in the process of update and if things dont go as they should, your kindle is bricked for good):
0. connect kindle to pc/laptop
1. enter Safestrap, tap Advanced -> ADB Sideload -> Swipe slider to start Sideload
2. on pc/laptop open cmd/terminal, type adb devices, you should see:
List of devices attached
XXXXXXXXXXXXXXXX sideload
3. type adb sideload update-kindle-13.3.1.0_user_310079820.zip
4. You will see a progress bar in the command prompt indicating that the Zip file is being copied to the device. Once the file is transferred, the Zip is automatically installed on your device.
OK fingers crossed, I hope something will work, but things can go wrong, so it is up to you if you try this or not ...
On a scale of 1 to worse, what happens if ADB sideload refuses to work? It just freezes at starting and does nothing afterwards, and I have to cancel.
Alex311360 said:
On a scale of 1 to worse, what happens if ADB sideload refuses to work? It just freezes at starting and does nothing afterwards, and I have to cancel.
Click to expand...
Click to collapse
You can also try to unlock your bootloader (since you have compatible FW) and proceed to flash cuber signed recovery (TWRP 2.8.5.0) through fastboot and then from TWRP you can do necessary steps to recover your kindle quite easily - if you are familiar with TWRP flashing...
Regarding sideloading I honestly dont know how it will react - never try it - it was developed exactly for quick system recovery, but you must be flashing 100% working rom ...
Personaly I would go for bootloader unlock and then flash TWRP 2.8.5.0 from which sideloading feature (If you want use that) must working... :good:
Do you require a factory fastboot cable for that?
Alex311360 said:
Do you require a factory fastboot cable for that?
Click to expand...
Click to collapse
No, standart USB cable is enough.
Can you give me a link on how to do this? I know I'm sounding very noobish, but I'm a tad new to this.
Alex311360 said:
Can you give me a link on how to do this? I know I'm sounding very noobish, but I'm a tad new to this.
Click to expand...
Click to collapse
Sure, here is original post from dpeddi.
... and here is how to for windows ... :good:
Hey, sorry it's taken me so long to reply. Was busy with school.
For some reason it won't connect to the device in fastboot, it just says "waiting for device", even the Kindle says "Ready." and does nothing.
What do I do?
Alex311360 said:
Hey, sorry it's taken me so long to reply. Was busy with school.
For some reason it won't connect to the device in fastboot, it just says "waiting for device", even the Kindle says "Ready." and does nothing.
What do I do?
Click to expand...
Click to collapse
If your OS is Windows 7, you can try install these drivers and then try again.
jeryll said:
If your OS is Windows 7, you can try install these drivers and then try again.
Click to expand...
Click to collapse
Still no dice. Doing fastboot devices or adb devices brings up nothing.
Please note I have done the following things:
- did a kindle fire system restore with safestrap restore still installed
- adb sideload doesn't work in safestrap
- fastboot drivers used installed does nothing
Still stuck.
Alex311360 said:
Still no dice. Doing fastboot devices or adb devices brings up nothing.
Please note I have done the following things:
- did a kindle fire system restore with safestrap restore still installed
- adb sideload doesn't work in safestrap
- fastboot drivers used installed does nothing
Still stuck.
Click to expand...
Click to collapse
On which FW you were before downgrading to 13.3.1.0?
Weird thing with windows and these drivers is it sometimes command fastboot -i 0x1949 devices does nothing, while actually direct commands like
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 getvar version
fastboot -i 0x1949 getvar kernel
works as expected...
Anyway to restore system on your kindle you need working connection between kindle and PC/laptop, so you can use adb commands to restore your system, or after bootloader unlock, you can use fastboot commands to flash required/missing components. I have tested while in safestrap kindle is recognizable by adb devices, if you can achieve that, you can continue with how to unbrick thread I posted before.
You can also learn how to install/use Linux, where adb and fastboot device recognition/commands works 100%...
I must leave for work now ...
So, some kind of miracle happened, and I found the source of the problem.
Upon trying to update to 13.3.2.4, it reboots the phone instead of installing it. I try booting into Safestrap, and it does Open Recovery Script, causing it to boot to a black screen upon booting to the actual thing.
I don't know how to fix Open Recovery Script doing that, but all I had to do to get it back to normal was reflash the 13.3.1.0 amazon OS onto stock.
hi. I have prime and it is stuck into twrp screen with just teamwin screen keep on flashing. nothing happens and it doesn't boot into recovery(twrp) also. tried to boot into bootloader by holding power button and volume down but nothing happens. then tried adb. used abd reboot bootloader and also adb fastboot recovery. but nothing happens, only shown "waiting for any device". thought adb not working but when I type adb devices.....it shows device serial number and recovery written next to it. I think adb works but I am not able to boot into recovery or bootloader....
earlier I was using cayanogen rom and twrp as recovery... tried to falsh another rom and from that day had this problem. if anyone knows what should do or what's the problem.. I be very thankful... please if you have any idea tell me what to do??
fastboot devices ?