Database Users

Updating firmware and root?

Hi guys,
I know how rooting and flashing works but I've been using HTC devices since the nexus one so there are some differences I just want to make sure of. I got my 6P yesterday, I unlocked the bootloader and flashed TWRP. I wanted to gain root but Im not sure about flashing the modified boot img and the vendor thing.
My build was K but I got an OTA before unlocking the bootloader which updated to L. Anyway I don't know why I just formatted every thing in TWRP instead of the factory reset and I lost the OS X_X I tried to restore my nandroid with no luck. Anyway I got the factory img (MDB08L) from google dev and flashed used 'flash-all.bat' in the bootloader, the phone is running fine right now but I would like to update to the latest firmware 6.0.1+root since im not getting any OTA.
I would like to install CleanCore(6.0.1), the guide is
-> Flash Bootloader & Radio (as needed)
-> Flash CleanCore
-> Flash Modified Boot (named angler-xxxxxx-boot.zip)
-> Flash SuperSU or SuperSU Beta
-> Flash latest vendor.img (ROM & Vendor builds need to match!)
1. Should I use MMB29M factory img and flash 'flash-all.bat' like I did with the L build for the first step? then I flash new recovery?
-Flashing the rom through the recovery
2. so after I flash the rom I boot into the bootloader and flash the modified boot img with fastboot flash boot boot.img right?
3. then I go back to recovery and flash SU which I should download before.
4. vendor img is flashed in recovery too or fastboot?
Sorry for the hassle I just want to make sure.
One more thing, in this guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 at step 9, OP flashes the factroy img files separately (bootloader,radio,etc), is there a problem with using flashall.bat?
Thanks in advance and sorry for my noobish questions.

If you want to keep your data while doing this process, then yes, using the flash-all.bat is a problem. However, if you are fine with reverting back to stock(where you have to activate Android and reinstall all of your apps) then the flash-all.bat file is just fine.
That guide in the thread you linked walks you through how to update without losing data. After doing all of that, you'll just need to install TWRP and SuperSU again(do the latest systemless supersu though)

Enddo said:
If you want to keep your data while doing this process, then yes, using the flash-all.bat is a problem. However, if you are fine with reverting back to stock(where you have to activate Android and reinstall all of your apps) then the flash-all.bat file is just fine.
That guide in the thread you linked walks you through how to update without losing data. After doing all of that, you'll just need to install TWRP and SuperSU again(do the latest systemless supersu though)
Click to expand...
Click to collapse
Thanks for the help.
I have rooted my stock rom and gained root. I also installed exposed so i'll be fine without a custom rom for some time. There has been a report that some cameras aren't working on 6.0.1 with root so I'll wait for a while.
Thanks again

mr.dj26 said:
Thanks for the help.
I have rooted my stock rom and gained root. I also installed exposed so i'll be fine without a custom rom for some time. There has been a report that some cameras aren't working on 6.0.1 with root so I'll wait for a while.
Thanks again
Click to expand...
Click to collapse
I'm pretty sure those reports are because they used the SuperSU root method that didn't auto patch the boot image(which is the version(or two versions) behind the current version of SuperSU). This is happening because people are updating to 6.0.1, but the patched SuperSU boot image is for 6.0 and the 6.0 boot image conflicts with 6.0.1
As long as you use the latest version of SuperSU then you won't have any trouble with the camera

Enddo said:
I'm pretty sure those reports are because they used the SuperSU root method that didn't auto patch the boot image(which is the version(or two versions) behind the current version of SuperSU). This is happening because people are updating to 6.0.1, but the patched SuperSU boot image is for 6.0 and the 6.0 boot image conflicts with 6.0.1
As long as you use the latest version of SuperSU then you won't have any trouble with the camera
Click to expand...
Click to collapse
Thanks for the info

Boot.img messed up (i think)

I flashed magMa ux 8.5 rom for my n900t and i saw the Magisk systemless root and i got intrested! So i installed Magisk v12 with SuperSU but i found there was conflict with it so i wanted Magisk v12 with MagiskSU!
I tried dirty flashing the Magisk v12 + MagiskSU over the Magisk V12 + SuperSU! Which caused (im guessing here) caused my boot.img to get corrupted or damaged because it installs into ramdisk!
I tried a nandroid back to my old rom which, worked, wiped in twrp to reflash the rom, which also worked, but installing the magisk to the ramdisk and what it does ends up failing!
I can still boot into my system with root but it causes some conflicts with apps, such as snapchat as it thinks i have magisk still but i only have supersu! And i cannot full unroot from SuperSU app because, i think the boot.img is corrupted!
Would flashing a stock boot.img fix my problems, then reflashing rom again? Or would i have to reflash the whole stock samsung rom and things?
Im on Note 3 N900T! If reflashing the boot.img would work could someone provide a link to download the N900T!!! boot.img?
Thanks

What you call boot.img is the kernel.
Stock kernel won't work with a MM port like magma.
I advise you to do a full wipe from twrp then flash magma.
Before that, refer to the rom's thread for extensive informations about Magisk and systemless root.

[Request] Can someone upload the Stock Boot.img? [Xt1686]

I've accidentally deleted last backup, and now left with magisk modified img. There are some problems with magisk 13.3 [unable to install any module, solutions are welcome.] so need to clean my phone and install it again.
Someone please upload stock boot.img
On build NPN25.137-67

I'd like to see the same. I think I might have backed up a Magisk modified boot image but I'm not 100% certain. I'm on the -83 release for US retail. If someone could provide the boot.img (or a twrp backup of it) of the 100% stock version on NPN25.137-83 that would be fantastic.

V12.0.2.0.qfjmixm work with magisk?

Hi, anyone know if V12.0.2.0.qfjmixm is ok with magisk? scared to update because hard to go back. I have have a phone that came from China but use in New Zealand. Took awhile for Magisk to fix the bootloop issue with that.

Updated yesterday.
Magisk works.

I updated to EEA V12.0.2.0.qfjmixm using the recovery method, upgrade went fine. Then tried to install magisk using twrp = bootloop.
Reinstalled the same ROM again using TWRP, followed by magisk (after initial boot) and now is OK.
But as always back-up your data/apps/etc using TWRP just in case.

i installed magisk without twrp, just patched boot.img from the v12 rom, works very well

woozie.2007 said:
i installed magisk without twrp, just patched boot.img from the v12 rom, works very well
Click to expand...
Click to collapse
Hi woozie, would you mind sending me a patched boot.img and an original one for MIUI 12? My version is 12.0.2.0.QFJMIXM. I'd really appreciate that since my net is too bad to download large files. Hopefully our version is the same. Thanks in advance

i don't mind at all, but my version is 12.0.3.0, if yours is the same it should not be any problem, tell me if you want the patched boot i will upload somewhere
---------- Post added at 12:27 PM ---------- Previous post was at 12:24 PM ----------
but i did not manage to install the OTA file, so i had to download the entire firmware, about 2,2 GB, i think the boot patched is useless for you until you have not the whole firmware
You have to remove completely Magisk, then update OTA the full firmware, copy the firmware on the pc, because magisk will damage the firmware and you wil not copy it after install magisk, the zip will be corrupted. Extract boot from it, put it on the phone, patch it with magisk manager and flash it via fastboot, then install magisk

woozie.2007 said:
but i did not manage to install the OTA file, so i had to download the entire firmware, about 2,2 GB, i think the boot patched is useless for you until you have not the whole firmware
You have to remove completely Magisk, then update OTA the full firmware, copy the firmware on the pc, because magisk will damage the firmware and you wil not copy it after install magisk, the zip will be corrupted. Extract boot from it, put it on the phone, patch it with magisk manager and flash it via fastboot, then install magisk
Click to expand...
Click to collapse
Oh, I don't think that would work. Thank you very much anyways, I'm still trying to download the ROM. Not even a dial up would be as troublesome hahah.
Sent from my davinci using XDA Labs

woozie.2007 said:
i installed magisk without twrp, just patched boot.img from the v12 rom, works very well
Click to expand...
Click to collapse
hi, can you guide us with the procedure to do that kinda stunt xD

shalashaska_ocelot said:
hi, can you guide us with the procedure to do that kinda stunt xD
Click to expand...
Click to collapse
yes, start here

Can't Root Samsung SM-T380

Hello,
I was wondering if the T380 is rootable?
I tried to follow [TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018 but it didn't work ( as I assume) since the guide is quite old. I also tried patching the boot.img using the magisk tutorial but I end up with the Installed: N\A Ramdisk: Yes A\B & Sars: no.
I can't also downgrade since I have the latest 2021 patch and the binary is 4 while the version below that is on 3. ROM STOCK
PS: I can install TWRP without any problems, the only issue is rooting with magisk
Any help or suggestion really appreciated.

This is exactly the same problem that I've been having with my T380. I've flashed the stock rom and retried many different methods of rooting with Magisk but they all have failed. If you got it workiing, please tell me what made it work for you. Thanks!
These are the steps that I took using post by Winston Churchill as a guide:
1. Enable OEM Unlock
2. Use Odin to flash TWRP with twrp_3.2.3-1_sm-t380_oo_4119.tar on AP Slot
3. TWRP Wipe/Reformat Data then reboot to recovery
4. Install boot.img patched by Magisk using TWRP (I extracted boot.img from stock firmware and used Magisk to make patched boot.img)
5. Install Magisk.zip using TWRP (this didn't do anything, I had to manually install the apk later on)
6. Install Tab_A_2017_Pie_forced+encryption_disabler.zip using TWRP
7. Wipe Cache and Dalvik
8. Reboot System
I tried alternative approach for installing Magisk using this guide. It basically is extracting boot.img off your current device firmware and using Magisk to patch that boot.img. Then flash the patched boot.img using TWRP (it didn't work for me though)
These are the places I went to get my files:
https://forum.xda-developers.com/t/rooting-sm-t380-with-pie.4049951/ (Post by Winston Churchill)
https://forum.xda-developers.com/t/guide-comprehensive-t380-tab-a-2017-8-0-root-guide.3753203/
https://forum.xda-developers.com/t/twrp-3-2-1-1-root-tab-a-sm-t380-t385-10-02-2018.3747564/

Barto604 said:
Hello,
I was wondering if the T380 is rootable?
I tried to follow [TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018 but it didn't work ( as I assume) since the guide is quite old. I also tried patching the boot.img using the magisk tutorial but I end up with the Installed: N\A Ramdisk: Yes A\B & Sars: no.
I can't also downgrade since I have the latest 2021 patch and the binary is 4 while the version below that is on 3. ROM STOCK
PS: I can install TWRP without any problems, the only issue is rooting with magisk
Any help or suggestion really appreciated.
Click to expand...
Click to collapse
I haven't done this on the T380, but it works on other Samsung tablets. Instead of the rigamarole of patching the boot image, just flash Magisk-v21.4.zip with TWRP. It won't give you the latest version, but it installs Magisk Manager, and you can use that to update to the latest version of Magisk and Magisk Manager.

lewmur said:
I haven't done this on the T380, but it works on other Samsung tablets. Instead of the rigamarole of patching the boot image, just flash Magisk-v21.4.zip with TWRP. It won't give you the latest version, but it installs Magisk Manager, and you can use that to update to the latest version of Magisk and Magisk Manager.
Click to expand...
Click to collapse
Hi, sorry for the late reply, I already tried using earlier versions of magisk it says it patch and everything via TWRP but when I reboot magisk app is not found and when I install the APK it says Installed: N/A

Barto604 said:
Hi, sorry for the late reply, I already tried using earlier versions of magisk it says it patch and everything via TWRP but when I reboot magisk app is not found and when I install the APK it says Installed: N/A
Click to expand...
Click to collapse
Try flashing Magisk23.apk with TWRP as if it were a zip. That worked with latest 11 ROM with T500.

Tried it, didn't work either, I think them latest security patch for this tablet block root or something, I'm literally stuck.