For those who are interested : A2017G V1.2.0B05
( link Spain : http://www.ztedevice.com/support/detail?id=1170789A90BA42E18B3364B80C7F5A26 )
Faster link : https://www.androidfilehost.com/?fid=889764386195912222
Like someone posted, Poland is getting the B05 too. Perhaps other countries will follow.
AFAIK : ZTE Germany mentioned a new security patch ( also future new security patches would be implemented), also the problem which was on Vodafone LTE is probably confirmed to be gone (german users could confirm this here when tested)
Will upload it to the DownloadCenter ( AndroidFileHost )
Perhaps @tron1 can make a flashable zip
Interesting.
I'm curious what ZTE bring to this update.
Sent from my iPad using Tapatalk
Is it a full rom or an incremental update?
wineds said:
Is it a full rom or an incremental update?
Click to expand...
Click to collapse
A full ROM ( a little bigger than the B04 ) - i'm uploading it to my AFH because ZTE server is sloooooooowwww
Imo, stock users could update this B05 on any G-version without a problem (rename to update.zip...you know by now....)
No changelog provided ( AFAIK )
Just updated.
Well the only very visible change compared to B04 is the upgrade of Google security patches to 1st of June.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also noticed with first boot changed the default from Nova Prime to Launcher 3 witch immediately switched again to Nova.
No other changes so far.
Sent from my iPad using Tapatalk
paatha13 said:
Just updated.
Well the only very visible change compared to B04 is the upgrade of Google security patches to 1st of June.
View attachment 4196625
Also noticed with first boot changed the default from Nova Prime to Launcher 3 witch immediately switched again to Nova.
No other changes so far.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Post back if you see anything new please.
I've installed it now and done a full reset. I'm really hoping battery life will be like B02 (7.1.1). With B04, battery life took a serious hit for me, even after resets.
I'm a bit disappointed that MiFavor 5.0 was not included. Hopefully it'll come soon.
It is quite snappy, but I'm not sure that it is more so than B04. I'm wondering if the finger print sensor is working a bit better or not. Could just be my imagination. Time will tell.
I'll report back if I notice anything special.
There are no official changelog?
I think this is a very good update. Cell reception has improved a lot. Phone feels and is much snappier. I've taken couple of shots with the camera and focusing is better and faster.
nfsmw_gr said:
Post back if you see anything new please.
Click to expand...
Click to collapse
Night light with scheduling. Noooooooice!
Any TWRP zip yet?
im still on b02, and phone says software is up to date.. dont even have b04.. i wonder if b05 will appear anytime soon?
OTA link please
ГАСООП said:
im still on b02, and phone says software is up to date.. dont even have b04.. i wonder if b05 will appear anytime soon?
Click to expand...
Click to collapse
Probably better if you just force the update yourself. OTA updates have been pretty hit and miss for a while now.
Laleka said:
OTA link please
Click to expand...
Click to collapse
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Everything can be found in this thread
raystef66 said:
For those who are interested : A2017G V1.2.0B05
...
Perhaps @tron1 can make a flashable zip
Click to expand...
Click to collapse
@raystef66
I too asked tron1 for TWRP flashable B05 version without answer yet (https://forum.xda-developers.com/showpost.php?p=72851004&postcount=95).
Since you have Android file host account, may I suggest you to build them by yourself and put them in your download center ?
Following is the procedure I found to build TWRP flashable version from full ROM ("update.zip") :
full ROM from ZTE = update.zip (27 files) = (tron1's bootstack (20 files) + tron1's stock system (4 files)+ recovery.img + fastboot.img + emmc_appsboot.mbn)
recovery.img is the stock recovery from full ROM
TWRP flashable ROM (bootstack + stock system) does not include recovery.img, this explains why TWRP is preserved and not overridden by stock recovery,
and so TWRP can be used to flash TWRP flashable-ROM. fastboot.img and emmc_appsboot.mbn are not included too, so the boot loader (usually unlocked) is untouched.
To build TWRP flashable ROM files:
ZTE_A2017GV1.2.0B05_BootStack_by_raystef66.zip
ZTE_A2017GV1.2.0B05_Stock_System_by_raystef66.zip
- copy ZTE_A2017GV1.2.0B04_BootStack_by_tron1.zip to ZTE_A2017GV1.2.0B05_BootStack_by_raystef66.zip
- copy ZTE_A2017GV1.2.0B04_Stock_System_by_tron1.zip to ZTE_A2017GV1.2.0B05_Stock_System_by_raystef66.zip
- open ZTE_A2017GV1.2.0B05_BootStack_by_raystef66.zip (with TotalCommander, or WinRAR etc...) and replace all the files (20 files)
(except META-INF directory) by their equivalent taken from update.zip.
- open ZTE_A2017GV1.2.0B05_Stock_System_by_raystef66.zip (with TotalCommander, or WinRAR etc...) and replace all the files (4 files)
(except META-INF directory) by their equivalent taken from update.zip.
- in ZTE_A2017GV1.2.0B05_BootStack_by_raystef66.zip, change \META-INF\com\google\android\updater-script content to reflect B05 and the author
ui_print("----------------------------------------");
ui_print("ZTE A2017G V1.2.0B05 Bootstack & Modem");
ui_print("----------- Nougat 7.1.1 -----------");
ui_print("---------- Provided by tron1/raystef66 ----------");
ui_print("----------------------------------------");
- in ZTE_A2017GV1.2.0B05_Stock_System_by_raystef66.zip, change \META-INF\com\google\android\updater-script content to reflect B05 and the author
ui_print("----------------------------------------");
ui_print("ZTE A2017G V1.2.0B05 System & Boot image");
ui_print("----------- Nougat 7.1.1 -----------");
ui_print("-------- Provided by tron1/raystef66 ---------");
ui_print("----------------------------------------");
- upload the 2 files to Android file host
jopomopo said:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Everything can be found in this thread
Click to expand...
Click to collapse
I need small package link from bo4 to B05 there is link to 2gb file...
dnlilas said:
@raystef66
I too asked tron1 for TWRP flashable B05 version without answer yet (https://forum.xda-developers.com/showpost.php?p=72851004&postcount=95).
Since you have Android file host account, may I suggest you to build them by yourself and put them in your download center ?
Following is the procedure I found to build TWRP flashable version from full ROM ("update.zip") :
full ROM from ZTE = update.zip = (tron1's bootstack + tron1's stock system + recovery.img)
recovery.img is the stock recovery from full ROM
TWRP flashable ROM (bootstack + stock system) does not include recovery.img, this explains why TWRP is preserved and not overidden by stock recovery,
and so TWRP can be used to flash TWRP flashable-ROM.
To build TWRP flashable ROM files:
ZTE_A2017GV1.2.0B05_BootStack_by_raystef66.zip
ZTE_A2017GV1.2.0B05_Stock_System_by_raystef66.zip
- copy ZTE_A2017GV1.2.0B04_BootStack_by_tron1.zip to ZTE_A2017GV1.2.0B05_BootStack_by_raystef66.zip
- copy ZTE_A2017GV1.2.0B04_Stock_System_by_tron1.zip to ZTE_A2017GV1.2.0B05_Stock_System_by_raystef66.zip
- open ZTE_A2017GV1.2.0B05_BootStack_by_raystef66.zip (with TotalCommander, or WinRAR etc...) and replace all the files
(except META-INF directory) by their equivalent taken from udpate.zip.
- open ZTE_A2017GV1.2.0B05_Stock_System_by_raystef66.zip (with TotalCommander, or WinRAR etc...) and replace all the files
(except META-INF directory) by their equivalent taken from udpate.zip.
- in ZTE_A2017GV1.2.0B05_BootStack_by_raystef66.zip, change \META-INF\com\google\android\updater-script content to reflect B05 and the author
ui_print("----------------------------------------");
ui_print("ZTE A2017G V1.2.0B05 Bootstack & Modem");
ui_print("----------- Nougat 7.1.1 -----------");
ui_print("---------- Provided by tron1/raystef66 ----------");
ui_print("----------------------------------------");
- in ZTE_A2017GV1.2.0B05_Stock_System_by_raystef66.zip, change \META-INF\com\google\android\updater-script content to reflect B05 and the author
ui_print("----------------------------------------");
ui_print("ZTE A2017G V1.2.0B05 System & Boot image");
ui_print("----------- Nougat 7.1.1 -----------");
ui_print("-------- Provided by tron1/raystef66 ---------");
ui_print("----------------------------------------");
- upload the 2 files to Android file host
Click to expand...
Click to collapse
Since the " Master of bootstack/system Tron1" made these files before, I just left this work for him :cyclops:. If he's not made it by this evening I will provide the 2 files and upload them.
Laleka said:
I need small package link from bo4 to B05 there is link to 2gb file...
Click to expand...
Click to collapse
There is no real ota (yet?). But you will not lose anything by updating with the full file. It will not erase data. You can check this through the system update service when you put the file on the SD card. It should say if the update will erase data or not.
joaste said:
There is no real ota (yet?). But you will not lose anything by updating with the full file. It will not erase data. You can check this through the system update service when you put the file on the SD card. It should say if the update will erase data or not.
Click to expand...
Click to collapse
Thanks.... But the real problem is my data limit.... I don't have WiFi.....
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is Google's Official KRT16M Factory Image for the Nexus 5, without any mods included, zipaligned/signed, unrooted, untouched and ready to be flashed through any custom recovery. It will always come handy to you if you want to return back to stock from a custom rom, do a fresh and clean install or simply use it as a base to add your own mods. It is not rooted as some may don't want a rooted rom but can easily be done at any time by the end user. It comes in 2 versions, odexed and deodexed. This was cooked with dsixda's Android Kitchen.
Download KTU84P/Android 4.4.4 - Odex New!!!
http://www.mediafire.com/download/5e8m6403zj806kr/hammerhead_KTU84P_ODEX_itasoulas.zip
Download KTU84P/Android 4.4.4 - Deodex New!!!
http://www.mediafire.com/download/cfgxfavc1dq1c3t/hammerhead_KTU84P_DEODEX_itasoulas.zip
Relevant post:http://forum.xda-developers.com/showpost.php?p=53548698&postcount=130
-------------------------------------------------------
Download KTU84M/Android 4.4.3 - Odex
via dev-host
Download KTU84M/Android 4.4.3 - Deodex
via dev-host
Relevant post: http://forum.xda-developers.com/showpost.php?p=53145268&postcount=120
**** OUTDATED ****
Download KOT49H/Android 4.4.2 - Odex
via MEGA
via dev-host
Download KOT49H/Android 4.4.2 - Deodex
via MEGA
via dev-host
-----------------------------------------------------------
Download KRT16M/Android 4.4 - Odex
via MEGA
via dev-host
Download KRT16M/Android 4.4 - Deodex
via MEGA
via dev-host
Installation Procedure
- You need TWRP or CWM Custom Recovery installed on your phone.
- Wipe cache & dalvik
- Wipe data/factory reset
- Format system
- Flash rom
- Wipe cache and reboot
Root Procedure (optional)
Follow this thread by Chainfire. Once rooted you may also need to install Busybox
Odexed vs. Deodexed Mini Info
- Odexed may boot faster, can receive OTA updates
- Deodexed is easily customisable but cannot receive OTA updates
Note: I do not own a Nexus 5 (I am a Galaxy Nexus/Nexus 7 2013 user) so I cannot test things for you. But it should be safe for you flashing this since the procedure with Android Kitchen is always the same. Again I am not held responsible for any damage or issues you may face with your device after flashing this. You do this at your own risk!
*** How to update Android Kitchen in order to cook succesfully Nexus 5 ROMS ***
(thanks to members a9y and Dirk64 for providing me the workaround)
- unzip the files as follows:
a. "hammerhead" in kitchen's tools/edify_defs folder
b. "api_level" in kitchen's tools/deodex_files folder (will overwrite default file in that folder)
c. "use_this_version" in kitchen's tools/deodex_files folder (will overwrite default file in that folder)
d. "smali-2.0" & "backsmali-2.0" files in kitchen's tools/deodex_files folder
- now you can cook succesfully!!!
Thread will be updated every time a new factory image from Google is available!
mine! awesome thanks
rc420head said:
mine! awesome thanks
Click to expand...
Click to collapse
Fight Ya haha
Sent from my HTC One mini using Tapatalk
Ah, and so it begins. Cant wait till Monday when I get mine. Thanks
Nice, can't wait till i get mine... hrrr
Thanks for sharing
Sent from my SGH-I337M
It has begun!!!
Sent from my SGH-T989 using xda app-developers app
added deodexed version. I guess I am done for now. See you again when google releases a new factory image. Enjoy your awesome Nexus 5! :good:
EDIT: removed deodex, will re-upload in a while. Needed to deodex private apps folder, sorry about that!
Here is a mirror if its ever needed of the STOCK factory rom from Google
http://storagecow.eu/index.php?dir=Xda/Nexus+5/Stock+4.4/
itasoulas said:
Odexed vs. Deodexed Mini Info
- Odexed may boot faster, can receive OTA updates
- Deodexed is easily customisable but cannot receive OTA updates
Click to expand...
Click to collapse
You know I never really knew the exact diff. What can be customized on deodexed that can't be on odexed? Just curious.
Hand76 said:
You know I never really knew the exact diff. What can be customized on deodexed that can't be on odexed? Just curious.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=40026270 :good:
itasoulas said:
added deodexed version. I guess I am done for now. See you again when google releases a new factory image. Enjoy your awesome Nexus 5! :good:
EDIT: removed deodex, will re-upload in a while. Needed to deodex private apps folder, sorry about that!
Click to expand...
Click to collapse
Fully deodex version link added @ 1st post (including the priv-app folder!)
As the Android Kitchen wasn't build to support Android 4.4, after I build deodex version, I had to manually go back and erase apps in working folder's system/app, move the apps from priv-app to system/app and deodex again. Now apps from priv-app folder are deodexed so I replaced the odexed versions in original deodexed zip and then zipaligned it via command through android sdk tools folders. So quite easy trick there!
I get same error like the other build posted here in this section on XDA:
Deodexed version:
TWRP install error:
Error executing updater binary in zip
FAILED
Has somebody a hint whats wrong..??.
TWRP or the build zip?
thanks
Wonderful Work
You are Awesome Bro Thanks for KitKat 4.4 Many user waiting for 4.4 wait is over Thanks for KitKat 4.4 Rom
shivasrage said:
I get same error like the other build posted here in this section on XDA:
Deodexed version:
TWRP install error:
Error executing updater binary in zip
FAILED
Has somebody a hint whats wrong..??.
TWRP or the build zip?
thanks
Click to expand...
Click to collapse
I really can't test since I do not own the phone. Maybe others give us some feedback, can you flash this people? (don't know how many you already own the phone) I guess, if the bug is really there and not just you, updater-script or update-binary files might have a fault. Maybe Android Kitchen is not suitable to cook for N5? Maybe TWRP? Try CWM maybe? The process with Android Kitchen is quite straight forward, it shouldn't give errors.
Hand76 said:
You know I never really knew the exact diff. What can be customized on deodexed that can't be on odexed? Just curious.
Click to expand...
Click to collapse
It's mostly just theming. Also, the longer boot time is only on the initial boot.
itasoulas said:
I really can't test since I do not own the phone. Maybe others give us some feedback, can you flash this people? (don't know how many you already own the phone) I guess, if the bug is really there and not just you, updater-script or update-binary files might have a fault. Maybe Android Kitchen is not suitable to cook for N5? Maybe TWRP? Try CWM maybe? The process with Android Kitchen is quite straight forward, it shouldn't give errors.
Click to expand...
Click to collapse
TWRP has issues with some update-binaries (and the same one will probably work on CWM). Grab one of their binaries from another release they've done.
Is deodexed booting?
shivasrage said:
I get same error like the other build posted here in this section on XDA:
Deodexed version:
TWRP install error:
Error executing updater binary in zip
FAILED
Has somebody a hint whats wrong..??.
TWRP or the build zip?
thanks
Click to expand...
Click to collapse
I get the same error on both deodex odex version. Tried TWRP official and the 0.1. Oddly enough I can flash Slim rom. So I'm not sure if it's recovery or ROM.
Sent from my Nexus 5 using XDA Premium 4 mobile app
It's the binary and script. Kitchen hasn't been updated in a long time and its using old binary/script. Gotta update those.
Hi all,
I'm from Thailand.
I try to make flashable file for 4.4.2 kitkat kdz file for LG G2 ,It can use for LG G2 all model if you have kdz file.
I am testing with kdz file from http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW545195432109876543213/D80220A_00.kdz
( A6SFBK )
I reccommend 7zip for unzip/zip file.
Step by Step Guide
Before doing follower by instruction please read warning in red line before
1. Goto
http://forum.xda-developers.com/showthread.php?t=2600575
Download WindowsLGFirmwareExtract-ver.1.2.1.0 new version
2. Unzip WindowsLGFirmwareExtract-ver.1.2.1.0.zip and open WindowsLGFirmwareExtract.exe
3. At kdz/tot file select open and select 4.4.2 kdz that matching your G2 model (select all files extract)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Select extract kdz and waiting for success
5. At dz files select open and select .dz from step (4) (select all files extract)
6. Select extract dz and waiting for success
7. Select merge system-bin and waiting for success
8. Download
You must select one from 2 template
- KKROM_template.zip
https://mega.co.nz/#!kcVxSLaB!BJ4hHTF_3H8HR6EJTuak2hjiK1g1JosdKDfhcQ9Kr8g
(Stock firmware all partition include when you flash can not use custom recovery)
- KKROM_template_new.zip
https://mega.co.nz/#!BN1EFYRY!RJDpGwN4r3Q7q7lJmQil5RH_1s1lQWLHGZt21vY-Ffw
(New customize for still has custom recovery)
9. Unzip KKROM_template_new.zip/KKROM_template.zip
10. Copy system.img and all bin file as list below from WindowsLGFirmwareExtract-1.2.1.0-Release folder to KKROM_template_new/KKROM_template folder and use bat file in rename_droidth.zip rename all bin file
- KKROM_template_new.zip
KKROM_template_new folder must have
- KKROM_template.zip
KKROM_template folder must have
11. Zip all file in KKROM_template_new/KKROM_template. Now you get KKROM_template_new.zip/KKROM_template.zip ready to flash
12. Download
- Supersu from http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip (For all template)
- Patched Kernels and KitKat BaseBand from http://forum.xda-developers.com/showthread.php?t=2680948 (For KKROM_template_new)
Thank @Cloudyfa for work Patched Kernels and KitKat BaseBand
13. You must on 4.2.2 root+custom recovery (TWRP 2.6.3.3 or 2.7 That I am testing) .
Copy KKROM_template_new.zip/KKROM_template.zip to sdcard
Copy Patched Kernels,KitKat BaseBand to sdcard (For KKROM_template_new)
Copy UPDATE-SuperSU-v1.93.zip to sdcard to sdcard (For all template)
14. Reboot to recovery
15. Wipe
- Dalvik Cache
- System
- Data
- Cache
16 . Install
Warning :
When flash KKROM_template_new.zip finish.Do not Change or Flash Recovery on KK or JB (in case use backup/restore from Recovery or use Custom ROM)
if do not flash kdz before.Your G2 may be can not boot.
For KKROM_template_new
- KKROM_template_new.zip
- KitKat BaseBand
- Patched Kernels
- UPDATE-SuperSU-v1.93.zip
For KKROM_template
- KKROM_template.zip
- UPDATE-SuperSU-v1.93.zip
17 . Wipe cache/dalvik
18. Reboot
19. Enjoy
Guide for KKROM_template
Thank
@AndroidUser00110001
@Cloudyfa
@shriom_manerker
I have KK rooted. Thanks?
Do you still have a custom recovery after you class this?
**** Ripple said:
Do you still have a custom recovery after you class this?
Click to expand...
Click to collapse
์No.
OMG thank you very much
With this it's easier to make custom rom
Thanks awesome
is this for 16gb or 32gb or both?
Seem your file not yet finished uploading?
Both
Sent from my Nexus 7 using Tapatalk
kennytung said:
is this for 16gb or 32gb or both?
Seem your file not yet finished uploading?
Click to expand...
Click to collapse
Thank you. I edited link file.
hi..
thanks, this is exactly what i need.
one question though,
what about "cust.bin"?
someone said in other thread that it's needed to avoid bootloop.
farhanito said:
hi..
thanks, this is exactly what i need.
one question though,
what about "cust.bin"?
someone said in other thread that it's needed to avoid bootloop.
Click to expand...
Click to collapse
In this this:
http://forum.xda-developers.com/showthread.php?t=2665985
I got bootloop then I solve problem by add cust.bin in ROM.it's work for me.
Sent from my Nexus 7 using Tapatalk
somboons said:
In this this:
http://forum.xda-developers.com/showthread.php?t=2665985
I got bootloop then I solve problem by add cust.bin in ROM.it's work for me.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
so, you need to put cust.bin inside the zip, and add this line in updater-script
Code:
package_extract_file("cust.bin", "/dev/block/platform/msm_sdcc.1/by-name/cust");
am i right?
farhanito said:
so, you need to put cust.bin inside the zip, and add this line in updater-script
Code:
package_extract_file("cust.bin", "/dev/block/platform/msm_sdcc.1/by-name/cust");
am i right?
Click to expand...
Click to collapse
Yes.
Sent from my Nexus 7 using Tapatalk
farhanito said:
so, you need to put cust.bin inside the zip, and add this line in updater-script
Code:
package_extract_file("cust.bin", "/dev/block/platform/msm_sdcc.1/by-name/cust");
am i right?
Click to expand...
Click to collapse
Oh Thank,I will edit instruction .Wrong picture.
I'm already in KK
So i need to downgrade to JB first right?
Sent from my LG-D802 using xda app-developers app
GaYoung28 said:
I'm already in KK
So i need to downgrade to JB first right?
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
yes
@somboons thanks for the awesome tutorial just did it and its working just fine on my D802 cheers
This is awesome. It would be easier to flash back to stock this way then requiring a PC. Would this work for Verizon? I'd love a backup of the stock rom incase I'm t hours away from a PC and Verizon forces a bricking OTA update and leaves me completely lost and without a phone.
Sent from my VS980 4G using XDA Premium 4 mobile app
i got error lokiflyng and unsuportted aboot image file :\
help please
player911 said:
This is awesome. It would be easier to flash back to stock this way then requiring a PC. Would this work for Verizon? I'd love a backup of the stock rom incase I'm t hours away from a PC and Verizon forces a bricking OTA update and leaves me completely lost and without a phone.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am not sure it's support Verizon but I think it should work too.
GaYoung28 said:
i got error lokiflyng and unsuportted aboot image file :\
help please
Click to expand...
Click to collapse
Can your G2 boot completely?
I did see this error on my device but At thread http://forum.xda-developers.com/showthread.php?t=2665985
@AndroidUser00110001 he told don't worry about error
If you get an error with flashing about loki then do not worry. ROM is ok and will boot. It just can't add loki to boot.img so it gives error but no big deal.
Click to expand...
Click to collapse
B008 Full Flash (Public Release)
Apparently, Huawei has deemed the latest B008 version to be stable enough for public consumption and thus has released it as the final (for now) EMUI 3.0 / 400 dpi ROM for Mediapad X1 501u.
For full ROM download, kindly visit:
http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI3.0_Android4.4_V100R002C208B008.zip&rid=901
(kindly note this is a FULL ROM, not an incremental update. Flash as per how you would normally flash a full rom; remember to backup your data prior as flashing a full rom most probably will wipe your data)
Another leaked official beta ROM from Huawei for 7D-501u.
The main feature in this ROM is EMUI 3.0, for those who are still in the dark, EMUI is the skin which Huawei applies over stock Android, think Sense for HTC, Touchwiz for Samsung. EMUI version for current ROMs is 2.3 for KK and 2.0 for JB.
This beta ROM is 4.4.2 based and uses a framework of 400DPI.
B002 Full Flash
http://www.mediafire.com/download/1n0rxw6ae17mlt6/7D-501uV100R002C208B002.zip
B005 Update (this is an 80MB update, your 501u needs to be already on the B002 ROM above to be able to flash; flashing procedure as below, thanks to bthoven)
http://www.mediafire.com/download/3ecpzlih5hqa05m/7D-501uV100R002C208B005.zip
1. Create dload folder in internal sdcard
2. Copy the whole b005 zip file to dload folder (don't unzip it)
3. Rename the b005 zip file to update.zip
4. Local update
http://forum.xda-developers.com/showpost.php?p=56766405&postcount=56
B005 changelog (edited translation provided by bthoven through Google translate)
http://forum.xda-developers.com/showpost.php?p=56742863&postcount=51
Newly added options:
1. Added 4G only (for 4G model), 3G only option
2. Added option to turn on the screen when a new message has been received
3. Added speed dial function to dialer interface
Important optimizations:
1. Optimizes memory allocation and management strategy
2. Optimizes the UI layout and icon adaptation
3. Fully optimized system stability, fixed rare instances of phone hanging and other problems
4. Optimizes network search time
5. Optimizes power consumption during phone standby with screen off when data is switched on
6. Fixed silent installation problem for App Store
7. Fixed delay reception of WeChat messages
8. Fixed various UI performance problems i.e. screen lagging when scrolling list of installed apps or when returning to home screen from web browser and also other instances when the phone appears unresponsive
9. Adjusted the indications layout for data services
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
B006 Update (this is an 60MB update, your 501u needs to be already on the B005 ROM above to be able to flash; flashing procedure as below, [same as that for B005])
http://www.mediafire.com/download/aggcrualriz1hhu/7D-501uV100R002C208B006.zip
1. Create dload folder in internal sdcard
2. Copy the whole b006 zip file to dload folder (don't unzip it)
3. Rename the b006 zip file to update.zip
4. Local update
B006 changelog
Important optimizations:
B008 Update (this is a 35MB update, your 501u needs to be already on the B006 ROM above to be able to flash; flashing procedure same as below, [same as that for B005])
http://www.mediafire.com/download/sop3lnafdjseit4/7D-501uV100R002C208B008.zip
Great news... :thumbup:
Time for testing
Sent from my Galaxy Nexus using XDA Free mobile app
Looking forwards to test result, especially about app compatibility.
FAILED to Update
My Current Version:
7D-501uV100R002C233B010
EMUI 2.3
check_update_package_load suceed
check_update_package_signature suceed
check_update_package_valid failed !
AhmadDawood said:
FAILED to Update
check_update_package_load suceed
check_update_package_signature suceed
check_update_package_valid failed !
Click to expand...
Click to collapse
for me too
it is untested fake
If you have previous ROM around, simply replace the update.app file , retaining the 2 cfg files and then flash again to see if it works.
If you don't, download the attachment below for those 2 files.
If it still doesn't work, it means the source is bad.
Original B010 4.4.2 EMUI 2.3 400DPI ROM from Huawei Direct if you dont already have it - http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI_2.3_V100R002C233B010.zip&rid=592
potatohead said:
If you have previous ROM around, simply replace the update.app file , retaining the 2 cfg files and then flash again to see if it works.
If you don't, download the attachment below for those 2 files.
If it still doesn't work, it means the source is bad.
Click to expand...
Click to collapse
Don't work, FAILED to Update
My Current Version:
7D-501uV100R002C233B010 EMUI 2.3
sorry folks.
source is bad i guess.
download link removed.
will update thread if new source found.
I successfully flashed it at the second time with another bigger rom download.
I can say that it is not worth of flashing because font size is very small and chrome is not compatible totally with phone page.
So, I decided to flash back to C233B010.
Don't waist your time.
vuhongduong said:
I successfully flashed it at the second time with another bigger rom download.
I can say that it is not worth of flashing because font size is very small and chrome is not compatible totally with phone page.
So, I decided to flash back to C233B010.
Don't waist your time.
Click to expand...
Click to collapse
Sorry dear, it seems your comment is not relevant to this thread. This rom is with EMUI 3.0 and 400 DPI. How the font can be very small? You have posted the same comment in another thread where it is relevant.
vuhongduong said:
I successfully flashed it at the second time with another bigger rom download.
I can say that it is not worth of flashing because font size is very small and chrome is not compatible totally with phone page.
So, I decided to flash back to C233B010.
Don't waist your time.
Click to expand...
Click to collapse
where is this bigger rom ?
AhmadDawood said:
where is this bigger rom ?
Click to expand...
Click to collapse
I have updated the URL in the opening post from a new source.
http://www.mediafire.com/download/1n0rxw6ae17mlt6/7D-501uV100R002C208B002.zip
It has been reported to work.
Feel free to try it and report back if it ain't working.
potatohead said:
I have updated the URL in the opening post from a new source.
It has been reported to work.
Feel free to try it and report back if it ain't working.
Click to expand...
Click to collapse
WAAAAAW ... Excellent.... really new and very smooth polished new emui 3 Interface
This is really fantastic
thanks for your Link bro
AhmadDawood said:
WAAAAAW ... Excellent.... really new and very smooth polished new emui 3 Interface
This is really fantastic
thanks for your Link bro
Click to expand...
Click to collapse
Welcome.
Glad it works this time round and thank you for your confirmation.
So questions:
Can access google play store?
Some apps compatibility issues?
Chinese rom? Not international rom?
Thx for replying
it is not working again
can u post screenshots plz
0/ what about e-mail client in stock - can't set up gmail (imap enable)
The Latest Link Posted by [potatohead] on 6 Nov. worked Great with no single problem
Concerning Google Apps and services,,this rom does not include them but you can easily download Google Play,Gmail....etc
as I did and all of them worked Great and excellent
it is a Chinese rom but includes all languages....for me I found even the Arabic Language in both the interface and Google KB .which was not found in the B010 Emui 2.3
also the stock Email Client is great including templates for all known Email providers including GMAIL
I have downloaded various Apps from Google Play(after installing it) with No compatability Problems
yes some app issues and non-complaint as what i discussed in '7d-503L 4.4.2 emui 3.0 400 dpi' thread. however this rom is not for LTE handset
When the official rom 3.0 will be relase?
(7.1) Flyme7. Fingerprint infrared V3 For the Leeco X720 and X727 ( Updated on 9/5/2018 )
AKA: The newest version of Flyme Original Chinese Name : 7to-X720.flyme7.指纹红外V3.zip
Developer: Cold and Ruthless
Original Link: http://rom.7to.cn/romdetail/1030273
Link: https://mega.nz/#F!xYJgXYxK
Key: !QNUTt-aMXA-Kvl39hOMp9A
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flyme:
LeTV pro3 transplant Flyme7.8.21R V3
Redesigned interface, better overall experience
Advanced settings root card brush package
Optimized sound
Author: Cold ruthless
Release Date: 2018-09-04
Android version: 7.1.x
UI type: Flyme ROM
Size: 1270.00MB
Experience the new interface, with advanced settings, high speed, theming options, and excellent call and sound quality, all are hallmarks of the Meizu Official Experience
Applicable models: LeEco LEX720, LEX727
Optimization of the optimized
volume of the bottom package update sound.
Temperature control based on port from: Charm Blue Note 6 Build
Double Wipe> reboot to Recovery, if you have an error you may need to format storage
The first boot is very slow, please wait for the Meizu official latest experience version transplant
Past Bluetooth issue resolved.
Optimization scheduling
New interface new experience, advanced settings and optimization
Installation Notes:
First Boot may be slow, so if it takes a while for the first system boot, the solution is just to wait longer.
Flyme Account http://forum.flymeos.com/
Create an Official Flyme account if you want to gain access to tons of addons.
Meizu is Port friendly and Flyme Account Provides:
Forum advice
Plugins,
Apps,
3rd party themes etc.
Download Flyme 7 Launcher, Stock Wallpapers, and Apps (Flyme 7 stock APK)
https://www.androidsage.com/2018/05/15/download-flyme-7-launcher-stock-wallpapers-apps-apk/
As always, flash anything under your own discretion
Root
This Rom comes with Magisk root, You can easily flash Magisk 17.1 overtop after setting up the system and then rebooting to recovery.
Gapps: I am using BeansGapps-Mini-7.1.x-20170725.zip
Helpful files:
https://mega.nz/#F!JMYSSCLQ
Key: !xgQFTB69PE-hL8RTUbpUIw
Firmware
https://mega.nz/#F!oAZ3yC4b!
Key: MDwbHXNTRdrpgMvQ42yviw
If you have safetynet issues, follow the steps below
Extract the boot.img file from the rom, and placed the boot image into storage.
Open Magisk and use install to Patch Magisk to the boot.img.
Reboot to recovery, install the patched boot.img to boot
Flash addonsu-15.1-arm-signed.zip, and then reflash Magisk again, from storage then use advanced options to clear cache, and then reboot to system.
With these steps you will always Pass Safetynet and be playstore certified
https://forum.xda-developers.com/showpost.php?p=77367331&postcount=4790
Build Prop Recommendations
After the installation and initial testing period,. you may decide to continuing using Flyme for a while:
If so you can further optimise the ROM with these build prop and edits posted below.
First backup your existing buildprop
* ro.product.locale.language = en ( or your language)
* ro.product.locale.region = IN or your country
* persist.sys.timezone = your country ( see proper entry here: https://gist.github.com/arpit/1035596)
* persist.sys.meizu.region =
or use persist.sys.oem.region= your country google correct acronym for your country
Reserved for future hints
Thanks I will try and feedback
i get error code 3 when i try to flash
rob_z11 said:
i get error code 3 when i try to flash
Click to expand...
Click to collapse
Me Too!
Yes, I tried it and the same thing happened to me, it must be a corrupt download because people are giving the release a 8.3/10. I found a slightly older but highly rated rogue pig version. ( see same link above)
I installed it successfully and must say, it's actually extremely good.
Corruption
The original newer file is probably just corrupted so I am going to try redownloading it. Until then, check out the other version that I placed in the same megadrive folder see the link above. Yes, it's a little older but its actually awesome!
I just attempted to find the newer rom by cold ruthless on the BBS website, has he been banned. I had a bookmark saved and when I click I get this message " Authors are banned or deleted automatically blocked" Not sure if its the same person or not, if this next download is corrupt. I would still recommend flyme_LEX720_rogue_6.8.3.17R-beta, I am testing it right now and like it alot.
Does Android Pay work with this ROM?
I flashed the ROM after the boot I face a black screen and a bar with Chinese written and I can't do anything only control the volume...I only flash the ROM with wipe the data,system and delvic cach
3llawi said:
I flashed the ROM after the boot I face a black screen and a bar with Chinese written and I can't do anything only control the volume...I only flash the ROM with wipe the data,system and delvic cach
Click to expand...
Click to collapse
No issue like this. Everything worked. It booted fine. You may have to use the recovery version from earlier in the month of Jan.
Everything worked for me except volte which is no big deal. Really impressive build. Thanks for downloading @tsongming..
3llawi said:
I flashed the ROM after the boot I face a black screen and a bar with Chinese written and I can't do anything only control the volume...I only flash the ROM with wipe the data,system and delvic cach
Click to expand...
Click to collapse
It looks like what happened to me when going from an Oreo rom to Nougat, you have to format data not only wipe data. Format data, write "yes" and then install the rom. Always have a backup of your data before.
flyme is one of the best system , the official one is good but it's old , be sure to have eui firmware before flashing flyme .
rob_z11 said:
No issue like this. Everything worked. It booted fine. You may have to use the recovery version from earlier in the month of Jan.
Everything worked for me except volte which is no big deal. Really impressive build. Thanks for downloading @tsongming..
Click to expand...
Click to collapse
Please can you put the link of old recovery version
rob_z11 said:
No issue like this. Everything worked. It booted fine. You may have to use the recovery version from earlier in the month of Jan.
Everything worked for me except volte which is no big deal. Really impressive build. Thanks for downloading @tsongming..
Click to expand...
Click to collapse
Did you format internal storage?
3llawi said:
Did you format internal storage?
Click to expand...
Click to collapse
No because I have always been on miui10
can some1 link me the gapps?
collisiion said:
can some1 link me the gapps?
Click to expand...
Click to collapse
Look at the post #1
Thanks to troubleshooting from @ rob_z11, I plan to post a working version of the Cold Ruthless file late tonight EST.
andrew2401 said:
Does Android Pay work with this ROM?
Click to expand...
Click to collapse
I believe so, though I haven't tried it yet. I will let you know late tonight
tsongming said:
I believe so, though I haven't tried it yet. I will let you know late tonight
Click to expand...
Click to collapse
Okay thank you how's the battery so far?; I've owned Meizu phones and there is was always good for battery optimization
tsongming said:
Thanks to troubleshooting from @ rob_z11, I plan to post a working version of the Cold Ruthless file late tonight EST.
Click to expand...
Click to collapse
Ok, this is what I have found. Your original latest flyme seems to be working ok. Here is what I have done. Using RAR apk, I unzipped it, and it complained about one apk in mizu-apk folder, and I ended up removing that folder completely, and zipped the ROM again. It flashed without any issue, but I can't seem to get Data to turn-on. It turns on briefly during the boot, but it goes away. I think if I compare the build.prop from older version with newer version, I may be able to find the fix.
andrew2401 said:
Okay thank you how's the battery so far?; I've owned Meizu phones and there is was always good for battery optimization
Click to expand...
Click to collapse
Extremely good, at the moment my phone has no OS at all..
I only glanced at battery life briefly yesterday with Gsam battery tool. Plus, I installed BlackScreen 5.3 r2 which worked fine, I would rather wait for a real answer. Otherwise it would just be a guess.
Hi All,
Below you can find a couple of incremental update packages that you can use for updating from various versions of your device.
Incremental update packagesThese can be installed using TWRP by following this tutorial.
710.82 MB folder on MEGA
3 files
mega.nz
edit: up-to-date until update A19
Boot imagesThese can sometimes be required when updating to a newer version.
320 MB folder on MEGA
10 files
mega.nz
VBMETAVBMeta must be flashed after every incremental update.
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Thanks to @HofaTheRipper in the telegram channel for providing most of these package / images.
dev-DaT said:
Hi All,
Below you can find a couple of incremental update packages that you can use for updating from various versions of your device.
Incremental update packagesThese can be installed using TWRP by following this tutorial.
710.82 MB folder on MEGA
3 files
mega.nz
Boot imagesThese can sometimes be required when updating to a newer version.
320 MB folder on MEGA
10 files
mega.nz
VBMETAVBMeta must be flashed after every incremental update.
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Not all have been uploaded yet, WIP.
Thanks to @HofaTheRipper in the telegram channel for providing most of these package / images.
Send me pm if you have new packages that need to be added.
Click to expand...
Click to collapse
Update A16 to A17 EU and boot stock A17 EU:
Update A17 to A19 EU and boot stock A19 EU:
HofaTheRipper said:
Update A17 to A19 EU and boot stock A19 EU:
Click to expand...
Click to collapse
Do you happen to have A20 boot.img?
CoinsClassic said:
Do you happen to have A20 boot.img?
Click to expand...
Click to collapse
Sorry... sold the device.
HofaTheRipper said:
Sorry... sold the device.
Click to expand...
Click to collapse
How did you extract stock boot img for the device?
CoinsClassic said:
How did you extract stock boot img for the device?
Click to expand...
Click to collapse
TWRP
Patched boot image myself using imgpatchtools. Used A19 from you and applied the boot.img.p patch from OTA zip.
For anyone who needs. Here is the C.01 image for DN2103, stock and patched with magisk, you can read and write these with MTKclient as fastboot is removed in C.01. You may need to rename it to .bin
ivoh95 said:
For anyone who needs. Here is the C.01 image for DN2103, stock and patched with magisk, you can read and write these with MTKclient as fastboot is removed in C.01. You may need to rename it to .bin
Click to expand...
Click to collapse
Hi,any chance of full install instructions as I've lost the ability to access fastboot/ bootloader I'm not sure how to flash A12 stock EU version.A y detailed help would be much appreciated.Thanks
Sorry, downgrade from OS A12 to Stock OS A11
A full OTA from Android 11 to Android 12, for DN2103 EU version, is possible to post? Thank you
Anyone got a A21 boot.img please?
davythom said:
Hi,any chance of full install instructions as I've lost the ability to access fastboot/ bootloader I'm not sure how to flash A12 stock EU version.A y detailed help would be much appreciated.Thanks
Click to expand...
Click to collapse
Why do you need fastboot? If root is all you want then flash those with MTKclient and BROM mode. Otherwise look in the forums there is instructions to downgrade from 11-12.
I'm actually wondering if we flash the right partitions from 11 while running 12 if it will brick or if it will reenable fastboot. Maybe someone brave can try
ruh01 said:
A full OTA from Android 11 to Android 12, for DN2103 EU version, is possible to post? Thank you
Click to expand...
Click to collapse
I have two EU phones right now. One have received OxygenOS 12.1 (C.01) and another one is sitting on A.20. Can I grab an update from the first phone somehow?
"quote
/data/OTA-package/update.zip
Assuming you've downloaded the update via the OTA settings tab, the update.zip will be at this location and can be transferred to your PC or flashed using TWRP as-is from the above location. "
@Maddinx
stock boot.img for A21 update with June Patch 2022.
Patched myself using this tool: https://github.com/erfanoabdi/imgpatchtools/releases/download/0.3/IMG_Patch_Tools_0.3.zip
$ ./ApplyPatch stock_A20_boot.img new_A21_boot.img 73f2f272c090ffa378b9662d00985bf81cff02ea 33554432 31016eca2954bf998f0fe961642ab6d025264f29 boot.img.p
Syntax is:
- ./ApplyPatch
- existing boot.img name (e. g. A20 from here)
- new boot.img name
- SHA hash of new boot.img file (to be created)
- filesize
- SHA hash of previous boot.img file
- patch file
The hashes and the filesize are located in the updater-script file under META-INF\com\google\android\
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Love letter to my future self in case I forget how to patch it myself )
CoinsClassic said:
@Maddinx
stock boot.img for A21 update with June Patch 2022.
Patched myself using this tool: https://github.com/erfanoabdi/imgpatchtools/releases/download/0.3/IMG_Patch_Tools_0.3.zip
$ ./ApplyPatch stock_A20_boot.img new_A21_boot.img 73f2f272c090ffa378b9662d00985bf81cff02ea 33554432 31016eca2954bf998f0fe961642ab6d025264f29 boot.img.p
Syntax is:
- ./ApplyPatch
- existing boot.img name (e. g. A20 from here)
- new boot.img name
- SHA hash of new boot.img file (to be created)
- filesize
- SHA hash of previous boot.img file
- patch file
The hashes and the filesize are located in the updater-script file under META-INF\com\google\android\
View attachment 5657295
View attachment 5657291
(Love letter to my future self in case I forget how to patch it myself )
Click to expand...
Click to collapse
Where to find update script A20 to A21?
You patched only the boot.img. Is this enough? Idk, since never received this A21 update.
Please elaborate how to update from A20 to A21 on rooted with magisk_patched_A20.img to A21 update with magisk_patched_A21.img
Thank you!
roldev said:
Where to find update script A20 to A21?
You patched only the boot.img. Is this enough? Idk, since never received this A21 update.
Please elaborate how to update from A20 to A21 on rooted with magisk_patched_A20.img to A21 update with magisk_patched_A21.img
Thank you!
Click to expand...
Click to collapse
update-script file is located under META-INF\com\google\android\ in the incremental OTA zip file. (To get the link of the OTA update file, I used https://github.com/Akilesh-T/OTALink )
Patching just the boot.img works perfectly for me. root access and no limitations.
So far I've used the described patching method like this:
1. Patch boot.img as described above (create A21 from A20 img file)
2. Patch created boot.img with Magisk
3. Uninstall Magisk (Restore boot Image)
4. Install incr. OTA
5. After OTA installation, boot to fastboot
6. Flash magisk patched boot.img
7. fastboot reboot
Done.
CoinsClassic said:
update-script file is located under META-INF\com\google\android\ in the incremental OTA zip file. (To get the link of the OTA update file, I used https://github.com/Akilesh-T/OTALink )
Patching just the boot.img works perfectly for me. root access and no limitations.
So far I've used the described patching method like this:
1. Patch boot.img as described above (create A21 from A20 img file)
2. Patch created boot.img with Magisk
3. Uninstall Magisk (Restore boot Image)
4. Install incr. OTA
5. After OTA installation, boot to fastboot
6. Flash magisk patched boot.img
7. fastboot reboot
Done.
Click to expand...
Click to collapse
Thank you very much.
I try to figure how to do the step 4. Need offline install, because: 1) if try with TWRP end with bootloop, 2) the system updater wants to push me C.01 straight from A20. 3) for now want to keep the latest 11.3
Maybe using imgpatchtools can do update from my PC. Any idea?