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...
Related
hi everyone,
I'm coming from this thread http://forum.xda-developers.com/showthread.php?t=1834761
I have been stuck for more than one week now and i didn't find any solution.
My problem is that I'm currently stock in a clockworkmod recovery boot loop on my Asus Transformer Prime without adb/fastboot connection:
1 - I had install CM9 stable on my Transformer Prime, after a wide data and then send throw "adb push" the CM9.zip,
2 - I reboot by CM9 in recovery mod to install Gapps,
3 - I install the Gapps zip,
4 - I ask to clockworkmod to reboot,
5 - Since then I'm in a clockworkmod recovery boot loop without adb/fastboot connection (witch used to be working),
If kown how can I get adb/fastboot connection back to be able to find my device with the adb command " adb devices " and then be able to send this command => " dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 "
Thank you for your understanding,
Kind regards,
Adb and fastboot are two different things... Fastboot is obtained buring booting process with vol down pressed, then not selecting recovery with volume up. So you should have fastboot access.
In this case I would suggest to fastboot flash TWRP (see on their website for instructions) it will perhaps fix things or at least give you adb access.
If you use cwm take the old 5.8.2.0 modded for not looping with reboot to recovery feature, or stay with twrp.
I would look at the following thread for unbricking the TF201:
http://forum.xda-developers.com/showthread.php?t=1514088
Sounds like you might fall into Option 1a.
I was having your same issue but it was because I rebooted into recovery from the reboot option on the CM10 rom. In any event, I couldn't get adb to work or recognize my device no matter what. I then decided to use my macbook pro. I can tell you that using adb on a mac is much easier as you don't have to download the drivers or sdk, just the platform tools. Here's a link: http://forum.xda-developers.com/showthread.php?t=1387527. I know this may not help if you or someone you know doesn't have a mac, but it saved me.
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
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Tommyboy77 said:
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Click to expand...
Click to collapse
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
es0tericcha0s said:
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
Click to expand...
Click to collapse
adb devces does not work in clockwork mod either.....what is the easiest way to get this custom rom sent to my internal sd card if the phone wont boot up and os is wiped off the phone? it is an htc one...
adb should work in CWM... You might have to manually load the driver. Even if every driver works when the phone is booted and all, Windows can still have issues finding the right one in recovery. Check in your device manager. If that doesn't work, then you'll have to see if your recovery supports USB OTG and see if you can load like that. If none of that works, you'll have to reload the OS via RUU and start over with root/recovery/etc.
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
C13v3r0n3 said:
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Neither of those things are options for the OP. He can't boot, so he can't mount USB (mounting USB in recovery hasn't worked for most phones since JB where most phones don't support USB mount - only MTP) and he can't sideload because he hasn't been able to get ADB working.
His options now are:
Find out why the adb driver isn't loading so he can just adb commands to push the file or sideload
USB OTG
Return to stock via RUU
I'm trying to root a pixel (sailfish). I'm able to find the device in adb, but when I go into bootloader, the device isn't there. I'm mostly trying things on my Mac, which I used to successfully root a Nexus 7, but I also had the same issue on a Raspberry Pi. What's more is that I have a Verizon Pixel, which is detected in bootloader (but I can't root it since it's Verizon), and the problematic Pixel in bootloader isn't even registering as a connected USB device when I use the command, "system_profiler SPUSBDataType". Anyone have any advice?
@macduffk
Try
Code:
adb reboot bootloader
fastboot devices
jwoegerbauer said:
@macduffk
Try
Code:
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
I’ve tried that. It doesn’t show anything.
I have spent months trying to figure out how to get TWRP flashed on my Pixel Phones (I have 2 of them). I have searched & read many links on this forum and can't find any firm details/directions on how to get TWRP on a pixel. From https://android.gadgethacks.com/how-to/install-twrp-custom-recovery-your-pixel-pixel-xl-0175163/ it appears I should of installed TWRP on the factory image first, but I went to Lineage a couple years ago on Android 9 & this was not an option back then.
Both phones have the two latest version of Lineage OS, Both Devices are UNLOCKED, Both have Developer Options Enabled, and on my Windows PC I have the latest version of SDK tools & drivers installed.
Plugging into the PC is done with a a tested/good USB cable plugged into a USB 2 Port. Here is what I am seeing with LinageOS running:
adb devices shows List of Devices Attached
FA77LO302202 device
After executing - adb reboot bootloader
adb devices -> shows an empty list, hence doing a -> fastboot devices shows no devices.
Going to Recovery Mode in Bootloader list of devices shows:
FA76F0303478 unauthorized
In Recovery Mode -> Advanced -> Enable ADB list of devices shows:
FA76F0303478 recovery
I can Apply Update in Recovery Mode via Sideload, but that does not help me get TWRP flashed.
With no devices showing in the main bootloader via adb I can't get the phone into autoboot mode. Per the link at android.gadgethacks.com in order to put the Factory Image back on the phone, https://developers.google.com/android/images, I need to get the phone into autoboot mode.
Anyone have any ideas????
Come-on guys & gals. I'm sure someone can help me at XDA get my devices to fastboot.
I just got a new F(x)tec Pro-1X and I want to root it. I'm following the instructions to use Magisk from the F(x)tec team which involves 1) installing Magisk, 2) connecting adb and authorizing, 3) adb pushing the Pro-1X boot.img, 4) Running Magisk and patching the boot.img, and 5) downloading the patched .img.
Then I run "adb reboot bootloader" which leads me to a screen where I can choose Recovery mode and then I get to an Android screen that says "No command". I believe it's here that I'm supposed to run "fastboot flash boot magisk_patched-25200_HsxJg.img"; however, when I run "adb devices", I get unauthorized, and trying to run fastboot anyway fails:
$ adb devices
List of devices attached
8ce396c8 unauthorized
$ fastboot flash boot magisk_patched-25200_HsxJg.img
< waiting for any device >
I found elsewhere that from this screen, I can hold the power button and press the volume up key and then release both and I see the Android recovery screen. Then I scroll down to Enter fastboot and press power to enter that and I see fastbootd, but I get the same "waiting for any device" output if I try the fastboot flash command here.
If I go back to recovery mode, and instead go to Apply update from ADB, I then see the following from adb devices, but I still can't run fastboot flash:
$ adb devices
List of devices attached
8ce396c8 sideload
I'm running the latest Android Studio and platform-tools on a Lenovo X270 running Fedora 37 and Linux kernel 6.0.17. I'm connecting using a USB-2 port without a hub and tried multiple USBC cords.
A commenter on the F(x)tec forums said that he could never get his Lenovo X250 to work and he had to buy a Raspberry Pi 3 model B.
Are there any alternatives or diagnostics I can run to help solve this "unauthorized" error?
Did you enable usb debugging in the developer options and validate the box after connecting with a USB cable?
ze7zez said:
Did you enable usb debugging in the developer options and validate the box after connecting with a USB cable?
Click to expand...
Click to collapse
Yes. That was required for steps 2-4 for pushing and pulling the image. When I did that, I had to authorize my laptop on my phone. There's no such dialog during recovery mode. Is there some way to pre-authorize recovery mode with my laptop, or otherwise disable this authorization?
Option below USB debugging, which is: Revoke USB debugging authorizations.
or
read this:
ADB Android Device Unauthorized
Since I reinstalled Eclipse (simply deleted and downloaded it again) I can't debug my applications on Samsung Galaxy i9001 (with CyanogenMod - Android 4.4.2). It worked fine before reinstallation.
stackoverflow.com
ze7zez said:
Option below USB debugging, which is: Revoke USB debugging authorizations.
or
read this:
ADB Android Device Unauthorized
Since I reinstalled Eclipse (simply deleted and downloaded it again) I can't debug my applications on Samsung Galaxy i9001 (with CyanogenMod - Android 4.4.2). It worked fine before reinstallation.
stackoverflow.com
Click to expand...
Click to collapse
Thanks, but none of that worked. My problem is authorizing during recovery mode, not during normal operations. It seems what I really need is to either modify /data/misc/adb/adb_keys on the device, or run adb disable-verity, or set ro.adb.secure=0, but I don't have permissions to do any of those.
It's interesting that another F(x)tec user says this works with a Raspberry Pi, and also says it does not work with his Lenovo X250 running Linux, which is similar to my laptop. This suggests there's some sort of limitation or additional security related to the Linux kernel 6.0.17 and/or Fedora, but I can't find what that is or how to diagnose it. I don't have SELinux running on my laptop.
Good day,
I'm use adb tools from my fedora 37
Your issue is related to how you call adb.
Try this:
adb kill-server
sudo adb start-server
sudo adb devices
The same game with fastboot tools
Its works perfect with selinux on
Regards
MoHuToP said:
Good day,
I'm use adb tools from my fedora 37
Your issue is related to how you call adb.
Try this:
adb kill-server
sudo adb start-server
sudo adb devices
The same game with fastboot tools
Its works perfect with selinux on
Regards
Click to expand...
Click to collapse
Doesn't work:
$ adb kill-server
$ sudo -i
# adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
# adb devices
List of devices attached
8ce396c8 device
# adb reboot bootloader
... Wait for recovery mode "no command" screen ...
# adb devices
List of devices attached
8ce396c8 unauthorized
# fastboot flash boot magisk_patched-25200_HsxJg.img
< waiting for any device >
For reference, attached are pictures of all the places where I try the commands and they fail.
I bought a Raspberry Pi 3 B and microSD, installed Raspbian, installed adb and fastboot, connected to phone (normal boot), authorized the Pi, ran adb reboot bootloader, entered recovery mode, phone goes to "No command" screen, but then I get a popup on my Raspberry Pi desktop that says:
Unable to open MTP device "001,013"
Clicked OK and ran adb devices, and I'm back to the "unauthorized" status and adb and fastboot don't work. Tried this in the Raspberry Pi as both a normal user and root (with adb kill-server in between).
Tried with another USB C cable and got a similar error, although it ended with "001,016".
Any ideas?
Resolved by running fastboot on the START screen! (And worked through my X270)