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 .
Related
Dear All
I'm a new android user, I just get a new A50 from Australia and try to root it. It's successful with z4root and I try to install Thai font to system. Unfortuantely I did wrong by deleting font folder in the system, therefore I can't run the system again. When I power on, it still have only garmin asus android logo and can't use it again. Does anyone please let me know how to restore or resolve this problem, or I have to throw it away? Thank you in advance.
Cheers!
Winext
Android 1.6 or the new 2.1 Eclair update?
It's a new Eclair 2.1 update, is there any solution?
Connect it to your computer via USB cable.
Using ADB, try this:
ADB REBOOT RECOVERY.
If it works, a yellow triangle appears with the green android guy.
Hit the HOME button. A menu appears. Use volume up/down to move through the options. Tap power to select it I beleive.
Reset/wipe to factory is one of the options.
If you need it, ADB is found in the Android SDK.
If that doesn't work, try calling in to Garmin for support.
Sent from my Garminfone using XDA App
Dear Spazmogen
Thank you for your suggestion, but I'm really new with ANDROID.
I downloaded ANDROID SDK and try to install but it dodn't work.
I use Win 7 64bit, do I need another software to run this command.
If possible, please let me know some previous post that already teach for beginner.
Thank you in advance.
Cheers!
Winext
ADB is a command line tool. But you will have to get Android SDK installed on the computer 1st.
Read the instructions for installing the SDK here: http://developer.android.com/sdk/index.html
ADB commands: HERE.
Interesting. I got into the recovery screen using the Quick Boot app,used the home button to show the menu. The arrows and volume buttons move, but can't actually do anything. Probably related to missing files that are reported in the data/cache/recovery folder.
https://www.garminasus.com/en_US/support/eclair/006-B1130-00.update
official 2.1 update came out today for USA GARMINFONES. Not the A50 Nuvifones elsewhere in the world...
Is the update different from the leaked one?
Sent from my Garminfone using XDA App
I am waiting for an answer to that question myself. I have no plans to change from the leaked version Garmin posted in mid-November.
Sent from my Garminfone using XDA App
Apparently someone did a bit comparison and said they matched. Plus, I tried and it told me it was the same version. On the plus side, I messed up my recovery partition and recovered it using the backups I made of each partition after I loaded 2.1 (dump_image). I made img backups and tar backups of all the files in 1.6 (I am anal about backing up). Good thing because 2.1 doesn't come with flash_image.
I can get into fastboot and the driver loads and stuff, but I get no devices listed when I do fastboot devices command. Next stop is Ubuntu
I know it works,just need to know how to get to it. Btw,I tried both the Garmin fastboot and adb drivers as well as adding the device hardware id's into the android drivers and neither worked.
I also need to find out if there is a similar enough kernel that I can use to get a fully functional recovery mode. I did find out that you can use adb just fine in the stock one and it loads a serial driver as well.
any possible way I could get that backup you made? I apparently didnt save my backup to the pc. And currrently I messed up permissions on my Garmin trying to get recovery working. I cant run the update or anything.
I've just stumbled across this forum post from google, I too am need of fixing my phone. All that is faulty is that the recovery mode has been overwritten with an incorrect one. Is it possible to extract the recovery image and reflash it from the optus supplied Android 2.1 006-B1130-00.update file?
Or is there a way of just getting say Rom Manager to work some magic for me?
Yes, it is possible... would be easier if someone could just use dump_image on a phone that has a working recovery mode and root access. I can provide the dump app and instructions.
Where can I get the Optus update, and are you positive recovery works on it? Does it also have working fastboot?
And to the other poster, which partition do you need? Btw, Rom manager has a permission fix mode. I can get you a tar file if it is the system partition or your choice of img or tar for the others.
And to everyone, after updating to 2.1, do a master clear because a lot of 1.6 apps are left over... duplicates.
Also, odexing all apps speeds it up a lot, with the caveat that you have to re-run the odex.sh file (found somewhere here and modified by me to be more thorough) after every app update or you will get force closes.
Oh I just reflashed the update again, and I got my recover menu back!
I'm not sure if i need any help anymore, but thanks for your offer of help merwin.
By working, do you mean that you can get to it with a hardware key combination and can actually select items?
first of all ,i 'm sorry for my english .my a50 is dead too.i also delet font folder and i use the adb command 'adb reboot recovery'.but the error is device not found. and my pohone can not boot .it stop at the android guy . how can i setup the device..Q.......Q......help me ..pls
garmin-asus a50
i have this garmin asus a50 was running 2.1 after installing a few apps.
tried to reboot and now is stuck on android screen.
tried hard reset stuck on android screen with wipe userdata on top
please help!
garmin-asus a50 dead
yoyoset
i think i have the same problem please let me know of any progress
thank you
I went through the [GUIDE] Rooting the 10.1 Tab, but I cannot get into fastboot.
I went through pershoots advice of uninstalling and reinstalling the drivers. I used the driver he has posted in the thread when I reinstalled.
Win7 cannot find the fastboot driver though. (Image attached)
*ADB works fine
*LE GoogleIO SGT with 3.1
Thanks to anyone who has some advice for me!
PS-- I'm too noob here to post in the dev forum.
same problem here annoying as f**
Hi, I facing the same problem here. Do you guys solve the problem? Please give me advice. Thank you
Same problem here. adb working fine on the tablet but not fastboot. I have tried Linux, osx, and win7 none work. Fastboot works fine on my nexus 1 with all of these platforms.
Sent from my GT-P7510 using XDA Premium App
Hi I just use mac os to done it, cause my windows 7 cant find the driver
my tab had just alive.. i cant post the link here cause i m newcomer..
jamn224 said:
I went through the [GUIDE] Rooting the 10.1 Tab, but I cannot get into fastboot.
I went through pershoots advice of uninstalling and reinstalling the drivers. I used the driver he has posted in the thread when I reinstalled.
Win7 cannot find the fastboot driver though. (Image attached)
*ADB works fine
*LE GoogleIO SGT with 3.1
Thanks to anyone who has some advice for me!
PS-- I'm too noob here to post in the dev forum.
Click to expand...
Click to collapse
I had similar problems and managed to finally use fastboot.
You have to choose drivers manually.
Read this post on how to choose drivers in order to get fastboot working
http://forum.xda-developers.com/showthread.php?t=1176292
Still no luck
I have had this problem for months, I have tried everything on this thread and on at least 10 to 20 other threads acrost the internet. I really need some help getting fastboot to work with my Galaxy Tab 10.1 Google I/O LE. Could this problem be from it being a I/O LE? Its so different than the shipping retail product, maybe these guides are for the retail 10.1? I would really appreciate any help!
Thanks
Josh
flacojo32,
As having just purchased an i/o edition used, i know what you mean about the differences, but i was able to root through fastboot on mine.. i just had to figure it out myself.
try this page, i wrote my steps that were successful for getting fastboot to load recovery:
http://forum.xda-developers.com/showthread.php?t=1429344
you may need to purge other drivers. i don't know exactly what protocol or method the fastboot is using for communication, but it may be based off the windows networking stack. i'd also suggest disabling any firewalls if it continues to fail.
flacojo32 said:
I have had this problem for months, I have tried everything on this thread and on at least 10 to 20 other threads acrost the internet. I really need some help getting fastboot to work with my Galaxy Tab 10.1 Google I/O LE. Could this problem be from it being a I/O LE? Its so different than the shipping retail product, maybe these guides are for the retail 10.1? I would really appreciate any help!
Thanks
Josh
Click to expand...
Click to collapse
The problem is using the right drivers. Going from memory here but in genersl go to your android-sdk folder and run sdk manager, select 3rd party and make sure to select usb drivers. After installing that go to device manager connect hte tab and you should see android device. if it has an exclamation point click on it and select update driver then select let me choose (not the browse for driver) - youn can then browse a list of devices and select samsung device. Once you do that the drivers are installed. you should be able to do fastboot.
A quick test is with the tab connected to the pc open a commamd editor type 'fastboot devices' and it should show a number
Sent from my GT-P7510 using Tapatalk
Thanks all for you help, but still no luck. I have rooted and or installed many of custom roms but just can't crack this one. I have all the right drivers for my other nexus devices to root them but this samsung galaxy tab 10.1 Google I/O just does not do fastboot right. It goes into fastboot but I don't know if its actually pushing the information to the computer. When I look under the Device Manager it show up as an ADB device, not fastboot. Also ADB works fine so the issue is with the tablet and how the fastboot is accomplished. Is there any other way to get a custom rom on this without fasboot? I have tried to use Odin and ADB to push a recovery but when I ADB reboot devices it just boots back up. That is after I have pushed a recovery file to the tablet. Im hopelessly deadlocked, I thought the LE I/O tab was to be open in every way for devs. but I can't seem to crack this beautiful device. Thanks for everyones help!
Josh
---------- Post added at 07:23 AM ---------- Previous post was at 07:21 AM ----------
Heck and I even used a mac that does not require drivers to try it, still it would not connect in fastboot mode. It did not even pull it up when I fastboot devices, just like on the windows machine.
Josh
flacojo32 said:
Thanks all for you help, but still no luck. I have rooted and or installed many of custom roms but just can't crack this one. I have all the right drivers for my other nexus devices to root them but this samsung galaxy tab 10.1 Google I/O just does not do fastboot right. It goes into fastboot but I don't know if its actually pushing the information to the computer. When I look under the Device Manager it show up as an ADB device, not fastboot. Also ADB works fine so the issue is with the tablet and how the fastboot is accomplished. Is there any other way to get a custom rom on this without fasboot? I have tried to use Odin and ADB to push a recovery but when I ADB reboot devices it just boots back up. That is after I have pushed a recovery file to the tablet. Im hopelessly deadlocked, I thought the LE I/O tab was to be open in every way for devs. but I can't seem to crack this beautiful device. Thanks for everyones help!
Josh
---------- Post added at 07:23 AM ---------- Previous post was at 07:21 AM ----------
Heck and I even used a mac that does not require drivers to try it, still it would not connect in fastboot mode. It did not even pull it up when I fastboot devices, just like on the windows machine.
Josh
Click to expand...
Click to collapse
Sorry for dumb Qs but wanted to make sure we are all on the same page.
So i take it you dont get a response when you connect via fastboot and type fastboot devices
You said you can use adb to push recovery did you try booting up from cold with the power and volume keys combo to enter recovery mode?
Sent from my GT-P7510 using Tapatalk
Right no response from the device or the PC when I type fastboot devices either on a Mac or PC. The problem lies that there is no button combination to boot the Google I/O LE Galaxy Tab into recovery, the only two options the Power + volume down button boot provides are the Fastboot(USB symbol) and the Android dude shoveling stuff(ODIN) choices. I can push recovery all day using ADB but there is no way for me to boot into recovery on the Limited Edition Tab. This is even after I try to reboot into recovery using ADB (ADB recovery or something like that) all that does is to boot me to the two choices Fastboot(USB symbol) and ODIN(android dude shoveling). I have pretty much tried everything. I appreciate all the help you are providing!
Josh
Any ideas? I can't be the only one with this problem.
flacojo32 said:
Any ideas? I can't be the only one with this problem.
Click to expand...
Click to collapse
It sounds like you do not have recovery. And since fastboot does not seem to work then it is likely yoi have the wrong drivers. Can you confirm you were able to push the recovery via adb?
Did you install the google drivers as described a couple of posts before ie using android sdk
Sent from my GT-P7510 using Tapatalk
animatechnica, I thank you for all of your help. But I return triumphant. I have found it to be a driver issue. I was trying to use a newer version of PDANet for Android (version 3.02) which did not include the correct drivers for the Galaxy Tab 10.1 LE. So I downloaded the version 2.15 of PDANet and bam fastboot started working like a charm. So I appreciate all the help from you animatechnica and also shane86 for his words of wisdom too. But overall tonight was a good night the Tide rolled, got my ICS update on my Transformer Prime and got fastboot to work and installed Galaxy Task 10.x on my Galaxy Tab 10.1 Google I/O LE. Im off to geek it up. Thanks all.
sweet and i will take note of how you solved it for future reference
flacojo32 said:
animatechnica, I thank you for all of your help. But I return triumphant. I have found it to be a driver issue. I was trying to use a newer version of PDANet for Android (version 3.02) which did not include the correct drivers for the Galaxy Tab 10.1 LE. So I downloaded the version 2.15 of PDANet and bam fastboot started working like a charm. So I appreciate all the help from you animatechnica and also shane86 for his words of wisdom too. But overall tonight was a good night the Tide rolled, got my ICS update on my Transformer Prime and got fastboot to work and installed Galaxy Task 10.x on my Galaxy Tab 10.1 Google I/O LE. Im off to geek it up. Thanks all.
Click to expand...
Click to collapse
I'll start out that I'm new to android, been an avid blackberry user that just purchased my note 2. I followed the casual root application, and unlocked and rooted my device. I went to install cm 10.2 mod on my device after wiping the device in development mode and it failed. Now my device will not respond to either download mode or development mode. I'm kind of stuck and not sure how to approach the correct solution to get my device back up and running.
Any help would be very appreciated, Thanks in advanced!
Sorry I should of mentioned this in the above post, I did make sure that the cm mod I downloaded was for my specific device. Is it possible that maybe the root/unlock method failed and thats where I went wrong when installing the cm mod? I also get no response when the device is plugged into my pc. So its not being read by odin currrently
Since it appears I have hard bricked my device, not quite sure what steps I can do to recover. I get no power to the device in any situation, I've read online about riff jtag (sorry spelling), if anyone could point me in a direction it would be helpful. Thanks in advance.
Hi there I think I have softbricked my Nabi 2. I tried to update the software from ICS to JB using files from the XDA Nabi 2 Wiki but have come to a massive problem. I can't boot back into TWRP because all I get is an Android laying down with an ! on his chest. I can't re-install TWRP because my Windows 8 PC can no longer see the device!! I can get into the tablet options menu with fastboot, forced recover etc. I think the biggest problem is getting the PC to see the device.
If I try selecting different options in the tablet boot menu then Windows will see the device as Android ADB Device or MTP USB Device.
Can anyone help me get over this problem? I'm not used to using shell commands but fear I will have to install the Android environment to use ADB to get things working.
Please help if you can as this tablet belongs to a nephew of mine and he is missing his YouTube. I am close to tears trying to find the solution. I have read and re-read XDA posts in case I missed something.
Many Thanks In Advance.
Doozeman
Hello,
First of all I read all topics regarding this issue and I'm using Windows as my operating system (no linux/unix).
My problem is I cannot make the device available when issuing the adb device command, in adb, although I ran all steps (read the hole 72 pages from [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 ).
I read a thread in which someone gave a hint to similar issue, by flashing the stock image to one "CWM Recovery v6.0.3.6.tar" file - which I did, using ODIN (v.307), where I can see my device mapped at some COM port, but after successfully flashing I expected to have my device showed in "adb device" command, but I don't.
Also I tried using the drivers from above topic, the ones from Samsung (which allowed me to use ODIN and successfully flash), I'm using the up volume key after booting in order to put Samsung device in "download mode", but still...I'm not able to see it under adb (because I want to use it to retrieve files).
Is there anything else I can try? As long as I can successfully flash, isn't there an image with debugging mode on? For now I think this is the only "variable" which I'm not able to alter, as I do not have the display.
Many thanks,
miborion said:
Hello,
First of all I read all topics regarding this issue and I'm using Windows as my operating system (no linux/unix).
My problem is I cannot make the device available when issuing the adb device command, in adb, although I ran all steps (read the hole 72 pages from [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 ).
I read a thread in which someone gave a hint to similar issue, by flashing the stock image to one "CWM Recovery v6.0.3.6.tar" file - which I did, using ODIN (v.307), where I can see my device mapped at some COM port, but after successfully flashing I expected to have my device showed in "adb device" command, but I don't.
Also I tried using the drivers from above topic, the ones from Samsung (which allowed me to use ODIN and successfully flash), I'm using the up volume key after booting in order to put Samsung device in "download mode", but still...I'm not able to see it under adb (because I want to use it to retrieve files).
Is there anything else I can try? As long as I can successfully flash, isn't there an image with debugging mode on? For now I think this is the only "variable" which I'm not able to alter, as I do not have the display.
Many thanks,
Click to expand...
Click to collapse
Have tried today, 3 different phones (some Sam I9300, Sam A3), but still same issue, devices not shown in devices command although I had enabled developer mode.
Should I check somethings regarding the PC? the port if is opened or not?
Look at below forum for your device Samsung I9300i
http://forum.xda-developers.com/galaxy-s3-neo
Please search for your problem and still having problems please create a new thread in below url
http://forum.xda-developers.com/galaxy-s3-neo/help
There is thread called [GUIDE] How to UNBRICK Samsung Galaxy S3 Neo ( i9300i & i9301i )
please select this url and search for it if u had a brick
http://forum.xda-developers.com/galaxy-s3-neo/help/how-to-unbrick-t2911301
Please search before making any new thread.
If I helped you please press THANKS button
Thanks
Salman Al-Badgail
Salman Al-Badgail said:
Look at below forum for your device Samsung I9300i
http://forum.xda-developers.com/galaxy-s3-neo
Please search for your problem and still having problems please create a new thread in below url
http://forum.xda-developers.com/galaxy-s3-neo/help
There is thread called [GUIDE] How to UNBRICK Samsung Galaxy S3 Neo ( i9300i & i9301i )
please select this url and search for it if u had a brick
http://forum.xda-developers.com/galaxy-s3-neo/help/how-to-unbrick-t2911301
Please search before making any new thread.
If I helped you please press THANKS button
Thanks
Salman Al-Badgail
Click to expand...
Click to collapse
Hello Salman,
The reason why I opened this post is that I need something which is not specific to my mobile model, in my case Sam. i9300i, but something which is useful for any other user as well, especially ones in my situation (broken display, with no debugging mode activated).
What I was trying to find in this section of the forum and trust me, by now I have read everything it was to read on this topic, was a custom build rom, which could have that debugging mode activated, as without it I (or somebody else in this predicament) cannot extract the needed data via ADB.
Therefore if somebody has any idea or knowledge about a such image, please do share.
Regards,
maybe you could try to enable the adb before you flash the stock rom by editing the build.prop file.
or you simply could try with this http://forum.xda-developers.com/tools/general/tool-gstreamer-emergency-toolbox-t3289951
good luck bro