Some of you may remember that there is a way to push su binary from CyanogenMod builds to commercial CM 11S builds & thus enable built-in Superuser. The original method is intended for OnePlus One but can be successfully applied on YU Yureka as well.
Well, CM 12S is everywhere now; so I extend the idea. Procedure is fairly simple - compatible su binary is taken from @varun.chitre15's CM 12.1 build & I have made a flashable zip on top of it. Flash using TWRP on top of a stock OS is recommended.
You may then flash boot-debuggable kernel from here.
Download: https://www.androidfilehost.com/?fid=23991606952604745
Please post feedback.
Proof:
YU Forums thread: http://forums.yuplaygod.com/threads/cm-12s-enable-built-in-superuser.12778/
Even after doing this can I update my phone via OTA updates? Without losing it!
Sent from my GT-I8552 using XDA Premium 4 mobile app
@Tuneer
Yes, you can get & apply OTA but you'll lose root access.
I flash the script i.e. only the .zip file, but nothing works on stock cm-12.0-YNG1TAS1K0-tomato-signed-fastboot.zip
It Boot debugging kernel compulsory to flash?
arvindgr said:
It Boot debugging kernel compulsory to flash?
Click to expand...
Click to collapse
Yes, it is.
Titokhan said:
Yes, it is.
Click to expand...
Click to collapse
I thought to use this Root access method, to prevent OTA installation failure which happens due to /system modification that's done by SuperSU. If this root method, also requires sys partition mod, then this also would render to OTA failures. Am I correct?
Sent from my Nexus 4 using XDA Free mobile app
@arvindgr
Every rooting method for this model requires to remount /system in RW mode to push su binary. So yes, incremental OTAs should fail in future but you can always opt for signed zips for manual upgrade.
Titokhan said:
@arvindgr
Every rooting method for this model requires to remount /system in RW mode to push su binary. So yes, incremental OTAs should fail in future but you can always opt for signed zips for manual upgrade.
Click to expand...
Click to collapse
By Signed zips, do you say those manual OTA files, we can flash from Stock recovery?
Also, this link u linked for signed zips directs me to login at https://www.androidfilehost.com/user/?w=login
@arvindgr
Kinda; I'm talking about these, not the incremental OTAs.
**Link corrected.
Oh, we can flash factory images i.e signed .zip's without data wipe command -w so that, we can update to latest. Now I get what u r telling..
even after successfully installing zip i m not able to see any option in developer options of superuseraccess, and neither i m able to get that popup...pls look into it
Related
So guys thanks to the lovely people here on XDA we have the incremental OTA captured!
its NOT the full ROM but is rather a patch to allow you to update to latest 4.4.3
Since this is incremental patch you will need to be on stock/minimally modified Stock KOT49H 4.4.2 ROM, most importantly you will have to be on original kernel (boot.img)...
best would be to use this procedure:
[IMP][ZU_GPe][How-To] Restore to original Google Play Edition firmware!
to get back to stock 4.4.2 (but you may lose your app data)
If you want an in-place upgrade and if you are using any of my kernel (recovery kernels or DooMKernel) then you will have to revert to pure stock kernel..
unfortunately you wont be able to flash the original KOT49H kernel via fastboot (considering that you might have unlocked bootloader)...
i am attaching below the original KOT49H as a recovery flashable zip:
ZU_GPe-DooMLoRD-Stock_KOT49H_kernel
flash it using CWM recovery and the kernel on your GPE device will be replaced with original kernel
now reboot into bootloader
Code:
adb reboot bootloader
select recovery and enter it...
select ADB method and flash the incremental OTA using the command:
Code:
adb sideload <NAME-OF-OTA-FILE>
it will take a while but once its done reboot device and enjoy latest KitKat 4.4.3
regards,
DooMLoRD
once i enter recovery and use the adb sideload command i get the following error:
device not found
vivalamoza said:
once i enter recovery and use the adb sideload command i get the following error:
device not found
Click to expand...
Click to collapse
you have to enable recovery menu (press POWER + VOLUME DOWN for a second or so when u see the "dead android robot screen")...
then select flash via adb (1st option in the recovery)
Can we follow this procedure if using the ported GPE ROM in a C6833? Is there anything GPE-specific in the update ZIP that could brick a non-GPE device?
Thanks!
dbolivar said:
Can we follow this procedure if using the ported GPE ROM in a C6833? Is there anything GPE-specific in the update ZIP that could brick a non-GPE device?
Thanks!
Click to expand...
Click to collapse
PLEASE DO NOT TOUCH THE INCREMENTAL OTA ZIP ON NON-GPE DEVICE!
bootloader/modem and lots of other things are getting patched!
wait for the fill flash zip and then port that...
What happens if I click restart and install that notification won't go away
Sent from my C6806_GPe using XDA Premium 4 mobile app
Okay restoring from the full 4.4.2 OTA then sideloading of the 4.4.3 OTA worked.
Definitely not as using fastboot....
So... Once I flash the 4.4.3 Update (Thanks btw); do I reflash your Kernel?
If not, how do I re-root?
Thanks,
Flipper
DooMLoRD said:
So guys thanks to the lovely people here on XDA we have the incremental OTA captured!
its NOT the full ROM but is rather a patch to allow you to update to latest 4.4.3
Since this is incremental patch you will need to be on stock/minimally modified Stock KOT49H 4.4.2 ROM, most importantly you will have to be on original kernel (boot.img)...
best would be to use this procedure:
[IMP][ZU_GPe][How-To] Restore to original Google Play Edition firmware!
to get back to stock 4.4.2 (but you may lose your app data)
If you want an in-place upgrade and if you are using any of my kernel (recovery kernels or DooMKernel) then you will have to revert to pure stock kernel..
unfortunately you wont be able to flash the original KOT49H kernel via fastboot (considering that you might have unlocked bootloader)...
i am attaching below the original KOT49H as a recovery flashable zip:
ZU_GPe-DooMLoRD-Stock_KOT49H_kernel
flash it using CWM recovery and the kernel on your GPE device will be replaced with original kernel
now reboot into bootloader
Code:
adb reboot bootloader
select recovery and enter it...
select ADB method and flash the incremental OTA using the command:
Code:
adb sideload <NAME-OF-OTA-FILE>
it will take a while but once its done reboot device and enjoy latest KitKat 4.4.3
regards,
DooMLoRD
Click to expand...
Click to collapse
flipperg said:
So... Once I flash the 4.4.3 Update (Thanks btw); do I reflash your Kernel?
Thanks,
Flipper
Click to expand...
Click to collapse
The kernel provided in the first post is for 4.4.2
If you flashed the 4.4.3 update properly then you you are good to go!
Though if you want custom recoveries just check the advanced stock kernel posted in my other thread...
Sent from my D6503 using XDA Free mobile app
Awesome!
:laugh:
That's what I needed - thank you, I did exactly that and then re-rooted from CWM via your Advanced Stock Kernel. I'm back.
Thank you,
Flipper
DooMLoRD said:
The kernel provided in the first post is for 4.4.2
If you flashed the 4.4.3 update properly then you you are good to go!
Though if you want custom recoveries just check the advanced stock kernel posted in my other thread...
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
---------- Post added at 02:26 AM ---------- Previous post was at 02:18 AM ----------
In case this helps others - I always change my DPI via ROM Toolbox build.prop editor and also install Xposed Framework...
Undo both (400 DPI, and Uninstall Framework) before you run the update or it will fail.
Flipper
flipperg said:
:laugh:
That's what I needed - thank you, I did exactly that and then re-rooted from CWM via your Advanced Stock Kernel. I'm back.
Thank you,
Flipper
Click to expand...
Click to collapse
DooMLoRD said:
you have to enable recovery menu (press POWER + VOLUME DOWN for a second or so when u see the "dead android robot screen")...
then select flash via adb (1st option in the recovery)
Click to expand...
Click to collapse
Thanks
Did that and now I have a message on my phone saying:
Now send the package you want to apply to the device with "adb sideload <filename>...
The thing is when I send the file via adb I get the error: device not found
I check my device manager and I found a yellow exclamation mark next to the phone, does the phone need a different driver to use the sideload command?
vivalamoza said:
Thanks
Did that and now I have a message on my phone saying:
Now send the package you want to apply to the device with "adb sideload <filename>...
The thing is when I send the file via adb I get the error: device not found
I check my device manager and I found a yellow exclamation mark next to the phone, does the phone need a different driver to use the sideload command?
Click to expand...
Click to collapse
A driver is probably not installed correctly. Re-install it and try again. If that doesn't work:
- Boot your phone
- Go to developer settings and enable USB debugging, and authorize ADB (it'll pop up and ask you on your phone)
- Open cmd on your computer and type "adb devices". Your device is a string of characters and numbers, like: "4JKF45234F" etc.
- If your device is found, try sideloading it now, by typing "adb sideload [file path]" and wait for it to flash it.
vivalamoza said:
Thanks
Did that and now I have a message on my phone saying:
Now send the package you want to apply to the device with "adb sideload <filename>...
The thing is when I send the file via adb I get the error: device not found
I check my device manager and I found a yellow exclamation mark next to the phone, does the phone need a different driver to use the sideload command?
Click to expand...
Click to collapse
I had this issue and drivers needed to be installed. Right click on device with exclamation, tab over to drivers, then select update drivers and "choose browse my computer", find the Sony fastboot and adb drivers from flashtool folder and install them. If you are on win8 or 8.1 you will need to disable signature verification. I assume somehow flashtool is able to use the drivers without them actually being installed?
@vivalamoza another option is to copy update to SD card and flash it from there using stock recovery.
Exactly that's a question I had, can't I just choose apply update from SD instead and browse the file location on my phone.
Sent from my C6806_GPe using XDA Premium 4 mobile app
vivalamoza said:
Exactly that's a question I had, can't I just choose apply update from SD instead and browse the file location on my phone.
Sent from my C6806_GPe using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did it that way by copying update to SD , flashing the CWM flashable stock recovery, then following the return to stock guide. Except at the end I chose apply update from SD instead of adb sideload. If you have used xposed to edit framework I would use the uninstall option inside xposed installer app. Also if any system apps have been deleted it will error out and not install.
@DooMLoRD do you have any idea what broke our cameras after update? Is it possible to return to 4.4.2 using your restore method with the full ota?
adfurgerson said:
@DooMLoRD do you have any idea what broke our cameras after update? Is it possible to return to 4.4.2 using your restore method with the full ota?
Click to expand...
Click to collapse
Full OTA of 4.4.2 won't work... Give me a few days I am out of town, will work on a fix soon!
Sent from my D6503 using XDA Free mobile app
DooMLoRD said:
Full OTA of 4.4.2 won't work... Give me a few days I am out of town, will work on a fix soon!
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks!
I flashed 4.4.3 using stock recovery and I'm unrooted. I'm having no camera problems, everything seems to be working fine. I'm using Google camera.
Sent from my C6806_GPe using XDA Premium 4 mobile app
vivalamoza said:
I flashed 4.4.3 using stock recovery and I'm unrooted. I'm having no camera problems, everything seems to be working fine. I'm using Google camera.
Sent from my C6806_GPe using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odd. My camera is completely broken.
Sent from my BN NookHD+ using Tapatalk
I have uploaded the latest androd 6.0.1 MMB29K.
I have twrp installed - the latest I believe.
super su - 2.46 pro
I installed the ElementX kernel - can't remember witch page I followed to root my nexus 9. but it suggested this.
Now I can't set a pin for my sudoers
tried uninstalling and reinstalling no luck.
I have ex kernel manager and it says there is a new version available, but I need superSU 2.61 - witch means the new beta version.
Looking at the thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
looks like I have refrash a stock boot
"
If you are coming from any SuperSU install in /system, you must re-flash the stock system partition contents prior to installing this.
"
how do I do this ?
What does the new kernel give me ?
Any idea on why my supersu doesn't let me use pin codes ?
KeyzerSuze said:
I have uploaded the latest androd 6.0.1 MMB29K.
I have twrp installed - the latest I believe.
looks like I have reflash a stock boot
"
If you are coming from any SuperSU install in /system, you must re-flash the stock system partition contents prior to installing this.
"
how do I do this ?
What does the new kernel give me ?
Any idea on why my supersu doesn't let me use pin codes ?
Click to expand...
Click to collapse
Latest TWRP for Nexus 9 is twrp-2.8.7.1-flounder
Get the latest factory image and unzip the contents a few times then use fastboot to flash both boot.img and system.img.
From TWRP Flash SuperSU-v2.62-3 first and then the latest ElemetalX kernel (if you want it, not needed for root).
Never used pin codes with supersu, so don't know about that.
corkiejp said:
Latest TWRP for Nexus 9 is twrp-2.8.7.1-flounder
Get the latest factory image and unzip the contents a few times then use fastboot to flash both boot.img and system.img.
The latest SuperSU-v2.62-3
From TWRP Flash that first and then the latest ElemetalX kernel (if you want it, not needed for root).
Never used pin codes with supersu, so don't know about that.
Click to expand...
Click to collapse
Flashing vendor.img is a good idea as well, just to make sure everything is synced up.
I'm I going to have to reinstall all my apps again ?
Sent from my Nexus 6P using Tapatalk
KeyzerSuze said:
I'm I going to have to reinstall all my apps again ?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Flashing just boot.img, system.img and vendor.img, will not wipe data.
And leaves data untouched, so won't need to reinstall apps again. Just don't flash the full factory image.
(Note: Flashing the full factory image can also be done without wiping data)
Thanks did it and all good.
Sent from my Nexus 6P using Tapatalk
Read before continue:
http://forums.yuplaygod.com/threads/15124/
http://forum.xda-developers.com/showpost.php?p=63197935
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Requirements:
Completely stock, untouched device (OnePlus One).
Unlocked bootloader.
Rooted boot images:
cm-12.1-YOG7DAS2K1-bacon-boot-debuggable-rooted.img
Usage:
Download the rooted boot image that matches with your installed build.
Flash using fastboot:
Code:
fastboot flash boot XXX.img
Install the SuperUser manager app: https://play.google.com/store/apps/details?id=me.phh.superuser
Profit!
To take incremental OTA:
Download the stock boot image that matches with your installed build. Either extract from signed fastboot flashable zips or get from this thread.
Flash using fastboot:
Code:
fastboot flash boot XXX.img
You should be able to take & install the OTA, if /system isn't tampered previously.
Note:
The rooted boot images are based on official boot-debuggable images & super-bootimg by @phhusson.
The whole thing is in alpha stage & still WIP, so expect bugs.
Not all apps are compatible with systemless root approach, so root access mayn't be visible to them.
Please provide detailed feedback to me, @phhusson & the concerned app developer.
Reserved for future v1.
Reserved for future v2.
I read the second and third links, but had to sign up to get the first (not with it at this time) and I'm kinda confused. What exactly is wrong with the "old way" of rooting? Is it just for things like Android pay to work or is there other benefits?
Sent from my LG-D800 using Tapatalk
@FlashHappy78
In a nutshell, traditional rooting method modifies the /system partition. As a consequence, subsequent OTAs will fail. In case of Cyanogen OS devices, it may be easier to grab the full signed zip later & update manually, but for others they need to re-flash the stock system.img to take the OTA.
In this new approach, only the boot image is modified but /system is untouched. Thus any event/application that verifies the integrity of /system partition (like OTA, Android Pay etc.) is ready to be executed on top of the rooted device without any hitch.
If OTA contains an updated boot image, then user need to re-flash the stock boot image first which is considerably easy to re-flash than the whole system.img.
I've always been under the assumption that oem OTA updates usually break root anyways, plus patch whatever exploits were used to gain root (especially from OEM's like Samsung and LG), so because of that, I never take OTA updates unless they come from custom ROM devs.
Anyways, thanks for the clarification. I don't use android pay and I use only custom ROMs, so this probably isn't for me then. Thanks again mate.
Sent from my LG-D800 using Tapatalk
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
poulopoulosa said:
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
Click to expand...
Click to collapse
Flash supersu at least the stable 2.64
poulopoulosa said:
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
Click to expand...
Click to collapse
As suggested by @hellcat50, I'll not provide any more update on this as newer SuperSU can patch the boot image on the fly.
This is a stock boot.img I use where I edited ramdisk and sepolicy for regular root. I also changed force encryption to encryptable and permissive Enforcing
I will continue to post new boot.img each update here.
Downloads
NBF26f big thanks for the update was done by @googy_anas
https://drive.google.com/file/d/0B4yuQy7Zn1WSdTFCMEtRbXpSREE/view?usp=drivesdk
NBD91K
https://www.androidfilehost.com/?fid=529152257862678470
NRD90U
https://drive.google.com/file/d/0B6DDdWOgUhVVMFpGTFlTQWVQOW8/view
@holla420 good looks on doing boot.img again.
NPD90G
https://www.androidfilehost.com/?fid=24591023225178833
big shout out to my homie @holla420 for knocking out this boot.img for everyone.
NPD56N
https://www.androidfilehost.com/?fid=24572369242686570
big shout out to my homie @holla420 for knocking out this boot.img for everyone
NPD35K
https://drive.google.com/file/d/0B4yuQy7Zn1WSQmdfZ3dNMW02Z3c/view?usp=drivesdk
Decrypted boot.IMG and no DM check for NPC91K
https://drive.google.com/file/d/0B4yuQy7Zn1WSVVJSbWpGaU1sTlU/view?usp=drivesdk
Decrypted boot.IMG for Android N build NPC56W
https://drive.google.com/file/d/0B4yuQy7Zn1WSZm11VE1KZmx3RG8/view?usp=sharing
Decrypted boot.IMG for Android N build inital release
https://drive.google.com/file/d/0B4VEhClrJEWpekpneFdUWkhBX1E/view
Big thanks to my good friend and co-dev @toknitup420 don't forget to thank him you see him around
works perfect. Good looks @Tigerstown.
Sent from my Nexus 6P using Tapatalk
Tigerstown said:
This is a stock boot.img I use where I edited ramdisk and sepolicy for regular root. I also changed force encryption to encryptable.
Download https://drive.google.com/file/d/0B4yuQy7Zn1WSTnE4bmxNZXRMdGs/view?usp=docslist_api
Click to expand...
Click to collapse
Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?
floepie said:
Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?
Click to expand...
Click to collapse
what's the point of systemless root is what you should be asking yourself
Tigerstown said:
what's the point of systemless root is what you should be asking yourself
Click to expand...
Click to collapse
Because you don't have to rely on the generosity of someone modifying the boot image to accommodate the older method, thereby requiring only 1 recovery flash?
floepie said:
Because you don't have to rely on the generosity of someone modifying the boot image to accommodate the older method, thereby requiring only 1 recovery flash?
Click to expand...
Click to collapse
Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.
Sent from my Nexus 6P using Tapatalk
Huh? No, really, I think I'm too old to be "trolling". Just curious to know if there are any potential advantages of the traditional method - not from a selfish perspective, but more out a, well, curiosity. Can we just keep this to the level of a civil "discussion"?
Is this still Enforcing? Is it possible to get a stock or close to stock kernel that is Permissive for a project I'm working on? I just need a boot.img. Thanks!
toknitup420 said:
Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I agree and thank you. as I am traditional root user. thank you for the boot img
Sent from my Nexus 9
floepie said:
Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?
Click to expand...
Click to collapse
Why do you guys attack the above person for asking "explain like I am 5, why does anyone want this?"
Tigerstown said:
what's the point of systemless root is what you should be asking yourself
Click to expand...
Click to collapse
toknitup420 said:
Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Would it have been better if the question were phrased: "Why do you need a separate modified boot.img, when you can force system root using any SuperSU above 2.65? It will still patch the boot.img and disable "forceencrypt"?
So, I'll ask....why do you need a modified boot.img and SuperSU, if SuperSU 2.6x will *automatically modify the boot.img for you and can be installed as system or system-less via terminal commands? Is it because you are using the stock rom and SuperSU will not install as system root due to lack of space in /system?
Edit: *automatically modify boot.img when installing as system-less, OR can be forced to install as system root via terminal commands?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Why do you guys attack the above person for asking "explain like I am 5, why does anyone want this?"
Would it have been better if the question were phrased: "Why do you need a separate modified boot.img, when you can force system root using any SuperSU above 2.65? It will still patch the boot.img and disable "forceencrypt"?
So, I'll ask....why do you need a modified boot.img and SuperSU, if SuperSU 2.6x will *automatically modify the boot.img for you and can be installed as system or system-less via terminal commands? Is it because you are using the stock rom and SuperSU will not install as system root due to lack of space in /system?
Edit: *automatically modify boot.img when installing as system-less, OR can be forced to install as system root via terminal commands?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Why use the terminal cmd? I make this for myself. I posted for people that want it. If you don't want it or need it that is cool. I flash this when flashing factory imgs and I can reboot still decrypted then I boot to twrp flash SuperSU zip and I'm done. I'm not a fan of systemless root. Do you know why it was even created??
guitardedhero said:
Is this still Enforcing? Is it possible to get a stock or close to stock kernel that is Permissive for a project I'm working on? I just need a boot.img. Thanks!
Click to expand...
Click to collapse
Yes it's still Enforcing
floepie said:
Because you don't have to rely on the generosity of someone modifying the boot image to accommodate the older method, thereby requiring only 1 recovery flash?
Click to expand...
Click to collapse
This boot.img isn't flashed in recovery so still one flash. This is fastboot when your updating factory imgs.
freddienuxx said:
I agree and thank you. as I am traditional root user. thank you for the boot img
Sent from my Nexus 9
Click to expand...
Click to collapse
no problem I do it for every update. I just decide to start posting them for people like yourself. ??
Hi,
Should I be using this file to update from MMB29P to MMB29Q and still maintain root?
I must flash the file through TWRP?
Touchmetallic said:
Hi,
Should I be using this file to update from MMB29P to MMB29Q and still maintain root?
I must flash the file through TWRP?
Click to expand...
Click to collapse
you can use this as boot.img to update yes. But keep root no. You just need to flash factory imgs with this boot.img then boot up and boot to twrp flash SuperSU 2.67 and you will be updated with regular root.
Flash this boot.img thru fastboot just like you do factory imgs not via recovery.
Tigerstown said:
you can use this as boot.img to update yes. But keep root no. You just need to flash factory imgs with this boot.img then boot up and boot to twrp flash SuperSU 2.67 and you will be updated with regular root.
Flash this boot.img thru fastboot just like you do factory imgs not via recovery.
Click to expand...
Click to collapse
Thanks for your reply.
Sorry if this is a redundant question as I'm not an expert, but is there an easy way to update without losing root?
Touchmetallic said:
Thanks for your reply.
Sorry if this is a redundant question as I'm not an expert, but is there an easy way to update without losing root?
Click to expand...
Click to collapse
No need to be sorry it's all good... Unfortunately no. You can just flash SuperSU zip in twrp after updating to new factory imgs with this modified boot.img and your 100% rooted again.
Touchmetallic said:
Thanks for your reply.
Sorry if this is a redundant question as I'm not an expert, but is there an easy way to update without losing root?
Click to expand...
Click to collapse
I recommend not flashing the userdata.img as that will wipe your internal storage sense it's still 6.0.+ FYI but that's up to you and don't flash the recovery.img either in factory imgs cause that will replace your twrp with stock recovery
Tigerstown said:
Why use the terminal cmd? I make this for myself. I posted for people that want it. If you don't want it or need it that is cool. I flash this when flashing factory imgs and I can reboot still decrypted then I boot to twrp flash SuperSU zip and I'm done. I'm not a fan of systemless root. Do you know why it was even created??
Click to expand...
Click to collapse
Ahh I see. That makes sense given that you are decrypted. Appreciate that.
Having followed SuperSU threads since late November, seems like it was created to make accepting OTAs easier. That, or to work around the limits of Marshmallow and /system rom space. If not that, then no I don't.
Sent from my Nexus 5X using Tapatalk
I made this tutorial because i see no ZCX TWRP here..
In this TUTORIAL, we will update MIUI 7.2.24 to MIUI 7.3.2 using our beloved TWRP
Why this happened ?
You will fail to update OTA if :
1. You modified boot.img
2. You modified system's folder
3. You are using UNPATCHED TWRP
Getprop-Fingerprint's command in TWRP, will give you string :
Xiaomi/cm_land/land:6.0.1/MOB30M/e9c4629b61:eng/test-keys
Not your real Fingerprint.
If you unpack TWRP, you can see that string on default.prop
LETS BEGIN THIS TRICK
Requirements:
1. TWRP (Of Course)
2. OTA FLASHER by SILFOX
3. miui_HM3SGlobal_7.2.24_b21bbbf2e4_6.0.zip
4. miui-blockota-land_global-7.2.24-7.3.2-4b1c573f58-6.0.zip
Instructions :
1. Download all required Files
2. Install OTA FLASHER and open it.
3. Choose Flash OTA
4. Choose miui_HM3SGlobal_7.2.24_b21bbbf2e4_6.0.zip for Current MIUI ROM
5. Choose miui-blockota-land_global-7.2.24-7.3.2-4b1c573f58-6.0.zip for OTA
6. Choose START FLASH
7. Your device will goto TWRP, and do its magic
8. After finish, you can flash SuperSu or anything
9. After that, "Disable DM-Verify", and then Reboot...
Awesome love this Totally.
ok that got past the preliminary round, but now my recovery falsely reports that my system partition has unexpected contents, but i have a systemless root and was carefull not to mount that system partition.
by chance can we further edit the update-script to remove checks altogether?
also whats this patched twrp you speak of? does it skip this part by it self?
Great work. By the way can you create the patched twrp recovery like zcx recovery? It would be very helpful.
Thanks
xdarkmario said:
ok that got past the preliminary round, but now my recovery falsely reports that my system partition has unexpected contents, but i have a systemless root and was carefull not to mount that system partition.
by chance can we further edit the update-script to remove checks altogether?
also whats this patched twrp you speak of? does it skip this part by it self?
Click to expand...
Click to collapse
You can only remove getprop check.
If you patch twrp, you can skip editing updater-script
P€πtex4869 said:
Great work. By the way can you create the patched twrp recovery like zcx recovery? It would be very helpful.
Thanks
Click to expand...
Click to collapse
Sorry, i cant.
But i'm working to make Ota flasher.
SILF0X said:
Sorry, i cant.
But i'm working to make Ota flasher.
Click to expand...
Click to collapse
Ohk
P€πtex4869 said:
Ohk
Click to expand...
Click to collapse
UPDATED ...
Doesn't this defeat the purpose?
The point was to not have to download that huge 1.5gb ROM every and just direct flash the OTA. Can't I just select the OTA and flash?
Sent from my Redmi 3S using Tapatalk
Download modded MIUI updater app
xdarkmario said:
Doesn't this defeat the purpose?
The point was to not have to download that huge 1.5gb ROM every and just direct flash the OTA. Can't I just select the OTA and flash?
Sent from my Redmi 3S using Tapatalk
Click to expand...
Click to collapse
There's a separate modded MIUI updater app available for download incremental updates.
Kindly download that app and download the OTAs through it.
@SILF0X
Does it work on miui 9 global Redmi 3S?. Thanks.
Can i'm using in mido redmi note 4x ?