Related
I have flashed twrp recovery over odin. I can only get into stock recovery though. Usual fix would be to remove battery b4 rebooting, but I can not make out the battery on this device - seems integrated / hidden.
I am running 4.4.2 KitKat. Trying to root it to debloat.
Any ideas? Maybe remove some startup scripts or Idk...
EDIT: I got word that it seems to be either some hash verification in the new android 4.4.x kernel or even a locked bootloader on top. Is that correct? And, if so, what would be a good course of action now?
More info can be found imo when googling for
Android 4.4 KitKat: Google Making Root Without Unlocked Bootloader Difficult?
Click to expand...
Click to collapse
(sry can't link)
JoeRifle said:
I have flashed twrp recovery over odin. I can only get into stock recovery though. Usual fix would be to remove battery b4 rebooting, but I can not make out the battery on this device - seems integrated / hidden.
I am running 4.4.2 KitKat. Trying to root it to debloat.
Any ideas? Maybe remove some startup scripts or Idk...
EDIT: I got word that it seems to be either some hash verification in the new android 4.4.x kernel or even a locked bootloader on top. Is that correct? And, if so, what would be a good course of action now?
More info can be found imo when googling for (sry can't link)
Click to expand...
Click to collapse
I don't know of any tablet that has user removable battery. I'm sure you have to be rooted before you can install a custom recovery. Are you using the rooting method in the development topic?
The question would be why you didn't use the recommended way of using Flashify to flash twrp?
Eddie Hicks said:
I don't know of any tablet that has user removable battery. I'm sure you have to be rooted before you can install a custom recovery. Are you using the rooting method in the development topic?
Click to expand...
Click to collapse
Yes. Would have posted there too had it been allowed. It is the method described in the t800 thread, where it says you should flash twrp via odin and then install SuperUser zip in TWRP.
kenkiller said:
The question would be why you didn't use the recommended way of using Flashify to flash twrp?
Click to expand...
Click to collapse
I thought that this was the way to do it. I have not read anything in that thread about flashify.
If flashify works with Android 4.4.2 I will dig into that. Does it?
JoeRifle said:
Yes. Would have posted there too had it been allowed. It is the method described in the t800 thread, where it says you should flash twrp via odin and then install SuperUser zip in TWRP.
I thought that this was the way to do it. I have not read anything in that thread about flashify.
If flashify works with Android 4.4.2 I will dig into that. Does it?
Click to expand...
Click to collapse
You did not follow the instructions in the first post, but the latter ones posted by bodivas? Then you should consider trying those in the first post - they work for T805 as well.
The ones in the first post work. Flashify I found it in the CF-Root for T700 thread, it works fine on T805 as well, as long as you get the correct img file from the TWRP site.
kenkiller said:
You did not follow the instructions in the first post, but the latter ones posted by bodivas? Then you should consider trying those in the first post - they work for T805 as well.
The ones in the first post work. Flashify I found it in the CF-Root for T700 thread, it works fine on T805 as well, as long as you get the correct img file from the TWRP site.
Click to expand...
Click to collapse
yes bodivas is his name. it seemed to be the better method. but since it did not "accept" the image, although odin said success, I dug deeper and found out that there is supposed to be a hash check in 4.4.2 which keeps me from keeping the flashed image
Will flashify solve that problem and make TWRP "resident"? I would rather not flash the CF Auto since it is for a t800 not t805, but maybe i am overcautious:angel:
JoeRifle said:
yes bodivas is his name. it seemed to be the better method. but since it did not "accept" the image, although odin said success, I dug deeper and found out that there is supposed to be a hash check in 4.4.2 which keeps me from keeping the flashed image
Will flashify solve that problem and make TWRP "resident"? I would rather not flash the CF Auto since it is for a t800 not t805, but maybe i am overcautious:angel:
Click to expand...
Click to collapse
You don't get by in XDA by being cautious in everything. There's enough reports to tell otherwise.
Yes, using Flashify to flash TWRP replaces stock recovery. TOTALLY.
Requires root though right? So is not possible for me I fear Only way would then be CF Auto for t800...as we found out. TU anyhow.
JoeRifle said:
Requires root though right? So is not possible for me I fear Only way would then be CF Auto for t800...as we found out. TU anyhow.
Click to expand...
Click to collapse
Of course it requires root. Not possible because you don't dare to flash the T800 files? Hehe.....you're gonna have a hard time here.
kenkiller said:
Of course it requires root. Not possible because you don't dare to flash the T800 files? Hehe.....you're gonna have a hard time here.
Click to expand...
Click to collapse
I just need to get the hang of these appy lil spy thingy thing things...god knows what g**gle has in store for you. out of curiosity, so you are saying there is no hash check in the bootloader keeping me/us from doing our evil deeds? how about the article up there I quoted, and what the heck happened when i odined TWRP?
just asking...will flash the CF. so lets cross thumbs and make tha knox trip count
Hi Guys. As following the instructions to flash openrecovery-twrp-2.8.0.1-chagallwifi.tar using Odin3 v3.09, my T805 reboots into recovery, the TWRP boot screen is blurred, and after the Menu appears, my device locks up and there is no way to reboot it. Force reboot by holding down the Power button doesn't work. I've been trying for nearly an hour and nothing works. The Task Menu and Return buttons are lit, but the screen is blank. Any suggestions on how to get my T805 to reboot normally?
Thanks.
UPDATE:
I found that 2.8.0.1 appears out of alignment on the screen, and I had to poke around until I found where the Reboot button was located. By chance I got it to go into Bootloader and the system rebooted. Once online I installed Flashify and installed TWRP 2.7.1.1 and SUCCESS!! Now my T805 is working normally. WHEW!!
Hi friendly xda android enthusiasts. I have, after many issues, finally rooted my gt-n5110 using odin and cf-auto. Workered without a hitch. Odin passed, tab rebooted, and BAM, "superSU has stopped working". I immediately navigated myself over to the playstore to reinstall SuperSU and for the first time i have ever seen it wouldnt allow me to. It only gave me a choice to open. No update no uninstall. Going into my apps list it was not present on downloads but was available on device list. Clucked it and no option to uninstall, only to force stop or turn off. So it is incorporated as a system with no access to it. This has me stumped. I have only seen old threads with answers to this and they are temp fixes. Need to know what i can do to fix this on a permanent basis and if someone could help me understand how and why this issue occured it would give me a better understanding and possibly prevent further issues. Thanks in advance guys.
Try the flashable version in this post after you install a custom recovery with odin.
ramjet73
ramjet73 said:
Try the flashable version in this post after you install a custom recovery with odin.
ramjet73
Click to expand...
Click to collapse
This may be a very stupid question but i have to be sure. As i stated the odin DID pass the auto root and tab rebooted. But along with the superSU error i ran root checker and was unable to obtain root. Im assuming its because supersu is not embedded. So with that said is it still ok to attempt to flash a recovery to the tab?
mattdiehl83 said:
This may be a very stupid question but i have to be sure. As i stated the odin DID pass the auto root and tab rebooted. But along with the superSU error i ran root checker and was unable to obtain root. Im assuming its because supersu is not embedded. So with that said is it still ok to attempt to flash a recovery to the tab?
Click to expand...
Click to collapse
Yes. Recovery is independent of whether or not you are rooted. You can install it from Android using tools like Flashify once you are properly rooted, but Odin works fine as long as you have a version of recovery in that format.
Flashing SuperSU from a custom recovery once it is installed should fix the superuser problems you are having.
ramjet73
ramjet73 said:
Yes. Recovery is independent of whether or not you are rooted. You can install it from Android using tools like Flashify once you are properly rooted, but Odin works fine as long as you have a version of recovery in that format.
Flashing SuperSU from a custom recovery once it is installed should fix the superuser problems you are having.
ramjet73
Click to expand...
Click to collapse
Doing now. Thankyou. Fingers crossed.
I had the same issue on my 5110. The flashable root only worked for me until I rebooted, then it would lose root. What ultimately worked for me was to unroot with Kingo. Then with USB debugging enabled, re-rooted with Kingo (which took around 10 min).
Sent from my AT&T Galaxy Note 3 using Tapatalk®
andygev35 said:
I had the same issue on my 5110. The flashable root only worked for me until I rebooted, then it would lose root. What ultimately worked for me was to unroot with Kingo. Then with USB debugging enabled, re-rooted with Kingo (which took around 10 min).
Click to expand...
Click to collapse
If flashing SuperSU from recovery doesn't result in a successful rooted system someone should let @Chainfire know. I've never had a problem rooting a stock ROM that way but let's see what @mattdiehl83 reports.
ramjet73
OS X
ramjet73 said:
If flashing SuperSU from recovery doesn't result in a successful rooted system someone should let @Chainfire know. I've never had a problem rooting a stock ROM that way but let's see what @mattdiehl83 reports.
ramjet73
Click to expand...
Click to collapse
Not near pc. Only have OS X available now. Can anybody walk me through using OS X to flash?
mattdiehl83 said:
Not near pc. Only have OS X available now. Can anybody walk me through using OS X to flash?
Click to expand...
Click to collapse
The recovery? I don't know if there is an OS X version of Odin.
ramjet73
ramjet73 said:
The recovery? I don't know if there is an OS X version of Odin.
ramjet73
Click to expand...
Click to collapse
I am wondering what flashing tool to use with OS X. Odin is for windows. I know of heimdall but that requires ALOT to flash anything. Wondering if there is another odin like tool for OS X
You could try this: http://forum.xda-developers.com/showthread.php?t=2598203
Sent from my AT&T Galaxy Note 3 using Tapatalk®
done.
Hi guys sorry for the delay in update. I ended up using VM ware and it allowed to operate as windows on OS X. I installed TWRP, went into the file manager in TWRP and removed the superSU, i then flashed superSU and rebooted. Once back to the tablet i went and restored services to superSU and went into the play store. And finally the playstore gave me the option the update the superSU. And then the rest was all normal installation of superSU. Hope this thread helps anybody dealing with these issues.
Glad you got it working. :good:
This post in the CF-Autoroot thread might be helpful as well.
ramjet73
there is a easy way to fix it!
download supersu 2.02 and install ta da and it works
2.01 does not work with n5110 well if you flash cf auto root
hmmmm.....
Bordo_Bereli51 said:
there is a easy way to fix it!
download supersu 2.02 and install ta da and it works
2.01 does not work with n5110 well if you flash cf auto root
Click to expand...
Click to collapse
Tada..your a genius. Oh wait i believe i stated it didnt have that option it was disabled. Yes i decided scarcasm would be fitting due to the fact it says ALL OVER xda to please read before you post.
mattdiehl83 said:
Tada..your a genius. Oh wait i believe i stated it didnt have that option it was disabled. Yes i decided scarcasm would be fitting due to the fact it says ALL OVER xda to please read before you post.
Click to expand...
Click to collapse
I read all the post and didnt found something
YOU DONT NEED TO DELETE SUPERSU 2.0.1
Install 2.02 apk and go to supersu, then to settings and push to /system
This is the easiest way. the one you found: go to recovery delete that and this. download supersu 2.0.2 apk and install it not the recovery zip i mean the APK! i didnt say the flashable supersu zip.
oh wait, yes you are a intelligent boy, you know everything.
mattdiehl83 said:
I am wondering what flashing tool to use with OS X. Odin is for windows. I know of heimdall but that requires ALOT to flash anything. Wondering if there is another odin like tool for OS X
Click to expand...
Click to collapse
That's a bit of a dilemma.
Unfortunately Samsung does not support using fastboot and bootloader mode (they call it download mode) so that standard SDK tool Google provides for Windows, Linux and MAC OS X isn't applicable. Your best bet would be to find a Windows PC that you can use to flash the recovery with Odin since that is the most common and best documented method.
Edit: NVM, somehow I responded to an old post of yours.
ramjet73
I tried a few ways to install CM11 on Galaxy TabPro 10.1 (picassowifi) and it doesn't work.
I can't even install a custom recovery, either CMR or TWRP. I think my Samsung bootloader maybe locked. Yes, I have rooted it OK and Root Checker tells me its rooted and SuperSU has been update and works fine. Titanium Backup works fine also, so I know its rooted OK.
Still running stock rom 4.4.2. Trying with Odin to load Recovery image and also Flashyfy but neither can install CMR or TWRP on my device. They just leave the stock bootloader in place. So I am thinking maybe the bootloader is locked?
Any advice, and if you have managed to install CM11 on this device, is there a step-by-step guide with file links somewhere?
Thanks
dave457 said:
I tried a few ways to install CM11 on Galaxy TabPro 10.1 (picassowifi) and it doesn't work.
I can't even install a custom recovery, either CMR or TWRP. I think my Samsung bootloader maybe locked. Yes, I have rooted it OK and Root Checker tells me its rooted and SuperSU has been update and works fine. Titanium Backup works fine also, so I know its rooted OK.
Still running stock rom 4.4.2. Trying with Odin to load Recovery image and also Flashyfy but neither can install CMR or TWRP on my device. They just leave the stock bootloader in place. So I am thinking maybe the bootloader is locked?
Any advice, and if you have managed to install CM11 on this device, is there a step-by-step guide with file links somewhere?
Thanks
Click to expand...
Click to collapse
You entered on donwload mode for install the recovery?
MastherAndroid said:
You entered on donwload mode for install the recovery?
Click to expand...
Click to collapse
Yes I got into download mode OK. Power and volume up etc. In fact, that was the way I rooted it originally. Download mode on tablet and Odin on PC
dave457 said:
Yes I got into download mode OK. Power and volume up etc. In fact, that was the way I rooted it originally. Download mode on tablet and Odin on PC
Click to expand...
Click to collapse
Did you followed the instructions below?
http://wiki.cyanogenmod.org/w/Install_CM_for_picassowifi
If it not helped then I think you have a locked bootloader.
cviniciusm said:
Did you followed the instructions below?
If it not helped then I think you have a locked bootloader.
Click to expand...
Click to collapse
Yeah I tried those instructions, Heimdall Suite. That just gave an error and messed up stock recovery. It then just got stuck on Samsung screen possibly trying to get into recovery mode. . I used my trusted root method again (via download mode) and it re-routed and put back stock recovery. So that fixed that but still no Custom Recovery and no CM11
Is there any way to check if the bootloader is locked or not?
If the bootloader is locked, any ideas how to unlock on this tablet?
Thanks
dave457 said:
Yeah I tried those instructions, Heimdall Suite. That just gave an error and messed up stock recovery. It then just got stuck on Samsung screen possibly trying to get into recovery mode. . I used my trusted root method again (via download mode) and it re-routed and put back stock recovery. So that fixed that but still no Custom Recovery and no CM11
Is there any way to check if the bootloader is locked or not?
If the bootloader is locked, any ideas how to unlock on this tablet?
Thanks
Click to expand...
Click to collapse
Bootloader is not locked.
Try using flashify to install twrp if you are having problems with Odin/heimdall.
crpalmer said:
Bootloader is not locked.
Try using flashify to install twrp if you are having problems with Odin/heimdall.
Click to expand...
Click to collapse
Thanks
I tried Flashyfy. It goes through the process and says "imaged flashed" etc but then it just reboots the tablet back into stock recovery.
dave457 said:
Thanks
I tried Flashyfy. It goes through the process and says "imaged flashed" etc but then it just reboots the tablet back into stock recovery.
Click to expand...
Click to collapse
Are you sure that you are rooted?
crpalmer said:
Are you sure that you are rooted?
Click to expand...
Click to collapse
Yes its rooted. Flashify also confirms root.
Anyway, I got it sorted now. The problem was version 2.8 of TWRP did not work with this tablet and Flashify. It just booted back into stock recovery. But version 2.7 of TWRP worked fine and that's fine for me.
Thanks everyone
same problem here
Hi, I'm having the same problem with my rooted Tab Pro 10.1. Unfortunately, v2.7 with Flashify still results in booting to the same stock recovery. Did you follow any additional steps to get yours working? Any other suggestions? (I tried the other methods you tried also)
m33syj said:
Hi, I'm having the same problem with my rooted Tab Pro 10.1. Unfortunately, v2.7 with Flashify still results in booting to the same stock recovery. Did you follow any additional steps to get yours working? Any other suggestions? (I tried the other methods you tried also)
Click to expand...
Click to collapse
No, v2.7 worked for me but maybe it was nothing to do with that. I may have just got lucky.
Try Rashr (from Google Play). I had success on other devices with this just to get TWRP on
dave457 said:
No, v2.7 worked for me but maybe it was nothing to do with that. I may have just got lucky.
Try Rashr (from Google Play). I had success on other devices with this just to get TWRP on
Click to expand...
Click to collapse
Using one of the root checker apps, it reported my device as having clockworkmod recovery even though it didn't boot into that. Must have only half worked or something, who knows. I just tried Rashr and that has just sucessfully installed TWRP so I think for here on I'm golden. Thanks so much for recommending me that!
Hi, I was fed up with my stock, slow, German 855 and wanted to root and flash CloudyG3 2.3.
First I tried Purple Drake lite but it aborted after the phone rebooted. Then I tried LG One Click Root 1.3 and this seemed to work.
Next on my list was flashing a recovery. I followed this: [RECOVERY][TWRP][D855] TeamWin Recovery with modem support and flashed the .img via flashify.
Now the phone does not boot. It says "Secure bootig error. Cause: Boot certification verify." after that the screen turns off and the notification LED flashes red and blue. I tried factory reset but I end up at the same error message.
I started panic googling and was about to try this: http://forum.xda-developers.com/showpost.php?p=59970974&postcount=6 but because OP had a slightly different problem and I don't want to make it any worst, I thought I ask for verification first.
What did I do wrong? I stuck to tutorials from the FAQ (apart from one click root which seemed to work). Am I supposed to flash stock firmware via ADP download mode now?
Thanks!
CutterSlade001 said:
Hi, I was fed up with my stock, slow, German 855 and wanted to root and flash CloudyG3 2.3.
First I tried Purple Drake lite but it aborted after the phone rebooted. Then I tried LG One Click Root 1.3 and this seemed to work.
Next on my list was flashing a recovery. I followed this: [RECOVERY][TWRP][D855] TeamWin Recovery with modem support and flashed the .img via flashify.
Now the phone does not boot. It says "Secure bootig error. Cause: Boot certification verify." after that the screen turns off and the notification LED flashes red and blue. I tried factory reset but I end up at the same error message.
I started panic googling and was about to try this: http://forum.xda-developers.com/showpost.php?p=59970974&postcount=6 but because OP had a slightly different problem and I don't want to make it any worst, I thought I ask for verification first.
What did I do wrong? I stuck to tutorials from the FAQ (apart from one click root which seemed to work). Am I supposed to flash stock firmware via ADP download mode now?
Thanks!
Click to expand...
Click to collapse
@CutterSlade001, seems like you are already rooted. Did you try pulling out the battery and then powering on again? Once you are sure you are rooted, you can try using various methods available on XDA or try searching AutoRec on the play store for installing twrp. It's meant for rooted lollipop devices. Hope this helps.
Sent from my LG-D855 using Tapatalk
ravi.vydianathan said:
@CutterSlade001, seems like you are already rooted. Did you try pulling out the battery and then powering on again? Once you are sure you are rooted, you can try using various methods available on XDA or try searching AutoRec on the play store for installing twrp. It's meant for rooted lollipop devices. Hope this helps.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Yes pulling the battery does nothing but to give me the ability to look at the error again.
I get that i am supposed to install twrp. But how to safely make the phone operational again?
Or can I only use ADB at hte moment? Yes rooting worked.
Thanks for your hint at AutoRec I will try that once the phone works again.
CutterSlade001 said:
Yes pulling the battery does nothing but to give me the ability to look at the error again.
I get that i am supposed to install twrp. But how to safely make the phone operational again?
Or can I only use ADB at hte moment? Yes rooting worked.
Thanks for your hint at AutoRec I will try that once the phone works again.
Click to expand...
Click to collapse
I presume you can get into download mode? If you can use flashtool to go back to stock then root your device then use Autorec.
Download mode seems to work. Slowly downloading factory image now...
So rooting via one click was not the problem? Not using Autorec was?
I will follow this then after factory flash and reset and root via oneclick?
Thanks a lot for your help! I got it working again.
But now I am back to KitKat and Autorec requires Lollipop. OTA says there is no update and I got all sorts of junk on the phone from other carriers.
Is there a factory Lollipop image I missed?
CutterSlade001 said:
Thanks a lot for your help! I got it working again.
But now I am back to KitKat and Autorec requires Lollipop. OTA says there is no update and I got all sorts of junk on the phone from other carriers.
Is there a factory Lollipop image I missed?
Click to expand...
Click to collapse
@CutterSlade001 seems like you got hold of a kk firmware file instead of lp. You should be able to the appropriate lollipop version for your phone model. After that, just flash once again and then use one click root plus recovery options available in XDA.
Sent from my LG-D855 using Tapatalk
ravi.vydianathan said:
@CutterSlade001 seems like you got hold of a kk firmware file instead of lp. You should be able to the appropriate lollipop version for your phone model. After that, just flash once again and then use one click root plus recovery options available in XDA.
Click to expand...
Click to collapse
Thanks for all your Help! I did that and it worked! I only found Lollipop .kdz files so I used the 2014 flash tool. After that, everything worked as expected. I am now running CloudyG3 2.3 and am Happy so far. But I did a clean install with only the bare minimum of apps for now and the stock firmware ran smooth for a few weeks also. Always buy the version with 3 GB RAM instead of the one with 2 GB RAM and a "free" LG G Watch.
CutterSlade001 said:
Thanks for all your Help! I did that and it worked! I only found Lollipop .kdz files so I used the 2014 flash tool. After that, everything worked as expected. I am now running CloudyG3 2.3 and am Happy so far. But I did a clean install with only the bare minimum of apps for now and the stock firmware ran smooth for a few weeks also. Always buy the version with 3 GB RAM instead of the one with 2 GB RAM and a "free" LG G Watch.
Click to expand...
Click to collapse
@CutterSlade001 glad that it worked for you ?
Sent from my LG-D855 using Tapatalk
cutterslader ..... please tell me how could u solve the problem. I have the same problem and i couldnt get to download mod because the screen is black and not functional. please help me, I am losing my phone. it is lg g3 d858hk
khalfan1984 said:
cutterslader ..... please tell me how could u solve the problem. I have the same problem and i couldnt get to download mod because the screen is black and not functional. please help me, I am losing my phone. it is lg g3 d858hk
Click to expand...
Click to collapse
Please let me know if you could fix this, I have the same problem
I keep having this problem. I just tried both KINGROOT and CF-AUTO ROOT.
After doing this whole process through ODIN. I then try to flash the latest TWRP from their website : dl.twrp.me/jfltetmo/twrp-3.2.0-0-jfltetmo.img.tar.html
Then after that finishes, I try to boot into recovery and it gives me the message: recovery is not seandroid enforcing and just sits there.
I have a tmobile s4.
and I also checked if I am indeed rooted by using an app from the play store to check root and it shows Im rooted.
Any help would be great.
Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?
audit13 said:
Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?
Click to expand...
Click to collapse
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.
Krappa420 said:
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.
Click to expand...
Click to collapse
I have the exact problem, can you kindly explain in details how you went about it? I already downloaded SkipSoft.
Same issues here, buddy.
I tried to work on solving it out for approximately 8 hours and still no sign of success. Tried to reflash stock OS back on the phone via ODIN and it went successful. Tried CF-Auto-root file and it went through successful. But when it only came to the TWRP file, it went successful onto flashing on ODIN's side, but now something is interfering with the boot up process onto TWRP now. Hopefully there's a alternative towards this issue, since i've been wanting to reflash a Nougat OS onto the device.
Edit: I give credit to @Krappa420 for the mention of "SkipSoft Unified Android Toolkit" because i just installed the program on my laptop now and it went successful. But since i already had other materials pre-installed, some others with ODIN and ADB installed can just download this TWRP version here: https://dl.twrp.me/jfltexx/twrp-2.7.0.0-jfltexx.img.html
Edit #2: Seems that the TWRP version is too old to flash some of the newer OS's, such as nougat itself. Will find a way to update TWRP without breaking the boot up process, like the past attempts
Edit #3: After fiddling with TWRP versions 2.7.0.0 and up, i managed to get it capped up to 3.1.1 any future versions will most likely not work, so you're capped at 3.1.1 Here's the link for flashing it with ODIN: https://dl.twrp.me/jfltexx/twrp-3.1.1-0-jfltexx.img.tar.html
So you twrp 3.1.1 and it will work right
I having the same issue
Thank you
so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran
timj3371 said:
so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran
Click to expand...
Click to collapse
It wouldn't really matter what order you're using.
You can use CF-Auto-Root to root it for you while you have stock recovery still, and after you can flash to TWRP and use a custom recovery afterwards
Or you can flash TWRP first and flash a SuperSU zip file afterwards and it'll give you root while maintaining to have TWRP installed.
But to sum it up, it wouldn't matter what order you choose. Help yourself
Trwp
What version of twrp I need to use
Thank you
timj3371 said:
What version of twrp I need to use
Thank you
Click to expand...
Click to collapse
TWRP version 3.1.1
Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran
timj3371 said:
Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran
Click to expand...
Click to collapse
Before anything, try to install the SuperSU app over on the play store, if it says you're not rooted, you may have to restart the whole process within TWRP and reflash the SuperSU Zip file.
Thank you
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks
timj3371 said:
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks
Click to expand...
Click to collapse
Try this one: https://download.chainfire.eu/696/supersu/
If it keeps on persisting, I'll have to find another way
I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you
timj3371 said:
I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you
Click to expand...
Click to collapse
Yeah try to re-flash the ROM again but this time flash magisk through TWRP since SuperSU is being trippy on your S4
Thank you for the help
Dummy me I found out from reading other forums you have to go in to tools and enable root after going in to recovery and flash the root file in the extra section.
Every thing works
Thank you so much
Disabled veteran