C:\Program Files\Minimal ADB and Fastboot>adb sideload Blur_Version.21.12.40.con
dor_retaildsds.retaildsdsall.en.03.zip
loading: 'Blur_Version.21.12.40.condor_retaildsds.retaildsd sall.en.03.zip'
error: device not found.
Even If My Device Is Connected To pc :/ then too
Related
Hey all i ran into a problem yesterday i downgraded my fire hdx tablet to 13.3.2.8 and everything went fine except that my boot image and recovery partitions got messed up so now when i turn it on it goes straight into fastboot mode i have the 32 GB model 2013 edition which is a 7 inch thor based tablet i heard someone was able to flash fastboot via linux but i cant get it to work on windows 7 64 bit so im going to try flashing a new boot image and recovery partition via linux to see if that will fix the problem but i would appreciate the assistance. Thanks
blue9a said:
Hey all i ran into a problem yesterday i downgraded my fire hdx tablet to 13.3.2.8 and everything went fine except that my boot image and recovery partitions got messed up so now when i turn it on it goes straight into fastboot mode i have the 32 GB model 2013 edition which is a 7 inch thor based tablet i heard someone was able to flash fastboot via linux but i cant get it to work on windows 7 64 bit so im going to try flashing a new boot image and recovery partition via linux to see if that will fix the problem but i would appreciate the assistance. Thanks
Click to expand...
Click to collapse
There is no known (or at least widely recognized) recovery from a catastrophic 3.2.8 boot failure. As the bootloader remains locked (and hence fastboot crippled) I do not believe you will have success restoring recovery or flashing a new boot image. Sorry - I'm afraid you now own a brick.
Davey126 said:
There is no known (or at least widely recognized) recovery from a catastrophic 3.2.8 boot failure. As the bootloader remains locked (and hence fastboot crippled) I do not believe you will have success restoring recovery or flashing a new boot image. Sorry - I'm afraid you now own a brick.
Click to expand...
Click to collapse
im testing it on ubuntu linux 14.04 LTS its reporting failure unknown command then ready so i guess thats something
blue9a said:
im testing it on ubuntu linux 14.04 LTS its reporting failure unknown command then ready so i guess thats something
Click to expand...
Click to collapse
Believe response would be similar regardless of host. With a locked bootloader only a few fastboot commands work - none of them useful. Maybe you'll find a workaround!
Davey126 said:
Believe response would be similar regardless of host. With a locked bootloader only a few fastboot commands work - none of them useful. Maybe you'll find a workaround!
Click to expand...
Click to collapse
python3 /home/jeremy/Desktop/cuberHDX.py 0x45202b1325
File "/home/jeremy/Desktop/cuberHDX.py", line 64
print 'Usage: %s [boot.img|serial]' % path.basename(argv[0])
^
SyntaxError: invalid syntax
hmm not sure if i did this right
[email protected]:~$ fastboot -i 0x1949 oem device-info
...
(bootloader) Device tampered: true
OKAY [ 0.036s]
finished. total time: 0.036s
[email protected]:~$ -i 0x1949 oem unlock 0x45202b1325
-i: command not found
[email protected]:~$ /fastboot -i 0x1949 devices
bash: /fastboot: No such file or directory
[email protected]:~$ fastboot -i 0x1949 devices
D0FCA0A03523013E fastboot
[email protected]:~$ fastboot -i 0x1949 flash unlock unlock.signed
target reported max download size of 536870912 bytes
error: cannot load 'unlock.signed': No such file or directory
[email protected]:~$ fastboot -i 0x1949 flash boot '/media/jeremy/MULTIBOOT/boot.img'
target reported max download size of 536870912 bytes
sending 'boot' (6884 KB)...
OKAY [ 0.290s]
writing 'boot'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.341s
[email protected]:~$ fastboot -i 0x1949 flash unlock '/media/jeremy/MULTIBOOT/unlock.img'
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.084s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.141s
[email protected]:~$ python cuberHDX.py 45202b1325
python: can't open file 'cuberHDX.py': [Errno 2] No such file or directory
[email protected]:~$ python cuber.py 45202b1325
python: can't open file 'cuber.py': [Errno 2] No such file or directory
[email protected]:~$ '/media/jeremy/MULTIBOOT/cuber.py' 45202b1325
bash: /media/jeremy/MULTIBOOT/cuber.py: Permission denied
[email protected]:~$ '/home/jeremy/Desktop/cuber.py' 45202b1325
bash: /home/jeremy/Desktop/cuber.py: Permission denied
[email protected]:~$ python '/home/jeremy/Desktop/cuber.py' 45202b1325
Usage: cuber.py [bits] [<data] [>sig]
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Traceback (most recent call last):
File "/home/jeremy/Desktop/cuberHDX.py", line 7, in <module>
from gmpy2 import iroot, mpz
ImportError: No module named gmpy2
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Traceback (most recent call last):
File "/home/jeremy/Desktop/cuberHDX.py", line 7, in <module>
from gmpy2 import iroot, mpz
ImportError: No module named gmpy2
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Traceback (most recent call last):
File "/home/jeremy/Desktop/cuberHDX.py", line 7, in <module>
from gmpy2 import iroot, mpz
ImportError: No module named gmpy2
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Your unlock code is in '45202b1325.unlock'.
[email protected]:~$ fastboot -i 0x1949 flash unlock '/home/jeremy/45202b1325.unlock'
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.085s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.142s
[email protected]:~$ /cuber_unlockbl --sign ./'/home/jeremy/Desktop/unlock.img' ./ '/home/jeremy/45202b1325.unlock'
bash: /cuber_unlockbl: No such file or directory
[email protected]:~$ python ./cuber_unlockbl --sign '/home/jeremy/Desktop/unlock.img' '/home/jeremy/Desktop/45202b1325.unlock'
python: can't open file './cuber_unlockbl': [Errno 2] No such file or directory
[email protected]:~$ python cuber.py ./cuber_unlockbl --sign '/home/jeremy/Desktop/unlock.img' '/home/jeremy/Desktop/45202b1325.unlock'
python: can't open file 'cuber.py': [Errno 2] No such file or directory
[email protected]:~$ python cuber.py --sign '/home/jeremy/Desktop/unlock.img' '/home/jeremy/Desktop/45202b1325.unlock'
python: can't open file 'cuber.py': [Errno 2] No such file or directory
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py ./cuber_unlockbl --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock
Usage: cuberHDX.py [boot.img|serial]
[email protected]:~$ python /home/jeremy/Desktop/cuber.py ./cuber_unlockbl --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock
Usage: cuber.py [bits] [<data] [>sig]
[email protected]:~$ python /home/jeremy/Desktop/cuber.py --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock Usage: cuber.py [bits] [<data] [>sig]
[email protected]:~$ python /home/jeremy/Desktop/cublock.py --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock
Usage: cublock.py manfid serial
[email protected]:~$
well i added a txt file that contains my device info if you can get a .unlock and .img file that would really help me btw my fire os was 13.3.2.8
blue9a said:
well i added a txt file that contains my device info if you can get a .unlock and .img file that would really help me btw my fire os was 13.3.2.8
Click to expand...
Click to collapse
Can't unlock bootloader versions >3.2.3.2; can't flash with a locked BL. Your device is bricked.
I was following this thread: http://forum.xda-developers.com/show...8#post53728658 to upgrade my LG to Android 5.0. I've downloaded latest drivers for my phone and official .kdz, after choosing CSE Flash upgrading begun, but something went wrong and upgrading stopped at 1% with flashtool crash. Phone rebooted and stuck at
[720] fastboot_init()
[720] Loading keystore failed status 5 [820] USB init ept @ 0x8f1f7000
[840] udc_start()
After connecting to my laptop:
[10680] --reset --
[10690] --portchange --
[10780] --reset --
[10780] --portchange --
[10690] fastboot: processing commands
Phone is visible only with fastboot devices without possibility to boot into download mode
I've tried to boot from twrp open recovery, but command fastboot boot openrecovery.img gives following result
in cmd console:
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.421s
phone:
[190060] fastboot: download:00c5f800
[190470] fastboot: boot
Help me please Is it possible to fix this issue?
LG F60 Android 4.4.4
PC Windows 7 x64
TerraBit97 said:
I was following this thread: http://forum.xda-developers.com/show...8#post53728658 to upgrade my LG to Android 5.0. I've downloaded latest drivers for my phone and official .kdz, after choosing CSE Flash upgrading begun, but something went wrong and upgrading stopped at 1% with flashtool crash. Phone rebooted and stuck at
[720] fastboot_init()
[720] Loading keystore failed status 5 [820] USB init ept @ 0x8f1f7000
[840] udc_start()
After connecting to my laptop:
[10680] --reset --
[10690] --portchange --
[10780] --reset --
[10780] --portchange --
[10690] fastboot: processing commands
Phone is visible only with fastboot devices without possibility to boot into download mode
I've tried to boot from twrp open recovery, but command fastboot boot openrecovery.img gives following result
in cmd console:
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.421s
phone:
[190060] fastboot: download:00c5f800
[190470] fastboot: boot
Help me please Is it possible to fix this issue?
LG F60 Android 4.4.4
PC Windows 7 x64
Click to expand...
Click to collapse
Same problem here, i tried everything and no help.
Anyone?
I was flashing custom roms and was trying to fix my the dm-verity and forced encryption problem for Oneplus 3T as TWRP used to ask for my pattern. I came across this video and it said to use the command:
fastboot format userdata
Me being me noticed that it didn't work..... so
I went on the internet and found a command called:
fastboot erase userdata......worst mistake of my life!
I need help to repartition my ext4 partition for Oneplus 3T. I have included the cmd adb text:
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
4863ecc8 device
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot format userdata
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 12.435s]
finished. total time: 12.435s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot recovery
fastboot: usage: unknown command recovery
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery
error: cannot load 'recovery': No such file or directory
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot
fastboot: usage: expected argument
C:\Program Files (x86)\Minimal ADB and Fastboot>boot
'boot' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot
fastboot: usage: no command
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot format userdata
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot format
fastboot: usage: expected argument
C:\Program Files (x86)\Minimal ADB and Fastboot>
Erasing 'system' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'system_ext' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'odm' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'product' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Can someone help? i downloaded the new adb drivers, adb is updated. bootloader is unlocked.
1.
ADB and Fastboot are different drivers that serve different purpose
2.
How Fastboot commands are implemented depends on manufacturer. In any case download and install the "Android USB Driver" suitable to your Android device.
jwoegerbauer said:
1.
ADB and Fastboot are different drivers that serve different purpose
2.
How Fastboot commands are implemented depends on manufacturer. In any case download and install the "Android USB Driver" suitable to your Android device.
Click to expand...
Click to collapse
The thing is fastboot works for other things but when I try to flash this from which formats it, it fails on erasing system and the other images. I've always used the adb 15 second installer on xda.
I'm pretty sure the Fastboot you've installed is for Google devices. If your device isn't a Google one then install, as by me suggested earlier, the driver provided by your device's manufacturer.
Hello,
My old Huawei P20 Lite were brick...Then I bought from second hand same Huawei P20 Lite, but it is demo unit. Is it possible reset phone, or flash this phone, uninstall demo app?
Thank you for helping me.
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase data
erasing 'data'...
FAILED (remote: Command not allowed)
finished. total time: 0.012s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
erik.aragorn said:
Hello,
My old Huawei P20 Lite were brick...Then I bought from second hand same Huawei P20 Lite, but it is demo unit. Is it possible reset phone, or flash this phone, uninstall demo app?
Thank you for helping me.
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase data
erasing 'data'...
FAILED (remote: Command not allowed)
finished. total time: 0.012s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/huawei-p20-lite-exhibition-mode-flash-to-normal-android.4376807/
https://forum.xda-developers.com/t/p20-lite-uninstall-demo-mode.4461987/
No comment...
-Alf- said:
https://forum.xda-developers.com/t/huawei-p20-lite-exhibition-mode-flash-to-normal-android.4376807/
https://forum.xda-developers.com/t/p20-lite-uninstall-demo-mode.4461987/
No comment...
Click to expand...
Click to collapse
Sorry, my fault, pls delete
erik.aragorn said:
bootloader) :ANE-LX1 9.1.0.397(C432E7R1P7)
OKAY [ 0.015s]
finished. total time: 0.016s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.014s]
finished. total time: 0.015s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.013s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem oeminforead-CUSTOM_VERSION
...
(bootloader) :ANE-LX1-CUST 9.1.0.7(C432)
OKAY [ 0.015s]
finished. total time: 0.016s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
Click to expand...
Click to collapse
Single SIM/dual SIM?
-Alf- said:
Single SIM/dual SIM?
Click to expand...
Click to collapse
dual sim
Strange, according to the data from fastboot you have the normal global version, not the Demo. Are you sure?
Yes I´m sure. Phone have installed app Retail Demo.
erik.aragorn said:
Yes I´m sure. Phone have installed app Retail Demo.
Click to expand...
Click to collapse
A) If your phone is fully functional, it should be enough to disable the Demo application:
Go to Settings -> Device administrators and disable administrator for demo apps (Retail mode and HwRetailAssistant).
- dial *#*#2846579#*#*, then "Background Setting", "USB Port Setting" and select "Manufacture Mode".
On the computer:
- Install ADB and connect your phone to your computer.
- Run the following commands:
adb devices
adb shell
pm uninstall -k --user 0 com.huawei.retaildemo
pm uninstall -k --user 0 com.huawei.retail.assistant
pm clear com.android.providers.contacts
Reboot.
Note: The package names of the demo apps may vary (for example, com.huawei.experience.mar.can). You can check the exact name using the "Package Inspector" application.
B) If the phone is not fully functional, try installing a service ROM
Downlad
Unpack downloaded package, find dload folder in "Software" , copy it to the SD card ( copy the folder as is, without unpacking it ! ). Turn off the phone and use 3-buttons to flas FW.
Warning: this process will erase all your personal data, so make a backup.
-Alf- said:
A) If your phone is fully functional, it should be enough to disable the Demo application:
Go to Settings -> Device administrators and disable administrator for demo apps (Retail mode and HwRetailAssistant).
- dial *#*#2846579#*#*, then "Background Setting", "USB Port Setting" and select "Manufacture Mode".
On the computer:
- Install ADB and connect your phone to your computer.
- Run the following commands:
adb devices
adb shell
pm uninstall -k --user 0 com.huawei.retaildemo
pm uninstall -k --user 0 com.huawei.retail.assistant
pm clear com.android.providers.contacts
Reboot.
Note: The package names of the demo apps may vary (for example, com.huawei.experience.mar.can). You can check the exact name using the "Package Inspector" application.
B) If the phone is not fully functional, try installing a service ROM
Downlad
Unpack downloaded package, find dload folder in "Software" , copy it to the SD card ( copy the folder as is, without unpacking it ! ). Turn off the phone and use 3-buttons to flas FW.
Warning: this process will erase all your personal data, so make a backup.
Click to expand...
Click to collapse
Device administrators and disable administrator for demo apps (Retail mode and HwRetailAssistant) it is not possible deactivate in this setting
c:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
9WV7N18A26005126 device
c:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
HWANE:/ $ pm uninstall -k --user 0 com.huawei.retaildemo
Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]
1|HWANE:/ $ pm uninstall -k --user 0 com.huawei.retail.assistant
Failure [not installed for 0]
1|HWANE:/ $ pm clear com.android.providers.contacts
Success
HWANE:/ $