Related
Error message during failed install of CM zip: assert failed: get prop ("ro.product.device") == "ovation" || get prop ("ro.build.product") = ="ovation"
Solved: See below.
When I first got my HD+, I did an SD "install" of CM 11. Then I installed CM 11 to the emmc, via CWM, per all the instructions on the xda website.
Once CM 11 was installed, I changed to TWRP 2.6.3.0. (I like being able to name the backups.)
Then I did a wipe and dropped down to CM 10.2.1. (More stable.) I did the install from TWRP.
Then I installed the fuzz kernel from TWRP.
Last, I updated to TWRP 2.6.3.0a when I couldn't get Succulent's CM 11 to install.
Okay, so tonight I wanted to do a clean install of CM 10.2.1, without gapps this time.
So I booted to recovery, did a wipe, and tried installing CM 10.2.1.(The build came direct from Cyanogen mod's website for the Ovation.)
I get an error similar to what I got when I tried to install Succulent's CM 11. Here's the error message:
assert failed: get prop ("ro.product.device") == "ovation" || get prop ("ro.build.product") = ="ovation"
I dropped back to CWM and tried installing the ROM from three different versions: CWM 6.0.4.5, 6.0.4.5b, and CWM 6.0.4.6.
I tried installing CM 10.2.1 from the internal and the external SD card.
No joy. Fortunately, a Nandroid backup beforehand and I've restored to where I was.
Any ideas what's wrong? It shouldn't be this hard. It doesn't seem that a ROM install should be Recovery Dependent . But maybe it is?
==========
Solved. leapinlar, in the thread where I originally posted this question, said to use an older version of CWM to install. Apparently some incompatibility between versions of CWM (and TWRP) and the ROM zip.
Another solution was alluded to by King200 in another forum, but it sounded arcane and hard to do. It wasn't.
Here are Windows instructions:
++++++++++
Note: This method removes the "sanity check" built into the recovery image which checks to make sure the ROM you're installing is compatible with your tablet. Obviously, flashing the wrong ROM can/will brick your tablet.
So be warned.
Since I only have one tablet that I flash CM 10.2.1 on, no problem for me. If you have more than one tablet, perhaps you should delete your hacked zip after you install, to be safe.
Okay?
But for educational purposes, here's what I did to work around the problem.
++++++++++
You do this with 7-Zip. (So install 7-Zip if you don't have it already.)
Right click on the ROM that you're trying to install.
A 7-Zip context menu opens.
Select "Open Archive."
Drill your way down to
/META-INF/com/google/android/updater-script
Right click on the updater-script and select "Edit."
Open updater-script with Notepad.
Delete the first line of code, all the way up to the first semicolon. And delete the first semi-colon as well.
Save the edited file in Notepad. You'll get a 7-zip message asking if you want to incorporate your changes back into the archive. "Yes."
Now the ROM will install with later versions of CWM or TWRP.
Note: I had to do with this with the "fuzz" kernel too.
P.S. I don't know how to read code, so I don't understand exactly what the problem here is. I peeked at the scripts. I have an "ovation" tablet. Both the ROM and the Recovery image mention "ovation" in their updater scripts. Seems like they ought to talk to each other.
Please don't do this procedure. It is dangerous. It could brick your device. And the issue is not whether you have more than one tablet, it is if you accidentally download a hummingbird (HD) zip when you have an ovation (HD+) and try to flash it to an HD+. If you remove that assert statement the HD zip will merrily install to an HD+. And you will have a real mess.
A real case happened where a Nook Color user tried to flash a Nook Tablet ROM to his Color. The assert statement which was designed to prevent that did its job and prevented it. However, another user recommended he remove the assert statement, which he did, and thus flashed the Tablet ROM to his Color. His Color ended up bricked.
NEVER REMOVE AN ASSERT STATEMENT!
There are two more safe procedures.
One, use an older version of CWM to flash the older zips.
Two, do as the procedure says by opening the archive, but don't edit the updater-script file to remove the assert line. Look in a newer zip like CM11 and extract the file 'update-binary' and copy it to the old zip replacing the old update-binary file there. Then the old zip is flashable with the newer CWM/TWRP recoveries.
Sent from my BN NookHD+ using XDA Premium HD app
For those who have myphone uno plss help me it won't update
If someone kind enough to share the link of
ota zip I can just flash It in stock recovery
gabisonfire98 said:
For those who have myphone uno plss help me it won't update
If someone kind enough to share the link of
ota zip I can just flash It in stock recovery
Click to expand...
Click to collapse
Ok lmy47o patch zip is just 23 mb
guys,
i also have a myphone uno rooted but no custom recovery as of now. i had no problem updating the previous system updates. the recent one came in just fine. then now, the phone (every time it connects to wi-fi) would offer a new sys update. but when this is applied, the procedure results with an ERROR. i wonder if you guys are getting similar results.
bodega1968 said:
guys,
i also have a myphone uno rooted but no custom recovery as of now. i had no problem updating the previous system updates. the recent one came in just fine. then now, the phone (every time it connects to wi-fi) would offer a new sys update. but when this is applied, the procedure results with an ERROR. i wonder if you guys are getting similar results.
Click to expand...
Click to collapse
i have the same problem. my current system is version is 5.1.1. i'm using stock recovery. my phone is rooted using superSU.
guys,
i've recently just tried doing a FACTORY RESET (myPhone UNO), Android 5.1.1, and to no avail: still an error when updated a 18MB update. either the update file has an error or my rooted settings are preventing a clean OTA update.
bodega1968
dude,
I finally resolved the update issue. will give you the instructions soon. got to go... but will get back to you once I have composed the procedures... I believe the cause is having rooted and changed some data in the system cache.
bod98
SOLVING [one solution] OTA PROBLEMS in myPhone UNO (sprout)
Background.
Phone model: myPhone UNO (sprout hardware)
Android 5.1.1
*Problem: OTA update failure.
*Log message:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
VErifying current system...
"/system/bin/app_process32" has unexpected contents.
E:Eror in 0/cache/recovery/block.map
(Status 7)
*Possible Cause: Occurred after rooting with anil293 (Android Root Kit here). I’m not saying that this program is bad, but only to caution anyone who may want to root and possibly lose OTA updates.
Solution. (*This worked for me since I had done a previous NANDROID backup (NB) of the phone prior to any system changes (i.e. rooting, custom recovery, etc.). The following steps were written to help those who may not be too familiar with some basic non-GUI (graphic user interface) commands in order to restore one’s device to it’s original and working condition.
Step 1: I chanced upon DEVAM30’s wonderful contribution on how to run RECOVERY without installing it ‘permanently’ into the phone. Check out his page here. This allowed me to make my NB. Download from this page the PHILZ8.img (*This will be the 'virtual' recovery file which you will boot into in order to make your NB)
Step 2: Assuming that you have a previous NB, this (huge file) should be located in the clockworkmod folder in your SDCard. You will refer to this once you have successfully booted in the PHILZ8 recovery.
Step 3: Set your phone to allow USB Debugging. (*This can be done in the Developer’s Section) NOTE: Prior to all this, make sure you BACKUP your critical personal files (i.e. contacts, SMS, data, etc. GOOGLE this to find out how to backup your personal data. The next steps will ERASE everything in your phone. I will not be responsible for any data lose or the bricking of your phone.
Step 4: Boot your device in FASTBOOT mode (FM). (*Power OFF the device, then after 5-10 seconds, press POWER ON + VOL UP. When screen turns on, release VOL UP followed by POWER ON). MENU comes up. Use VOL UP to SCROLL among the choices, and when you have selected FM, press VOL DOWN and the phone should pretty much be in FMode.
Step 5: While your phone is in FM. In your PC you should have ADB/FASTBOOT functions already set up. Check the link here on how to install and work in fastboot mode. When you have properly installed everything in this STEP, you must copy the PHILZ8.img into the adb/fastboot folder. You may rename it into something simpler like recovery.img
Step 6: Connect your phone (*already in FM) to the PC.
Step 7: In your PC, in adb/fastboot folder (*check if your device is connected properly – adb devices or fastboot devices). If your device is detected some number should appear in the screen. Then you type: fastboot boot philz8.img or the name you gave to the .img file.
Step 8: Wait for the PHILZ8 recovery to kick in. Once it boots up you’re now ready to do a RESTORE of your NB. You will see a TOUCH menu in your screen. You will carry out two important steps. (a) wipe the cache and (b) restore the NB image from the SDCard.
Step 9: Choose the wipe menu. In my case, I chose to WIPE (*Choose wipe cache options) cache and the dalvik cache. The former one will take a while, and the latter only takes a few seconds. Once done, +++GO BACK++ to the main menu and then TAP on RESTORE. It will ask you where you will restore the image from. Choose SD card. If it doesn’t do this automatically, you may have to navigate to the clockworkmod folder where your NB image is located. Choose that image and you’re good to go!
Step 10: Once the entire procedure is over (*be patient, it may take some time to finish the entire restoring of the image), you will now opt to REBOOT the SYSTEM. Now, this is critical (in my opinion) because the virtual recovery (PHILZ8) will ask if you wish to install root. Choose NO! Otherwise, it may make some changes in the system settings that will conflict with the OTA updates we want to work.
The device will reboot and you will pretty much be back to its original settings (more than a simple factory reset). And your phone will update a few times and no error will come out.
For those of your who don’t have or have not been able to make a CLEAN NB, I uploaded this RAW image phone (it does not contain any personal data or programs) . You may download it here.
bod68
*updated 9IX15
LINK to my NANDROID BACKUP
gabisonfire98 said:
Ok lmy47o patch zip is just 23 mb
Click to expand...
Click to collapse
gabisonfire98,
dude, if you're patient enough to follow my 'SOLUTION' to regaining OTA updates, check out the procedure i outlined below, september 4, i believe it was.
the link to my NANDROID BACKUP which could be RESTORED to your device (*Using the wonderful procedure outlined by DEVAM03)!
Download the image here
Just email me if you find some of the instructions confusing, just email me.
bod68
I recently started playing pokemon go and I am getting really frustrated while playing because it lags soo much and my phone is generally quite slow now. I have been told rooting and installing a good ROM can help with this and I have never attempted this, could someone please explain what rooting and ROMs are and their benefits and a how to guide for this phone and also the best ROM?
I know there are loads of threads on this but if someone could link me best threads I would be eternally gratefull!!
First of all, which variant of LG L90 is your phone (D4xx)? And could you go to Menu > General > About Phone > Software Information and tell me your "version" (v10x or v20x)?
Root is the ability for the user to take total control of his phone, from doing as little as automate 3G activation when an app is open to instaling custom ROMs, which are custom firmwares that you can install in your device, just like the stock one you're currently in, but with some modifications made by its creators. As for advantages, with root you have more freedom over your device, and with Custom ROMs you have some tweaks, which change depending on the ROM you choose to install, going from just porting newer firmwares to older devices to being an entire new OS (Operational System, in case you don't know).
Hyoretsu said:
First of all, which variant of LG L90 is your phone (D4xx)? And could you go to Menu > General > About Phone > Software Information and tell me your "version" (v10x or v20x)?
Root is the ability for the user to take total control of his phone, from doing as little as automate 3G activation when an app is open to instaling custom ROMs, which are custom firmwares that you can install in your device, just like the stock one you're currently in, but with some modifications made by its creators. As for advantages, with root you have more freedom over your device, and with Custom ROMs you have some tweaks, which change depending on the ROM you choose to install, going from just porting newer firmwares to older devices to being an entire new OS (Operational System, in case you don't know).
Click to expand...
Click to collapse
Thank you soo much for your reply and sorry about my late reply. My variant is LG-D405n and software version is V20c-234-30. I think I understand what Root and ROM is thx.
So could you link me to the best method to root and install ROM on my phone?
And what is the best ROM for my device to free up the RAM and CPU used on my device to increase my phone speed?
First of all, install these required apps:
http://king.myapp.com/myapp/kdown/img/NewKingrootV4.9.6_C151_B309_en_release_2016_08_18_105203.apk (For rooting)
https://play.google.com/store/apps/details?id=com.cgollner.flashify (For flashing the Custom Recovery)
https://play.google.com/store/apps/details?id=jackpal.androidterm (For terminal emulation)
Custom Recovery:
TWRP: http://forum.xda-developers.com/devdb/project/dl/?id=18679&task=get
Personally recommended Custom ROM, CyanogenMod (Ports Android updates to older phones plus some tweaks) and Gapps (Google Apps, it's needed to have things like calculator, play store, etc):
CM13: https://download.cyanogenmod.org/get/jenkins/175208/cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J8-w7.zip
Gapps: http://opengapps.org/ (Go to this link, select ARM in platform, 6.0 in android and Nano in variant, then just click the download image button)
Put the TWRP img, the CM13 rom img and gapps on microSD or internal storage. Open Kingroot and click on the green button after the 3 introduction images. After a few minutes, your device will be rooted. Grab this file: http://forum.xda-developers.com/lg-...0w7xxshoxx-t2826150/post54358527#post54358527 (D405n_v20a_patched_aboot, don't worry, it's okay if you flash a different software version aboot as long as it's the same device as yours. The only "problem" you can have is to have your software version changed to v20c, which if I remember correctly, can be fixed using Bootstacks), transfer it to your phone and open Terminal Emulator. Then input the following commands:
su
dd if=(aboot.bin storage directory) of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Then, go to flashify and flash your custom recovery image (TWRP or CWM) in the flash recovery img option. After this, reboot into recovery by pressing Volume Down + Power and when you see the LG Logo, let go of the Power button and press it again. Then select yes two times with the volume keys for selection and power button to actually select the options (Don't worry, your device won't be factory resetted if you successfully installed custom recovery). Then, if you want, make a backup of your entire phone (recommended, just in case something goes wrong or if you just want your apps back when the process is done) in the Backup section and then do a factory reset through the Wipe option (Don't select anything, just swipe the bar). Select the Install option and select your ROM zip. After this, do the same process as the ROM installation but this time with Gapps zip. There you go, now you have CM13 installed. If you want root again, you don't have to install Kingroot again this time, as CM13 has built-in root, just enable Developer options and activate root and you're ready to go. Also, if you want the apps you had before the installation, just restore your backup (ONLY THE DATA PARTITION, otherwise CM13 will be uninstalled and replaced with stock ROM). If something goes wrong and you accidentally brick your device, just reply and I'll help you fix it. (If helped, click the Thanks! button)
Hyoretsu said:
Grab this file: http://forum.xda-developers.com/lg-...0w7xxshoxx-t2826150/post54358527#post54358527 (D405n_v20a_patched_aboot, don't worry, it's okay if you flash a different software version aboot as long as it's the same device as yours. The only "problem" you can have is to have your software version changed to v20c, which if I remember correctly, can be fixed using Bootstacks), transfer it to your phone and open Terminal Emulator. Then input the following commands:
su
dd if=(aboot.bin storage directory) of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
Hi, thank you so much, I finally rooted my device but I am having problems with the script part of the terminal emulator.
I wrote upto msm_sd and then this happen automatically:
View attachment 3865360
View attachment 3865361
View attachment 3865362
View attachment 3865363
I don't know what to do here..
EDIT: Also am I meant to have the SuperSU/SuperUser app installed once rooted? Then get a popup in the terminal emulator for permission for its root access?
Firebird3334 said:
Hi, thank you so much, I finally rooted my device but I am having problems with the script part of the terminal emulator.
I wrote upto msm_sd and then this happen automatically:
View attachment 3865360
View attachment 3865361
View attachment 3865362
View attachment 3865363
I don't know what to do here..
EDIT: Also am I meant to have the SuperSU/SuperUser app installed once rooted? Then get a popup in the terminal emulator for permission for its root access?
Click to expand...
Click to collapse
You have to change "(aboot.bin storage directory) with the directory in which aboot.bin is stored. And no, you don't need SuperSU, when you use the su command, a KingRoot window will open, just say yes.
EDIT: Wahay! It works! Thank you soo much for your help!
EDIT 2: I can't seem to find the option to edit my recent button in settings. What can I do?
Firebird3334 said:
EDIT: Wahay! It works! Thank you soo much for your help!
EDIT 2: I can't seem to find the option to edit my recent button in settings. What can I do?
Click to expand...
Click to collapse
If it's the menu button, I don't know of any way to change them, as Android updates change them. For example, my phone in KitKat used the home button for recent apps, in Lollipop it used the menu button for recent apps, and when I installed CM13, it used the home button again.
EDIT: Browsing LG L90 xda, I found this: http://forum.xda-developers.com/lg-l90/themes-apps/mod-button-remaps-l90-t3145146
Hyoretsu said:
If it's the menu button, I don't know of any way to change them, as Android updates change them. For example, my phone in KitKat used the home button for recent apps, in Lollipop it used the menu button for recent apps, and when I installed CM13, it used the home button again.
EDIT: Browsing LG L90 xda, I found this: http://forum.xda-developers.com/lg-l90/themes-apps/mod-button-remaps-l90-t3145146
Click to expand...
Click to collapse
You have helped me out so much already! Thank you so much!
But just one more thing though, could you explain how to install magisk and xposed in layman's term so I can use Android Pay?
I don't know what magisk is nor layman's term, but to install Xposed just go to this thread: http://forum.xda-developers.com/showthread.php?t=3034811, download both Xposed installer apk and xposed zip. Install xposed apk and flash xposed zip
Hello,
Help me please I'm getting Error 7 and after twrp reflash Error executing updater binary in zip
I did all the previus steps phone LG L90 d405n is rooted and bootloader is unlocked and rom downgraded to KK v10b
Now I want to flash CM or RR rom but I simply can't!
First I was getting error 7 when flashing I found out that I need TWRP 2.8.7 build 2 to flash so I found it and flashed. Now I'm getting ''error executing updater binary in zip twrp'' and I can't flash any rom.?*
I tried deleting first assert lines in updater-script from this?*thread?*but It didn't helped in any way...
Any ideas? Why the hell it is so ****ing complicated to flash custom on this ****ty device? Can't it work like Nexus4 or any other normal device??*
Thanks in advance for any tips&trics
PS. I can't open new thread dunno why...
amonlb said:
Hello,
Help me please I'm getting Error 7 and after twrp reflash Error executing updater binary in zip
I did all the previus steps phone LG L90 d405n is rooted and bootloader is unlocked and rom downgraded to KK v10b
Now I want to flash CM or RR rom but I simply can't!
First I was getting error 7 when flashing I found out that I need TWRP 2.8.7 build 2 to flash so I found it and flashed. Now I'm getting ''error executing updater binary in zip twrp'' and I can't flash any rom.?*
I tried deleting first assert lines in updater-script from this?*thread?*but It didn't helped in any way...
Any ideas? Why the hell it is so ****ing complicated to flash custom on this ****ty device? Can't it work like Nexus4 or any other normal device??*
Thanks in advance for any tips&trics
PS. I can't open new thread dunno why...
Click to expand...
Click to collapse
First of all, you don't need to use that TWRP build, you can use the latest one. To fix the only errors that should appear (Updater error 7 and 6), delete the first lines of updater-script until you reach the ui_print part (the first line of your file should be "ui_print("Target: 1471683591");"). Also, delete any double spaces that exist (there should be two, one before "abort" at line 27 and the other before "abort" at line 30). If it still gives the same error, try wiping Cache, data, system and dalvik-cache partitions, try to install the ROM, it'll give the error. Now, reboot your phone and try to install without wiping anything. (To properly see the line indications, open the file using Notepad++)
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.
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 ?