My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
http://www.mediafire.com/?gcenefqc3khcc0c
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Please DO NOT ask Questions in the Development forum
Moving to General
When i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
It is alive again. Thanks all who helped out
renedg said:
when i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
Click to expand...
Click to collapse
it is alive again. Thanks all who helped out
You are the man! My IO Galaxy Tab 10.1 is alive again!
Thanks!
Hi All,
I am done the ODIN step, but it still in bootloop mode. I dont know how to do with the Fastboot recover mode. I tried with my Windows 7 and it can't recognized my fastboot driver and stay in the <waiting for device>. Is there any solution for me. Thank you so much.
ericc191 said:
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
Click to expand...
Click to collapse
Hello, I have also followed these directions however I am having issues rebooting into recovery using adb.
When I execute adb devices no devices are found.
Any additional help would be appreciated. Thanks
UPDATE:
Success!! I was able to correct the boot loop problem by installing fastboot on a linux machine and running sudo fastboot -w. Also my tablet was in fastboot mode (Power + Volume down, then Select the usb symbol).
Instructions for installing fastboot were found here http://forum.xda-developers.com/showpost.php?p=14675422&postcount=2
boot looping SOLVED! Honeycomb 3.1 google i/o galaxy tab 10.1
[IO TAB] Boot looping? Try this to get your tab back...
I had an issue with my IO 10.1 Tab boot looping. I imagine that this would work for retail as well but have not tried it.
This process will factory reset your device.
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Fastboot & Stock IO recovery comes from this post as an attachment at the bottom.
You need adb to continue (windows).
1. Extract files to where adb resides (platform-tools folder in android SDk main folder) e.g
C:\Program Files\Android\android-sdk\platform-tools .
2. Plug your tab in to a power source and then hold down the power button until it shuts down. Wait until the tab displays the charging battery.
3. Press and hold the volume down (left button in landscape) and power buttons until the usb and odin icons show up. Volume down to move left and volume up to select the usb logo. Now you should be in fastboot. Plug the usb into your computer.
4. Time to fire up adb!
Start / run / cmd , cd\,
Than, cd to your platform-tools folder or wherever your adb is at. (should be in platform-tools inside of android-sdk-windows)
5. In cmd type "adb start-server" without quotes to start adb. All comands should exclude quotes.
6. Type "fastboot devices" your device serial should appear!If not:
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows).
NO Empty line above this set, though galaxy tab 10.1v but works for all variants!(tab detected as adb xxx device)
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
;
Download the fastboot zip attached to this post (includes both Win and Linux version) and extract the files to your “<PATH TO ANDROID SDK>\platform-tools” folder
7. Now, type "fastboot boot recovery.img"
8. Now you should boot into recovery. For "adb command lines" to work boot with clockworkmod recovery img (Command and files here: http://droidbasement.com/db-blog/?p=2032)
If you want to try other stuff like push a system restore, kernel or whatever, now you can. If you fail at it, you can always repeat the steps leading up to this point to get back to recovery.
9. Time to just get the tab back! Select "wipe data/factory reset" and confirm, clear cache.
10. After that is done select "reboot device".
Credits to JASKRU from rootwiki, with some additions and modifications extracted from different sources!
for rooting the tab install the zip file from this post in recovery mode (loading recovery.img from fastboot):
http://droidbasement.com/db-blog/?p=2054
P.S don't reboot into recovery with adb command "adb reboot recovery" as it doesn't work, correct way is with fastboot command as mentioned in step 7!
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
FIRST STEP: add the attached fastboot files into the container folder of adb (in sdk folder)
This is mine:
C:\Program Files\Android\android-sdk\platform-tools
of course I did that and mine is in the same folder as yours
I get to step six and thats when it gives me the error
E:\android-sdk-windows\platform-tools>fast boot devices
'fast' is not recognized as an internal or external command,
operable program or batch file.
also when I go to the left instead of odin this is my pic (in attachment)
NOW if I hit the power button and the right on in landscape mode I do get the android system recovery options says Android System Recovery <3e> (pic attached)
I have tried wiping date clearing cache as far as fastboot goes it still doesnt let me in fastboot eventhough im not sure at this point what fastboot even is
I finally got CWM 4.0.0.4 on it but now what because somehow im on 3.0.1 on my tab it wont charge and idk what to do
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
tried this route but it cannot find my device via ADB - used the PDANet driver - note i did not get a driver in the extras folder
ideas?
mughalgxt said:
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
Click to expand...
Click to collapse
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
animatechnica said:
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
Click to expand...
Click to collapse
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
yes and i should add your method was very effective ! thanks
what threw me off initially was not finding the fastboot.exe which was in a different folder and the usbdriver - which needed to be installed separately and can be found by launching SDK manager, selecting Available packages-Third-party Add ons-Google Inc - Google USB Driver Package revision 4
mughalgxt said:
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
Click to expand...
Click to collapse
Thanks!!!
This totally worked!
vokhoa408 said:
Thanks!!!
This totally worked!
Click to expand...
Click to collapse
Is this thing getting Ice cream sandwich?
that might solve all these problems.
Samsung Galaxy Tab 10.1 boot loop
Edit: *Fixed!* Ok, so here is my advice to all you other noobs who bricked your tablet, be AWARE that your tablet actually is conscious, it chooses when it wants to work. Just do everything it says on here, all the fixes I have listed, reboot a bunch of times, yell at it, and when you cry a true tear of pain and remorse, and it splashes down on the surface, it will recognize this and all of a sudden work. Booted to 3.0.1 and going to update, that all that is holy.
Hi Guys, I am having the same problem and need some expert advice please, I have a Samsung Galaxy Tab 10.1 with Android Honeycomb 3.1, running Windows XP Pro SP3
I've gone over every solution to this problem on xda over two days and none have worked for me, either that or i'm not doing it correctly.
I successfully rooted my Tab a few days ago, then tried to install a 'boosted' theme and everything is messed up now. When I boot it just hangs on the samsung loading screen, and it reboots to the same screen.
I have tried wiping data/factory reset in cwm
I have tried wiping cache partition
I have tried running Odin through downloading mode
I have adb and fastboot installed on my computer
I have Samsung Android adb interface driver in Device Manager
I have PDAnet installed
When I boot holding the volume down and power button to get the two options, the only two options I have are the Odin Downloading green guy on the right, and an icon with a box and an arrow coming out of it that takes me to CWM on the left.
So I cannot choose fastboot mode on the Tab, when I try to run 'fastboot flash system new.img' through cmd.exe it just says < waiting for device >
I"m a total noob to this and should have left well enough alone when I successfully rooted it, i'm sure I must be just missing a small step, if I could get a bit of guidance it would be greatly appreciated, thanks.
So I've been playing around with the Nexus Q, trying to build custom ROMs for it, but ran into a bit of a snag last night when I flashed a new kernel and somehow lost xloader and uboot. Luckily for us Google was kind enough to leave a flag on in the hardware that boots up the device into diagnostic mode for 2 seconds prior to loading xloader (if it can). When you plug the device into your computer and then power it on you'll always see a new device pop up called "OMAP4440" very briefly. This is the serial console that the CPU sets up to allow flashing when the flasher (fastboot) is broken.
In order to use this emergency recovery mode you'll need to download the OMAPFlash application that can be found here: http://goo.gl/iRvRk
That package contains drivers for the OMAP4440 device (the driver is labeled OMAP 4460 when you install it) and installing it can be a bit tricky. Since you only have 2 seconds to install the driver you'll have to have the Device Manager open and ready to double click on the OMAP4440 device as soon as it pops up. From there you can click Update Driver and install it from the usb_drv_windows folder. The device will go offline while you're in the process but when you plug it back in again Windows should find the driver you just installed. NOTE: I had some problems with Windows trying to search Windows Update even after installing the driver and had to click on the cancel link in the driver installation dialog.
Now that you've got the driver installed we can use OMAPFlash to get the Q back into a working state. The package I linked to above contains definitions for the Galaxy Nexus (tuna) but just so happen to work on the Nexus Q. In a Command Prompt run the following command in the directory you extracted the files:
Code:
omapflash -v -t 60 -2 -p OMAP4460_TUNA_8G_HS_ENG fastboot
An explanation of the flags:
-v = Verbose
-t 60 = Timeout: 60 seconds
-2 = Upload and execute the 2nd boot ROM
-p OMAP4460_TUNA_8G_HS_ENG = Device configuration (8G = 1GB of RAM)
fastboot = Boot the device into fastboot mode
Run the command then plug in the device. OMAPFlash will see the device come online and send the 2nd boot ROM to boot it into fastboot mode. If everything goes well your Q will turn completely red and you'll now have a fastboot device plugged in to your system.
From here "fastboot flash" all the partitions to restore your device to its former glory (using the img files from the factory ZIP):
Code:
fastboot flash xloader xloader-phantasm-ian67k.img
fastboot flash bootloader bootloader-phantasm-steelheadb4h0j.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
My lesson learned: don't flash the "boot" partition until you've tested it first with "fastboot boot boot.img"
Great work! Does this work with the gnex too?
animal24 said:
Great work! Does this work with the gnex too?
Click to expand...
Click to collapse
The instructions and OMAPFlash package were actually taken from a GNEX thread (the GNEX is nick-named "tuna" )
OP updated to include a working download URL.
Great to know, maybe it could be useful for Glass
Sent from my HTC One using Tapatalk 4 Beta
Anyone know about any custom room or kernel or recovery that works on Asus Live (G500TG / Z00YD) ?
I searched everywhere and didn't found anything custom for this model.
Please help.
I need recovery image of this model. Could you provide me a copy of your recovery?
ralp5628 said:
I need recovery image of this model. Could you provide me a copy of your recovery?
Click to expand...
Click to collapse
I'm using all stock.
You can get it from http://dlcdnet.asus.com/pub/ASUS/ZenFone/G500TG/UL-G500TG_ASUS_Z00YD-WW-12.0.0.41-user.zip
I didn't find a recovery image within that file. The only thing I can access is fastboot. My recovery is broken, my system doesn't boot (bootloop). :crying: :crying:
personal HELLO I also need recovery.img Asus Live (G500TG) Z00YD
I've managed to extract the system files (and kernel) from the zip, but no luck in flashing it back using fastboot. I think the problem is in the conversion from raw image to sparse (that fastboot uses).
To extract system raw ext4 partition from zip:
http://forum.xda-developers.com/and...-conver-lollipop-dat-files-to-t2978952/page11
To unpack boot.img:
http://forum.xda-developers.com/showthread.php?t=443994
The idea now is trying to boot from a ramdisk in the pc, to start adb service.
Guys, I figured out how to reverse the situation of hard brick.
1) First you need to download the kernel source code on the asus website. The file name is: ASUS Live (G500TG) Kernel Code (V12.0.0.26). Here is:
http :// dlcdnet.asus .com/pub/ASUS/ZenFone/G500TG/G500TG_Kernel_V12_0_0_26.zip?_ga=1.213911127.1348745149.1467264204
Inside it there are the images of all partitions, including scatter file.
2) You will need to download a program called SP Flash tool. Here: http :// spflashtool .com/. I'm currently using v5.1628
3) Open the tool flash sp as administrator (on Windows) or administrator privileges (using sudo on linux).
4) Extract the downloaded file and select the scatter file in sp flash tool.
5) Select download only.
6) Leave the phone without the battery for 30 seconds before connecting it to your computer. Put the battery again. Holding the - button (lower volume) connect it to the computer. Wait a bit and release the button. Click download in flash tool sp.
7) Wait until all the transfer is completed. After finishing connect the phone and put it to charge on power supply.
no select format+download, possible DTV problem in upgrade for new version
Alguém saber fazer alguma modificação no asus live? Bota outra rom, qualquer coisa? Entre em contato cmg 75988302133
ralp5628 said:
Guys, I figured out how to reverse the situation of hard brick.
1) First you need to download the kernel source code on the asus website. The file name is: ASUS Live (G500TG) Kernel Code (V12.0.0.26). Here is:
http :// dlcdnet.asus .com/pub/ASUS/ZenFone/G500TG/G500TG_Kernel_V12_0_0_26.zip?_ga=1.213911127.1348745149.1467264204
Inside it there are the images of all partitions, including scatter file.
2) You will need to download a program called SP Flash tool. Here: http :// spflashtool .com/. I'm currently using v5.1628
3) Open the tool flash sp as administrator (on Windows) or administrator privileges (using sudo on linux).
4) Extract the downloaded file and select the scatter file in sp flash tool.
5) Select download only.
6) Leave the phone without the battery for 30 seconds before connecting it to your computer. Put the battery again. Holding the - button (lower volume) connect it to the computer. Wait a bit and release the button. Click download in flash tool sp.
7) Wait until all the transfer is completed. After finishing connect the phone and put it to charge on power supply.
Click to expand...
Click to collapse
I don't get it, Where i put the extracted folder from the kernel source?
You need to extract the G500TG_Kernel_V12_0_0_26_zip.zip file and with the SP Flash Tool point to the scatter file inside the extracted folder. It will load all the partitions you just extracted.
ralp5628 said:
I didn't find a recovery image within that file. The only thing I can access is fastboot. My recovery is broken, my system doesn't boot (bootloop). :crying: :crying:
Click to expand...
Click to collapse
You fixed it?
vitorMndC said:
You fixed it?
Click to expand...
Click to collapse
Yessssss!! A long time ago.
This is an guide for when you bricked your ZTE Blade V9, or you destroyed OS without being able to flash with recovery mode(go to step 9).
There are some hacked webservers with articles and shady downloadlinks about this topic, use brain.
I think it can work with an locked oem, because i locked it at some piont earlier.
If your phone isnt showing up as device, give it 1-2 minutes.
Your Phone works even when its showing a black screen.
You do that on your own risk, Iam no ZTE developer.
1. Read the guide, know what you are doing.
2. Download "ZTE Terminal Software", "adb,fastboot,emmc", "ZTE drivers", Stock Rom (update.zip).
Also some "aboot" chinese-factory-testing-firmware which at least gets the phone booting (emmc_appsboot.mbn) from unofficialtwrp at page zte-blade-v9-twrp-3-2-root.
3. Prepare you stock system.img file from the stock rom to flash later. Get an dat to img converter (I used sdat2img.py [email protected]) and extract the img. Rename it to system.img.
4. Boot phone in download mode, the display may be dark but its there ... depends on your damage. Power + Vol- (If it wont work, try starting it normally)
5. Run PortManager from Terminal Software.
6. See COM4(DIAG) -> if anything other adjust drivers in Device Manager. "ZTE 3G Phone AT" should be the right one. There are also some Qualcomm usb drivers which work.
7. Select Port from PortManager as LINE1 USB in "ZTE Terminal Software".
You should now see COM3(DIAG) in ZTE Terminal Software.
8. Use emmcdl on COM3 to flash. Exclude recovery if you have a working/modded one.
I used the original recovery from the stock rom. (emmcdl -p COM3 -f prog_emmc_firehose_SDM450.mbn -b aboot emmc_appsboot.mbn & emmcdl -p COM3 -f prog_emmc_firehose_SDM450.mbn -b recovery recovery-orig.img)
9. Boot phone in recovery mode. Power + Vol+
10. Select "Reboot to bootloader".
11. Find your phone in ">\ fastboot devices".
12. Get the flashscript from file "\META-INF\com\google\android\updater-script" in the stock firmware "update.zip".
Get all extract commands like "package_extract_file("lksecapp.mbn", "/dev/block/bootdevice/by-name/lksecapp");" ;
13. Transfer them into fastboot flash commands and reflash all partitions. (exclude recovery if you have a working/modded one)
Flash your system.img file (step 3) to "system" .
If needed do the same with "vendor".
14. unlock oem.
15. Try restarting your Phone.
16. ???
17. Success !
18. Disable any updates from ZTE, update 1.4 will go good but 1.5 bricks the phone.
18.2 I updated to 1.5 and bricked the phone, because its a "mayor update".
18.3 Follow steps 4 to 8 and only flash the emmc_appsboot.mbn from the STOCK ROM .
19. Do a backup.
Known bugs:
- Wifi cant start -> try reflash (flash system first or including "vendor") or use simcard and hope that ZTE Android update will fix it.
- oem seems locked and unlocked at the same time - ?
Greetings
-deleted-