Related
Hello!
I am sorry if this is the incorrect place to post, but I have a very annoying issue with my OnePlus One!
A few days ago I took the OTA update from Android 4.4.4 all the way to 5.1.1. However, there are quite a few bugs with this version, and the "Material UI" is seriously getting on my nerves so I would like to revert back to my previous version. This should be doable because I performed a Nandroid backup with TWRP before updating the phone. My backup is saved on a USB stick which I connect to the phone via a USB OTG cable, which is perfectly mountable in the Recovery.
My phone is rooted and WAS running TWRP Recovery before I upgraded to Lollipop, this replaced TWRP with Cyanogens stock. When I re-rooted my phone I had to reinstall a custom recovery. For some reason, ADB installing TWRP was just not working (No errors, it just didnt install no matter what) so I opted to try a CWM recovery which did the trick.
Now my issue is that my recovery is unable to mount /sdcard which prevents it from performing backups or restores.
I could really use some help here.
Did you update your backup (TWRP?) as well? What version of it are you on?
JeffDC said:
Did you update your backup (TWRP?) as well? What version of it are you on?
Click to expand...
Click to collapse
I am not sure what you mean by updating the backup. The backup is backed up and left in the state it was when I took it, that is to say Android 4.4.4 and the version of TWRP (The date I installed TWRP the first time) is mid February 2015.
The phones recovery right now is PhilzRecovery which as far as I understand is CWM. Latest version.
Try installing twrp from the CWM recovery.. And before restoring the phone from nandroid try installing the clean stock rom at 4.4.4 and then do the nandroid restore.
Sent from OPO using Tapatalk
Press on thanks if I helped you
ashuthosh.heda said:
Try installing twrp from the CWM recovery.. And before restoring the phone from nandroid try installing the clean stock rom at 4.4.4 and then do the nandroid restore.
Sent from OPO using Tapatalk
Press on thanks if I helped you
Click to expand...
Click to collapse
And to do this, I would just drop the .img for TWRP into my phones storage and chose it from inside the recovery? Would this really work? It might be my inexperience, but it sounds somewhat risky.
NodCom said:
And to do this, I would just drop the .img for TWRP into my phones storage and chose it from inside the recovery? Would this really work? It might be my inexperience, but it sounds somewhat risky.
Click to expand...
Click to collapse
Don't know if CWM recovery supports installing img. Twrp supports img flashing. Check the features of CWM recovery and proceed.
Sent from my A0001 using Tapatalk
ashuthosh.heda said:
Don't know if CWM recovery supports installing img. Twrp supports img flashing. Check the features of CWM recovery and proceed.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Well... I am not sure how I just managed this, but I was tinkering about inside my TWRP application and tried the "Install TWRP recovery" setting a second time (I tried it before making this thread, the first time it failed), it actually was successful because it booted into TWRP. From here I selected the TWRP-backup I kept and it installed it successfully (With one note, that it during the installation said something among the lines of "Restoring backup without deleting /data/media" or something like that. The phone rebooted itself after it finished updating, and the old Cyanogen/OPO bootanimation plays. But at login (My device is encrypted since long) it tells me my password is incorrect?!
How could this to happen? I've only ever used a single password (numbers only) for my phone encryption. This is very odd.
NodCom said:
Well... I am not sure how I just managed this, but I was tinkering about inside my TWRP application and tried the "Install TWRP recovery" setting a second time (I tried it before making this thread, the first time it failed), it actually was successful because it booted into TWRP. From here I selected the TWRP-backup I kept and it installed it successfully (With one note, that it during the installation said something among the lines of "Restoring backup without deleting /data/media" or something like that. The phone rebooted itself after it finished updating, and the old Cyanogen/OPO bootanimation plays. But at login (My device is encrypted since long) it tells me my password is incorrect?!
How could this to happen? I've only ever used a single password (numbers only) for my phone encryption. This is very odd.
Click to expand...
Click to collapse
I guess it's a side effect of restoring up a backup of 4.4.4 on lollipop. Try factory reset from twrp and then flash the backup. I would still suggest to first install the stock firmware of 4.4.4 and flash it and then do a restore of 4.4.4.
Sent from OPO using Tapatalk
Currently on Resurrection Remix
Thank me if I helped you.
Also make sure you are using the most recent version of TWRP, as it provides better 'outs' and reliability for newer OP OS versions.
A few questions about encryption on the S7:
Some threads, e.g., TWRP, refer to "Samsung encryption". Does the S7 use some sort of proprietary Samsung encryption, or does it use the standard Android encryption?
Since I have now disabled encryption after installing TWRP, can I re-enable it? If so, how?
Would FlashFire allow me to flash ROMs with encryption still enabled?
Thanks in advance.
dildano said:
A few questions about encryption on the S7:
Some threads, e.g., TWRP, refer to "Samsung encryption". Does the S7 use some sort of proprietary Samsung encryption, or does it use the standard Android encryption?
Since I have now disabled encryption after installing TWRP, can I re-enable it? If so, how?
Would FlashFire allow me to flash ROMs with encryption still enabled?
Thanks in advance.
Click to expand...
Click to collapse
1. Simply put, the method in which Samsung decrypts encrypted data isn't known
2. You can enable encryption but you must start from scratch. (As far as I am aware anyways). Means you must flash stock ROM in ODIN.
3. Not sure. You can certainly flash zips that modify /system. You can also use TWRP as long as you don't need to mount data. Switching ROM normally means a standard factory reset but if you are encrypted you can't use TWRP to factory reset and I am not sure if FlashFire can do it either.
Galactus said:
1. Simply put, the method in which Samsung decrypts encrypted data isn't known
2. You can enable encryption but you must start from scratch. (As far as I am aware anyways). Means you must flash stock ROM in ODIN.
3. Not sure. You can certainly flash zips that modify /system. You can also use TWRP as long as you don't need to mount data. Switching ROM normally means a standard factory reset but if you are encrypted you can't use TWRP to factory reset and I am not sure if FlashFire can do it either.
Click to expand...
Click to collapse
2. do you have to really start from the scratch?
http://forum.xda-developers.com/galaxy-s7/how-to/how-to-encrypt-device-custom-rom-knox-1-t3392301
3. is factory reset not just a kind of a wipe? why cant twrp just format the encrypted partitions?
I spent also several days to fully customize my S7 (cfw S7 debloated) and i am quite happy yet.
But if I lost once a phone long time ago.. So encryption is a must, root too.
I would accept definetely a non-working TWRP, if I could get an encryption?
any advices?
thx.
tefole said:
2. do you have to really start from the scratch?
http://forum.xda-developers.com/galaxy-s7/how-to/how-to-encrypt-device-custom-rom-knox-1-t3392301
3. is factory reset not just a kind of a wipe? why cant twrp just format the encrypted partitions?
I spent also several days to fully customize my S7 (cfw S7 debloated) and i am quite happy yet.
But if I lost once a phone long time ago.. So encryption is a must, root too.
I would accept definetely a non-working TWRP, if I could get an encryption?
any advices?
thx.
Click to expand...
Click to collapse
Yep, once you disable encryption in TWRP and flash the dm-verity zip, the option to encrypt the phone won't even be available in settings. In the rare case that it is, it will always fail.
Since you want root and encryption, it is pretty simple.
Flash stock rom in ODIN (Backup, backup, backup anything valuable)
Obtain root using CF-Auto Root method
Install TWRP, allow modifications, don't wipe /data
You can only flash zips from external SD card. Internal storage will be unavailable in TWRP
I did a make backups with TWRP and TitaniumBackup.
May I ask some more questions, i do want to understand the procedure.
Galactus said:
Flash stock rom in ODIN (Backup, backup, backup anything valuable)
Click to expand...
Click to collapse
I guess the stock ROM is already encrypted - is that the reason why TWRP doesnt have access to /data (as well to the internal /sdcard) till the encryption is disabled?
Obtain root using CF-Auto Root method
Click to expand...
Click to collapse
After flashing stock the bootloader is locked again, so I do have to unlock the "OEM unlock" per developer settings again? The phone wont be wiped afterwards?
Install TWRP, allow modifications, don't wipe /data
Click to expand...
Click to collapse
May i recover/restore here a formerly per TWRP backuped ROM? I guess, this want be possible, hence TWRP doesnt has access to /data, nor to /sdcard?!
Which partitions I am allowed to restore, respectively is there a chance to recovery somehow the TWRP backup (it was soo much work).
Or can i disable encryption and enable it again, after restore?
You can only flash zips from external SD card. Internal storage will be unavailable in TWRP
Click to expand...
Click to collapse
After everything went well, I am going to encrypt the ext-sdcard too. I guess, TWRP will be useless then...
tefole said:
I did a make backups with TWRP and TitaniumBackup.
May I ask some more questions, i do want to understand the procedure.
I guess the stock ROM is already encrypted - is that the reason why TWRP doesnt have access to /data (as well to the internal /sdcard) till the encryption is disabled?
After flashing stock the bootloader is locked again, so I do have to unlock the "OEM unlock" per developer settings again? The phone wont be wiped afterwards?
May i recover/restore here a formerly per TWRP backuped ROM? I guess, this want be possible, hence TWRP doesnt has access to /data, nor to /sdcard?!
Which partitions I am allowed to restore, respectively is there a chance to recovery somehow the TWRP backup (it was soo much work).
Or can i disable encryption and enable it again, after restore?
After everything went well, I am going to encrypt the ext-sdcard too. I guess, TWRP will be useless then...
Click to expand...
Click to collapse
Once you flash the stock ROM, the phone is encrypted before first boot
Once you OEM Unlock, it stays that way unless you attempt to re-lock it. Once you flash a stock ROM and go to developer settings, you'll see OEM Unlock is still on
Encrypted device = No restoring of any kind in TWRP, that is the trade off. Some people use FlashFire to back up and restore. I tried once a while back and it didn't work. Others seem to be ok
If external sd is encrypted also, then your only chance is to use FlashFire. TWRP is basically useless
Galactus said:
Once you flash the stock ROM, the phone is encrypted before first boot
Once you OEM Unlock, it stays that way unless you attempt to re-lock it. Once you flash a stock ROM and go to developer settings, you'll see OEM Unlock is still on
Encrypted device = No restoring of any kind in TWRP, that is the trade off. Some people use FlashFire to back up and restore. I tried once a while back and it didn't work. Others seem to be ok
If external sd is encrypted also, then your only chance is to use FlashFire. TWRP is basically useless
Click to expand...
Click to collapse
Thx for your reply
After I flashed stock and finally customized my installation, would this be safety feature to relock the OEM? Is a relocking wiping also the whole phone or only the unlocking?
So that means, that if go through this instructeres, i cant flash any CFW, neither i cant restore my TWRP backup?
Thats a pitty.
tefole said:
Thx for your reply
After I flashed stock and finally customized my installation, would this be safety feature to relock the OEM? Is a relocking wiping also the whole phone or only the unlocking?
So that means, that if go through this instructeres, i cant flash any CFW, neither i cant restore my TWRP backup?
Thats a pitty.
Click to expand...
Click to collapse
If you try to relock OEM, your device won't boot lol. I learned that the hard way months ago. Had to start from scratch.
What custom firmware are you trying to flash? If you mean custom ROMs then theoretically speaking you should be able to flash them using FlashFire.
Thank you for the hint - this will me spare the fate
I chose S7_extreme_debloated from @Battlehero.
I am quite happy with that CFW and i thought, i can install my apps and customize the system and start the encryption - didnt worked.
So, I will begin from the scratch too. It would be great, if I could start with this CFW after, flashing stock.
My problem is very simple at its core and I find myself resorting to extreme solutions such as factory reset to solve it. However, I am okay with this. I would like to know the best way to unroot and factory reset my Note 4 SM-N910U.
What follows is the original story and my attempts to fix it. It's rather long, so if you would like to skip this section there is a tl;dr at the end.
Originally, I had found myself unable to login to the app Snapchat because they had gone to extreme lengths to lock out rooted users (an infamous fact on online discussions).
A popular solution for this would've been to install the Xposed Framework with RootCloak to hide Root from Snapchat - this is where my first problem came along.
My Android phone is encrypted.
This means that I could not use TWRP to flash the Xposed Framework zip (because TWRP for my device does not support encryption, thus could not read /data directory.)
I tried using FlashFire to skip recovery and got the same result - /data encrypted.
I tried to flash with CWM to see if it would support decryption of /data partition, but CWM isn't even compatible with my device.
At this point I was running out of things to try (I had been after this problem for about three days) and I decided to just kick the bucket, unroot and factory reset, because apparently the only way to undo data encryption on Android is to delete everything .
Apparently, even this would be a challenge. To factory reset a rooted device, you apparently need a stock ROM.
I tried looking for stock ROMs for SM-N910U online but the sites that came up (there were about 9 hits on Google for my baseband) all seemed fake and potentially harmful.
Even then, I don't know how I would flash the ROM since my TWRP doesn't work but that's the least of my worries at the moment .
I'd be extremely grateful if anyone could offer any potential pointers on where to download a safe stock ROM for my device and how to flash this ROM when I have no working TWRP (since my /data partition is, again, encrypted).
It seems a bit like a paradox - to remove data encryption you need a TWRP stock flash, but for a TWRP stock flash you need to remove data encryption.
Please do help... thank you in advance.
TL;DR
- tried to install xposed to hide root.
- found out that i can't flash any roms from recovery, because my recovery (twrp) doesn't support android disk encryption.
- found out that to remove encryption, i need to factory reset.
- i can't factory reset, because I need a stock ROM and I don't know where to find said stock ROM.
- also, how would i even flash this rom without a working recovery (again, the recovery doesn't work because full disk encryption).
Device Details:
Phone: Samsung Galaxy Note 4Model: SM-N910UAndroid version: 6.0.1 MarshmallowBaseband version: N910UXXU1DPL1
qnxo said:
My problem is very simple at its core and I find myself resorting to extreme solutions such as factory reset to solve it. However, I am okay with this. I would like to know the best way to unroot and factory reset my Note 4 SM-N910U.
What follows is the original story and my attempts to fix it. It's rather long, so if you would like to skip this section there is a tl;dr at the end.
Originally, I had found myself unable to login to the app Snapchat because they had gone to extreme lengths to lock out rooted users (an infamous fact on online discussions).
A popular solution for this would've been to install the Xposed Framework with RootCloak to hide Root from Snapchat - this is where my first problem came along.
My Android phone is encrypted.
This means that I could not use TWRP to flash the Xposed Framework zip (because TWRP for my device does not support encryption, thus could not read /data directory.)
I tried using FlashFire to skip recovery and got the same result - /data encrypted.
I tried to flash with CWM to see if it would support decryption of /data partition, but CWM isn't even compatible with my device.
At this point I was running out of things to try (I had been after this problem for about three days) and I decided to just kick the bucket, unroot and factory reset, because apparently the only way to undo data encryption on Android is to delete everything .
Apparently, even this would be a challenge. To factory reset a rooted device, you apparently need a stock ROM.
I tried looking for stock ROMs for SM-N910U online but the sites that came up (there were about 9 hits on Google for my baseband) all seemed fake and potentially harmful.
Even then, I don't know how I would flash the ROM since my TWRP doesn't work but that's the least of my worries at the moment .
I'd be extremely grateful if anyone could offer any potential pointers on where to download a safe stock ROM for my device and how to flash this ROM when I have no working TWRP (since my /data partition is, again, encrypted).
It seems a bit like a paradox - to remove data encryption you need a TWRP stock flash, but for a TWRP stock flash you need to remove data encryption.
Please do help... thank you in advance.
TL;DR
- tried to install xposed to hide root.
- found out that i can't flash any roms from recovery, because my recovery (twrp) doesn't support android disk encryption.
- found out that to remove encryption, i need to factory reset.
- i can't factory reset, because I need a stock ROM and I don't know where to find said stock ROM.
- also, how would i even flash this rom without a working recovery (again, the recovery doesn't work because full disk encryption).
Device Details:
Phone: Samsung Galaxy Note 4Model: SM-N910UAndroid version: 6.0.1 MarshmallowBaseband version: N910UXXU1DPL1
Click to expand...
Click to collapse
Go to Sammobile .com or samsung-updates .com this use your model number to search for your stock firmware, find the firmware for your region then flash that via Odin.
Sent from my SM-S903VL using Tapatalk
Would I first need to "wipe" anything in TWRP?
qnxo said:
Would I first need to "wipe" anything in TWRP?
Click to expand...
Click to collapse
It wouldn't hurt
Sent from my SM-S903VL using Tapatalk
My XT1540/rooted/stock 6.0 ROM/ stock recovery now has an update available. I assume I can not accept this system update, even if I un-root my device. I do have a pre-rooted TWRP back up. I can reload that image, but my concern is the best way to get all my apps and data reloaded. I do have TB backups, but I thought that may not be a good option after system update. I am looking for advise how to proceed getting the latest system update and preserving all my current apps and data.
No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.
acejavelin said:
No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.
Click to expand...
Click to collapse
Thanks. I have read conflicting information on the use of Titanium Backup, and that was my main reason for my post. My understanding of your reply is that TB would not be a recommended choice to restore apps&data (using either update.zip or batch mode) and that I have an 80% chance of restoring user apps and data by flashing the /data partition from my pre-OTA TWRP backup. And yes, I will make a pre-rooted backup prior to rooting or restoring apps.
I never heard of Magisk and will read more. In the mean time I will stick with SuperSU unless there is strong advise to go with Magisk.
MrTooPhone said:
Thanks. I have read conflicting information on the use of Titanium Backup, and that was my main reason for my post. My understanding of your reply is that TB would not be a recommended choice to restore apps&data (using either update.zip or batch mode) and that I have an 80% chance of restoring user apps and data by flashing the /data partition from my pre-OTA TWRP backup. And yes, I will make a pre-rooted backup prior to rooting or restoring apps.
I never heard of Magisk and will read more. In the mean time I will stick with SuperSU unless there is strong advise to go with Magisk.
Click to expand...
Click to collapse
I dislike TiBU... It is best to reinstall from scratch each time if possible, if not, this is a simple security update to TWRP should suffice.
Magisk is good, and it appears to be the root method most ROMs are going to because with Magisk Hide and a few tweaks that are built in, the device can still pass SafetyNet API checks, and there is no special process for systemless installing (it is the only way it can be done with Magisk). But if you are on SuperSU now and want to restore the data partition, do NOT switch that way... Get clean ROM and flash Magisk then install Magisk Manager. It has it's own community here: https://forum.xda-developers.com/apps/magisk
I am not saying Magisk is superior, but it is quite versatile and most ROMs seem to be switching to it so devices can pass SafetyNet checks.
I was also thinking this would be simple. Pleasant surprise after almost a year and a half to get a security update. So I uninstalled SuperSU (Tried Full Unroot option & it failed, so then just uninstalled the app.....Looks like I may still be rooted), re-installed the stock recovery, and with absolutely no other modifications to this phone, performed the update. So it failed. I thought I was able to do this on my Nexus 4, but that was a while back, and I always did it with a file, not OTA; maybe that was just OS update, who knows. I was just looking for some security peace of mind while waiting for Nougat to become a bit more stable. If I am going to have to go through hoops to do this, then I guess I will just wait; not going to go through this twice. Besides, will it be another year for the next security update; heck, they are already 1 or 2 months behind already.
The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.
Rohi09 said:
The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.
Click to expand...
Click to collapse
Oh well. On a side note, always grateful for making Nandroid backups before I start playing around with anything though. Things were acting up after haphazardly trying various SuperSU options, so I had to do a restore.
These constant OTA update messages every few minutes that I have to keep canceling are brutal! I might have to install an app to kill them.
Rohi09 said:
The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.
Click to expand...
Click to collapse
Are you saying OTA updates can be flashed successfully without unrooting.
MrTooPhone said:
Are you saying OTA updates can be flashed successfully without unrooting.
Click to expand...
Click to collapse
that's the idea, I have never tried it on moto g 2015 though. As far as I know every root solution had its own Uninstaller. which root interface do you use? magisk or supersu?
Rohi09 said:
that's the idea, I have never tried it on moto g 2015 though. As far as I know every root solution had its own Uninstaller. which root interface do you use? magisk or supersu?
Click to expand...
Click to collapse
I have SuperSU. It would be great to flash an OTA over my current system, but I have heard many reports including @pjc123 above where it did not work.
All my searches resulted in suggestions in going back to stock, accept OTA, then use TB or some other similar program to restore saved apps & data. Tomorrow I will try @acejavelin 's above suggested method of flashing the /data partition. If that does not work, I will try TB. I will report my progress.
MrTooPhone said:
I have SuperSU. It would be great to flash an OTA over my current system, but I have heard many reports including @pjc123 above where it did not work.
All my searches resulted in suggestions in going back to stock, accept OTA, then use TB or some other similar program to restore saved apps & data. Tomorrow I will try @acejavelin 's above suggested method of flashing the /data partition. If that does not work, I will try TB. I will report my progress.
Click to expand...
Click to collapse
you can flash unsu zip or magisk Uninstaller and try to install ota via flashfire, won't hurt trying, might save you some time.
acejavelin said:
No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.
Click to expand...
Click to collapse
Another dumb question, I am in the process of installing OTA. When I loaded the pre-root rom, I did not see any option to clear clear caches. I did see a wipe data and cache option which I understand to be a factory reset. I know I have seen it before but can't find it, so where do I clear cache after restoring data partition?
MrTooPhone said:
Another dumb question, I am in the process of installing OTA. When I loaded the pre-root rom, I did not see any option to clear clear caches. I did see a wipe data and cache option which I understand to be a factory reset. I know I have seen it before but can't find it, so where do I clear cache after restoring data partition?
Click to expand...
Click to collapse
Another simple Google question...
Open TWRP, go to Wipes - Advanced, and select Cache and Dalvik cache (a misnomer today, it should be called ART cache) and swipe to wipe, then reboot.
Thanks to @acejavelin recommendations, I have successfully applied the latest system update to my XT1540. My steps were as follows:
Booted to TWRP (3.0.2-r5.img)
restored original pre-rooted ROM
rebooted, accepted system updates
backed up new pre-rooted ROM
installed SuperSU 2.62-3, rebooted
updated SuperSU to 2.79 via Playstore
restored /data partition from last saved rooted ROM
wiped Dalvik/ART Cache
Reboot system
took a while, a couple of minutes on “Hand stitched by Peter Crawly”, several minutes optimizing apps. The phone booted succesfully then I got an error message the update failed (which I hit OK) But looking at about phone, latest security patch is listed. Phone looks configured (apps, data, configuration) exactly as it was prior to the update.
Rebooted phone, all still seems fine.
Hello, how do I restore original pre-rooted ROM? When I made the backup I got a folder with 6 files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win
system.ext4.win.md5
system.info
None of them seems to be the .img file
bradmoss said:
Hello, how do I restore original pre-rooted ROM? When I made the backup I got a folder with 6 files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win
system.ext4.win.md5
system.info
None of them seems to be the .img file
Click to expand...
Click to collapse
Your are not going to see an img file. Once booted into TWRP, select Restore, navigate and select your original ROM. Those files you have listed are within the restoration directory that you select with TWRP. Just select the directory with TWRP.
Bad news, I could restore pre-TRWP image using that folder and aplied the update.
But now I am in a loop, it tries to install (again) the update and then boots to TWRP
Is there any way out of this loop?
Thanks!
no idea? Am I the sad owner of a bricked phone?
bradmoss said:
no idea? Am I the sad owner of a bricked phone?
Click to expand...
Click to collapse
You could try a factory reset if you're not worried about losing your data. A factory reset solves most of the problems, though I'm a little doubtful because a factory reset won't uninstall the new update (given that it installed in the first place).
bradmoss said:
Bad news, I could restore pre-TRWP image using that folder and aplied the update.
But now I am in a loop, it tries to install (again) the update and then boots to TWRP
Is there any way out of this loop?
Thanks!
Click to expand...
Click to collapse
If it boots to TWRP, sounds like you didn't have a clean pre-root ROM as you did not have stock recovery. Did you try deleting Dalvik and ART cache?
Hello,
I have a rooted Samsung J2 2016. I thought of getting Viper4Android and when I tried to install the drivers it just said drivers installed reboot your phone. I rebooted it 2 times but still it said driver 0.0.0.0 and would ask for permission for updating drivers again. Fed up of this I went to Link2SD app and uninstalled the app. As I had flashed the zip file for Viper, it erased the sound drivers(I think) and I couldnt get any audio through the ear phones so I decided to do a factory reset of the phone by flashing the latest firmware update(This usually removes all apps, TWRP and root from my phone). After I did the factory reset I noticed that all the apps that I had before were still thereconfused I ignored it and plugged in my headphones only to find a complete loss in bass. I tried to tweak the inbuilt equalizer but nothing came out of it. After restarting, bass would enable for a few seconds and then it would disable again. I dont know what to do now. How can I get back my deleted drivers(if they got deleted)?
P.S. I had taken a complete backup but it got erased from the SD card after I formatted it as portable storage( I had it enabled for adoptable storage through root essentials. This might be the reason why the phone didnt factory reset) :crying:
Sorry for the long post. Im a beginner at this. Any help would be appreciated. Thank you
Edit- I tried different earphones and different music players but no success
darshan1504 said:
Hello,
I have a rooted Samsung J2 2016. I thought of getting Viper4Android and when I tried to install the drivers it just said drivers installed reboot your phone. I rebooted it 2 times but still it said driver 0.0.0.0 and would ask for permission for updating drivers again. Fed up of this I went to Link2SD app and uninstalled the app. As I had flashed the zip file for Viper, it erased the sound drivers(I think) and I couldnt get any audio through the ear phones so I decided to do a factory reset of the phone by flashing the latest firmware update(This usually removes all apps, TWRP and root from my phone). After I did the factory reset I noticed that all the apps that I had before were still thereconfused I ignored it and plugged in my headphones only to find a complete loss in bass. I tried to tweak the inbuilt equalizer but nothing came out of it. After restarting, bass would enable for a few seconds and then it would disable again. I dont know what to do now. How can I get back my deleted drivers(if they got deleted)?
P.S. I had taken a complete backup but it got erased from the SD card after I formatted it as portable storage( I had it enabled for adoptable storage through root essentials. This might be the reason why the phone didnt factory reset) :crying:
Sorry for the long post. Im a beginner at this. Any help would be appreciated. Thank you
Edit- I tried different earphones and different music players but no success
Click to expand...
Click to collapse
You probably needed to make sure you had SELinux set to permissive mode, then V4A would probably install the driver and reboot correctly without having to do it again.
You have 2 options:
1) reflash your stock firmware or your custom ROM, whichever one you're using. This will replace what was removed when you flashed V4A zip.
Or
2) enable permissive mode and try V4A again.
Or if you'd like, you can flash your stock or custom ROM just to get things back to a clean start and then try installing V4A again in permissive mode and see if it works right this time.
By the way, when flashing with Odin, it doesn't erase user data unless what you're flashing includes an upgraded/downgraded bootloader. When flashing exactly what you had, it leaves your data intact.
This time, when you flash stock firmware via Odin, boot the device to recovery and factory reset from within recovery, this will wipe user data, then connect to Odin and flash firmware. This should return everything to like it came out of the box.
By the way, in android, the term "factory reset" does not mean flashing stock firmware, that's called "factory restore".
In android, the term factory reset is something completely different, in android, it means wiping user data and leaving only the stock software.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
You probably needed to make sure you had SELinux set to permissive mode, then V4A would probably install the driver and reboot correctly without having to do it again.
You have 2 options:
1) reflash your stock firmware or your custom ROM, whichever one you're using. This will replace what was removed when you flashed V4A zip.
Or
2) enable permissive mode and try V4A again.
Or if you'd like, you can flash your stock or custom ROM just to get things back to a clean start and then try installing V4A again in permissive mode and see if it works right this time.
By the way, when flashing with Odin, it doesn't erase user data unless what you're flashing includes an upgraded/downgraded bootloader. When flashing exactly what you had, it leaves your data intact.
This time, when you flash stock firmware via Odin, boot the device to recovery and factory reset from within recovery, this will wipe user data, then connect to Odin and flash firmware. This should return everything to like it came out of the box.
By the way, in android, the term "factory reset" does not mean flashing stock firmware, that's called "factory restore".
In android, the term factory reset is something completely different, in android, it means wiping user data and leaving only the stock software.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thank you for replying. The problem is that I am running the stock touchwiz samsung ROM so SELinuxModeChanger doesn't work for me. I would like to go with the second option but I can't find any other method to make it permissive. Can you please help me with this? I dont want to do a factory reset cause talking the phone back to how it is will be a real pain and time consuming. Will just flashing the Viper file again do the job in any way?
Droidriven said:
You probably needed to make sure you had SELinux set to permissive mode, then V4A would probably install the driver and reboot correctly without having to do it again.
You have 2 options:
1) reflash your stock firmware or your custom ROM, whichever one you're using. This will replace what was removed when you flashed V4A zip.
Or
2) enable permissive mode and try V4A again.
Or if you'd like, you can flash your stock or custom ROM just to get things back to a clean start and then try installing V4A again in permissive mode and see if it works right this time.
By the way, when flashing with Odin, it doesn't erase user data unless what you're flashing includes an upgraded/downgraded bootloader. When flashing exactly what you had, it leaves your data intact.
This time, when you flash stock firmware via Odin, boot the device to recovery and factory reset from within recovery, this will wipe user data, then connect to Odin and flash firmware. This should return everything to like it came out of the box.
By the way, in android, the term "factory reset" does not mean flashing stock firmware, that's called "factory restore".
In android, the term factory reset is something completely different, in android, it means wiping user data and leaving only the stock software.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Also sir I found an old complete titanium backup on my laptop. So can it have the original drivers? If yes can I restore them using titanium and how?
I am sorry for asking so many questions but listening to music is what I do most of the times and I am feeling guilty for screwing up something that I like the most and that I can not restore it :crying:
darshan1504 said:
Also sir I found an old complete titanium backup on my laptop. So can it have the original drivers? If yes can I restore them using titanium and how?
I am sorry for asking so many questions but listening to music is what I do most of the times and I am feeling guilty for screwing up something that I like the most and that I can not restore it :crying:
Click to expand...
Click to collapse
What you need wouldn't be in a Titanium Backup file unless you backed up system apps and their data.
If you had a TWRP backup from before you installed V4A then you could use that. Otherwise than that, you'll have to flash stock firmware or at least manually reinstall the stock sound app and it's resources.
Best option to be sure you fix it without having to dig through anything is to flash stock firmware and start over and do it correctly the next time.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
What you need wouldn't be in a Titanium Backup file unless you backed up system apps and their data.
If you had a TWRP backup from before you installed V4A then you could use that. Otherwise than that, you'll have to flash stock firmware or at least manually reinstall the stock sound app and it's resources.
Best option to be sure you fix it without having to dig through anything is to flash stock firmware and start over and do it correctly the next time.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
The titanium backup is a complete system backup. I had chosen the backup all apps and system data option in Titanium and when I went through the backup files, I found the Sound Alive files in it. Those files were different from the ones which I currently have. So this is what I have in the end. If this is useful then fine. Otherwise there's no other option left I guess
darshan1504 said:
The titanium backup is a complete system backup. I had chosen the backup all apps and system data option in Titanium and when I went through the backup files, I found the Sound Alive files in it. Those files were different from the ones which I currently have. So this is what I have in the end. If this is useful then fine. Otherwise there's no other option left I guess
Click to expand...
Click to collapse
No, it's not a complete system backup because Titanium Backup can't do a complete system backup, the only part of system it can backup is system apps and their app data, it doesn't backup anything else from system. TWRP can make a complete system backup but Titanium Backup can't.
If you backed up the system apps themselves then yes, you can restore them but I wouldn't restore any of the app data that goes with those system apps.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
No, it's not a complete system backup because Titanium Backup can't do a complete system backup, the only part of system it can backup is system apps and their app data, it doesn't backup anything else from system. TWRP can make a complete system backup but Titanium Backup can't.
If you backed up the system apps themselves then yes, you can restore them but I wouldn't restore any of the app data that goes with those system apps.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I did a factory reset through TWRP and flashed it again. That did the trick. Thank you for all the help