Hello Everyone, this is one of my first posts so go easy on me.
I used the method in this thread to flash JB onto my TF201, and now i cannot boot to recovery (get the android on his back/side with the red exclamation) and fastboot shows up as a device in device manager in windows, but when i run the "fastboot devices" command with the up to date SDK nothing is listed. ADB works, but for osme reason superuser was installed as a system process and will not uninstall, and will not issue any sort of root command to anything, including ADB. any ideas?
Related
Hi xda,
I was unlocking and installing AOKP ROM this week and I've hit a problem that I can't get past. I apologise that this seems like so many other questions already posted, but I haven't found a solution in the threads I've read. I also apologise that I write verbose explanations; I just want to be as clear as possible.
My new TF201 was on ASUS firmware .21 so I used bpear's viperMod/Wolf849-based tool to downgrade to ASUS firmware WW .15.
I then used bpear's tool to root it after downgrading, and then unlocked the bootloader using ASUS' tool. Before anyone asks why I bothered to root if I was going to unlock, I didn't entirely understand what was required to flash a custom ROM on the TP; the process was much simpler on my HTC Desire.
After unlocking the TF201 I used bpear's tool to flash CWM. I downloaded AOKP (aokp_tf201_build-38.zip) and put it on the internal space - I don't have an SD card in it. I rebooted the device into CWM and wiped Dalvik cache, reset factory settings, then went to "Install from zip" and selected the AOKP zip. It ended successfully (i.e: no errors, all messages on the screen appeared normal), so I reboot the device.
And after rebooting it hangs at the splashscreen. I tried to reflash AOKP but there was no change, so I rebooted into the bootloader menu and, without thinking about the consequences, selected to wipe the device. Now I can't reflash AOKP because I wiped the device, and I can't restore a nandroid backup because I didn't take one before flashing AOKP.
I rebooted to the bootloader and selected Fastboot mode while the device was connected to my computer (Windows 7 x64). In Windows, I can see in the taskbar that a device is recognised as "fastboot", and drivers are installed successfully, so I type in the command 'fastboot devices' which simply returns a new line. I reboot into CWM and try to use adb to connect to the device, but there is no device detected in Windows and the command 'adb devices' indicates there is nothing found.
At this point I'm unsure what step to take next. Any tips would be useful.
The command "adb devices" will not show your device unless it's booted, so what you're seeing is normal. You may want to try pushing a ROM to your TFP via adb fastboot.
cam30era said:
The command "adb devices" will not show your device unless it's booted, so what you're seeing is normal. You may want to try pushing a ROM to your TFP via adb fastboot.
Click to expand...
Click to collapse
there is no 'adb fastboot' command
@OP, you have to reinstall/point windows again (while in recovery) to the drivers manually. it's the same drivers, yes.
Hi xda,
I got everything sorted a couple of days after this thread was started.
I followed the same procedure described in the OP, with two changes:
1. I swapped AOKP for Virtuous Prime.
2. I installed the Universal Naked Drivers .
My TF201 is functioning very well on Virtuous Prime ROM. I am pleasantly surprised with the battery life but sufficiently annoyed with the wireless that I set up an AP at the other end of the apartment just for the TF201.
cam30era said:
The command "adb devices" will not show your device unless it's booted, so what you're seeing is normal. You may want to try pushing a ROM to your TFP via adb fastboot.
Click to expand...
Click to collapse
While I was searching for a solution, I read on several sites that it was possible to push files to the tablet while in recovery mode/CWM. An example is this thread. I have to wonder: am I misunderstanding the steps being provided, or is the information being provided is incorrect or incomplete?
With regards to fastboot, I did mention in the OP that fastboot wasn't functional.
Cheers.
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
Hi all, trying to install CM on Nextbit Robin and I'm having trouble getting the TWRP recovery img flashed. I have working Fastboot & ADB tools installed. Robin driver is installed on PC. Device IS responding to Fastboot and ADB commands. Have unlocked Bootloader and in Fastboot mode now trying to flash recovery (TWRP) img. Have latest TWRP file etc but CMD screen on PC returns a "cannot load file" message. TWRP file located in same directory as Fastboot etc. (I'm working from Windows 10 environment.) Debugging enabled etc. on device. I've flashed CM many times on other Android devices - haven't encountered this issue before. Only issue I've noticed is that the command ADB Devices returns "List of devices" but nothing is listed - HOWEVER device IS responding to ADB commands and Fastboot commands. Thanks in advance for any help you can provide!
I have the exact same problem,
Hello everyone!
I am currently having issues with my Galaxy S4. I am attempting to install twrp onto it although I am having issues. I have not made any modifications to it, it is running the stock rom and it is not rooted.
I am following this guide: https://www.xda-developers.com/how-to-install-twrp/
I installed adb and fastboot using: https://forum.xda-developers.com/showthread.php?p=48915118#post48915118
I have not gotten any errors.
I type into command prompt:
adb devices
I then get my devices id.
I then type adb reboot bootloader
Once it finishes going into bootloader.
I type adb devices and then get nothing.
I also tried typing fastboot devices and also got nothing.
When I use flashboot flash recovery it gives: <waiting for device>
Could anyone help? I am a newbie at this.
Thank you!
Hi,
I am new in this topic and not a great geek ans please excuse mi for my aprroximative english ! but i am trying to convert an old cube tablet to a domotic tablet. So i have to flash the old rom to a newer like lineageos for example.
So the tablet is an U30GT C4H with android 4.2.2 and the original rom.
I connect the device to my Mac Os and with adb tools (from plateform tools find here) and terminal i wrote adb devices (tablet on) i see the device. OK
When i command fastboot devices, nothing, no line
When i command adb reboot-bootloader, the tablet take off and the screen keep black. With the terminal fastboot devices, no response, with adb devices command > List of devices attached but no more, no device.
With this tablet it is possible to start in recovery mode with power + audio down but with this option i have the android logo and no command. If i take power on no change.
If with adb command and tablet on, i write adb reboot recovery, the tablet restart and the screen see logo android and no command.
I know this kind of topic do not interese a lot of people but i would like use this cube for my house to command domotic (music, heaters etc..). More, i think it's a shame not to recycle this type of device for the planet !!!
Thanx
Fastboot only works if in your tablet's Android's Settings -> Developer options the option OEM unlock got enabled and tablet got restarted afterwards.
i don't see any option OEM in the menu developer
I found that the solution is use slideload protocol. I reseted the tablet and now i get recovery mode. Then i can connect the tablet to my Mac and use terminal with slideload lines. OK
But each time the process failed with rom i found on the net...
Is there an universal rom !!!
Any idea ?
You don't have to boot the device into Recovery mode:
Code:
adb devices
adb reboot sideload
adb sideload <PROPERLY-SiIGNED-FILE.ZIP>
adb reboot
BTW: adb sideload is meant to re-flash Stock ROMs only.
jwoegerbauer said:
You don't have to boot the device into Recovery mode:
Code:
adb devices
adb reboot sideload
adb sideload <PROPERLY-SiIGNED-FILE.ZIP>
adb reboot
BTW: adb sideload is meant to re-flash Stock ROMs only.
Click to expand...
Click to collapse
maybe the issue is the rom i doawnloaded ?
it is kasty-cube_u30gt_h-411-111-rooted4_4gb.zip
or
kasty-cube_u30gtc4-441-20131212-rooted4.zip
both failed.
Perhaps i have to unlock the bootloader as you said but i don't know
I'm pretty sure the 2 mentioned ROMs are a Custom ROM. Hence you can't use adb sideload method to flash them. To install a Custom ROM it's required that a Custom Recovery already got installed on device's Android.
I don't find any way to instal a recovery. I had arctools.zip but the app failed to acess to the SD disk or internal storage...