It has taken a long since I tried to root my ZTE kis Q with no success. FramaRoot didn't work, so I tried adb and fastboot. However I think the recovery image from Clockworkmod is no working with my ZTE version, because it refuses to install it when I make
fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img I get
> sending 'recovery' (3768 KB)... OKAY [ 0.142s]
writing 'recovery'...
FAILED (remote: partition 'recovery' not support flash )
finished. total time: 0.155s
Since I'm using linux I don't have drivers issues
Does anyone have an opinion about it.
Thanks
Hi, hope somebody can help me.
First, I am no expert, so this will have to be help for dummies!
I have flashed lots of phones and unbricked a few following instructions on this site, but this has me beaten. A friend just got into flashing and tried to flash his moto G XT1032 to lollipop, very unsuccessfully. He wanted to do it himself
so I pointed him in the direction of this excellent site. Note his phone could enter fastboot at the time, unlocked (code 3 etc). He downloaded all the stuff, including Oversleeper's tools and...ran them including the bootloader refresher!! There is now no fastboot and the phone is bricked. I have managed to get to the stage where the phone is recognised as Qualcomm MS-USB QDLoader 9008 (COM8), but when I try to blank flash, the end line says "Error reading packet" and fails. I have looked all over on XDA for a solution but can't seem to find one. I know there are some absolute wizards on this site, so please somebody help? I can't give up. I don't know the meaning of the word!
Thank you all so much.
Gareth J
According to oversleeper's post, it says "The bricker should be used very carefully and only on Android 4.4.4 with 41.13 bootloader. DO NOT use it on higher versions, unless you wanna kill your phone definitively."
Is it possible that the phone has a 41.18 bootloader?
audit13 said:
According to oversleeper's post, it says "The bricker should be used very carefully and only on Android 4.4.4 with 41.13 bootloader. DO NOT use it on higher versions, unless you wanna kill your phone definitively."
Is it possible that the phone has a 41.18 bootloader?
Click to expand...
Click to collapse
It is possible but I really don't know. I got it in a very sorry state. I suppose there is hope in the fact that it can still be detected and seen as Qualcomm etc. Does there need to be an unpacked firmware in the same folder as the batch file or something? I can't understand the "error reading packet" statement. The only tool that he said he ran was the refresher tool. Goodness knows why, when he had the phone in fastboot mode ready for flashing a ROM.
garethjames said:
It is possible but I really don't know. I got it in a very sorry state. I suppose there is hope in the fact that it can still be detected and seen as Qualcomm etc. Does there need to be an unpacked firmware in the same folder as the batch file or something? I can't understand the "error reading packet" statement. The only tool that he said he ran was the refresher tool. Goodness knows why, when he had the phone in fastboot mode ready for flashing a ROM.
Click to expand...
Click to collapse
have you used motoflasher???
motorola.lover1998 said:
have you used motoflasher???
Click to expand...
Click to collapse
I haven't, no. Do you think it will work? Ah I think you need bootloader which this device does not have now. That's why I was trying to use blank flash.
garethjames said:
I haven't, no. Do you think it will work? Ah I think you need bootloader which this device does not have now. That's why I was trying to use blank flash.
Click to expand...
Click to collapse
you should use it its the same thing as blankflash but it also has 4.4.2,4.3 options
motorola.lover1998 said:
you should use it its the same thing as blankflash but it also has 4.4.2,4.3 options
Click to expand...
Click to collapse
I'll give it a try. Thanks. Will post back.
garethjames said:
I'll give it a try. Thanks. Will post back.
Click to expand...
Click to collapse
SYSTEM: Device Selected: Moto G v1, Android 4.4.4
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.006s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: FAILED (blank-flash:greet-device:error reading packet)
OUTPUT:
OUTPUT:
This is the problem I have. Absolutely no idea what it means! "your MBM-CI dont match with your bootloader version, use another MBM-CI version."
Thanks
garethjames said:
SYSTEM: Device Selected: Moto G v1, Android 4.4.4
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.006s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: FAILED (blank-flash:greet-device:error reading packet)
OUTPUT:
OUTPUT:
This is the problem I have. Absolutely no idea what it means! "your MBM-CI dont match with your bootloader version, use another MBM-CI version."
Thanks
Click to expand...
Click to collapse
hold the power button until the notification light blinks then post back
---------- Post added at 06:41 AM ---------- Previous post was at 06:37 AM ----------
use it with other versions if your using motoflasher
I think you are in the same boat as me my friend. If you have attempted, or your friend has attempted to flash lollipop, then your bootloader will now be 41.18, so there is currently no fix. As I understand it, and I may be wrong, the current blankflash will not work to run a singleimage.bin on the 41.18 bootoader and a newer blankflash version is required to get us out of this fix. It's a waiting game currently. I am following the progress of another thread waiting to see when this occurs.
Same with me
garethjames said:
SYSTEM: Device Selected: Moto G v1, Android 4.4.4
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.006s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: FAILED (blank-flash:greet-device:error reading packet)
OUTPUT:
OUTPUT:
This is the problem I have. Absolutely no idea what it means! "your MBM-CI dont match with your bootloader version, use another MBM-CI version."
Thanks
Click to expand...
Click to collapse
Same with me .Pl.help .
debakumarc2 said:
Same with me .Pl.help .
Click to expand...
Click to collapse
We cant help at the moment because there isnt a newer blankflash so we have to wait until leaked 5.0.1 firmwares come.. my device is also bricked i know what you feel bro :'(
Thanks.
I will wait. Pl.inform , if any hope ASAP. Thanks.
disconnect battery
I had similiar Problem inspite of correct bootloader 41.13. I could indeed blank flash only with disconnected battery.
1) Disconnect battery
2) Start blankflash.bat and quickly! insert usb cable - If you are not quick enough the batch process has finished before connection is established. Just retry!
3) After successful completed blankflash process, reconnect battery
4) Now the smartphone should be in fastboot mode.
5) If fastboot shows "low battery" disconnect and reconnect usb cable.
iacklink said:
I had similiar Problem inspite of correct bootloader 41.13. I could indeed blank flash only with disconnected battery.
1) Disconnect battery
2) Start blankflash.bat and quickly! insert usb cable - If you are not quick enough the batch process has finished before connection is established. Just retry!
3) After successful completed blankflash process, reconnect battery
4) Now the smartphone should be in fastboot mode.
5) If fastboot shows "low battery" disconnect and reconnect usb cable.
Click to expand...
Click to collapse
Why you had to use the bankflash tool? Because of upgrade from kitkat to lolipop?
disconnect battery
No, it was because of an interrupted flash process. My computer crashed during flashing stock rom. Thereafter the phone could not started anymore (even no LED when connected to power supply or PC).
Blank-flash
iacklink said:
No, it was because of an interrupted flash process. My computer crashed during flashing stock rom. Thereafter the phone could not started anymore (even no LED when connected to power supply or PC).
Click to expand...
Click to collapse
Came back to see if any new developments anywhere with regard to this problem. Read this, but unfortunately the battery can't be removed.
Same problem, any news please?
Same Problem
Hi all,
I was Flash my Moto G 1033 to Stock Firmware Android 4.4.4 Kitkat by Ushing ADB Recovery from Stock recovery.
it was Completed Installation. but when i Select Reboot System Now. Then After it will not Boot system as well as Not Boot Into boot-loader.
Please Brothers Help me.
i also Tried Blank-Flash tool but getting same problem as Above.
Please Give me Only idea to Install Only Boot-Loader Then After i will Install Full System only need Boot-loader.
Please help me all I m Very Sad About it. and i have only one phone, and That is Bricked, Now what can i do ?
I read This problem somewhere before thats why i never downgrade to kitkat, hope someone came with good news
Ps from what i read its safe to downgrade to 5.0 or 5.1
I got a Nexus 5 that won't boot. When you turn it on normally it hangs on the Google logo indefinitely. Recovery mode results in the red triangle logo. The only thing that 'works' is fastboot. But when I plug it into any of my PC's they all say: unknown usb device (device descriptor request failed) in the device manager.
I've tried installing various drivers, but it won't detect my phone in any way. As long as the descriptor isn't known by Windows it cannot install any driver. It will just resort back to the error message. Is there any way for Windows to recognize my device again?
I've tried various PC's and USB cables / ports. It's the device at fault not my other hardware for sure.
I plugged in my Galaxy S6, and it works just fine. Now the funny thing is when I plug back to Nexus 5 it is all the sudden recognized. I flashed the stock firmware back and it hang on the google logo again. Now going to fastboot the device is not recognized again. Recovery mode now also results in a Google logo that is stuck instead of the triangle.
After some retries I can connect in fastboot and the device is recognized as: "android bootloader interface"
Now how can I unbrick it? I am able to flash something to the device, i've tried the Restore_Nexus_5_KTU84P toolkit. It flashes but when it's done the phone reboots into the same brick mode.
When I manually try to flash an .img it says:
FAILED (command write failed (Unknown error))
The bootloader remains unlocked when the phone is rebooted? What OS is on the computer? Tried different USB ports and USB cables?
Tried with Ubuntu and I can flash stable now. But no matter what stock OS I flash (tried 6,5,4.4) after that flashing is done and the phone reboots it stuck on the google logo again. Any options beside throwing it in the bin?
And yeah, the bootloader stays unlocked.
Tried the unbrick method as shown here:
http://forum.xda-developers.com/goo...ck-nexus-5-stucked-qualcomm-hs-t3043301/page1
Flashes fine, also the memory tests pass. But it doesn't change the situation at all.
If when you try to lock or unlock the bootloader and after a reboot the locking or unlocking didn't take that usually means the emmc is bad.
Sent from my Nexus 9 using XDA-Developers mobile app
Are you flashing the userdata.img file too? The file should be flashed last. After flashong, immediately boot into recovery and perform a factory wipe, then reboot.
jd1639 said:
If when you try to lock or unlock the bootloader and after a reboot the locking or unlocking didn't take that usually means the emmc is bad.
Sent from my Nexus 9 using XDA-Developers mobile app
Click to expand...
Click to collapse
Lock / unlock sticks just fine.
audit13 said:
Are you flashing the userdata.img file too? The file should be flashed last. After flashong, immediately boot into recovery and perform a factory wipe, then reboot.
Click to expand...
Click to collapse
I did indeed also manually flash all img files including the userdata.
Code:
sending 'bootloader' (2506 KB)...
OKAY [ 0.317s]
writing 'bootloader'...
OKAY [ 0.462s]
finished. total time: 0.779s
rebooting into bootloader...
OKAY [ 0.061s]
finished. total time: 0.162s
sending 'radio' (42033 KB)...
OKAY [ 2.006s]
writing 'radio'...
OKAY [ 2.892s]
finished. total time: 4.898s
rebooting into bootloader...
OKAY [ 0.077s]
finished. total time: 0.278s
erasing 'system'...
OKAY [ 1.125s]
sending 'system' (692940 KB)...
OKAY [ 31.024s]
writing 'system'...
OKAY [ 47.110s]
finished. total time: 79.259s
sending 'boot' (8620 KB)...
OKAY [ 0.615s]
writing 'boot'...
OKAY [ 0.743s]
finished. total time: 1.358s
sending 'recovery' (9202 KB)...
OKAY [ 0.644s]
writing 'recovery'...
OKAY [ 0.775s]
finished. total time: 1.418s
erasing 'cache'...
OKAY [ 0.531s]
sending 'cache' (13348 KB)...
OKAY [ 0.840s]
writing 'cache'...
OKAY [ 1.075s]
finished. total time: 2.446s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.911s]
finished. total time: 6.911s
erasing 'userdata'...
OKAY [ 6.697s]
sending 'userdata' (137318 KB)...
OKAY [ 6.441s]
writing 'userdata'...
OKAY [ 9.135s]
finished. total time: 22.273s
rebooting...
finished. total time: 0.274s
After flashing I cannot enter recovery, cause every mode except for fastboot results in a stuck Google logo.
aapje1299 said:
Lock / unlock sticks just fine.
I did indeed also manually flash all img files including the userdata.
After flashing I cannot enter recovery, cause every mode except for fastboot results in a stuck Google logo.
Click to expand...
Click to collapse
Let's try something. I'm going to have you try to boot into twrp recovery and if you can do a factory reset from that. At the bootloader you'll use the commands fastboot boot twrp.img. Where twrp.img file be the full file name of the twrp recovery image. If you don't know where to get twrp Google teamwin nexus 5. Download that to your pc. If it boots to twrp go to wipe and wipe the device. Then try rebooting to system.
So you can't enter recovery, even from fastboot mode?
I couldn't
Don't ask me how, but today I flashed it again to show my collegue that it wouldn't work. And after flashing it it came alive all the sudden. I'm a happy man! Everything seems to work except for the camera, but that is probably something else!
--
Hmm, disconnected and reconnected the charger, phone froze. Reboot and now it's stuck on the google logo again. I think this phone is toast
--
Another update
I removed the cover, and all the sudden it booted fine again. The battery was loose inside and there was some duct inside to keep it in place. This phone has been repaired before because the screen was broken. I think something is short circuiting in there. I got it booted now and first I'm going to give it a full charge.
I declared it dead, was able to actually get TeamWin recovery flashed and it worked. Then after some time it was dead again and unable to boot. Also the camera was broken. Thanks for thinking along guys!
I enabled usb debugging in developer options and booted into the bootloader. The first time I ran "sudo fasboot boot" recovery I think it took me back to the boot loader, so I ran it a second time. Upon running the command a second time my phone instead loaded a screen telling me it is corrupted. Every time I reboot it takes me straight back to the bootloader. I am unable to get into the stock recovery. Is there a way to fix this? This is a brand new phone running android 8 and I was trying to make a backup of everything before I started using it.
Here is a copy of the commands I ran:
[email protected]:~$ sudo adb devices
[sudo] password for pc:
List of devices attached
90981ed7 device
[email protected]:~$ sudo adb reboot bootloader
[email protected]:~$ sudo fastboot boot /home/pc/Desktop/enchilada.zip
creating boot image...
creating boot image - 15024128 bytes
downloading 'boot.img'...
OKAY [ 0.376s]
booting...
OKAY [ 0.049s]
finished. total time: 0.425s
[email protected]:~$ sudo fastboot boot /home/pc/Desktop/enchilada.zip
creating boot image...
creating boot image - 15024128 bytes
downloading 'boot.img'...
OKAY [ 0.364s]
booting...
FAILED (status read failed (No such device))
finished. total time: 26.555s
[email protected]:~$ sudo fastboot reboot
rebooting...
finished. total time: 0.050s
[email protected]:~$
UPDATE:
I guess I panicked a bit. I have no clue why, but I was able to fix the issue by trying the same command, waiting several minutes, and then rebooting:
[email protected]:~$ sudo fastboot devices
[sudo] password for pc:
90981ed7 fastboot
[email protected]:~$ sudo fastboot boot /home/pc/Desktop/enchilada.zip
creating boot image...
creating boot image - 15024128 bytes
downloading 'boot.img'...
OKAY [ 0.376s]
booting...
OKAY [ 0.050s]
finished. total time: 0.426s
[email protected]:~$ sudo fastboot devices
90981ed7 fastboot
[email protected]:~$ sudo fastboot reboot
rebooting...
finished. total time: 0.050s
[email protected]:~$
Out of the box this thing is running OxygenOS 5.1.5, so I don't know if this is just a bug or something.
Maybe someone can give me advice on how to boot into TWRP without flashing it so that I can make a backup without this happening again?
UPDATE 2:
I'm an idiot who downloaded the installer instead of the image... is there a way to delete this post?
Hi,
I was trying to install TWRP but I keep getting the same error all the time.
Someone please help me.
Any suggestions?
My Tablet is not rooted yet also do I need to do a bootloader unlock or not?
If yes any useful links? Im so stuck I wanna install 7.1 to my Tablet.
Im still using JB android official by Asus.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash recovery "C:\twrp.img"
target didn't report max-download-size
sending 'recovery' (7126 KB)...
OKAY [ 1.285s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 4.382s
Hi, you could try flashing with the executables from my pack: https://forum.xda-developers.com/t/...0t-any-version-to-android-7-1-nougat.3554744/