Related
This is going to be simply a collection of links with important points...Please read ALL directions and comments carefully...as no one is responsible for any damage to your phone.
NOTE 1: IF YOU ARE UNROOTED AND ALREADY UPDATED WITH OTA, YOU CAN STILL USE THE PROCESSES BELOW TO ROOT AND FLASH RECOVERY.
>> Rooting Samsung Fascinate
>> Flashing Clockwork Recovery
NOTE 2: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.
If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock
If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image
NOTE 3: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.
If you want to stop the OTA update notification, use this file which provides simple edits...but be careful as it may make further updates more difficult >> SCH-I500.DI01 Update
UPDATED:
OTA Update with Root and Busybox >> DH12 to DI01 update with root and busybox
Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
My path.
1) Stock with root mentioned in this dev section
2)restored CW backup
3)used CW to install the update mentioned in this thread.
No problems so far.
After reading this thread again I went to stock and stock kernel. Rooted and gold again.
I think that CPU Scale app causes the Fascinate to shut down, so if you use it and getting them.... remove the app or let me know if you fixed.
Thanks!!!
Now, here is something I didn't try yet. I am still stock (not rooted), ran the OTA...and with all people having issues, I am scared to root. I want to try but I think I will wait and see if anyone else does this.
tats_06 said:
This is going to be simply a collection of links with important points...
>> Rooting Samsung Fascinate
>> Flashing Clockwork Recovery
NOTE 1: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.
If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock
If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image
NOTE 2: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.
If you don't care about root and want to install the OTA update manually >> SCH-I500.DI01 Update
Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
Click to expand...
Click to collapse
I thought the post about doing the OTA manually would allow you to keep root, seeing that it's a stripped down version.
Let me clarify that. If that's the case, I can update the OP.
Restored, updated and Rerooted
All is well. No problems so far.
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.
If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.
Read before using, that's all I ask.
namebrandon said:
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.
If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.
Read before using, that's all I ask.
Click to expand...
Click to collapse
Thanks for heads up...first post updated.
Bump.... Back to top till this gets stickied!
wasupwithuman said:
Bump.... Back to top till this gets stickied!
Click to expand...
Click to collapse
Thanks! I just reported it too to request for sticky.
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
Sent from my SCH-I500 using XDA App
azalvarez03 said:
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks.
tats_06 said:
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks.
Click to expand...
Click to collapse
I don't think the update blocks root. you should be able to install the OTA as long as your not rooted, then once it is installed go ahead and root your device.
Ok...looks like root went thru...working on cwm recovery now.
OK, recovery installed successfully...running a backup right now.
Should I test restoring? Or should I assume I am safe?
Rooting after OTA update.
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
lukaro said:
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
Click to expand...
Click to collapse
If you have CWM installed, you always have root via adb, which means you can get your root apps working.
If you're not running CWM, I don't know. Someone who's tried rage.bin post-update could tell you.
lukaro said:
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
Click to expand...
Click to collapse
Yes you can root after update, I did it fine, but had to attempt it twice, the first try it hung, so had to do a battery pull, and then the second time it worked fine.
Nothing in the update seems worth it to return to stock (I've removed so many stock apps already.)
I'm having the Force Close loop issue. My CWR seems to be missing, as all I can access is Android system recovery <2e> with the options of:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Using the Odin method didn't work for me, on multiple tries. My SD card appears to be wiped clean and I can't enter debug mode.
Is there anything short of a miracle that I can do to fix my phone? I've seen a few posts with people saying they had similar problems as mine, but there was never and explanation of how or if they fixed there phone.
Thanks in advance
Can someone advise on the ota update.. I don't quite understand entirely boot loaders and such.. My note 2 is stock rooted. I don't think I will ever Change roms, but I want to stay rooted.
What is the verdict for someone like me? I do not want to block ota then miss other important updates, but I do not want to lose root either.
Please advise.
Again, sorry for such a basic question. I am still transistioning from iPhone world
Sent from my iPad using Tapatalk HD
crash613 said:
Can someone advise on the ota update.. I don't quite understand entirely boot loaders and such.. My note 2 is stock rooted. I don't think I will ever Change roms, but I want to stay rooted.
What is the verdict for someone like me? I do not want to block ota then miss other important updates, but I do not want to lose root either.
Please advise.
Again, sorry for such a basic question. I am still transistioning from iPhone world
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
Just block it. Sure devs will find a way to root and unlock again soon. At that point, you can restore the SDM 1.0 and get later updates if you need them.
You're sure to lose root within 5 days if you don't.
Ok, based on what you say you don't want to rom but you want root. That is where I am. There is an app called voodoo ota rootkeeper in the play store. It is free. Install it and use it to backup root. Take the update and use voodoo to restore root.
That will get you root and a locked bootloader. Which is where I read you want to be. But remember you may be stuck with a locked bootloader forever.
That said consider this. Pass on the update for now. You can always update to it later to get the next update. By waiting you keep your options open and miss nothing.
TonikJDK said:
Ok, based on what you say you don't want to rom but you want root. That is where I am. There is an app called voodoo ota rootkeeper in the play store. It is free. Install it and use it to backup root. Take the update and use voodoo to restore root.
That will get you root and a locked bootloader. Which is where I read you want to be. But remember you may be stuck with a locked bootloader forever.
That said consider this. Pass on the update for now. You can always update to it later to get the next update. By waiting you keep your options open and miss nothing.
Click to expand...
Click to collapse
Good advice. This is my plan as well.
Sent from my SCH-I605 using xda app-developers app
Thank you both for the quick replies. I think that is what I am going to do. Block it for now, using titanium. Then wait and see.
I am going to look in to that other program though. Right now I feel I will always want to reman stock-rooted, but who knows... No point in closing that door forever.
Just so I have this straight..... Using titanium I backed up the sdm 1.0 file, then in the same screen I click on it and choose delete? That's it? Thanks for being patient with me.
crash613 said:
Thank you both for the quick replies. I think that is what I am going to do. Block it for now, using titanium. Then wait and see.
I am going to look in to that other program though. Right now I feel I will always want to reman stock-rooted, but who knows... No point in closing that door forever.
Just so I have this straight..... Using titanium I backed up the sdm 1.0 file, then in the same screen I click on it and choose delete? That's it? Thanks for being patient with me.
Click to expand...
Click to collapse
Yes, although I believe it's "Un-install", not delete. You could freeze it as well, if you have the paid for version.
Sent from my SCH-I605 using xda app-developers app
I have a Note 2 that was rooted using a root-injected stock OS. Unfortunately, the OTA got me this morning and I have lost root. At the following link several folks have replied that they were able to get their Note 2's rooted after the OTA. What do you guys think? I don't want to brick my phone but I sure need Root-Explorer and Titanium Backup.
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Guitar4Him said:
I have a Note 2 that was rooted using a root-injected stock OS. Unfortunately, the OTA got me this morning and I have lost root. At the following link several folks have replied that they were able to get their Note 2's rooted after the OTA. What do you guys think? I don't want to brick my phone but I sure need Root-Explorer and Titanium Backup.
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Click to expand...
Click to collapse
I can now confirm that, if you have a rooted, stock Note II and lose root through the OTA, you can go the Odin route with a rooted stock image and successfully root the device. Additionally, if you install Voodoo OTA Rootkeeper after rooting the device, you can then, do the OTA and restore root using the Voodoo app. Instructions and files are available at:
http://forum.xda-developers.com/showthread.php?t=2024207
Please post Questions in Q&A'
Thread moved
Friendly Neighborhood Moderator
http://forum.xda-developers.com/showpost.php?p=37066564&postcount=1167
I can confirm that a handy dandy combination of:
1. Deferring the update
2. Rooting via ExynosAbuse
3. Backing up root via Voodoo OTA Rootkeeper
4. Updating
will maintain root with the latest Verizon Galaxy Note 2 update.
I am now I605VRALL4and my Device Status says "Normal" since I haven't flashed anything.
y8s said:
I am now I605VRALL4and my Device Status says "Normal" since I haven't flashed anything.
Click to expand...
Click to collapse
I did what you did and I am modified. I did the light sabre mod. But I don't think that would do it.
Edit......reboot and mine is back to normal.
So, I noticed that my S4 had a new software update and I started to download it, then walked back to my desk to read what was in it and was surprised to find out that the new update would lock the bootloader (which I definitely don't want). As of now, I'm delaying INSTALLING it but because it was downloaded, it keeps bugging me to install it.
My question was am I still good to root my phone, even if it's been downloaded to my phone? Or is it likely the bootloader has already been locked and installing the update will just install the rest of the files? I assume now is probably the best time to root it (since I likely won't have the option down the road). I just wanted to check with you guys first. Let me know when you get the chance. Thanks!
jbrookley said:
So, I noticed that my S4 had a new software update and I started to download it, then walked back to my desk to read what was in it and was surprised to find out that the new update would lock the bootloader (which I definitely don't want). As of now, I'm delaying INSTALLING it but because it was downloaded, it keeps bugging me to install it.
My question was am I still good to root my phone, even if it's been downloaded to my phone? Or is it likely the bootloader has already been locked and installing the update will just install the rest of the files? I assume now is probably the best time to root it (since I likely won't have the option down the road). I just wanted to check with you guys first. Let me know when you get the chance. Thanks!
Click to expand...
Click to collapse
You can still root it if the update wasn't installed. As long as it says your on mdk and not on me7 under "about phone" in the settings you should have no problem rooting. After rooting use a app like titanium backup or my backup pro to freeze sdm and fwupgrade....in system apps.
jbrookley said:
So, I noticed that my S4 had a new software update and I started to download it, then walked back to my desk to read what was in it and was surprised to find out that the new update would lock the bootloader (which I definitely don't want). As of now, I'm delaying INSTALLING it but because it was downloaded, it keeps bugging me to install it.
My question was am I still good to root my phone, even if it's been downloaded to my phone? Or is it likely the bootloader has already been locked and installing the update will just install the rest of the files? I assume now is probably the best time to root it (since I likely won't have the option down the road). I just wanted to check with you guys first. Let me know when you get the chance. Thanks!
Click to expand...
Click to collapse
If it only downloaded, and you did not install it, then you are good to root. I would delete the update.zip file from the cache to be safe though.
Please read forum rules before posting
Questions and Help issues go in Q&A and help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I just downloaded a OTA update on my S4, which I hoped was 4.4.4, but it looks like it is still Android 4.4.2. During the update, it says it was also updating KNOX, does anyone know what this update is, I was hoping it was the 4.4.4 upgrade. It did update KNOX to 2.0, so hopefully I can move my work stuff into KNOX now, and not have my basic phone subject to my work's locking policy.
The build number is KOT49H.I545VRUFNG6.
reckert said:
I just downloaded a OTA update on my S4, which I hoped was 4.4.4, but it looks like it is still Android 4.4.2. During the update, it says it was also updating KNOX, does anyone know what this update is, I was hoping it was the 4.4.4 upgrade. It did update KNOX to 2.0, so hopefully I can move my work stuff into KNOX now, and not have my basic phone subject to my work's locking policy.
The build number is KOT49H.I545VRUFNG6.
Click to expand...
Click to collapse
It's just small bug fixes for bluetooth connectivity and updates for KNOX 2.0.
Oh noze! Search is borken again.
How do you stop the ota updates
siouxhockey11 said:
How do you stop the ota updates
Click to expand...
Click to collapse
Download Titanium Backup and try to freeze SDM, you might have to purchase Titanium Backup Pro to freeze apps.
When it asks just click , No Thanks.. Update won't show again till you manually look for an update in settings.
I see the method for rooting the G6 involves the roll back to G5 and flashing G6. I've already towel rooted G5, will accepting the G6 OTA remove root for me because of the knox update? IOW if I want the LAG, is it better to flash G6 via odin, or can I just accept the OTA?
Thanks for your time!
BrianLayman said:
I see the method for rooting the G6 involves the roll back to G5 and flashing G6. I've already towel rooted G5, will accepting the G6 OTA remove root for me because of the knox update? IOW if I want the LAG, is it better to flash G6 via odin, or can I just accept the OTA?
Thanks for your time!
Click to expand...
Click to collapse
You will lose root if you flash NG6 on Odin or Accept the OTA update. The only way to keep root is to follow that flash back method if you want the update and keep root. My advice is not to updated at all. The NG6 update has issues with random reboots.
Fadtydawg said:
You will lose root if you flash NG6 on Odin or Accept the OTA update. The only way to keep root is to follow that flash back method if you want the update and keep root. My advice is not to updated at all. The NG6 update has issues with random reboots.
Click to expand...
Click to collapse
I would also advise not taking the NG6 update. I did and I went back to NC5. The random reboots seem to be unfixable and there really wasn't anything new and exciting with NG6, unless you need Knox 2.0 for some crazy reason! STAY WITH NC5!!!
michaely123 said:
Download Titanium Backup and try to freeze SDM, you might have to purchase Titanium Backup Pro to freeze apps.
Click to expand...
Click to collapse
I disabled SDM with 'No Bloat". Annoying notification for update is gone.
wulto said:
I disabled SDM with 'No Bloat". Annoying notification for update is gone.
Click to expand...
Click to collapse
Will this work for non-rooted phones?
dwmartin6341 said:
Will this work for non-rooted phones?
Click to expand...
Click to collapse
No u need a rooted phone.
Fadtydawg said:
When it asks just click , No Thanks.. Update won't show again till you manually look for an update in settings.
Click to expand...
Click to collapse
Say what? Mine is prompting me to install the update. It only gives me 2 choices "Install now" and "Install later", and if I choose later, it prompts me to pick a time for it to install. There is also a checkbox that says "Install automatically", which I am leaving unchecked. So, I think it's going to prompt me every day from now on, unless I root and then freeze something.
stuartv said:
Say what? Mine is prompting me to install the update. It only gives me 2 choices "Install now" and "Install later", and if I choose later, it prompts me to pick a time for it to install. There is also a checkbox that says "Install automatically", which I am leaving unchecked. So, I think it's going to prompt me every day from now on, unless I root and then freeze something.
Click to expand...
Click to collapse
It will just keep bugging you with the prompt everyday unless you root and freeze the apps.
With my wife's phone I went in to settings, application manager scrolled over to all & found SDM app & forced stopped it. Notification is now gone.
She IS NOT rooted.
I also have it auto hibernate using greenify so it does not come back.
Sent from my SCH-I545 using Tapatalk 2
So is this update buggy for those who were unrooted? Or just for those who were rooted and took the update?
I wonder if we were to unroot, take the update, then follow the root instructions if many of the problems go away?
Sent from my SCH-I545 using XDA Free mobile app
My wife's S4 is totally stock and she's had zero problems with the update. Took it earlier today.
After playing around with the update for a while, it looks like we have finally lost write access to the SD card like we were supposed to since the first Kit Kat update. I cannot write to the SD card (unrooted) with any file explorer, and my SMS backup app fails at writing to the SD card.
Zelmo88 said:
I would also advise not taking the NG6 update. I did and I went back to NC5. The random reboots seem to be unfixable and there really wasn't anything new and exciting with NG6, unless you need Knox 2.0 for some crazy reason! STAY WITH NC5!!!
Click to expand...
Click to collapse
I read your post..updated for the heck of it..FDR'd it...random rebooted after a a few minutes.
Its been 2 days so far, and the thing reboots 3-4 times a day.
I noticed that sometimes before it reboots, I'll unlock it, and it wont even register my security swipe..Then it reboots..Sometimes, if it does let me in, tapping on an icon does nothing...then it reboots...Other times, like this morning, it was just sitting on the end table, and it rebooted. Boy, you weren't kidding about the reboots.
BTW..All stock.
Here's what I did, worked.
I used the towel root method posted here (and other places I'm sure):
Ok...Forum won't let me post a link because I'm new. So Google "Root Verizon Galaxy S4 SCH-I545 on I545VRUFNG6 Firmware" and it will be the top choice from droid views.
Read the comments section too I posted the issue I was having then reinstalled super SU, flashed the NG6 Kernal and I've been good to go.
Hope it works out for you, I'm on NG6 with root, no errors, no reboots.
Q&A for Community effort to Towelroot Mega I527 / I527M
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Community effort to Towelroot Mega I527 / I527M. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I'm down, long as no damage is done.. like bricking
DBugg said:
I'm down, long as no damage is done.. like bricking
Click to expand...
Click to collapse
OP here.
It's unlikely to brick but I don't even want it to trip the Knox flag, let alone bricking!
My main focus as of now is I527M (Canadian variation). I can say that I527M uses logic board of I527, so I'm guessing it's just a matter of software issue that people are having so much trouble rooting I527 at all.
I was able to root my Mega 6.3 sgh-i527m
Hello all, I found a few articles that lead no where, Then I saw this forum talking about using Package Disabler. Download it from the google play store. Kill any process looking like Knox Icon. One will not allow it as Package Disabler will need Admin access to your phone and remove Knox Admin privileges, Disable last Knox Package. Then Boot into Download mode with Odin 3.09 on. Root your phone as normal, except for the Reboot automatically option. Uncheck that feature as you want to boot into Bootloader first. Once your into the CW custom recovery or the recovery that comes with your choice of rooting, Install latest version of SuperSU. Finish and boot back into Android. Get Root Checker to verify or Titanium Backup. I used Titanium Backup to un install everything related to Knox. No more Nagging Knox popping up and phone is rooted.
friendlyG said:
Hello all, I found a few articles that lead no where, Then I saw this forum talking about using Package Disabler. Download it from the google play store. Kill any process looking like Knox Icon. One will not allow it as Package Disabler will need Admin access to your phone and remove Knox Admin privileges, Disable last Knox Package. Then Boot into Download mode with Odin 3.09 on. Root your phone as normal, except for the Reboot automatically option. Uncheck that feature as you want to boot into Bootloader first. Once your into the CW custom recovery or the recovery that comes with your choice of rooting, Install latest version of SuperSU. Finish and boot back into Android. Get Root Checker to verify or Titanium Backup. I used Titanium Backup to un install everything related to Knox. No more Nagging Knox popping up and phone is rooted.
Click to expand...
Click to collapse
Well, rooting SGH-I527M was possible and pretty simple to be honest. What I wanted to achieve was to root it without tripping Knox.
I'm sure your Knox flag is tripped, right?
I have root!!! I527 4.4.2
Kingroot latest version 4.1.0.249 (From androidxda) successfully rooted my phone. Knox didn't get tripped until I tried to do a custom recovery on my own, which admittedly, I don't know what I'm doing. But other than that, it did disable knox and worked perfectly. I do have screenshots, but it won't let me post outside links because I have less than 10 posts.
JCSouth said:
Kingroot latest version 4.1.0.249 (From androidxda) successfully rooted my phone. Knox didn't get tripped until I tried to do a custom recovery on my own, which admittedly, I don't know what I'm doing. But other than that, it did disable knox and worked perfectly. I do have screenshots, but it won't let me post outside links because I have less than 10 posts.
Click to expand...
Click to collapse
Yes people this work finally we got root..Thanks to JCSouth he funded
JCSouth said:
Kingroot latest version 4.1.0.249 (From androidxda) successfully rooted my phone. Knox didn't get tripped until I tried to do a custom recovery on my own, which admittedly, I don't know what I'm doing. But other than that, it did disable knox and worked perfectly. I do have screenshots, but it won't let me post outside links because I have less than 10 posts.
Click to expand...
Click to collapse
I tried it on SGH-I527M unrooted Mega and it didn't work. It went to 52% rebooted and said root failed.
I confirm work on Mega sgh-i527 att
mine as well,mega 6.3 NJ1 AT&T
friendlyG said:
Hello all, I found a few articles that lead no where, Then I saw this forum talking about using Package Disabler. Download it from the google play store. Kill any process looking like Knox Icon. One will not allow it as Package Disabler will need Admin access to your phone and remove Knox Admin privileges, Disable last Knox Package. Then Boot into Download mode with Odin 3.09 on. Root your phone as normal, except for the Reboot automatically option. Uncheck that feature as you want to boot into Bootloader first. Once your into the CW custom recovery or the recovery that comes with your choice of rooting, Install latest version of SuperSU. Finish and boot back into Android. Get Root Checker to verify or Titanium Backup. I used Titanium Backup to un install everything related to Knox. No more Nagging Knox popping up and phone is rooted.
Click to expand...
Click to collapse
4 look like this?
App said no root available for my device....did you get this message as well and went ahead with root anyways?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
@txnolesfan93: You can proceed. Report back if successful.
@friendlyG: any updates?
Success...? Said root successful and titanium backup says I have it too. Sgh-i527 4.4.2 baseband nj1
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Root checker says as well
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
I get this when I restart my phone. Phone boots fine but I have no idea what it means. I uninstalled knox with titanium backup.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
This
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Yeah, unlocked. That's the same thing I got on my old Nexus S when I got fastboot. It's unlocked, but still have an issue with AT&T software. If someone can figure out how to get around that, I've been trying and spent all night trying to get my phone back to where it was, working backups and custom roms can be created.
Ok...nothing really just that I was able to get knox back in my phone and when I try and update su it says that knox has been detected when I took it off it said just that I couldn't update su....so....yeah. but unlock is still on boot. I hope we can get this thing cracked.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
As a record in the history of mankind, I've been living with this phone for months happily without rooting it, but now I can't take it anymore. It is ridiculous that I can't sync my Dropbox to the external SD card! What the hell KitKat!!! I am very close to root this baby, in an unstoppable rampage!!! Seriously, what the hell Android team! I am very close to say goodbye to Knox 0x0...
But I might wait a bit more for @Kingxteam and PingPongRoot !