Database Users

[HOW-TO] [ROOT] Root Samsung Galaxy Tab 2 7.0 P31XX using Linux

This guide will teach you how to root the Tab 2 7.0 P3110 and P3113 running Android version 4.1+ in Linux. I tested this with 4.1.2, but it should work on anything later and possibly ICS (This has not been tested in ICS, but I don't see why it wouldn't work.)
NOTICE: I am not responsible for what happens to your tablet! Make sure you use the correct files for your tablet model. This has been successfully tested on my P3113. THIS WILL VOID YOUR WARRANTY AND IF ANYTHING GOES WRONG COULD BRICK YOUR TAB!!! Proceed at your own risk!
Prerequisites: Admin account on Linux computer and tablet charged to 80% or higher
1. Download and install Heimdall and Heimdall Frontend from http://glassechidna.com.au/heimdall/
2. Download 51-android.rules and 70-android.rules from Files to Root ***.zip at the bottom of this post. Make sure you use the correct file for your tablet model.
3. Copy the .rules files into /etc/udev/rules.d and set as executable. Reboot computer
4. Copy the ***.pit from Files to Root ***.zip at the bottom of this post to the directory of your choice. Again, make sure you use the correct file for your tablet model.
5. Download SuperSU zip and this TWRP file for P311X or this TWRP file for P3100 (click names for links.) This version of TWRP will be able to flash KitKat and Lollipop ROMs. Decompress the TWRP tar.md5 file to get a recovery.img file and copy the SuperSU zip to your tablet.
6. Enable USB Debugging on your tablet and reboot into download mode (power off then hold in power and volume down)
7. Open Heimdall Frontend (make sure you run as admin) and click utilities then detect device. It should say "Device Detected"
8. Go into the flash section. In pit section, select the previously downloaded p311x.pit file. DO NOT check repartition.
9. In partition files section, click "Add." Select RECOVERY from the dropdown and select the recovery.img that you decompressed from the tar.md5 file.
10. Double check everything to make sure it is correct. Check the "No Reboot" box and click "Start."
11. If everything went well, you should get to 100%. Wait 10 seconds and disconnect the tablet from the computer. Reboot into recovery by holding down power and volume up.
12. Select "Install" and navigate to the SuperSU zip file. Flash the file and then click "Wipe Cache/Dalvik." Once that is done, select "Back" and "Reboot System"
You have now rooted your Tab 2 P31XX! If you have any question or need screenshots for something, feel free to post in the thread.
If I missed anything, please let me know!

Credits:
Glass Echidna & @Benjamin Dobell (Heimdall)
@Chainfire (SuperSU)
@Android-Andi (TWRP Recovery)
@jrc2 [me] (p311x.pit file, **-android.rules files)
@statmonkey (P3100 pit file)
AND whoever I found the tutorial from to make the android.rules file way back when...
If this thread was helpful, press the THANKS button!

reserved

reserved

Error
jrc2 said:
Over 600 views and no replies or thanks?!?! Hmm, I hope that this thread is still helping people. Bump
Sent from my SGH-T989
Click to expand...
Click to collapse
Thanks for this. Very well written guide and thought this would be a breeze ..... but .......
I am having an issue and not sure where to start looking. I have a GT-P3100 that I picked up in Thailand and am connecting from a Linux Debian box. Everything goes well until I try to add TWRP from Heimdall (Step 11). It starts through the process and then stops saying ERRORrotocol Intialisation failed. Heimdall is still connected, the device seems to be fine and I can reboot into my system with no issues but obviously can't go any farther since TWRP isn't there. I am using the TWRP that you suggested for the 3100 and have used the steps you suggested for that device.

statmonkey said:
Thanks for this. Very well written guide and thought this would be a breeze ..... but .......
I am having an issue and not sure where to start looking. I have a GT-P3100 that I picked up in Thailand and am connecting from a Linux Debian box. Everything goes well until I try to add TWRP from Heimdall (Step 11). It starts through the process and then stops saying ERRORrotocol Intialisation failed. Heimdall is still connected, the device seems to be fine and I can reboot into my system with no issues but obviously can't go any farther since TWRP isn't there. I am using the TWRP that you suggested for the 3100 and have used the steps you suggested for that device.
Click to expand...
Click to collapse
Did you do the download pit part for the 3100? It might use a different pit file. Also, what version of heimdall and heimdall front-end are you using? Did you run the front-end as root in terminal like this:
Code:
cd path/to/heimdall (CLICK ENTER)
sudo heimdall-frontend (CLICK ENTER)
Also, if you made a 3100 pit file, could you pm me link to download so I can post it here so other people can use it?
Sent from my SGH-T989

I just remembered what was causing that problem for me. After you download pit in Heimdall, disconnect the tab, reboot it, restart Heimdall, and boot back into download mode. Connect the tab to your computer and click on detect device. Put the pit file you downloaded from the tab in the pit space in the flash tab. Add the recovery image and click flash. I forgot in my previous post that after clicking on download pit, you have to reboot back into download mode and restart Heimdall to make it work.
Have a good day,
jrc2
Sent from my SGH-T989

jrc2 said:
I just remembered what was causing that problem for me. After you download pit in Heimdall, disconnect the tab, reboot it, restart Heimdall, and boot back into download mode. Connect the tab to your computer and click on detect device. Put the pit file you downloaded from the tab in the pit space in the flash tab. Add the recovery image and click flash. I forgot in my previous post that after clicking on download pit, you have to reboot back into download mode and restart Heimdall to make it work.
Have a good day,
jrc2
Sent from my SGH-T989
Click to expand...
Click to collapse
That makes some sense. When I was trying this before I really didn't grok on what the point was. It actually makes more sense to me that I would need to reset the environment. Anyway, will try and test this out as soon as I can. Thank you for your help and I pm'd that pit file to you.
---------- Post added at 11:02 PM ---------- Previous post was at 10:02 PM ----------
Sorry for the double post but I was a little giddy at the prospect of finally getting this done. Ran out of a dinner party to test this. Anyway, works a treat. Followed the additional notes to the letter and boom like that we are back and rooted. Many thanks!

statmonkey said:
That makes some sense. When I was trying this before I really didn't grok on what the point was. It actually makes more sense to me that I would need to reset the environment. Anyway, will try and test this out as soon as I can. Thank you for your help and I pm'd that pit file to you.
---------- Post added at 11:02 PM ---------- Previous post was at 10:02 PM ----------
Sorry for the double post but I was a little giddy at the prospect of finally getting this done. Ran out of a dinner party to test this. Anyway, works a treat. Followed the additional notes to the letter and boom like that we are back and rooted. Many thanks!
Click to expand...
Click to collapse
No problem. I'm going to put the pit file you pm'd me in the OP and add you to the credits.
Edit: done! No one else will have the problem you were having since I have the pit file uploaded. Thanks again for it.

Bump

Bumping so more can see this thread

I can only guess that the reason why this thread has so few comments is because it works so well. It was a lifesaver for me. Thanks again.

TWRP links are dead any updates?

nutpants said:
TWRP links are dead any updates?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC

smart-t78 said:
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
Click to expand...
Click to collapse
Man that was fast, impressive.
This device, on this build has been one of the most stable and useful mods I have ever done. I love this device and the root/etc. have worked so perfectly over the years that I often forget that it is rooted. This is the way it is supposed to be, but often (due to manufacturers, brands who monkey too much, carriers, or whoever) is not. I just want to thank again all who worked so hard on the galaxy tab 2.0 stuff.

Root D6603 on .77 by downgrade, no data wipe

I managed to use giefroot root my D6603 (US version) on firmware 23.0.1.A.5.77 by downgrading to 23.0.A.2.93 without wiping the whole /data.
This is what I did: (Try at your own risk!)
1 Backup the contacts first. The contacts data will be cleared.
2 Use Flashtool to flash D6603_23.0.A.2.93_Generic_20GLOBAL.ftf. Uncheck wipe DATA.
3 Restart the device. There will be lots of annoying force close popups. For me, only two packages were reported closing: android.process.acore and android.process.media. USB debugging doesn’t work either.
4. Just close the popups and go to Settings – Apps – All. Find “Media Storage” and press “clear data” to get rid of FCs of android.process.media. USB debugging should work now.
5. Find “Contacts Storage” and press “clear data”. No more FCs of android.process.acore.
After this, no more FC popups for me. It looked normal on fw 2.93 and I tried many times to use giefroot v2 but failed. It seems like that the system exploit app CVE-2014-7911 will crash android.
6. I tried clearing data of more apps. After clearing ApplicationSettings and ConfigUpdater, giefroot v2 worked! I don’t know which one is the key. Can anyone confirm?
Hope it's helpful for you.
Thanks again! @zxz0O0

I followed your steps and after a few tries i got root. The only thing i did diferrent was that i enabled "Allow mock locations" and it worked.
Thanks @zxz0O0

carasd said:
I followed your steps and after a few tries i got root. The only thing i did diferrent was that i enabled "Allow mock locations" and it worked.
Thanks @zxz0O0
Click to expand...
Click to collapse
Yes, you are right. After my steps, one still needs to follow the instructions of giefroot by zxz0O0:
How to use
Download the tool (latest version) and extract it
Start your device and plug it to your computer
Put your device in air plane mode
Run install.bat and follow the instructions on screen
Congratulations! You should now be rooted. If you get an error "Device not rooted", try running the tool a second time.
Click to expand...
Click to collapse

It worked
This works like a charm. I followed every step to the T and im rooted. Awesome Job.

It worked
thanks for this useful tip. Step 6 was not needed with D6603_23.0.A.2.98_Customized_20DE.ftf and giefroot v2.

I've heard that you can create a pre rooted version of the latest update, is this possible or will I have to stick with the downgrade?

lalala2003 said:
I've heard that you can create a pre rooted version of the latest update, is this possible or will I have to stick with the downgrade?
Click to expand...
Click to collapse
There's already a pre-rooted version which you can flash in recovery

Thanks for this guide!
The only problem I'm having is, once rooted and with the dual-recovery installed, I can't decrypt my device in TWRP. It asks for my password, but tells me it's wrong and just asks for the password again. If I choose 'cancel' it continues but won't load anything off my sd card/internal. So I can't flash the update to .77
Anyone know why this might be?
---------- Post added at 09:45 PM ---------- Previous post was at 09:25 PM ----------
omnikai said:
Thanks for this guide!
The only problem I'm having is, once rooted and with the dual-recovery installed, I can't decrypt my device in TWRP. It asks for my password, but tells me it's wrong and just asks for the password again. If I choose 'cancel' it continues but won't load anything off my sd card/internal. So I can't flash the update to .77
Anyone know why this might be?
Click to expand...
Click to collapse
I seem to have gotten around this for now by using adb push to copy the file to the /tmp folder of my device. I still can't access internal storage, which is a pain, but at least I can finish the steps to get back to .77 (and hopefully Lollipop soon!).

omnikai said:
Thanks for this guide!
The only problem I'm having is, once rooted and with the dual-recovery installed, I can't decrypt my device in TWRP. It asks for my password, but tells me it's wrong and just asks for the password again. If I choose 'cancel' it continues but won't load anything off my sd card/internal. So I can't flash the update to .77
Anyone know why this might be?
---------- Post added at 09:45 PM ---------- Previous post was at 09:25 PM ----------
I seem to have gotten around this for now by using adb push to copy the file to the /tmp folder of my device. I still can't access internal storage, which is a pain, but at least I can finish the steps to get back to .77 (and hopefully Lollipop soon!).
Click to expand...
Click to collapse
Sorry that I know nothing about the decryption. After a quick search, it seems to me probably a bug of TWRP (github.com/TeamWin/Team-Win-Recovery-Project/issues/247).

lalala2003 said:
I've heard that you can create a pre rooted version of the latest update, is this possible or will I have to stick with the downgrade?
Click to expand...
Click to collapse
Yes. Once you root your phone and have the dual recovery installed, you can use the pre rooted image to upgrade to the latest version and keep root.

hi
hello sir. i deleted everything on your step. now i cant access my wifi. how can i return it again? thanks. noob here.

nivek4th said:
hello sir. i deleted everything on your step. now i cant access my wifi. how can i return it again? thanks. noob here.
Click to expand...
Click to collapse
Flash a FTF file but exclude the system

hi
gregbradley said:
Flash a FTF file but exclude the system
Click to expand...
Click to collapse
i already flashed a latest firmware i can't root my phone even in the old firmware. i followed all the steps.

nivek4th said:
i already flashed a latest firmware i can't root my phone even in the old firmware. i followed all the steps.
Click to expand...
Click to collapse
Then you must be doing something wrong
You can try to force a software repair using PCCompanion,

gregbradley said:
Then you must be doing something wrong
You can try to force a software repair using PCCompanion,
Click to expand...
Click to collapse
i flashed version 23.0.1.A.5.77 everything went back to normal. when i will flash again the older FW the acore stopped and media stopped gonna show again and when i deleted everything in the step it disappears but i cant root. i tick the debug and allow mock even put it into airplane mode. but CVE is showing up. not rooted.

it works, thanks a lot!

Worked perfekt. Thanks!

nivek4th said:
i flashed version 23.0.1.A.5.77 everything went back to normal. when i will flash again the older FW the acore stopped and media stopped gonna show again and when i deleted everything in the step it disappears but i cant root. i tick the debug and allow mock even put it into airplane mode. but CVE is showing up. not rooted.
Click to expand...
Click to collapse
On the older FW, did you clear the data of ApplicationSettings and ConfigUpdater as well (as in Step 6)?

Friends have achieved to root my phone, it also improves the latest system version and everything is great I put the dual recovery 2.8.2 and of there add Xposed. But after a day in the early morning the phone started to constantly reboot, try to get into recovery mode and freezes with the logo of Sony. turn off and turn on in normal mode, install the recovery again and I wipe cache and dalvik, every normal by day and in the early morning again restarts. PLEASE any solution

Has anyone managed to successfully downgrade from a LP firmware (ex. 690 or .726) back to .93, a KK firmware, without having to wipe using this method?

Cant get my Verizon S5 runnig after trying to get CM 14.1

Hi Guys,
Im litterlay close to breaking down after trying to get Lineageos 14.1 running on my G900V verizon S5 for more than 12 hours now.
I followed various youtube tutorials and the guide given in this article https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848.
The last thing i tried was unlocking the bootloder following a yt tutorial... now the phone pretty much freezes when booting showing the galaxy s5 and the custom android logo, it even plays the booting sound of samsung but after nothing happens. All i tried since was trying to get it back to stock 4.4.2 but when i use ODIN it gives me the error " sw rev check fail aboot fused 2 binary 1".
At the moment i literally lost hope to ever get nougat to run on this f***kin verizon phone, all i want is to get it to run again on something newer than 4.4.4 :crying:
I´ll be so glad for any help and if you could even help me get 14.1 to run on it id love you guys for ever.
Edit: I can still get into recovery and download mode but cant get into safestrap anymore, but i do have a backup of the system 4.4.2 with root and safestrap on my pc would there be a way to use that?

Marv95 said:
" sw rev check fail aboot fused 2 binary 1"
Click to expand...
Click to collapse
It means that you've flashed a firmware newer than BOK3 at least once.
No chance to flash 4.4.2 with Odin any more.
If you just need a working VZW phone - simply download a stock firmware BOK3 or newer and flash it with Odin.
The first boot will take 15 min or so.
If you need something else - tell what you would like to have.

wow simple as that? well awesome but then what would you recommend me to do next? is there a way to still get cm 14.1 on the verizonphone or should i just go with stock 6.1 and accept all the verizon bloatware bulls** :/

@Marv95
I cannot recommend anything, you have to decide yourself.
But the first thing you need is to have a working phone back and check the CID of your device.
If it's 15 then you'll be able to install LOS. If it's 11 - you won't.
I'd have a look at this topic. No need to flash back a stock firmware, you may begin with COMBINATION_VZW_FA44_G900VVRU2APA1

Well awesome thanks so far, ill check the cid :good: do you have a link where i can get the G900VVRU2BOK3 - GALAXY S5 SM-G900V VZW USA firmware the sammobile download takes 2 hours
Edit: https://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-t3281095 , this a right one (VZW_BOK3_ODEX_DEODEX_V2.zip)??

Marv95 said:
Well awesome thanks so far, ill check the cid :good: do you have a link where i can get the G900VVRU2BOK3 - GALAXY S5 SM-G900V VZW USA firmware the sammobile download takes 2 hours
Click to expand...
Click to collapse
I think this is it.
https://androidfilehost.com/?fid=24349802275799044

well first of all thank you so much the phone is working again but sadly cid shows 11 so no cm14.1...guess 13 wont work then either? will have a closer look for what to do next this evening my goal would be the most uptodate firmware (german language support would be the dream since somehow this verizonfirmware [like the old 4.4.4] only supports english)

Marv95 said:
guess 13 wont work then either?
Click to expand...
Click to collapse
The locked bootloader (that cannot be unlocked) matters, not CM/LOS version.
The locked bootloader cannot boot unsigned kernel, that's why you're limited to Touchwiz-based roms only.
my goal would be the most uptodate firmware (german language support would be the dream since somehow this verizonfirmware [like the old 4.4.4] only supports english)
Click to expand...
Click to collapse
German? Not a big problem. So Verizon is not your provider?

bbsc said:
The locked bootloader (that cannot be unlocked) matters, not CM/LOS version.
The locked bootloader cannot boot unsigned kernel, that's why you're limited to Touchwiz-based roms only.
German? Not a big problem. So Verizon is not your provider?
Click to expand...
Click to collapse
No i use a german Simcard (Netzclub) only the phone is a Verizon sent to me from the US

Marv95 said:
No i use a german Simcard (Netzclub) only the phone is a Verizon sent to me from the US
Click to expand...
Click to collapse
Well, I'm in the similar boat.
Let's see and decide. Netzclub means O2 network, which means B20 band for LTE, which is definitely not supported by device. So we can forget it.
German general CSC is DBT.
Ok, I'd say, your choice is this stock-like cleaned ROM for SM-G900F and the latest DQF2 firmware for SM-G900V. CSC must be DBT.
It's a little tricky to flash, but possible.
You'll have a phone that looks like F variant with German and so on.
But you won't have root.
Do you need root?

bbsc said:
Well, I'm in the similar boat.
Let's see and decide. Netzclub means O2 network, which means B20 band for LTE, which is definitely not supported by device. So we can forget it.
Click to expand...
Click to collapse
You mean i cant use LTE with that phone here in Germany? Actually never tried it before lol but was recently thinking bout switching provider to get the benefits
German general CSC is DBT.
bbsc said:
Ok, I'd say, your choice is this stock-like cleaned ROM for SM-G900F and the latest DQF2 firmware for SM-G900V. CSC must be DBT.
Click to expand...
Click to collapse
Ok so root the device, get custom recovery, install the rom and then flash the firmware G900FXXS1CQD4 - GALAXY S5 SM-G900F DBT Germany (Sammobile [CSC: G900FDBT1CQA1] even though its not for verizon phone) with odin?
bbsc said:
It's a little tricky to flash, but possible.
You'll have a phone that looks like F variant with German and so on.
But you won't have root.
Do you need root?
Click to expand...
Click to collapse
well would´ve played around with it a bit since i invested that much time to get used to this damn phone now but no actually i dont :laugh:

Marv95 said:
but no actually i dont :laugh:
Click to expand...
Click to collapse
Good decision.
Sorry, I'm a little busy at the moment, but I'll give you some directions ASAP.
You need to download:
1. This service firmware.
2. Alexndr's firmware (G900FXXU1CQG1_DevBase_v4.3.zip)
You do have Odin already.
You'll need some more files, I'll prepare them for you a little later.

Here we go.
1. Check if Reactivation Lock is disabled. Charge the battery to more than 50%.
2. Download Odin (you should already have it) and COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 (link is in my previous post).
3. Download applications and firmware files - CID11_DBT.zip
4. Download ROM file - G900FXXU1CQG1_DevBase_v4.3.zip (link is in my previous post).
5. Run Odin.exe.
6. Select COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in Odin's AP slot, boot the phone into the download (Odin) mode, connect with USB cable to the computer, press Start, wait till the flash process is finished. Press Exit and wait for the phone to complete reboot.
7. Disconnect USB cable from the phone and connect again.
8. Unzip CID11_DBT.zip into the CID11_DBT forlder on the Desktop.
9. Copy everything from CID11_DBT folder to the root of phone's internal memory. IMPORTANT: options.prop should appear in the root of phone's memory, not in a subdirectory.
(Root means that root which you can see in your Windows File Explorer, not the absolute root from the phone's side. Really it's /sdcard/ from the phone's side.)
10. Copy ROM file G900FXXU1CQG1_DevBase_v4.3.zip to the root of phone's internal memory.
11. Disconnect the cable from the phone.
12. Press Menu (dotted button) - My Files - All - RootS5.
13. Apex_Launcher.apk - Settings - Unknown Sources - Ok - Back - Apex_Launcher.apk - Next - Install - Done.
14. BusyBox.apk - Install - Done.
15. Safestrap_KK.apk - Install - Done.
16. tr_v2.apk - Install - Open - make it rain (a message "You should have root, no reboot required" should appear) - Back.
17. Superuser.apk - Install - Open - Continue - Normal - Reboot.
18. After reboot, in the pop-up window - Apex Launcher - Always - Ok.
19. Menu (dotted button) - BusyBox Free - Grant - close balloon - Install - close balloon - Back.
20. Safestrap - Grant - Agree - Install Recovery - Reboot to recovery. Wait patiently for SafeStrap Recovery to boot.
21. Swipe to Allow modifications - Wipe - Advanced Wipe - Dalvik/Data/Cache - Swipe to Wipe.
22. Back - Back - Back - Install, install G900FXXU1CQG1_DevBase_v4.3.zip.
23. Back - Back - Mount - check System.
24. Back - Advanced - File manager - go to /sdcard/ and copy these files:
- /sdcard/build.prop - to /system/;
- /sdcard/others.xml - to /system/CSC/;
- /sdcard/others.xml - to /system/CSC/DBT/system/csc/.
25. Go to /system/, highlight build.prop, change file's permissions to 0644 (chmod 0644).
26. Go to /system/CSC/, highlight others.xml, change file's permissions to 0644 (chmod 0644).
27. Go to /system/CSC/DBT/system/csc/, highlight others.xml, change file's permissions to 0644 (chmod 0644).
28. Exit File manager pressing Back. In the main menu - Mount - uncheck System - Back - Install.
29. Install DQF2_Firmware_Bootloaders.zip. Then Reboot System - Do not install.
30. The phone will reboot. The first boot takes 10 min. or so.
After all you may erase all the files from the phone's memory or perform a factory reset from menu or Recovery.

Thanks ill try this evening after work :good::good::good:

Awesome mate, awesome thank you so much it worked without any problems :highfive::good::good:

Ok, glad it helped.
Now you have the most up-to-date SM-G900V: system - G900FXXU1CQG1 (changelist 9493471, security patch 2017-07-01) and firmware -G900VVRS2DQF2 (changelist 8025411, security patch 2017-07-01)

bbsc said:
Ok, glad it helped.
Now you have the most up-to-date SM-G900V: system - G900FXXU1CQG1 (changelist 9493471, security patch 2017-07-01) and firmware -G900VVRS2DQF2 (changelist 8025411, security patch 2017-07-01)
Click to expand...
Click to collapse
One more question somewhere between step 23 and 28 would it have been possible to install newest emoji package or even iphone emojis into systemfiles? or is it to late to just do all the steps above again
because i feel like i now see even less emotes than before

1. It cannot be late to revert the things back as you haven't done anything irreversible.
You can at any moment just flash a stock Verizon firmware and get a "stock" phone.
You can at any moment start with my guide from the beginning too.
2. You're right, after 23 but before 28 you have full access to /system and can install or copy something there.
3. Generally, you can leave Safestrap Recovery in the system.
On the one hand, you'll be able to access system files from time to time when you need.
On the other hand, some apps with higher security demands may not work (say, bank applications or so).
If you decide you need it, you'll have to install it after 22 before 23. Let me know and I'll give you necessary files.
P.S. I don't know what "emoji package" is. Maybe it can be installed as app or font or something that does not need direct /system access. It's always a good idea to place your data to /data, not to /system.

P.S. I don't know what "emoji package" is. Maybe it can be installed as app or font or something that does not need direct /system access. It's always a good idea to place your data to /data, not to /system.[/QUOTE]
More or less im talking bout this https://forum.xda-developers.com/general/general/mod-google-keyboard-unicode-9-10-emojis-t3348544/

bbsc said:
P.S. I don't know what "emoji package" is. Maybe it can be installed as app or font or something that does not need direct /system access. It's always a good idea to place your data to /data, not to /system.
Click to expand...
Click to collapse
More or less im talking bout this https://forum.xda-developers.com/general/general/mod-google-keyboard-unicode-9-10-emojis-t3348544/

Need help unbricking my Galaxy S7 edge SM-G935P phone

I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.

Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
bothambhai said:
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Click to expand...
Click to collapse

just checking... are you using the edited princecomsy odin? http://d-h.st/gsDA or use the link here https://forum.xda-developers.com/att-s7-edge/help/princes-odin-t3545104
find the correct rom here https://forum.xda-developers.com/sprint-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3569834
just use files from one rom at a time. get good at that first. maybe you are careful but it really looks like you were guessing what goes where at the end of your post.
i just have tips on what helped me. passing along the info and the link.

epikroms said:
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
Click to expand...
Click to collapse
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.

bothambhai said:
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
Click to expand...
Click to collapse
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS

epikroms said:
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
Click to expand...
Click to collapse
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?

bothambhai said:
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
Click to expand...
Click to collapse
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it

epikroms said:
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
Click to expand...
Click to collapse
Thanks for your reply. If it is not too much can you please break down the steps a bit more because I don't want to guess and mess it up again and also if you could please kindly point me to the other thread as well so I can download the appropriate stuff from there and read a bit more about it. I am right now unable to use the phone with the sprint firmware on it on TMo, it's super annoying.
Thanks in advance.

https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375

Did you get it sorted out? Hopefully you are on the rom and haven't bricked your device. I attached a picture so you could see that I am on what I say I am on.

epikroms said:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Click to expand...
Click to collapse
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?

bothambhai said:
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
Click to expand...
Click to collapse
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help

thats pretty interesting being on the binary 5 baseband and binary 4 rom. to clarify, you were on the binary 5 rom and reverted? or were you on the baseband 4 and upgraded just the baseband? thanks for the info.

epikroms said:
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
Click to expand...
Click to collapse
I odined the AP_Nougat_S7_Edge_EngBoot.tar.md5 then ran the root.bat file from Nougat_S7_Root_2_82_All_Carriers_V2 , I chose the options to install the fingerprint fix and install the root without any gpu tweaks. I watched the whole process complete and the cmd prompt close, my phone never asked my permission to ALLOW anything, everything was on the computer. I ran the root.bat from cmd as an administrator and the program ran evidently because it asked me about the fingerprint fix and root with or without tweaks etc. I noticed the phone reboot and there was a notification, the phone was rooted but no SU and flashwire says no root access. I tried it back from square one a couple of tries more right back from flashing stock sprint firmware and trying the whole rooting process again, same results except the next two times the phone doesn't reboot after running the root.bat file. I notice now when the phone boots up there is a sign saying "CUSTOM" beneath the samsung logo on the screen. I don't know where I am going wrong in the process though. I don't know if it is because I am on the binary 5 however I also read somewhere that people have been successful in rooting their binary 5 sprint S7 edges. I have rooted many devices before and installed roms etc, this has been, by far, the most perplexing phone in every which way.

Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.

epikroms said:
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
Click to expand...
Click to collapse
Bummer about your phone. On a glad note I managed to root and flash my phone and everything works great now. I was taking the hard nerdy way to do it by running cmd as an administrator and having that run the root.bat file. I read somewhere else you could just double click the file and it worked for me . From there on the aroma part was pretty straightforward. I am grateful to you for pointing me in this direction and breaking it down for me, I seriously doubted me being able to achieve this on my binary 5 phone but it turned out to be smooth.
I do wish you the best and thanks once again.

problem with Galaxy A03. after Odining the phone it seem to black screen. I think the phone turn off. (Magisk, Frija)

hello everyone, first poster here:
point:
-first time Rooting
-has unlock Bootloader( at least according to the https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root . bootloader was grayout in developer option)
used this tutorial: https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
timeline:
-used frija to get the Firmware (model: SM-A035F. have check extensively in the phone what was my Model and CSC) ((got firja from Github by SlackingVeteran)
-install Magisk on to the phone (version: v25.1)
-copy and paste the AP.tar.md5 into Phone's download folder, using Window's File explorer.
-Magisked the AP.tar.md5 in the download folder.
-using ADB to pull the Magisked AP.tar folder into C:/folder
-gone to the downloading custom OS interface
-Use Odin3 v.314 with the Magisked AP, original BL, CP, and CSC. DIDN'T used HOME_CSC_OMC. auto Reboot is on.
-i have gone to the toilet while waiting for Odin to finish.
-comeback to only see glimpse of the samsung Logo before blackscreen(no power). (odin app said installation was complete)
-wait for 1 hour. nothing
try to get into recovery mode. so far the phone hasn't comeup with anything. (tried Volume up + power button, Volume up & down + power button, Volume up & down, power button only. i think i hold the button for about 14 second?)
ummmmm yeah... this might be my last hope of not hard bricking this phone.
Also, this was a off the shelve new Galaxy A03, so there shouldn't be any wear and tear.
Edit: sorry in advanced. I couldn't find the Galaxy A03 in the samsung section( had try web search)

Flash boot.img.tar only using Odin
Don't flash the whole AP

Your phone turned off right? Go to a cellphone technician and tell him to battery shock your phone.

I've experienced that issue before

tata33003 said:
hello everyone, first poster here:
point:
-first time Rooting
-has unlock Bootloader( at least according to the https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root . bootloader was grayout in developer option)
used this tutorial: https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
timeline:
-used frija to get the Firmware (model: SM-A035F. have check extensively in the phone what was my Model and CSC) ((got firja from Github by SlackingVeteran)
-install Magisk on to the phone (version: v25.1)
-copy and paste the AP.tar.md5 into Phone's download folder, using Window's File explorer.
-Magisked the AP.tar.md5 in the download folder.
-using ADB to pull the Magisked AP.tar folder into C:/folder
-gone to the downloading custom OS interface
-Use Odin3 v.314 with the Magisked AP, original BL, CP, and CSC. DIDN'T used HOME_CSC_OMC. auto Reboot is on.
-i have gone to the toilet while waiting for Odin to finish.
-comeback to only see glimpse of the samsung Logo before blackscreen(no power). (odin app said installation was complete)
-wait for 1 hour. nothing
try to get into recovery mode. so far the phone hasn't comeup with anything. (tried Volume up + power button, Volume up & down + power button, Volume up & down, power button only. i think i hold the button for about 14 second?)
ummmmm yeah... this might be my last hope of not hard bricking this phone.
Also, this was a off the shelve new Galaxy A03, so there shouldn't be any wear and tear.
Edit: sorry in advanced. I couldn't find the Galaxy A03 in the samsung section( had try web search)
Click to expand...
Click to collapse
I have had the same issue. After waiting for the battery to completely run down then I was able to get into download mode.

have you sort out your problem? I just have the same issue, after flash BL, AP rooted, CP, CSC my phone dead, totally b;lack screen and no life signal, could someone help me please, an if have any link how to root SM-a035M/DS could I have it please, i really didn't find it... thanks a lot

JefersonLHP said:
have you sort out your problem? I just have the same issue, after flash BL, AP rooted, CP, CSC my phone dead, totally b;lack screen and no life signal, could someone help me please, an if have any link how to root SM-a035M/DS could I have it please, i really didn't find it... thanks a lot
Click to expand...
Click to collapse
Mine is sm-a035f/ds. Wait for a few days and then try again. Or you can get it battery shocked. I don't recommend rooting phones because I don't see the gain in it.

apreciate that, unfortunately I need root it the question is that is possible? SM-A305M/DS?

JefersonLHP said:
apreciate that, unfortunately I need root it the question is that is possible? SM-A305M/DS?
Click to expand...
Click to collapse
That is very much possible but I don't see the point in it. Why so? It trips knox and that is irreversible. Banking apps will NOT work. Some more apps like Netflix will break too. Now wonder. Is it worth the effort? Btw why are you trying to root it? There's a solution to every problem these days without root.

JefersonLHP said:
have you sort out your problem? I just have the same issue, after flash BL, AP rooted, CP, CSC my phone dead, totally b;lack screen and no life signal, could someone help me please, an if have any link how to root SM-a035M/DS could I have it please, i really didn't find it... thanks a lot
Click to expand...
Click to collapse
You can also use an otg cable to drain the battery quickly... just plug in a usb device that uses a lot of power like a usb fan... it works 90% of the time ( as long as the phone is on it is able to "see" the device and automatically tries to charge it )

JefersonLHP said:
have you sort out your problem? I just have the same issue, after flash BL, AP rooted, CP, CSC my phone dead, totally b;lack screen and no life signal, could someone help me please, an if have any link how to root SM-a035M/DS could I have it please, i really didn't find it... thanks a lot
Click to expand...
Click to collapse
Found the issue, ignore whatever I said before. Flashing only boot.img works. Not patched ap and others. Just flash stock firmware, let it boot, then patch only boot.img from ap file and then patch and flash it. I am running my phone rooted now.

[How To] How to root Samsung Galaxy A03 the proper way
This is my first guide. Please forgive me for any mistakes and please alert me if there are any. Some Samsung phones and tablets are having bootloops when flashing patched AP file. This guide gives you root and no bootloops! These issues will...
forum.xda-developers.com
I made a guide for this device with proper instructions to root.

Deleted member 12167035 said:
Iy Found the issue, ignore whatever I said before. Flashing only boot.img works. Not patched ap and others. Just flash stock firmware, let it boot, then patch only boot.img from ap file and then patch and flash it. I am running my phone rooted now.
Click to expand...
Click to collapse
Wait so how did you make it boot up then ?

Huyqwerty said:
Wait so how did you make it boot up then ?
Click to expand...
Click to collapse
You actually replied to a deleted users account....err it was me anyways. I shifted to a new account.
Anyways, I made it boot up by booting up the phone (what kind of question was that??)

Hyperio546 said:
You actually replied to a deleted users account....err it was me anyways. I shifted to a new account.
Anyways, I made it boot up by booting up the phone (what kind of question was that??)
Click to expand...
Click to collapse
I meant your phone was unable to boot after you try to root, how did you make it boot up after that ?

Huyqwerty said:
I meant your phone was unable to boot after you try to root, how did you make it boot up after that ?
Click to expand...
Click to collapse
It was bootlooping so I just waited for the battery to run down and then booted to download mode, flashed stock firmware and fixed it. I was able to root by flashing only the patched boot.img.

Hyperio546 said:
It was bootlooping so I just waited for the battery to run down and then booted to download mode, flashed stock firmware and fixed it. I was able to root by flashing only the patched boot.img.
Click to expand...
Click to collapse
Oh, thanks for the reply. Have you found any ways to stop scoped storage ?

Huyqwerty said:
Oh, thanks for the reply. Have you found any ways to stop scoped storage ?
Click to expand...
Click to collapse
Not possible because magisk in systemless.