I tried rooting my A500 this morning. I've done it before, but this time it didn't seem to go as planned. I was trying to root with http://http://forum.xda-developers.com/showthread.php?t=1546593. It didn't work, told me to reboot, and now I'm stuck with a black screen, the power button light is flashing like it normally does while it's powered on, and holding the power button down won't power it down. Help...?
natoe33 said:
I tried rooting my A500 this morning. I've done it before, but this time it didn't seem to go as planned. I was trying to root with http://http://forum.xda-developers.com/showthread.php?t=1546593. It didn't work, told me to reboot, and now I'm stuck with a black screen, the power button light is flashing like it normally does while it's powered on, and holding the power button down won't power it down. Help...?
Click to expand...
Click to collapse
Install adb.
Open up a command line (or *nix terminal emulator)
run:
adb devices
If you get a response from the device, you may have a chance. If not, there's always the fun way using APX mode.
apapousek said:
Install adb.
Open up a command line (or *nix terminal emulator)
run:
adb devices
If you get a response from the device, you may have a chance. If not, there's always the fun way using APX mode.
Click to expand...
Click to collapse
What's APX mode and how do I use it?
Related
Ok I've looked everywhere, maybe not well enough but I have and I can't find the answer to my question. I installed the new official 2.2 on the 10th when it came out in canada here. My phone has worked "ok" for the past 2 days. (lots of new force closes and some major lag in some spots that didn't happen in 2.1) but that's besides the point. Today i was trying to set up a new wallpaper and all of a sudden the screen started flashing on and off. I couldn't do anything to stop it except pull the battery. Now when I turn on the phone it just flashes the opening screen that says "Galaxy S blah blah". and the only way I can stop that is pull the batt. I've tried hard resetting and all that but it always gets stuck at the openning screen. Now I'm still noobish to android stuff. Was too scared to flash anything before the official so if you have any advice that involves other programs/pc i'd appreciate a point in the direction of a walkthrough.
I'd hate to have to send it in and wait the 2 months it takes samsung canada to get it back to me.
Thanks.
http://forum.xda-developers.com/showthread.php?t=732458
tried that, can't get into download mode. as soon as i plug it in it starts looping the boot screen.
canadianrider said:
tried that, can't get into download mode. as soon as i plug it in it starts looping the boot screen.
Click to expand...
Click to collapse
Look up the "jig" solution. That will be guaranteed to set your device on Download Mode.
It was the same problem with my Vibrant. Solved with JTAG controller. But you'll waste your warranty in that way. Try jig solution first
Adb?
Sent from my SGH-T959 using XDA App
ok i have android sdk/adb from when i pulled screen shots with 2.1 ... how could i use that to try and boot my phone
canadianrider said:
ok i have android sdk/adb from when i pulled screen shots with 2.1 ... how could i use that to try and boot my phone
Click to expand...
Click to collapse
option 1
METHOD 2: STUCK AT VIBRANT SCREEN:
(and are not able to use vol+ vol- methods to access downloader/recovery)
You will need the samsung ADB drivers installed for your phone as well as ADB...
ACCESS DOWNLOAD MODE
1) remove back cover and take our sim card and sd-card.
2) take out the battery
3) hold ALL 3 buttons down at the same time. (Vol +, Vol -, Power)
4) while holding down those 3 buttons put the battery back in
5) continue holding all 3 buttons until the vibrant disappears and reappears... once it reappears, release all 3 buttons
6) Setup ODIN and get it all setup and ready... (if you are flashing your phone via odin)
6) now connect your phone to your pc via USB cable
7) open a cmd prompt and navigate to the folder with ADB and type ADB REBOOT DOWNLOAD
8) Your phone will reboot into the download screen... go back to ODIN - A com port should now appear for your phone...
9) Click start and wait for your phone to do its thing
Option 2
***First you must have ROOT***
Download Terminal Emulator from the Market
open terminal emulator
**you may need to change to default android keyboard for proper inputting
1.) type "su" and press enter
a dialog box will appear asking for root access and say yes (obviously)
2.) type "reboot recovery" and press enter
at that moment, ur phone should reboot into Download Mode to load Alternate firmwares for like Eugene's Vibrant4 ROM etc......
this it what it should look like...
#su
#reboot download
Option 3
or you can download and install quick boot from the market which you then can make a shortcut to reboot into recovery with just one click
Sometimes it takes more than one try to get into download mode. I just take the battery out for a little while. Put it back in and hold only the volume up and down buttons while it is off and plug in the USB cable.
One thing though, when holding down the up and down volume buttons, it is very easy to mistakenly press the power button because it is exactly opposite of it.
Hey, I just tried this for fun, but can't figure/find what's going on. When I power up my MT4G, I pressed "Volume Up", then pressed "Power". The phone vibrated a couple times, then the upper left LED flashed orange repeatedly. I couldn't do anything from there but pull the battery.
What was going on? Anyone know?
Its strange the light just keeps blinking. I had to pull out my battery.
Sent from my HTC Glacier using XDA App
Okay, so I t went into this mode while the phone was plugged in and the computer was asking for some drivers. I already have the HTC Sync, myTouch 4G, and Android 1.0 drivers, but it still wasn't able to find the ones for this mode? What does this mode do anyways? I have a feeling this is the mode the RUU.exe uses install updates/software on the device. What am I missing? Why will my computer not read the myTouch in this mode?
Its just telling you that you didn't boot into bootloader correctly, so try again. Type in adb devices or fastboot devices in a terminal to see what comes up.
GazaIan said:
Its just telling you that you didn't boot into bootloader correctly, so try again. Type in adb devices or fastboot devices in a terminal to see what comes up.
Click to expand...
Click to collapse
Nothing comes up. The computer recognizes the device, but can't find the drivers. :/
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!
So I have tried just about everything I can find on whats supposed to put a K1 with 3.2.x into Recovery with no luck.
I have held Vol + and Vol - down then holding down power. The unit seems to go to APX but then just boots. I have also tried just Vol - and just Vol + behing held then power, I have tried it without holding power... it just boots unless I never let go o the power button in which case it just turns off...
USB Debugging is on, I tried to use terminal on the device and use the command
adb shell k1recovery
Which I found on the forums as well... no luck. I have the SDK kit installed and updated including version 3.2.x SDK's and no luck. However I am by no means an expert so I may not understand fully how to do this...
I am by no means a complete Noob, I have flash every android phone I have owned which as most here I am sure can attest... we go through a lot of phones. However this is the first time I have not been able to get a device to just go into recovery... and its very frustrating.
I cannot post else where because apparently to many others have abused this privilege, but I have searched around here and done a ton of Google searching even forcing myself through some of the YouTube video's that all talk about getting in but never show it.
I could really use some help, I really just want root and ICS thats all.
Thanks.
CapsuleER said:
So I have tried just about everything I can find on whats supposed to put a K1 with 3.2.x into Recovery with no luck.
I have held Vol + and Vol - down then holding down power. The unit seems to go to APX but then just boots. I have also tried just Vol - and just Vol + behing held then power, I have tried it without holding power... it just boots unless I never let go o the power button in which case it just turns off...
USB Debugging is on, I tried to use terminal on the device and use the command
adb shell k1recovery
Which I found on the forums as well... no luck. I have the SDK kit installed and updated including version 3.2.x SDK's and no luck. However I am by no means an expert so I may not understand fully how to do this...
I am by no means a complete Noob, I have flash every android phone I have owned which as most here I am sure can attest... we go through a lot of phones. However this is the first time I have not been able to get a device to just go into recovery... and its very frustrating.
I cannot post else where because apparently to many others have abused this privilege, but I have searched around here and done a ton of Google searching even forcing myself through some of the YouTube video's that all talk about getting in but never show it.
I could really use some help, I really just want root and ICS thats all.
Thanks.
Click to expand...
Click to collapse
why dont u got some 3rd party apps, like room toolbox?
i just try that, and it has a menu to go to recovery mode.
CapsuleER said:
So I have tried just about everything I can find on whats supposed to put a K1 with 3.2.x into Recovery with no luck.
I have held Vol + and Vol - down then holding down power. The unit seems to go to APX but then just boots. I have also tried just Vol - and just Vol + behing held then power, I have tried it without holding power... it just boots unless I never let go o the power button in which case it just turns off...
USB Debugging is on, I tried to use terminal on the device and use the command
adb shell k1recovery
Which I found on the forums as well... no luck. I have the SDK kit installed and updated including version 3.2.x SDK's and no luck. However I am by no means an expert so I may not understand fully how to do this...
I am by no means a complete Noob, I have flash every android phone I have owned which as most here I am sure can attest... we go through a lot of phones. However this is the first time I have not been able to get a device to just go into recovery... and its very frustrating.
I cannot post else where because apparently to many others have abused this privilege, but I have searched around here and done a ton of Google searching even forcing myself through some of the YouTube video's that all talk about getting in but never show it.
I could really use some help, I really just want root and ICS thats all.
Thanks.
Click to expand...
Click to collapse
The command you used is if you were on adb but you are on the device itself so instead try this:
Terminal emulator:
Code:
su
k1recovery
if it don't work try reboot recovery instead. This always worked for me.
recovery mode
I found that on my K1 to get it in the recovery mode I stood it on its side with the power and volume buttons on top. Then use something flat to push the two volume buttons down together then, while holding them down push the power button. I fought with it before trying this. I just could not do it with my fingers. That gets it in the APX mode.
hello and thanks in advance. I recently installed twrp on my device and somehow deleted entire os. while in twrp I was informed of this but as luck would have it experienced a power outage, phone died and now adb is not finding device. since deleting os is it possible to get comp to locate it? all I get is the blue led and if I try to volume down power to boot recovery ligts go out. I do get a chime saying something is connected to comp but I cannot locate it. any advice would be great.
Have you tried to follow instructions to reflash TWRP? Can you put the phone in bootloader/fastboot mode?
Lostsheep420 said:
hello and thanks in advance. I recently installed twrp on my device and somehow deleted entire os. while in twrp I was informed of this but as luck would have it experienced a power outage, phone died and now adb is not finding device. since deleting os is it possible to get comp to locate it? all I get is the blue led and if I try to volume down power to boot recovery ligts go out. I do get a chime saying something is connected to comp but I cannot locate it. any advice would be great.
Click to expand...
Click to collapse
divineBliss said:
Have you tried to follow instructions to reflash TWRP? Can you put the phone in bootloader/fastboot mode?
Click to expand...
Click to collapse
no all I have is a black screen but but blue led is on. no recovery mode and device not found by way of computer
Try putting it in fastboot mode with this method:
https://forum.xda-developers.com/showpost.php?p=70556152&postcount=712
Does the phone screen show fastboot mode in title?
Let me know what happened.
Lostsheep420 said:
no all I have is a black screen but but blue led is on. no recovery mode and device not found by way of computer
Click to expand...
Click to collapse
divineBliss said:
Try putting it in fastboot mode with this method:
https://forum.xda-developers.com/showpost.php?p=70556152&postcount=712
Does the phone screen show fastboot mode in title?
Let me know what happened.
Click to expand...
Click to collapse
as I stated earlier the only sign of life is the blue led. no screen sound or vibration nor does it seem to have anything but attemptin the adb by buttons did cause the blue led to turn off. its using battery as if smething is running its like a completely clean slate nothing at all
Unclear to me if you tried my post instructions to get into fastboot mode. If that's not working, I'm not sure what can be done other than sending phone to Huawei for repair. Maybe someone else has another idea? Good luck
Lostsheep420 said:
as I stated earlier the only sign of life is the blue led. no screen sound or vibration nor does it seem to have anything but attemptin the adb by buttons did cause the blue led to turn off. its using battery as if smething is running its like a completely clean slate nothing at all
Click to expand...
Click to collapse
Maybe missing something here but if can get to TWRP, power off then on holding volume up, you can flash any rom. Not volume down on my phone to get to TWRP, is volume up.
Good catch on the volume up button.
Original H1611 bootloader unlock and TWRP flashing instructions which cover key sequence to get into TWRP:
https://forum.xda-developers.com/showpost.php?p=69811031&postcount=1
popeye2014 said:
Maybe missing something here but if can get to TWRP, power off then on holding volume up, you can flash any rom. Not volume down on my phone to get to TWRP, is volume up.
Click to expand...
Click to collapse
I cannot get to recovery mode. My computer is not finding device by way of adb. Is there a way to push by way of command prompt and force it on to device?
Lostsheep420 said:
I cannot get to recovery mode. My computer is not finding device by way of adb. Is there a way to push by way of command prompt and force it on to device?
Click to expand...
Click to collapse
No way if you don't have adb working. Again, if you hold volume up button while pressing power on button, then release power on button as soon as you see boot screen, do you get recovery screen?
No screen reaction at all. Only the led when connected by us to computer it seems to charge and led stays lit blue after fully charged and red when still charging. I was hoping maybe there was a shell comand that would maybe push data enough to get into recovery at least.