Some of us used the flash-stock-then-flash-CWM method of installing the ICS leak, but were left without a working recovery. The method below allows you to unlock the bootloader and install a custom CWM.
This method may or may not work for you. I take NO CREDIT for making this happen, I'm just writing a quick howto. Thanks to strra for making it convenient.
Typically, attempting to boot into Recovery would generate an error that recovery image was not verified (something along those lines).
Thanks for all the devs who made this possible - you guys are amazing. Donate to them if you can, they deserve it.
I TAKE NO RESPONSIBILITY IF YOU TURN YOUR A500 INTO A PAPERWEIGHT.
If you don't feel comfortable with this possibility, stop here.
Install the A500 drivers from Acer on PC (from Acer's site).
Install and launch Android terminal app on tablet. Run the following command:
Code:
dmesg>/mnt/external_sd/dmesg.txt
Open up dmesg.txt and look for androidboot.serialno. That is your CPUID. In my case, the serial number reported by the OS, on the box, in the MicroSD slot was NOT my cpuid.
Use Vache's site to convert that number into your SBK (four long hex values).
Extract all of the required files (batch.rar and nvflash) from strra's post into c:\nvflash.
Open up a Windows command prompt (cmd.exe) and then `cd c:\nvflash`.
Launch `run.bat`, but don't enter your SBK yet.
Power down the tablet.
Use a paper clip and hold down the Reset button. Do not release it. Hold down power for 3 secs and then release it. After another second, remove the paper clip. Your Windows PC should then detect your device and install the APX driver. You should then have an APX USB device installed. If you do not have an APX USB device listed in your system tray, you cannot proceed.
Go back to the Windows command prompt and enter your SBK. Once you enter it, the process should begin. If you receive a USB write error, your SBK is incorrect.
Once the process begins, the Windows command prompt will read "Press any key when your A500 is in bootloader mode". Do not continue until the tablet is in Download Mode.
Once the tablet reads "download mode" (something along those lines), you are in bootloader mode. You can proceed and it will begin formatting the various partitions and installing the recovery.
Once the process completes, it should say PASS. You can then power off the tablet and power it back on again.
Make sure your tablet boots.
Power the tablet down and attempt to launch CWM via Power+VolDown.
PROTIP
Remount /system rw:
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p3 /system
Worked perfectly! Thanks!
yaw
worker for me too... thanks to all for this work!
good write-up
also, another protip:
if you right click the title bar of the command prompt, you can go to edit>paste to copy/paste the SBK... should make things a little easier
@strra:
You don't happen to know the location of the apk's for `Acer Media` and `Weather`, do you?
I'd like to add them to the following list of bloat that can go (another PROTIP) once you remount /system rw.
Under /system/app, rename:
3DPhotoBrowser-apk
AcerNidus-apk
Clearfi-apk
aupeo-apk
Problem with recovery
When it launches download mode, it says entering download mode in acer boot screen and it stays like that. How much time should I wait until it enters download mode? Or is that download mode? When it shows PASS message then under appears a red text saying LNX image not certified or something like that, why? Please help me. Thanks.
Now my tablet boots with a white text on it saying custom bootloader. But i don't have recovery mode.
Luescoff said:
Now my tablet boots with a white text on it saying custom bootloader. But i don't have recovery mode.
Click to expand...
Click to collapse
Install new recovery with fastboot. Boot into Android normally and connect it to PC with Android SDK (you need working adb and fastboot commands).
Check if adb sees your device:
Code:
adb devices
Boot into bootloader:
Code:
adb reboot bootloader
If you haven't been in bootloader mode before you might need to install fastboot drivers (from ACER Drivers for example).
Check if fastboot sees your device:
Code:
fastboot devices
My a500 didn't return its ID so fastboot is showing a device with "?" instead of ID. It is ok.
Install new recovery (here it is in recovery.img file, change it to yours):
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
When device will be booting just hold Volume Down like always to get into recovery.
You can also test and boot recovery.img directly from PC with fastboot:
Code:
fastboot boot recovery.img
You can test with fastboot boot command as it doesn't overwrite anything in device's flash. It downloads boot image (like recovery.img or boot.img into RAM and runs it from there).
jm77 said:
@strra:
You don't happen to know the location of the apk's for `Acer Media` and `Weather`, do you?
I'd like to add them to the following list of bloat that can go (another PROTIP) once you remount /system rw.
Under /system/app, rename:
3DPhotoBrowser-apk
AcerNidus-apk
Clearfi-apk
aupeo-apk
Click to expand...
Click to collapse
You can also add social Jogger
Link to facebook .
and all the links to there so called book shelf apps like link to games link to media .there are 4 of them They Hog resources even if you NEVER use them.I forget all there names and im on Vachs rom he has removed them all.
@jm77: Maybe could you split the DL link (batch.rar) and add the link to the OP of the orig. thread for downloading the bootloader binary (so when I update it people get the updated version directly)?
jm77 said:
@strra:
You don't happen to know the location of the apk's for `Acer Media` and `Weather`, do you?
.......
Click to expand...
Click to collapse
Acer hid them in flexrom/app this time around!
Thanks for the help.
yaworski said:
Install new recovery with fastboot. Boot into Android normally and connect it to PC with Android SDK (you need working adb and fastboot commands).
Check if adb sees your device:
Code:
adb devices
Boot into bootloader:
Code:
adb reboot bootloader
If you haven't been in bootloader mode before you might need to install fastboot drivers (from ACER Drivers for example).
Check if fastboot sees your device:
Code:
fastboot devices
My a500 didn't return its ID so fastboot is showing a device with "?" instead of ID. It is ok.
Install new recovery (here it is in recovery.img file, change it to yours):
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
When device will be booting just hold Volume Down like always to get into recovery.
You can also test and boot recovery.img directly from PC with fastboot:
Code:
fastboot boot recovery.img
You can test with fastboot boot command as it doesn't overwrite anything in device's flash. It downloads boot image (like recovery.img or boot.img into RAM and runs it from there).
Click to expand...
Click to collapse
Thank you, yaworski
For a mysterious reason the only way to boot in CWM recovery mode on my a500 is passing by your last command
Code:
fastboot boot recovery.img
The classical "volume-/power" method brings me to the "dead android man" with the exclamation mark... Same thing if I use the "Acer recovery" app.
In others words, the only way to open the recovery is passing by the bootloader and the fastboot commands...
Any idea for the reason of that?
So should the odmdata in the bat file be 0x300d8011 or 0xb00d8011. It has 0x300d8011, but i saw another post where it should match was EUU uses as 0xb00d8011.
Thanks.
castafiore said:
Thank you, yaworski
For a mysterious reason the only way to boot in CWM recovery mode on my a500 is passing by your last command
Code:
fastboot boot recovery.img
The classical "volume-/power" method brings me to the "dead android man" with the exclamation mark... Same thing if I use the "Acer recovery" app.
In others words, the only way to open the recovery is passing by the bootloader and the fastboot commands...
Any idea for the reason of that?
Click to expand...
Click to collapse
it's because you didn't delete recovery-from-boot.p from /system and it's reflashing stock recovery whenever you boot into android
I want to make a backup of my current EBT before I try flashing this new one. When I enter APX mode (reset button + power), I get "Acer Picasso USB Boot-recovery driver" listed in my device manager.
Then I issue the command (i blanked out most of my SBK here).
Code:
nvflash --read 4 myboot.img --sbk 0x8E000006 0x9C000001 0x22000002 0xF0000002 --sync
I've tried different flags like --bct --odmdate --configuration but i always get:
Code:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Following that, the device dissappears from my windows device manager.
I've also tried the first command from run.bat with both odmdata values
Code:
nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0xb00d8011 --sbk 0x8E000006 0x9C000001 0x22000002 0xF0000002 --sync
nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x8E000006 0x9C000001 0x22000002 0xF0000002 --sync
Both of these give the error message same message.
Any ideas?
---------- Post added at 01:21 PM ---------- Previous post was at 01:11 PM ----------
Also, just tried the run.bat as is (well.. i removed the "cls" so the screen woudln't blank. Get the same error..
Code:
C:\Users\james\Downloads\bootloader>run
****************************************************************
* This will boot your A500 into bootloader mode, *
* flash patched bootloader V2, and flash Thor Recovery 1.7 *
****************************************************************
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here : http://vache-android.com/v1/index.
php?site=sbk
Enter your SBK:0x8E000006 0x9C000001 0x22000002 0xF0000002
Loading bootloader...
Nvflash started
rcm version 0X4
[COLOR="Red"]Command send failed (usb write failed)
[/COLOR] **********************************************************
* Press any key when your A500 is in bootloader mode *
**********************************************************
Press any key to continue . . .
strra said:
it's because you didn't delete recovery-from-boot.p from /system and it's reflashing stock recovery whenever you boot into android
Click to expand...
Click to collapse
Thank you, strra.
I suspected it, to be honest, since I've noticed this advice when I launched the run.bat
But, my question has been/is still now: how to remove this "recovery-from-boot.p" ?
Can it be done when in APX mode? Do the adb commands work in APX mode?
castafiore said:
Thank you, strra.
I suspected it, to be honest, since I've noticed this advice when I launched the run.bat
But, my question has been/is still now: how to remove this "recovery-from-boot.p" ?
Can it be done when in APX mode? Do the adb commands work in APX mode?
Click to expand...
Click to collapse
While in Android you need to remount your /system partition as writable and just delete the file with rm command . If you didn't replaced your boot.img yet with patched one, just use
Code:
fastboot boot boot.img
command where boot.img is patched kernel, then wait until Android is started (it will run on patched kernel from ram like with recovery).
When you run on patched kernel and you use adb shell then you will have root from the beginning. Then just use
Code:
mount -o remount,rw /system
and you can remove the file.
Thanks for your quick and clear answer, yaworski
Booting on this patched boot.img is the trick.
fastboot boot recovery.img doesnt work for me, and i'm no able to mount rw to delete the recovery-from-boot.p. what can i do now??? i'm stuck in this leak version...
querobolo said:
fastboot boot recovery.img doesnt work for me, and i'm no able to mount rw to delete the recovery-from-boot.p. what can i do now??? i'm stuck in this leak version...
Click to expand...
Click to collapse
Did you flash the patched bootloader in APX mode using nvflash? Because all above instructions work only on unlocked and patched bootloader with "secure" flag off.
Related
I'm trying to install baconbits on my G2 and I have a mac. I cannot seem to get the recovery image to work through fastboot. Help?
I can access the phone through the terminal but once I command it to reboot to the bootloader I can't get it to find the img file
There's a fastboot binary available for download from this page: http://developer.htc.com/adp.html
I have the binary in my sdk's tools folder but I still can't figure it out. Where/how do input the command to boot the img file?
pak256 said:
I have the binary in my sdk's tools folder but I still can't figure it out. Where/how do input the command to boot the img file?
Click to expand...
Click to collapse
You can flash files from recovery if they are on the SD card. You can either adb push while in recovery, or mount USB storage and tranfer the file. Or just transfer it via USB while the phone is on (big, green android screen)
I'm not sure how to install baconbits, but I think you need fastboot to flash the .img file. Recovery flashes .zip files and fastboot flashes .img files. You can put fastboot-mac in the same folder as adb... then fastboot flash recovery your_recovery.img. You really don't need adb (for this) since you can boot into fastboot on the phone by restarting while holding down the trackpad button.
These might be the droids you are looking for...
Code:
adb (read the instructions)
adb devices (you'll see your phone if it's plugged in, turned on, and in the proper mode)
adb reboot bootloader (white screen with androids on skateboards)
fastboot-mac (more reading...)
fastboot-mac devices (your phone again)
fastboot flash recovery your_recovery.img
fastboot reboot-bootloader
For some reason, I had a little trouble flashing my recovery- sometimes it would hang and wouldn't flash, sometimes it would only fastboot boot. So if you run into trouble, there might be other problems.
While you are at it, you might as well save yourself the trouble and either add the adb and flashboot folders into your path, or put the binaries somewhere in your path. I also renamed fastboot-mac to fastboot for simplicity.
Going to try that when I get out of class but I think you helped me realize what I was doing wrong. Thanks and will let you know if it works
Sent from my T-Mobile G2 using XDA App
Okay I could get the fastboot prompts to work but when I try to flash the recovery it tells me "g2recovery.img" could not be loaded
okay, used clockwork and got it to work. yay!
Alright in the irc channel we have figured out a few ways to get into recovery if you kill your system on the wifi version.
1) Hook up usb cable, open terminal/command, power on xoom, copy and paste this in the terminal:
adb wait-for-device && adb reboot recovery
2) Download CWM recovery.img. Go into fastboot mode (power and volume down). Once there paste the following in terminal/command:
fastboot flash boot recovery.img
Then just reboot.
3) If you wipe out your system hard enough, it will actually put you into a recovery loop, so just set back and wait.
Thanks to
DeadRinga for #1
Bigrushdog for #2
BWCorvus for #3
Not entirely sure what you mean by kill your system, but i have a wi/fi model that i attempted to re-lock and ended up a real problem.
"Failed image LNX 0x0002
Starting Fastboot protocol support"
and alternatively in the bootloader I also have
"Starting RSD mode 2"
Cant get a single sight of my xoom on the pc. Nothing in RSD or adb commands. Is this a solution then for my case. Im pretty sure im straight up cold-stone brick.
Nvflash-ICS Restore!
This guide will not provide information to install Nvflash-ICS as that is covered well elsewhere.
Once you have read the information on that page click Guide.
All necessary partitions are backed up with Nvflash and you can restore only the ones necessary to recover your unit.
The second method to restore has been removed until further study can be done!
If your problem can't corrected using this information and normal use of recovery, adb, and fastboot go to this post to access the IRC channel for all Asus transformers using nvflash.
I have finished installing Nvflash but where are my files?
/sdcard/AndroidRoot/ - this is your internal sdcard
Click to expand...
Click to collapse
What files should I have?
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
Click to expand...
Click to collapse
Nvflash recovery and going back to ICS for a fresh start.
Use blobunpack to unpack a stock ICS blob. The blob is found by unzipping the stock ICS firmware twice.
You can find the ICS firmware at this link (9.4.3.30) (post #3).
[INDEX][18 April 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc.
Please give philos64 a thanks while there, without him you would have a very hard time finding these downloads if at all.
these files have to be in the folder with Nvflash
wheelie -r --blob blob.bin -created with Nvflash install
nvflash --resume --download 4 blob.EBT -created with blobunpack
nvflash --resume --download 10 blob.APP – created with blobunpack
nvflash --resume --download 6 blob.LNX – created with blobunpack
nvflash --resume --download 5 recovery.img-ICS twrp recovery image name
nvflash --resume --go
then press volume down to enter twrp, flash root, flash rom or whatever you wish
Click to expand...
Click to collapse
If your problem can't corrected using this information and normal use of recovery, adb, and fastboot go to this post to access the IRC channel for all Asus transformers using nvflash.
What is blobunpack?
Here are some links to download and explain use.
https://github.com/AndroidRoot/BlobTools
windows compiled blobtools - http://forum.xda-developers.com/showpost.php?p=21620550&postcount=24
see post #7 for info - http://forum.xda-developers.com/show....php?t=1068548
There were no dates for the following information.
The current AndroidRoot.mobi bootloader versions are
Transformer Prime: 9.4.2.28r01
Transformer TF300: 9.4.3.30r01
Transformer TF700:9.4.5.30r01
ChangeLog:-
Patch: Enable ‘fastboot boot’ command (removes ‘fastboot continue’, use ‘fastboot reboot’ instead).
Patch: Force unlocked state (protect your unlock status no matter what happens to your token).
Patch: Remove blob requirement from ‘fastboot flash’ (Flash the raw images (example: ICS_recovery.img) and not blob files).
Click to expand...
Click to collapse
When failing to get into APX mode you can try the following suggestions.
Special thanks to wha2do and daws for their input!
Also wha2do has posted a guide to enter APX that provides detail not found here! Please see his guide and give proper thanks if you find it helpful!
http://forum.xda-developers.com/show...3#post36159253
1.To enter APX mode you either have to boot, choose reboot (if available) and hold volume up pressed until it reboots and then the screen should remain black. Or if that doesn't work, completely shutdown your tablet and wait a second or two and then hold volume up pressed while pressing power on and keep it pressed until screen is blank.
or
2.fastboot -i 0x0B05 reboot (hold volume up)
or
3. adb reboot (hold volume up)
or
4. with unit powered on hold volume up and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
or
5. su
reboot -hold volume up.
This is done using a terminal; Android terminal is free from the play store. You must be rooted for this to work.
or
6. Another way:- Provided by daws
Power off the tablet and don't touch the power button again.
Connect USB cable to tablet but not to PC yet.
Press volume up and then connect USB cable to PC.
Wait a few seconds before releasing volume up button.You should now be in APX mode.
Thanks for the help daws.
or
Only if there is no other resort!
7. remove cover from unit, disconnect battery, press and hold volume up, reconnect battery!
Click to expand...
Click to collapse
Good Luck!
Click to expand...
Click to collapse
Due to my dock smoking my motherboard I have purchased a new motherboard and luckily it came as 4.0.3 ICS.
I now have installed and use Nvflash on my tablet.
In case anyone is interested this is the unit I purchased.
The box shows - Manufacturer's Reconditioned Parts - 90 Day Limited Warranty.
Usefull guide
Good work and helpfull guide for xda members :good:
Nice stuff
philos64 said:
Good work and helpfull guide for xda members :good:
Nice stuff
Click to expand...
Click to collapse
Thank you for your kind words.
can I use these file
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
from other tf300t to unbrick my tf300T bricked ver 4.1.2.?.
chanhny said:
can I use these file
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
from other tf300t to unbrick my tf300T bricked ver 4.1.2.?.
Click to expand...
Click to collapse
No.
The files contain device-specific keys and cannot be used for other devices.
See the original thread for details:
[DEV][TOOL][BRICKPROOF]TF300 NVFlash release!
There's something I've not been quite clear about with NVFlash.
So I do my backup and keep my files.
Afterwards I upgrade to Jelly Bean (because I need the JB bootloader for ROM's right?), put TWRP recovery on, and flash a new ROM that uses the bootloader version I have.
So now I have the JB bootloader, can I still enter APX mode and do a restore, or do I have to remain on ICS bootloader to do a restore?
Is NVFlash truly unbrickable? A glance at this forum shows loads of bricks, would this have sorted their problem if they backed-up first?
Thanks!
tobdaryl said:
This guide will not provide information to install Nvflash as that is covered well elsewhere.
Once you have read the information on that page click Guide.
All necessary partitions are backed up with Nvflash and you can restore only the ones necessary to recover your unit.
I have finished installing Nvflash but where are my files?
What files should I have?
Nvflash recovery and going back to ICS for a fresh start.
What is blobunpack?
Caution
Caution
There were no dates for the following information.
When failing to get into APX mode you can try the following suggestions.
Caution
Full brick recovery
Caution
Good Luck!
Click to expand...
Click to collapse
I played around with your instructions today. Ran into 2 snags:
1. Using blob UI, I typed "u" for unpack, then "blob." It returned with "cannot open 'b'";
2. Typed blobunpack.exe blob. Gave me all the files as shown in attached thumb, except LNX. Where did I go wrong?
graphdarnell said:
I played around with your instructions today. Ran into 2 snags:
1. Using blob UI, I typed "u" for unpack, then "blob." It returned with "cannot open 'b'";
2. Typed blobunpack.exe blob. Gave me all the files as shown in attached thumb, except LNX. Where did I go wrong?
Click to expand...
Click to collapse
I'm having problems with the UI myself. It worked properly when posted. We probably have had an update that broke the UI. I'll remove the link. The tools are easy to use without the UI.
You don't have an LNX extension but you do have boot.img which is the same partition. Did you possibly rename the file and forget? Packing and repacking are still working properly for me including LNX.
I also updated the download link. The link now shown is for the version that can sign when blobpacking.
tobdaryl said:
I'm having problems with the UI myself. It worked properly when posted. We probably have had an update that broke the UI. I'll remove the link. The tools are easy to use without the UI.
You don't have an LNX extension but you do have boot.img which is the same partition. Did you possibly rename the file and forget? Packing and repacking are still working properly for me including LNX.
I also updated the download link. The link now shown is for the version that can sign when blobpacking.
Click to expand...
Click to collapse
Not really. I didn't touch it. I'll do it again today to see. Thanks for the reply.
No recovery
Hello Everybody,
I followed the instructions to restore my device however when my tf300t reboots I can't get the device into recovery mode. It will start up into android or if I hold the volume down during restart it says "platform pre os boot configuration cold booting linux". I download a ICS twrp img recovery file from here for the tf300t. "http://techerrata.com/browse/twrp2/tf300t"
My only options at this point are to enter APX mode or boot into android.
If somebody could help me install a recovery so I can use custom roms I would appreciate it!!!!!
Thanks,
Mike
waynestatemac said:
Hello Everybody,
I followed the instructions to restore my device however when my tf300t reboots I can't get the device into recovery mode. It will start up into android or if I hold the volume down during restart it says "platform pre os boot configuration cold booting linux". I download a ICS twrp img recovery file from here for the tf300t. "http://techerrata.com/browse/twrp2/tf300t"
My only options at this point are to enter APX mode or boot into android.
If somebody could help me install a recovery so I can use custom roms I would appreciate it!!!!!
Thanks,
Mike
Click to expand...
Click to collapse
Use nvflash again to flash only twrp.
or
Other options
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
or if rooted
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I use 2.5.0.0 twrp as I have problems with 2.6.0.0.
tobdaryl said:
Use nvflash again to flash only twrp.
or
Other options
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
or if rooted
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I use 2.5.0.0 twrp as I have problems with 2.6.0.0.
Click to expand...
Click to collapse
Thanks tobdary for replying back. I tried other versions of the recovery but none seem to work. I can't do that fastboot method because I dont get the fastboot option when the I hold the volume down and power like I did when the tablet was bone stock. I can't get su access on the tablet because its not rooted anymore once I reinstalled the nvflash rom so I cant try and flash recovery that way either. I'm really stuck and not sure why this isn't working!
Thanks,
Mike
waynestatemac said:
Thanks tobdary for replying back. I tried other versions of the recovery but none seem to work. I can't do that fastboot method because I dont get the fastboot option when the I hold the volume down and power like I did when the tablet was bone stock. I can't get su access on the tablet because its not rooted anymore once I reinstalled the nvflash rom so I cant try and flash recovery that way either. I'm really stuck and not sure why this isn't working!
Thanks,
Mike
Click to expand...
Click to collapse
I'm not sure either.
Try flashing stock recovery and recheck your bootloader menu for fastboot.
tobdaryl said:
I'm not sure either.
Try flashing stock recovery and recheck your bootloader menu for fastboot.
Click to expand...
Click to collapse
Do you know where I can find the stock recovery? Is it something ziped in the original rom file?
I was able to root the tablet using a program that that uses a exploit while android is running. I then could adb through su access and flash different twrp recovery blob files to the tablet. Though the tablet rebooted and showed a blue line with recovery being installed when I restarted I have no options to load recovery, fastboot, or linux. I'm thinking the bootloader is corrupt. I own a tf201 and might have accidentally used one of the hairybean 2.3 (4.2) bootloader updates for that device on this one. Is there a way to get my bootloader back to the original and maybe that will fix it?
Thanks,
Mike
waynestatemac said:
Do you know where I can find the stock recovery? Is it something ziped in the original rom file?
I was able to root the tablet using a program that that uses a exploit while android is running. I then could adb through su access and flash different twrp recovery blob files to the tablet. Though the tablet rebooted and showed a blue line with recovery being installed when I restarted I have no options to load recovery, fastboot, or linux. I'm thinking the bootloader is corrupt. I own a tf201 and might have accidentally used one of the hairybean 2.3 (4.2) bootloader updates for that device on this one. Is there a way to get my bootloader back to the original and maybe that will fix it?
Thanks,
Mike
Click to expand...
Click to collapse
The first thing you flash in this guide is the bootloader. nvflash --resume --download 4 blob.EBT
With nvflash you can flash only what is needed for your situation. If you feel the problem is the bootloader you can flash just that and try again.
What you describe sounds like stock recovery is still working on your tablet. If flashing the bootloader does not help I would use stock 9.4.3.30, unzip once and place the remaining zip on your internal sdcard. You may get an update notification. Accept it and let your tablet do the work. If you don't get the notification reboot your tablet and you should see it then. Doing this will write stock bootloader, recovery, etc.
Stock recovery is the blob.SOS when you blobunpack. Just use the stock 9.4.3.30 blob and use the resulting SOS (recovery.img).
TF300T Bricked accessible using APX Mode.
Hello @tobdaryl
I have read your thread fully, but my case differs a little bit and need your advice:
I have unlocked ASUS TF300T.
I cant access FastBoot or ADB.
I can access the APX mode.
The ASUS shows only the ASUS logo when powered on.
I don't have BackUp of anything.
I have flashed everything from my ASUS, even the recovery. (I was novice):angel:
Any suggestions or advices please?
What should i do and from where shall i get the needed files, etc...
Thank you in advance.
Nader H.AL-Dirany
NaderALDirany said:
Hello @tobdaryl
I have read your thread fully, but my case differs a little bit and need your advice:
I have unlocked ASUS TF300T.
I cant access FastBoot or ADB.
I can access the APX mode.
The ASUS shows only the ASUS logo when powered on.
I don't have BackUp of anything.
I have flashed everything from my ASUS, even the recovery. (I was novice):angel:
Any suggestions or advices please?
What should i do and from where shall i get the needed files, etc...
Thank you in advance.
Nader H.AL-Dirany
Click to expand...
Click to collapse
I have read your previous posts in addition to this one.
There are four vehicles to restore your tablet. (some things can be done within android but you have no access)
1. recovery - stock or twrp
2. fastboot
3. adb
4. nvflash
I notice you also posted in my guide for accessing adb, fastboot, and apx. You were unable to access fastboot, adb, or recovery with those methods.
I don't know of any way to recover through apx without nvflash previously installed and you have no access to the other three methods.
Needs Stickied ... thanks man you helped save my butt :good:
Trigger911 said:
Needs Stickied ... thanks man you helped save my butt :good:
Click to expand...
Click to collapse
Thanks! *I'm glad you found the info useful.
Code:
#include <std/disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will amputate it with
* a piece of rusty metal. Unless it kills your cat, in which case I shall apologise
* for your loss.
*/
This is for the 2013 Kindle Fire HD (3rd Generation) "soho" or KFSOWI. Please follow the instructions below very carefully. These instructions WILL change, ensure you keep up to date.
First, download and extract the attachment (exploit.zip) into a folder. Then you need to download Fire OS 4.5.5.1 and SuperSU into that folder. Check the MD5 sums!
Although not recommended, if your Fire is rooted, you can enter fastboot mode without a fastboot cable. Using a fastboot cable covers you against most cases of bricking your device. Not using one increases the likelihood.
To use this totally unsupported, unsafe method of accessing fastboot mode, run
Code:
adb shell su -c "dd if=/dev/zero of=/dev/block/platform/omap_hsmmc.1/by-name/boot bs=1 count=1 seek=848"
adb reboot
Make sure you have the latest version of adb and fastboot and that you have installed drivers for the Fire (if you run an inferior operating system). Boot into Fire OS and ensure you have a good charge on the device. Connect the device with a fastboot cable and enter fastboot mode.
Run
Code:
fastboot -i 0x1949 oem format
fastboot -i 0x1949 flash boot hijack.img
fastboot -i 0x1949 flash system system.img
fastboot -i 0x1949 continue
Now wait for the Amazon logo with the orange underline and run
Code:
fastboot -i 0x1949 flash boot recovery.img
fastboot -i 0x1949 oem format
fastboot -i 0x1949 continue
Now wait for TWRP to load up and go into Advanced -> ADB Sideload and tick the two boxes (Wipe Dalvik Cache and Wipe Cache) then swipe the slider (Swipe to Start Sideload). Return to your terminal and run (changing the filename, if necessary)
Code:
adb sideload [B]update-kindle-11.4.5.5_user_455002120.bin[/B]
Now wait for TWRP to finish flashing and press Back then go into ADB Sideload and swipe the slider (Swipe to Start Sideload). Return to your terminal and run (changing the filename, if necessary)
Code:
adb sideload [B]UPDATE-SuperSU-v2.46.zip[/B]
If you want to, you can download the Google Apps and flash them in a similar manner. Google Apps will cause issues with Fire OS if you perform a factory reset! You have been warned.
Now wait for TWRP to finish flashing, remove the fastboot cable and press Reboot System. When the device has booted, reinsert the cable and run
Code:
adb push recovery.img /sdcard/recovery.img
adb shell su -c "dd if=/sdcard/recovery.img of=/dev/block/platform/omap_hsmmc.1/by-name/recovery"
adb push exploit.img /sdcard/exploit.img
adb shell su -c "dd if=/sdcard/exploit.img of=/dev/block/platform/omap_hsmmc.1/by-name/exploit"
adb shell rm /sdcard/recovery.img /sdcard/exploit.img
To boot into recovery, power off the device and hold the volume button [ - ] then push the power button (you may need to do this more than once). When the Amazon logo appears, release the volume button.
Please could any testers report back with results, and which model they have (pictures of it running TWRP would be nice). If you have any problems, also include your entire terminal session and any errors TWRP gives when flashing. You shan't recieve help otherwise. If you are inexperienced, please wait for other testers to try this method.
Please refrain from mirroring any of the files, just link back to this post.
ROM Developers: you need to add boot.img from the files to the beginning of your ROM's boot.img
XDA:DevDB Information
Kindle Fire HD (3rd Generation) Bootloader Unlock and TWRP, Tool/Utility for the Amazon 7" Kindle Fire HD
Contributors
spudowiar
Version Information
Status: Alpha
Created 2015-12-13
Last Updated 2016-01-01
Reserved
Reserved
Reserved
nice work
To be clear this is for:
[Kindle Fire HD] 3rd Gen/2013
Codename: soho
Model # KFSOWI
sd_shadow said:
nice work
[Kindle Fire HD] 3rd Gen/2013
Codename: soho
Model # KFSOWI
Click to expand...
Click to collapse
I'll start on TWRP soon then I'll post a full unlocking tutorial
Many happy people in soho-land today--thanks!
sd_shadow said:
nice work
To be clear this is for:
[Kindle Fire HD] 3rd Gen/2013
Codename: soho
Model # KFSOWI
Click to expand...
Click to collapse
Yep, KFSOWI. I've tried this on my 8GB one but I'll need someone with a rooted 16GB to confirm something
spudowiar said:
Yep, KFSOWI. I've tried this on my 8GB one but I'll need someone with a rooted 16GB to confirm something
Click to expand...
Click to collapse
I can help, tell me what to do
Sent from my Mi-4c using Tapatalk
http://i.imgur.com/tuMFhAP.jpg
The unlock is released, go to the first post to find out how to install!
Test #1
This is a major accomplishment and all us hackers love you. :good:
I tested and here are some observations/suggestions.
1. Make a backup of your device before starting this exploit.
2. The command "adb reboot" does not reboot into fastboot mode even when connected with fastboot cable.
Try to disconnect fastboot cable, turn off device, and reconnect fastboot cable. Boots into fastboot ok.
Will try from scratch again.
bobcat131 said:
2. The command "adb reboot" does not reboot into fastboot mode even when connected with fastboot cable.
Click to expand...
Click to collapse
does this work?
Code:
adb reboot-bootloader
Sent from my KFFOWI using Tapatalk
Got it!
sd_shadow said:
does this work?
Code:
adb reboot-bootloader
Of course! My bad.
Click to expand...
Click to collapse
I got stucked.
Everything went well until the second oem format command. Thats just not working. I'm using ubuntu in a virtualbox on windows 7, i'll try it tomorrow from my workplace where I have a real ubuntu installation.
I have a 16G version.
the console output:
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 devices
00D306073494080F fastboot
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 oem format
...
OKAY [ 0.052s]
finished. total time: 0.052s
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 flash boot recovery.img
target reported max download size of 1005584384 bytes
sending 'boot' (8192 KB)...
OKAY [ 1.033s]
writing 'boot'...
OKAY [ 0.583s]
finished. total time: 1.616s
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 flash system system.img
target reported max download size of 1005584384 bytes
sending 'system' (6370 KB)...
OKAY [ 0.821s]
writing 'system'...
OKAY [ 0.913s]
finished. total time: 1.734s
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 continue
resuming boot...
OKAY [ 0.004s]
finished. total time: 0.004s
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 oem format
...
FAILED (command write failed (Broken pipe))
finished. total time: 0.002s
[email protected]:/home/bari/SOHO#
Click to expand...
Click to collapse
Test 2 failed.
All went well, until I rebooted to system from TWRP. It booted straight into language select then system settings and no navigation bar or home screen.
Stuck in system settings .
Is this just me or a bug?
bobcat131 said:
This is a major accomplishment and all us hackers love you. :good:
I tested and here are some observations/suggestions.
1. Make a backup of your device before starting this exploit.
2. The command "adb reboot" does not reboot into fastboot mode even when connected with fastboot cable.
Try to disconnect fastboot cable, turn off device, and reconnect fastboot cable. Boots into fastboot ok.
3. The adb reboot recovery command reboots into red triangle options and unable to enter recovery.
Using power button and volume button also boots into red triangle. Needs a fix.
4. Boot into system is not complete. No navigation.
5. Missed the exploit flash, so I will reset and test again.
Click to expand...
Click to collapse
Which model do you have (8GB or 16GB)? I tested these instructions from stock using my fastboot cable, YMMV.
That is probably wise but Amazon provide complete stock images of everything but the system (which can be reconstructed), cache and userdata
"adb reboot" should reboot into fastboot mode since it does a hard reboot, I did this since my fastboot cable (whilst it worked with the "otter2") only allowed one command if it had been plugged into the powered off "soho". I only have access to one fastboot cable and this worked for that one.
That means you didn't flash SuperSU or the recovery (that is the stock recovery)
Not flashing the exploit results in the recovery not booting (the screen would flash red and fastboot would load up on both of the methods you tried), you didn't flash SuperSU or the recovery (the stock recovery booted up)
Rhyn said:
I got stucked.
Everything went well until the second oem format command. Thats just not working. I'm using ubuntu in a virtualbox on windows 7, i'll try it tomorrow from my workplace where I have a real ubuntu installation.
I have a 16G version.
the console output:
Click to expand...
Click to collapse
You were too quick on that command. I wrote "arrow underline" in the instructions, I meant "orange underline". (originally I wrote "orange arrow underline" ) What happened is fastboot reinitialised but was not accepting commands. Also, VirtualBox may take a bit of time (there was a USB disconnect/reconnect). A live CD would be much easier, I avoided putting any Linux commands in here (I have a script to craft the images).
bobcat131 said:
All went well, until I rebooted to system from TWRP. It booted straight into language select then system settings and no navigation bar or home screen.
Stuck in system settings .
Is this just me or a bug?
Click to expand...
Click to collapse
As I said, I tested these instructions from stock. Did you try a factory reset? (You can do a backup in TWRP )
sd_shadow said:
does this work?
Code:
adb reboot-bootloader
Of course! My bad.
Click to expand...
Click to collapse
See above.
Anyway, this is definitely a WIP, I have access to one device and one fastboot cable. You can help iron out any bugs with this method. Thanks for trying!
Booting into TWRP might cause a TWRP bootloop (when you reboot, it boots back into TWRP instead of system). For now, only use TWRP with access to a fastboot cable (so you can go into fastboot and do fastboot -i 0x1949 continue) or you could flash /system/recovery.img to the recovery partition and reboot using the stock recovery - but don't bother!
spudowiar said:
You were too quick on that command. I wrote "arrow underline" in the instructions, I meant "orange underline". (originally I wrote "orange arrow underline" ) What happened is fastboot reinitialised but was not accepting commands. Also, VirtualBox may take a bit of time (there was a USB disconnect/reconnect). A live CD would be much easier, I avoided putting any Linux commands in here (I have a script to craft the images).
Click to expand...
Click to collapse
It was the virtualbox. On my work computer from linux it worked perfectly.
Pictures as you requested http://imgur.com/a/GVr7f
Rhyn said:
It was the virtualbox. On my work computer from linux it worked perfectly.
Pictures as you requested http://imgur.com/a/GVr7f
Click to expand...
Click to collapse
It could be a coincidence (if the first fastboot worked, it must have been VirtualBox reconnecting the USB). But still, good to see it worked
It's seems like Nvidia released the developers image for the shield 2019 pro. There is no description at links only some dots see images.
Shield Android TV SW Version: 8.1.0 (32.7.301.32)
Android Paches: 5 oct 2019
https://developer.nvidia.com/search/site/Shield 2019
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image
https://developer.nvidia.com/nvidia-shield-android-tv-pro-developer-only-os-image
Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0-dev-rooted.zip
NVIDIA SHIELD ANDROID TV 2019 Pro Recovery OS Image
https://developer.nvidia.com/nvidia-shield-android-tv-pro-recovery-os-image
Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip
I have downloaded them let see what happens, i'm not responsible if you brick your device.
Both recovery images are working on the Shield 2019 PRO and I was able to fully flash my shield and got things running again.
Image files contains a flash-all file and all the images to recover you device
fastboot oem unlock
:: Confirm the prompt on the screen
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash dtb mdarcy.dtb.img
fastboot flash vbmeta vbmeta.img
fastboot oem lock
:: Confirm the prompt on the screen
The developer version contains 1 extra file called vbmeta_skipped.img.
NOTE: After unlocking your bootloader you will lose Dolby Vision, after locking you bootloader you will get back Dolby Vision
See also https://forum.xda-developers.com/showpost.php?p=81200005&postcount=380
Below are the steps we used to root our Nvidia Shield 2019 PRO, if you are new to rooting devices you better can wait until their are less steps.
For some reason this post doesn't show correctly in the XDA app.
UPDATE: it's possible to use the official release of Magisk.
PreRequisites:
Download: Experimental TWRP is from https://forum.xda-developers.com/showpost.php?p=80769929&postcount=312
Download: Magisk official release https://github.com/topjohnwu/Magisk/releases/tag/v20.4
Download: Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0-dev-rooted.zip (see above post)
Download: Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip (see above post)
Working ADB/Fastboot.
Coffee and a bit of luck.
Enable Developers options/Enable USB Debugging/Authorize device.
Step 1
Reboot to bootloader to start fresh...(you will need a keyboard)
Use files from filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip
Use vbmeta_skipped.img from filename:
nv-recovery-image-shield-atv-pro-2019-8.1.0-dev-rooted.zip
a) fastboot oem unlock and confirm by pressing A
b) fastboot flash staging blob
c) fastboot flash boot boot.img
d) fastboot flash recovery recovery.img
e) fastboot flash system system.img
f) fastboot flash vendor vendor.img
g) fastboot flash dtb mdarcy.dtb.img
h) fastboot flash vbmeta vbmeta_skip.img
I) fastboot -w
j) fastboot reboot bootloader
Step 2
Now we will boot to twrp and install magisk...
a) fastboot boot twrp.img (you will need a mouse for this)
b) select mount and mount everything it lets you (usually data, system_root, vendor, cache)
c) adb remount all
d) adb shell
e) rm /system (removes symlinked folder)
f) mkdir /system
g) mount -o bind /system_root/system /system
h) exit
i) adb push Magisk-v20.4.zip /data/media
j) In twrp press install and navigate to magisk zip and flash it
k) adb reboot bootloader
l) fastboot -w
m) fastboot reboot bootloader
n) fastboot flash dtb mdarcy.dtb.img
o) fastboot flash vbmeta vbmeta_skip.img
p) fastboot reboot
q) let it reboot a couple of times, after Nvidia blinks and then reboots).
Optional
r) If Shield doesn't go passed the Nvidia logo.
s) start shield with A+B pressed to get in fastboot
t) in fastboot menu select reset factory default.
u) fastboot flash dtb mdarcy.dtb.img
v) fastboot flash vbmeta vbmeta_skip.img
w) fastboot reboot
x) let it reboot a couple of time
Step 3
Device eventually loads.. when it does follow these steps
a) Enable usb debugging
b) make sure its authorized and connected
c) adb install -g magisk.apk
d) adb shell
e) su (grant root to shell when it pops up)
f) mount -o rw,remount /
g) Go to apps (trough settings), show all apps, start/open magisk manager
h) When it pops up telling you it needs to install stuff select ok and install it.. device will reboot in 5 seconds...
Step 4
When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
a) adb shell
b) su
c) resetprop ro.boot.verifiedbootstate orange
d) after device boots run: resetprop ro.boot.verifiedbootstate green
Step 5
If you have registerd for the hotfix (32.7.301.43) then you can start the upgrade now. The device will reboot and starts the upgrade, after that you lost root again.
a) adb reboot bootloader
b) fastboot boot twrp.img (you will need a mouse for this)
c) select mount and mount everything it lets you (usually data, system_root, vendor, cache)
d) adb remount all
e) adb shell
f) rm /system (removes symlinked folder)
g) mkdir /system
h) mount -o bind /system_root/system /system
i) exit
j) adb push Magisk-v20.4.zip /data/media
k) In twrp press install and navigate to magisk zip and flash it
l) adb reboot bootloader
m) fastboot flash dtb mdarcy.dtb.img
n) fastboot flash vbmeta vbmeta_skip.img
o) fastboot reboot
p) When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
q) adb shell
r) su
s) resetprop ro.boot.verifiedbootstate orange
t) after device boots run: resetprop ro.boot.verifiedbootstate green
After every reboot
When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
a) adb shell
b) su
c) resetprop ro.boot.verifiedbootstate orange
d) after device boots run: resetprop ro.boot.verifiedbootstate green
Stuck at Nvidia Logo
a) Power off Shield, remove power cable
b) Press & Hold A+B on keyboard or controller.
c) Plugin power cable will holding keys.
d) You will see the fastboot menu.
Restore Stock
Use files from Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip
a) Power off Shield, remove power cable
b) Press & Hold A+B on keyboard or controller.
c) Plugin power cable will holding keys.
d) You will see the fastboot menu.
e) fastboot flash staging blob
f) fastboot flash boot boot.img
g) fastboot flash recovery recovery.img
h) fastboot flash system system.img
i) fastboot flash vendor vendor.img
j) fastboot flash dtb mdarcy.dtb.img
k) fastboot flash vbmeta vbmeta.img
l) fastboot -w
m) fastboot reboot bootloader
n) fastboot oem lock and confirm by pressing A
Like I mentioned before, only use this when you know what your are doing. I'm not responsible for any brick devices.
All the credits are for @elliwigy and @rootfan
reserved
Hello and thank you for sharing this.
I'm looking for the fastboot drivers (the 2017 don't works with the pro 2019), I have contacted Nvidia by chat and he doesn't found too.
Can you please tell me where I can download them ?
And sorry for my poor english I'm french.
EDIT :
Ok I have resolved the problem, I have manually installed the .inf.
Regards.
After every reboot
When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
a) adb shell
b) su
c) resetprop ro.boot.verifiedbootstate orange
d) after device boots run: resetprop ro.boot.verifiedbootstate green
Click to expand...
Click to collapse
I don't understand, does this mean we have to do these steps every time the shield reboot ?
lycaos said:
Hello and thank you for sharing this.
I'm looking for the fastboot drivers (the 2017 don't works with the pro 2019), I have contacted Nvidia by chat and he doesn't found too.
Can you please tell me where I can download them ?
And sorry for my poor english I'm french.
EDIT :
Ok I have resolved the problem, I have manually installed the .inf.
Regards.
Click to expand...
Click to collapse
Hi,lycaoslease tell me how to edit the .inf,thanks a lot!
marokino95 said:
I don't understand, does this mean we have to do these steps every time the shield reboot ?
Click to expand...
Click to collapse
Yes every time you reboot you will have to do this. I have connected a Raspberry to the shield which makes it easier.
song4 said:
Hi,lycaoslease tell me how to edit the .inf,thanks a lot!
Click to expand...
Click to collapse
Hello.
It's not easy for me to explain in english, I have Windows in french. But simply go to "device manager" or something like that, select update fastboot, select choose manually, and select again the option to choose manually the driver. Select the .inf and choose boooader driver (it is really simple but like I've said It's not easy for me to explain in english, just don't select the option to search automatically the driver in folder/sub folders, select the other option).
Ok so, I have a big problem when I boot twrp.img : My mouses are not recognized (I have tried 4 wired mouses and bought one very basic old mouse. All the mouses are detected in normal or fastboot mode but 0 device are detected except the computer (I can send adb commands in twrp mode, it's all I can do).
I have also tried a lot of wired controller...
If someone have a solution to use twrp...
(All that things just for modify the Vendor_045e_Product_028e.kl to change A to B and Y to X to use my switch controller pro connected to the 8bitdo recognized as xbox 360 controller >< because natively the switch have pads issues and button mapper have a big latence and don't works in nvidia gamestream !!).
Have a good week-end guys, french kisses :silly:
lycaos said:
Hello.
It's not easy for me to explain in english, I have Windows in french. But simply go to "device manager" or something like that, select update fastboot, select choose manually, and select again the option to choose manually the driver. Select the .inf and choose boooader driver (it is really simple but like I've said It's not easy for me to explain in english, just don't select the option to search automatically the driver in folder/sub folders, select the other option).
Ok so, I have a big problem when I boot twrp.img : My mouses are not recognized (I have tried 4 wired mouses and bought one very basic old mouse. All the mouses are detected in normal or fastboot mode but 0 device are detected except the computer (I can send adb commands in twrp mode, it's all I can do).
I have also tried a lot of wired controller...
If someone have a solution to use twrp...
(All that things just for modify the Vendor_045e_Product_028e.kl to change A to B and Y to X to use my switch controller pro connected to the 8bitdo recognized as xbox 360 controller >< because natively the switch have pads issues and button mapper have a big latence and don't works in nvidia gamestream !!).
Have a good week-end guys, french kisses :silly:
Click to expand...
Click to collapse
Dear lycaos,Thank you for your kindness to help me.Wish you have a good weekend.
Thanks
hi, I am trying to root my Shield 2019 Pro. However I am stuck at installing Fastboot drivers for Windows 10. I only found the Windows drivers for older Shield models. And they don't work. How can I make these work? Thanks a lot!
Well, some of you know this because you have successfully rooted the Shield Pro 2019.
How do I install Fastboot drivers on Windows 10?
thanks for absolutely no help.
Rey3000 said:
thanks for absolutely no help.
Click to expand...
Click to collapse
That's a interesting reply, I also have a busy job and a family. And the same goes for other people on xda.
I'm using Linux and I don't have a problem with the drivers. But you can use the drivers on the Nvidia site.
https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
If that doesn't work you could maybe try
https://xdaflash.com/download-universal-adb-driver-installer-windows
Rey3000 said:
thanks for absolutely no help.
Click to expand...
Click to collapse
Maybe read all post next time ? Lycaos had the same problem you have and he explained how he resolved it on the first page, i had it too and resolved it by following what he said.
powercommy said:
Below are the steps we used to root our Nvidia Shield 2019 PRO, if you are new to rooting devices you better can wait until their are less steps.
Click to expand...
Click to collapse
While I'm generally familiar with Android, I'm new to rooting devices. Where is the best place to keep tabs on progress? Also, out of curiosity, how long does it usually take "until there are fewer steps"?
Exosq said:
Maybe read all post next time ? Lycaos had the same problem you have and he explained how he resolved it on the first page, i had it too and resolved it by following what he said.
Click to expand...
Click to collapse
Of course I tried. Doesn't work. Windows 10. Tried all USB ports. Hence my plea. - how dare I ask for help??
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
besides ... he didn't mention what drivers he used. I OBVIOUSLY tried the latest ones from Nvidia - 2018. They do NOT work ffs.
Rey3000 said:
Of course I tried. Doesn't work. Windows 10. Tried all USB ports. Hence my plea. - how dare I ask for help??
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
besides ... he didn't mention what drivers he used. I OBVIOUSLY tried the latest ones from Nvidia - 2018. They do NOT work ffs.
Click to expand...
Click to collapse
Maybe you should try a different approach with users of XDA and tone down your attitude a little bit. I have no interest in helping you out this way. Maybe other xda-ers will.
powercommy said:
Maybe you should try a different approach with users of XDA and tone down your attitude a little bit. I have no interest in helping you out this way. Maybe other xda-ers will.
Click to expand...
Click to collapse
In case you haven't noticed ... you DIDN'T help me.
mgmcd said:
While I'm generally familiar with Android, I'm new to rooting devices. Where is the best place to keep tabs on progress? Also, out of curiosity, how long does it usually take "until there are fewer steps"?
Click to expand...
Click to collapse
It really depends on how many users are using their Nvidia 2019 Pro before things gets easier. Their is not much differents between rooting your phone/tablet. As long as you follow the the steps you should be okay. It's very difficult to brick your device.
You could also monitor this thread @elliwigy is a user to watch.
https://forum.xda-developers.com/sh...-twrp-shield-android-tv-t3510456/post81811131