Root unsuccessful everytime - Samsung Galaxy S10+ Guides, News, & Discussion

I tried every method but still can't get the root access. My device is on the latest January update.
Kindly help me to root my device.

Have you unlocked the oem lock? Make sure the rooting procedure is updated.

kazim.asghar said:
Have you unlocked the oem lock? Make sure the rooting procedure is updated.
Click to expand...
Click to collapse
yes i did unlocked the bootloader and also the oem lock option is grey in settings

sunmughans said:
yes i did unlocked the bootloader and also the oem lock option is grey in settings
Click to expand...
Click to collapse
If its unlocked and its g975+ use these FILES already patched with magisk and also have twrp in it. Just flash these using Odin. After flashing you must install magisk manager if not installed.
Edit. These files are from CAROTIX CARHDMOD thread and is android Q.

comsite said:
If its unlocked and its g975+ use these FILES already patched with magisk and also have twrp in it. Just flash these using Odin. After flashing you must install magisk manager if not installed.
Edit. These files are from CAROTIX CARHDMOD thread and is android Q.
Click to expand...
Click to collapse
Thanks sir, let me download it and flash first. I'll revert you after finishing the process.

What type of S10+ you have ?
Sent from my SM-G9750 using Tapatalk

comsite said:
If its unlocked and its g975+ use these FILES already patched with magisk and also have twrp in it. Just flash these using Odin. After flashing you must install magisk manager if not installed.
Edit. These files are from CAROTIX CARHDMOD thread and is android Q.
Click to expand...
Click to collapse
TWRP Installed successfully! But One UI isn't booting. Bootloop.......

sunmughans said:
TWRP Installed successfully! But One UI isn't booting. Bootloop.......
Click to expand...
Click to collapse
Wipe data from twrp then use multidisabler from ian thread flash it through twrp. Then reboot and report.

comsite said:
Wipe data from twrp then use multidisabler from ian thread flash it through twrp. Then reboot and report.
Click to expand...
Click to collapse
Working bro

sunmughans said:
Working bro
Click to expand...
Click to collapse
Good to hear

comsite said:
Good to hear
Click to expand...
Click to collapse
I want to upgrade to January patch without losing twrp and magisk. Is there any working guide ?

sunmughans said:
I want to upgrade to January patch without losing twrp and magisk. Is there any working guide ?
Click to expand...
Click to collapse
Download latest firmware jan patch from sammobile patch it with magisk app you already have. Download ian recovery for android Q patch this too and rename patched_recovery.img to recovery.img. Open patched firmware ap tar with 7zip put patched recovery in this tar. And flash it. If you wanna save whe data using HOME_CSC.
OR
Simply dirty flash beyond rom you will automatically upgraded to jan patch and also with lots of useful mods too.

comsite said:
If its unlocked and its g975+ use these FILES already patched with magisk and also have twrp in it. Just flash these using Odin. After flashing you must install magisk manager if not installed.
Edit. These files are from CAROTIX CARHDMOD thread and is android Q.
Click to expand...
Click to collapse
Will these files work on my S10 + Exynos uk
Thank you

Wingchundub said:
Will these files work on my S10 + Exynos uk
Thank you
Click to expand...
Click to collapse
Yes as mine is also s10+ uk

Appreciated fella, Thank you
just to clarify, I have 1 x AP rar file aka patched and 3x Md5

Wingchundub said:
Appreciated fella, Thank you
just to clarify, I have 1 x AP rar file aka patched and 3x Md5
Click to expand...
Click to collapse
Yes. You have all files.

Phone came today, seller has updated it to 10 ONE UI v2.0
So i will downgrade, as my current bootloader binary code aka 3 is the same as the last version of android 9, so i am able to downgrade, which i'd rather do to be safe, before i proceed with root method.

Downgraded to v9, all is well, but OEM UNLOCK was not showing in developer options, so did the change date to 8 days before trick and OEM UNLOCK is back

OK, i followed tut oem greyed out,and proceeded with install, all ok, now rooted after using disabler and installing magisk manager.
Also not sure if a new thing or need additional program on my laptop, but i can not transfer files from laptop to the sd card or internal of phone.
I get your path sdcard is not accessible alot?
Is this due to android 10? am i best installing another rom, pref v9
All the folders in internal of phone are not named as normal, just all mixed numbers and letters

Wingchundub said:
OK, i followed tut oem greyed out,and proceeded with install, all ok, now rooted after using disabler and installing magisk manager.
Also not sure if a new thing or need additional program on my laptop, but i can not transfer files from laptop to the sd card or internal of phone.
I get your path sdcard is not accessible alot?
Is this due to android 10? am i best installing another rom, pref v9
All the folders in internal of phone are not named as normal, just all mixed numbers and letters
Click to expand...
Click to collapse
You need to wipe data from twrp.
You must have to wipe data if rooting first time.
Anyways don't do any lengthy processes like downgrade or flash any firmware. Just wipe.
Turn off phone and boot into twrp by pressing power+volume up+bixby. Choose wipe then either format data or choose advance and wipe it.

Related

Can anyone prove me marshmallow latest update stock firmware ? MOB31E ?

Can anyone provide me stock firmware. my mobile got stuck on boot animation please help me ?
vivek1310yadav said:
Can anyone provide me stock firmware. my mobile got stuck on boot animation please help me ?
Click to expand...
Click to collapse
Well there's no MM based SPFT file, so all you have to do is either flash stock kk/LP using SPFT or if you've twrp installed, boot into TWRP again and wipe everything except SD, flash the MOB31E full stock Rom zip. Link : MOB31E OTA's and flashable zips thread
sachin n said:
Well there's no MM based SPFT file, so all you have to do is either flash stock kk/LP using SPFT or if you've twrp installed, boot into TWRP again and wipe everything except SD, flash the MOB31E full stock Rom zip. Link : MOB31E OTA's and flashable zips thread
Click to expand...
Click to collapse
Hello, please help
The device is canvas a1 and it is fully updated till the last update via OTAs only. I performed factory reset on it. It is now stuck on setup wizard. Not able to skip from there.
I wanted to flash it again.
So, can you please tell if it is OK to flash KK or LP flash files?
(I am asking this because, its BL might have got upgraded in OTA updates and it could be dangerous to downgrade to lower versions by flashing.)
pra27 said:
Hello, please help
The device is canvas a1 and it is fully updated till the last update via OTAs only. I performed factory reset on it. It is now stuck on setup wizard. Not able to skip from there.
I wanted to flash it again.
So, can you please tell if it is OK to flash KK or LP flash files?
(I am asking this because, its BL might have got upgraded in OTA updates and it could be dangerous to downgrade to lower versions by flashing.)
Click to expand...
Click to collapse
Do you've twrp recovery installed at the moment?
sachin n said:
Do you've twrp recovery installed at the moment?
Click to expand...
Click to collapse
No it is not even unlocked yet.
pra27 said:
No it is not even unlocked yet.
Click to expand...
Click to collapse
Remove your battery and insert it again, put the device into bootloader mode and unlock it, then you can fastboot the twrp and good to go.
Sent from my Redmi Note 4 using Tapatalk
sachin n said:
Remove your battery and insert it again, put the device into bootloader mode and unlock it, then you can fastboot the twrp and good to go.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
You mean after this I can file LP flash files?
No downgrading bootloader issues right?
pra27 said:
You mean after this I can file LP flash files?
No downgrading bootloader issues right?
Click to expand...
Click to collapse
Nothing to worry. Once you get twrp, just clean flash stock lollipop Rom. Don't use SPFT, you gonna brick your phone if something goes wrong wrong. I'll link you LP (flashable via twrp) Rom, tell me when you done.
sachin n said:
Nothing to worry. Once you get twrp, just clean flash stock lollipop Rom. Don't use SPFT, you gonna brick your phone if something goes wrong wrong. I'll link you LP (flashable via twrp) Rom, tell me when you done.
Click to expand...
Click to collapse
Thanks a lot for your help.
Should i flash this twrp ? (from official site)
https://dl.twrp.me/sprout/
pra27 said:
Thanks a lot for your help.
Should i flash this twrp ? (from official site)
https://dl.twrp.me/sprout/
Click to expand...
Click to collapse
Nah, use this : https://www.androidfilehost.com/?fid=24562946973632081
Stable enough!!!!
sachin n said:
Nah, use this : https://www.androidfilehost.com/?fid=24562946973632081
Stable enough!!!!
Click to expand...
Click to collapse
thanks.. bdw that official twrp whose link i gave is also for sprout4 right?
Please give the stock rom link you were talking about earlier.
pra27 said:
thanks.. bdw that official twrp whose link i gave is also for sprout4 right?
Please give the stock rom link you were talking about earlier.
Click to expand...
Click to collapse
Yes it was also sprout4, in fact for both sprout 4 and sprout 8.
This : https://drive.google.com/uc?id=0B9_eDTtTcnv1LTF2UFhaSjhhZWM&export=download
Boot to TWRP
Wipe everything except SD card
Flash this rom
Reboot
sachin n said:
Yes it was also sprout4, in fact for both sprout 4 and sprout 8.
This : https://drive.google.com/uc?id=0B9_eDTtTcnv1LTF2UFhaSjhhZWM&export=download
Boot to TWRP
Wipe everything except SD card
Flash this rom
Reboot
Click to expand...
Click to collapse
i found this and right now flashing marshmallow from this thread. https://forum.xda-developers.com/ca...-stock-debloated-prerooted-untouched-t3403499
can you please share the thread from which you shared the file? also if there any marshmallow zip available, please give its link.
pra27 said:
i found this and right now flashing marshmallow from this thread. https://forum.xda-developers.com/ca...-stock-debloated-prerooted-untouched-t3403499
can you please share the thread from which you shared the file? also if there any marshmallow zip available, please give its link.
Click to expand...
Click to collapse
Wait..
Edit : https://forum.xda-developers.com/crossdevice-dev/android-one-general/rom-t3120737
Sent from my mido using XDA Labs
sachin n said:
Wait..
Edit : https://forum.xda-developers.com/crossdevice-dev/android-one-general/rom-t3120737
Sent from my mido using XDA Labs
Click to expand...
Click to collapse
Thanks bro, you have been helpful in bringing my phone back to life.
One last thing though, what should i do incase some OTA arrives.. is there any way to block it?
pra27 said:
Thanks bro, you have been helpful in bringing my phone back to life.
One last thing though, what should i do incase some OTA arrives.. is there any way to block it?
Click to expand...
Click to collapse
Disable Gplay services notifications. Or Just download and flash MOB31E stock Rom. Zip
Sent from my mido using XDA Labs
Hi there
I have the same problem and my phone is stuck at the boot screen.
My phone does not allow me to enable USB debugging and I am really stuck with being able to install TWRP and flash the stock ROM.
I'm incredibly confused and am unsure what I am doing. Attached is a screenshot of the CMD box.
Help and simple instructions would be appreciated.
Thanks in advance.

Any root for a3 (2017) on Nougat?

Is already possible to root the Galaxy a3 (2017) on Nougat and so yes can sombody give a link?
Sure, search in the forum there is a thread but remember to use supersu 2.82
I also have root, I have installed Magisk.
notthesun said:
Sure, search in the forum there is a thread but remember to use supersu 2.82
Click to expand...
Click to collapse
you mean this threat?
tonime said:
I also have root, I have installed Magisk.
Click to expand...
Click to collapse
you did it from this threat?
khanvict90 said:
you did it from this threat?
Click to expand...
Click to collapse
Yes, Root here:
https://forum.xda-developers.com/sa...root-sm-a320f-fl-y-samsung-galaxy-a3-t3556026
Magisk here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
tonime said:
Yes, Root here:
https://forum.xda-developers.com/sa...root-sm-a320f-fl-y-samsung-galaxy-a3-t3556026
Magisk here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
How to install Magisk ???
If one of it's installation steps is to be fully unrooted first and the boot image should be stock.
I already rooted and modified the boot image as for this device we need to flash a file to the boot.img to stop the device from encrypting the internal storage to be able to mount it.
Please Help ...
tonime said:
Yes, Root here:
https://forum.xda-developers.com/sa...root-sm-a320f-fl-y-samsung-galaxy-a3-t3556026
Magisk here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Thanks mate! But little quistion this is root for nougat right and do i need to unlock my boot loader or can i start right away because i did buy it yesterday so its fully stock and it is A320 FL im from the netherlands
khanvict90 said:
Thanks mate! But little quistion this is root for nougat right and do i need to unlock my boot loader or can i start right away because i did buy it yesterday so its fully stock and it is A320 FL im from the netherlands
Click to expand...
Click to collapse
By Odin flash TWRP, copy the Magisk file to the memory of the phone or to the SD card and Magisk flash by TPWR recovery.
When you restart, install the Magisk manager apk and that's it.
tonime said:
By Odin flash TWRP, copy the Magisk file to the memory of the phone or to the SD card and Magisk flash by TPWR recovery.
When you restart, install the Magisk manager apk and that's it.
Click to expand...
Click to collapse
Wow thats easy man thanks hehe and btw when i did install nougat on my phone i only flashed the ap is that a problem or should i flash al the other files like bl cp and csc togther? I was scared because i have a320FL and not a320F
tonime said:
By Odin flash TWRP, copy the Magisk file to the memory of the phone or to the SD card and Magisk flash by TPWR recovery.
When you restart, install the Magisk manager apk and that's it.
Click to expand...
Click to collapse
Edited: i found it i put it in sd card now its working i have root!!
Root 100% Working!
Root is working 100% for A3 (2017) Android 6.0.1 and even for 7.0!
Links are given in the Galaxy A series 2017 forum
After Flashing Twrp On Nougat
Some balck Screen Shows To Reset My Phone
Sorry Not Good In English
hi after flashing nougat on the a3 2017 i got in the settings menu two battery tabs other than the device maintenance, it's a bug or i flashed it in wrong way ?
edwardola said:
hi after flashing nougat on the a3 2017 i got in the settings menu two battery tabs other than the device maintenance, it's a bug or i flashed it in wrong way ?
Click to expand...
Click to collapse
This is normal and it happened because you flashed the AP file only
If you want to get rid of these Russian providers menus and have stock settings menu you need to flash the full rom files (BL+AP+CP+CSC) via Odin.
AK2H said:
This is normal and it happened because you flashed the AP file only
If you want to get rid of these Russian providers menus and have stock settings menu you need to flash the full rom files (BL+AP+CP+CSC) via Odin.
Click to expand...
Click to collapse
if i flash everything i get a fail but if i only flash ap it passes?
khanvict90 said:
if i flash everything i get a fail but if i only flash ap it passes?
Click to expand...
Click to collapse
No you shouldn't get a fail.
If you're encountering any issues in flashing via Odin make sure to use the latest version 3.12.3
AK2H said:
No you shouldn't get a fail.
If you're encountering any issues in flashing via Odin make sure to use the latest version 3.12.3
Click to expand...
Click to collapse
im using 3.12.7 and i am already on nougat but i want to flash all the files instead of only AP
is it possbile that it fails because the model number i have a 320FL not the F but i flashed the AP of F on FL it worked but if i want to flash all files it gives fail?
khanvict90 said:
im using 3.12.7 and i am already on nougat but i want to flash all the files instead of only AP
is it possbile that it fails because the model number i have a 320FL not the F but i flashed the AP of F on FL it worked but if i want to flash all files it gives fail?
Click to expand...
Click to collapse
Many people reported that the Russian firmware is working flawlessly on A320FL Model and no one mentioned any issues during the flash process.
For me, first time i flashed the rom the flash progress stopped near the end because i was using the 3.10.7 (not 3.12.7 as you mentioned) version just like you.
After using the 3.12.3 version it worked perfectly.
So you nead to use the latest version of Odin (3.12.3)
Whether this method can be applied in galaxy a7 2017 running in nougat?

[ROOT] SM-J730G/GM/F Galaxy J7 Pro

Below you will find my procedure to root the SM-J730G/GM Galaxy J7 Pro - Exynos 7870
(may also work for J730F, see post #3)
This procedure has been tested on J730GMDXU1AQF8 firmware. It may work for future releases or it may not.
If an updated firmware becomes available my advice is to update with FLASHFIRE to maintain root.
DISCLAIMER: YOU FLASH THESE AT YOUR OWN RISK. THE KNOX COUNTER WILL BE TRIPPED AND WILL POTENTIALLY VOID YOUR WARANTY. HAVING THE STOCK FIRMWARE TO HAND IS ALSO ADVISED
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Instructions:
◘ 1. Download the files below:
sm-j730gm_SR3-SuperSU-v2.79-SR3_root_boot_32
ODIN 3.12
SAMSUNG_USB_Driver_for_Mobile_Phones
◘ 2. Install the USB driver and ODIN to Windows.
◘ 3. Boot your device to RECOVERY mode then select FACTORY RESET. THIS WILL WIPE YOUR DEVICE AND YOU WILL LOSE ALL DATA. (This procedure is required to remove encryption or your device won't boot)
◘ 4. From RECOVERY, IMMEDIATELY Boot your device to DOWNLOAD mode then connect your USB cable. (DO NOT LET YOUR DEVICE REBOOT NORMALLY OR YOUR DEVICE WILL RE-ENCRYPT)
◘ 5. Run ODIN and place the sm-j730gm_SR3-SuperSU-v2.79-SR3_root_boot_32.tar file as is in the AP slot. Don't change any options and hit START.
◘ 6. Wait for the device to flash and reboot.
◘ 7. Install the SuperSU apk from Play store and you should be rooted.
◘ 8. Have fun!
Credits: Me, @Chainfire(for supersu), @mottx(for testing)
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
IF YOU APPRECIATE WHAT I DO AND WISH TO DONATE ME A COFFEE/BEER THEN CLICK HERE OR HIT THE THANKS BUTTON IF I HELPED YOU
Great work Thanks hit.
Sir, flashing zips thru Flashfire? I Hope TWRP will be released soooon.
works for 730F
Hi ashyx, thanks you! I can confirm that this method is working for the J7 730F/DS model whith Version J730FXXU1AQF4.
Does anyone know why the bloatware can not uninstall on Android 7 Nougat? I have rooted my J730G and use Link2SD app to uninstall the default apps, but the apps can not remove. I can use link2sd app on Android 6 Marshmallow to remove default app.
I use System App Remover from Playstore.
ilsor76 said:
I use System App Remover from Playstore.
Click to expand...
Click to collapse
I have used the apps and others apps but It failed, It looks like storage protection.
Update:
I could removed the apps using ES File Explorer by activated Root Exlorer -> Mount R/W
Great buddy
Is this boot image built from kernel source ? Whats the difference in 64 bit and 32 bit version u gave at oves thread? Pls explain as it will help me for future development
Sent from my SM-J730GM using Tapatalk
Berong said:
Great work Thanks hit.
Sir, flashing zips thru Flashfire? I Hope TWRP will be released soooon.
Click to expand...
Click to collapse
TWRP already available here:
https://forum.xda-developers.com/galaxy-j7-2017/how-to/guide-j7-pro-2017-t3647101/post73181512
v00d007 said:
TWRP already available here:
https://forum.xda-developers.com/galaxy-j7-2017/how-to/guide-j7-pro-2017-t3647101/post73181512
Click to expand...
Click to collapse
I think its only for GM variants...
Berong said:
I think its only for GM variants...
Click to expand...
Click to collapse
Yes, you are right. It does not work for SM-J730F and SM-J730G (tested). Stuck on samsung logo.
redymedan said:
Yes, you are right. It does not work for SM-J730F and SM-J730G (tested). Stuck on samsung logo.
Click to expand...
Click to collapse
After installing it reset phone
So it does work for G?
Berong said:
So it does work for G?
Click to expand...
Click to collapse
according to @redymedan yes.
ashyx said:
according to @redymedan yes.
Click to expand...
Click to collapse
I mean, will the TWRP work for G/DS?
I'm sorry for messing the thread...
I know the modified boot.img will work for G/DS.
But Oves said flashing TWRP and wipe data will make it work ( Correct me if I'm wrong)
Sent from my LG-H502 using XDA-Developers Legacy app
Berong said:
I mean, will the TWRP work for G/DS?
I'm sorry for messing the thread...
I know the modified boot.img will work for G/DS.
But Oves said flashing TWRP and wipe data will make it work ( Correct me if I'm wrong)
Click to expand...
Click to collapse
As long as the variants don't differ in CPU/SoC (Qualcomm/Exynos), with Samsung it never was a big deal to use twrp from a "brother" model. Always make a backup first before flashing critical system parts and keep the original odin flash file in handy.
Thanks. Now I know sir.
File not found
ashyx said:
◘ 1. Download the files below:
sm-j730gm_SR3-SuperSU-v2.79-SR3_root_boot_32
Click to expand...
Click to collapse
Hi. I read through this new thread, and the original thread by Oves (India) who was working on the root for the J730G/DS as well. @ashyx love the work, thank you very much. But when I click on the 32 bit root file on androidfilehost.com it gives me a 404 error, file not found.
I think the link is either broke, or the file has been removed. If people are reading the old thread, they may eventually make there way here to find the updated file.
Can you please repost the link for the proper file? Thanks again for all your hard work!
superkid333 said:
Hi. I read through this new thread, and the original thread by Oves (India) who was working on the root for the J730G/DS as well. @ashyx love the work, thank you very much. But when I click on the 32 bit root file on androidfilehost.com it gives me a 404 error, file not found.
I think the link is either broke, or the file has been removed. If people are reading the old thread, they may eventually make there way here to find the updated file.
Can you please repost the link for the proper file? Thanks again for all your hard work!
Click to expand...
Click to collapse
It hasn't been removed it's still working just checked.
Maybe try a different browser or disable any ad blockers.
That is strange, I still can't get it to work via Chrome or Firefox. I just tried it now on my mobile, same thing.
This is the link from the browser:
https://www.androidfilehost.com/?fid=673368273298979779"
Well, no worries, I'm sure somehow I will figure it out. I'm using the link on the first page of this thread for the 32 bit file.

[GUIDE] OTA Update Rootet(Magisk) H6X (Honor 6X)

I had trouble updating my Honor 6X (BLN-L21) after I rooted it, so I searched the whole xda to gain some information. Finally I made it, so I thought I could share this information with you guys, hope it helps, but I do not take responsibility if not, as you may have already heard, the Honor 6X (like every Kirin device) is very easy to brick.
- If everything is gone alright you should keep all of your data, apps and settings.
- If there is a big update, like from MM to N you maybe should backup all your stuff and relock the bootloader to update (big updates can relock frp so you can't unlock your bootloader then a rollback is the only way.
Successfully tried from:
B360 to B365
B365 to B367
Short Version (for expert users):
1. uninstall busybox bynaries and the Xposed Framework
2. uninstall magisk (inside the app)
3. flash stock recovery.img (of your actual firmware)
4. flash stock boot.img (of your actual firmware)
5. make OTA update (Reminder: safe update file)
6. flash twrp again and root
7. you are all done
Detailed Version:
#cmd commands#
1. backup your system over TWRP #adb reboot recovery# and do a backup there (for safety reasons)
2. #fastboot reboot#
3. uninstall busybox bynaries and the Xposed Framework(not just the app) (if you have it)
4. uninstall magisk (in app over "complete Uninstall button")
5. restart to bootloader #adb reboot bootloader#
6. flash stock recovery #fastboot flash recovery recovery.img# [use the recovery out of your actual firmware, how to extract is explained in the Forum I added at the end
7. flash stock boot #fastboot flash boot boot.img# [also use the extracted version of your actual package]
8. #fastboot reboot#
9. download update over OTA Update app (System update) in stock system. -> If the "System updater" app does not provide a Full version of the update package, the update could get stopped at 8% saying it could not verify the update, if so, just take the step to the error and reboot, if you then search for an update again, the "System updater" should now show you a Full version of the update package. like "BLN-L21C432B365-FULL"
10. you should safe that update files out of the HwOUC folder, so you can extract the recovery.img and boot.img later before you restart your device to do the update, because the system deletes these files after successful update
11. update over OTA Update app (System update) in stock system
12. restart to bootloader (#adb restart bootloader#)
13. flash twrp again #fastboot flash recovery twrp-3.1.1-0-berlin.img# [use the OpenKirin twrp edition (the official leads to a bootloop] -> [url]https://forum.xda-developers.com/honor-6x/development/twrp-t3583413[/URL]
14. Important is not to boot to system after flashing TWRP, exactly like as you installed it the first time. So you do #fastboot reboot# and then Vol down + lock
15. backup your system over TWRP (for safety reasons)
16. #adb reboot recovery#
17. flash Magisk zip in TWRP again
18. reboot in twrp
19. you are ready to go with the latest stock rom​
How to extract boot.img and recovery.img out of your actual firmware is explained here:
[url]https://forum.xda-developers.com/honor-6x/how-to/extract-stock-recovery-img-boot-img-img-t3676880[/URL] thanks @Khan ubaid​
citizenserious said:
the Honor 6X is very easy to brick.
Click to expand...
Click to collapse
Not just the 6X but every Kirin device.
This work only with packages like "xxxB360-FULL" or even with smaller downloaded packages that just updates some files? And, if I choose to do this with the FULL package do i have to re modify all the settings that i use actually?
RedSkull23 said:
This work only with packages like "xxxB360-FULL" or even with smaller downloaded packages that just updates some files? And, if I choose to do this with the FULL package do i have to re modify all the settings that i use actually?
Click to expand...
Click to collapse
I already tried it with the FULL package (edited the Guide btw.) you keep all your settings and stuff like before.
If it doesn't show you the FULL package just try the update until it fails, the system than will show you a FULL version of the update after the restart and research. That worked for me so far.
Hope I could help
citizenserious said:
I already tried it with the FULL package (edited the Guide btw.) you keep all your settings and stuff like before.
If it doesn't show you the FULL package just try the update until it fails, the system than will show you a FULL version of the update after the restart and research. That worked for me so far.
Hope I could help
Click to expand...
Click to collapse
What a nice notice, thanks dude! I already own the FULL, i only was worried about the fact that i could lose my data with the FULL one, i waa seeing it a clean firmware install but after this i can go straight with the update. I'll do that later today
RedSkull23 said:
What a nice notice, thanks dude! I already own the FULL, i only was worried about the fact that i could lose my data with the FULL one, i waa seeing it a clean firmware install but after this i can go straight with the update. I'll do that later today
Click to expand...
Click to collapse
I have done it that way yesterday, from B365 to B367 with the FULL package.
But nevertheless please back up your data.
edit: please let us know if it worked for you too
Thank for this guide. I might use this when an update comes.

			
				
[email protected] said:
Click to expand...
Click to collapse
What's the matter?
citizenserious said:
I have done it that way yesterday, from B365 to B367 with the FULL package.
But nevertheless please back up your data.
edit: please let us know if it worked for you too
Click to expand...
Click to collapse
Finally i found some time to dedicate on updating my phone, and I'm happy to say that it worked. I made from B360 to B365 and from B365 to B367, both worked at first shot. The only thing that i just can't understand is why the OTA package downloaded yesterday worked immediately, while the same B365-FULL package downloaded a month ago, copied on PC before starting it and later started didn't. With stock recovery and boot images obviously. I tried to start it later but nothing, i tried dload method with the update.app but neither that worked. Probably the OTA downloaded creates a sort of signature that can't be recreated that easily, if the same package fails through dload method... But what matters most is that now I'm on B367, protected with the latest security patch. Sorry for the late answer, time is hard to find... Thanks
Hi
Can someone upload the boot.img and and recovery.img from B367
Thanks in advance
Archerous said:
Hi
Can someone upload the boot.img and and recovery.img from B367
Thanks in advance
Click to expand...
Click to collapse
B367 of which model BLN-LXXCXXX?
shashank1320 said:
B367 of which model BLN-LXXCXXX?
Click to expand...
Click to collapse
I forgot sorry
BLN-L21C432B367
Archerous said:
I forgot sorry
BLN-L21C432B367
Click to expand...
Click to collapse
Check repository thread. Redskull23 has updated there. You may find in OP also in that thread. Link to the thread in my signature
shashank1320 said:
Check repository thread. Redskull23 has updated there. You may find in OP also in that thread. Link to the thread in my signature
Click to expand...
Click to collapse
There is no B367 in the Repository,no boot.img or recovery. thanks for you help
I wait for the next update,and i will not forget to save the update.app to pc. And extract the files
Archerous said:
There is no B367 in the Repository,no boot.img or recovery. thanks for you help
I wait for the next update,and i will not forget to save the update.app to pc. And extract the files
Click to expand...
Click to collapse
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
shashank1320 said:
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
Click to expand...
Click to collapse
I share ist,with the next update :good:
shashank1320 said:
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
Click to expand...
Click to collapse
If we find the B367 package I'll upload everything from it!
I was on rooted BLN-L24C5678B360, and I want to take the OTA 365, so I flashed stock recovery and boot, reboot into system and started the update, but it failed, afterwards the phone stuck at booting up screen.
I have to boot into fastboot and run "fastboot oem relock [my unlock code]" to relock it, then followed by a factory reset. But when it comes to update, it failed again. Upon reboot, it stuck again with the message "Your device has failed verification and may not work properly."
What did I do wrong?
Update: recovered with the official rollback software to 6.0.
shadowcliffs said:
I was on rooted BLN-L24C5678B360, and I want to take the OTA 365, so I flashed stock recovery and boot, reboot into system and started the update, but it failed, afterwards the phone stuck at booting up screen.
I have to boot into fastboot and run "fastboot oem relock [my unlock code]" to relock it, then followed by a factory reset. But when it comes to update, it failed again. Upon reboot, it stuck again with the message "Your device has failed verification and may not work properly."
What did I do wrong?
Click to expand...
Click to collapse
You can try full firmware for b365 if available via dload.
Unlock your bootloader and it will boot to twrp and then boot normally.

Samsung Galaxy Tab S7 Model SM-T875 finally Rooted

Hello. I have managed to Root My Samsung Galaxy Tab S7 Model SM-T875 with KNOX value 0x1 and no custom recovery has been installed. I am linking an image from Root Checker
bit.ly/3kOE6NW
Sorry for bitly link guys, this is my first post so not allowed to post url, pls understand
Only for SM-T875
If you have any other models, let me know, I will patch their boot.tar and provide link for the same
Steps for root :
Download and install the latest version of Magisk Manager
Make sure you have an unlocked boot loader
On your PC, download Odin and put your S7 into download mode
Flash the tar file listed here
I am linking the exact boot.tar image I used
bit.ly/3j4mYDw
Sorry for bitly link guys, this is my first post so not allowed to post url, pls understand
In Odin, select the AP option, make sure ur tab is connected in COM1 and then select the boot.tar file. Once flashed, you have to restart your device.
NOTE
Once this boot.img file is flashed you will get this an error saying your device is not on official firmware and you will have to hard reset your device, go ahead and hard reset your device, you might think its in bootloop but it is not. Once hard reset is done, your device will boot twice, make sure to press the power button each time to skip the unlocked bootloader warning. Once done, set up your tab as new one. Now Magisk Manager will not be installed on your device. For root , go ahead and install Magisk Manager again and this time Magisk will be installed in your device and your Knox value will be 0x1 and warranty will be void and device will be rooted
If any questions, please feel free to ask
Hope this helped you
Did someone confirmed?*I wait to got the root before to buy this model specifically
T870
Hi, can you please upload the patched boot img for SM-T870?
Thanks in advanced..
Sushantydv said:
Hi, can you please upload the patched boot img for SM-T870?
Thanks in advanced..
Click to expand...
Click to collapse
just copy and past the provided link address he gave into your browser and download
jionny said:
just copy and past the provided link address he gave into your browser and download
Click to expand...
Click to collapse
The link is for the t875 version mate.. i need image file for t870
Sushantydv said:
Hi, can you please upload the patched boot img for SM-T870?
Thanks in advanced..
Click to expand...
Click to collapse
Sure, here ya go
bit.ly/33DC7GM
If this img file is not flashing, make sure to tar it using 7-zip and then flash from ODIN.
This is the boot.img from the latest version of Android Q (release Sep 1) so make sure you're on the same version before flashing this.
Let me know if this worked or if you need the boot file for any other version
also, sry for bitly link, am not trying to profit out of this, once my 10 posts are complete, i'll post direct download links.
Thx for understanding
umibuzu said:
Did someone confirmed?*I wait to got the root before to buy this model specifically
Click to expand...
Click to collapse
Not that I should be saying this, but if you want to know, I have done the same steps on both of my Tab S7's and bot are working while being rooted. If you still want someone else to confirm, im totally fine with it. Thx for replying tho.
Sushantydv said:
The link is for the t875 version mate.. i need image file for t870
Click to expand...
Click to collapse
T870 XAR version. Be sure to select the proper ver... TH1 or TI4 or TJ4.
Updated 11-2-20
https://forum.xda-developers.com/galaxy-tab-s7/how-to/magisk-t4159291
Could you do t878?
jhill110 said:
T870 XAR version. Be sure to select the proper ver... TH1 or TI4 or TJ4.
Updated 11-2-20
https://forum.xda-developers.com/galaxy-tab-s7/how-to/magisk-t4159291
Click to expand...
Click to collapse
Is there a working custom recovery (TWRP) for the T875/870 yet? Haven't found anyone mention it so far.
rosrog said:
Is there a working custom recovery (TWRP) for the T875/870 yet? Haven't found anyone mention it so far.
Click to expand...
Click to collapse
Unfortunately no.
I have T875 TabS7 brand new I have Build number
QP1A.190711.020.T875XXU1ATI4 and device says upd are available ATJ4 Something. with october patch. The boot image you have linked is of which firmware ?. Should I update and then root.
EDIT:
Anyways i followed this guide by Dr ketan for rooting which i used for my Note 20 Ultra and it didnt work with patching AP file method.
https://forum.xda-developers.com/galaxy-note-20-ultra/how-to/guide-how-to-root-n20-ultra-t4147023
So i downloaded the latest firmware which was ATJ4 my CSC version was CAC so i downloaded same firmware from SAMFW(super website with downloads resumable via google drive option.
1. I extracted boot.img.lz4 from AP file of stock firmware downloaded and made a TAR file of it with 7Zip
2. Put it in phone and used magisk manager on tab to patch this file
3. Copy back to PC and flash via odin 3.14.3 in AP tab and uncheck auto reboot in ODIN
4. Booted straight into stock recovery and wiped/factory reset
5. Now i have root on Tab S7 T785.
Here is a link to boot file patched for TAB S7 N985 LTE Latest ATJ4 Firmware .
http://www.mediafire.com/file/mhss32jmt1b1oza/Patched_BooT_ATJ4_TAB_S7_N985.zip/file
Possible to Root SM-T878U ?
Smoker1 said:
Possible to Root SM-T878U ?
Click to expand...
Click to collapse
Yeah it might be.
I have gotten a TWRP up and running on my Galaxy Tab S7 but it's not functioning properly, I'll post the stable version here in case I figure out one haha.
I have the Tab S6 and I love it. I am thinking to buy the Tab S7+. I was very quick to root the Tab S6 and did not take much notice of the Knox trip. Is there any sell value if the tablet cannot have certain apps working such as secure folder? I understand even if you unroot and relock the bootloader then knox is still going to be changed to 0x1
My Tablet still seems to be 0x0 though.
CamronCamr said:
Yeah it might be.
Click to expand...
Click to collapse
Any luck on this? I also was dumb enough to get this T878U from ATT. I realize I have a signed locked bootloader. Is there any hope for us? I'm fairly technical and can follow directions
I'm in the same boat. Att locked out usb and wifi tethering. A rooted device would be very helpful.
Did you have any luck with magisk hide(safetynet)? I'm still waiting for fingerprint for magisk-hide-props-config.
Is this possible for the SM-T978U?
legokangpalla said:
Did you have any luck with magisk hide(safetynet)? I'm still waiting for fingerprint for magisk-hide-props-config.
Click to expand...
Click to collapse
On the latest Samsung Tab S7 T875 Stock firmware Android 11 and one UI 3.1 , i have it rooted with Magisk V22 , widevine is L1, and safetynet passed .
Running with following magisk modules
1. Magiskhide props Config (Just install no config set
2. Riru
3. Riru Edxposed
4. Universal safetynet Fix V2.00 Test version 2 Thanks to kdrag0n

Categories

Resources