I know there are a lot of threads on the outdated SU binary problem, but none of them could help. I just updated my evo to 4.3 via ruu and so far I'm liking it. But I tryed installing SuperSu and it said the binary was outdated. I've had this happen lots of times before and flashing the SU update.zip always fixed it. This time I tried and it didn't work. I've been looking for other ways to fix the SU outdated binary problem but nothing has worked. I checked and I am still unlocked and s-off, it wiped recovery so flashed the latest twrp version. I would really like to try sense 5 out but I don't want to give up root.
Thanks in advance
Somebody had a similar issue getting the latest version of SuperSU to install. Go check out the SuperSU thread and try an older version and see if it works. That seems to have fixed the problem the other person had recently.
Sent from my HTC device
Thanks for replying, I just flashed 1.43 update instead of 1.93 and it did nothing. Also is it significant that in twrp when I reboot it tells me I'm not rooted and asks me if I want to install SuperSu, wether I have it installed or not (does nothing if I say yes or no)
Make sure you are using the correct twrp for the updated partitions
Sorry I'm kind of a noob, so what twrp should I be using and what is the updated partion
kagetheelephant said:
Sorry I'm kind of a noob, so what twrp should I be using and what is the updated partion
Click to expand...
Click to collapse
Post 3
http://forum.xda-developers.com/showthread.php?t=2639180
Thank you guys so much, I didn't know the update required a modded version of twrp. I just flash supersu 1.93 with the new twrp and its working fine :laugh:
kagetheelephant said:
Thank you guys so much, I didn't know the update required a modded version of twrp. I just flash supersu 1.93 with the new twrp and its working fine :laugh:
Click to expand...
Click to collapse
Very good enjoy
Related
I couldnt find a solid answer, so i was looking for help. I unlocked my phone and installed TWRP. I then flashed the SuperSU and BusyBox .zip file via recovery. But when i open the SU app i get prompted to update binaries and it will crash if i attempt to do so.
I have not flashed the insecure kernel, but I was almost certain that this was not need to gain root access.
Can i get confirmation? Maybe some help too :laugh:
Questions go in Q&A
Sent from my EVO using Tapatalk 2
Same issue
dekend said:
I couldnt find a solid answer, so i was looking for help. I unlocked my phone and installed TWRP. I then flashed the SuperSU and BusyBox .zip file via recovery. But when i open the SU app i get prompted to update binaries and it will crash if i attempt to do so.
I have not flashed the insecure kernel, but I was almost certain that this was not need to gain root access.
Can i get confirmation? Maybe some help too :laugh:
Click to expand...
Click to collapse
I have this exact same issue and I AM running the insecure kernel so I don't think it is an issue of the kernel. I found that using the SuperUser app rather than SuperSU works to alleviate this problem, but now I can't figure out how to uninstall the SuperSU app. If anybody can help me with this let me know
SuperSU wont work you have to use superuser for now..i had the same mistake but when i removed everything and redid it with superuser it been working fine since
Ok, well here's an update. I installed SuperUser via the Play Store, and updated the binaries. Afterwards I reboot and uninstalled the new SuperUser app and. tested SuperSU again. It prompted me to update Binaries again, but this time it worked, and now I am working just fine.
http://www.youtube.com/watch?v=vAwfgi0suJQ&feature=youtu.be
this worked for me on the super user gaining root
Hey guys.
Used the HTC All in one toolkit and rooted, installed TWRP, and a new rom on my device. I want to S-off but since my phone is brand new it doesnt seem to work. (This will never work on your phone stop trying - error with firewater) I used the Perm Root method on the All-in-one toolkit but everytime i reboot my device i lose root and need to wait for it to come back up (2-3 Min after bootup). This means its not permanent correct? Maybe this is why firewater is not working?
Another really weird thing, when i reboot with adb reboot, the phone takes literally like 10-15 minutes to power on. What is that about?
TWRP seems as it is permanent, and on the bootloader it says tampered and unlocked with s-on.
Im kinda confused here, I came from a nexus 4 so im not used to things not working.
SOOOOOOO..
(Q) Can someone give me an overview of what is going on so i can go in the right direction? should i unroot to stock and try again? Why would it give me a TEMP root if i used the permanent root method of flashing SuperSU in recovery? If i switch roms, is the perm root method removed?
Thanks in advance guys!
If you flashed a custom ROM, they are already rooted. So if you also flashed SuperSU in addition, you might have some conflict, such as a built-in SU conflicting with the SuperSU you flashed.
I would re-flash the ROM (you can probably "dirty" flash and keep user data, just wipe cache and Dalvik), don't flash any separate SuperSU or SU, and see if the problem persists.
The long boot problem is a known issue if you flashed a 2.xx based ROM (Android 4.4.3) but your phone is still on older firmware (hboot, radio, etc.). You might also experience some other significant bugs like broken WiFi or Bluetooth.
Firewater s-off has been patched for some time now, but Sunshine S-off should work (but costs $25).
You will need s-off to manually update firmware. But the alternative is to return to stock ROM and recovery, accept your latest OTA, which will install the new firmware.
redpoint73 said:
If you flashed a custom ROM, they are already rooted. So if you also flashed SuperSU in addition, you might have some conflict, such as a built-in SU conflicting with the SuperSU you flashed.
I would re-flash the ROM (you can probably "dirty" flash and keep user data, just wipe cache and Dalvik), don't flash any separate SuperSU or SU, and see if the problem persists.
The long boot problem is a known issue if you flashed a 2.xx based ROM (Android 4.4.3) but your phone is still on older firmware (hboot, radio, etc.). You might also experience some other significant bugs like broken WiFi or Bluetooth.
Firewater s-off has been patched for some time now, but Sunshine S-off should work (but costs $25).
You will need s-off to manually update firmware. But the alternative is to return to stock ROM and recovery, accept your latest OTA, which will install the new firmware.
Click to expand...
Click to collapse
Thanks for the speedy response.
I flashed the insertcoin rom. It was supposed to root with that (Chose SuperSU on aroma install) but no SuperSU was installed. It seemed like insert coin was a little buggy. So i installed the SuperSU with perm root option on all-in-one toolkit. And SuperSU was giving me errors of not being supported and need to update through recovery, it wasnt updating. Wiped, Reflashed insertcoin, this time SuperSU installed on the device, tried s-off with firewater and didnt work. Then i did a full wipe again.
This time I flashed M8Rx.v2 and seems like a solid running rom - Minus the fact that Wifi is broken. (It said use a specific kernel if on 1.58 firmware, but my phone came with 2.xx, maybe it went down to 1.58 with insertcoin) Came with SuperSU however now it doesn't have permanent root (I have not done perm root on all-in-one after wiping and flashing M8Rx.v2).
I have read that perm root may not work unless s-off. Is this true?
Also - Worth noting that when i was stock, there was no OTA available. i was on build 2.xx and now with M8rx.v2 im on build 1.58.502.1.
H0rn3t920 said:
I have read that perm root may not work unless s-off. Is this true?
Click to expand...
Click to collapse
No, that is completely false.
How are you determining root or no root?
For Insertcoin, you won't see SuperSU or SU in the app drawer. Its in the Settings>InsertCoin. If not having SuperSU in the app drawer is solely what led you to believe you weren't rooted, I think you may have just been confused about it and were rooted all along.
I don't know about M8Rx, as I've never used it.
redpoint73 said:
No, that is completely false.
How are you determining root or no root?
For Insertcoin, you won't see SuperSU or SU in the app drawer. Its in the Settings>InsertCoin. If not having SuperSU in the app drawer is solely what led you to believe you weren't rooted, I think you may have just been confused about it and were rooted all along.
I don't know about M8Rx, as I've never used it.
Click to expand...
Click to collapse
That was part of it, the other part was when using firewater, i would get no superuser prompts. That is a good piece of info though, thanks!
So how would i go about doing a permanent root and s-off? should i go back to stock and use the 25$ method or should i keep my rom and custom recovery and then do it? Mainly im curious about the permanent root as i have done what i should have for a permanent root and its not permanent. So I dont really understand what to do here.
H0rn3t920 said:
That was part of it, the other part was when using firewater, i would get no superuser prompts. That is a good piece of info though, thanks!
So how would i go about doing a permanent root and s-off? should i go back to stock and use the 25$ method or should i keep my rom and custom recovery and then do it?
Click to expand...
Click to collapse
I think you are perm rooted already. Not getting SU prompt in firewater is likely a different issue.
Make sure debugging is activated. Also, firewater doesn't work with some custom ROMs, not sure about InsertCoin. But you might try a different ROM.
Firewater was patched some time ago, and doesn't work for most M8's at this point. As your device was updated to the 2.xx software, firewater likely won't work. But you should at least get to the "whelp" error message from firewater before concluding that it won't work on your device.
redpoint73 said:
I think you are perm rooted already. Not getting SU prompt in firewater is likely a different issue.
Make sure debugging is activated. Also, firewater doesn't work with some custom ROMs, not sure about InsertCoin. But you might try a different ROM.
Firewater was patched some time ago, and doesn't work for most M8's at this point. As your device was updated to the 2.xx software, firewater likely won't work. But you should at least get to the "whelp" error message from firewater before concluding that it won't work on your device.
Click to expand...
Click to collapse
I did get the whelp message...
My confusion here is if i am perm rooted, why do i lose root on a reboot? All my xposed modules stop working, says version 58 has been installed but only found version 47. I hit install/update, superuser permissions granted and it immedietely says version 58 is found. I need to then soft reboot in order for all modules to activate.
Now its saying SuperSU is having issues updating the binaries. I flash the binaries in TWRP and then after the phone boots, it says the same thing again, to update binaries. I want to get into SuperSU to unroot and then flash SuperSU again in TWRP to see if that works, but i can not get around the update binaries screen. If i hit cancel, app closes.
EDIT: So i updated binaries, and i didnt get the update notification anymore. Got into the app, unrooted, then reinstalled supersu from TWRP, and then installed SuperSU from app store. Asked to update binaries, did it. Enabled SU at boot in SuperSU Settings. Still exactly the same. Even though xposed is granted superuser permissions, i need to go into the app and tinker with it before its auto granted and version 58 of xposed is seen.
I also tried in SuperSU Settings to write to system but it doesnt seem to work.
What am i missing here!?
Did you try to flash the ROM again, and this time not do anything additional to root (aside from the AROMA selection of SU/SuperSU), like I suggested back in Post #2?
I think something with the toolkit or flashing SU otherwise is messing with the built-in root.
I'm on InsertCoin, and have never had any issues with root.
redpoint73 said:
Did you try to flash the ROM again, and this time not do anything additional to root (aside from the AROMA selection of SU/SuperSU), like I suggested back in Post #2?
I think something with the toolkit or flashing SU otherwise is messing with the built-in root.
I'm on InsertCoin, and have never had any issues with root.
Click to expand...
Click to collapse
Thats how i did it to begin with on all my roms that i flashed. Only went and flashed the SuperSU after I realized that the rom itself didnt give a permanent root.
So I wiped the phone fully like 4-5 times before flashing M8Rx.v2 and everything is working super smooth and beautiful now. Thank you to redpoint73 and his help!
H0rn3t920 said:
Thats how i did it to begin with on all my roms that i flashed. Only went and flashed the SuperSU after I realized that the rom itself didnt give a permanent root.
Click to expand...
Click to collapse
Odd, all I can think is that the AROMA option to select SU/SuperSU is a little buggy.
Looks like persistence (or at least vigorous wiping) was the key!
All,
I was running a stock rooted LG G3. I decided I wanted to apply the OTA (I know, it was probably a terrible idea). Anyways I paid for the ChainFire SuperSU Pro hoping that I could apply the OTA keep root and carry on my way. After I applied the update it rebooted into TWRP and I couldn't get it to stop so I figured now was as good of time as any to wipe and install a custom ROM. I have tried both of the latest versions of unofficial CM12 and ParanoidAndroid and after I wipe and do the install then reboot it still goes back to the TWRP recovery. I am running version 2.8.3.0. Any help would be greatly appreciated!
V/r,
RH
RadiationHazard said:
All,
I was running a stock rooted LG G3. I decided I wanted to apply the OTA (I know, it was probably a terrible idea). Anyways I paid for the ChainFire SuperSU Pro hoping that I could apply the OTA keep root and carry on my way. After I applied the update it rebooted into TWRP and I couldn't get it to stop so I figured now was as good of time as any to wipe and install a custom ROM. I have tried both of the latest versions of unofficial CM12 and ParanoidAndroid and after I wipe and do the install then reboot it still goes back to the TWRP recovery. I am running version 2.8.3.0. Any help would be greatly appreciated!
V/r,
RH
.
Click to expand...
Click to collapse
Nevermind. I think I found the fix! :victory:
http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
RadiationHazard said:
Nevermind. I think I found the fix! :victory:
http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
Click to expand...
Click to collapse
LOL...Never take a OTA while rooted....lesson learned....always flash manually, everything you need to know is here if you havent found it already.... http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
Hello. I want to root my nexus 9 without installing any custom recovery. I want this because i want to receive google updates...
And sont suggest me about "install custom recovery and when you need flash the stock etc.)
Thanks in advance
Wrong forum. This is a dev forum, not Q&A. Rooting w/out custom recovery is possible with chainfire's autoroot flashable zips. But still you won't receive OTA updates b/c since Lollipop the validation process has changed and you need to be pure stock. This also includes the recovery iirc.
Moved to correct forum
Just root it. You don't need custom. Use the nexus tool kit
Sent from my Nexus 9 using XDA Free mobile app
giannisgt said:
Hello. I want to root my nexus 9 without installing any custom recovery. I want this because i want to receive google updates...
And sont suggest me about "install custom recovery and when you need flash the stock etc.)
Thanks in advance
Click to expand...
Click to collapse
brownog1 said:
Just root it. You don't need custom. Use the nexus tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
You will not receive OTA updates if you are rooted.
cam30era said:
You will not receive OTA updates if you are rooted.
Click to expand...
Click to collapse
Since when does rooting prevent OTA updates? Thats the first time I hear that.
On my N10 I always booted only into TWRP (fastboot boot twrp.img) and flashed from there the supersu.zip and still got OTAs without any issues.
I sold my N10 and my N9 is currently on the way to me so Im preparing everything to unlock and root it as soon as it arrives, thats why I am checking all those threads right now regarding root.
Well, I read only about this root injecting methode which doesnt sound very good to me and the nexus toolkit methode. Isnt it possible to boot into TWRP like I did before? Why shouldnt this work on the N9?
HansiHusten said:
Since when does rooting prevent OTA updates? Thats the first time I hear that.
On my N10 I always booted only into TWRP (fastboot boot twrp.img) and flashed from there the supersu.zip and still got OTAs without any issues.
I sold my N10 and my N9 is currently on the way to me so Im preparing everything to unlock and root it as soon as it arrives, thats why I am checking all those threads right now regarding root.
Well, I read only about this root injecting methode which doesnt sound very good to me and the nexus toolkit methode. Isnt it possible to boot into TWRP like I did before? Why shouldnt this work on the N9?
Click to expand...
Click to collapse
My bad. I should have said you will not be able to install OTA if you are rooted. The install script checks system files and if anything has been modified, it aborts installation. Your better option is to fastboot flash the Google factory image.
So what is the current working root methode for 5.1.1 without losing OTA or flashing any recovery?
This injecting thing, nexus toolkit or another way?
--edit--
seems like CF-Auto-Root (special version for the N9) works also? Im right now having 40 windows open in chrome, trying to find the best way...
Question is, does it still work for 5.1.1?
Again: Why should not boot into TWRP and then flash the supersu zip not work? Any issues with that?
Please share your experience. Thanks
HansiHusten said:
So what is the current working root methode for 5.1.1 without losing OTA or flashing any recovery?
This injecting thing, nexus toolkit or another way?
--edit--
seems like CF-Auto-Root (special version for the N9) works also? Im right now having 40 windows open in chrome, trying to find the best way...
Question is, does it still work for 5.1.1?
Again: Why should not boot into TWRP and then flash the supersu zip not work? Any issues with that?
Please share your experience. Thanks
Click to expand...
Click to collapse
It's a Nexus device. The easiest root method is to fastboot flash TWRP, the download SuperSU and flash it in recovery. Link here > http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
cam30era said:
It's a Nexus device. The easiest root method is to fastboot flash TWRP, the download SuperSU and flash it in recovery. Link here > http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
Click to expand...
Click to collapse
Alright, so the 'usual' way works as always, thanks for clearing this up. Was wondering if there were still some issues with rooting the N9.
So you suggest the beta version of supersu, will give a try first to the stable one, if this doesnt work ill try the beta.
Thanks m8
HansiHusten said:
Alright, so the 'usual' way works as always, thanks for clearing this up. Was wondering if there were still some issues with rooting the N9.
So you suggest the beta version of supersu, will give a try first to the stable one, if this doesnt work ill try the beta.
Thanks m8
Click to expand...
Click to collapse
Stable should work for Lollipop. Beta necessary for M. And beta works fine on Lollipop, too, FWIW.
DO NOT USE ON FOF6 FIRMWARE. WILL "BREAK" YOUR CAMERA. CHECK YOUR FIRMWARE VERSION.
Root method for FOG6 / 5.1.1 for the G900t THIS WILL TRIP KNOX. If you don't want to trip knox don't use this. If you do use it and whine you tripped knox because you didn't read ,we will all point and laugh at you.
Named it TrapKernel because well its not my normal HispAsian Kernel and I listened to a crap ton of Trap Music while doing it.
Thanks to @g.lewarne and his root method with his Unibase and Unikernel for the s6 , we finally have root after I ported it over to us. So be sure to thank him for his work.
What's included:
Auto installation of root and busy box
SuperSu.apk
A stock build prop with secure storage set to false so wifi passwords and etc aren't forgotten after reboots.
Kernel set to permissive
Otherwise stock
So here's the deal. Stupid simple.
1. Download the kernel
2. Flash in recovery (if twrp asks if you want to install su say NO)
3. Reboot and profit.
If you need more detailed help go HERE
Download
TrapKernel G6 [TWRP ZIP]
TrapKernel G6 [ODIN TAR]
Do NOT mirror this link. That means you "Android Geeks".
Special thanks to:
@g.lewarne for the obvious reason of being awesome and his root method for the s6. I suggest donating to him here [emoji14]
@ashraf sharif for testing
@Chainfire for SuperSU
also mine
This is wonderful. Thank you, sir.
EDIT: Works perfectly.
i just flashed it and somehow it broke the fingerprint scanner. nvm after a reboot, it is working now.
Awesome... thanks man!
Thanks! Working good. This. Is the 5.1.1 we should have gotten.
So when I come BAck I have everything.... is this new update faster the older one. was so buggy like 4-5 random restarts and freezes
I tripped Knox thanks bro ahaha!!!!
edited. My questions seemed too dumb
Great news about Trap Kernel root method for FOG6/5.1.1.
Background: I got a rooted TMobile GS5 4.4.2 last year and lately I had problems with storage from contact list file cache filling-up, over heating phone/cpu. Shortage of storage was fixed by clearing contacts app cache but still it prompted me to upgrade to 5.1.1 Lollipop, rooted earlier this week (see details below), but the camera app is broken. Glad that ShinySide was able to provide a Root method which won't break the camera app.
Just reviewed the detailed help links and took note about not letting TWRP install SU - note that I had let TWRP install SU with HispAsian kernel. I am using Android Unified toolkit PRO (with Odin3 v3.09), which was used to install TWRP 2.7.1.0 (latest available there). Before installing this new Trap Kernel when I get a chance:
Is it recommended to first update my current TWRP 2.7.1.0 to a newer version?
Is tripping Knox really an issue for phones if they are past 1 year since purchase (i.e. 1 yr manufacturer warranty expired)?
Thank you for clarifying,
Current system (rooted but broken camera app):
Baseboard: G900TUVU1FOG6
Kernel ver: 3.4.0_HispAsian_Kernel ShinySide #1 Thu Aug 6 23:52:39 2015
Build #: LMY47X.G900TUVU1FOG6
Recovery: TWRP 2.7.1.0
dpluigi said:
Great news about Trap Kernel root method for FOG6/5.1.1.
Background: I got a rooted TMobile GS5 4.4.2 last year and lately I had problems with storage from contact list file cache filling-up, over heating phone/cpu. Shortage of storage was fixed by clearing contacts app cache but still it prompted me to upgrade to 5.1.1 Lollipop, rooted earlier this week (see details below), but the camera app is broken. Glad that ShinySide was able to provide a Root method which won't break the camera app.
Just reviewed the detailed help links and took note about not letting TWRP install SU - note that I had let TWRP install SU with HispAsian kernel. I am using Android Unified toolkit PRO (with Odin3 v3.09), which was used to install TWRP 2.7.1.0 (latest available there). Before installing this new Trap Kernel when I get a chance:
Is it recommended to first update my current TWRP 2.7.1.0 to a newer version?
Is tripping Knox really an issue for phones if they are past 1 year since purchase (i.e. 1 yr manufacturer warranty expired)?
Thank you for clarifying,
Current system (rooted but broken camera app):
Baseboard: G900TUVU1FOG6
Kernel ver: 3.4.0_HispAsian_Kernel ShinySide #1 Thu Aug 6 23:52:39 2015
Build #: LMY47X.G900TUVU1FOG6
Recovery: TWRP 2.7.1.0
Click to expand...
Click to collapse
Flash which ever version. I always use the latest
You've already tripped Knox considering you have HispAsian kernel installed.
Install this kernel camera will work
An updated hispasian will be posted soon. It's already up to date plus some as the F6 version, I was just waiting for Kernel Auditor to accept a pull request so we're officially supported by its kernel download feature so I can push updates thru the app and can flash it via the app
ShinySide said:
Flash which ever version. I always use the latest
You've already tripped Knox considering you have HispAsian kernel installed.
Install this kernel camera will work
An updated hispasian will be posted soon. It's already up to date plus some as the F6 version, I was just waiting for Kernel Auditor to accept a pull request so we're officially supported by its kernel download feature so I can push updates thru the app and can flash it via the app
Click to expand...
Click to collapse
Just did mine. All seems good. Camera working.
Question. Lately, anytime I flash anything, when clicking on twrp reboot, it gets stuck on tmobile screen on reboot, and sometimes I long press power button and it's finishes boot and my homescreen loads. Other times, I gotta pull battery, and then boots fine and all further reboots are fine, no hang ups. What you think this is? Something in my twrp? I leave everything checkmarked in twrp restore, cache and everything. Wonder if that is causing it somehow. Should I wipe cache and dalvik in twrp reboot?
Thanks for the new trapkernel! I missed my root access those past two days and not having my adaway to block ads.
ShinySide said:
Flash which ever version. I always use the latest
You've already tripped Knox considering you have HispAsian kernel installed.
Install this kernel camera will work
An updated hispasian will be posted soon. It's already up to date plus some as the F6 version, I was just waiting for Kernel Auditor to accept a pull request so we're officially supported by its kernel download feature so I can push updates thru the app and can flash it via the app
Click to expand...
Click to collapse
Thanks, that was quick and easy. TWRP was updated to 2.8.7.0, and with TrapKernel both Camera and MHL connection work fine. Note though that I forgot to deselect Auto Reboot in Odin Option tab, so the phone did boot up fully after TWRP update and before flashing TrapKernel from Recovery Boot. It seems fine.
Regarding your note about not letting TWRP install SU, I already had SuperSU installed under my previous Kernel by TWRP. SU (already installed) seems to work fine but it is now prompting to update the SU binary. So under TrapKernel is it ok to proceed and update -or- should it be removed?
Thanks,
Donat
dpluigi said:
Thanks, that was quick and easy. Camera and MHL connection work fine. Note though that I forgot to deselect Auto Reboot in Odin Option tab, so the phone did boot up fully after TWRP update and before flashing TrapKernel from Recovery Boot. It seems fine.
Regarding your note about not let TWRP install SU, I already had SuperSU installed under my previous Kernel by TWRP. SU (already installed) seems to work fine but it is now prompting to update the SU binary. Under TrapKernel is it ok to proceed and update -or- should it be removed?
Thanks
Click to expand...
Click to collapse
Because hispasian kernel doesn't contain the auto root.
You should be able to update it. I've havent been prompted yet
Since the more details link seems to be dead or at least down, is there another way I can find out how to do this? It seems like you already have to know a number of things to follow the instructions in the first post.
Also, does this method reset your phone? OR are your settings, etc still intact after the root is complete?
Thanks.
CptCrackers said:
Since the more details link seems to be dead or at least down, is there another way I can find out how to do this? It seems like you already have to know a number of things to follow the instructions in the first post.
Also, does this method reset your phone? OR are your settings, etc still intact after the root is complete?
Thanks.
Click to expand...
Click to collapse
Their down for maintenance.
Put zip on SD card
Flash twrp with odin
Reboot directly to recovery
Flash kernel
Hit no if asks to install SU
Reboot.
No settings or data loss.
What dhould the wake and sleep be set at and what do they do ?
Thanks
Sent from my SM-G900T using XDA Free mobile app
ShinySide said:
Their down for maintenance.
Put zip on SD card
Flash twrp with odin
Reboot directly to recovery
Flash kernel
Hit no if asks to install SU
Reboot.
No settings or data loss.
Click to expand...
Click to collapse
Thanks.
As far as lost settings. So far, I've had to re-enter wifi keys.
Is it possible or even advisable to put the original recovery back in after it's rooted?
CptCrackers said:
Thanks.
As far as lost settings. So far, I've had to re-enter wifi keys.
Is it possible or even advisable to put the original recovery back in after it's rooted?
Click to expand...
Click to collapse
Yeah you can
what will happen if I try to do this with SM-G900V ?