Hello,
I'm new to XDA and I really need help in fixing by hard bricked ZTE Q505T (4g) device. I just got this phone like last month and I successfully rooted it, and then i edited something in the build.prop which began my problem. Whenever i boot the phone, logo shows but then the screen starts flashing white and black and vibrates on key press. At then I could boot into my recovery, which I figured out that my device was soft bricked. Allelujah!!! at then, i boot into recovery, downloaded my stock rom which was in a .zip format, copied it to my SD card, tried to "install update from SD card" option (I don't have a custom recovery since my device was too rare), got "E: signature validation error, installation aborted" error, I tried using the "apply update from ADB" option as well and the adb sideload program on my PC, got same error on my phone. Since my device was a qualcomm device, I googled "How to unbrick a qualcomm device" and came across a site where it said (among its steps to follow) to use miniTool partition to format my device's partition, and I did, and that began the second phase of my problem , cos I later got to realize i just deleted my recovery image as well and the other step to follow to restore it with QFIL was to have my firmware image not a .zip type and that was the only one I could online, a firmware.zip that Just contained the boot.img, META.INF folder and system folder, no recovery.img
and the other stuffs needed. I tried my luck if I could use the extracted .zip for flashing back to my stock rom, but got a Sahara Failed/Error report. Right now I'm stuck :crying: don't know what to do, except if someone here could help me to get a backup firmware image with all its needed files for my phone let me try again. My device has an inbuilt battery but thank goodness it is a qualcomm HS-USB QDLoader 9008 driver. Right now the device can't boot up or show any logo or even charge or show the LED, but my system recognizes it as a qualcomm HS-USB QDLoader 9008 whenever i plug it in, that gave me alot of hope, I know i messed big time, Please just help me :crying::angel: !!!!!
Hello, I have the same phone, and I have the same problem as you, I have not been able to solve my case, do you know any solution?
No, not YET:crying:
RyanRaphael said:
Hello,
I'm new to XDA and I really need help in fixing by hard bricked ZTE Q505T (4g) device. I just got this phone like last month and I successfully rooted it, and then i edited something in the build.prop which began my problem. Whenever i boot the phone, logo shows but then the screen starts flashing white and black and vibrates on key press. At then I could boot into my recovery, which I figured out that my device was soft bricked. Allelujah!!! at then, i boot into recovery, downloaded my stock rom which was in a .zip format, copied it to my SD card, tried to "install update from SD card" option (I don't have a custom recovery since my device was too rare), got "E: signature validation error, installation aborted" error, I tried using the "apply update from ADB" option as well and the adb sideload program on my PC, got same error on my phone. Since my device was a qualcomm device, I googled "How to unbrick a qualcomm device" and came across a site where it said (among its steps to follow) to use miniTool partition to format my device's partition, and I did, and that began the second phase of my problem , cos I later got to realize i just deleted my recovery image as well and the other step to follow to restore it with QFIL was to have my firmware image not a .zip type and that was the only one I could online, a firmware.zip that Just contained the boot.img, META.INF folder and system folder, no recovery.img
and the other stuffs needed. I tried my luck if I could use the extracted .zip for flashing back to my stock rom, but got a Sahara Failed/Error report. Right now I'm stuck :crying: don't know what to do, except if someone here could help me to get a backup firmware image with all its needed files for my phone let me try again. My device has an inbuilt battery but thank goodness it is a qualcomm HS-USB QDLoader 9008 driver. Right now the device can't boot up or show any logo or even charge or show the LED, but my system recognizes it as a qualcomm HS-USB QDLoader 9008 whenever i plug it in, that gave me alot of hope, I know i messed big time, Please just help me :crying::angel: !!!!!
Click to expand...
Click to collapse
Try a Google search for:
"Unbrick qhsusb qdloader 9008"
You'll find many different guides for fixing this, try them all, just make sure that the tools and files you use are for your specific model number.
tygans77 said:
Hello, I have the same phone, and I have the same problem as you, I have not been able to solve my case, do you know any solution?
Click to expand...
Click to collapse
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
zteQ505T
RyanRaphael said:
No, not YET:crying:
Click to expand...
Click to collapse
My problem is with partition tables I can not install any ROM with recovery, I use twrp, but I do not know how I can repair the partitions.
tygans77 said:
My problem is with partition tables I can not install any ROM with recovery, I use twrp, but I do not know how I can repair the partitions.
Click to expand...
Click to collapse
Do you have the stock firmware for your device?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Do you have the stock firmware for your device?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
If I have the original stock firmware for my device, the bad thing I can not install,
tygans77 said:
If I have the original stock firmware for my device, the bad thing I can not install,
Click to expand...
Click to collapse
Do you have a PC with adb/fastboot installed and set up correctly?
Can you boot to TWRP and successfully connect to adb?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I don't even have a recovery installed at all on my device cos I deleted my device's partition, The stock firmware I have is a .zip format, with only a META.INF, System Folder and a Boot.img file in it and a ".sh" file extension etc. I don't know where to get a "Stock firmware" for my device with a boot.img, cache.img, recovery.img, .mbn and .xml files etc.
RyanRaphael said:
I don't even have a recovery installed at all on my device cos I deleted my device's partition, The stock firmware I have is a .zip format, with only a META.INF, System Folder and a Boot.img file in it and a ".sh" file extension etc. I don't know where to get a "Stock firmware" for my device with a boot.img, cache.img, recovery.img, .mbn and .xml files etc.
Click to expand...
Click to collapse
The file you have is not the stock firmware, it's a copy of your stock ROM that has been converted into a flashable.zip that is designed to be flashed in custom recovery(TWRP). Or its a stock update that only contains a bootloader update and a system update.
It isn't a copy of what you need.
If you can get into fastboot mode then you can flash TWRP then use TWRP to flash the stock.zip that you have.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
RyanRaphael said:
I don't even have a recovery installed at all on my device cos I deleted my device's partition, The stock firmware I have is a .zip format, with only a META.INF, System Folder and a Boot.img file in it and a ".sh" file extension etc. I don't know where to get a "Stock firmware" for my device with a boot.img, cache.img, recovery.img, .mbn and .xml files etc.
Click to expand...
Click to collapse
Well, the only help I can offer you since I can only get there, this is the TWRP recovery link http://pan.baidu.com/s/1c0BGANQ
After downloading, you should install it using Fastboot by running this command "fastboot -i 0x19d2 boot twrp-2.8.7.0-q505t.img"
---------- Post added at 01:53 PM ---------- Previous post was at 01:37 PM ----------
Droidriven said:
Do you have a PC with adb/fastboot installed and set up correctly?
Can you boot to TWRP and successfully connect to adb?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
If I have TWRP on my device I can connect adb and fastboot correctly, but I could not install the ROM via Zip or fastboot or adb since I have problems with the partitions
tygans77 said:
Well, the only help I can offer you since I can only get there, this is the TWRP recovery link http://pan.baidu.com/s/1c0BGANQ
After downloading, you should install it using Fastboot by running this command "fastboot -i 0x19d2 boot twrp-2.8.7.0-q505t.img"
---------- Post added at 01:53 PM ---------- Previous post was at 01:37 PM ----------
If I have TWRP on my device I can connect adb and fastboot correctly, but I could not install the ROM via Zip or fastboot or adb since I have problems with the partitions
Click to expand...
Click to collapse
Find the full stock firmware. Then extract the firmware until you get to the individual .img files inside the firmware (boot, system, recovery, etc...)
Then use fastboot to flash each .img by itself.
Or
Use adb shell and dd commands to dd the individual .img files to their correct partitions. If you don't understand how to use dd commands then this method is too dangerous for you, if you don't get the dd commands exactly right then you'll only damage your device worse and then you won't be able to fix it at all.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
---------- Post added at 09:15 AM ---------- Previous post was at 09:06 AM ----------
RyanRaphael said:
I don't even have a recovery installed at all on my device cos I deleted my device's partition, The stock firmware I have is a .zip format, with only a META.INF, System Folder and a Boot.img file in it and a ".sh" file extension etc. I don't know where to get a "Stock firmware" for my device with a boot.img, cache.img, recovery.img, .mbn and .xml files etc.
Click to expand...
Click to collapse
You need the full stock firmware and you need to do the Google search I suggested:
"Unbrick qhsusb dloader 9008"
Those search terms will show you many different guides for solving your issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
pls Tygans can u send me d firmware u have??
UPDATE!!!
Now I was able to get the firmware, but each time I try using other qualcomm flashing tools (except QFIL as i keep getting Sahara Error report), my device just can't be detected for some reason I'm not aware of, anytime I try, either I get stuck at the "Waiting for Device" or a "Can't detect device" error, what can I do please, ANY HELP is greatly appreciated
RyanRaphael said:
UPDATE!!!
Now I was able to get the firmware, but each time I try using other qualcomm flashing tools (except QFIL as i keep getting Sahara Error report), my device just can't be detected for some reason I'm not aware of, anytime I try, either I get stuck at the "Waiting for Device" or a "Can't detect device" error, what can I do please, ANY HELP is greatly appreciated
Click to expand...
Click to collapse
I have been looking for the name of the sahara.xml application that I could not get, we were there, you do not have cell phone backup?
tygans77 said:
I have been looking for the name of the sahara.xml application that I could not get, we were there, you do not have cell phone backup?
Click to expand...
Click to collapse
Yes, Can you give me the format of your firmware? like the order of files and folders, just trying to be sure of what i downloaded....
Cos I have an error with ZTE Tool Studio-eMMC Download Tool, says missing tpsfw0109.mbn stuff....
THANKS IN ADVANCE...
Related
Q&A for **TWRP** custom recovery for IDOL3 6045
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for **TWRP** custom recovery for IDOL3 6045. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
stuck on twrp bootloop
stuck on twrp boot loop. any suggestions? i followed instructions as posted, but when rebooted into twrp and tried to reboot system, i keep going back to twrp. thanks
Heyy
I have the same problem,, although i did a backup and then a deleted everything cause it was looping,,, how do i fix everything to the original condition,, i won't be doing this again,, my model is an i version.. Although mine is not booting into twrp ,, just the original..
Restoring my backup does not work
I tryed everything,, i know not to do this anymore I think it's broke forever.
If you can get into twrp it can most likely be fixed.
Download the system image and try to install it. May need to put it on sdcard or USB otg.
This is all Alcatel's fault for not releasing anything when we kindly asked...
Where is the system image?
neilownz said:
If you can get into twrp it can most likely be fixed.
Download the system image and try to install it. May need to put it on sdcard or USB otg.
This is all Alcatel's fault for not releasing anything when we kindly asked...
Click to expand...
Click to collapse
---------- Post added at 12:30 AM ---------- Previous post was at 12:20 AM ----------
im in tears (
I believe there's a link in the thread about ota updates after rooting.
http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
---------- Post added at 02:43 AM ---------- Previous post was at 01:43 AM ----------
TrevBlu19 said:
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
Click to expand...
Click to collapse
Trying to make the other guys restore show up.... with my other phone and swapping.. trying to change timestamps...
TrevBlu19 said:
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
---------- Post added at 02:43 AM ---------- Previous post was at 01:43 AM ----------
Trying to make the other guys restore show up.... with my other phone and swapping.. trying to change timestamps...
Click to expand...
Click to collapse
Tell us which backup you used and exactly what the path is to where you put it on the phone. Is it in TWRP/BACKUPS? If so, give us the rest of the path. If TWRP's Restore menu is not showing the backup you put on the phone, it's probably (assuming it's there and in the right place) because the folder name that starts with "4" isn't the right one or because it's in the wrong place. If you haven't already done this, from TWRP, make a system image backup. You probably won't use it, but it'll create the directory in which you can put the backup from XDA. It'll have a name that your installation of TWRP can recognize. Then, you can put that unrecognized backup there and it should be seen.
I can't even get into TWRP mode now it reboots too fast now..
maigre said:
Tell us which backup you used and exactly what the path is to where you put it on the phone. Is it in TWRP/BACKUPS? If so, give us the rest of the path. If TWRP's Restore menu is not showing the backup you put on the phone, it's probably (assuming it's there and in the right place) because the folder name that starts with "4" isn't the right one or because it's in the wrong place. If you haven't already done this, from TWRP, make a system image backup. You probably won't use it, but it'll create the directory in which you can put the backup from XDA. It'll have a name that your installation of TWRP can recognize. Then, you can put that unrecognized backup there and it should be seen.
Click to expand...
Click to collapse
You mean it's looping every few seconds? What happens, exactly? Do you get the black logo screen briefly, then it all goes black and comes back again?
Maybe it's worth copying a command like
Code:
adb reboot-bootloader
or, maybe better,
Code:
fastboot reboot bootloader
so that you have it in your clipboard. Then, keep entering them into the command line. You're bound to time it right at some point, at least if it can possibly be done in the state your device is in. You might have to do:
Code:
fastboot -i 0x1bbb reboot-bootloader
If you can get into the bootloader, you should be able to get booted into TWRP from there. Keep in mind that when you do get booted into the bootloader, it won't look like anything distinct. It's just that same black logo screen you see every time you boot up (or loop, probably).
I soft-bricked my 6045i after editing the build.prop and didn't have a backup like a fool. I cannot get the phone to boot at all, stuck on the Alcatel Onetouch boot logo and can't go any further. I have tried to create an update.zip to be able to flash the build.prop thru stock recovery but so far no luck. Each time it would give me an error saying invalid footer, I tried editing the updater-script to match the device but still the error remains and I cannot sideload the update.zip.
Would it be possible for someone to upload a signed update.zip for the 6045i model with only the build.prop for use with adb sideload in stock recovery?
datkevjames said:
I soft-bricked my 6045i after editing the build.prop and didn't have a backup like a fool. I cannot get the phone to boot at all, stuck on the Alcatel Onetouch boot logo and can't go any further. I have tried to create an update.zip to be able to flash the build.prop thru stock recovery but so far no luck. Each time it would give me an error saying invalid footer, I tried editing the updater-script to match the device but still the error remains and I cannot sideload the update.zip.
Would it be possible for someone to upload a signed update.zip for the 6045i model with only the build.prop for use with adb sideload in stock recovery?
Click to expand...
Click to collapse
Flash a stock system rom image from here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745/
Important points: A corrupted build.prop should still mean you have adb access to your phone even though it won't finish booting...you can do an "adb reboot bootloader" then fastboot boot twrp and flash one of the stock recoveries.
How do I know this so well? I soft bricked mine for a day by editing the build.prop before TWRP was available.
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
maigre said:
You mean it's looping every few seconds? What happens, exactly? Do you get the black logo screen briefly, then it all goes black and comes back again?
Maybe it's worth copying a command like
Code:
adb reboot-bootloader
or, maybe better,
Code:
fastboot reboot bootloader
so that you have it in your clipboard. Then, keep entering them into the command line. You're bound to time it right at some point, at least if it can possibly be done in the state your device is in. You might have to do:
Code:
fastboot -i 0x1bbb reboot-bootloader
If you can get into the bootloader, you should be able to get booted into TWRP from there. Keep in mind that when you do get booted into the bootloader, it won't look like anything distinct. It's just that same black logo screen you see every time you boot up (or loop, probably).
Click to expand...
Click to collapse
If you can execute fastboot commands, your already in bootloader.
famewolf said:
Flash a stock system rom image from here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745/
Important points: A corrupted build.prop should still mean you have adb access to your phone even though it won't finish booting...you can do an "adb reboot bootloader" then fastboot boot twrp and flash one of the stock recoveries.
How do I know this so well? I soft bricked mine for a day by editing the build.prop before TWRP was available.
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
If you can execute fastboot commands, your already in bootloader.
Click to expand...
Click to collapse
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
I either need to flash an update.zip with build.prop or somehow flash an entire image uploaded to the other thread which I'm well aware of.
PS: I've tried all different sorts of adb/fastboot executables as well as multiple adb drivers (Samsung, Motorola, Google etc) even the Alcatel ones provided with their Mobile Upgrade Q app which install more of the phone than any other drivers, I've noticed.
PPS: A handful of times I was able to get a tiny bit further in stock recovery adb sideload mode, of course it was an error: 'you must use adb 1.0.32 to be able to sideload' blah blah and I made sure I was using that version.
PPPS: Is there a 3rd party app I can use to flash the image like odin or rsd lite? I cannot for the life of me get to fastboot to flash the image. Adb devices detects the phone but beyond this I can't do squat.
PPPPS: Phone is rooted and bootloader unlocked. USB debugging enabled iirc although this may be the reason for all the 'error: closed' issues.
Please someone upload a signed flashable zip with build.prop in it for 6045i (USA) model. I love this phone more than my Moto X 2014 (XT1097), that's saying something considering the Moto has more power and smoothness to it.
twrp bootloop
im able to boot into bootloader and also able to get into twrp, but cant fully reboot. i have 6045i and if anybody has any solution to this, i would greatly appreciate it.
datkevjames said:
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
I either need to flash an update.zip with build.prop or somehow flash an entire image uploaded to the other thread which I'm well aware of.
PS: I've tried all different sorts of adb/fastboot executables as well as multiple adb drivers (Samsung, Motorola, Google etc) even the Alcatel ones provided with their Mobile Upgrade Q app which install more of the phone than any other drivers, I've noticed.
PPS: A handful of times I was able to get a tiny bit further in stock recovery adb sideload mode, of course it was an error: 'you must use adb 1.0.32 to be able to sideload' blah blah and I made sure I was using that version.
PPPS: Is there a 3rd party app I can use to flash the image like odin or rsd lite? I cannot for the life of me get to fastboot to flash the image. Adb devices detects the phone but beyond this I can't do squat.
PPPPS: Phone is rooted and bootloader unlocked. USB debugging enabled iirc although this may be the reason for all the 'error: closed' issues.
Please someone upload a signed flashable zip with build.prop in it for 6045i (USA) model. I love this phone more than my Moto X 2014 (XT1097), that's saying something considering the Moto has more power and smoothness to it.
Click to expand...
Click to collapse
There are no install-script and install-binary example files to use to build a signed update.zip because there are no rom's available....maybe someone could build something using the spanish rom just posted but I don't read spanish and they seem to have built it for a 6045Y which isn't gonna help 6045i or 6045K users. If you were running twrp it wouldn't be an issue as twrp allows adb access....stock recovery doesn't..it also doesn't support rebooting to bootloader....if your bootup was "freezing" as a normal build.prop issue would then you should STILL be able to do an "adb reboot bootloader" or an "adb shell" and look around.
datkevjames said:
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
.
Click to expand...
Click to collapse
Try this:
-turn off your phone
-run command line in direcotry where is fastboot and adb.exe
-connect phone to the pc and turn the phone on
-when the phone is booting you will hear a sound that new device is detected from your pc
-in this point type "adb reboo bootloader"
-the phone should reboot to initial screen and stays there
-now you are in bootloader mode and you can flash twrp recovery
-in twrp recovery you can run file manager and copy and delete files, so you can replace the bad build.prop with your backup (you surely have)
---------- Post added at 10:58 AM ---------- Previous post was at 10:50 AM ----------
faresbreech said:
im able to boot into bootloader and also able to get into twrp, but cant fully reboot. i have 6045i and if anybody has any solution to this, i would greatly appreciate it.
Click to expand...
Click to collapse
if you have a problem then:
1- you have to tell what did you do before it happen.
anyway if you can go to TWRP, you can download system Image backup from @famewolf thread HERE, copy it to your sd card and then proceed with restore menu from TWRP. And just check the "system" .
First I rooted phone, then verified through root checker that I was truly rooted. After that I proceeded to flash twrp. Once twrp was flashed, I went to recovery to make a full backup. There I first chose read only and then backed up, but realized that I was limited on performing different actions so I reflashed twrp and this time I chose for twrp to fully work and again preformed another backup. It was when I rebooted system after the second backup when I started looping back to twrp.
I was wondering if maybe there is a terminal command I can execute through twrp to fix this like the LG G2 has. I had a problem like this before on my G2 but after executing the terminal command it would get fixed. Thanks
Sent from my Z987 using XDA Free mobile app
DallasCZ said:
Try this:
-turn off your phone
-run command line in direcotry where is fastboot and adb.exe
-connect phone to the pc and turn the phone on
-when the phone is booting you will hear a sound that new device is detected from your pc
-in this point type "adb reboo bootloader"
-the phone should reboot to initial screen and stays there
-now you are in bootloader mode and you can flash twrp recovery
-in twrp recovery you can run file manager and copy and delete files, so you can replace the bad build.prop with your backup (you surely have)
Click to expand...
Click to collapse
I tried spamming 'adb reboot-bootloader' as fast as possible, but apparently I didn't authorize my computer. ADB gives me this: error: device unauthorized. Please check the confirmation dialog on your device. ffs. Now what? I do appreciate all help. I am savvy enough to try to solve this on my own but any helpful advice would be awesome.
Hi everyone. First of all, excuse me for my not well English. Today I've tried to reset my Motorola Moto G XT1032: it's a GPE converted by me some months ago. I've not succeded to reset it using Android settings. So, I've tried using the flashboot menu (Volume down + power, Recovery, Volume up + power, delete all), but all data has remained on the phone.
So I tried to re-flash GPE firmware, as I did some months ago, but after the process the phone does not boot and stucks on Google boot logo with an the opened lock. I've tried many guides but I've not succeded to repair. Please, help me! Thanks.
P.S. I'm using Linux for fastboot and other tools.
I'm trying again by re-flashing. Now I'm seeing that there is an error on flashing partition.gpt. Why?
u can change a rom
Hi !
I have the same problem, beside all that my phone is in bootloop i cannot install any custom recovery, what ever custom recovery i flash i get hab check failed or partition mismatch and then i end up with the stuck recovery (i know i should not reboot right after the flash and i go to recovery mode but the moment i boot up i see the old recovery)
I am not sure what is wrong but i guess there should be something wrong with my partitions. the only rom that gets flashed with no errors (but still gets stuck in the bootloop) is XT1032_FALCON_RETFR_5.1_LPB23.13-56_cid7_CFC
I managed to see my files via the command fastboot boot recovery recovery.img but then i only have read access, If only i had write access i could upload some files to my phone and get it working with updating from SD card .
any help is appreciated
Have you guys tried flashing stock firmware image (not flashable zip)? Take a look at http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795 and at the guide in the OP on how to flash it.
Enviado de meu SM-G900M usando Tapatalk
alexandrino said:
Have you guys tried flashing stock firmware image (not flashable zip)? Take a look at http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795 and at the guide in the OP on how to flash it.
Enviado de meu SM-G900M usando Tapatalk
Click to expand...
Click to collapse
Thank you for your reply. Is nt that exactly what i did ? i mean i looked at the files . there ate generally two types of files. some are XML which i need to use fast boot. the other one is a zip file with several folders in it which i dont know how to flash. do you mean there is my answer?
Inside the factory firmware file you should find several files (.img,. bin, etc.) inside the zip which you should flash following this guide: http://forum.xda-developers.com/showthread.php?t=2542219. Just remember to not downgrade (or just flash a Lollipop image)
alexandrino said:
Inside the factory firmware file you should find several files (.img,. bin, etc.) inside the zip which you should flash following this guide: http://forum.xda-developers.com/showthread.php?t=2542219. Just remember to not downgrade (or just flash a Lollipop image)
Click to expand...
Click to collapse
I have followed the guide but maybe here is actually my problem
there are two kinds of ROMS to my knowledge. one has several files in it boot.img recovery.img chucnks etc... and there are no folders in the ROM file it is usually called XML
second type is a zip file like this one http://forum.xda-developers.com/devdb/project/dl/?id=14940 if you exract it there is a file named boot.img and two folders META-INF and System.
in the system there are numerous files but there is nothing to flash. the only way i know is flashing via fastboot. i dont know how flash these zip files.
one more point is that i dont have a custom recovery ( and i cannot install one since it does not show up after each reboot for an unknown reason)
from what i read people upload these second type zip files to their phone and then install it with their custom recovery software, but i dont have that luxury!
I have just noticed that we have been discussing your problem in two different threads (I thought they were from different people).
So you have already tried using fastboot to flash all those bin and img files and it still does not work? What error are you getting while trying to perform those commands?
alexandrino said:
I have just noticed that we have been discussing your problem in two different threads (I thought they were from different people).
So you have already tried using fastboot to flash all those bin and img files and it still does not work? What error are you getting while trying to perform those commands?
Click to expand...
Click to collapse
yes i guess. we can continue here, and thanks.
For anyfirmware i get hab check failed and partition mismatched errors
for recoveries i get mismatched partition error
they said you should ignore them but i am not sure if i should!
the only firmware which flashes flawlessly is XT1032_FALCON_RETFR_5.1_LPB23.13-56_cid7_CFC.xml by works i mean it just does not come up with any errors and it flashes but still the bootloader loops.
by the way, is there anyway i could upload some images to the device ? i cannot side load adb cause it comes with verification error in the middle of upload for anything i tried.
Thank you everyone for the replies. Some months ago I converted my Moto G to GPE as reported in this guide. When I tried to do it again (with the purpose of resetting the device) I got the issue descripted in my first post. But I was doing the all procedure using Ubuntu: I opened the batch file, written in Windows Batch Language, and I executed all the commands through the bash. Maybe, that's the thing that has made the phone not starting anymore. In my last try I've followed the procedure using Windows and now everything is ok.
Update/Solved:
Currently the only way for people who deleted their OS completely in this phone model X00HD/ZC520KL is to restore the official firmware.
You can ask for a backup recovery folder in XDA Forums ( https://forum.xda-developers.com/zen...help?nocache=1) if you do not have made a backup with people who have the same phone model. You must have TWRP previously installed and bootloader unlocked. Flashing the official firmware via .zip files is not working with twrp, you must restore the folder. After having the files needed, your recovery folder will not appear on the RESTORE section so follow this simple tutorial to make it appear there (https://youtu.be/trlG3ZxwQxI)
This method will bring your phone back to life if you're stuck in TWRP Recovery Mode with "No OS installed". This method is working and it's the only way for you to use your phone again until developers create custom ROM's for this model.
DEVICE INFO:
ASUS ZENFONE 4 MAX ZC520KL [X00HD]
Please, can anyone reply? I need an answer. Thanks for your time.
https://forum.xda-developers.com/zenfone-4-max/how-to/zenfone-4-max-rom-twrp-flash-twrp-t3776287
jenere said:
https://forum.xda-developers.com/zenfone-4-max/how-to/zenfone-4-max-rom-twrp-flash-twrp-t3776287
Click to expand...
Click to collapse
This ROM is for is for the Asus model of ZenFone 4 Max ZC554KL [X00ID]. My device is the same but the model is ZenFone 4 Max ZC520KL [X00HD]. Will it work also on my device? :fingers-crossed:
jenere said:
https://forum.xda-developers.com/zenfone-4-max/how-to/zenfone-4-max-rom-twrp-flash-twrp-t3776287
Click to expand...
Click to collapse
Hello, I tried your solution. It did not work. I keep getting Error Number 7 when flashing the ROM. Plus I also tried to delete the assert line in the uptader-script of the ROM you gave me the link after learning from a tutorial how to solve Error Number 7 and after that I got another error: Invalid Zip Format. I don't know what do to more, is this ROM link really compatible with my device? I need urgent help.
ANDROIDMASTER67 said:
Hello, I tried your solution. It did not work. I keep getting Error Number 7 when flashing the ROM. Plus I also tried to delete the assert line in the uptader-script of the ROM you gave me the link after learning from a tutorial how to solve Error Number 7 and after that I got another error: Invalid Zip Format. I don't know what do to more, is this ROM link really compatible with my device? I need urgent help.
Click to expand...
Click to collapse
did you try the stock firmware in the official site for asus? i think installing the the official stock firmware will solve your problem just chose there the proper firmware for.. can i ask if already unlock your bootloader or already change you stock twrp?
jenere said:
did you try the stock firmware in the official site for asus? i think installing the the official stock firmware will solve your problem just chose there the proper firmware for.. can i ask if already unlock your bootloader or already change you stock twrp?
Click to expand...
Click to collapse
Thanks for the attention. I already tried tons of ROM's including the official one for this phone. I keep getting Error Number 7. Sometimes when I force an installation editing the uptader-script file it seems everything is working fine, but at the end of the ROM flash process the phone reboots and goes back to TWRP like everything had never happened. I have never seen a successful feedback, just the "Failed" message or a unexpected reboot that goes back to TWRP.
I don't know what do you mean with unlocking bootloader as I have no ROM installed and always I turn ON my phone I go to TWRP automatically. My TWRP version is 3.1.1.
ANDROIDMASTER67 said:
Hello, I tried your solution. It did not work. I keep getting Error Number 7 when flashing the ROM. Plus I also tried to delete the assert line in the uptader-script of the ROM you gave me the link after learning from a tutorial how to solve Error Number 7 and after that I got another error: Invalid Zip Format. I don't know what do to more, is this ROM link really compatible with my device? I need urgent help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2302599 did you try this?
---------- Post added at 01:50 AM ---------- Previous post was at 01:45 AM ----------
there's alot of tutorial video in google and youtube showing how to fix error code 7 when flashing rom
jenere said:
https://forum.xda-developers.com/showthread.php?t=2302599 did you try this?
---------- Post added at 01:50 AM ---------- Previous post was at 01:45 AM ----------
there's alot of tutorial video in google and youtube showing how to fix error code 7 when flashing rom
Click to expand...
Click to collapse
Not working, as I said before, I've already tried to solve this Error. Either 3 things happen: the installation seems to be running good but at some point the device automatically reboots to it's original condition of TWRP (Liniage OS flash and after editing the file to solve Error Number 7 + I get a message saying "Invalid zip format" (Official Asus Firmware flash after editing the file to solve Error Number 7) + I get Error Number 7.
Backup ROM
Hi, I have the same model and I have TWRP as well. I think I can make backup of my ROM an upload it so you can install it on your phone, would that work for you?
pantarz said:
Hi, I have the same model and I have TWRP as well. I think I can make backup of my ROM an upload it so you can install it on your phone, would that work for you?
Click to expand...
Click to collapse
Hello @pantarz, yes, give me your backup ROM you have in your phone, it should work on mine. I'm really thankful to see people like this these days. Just need the .zip file for the ROM. Thanks in advance.
Currently the only way for people who deleted their OS completely in this phone model X00HD/ZC520KL is to restore the official firmware.
You can ask for a backup recovery folder in XDA Forums ( https://forum.xda-developers.com/zenfone-4-max/help?nocache=1) if you do not have made a backup. You must have TWRP previously installed and bootloader unlocked. Flashing the official firmware via .zip files is not working with twrp, you must restore the folder. Your recovery folder will not appear on the RESTORE section so follow this simple tutorial to make it appear there (https://youtu.be/trlG3ZxwQxI)
This method will bring your phone back to live if you're stuck in TWRP Recovery Mode with "No OS installed". This method is working and it's the only way for you to use your phone again until developers create custom ROM's for this model.
Hi @ANDROIDMASTER67, @pantarz I also break my phone ZC520KL ( X00HD ). It shows "no os installed" and "error 7" when I try to install a ROM.
Can you please help me fix my phone? If there is a backup that I can get please let me know.
Many thanks in advance.
I've managed to fix it by doing the following:
Copy the original recovery from a firmware package.
I could find one in the file https://androidfilehost.com/?fid=11050483647474829889, location /Asus_Zenfone_4_Max_ZC520KL_20171225/Firmware/recovery.img
Load default recovery
fastboot flash recovery recovery/original-recovery.img
Restart to bootloader
fastboot reboot bootloader
Load flashboot mode
choose the option "update using adb"
ensure that adb can locate devices with
adb devices
load firmware with
adb sideload UL-ASUS_X00HD-WW-14.2016.1805.374-user.zip ( try download from: https://www.beritahuaja.com/2018/11/download-stock-rom-asus-zenfone-4-max-zc520kl.html )
Easy way with only fastboot
1. Get adb and fastboot drivers
2. go to this page h ttps://addrom.com/raw-rom-for-asus-zenfone-4-max-zc520kl/ Dowload the original firware
3. Extract the files inside the your disc C:Adb
4. Go to your celphone and enter in fastboot mode... then conect the celphone to your computer ... then use cmd " fastboot flash recovery recovery.img" .. this is for restore the original recovery if you have twrp.. if you dont have it , its no neccesary ..
5. in fastboot mode , go to Inside the firware search flashall_AFT.bat , double clik , wait until finish
6. go to recovery mode wipe/factory reset and tadaaaa! Your Os is restore again :bueno:
asus-zenfone-4-max-zc520kl
Luisanchez70 said:
1. Get adb and fastboot drivers
2. go to this page h ttps://addrom.com/raw-rom-for-asus-zenfone-4-max-zc520kl/ Dowload the original firware
3. Extract the files inside the your disc C:Adb
4. Go to your celphone and enter in fastboot mode... then conect the celphone to your computer ... then use cmd " fastboot flash recovery recovery.img" .. this is for restore the original recovery if you have twrp.. if you dont have it , its no neccesary ..
5. in fastboot mode , go to Inside the firware search flashall_AFT.bat , double clik , wait until finish
6. go to recovery mode wipe/factory reset and tadaaaa! Your Os is restore again :bueno:
Click to expand...
Click to collapse
i have unlock bootloader after flash this firmware relock it agin ?
Amadu said:
I've managed to fix it by doing the following:
Copy the original recovery from a firmware package.
I could find one in the file https://androidfilehost.com/?fid=11050483647474829889, location /Asus_Zenfone_4_Max_ZC520KL_20171225/Firmware/recovery.img
Load default recovery
fastboot flash recovery recovery/original-recovery.img
Restart to bootloader
fastboot reboot bootloader
Load flashboot mode
choose the option "update using adb"
ensure that adb can locate devices with
adb devices
load firmware with
adb sideload UL-ASUS_X00HD-WW-14.2016.1805.374-user.zip ( try download from: https://www.beritahuaja.com/2018/11/download-stock-rom-asus-zenfone-4-max-zc520kl.html )
Click to expand...
Click to collapse
It works. It really works. You have saved my Asus X00HD. Thank you.
Luisanchez70 said:
Easy way with only fastboot
1. Get adb and fastboot drivers
2. go to this page h ttps://addrom.com/raw-rom-for-asus-zenfone-4-max-zc520kl/ Dowload the original firware
3. Extract the files inside the your disc C:Adb
4. Go to your celphone and enter in fastboot mode... then conect the celphone to your computer ... then use cmd " fastboot flash recovery recovery.img" .. this is for restore the original recovery if you have twrp.. if you dont have it , its no neccesary ..
5. in fastboot mode , go to Inside the firware search flashall_AFT.bat , double clik , wait until finish
6. go to recovery mode wipe/factory reset and tadaaaa! Your Os is restore again :bueno:
Click to expand...
Click to collapse
you save me
THANK YOUUUU
Opening new thread cuz it's too much for [HELP THREAD]
Start here:
https://forum.xda-developers.com/showpost.php?p=77850102&postcount=42169
I used OS_Acer_Acer.T09.AV0M0.1.035.00.EMEA.GEN1_A60M_A.zip to build rom
but it always fail to create system.img
It does create the zipped rom.
I try to copy extracted system folder to 'work' folder but same error.
Is there any log or some way to get more details on that error?
nickless07 said:
I used OS_Acer_Acer.T09.AV0M0.1.035.00.EMEA.GEN1_A60M_A.zip to build rom
but it always fail to create system.img
It does create the zipped rom.
I try to copy extracted system folder to 'work' folder but same error.
Is there any log or some way to get more details on that error?
Click to expand...
Click to collapse
When Assayed will go to step to make a size for the system image you have to put the values. Take as reference the size of your system image that you dumped before and express this value in MB.
SubwayChamp said:
When Assayed will go to step to make a size for the system image you have to put the values. Take as reference the size of your system image that you dumped before and express this value in MB.
Click to expand...
Click to collapse
That did the trick (used size from Auto Tool Unpack Repack .DAT & .IMG for Windows)
I got system.img. Now use system.img and boot.img in sp flash tool with the scatter from your zip or did i miss something?
nickless07 said:
That did the trick (used size from Auto Tool Unpack Repack .DAT & .IMG for Windows)
I got system.img. Now use system.img and boot.img in sp flash tool with the scatter from your zip or did i miss something?
Click to expand...
Click to collapse
Use these two files (system and boot) and put inside the others that you dumped before.
SubwayChamp said:
Use these two files (system and boot) and put inside the others that you dumped before.
Click to expand...
Click to collapse
Ok. which scatter should i use (only the one from your zip does not error) and should i check everything in flash tool or only specific partitions?
@nickless07
Did you see that? it looks that here there are three firmwares for your model :https://www.acer.com/ac/en/US/content/support-product/6995?b=1
Open Menu, open drivers&Manuals and you will see three firmwares under O.S.
---------- Post added at 03:23 AM ---------- Previous post was at 03:21 AM ----------
nickless07 said:
Ok. which scatter should i use (only the one from your zip does not error) and should i check everything in flash tool or only specific partitions?
Click to expand...
Click to collapse
Use just this zip, the rest won´t work, i added some info there.
Put all the files that you dumped but replace for the new system and boot.
SubwayChamp said:
@nickless07
Did you see that? it looks that here there are three firmwares for your model :https://www.acer.com/ac/en/US/content/support-product/6995?b=1
Open Menu, open drivers&Manuals and you will see three firmwares under O.S.
Click to expand...
Click to collapse
Yes i tested all 3 of them in recovery mode. And if you search on website for phone snid 717007914635 you get 2 other firmware. Right now i used the 1.035.00
So use the preloader i dumped means that the preloader i got from your zip
nickless07 said:
Yes i tested all 3 of them in recovery mode. And if you search on website for phone snid 717007914635 you get 2 other firmware. Right now i used the 1.035.00
So use the preloader i dumped means that the preloader i got from your zip
Click to expand...
Click to collapse
And all the firmwares are for recovery, with system.new.dat?
Yes, use this preloader
Ok flashed all of them. Still stuck at boot logo (i got the boot logo back) and now i can mount /system in recovery mode
Should i repeat that with other firmware?
nickless07 said:
Ok flashed all of them. Still stuck at boot logo (i got the boot logo back) and now i can mount /system in recovery mode
Click to expand...
Click to collapse
It´s an advance, you can do the same with these firmwares that you tried before preparing them via Assayed and flash it through Philz recovery.
SubwayChamp said:
It´s an advance, you can do the same with these firmwares that you tried before preparing them via Assayed and flash it through Philz recovery.
Click to expand...
Click to collapse
This does not work. Fastboot can't boot philz due to locked bootloader. Can i flash philz with sp flash tool?
nickless07 said:
This does not work. Fastboot can't boot philz due to locked bootloader. Can i flash philz with sp flash tool?
Click to expand...
Click to collapse
Yes, you can, put Philz renamed recovery and flash only this partition.
How you unlocked before, did you remember what method do you use?
SubwayChamp said:
Yes, you can, put Philz renamed recovery and flash only this partition.
How you unlocked before, did you remember what method do you use?
Click to expand...
Click to collapse
I used fastboot oem unlock then i pressed Vol. Up on device to confirm.
When i do this now the device tells me Unlock failed.
This is happening after i flashed the files from your zip.
Philz fails. I renamed it to recovery.img and only selected that one in sp flash tool (no error) but when entering recovery mode it is stock recovery
nickless07 said:
I used fastboot oem unlock then i pressed Vol. Up on device to confirm.
When i do this now the device tells me Unlock failed.
This is happening after i flashed the files from your zip.
Click to expand...
Click to collapse
These files were from the zip from Acer that you said that before that recovery stock fails to flash so I don´t understand why it could change bootloader status. Then these files from Acer itself are not for your exact version or maybe build update.
Now that you can mount system maybe you can flash the zip through your stock recovery.
Edit: the files that you flashed before from my zip were lk.bin, preloader and trustzone; flash now from all the firmwares that you downloaded these three files (one by one for firmware and try to unlock every time) using SPFlashTool and the working scatter.txt to see if you recover functionality of the bootloader
SubwayChamp said:
These files were from the zip from Acer that you said that before that recovery stock fails to flash so I don´t understand why it could change bootloader status. Then these files from Acer itself are not for your exact version or maybe build update.
Now that you can mount system maybe you can flash the zip through your stock recovery
Click to expand...
Click to collapse
Yes they are update, phone got bricked while performing ota via system updates.
I try'ed that. No luck. I will use assayyed to make some more system.img file with other zip from acer website
I've tried to restore to Stock using a few of the different ROM's from the Android File Host site, but I'm constantly stuck in a revolving Fastboot mode.
The Sprint bootloader unlock here worked fine:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
At one point I had the TWRP zip installed and working fine, so I'm not sure why I can't reboot to recovery anymore. It always boots to fastboot.
I've also tried ADB commands to run from a different slot (A/B/Other). Both slots produce this error when trying to flash the twrp.img to either slot:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Any ideas are appreciated. I thought all the Stock ROMs provided work for all variants. My phone connects successfully with TOOL_ALL_IN_ONE, and flashing a Stock image seems successful, but the phone reverts back to Fastboot loop.
Edit: I tried the Guac for All unbrick tool and method specified here:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I made sure to install the L2 drivers certificate and use the original cable that came with my phone in a USB 2.0 port. However, on the last MSM Tool's Status of Communication called Param Preload, I get an error that says Device does not match image. I'm guessing the Guac for All tool has a unified ROM, but it doesn't seem to work for my SM1925 (Sprint). I'll keep trying other methods and updating.
aktiv8d said:
I've tried to restore to Stock using a few of the different ROM's from the Android File Host site, but I'm constantly stuck in a revolving Fastboot mode.
The Sprint bootloader unlock here worked fine:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
At one point I had the TWRP zip installed and working fine, so I'm not sure why I can't reboot to recovery anymore. It always boots to fastboot.
I've also tried ADB commands to run from a different slot (A/B/Other). Both slots produce this error when trying to flash the twrp.img to either slot:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Any ideas are appreciated. I thought all the Stock ROMs provided work for all variants. My phone connects successfully with TOOL_ALL_IN_ONE, and flashing a Stock image seems successful, but the phone reverts back to Fastboot loop.
Edit: I tried the Guac for All unbrick tool and method specified here:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I made sure to install the L2 drivers certificate and use the original cable that came with my phone in a USB 2.0 port. However, on the last MSM Tool's Status of Communication called Param Preload, I get an error that says Device does not match image. I'm guessing the Guac for All tool has a unified ROM, but it doesn't seem to work for my SM1925 (Sprint). I'll keep trying other methods and updating.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261604268
Flash this, install the 9.5.17 ota and try to re-unlock
Whoareyou said:
https://androidfilehost.com/?fid=4349826312261604268
Flash this, install the 9.5.17 ota and try to re-unlock
Click to expand...
Click to collapse
Thank you so much for your help. I followed your instructions exactly.
After the MSM Tool's flash with the image provided, it no longer fastboot cycled and booted normally to 9.5.12. It paused on the 5G logo for a couple mins and then loaded into the phone setup screen. I think updated to 9.15.17 ota as instructed. Everything is now working properly.
Can I ask where you found this version of the MSM tool's stock image that works for the GM1925? I searched and searched, but couldn't find anything. Even searching for that zip's filename returned 0 results for me. I saved that file, but if new compatible stock ROM's are released, I'd like to be able to find them, too.
aktiv8d said:
Thank you so much for your help. I followed your instructions exactly.
After the MSM Tool's flash with the image provided, it no longer fastboot cycled and booted normally to 9.5.12. It paused on the 5G logo for a couple mins and then loaded into the phone setup screen. I think updated to 9.15.17 ota as instructed. Everything is now working properly.
Can I ask where you found this version of the MSM tool's stock image that works for the GM1925? I searched and searched, but couldn't find anything. Even searching for that zip's filename returned 0 results for me. I saved that file, but if new compatible stock ROM's are released, I'd like to be able to find them, too.
Click to expand...
Click to collapse
They're only sent out by OnePlus when someone needs to restore their phone due to malfunction, not released on any regular basis, but this one has been around for a while.
Hi, I am in the exact same position as you were. I downloaded the .rar file provided, but how do I flash it?
Thanks!
---------- Post added at 03:51 AM ---------- Previous post was at 03:37 AM ----------
mimat1 said:
Hi, I am in the exact same position as you were. I downloaded the .rar file provided, but how do I flash it?
Thanks!
Click to expand...
Click to collapse
UPDATE: I flashed it by starting the MSMDownloader while in EDL mode. Much thanks for this method and fix. My phone thanks you for revival!
Narwhal73 said:
Ok so for future people who run into the same problem and are clueless like me! The RAR file contains the system image and an MSM Tool. Unrar it, open the tool, put your phone in EDL mode, make sure the tool recognizes the device, then click "start".
Cheers!
Click to expand...
Click to collapse
Alright, sorry for hijacking this thread... It seems like after flashing this image, the phone has been SIM locked to Sprint?! I purchased this phone unlocked, and it was working with Public Mobile prior to trying to unlock the bootloader. @Whoareyou any advice?
---------- Post added at 07:36 PM ---------- Previous post was at 07:22 PM ----------
Narwhal73 said:
Alright, sorry for hijacking this thread... It seems like after flashing this image, the phone has been SIM locked to Sprint?! I purchased this phone unlocked, and it was working with Public Mobile prior to trying to unlock the bootloader. @Whoareyou any advice?
Click to expand...
Click to collapse
Ok, I was really spooked by the Android 9 ROM saying my device was SIM locked when I bought it unlocked.
On point with answering my own questions: applying the OTA update now shows that my phone is unlocked (as it should be!) under Settings > System updates > UICC unlock.
My phone always reboots to fastboot. I've opened MSM tool and my phone doesn't appear there. It does appear using fastboot devices command on CMD though. How can I flash this? Restart recovery or restart bootloader does nothing, always back to fastboot.