Just bought a used Nvidia Shield (1st gen, not the k1). It was already rooted and I wanted a clean install. Wiped the data with TWRP, downloaded the stock zip from Nvidia and tried to install it in TWRP. No luck, I get "Failed to sysMapFile 'sdcard/longzipname.zip' Error flashing zip..."
So I tried to do it manually with fastboot. Have no problem doing any adb commands, but fastboot does nothing, just always 'waiting on devices'. My device shows up when doing 'adb devices' but not 'fastboot devices'.
Something tells me there could be a driver issue on my computer (Windows 10), but Windows won't let me update the drivers I downloaded from Nvidia, it always automatically installs its defaults.
I'm bootlooped now, but can get into TWRP and the bootloader. Halp!
UPDATE: New problem. Got the driver deal resolved (see below). Got stock reflashed onto the device, booted back and began going through first time set up process. While connecting to my wifi (the first part of the setup process), everything went black. I saw TWRP come on the screen for just a second along with a script of some kind (didn't get a chance to see what it was), and everything went black again. Now my device will not turn at all. Can't boot into bootloader either. Device will charge when plugged in (there's a light). Additionally, the computer does recognize it (APX Device?). I'm still researching at the moment, but any help would be appreciated.
Did you flash newsest firmware? You have the links kn the CM thread
I did download the latest. I do want to reiterate, I'm not trying to flash CM, but stock.
Got the driver thing sorted it seems. When plugged in and in fastboot, I needed to update the fastboot driver in the device manager. flashall.bat didn't seem to want to work, but manually flashing the items seems to doing things. Working on it and hoping!
In case anyone else needs this in the future, I could run adb commands no problem, but couldn't do anything with fastboot. I downloaded the Nvidia drivers from their website, but the Device Manager wouldn't let me update the drivers for my Shield tablet. How I fixed: when in fastboot on the tablet, I pulled up my Device Manager. There was one specifically for fastboot and (surprise) the driver was no good. Updating that one with the ones I downloaded from Nvidia did the trick.
But I now have a new problem. Edited first post.
sounds like you bought a recalled tablet. If the seller did not tell you that then you need to chat with him.
This is what I was worried about. There's a thread in here to determine if your Shield tablet is slated for the kill switch update. It looks like mine was. Then I found the Nvidia recall website and it does appear that a claim has already been submitted on this tablet. So if I understand that process correctly, whenever the claim was done by whatever previous owner, Nvidia activated their kill switch. I think maybe the fact that it was rooted and didn't have the latest update protected it. Until I flashed the latest stock. The moment it connected to my WiFi, boom.
Is there anyway to fix the bootloader (which appears to be corrupted)? I found threads where people were talking about NVflash, but no real specifics.
True, lots of people come in and say they can fix but never do. I think they hope someone else will fix for them.
In reality it is also posted many times that this is not fixable except by nvidia itself.
Related
I had rooted/cwm'd my tf101 when I first got it. It was running the 3.1 update at the time. I followed the pure root posts here on XDA.
Sadly I had never tested CWM, and perhaps since it went so easily I didn't really understand/read enough on CWM to understand what is happening. When I ran the 3.2 OTA (OK so I shouldn't have done that, I know now) the TF froze on the initial splash screen.
I've tried many things and read tons of posts here on XDA and other sites, and I'm not getting anywhere, but part of it is I don't know for sure what I'm trouble shooting.
I was using a dual boot laptop in Windows mode when I did the initial update. I had the drivers working and succesfully rooted my system.
What I am trying to do is restore a stock rom for now and I've tried several methods.
1) Asus download SOP - It detects the image on the SD card, checks validity of the firmware, shuts down and reboots and hangs at the first splash screen.
2) CWM recovery, if I understand this right, I Power+ vol_down. I hit the vol_up to enter The screen says
Checking for RCK. press key <Vol_Up> in 5 sec to enter RCK.
I do that and it hangs at:
Booting recovery kernel image
3) I've tried several nvflash posts out there. NVFlash does not seem to be working, I've now done this on two windows boxes. Both the one that used to work, and a clean windows XP machine I had lying around. In both cases, I can get the nvidia APX drivers loaded and the device is seen. However, adb doesn't show any devices, and from pulling apart the batch files and doing some reading, I tried nvflash -r --getpartitiontable myfile.txt and some other commands which always hang. Eventually if I disconnect the tablet - then I get a read error of some sort.
4) quick reboot - every option leads to reboot and freeze at first splash screen.
So questions that I can't seem to find an answer too.
1) If I'm connected in APX mode, should adb show a device? Like I said the PC recognizes it as the APX device and loads the nvidia drivers instead of the normal transformer MTP drivers when I do the power + vol_up.
2) Is there a simple test to use for nvflash? The device shows up, is there anyway I can confirm whether APX mode is working or not?
I'm only starting to piece together the boot process in my own head, and my guess is that niether the stock recovery image or the cwm recovery boot image is working. Would that be a reasonable assumption based on behavior? I will admit I really don't understand the boot loading process in android.
FYI, if I go through Power+Vol_down, wait for rck to skip and then boot without wiping, the TF is fine after that. Meaning as long as I don't try to update, it will work and reboot normally. Root also still seems to be working.
I tend not to suspect a driver issue, since one machine was confirmed working, it's how I got root - and 90% of the time that machine is run as linux. I almost never boot into windows. I'm pretty sure the last time I did was to root the TF.
What happened is you overwrote the cwm when you installed the new update. You can't just randomly install things once you're rooted.
If you have a B7O machine, you need to check that you have the old or new sbk. Go to the general transformer forum, and there's a thread about the new sbk locked bootloader. Follow the test to see if you have one that you can use nvflash with. If that is the case, then go to the dev forum, and look through the nvflash unbricking thread.
Thanks for the reply
First off, you're right and I should have known better. Almost nothing I own runs it's stock firmware, and I just got dumb and didn't do the full research excited for HC 3.2 goodness.
I have a B50 machine, or at least the my serial number indicates that.
I've already tried several nvflash debricking instructions, but it seems that nvflash is not working either. I have several copies of prime and the .11 release from asus. But since nvflash is not behaving as expected, all of those threads are not helping.
I do have the nvidia USB recovery device show up in device manager, but every nvflash command fails hangs at
nvflash started
[resume mode]
ADB devices shows a serial when I'm normally connected, but it doesn't show up when I'm in APX mode. I'm just not sure if the device is in a functional APX mode, since nothing actually runs, despite it showing up in device manager. I've tried googling that situation, but I can only find posts that tell me how to get it to show up in dev manager... It seems like when that happens everyone else has been fine.
WHILE GOOGLING FOR MORE INFO ON b70 - I managed to get NVFLASH working, and now I get what the first command and -r do.
3.2 Update Problem SOLVED
So look at the original post for the strange condition I had gotten into.
Somewhere along the line, the transformer had stopped responding to adb even not in APX mode.
I uninstalled PC Suite and Asus Sync. Then reinstalled only ASUS sync. ADB started working when TF was connected normally
I did not reboot my PC, win7 64 bit. Shutdown transformer, it hung at the splash screen. WHILE HUNG, I held power and vol_up until device manager showed nvidia USB recovery device
I used the stock rom replacement from tabletroms. Sorry I can't include the link as I am too new to XDA.
Got the transformer back up, set up my account, restored data. However OTA from there was not working.
So I went to ASUS, grabbed the .11 image and updates via SDCARD following the SOP instructions.
After reboot, checked for updates, and there was one. Let it do the OTA for 3.2 and now I'm back at having stock 3.2 updated TF.
I will probably root, but may not CMW this time.
HELP! (I used the Debugfs method: http://forum.xda-developers.com/show....php?t=1706588)
I feel like an utter moron at this point, which I think is frustrating me as much or more than my inability to get my new 300T (running .30) rooted, especially as I've managed to root all my other devices with no problems! OK, I'm not terribly familiar with ADB (although I can C/P code to it and not kill things), so I chose this method to try to root. Got everything set on my 300T, downloaded/unzipped the zip, ran batch file. Selected option 1, and watched the code fly by, with lots of "adb out of date, killing". It reboots my 300T a few times, and I get to the end, and check for SU, no dice. I tried downloading it, then running Titanium Backup to test if the root had been done, no luck. AND, now I'm getting an android.process.media error. ARGH!
What am I doing wrong here? Help?
**Also, I just noticed that my computer is no longer recognizing my 300T- as in I pluc the 300T into my computer, and NOTHING happens. I've tried rebooting the computer and the tab, with no luck either way. As far as the computer is concerned (any of them, I've tried it on three computers, same result), there is nothing connected to it at all. I've also tried booting the tab into recovery (pwr + Vol down), and it gives me the dead android with the red triangle/exclamation mark. Somehow, I don't have root, but I've lost recovery.
I have no idea why the computer might stop detecting the tablet. Did you make sure to turn USB debugging on in the developer options? Do other computers recognize it? Have you checked to see if it's listed in Device Manager? Did you try uninstalling and reinstalling the drivers? I would personally recommend using a live Linux distribution and following the step-by-step instructions in Linux. No drivers to install; just install the SDK, and you're good to go.
On another note, the Android on its back when you tried going to recovery, is the stock recovery. It's not meant for you to flash or restore anything. Its only job is to flash OTA updates, which it will only do when there is an OTA.
Hello, first time posted, long time browser...
So, I have a bricked (or almost totally bricked) LG G2X. Here is what I did:
I had flashed the Hellfire Sandwich 1.9 rom and was just fine...until my phone started turning off randomly. After reading somewhere here that I should nullify my phone and the re-flash the rom in order to fix my issue.
So, I backed up my data and downloaded the Aroma Nullifier from Volk (thanks for all you do). I booted to recovery and ran the Nullifier. Once the Nullifier had stopped, still while in Recovery, I tried to access my sdcard to re-flash my Rom...well, I couldn't access my SD card. Furthermore, I couldn't unmount the SD or mount the USB Storage.
Here comes the big mistake:
So, as I was doing some research about how to proceed, my USB cord wiggled out of the phone and my phone lost power. Now, since I had read from Volk not to let that happen, I knew I was in trouble.
At this point, I can only load into the LG Boot Screen and my computer loads drivers for "Asus Android Device" (I have the Asus Transformer Prime Tablet) and under that title "Asus Android Bootloader Interface". No APX, No USB Controller....no other communication.
Last little note, I took the phone to the Tmobile store on a hunch one of the guys who works there had some experience (which he did), and while he was trying to boot into recovery from battery power (something I have been unable to do) he got the USB communication interface...something like "S/W Do not disconnect".... Since then, I have not been able to reproduce that interface.
I am at the end of my abilities...I haven't seen anything that addresses this particular problem though I have tried a bunch of solutions without success. I have looked all through XDA forums, but if there is one I missed, please let me know.
Any thoughts would be very helpful.
Kickingcans
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Thanks much...but...
therealnexion said:
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Click to expand...
Click to collapse
Thanks for the thoughts. I will try that all again, but I have tried nvflash and tried updating APX drivers. My computer only recognizes the phone as an "Android Bootloader Interface". When I try to manually update/change the drivers for the "Android Device", there is a problem with 64-Bit operating System (Windows 7 Home Premium). I was going to try to boot the computer in Safe Mode, but I don't know if that will help.
I haven't been able to communicate with the phone, and only saw the S/W Upgrade screen once and that was in the Tmobile store without access to my computer.
I am going to try those suggested steps again. Thanks again.
Leigh
Got it going....
THANKS SO MUCH. I knew I was missing something stupid. I kept reading the nvflash instructions and pressing the Power and Volume Down button instead of Volume Up and Down.
Things are going again. Thanks so much.
Kickingcans
I recently got a Shield for $85 because the ebay seller said it was missing apps.
I've got it rooted with the custom towelroot, but i'd like to use a recovery and restore to normal shield firmware instead of the Diagnostics it's on.
Basicaly, it's The shield, stripped of google services, & OTA update, with "Input Viewer," and "Mfg Test" added.
It's on 4.2.1 Build- rothdiag-userdebug 4.2.1 JOP40D 7947_223.4068 test-keys
Kernel- 3.4.10-g6f428d8 [email protected] #1 Tue Aug 27 16:37:56 PDT 2013
Model number is Roth Diagnostics
It runs everything fine, I just need to put it to stock shield as a normal user would have, since I can't stream from my laptop to it with how it's setup now (It has tegra zone, but won't detect my pc)
I just recently acquired a Shield Portable as well, and of course, now I’m doing the research to get all I can from the device.
When I got mine, I immediately unlocked and rooted it, installed TWRP recovery, flashed the Roth 1.6 updates, and flashed CM12.1 Nightly with Open GApps ARM 5.1 Micro. All went well, and works fine, though I’m still uncertain as to the best recipe to bake my Shield with.
As for your question, how to get back to stock, well, from what I did, it’s actually quite simple.
Take my method with caution!! I’m still new to the Shield, and whenever flashing a device you always run the risk of bricking, so be damn sure you know the do’s and don’ts. Also, this method should completely return you to stock, including removing any custom recovery you installed.
Keep in mind, when I flashed back to stock, my Shields bootloader was unlocked, had a custom recovery, and CM12.1 installed. I’m not quite sure if this makes a difference, I’m just pointing out my configuration at the time.
One last thing, I flashed from a Windows 10 rig, and my instructions will be noob friendly for those that stumble upon this post and need to know what to do from the beginning.
1. Connect your Shield to your PC, and boot your Shield into Fastboot mode by simultaneously pressing the Back + Home + Shield button. Your shield will boot to a black screen displaying menu options such as Continue, Restart Bootloader, Recovery Mode, among some other options.
2. (SKIP IF SHIELD DRIVERS ARE PROPERLY INSTALLED ON PC) Now, make sure your Shield can be seen on your PC.
In Windows, go into Device Manger, and if there’s an exclamation point next to your Nvidia Shield device (it might read Fastboot device or Roth), then you’ll need to fix that problem so Windows installs the proper drivers.
I’m running Windows 10, and the following method worked for me to get the proper driver installed.
Right click Nvidia device in Device Manager then click the following... Update Driver > Browse My Computer for driver software > Let me pick from a list of device drivers on my computer > Android Device > Android Composite ADB Interface > Click Next and that should install the driver.
3. (SKIP IF SHIELD DRIVERS ARE PROPERLY INSTALLED ON PC) If you have the driver properly installed, you can verify Windows sees your shield by running fastboot devices.
To do this, one method is to download Shield Root files courtesy of CriticalComposer from this link https://www.dropbox.com/s/mr8ro1gx2axynwg/Shield Root.zip
Extract the file, go into Shield > Shield Root. The ABD files are located there.
Press the shift key on your PC keyboard as you right click in that folder, then select “Open command window here”. This will open a command prompt pointing to the Shield Root folder.
Now type fastboot devices in the command prompt and press enter. If Windows sees your Nvidia Shield a serial number will appear. If nothing appears, that means you may not have your Nvidia driver properly installed or in Fastboot Mode.
4. Now that your Shield is connected to your PC and can be seen by Windows, you’ll need to download the Stock image from Nvidia.
Here’s the link https://developer.nvidia.com/gameworksdownload
You might have to create an account to download.
I believe NVIDIA SHIELD Portable Recovery OS Image Update 106 is the latest as of this post. Download it and extract it to your PC.
5. (THIS STEP STARTS THE FLASHING PROCESS) Open the extracted folder, and simply double click flash-all.bat. That should start the flashing process, and it will flash everything needed to return to stock. If it doesn’t start the flashing process, re-check to ensure Windows has the proper drivers installed.
6. Once it completes flashing it will display “press any key to exit” in the DOS box, do that, then reboot your Shield.
7. When your Shield reboots, it should display a screen with NVIDIA and its logo, and might take up to 5 minutes to finish booting.
8. Hopefully all goes well, and you should now be back at stock with Lollipop 5.1 and Nvidia update 106.
Same Situation Different Issue??? NoWiFi??
I have the exact same situation as the OP but i cannot get the WiFi to work at all, I tried flashing every recovery ROM from the site from factory image to update 106, still no WiFi,I have also tried rooting and installing CM but the issue is still present. i have found other posts about the same problem but most posts only talk about the K1 tablet, I tried restarting over and over again, i have tried factory reset, I feel like i have tried just about everything, if anyone has better knowledge and cant step me through it that would be much appreciated because i was told the item only had apps missing and i tried to return it but was denied somehow so i'm stuck figuring it out, everything else works on the shield portable perfectly and it looks new, i just feel its only half a shield with no internet.
EDIT:
Also i just used foxfi on my phone and paired them and when i enable "use for internet access" It enables and then automatically disables, So it seems like a software issue, i'm still clueless as what to do, i assume if i could find the system apk for WiFi i could reinstall it but i can't find it.
simmpledeals said:
I have the exact same situation as the OP but i cannot get the WiFi to work at all, I tried flashing every recovery ROM from the site from factory image to update 106, still no WiFi,I have also tried rooting and installing CM but the issue is still present. i have found other posts about the same problem but most posts only talk about the K1 tablet, I tried restarting over and over again, i have tried factory reset, I feel like i have tried just about everything, if anyone has better knowledge and cant step me through it that would be much appreciated because i was told the item only had apps missing and i tried to return it but was denied somehow so i'm stuck figuring it out, everything else works on the shield portable perfectly and it looks new, i just feel its only half a shield with no internet.
EDIT:
Also i just used foxfi on my phone and paired them and when i enable "use for internet access" It enables and then automatically disables, So it seems like a software issue, i'm still clueless as what to do, i assume if i could find the system apk for WiFi i could reinstall it but i can't find it.
Click to expand...
Click to collapse
I've had this issue before back in the days when the Xperia Play was still a thing. The problem (if I remember correctly) was the radio.img needed reflashed.
You'll have to get the latest one and put the device in fastboot mode, and do
fastboot oem unlock
fastboot flash radio radio.img
in the cmd prompt.
loismustdie555 said:
I've had this issue before back in the days when the Xperia Play was still a thing. The problem (if I remember correctly) was the radio.img needed reflashed.
You'll have to get the latest one and put the device in fastboot mode, and do
fastboot oem unlock
fastboot flash radio radio.img
in the cmd prompt.
Click to expand...
Click to collapse
I know how the process works but I tried so many times and searched all over and I cannot find a radio.img for this device, do you know how or where I can find it, it would be amazing to get this too work at its full capability, cause it pretty much sucks without wifi.
Sorry to ask a dumb question but, why not restore the sock image from Nvidia's site?
It sounds like you all bought failed attempts to use CM.
Sent from my HTC One_M8 using Tapatalk
Ok, I've been reading around the forum for about a week, trying to solve a problem with an original moto g (falcon). Basically my cousin got the moto g a few years back, and I, in my ignorance, tried to root the device for him. What I can remember was oem unlocking the bootloader with Motorola's unlock code through their website and adb. then my cousin freaked about the warranty warning on the boot animation, and decided against it. So cut to now, I'm a little more experienced, the phone's years old now, and he'd like to refresh it with a new rom, which I suggested, trying to help him. So forgetting what I'd originally done those years ago, I started the process of rooting the phone, installing a custom recovery, to hopefully put a lighter rom on it for him.
OK so it's a UK Retail on tesco mobile, moto g xt1032 running Android 5.1.
in bootloader menu it says "Device Locked status 2", dunno what this is in relation to.
first I checked the bootloader was still unlocked, and adb said it was. so I tried to use CF-autoroot to finish the job, but there was issues. it restarted the phone into fastboot mode, but when the script started, pc end did nothing, on the phone it said, "flashing unlock" and just sat there for 10-15mins doing nothing (i left it the time, just incase it was doing it).
So i read a little more, and found because i'd already unlocked the bootloader, I could just flash a custom recovery and root from adb? so I downloaded the latest twrp and tried. I was unable to do so. it said the partition wasn't the right size? should have documented it, but really didn't expect to run into any problems.
So I restarted and tried to do my usual fallback, and flash the factory image and start again, But couldn't find a source for the specific img, and tried to keep fighting on.
So I noticed that the phone wouldn't respond to adb or fastboot once in fastboot mode, when in android with usb debugging, no problems, in fastboot, didn't show up as adb devices?
I tried booting into the recovery from the bootloader menu, and got a no command. So there isn't a recovery, and I can't flash a new one? if i could find the stock recovery, I would try that.
so apart from deleting all his apps and settings, I hadn't solved the problem at all, and had to leave the job there as I couldn't find a solution.
I know this isn't the most detailed, but I've done this with quiet a few phones now, and felt I was pretty competent. I see everyday as an excuse to learn more, and like to think I have humility. So, I'm assuming I did something those years ago to damage the recovery? I'm running out of ideas, and was hoping someone could point me in the right direction?
I've lurked on xda for years, and learned so much about this kind of thing through my past experiences, but I'm stumped this time, and feel obliged to resolve the problem, as it was me who caused it.
TL DR
Can't flash recovery, no command when I try to open recovery, trying to either factory image back, or root/custom recovery it.
any insight would be much appreciated.
Hi. I just rooted and installed CM13 on an old XT1034 about two days ago. I am also sort of a ROM noob, I have ROMed a few devices, but usually but following strict step by step guides I have found here on XDA. Over the years I have some minor understanding of the process now.
I also got the "No command screen" when trying to get into TWRP recovery. The issue seems to be that if you reboot via ADB and the ROM launches it will automatically rewrite the recovery to the stock one, and when you try to go to recovery from fastboot, it gives you the "no command" error. Apparently you can get to the stock recovery from there by a hardware key combo, something like holding up vol for 10 sec then a quick press of power (I can't remeber the exact key sequence or what forum I read it in). If it does this you have to reflash TWRP again. This issue is mentioned here (http://wiki.cyanogenmod.org/w/Install_CM_for_falcon) in step 8 about installing recovery. What I ended up doing was after the flash of TWRP via ADB, I manually powered down, then manually bood into fastboot by holding volume down and power, and selecting recovery. This was a bit fiddly and I had to attempt it a few times but eventually it worked and TWRP installed.
The issue with the phone not being recognized may be due to incorrect drivers. I had no issue with this because I installed the official driver package from Motorola. It is available in their website in the developer section. I don't have the URL right now.
Hopefully this helps, for me CM13 Official has been an a stable fresh start for this old device.