Hello all,
Like seemingly many others, my io edtion galaxy tab 10.1 is blocked in a boot loop. I've read about some methods allowing to reset the tablet thanks to adb and or fastboot.
But my problem is that in whatever state my tablet is, adb and fastboot never seem to be able to detect it, so I can't use them to wipe it and I don't see an other so I can't repair my tablet.
My question is : has anyone been able to make a boolooping tablet detectable by android dev tools ?
Alternatively, has anyone been able to get in touch with samsung support on that issue ? Are io edition tablets under warranty ? I haven't seen any reports related to that.
Thanks in advance for your answers, it is my last chance attempt to make that tablet work again.
Are you able to enter Download Mode? If so, you should be able to communicate with your tablet using Odin.
Go to the link in my signature and read Sections IV and VI.
If someone else can point you to the correct .tar file for your device (do not use the one T-Mobile one), you can just follow directions in Section VI to restore your tablet.
Regarding warranty, if you have messed around with your device's firmware, it should be void. Try to solve the issue yourself.
Teovald said:
Hello all,
Like seemingly many others, my io edtion galaxy tab 10.1 is blocked in a boot loop. I've read about some methods allowing to reset the tablet thanks to adb and or fastboot.
But my problem is that in whatever state my tablet is, adb and fastboot never seem to be able to detect it, so I can't use them to wipe it and I don't see an other so I can't repair my tablet.
My question is : has anyone been able to make a boolooping tablet detectable by android dev tools ?
Alternatively, has anyone been able to get in touch with samsung support on that issue ? Are io edition tablets under warranty ? I haven't seen any reports related to that.
Thanks in advance for your answers, it is my last chance attempt to make that tablet work again.
Click to expand...
Click to collapse
The issue here is having the right driver. Assuming you imstalled the amdroid ask, run sdk mamager tick 3rd party then usb drivers and let the sdk manager install the drivers. Thwm go to your pc control panel and check for android or samsung device (going by memory here) if there is an exclamation mark, right click and selwct update driver then 'let me choose' then find android device among the listed. Click that and try odin
Sent from my GT-P7510 using Tapatalk
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Thanks a lot for those answers, I have finally been able to restore my tablet using this method found on rootzwiki / topic 2525 guide wifi flashing stock bootloader to io tab (sorry but i can't post links on xda)
Sadly, it also installed samsung's touchwiz but that is nothing that a custom rom can't fix .
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
adiemask said:
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
Click to expand...
Click to collapse
try this: http://forum.xda-developers.com/showthread.php?t=1706918
if it didnt help u just reply and we´re gonna look whats next to unbrick ur phone
Hi
Thanks for your reply, I have hit the 'Thanks' button
I read the posting you referenced but it doesn't really offer a solution to my problem.
As described earlier I rooted my phone and flashed a Rom (Maximus) succesfully but on turning the phone on after installing the new Rom I got into a cycle of the phone rebooting without actually getting past the lock screen. My thoughts at that stage were to re flash using stock rom but on running fastboot and plugging into my Mac OSX machine via USB, the phone doesn't show up in 'devices' on the Mac. I have also tried 'adb devices' form within Android Dev Tools and although 'adb' runs fine no device is reported. Of course without devices being avaialble to 'adb' then I cannot reflash!
I have also tried from within a bootcamp installation of 'Windows XP' installed on the mac with the same results, this with 'HTC Sync' installed and therefore providing the USB Drivers required within Windows.
I have tried logging into fastboot using 'power' and 'Down Volume' at various stages of the boot process on the phone but have never seen the phone within devices.
Clearly prior to installation of the Rom (Maximus) I could see devices at both the Finder window on the Mac and from adb devices.
Any help or insight you could provide would be very gratefully received
Ok ok ok dont worry
I had to read a bit and found quit much german threads where they flash back the stock rom
as is suggested u cant flash it with odin...
the only solution i woul suggest is that u have to find a computer running windows
there its very easy to restore the stock with the methods u described earlier in the thread...
hope u get done let me know what happend
=)
The question remains; how can I flash anything be it a hacked rom or an official rom when I cant see the 'device' in both windows and mac osx?
I think what I am looking for is a reason why the phone isn't seen when plugging in via USB. Once it is seen as a 'device' I will be able to flash anything via 'adb'.
Thank you for your continued interest and assistance
ok so u know how the get it back but ur phone is not really recognized by ur computer
but i found a method using the bootloader
the problem is that the instructions are in german
but i think if u google a bit u may find it
Don't know if I misunderstood what you said..but to get into recovery, you hold volume down and the power button when the phone is turned off. Not during the boot process.
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
moksha098 said:
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
Click to expand...
Click to collapse
Yes, I know that. He said he attempted to do that DURING the boot process. I was stating that he had to do it while the phone was powered down.
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
adiemask said:
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
Click to expand...
Click to collapse
But if this doenst work why dont u try the method with the recovery mode or the bootloader i suggested
Hello All,
I have taken the liberty of re-packaging the adb binary and fastboot binaries so they will work naively on Android into a flashable zip file. With these tools, you can theoretically use your Android device (plus a USB OTG Cable) to connect to another Android Device. If your device has a native USB port (such as the ASUS Transformers), it will work as well.
As not to conflict with the official adb in /system/bin (which does not work the same way), I renamed these to "kadb" and "kfastboot". You just need to supply your own Terminal Emulator (such as connectbot) to use.
Example Uses
1) Unlock a bootloader on a Nexus device (erases all data on the target device)
kfastboot oem unlock
2) Lock a bootloader
kfastboot oem lock
3) Boot a recovery
kfastboot boot /sdcard/path/to/recovery.img
4) Flash a recovery
kfastboot flash recovery /sdcard/path/to/recovery.img
5) Reboot into the bootloader
kadb reboot bootloader
6) Shell
kadb shell
7) Reboot into recovery
kadb reboot recovery
8) logcat
kadb logcat
9) Sideload an APK file
kadb install /sdcard/path/to/APK.APK
10) Push a file
kadb push /sdcard/path/to/file /sdcard/path/to/destination
Please remember that these are taking place on the remote device connected via USB. Most, if not ALL ADB commands are supported. You can even modify most linux based one-click root methods (by changing all "adb" references to "kadb" and "fastboot" with "kfastboot") and run them via shell. Its also perfect for remote debugging of embedded Android Systems. Hell, the uses are endless!
Installation Instructions
Note : You do not need to be rooted, you do however need a custom recovery or temp boot a custom recovery.
1) Flash the attached Zip File via any Recovery such as CWM or TWRP
2) Reboot and install a Terminal Emulator, if using ConnectBot, you should choose the "local" option.
3) Connect a device and test
This should support any ARM based device, so far I have tested it on my ASUS Nexus 7 and ASUS Transformer 700 (Stock/Rooted)
HAVE FUN!!!
KMyers said:
Hello All,
I have taken the liberty of re-packaging the adb binary and fastboot binaries so they will work naively on Android into a flashable zip file. With these tools, you can theoretically use your Android device (plus a USB OTG Cable) to connect to another Android Device. If your device has a native USB port (such as the ASUS Transformers), it will work as well.
As not to conflict with the official adb in /system/bin (which does not work the same way), I renamed these to "kadb" and "kfastboot". You just need to supply your own Terminal Emulator (such as connectbot) to use.
Example Uses
1) Unlock a bootloader on a Nexus device (erases all data on the target device)
kfastboot oem unlock
2) Lock a bootloader
kfastboot oem lock
3) Boot a recovery
kfastboot boot /sdcard/path/to/recovery.img
4) Flash a recovery
kfastboot flash recovery /sdcard/path/to/recovery.img
5) Reboot into the bootloader
kadb reboot bootloader
6) Shell
kadb shell
7) Reboot into recovery
kadb reboot recovery
8) logcat
kadb logcat
9) Sideload an APK file
kadb install /sdcard/path/to/APK.APK
10) Push a file
kadb push /sdcard/path/to/file /sdcard/path/to/destination
Please remember that these are taking place on the remote device connected via USB. Most, if not ALL ADB commands are supported. You can even modify most linux based one-click root methods (by changing all "adb" references to "kadb" and "fastboot" with "kfastboot") and run them via shell. Its also perfect for remote debugging of embedded Android Systems. Hell, the uses are endless!
Installation Instructions
Note : You do not need to be rooted, you do however need a custom recovery or temp boot a custom recovery.
1) Flash the attached Zip File via any Recovery such as CWM or TWRP
2) Reboot and install a Terminal Emulator, if using ConnectBot, you should choose the "local" option.
3) Connect a device and test
This should support any ARM based device, so far I have tested it on my ASUS Nexus 7 and ASUS Transformer 700 (Stock/Rooted)
HAVE FUN!!!
Click to expand...
Click to collapse
Very interesting and nice work, certainly a lot of interesting possibilities for apps that could be written to take advantage of these features.
Awesome Post. Thanks Alot.Need this tool very much .
shimp208 said:
Very interesting and nice work, certainly a lot of interesting possibilities for apps that could be written to take advantage of these features.
Click to expand...
Click to collapse
Yeh... I can picture one of you going to a store and rooting all of the Demo Tablets or Phones with your phones. With a small amount of effort, one can port ZergRush or a few of the "adb backup restore" exploits over to run naively on your Phone or Tablet.
No GameStop, BestBuy, Sprint Store, T-Mobile Store, AT&T Store, CompUSA or WalMart is safe
KMyers said:
Yeh... I can picture one of you going to a store and rooting all of the Demo Tablets or Phones with your phones. With a small amount of effort, one can port ZergRush or a few of the "adb backup restore" exploits over to run naively on your Phone or Tablet.
No GameStop, BestBuy, Sprint Store, T-Mobile Store, AT&T Store, CompUSA or WalMart is safe
Click to expand...
Click to collapse
Or Verizon Store, or any other store that sells smartphones and tablets . You could make a app that has a run button that when pressed automatically run's a root exploit such as Zerg Rush, then permanently flashes a custom recovery, then a custom ROM of your choice all one after the other. Think of it as mix of z4root, EZ-Recovery, and ROM manager all rolled into one. Only problem is not every device supports fastboot so some devices would be left out. Also wondering if you wouldn't mind clarifying if the target device must be running a custom recovery or the host device must be running a custom recovery for this to work?
shimp208 said:
eft out. Also wondering if you wouldn't mind clarifying if the target device must be running a custom recovery or the host device must be running a custom recovery for this to work?
Click to expand...
Click to collapse
Hello,
Just the host device needs a custom recovery only to install the tools (this can be perm flashed or temp flashed (fastboot boot recovery.img). Once the tools are installed, the recovery is no longer used.
The target device only needs USB Debugging enabled.
You are also correct in your statement that not all phones respond to the Fastboot protocol. The other tools such as Odin and NVFlash are not so easy to package. Some devices such as the ASUS Transformer TF700 have a Fastboot mode, assuming you unlock the bootloader. Fastboot is the standard on all HTC, Sony and any phone bearing the sacred "Nexus" moniker. It is also favored among "cheap/knockoff" devices.
There are several root tools that simply use adb to work.
What?!
KMyers said:
Hello All,
I have taken the liberty of re-packaging the adb binary and fastboot binaries so they will work naively on Android into a flashable zip file. With these tools, you can theoretically use your Android device (plus a USB OTG Cable) to connect to another Android Device. If your device has a native USB port (such as the ASUS Transformers), it will work as well.
As not to conflict with the official adb in /system/bin (which does not work the same way), I renamed these to "kadb" and "kfastboot". You just need to supply your own Terminal Emulator (such as connectbot) to use.
.....
HAVE FUN!!!
Click to expand...
Click to collapse
I'm truly stumped as to why you don't have pages of thank you posts here but I wanted to add mine. So often I cannot get to my PC or just want more freedom but need to use Fastboot. Now I'm free! Thank you so much! I
rainabba said:
I'm truly stumped as to why you don't have pages of thank you posts here but I wanted to add mine. So often I cannot get to my PC or just want more freedom but need to use Fastboot. Now I'm free! Thank you so much! I
Click to expand...
Click to collapse
Thanks,
I guess the reason many have not downloaded this is because it was stuck in one of the lesser active sections of XDA-Developers. I assume that most people visit the portal and device specific development threads. Aside from being featured on the portal, not many ways to get people in here.
Just tried this out on my nexus 7 running ubuntu, this is indeed awesome, thanks for compiling it
Hi, just came across this whilst trying to find a solution to flashing a custom recovery on an Nexus 7 that i cannot get to a computer. (its in my car). this would fit my needs perfectly but i just cannot get it to work. wondering if im missing something.
ive tried using another N7, and also my Galaxy Nexus. i plug in using an OTG cable on host device, then a USB cable to the target device. the target device starts to charge, and it shows debugging icon on notification bar.
Then try "kadb devices" but shows no devices. could it be to do with the adb binaries needing updating? (current adb is 1.0.31, this one is 1.0.29).. All devices are running stock rooted 4.2.2 (except the target device, that im trying to root.)
i have a friend interested too, he tried with a 4.2.2 Nexus 7 to a HTC One X and is seeing similar issue.
hope theres an easy fix, or something obvious im doing wrong.
Cheers
Ross.
rmclardy said:
Hi, just came across this whilst trying to find a solution to flashing a custom recovery on an Nexus 7 that i cannot get to a computer. (its in my car). this would fit my needs perfectly but i just cannot get it to work. wondering if im missing something.
ive tried using another N7, and also my Galaxy Nexus. i plug in using an OTG cable on host device, then a USB cable to the target device. the target device starts to charge, and it shows debugging icon on notification bar.
Then try "kadb devices" but shows no devices. could it be to do with the adb binaries needing updating? (current adb is 1.0.31, this one is 1.0.29).. All devices are running stock rooted 4.2.2 (except the target device, that im trying to root.)
i have a friend interested too, he tried with a 4.2.2 Nexus 7 to a HTC One X and is seeing similar issue.
hope theres an easy fix, or something obvious im doing wrong.
Cheers
Ross.
Click to expand...
Click to collapse
Hello Ross,
The new "secure adb" that was introduced in Android 4.2.2 will not work at this time. You may be able to try running "adb devices" at root to see if it works for you. If not, you can manually reboot it into recovery and use kfastboot to flash the new recovery
Hi Keith, thanks for the reply.
sorry for my delayed response, busy few days!. I did have another go at seeing if i could get two devices talking to each other using kfastboot, but again, i dont seem to be picking anything up. "kfastboot devices" just returns me to the prompt with no devices listed. im trying between a galaxy nexus and another nexus 7. my other problem is that the one i have fiited in the car no longer has access to the volume keys, so i cant even manually get into the bootloader. Shame its not possible to turn off the secure adb feature. lol.
it was worth a try tho.
Cheers
Ross.
rmclardy said:
Hi Keith, thanks for the reply.
sorry for my delayed response, busy few days!. I did have another go at seeing if i could get two devices talking to each other using kfastboot, but again, i dont seem to be picking anything up. "kfastboot devices" just returns me to the prompt with no devices listed. im trying between a galaxy nexus and another nexus 7. my other problem is that the one i have fiited in the car no longer has access to the volume keys, so i cant even manually get into the bootloader. Shame its not possible to turn off the secure adb feature. lol.
it was worth a try tho.
Cheers
Ross.
Click to expand...
Click to collapse
Hello Ross,
If your device is currently rooted, you should be able to run an App from the Play Store to reboot it into recovery (https://play.google.com/store/apps/details?id=com.liveov.rebooter ), from there, kfastboot will work
Great tool. Just unlocked, installed recovery and rooted my Google Nexus 4 with my Asus TF300t.
It only took a while before I figured out that the first terminal command must be SU before I could use the kfastboot command.
Thanks for your work.
Harald
Verstuurd van mijn Nexus 4 met Tapatalk
777.300 said:
Great tool. Just unlocked, installed recovery and rooted my Google Nexus 4 with my Asus TF300t.
It only took a while before I figured out that the first terminal command must be SU before I could use the kfastboot command.
Thanks for your work.
Harald
Verstuurd van mijn Nexus 4 met Tapatalk
Click to expand...
Click to collapse
Hello,
You would be correct as Fastboot needs root access to be able to run (it is the same as fastboot on Ubuntu)
KMyers said:
Hello,
You would be correct as Fastboot needs root access to be able to run (it is the same as fastboot on Ubuntu)
Click to expand...
Click to collapse
Yes I know but did not remember it when using your great tool for the first time. Perhaps it is good to mention it in your first post.
You build a great tool, still amazed that I was able to unlock, root and install a recovery on my Nexus 4 thru my Asus tablet while on vacation . (laptop at home)
Just great.
Harald
Verstuurd van mijn ASUS Transformer Pad TF300T met Tapatalk
777.300 said:
Yes I know but did not remember it when using your great tool for the first time. Perhaps it is good to mention it in your first post.
You build a great tool, still amazed that I was able to unlock, root and install a recovery on my Nexus 4 thru my Asus tablet while on vacation . (laptop at home)
Just great.
Harald
Verstuurd van mijn ASUS Transformer Pad TF300T met Tapatalk
Click to expand...
Click to collapse
Yes, I had a similar issue a few weeks ago. I was in Texas for a few days and my HTC EVO 4G LTE had an unfortunate run in with the Drink Cart on the Airplane. I had to go out and purchase a new phone at the Sprint Store in Texas. I had the phone purchased and rooted in about 10 minutes . Thanks to revone, unlocking the bootloader on the HTC one took almost no effort and I had S-Off to boot. All from my ASUS Transformer 700
so this is only for nexus?
Thank you very much!,
Testing on Samsung Galaxy Y
Just what i was looking for
I am yet to test it out, but i surely am very happy to see this thing actually exists. Just googled it out of the the blue and "kaboom!"here it was..
Keep up the good work.
Cheers
Recently, actually the day after getting a phone, it broke, somehow, while using king root, and I need to fix it quick as possible. Is it possible to flash a new rom onto a phone using the chromebook I have. I need to know quick before I get in trouble.:crying:
H4ck3rz said:
Recently, actually the day after getting a phone, it broke, somehow, while using king root, and I need to fix it quick as possible. Is it possible to flash a new rom onto a phone using the chromebook I have. I need to know quick before I get in trouble.:crying:
Click to expand...
Click to collapse
Hello H4ck3rz,
I have recently purchased a Samsung Chromebook Plus and I also recently got a Nexus 6. I have been looking into how to use fastboot in order to root and rom my Nexus. I have found some promising info on the subject:
I first found this XDA Article that gives more of an overview on enabling ADB and Fastboot on Chrome OS
https://www.xda-developers.com/guide-to-enable-adb-and-fastboot-on-chromeos/
That article refers to an actual XDA guide (tutorial thread) at the very end:
https://forum.xda-developers.com/showthread.php?p=38232908#post38232908
I've read through them both and they seem pretty straight forward. It helps to have a bit of command line knowledge, but the commands used are clear in the instructions.
There is a section in the tutorial that links back to the Chromium Project site where you'll have to find your specific device to learn how to get into developer mode (assuming you don't already know).
NOTE: I have not tried this yet, but I am 100% sure I am going to at some point soon. Probably some time this weekend. After I go through it, I will post again to let you know how it went, if you want to wait to hear about results before you try it.
Hope this helps.
Rk.
Update: I decided I to work on this last night and from the beginning I had problems. TL;DR - adb and fastboot are already part of the developer mode system on my Chromebook Plus. So the need to follow those guides isn't necessary for me.
I was not, however, able to do anything to my Nexus 6 from my Chromebook. Since the Plus only has USB Type-C ports, I bought a USB Type-C to Micro USB cord, but the Nexus wasn't being recognized properly. adb devices returned "????????????" devices, and I didn't get anything with fastboot. I can only surmise that it is the cord, because on my windows laptop, adb and fastboot work flawlessly while my Nexus 6 was connected with the included sync cable.
I'll post again if have more info to share. Sorry I couldn't be of more help.
Rk
rkwarner2 said:
Hello H4ck3rz,
I have recently purchased a Samsung Chromebook Plus and I also recently got a Nexus 6. I have been looking into how to use fastboot in order to root and rom my Nexus. I have found some promising info on the subject:
I first found this XDA Article that gives more of an overview on enabling ADB and Fastboot on Chrome OS
https://www.xda-developers.com/guide-to-enable-adb-and-fastboot-on-chromeos/
That article refers to an actual XDA guide (tutorial thread) at the very end:
https://forum.xda-developers.com/showthread.php?p=38232908#post38232908
I've read through them both and they seem pretty straight forward. It helps to have a bit of command line knowledge, but the commands used are clear in the instructions.
There is a section in the tutorial that links back to the Chromium Project site where you'll have to find your specific device to learn how to get into developer mode (assuming you don't already know).
NOTE: I have not tried this yet, but I am 100% sure I am going to at some point soon. Probably some time this weekend. After I go through it, I will post again to let you know how it went, if you want to wait to hear about results before you try it.
Hope this helps.
Rk.
Click to expand...
Click to collapse
Thanks for this! I can't find my windows laptop and all I have to use now is a Chromebook that does not have adb or fastboot installed. I followed the links and tutorials you shared and was able to install chroot (linux), install adb and fastboot on that linux, and then finally use it to load my phone into fastboot and flash TWRP on my nexus 5. You saved me so much trouble!
i3uu said:
Thanks for this! I can't find my windows laptop and all I have to use now is a Chromebook that does not have adb or fastboot installed. I followed the links and tutorials you shared and was able to install chroot (linux), install adb and fastboot on that linux, and then finally use it to load my phone into fastboot and flash TWRP on my nexus 5. You saved me so much trouble!
Click to expand...
Click to collapse
can you please help me. when I enter 'sudo adb devices' the device is seen. but it says unauthorized. Can you help me with a a step by step write up. I want to flash Android P on to my Pixel 2 XL.
Thanks