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 ?)
Related
<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
installing..,
Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.
Any idea what fixes are in this one?
davidstjohn1 said:
Any idea what fixes are in this one?
Click to expand...
Click to collapse
https://source.android.com/security/...019-04-01.html
https://source.android.com/security/...language=zh_cn
davidstjohn1 said:
Any idea what fixes are in this one?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2019-04-01.html
Hi everyone, I need some help/advice,
I tried flashing the April factory image (minus -w), and am now on "Can't load Android System. Your data may be corrupt" error. Everytime I reboot the device it just goes to "No Command" or this error screen.
I uninstalled Magisk, and was on Sultan's kernel. Does anyone have any suggestions on how to restore my system without having to factory reset? I know some people suggested flashing stock kernel, but I can't seem to find the link to it (I thought the stock kernel was with the factory image).
Any help would be appreciated!
I am dling the factory image now, but boot.img should be in there. Are you sure it was not a bad dl?
-Boot.img is in there. Extract the zip then open the "image-blueline....zip" it is in there. If it is not then something is wrong with your dl.
sliding_billy said:
Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.
Click to expand...
Click to collapse
What prop setting are you making. Just curious, I haven't seen any prop editing threads for the pixel 3.
FilthyFord said:
What prop setting are you making. Just curious, I haven't seen any prop editing threads for the pixel 3.
Click to expand...
Click to collapse
Native tethering. This method works on my 3 XL as well as my wife's "little" 3 on T-Mobile.
https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662
atu567 said:
Hi everyone, I need some help/advice,
I tried flashing the April factory image (minus -w), and am now on "Can't load Android System. Your data may be corrupt" error. Everytime I reboot the device it just goes to "No Command" or this error screen.
I uninstalled Magisk, and was on Sultan's kernel. Does anyone have any suggestions on how to restore my system without having to factory reset? I know some people suggested flashing stock kernel, but I can't seem to find the link to it (I thought the stock kernel was with the factory image).
Any help would be appreciated!
Click to expand...
Click to collapse
I had the same issue, cant find stock kernel either.
extracted the zip, fastboot flash boot boot.img, fixed.
jk didnt work oddly enough.
got to login then wouldnt let me use my screen. no touch input.
edit again: update platform tools fixed problem. https://dl.google.com/android/repository/platform-tools_r28.0.2-windows.zip
sliding_billy said:
Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.
Click to expand...
Click to collapse
hey,bro!I would like to ask if magisk can pass the safetynet check after installing the April Updata. My pixel 3 feedback me ‘’the return value is invalid’’
wssxzzzz said:
hey,bro!I would like to ask if magisk can pass the safetynet check after installing the April Updata. My pixel 3 feedback me ‘’the return value is invalid’’
Click to expand...
Click to collapse
No problem with safetynet here.
sliding_billy said:
No problem with safetynet here.
Click to expand...
Click to collapse
Ok, thank you, I think that is my problem.
wssxzzzz said:
Ok, thank you, I think that is my problem.
Click to expand...
Click to collapse
What is the problem?
Obviously quite subjective, but the camera appears to be opening faster for me when double clicking power. There was also a Google Camera update from the Play Store this morning, so could have been that as well, but this has been a major bug bear of mine since getting the Pixel 3, so hope it stays like that!
benj! said:
Obviously quite subjective, but the camera appears to be opening faster for me when double clicking power. There was also a Google Camera update from the Play Store this morning, so could have been that as well, but this has been a major bug bear of mine since getting the Pixel 3, so hope it stays like that!
Click to expand...
Click to collapse
Def the cam app I noticed too and I'm on Jan update, it's nice tho!
I installed the April update to fix the flashing bug of the ambient display, bit it is still there. Any body else having this issue? Also, is there any fix for this?
Hi guys
My mido vibration stopped working a week back abruptly. I didn't flash anything new back then.
Tried diagnosing it with change of vibration motor (with a technician) as well but the new one didn't work either. He did attempt a temporary replacement of its underlying chip as well but again it didn't resolve the issue.
Attempted clean reflash RR. Then clean reflashed Havoc 2.9 build as well.
After reflash in both the builds, didn't install Magisk (just to be sure some version could have been conflicting with the motor may be)...No solution
Attempted firmware upgrade to notably stable versions 10.2.3 and then downgraded to 9.6.3 as well. No solution still....
Could anyone advise what I could attempt next..?
Current environment: Havoc 2.9
No magisk installed as of now.
Nothing works.
Magisk 20.1 was installed but removed now... Still doesn't work...
Please help.
@Walden0 brother could you help may be?
Naagraj said:
@Walden0 brother could you help may be?
Click to expand...
Click to collapse
I don't really know what might be the issue , but I can suggest you to flash stock miui rom to see if it works there.
Don't forget to backup modem and efs partitions in case anything goes wrong with IMEI numbers. I hope that solves it.
Walden0 said:
I don't really know what might be the issue , but I can suggest you to flash stock miui rom to see if it works there.
Don't forget to backup modem and efs partitions in case anything goes wrong with IMEI numbers. I hope that solves it.
Click to expand...
Click to collapse
That could be a little tricky for me since I haven't attempted to go back to MIUI again. Could you point me to a guide or so?
Naagraj said:
That could be a little tricky for me since I haven't attempted to go back to MIUI again. Could you point me to a guide or so?
Click to expand...
Click to collapse
First take a backup of EFS Am& modem partitions from recovery.
Wipe data, cache, dalvik & system. Flash miui rom, format data and flash orange fox recovery again. Boot into system.
That's it.
Is orange fox recovery necessary? I don't know.
I an currently using twrp 3.3.1.0
Will that work?
Furthermore just to tell
Vibration doesn't work even in twrp (which actually is very strong in twrp navigation generally)
Could this hint a hardware malfunction?
Also, i did see the efs partition but not modem one....
Naagraj said:
Is orange fox recovery necessary? I don't know.
I an currently using twrp 3.3.1.0
Will that work?
Click to expand...
Click to collapse
Should work, orangefox has aggressive stock recovery deactivation which isn't available in twrp I guess.
btw quote or mention me as I can't get any notification if you don't.
Naagraj said:
Furthermore just to tell
Vibration doesn't work even in twrp (which actually is very strong in twrp navigation generally)
Could this hint a hardware malfunction?
Also, i did see the efs partition but not modem one....
Click to expand...
Click to collapse
Have already told you pal, try flashing miui and see if it works.
Modem partition should be in orangefox. I can't confirm as I don't have the device anymore.
Brother I am having same problem right now in 2020. did you find any solution to it? Any response will be greatly appreciated
I'm having this same problem in 2021. Any fix guys?
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
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