i have tried evrythin possible i can... i keep getting some command
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
94975f80 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (31748 KB)...
OKAY [ 0.935s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.954s
C:\Program Files (x86)\Minimal ADB and Fastboot>
KedKaeDee said:
i have tried evrythin possible i can... i keep getting some command
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
94975f80 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (31748 KB)...
OKAY [ 0.935s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.954s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Are you in LP or MM? Judging by the error it looks like on MM if so follow this thread to root and flash twrp http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
Edit: This is the wrong section to post this in btw
Sorry i will delete the post. Thank yu for yur help
Ummm how do i delete the post? From the app? Or do i need to go into the browser to do so
KedKaeDee said:
Ummm how do i delete the post? From the app? Or do i need to go into the browser to do so
Click to expand...
Click to collapse
I don't think you can. Just ask a mod to delete it or leave it up since someone posted a link to the guide in case someone else has the same question.
Sent from my VK815 using XDA-Developers mobile app
^^
What he said.
Moved to Q/A section and leaving it open in case someone else has same question.
-karandpr
Related
Hey guys,
I have been trying to flash my Tablet for a few hours now. I would constantly get problems trying to flash. I'd reboot and go into fastboot again and then it would flash successfully. This works for everything (boot.img, recovery.img, system.img) however i can never get userdata.img to flash correctly. I am using the steps from nVidia to do this. Ill post the steps here as well as the exact error im getting.
Steps:
Code:
SHIELD TABLET RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD TABLET, connect your SHIELD TABLET
via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD TABLET into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method:
- Turn off the device
- Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
To flash this recovery image to your SHIELD TABLET, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Unlocking the Bootloader
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.
My CMD window:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 12.593s]
finished. total time: 12.594s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.022s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata
.img
target reported max download size of 570425344 bytes
erasing 'userdata'...
OKAY [ 12.548s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 23.951s]
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 46.546s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 570425344 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.425s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 10.476s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase recovery
erasing 'recovery'...
OKAY [ 5.034s]
finished. total time: 5.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 570425344 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.416s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 10.463s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
sending 'recovery' (9758 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 570425344 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.414s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 10.462s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.030s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 570425344 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.428s]
writing 'recovery'...
OKAY [ 0.281s]
finished. total time: 0.711s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 570425344 bytes
sending 'boot' (7608 KB)...
OKAY [ 0.339s]
writing 'boot'...
OKAY [ 0.226s]
finished. total time: 0.567s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 570425344 bytes
erasing 'system'...
OKAY [ 0.637s]
sending sparse 'system' (556772 KB)...
OKAY [ 24.041s]
writing 'system'...
OKAY [ 20.876s]
sending sparse 'system' (555305 KB)...
OKAY [ 24.219s]
writing 'system'...
OKAY [ 19.289s]
sending sparse 'system' (56409 KB)...
OKAY [ 2.431s]
writing 'system'...
OKAY [ 1.964s]
finished. total time: 93.461s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata
.img
target reported max download size of 570425344 bytes
erasing 'userdata'...
OKAY [ 10.050s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 23.801s]
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 43.929s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata
.img
target reported max download size of 570425344 bytes
erasing 'userdata'...
OKAY [ 5.048s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 23.702s]
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 38.796s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot staging blob
usage: fastboot [ <option> ] <command>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash staging blob
target reported max download size of 570425344 bytes
sending 'staging' (17491 KB)...
OKAY [ 0.742s]
writing 'staging'...
FAILED (remote: (FileWriteFailed))
finished. total time: 10.807s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash staging blob
target reported max download size of 570425344 bytes
sending 'staging' (17491 KB)...
OKAY [ 0.752s]
writing 'staging'...
OKAY [ 0.495s]
finished. total time: 1.249s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dtb tegra124-tn8-
p1761-1270-a04-e-battery.dtb
target reported max download size of 570425344 bytes
sending 'dtb' (68 KB)...
OKAY [ 0.027s]
writing 'dtb'...
OKAY [ 0.011s]
finished. total time: 0.039s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata
.img
target reported max download size of 570425344 bytes
erasing 'userdata'...
OKAY [ 12.662s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 23.825s]
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 46.542s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.002s]
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery G:\recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (26708 KB)...
OKAY [ 0.813s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.813s
(yes, the recovery.img is at disk G)
Try fastboot oem device-info
Sent from my Redmi Note 3 Pro using Tapatalk
I have a problem which through thorough google searches, I haven't been able to find an answer to. I'm trying to flash a custom recovery onto an LG G5, as probably presumed in the topic name, utilizing fastboot and it never seems to flash so I tried to go into the stock recovery and found that there wasn't a recovery at all. It simply shows the android bot with an open stomach and says no command. How would I go about getting a recovery on it, if at all possible?
Command Prompt Log:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (19100 KB)...
OKAY [ 0.721s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.744s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.024s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.759s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.795s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot format recovery
Formatting is not supported for file system with type ''.
Somebody know how to repair dummy partition?
when i try to flash dummy.img give me an error: its a redmi note 3 pro
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dummy dummy.img
target reported max download size of 536870912 bytes
sending 'dummy' (8 KB)...
OKAY [ 0.003s]
writing 'dummy'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.008s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Hello, i have a p20 lite that bricked after a night of charging, and I whould like to have some ideas to have informations to understand the problem.
If I press the vol - button and I connect the USB i have the phone into fastboot (Phone locked)
I downloaded the USB driver from here https://forum.xda-developers.com/t/...sb-driver-installer-tool-for-windows.3999445/
and Minimal_ADB_Fastboot_v1.4.3 but I can't have any useful information...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
Click to expand...
Click to collapse
fastboot oem get-build-number
...
FAILED (unknown status code)
finished. total time: 0.136s
Click to expand...
Click to collapse
brazoayeye said:
Hello, i have a p20 lite that bricked after a night of charging, and I whould like to have some ideas to have informations to understand the problem.
If I press the vol - button and I connect the USB i have the phone into fastboot (Phone locked)
I downloaded the USB driver from here https://forum.xda-developers.com/t/...sb-driver-installer-tool-for-windows.3999445/
and Minimal_ADB_Fastboot_v1.4.3 but I can't have any useful information...
Click to expand...
Click to collapse
Look here:
https://forum.xda-developers.com/t/...squares-only-able-to-access-fastboot.4226271/
https://forum.xda-developers.com/t/huawei-p20-lite-bricked.4331729/
https://forum.xda-developers.com/t/p20-lite-bootloop.4230037/post-84447333
brazoayeye said:
I downloaded the USB driver from here
Click to expand...
Click to collapse
install Hisuite on a computer and try again with Minimal ADB.
From https://forum.xda-developers.com/t/...squares-only-able-to-access-fastboot.4226271/
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
FAILED (unknown status code)
finished. total time: 0.136s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.136s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.144s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.148s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.145s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem battery_present_check
...
(bootloader) 3326mv
OKAY [ 0.015s]
finished. total time: 0.019s
Click to expand...
Click to collapse
I cannot enter in the recovery
Is there a way to extract data from the phone before trying with erase user data?
Thanks
brazoayeye said:
Is there a way to extract data from the phone before trying with erase user data?
Click to expand...
Click to collapse
Nope bro.
I cannot even erase userdata
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
What should I do to try to unbrick it?
brazoayeye said:
I cannot even erase userdata
What should I do to try to unbrick it?
Click to expand...
Click to collapse
I gave you a link, you didn't read, did you?
IMO it's hardware problem, so board FW won't help you...