Hey, everyone, I didn't see any specific posts on this topic, combined. My new GS4 had two problems.
1) I didn't switch the su binary to SuperSU before swapping back to the stock kernel, and I got the unlocked padlock at boot with "System Status Custom" in the Download screen
2) GPS never worked
I tried going back to the stock kernel, properly rooting, etc., but could not get my phone, no matter how many reboots, to go back to "normal" and not recognizing a custom binary. This was finally resolved by a factory reset through the Accounts menu in settings. The first reboot after the full wipe the phone does from recovery still showed the unlocked padlock, but upon one more reboot, the phone boots normally again. I have not yet attempted re-rooting.
The complete factory wipe also fixed, for whatever reason, my GPS problem.
So, if you are having either/both of these issues, I can tell you that, for me, a Factory Reset seems to have resolved them both.
I'm posting this hoping any others having these issues might fast-track themselves to a solution.
Related
I used the 1 click toot method and thought I may return my fascinate. I decided against it and tried to root again with no luck. The root always has a bunch of FC's and eventually gets stuck. The generic ringer also starts with no way to stop it. Only a battery pull will restart the phone afterward. I have also already really installed the Samsung drivers for the phone. Anybody have any thoughts?
Did you go back to stock via odin...if not do so...and push root manually...instead of an app.
I did through Odin. Tried to push root manually last night. The phone froze right after the push and never recovered. Had to battery pull. I had all of the files pushed and got to the chmod and wait stage when it froze.
Hmm, maybe re push to stock in odin...make sure you are doing the correct files...though it sounds like you did...a second time around sometimes seems to hit the spot...droid used to give me the same issues with sbf.
Do a factory data reset after you redo the odin recovery. Make sure you are using the verizon file when pushing each flash and doing it in the proper order. Then manually root, dont use one click or an app.
Also remember to push the files one at a time and let the phone restart between each one booting back into download mode.
Sent from my SCH-I500 using XDA App
I've been working all weekend so I havent had too much time to deal with it. I wiped data and cache in the recovery menu initially and then the phone wouldn't allow me to sign back into my Google account. It kept telling me that I didn't have a data connection on 3g OR wifi. I finally did a factory reset through the privacy menu (not in recovery) and all seems to finally be working and completely stock. Now off to root and flash voodoo...
hey i had the same problem i made a post on how to fix it though.. go to the 0.00 internal storage issue mine was doing what u said plus more but i fixed it just follow the steps i set
http://forum.xda-developers.com/showthread.php?t=804457
Got it. Just for the record: Rooted, Flashed all three files with Odin to get "back to stock". Re-OTA'd. Somehow Busybox and Su were still there so I manually removed. Then changed my mind about returning the phone and attempted to root again with no luck. Re-flashed through Odin ok, then attempted root but errors prevented finish. Cleared data and wiped cache through recovery. Then my google account wouldn't resync b/c of network connection error, even though I had a working data connection the entire time. Tried booting into recovery and clear and wipe data again. No luck. Finally decided to use factory data reset from within settings. Now all clear, rooted again, re-synced my google account and all good. You guys rock. Thanks for the help.
Hey all.
So just a few hours ago, I was running rooted stock, as per the guide in the development section. I then installed twrp, and attempted to flash a ROM, which resulted in my phone not booting.
Since then, I got into recovery, attempted a factory reset (which didn't work), and ended up using Odin to restore to stock.
So now I'm sitting on the stock image, unsure if I have root. Everything seems to work fine, but is slow. Also, I cannot enable wifi (the switch goes on for a split second, then back to off).
Is there a way I can uninstall twrp, and go back to complete and total stock?
If it's relevant, I get a constant "This device has detected an application attempting unpermitted actions..." error.
Thanks guys!!!
UPDATE: It still has root access.
UPDATE 2: I'm finding some similar issues people were having with the T-Mobile version (http://androidforums.com/t-mobile-g...connect-wifi-prevention-information-help.html) though I'm not sure whether I can follow those solutions. I will wait until someone can advise me on this.
It sounds like you didn't installed the complete stock image, that the stocked rooted image is installed. Have you done factory reset?
wolfgrrl said:
It sounds like you didn't installed the complete stock image, that the stocked rooted image is installed. Have you done factory reset?
Click to expand...
Click to collapse
I tried the factory reset option from within twrp recovery, which doesn't fix any of these issues I'm having with constant security alerts or Wifi.
Got it fixed by doing this:
http://forum.xda-developers.com/showthread.php?t=2301259
I'm new to rooting and it took me a while to get it working on my phone. It was going great though for over a year until today. I updated my phone with an AT&t update and after it booted me to the recovery area which I believe is called teamwin. I updated that too (like I have a couple of times) and my phone completely stopped working.
After troubleshooting for a few hours I was able to boot into safe mode, which I then did a factory reset. I've been able to install apps, but I none of them seem to work. Spotify is giving me error messages saying, (no storage area found) and when I installed zedge to look at ringtones and whatnot I couldn't install anything through there.
I'm assuming I have to redo the root process, but I was hoping there was another fix I'm not seeing. Like I said I'm very new to all of this. Any help would be awesome and also if I have to reroot is there any specific I have to do? Like getting rid of what I've done already?
KStef56 said:
I'm new to rooting and it took me a while to get it working on my phone. It was going great though for over a year until today. I updated my phone with an AT&t update and after it booted me to the recovery area which I believe is called teamwin. I updated that too (like I have a couple of times) and my phone completely stopped working.
Click to expand...
Click to collapse
You need stock recovery, as well as stock ROM (never rooted, unrooting does not work) in order to update OTA.
The phone tried to boot into stock recovery to install OTA; and since you don't have it (TWRP is a custom recovery), update fails.
General rule on Android, is that OTA updates don't play well with root. You should always research (for the specific device) before applying an OTA to a rooted device. That includes requirements to OTA, and also the expected results. On past devices, I've seen it not uncommon that an update removes the ability to unlock the bootloader and root. So its good to know what you are getting into before installing OTA.
KStef56 said:
After troubleshooting for a few hours I was able to boot into safe mode, which I then did a factory reset. I've been able to install apps, but I none of them seem to work. Spotify is giving me error messages saying, (no storage area found) and when I installed zedge to look at ringtones and whatnot I couldn't install anything through there.
I'm assuming I have to redo the root process, but I was hoping there was another fix I'm not seeing. Like I said I'm very new to all of this. Any help would be awesome and also if I have to reroot is there any specific I have to do? Like getting rid of what I've done already?
Click to expand...
Click to collapse
I suspect that your internal storage got corrupted somewhere along the way (as you were trying to OTA, recover, etc.). I'm not clear on the current status, you are still on the stock rooted LP ROM, with TWRP custom recovery?
If you still have working TWRP, I'd suggest booting into TWRP, select Wipe from the main menu, then the option to "Format Data" which will format internal storage. Strongly suggest not picking any other options (particularly in "Advanced Wipe" section) unless you know exactly what you are going. Lots of posts on here, by folks that delete things like System (OS) and wonder why there is no longer any OS!
After formatting internal storage, reboot and see if you still have the same issues accessing storage. If so, you may need to RUU back to full stock image, and root again. But we'll cross that bridge if the TWRP format storage option doesn't work.
Hey guys, I was running stock ZVC (with stock recovery and bootloader) until just a few minutes ago, when I finally gave in and told the phone to apply the OTA update that was pushed out last week (the "ZVE" one). It started doing its thing, but next time I looked back at the device it was in recovery mode, just sitting there at the menu prompt...
I've since tried rebooting and powering off about half a dozen times, but it just keeps looping back to recovery mode. I also tried wiping the cache and rebooting, with no luck... It still loops back to recovery mode. I don't know what went wrong, but I'm assuming it could be related to one of two things that I didn't think about until afterwards:
1) The phone was rooted via Kingoroot, and root was still active when I tried to apply the update.
2) Just a FEW programs were frozen via TitaniumBackup (as well as Android's own app management system, using the "disable" feature), but these weren't system- or kernel-critical apps. They were things like LG Health, Sprint Money, etc...
Can anyone suggest a fix? Right now it just keeps rebooting into stock recovery and I've never had to deal with an issue like this, so I'm not sure what to do. I was obviously running the stock ROM, so I'm not set up to flash stuff. Although if it can be done with the default recovery, I suppose I could obviously do that... Once again, everything was stock on the phone except for Kingoroot, which was still enabled during the update.
I'm in a pickle here, guys. It's not like I'm any different than everyone who "needs their phone for work," but yeah, I need my phone for work... If I have to wipe data/factory reset, there's probably no way to pull some data off of the phone via PC first, is there? I suppose it's not that big of a deal, but I have some data and some program data that I hadn't gotten around to backing up yet, because I didn't think I'd need to until before I attempted to flash a new ROM or custom recovery.
Any help would be HUGE. Thanks...
EDIT: I took it into the Sprint store today a couple hours after I posted this, and they said I'd have to send it in to LG for warranty service. I don't know if the Sprint tech person knew what she was doing or not (because she had to use Google to figure out how to put the phone into download mode, even though she owns the same model), but she said that she couldn't establish a connection between the PC and the phone...
Now I'm not sure if that's the case, or if she just didn't have the right drivers installed, or if she was even in the right mode (I think she was using some Sprint-made flashing tool, but she did get it into download mode). She also seemed bored and like she just didn't wanna deal with it, so I don't know...
Assuming I can flash back to an earlier build like ZVB (and assuming I can even find it online), is that done from download mode or from recovery? By the way, we also tried just doing a factory reset and that didn't work either; just keeps rebooting to recovery...
Thanks...
EDIT 2: Fixed by flashing to stock via these instructions. Had to select Board DL and use a different key sequence as described here.
I thought you guys might find this amusing, and hopefully it will help some people that get into a similar situation as myself. First, a little background - I rooted and installed Alliance Rom years ago back before the bootloader was unlocked. This worked amazing for me for a long time but I've recently had some weird issues with my phone so I decided to do a factory reset.
I went into settings, clicked factory reset, and then my phone got into a boot loop on recovery. I remember from before I had to do a regular boot then click recovery at the prompt instead of doing the factory recovery so I did that.
Instead of doing a normal wipe, I wanted to wipe everything on my phone and start from scratch so I did the full wipe (in what I think was TWRP or safestrap or whatever). When I went to reboot my phone it had a message like "are you sure? there's no OS installed" and I clicked ok. Well now I couldn't get the phone to boot into anything except download mode so at least I can use Odin.
I'm frantically searching google to try and find ways to install some sort of recovery so I could load AllianceRom again since I still had the zip file for it. Eureka, I found TWRP for my phone! I tried to flash TWRP through Odin but that doesn't work because my bootloader wasn't unlocked.... I remember this from last time ... all of the places I found online to install any sort of recovery required the phone to be booted into android.
So I'm clicking around and someone has a recovery randomly posted in a thread so I install it thinking, what the hell, what's the worst that could go wrong. So I install it through Odin and boot into normal recovery and I get this message saying my phone has been tampered with and to go to a verizon store immediately! Oops... upon further investigation (looking at the download screen), I tripped the knox flag... oh well, it's not like my phone is in warranty anymore (I got it on release day).
I search around looking for what I should do next and I found a thread that talked about being on complete stock, rooting, then unlocking the bootloader. I download all the files I need (newest firmware here - https://www.sammobile.com/firmwares/galaxy-note3/SM-N900V/ and thread here - https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010) to go back to stock and flash in Odin. Actually I didn't download from sammobile.com because it was downloading too slow so I just googled the file name and found it somewhere else faster, go figure.
Everything seems to be going ok then all of a sudden FAIL in Odin... Ahhh what the heck do I do now? Try again obviously! Second try works woo hoo! Phone start booting up, things are looking good!!! hooray!! But wait... it's taking forever to start and it's stuck on the Verizon logo... uh oh... taking way too long to boot up so I pull the battery and try again. Boots right in saying that android is upgrading so I think I'm finally in the home stretch here.
I try to run the ArabicToolApp for Root but I installed the latest firmware which isn't supported DAMN IT! Downloaded the correct firmware (OB6!), flashed in Odin, same problem before where it was stuck on the red verizon screen, pulled battery, rebooted, finally time to get root!
Phone finally boots into OS and I get a popup "unfortunatley com.google.process.gapps has stopped" great... and it keeps coming up over and over again after I hit ok... just my luck! Reboot again to see if that fixes the issue. Seems weird that I didn't have to go through all the initial setup stuff I did on the other version I installed... hmm... or maybe it was because I pulled the battery on the red verizon screen? Whatever. I somehow manage to get to options to do a factory reset and I let the verizon screen stay on a while this time. I'll go take my contacts out and give my wife some love while I wait
Come back and the phone is at the setup wizard, this is good news. Enabled USB debugging, installed root, done! Thank god!
Next I want to unlock the bootloader. I follow the steps here which aren't very clear (I'm guessing on purpose for novice computer users) - https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
1. I installed eMMC from the play store to make sure my CID started with a 15, it does so I know I'm good to use the hack.
2. I installed both files in the unlock kit (adb and driver setup)
3. Fired up adb, navigated to where I had unlock_n3, and ran through the first part of the code once, reboot my phone, checked that the CID was the developer CID, and then ran the second part of the code three times before it worked
I verified the bootloader was installed correctly by trying to install TWRP through Odin, which worked!
I'm going to try out Jasmine Rom since it's a popular one that is on 5.0. My SD card only showed 30 megs free or something like that, so I formatted it from within android and copied the zip file over and installed the Rom through TWRP. Rom installed just fine, so I did one last factory reset which worked great and I think I'm finally good to go!
If you have any questions or run into any issues feel free to reply here and I'll try to help as much as I can.
Glad it worked out for you in the end.
From making a few mistakes I know that sinking feeling "oh no, what have I done?"
FWIW, the bootloader unlock method (in principle) works from nearly ANY ROM which is rooted - so, you would have saved yourself a bunch of time if you had started with that before you wiped the Alliance ROM. So long as you have root and a CID value that starts with 0x15, you just need root privileges - no need to return to stock and re-root.
(The "in principle" part is that there were several bugs in the "safety checks" portion of the unlocker binary that were sensitive to the OS revision, so you might have to search through the unlock thread to find a version of the unlock binary that is compatible with whatever rooted ROM is on the phone when the unlocking is attempted.)
good luck
PS The AryaMod ROM (w/ phantomOne kernel) is pretty solid - Marshmallow w/ S-Pen apps, too! As with any other dev ROM, there are a few sharp edges, but mostly everything works (except NFC).
.