I just rooted the S3 using ODIN, but I still can't get into the data partition. [adb backup -f data data.img] doesn't seem to work (it asks me to confirm it on my phone...broken screen), and neither does [adb pull /data/data %userprofile%\desktop]. It's on 4.3 and usb debugging is disabled. The only thing I need is to have usb debugging enabled and I can take it from there. I've tried editing the settings.db file in com.android.providers.settings, and when I use [adb devices], it lists the S3 but it says it's offline (probably because I have to allow it on the phone, but the touchscreen is broken). Any suggestions?
tl;dr I need to pull files from /data/data, keep getting denied. If I can get usb debugging to work on 4.3 I may be able to figure out the rest myself.
edit: I couldn't find one (three days of searching), but if anyone knows of a 4.3 ODIN file with usb debugging enabled for all computers, please let me know.
edit 2: By broken, I mean completely shattered.
You may want to push Wireless ADB.I believe it does turn on Debug by default. Then there's ADB Commander or suchlike app for PC. It can get to the Partition.
Perseus71 said:
You may want to push Wireless ADB.I believe it does turn on Debug by default. Then there's ADB Commander or suchlike app for PC. It can get to the Partition.
Click to expand...
Click to collapse
Android Commander is a godsend, but I've installed every Wireless ADB through play.google.com to the S3 and I've had no luck. [adb devices] still shows the S3's serial number, but it still says that it's offline. Is there any ODIN tarball that has usb debugging enabled by default? or is there a way I can downgrade to 4.1.2 from 4.3?
Youll probably need an insecure kernel.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Youll probably need an insecure kernel.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I can't find any ODIN-able insecure kernels, but I can get into ADB while I'm in recovery. How would I go about flashing an update.zip I put in /sdcard through adb? Thanks in advance.
Ill try to make one for you in a while. What rom/build were you running?
Sent from my SGH-T999 using Tapatalk
Hetes the kernel thread. Its in general section.
http://forum.xda-developers.com/showthread.php?t=2407583
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Hetes the kernel thread. Its in general section.
http://forum.xda-developers.com/showthread.php?t=2407583
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Ah. I've found that thread yesterday while searching for an insecure kernel after reading your reply. However, I couldn't seem to find one for my ROM. Thanks though!
DocHoliday77 said:
Ill try to make one for you in a while. What rom/build were you running?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
That would be great! But the ROM I'm using is the root66 T999_UVUEMJC from this thread. It was the earliest one that would flash without a NAND write error and the only other ODIN root I could find; I tried using CF-root but it didn't seem to stick.
Related
I've been trying to root all damn day using this link:
http://forum.xda-developers.com/showthread.php?t=1311194
Than tried that Samsung S2 Tool Kit and I don't know whats going on now, I have CWM 5.0.6 or whatever on my device but it won't allow root it keeps not allowing it than after trying that Tool Kit I can't even get into my device now even with Debugging turned (ON)??? geezzz:crying:
TheCrow1372 said:
I've been trying to root all damn day using this link:
http://forum.xda-developers.com/showthread.php?t=1311194
Than tried that Samsung S2 Tool Kit and I don't know whats going on now, I have CWM 5.0.6 or whatever on my device but it won't allow root it keeps not allowing it than after trying that Tool Kit I can't even get into my device now even with Debugging turned (ON)??? geezzz:crying:
Click to expand...
Click to collapse
Did you flash superuser?
Sent from my SGH-T989 using XDA
TheTechNiq said:
Did you flash superuser?
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
I can't even get my USB to allow me in now, even with USB Debugging ON??
The first time I rooted I had a similar problem. Even after flashing super-user Titanium would tell me I wasn't rooted.
In the end downloading a different super user version fixed the problem.
Not sure what to suggest for your usb problem though... Have you tried turning it off and on again?
Try getting to dload mode. Flash stock. Retry root maybe
Sent from my SGH-T989 using XDA
TheCrow1372 said:
I've been trying to root all damn day using this link:
http://forum.xda-developers.com/showthread.php?t=1311194
Than tried that Samsung S2 Tool Kit and I don't know whats going on now, I have CWM 5.0.6 or whatever on my device but it won't allow root it keeps not allowing it than after trying that Tool Kit I can't even get into my device now even with Debugging turned (ON)??? geezzz:crying:
Click to expand...
Click to collapse
To fix your problem with not getting into your phone you'll follow these directions
http://galaxys2root.com/t-mobile-ga...-to-ics-stock-on-t-mobile-galaxy-s2-sgh-t989/
Then after you do this you will have to put ics back on your phone or just flash a rom that is 4.0.3
This is what you should download download the file and use this superuser I had a problem rooting to.
http://downloadandroidrom.com/file/GalaxyS2TMobile/rooting/tmobilegalaxys2rootICS.zip
Sent from my SGH-T989 using xda premium
The root was finally completed in recovery but after rebooting and going into ES Explorer like normal in Settings to set (Root) user, it says not accessable also using the Superuser app from Google Play it says (root failed) but in recovery it said (root achieved and enjoy) so yeah makes no sense also should I just flash the theme I want in and see if that works out (Juggernaut 5.0)?
I used a video to unroot my phone and now it will not come out of boot mode, I turn it on it acts like it is booting up but never does just stays in the same position. and when I try to go into fastboot mode I get an error, it shows an android laying down and a red triangle over him how do I fix this? PLEASE HELP
follow this exactly as its written: http://forum.xda-developers.com/showthread.php?t=1626895
I will try this, but I am not sure that the computer is reading the phone, I can get odin to work but it is not helping I tried putting stock files using odin but same thing. when i tried cmd and fastboot devices it brings up nothing
when I plug my phone in my computer does not recognize it, now what do I do?
Zepius said:
follow this exactly as its written: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
did everthing step by step, I am able to see the device in my device manager, but when I get to the part where I put it in bootloader and and type fastboot devices it does not recognize it. any suggestions?
pamelak38 said:
did everthing step by step, I am able to see the device in my device manager, but when I get to the part where I put it in bootloader and and type fastboot devices it does not recognize it. any suggestions?
Click to expand...
Click to collapse
You need to install the fastboot driver.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
You need to install the fastboot driver.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I cannot turn my phone on to put it on usb debugging, could this be my problem? and how do I install fastboot driver I thought I had it with sdk tools
pamelak38 said:
I cannot turn my phone on to put it on usb debugging, could this be my problem? and how do I install fastboot driver I thought I had it with sdk tools
Click to expand...
Click to collapse
When you are booted into bootloader but a "fastboot devices" does not list your device, it's almost always caused by having installed either no driver at all or the wrong one. Use the naked driver, follow the link in my signature to find it.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
When you are booted into bootloader but a "fastboot devices" does not list your device, it's almost always caused by having installed either no driver at all or the wrong one. Use the naked driver, follow the link in my signature to find it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ok I got it up and running! My only concern is I did every step but the radio step failed every time, is this a problem?????
THANK YOU SO MUCH, I HAVE LEARNED A LOT FROM THIS!!
pamelak38 said:
Ok I got it up and running! My only concern is I did every step but the radio step failed every time, is this a problem?????
THANK YOU SO MUCH, I HAVE LEARNED A LOT FROM THIS!!
Click to expand...
Click to collapse
Lte radio? Anyway if your connection is ok I'd say it's not an issue.
Good you figured it out.
Sent from my Galaxy Nexus using Tapatalk 2
still cant get into recovery mode
can anyone help, I got the phone back to where I can get into it, but if I try to go into recovery mode I still get the dead android with the red triangle and can anyone tell me where to find a lte radio
pamelak38 said:
can anyone help, I got the phone back to where I can get into it, but if I try to go into recovery mode I still get the dead android with the red triangle and can anyone tell me where to find a lte radio
Click to expand...
Click to collapse
What you see is the stock recovery. Android will flash it back automatically even after you've flashed a custom recovery. To prevent this, you must either rename/delete /etc/install-recovery.sh OR rename/delete /system/recovery-from-boot.p.
LTE radios are in the factory images. Read this: http://forum.xda-developers.com/showthread.php?t=1626895
Petrovski80 said:
What you see is the stock recovery. Android will flash it back automatically even after you've flashed a custom recovery. To prevent this, you must either rename/delete /etc/install-recovery.sh OR rename/delete /system/recovery-from-boot.p.
LTE radios are in the factory images. Read this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Ok, I have never had to rename/delete,ect before, can you help walk me thru that, I know I am asking a lot but I would sure appreciate it
pamelak38 said:
Ok, I have never had to rename/delete,ect before, can you help walk me thru that, I know I am asking a lot but I would sure appreciate it
Click to expand...
Click to collapse
Do you have root? In that case it's a matter of launching your file manager.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
Do you have root? In that case it's a matter of launching your file manager.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes I have root, now what do I need to do?
pamelak38 said:
Yes I have root, now what do I need to do?
Click to expand...
Click to collapse
Navigate to the folder /etc with a file manager. Remount with RW rights (root explorer has a convenient button for this) and rename the file install-recovery.sh to install-recovery.sh.bak.
Then reflash a custom recovery. This time it will stick.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
Navigate to the folder /etc with a file manager. Remount with RW rights (root explorer has a convenient button for this) and rename the file install-recovery.sh to install-recovery.sh.bak.
Then reflash a custom recovery. This time it will stick.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I got it back to stock and locked, THANK YOU so much you are awesome!!!!
Hi,
Has anyone any idea how to restore my Galaxy Nexus to original without using USB?
I have a Galaxy Nexus Android 4.2.2. The USB doesn't working, however when connected to the power it recharges the battery but turns the phone off.
I can not use USB connection to computer either because the phone switches off immediately.
The phone has been rooted and I can access the root section when the phone turned on and I can upload any file via SMB.
I just need some info on what to do to restore the phone to it's original condition and so remove the info on rooting.
Please don't send me info on any external USB connection because I've tried it all and it does not working.
Thanks
gabcix said:
Hi,
Has anyone any idea how to restore my Galaxy Nexus to original without using USB?
I have a Galaxy Nexus Android 4.2.2. The USB doesn't working, however when connected to the power it recharges the battery but turns the phone off.
I can not use USB connection to computer either because the phone switches off immediately.
The phone has been rooted and I can access the root section when the phone turned on and I can upload any file via SMB.
I just need some info on what to do to restore the phone to it's original condition and so remove the info on rooting.
Please don't send me info on any external USB connection because I've tried it all and it does not working.
Thanks
Click to expand...
Click to collapse
You can use adb over network via developer options.then it is possible to restore stock and lock your phone by using wugs tools from pc.
Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
http://forum.xda-developers.com/showpost.php?p=28178320&postcount=2
standa75 said:
You can use adb over network via developer options.then it is possible to restore stock and lock your phone by using wugs tools from pc.
Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
Click to expand...
Click to collapse
Thanks mate for your help but I have no idea what are you talking about. Would you be kind enough to explain it for me?
efrant said:
http://forum.xda-developers.com/showpost.php?p=28178320&postcount=2
Click to expand...
Click to collapse
Thanks for your info but I forgot to tell in my first post that the fastboot mode is not working. The phone shows the Android icon when I press the volume up+down+pwr buttons but it turns out once I release them. So I have to upload the files wia network from my computer but I don't know what files and what to edit....
gabcix said:
Thanks for your info but I forgot to tell in my first post that the fastboot mode is not working. The phone shows the Android icon when I press the volume up+down+pwr buttons but it turns out once I release them. So I have to upload the files wia network from my computer but I don't know what files and what to edit....
Click to expand...
Click to collapse
You don't need access to fastboot if you have root.
Install ROM Manager from the Play Store and use that to install CWM. The just flash the zip in the post i linked to. (Flash a superuser zip right after as well if you want root.)
Sent from my Nexus 4 using Tapatalk 2
Did you try a different USB cable? I had similar issue, and drove me crazy for several days. The issue was the cable.
Note that the cable was working fine to connect a galaxy s2 to PC, but failed to connect the GNex
Sent from my Galaxy Nexus using xda app-developers app
Worst case, download mobile Odin via play store. If u still have root access then your good. Search for latest gnex stock image(its available to public in its original form made for restore purposes or manual upgrade) keep in mind this wipes everything. While using app ensure ever root is enabled otherwise you'll lose root. The stock image should be in tgz format or something similar. Extract it to your SD card, it will give u a folder. Inside the folder is a bunch of files( possibly a folder within a folder, been a while for me). When using mobile Odin u manually select the boot.IMG system.IMG radio.IMG user data.IMG so if u know the problem u can choose just what u need. Sounds complicated as hell but its really simple. I figured this to be a temporary solution as my laptop had no internet to download need files to restore. Only problem is Mobil Odin isn't free about 4 bucks I think. But well worth the money
Sent from my Galaxy Nexus using xda premium
gabcix said:
Thanks mate for your help but I have no idea what are you talking about. Would you be kind enough to explain it for me?
Click to expand...
Click to collapse
Under developer options is option "adb over the network", so if you select this your phone will get ip address and listening port and then you can access it via your computer on that specifics ip/port.
Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
efrant said:
You don't need access to fastboot if you have root.
Install ROM Manager from the Play Store and use that to install CWM. The just flash the zip in the post i linked to. (Flash a superuser zip right after as well if you want root.)
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Unfortunately the restore process didn't work from the ROM manager. It just stuck at the restart and didn't do anything. I will send it back and let's see what Samsung will tell me.
Thanks for your help anyway.
gabcix said:
Unfortunately the restore process didn't work from the ROM manager. It just stuck at the restart and didn't do anything. I will send it back and let's see what Samsung will tell me.
Thanks for your help anyway.
Click to expand...
Click to collapse
As per usual when changing ROMs, you need to wipe data (in most cases) for your device to boot.
Hey fellaz,
Earlier, I was installing some apps for a custom keyboard. I was notified by Android that I needed to update the APK installer (I cannot remember the exact dialog) which I installed. After that, whenever I tried to open ANY .apk file, it kept saying the installer has stopped working. Couple minutes later, the phone rebooted and was stuck in a loop.
I read this thread: http://forum.xda-developers.com/showthread.php?t=1856188&page=4 , but I am completely new to working with ADB. I did manage to install the SDK and update it. I booted into Recovery mode and tried the command 'adb backup -all' (given in another thread) and I was given "adb: unable to connect for backup."
Unless I did something wrong, I doubt ADB would work since I'm not booted into the phone right? (http://forum.xda-developers.com/showpost.php?p=30826050&postcount=32)
I would just like to back up maybe one or two folders that are crucial to me.
Any advice? Is there anything Verizon can do if I take it into the store?
Thanks!
EDIT: Forgot to add that I have the phone completely stock. I'm debating whether or not to do a hard reset as I'm reading conflicting reports of sdcard being saved and not being saved.
Thats your problem. Adb works only on custom recovery's. There is a thread on flashing the stock image via fastboot without wiping data. I think thats your only solution..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Thats your problem. Adb works only on custom recovery's. There is a thread on flashing the stock image via fastboot without wiping data. I think thats your only solution..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
would you kindly point me to that thread? I found this one, "how-to-install-jelly-bean-on-galaxy-nexus/" (search on google, guide from betanews) but I don't think that is what you're speaking of.
tangosmango said:
would you kindly point me to that thread? I found this one, "how-to-install-jelly-bean-on-galaxy-nexus/" (search on google, guide from betanews) but I don't think that is what you're speaking of.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2377307
Here you go. Hope it works. One tip: read it very carefully and maybe multiple times..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
http://forum.xda-developers.com/showthread.php?t=2377307
Here you go. Hope it works. One tip: read it very carefully and maybe multiple times..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
[ a) Turn on USB Debugging
I'm not sure if I had that on. I doubt there is a way to turn USB debugging on without booting right?
In any case, I was able to follow the steps and now it just says 'waiting for device'
tangosmango said:
[ a) Turn on USB Debugging
I'm not sure if I had that on. I doubt there is a way to turn USB debugging on without booting right?
In any case, I was able to follow the steps and now it just says 'waiting for device'
Click to expand...
Click to collapse
Hmm thats quite a problem. Its waiting for device because USB debugging is off.. You cant turn it on without booting. I'll search for you but it might be that I cant help you.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Hmm thats quite a problem. Its waiting for device because USB debugging is off.. You cant turn it on without booting. I'll search for you but it might be that I cant help you.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
hey, I really appreciate your help but I did a hard reset which fixed everything. I did however lose a lot of data (from my last backup).
Again, thanks for your help!
you do not need usb debugging for fastboot so do not worry about turning that on.
Ok, so I have been looking into some of the SuperSU.zip files and sound that there are a few that actually dont make the phone go into boot loop. I double checked the system/xbin and su is installed as well as busybox. Then When I replace a 64 bit su file into Superuser 2.19, supersu app keeps telling me to update the binaries. Thats where Im stuck. So to recap.
I used the root method from CF-autoroot.
Once it failed I pulled the battery and flashed SuperSU-v2.19zip..
Now I get the binary update notification...
If I can just get some help from anyone that knows what they are doing that would be awesome..
Here is the Modded zip.. https://drive.google.com/file/d/0B6opNIGQWcVYT1JRMmtrNFUtbE0/view?usp=sharing
BTW: I got the 64 su file from root junky...
I know you've tried a lot more than posted here, not sure if all attempts but did you try CWM recovery in any of the superuser flashes?
I think the su binary is dependent on the application. SuperSU is telling you update the binary and going no further?
TWRP and SuperSU are bound to Google's interactive shell limitations to remain in Google Play. They may not be the most capable sources to deal with latest Samsung increased security. Those may be reasons older applications targeted to lollipop are working better than latest.
Sent from my SM-N910P using Tapatalk
samep said:
I know you've tried a lot more than posted here, not sure if all attempts but did you try CWM recovery in any of the superuser flashes?
I think the su binary is dependent on the application. SuperSU is telling you update the binary and going no further?
TWRP and SuperSU are bound to Google's interactive shell limitations to remain in Google Play. They may not be the most capable sources to deal with latest Samsung increased security. Those may be reasons older applications targeted to lollipop are working better than latest.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have tried that... the earlier builds flash without bootloop.. v2.16-2.19, newer builds, v2.30 on up, send it to bootloop.. i just felt i was getting closer with the modded su and the notification.
Ive been at it for like 2 weeks.. lol..
z31k said:
I have tried that... the earlier builds flash without bootloop.. v2.16-2.19, newer builds, v2.30 on up, send it to bootloop.. i just felt i was getting closer with the modded su and the notification.
Ive been at it for like 2 weeks.. lol..
Click to expand...
Click to collapse
So beta 2.49 SuperSU fails also? Have you tried its su binary with those earlier builds targeted at lollipop? Maybe there was a reason for beta; can't be released in Play, no terms would apply to it. Wishful thinking?
None of the su binaries work?
Regards,
Edit: by definition, the terms indicated how interactive shell interacts with SEAndroid or SELinux. Maybe the /system/vendor/lib/liboemcrypto.so and /system/lib/libselinux.so need to be swapped with the first Lollipop tar that dropped? OB7 for Sprint Note 4.
Edit 2: if using custom kernel, don't need liboemcrypto.so
Sent from my SM-N910P using Tapatalk
samep said:
So beta 2.49 SuperSU fails also? Have you tried its su binary with those earlier builds targeted at lollipop? Maybe there was a reason for beta; can't be released in Play, no terms would apply to it. Wishful thinking?
None of the su binaries work?
Regards,
Edit: by definition, the terms indicated how interactive shell interacts with SEAndroid or SELinux. Maybe the /system/vendor/lib/liboemcrypto.so and /system/lib/libselinux.so need to be swapped with the first Lollipop tar that dropped? OB7 for Sprint Note 4.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
How can u swap it with a locked boooader
Sent from my SM-N910P using XDA Premium HD app
pbedard said:
How can u swap it with a locked boooader
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
The OP says he can flash mods. I'm assuming here and you know the consequences of such, but thought it also possible to mount system and use the TWRP file manager to edit system.
I'm still OB7 but following with interest regarding the root of OG5 and recovery methods.
Edit: If L Speed Mod flashes successfully, default mode should give more freedom if using ADB and it doesn't need root. I think it's all shell scripts. (ADB Insecure required for booted mode adb access.)
Sent from my SM-N910P using Tapatalk
Yea i debloated it wothout root in an adb abell
Sent from my SM-N910P using XDA Premium HD app
Ill look into it flashing l speed mods.. maybe that can be a door... I know that Selinux and fix permissions can be applied via TWRP. SU binaries are applied.. they were in the system folders. So su is where its supposed to be. Busybox is where its supposed to be, 2.49 does not work just older builds. Its all a matter of figuring out how to update binaries??
pbedard said:
Yea i debloated it wothout root in an adb abell
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
I would love to debloat in adb shell, however whenever I make a shell environment the device will not detect in adb shell. regular adb commands is fine, just when I start shell.. Suggestions?
Flashing speed mod did not help.. Same issue with the binaries not being updated.. Anyone got anymore ideas?
z31k said:
Flashing speed mod did not help.. Same issue with the binaries not being updated.. Anyone got anymore ideas?
Click to expand...
Click to collapse
I'm out of ideas. Maybe the kernel devs will figure it out when source drops. Everything seems to be pointing that direction due to S6 exploit required.
Did L Speed Mod do anything to help with adb access or adb shell? I have to use ADB Insecure to use adb in booted mode with stock OB7 kernel; initial lollipop release. I was hoping that would help TW 5.1.1 as well.
Did you get the init.d test to pass? Here's a good tutorial; I think it's the developer's tut.
https://youtu.be/zOUrd04dvI4
Sent from my SM-N910P using Tapatalk
samep said:
I'm out of ideas. Maybe the kernel devs will figure it out when source drops. Everything seems to be pointing that direction due to S6 exploit required.
Did L Speed Mod do anything to help with adb access or adb shell? I have to use ADB Insecure to use adb in booted mode with stock OB7 kernel; initial lollipop release. I was hoping that would help TW 5.1.1 as well.
Did you get the init.d test to pass? Here's a good tutorial; I think it's the developer's tut.
https://youtu.be/zOUrd04dvI4
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you for the link.. I'm going to try that out when i get some time. I didnt try adb on this run.. I Will test it.
z31k said:
Thank you for the link.. I'm going to try that out when i get some time. I didnt try adb on this run.. I Will test it.
Click to expand...
Click to collapse
You're welcome. Just try the default settings once you know init.d works. Maybe you won't need root since you can flash scripts.
Hang in there. I don't think it will long. It would sure be nice if all carriers got a developer edition. I'm all for security but not at the price of losing root. I still prefer the stock kernel. Now I may be looking for a near stock kernel again.
Sent from my SM-N910P using Tapatalk
samep said:
You're welcome. Just try the default settings once you know init.d works. Maybe you won't need root since you can flash scripts.
Hang in there. I don't think it will long. It would sure be nice if all carriers got a developer edition. I'm all for security but not at the price of losing root. I still prefer the stock kernel. Now I may be looking for a near stock kernel again.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Well, that's the thing. I need all the help i can get. I posted over here because you guys have development. I have been watching your forum like a hawk, just waiting for you guys to get 5.1.1. Lol....We dont in the sprint note edge forum. But i figure its the same hardware.
So with all that said, i really appreciate your help. Its a great step at a fresh direction.