Database Develop

No rooting method is working

Obviously possible but I am trying to root my buddies CAptivate and NOTHING is working. What am I missing. TRied z4, cant use because AT&T blocks 3rd arty installs, tried superone click and does nothing, tried the other one click and it sits on the little blue screen saying my phone should be rebooting but my phone just sits there ? Tried the "update.zip" method and tells me "bad E-siganture"
can someone please HELP!!!
Pc has current drivers installed and has degugging checked

1: search for esignature problems, there is a way around this. (simple)
2: use sideload wonder machine from android central to load z4root.
3:use z4root
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

What are his specs?
Sent from my SAMSUNG-SGH-I897 using XDA App

[APP]SuperOneClick v1.7 (Root, Unroot, Enable Non-Market App) - xda-developers
use the 1.7 version posted
it works use it.

pinoyplaya said:
What are his specs?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Its a captivate running 2.2 froyo . I'll try the abover methods later today after I get done with the kids bday party. Gotta have the phone back to him on Mon

doesnt matter what your specs are.
use the link i posted above .
use version 1.7

TRusselo said:
doesnt matter what your specs are.
use the link i posted above .use version 1.7
Click to expand...
Click to collapse
Thank you. I finally got this to work as far as I have the Super User app installed on the phone. I thought if I had this then the phone is def rooted yet when I try to delete ATT bloat ware it still won't let me.
Is this only because its still running the factory 2.2 froyo. Will the full SU benefits be there one I flash whatever ROM he wants on Monday ?
And what is the best rom for the cap ? I have the Eris running a GB rom that I love but I'm sure this phone is different

go to the market, download titanium backup. use that to uninstall, unwanted bloat...you cannot use the native package installer/uninstaller to remove system apps.

studacris said:
go to the market, download titanium backup. use that to uninstall, unwanted bloat...you cannot use the native package installer/uninstaller to remove system apps.
Click to expand...
Click to collapse
Tried using Astro and E Strongs both and niether worked and they are non native. I'll give TBU a try.

Tbu is the most popular app users use to remove apps. And it worked for me do I hope it can work for you
Sent from my Deodexed Captivate with Voodoo

TB did the job.
What ROM do most cap users seem to like these days that stable and quick.

stable and quick
stick with froyo based roms. especially if you have to ask
besides that,,, research research.
there is no best.

scottcwhite said:
TB did the job.
What ROM do most cap users seem to like these days that stable and quick.
Click to expand...
Click to collapse
My personal preference... Firefly.
The Gingerbread ROMs are still Beta.

ok i have to agree... firefly...

Thanks all. I don't think it's going to matter since when I reboot into recovery I do not have the option to "flash zip from sd card". I got it rooted, installed rom manager and flashed clockwork but to no avail. This all seemed to go so smoothly when I did our eris phones.
I have his "wireless tether" working and was able to delete a ton of ATT bloatware but I think he's going to stuck with the stock ATT 2.2 ota rom.

scottcwhite said:
Thanks all. I don't think it's going to matter since when I reboot into recovery I do not have the option to "flash zip from sd card". I got it rooted, installed rom manager and flashed clockwork but to no avail. This all seemed to go so smoothly when I did our eris phones.
I have his "wireless tether" working and was able to delete a ton of ATT bloatware but I think he's going to stuck with the stock ATT 2.2 ota rom.
Click to expand...
Click to collapse
As you have already been told in this thread you need to make sure you have modified your 3e recovery to allow cwm to work.
Sent from my HTC Desire Z

Check out TRusello's signature "3e recovery fix" also after you boot into recovery from rom manager you have to "reinstall packages" twice, then you will see all the options...

scottcwhite said:
Thanks all. I don't think it's going to matter since when I reboot into recovery I do not have the option to "flash zip from sd card". I got it rooted, installed rom manager and flashed clockwork but to no avail. This all seemed to go so smoothly when I did our eris phones.
I have his "wireless tether" working and was able to delete a ton of ATT bloatware but I think he's going to stuck with the stock ATT 2.2 ota rom.
Click to expand...
Click to collapse
you need to reinstall packages in recovery twice.
also you need the to fix 3e recovery before you can flash the cwm .zip.
look @ the stickies in the general section. there is a thread on working around 3e recovery. it contains a link to a batch script that'll fix it
there is also odin(tethered) that can replace the kernel with one that has cwm baked in
and sgs kernel flasher in the market that can do the same from the phone as long as it's rooted.

bit.ly is great...
3e fix in my sig 100 hits to-date (dirty version)
3e fix in the 3e thread 1 hit (cleaner version)
lol

TRusselo said:
bit.ly is great...
3e fix in my sig 100 hits to-date (dirty version)
3e fix in the 3e thread 1 hit (cleaner version)
lol
Click to expand...
Click to collapse
Lmfao. that's awesome.
The dirty version is hilarious.

Initial setup/best practices

Soon-to-be, first-time, smart phone owner here.
My new Revolution is on the way and I have a few questions for current owners, rooters and rom installers.
I want to remove bloatware and Bing, improve battery life, allow tethering, and unlock the FM radio. Should I wait for Gingerbread? Root only? Install a custom Rom?
I know that the rooting process and roms improve over time and would also appreciate some input to the most current root/rom process.
Thanks,
J.

I would root right away, downgrade if necessary. RevoIt rom is incredibly fast and has bloat removed. We don't know how long until gingerbread so not worth waiting.
Sent from my VS910 4G using Tapatalk

Sorry for double post. Best way to root is if your on VS910V6 is to downgrade (there is a tutorial on here somewhere) and use superoneclick 1.7 ragethecage. If VS910ZV4 is on your phone just use superoneclick regular root. Then you have to put on revotoolkit to put on cwm. There you can flash a new rom
Sent from my VS910 4G using Tapatalk

jackpot08 said:
Sorry for double post. Best way to root is if your on VS910V6 is to downgrade (there is a tutorial on here somewhere) and use superoneclick 1.7 ragethecage. If VS910ZV4 is on your phone just use superoneclick regular root. Then you have to put on revotoolkit to put on cwm. There you can flash a new rom
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
Where do I find instructions for S1C 1.7? I went to the "development" forum and the S1C instructions say "confirmed not working, guide removed till update is available."

jyossarian said:
Where do I find instructions for S1C 1.7? I went to the "development" forum and the S1C instructions say "confirmed not working, guide removed till update is available."
Click to expand...
Click to collapse
Just extract the files, run the program, plug phone in and select internet mode with USB debugging enabled, select the "rageagainstthecage" exploit in the right hand side drop-down menu and click ROOT.
If it hangs (gets stuck) try checking and unchecking USB Debugging while the program is running and the phone is plugged in.

Thanks for the help so far. I have successfully downgraded and rooted.
I apologize in advance because I know all of these questions have been asked before but there are sooo many guides and youtube videos and forums. Some things might apply to the Revo and some might not.
Anyway...
1. I plan on installing revolt 1.5 but first think I should backup and save a copy of the Verizon Rom to be able to go back if all hell breaks loose or they update to GB. If I backup in clockworkmod, where does the backup go on the sd card? What is the name of the file? Should I take it off the sd and or put it on a computer for safe keeping?
2. Does "rom manger" work for the revolution? I asked me for phone model but didn't have the revo listed.
3. I installed Ti backup but already have the rom backed up. Is Ti backup used solely to backup apps?
4. The install instructions for revolt 1.5 say "make sure 4g is enabled," how do I do that?
5. The instructions do not say to wipe the cache. Is that no longer a required step?
6. Is there a "file manager" for accessing the sd card?
Too many ?'s, but thanks.
J.

In the same boat, sort of.
Was wondering if the sixaxis app for connecting a playstation controller to our phone works. was gonna root my phone this weekend and if this app works with our phone maybe ill stay up a little later tomorrow to see if i can get it working lol.
Thanks for any reply
ANdy

jyossarian said:
Thanks for the help so far. I have successfully downgraded and rooted.
I apologize in advance because I know all of these questions have been asked before but there are sooo many guides and youtube videos and forums. Some things might apply to the Revo and some might not.
Anyway...
1. I plan on installing revolt 1.5 but first think I should backup and save a copy of the Verizon Rom to be able to go back if all hell breaks loose or they update to GB. If I backup in clockworkmod, where does the backup go on the sd card? What is the name of the file? Should I take it off the sd and or put it on a computer for safe keeping?
2. Does "rom manger" work for the revolution? I asked me for phone model but didn't have the revo listed.
3. I installed Ti backup but already have the rom backed up. Is Ti backup used solely to backup apps?
4. The install instructions for revolt 1.5 say "make sure 4g is enabled," how do I do that?
5. The instructions do not say to wipe the cache. Is that no longer a required step?
6. Is there a "file manager" for accessing the sd card?
Too many ?'s, but thanks.
J.
Click to expand...
Click to collapse
1. I'm pretty sure backups go to external/clockworkmod/backups
But you don't need to make backups for this since you can always flash the rooted stock ROM.
2.ROM manager does not work.
3.titanium backs up only apps and there data (I like mybackup pro more)
4. If you didn't change any settings 4g you'll be fine.
5. Always wipe cache and dalvik cache. May take time to boot up but its.normal .
6. Es file explorer or root explorer
Sent from my VS910 4G using Tapatalk

Need a little help...

I went and rooted my droid 4, and without knowing about safestrap, i started backing up and deleting apps with the free version of Titanium Backup. I now have a couple of apps that will not restore back into place, and i am unable to perform the upgrade. Since then, i have installed safestrap, and attempted to flash the rom at http://forum.xda-developers.com/showthread.php?t=1508341, but all i do is bootloop on my safe system. Any idea what i can do to fix the unsafe side so i can apply the 219 update? Am i kinda out of luck until the fastboot files are released?

try asking here
http://forum.xda-developers.com/forumdisplay.php?f=565
this forum is nearly dead, like 5 people a day visit here, very few people have a droid 4
i wish i could help more, but im not very good at this, but there are more people there that could help

What I'd do is download the stock recovery files that Hashcode has put up, and make sure you have anything you want backed up, and try advanced restore and flash all 3 options. As for the boot loop, did you try to clear cache and dalvik cache?

Are you referring to the [SAFESTRAP ROM] Stock MotoBlur 6.13.215 for Droid 4 at droidforums (forum won't let me post link) for hashcode's stock recovery? Or do you mean simply uninstalling the safestrap recovery from the safestrap app? I haven't played much with the stock recovery, so i'm not sure what 3 options you are referring to.
As far as the safe side, i wiped cache, wiped dalvik cache in the advanced menu, and done a factory reset... still bootloops...

Gengar1603 said:
Are you referring to the [SAFESTRAP ROM] Stock MotoBlur 6.13.215 for Droid 4 at droidforums (forum won't let me post link) for hashcode's stock recovery? Or do you mean simply uninstalling the safestrap recovery from the safestrap app? I haven't played much with the stock recovery, so i'm not sure what 3 options you are referring to.
As far as the safe side, i wiped cache, wiped dalvik cache in the advanced menu, and done a factory reset... still bootloops...
Click to expand...
Click to collapse
I am having the same issue. I was recommended to unzip the stock rom posted and attempt either a direct or adb push install of those apk's that are missing. Someone did this one by one and was successful in installing the 219 update.
You could attempt to install the stock rom through safestrap to get the update. please make sure that you are at full 100% charge as most roms wont flash correctly with less. I recommend getting full charge and flashing while still plugged in.

Hey guys, so what exactly is going on? You are missing apks on your main system, and your safe system bootloops?
So, your primary system functions, it just is missing bloatware, preventing you from updating? I just want to be sure I understand before making a recommendation.

Welp, i got some good news, i got the main system fixed and then updated. I took a stock 215 rom, extracted the /system/app folder and the system/build.prop to the sd card. Then i simply copied the contents of that folder into the /system/app on the root of the system with a file manager (used estrong's, other file managers that support root should work.), copied the build.prop to /system, and then did the update OTA. I lost safestrap and root, but i was able to reroot with moto fail... i have not tried reinstalling safestrap yet, nor have i mess with the bloatware like i did last time.

Gengar1603 said:
Welp, i got some good news, i got the main system fixed and then updated. I took a stock 215 rom, extracted the /system/app folder and the system/build.prop to the sd card. Then i simply copied the contents of that folder into the /system/app on the root of the system with a file manager (used estrong's, other file managers that support root should work.), copied the build.prop to /system, and then did the update OTA. I lost safestrap and root, but i was able to reroot with moto fail... i have not tried reinstalling safestrap yet, nor have i mess with the bloatware like i did last time.
Click to expand...
Click to collapse
I sort of did the same thing. I downloaded the rooted stock from and unzipped it. I then rebooted and manually tried to install the update and noted what files needed to be restored and then I coped them to dropbox then moved them to /system/app and it worked

I attempted to move the files but got an error when doing so saying I could not move them to the folder. The only file I seem to be getting the error with is backupassistantclient.apk but that might be because it is getting to that first and erroring out. Does Astro not support root to ove the files in /system, etc?
Sent from my DROID4 using XDA

azrael293 said:
I attempted to move the files but got an error when doing so saying I could not move them to the folder. The only file I seem to be getting the error with is backupassistantclient.apk but that might be because it is getting to that first and erroring out. Does Astro not support root to ove the files in /system, etc?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
Why don't you just flash it back to stock instead of messing it up more. I got a thread up here on our to do that.
I was playing once like that with the Nook Tablet. It took me 3 weeks to fix it. I hope you don't fall under the same crap with your phone

mrbidjey said:
Why don't you just flash it back to stock instead of messing it up more. I got a thread up here on our to do that.
I was playing once like that with the Nook Tablet. It took me 3 weeks to fix it. I hope you don't fall under the same crap with your phone
Click to expand...
Click to collapse
I will try to flash the stock Rom via safestrap and update. Thanks mrbidjey
Sent from my DROID4 using XDA

azrael293 said:
I will try to flash the stock Rom via safestrap and update. Thanks mrbidjey
Click to expand...
Click to collapse
I think he was referring to the fastboot files that just leaked a few days ago. Check out this thread

SGMD1 said:
I think he was referring to the fastboot files that just leaked a few days ago. Check out this thread
Click to expand...
Click to collapse
I actually read that thread right after replying on here. ill definitely go that route. thanks everyone
Sent from my DROID4 using XDA

[HOW TO]Update from stock rooted MF9/MJA/MK2 to NAE (with root) without losing data

Updated for NAE. When the NAE tar.md5 comes out you can just flash it directly rather than doing all this.
This will update everything (firmware, modem, bootloader, ROM, recovery, etc) to NAE. As long as you're coming from stock or mostly stock, this should work, and you will still have all your data and apps. It will also probably work coming from another MF9, MJA, or MK2 based ROM, but you may have problems (in which case you can just wipe data. The whole process should take less than 30 minutes, not counting the time it takes to download the stock tar.md5 image. I recommend starting it now (link in Step 2) so it will be ready when you need it. This will NOT work if you've already tried to take the NAE OTA and it failed because you weren't fully stock.
You will need odin. It can be downloaded from this thread. Alternatively, if you're using OS X or Linux, I found that Heimdall works very well in place of odin. There are a few extra steps involved though, but if you install Heimdall Frontend then you don't have to mess with the terminal.
Step 1: Backup your current ROM with TWRP, CWM, or Philz.
Step 2: Download the MK2 tar.md5 from sammobile. Sammobile is pretty slow to download, but I found a mirror and a second mirror. I also made a torrent that might be faster (please seed if you use it to speed it up for everyone). Flashing this with odin does NOT wipe data. You can verify it by opening it in an a program that supports tar and looking at the files within it; those are the partitions it overwrites. This will give you stock MK2 recovery, bootloader, modem, firmware, and software.
Step 3: Use odin to flash it over your current ROM. To do this, you need to first put the phone into download mode. Power it off completely, then press and hold volume down, home, and power. Then connect it to your computer.
In odin, I just left default odin settings checked. Make sure that you add the tar.md5 in the PDA slot and apply it. Reboot and verify that your data is all there. You can still easily revert to the backup you made in Step 1 if things aren't right.
Step 4: Put the MK2 to NAE OTA on your external sd card (not internal). You don't need to rename it.
Power the phone off completely. Then press and hold home, volume up, and power to get into stock recovery. Navigate to where you put the OTA zip on your external sd card and flash it. It will reboot a couple times during the update, including one time where it seems like it's booted up and done before it powers off again. You'll know it's done when you get a popup notification saying it completed successfully. All your data and apps should still be there.
Note: From this point on, performing any of these steps will set the Knox flag. So if you just purchased the phone (within your return window) or are having issues and may need a replacement, you may want hold off on root. Sprint may or may not check for this during a warranty replacement. Insurance replacements should be fine.
Step 5: Go back into download mode and flash CF Auto Root through odin. You should now have root, and knox will not complain. You'll need to re-download the SuperSU app from the Play Store though. Open the app and let it update the su binary to the newest version.
Step 6: Flash TWRP (or CWM or Philz) through odin (it didn't work for me with goo manager). Optionally reboot into recovery to make sure it actually stuck.

Ingenium13 said:
As long as you're coming from stock or mostly stock, this should work, and you will still have all your data and apps. It will also probably work coming from another MF9 based ROM, but you may have problems (in which case you can just wipe data. See note at the end if you're using Titanium Backup). The whole process should take less than 30 minutes. It will NOT work if you've already tried to take the MJA OTA and it failed.
Step 1: Backup your current ROM with TWRP, CWM, or another recovery.
Step 2: Download the MF9 tar.md5 from sammobile (here is a fast mirror: http://goo.gl/gky86G, sourced from here). This one does NOT wipe data. You can verify it by opening it in an a program that supports tar and looking at the files within it; those are the partitions it overwrites.
Step 3: Use odin to flash it over your current MF9 ROM. Reboot and verify that your data is all there. You can still easily revert to the backup you made in Step 1 if things aren't right.
Step 4: Put the OTA on your external sd card (not internal). Power the phone off completely. Then press and hold home, volume up, and power to get into stock recovery. Navigate to where you put the OTA zip on your external sd card and flash it. It will reboot a couple times during the update, including one time where it seems like it's booted up and done before it powers off again. You'll know it's done when you get a popup notification saying it completed successfully. All your data and apps should still be there.
Step 5: Go back into download mode and flash CF Auto Root through odin. You should now have root, and knox will not complain. You'll need to re-download the SuperSU app from the Play Store though. Open the app and let it update the su binary to the newest version.
Step 6: Flash TWRP (or CWM) through odin (it didn't work for me with goo manager). Optionally reboot into recovery to make sure it actually stuck.
It seems that with all the issues with the new firmware, that it's actually worth the trouble to do it the "official" way to make sure it works, especially since it's trivial to get root back. Follow these steps and you should be fine.
NOTE: For those who want to wipe data anyway (or have to because they're having problems), Titanium Backup is currently not working properly with MJA. The workaround is to manually install your apps from the Play Store and then restore just the data from Titanium Backup. Restoring the apps themselves through Titanium Backup causes problems at the moment.
Click to expand...
Click to collapse
You WILL Knox Warranty Void with this method.

Is there a workaround for tripping Knox?

Not yet. A method will probably be developed, but it will involve flashing a custom kernel that doesn't require the new bootloader. The version of MJA would have to have this kernel included. The stock kernel seems to not boot without the new bootloader. You will have to keep using a custom kernel from that point onward.

Ingenium13 said:
Not yet. A method will probably be developed, but it will involve flashing a custom kernel that doesn't require the new bootloader. The version of MJA would have to have this kernel included. The stock kernel seems to not boot without the new bootloader. You will have to keep using a custom kernel from that point onward.
Click to expand...
Click to collapse
Sorry, where do I find the OTA MJA update?

For those of us new to Odin, can we get a screenshot of what should and shouldn't be checked?
Edit: Nothing NEEDS to be checked.
Checking Auto Reboot does just that, but doesn't seem to work for me.
Checking R.Flash Time resets a counter, not a big deal, either.
The rest uncheck.
Anyways, that all worked. I tried combining the Odin'ing of CF Root and recovery, until I saw that the CF-Auto-Root restores the old recovery as one of the steps...

with this method do we get the mja modem?
if the option available to go back to aosp 4.3 if we dont like it? 4.2 tw?

aberchonbie said:
Sorry, where do I find the OTA MJA update?
Click to expand...
Click to collapse
To be more specific, where is the OTA downloaded to?
I would like help with the file location also. Thanks.
FOUND IT in the Cache folder. You must allow root permissions in your file explorer.

Can I follow these steps if I have TWRP instead of stock recovery?
Also, what update for to apply?

After reading in this forum, non stop since Oct. 28, I took the plunge and did the dirty deed late last night with the downloadable OTA, after restoring to stock.
I woke up this morning and the Keebler elves hooked me up. I was fully rooted and all I had to do was reinstall Clockwork.
Mobile ODIN and SuperUser's Keep root are what's happening.
I have been looking for any glitches this morning but this thing runs perfect. I did see a security warning once that I assume is the Knox thingy I read so much about. Other than that, I'm gravy.
Now, can someone remind me why I upgraded?
I mean, what did I gain by leaping to 4.3? Is there something under the hood I ain't seeing?

Bonefishbf3 said:
To be more specific, where is the OTA downloaded to?
I would like help with the file location also. Thanks.
FOUND IT in the Cache folder. You must allow root permissions in your file explorer.
Click to expand...
Click to collapse
Here's a link to the update zip directly from Google's servers: http://android.clients.google.com/p...CSB_user_RP_to_MJA_CSB_user_RP_Update_FWD.zip
You don't have to rename it, just put it on your external SD card and navigate to it in the stock recovery.
M3wThr33 said:
For those of us new to Odin, can we get a screenshot of what should and shouldn't be checked?
Edit: Nothing NEEDS to be checked.
Checking Auto Reboot does just that, but doesn't seem to work for me.
Checking R.Flash Time resets a counter, not a big deal, either.
The rest uncheck.
Anyways, that all worked. I tried combining the Odin'ing of CF Root and recovery, until I saw that the CF-Auto-Root restores the old recovery as one of the steps...
Click to expand...
Click to collapse
Just leave the default checked, and it will be fine. The only one that really matters is that re-partion is NOT checked.
Memphisjojo said:
with this method do we get the mja modem?
if the option available to go back to aosp 4.3 if we dont like it? 4.2 tw?
Click to expand...
Click to collapse
Yes, you get the MJA modem as well. I believe AOSP 4.3 works fine with the new modem and bootloader, but I haven't tried it.
Bielinsk said:
Can I follow these steps if I have TWRP instead of stock recovery?
Also, what update for to apply?
Click to expand...
Click to collapse
The OTA won't apply with TWRP. Follow the steps and you'll get the stock recovery back when you odin to stock MF9. You can then update to TWRP after re-rooting.

Just did the update only issue im having is No WiFi??Any solutions?? Thanks

rob97ss said:
Just did the update only issue im having is No WiFi??Any solutions?? Thanks
Click to expand...
Click to collapse
Did you try updating to MJA before this?
Sent from my SPH-L720 using Tapatalk

Ingenium13 said:
Did you try updating to MJA before this?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
No.Any ideas??
Sent from my SPH-L720 using XDA Premium 4 mobile app

rob97ss said:
No.Any ideas??
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Were you coming from stock rooted MF9? Losing wifi is a common problem with anyone who didn't fully take the OTA.
There is a wifi fix in this thread that supposedly will cleanly apply to the stock kernel as well as the custom kernel listed, but I haven't tried it http://forum.xda-developers.com/showpost.php?p=47030804&postcount=1638
Sent from my SPH-L720 using Tapatalk

Ingenium13 said:
Were you coming from stock rooted MF9? Losing wifi is a common problem with anyone who didn't fully take the OTA.
There is a wifi fix in this thread that supposedly will cleanly apply to the stock kernel as well as the custom kernel listed, but I haven't tried it http://forum.xda-developers.com/showpost.php?p=47030804&postcount=1638
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Thanks buddy.. WiFi fixed..Stock kernel...
Sent from my SPH-L720 using XDA Premium 4 mobile app

Ingenium13 said:
Step 2: Download the MF9 tar.md5 from sammobile (here is a fast mirror: http://goo.gl/gky86G, sourced from here). This one does NOT wipe data. You can verify it by opening it in an a program that supports tar and looking at the files within it; those are the partitions it overwrites. This will give you stock MF9 recovery, bootloader, modem, firmware, and software.
Click to expand...
Click to collapse
I had to install this ROM twice via Odin3 to get stock recovery back.

This seems to be the only side affect of flashing to 4.3. I guess it's a Knox thing.
Is there a fix for this?
Sent from my SPH-L720 using XDA Premium 4 mobile app

SpringerRider said:
This seems to be the only side affect of flashing to 4.3. I guess it's a Knox thing.
Is there a fix for this?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You could freeze the Knox apps (filter for them in titanium backup). I had no issues with knox until yesterday when I got a notification in the drawer when I used su (but su worked fine when this happened). I just froze all the apps with knox in the name and it's been fine since.
Also, there's a check box somewhere in the Android settings to tell it not to update the Knox list. I unchecked that as well.
Sent from my SPH-L720 using Tapatalk

stuck on yellow Sprint Boot Screen after step 3
Help......after running step 3 and using odin I am stuck on the yellow sprint boot screen.
Any Ideas on what to do from here?

Att NC2 need help going back to factory ASAP

Hello I searched and couldn't find an answer basically I rooted my note 3 with root towel and safe strap unfortunately i didn't back up or back anything up was kinda drunk lol so at this point I can't seem to flash anything I see the galaxy note 3 on the booting then the safe strap shows up and it is giving me two options recovery or continue ... If I hit continue nothing happens ...black screen now if I hit recovery I'll be in safe strap recovery but can't see to flash any NC2 rom anyway at ths point I rather like to go back to stock ncu and start over any help will be greatly appreciated!!

Hello no one here can help? Please!!!

I am having the almost same problem a you, with the exception that I can still use my phone right now. But I can't install any other rom or even use my backup that I made in recovery. They just keep failing. I can give you a copy of my backup that I made maybe that will help you. Just pm me if you want it OK.
Sent from my Rooted AT&T N900A Samsung Galaxy Note 3 Using XDA Premium HD app

I ran into a similar issue. I messed up and learned the hard way to make sure and run a backup before messing with my phone. In my case, I make sure to run Nandriod backup and make a full backup to my external sdcard.
As a suggestion, you can always restore to MLG using the n900aucumlg one click (by designgears) 4.4.2: http://forum.xda-developers.com/showthread.php?t=2619941
You can then simply update the modem using this thread: http://forum.xda-developers.com/showthread.php?t=2698464

Did you install busybox. The order to do all that was 1. Towelroot. 2. Install busybox. 3. Install safestrap. If nothing is happening I would suggest to boot into stock recovery via power, home, volume up (or down I forget which one it is) and just factory reset like that. It should erase everything and start you fresh
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

FYI, I would also check out the source from where you are loading your ROMs. Since I swapped over to a different SD card, my installation problems have been cleared up.