Related
[POSTED IN THE WRONG FORUM. REPOSTED @ http://forum.xda-developers.com/showthread.php?t=1174493]
Hello Folks,
I seem to have a problem and I can't find an answer in the forums.
I rooted my Asus Transformer with Android 3.1 using this method: http://forum.xda-developers.com/showthread.php?t=1125714
I only rooted the Transformer, I didn't install CWM. Everything was working fine until my overenthusiastic wife updated the tablet with the 8.4.4.11-20110711 update. Suddenly my tablet was unrooted again. I thought "No problem, no harm's done, I'll just reinstall the stock 3.1 and then root the device once again and just leave the new update for what it is for the moment."
The problem is that I can't get into APX mode anymore. When I try to start the device with vol+ and the power button, nothing's happening. Both buttons are working fine (neither's stuck). I thought that the device might just be showing me a blank screen but when I press and hold vol+ and the power button for 5, 10 or 30 seconds then wait 30 secs and start adb.exe it says my device isn't connected.
When I press vol- and the power button I do get the option to wipe all my data and factory reset (which I tried and is working).
When I press vol- and the power button then vol+ when it's booting to get into RCK (recovery kernel mode) I get a droid image with a yellow triangle with an exclamation mark. Nothing happening.
Anyone got a clue what's going on and or how I can solve this issue?
The Transformer is working fine besides not being able to get into APX mode btw. I can use it, just can't root it anymore.
same situation here, just bought my eeePad today, updated to .11 version....now trying to root but can't figure out how...
I'm having the same problem. Brand new transformer, rooted it, and now I can't get it to boot past the splash screen. Tried putting it back into APX mode, and it doesn't work. Anyone find a solution to this?
I didnt even root mine and i have this ****ing problem -.-
Same problem..
You'll notice if you watch the device manager on windows, it flashes a refresh but the device doesn't show up. Looks like it's trying to work but doesn't catch..
SSame here after using Brk's on my 3.2 B70 tf101.
Same here. 3.1, rooted, CWM.
Same here on an Asus running Android 3.2.
Serial number B60KA.
Build number on mine is 8.6.5.9-20110816.
Anyone find a solution to this?
My friends tablet is at HTK75.US-8.6.5.13-20110925 and I just got it in to APX mode.
I had the Transformer turned off and plugged in, held vol up + power until I hear the first US notification noise and released the two buttons. The searching for drivers screen came up and it installed "Nvidia Bootloader Recovery" And now my safe to eject calls it APX.
I found if you hold the power and volume up for too long it messes things up.
Any news anyone? I would love to know how to do get into APX mode. The volume + and power is not working for me like the others (did it all conceivable ways).
APX already on
Hi, I solved this problem very easy.
Just connected my eeePad, installed the APX driver after Volume up and Power on Button and it was working. You will see nothing on eeePad screen. Just check the device manager on your computer.
it all started when i wanted to try the Stock Deodexed T959VUVKG4 with Root, and i went to the red recovery i had, voodo recovery, and i did all the unmount, mount, and all that good stuff.I flahsed the room waiting for the process to finish but i got stock on the galaxy logo. when i went back to the post, i read that recovery didnt work for some reason, so i decided it was time for me to restore my phone using odin, but my pc doesnt recognize my phone anymore, whenever i plug in the cable to the pc, its like nothing has happened, i have installed all of the usb drivers ive seen on the web, but nothing seems to work, any suggestions???/
Did you forget to disable voodoo in CWM and then reboot to un-convert the file system before you started flashing?
to get into download mode, are you sure you are holding both volume up/down buttons down while you plug in the usb?
the kg4 doesnt have the bootloaders, so you should be able to get into download mode using the three button combo.
i disabled voodo lagfix but i did not reboot the phone instead i flashed the room right after. and i am holding both volume up/down buttons down while i plug in the usb and i see the download pictures and everything
and what do i do if my pc doesnt recognize my phone???
djj.p said:
and what do i do if my pc doesnt recognize my phone???
Click to expand...
Click to collapse
I had an issue where my pc would not recognize my phone in download mode after flashing the original 2.3.4 posted by chadster. I finally got it to recognize it by installing all the drivers used with heimdell. Hope that helps.
Sent from my SGH-T959V using XDA Premium App
ive tried that but the only driver that my pc recognizes is my wireless driver.thanks for the help everybody.
ok. drivers are sometimes a problem. restart the computer and then reinstall the drivers. then plug your phone into a different usb port from what you had it and go into download mode. let me know if that works.
i will try again with Heimdall to see if it works
Can you try taking the battery out for 30secs open odin plug the usb in the phone hold vol up and down then slap the battery in while still holding keep holding it and if a com sign comes up in odin flash it even if screens blank
Sent from my SGH-T959V using XDA Premium App
it doesnt work
i still have the same problem with the usb drivers, does anybody know how to fix it?
Try uninstalling all your phone's usb drivers, then go to the device manager in system properties, right click on your USB controller, and uninstall the device. Then reboot your pc, and let windows find and reinstall the USB controller. Then reinstall the samsung usb drivers, and see if that works.
I had the same issue once.
I had the same issue before and was able to fix it by rebooting the phone and letting GB boot up. I then turned on debugging mode and plugged the phone into the pc. I then installed the hemi drivers and windows installed the device and everything worked after that. From what I've found, after you flash GB, sometimes it wont recognize the device anymore, so putting the phone into debug mode after booting seems to force it to use the correct drivers. Hope this helps!
I'd try the fevers then hold up and down and put USB cord in
Sent from my SGH-T959V using XDA App
Hi, this situation is kind of strange and I hope it's just the battery and not the whole goddamn phone.
What I'm dealing with at the moment is:
The phone doesn't boot
When plugged onto charger or USB cable it boots but stuck at Google logo after a blink and stays there. Also, Home, Back and other buttons are lighten.
When "forcefully" put into fastboot mode, e.g. after plugging it onto USB and instantly pressing Vol Up + Power it stuck there as well, volume rocker no more response neither does the power button. Also, I notice there are no commands at the end like "USB int" etc we see normally.
Fastboot or ADB returns no device found
Please help. I personally believe it could be due to battery, what do you guys think?
Thank you.
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
ej8989 said:
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
Click to expand...
Click to collapse
Thanks. My OS is Windows 8.1 Update 1. The last thing was to install UPDATE-SuperSU to root so that I can install ROM Manager to update Recovery but the installation was aborted so I attempt to flash it via Fastboot with success. Then, wanted to install SlimKat but it couldn't let me mount USB storage so that I can put the .zip file. I, then stupidly click on install via ADB but didn't know how to go back so I pulled the battery and powered up; used ADP push command to transfer said the file, but again for some reason I had to pull the battery and since then I am in above position.
Sent from my XT1032 using Tapatalk
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
BaghiXDA said:
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
Click to expand...
Click to collapse
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Setting.Out said:
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Click to expand...
Click to collapse
The problem is, even the Toolkit doesn't recognize the device no matter what. Even the keys for ODIN don't work, aren't they Home+VOL+ and Power?
EDIT1:
Kept plugged in for little longer as suggested but it heats up (it's too hot here) so I plugged out. Going to be running it off of Linux and lets see how it goes. :fingers-crossed:
EDIT2:
Tried Adam's UnBrickable method on Linux and even that couldn't find device. But that was to be expected since Adam clearly mentioned in his post that this tool isn't for those who see anything on their screen.
Whelp! Currently I can only see I:\ drive in device manager and that's all under portable devices and that's all. I see the same even in BIOS boot options, it's listed as "Google".
Guess need to close this thread now.
I've broken my phone! I was rooted, and was installing a custom rom. It worked fine for a few hours, and now the phone won't boot up in normal, recovery or fastboot modes. All I get is the android logo and then a white screen for a few seconds, and this repeats until i get fed up and turn it off again.
My device is a Vodafone 785 and my pc is running Windows 7 with the latest drivers installed and updated.
When I plug the phone into the computer, it tries to register but the flashtool says the device is not recognized, so I can't re-install my recovery image.
I've been at this for about three weeks now, and I cannot for the life of me figure out how to get this working again. Can someone please help?
coling24 said:
I've broken my phone! I was rooted, and was installing a custom rom. It worked fine for a few hours, and now the phone won't boot up in normal, recovery or fastboot modes. All I get is the android logo and then a white screen for a few seconds, and this repeats until i get fed up and turn it off again.
My device is a Vodafone 785 and my pc is running Windows 7 with the latest drivers installed and updated.
When I plug the phone into the computer, it tries to register but the flashtool says the device is not recognized, so I can't re-install my recovery image.
I've been at this for about three weeks now, and I cannot for the life of me figure out how to get this working again. Can someone please help?
Click to expand...
Click to collapse
Hi, try this:
http://forum.xda-developers.com/android/help/vodafone-smart-4-mini-killed-vodafone-t2869185
Yes I tried that one and most of the other threads about this damn phone. It won't boot in recovery. I've tried Power button and volume up AND Power button and volume down. All I get is android logo for a few seconds and white screen for another few seconds and this will loop until the end of time. Using SP Flashtool, the computer won't recognize the device when I plug in the USB with either the battery removed or inserted into the phone.
coling24 said:
Yes I tried that one and most of the other threads about this damn phone. It won't boot in recovery. I've tried Power button and volume up AND Power button and volume down. All I get is android logo for a few seconds and white screen for another few seconds and this will loop until the end of time. Using SP Flashtool, the computer won't recognize the device when I plug in the USB with either the battery removed or inserted into the phone.
Click to expand...
Click to collapse
Unfortunately, it sounds like the device may be unrecoverable.
I'm not for giving up. Somehow I'll find a way to fix this thing. :fingers-crossed:
coling24 said:
I'm not for giving up. Somehow I'll find a way to fix this thing. :fingers-crossed:
Click to expand...
Click to collapse
Good luck!
Hi!
I have tried to install a custom rom, but there was an error. When I tried to boot back to bootloader mode, the qualcomm logo started blinking and the device is vibrating.
Tried to connect to pc, but I don't see any device in COM Ports in the device manager, also MSM tools says waiting for the device.
If I connect the cable while I am pressing the both volume button, I hear the sound from the pc that something is connected, but after a few seconds the device disconnects.
Can you help me?
Got the same problem installing a wrong firmware, probably. I'm hoping for someone knowing how to solve...
That was easy. Unfortunately I had to format the phone entirely (MSMTool), but it's back with the living.
Install Qualcomm EDL drivers
Download an MSMTool release for OnePlus 8T
Enter in EDL Mode. With the phone connected to a computer running Windows, press volUp + volDown right when you see the Snapdragon logo. The phone will stay with screen off
Follow the usual flashing procedure with MSMTool
Thanks, I just had to install the Qualcomm drivers exe file. After that it appeared in device manager.
Livingsilver94 said:
3. Enter in EDL Mode. With the phone connected to a computer running Windows, press volUp + volDown right when you see the Snapdragon logo. The phone will stay with screen off
Click to expand...
Click to collapse
Nothing happens when i press that. phone keeps on vibrating and flashing the logo
UPDATE: Got a different computer and it worked