Related
Hi Guys,
Note : By doing this, you know that you're gonna do a modification to your phone, and im not in any way, responsible for what happen after. Escape Route for if something wrong happen is provided, but YOU DO THIS ON YOUR OWN RISK
since this phone is fairly new, at this moment a clear rooting method haven't established yet. This is what this thread for.
Based on information gathered from P20 Lite Forum (the rooting guide for that device even already up - here), it seems the old trick of rooting (from Mate 10 Pro) using Patched Boot Method is working fine. And Magisk is working
Basically this method need few pre-requisites :
1. Unlocked Bootloader (by getting the code here ) - and if you not sure how to do it, go here for the guide
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
3. Magisk Manager 5.5.4 (from Magisk Thread) to patch the .img above, or
4. Patched RAMDISK image (i patched it) from here
5. and of course computer with ADB & Fastboot installed (make sure you have latest SDK to prevent something not working)
Now, to Root it, all you need to do is,
1. Boot into bootloader
2. Type
Code:
fastboot flash ramdisk patched_boot.img
(patched_boot.img is the file you download from prerequisites number 4, placed it in the same directory with your adb & fastboot - i assume you know that already)
3. Reboot
4. You now should have root access, download Magisk Manager to manage modules and superuser
(you might need to flash this module if you failed to pass safetynet)
In case something go wrong, flash back the stock RAMDISK from pre-requistes number 2 above using same method as what u did to flash the patched one.
That way worked. Thanks.
Edit:
Just as a hint. To get magisk work as it should..
After boot into the system and installed Magisk Manager, install Magisk from there again, so you dont get any /data/magisk problems.
SafteyNet passed then.
Fingers crossed twrp is possible soon
Works on CLT-L09
I have a German single Sim from Vodafone tested the root yesterday and works very well
Would this method work on CLT-L09 model? Thanks
danifilth4king said:
Would this method work on CLT-L09 model? Thanks
Click to expand...
Click to collapse
The post before you just confirmed yourbquestion, LoL
Yes it does
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
otonieru said:
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
Click to expand...
Click to collapse
fl4r3 said:
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
Click to expand...
Click to collapse
It's from www.allrom.ir (its in persian) and there's another site, rusian one if am not mistaken, but i forget the exact address
Great, thanks for that! I managed to find it on allrom.ir
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
danifilth4king said:
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
Click to expand...
Click to collapse
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
otonieru said:
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
Click to expand...
Click to collapse
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
danifilth4king said:
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
Click to expand...
Click to collapse
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
otonieru said:
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
Click to expand...
Click to collapse
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
danifilth4king said:
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
Click to expand...
Click to collapse
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
otonieru said:
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
Click to expand...
Click to collapse
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
danifilth4king said:
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
Click to expand...
Click to collapse
Its better to do it from ON state, and use adb reboot bootloader command
otonieru said:
Its better to do it from ON state, and use adb reboot bootloader command
Click to expand...
Click to collapse
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Put the device off and hold power button and volume down. You should come directly into the rescue mode.
danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Ah, sorry, i got it wrong. Yes, its power n volume down.
Can I relock bootloader, and flash completely stock if I need?
Yes but at this moment don't, BC if something goes wrong u have no way of fixing it unless u call oneplus and wait for them to give u a remote session, don't be scared to have ur bootloader unlocked
suzook said:
Can I relock bootloader, and flash completely stock if I need?
Click to expand...
Click to collapse
Someone else will have to verify as my OP6 is still shipping but..
YES, OnePlus 6 should still be able to go complete back to stock as it always has.
The same procedure as the 3, 3T, 5, 5T will likely follow:
if you flash a complete stock rom such as (this is a OP6 stock rom): androidfilehost.com/?fid=674106145207488340
then while booted into fastboot mode: fastboot oem lock
This is a standard procedure for OnePlus devices and I'll test it out once I get mine.
The rom i linked to is the stock rom, an OP moderator linked to it.
And the fastboot command is just a standard command. So unless they decide to screw their main audience this time around, :good:.
---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------
Bradl79 said:
Yes but at this moment don't, BC if something goes wrong u have no way of fixing it unless u call oneplus and wait for them to give u a remote session, don't be scared to have ur bootloader unlocked
Click to expand...
Click to collapse
Why do you state this?
OP has already shared a link to a stock rom. And the lock/unlock bootloader command is a standard for their devices.
effmsee said:
Someone else will have to verify as my OP6 is still shipping but..
YES, OnePlus 6 should still be able to go complete back to stock as it always has.
The same procedure as the 3, 3T, 5, 5T will likely follow:
if you flash a complete stock rom such as (this is a OP6 stock rom): androidfilehost.com/?fid=674106145207488340
then while booted into fastboot mode: fastboot oem lock
This is a standard procedure for OnePlus devices and I'll test it out once I get mine.
The rom i linked to is the stock rom, an OP moderator linked to it.
And the fastboot command is just a standard command. So unless they decide to screw their main audience this time around, :good:.
---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------
Why do you state this?
OP has already shared a link to a stock rom. And the lock/unlock bootloader command is a standard for their devices.
Click to expand...
Click to collapse
just wait until u get it
don't believe u can sideload OS anymore, yes we do have a fastboot mode to restore but u will have to have ur bootloader unlocked, if u have ur bootloader locked there is not way to put on OS on there due to twrp is not mountable and u cannot side load, so its not like other OP devices
effmsee said:
Someone else will have to verify as my OP6 is still shipping but..
YES, OnePlus 6 should still be able to go complete back to stock as it always has.
The same procedure as the 3, 3T, 5, 5T will likely follow:
if you flash a complete stock rom such as (this is a OP6 stock rom): androidfilehost.com/?fid=674106145207488340
then while booted into fastboot mode: fastboot oem lock
This is a standard procedure for OnePlus devices and I'll test it out once I get mine.
The rom i linked to is the stock rom, an OP moderator linked to it.
And the fastboot command is just a standard command. So unless they decide to screw their main audience this time around, :good:.
---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------
Why do you state this?
OP has already shared a link to a stock rom. And the lock/unlock bootloader command is a standard for their devices.
Click to expand...
Click to collapse
Things are missing in recovery. Im hoping they forgot vs take the feature out.
Bradl79 said:
just wait until u get it
don't believe u can sideload OS anymore, yes we do have a fastboot mode to restore but u will have to have ur bootloader unlocked, if u have ur bootloader locked there is not way to put on OS on there due to twrp is not mountable and u cannot side load, so its not like other OP devices
Click to expand...
Click to collapse
Obviously you have to have you bootloader unlocked.
What are you trying to say? I can't follow your sentence structure. Please use proper English structure... or remotely proper...
You're claiming that with the OnePlus 6 you can no longer sideload roms? What??? That would be a HUGE slap in the face to us.
I wouldn't believe what this guy is saying.
I'm not claiming I factually know that the OP6 can be unlocked through that method but it is highly likely it is. As said, I'm still waiting on the OP6. If OnePlus doesn't allow these things, re-locking bootloader and sideloading, they're FU***** all of us over and I'm sure would suffer major backlash from the user base.
---------- Post added at 02:21 AM ---------- Previous post was at 02:20 AM ----------
intruda119 said:
Things are missing in recovery. Im hoping they forgot vs take the feature out.
Click to expand...
Click to collapse
Ah, got it. That sucks. :'( Thanks!
effmsee said:
Obviously you have to have you bootloader unlocked.
What are you trying to say? I can't follow your sentence structure. Please use proper English structure... or remotely proper...
You're claiming that with the OnePlus 6 you can no longer sideload roms? What??? That would be a HUGE slap in the face to us.
I wouldn't believe what this guy is saying.
I'm not claiming I factually know that the OP6 can be unlocked through that method but it is highly likely it is. As said, I'm still waiting on the OP6. If OnePlus doesn't allow these things, re-locking bootloader and sideloading, they're FU***** all of us over and I'm sure would suffer major backlash from the user base.
---------- Post added at 02:21 AM ---------- Previous post was at 02:20 AM ----------
Ah, got it. That sucks. :'( Thanks!
Click to expand...
Click to collapse
if all else fails we do have an unbrick tool, but from what i have read, u can no longer sideload with ur bootloader locked and there is not install from internal storage from stock recovery
I learned the hard way. Soft brick in the first hour of ownership.i thought I really broke something until eventually a few others reported on it. B
Op I would wait
I just relocked my bootloader with no issues. I uninstalled magisk through magisk manager, reboot to completely remove, then factory reset, boot into fastboot and relock. No issues. Note I didn't use twrp. I was still on stock bootloader.
BoboBrazil said:
I just relocked my bootloader with no issues. I uninstalled magisk through magisk manager, reboot to completely remove, then factory reset, boot into fastboot and relock. No issues. Note I didn't use twrp. I was still on stock bootloader.
Click to expand...
Click to collapse
Certain I did something wrong. But I tried the same thing initially and would bootloop to recovery after factory reset. Wasn't a biggie learned about the new a/b system in the process
Somewhat related question:
If you relock the bootloader, does Widevine go back to L1?
One user reported no. Is it really a permanent change of the Widevine status to unlock it?
I might be able to deal with 480p netflix, but if I sell this phone someday it sucks for the next owner.
No worry just try mega unbrick guide used it to relock bootloader and flash stock hydrogen os it can recover your device from even hardbrick I tested it for safety it works like charm so I recommend you that
Can anyone who has unlocked and re-locked their bootloader check their Widevine status in DRM info?
I have relocked because netflix quality was to low on when unlocked. When i relocked i got the drm lvl 1 back so it works
noppoer2 said:
I have relocked because netflix quality was to low on when unlocked. When i relocked i got the drm lvl 1 back so it works
Click to expand...
Click to collapse
What's the procedure to re lock the bootloader and revert to stock recovery along with no root.
I unlocked the boot loader, installed TWRP and Magisk but would like to go back to stock. Any help will be appreciated
kailashnj said:
What's the procedure to re lock the bootloader and revert to stock recovery along with no root.
I unlocked the boot loader, installed TWRP and Magisk but would like to go back to stock. Any help will be appreciated
Click to expand...
Click to collapse
Reinstall your rom ( i believe 5.1.6 ) to get rid of TWRP & root
Factory reset
Then on fastboot " fastboot oem lock"
Data & internal storage will be wiped
Which means post following the steps origins bootloader will be locked and I will not get the warning again right at the start of the phone
All you can do is try but first make a Nandroid just in case this falls through
Hi, I want to lock my bootloader after recently unlocking it on my OP6 to install Oxygen OS as was originally on Hydrogen OS. If I use CMD and type fastboot oem lock, what are the risks of the phone going into a boot loop, and also, does the factory reset revert the phone back to Hydrogen OS? Cheers.
thealexwu said:
Hi, I want to lock my bootloader after recently unlocking it on my OP6 to install Oxygen OS as was originally on Hydrogen OS. If I use CMD and type fastboot oem lock, what are the risks of the phone going into a boot loop, and also, does the factory reset revert the phone back to Hydrogen OS? Cheers.
Click to expand...
Click to collapse
Lock as you unlocked in cmd by typing lock instead of unlock. It will make a wipe, so I recommend make backup before.
Edit: Update!
See My Guide: [Guide] Pixel 3 XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + September 2018 Security Patch
Doubtful being that the article's date is from May...
jrac86 said:
Doubtful being that the article's date is from May...
Click to expand...
Click to collapse
Edit: OP updated!
Fake News...
It's a feature of Magisk. You install Magisk manager and it will save a patched version of your boot.img that you can pull and flash in fastboot mode.
Sent from my Pixel 2 XL using Tapatalk
bxlegend said:
It's a feature of Magisk. You install Magisk manager and it will save a patched version of your boot.img that you can pull and flash in fastboot mode.
Click to expand...
Click to collapse
Some think the link is "clickbait."
I thought if you installed MM only, you could patch a boot.img with MM. Are you saying that when you install MM it does it without intervention?
Last time I did it you had to get a boot image, transfer it to the device, MM can then patch it, you transfer it back to a PC, flash in fastboot.
Pretty sure we need to wait for a few things, twrp for the Pixel 3, and Google to release the images.
the phone is starting to get to hands on people
it's not like samsung where we can make twrp and root without the device
we need to get images and do testing too
kachaffeous said:
Pretty sure we need to wait for a few things, twrp for the Pixel 3, and Google to release the images.
Click to expand...
Click to collapse
Edit: OP updated
TheUndertaker21 said:
the phone is starting to get to hands on people
it's not like samsung where we can make twrp and root without the device
we need to get images and do testing too
Click to expand...
Click to collapse
Edit: OP updated.
I'm curious what the new Titan security chip will do for rooting and custom rooms. Sounds like something that if done right it can be flashed, but it could present a roadblock depending on how it was implemented.
Images are up.
Sent from my taimen using XDA Labs
---------- Post added at 08:01 PM ---------- Previous post was at 07:12 PM ----------
Current boot patch doesn't work. John will have his phone today.
https://twitter.com/topjohnwu/status/1052993970303889418
Sent from my taimen using XDA Labs
I found this out the hard way
Thought I bricked my phone; black screen. Finally after holding down the power button for a second it said boot incompatible or something in the bootloader. There was a new message I hadn't seen before on a Pixel bootloader. (It also says "button combo" in that message area if you use the buttons to get to bootloader.)
Current boot patch doesn't work.
Click to expand...
Click to collapse
No luck here. I patched the boot img with magisk and it fails to boot. @topjohnwu Please save us. I'll test if needed. I flashed back to stock boot and am good to go.
Factory images are up
Thanks for giving it a try,,,was hoping it would work but I doubted it. Hopefully Magisk can be updated for root! If not, this is going back,,,not enough of a worthy upgrade esp if root is not possible.
northmendo said:
No luck here. I patched the boot img with magisk and it fails to boot. @topjohnwu Please save us. I'll test if needed. I flashed back to stock boot and am good to go.
Click to expand...
Click to collapse
I think I can still cancel my order but I''m hopeful it wont come to that.
Archangel said:
Thanks for giving it a try,,,was hoping it would work but I doubted it. Hopefully Magisk can be updated for root! If not, this is going back,,,not enough of a worthy upgrade esp if root is not possible.
Click to expand...
Click to collapse
Root will come. Give it time
Same tried patching boot.img, fails to boot. Reflashing stock boot.img fixes it. Never really looked at the sizes before, but the patched_boot.img is roughly half the size of the stock boot.img
I am starting this thread for us users and experiences while using Android Q. What works, what doesn't. I am not a dev. I am a user. Not here to bash anyone if something doesn't work. @topjohnwu just got root released for this last night.
So one thing I found which I am sure will fixed soon is
SD MAID not working.
Afwall is working.
Systemui tuner working
Button mapper working
I am sure as we go on and they will all work great. But like I said this is just a post what you found thread. If something does work, post it. If something doesn't, post it. Even if someone needs something like an apk. Ask and shall receive. This is a time of helping each other. Not flaming and bashing. Thank you to everyone that has read this and thank you to all the great devs out there and thank you to us users that can exchange information peacefully.
Is it still not possible to write to /system?
w0rdie said:
Is it still not possible to write to /system?
Click to expand...
Click to collapse
Same here. I would think the File Explorer devs would have to update to support Q?
Quickswitch is not working, back button did not work for me with it installed
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
I am using a custom kernel so I didn't try to root the stock boot image. But it seems other people are rooting the stock boot image. I would hope they can help you. If I get around to it, I will try and root the stock boot image to see if it works. Someone should be able to help. Custom kernel roots just fine
kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
Make sure you are flashing the patched boot image to both slots.
Sent from my Pixel 3 XL
Eudeferrer said:
Make sure you are flashing the patched boot image to both slots.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
I ran fastboot flash boot_b magisk_patched.img
then
fastboot flash boot_a magisk_patched.img
Same issue still bootloops.
Thanks.
Kevin
so im guessing custom kernels are a no no?
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
kevdog98 said:
I ran fastboot flash boot_b magisk_patched.img
then
fastboot flash boot_a magisk_patched.img
Same issue still bootloops.
Thanks.
Kevin
Click to expand...
Click to collapse
I ran into the same issue... it started bootlooping, so I flashed dp4 from scratch and then skipped setup, grabbed the boot.img from the dp4 folder on pc, put it on my phone, installed the newest app.release from canary builds and patched it..... rebooted to bootloader and flashed the boot.img in both slots and rebooted .. it worked
i42o said:
so im guessing custom kernels are a no no?
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
I ran into the same issue... it started bootlooping, so I flashed dp4 from scratch and then skipped setup, grabbed the boot.img from the dp4 folder on pc, put it on my phone, installed the newest app.release from canary builds and patched it..... rebooted to bootloader and flashed the boot.img in both slots and rebooted .. it worked
Click to expand...
Click to collapse
Custom kernel. Singular is a go. That's what I'm running. I didn't have to flash both slots. That doesn't make sense at all. I am going to get my lazy ass off the veranda and flash the rooted boot image.
Edit: I have Pie in my inactive slot and QBeta 4 in my active slot. If that makes any sense to you guys?
What's the problem? Flashed to active slot only.
Your doing something wrong if you can't root the stock boot image
When I originally rooted Q I did it ota patch inactive slot. Bootlooped. I just went to factory recovery and wiped data. Has worked ever since. I believe mine was looping to modules not being compatible with Q yet. Also if you grab the Q image and pull the boot image. You can patch it that way too. With Q, it is finicky with apps because of isolated storage. Which is weird because zarchiver still sees all files but amaze only sees root directory. Files app I noticed is saying some files I have are folders and not disk images. Zarchiver says it right still. Fastboot -w to manually remove all data too. Sometimes Titan m drive can cause weird things that is why I go to stock recovery and wipe it that way, wipes the Titan m drive too.
Did anybody already try to flash ainur sound mod and can report if it's working? For me the main reason to unlock bootloader again and start root procedure on Q...
kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
Same problem here. Already posted the issue at the Magisk thread.
alex1301 said:
Same problem here. Already posted the issue at the Magisk thread.
Click to expand...
Click to collapse
Very strange. Are you guys on the MM Canary channel?
Magisk Manager 228
Magisk Canary 19304
Golf c said:
Very strange. Are you guys on the MM Canary channel?
Magisk Manager 228
Magisk Canary 19304
Click to expand...
Click to collapse
Yeah, updated everyhting before getting started.
alex1301 said:
Yeah, updated everyhting before getting started.
Click to expand...
Click to collapse
Do you have any modules for magisk on your phone? Almost none work at the moment. They are working to get them up and running. Also old data can cause bootloops. Did you leave the Preserve AVB unchecked? If you have Q up and running, check that you are getting the latest magisk zip when patching too.
S8rooted&tooted said:
Do you have any modules for magisk on your phone? Almost none work at the moment. They are working to get them up and running. Also old data can cause bootloops. Did you leave the Preserve AVB unchecked? If you have Q up and running, check that you are getting the latest magisk zip when patching too.
Click to expand...
Click to collapse
Nothing left. My Pixel had never any modules activated or anything else. What is preserve AVB?
Used the latest files.
alex1301 said:
Nothing left. My Pixel had never any modules activated or anything else. What is preserve AVB?
Used the latest files.
Click to expand...
Click to collapse
Click on advanced settings. And make sure when you did patch it, it wasn't checked. It should not be now with 10. With pie it is. Q will not work with it checked. It will double check system to the other partition. And the slot with magisk doesn't match the untouched slot.
*****I am not responsible for anything you do to your device. Do this at own risk***** If all goes bad just flash Factory firmware with PIT file.
Credit goes to those who built twrp.img and the vbmeta image for the A30/A70. I am no dev, I read somewhere about the crossflash to DS firmware but cannot find it any more.
This is for people who understand Odin and have some experience flashing firmware.
Maybe someone will make noob friendly instructions, please feel free.
I currently have an a205u with an unlocked bootloader root and twrp.
1. Using Patched odin crossflash to DS firmware. OEM toggle-download mode-unlock bootloader.
2. You are now able to flash back to the W/U firmware keeping an unlocked Bootloader even though you will not see an oem toggle in developer options
3. Patch boot with magisk 8.02 compress it to tar file along with A30 vbmeta.
***** Important***** make sure to use 7zZ for all steps, and rename boot from magisk_patched_image to boot.img or you will receive errors.
( I may have used a70 vbmeta as I was trying various ideas someone will have to try this and let us know) It will hang at samsung logo for a while on first boot.
4. Then flash A30 TWRP using flashify. Probably works with odin too. Boot to recovery- Perform format data, reboot recovery, flash dmverity+magisk. May be able to get it to work in less steps that's just what I did to make it work.
Link containing vbmeta , magisk patched boot Patched odin . Bootloader 4
First time flashing I got a pass in Odin and fail on phone Flash the second time everything was good
https://drive.google.com/file/d/1F_Bjv8YzPqJLk4YqbXLjYamlPgIZ3nGN/view?usp=drivesdk
Drop that DS firmware.
Johnmoerike said:
*****I am not responsible for anything you do to your device. Do this at own risk***** If all goes bad just flash Factory firmware with PIT file.
Credit goes to those who built twrp.img and the vbmeta image for the A30/A70. I am no dev, I read somewhere about the crossflash to DS firmware but cannot find it any more.
This is for people who understand Odin and have some experience flashing firmware.
Maybe someone will make noob friendly instructions, please feel free.
I currently have an a205u with an unlocked bootloader root and twrp.
1. Using Patched odin crossflash to DS firmware. OEM toggle-download mode-unlock bootloader.
2. You are now able to flash back to the W/U firmware keeping an unlocked Bootloader even though you will not see an oem toggle in developer options
3. Patch boot with magisk 8.02 compress it to tar file along with A30 vbmeta.
***** Important***** make sure to use 7zZ for all steps, and rename boot from magisk_patched_image to boot.img or you will receive errors.
( I may have used a70 vbmeta as I was trying various ideas someone will have to try this and let us know) It will hang at samsung logo for a while on first boot.
4. Then flash A30 TWRP using flashify. Probably works with odin too. Boot to recovery- Perform format data, reboot recovery, flash dmverity+magisk. May be able to get it to work in less steps that's just what I did to make it work.
Click to expand...
Click to collapse
You have the only A205U in existence that is rooted.
Congratulations
Could you please change the title to A205U so others can find it
https://linksharing.samsungcloud.com/jQ6RcTYUMPxR
ninjasinabag said:
Drop that DS firmware.
Click to expand...
Click to collapse
I do not have the DS firmware, I did the unlock months ago then proceeded to break my phone screen. I just replaced it and came to xda to find custom roms. Thought this method would have been old news. Try flashing F firmware as they are identical processors. LINK TO PROOF ABOVE
physwizz said:
You have the only A205U in existence that is rooted.
Congratulations
Could you please change the title to A205U so others can find it
Click to expand...
Click to collapse
So you know what he means by ds firmware?
ninjasinabag said:
So you know what he means by ds firmware?
Click to expand...
Click to collapse
No.
I will try yo find out
DS could mean Dual Sim in firmware , Like mine is and SM-A205F/DS.
It is dual sim. @physwizz @ninjasinabag
physwizz said:
No.
I will try yo find out
Click to expand...
Click to collapse
So far it seems DS refers to the singapore version of a couple Samsung phones.
The a205FN would be the closest version in that regard and it's got a recent version of Android.
I'll give it a flash and see.
---------- Post added at 01:55 AM ---------- Previous post was at 01:42 AM ----------
KineSight said:
DS could mean Dual Sim in firmware , Like mine is and SM-A205F/DS.
It is dual sim. @physwizz @ninjasinabag
Click to expand...
Click to collapse
That's exactly what it means and I love you for pointing this out.
The singapore firmware on the F is universally unlocked.
ninjasinabag said:
So far it seems DS refers to the singapore version of a couple Samsung phones.
The a205FN would be the closest version in that regard and it's got a recent version of Android.
I'll give it a flash and see.
---------- Post added at 01:55 AM ---------- Previous post was at 01:42 AM ----------
That's exactly what it means and I love you for pointing this out.
The singapore firmware on the F is universally unlocked.
Click to expand...
Click to collapse
Awesome, glad I could be of help. @ninjasinabag
ninjasinabag said:
So far it seems DS refers to the singapore version of a couple Samsung phones.
The a205FN would be the closest version in that regard and it's got a recent version of Android.
I'll give it a flash and see.
---------- Post added at 01:55 AM ---------- Previous post was at 01:42 AM ----------
That's exactly what it means and I love you for pointing this out.
The singapore firmware on the F is universally unlocked.
Click to expand...
Click to collapse
So you're going to do it?
physwizz said:
So you're going to do it?
Click to expand...
Click to collapse
Yeah, I've downloaded a couple of firmwares with unlocked bootloaders. Gonna try out a couple and see if they stick.
Hit a few errors tonight trying out different versions of odin, so I'll try more tomorrow/today
ninjasinabag said:
Yeah, I've downloaded a couple of firmwares with unlocked bootloaders. Gonna try out a couple and see if they stick.
Hit a few errors tonight trying out different versions of odin, so I'll try more tomorrow/today
Click to expand...
Click to collapse
Good Luck
Re:
Omg I've been waiting almost 2 years for this metropcs a205U to be rooted can you please PM me if mine can be rooted and sent me the Odin and combination firmware so I can root mine to PLEASE bro this phone is complete ass with so many Samsung restrictions please let this be real!!
your instructions are completely vauge with no links and no clarification between which vbmeta to flash and your picture shows your on A205W VLU 4BTE3 which is a Canada variant of the phone..gah this is just too complicated for me can someone please reiterate with a proper guide to root a205U (metropcs)
Johnmoerike said:
https://linksharing.samsungcloud.com/jQ6RcTYUMPxR
I do not have the DS firmware, I did the unlock months ago then proceeded to break my phone screen. I just replaced it and came to xda to find custom roms. Thought this method would have been old news. Try flashing F firmware as they are identical processors. LINK TO PROOF ABOVE
Click to expand...
Click to collapse
Can you please post odin, vbmeta, patched boot.img ?
physwizz said:
Can you please post odin, vbmeta, patched boot.img ?
Click to expand...
Click to collapse
Its added to the first post, sorry I would wasn't able to be more clear. I unlocked the bootloader couple months ago, not realizing that I was the only one to have done so. If I can be of any more help let me know
Johnmoerike said:
Its added to the first post, sorry I would wasn't able to be more clear. I unlocked the bootloader couple months ago, not realizing that I was the only one to have done so. If I can be of any more help let me know
Click to expand...
Click to collapse
Thanks.
There are a lot of people who are waiting to root their a205U.
---------- Post added at 11:39 PM ---------- Previous post was at 11:21 PM ----------
ninjasinabag said:
Yeah, I've downloaded a couple of firmwares with unlocked bootloaders. Gonna try out a couple and see if they stick.
Hit a few errors tonight trying out different versions of odin, so I'll try more tomorrow/today
Click to expand...
Click to collapse
Tar and odin in post 1
The firmware I downloaded was a205fn. That's the answer let me know how it goes
Johnmoerike said:
The firmware I downloaded was a205fn. That's the answer let me know how it goes
Click to expand...
Click to collapse
Thanks
physwizz said:
Thanks
Click to expand...
Click to collapse
Any progress in the a205u root?