Related
Hi all, try to be brief, but not simple:
First, I swear I've read many posts with cases similar to mine and I tried so many commands and tricks without success, so I decide to publish mine.
I have an HTC Inspire 4G, AT&T, rooted, S-off, and running Trickdroid. After a while I decided to return it to the original stock. However, when using the RUU utility, I got an error message and my phone it ruined.
Try to summarize as much as possible the conditions and the current situation:
Environments: Windows XP, Windows 7, Mac OS.
Power not work
Power + Vol Down do not work.
If I connect it to the outlet orante LED turn on, and charging it, but I must not press any buttons at all, after ten minutes, HTC logo appears with four exclamation marks on the screen. However, Windows can not find the device until 5 or 10 minutes later.
I have access to fastboot commands, but not ADB. I tried to format the partitions, reflash, do recovery, recover partitions, etc, endless commands that do not give me a result.
The information obtained from the achievement of limited screen or fastboot commands is as follows:
ACE PVT HIP S-OFF RL
HBOOT-0.85.0019
MICROP-0438
RADIO-26.06.04.06_M
eMMC-BOOT
Dec 27 2012, 14:47:30
RUU
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0019
(bootloader) version-baseband: 26.06.04.06_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 2.47.502.7
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9812000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4196mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-9854d819
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.171s
fastboot oem boot
< waiting for device >
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D08BECC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x27E0E
(bootloader) TAG:hero panel = 0x830012
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is CWS__001
(bootloader) setting->cid::CWS__001
(bootloader) serial number: HT19VT207144
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =506
(bootloader) active commandline: board_spade.disable_uart2=0 board_spade.
(bootloader) usb_h2w_sw=0 board_spade.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_spade.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=true androidboot.baseband=26.06.04.06_M androidboot.cid
(bootloader) =CWS__001 androidboot.batt_poweron=good_battery androidboot.
(bootloader) carrier=ATT androidboot.mid=PD9812000 enable_zcharge=1 andro
(bootloader) idboot.keycaps=qwerty androidboot.mode=normal androidboot.se
(bootloader) rialno=HT19VT207144 androidboot.bootloader=0.85.0019 zygote_
(bootloader) oneshot=off kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) Delay 98712(us) for dpram command before goto AMSS...
(bootloader) jump_to_kernel: machine_id(2844), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:0 msec
FAILED (status read failed (Too many links))
finished. total time: 232.216s
I used the commands, among many others:
Fastboot oem boot
fastboot flash recovery recovery.img (or zip)
fastboot oem resetRUUflag
fastboot reboot -bootloader (this just turn the phone off)
fastboot oem get_identifier_token (answer: (bootloader) [ERR] Command error !!!)
fastboot format userdata
formatting 'userdata' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.020sfastboot format cache
formatting 'cache' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.017s
In many cases the response message in the command line is: remote no allowed
SD card formatted.
I have no access to the SD card from the phone connected.
Please tell me if there is any other way to recover my phone, or if it is just an expensive piece of nothing.
Thanks for everything.
What happened when you tried to flash recovery from fastboot?
bananagranola said:
What happened when you tried to flash recovery from fastboot?
Click to expand...
Click to collapse
./fastboot flash zip PD98IMG.zip
sending 'zip' (3619 KB)...
OKAY [ 0.623s]
writing 'zip'...
No more response, stuck there...
In many other commands (I just don't remember after trying several) I got the message "remote not allowed"
Frogzter said:
./fastboot flash zip PD98IMG.zip
sending 'zip' (3619 KB)...
OKAY [ 0.623s]
writing 'zip'...
No more response, stuck there...
In many other commands (I just don't remember after trying several) I got the message "remote not allowed"
Click to expand...
Click to collapse
That's because you need a recovery.img, not a PD98IMG.zip:
Code:
fastboot flash recovery recovery.img
bananagranola said:
That's because you need a recovery.img, not a PD98IMG.zip:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I got this:
./fastboot flash recovery r.img
sending 'recovery' (4456 KB)...
OKAY [ 0.764s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.771s
Why?
Click to expand...
Click to collapse
Is your phone in fastboot mode?
bananagranola said:
Is your phone in fastboot mode?
Click to expand...
Click to collapse
Yes, it is, or at least I think so, because the command fastboot devices, found my device, besides, the command fastboot getvarr all, also works...
No more responses guys?
Where are you getting the recovery? How are you putting your phone in fastboot? Are you running the command from the folder where the recovery is? Are you sure you are S-Off?
bananagranola said:
Where are you getting the recovery? How are you putting your phone in fastboot? Are you running the command from the folder where the recovery is? Are you sure you are S-Off?
Click to expand...
Click to collapse
Power button not work
Power + Vol Down not work either.
If I connect it to the outlet orange LED turn on, and charges the battery, after ten minutes, HTC logo appears with four exclamation marks on the screen. However, Windows can not find the device until 5 or 10 minutes later, after this 10 minutes, if I connect via USB the device is responsive to fast boot devices command...
besides the screen shows:
ACE PVT HIP S-OFF RL
I have to command and the recovery file in the same folder
Er, what about the rest of my questions? How are you getting to fastboot with broken buttons? Is there an "adb reboot fastboot"?
Frogzter said:
Power button not work
Power + Vol Down not work either.
If I connect it to the outlet orange LED turn on, and charges the battery, after ten minutes, HTC logo appears with four exclamation marks on the screen. However, Windows can not find the device until 5 or 10 minutes later, after this 10 minutes, if I connect via USB the device is responsive to fast boot devices command...
besides the screen shows:
ACE PVT HIP S-OFF RL
I have to command and the recovery file in the same folder
Click to expand...
Click to collapse
What RUU did you use?? that sounds like a messed bootloader....
bananagranola said:
Er, what about the rest of my questions? How are you getting to fastboot with broken buttons? Is there an "adb reboot fastboot"?
Click to expand...
Click to collapse
I don't do anything.. I can't... if I plug the usb cable and touch any button nothing happen but if just plug it and let the phone alone, after 20 minutes do to fastboot mode...
"adb devices" don't detect the device.. just "fastboot devices" does
glevitan said:
What RUU did you use?? that sounds like a messed bootloader....
Click to expand...
Click to collapse
Well, now I feel ashamed, I can't remember with one I used... I just google the last version, because I wanted to get back to the original rom...
I formatted the computer with MAC OS, Linux, Win 7 and Win XP, looking for fix it, so I don't have much trace of with one I used.
HTC INSPIRE. att cws_001 bootloader 2.00.0030 s-on
Same thing on mine except my phone never comes on but fastboot is the only thing that recognizes my phone with limited commands. when I do a faceboot devices I get this ☺ ⌠σ fastboot no serial numbers as it use to have. Phone will not turn on at all. while nothing plugged in no light or anything even when trying to power on or get to hboot no sign of life at all. When I plug it in I get solid orange light. Pc sees it as android usb devices - my htc. but stock rom exe dont find phone. this happened to me when I was using xlmultitool 2.1. I was tyring for s 0ff after the option to [5] Flash HBOOT S-OFF Unprotected (via adb) this is when my troubles started. cant flash anything to it. when I try to flash the stock rom I get error file to big. In need of help.......I do have a gold card....
C:\Android>fastboot flash zip PD98IMG_Inspire_S-ON_FactoryRestore_GB_1.07.zip.
sending 'zip' (315734 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader:
(bootloader) version-baseband: 26.09.04.11_M2
(bootloader) version-cpld: ☺
(bootloader) version-microp: ☺
(bootloader) version-main: ♦
(bootloader) serialno: ☺ ⌠σ
(bootloader) imei: 3544550xxxxxxxx ......just sits here tells me nothing more
C:\Android>fastboot flash recover recovery.img
< waiting for device >
sending 'recover' (5532 KB)...
OKAY [ 0.624s]
writing 'recover'...
FAILED (remote: partition does not exist!)
finished. total time: 0.625s
C:\Android>fastboot flash system system.img
sending 'system' (571388 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.002s
C:\Android>fastboot oem boot
...
(bootloader) [DISPLAY_ERR] allocate heap for splash image fail!!!
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) [ERR] Boot/Recovery image does not exist!!!
OKAY [ 0.116s]
finished. total time: 0.117s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.002s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.008s
C:\Android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 1.004s]
finished. total time: 1.005s
sorry to double post but its been about a year is there a fix for this please someone help....
wacky_35016 said:
sorry to double post but its been about a year is there a fix for this please someone help....
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.002s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.008s
C:\Android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 1.004s]
finished. total time: 1.005s
Click to expand...
Click to collapse
Sounds like it's still s-on. Where did you get your Unlock_code.bin from? Have you tried using htc dev to get one or a new one?
Hello I did all the procedures to unlock the bootloader, I took notice of warning logo.bin, so q can not install CWM or TRW, the error message Mismatched partition size (recovery), and every time I put q in the recovery screen goes blank or turns black Reboot help me. my android is 4.4.2
First I just want to repeat what you said, to make sure I understand. You followed the instructions to unlock the bootloader. Then you saw the warning screen so you know the unlocked worked. You tried to install a recovery, got a "mismatched partition size" error, and you can't get into your recovery. Is this correct?
The "mismatched partition size" error is normal, and you will get this message even if the new recovery flashes properly. Are you able to get to the bootloader without any problems? From where did you download the recovery that you tried to flash?
grrrrrrrrrrrrrrrrrrrr
FaultyFirmware said:
First I just want to repeat what you said, to make sure I understand. You followed the instructions to unlock the bootloader. Then you saw the warning screen so you know the unlocked worked. You tried to install a recovery, got a "mismatched partition size" error, and you can't get into your recovery. Is this correct?
The "mismatched partition size" error is normal, and you will get this message even if the new recovery flashes properly. Are you able to get to the bootloader without any problems? From where did you download the recovery that you tried to flash?
Click to expand...
Click to collapse
so I did it all you said, the only thing different foia message on boot that the phone was unlocked with the bootloader, you know that warning?
Dai to remove this message from the unlocked bootloader, flash the logo.bin file to go back to the original boot animation from motorola, I think that the bootloader is still unlocked ...
I grab the file from CWM downloaded here XDA same, this message of "Mismatched partition size (recovery)".
Ta many say that this message is normal, it happens that I put in the recovery squeeze the power button and the phone gets the black screen, and not everything goes back even after 2 minutes.
I believe that it shuts down, a version ai step before CWM, of the mismatched message ... however I enter recovery, and he does not turn off, just restarts ...
I mean I can not even get into recovery, and therefore can not make root .
Got the point? if you want to put the names of the files I tried to flash.
Here is a program that will help you install the recovery. USB debugging should be turned on on your phone, and you should be booted into the system. Also be sure that the proper USB drivers are installed on your computer.
http://forum.xda-developers.com/showthread.php?t=2635706
Here is the latest version of TWRP.
http://forum.xda-developers.com/showthread.php?t=2561757
Here is the latest version of PhilZ. It is a modified version of CWM.
http://forum.xda-developers.com/showthread.php?t=2639583
Choose one of the recoveries listed above and install with the tool. If you flash the recovery in this way, I think it will work for you. As always, read everything carefully. Know the type of Moto G you have and be sure to choose the right files.
this is complicated again tried to do what was already done with the files that I step, and the Moto tool aio tool and also via adb, and he clicking recovery restarts, do not know what to do more lost. I made a video and played on youtube showing the process, and what happens there happened to all types of file recovery and point out that the latter (philz_touch_6.13.2-xt1033.zip).
In the video also has all specifications. Please help me
So after you select and activate recovery and you see the Motorola logo, it boots into the normal system? You have the 8GB dual-sim Brazil/India/Malaysia version? This is not a Google Play Edition? Does the box it came in say "XT1033"?
The PhilZ you chose is not the latest version. They use a unified build now, which should work on all types of Moto G. It is here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon//philz_touch_6.26.6-falcon.zip That one is worth a try. Your TWRP version is correct, though, so I don't know why that didn't work.
Your USB connection seems to be working fine, and you have tried ADB and the AIO tool. Have you tried using fastboot from the bootloader? The command would be "fastboot flash recovery recovery.img" and you would do this while you are in the bootloader. You should still expect to see the partition size mismatch error.
If that fails we can try flashing everything back to stock and start fresh. Please use "fastboot getvar all" and post the results (you can remove IMEI, Serial Number, and other private information). This will tell us which stock to use.
FaultyFirmware said:
So after you select and activate recovery and you see the Motorola logo, it boots into the normal system? You have the 8GB dual-sim Brazil/India/Malaysia version? This is not a Google Play Edition? Does the box it came in say "XT1033"?
The PhilZ you chose is not the latest version. They use a unified build now, which should work on all types of Moto G. It is here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon//philz_touch_6.26.6-falcon.zip That one is worth a try. Your TWRP version is correct, though, so I don't know why that didn't work.
Your USB connection seems to be working fine, and you have tried ADB and the AIO tool. Have you tried using fastboot from the bootloader? The command would be "fastboot flash recovery recovery.img" and you would do this while you are in the bootloader. You should still expect to see the partition size mismatch error.
If that fails we can try flashing everything back to stock and start fresh. Please use "fastboot getvar all" and post the results (you can remove IMEI, Serial Number, and other private information). This will tell us which stock to use.
Click to expand...
Click to collapse
i have same problem. but i cant boot into ROM or custom recovery. i try flash latest phillz recovery but still not working. there is my log
H:\MotoToolAioV3\mfastboot-v2>fastboot devices
TA929046PR fastboot
H:\MotoToolAioV3\mfastboot-v2>fastboot -w
erasing 'userdata'...
OKAY [ 3.244s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.022s]
erasing 'cache'...
OKAY [ 0.413s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.024s]
finished. total time: 3.727s
H:\MotoToolAioV3\mfastboot-v2>fastboot flash recovery cwm.img
target reported max download size of 536870912 bytes
sending 'recovery' (8556 KB)...
OKAY [ 0.356s]
writing 'recovery'...
OKAY [ 0.314s]
finished. total time: 0.676s
H:\MotoToolAioV3\mfastboot-v2>fastboot reboot recovery
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
H:\MotoToolAioV3\mfastboot-v2>fastboot reboot recovery
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
H:\MotoToolAioV3\mfastboot-v2>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA929046PR
(bootloader) cid: 0x0007
(bootloader) uid: E98452020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359276056402244
(bootloader) meid:
(bootloader) date: 01-24-2014
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 8 8:20: 6 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_o2de/falcon_umts:4
(bootloader) ro.build.fingerprint[1]: .4.2/KLB20.9-1.10-1.9.1/1:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.175.44.1.falcon_umts
(bootloader) ro.build.version.full[1]: .O2.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-gc6fc9e1-00001-g6ff8
(bootloader) kernel.version[1]: 71f ([email protected]) (gcc version 4.
(bootloader) kernel.version[2]: 7 (GCC) ) #1 SMP PREEMPT Mon Jan 13 04:4
(bootloader) kernel.version[3]: 6:14 CST 2014
(bootloader) sdi.git: git=MBM-NG-V41.05-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.05-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.05-0-g4018bbe
(bootloader) tz.git: git=MBM-NG-V41.05-0-g11658be
(bootloader) aboot.git: git=MBM-NG-V41.05-0-gf4ab363
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.060s
H:\MotoToolAioV3\mfastboot-v2>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA929046PR
(bootloader) cid: 0x0007
(bootloader) uid: E98452020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359276056402244
(bootloader) meid:
(bootloader) date: 01-24-2014
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 8 8:22:49 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_o2de/falcon_umts:4
(bootloader) ro.build.fingerprint[1]: .4.2/KLB20.9-1.10-1.9.1/1:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.175.44.1.falcon_umts
(bootloader) ro.build.version.full[1]: .O2.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-gc6fc9e1-00001-g6ff8
(bootloader) kernel.version[1]: 71f ([email protected]) (gcc version 4.
(bootloader) kernel.version[2]: 7 (GCC) ) #1 SMP PREEMPT Mon Jan 13 04:4
(bootloader) kernel.version[3]: 6:14 CST 2014
(bootloader) sdi.git: git=MBM-NG-V41.05-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.05-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.05-0-g4018bbe
(bootloader) tz.git: git=MBM-NG-V41.05-0-g11658be
(bootloader) aboot.git: git=MBM-NG-V41.05-0-gf4ab363
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.061s
H:\MotoToolAioV3\mfastboot-v2>
Click to expand...
Click to collapse
FaultyFirmware said:
So after you select and activate recovery and you see the Motorola logo, it boots into the normal system? You have the 8GB dual-sim Brazil/India/Malaysia version? This is not a Google Play Edition? Does the box it came in say "XT1033"?
The PhilZ you chose is not the latest version. They use a unified build now, which should work on all types of Moto G. It is here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon//philz_touch_6.26.6-falcon.zip That one is worth a try. Your TWRP version is correct, though, so I don't know why that didn't work.
Your USB connection seems to be working fine, and you have tried ADB and the AIO tool. Have you tried using fastboot from the bootloader? The command would be "fastboot flash recovery recovery.img" and you would do this while you are in the bootloader. You should still expect to see the partition size mismatch error.
If that fails we can try flashing everything back to stock and start fresh. Please use "fastboot getvar all" and post the results (you can remove IMEI, Serial Number, and other private information). This will tell us which stock to use.
Click to expand...
Click to collapse
ok this is the print:
D:\Downloads\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tool
oot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4108
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) cid: 0x000C
(bootloader) uid: F66F3B020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 2014-01-24
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 18 15:49:10 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_amxbr_ds/falcon_um
(bootloader) ro.build.fingerprint[1]: tsds:4.4.2/KXB20.25-1.31/15:user/r
(bootloader) ro.build.fingerprint[2]: elease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.171.44.31.falcon_umt
(bootloader) ro.build.version.full[1]: sds.AmericaMovil.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-g13e395f ([email protected]
(bootloader) kernel.version[1]: lclbld52) (gcc version 4.7 (GCC) ) #1 SM
(bootloader) kernel.version[2]: P PREEMPT Thu Jan 23 21:22:07 CST 2014
(bootloader) sdi.git: git=MBM-NG-V41.08-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.08-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.08-0-g8ef2ac8
(bootloader) tz.git: git=MBM-NG-V41.08-0-gcebfadf
(bootloader) aboot.git: git=MBM-NG-V41.08-0-g04a4bc3
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.057s
Yeah, I have the same issue :-/ phone just reboots instead of going into recovery :-/ I tried cwm and philz...
Sent from my XT1032 using xda app-developers app
---------- Post added at 06:36 PM ---------- Previous post was at 06:19 PM ----------
Guys, I have just discovered how to enter recovery... In fastboot mode press vol-down (this selects recovery option) and then vol-up. It goes into recovery. Tested with latest philz. I tried million of times but I expected power button to choose options... Is it normal behavior?
Sent from my XT1032 using xda app-developers app
Bro, try this method.
1.Download the Android SDK
2.Download the recovery you want (I used CWM but TWRP works aswell)
3.Go to Your SDK directory then go to \adt-bundle-windows-x86_64-20140321\sdk\platform-tools\
4.Inside you will find adb, fast boot stuff like that, now put your recovery inside there and rename it to recovery.img
5.Reboot into fasboot mode (power off + Vol- )
6.Go to your platform-tools folder, now hold Shift + press Right click, and select open command window here.
7. Type in:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
8.When that is complete reboot into recovery via the fastboot menu (Volume - then Volume + to select).
I hope this works, i had this problem before so now i just do this and i dont use the MotoTool AIO.
Wow, so much activity. Let's get this sorted.
sinkadorable: The command for rebooting into recovery is "fastboot reboot-recovery". Without the dash, nothing happens. That's what your log describes. You can use "adb reboot recovery" to enter recovery if you are fully booted into the system.
Routerm4N: For privacy you may want to edit your post to remove the lines labeled "imei" and "serialno". These can be used to uniquely identify your phone. So you tried flashing the file I liked in my last post and were unsuccessful? I don't have a copy of you ROM you are currently using, but it looks like this stock ROM is compatable with your phone. http://sbf.droid-developers.org/download.php?device=14&file=130 Are you on Android 4.3 or 4.4? The ROM I linked will take you back to 4.3, but you can always use OTA updates to get back again later. Here are the instructions for flashing stock firmware: http://forum.xda-developers.com/showthread.php?t=2542219 It is a bit of an involved process. Only do this if you have exhausted your other options.
fabus: Yes, it is unintuitive that the "up" button activates the selected option. However, it says on the bootloader screen that this is how it works. They probably wanted to reserve the power button for powering the device on and off.
FaultyFirmware said:
Wow, so much activity. Let's get this sorted.
sinkadorable: The command for rebooting into recovery is "fastboot reboot-recovery". Without the dash, nothing happens. That's what your log describes. You can use "adb reboot recovery" to enter recovery if you are fully booted into the system.
Routerm4N: For privacy you may want to edit your post to remove the lines labeled "imei" and "serialno". These can be used to uniquely identify your phone. So you tried flashing the file I liked in my last post and were unsuccessful? I don't have a copy of you ROM you are currently using, but it looks like this stock ROM is compatable with your phone. http://sbf.droid-developers.org/download.php?device=14&file=130 Are you on Android 4.3 or 4.4? The ROM I linked will take you back to 4.3, but you can always use OTA updates to get back again later. Here are the instructions for flashing stock firmware: http://forum.xda-developers.com/showthread.php?t=2542219 It is a bit of an involved process. Only do this if you have exhausted your other options.
fabus: Yes, it is unintuitive that the "up" button activates the selected option. However, it says on the bootloader screen that this is how it works. They probably wanted to reserve the power button for powering the device on and off.
Click to expand...
Click to collapse
Thanks I use 4.4.2
FaultyFirmware said:
Wow, so much activity. Let's get this sorted.
sinkadorable: The command for rebooting into recovery is "fastboot reboot-recovery". Without the dash, nothing happens. That's what your log describes. You can use "adb reboot recovery" to enter recovery if you are fully booted into the system.
Routerm4N: For privacy you may want to edit your post to remove the lines labeled "imei" and "serialno". These can be used to uniquely identify your phone. So you tried flashing the file I liked in my last post and were unsuccessful? I don't have a copy of you ROM you are currently using, but it looks like this stock ROM is compatable with your phone. http://sbf.droid-developers.org/download.php?device=14&file=130 Are you on Android 4.3 or 4.4? The ROM I linked will take you back to 4.3, but you can always use OTA updates to get back again later. Here are the instructions for flashing stock firmware: http://forum.xda-developers.com/showthread.php?t=2542219 It is a bit of an involved process. Only do this if you have exhausted your other options.
fabus: Yes, it is unintuitive that the "up" button activates the selected option. However, it says on the bootloader screen that this is how it works. They probably wanted to reserve the power button for powering the device on and off.
Click to expand...
Click to collapse
Still cannot boot into recovery with every method was i found. When i choose boot into recovery it just looping in boot logo
Even with adb?
sinkadorable said:
Still cannot boot into recovery with every method was i found. When i choose boot into recovery it just looping in boot logo
Click to expand...
Click to collapse
Are you getting same error when you fully boot into system, connect it to pc via a data cable
and run
Code:
adb reboot recovery
??
deej_roamer said:
Are you getting same error when you fully boot into system, connect it to pc via a data cable
and run
Code:
adb reboot recovery
??
Click to expand...
Click to collapse
I think in fastboot menu cannot run adb command
sinkadorable said:
I think in fastboot menu cannot run adb command
Click to expand...
Click to collapse
This is true. I was saying you can use adb if you happen to be fully booted into the system.
Edit: Obviously you weren't referring to my post. Now I can't find the delete button.... Oh well.
Sinkadorable: have you tried flashing everything back to stock from the bootloader?
Routerm4N: How's your progress?
FaultyFirmware said:
This is true. I was saying you can use adb if you happen to be fully booted into the system.
Edit: Obviously you weren't referring to my post. Now I can't find the delete button.... Oh well.
Sinkadorable: have you tried flashing everything back to stock from the bootloader?
Routerm4N: How's your progress?
Click to expand...
Click to collapse
Yes. Every method was i found
While in bootloader menu, VOLUME DOWN(-) is for navigation, and VOLUME UP(+) is to select or choose the option.
POWER BUTTON DOES NOTHING!
DO NOT USE THE POWER BUTTON FOR ANYTHING WHILE IN BOOTLOADER MENU!
wow nice thanks
Hey i am having the same problem
anyone got any solution.
please update it.
My moto g get stucked on a blank screen after the motorola logo animation.
I tried going into the recovery and wiping data and cache. Nothing happened.
I tried unlocking the bootloader --> No problem, it's unlocked now.
I tried reflashing the stock ROM via fastboot. Apparently all goes OKAY, all commands pass without problems, but when I reboot, still a blank screen.
I tried flashing a new ROM (5.0.2 Lollipop). Same problem, apparently it flashes everything ok but when reboots... nothing.
I tried to update only the recovery to ither Team Wins or Clockwork, they flash without problems but when I go to the recovery I get the stock one (I didnt reboot the phone went straight to recovery after flashing, and tried rebooting the phone as well).
I also tried to update only the bootloader (right now I'm at 41.13) tried to update it to 41.18, same problem... Apparently it flashes but when I reboot I still get the 41.13
Finally, I tried to hard-brick my phone using the Bootloader Bricker Tool posted here: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798 and nothing happened.
So basically, it seems that everything I do via fastboot (or mfastboot - I tried both) it goes through without problems, but then it either reverts back to stock when the phone reboots or actually it doesnt write anything.
Any help, will be greatly appreaciated.
This is my getvar:all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: T09290UV3C
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: ADC65E030F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jun 26 18: 9:42 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_amxar/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/37:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.AmericaMovil.en.AR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld28) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 04:31:45 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.13-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.057s
Sounds like possible Bootloader corruption. I would try again with the unbrick tool. Best ask in the thread. Avoid trying to update Bootloader (motoboot.img) - Lollipop is not supported.
Here is the exact 4.4.2 Firmware Image:
http://www.filefactory.com/file/793...9_7_release-keys-cid12-AmericaMovil_AR.tar.gz
Thanks for the reply.
Ok, I'll head over to the unbrick thread again. The thing is my phone doesn't seem to be hard-bricked, because it boots to bootlader and it's not recognized by the PC as "qhsusb_bulk" in Device Manager.
That's why I tried to "brick" it using the tool on that thread, but it didnt get bricked at all :\
The unbrick tool should allow you to restore the Bootloader - if it is indeed corrupted.
lost101 said:
The unbrick tool should allow you to restore the Bootloader - if it is indeed corrupted.
Click to expand...
Click to collapse
I tried it several times now... The problem is that my phone is not being detected by Windows as "qhsusb_bulk" in the Device Manager. So I can't do what the instructions tell me to do.
So I used the Bootloader Bricer Tool
oversleeper said:
Bootloader Bricker Tool: If the previous tool had no effect or you think your bootloader is seriously damaged, this script will make your phone recognized as "qhsusb_bulk" so you can perform a blank flash
Click to expand...
Click to collapse
And this is what I get:
Code:
WARNING: READ CAREFULLY BEFORE YOU PROCEED!
THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.
Do you want to continue [Y/N]?Y
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.033s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.067s
rebooting...
finished. total time: 0.002s
Your device is now hard bricked!
When it automatically reboots, it's like nothing happened: motorola logo, full animation, then blank screen. I can still enter the bootloader, run fastboot commands, etc etc...
epexy said:
I tried it several times now... The problem is that my phone is not being detected by Windows as "qhsusb_bulk" in the Device Manager. So I can't do what the instructions tell me to do.
So I used the Bootloader Bricer Tool
And this is what I get:
Code:
WARNING: READ CAREFULLY BEFORE YOU PROCEED!
THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.
Do you want to continue [Y/N]?Y
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.033s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.067s
rebooting...
finished. total time: 0.002s
Your device is now hard bricked!
When it automatically reboots, it's like nothing happened: motorola logo, full animation, then blank screen. I can still enter the bootloader, run fastboot commands, etc etc...
Click to expand...
Click to collapse
I have two devices with the same problem as yours, one = motorola logo -> full animation -> black screen. And another boots up normally, but have a forgotten password, but if I try to enter recovery mode then "Boot Up Failed" message appear, and after I flash the device (and use erase userdata command), the device still have the password and all data apparently (the device boot up fast too).
The only thing that seems to work with fastboot is unlocking bootloader, and relock fails (even showing sucessful)
No one have this problems and have solutions ?????
I have the exact same problem. Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.
Special thanks to @diplomatic for finding an exploit that has the potential to target many MTK devices, which he originally wrote to target Amazon devices: Experimental Software Root for HD 8 & HD 10
With some tweaking, he got it to work on my Acer B3-A40 with an MT8167 chip and kernel 4.4.22. The result is getting a root shell on the device:
Code:
acer_asgard:/data/local/tmp $ ./mtk-su
New UID/GID: 0/0
acer_asgard:/data/local/tmp # id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:shell:s0
acer_asgard:/data/local/tmp #
The issue now is getting permanent root. From my understanding, because of dm-verity, I can't just mount /system as read/write to install su permanently. So I'm looking for help from you guys on how to proceed from here to get permanent root. And I think this is where it gets into specifics for each device.
On my particular device, nothing shows on screen in fastboot mode. If I run 'fastboot oem unlock', I can press any button on the device, but as soon as I press Vol+ it goes back to the prompt. But when I run 'fastboot getvar unlocked', it still shows "no". So I'm not sure how to proceed from here.
At the very least, I'm sure you guys can have some fun with this for other devices, but I am hoping to get some help with mine.
(As you can tell, I'm not super familiar with Android development. I am primarily a .NET developer, although I've dabbled a little in C/C++.)
Tagging the main contributors to the big Acer root thread in case you can help, or just want to have fun with this: @FireDiamond @vache @Shreps
A year later - any luck?
balexandrov said:
A year later - any luck?
Click to expand...
Click to collapse
Yeah, I did get it unlocked and rooted, through a roundabout way (a tool that diplomatic wrote). But I found out later that I can also try "fastboot flashing unlock". Apparently some tablets use that, including some Acer ones. It won't really make a difference on mine anymore since I'm already unlocked. And I don't want to re-lock and try it since I already modified the system partition and it'll probably brick my tablet.
So try that first. If "fastboot flashing unlock" doesn't work, then I can share the convoluted way.
balexandrov said:
A year later - any luck?
Click to expand...
Click to collapse
Hi, I'm interrested in rooting my B3-A40 permanently too.
Can someone confirm that it works with Amazing Temp Root for MediaTek ARMv8 [2019-12-28] and the "fastboot flashing unlock" command?
What else do I have to do to be rooted permanently?
Which guide I have to follow? I am not sure !
Do I have to install Magisk too?
Can you show me the correct steps please?
Thank you
BenchBox said:
Hi, I'm interrested in rooting my B3-A40 permanently too.
Can someone confirm that it works with Amazing Temp Root for MediaTek ARMv8 [2019-12-28] and the "fastboot flashing unlock" command?
What else do I have to do to be rooted permanently?
Which guide I have to follow? I am not sure !
Do I have to install Magisk too?
Can you show me the correct steps please?
Thank you
Click to expand...
Click to collapse
That temp root does work on this tablet, but to get permanent root, you need to unlock the bootloader. So try "fastboot flashing unlock" and see if that works for you.
cybersaga said:
That temp root does work on this tablet, but to get permanent root, you need to unlock the bootloader. So try "fastboot flashing unlock" and see if that works for you.
Click to expand...
Click to collapse
Should it be possible to install TWRP-Recovery and Custom-Roms after getting permanent root with Magisk and unlocking the Bootloader?
I ask this because of the VM-Verity .
BenchBox said:
Should it be possible to install TWRP-Recovery and Custom-Roms after getting permanent root with Magisk and unlocking the Bootloader?
I ask this because of the VM-Verity .
Click to expand...
Click to collapse
I'm not aware of anyone who has ported TWRP to this tablet, or made a custom ROM. I just have permanent root via Magisk.
Once you unlock the bootloader, DM Verity isn't an issue anymore. That's your first step. Have you tried to see if "fastboot flashing unlock" works yet?
cybersaga said:
I'm not aware of anyone who has ported TWRP to this tablet, or made a custom ROM. I just have permanent root via Magisk.
Once you unlock the bootloader, DM Verity isn't an issue anymore. That's your first step. Have you tried to see if "fastboot flashing unlock" works yet?
Click to expand...
Click to collapse
O.K. then I would try it.
Can you please confirm the order of steps that nothing goes wrong?
1.) Amazing Temp Root for MediaTek ARMv8 [2019-12-28]
2.) Then I get the Bootloader unlocked with your command "fastboot flashing unlock" (if it is possible for me)
3.) After unlocking Bootloader I can install Magisk with Get full root with Magisk on a locked bootloader! ?
Is this the right way of getting it running permanently?
Sorry for so much questions but I am a little bit unsure.
Thank you.
cybersaga said:
Yeah, I did get it unlocked and rooted, through a roundabout way (a tool that diplomatic wrote). But I found out later that I can also try "fastboot flashing unlock". Apparently some tablets use that, including some Acer ones. It won't really make a difference on mine anymore since I'm already unlocked. And I don't want to re-lock and try it since I already modified the system partition and it'll probably brick my tablet.
So try that first. If "fastboot flashing unlock" doesn't work, then I can share the convoluted way.
Click to expand...
Click to collapse
I have give it a try but "fastboot flashing unlock" do not work for me, pls share the convoluted way, thx.
Code:
PS C:\WINDOWS\system32> fastboot flashing unlock
...
OKAY [183.578s]
finished. total time: 183.578s
PS C:\WINDOWS\system32> fastboot getvar unlocked
unlocked: no
finished. total time: 0.000s
BenchBox said:
I have give it a try but "fastboot flashing unlock" do not work for me, pls share the convoluted way, thx.
Code:
PS C:\WINDOWS\system32> fastboot flashing unlock
...
OKAY [183.578s]
finished. total time: 183.578s
PS C:\WINDOWS\system32> fastboot getvar unlocked
unlocked: no
finished. total time: 0.000s
Click to expand...
Click to collapse
Hi Normally Unlocking the bootloader is easy on most MediaTek's although I have not tried it with any Acer devices and especially this 4.4 kernel version.
The standard way is as follows so do each step in order.
1. Go to /settings/about device/ and tap build number seven times till you get the "You are Now a Developer" toast then press the back button
2. Got to /settings/developer option (this is a new menu item BTW)/You should see "OEM Unlocking" if allowed slide it to on along with usb debugging.
3. You can now try adb reboot bootloader or adb reboot fastboot if niether of those bring you to fastboot reboot to stock recovery and choose fastboot mode from the stock recovery option.
4. OEM's use their own cmds so this could be tricky part. In fastboot try the standard "fastboot oem unlock" or "fastboot flashing unlock" You will need to reboot after each before the Var becomes updated. To be honest it looks like the "fastboot flashing unlock" worked so double check the var after reboot to fastboot.
Your userdata should be wiped on reboot so if it is then the unlocking worked regardless of the Var some of the OEM bootloader unlocking implementation are a little flaky and some are just simply broke so dont always expect a nice read out. :laugh:
On alot of MTK devices simply signing the custom boot.img with AVB is enough to fool the bootloader so no need to unlock the bootloader at all. :fingers-crossed:
PS: Use the [ fastboot getvar all ] cmd we do with seeing if the "secure" var is set too.
.
bigrammy said:
Hi Normally Unlocking the bootloader is easy on most MediaTek's although I have not tried it with any Acer devices and especially this 4.4 kernel version.
The standard way is as follows so do each step in order.
1. Go to /settings/about device/ and tap build number seven times till you get the "You are Now a Developer" toast then press the back button
2. Got to /settings/developer option (this is a new menu item BTW)/You should see "OEM Unlocking" if allowed slide it to on along with usb debugging.
3. You can now try adb reboot bootloader or adb reboot fastboot if niether of those bring you to fastboot reboot to stock recovery and choose fastboot mode from the stock recovery option.
4. OEM's use their own cmds so this could be tricky part. In fastboot try the standard "fastboot oem unlock" or "fastboot flashing unlock" You will need to reboot after each before the Var becomes updated. To be honest it looks like the "fastboot flashing unlock" worked so double check the var after reboot to fastboot.
Your userdata should be wiped on reboot so if it is then the unlocking worked regardless of the Var some of the OEM bootloader unlocking implementation are a little flaky and some are just simply broke so dont always expect a nice read out. :laugh:
On alot of MTK devices simply signing the custom boot.img with AVB is enough to fool the bootloader so no need to unlock the bootloader at all. :fingers-crossed:
PS: Use the [ fastboot getvar all ] cmd we do with seeing if the "secure" var is set too.
.
Click to expand...
Click to collapse
Thanks for your help,
if i give the "fastboot flashing unlock" command it looks like this in the CMD:
Code:
C:\Minimal ADB and Fastboot>fastboot flashing unlock
...
But the problem is that i can't see something on the screen of the device because in bootloader-mode the screen is black!
If I push the "Power" or the "Vol -" Buttons on the device nothing is changing.
But if i press "Vol+" it comes back in the CMD:
Code:
C:\Minimal ADB and Fastboot>fastboot flashing unlock
...
OKAY [1034.731s]
finished. total time: 1034.733s
C:\Minimal ADB and Fastboot>
then i give the "fastboot reboot" command and it's rebooting:
Code:
C:\Minimal ADB and Fastboot>fastboot flashing unlock
...
OKAY [1034.731s]
finished. total time: 1034.733s
C:\Minimal ADB and Fastboot>
Now we have a look at the "fastboot getvar all" command:
Code:
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:userdata: 292380000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 20000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: ed000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2100000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk2: 60000
(bootloader) partition-type:lk2: raw data
(bootloader) partition-size:lk: 60000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:persist: 3000000
(bootloader) partition-type:persist: ext4
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: NEOSTRA8167_TB_N
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.153s
C:\Minimal ADB and Fastboot>
"secure: yes"
Thank you for helping me.
What else can i do know?
BenchBox said:
Thanks for your help,
But the problem is that i can't see something on the screen of the device because in bootloader-mode the screen is black!
If I push the "Power" or the "Vol -" Buttons on the device nothing is changing.
But if i press "Vol+" it comes back in the CMD:
Click to expand...
Click to collapse
A blank screen is not uncommon as long as you get the reply on you cmd prompt then it's OK as I doubt you will need to confirm anything on the device :fingers-crossed:
BTW what version of Fastboot are you using in Minimal ADB and Fastboot?
Running
Code:
fastboot --version
in the cmd prompt should tell you the version and the location from which it's been run. (Post the output of that cmd) A up to date fastbboot.exe is recommended along with up to date drivers. :good:
BenchBox said:
Code:
C:\Minimal ADB and Fastboot>fastboot flashing unlock
...
OKAY [1034.731s]
finished. total time: 1034.733s
C:\Minimal ADB and Fastboot>
then i give the "fastboot reboot" command and it's rebooting:
Now we have a look at the "fastboot getvar all" command:
Code:
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:userdata: 292380000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 20000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: ed000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2100000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk2: 60000
(bootloader) partition-type:lk2: raw data
(bootloader) partition-size:lk: 60000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:persist: 3000000
(bootloader) partition-type:persist: ext4
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1[/HIDE]
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: NEOSTRA8167_TB_N
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.153s
C:\Minimal ADB and Fastboot>
"secure: yes"
Thank you for helping me.
What else can i do know?
Click to expand...
Click to collapse
Can you use SPFlashTool on the device?? I know a few OEM's disable it but I think I have seen some Acer devices using it before.
The cmd fastboot flashing unlock seems to do something but I suspect it's not a complete cmd
Most bootloaders use
Code:
fastboot flash unlock theunlockcodegivenbytheOEM
followed by
Code:
fastboot oem unlock
then
Code:
fastboot reboot
or just
Code:
fastboot oem unlock
on it's own.
Sometimes none of this is required.
Can you easily recover the device using SPFlashTool (Preferred) or Micro SD and a official update.zip??
If so upload your boot.img LK and preloader (pull them using mtk-su and the dd-backup script in that thread) and I will make a small change to the boot.img and sign it with AVB I will also have a look at the LK and preloader to see if I can see any fastboot cmds you can use mtk-su to flash the modded boot.img if fastboot does not allow flashing.
My simple dd-backup helper script is here see the Readme for instructions. https://github.com/bigrammy/dd-backup-helper-script
Edit FYI See post #12 > for a discussion on this issue in general https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213/page2
Fatsboot Version:
Code:
C:\Minimal ADB and Fastboot>fastboot --version
fastboot version 0.0.1-4500957
Installed as C:\Minimal ADB and Fastboot\fastboot.exe
C:\Minimal ADB and Fastboot>
I don't know if it is possible to flash via SPFlashTool .
I get an Error loading the scatter.txt file.
Micro SD and a official update.zip should be possible i think. But I don't have testet yet. Should I test it before?
dd-backup script shows me this dd-commands:
Code:
acer_asgardfhd:/data/local/tmp # ./dd-backup.sh
##################################################
##################################################
## ##
## dd-backup script ##
## ##
## Generator ##
## ##
## Quick Easy and Universal ##
## ##
## by: xda members @mrmazak @bigrammy ##
## ##
##################################################
##################################################
mkdir: '/sdcard/dd-backup': File exists
1. The dd-backup folder is created!
2. Searching for by-name!
3. Folder located!
4. Begin editing script!
5. Done basic editing
6. Adding dd if cmd's
7. Adding dd of cmd's
8. Getting all the partition names!
9. Joining files!
dd if=/dev/block/platform/soc/11120000.mmc/by-name of=/sdcard/dd-backup/.boot.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/.boot of=/sdcard/dd-backup/flashinfo.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/flashinfo of=/sdcard/dd-backup/userdata.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/userdata of=/sdcard/dd-backup/cache.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/cache of=/sdcard/dd-backup/system.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/system of=/sdcard/dd-backup/metadata.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/metadata of=/sdcard/dd-backup/dkb.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/dkb of=/sdcard/dd-backup/kb.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/kb of=/sdcard/dd-backup/tee2.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/tee2 of=/sdcard/dd-backup/tee1.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/tee1 of=/sdcard/dd-backup/frp.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/frp of=/sdcard/dd-backup/expdb.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/expdb of=/sdcard/dd-backup/logo.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/logo of=/sdcard/dd-backup/para.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/para of=/sdcard/dd-backup/recovery.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/recovery of=/sdcard/dd-backup/lk2.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/lk2 of=/sdcard/dd-backup/lk.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/lk of=/sdcard/dd-backup/seccfg.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/seccfg of=/sdcard/dd-backup/persist.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/persist of=/sdcard/dd-backup/protect2.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/protect2 of=/sdcard/dd-backup/protect1.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/protect1 of=/sdcard/dd-backup/nvram.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/nvram of=/sdcard/dd-backup/proinfo.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/proinfo of=/sdcard/dd-backup
10. Cleaning up!
11. dd-backup.txt created!
12.!!!! Credits !!!!!
@mrmazak for amazing code skills
@diplomatic for mtk-su!
@bigrammy for my time & effort
@HemanthJabalpuri for helping
@Rortiz2 for all the testing
Hit the above's THANKS Buttons
I think the commands are not right! They are shifted one row!
Where can I find the preloader partition?
Which backups do we need?
Thank you very much.
Hate to necro a year old post but I am interested in permanently rooting my B3-A40 as well, I've made backups of all my files with Wwr and SP flash tool, have tried flashing ported, signed (not entirely sure the signature used, as i used a hovatech tool, any attempts with android kitchen end in the image signing failing and me getting an unsigned_recovery.img), and padded TWRP recovery images, only to have the tablet to say something along the lines of "... CRITICAL: red state... rebooting to system..." when booting into recovery.
Find the stock recovery and boot images attached if anyone is interested. If you need/ want any other files from the backup I'm happy to oblige.
Good day all
i have been trying to flash a phone for a few weeks now with no success i have tried various flashing tools and some dont work at all and others have various errors appearing
currently i am using Qfil as thats been recommeneded a number of times but have had a number of errors with the software and this is the main error i get
11:37:47: INFO: File system.img is a sparse file, being split up into 7943 separate XML tags
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
11:37:50: {ERROR: StoreXMLFile:8890 2. Too many XML files in XMLStringTable, max is 8000
and i have tried various versions of the Qfil software from earliest to latest with no luck
until the other day i googled the error mentioned above and i came across a forum that linked to a flashing tool turned out to be Qfil again but on this occastion there was more activity it started the flashing process it appears to me it is flashing the images but seem to stop short of reaching 100% the amount transfered is different for each image it try sending and then errors out and moves onto the next image same thing raches a set percentage then error
i have attached some files a couple of screenshots plus the port trace txt file so hopefully someone can make sense of whats going on
im aware of some phones dont like being flashed with their battery still connected would it be worth cracking open the back cover and try disconnecting it
lastly to rule out any memory problems is there a tool that can read the emmc memory test it and detect any possible bad sectors if there is any issues how to get the flash tool to partition and flash around any bad sectors
many thanks
nighthawk658 said:
Good day all
i have been trying to flash a phone for a few weeks now with no success i have tried various flashing tools and some dont work at all and others have various errors appearing
currently i am using Qfil as thats been recommeneded a number of times but have had a number of errors with the software and this is the main error i get
11:37:47: INFO: File system.img is a sparse file, being split up into 7943 separate XML tags
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
11:37:50: {ERROR: StoreXMLFile:8890 2. Too many XML files in XMLStringTable, max is 8000
and i have tried various versions of the Qfil software from earliest to latest with no luck
until the other day i googled the error mentioned above and i came across a forum that linked to a flashing tool turned out to be Qfil again but on this occastion there was more activity it started the flashing process it appears to me it is flashing the images but seem to stop short of reaching 100% the amount transfered is different for each image it try sending and then errors out and moves onto the next image same thing raches a set percentage then error
i have attached some files a couple of screenshots plus the port trace txt file so hopefully someone can make sense of whats going on
im aware of some phones dont like being flashed with their battery still connected would it be worth cracking open the back cover and try disconnecting it
lastly to rule out any memory problems is there a tool that can read the emmc memory test it and detect any possible bad sectors if there is any issues how to get the flash tool to partition and flash around any bad sectors
many thanks
Click to expand...
Click to collapse
What is the device model number? What are you trying to flash? Are you trying to flash a stock software or are you trying to flash a custom software?
Droidriven said:
What is the device model number? What are you trying to flash? Are you trying to flash a stock software or are you trying to flash a custom software?
Click to expand...
Click to collapse
Thanks for your reply
Am trying to flash a stock firmware .. the mobile phone is an Asus ZenFone 5Q ZC600KL
I just noticed this minute that the error report from Qfil didn't upload I assume either this site doesn't allow txt documents or the size of the file it's to big
It's actually the error report in text file that would be more relevant
nighthawk658 said:
Thanks for your reply
Am trying to flash a stock firmware .. the mobile phone is an Asus ZenFone 5Q ZC600KL
I just noticed this minute that the error report from Qfil didn't upload I assume either this site doesn't allow txt documents or the size of the file it's to big
It's actually the error report in text file that would be more relevant
Click to expand...
Click to collapse
Try this, I tested the download link for the first firmware.zip on the list and it successfully downloaded.
Asus ZenFone 5 Lite Stock Firmware Collections [Back To Stock ROM]
Do you want to install Stock ROM on Asus ZenFone 5 Lite (ZC600KL)? then, you are at the right place. Here we will share all the latest Asus ZenFone 5 Lite
www.getdroidtips.com
Try downloading whichever firmware.zip of your choice from the list then try the two installation methods described in the guide.
Droidriven said:
Try this, I tested the download link for the first firmware.zip on the list and it successfully downloaded.
Asus ZenFone 5 Lite Stock Firmware Collections [Back To Stock ROM]
Do you want to install Stock ROM on Asus ZenFone 5 Lite (ZC600KL)? then, you are at the right place. Here we will share all the latest Asus ZenFone 5 Lite
www.getdroidtips.com
Try downloading whichever firmware.zip of your choice from the list then try the two installation methods described in the guide.
Click to expand...
Click to collapse
Thanks for that
I already have the firmware so am good with that
Reading the instructions I have not tired the first one yet by placing the firmware on memory card but will get a card and try that option ... ( BUT ) by trying to get into recovery mode or factory reset those options don't appear because that was the first thing I tried is getting into that menu for a factory reset but all I can get is CSC fastboot.. will recovery come up if the firmware is on a mem card
Second option I cannot do because the bootloader is locked and I cannot access the developer options or the OEM unlock because the phone is stuck on Logo
It I attempt to flash by fastboot it just says cannot flash in locked state
Will ask the missus for her mem card and try that recovery ootion but not sure if it will go but worth a shot..
But if flashing in EDL mode is my last resort I ideally need to get to the bottom of what's causing errors one error I seen comes up NAK and the rest are not completing the various images system stops at 84% other images at different percentages
nighthawk658 said:
Thanks for that
I already have the firmware so am good with that
Reading the instructions I have not tired the first one yet by placing the firmware on memory card but will get a card and try that option ... ( BUT ) by trying to get into recovery mode or factory reset those options don't appear because that was the first thing I tried is getting into that menu for a factory reset but all I can get is CSC fastboot.. will recovery come up if the firmware is on a mem card
Second option I cannot do because the bootloader is locked and I cannot access the developer options or the OEM unlock because the phone is stuck on Logo
It I attempt to flash by fastboot it just says cannot flash in locked state
Will ask the missus for her mem card and try that recovery ootion but not sure if it will go but worth a shot..
But if flashing in EDL mode is my last resort I ideally need to get to the bottom of what's causing errors one error I seen comes up NAK and the rest are not completing the various images system stops at 84% other images at different percentages
Click to expand...
Click to collapse
Have you tried doing a Google search for the specific error that you were getting?
Where did you download the firmware that you have been trying to flash? If you extract the file that you have, what is inside of it? Do you know if it is an update file that was designed to be flashed via stock recovery or is it an update file that was designed to be flashed via other flash tools? It makes a difference, if it was not designed to be flashed via stock recovery then it will not work. There is a difference between a firmware flash file and a stock recovery flashable update.
Try downloading the file listed in the guide because you can be 100% sure that it will work via the methods discussed in the guide provided that you follow the instructions to the letter. Just make sure to rename the file(the file I'm telling you to download) to "update.zip" or it will not flash.
As for why you are having issues with booting into stock recovery, what methods have you used to try getting into recovery? Does your device have a bootloader menu that gives you options to boot into bootloader mode, recovery mode, etc? Have you try using adb to issue the "adb reboot recovery" command? Can you connect to fastboot and reboot recovery?
Droidriven said:
Have you tried doing a Google search for the specific error that you were getting?
Where did you download the firmware that you have been trying to flash? If you extract the file that you have, what is inside of it? Do you know if it is an update file that was designed to be flashed via stock recovery or is it an update file that was designed to be flashed via other flash tools? It makes a difference, if it was not designed to be flashed via stock recovery then it will not work. There is a difference between a firmware flash file and a stock recovery flashable update.
Try downloading the file listed in the guide because you can be 100% sure that it will work via the methods discussed in the guide provided that you follow the instructions to the letter. Just make sure to rename the file(the file I'm telling you to download) to "update.zip" or it will not flash.
As for why you are having issues with booting into stock recovery, what methods have you used to try getting into recovery? Does your device have a bootloader menu that gives you options to boot into bootloader mode, recovery mode, etc? Have you try using adb to issue the "adb reboot recovery" command? Can you connect to fastboot and reboot recovery?
Click to expand...
Click to collapse
Yes did try to Google the errors but seem to be very little information about the errors and what does come up either relates to a different phone or states various things like changing drivers and versions of flash tool
The firmware I got is the exact firmware version I found on the phone I got the firmware version by pulling the version.bin file off of the phone and opening it in a hex program it was rather hard to find the version I can't remember the site I found it on but it all appears to be a complete set of files
In the firmware it has all the image files boot.img system.img and so on also the .elf files needed for Qfil the patch and so on
It also contains the batch files for using fastboot
In fastboot I can detect the phone using fastboot devices command it shows the serial number when executing the flashall command it will start sending data but will then just say cannot flash in locked state
I have tried ADB commands and from what I can remember it doesn't respond even ADB devices command shows nothing I assume because debugging is not enabled
To enter the recovery and or factory reset menu I tried all the combination the hold down of volume down plus power and volume up plus power only thing that appears is the CSC fastboot mode so where I would normally enter into factory reset on other phones using the standard procedure doesn't work on this phone
And I can enter EDL by holding both volume buttons and plugging in usb cable
I would like to post the last errors as I mentioned above that shows an error NAK and where it shows on each image it stops at a fixed percentage for example system.img stops at 84%
Due to the huge amount of data in the text file I can't copy it on here
Unfortunately I can't get a memory card yet stores nearby not got one in 4GB range in stock and due to restrictions can't get into city so am a bit stuck there
nighthawk658 said:
Yes did try to Google the errors but seem to be very little information about the errors and what does come up either relates to a different phone or states various things like changing drivers and versions of flash tool
The firmware I got is the exact firmware version I found on the phone I got the firmware version by pulling the version.bin file off of the phone and opening it in a hex program it was rather hard to find the version I can't remember the site I found it on but it all appears to be a complete set of files
In the firmware it has all the image files boot.img system.img and so on also the .elf files needed for Qfil the patch and so on
It also contains the batch files for using fastboot
In fastboot I can detect the phone using fastboot devices command it shows the serial number when executing the flashall command it will start sending data but will then just say cannot flash in locked state
I have tried ADB commands and from what I can remember it doesn't respond even ADB devices command shows nothing I assume because debugging is not enabled
To enter the recovery and or factory reset menu I tried all the combination the hold down of volume down plus power and volume up plus power only thing that appears is the CSC fastboot mode so where I would normally enter into factory reset on other phones using the standard procedure doesn't work on this phone
And I can enter EDL by holding both volume buttons and plugging in usb cable
I would like to post the last errors as I mentioned above that shows an error NAK and where it shows on each image it stops at a fixed percentage for example system.img stops at 84%
Due to the huge amount of data in the text file I can't copy it on here
Unfortunately I can't get a memory card yet stores nearby not got one in 4GB range in stock and due to restrictions can't get into city so am a bit stuck there
Click to expand...
Click to collapse
Trying different versions of flashtool has been known to solve flashing issues.
As for fastboot saying it can't flash while in locked state. Have you tried connecting to fastboot and then typing the command:
fastboot OEM unlock
Or
fastboot flashing unlock
If those don't work, do a Google search for:
"How to unlock bootloader (your specific model number"
Unlocking bootloader may allow fastboot to flash your file(s). Try flashing the whole file first, if it will not flash all at once, try flashing the .img files one at a time, but, make sure you use the correct command for each individual .img, using the wrong command could flash them in the wrong partition which would then cause a bigger problem to fix.
If your file has a series of .img files in it when you extract it, then the file you have is not the file that is designed to be flashed via stock recovery. That file is not going to work with the methods described in the guide. Stop being stubborn and listen to me, download the update from the guide, download it, download it, download it.
The memory card doesn't necessarily have to be 4GB, it can be any size greater than that, you only need the card as a medium to store the file so that stock recovery can find, access and flash the file.
Not all devices boot into recovery the same way, some have different button combinations and some have a bootloader menu with recovery as one of the options on the list. Unless you have corrupted your recovery partition, you should be able to boot into recovery.
You may have to use "fastboot erase" commands to wipe the cache partition and system partition then try flashing the firmware via fastboot. E.g. "fastboot erase cache" and "fastboot erase system". This may clear out any issues that were interfering with it successfully flashing. Have you tried extracting the file that you have and then flashing each individual file one at a time via fastboot? For exampleq:
fastboot flash system <name of your system.img>
fastboot flash boot <name of your boot.img>
If you attempt to flash your .img files via fastboot, remember to put your file in your fastboot folder on your PC, then extract the various .img files from inside it. Then, with the fastboot folder open in Windows file explorer, hold the shift key then right-click on your mouse, in the menu that pops up, select "open command here".
How did this issue start? What was your original reason for flashing the device? How many different ways have you tried to flash the device and what problems did you encounter with those methods? Depending on what you have tried up to now, you may have corrupted the device to the point that normal flashing methods won't work. You may have to use EDL mode to flash it. Have you found a guide that explains how to flash your specific device using EDL mode?
Please read this post carefully and answer every question I've asked. I'm trying to approach your issue from as many different angles as possible, maybe one of them will lead to a solution.
Hi
thanks for the new tips i will give that erase method a go and flashing the IMG files one by one as you suggested and will update on that either way i think that is the one method i have not tried yet because all the instructions i followed was based either on fastboot and using the flashall command or the Qfil under EDL mode and thinking about it if the old files are still on the phone might be why it wont flash the new ones
you asked how the issue started and reason for flashing well the phone got stuck on the Asus Logo when powering the phone on it would flash up saying powered by android then the asus logo will apear and its stuck there
the next process was to do what i would do with any phone is try to do a recovery / factory reset by using the volume down and power buttons but phone doesnt respond so tried the volume up and power and just brings me into CSC fastboot mode i tried holding volume button down press power and release power when phone vibtates but kept holding volume nothing happened ans then i tried holding both volume buttons plus power no response so either the phone was setup in a way that the recovery options was never there or some how the phone got corrupted i dont know because one minute it was working as normal and next its the Asus logo
tho i should say the phone at times had got a little warm usually because the phone is a bit of a work horse meaning its always being used for video recording and uploading and other work related tasks
all that i have tried has been the fastboot options such as being able to detect the phone via the fastboot devices command and that does bring up the serial number and have tried to use the flashall command per what the instructions said it would appear its doing something then suddenly it will give up the error cannot flashed in lock state oh yes and did run a command that bring up info about the bootloader and it states the bootloader unlocked is set to false
then i have tried the Qfil software and in most cases it had always given errors such as sahara errors and too many XML in string table max was supposed to be 8000 but it was something like 8900
the interesting thing to note is that i had downloaded several firmwares because i was not sure of the exact firmware on the phone so i was left guessing at the selection that was given so i tried working with a more up to date the interesting part about that is when trying in fastboot the error was different compared to the last 2 firmwares i tried the first 3 i tried i would get almost instantly a write protected error where as the last 2 firmwares will bring up the cannot falsh in locked state error so it seems to me the newer versions of the firmware the phone is rejecting where as the last 2 firmwares the phone seems to respond to them and fastboot might accept them if the bootloader is unlocked
back to Qfil i tried researching the various errors that displaed mainly the too many XML in string table and came across a post on XDA regarding Flashone 2.0 it has a Qfil flasher within its folders and i have tried that and that is the one that gave me the most action and that is what i discussed above when it copies over the IMG files it would stop and error at certian percentages such as system.bin 85% another image maybe 20% i will try and copy a snippet of the log on here so you can see for your self and this version of the Qfil was the first time i ever seen the blue progress bar move
in your reply you mentioned about using an update file i assume is where you mentioned the memory card i cant do the memory card option just yet because i cant get access to memor card have to rely on stores near home and dont have in stock size i need i dont want to go out and buy a huge size as i rarely ever use memor cards .. and i do believe one of the firmwares i download was actually an update rather than a folder full of files and because i cannot access any of the options under hardware key on start up im in doubt that accessing the memory card to recover would work anyway
now looking at the website you gave with the instructions i believe the memory card option as mentioned may not work because the volume up plus power puts the phone into CSC fastboot mode only
second option is install via ADB Sideload but the requirements is the phone needs to have its developer options enabled and thats disabled on this phone
as for the question about the bootloader yes have tried those commands you mentioned doesnt work and any research on unlocking bootloader for this model seems to always bring me back to the same options by using the APK file from Asus or the ADB commands
by the way here is the list of firmwares i have tried not sure if the info will help but its here anyway just in case Note the last 2 firmwares are the ones i mentioned above that seems to make the phone respond differently compared to the first ones
Asus_Zenfone_5_Lite_ZC600KL_630_14.0400_1808.057_20180903_CMD
ASUS Factory WW ZC600KL(630)-14.0400.1807.056-20180816
[firmware27]NGI77B.WW_Phone-14.0400.1801.018-20180128(SW_T89199AA1_V018_M10_EF_ASUS_ZC600KL_USRD_ATO)
UL-ASUS_X017D_2-WW-14.0400.1811.061-user
[up_vnROM.net]_WW__ZC600KL(630)_14.0400.1801.031_20180313_Phone-user
WW__ZC600KL(630)_14.0400.1801.021_20180204_Phone-user
the last firmware on the list is the one i believe is the original version thats installed on the phone as i managed to pull the version.bin off of the device and open the bin file using Hex and this was what i found
4028938�1ASUS_X017D_2���asus/WW_Phone/ASUS_X017D_2:7.1.1/NGI77B/14.0400.1801.021-20180204:user/release-keys���������������������������������������������wt89199-user������������wt89199-user 7.1.1 NGI77B 14.0400.1801.021-20180204 release-keys��������������������WW__ASUS_X017DA_14.0400.1801.021����������������SW_T89199AA1_V021_M10_NF_ASUS_ZC600KL_USR_TEST��������������
here is a quick snippet from the text document of the error that i mentioned about when it stops copying after a certain percentage
this is one of the erorrs i mentioned 12:31:43: DEBUG: Response was 'NAK'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
12:31:43: {ERROR: handleProgram:7786 Please see log
12:31:43: INFO: In handleProgram('tz.mbn')
12:31:43: DEBUG:
second error
i will need to post the details a bit later cant find the full error its not showing in the log file but seems to only appear within Qfil so will attempt to get those details later
am downloading one of the firmwares from the link you gave
Droidriven said:
Trying different versions of flashtool has been known to solve flashing issues.
As for fastboot saying it can't flash while in locked state. Have you tried connecting to fastboot and then typing the command:
fastboot OEM unlock
Or
fastboot flashing unlock
If those don't work, do a Google search for:
"How to unlock bootloader (your specific model number"
Unlocking bootloader may allow fastboot to flash your file(s). Try flashing the whole file first, if it will not flash all at once, try flashing the .img files one at a time, but, make sure you use the correct command for each individual .img, using the wrong command could flash them in the wrong partition which would then cause a bigger problem to fix.
If your file has a series of .img files in it when you extract it, then the file you have is not the file that is designed to be flashed via stock recovery. That file is not going to work with the methods described in the guide. Stop being stubborn and listen to me, download the update from the guide, download it, download it, download it.
The memory card doesn't necessarily have to be 4GB, it can be any size greater than that, you only need the card as a medium to store the file so that stock recovery can find, access and flash the file.
Not all devices boot into recovery the same way, some have different button combinations and some have a bootloader menu with recovery as one of the options on the list. Unless you have corrupted your recovery partition, you should be able to boot into recovery.
You may have to use "fastboot erase" commands to wipe the cache partition and system partition then try flashing the firmware via fastboot. E.g. "fastboot erase cache" and "fastboot erase system". This may clear out any issues that were interfering with it successfully flashing. Have you tried extracting the file that you have and then flashing each individual file one at a time via fastboot? For exampleq:
fastboot flash system <name of your system.img>
fastboot flash boot <name of your boot.img>
If you attempt to flash your .img files via fastboot, remember to put your file in your fastboot folder on your PC, then extract the various .img files from inside it. Then, with the fastboot folder open in Windows file explorer, hold the shift key then right-click on your mouse, in the menu that pops up, select "open command here".
How did this issue start? What was your original reason for flashing the device? How many different ways have you tried to flash the device and what problems did you encounter with those methods? Depending on what you have tried up to now, you may have corrupted the device to the point that normal flashing methods won't work. You may have to use EDL mode to flash it. Have you found a guide that explains how to flash your specific device using EDL mode?
Please read this post carefully and answer every question I've asked. I'm trying to approach your issue from as many different angles as possible, maybe one of them will lead to a solution.
Click to expand...
Click to collapse
here is an update
have downloaded the firmware from the site you mentioned but i will need to wait till i get a memory card and cannot do the sideloading using ADB as i cannot enable developer options but i did try it anyway and will show the error messages
i also tried the erase command you mentioned i tried the erase on the cache it seemed to have done something rather quickly but did not show any error so then tried to flash the cache image from the firmware folder and did get an error
here is the errors for both adb and fastboot commands note there is 2 errors for the flash part because i did it fastboot flash cache.bin but per your message it said to fastboot flash cache cache.bin
Under ADB commands
C:\Users\Me\Desktop\firmware flashing>adb sideload update.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
fastboot commands
C:\Users\Me\Desktop\firmware flashing>fastboot devices
J2AXHM011670RNJ fastboot
C:\Users\Me\Desktop\firmware flashing>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.008s]
Finished. Total time: 0.023s
C:\Users\Me\Desktop\firmware flashing>fastboot flash cache.bin
unknown partition 'cache.bin'
fastboot: error: cannot determine image filename for 'cache.bin'
C:\Users\Me\Desktop\firmware flashing>fastboot flash cache cache.bin
fastboot: error: cannot load 'cache.bin': No such file or directory
as you asked earlier about the files within the firmware folder i have taken a screenshot so you can have a look at whats what it also should show the version details there also
i have also attached a text document (( i hope it shows up on site this time )) this is the log i saved directly from the information under the progress bar in Qfil it shows a lot of errors but i will also show what i was talking about when i mentioned it stops afrer a certain percentage
hope the information given could be helpful
again thanks for your time much appreciated
nighthawk658 said:
here is an update
have downloaded the firmware from the site you mentioned but i will need to wait till i get a memory card and cannot do the sideloading using ADB as i cannot enable developer options but i did try it anyway and will show the error messages
i also tried the erase command you mentioned i tried the erase on the cache it seemed to have done something rather quickly but did not show any error so then tried to flash the cache image from the firmware folder and did get an error
here is the errors for both adb and fastboot commands note there is 2 errors for the flash part because i did it fastboot flash cache.bin but per your message it said to fastboot flash cache cache.bin
Under ADB commands
C:\Users\Me\Desktop\firmware flashing>adb sideload update.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
fastboot commands
C:\Users\Me\Desktop\firmware flashing>fastboot devices
J2AXHM011670RNJ fastboot
C:\Users\Me\Desktop\firmware flashing>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.008s]
Finished. Total time: 0.023s
C:\Users\Me\Desktop\firmware flashing>fastboot flash cache.bin
unknown partition 'cache.bin'
fastboot: error: cannot determine image filename for 'cache.bin'
C:\Users\Me\Desktop\firmware flashing>fastboot flash cache cache.bin
fastboot: error: cannot load 'cache.bin': No such file or directory
as you asked earlier about the files within the firmware folder i have taken a screenshot so you can have a look at whats what it also should show the version details there also
i have also attached a text document (( i hope it shows up on site this time )) this is the log i saved directly from the information under the progress bar in Qfil it shows a lot of errors but i will also show what i was talking about when i mentioned it stops afrer a certain percentage
hope the information given could be helpful
again thanks for your time much appreciated
Click to expand...
Click to collapse
The command to flash your cache.bin is:
fastboot flash cache cache.bin
Fastboot commands to flash .img/.bin files to their proper partitions work like this:
fastboot flash <name of partition> <name of .img/.bin>
For example, to flash system.img:
fastboot flash system system.img
Do you see how it says "fastboot flash system" and then it says "system.img"? Do you see how it says "fastboot flash"(this tells fastboot that you want to flash a file), then it says "system"(this tells fastboot which physical partition you want to flash a file to), then it says "system.img"(this tells fastboot which file you want to flash to the specified partition)? You are telling fastboot that you want to flash "this" partition with "that" file.
To flash recovery:
fastboot flash recovery recovery.img
Again, the action that you want fastboot to perform(fastboot flash) followed by the name of the partition(recovery) followed by the name of the file that you want to flash to that partition(recovery.img)
A bit overdefined but I hope this helps you understand the structure or syntax required for fastboot flash commands.
To post your .txt file, upload it to hosting site of some kind and then post a link to it here then it can be viewed here.
Also, just to be sure, place your files inside your fastboot folder on your PC, then, when you open a command window, do it by going to the fastboot folder in Windows file explorer, then, with the mouse pointer somewhere in the empty field of that folder, hold the shift key and then right click, on that menu that pops up, select "open command here", then try the commands. This "might" fix the unknown file error because it bypasses the need for a file path in your commands and flashes files located in the fastboot folder by default without having a path name in the commands, you don't have to tell it to look for the file in fastboot folder, it does it automatically if the file is located in that folder.
Other than what I have told you so far, I think I might agree with you that you may not get anything to work with the bootloader being locked and USB debugging not being enabled. You may have to resort to EDL flashing methods, it is more of a "brute force" flashing method as it bypasses the bootloader.
Droidriven said:
The command to flash your cache.bin is:
fastboot flash cache cache.bin
Fastboot commands to flash .img/.bin files to their proper partitions work like this:
fastboot flash <name of partition> <name of .img/.bin>
For example, to flash system.img:
fastboot flash system system.img
Do you see how it says "fastboot flash system" and then it says "system.img"? Do you see how it says "fastboot flash"(this tells fastboot that you want to flash a file), then it says "system"(this tells fastboot which physical partition you want to flash a file to), then it says "system.img"(this tells fastboot which file you want to flash to the specified partition)? You are telling fastboot that you want to flash "this" partition with "that" file.
To flash recovery:
fastboot flash recovery recovery.img
Again, the action that you want fastboot to perform(fastboot flash) followed by the name of the partition(recovery) followed by the name of the file that you want to flash to that partition(recovery.img)
A bit overdefined but I hope this helps you understand the structure or syntax required for fastboot flash commands.
To post your .txt file, upload it to hosting site of some kind and then post a link to it here then it can be viewed here.
Also, just to be sure, place your files inside your fastboot folder on your PC, then, when you open a command window, do it by going to the fastboot folder in Windows file explorer, then, with the mouse pointer somewhere in the empty field of that folder, hold the shift key and then right click, on that menu that pops up, select "open command here", then try the commands. This "might" fix the unknown file error because it bypasses the need for a file path in your commands and flashes files located in the fastboot folder by default without having a path name in the commands, you don't have to tell it to look for the file in fastboot folder, it does it automatically if the file is located in that folder.
Other than what I have told you so far, I think I might agree with you that you may not get anything to work with the bootloader being locked and USB debugging not being enabled. You may have to resort to EDL flashing methods, it is more of a "brute force" flashing method as it bypasses the bootloader.
Click to expand...
Click to collapse
ok here is the latest
i tried the flashing of files again as i realised my mistake yesterday was using the extention .bin when it should of been .img i think the word bin got stuck in my brain because of the Qfil software as i access it from Bin folder haha
anyway i did the fastboot earse cache command and seemed ok
and then attempted to flash the cache.img file using fastboot flash cache cache.img and i got error
C:\Users\Me\Desktop\flashing folder>fastboot flash cache cache.img
Sending 'cache' (6400 KB) OKAY [ 0.265s]
Writing 'cache' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
i am suspecting thats because the bootloader is locked as per your question about researching how to unlock my bootloader sadly i been unable to find any working solution for this model other than the unlock app via the asus website but since the phone doesnt boot thats of no use
so i either need another method to unlock the bootloader and try flashing again or i need to be able to flash via EDL mode
by the way here is details from getvar all command just in case if any of the info is of any use
C:\Users\Me\Desktop\flashing folder>fastboot getvar all
(bootloader) hw-revision:10000
(bootloader) unlocked:no
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4068
(bootloader) version-baseband:
(bootloader) version-bootloader-CS2-8.0-user
(bootloader) erase-block-size: 0x200
(bootloader) logical-block-size: 0x200
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xD20BF7E00
(bootloader) partition-type:version:raw
(bootloader) partition-size:version: 0x500000
(bootloader) partition-typeem:raw
(bootloader) partition-sizeem: 0x4000000
(bootloader) partition-type:APD:ext4
(bootloader) partition-size:APD: 0xD000000
(bootloader) partition-type:ADF:ext4
(bootloader) partition-size:ADF: 0x2000000
(bootloader) partition-type:asusfw:raw
(bootloader) partition-size:asusfw: 0x4000000
(bootloader) partition-type:wt_ftm:raw
(bootloader) partition-size:wt_ftm: 0x500000
(bootloader) partition-type:asdf:ext4
(bootloader) partition-size:asdf: 0x4000000
(bootloader) partition-type:factorybak:raw
(bootloader) partition-size:factorybak: 0xA00000
(bootloader) partition-type:factory:raw
(bootloader) partition-size:factory: 0xA00000
(bootloader) partition-type:asuskey6:raw
(bootloader) partition-size:asuskey6: 0x100000
(bootloader) partition-type:asuskey5:raw
(bootloader) partition-size:asuskey5: 0x100000
(bootloader) partition-type:asuskey4:raw
(bootloader) partition-size:asuskey4: 0x100000
(bootloader) partition-type:asuskey3:raw
(bootloader) partition-size:asuskey3: 0x100000
(bootloader) partition-type:asuskey2:raw
(bootloader) partition-size:asuskey2: 0x100000
(bootloader) partition-type:asuskey:raw
(bootloader) partition-size:asuskey: 0x100000
(bootloader) partition-type:vbmetabak:raw
(bootloader) partition-size:vbmetabak: 0x10000
(bootloader) partition-type:vbmeta:raw
(bootloader) partition-size:vbmeta: 0x10000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:devcfgbak:raw
(bootloader) partition-size:devcfgbak: 0x100000
(bootloader) partition-type:devcfg:raw
(bootloader) partition-size:devcfg: 0x100000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x400000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x400000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:bluetoothbak:raw
(bootloader) partition-size:bluetoothbak: 0x100000
(bootloader) partition-type:bluetooth:raw
(bootloader) partition-size:bluetooth: 0x100000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x1000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x20A4000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x400
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x1000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:ablbak:raw
(bootloader) partition-size:ablbak: 0x100000
(bootloader) partition-type:abl:raw
(bootloader) partition-size:abl: 0x100000
(bootloader) partition-type:dspbak:raw
(bootloader) partition-size:dspbak: 0x1000000
(bootloader) partition-type:dsp:raw
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:modem:raw
(bootloader) partition-size:modem: 0x6E00000
(bootloader) partition-type:mdtp:raw
(bootloader) partition-size:mdtp: 0x2000000
(bootloader) partition-type:mdtpsecappbak:raw
(bootloader) partition-size:mdtpsecappbak: 0x400000
(bootloader) partition-type:mdtpsecapp:raw
(bootloader) partition-size:mdtpsecapp: 0x400000
(bootloader) partition-type:cmnlib64bak:raw
(bootloader) partition-size:cmnlib64bak: 0x100000
(bootloader) partition-type:cmnlibbak:raw
(bootloader) partition-size:cmnlibbak: 0x100000
(bootloader) partition-type:cmnlib64:raw
(bootloader) partition-size:cmnlib64: 0x100000
(bootloader) partition-type:cmnlib:raw
(bootloader) partition-size:cmnlib: 0x100000
(bootloader) partition-type:keymasterbak:raw
(bootloader) partition-size:keymasterbak: 0x100000
(bootloader) partition-type:keymaster:raw
(bootloader) partition-size:keymaster: 0x100000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x120000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x8000000
(bootloader) partition-type:recovery:raw
(bootloader) partition-size:recovery: 0x4000000
(bootloader) partition-type:boot:raw
(bootloader) partition-size:boot: 0x4000000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x400000
(bootloader) partition-typemicbak:raw
(bootloader) partition-sizemicbak: 0x80000
(bootloader) partition-typemic:raw
(bootloader) partition-sizemic: 0x80000
(bootloader) partition-type:hypbak:raw
(bootloader) partition-size:hypbak: 0x80000
(bootloader) partition-type:hyp:raw
(bootloader) partition-size:hyp: 0x80000
(bootloader) partition-type:rpmbak:raw
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:raw
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:tzbak:raw
(bootloader) partition-size:tzbak: 0x400000
(bootloader) partition-type:tz:raw
(bootloader) partition-size:tz: 0x400000
(bootloader) partition-type:xblbak:raw
(bootloader) partition-size:xblbak: 0x380000
(bootloader) partition-type:xbl:raw
(bootloader) partition-size:xbl: 0x380000
(bootloader) project-info:ZC600KL-SDM630
(bootloader) aft_support:yes
(bootloader) secure:yes
(bootloader) serial:c462427
(bootloader) product:sdm660
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 5.844s
nighthawk658 said:
ok here is the latest
i tried the flashing of files again as i realised my mistake yesterday was using the extention .bin when it should of been .img i think the word bin got stuck in my brain because of the Qfil software as i access it from Bin folder haha
anyway i did the fastboot earse cache command and seemed ok
and then attempted to flash the cache.img file using fastboot flash cache cache.img and i got error
C:\Users\Me\Desktop\flashing folder>fastboot flash cache cache.img
Sending 'cache' (6400 KB) OKAY [ 0.265s]
Writing 'cache' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
i am suspecting thats because the bootloader is locked as per your question about researching how to unlock my bootloader sadly i been unable to find any working solution for this model other than the unlock app via the asus website but since the phone doesnt boot thats of no use
so i either need another method to unlock the bootloader and try flashing again or i need to be able to flash via EDL mode
by the way here is details from getvar all command just in case if any of the info is of any use
C:\Users\Me\Desktop\flashing folder>fastboot getvar all
(bootloader) hw-revision:10000
(bootloader) unlocked:no
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4068
(bootloader) version-baseband:
(bootloader) version-bootloader-CS2-8.0-user
(bootloader) erase-block-size: 0x200
(bootloader) logical-block-size: 0x200
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xD20BF7E00
(bootloader) partition-type:version:raw
(bootloader) partition-size:version: 0x500000
(bootloader) partition-typeem:raw
(bootloader) partition-sizeem: 0x4000000
(bootloader) partition-type:APD:ext4
(bootloader) partition-size:APD: 0xD000000
(bootloader) partition-type:ADF:ext4
(bootloader) partition-size:ADF: 0x2000000
(bootloader) partition-type:asusfw:raw
(bootloader) partition-size:asusfw: 0x4000000
(bootloader) partition-type:wt_ftm:raw
(bootloader) partition-size:wt_ftm: 0x500000
(bootloader) partition-type:asdf:ext4
(bootloader) partition-size:asdf: 0x4000000
(bootloader) partition-type:factorybak:raw
(bootloader) partition-size:factorybak: 0xA00000
(bootloader) partition-type:factory:raw
(bootloader) partition-size:factory: 0xA00000
(bootloader) partition-type:asuskey6:raw
(bootloader) partition-size:asuskey6: 0x100000
(bootloader) partition-type:asuskey5:raw
(bootloader) partition-size:asuskey5: 0x100000
(bootloader) partition-type:asuskey4:raw
(bootloader) partition-size:asuskey4: 0x100000
(bootloader) partition-type:asuskey3:raw
(bootloader) partition-size:asuskey3: 0x100000
(bootloader) partition-type:asuskey2:raw
(bootloader) partition-size:asuskey2: 0x100000
(bootloader) partition-type:asuskey:raw
(bootloader) partition-size:asuskey: 0x100000
(bootloader) partition-type:vbmetabak:raw
(bootloader) partition-size:vbmetabak: 0x10000
(bootloader) partition-type:vbmeta:raw
(bootloader) partition-size:vbmeta: 0x10000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:devcfgbak:raw
(bootloader) partition-size:devcfgbak: 0x100000
(bootloader) partition-type:devcfg:raw
(bootloader) partition-size:devcfg: 0x100000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x400000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x400000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:bluetoothbak:raw
(bootloader) partition-size:bluetoothbak: 0x100000
(bootloader) partition-type:bluetooth:raw
(bootloader) partition-size:bluetooth: 0x100000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x1000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x20A4000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x400
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x1000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:ablbak:raw
(bootloader) partition-size:ablbak: 0x100000
(bootloader) partition-type:abl:raw
(bootloader) partition-size:abl: 0x100000
(bootloader) partition-type:dspbak:raw
(bootloader) partition-size:dspbak: 0x1000000
(bootloader) partition-type:dsp:raw
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:modem:raw
(bootloader) partition-size:modem: 0x6E00000
(bootloader) partition-type:mdtp:raw
(bootloader) partition-size:mdtp: 0x2000000
(bootloader) partition-type:mdtpsecappbak:raw
(bootloader) partition-size:mdtpsecappbak: 0x400000
(bootloader) partition-type:mdtpsecapp:raw
(bootloader) partition-size:mdtpsecapp: 0x400000
(bootloader) partition-type:cmnlib64bak:raw
(bootloader) partition-size:cmnlib64bak: 0x100000
(bootloader) partition-type:cmnlibbak:raw
(bootloader) partition-size:cmnlibbak: 0x100000
(bootloader) partition-type:cmnlib64:raw
(bootloader) partition-size:cmnlib64: 0x100000
(bootloader) partition-type:cmnlib:raw
(bootloader) partition-size:cmnlib: 0x100000
(bootloader) partition-type:keymasterbak:raw
(bootloader) partition-size:keymasterbak: 0x100000
(bootloader) partition-type:keymaster:raw
(bootloader) partition-size:keymaster: 0x100000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x120000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x8000000
(bootloader) partition-type:recovery:raw
(bootloader) partition-size:recovery: 0x4000000
(bootloader) partition-type:boot:raw
(bootloader) partition-size:boot: 0x4000000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x400000
(bootloader) partition-typemicbak:raw
(bootloader) partition-sizemicbak: 0x80000
(bootloader) partition-typemic:raw
(bootloader) partition-sizemic: 0x80000
(bootloader) partition-type:hypbak:raw
(bootloader) partition-size:hypbak: 0x80000
(bootloader) partition-type:hyp:raw
(bootloader) partition-size:hyp: 0x80000
(bootloader) partition-type:rpmbak:raw
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:raw
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:tzbak:raw
(bootloader) partition-size:tzbak: 0x400000
(bootloader) partition-type:tz:raw
(bootloader) partition-size:tz: 0x400000
(bootloader) partition-type:xblbak:raw
(bootloader) partition-size:xblbak: 0x380000
(bootloader) partition-type:xbl:raw
(bootloader) partition-size:xbl: 0x380000
(bootloader) project-info:ZC600KL-SDM630
(bootloader) aft_support:yes
(bootloader) secure:yes
(bootloader) serial:c462427
(bootloader) product:sdm660
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 5.844s
Click to expand...
Click to collapse
Yep, that data shows the bootloader is definitely locked, I don't have anything else to offer for advice in the scenario you are in as I'm not familiar enough with your model number or hardware architecture. I'd probably get you stuck in worse position from here on. As far as I can tell since I started helping, you haven't really done anything except erase the cache.img, that shouldn't be too complicated to straighten out if you can get the firmware to flash. I don't understand why the firmware won't flash, if it is the exact same version that was already on the device, it seems like it should flash without having to unlock the bootloader. It may be due to USB debugging not being enabled instead of it being an issue with the bootloader being locked.
EDL seems to be your only option from here going forward, I doubt anything else will, its virtually your last and only shot.
Droidriven said:
Yep, that data shows the bootloader is definitely locked, I don't have anything else to offer for advice in the scenario you are in as I'm not familiar enough with your model number or hardware architecture. I'd probably get you stuck in worse position from here on. As far as I can tell since I started helping, you haven't really done anything except erase the cache.img, that shouldn't be too complicated to straighten out if you can get the firmware to flash. I don't understand why the firmware won't flash, if it is the exact same version that was already on the device, it seems like it should flash without having to unlock the bootloader. It may be due to USB debugging not being enabled instead of it being an issue with the bootloader being locked.
EDL seems to be your only option from here going forward, I doubt anything else will, its virtually your last and only shot.
Click to expand...
Click to collapse
yes does seem the bootloader or something to do with debugging is a possible issue
i have tried to use Qfil as mentioned before but that always kept throwing up errors and also has been a mix bag of activity also most of the versions of Qfil i tried never did anything other than throwing up an error almost instantly
but i did download a package named flashone and as mentioned before gave the most activity by actually trasnfering images and progress bar moving i think the progrss bar stopped at 85% with images stopping at random percentages but all in all that was more activity than it ever did before using Qflash so something is amiss somewhere
and it took me a while to figure out the exact firmware that was on the phone luckily i used San mobile Qualcomm tool and i pulled files off of the phone and looked in the version image using a hex tool and found the exact firmware
have even tried using san mobile tool to flash over the images but get an error
there is a suggestion it may be a hardware issue the fact that i can pull data off of the phone suggests its not a read problem
but to rule out any hardware issues do you know of any tools i can run a memory test look for bad sectors on the phone memory if any a way to partition around them
but i do thank you for all your assisance on this it has been very much appreciated