Related
I flashed this rom and it says I dont have root access. I used both a older CWM, and the 5504 beta 10 from team drh. I couldn't even update Superuser, any help would be greatly welcomed. Thanks
thew-tab said:
I flashed this rom and it says I dont have root access. I used both a older CWM, and the 5504 beta 10 from team drh. I couldn't even update Superuser, any help would be greatly welcomed. Thanks
Click to expand...
Click to collapse
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
Try this it worked for me on a AOSP build on my phone. You can download it on the tablet or computer and side load the zip file. Do not unzip the file boot up into CWM and clear Cache and Dalvic then install the zip file and reboot. Wait for android to finish updating apps and should be able to regain su user.
Scratch that CWM wouldn't load the zip trying another way.
thew-tab said:
I flashed this rom and it says I dont have root access. I used both a older CWM, and the 5504 beta 10 from team drh. I couldn't even update Superuser, any help would be greatly welcomed. Thanks
Click to expand...
Click to collapse
at this time it is something with the ROM so there is nothing we can do
edit: it is also going to be a while before any root fix...so i would say to try another ROM like team DRH's ROM....also i recommend not trying to fix the problem yourself because you can end up in a SOD(like i did) or even possibly hard brick
---------- Post added at 03:08 AM ---------- Previous post was at 02:28 AM ----------
the method used to root the ROM was really bad and i cant seem to crack the ROM... i've been able to unroot it but when i try to reroot; the closest i come is to being able to open the superuser app( most methods dont get that far)
I am rooted only and on version 11c. I can download JB fine and the install starts. When it gets to 2% I get a message saying I have a 0X13E error. The phone reboots into ICS and works fine.
There are several comments in other threads about this error but I don't see if anyone has found what causes it or how to fix it. One thread has someone deciding the phone is defective and getting a refurb from AT&T. They mention doing a factory reset and still having the update fail. I don't want to got that route (having dealt with refurbs before) and I haven't tried the factory reset yet.
Any information would be appreciated.
Thanks,
I got the 0x13E error as well.
I'm rooted an unlocked, and I tried to do the update by rolling back to an ICS nandroid. I downloaded the update several times, same thing each time.
At some point in my attempts, SnowLeapord posted his flashable 20j .ZIP, so I quit trying to figure out why I got the error.
If you want to get the update OTA, I think you'll have to LGNPST back to stock 11c.
I'd recommend just using the flashable zip personally.
Same issue here, and factory reset does nothing. I've tried three different backups, both rooted and unrooted, and I've tried flashing 11c and 10o. Oddly enough, even my fully stock backup on 10o has no available updates(ie, the update to 11c isn't there anymore, and you can't update direct to 20j).
I got the same issue when I was rooted and unlocked. I used the Freegee app to re lock and then did the update. That seemed to do the trick
Sent from my LG-E970 using xda premium
I'm pretty sure that the only reason this error crops up is the use of an unofficial bootloader on the phone; In other words: It's been unlocked. It's the reason I got this error.
Most of the time, if you've unlocked with FreeGee, you relock and go on your merry way.
As for the OP getting the error on rooted only (and not unlocked) - never heard of this error for someone who hadn't unlocked their phone int he past. Since you're rooted, you could do a data backup, factory reset and try the update again.
Basically, the phone must have a locked bootloader (but can be rooted, I believe) for the OTA update to work.
miller150 said:
Same issue here, and factory reset does nothing. I've tried three different backups, both rooted and unrooted, and I've tried flashing 11c and 10o. Oddly enough, even my fully stock backup on 10o has no available updates(ie, the update to 11c isn't there anymore, and you can't update direct to 20j).
Click to expand...
Click to collapse
Mine also did this. Speculation is because it's comparing between what you *should* be on (11c) and what's available (20j). When your phone shows up with 10o comparing to 20j, it's not an exact match, therefore no update found (hence the "up to date" message). I like to think of it as either poor coding on the update engine or (more likely) poor wording in the "up to date" message box.
Thanks, I was able to update after I restored through freegee.
I'm having the same issue on my E970. Rooted on the stock ROM.
Please Help!!!
Hello I tried wiping the phone to factory reset and still go the 0x136 error whenever i tried to update so no realizing what i was doing i accidentally wiped the whole Android and now my phone wont even turn on :'( its a brand new phone and i don't want to go to ATT and buy another please help!
Also i wiped everything i could form the bootloader except the bootlaoder itself...
polarzombies said:
Thanks, I was able to update after I restored through freegee.
Click to expand...
Click to collapse
I have the same issue. I just downloaded and installed FreeGee. Do I have to unlock it first and then lock it? I do not currently have any backups to a locked state.
Thanks.
BobbyF said:
I have the same issue. I just downloaded and installed FreeGee. Do I have to unlock it first and then lock it? I do not currently have any backups to a locked state.
Thanks.
Click to expand...
Click to collapse
If you could post the instructions, that would be great. I had rooted my LGOG but seems like there is no easy way of going back and I would like to get the JB OTA. Appreciate your help.
BobbyF said:
I have the same issue. I just downloaded and installed FreeGee. Do I have to unlock it first and then lock it? I do not currently have any backups to a locked state.
Thanks.
Click to expand...
Click to collapse
You have to restore in freegee which doesn't wipe your om it just removes the recovery menu. After you restore with the freegee app the phone's bootloader is locked but it doesn't wipe the rom. Then you just update and then use the freegee app again to unlock your bootloader and then it installs TWRP instead of CWM. So far I've had no md5 mismatches with TWRP so my backups seem to be more reliable then with CWM.
polarzombies said:
You have to restore in freegee which doesn't wipe your om it just removes the recovery menu. After you restore with the freegee app the phone's bootloader is locked but it doesn't wipe the rom. Then you just update and then use the freegee app again to unlock your bootloader and then it installs TWRP instead of CWM. So far I've had no md5 mismatches with TWRP so my backups seem to be more reliable then with CWM.
Click to expand...
Click to collapse
I am not into flashing ROMs, recovery menus etc. So, let me repeat the steps I need to do get OTA.
1. I am now rooted and at 4.0.4.
2. Installed FreeGee app
So, these are my next steps? Could you confirm?
1. Unlock bootloader using FreeGee
2. Get the OTA update of JB
Now, at this point I understand my bootloader is locked again. Here is the question. After the update is done, will my recovery menu be still CWM (am I right) or the recovery menu whatever LG provides (I am not sure of the name)? If not, is there any way of going back to LG's version of recovery menu? Is there any chance of bricking my device?
Sincerely appreciate all your help.
I'm a bit confused... I installed FreeGee from Google Play, and I have options to restore with backups and unlock my Optimus G. I'm rooted on AT&T 4.0.4 still. Do I need to use the Unlock my Optimus G option, let it do its thing, and then have it relock it to get the OTA update to work? My only worry is that the phone will eventually get to a point where it can't boot anymore.
---------- Post added at 02:54 PM ---------- Previous post was at 02:49 PM ----------
Obviously, that was a stupid idea. Black screen right after the LG logo came up.
---------- Post added at 03:04 PM ---------- Previous post was at 02:54 PM ----------
Managed to go into fastboot mode (volume up + power) and I eventually got it to boot back up. Was worried for a while.
---------- Post added at 03:09 PM ---------- Previous post was at 03:04 PM ----------
Restored the backup that FreeGee made. Trying an OTA update again, as per polarzombies instructions.
---------- Post added at 03:12 PM ---------- Previous post was at 03:09 PM ----------
As expected, 0x13E again.
http://webchat.freenode.net/?channels=lg-optimus-g
besweeet said:
I'm a bit confused... I installed FreeGee from Google Play, and I have options to restore with backups and unlock my Optimus G. I'm rooted on AT&T 4.0.4 still. Do I need to use the Unlock my Optimus G option, let it do its thing, and then have it relock it to get the OTA update to work? My only worry is that the phone will eventually get to a point where it can't boot anymore.
---------- Post added at 02:54 PM ---------- Previous post was at 02:49 PM ----------
Obviously, that was a stupid idea. Black screen right after the LG logo came up.
---------- Post added at 03:04 PM ---------- Previous post was at 02:54 PM ----------
Managed to go into fastboot mode (volume up + power) and I eventually got it to boot back up. Was worried for a while.
---------- Post added at 03:09 PM ---------- Previous post was at 03:04 PM ----------
Restored the backup that FreeGee made. Trying an OTA update again, as per polarzombies instructions.
---------- Post added at 03:12 PM ---------- Previous post was at 03:09 PM ----------
As expected, 0x13E again.
Click to expand...
Click to collapse
I would recommend using lgnpst to install the 20 j update.
Everything you need is in header of this Irc channel
adfurgerson said:
http://webchat.freenode.net/?channels=lg-optimus-g
I would recommend using lgnpst to install the 20 j update.
Everything you need is in header of this Irc channel
Click to expand...
Click to collapse
Thanks, that finally got me onto 4.1.2 without losing anything at all. Process worked perfectly.
Do you still use LG Optimus G? I'm experiencing the same error I tried freegee to re lock but just error 1 showed I got Android 4.4.2
I just rooted my Note 3 using Towelroot method and it didn't trip the Knox counter
1. Just install Towelroot.apk from http://towelroot.com/
2. Open Towerroot to root than reboot
3. install Root checker from the Play store to check root
4. install Supersu from http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip - Unzip and install APK, open and let it uninstall Knox and Reboot.
For more details refer to - http://forum.xda-developers.com/showthread.php?t=2783157
Installing Safestrap:
After Rooting and Supersu is installed follow below steps to install safestrap:
1. Install Busybox app from Play store https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
2. Install Safestrap from herehttp://forum.xda-developers.com/showthread.php?t=2517610 and follow instructions in the thread
Yahoo! Happy father's day!
Sent from my HTC6525LVW using Tapatalk
Good find thanks for sharing!! Yeeeesss
Sent from my SM-N900V using Tapatalk
everytime i update supersu it says failed any thoughts?
breakyosef said:
everytime i update supersu it says failed any thoughts?
Click to expand...
Click to collapse
Did you install the Supersu from Chainfire website? the website one is the most current and it should work, though the unistall of knox took long time, i waited for 5 minutes and while it's still running the unistall I rebooted and everything is fine now.
droidguy22 said:
Did you install the Supersu from Chainfire website? the website one is the most current and it should work, though the unistall of knox took long time, i waited for 5 minutes and while it's still running the unistall I rebooted and everything is fine now.
Click to expand...
Click to collapse
yeah i installed towelroot again.. and it finally updated.
What do we do now wait tell there's a recovery out??
Safe strap v3.72 works for this too.
Nevermind...figured it out!
What roms can we flash once rooted an safestrap installed
oner14 said:
Okay thanks man I'm going to try that see what happens thanks
---------- Post added at 11:32 PM ---------- Previous post was at 11:25 PM ----------
Can u possibly put the link here to make sure I use the same one
Click to expand...
Click to collapse
check Updated OP with safestrap instructions
SuperSU
How to enable wifi tethering now?
BEST POST EVER.
One of my kids pushed the OTA through when I had rebooted into stock and let her use my phone for a day. Two weeks of Hell, but I knew someone would find the way through this darkness!!
GREAT job! Thank you!!!
This works perfectly, just follow the instructions to the letter!
Too much following of directions
I towelrooted this morning, installed SU (chainfire's) - got the same error "cannot parse package" - however it worked even though when I went in SU it said the binary was wrong and updating it would fail (play store version). Tried to do the CWM method since i got frustrated at the SU error - and the CWM soft bricked the phone. Now im going to odin it back to stock - when the download is done in 2 hours... Oh well all is fair in device freedom and rooting : )
Proud Note 3 owner of ~96 hours so far : )
P.S. Geohot is amazing.
---------- Post added at 08:00 PM ---------- Previous post was at 07:55 PM ----------
Also, of note - titanium backed up the phone prior to the soft bricking - titanium on NC4 still suffers the cannot write to external SD issue.. FYI - if you think your schedules will run - might want to double check.
droidguy22 said:
I just rooted my Note 3 using Towelroot method and it didn't trip the Knox counter
1. Just install Towelroot.apk from http://towelroot.com/
2. Open Towerroot to root than reboot
3. install Root checker from the Play store to check root
4. install Supersu from http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip - Unzip and install APK, open and let it uninstall Knox and Reboot.
For more details refer to - http://forum.xda-developers.com/showthread.php?t=2783157
Installing Safestrap:
After Rooting and Supersu is installed follow below steps to install safestrap:
1. Install Busybox app from Play store https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
2. Install Safestrap from herehttp://forum.xda-developers.com/showthread.php?t=2517610 and follow instructions in the thread
Click to expand...
Click to collapse
Thank you kinldy, I'm sure alot of users have been waiting for this
NC4 Stock Rooted!
Just found the Towelroot information off the internet and decided to apply on my stock NC4 rom.
It worked fine without any issues!
Installed the APK file and ran it. After the reboot, I installed SuperSu too. Now I'm able to install and invoke all APKs requiring root access!
It seems like there's none yet mentioned about the Knox void count. I checked the Knox void count and it's still 0!
Thanks to Geohot for this great rooting apk!
Still no "perfect" love on SU
It did the busybox and twrp just fine - but still get the binary update message / close on SuperSU
After the data wipe / redownload of UPDATE-SuperSU-v1.99r4.zip .. same result.
it works, and prompts - just cannot enter the application. Guess its just wait until further version.
Thanks for the guide - worked perfectly (steps wise) - now to tip Geohot and go to bed.
I have successfully rooted and installed safestrap on my stock nc4 note 3 however when I try to install jellybeans build 6 into romslot 1 and boot to it, the phone never shows a boot screen after the safestrap screen. I get a blue led and nothing else.
Any ideas? Maybe 4.3 isn't compatible with the new modem?
New safe strap didn't let you use anything but the stock slot. So you can only use that for now. Can't flash roms into slots 1-4
Sent from my GlaDos Baked Potato
Legato Bluesummers said:
New safe strap didn't let you use anything but the stock slot. So you can only use that for now. Can't flash roms into slots 1-4
Sent from my GlaDos Baked Potato
Click to expand...
Click to collapse
so when theres a new safe strape we can run diffrent roms??like multi boot? i havent read much on it intersting what roms can we flash
http://forum.xda-developers.com/galaxy-s5/general/sm-g900f-root-android-5-0-t2963451
Soon...
Are you saying we can't root?
I personally havent ever seen that post as i just stick mainly to the tmobile board, not the unified board.
But i have root on DOB1.
Just use odin (3.07) and flash the CF-Auto-Root for the G900T ( even though the link on the CF-auto-Root website says for 4.4.2)
I just got the phone, it was updated to Lollypop, I would rather put a rom on it anyways, do I need to revert back or something? some help would be nice, I am new to this Tmobile phone.
joachim123 said:
I personally havent ever seen that post as i just stick mainly to the tmobile board, not the unified board.
But i have root on DOB1.
Just use odin (3.07) and flash the CF-Auto-Root for the G900T ( even though the link on the CF-auto-Root website says for 4.4.2)
Click to expand...
Click to collapse
That's what I thought. I usually just flash a recovery and flash super su.
I rooted my device just fine after updating to 5.0 with the cf auto root for kitkat... worked like a charm on lollipop 5.0
So does any twrp recovery .
Sent from my Tmobile S5 on Lollipop 5.0
SuperSU installed but no SU
Hi,
Just installed the DOB1 build, installed Philz recovery which worked OK and also installed the SuperSU ZIP through recovery (UPDATE-SuperSU-v1.94.zip) .
Everything seemed fine. I launched several applications (BusyBox, Titanium Backup, terminal emulation) and all of them prompted SuperSU to grant root permission and I acknowledged the permission. SuperSU app itself says that root is enabled.
BUT - it seems that even though SuperSU believes it gives root permission - it does not. The apps keeps asking (and "granted" root per the toast message) but they do not get root and keep asking for that after 30 sec. or so.
I also tried terminal emulation. At the shell prompt I've entered "su", immediately I've got the prompt to allow root, I clicked OK and the in the terminal emulation the cursor just got stuck. never got the "#" prompt for root access.
If someone was able to actually grant root access to the apps, can you please share the steps you've done that? following the posts through Philz' recovery and root did not help, I did follow the same steps I've done before upgrading to lollipop...
Thanks,
Gil.
---------- Post added at 02:30 PM ---------- Previous post was at 02:19 PM ----------
gilbnx said:
Hi,
Just installed the DOB1 build, installed Philz recovery which worked OK and also installed the SuperSU ZIP through recovery (UPDATE-SuperSU-v1.94.zip) .
Everything seemed fine. I launched several applications (BusyBox, Titanium Backup, terminal emulation) and all of them prompted SuperSU to grant root permission and I acknowledged the permission. SuperSU app itself says that root is enabled.
BUT - it seems that even though SuperSU believes it gives root permission - it does not. The apps keeps asking (and "granted" root per the toast message) but they do not get root and keep asking for that after 30 sec. or so.
I also tried terminal emulation. At the shell prompt I've entered "su", immediately I've got the prompt to allow root, I clicked OK and the in the terminal emulation the cursor just got stuck. never got the "#" prompt for root access.
If someone was able to actually grant root access to the apps, can you please share the steps you've done that? following the posts through Philz' recovery and root did not help, I did follow the same steps I've done before upgrading to lollipop...
Thanks,
Gil.
Click to expand...
Click to collapse
Sorry guys! My mistake, I didn't use cf-autoroot. I just ODIN'ed the autoroot and now all is well!
Please anyone who's taken the update (via OTA or by flashing the full DOB1 tar) and then rooted and installed custom recovery: if you've since installed custom Roms, please head over to this thread and let us know how you did it, what steps you took, etc.
http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034
Thanks much!
I know this model is new, but how do we start a section for this model? It's a great phone with plenty under the hood. It seems to have an unlock oem bootloader option in the developer options. How can I root this phone, but more importantly, are there any custom ROMs which will work with it? Can there be some ported over? Any assistance appreciated.
This is the ZTE Warp 7 N9519 for Boost Mobile
:highfive:
GrimeSyndicate said:
I know this model is new, but how do we start a section for this model? It's a great phone with plenty under the hood. It seems to have an unlock oem bootloader option in the developer options. How can I root this phone, but more importantly, are there any custom ROMs which will work with it? Can there be some ported over? Any assistance appreciated.
This is the ZTE Warp 7 N9519 for Boost Mobile
:highfive:
Click to expand...
Click to collapse
I have this phone it seems unrootable. Help?
I know i have tge same device....someone getthis phone and help us...im stuck in the same spot.
I'm on the same page. Spent a few hours on trying to find a working root method but no success. However, King root, specifically version 4.1.0.703, worked for a bit then after close to 30 minutes, the phone restarted itself and was unrooted. I decided not to try it again especially since I just got this phone yesterday.
I have this phone too... Been all over the forums, all over xda university, and im still lost... If someone could give me a little direction, custom recovery or root access... Do i have to build from source? That seems a little above my pay-grade
so has anyone found a solution for rooting?
i looked at XDA a while back when i first got the phone but nothing.
ive been doing reaserch and placing my findings in a different androidforums.(website)
since i didnt see any options to post on here.
anyone wanna help us with info?
KingRoot works after a couple of tries, root access verified, but phone will reboot anywhere from 30 seconds to 30 minutes and root access is denied upon phone start. Haven't tried anything fancy in the little time I've had root access, then again I am not sure this phone is even compatible with custom recovery nor does it have any development of custom roms.. Wondering why the phone reboots and removed root, set SELinux to permissive to no avail, maybe there's a security package or two that could be disabled/blocked to prevent the phone from removing root access?
Really good phone for the money and the specs lend well to a debloated/custom ROM.. Not giving up on these lesser loved phones, finally got my S550TL rooted thanks to the helpful members here don't want to stop now lol.
Caddykings1987 said:
KingRoot works after a couple of tries, root access verified, but phone will reboot anywhere from 30 seconds to 30 minutes and root access is denied upon phone start. Haven't tried anything fancy in the little time I've had root access, then again I am not sure this phone is even compatible with custom recovery nor does it have any development of custom roms.. Wondering why the phone reboots and removed root, set SELinux to permissive to no avail, maybe there's a security package or two that could be disabled/blocked to prevent the phone from removing root access?
Really good phone for the money and the specs lend well to a debloated/custom ROM.. Not giving up on these lesser loved phones, finally got my S550TL rooted thanks to the helpful members here don't want to stop now lol.
Click to expand...
Click to collapse
Have you tried installing the su file with SuperSu before the device rebooted. Because when I had root for less than 10 minutes I checked to see if there was a su file installed and there wasn't any. Is like if KingRoot was simulating root access and didn't install the su file.
---------- Post added at 04:07 PM ---------- Previous post was at 04:01 PM ----------
Heartseed said:
I'm on the same page. Spent a few hours on trying to find a working root method but no success. However, King root, specifically version 4.1.0.703, worked for a bit then after close to 30 minutes, the phone restarted itself and was unrooted. I decided not to try it again especially since I just got this phone yesterday.
Click to expand...
Click to collapse
You should try installing the su file with SuperSu because KingRoot doesn't really install the su file and when the device reboots it removes all root access that KingRoot was simulating. I recommend getting root access with KingRoot then installing the su file with SuperSu and see if it works.
Has any one tried adding SuperSu after temp KingRoot? Or tried adding SuperSU and replacing KingRoot with Super-Sume Pro app?
Just tried Rooting with KingRoot thru APK and didn't even temp root
shezzy83 said:
Has any one tried adding SuperSu after temp KingRoot? Or tried adding SuperSU and replacing KingRoot with Super-Sume Pro app?
Just tried Rooting with KingRoot thru APK and didn't even temp root
Click to expand...
Click to collapse
If KingRoot is not temp rooting your device just go to recovery and clear cache then it should work. Also I wanted to update the su file with SuperSU when I had temp root but I fear it might brick or something. I found out the su was located at sbin.
Are we getting anywhere on this? I really like this phone but i need to de-bloat
drgsrbad81 said:
Are we getting anywhere on this? I really like this phone but i need to de-bloat
Click to expand...
Click to collapse
Not really, I just need someone to update the su binary with SuperSU once temp rooted with KingRoot to see if after that the root doesn't remove after reboot. Or maybe moving the Su file to xbin or bin since it is at sbin.
Tried to install binary through Chainfire SuperSU app and got the "binary update failed" message.
Weird how KingRoot simulates root access without installing any SU binaries, I was able to disable a few packages and verify root access through other apps until the phone restarted.
Can you flash an SU binary through flashify or similar app without restarting to bootloader/recovery (where root access is once again revoked)?
hmmm....thinking of using this as my next phone can anyone give info on a working Fastboot Mode? if there is then we can maybe do the same method of flashing a custom TWRP recovery in order to flash SuperSU
Really like this phone, just got it yesterday. I tried the temp root with kingroot and then after 5 or 10 minutes it rebooted. I'm a bit hesitant to download Flashify and try flashing as I do not know what will happen. But its a good start we have an entry point to work with :silly:
Caddykings1987 said:
Tried to install binary through Chainfire SuperSU app and got the "binary update failed" message.
Weird how KingRoot simulates root access without installing any SU binaries, I was able to disable a few packages and verify root access through other apps until the phone restarted.
Can you flash an SU binary through flashify or similar app without restarting to bootloader/recovery (where root access is once again revoked)?
Click to expand...
Click to collapse
Actually it does install a su binary because when I go to sbin I see a su file there
I was able to confirm root after rooting with kingroot and i tried replacing it with SU but it fails and reboots. I'm very new to ZTE as this is my first phone. I wouldn't think obtaining permanent root would be super difficult since we are able to get some sort of root with king. I am no code expert either so I remain in the dark...
mycosmicmind said:
I was able to confirm root after rooting with kingroot and i tried replacing it with SU but it fails and reboots. I'm very new to ZTE as this is my first phone. I wouldn't think obtaining permanent root would be super difficult since we are able to get some sort of root with king. I am no code expert either so I remain in the dark...
Click to expand...
Click to collapse
So I noticed something very helpful that will totally or maybe allow us to have permanent root. When I rooted with KingRoot I went to Superuser and it said that su binary can't be updated because of its location /sbin/su, so that shows that the su file needs to be at /xbin or /bin. We can try moving the su file to /xbin or /bin once we have temp root to see if it becomes permanent.
---------- Post added at 09:14 PM ---------- Previous post was at 09:13 PM ----------
So I noticed something very helpful that will totally or maybe allow us to have permanent root. When I rooted with KingRoot I went to Superuser and it said that su binary can't be updated because of its location /sbin/su, so that shows that the su file needs to be at /xbin or /bin. We can try moving the su file to /xbin or /bin once we have temp root to see if it becomes permanent.
i can try tomorrow, i dont know if i'll be able to do it before a reboot though
mycosmicmind said:
i can try tomorrow, i dont know if i'll be able to do it before a reboot though
Click to expand...
Click to collapse
The average is about 5 minutes that it allows you to have root, sometimes it let's you even more but it reboots.