Trying to install root on my t350, when i try to boot into recovery mode for twrp the screen says WARRANT BIT: RECOVERY in corner but then goes to black screen. I tried holding it a while but twas' to no avail......
What did i mess up now?
le boi said:
Trying to install root on my t350, when i try to boot into recovery mode for twrp the screen says WARRANT BIT: RECOVERY in corner but then goes to black screen. I tried holding it a while but twas' to no avail......
What did i mess up now?
Click to expand...
Click to collapse
Are you running nougat? And did you happen to flash CF autoroot, or TWRP for Marshmallow?
Spaceminer said:
Are you running nougat? And did you happen to flash CF autoroot, or TWRP for Marshmallow?
Click to expand...
Click to collapse
i didnt update my tablet in the recent update so i dont think i am
How would i go about checking?
EDIT: im running marshmellow
now..... i made a cf auto root file from firmware.mobi but it failed flashing..............
Edit: Unsupport dev_type
ADB
Have you tried seeing if ADB detects your device? Try ADB reboot recovery and if it says waiting for device for a long time then there must be wrong with your device. I am currently working on a flashable zip that has root so it might be root. If it is root and you get recovery working I'll post the flashable zip for you to flash.
le boi said:
now..... i made a cf auto root file from firmware.mobi but it failed flashing..............
Edit: Unsupport dev_type
Click to expand...
Click to collapse
Use the latest version of ODIN
just saying, the cf auto root u made from firmwaremobi will not work. It didn't work for me either and it soft bricked my SM-T350. To fix it, and properly root it, all u need is the cf auto root file from the old site. The version for marsmallow worked for me, even though im on android Nougat.
Related
Hello, I'm having a problem when rooting my device. I've successfully flashed the CF-Auto-Root file and it says "PASS" in Odin but the phone boots into recovery and won't boot to the OS and the recovery is showing this message: "Recovery is not Seandroid enforcing".
I've used this file to root: http://download.chainfire.eu/727/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltedx-smg900f.zip How can I fix this? I've flashed BOB7 stock and the phones back to normal but I need to root in order to install a custom recovery (Philz)
Thanks.
KayKrate said:
Hello, I'm having a problem when rooting my device. I've successfully flashed the CF-Auto-Root file and it says "PASS" in Odin but the phone boots into recovery and won't boot to the OS and the recovery is showing this message: "Recovery is not Seandroid enforcing".
I've used this file to root: http://download.chainfire.eu/727/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltedx-smg900f.zip How can I fix this? I've flashed BOB7 stock and the phones back to normal but I need to root in order to install a custom recovery (Philz)
Thanks.
Click to expand...
Click to collapse
You can try this if you want it works when using TWRP recovery but not sure about Philz
Make sure you don't have super user app installed on your phone
Download the attached zip and put it in a folder on your phones internal storage
Install Philz custom recovery via Odin
When the phone reboots go to the market and install Chainfires SuperSU, this one here
Once installed reboot phone into recovery and install the zip file you downloaded above
Reboot the phone and go to the SuperSU app and tap it, give it a moment and it should ask for you to grant root access
If it has worked as it does with TWRP you will be rooted, let me know if it works or not.
ag4751 said:
You can try this if you want it works when using TWRP recovery but not sure about Philz
Make sure you don't have super user app installed on your phone
Download the attached zip and put it in a folder on your phones internal storage
Install Philz custom recovery via Odin
When the phone reboots go to the market and install Chainfires SuperSU, this one here
Once installed reboot phone into recovery and install the zip file you downloaded above
Reboot the phone and go to the SuperSU app and tap it, give it a moment and it should ask for you to grant root access
If it has worked as it does with TWRP you will be rooted, let me know if it works or not.
Click to expand...
Click to collapse
I don't really want to risk anything , I've also noticed that there are 2 CF-Auto-Root files , one that says kltedx and other that says kltexx. Should I give the other one (kltexx) a try? Also , my friend told me that I need to root first and then install a custom recovery (Philz).
KayKrate said:
I don't really want to risk anything , I've also noticed that there are 2 CF-Auto-Root files , one that says kltedx and other that says kltexx. Should I give the other one (kltexx) a try? Also , my friend told me that I need to root first and then install a custom recovery (Philz).
Click to expand...
Click to collapse
I never mentioned CF Auto Root the process mentioned above doesn't use it. it is just TWRP Recovery 2.4 or higher you install via Odin
Then SuperSu form the marked
Then boot into recovery and install the zip file which updates SuperSU binary to give root access
That's it, no CF Aoto Root
ag4751 said:
I never mentioned CF Auto Root the process mentioned above doesn't use it. it is just TWRP Recovery 2.4 or higher you install via Odin
Then SuperSu form the marked
Then boot into recovery and install the zip file which updates SuperSU binary to give root access
That's it, no CF Aoto Root
Click to expand...
Click to collapse
Are you sure that your method is going to work on my G900F? I'm on Lollipop OB7 if that makes any difference.
KayKrate said:
Are you sure that your method is going to work on my G900F? I'm on Lollipop OB7 if that makes any difference.
Click to expand...
Click to collapse
It is totally tour choice to try or not, my phone details are in the screen clip attached
ag4751 said:
It is totally tour choice to try or not, my phone details are in the screen clip attached
Click to expand...
Click to collapse
Same as mine , so you've used exact same method on the same firmware version (BOB7) ?
Nevermind , It appears that there's another G900F , one's kltexx and kltedx and kltexx worked for me and the other didn't. Thanks for helping tho
Hi everyone,
After my A700YD upgrade to android 5.0.2, I cannot find a feasible solution to root my phone. I have tried the CF root or TWRP recovery of other A700 model but my phone stuck at samsung logo after reboot. Could anyone help me to root my A700YD? Many thanks.
dropbox.com/s/vfcms69qfn0vziq/BL_A700YDZSU1BOL4.tar.md5?dl=0
dropbox.com/s/phmabycaq9d5dm0/recovery.img?dl=0
Could anyone help? You can find the BL and recovery in the above links. New users cannot post link, sorry
Anyone can help?
Install twrp then use supersu v2.65
ashyx said:
Install twrp then use supersu v2.65
Click to expand...
Click to collapse
I have tried some twrp recovery. It can enter the recovery successfully but it cannot boot normally. It stuck at samsung logo.
ashyx said:
Install twrp then use supersu v2.65
Click to expand...
Click to collapse
I've tried to dig more in it, and what I get is
1. The only way I succeed is by using KingRoot, and the method it's using is by exploiting and keeping a daemon background and the su file for calling the daemon. So that means after reboot, root is lost.
3. Replacing KingRoot with SuperSU's su file will lead to a bootloop, same as goes to installing zip by twrp.
4. In the bootloop, logcat shows that it is repeating a particular normal boot process
5. In the bootloop, using adb shell and typing "su" will not get into root, despite su is located in xbin.
6. Busybox functions normally.
Any ideas?
ProtoAES256 said:
3. Replacing KingRoot with SuperSU's su file will lead to a bootloop, same as goes to installing zip by twrp.
Click to expand...
Click to collapse
Incorrect, installing supersu version 2.6x> with twrp will patch the boot image to prevent bootloop on samsung devices.
ashyx said:
Incorrect, installing supersu version 2.6x> with twrp will patch the boot image to prevent bootloop on samsung devices.
Click to expand...
Click to collapse
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
ProtoAES256 said:
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
Click to expand...
Click to collapse
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
pianman said:
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
Click to expand...
Click to collapse
From my current experience, no. The sad thing is I'm not skilled enough to do it myself, and seemly there is no reason that skilled devs are willing to have a head in to this not-quite-popular device.
Btw, you need to format /system partition before you flash the kitkat(well, maybe it works maybe it don't, it's just my experience.)
ProtoAES256 said:
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
Click to expand...
Click to collapse
Nope, it will only do that if you attempt to replace Kingroot with supersu.
If you apply supersu to a clean stock boot and system partition it shouldn't boot loop.
---------- Post added at 10:16 AM ---------- Previous post was at 10:11 AM ----------
pianman said:
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
Click to expand...
Click to collapse
If you have twrp installed I will upload a modified version of SuperSU which will allow systemless root on 5.0.2.
This will patch the boot image and should prevent a bootloop.
ashyx said:
Nope, it will only do that if you attempt to replace Kingroot with supersu.
If you apply supersu to a clean stock boot and system partition it shouldn't boot loop.
Click to expand...
Click to collapse
Weird, I did format my /system, /data and /cache before pushing in stock rom and supersu...
Isn't it sufficient to remove KingRoot?
Edit:
Or did I just messed up something?
ProtoAES256 said:
Weird, I did format my /system, /data and /cache before pushing in stock rom and supersu...
Isn't it sufficient to remove KingRoot?
Edit:
Or did I just messed up something?
Click to expand...
Click to collapse
If you flashed the stock rom that should remove the Kingroot and Super su binaries.
Are you using a stock kernel?
Usually only 5.1.1 and 6.0> need a patched boot.img as Samsung don't use root protection on 5.0.2 firmware.
However never say never and Samsung may may now be using root prevention in the later 5.0.2 kernels.
This means that a patched boot image is required to circumvent Samsung's root prevention.
If you have the boot.img I can patch it manually.
ashyx said:
If you flashed the stock rom that should remove the Kingroot and Super su binaries.
Are you using a stock kernel?
Usually only 5.1.1 and 6.0> need a patched boot.img as Samsung don't use root protection on 5.0.2 firmware.
However never say never and Samsung may may now be using root prevention in the later 5.0.2 kernels.
This means that a patched boot image is required to circumvent Samsung's root prevention.
If you have the boot.img I can patch it manually.
Click to expand...
Click to collapse
here you go, extracted from A700YDZSU1BOL4_A700YDZZT1BOL4_A700YDZSU1BOL4_HOME.tar
https://mega.nz/#!14IE3YoA!mRAhQSJCgZ53r5teACeJGWMwrftIY0g0GvZM0LMX9Kg
Hi everyone!
I found this two files, they are recovery.img and supersu 2.46. I still haven't tested them, because recovery is in img format and it has only the Chinese language. If anyone can help me translate the recovery and convert it in tar.md5 format. I found this 2 files on a700yd chinese forum. Thanks!
Same device platform. So should be compatible.
http://forum.xda-developers.com/samsung-a-series/general/recovery-twrp-galaxy-a7-t3153369
ashyx said:
Same device platform. So should be compatible.
http://forum.xda-developers.com/samsung-a-series/general/recovery-twrp-galaxy-a7-t3153369
Click to expand...
Click to collapse
I wiped my phone again and tried it
Here's my procedure
Wipe everything excluding external storage
reboot to bootloader and odin in stock rom
reboot to bootloader again and odin in twrp
reboot to recovery
twrp pops up patch notification(agrees and applied)
install SuperSU 2.65(stable) via sideload
reboot into system
Bootloop. ):
What does not cause bootloop
Stock ROM
TWRP installed only with stock ROM
What causes bootloop
installing SuperSU just after TWRP install (via zip or sideload)
Other problems
installing SuperSU from TWRP built-in will cause a recovery loop(unable to get past recovery screen)
=========
the recovery works good! (a good news at least)
ProtoAES256 said:
I wiped my phone again and tried it
Here's my procedure
Wipe everything excluding external storage
reboot to bootloader and odin in stock rom
reboot to bootloader again and odin in twrp
reboot to recovery
twrp pops up patch notification(agrees and applied)
install SuperSU 2.65(stable) via sideload
reboot into system
Bootloop. ):
What does not cause bootloop
Stock ROM
TWRP installed only with stock ROM
What causes bootloop
installing SuperSU just after TWRP install (via zip or sideload)
Other problems
installing SuperSU from TWRP built-in will cause a recovery loop(unable to get past recovery screen)
=========
the recovery works good! (a good news at least)
Click to expand...
Click to collapse
Try the supersu version above.
ashyx said:
Try the supersu version above.
Click to expand...
Click to collapse
i just update myphone to new firmware. i see something new eg : About device > "android security patch level"
i have same prolem (myphone boot stuck after flash superuser.zip v2.62-2.72 via twrp). And i try reflash one old boot.img via odin then myphone boot up normally with superuser.
i think the new boot.img make myphone stuck.
Can you please help me patch the new boot.img !?
ps: i'm so sorry for my bad english
https://drive.google.com/folderview?id=0B7uFmNBw-G1QalBCZERkeUpjd0U&usp=sharing
Hi Guys!
I ask you if someone used cf-auto root on this device and it was able to root the phone? Thanks.
hkopenh17071 said:
Hi everyone,
After my A700YD upgrade to android 5.0.2, I cannot find a feasible solution to root my phone. I have tried the CF root or TWRP recovery of other A700 model but my phone stuck at samsung logo after reboot. Could anyone help me to root my A700YD? Many thanks.
dropbox.com/s/vfcms69qfn0vziq/BL_A700YDZSU1BOL4.tar.md5?dl=0
dropbox.com/s/phmabycaq9d5dm0/recovery.img?dl=0
Could anyone help? You can find the BL and recovery in the above links. New users cannot post link, sorry
Click to expand...
Click to collapse
http://forum.xda-developers.com/samsung-a-series/development/galaxy-series-cf-auto-root-t3280406
I recently updated to marshmallow 6.0.1 on my galaxy s5 sm-g900s device. But i cant seem to get root working. Everytime I odin flash cf auto root, the red andriod logo would appear but the supersu app would not. After that, i flash cwm recovery and then flash supersu file through the recovery mode. I then atempt to reenable supersu through the settings but it would say that it cannot ennable/instal supersu and go restart the phone and try again. But this time is says something lile "cannot install or update binary."
I tried this 4 times alrdy and each time before flashing root, i would flash stock firmware to make sure my device is clean.
Usb debugging and allow download from unkown source is on.
I also tried sphinx root but it put my phone into a bootloop
Try this here
Thank me later...
demon434 said:
Try this here
Thank me later...
Click to expand...
Click to collapse
That will work for sm-g900s as well?
Can Anyone Tell me how to Root J500H 2015 3G 8GB latest Marshmellow 6.0.1 Installed Any Way to Root this Phone??
Humayun Butt said:
Can Anyone Tell me how to Root J500H 3G 8GB latest Marshmellow 6.0.1 Installed Any Way to Root this Phone??
Click to expand...
Click to collapse
Cf auto root perhaps
Not Working Any Method
SpamMachine said:
Cf auto root perhaps
Click to expand...
Click to collapse
Hi! One way is to use custom recovery to root your Galaxy J5. To root with custom recovery you will need a computer running Windows OS (didn't work with Linux distros using Wine) and download Odin from samsungodin.com. Then you will need a TWRP-recovery, the link is here:
https://eu.dl.twrp.me/j53gxx/twrp-3.1.1-1-j53gxx.img.tar.html
In Odin, click on the AP button and select your downloaded recovery file, boot your phone to download mode (Pwr+VolumeDown+Home), connect your phone with computer and start the installation process. It will usually take less than five seconds.
Once you installed the recovery, you will be able to easily root your phone. I recommend SuperSU as your SuperUser app. The link to official SuperSU is below:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Boot into recovery (Pwr+VolumeUp+Home) and install SuperSU and that's it, your phone should now be rooted. If you consider any problems, feel free to ask for more help!
Regards,
Patrik.
Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Cool:good:
Xposed isn't working with magisk? I was planning to install it
amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk
Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )
how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?
We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...
We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?
We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2