Related
Hi,
Sony released new firmware update for Z4T: 32.2.A.5.11
See on Xpericheck and FlashTool.
November security patch update:
http://www.xperiblog.com/2016/12/322a511-hits-xperia-z5-series.html
For those who have installed Xposed upgrade to version 87 (due to a bug with november security patch that causes a bootloop)
Nice. Though I think I'll skip this update. I have the best stability and battery life I've ever had on any Android device right now, so I'm sticking with that.
For example, with my Samsung Galaxy S6 I regularly updated, but in the end I was stuck with different ROMs that all suffered from battery drain or stability issues. I eventually rolled back to a very old ROM that performed well again.
Not saying it's the same with Sony, but.. it ain't broken so I'm not fixing it And I couldn't care less about the November security update.
Flashed Customized NOBA 32.2.A.5.11-R4C with FlashTool v0.9.22.3. No problem for the moment
Z4T_SGP771_AndroPlusKernel_v42.zip
SuperSU-v2.79-201612051815.zip
TWRP-3.0.2-0-20160604.img
xposed-v87-sdk23-arm64.zip
drmrestore.zip
killdozer56 said:
Flashed Customized NOBA 32.2.A.5.11-R4C with FlashTool v0.9.22.3. No problem for the moment
Z4T_SGP771_AndroPlusKernel_v40.zip
TWRP-3.0.2-0-20160604.img
SuperSU-v2.78-SR4-20161115184928.zip
xposed-v87-sdk23-arm64.zip
drmrestore.zip
Click to expand...
Click to collapse
M8, is this combination really working with DRMrestore? It is said that you need the same version of firmware and kernel...
GhostLeader said:
M8, is this combination really working with DRMrestore? It is said that you need the same version of firmware and kernel...
Click to expand...
Click to collapse
Hi,
Yes it works with the features I tested (X-Reality, camera enhancement). And after flashing drmrestore.zip you got new tabs for update sony applications in
Parameters-> about the tablet->Software update
Here is the Sony service menu after flashing drmrestore.zip:
After trying the CM 13 Alfa version, I can confirm the configuration of Killdozer56 (Andro+ kernel v42) is working like a charm, including keys.
After uninstalling most of the Sony bloatware I have never seen such a responsive piece of hardware.
aykito said:
After trying the CM 13 Alfa version, I can confirm the configuration of Killdozer56 (Andro+ kernel v42) is working like a charm, including keys.
After uninstalling most of the Sony bloatware I have never seen such a responsive piece of hardware.
Click to expand...
Click to collapse
It really is something, right? Yesterday I was reading some manga for several hours (Berserk on PerfectViewer) and the battery drained very, very slowly. And this is while constantly upscaling images with Lanczos 3 to 2560x1600, which is quite intensive. Super impressive.
killdozer56 said:
Flashed Customized NOBA 32.2.A.5.11-R4C with FlashTool v0.9.22.3. No problem for the moment
Z4T_SGP771_AndroPlusKernel_v42.zip
SuperSU-v2.79-201612051815.zip
TWRP-3.0.2-0-20160604.img
Click to expand...
Click to collapse
did this, but twrp touch is not responding, i can't do anything in twrp. device boots only into twrp...
whta did I wrong?
thanks in advance!
theeyeofspike said:
did this, but twrp touch is not responding, i can't do anything in twrp. device boots only into twrp...
whta did I wrong?
thanks in advance!
Click to expand...
Click to collapse
Hi,
You are sure you have flashed the right versions for the right models (kernel v42 and TWRP-3.0.2-0-20160604-1.img). Try to reflash via ADB.
killdozer56 said:
Hi,
You are sure you have flashed the right versions for the right models (kernel v42 and TWRP-3.0.2-0-20160604-1.img). Try to reflash via ADB.
Click to expand...
Click to collapse
I used this ones:
Xperia Z4 Tablet LTE,
Central Europe 1 , Customized CE 1, 32.2.A.5.11 / R4C
TWRP-3.0.2-0-20160604.img
Z4T_SGP771_AndroPlusKernel_v42
flashed via flashtool-0.9.23.0-windows. right after flashing the kernel, there is the red light blinking...and the device soesn't do anything.
I flashed Z4T_SGP771_AndroPlusKernel_v42 - only the img.
Should I flash the whole Z4T_SGP771_AndroPlusKernel_v42.zip??? how would I do that?
You might be up for a factory reset (full wipe) since you are the only one with this combination and touch not working.
theeyeofspike said:
I used this ones:
Xperia Z4 Tablet LTE,
Central Europe 1 , Customized CE 1, 32.2.A.5.11 / R4C
TWRP-3.0.2-0-20160604.img
Z4T_SGP771_AndroPlusKernel_v42
flashed via flashtool-0.9.23.0-windows.
I flashed Z4T_SGP771_AndroPlusKernel_v42 - only the img.
Should I flash the whole Z4T_SGP771_AndroPlusKernel_v42.zip??? how would I do that?
Click to expand...
Click to collapse
When i flash a new firmware via flashtool then after i flash first kernel then twrp directly with fastboot command line under windows 10 (not via flashtool)
Boot in fastboot mode (press volume up and connect to the pc the led become blue)
Fastboot flash boot boot.img
Fastboot reboot
Power off the tablet
Boot in fastboot mode
Fastboot flash recovery twrp.img
Fastboot reboot
No problems with this method.
killdozer56 said:
When i flash a new firmware via flashtool then after i flash first kernel then twrp directly with fastboot command line under windows 10 (not via flashtool)
Boot in fastboot mode (press volume up and connect to the pc the led become blue)
Fastboot flash boot boot.img
Fastboot reboot
Power off the tablet
Boot in fastboot mode
Fastboot flash recovery twrp.img
Fastboot reboot
No problems with this method.
Click to expand...
Click to collapse
i tried to flash the kernel via fastboot command line, BUT, i writes "waiting for devide" and nothing happens.. I connected the device in fastboot mode. thats why later I tried to flash with flashtool...
theeyeofspike said:
i tried to flash the kernel via fastboot command line, BUT, i writes "waiting for devide" and nothing happens.. I connected the device in fastboot mode. thats why later I tried to flash with flashtool...
Click to expand...
Click to collapse
"Waiting for device" This indicates that the drivers are incorrectly or not installed
when you type fastboot devices a serial number like CB5A27N6F must appear.
Check into windows devices manager to see if there's no problems when the tablet is connected in fastboot mode (for me i have it under Android devices -> Android composite ADB interface)
What windows version ?
killdozer56 said:
"Waiting for device" This indicates that the drivers are incorrectly or not installed
when you type fastboot devices a serial number like CB5A27N6F must appear.
Check into windows devices manager to see if there's no problems when the tablet is connected in fastboot mode (for me i have it under Android devices -> Android composite ADB interface)
What windows version ?
Click to expand...
Click to collapse
thanks!
in the device manager, everything seems to be alright.
i installed:
"C:\Flashtool\drivers\Flashtool-drivers.exe"
Xperia_Z4_Tablet_driver
and ran the cmd in admin mode...
killdozer56 said:
When i flash a new firmware via flashtool then after i flash first kernel then twrp directly with fastboot command line under windows 10 (not via flashtool)
Boot in fastboot mode (press volume up and connect to the pc the led become blue)
Fastboot flash boot boot.img
Fastboot reboot
Power off the tablet
Boot in fastboot mode
Fastboot flash recovery twrp.img
Fastboot reboot
No problems with this method.
Click to expand...
Click to collapse
I was also having issues with touch not working, but I found it it was because I was trying to use the rootkernel tool to generate the boot.img with DRM fix... so either the rootkernel tool doesn't work anymore, or the DRM fix is causing an issue.
Anyone know how to restore the backed up TA drm keys without using the rootkernel tool?
theeyeofspike said:
thanks!
in the device manager, everything seems to be alright.
i installed:
"C:\Flashtool\drivers\Flashtool-drivers.exe"
Xperia_Z4_Tablet_driver
and ran the cmd in admin mode...
Click to expand...
Click to collapse
And Fastboot devices ?
killdozer56 said:
And Fastboot devices ?
Click to expand...
Click to collapse
as well... i must say, that i had connected a sony xperia z5 premium to this computer... is this a problem?
when I do : cmd "fastboot devices", there apperrs a serial number...
now i finally got the boot.img flashed via "C:\Flashtool\x10flasher_lib", BUT red lights blinkung on the device.
i just don't know what to do right now...
theeyeofspike said:
as well... i must say, that i had connected a sony xperia z5 premium to this computer... is this a problem?
when I do : cmd "fastboot devices", there apperrs a serial number...
now i finally got the boot.img flashed via "C:\Flashtool\x10flasher_lib", BUT red lights blinkung on the device.
i just don't know what to do right now...
Click to expand...
Click to collapse
Are you sure the USB device debug mode was activated in andoid developper options before you flash the kernel first time after flashing the new firmware.
killdozer56 said:
Are you sure the USB device debug mode was activated in andoid developper options before you flash the kernel first time after flashing the new firmware.
Click to expand...
Click to collapse
yes. did that...
just tried with itala firmware, no success... still just blinking re light...
Hi there,
I finally got around to try unlocking my axon/root/custom rom and ran into problems right in the beginning.
I'm using the Axon Toolkit 1.1.1 (that should fully work with A2017G) and followed the steps to unlock the bootloader (as afaik fastboot isn't working on the G-Variant before unlock/TWRP).
So I chose option 6-unlock, MiFlash launches and I have to select the folder with the files to flash, following the instructions of the toolkit.
For the record - I'm on MM B08.
The unlock files the AxonToolkit offers are in a folder 'A2017U_FASTBOOT_UNLOCK_EDL' containing a fastboot.img.
Can I use these files or are they only for the A2017U (as the name would suggest)??
My first thought is 'No', but then if the Toolkit is supposed to fully support the A2017G?
There is a also another downloadable file from a different thread called 'TWRP_UnlockBootloader_by_DrakenFX.zip' (by DrakenFX for Generic Device/Other), which sounds more like it, BUT:
This one is normally flashed with TWRP, not MiFlash.
In this thread one would use tenfar's signed (but containing a bug) version of TWRP to install that file BEFORE the bootloader is unlocked.
I'm however keen to jump the flawed version and
- unlock first
- flash TWRP
- flash above fastboot enabler
- flash modem/custom rom (RR) etc.
So could someone please confirm:
With a 2017G (6.0MM B08) is it possible to
- Unlock the bootloader first without using tenfar's 3.0.2 TWRP?
- Which Unlock file should I use? The first one? Or can I use the generic (second) one with MiFlash or TWRP only?
- If that works, did you simply go Advanced Options<Flash boot/bootloader/modem/recovery<choose recovery partition<select C:\Axon7Development\Axon7Toolkit\twrp\twrp-3.1.0-ailsa_ii.img with the Toolkit? (or did you e.g. have to install adb 1.4.2 first to get twrp on the device via adb)
Thanks a lot for the help everyone - I know there are a lot of Guides out there, unfortunately (and I was reading through the whole threads for all of them) it gets more confusing with each one, as they all do things slightly differently, for slightly different versions, etc.
The Toolkit seems like a great start to simplify things a lot, but there is no step-by-step guide how to exactly use it for the 2017G (using what files).
The guide using the toolkit for the A2017G uses it in command line mode - that didn't work for me. Not sure if it's using an older version, but as soon as I start the tool with a command line, it kills the existing process and comes up with the dialog (I'm also on Win7 32-bit, using 32-bit MiFlash)...
@Whoooo?
This guide is suited for you:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
There are some steps that could be simplified, but there are all OK.
Personally I think A2017G is not working well with MiFlash (several problems: difficulty to recognize the phone, MiFlash software is touchy,
many versions, need time window in EDL mode, receive hello packet error etc...). The above guide did not mention MiFlash neither.
Do not use Qualcomm bulk drivers that gives you Qualcomm HS-USB QDLoader 9008 for use with MiFlash.
Recommendation: Use Zadig (http://zadig.akeo.ie/) to have WinUSB driver for QUSB_BULK. So probably you need to uninstall the driver first ("adb reboot edl", then start Windows
device manager, Uninstall and delete the driver Qualcomm HS-USB QDLoader 9008). Unplug and replug the phone, it will appear under unknown device QUSB_BULK.
Run zadig to install driver (select the WinUSB driver) => the phone will appear OK under USB peripheral:
it will be able to receive command from axon7tool in EDL mode.
To answer your questions:
>With a 2017G (6.0MM B08) is it possible to
>- Unlock the bootloader first without using tenfar's 3.0.2 TWRP?
Yes you can do that, before installing TWRP. You can also as in the guide, install TWRP first, then unlock bootloader.
Note: if you choose to unlock the bootloader first, then you can directly install latest TWRP 3.1.1-0 (unsigned) without the need to install the signed tenfar's TWRP first as with locked bootloader, then upgrade TWRP to 3.1.1-0.
The guide is applicable for any version of MM up to V1.0.0B11.
>- Which Unlock file should I use? The first one? Or can I use the generic (second) one with MiFlash or TWRP only?
If you follow the above mentioned guide, you do not need any of these files.
>- If that works, did you simply go Advanced Options<Flash boot/bootloader/modem/recovery<choose recovery partition<select C:\Axon7Development\Axon7Toolkit\twrp\twrp-3.1.0-ailsa_ii.img with the Toolkit? (or did you e.g. have to install adb 1.4.2 first to get twrp on the device via adb)
You want to install TWRP? Follow the mentioned guide.
My own remarks on top of the guide :
Part A) step 15): Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK".
You should see the phone correctly installed thanks to Zadig and not unknown device with yellow cross.
Steps 16 to 19 could be skipped (since you can have full ROM image to restore boot/recovery if needed: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547).
Step 20) In command, type "axon7tool -w recovery": this means you should have in the directory the file recovery.bin which is exact copy of twrp_rec_tenfar.img.
Attention to enable file extension display in Windows.
Part B) steps 1 to 13 could be skipped and replaced by:
Boot into TWRP : either "adb reboot recovery" or Power + Vol Up.
Inside TWRP, flash TWRP_UnlockBootloaderPackage_by_DrakenFX.zip
https://androidfilehost.com/?fid=24723757092307343
to enable fastboot (this patch aboot and fastboot so fastboot command to unlock bootloader will be accepterd).
Then follow steps 14 to 18.
Note: if you do not enter TWRP immediately in step 17) after unlock procedure, maybe you will boot to system (Android),
and probably password asked, cancel, boot to TWRP and format data (ext4fs): Power + Volume Up (or if you can boot to system, type command "adb reboot recovery").
Note: important: in TWRP do not allow system modifications. If you allow system modifications and not flash no-verity-opt-encrypt-5.1.zip
or not flash SuperSU 2.79 immediately, you will get in trouble at boot.
Now update TWRP (if not yet done): boot in to TWRP, Install, Image, choose latest TWRP 3.1.1-0 taken from
https://eu.dl.twrp.me/ailsa_ii/
File twrp-3.1.1-0-ailsa_ii.img
md5 94018d5d92a89657ccd0420a0464859b
then check "boot partition".
Reboot to recovery and check that TWRP is the latest.
Done. Now with unlocked bootloader and TWRP latest version, you can do anything with the phone
(backup/restore, install latest stock Marshmallow or Nougat with TWRP https://forum.xda-developers.com/axon-7/development/stock-rom-a2017g-twrp-flashable-images-t3599069,
flash SuperSU2.79 for root, install custon ROM with TWRP...).
dnlilas said:
@Whoooo?
This guide is suited for you:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
There are some steps that could be simplified, but there are all OK.
Personally I think A2017G is not working well with MiFlash (several problems: difficulty to recognize the phone, MiFlash software is touchy,
many versions, need time window in EDL mode, receive hello packet error etc...). The above guide did not mention MiFlash neither.
Do not use Qualcomm bulk drivers that gives you Qualcomm HS-USB QDLoader 9008 for use with MiFlash.
Recommendation: Use Zadig (http://zadig.akeo.ie/) to have WinUSB driver for QUSB_BULK. So probably you need to uninstall the driver first ("adb reboot edl", then start Windows
device manager, Uninstall and delete the driver Qualcomm HS-USB QDLoader 9008). Unplug and replug the phone, it will appear under unknown device QUSB_BULK.
Run zadig to install driver (select the WinUSB driver) => the phone will appear OK under USB peripheral:
it will be able to receive command from axon7tool in EDL mode.
To answer your questions:
>With a 2017G (6.0MM B08) is it possible to
>- Unlock the bootloader first without using tenfar's 3.0.2 TWRP?
Yes you can do that, before installing TWRP. You can also as in the guide, install TWRP first, then unlock bootloader.
Note: if you choose to unlock the bootloader first, then you can directly install latest TWRP 3.1.1-0 (unsigned) without the need to install the signed tenfar's TWRP first as with locked bootloader, then upgrade TWRP to 3.1.1-0.
The guide is applicable for any version of MM up to V1.0.0B11.
>- Which Unlock file should I use? The first one? Or can I use the generic (second) one with MiFlash or TWRP only?
If you follow the above mentioned guide, you do not need any of these files.
>- If that works, did you simply go Advanced Options<Flash boot/bootloader/modem/recovery<choose recovery partition<select C:\Axon7Development\Axon7Toolkit\twrp\twrp-3.1.0-ailsa_ii.img with the Toolkit? (or did you e.g. have to install adb 1.4.2 first to get twrp on the device via adb)
You want to install TWRP? Follow the mentioned guide.
My own remarks on top of the guide :
Part A) step 15): Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK".
You should see the phone correctly installed thanks to Zadig and not unknown device with yellow cross.
Steps 16 to 19 could be skipped (since you can have full ROM image to restore boot/recovery if needed: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547).
Step 20) In command, type "axon7tool -w recovery": this means you should have in the directory the file recovery.bin which is exact copy of twrp_rec_tenfar.img.
Attention to enable file extension display in Windows.
Part B) steps 1 to 13 could be skipped and replaced by:
Boot into TWRP : either "adb reboot recovery" or Power + Vol Up.
Inside TWRP, flash TWRP_UnlockBootloaderPackage_by_DrakenFX.zip
https://androidfilehost.com/?fid=24723757092307343
to enable fastboot (this patch aboot and fastboot so fastboot command to unlock bootloader will be accepterd).
Then follow steps 14 to 18.
Note: if you do not enter TWRP immediately in step 17) after unlock procedure, maybe you will boot to system (Android),
and probably password asked, cancel, boot to TWRP and format data (ext4fs): Power + Volume Up (or if you can boot to system, type command "adb reboot recovery").
Note: important: in TWRP do not allow system modifications. If you allow system modifications and not flash no-verity-opt-encrypt-5.1.zip
or not flash SuperSU 2.79 immediately, you will get in trouble at boot.
Now update TWRP (if not yet done): boot in to TWRP, Install, Image, choose latest TWRP 3.1.1-0 taken from
https://eu.dl.twrp.me/ailsa_ii/
File twrp-3.1.1-0-ailsa_ii.img
md5 94018d5d92a89657ccd0420a0464859b
then check "boot partition".
Reboot to recovery and check that TWRP is the latest.
Done. Now with unlocked bootloader and TWRP latest version, you can do anything with the phone
(backup/restore, install latest stock Marshmallow or Nougat with TWRP https://forum.xda-developers.com/axon-7/development/stock-rom-a2017g-twrp-flashable-images-t3599069,
flash SuperSU2.79 for root, install custon ROM with TWRP...).
Click to expand...
Click to collapse
What?? Zadig drivers never worked for me on MiFlash. Also if you restart the EDL mode (vol up+dn+power) if you do something and it fails, it will probably work. I've been using MiFlash a lot on A2017G and don't have all those problems you mentioned
Using Controllerboy's guide would be better though, true
Hi there,
And thanks a lot both of you!
I think that pins down my problem:
- I cannot use Controllerboy's guide as the linked axontool works only on Win64 and the Toolkit for Win32 doesn't support command line...
- I managed to get the QUSB_Bulk driver installed, but MiFlash needs Qualcomm HS-USB QDLoader 9008?? Can anyone confirm this? And how do I get these back again?
- Still not sure if the 'A2017U_FASTBOOT_UNLOCK_EDL' is the right file to flash - I noticed the trial Toolkit (v1.2) has a different one?
So I either now need a guide to use the newest Toolkit version, or get MiFlash running with the right file (starting with the Unlock)...
Whoooo? said:
Hi there,
And thanks a lot both of you!
I think that pins down my problem:
- I cannot use Controllerboy's guide as the linked axontool works only on Win64 and the Toolkit for Win32 doesn't support command line...
- I managed to get the QUSB_Bulk driver installed, but MiFlash needs Qualcomm HS-USB QDLoader 9008?? Can anyone confirm this? And how do I get these back again?
- Still not sure if the 'A2017U_FASTBOOT_UNLOCK_EDL' is the right file to flash - I noticed the trial Toolkit (v1.2) has a different one?
So I either now need a guide to use the newest Toolkit version, or get MiFlash running with the right file (starting with the Unlock)...
Click to expand...
Click to collapse
Did you mean that you run Windows 32-bit so you can't use axon7toolkit (64-bit)?
To get back Qualcomm HS-USB QDLoader 9008 needed for MiFlash, in EDL mode, in Windows device manager, uninstall the driver QUSB_BULK and check option delete the driver. Unplug and replug the phone, then under unknown device QUSB_BULK install the Qualcomm HS-USB QDLoader 9008 driver from Qualcom bulk driver (qcser.inf).
dnlilas said:
Did you mean that you run Windows 32-bit so you can't use axon7toolkit (64-bit)?
To get back Qualcomm HS-USB QDLoader 9008 needed for MiFlash, in EDL mode, in Windows device manager, uninstall the driver QUSB_BULK and check option delete the driver. Unplug and replug the phone, then under unknown device QUSB_BULK install the Qualcomm HS-USB QDLoader 9008 driver from Qualcom bulk driver (qcser.inf).
Click to expand...
Click to collapse
Hi there,
Yes, the version you linked doesn't work on Win 32 - hence I#m using this one: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Unfortunately it doesn't seem to support command line.
I reinstalled the Qualcomm drivers - MiFlash now detects the phone, but when I try to select the package it first complains 'cannot find script', then it shows an error 'cannot receive hello package' and times out after trying to reset the status... aaargh
Whoooo? said:
Hi there,
Yes, the version you linked doesn't work on Win 32 - hence I#m using this one: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Unfortunately it doesn't seem to support command line.
I reinstalled the Qualcomm drivers - MiFlash now detects the phone, but when I try to select the package it first complains 'cannot find script', then it shows an error 'cannot receive hello package' and times out after trying to reset the status... aaargh
Click to expand...
Click to collapse
For MIFlash problems, I already mentioned. I cannot even get MiFlash to recognize my phone, while similar tool like Qualcom Qfil/QPST can without problem.
You said "the version you linked doesn't work on Win 32" : I did not understand. Which one, axon7tool-1.5-win64.exe ? This is command line tool only.
dnlilas said:
For MIFlash problems, I already mentioned. I cannot even get MiFlash to recognize my phone, while similar tool like Qualcom Qfil/QPST can without problem.
You said "the version you linked doesn't work on Win 32" : I did not understand. Which one, axon7tool-1.5-win64.exe ? This is command line tool only.
Click to expand...
Click to collapse
Hi there,
Yes, that's (one of) my problem(s), the axon7tool-1.5-win64.exe doesn't work (even in command line) on Win 7 32-bit. At least for me...
EDIT:
Aaaaaargh: MiFlash, 'Run as Admin' and the fastboot package flashed successful.... no problems by the looks of it.
Also no idea how to check if the bootloader is really unlocked...
OK I did not realize that you are running Windows 7 32-bit, this is why axon7tool-1.5-win64.exe (64-bit) of course could not be run.
I think the best for you is manage to find out a computer running Windows 64-bit and use axon7tool-1.5-win64.exe (EDL mode, QUSB_BULK WinUSB driver) to install TWRP (tenfar). Once TWRP installed, you can then use your Windows 7 32-bit to unlock bootloader, upgrade TWRP, flash stock ROM, flash custom ROM etc... all using TWRP as I mentioned previously.
OK, got it (I think I will post a guide here soon, clarifying some things) -
I now hav unlocked bootloader and TWRP 3.1.
Question, with dm-verity, do I swipe to 'allow modifications' before flashing e.g. RR? Or do I flash a non-stock kernel first (or does RR use a different one)? And if, which one?
Sorry for the stupid question, I haven't read up on dm-verity before...
https://twrp.me/devices/zteaxon7.html
Download the latest stable Chinese rom qpst file for z2 plus which is qfil flashable.
i found these file on club.lenovo.com.cn after two days of searching. i have flashed it in my lenovo z2 plus and it is working very well. it can be flashed with the qfil or mi flash tool. Download the rom from the given link below and follow the steps to flash.
https://club.lenovo.com.cn/thread-4259783-1-1.html
or
http://s.bs.zui.com/E82d
Seps:-
1. Download the latest rom from the given link .
2. Extract it in the C drive within a folder having very simple name like 'new'.
3. Install the flashtool and other required drivers from the link below.
4. Boot the phone into EDL mode.
5.. Use qfil to flash the file in the phone.
[note:- all data will be wiped so be sure to take backup before flashing.]
To download and use the qfil and other drivers follow the link below
http://https://forum.xda-developers.com/lenovo-zuk-z2/how-to/how-to-recover-hard-bricked-zuk-z2-plus-t3576007.
HOW TO BOOT IS THE EDL MODE[9008 PORT]
follow the steps in the link.
For bricked phone(tricky).
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/reboot-to-edl9008-modetotally-bricked-t3720932
If your phone is alive the follow these steps(easy method).
1. Enable developer option.
2. Enable usb debuging option.
3. Install latest adb driver from here.
4. Go to the directory where the adb driver is installed and inside the adb folder press shift and right click at the same time and then click on the option open command window here,
5. Type 'adb devices' these will pop a message in your phone accept it.now in the command window your device will be displayed.
6. Now type 'adb reboot edl' these command will reboot your device in the edl mode or 9008 port.
now every thing is wiped.
After first boot how to reach the home page and change the language of the phone.
just use the blue option at the top right corner of the screen and some common sense to reach the home screen.these will take you to the home screen every thing here is in the Chinese language so now we have to change it to English to do this follow the images.
Where is the rom link? and is flashing china rom (Z2131) on Indian device (Z2132) will help to relock the bootloader?
RajuMon said:
Where is the rom link? and is flashing china rom (Z2131) on Indian device (Z2132) will help to relock the bootloader?
Click to expand...
Click to collapse
It's a pretty old ROM now.
There is 3.5 QPST available. Even that too would receive official OTA builds as the latest for Z2 Plus is 4.0.xxx
Thanks.
Can I flash a Chinese rom in z2 plus and relock the bootloader?
RajuMon said:
Can I flash a Chinese rom in z2 plus and relock the bootloader?
Click to expand...
Click to collapse
Yes official Chinese room flashing can relock the bootloader
Thanks, mate this is the answer what I'm looking for:laugh:
I am using ARROW Os (pie), Now i want to get back to official stock rom with locked bootloader plox help me how to do so.
JUST now I HAVE FLASHED Lenovo_Z2_Z2132_Q01017.1_M_ZUI_2.0.093_ST_160811_QPST with QFIL and it is showing error ownload Fail:Sahara Fail:QSaharaServer Fail:The directory name is invalid. plz help me
hilarioustiwari said:
I am using ARROW Os (pie), Now i want to get back to official stock rom with locked bootloader plox help me how to do so.
JUST now I HAVE FLASHED Lenovo_Z2_Z2132_Q01017.1_M_ZUI_2.0.093_ST_160811_QPST with QFIL and it is showing error ownload Fail:Sahara Fail:QSaharaServer Fail:The directory name is invalid. plz help me
Click to expand...
Click to collapse
Do you connect your phone to 9008 port
NOTE: DON'T HOLD ANYONE RESPONSIBLE IF SOMETHING GOES WRONG DURING THE PROCESS!
This thread contains full information you might need for rooting, backing up TA partition, unlocking bootloader, installing custom recovery, installing custom rom etc.
Some notes below, read them
-I try to keep this thread clean so people have easier time navigating. @derjango has ALOT of info and fixes on his THREAD which is related to this one, give it a read
-Read comments if you have problems. You may find answer and fix there by other users. I wrote this thread few months after I did these steps to my phone so I likely made mistakes (e.g. I forgot or got some steps wrong). If you do see those mistakes or have problems that nobody else has, feel free to ask in comments.
-We will use legit rooting methods and not those sketchy one click root apps
-These instructions may apply for other z line devices but you will have to find ftf files for your own device
-Written for 14.6.A.1.236 firmware but it will work on any version that you have currently.
0. PREPARATIONS
Backup all your data (photos, videos, contacts etc.)
Fully charge your battery
Enable USB debugging
Download the following:
Latest XperiaCompanion from HERE (for drivers mainly)
Sony flashtool from HERE
Follow THIS thread to install adb drivers
Navigate to your C:\Flashtool\drivers and run Flashtool-drivers
Select Flashmode drivers, Fastboot drivers and Xperia Z1 Compact drivers and click install
Now download THIS and THIS and put it in C:\Users\username\.flashTool\firmwares
(Windows 8/8.1/10 users can try - THIS fix if you can't install flashtool drivers)
1. FLASHING .108 FIRMWARE
1.1. Run Flashtool and click on lightning button, make sure flashmode is selected and hit Ok
1.2. In left window click on + symbol until you find 14.4.A.0.108
1.3. Under wipe check both options
1.4. Click Flash
1.5. Wait
1.6. Follow the on screen instructions
(You can release vol- when you see activity in flashtool window)
(If you get device disconnected just unplug phone and repeat all from step 1.1)
1.7. Don't touch anything until blue progress bar disappears. You should see Device disconnected> Device connected in flash mode.
(Don't worry if bar gets stuck near end just let it do it's thing)
1.8. Disconnect phone and reboot
1.9. Done!!!
(Do only basic setup, we won't be staying on this rom for long)
2. ROOTING .108 FIRMWARE
2.1. Make sure USB debugging is enabled
2.2. Download THIS Easy Root Tool by zxz0O0
2.3. Unzip and run install.bat
2.4. Download SuperSu apk form HERE put it in internal storage and install it.
2.5. Update binary normally.
2.6. Done!!! You should have root now.
(Download Root Checker to make sure you do)
3. TA PARTITION BACKUP
(NOTE: This is absolutely not necessary and is only needed if you plan to go back to stock firmware AND use BionZ, X-Reality and Music ID/Gracenote. TA partition and DRM keys stored inside get erased when you unlock bootloader.
3.1 Download THIS Backup TA v9.11 by DevShaft
3.2. Extract and run Backup-TA.bat. You should see backup>TA backup.zip in main folder where you extracted
3.3. Backup whole folder to cloud since you can't flash someone's else backup if you loose yours
3.4. Done!!!
(Read linked thread for useful information and FAQ)
4. UNLOCKING BOOTLOADER
4.1. Dial *#06# on your device. You will see your IMEI code
4.2. Go HERE and scroll to bottom
4.3. Under select device select Z1 Compact and enter your IMEI code
4.4. Check the 2 boxes and click on submit. You will get your unlock code. Copy it to clipboard
4.5. Run Flashtool again and click on "BLU" button
4.6. Connect phone in flashmode.
4.7. When prompted, enter your unlocking code that you copied form SONY website
4.8. Click unlock.
(Follow any instructions that flashtool gives you. I don't remember if there are any after this)
4.9. Done!!! Your bootloader is unlocked!
5. FLASHING RECOVERY
This is how I did it. You can try to skip step 5.2. If it doesn't work try again following all steps
5.1. Download THIS TWRP by 115ek and extract recovery image in new folder
5.2. Run Flashtool and flash 14.6.A.1.236 just like you did with .108 in first step (If you have problems here see THIS comment)
5.3. Now without rebooting or disconnecting your phone flash THIS open bootloader with flashtool just like you flashed system ftf-s.
5.4. Disconnect your phone and press volume up and connect your data cable. You should see blue led.
5.5. Now enter that folder where you extracted recovery image and press shift and right click in empty window area and select Open Command window here (Powershell for windows 10 users should work fine I think. Never used it)
5.6. Type "fastboot flash recovery recovery.img" and hit enter.
5.6 Done!!! You should have your recovery now.
To reboot to recovery first disconnect your phone and hold volume down and power button. Release power button when phone vibrates but keep holding volume down until you see twrp logo.
AND THAT IS IT
Now that you have your recovery and unlocked bootloader you can flash whatever roms, kernels, mods that you want for your phone.
Thanks to:
derjango for his thread mentioned above
munjeni For supplying open bootloader ftf and for giving me support with my problems
Androxyde For Flashtool
Snoop05 For ADB driver tool
zxz0O0 For Root tool And PRF Creator tool
DevShaft For Backup TA tool
115ek For TWRP
[NUT] For XZDualRecovery
kulvertti For SuperSu Dummy
Placeholder
I'm really struggling to get past unlocking the bootloader and starting to get quite confused.
Sony Companion is up to date.
Flashtool installed and used to flash .108 firmware.
Device is rooted using Easyroot tool.
Supersu installed and binary updated.
When I go to run BLU in Flashtool it prompts me to connect my device whilst holding the volume-down button (so flash mode). A couple of seconds after doing that it prompts me to re-connect the device whilst holding the volume-up button (so fastboot mode), but nothing happens. Blue LED is on the device, but Flashtool does absolutely nothing.
When I check Flashtool-driver it does fail to install the AndroidUsbDeviceClass driver, but when I run the 15-second ADB Installer it completes successfully - plus I was able to flash the firmware earlier so I don't see why I'd now have a driver issue.
Any ideas? It's starting to drive me crazy.
Here is what you can try.
Connect your phone to pc and in command prompt type adb reboot bootloader or hold vol+ and connect your phone
Your phone will be booted to fastboot now
Now type fastboot devices
You should see
XXXXXXXXXblabla fastboot
If you see this that means that your phone is recognized in fastboot by your pc.
If you see <waiting for device> or something else go to your device manager while still in fastboot
IIRC you should see under other devices something like saXXXX or something
You can tell me what exactly it says or you can fix it yourself by googling that number and adding fastboot driver and update it manually through device manager
If you decide to do it yourself make sure you link me website where you link me thread where you found driver and write down instructions so other people can see it
If you have any other problems feel free to reply
Also i just noticed that i didn't include that you lose ta partition when ubl and since you don't have ta backup make sure you make one. You never know when you might need it
Ok, thanks for that I definitely had a problem with driver installation so followed the steps in this video - https://www.youtube.com/watch?v=fcz4o6fpDGc
Now I am a bit stuck on flashing recovery.
5.2. Run Flashtool and flash 14.6.A.1.236 just like you did with .108 in first step --- do I also check both options under Wipe? will this not remove root?
5.3. Now without rebooting or disconnecting your phone flash THIS just like you did with system ftf-s. --- not sure what I'm meant to do here
Glad you fixed that problem
Flash that file through flashtool just like you flashed system ftf
Also yes that will remove root but we had that root only to backup ta and unlock bootloader. Since you unlocked bootloader and you install twrp you can easily root any rom
I get the "'fastboot' is not a recognised ..." error when trying to flash recovery - using Windows PowerShell as I'm on Win10.
EDIT: running CMD then moving to the location of where ADB was installed and contains Fastoot.exe worked.
Thanks for the guide!
scanz said:
I get the "'fastboot' is not a recognised ..." error when trying to flash recovery - using Windows PowerShell as I'm on Win10.
Click to expand...
Click to collapse
That means you don't have fastboot drivers installed. Here is temporary fix that got me out of frustrating situations when i can't install drivers systemwise
https://mega.nz/#F!aBoUXI5Q!RmxLAO638aHNJKLwo00Hew
If it downloads as zip first unzip it and run command prompt/powershell in that folder or in powershell type cd and drag that folder, that should do the same.
fastboot will now be recognised as command
this also includes adb drivers
Just wondering, I'm trying to get Magisk running after finishing the steps in your guide, but it does not pass any of the SafetyNet checks - even basicIntegrity check comes back false. Have you any ideas or experience with this? If so perhaps you could include it as part of the guide
If you get cts fasle that means you flashed rom that comes with supersu preinstalled. You could try installing rom without magisk and removing su then flashing mahgisk.
Not sure about integrity tho. I heard that xposed can cause problems with that.
colaigor said:
5.3. Now without rebooting or disconnecting your phone flash THIS with flashtool just like you flashed system ftf-s.
Click to expand...
Click to collapse
I get this:
23/015/2018 22:15:07 - INFO - Selected Bundle for Sony Xperia Z1 Compact(D5503). FW release : 1. Customization : openbootloader
23/015/2018 22:15:07 - INFO - Preparing files for flashing
23/015/2018 22:15:07 - INFO - Please connect your device into flashmode.
23/015/2018 22:15:08 - INFO - Opening device for R/W
23/015/2018 22:15:08 - INFO - Device ready for R/W.
23/015/2018 22:15:08 - INFO - Reading device information
23/015/2018 22:15:08 - INFO - Unable to read from phone after having opened it.
23/015/2018 22:15:08 - INFO - trying to continue anyway
23/015/2018 22:15:08 - INFO - Phone ready for flashmode operations.
23/015/2018 22:15:08 - INFO - Opening TA partition 2
23/015/2018 22:15:08 - INFO - Start Flashing
23/015/2018 22:15:08 - INFO - No loader in the bundle. Searching for one
23/015/2018 22:15:13 - INFO - Processing loader.sin
23/015/2018 22:15:13 - INFO - Checking header
23/015/2018 22:15:13 - ERROR - Processing of loader.sin finished with errors.
23/015/2018 22:15:13 - INFO - Ending flash session
23/015/2018 22:15:13 - ERROR - null
23/015/2018 22:15:13 - ERROR - Error flashing. Aborted
23/015/2018 22:15:14 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
Are you sure you installed flashtool and other drivers? I can't think of any other cause for this problem right now
I flash 14.6.A.1.236 without problems using flashtool, so drivers should be ok; maybe why I'm using a Mac istead Windows?
_Pano_ said:
I flash 14.6.A.1.236 without problems using flashtool, so drivers should be ok; maybe why I'm using a Mac istead Windows?
Click to expand...
Click to collapse
Found this boot bridge for mac users. you may try it and see if it works. Can't really tell you anything about drivers on mac since i never touched one.
Also mega file may be corrupted. You can try downloading from this comment where i downloaded openbl from
Do you have windows machine to try flashing ?
yes, I try tomorrow using Windows 10, thanks
colaigor said:
Found this boot bridge for mac users. you may try it and see if it works. Can't really tell you anything about drivers on mac since i never touched one.
Also mega file may be corrupted. You can try downloading from this comment where i downloaded openbl from
Do you have windows machine to try flashing ?
Click to expand...
Click to collapse
ok, I flash .236 linked in your first post and then without rebooting or disconnecting the device I flash openbootloader and I see:
24/020/2018 09:20:14 - INFO - Closing TA partition
24/020/2018 09:20:14 - INFO - Ending flash session
24/020/2018 09:20:14 - INFO - Flashing finished.
24/020/2018 09:20:14 - INFO - Please unplug and start your phone
24/020/2018 09:20:14 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
24/020/2018 09:20:16 - INFO - Device connected in flash mode
24/022/2018 09:22:15 - INFO - Selected Bundle for Sony Xperia Z1 Compact(D5503). FW release : 1. Customization : openbootloader
24/022/2018 09:22:15 - INFO - Preparing files for flashing
24/022/2018 09:22:15 - INFO - Please connect your device into flashmode.
24/022/2018 09:22:15 - INFO - Device connected in flash mode
24/022/2018 09:22:16 - INFO - Using Gordon gate drivers version 3.1.0.0
24/022/2018 09:22:16 - INFO - Opening device for R/W
24/022/2018 09:22:16 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
that's all? 1 second flash?
_Pano_ said:
that's all? 1 second flash?
Click to expand...
Click to collapse
Sorry for late answer.
Does it work? I don't remember how much it took to flash tbh
colaigor said:
Sorry for late answer.
Does it work? I don't remember how much it took to flash tbh
Click to expand...
Click to collapse
yes, after various attempts: after flashing .236 I had to disconect and reconnect the phone in order to flash openbootloader; otherwise it doens't flash
thank you for these tutorials..I now have a rooted z1compact lollipop 5.11 locked bootloaders..My question is how can I debloat my phone..I want to uninstall other system apps that I don't need and I want to install xposed on my own..sorry I am newbie
xjhayar09 said:
thank you for these tutorials..I now have a rooted z1compact lollipop 5.11 locked bootloaders..My question is how can I debloat my phone..I want to uninstall other system apps that I don't need and I want to install xposed on my own..sorry I am newbie
Click to expand...
Click to collapse
You can download Titanium backup from playstore and delete all that you dont need and keep what you nees. Also you can find twrp flashable script that deletes all bloatware. Just sreach xperia lolipop debloat script on xda.
I downloaded a rom from androidhost.ru thinking it was an official rom. My aim was downgrading. But it's not an official rom, i guess. And either I can't get back to official rom. Please help. The Huawei technical support told me that the device could be out of guarentee.
Try installing Hi Suite and do a recovery from there
Billabomb75 said:
Try installing Hi Suite and do a recovery from there
Click to expand...
Click to collapse
Thank you. I tried Hi Suite. Hi Suite says the firmware is updated.
There is no huawei identity part and there is no update information, the firmware seems updated.
I downloaded 155 version but i can't update. About phone section --> software number seems 8.0.0.0.46(0JVO).
I can downgrade or upgrade using androidhost.ru files but the other files (app or update.zip) don't work.
Eset Nod32 says the phone is rooted, root checker says the phone is not rooted.
Well try forcing your phone to install the official Rom... Try to boot into a download mode and flash through there
I download full ota zip and L11_hw_eu files from different sites. I turn off the device. I push the volume down and volume up and power button (force) the software installation fails.
Search XDA universal search for hurupdater ..
Get firmware finder from playstore ..download correct stock rom
Follow hurupdater instructions to update in recovery
Firmware finder doesn't find firmware for p smart.
Hurupdater needs unlocked bootloader i guess.
candask said:
Firmware finder doesn't find firmware for p smart.
Hurupdater needs unlocked bootloader i guess.
Click to expand...
Click to collapse
I have a huawei p smart and firmware finder & hurupdater is working ..but yes ..you need an unlocked bootloader ..
In that case
Download stock rom with firmware finder and put on sd
download stock recovery from p smart forum and flash with fastboot ..boot into stock recovery and use stock recovery to restore ...
And on a seperate note , I recommend downloading dc unlocker application and downgrading and unlocking bootloader using dc unlocker ..just search in XDA universal search ....it's a working method ..
Here you can see it :good:
KevMetal said:
I have a huawei p smart and firmware finder & hurupdater is working ..but yes ..you need an unlocked bootloader ..
In that case
Download stock rom with firmware finder and put on sd
download stock recovery from p smart forum and flash with fastboot ..boot into stock recovery and use stock recovery to restore ...
Click to expand...
Click to collapse
thank you but here somebody says:
"Unless your bootloader is unlocked you can't flash ANY .img file ..."
candask said:
thank you but here somebody says:
"Unless your bootloader is unlocked you can't flash ANY .img file ..."
Click to expand...
Click to collapse
No , you can flash only *signed files ...big difference ..you can ALWAYS flash files signed by huawei like stock recovery
https://drive.google.com/file/d/1dFFjCG2xeg9E08SZFA7jC9y21iX1sJgD/view
_there is stock recovery in link
_put in fastboot folder
_rename to recovery.img
_inside settings of phone enable usb debugging ..connect to pc ..in pop-up window allow debug connection (tick always allow )
_open cmd window as admin in fastboot folder
_Run the following commands
adb devices
*should show a serial number
adb reboot bootloader
fastboot devices
*should show a serial number
fastboot flash recovery_ramdisk recovery.img
fastboot reboot
KevMetal said:
No , you can flash only *signed files ...big difference ..you can ALWAYS flash files signed by huawei like stock recovery
https://drive.google.com/file/d/1dFFjCG2xeg9E08SZFA7jC9y21iX1sJgD/view
_there is stock recovery in link
_put in fastboot folder
_rename to recovery.img
_inside settings of phone enable usb debugging ..connect to pc ..in pop-up window allow debug connection (tick always allow )
_open cmd window as admin in fastboot folder
_Run the following commands
adb devices
*should show a serial number
adb reboot bootloader
fastboot devices
*should show a serial number
fastboot flash recovery_ramdisk recovery.img
fastboot reboot
Click to expand...
Click to collapse
thank you. but failed command not allowed?
Does your phone have the OEM UNLOCK option enabled in the developer settings / is the FRP setting disabled. Having an unlocked bootloader simplifies things a lot. I had a similar issue and used the PC version of the huawei firmware finder by TEAM MT and had to use the DNS method (either do via router or set the pc as a hotspot to reflash a lower version of firmware
I took the telephone to a shop for firmware repair. He tried for a couple of days and he also couldn’t get back to official software.
candask said:
Firmware finder doesn't find firmware for p smart.
Hurupdater needs unlocked bootloader i guess.
Click to expand...
Click to collapse
Hi, Candask
I see you are having problems getting back to official software for the Huawei P smart
Knowing that it says System 8.0.0.046 means you are running Huawei Firmware but System 8.0.0.046 usually means the firmware was made for a different model
How this works is the version folder ( partition ) includes information on the device model and if that version folder does not include the files for your region or model, it will display as System 8.0.0.046, not a serious issue but it is fixable
If you could get in contact with me on our Facebook page www.facebook.com/livitechdev
and also provide us with the Huawei P smart model number ( at the bottom of the phone on the back it will say Model: FIG-XXX, mine says FIG-LX1 )
And we will see if we can help you out - Thanks Ryan
8.0.0 is just the software version, what i think you need to match is for example mine is C782
example if you search you had found the following FIG-LX1C09B139 is device/model , and (8.0.0.139) is software version, id reckon aslong as you match the device and get the latest software version it would work
friartuckme said:
8.0.0 is just the software version, what i think you need to match is for example mine is C782
example if you search you had found the following FIG-LX1C09B139 is device/model , and (8.0.0.139) is software version, id reckon aslong as you match the device and get the latest software version it would work
Click to expand...
Click to collapse
@candask - this User is on the right track,
He would be able to get the software version of he already knows his phones model number C782, C472, C106, etc
The only place I believe you can find your model number inside Android is on the build number inside of settings>System>About Phone
8.0.0.137 ( C782 ) is the usual format
8.0.0 being Android version
137 being Huawei's version
( C782 ) being model number of device
the build number Candask has says
System 8.0.0.046( 0VJO )
Which does not give Indication of what model phone he has
Have you tried using E-recovery?
Livi-Tech said:
@candask - this User is on the right track,
He would be able to get the software version of he already knows his phones model number C782, C472, C106, etc
The only place I believe you can find your model number inside Android is on the build number inside of settings>System>About Phone
8.0.0.137 ( C782 ) is the usual format
8.0.0 being Android version
137 being Huawei's version
( C782 ) being model number of device
the build number Candask has says
System 8.0.0.046( 0VJO )
Which does not give Indication of what model phone he has
Have you tried using E-recovery?
Click to expand...
Click to collapse
hi livi-tech
I think what he is experiencing is when he has flashed a custom rom on his phone its changed the rom version name i believe, so even in e-recovery and fastboot it is being read as an unsupported device. il attach a picture to try and show
E-Recovery and attempting to use hisuite will work up until it checks his imei and device / software info then it is unable to proceed
friartuckme said:
hi livi-tech
I think what he is experiencing is when he has flashed a custom rom on his phone its changed the rom version name i believe, so even in e-recovery and fastboot it is being read as an unsupported device. il attach a picture to try and show
E-Recovery and attempting to use hisuite will work up until it checks his imei and device / software info then it is unable to proceed
Click to expand...
Click to collapse
Hello @friartuckme
I haven't had any issues with E-recovery and fastboot in the past no matter what my build number was or what custom ROM was flashed, not sure about HiSuite as I don't have a use for it but I had a look to confirm, even with the build number being different E-recovery still works and fastboot
This is my current setup
Build number: LiviTech (EM Pixel)
EMUI version: 8.0.0
E-recovery picks up: 8.0.0.137(C782) and starts downloading package
This was my setup when looking into compatibility issues a few months ago
Build number: System 8.0.0.046( 0VJO )
EMUI version: 8.0.0
E-recovery picks up: 8.0.0.137(C782) and starts downloading package
Deleting the whole version partition results in
Build number: System 8.0.0.046( OVJO )
EMUI version: 8.0.0
E-recovery picks up: 8.0.0.137(C782) and starts downloading package
( Would not recommend deleting version partition or modifying it unless you want phone to reset or apps to get removed, it's a Huawei issue )
I think I know what the issue his, the firmware he flashed sounds like Huawei firmware ( or a version of it ) but it sounds like the version partition included with that firmware doesn't include the files for his model.