What are the steps to rooting my phone safely?
I'm on MIUI 12.5.7.
I've done a lot of research but I'd like to confirm on here before doing anything just in case, I can provide any other information needed, thanks!
You want confirmation ? Then list what are the steps and we will approve or disapprove.
Fytdyh said:
You want confirmation ? Then list what are the steps and we will approve or disapprove.
Click to expand...
Click to collapse
I'd like a definitive list of what to do lmao, I've seen lots of different ways to do it so there's confusion on what to do.
from what I can tell the basic steps are to unlock bootloader, flash custom recovery then flash magisk?
yes those are the basic steps. do go on. you said that you ve made a lot of "research" but so far i have not seen any. dont be lazy or you will hard brick your device.
Fytdyh said:
yes those are the basic steps. do go on. you said that you ve made a lot of "research" but so far i have not seen any. dont be lazy or you will hard brick your device.
Click to expand...
Click to collapse
Eh hard-bricks are not a big deal anymore.
As for rooting:
1)Unlock your bootloader using MiUnlock (or mtkclient if you are impatient)
This will wipe your data unless you are using mtkclient. (which to my surprise doesnt wipe data)
2)Disable Android Verified Boot (causes soft-brick if u dont)
Extract vbmeta.img from the ROM zip file then flash it using this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2)Install TWRP
MIUI 12.5 TWRP:https://sourceforge.net/projects/be...rp-3.5.2_11-0-UNOFFICIAL-begonia.img/download
3)Download Magisk, rename .apk to .zip then flash it.
That's it. Now you have a rooted phone.
Canny1913 said:
Eh hard-bricks are not a big deal anymore.
As for rooting:
1)Unlock your bootloader using MiUnlock (or mtkclient if you are impatient)
This will wipe your data unless you are using mtkclient. (which to my surprise doesnt wipe data)
2)Disable Android Verified Boot (causes soft-brick if u dont)
Extract vbmeta.img from the ROM zip file then flash it using this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2)Install TWRP
MIUI 12.5 TWRP:https://sourceforge.net/projects/be...rp-3.5.2_11-0-UNOFFICIAL-begonia.img/download
3)Download Magisk, rename .apk to .zip then flash it.
That's it. Now you have a rooted phone.
Click to expand...
Click to collapse
hihi, sorry for the late reply, I would've written out what I knew but this pretty much it, my main questions were which TWRP files to use and about MiUnlock, well now specifically mtkclient. Is it completely safe to use? I'd prefer not to wipe my files
Luxetrixx said:
hihi, sorry for the late reply, I would've written out what I knew but this pretty much it, my main questions were which TWRP files to use and about MiUnlock, well now specifically mtkclient. Is it completely safe to use? I'd prefer not to wipe my files
Click to expand...
Click to collapse
I've watched a few videos about it and some of them were formatted, some of them were not.
Try at your own risk.
When unlocked using mtkclient it may throw a dm-verity error or fastboot may refuse to work. Both of these are normal.
Related
I got the OTA update downloaded but could not install.Read somewhere if you have CWM ota update wont work.So i have downloaded the stock image for 4.0.2 and its in .tgz format
How can i upgrade to 4.0.2 using CWM or odin and not loose my data and setup.?
Please advice
Hussainally said:
I got the OTA update downloaded but could not install.Read somewhere if you have CWM ota update wont work.So i have downloaded the stock image for 4.0.2 and its in .tgz format
How can i upgrade to 4.0.2 using CWM or odin and not loose my data and setup.?
Please advice
Click to expand...
Click to collapse
Check out Chainfire's thread. He posted a no-wipe version flashable through Odin. Follow the instructions there and make sure you download the correct version for your phone (GSM/LTE)!
mbroeders said:
Check out Chainfire's thread. He posted a no-wipe version flashable through Odin. Follow the instructions there and make sure you download the correct version for your phone (GSM/LTE)!
Click to expand...
Click to collapse
hi thanks for your reply.His update you will not be updating to new bootloader am i right?
Hussainally said:
hi thanks for your reply.His update you will not be updating to new bootloader am i right?
Click to expand...
Click to collapse
Indeed, it won't touch your data, recovery or bootloader. They're all safe afaik
mbroeders said:
Indeed, it won't touch your data, recovery or bootloader. They're all safe afaik
Click to expand...
Click to collapse
thats the prob...4.0,2 has a new bootloader right?i want that.
ok what if i just want to install fresh clean stock 4.0.2...how do i do that?
Hussainally said:
thats the prob...4.0,2 has a new bootloader right?i want that.
ok what if i just want to install fresh clean stock 4.0.2...how do i do that?
Click to expand...
Click to collapse
If you want fresh clean stock then you can do two things:
1) on linux, extract the contents of the tgz package and use the sh script inside to flash.
2) since that's not possible on windows, you could use Chainfire's odin files first and next manually flash the bootloader and/or radioimage with fastboot. You can extract the bootloader and radio yourself from the tgz/tar package or look for them in the development section, someone posted them there.
mbroeders said:
If you want fresh clean stock then you can do two things:
1) on linux, extract the contents of the tgz package and use the sh script inside to flash.
2) since that's not possible on windows, you could use Chainfire's odin files first and next manually flash the bootloader and/or radioimage with fastboot. You can extract the bootloader and radio yourself from the tgz/tar package or look for them in the development section, someone posted them there.
Click to expand...
Click to collapse
You can flash it in windows using fastboot, you don't need to use odin for anything:
Extract the factory images
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot update image-yakju-icl53f.zip
Thanks everyone...will give it a go.....Cheers
krohnjw said:
You can flash it in windows using fastboot, you don't need to use odin for anything:
Extract the factory images
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot update image-yakju-icl53f.zip
Click to expand...
Click to collapse
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
mbroeders said:
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
Click to expand...
Click to collapse
What I posted does not wipe. There's little reason to use Odin. Using Odin you *can* easily brick your device (Ask all of the folks in the Nexus S forums that used Odin to flash the wrong package for their device).
fastboot update image-yakju-icl53f.zip <-- This does not wipe
fastboot -w update image-yakju-icl53f.zip <-- This wipes (-w wipes)
mbroeders said:
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
Click to expand...
Click to collapse
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
Nevermind guys...I DID IT.Thanks so much...excellent guide
Hussainally said:
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
ok i lost root after flashing to 4.0.2 using this guide and re did install superboot windows .bat and now the phone rebooted and its stuck on google screen...how long do i wait and what do i do next???
Click to expand...
Click to collapse
Hussainally said:
Hussainally said:
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
ok i lost root after flashing to 4.0.2 using this guide and re did install superboot windows .bat and now the phone rebooted and its stuck on google screen...how long do i wait and what do i do next???
Click to expand...
Click to collapse
Give it some time, if it doesn't boot all is not lost. Pull the battery and restart.
Click to expand...
Click to collapse
ok..fingers crossed...how much time?
Halleluyah....Praise the lord....thanks a million...All is well
Hussainally said:
ok..fingers crossed...how much time?
Click to expand...
Click to collapse
I think that it depends on how many apps do you have...usually 2-3 minutes max. !
Hey guys,
Ever since I updated my Wileyfox a few days ago, it's gone to crap. Half my apps don't work, and they've removed features I really liked.
Is there any way to reverse this dreadful update and restore it to how it was?
Thanks in advance
jjl5590 said:
Hey guys,
Ever since I updated my Wileyfox a few days ago, it's gone to crap. Half my apps don't work, and they've removed features I really liked.
Is there any way to reverse this dreadful update and restore it to how it was?
Thanks in advance
Click to expand...
Click to collapse
Here you go
http://www.mediafire.com/download/24748t4ghkoam9h/cm-12.1-YOG7DAS2FI_%28recovery%29_%2828.12.15%29.zip
This is the recovery zip, I also have the fastboot zip if you want it?
robin0800 said:
Here you go
http://www.mediafire.com/download/24748t4ghkoam9h/cm-12.1-YOG7DAS2FI_%28recovery%29_%2828.12.15%29.zip
This is the recovery zip, I also have the fastboot zip if you want it?
Click to expand...
Click to collapse
Thanks very much Robin. Is that the cyanogen/android version prior to this latest OTA update? I'm looking for the official cyanogen, not cyanogenmod.
Do you know if I need to root my phone to be able to install it? Presumably I'd lose all my data?
Sorry for all the questions
EDIT: I think you sent the firmware for the Storm?
jjl5590 said:
Thanks very much Robin. Is that the cyanogen/android version prior to this latest OTA update? I'm looking for the official cyanogen, not cyanogenmod.
Do you know if I need to root my phone to be able to install it? Presumably I'd lose all my data?
Sorry for all the questions
EDIT: I think you sent the firmware for the Storm?
Click to expand...
Click to collapse
Yes it is cyanogen not cyanogenmod
and yes it is swift and not storm
robin0800 said:
Yes it is cyanogen not cyanogenmod
and yes it is swift and not storm
Click to expand...
Click to collapse
Ah ok, if you are 100% sure. Cos if it's for the storm it will probably hard brick the phone!
jjl5590 said:
Ah ok, if you are 100% sure. Cos if it's for the storm it will probably hard brick the phone!
Click to expand...
Click to collapse
I don't have a storm why would I download a storm file?
robin0800 said:
I don't have a storm why would I download a storm file?
Click to expand...
Click to collapse
I don't know xD
Did you also downgrade from the latest update?
Ok stupid question but do I need to root my phone to install the downgrade?
jjl5590 said:
Ok stupid question but do I need to root my phone to install the downgrade?
Click to expand...
Click to collapse
No its a signed Zip so should install on a stock ROM but be careful if you are downgrading the bootloader as that has been known to brick phones.
As far as I know the swift won't be bricked by this. But if you are worried I would use the fastboot zip and use a script to make sure everything is wiped first.
robin0800 said:
No its a signed Zip so should install on a stock ROM but be careful if you are downgrading the bootloader as that has been known to brick phones.
As far as I know the swift won't be bricked by this. But if you are worried I would use the fastboot zip and use a script to make sure everything is wiped first.
Click to expand...
Click to collapse
I'm trying to follow this guide to install it but it's saying I need a recovery as well, do you happen to have that too?
http://techchomps.com/how-to-install-a-custom-recovery-on-the-wileyfox-swift/
Many thanks
jjl5590 said:
I'm trying to follow this guide to install it but it's saying I need a recovery as well, do you happen to have that too?
http://techchomps.com/how-to-install-a-custom-recovery-on-the-wileyfox-swift/
Many thanks
Click to expand...
Click to collapse
You don't need a custom recovery that is the whole point of it being a signed zip
unzip first?
robin0800 said:
No its a signed Zip so should install on a stock ROM but be careful if you are downgrading the bootloader as that has been known to brick phones.
As far as I know the swift won't be bricked by this. But if you are worried I would use the fastboot zip and use a script to make sure everything is wiped first.
Click to expand...
Click to collapse
Hi,
When I am trying to
fastboot flash recovery filename
do I need to unzip the folder first?
or do I :
fastboot -i 0x2970 flash filename.zip
?
jjl5590 said:
I'm trying to follow this guide to install it but it's saying I need a recovery as well, do you happen to have that too?
http://techchomps.com/how-to-install-a-custom-recovery-on-the-wileyfox-swift/
Many thanks
Click to expand...
Click to collapse
if you can find the 12.1 fastboot zip you can revert back to factory reset stock by fastboot flashing:
Code:
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
and
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
PM me if you cannot find cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip
Hi, could you please confirm if this worked? I'm on a completely stock Swift with OTA to Cyanogen OS13. I'm finding the battery life disappointing so want to try downgrading to 12.1
While unlocking camera 2 api It says failed (remote:dtb not found) in fastboot boot patchedboot.img step, any idea whats wrong?I tried with latest magisk as well as with the one in the patched boot file. Bootloader is unlocked and my phone is in the latest build 11.0.4.0 stock.
Samir 120 said:
While unlocking camera 2 api It says failed (remote:dtb not found) in fastboot boot patchedboot.img step, any idea whats wrong?I tried with latest magisk as well as with the one in the patched boot file. Bootloader is unlocked and my phone is in the latest build 11.0.4.0 stock.
Click to expand...
Click to collapse
I suppose you are trying to flash the patched boot.img. If that's the case, the command is "fastboot flash boot patched_boot.img".
Neon丶 said:
I suppose you are trying to flash the patched boot.img. If that's the case, the command is "fastboot flash boot patched_boot.img".
Click to expand...
Click to collapse
Im trying to install gcam without root. It says fastboot boot patched_boot.img in every guide i have seen so far, are you sure i need to add flash? Im dont have much knowledge in these things dont want to cause problems dor my device.
Samir 120 said:
Im trying to install gcam without root. It says fastboot boot patched_boot.img in every guide i have seen so far, are you sure i need to add flash? Im dont have much knowledge in these things dont want to cause problems dor my device.
Click to expand...
Click to collapse
No, not flash. Just boot.
Sounds like you are not running the command from the folder with the patched boot file. Or the file has a different name.
I recently bought a Chinese phone from a relatively unknown manufacturer, so I was unable to find any TWRP images that match the device, I was wondering if it was possible to extract the boot image directly from a GSI ROM. My end goal is to install Magisk so if there is a better way to go about this please let me know.
can you tell model and brand
Hsnmastoor said:
can you tell model and brand
Click to expand...
Click to collapse
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.
XDA-Developer30 said:
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.
Click to expand...
Click to collapse
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter
Hsnmastoor said:
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter
Click to expand...
Click to collapse
Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek
If you wish to root your Mediatek Android phone, we'd dropped a guide on rooting using Magisk and stock boot.img at https://www.hovatek.com/forum/thread-21427.html , no custom recovery is required. Se
forum.hovatek.com
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
Thank you for the reply, I forgot to mention that I used Hsnmastoor's method successfully.
LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?
elmapq said:
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?
Click to expand...
Click to collapse
And your device is...???
LinhBT said:
And your device is...???
Click to expand...
Click to collapse
Tecno Spark 6 ke7
LinhBT said:
And your device is...???
Click to expand...
Click to collapse
I have a Vortex V22 MTM6761 There is no stock rom. It has unofficial GSI Pixel experience plus 13.0 running on it. I too would like to root. How can I retrieve the boot.img file from the GSI rom? Or how can I pull it from the phone via terminal and fastboot? All help is greatly appreciated! Happy Saint Patricks Day!
For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device
LinhBT said:
For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device
Click to expand...
Click to collapse
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?
defcondoc said:
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?
Click to expand...
Click to collapse
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!
.
LinhBT said:
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!
Click to expand...
Click to collapse
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!
defcondoc said:
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!
Click to expand...
Click to collapse
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.
LinhBT said:
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.
Click to expand...
Click to collapse
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?
I have 2 models I cannot find stock ROM's for:
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB - manufacture date year 2022
Moxee M2160 Model MH-T6000 2APQU-MH-T6000 Q6006_V1.0 - manufacture date year 2022
Can anyone find anything? I have scoured the web for months!
I can't believe there is nothing available for these phones.
Please let me know if you can find a stock ROM. I would love to learn where and how you found them. As I've have found nothing for months and months.
Thank you!!!
defcondoc said:
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?
Click to expand...
Click to collapse
You CAN extract the boot.img via terminal ONLY IF you're on a ROOTED devices!
So has anyone tried to keep root when switching to the new OOS12 Open Beta build released on 10/4/21? If so did you just do the same as doing a normal update? i.e. Going into Magisk before reboot and hitting the OTA button in the installer app.
nickdagriff said:
So has anyone tried to keep root when switching to the new OOS12 Open Beta build released on 10/4/21? If so did you just do the same as doing a normal update? i.e. Going into Magisk before reboot and hitting the OTA button in the installer app.
Click to expand...
Click to collapse
cant root dp2
will cause cash dump everytime
FizzyAps said:
cant root dp2
will cause cash dump everytime
Click to expand...
Click to collapse
Do you know why
encoded
FizzyAps said:
encoded
Click to expand...
Click to collapse
Do you think I should just throw myself off a building?
i mean its beta what did you except lol
I was just hoping to be able to test it and root it like every other open beta.
What about twrp
You cant flash anything at this time
It will cash dump
FizzyAps said:
cant root dp2
will cause cash dump everytime
Click to expand...
Click to collapse
What do you mean can't root db2? He's talking about the new open beta. Have you actually tried to root that?
Burt Squirtz said:
What do you mean can't root db2? He's talking about the new open beta. Have you actually tried to root that?
Click to expand...
Click to collapse
Yes I tried rooting both and they both end In cash dump
FizzyAps said:
Yes I tried rooting both and they both end In cash dump
Click to expand...
Click to collapse
How did you try though? Install to inactive slot, AND adb? Or just one of the other?
flashed patched img on both slots
FizzyAps said:
flashed patched img on both slots
Click to expand...
Click to collapse
Can you try this method bro? This is the surefire way to root color OS. A friend reported that it works. I'm traveling not near a PC now otherwise I'd do it.
Somehow I managed to get root on dp2 and I don't know how I did it. Because I didn't do these steps.
<How to Root OOS12 OP9 (aka ColorOS)>
Extract boot.img, vendor_boot.img, vbmeta.img from ota file first
Patch boot.img and vendor_boot.img using magisk manager
reboot phone to bootloader after moving patched imgs to pc
fastboot flash boot patched_boot.img
fastboot flash vendor_boot patched_vendor_boot.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
ENCODED, NO METHODS WORK....
I rooted successfully with a Chinese tool
It works on both OOS12 and ColorOS12
Burt Squirtz said:
Can you try this method bro? This is the surefire way to root color OS. A friend reported that it works. I'm traveling not near a PC now otherwise I'd do it.
Somehow I managed to get root on dp2 and I don't know how I did it. Because I didn't do these steps.
<How to Root OOS12 OP9 (aka ColorOS)>
Extract boot.img, vendor_boot.img, vbmeta.img from ota file first
Patch boot.img and vendor_boot.img using magisk manager
reboot phone to bootloader after moving patched imgs to pc
fastboot flash boot patched_boot.img
fastboot flash vendor_boot patched_vendor_boot.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I used this method to root last night and can confirm it works on OB 1 A12. I did the vbmeta part before flashing boot.img and didn't do the vendor_boot part at all.
https://www.droidwin.com/root-android-12-via-magisk-patched-boot-img-without-twrp/ this is the guide I followed.
P.S. On a side note I found it interesting that the "unlocked bootloader" message screen when booting is absent on this new OB1 A12 build. It's kinda nice, I know how much of an eye sore it is for some.
ecera said:
P.S. On a side note I found it interesting that the "unlocked bootloader" message screen when booting is absent on this new OB1 A12 build. It's kinda nice, I know how much of an eye sore it is for some.
Click to expand...
Click to collapse
Really?? I'll try it just to get rid of that message. I'm all about faster boot time.
terlynn4 said:
Really?? I'll try it just to get rid of that message. I'm all about faster boot time.
Click to expand...
Click to collapse
Well I cant really say the boot time is noticeably faster, but the unlocked bootloader message is deff gone for me.
ecera said:
Well I cant really say the boot time is noticeably faster, but the unlocked bootloader message is deff gone for me.
Click to expand...
Click to collapse
Since boot is significantly slower after unlocking bootloader, I figured the message was to blame and the reverse would also be true. I could be wrong. Thanks for the info though. It'd be nice if they get rid of that message entirely with A12 stable and going forward.
terlynn4 said:
Since boot is significantly slower after unlocking bootloader, I figured the message was to blame and the reverse would also be true. I could be wrong. Thanks for the info though. It'd be nice if they get rid of that message entirely with A12 stable and going forward.
Click to expand...
Click to collapse
It probably does boot a bit faster. Like you said that message is an extra few seconds. To me its not really noticeable, maybe to someone else it might be.