Related
*************************************************************
INCORRECT USE OF THESE FILES WILL BRICK YOUR DEVICE
PLEASE ENSURE YOU KNOW WHAT YOU ARE DOING AND
I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG
*************************************************************
Here you can find stock firmware for both thor and apollo devices which are safestrap flashable.
Please note the following:
- These updates do NOT flash a new kernel or recovery - only a new /system image
- Before flashing ensure you know which stock base/kernel/safestrap you have installed and choose the appropriate version for that stock base/kernel.
- Do NOT use these images to downgrade or upgrade your base firmware.
I will be uploading them as and when I have time.
Thor Images:
- 13.3.1.0 <- Flashable on Safestrap 3.7.2
- 13.3.2.6 <- Flashable on Safestrap 3.7.5
*** THESE ONES DO NOT HAVE ROOT OR BLOCK UPDATES ***
- 13.4.5.2 <- Flashable on Safestrap v4.0.1
Apollo Images:
- 14.3.1.0 <- Flashable on Safestrap 3.7.2
- 14.3.2.6 <- Flashable on Safestrap 3.7.5
*** THESE ONES DO NOT HAVE ROOT OR BLOCK UPDATES ***
- 14.3.2.8 <- Flashable on Safestrap v3.7.5
- 14.4.5.2 <- Flashable on Safestrap v4.0.1
If you want to re-enable over the air updates then do the following:
- Skip this if you are using the 4.5.2 files - As stated above this does not apply so be careful.
- rename /system/etc/security/otacert.old to otacert.zip
- rename /system/app/com.amazon.dcp.old to com.amazon.dcp.apk
ggow said:
Hi All,
Here you can find stock firmware for both thor and apollo devices which are safestrap flashable.
Please note the following:
- These updates do NOT flash a new kernel or recovery - only a new /system image
- Before flashing ensure you know which stock base/kernel/safestrap you have installed and choose the appropriate version for that stock base/kernel.
I will be uploading them as and when I have time.
Thor Images:
- 13.3.1.0
Apollo Images:
- 14.3.1.0
If you want to re-enable over the air updates then do the following:
- rename /system/etc/security/otacert.old to otacert.zip
- rename /system/app/com.amazon.dcp.old to com.amazon.dcp.apk
Click to expand...
Click to collapse
Excellent! I am able to revert back to this stock firmware after nearly bricking my device. Thank you!!
Since I"m heavily tied into the Amazon ecosystem and have other Kindle devices, installing HDX Nexus 2.01 didn't work for me.
However, thanks to @ggow, using the same upgrade guide, Iwas able to get my 3.1.0 to 3.2.6, allowing my fire hdx devices to finally be able to do screen sharing with my fire TVs! I did have to restore /data, enable xposed + hdxposed, re-install kindlefree + Google play store APKs & stucks wallpaper fix to be back at 100%...
Will you make a pre rooted 4.5.1 image for the HDX 7.0 Thor?
Can I flash this over a Stock 4.5.1 device?
D0ubl3_X said:
Will you make a pre rooted 4.5.1 image for the HDX 7.0 Thor?
Can I flash this over a Stock 4.5.1 device?
Click to expand...
Click to collapse
As of right now, it's impossible to root 4.5.1.
No, you can't flash them over a newer version just like that. If you want to downgrade, check this thread.
Hey @ggow, would it be possible for you to release a rooted 14.3.2.6?
_Alex_ said:
Hey @ggow, would it be possible for you to release a rooted 14.3.2.6?
Click to expand...
Click to collapse
Hi _Alex_, yes I'll sort one out for you.
ggow
I goofed - flashed the apollo zip over my already properly up(down)graded stock. Now of course I get a blank screen when trying to boot the stock - not that I do it that often of course. I can still get into safestrap and boot the nexus 2.01 rom with no issues so am okay for now. Would I need something like a rooted 14.3.2.6 to fix this?
aren't these roms very old? Is there any way to get the latest AMAZON STOCK apps AND keep root? I really like the FIRE OS (way more than stock Android) but I also want all apps etc.
_Alex_ said:
Since I"m heavily tied into the Amazon ecosystem and have other Kindle devices, installing HDX Nexus 2.01 didn't work for me.
However, thanks to @ggow, using the same upgrade guide, Iwas able to get my 3.1.0 to 3.2.6, allowing my fire hdx devices to finally be able to do screen sharing with my fire TVs! I did have to restore /data, enable xposed + hdxposed, re-install kindlefree + Google play store APKs & stucks wallpaper fix to be back at 100%...
Click to expand...
Click to collapse
Was screen sharing to Fire TV not available on 13.3.2.3.2? Furthermore, what exactly does 13.3.2.6 offer that's new/improved? Does anyone have the changelog for this?
OK, so the LATEST FIRE OS Version that is rootable is "13.3.2.6" for the THOR device, is that correct? Or is there any other way to root a newer OS Version?´
Oh, and how can I flash this update? My device is rooted, but I have a very old OS Version on my kindle hdx.
Hey guys.. I screwed up.
I have a fire hdx Apollo that had been properly up(down)graded and running fine with 2.01. For some reason (and my lack of understanding the correct versions of things) I thought it would be a good idea to install the Apollo update on my stock rom. This of course has now caused boot loops on my stock boot but not my 2.01 boot.
Would love to be able to restore the stock as I do use some of the fire's capabilities from time to time. Sadly I did not do a backup before the update (kicks self furiously).
I DO have a backup from before the upgrade/downgrade so maybe I could restore that then push through the upgrade steps again or something. I'm worried that I will bork my safestrap or do something worse based on my proclivity for damage and chaos.
E.
_Alex_ said:
Hey @ggow, would it be possible for you to release a rooted 14.3.2.6?
Click to expand...
Click to collapse
Hi _Alex_,
Sorry about the long wait, I have posted a zip for 14.3.2.6. See OP.
Hey @ggow,
Thanks for your hard work. Could you possibly make an image for 13.3.2.4 (Thor)? It would be nice to have along with Nexus HDX 2.0.2.
NextDroid said:
Hey @ggow,
Thanks for your hard work. Could you possibly make an image for 13.3.2.4 (Thor)? It would be nice to have along with Nexus HDX 2.0.2.
Click to expand...
Click to collapse
Yes, I'll sort one out for you. Let you know when its up.
Sent from my Nexus 6 using Tapatalk
Looks like we're going to need it with the new bootloader bypass!
Just to clarify because someone asked, users of the HDX Nexus ROM would need it to downgrade to a firmware that the unlock works on.
ggow said:
Yes, I'll sort one out for you. Let you know when its up.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thank you!
Sent from my device
recreated the error with the Symlink. Crossposting from the TWRP Thor thread
Wiped system manually
The error log is:
Code:
Wiping system...
Symlinking...
symlink: some symlinks failed
[COLOR="Red"]E: Error executing updater binary in zip '/sdcard/TWRP13.3.1.0.zip'[/COLOR]
Error flashing zip '/sdcard/TWRP13.3.1.0.zip'
Updating partition details
Interesting... Getting the same error when I try to flash the original HDX 13.3.2.3 firmware, after I renamed it from .bin to .zip
Hi @ggow !
I made a flashable zip of the 4.5.2 update for Thor which is compatible with the signing exploit (bootloader/fw flashing removed and modified bootimage with happened dt) as there was some demand.
I'm not sure i should again create a thread for this rom(s) as we may be easily lost. Maybe all our "stock/modified stocks" roms should be in the same thread. What do you think about this ? Here is the link in case : http://android.mydedibox.fr/hdx/update-kindle-13.4.5.2_user_452004120-twrp.zip
Note that i only renamed "otacert.zip" to "otacert.old" on this rom as the "dcp" apk name has changed and i don't remember how i fixed that ... so ota updates may still be enabled isnt it ?
---------- Post added at 03:21 PM ---------- Previous post was at 03:16 PM ----------
aquaphun said:
recreated the error with the Symlink. Crossposting from the TWRP Thor thread
Wiped system manually
The error log is:
Code:
Wiping system...
Symlinking...
symlink: some symlinks failed
[COLOR="Red"]E: Error executing updater binary in zip '/sdcard/TWRP13.3.1.0.zip'[/COLOR]
Error flashing zip '/sdcard/TWRP13.3.1.0.zip'
Updating partition details
Interesting... Getting the same error when I try to flash the original HDX 13.3.2.3 firmware, after I renamed it from .bin to .zip
Click to expand...
Click to collapse
I don't know if it's the problem but the appolo recovery is based on an older kernel (3.1.0?) which doesn't have full selinux support. This prevented some zip to be properly flashed (at least on thor) until i use the 4.5.2 kernel sources. Unfortunately we will have to wait for @ggow to receive his new device, in the hope of an exploitable one (but this may be a different problem)
Edit : oups, you are on thor so it's not the problem !
Cpasjuste said:
Hi @ggow !
I made a flashable zip of the 4.5.2 update for Thor which is compatible with the signing exploit (bootloader/fw flashing removed and modified bootimage with happened dt) as there was some demand.
I'm not sure i should again create a thread for this rom(s) as we may be easily lost. Maybe all our "stock/modified stocks" roms should be in the same thread. What do you think about this ? Here is the link in case : http://android.mydedibox.fr/hdx/update-kindle-13.4.5.2_user_452004120-twrp.zip
Note that i only renamed "otacert.zip" to "otacert.old" on this rom as the "dcp" apk name has changed and i don't remember how i fixed that ... so ota updates may still be enabled isnt it ?
---------- Post added at 03:21 PM ---------- Previous post was at 03:16 PM ----------
I don't know if it's the problem but the appolo recovery is based on an older kernel (3.1.0?) which doesn't have full selinux support. This prevented some zip to be properly flashed (at least on thor) until i use the 4.5.2 kernel sources. Unfortunately we will have to wait for @ggow to receive his new device, in the hope of an exploitable one (but this may be a different problem)
Edit : oups, you are on thor so it's not the problem !
Click to expand...
Click to collapse
Hi @Cpasjuste,
Yes that's fine, I'll put your 4.5.2 image up on the same thread - no point replicating things
On 4.5.2 I wasn't sure which services needed to be disabled to prevent OTA. I'll add a note for this file to warn people to be careful when using it.
As things have changed with how root is obtained and how OTA's are limited to users since 5.0, I hope this thread to serve as a basic overview of the root options available to you. I see a lot of threads asking about updating to Lollipop and about returning to stock to receive OTA updates.. from rooted users.
*The below post covers updating to 5.0 only. For updating to 4.4.x, read this thread: [Info] Rooted user? Learn to update properly
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have created this thread as I have strong feelings about rooted users and OTA's in general, so I wanted to collect my thoughts together in a single thread to hopefully persuade rooted users to avoid OTA updates. Of course, you're free to choose to ignore this.
OTA's are simple for unrooted users. They are minimal effort, quick and require no knowledge. However they have a propensity to go wrong - often resulting in a user having to factory reset to get things working.
OTA's are designed to be small to save on data usage. This is achieved by not supplying the entire ROM, kernel or app, but instead, including patches. These patch files (*.p) will unpack the recovery.img, bootloader.img, boot.img or *.apk and insert the new code into it. This means the OTA expects an exact version to install. You cannot skip an OTA and expect to apply a later one because the code in the patch might not "fit". Also, this is why modified users cannot apply an OTA. There are ways for rooted, stock kernel, no modification users to apply OTA updates but it is not recommended
Please note, rooted users will still receive the OTA notification. You do not need to apply it though. Some Custom ROMS even receive it.
Well if you are modified, you have to first return completely to stock to apply an OTA. This is a relatively long process compared to other options available to you. If you are simply rooted with stock kernel and no modifications, you can simply re-apply root after accepting the OTA, but it's a bit messy and still - it's an OTA that can go wrong. I think part of OTA's appeal is you can do it anywhere - but this is also it's biggest problem. rooted users need resources to be available to them so they can remedy whatever needs remedying after application.
In short, it's just not the best option, Why would anyone ever choose "not the best"?
Section 1, from Stock (unrooted)
Method 1 (You are fully stock 5.0)
1. Unlock bootloader if necessary (This wipes data)
2. Fastboot flash a custom recovery image (of your choice)
3. Fastboot flash a custom boot.img (@Chainfire for basic root, @sykopompos for full permissive mode)
4. Flash from recovery, SuperSU (Please note BETA 2.27+ May mean you do not need a modified boot.img)
You can get the boot.img's and SuperSU from here: [ROM] N5 Lollipop + Stock IMG Mirrors & More! (by @vomer)
Method 2a (You are fully stock 4.4.x)
1. Unlock bootloader if necessary (This wipes data)
2. Fastboot flash a custom recovery image (of your choice)
3. Fastboot flash stock 5.0 system.img (this will not wipe data if yous till have data at this time, however, you MAY still need to wipe data later)
4. Fastboot flash a custom boot.img (@Chainfire for basic root, @sykopompos for full permissive mode)
5. Flash from recovery, SuperSU (Please note BETA 2.27+ May mean you do not need a modified boot.img)
You can get the boot.img's and SuperSU from here: [ROM] N5 Lollipop + Stock IMG Mirrors & More! (by @vomer)
Method 2b (You are fully stock 4.4.x)
1. Unlock bootloader if necessary (This wipes data)
2. Accept OTA update
3. Fastboot flash a custom recovery image (of your choice)
4. Fastboot flash a custom boot.img (@Chainfire for basic root, @sykopompos for full permissive mode)
5. Flash from recovery, SuperSU (Please note BETA 2.27+ May mean you do not need a modified boot.img)
You can get the boot.img's and SuperSU from here: [ROM] N5 Lollipop + Stock IMG Mirrors & More! (by @vomer)
Method 3a (You are fully stock 4.4.x)
1. Unlock bootloader if necessary (This wipes data)
2. Use the google Factory flash-all method to flash 5.0
3. Use the CF-Autoroot method to modify the kernel (boot.img) for root (Will not get permissive mode) and SuperSU
4. Fastboot flash a custom recovery
You can follow this guide here: [How-To][Windows] Download and Flash Android 5.0 and Reroot & Recovery (by @spc_hicks09)
Method 3b (You are fully stock 4.4.x)
1. Unlock bootloader if necessary (This wipes data)
2. Accept OTA update
3. Use the CF-Autoroot method to modify the kernel (boot.img) for root (Will not get permissive mode) and SuperSU
4. Fastboot flash a custom recovery
Method 3c (You are fully stock 5.0)
1. Unlock bootloader if necessary (This wipes data)
2. Use the CF-Autoroot method to modify the kernel (boot.img) for root (Will not get permissive mode) and SuperSU
3. Fastboot flash a custom recovery
Section 2, from rooted with custom recovery
Method 4 (You are rooted 4.4.x with custom recovery)
1. Fastboot flash stock 5.0 system.img (this will not wipe data if you still have data at this time, however, you MAY still need to wipe data later)
2. Fastboot flash a custom boot.img (@Chainfire for basic root, @sykopompos for full permissive mode)
3. Flash from recovery, SuperSU (Please note BETA 2.27+ May mean you do not need a modified boot.img)
You can get the boot.img's and SuperSU from here: [ROM] N5 Lollipop + Stock IMG Mirrors & More! (by @vomer)
Method 5 (You are rooted 4.4.x with custom recovery)
1. Flash from recovery, an existing packages ROM.zip
2. Flash from recovery, a flashable custom boot.img (@Chainfire for basic root, @sykopompos for full permissive mode)
3. Flash from recovery, SuperSU (Please note BETA 2.27+ May mean you do not need a modified boot.img)
You can get the boot.img's and SuperSU from here: [ROM] N5 Lollipop + Stock IMG Mirrors & More! (by @vomer)
You can get a ROM.zip from here: [ROM] [STOCK] Android 5.0 LRX21O - Stock/Flashable (11/12/14) )by @bigxie
Please note, there is no OTA option mentioned here in section 2. This is becuse now, since 5.0 - you MUST be fully stock (recovery included) to accept an OTA update, so the process doesn't really exist
OTA is designed for everyday users. If you're going to be rooted, you should understand what you have and what it means to be rooted. Familiarise yourselves with fastboot. Familiarise yourself with your recovery. Learn how to take backups and you will get much more out of your phone that constantly wasting time returning to stock, applying OTA's then re-rooting. You're wasting time doing this - it's a fools errand. I hope this thread helps to open your eyes and your minds.
If you still want to (return to stock in order to) accept OTA updates, even after reading this thread (perhaps because doing things properly mean more work for you) then perhaps you shouldn't be rooted. Having, maintaining and understanding root takes effort and if you're not willing to put the time in, you will become a danger to your phone and possibly a drain on this forum too We write lots of guides and info threads for your benefit. If you have questions, please just ask.
Please let me know if I have missed anything
This is not a "help me update" thread so please don't post here asking for help with a particular process. Post in the thread for the method you are using. This thread is to discuss which option/method would be best for you.
Do we really need yet another thread on updating and rooting?
Also, permissive boot image is no longer needed on Lollipop.
http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Guide on how to retain SuperSU Root permission after flashing Code Blue kernel
How To Retain SuperSU Root Permission with Code Blue Kernel on custom Lollipop ROMs
Not sure how many here have flashed Code Blue kernel on N5X ROM (ver.5.4), but recently I discovered that even though I had Superuser in my Settings menu, my Rooted apps (MyBackup Root, Root Explorer, Wakelock Detector) were not working after I flashed a custom kernel like Code Blue kernel.
After digging through various forum threads, I have managed to make my rooted apps work again on a custom kernel like Code Blue.
Hopefully some of you may find this how to guide helpful.
Pre-requisite
Download the following files to your Nexus 5:-
Permissive Kernel Zip
- https://www.androidfilehost.com/?fid=95747613655048458
Code Blue Kernel for Lollipop
- http://forum.xda-developers.com/google-nexus-5/orig-development/kernel-t2697951
Latest SuperSU by Chainfire (at the time of this post it is [BETA][2014.11.20] SuperSU v2.27)
- http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
- Direct download link: http://download.chainfire.eu/630/SuperSU/BETA-SuperSU-v2.27.zip
Step 1: Reboot to TWRP Custom Recovery
1. Shut off the phone
2. Press and hold Volume Down + Power Button
3. Use Volume down to toggle to Recovery Mode and confirm selection using the Power Button
Step 2: Flash the Permissive Kernel
1. Click on Install button in TWRP Custom Recovery
2. Select the Permissive Kernel Zip file which is N5_+LPX13D_PermissiveKernel.zip
3. Swipe to Confirm Flash
4. Click on the Home button only!
Important Note: Do Not click Reboot System yet!!!
Step 3: Flash the Code Blue Kernel
1. Click on Install button in TWRP Custom Recovery
2. Select the Code Blue Kernel Zip file (at the time of this post is Code_Blue_r620-L_hammerhead.zip)
3. Swipe to Confirm Flash
4. Click on the Home button only!
Important Note: Do Not click Reboot System yet!!!
Step 4: Flash the latest SuperSU
1. Click on Install button in TWRP Custom Recovery
2. Select the SuperSU Zip file (at the time of this post is BETA-SuperSU-v2.27.zip)
3. Swipe to Confirm Flash
4. Now click on Reboot System button and wait for the phone to reboot.
Once the phone boots up, you should have SuperSU appear under the Settings menu.
Try to reinstall your rooted apps again just to make sure they get fresh root permission from SuperSU.
upndwn4par said:
Do we really need yet another thread on updating and rooting?
Click to expand...
Click to collapse
Yes indeed. There is no single place that addresses all the options. Any guide we have just gives one or two methods. This thread serves as a place to direct the hundreds of people asking the same question that drives those of us who frequently assist these users a little bit batty.
upndwn4par said:
l
Also, permissive boot image is no longer needed on Lollipop.
http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Then I shall verify the lack of requirement and update accordingly - should I be satisfied. Thanks for bringing it to my attention.
upndwn4par said:
Do we really need yet another thread on updating and rooting?
Also, permissive boot image is no longer needed on Lollipop.
http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
I was under the impression this wasn't ready for release to the masses just yet?
It's definitely the solution I'm waiting for and happy to enjoy the standard experience until it's approved for the less technical amongst us.
Updated OP to make it feel less like a roll-up thread as that is not what it is intended to be. It's an info thread to allow users to understand what update / root options are available to them in regards to Android 5.0.
This is not a "help me update" thread so please don't post here asking for help with a particular process. Post in the thread for the method you are using. This thread is to discuss which option/method would be best for you.
I appreciate the thread. There is an over abundance of random threads addressing methods. It is nice to have a centrally located one. I haven't jumped on LP just yet, as I am waiting a little while for more development. It is nice to know people are taking the time to collect the options. I am tired of reading over and over about how people failed.
As usual, good post rootSU
wangdaning said:
I appreciate the thread. There is an over abundance of random threads addressing methods. It is nice to have a centrally located one. I haven't jumped on LP just yet, as I am waiting a little while for more development. It is nice to know people are taking the time to collect the options. I am tired of reading over and over about how people failed.
As usual, good post rootSU
Click to expand...
Click to collapse
Thank you kindly.
upndwn4par said:
Do we really need yet another thread on updating and rooting?
Also, permissive boot image is no longer needed on Lollipop.
http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
If this is how you have root could you please test something for me
1 - root (mount as rw) on es file explorer
2 - installing better battery stats through app to system
3 - use Terminal Emulator and type su (press enter) type am start (press enter) and does it return with error or lots of options
Sent from my Android 5.0 Nexus 5
Ben36 said:
If this is how you have root could you please test something for me
1 - root (mount as rw) on es file explorer
2 - installing better battery stats through app to system
3 - use Terminal Emulator and type su (press enter) type am start (press enter) and does it return with error or lots of options
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
1) Works
2) Works
3) Haven't found a terminal emulator that works on lollipop. In adb shell I get what looks like a man page in Linux.
This one works - https://play.google.com/store/apps/details?id=jackpal.androidterm
Sent from my Android 5.0 Nexus 5
upndwn4par said:
1) Works
2) Works
3) Haven't found a terminal emulator that works on lollipop. In adb shell I get what looks like a man page in Linux.
Click to expand...
Click to collapse
Ben36 said:
This one works - https://play.google.com/store/apps/details?id=jackpal.androidterm
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
+1 for jackpal.
Ben36 said:
This one works - https://play.google.com/store/apps/details?id=jackpal.androidterm
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
rootSU said:
+1 for jackpal.
Click to expand...
Click to collapse
Been using that one for years. Won't install from Google Play. Same error that a lot of people get on Lollipop.
The one in ROM Toolbox FCs.
upndwn4par said:
Been using that one for years. Won't install from Google Play. Same error that a lot of people get on Lollipop.
The one in ROM Toolbox FCs.
Click to expand...
Click to collapse
Weird... Works fine here. But your error can't be a root issue if it's on actual install of the app from the play store
Sent from my Android 5.0 Nexus 5
upndwn4par said:
Been using that one for years. Won't install from Google Play. Same error that a lot of people get on Lollipop.
The one in ROM Toolbox FCs.
Click to expand...
Click to collapse
Run a logcat. The smart money is on INSTALL_FAILED_DUPLICATE_PERMISSION. I had this when i tried to install quicksearchbox. Turned out
Code:
Package com.google.android.googlequicksearchbox attempting to redeclare permission com.android.launcher3.permission.RECEIVE_LAUNCH_BROADCASTS already owned by com.android.launcher3
Wonder if you find similar
OK I tested the SuperSU 2.27 BETA on stock kernel without permissive boot.img
Most things I tested worked OK. For example, am start displayed man, which I would expect. However, Viper4Android I didn't get working, which is one app we knew previously to require permissive kernel. Also I asked @sykopompos if we still need permissive and he said SELinux is buggy in L so this method is still a bit different (patraphrasing) So although, yes this is an alternative worth mentioning, it doesn't rule out the Permissive option completely.
I will adjust the OP appropriately.
I've always used permissive with pie patch and i have never had any problems like I see others post about
Sent from my Android 5.0 Nexus 5
Ben36 said:
I've always used permissive with pie patch and i have never had any problems like I see others post about
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
I've never needed PIE patch. I thought PIE patch was if you didn't have permissive, but I don't really know a lot about it. I just use permissive
rootSU said:
I've never needed PIE patch. I thought PIE patch was if you didn't have permissive, but I don't really know a lot about it. I just use permissive
Click to expand...
Click to collapse
Es file explorer root access wouldn't work without pie patch even with the permissive kernel
Sent from my Android 5.0 Nexus 5
Ben36 said:
Es file explorer root access wouldn't work without pie patch even with the permissive kernel
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
Ah ok. But yeah, bad application
[Q&A] [23.0.1.A.5.77] Debloated, Deodexed, Zipaligned, Rooted, Super User Mode - 28/
Q&A for [23.0.1.A.5.77] Debloated, Deodexed, Zipaligned, Rooted, Super User Mode - 28/Jan/15
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [23.0.1.A.5.77] Debloated, Deodexed, Zipaligned, Rooted, Super User Mode - 28/Jan/15. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I know these are novice questions but please bear with me as I just want to understand the process.
I have the Z3C rooted on 5.77 with SuperSU, Xposed and various modules installed plus other ‘normal’ apps.
1. So if I do as in the OP I will have a ‘stock’ Z3C without the apps listed in the OP, meaning I have to install Xposed, modules and all my ‘normal’ apps afterwards? (don’t mind this, just want to be clear)
2. Is SuperSU ok?
3. Can I sync a backup from Sony Companion to get all my personal stuff back?
4. A.If I want to get one of the deleted apps back I just install it from e.g. GooglePlay? or
B. Using RootExplorer can I just delete the App's apk & odex files with same result as flashing?
5. Main reason for wanting to try/use this is I would like to use the Xperia™ Xposed module, so once above is completed I can d/l Xperia™ Xposed , activate it and I’m good to go?
Again, thanks for bearing with me and any advice appreciated.
I softbricked my D5833, what went wrong?
Requirements:
- Z3 Compact (any) or even Z3 (to be confirmed)
- Running rooted 23.0.1.A.5.77 firmware
- Recovery
- System partition mountable as r/w
Install:
1. Enter recovery and backup your current rom (good practice)
2. Download flashable zip
3. Enter recovery and flash it
4. Wipe Cache and Dalvik Cache (and Data - optional)
Click to expand...
Click to collapse
Hi there. I had a well running rooted 23.0.1.A.5.77 firmware. After flashing the "[23.0.1.A.5.77] Debloated, Deodexed, Zipaligned, Rooted, Super User Mode" my phone wouldn't boot any more. It got stuck on the Sony logo.
I cant understand why. Is it because I have a D5833? Or might it be because after wiping the cache and the Dalvik cache I also ran "Prepare for flashing a new image" (I can't remember the exact phrase right now)
Please tell me what you think went wrong.
richard roe said:
Hi there. I had a well running rooted 23.0.1.A.5.77 firmware. After flashing the "[23.0.1.A.5.77] Debloated, Deodexed, Zipaligned, Rooted, Super User Mode" my phone wouldn't boot any more. It got stuck on the Sony logo.
I cant understand why. Is it because I have a D5833? Or might it be because after wiping the cache and the Dalvik cache I also ran "Prepare for flashing a new image" (I can't remember the exact phrase right now)
Please tell me what you think went wrong.
Click to expand...
Click to collapse
Never mind.
Thanks for this, @serajr. I just had a quick question regarding recovery. I have rooted my device with this guide (all steps completed); when I boot into TWRP and flash this .zip, how do I maintain the Dual Recovery installed in the root guide?
Apologies, I've found that recovery is still maintained on the device after using the .zip but NDRUtils is uninstalled which is easily downloadable again.
apSlain said:
Thanks for this, @serajr. I just had a quick question regarding recovery. I have rooted my device with this guide (all steps completed); when I boot into TWRP and flash this .zip, how do I maintain the Dual Recovery installed in the root guide?
Apologies, I've found that recovery is still maintained on the device after using the .zip but NDRUtils is uninstalled which is easily downloadable again.
Click to expand...
Click to collapse
Thanks buddy!
Keep cool wiping everything AFTER flashing this thread zip file, it will just do changes into folders below:
/system/app (here including latest Superuser.apk)
/system/priv-app
/system/framework
Root binary (/system/xbin/su) and recovery files won't be touched!
serajr said:
Thanks buddy!
Keep cool wiping everything AFTER flashing this thread zip file, it will just do changes into folders below:
/system/app (here including latest Superuser.apk)
/system/priv-app
/system/framework
Root binary (/system/xbin/su) and recovery files won't be touched!
Click to expand...
Click to collapse
Thanks for the prompt response! So, as far as I've understood, despite NDRUtils being uninstalled after flashing, recovery is still maintained and I just need to redownload NDRUtils if I need it via the Play Store.
I just had two quick follow up questions if you have the time to answer them?
1. If I want to go back to complete stock i.e. out-of-the-box functionality with all the bloat reinstalled, recovery deleted, etc., am I right in saying all I need to do is re-flash a stock firmware from this thread with Flashtool?
2. Can I delete your flashable .zip file and the SonyRICDefeat .zip file from /sdcard0 after flashing them in recovery?Hopefully these are simple questions. Thanks!
apSlain said:
Thanks for the prompt response! So, as far as I've understood, despite NDRUtils being uninstalled after flashing, recovery is still maintained and I just need to redownload NDRUtils if I need it via the Play Store.
I just had two quick follow up questions if you have the time to answer them?
1. If I want to go back to complete stock i.e. out-of-the-box functionality with all the bloat reinstalled, recovery deleted, etc., am I right in saying all I need to do is re-flash a stock firmware from this thread with Flashtool?
2. Can I delete your flashable .zip file and the SonyRICDefeat .zip file from /sdcard0 after flashing them in recovery?Hopefully these are simple questions. Thanks!
Click to expand...
Click to collapse
1. Yes, you are! By fully flashing ftf file you will be on raw stock fw again!!
2. Yep, you can delete both!
First time at debloating and deleted the apks at /system/etc/customization/applications/. before first uninstalling.
Could some kind soul post the list or instruct how i can work out the list from the zip? tried exploring the system.ext4 file but that didnt help as i thought it would.
Thanks for the debloat.
Serajr, can you release next version of your modification as a fully fledged ROM, please? It would be way easier to use.
I've just bought my Xperia and i'm a bit confused. With my old Samsung Galaxy everything was easy as a dream:
- flash popular ROM
- update it via OTA for years
With Xperia everything is much more complicated. (2 bootloaders, DRM keys, flash counters, etc.)
Sometimes I think that i'm too old for this but I can't imagine to use Android phone without root, xposed framework, firewall, navbar customization...
Regards.
Newb here, so I can't find my zip file when searching for zip with CWM. I did put it on SDcard and it's mounted, heck I put it in all kinds of folders for a look, but CWM is not recognizing it.
What is the system/method you guys have flashed this rom?
What have I missed? What have I not done? Is there another method?
Thanks.
Edit:
got it, thanks
I am hopefully not the only one with this problem on this deodexed rom but I have the problem to not be able to change the lockscreen wallpaper. It only shows the wallpaper of the homescreen at my lockscreen.
Is anyone else experiencing same issue or has a solution for me?
Maybe only a missing systemapp....
Sent from my D5803 using XDA Free mobile app
Kernel Problem
The debloated ROM works fine.
Problem: If I flash a Kernel (of course with unlocked Bootloader ) for instance AndroPlus or XZDR Kernel with your ROM - -> Bootloop.
With original/generic .77 firmware - -> no Bootloop
Do I make a mistake?
[23.1.A.0.690] Debloated, Deodexed, Zipaligned, Rooted, Super User Mode - 04/04/15
Sorry everyone,
Dont know where my post ended up here???
Of course, my mistake
QUOTE
Link for the last KK version
Dear @serajr
could you post a link to your last KK version? I'm waiting for LP xposed to be become stable, and until that I'll stay on KK
I'm on rooted stock (december KK), so I just flash this in recovery and it cleans all the sh*t from an existing ROM? I don't need to start over?
UNQUOTE
Yeah, I second this request (and questions)
Much appreciated.
Finally it's here!!! A big thanks to the developer *___*
Norup58 said:
Sorry everyone,
Dont know where my post ended up here???
Of course, my mistake
QUOTE
Link for the last KK version
Dear @serajr
could you post a link to your last KK version? I'm waiting for LP xposed to be become stable, and until that I'll stay on KK
I'm on rooted stock (december KK), so I just flash this in recovery and it cleans all the sh*t from an existing ROM? I don't need to start over?
UNQUOTE
Yeah, I second this request (and questions)
Much appreciated.
Click to expand...
Click to collapse
Go to original thread and take it under "KitKat version (23.0.1.A.5.77)"
Why deodex? Deodexing impairs performance and gains nothing but the ability to mess with system apk more easily.
Worked perfectly for me.
Got Xposed with GravityBox and more all up and running. No bootloops after multiple reboots as well.
I, too, am in doubt which is the correct/easiest approach for upgrading to Lp 5.0.2 from KK .77 LB.
It appears we can piece together a working solution for a Lp with R/W, Recovery & Xposed Framework:
R/W: e.g. use the one from Meetdaleet, which we apparently can 'dirty' flash directly from .77 to 5.0.2
RECOVERY: http://forum.xda-developers.com/showthread.php?t=2261606&page=384 -Read post 3837 & jump to 3876 where *NUT* says it will be implemented in DualRecovery
Xposed Framework: see *Serajr*'s post 177
As *NUT* is planning on releasing DualRecovery 2.84 next week I think I'll wait and in the meantime hoping Xposed Framework will be updated also.
sry wrong post thx for the share
Code:
[B]NOTE : [/B]PROCEED AT YOUR OWN RISK. Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from [U]Stock WW-15.2016.1804.252[/U] on primary device. Also I will try to help out in case of issues.
If on Custom Rom then visit THIS THREAD to first return back to Stock Rom.
If you want to DOWNGRADE then visit THIS THREAD to revert to older firmware.
This thread is for those who are on stock rooted rom with TWRP installed and want to have system update WITHOUT LOOSING DATA.
How to ,
Backup important app data like whatsapp chats etc. (precautionary step & is not needed, but better be safe).
Download latest modified system update file - WW-15.2016.1902.340.
Download decrypt.zip from HERE.
Download Magisk from HERE .
Reboot to TWRP.
Flash the ROM file.
Flash decrypt.zip file.
Flash Magisk zip file.
Reboot & Enjoy.
(optional) If you want to boost up by debloating then use this MOD.
(optional) If you want to boost up BATTERY then use this GUIDE.
No partition is required to be wiped before or after flashing these files.
Also you do not have to uninstall Magisk before the procedure.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
NOTE : ROM works independant of RAM i.e. applicable for 3/4/6 GB variants.
Recommended TWRP : https://androidfilehost.com/?fid=3700668719832241089 by @SagarMakhar.
Older full firmware packages :
WW-15.2016.1805.309 (14th June 2018)
WW-15.2016.1805.311 (04th July 2018)
WW-15.2016.1805.316 (16th July 2018)
WW-15.2016.1805.318 (23rd July 2018)
WW-15.2016.1808.323 (21st August 2018)
WW-15.2016.1808.326 (06th Sept 2018)
WW-15.2016.1808.327 (20th Sept 2018)
WW-15.2016.1809.331 (17th Oct 2018)
WW-15.2016.1810.334 (02nd Nov 2018)
WW-15.2016.1810.337 (20th Nov 2018)
WW-15.2016.1811.338 (19th Dec 2018)
WW-15.2016.1901.339 (22nd Jan 2019)
.A.V.i.n.a.S.h. said:
Modified full firmware packages (New packages will be added as they are available on Asus site) :
WW-15.2016.1805.309 (24th June 2018)
Click to expand...
Click to collapse
Will this Mod Rom work on indonesian version (ZB602KL) ?
I am on custom rom now and would like to back to stock and still rooted with this modified rom.
Thanks
Tolay said:
Will this Mod Rom work on indonesian version (ZB602KL) ?
I am on custom rom now and would like to back to stock and still rooted with this modified rom.
Thanks
Click to expand...
Click to collapse
I am on data pack right now .. tomorrow I will have WiFi access.
I will download and compare ZB602KL version full rom and reply back if I find a difference.
As far as I know, both versions are same but let me check once. I will let you know
first i remove my magisk or not,or flash without removing magisk
plz tell me full procedure to flash
.A.V.i.n.a.S.h. said:
I am on data pack right now .. tomorrow I will have WiFi access.
I will download and compare ZB602KL version full rom and reply back if I find a difference.
As far as I know, both versions are same but let me check once. I will let you know
Click to expand...
Click to collapse
Same here , ZB602KL variant.
Courious about different..
rajesh.880889 said:
plz tell me full procedure to flash
Click to expand...
Click to collapse
Yes .. flash without removing Magisk as we do not want to setup Magisk again.
We will reflash Magisk during installation.
Please follow given sequence of flash .. Rom - Decrypt - Magisk :good:
Tolay said:
Will this Mod Rom work on indonesian version (ZB602KL) ?
I am on custom rom now and would like to back to stock and still rooted with this modified rom.
Thanks
Click to expand...
Click to collapse
Please refer to other guide -- [ROM][STOCK][ZB601KL/ZB602KL] TWRP flashable Stock ROM
This guide is for those who are on Stock ROM. Process is little different.
Randyshare said:
Same here , ZB602KL variant.
Courious about different..
Click to expand...
Click to collapse
The method is applicable for both ZB601KL and ZB602KL .. Confirmed
how to flash rom steps
plz steps for rom flashing what to delete what to have,
i am on stock rom and magisk installed
rajesh.880889 said:
plz steps for rom flashing what to delete what to have,
i am on stock rom and magisk installed
Click to expand...
Click to collapse
Please follow the steps as in first post.
You should have TWRP along with Stock rom which you have I believe.
Download the 3 files mentioned in first post - ROM + Decrypt + Magisk and keep them in storage.
Reboot to TWRP and flash files in below seqeunce -
Stock_X00T_Patch_May_Version_309_TWRP.zip
decrypt.zip
Magisk-v16.0.zip
Do not wipe anything in TWRP before or after installation .. do not uninstall Magisk or anything else.
Just flash the files are reboot.
Other than the changes to the update script, are there any other changes you have done? The script output in twrp says 'patching system image that is modified by ....."
So I am wondering if you made changes to the system.img file too?
candiesdoodle said:
Other than the changes to the update script, are there any other changes you have done? The script output in twrp says 'patching system image that is modified by ....."
So I am wondering if you made changes to the system.img file too?
Click to expand...
Click to collapse
No changes .. it is just for testing .. I have not created the entire ROM so I mentioned this is Guide section and not the ROM development section.
Also the new file I have updated has no such message but just a message to identify the ROM change. You must have the old version which was there on Sunday.
.A.V.i.n.a.S.h. said:
No changes .. it is just for testing .. I have not created the entire ROM so I mentioned this is Guide section and not the ROM development section.
Also the new file I have updated has no such message but just a message to identify the ROM change. You must have the old version which was there on Sunday.
Click to expand...
Click to collapse
I downloaded last night only. About 24 hrs ago. I am referring to the first line In the script. See the SS
Also who made the new zip? I am interested in finding out what changes are being made if any other than the updater script.
candiesdoodle said:
I downloaded last night only. About 24 hrs ago. I am referring to the first line In the script. See the SS
Also who made the new zip? I am interested in finding out what changes are being made if any other than the updater script.
Click to expand...
Click to collapse
New zip name - Stock_X00T_Patch_May_Version_309_TWRP.zip
As already mentioned, the message was put just to let me know if the flashed file is changed one or original one from Asus.
I am taking Asus original rom and doing modification in update-script and if needed will make changes to boot.img (replacing with old boot image from Asus) and any other file to keep Magisk+TWRP to be working after update. I test the update for some time and then share it with all.
I will mention any substantial changes if any (for v309 no changes are there).
I have no intention to change what Asus has provided.
Purpose is to provide stock tested firmware for easy update at one stop .. and an easy way for people to come back to stock ROM.
.A.V.i.n.a.S.h. said:
New zip name - Stock_X00T_Patch_May_Version_309_TWRP.zip
As already mentioned, the message was put just to let me know if the flashed file is changed one or original one from Asus.
I am taking Asus original rom and doing modification in update-script and if needed will make changes to boot.img (replacing with old boot image from Asus) and any other file to keep Magisk+TWRP to be working after update. I test the update for some time and then share it with all.
I will mention any substantial changes if any (for v309 no changes are there).
I have no intention to change what Asus has provided.
Purpose is to provide stock tested firmware for easy update at one stop .. and an easy way for people to come back to stock ROM.
Click to expand...
Click to collapse
Thanks for confirmation. Great work
update ota automatic
hey after i follow your guide, can i get automatic update ftom system udpate?
hi.
can you make a guide on how you modify the zip file?
i successfully used it to update from 247 to 309
Kionaru said:
hey after i follow your guide, can i get automatic update ftom system udpate?
Click to expand...
Click to collapse
You will get update notifications .. no issue. But the update will not flash if you have TWRP and Magisk.
I will provide TWRP flashable file (after testing) in this thead in future. So expect the update within 48 hrs after new update (full ROM for the OTA) is relased by Asus.
To flash OTA there is an excellant guide HERE you can follow that to flash OTA (i.e. delta file). In this thread you can get full file.
.A.V.i.n.a.S.h. said:
Code:
[B]NOTE : [/B]Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from [U]Stock WW-15.2016.1804.252[/U] on primary device. Also I will try to help out in case of issues. BUT still proceed at your own risk.
This thread is for those who are on stock rooted rom with TWRP installed and want to have system update WITHOUT LOOSING DATA.
If you are coming from Custom ROM then
How to ,
Backup important app data like whatsapp chats etc. (precautionary step & is not needed but better be safe).
Download modified system update file from
[*]Download decrypt.zip from
[*]Download Magisk from
[*]Reboot to TWRP.
[*]Flash the ROM file.
[*]Flash decrypt.zip file.
[*]Flash Magisk zip file.
[*]Reboot & Enjoy.
[*](optional) If you want to boost up by debloating then
No partition is required to be wiped before or after flashing these files.
Also you do not have to uninstall Magisk before the procedure.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
Click to expand...
Click to collapse
Dude, i'm on Stock - 14.2016.1804.305 with TWRP & Magisk. will it work on me?
Thanks
boneyd26 said:
Dude, i'm on Stock - 14.2016.1804.305 with TWRP & Magisk. will it work on me?
Thanks
Click to expand...
Click to collapse
Yes .. it is for all those who are on stock ROM.
You can update from any past version i.e. v247,v252 &v305 to v309
[UPDATE/KEEP ROOT GUIDE] SEP 2020 (RP1A.200720.009) "FLAME" Magisk/Stock Boot Images
PLEASE READ ALL ADDITIONAL NOTES IN THE FIRST 2 POSTS!!!
THIS IS A MAJOR UPDATE TO A NEW VERSION OF ANDROID AND CONSEQUENTLY COMES WITH A MUCH HIGHER RISK OF BOOTLOOPING IF YOU'RE NOT CAREFUL.
PLEASE DROP A QUICK THANKS IF YOU STILL FIND THESE GUIDES HELPFUL! :good:
(I PERSONALLY AM WAITING TO UPDATE TO ANDROID R (WAITING ON GRAVITYBOX) SO I WON'T BE ABLE TO HELP AS MUCH - PLEASE BE KIND TO ONE ANOTHER AND HELP EACH OTHER OUT! )
***IF YOU ARE STILL ON AUGUST / ANDROID 10 BUILD AND WANT TO UPGRADE TO CURRENT OCTOBER 2020 BUILD: I HIGHLY RECOMMEND FOLLOWING THIS SEPTEMBER UPDATE GUIDE FIRST (TO FIRST ENSURE YOU PROPERLY UPGRADE TO ANDROID 11, ELIMINATE ANY POTENTIAL ISSUES WITH BOOTLOOPING, MAKE SURE ALL MODULES ARE UP TO DATE AND COMPATIBLE, ETC). ONCE YOU ARE SUCCESSFULLY UPGRADED TO SEPTEMBER BUILD ANDROID 11, LET IT SETTLE AND PLAY AROUND FOR A WHILE BEFORE YOU FOLLOW THE OCTOBER UPDATE GUIDE.***
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 "FLAME" ONLY, NOT PIXEL 4 XL "CORAL"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR "RP1A.200720.009, Sep 2020"!
Magisk Canary v21.0 Patched Boot Image: https://www.androidfilehost.com/?fid=10763459528675562381
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=10763459528675562110
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=10763459528675562111
[SAFETYNET INFO]: Again, I'm not updating myself yet, so I'm not sure about this. I will update this info as others report back. On Android 10, using the MagiskHide Props Config module (or an alternate module created by Displax, though I prefer Didgeridoohan's module) and choosing option 2 - Force BASIC key attestation would force BASIC HW attestation and allow SafetyNet to pass again. This works perfectly for me, and I even run additional mods including EdXposed. I'm not sure if this works on Android 11, and I won't be able to confirm myself for a while. If anybody tries it, please let me know and I'll update this section. The module and info on using it can be found here: https://forum.xda-developers.com/ap...just search for it in the Magisk Manager app.
READ THIS ENTIRE POST BEFORE PROCEEDING!
ADDITIONAL PRELIMINARY STEPS COMPARED TO PREVIOUS MONTHS - DO NOT SKIP!!!!:
A. Make sure all of your Magisk / EdXposed modules are updated for compatibility with R. For example:
* Magisk Module: Riru (Riru - Core) v21.3
* Magisk Module / EdXposed version: EdXposed v.0.5.0.6-android_r (4561) [this is a Canary build]
B. Recommend disabling any Magisk and/or Xposed modules that have not been tested with Android R.
C. Install latest Magisk Manager build: https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.2/MagiskManager-v8.0.2.apk
D. Regular reboot the phone to make sure updates are applied before proceeding with the rest of the update process.
---------------------------
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "10.0.0 (QQ3A.200805.001, Aug 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
flame-qq3a.200805.001-factory-dtbo.img: https://www.androidfilehost.com/?fid=8889791610682911608
flame-qq3a.200805.001-factory-boot.img: https://www.androidfilehost.com/?fid=8889791610682911606
September 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-rp1a.200720.009-6dde3195.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot flame-qq3a.200805.001-factory-boot.img
3. fastboot flash dtbo flame-qq3a.200805.001-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload flame-ota-rp1a.200720.009-6dde3195.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot flame-rp1a.200720.009-magisk_patched-21.0.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
---------------------------
ADDITIONAL NOTES FROM @sidhaarthm, WHO TESTED FOR ME - THERE'S SOME GOOD INFO HERE TO HELP PREP YOU BEFORE UPDATING YOUR PHONE (NOTE, THIS WAS DONE BEFORE MAGISK MANAGER 8.0.x BECAME STABLE, AND WAS FOR PIXEL 4 XL):
Okay, so I just successfully completed the steps and I'm booted into Android 11 without issues.
Here are my observations, notes and findings:
Pre-requisites:
- I installed the Canary Build of Magisk apk - it basically overwrote the existing installation of Magisk and worked straight away. I remained on the 'stable' update channel.
- I uninstalled all the Accent and Colour Mods from Tulsadiver as he is yet to update the mods for R11 (although he's confirmed its' possible and will publish it soon).
- I also deleted the AK3 Helper module from Magisk that gets flashed with Kirisakura Kernel since I was about to to flash the stock kernel anyway.
- I left the GPay SQlite Fix, Systemless Hosts, Busybox, V4A and AML Modules in Magisk enabled and as is.
Upgrade Notes:
- Followed your instructions to the T and the upgrade process was a breeze.
- I did extract the boot file from the factory ROM and patched it in Canary Magisk myself on my P4XL, but I chickened out at the last minute and flashed the boot file you had provided anyway. Reason being the flashed boot IMG I generated was 33,292 KB vs the one you had provided (and the ones I saw posted in other threads) were all 33,332 KB. So there was definitely some differences there and I just didn't want to risk it at that point.
- The phone got a bit hot during the upgrade process - around 40C+ but I suppose that's alright. Its' cooled down now and running okay.
- I did not flash any Kernel yet since I am waiting for the next official Kirisakura Kernel release for R11.
Findings:
- My P4XL booted first time, no bootloops etc - finalised the upgrade in a couple of minutes and everything thereafter seems smooth as butter.
- GPay works perfect without any tinkering (that's a big plus!)
- Device is rooted and all Root apps (AdAway, TiB etc), all work as normal. Camera, WiFi, Bluetooth, everything works, no issues whatsoever.
- Face Unlock works as normal and so do all the apps that use the biometric API to unlock (banking apps etc).
- SafetyNet fails on ctsProfile (evalType Hardware) but it was the same before upgrading to R11, so not surprised.
- Viper FX doesn't work post upgrading to R11 - that's expected and people have already reported the same 'failed at patching system' error on the main thread. Hopefully we get an upgrade at some point. Really gutted about this one as I love V4A!
Click to expand...
Click to collapse
Big thanks to @sidhaarthm for being an awesome and detailed tester!
-------------------
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Coming from an earlier build than August 2020?
Download the September 2020 Full Factory Image .zip file and extract it. BEFORE RUNNING THE FLASH-ALL BATCH / SHELL FILE, EDIT THE FILE AND REMOVE THE "-w" FLAG FROM THE LAST FASTBOOT LINE. If you fail to remove -w, your phone will be wiped when it reaches this step. After flashing the full factory image, your phone will automatically reboot into O/S. From here, reboot back into bootloader, and flash the new Magisk patched boot image.
Since this is a major jump to a new version of Android, I don't want to recommend this yet until someone tests it. If anybody tries this way successfully, please let me know so we can update this part. Thanks!
Link to October 2020 update guide: https://forum.xda-developers.com/pixel-4/how-to/update-root-guide-oct-2020-rp1a-201005-t4175957
P.S.: Yes, I know this is very late to post last month's update, but life has been super busy for me, my wife, and the "new" member of our family <3 <3 <3. Plus, the Pixel 4 is not my phone but my wife's phone, and on top of that I haven't updated either of us to Android 11 yet. I really wanted to make sure I wasn't leading everyone who follows my guides into bootloop / bricking hell, so along with the help of a great tester and an abundance of caution, I only released the September guide for the Pixel 4 XL. Then I just never got around to doing the same for the Pixel 4. Whoops, my bad. Anyway, there's some great news brewing on the GravityBox scene, and hopefully I'll be updating our phones in the near future and I can get back on top of these guides without worrying that there may be any issues that I can't help out with, not having performed the upgrades myself.
Anyway, enjoy! And please let us know if you have any issues.
i5lee8bit said:
Link to October 2020 update guide: https://forum.xda-developers.com/pixel-4/how-to/update-root-guide-oct-2020-rp1a-201005-t4175957
P.S.: Yes, I know this is very late to post last month's update, but life has been super busy for me, my wife, and the "new" member of our family <3 <3 <3. Plus, the Pixel 4 is not my phone but my wife's phone, and on top of that I haven't updated either of us to Android 11 yet. I really wanted to make sure I wasn't leading everyone who follows my guides into bootloop / bricking hell, so along with the help of a great tester and an abundance of caution, I only released the September guide for the Pixel 4 XL. Then I just never got around to doing the same for the Pixel 4. Whoops, my bad. Anyway, there's some great news brewing on the GravityBox scene, and hopefully I'll be updating our phones in the near future and I can get back on top of these guides without worrying that there may be any issues that I can't help out with, not having performed the upgrades myself.
Anyway, enjoy! And please let us know if you have any issues.
Click to expand...
Click to collapse
thanks mate ive been waiting for this!! i did not feel like accidentally bricking or doing factory clean/. i followed the guide exactly and i updated all magisk modules to latest versions available and downloaded latest xposed canary yahfa. everything working buttery smooth with no hic cups at all. thank you for continuing to make thes guides :good::good::good:
also happy to report the magiskprophide module seems to be working for me and i pass safetynet! i will also take your advice and wait a bit before ota ing to october build. thanks again mate!
strange issue after updating...
i5lee8bit said:
Link to October 2020 update guide: https://forum.xda-developers.com/pixel-4/how-to/update-root-guide-oct-2020-rp1a-201005-t4175957
P.S.: Yes, I know this is very late to post last month's update, but life has been super busy for me, my wife, and the "new" member of our family <3 <3 <3. Plus, the Pixel 4 is not my phone but my wife's phone, and on top of that I haven't updated either of us to Android 11 yet. I really wanted to make sure I wasn't leading everyone who follows my guides into bootloop / bricking hell, so along with the help of a great tester and an abundance of caution, I only released the September guide for the Pixel 4 XL. Then I just never got around to doing the same for the Pixel 4. Whoops, my bad. Anyway, there's some great news brewing on the GravityBox scene, and hopefully I'll be updating our phones in the near future and I can get back on top of these guides without worrying that there may be any issues that I can't help out with, not having performed the upgrades myself.
Anyway, enjoy! And please let us know if you have any issues.
Click to expand...
Click to collapse
Thanks again! I do have a strange issue after updating that hasn't happened before and I can't seem to track down. Updated per instructions, same as I do pretty much every month, however this time (I use the 3 button home buttons) my home and task button don't work. They flash to indicated that I have pressed them, but no luck. Also noticed that dark theme is not holding after reboot... No issues popped up during install. Tried process a second time, again no issue, same deal. Also tried booting into safe mode and the issue is in safe mode as well...anything else to try before wipe and reset? I don't believe its related to this process, just hoping someone has any ideas or experienced this after the latest update...I just can't seem to find anyone having the same issue...
JakeKane08 said:
Thanks again! I do have a strange issue after updating that hasn't happened before and I can't seem to track down. Updated per instructions, same as I do pretty much every month,
1) however this time (I use the 3 button home buttons) my home and task button don't work. They flash to indicated that I have pressed them, but no luck.
2)Also noticed that dark theme is not holding after reboot...
3) No issues popped up during install. Tried process a second time, again no issue, same deal. Also tried booting into safe mode and the issue is in safe mode as well...anything else to try before wipe and reset? I don't believe its related to this process, just hoping someone has any ideas or experienced this after the latest update...I just can't seem to find anyone having the same issue...
Click to expand...
Click to collapse
1) We still haven't updated to Android 11, so unfortunately I'm not sure if I can be of much help. Actually, I hate gesture navigation and plan to use 3-button myself, so hopefully this doesn't happen to us, lol. I would start with something simple and quick - try to toggle 3-button navigation off (system, settings, navigation option or wherever it is), then back on. Maybe try rebooting in between? Then of course see if there are any modules (Magisk or Xposed) that may be messing with the setting. I would think GravityBox, but it isn't compatible with Android 11 yet... If you have EdXposed, try disabling the module to disable Xposed and see if it still happens. If that still doesn't work, perhaps try booting into Magisk core-only mode, or just flash the stock boot and dtbo images (for the current month you're on) for testing to see if it works, then flash the magisk-patched boot image again afterwards to re-root. Maybe booting non-rooted / all modules disabled will easily tell you if the problem is an uncooperative module.
2) Actually, I've had this issue since as long as I can remember in owning the device (well, on my P4XL, and also happens on my wife's P4). We both have the setting for auto dark mode (morning / evening auto setting). We're still both on Android 10 and it does the same thing. If it's on dark mode and the phone is rebooted, it boots back into light mode. We would have to toggle it back manually. However, I do believe it does automatically switch to dark theme on the next scheduled time/day. Yeah, it's been like that for literally as long as I can remember, unfortunately. Kinda annoying but meh, whatever.
I'm also not sure what happens if you follow the guide twice, only because you would already be on the current month, then flashing the previous month's boot/dtbo images, and OTA'ing to what you're already on. I doubt it would permanently break anything though, but maybe try flashing your current build's dtbo image just to be safe? Not sure if the OTA directly updates the dtbo partition. For example:
Round 1: You follow my guide for September update. You are currently on August build. You are flashing the stock August boot / dtbo images to revert recovery to stock for your current patch level, then flashing the September OTA. You are now on all September images. You then flash the Magisk patched September boot image to re-root.
Round 2: You follow the guide again. You are already on September build, yet you're flashing the August boot / dtbo images to revert recovery to stock - but for a month back. See what I'm saying? But at least you said you got no errors. I would assume the 2nd round of following the guide didn't hurt anything, but this is also why I say maybe try flashing the stock dtbo image for the current month you're on.
Good luck! Let me know how it turns out. Still waiting to update, and having working 3 button navigation is a MUST for both my wife and I! Not trying to have an Apple Pixel here.
i5lee8bit said:
1) We still haven't updated to Android 11, so unfortunately I'm not sure if I can be of much help. Actually, I hate gesture navigation and plan to use 3-button myself, so hopefully this doesn't happen to us, lol. I would start with something simple and quick - try to toggle 3-button navigation off (system, settings, navigation option or wherever it is), then back on. Maybe try rebooting in between? Then of course see if there are any modules (Magisk or Xposed) that may be messing with the setting. I would think GravityBox, but it isn't compatible with Android 11 yet... If you have EdXposed, try disabling the module to disable Xposed and see if it still happens. If that still doesn't work, perhaps try booting into Magisk core-only mode, or just flash the stock boot and dtbo images (for the current month you're on) for testing to see if it works, then flash the magisk-patched boot image again afterwards to re-root. Maybe booting non-rooted / all modules disabled will easily tell you if the problem is an uncooperative module.
2) Actually, I've had this issue since as long as I can remember in owning the device (well, on my P4XL, and also happens on my wife's P4). We both have the setting for auto dark mode (morning / evening auto setting). We're still both on Android 10 and it does the same thing. If it's on dark mode and the phone is rebooted, it boots back into light mode. We would have to toggle it back manually. However, I do believe it does automatically switch to dark theme on the next scheduled time/day. Yeah, it's been like that for literally as long as I can remember, unfortunately. Kinda annoying but meh, whatever.
I'm also not sure what happens if you follow the guide twice, only because you would already be on the current month, then flashing the previous month's boot/dtbo images, and OTA'ing to what you're already on. I doubt it would permanently break anything though, but maybe try flashing your current build's dtbo image just to be safe? Not sure if the OTA directly updates the dtbo partition. For example:
Round 1: You follow my guide for September update. You are currently on August build. You are flashing the stock August boot / dtbo images to revert recovery to stock for your current patch level, then flashing the September OTA. You are now on all September images. You then flash the Magisk patched September boot image to re-root.
Round 2: You follow the guide again. You are already on September build, yet you're flashing the August boot / dtbo images to revert recovery to stock - but for a month back. See what I'm saying? But at least you said you got no errors. I would assume the 2nd round of following the guide didn't hurt anything, but this is also why I say maybe try flashing the stock dtbo image for the current month you're on.
Good luck! Let me know how it turns out. Still waiting to update, and having working 3 button navigation is a MUST for both my wife and I! Not trying to have an Apple Pixel here.
Click to expand...
Click to collapse
Sorry for the late reply and confusing with versions I was actually working with September images the entire time. I hadn't actually flashed back August images. After I installed the September OTA and it didn't work, I applied the entire September image to see if something in the OTA broke. No luck there either. I ended up backing everything up and performing a system wipe/recovery. Happy to report that all is working and actually working much better than before. Device is quite snappy and battery has improved, I find that at the end of the day I have about 10-15% more battery than I had before. I'm sure that this is probably due to less bloat and/or something was definitely not working right on the system.