DEPRECATED GUIDE
INSTEAD USE Could-Chaplain's TWRP 12.1 v2.00.1-alpha+
This is a solution for those, like me, who let their phone upgrade to Android 12 and can't downgrade to A11.
It's base on Could-Chaplain's TWRP for A11 firmware (great thanks to you sir). I'm not a developer, it's just a makeshift job.
Base on :
TWRP v1.02.2-alpha
Firmware ("Build version") : A226BXXU5BVH2 (works even if you have another firmware version in your phone as long as it's an A12)
Of course, all of this is at your own risk. I am not responsible for lost warranty, lost data or any other damage to your device, neither for blowing the bridge on the river Kwaï.
How to root and flash TWRP :
Prerequisites :
Unlock Bootloader
Odin on PC
1. Reboot device to Download Mode (longpres vol+ / vol- and plug USB cable)
2. Download the magisk_a226b_boot.tar and the twrp12_a226b_recovery.tar from attachments
3. Start Odin on PC
4. In Odin press on Options and untick Auto Reboot
5. Flash magisk_a226b_boot.tar with Odin (In Odin click on AP, select the magisk_boot.tar and press start)
(It roots you phone, if you don't want go directly to step 7 with blank vbmeta.img (in magisk_a226b_boot.tar) in USERDATA slot (don't forget to TAR vbmeta.img).)
6. After flash magisk_a226b_boot.tar without errors press in Odin on Reboot download if possible, device reboots to Download Mode
7. Flash twrp12.1_a226b_recovery.tar with Odin (In Odin click on AP, select the twrp12.1_a226b_recovery.tar and press start)
8. If all is flashed without errors longpress power and vol- on device
9. (The most complicated part, if it doesn't work restart from step 1. For me it seems to be easier if Auto Reboot is tick in Odin Options before step 7, in this case no step 8, be quick.)
Instantly after device goes Blackscreen press and hold power and vol+ for 5-8 seconds to boot to TWRP
10. In TWRP press on Advanced, than on Terminal, write "multidisabler" and press on the blue button
11. Repeat step 10
12. Go back in TWRP main menu, press on Wipe then on Format data, type "yes" and press on the blue button.
12. Go back in TWRP main menu, press on Reboot, then on Recovery
How to flash GSI :
Prerequisites :
TWRP on your phone
adb/fastboot on your PC
1. Boot to TWRP
2. In TWRP press Wipe, Advanced Wipe, select Dalvik, data, cache and swipe to wipe
2. After wipe go back to main screen and press Reboot, then press Fastboot
3. Device reboots to TWRP with Fastboot Interface
4. Now plugin device to PC and open a terminal
5. Type : fastboot devices
6. If device is found type : fastboot flash system PATH/TO/YOUR/GSI.img
Ignore "Invalid sparse file format at header magic" message
7. After flash completed without errors type : fastboot reboot
Tested GSI (list) : crDroid 8.10 (A12) and LineageOS 20 TD-based (A13) both vanilla with MinMicroG release, work fine (but no 5G and no VoLTE/VoWifi).
After GSI installation, if you haven't internet on apps, refer to this post for explanation/workaround of a MediaTek-specific kernel bug.
If you want to hide unlocked bootloader warning (rooted phone only) go here AND here.
Feel free to report your failures and successes for everyone's benefit.
Credits (thanks to all of you) :
Could-Chaplain for TWRP11 A226B (special thanks for your work)
Williamtung for the guide to Magisk's root boot.img here
SoftnGeek for explanations to transform TWRP11 to TWRP12 here
osm0sis for Android Image Kitchen here
Cheese-ass for this guide here
AndyYan for apps internet problem solving
razs.originals and kevinARIAN21 for warning bootloader hiding solution
Do I need to flash anything else in odin with magisk and twrp like bl, cp etc or vbmeta ?
RoryTheNoncingCar said:
Do I need to flash anything else in odin with magisk and twrp like bl, cp etc or vbmeta ?
Click to expand...
Click to collapse
No just flash Magisk boot (vbmeta is include in magisk_a226b_boot.tar) in AP slot then click in Odin on Try to reboot download and after reboot, flash TWRP recovery in AP too.
For my phone, it worked like this.
can i use this on A226BXXU5BVH3 ?
KOROZILA said:
can i use this on A226BXXU5BVH3 ?
Click to expand...
Click to collapse
It depends. A226BXXU5BVH3 is MODEM/CP version. If your PDA/AP version is A226BXXU5BVH2, it's good. Otherwise I'm not sure it will work, I didn't try so I don't know. You can try and if it doesn't work see the Credits part of the post to create TWRP for your AP version.
{
"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"
}
KOROZILA said:
can i use this on A226BXXU5BVH3 ?
Click to expand...
Click to collapse
Did you try? I also have the same version.
Hkd6010 said:
Did you try? I also have the same version.
Click to expand...
Click to collapse
A226BXXU5BVH3 is a "Basebande version", it isn't the good information to watch.
A226BXXU5BVH2 is a "Build number", you need this information.
You can also watch "Android security update". A226BXXU5BVH2 "Build number" corresponding to 1 July 2022 "Android security version".
Go to Parameter/About device/Software informations
As you can see on a colleague's phone screenshot he has A226BXXU5BVH3 "Basebande version" and A226BXXS5BVI6 "Build version" (corresponding to 1 September 2022 "Android security update").
If you have A226BXXU5BVH2 as "Build number", it's good.
If you have A226BXXS5BVI6 or A226BXXS5BVJ2 (depends of your country/operator) as "Build number", I'm pretty sure the process works, cause it's Android 12 too, but I didn't try.
In this case, if you don't want to risk, you can downgrade to A226BXXU5BVH2 "Build number" with Odin (explanation here).
I found a gsi for Cherish OS but there are many downloads for different versions of this GSI do I have to download a specific one or I can use the one I want
xXLoulouXx said:
I found a gsi for Cherish OS but there are many downloads for different versions of this GSI do I have to download a specific one or I can use the one I want
Click to expand...
Click to collapse
As long as it's an ab and arm64 version, it will be fine. Googled or vanilla, read only or read-write system, with or without superuser, ...as you want.
If you choose one of these CherishOS A12 or A13, all releases seem to be possible.
ttritium said:
A226BXXU5BVH3 is a "Basebande version", it isn't the good information to watch.
A226BXXU5BVH2 is a "Build number", you need this information.
You can also watch "Android security update". A226BXXU5BVH2 "Build number" corresponding to 1 July 2022 "Android security version".
Go to Parameter/About device/Software informations
View attachment 5767847
As you can see on a colleague's phone screenshot he has A226BXXU5BVH3 "Basebande version" and A226BXXS5BVI6 "Build version" (corresponding to 1 September 2022 "Android security update").
If you have A226BXXU5BVH2 as "Build number", it's good.
If you have A226BXXS5BVI6 or A226BXXS5BVJ2 (depends of your country/operator) as "Build number", I'm pretty sure the process works, cause it's Android 12 too, but I didn't try.
In this case, if you don't want to risk, you can downgrade to A226BXXU5BVH2 "Build number" with Odin (explanation here).
Click to expand...
Click to collapse
Thanks for the reply. Yes, I have the exact same version mentioned in your screenshot. I am gonna download A226BXXU5BVH2 version firmware from Sammobile and then will try to flash TWRP as given above. Correct?
Hkd6010 said:
Thanks for the reply. Yes, I have the exact same version mentioned in your screenshot. I am gonna download A226BXXU5BVH2 version firmware from Sammobile and then will try to flash TWRP as given above. Correct?
Click to expand...
Click to collapse
Correct.
With A226BXXU5BVH2 version, it's sure the process works.
But with A226BXXS5BVI6 version, I'm 90% sure it works (cause I didn't try). If you want to try and reply the result after, it's wonderful (if it don't work, you just have to flash A226BXXU5BVH2 with odin, so it's not very risky but very kind for all).
ttritium said:
Correct.
With A226BXXU5BVH2 version, it's sure the process works.
But with A226BXXS5BVI6 version, I'm 90% sure it works (cause I didn't try). If you want to try and reply the result after, it's wonderful (if it don't work, you just have to flash A226BXXU5BVH2 with odin, so it's not very risky but very kind for all).
Click to expand...
Click to collapse
I have tried this process on A226BXXS5BVI6 and it worked fine. I did't have to downgrade to A226BXXU5BVH2. Thanks very much.
Hkd6010 said:
I have tried this process on A226BXXS5BVI6 and it worked fine. I did't have to downgrade to A226BXXU5BVH2. Thanks very much.
Click to expand...
Click to collapse
Thanks.
I modified the explanations to take this information into account.
ttritium said:
As long as it's an ab and arm64 version, it will be fine. Googled or vanilla, read only or read-write system, with or without superuser, ...as you want.
If you choose one of these CherishOS A12 or A13, all releases seem to be possible.
Click to expand...
Click to collapse
thank you very much
Also I tried the Cherish GSIs you linked but when I do "fastboot flash system gsi.img" it says "Invalid sparse file format at header magi" (not magic or something it really says "magi") can you help me (again) I'm pretty new to all this samsung stuff and GSIs
xXLoulouXx said:
Also I tried the Cherish GSIs you linked but when I do "fastboot flash system gsi.img" it says "Invalid sparse file format at header magi" (not magic or something it really says "magi") can you help me (again) I'm pretty new to all this samsung stuff and GSIs
Click to expand...
Click to collapse
I'm sorry but I'm not a specialist (newbie too) and I never seen this so I don't know.
Maybe you GSI.img is corrupted, try to download and uncompress it again.
I also advise you to begin the process again (or just flash from TWRP) with the new Could-Chaplain's TWRP 12.1 v2.00.1-alpha instead of my twrp12.1_a226b_recovery.tar which is just a makeshift job.
Touch dosent work is there a fix for this?
elosanta said:
Touch dosent work is there a fix for this?
Click to expand...
Click to collapse
Sorry no fix for this.
Try with TWRP v2.00.1-alpha.
ttritium said:
Sorry no fix for this.
Try with TWRP v2.00.1-alpha.
Click to expand...
Click to collapse
thank you!
Related
So sorry to say this but this only method works in WINDOWS 7 and for Marshmallow ROM ONLY
Supported Devices: Oppo F3 Plus (CPH1613EX) & Oppo R9s Plus (CPH1611EX)
Caution:
Please disable Antivirus for any false Detections
Screenshots
{
"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"
}
TWRP Recovery:
1. Download Drivers and install them (Disable Signed Driver Enforcement)
https://drive.google.com/open?id=1T6MTq1upNt_yxrPD9MfOHR8vTOzRisvs
2. Download Oppo R9s Plus/F3 Plus Marshmallow Firmware (CPH1611EX_11_A.16_180106) and Extract it using Winrar/7-zip into a seperate FOLDER
https://drive.google.com/file/d/1xo-J5Pe65-fXyJbysVrAZYQ1mocfl53s/view
2.1 Also Download Oppo A57 Firmware and extract it anywhere you like
https://drive.google.com/uc?id=0B_0XnEjFCVsPWndzSnp2YTFYSkU&export=download
3. Download TWRP Recovery - Keep the recovery img in the same folder as of extracted firmware folder and make sure recovery file name is set to "recovery.img"
Twrp 3.1.1-0 (Latest) - Material Theme and Inbuilt Super SU Root available for easy rooting BUT Chinese language
Download and Extract only recovery.img and place it under firmware folder. u can delete other files.
https://drive.google.com/file/d/1gkNNx2Ik6oRF-juBDNIilDUu31w6_oI_/view?usp=sharing
To change the chinese language to english please download and flash this zip But in English language you will not get Super SU Root option to root the device from built-in twrp. you have to download SU zip now. So root directly from chinese language and then flash the english language zip to be on safe and easy side
https://androidfilehost.com/?fid=817550096634752414
Twrp 3.1.0-0 (old) (RECOMMENDED) -
Normal appearance of twrp and no inbuilt SU (sometimes it prompts to install SU, if you decline once, it won't prompt again) and totally English language. Most importantly you can flash opposite OTA updates (ozip) via this twrp
https://www.dropbox.com/sh/qbobokagdgme2oa/AABQBtKTmbwChne9z1DaayHca?dl=0&preview=recovery.zip
4. Run the MsmDownloadTool from A57 Firmware folder and you will get Session Timeout error. just ignore it and close the software
4.1. Now run MsmDownloadTool from our F3 plus firmware folder and uncheck "Reset After Download"
5. Switch off ur Mobile and Hold Vol down + Vol Up simultaneously and Plug the usb to pc
5.1 After plugging to pc, open device manager and expand PORTS section and make sure the device is detected as "Qualcomm HS-USB QDLoader 9008 (COM xx)". if not you have drivers issues!
6. Press F5, uncheck all options except Recovery and double click on Recovery option and select the recovery.img from firmware folder.
7. press Start and Flashing will be success (Green color message). press stop and unplug the usb
8. Press and hold Vol Up and Power Button and release them when it vibrates. NOW IMMEDIATELY after seeing oppo logo AGAIN PRESS Vol up + Power button to Power Off your device to prevent booting!!!! (If you fail to turn off your device, mobile will boot and will auto restore the stock recovery. so you will have to re-flash the twrp again)
9. Now press Vol Down + Power button to Enter into TWRP
BONUS - Stock Recovery & New OTA Update
Stock Recovery build: CPH1611EX_11_A.16_180106
https://drive.google.com/open?id=1u2Td1g93FwyAdPuKYNqz_iMHAYMpwrwJ
New Build Version: CPH1611EX_11_A.18_180413
Flash this zip via twrp. if it gives error 7 please ask in comment section
https://drive.google.com/open?id=1UA_DEjSQ4ESQO22VuvEpBsZhW9UepafY
else, flash this ozip from stock recovery
https://drive.google.com/open?id=1u2R65wYrLy2zqIhjww8adYWkqBjXgdq3
ROOTING
Screenshot: No more red line
Boot into TWRP by Holding Vol Down + Power Button
TWRP 3.1.1.0 - Go To Advanced option (Last but one option), Tap on last option: Super SU Root and Swipe to flash
UNROOT: just uninstall the SuperSU app to remove root
TWRP 3.1.0.0 - Download this zip and copy to storage and flash it
https://drive.google.com/open?id=1dIa9jRgh5Jy_cayM4QuOw8nL8ma574jU
UnRoot: Open SuperSU>Settings>Full UnRoot.
Note: After Rooting via twrp your device might reboot twice. dont worry. its not a bootloop. its a sign of success
XPOSED FRAMEWORK - Fix Red Statusbar Warning
Screenshot:
1. Download and add extension (.zip)
https://www.dropbox.com/s/e35zeqf619...bar FIX?dl=0
2. Boot into TWRP and flash the xposed framework zip and reboot (Reboot will take about 15mins. Please dont think its a Bootloop. Have a nap)
3. Install XposedInstaller 3.1.1 apk AND Hookcoloros_1.1_2_new.apk
4. Open ColorsOs3.0 app and make sure all the options (toggles) in chinese are Enabled or leave it as deafult or if you know chinese you can choose what you want
5. Open Xposed Framework > Modules > Enable ColorOs module that you have installed now
6. Reboot. Thadaaaa. No more Red warning statusbar
Note: Flashing Xposeduninstall zip will uninstall the xposed framework. Also, if something went wrong and gone bootloop after installing the xposed framework then use this uninstaller zip to fix the bootloop. bootloop wont occur but just telling this on safety thing
Video Tutorial:
https://www.youtube.com/watch?v=T6yQWCSLZt4
Optional:
IMEI Backup
goto twrp and backup EFS partition
you can also backup using this easy method via pc : https://forum.xda-developers.com/on...click-backup-restore-efs-oneplus-one-t3150883
CREDITS:
Xda, Baidu, bbs.7to.cn
used couple of links and very useful thread: https://forum.xda-developers.com/android/help/how-to-root-oppo-r9s-plus-cph1611-t3609586
@Rimo4099 for sharing 100% working twrp recovery.img
@john_david9000 - For sharing valuable information
@wuxianlin - He is the one who ported twrp :fingers-crossed:
@cjkimlaysico - he gave the instructions to run the msm tool (hard part)
does this have the red line on the notification bar after root anymore? recommend me sth we can do after root this phone pls ty so much ☺
verydp1 said:
does this have the red line on the notification bar after root anymore? recommend me sth we can do after root this phone pls ty so much
Click to expand...
Click to collapse
yes, Statusbar will turn into Red saying Root is enabled but i havent tried fixing by myself
However i have found a way to FIX IT <3
Please check the OP again. im updating the fix
i can't access the download link for msm download tools, help pls sir
shepherd80 said:
i can't access the download link for msm download tools, help pls sir
Click to expand...
Click to collapse
damnnn. something is not legal by sharing that specific file maybe bcoz of paid or cracked content. idk
first please try to flash with stock msmdownloadtool.exe which u get by extracting firmware. if it doesnt work then you need cracked msmdownload tool
iHeymanth said:
yes, Statusbar will turn into Red saying Root is enabled but i havent tried fixing by myself
However i have found a way to FIX IT <3
Please check the OP again. im updating the fix
Click to expand...
Click to collapse
ty so much. and btw show me sth we can do after root :fingers-crossed:
and is this similar to remove the yellow line "develope mode..." ?
verydp1 said:
ty so much. and btw show me sth we can do after root :fingers-crossed:
and is this similar to remove the yellow line "develope mode..." ?
Click to expand...
Click to collapse
show you what ? i dont understand ur first line.
yes, similar to remove the yellow line but not yellow line. just similarly red line will remove. we can also remove the captcha codes and yellow warning lines of developer options etc.. im figuring out to test in f3 plus
iHeymanth said:
So sorry to say this but this only method works in WINDOWS 7 and for Marshmallow ROM ONLY
Caution:
1. Please disable Antivirus for any false Detections
2. After getting Rooted, the statusbar will turn into Red cautioning about root access
check the screenshot
Note: Downloading Firmware is an Optional thing to Install only Recovery. If you want to install both Rom and Recovery then Download the firmware files too
TWRP Recovery:
1. Download Drivers and install
https://drive.google.com/open?id=1T6MTq1upNt_yxrPD9MfOHR8vTOzRisvs
2. Download Oppo F3 Plus Marshallow Firmware and Extract it using Winrar/7-zip into a seperate FOLDER
https://drive.google.com/open?id=0B5ZISKae4wQKeEdfbGNOT3lDa28
3. Download the Tool. zip (extract it) and Recovery.img and place it under the Firmware's FOLDER (step2)
msmdownloadTool link is down. find the cracked tool in google or crack the stock tool manually by this tutorial : techzai.com/crack-msmdownload-tool/
https://drive.google.com/open?id=13AKVz94x6w4-GaSnPTXzgCoGjwm2QqpQ
4. Switch off ur Mobile and Hold Vol down + Vol Up simultaneously and Plug the usb to pc
5. Run the MsmDownloadTool and Load the extracted Firmware from folder (.ofp)
6. Press F5, uncheck all options except Recovery and double click on recovery to Browse the recovery.img
7. press Start and Flashing will be done.
Holding Vol Down + Power Button will boot into Recovery
To Avoid Signal Loss/ IMEI Missing in future, please boot into twrp and take a backup of EFS Partition
ROOTING
Boot into TWRP by Holding Vol Down + Power Button and Flash the SU or Magisk
find the zip somewhere in xda. i will post it later. sorry
Please check the Video tutorial for this Rooting process
I will try to post a clean video tutorial. stay tuned!
FIX to Red Statusbar Warning (Screenshot)
1. Download the zip below and extract them
https://drive.google.com/open?id=1hVLLigAks6ltcHrPL21L5hqDgkUKSwv5
2. Boot into TWRP and flash the xposed framework zip and reboot
3. Install XposedInstaller 3.1.1 apk AND Hookcoloros_1.1_2_new.apk
4. Open ColorsOs3.0 app and make sure all the options (toggles) in chinese are Enabled
5. Open Xposed Framework > Modules > Enable ColorOs module that you have installed now
6. Reboot. Thadaaaa. No more Red warning statusbar
Note: Flashing Xposeduninstall zip will uninstall the xposed framework. Also, if something went wrong and gone bootloop after installing the xposed framework then use this uninstaller zip to fix the bootloop. bootloop wont occur but just telling this on safety thing
Video Tutorial:
https://www.youtube.com/watch?v=T6yQWCSLZt4
CREDITS:
Xda and Developers who made all these zips/apks
@Rimo4099 for sharing the 100% confirmed recovery.img, video tutorial, screenshot and installation steps
@john_david9000 - For sharing valuable information to confirm the source of this recovery img
@Wuxalin - according to info that John david provided me, i believe this recovery is exactly same as OPPO R9S recovery by wuxalin
Click to expand...
Click to collapse
Thank you for the mention, honestly I just said a few details only. We need people like you to shed some light on these unloved phones. XDA community thanks you heartfully for your contribution.
The only thing I can say is : Go Forth, and plant the Nougat to the ground herewith. . . . . . . . . . . . . . . . It's time for Nougat to be rooted.
Also just like to confirm that MSMDownloadTool works for Windows 10 too, as proved by this article and video : http://www.techzai.com/crack-msmdownload-tool/
john_david9000 said:
Thank you for the mention, honestly I just said a few details only. We need people like you to shed some light on these unloved phones. XDA community thanks you heartfully for your contribution.
The only thing I can say is : Go Forth, and plant the Nougat to the ground herewith. . . . . . . . . . . . . . . . It's time for Nougat to be rooted.
Also just like to confirm that MSMDownloadTool works for Windows 10 too, as proved by this article and video : http://www.techzai.com/crack-msmdownload-tool/
Click to expand...
Click to collapse
i think i have the nougat recovery. testing in progress now. will let you know
edit: tested nougat recovery of r9s/r9sk but FAILED
tested windows 10 method of flashing via MiFlash tool. flashing goes success but mobile keeps vibrating but no life
tested twrp 3.1.1.0 and 3.1.0.0. both are working fine but the latest twrp is in chinese language. will figure out to change its language
only windows 7 with msmdownload tool method is working.
Good news:
Root > Magisk v16.0(latest stable) is working flawlessly
Will update OP with magisk installation steps
note: backup ur internal memory in advance xD xD
Hi, i recently update my oppo F3 plus (CPH1613EX_11_A.18_180413 marshmallow), and i try to root it using this method, it's always boot on the stock recovery when i finish (i did step by step every single world you said).
I think that's a security renforcement about this version of colorOs, i wonder if there is a way ton downgrade to the last version without losing my data (lots of apps), because i did root it whit the version that i had once.
Thanks you
Re: So, i flashed my oppo with the msmtool that you put on your post (all images expect datauser partition), and changed the recovery image before the phone boots..... and it woorks perfectly now.
PS: dont upgrade to the version CPH1613EX_11_A.18_180413 if you want root your phone, it won't work.
EniMaX said:
Hi, i recently update my oppo F3 plus (CPH1613EX_11_A.18_180413 marshmallow), and i try to root it using this method, it's always boot on the stock recovery when i finish (i did step by step every single world you said).
I think that's a security renforcement about this version of colorOs, i wonder if there is a way ton downgrade to the last version without losing my data (lots of apps), because i did root it whit the version that i had once.
Thanks you
Click to expand...
Click to collapse
Did you uncheck "Reset After Download" option in msmtool ?
No, i didn't ; in all case i didn't let the phone boot after passing the recovery.img.
Wich version of rom do you have please ?
EDIT: when i downgrade the rom, it worked perfectly
NB: after downgrading , the first time, the phone boot directly and it was the new version (wich causes me problems) that was on it, even when i had flashing all the system
EniMaX said:
No, i didn't ; in all case i didn't let the phone boot after passing the recovery.img.
Wich version of rom do you have please ?
Click to expand...
Click to collapse
1. U need to uncheck reset after download option to not let the tool to reboot it phone into os
2. I have upgraded to a.18 build via ota 65mb and root worked. Tested with my own hands
3. Caution: if you dont CHECK userpartition in msmtool, after reboot it asks for Android password to proceed and we don't know that password. It's a checkmate. You need to wipe everything to boot
4. If you have patience please flash Magical 16.0 and test it. For me Wi-Fi is not turning on after flashing magisk.
5. I suggest you to use the twrp 3.1.0. bcoz the latest 3.1.1 does not flash oppo ota (.ozip)
Thank you for replying, can you please sent me a link for this OTA updates , beacause the one which is proposed for me on my phone weights 1.7Gb , and the only link i found is on a vientnam website wich doesn't work (probabely because i'm in algeria lol)
EniMaX said:
Thank you for replying, can you please sent me a link for this OTA updates , beacause the one which is proposed for me on my phone weights 1.7Gb , and the only link i found is on a vientnam website wich doesn't work (probabely because i'm in algeria lol)
Click to expand...
Click to collapse
I forgot to take backup of that 65mb Ota. Sorry. I will restore stock recovery in sometime and will download that 65mb ota
Does our oppo camera supports camera2api feature?
okay thanks you. if you are talking about the "expert mode" , yes the feature is on it
EniMaX said:
okay thanks you. if you are talking about the "expert mode" , yes the feature is on it
Click to expand...
Click to collapse
I have enabled it to check pixel cameras to work but failed.
also if ur willing to do then please enable multi window in ur rooted marshmallow (build prop and developer mode method)
I tried but no multi window option enabled in recent apps
EniMaX said:
Thank you for replying, can you please sent me a link for this OTA updates , beacause the one which is proposed for me on my phone weights 1.7Gb , and the only link i found is on a vientnam website wich doesn't work (probabely because i'm in algeria lol)
Click to expand...
Click to collapse
OTA link for CPH1613EX_11_A.18_180413 (65mb)
Can use this 65mb ota if you are in A16 or A17 build versions
https://drive.google.com/file/d/1u2R65wYrLy2zqIhjww8adYWkqBjXgdq3/view?usp=drivesdk
(Resized to fit the XDA thread for mobile phones)
{
"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"
}
Hello everyone, my name's SmallTarzan (@dotMiracle at Telegram), and I'm here to do it once again - to write yet another guide.
But, why am I doing this? There are two other guides already that explain the installation process well.
Well, I've gone through them, and the first one was not clear to me, I had to read it several times to properly understand the guide. I think that's, especially for new users, not helpful. The other one was written quite well, (shoutout to @madsponge26).
So, here I am, with my little bit to add to this, so far quite empty, sub-forum.
- an unlocked bootloader
- a TWRP recovery image
- a GSI image of your choice
- an Encryption Disabler - the current build of TWRP cannot decrypt your data
The process of unlocking the bootloader is the same on all Xiaomi devices. (Not counting the Android One ones.)
This process factory-resets your phone.
-
0. Open your phone's settings, go to About Phone at the top, find "MIUI version (For POCO)", and tap on it 7 times. (You should see a notification at the bottom, that you are now a developer.)
0.1 Go back, scroll down to Additional settings > Developer Options > Check "OEM unlocking" slider, (it may ask you for your password). Also, open "Mi Unlock status", agree to the permissions, and click on "Add account and device".
0.2 After this, you have to wait for 72 hours to unlock your phone. (Xiaomi Security Procedure)
-
1. Head over to Xiaomi Unlock Tool website, register, if you haven't yet, and download the tool.
2. Open the tool, accept the agreement, log in, and connect your device via USB-C cable to your computer.
3. Now, we'll need to reboot our device to fastboot: Turn off your device completely, hold down power button + volume down button at the same time, until you see a green logo of "fastboot".
4. The tool should now detect the device, press the Unlock button.
At the moment, there's only one TWRP recovery image available for this phone.
0. Currently, the TWRP cannot decrypt your data, make sure to back it up beforehand.
-
0.1 Download the Encryption disabler
0.2 Download ADB tools (Also, run the .exe, let it install all the required files, the driver from Google too.)
0.3 It's recommended to remove your screen-lock before doing this.
1. Reboot your device to fastboot again: Turn off your device completely, hold down power button + volume down button at the same time, until you see a green logo of "fastboot".
1.1 Connect your device to your computer.
2. Open your ADB folder, shift+right click on an empty space in the folder, choose open a Powershell/Command prompt window. (The folder should be located at C:/adb, or in the root of your system drive /adb.)
3. Now, put the recovery image you've downloaded in the ADB folder.
4. Type: fastboot flash recovery twrp-3.2.3.0-beryllium-20180831.img (You can, optionally, rename the file to recovery.img to make the typing easier for you.)
5. Once the process completes, hold down the power button + volume up button. (Your device may even restart twice, hold these buttons until you see the TWRP recovery screen.)
6. Allow modifications, if prompted.
7. Go to Install > select the DisableForceEncryption_Treble.zip > Swipe to flash it.
8. Once that's done, go back to the main screen (by using the on-screen buttons), Wipe > Advanced Wipe > Select Data > Swipe to wipe.
9. Go back to the main screen again, Reboot > Recovery.
(Android P for Poco F1. For those who didn't get the pun.)
0.1 Let's get the image we want first. Head over to the: Treble-Enabled Device Development, and choose the OS you'd like.
For the sake of this tutorial, and obviously, the header with Android P in it, we'll use one of the P GSI images. I, personally, like the ArrowOS.
0.2 Reboot into recovery, and connect the device to your computer.
1. Download the ArrowOS-9.0-OFFICIAL-GSI-A.zip to your computer. (Or any other .zip you'd like to install.)
2. Unzip the file with WinRAR or 7zip.
3. Copy the .img file to either your SD card, or your internal storage.
4. Install > On the bottom right "Install Image" > Find the .img file > Tap on it.
5. Select partition System/System Image > Swipe to flash.
6. This might not be necessary, but I highly recommend flashing the DisableForceEncryption_Treble.zip again.
6.1 If you don't need root, reboot the device. (Reboot > System)
0. You may, as well, reboot the device first, and do the setup, in order to avoid any potential issues.
1. Download the latest stable version of Magisk.
2. Reboot to recovery.
3. Install > Find Magisk-v17.2.zip (make sure you selected "Install zip" at the bottom right) > Find the .zip file > Swipe to Flash.
4. Again, it's recommended to flash the DisableForceEncryption_Treble.zip.
5. Reboot > System.
@madsponge26
@Shivam Kumar Jha - used his TWRP image in this guide.
@ganesh varma - used his ArrowOS GSI in this guide.
No sound/Broken sound/Low volume temporary fix: here.
For GApps, you can download them here. Flash them through the TWRP recovery.
Reserved.
EDIT: The guide works for both MIUI 10, and P custom GSI ROMs.
Also, search for GSI A images.
Thanks @SmallTarzan for the tutorial. I will try it.
Starred for later reference when I finally got this phone.
Sent from my Xiaomi Redmi Note 4 using XDA Labs
This is the first guide i actually understood. Thank you for that. I've one question though, the OS you suggested, is it stable for poco f1. I'm actually new to a treble device so i don't actually know how it works. Thank you once again for this guide.
Hello, thank you for your guide it's really very well explained with enough details that any newb can understand.
Btw, i have suggestion for your thread title, if you want you should rename your thread title to "[GUIDE]Install Any Android P GSIs In Your Poco"
Its just my suggestion cause i think it's better to follow the correct proforma:silly:
Anyway, have a nice day.
Regards,
Ali.
u_knw_who said:
This is the first guide i actually understood. Thank you for that. I've one question though, the OS you suggested, is it stable for poco f1. I'm actually new to a treble device so i don't actually know how it works. Thank you once again for this guide.
Click to expand...
Click to collapse
I haven't tried it yet, I'll do a test tommorow, and I'll let you know the result.
Ali Haide 001 said:
Hello, thank you for your guide it's really very well explained with enough details that any newb can understand.
Btw, i have suggestion for your thread title, if you want you should rename your thread title to "[GUIDE]Install Any Android P GSIs In Your Poco"
Its just my suggestion cause i think it's better to follow the correct proforma:silly:
Anyway, have a nice day.
Regards,
Ali.
Click to expand...
Click to collapse
Done, thanks!
Thanks for your well made guide. I just wonder how well everything works with these GSI images. Usually some features don't work.
Tomatot- said:
Thanks for your well made guide. I just wonder how well everything works with these GSI images. Usually some features don't work.
Click to expand...
Click to collapse
I haven't faced any issues.
SmallTarzan said:
I haven't faced any issues.
Click to expand...
Click to collapse
is gcam and face unlock working with you?
adityajiwap said:
is gcam and face unlock working with you?
Click to expand...
Click to collapse
I'll let you know later today.
@SmallTarzan,
I didn't see Treblizing step ..... Does it mean this Poco F1 is Treble enabled already?
don´t have sound.
Anyone have the same problem?
yis221 said:
@SmallTarzan,
I didn't see Treblizing step ..... Does it mean this Poco F1 is Treble enabled already?
Click to expand...
Click to collapse
Yes, it is.
detritu5 said:
don´t have sound.
Anyone have the same problem?
Click to expand...
Click to collapse
Correct, it's a bug currently present on some treble ROMs.
https://forum.xda-developers.com/poco-f1/how-to/temp-audio-distorted-p-gsis-fix-t3839427
Good stuff, five stars for you my friend for putting in the effort to help the rookies
is face unlock working?
ganyguru said:
is face unlock working?
Click to expand...
Click to collapse
Not in treble roms as of now.
detritu5 said:
don´t have sound.
Anyone have the same problem?
Click to expand...
Click to collapse
use global stable rom as base before installing GSI. it should fix it
u_knw_who said:
Not in treble roms as of now.
Click to expand...
Click to collapse
is there an apk for the facescanner in the stock rom?
Running PixelExperience 8.1 GSI. Had a problem on the google initial play service setup. google came up with a message that my device is uncertified and I had to register it at google to use the play service. Anyone else got that problem ?
Root for all Exynos 850 devices.
A. Root part 1 - Preparing the file
I accept no responsibility for bricked phones but I will help you to recover.
1. Download the exact firmware (including upgrade date) for your device from https://samfrew.com or https://www.samfirmware.net/ or https://www.full-repair-firmware.com/search?q=A20 or
{
"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"
}
Samsung Firmware Download - Lastest official firmware updateSamsung Firmware Download Official and fast update Lastest and old version Max speed and free download Best Samsung Galaxy website
samfw.com
2. Download patched magisk
3. Use zarchiver to extract the apxxxxxx....md5 section from the firmware.
4. Use patched magisk to patch the ap section. Allow the extra files.
Click on install and select patch file.
The output will be a patched tar file.
B. To Unlock Bootloader
1. Activate developer options by going to settings, about phone, software information and tapping on build number 7 times.
On phone developer options in settings allow OEM unlocking and enable usb debugging by moving both
sliders RIGHT
If you don't see the OEM unlock
-Disable Auto System Update
-Then disable Automatic date and time (Found in General Management) > then set the time back 14 days
- Connect to the internet
-Go to software update then check for update and wait a long time till it registers the device on server
-Once it's registered the OEM Unlock should be visible in the Developer Options
then connect phone to PC
2. Reboot into download mode by holding down both Vol up and Vol down
(You might need to long press vol up to unlock bootloader)
then press vol up to continue
Reboot and skip through the setup process.
C. Root part 2
Reboot into download mode again
6. Flash the patched ap tar file using special Odin.
https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/
(Click on the ap button and choose the patched tar file. Press start)
7. Reboot.
8. Skip all the way through the set-up process.
I successfully rooted my SM-A127F U3 with this manual. There are two problems.
USB tethering to Debian 10 and Ubuntu 20.04 is broken after rooting.
Second problem is that I can't update my service provider.
First time rooting I replaced only the AP. Later I tried replacing everything. Once with CSC and once with HOME_CSC nothing works. When I patch with the original AP there is no CID manager problem. Tethering I didn't try
Usbtt said:
I successfully rooted my SM-127F U3 with this manual. There are two problems.
USB tethering to Debian 10 and Ubuntu 20.04 is broken after rooting.
Second problem is that I can't update my service provider.
First time rooting I replaced only AP. Later I tried replacing everything. Once with CSC and once with HOME_CSC nothing works. When I patch with the original AP there is no CID manager problem. Tethering I didn't try
Click to expand...
Click to collapse
Interesting.
Exynos 850 Resources
A127 M127 F127 A135 M135 A217 A047
t.me
Rooting with magisk is better option
@Malware said:
Rooting with magisk is better option
Click to expand...
Click to collapse
Yes.
A patched magisk is needed for this device.
2. Download patched magisk
3. Use zarchiver to extract the apxxxxxx....md5 section from the firmware.
4. Use patched magisk to patch the ap section. Allow the extra files.
Click on install and select patch file.
The output will be a patched tar file.
This method will give a patched vbmeta so twrp will then work properly.
physwizz said:
Yes.
A patched magisk is needed for this device.
2. Download patched magisk
3. Use zarchiver to extract the apxxxxxx....md5 section from the firmware.
4. Use patched magisk to patch the ap section. Allow the extra files.
Click on install and select patch file.
The output will be a patched tar file.
This method will give a patched vbmeta so twrp will then work properly.
Click to expand...
Click to collapse
Bruh, no. I mean yes one can root that way but a developer of magisk suggest not to use this way instead patch boot.img for your device using magisk and then flash it.
@Malware said:
Bruh, no. I mean yes one can root that way but a developer of magisk suggest not to use this way instead patch boot.img for your device using magisk and then flash it.
Click to expand...
Click to collapse
That will work but it doesn't give you a patched vbmeta.
So custom recovery gives an error
physwizz said:
That will work but it doesn't give you a patched vbmeta.
So custom recovery gives an error
Click to expand...
Click to collapse
Ig no.......
is there any android 12 patched magisk
please send without telegram link
TheWorldYT said:
is there any android 12 patched magisk
please send without telegram link
Click to expand...
Click to collapse
Yes
how to update magisk?
pando345 said:
how to update magisk?
Click to expand...
Click to collapse
Install the apk
physwizz said:
Root for all Exynos 850 devices.
A. Root part 1 - Preparing the file
I accept no responsibility for bricked phones but I will help you to recover.
1. Download the exact firmware (including upgrade date) for your device from https://samfrew.com or https://www.samfirmware.net/ or https://www.full-repair-firmware.com/search?q=A20 or
Samsung Firmware Download - Lastest official firmware updateSamsung Firmware Download Official and fast update Lastest and old version Max speed and free download Best Samsung Galaxy website
samfw.com
2. Download patched magisk
3. Use zarchiver to extract the apxxxxxx....md5 section from the firmware.
4. Use patched magisk to patch the ap section. Allow the extra files.
Click on install and select patch file.
The output will be a patched tar file.
B. To Unlock Bootloader
1. Activate developer options by going to settings, about phone, software information and tapping on build number 7 times.
On phone developer options in settings allow OEM unlocking and enable usb debugging by moving both
sliders RIGHT
If you don't see the OEM unlock
-Disable Auto System Update
-Then disable Automatic date and time (Found in General Management) > then set the time back 14 days
- Connect to the internet
-Go to software update then check for update and wait a long time till it registers the device on server
-Once it's registered the OEM Unlock should be visible in the Developer Options
then connect phone to PC
2. Reboot into download mode by holding down both Vol up and Vol down
(You might need to long press vol up to unlock bootloader)
then press vol up to continue
Reboot and skip through the setup process.
C. Root part 2
Reboot into download mode again
6. Flash the patched ap tar file using special Odin.
https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/
(Click on the ap button and choose the patched tar file. Press start)
7. Reboot.
8. Skip all the way through the set-up process.
Click to expand...
Click to collapse
Will this a21s file work for m12 also?
Star_xda said:
Will this a21s file work for m12 also?
Click to expand...
Click to collapse
Use delta magisk
physwizz said:
Use delta magisk
Click to expand...
Click to collapse
Can I do this without losing Data?
Star_xda said:
Can I do this without losing Data?
Click to expand...
Click to collapse
Yes
physwizz said:
Yes
Click to expand...
Click to collapse
Just tried but no luck. I flashed by bootloader but it was stuck at sending boot.img
Star_xda said:
Just tried but no luck. I flashed by bootloader but it was stuck at sending boot.img
Click to expand...
Click to collapse
Follow instructions exactly
physwizz said:
Yes
Click to expand...
Click to collapse
I am having issue rooting my samsung m12. The magisk is unable to patch the AP. Screenshot for reference. Please help me fix the issue.
mdbshuvo said:
I am having issue rooting my samsung m12. The magisk is unable to patch the AP. Screenshot for reference. Please help me fix the issue.
View attachment 5874391
View attachment 5874393
Click to expand...
Click to collapse
you must use delta magisk
{
"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"
}
It took me sometime, but I can now share with you a TWRP with basic functionality. You of course flash at your own risk. I am not responsible for lost warranty, lost data or any other damage to your device.
This Build of TWRP is based on:
Firmware: A226BXXU4AVB1(Android 11) and A226BXXU4BVF7(Android 12)
TWRP-11 minimal manifest or TWRP-12.1 minimal manifest
Device Tree
Kernel source
Working:
flash of zips
fastbootd
flashing of GSI images (via fastbootd)
MTP
Not working:
Probably a lot of stuff ...
What you need:
Unlocked bootloader.
Odin3 v3.13.1
android platform-tools and device driver.
adb and fastboot
Magisk or GSI depending on what you want to do.
Patience, the device can be very tricky to get to download mode.
How to flash:Be advised that this build is a work in progress and is not ready as a daily driver. Only flash if you know what you are doing.
Spoiler
First read all points below, without doing anything. Warning, you will lose all your data!
If you are on Android 11 firmware download v1.01.2-alpha if you are on Android 12 firmware download the recovery.tar from here.
You start off in Odin, put recovery.tar in AP slot and the vbmeta_disabled_R.tar in the USERDATA slot, uncheck auto-reboot.
After the flash is completed hold down power + volume down, instantly after device goes Black screen press and hold power + vol up to boot to TWRP
if you didn't get to TWRP, you have to flash again.
In TWRP, go to Advanced → terminal.
Type multidisabler two times.
Now go to Wipe → Format Data (not wipe) → and type yes.
You can boot to system now.
Hot to install Magisk:
Spoiler
Method 1, Micro-SDCard
Download Magisk from here, rename the file from .apk to .zip
Save the file to a Mico-SDCard
Reboot the phone to TWRP.
Go to Install → Select Storage → Micro-SDCard. In the file system, choose Magisk-vXX.X.zip and swipe to confirm flash.
You can now Reboot to System
Method 2, sideload
Download Magisk onto your PC from here, rename the file from .apk to .zip.
Reboot the Phone into TWRP. Go to Advanced → ADB Sideload → Swipe to start Sideload.
On your PC, type in a Terminal adb sideload Magisk-v24.3.zip
You can now Reboot to System. adb reboot system
How to install GSI:
Spoiler
Go to Wipe → Format Data (not wipe) → and type yes.
Now reboot to fastboot.
Connect the phone to your pc and startup a terminal of your choice.
In the terminal type fastboot flash system name-of-your-gsi-iamge.img (it has to be a .img file, extract .img.xz files do not just rename them).
You should now be good to go and can reboot to system.
Thanks and credits to:
cheese-ass
akhil99
TeamWin
How to get TWRP log files:recovery.log
adb pull /tmp/recovery.log
OR
Advanced -> Copy Log -> Swipe to copy log to default storage
dmesg
adb shell dmesg > dmesg.log
OR
Advanced -> Copy Log -> check "Include kernel log" -> Swipe to copy log to default storage
logcat
adb logcat -d > logcat.txt
OR
Advanced -> Copy Log -> check "Include Logcat" -> Swipe to copy log to default storage
Changelogv2.00.1-alpha
bump firmware and touchscreen drivers to A226BXXU4BVF7 and TWRP to TWRP-12.1
v1.02.2-alpha
added drivers for himax touch screens.
v1.02.1-alpha
added drivers for novatek touch screens.
v1.01.2-alpha
added patch with improved multidisabler
v1.01.1-alpha
update multidisabler
v1.01.0-alpha
fix permission for mkbootimg
v1.00.0-alpha
Initial Release
This has been tested, right? If it does work, I'll probably try it out when I have free time, which might be in a few days.
Yes, it runs on my A22 5G.
Could-Chaplain said:
Yes, it runs on my A22 5G.
Click to expand...
Click to collapse
It worked. But I didn't read your post carefully and now I have to format data :/
Edit: Ran multidisabler twice. On the second time, it said that /system was an invalid argument
Edit2: Trying to mount partitions don't work, like trying to make a backup or using the file manager. Speaking of backups, I didn't format data because I really don't want to, and it rebooted safely (Thank god), so now I'm making a backup of apps I should have made a week ago.
Edit: Ran multidisabler twice. On the second time, it said that /system was an invalid argument
Click to expand...
Click to collapse
It's the same for me, but no issues so far.
Edit2: Trying to mount partitions don't work, like trying to make a backup or using the file manager. Speaking of backups, I didn't format data because I really don't want to, and it rebooted safely (Thank god), so now I'm making a backup of apps I should have made a week ago.
Click to expand...
Click to collapse
That will be because you didn't format data. If I find sometime, I will try to reproduce that. Thank you, for testing.
Edit: Backups should work fine if you uncheck data?
Is the A226BZH3AUL1 suitable？
a0963655966 said:
Is the A226BZH3AUL1 suitable？
Click to expand...
Click to collapse
If your device is a SM-A226B you should be fine. But as always, flash at your own risk.
Works great! Thanks! Keep up the good work!
Any idea why adb shell doesn't work? For the same reason why /data isn't mountable?
Thank you! Going to test asap.
lebigmac said:
Works great! Thanks! Keep up the good work!
Any idea why adb shell doesn't work? For the same reason why /data isn't mountable?
Click to expand...
Click to collapse
/data is most likely not mountable because you didn't run multidisabler twice and formatted data? ADB shell works fine for me, check in device manager that it shows up as ADB Interface.
Tested working, but haven't succeeded flashing a gsi yet, phone reboots and then goes to blank black screen, and ideas?
koosman911 said:
Tested working, but haven't succeeded flashing a gsi yet, phone reboots and then goes to blank black screen, and ideas?
Click to expand...
Click to collapse
Honestly, it could be everything. Just go over How to flash again. But this time without vbemta and multidisabler. Then continue as described in How to flash GSI. Please let me know if that works for you.
I recommend Pixel Experience.
Could-Chaplain said:
Honestly, it could be everything. Just go over How to flash again. But this time without vbemta and multidisabler. Then continue as described in How to flash GSI. Please let me know if that works for you.
I recommend Pixel Experience.
Click to expand...
Click to collapse
Are you using pixel experience on your device currently?
koosman911 said:
Are you using pixel experience on your device currently?
Click to expand...
Click to collapse
Yes and no, currently I am working on TWRP and there for flash the stock Rom quite frequently. But I do plan to use Pixel Experience. The only thing that does not work is NFC. But that seems to be the case with all the GSI I could find, as they are all based on phh.
Hey Guys, I did some work on the TWRP recovery. It's now more reliable, I highly recommend the update. You will find the download link and updated instructions at the top.
Thank you sir, updated recovery works perfectly on two separate phones so far, I've flashed a few gsi's and they work as far as they are able to obviously each gsi might have its own issues, the two phones I have don't have Nfc so I can't help to test that sadly. We appreciate the hard work.
koosman911 said:
Thank you sir, updated recovery works perfectly on two separate phones so far, I've flashed a few gsi's and they work as far as they are able to obviously each gsi might have its own issues, the two phones I have don't have Nfc so I can't help to test that sadly. We appreciate the hard work.
Click to expand...
Click to collapse
Thank you. What other phones despite the A22 5G are you using the recovery with?
Edit: Ahhh, you mean, you have nothing to test NFC with?
The model of a22 5G available in my country does not have nfc.
Hello guys. Does anybody know when would we be able to root our beloved Flip 4? I haven't seen any thread for it. Is there something that's blocking the devs from discovering a root method? Just trying to understand.
Thanks!
shreyas.kukde said:
Hello guys. Does anybody know when would we be able to root our beloved Flip 4? I haven't seen any thread for it. Is there something that's blocking the devs from discovering a root method? Just trying to understand.
Thanks!
Click to expand...
Click to collapse
Probably just need to wait for John Woo (developer of magisk) to update it for the fold and flip 4 series. You can try asking in the magisk forums if anyone knows anything.
if you can unlock the bootloader (not possible on the US versions) download the stock firmware and transfer the AP file to your phone.
then install magisk and patch the AP file, transfer back and odin flash the patched file and you should have root.
beanbean50 said:
if you can unlock the bootloader (not possible on the US versions) download the stock firmware and transfer the AP file to your phone.
then install magisk and patch the AP file, transfer back and odin flash the patched file and you should have root.
Click to expand...
Click to collapse
Well unfortunately I'm not that expert as to discover how to unlock bootloader myself. But I guess the expert guys could help us if they would like to.
shreyas.kukde said:
Well unfortunately I'm not that expert as to discover how to unlock bootloader myself. But I guess the expert guys could help us if they would like to.
Click to expand...
Click to collapse
if you can get into the development options in settings you should be able to see OEM unlock toggle but be warned if you choose it it will wipe all your data..!
1) go into settings/about phone
2) then software information tap on build number 7 times
3) go back to settings and you should see development options at the bottom
4) if the OEM unlock is there choose it and it will reboot to the bootloader screen
5) it will then ask you do you really want to unlocck it, if you choose to yes it wipe all data and you have to start from scratch re-installing everything
6) download the latest firmware and extract it to a new folder on your PC
7) copy the AP file to your phone
8) download and install the latest Magisk apk
9) in Magisk choose the top option 'install' then select patch a file
10) after patching transfer the file back to your PC (it can be found in the download file on your phone)
11) download and install Odin on your PC
12) open Odin and put the AP patched file in the AP slot and the CSC file in the CSC slot
13) after flashing and rebooted install the Magisk app again and it should confirm being rooted after Magisk reboots the phone
beanbean50 said:
1) go into settings/about phone
2) then software information tap on build number 7 times
3) go back to settings and you should see development options at the bottom
4) if the OEM unlock is there choose it and it will reboot to the bootloader screen
5) it will then ask you do you really want to unlocck it, if you choose to yes it wipe all data and you have to start from scratch re-installing everything
6) download the latest firmware and extract it to a new folder on your PC
7) copy the AP file to your phone
8) download and install the latest Magisk apk
9) in Magisk choose the top option 'install' then select patch a file
10) after patching transfer the file back to your PC (it can be found in the download file on your phone)
11) download and install Odin on your PC
12) open Odin and put the AP patched file in the AP slot and the Home CSC in the CSC slot
13) after flashing and rebooted install the Magisk app again and it should confirm being rooted after Magisk reboots the phone
Click to expand...
Click to collapse
Wow. Are you rooted?
yes, rooted on the flip 3 but it will work on the flip 4 aswell. I know it looks quite difficult at first but it does become easier after doing it a few times
beanbean50 said:
yes, rooted on the flip 3 but it will work on the flip 4 aswell. I know it looks quite difficult at first but it does become easier after doing it a few times
Click to expand...
Click to collapse
I'm not able to get past the step #3 on this phone, its locked down.
Can access recovery but the "wipe data" option is removed.
Any advice? It's a demo unit with an IMEI number I kinda got scammed into buying, trying ot figure out if its a lost cause.
{
"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"
}
ankur079 said:
I'm not able to get past the step #3 on this phone, its locked down.
Can access recovery but the "wipe data" option is removed.
Any advice? It's a demo unit with an IMEI number I kinda got scammed into buying, trying ot figure out if its a lost cause.
View attachment 5707965
Click to expand...
Click to collapse
if you have the US version then it's mission impossible
beanbean50 said:
if you have the US version then it's mission impossible
Click to expand...
Click to collapse
Because it's a new-er device or just never gonna happen? I even made a call using my SIM to check all is well.
ankur079 said:
Because it's a new-er device or just never gonna happen? I even made a call using my SIM to check all is well.
Click to expand...
Click to collapse
unfortunately all US phones are bootloader locked
that's annoyingly unfortunate. I suppose i'm out 750 bucks, gonna file a police report if nothing else, what an uncool guy.
not true. root will come for t mobile and unlocked versions
Jmoney55 said:
not true. root will come for t mobile and unlocked versions
Click to expand...
Click to collapse
not true. when they say unlocked versions nowadays in the US they are referring to carrier unlocked
beanbean50 said:
1) go into settings/about phone
2) then software information tap on build number 7 times
3) go back to settings and you should see development options at the bottom
4) if the OEM unlock is there choose it and it will reboot to the bootloader screen
5) it will then ask you do you really want to unlocck it, if you choose to yes it wipe all data and you have to start from scratch re-installing everything
6) download the latest firmware and extract it to a new folder on your PC
7) copy the AP file to your phone
8) download and install the latest Magisk apk
9) in Magisk choose the top option 'install' then select patch a file
10) after patching transfer the file back to your PC (it can be found in the download file on your phone)
11) download and install Odin on your PC
12) open Odin and put the AP patched file in the AP slot and the Home CSC in the CSC slot
13) after flashing and rebooted install the Magisk app again and it should confirm being rooted after Magisk reboots the phone
Click to expand...
Click to collapse
I own a Flip 4 from Austria and can confirm your described method works, except I had to use CSC —> CSC instead of the Home CSC, cause it didn’t boot before.
Google Wallet (ex Pay) works with Magisk Props module as well!
Plazza86 said:
I own a Flip 4 from Austria and can confirm your described method works, except I had to use CSC —> CSC instead of the Home CSC, cause it didn’t boot before.
Google Wallet (ex Pay) works with Magisk Props module as well!
Click to expand...
Click to collapse
Glad it all went well for you, it's quite a learning curve at first..!
I've edited my 'how to' about the CSC file thanks
Jmoney55 said:
not true. root will come for t mobile and unlocked versions
Click to expand...
Click to collapse
Sure it will. Just pay $150 and let some unknown asshole remote into your device.
This info came out today, but I have the unlocked version that I bought directly from samsung (U1) and I can confirm that I cannot "OEM Unlock" my Flip4.
Samsung uploads Galaxy Z Flip 4 and Fold 4 kernel sources to the joy of ROM makers
The Galaxy Z Flip 4 and Fold 4 are going open source:
www.androidpolice.com
good evening @
shreyas.kukde @jdenman03 @entropism @beanbean50 @Plazza86 @Jmoney55 @ankur079 @Philnicolls89, I have just bought the Samsung Galaxy Z Flip 4 in Europe (France) and indeed to ROOT it you have to put the Tarmd5 AP file in the AP box and the CSC file (and not Home CSC) in the CSC box to that everything works fine, when the phone restarts, you have to reinstall Magisk and everything is OK. Thanks for this tutorial, hope it helps other people.