I get that message when I go into Settings>Application Manager and tap on the All tab. If I try this several times, the phone starts rebooting when I just try to go into Settings. I tried wiping cache in the stock recovery, but that didn't help? Any ideas?
wipe data
droidstyle said:
wipe data
Click to expand...
Click to collapse
Thanks. Wiping data is the same as a factory reset in that it will revert phone to original state when purchased, correct?
Wingnuts said:
Thanks. Wiping data is the same as a factory reset in that it will revert phone to original state when purchased, correct?
Click to expand...
Click to collapse
yes and it will reformat your internal sd, so back it up first.
OK, thanks for you help.
I've backed up my IMEI with adb nvbackup and QPST. The Synergy backup .zip doesn't work unless I'm rooted and unlocked, correct? Should I root / unlock and flash the Synergy zip before wiping data? Any chance rooting and unlocking will fix the 'settings has stopped' issue? I assume wiping data will cause me to lose root and unlocked state. Thanks for your help.
sordswi seems
Same thing with me on Samsung GT-I9300 with Android 4.1.1
I came across this problem 2 times.
The first time it happened when I installed a game "Waking Mars". The game was working fine, I played for around 20 minutes and then wanted to check free storage left after installing. But when I opened Application manager swiping was very laggy and after a few (5-10) secs it crashed with "Unfortunately, Settings has stopped" error or just closed. At that time I didn't know that it was because of "Waking Mars" and started to delete unnecessery applications I installed that day and yesterday, but problem vanished only after uninstalling "Waking Mars". Also, while this app was installed, phone's screen was glitchy and became bleached (the glitch disappeared after rebooting), like when "Natural" screen mode is activated, but it wasn't. When I had tried to install the game again, the problem came back.
The second time it was because of "Galaxy On Fire 2" installed. Same problems appeared: crashing Application manager and glitchy screen.
Both games contained their data in ".apk" file, but another Waking Mars version with separate data (cache) caused the same problem too.
By the way, funny thing is that both games are about space
P.S.: Sorry for my English, it isn't my native language.
Hi.
I installed some dodgy app which required root access to operate (but it didn't even though I allowed it in SuperSu) and this is where my problems started.
First of all, I noticed each and every app I tried to run would immediately crash. That included system apps, such as the Settings app. At that stage I was left with only the launcher working and attempts to uninstall apps would also cause a crash. Even the shutdown menu was broken and the phone hung up so I was forced to reboot it by holding the power button for 10 seconds.
After that, the phone would no longer be able to boot, it was stuck in a boot loop, but recovery still worked (TWRP for that matter) so firstly I wiped the cache partitions (including dalvik cache) but that didn't help, as the phone still wouldn't boot. In this case there was only one thing left for me to try and that was the factory reset capability of TWRP which claimed to not even touch internal storage so I was fine with that and did the wipe.
Thankfully, the phone booted afterwards and it welcomed me with the first startup guide (the language selection dialog was really buggy but that's Huawei's fault) and the phone was seemingly ok, except that the whole internal storage had been wiped out but not only that - the external microsd card was empty as well! Could you believe that? I couldn't. TWRP promised not to touch internal storage and the external memory card wasn't even mentioned but why would it wipe it anyway?
That's for the story behind it, now for the actual problems I'm facing right now:
The stock remote app is gone
The boot animation has changed to a different one (now it's a silver "android" logo instead of the "honor" logo)
Battery usage stats are not available (see: http://i.cubeupload.com/BXCknW.png)
Sound quality from the built-in speaker seems noticeably worse
Hereby, I'm asking you guys to help me out with all of this.
The "remote app missing" problem could be solved by someone sharing their apk file with me, that's probably the simplest one to fix.
As for the boot animation, I have no clue as I don't even know what files are responsible for that.
The same for the battery stats problem, I'm already through a couple of full-charge-to-discharge cycles as well as wiping the cache partition, but the problem remains.
The sound quality probably has to do with the DTS sound enhancer. The config file for that is either "/cust/unicom/cn/xml/dolby_config.xml" or "/cust/unicomelectric/cn/xml/dolby_config.xml" and I'm asking you to upload these files somewhere so I can compare them with mine to see if anything is different.
The device I'm using is the H60-L02 variant running the B532 ROM.
Does the 3 buttons method erase internal storage as well? I've already set up quite some apps and having to do it again wouldn't be the most pleasant surprise. But at least in this case I could make some backups and whatnot...
Also, would it work if I flashed B535 straight away or does the 3 buttons method expect the same version which is already installed, in this case B532?
pudup said:
It will wipe internal storage. You can flash any *full* ROM as long as you're not moving up or down from kitkat-lolipop/marshmallow.
Click to expand...
Click to collapse
Okay, so I decided I'd do the whole thing today. I downloaded the full B535 ROM on my PC, backed up all the stuff I care about from the phone to the PC as well, and also I downloaded the MultiTool.
Though the MultiTool thread says this in bold red:
VirusPlus said:
EMUI 3.1 WARNING! Update over rooted or system modded in EMUI 3.1 gives a BRICK.
You have to restore system and REMOVE root before every update in EMUI 3.1 for now.
Click to expand...
Click to collapse
So I also fired up Titanium Backup in order to defrost all the frozen apps, which went fine, and then I wanted to unroot the phone but I've been unable to do so so far.
To unroot, I launch the SuperSU app, navigate to the "Settings" tab and select "Full unroot". The problem being, it just gets stuck on the screen saying "Uninstalling, please wait...". I don't know how long it usually takes to complete, so far I've waited for maybe 10 minutes and nothing seems to change. Should I care about that? Is that warning about updating rooted/modified EMUI 3.1 resulting in a brick still true?
Can I skip this step and just flash the stock recovery followed by the 3 buttons method?
EDIT:
After some trial and error with the multi tool and different recoveries, I was able to finally unroot. Next, I flashed the stock recovery for B532 and attempted to do the 3 buttons method, but it would say "Install failed. The update package does not exist" (could be because I'm doing the update from a USB flash drive as I don't have an micro sd card big enough to fit the package). So I rebooted the phone into system and used the Updater to perfrom a local update where it would let me pick the USB drive. It completed without errors and then rebooted into some kind of updater (black background and some bluish emui colors) where it also took some time to finish thankfully successfully. I can right now see the phone booting and for what it's worth, the boot animation is once again the good old "honor" logo and not that ugly silvery "android" one
And now it's "Optimizing system...". I really hope it finsishes successfully as it's already a bit late here and I wouldn't like the phone to be unusable tomorrow :laugh:
36% ready...
46% it's kind of fun to watch this, and now 49%
I'd like to thank @pudup once more for helping out, I'm not really that much into flashing recoveries, roms and all that myself. Without your help I would probably be too scared to try doing something on my own :crying:
86%, 89%, 95% and 100%. Aww, what a relief Good old stock lock screen and wallpaper.
I had a bug on my S7 where it would say "No apps running" when in fact there were apps running - I read that the solution to this was to wipe the cache. I booted into recovery mode and wiped the cache - but I guess I must've accidentally selected "factory reset" (they really shouldn't have them right next to each other) and wiped my phone. I'm running stock Android, the phone isn't rooted.
Since starting over, my phone is now VERY VERY slow. Just trying to wake it up can take up to 6 seconds to get the screen to come back on. I have no idea what's causing it.
What I've tried doing to fix the problem:
* I've uninstalled almost every app except what it comes with
* I've tried disabling the stock bloatware apps
* I've tried clearing the cache again (making sure NOT to accidentally hit factory reset this time)
I'm at a loss. Any ideas? BTW, I don't have an SD card in my phone.
Thanks!
Piornet said:
I booted into recovery mode and wiped the cache - but I guess I must've accidentally selected "factory reset" (they really shouldn't have them right next to each other)
Click to expand...
Click to collapse
When you select an option in recovery, it's very easy to see which one is highlighted before you press select, if you selected factory reset instead of clear cache, it's your own fault for not looking what you were doing, not because they are next to each other, you've been too quick and not watching the screen properly
Not only that, but when you do select it, (Haven't been into the S7 recovery yet to check, but usually) you have to scroll down a list of empty lines before you reach the Yes option to actually perform the action
That said, I would try (considering the phone is now empty) another factory reset, see how you get on after that
Not sure if FRP lock would cause any problems?
Piornet said:
I had a bug on my S7 where it would say "No apps running" when in fact there were apps running - I read that the solution to this was to wipe the cache. I booted into recovery mode and wiped the cache - but I guess I must've accidentally selected "factory reset" (they really shouldn't have them right next to each other) and wiped my phone. I'm running stock Android, the phone isn't rooted.
Since starting over, my phone is now VERY VERY slow. Just trying to wake it up can take up to 6 seconds to get the screen to come back on. I have no idea what's causing it.
What I've tried doing to fix the problem:
* I've uninstalled almost every app except what it comes with
* I've tried disabling the stock bloatware apps
* I've tried clearing the cache again (making sure NOT to accidentally hit factory reset this time)
I'm at a loss. Any ideas? BTW, I don't have an SD card in my phone.
Thanks!
Click to expand...
Click to collapse
Have you restarted your Phone and sure that you not have any "Cleaner" on your device (except Sammys)?
I've been stressed out lately about trying to root my Samsung Galaxy J3 Emerge.
I got TWRP 3.1.0-0 and went on install but the supersu 2.82 zip file wasn't showing so I tried to fix it.
First I tried Format Data and that didn't work, then I tried Changing File System for System, Data, and Cache one by one and that seemed to have worked. The supersu file showed and I installed it.
Then I Rebooted System and it said,"No OS Installed! Are you sure you wish to reboot?" and this has happened to me before so I figured it would reboot back into TWRP and I would have to boot to download mode, and install the firmware through Odin, but that didn't happen, what happened instead was when I Rebooted System, on the top right it said,"kernal is not seandroid enforcing, set warrenty bit:kernal" and would keep bootlooping, I went back into TWRP by taking the battery out and putting it back in then holding power, home, and volume up and I was back in TWRP.
The thing is it would keep doing this and I'm kinda stuck right now tbh. I already tried Formatting Data, Flashing a ROM, and installing the SM-J327P Firmware, but nothing worked. I'm guessing the only way to fix this is by changing back to my original File Systems and then installing the Firmware through Odin, but I'm stupid and don't remember the original File Systems. So if any of you could tell me the default File System for System, Data, and Cache or another way to fix this that would be great. Thanks
I'm still stuck in this situation...
Any help plz?
IYaWonaRoo said:
I've been stressed out lately about trying to root my Samsung Galaxy J3 Emerge.
I got TWRP 3.1.0-0 and went on install but the supersu 2.82 zip file wasn't showing so I tried to fix it.
First I tried Format Data and that didn't work, then I tried Changing File System for System, Data, and Cache one by one and that seemed to have worked. The supersu file showed and I installed it.
Then I Rebooted System and it said,"No OS Installed! Are you sure you wish to reboot?" and this has happened to me before so I figured it would reboot back into TWRP and I would have to boot to download mode, and install the firmware through Odin, but that didn't happen, what happened instead was when I Rebooted System, on the top right it said,"kernal is not seandroid enforcing, set warrenty bit:kernal" and would keep bootlooping, I went back into TWRP by taking the battery out and putting it back in then holding power, home, and volume up and I was back in TWRP.
The thing is it would keep doing this and I'm kinda stuck right now tbh. I already tried Formatting Data, Flashing a ROM, and installing the SM-J327P Firmware, but nothing worked. I'm guessing the only way to fix this is by changing back to my original File Systems and then installing the Firmware through Odin, but I'm stupid and don't remember the original File Systems. So if any of you could tell me the default File System for System, Data, and Cache or another way to fix this that would be great. Thanks
Click to expand...
Click to collapse
You have to use the getprop command to get your software number. Then you have to restore that EXACT software. You might have probably updated unknowingly, and the bootloader updated too. So restoring to an older firmware might bootloop. It was a huge pain in the butt to get mines working after this issue but I got it right after a few tries. I flashed the custom J327p rom they made for it, factory reset and just waited until it booted. Was a long time but after trying every restore and refreshing, I got it working. There's the newest firmware out (idk the name since I just have the metro version of this phone now) but only that one will get the phone running. If you ever do get it running, root with magisk as this phone is VERY sensitive to SU and won't work half the time
savagevegeta said:
You have to use the getprop command to get your software number. Then you have to restore that EXACT software. You might have probably updated unknowingly, and the bootloader updated too. So restoring to an older firmware might bootloop. It was a huge pain in the butt to get mines working after this issue but I got it right after a few tries. I flashed the custom J327p rom they made for it, factory reset and just waited until it booted. Was a long time but after trying every restore and refreshing, I got it working. There's the newest firmware out (idk the name since I just have the metro version of this phone now) but only that one will get the phone running. If you ever do get it running, root with magisk as this phone is VERY sensitive to SU and won't work half the time
Click to expand...
Click to collapse
Thanks for the reply but I have tried restoring with a firmware with my exact software number, model, version, changelist, build date, country/carrier(sprint), and security patch level and I did a format data, yet It didn't work... As far as I know, the bootloop was not caused by the firmware, it was caused by me manually changing the Partitions' File Systems, however I do not remember the original File Systems for the partitions. In case this madders, the way I changed it was by pressing "Wipe" in TWRP, then "Advanced Wipe", then selecting "System", then "Repair or Change File System", then "Change File System", and choosing a random button. I also selected "Data" and "Cache" but I did it individually, one at a time.
IYaWonaRoo said:
Thanks for the reply but I have tried restoring with a firmware with my exact software number, model, version, changelist, build date, country/carrier(sprint), and security patch level and I did a format data, yet It didn't work... As far as I know, the bootloop was not caused by the firmware, it was caused by me manually changing the Partitions' File Systems, however I do not remember the original File Systems for the partitions. In case this madders, the way I changed it was by pressing "Wipe" in TWRP, then "Advanced Wipe", then selecting "System", then "Repair or Change File System", then "Change File System", and choosing a random button. I also selected "Data" and "Cache" but I did it individually, one at a time.
Click to expand...
Click to collapse
That's a tough one. I've never touched those options in TWRP. Have you used Odin to completely wipe the phone from everything including TWRP and flashing stock?
savagevegeta said:
That's a tough one. I've never touched those options in TWRP. Have you used Odin to completely wipe the phone from everything including TWRP and flashing stock?
Click to expand...
Click to collapse
I do have a brother that has the EXACT same phone as me so I tried installing TWRP on his phone and checking the original File Systems, however TWRP doesn't install on his phone for some reason. I enabled developer options, USB debugging, OEM, and installed the drivers and when I install TWRP recovery on his phone through odin it says it was successful but for some reason when I boot into the bootloader it's the regular one that comes with the phone and not TWRP. I'm guessing this is because he has low storage (95% used up). But he doesn't cooperate with me and says he doesn't want the TWRP on his phone because virus blah blah idk (and I don't know how to remove it without factory reset, which he doesn't want to do even though he can backup his stuff) also doesn't want to delete or free up storage from his phone. So I'm going to try wiping my phone through odin i guess...
IYaWonaRoo said:
I do have a brother that has the EXACT same phone as me so I tried installing TWRP on his phone and checking the original File Systems, however TWRP doesn't install on his phone for some reason. I enabled developer options, USB debugging, OEM, and installed the drivers and when I install TWRP recovery on his phone through odin it says it was successful but for some reason when I boot into the bootloader it's the regular one that comes with the phone and not TWRP. I'm guessing this is because he has low storage (95% used up). But he doesn't cooperate with me and says he doesn't want the TWRP on his phone because virus blah blah idk (and I don't know how to remove it without factory reset, which he doesn't want to do even though he can backup his stuff) also doesn't want to delete or free up storage from his phone. So I'm going to try wiping my phone through odin i guess...
Click to expand...
Click to collapse
Storage space has nothing to do with flashing recoveries because they have their own partition. I suggest you flash the same TWRP you used on his phone, then as soon as it finishes flashing, boot into recovery IMMEDIATELY by pressing volume up, power, and home. do NOT let the device boot. If you screw up and it gets to the Samsung animation, flash again and try again. This is because some of the latest Android devices tend to restore recovery upon boot for some reason. Through my experience, anyways. Try this and let me know your results.
savagevegeta said:
Storage space has nothing to do with flashing recoveries because they have their own partition. I suggest you flash the same TWRP you used on his phone, then as soon as it finishes flashing, boot into recovery IMMEDIATELY by pressing volume up, power, and home. do NOT let the device boot. If you screw up and it gets to the Samsung animation, flash again and try again. This is because some of the latest Android devices tend to restore recovery upon boot for some reason. Through my experience, anyways. Try this and let me know your results.
Click to expand...
Click to collapse
Ok. It worked and my phone is back, the problem is now my brothers phone keeps popping up a message on his home screen saying, "Unfortunately, TouchWiz home has stopped.", and "Unfortunately, Google Services Framework has stopped", and other messages over and over and he can't do anything after installing TWRP. I've tried rebooting, and force stopping and clearing cache of Google Services and TouchWiz but nothing worked
IYaWonaRoo said:
Ok. It worked and my phone is back, the problem is now my brothers phone keeps popping up a message on his home screen saying, "Unfortunately, TouchWiz home has stopped.", and "Unfortunately, Google Services Framework has stopped", and other messages over and over and he can't do anything after installing TWRP. I've tried rebooting, and force stopping and clearing cache of Google Services and TouchWiz but nothing worked
Click to expand...
Click to collapse
You have to factory reset. I don't know how you're gonna do it but that's the only way to get out of it otherwise you might have been doing something else other than installing TWRP and broke something. I suggest you restore to stock and try again. If you didn't make a back up, you might be bricked unless you flash the stock firmware with a computer
savagevegeta said:
You have to factory reset. I don't know how you're gonna do it but that's the only way to get out of it otherwise you might have been doing something else other than installing TWRP and broke something. I suggest you restore to stock and try again. If you didn't make a back up, you might be bricked unless you flash the stock firmware with a computer
Click to expand...
Click to collapse
Thank you so much for your help! My phone is back and luckily my brother had a backup so we fixed his phone and I rooted with Magisk which apparently I needed a micro SD card because my internal storage showed as 0mb and tried everything to fix it ,which is why I was in this mess in the first place, then I finally decided to buy an SD card and it worked!
IYaWonaRoo said:
Thank you so much for your help! My phone is back and luckily my brother had a backup so we fixed his phone and I rooted with Magisk which apparently I needed a micro SD card because my internal storage showed as 0mb and tried everything to fix it ,which is why I was in this mess in the first place, then I finally decided to buy an SD card and it worked!
Click to expand...
Click to collapse
The steps to fix storage 0mb are clearly posted in the TWRP thread.
ashyx said:
The steps to fix storage 0mb are clearly posted in the TWRP thread.
Click to expand...
Click to collapse
I have tried manually mounting, format data, wiping system, cache, and data one by one, changing the File Systems one by one, and alot more. NOTHING WORKED. However every youtube video that I have seen about rooting my exact phone with twrp, all had and used micro SD cards! I tried avoiding buying one but every time I try to fix it any other way it ends up either not doing anything or screwing up my device. Once savagevegeta helped me out of the mess I caused by trying to fix the 0mb I decided screw it, no other method worked so might as well try buying a SD card, and guess what happened, IT WORKED! And I realized why every single guide and yt video used micro SD cards for my model.
IYaWonaRoo said:
I have tried manually mounting, format data, wiping system, cache, and data one by one, changing the File Systems one by one, and alot more. NOTHING WORKED. However every youtube video that I have seen about rooting my exact phone with twrp, all had and used micro SD cards! I tried avoiding buying one but every time I try to fix it any other way it ends up either not doing anything or screwing up my device. Once savagevegeta helped me out of the mess I caused by trying to fix the 0mb I decided screw it, no other method worked so might as well try buying a SD card, and guess what happened, IT WORKED! And I realized why every single guide and yt video used micro SD cards for my model.
Click to expand...
Click to collapse
I guarantee you're doing it incorrectly. See my TWRP thread for correct instructions to mount data.
ashyx said:
I guarantee you're doing it incorrectly. See my TWRP thread for correct instructions to mount data.
Click to expand...
Click to collapse
I probably was doing it wrong lol. But its fixed now so dont worry
IYaWonaRoo said:
I probably was doing it wrong lol. But its fixed now so dont worry
Click to expand...
Click to collapse
Your data partition will still be unmountable and remain 0mb, which means you are unable to make a backup.
However if you're happy with it in that state...
Re: bootloop
have you tried grabbing the no verity/encrypt form the rooting forum, this solves seandroid problem
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.