Related
hi guys.i have nexus 9 with unlock bootloader, rooted mmb29s lte and twrp installed.do i need to flash all mmb29r stock rom or there are another method how to flash update from google.
thanks in advance
Sent from my Nexus 9 using Tapatalk
As no one else replied.
http://www.digitaltrends.com/mobile/how-to-install-android-factory-image/
Can be done without wiping data if needed.
Also checkout Chainfire's Flashfire App, if you have systemless root and an unmodified system, which can update by ota.
Can also be used to flash factory images.
Alternatively just flash boot, system and vendor images.
Reboot to recovery, wipe cache and dalvik cache, flash, reboot system = dirty flash.
I assume we're talking about going from MMB29S to MMB29R? For the February security patches?
I'm currently downloading 29R and have a rooted MMB29S (TWRP). Have we confirmed or played with Flashfire on the Nexus 9? I've used it with my S5 with success but haven't on the tablet.
TheMuffnMan said:
I assume we're talking about going from MMB29S to MMB29R? For the February security patches?
I'm currently downloading 29R and have a rooted MMB29S (TWRP). Have we confirmed or played with Flashfire on the Nexus 9? I've used it with my S5 with success but haven't on the tablet.
Click to expand...
Click to collapse
Let us know if it works out for you.
I tried it with February OTA, but my system had been mounted RW so it failed.
Flashed the Factory Image with NRT instead, then was playing with Flashfire and successfully applied the R OTA on top of it (even with ElementalX Kernel installed).
Are you hoping to update by OTA or using it to flash factory images?
corkiejp said:
Let us know if it works out for you.
I tried it with February OTA, but my system had been mounted RW so it failed.
Flashed the Factory Image with NRT instead, then was playing with Flashfire and successfully applied the R OTA on top of it (even with ElementalX Kernel installed).
Are hoping to update by OTA or using it to flash factory images?
Click to expand...
Click to collapse
Definitely not OTA - probably bricking that if I tried haha.
Flash the factory images separately I'm thinking.
TheMuffnMan said:
Definitely not OTA - probably bricking that if I tried haha.
Flash the factory images separately I'm thinking.
Click to expand...
Click to collapse
As long as your bootloader is unlocked, it would be pretty hard to brick it.
I will be trying it by OTA for March's update.
corkiejp said:
As long as your bootloader is unlocked, it would be pretty hard to brick it.
I will be trying it by OTA for March's update.
Click to expand...
Click to collapse
I say brick, I actually mean like boot loop - where I'd need to do a full erase and rebuild. Not an actual creation of a paperweight.
it hard to flash whole rom for every update.and i once have brick my tab.twrp not recognise internal storage,it state internal storage 0mb.
Sent from my Nexus 9 using Tapatalk
Just completed it last night, tried OTA for ****s and giggles with FlashFire (it auto detects an OTA pending) which did absolutely nothing. Just booted back up as it was MMB29S.
Then I tried just the OTA for fun, got a dead Android symbol.
Then I just did my usual process, extracted each file, flashed each - except recovery which I flashed with TWRP 3.0.0.2 and then rebooted into Recovery where I flashed SuperSU 2.6.6 Beta, wiped Dalvik/cache and then booted tablet.
Retained all my data and it seems to be running fine.
TheMuffnMan said:
Just completed it last night, tried OTA for ****s and giggles with FlashFire (it auto detects an OTA pending) which did absolutely nothing. Just booted back up as it was MMB29S.
Then I tried just the OTA for fun, got a dead Android symbol.
Click to expand...
Click to collapse
Any chance you still have access to the logs? Try posting to the linked thread.
Chainfire said:
In case of issues, immediately after rebooting back into Android:
- Post /sdcard/FlashFire/lastlog
- Post /proc/last_kmsg
The latter may not be present, and is replaced on every reboot. So if you rebooted twice, no sense posting it.
Click to expand...
Click to collapse
Didn't know TWRP was updated, just used flashfire to flash the updated version.
Why not the latest SuperSU 2.67?
corkiejp said:
Any chance you still have access to the logs? Try posting to the linked thread.
Click to expand...
Click to collapse
I'm sure I could probably dig them up!
corkiejp said:
Didn't know TWRP was updated, just used flashfire to flash the updated version.
Why not the latest SuperSU 2.67?
Click to expand...
Click to collapse
Didn't know about the 2.67! Already had the 2.66 Beta on the device so I just flashed that guy.
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 ?)
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
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
Tried to root with magisk and now the phone won't boot, just keep getting message boot failed and then my firmware is corrupt. Anyone managed to root yet? I can't seem to get into fastboot or recovery either
andy242 said:
Tried to root with magisk and now the phone won't boot, just keep getting message boot failed and then my firmware is corrupt. Anyone managed to root yet? I can't seem to get into fastboot or recovery either
Click to expand...
Click to collapse
Finally managed to get into fastboot and flash stock firmware. Hopefully it was just one of those things and Google haven't changed anything to stop us rooting
Probably just need a Magisk update.
Canary build of Magisk?
Patched init_boot, not boot?
Colchiro said:
Canary build of Magisk?
Patched init_boot, not boot?
Click to expand...
Click to collapse
I tried to patch using magisk alpha but will try again with canary tomorrow. Got in a bit of a panic because I couldn't get into fastboot. Had to power off with power and volume up (couldn't power off any other way) then I could boot into fastboot with power and volume down (took 20 seconds) not sure if that's normal as it's my 1st pixel
We had to patch init_boot for the 7 Pro, so I assume the Fold will be the same. (I have no insider knowledge.)
My plan is to let the experts be the guinea pigs.
Colchiro said:
Canary build of Magisk?
Patched init_boot, no
Colchiro said:
We had to patch init_boot for the 7 Pro, so I assume the Fold will be the same. (I have no insider knowledge.)
My plan is to let the experts be the guinea pigs.
Click to expand...
Click to collapse
I used pixelflasher to extract the init_boot then patched it with magisk alpha then tried to flash it with pixelflasher once patched. Maybe I did something wrong with slots or something? It flashed in a couple of seconds and then straight to the corrupt message. I'll try again tomorrow doing it manually with canary unless someone beats me to it and writes a guide
Click to expand...
Click to collapse
I've always patched the file with Magisk, then update via fastboot, then flashed the patched image, all from the command line. I've been doing it this way for the last decade, so when PixelFlasher came out, saw no reason to learn something new.
A month or so ago I saw there was a newer version of ADB and updated it only to find out there were issues (my upgrade failed) with it so installed an older version. I hope you haven't made the same mistake.
andy242 said:
I tried to patch using magisk alpha but will try again with canary tomorrow. Got in a bit of a panic because I couldn't get into fastboot. Had to power off with power and volume up (couldn't power off any other way) then I could boot into fastboot with power and volume down (took 20 seconds) not sure if that's normal as it's my 1st pixel
Click to expand...
Click to collapse
Please do report back your results with Canary. Thanks!