Database Info

[HOWTO] Revive a bricked P500 on fastboot mode (the SHORT way)

The usual DISCLAIMER: Use at your own risk!
Fastboot mode usually comes up if something went wrong when trying to flash a recovery image, for example when flashing AmonRa recovery or ClockWorkMod. It happened to me several times so I tried to learn to revive it without reflashing the original firmware. Note: This tutorial works only if recovery is the only one broken. (If the ROM itself is broken, then that's a subject for another tut.) In this case, the most logical thing to do is just reflash the recovery image. So how do you do it in fastboot mode? Here's how:
Symptom
You tried flashing a custom recovery like ClockWorkMod or Thunderg, or you flashed an incorrect ROM, and when you rebooted, it showed this screen:
Code:
fastboot mode started
udc_start()
and the phone stays there. When you plugin the phone to your computer's USB, it is detected and the screen has this display:
Code:
fastboot mode started
udc.start()
-- suspend --
-- reset --
-- portchange --
-- reset --
-- portchange --
You will need
1) Your PC and your USB cable for the phone
2) USB drivers for your phone (use B2C from LG).
3) Android SDK (download from here)
4) Java, required to run the SDK (but right now I am not sure if this is required to run fastboot!)
5) ClockWorkMod or AmonRa Recovery.
Here's what to do
1) Assuming phone is turned on in fastboot mode, plug it in to the USB of your PC. You will know that it is detected if you see the the lines "suspend", "reset" and whatnot on the phone's screen.
2) Extract the recovery image from the zipfile downloaded from step#5 above (e.g. LGp500-recovery-v12.img). Place the image file in the same folder where fastboot.exe is (usually in the tools\ folder in the SDK). For your convenience, rename the img file as recovery.img
3) Fire up your command prompt and cd to the directory where fastboot.exe is located. Then type the following command:
Code:
fastboot erase recovery
Once you get the confirmation that it was successful, type this:
Code:
fastboot flash recovery recovery.img
Once you get the success confirmation, reboot the phone, or you can also type (optional):
Code:
fastboot reboot
The phone will reboot itself, and with any luck you should be able to go back to your same old Android bootscreen. Note that no settings were modified here, so this is extremely useful for those who do not want a clean slate after a fastboot nightmare.
Also, note that if this is successful, you can now boot to recovery with the usual button-combos, thus enabling you to flash ROMs and other recovery zips.
Note: On some SDK versions, fastboot may not be included. For your convenience, I have attached the fastboot binary I got from my downloaded SDK. I have also attached AdbWinApi.dll which some user reported is missing in the SDK. Place the DLL in the same folder where fastboot.exe is located.
Questions, just drop me a line here

thanks dude, its very usefull

Nice tutorial for newbies like me, thanks...
Sent from my LG-P500 using XDA Premium App

We already have a tut like this.

@arvinoids
Good tutorial, but you forgot to say that LG USB drivers are needed and that fastboot.exe must be downloaded before (it's no more included in android SDK)
thanks man

d3s3rt_eagle said:
@arvinoids
Good tutorial, but you forgot to say that LG USB drivers are needed and that fastboot.exe must be downloaded before (it's no more included in android SDK)
thanks man
Click to expand...
Click to collapse
You are right! I should add that here. Also, I got the latest SDK to verify and found fastboot.exe under the "tools" folder. Can tell me which SDK version you downloaded?

Usefull, thank you
Sent from my LG-P500 using XDA Premium App

Kudos to arvinoids.
This will be of great help in times of need.
Sent from my LG-P500 using Tapatalk

arvinoids said:
You are right! I should add that here. Also, I got the latest SDK to verify and found fastboot.exe under the "tools" folder. Can tell me which SDK version you downloaded?
Click to expand...
Click to collapse
I have SDK r10 and cannot found fastboot under tools
So i had to download it from htc's website.

d3s3rt_eagle said:
I have SDK r10 and cannot found fastboot under tools
So i had to download it from htc's website.
Click to expand...
Click to collapse
Wow, that's strange. I have r11 and it is included there. For your convenience, I have attached the fastboot.exe from r11 on the first post. Thanks for trying this out.

i have a question... if we don't see the fastboot line on our breaked phone and we see just stuck at LG Logo and the Recovery is broken too, what we can do?! how we can enter in fastboot mode in this situation?

hey
I run the CMD
executed cd command but the next command
"fastboot erase recovery"
gives the following error ( see the image)
Please help

@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate

DJoptimus-One said:
@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate
Click to expand...
Click to collapse
Did rom manager messed up your phone?
Sent from my LG-P500 using Tapatalk

lekhwani said:
Did rom manager messed up your phone?
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Yes. For the first time.

DJoptimus-One said:
Yes. For the first time.
Click to expand...
Click to collapse
How is your phone now?
Sent from my LG-P500 using Tapatalk

lekhwani said:
How is your phone now?
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Revived now

DJoptimus-One said:
Revived now
Click to expand...
Click to collapse
Good to hear that. I think this is your 2nd or 3rd day and you came across worst o1 modding scenario and overcame it. Kudos to you.
Sent from my LG-P500 using Tapatalk

AdbWinApi.dll is included in platform-tools
DJoptimus-One said:
@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate
Click to expand...
Click to collapse
Hi. Sorry I was away for the weekend and just got back. Thanks for reporting this. I just did a search on my desktop and found out that AdbWinApi.dll is included in the platform-tools package. I will add the instructions to download the package from the SDK. I'm glad you were able to revive your phone. Thanks again!

pymebrahimi said:
i have a question... if we don't see the fastboot line on our breaked phone and we see just stuck at LG Logo and the Recovery is broken too, what we can do?! how we can enter in fastboot mode in this situation?
Click to expand...
Click to collapse
I'm afraid your issue may not be a subject for this tutorial. Fastboot mode is activated when the phone's recovery image is broken. May I know how you are sure that the recovery is actually broken?

[Q] Erased recovery

Help Ive erased recovery and im not really experienced with fastboot I was trying to install clockworkmod and ended up deleting recovery please help ive got the kernal image from ASus but it is tar.gz please help im so confused I cant update or flash custom rom now its a nightmare just got this 2 or 3 days ago

4SHR4F said:
Help Ive erased recovery and im not really experienced with fastboot I was trying to install clockworkmod and ended up deleting recovery please help ive got the kernal image from ASus but it is tar.gz please help im so confused I cant update or flash custom rom now its a nightmare just got this 2 or 3 days ago
Click to expand...
Click to collapse
So I assumed that your device is unlocked? I recommend to flash twrp, more easier and works wellstart with section 2).
http://forum.xda-developers.com/showthread.php?p=32825557

how did you delete recovery?
cyanogen mod forum has a good wiki on fastboot.

buhohitr said:
So I assumed that your device is unlocked? I recommend to flash twrp, more easier and works wellstart with section 2).
http://forum.xda-developers.com/showthread.php?p=32825557
Click to expand...
Click to collapse
I followed this thread before it says Scott's TF700T Recovery Install tool V1.0
www.scottsroms.com
Congrats! You now have a custom Recovery installed on the official
JB release by Asus!
From here you can install a custom ROM or simply root the stock ROM.
The choice is yours!
Thank you for using my Recovery Install Tool!
Please visit www.scottsroms.com!
Donations Greatly Appreciated but Never Expected!
But when I boot into recovery I get Un recoverable bootloader error (0x00000000)
Also when I used the program it does the first reboot but not the second I dont know why? Please HELP

4SHR4F said:
I followed this thread before it says Scott's TF700T Recovery Install tool V1.0
www.scottsroms.com
Congrats! You now have a custom Recovery installed on the official
JB release by Asus!
From here you can install a custom ROM or simply root the stock ROM.
The choice is yours!
Thank you for using my Recovery Install Tool!
Please visit www.scottsroms.com!
Donations Greatly Appreciated but Never Expected!
But when I boot into recovery I get Un recoverable bootloader error (0x00000000)
Also when I used the program it does the first reboot but not the second I dont know why? Please HELP
Click to expand...
Click to collapse
I don't think you did it correctly, first boot you should see the 4 icons and you need to hit the volume down button on your device (within 10sec) to select USB icon then hit the volume up button to select this setting, now proceed with the instruction on your pc to flash. Make sure you copy the recovery twrp file named" openrecovery-twrp-2.3.1.0-tf700t.blob" from here http://goo.im/devs/OpenRecovery/tf700t to the "install Recovery" folder and RENAME this file to recovery.blob

buhohitr said:
I don't think you did it correctly, first boot you should see the 4 icons and you need to hit the volume down button on your device (within 10sec) to select USB icon then hit the volume up button to select this setting, now proceed with the instruction on your pc to flash. Make sure you copy the recovery twrp file named" openrecovery-twrp-2.3.1.0-tf700t.blob" from here http://goo.im/devs/OpenRecovery/tf700t to the "install Recovery" folder and RENAME this file to recovery.blob
Click to expand...
Click to collapse
OK last time im trying this wish me luck
Edit: Same problem grrrrrr it says its sent hasnt reboot my device as well so have to do it manually and still says same error

4SHR4F said:
OK last time im trying this wish me luck
Edit: Same problem grrrrrr it says its sent hasnt reboot my device as well so have to do it manually and still says same error
Click to expand...
Click to collapse
Sounds like your pc is not communicate correctly with your device. When your device is on and you execute Scott's bat file, is your device reboot into recovery so that you can select fastboot mode? Basically, Scott bat file is using adb command to reboot your device into recovery mode, you manually select and enable fast boot mode on your device, then the script is using fastboot command to push the recovery.blob (located in the same directory as Scott bat file) to your device.

buhohitr said:
Sounds like your pc is not communicate correctly with your device. When your device is on and you execute Scott's bat file, is your device reboot into recovery so that you can select fastboot mode? Basically, Scott bat file is using adb command to reboot your device into recovery mode, you manually select and enable fast boot mode on your device, then the script is using fastboot command to push the recovery.blob (located in the same directory as Scott bat file) to your device.
Click to expand...
Click to collapse
Yes it reboots the first time allowing me to go into recovery but then doesnt reboot second after it writes the recovery files dont know why fastboot works thats why I can delete recovery but writing is a problem :~

4SHR4F said:
Yes it reboots the first time allowing me to go into recovery but then doesnt reboot second after it writes the recovery files dont know why fastboot works thats why I can delete recovery but writing is a problem :~
Click to expand...
Click to collapse
And you did select the USB icon and the text displayed "fastboot" on your device? You also have the twrp renamed to recovery.blob in the same folder as the script? Let manually push this file using fastboot.exe and see what's happens.

buhohitr said:
And you did select the USB icon and the text displayed "fastboot" on your device? You also have the twrp renamed to recovery.blob in the same folder as the script? Let manually push this file using fastboot.exe and see what's happens.
Click to expand...
Click to collapse
With fastboot same problem when I load from command prompt it sends the file however if I do it without starting from that directory it says file not found but fastboot devices show the number should I make a video and send it

4SHR4F said:
With fastboot same problem when I load from command prompt it sends the file however if I do it without starting from that directory it says file not found but fastboot devices show the number should I make a video and send it
Click to expand...
Click to collapse
don't trust the log from fastboot or any script. Just make sure the recovery.blog is in the same directory of the fastboot command and you must execute fastboot.exe from command prompt.
1. manually boot to fastboot mode from your device. (boot to recovery then select USB icon)
2. Open command prompt and run as admin and navigate to fastboot.exe directory (with recovery.blog in this directory also)
3. type;
fastboot.exe -i 0x0B05 flash recovery recovery.blob
4. Once done, type
fastboot -i 0x0B05 reboot
Let me know the status.

buhohitr said:
don't trust the log from fastboot or any script. Just make sure the recovery.blog is in the same directory of the fastboot command and you must execute fastboot.exe from command prompt.
1. manually boot to fastboot mode from your device. (boot to recovery then select USB icon)
2. Open command prompt and run as admin and navigate to fastboot.exe directory (with recovery.blog in this directory also)
3. type;
fastboot.exe -i 0x0B05 flash recovery recovery.blob
4. Once done, type
fastboot -i 0x0B05 reboot
Let me know the status.
Click to expand...
Click to collapse
This is what I get recovery.blob is in the folder and fastboot works as I can delete recovery just not write for some reason
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
H:\Users\Install user>cd C:\Fastboot
H:\Users\Install user>fastboot devices
015d262e99141416 fastboot
H:\Users\Install user>fastboot.exe -i 0x0B05 flash recovery recovery.blob
error: cannot load 'recovery.blob': No error
H:\Users\Install user>
Also I would also like to point out it does not let me reboot after I write the files (using holding shift key and opening command prompt) as it freezes I think??? BEcause I can reboot from fastboot before I input writing flash recovery but after it wont allow don't know why?

4SHR4F said:
This is what I get recovery.blob is in the folder and fastboot works as I can delete recovery just not write for some reason
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
H:\Users\Install user>cd C:\Fastboot
H:\Users\Install user>fastboot devices
015d262e99141416 fastboot
H:\Users\Install user>fastboot.exe -i 0x0B05 flash recovery recovery.blob
error: cannot load 'recovery.blob': No error
Click to expand...
Click to collapse
Did you even notice that you didn't change to drive C: before calling fastboot? Is your recovery.blob in C:\Fastboot or in "H:\Users\Install user"?

_that said:
Did you even notice that you didn't change to drive C: before calling fastboot? Is your recovery.blob in C:\Fastboot or in "H:\Users\Install user"?
Click to expand...
Click to collapse
Yes I know but my command prompt is awkward either way ive tried using Android flasher but I find the problem is my device freezes while writing files dont know why

4SHR4F said:
Yes I know but my command prompt is awkward either way ive tried using Android flasher but I find the problem is my device freezes while writing files dont know why
Click to expand...
Click to collapse
Try this, copy the recovery.blob to this directory:
H:\Users\Install user\
Then type dir then hit enter, make sure your fastboot.exe and recovery.blob are there
H:\Users\Install user> dir then hit enter
Should show both fastboot.exe and recovery.blob
Now execute the fastboot command to push the recovery.blob

buhohitr said:
Try this, copy the recovery.blob to this directory:
H:\Users\Install user\
Then type dir then hit enter, make sure your fastboot.exe and recovery.blob are there
H:\Users\Install user> dir then hit enter
Should show both fastboot.exe and recovery.blob
Now execute the fastboot command to push the recovery.blob
Click to expand...
Click to collapse
Same problem says its sent and that it is written but after if I try to reboot the tablet doesn't respond and cant go into recovery because of that error 0x00000000
All I want to do is get UBuntu and Clean ROM on my Tablet then no more modding

OK I give up with command prompt can I use Odin or some other software to flash recovery or at least flash a custom rom from windows rather then twrp or cwm boatloaders or can I get ubuntu and do it through ubuntu any possibilities helpful please

4SHR4F said:
OK I give up with command prompt can I use Odin or some other software to flash recovery or at least flash a custom rom from windows rather then twrp or cwm boatloaders or can I get ubuntu and do it through ubuntu any possibilities helpful please
Click to expand...
Click to collapse
Nope, no Odin, but if your device is rooted, you could download goomanager from the market and install twrp using goomanager app.

buhohitr said:
Nope, no Odin, but if your device is rooted, you could download goomanager from the market and install twrp using goomanager app.
Click to expand...
Click to collapse
What about install linux without root and from there send in the recovery that way will that work

4SHR4F said:
What about install linux without root and from there send in the recovery that way will that work
Click to expand...
Click to collapse
You can be the first one to try...it may or may not works, but the methods I provided proved by many that they worked.

[Q] HELP HELP HELP Bricked

Ok here goes.. I have a ASUS TF101 and tryed to install Cyanogenmod 9 on it and to my amazment it worked but then it shut off after a min and now is stuck on the 1st boot screen (EEE Pad) I tryed to restore stock rom in recovery but nothing happened then I tryed using easyflasher and couldn't enter into apx mode the only thing I can do is enter recovery mode and see that its running ClockworkMod recovery 6.0.1.3
Please help me

Meat6911 said:
Ok here goes.. I have a ASUS TF101 and tryed to install Cyanogenmod 9 on it and to my amazment it worked but then it shut off after a min and now is stuck on the 1st boot screen (EEE Pad) I tryed to restore stock rom in recovery but nothing happened then I tryed using easyflasher and couldn't enter into apx mode the only thing I can do is enter recovery mode and see that its running ClockworkMod recovery 6.0.1.3
Please help me
Click to expand...
Click to collapse
How did you install CWM 6.0.1.3? Did you use ROM Manager? If so, that is your problem.
You need to get a working recovery installed.
Are you sure you could not get into APX Mode? It is a black screen and the only indication is that your computer detects new hardware.
If you cannot get into APX to use EasyFlasher or NVFlash, is your tablet recognized as an ADB device in CWM? If so you can push a new recovery using the dd command. I would recommend checking out TWRP.
To install TWRP via ADB, download the latest TWRP from here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save it as TWRP.blob in an easy to find place (like c:\TWRP.blob)
Connect your tablet to your PC and update the driver and use the Universal Naked Drivers
Put the adb.exe file in the c:\ folder as well (in the EasyFlasher Tools folder)
Open a command prompt (WIN+R, type CMD and click OK)
Code:
adb devices
(if connected, should show a device connected)
adb push c:\TWRP.blob /sdcard/
adb shell
cd /sdcard/
ls -a -l
(check for TWRP.blob)
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Do not try to enter recovery until after it reboots past the Eee Pad logo (and shows the progress indicator). This is when it acutally updates the recovery.
Once you see it get past the Eee Pad screen hold VOL DOWN and POWER for about 12-15 seconds and then press VOL UP once you see the small text and it should boot to TWRP recovery.​
Here are the ADB commands to run:

When I connect to PC it makes the connection sound but doesn't show as a removable drive so I can't use Easyflash or any program like that also like I said APX mode wont work it makes the sound that it detects the tablet but then makes the remove sound right away. and this happened when I installed the Cyangenmod 9. I found someone who says he may be able to fix it for $50 using Odin but I am worried that he wont be able to and its an hour drive to take it to him... At this point I just want it back to stock ...

erm... ODIN won't work with a transformer, it's only for samsung devices.
Alright, you probably used ROM manager judging by your Recovery version.
You need to just NvFlash the device back to stock:
Download your region's Stock ROM from here: (WW if outside of US, US if inside.) Stock Rom
Download Wheelie NvFlash tool from here: Wheelie
Unzip the stock rom .zip first, into it's own folder. Then unzip the wheelie tar.bz2 into the folder you just made by unzipping the stock rom. Overwrite any files with the wheelie files.
Next find out your Sbk variant, Look at the serial number on the sticker on the bottom of your tablet.
If it says B70, or a higher number like B80 or any C, then you are Sbkv2
If the number is B60 or lower, you are Sbkv1.
Remember this for the next step.
Make sure the tablet is off totally, Then hold the Volume-UP key and Then press power, keep holding volume up. It will enter APX mode.
Plug it into your computer, the screen will stay blank.
It should be detected, if it says unknown device or similar, use the windows device manager to select the 'asus bootloader interface' or 'Unknown device' or similar, with Nvidia ASUS or APX or Bootloader, something along those lines, to update the driver, right click this and navigate to the 'usbpcdriver' folder in the folder you unzipped earlier. It will install and detect.
Then run the .bat file that says Reflash_(Your Sbk version).bat while the tab is connected in apx mode.
It will return to stock, give it time, DO NOT UNPLUG IT.
The screen may flash, and the tablet may/will reboot.
When done you will be on Stock latest from ASUS.
If you want safe root / recovery, download and run my PERI tool, link in signature.
good luck.

ok I am trying that now but I wish I had someone to walk me through everything in real time...

OMG you are the best Thing O Doom I bow down to your all mighty knowledge lol thank you

Meat6911 said:
OMG you are the best Thing O Doom I bow down to your all mighty knowledge lol thank you
Click to expand...
Click to collapse
erm, I guess it worked?
The best thing you can do for someone on xda is hit the 'thanks' or donate buttons, and thanks is free!
Any other questions, I'm guessing it worked alright?

frederuco said:
How did you install CWM 6.0.1.3? Did you use ROM Manager? If so, that is your problem.
You need to get a working recovery installed.
Are you sure you could not get into APX Mode? It is a black screen and the only indication is that your computer detects new hardware.
If you cannot get into APX to use EasyFlasher or NVFlash, is your tablet recognized as an ADB device in CWM? If so you can push a new recovery using the dd command. I would recommend checking out TWRP.
To install TWRP via ADB, download the latest TWRP from here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save it as TWRP.blob in an easy to find place (like c:\TWRP.blob)
Connect your tablet to your PC and update the driver and use the Universal Naked Drivers
Put the adb.exe file in the c:\ folder as well (in the EasyFlasher Tools folder)
Open a command prompt (WIN+R, type CMD and click OK)
Code:
adb devices
(if connected, should show a device connected)
adb push c:\TWRP.blob /sdcard/
adb shell
cd /sdcard/
ls -a -l
(check for TWRP.blob)
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Do not try to enter recovery until after it reboots past the Eee Pad logo (and shows the progress indicator). This is when it acutally updates the recovery.
Once you see it get past the Eee Pad screen hold VOL DOWN and POWER for about 12-15 seconds and then press VOL UP once you see the small text and it should boot to TWRP recovery.​
Here are the ADB commands to run:
Click to expand...
Click to collapse
I had similiar problem when I tried to downgrade and go back to stock. After flashing stock from asus, I did it wrong by unzipping (stock_ics_kernel_9.2.1.24US-secure) first then flash the file under the downloaded zip files. Now I am also stuck at Eee Pad, can't get into recovery because it probably wiped out everything. Hopefully this can recover my Eee Pad!!!! I got my fingers cross. This may be my only hope for my asus pad .

Ok so off topic question how can I watch videos online from like 1channel or other streaming sites and what is the best ad blocker and antivirus to use

Meat6911 said:
Ok so off topic question how can I watch videos online from like 1channel or other streaming sites and what is the best ad blocker and antivirus to use
Click to expand...
Click to collapse
You should be able to with Dolphin HD browser and Flash installed, make sure flash is integrated into the Dolphin. That or the sites should just work..
I use Adaway.

Flatline - Unbrickable Transformer TF700 - Jellybean edition

The AndroidRoot.Mobi Team is proud to present Flatline: Nvflash for TF700 Jellybean!
This release allows generating nvflash blobs for your specific device, making your device unbrickable as long as you have a copy of the blobs.
As a brand new feature, it will also enable wifi and upload a copy of the blob to androidroot's server. Later, a solution will be released to retrieve the blobs from the server if you ever loose them.
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Credit goes to the AndroidRoot.Mobi team:
Bumble-Bee (Apache14), IEF, kmdm, lilstevie & RaYmAn.

For the love of God somebody please confirm this is true. I'm pinching myself trying to make sure this isn't a dream.

Im lost for words...... will test asap. The AndroidRoot.Mobi team are champions

Will this work with the 10.6.1.14.10 bootloader?

laod said:
Will this work with the 10.6.1.14.10 bootloader?
Click to expand...
Click to collapse
Guide says you need to use their modified 10.6.1.14.4 bootloader. I'm just waiting for 1 person I "know" to try this and then I will. I may do it tomorrow anyway...

workdowg said:
Guide says you need to use their modified 10.6.1.14.4 bootloader. I'm just waiting for 1 person I "know" to try this and then I will. I may do it tomorrow anyway...
Click to expand...
Click to collapse
OK thanks, I didn't notice that little tidbit of information. I'm waiting for someone to confirm this is working. Then I will install.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Ok guys CONFIRMED WORKING! make sure you follow the instructions like your performing heart surgery and you should be fine. (they have made it a lot easier then the ICS method!) and Make 6+ copies of the recommend backups
NOTE: I done it from CROMI-X 5.0.3 which i believe uses 10.6.1.14.10 bootloader. But it should work on any JB bootloader(But dont hold me too it ).

JoinTheRealms said:
Ok guys CONFIRMED WORKING! make sure you follow the instructions like your performing heart surgery and you should be fine. (they have made it a lot easier then the ICS method!) and Make 6+ copies of the recommend backups
NOTE: I done it from CROMI-X 5.0.3 which i believe uses 10.6.1.14.10 bootloader. But it should work on any JB bootloader(But dont hold me too it ).
Click to expand...
Click to collapse
When it finished generating my blobs I tried doing adb pull /tmp/AndroidRoot i get "error: device not found"

what does "adb devices" say?
btw did you try "adb pull /data/media/AndroidRoot"? thats what i used..

JoinTheRealms said:
what does "adb devices" say?
btw did you try "adb pull /data/media/AndroidRoot"? thats what i used..
Click to expand...
Click to collapse
It doesn't show anything. Do i have to reboot the tablet back into fastboot mode?
Yes i tried "adb pull /data/media/AndroidRoot"

laod said:
It doesn't show anything. Do i have to reboot the tablet back into fastboot mode?
Yes i tried "adb pull /data/media/AndroidRoot"
Click to expand...
Click to collapse
Well you most likely dont have an adb driver installed the tf700 universel naked driver contains adb/ fastboot and apx drivers but you have to install them individually. check device manager and manually update the apx driver if its got the yellow triangle. You will have to do the same when you boot into apx mode.
At that point you can probably reboot into android (again im not responsible for any mishaps ) and copy the files over via mtp as you need the blob.bin file stored in /data/media/AndroidRoot to bootstrap nvflash.

JoinTheRealms said:
Well you most likely dont have an adb driver installed the tf700 universel naked driver contains adb/ fastboot and apx drivers but you have to install them individually. check device manager and manually update the apx driver if its got the yellow triangle. You will have to do the same when you boot into apx mode.
At that point you can probably reboot into android (again im not responsible for any mishaps ) and copy the files over via mtp as you need the blob.bin file stored in /data/media/AndroidRoot to bootstrap nvflash.
Click to expand...
Click to collapse
Im using ubuntu not windows. If they are just stored on the internal memory then I'll reboot and copy them over to an sd card.
Edit: I have everything working now.

Now I have a new problem with trying to bootstrap into nvflash. When I use my terminal and type in "wheelie --blob blob.bin" i get the error "wheelie: command not found"

laod said:
Now I have a new problem with trying to bootstrap into nvflash. When I use my terminal and type in "wheelie --blob blob.bin" i get the error "wheelie: command not found"
Click to expand...
Click to collapse
You need to download this http://download.androidroot.mobi/nvflash-tools-linux.tar.bz2 and cd into the extracted directory and run that above command to use the wheelie binary.
Make sure the blob.bin you previously generated is in that directory also.

JoinTheRealms said:
You need to download this http://download.androidroot.mobi/nvflash-tools-linux.tar.bz2 and cd into the extracted directory and run that above command to use the wheelie binary.
Make sure the blob.bin you previously generated is in that directory also.
Click to expand...
Click to collapse
I already have all that setup.b

laod said:
I already have all that setup.b
Click to expand...
Click to collapse
Sorry i dont have a linux machine near atm, make sure it a has executable permissions and try adding ./ before the command.

JoinTheRealms said:
Sorry i dont have a linux machine near atm, make sure it a has executable permissions and try adding ./ before the command.
Click to expand...
Click to collapse
adding ./ before seemed to have fixed my issue. Accept i keep getting "libusbx requires write access to usb device nodes. It keeps printing that and some numbers on the left

laod said:
adding ./ before seemed to have fixed my issue. Accept i keep getting "libusbx requires write access to usb device nodes. It keeps printing that and some numbers on the left
Click to expand...
Click to collapse
Unfortunately, that error message isn't the best in the world. I'll try and get around to adding a FAQ to cover issues like this...
What it means is that wheelie doesn't have the rights to access the NVflash mode. It can fixed by adding Vendor 0955 to a file similar to '51-android.rules" similar to getting adb working as non-root.
Alternatively, if you run wheelie and nvflash as root it will work. We'll provide a better explanation later.

rayman said:
Unfortunately, that error message isn't the best in the world. I'll try and get around to adding a FAQ to cover issues like this...
What it means is that wheelie doesn't have the rights to access the NVflash mode. It can fixed by adding Vendor 0955 to a file similar to '51-android.rules" similar to getting adb working as non-root.
Alternatively, if you run wheelie and nvflash as root it will work. We'll provide a better explanation later.
Click to expand...
Click to collapse
Thank you for the explanation. It is all working just fine now

Done. Make sure to follow the steps like you are defusing a bomb... Thank you AndroidRoot team!
---------- Post added at 05:31 PM ---------- Previous post was at 05:26 PM ----------
Alert: Possible stupid question. Now that I'm all nvflash set... I can reflash TWRP and the newest bootloader. Then if I brick, do I have to reflash the custom recovery and bootloader?

[Q] fastboot access trouble

This probably sounds stupid, but its been 4 days and i cannot for the life of me figure out this whole fastboot thing. I've searched and searched and cant seem to find anything. My goal is to flash a better ROM on my infinity, and i cant get past step 2. I've already unlocked the device, and now im trying to go through the whole nvflash fastboot procedure. I'm following this guide: https:// www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
I have the tablet in fastboot mode, and all the necessary files according to the guide, but where it says to run the "fastboot flash recovery flatline_device.img" command all i get is "fastboot isn't a recognized command" error, which makes sense because i don't have any file called "fastboot" and have no idea what to do.
I'm starting to pull out my hair over here could someone help me out?

I downloaded the ADT package from Android.com which gives me the adt commands, but i am still unable to figure out the "fastboot" command. I'm still getting a "fastboot is not a recognized command/program" error in CMD. Am i missing a program on my PC or should it work with Universal Naked Driver package?

mateusmaximus said:
I downloaded the ADT package from Android.com which gives me the adt commands, but i am still unable to figure out the "fastboot" command. I'm still getting a "fastboot is not a recognized command/program" error in CMD. Am i missing a program on my PC or should it work with Universal Naked Driver package?
Click to expand...
Click to collapse
ADT is a plugin for Eclipse. You need to install the platform-tools, which include adb and fastboot.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

_that said:
ADT is a plugin for Eclipse. You need to install the platform-tools, which include adb and fastboot.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Sorry, youre right, i downloaded the SDK package that has ADT & platform-tools. since im not gonna be developing, could you give me a quick walkthrough on what i need to do to get it set up correctly so i can flash nvflash? or shoot me a link that has the steps.

mateusmaximus said:
Sorry, youre right, i downloaded the SDK package that has ADT & platform-tools. since im not gonna be developing, could you give me a quick walkthrough on what i need to do to get it set up correctly so i can flash nvflash? or shoot me a link that has the steps.
Click to expand...
Click to collapse
So if you have installed the SDK platform-tools, fastboot and adb should work - maybe you need to add the platform-tools directory to your PATH. If you have the correct USB driver installed, "adb devices" should find your tablet when Android is running and "USB debugging" is activated, and "fastboot devices" should find your tablet when you are in the bootloader menu. When this works, you can continue with the guide on androidroot.

_that said:
So if you have installed the SDK platform-tools, fastboot and adb should work - maybe you need to add the platform-tools directory to your PATH. If you have the correct USB driver installed, "adb devices" should find your tablet when Android is running and "USB debugging" is activated, and "fastboot devices" should find your tablet when you are in the bootloader menu. When this works, you can continue with the guide on androidroot.
Click to expand...
Click to collapse
Great, i'll give it a shot today. This is my first time dealing with ADB stuff, and there was no mention of needing the SDK platform-tools in the "all in one guide" by Pretoriano80 for the tf700, or the guide on andoidroot. So thanks for the help! :good: Ill post back my results later.