Im stuck on nvidia logo. With no recovery and OS.
I am planning to go back to stock.
But i cannot connect shield to my laptop. It doesn't connect, it just charging. I tried adb, i tried my device manager but i still got nothing.
Please, if anyone knows a solution on how to connect. Or to go back to stock
How do you know there's no recovery? Did you mess up the partition?
That part, i mean i used fastboot and success, but im stuck. Like its not installed. But when i tried twrp 3.1 it was installed but the problem is it wont touch.
If you can access fastboot, that means you can pretty much re-flash recovery and the ROM. Download the latest recovery image file from the Nvidia download center (it's 5.1). Don't need twrp for that
Related
First off I am sorry for posting this, however I DID use the search tool. I recently got a USA spec Wifi only Xoom. It came with 4.1.1 preinstalled. I have sucessfully unlocked the bootloader.
My problem is this. I cannot gain root or even get CWM installed. I have tried oneclick, i have tried cmd prompt. I have followed every guide I can find to a "T". Is there something missing, is it an issue with Jellybean being preinstalled?
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
airesch said:
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
Click to expand...
Click to collapse
Thanks for the reply, however this is one of the utilities I have tried,..
Here is a bit more info.
I am running windows 7 64bit if it makes a difference. Whenever I get the device into fastboot and try to flash anything, it just hangs at the original fastboot screen. I have let it sit there from 3 hours and eventually I have to reboot it. The Lord AIO Tool you linked just gives me and error message that the device is not a 2.2/2.3 device. If I were at home I would take a screenshot.
Could my bootloader be corrupt? The device still boots up and runs jellybean fine, but I am not loving the stock experience thus far...
Thanks again for the links!
Actually sounds like your drivers aren't right. I will look them up and link them when I get home
Try installing the driver from http://developer.motorola.com/tools/usb_drivers/, rebooting your pc, and try fastboot again. If that still doesn't work, then there may be something wrong with your pc setup OR your Xoom, not sure at that point.
Sent from my SPH-D710 using xda premium
Thanks a million, I am going to try it fresh on my pc at work. Thanks!
That did the trick THANKS A BUNCH!!!!!
Hello,
I tried to get back to the Stock ROM but I then flahed the update JB 4.1.2 through CWM as well. However when I restarted my Tablet I get into a boot loop. The I tried to flash the update.zip through the Acer Stock Recovery, but I cant even get into the bootloader, it just says: Recovery Verified Failed. So i think okay, why dont I try to unlock the bootloader again. I can get into fastboot but adb wont recognize the device, even though the pc seems to install some drivers. Does anyone have an idea what is wrong with my device and/or how I could fix it?
Thank you in advance.
--Update--- Seems that the USB Driver for the Tablet doesnt work on Windows 8
See here :
http://forum.xda-developers.com/showthread.php?t=2046832
Solved. Anyone else with the problem of windows 8 driver ask me
So i got a new T F 300T yesterday and wanted to root it today.
I unlocked it and rooted it successfully. But then I tried installing a recovery. Installed CWM using fastboot. tried booting into it using RCK. It says booting into recovery mode and just reboots to OS. Installed CMW touch, same problem. Installed TRWP since i read that cmw has some problems.Now i used the 1 click root 1.1 to boot into recovery mode. The device now keeps rebooting. IT starts on the asus screen, then reboots again. So im stuck in a boot loop. When I press vlm dwn +power, it doesnt give me a menu anymore , instead it says that its rebooting into recovery mode and reboots again. Im freaking out right now, anyway to recover my device? Or is it 400 bucks down the dran? I dunno why this happened , since i am not new to flashing ROMs and stuff, and ususally test out new ROMs using my GNex. Any help would be appreciated, thanks.
Wiltuz said:
So i got a new T F 300T yesterday and wanted to root it today.
I unlocked it and rooted it successfully. But then I tried installing a recovery. Installed CWM using fastboot. tried booting into it using RCK. It says booting into recovery mode and just reboots to OS. Installed CMW touch, same problem. Installed TRWP since i read that cmw has some problems.Now i used the 1 click root 1.1 to boot into recovery mode. The device now keeps rebooting. IT starts on the asus screen, then reboots again. So im stuck in a boot loop. When I press vlm dwn +power, it doesnt give me a menu anymore , instead it says that its rebooting into recovery mode and reboots again. Im freaking out right now, anyway to recover my device? Or is it 400 bucks down the dran? I dunno why this happened , since i am not new to flashing ROMs and stuff, and ususally test out new ROMs using my GNex. Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Hi there, sucks to hear what happened..
I believe you haven't put in enough research, ASUS has a publicly available unlocker for the 300T, why did you use a 3rd party root app?
Can you still boot Android? If you have root and your recovery partition is broken, there should still be a way to overwrite the recovery partition.
If not, this basically looks like a brick, unless you can hook up a debugger during the boot process somehow.
Someone with in-depth knowledge of this device might be able to help you out further, I'm just theorycrafting here.. Best of luck!
I would try using fastboot to reflash stock firmware, which you can download from the Asus website.
You could also try getting into APX mode and using nvflash to reflash it.
Sent from my Transformer Pad TF300T using xda app-developers app
Background:
I attempted to root the device. so I installed CWM... Well it doesnt stick. once you boot it never stays. When I go into recovery mode from the boot loader it says "no command" But if I flash it and then reboot right into the bootloader then go into recovery it works fine.
First issue: CWM doesnt stick
which led me to another issue..
ADB doesnt work in CWM (which I thought). So I decided to flash PhilZ recovery and found it didnt work there either! So I figured it had to be my drivers - but they worked fine in Windows and when the device is booted normally in the OS. (I am using Nvidia latest drivers)
Then I figured let me restore the unit back to the original image (i signed up as a developer) downloaded the Nvidia 1.2 Image and reflashed everything using fastboot (system, boot, recovery, data, etc.)
Since I had never tried to go into the stock recovery maybe it was CWM or PhilZ...
Leads to my next issue:
The stock recovery doesnt work no matter how many times I flash it. When I go into the bootloader and click on recovery mode I get "no command" with the andorid guy dead.
1. How can I get back the stock recovery using Nvidia's image. The recovery is not working
2. How can I get CWM to stick?
3. Why isnt ADB working in recovery mode but working fine when booted in the device?
stanglx said:
Background:
I attempted to root the device. so I installed CWM... Well it doesnt stick. once you boot it never stays. When I go into recovery mode from the boot loader it says "no command" But if I flash it and then reboot right into the bootloader then go into recovery it works fine.
First issue: CWM doesnt stick
which led me to another issue..
ADB doesnt work in CWM (which I thought). So I decided to flash PhilZ recovery and found it didnt work there either! So I figured it had to be my drivers - but they worked fine in Windows and when the device is booted normally in the OS. (I am using Nvidia latest drivers)
Then I figured let me restore the unit back to the original image (i signed up as a developer) downloaded the Nvidia 1.2 Image and reflashed everything using fastboot (system, boot, recovery, data, etc.)
Since I had never tried to go into the stock recovery maybe it was CWM or PhilZ...
Leads to my next issue:
The stock recovery doesnt work no matter how many times I flash it. When I go into the bootloader and click on recovery mode I get "no command" with the andorid guy dead.
1. How can I get back the stock recovery using Nvidia's image. The recovery is not working
2. How can I get CWM to stick?
3. Why isnt ADB working in recovery mode but working fine when booted in the device?
Click to expand...
Click to collapse
All has been fixed except for #2. Cant get CWM to stick... but for 1 and 3:
OK.. got the stock recovery - I didnt actually know you had to do volume up when at the "no command" screen..
and also I figured out how to fix the driver issue...
For anyone else having the issue you need to uninstall the driver until it shows up as Shield with the exclamation. You must be in the recovery in an area like sideload.. (Not in android OS)
Then Update Driver, Browser and then click on "Let Me Pick from a list on my computer"... find Android then select "Android Composite ADB Interface".
Now the driver works in ADB and in the OS
Same Problem
I'm having the same problem with CWM reverting to stock recovery after system boot. I didn't see your post until after I posted my own thread -- I probably should have titled it specifically about the stock recovery reversion so others will find it. Anyway, not that there's at least one other person besides me having this problem, I'm less worried that it's just me being stupid. Although that's always a possibility. Maybe someone will come along and help.
Recovery Reversion Problem Solved
Okay, I solved my recovery reversion problem -- I wasn't using either a custom boot.img or the Beta SuperSu (currently BETA-SuperSU-v2.42.zip), one of which is needed to keep root on Lollipop. (Apparently I knew this a month ago when I first went to 5.0.)
I let a friend try to root it and he screwed me. The phone won't boot into the os, fastboot, or recovery. in fact it constantly tries to install some new recovery but gets to 25% and repeats. I can get into download mode, I assume it's download mode. that's the only way my pc will recognize the phone. I've tried everything, can't even find the stock rom and recovery for this thing. ADB doesn't see the device nor does fastboot. Am I out of luck or is there some type of fix for this?