Related
Hey,
Rooted my Galaxy Tab plus, then backed it up with TB, then tried to transfer the backup to the external sd... which didn't work. I then very precisely (I thought) followed the instructions for creating permissions to write to the external sd, and as per those instructions, rebooted.
And so my Tab has. Rebooted, and rebooted, and rebooted, and rebooted.
I've got it in recovery mode at the moment... but does anyone know how to get this thing out of circular reboot mode? I'm leery of doing a factory reset from recovery until I know if that will have the desired effect--mainly, getting me back into my Tab. I have the stock firmware and ODIN, if that's what's needed. I just need some advice on which is the best to try.
Or, if there's an altogether different solution, then please share...
This may not be useful to solve your problem. However, FYI,...
I was able to applied the permission mod previously, and afterwards, I did a factory reset. It did not remove the permission mod that I applied. That is, after the reset, it was still able to write the the external SD even though all my data and apps were gone.
So chances are the factory reset is not going to solve your problem.
factory reset doesn't mess with the system partition - it basically just wipes the /data partition. So it won't fix your problem.
If you have ODIN, just find a replacement image and re-image the device.
garyd9 said:
factory reset doesn't mess with the system partition - it basically just wipes the /data partition. So it won't fix your problem.
If you have ODIN, just find a replacement image and re-image the device.
Click to expand...
Click to collapse
I initially downloaded the stock firmare for the US version, after discovering for myself that doing a factory reset from it's semi-bricked state did no good. The original firmare download was somehow incomplete; it reached an "unexpected end" while extracting and so would not work in ODIN. Then my Tab wouldn't connect to the computer I was using at all.
Fortunately, I was able to re-download the firmware and use ODIN on another computer, so I was able to get back to stock. Even after that, however, I had to do a factory reset; for some reason, my Tab downloaded the first update from Samsung, but would not make the leap to LA3. Once I did the factory reset, though, all was well.
Then, of course, I immediately re-rooted and manually made the changes that let me write to the external sd--correctly, this time. No trouble at all on reboot.
Thank God.
Hi All,
I did an upgrade to 5.1 (LMY47I) on my Nexus 5 and started facing some strange issues and have no clue on how to resolve them. Before the upgrade I had the following config:
Recovery: TWRP
Root status: Rooted
ROM: Stock 5.0 LRX22C
I used following method for the upgrade: http://forum.xda-developers.com/goo...e-update-rooted-device-to-5-1-lmy47d-t3050789
It was successful but post that I came across few issues as below:
1. Power button functionality was erratic. Sometimes it would lock my mobile but at other times it was locking and waking up my phone immediately. At times "Power Off" popup was also showing up. While I tried to figure out reason for that, trying power button multiple times, my phone rebooted and started the "Optimising Apps" sequence once again. It happened again a couple of times and so I decided to try out factory reset (since I hadn't done that after upgrading).
2. I did a factory rest from Settings. After factory reset, apps and other settings were gone but I noticed that user data in the storage was intact. I guess that also gets removed on a factory reset. Am I wrong on this one?
3. I wanted to install Cerberus as a system app and so I downloaded its zip from the website and flashed using recovery. I was surprised to see that the app wasn't showing after booting up. I tried couple of times more but got no success. So, I decided to install it from Play store and convert to system app using Link2SD. When I tried doing that, Link2SD gave me an error saying "/system: not enough storage space". I tried converting few other apps but got same error. Any thoughts on what could be going on here?
Thanks,
Anurag
crypticlight said:
Hi All,
I did an upgrade to 5.1 (LMY47I) on my Nexus 5 and started facing some strange issues and have no clue on how to resolve them. Before the upgrade I had the following config:
Recovery: TWRP
Root status: Rooted
ROM: Stock 5.0 LRX22C
I used following method for the upgrade: http://forum.xda-developers.com/goo...e-update-rooted-device-to-5-1-lmy47d-t3050789
It was successful but post that I came across few issues as below:
1. Power button functionality was erratic. Sometimes it would lock my mobile but at other times it was locking and waking up my phone immediately. At times "Power Off" popup was also showing up. While I tried to figure out reason for that, trying power button multiple times, my phone rebooted and started the "Optimising Apps" sequence once again. It happened again a couple of times and so I decided to try out factory reset (since I hadn't done that after upgrading).
2. I did a factory rest from Settings. After factory reset, apps and other settings were gone but I noticed that user data in the storage was intact. I guess that also gets removed on a factory reset. Am I wrong on this one?
3. I wanted to install Cerberus as a system app and so I downloaded its zip from the website and flashed using recovery. I was surprised to see that the app wasn't showing after booting up. I tried couple of times more but got no success. So, I decided to install it from Play store and convert to system app using Link2SD. When I tried doing that, Link2SD gave me an error saying "/system: not enough storage space". I tried converting few other apps but got same error. Any thoughts on what could be going on here?
Thanks,
Anurag
Click to expand...
Click to collapse
1- Possibly hardware (power key) issue
2- Factory reset from Android OS *should* erase all user data.
3- Its just that, /system does not have enough free space to put more apps in there. Common issue after Lollipop. Remove some other app from /system, such as Maps, for example, to free up some more space. Be reminded that once you start messing with /system, this will (or might) cause issues with OTA updates.
So I managed to tackle (or at least figured the reason) for all the issues I was having:
1- Yes, there is some issue with the power key. ? But the other issue of optimising apps loop was because I did not do a clean install which disappeared when I did the factory reset after that.
2- After doing some reading on the Internet, I came to know that stock recovery cleans the user data but twrp doesn't by default. Since I had twrp, it just removed apps and settings but retained other data. In order to do a clean install I flashed stock LMY47I again including recovery, userdata etc. (used flash-all.bat). This removed everything from storage and made my phone as good as a new one (software wise).
3- Yes, it was the issue with storage space and was a surprise for me. Thanks for clarifying on that. Before I did a clean install, I tried removing couple of system apps and was able to install cerberus after that via recovery too. However, clean install solved everything.. ☺
Sent from my Nexus 5 using XDA Free mobile app
Ill try to be as descriptive as possible
Zopo ZP820 running 4.2.2
Phone worked fine the other day, went to use it yesterday morning, kept saying all running processes forced quit over and over, all google services, etc.
If i reboot the phone, it keep showing the same 4 Gmail emails, the same 4 text messages. If i go in and physically delete all of the emails and text messages, they are gone. If i reboot the phone, they all come back.
Also went in and uninstalled every single app on phone that was allowable, basically it went back to stock apps, even uninstalled all updates to all google services, etc.
Reboot the phone, everything is back to the way it was, apps and all, and this is after removing the SD card and powering off and rebooting.
Tried to do a factory reset from the settings screen, it reboots into recovery mode, the only options i had were to wipe cache and reset data/cache, when done, i reboot, and yet again it goes back to the same exact way.
It is almost as if the entire phone restores itself every reboot to the same setup.
Also tried using newest SP Flash Tools with 3 different versions of the ROM for my phone, the original stock one, the updated stock one and a custom MIUI one. I go thru the entire process for the two stock ones, it says it formatted and reflashed, but reboot again and it is back to same one that is corrupt.
If i try to use the MIUI one using the recovery option holding power and vol down, when i choose the zip file for the MIUI, it says installation aborted.And what is ieven more odd is that if i reinstall all of the programs or even new apps, if i reboot they are all gone as if they were never installed.
Is there a way that the phone can be totally wiped so that no trace of any files on the phone exist at all? in SP Tools there was an auto format and manual format i did both, but got the same results
Any help would be greatly appreciated
XDA Visitor said:
Ill try to be as descriptive as possible
Zopo ZP820 running 4.2.2
Phone worked fine the other day, went to use it yesterday morning, kept saying all running processes forced quit over and over, all google services, etc.
If i reboot the phone, it keep showing the same 4 Gmail emails, the same 4 text messages. If i go in and physically delete all of the emails and text messages, they are gone. If i reboot the phone, they all come back.
Also went in and uninstalled every single app on phone that was allowable, basically it went back to stock apps, even uninstalled all updates to all google services, etc.
Reboot the phone, everything is back to the way it was, apps and all, and this is after removing the SD card and powering off and rebooting.
Tried to do a factory reset from the settings screen, it reboots into recovery mode, the only options i had were to wipe cache and reset data/cache, when done, i reboot, and yet again it goes back to the same exact way.
It is almost as if the entire phone restores itself every reboot to the same setup.
Also tried using newest SP Flash Tools with 3 different versions of the ROM for my phone, the original stock one, the updated stock one and a custom MIUI one. I go thru the entire process for the two stock ones, it says it formatted and reflashed, but reboot again and it is back to same one that is corrupt.
If i try to use the MIUI one using the recovery option holding power and vol down, when i choose the zip file for the MIUI, it says installation aborted.And what is ieven more odd is that if i reinstall all of the programs or even new apps, if i reboot they are all gone as if they were never installed.
Is there a way that the phone can be totally wiped so that no trace of any files on the phone exist at all? in SP Tools there was an auto format and manual format i did both, but got the same results
Any help would be greatly appreciated
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
First, please create an account so you can post in other forums.
There's not much information on your device here on XDA but you may post your question here:
http://forum.xda-developers.com/showthread.php?t=2257421
The experts in that thread may be able to help.
Good luck!
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.