Hi friends. Bought my one on *site name*. China version. How to install Magisk root? I tried to boot patched boot.img... didn't help
have you unlock your phone?
AmbazidA said:
have you unlock your phone?
Click to expand...
Click to collapse
Yea
Rezinochka said:
Yea
Click to expand...
Click to collapse
okay, was the flashing of patch boot image not successful? or what error did you find?
AmbazidA said:
okay, was the flashing of patch boot image not successful? or what error did you find?
Click to expand...
Click to collapse
In adb it wrote "OKAY". But in magisk root haven't installed.
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
If for some reason it’s not already installed, install it.
AmbazidA said:
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
Click to expand...
Click to collapse
Sorry, didn't understand wdym
Sirs. With your permission, we will continue tomorrow morning. I am forced to leave you for an indefinite period for the time being.
Ok. Good morning "Vietnam"
AmbazidA said:
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
Click to expand...
Click to collapse
I didn't understand wdym
Is the magisk app currently on your device?
If so, enter it, and clcik on the install button. Then click on”direct install”
Arealhooman said:
Is the magisk app currently on your device?
Click to expand...
Click to collapse
Yes
Arealhooman said:
If so, enter it, and clcik on the install button. Then click on”direct install”
Click to expand...
Click to collapse
I patched boot.img earlier
this video will walk you through rooting the Redmi Note 12
-
Enddo said:
this video will walk you through rooting the Redmi Note 12
-
Click to expand...
Click to collapse
Thx, i will try
Enddo said:
this video will walk you through rooting the Redmi Note 12
-
Click to expand...
Click to collapse
i tried with different versions of rom and magisk. So it doesnt work. And in video he flash patched file to the boot_a. I can flash it only to boot_b
Rezinochka said:
i tried with different versions of rom and magisk. So it doesnt work. And in video he flash patched file to the boot_a. I can flash it only to boot_b
Click to expand...
Click to collapse
it will flash to whatever your current partition is set to. some will be set to the _a partition and others will be set to the _b partition. it all depends on how many OTA updates you have installed (or if you've manually switched partitions for some reason)
the video does work, my Redmi Note 12 is rooted right now
IDK if it will work or not. But at least you could try. Someone suggested to patch init_boot.img on the Redmi note 12 4g forum.
Actual Post
Related
Hi to all
My honor7 was perfectly functional until this night
But i don't know why, when i screen on it asked me a nck code
It's the first time
The phone is unlocked and rooted since 2 years already
I checked the imei, it was incorrect with 15x0
000000000000000
I checked with other sim Card same issue
Any help ?
nmen00vb said:
Hi to all
My honor7 was perfectly functional until this night
But i don't know why, when i screen on it asked me a nck code
It's the first time
The phone is unlocked and rooted since 2 years already
I checked the imei, it was incorrect with 15x0
000000000000000
I checked with other sim Card same issue
Any help ?
Click to expand...
Click to collapse
Did you try factory reset?
Finally It's resolved
Magisk is in fault, I repatched boot image again and it rework
nmen00vb said:
Finally It's resolved
Magisk is in fault, I repatched boot image again and it rework
Click to expand...
Click to collapse
Good to hear.. :good:
Seems like Magisk badly wrote to the boot image... it also asked for me for a NCK code.
ShadixAced said:
Seems like Magisk badly wrote to the boot image... it also asked for me for a NCK code.
Click to expand...
Click to collapse
You too having the same issue??
hassanjavaid8181 said:
You too having the same issue??
Click to expand...
Click to collapse
I've had the same issue, not anymore. I've reflashed Magisk and it works now.
ShadixAced said:
I've had the same issue, not anymore. I've reflashed Magisk and it works now.
Click to expand...
Click to collapse
Ohhk.. Thats good.
ShadixAced said:
I've had the same issue, not anymore. I've reflashed Magisk and it works now.
Click to expand...
Click to collapse
Thank you!
I was facing the same issue after updating to the latest Magisk! so i revert back to ver 15 and ignored all latest update.
Finally - Referring to your method - solving the issue. :good:
Big Thanks!
fiezwan said:
Thank you!
I was facing the same issue after updating to the latest Magisk! so i revert back to ver 15 and ignored all latest update.
Finally - Referring to your method - solving the issue. :good:
Big Thanks!
Click to expand...
Click to collapse
Glad I could help.
Huamei Mediapad M2-803L
ShadixAced said:
Glad I could help.
Click to expand...
Click to collapse
I have the same issue. May I know whether I should:-
(1) flash stock boot.img;
(2) reflash Magisk v16; or
(3) revert back to Magisk v15
I have done (1) and (2) but still need NCK code.
Thank you!
Were you able to get it working again? Also tried all these steps on my mediapad x2 and grabbing for anything that might help. Even tried hcu and dc unlocker but to no avail. Any help appreciated.
Thanks.
to resolve the problem, you must flash twice magisk
when you flash , the log show an error about space, if you have that be sure you will have the issue
if he passed this message you are ok and you dont need to flash the boot again
twlai said:
I have the same issue. May I know whether I should:-
(1) flash stock boot.img;
(2) reflash Magisk v16; or
(3) revert back to Magisk v15
I have done (1) and (2) but still need NCK code.
Thank you!
Click to expand...
Click to collapse
Hello there and sorry for the long-time answer.
Normally you should have only flashed Magisk v16, since the error resides on the framework.
(actually, it is a "ramdisk" error, making it impossible to allocate all the space needed into the ramdisk to be rebuilded, @topjohnwu if you know anything about this )
Dude, thank you so much for writing this down. I have been facing the same problem today. Staying with Magisk 14
Hi. I'm facing the same issue. My imei is 000000000000 and its asking for the NCK code.
I extracted the stock boot image from the rom. flashed it. then installed magisk. patched boot, and flashed patched boot but the problem still persists.
when you say flash magisk twice what do you mean exactly?
thanks!
ShadixAced said:
Hello there and sorry for the long-time answer.
Normally you should have only flashed Magisk v16, since the error resides on the framework.
(actually, it is a "ramdisk" error, making it impossible to allocate all the space needed into the ramdisk to be rebuilded, @topjohnwu if you know anything about this )
Click to expand...
Click to collapse
Flash Magisk from recovery, it seems that it works when done so.
Try this :
1) Flash the stock boot image back
2) Flash Magisk FROM recovery.
Optional : wipe cache and dalvik.
Try again and see.
i dont have a recovery.
should i install twrp? thanks.
ShadixAced said:
Flash Magisk from recovery, it seems that it works when done so.
Try this :
1) Flash the stock boot image back
2) Flash Magisk FROM recovery.
Optional : wipe cache and dalvik.
Try again and see.
Click to expand...
Click to collapse
Yes you can install TWRP. (I do think it's the only one available ?)
This is kind of storytime... I got the application by redeeming a code that was posted as a gift on their fanpage at Facebook. I had to sent them via Telegram the Google play ID order, something that I couldn't find. I explained that and they understood me and said that if I could send the code that I got the application, they are gonna send be the actual files. So I received the files and I'm ready to begin! I don't have much spare time so I'm gonna do this whenever I have the time to do so. Wish me luck! I'm gonna keep you guys updated and let you know what happened.
Andriano24 said:
This is kind of storytime... I got the application by redeeming a code that was posted as a gift on their fanpage at Facebook. I had to sent them via Telegram the Google play ID order, something that I couldn't find. I explained that and they understood me and said that if I could send the code that I got the application, they are gonna send be the actual files. So I received the files and I'm ready to begin! I don't have much spare time so I'm gonna do this whenever I have the time to do so. Wish me luck! I'm gonna keep you guys updated and let you know what happened.
Click to expand...
Click to collapse
knox to 0x0?
DaniPS2002 said:
knox to 0x0?
Click to expand...
Click to collapse
Yeah that's what the app suppose to do
Andriano24 said:
Yeah that's what the app suppose to do
Click to expand...
Click to collapse
the app name is knox reset 0x0 (0)?
DaniPS2002 said:
the app name is knox reset 0x0 (0)?
Click to expand...
Click to collapse
Yes
Okay, let we know!
MarcusBS said:
Okay, let we know!
Click to expand...
Click to collapse
I've stuck in a step. Sadly I cannot complete now the instructions given because I can't turn the systemless root into system mode
Andriano24 said:
I've stuck in a step. Sadly I cannot complete now the instructions given because I can't turn the systemless root into system mode
Click to expand...
Click to collapse
What do you mean you can't turn systemless root into system mode?
ashyx said:
What do you mean you can't turn systemless root into system mode?
Click to expand...
Click to collapse
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
Check that out
Andriano24 said:
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
Check that out
Click to expand...
Click to collapse
I actually meant what is preventing you from installing supersu in system mode, it's simple enough? Also which device is this?
ashyx said:
I actually meant what is preventing you from installing supersu in system mode, it's simple enough? Also which device is this?
Click to expand...
Click to collapse
I flash the super su, then try to full unroot, my phone reboots and I press the combination of keys to go to twrp recovery, go to terminal thingy, type the code and the last step I do is flashing again the supersu. But then I boot into system I stuck on the logo screen
Andriano24 said:
I flash the super su, then try to full unroot, my phone reboots and I press the combination of keys to go to twrp recovery, go to terminal thingy, type the code and the last step I do is flashing again the supersu. But then I boot into system I stuck on the logo screen
Click to expand...
Click to collapse
You've lost me Tbh. I don't understand what steps you are performing and why.
Type what code?
ashyx said:
You've lost me Tbh. I don't understand what steps you are performing and why.
Type what code?
Click to expand...
Click to collapse
Didn't you see the post I send you? The "code" is
Echo SYSTEMLESS=false > /data/.supersu
Andriano24 said:
Didn't you see the post I send you? The "code" is
Echo SYSTEMLESS=false > /data/.supersu
Click to expand...
Click to collapse
OK first things first. You have to reinstall SuperSu for that code to work AND a patched boot.img.
Second for what reason do you need SuperSU to be in system mode?
[Deleted by me]
ashyx said:
OK first things first. You have to reinstall SuperSu for that code to work AND a patched boot.img.
Second for what reason do you need SuperSU to be in system mode?
Click to expand...
Click to collapse
Thank you for your time. But can you wrote the full steps below? Because I'm tired of getting into a bootloop only because I am not able to understand the instructions! You can do it only of you want to!
Secondary, the Knox Reset app has a plugin to make the success rate bigger of turning the 0x1 back to 0x0 (as far as I know) and the plugin needs system mode root :/
Lol right now I'm not rooted because I'm tired of the bootloops while rying to system mode root
Andriano24 said:
Lol right now I'm not rooted because I'm tired of the bootloops while rying to system mode root
Click to expand...
Click to collapse
Easiest way is to reroot systemless. After rooting back up the boot partition with TWRP.
Unroot then install SuperSU in system mode.
Finally restore the boot.img from the backup.
Reboot.
Note also be aware that system mode root is hit and miss on devices running nougat.
You still haven't stated which device?
ashyx said:
Easiest way is to reroot systemless. After rooting back up the boot partition with TWRP.
Unroot then install SuperSU in system mode.
Finally restore the boot.img from the backup.
Reboot.
Note also be aware that system mode root is hit and miss on devices running nougat.
You still haven't stated which device?
Click to expand...
Click to collapse
Oh sorry I forgot about that! I have the Samsung galaxy A5 2017 running...... nougat.....
Andriano24 said:
Oh sorry I forgot about that! I have the Samsung galaxy A5 2017 running...... nougat.....
Click to expand...
Click to collapse
Then you have a 50/50 chance of root working in system mode.
Also tbh I think this knox app is fake or it just fakes knox to 0x0 the same way Magisk can.
It's up and here https://developers.google.com/android/ota
gm007 said:
It's up and here https://developers.google.com/android/ota
Click to expand...
Click to collapse
Changelog?
Sent from my Pixel 3 using Tapatalk
nickporwal said:
Changelog?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2018-12-01.html
One of this days the 'Check for Update' button will work damn it! Hahahaha
Hahaha right, I have been flashing the OTA manually, its no biggie for me I am used to manually flashing the ota now
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
I got it through ota 1 hour ago.
gm007 said:
I got it through ota 1 hour ago.
Click to expand...
Click to collapse
You know Im mashing the button, lol. Only google phone that got all the updates pretty much same day was the Nexus 6P, I used to get the update notification even before any site would announce that it was out
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Do you have the Magisk uninstaller on your phone? Run it from the temp TWRP .img, and then it should boot OK. Go back to temp TWRP, and install Magisk again. The Edge Sense Plus module is broken again. Don not reinstall it until fixed.
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Flash all after removing the -w, rebooted and let it finish. Boot to TWRP and installed the latest canary. Did not install TWRP.
All good.
jd1639 said:
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ah figured it out, edge sense broken.
edit- thanks guys~
sulpher said:
Ah figured it out, edge sense broken.
Click to expand...
Click to collapse
There's no magic. I sideload the ota in the stock recovery. Booted into the system to make sure everything worked. Powered off the device and booted into the bootloader. Then booted twrp and flashed magisk. Then booted into the system. That's it.
Sent from my [device_name] using XDA-Developers Legacy app
No OTA here... It usually comes days later with unlocked Google pixel using TMobile. -.-
Installed the full version to update it, root just after and everything's fine!
There is only the edge sense that is'nt working as already told
TWRP keeps getting error 1 when flashing the OTA, bit odd
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
laill said:
TWRP keeps getting error 1 when flashing the OTA, bit odd
Click to expand...
Click to collapse
Archangel said:
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
Click to expand...
Click to collapse
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
What I do is download the full updated firmware, unzip that in your platform tools folder,,,make sure you also unzip the second zip inside there as well. If you have the Pixel edge module installed uninstall it and I also uninstalled Magisk in TWRP before I updated just in case there were any problems. Then find the flash-all.bat file in your platform tools folder, right click on it, open with notepad+ and find the -w at the bottom and delete it. After this, save the flash-all.bat notepad xml file and do not just close it. You can then flash the full firmware without it deleting your user data. After this you will have to fastboot boot TWRP and flash the TWRP zip over again. I rebooted then used TWRP to flash the Magisk 17.1 zip. I am up and running and did the same thing last month for the Nov update,,,hope this helps.
Rumsfield said:
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
Click to expand...
Click to collapse
<removed>
I think Moto Moto don't like us
Command should be "dd if=/dev/block/mmcblk0p40 of=/external_sd/boot.img" then, and don't forget to mount micro sd in twrp first.
Ofc it works fine to execute command from adb shell when booted to twrp, which makes it a bit easier to type.
When I try to boot from patched image, phone is stuck on 'Android One' logo.
I'm on firmware version OPENEU_9.0_PPK29.68-16-21. I guess this firmware version isn't rootable .
Well, I'll wait for some custom ROM to enjoy rooted phone (maybe that Ressurection Remix ROM which was announced few days ago) .
gregory678 said:
When I try to boot from patched image, phone is stuck on 'Android One' logo.
I'm on firmware version OPENEU_9.0_PPK29.68-16-21. I guess this firmware version isn't rootable .
Well, I'll wait for some custom ROM to enjoy rooted phone (maybe that Ressurection Remix ROM which was announced few days ago) .
Click to expand...
Click to collapse
Propably you patch wrong boot image, try to extract from your device stock
tys0n said:
Command should be "dd if=/dev/block/mmcblk0p40 of=/external_sd/boot.img" then, and don't forget to mount micro sd in twrp first.
Ofc it works fine to execute command from adb shell when booted to twrp, which makes it a bit easier to type.
Click to expand...
Click to collapse
It's not universal path so i BOLD the path to change
[email protected] said:
It's not universal path so i BOLD the path to change
Click to expand...
Click to collapse
That's understood, but if you're booted to twrp, then "of=/external_sd/boot.img"" is pretty much your only option since internal is encrypted.
tys0n said:
That's understood, but if you're booted to twrp, then "of=/external_sd/boot.img"" is pretty much your only option since internal is encrypted.
Click to expand...
Click to collapse
Edited
[email protected] said:
Propably you patch wrong boot image, try to extract from your device stock
Click to expand...
Click to collapse
That didn't help as well. Now I'm sure that only some custom ROM will be my way to enjoy root. I will not flash any other stock ROM, I'm not that desperate (I'm also a bit afraid of doing so) .
gregory678 said:
That didn't help as well. Now I'm sure that only some custom ROM will be my way to enjoy root. I will not flash any other stock ROM, I'm not that desperate (I'm also a bit afraid of doing so) .
Click to expand...
Click to collapse
Okay, contact me on Telegram @Zmianek, and be a Tester of RessuectionRemix ! I always need to wait till the weekend with tests that slow's down development speed
gregory678 said:
That didn't help as well. Now I'm sure that only some custom ROM will be my way to enjoy root. I will not flash any other stock ROM, I'm not that desperate (I'm also a bit afraid of doing so) .
Click to expand...
Click to collapse
It should work. I've patched boot after every update without problems.
XT1941-4
Sent from my moto one
[email protected] said:
Okay, contact me on Telegram @Zmianek, and be a Tester of RessuectionRemix ! I always need to wait till the weekend with tests that slow's down development speed
Click to expand...
Click to collapse
I would like to, but is there some way of backing up stock ROM? I know that current version of TWRP has some issues with /data partition, that's why I ask .
And what about installing this ROM? Would I need to use that TWRP we have now? Is it safe?
tys0n said:
It should work. I've patched boot after every update without problems.
XT1941-4
Click to expand...
Click to collapse
Well, you have different software channel, I think that's the only reason why it works for you and it doesn't work for me . OPENEU seems to be bulletproof. (I have XT1941-4 too)
Someone correct me if I'm wrong, maybe for someone with OPENEU it does work.
I Request close due to failures
BEWARE
Has this changed, or is it still unsafe? I'm just getting back to checking on on rooting the GN2200 and I am on the C.11 update currently.
DemonLoader said:
Has this changed, or is it still unsafe? I'm just getting back to checking on on rooting the GN2200 and I am on the C.11 update currently.
Click to expand...
Click to collapse
I tried rooting c11 and I ended up bricked.
Could you make a rom backup of your device so i can un brick un mine
If you can guide me in the current set of utilities, I certainly can. I just don't stay that current until I'm ready to utilize, is all.
Im learning now
You have to be rooted to backup the firmware
I would never try to root a newer phone if it didn't support custom recovery like TWRP in-case something goes south.
immortalwon said:
I would never try to root a newer phone if it didn't support custom recovery like TWRP in-case something goes south.
Click to expand...
Click to collapse
There is custom recovery for this device. Buts its tricky to get it installed. The guide was deleted when the forum police banned scarlet wizard who wrote the guide
Have you tried installing KernelSU, and simply booting from fastboot in order to get your backups? Then once you have them, you can play with rooting again? I just learned of KernelSU this year, and I think it's a remarkable tool for getting our backups before flashing anything.
bricklife4me said:
BEWARE
Click to expand...
Click to collapse
def works flash this magisk patched A12 boot!
A12 C.11 magisk patched boot (working ON (GN2200) ONLY!!!!)
halloweenm925 said:
def works flash this magisk patched A12 boot!
A12 C.11 magisk patched boot (working ON (GN2200) ONLY!!!!)
Click to expand...
Click to collapse
Ya i got rooted too. I don't know what happen the first time
bricklife4me said:
Ya i got rooted too. I don't know what happen the first time
Click to expand...
Click to collapse
Do you just flash the boot img, or is there some thing else aso?
yacopsae said:
Do you just flash the boot img, or is there some thing else aso?
Click to expand...
Click to collapse
Fastboot flash boot <patches boot.img>
I dont need to disable dm-verity or anything? I just want to make sure before I try to flash a patched boot.img
Why remember them?
Damn they band Scarlet for real?
Use the script in the other thread
CoryBlaze said:
Damn they band Scarlet for real?
Click to expand...
Click to collapse
Yes they bannned my original account
mobile_sensei said:
Why remember them?
Click to expand...
Click to collapse
Cause that was a very fun forum
bricklife4me said:
Use the script in the other thread
Yes they bannned my original account
Click to expand...
Click to collapse
You still alive, how would I flash my IMEI back I lost it during the brick, but used your guide to restore my brick but IMEI is on back of the phone my carrier suspended my account because I didn't have the IMEI do you know how permanent add back