So I have bitten the bullet after all of the issues that I was having with my phone today and I did an SBF flash of my Droid 4's firmware. I rooted successfully and installed Busy Box, but I am unable to install Safestrap v3.72
I get to the 60/100 point where it is "Running Installation Script" but it never gets beyond that. I have also tried to Uninstall in case one of the several tries worked behind the scenes, but that also gets stuck at 60/100. This allegedly has something to do with Busy Box not being installed, but I have done that for sure.
Update: Just repeated the root process with SafeRoot and that installs Busy Box as part of the process. Completed successfully, and I'm still hanging at 60/100...
What else am I forgetting to do?
Related
Hey guys, I'm definitely a novice in these matters, but this is the first time I've had a problem so I'd appreciate some help.
While my Droid was on FRG83D I rooted with SuperOneClick using rageagainstthecage. I had to install PdaNet to get it to work, but it did work for me. This morning I got the OTA update for FRG83G and downloaded and installed it just a few minutes ago.
I didn't unroot my phone before I did this.
Afterwards the two apps I use that require su won't work (Barnacle and ROM Manager for backups, I don't have a custom ROM flashed to my phone yet) so I ran SuperOneClick again, ran root using psneuter. Still didn't work so I unrooted using psneuter. Then I realized that I should probably unroot using rageagainstthecage and did so. So at this point (theoretically) my phone was unrooted. Then I ran root with rageagainstthecage again and my two apps still won't work.
Every time I rooted or unrooted using either method SuperOneClick worked seemingly perfectly.
So here's my question: What did I do wrong? And just as importantly, how do I fix it so I can have root access on my phone again?
*Edit* Well this is pretty embarrassing. I just rebooted my phone and tried Barnacle again, and the su acceptance box came up like it's supposed to. I suppose I'm back to being rooted. I think I'll leave this here, and if anyone has any constructive criticism of my (lack of) process or comments about why things acted the way they did and why it works now I'd like to hear it. I'm all about learning more about all of this.
I've tried searching, but didn't seem to get anything on this one.
I've been trying to install the OTA Update to 4.3 for a minute, now... Currently, I've got the update downloaded, but it won't continue b/c it's saying the battery is too low. The thing is, the battery is at 100%. It is also plugged into a charger... Tried it with and without.
Here's info on my phone:
MJ5
Rooted via Kingo
Xposed Installer installed (very few modules installed - nothing hardcore)
RootCloak [1.4] installed in order to hide root status from the OTA update service
I have a bit of bloat uninstalled by Titanium Backup... But, that was all AT&T stuff like Navigator - I left the OTA service in place. I froze some Samsung bloat, but didn't uninstall it.
Any ideas on why I'm getting this error?
You have to be unrooted. At least that what I hear . When I got the update I did a factory reset and downloaded the update and installed with no issues.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Blargh. I unrooted via Kingo, rebooted and I am still getting the same low battery error.
I really don't want to have to do a factory reset...... Are there any other options?
Ah, great. Now Kingo won't re-root the phone. Looks like factory reset is what I'll be spending my evening doing.
Great. Did a factory reset, and went to update. It failed; said the installation was interrupted.
I tried two more times... Same results. This is getting pretty frustrating...
Pscheoverdrive said:
Great. Did a factory reset, and went to update. It failed; said the installation was interrupted.
I tried two more times... Same results. This is getting pretty frustrating...
Click to expand...
Click to collapse
Unfortunately nothing will work except restoring back to stock. I had to do that for the last 2 updates we've received. I just did it to get the last update and I am staying stock until Kitkat arrives then will look for a root solution. I know, it sucks.
Follow this thread:
http://forum.xda-developers.com/showthread.php?t=2559715
Pscheoverdrive said:
Blargh. I unrooted via Kingo, rebooted and I am still getting the same low battery error.
I really don't want to have to do a factory reset...... Are there any other options?
Click to expand...
Click to collapse
If you didn't uninstall the Xposed modules the uninstall Xposed that could be your issue right there. Try uninstalling everything root then try again.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Well, at this point, I have done a factory reset several times. No root, nothing installed.
Knox keeps giving me a notification that it's blocking a process... I can download the update and start the install process. Once the phone reboots and the AT&T splash screen comes up, the progress bar will start and get to about 20%, then the phone will restart, then boot normally. Once booted, it will go to the Update page and then say that the installation was interrupted.
What... the... heck... I thought a factory reset restored the phone to like how it was from the factory? I notice my keyboard is the old version, too. When I bought the phone, I had the updated keyboard with punctuation for long-key presses.
Any insights?
Pscheoverdrive said:
Well, at this point, I have done a factory reset several times. No root, nothing installed.
Knox keeps giving me a notification that it's blocking a process... I can download the update and start the install process. Once the phone reboots and the AT&T splash screen comes up, the progress bar will start and get to about 20%, then the phone will restart, then boot normally. Once booted, it will go to the Update page and then say that the installation was interrupted.
What... the... heck... I thought a factory reset restored the phone to like how it was from the factory? I notice my keyboard is the old version, too. When I bought the phone, I had the updated keyboard with punctuation for long-key presses.
Any insights?
Click to expand...
Click to collapse
Factory reset just wipes your data and cache. It will not reinstall the system files. When you rooted you directly modified some of your system files via root access. Simple solution however. Follow these steps as mentioned before by theorioles33 using Odin and Heimdall. Takes about 10 mins (maybe 30 if its ur first time) Follow every step to the T and when ur back to stock try the OTA. Good Luck!
Hello, all!
I've searched the web, and haven't been able to find any reports of this.
I recently downgraded from CM12 to Kitkat 4.4.4, and was going through the steps of re-setting up my phone. I rooted it/installed SuperSU, installed busybox, installed greenify, as well as a bunch of non-root apps. I finally decided to install Xposed Framework to get the experimental features in Greenify (I did this fine in 4.4.3 a year ago), but this is where I ran into trouble.
I downloaded the newest Xposed Installer (2.7 experimental1: http://repo.xposed.info/module/de.robv.android.xposed.installer), opened it, clicked on "Framework," and clicked "Install/Update." I was shown a message for a fraction of a second that looked like it said something about it being successfully installed, and the screen went black. I didn't think much of it, figuring it was rebooting, and left it for a couple of minutes. Nothing happened, so started pushing the power button, then holding it, and absolutely nothing happened. No backlight, no bootloader, no nothing. I plugged it into my computer, and it showed up as "qhsusb_bulk."
Long story short, it was hard bricked. Fortunately, I was able to revive the thing using this guide (http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798), and re-flashed 4.4.4 on it. I have just successfully installed Xposed Framework going through the same process I did previously (in fact, all my apps were still installed, since I didn't wipe them when re-flashing), so am unsure what happened, so everything was either the same, or at least very similar to how it was set up when I tried previously). I'm figuring it could be any one of three gazillion things that could have caused it...
Anyway, figured I'd mention it here for any future Googlers who may run into this issue.
Thanks for reading!
ElectroPulse
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 know these phones are a bit dated, but I have a pair of AT&T SGH-I747's that I've been trying to get rooted. Using Kingoroot, they both crashed and rebooted at different %'s and upon reboot one failed and one passed the root checker test.
The one that passed crashes upon attempting to do anything with root (seemingly as soon as an app requests the permission), this includes attempting to update the binary for SuperSU and any other root-based app.
The one without root continues to crash upon re-attempting the root process. Attempting a CF-Autoroot via Odin elicited a crash during the "Extracting" step on the phone (the actual Odin part went fine).
Is there any way to fix whatever may have been damaged/corrupted by the initial crashes and start over, or otherwise repair it? If there is a crashlog somewhere I can access I will post that if someone tells me where it may be.
Thanks in advance.