I used this guide to root my TF and install CWM. But I have never been able to boot into Recovery. I still get the green Android with the exclamation mark.
I thought I would retry running the cwm.bat again from that guide to see if maybe it just didn't install correctly, but now I can't get ADB Devices to show my device when it's in APX mode. With the device on I can get ADB Devices to show it, but when I power off, and then do Power + Vol Up it boots into APX and my computer makes the sound that a USB was attached... but it never shows up in ADB Devices.
So, I can't update CWM, I can't reinstall it... what do I do?
Any takers?
Related
OK, so I flashed the wrong ROM today (I9000HVJH1) and the phone now boots into recovery everytime the battery is inserted. I have tried all the tricks to get back to download mode with no luck. The device is recognized by the USB in recovery and was able to push the root update file but can not get it to apply sdcard:update.zip (just sits there and doesn't respond to the power button unless i hold it). Interesting thing is when I plug the USB in and insert the battery, it never goes to charging, it boots into recovery.
Tried:
1. Plug USB
2. Hold vol up (and down but the keys are now backwards in recovery)
3. Insert battery
and
1. Power down (removed battery)
2. Hold vol up + down + power
and
1. Hold vol up (and down too for a few hundred times)
2. Hold power until Samsung logo then release
and
all combo's with and without the USB plugged into the phone.
Beside the tricks shown on the forum, can anything think of a way to get this phone into download mode instead of it constantly booting into recovery? ADB see's the device, just no root access or knowledge of how to get it to apply the update.zip that would root the device.
Thanks~!
http://forum.xda-developers.com/showthread.php?t=741027&page=3
Wrong section. This belongs in general...
Sent from my messenger rabbit
UPDATE!!
After going to T-Mobile on Monday to buy a new Vibrant, I started to think about how to get the "bricked" one working again. I was able to admit defeat for long enough to get a new one but was bothered that I couldn't fix my old one.
I started to think about what I could and couldn't do with the "bricked" one. It would constantly boot start to Android Recovery with error about CSC. No matter what combination of buttons pressed, held, release, the darn phone would never get back to a download mode. Since it could never boot into the OS, ADB seemed impossible. The GOOD news (as it turns out) was when it booted into recovery if I disconnected the USB and reconnected, my computer recognized it and Odin saw it on COM10. I began to look at the batch file for the one click root and noticed the line "adb reboot download". I had messed with ADB the day I screwed up the phone but always tried to do commands after typing "adb shell" and without super user access, I felt doomed. Last night I thought what the heck and powered up the old Vibrant and it went straight to recovery. After another 45 minutes of trying to manually put it into download mode I opened a command prompt and typed "adb reboot download" and the freaking phone rebooted into download mode!!!! So after flashing back to stock I now have fixed the phone
So for anyone who can't get their Vibrant to stop rebooting itself into recovery here is a simple breakdown of what I did.
1 - Power up phone (mine went straight to recovery)
2 - Un-plug the USB and plug it back in (computer should recognize the connection)
3 - Open command prompt and change to the directory that has adb.exe
4 - Type "adb kill-server" and then enter
5 - Type "adb reboot download" and then enter
6 - Phone should reboot into download mode and ready to flash
Make sure you have Odin open with the pit and pda file loaded as there seems to be only a short window of time in which the phone will accept the download and get the status bar moving. If you wait too long, repeat the steps above and start the flash quickly.
I hope this helps someone out that might be experiencing the same problem as me.
I am trying to get clockwork recovery installed and when i try to boot in fastboot by pressing the power button and holding volume down it loads up a screen that has a yellow triangle and a usb looking thing. I click over to the usb looking icon and it loads up some words on the left hand side and some of it says fastboot and says unlock mixed in it,,,, then when i go to my computer to type in cmd and then fastboot devices nothing shows up??
I rooted using ADB so i know i have some type of connection and downloaded the kies drivers,,,any help someone could give to get clockwork loaded please.
So I've had the transformer for a while and I finally took the plunge and followed this guide http://forum.xda-developers.com/showthread.php?t=1125714 to root. I got to step 4c, meaning I successfully ran root.bat and cwm.bat and rebooted afterwards. When I rebooted however, the tablet stayed on the "asus powered by nvidia" screen for a very long time. I decided to shut it down, but it immediately started back up again and stayed on that screen again. The only way to stop it was to put it into APX mode so it doesn't drain my battery.
I'm pretty sure I followed all the steps correctly, and I was on the latest .11 OTA update. Help please?
EDIT: I reread the first few sentences of the guide and realized I missed a very important step... I forgot to extract 84411.zip into the "root" folder of tf_rootkit_31, which means I have no boot or recovery image. Is there any way I can recover from this?
Just start over with the correct files in place.
The boot.bat file will write those files and you should be good to go.
With APX mode the transformer is basically un(software)brick able.
sassafras
I tried starting over but I can't seem to boot into APX mode. When I turn it off and then hold power/vol up, device manager refreshes but APX mode doesn't show up. the device also isn't listed under adb devices in the command prompt...
Vertiginouz said:
I tried starting over but I can't seem to boot into APX mode. When I turn it off and then hold power/vol up, device manager refreshes but APX mode doesn't show up. the device also isn't listed under adb devices in the command prompt...
Click to expand...
Click to collapse
When you say it doesn't enter APX mode, is it still boot looping? When this happened to me, it took about 10 seconds just holding power and vol+ before I heard the USB connected sound.
Vertiginouz said:
I tried starting over but I can't seem to boot into APX mode. When I turn it off and then hold power/vol up, device manager refreshes but APX mode doesn't show up. the device also isn't listed under adb devices in the command prompt...
Click to expand...
Click to collapse
adb won't show the device when it is in APX mode. If you're on windows you need to check your device manager or connected usb devices to see if it's there. The screen on the TF should be black until you start the rooting proccess.
If it is bootlooping just keep power and vol+ unti the screen goes blank - can take a few seconds extra.
Also make sure you use the correct 84411 zip - using the US version on a WW TF will make it go into a bootloop - I suspect the same will happen the other way around.
GL
Thanks for the responses, I'll try again when I get home in 3 hours. also when I say bootloop, it's not turning on and off repeatedly, it just stays on one screen until I turn it off, then it starts back up by itself.
Well it finally worked, I had to reinstall the APX drivers first though, thanks has been given!
Hi all,
I have just recently rooted my 306SH, the rooting process was fine. The problem started when I flashed an incompatible twrp image. Now I can't boot into anything it seems, no recovery, no fastboot and the power button will show only the logo screen. If connected to a power source the red led light will stay on even if unplugged. The device can be completely shut down and the red light off if I hold the down+volume and power down for few seconds.
I can connect it to my computer via usb by holding up+volume and power (green led light) . I installed google usb driver onto the android device and it stays connected for about 30 seconds to 1 minute. I tried using command prompt and SDK by typing "adb reboot recovery" but get an error message "error: device '(null)' not found.
Things I have installed on my computer:
(ADB, fast boot and drivers) https://forum.xda-developers.com/showthread.php?p=48915118#post48915118
SDK Platform-tools
306SH:
Google USB driver
Is there anything I can do from my computer? I was thinking maybe I can flash in an image to replace it. And also my sim card pops out and can't be set back in, is this due to the incorrect flashing?
Any help or input is greatly appreciated, I've been working on this for a while and is getting no where.
I installed LineageOS 14.1 but I was having some blue screens so I decided to go back to stock ROM but I had a brainfart and rebooted after wiping everything except microSD, and now I can't boot my phone normaly, nor enter recovery mode or download mode.
What is happening with TWRP recovery mode is that it seems to load properly but then it doesn't give me options or anything it just starts formatting cache or something for like 2 seconds and then just tries to reboot normally, but there's no OS so it just gives me a blue screen(im not at home right now but im panicking, i will upload a video for better understanding in a couple hours).
And with download mode it just stays on the charging screen.
Did I just brick my ****ing phone? Im on the verge of tears, I have been watching videos and reading for the past 2 hours and nothing seems to help
Patala1 said:
I installed LineageOS 14.1 but I was having some blue screens so I decided to go back to stock ROM but I had a brainfart and rebooted after wiping everything except microSD, and now I can't boot my phone normaly, nor enter recovery mode or download mode.
What is happening with TWRP recovery mode is that it seems to load properly but then it doesn't give me options or anything it just starts formatting cache or something for like 2 seconds and then just tries to reboot normally, but there's no OS so it just gives me a blue screen(im not at home right now but im panicking, i will upload a video for better understanding in a couple hours).
And with download mode it just stays on the charging screen.
Did I just brick my ****ing phone? Im on the verge of tears, I have been watching videos and reading for the past 2 hours and nothing seems to help
Click to expand...
Click to collapse
To boot into download mode, you must first turn it off then connect your phone to pc and then long press power up button.
As with the twrp formatting cache or something like that, you must have downloaded a buggy version. For now, if you have a pc nearby try to boot into twrp with adb.
mayankjet said:
To boot into download mode, you must first turn it off then connect your phone to pc and then long press power up button.
As with the twrp formatting cache or something like that, you must have downloaded a buggy version. For now, if you have a pc nearby try to boot into twrp with adb.
Click to expand...
Click to collapse
Download mode still isn't working with the computer im trying, are you saying I just have to turn it off, plug it into the pc(charging screen appears), and just hold power button alone until I get to DL mode? Does my computer need a specific driver already installed for this?
And how would I go about giving my phone commands with adb if I can't boot it into anything? Should my pc recognize the device and be able to use adb when it's in the blue "Subsystem Crash" screen, or maybe when in the first 2 screens before booting into recovery where you have to press "Yes" twice, or when? Maybe when it's charging?
Thanks a lot for the help
Patala1 said:
Download mode still isn't working with the computer im trying, are you saying I just have to turn it off, plug it into the pc(charging screen appears), and just hold power button alone until I get to DL mode? Does my computer need a specific driver already installed for this?
And how would I go about giving my phone commands with adb if I can't boot it into anything? Should my pc recognize the device and be able to use adb when it's in the blue "Subsystem Crash" screen, or maybe when in the first 2 screens before booting into recovery where you have to press "Yes" twice, or when? Maybe when it's charging?
Thanks a lot for the help
Click to expand...
Click to collapse
Yes, you need to turn off your phone and plug the usb cable in your phone while holding volume up button until it goes into download mode( you must connect it to a pc or laptop). Also, you don't need specific drivers for that.
To boot into twrp with adb, you must first boot into os, or boot into twrp with hardware keys, assuming you can't do any of these then your only option is flashing a new kdz via download mode.
Edit: You need adb drivers installed on your pc if you're going to use adb commands on your pc.
mayankjet said:
Yes, you need to turn off your phone and plug the usb cable in your phone while holding volume up button until it goes into download mode( you must connect it to a pc or laptop). Also, you don't need specific drivers for that.
To boot into twrp with adb, you must first boot into os, or boot into twrp with hardware keys, assuming you can't do any of these then your only option is flashing a new kdz via download mode.
Edit: You need adb drivers installed on your pc if you're going to use adb commands on your pc.
Click to expand...
Click to collapse
Fixed it, thank you a lot my friend, saved my ass
Patala1 said:
Fixed it, thank you a lot my friend, saved my ass
Click to expand...
Click to collapse
:good:
OK I have added the fix in guide