Related
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
frankieGom said:
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
Click to expand...
Click to collapse
I think using Exynos Abuse apk will do the work
http://forum.xda-developers.com/showthread.php?t=2050297
Thanks for the heads up, I'll look into it. But to be clear, that answers question 1, correct?
Sent from my GT-N7105 using xda app-developers app
frankieGom said:
Thanks for the heads up, I'll look into it. But to be clear, that answers question 1, correct?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Yes that's a way to root the device.
Regarding encryption, very few people on xda seem to use it. So for that reason you'll have trouble finding out what works... I do use it though through choice so I can help you a bit.
When you encrypt the device, just consider /data to be off limits to anything not booted fully. That's why it asks you for your key in swedish - it can't see what language is in use until you unlock /data.
You will have issues using recovery with the device, since they can't read /data. You can use an external sd to perhaps load data to the device though.
I believe that TWRP might soon support the Samsung encryption on the device, meaning you could use it as recovery. Once you have a recovery that supports Samsung encryption, you should be able to consider it a fairly normal device.
Just be more cautious to backup your data as it is hard to recover if something goes wrong...
If your using stock rom 4.1.2, exynos abuse method of root will not work. It's been patched
Sent from my GT-N7100 using xda app-developers app
pulser_g2 said:
Yes that's a way to root the device.
Regarding encryption, very few people on xda seem to use it. So for that reason you'll have trouble finding out what works... I do use it though through choice so I can help you a bit.
When you encrypt the device, just consider /data to be off limits to anything not booted fully. That's why it asks you for your key in swedish - it can't see what language is in use until you unlock /data.
You will have issues using recovery with the device, since they can't read /data. You can use an external sd to perhaps load data to the device though.
I believe that TWRP might soon support the Samsung encryption on the device, meaning you could use it as recovery. Once you have a recovery that supports Samsung encryption, you should be able to consider it a fairly normal device.
Just be more cautious to backup your data as it is hard to recover if something goes wrong...
Click to expand...
Click to collapse
Fine, I understand. As long as I have a way to recover my data if I need to wipe I'm okay... I just have to hope Titanium backup gives me that until TWRP can manage encruption on the Note 2.
I'm really waiting for a stock rom that boots in English or French now.
Sent from my GT-N7105 using xda app-developers app
vash_h said:
If your using stock rom 4.1.2, exynos abuse method of root will not work. It's been patched
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Not the case with xxdll1. When was it patched, xxdll4 or xxdll7?
Sent from my GT-N7105 using xda app-developers app
frankieGom said:
Not the case with xxdll1. When was it patched, xxdll4 or xxdll7?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
I am on Stock 4.1.2 and Exynos Abuse did work on my device, it's successfully rooted using the Exynos AbuseAPK on 4.1.2 :good:
OK, now I have been experimenting a bit with backups and upgrade and have trouble restoring my device fully. Let me explain...
I got hold of a TWRP build that seems to handle Samsung encryption fine through one of the TWRP devs (thanks!), so I decided to go back and try to update my device.
Current ROM: N7105XXDLL1_N7105TLADLL1_N7105XXDLK7_HOME.tar (obtained from Samsung Updates)
New ROM: N7105XXDLL7_N7105OLBDLL2_N7105DXDLL1_HOME.tar (obtained from Samsung Updates)
First I performed a complete Titanium Backup on the device and pulled the files to my laptop using ADB.
Then I restarted into TWRP 2.4.0.0 (got a prompt for my password), performed a full backup and pulled the files to the laptop using ADB.
(for some reason, I could not install the new ROM from TWRP (unable to open ZIP), but the ZIP looked OK, as well as after a second download which TWRP since did not like, so I had to use Odin instead).
Next, I flashed DLL7 with Odin. It worked, asked for the password at boot, but the device was unrooted at this point (I expected that).
Then, I flashed CF-Auto-Root-t0lte-t0ltexx-gtn7105.tar from Odin, but the boot up password would not be accepted anymore as I already knew.
Tried to flash DLL7 again from Odin, same thing
Flashed TWRP back on recovery partition, but on startup it would not ask for password anymore and the external sdcard looked empty to it.
I then copied my backup to a different, non encrypted sdcard and could restore from TWRP but the password would still not work after reboot.
I did a factory reset, restored backup, same result.
At this point I decided to factory reset, wipe Dalvik and format /data. The format did the trick and after TWRP restore of my original back up the device booted up, did not ask for password and all my data was there. Except the Exchange account I use for Corporate email wants me to restore encryption in order to work (I expected that too).
Back at DLL1, so I flashed DLL7 again with Odin (OK), rooted the phone, triangled away the flash counter and reflashed TWRP to recovery.
I was where I wanted to be except for one thing: I need to restore Corporate access. But when I let it encryp the phone it does nothing. I let it through the night and nothing). And if I reboot the phone no password is needed at boot time, yet the phone seems to behave as if it thought the device was still encrypted...
I reflashed my original, full, backup (i.e DLL1) succesfully but Exchange still wants to encrypt my device. Isn't restore supposed to restore the encrypted /data I backed up?
At this point I'm left with possibly tryinjg to go back to full factory settings, not use the backup at all, encrypt the device then restore my data from the Titanium backup I made.
Is there a better option?
[edited jan 18 - TWRP/TB behaviour]
My comments apply to encrypted devices only! I am not trying to talk down TWRP or TB here, as they provide splendid performance on non encrypted devices. I have come upon hard time trying to upgrade/restore an encrypted device using thoise tools, that's all
For those considering upgrading & re-rooting encrypted devices, don't!
I am finding the hard way that this is a one way street. At this point, my TWRP made full backup does not restore the device to the expected status. Each time I apply it, subsequent bootup takes several minutes and I end up going through the initial setup procedure. It seems the device for some reasoin goes through a complete reset procedure.
[edit]
Clarification: The TWRP build I use, 2.4.0.0 is an alpha build and I was not current when I restored my backup. I so happens that it was overwriting the encryption header on the partition, which messed things up bad, and had issues writing back the data partition, ending up in a factory reset status!
Using the latest drop as of today (jan 27) I was able to restore my original backup and am now back to my original state. All is well.
[/edit]
Titanium Backup is none better. It keeps telling me that my Android ID has changed, a host of system applications start to fail when I try to restore and generally speaking I have now spent between a good 20 hours trying to simply restore my data.
[edit]
this behaviour is probably linked to encryption. I know for a fact that TB works very well on non encrypted phones. The 20h figure is overall, not just with TB.
[/edit]
The end story is: root before you encrypt, and either don't upgrade or don't re-root if you do! If you do, be prepared for some rough times...
Unless someone has a cleat idea of how to do this properly without losing all your data, that is.
François
frankieGom said:
For those considering upgrading & re-rooting encrypted devices, don't!
I am finding the hard way that this is a one way street. At this point, my TWRP made full backup does not restore the device to the expected status. Each time I apply it, subsequent bootup takes several minutes and I end up going through the initial setup procedure. It seems the device for some reasoin goes through a complete reset procedure.
Titanium Backup is none better. It keeps telling me that my Android ID has changed, a host of system applications start to fail when I try to restore and generally speaking I have now spent between a good 20 hours trying to simply restore my data.
The end story is: root before you encrypt, and either don't upgrade or don't re-root if you do!
Unless someone has a cleat idea of how to do this properly without losing all your data, that is.
François
Click to expand...
Click to collapse
I have had no issues despite doing upgrades, with and without wipes.
Titanium is fine, just stop restoring system app data. Seriously, what data do you have in a system app that you want to restore.
Restore your user apps, their data, and the xml based call, sms, Wifi backups. It will work fine.
Device ID isn't a problem - it's just trying to help you.
pulser_g2 said:
I have had no issues despite doing upgrades, with and without wipes.
Titanium is fine, just stop restoring system app data. Seriously, what data do you have in a system app that you want to restore.
Restore your user apps, their data, and the xml based call, sms, Wifi backups. It will work fine.
Device ID isn't a problem - it's just trying to help you.
Click to expand...
Click to collapse
Sorry if I came across dissing Titanium Backup and/or TWRP. This was not the intent... I am sure both tools work real nice in general cases (and I have had success restoring data on a Jetstream before).
My main issue here is _full device encryption_ enforced by my company's corporate IT to allow me on the corporate exchange server. Do you have full device encryption on?
On my device, even after a full wipe and flashing a fresh stock rom Titanium Backup just did not work as I hoped. When I had to confirm individual popups of apps closing unexpectedly while it was proceeding and got nothing back in the end, what was I supposed to think? It could be that I don't understand how TB works... I was neither able to restore missing apps after the flash (missing apps: 0) nor installed apps data (they would close unexpectedly when started after restoring the back up). So I say: until full operation of TB on encrypted devices is documented, I will stay away from it, even though I am a registered user (and I do not plan to seek reimbursment)!
Anyway, I got to a belated happy ending (previous post edited).
frankieGom said:
Sorry if I came across dissing Titanium Backup and/or TWRP. This was not the intent... I am sure both tools work real nice in general cases (and I have had success restoring data on a Jetstream before).
My main issue here is _full device encryption_ enforced by my company's corporate IT to allow me on the corporate exchange server. Do you have full device encryption on?
On my device, even after a full wipe and flashing a fresh stock rom Titanium Backup just did not work as I hoped. When I had to confirm individual popups of apps closing unexpectedly while it was proceeding and got nothing back in the end, what was I supposed to think? It could be that I don't understand how TB works... I was neither able to restore missing apps after the flash (missing apps: 0) nor installed apps data (they would close unexpectedly when started after restoring the back up). So I say: until full operation of TB on encrypted devices is documented, I will stay away from it, even though I am a registered user (and I do not plan to seek reimbursment)!
Anyway, I got to a belated happy ending (previous post edited).
Click to expand...
Click to collapse
Yup I use device encryption Enabled manually, but it's the same encryption.
You should find that titanium shouldn't even be aware of it - the encryption is transparent!
I wonder... I'm sure lenny had that issue on a recent 4.1.2 "stock" ROM... And he doesn't use encryption...
I personally have had no issues with titanium on an encrypted device anyway
I notice you were using the newest rom - that's the one lenny had issues on.
pulser_g2 said:
Yup I use device encryption Enabled manually, but it's the same encryption.
You should find that titanium shouldn't even be aware of it - the encryption is transparent!
I wonder... I'm sure lenny had that issue on a recent 4.1.2 "stock" ROM... And he doesn't use encryption...
I personally have had no issues with titanium on an encrypted device anyway
I notice you were using the newest rom - that's the one lenny had issues on.
Click to expand...
Click to collapse
Exactly like I thought, encryption should be transparent to Titanium Backup since it runs within the OS.
I have had problems restoring into 4.1.2 DLL1 (the build I came from) and DLL7 (the one I was trying to go to)
The point is moot anyway since the DLL7 I tried was actually branded (Singtel stuff all around the launcher) and did not include French, which is why restoring my TWRP backup was a tempting proposition.
Good to know TB runs fine with encryption as well. What ROM are you running?
François
frankieGom said:
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
Click to expand...
Click to collapse
About a backup : have you tried Online Nandroid (Playstore) (or similar, based on Onandroid) ? This makes a CWM or TWRP compatible backup while the device is running (everything should be unencrypted at this moment).
See http://forum.xda-developers.com/showthread.php?t=1620255
About rooting : you can try the same trick as above, by using ADB-shell and pushing the needed files to root to the device while it is running.
For my S3 there is a Toolkit that automates all this (http://forum.xda-developers.com/showthread.php?t=1703488), maybe there is something similar for your device ?
If not, you should still be able to do it using manual ADB-pushing.
I'm sorry I can't give you detailed instructions about the rooting as I'm not familiar with your device. Search here on XDA and you'll find more details.
pat357 said:
About a backup : have you tried Online Nandroid (Playstore) (or similar, based on Onandroid) ? This makes a CWM or TWRP compatible backup while the device is running (everything should be unencrypted at this moment).
See http://forum.xda-developers.com/showthread.php?t=1620255
About rooting : you can try the same trick as above, by using ADB-shell and pushing the needed files to root to the device while it is running.
For my S3 there is a Toolkit that automates all this (http://forum.xda-developers.com/showthread.php?t=1703488), maybe there is something similar for your device ?
If not, you should still be able to do it using manual ADB-pushing.
I'm sorry I can't give you detailed instructions about the rooting as I'm not familiar with your device. Search here on XDA and you'll find more details.
Click to expand...
Click to collapse
Thanks for the suggestions, and no I had not tried Online Nandroid as I was not aware of it. Anyway, my main issue is now resolved since TWRP has include support for Samsung TouchWiz based encryption in 2.4 and that works well.
For those interested, the only remaining issues I have with TWRP regarding encryption are that if you want to format /data from TWRP (say, to remove encryption) it will fail unless you _do not_ enter the password at boot, and the TWRP formated /data cannot be re-encrypted (you must use stock recovery to factory reset/wipe the device or else the encryption step will sit deat in the water doing nothing). I suppose the second one is a bug that will be fixed in a later version.
I will check Online Nandroid out anyway, being able to make a backup from a live system sounds good!
François
frankieGom said:
Thanks for the suggestions, and no I had not tried Online Nandroid as I was not aware of it. Anyway, my main issue is now resolved since TWRP has include support for Samsung TouchWiz based encryption in 2.4 and that works well.
For those interested, the only remaining issues I have with TWRP regarding encryption are that if you want to format /data from TWRP (say, to remove encryption) it will fail unless you _do not_ enter the password at boot, and the TWRP formated /data cannot be re-encrypted (you must use stock recovery to factory reset/wipe the device or else the encryption step will sit deat in the water doing nothing). I suppose the second one is a bug that will be fixed in a later version.
I will check Online Nandroid out anyway, being able to make a backup from a live system sounds good!
François
Click to expand...
Click to collapse
I have a similar issue. I had the device encrypted and decided to ROOT (using CF-AutoRoot). Unfortunately I cannot bypass the password screen now, although I know that I'm entering the right password. You are saying that if I flash TWRP everything will be fine?
ludovicianul said:
I have a similar issue. I had the device encrypted and decided to ROOT (using CF-AutoRoot). Unfortunately I cannot bypass the password screen now, although I know that I'm entering the right password. You are saying that if I flash TWRP everything will be fine?
Click to expand...
Click to collapse
Two separate things:
Root messing up encrypted touchwiz devices and twrp not handling touchwiz encrypted partitions properly.
The 2nd one, as much as I can tell, is fixed since before 2.5 so if youwork with the latest (2.6) you should be fine.
The first one I haven't played with in a while, but my finding is that you don't want to root a device once it's been encrypted. I've tried several different methods including rooting as you flag as is possible with twrp and all end up the same:the password is not recognised anymore!
The only thing that works for me is rooting before encrypting or only flashing pre-rooted ROMs.
frankieGom said:
Two separate things:
Root messing up encrypted touchwiz devices and twrp not handling touchwiz encrypted partitions properly.
The 2nd one, as much as I can tell, is fixed since before 2.5 so if youwork with the latest (2.6) you should be fine.
The first one I haven't played with in a while, but my finding is that you don't want to root a device once it's been encrypted. I've tried several different methods including rooting as you flag as is possible with twrp and all end up the same:the password is not recognised anymore!
The only thing that works for me is rooting before encrypting or only flashing pre-rooted ROMs.
Click to expand...
Click to collapse
Yes - I had to factory reset the phone and format the SD Card. Never root AFTER encryption :silly:
I've had this tab for awhile now and the lack of updates wasn't an issue for me while my Nexus 7 was still my workhorse. USB port and charging issues has forced me to use the Pro almost exclusively now and it's frustrating. I'm thinking CyanogenMod 13 because it's available and the latest version of android. But I have a couple questions. Please help. I've searched and will continue but a little help would be appreciated.
Internal storage is at the top of my list right now and I believe Cm allows the ability to use SD card as internal storage. It's available in CM12 but apparently not CM13 as it sits as a nightly. Is this still true? I'm going to flash this tab today. Would rather go with 13 but I'll flash a stable 12 because I need this ability.
This isn't really that important but would help with dealing with all my remote controls. Does Cm now have the ability to take advantage of the RF sensor for remote control? In the past it was always blamed on closed source drivers. Still an issue or no?
Thanks for your input. After being away from the scene for awhile I've answered most of my questions. These are the last two.
I have the CM13 version from about a week ago, and it has the option for using the SD card as internal storage. As for the IR blaster, there are a couple of apps on the play-store that worked with CM12, so I assume they will also work with CM13.
Sicron said:
I have the CM13 version from about a week ago, and it has the option for using the SD card as internal storage. As for the IR blaster, there are a couple of apps on the play-store that worked with CM12, so I assume they will also work with CM13.
Click to expand...
Click to collapse
Thank you! Guess I'll grab a 13 nightly and get to work :good:
Hey guys. The install went smooth but I'm getting parsing error when trying to install apps from unknown sources. In particular right now I'm trying to get PS Remote Play setup but the only remote app I can get to install needs updating. Every single other download I've tried has failed due to parsing error.
Edit: Now I'm stuck. Cm13 is running fine. Rooting was smooth, flashing Twrp 3.0.0-2 was smooth. But then I started installing my apps from unknown sources. Parsing errors even though it's set to allows unknown sources. Hours of searches, tons of articles dealing with parsing errors and everyone recommends check the unknown sources box. Nice!
During this process I've booted into recovery and even though it worked fine before now it freezes in different areas. The menu will sometimes freeze right away or wait till I try and reboot into recovery, OS, download it doesn't matter. Reinstall Twrp and no change. I originally used Flashify but also tried Twrp manager which was worthless. Shocker.
At this point I want to just start over but I have zero confidence in Twrp. Or is maybe because of flashify? I'm lost. Is clockworkmod available? Most likely regardless of my thinking I'm missing something here. I just need a fresh start. How should I start. I need a recovery first.
IFLATLINEI said:
flashing Twrp 3.0.0-2 was smooth.
During this process I've booted into recovery and even though it worked fine before now it freezes in different areas. The menu will sometimes freeze right away or wait till I try and reboot into recovery, OS, download it doesn't matter. Reinstall Twrp and no change. I originally used Flashify but also tried Twrp manager which was worthless. Shocker.
At this point I want to just start over but I have zero confidence in Twrp. Or is maybe because of flashify? I'm lost. Is clockworkmod available?
Click to expand...
Click to collapse
Are you flashing TWRP 3.0.0.2 every time? I wasn't even aware they had a 3.0.0.2 build. And once in a while, they release a build with some problems. If you haven't already, try 3.0.0.0. I'm still back on 2.8.5.0 and no issues like you describe.
redpoint73 said:
Are you flashing TWRP 3.0.0.2 every time? I wasn't even aware they had a 3.0.0.2 build. And once in a while, they release a build with some problems. If you haven't already, try 3.0.0.0. I'm still back on 2.8.5.0 and no issues like you describe.
Click to expand...
Click to collapse
Yeah but its 3.0.0-2. https://dl.twrp.me/mondrianwifiue/
Somehow I got it all worked out. Starting over from scratch. The problem now is how to update to more recent nightlies. TWRP doesn't see any files anymore.
IFLATLINEI said:
Yeah but its 3.0.0-2. https://dl.twrp.me/mondrianwifiue/
.
Click to expand...
Click to collapse
I don't know why they just switched from the last digit in the version number being -1, -2, etc, instead of .1, .2 (dash instead of dot) which they used for years.
But that misses the point. If you are having trouble on a brand new TWRP version, try a previous, known good one.
redpoint73 said:
I don't know why they just switched from the last digit in the version number being -1, -2, etc, instead of .1, .2 (dash instead of dot) which they used for years.
But that misses the point. If you are having trouble on a brand new TWRP version, try a previous, known good one.
Click to expand...
Click to collapse
Yeah I got ya. I may try another one. Problem is I couldn't begin to guess which one is a "known good one". I know I've used a few starting with a 2.8 something up to the one I'm using now. None of these were even able to get me this far. But thanks
IFLATLINEI said:
The problem now is how to update to more recent nightlies. TWRP doesn't see any files anymore.
Click to expand...
Click to collapse
You have the right location selected, correct (internal storage vs. SD card)? A number of times, I've switched the location in TWRP, then forgot to change it back and scratched my head wondering where the files went.
redpoint73 said:
You have the right location selected, correct (internal storage vs. SD card)? A number of times, I've switched the location in TWRP, then forgot to change it back and scratched my head wondering where the files went.
Click to expand...
Click to collapse
Yeah I ran into that as well. I can assure you now its set correctly but I did experiment with placing the zip file in folders on both.
I got fed up last night and just started over. I flashed back to stock, Rooted, and flashed TWRP 3.0.0.0 this time and it worked! Installed CMs latest nightly and im up and running. Havent tested yet to see if zip files now show up in TWRP. Ill be looking after lunch
IFLATLINEI said:
I got fed up last night and just started over. I flashed back to stock, Rooted, and flashed TWRP 3.0.0.0 this time and it worked! Installed CMs latest nightly and im up and running. Havent tested yet to see if zip files now show up in TWRP. Ill be looking after lunch
Click to expand...
Click to collapse
If you don't know if zip files show up in TWRP, how did you flash CM? Did you sideload?
To be clear, when you were having trouble seeing zip files in TWRP before, it was using the "Install" function in TWRP? Or were you trying to "Restore"?
redpoint73 said:
If you don't know if zip files show up in TWRP, how did you flash CM? Did you sideload?
To be clear, when you were having trouble seeing zip files in TWRP before, it was using the "Install" function in TWRP? Or were you trying to "Restore"?
Click to expand...
Click to collapse
Because adopted storage wasn't setup till after CM13 was installed. Adopted Storage is the key in this whole mess. Unfortunately for me its also the one key component I need to make this tab last me another year. What I was trying to do was flash the latest nightly with TWRP. That's when I realized TWRP couldn't see any of the files in any folder.
But get this. I forgot to repost after lunch. Seeing as though this time I successfully used 3.0.0.0 to flash CM I thought my chances of it seeing a zip file were pretty good. And it did! But then it freezes. Multiple reboots and all attempts to select a file or folder resulted in TWRP freezing. But at least 3.0.0.0 seen the files as you would expect. Maybe I should give 3.0.0.0-1 a shot again.
Depends do you have the T320, or the T325? AFAK the newer version of TWRP is ONLY for the T320. Having installed it to my T325 I lost my Recovery. thankfully I was able enough to recover it by flashing 2.7.8.x though Odin again in Download Mode. Not sure what was so special about the T320 that it needed a point realese fix for, that the T325 never got.
Ichijoe said:
Depends do you have the T320, or the T325? AFAK the newer version of TWRP is ONLY for the T320. Having installed it to my T325 I lost my Recovery. thankfully I was able enough to recover it by flashing 2.7.8.x though Odin again in Download Mode. Not sure what was so special about the T320 that it needed a point realese fix for, that the T325 never got.
Click to expand...
Click to collapse
I have the T320
At the risk of adding confusion to this Thread, it seems that the T325 version of TWRP was also recently updated to v3.0.1.0 recently.
Since that's the version I'm running,
FYI:
mondrianWIFI = T320
mondrianLTE = T325
The trick here is to google mondrian<INSERT DEVICE> TWRP, which should take you to the direct download page.
To flash from rooted stock you'll need a *.img.tar File, with which to flash from Odin. In my case that would apply to v2.8.7.0 (IIRC).
Once that's been installed you can just use *.zip Files from within TWRP to update it.
Ichijoe said:
At the risk of adding confusion to this Thread, it seems that the T325 version of TWRP was also recently updated to v3.0.1.0 recently.
Since that's the version I'm running,
FYI:
mondrianWIFI = T320
mondrianLTE = T325
The trick here is to google mondrian<INSERT DEVICE> TWRP, which should take you to the direct download page.
To flash from rooted stock you'll need a *.img.tar File, with which to flash from Odin. In my case that would apply to v2.8.7.0 (IIRC).
Once that's been installed you can just use *.zip Files from within TWRP to update it.
Click to expand...
Click to collapse
Just to be clear. There was no problem flashing CM13 from stock with TWRP. Its not till the flash is all done and I selected to adopt SD card as internal storage. Then regardless of TWRP version it either won't see any files or and I've only been able to get 3.0.0.0 to see files but it freezes.
Here's the question. Are you using adopted storage?
IFLATLINEI said:
Just to be clear. There was no problem flashing CM13 from stock with TWRP. Its not till the flash is all done and I selected to adopt SD card as internal storage. Then regardless of TWRP version it either won't see any files or and I've only been able to get 3.0.0.0 to see files but it freezes.
Here's the question. Are you using adopted storage?
Click to expand...
Click to collapse
no not yet, I'm still kinda stuck on a 32GB card that I've had since my S1 days. I'm kinda hoping to pick up a 64GB MicroSD for that purpose soonish though.
But, just outta interest, you wouldn't have happened to have Device encryption enabled, would you? As for myself I managed to figure out that if you encrypt the Device early enough (i.e. before you root it), the GSM \ Data Connections still work. Where as if you do it post root, it would kill those functions. (Not that a T320 User should care though).
But, the other side effect of encryption (of the /data Partition), is the loss of said /data Partition under TWRP. Which can no longer 'see', what it thinks should be a valid /data Partition. So reports back to you a 0kb free (e.g. not found).
Now like I have stated I have not used any features which would marry my MicroSD to the Device, yet... But if I had then as I understand how Google implemented Adapted Storage to work. then it would be reasonable to assume that it would become part of the /data Partition.
So to get to the punch line... is your Device encrypted? If so that's your problem right there.
No I haven't encrypted it. Its on my list of things though. I just didn't want to overcomplicate things at this point. I felt as though I was already pushing pretty hard with the CM13 nightlies and adopted storage. I'll tell you this much though. I said it before and I'll say it again. This thing has never ran so well. Also for the first time since I've had it storage is not an issue.
I'd seriously recommend the Samsung Evo+ micro SD card. I haven't noticed any issues with lag when loading or using any app. Since I've installed this setup a few times now though I noticed that when you do select to adopt storage and it tests your card, pay zero attention to what it says. Same card and twice it said the card was too slow and twice it said nothing. There's a flaw there I think. It alternated. First time the card was too slow but the second time there wasn't a problem and so on. Then again maybe not. Could be the SD card that's causing that. Ahhhhhh who knows. Lol
Hi Folks:
I had been running CM12 and deciding to upgrade to CM13 last night as the several issues seemed to have been addressed most recently in the most recent string of Nightly's.
I followed the instructions from RootJunky dude and all went just fine.
HOWEVER
I lost my root in the process. Not pleased about that.
Any way to get it back now that I'm on CM13, or do I have to roll it all back via a recovery?
Thanks for your assistance
whitehawk66 said:
Hi Folks:
I had been running CM12 and deciding to upgrade to CM13 last night as the several issues seemed to have been addressed most recently in the most recent string of Nightly's.
I followed the instructions from RootJunky dude and all went just fine.
HOWEVER
I lost my root in the process. Not pleased about that.
Any way to get it back now that I'm on CM13, or do I have to roll it all back via a recovery?
Thanks for your assistance
Click to expand...
Click to collapse
Settings - > About Tablet -> click the build number a few times to enable "Developer options" then Click the back arrow or back button -> Developer options -> Root acess - Click Apps and ADB
now apps that need root will prompt you
I am trying to create a master backup of my phone with all of my apps installed and set up the way I want them as a kind of master reference point that I can always go back to in case of problems. I had thought that the way to do this was to set everything up and then do a Nandroid backup from TWRP. However, when I restore it completely resets my system.
I have:
Oneplus 3
TWRP 3.1-0-0
lineage-14.1-20170413-nightly-oneplus3
I am also getting the annoying Dm-Verity message at boot. I have tried to kill it but for now, as it is only cosmetic, I will leave it.
I would appreciate any help.
I continue to research this and I have found this from the twrp.me web page.
"On most devices shipping with Android 6.0 or higher, the device maker has enabled dm-verity as a security measure. The device will signature check blocks of data on the system partition during boot at the block level. The usage of dm-verity prevents TWRP from being able to successfully restore a normal system backup. On most of these devices, you will see an option on the backup page for System Image. A system image backup takes up more space than a regular system backup, but the system image backup is a bit-perfect backup that, when restored, will not break dm-verity (assuming that you don't break dm-verity before making the backup). On a handful of devices, you may also find a Vendor and Vendor Image backup option. The same rules apply with regards to dm-verity. If you need a perfect "go back to completely stock" backup then you should be using System Image (and Vendor Image, when available) instead of just system."
So it sounds like if I make a more complete backup I should not have any issues. But my backups included everything possible to backup.
Still searching for answers.
OK. I just created a backup of a very basic (no apps installed) lineage install. Just creating (not restoring) the backup without flashing anything factory reset the phone.
Flash latest twrp (3.0.4-1). it'll solve your problem..
Thanks vinothkumarv for the reply. I will go get it off twrp.me now. But while I do that, wouldn't TWRP 3.1-0-0 (the one that I am using) be newer than 3.0.4-1?
twrp.me doesn't have 3.0.4-1 listed. A web search brings me to this page that indicates that it is a bug in recent versions of twrp. Another page has a couple of users saying that a modified "blue spark" twrp does not have this issue. I will do some experimenting and get back tomorrow.
Thank you vinothkumarv for the suggestion. I was barking up the wrong tree (thinking dm-verity was responsible) until your suggestion.
hi boxylisher, even i faced the same issue. if I enter twrp, it'll do reset my phone. after flashing this twrp, it resolved that issue.. you can also try this..
Boxylisher said:
twrp.me doesn't have 3.0.4-1 listed. A web search brings me to this page that indicates that it is a bug in recent versions of twrp. Another page has a couple of users saying that a modified "blue spark" twrp does not have this issue. I will do some experimenting and get back tomorrow.
Thank you vinothkumarv for the suggestion. I was barking up the wrong tree (thinking dm-verity was responsible) until your suggestion.
Click to expand...
Click to collapse
TWRP 3.1.0-0 is compatible with OOS but not with other ROMs. So you will have to use either jcadduono's or eng.stk's versions of TWRP which are compatible with both OOS and other ROMs.
dammit....I just flashed the right twrp rebooted recovery. did another backup deleted my old one then rebooted and phone is wiped factory reset. Its because I forgot to turn of screen security?!! dam...oh man...im bummed....... EDIT. It wiped my existing ROM. Im trying to restore the backup that I made with the correct TWRP fingers crossed. I never had any of these problems on my OP2 this phones kicking my ass!! it didnt work its wiped again fdam
Hello Dollar, Yes I feel your pain. It's clearly a bug in TWRP. I am now using bluespark TWRP and everything is running the way it is supposed to.. I have Backed up and restored without this bug wiping my system. I have not set a password yet (and I won't until after I make another "master backup").
Hi all
Does anyone know the best way to roll back from updating to AndroidQ?
I have issues (android auto, casting etc) so would like to roll back to the lastest stable release
I am having a right pain restoring to to anything at the moment
Thanks
nick w said:
Hi all
Does anyone know the best way to roll back from updating to AndroidQ?
I have issues (android auto, casting etc) so would like to roll back to the lastest stable release
I am having a right pain restoring to to anything at the moment
Thanks
Click to expand...
Click to collapse
Yeah you can either use the "flash-all.bat" file that comes in the android p stock image zip or fastboot boot twrp.img and once booted into twrp just restore a backup. But you'll need to create a folder on you sdcard called TWRP. Then put a backup in it. I've even booted twrp then flashed pixel dust. It's not as critical as it was years ago when once you went up bootloader then downgraded which would cause bricking. At least I haven't run into any issues. Just make sure you turn off any lock screens and have "USB debugging" enabled.
If you are enrolled in the beta, just opt out on the website where you opted in. You'll get an OTA, which will wipe your device, so back up first. Just did this last night. Couldn't have gone any more smoothly.
For some odd reason when I rolled back my battery refuses to charge up to 100% any one else having this issue?
You have to have your phone unlocked... Yes, you will lose everything from internal memory, but can restore all your apps and settings.
I made this path twice, on beta 1 and now on beta 2.
First, make sure you have twrp. Back up on twrp everything but you will need only the data partition. Also don't forget to backup your internal memory (different from the data partition).
After that, just flash normally the last factory image from Pie, or at least the same version that you have on your nandroid backup.
After finish the installation, install again twrp. Go into twrp and restore ONLY the data partition!!! You can also restore the boot if you like (if you had magisk installed for instance). This worked flawless with me.
I repeat, no use if you try to restore ALL partitions on twrp!! At least with me, twrp would just reboot in the middle of restoring the system partition (no idea why that happened on beta 1 and now on 2). Second, the same if you try to flash factory image without the -w (without wiping internal memory), it just reboot every time it tries to enter android.
reno218 said:
For some odd reason when I rolled back my battery refuses to charge up to 100% any one else having this issue?
Click to expand...
Click to collapse
This is a bug that was fixed in Q. You can alternatively fix it in pie by flashing a kernel that has Q patches merged in.
Hi,
I flashed TWRP on my unlocked Redmi Note 8T with MIUI Global 12.5.5. Everything was great until I rebooted it and saw Bluetooth error which pops every time I try to turn Bluetooth on or just randomly during usage of the device. I also tried to re-flas TWRP with Orange fox but it unfortunatelly did not help. Now I have no idea what to do but there are also some other people with this problem (for example:
https://www.reddit.com/r/Xiaomi/comments/y9zsak
).
Does anybody know any solution? Thanks!
Btw Orange fox is for ginko devices, I did not find version for willow
I had the exact same problem when I tried to root my stock rom in ginkgo. I was getting a lot of "app keeps stopping" pop ups, and that also included bt. My bt was completely broken until I changed rom. Also I'm guessing this had happened when I had rooted my phone with magisk, not by flashing recovery itself. Perhaps you could try to uninstall magsik, and see it it resolves the issue for you. If that would be the case, then you would have found your problem, and maybe you can flash a custom rom to safely root your phone.
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
So now it tried one of my ideas, which was to install Magisk (root) and uninstall it but it also did not help (I expected that)
vasik006 said:
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
Click to expand...
Click to collapse
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Yeah, that's true. But don't you know how to backup data from these "offline" apps? I was trying to solve this also before unpocking bootloader like a year ago but unsuccessfuly.
Also, which rom should I choose? I'm deciding between LineageOS and Pixel experience.
So I have LOS installed but I can´t install other zip files (like Google apps). Im only getting error: signature verification failed while. Im using LOS recovery so where is the problem?
Solved it!
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Thanks, this might help someone else with this problem. I have already formatted my phone, installed Lineage OS and everything is ok
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Jatin Verma x821 said:
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Click to expand...
Click to collapse
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly? Tks
ennev said:
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly?
Click to expand...
Click to collapse
no need to unroot. simple factory reset the device and you're done.
Jatin Verma x821 said:
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Click to expand...
Click to collapse
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Alpha_Geek1 said:
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Click to expand...
Click to collapse
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Jatin Verma x821 said:
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Click to expand...
Click to collapse
TWRP does backup personal apps and their settings. Once you restore a TWRP backup, you have everything back except media files - images, videos, documents, etc. The launcher icons, the apps, the system settings - everything is a perfect clone which you can restore on a new device (same model, of course).
I actually came across this thread searching to see if others had a problem where merely flashing TWRP caused Bluetooth to crash (and Atmos).
Use OrangeFox
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
s3rv said:
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Click to expand...
Click to collapse
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
starkshadow said:
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
Click to expand...
Click to collapse
It looks like this guy didn't have any luck with it either. It may be divice specific
Dredead said:
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
It looks like this guy didn't have any luck with it either. It may be divice specific
Click to expand...
Click to collapse
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
starkshadow said:
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
Click to expand...
Click to collapse
It seems to be a twrp issue. What version do you have? And what version of magisk do you have?
I have recently flashed miui 12 (android 10) after bricking the phone using qtel. I noticed the Bluetooth problem last week and didn't find a fix. I have twrp 3.6.2 and magisk 25.1. I had twrp 3.7.1 but if failed to decrypt data using pattern so I rolled back to 3.6.2. And I thought that magisk had to do with the Bluetooth problem so I rolled back to 25.1 from 26.
I still can't use the Bluetooth, and I don't have time to reset the phone, I just finished restoring everything
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Olfason said:
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Click to expand...
Click to collapse
I can't afford resetting my phone right now , don't have enough time. I'll let it like that for some months.
Edit : I have miui 12.0.6 installed (android 10) and I'm not planning to upgrade since I have much better battery life (even better than every mod I tried). I wander if I flash miui rom from recovery can fix it?
Edit 2: flashing the rom from recovery didn't fix it