Hi. My S6 has been running great for a while. It's running CleanROM. I got a notification that there is an update to SuperSU. I chose to update it normally because there's no recovery since the bootloader is locked. During the upgrade, I got a message saying that Knox was detected and if I wanted to disable it (temporarily?). I chose Never not thinking about the implications. The phone rebooted as part of the upgrade but now it is stuck in a bootloop. It does boot up for a very short time. Enough time for me to draw my security pattern and for some apps to load, but then the phone reboots. Any idea what's going on? Any suggestions on recovering from this? Thanks.
UPDATE: Somehow I recovered. I was able to power down the S6 because I had that small window to do so. I booted to Safe Mode and disabled SuperSU. I rebooted normally and everything was ok except SuperSU was disabled. I uninstalled SuperSU Pro and then uninstalled all updates for SuperSU. Play Store wouldn't let me totally uninstall it. I updated SuperSU. This is where it gets a little foggy. I think I re-enabled SuperSU and then it said that Knox was detected and whether to try to disable it or never disable it. This time I chose to disable Knox. SuperSU tried to disable Knox but got stuck with the spinning arrow. It was strange because I was able to go to Settings, but when I went to Apps or Logs, I got a continuous spinning arrow. It seemed to do what was needed though because my root checker verified I was rooted again. I rebooted again and ran SuperSU again. It gave me the Knox detected message again. This time I said Never disable. Rebooted one more time, ran SuperSU and no more message. Last step was to reinstall SuperSU Pro. I am not sure exactly if I had to do all these steps and what exactly was going on, but I think I am back to normal running SuperSU Pro v2.79.
Related
I downloaded the z4root app and started it. I started the install for permanent root. It appeared that everything started up fine, a screen came up stating that it was "running exploit in order to obtain root access..." this ran for approximately 10 minutes then stopped processing. The phone is now stuck on the Blue z4mod screen showing no activity. The little circular icon has stopped moving.
I have not done anything to the phone to disturb it, but......
Is it locked up? Should I pull the battery and reset? Not sure, this is my first Droid (Blackberry before).
Some help ASAP to get the phone going again would be greatly appreciated.
Thanks
Use z4root 1.1.0 instead and it will work immediately. Some bug in newer version causes it to hang like that.
Hey, thanks for the reply. I actually pulled the battery and it reset itself.
I then tried the temporary root and it worked, but...
It said there was a new version of the su binary available. Press ok to attempt to install it automatically. When I pressed ok the message came up
An error occurred and the su was not updated. A zip file (su-2.3.1-bin-signed.zip has been placed on your SDcard, please reboot into recovery mode and flash it to update your su binary.
?
How do I reboot into the recovery mode?
Thanks
I have a Samsung Galaxy S5 mini on stock rom, rooted. I was looking through Xposed for new possibly interesting modules. I installed one which said you can set volumes to have more than 15 points. So I installed it but I did not reboot yet figuring that I would do that later. I made all new backups of my apps and data using Titanium backup and then tried to reboot my phone but the reboot menu button would not work and the screenshot button at the top was blank yet functional. So I loaded up, or attempted to load up Wanam Xposed to check what was going on since that is what configures my rom and it said the app was not installed when I pressed on the shortcut.
So I rebooted the phone, entered the encryption password, it came up to the lock screen and from that point it would say my password did not match. I tried every password I have ever used, varying case and everything. No password worked. I had not manually changed it either. I had no choice but to factory reset the phone and format the SD card. Also I should mention that when I found out that wanam xposed was not seemingly installed any more, I attempted to install it and it would just say "App was not installed" or something. Then I installed Wanam Toolbox or something, I forget exactly now, but that installed and I rebooted and that's when I noticed my lock screen password was not working.
Any ideas on what the cause may have been and what things I could attempt to do if it ever happens again? I thought there was a thing where you can use your google account to unlock the phone but I could not get that thing to come up.
I have the US 32gb unlocked version. Tried to do the downgrade to install CM using the method mentioned several times that changes the version from a command put in twrp.
First I unlocked bootloader, then installed twrp, then did the command line thing to lower the fw version, then put the v1.12 firmware on zip then rebooted to install.
Well, the install failed so I decided to stop there and try to put everything back to stock by using the latest ruu exe from HTC. The exe started sending a file to phone, then locked up and threw an error. I restarted the exe and it finally passed. I got everything set up and went to bed while it was updating apps.
This morning, shut off phone to put in SD, and when turning on it was optimizing apps then when done, would reboot and optimize again. The phone was stuck in this loop until I let the battery die. I couldn't do anything with it.
Battery finally died and tried to run the ruu exe again. This time it would not pass at all, no matter how many tries. I wanted to try to run the zip from SD but the latest firmware I can only find as exe.
Finally decided to just do a factory reset from recovery mode. This let the phone boot normally and I could do set up again. I tried doing a soft reboot, and it booted fine. Then I disabled apps I don't use, and did a full power down, now the phone is back to doing the 'optimizing apps' bootloop.
Right now I'm waiting for it to run its battery down again so I can at least get to download mode/recovery. Maybe I will try a full power off and app disabling separately, to see which is causing the loop.
Anyone have an idea what's going on? A link to the latest ruu in zip form? I really need a sure fire way to get this thing full clean stock (remember the exe is failing for me) to eliminate if thats the cause. Is it because I edited the version number?
Edit: just realized I put this in the wrong section
Update: Once battery died, I did factory reset again from recovery. Went through setup, and I then immediately shut the phone completely off and turned back on. It booted up fine. I then went to disable the same apps as before, EXCEPT for the "Google App". Phone still powers up fine, so I left it there and phone is working fine. I didn't want to see if disabling the Google App was causing the phone to boot loop. I had that app disabled the entire time I've had the phone, but don't think I've ever completely shut the phone down, so maybe that's why I never had the problem.
Still don't know why the ruu exe didn't work. Hopefully it was the computer, and I can still take updates.
I have the same problem, can't disable apps without phone going into bootloop on restart. Can you tell me what apps did you disable? Facebook, Instagram, Google docs, HTC apps etc,etc...
hmedved said:
I have the same problem, can't disable apps without phone going into bootloop on restart. Can you tell me what apps did you disable? Facebook, Instagram, Google docs, HTC apps etc,etc...
Click to expand...
Click to collapse
I think what caused my problem was disabling the app called "Google App". No problem disabling all the Facebook and Instagram apps.
What about Google docs, slides and news apps? Can those be disabled?
Same problem with my A9 bought a week ago. Like Rouyal, I recall disabling the Google App and then came the OTA update and the bootloop. Tried alll permutations of buttons and even when I could get to RECOVERY MODE, all the options looped as well, returning to the same screen: no bootloader, no recovery. The only alternative screen was the "Enter your code to decrypt your drive" after leaving RECOVERY MODE. It looped as well. Copied the stock RUU to an external SD card; did nothing (with HTC Sync).
SOLUTION: Enter wrong codes for the "decrypt your drive" screen 30 times; that is the limit before the drive gets a factory reset. After the 30th it was factory reset. On restarting, the systems asks for the SAME email that was used previously.
I might as well try here if anyone will see my post.
I'm screwed. Latest stock ROM, unrooted and locked bootloader. I have/had the Google App (beta) installed on my phone but for the past couple of days it was constantly crashing and my phone became sluggish so I decided to uninstall it today. I left the beta program and as provided with instructions there went to uninstall the beta version to install the non-beta one.
It stayed on "uninstalling" for about 10 minutes and I presumed it was just a Google Play glitch and decided to reboot my phone. Big mistake! After the first install it was optimizing apps (but only one, so it was probably the Google App but it never got out of the next step (starting system/app, I don't recall what it said exactly right now)). I decided, stupidly, to reboot the phone since it was stuck and now I'm stuck on a bootloop and the phone won't even go past the Android logo animation. I guess the uninstallation never completed somehow and the app got corrupted(?).
I'm lost and I don't know what my options are except trying a factory reset and/or even unlocking the bootloader and getting a custom recovery and potentially rooting the phone too. But I really don't want to lose my data!! I have no backups.
Is there ANY chance I could somehow manage to solve the problem? Is it possible to sideload an app with a locked bootloader and stock recovery? I'm trying to sideload the Google app back in case it got corrupted but it doesn't work. I get the following errors:
Code:
E: footer is wrong
E: signature verification failed
installation aborted
Haaalp!
EDIT: Even weirder. I just let it run the booting sequence again and it got beyond the lollipop logo animation and is now stuck on "Android is starting... Starting apps." message.
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
shagexpert said:
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
Click to expand...
Click to collapse
I had the same issue when I first got my 6 when I was playing around with the slots. Also my original TWRP install for some reason would crash and reboot whenever I plugged in the data cable while in TWRP. I ended up flashing back to stock OOS 5.1.5 through fastboot (used the flash-all command) and then reinstalled TWRP and everything has been working great since then.
MickyFoley said:
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
Click to expand...
Click to collapse
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
To be honest I didn't know they did the same thing (magisk and Super SU). I am curious now, what if I factory reset my phone and attempted to install Super SU instead of Magisk this time?
If I do a factory reset (let's say I want it just like it was out of the box and I format the data partition as well), will I need to root the phone again? I am asking because I don't know which part of the instructions I should ignore. I am sure TWRP will already be installed after the reset so I would only need to install the extra apps...
You don't have to format data. Just factory reset it. Then use "fastboot boot twrp.img", don't allow modifications, flash a kernel you want (if you want one - I really recommend ElementalX) and then the latest version of Magisk (16.4 BETA currently). Did so - all fine. And yes: Even Titanium Backup works without any issue with Magisk.
We had similar problems with TWRP on the Razer Phone when it was new. We solved the problem by using the TWRP boot image to flash the stock boot image and then flashing a TWRP zip. I just got the OnePlus 6 yesterday and haven't really messed with it yet but everything sounds the same to me so far.
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
shagexpert said:
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
Click to expand...
Click to collapse
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
shagexpert said:
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
Click to expand...
Click to collapse
When your phone booted straight into that mode with black screen and the led, then you bricked it. Same happened to me 2 days ago. The solution was to use the Msmtool from another thread and it worked great. Just follow the guide. But it will wipe your device. And you have to install oxygenos manually via "local upgrade". If you have a question, just ask
What I ended up doing was restoring from the backup I had. This was the "bad backup" without WiFi and broken finger print and facial recognition. After the restore, I did a normal wipe (not advanced). This reset the phone to factory settings. Once I configured WiFi and signed into my Google account, Google offered to recover from a cloud backup of my One Plus - I didn't know Google made these backups. It downloaded all the apps automatically. I don't know yet if I have sign into all of them all over again.
The bad back up saved my ass, I wasn't even planning on making it. I was just testing the backup feature. That's why you should always do a backup, even if the device isn't in ideal configuration.
shagexpert said:
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
Click to expand...
Click to collapse
I rooted my phone with Magisk and installed the 5.1.6 via OTA (and reroot via installed Magisk Manager). So no need to install TWRP so far.
Titanium Backup runs flawlessly with Magisk (already on my OP 3T and my OP 5).
So give Magisk a try, I never had such an easy and reliable update as the one from 5.1.5 to 5.1.6
Helium is a great alternative to titanium.