I read some articles which mention we can flash every soft on every variant,but its really working and dont get brick?Somebody tried it?
I want to update the chinese to us rom,because the more frequently updates.
I can't post a post, not too sure why but to answer your question, I recently has my A2017G model updated to B07 by a service staff, had it downgraded back to B02 because B07 never existed on Global models. And, A2017 seems to have B07, so my guess is yes, you can. But it looks kind of risky, u might have to ask the person who created the USA model and the China model
Thanks!Here is a lot of unclear things like the bootloader unlock methods and compatible software things for the global and chinese version.
Make sure to not flash the radio, whatever you do.
mihione said:
I read some articles which mention we can flash every soft on every variant,but its really working and dont get brick?Somebody tried it?
I want to update the chinese to us rom,because the more frequently updates.
Click to expand...
Click to collapse
You just need to flash Boot+System, and DON'T Flash bootstacks from other variants.
If you want Root you need to have Unlock Bootloader otherwise you are going to be able to pass ZTE Logo and have what we call softbrick
Thanks for the info!I get my phone today so i firstly have to unlock bootloader and install twrp,after that i can flash US rom without bootstack flash and im done?Wie dalvik/cache and it will boot?
mihione said:
Thanks for the info!I get my phone today so i firstly have to unlock bootloader and install twrp,after that i can flash US rom without bootstack flash and im done?Wie dalvik/cache and it will boot?
Click to expand...
Click to collapse
Did it work @mihione ?
So did it works guys? Flashing US firmware to Chinese version?
honestloez said:
So did it works guys? Flashing US firmware to Chinese version?
Click to expand...
Click to collapse
On the contrary, I successfully flashed the Chinese B13 rom to US hardware (A2017U) and it works normally. I think it may work in the same way for your case. Just need to modify the META-INF/com/google/android/updater-script to include flashing boot.img and system.new.dat only. Here's an example:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for "ailsa_ii" devices; this is a "" + getprop("ro.product.device") + "".");
show_progress(0.850000, 180);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("Failed to update system image.");
show_progress(0.050000, 1);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
set_progress(1.000000);
Backup first, and it's at your own risk!
BTW, I have twrp installed so I don't need to resign the modified zip file.
I have the ZTE Axon 7(a2017) in order for me to use the a2017U software all I had to do was download the a2017u stock firm from the ZTE website and follow the instructions in the zip folder.
wallee38 said:
I have the ZTE Axon 7(a2017) in order for me to use the a2017U software all I had to do was download the a2017u stock firm from the ZTE website and follow the instructions in the zip folder.
Click to expand...
Click to collapse
And everything works? No issues? Did you flash it by putting it on the internal memory and hit update software?
Sent from my ZTE A2017 using Tapatalk
wallee38 said:
I have the ZTE Axon 7(a2017) in order for me to use the a2017U software all I had to do was download the a2017u stock firm from the ZTE website and follow the instructions in the zip folder.
Click to expand...
Click to collapse
You are correct, the B29 factory package has no assert checks, it will just blindly flash over, but it will flash the U modem as well so its interesting to see if it messes with radio bands. What region are you using it in (US and what carrier) and is it working as expected?
Code:
ui_print("Target: ZTE/P996A01/ailsa_ii:6.0.1/MMB29M/20161014.114339:user/release-keys");
show_progress(0.850000, 180);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
package_extract_file("ddr.img", "/dev/block/bootdevice/by-name/ddr");
package_extract_file("xbl.elf", "/dev/block/bootdevice/by-name/xblbak");
package_extract_file("lksecapp.mbn", "/dev/block/bootdevice/by-name/lksecapp");
package_extract_file("rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("echarge.img", "/dev/block/bootdevice/by-name/echarge");
package_extract_file("mdtp.img", "/dev/block/bootdevice/by-name/mdtp");
package_extract_file("xbl.elf", "/dev/block/bootdevice/by-name/xbl");
package_extract_file("fastboot.img", "/dev/block/bootdevice/by-name/fbop");
package_extract_file("adspso.bin", "/dev/block/bootdevice/by-name/dsp");
package_extract_file("recovery.img", "/dev/block/bootdevice/by-name/recovery");
package_extract_file("sec.dat", "/dev/block/bootdevice/by-name/sec");
package_extract_file("NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("pmic.elf", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
package_extract_file("splash.img", "/dev/block/bootdevice/by-name/splash");
package_extract_file("hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");
package_extract_file("cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
show_progress(0.100000, 10);
format("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "0", "/data");
set_progress(1.000000);
Can you flash the G variant like the U variant, a straight flash?
Sent from my ZTE A2017 using Tapatalk
Related
Hello,
I want to retrive stock rom without any mod but I have a problem. I made backup before i flash sokkoban's rom but when i want to retrive this it's still this chinese model ALE-UL00. The next problem is when i want to flash system.img from stock package in cmd i see info that this file is unreachable (it has more than 2 GB), but when i change name of other file to system.img it's flashing. I don't know what file i can flash that will work properly?
This procedure means converting location of the phone. First flash the correct location zip via twrp. unicomelectric/cn for chineese fw, like 564 mod, and hw/eu for european fw like 575 mod. Secondly: after that flash b50 package for eu, b230/240 for cn. Lastly you can make all official updates till 575 (eu) or 564 (cn). From those fws you can flash sokkobans custom roms from sokkoban. Good luck.
tamaskurti said:
Secondly: after that flash b50 package for eu, b230/240 for cn.
Click to expand...
Click to collapse
You mean B550?
vqsk said:
You mean B550?
Click to expand...
Click to collapse
Sorry about typo. i mean b050 ... for start.
You will lose network and sim but after update to b170 they will return.
Oh, and for mm: update procedure (official updates via ota):
eu: b050, b170, b188, b550/564, b575
cn: b230/240, b558, b564
I don't see b050, only b052 to download.
vqsk said:
I don't see b050, only b052 to download.
Click to expand...
Click to collapse
That is. The basic eu fw.
Ok, great. All works properly, but the last update. I got error "Software Install Failed!" :/ I downloaded this from this site: http://huaweip8lite.blogspot.bg/2016/03/firmwarehuawei-p8-liteale-l21-official.html and i got error :/
EDIT>
All works.
vqsk said:
Ok, great. All works properly, but the last update. I got error "Software Install Failed!" :/ I downloaded this from this site: http://huaweip8lite.blogspot.bg/2016/03/firmwarehuawei-p8-liteale-l21-official.html and i got error :/
EDIT>
All works.
Click to expand...
Click to collapse
Ok. So that fw b564 from sokkobans blog is for cn firmwares. It is necessary to be on b558, or b564 (official, via ota). Because that fw its a mod from another modded cn firmware kangvip mod.
Now, if you are on eu channel, you cannot performe update to b564 sokkoban mod, because that is for cn.
BUT, from b565 (eu) or b574 (eu) you can flash another mod of sokkoban: b574 mod.
After flashing official A2017U B29 firmware from ZTE the signal network service is lost. I ignore this and continue to upgrade to Nougat successfully and I get lost signal. I notice that Dual Sim Setting is working.
Does official firmware overwrite original chinese baseband/bootstack? Is this the reason?
Can someone please upload chinese baseband/bootstack A2017 please?
Thanks so much
Thalias said:
After flashing official A2017U B29 firmware from ZTE the signal network service is lost. I ignore this and continue to upgrade to Nougat successfully and I get lost signal. I notice that Dual Sim Setting is working.
Does official firmware overwrite original chinese baseband/bootstack? Is this the reason?
Can someone please upload chinese baseband/bootstack A2017 please?
Thanks so much
Click to expand...
Click to collapse
Yes, it flashes the US bootstack. You have to flash the one here, but the dual sim settings won't work.
awsomjgp said:
Yes, it flashes the US bootstack. You have to flash the one here, but the dual sim settings won't work.
Click to expand...
Click to collapse
It is hanging ZTE and 2 chinese words logo
Thalias said:
It is hanging ZTE and 2 chinese words logo
Click to expand...
Click to collapse
Try flashing the latest A2017 rom
awsomjgp said:
Try flashing the latest A2017 rom
Click to expand...
Click to collapse
Yeah, I am on downloading it right now. I guess I have to wait DrakenFX pull out Nougat.
awsomjgp said:
Try flashing the latest A2017 rom
Click to expand...
Click to collapse
I failed to flash full A2017 B13 and got the message :assert failed getprop( ro.product.name) == "P996A03"
But I can flash full A2017U B29. Any suggestion?
Hello,
I try to upgrade from c150b123 to c150b160 but obviously I failed. I flash C150, so I dont know where was the problem...
I read that is void my warranty. Is that a true?
What can I do to resolve this problem?
Sorry for my English!
I think you can use Huawei RollBack package using 3 buttons method and then flash c150b160 using the same method.
The rollback package and firmware image can be found on huawei site. Use google.
feldwebel said:
I think you can use Huawei RollBack package using 3 buttons method and then flash c150b160 using the same method.
The rollback package and firmware image can be found on huawei site. Use google.
Click to expand...
Click to collapse
There is just Asia version of Rollback. I need to flash that?
As far as i know the region of the rollback package doesn't matter. I'm on c432 and used this
http://download-c1.huawei.com/download/downloadCenter?downloadId=93800&siteCode=pl
Be careful with the firmware image to be the right one (c150)
feldwebel said:
As far as i know the region of the rollback package doesn't matter. I'm on c432 and used this
http://download-c1.huawei.com/download/downloadCenter?downloadId=93800&siteCode=pl
Be careful with the firmware image to be the right one (c150)
Click to expand...
Click to collapse
Thanks for helping! I didn't mention that I have L31 version. Or I can flash that for L21?
No, don't flash l21. The model matters. Download from huawei website rollback pckage for l31. The model does matter.
Forgot to ask you. You're on stock recovery ?
feldwebel said:
No, don't flash l21. The model matters. Download from huawei website rollback pckage for l31. The model does matter.
Forgot to ask you. You're on stock recovery ?
Click to expand...
Click to collapse
Yes, everything is stock. And b160 is Marshmallow, not Nougat.
b12x has many bugs and I just want to fix them , because my carrier didn't release update from september...
Oh yes sorry my bad. Then you don't need the rollback package. In this case the best option is to use firmware finder to update a full ota via system update.
feldwebel said:
Oh yes sorry my bad. Then you don't need the rollback package. In this case the best option is to use firmware finder to update a full ota via system update.
Click to expand...
Click to collapse
I use firmware finder and got this problem although I check hundred times to use correct upgrade zip. I am scared to repeat update procedure because I don't want to brick my phone... :/
I guess I will have to take a risk.
You have to get the full ota update (with mf and pv in update name).
Hi,
I could not update the firmware on this phone, I can not find any C65 firmware anywhere, do you have any idea how to do it, or if there are firmware compatible to install?
Tanks at all
adryzz said:
Hi,
I could not update the firmware on this phone, I can not find any C65 firmware anywhere, do you have any idea how to do it, or if there are firmware compatible to install?
Tanks at all
Click to expand...
Click to collapse
Are you sure its not C654 or C55?
Sorryyyyyyyyyyyy ..... C652 not C65.
The phone is a retail demo version, i've unlocked bootloader and install root and twrp, but if i try to flash one firmware, twrp stop it with error e:unknown command [errno]
Any idea ?
Thanks
Try to rebrand with this method https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page54
Hi everybody!
My question is in the title "Is it possible to flash EU ROM on a CAZ-AL10?".
Thank you for your feedback!
CAZ AL 10
Also searching same
The CAZ AL10 is the model that came out in China and is for all major Chinese carriers versus the China mobile only one. The twrp, LOS and other things work fine on it (there was one poster who had problems, but they cannot be confirmed with logs).
I'm trying to flash system.img with fastboot but that error occurs:
UNLOCKED Bootloader = FAILED Remote: command not allowed
I made sure that the command is correct.
I have CAZ-AL10 which was changed to CAN-L11. There is guide in russian language how do it with TWRP and HUC. 4pda_link
After this instruction u will have euro location L11C432, and firmware CAN-L11C432B390, but u will have china boot.img. There are not any bugs.
UNLOCKED Bootloader = FAILED Remote: command not allowed
wangdaning said:
The CAZ AL10 is the model that came out in China and is for all major Chinese carriers versus the China mobile only one. The twrp, LOS and other things work fine on it (there was one poster who had problems, but they cannot be confirmed with logs).
Click to expand...
Click to collapse
Anderusk said:
I have CAZ-AL10 which was changed to CAN-L11. There is guide in russian language how do it with TWRP and HUC. 4pda.ru/forum/index.php?showtopic=795283&st=4100#entry67937512
After this instruction u will have euro location L11C432, and firmware CAN-L11C432B390, but u will have china boot.img. There are not any bugs.
Click to expand...
Click to collapse
Thank you for that! I will try next time. I come back to tell you my experience.
Good evening! (10pm in France)