i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.
thejase said:
i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here
tabletalker7 said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here
Click to expand...
Click to collapse
I saw this. Will i keep my data with this method?
thejase said:
I saw this. Will i keep my data with this method?
Click to expand...
Click to collapse
no, but if you can't even boot to TWRP then you have nothing left to save at this point.
Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.
iElvis said:
Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.
Click to expand...
Click to collapse
thanks for the suggestions but no dice.
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.
thejase said:
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.
Click to expand...
Click to collapse
tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot ROM to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
So as it turns out that method worked using the bat file flash all fastboot. Though, not at first. When it first rebooted after the bat file finished flashing. system UI was still crashing. When you initially run the bat file at the beginning, it asks if you want to delete your data. First time around i said no, just to see what it would do. Well it booted, but kept getting that system ui crash that I had in the beginning of all this mess. I rebooted and this time chose to erase data and then it re-flashed all again (same bat file). Turns out, when it booted, same deal, system UI crash. So this time i was looking things up while the crashes where happening and then it just rebooted on its own (as it does with a number of system UI crashes in succession). When it came up it was that Chinese menu (which i assume to be download mode or something). Anyway, i chose English and it's a menu to clear dalvik and cache, system settings reset, and one other i can't remember. i did system settings then dalvik and finally, when i rebooted, it was like it was booting for the first time with no crashes. Only thing i can figure is that setting in the bat file at first launch actually didn't erase user data since when it booted, all my icons where there in the background. doing it "on device" in download mode seems to have worked. I am only adding this information as an f.y.i.. Thanks again for all your help, guys.
thejase said:
When it came up it was that Chinese menu (which i assume to be download mode or something).
Click to expand...
Click to collapse
That's stock recovery.
maigre said:
That's stock recovery.
Click to expand...
Click to collapse
Oh, ok. Funny thing is, I had never seen what that looked like as I immediately installed twrp from the time I bought it. Makes sense, though I still wonder why it booted to stock recovery after systemui crashing. Unless it senses the crashes and does that by default to clear system settings and data for a successful boot?
Related
I loaded my Rogers HTC one X with the CyanogenMod 10 - Endeavor Unleashed | 027 | UNIFIED HBOOT. It worked for a bit but is now stuck in the loading screen. I connected it to my PC and put it in fastboot and attempt to reflash the boot img and nothing changes. I have attempted to find an original RUU as mine is corrupted.
I have read the forums and see alot of fixes if you can access the phone to move the files to the SD however I cant get to that point. I am sure this has been answered somewhere but i haven't been able to find it as yet.
This is my first attempt to use a ROM.. The phone was unlocked via HTC dev. I have since read I should have also turned the S-off but I missed that before I flashed the ROM.
Any ideas would be appreciated.
Here is the info from the device.
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0000
(bootloader) version-baseband: 0.18as.32.09.28L
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.94.631.3
(bootloader) serialno: HT249W305429
(bootloader) imei: 359691042187149
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8d23f0c0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
c:\Android>
I originally posted this in the wrong forum. I was told not to use the international ROMS. I did try flashing cm-10-20121126-NIGHTLY-evita using the One X One Click v 1.9. When I reboot it it just gives me the CM loading screen.
First, we don't have S-Off yet. Whoever told you that doesn't know what they're talking about.
Flashing international/Tegra3 roms on this phone, as you've learned, won't work. There are certain Tegra3 roms that will hard-brick you, but I've seen people recover from flashing the wrong CM10. If you can still get to the bootloader, you're okay.
It's possible you corrupted your sd card. Try reformatting it.
Drag0nus said:
I loaded my Rogers HTC one X with the CyanogenMod 10 - Endeavor Unleashed | 027 | UNIFIED HBOOT. It worked for a bit but is now stuck in the loading screen. I connected it to my PC and put it in fastboot and attempt to reflash the boot img and nothing changes. I have attempted to find an original RUU as mine is corrupted.
I have read the forums and see alot of fixes if you can access the phone to move the files to the SD however I cant get to that point. I am sure this has been answered somewhere but i haven't been able to find it as yet.
This is my first attempt to use a ROM.. The phone was unlocked via HTC dev. I have since read I should have also turned the S-off but I missed that before I flashed the ROM.
Any ideas would be appreciated.
Here is the info from the device.
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0000
(bootloader) version-baseband: 0.18as.32.09.28L
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.94.631.3
(bootloader) serialno: HT249W305429
(bootloader) imei: 359691042187149
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8d23f0c0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
c:\Android>
I originally posted this in the wrong forum. I was told not to use the international ROMS. I did try flashing cm-10-20121126-NIGHTLY-evita using the One X One Click v 1.9. When I reboot it it just gives me the CM loading screen.
Click to expand...
Click to collapse
Also, try to format system and do factory reset using TWRP
While in a directory with ADB, fastboot and TWRP (custom recovery), Do the following command
fastboot boot TWRP.img
Then, in TWRP, go to wipe
Then go toilet pap--- oops
Jk but go to Factory Reset
When it's done, do wipe system
Then, finally install a rom and flash the kernel
Hope I helped!
Tanmaynarang said:
Also, try to format system and do factory reset using TWRP
While in a directory with ADB, fastboot and TWRP (custom recovery), Do the following command
fastboot boot TWRP.img
Then, in TWRP, go to wipe
Then go toilet pap--- oops
Jk but go to Factory Reset
When it's done, do wipe system
Then, finally install a rom and flash the kernel
Hope I helped!
Click to expand...
Click to collapse
Thank you for the idea.
I tried this but it goes to the HTC screen and stops.
Also I am now noticing that my SD is not accessible. I think I did something way wrong when I originally flashed the rom.
Drag0nus said:
Thank you for the idea.
I tried this but it goes to the HTC screen and stops.
Also I am now noticing that my SD is not accessible. I think I did something way wrong when I originally flashed the rom.
Click to expand...
Click to collapse
Did you wipe/factory reset in bootloader? That will completely wipe your sd card so that you have to reformat it.
iElvis said:
Did you wipe/factory reset in bootloader? That will completely wipe your sd card so that you have to reformat it.
Click to expand...
Click to collapse
Yes I did. The thing is I can't access the SD card to format it. when I try to mount the SD from the phone it does nothing either. I am very lost now.
Drag0nus said:
Yes I did. The thing is I can't access the SD card to format it. when I try to mount the SD from the phone it does nothing either. I am very lost now.
Click to expand...
Click to collapse
You need to mount it from your computer.
iElvis said:
You need to mount it from your computer.
Click to expand...
Click to collapse
Ok thanks. Can you point me in the right direction to be able to do so?
Drag0nus said:
Ok thanks. Can you point me in the right direction to be able to do so?
Click to expand...
Click to collapse
Just plug it in and navigate to your phone in Explorer. You should then get a prompt to format it.
iElvis said:
Just plug it in and navigate to your phone in Explorer. You should then get a prompt to format it.
Click to expand...
Click to collapse
That's the thing. I hook it to the PC, it will open sence but it doesnt show in explorer now.
Drag0nus said:
That's the thing. I hook it to the PC, it will open sence but it doesnt show in explorer now.
Click to expand...
Click to collapse
Are you in bootloader? Try a different cable, or different USB port.
Try plugging it in, shutting down, and rebooting to bootloader. Sometimes it takes some effort to get it to show up.
Go to my computer. Right click where it says removable storage .... format.. it WILL erase everything. But hey, at least you Still have a phone right
Sent from my One X using Tapatalk 2
Just run rogers 1.94 ruu
The problem is that the computer does not see it as a storage device because the SD card doesn't show up I have tried multiple computers and multiple cables any suggestions
Sent from my SGH-I747M using xda app-developers app
try this
http://forums.team-nocturnal.com/showthread.php/1050
You are going into TWRP and clicking mount usb storage to get windows to recognize it right?
codeprimate said:
try this
http://forums.team-nocturnal.com/showthread.php/1050
Click to expand...
Click to collapse
Thanks. this worked and I just finished flashing the new ROM and am waiting for it to complete and then I should be golden.
Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks
I suggest reflashing kernel.
Wysłane z mojego HTC One S przy użyciu Tapatalka
jaco_lbn said:
I suggest reflashing kernel.
Wysłane z mojego HTC One S przy użyciu Tapatalka
Click to expand...
Click to collapse
Thanks, but I even cannot get into recovery
velvel said:
Thanks, but I even cannot get into recovery
Click to expand...
Click to collapse
Hm, really strange behavior, had couple of HTC phones but never seen something like this happening.
I did run RUU (first changed cid and relocked), everything went fine (no errors), but still cannot boot. My experience so far was that if RUU runs fine, you should boot without problem. Thinking more and more that there is some hardware problem, that is causing phone to bootloop.
If anyone has any idea, I would appreciate it a lot.
Thanks
Build me a scenario
velvel said:
Hm, really strange behavior, had couple of HTC phones but never seen something like this happening.
I did run RUU (first changed cid and relocked), everything went fine (no errors), but still cannot boot. My experience so far was that if RUU runs fine, you should boot without problem. Thinking more and more that there is some hardware problem, that is causing phone to bootloop.
If anyone has any idea, I would appreciate it a lot.
Thanks
Click to expand...
Click to collapse
According to your first post, everything seems to be okay. Your drivers are seeing the phone, and the phone is recognizing its hardware.
Which recoveries did you try to flash? (TWRP, CWM)
And which version?
Have you tried to reroot the device and flash a recovery again since running the RUU?
From my experience with running an RUU, you should be able to boot right away. What were the steps you took (in order) before you ran the RUU?
Sorry for all the questions, trying to establish a scenario.
[EDIT] Also, I see that you got the initial recovery from the CM11 ROM page. You didn't happen to flash a ROM that is meant for HBOOT 2.16 did you? I sure hope not. That could be a possibility as to why you can not boot anything.
42freelancer said:
Which recoveries did you try to flash? (TWRP, CWM)
Click to expand...
Click to collapse
I've tried both. fastboot flash recovery imgname would work fine, but I would again finish in bootloop after restart.
And which version?
Click to expand...
Click to collapse
TWRP_2.6.1.0_ville_4.2.2 and latest CWM
Have you tried to reroot the device and flash a recovery again since running the RUU?
Click to expand...
Click to collapse
You mean reunlock, not reroot, right? I've done reunlock so I could flash recovery.
From my experience with running an RUU, you should be able to boot right away. What were the steps you took (in order) before you ran the RUU?
Click to expand...
Click to collapse
I would run:
fastboot erase cache
fastboot reboot-bootloader
and then start RUU.
Sorry for all the questions, trying to establish a scenario.
Click to expand...
Click to collapse
You are welcome and thanks for the help.
[EDIT] Also, I see that you got the initial recovery from the CM11 ROM page. You didn't happen to flash a ROM that is meant for HBOOT 2.16 did you? I sure hope not. That could be a possibility as to why you can not boot anything.
Click to expand...
Click to collapse
No, 2.15 all the time...
velvel said:
I've tried both. fastboot flash recovery imgname would work fine, but I would again finish in bootloop after restart.
TWRP_2.6.1.0_ville_4.2.2 and latest CWM
You mean reunlock, not reroot, right? I've done reunlock so I could flash recovery.
I would run:
fastboot erase cache
fastboot reboot-bootloader
and then start RUU.
You are welcome and thanks for the help.
No, 2.15 all the time...
Click to expand...
Click to collapse
Try getting into bootloader and pushing the kernel this way: fastboot flash boot boot.img
you don't have to be in recovery for this. The phone is s-on right?
[edit] actually your security says it's off.
42freelancer said:
Try getting into bootloader and pushing the kernel this way: fastboot flash boot boot.img
you don't have to be in recovery for this.
Click to expand...
Click to collapse
No, it didn't work, this is something more serious
I've basically tried all I could think of, from doing RUUs (3 of them), flashing boot and recovery images, going 2.15, 2.16, locking/unlocking (obviously) and finally going S-On (ok, might be stupid, but I run out of ideas).
Bottom line is that all of the flashing worked for me, I get no error, but even simple fastboot boot recovery.img brings back the bootloop.
For example:
>fastboot flash recovery openrecovery-twrp-2.6.3.0-ville-selinux.img
sending 'recovery' (8668 KB)...
OKAY [ 1.108s]
writing 'recovery'...
OKAY [ 2.059s]
finished. total time: 3.173s
>fastboot reboot
and if I hold Vol- and select recovery in bootloader I am back to bootloop.
Same thing if I try:
>fastboot boot openrecovery-twrp-2.6.3.0-ville-selinux.img
I just do not understand why I am not getting any error message when flushing and is it possible that there is something wrong with the hardware that causes this behavior...
velvel said:
No, it didn't work, this is something more serious
I've basically tried all I could think of, from doing RUUs (3 of them), flashing boot and recovery images, going 2.15, 2.16, locking/unlocking (obviously) and finally going S-On (ok, might be stupid, but I run out of ideas).
Bottom line is that all of the flashing worked for me, I get no error, but even simple fastboot boot recovery.img brings back the bootloop.
For example:
>fastboot flash recovery openrecovery-twrp-2.6.3.0-ville-selinux.img
sending 'recovery' (8668 KB)...
OKAY [ 1.108s]
writing 'recovery'...
OKAY [ 2.059s]
finished. total time: 3.173s
>fastboot reboot
and if I hold Vol- and select recovery in bootloader I am back to bootloop.
Same thing if I try:
>fastboot boot openrecovery-twrp-2.6.3.0-ville-selinux.img
I just do not understand why I am not getting any error message when flushing and is it possible that there is something wrong with the hardware that causes this behavior...
Click to expand...
Click to collapse
Sounds like you have a soft brick on your hands.
Can you boot the device at all, stock or custom ROM?
Maybe reverting to COMPLETE STOCK and starting over fresh will help?
What was the last thing you did right before you got stuck?
42freelancer said:
Sounds like you have a soft brick on your hands.
Can you boot the device at all, stock or custom ROM?
Maybe reverting to COMPLETE STOCK and starting over fresh will help?
What was the last thing you did right before you got stuck?
Click to expand...
Click to collapse
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...
velvel said:
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...
Click to expand...
Click to collapse
And here we are. Do you happen to have the old All In One Kit that became obsolete, by hasoon2000? It has the function to flash your recovery back to stock. I found two mirrors on the internet, but because of the rules, I can't post them. But they are accessible through the internets if you use the right keywords.
42freelancer said:
And here we are. Do you happen to have the old All In One Kit that became obsolete? It has the function to flash your recovery back to stock. It's probably floating around the internet somewhere. If you don't I can try to find it.
Click to expand...
Click to collapse
Tried that too, no luck. Looks like I am getting a new paperweight
velvel said:
Tried that too, no luck. Looks like I am getting a new paperweight
Click to expand...
Click to collapse
If you haven't lost all hope, try reading through this and (Return to Stock - http://forum.xda-developers.com/showthread.php?t=2164783) see if you missed anything?
You seem pretty savvy in your HTC ONE S know-how. But it's always good to follow someone else's tutorial just for guidance.
Seems issue with Recovery, bootloop is normal
velvel said:
Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks
Click to expand...
Click to collapse
Hi,
Bootloop is normal for ROM geeks.
In your case, it seems your phone has issue with version of Recovery. I had this issue too and found correct Recovery @ http://techerrata.com/browse/twrp2/ville ....
You can give a try..:fingers-crossed::fingers-crossed::fingers-crossed:
velvel said:
Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks
Click to expand...
Click to collapse
Did you check the fast boot option in the powermenue under settings? If its check it will happen like ur problem.
velvel said:
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...
Click to expand...
Click to collapse
Have you tried this? :
--> flash STOCK recovery via fastboot or toolkit
--> Boot to bootloader --> Factory Reset(Userdata) / Clear Stotage (SD-card) (these commands only work with STOCK recovery)
Before I got the same problem, so in Bootloader I did Factory Reset and then flash the Recovery TWRP 2.6.3.0. Now it works
My power button quit working, I'm within the 1 year warranty period, and I need to go back to stock after I get my replacement.
Before I call VZW, since I'm rooted and using nV ROM, and I know they ask about the Software, does anyone have a screen shot of the Stock Software screen, Kit Kat unless LP has been pushed?
Thanks!
Sent from my HTC6525LVW using XDA Premium 4 mobile app
EvoNotion said:
My power button quit working, I'm within the 1 year warranty period, and I need to go back to stock after I get my replacement.
Before I call VZW, since I'm rooted and using nV ROM, and I know they ask about the Software, does anyone have a screen shot of the Stock Software screen, Kit Kat unless LP has been pushed?
Thanks!
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
They can see more information than you can tell them. Best bet is to be stock during that call.
Thanks for that input.
So, since the new phone arrived, I've been trying to restore my old phone to stock, S-OF, Unroot and Locked boot loader, etc.
I'm able to ADB into fastboot, however for whatever reason I cannot load the 06BIMG.zip(not at my computer)
Fastboot simply reboots immediately when I adb reboot boatloader.
Is there another way to get a stock image on the phone, remove the red text at boot up, s-off, lock boot loader with stock recovery and unroot?
Everything I've tried seems to be hinged on that fastboot rebooting issue.
Thanks
Sent from my HTC6525LVW using XDA Premium 4 mobile app
EvoNotion said:
Thanks for that input.
So, since the new phone arrived, I've been trying to restore my old phone to stock, S-OF, Unroot and Locked boot loader, etc.
I'm able to ADB into fastboot, however for whatever reason I cannot load the 06BIMG.zip(not at my computer)
Fastboot simply reboots immediately when I adb reboot boatloader.
Is there another way to get a stock image on the phone, remove the red text at boot up, s-off, lock boot loader with stock recovery and unroot?
Everything I've tried seems to be hinged on that fastboot rebooting issue.
Thanks
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
0P6BIMG.zip ?
I typed it from my phone whilst I was enjoying the evening outside. Just the only numbers in my head.
I'm downloading your RUU exe right now Dottat. Didn't realize you're local by an hour to me.
thanks!
dottat said:
0P6BIMG.zip ?
Click to expand...
Click to collapse
So I downloaded your EXE, and I get a failure in regard that it reboots to the HTC logo and the phone reboots immediately, causing the program to fail.
Error 155: unknown error
This is the same problem i was having when trying to do the fastboot push of the RUU I had downloaded previously.
Image version is 1.54.401.10
What ever can i do?
EvoNotion said:
So I downloaded your EXE, and I get a failure in regard that it reboots to the HTC logo and the phone reboots immediately, causing the program to fail.
This is the same problem i was having when trying to do the fastboot push of the RUU I had downloaded previously.
Image version is 1.54.401.10
What ever can i do?
Click to expand...
Click to collapse
Try flashing official stock vzw firmware via SD card. Are your mid and cid stock?
401 isn't vzw firmware BTW
dottat said:
0P6BIMG.zip ?
Click to expand...
Click to collapse
dottat said:
Try flashing official stock vzw firmware via SD card. Are your mid and cid stock?
401 isn't vzw firmware BTW
Click to expand...
Click to collapse
I just remember last year downloading and installing the nV Rom which was 4.4.2. and updating the radios.
I've tried the 0p6bimg.zip method in fastboot, but it fails as well. Maybe I'm doing it wrong, but it's in the root of the SD card.
EvoNotion said:
I just remember last year downloading and installing the nV Rom which was 4.4.2. and updating the radios.
I've tried the 0p6bimg.zip method in fastboot, but it fails as well. Maybe I'm doing it wrong, but it's in the root of the SD card.
Click to expand...
Click to collapse
I can do a team viewer session with you this weekend to take a look with you if you want
dottat said:
I can do a team viewer session with you this weekend to take a look with you if you want
Click to expand...
Click to collapse
That would be tits man. I'll be in Dover tomorrow night if you want to check it out live....LMK
EvoNotion said:
That would be tits man. I'll be in Dover tomorrow night if you want to check it out live....LMK
Click to expand...
Click to collapse
Depends on what time...lol. I work in Lancaster during the week a lot.
dottat said:
Depends on what time...lol. I work in Lancaster during the week a lot.
Click to expand...
Click to collapse
You tell me, I'll probably get out of work around 3pm and head down to York. I have to pick up tools from a friend that's borrowing them for work around 5/530, so whenever.
Since the PWR buttons not working, I'm not able to select HBOOT at the bootloader screen, and the commands I was using to get the HTC black screen fail to push. However, I just renamed your ZIP file and will try again and report back
EvoNotion said:
You tell me, I'll probably get out of work around 3pm and head down to York. I have to pick up tools from a friend that's borrowing them for work around 5/530, so whenever.
Since the PWR buttons not working, I'm not able to select HBOOT at the bootloader screen, and the commands I was using to get the HTC black screen fail to push. However, I just renamed your ZIP file and will try again and report back
Click to expand...
Click to collapse
BTW...from a booted ROM the command adb reboot oem-78
Will land you in ruu mode.
dottat said:
BTW...from a booted ROM the command adb reboot oem-78
Will land you in ruu mode.
Click to expand...
Click to collapse
well now, learn something new everyday. Got me to the HTC screen, and then it rebooted though.
EvoNotion said:
well now, learn something new everyday. Got me to the HTC screen, and then it rebooted though.
Click to expand...
Click to collapse
Can you adb reboot-bootloader and get a fastboot getvar all.
X out your imei and sn
dottat said:
Can you adb reboot-bootloader and get a fastboot getvar all.
X out your imei and sn
Click to expand...
Click to collapse
C:\Users\Abraham\Documents>adb kill-server
C:\Users\Abraham\Documents>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Abraham\Documents>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.027s]
finished. total time: 0.037s
C:\Users\Abraham\Documents>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1726320 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 8.723s
C:\Users\Abraham\Documents>adb reboot bootloader
C:\Users\Abraham\Documents>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXX
(bootloader) imei: XXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 99000429333087
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.141s
C:\Users\Abraham\Documents>
EvoNotion said:
C:\Users\Abraham\Documents>adb kill-server
C:\Users\Abraham\Documents>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Abraham\Documents>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.027s]
finished. total time: 0.037s
C:\Users\Abraham\Documents>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1726320 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 8.723s
C:\Users\Abraham\Documents>adb reboot bootloader
C:\Users\Abraham\Documents>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXX
(bootloader) imei: XXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 99000429333087
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.141s
C:\Users\Abraham\Documents>
Click to expand...
Click to collapse
Try flashing this zip the same exact way...
https://www.androidfilehost.com/?fid=95916177934537898
dottat said:
Try flashing this zip the same exact way...
https://www.androidfilehost.com/?fid=95916177934537898
Click to expand...
Click to collapse
Should I rename it to something?
EvoNotion said:
Should I rename it to something?
Click to expand...
Click to collapse
Should not need to
dottat said:
Try flashing this zip the same exact way...
https://www.androidfilehost.com/?fid=95916177934537898
Click to expand...
Click to collapse
Got half way through and now I'm at the four exclamation marks on the corners
I only just upgraded to Oreo a few weeks ago - mostly delayed by my CID / dual SIM model causing me to not receiving the OTA for ages. I just noticed today that TWRP no longer works. All that happens is the screen turns black, still backlit, and oddly enough, fastboot devices still lists it.
I use fastboot boot <twrp.img> so I can keep the stock recovery installed. I'm hesitant to try flashing TWRP as I don't have a backup of the current recovery, and can't see how to make one. I suppose to restore it, I could track down a link for the OTA I applied to extract it from, but I doubt flashing TWRP would help anyway.
I've tried all the versions available from the TWRP website:
Code:
twrp-3.1.1-1-ocn.img
twrp-3.2.1-0-ocn.img
twrp-3.2.1-1-ocn.img
twrp-3.2.1-2-ocn.img
Here's my output of
Code:
fastboot getvar all
:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_ocndugl
(bootloader) version: 1.0
(bootloader) max-download-size: 2399200000
(bootloader) serialno: FA78H1800284
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 356133083656859
(bootloader) version-main: 2.42.400.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1712011153
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC30000
(bootloader) cid: HTC__060
all:
finished. total time: 0.004s
Could it be to do with some partition structure change that could be part of my model's Oreo update that TWRP has yet to reflect? I don't know what else could cause this.
Does TWRP place a log file somewhere?
Is it even getting into the TWRP boot process at all? The fact it's still listed in fastboot devices is intriguing.
I've been rooting for several years, and as a developer and avid Arch Linux user, I tend to be able to sort out most issues myself, and so only have the need to post very rarely. I've tried hard to find information on this issue, but I'm completely stumped and would very much appreciate some help. Cheers!
Edit: I thought I should probably try flashing it just in case - lo and behold, it worked! Though I'm still quite curious as to why booting directly could have stopped working.
Twrp versions are now related to the android versions, at least for htc. I think I remember reading something to do with the encryption and how twrp interacts with the os..
Newest os = newest twrp. Once you have the device running don't change/upgrade twrp. It is meant to be safe but i dont trust it.
I do recall seeing something to do with encryption, actually. Surely they're aiming for backwards compatibility though. And I'd like to think it'd show a message if it's not working.
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