I have rooted my note 3 N900A with towelroot and installed safestrap v3.75 .
Everything seems to have installed correctly, when I check to see if I have root with root checker pro, it says I have root and that I have busybox installed as well.
When I go into safestraps/recovery and do a backup of my stock slot. Everything works for the backup. But then when I try to install a rom in any one of the slots it goes through the whole process just fine until the very end when it says in red fail.
It does the fail with every rom that I try to install. And if I try to do a restore in any slot with the backup that I made in the recovery it will fail as well.
So this just leaves me with having to use the stock slot with the original stock phone software.
Also when I try to install titanium backup on my phone that is saying it's rooted, The app won't work because it says that I don't have root. There was another app that would not work when I tried to instead it too because life the same reason. It said that I don't have root as well.
After trying to look for a solution to this, I found that there is an app that I could try to fix what has happened, called
SELinux Mode Changer
After I installed that app and tried to use it. The app made it look like it was working but really it was not doing anything. When I went into the phone info in settings, it still said that selinux was still enforcing.
Does anyone know if there is a solution to this? I would really like to be able to install a new rom on one of the other slots, heck ide settle for being able to put my stock backup on one of the other slots besides the stock slot.
Sent from my Rooted AT&T N900A Samsung Galaxy Note 3 Using XDA Premium HD app
I ran into a similar situation.. After wiping everything and then manually updating my stock to Kit Kat (MLG) I was then able to load custom roms in available slots. I used safestrap version 3.72 along with busy box. Also be sure to format the slot and wipe the cache and dalvik after installation.
The only ROM I am unable to install is Dynamic Kat xtreme. After loading that guy, the flash just fails.
UPDATE: I for unknown reasons to me, was able to successfully install one of my restore files to slot 1. Then after it reboots the phone acts as if it is restarting correctly, but ason as it gets past the safestrap logo with recovery/startup. It goes right into the phones recovery, and it keeps saying that it is installing "multiple csc or something.
Can someone help me with this?
Sent from my Rooted AT&T N900A Samsung Galaxy Note 3 Using XDA Premium HD app
After hitting rock bottom with many of the roms, I finally checked out my external sdcard and realized that it was having issues. After using a different card, I was then able to install all roms for testing.
I had to downgrade safe strap to 3.72 for it to work on my device.
Sent from my SM-N900A using XDA Free mobile app with Dynamic Kat 4.2 the kat is awesome.
For some strange reason everything stayed to work and I have no idea how..but I now have another problem the aliancerom that i installed on slot 1 works fine with the exception that the aliancerom that i installed won't let the wifi work. After i put in the info for the at&t 3g, The phone's 3g worked but the home wifi won't. Any ideas?
Sent from my Rooted AT&T N900A Samsung Galaxy Note 3 Using XDA Premium HD app
marknderm said:
For some strange reason everything stayed to work and I have no idea how..but I now have another problem the aliancerom that i installed on slot 1 works fine with the exception that the aliancerom that i installed won't let the wifi work. After i put in the info for the at&t 3g, The phone's 3g worked but the home wifi won't. Any ideas?
Sent from my Rooted AT&T N900A Samsung Galaxy Note 3 Using XDA Premium HD app
Click to expand...
Click to collapse
if it is the kk version it needs to be installed in the stock slot other slots do not work with kk yet
Related
FYI I installed the newest busybox and it broke wifi as well as cell reception. Won't recognize the sim. I found this post below as well... going to have to odin when I get home. i have the i957
- - - - -
just for the docs:If you installed Busybox on a rooted OneX with stock ROM, and removed some symlinks in /system/bin, make shure to keep /system/bin/insmod and /system/bin/chmod untouched or link it with /system/xbin/busybox (or wherever you installed busybox to).*If you don't, you phone will not prompt for the SIM PIN and will not show any network operator or signal.If the phone starts, the file /system/bin/poweron_modem_fls.sh gets executed. This file will call a binary named IMCdownload which has /system/bin/insmod hardcoded. If this insmod is nonexistent the IMCdownload will fail and /dev/ttyACM0 (the GSM modem terminal) does't get created.Next, gsm0710mux is called. This tool talks to /dev/ttyACM0. It tries to run /system/bin/chmod (even hardcoded). If this fails, the phone will not prompt for the SIM PIN even.It took me two days and a nearly bricked OneX to figure this out.Maybe its helpful so someone
Sent from my SAMSUNG-SGH-I727 using xda premium
Mine is broken also.
Hey guys, This isn't a problem with Busybox, It was a bug in my application.
The bug was present in version 8.0 I pathced the bug as fast as possible in 8.1 but a lot of people still got it because of caching issues.
What happened was that it symlinked all applets to busybox which means it overwrote some system applets that on some devices shouldnt be overwritten. I didn't catch this bug because my device was not affected by this.
To resolve this issue, simply reflash your current rom. You do not have to wipe any data.
When you reboot this should resolve the problem.
Again I want to apologize for this problem and annoyance.
Best Regards,
Stephen - Stericson
Thanks for the response!
Sent from my SAMSUNG-SGH-I727 using xda premium
Your welcome, did you get it fixed?
I really hate that this happened so I am trying my best to help everyone get back up and running. Hopefully too many people won't hate me after this goof.
Stericson said:
Your welcome, did you get it fixed?
I really hate that this happened so I am trying my best to help everyone get back up and running. Hopefully too many people won't hate me after this goof.
Click to expand...
Click to collapse
Yea works just fine, just odin flashed a new rom. I've been in much worse situations, just hope the people who don't know as much are ok.
Sent from my SAMSUNG-SGH-I727 using xda premium
A lot of them have been emailing me and so far I have had success getting them all back on track.
and I've made found two threads on XDA about it and have posted there, so I'm trying to make sure all is right in the world
Stericson said:
A lot of them have been emailing me and so far I have had success getting them all back on track.
and I've made found two threads on XDA about it and have posted there, so I'm trying to make sure all is right in the world
Click to expand...
Click to collapse
It's great you are doing that as a dev.
Sent from my SAMSUNG-SGH-I957 using xda premium
I'm using the stock rom of Galaxy Tab 7.7, the latest version of Busybox break wifi, and I can't access Google Play, Gmail, I can't install or uninstall from within busybox, and the terminal emulator won't work neither. So i can't install new version, can't access to command line, can't get rid of the installed version.
The rom refreshing is troublesome, since I'm using the stock rom and stock recovery. Is there any simple fix for this situation???
scubajeff said:
I'm using the stock rom of Galaxy Tab 7.7, the latest version of Busybox break wifi, and I can't access Google Play, Gmail, I can't install or uninstall from within busybox, and the terminal emulator won't work neither. So i can't install new version, can't access to command line, can't get rid of the installed version.
The rom refreshing is troublesome, since I'm using the stock rom and stock recovery. Is there any simple fix for this situation???
Click to expand...
Click to collapse
I suppose you could find someone to adb pull the missing files and then push them manually?
Sent from my SAMSUNG-SGH-I727 using xda premium
orlandoxpolice said:
I suppose you could find someone to adb pull the missing files and then push them manually?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Galaxy Tab 7.7 is not a popular device. Besides, I really don't know which file busybox touched.
Reflashing took ten minutes and all my apps are fine. Didn't have to do a seperate root like last time so that was nice. Aslo the bloatware was removed.
Odin for I957 only:
http://forum.xda-developers.com/showthread.php?t=1658243
WiFi But No Mobile Network
I installed Busybox 1.20.1 and my WiFi still works fine but I have no mobile 3g network. I can call and text message fine also. Google Play and any other application requiring internet access only work while WiFi is enabled. Busybox 1.20.0 worked fine. I have a Casio Commando with a stock rom. I have tried uninstalling busybox but it fails every time, telling me the system will bootloop. I have tried unrooting with no luck also. What are my options to fix this?
What version of my app did you use to install Busybox? 8.0? Curiously if you were hit by the 8.0 bug you lost both.
The easiest way is just to reflash a stock rom. You should not have to wipe or lose any data.
Version 8.3
I've also read that the Casio Commando cannot be reflashed.
Did you change any of the smart install settings? If not, I'm a little unsure if the cause was Busybox.
The previous bug was caused by overwriting system applets that shouldnt be overwritten, that was fixed as of 8.1. so the only way it could overwrite something it shouldnt would be if you adjusted the pre-adjusted settings in smart install.
Have you tried a reboot to see if the issue persists after that? Or maybe a reinstall of Busybox? Maybe you got an incomplete install somehow?
Yeah, I tried all of that. I didn't change any settings either. It won't even let me use smart install anyway. I just used the regular install option. I waited for smart install to finish loading then installed 1.20.1 over 1.20.0 and then I had no mobile network. The 3g icon and bars show up and they're white but they're supposed to turn green. Mobile network settings look good too.
Maybe it's an issue with 1.20.1, Can you try rolling back to 1.20.0?
Yeah, I already installed 1.19.4, 1.19.3, and 1.20.0 after I installed 1.20.1. Right now it says BusyBox v1.19.3 is installed to /system/bin/
Can you run the command:
ls -l /system/bin
and show us the output?
Hey guys. I got my grouper yesterday, I'm hoping for a warm welcome
The first thing I did when I took it out of the box was fire it up, unlocked and rooted. When I rooted, I flashed SuperSU flashable. I also flashed CWM touch. After that I flashed SmoothROM 4.4, and I was solid. I installed all of my usual apps, then went to do what I call debloating, (Looking for apps I don't use such as voicedialer.apk, and deleting them) using root browser (/system/app). I noticed it wouldn't delete, then tried another app that requires root permissions. Nothing. I got suspicious, then re-downloaded root checker. "Sorry! You're device does not have proper root access!" What happened? Is this just me, or is this a widespread problem with this ROM? I'd like to keep this ROM if possible. Is there a way to re-root my device (more or less)? Thanks, a response or any help would be very much appreciated.
Sent from my Nexus 7 using xda premium
Rom specific questions need to be posted in that rom's thread. Do not start new threads about custom rom issues.
LiquidPlatinum said:
Hey guys. I got my grouper yesterday, I'm hoping for a warm welcome
The first thing I did when I took it out of the box was fire it up, unlocked and rooted. When I rooted, I flashed SuperSU flashable. I also flashed CWM touch. After that I flashed SmoothROM 4.4, and I was solid. I installed all of my usual apps, then went to do what I call debloating, (Looking for apps I don't use such as voicedialer.apk, and deleting them) using root browser (/system/app). I noticed it wouldn't delete, then tried another app that requires root permissions. Nothing. I got suspicious, then re-downloaded root checker. "Sorry! You're device does not have proper root access!" What happened? Is this just me, or is this a widespread problem with this ROM? I'd like to keep this ROM if possible. Is there a way to re-root my device (more or less)? Thanks, a response or any help would be very much appreciated.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I am having same issue
This issue has been addressed; do a Verizon Nexus Forum search.
Uninstall supersu, reboot, then install the market version, not the flash able zip
Sent from my Nexus 7 using xda premium
That fixed my issue
Sent from my HTC Raider X710e using xda app-developers app
So I got Android Pay today and it looks like it will not work on a stock TOUCHWIZ ROM. Had anyone had any luck using it?
After taking a quick look at what it is needs to verify your phone I'm not sure if we'll ever work on a rooted device.
Sent from my SM-N910T using XDA Free mobile app
More info:
https://plus.google.com/+ArtemRussakovskii/posts/DEz1qUnscZF
Looks like some rerooting has worked, no luck on the Note 4 yet though.
Sent from my SM-N910T using XDA Free mobile app
Anybody get this working? I disabled root in SU and cleared data to no avail.
livejamie said:
Anybody get this working? I disabled root in SU and cleared data to no avail.
Click to expand...
Click to collapse
I've had no luck
I tried:
1.) rootcloak - fail after card setup
2.) no device check - failed before card setup
3.) disabling su - failed after card setup
Still no luck
Sent from my SM-N910T using XDA Free mobile app
I got it working, but am not rooted, using stock 5.1.1 on the T3 version. Used it at McDonald's today to get a drink. Works very well!
Sent from my SM-N910T3 using XDA Premium HD app
It works fine for me and i'm rooted. I just disabled SU within SuperSU and it let me set up my cards, and works like a charm.
Cuppeerr said:
It works fine for me and i'm rooted. I just disabled SU within SuperSU and it let me set up my cards, and works like a charm.
Click to expand...
Click to collapse
What ROM are you using?
Sent from my SM-N910T using XDA Free mobile app
ShrekOpher said:
What ROM are you using?
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Stock rom, N910T3
Running unofficial CM 12.1 and no dice, Work at Wholefoods and I have been using Wallet for a while now. Pretty annoyed that I can't even downgrade my google services and get the older Wallet NFC app and why did they decide to split it into 2 apps instead of just one?
Meh....
For the Note 4 (N910T), I had Tekxodus Rom URv5. Wouldn't work. Even tried disabling SU, Changing DPI, RootCloak, etc NO LUCK! However, i decided to get the stock rooted/debloated/deodexed rom - N910TUVU1COG2.
1. Backed up my current rom using TB.
2. Flash N910TUVU1COG2 rom (https://www.androidfilehost.com/?fid=24052804347790828)
3. At first boot and setup, immediately disabled SU, and setup Lock Pin.
4. Installed Google Play Services 8.1.14_(2244331-238)-8114238-minAPI21.
5. Installed Android Pay 1.0.103131485
6. Open Android Pay and verified card.
7. Re-Enabled SU.
8. Restore Apps using TB.
Hope this helps.
The old wallet app works better and supports more cards
REAL bad experience with No Device Check (Xposed) on rooted N7100 Note 2, stock rom, 4.4.2.
Installed it, rebooted and immediately I noticed that all of my apps that require root had disappeared from not only the main screen but from the app drawer.
Thought that I would freeze it but Ti Backup wasn't there.
Went into App Manager and tried to uninstall but it would not uninstall.
Wanted to restart into recovery mode but the options were missing... just the option to restart which did not work. The phone would not restart.
Did a full shut down and restarted into recovery the conventional way and luckily got into TWRP and did a recovery. Thankfully I did a backup last night.
Before doing a recovery, I worked on the phone from a 99% charge down to 11%, so I spent some time with it.
One funny thing though, while going through all of this, I got an update to Android Pay and my camera app.
Right after that update, I opened AP and it wanted the code on the back of the card so I tapped the field and the keyboard didn't come up and that's when I decided to do the recovery from TWRP.
BTW, over the last few days I tried all of the above suggestions and none have worked but haven't tried them again after the update to Android Pay. I think that for the time being I'll just play it safe and whip out the plastic.
so basically you can't use a customized rom
krypticsoul said:
For the Note 4 (N910T), I had Tekxodus Rom URv5. Wouldn't work. Even tried disabling SU, Changing DPI, RootCloak, etc NO LUCK! However, i decided to get the stock rooted/debloated/deodexed rom - N910TUVU1COG2.
1. Backed up my current rom using TB.
2. Flash N910TUVU1COG2 rom (https://www.androidfilehost.com/?fid=24052804347790828)
3. At first boot and setup, immediately disabled SU, and setup Lock Pin.
4. Installed Google Play Services 8.1.14_(2244331-238)-8114238-minAPI21.
5. Installed Android Pay 1.0.103131485
6. Open Android Pay and verified card.
7. Re-Enabled SU.
8. Restore Apps using TB.
Hope this helps.
Click to expand...
Click to collapse
does your androidpay still work? wondering if it's worth trying. Or did you system force an upgrade of google play services?
wpcprez said:
does your androidpay still work? wondering if it's worth trying. Or did you system force an upgrade of google play services?
Click to expand...
Click to collapse
Android pay is working. However I believe that may change with the next update of the Android pay app. Most likely not until the new year.
Hello everyone... I just bought at&t note 3 unlocked version. Problem is that its on kitkat 4.4.2 and doesnt show any ota update so can anyone please provide me a link of stock rooted at&t lollipop rom which i can flash and root method with a proper guide please? I would be very thankful.
What you do is root what you have, install Towelroot https://www.androidfilehost.com/?fid=23991606952593961 (open the app and click "make it rain" and it's rooted). Install Supersu and Busybox, then Safestrap https://www.androidfilehost.com/?fid=23991606952593962, open it and install it and this is rooted lollipop http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2. Just one thing, (not saying you will) but flash the OC1 Kernel in Safestrap before you leave Safestrap. " 5. Flash the file called "SM-N900A_OC1_Kernel_Safestrap_Installer.zip" which is located under /sdcard/OC1_Kernel/ "
Hey Rooted, i have a 1.39gb file on my ext sd card called SM-N900A_0C1_Lollipop_Rooted_rom.zip, is it safe to delete this if i already have rooted oc1? or do i need it to flash safestrap? Also, for the past few weeks my oc1 rooted note 3 has been randomly rebooting itself in the middle of me using it, then entering a bootloop until it successfully boots up. Then sometimes when it successfully boots up, it reboots itself right when i put my password into the lockscreen. Sometimes clearing the cache doesnt help, i clear it multiple times for it to work. The other day i clicked the end button on a phone call, and right when i ended the call it rebooted itself. im lucky it didnt reboot during the call, i was on the phone with a towing company lol! Any idea whats going on?
If it's rooted, yea you can delete the file then. Do you have Xposed install, flash anything else with Safestrap, did you do a clean install of the Rom? When did the rebooting start, after you installed an app?
I do not have xposed framework installed, i heard its not compatible with the oc1 root. I never flashed any custom rom, im running just a stock rooted rom. Im not sure exactly when the rebooting started, its been going on for 2-3 weeks, i cant remember what i did before that. Last night i swapped sd cards to make sure it wasnt that, but i already had 1 random restart today. Do you think swapping sim cards is a good idea?
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Just looked now. For one example, SuperSU acknowledges AdAway, but when I try to fire up AdAway, it won't work, saying it doesn't have access.
Did you install twrp and did it ask after you booted to twrp if you wanted to root the device.. if so this was a no no.. your already rooted twrp just get a little confused with the new kernels... you must remove root and reinstall supersu and when it ask when you load twrp do not root but reboot do not swipe... unless there is an easier way this worked for me...
I had the same or a similar problem. I didn't lose root completely but at times various apps were unable to gain root (after previously getting it successfully). The phone would freeze while Titanium or Root Explorer for example were waiting fruitlessly for root to be granted. It was haphazard. One time the app would work and next time it wouldn't, or another wouldn't.
Finally it got so frustrating that I installed my favorite rom on it (Tekhd). Now all is stable. I was hoping to keep it stock rooted until mm came out but I couldn't figure out what was going on so I blew it away. I had twrp on it too and would always be prompted "root not detected" but if I allowed it to install SuperSu it would loop.
Sent from my SM-N910T3 using XDA-Developers mobile app
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Eric618 said:
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Click to expand...
Click to collapse
you need to odin the firmware for your phone and then restart fresh
without root twrp won't install rom you will get error..
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Eric618 said:
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Click to expand...
Click to collapse
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Thanks! I'll give that a try when I get home today.
S5Sickness said:
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Click to expand...
Click to collapse
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Eric618 said:
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Click to expand...
Click to collapse
Your Welcome...
Eric618 said:
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Click to expand...
Click to collapse
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
marseillesw said:
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
I had tried that. It was very sluggish, and would frequently drop root access altogether. Since following S5Sickness's advice it's been solid, however.
https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app