Database Develop

[ROM][5.0 Lollipop] AOSP build

Welcome to Lollipop
Clean install with custom recovery (TWRP) (recommended)
Download the following files:
aosp_mako-ota-eng.5.0.zip or aosp_mako-ota-eng-preroot.5.0.zip (if you want to have root*) (mirrors, thanks to dorqus)
* In case you have already downloaded aosp_mako-ota-eng.5.0.zip you can also flash aosp_mako-boot-root.5.0.zip to prepare for root
optional: BETA-SuperSU-v2.19.zip
defcon-L-gapps-v2.zip
Recommended: Backup your apps:
Code:
adb backup -apk -obb -all -system
Recommend: Backup your internal storage (see FAQ below for the reason). Either copy all files in Explorer or use adb:
Code:
adb pull /sdcard/
Boot to recovery
Recommend: Factory reset. Warning: All your apps and app data will be deleted! Make sure you have a backup!
Recommend: Format/wipe internal storage (see FAQ below for the reason). Warning: All your files will be deleted! Make sure you have a backup!
Format/wipe system
Unmount system
Install aosp_mako-ota-eng.5.0.zip (or aosp_mako-ota-eng-preroot.5.0.zip)
Install gapps-lp-20141105-signed.zip
Optional: Install BETA-SuperSU-v2.19.zip
Reboot
Have a break and don't panic! The first boot can take 5 to 10 minutes
Optional: Recover from backup:
Code:
adb restore backup.ab
Optional: Copy your files back to internal storage
Clean install with fastboot
You won't have GApps this way ...
WARNING: If you flash userdata.img, all your data will be gone! Even the files on internal storage!
Download the images
boot.img or boot-root.img (prepared for root, you still have to install SuperSU somehow...)
system.img
Optionalrecovery.img
Optional, should be empty: cache.img
Optional, should be empty: userdata.img
Boot to bootloader
Flash
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
FAQ
Oh no, all my files are lost!!!
or
Why should I wipe internal storage?
5.0 uses a much stricter SELinux policy than most 4.4 ROMs do. Normally the first boot should migrate all the things (and it did for me, but only the first time). If not, you are no longer able to see your internal storage (aka SD card). E.g. Camera says: Please enter an SD card. To fix that problem you have to either wipe the internal storage and let Android recreate the file structure. (You can before still access the /sdcard in TWRP for a backup with adb). Or you can fix the SELinux context with the following command (in recovery):
Code:
adb shell
IFS="
"
for i in `find /data/media`; do chcon u:object_r:media_rw_data_file:s0 "$i"; done
Is this the official update from Google?
No, this is an AOSP build from the latest Lollipop sources.
Do I need to be on stock 4.4.4 before flashing?
No, but you should consider doing a factory reset otherwise.
Can I do a dirty upgrade?
Yes, you can. But you might spend a lot of time in fixing F/Cs...
Can this ROM be rooted?
Yes, just flash aosp_mako-ota-eng-preroot.5.0.zip (or aosp_mako-boot-root.5.0.zip) and BETA-SuperSU-v2.19.zip
Known issues
General:
No access to internal storage, even not with adb or as root. Seems like SELinux is misconfigured. See FAQ for solution
Due to incomplete GApps:
WLAN/mobile based location isn't working
No face unlock (libs missing) works with new gapps
calendar sync provider missing works with new gapps
How to build
This ROM is build with the original Google sources:
Code:
repo init -u https://android.googlesource.com/platform/manifest -b android-5.0.0_r2
See https://source.android.com/source/building.html for build instructions.
Binary blobs are taken from https://developers.google.com/android/nexus/blobs-preview.
The kernel is the default precompiled kernel provided by Google (can be found in device/lge/mako-kernel/kernel).
To prepare for root, you have to remove the seclabel line from system/core/rootdir/init.rc:
Code:
service flash_recovery /system/bin/install-recovery.sh
class main
seclabel u:r:install_recovery:s0
oneshot

C-o-M said:
Welcome to Lollipop
Download: https://drive.google.com/file/d/0B10l7w-7w3boRzlmT1pxSFF5YlU/view?usp=sharing
We don't have 5.0 gapps yet, so I flashed pa-gapps-modular-mini-4.4.4-20140930 (after removing the version check in updater-script). Works great so far.
I'm running a dirty upgrade from 4.4.4, no issues so far. Just format /system, flash ota.zip and gapps, wipe cache and enjoy.
Click to expand...
Click to collapse
I guess this requires me to be running stock 4.4.4 before flashing.
Could you post the system.img , userdata.img , cache.img , boot.img and recovery.img so I could flash it via fastboot.
Thanks

Amazing work!!
can you upload modified pa gapps??
or any instruction to modify it?

Good job!
trasteando...

is this from google ?

richardyusan said:
is this from google ?
Click to expand...
Click to collapse
all ROM's are from Google's base dude
maybe what you really mean is from stock L image?

is this rooted guys?

Is this official aosp build and can I clean flash?

Please explain how to root tris ROM?!

C-o-M said:
Welcome to Lollipop
Download: https://drive.google.com/file/d/0B10l7w-7w3boRzlmT1pxSFF5YlU/view?usp=sharing
We don't have 5.0 gapps yet, so I flashed pa-gapps-modular-mini-4.4.4-20140930 (after removing the version check in updater-script). Works great so far.
I'm running a dirty upgrade from 4.4.4, no issues so far. Just format /system, flash ota.zip and gapps, wipe cache and enjoy.
Click to expand...
Click to collapse
dirty flash from stock 4.4.4 ?
also can you provide a link to working gapps

great job , waiting issues from other

groovepeppy said:
all ROM's are from Google's base dude
maybe what you really mean is from stock L image?
Click to expand...
Click to collapse
lol you don't say
we know every android build is from google
is this official from google or not?

richardyusan said:
lol you don't say
we know every android build is from google
is this official from google or not?
Click to expand...
Click to collapse
It's in the topic dude.
AOSP not OTA

Bladyle said:
It's in the topic dude.
AOSP not OTA
Click to expand...
Click to collapse
What he means is this proper aosp fully working 100% and has latest kernel and everything?

SRun said:
What he means is this proper aosp fully working 100% and has latest kernel and everything?
Click to expand...
Click to collapse
it will be 100% working when we have OTA or after some time with AOSP when developers fix all the missing binaries, libraries, bugs and etc.

SRun said:
What he means is this proper aosp fully working 100% and has latest kernel and everything?
Click to expand...
Click to collapse
i think we should install the rom and experience

Bugs? Root? Smooth? Please post bugs and stuff

I'm returning to stock 4.4.4 as I type this, and then I will do a clean flash of this 5.0 AOSP build and see how I go. Shall report back here upon completion.

richardyusan said:
lol you don't say
we know every android build is from google
is this official from google or not?
Click to expand...
Click to collapse
understood "sam"
that's why i wrote "maybe what you really mean is from stock L image?"

how to i disable the version check to install gapps?
anyway to get the official launcher? the one in this rom looks like 4.4 stock

How can I determine what bootloader version I have?

My intent was to end up with Fire OS 5.3.2 & 5.1.2's bootloaders.
I have a rooted (SuperSU) Fire OS 5.3.2, (Alexa works ),
with Play Store, Flashfire, Busybox, xposed framework,
removed lockscreen ads, blocked updates.
I started with a Fire 7 on Fire OS 5.1.3 downgraded to 5.1.2 via adb sideload.
I then used Supertool to root / SuperSU; installed Flashfire to try to
run 5.3.2 rooted.
On Flashfire I installed these zip's
update-kindle-global-37.5.6.0_user_560177220---5-3-2.zip
fire_boot_5.1.2-5.4.2_542168620.zip
UPDATE-SuperSU-v2.46.zip
open_gapps-arm-5.1-pico-20161125.zip
xposed-v87-sdk22-arm.zip
I did lose busybox, but I reinstalled from Play Store fine.
How can I tell what bootloader I have [5.1.2 vs 5.3.1]?

fuzzynco said:
My intent was to end up with Fire OS 5.3.2 & 5.1.2's bootloaders.
I have a rooted (SuperSU) Fire OS 5.3.2, (Alexa works ),
with Play Store, Flashfire, Busybox, xposed framework,
removed lockscreen ads, blocked updates.
I started with a Fire 7 on Fire OS 5.1.3 downgraded to 5.1.2 via adb sideload.
I then used Supertool to root / SuperSU; installed Flashfire to try to
run 5.3.2 rooted.
On Flashfire I installed these zip's
update-kindle-global-37.5.6.0_user_560177220---5-3-2.zip
fire_boot_5.1.2-5.4.2_542168620.zip
UPDATE-SuperSU-v2.46.zip
open_gapps-arm-5.1-pico-20161125.zip
xposed-v87-sdk22-arm.zip
I did lose busybox, but I reinstalled from Play Store fine.
How can I tell what bootloader I have [5.1.2 vs 5.3.1]?
Click to expand...
Click to collapse
AFAIK there is no way to directly query bootloader version.
Unless modified the first zip you flashed contains the relevant bootloader/kernel. Whether they were actually applied/updated by FlashFire is unknown (at least to me).

Update to bootloader query 5.1.2 vs 5.3.1
Extracted from 'fire_boot_5.1.2-5.4.2_542168620.zip"
The special that was supposed to 're-replace' the bootloaders, kernel and native recovery
with the versions from Fire OS 5.1.2. So should further recovery be needed, the native recovery
system's ADB Sideload, (of a full 5.1.2 Fire OS), should work.
product=ford
package=com.amazon.ford.android.os
version_name=Fire OS 5.1.2 (542168620)
version_number=542168620
description=full_ford-user 5.1.1 LMY47O 37.5.4.2_user_542168620 release-keys
key_type=release-keys
sign_type=release
binary_type=full
Click to expand...
Click to collapse
getprop("ro.product.device") == "ford" || abort("This package is for "ford" devices; this is a "" + getprop("ro.product.device") + "".");
show_progress(0.750000, 0);
#ui_print("Patching system image unconditionally...");
#block_image_update("/dev/block/platform/mtk-msdc.0/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
#package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/by-name/boot");
show_progress(0.200000, 10);
package_extract_file("images/lk.bin", "/dev/block/platform/mtk-msdc.0/by-name/UBOOT");
package_extract_file("images/tz.img", "/dev/block/platform/mtk-msdc.0/by-name/TEE1");
package_extract_file("images/recovery.img", "/dev/block/platform/mtk-msdc.0/by-name/recovery");
#
# Edify script to copy the correct preloader image
#
# check if production device
if (getprop("ro.boot.secure_cpu") == "1")
then
ui_print("Copying preloader_prod.img to boot partition 0 for secure device...");
package_extract_file("images/preloader_prod.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
else
if (getprop("ro.boot.secure_cpu") == "0")
then
ui_print("Copying preloader.img to boot partition 0 for unsecure device...");
package_extract_file("images/preloader.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
else
if ("0025001000000015" == read_file_str("/proc/idme/board_id") ||
"0025001000010015" == read_file_str("/proc/idme/board_id") ||
"0025001010000015" == read_file_str("/proc/idme/board_id") ||
"0025001010010015" == read_file_str("/proc/idme/board_id") ||
"0025001020000015" == read_file_str("/proc/idme/board_id"))
then
ui_print("Copying preloader.img to boot partition 0 for unsecure device...");
package_extract_file("images/preloader.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
else
ui_print("Copying preloader_prod.img to boot partition 0 for secure device...");
package_extract_file("images/preloader_prod.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
endif;
endif;
endif;
#
# Edify script to copy the correct logo image
#
ui_print("Copying logo.bin to LOGO partition ...");
package_extract_file("images/logo.bin", "/dev/block/platform/mtk-msdc.0/by-name/LOGO");
package_extract_file("META-INF/com/amazon/android/target.blocklist", "/cache/recovery/last_blocklist");
set_metadata("/cache/recovery/last_blocklist", "uid", 0, "gid", 0, "mode", 0444, "capabilities", 0x0);
Click to expand...
Click to collapse
All the tools I can find tell me I have a working Fire OS 5.3.2, with SuperSU Pro root, Flashfire Pro,
Titanium Backup Pro, and having re-run Supertool, Play Store, blocked updates, etc.
I'm guessing because I rooted first on 5.1.2, and used Flashfire to install first 5.3.2 then
the required parts of 5.1.2 to have the bootloaders think it is a 5.1.2 system
then SuperSU via Flashfire all in one 'session' I ended up with the 'hybrid'
system I have?

fuzzynco said:
I'm guessing because I rooted first on 5.1.2, and used Flashfire to install first 5.3.2 then
the required parts of 5.1.2 to have the bootloaders think it is a 5.1.2 system
then SuperSU via Flashfire all in one 'session' I ended up with the 'hybrid'
system I have?
Click to expand...
Click to collapse
Possibly. 5.1.2 bootloader has no special 'powers' so there is no benign check you can run to confirm. The only definitive test is sideloading 5.1.2 which will brick device if bootloader/kernel is not in sync.

Can you run the "whichpl" script on your Fire? It should identify the preloader installed: https://drive.google.com/drive/folders/0B214JJmar6j-VllGSWNXTS1mSU0?usp=sharing

steve8x8 said:
Can you run the "whichpl" script on your Fire? It should identify the preloader installed: https://drive.google.com/drive/folders/0B214JJmar6j-VllGSWNXTS1mSU0?usp=sharing
Click to expand...
Click to collapse
yes -- worked - reported fireOS 5.1.2 (which is what I'd hoped I'd see).
Working with 5.1.2's bootloaders / boot and 5.3.2's /system.
Rooted with SuperSU via flashfire (from actual fireOS 5.1.2
/system, after rooting with Supertool & kingroot / supersu).

Good to know the script works for other fireOS versions than mine
I've got a Fire still running 5.1.1, with all its vulnerabilities, and might follow the same track to bump it to 5.3.1 at least.
Still wondering whether there might be a generic "patch" to the updater script (which has been unchanged since 5.1.1) and the images/ directory inside the zip, i.e. a "cookbook recipe" to transform an existing ROM into an upgrade zip that doesn't touch the bootloader parts, making the fire_boot zips obsolete (and which would work with *every* rooted fw version)... I'll have another look when... um, later...

steve8x8 said:
Good to know the script works for other fireOS versions than mine
I've got a Fire still running 5.1.1, with all its vulnerabilities, and might follow the same track to bump it to 5.3.1 at least.
Still wondering whether there might be a generic "patch" to the updater script (which has been unchanged since 5.1.1) and the images/ directory inside the zip, i.e. a "cookbook recipe" to transform an existing ROM into an upgrade zip that doesn't touch the bootloader parts, making the fire_boot zips obsolete (and which would work with *every* rooted fw version)... I'll have another look when... um, later...
Click to expand...
Click to collapse
FYI - a tool was created for 3rd gen HDX devices that stripped out bootloader, recovery and other components from the generic Amazon update package leaving just FireOS which could be flashed w/TWRP (presumably FlashFire could also be used) without messing with the other partitions. While it worked a treat few users took advantage of the capability preferring to go the custom ROM route instead. I can dig up the link if interested.

Thanks for the offer - I try to find a spare hour or two (to have a look at the FW packages) as soon as I got my new specs - coding/scripting without them has become more and more dangerous

Still scratching my head, first bald spots start to appear...
fuzzynco said:
On Flashfire I installed these zip's
update-kindle-global-37.5.6.0_user_560177220---5-3-2.zip
fire_boot_5.1.2-5.4.2_542168620.zip
UPDATE-SuperSU-v2.46.zip
open_gapps-arm-5.1-pico-20161125.zip
xposed-v87-sdk22-arm.zip
Click to expand...
Click to collapse
I had a closer look at the updater-script inside the fire-boot package, and what has been changed compared to the original 5.1.2 one.
Not too much: bootloader files are written (back, replacing the ones of the later ROM :good: ); system, of course, doesn't get written :good: ; the boot.img (OS kernel) doesn't get written :good: ; a recovery shows up though . The latter is worrying me - it is identical between 5.1.1 and 5.1.2 versions while boot.img of the original ROMs aren't - how has it been created? and why does it have to be replaced at all? (Stock doesn't seem to care. Yes, I know that recovery is signed and cannot be replaced at random. So this one must be special.)
Also, there are two lines at the very end of the updater-script providing a file /cache/recovery/last_blocklist - which contains checksums of the components of the (original) 5.1.2 ROM as a whole. These (and more info) wouldn't match a later ROM like the 5.3.2 you had installed before. Does this mean that the recovery will choke on it *if* /cache doesn't get wiped (I suppose you're doing that - but that would make the last two lines in the script obsolete)?
I may be mistaken but a bootloader-less update, based on *any* stock ROM, would cut down the updater-script to the first seven (7) lines - install system, and boot.img, done. Sounds too simple. Where's my mistake? There must be one

steve8x8 said:
Can you run the "whichpl" script on your Fire? It should identify the preloader installed: https://drive.google.com/drive/folders/0B214JJmar6j-VllGSWNXTS1mSU0?usp=sharing
Click to expand...
Click to collapse
This script sounds like what I've been looking for to determine bootloader versions on numerous Fire tablets. Can you please share this script in a location that doesn't require a g00g account to get to it? Thanks.

[UNOFFICIAL][Recovery][Stock][tissot] TWRP 3.2.1-0 for Mi A1 (New installer)

What?
A TWRP bootable-image and installer ZIP for stock-based ROM's (i.e. not LOS 15.1) and maybe others (untested).
Based on:
Latest TWRP build provided by @pl_blaze
The official TWRP installation script for Pixel 2 by Dees_Troy (will install to both slots automatically - more resilient than the other TWRP script)
The IMG uses official kernel 8.1.10 so might be flashable (not tested!)
Not compatible with LineageOS 15.1 because it uses some custom update API that isn't in this TWRP. I considered using the LOS 15.1 TWRP build in this, but it's not compatible with stock encryption (it always thinks the passcode is wrong).
Full credits to @pl_blaze and Dees_Troy for this. I just packaged up something new and wrote clear instructions.
Why?
The old TWRP thread is not maintained and people keep asking/reporting the same questions/problems. I will try to keep this up to date as long as necessary. This is also a more robust installation script, using magiskboot binary to unpack/repack the boot image.
How?
Uninstall Magisk first if you have it installed, just to be safe. Or reflash stock boot.img. (Might not be necessary - a dirty flash worked OK for me but YMMV).
Fastboot boot (hotboot) any existing working TWRP image. Don't worry about working encryption/data, we only need kernel access. For example...
Code:
fastboot boot oreo_3.2.2_recovery.img
... which can be downloaded from Google Drive here (thanks to whoever shared this, I think it's a pl_blaze reshare).
Download attachment ZIP installer and flash in hot-booted TWRP (it will flash to both slots)
Reboot to Recovery and (re-)flash Magisk, if you use it.
Profit

@pl_blaze brother always thank you for the contributions that you do without coming to the light .and thanks for you @op to post working twrp for stock

this twrp will work on 7.1.2 ? i'm now on aex rom

Thanks @CosmicDan for starting this thread. I started to implement @pl_blaze changes into the official TWRP but I've been failing miserably (I'm a noob). Can you provide sources for the images?
I can't trust binaries floating all over the internet if it's not from a reliable dev. If you've compiled it yourself I'll give a try.

I reshare this twrp img on Telegram group,I tested it, works without problem
Flash of permaent twrp not tested by me
It's a good twrp!

CosmicDan said:
What?
A TWRP bootable-image and installer ZIP for stock-based ROM's (i.e. not LOS 15.1) and maybe others (untested).
Based on:
Latest TWRP build provided by @pl_blaze
The official TWRP installation script for Pixel 2 by Dees_Troy (will install to both slots automatically - more resilient than the other TWRP script)
The IMG uses official kernel 8.1.10 so might be flashable (not tested!)
Not compatible with LineageOS 15.1 because it uses some custom update API that isn't in this TWRP. I considered using the LOS 15.1 TWRP build in this, but it's not compatible with stock encryption (it always thinks the passcode is wrong).
Full credits to @pl_blaze and Dees_Troy for this. I just packaged up something new and wrote clear instructions.
Why?
The old TWRP thread is not maintained and people keep asking/reporting the same questions/problems. I will try to keep this up to date as long as necessary. This is also a more robust installation script, using magiskboot binary to unpack/repack the boot image.
How?
Uninstall Magisk first if you have it installed, just to be safe. Or reflash stock boot.img. (Might not be necessary - a dirty flash worked OK for me but YMMV).
Fastboot boot (hotboot) any existing working TWRP image. Don't worry about working encryption/data, we only need kernel access. For example...
Code:
fastboot boot oreo_3.2.2_recovery.img
... which can be downloaded from Google Drive here (thanks to whoever shared this, I think it's a pl_blaze reshare).
Download attachment ZIP installer and flash in hot-booted TWRP (it will flash to both slots)
Reboot to Recovery and (re-)flash Magisk, if you use it.
Profit
Click to expand...
Click to collapse
what does mean "hot boot", sorry am novice, Not even he could boot boot recovery from Minimal ADB and fastboot ,,, What am I doing wrong?
View attachment 4438212

teacapan said:
Fastboot boot (hotboot) anwhat does mean "hot boot", sorry am novice, Not even he could boot boot recovery from Minimal ADB and fastboot ,,, What am I doing wrong?
Click to expand...
Click to collapse
Hot boot means you are not flashing the recovery image just running it temporarily. Stock boot image is untouched in this process.
Run
fastboot devices
To check whether your device is connected.

alkesh95 said:
Hot boot means you are not flashing the recovery image just running it temporarily. Stock boot image is untouched in this process.
Run
fastboot devices
To check whether your device is connected.
Click to expand...
Click to collapse
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.

teacapan said:
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
Click to expand...
Click to collapse
Did you put your recovery into the fastboot forder?
Did you unpack the zip ?
Also check if the name of recovery image is the same

It's possible to make password for twrp

DELETED.

lef7er1s said:
Did you put your recovery into the fastboot forder?
Did you unpack the zip ?
Also check if the name of recovery image is the same
Click to expand...
Click to collapse
1-yes
2-yes
3-yes
Anyway thanks for try help me.

Yeah well, I'm still stuck where, some help would be very appreciated.
View attachment 4438552
View attachment 4438553

Polluktus said:
this twrp will work on 7.1.2 ? i'm now on aex rom
Click to expand...
Click to collapse
Not sure, I've only tested on stock Oreo. Try and and let us know!
atttoush said:
Thanks @CosmicDan for starting this thread. I started to implement @pl_blaze changes into the official TWRP but I've been failing miserably (I'm a noob). Can you provide sources for the images?
I can't trust binaries floating all over the internet if it's not from a reliable dev. If you've compiled it yourself I'll give a try.
Click to expand...
Click to collapse
Indeed, no I have not compiled it myself - just ripped from pl_blaze.
I have a Oreo source repo cloned now for other reasons, but I might try and compile TWRP myself. Although it's been a couple years since I've tried to compile device-specific stuff from an AOSP tree so I don't know how long that will take.
teacapan said:
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
Click to expand...
Click to collapse
Sounds like you just need to learn more about how to use console tools. You need to make sure the "fastboot boot filename.img" command will have a "filename.img" that matches the img filename in the current directory. This is just an example - substitute "filename.img" for the real filename. Use the CD command to change directory to where the img is.

teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
View attachment 4438552
View attachment 4438553
Click to expand...
Click to collapse
Try renaming the img file to something simpler like oreo_twrp.img
Edit: ah yes, the file you are pointing to has to be in the same directory where you opened cmd window, as cosmicdan stated above

CosmicDan said:
Indeed, no I have not compiled it myself - just ripped from pl_blaze.
I have a Oreo source repo cloned now for other reasons, but I might try and compile TWRP myself. Although it's been a couple years since I've tried to compile device-specific stuff from an AOSP tree so I don't know how long that will take.
Click to expand...
Click to collapse
Glad you open this thread. I'll wait for your compiled version to give it a try
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
I don't know man, these adb and fastboot binaries look old (2014?). Try to get recent ones. And repeat the process.

silv3rfox said:
Glad you open this thread. I'll wait for your compiled version to give it a try
I don't know man, these adb and fastboot binaries look old (2014?). Try to get recent ones. And repeat the process.
Click to expand...
Click to collapse
Thanks, i will.

teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
Before flashing recovery
CD C:\Users\YOUR_USERNAME\Desktop\Adb

teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
The name of the file is ending with .img, delete ending " .img ", see below that patched_boot without .img in the end

Thanks for this. I checked out the differences between this and the flashable zip I was using (twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester) and found this:
Code:
# write the new boot image to boot block
write_boot() {
print "Writing new boot image to memory..."
cd "$tmp"
if $use_dd; then
dd if=boot-new-a.img of="$boot_block"_a
[ $? = 0 ] || abort "Failed to write boot image A! You may need to restore your boot partition"
dd if=boot-new-b.img of="$boot_block"_b
[ $? = 0 ] || abort "Failed to write boot image B! You may need to restore your boot partition"
else
flash_image "$boot_block" boot-new.img
fi
[ $? = 0 ] || abort "Failed to write boot image! You may need to restore your boot partition"
}
This also flashes it into boot_a and boot_b correct?
What other differences does this have over that?

[GUIDE][OTA]Manually flashing ota over rooted system (Latest v309)

Things needed:
1. Unlocked and Asus Zenfone Max Pro M1 (why dafaq so long name?)
2. Stock rom (recovery/fastboot doesn't matter) i used this to updated to 305, get accordingly from here
3. Modified TWRP recovery
4. Ota package
Instructions:
1. Download the full rom and ota (in your phone, from second post or get from our telegram group)
2. After download gets completed, go to /data/cache and copy dlpkgfile somewhere in sdcard, and rename it to ota.zip
3. Extract ota.zip and go to META-INF\com\google\android , open updater-script in text editor and remove these lines from it
Code:
containprop(getprop("ro.product.device")) || abort("E3004: This package is for \"ASUS_X00TD\" devices; this is a \"" + getprop("ro.product.device") + "\".");
getprop("ro.build.asus.sku") == "WW" || abort("E3009: This package is for sku: \"WW\"; this is a sku: \"" + getprop("ro.build.asus.sku") + "\".");
ui_print("Source: Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.252-20180428:user/release-keys");
ui_print("Target: Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.305-20180521:user/release-keys");
ui_print("Verifying current system...");
containprop(getprop("ro.build.fingerprint")) ||
abort("E3001: Package expects build fingerprint of Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.252-20180428:user/release-keys or Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.305-20180521:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
i.e. everything till
Code:
apply_patch_check("EMMC:/dev/block/bootdevice/by-name/boot:47510824:9ca7a29f3b90af90492bfa0c07275390f72f397d:47502632:80fbccb727c484733397429a9df38a499dee67fe") || abort("E3005: \"EMMC:/dev/block/bootdevice/by-name/boot:47510824:9ca7a29f3b90af90492bfa0c07275390f72f397d:47502632:80fbccb727c484733397429a9df38a499dee67fe\" has unexpected contents.");
Save it and zip back the ota
NOTE: Skip step 4 if you have stock fastboot images
4. Extract stock rom zip and go to META-INF\com\google\android , open updater-script in text editor and remove these lines from it
Code:
(!less_than_int(1524926024, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Sat Apr 28 22:33:44 CST 2018) over newer build (" + getprop("ro.build.date") + ").");
containprop(getprop("ro.product.device")) || abort("E3004: This package is for \"ASUS_X00TD\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.252-20180428:user/release-keys");
show_progress(0.650000, 0);
i.e everything till
Code:
ui_print("Patching system image unconditionally...");
Once done, zip it back
5. Reboot to bootloader and flash system.img vendor.img boot.img and modified twrp.img if you have correct version of fastboot rom, otherwise, just flash the modified twrp.img and force reboot to recovery by pressing and holding volume down + power key
6. Once in recovery, flash the rom.zip you made and right after that flash the ota.zip, once done, make a backup of boot, modem, system image, vendor image
7. (OPTIONAL) if you had decrypted data partition before, flash normal twrp using current twrp or fastboot and flash decrypt.zip again
8. (OPTIONAL) if you want rooted system no twrp and easy ota updates for future, flash magisk and stock recovery using modified twrp and reboot. you'll be able to flash ota normally after this with root access.
Enjoy.
What to do on next ota?
1. Flash the modified twrp
2. Restore the backup you made in step 6
3. Edit the ota as explained in step 3
4. Flash the ota zip and make another backup of system image, vendor image, modem, and boot (also any other partition depending on the ota)
5. Do the optional steps as said in steps 7 and 8

Modified OTA Links:
From 252 to 305
From 305 to 309

Wow... I just came here to say someone to write this out.. and seeing it already posted just few hours ago..

can you please explain it with detail, dude.. newbie here

8. (OPTIONAL) if you want rooted system no twrp and easy ota updates for future, flash magisk and stock recovery using modified twrp and reboot. you'll be able to flash ota normally after this with root access.
Click to expand...
Click to collapse
So we dont need to flash the original boot.img if we choose this? Because Magisk modified the boot image....

dimedevil said:
So we dont need to flash the original boot.img if we choose this? Because Magisk modified the boot image....
Click to expand...
Click to collapse
Depends on ota, if it has patch or complete boot.img
You can flash magisk uninstaller to restore boot.img too
Sent from my ASUS_X00TD using Tapatalk

Step 2 : I cant find data folder in me internal storage! Plz help me out
---------- Post added at 06:16 AM ---------- Previous post was at 06:07 AM ----------
Where to find dlkgpfile??? I couldn't find it

Sudeep Duhoon said:
Modified OTA Links:
From 252 to 305
Click to expand...
Click to collapse
do you have this file before editing?

Sudeep Duhoon said:
Depends on ota, if it has patch or complete boot.img
You can flash magisk uninstaller to restore boot.img too
Sent from my ASUS_X00TD using Tapatalk
Click to expand...
Click to collapse
I see... but in my case, Magisk Uninstaller failed on TWRP and RWRP... error 1 it said...
So I'm going to try the 8th option... let's hope there's no problem flashing in the future...

please create video tutor easy to understand

.A.V.i.n.a.S.h. said:
Instead of doing the backup of the partitions & the restore before OTA, can I continue to modify full ROM + OTA and flash it.
Click to expand...
Click to collapse
Yes, full ota will work just fine
But if there is no full ota, backup and restore is the solution
Sent from my Phh-Treble with GApps using Tapatalk

.A.V.i.n.a.S.h. said:
Can you please clarify this final doubt.
If I go for Magisk+Stock recovery -
The Magisk update (like from v15.3 to v16.0) will effect the OTA or no.
Click to expand...
Click to collapse
if you flash magisk using modified twrp, and flash stock recovery afterwards
if there is complete boot.img in next ota, stock recovery will flash ota just fine, if there is patch for boot, ota will fail and you will have to flash stock boot.img using fastboot/modified twrp or flash magisk uninstaller by modified twrp.
.A.V.i.n.a.S.h. said:
So by step-7, I flash TWRP_unofficial and flash decrypt.zip
In step-8, flash TWRPnomount again over regular TWRP and flash magisk and stock recovery right.
Also should I stick with Magisk-16.0 or can I update Magisk without breaking OTA.
Click to expand...
Click to collapse
if you flash decrypt.zip you have to flash stock vendor.img before flashing next ota
both steps are optional and independent from each other, may break ota
also i am unable to understand what you are trying to achieve here. sorry.

Sudeep Duhoon said:
Things needed:
1. Unlocked and Asus Zenfone Max Pro M1 (why dafaq so long name?)
2. Stock rom (recovery/fastboot doesn't matter) i used this to updated to 305, get accordingly from here
3. Modified TWRP recovery
4. Ota package
Instructions:
1. Download the full rom and ota (in your phone, from second post or get from our telegram group)
2. After download gets completed, go to /data/cache and copy dlpkgfile somewhere in sdcard, and rename it to ota.zip
3. Extract ota.zip and go to META-INF\com\google\android , open updater-script in text editor and remove these lines from it
Code:
containprop(getprop("ro.product.device")) || abort("E3004: This package is for \"ASUS_X00TD\" devices; this is a \"" + getprop("ro.product.device") + "\".");
getprop("ro.build.asus.sku") == "WW" || abort("E3009: This package is for sku: \"WW\"; this is a sku: \"" + getprop("ro.build.asus.sku") + "\".");
ui_print("Source: Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.252-20180428:user/release-keys");
ui_print("Target: Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.305-20180521:user/release-keys");
ui_print("Verifying current system...");
containprop(getprop("ro.build.fingerprint")) ||
abort("E3001: Package expects build fingerprint of Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.252-20180428:user/release-keys or Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.305-20180521:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
i.e. everything till
Code:
apply_patch_check("EMMC:/dev/block/bootdevice/by-name/boot:47510824:9ca7a29f3b90af90492bfa0c07275390f72f397d:47502632:80fbccb727c484733397429a9df38a499dee67fe") || abort("E3005: \"EMMC:/dev/block/bootdevice/by-name/boot:47510824:9ca7a29f3b90af90492bfa0c07275390f72f397d:47502632:80fbccb727c484733397429a9df38a499dee67fe\" has unexpected contents.");
Save it and zip back the ota
NOTE: Skip step 4 if you have stock fastboot images
4. Extract stock rom zip and go to META-INF\com\google\android , open updater-script in text editor and remove these lines from it
Code:
(!less_than_int(1524926024, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Sat Apr 28 22:33:44 CST 2018) over newer build (" + getprop("ro.build.date") + ").");
containprop(getprop("ro.product.device")) || abort("E3004: This package is for \"ASUS_X00TD\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.252-20180428:user/release-keys");
show_progress(0.650000, 0);
i.e everything till
Code:
ui_print("Patching system image unconditionally...");
Once done, zip it back
5. Reboot to bootloader and flash system.img vendor.img boot.img and modified twrp.img if you have correct version of fastboot rom, otherwise, just flash the modified twrp.img and force reboot to recovery by pressing and holding volume down + power key
6. Once in recovery, flash the rom.zip you made and right after that flash the ota.zip, once done, make a backup of boot, modem, system image, vendor image
7. (OPTIONAL) if you had decrypted data partition before, flash normal twrp using current twrp or fastboot and flash decrypt.zip again
8. (OPTIONAL) if you want rooted system no twrp and easy ota updates for future, flash magisk and stock recovery using modified twrp and reboot. you'll be able to flash ota normally after this with root access.
Enjoy.
What to do on next ota?
1. Flash the modified twrp
2. Restore the backup you made in step 6
3. Edit the ota as explained in step 3
4. Flash the ota zip and make another backup of system image, vendor image, modem, and boot (also any other partition depending on the ota)
5. Do the optional steps as said in steps 7 and 8
Click to expand...
Click to collapse
After rooting phone, for ota update, If I flash stock recovery via flashify and uninstall magisk from magisk app then put rom in internal storage, will it detect software update & installe it?? Or if I flash updated zip by stock recovery will it work??

Kindly explain the steps for those guys who are on 305 Version already, have it rooted and have TWRP installed and
1) Want to have root and TWRP intact after update
2) And data also remains
How can they update to 309 ?
And thank you for posting the guide.

arnold991 said:
Kindly explain the steps for those guys who are on 305 Version already, have it rooted and have TWRP installed and
1) Want to have root and TWRP intact after update
2) And data also remains
How can they update to 309 ?
And thank you for posting the guide.
Click to expand...
Click to collapse
yes help

arnold991 said:
Kindly explain the steps for those guys who are on 305 Version already, have it rooted and have TWRP installed and
1) Want to have root and TWRP intact after update
2) And data also remains
How can they update to 309 ?
And thank you for posting the guide.
Click to expand...
Click to collapse
Kindly help brother.

Sudeep Duhoon said:
Modified OTA Links:
From 252 to 305
From 305 to 309
Click to expand...
Click to collapse
Thank you, thank you.. You are a life saver!!! Please continue to upload the modified OTAs in the future too.. Really appreciate this..

Sudeep Duhoon said:
Modified OTA Links:
From 252 to 305
From 305 to 309
Click to expand...
Click to collapse
I am on Redwolf recovery.
Unlocked bootloader and Rooted with magisk.
Can I flash this zip with Redwolf Recovery?
Do I have to follow full procedure?

Sudeep Duhoon said:
Modified OTA Links:
From 252 to 305
From 305 to 309
Click to expand...
Click to collapse
So this modified ota will work if just flash by TWRP or RWRP?? Don't need to flash system.img, vendor.img, boot.img???

Ariful Hasan Soikot said:
So this modified ota will work if just flash by TWRP or RWRP?? Don't need to flash system.img, vendor.img, boot.img???
Click to expand...
Click to collapse
No, it won't, I have tried that, you will get flashing error.
Full ROM is out. @Sudeep Duhoon
https://www.asus.com/in/Phone/ZenFone-Max-Pro-ZB601KL/HelpDesk_Download/
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZB601KL/UL-ASUS_X00T-WW-15.2016.1805.309-user.zip
The questions I asked earlier.
Kindly explain the steps for those guys who are on 305 Version already, have it rooted and have TWRP installed and
1) Want to have root and TWRP intact after update
2) And data also remains
How can they update to 309 ?

Flashing TWRP as Image - Possible?

TWRP 3.3 is out but only the IMG version is available in the TWRP site. Flashable ZIP file isn't available yet. I can fastboot boot into TWRP.img but since this is an A/B phone i guess i can't flash the image to any partition? Is there a way i can do that or do i have to wait until TWRP releases ZIP files for the update?
Thanks!

Helhound0 said:
TWRP 3.3 is out but only the IMG version is available in the TWRP site. Flashable ZIP file isn't available yet. I can fastboot boot into TWRP.img but since this is an A/B phone i guess i can't flash the image to any partition? Is there a way i can do that or do i have to wait until TWRP releases ZIP files for the update?
Thanks!
Click to expand...
Click to collapse
In order to flash the recovery as an image, you need to pack it inside a boot.img and then flash the boot partition.
The recovery itself is just the ramdisk from the boot.img. when you boot to recovery, the ramdisk gets unpacked and used as the root file system. When you boot to the os, the ramdisk is skipped and the system partition is mounted as the root partition.
There are some ROM kitchens that should be able to do this. I think there is a binary in the twrp installer that well let you do all this from your phone.
From the command line, you would use the unpackbootimage binary to dump your boot.img, gunzip and cpio to dump and repack the ramdisk, then mkbootimg to pack it all back up.
There might be an extra step to sign the boot.img, but you can take a look at the twrp installer to see if it does any extra magic at the end.
So yes it's possible, but certainly not a "flash it and forget it" kind of thing.
Lastly, isn't there an option to install twrp from inside twrp? I thought I read that in the change log. Maybe I should have lead with this?:good:
---------- Post added at 01:42 PM ---------- Previous post was at 01:36 PM ----------
Yup, it's in the XDA post.
Going forward, users will be presented with a new “install recovery ramdisk” option in recovery. This means that users can boot TWRP and then install it without downloading a separate ZIP file.
Click to expand...
Click to collapse
https://www.xda-developers.com/twrp-3-3-0-release/
I haven't flashed it yet, so I can't say if this is implemented in our version yet.

gee one said:
In order to flash the recovery as an image, you need to pack it inside a boot.img and then flash the boot partition.
The recovery itself is just the ramdisk from the boot.img. when you boot to recovery, the ramdisk gets unpacked and used as the root file system. When you boot to the os, the ramdisk is skipped and the system partition is mounted as the root partition.
There are some ROM kitchens that should be able to do this. I think there is a binary in the twrp installer that well let you do all this from your phone.
From the command line, you would use the unpackbootimage binary to dump your boot.img, gunzip and cpio to dump and repack the ramdisk, then mkbootimg to pack it all back up.
There might be an extra step to sign the boot.img, but you can take a look at the twrp installer to see if it does any extra magic at the end.
So yes it's possible, but certainly not a "flash it and forget it" kind of thing.
Lastly, isn't there an option to install twrp from inside twrp? I thought I read that in the change log. Maybe I should have lead with this?:good:
---------- Post added at 01:42 PM ---------- Previous post was at 01:36 PM ----------
Yup, it's in the XDA post.
https://www.xda-developers.com/twrp-3-3-0-release/
I haven't flashed it yet, so I can't say if this is implemented in our version yet.
Click to expand...
Click to collapse
Yes i got to know about the update with this Article, But I don't get a “install recovery ramdisk” option anywhere in my recovery when i boot into 3.3. Besides the article says this:
the team will offer installer ZIPs this time around to give people a chance to update from older versions, but future TWRP releases won’t have separate installer scripts.
Click to expand...
Click to collapse

Helhound0 said:
Yes i got to know about the update with this Article, But I don't get a “install recovery ramdisk” option anywhere in my recovery when i boot into 3.3. Besides the article says this:
Click to expand...
Click to collapse
I just spoke with the device TWRP device maintainer for the OnePlus 6T and he instructed me to make this change in the device tree.
Add
TW_INCLUDE_REPACKTOOLS := true
Into
boardconfig.mk
I'll try this out when i get back home later and post an update.

I've made a zip for it and attached it. What I did was download the zip for another device (fajita I believe), download the image for this device, extract the ramdisk from the image using magiskboot, replace the ramdisk inside the zip with the one from the image, and sign it using the default testkey. Steps to install the zip:
1. Update LineageOS so that I have a boot image with no older TWRP (may not be necessary, but better safe than sorry). I DID NOT REBOOT YET! (Although I don't think rebooting would've caused problems, I just didn't want to deal with rebooting twice)
2. Install the modded TWRP zip from Magisk Manager (not from TWRP itself). DO NOT REBOOT, THE ZIP REMOVES MAGISK, WE NEED TO REINSTALL IT FIRST.
3. Go to the main page of Magisk Manager, and install Magisk to the inactive slot
4. Reboot, everything should be fine
Note: this uses the TWRP image from the website, so it does not have the Install to Ramdisk or whatever option. It does however have the rest of the TWRP 3.3 features like being able to decrypt data for Android Pie.
Obviously, full credit goes to the TWRP team, all I did was replace the ramdisk in the zip with the one from the image.

Turns out an official build was released not long after I posted that, oops. There's a zip on the website now.

BeeWall said:
Turns out an official build was released not long after I posted that, oops. There's a zip on the website now.
Click to expand...
Click to collapse
Yeah i came to post about that in the thread. Thanks for your work tho
To anyone interested, they've uploaded a flashable ZIP file for Payton in their website.
You can download it here : https://dl.twrp.me/payton/