Related
I almost had a heart attack last night doing some kernel work. This is what happened, and how I got out of it.
I had just finished compiling a kernel I was working on and was excited to flash it and give it a run. So I built the boot.img and did
Code:
adb reboot bootloader
I got into the bootloader and
Code:
fastboot flash boot [B][I]boot.zip[/I][/B]
fastboot reboot
Working quickly, a got a little sloppy. Most unfortunately, I had a boot.zip in the same folder as the boot.img so boot.zip got flashed to the boot partition. Upon reboot, I got the usual splash screen but the upper left hand corner indicated I was in "RSD Mode 3". I pressed and held Vol up + power to get into bootloader but that was unresponsive. All I could do was press Vol Down + power which brought me back to the same state. I was unable to issue fastboot commands from here as well. This is what I did to fix it.
While I was in "RSD Mode 3" I did
Code:
fastboot flash boot boot.img
Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img. Finally, I did
Code:
fastboot reboot
and was back in the game.
Guys, I think the moral of the story is to slow down and be careful with fastboot. You can bet i'll be a little more careful
good post I'm sure this will help devs in the future
way to stay calm under pressure lol. good info.
Small world, I used to live in Fontana for 25 years and moved to NY couple of years ago Oh and thanks for the tip
Ran into this today, i had a similar, but different experience..hope this helps
Once i got into the RSD 3 mode, fastboot commands were basically dead...all i would get was <waiting for device>...
in order to get out, i had to hold BOTH VOL+ and VOL- and Power at the same time, then as soon as the screen turned off, I had to press VOL- and power at the same time to get to a 'regular' looking boot screen. I saw regular because there was no text at the top ofthe screen; however fastboot commands would work here. Because i FUBAR'd a kernel install, i just did
fastboot flash boot boot.img
fastboot reboot
and voila...it was alive again
a bit scary though
Ok, so I definitely know the heart attack feeling, and hopefully someone here can help me out. I got my Xoom today(wifi), and went looking for a root. I found a link to a root here that -said- it worked for both 3g and wifi models(found out later that it doesn't, obviously). So, I flashed the boot image, and came up with the RSD message. At that point all fastboot and adb capability was lost, and I can't seem to get it back.
Here's what happens with the following button combo's:
Hold Power+VolUp and release on screen-black: Motorola splash screen(dual core etc) with no text in corner
Hold Power+VolUp until after the splash comes up: splash with "Starting RSD protocol support 3"
Hold Power+VolUp and then hold VolDown immediatedly afterward: Splash screen with "Starting Fastboot protocol support."
Hold Power+VolUp and then VolDown after waiting a second: Splash screen with NvFlash/RSD/Fastboot menu
Hold Power+VolUp and then press VolUp again: Splash with "Starting RSD protocol support 3"
If I choose Fastboot from the menu, it just sits at the "starting fastboot protocol support".
If I choose RSD, it gives me the "starting RSD protocol support 3"
If I choose NvFlash, it says "entering nvFlash (something) and the screen immediately goes black and the notification led comes on (sits there until reboot)
No other button combinations seem to do anything. Holding Power+VolDown doesn't do anything from any mode, and Power+VolUp+VolDown acts just like Power+VolUp.
In any mode, I can't issue fastboot or adb commands. Fastboot simply says <waiting for device> for anything. I tried the advice above, to queue up a "good" boot.img (from here at xda), but it doesn't recognize it on a reboot from/to any mode I can get to. I've tried each about 20-30 times now, and I'm about ready to test the thing's shatter-resistance with my fist, so any help here would be -greatly- appreciated.
Quick update to previous post: Resolved!!
My advice? If you get stuck unable to fastboot or adb in linux, try it in windows. I hadn't booted into win for over a year, so it never occured to me until I saw someone mention it in the Tiamat thread. Even a fresh JDK/SDK install in Ubuntu didn't work for me. I didn't have any tools or SDK's installed in my winXP partition, but after a quick install, it worked first time, so now I'm the happy owner of a rooted Wifi Xoom with SD card.
Once again, the XDA forum saves the day. I love this place.
I recommend everyone keep a backup copy of their system.img around just in case too. I was going nuts after messing with my framework-res.apk file to get SMS working (for the verizon web account activiation message). I used root explorer, and BAM! crash, crash, FC, FC, then stuck at the moto logo at boot. I couldnt get it back with just a boot.img flash. I went for broke and found a post of the HI66 system.img. it was HUGE, dont know if thats what I needed. but flashed that and I was back in business as nothing else was working and couldnt get ADB to take to push the old framework-res.apk.
I have a similar issue. I have tried for over three hours now to understand why I cannot reboot into fastboot. It seems lika I have lost both fastboot and NVflash. Only RSD mode and a logo screen without text. Can't shut it down with powerbutton or factory reset. I tried to root it with a 3g boot.img whitch was terribly wrong on a wifi-only xoom and I'm now trying to flash a stock wifi boot.img. It just sits there on the M dual core screen.
What can I do from RSD mode 3?
EDIT: I have a feeling that it has freezed on that logo screen. I want to try a hard reset and the only way for me is to try to first shut it down then power it on again. Don't know if it helps but it is silly to be unable to stop it. How can I shut it down?
I've tried all the suggestions above with no luck
Will try a windows machines tonight to see if that will help, but I fear I will need to send my Xoom back to mfg for rework
may seem a stupid suggestion but what if you let the battery go dead. it will turn off. Then connect to power supply and do a fast boot restart, holding power button and vol down.
Just a thought!
I will try but I think I already tried that. It seems like boot and recovery is dead. I tried to flash the 3g .sbf file today. Thought that an already bricked tab couldn't be more bricked and perhaps it would restore the recovery or boot but RSD Lite couldn't do it. It's unvisible for a computer. I've tried both win7 and my Arch Linux box. The device is dead. Hopefully they wont have to replace the motherboard. I'm sending it for repair on Monday.
mines bricked also says
failed image lnx 0x0002
starting rsd mode 2
i can get it in the fastboot protocol mode with the - button and power but cmd window says waiting on device. my started after i did an fastboot oem lock with a bad kernel.
dogma444 said:
mines bricked also says
failed image lnx 0x0002
starting rsd mode 2
i can get it in the fastboot protocol mode with the - button and power but cmd window says waiting on device. my started after i did an fastboot oem lock with a bad kernel.
Click to expand...
Click to collapse
iirc the Failed Image lnx 0x0002 is due to locking the boot loader with custom stuff.
Unplug xoom usb
boot into fastboot
plug in xoom usb
fastboot oem unlock
orionshock said:
iirc the Failed Image lnx 0x0002 is due to locking the boot loader with custom stuff.
Unplug xoom usb
boot into fastboot
plug in xoom usb
fastboot oem unlock
Click to expand...
Click to collapse
Man that just sound to easy to work. ADB has no clue the device is.....wel, a device! Its like my xoom de-evolutionized to a primitive state and is suffering from tourrets. Anyway command typed in adb gives you back < waiting for device >. I've tried just about all the techniques here on the forums. And the people who claim to have been brought back to life are not victims of this "RSD mode 2" Im pretty sure this is like a failsafe if you blow up the original bootloader, 3. IDK though, pretty sure they are going to require some hardware replacements. Im not sure people are recognizing the degree of our bricks. These are what appear to be real BRICKS. no "soft" ness up in here. straight up cement
http://forum.xda-developers.com/showthread.php?t=1041192
adb wait-for-device && adb reboot recovery
tried this command and seemed pretty slick but, still nothing
Same thing here, was there any solution?
Give this a try:
http://forum.xda-developers.com/showthread.php?t=1079784
Please, I have same problem, but I can just reset it by pressing and holding Vol Up + Power On. When I press Vol Down + Power Down, nothing happens. If I press Vol Down when it restarts, it doesn't show me the message but shows the Motorola Dual Core logo and stops. Even in this situation I can't comunicate via usb. Now it just turn off when the battery is totally low.
I CAN boot into fastboot mode and issue fastboot commands from CMD. apparently mine is booting into RMD 3 mode or whatever it's called. when I boot normally (just hold down power button, I get the moto dual-core screen, and then it boots into the Clockwork Recovery Mod... PLEASE HELP
Hi all,
I have a bit of a problem and in need of some help. Yesterday my TF101 shut itself down and since then it won't boot anymore. The screen stays off completely, so no freezes on logo's or bootcycles (as far as I can tell since the screen is not showing anything).
I've tried:
- Holding power button for 30 sec, release, then hold it for 3 secs (hard reset)
- Holding power + volume down (cold boot)
ADB doesn't work either (since the device isn't turned on)
The only way I get some sort of response from the tablet is when I boot it into APX mode (power + volume up while usb is connected to pc). My computer recognizes 'a device', I've installed the nvflash-driver and started looking for unbricking-roms. To no avail.
I've tried numerous downloads/versions of nvflash unbrick-tools with basically two results:
- http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
After downloading and unzipping I boot the tf101 into APX mode, doubleclick download.bat and it starts. So my tablet isn't _completely_ dead. But after uploading bootloader.bin and waiting for bootloader to initialize I get an error:
(...)
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
3 (0x3) flags: 0
Click to expand...
Click to collapse
(copy/pasted from other thread but this is pretty much what happens)
- http://forum.xda-developers.com/showthread.php?t=1558170
I got the nvflash+stockrom files from xdafileserver.nl (NVFLASH_ICS_9.2.1.21_WW_NOROOT.zip).
Again, tf101 in apx-mode, doubleclick download.bat..
- this time it uploads blob.EBT (instead of bootloader.bin) and then gets stuck on 'waiting for bootloader to initialize'
I've run out of ideas.. Anyone hasn't?
I'm running the latest firmware (.24) on a WW B60-model (+nvflash has worked before)
Try using blobtools to unpack an EBT partition of the latest stock update, then rename to bootloader.bin and flash using NvFlash, or try different NvFlash versions.
Thnx for your reply
Do you know of a guide on how to do this (blobtool, extract ebt partition?)
My guide for changing the splash screen involves those steps, so give it a look, you don't need to change the splash screen though: http://forum.xda-developers.com/showthread.php?t=1666984
First thing first... have you check and confirmed if your battery had totally drained and it caused your TF to shut down? Which all you need is charging now..
Drained battery is not the problem (it was fully charged and I charged it quite a long time when it wouldn't start - and it 'boots' into APX-mode so it wasn't totally dead anyway)
Will look into the 'create your own blob'-suggestion, I've some time today for that. I'll keep u posted
Hello! I will say first I tried for a long time to search for this problem before posting, but I can't find the same problem so far.
I am trying to upgrade my tmobile g2x to something better (cyanogenmod preferably) and after researching all day yesterday, it seemed that the best method (according to over 50 tabs of open forums and information) was to avoid rooting and directly install clockworkmod using the method here:
http://forum.xda-developers.com/showthread.php?t=1056847
My g2x has never been modified in any way, its been running gingerbread, I BELIEVE, before I attempted those instructions. Whatever the latest tmobile version had been pushed out. (was it 2.3.4?)
The instructions were perfect until after I used NVFLasher. I pulled battery, held vol buttons, plugged in USB, flashed 5.0.2.0, waited till operation was complete, then I let go of buttons and pulled cord.
After this, the phone literally won't boot back up, nothing but a black screen. I can't boot up normally, nor can I boot into cwm by holding vol+pwr buttons.
I AM able to repeat the flashing process, which i tried a 2nd time just to be sure that the process actually completed successfully - to no avail.
If anyone could help, I'd really appreciate it, and thanks ahead of time!
Need information:
Look under the cover and confirm you have p999 please.
Which recovery did you choose?
-- The noob says:
From first-hand experience, a smartphone is incapable of making you smarter!
Sorry for a late response I work 2nd shift so i'm available only mornings and nights :<
Yes, its a p999. It says it on the white sticker beneath the battery, and also below the battery slot; "LG-P999DW"
I flashed it with 5.0.2.0, the 2nd option for both internal and external SD support.
Midnitewolfy said:
Sorry for a late response I work 2nd shift so i'm available only mornings and nights :<
Yes, its a p999. It says it on the white sticker beneath the battery, and also below the battery slot; "LG-P999DW"
I flashed it with 5.0.2.0, the 2nd option for both internal and external SD support.
Click to expand...
Click to collapse
Do the flash again and paste the output here. Looks like a bad flash. Should have worked.
-- The noob says:
From first-hand experience, a smartphone is incapable of making you smarter!
===============================================================
===============================================================
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x0380618442017497
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: CWM-5020.img
| 3563520/3563520 bytes sent
CWM-5020.img sent successfully
===============================================================
===============================================================
*****Once nvflash has completed successfully then hit any key to close.*****
****If any step failed then repeat the process****
Press any key to continue . . .
This is what the box says. When i click a key it just closes out. And it still won't power on at all.
post-post edit: I recently wondered if i could flash it back to the stock and see if it will power up again and go beyond brick mode, and it manages to power up just fine. Something must be wrong with the files they are sending onto my phone during the other flashes.
Midnitewolfy said:
===============================================================
===============================================================
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x0380618442017497
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: CWM-5020.img
| 3563520/3563520 bytes sent
CWM-5020.img sent successfully
===============================================================
===============================================================
*****Once nvflash has completed successfully then hit any key to close.*****
****If any step failed then repeat the process****
Press any key to continue . . .
This is what the box says. When i click a key it just closes out. And it still won't power on at all.
post-post edit: I recently wondered if i could flash it back to the stock and see if it will power up again and go beyond brick mode, and it manages to power up just fine. Something must be wrong with the files they are sending onto my phone during the other flashes.
Click to expand...
Click to collapse
Yeah, seems like a bad flash. Try the CWM touch. It says it's experimental but works just fine except won't flash trinity kernels due to lack of ext 4 support.
Touch is 5.8 something, at the top of the GUI.
-- The noob says:
From first-hand experience, a smartphone is incapable of making you smarter!
I did as you suggested, it also installed successfully with pretty much the same exact copy/paste as the previous flash (i can give you it if you want me to)
This time, it still won't boot into recovery (by holding volume keys + pwr button), BUT it will boot normally. Nomatter how long I hold the buttons nothing happens. It just boots up as a normal phone (pwr only)
I'm not sure why this is happening.
Edit (i didn't really edit, i just left this window open for a while, whist i tried a couple more times) and i discovered some pretty disturbing news. It seems that these particular instructions, i'll copy paste it: "Hold Vol Down + Power." in the instructions for "Booting into clockworkmod recovery" were more literal than I thought! It should have been more clearly stated that you had to only hold the DOWN VOL key, not UP, and pwr buttons. Then you have to keep them held AFTER the lg logo (the directions say to let go at the LG logo incorrectly) because a 2nd LG logo pops up with some blue glow around it (its actually a bit subtle to notice), and then only here you let go, and it finally goes into recovery...
Ah.. Hopefully I can continue installing cyanogenmod 10 without problems.
Thank you Mansa for all your help! :good: :good: :good:
Lol glad you got it working
Sent from my LG-P999 using xda premium
Hi Friends,
Need advise as currently my TF101 is having blank screen and i can't even boot it up and also the Asus Boot logo is also not appearing.
It happened as i was trying to flash it stock rom to my device using Easy Flasher in APX mode. After all success, i got below screen on my PC and also tablet:
Screen on PC - refer attachment
- Getting message NVFlash [resume mode] and hangs
Screen on Tablet - refer attachment
- Flash success, then flash failed.
Really need help from anyone on bringing back my tab to life. I am just suspecting i am stuck in APX mode (even when i already tried to press power 30 secs), i still get blank screen. At the same time, as per the second screenshot, since i can see contents on the screen i assume no problem with the tab screen.
Hoping someone can advise and guide me on this at the same time provide alternative solution to get any recovery flashed or even alternative way to flash stock rom.
Thanks in advance.
salpet said:
Hi Friends,
Need advise as currently my TF101 is having blank screen and i can't even boot it up and also the Asus Boot logo is also not appearing.
It happened as i was trying to flash it stock rom to my device using Easy Flasher in APX mode. After all success, i got below screen on my PC and also tablet:
Screen on PC - refer attachment
- Getting message NVFlash [resume mode] and hangs
Screen on Tablet - refer attachment
- Flash success, then flash failed.
Really need help from anyone on bringing back my tab to life. I am just suspecting i am stuck in APX mode (even when i already tried to press power 30 secs), i still get blank screen. At the same time, as per the second screenshot, since i can see contents on the screen i assume no problem with the tab screen.
Hoping someone can advise and guide me on this at the same time provide alternative solution to get any recovery flashed or even alternative way to flash stock rom.
Thanks in advance.
Click to expand...
Click to collapse
I used to get stuck on a black screen after NVFlash too
Holding the power button for 30 seconds, and then powering on normally again always fixed it
You can test if you are stuck in APX mode by plugging it into the PC and see what device manager says
You can try NVFlash to stock using this
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z
Or try Easyflasher again to flash TWRP
usaft
*Detection* said:
I used to get stuck on a black screen after NVFlash too
Holding the power button for 30 seconds, and then powering on normally again always fixed it
You can test if you are stuck in APX mode by plugging it into the PC and see what device manager says
You can try NVFlash to stock using this
Or try Easyflasher again to flash TWRP
Click to expand...
Click to collapse
Hi bro, thank you so much for the reply. I have downloaded NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z and extracted it, later on i have put Wheelie files replacing the ones in NVFLASH_ICS_9.2.1.27_WW_NOROOT folder. And i launched the reflasher but it is stuck at below state. Am i doing something wrong? How long does it normally take for the flashing process? Can guide me with the correct way to use wheelie/nvflash?
Problem:
[=] Chip UID: 0x254614196533097303
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 6 %
Really hoping for some good answers. Thanks
salpet said:
Hi bro, thank you so much for the reply. I have downloaded NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z and extracted it, later on i have put Wheelie files replacing the ones in NVFLASH_ICS_9.2.1.27_WW_NOROOT folder. And i launched the reflasher but it is stuck at below state. Am i doing something wrong? How long does it normally take for the flashing process? Can guide me with the correct way to use wheelie/nvflash?
Problem:
[=] Chip UID: 0x254614196533097303
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 6 %
Really hoping for some good answers. Thanks
Click to expand...
Click to collapse
Update: I have managed to flash the TWRP via EasyFlasher to my Tf101 and i can see "Phone update success!!!" message twice. From here i still cant go into recovery or also on my tab. The screen is always blank and also i can't even get the boot logo. Really hoping someone can help me with this. Thanks
Try a 30 second power button press followed by a 3 second press and see if you get the Eee pad logo.
salpet said:
Hi bro, thank you so much for the reply. I have downloaded NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z and extracted it, later on i have put Wheelie files replacing the ones in NVFLASH_ICS_9.2.1.27_WW_NOROOT folder. And i launched the reflasher but it is stuck at below state. Am i doing something wrong? How long does it normally take for the flashing process? Can guide me with the correct way to use wheelie/nvflash?
Problem:
[=] Chip UID: 0x254614196533097303
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 6 %
Really hoping for some good answers. Thanks
Click to expand...
Click to collapse
The NVFlash file I linked you to doesn't need anything added to it, just extract it, put your tab in APX mode, connect to PC > USB, run download.bat as Admin
Wait for it to complete, the result all being well should be 100% stock tab
It takes about 10mins~ from what I remember, been a long time since I used it though
*Detection* said:
The NVFlash file I linked you to doesn't need anything added to it, just extract it, put your tab in APX mode, connect to PC > USB, run download.bat as Admin
Wait for it to complete, the result all being well should be 100% stock tab
It takes about 10mins~ from what I remember, been a long time since I used it though
Click to expand...
Click to collapse
Hi bro, thanks for your reply. Tried both methods and i still get it to Flash. Each time i use NVFlash it just gets hang halfway and not moving. I have tried on a few PC. There was once it was success, but i can't get seem to come out of APX mode (pressed power for 30secs). Each time i plug the tab to my PC it always detected as APX mode.
Guess it is time for me to bring it to the Shop
Is your VOL UP button stuck down?
salpet said:
Hi bro, thanks for your reply. Tried both methods and i still get it to Flash. Each time i use NVFlash it just gets hang halfway and not moving. I have tried on a few PC. There was once it was success, but i can't get seem to come out of APX mode (pressed power for 30secs). Each time i plug the tab to my PC it always detected as APX mode.
Guess it is time for me to bring it to the Shop
Click to expand...
Click to collapse
If you leave it plugged into the PC > USB, and hold down power for 30 seconds, does the PC see it disconnect from APX mode and then enter APX mode again when you let go of the button ?
Try that, and keep hold of the power button until the PC recognises that it has disconnected
*Detection* said:
If you leave it plugged into the PC > USB, and hold down power for 30 seconds, does the PC see it disconnect from APX mode and then enter APX mode again when you let go of the button ?
Try that, and keep hold of the power button until the PC recognises that it has disconnected
Click to expand...
Click to collapse
frederuco said:
Is your VOL UP button stuck down?
Click to expand...
Click to collapse
Hi friends, thank you so much finally i got it working! Really grateful. The problem is the tab was stuck in apx mode. Hence i got EasyFlasher to flash again and it worked fine.
What i did was:
- Flash TWRP via EasyFlasher in APX mode.
- Came out from APX mode as per advise by leaving cable on PC, press 30secs and make sure the detection of APX is gone via Device Manager.
- Removed and reinstalled the APX driver and flashed stock Rom from ASUS via EasyFlasher. This way the flashing did not get stuck half way.
- System rebooted and i had a working Tab again.
- Flashed KatKiss 4.3 and it is awesome!
Thank you so much guys!
Great!
To sum it up, I followed the steps basically to a tee located here > http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
After flashing custom recovery, I rooted through the supersu.zip I copied onto the SD card. I selected "yes" to the option that appeared for it to fix the root. After doing that, the screen on my tablet will not turn on, but the device appears to be on whenever I connect it to a computer. In device manager, it's labeled "APX", with a driver that failed to install.
Give it to me straight doc, can we fix her?
Edit: Issue solved, am in fact a monkey.
Thepiewarrior said:
To sum it up, I followed the steps basically to a tee located here > http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
After flashing custom recovery, I rooted through the supersu.zip I copied onto the SD card. I selected "yes" to the option that appeared for it to fix the root. After doing that, the screen on my tablet will not turn on, but the device appears to be on whenever I connect it to a computer. In device manager, it's labeled "APX", with a driver that failed to install.
Give it to me straight doc, can we fix her?
Click to expand...
Click to collapse
Can you get into fastboot?
mcord11758 said:
Can you get into fastboot?
Click to expand...
Click to collapse
As far as I'm aware, no. Whenever I try to connect the device to my computer, it's detected as an APX device, and I can't see anything on the display.
Hi,
How did you solve this issue, since I'm having the same problem (can't boot after logo firstly, not even fastboot, now won't boot at all).
APX
same here. wont show bootloader, black screen.
but does show up in device manager when connected to computer as "APX".
I can here it turning on/off through the computer when connected to usb, but always black screen on tablet.
am I fckd? i cant seem to get into bootloader
D:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: device not found
salado said:
same here. wont show bootloader, black screen.
but does show up in device manager when connected to computer as "APX".
I can here it turning on/off through the computer when connected to usb, but always black screen on tablet.
am I fckd? i cant seem to get into bootloader
D:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: device not found
Click to expand...
Click to collapse
If you can get APX mode then you'll have to work out how to flash via nvflash.
This is what you'd use for the ASUS TF100 when in APX mode and it's likely to be your only way out. Good luck!
salado said:
same here. wont show bootloader, black screen.
but does show up in device manager when connected to computer as "APX".
I can here it turning on/off through the computer when connected to usb, but always black screen on tablet.
am I fckd? i cant seem to get into bootloader
D:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: device not found
Click to expand...
Click to collapse
To exit USB boot recovery mode ( APX w/o driver installed ), simply press and hold POWER for at least 11 seconds.
kickassdave said:
If you can get APX mode then you'll have to work out how to flash via nvflash.
This is what you'd use for the ASUS TF100 when in APX mode and it's likely to be your only way out. Good luck!
Click to expand...
Click to collapse
The command for flash the SHIELD should be;
Code:
nvflash.exe --bct bct.cfg --setbct --odmdata [OFFSET REMOVED] --configfile flash.cfg --create --bl bootloader.bin --go
Please notice that I have removed the OFFSET required.
xXlAinXx said:
To exit USB boot recovery mode ( APX w/o driver installed ), simply press and hold POWER for at least 11 seconds.
The command for flash the SHIELD should be;
Code:
nvflash.exe --bct bct.cfg --setbct --odmdata [OFFSET REMOVED] --configfile flash.cfg --create --bl bootloader.bin --go
Please notice that I have removed the OFFSET required.
Click to expand...
Click to collapse
I am running in the same problem.
I both the tablet yesterday. Try to do the OTA updates and it kept freezing at the nvidia logo. Force shut down and bootloader to Recovery mode.
The update 1.2.1 installed.
Update 2.1 did the same thing. I repeat the steps.
Now I am stuck in APX mode (recognized that way by PC)
Screen is black
Cannot get in bootloader
I can turn on/off (with the sound from pc) by hold power button down and then pressing power & volume+ together. Black screen again.
Nothing is working.... I need help I bought the tablet for my trip to Belgium. I am leaving for the airport in 1 hour !!!
Wicstar said:
I am running in the same problem.
I both the tablet yesterday. Try to do the OTA updates and it kept freezing at the nvidia logo. Force shut down and bootloader to Recovery mode.
The update 1.2.1 installed.
Update 2.1 did the same thing. I repeat the steps.
Now I am stuck in APX mode (recognized that way by PC)
Screen is black
Cannot get in bootloader
I can turn on/off (with the sound from pc) by hold power button down and then pressing power & volume+ together. Black screen again.
Nothing is working.... I need help I bought the tablet for my trip to Belgium. I am leaving for the airport in 1 hour !!!
Click to expand...
Click to collapse
did you find a solution?
Motawa88 said:
did you find a solution?
Click to expand...
Click to collapse
I went to the movies on Friday, turned off my tablet before the show, and appear to be in this APX mode now. I've got a replacement (battery recall) LTE 32g US device. I don't know why nVidia would want / need to kill my device remotely as I am believing happened based on all the forum posts, but here I am..
No clue what to do...
How u solved it?
I too have the same problem with APX driver
Are you sure you guys are not pressing the Power and Volume Up buttons as this will boot you into APX.
If your unsure Press and hold the Power button for 15 seconds it will boot up if you have pressed the Power + Volume Up Button, i found this out myself and was totally bricking it till i held the power button in for 15 seconds and watched it come back to live.
Power + Volume Down = Bootloader
Power + Volume Up = APX Mode.