Hi everyone,
I'm just here announcing for anyone who doesn't know and have the A2017U (USA Axon 7), The Nougat B15 update (SDCard Full Zip) is available online for those who need factory image base on Nougat B15.
Where to Download? :
* ZTE Axon 7 B15 (Nougat)
* Click / Tap " Software Updates "
Things to know about this Nougat B15 SDCard update zip :
FOR LOCK BOOTLOADER USERS :
1- This update.zip will perform a FDR / Factory Reset
NOTE : save everything to your SDCard or PC before proceeding with B15 update.zip installation
FOR UNLOCK BOOTLOADER USERS :
1- Same as Lock bootloader users. (READ ABOVE)
2- This zip file will replace current recovery for the stock B15 recovery.
3- Your bootloader will remain unlock, BUT you no longer will be able to execute fastboot commands.
I just want to Thank ( BIG THANK YOU ) to our hero @SShasan from Z-Community for this update / factory images file, WE wouldn't have this file if wasn't for him.
Always good to have another image.
@DrakenFX, I saw the update when I checked a few days ago. Too busy to make a post about it.
In any event, looks like they're including a fastboot.img again. Have you had a chance to compare this against previous fastboot.img's? My guess is it's similar/identical to b29.
For those that want to preserve fastboot commands and twrp (this too should be flashable in twrp as b29 was), just edit the update script to remove the lines for fastboot, recovery. Probably a good idea to leave the format user data if you're switching between roms.
These lines specifically in update-script.
Code:
package_extract_file("recovery.img", "/dev/block/bootdevice/by-name/recovery");
package_extract_file("fastboot.img", "/dev/block/bootdevice/by-name/fbop");
gpz1100 said:
@DrakenFX, I saw the update when I checked a few days ago. Too busy to make a post about it.
In any event, looks like they're including a fastboot.img again. Have you had a chance to compare this against previous fastboot.img's? My guess is it's similar/identical to b29.
For those that want to preserve fastboot commands and twrp (this too should be flashable in twrp as b29 was), just edit the update script to remove the lines for fastboot, recovery. Probably a good idea to leave the format user data if you're switching between roms.
These lines specifically in update-script.
Code:
package_extract_file("recovery.img", "/dev/block/bootdevice/by-name/recovery");
package_extract_file("fastboot.img", "/dev/block/bootdevice/by-name/fbop");
Click to expand...
Click to collapse
What is the process for deleting these lines? Last time I tried it wouldn't flash.
No need to quote an entire post when your reply immediately follows.
I use notepad++ to edit. Regular notepad does something to end of line indicators. Use 7zip to extract and update the script file.
gpz1100 said:
@DrakenFX, I saw the update when I checked a few days ago. Too busy to make a post about it.
In any event, looks like they're including a fastboot.img again. Have you had a chance to compare this against previous fastboot.img's? My guess is it's similar/identical to b29.
For those that want to preserve fastboot commands and twrp (this too should be flashable in twrp as b29 was), just edit the update script to remove the lines for fastboot, recovery. Probably a good idea to leave the format user data if you're switching between roms.
These lines specifically in update-script.
Code:
package_extract_file("recovery.img", "/dev/block/bootdevice/by-name/recovery");
package_extract_file("fastboot.img", "/dev/block/bootdevice/by-name/fbop");
Click to expand...
Click to collapse
Those 2 lines and the last line : Wipe Data
Well if you want to keep data if not , just leave it there
I thought not formatting data could lead to decryption issues when switching between rom bases. For example LOS --> Stock.
gpz1100 said:
I thought not formatting data could lead to decryption issues when switching between rom bases. For example LOS --> Stock.
Click to expand...
Click to collapse
If you switching from NON-Stock ROM to LOS base Roms, so yeah DATA needs to be wipe. Otherwise you can remove that line...Is not like TWRP doesn't have the ability to wipe data hehehe :silly:
Is it possible to downgrade back to b29 if nougat goes haywire on me?
DrakenFX said:
If you switching from NON-Stock ROM to LOS base Roms, so yeah DATA needs to be wipe. Otherwise you can remove that line...Is not like TWRP doesn't have the ability to wipe data hehehe :silly:
Click to expand...
Click to collapse
Is modifying the update script will remove zte signed certif to flash in Stock recovery, correct?
If you Modify the file only way of flashing isTwrp.
Sent from my ZTE A2017U using Tapatalk
---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ----------
XBlackChaosX said:
Is it possible to downgrade back to b29 if nougat goes haywire on me?
Click to expand...
Click to collapse
Yes you can go back using draken b29 modded zip or flashing Zte b29 firmware..
Sent from my ZTE A2017U using Tapatalk
DrakenFX said:
Hi everyone,
I'm just here announcing for anyone who doesn't know and have the A2017U (USA Axon 7), The Nougat B15 update (SDCard Full Zip) is available online for those who need factory image base on Nougat B15.
Where to Download? :
* ZTE Axon 7 B15 (Nougat)
* Click / Tap " Software Updates "
Things to know about this Nougat B15 SDCard update zip :
FOR LOCK BOOTLOADER USERS :
1- This update.zip will perform a FDR / Factory Reset
NOTE : save everything to your SDCard or PC before proceeding with B15 update.zip installation
FOR UNLOCK BOOTLOADER USERS :
1- Same as Lock bootloader users. (READ ABOVE)
2- This zip file will replace current recovery for the stock B15 recovery.
3- Your bootloader will remain unlock, BUT you no longer will be able to execute fastboot commands.
I just want to Thank ( BIG THANK YOU ) to our hero @SShasan from Z-Community for this update / factory images file, WE wouldn't have this file if wasn't for him.
Click to expand...
Click to collapse
How can I get back fastboot commands?
@DrakenFX
On B29 I was able to add the modified update-script file using 7-zip without any issues. On B15 it's rejecting it with a 'not implemented error' from 7-zip. Is there a different tool to use to manipulate these archive files?
Thanks!
Edit: B15, not B19
sinekm1 said:
How can I get back fastboot commands?
Click to expand...
Click to collapse
Check edl thread.
I just updated to 7.1.1 and would like roll back to 7.1.0. Will downloading the .zip on the SD card of the phone and running it re-install 7.1.0 on my phone?
Thanks
Itsmejayson said:
I just updated to 7.1.1 and would like roll back to 7.1.0. Will downloading the .zip on the SD card of the phone and running it re-install 7.1.0 on my phone?
Thanks
Click to expand...
Click to collapse
There is no 7.1.0, just 7.0. What issue are you having with 7.1.1?
Yes, flashing the full firmware image from the zte site will downgrade it to 7.0.
gpz1100 said:
There is no 7.1.0, just 7.0. What issue are you having with 7.1.1?
Yes, flashing the full firmware image from the zte site will downgrade it to 7.0.
Click to expand...
Click to collapse
Thanks for your reply. Some apps I was using does not work with the March security patch.
It seems like the mirror for the download is down. Does anyone has another link?
Thanks
Itsmejayson said:
Thanks for your reply. Some apps I was using does not work with the March security patch.
It seems like the mirror for the download is down. Does anyone has another link?
Thanks
Click to expand...
Click to collapse
Indeed, looks like they pulled it. I wonder if this means the B19 firmware package will be available shortly.
Here's another mirror on afh
https://www.androidfilehost.com/?fid=673368273298940518
gpz1100 said:
There is no 7.1.0, just 7.0. What issue are you having with 7.1.1?
Yes, flashing the full firmware image from the zte site will downgrade it to 7.0.
Click to expand...
Click to collapse
bro u can help me
im on 7.1.1 without root and lock bootloader
i want back to 6.0. for unlock the bootloader u have idea how i can back
really im tired
mr.mgmg said:
bro u can help me
im on 7.1.1 without root and lock bootloader
i want back to 6.0. for unlock the bootloader u have idea how i can back
really im tired
Click to expand...
Click to collapse
Go to zte and download b29, put on sd and go to settings/updates.
lafester said:
Go to zte and download b29, put on sd and go to settings/updates.
Click to expand...
Click to collapse
Zte pulled the image for B29 when they posted B15. Looks like in the last week or so they pulled the B15 image too.
Related
I was in the process of removing kingroot and installing supersu when my phone decided to reboot and now will not boot past the very first screen no matter how long I let it sit. I tried factory resetting it but that didn't change anything. I've searched high and low for firmware but have come up empty. Does anyone have stock firmware for the Alcatel Streak? Thanks.
archmagusdg said:
I was in the process of removing kingroot and installing supersu when my phone decided to reboot and now will not boot past the very first screen no matter how long I let it sit. I tried factory resetting it but that didn't change anything. I've searched high and low for firmware but have come up empty. Does anyone have stock firmware for the Alcatel Streak? Thanks.
Click to expand...
Click to collapse
Concur.
I had exactly the same problem. Alcatel Streak (40600) would not boot after I did KingRoot and superSu replacement.
There has been no activity on this or other Alcatel STREAK threads for some time, but for any members needing, I have a full stock ROM for the Cricket Alcatel STREAK (4060o), Android 6.0.1 Marshmallow. Any interested members please leave a comment and I will upload the ROM and post a download link.
i need the file for the streak 4060o
@Viva La Android
Viva La Android said:
There has been no activity on this or other Alcatel STREAK threads for some time, but for any members needing, I have a full stock ROM for the Cricket Alcatel STREAK (4060o), Android 6.0.1 Marshmallow. Any interested members please leave a comment and I will upload the ROM and post a download link.[/QUOT
Ive been able to aquire a stock firmware as well...the problem is after i flash with qfil it wont boot??? Qualcom qfil says download complete with no sahara errors..ive got the emmc programmer file if anyone needs... i just dont know what to do next to get it to boot
Click to expand...
Click to collapse
KtownJeff said:
@Viva La Android
Viva La Android said:
There has been no activity on this or other Alcatel STREAK threads for some time, but for any members needing, I have a full stock ROM for the Cricket Alcatel STREAK (4060o), Android 6.0.1 Marshmallow. Any interested members please leave a comment and I will upload the ROM and post a download link.[/QUOT
Ive been able to aquire a stock firmware as well...the problem is after i flash with qfil it wont boot??? Qualcom qfil says download complete with no sahara errors..ive got the emmc programmer file if anyone needs... i just dont know what to do next to get it to boot
Click to expand...
Click to collapse
I understand your dilemma. My stock ROM and firmware are installable via TWRP, which I have ported over from the Alcatel IDEAL (4060a). Flashing a firmware to this device without using a custom recovery is problematic to say the least. QFIL/QPST does not seem to work, and true to their typical protocol, TCL seems to have disabled fastboot mode on the 4060o. I will research this matter some more to see if I can help. There are reports of forcing the device into a hard brick by corrupting the /sbl1 bootloader partition. As such, Qualcomm's EDL (9008) mode is enabled which will allow for an emergency firmware installation per firehose protocol via QPST. But again, I'll try and research this more. Also, if you don't mind, could you share the firmware you have please? It sounds like you have an official package which I have not been able to locate. My ROM and firmware are both self compiled. Thank you.
Click to expand...
Click to collapse
awesome
Viva La Android said:
KtownJeff;80315069 [user=10059830 said:
@Viva La Android[/user]
I understand your dilemma. My stock ROM and firmware are installable via TWRP, which I have ported over from the Alcatel IDEAL (4060a). Flashing a firmware to this device without using a custom recovery is problematic to say the least. QFIL/QPST does not seem to work, and true to their typical protocol, TCL seems to have disabled fastboot mode on the 4060o. I will research this matter some more to see if I can help. There are reports of forcing the device into a hard brick by corrupting the /sbl1 bootloader partition. As such, Qualcomm's EDL (9008) mode is enabled which will allow for an emergency firmware installation per firehose protocol via QPST. But again, I'll try and research this more. Also, if you don't mind, could you share the firmware you have please? It sounds like you have an official package which I have not been able to locate. My ROM and firmware are both self compiled. Thank you.
Click to expand...
Click to collapse
https://mega.nz/#!BGwGFAgK!gW3ik2f_-oyI9MtER-PCrfSTQCio4CFzVWR6JVmSw_0
stock cricket Rom mm 6.0.1
@Viva La Android
...now let me tell you how this started to give you more info....I rooted with kingroot installed twrp for the 4060a with flashify and directly installed magisk 18 with twrp...somewhere in there i deleted king root...everything worked great..made a full back up through twrp..I had titanium backup installed deleated all the bloat and started on magisk mods..installed xposed as well...flashed viper4...well I got greedy and started trying to dirty flash pixie4 roms to get a higher os like oreo...fail fail fail...I had read in the forum not to tick fix permissions in TWRP but i did it anyway...never ending bootloop after that...i side loaded a custom rom for the 4060a ....hard brick...i guess thats when i was EDL mode because of the wrong bootloader...i tried to flash the cricket rom with qset\qfil and it would not work...then i flashed the stock 4060a and it worked...wouldn't boot past the splash screen...kinda weird though because the splash screen was split in half and reversed with a gap in the middle....ill figure out a way to screen shot later....but i was able to hook back into the pc and I have adb but unauthorized because the OS got factory wiped so no usb debugging...I do have fastboot access now...which is strange but since my oem unlock is not ticked in the OS every boot img recovery img or system img i try to flash acts all good then fail in fastboot....my realization is that I wiped my modem somewhere in there and it replaced it with a downgrade which forced the EDL mode...well I flashed wrong with the 4060a firmware so Im stuck is all I can figure...I cant get adb shell access either haven't tried
shell with ubuntu/python maybe i can get shell access to force feed super user and tick oem unlock for the bootloader...other than that Im stumped...Maybe DD commands and a good dump file to see where I stand...and as far as my TWRP backup goes..I got careless and deleated it when I formated my PC to remove all the crap Ive picked up trying to fix this mess off the MTK and GSM sites...
My main objective right now is to get my adb key authorized there has to be a way
Click to expand...
Click to collapse
Yeah I agree totally. If there was a way to enable the OEM Unlocking option from a shell environment, you would likely have total control of the device via fastboot protocol. Like you, I concur that there has to be a way. You have me perplexed enough to dig in and help find an answer. I have a working device and a bricked device, so I am free to experiment around on my brick using QFIL/QPST. I am impressed that you have been able to access fastboot. This is more progress than most people make, so congrats there. Nice work.
By the way @KtownJeff, if you need any partition dumps from my device, for example, /sbl1, /aboot, /rpm, /tz, etc., just let me know. Just a thought, but if you could push my /persist partition image to your device (my OEM Unlocking is enabled), I think your OEM Unlocking would tick enabled. I recall a Moto device where OEM Unlocking was enabled in a similar manner. @KtownJeff, if possible, please share a download link of the official firmware package to which you referred. I will be glad to share my self compiled firmware package and stock ROM. Thank you friend.
Viva La Android said:
Yeah I agree totally. If there was a way to enable the OEM Unlocking option from a shell environment, you would likely have total control of the device via fastboot protocol. Like you, I concur that there has to be a way. You have me perplexed enough to dig in and help find an answer. I have a working device and a bricked device, so I am free to experiment around on my brick using QFIL/QPST. I am impressed that you have been able to access fastboot. This is more progress than most people make, so congrats there. Nice work.
By the way @KtownJeff, if you need any partition dumps from my device, for example, /sbl1, /aboot, /rpm, /tz, etc., just let me know. Just a thought, but if you could push my /persist partition image to your device (my OEM Unlocking is enabled), I think your OEM Unlocking would tick enabled. I recall a Moto device where OEM Unlocking was enabled in a similar manner. @KtownJeff, if possible, please share a download link of the official firmware package to which you referred. I will be glad to share my self compiled firmware package and stock ROM. Thank you friend.
Click to expand...
Click to collapse
I actually stumbled on the fastboot accidentally!!...After I flashed the Stock 4060A firmware with the split up splash image I checked my driver to see if I was in qloader 9008 mode still and I saw the holy grail "Android Bootloader"...The phone screen didnt have anything showing on it like any moto mfastboot mode or like a samsung when hooked up to odin...just the frozen "half splash" Alcatel Logo..I had minimal adb/fastboot installed...I switched to the Android platform tools latest version and had better results...I had a lot of failures when it come down to recovery partition and system partition...I had some successes tho...Fastboot erase works but I dont know if thats standard and the OS reinstalls what I erased because of the lock..prob so just like no superuser access in ADB...I tried to re flash TWRP for like three days and gave up...I forgot to mention I have no stock recovery access.......Yes please I need a full phone dump of whatever you got... all the better..I might try shorting my board to get back to EDL so I can try flash the cricket 6.0.1 again...but I don't want to lose my fastboot access either....the 6040O aboot partion does not have fastboot... The Stock crickit 4060O rom link was posted earlier...I'm in the process of uploading to MEGA as we speak so here in a few I will post all my stuff for this phone...And please share yours as well...
stock Rom's and tools for Alcatel 4060A/O
@Viva La Android
TWRP Recovery https://mega.nz/#!QTwlESgJ!YSu6T5r93AonRiSxh6QQtov_ZDsxz95YW1RXYSuPJRQ
QSET/QSIL Qualcom all in one https://mega.nz/#!xSoSQCTK!MPQJytxtVUl4aHBXQp7wYbZb9o6ZpXX5wpTy3dqX7xA
Firehose Programmer file for QFIL/QSET https://mega.nz/#!EGQAXKBC!LfyE2zJzhXB15XeAgxB3H2HcL0OiXNa38V74ZodJf5I
Acatel Ideal 4060A AT&T Stock Firmware L 5.1.1
https://mega.nz/#!8ewAxCZS!sGURkuzmzcgbh6_AYOMyokzkx3VA74g50gYfZPFZOAA
Alcatel Streak 4060O Cricket Stock Firmware MM 6.0.1 https://mega.nz/#!BGwGFAgK!gW3ik2f_-oyI9MtER-PCrfSTQCio4CFzVWR6JVmSw_0
Fix BootLoop Alcatel Ideal
there´s any stock rom flashable for the alcatel ideal? i need unbrick my device because when i make a flashable stock rom the device boots and shows the screen for a second and after still bootlooping, i tried with QFIL but i have problems connecting the device, any way to fix? porting a rom with same chipset? or using another methods. PLZ i need unbrick my phone :crying:
KV2_URSS said:
there´s any stock rom flashable for the alcatel ideal? i need unbrick my device because when i make a flashable stock rom the device boots and shows the screen for a second and after still bootlooping, i tried with QFIL but i have problems connecting the device, any way to fix? porting a rom with same chipset? or using another methods. PLZ i need unbrick my phone :crying:
Click to expand...
Click to collapse
There was one here on XDA. It was a TWRP flashable Android 5.1.1 stock ROM I believe. The OP of the ROM is no longer on XDA and it appears that the download links are dead. I'll try to find you a copy of the ROM though.
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
KtownJeff said:
@Viva La Android
TWRP Recoveryhttps://mega.nz/#!QTwlESgJ!YSu6T5r93AonRiSxh6QQtov_ZDsxz95YW1RXYSuPJRQ
QSET/QSIL Qualcom all in onehttps://mega.nz/#!xSoSQCTK!MPQJytxtVUl4aHBXQp7wYbZb9o6ZpXX5wpTy3dqX7xA
Firehose Programmer file for QFIL/QSET https://mega.nz/#!EGQAXKBC!LfyE2zJzhXB15XeAgxB3H2HcL0OiXNa38V74ZodJf5I
Acatel Ideal 4060A AT&T Stock Firmware L 5.1.1
https://mega.nz/#!8ewAxCZS!sGURkuzmzcgbh6_AYOMyokzkx3VA74g50gYfZPFZOAA
Alcatel Streak 4060O Cricket Stock Firmware MM 6.0.1https://mega.nz/#!BGwGFAgK!gW3ik2f_-oyI9MtER-PCrfSTQCio4CFzVWR6JVmSw_0
Click to expand...
Click to collapse
Oh thank you very much. I was in need of the 4060o official firmware package. I'm in debt to you. Thanks for all the extras as well! Nice. I will upload my stock partition dump of my 4060o and get that posted ASAP. Have you tried using an insecure boot image for ADB superuser (ADBD) access? If you want I can set my stock boot image insecure with ADBD and upload that as well.
I'm found a copy of a stock 5.1.1 ROM for the 4060a that is TWRP flashable. I'm uploading it to Mega File now. I'll post the link when completed. I fixed the installer on this ROM and rewrote the Edify script.
4060a Stock ROM
TWRP Flashable Zip
Android 5.1.1 Lollipop
Build No. M5RUAR4
Root: SuperSU v2.82-SR5
Link: https://mega.nz/#!VEVUwaxB!sCsdYXPE-_ytsqKnXRJHhFLVLnn3jxCDY8bG7FP89nM
@KV2_URSS, if you have TWRP installed, this may unbrick your device.
Update: I dissected that ROM and discovered some syntax errors in the Edify script. I've rewritten the installer and fixed some bugs with the updater-script. I also just tested the ROM on my own 4060a and confirmed that it does work. I'll post the updated link to replace the other link in a few minutes.
Viva La Android said:
Update: I dissected that ROM and discovered some syntax errors in the Edify script. I've rewritten the installer and fixed some bugs with the updater-script. I also just tested the ROM on my own 4060a and confirmed that it does work. I'll post the updated link to replace the other link in a few minutes.
Click to expand...
Click to collapse
Thanks, this is a posibility for unbrick my phone, you now fixed the rom link? :good:
KV2_URSS said:
Thanks, this is a posibility for unbrick my phone, you now fixed the rom link? :good:
Click to expand...
Click to collapse
flashed but still bootlooping, i think my phone its broken Anyway: thanks for help!
KV2_URSS said:
flashed but still bootlooping, i think my phone its broken Anyway: thanks for help!
Click to expand...
Click to collapse
Did you download from the updated link? The ROM from the old link was bootlooping my 4060a also. I fixed the installer script and when I tried it again it worked. On the new one, I added my username to the installer script and removed the original dev's name. Is this the one you tried? Also, did you do a full wipe before installing? (/system, /cache, Dalvik, format /data)
---------- Post added at 01:22 PM ---------- Previous post was at 01:17 PM ----------
@KtownJeff I'll try to have the 4060o stock 6.0.1 ROM posted later today, and I'll post the dump files from my device. Thank you again for the official firmware.
Viva La Android said:
Did you download from the updated link? The ROM from the old link was bootlooping my 4060a also. I fixed the installer script and when I tried it again it worked. On the new one, I added my username to the installer script and removed the original dev's name. Is this the one you tried? Also, did you do a full wipe before installing? (/system, /cache, Dalvik, format /data)
Click to expand...
Click to collapse
i flashed the updated rom with your name in updater script and still bootlooping
KV2_URSS said:
i flashed the updated rom with your name in updater script and still bootlooping
Click to expand...
Click to collapse
Ok. My guess is your boot chain may be corrupt. I'll write you an installer to try and fix it. I'm fixing some things on the 4060o ROM, so I'll write you an installer for your 4060a when I get ready to upload the other ROM. In the installer, I'll place some of the bootloader partitions from the firmware package to be installed on your device.
Viva La Android said:
Did you download from the updated link? The ROM from the old link was bootlooping my 4060a also. I fixed the installer script and when I tried it again it worked. On the new one, I added my username to the installer script and removed the original dev's name. Is this the one you tried? Also, did you do a full wipe before installing? (/system, /cache, Dalvik, format /data)
---------- Post added at 01:22 PM ---------- Previous post was at 01:17 PM ----------
@KtownJeff I'll try to have the 4060o stock 6.0.1 ROM posted later today, and I'll post the dump files from my device. Thank you again for the official firmware.
Click to expand...
Click to collapse
@Viva La Android....no problem for the files my friend...please post the ROM and dump files...i went as far as test point into EDL mode and I cant get anything to download for some reason...Im gonna play around with QSET and see if there is a way to just wipe and manual install partitions that way
KtownJeff said:
@Viva La Android....no problem for the files my friend...please post the ROM and dump files...i went as far as test point into EDL mode and I cant get anything to download for some reason...Im gonna play around with QSET and see if there is a way to just wipe and manual install partitions that way
Click to expand...
Click to collapse
Ok friend. I'll expedite and get that done now. To clarify, you want a full partition dump of my 4060o, correct?
The partition dump files and MM stock ROM for 4060o are uploading now. @KtownJeff, I don't have the best signal tonight in terms of fast upload/download data speed, but the ROM and files you need are uploading and links will be posted here ASAP. For informational purposes, my partition dump is taken from a stock Android 6.0.1 Alcatel STREAK, Build No. A45UC50, Build Date: June 24, 2016; Security Patch Level June 1, 2016, Kernel Version: 3.10.49, and Baseband Version: MSM8909.12110.15W46. My ROM has been built from this firmware version as well.
Update: Link will be posted within the hour.
*** WARNING ***
Do NOT flash this on an H918, you will brick your phone.
This is for the AT&T H910 ONLY
Thanks to @toastyp for the dump of 10r.
Thanks to @askermk2000 for the kernel. Dude doesn't even have a V20 anymore, but he jumped in and helped when I lost my dev environment to build the kernel. That is what XDA is supposed to be about. Seriously man, huge thanks.
With that said, this is the v10r firmware + boot + system. For now, it is possible to dirty flash this, but if there are a lot of posts about problems, I will force a wipe in the zip since most people will be coming from 10m or even earlier (I think NATF is based on 10l, and I don't know what WETA is based on).
So, please, just backup your data and do a clean install
This is 100% stock v10r, bloat and all. It is ARB 0, so if you don't like it, you can go back to any older version.
This include v1.0 of the mk2000 kernel, please check his thread here for any updates.
Also, the 10r firmware doesn't work with 10m or lower system images -- 10p or 10q only. Since there are no custom ROMs currently that are based on 10p, 10q, or 10r, there is no reason to flash JUST the firmware without boot and system.
If you choose to dirty flash, then you MUST reinstall Magisk or SuperSU before rebooting. If you don't, then your data will be encrypted when the phone boots.
With the new firmware, the engineering aboot is able to init the screen correctly so the nasty warning message is clearly visible. This is the same warning as before, but it was garbled and you couldn't read it. Ignore it... your phone will boot.
Download here.
SHA: 5451146030393e490dcfba3558b620badefe75cd
-- Brian
Awesome work wi'll be trying this later
Awesome! Thank you!
runningnak3d said:
Thanks to @crackness for the dump of 10q before he rooted his device.
Thanks to @askermk2000 for the kernel. Dude doesn't even have a V20 anymore, but he jumped in and helped when I lost my dev environment to build the kernel. That is what XDA is supposed to be about. Seriously man, huge thanks.
With that said, this is the v10q firmware + boot + system. For now, it is possible to dirty flash this, but if there are a lot of posts about problems, I will force a wipe in the zip since most people will be coming from 10m or even earlier (I think NATF is based on 10l, and I don't know what WETA is based on).
So, please, just backup your data and do a clean install
This is 100% stock v10q, bloat and all. It is ARB 0, so if you don't like it, you can go back to any older version.
Also, the 10q firmware doesn't work with 10m or lower system images -- 10p or 10q only. Since there are no custom ROMs currently that are based on 10q, there is no reason to flash JUST the firmware without boot and system.
You will need to reinstall Magisk or SuperSU.
With the new firmware, the engineering aboot is able to init the screen correctly so the nasty warning message is clearly visible. This is the same warning as before, but it was garbled and you couldn't read it. Ignore it... your phone will boot.
Download here.
SHA: 6bbc1bc160baff3f44bd6b68b27b10324b0d087d
-- Brian
Click to expand...
Click to collapse
If I wanted to root, I could download this to my H91010q and go back to stock?
Apologies in advance if already obvious, but can someone on 10j or 10k flash this without first being on p or q?
The reason I ask is that you mentioned this "It is ARB 0, so if you don't like it, you can go back to any older version." and " 10q firmware doesn't work with 10m or lower system images -- 10p or 10q only."
My build number is NRD90M and my software version is H91810j.
I just want confirmation that this will work without me having to upgrade my firmware first.
Thanks for all your hard work!
@Jburd23 This does not root your phone. You flash this in TWRP if you are already rooted and want to upgrade to 10q.
@Quiksmage Yes, you can flash this no matter what version you are on. It includes system, so your current system will be wiped. It also contains the rest of the 10q firmware.
-- Brian
runningnak3d said:
@Jburd23 This does not root your phone. You flash this in TWRP if you are already rooted and want to upgrade to 10q.
@Quiksmage Yes, you can flash this no matter what version you are on. It includes system, so your current system will be wiped. It also contains the rest of the 10q firmware.
-- Brian
Click to expand...
Click to collapse
I should have also added the following. I can go back to a j based firmware after flashing this, correct?
It doesn't flash the modem/bootloader?
Sorry about the repeated questions, but I just want to be absolutely sure I don't end up in a place where I can't go back to the rootable firmware. Thanks
Nice to see some love for our v20, nice work.
Quiksmage said:
I should have also added the following. I can go back to a j based firmware after flashing this, correct?
Click to expand...
Click to collapse
Yes, you can revert to any older firmware. However, I don't know of any that was dumped. The H910 doesn't have a KDZ so the only way to get new (or older) firmware, is to have someone that hasn't rooted dump it.
If you are currently on 10j, then use the patched LG UP to dump your phone so that you will have a copy of the complete 10j firmware (minus an untouched system). At least that way you can flash back to it if you want. I only have dumps of 10m, 10p, and 10q. If you do dump your phone, please zip up the firmware and send it to me. You just need the files that are in this 10q zip.
It doesn't flash the modem/bootloader?
Click to expand...
Click to collapse
Yes it does. When a post says firmware + boot + system, the firmware is the bootloader, modem, hypervisor, trustzone, etc.... Boot is the kernel, and system is the actual Android install.[/quote]
Sorry about the repeated questions, but I just want to be absolutely sure I don't end up in a place where I can't go back to the rootable firmware. Thanks
Click to expand...
Click to collapse
Don't quite understand this question. You don't lose TWRP if you flash this, so you can root with Magisk again. Also, ALL H910 firmware is currently rootable. The H910 and the unlocked US996 are the last two V20s that can be rooted on the latest firmware.
-- Brian
Hey Brian, that was my fault. I thought I had read H918 v10q. The t-mobile variant cannot go back once updated past K. Apologies!
First post updated to 10r with mk2000 v1.0 kernel.
-- Brian
runningnak3d said:
Thanks to @toastyp for the dump of 10r.
Thanks to @askermk2000 for the kernel. Dude doesn't even have a V20 anymore, but he jumped in and helped when I lost my dev environment to build the kernel. That is what XDA is supposed to be about. Seriously man, huge thanks.
With that said, this is the v10r firmware + boot + system. For now, it is possible to dirty flash this, but if there are a lot of posts about problems, I will force a wipe in the zip since most people will be coming from 10m or even earlier (I think NATF is based on 10l, and I don't know what WETA is based on).
So, please, just backup your data and do a clean install
This is 100% stock v10r, bloat and all. It is ARB 0, so if you don't like it, you can go back to any older version.
Also, the 10r firmware doesn't work with 10m or lower system images -- 10p or 10q only. Since there are no custom ROMs currently that are based on 10p, 10q, or 10r, there is no reason to flash JUST the firmware without boot and system.
You will need to reinstall Magisk or SuperSU.
With the new firmware, the engineering aboot is able to init the screen correctly so the nasty warning message is clearly visible. This is the same warning as before, but it was garbled and you couldn't read it. Ignore it... your phone will boot.
Download here.
SHA: 5451146030393e490dcfba3558b620badefe75cd
-- Brian
Click to expand...
Click to collapse
You should really put a device check in the updater-script.... I couldve sworn this said H918 (8 and 0 look VERY similar on mobile), flashed it, full hard-bricked it.....
Qualcomm HS-USB QDLoader 9008
RIP
Tiny line in updater-script would have prevented this
Tilde88 said:
You should really put a device check in the updater-script.... I couldve sworn this said H918 (8 and 0 look VERY similar on mobile), flashed it, full hard-bricked it.....
Qualcomm HS-USB QDLoader 9008
RIP
Tiny line in updater-script would have prevented this
Click to expand...
Click to collapse
As much as I like and appreciate your work, you screwed up dude lol its ok to admit it
Sent from my LG-H910 using Tapatalk
@Tilde88 I did use an assert line at first, but I got tired of having to keep editing it and adding additional checks.
H910 || US996 || H915 || elsa || H910a
I am pretty sure that covers all the possibilities now, so I should probably put it back -- but at the end of the day, just have to be careful.
I could understand misreading the H910 on the forum post, but the zip file as well? That is an awful lot of seeing 8 instead of 0.....
I am sorry you toasted your device. Even if you bought it used, as long as it is still under the 2 year warranty, LG will fix it.
I am updating the first post with a big red warning....
-- Brian
runningnak3d said:
@Tilde88 I did use an assert line at first, but I got tired of having to keep editing it and adding additional checks.
H910 || US996 || H915 || elsa || H910a
I am pretty sure that covers all the possibilities now, so I should probably put it back -- but at the end of the day, just have to be careful.
I could understand misreading the H910 on the forum post, but the zip file as well? That is an awful lot of seeing 8 instead of 0.....
I am sorry you toasted your device. Even if you bought it used, as long as it is still under the 2 year warranty, LG will fix it.
I am updating the first post with a big red warning....
-- Brian
Click to expand...
Click to collapse
Lol I don't blame you at all. I flashed it, I did it. It will get repaired and I have other phones, so not a big deal. I meant it mostly for others. 2nd phone I brick in 10 years (other one was the HTC touch pro2 back in windows mobile days). I just hope there will be root for 10q in a few weeks, BC I'm sure lg will send a refurb with that.
As for the recovery, I saw the file and just flashed, who needs to read anyway lmao. /s
Anyway, thanks for your work. It flashed beautifully, and its a great way to update
Ok flashed and running decent. But twrp asked for encrypt password. Wasnt encrypted. I can get past it but its showing 0mb for internal storage. Anyone else get this? Any idea how to fix it? I flashed supersu but it wont install I'm thinking because of this error.
You flashed SuperSU before rebooting or after?
-- Brian
runningnak3d said:
You flashed SuperSU before rebooting or after?
-- Brian
Click to expand...
Click to collapse
The initial reboot? After. I went through setup and got everything done. Went back into twrp. Asked for a password to decrypt. I can hit cancel to get past it. Flashed supersu. Rebooted. No su app or root. I'm guessing because twrp thinks data is encrypted.
TWRP thinks your data is encrypted because it IS encrypted. If you don't flash SuperSU or Magisk before rebooting, then /data gets encrypted on the first boot. Now that it is encrypted, the only way to fix it is to format data in TWRP.
There is no way for you to back it up now either.
-- Brian
runningnak3d said:
TWRP thinks your data is encrypted because it IS encrypted. If you don't flash SuperSU or Magisk before rebooting, then /data gets encrypted on the first boot. Now that it is encrypted, the only way to fix it is to format data in TWRP.
There is no way for you to back it up now either.
-- Brian
Click to expand...
Click to collapse
Eh a wipe/format isnt the end of the world. Save my pics onto external and do it. Thanks for the help man and for the Rom. She is smooth. Btw I saw you thank askermk2000 for the kernel. Is that the same one as in a thread of its own? I was thinking of flashing his updated 1.1 version but if its the same I wont bother. Thanka again.
Consider one day you upset the devil and your phone is bricked by him, lets try to revive the phone from hell (at your own risk) :
Link to the OTA firmware's :
Click here for the links page
Important tools links:
[TOOL] Huawei Multi-Tool v8 by Team MT by inside!out
TWRP Honor 7X img
Stage 1
Download from here everything you need for the procedure - Download Folder Link
I am testing it on my BND-L21 firmware from BND-AL10
Downloading firmware (from topic). Full firmware must be more than 1.5Gb, all smaller is just
OTA Updates to the system.
After that we must download Huawei-MultiTool (future MT) version 8.x.x (link topic)
and downloading custom recovery. We will use TWRP for Honor7x (link topic)
Last we must prepare OTG Cable, SD Card more than 4Gb. On first stage that's all.
Stage 2
Go to MT and reboot phone to Fastboot mode (while phone off, hold "Volume -" and power)
If you did all correctly, you will see in the down right side your number and "Fastboot".
Now go in MT to the Bootloader and check the status. If you have already unlocked, skip this.
If you have locked phone, you must have IMEI and Huawei account. (if not please unlock your bootloader via the Huawei site)
After that, go to Recovery menu and choose our TWRP image in "Custom recovery" section and
type "Recovery". IMPORTANT!!! DON'T FLASH ERECOVERY, I DON'T HAVE THIS IMAGE!!!
After flashing recovery, we must turn off our phone.
Now we must to prepare base system image. In archive we have UPDATE.ZIP file. extract this
file to custom folder and open "Unbrick" in MT and choose "extractor". Open our file in extractor
and click right mouse key on empty space, choose extract all... and choose custom folder to
extracting.
Go to the folder and copy file VENDOR.IMG to the SD-Card (or USB with OTG). Turn on your
device in Recovery mode (Volume + and power), choose Wipe and Wipe ALL partitions! After
doing this, go to Install and choose "Install img", go to the SD-Card, and install VENDOR.img to
VENDOR folder (Important!)
After installing reboot phone again to Fastboot mode and connect to PC.
Now we must download .zip update to your region. We need this for using LTE (4G) in your country + Localization.
After downloading open .zip archive with our CUST file. archive must be called update_BND-
YOUR-NUMBER_hw_YOUR- COUNTRY.zip
From this archive we must extract .img file from root folder. It can be called cust.img CUST.img
version.img etc.
if name different from CUST.img rename it and put to the extracted UPDATE.app folder.
Last Stage 3
In MT go to Unbrick, choose our unpacked system with our CUST file and we must have at least
4/5 checkbox. And just type "UNBRICK" and wait. NOTICE: at moment of extracting system.img
it will be about 10-15 minutes. It's not a freezing of PC)
After good installing in log you will see like "All ok" Just reboot phone and you will see low level
factory reset, or something else like formatting. After formatting phone will reboot to the system.
That's all
Flashing Gapps method coming soon...
Password - 4pda for the update_full_bnd-AL10... Zip
Special Thanks to Kallibr44 my friend who helped me decipher everything. :highfive:
HIT THANKS IF I HELPED YOU IT MAKES ME HAPPY
We need a Full Firmware Package for L21,this is only Ota Updates.
letschky said:
We need a Full Firmware Package for L21,this is only Ota Updates.
Click to expand...
Click to collapse
there is a procedure used by EU users to completely revive the phone using the OTA but the procedure is too long which i haven't tried yet and is completely for users who have dead phones for now and yes obviously there is no official firmware available for Honor 7x but the user from an EU forum revived his phone so it is possible from the images.
though i made this thread for users who want to update their firmwares and not the procedure to flash a stock firmware since there is not one available yet but i can point to the thread where this user posted the procedure if someone wants to try. PM me
sid21 said:
i can point to the thread where this user posted the procedure if someone wants to try. PM me
Click to expand...
Click to collapse
Yes please....
fmotta said:
Yes please....
Click to expand...
Click to collapse
Sent reply.
There are teams who have unlocked a lot of stuff like flashing international FW,
flashing gapps on chinese fw, Automatic Call Recording, restoring the phone.
so i am in contact with them to make our phone better. lets keep our fingers crossed. :fingers-crossed:
i am waiting for firmware flashing to get it translated from one of the users.
This is the full recovery package right? Atleast for the Indian version?
TheDj408 said:
This is the full recovery package right? Atleast for the Indian version?
Click to expand...
Click to collapse
They arent recovery packages. they are full OTA which can be flashed for updating.
but there is a process to compile them into making them stock firmware packages but due to the long procedure i didnt post it here. rather wait for official stock firmware package.
sid21 said:
Hello Honor 7X Users, turns out there is firmware available for flashing for the AL10 and L21 variants
but i haven't tried them out and can post the procedure if someone needs it but all credit goes to PRO-TEAMMT for releasing them for us so now if we mess up we got official firmware's latest available to go back to.
I personally haven't tested any but i soon will.
Link to the firmware's :
Click here for the links page
Important tools :
[TOOL] Huawei Multi-Tool v8 by Team MT by inside!out
TWRP Honor 7X img
Steps : (Considering you have unlocked bootloader and flashed twrp)
1. Download the appropriate firmware as per your model (Link to the website given)
2. Clear Cache
3. Flash the firmware file
(Wait for the complete process to flash a firmware from scratch so that i can do it and confirm myself but if anybody tests before me let me know)
Refer to the thread by inside!out for any help till them if you want to try out
Click to expand...
Click to collapse
Hi
I am a New in Android world
I have honor 7x BND L21c185b101
And i rooted
Know exactly do this?
Step 3 how?
And the multi tool For what?
sid21 said:
there is a procedure used by EU users to completely revive the phone using the OTA but the procedure is too long which i haven't tried yet and is completely for users who have dead phones for now and yes obviously there is no official firmware available for Honor 7x but the user from an EU forum revived his phone so it is possible from the images.
though i made this thread for users who want to update their firmwares and not the procedure to flash a stock firmware since there is not one available yet but i can point to the thread where this user posted the procedure if someone wants to try. PM me
Click to expand...
Click to collapse
Can I have the procedure link?
I ordered a 7X from AliExpress.
I also own an Honor 5X & errrmmmm.. I'm not a developer rather still a learning buildbot ? still I want to take part in bringing up LOS or AOSP for Honor 7X. So we can work on it together if you want. ?
Cheers!
P.S. Belated Merry Christmas.
tootysa said:
Hi
I am a New in Android world
I have honor 7x BND L21c185b101
And i rooted
Know exactly do this?
Step 3 how?
And the multi tool For what?
Click to expand...
Click to collapse
exactly what you want to do?
this is to update to the latest firmware. if you have the latest firmware you dont need it.
the multi tool is used to flash stock with a procedure which is only needed to return to stock or else theres no need for it for the most part..
mumith3 said:
Can I have the procedure link?
I ordered a 7X from AliExpress.
I also own an Honor 5X & errrmmmm.. I'm not a developer rather still a learning buildbot ? still I want to take part in bringing up LOS or AOSP for Honor 7X. So we can work on it together if you want.
Cheers!
P.S. Belated Merry Christmas.
Click to expand...
Click to collapse
PM Sent kindly check.
sid21 said:
Hello Honor 7X Users, turns out there is firmware available for flashing for the AL10 and L21 variants
but i haven't tried them out and can post the procedure if someone needs it but all credit goes to PRO-TEAMMT for releasing them for us so now if we mess up we got official firmware's latest available to go back to.
I personally haven't tested any but i soon will.
Link to the firmware's :
Click here for the links page
Important tools :
[TOOL] Huawei Multi-Tool v8 by Team MT by inside!out
TWRP Honor 7X img
Steps : (Considering you have unlocked bootloader and flashed twrp)
1. Download the appropriate firmware as per your model (Link to the website given)
2. Clear Cache
3. Flash the firmware file
(Wait for the complete process to flash a firmware from scratch so that i can do it and confirm myself but if anybody tests before me let me know)
Refer to the thread by inside!out for any help till them if you want to try out
Click to expand...
Click to collapse
HI I wanna know many things:
1-if I can constantly update the 7x with the application (or the software on PC, is the same) "Firmware Finder" even if I don't recive the official OTAs (because I want to root my device)
2-if its possible upgrade the system via OTA (or Firmware finder etc...) when the device is rooted
3-is dangerous root the Honor 7x?
4-if I can upgrade the system when the device Is rooted via the software HiSuite
5- how/where can I do/find and restore a Nandroid Backup for my phone
6-where I can find a local/manual update (UPDATE. APP) for the 7x (in case a brick the phone)
7-how can i UNBRICK my phone I case of brick
(sorry for my bad english?)
PLEASE HELP ME??
Thanks
Lambo™ said:
HI I wanna know many things:
1-if I can constantly update the 7x with the application (or the software on PC, is the same) "Firmware Finder" even if I don't recive the official OTAs (because I want to root my device)
2-if its possible upgrade the system via OTA (or Firmware finder etc...) when the device is rooted
3-is dangerous root the Honor 7x?
4-if I can upgrade the system when the device Is rooted via the software HiSuite
5- how/where can I do/find and restore a Nandroid Backup for my phone
6-where I can find a local/manual update (UPDATE. APP) for the 7x (in case a brick the phone)
7-how can i UNBRICK my phone I case of brick
(sorry for my bad english?)
PLEASE HELP ME??
Thanks
Click to expand...
Click to collapse
1) ???
2) Not sure there is always a chance of bricking
3) Yes, if you don't know what you're doing. No if you're not going to be flashing anything.
4) You should be able to and also refer to #1.
5) None available
6) None available
7) You can't, no stock image released = no procedures to unbrick
Soapy! said:
1) ???
2) Not sure there is always a chance of bricking
3) Yes, if you don't know what you're doing. No if you're not going to be flashing anything.
4) You should be able to.
5) None available
6) None available
7) You can't, no stock image released = no procedures to unrbcik
Click to expand...
Click to collapse
1- can i upgrade the system at every update (when the device is rooted) with Firmware finder many times even if I don't recive the notification on the phone of the update (or if the device updater cannot find it)?
2-ok but if do all right steps you cannot brick the phone, no?
3-ok i only wanna unlock bootloader, flash twrp and root the phone. If I do all right steps there are no risks, no?
4-i don't understand it (in hisuite there s the option that says "Update device". With the device rooted can I update the phone with this software?)
5-ok but can I do one with a custom recovery, no?
6-ok so we just have to wait, no?
7-ok. Same thing of the - 6 (we have to wait for the UPDATE.APP for the 7x to be able to UNBRICK the phone in case it could happen, no?)
Sorry for my bad English and thanks for the answers?
Lambo™ said:
HI I wanna know many things:
1-if I can constantly update the 7x with the application (or the software on PC, is the same) "Firmware Finder" even if I don't recive the official OTAs (because I want to root my device)
2-if its possible upgrade the system via OTA (or Firmware finder etc...) when the device is rooted
3-is dangerous root the Honor 7x?
4-if I can upgrade the system when the device Is rooted via the software HiSuite
5- how/where can I do/find and restore a Nandroid Backup for my phone
6-where I can find a local/manual update (UPDATE. APP) for the 7x (in case a brick the phone)
7-how can i UNBRICK my phone I case of brick
(sorry for my bad english)
PLEASE HELP ME
Thanks
Click to expand...
Click to collapse
1. yes you can if the app supported honor 7x with their firmware but it doesn't yet, use twrp
2. yes you can upgrade via flashing it in twrp
3. unlocking bootloader itself is dangerous let alone rooting since your waranty is gone since there is still no sign of official stock firmware
4. same as no. 1 ans
5. if u flashed twrp you can do your nandroid backup which can be later restored anytime so it will be obv on the phone at that time
6. manual or local update? in the op main post i guess? by opening the link?
7. Still no official firmware and the procedure i am aware of consists of turning the official chinese firmware into normal by changing settings and stuff which is a long procedure so probably if u brick, u r stuck until honor decides to release stock firmware
by the looks i guess you have no clue about phone flashing, its better you dont try anything until there are guides properly made for newbies. :silly:
sid21 said:
1. yes you can if the app supported honor 7x with their firmware but it doesn't yet, use twrp
2. yes you can upgrade via flashing it in twrp
3. unlocking bootloader itself is dangerous let alone rooting since your waranty is gone [emoji14] since there is still no sign of official stock firmware
4. same as no. 1 ans
5. if u flashed twrp you can do your nandroid backup which can be later restored anytime so it will be obv on the phone at that time
6. manual or local update? in the op main post i guess? by opening the link?
7. Still no official firmware and the procedure i am aware of consists of turning the official chinese firmware into normal by changing settings and stuff which is a long procedure so probably if u brick, u r stuck until honor decides to release stock firmware
by the looks i guess you have no clue about phone flashing, its better you dont try anything until there are guides properly made for newbies. :silly:
Click to expand...
Click to collapse
Thanks lol [emoji23]
Sent from my BND-L24 using Tapatalk
I rooted my 7X(Al10) version successfully but while performing the reset, deleted the system file also by mistake. There is no TWRP backup. Is there any way to get the stock OS files again to flash in TWRP ? Or does anyone have a backup file they made that they can share? I tried Huawei e-recovery too, but that gets stuck at 'unable to get package info'. The people at the service centre can't think of any other method to restore the phone, except changing the motherboard. When is the official stock file expected to be available?
GC95 said:
I rooted my 7X(Al10) version successfully but while performing the reset, deleted the system file also by mistake. There is no TWRP backup. Is there any way to get the stock OS files again to flash in TWRP ? Or does anyone have a backup file they made that they can share? I tried Huawei e-recovery too, but that gets stuck at 'unable to get package info'. The people at the service centre can't think of any other method to restore the phone, except changing the motherboard. When is the official stock file expected to be available?
Click to expand...
Click to collapse
I have a TWRP backup not sure if it'll work, https://drive.google.com/file/d/1EntdgNwcJSOTZizqt_W-yWfkd3-YVmCm/view?usp=drivesdk
It's a zip file with 2 backup folder, one with boot and system and one with vendor
Edit: pls thank if it worked, so I have an indicator of the effectiveness
GC95 said:
I rooted my 7X(Al10) version successfully but while performing the reset, deleted the system file also by mistake. There is no TWRP backup. Is there any way to get the stock OS files again to flash in TWRP ? Or does anyone have a backup file they made that they can share? I tried Huawei e-recovery too, but that gets stuck at 'unable to get package info'. The people at the service centre can't think of any other method to restore the phone, except changing the motherboard. When is the official stock file expected to be available?
Click to expand...
Click to collapse
I am waitinig for the official stock file since two weeks now, because I deleted accidently the OS from my phone -_-
I think we can wait several weeks again...
---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------
Jan.Pul said:
I have a TWRP backup not sure if it'll work, https://drive.google.com/file/d/1EntdgNwcJSOTZizqt_W-yWfkd3-YVmCm/view?usp=drivesdk
It's a zip file with 2 backup folder, one with boot and system and one with vendor
Click to expand...
Click to collapse
Thanks! I will try on my bricked phone
sid21 said:
1. yes you can if the app supported honor 7x with their firmware but it doesn't yet, use twrp
2. yes you can upgrade via flashing it in twrp
3. unlocking bootloader itself is dangerous let alone rooting since your waranty is gone since there is still no sign of official stock firmware
4. same as no. 1 ans
5. if u flashed twrp you can do your nandroid backup which can be later restored anytime so it will be obv on the phone at that time
6. manual or local update? in the op main post i guess? by opening the link?
7. Still no official firmware and the procedure i am aware of consists of turning the official chinese firmware into normal by changing settings and stuff which is a long procedure so probably if u brick, u r stuck until honor decides to release stock firmware
by the looks i guess you have no clue about phone flashing, its better you dont try anything until there are guides properly made for newbies. :silly:
Click to expand...
Click to collapse
1. In the app firmware finder there are firmwares for the phone but how can I flash a official firmware (OTA I mean) if there are no one (or how can I flash a firmware finder Update)?
2. Same thing in -1 (I mean)
3. Ok. Now we have to wait the official stock firmware, no? (i don't understand this answer, please write it in another way)
4. I don't understand it
5. Okok (obv? Sorry I'm Italian hahaha)
6. It's not the same thing local or manual? Write it in another way please hahaha google translate doesnt help me?
7. Okok, So if I don't use your method I only have to wait that honor release the official stock firmware (UPDATE. APP). And for greater security it's better wait it before to root and unlock bootloader etc, no?
Anyway, I have an idea of what flashing is, in fact every device I have (they are all Samsung, so that's why I'm disoriented) is completely modified. The fact is that I dont have much experience (I'm 14 years old) with non-Samsung devices, in fact my honor 7x I received for Christmas and for the hurry and the want to modify it, I would like to know all these things.
Thank you
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
k0pernicus said:
I am waitinig for the official stock file since two weeks now, because I deleted accidently the OS from my phone -_-
I think we can wait several weeks again...
---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------
Thanks! I will try on my bricked phone
Click to expand...
Click to collapse
OK thanks I'll keep it aside in case of brick
I would recommend everyone to not do experiments over your phone to try and root and flash random stuff..
they only have official chinese firmware for flashing so its better to wait for the official firmware for non chinese version.
the method which i know of to flash on the phone is for people with flashing knowledge cz the procedure is not simple and secondly even i have been flashing my phone for many years on various devices yet i havent got the guts to root this first honor device cz their partitions are different and somewhat secured so dont play with it.
wait for the official firmware for your respective devices. maybe they will straightaway launch the oreo firmware.
READ THE WHOLE THREAD BEFORE CONTINUING or FLASHING THE ZIP ! AS THIS ONLY WORKS DESCENT FOR G VERSION , I ONLY RECOMMEND TO DO SO ! USING IT ON A U-VERSION (B19/B25) MIGHT BRICK YOUR PHONE. ALSO TESTED & WORKING ON Project New World (Oreo) on G VERSION
I am not responsible for damaging/bricking your phone or other related stuff…DO MAKE A FULL BACKUP !
ONLY FOR A2017G & also on A2017G B32 Oreo PNW
DON'T USE ON B13 (MF5.0) BECAUSE IT DOES NOT WORK !!! Tested it myself.
Only to use whether flashed Universal B15 (or B32 on PNW) or Stock Bootloaders before.
Don't use on encrypted phones and remove security pattern before flash
Always backup your data. In case you have to format data you'll have a spare one to restore
EDIT : made a flashable zip : Remove Bootloader Unlock Warning on Axon 7G : https://androidfilehost.com/?fid=745849072291698596
As @Choose an username... asked to bring this to your attention again hereby a fairly easy and safe method to get rid of that annoying "unlocked bootloader" warning.
I did mentioned this before in the earlier days but perhaps its usefull to post it again. And if you're planning to stay a while on your rom this might help to have a clean boot.
I performed this steps often on my G and imo are safe to do.
So, take a look HERE
Prepare with necessary files (if you already haven't from before )
( Be on twrp 3.1.1.0 (3.2.1.0) )
Just perform steps 6 to 14 again (NOTE ! : If you get a permissions denied issue, try doing these steps while your device is in TWRP )
After that just type "fastboot reboot" and you should have a clean boot.
-------------------------------------------------
B) Unlock the bootloader
Q: Why do I need to unlock the bootloader?
A: With an unlocked bootloader, you can install custom ROMs.
1) Go to https://mega.nz/#F!rcFCQZ7C!vn457hU1zDwc0uVpvm5otw and download the aboot.img file from there (1024Kb). Put it in the same folder you used in the previous process
2) Download this file: https://www.androidfilehost.com/?fid=529152257862665656
3) Unzip the file and copy/cut the file called "fastboot_unlock.img"
4) Paste that file in the folder where "adb.exe", "axon7tool.exe", "recovery.img", "recovery.bin" and "aboot.img" are located
5) If there's none open, open a new command window in that folder again (Shift + right-click and "open command window here")
6) Type "adb push aboot.img /sdcard/" and hit enter
7) Type "adb push fastboot_unlock.img /sdcard/" and hit enter
8) Type "adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img" and hit enter
9) Type "adb shell dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot_lock.img" and hit enter
10) Type "adb pull /sdcard/fbop_lock.img" and hit enter
11) Type "adb pull /sdcard/aboot_lock.img" and hit enter
12) Type "adb shell dd if=/sdcard/fastboot_unlock.img of=/dev/block/bootdevice/by-name/fbop" and hit enter
13) Type "adb shell dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot" and hit enter
14) Type "Adb reboot bootloader" and hit enter to go to the bootloader
-------------------------------------------------
Thanks @Controllerboy
Can we not create flashable ZIPs for this to save Time? Something with AROMA to choose the Specific Device Files would be cool or nah? Let Me know if there is interest on this. I could help with the Scripts...
BR
Miustone said:
Can we not create flashable ZIPs for this to save Time? Something with AROMA to choose the Specific Device Files would be cool or nah? Let Me know if there is interest on this. I could help with the Scripts...
BR
Click to expand...
Click to collapse
Thnx for your reply.
But AFAIK this procedure might not work on the U version but not sure ( afaik no go on A2017). So therefore i just used the "known" familiar bootloader files.
But if it would work, so someone should test their specific files on U version, an AROMA zip would be interesting to make.
I can i you want but feel free to join in if A2017U and A2017 or good to go :good:
But then again we have to get some feedback on this.
raystef66 said:
Thnx for your reply.
But AFAIK this procedure might not work on the U version but not sure ( afaik no go on A2017). So therefore i just used the "known" familiar bootloader files.
But if it would work, so someone should test their specific files on U version, an AROMA zip would be interesting to make.
I can i you want but feel free to join in if A2017U and A2017 or good to go :good:
But then again we have to get some feedback on this.
Click to expand...
Click to collapse
First of all a happy new Year! :angel:
Think i will take a look on it in the next Days, would be cool if someone could test which Variants are supporting this. I see a flashable ZIP could be very useful for People who are switching the OS a lot of times (like i do). I own the G Version BTW.
BR
At the boot hold the Vol-Button and Power. And now you cant see the Bootloader-Message. Otherwise flash this zip: http://www120.zippyshare.com/v/xYBio6uW/file.html
I dont know if its work on the A2017U oder A2017 Devices. But it works definitely on the A2017G.
Miustone said:
First of all a happy new Year! :angel:
Think i will take a look on it in the next Days, would be cool if someone could test which Variants are supporting this. I see a flashable ZIP could be very useful for People who are switching the OS a lot of times (like i do). I own the G Version BTW.
BR
Click to expand...
Click to collapse
Happy new Year too and best wishes to all here on XDA !
Yeah such a zip for all variants should be handy. A A2017U user should test this method.
Anyway on G it works.
BaamAlex said:
At the boot hold the Vol-Button and Power. And now you cant see the Bootloader-Message. Otherwise flash this zip: http://www120.zippyshare.com/v/xYBio6uW/file.html
I dont know if its work on the A2017U oder A2017 Devices. But it works definitely on the A2017G.
Click to expand...
Click to collapse
This zip works on G version (not sure about other versions) but only when coming from Universal BL imo. When using the B13 bootstack f.e. like on Mifavor 5.0 this ZIP would not work imo. So be carefull flashing it. As said, when on Universal BL this should work.
Thanks !
BaamAlex said:
At the boot hold the Vol-Button and Power. And now you cant see the Bootloader-Message. Otherwise flash this zip: http://www120.zippyshare.com/v/xYBio6uW/file.html
I dont know if its work on the A2017U oder A2017 Devices. But it works definitely on the A2017G.
Click to expand...
Click to collapse
And if i have stock B08/B09 bootloader, not the universal BL?
I cant say that. It works under a2017g. But...you can test it. And say me if its work for the a2017u or a2017. But i cant guarantee for anything. Sry.
Okay then in another way: which bootloader was installed before you flashed your linked zip?
I messed up my phone completely one time with this "removal" from the first thread a few month ago.
So a wanna get sure this works with stock bootloader and not only the universal bootloader.
I also have the A2017G.
Spillunke said:
Okay then in another way: which bootloader was installed before you flashed your linked zip?
I messed up my phone completely one time with this "removal" from the first thread a few month ago.
So a wanna get sure this works with stock bootloader and not only the universal bootloader.
I also have the A2017G.
Click to expand...
Click to collapse
If you're not sure about the zip he provided, just don't use it
Do the above steps in 1st post and you'll be good to go. It takes only a minute or so, just copy paste in adb
Tip : just boot your phone in twrp before you do the steps. So you'll be sure about permissions
Spillunke said:
Okay then in another way: which bootloader was installed before you flashed your linked zip?
I messed up my phone completely one time with this "removal" from the first thread a few month ago.
So a wanna get sure this works with stock bootloader and not only the universal bootloader.
I also have the A2017G.
Click to expand...
Click to collapse
Better use @raystef66 method to remove the message.
Owning a A2017G isn't the only prerequisite to flash this file; like already said it depends on bootloader version, device encryption and probably much more ...
As you said, flashing this sort of stuff is too hasardous. Just take a look at the thread concerning this remover; lot of users "bricked" their devices with this stuff.
Pff
Spillunke said:
Hi all,
we need a person to test the tool, which removes the unlocked bootloader screen.
It do what it should do, but main problem is the question, if the adb.exe, which is included, is working in this case.
Axon 7 2017G on nougat with unlocked BL info-screen and a windows pc without ADB are the only requirements.
Download the file and give a feedback pls.
Click to expand...
Click to collapse
Why can't this be made via a flashable zip? It would be much easier to use and you wouldn't have to rely on Windows behaving.
The only thing needed would be to test if ro.product.model=ZTE A2017G, I don't know if you can read from build.prop with a flashable zip but if possible that would be the best approach. That would be to test if your phone is actually a G, minimize problems. Also, if you have the Universal Bootloader all this would do is restore fastboot; it wouldn't brick a G with univ bl (Someone made a flashable zip with an old aboot a while back actually. It was meant for getting fastboot back. I think it doesn't work though).
Choose an username... said:
Why can't this be made via a flashable zip? It would be much easier to use and you wouldn't have to rely on Windows behaving.
The only thing needed would be to test if ro.product.model=ZTE A2017G, I don't know if you can read from build.prop with a flashable zip but if possible that would be the best approach. That would be to test if your phone is actually a G, minimize problems. Also, if you have the Universal Bootloader all this would do is restore fastboot; it wouldn't brick a G with univ bl (Someone made a flashable zip with an old aboot a while back actually. It was meant for getting fastboot back. I think it doesn't work though).
Click to expand...
Click to collapse
It's indeed better to make an aroma zip for all devices. I'm actually looking into that right now. Hopefully with success. Come back to you when working on G in the first place.
A2017G & A2017U Remove Bootloader Unlock Warning
As the aboot and fastboot_unlock (from controllerboy thread) are the same in G & U (correct me if i'm wrong) this can be used on both models.
I've tested on my G and works flawless. Perhaps a U-user can test it out.
Remove Bootloader Unlock Warning on Axon 7G & U : https://androidfilehost.com/?fid=745849072291698596
it work but after reboot it dose not accept pattern password !
am2006 said:
it work but after reboot it dose not accept pattern password !
Click to expand...
Click to collapse
On my G it does. Pin, pattern.... No problem there.
Hmm, maybe coz am on LOS rom
am2006 said:
Hmm, maybe coz am on LOS rom
Click to expand...
Click to collapse
Don't think so because you used the universal B15 I suppose? Did those tests coming from that universal.
Can you not pattern afterwards?
Having a A2017U?
raystef66 said:
Don't think so because you used the universal B15 I suppose? Did those tests coming from that universal.
Can you not pattern afterwards?
Having a A2017U?
Click to expand...
Click to collapse
i use universal, my is A2017G, i do factory reset its work fine now
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.