Related
So, I wiped all data, system, cache, internal storage using TWRP and then I flash the system.img to System Image and boot.img to Boot into 2 slots (A & B). Consequently, I lose TWRP and root. I have gone back to May Security Patch Nokia 8 TA-1004. I have updated and updated up until October 2018 Patch.
Then, I tried to use "fastboot boot twrp.img", however it doesn't work. It is just stuck to POWERED BY ANDROID LOGO. Flashing twrp will break the wifi and I do not want that. Anybody has solutions for this? I can't get it to boot to TWRP. I use Android stock recovery and apply update in SD Card, not working as well.
I really want to have access root. All because of that stupid random restart occurs in this thread https://forum.xda-developers.com/nokia-8/help/nokia-8-sudden-restart-occurred-randomly-t3852357
Note: During flashing system.img which reverts back to stock one, I didn't use fastboot command. I use TWRP to revert back.
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
Is this the latest stock boot image (october patch)?
For resolve a lower security than september can't boot to twrp try this method.
Boot to download mode. Then Use command.
Fastboot reboot bootloader => for enter again download mode
Fastboot boot twrp.... It will go to twrp well.
Topogigi said:
Is this the latest stock boot image (october patch)?
Click to expand...
Click to collapse
Um I think cuz Magisk took this backup right during the Install to Second Slot option
ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
This is October patch? If it does, you are a lifesaver.
ValKyre said:
For resolve a lower security than september can't boot to twrp try this method.
Boot to download mode. Then Use command.
Fastboot boot bootloader => for enter again download mode
Fastboot boot twrp.... It will go to twrp well.
Click to expand...
Click to collapse
YOU SIR, ARE ROCK. This is very much working for me. I can boot already to twrp. No longer stuck in POWERED BY ANDROID LOGO.
Although you have mistyped the command. It should be "fastboot reboot bootloader". Anyway, thank you. I have given my thanks to you.
godofknife said:
This is October patch? If it does, you are a lifesaver.
YOU SIR, ARE ROCK. This is very much working for me. I can boot already to twrp. No longer stuck in POWERED BY ANDROID LOGO.
Although you have mistyped the command. It should be "fastboot reboot bootloader". Anyway, thank you. I have given my thanks to you.
Click to expand...
Click to collapse
Yup ... Sorry with my head not remember true command hehe
ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
Click to expand...
Click to collapse
So can i use this img to root with Magisk with patch boot image option? Is this October patch?
Edit: Stuck on Powered by Android logo => not October boot img
Mo4o293 said:
So can i use this img to root with Magisk with patch boot image option? Is this October patch?
Edit: Stuck on Powered by Android logo => not October boot img
Click to expand...
Click to collapse
My bad I guess
ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
I wonder if some kind soul can offer some wisdom, I unlocked my bootloader and flashed twrp. All fine so far.
I then upgraded to Pie.
I then flashed Magisk.
I was getting some strange Magisk behaviour so uninstalled it but for some reason it did'nt restore stock boot and Play Store was misbehaving.
I then flashed this boot image ^^ and yes, very stupidly, I now have no wifi (my MAC address is screwed).
I can boot to OS but I have no File Manager, nor root and I don't really know what to try from here.
I cant get to recovery (twrp or stock), it just get stuck on the Powered by Android logo.
I have debugging enabled but adb just reports my device as offline.
I cant get in to fastboot mode either.
Really appreciate some help from a kind soul
Ta
Hello i unlocked bootloader and after working so hard i finally booted twrp img to my nokia 8 and from there i cant access to twrp it always opens stock recovery.pls help me.....
I tried 2 to 3 times but i cant access twrp the process was successful but cant access it
I would say if it does not boot to it, its not there. Just flash twrp again. Use the latest from their website to do it.
Hi Guys
UPDATE 2: (2/11/2019) Boot img now patched to Magisk V20.1 and added Google Drive as a mirror
UPDATE: It has come to my attention that some users are having issues with this version, please note this is still in beta and root isn't fully supported yet, also please make sure your running the latest magisk manager (version 7.3.5 at the time of this update) BEFORE flashing the patched boot IMG, those currently having issues, try flashing the stock IMG provided and installing the latest magisk manager then flashing the patched IMG
here is a working magisk patched boot img for you guys wanting root on your new android 10 open beta 1 software.
PLEASE BE AWARE THIS DOESNT COME WITH TWRP, THIS MAY ALSO BREAK THE ORIGINAL STOCK RECOVERY, BY FLASHING THIS BOOT IMG, YOU TAKE FULL RESPONSIBILITY FOR YOUR DEVICE AND NEITHER I OR XDA WILL BE HELD RESPONSIBLE
this DOESNT contain TWRP but is just rooted with magisk v20.0
simply flash the provided file in fastboot with the following command
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
Please note this will ONLY work with the OnePlus 6T
i have also provided the stock android 10 boot img in case anything goes wrong
DOWNLOADS::
[CURRENT VERSION - Magisk V20.1]
Mega -> https://mega.nz/#!YI5BkICC!66fiUUdmg1EgGcTNExHZ52IoliVY4HBMBdwxErpI-co
Google Drive -> https://drive.google.com/file/d/1xyRPzsKh1kQXK0_RpdnesuR85vc6FvRf/view?usp=sharing
[OLD Versions]
[Magisk V20.0]
https://mega.nz/#!cQRFwA7b!R1yLz1ozFUTEOLXv-OREK-oF5YeUGN1PrWvSSh22vHw
Stock Boot img
https://mega.nz/#!1BAnRCoK!nu6UVAnR2yHnbaf54FEhc7U_3oEyP1q2BFMU0LK7XC4
Credits:
@oneplus for the phone and stock boot image
@topjohnwu for magisk and his boot image patcher
Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.
Do i need a computer for this ?
techlogik said:
Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.
Click to expand...
Click to collapse
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
charlie95113 said:
Do i need a computer for this ?
Click to expand...
Click to collapse
yes because fastboot command is needed, henced done using pc.
mywebslave said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Click to expand...
Click to collapse
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I also used the payload extractor and took the stock boot.img and patched it with Magisk myself. Same issue. So obviously Magisk just doesn't suppor this phone yet and Devs need to work on it.
Thx
techlogik said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I tried patching the stock boot.img myself as well, it ends up being the exact same size as the TS for this method...same problem.
Thx
Click to expand...
Click to collapse
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.
mywebslave said:
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.
Click to expand...
Click to collapse
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks
techlogik said:
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks
Click to expand...
Click to collapse
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
So should we be using this instead?
Sent from my ONEPLUS A6013 using Tapatalk
mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine
zhenliang1102 said:
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine
Click to expand...
Click to collapse
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot
when i flash the magisk_patched.img and my cellphone reboot my cellphone does not recognize my simcard and have no network, am back on the stock boot.img
cultofluna said:
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot
Click to expand...
Click to collapse
I doubt this would work because the patched image is only 26mb while the stock boot image is 64mb. Someone mentioned this in the OB thread
Black screen after the update
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.
Hy, do you have proximity sensor problem after update?! Thanks...is anything i can do?
jack5225 said:
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.
Click to expand...
Click to collapse
Same happened to me
Phone boots to a Black screen
adb reboot bootloader -> works
fastboot flash boot boot.img -> works
Only Patched boot.img -> boots to black screen
Sent from my ONEPLUS A6010 using Tapatalk
Same for me. Softbrick and phone doesn't boot. It also encrypted my whole /data with diferent password i think and I had to wipe whole /data partition. System boots after wiping data storage but as soon as I install magisk it doesn't want to boot again. I guess I will wait for final image and TWRP support.
i couldnt flash it manually (via cmd), but all in one tool managed it well.
worked fine and quick,thank you
Crazy that some phones it is working and others it doesn't. Nothing we are doing wrong, OP has work to do still. I can imagine this official update to Q is going to cause a support fiasco...if you want to root that is. ROFL. All works fine with stock though upgrade. Understand it is Beta, but they claim a November official release
We are going to need some Dev help. Or going to need to sell this phone and upgrade to the 7t or Pro..haha
Pre rooted boot image with TWRP included for OOS11 Beta 2, OB2. This is not for the beta 1 hotfix. Flash in fastboot if not rooted, and through a kernel manager if you are already on beta 2 and rooted but don't have TWRP because flashing kept putting you in crash dump mode. Remove lock screen as a precaution before flash. No need to wipe anything.
Just like any other image I tried, this gets me into a boot loop on the spinning circle. I can get into twrp, but the magisk root seems to be breaking something. Any ideas?
romanuks said:
Just like any other image I tried, this gets me into a boot loop on the spinning circle. I can get into twrp, but the magisk root seems to be breaking something. Any ideas?
Click to expand...
Click to collapse
What device are you using ( 6 or 6T ) ? Or whats the code name for your device??
SOK seila said:
What device are you using ( 6 or 6T ) ? Or whats the code name for your device??
Click to expand...
Click to collapse
OP6T europe
i use command "fastboot boot fajita-ob2-oos11-twrp-rooted.img" but in boot to system
lockmunk said:
i use command "fastboot boot fajita-ob2-oos11-twrp-rooted.img" but in boot to system
Click to expand...
Click to collapse
you should probably write fastboot flash boot ...
romanuks said:
you should probably write fastboot flash boot ...
Click to expand...
Click to collapse
"fastboot boot" and "fastboot flash" are do the same thing (to flash). If you use "fastboot flash" you have to manually reboot the phone to system or twrp, it is auto reboot after finished flash (based on image if flash TWRP it will boot to TWRP) if you use "fastboot boot".
Sooooo, any ideas on what I could do?
romanuks said:
Sooooo, any ideas on what I could do?
Click to expand...
Click to collapse
So you are using op6T-EU. I don't know if eu image different from groble image or not but you can try to patch boot image yourself.
Well, I already tried that too, so really not a clue as to why it wouldnt work... Probably should just downgrade, backup and get lineage or so
I've tried multiple times, but keep hitting errors...I'm not super familiar with building TWRP from source, but I'm hoping someone here could possibly help out and put together an unofficial twrp for barbet?
having a working unofficial twrp for this device would be a definite plus.
So I'm guessing it's fair to say that this claim is fake then, right?
There is an official version for the 5 now. So it should be possible.
MrPolite said:
There is an official version for the 5 now. So it should be possible.
Click to expand...
Click to collapse
I wonder if the pixel 5 version is compatible with pixel 5a.
I've tried multiple times, but keep hitting errors.
we need the wizard @Captain_Throwback to make an unofficial twrp. he's made a lot of unofficial twrps over the years and does a damn good job at doing it.
rchris494 said:
we need the wizard @Captain_Throwback to make an unofficial twrp. he's made a lot of unofficial twrps over the years and does a damn good job at doing it.
Click to expand...
Click to collapse
Unless someone buys me one, I won't be doing that. I don't build for devices I don't have anymore, unless they're essentially similar to a device that I do. And this device doesn't fit that scenario. I'm sure at some point a dev will come along to help. You'll just all have to be patient.
saibotnoob said:
So I'm guessing it's fair to say that this claim is fake then, right?
Click to expand...
Click to collapse
Yep. I think all they do is copypasta other tutorials and make money with ad revenue.
I tried to build it, but I ran into issues. anyone have any idea the proper repos I'm supposed to use? also, when getting to the blobs point, extractblobs script is missing from lineage repos. (I also tried to build for android 12
Point me in the right direction!
eriklion said:
I tried to build it, but I ran into issues. anyone have any idea the proper repos I'm supposed to use? also, when getting to the blobs point, extractblobs script is missing from lineage repos. (I also tried to build for android 12
Point me in the right direction!
Click to expand...
Click to collapse
You should use the official Google device repo for A11, along with the minimal manifest for TWRP. Then just follow the same process as the bonito repo to retrofit it for TWRP.
The easiest way to extract blobs is to do so from the factory images.
EDIT: If I can find some time I may help with this, as long as you're willing to do the building and testing, I can probably create a mostly complete device tree for you to start with.
Someone want to see if this TWRP boots?
twrp-3.6.0_11-0_CPTB-20211220-01-barbet.img
drive.google.com
No idea if it'll boot or if touch or vibration will work or anything, but it's a first attempt.
Captain_Throwback said:
Someone want to see if this TWRP boots?
twrp-3.6.0_11-0_CPTB-20211220-01-barbet.img
drive.google.com
No idea if it'll boot or if touch or vibration will work or anything, but it's a first attempt.
Click to expand...
Click to collapse
Doesn't boot, stuck at Google logo. Just FYI the official twrp-3.6.0_11-0-redfin.img for Pixel 5 boots beyond Google logo and gets stuck at TWRP splash screen with ADB ability... Running A12.
nijel8 said:
Doesn't boot, stuck at Google logo. Just FYI the official twrp-3.6.0_11-0-redfin.img for Pixel 5 boots beyond Google logo and gets stuck at TWRP splash screen with ADB ability...
Click to expand...
Click to collapse
Are you sure it's not booting? Did you confirm that adb isn't working by checking adb devices while on the logo screen?
Captain_Throwback said:
Are you sure it's not booting? Did you confirm that adb isn't working by checking adb devices while on the logo screen?
Click to expand...
Click to collapse
Absolutely sure, stuck at Google logo before getting to TWRP at all so ADB doesn't see any devices.
nijel8 said:
Absolutely sure, stuck at Google logo before getting to TWRP at all so ADB doesn't see any devices.
Click to expand...
Click to collapse
Can you get a recovery log and logcat from the redfin build so I can see why that one isn't working? If that boots then it may be relatively easy to get it working on this device. That's probably the best place to start.
Captain_Throwback said:
Can you get a recovery log and logcat from the redfin build so I can see why that one isn't working? If that boots then it may be relatively easy to get it working on this device. That's probably the best place to start.
Click to expand...
Click to collapse
Sure...
Just booted into official twrp for Pixel 5 with no issue
Edit: magisk rooted, android 11
More editing as I am testing:
The first thing I tried to do was boot into fastboot through TWRP. It goes back to TWRP screen and then back to TWRP, never entering any fastboot.
Okay, I did not plan this out well at all lol.
Just Completed Factory Flash to Android 11 through the Android Flash Tool
Booted into Pixel 5 TWRP
Did not get an 'Allow Modifications Pop Up.
Tried to run fastboot through TWRP and TWRP when back to its logo and than returned to the menu.
SolGonNet said:
Just booted into official twrp for Pixel 5 with no issue
Edit: magisk rooted, android 11
More editing as I am testing:
The first thing I tried to do was boot into fastboot through TWRP. It goes back to TWRP screen and then back to TWRP, never entering any fastboot.
Okay, I did not plan this out well at all lol.
Just Completed Factory Flash to Android 11 through the Android Flash Tool
Booted into Pixel 5 TWRP
Did not get an 'Allow Modifications Pop Up.
Tried to run fastboot through TWRP and TWRP when back to its logo and than returned to the menu.
Click to expand...
Click to collapse
Did you manage to flash something with twrp?
I have interest in this process as well. I see that Magisk recommends TWRP to install, and it seems that may be require for SafetyNet verification. I am fairly unclear on that point though: is TWRP the only reasonable way to use magisk? And, also, does a custom ROM not automatically provide a user with root access? Why is Magisk needed in that case?
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Hey,
If you've only booted the image, then you only need to reboot and the image is lost, the only way that it would be permanent is if it was flashed: fastboot flash not: fastboot boot.
Usually what happens is when you obtain a firmware to install or in your case change region, and you wish to root this firmware you would extract payload.bin then use fastboot enhance to extract the boot.img
Then copy to your phone and patch it with the latest stable Magisk (in this case 24.3)
So again, if you've only booted the image then just reboot your phone and it'll turn on using the actual flashed boot.img from the firmware, not the one you booted.
If that doesn't work then you must have flashed it. In which case you can either re-flash your original boot.img or boot then direct install a correctly patched image for the correct firmware (after a success boot) via Magisk.
leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Here's a good "how to" to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/
Canuck Knarf said:
Here's a good how to to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/
Click to expand...
Click to collapse
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse
dladz said:
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse
Click to expand...
Click to collapse
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk
Canuck Knarf said:
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk
Click to expand...
Click to collapse
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
If what he's advised is true then he's successfully changed OS/region and now wants to root, the only thing he's done thus far is to boot a boot image. I think he's flashed it as booting is not permanent, to suggest to go ahead and attempt to obtain a color OS boot image or vendor image is absolutely ridiculous.
He's on an EU firmware. So he requires an EU boot image.
He's in boot loop cause he is booting to A slot...
Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode
dladz said:
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
Click to expand...
Click to collapse
oxygen OS using the firmware EU 11_A.12.... He still needs boot img ...vender_boot form the firmware EU 11_A.12 . to root
leofung_wai said:
Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode
Click to expand...
Click to collapse
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance
He already had boot?? What are you talking about???
He had a functional OS, in order to root you only need ONE image.
The boot image which comes from OOS. The link you sent is for Color OS?? Make sense now ??
He just needs to patch it correctly and boot it then direct install.
Im going over this again with someone who's incapable of understanding the basics.
Canuck Knarf said:
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance
Click to expand...
Click to collapse
You do realise that booting an image does not need to be directed don't you?
Only by flashing should you direct the image to a particular slot.
By flashing you are permanently flashing an image.
I don't think you understand this so I'll make it simple for you.
You want to root your phone. You have an image you've just patched, from boot.img to magisk_patched.img
Firstly you would want to send this via fastboot, you do not need fastboot enhance for this.
The preferred way to do this is to fastboot boot magisk_patched.img
Why is this preferred??
Because if it fails as it may. Then you are not stuck in a boot loop, you just reboot and you're back in the OS.
The 2nd method is flashing.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter.
Now although this can work it is not the preferred method because you aren't just booting the image you are flashing it, this means that if it fails you cannot just reboot and get back to the OS you have to either obtain a new boot image and patch it although you cannot do this yourself as your phone no longer boots or you obtain an already patched boot image, again the last one I wouldn't recommend..
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
Ok so if you've got into the system..
You need to follow the instructions I have in my guide in order to get root...
You can use the boot image I have there.
leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
It is always better to patch boot.img of your own version (you can dump it from payload dumper etc.) and then only fastboot boot patched_image.img and then directly install it via Magisk.
Boot this image.
192 MB folder on MEGA
mega.nz
Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally
Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done
leofung_wai said:
Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally
Click to expand...
Click to collapse
If you've patched your own image and booted it then click Magisk then install. Then direct install and you're done..
dladz said:
Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done
Click to expand...
Click to collapse
thanks i success root by your image now
but i had a question, i messed up the slot B and now can only boot through slot A Will it affect anything