How to update OEM partitions? - ASUS ZenFone 6 (2019) Questions & Answers

How do you update oem/modem/other manufacturer specific partitions if you are on Lineage or another custom rom. Obviously OTA won't work and flashing the recent stock rom is not an option since you would (probably) lose all of your data.
Can you somehow extract those partitions from the stock rom and flash them separately?

mr_keule said:
How do you update oem/modem/other manufacturer specific partitions if you are on Lineage or another custom rom. Obviously OTA won't work and flashing the recent stock rom is not an option since you would (probably) lose all of your data.
Can you somehow extract those partitions from the stock rom and flash them separately?
Click to expand...
Click to collapse
I would leave those alone, unless you have many years of firmware hacking... Everytime I messed with them, they bricked my phone... Not worth it for what you get...

Related

Untouched Jelly Bean Stock ROM

If you are looking for the Odin-Flashable Image go here. These update files are based on that image.
These are recovery-flashable zips for the untouched Jelly Bean image that Nardholio provided.
They are as Samsung provided them with all the crap. I stripped the recovery though since i don't think anybody would want to loose theirs.
If you flash using TWRP (dunno about CWM), it detects that your current system is un-rooted and asks if you want to install SuperSU. If you want root, just let him do it.
I've split the update into three files:
JB stock modem (md5: 932407773cb6e0e5bd133da49ba8a442) as provided by Nardholio. This is just a mirror. Didn't touch that.
JB stock bootloader (md5: 2a980ce6d3f109f56e86b663f03fd761) that came with the update. Seems like it's purely optional. You only need to flash this once (if you want it) as it is usually not overwritten by any updates.
and the actual JB stock image (md5: b70f44d4619391c8f0f4debaa6239fc3)
cache/data wipe is required for the image.
if you just want the bootloader/modem there's no need to wipe.
The Odin image also came with an empty persist partition. None of these updates touches persist as you might want to flash back and have a ROM that relies on those files.
I've tested all the images and they work fine for me. But, certainly, they come without warranty. Flashing things, especially bootloader and modem, always come with the risk of bricking your phone. Be aware of it and don't blame me.
Hi
On flashing the new bootloader i am not getting any network...do i need to unlock again?
edit: Got network after trying several different SIMs. weird eh?
kilr00y said:
If you are looking for the Odin-Flashable Image go here. These update files are based on that image.
These are recovery-flashable zips for the untouched Jelly Bean image that Nardholio provided.
They are as Samsung provided them with all the crap. I stripped the recovery though since i don't think anybody would want to loose theirs.
If you flash using TWRP (dunno about CWM), it detects that your current system is un-rooted and asks if you want to install SuperSU. If you want root, just let him do it.
I've split the update into three files:
JB stock modem (md5: 932407773cb6e0e5bd133da49ba8a442) as provided by Nardholio. This is just a mirror. Didn't touch that.
JB stock bootloader (md5: 2a980ce6d3f109f56e86b663f03fd761) that came with the update. Seems like it's purely optional. You only need to flash this once (if you want it) as it is usually not overwritten by any updates.
and the actual JB stock image (md5: b70f44d4619391c8f0f4debaa6239fc3)
cache/data wipe is required for the image.
if you just want the bootloader/modem there's no need to wipe.
The Odin image also came with an empty persist partition. None of these updates touches persist as you might want to flash back and have a ROM that relies on those files.
I've tested all the images and they work fine for me. But, certainly, they come without warranty. Flashing things, especially bootloader and modem, always come with the risk of bricking your phone. Be aware of it and don't blame me.
Click to expand...
Click to collapse
Do you know where to find official Jelly Bean but not the latest one?
I think it was 4.0.4.
I need to test something with bluetooth related (as I am writing in other my post it might be worst in 4.1.2).
Regards
flashed modem and image. couldn't get Wi-Fi to work until i flashed the bootloader though.
froze a couple of times within the first 30min of playing with it, but whatever was causing it seems to have "healed" because it hasn't happened at all today.
much appreciated
Any idea where to get the stock recovery?
Just for completeness.... Both in update.zip form (unsigned):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/JB-stock-recovery.zip
-- Recovery
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/JB-stock-system.zip
-- System & Kernel
(This is not the same form as kilr00y posted in the OP... His is a version that's been converted. This is the full filesystem, extracted to the block device. This shows up as official on the downloader. It is not pre-rooted. ... This also differs from an ODIN flashable version of this. Heimdall might be able to flash the resultant image, but this is meant to be flashed through recovery)

[Q] OTA update ?

I just bought my nexus 5 and it's rooted with a custom ROM. Will I still get the update? I have a backup of the stock ROM but not the stock recovery. Do I need to restore my backup and wait for the update? Thanks.
If you want the ota, go back to stock. Or wait a few days and flash lollipop from your custom recovery I once a Dev packages it up. Or fastboot flash it as soon as available.
Depends on how patient you can be and how technical you are prepared to be.
I will be editing far the system image and fast boot flashing myself.
I think you have to be on stock ROM with the stock recovery to get the 5.0 ota.
IMO you can wait for the factory images from Google and flash them directly rather then flash stock ROM and recovery now and wait for the ota, because OTA will hit later then the factory images.
evertking said:
I just bought my nexus 5 and it's rooted with a custom ROM. Will I still get the update? I have a backup of the stock ROM but not the stock recovery. Do I need to restore my backup and wait for the update? Thanks.
Click to expand...
Click to collapse
U could have asked that in the lollipop thread...
No u will need stock recovery to flash ota.....
Also i would strictly advice u to either flash pure kitkat image...or lollipop image .... That would prevent most of the bugs u encounter wid userdata...
rootSU said:
If you're going to live in the rooted world, you should learn to do things properly. OTA is the worst way of managing a rooted phone, which is why I said OTA is super-noob. If someone is reliant on OTA updates, they probably should not be rooted in the first place.
Click to expand...
Click to collapse
See above
There are also dedicated OTA threads as well as dedicated Lollipop threads. Nor does this belong in General.
This thread has all of the OTA info you could imagine.
http://forum.xda-developers.com/showthread.php?t=2523217
As mentioned above. We have a dedicated OTA thread.
Closed.

[Recovery][4.4.4] STOCK RECOVERY for XT1033

As we All know we are going to get Android 5.0 Lollipop OTA in coming days and for OTA stock recovery is necessary.
Downloading whole firmware just for stock recovery is not worthy that's why I'm sharing stock recovery of Asian variant(XT1033 including India).
LINK:-
Stock recovery(Here)
.
Waiting so anxiously for Lollipop
BUT, flashing the ENTIRE firmware to OTA your device is a MUST.
OTA will fail if your device was rooted then unrooted because system partition was modified by root.. So, for the update to succesfully work, you have to flash entire firmware (including stock recovery), like it or not, to have an untouched system partition.
Flashing only stock recovery again is not enough, it will make no difference, OTA will fail.
So, this thread is kinda useless if you think about it...
MarckozZ said:
BUT, flashing the ENTIRE firmware to OTA your device is a MUST.
OTA will fail if your device was rooted then unrooted because system partition was modified by root.. So, for the update to succesfully work, you have to flash entire firmware (including stock recovery), like it or not, to have an untouched system partition.
Flashing only stock recovery again is not enough, it will make no difference, OTA will fail.
So, this thread is kinda useless if you think about it...
Click to expand...
Click to collapse
Now that you said... Agreed
Sent from my XT1033 using XDA Free mobile app
Flashing Stock recovery alone wont work... I tried flashing the stock recovery alone for upgrading to 4.4.4.. but it didn't work..... We need to flash the whole firmware again for successful upgrade..
But it's good if somebody else want to find official recovery
Sent from my XT1033 using XDA Free mobile app

[Q] Can I update stock N5 BUT with Franco Kernel?

I've got a Nexus 5 on Lollipop that's completely stock except for running franco kernel. Haven't touched it for awhile. If I check and there are any OTA updates available, will they install successfully?
No, you must have stock kernel, stock recovery, and unroot
micens said:
No, you must have stock kernel, stock recovery, and unroot
Click to expand...
Click to collapse
Thanks.
Is there a way to manually flash the OTA, or to install it one way or another, without having to revert to stock kernel and unroot and then re-root and re-install franco again?
Edit flash-all file and remove "-w".
Save the file and flash it from fastboot
.psd said:
Is there a way to manually flash the OTA, or to install it one way or another, without having to revert to stock kernel and unroot and then re-root and re-install franco again?
Click to expand...
Click to collapse
As of Lollipop, the OTA method has changed and instead compares the checksum/hash of the entire /system partition, as well as the boot and recovery partitions. The "old" pre-Lollipop method was to check the specific files it cares about rather than sum of the entire partition.
The best way for you to update is download the factory image, extract it then flash the boot and system images using fastboot while your device is booted into the bootloader. You may also want to flash the new bootloader and/or radio. Don't flash the userdata image as it will wipe your /data partition (which the internal storage also resides in), unless that is something you want.
After that, boot into your custom recovery and simply flash the latest SuperSU and if you want to, a Lollipop version of the kernel you want. Files required by SuperSU/root access reside in the /system partition, which prevents an OTA update, and is overwritten when flashing a factory system image. A KitKat kernel won't boot on Lollipop, and a custom kernel also prevents OTA.
OTAs are really only for those who have absolutely no software modifications (and are not informed enough to be able to flash manually) and is honestly the worst way of updating.

Is there a way to revert custom ROM to stock and keep the phone rooted?

Also, how can I tell what were the previous versions of Android that my phone had (STOCK)?
For example: there were several 5.1.1 versions or 5.0. versions - how do I know which one do I need?
Thanks.
The easiest way to have a routed rom would be to flash a stock rom from Google, flash twrp, and flash supersu from twrp.
audit13 said:
The easiest way to have a routed rom would be to flash a stock rom from Google, flash twrp, and flash supersu from twrp.
Click to expand...
Click to collapse
Sorry if I didn't explain myself - my phone is rooted and I have a custom ROM. What I want to do is to go back to stock ROM but keep it rooted.
Thanks.
Flash a stock rom, then just root the stock rom. There is no other way unless you flash a stock pre-rooted rom.
audit13 said:
Flash a stock rom, then just root the stock rom. There is no other way unless you flash a stock pre-rooted rom.
Click to expand...
Click to collapse
So you can't keep it rooted while flashing stock?
And how do you know which versions are for your phone (if I don't want to go back to the latest Marshmallow for example)?
You can only keep root when flashing stock if you find a prerooted stock image.
Google search for nexus factory images.
audit13 said:
You can only keep root when flashing stock if you find a prerooted stock image.
Google search for nexus factory images.
Click to expand...
Click to collapse
Yes, I know that I need to Google for factory image, but there are several images with the same release. For example, there are three 5.1.1. (LMY48B, LMY48I and LMY48M). Same with 6.0.0. and 4 X 6.0.1 version. How do you know which one is for my device?
Thanks.
Any stock image for hammerhead will work on a hammerhead device. The reason it will delete root is you will have to flash system, and unless the system image you flash is prerooted, no more root.
wangdaning said:
Any stock image for hammerhead will work on a hammerhead device. The reason it will delete root is you will have to flash system, and unless the system image you flash is prerooted, no more root.
Click to expand...
Click to collapse
Thanks!
Just trying to understand that difference between the different versions, or are these simply system updates, from XXX29K to XXX29S for example?
Changes in the android version 5.0->5.1->6.0 are fairly large system updates. Within 5.1.1 they are security patches.
If you have a rooted phone and talk about flashing, you should know this. Else you are a menace to your phone...
Root is a system modification - if you delete or reinstall the System partition, you'll lose root. But re-root is easy.
I recommend to read tutorials and get some knowledge before trying to root, flash or before asking those questions, where Senior xda-members just shake their heads.
The simple way to do what you seem to want is to back up all your important stuff (photos, etc.), install MMB29V (the latest March 1st 6.0.1 security version), install TWRP 3.0.0.0, and from TWRP flash SuperSU v2.70. It will take slightly longer than it's taken me to type this, but not much...
After that, when a new monthly security version comes out, flash system.img, boot.img & radio.img, and repeat the TWRP & SuperSU steps. No data loss.

Categories

Resources