Since those generic system images are image files, can I flash them using Odin instead of custom recovery?
Answering my own question
I have tested it yesterday with Heimdall and it worked!
This was the command line I used:
Code:
$ heimdall flash --pit file.pit --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img
Being boot.img patched by Magisk, recovery.img -> TWRP and system.img a generic System Image of Android Q pure, type AB.
cizordj said:
Answering my own question
I have tested it yesterday with Heimdall and it worked!
This was the command line I used:
Code:
$ heimdall flash --pit file.pit --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img
Being boot.img patched by Magisk, recovery.img -> TWRP and system.img a generic System Image of Android Q pure, type AB.
Click to expand...
Click to collapse
so you flashed recovery.img
Can't you now boot into recovery and flash GSIs from there?
physwizz said:
so you flashed recovery.img
Can't you now boot into recovery and flash GSIs from there?
Click to expand...
Click to collapse
No, I installed the first release of TWRP taken from here
https://forum.xda-developers.com/ga...overy-twrp-3-3-1-0-galaxy-a10-exynos-t4013481
and it simply doesn't flash system images, only small boot images.
Now I'm going to the latest version to see if it has been fixed.
cizordj said:
No, I installed the first release of TWRP taken from here
https://forum.xda-developers.com/ga...overy-twrp-3-3-1-0-galaxy-a10-exynos-t4013481
and it simply doesn't flash system images, only small boot images.
Now I'm going to the latest version to see if it has been fixed.
Click to expand...
Click to collapse
What is your firmware date.
cizordj said:
No, I installed the first release of TWRP taken from here
https://forum.xda-developers.com/ga...overy-twrp-3-3-1-0-galaxy-a10-exynos-t4013481
and it simply doesn't flash system images, only small boot images.
Now I'm going to the latest version to see if it has been fixed.
Click to expand...
Click to collapse
Dude I just want to say lol.
physwizz said:
What is your firmware date.
Click to expand...
Click to collapse
If I am not mistaken I was running november 2019 released firmware, I know... I read somewhere that this firmware would not work well with TWRP - yet - but I installed it anyway.
I flashed the android 10 GSI with Heimdall, I don't know how but it's working. I'm using it right now haha
cizordj said:
If I am not mistaken I was running november 2019 released firmware, I know... I read somewhere that this firmware would not work well with TWRP - yet - but I installed it anyway.
I flashed the android 10 GSI with Heimdall, I don't know how but it's working. I'm using it right now haha
Click to expand...
Click to collapse
The TWRP you are using is correct for your firmware.
I've not read of any issues with it.
Most problems work out to be some other cause.
Hi, Can anyone tell me where to get the pit.img?
Moreover, Is it alright to use boot.img extracted from Stock ROM?
Also would like to know about pit file. Trying to install google GSI at a Galaxy A7 2018 (1750G/DS). Without any luck so far...
Please show me how you did it via windows?
Related
Hi everyone, just in case someone wanna try ColorOs (default OS for chinese OnePlus one).
There's some zip files flashable with twrp but, after that, you can't use OTA update and have to manually download the upgrade and flash it.
For me is annoying so I've flashed the rom, with gapps without installing a recovery.
First download ColorOs from here:
https://mega.co.nz/#!BkpwyYSB!rkYSkFI28vFGuhtsIli-vyDdsb4ZZp1-MX1cLLtaiRo
Download Gapps from cyano (select the 10.2):
http://wiki.cyanogenmod.org/w/Google_Apps
Download Twrp (we will use it but we will not install it)
http://teamw.in/project/twrp2/231
Remember, this process will wipe everything on your phone, so MAKE A BACKUP!!
Extract color.zip and boot the phone in fastboot mode (volume up + power), connect it to you computer.
Important if you have a 16gb phone, the second command is
Code:
fastboot flash userdata userdata.img
Code:
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
After that, fastboot reboot will reboot your phone. You have to wait a bit the first time. Now, select english (ColorOs support only chinese and english). go to system > update a make the system update (I had to do two consecutive updates), don't worry, it's really slow.
Now, the phone is up to date but has no Google app and, the ColorOs recovery isn't able to flash them so, connect the phone and copy the gapps into the phone, after that reboot it in fastboot mode (volume up + power).
Code:
fastboot boot <twrp_image.img>
This will boot temporary the twrp recovery, go to install zip from sd card and flash the gapps, after that, you can reboot the phone and enjoy ColorOs with google apps.
Hope this could help.
EDIT:
If someone want to root it, have to install (using TWRP) this
http://d-h.st/zJ8
I've NOT tried this file.
THX!
Could I go back to a other ROM like mahdi ROM whenever I want by just flashing a back up? And is this color OS 2.0.11 or 1.2?
AndroidInsanity said:
Could I go back to a other ROM like mahdi ROM whenever I want by just flashing a back up? And is this color OS 2.0.11 or 1.2?
Click to expand...
Click to collapse
Yes, you obviously can but, if you use this method, first you have to flash twrp or another recovery.
You can backup the phone, save the backup folder to your pc.
If you want to rollback, copy the folder that you have saved into your pc, flash twrp and restore everything.
I used this method becouse, in this way you have ota updates with no problems.
And this method, after the system update, will give you 2.0.11
MultiRom?
mojna37 said:
MultiRom?
Click to expand...
Click to collapse
I tried colorOS version 2.0.11 using multirom but it doesn't boot up.
MIUI boots and works flawlessly on multirom.
Miui works fine to me to. ColorOS faild on install.
Sent from my OnePlus One using Taptalk
mojna37 said:
Miui works fine to me to. ColorOS faild on install.
Sent from my OnePlus One using Taptalk
Click to expand...
Click to collapse
Following this guide?
ColorOs has a lot of problems with twrp flashable zips.
I preferred to share a guide that uses fastboot. I've tried all of this command and, now I'm testing ColorOs, no issues at all.
ColorOs is a really good rom, smooth, nice with battery, full of functionality and, the best camera, other rom seems to use different hardware.
The rom is really too similar to Ios and I don't like ios clones but, I think that it's a rom that deserves a try.
Castore said:
Following this guide?
ColorOs has a lot of problems with twrp flashable zips.
I preferred to share a guide that uses fastboot. I've tried all of this command and, now I'm testing ColorOs, no issues at all.
ColorOs is a really good rom, smooth, nice with battery, full of functionality and, the best camera, other rom seems to usa different hardware.
The rom is really too similar to Ios and I don't like ios clones but, I think that it's a rom that deserves a try.
Click to expand...
Click to collapse
I mean to install with MultiRom. I will try it using fastboot soon.
Sent from my OnePlus One using Taptalk
Castore said:
Yes, you obviously can but, if you use this method, first you have to flash twrp or another recovery.
You can backup the phone, save the backup folder to your pc.
If you want to rollback, copy the folder that you have saved into your pc, flash twrp and restore everything.
I used this method becouse, in this way you have ota updates with no problems.
And this method, after the system update, will give you 2.0.11
Click to expand...
Click to collapse
Thanks. Will follow instructions and let you know if I succeed later (Y) thanks for the help
I get a fail when flashing system
C:\adb>fastboot flash system system.img
sending 'system' (890182 KB)... FAILED (remote: data too large)
finished. total time: 0.003s
EDIT: just updated my fastboot. SEEMS to be ok now
SUCCESS! thanks ! really like it. although I wish it had the 50MP photo option, someone on the oneplus forum said it did :S
By the way. is their a method to root color OS?
@AndroidInsanity
How did you solved the problem with fastboot dimension exceed?
I had the same problem with cyano 11s and Fedora.
I've edited the first post with a link that root the rom.
I've not tried to root the rom.
Can someone extract the modem image from this please? It won't complete download for me.
Sent from my A0001 using Tapatalk
Hello Bro, from your understanding, will there be any problem on the 3G and 4G network after flashing to Color? Thanks
Castore said:
@AndroidInsanity
How did you solved the problem with fastboot dimension exceed?
I had the same problem with cyano 11s and Fedora.
I've edited the first post with a link that root the rom.
I've not tried to root the rom.
Click to expand...
Click to collapse
Grab the latest android SDK and download platform tools from it then replace your current fastboot.exe with the one in the latest SDK.
etlok said:
Hello Bro, from your understanding, will there be any problem on the 3G and 4G network after flashing to Color? Thanks
Click to expand...
Click to collapse
I've no 4g connection in my data plan.
With 3g there's no problem at all.
Could I boot twrp and restore I backup of Mahdi ROM without issues?
AndroidInsanity said:
Could I boot twrp and restore I backup of Mahdi ROM without issues?
Click to expand...
Click to collapse
I've restored today the backup of Cyano 11 with no problem at all.
Anyone having issues with GPS lock for the stock weather app? When I try to get my location it stays at searching forever then eventually tells me it can't find my location, yet when I use the Chronic widget it finds my location easily.
Any patches to apply for the Colors weather? Would love to use it and some of the awesome animated lockscreens as well.
From the first time i was not able to upgrade my phone to another new version of Android.
The phone was bought on chinese store with Android version : WW V10.40.47.107 (Android MM)
When i checked availability of new versions, phone showed me no result available.
Then following instructions i unlocked bootloader and then install TWRP as recovery system.
I tried to install updates of ROM downloaded from Asus website using this methods with this results :
installing by TWRP with ROM transfered to internal memory of phone KO
installing by "ADB sideload" command KO
I partially resolved after many attempts updating only to Version V11.41.87.2 (Android MM)
I solved in this way :
i used TWRP installing from file transfered directly in microSD
i extracted from zipped file "updater-script" file that is possible to find in the following folder path :
META-INF > com > google > android
and then deleted this rows :
(!less_than_int(1494697617, getprop("ro.build.date.utc"))) || abort("Can't install this package (2017年 05月 14日 星期日 01:46:57 CST) over newer build (" + getprop("ro.build.date") + ").");
.....
getprop("ro.build.asus.sku") == "WW" || abort("Please use the right SKU for updating...");
.....
and then save file extracted and compress into zip file.
During TWRP install process i got some error updates, it seems connected to System folder/partition update
but at the end i was able to update Android to my phone
I tried to do the same method with an other update Version V20.32.67.25 i got a corrupted System folder/partition
It seems essential to update this phone to use original recovery system. Can anyone give it to me?
Or is there someone who has been able to install updates using TWRP without any error ?
Also after installation I wiped the Boot, System, Data, Cache partitions and then I restored from Nandroid backup done by TWRP.
But the phone did not start at the reboot.
I then had to reinstall the update with the method described above to get the working phone back
Why did Nandroid backup with TWRP not correctly restore the phone?
Many thanks to anyone can help me
https://forum.xda-developers.com/showthread.php?p=72448182
There is a link to a rom in this post. In that zip you will find recovery.img. Flash it with adb, like you flashed twrp.
Then you can flash the last M official rom, and subsequently the first and last N roms.
That's the way I did it. I had to end up wiping data, to make it work correctly.
I'm also looking for a Nougat recovery.img.
I wouldn't like to go thru all the process again if there is another update.
Good luck.
Sent from my ASUS_Z01HD using Tapatalk
betche99 said:
https://forum.xda-developers.com/showthread.php?p=72448182
There is a link to a rom in this post. In that zip you will find recovery.img. Flash it with adb, like you flashed twrp.
Then you can flash the last M official rom, and subsequently the first and last N roms.
That's the way I did it. I had to end up wiping data, to make it work correctly.
I'm also looking for a Nougat recovery.img.
I wouldn't like to go thru all the process again if there is another update.
Good luck.
Sent from my ASUS_Z01HD using Tapatalk
Click to expand...
Click to collapse
I already downloaded that file but i didn't find any recovery.img file inside.
I try again
Many thanks :good::good::good:
johnjohnmel said:
I already downloaded that file but i didn't find any recovery.img file inside.
I try again
Many thanks :good::good::good:
Click to expand...
Click to collapse
i think you need flash full firmware bro ,
1. Download newer version firmware
2. You need Convert system.New.DAT to system.img
3. Move system.img and boot.img to minimal adb & fastboot folder
4. Open minimal adb & fastboot
5. Flash boot.img and system.img
halim_wijaya58 said:
2. You need Convert system.New.DAT to system.img
Click to expand...
Click to collapse
Hi Halim
Can I change *.DAT to *.img? or I should convert DAT to IMG with special app.?
Hi all.
I have the same room and can't seem to upgrade to N does anyone have a solution?
halim_wijaya58 said:
i think you need flash full firmware bro ,
1. Download newer version firmware
2. You need Convert system.New.DAT to system.img
3. Move system.img and boot.img to minimal adb & fastboot folder
4. Open minimal adb & fastboot
5. Flash boot.img and system.img
Click to expand...
Click to collapse
Just to let you know I did this then downloaded each update from Asus website. You have to do it in order ie newest MM to oldest N to newest N. Takes a lot of time but it works. I now have N on my phone.
Thanks everyone for all your help.
mikejasonsmith said:
Just to let you know I did this then downloaded each update from Asus website. You have to do it in order ie newest MM to oldest N to newest N. Takes a lot of time but it works. I now have N on my phone.
Thanks everyone for all your help.
Click to expand...
Click to collapse
Boss, I have Asus Zenfone 3 Zoom. I want to update Android nougat. Please help me . Already I unlocked bootloader and convert CN to WW Rom ........
Please help me ....... Please help me....... Please help me
???
---------- Post added at 12:13 PM ---------- Previous post was at 12:10 PM ----------
mikejasonsmith said:
Just to let you know I did this then downloaded each update from Asus website. You have to do it in order ie newest MM to oldest N to newest N. Takes a lot of time but it works. I now have N on my phone.
Thanks everyone for all your help.
Click to expand...
Click to collapse
Boss, I have Asus Zenfone 3 Zoom. I want to update Android nougat. Please help me . Already I unlocked bootloader and convert CN to WW Rom ........
Please help me ....... Please help me....... Please help me
???
Dear boss , please give me Asus Zenfone 3 Zoom Nougat flashable Rom or any easy solutions........
???
After 11 hours trying out finally solved!!!
I originally just wanted to do a factory reset, and swiped then not only data/cache, but unfortunally - because of lack of expirience - also system partition. After that all the problems occured like described above and partitionally in https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970 (there was no OS anymore, twrp warned me this every time I wanted to power off, but I couldn't install the firmware again through fastboot neither through twrp -> install zip; have got error 7 or 6).
Afer a lot of fears and hours of trying aroud possibilities above as well as ideas from articles here:
https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970
https://www.getdroidtips.com/v20-31-49-2-nougat-asus-zenfone-3-zoom/
https://forum.xda-developers.com/ze...om-ze553kl-t3612990/post72448182#post72448182
https://forums.oneplus.net/threads/twrp-failed-to-mount-system-invalid-argument.508967/
https://android.stackexchange.com/questions/165370/restoring-system-partition-in-twrp
https://4pda.ru/forum/index.php?showtopic=810939&st=240#entry63616813
I have finally founded a solution!!! This is in FIRSTLY restoring original recovery and just then flashing the stock ROM. Here the steps to do for it:
a.) Download original stock rom (raw-version!) from https://cloud.mail.ru/public/HuMJ/wEybSNsQA (raw is to flash through AFT - asus flash tool) or from any other source you can find online; official name seems to be "WW-ZE553KL-20.31.49.2-MR2-user-20170620235128-release_raw.zip"
b.) Exctract and move recovery.img to your adb-folder on PC
c.) Boot your phone into fastboot/boot mode, connect to PC through USB-Cable
d.) Run cmd in adb folder, then type in the command "fastboot flash recovery recovery.img"
e.) Reboot and choose recovery mode - now you have no twrp anymore, but the original recovery menue
f.) Install update, which means, original stock from your sd-card.
Be happy!
It would be nice if you could give me feedback, whether my solution was helpful for you, because it took time to write it and hope it will usefull
figulus said:
I originally just wanted to do a factory reset, and swiped then not only data/cache, but unfortunally - because of lack of expirience - also system partition. After that all the problems occured like described above and partitionally in https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970 (there was no OS anymore, twrp warned me this every time I wanted to power off, but I couldn't install the firmware again through fastboot neither through twrp -> install zip; have got error 7 or 6).
Afer a lot of fears and hours of trying aroud possibilities above as well as ideas from articles here:
https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970
https://www.getdroidtips.com/v20-31-49-2-nougat-asus-zenfone-3-zoom/
https://forum.xda-developers.com/ze...om-ze553kl-t3612990/post72448182#post72448182
https://forums.oneplus.net/threads/twrp-failed-to-mount-system-invalid-argument.508967/
https://android.stackexchange.com/questions/165370/restoring-system-partition-in-twrp
https://4pda.ru/forum/index.php?showtopic=810939&st=240#entry63616813
I have finally founded a solution!!! This is in FIRSTLY restoring original recovery and just then flashing the stock ROM. Here the steps to do for it:
a.) Download original stock rom (raw-version!) from https://cloud.mail.ru/public/HuMJ/wEybSNsQA (raw is to flash through AFT - asus flash tool) or from any other source you can find online; official name seems to be "WW-ZE553KL-20.31.49.2-MR2-user-20170620235128-release_raw.zip"
b.) Exctract and move recovery.img to your adb-folder on PC
c.) Boot your phone into fastboot/boot mode, connect to PC through USB-Cable
d.) Run cmd in adb folder, then type in the command "fastboot flash recovery recovery.img"
e.) Reboot and choose recovery mode - now you have no twrp anymore, but the original recovery menue
f.) Install update, which means, original stock from your sd-card.
Be happy!
It would be nice if you could give me feedback, whether my solution was helpful for you, because it took time to write it and hope it will usefull
Click to expand...
Click to collapse
Boss,
This solutions can work with ASUS ZENFONE 3 ZOOM.........???
I have ZenFone 3 zoom. Already I successfully convert CN to WW Rom by following this introduction ... https://forum.xda-developers.com/zenfone-3-zoom/how-to/transfer-cn-rom-to-ww-rom-ze553kl-t3612990
But, I can't update android nougat any way. I convert system.new.dat to system.img...... And try to flash it but unfortunately that's not working......
Please help me .......:crying:
Yes, I did it with my Zenfone 3 Zoom (ze553kl). So, you have firstly to flash the original recovery - to find, as described, in the raw stock rom zip archive. Or, you can find all original recovery's also here: (not tested by myself) https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Copy recovery.img to adb-folder, then flash it in fastboot mode in the cmd with "fastboot flash recovery recovery.img". Also copy the original stock rom with Android N to your sd-card and put it into your phone.
Then reboot your phone into recovery - now you have no twrp anymore, but original recovery. Install now the zip with Android-N-stock-firmware from sd-card. Enjoy!
figulus said:
Yes, I did it with my Zenfone 3 Zoom (ze553kl). So, you have firstly to flash the original recovery - to find, as described, in the raw stock rom zip archive. Or, you can find all original recovery's also here: (not tested by myself) https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Copy recovery.img to adb-folder, then flash it in fastboot mode in the cmd with "fastboot flash recovery recovery.img". Also copy the original stock rom with Android N to your sd-card and put it into your phone.
Then reboot your phone into recovery - now you have no twrp anymore, but original recovery. Install now the zip with Android-N-stock-firmware from sd-card. Enjoy!
Click to expand...
Click to collapse
Boss ,
Thank you very much ...... Your solution absolutely excellent and work very well . I am very happy for your support . But unfortunately I found new problem on my phone ...... After update nougat a white line found on the display......
How can I solved it .......
Waiting for solution.......
Thanks again for your support ........
Glad to hear, that it worked for you as well. About white line I have no idea, but on other pages I have already seen somewhere, that other users also reported about this problem. Try to look at google "ze553kl update white line". You can also search a solution for ze552kl instead of ze553kl, because, as far as I know, the ze552kl (ZenFone 3, without "Zoom") is almost the same device, just with a little worse cam. Therefore, it seems to be longer on the market and to have more users, so there are also more solutions for problems which can occure to this device in the internet. Wish you a good luck!
figulus said:
I originally just wanted to do a factory reset, and swiped then not only data/cache, but unfortunally - because of lack of expirience - also system partition. After that all the problems occured like described above and partitionally in https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970 (there was no OS anymore, twrp warned me this every time I wanted to power off, but I couldn't install the firmware again through fastboot neither through twrp -> install zip; have got error 7 or 6).
Afer a lot of fears and hours of trying aroud possibilities above as well as ideas from articles here:
https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970
https://www.getdroidtips.com/v20-31-49-2-nougat-asus-zenfone-3-zoom/
https://forum.xda-developers.com/ze...om-ze553kl-t3612990/post72448182#post72448182
https://forums.oneplus.net/threads/twrp-failed-to-mount-system-invalid-argument.508967/
https://android.stackexchange.com/questions/165370/restoring-system-partition-in-twrp
https://4pda.ru/forum/index.php?showtopic=810939&st=240#entry63616813
I have finally founded a solution!!! This is in FIRSTLY restoring original recovery and just then flashing the stock ROM. Here the steps to do for it:
a.) Download original stock rom (raw-version!) from https://cloud.mail.ru/public/HuMJ/wEybSNsQA (raw is to flash through AFT - asus flash tool) or from any other source you can find online; official name seems to be "WW-ZE553KL-20.31.49.2-MR2-user-20170620235128-release_raw.zip"
b.) Exctract and move recovery.img to your adb-folder on PC
c.) Boot your phone into fastboot/boot mode, connect to PC through USB-Cable
d.) Run cmd in adb folder, then type in the command "fastboot flash recovery recovery.img"
e.) Reboot and choose recovery mode - now you have no twrp anymore, but the original recovery menue
f.) Install update, which means, original stock from your sd-card.
Be happy!
It would be nice if you could give me feedback, whether my solution was helpful for you, because it took time to write it and hope it will usefull
Click to expand...
Click to collapse
Very helpful, thanks!
I must've messed something up when I flashed TWRP.
TWRP ran fine, but when I tried to start it up, it stayed stuck at the Android logo.
Then errors popped up when I tried to install the stock rom through TWRP.
I never would've thought or had the guts to restore stock recovery first.
This should get its own thread.
Edit: I think my mistake was unchecking "Mount system partition read-only."
halim_wijaya58 said:
i think you need flash full firmware bro ,
1. Download newer version firmware
2. You need Convert system.New.DAT to system.img
3. Move system.img and boot.img to minimal adb & fastboot folder
4. Open minimal adb & fastboot
5. Flash boot.img and system.img
Click to expand...
Click to collapse
After many days i finally found enough time to try to use your tips.
I tried to convert system.New.DAT to system.img but without success using this program Autotool 3.0
http://www.droidviews.com/convert-and-extract-system-img-and-system-new-dat-files-on-windows/
After this attempt i used a ROM provided by chinese store to flash its content :
system.img
boot.img
recovery.img
Original recovery.img is essential to install other updates.
After that i tried to install other updates recognized directly starting by phone but always without success.
So i have had to install updates using original recovery tool.
Now i got Android 7.1.1 last version installed on my phone but it's impossible to use
TWRP recovery tool.
Obviously it's possible to install TWRP instead of original recovery tool and also possible to make a nandroid backup
but it's impossible to use it to install original ROMs released from Asus and it's not possible
to use to restore nandroid backups.
Is it eventually possible to use a custom ROM ? If it's, which one and possibly compatible with TWRP ?
i solved issue of update, but TWRP ?
halim_wijaya58 said:
i think you need flash full firmware bro ,
1. Download newer version firmware
2. You need Convert system.New.DAT to system.img
3. Move system.img and boot.img to minimal adb & fastboot folder
4. Open minimal adb & fastboot
5. Flash boot.img and system.img
Click to expand...
Click to collapse
After many days I finally found enough time to try to update my Asus Zenfone 3 Zoom to Android Nougat.
To solve the issue, I used an original Rom from the Chinese store because it contains useful files for purpose without any conversion:
boot.img
system.img
recovery.img
I flashed all 3 IMG files.
Recovery.img that it's necessary to get original recovery without which any update can be done.
You must use a microSD and the original recovery tool to be able to upgrade your system.
The problem is that it does not seem possible to use TWRP. It is possible to install it in place of the original recovery and you can do also a nandroid backup but in practice you can not use it to install any updates and restore any nandroid backups.
Is there a custom rom that you can use instead of the original one?
SUJAN SN HW said:
Boss,
This solutions can work with ASUS ZENFONE 3 ZOOM.........???
I have ZenFone 3 zoom. Already I successfully convert CN to WW Rom by following this introduction ... https://forum.xda-developers.com/zenfone-3-zoom/how-to/transfer-cn-rom-to-ww-rom-ze553kl-t3612990
But, I can't update android nougat any way. I convert system.new.dat to system.img...... And try to flash it but unfortunately that's not working......
Please help me .......:crying:
Click to expand...
Click to collapse
how did you convert the .dat to .img?
josejbs said:
how did you convert the .dat to .img?
Click to expand...
Click to collapse
Here's a link to the tool
https://forum.xda-developers.com/android/general/tools-extract-dat-t3467581
I wanted to relock my Mi A1 but forgot to backup the stock boot image. Searched the monthly ROM update thread but it's not there yet.
Anyone got it?
Thanks!
Edit:
My bad, it was June patch (OPM1.171019.019.V9.6.3.0.ODHMIFE)
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
i need stock boot image for july patch to
I want to update to August but I have already rooted Magisk and I uninstalled it first which happened to be uncommand, because it might boot. img patch has overwritten boot.img default.
for the link above I do not understand why it is so large in size even though the img boot that has been patched is less than 5MB.
please help
nirvanarahadian said:
I want to update to August but I have already rooted Magisk and I uninstalled it first which happened to be uncommand, because it might boot. img patch has overwritten boot.img default.
for the link above I do not understand why it is so large in size even though the img boot that has been patched is less than 5MB.
please help
Click to expand...
Click to collapse
it's the entire rom, not only the boot image, that's why it is so large in size
Done
smsporto said:
it's the entire rom, not only the boot image, that's why it is so large in size
Click to expand...
Click to collapse
Done i downloaded fastboot in here https://forum.xda-developers.com/mi...-ota-links-t3718542/post74828108#post74828108, i download Android 8.1.0 [OPM1.171019.026.V9.6.4.0.ODHMIFE] (fastboot image) and i do flash with cmd boot.img. its work , not uncommand anymore, and i did an experiment with restarting my phone and stock boot img is only temporary and returns uncommand. how to fix it?,is it safe if i immediately update to the latest patch from OTA, the thing that is feared if booting will return like that and i'm confused looking for boot.img for august patch
nirvanarahadian said:
Done i downloaded fastboot in here https://forum.xda-developers.com/mi...ota-links-t3718542/post74828108#post74828108, i download Android 8.1.0 [OPM1.171019.026.V9.6.4.0.ODHMIFE] (fastboot image) and i do flash with cmd boot.img. its work , not uncommand anymore, and i did an experiment with restarting my phone and stock boot img is only temporary and returns uncommand. how to fix it?,is it safe if i immediately update to the latest patch from OTA, the thing that is feared if booting will return like that and i'm confused looking for boot.img for august patch
Click to expand...
Click to collapse
If u are sure that u haven't touched the system partition then u can try to update via OTA. Make sure u flashed and not only booted the downloaded boot.img from V9.6.4.0 ROM. I guess it's better to download the latest version from here:
https://drive.google.com/drive/mobile/folders/1dw87qgRNGxfj7UZduHK91LE6X1Xs7CWL
Then do a clean flash and install the entire ROM with fastboot.
"'*"*"
I've done flashing while on the way and I'm waiting. My cellphone suddenly turns on and it looks like it's doing a factory format. and I just updated it to August. all my data is lost even though the user data has been secured and the flashing process has not finished
Somehow I managed to lose my Recovery Of the Syszem.img and Vendor.img . If any of you guys still has them and could send me these. This would safe me a lot of time. So Basically because I wanted to install a new gsi ROM , I would need at least a Vendor.Img for the Nokia 6.1 Plus. Thx, hope some of you can help me
suspectxxx said:
Somehow I managed to lose my Recovery Of the Syszem.img and Vendor.img . If any of you guys still has them and could send me these. This would safe me a lot of time. So Basically because I wanted to install a new gsi ROM , I would need at least a Vendor.Img for the Nokia 6.1 Plus. Thx, hope some of you can help me
Click to expand...
Click to collapse
https://r.tapatalk.com/shareLink?ur...share_tid=3874513&share_fid=3793&share_type=t
There is a download link on the first post for boot.img and vendor.img
Just download the gsi system image and flash from fastboot.
gaban05 said:
https://r.tapatalk.com/shareLink?ur...share_tid=3874513&share_fid=3793&share_type=t
There is a download link on the first post for boot.img and vendor.img
Just download the gsi system image and flash from fastboot.
Click to expand...
Click to collapse
Looks like the page is down do you have a mirror?
https://forum.xda-developers.com/no...ide-how-to-flash-generic-image-using-t3874513
DISCLAIMER
I have only tested this on my OnePlus8T Indian model - KB2001
Huge thanks to @topjohnwu for his magic.
YOU NEED TO UNLOCK YOUR BOOTLOADER!
In case you brick your device, use this unbrick guide
If you get into a boot-loop by flashing problematic magisk modules, consider using the patched recoveries from my post HERE to remove the modules.
Manual ROOT procedureSkip to step #6 and then #10 if you do not want to use the payload dumper tool and want to directly patch and flash the stock images for your variant and Build version!
If you haven't updated OxygenOS yet, download it via the system updater. It will be stored in /sdcard/.Ota folder in your internal storage ( /sdcard/.Ota/OnePlus8TOxygen_15.I.16_OTA_0160_all_2010150110_84be0c.zip )
The size should be >2GB. If it is not, it's probably an incremental OTA, not a full one. This guide will NOT work on incremental OTA Zips.
DO NOT Reboot or else you will lose the file
Copy the ZIP file over to your PC
Download the Payload Dumper
Alt dumper for windows only:
https://androidfilehost.com/?fid=818070582850510260
1.Put payload.bin to "payload_input" folder
2.Run payload_dumper.exe
3.Successfully extracted img files are in "payload_output" folder
Extract the zip in the folder where you downloaded the payload dumper.
Follow the instructions in the readme of payload dumper, and extract the OTA images:
Code:
python payload_dumper.py payload.bin
You will get a boot.img file in the output folder.
Proceed with installing the OxygenOS update and reboot the phone.
Download and install the latest magisk canary release to your phone : https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
Copy over the boot.img file created by payload_dumper to your internal storage
Open Magisk Manager > Select Install > "Select and patch a file"
Browse and select the boot.img file.
Magisk will create a patched boot.img file in /sdcard/Downloads/magisk_patched.img . Copy this file over to your PC.
Reboot to fastboot mode
Code:
adb reboot bootloader
Either flash the patched magisk_patched.img in the active slot or temporarily boot into it if you are skeptical.
I recommend to BOOT first and then perform a direct install via magisk as it is more reliable to patch the active slot.
To flash:
Code:
fastboot flash boot magisk_patched.img
To Temporarily boot into a rooted system (RECOMMENDED!!):
Code:
fastboot boot magisk_patched.img
If you used the fastboot BOOT method, next you'll have to open magisk manager again, and this time, perform a "Direct Install".
This will install magisk on the active boot slot and the next reboot will give you root.
How to update OTA and KEEP ROOT
It is advised to disable all magisk modules to be safe!
epr said:
- Go to System-Update
- Tap OK when the message that you are rooted appears
- Tap "Download and install"
- Wait until you are prompted to reboot - DO NOT REBOOT NOW!
- Open Magisk Manager, select install -> Install to inactive slot and start installation
- When Magisk has finished to install, reboot and you stay rooted with newest OTA.
Click to expand...
Click to collapse
For the curious / impatient, Here are the OTAs / boot images for the different 8T Versions
All patched images are removed to ensure users perform the steps 6 - 11 of the guide and also not trust images patched by others.
To find your model and build to download the right file:
Bash:
adb shell getprop ro.product.model
KB2001
adb shell getprop ro.build.version.ota
OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
adb shell getprop ro.build.display.id
KB2001_15_201015
KB2000 / KB05?? - Chinese Variant
11.0.1.2 Hydrogen_15.H.16_OTA_0160_all_2010150101_4101
STOCK boot.img
KB2001 / KB05DA - Indian Variant
11.0.1.2 - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
STOCK boot.img (md5sum 3202f74ea45b906e9f0ea7cfcd81a014 )
11.0.2.3 - OnePlus8TOxygen_15.I.17_OTA_0170_all_2010240047
STOCK boot.img
11.0.3.4 - OnePlus8TOxygen_15.I.18_OTA_0180_all_2011010208
STOCK boot.img
11.0.4.5 - OnePlus8TOxygen_15.I.19_OTA_0190_all_2011101438_3032f.zip
STOCK boot.img
11.0.5.6 - OnePlus8TOxygen_15.I.20_OTA_0200_all_2011132215_feb8ca02ab.zip
KB05DA_11.0.5.6_BOOT_STOCK.img
11.0.6.8 - 11.0.10.10
KB05DA - India Folder on AFH
KB2003 / KB05BA - EU Variant
11.0.1.2 - OnePlus8TOxygen_15.E.17_GLO_0170_2010150108
STOCK boot.img (md5sum af4bb15254d38ab17167583eba23d5bd )
11.0.2.3 - OnePlus8TOxygen_15.E.18_OTA_0180_all_2010240038
STOCK boot.img
11.0.3.4 - OnePlus8TOxygen_15.E.19_OTA_0190_all_2011010157
Thanks @GraveDigger176 for the OTA zip
STOCK boot.img
11.0.4.5 - OnePlus8TOxygen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip
STOCK boot.img
11.0.5.6 - OnePlus8TOxygen_15.E.21_OTA_0210_all_2011132216_d2e1e993.zip
KB05BA_11.0.5.6_BOOT_STOCK.img
11.0.6.9 - 11.0.11.11
KB05BA - EU Folder on AFH
KB2005 / KB05AA - International Variant
Credit @northmendo @SAKO4444GODZ and @g96818
UPDATE:
For this variant please refer to this guide first! The OTA updates on this variant are partial and hence the rooting method isn't straightforward.
https://forum.xda-developers.com/showpost.php?p=83791723&postcount=95
Stock KB2005_15_201015 boot image SHA-1 D59C74767F74F4D7876BDCA930DEF23CCAA3FD2E
Patched KB2005_15_201015 boot image SHA-1 C1126E8057EF9FB25D80645B850374BBDDE983C5
OOS 11.0.3.4.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83893183&postcount=151
OOS 11.0.4.5.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83940123&postcount=210
OOS 11.0.5.6.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=84003695&postcount=258
OOS 11.0.6.8 - 11.0.11.11 : https://androidfilehost.com/user/?w=settings-dev-files&flid=329462
KB2007 / KB05CB - T-Mobile Variant
¯\_(ツ)_/¯
It's also a good practice to backup a few important partitions once you're rooted.
I used ADB shell, but you can use any terminal emulator from the play store (Termux)
adb shell
[email protected]:/ $ su
[email protected]:/ #
Now run:
Bash:
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/modemst2 of=/sdcard/modemst2.img
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/modemdump of=/sdcard/modemdump.img
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/persist of=/sdcard/persist.img
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/persist_bkp of=/sdcard/persist_bkp.img
Other Misc Stuff for my reference!
If after flashing a custom kernel, you see Sim cards not working:
FullOfHell said:
Be sure NOT to have a magisk patched image on both boot slots. That causes this behavior
Click to expand...
Click to collapse
Recovering lost app data after a failed boot:
Download and flash one of my adb-patched recoveries from my post here
Reboot to recovery, enter the password, open adb shell
Create a tar bundle of the app via tar -czvf MiXBackup.tgz data/data/com.mixplorer/silver and adb pull it to your system
*Or* the entire /data partition via tar --exclude /data/media/0 -czvf /data/media/0/data.tgz data/ (You CANNOT restore all of /data like this due to encryption stuff! but you can extract one app at a time and test)
Reinstall the app , reboot to recovery, adb push, and extract via tar xf MiXBackup.tar
Repo of Oxygen OS Builds
OOS Unbrick tool
ADB Enabled OOS Recovery
Re-locking the bootloader on the OnePlus 8t with a self-signed build of LOS
Widevine discussions
KB2000 / KB05?? - Chinese Variant
11.0.1.2 Hydrogen_15.H.16_OTA_0160_all_2010150101_4101
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB2000_Magisk_15.H.16_OTA_0160_all_2010150101_4101.img
KB2001 / KB05DA - Indian Variant
11.0.1.2 - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
STOCK boot.img (md5sum 3202f74ea45b906e9f0ea7cfcd81a014 )
MAGISK patched boot.img which you can flash/boot directly - KB2001_magisk_patched_11.0.1.2.KB05DA.img
11.0.2.3 - OnePlus8TOxygen_15.I.17_OTA_0170_all_2010240047
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB2001_magisk_patched_11.0.2.3.img
11.0.3.4 - OnePlus8TOxygen_15.I.18_OTA_0180_all_2011010208
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB05DA_11.0.3.4_BOOT_MAGISK.img
11.0.4.5 - OnePlus8TOxygen_15.I.19_OTA_0190_all_2011101438_3032f.zip
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB05DA_11.0.4.5_BOOT_MAGISK.img
11.0.5.6 - OnePlus8TOxygen_15.I.20_OTA_0200_all_2011132215_feb8ca02ab.zip
KB05DA_11.0.5.6_BOOT_STOCK.img
MAGISK patched boot.img which you can flash/boot directly - KB05DA_11.0.5.6_BOOT_MAGISK.img
KB2003 / KB05BA - EU Variant
11.0.1.2 - OnePlus8TOxygen_15.E.17_GLO_0170_2010150108
STOCK boot.img (md5sum af4bb15254d38ab17167583eba23d5bd )
MAGISK patched boot.img which you can flash/boot directly - boot_magisk_patched_11.0.1.2_EU.img
11.0.2.3 - OnePlus8TOxygen_15.E.18_OTA_0180_all_2010240038
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB2003_magisk_patched_11.0.2.3.img
11.0.3.4 - OnePlus8TOxygen_15.E.19_OTA_0190_all_2011010157
Thanks @GraveDigger176 for the OTA zip
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly (thanks @rage302) - magisk_patched_11.0.3.4_KB05BA.img
11.0.4.5 - OnePlus8TOxygen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly (thank @rage302) - magisk_patched_11.0.4.5_KB05BA.img
11.0.5.6 - OnePlus8TOxygen_15.E.21_OTA_0210_all_2011132216_d2e1e993.zip
KB05BA_11.0.5.6_BOOT_STOCK.img
MAGISK patched boot.img which you can flash/boot directly - magisk_patched_11.0.5.6_KB05BA.img
KB2005 / KB05AA - International Variant
Credit @northmendo @SAKO4444GODZ and @g96818
UPDATE:
For this variant please refer to this guide first! The OTA updates on this variant are partial and hence the rooting method isn't straightforward.
https://forum.xda-developers.com/showpost.php?p=83791723&postcount=95
Stock KB2005_15_201015 boot image SHA-1 D59C74767F74F4D7876BDCA930DEF23CCAA3FD2E
Patched KB2005_15_201015 boot image SHA-1 C1126E8057EF9FB25D80645B850374BBDDE983C5
OOS 11.0.3.4.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83893183&postcount=151
OOS 11.0.4.5.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83940123&postcount=210
OOS 11.0.5.6.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=84003695&postcount=258
I wonder if this same process would work for the KB2005 model? Unfortunately I was too quick to pull the trigger on the system update ??*
guess I'll be waiting a little longer
JWhetstone02 said:
I wonder if this same process would work for the KB2005 model? Unfortunately I was too quick to pull the trigger on the system update ??*
guess I'll be waiting a little longer
Click to expand...
Click to collapse
Yep, the procedure will stay the same. I would recommend waiting for someone to upload the OOS OTA zip or Oneplus to provide a direct download link.
However, if you are on the same build version, you try to patch the KB2001 boot.img and just use the fastboot boot method instead of flashing the patched image.
If it boots, you're in luck. If it doesn't, force reboot back into stock OOS.
Would be nice if someone can do this with the european version too. Maybe I can do it tomorrow but only if the dumper tool works on windows. Any idea on that?
5nickers said:
Would be nice if someone can do this with the european version too. Maybe I can do it tomorrow but only if the dumper tool works on windows. Any idea on that?
Click to expand...
Click to collapse
Yes it should work. All you need is to have python and the dependencies installed. It's listed in the readme of the dumper.
You can also use this one I found from the OnePlus NORD thread
https://androidfilehost.com/?fid=818070582850510260
DroidFreak32 said:
Yes it should work. All you need is to have python and the dependencies installed. It's listed in the readme of the dumper.
You can also use this one I found from the OnePlus NORD thread
https://androidfilehost.com/?fid=818070582850510260
Click to expand...
Click to collapse
Cool, guess I'll be doing that tomorrow after I get my phone. If it works I'm gonna upload the modified boot image here for everyone else
5nickers said:
Cool, guess I'll be doing that tomorrow after I get my phone. If it works I'm gonna upload the modified boot image here for everyone else
Click to expand...
Click to collapse
Also share the OTA zip too, please
If anyone can provide the OTA or patched img for the KB2005 that would've great, I was too quick to update [emoji2363]
Oh well, I guess I'll need to wait a little longer
Sent from my KB2005 using Tapatalk
DroidFreak32 said:
Yes it should work. All you need is to have python and the dependencies installed. It's listed in the readme of the dumper.
You can also use this one I found from the OnePlus NORD thread
https://androidfilehost.com/?fid=818070582850510260
Click to expand...
Click to collapse
After rooting and making the safetynet pass, does the widevine remains L1 like OP8 and OP8Pro? Or it becomes L3 like older OP devices?
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Wykillin said:
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Click to expand...
Click to collapse
Here is the boot.img extracted from your OTA:
https://drive.google.com/file/d/1jxf6EBSU6-8TuIUV_vN5ABiy-bUA38L1/view?usp=sharing
epr said:
Here is the boot.img extracted from your OTA:
https://drive.google.com/file/d/1jxf6EBSU6-8TuIUV_vN5ABiy-bUA38L1/view?usp=sharing
Click to expand...
Click to collapse
Wykillin said:
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Click to expand...
Click to collapse
What model is this for? ... Or would it matter?
Yeah please clearly state which version all these OTAs are from.
5nickers said:
Yeah please clearly state which version all these OTAs are from.
Click to expand...
Click to collapse
Just wanted to give Wykillin a little help...
Payload.properties from his OTA says: ota_target_version=OnePlus8TOxygen_15.O.16_GLO_0160_2010150057
Hope this makes it a little bit clearer...
Wykillin said:
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Click to expand...
Click to collapse
Yes, you'll need to have the original boot.img as this is just an incremental OTA, not a full one.
I will add a note in the OP as well to not use incremental OTA files.
epr said:
Here is the boot.img extracted from your OTA:
https://drive.google.com/file/d/1jxf6EBSU6-8TuIUV_vN5ABiy-bUA38L1/view?usp=sharing
Click to expand...
Click to collapse
I wouldn't use this image. It cannot be just 4.4 MB in size. I believe it is a partial extract as the OTA zip is just incremental, not a full ~2GB OTA
DroidFreak32 said:
Yes, you'll need to have the original boot.img as this is just an incremental OTA, not a full one.
I will add a note in the OP as well to not use incremental OTA files.
I wouldn't use this image. It cannot be just 4.4 MB in size. I believe it is a partial extract as the OTA zip is just incremental, not a full ~2GB OTA
Click to expand...
Click to collapse
Hi. Could you please answer my earlier question? Thank you
theincognito said:
Hi. Could you please answer my earlier question? Thank you
Click to expand...
Click to collapse
It's l3 unfortunately.
I didn't know op8 could keep it at l1! I would've bought that otherwise!
DroidFreak32 said:
It's l3 unfortunately.
I didn't know op8 could keep it at l1! I would've bought that otherwise!
Click to expand...
Click to collapse
Yeah. Both OP8 and OP8 Pro can retain L1
DroidFreak32 said:
PS: For the curious / impatient, I have uploaded the OTA ZIP here (md5sum d1a944205b91898a84b082c57ebac5a8 ):
https://drive.google.com/file/d/18kTOttFEfQN04JHt_7bkoHN3MWa4ZKo4/view
Click to expand...
Click to collapse
I am about to receive my China version of OnePlus 8T. Since the Global ROM is not yet released by OnePlus, if I flash this full OTA will it work? I want to replace the stock HydrogenOS with OxygenOS.
zellleonhart said:
I am about to receive my China version of OnePlus 8T. Since the Global ROM is not yet released by OnePlus, if I flash this full OTA will it work? I want to replace the stock HydrogenOS with OxygenOS.
Click to expand...
Click to collapse
It will. Though I suggest that you flash the EU variant over the Indian variant (cleanest OOS variant).
---------- Post added at 09:07 PM ---------- Previous post was at 08:49 PM ----------
@DroidFreak32
Magisk patched boot image for OOS 11.0.1.2 EU variant (from the full OTA zip - OnePlus8TOxygen_15.E.17_OTA_0170_all_2010150108_77edc51b51680.zip)
https://androidfilehost.com/?fid=10763459528675567936