Related
Hi!
Apologies in advance, I don't know much about the workings of android, I just follow guides!
I'm trying out my first custom rom, namely gingerclone, and am having trouble getting all my apps back up and running...
Before installing the rom, I backed up all my apps and settings with titanium backup, so I could restore them much easier after the rom change.
Although when I tried restoring them, I had lots of force closes with titanium backup itself, and about half of my apps would immediately FC on opening and didn't have icons. I then uninstalled the problem apps manually in settings>applications, and tried installing via the market. For some apps, it worked fine, but for others, whenever I try to install from the market, my phone reboots when the download is done and it tries installing. Sometimes it won't even download and just gives me errors, and for some they will install, but will not launch, just force close. I've tried cleaning the dalvik cache with titanium backup, and deleting settings files for the problem apps from my sd card, so that as far as I can see, there is no trace of them. But still, random reboots whenever I try installing, or unopenable if I manage to get them to install.
Any idea what could be going on? Plenty of other apps have installed and are working fine, so I'm stumped.
Had the same exact problem trying to install apps with titanium backup.
what i did was just slow down and install each app one by one and wait for each app to completely install before trying to install the next.
trying to download all of them all and once always made my phone reboot like it does to yours.
well hope this helps!
Wel I ended up uninstalling them all and trying to install again from the market, but I can't even get them to install individually now. It seems like trying to restore the backup has put some rogue files somewhere and is messing it up when I try to install the apps...
I have no idea why, but everything has started working again, so problem solved :/
I don't know. That never happened with me
*****I'm a beginner ROM Developer, so don't forget to thank and donate*****
Phone: Sidekick 4G
ROM: FreshBlood ROM - Beta
Kernel: Bali 2.2 /w Voodoo
Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Or you could just copy the whole twrp folder to your hdd. thats what I do anyway and restore without a problem.
Yep that would have prevented me ending up in that predicament for sure.
So would not flashing roms. The point of the post is really about what to do if you find yourself in that situation and the value of keeping a cool head and thinking through a solution rationally, using your own resources.
The way I see it is: it's my mess I got into it, how am I going to solve it....
Sent from my HTC One S using xda app-developers app
Lost my Backup
Good advice which I'm trying to follow but my TWRP Recovery cannot see the TWRP ROM Backups that I created with ROM Customizer which ROM Customizer has placed in the folder
/data/media/0/TWRP/Backups/4df1bd936aae7f4b
but when my Samsung Galaxy S3 i9300 is in Recovery Mode it is obviously looking somewhere else........I just can't figure out where because then I can just move the backup to where ?Recovery Mode is looking.
Anyone any ideas please?
matrixmainframe said:
Good advice which I'm trying to follow but my TWRP Recovery cannot see the TWRP ROM Backups that I created with ROM Customizer which ROM Customizer has placed in the folder
/data/media/0/TWRP/Backups/4df1bd936aae7f4b
but when my Samsung Galaxy S3 i9300 is in Recovery Mode it is obviously looking somewhere else........I just can't figure out where because then I can just move the backup to where ?Recovery Mode is looking.
Anyone any ideas please?
Click to expand...
Click to collapse
Do what the op says and do a backup and you will know where to put it.
Sent from my HTC One S using Tapatalk 2
Plz HELP!!!
ACtually im in deep deep trouble please i would be really grateful to the person who helps me. OK so last night i flashed cyanogen mod10 on my htc one x and when i did everything booted the boot.img and all i factory reseted from cm10 because it gave me the error that unfortunately android.process.phone has stopped nevertheless now everythings gone and no supersu root file is gone which is obvious that i dont have root now. Plz tell me how to go back to my factory settings with htc sense on it now i just want my phone back, i did another factory reset wiping off the rom but it says no OS installed and it gets stuck on htc quitly brilliant screen plz plz plz plz help me any one plz.
abdullah.imran2158 said:
ACtually im in deep deep trouble please i would be really grateful to the person who helps me. OK so last night i flashed cyanogen mod10 on my htc one x and when i did everything booted the boot.img and all i factory reseted from cm10 because it gave me the error that unfortunately android.process.phone has stopped nevertheless now everythings gone and no supersu root file is gone which is obvious that i dont have root now. Plz tell me how to go back to my factory settings with htc sense on it now i just want my phone back, i did another factory reset wiping off the rom but it says no OS installed and it gets stuck on htc quitly brilliant screen plz plz plz plz help me any one plz.
Click to expand...
Click to collapse
1. wrong forum, if you have a one x device
2. calm down
3. relock your bootloader (fastboot oem lock)
4. download and run latest ruu for your phone (search for a suitable one for your cid and carrier if you are branded)
5. you also can flash a custom sense based rom, which gives you sense back (viper one s or trickdroid or android revolution hd)
6. if you want to flash one of these,dont forget to flash the boot.img too
7. before flashing a rom, wipe system, data and cache 3xtimes to be sure you do a clean install
Thanks Man
ATSPerson said:
Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
Thanks Man, been stuck in TWRP for about two hours now, thought I soft bricked my Droid Dna forever. I had a backup, and adb pushed it to the /sdcard directory, but it wouldn't show up in the restore section. This empty-backup method worked fine. Thanks, you saved me $400.:good:
Saved my HTC One!
ATSPerson said:
Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
I'd just like to say a MASSIVE THANK YOU for this post! I had a major issue and thought I'd lost my 1-day old HTC One (M7). I wasn't so much panicking as I knew i'd find a way, but a cold sweat had started to break!
The biggest lesson I can take from this is simply this... MAKE SURE YOU BACKUP YOUR ORIGINAL ROM BEFORE YOU DO ANYTHING! It's such an obvious thing, but without this simple step, I'd be in trouble right now as HTC haven't an RUU for my specific device yet (plus I'm on a Mac, making running .exe files more painful still)
What had happened was that as a result of a corporate email policy, I had to encrypt my device. I did this after flashing to a new ROM. Unfortunately after I had done so, the new ROM wasn't playing nicely with Exchange (using native HTC Mail app). Of course the issue here is that when you so into TWRP, you can't see the files to restore (because TWRP is opened before the device asks you for the passcode to decrypt... another learning!). To remove the encryption, I had no choice but to do a full format of the device, so I was basically left with a brick
Anyway, once again, thank you for this post, you just saved me AU$700!
Ok so, in not so many words, ur saying " to restore a nanBU":
1. Wipe: data factory reset/cache/ delvic
Wipe system (but not sure which one(s) cause I was used to cwm and it looks diff in twrp
2. Flash the Rom that the nanbu is based from
3. Flash the nanbu
4 reboot
It's this the correct way to restore a nanbu from a diff or upgraded rom?
So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
---------- Post added at 01:20 PM ---------- Previous post was at 12:42 PM ----------
cheyennemtn said:
So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
Click to expand...
Click to collapse
Solved.. Copied my backup stock ROM from the TWRP folder on the phone and placed it on the SDcard, then I placed my Goodness Noteworthy 1.7 backup rom I had that I had on my computer and copied and placed that on the SDcard in the TWRP folder next to the Stock Rom backup I made. Booted back into recovery and clicked RESTORE and I was able to see both the backup rom and the Goodness Noteworthy ROM. I then wiped and did a restore and I'm back in business.
:good:
cheyennemtn said:
So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
---------- Post added at 01:20 PM ---------- Previous post was at 12:42 PM ----------
Solved.. Copied my backup stock ROM from the TWRP folder on the phone and placed it on the SDcard, then I placed my Goodness Noteworthy 1.7 backup rom I had that I had on my computer and copied and placed that on the SDcard in the TWRP folder next to the Stock Rom backup I made. Booted back into recovery and clicked RESTORE and I was able to see both the backup rom and the Goodness Noteworthy ROM. I then wiped and did a restore and I'm back in business.
Click to expand...
Click to collapse
Deleted comment
Hei guys,
Please help!!!! I tried to install MaximusHD 10.0.0 | JB 4.2.2 | Sense 5.0 on my HTC One s,i got storage issue. Now my sd card is just 48MB. I have installed TWRP v2.6.3.0 and i did backup before flashing room. I decided to do factory restore by TWRP and wiped OS from MY device.Now when i do backup i get failed error: not enough free space on storage. Total size of all data 203MB, available space 48 MB.I see my sd card on pc through TWRP, but i cannot make backup and even put any new rom into my sd card to flash it because of 48MB...Is it any chance to get back any OS on my HTC One s....?
This post might help
http://forum.xda-developers.com/showthread.php?p=47744972.
Sent from my One S using xda app-developers app
StifflerServices said:
Ok so, in not so many words, ur saying " to restore a nanBU":
1. Wipe: data factory reset/cache/ delvic
Wipe system (but not sure which one(s) cause I was used to cwm and it looks diff in twrp
2. Flash the Rom that the nanbu is based from
3. Flash the nanbu
4 reboot
It's this the correct way to restore a nanbu from a diff or upgraded rom?
Click to expand...
Click to collapse
EDIT: oops, somehow thought this was a recent post. Never mind
Not really.
If you are S-off,
Restore Backup,
Wipe Caches
S-On
Restore Backup
Wipe Caches
(if the rom you were previously on had a different Boot.img you will need to fastboot your boot.img) In the backup
Assumes you are not trying to restore a backup to 2.15 if you were just on 2.16. You will need to RUU + factory reset/clear storage for that.
I'm sry not sure what "RUU" means... Probably will remember once u tell me I'm sure. But Ya I kinda just winged it, didn't flash the Rom to do the NanBU and all went fine, which is odd cause on my S2 w cwm it out me in a boot loop and had to start over, but I think TWRP may be a diff setup when restoring nanbu's. But either way it's always nice to know and find a "step by step" guide to restoring NanBU's from previous / updated / or different ROMs. For noobs that was one of the confusing things to do due to lack of that info in threads or utube vids out there.
Got a question. I've made my backup files but restore shows nothing but storage... No files to chose, no more options to restore. Is it normal?
Sent with my One S C2 Sense 5 using Taptalk
brilliant!
ATSPerson said:
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
you my friend, are a genius! I have been so screwed trying all kind of crazy stuff the last few days.
Brilliant! May I suggest you run for Pres of the Colonies.
metropical said:
you my friend, are a genius! I have been so screwed trying all kind of crazy stuff the last few days.
Brilliant! May I suggest you run for Pres of the Colonies.
Click to expand...
Click to collapse
From one Clash fan to another, thanks for the thanks ☺
¡La lucha continua!
Dear community,
honestly I considered myself not a noob anymore when it comes to flashing, rooting and installing devices. But obviously I was wrong: Cyanogenmod, Titanium Backup and SuperSU are fooling me to madness. :silly: So I hope to find help here because all I want to do is to restore all apps' data. But I will start at the beginning:
I updated my rooted Nexus 7 LTE to CM 13.0-20151226-NIGHTLY-deb and it turned out that Google Play Services continue to crash, no PlayStore could be loaded and so on. I've searched for this issue and don't want to discuss this here as there are many threads for this already.
However, I deciced to switch to OpenGapps and downloaded the pico package for Android 6 on ARM.
By the way I also switched from CWM recovery to TWRP 2.8.7.1.
Finally, CM was running as expected and I danced my pants off!
During all this I formatted the device completely, but made a backup of all apps using Titanium Backup.
So, I re-installed Titanium Backup, copied the backup files to the device and started to "restore missing apps and data" from the bulk operations menu.
All selected apps were installed perfectly (danced again) but then I noticed that the apps' data was not restored.
I searched for this issue and found instructions saying that SuperSU is needed for Titanium Backup to restore data. That was new to me as TB worked fine without SuperSU on my device all the time.
However, I flashed the latest stable Version of SuperSU from chainfire.
After rebooting, the SuperSU app was installed and when it starts, an error popup appears saying that no su file is installed and this has to be done manually.
When I now start Titanium Backup, it prompts missing root access and consequently does not start up.
Furthermore CM is really unstable and freezes from time to time.
So, I lost root by flashing SuperSU? What irony!
Anyway, I am willing to format and re-install my device another time and I would gladly set SuperSU aside as I never needed it in the past. But I really need to get Titanium Backup working to restore the apps' data.
Can anyone of you help me on this, please? Is SuperSU really necessary or do you know a way to manage Titanium Backup without SuperSU on CM13?
cocororo said:
Dear community,
honestly I considered myself not a noob anymore when it comes to flashing, rooting and installing devices. But obviously I was wrong: Cyanogenmod, Titanium Backup and SuperSU are fooling me to madness. :silly: So I hope to find help here because all I want to do is to restore all apps' data. But I will start at the beginning:
I updated my rooted Nexus 7 LTE to CM 13.0-20151226-NIGHTLY-deb and it turned out that Google Play Services continue to crash, no PlayStore could be loaded and so on. I've searched for this issue and don't want to discuss this here as there are many threads for this already.
However, I deciced to switch to OpenGapps and downloaded the pico package for Android 6 on ARM.
By the way I also switched from CWM recovery to TWRP 2.8.7.1.
Finally, CM was running as expected and I danced my pants off!
During all this I formatted the device completely, but made a backup of all apps using Titanium Backup.
So, I re-installed Titanium Backup, copied the backup files to the device and started to "restore missing apps and data" from the bulk operations menu.
All selected apps were installed perfectly (danced again) but then I noticed that the apps' data was not restored.
I searched for this issue and found instructions saying that SuperSU is needed for Titanium Backup to restore data. That was new to me as TB worked fine without SuperSU on my device all the time.
However, I flashed the latest stable Version of SuperSU from chainfire.
After rebooting, the SuperSU app was installed and when it starts, an error popup appears saying that no su file is installed and this has to be done manually.
When I now start Titanium Backup, it prompts missing root access and consequently does not start up.
Furthermore CM is really unstable and freezes from time to time.
So, I lost root by flashing SuperSU? What irony!
Anyway, I am willing to format and re-install my device another time and I would gladly set SuperSU aside as I never needed it in the past. But I really need to get Titanium Backup working to restore the apps' data.
Can anyone of you help me on this, please? Is SuperSU really necessary or do you know a way to manage Titanium Backup without SuperSU on CM13?
Click to expand...
Click to collapse
lmao, your title is nice!
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken. .52 is stable even though its not listed as, i have been using it for some time, and its whats needed for M. you may even find some .6 versions, dont use those, they are systemless, well you can if you want lol. i havent tried them yet, so i dont know what pitfalls may lurk.
Thank you for your help and I am happy to entertain
bweN diorD said:
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken.
Click to expand...
Click to collapse
I will try to update SuperSU as soon as possible.
But sadly TWRP now freezes a few moments after I start the device in recovery mode. When the device starts normally, it freezes as well while showing the CM launcher screen. It stays animated but nothing happens. I will try to re-install TWRP via fastboot flash and then install SuperSU .52 and post my experiences here. :fingers-crossed:
Hi again bweN diorD,
bweN diorD said:
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken.
Click to expand...
Click to collapse
Sorry to say so but SuperSU .52 does not solve the problem. In fact, after flashing the BETA-SuperSU-v2.52.zip using TWRP, CM does not start up anymore. The loading screen with the hypnotizing smiley appears and stays animated but even after 15 minutes CM does not start up. Even TWRP was freezing from time to time.
So I re-installed TWRP, CM and Gapps like in my first post again.
So, is the problem that my device is not rooted indeed? Could this be fixed with CF-autoroot or any tool like this?
I found this thread http://forum.xda-developers.com/showthread.php?t=2448352 although it is for the device deb-razor and my device's bootloader says it is a deb-zoo. By the way, the bootloader displays "LOCK STATE - unlocked".
cocororo said:
Hi again bweN diorD,
Sorry to say so but SuperSU .52 does not solve the problem. In fact, after flashing the BETA-SuperSU-v2.52.zip using TWRP, CM does not start up anymore. The loading screen with the hypnotizing smiley appears and stays animated but even after 15 minutes CM does not start up. Even TWRP was freezing from time to time.
So I re-installed TWRP, CM and Gapps like in my first post again.
So, is the problem that my device is not rooted indeed? Could this be fixed with CF-autoroot or any tool like this?
I found this thread http://forum.xda-developers.com/showthread.php?t=2448352 although it is for the device deb-razor and my device's bootloader says it is a deb-zoo. By the way, the bootloader displays "LOCK STATE - unlocked".
Click to expand...
Click to collapse
hmmm,
i havent used 2.52 on a cm rom, but i have used it on plenty aosp 6.0.* roms without issue.
clean things up so its booting again, then look in developer options and make sure root is turned on. i have seen a few times devs default it to off, but i have never seen a custom rom come not rooted at all.
bweN diorD said:
clean things up so its booting again, then look in developer options and make sure root is turned on.
Click to expand...
Click to collapse
Thanks for your support!
I cleaned everything up -- meaning re-installed everything -- so the device boots up. I checked the developer options and root is set to "apps only". That worked up to now.
Speaking of root: As I wrote I used to have CWM and switched to TWRP. Anyhow, CWM always asked to "fix root" when exiting. I think that's why things worked then and now with TWRP this "fix root" option is gone. But why is SuperSU not working for my Nexus 7 deb? I also tried to install older versions like advised in the Nexus 7 thread here but there was not even a SuperSU app.
So, I recap: CWM used to fix root, TWRP does not. That's why installing SuperSU seems to be a good idea. SuperSU's latest version freezes CM at start-up. Without SuperSU Titanium Backup does not restore app data while other apps do not have problems to get root access. I'm confused
cocororo said:
Thanks for your support!
I cleaned everything up -- meaning re-installed everything -- so the device boots up. I checked the developer options and root is set to "apps only". turn it on apps and adb and see if that helps, thats the preferred setting anywaysThat worked up to now.
Speaking of root: As I wrote I used to have CWM and switched to TWRP. Anyhow, CWM always asked to "fix root" when exiting. I think that's why things worked then and now with TWRP this "fix root" option is gone. its not gone in twrp, it sees that you have root and doesnt ask. really its unadvised to use the twrp generated root anyways But why is SuperSU not working for my Nexus 7 deb? I also tried to install older versions like advised in the Nexus 7 thread here but there was not even a SuperSU app.hmm, maybe thats the problem, maybe you need to install supersu to get things working properly. its on the play store, give it a shot
So, I recap: CWM used to fix root, TWRP does not. That's why installing SuperSU seems to be a good idea. SuperSU's latest version freezes CM at start-up. Without SuperSU Titanium Backup does not restore app data while other apps do not have problems to get root access. I'm confused
Click to expand...
Click to collapse
^^^^
so to clarify your last paragraph, when you say that installing supersu breaks things, were talking about the zip right?
i just want you to get the app from the play store, if you havent tried that alone yet. but change the root setting too.
bweN diorD said:
so to clarify your last paragraph, when you say that installing supersu breaks things, were talking about the zip right?
i just want you to get the app from the play store, if you havent tried that alone yet. but change the root setting too.
Click to expand...
Click to collapse
Correct, I was talking about the zip which is meant to be installed through TWRP.
So, I downloaded the SuperSU app after double-checking that root is set to "Apps & ADB" in the developer settings. Btw. debugging and installation from unknown sources (I hope this is the right translation for this feature) is enabled as well.
When I started the SuperSU app, it first says the binary SU needs an update and I could choose the installation method: When choosing "normal", the app tried to install but failed saying "Installation failed! Restart device and try again!" but even after restarting this was what the app gave me. When I chose "TWRP" the app rebooted the device to recovery but I assume this would end up in installing the zip file which crashed my CM.
Finally, I installed CF-autoroot for deb via the .bat file included in the CF-autoroot package. Now, SuperSU and Titanium Backup are not complaining anymore, so I think this root issue is fixed! :highfive: (couldn't find a dancing smiley).
However, Titanium Backup is not bringing back my app data The restore process seems good as Titanium Backup installs missing apps but even if I install an app the official way via PlayStore and then restore the app's data from my backup using Titanium Backup, there is no effect and the app acts like being installed freshly.
TB claims "restore successful" but the app's data is still missing. I will now check if the backup files are really sound and if I can get them to work on another device. The worst thing I could imagine is that TB did not backup data of apps which had been installed on sdcard. In that case, the data is lost, I'm afraid...
Do you have an idea how this could be or what I could try?
cocororo said:
Correct, I was talking about the zip which is meant to be installed through TWRP.
So, I downloaded the SuperSU app after double-checking that root is set to "Apps & ADB" in the developer settings. Btw. debugging and installation from unknown sources (I hope this is the right translation for this feature) is enabled as well.
When I started the SuperSU app, it first says the binary SU needs an update and I could choose the installation method: When choosing "normal", the app tried to install but failed saying "Installation failed! Restart device and try again!" but even after restarting this was what the app gave me. When I chose "TWRP" the app rebooted the device to recovery but I assume this would end up in installing the zip file which crashed my CM.
Finally, I installed CF-autoroot for deb via the .bat file included in the CF-autoroot package. Now, SuperSU and Titanium Backup are not complaining anymore, so I think this root issue is fixed! :highfive: (couldn't find a dancing smiley).
However, Titanium Backup is not bringing back my app data The restore process seems good as Titanium Backup installs missing apps but even if I install an app the official way via PlayStore and then restore the app's data from my backup using Titanium Backup, there is no effect and the app acts like being installed freshly.
TB claims "restore successful" but the app's data is still missing. I will now check if the backup files are really sound and if I can get them to work on another device. The worst thing I could imagine is that TB did not backup data of apps which had been installed on sdcard. In that case, the data is lost, I'm afraid...
Do you have an idea how this could be or what I could try?
Click to expand...
Click to collapse
sorry, i really dont know what happens as far as titanium when you put an app on the sd.
glad you got root working though, although i still dont understand why it wouldnt work the right way.
if you run into any more specific road blocks, ill try and help if i can, but this general problem with the data, i havent a clue the problem or solution, short of the data isnt there completely.
Hi again,
sorry for my late reply! I tried a couple of things but here's the most obvious one:
Apparently the backup files are kind of corrupt. I don't know what went wrong there but TB did not create a full backup. Indeed there is a .tar.gz file for every app but in fact none of these has more than 2 KB. So I strongly assume that this might be the mistake - which also means that all my app's data is lost.
bweN diorD said:
glad you got root working though
Click to expand...
Click to collapse
At least this is a success and I am happy to have TWRP, OpenGapps and Titanium Backup running on a fully rooted device :good:
Thank you for all your time and help! I really appreciate how supportive we "techies" are :highfive:
Have a great day and - a bit late but anyway - a happy new year!
Hello everyone, I was able to fix my bootloop occuring after flashing a zip on magisk, without any data loss. I wanted to share what I did to fix since it may be helpful for others. It is useful method worth trying if you know what caused the bootloop. It is definitely not a universal method of fixing bootloops or anything, but If you have a similar problem, you can try these steps.
The bootloop happened after I flashed a zip on Magisk that I downloaded using EdXposed Manager app. I remember downloading the latest alpha version zip and flashing it using Magisk (I had already had the riru core and riru edxposed modules installed on Magisk but on Edxposed manager app, it was showing some error, so I also flashed the zip that I downloaded using the app. I think this caused the bootloop somehow. ) I had no backups.
(I had also "unable to mount /data" problem on TWRP, I am explaining how I fixed that also, if you don't have the problem, you can skip this paragraph)
My TWRP version was 3.2.1.0. And when I was in recovery mode, I was getting "unable to mount /data" error. This is actually a well-known error, but I was able to fix it without a format by just updating my TWRP to 3.3.1.0. After the update, somehow, internal storage could be mounted and everything was fine. My goal by trying to fix this problem is to be able to have a backup using TWRP (using backup feature on TWRP) (just make sure that you didn't choose the compression option on options tab of TWRP backup page).
If you don't have "unable to mount data" problem at all, just make a TWRP backup. (just make sure that you didn't choose the compression option on options tab of TWRP backup page).
So, after having a TWRP backup of everything (actually just System and Data backup would also be fine), I tried to edit my backup files to fix the problem that caused the bootloop.
I changed 2 things in my backup files (you can edit the backup files ending with .win001 etc using 7zip on windows or anything similar. since the backup files are not compressed, you can just delete files) (I edited only the "Data" backup files due to my specific problem, but if your problem is something different, you may have to edit different files also):
1) I deleted everything about EDXposed manager(com.xx.edxposedmanager files) (It might have nothing to do with the fix, I am not sure)
2) In one of the data backup files (probably in the last one), there is a folder called "adb". In adb, there is a "modules" folder. I deleted riru core and riru edxmanager folders in modules.
After these steps, I restored "Data" and "System" using TWRP restore. Bootloop is fixed without any data loss.
If your bootloop is caused by something different, (the point I am trying to tell is) you can edit the nandroid backup files if you know the root of the problem and maybe fix your phone. When I was editing the backup files, I had no hope. As I said, I think this method is worth trying.
I Found this to be true. I also don't see the reason to reflash everything to fix a problem. Thank you for this tutrorial this is an undocumented tactic and i don't know why. Before i discovered this type of surgery i operated under the assumtion that android must be different from other operating systems in some way which would make this impossible. But like you i delved deeper and discovered that this is like a dark art the devs keep to themselves because of what ever but it works. I like this type of post and usually aside from asking for help or a little feed back this is the only type of post i ever make. I mean how do you expect people to learn how to do anything if you never teach them anything useful. EX: "You didn't do it exactly right from the beginning because if left out one thing in my tutorial so you would fail now erase everything and start over." "I only did that to teach you to backup" such bull ****! Thanks again for fighting the good fight.
After my experiment of trying out Beta 3 of Android Q failed apocaliptical I tried to restore the backup I made minutes before. But no matter what I do, I keep getting:
- bootloops (straight rebooting after showing the unlocked bootloader warning)
- restart into recovery
- Oxygen OS loading animation stuck and animation being very slow
- not getting it anymore but had it yesterday in the early stages of my disaster management: Qualcomm Crash POST
Despite that the backup was generated succesfully (at least thats what TWRP said)
I tried almost every guide out there.
- switching to rm -rf
- restoring only data, only boot, only system and a mix of those
- flashing the OTA before restoring backup
- uninstalling magisk und reinstallating magisk (with and without separate reboots)
-multiple wipes of single partitions and data formatting
The only good thing is that I don't get the 255 error anymore I had at the beginng, allthough I don't really know anymore how I did it.
At the end I am only able to restore everything with the MSNTOOL out there.
Is there any golden hint to get the data the be restored? The backup of /data is critical as there my authenticator and banking data are in there.
Thank you in advance
Edit: As I am slowly getting fed up with OnePlus and the problems (proximity sensor, adaptive brightness, whatspps microphone, twrp issues, lacking tech guides if at all) I thought about migrating to Pixel 5. Is it possible to migrate the data partition? Or are all backup partitions strictily device specific?
anphex said:
After my experiment of trying out Beta 3 of Android Q failed apocaliptical I tried to restore the backup I made minutes before. But no matter what I do, I keep getting:
- bootloops (straight rebooting after showing the unlocked bootloader warning)
- restart into recovery
- Oxygen OS loading animation stuck and animation being very slow
- not getting it anymore but had it yesterday in the early stages of my disaster management: Qualcomm Crash POST
Despite that the backup was generated succesfully (at least thats what TWRP said)
I tried almost every guide out there.
- switching to rm -rf
- restoring only data, only boot, only system and a mix of those
- flashing the OTA before restoring backup
- uninstalling magisk und reinstallating magisk (with and without separate reboots)
-multiple wipes of single partitions and data formatting
The only good thing is that I don't get the 255 error anymore I had at the beginng, allthough I don't really know anymore how I did it.
At the end I am only able to restore everything with the MSNTOOL out there.
Is there any golden hint to get the data the be restored? The backup of /data is critical as there my authenticator and banking data are in there.
Thank you in advance
Edit: As I am slowly getting fed up with OnePlus and the problems (proximity sensor, adaptive brightness, whatspps microphone, twrp issues, lacking tech guides if at all) I thought about migrating to Pixel 5. Is it possible to migrate the data partition? Or are all backup partitions strictily device specific?
Click to expand...
Click to collapse
Try, booting into twrp... Format data. Type yes to format. Restore. Should boot.
@soka said:
Try, booting into twrp... Format data. Type yes to format. Restore. Should boot.
Click to expand...
Click to collapse
I did just exactly that on stock 10.0.0.11 to no avail, the TWRP restore went through fine but upon system reboot the phone stayed on the bootloader unlocked warning for about two minutes, then it rebooted straight into stock recovery.
It's beyond my understanding yet how the user data partition can cause the whole system to effing die.
My only hunch is that it has something to do with Magisk I had installed during the backup (encryption was disabled btw). But as I said I already tried running Magisk installer and uninstaller on different occasions with the same result. Also the only thing that should happen is that after restore and reboot the phone should tell me that Magisk isn't installed anymore.
Edit: So for now I reverted to full stock 10.0.11 and for the sake of experimenting I made a backup with system, boot and data of this stock rom and restored it succesfully. When I restore my actual data backup I get the same old restart and then it throws me back into TWRP. Is there any log I can check to see what's happening there?
Sorry for double post, but I think this might be very interesting for people with a similar problem as this seems to be very common with OnePlus phones.
So I found a very dirty and hacky way to get a least my most importants app running in the state they had during my backup I was trying to restore. Here's what I did, without any guarantee it might work for you or be stable in the end.
Code:
1. Revert the phone to a clean stock rom and update to the latest stable version (at the time of writing 10.0.11), it should be fully factory reset, aka like new. I am not sure but it may be necessary that you install the apps you want to restore first since the I am not sure the partition we use later contains the app AND the data too.
2. Unlock bootloader and flash latest TWRP, may it be official or mauronofio's
3. Make a backup of that current stock data partition
4. Restore data partition from your actual needed twrp backup (if it ends with 255, try to format data partition before in TWRP)
5. With the TWRP file manager navigate to the /data/data folder and copy everything to an external storage (I chose USB)
6. Restore the stock data partition
7. Now again with the TWRP file manager navigate to the /data/data folder on your external storage (should be /usbstorage) and search for the apps you need to restore (probably banking apps, authenticator, etc.), the name will be something like com.google.authenticator2.
8. Copy the folder of any needed app into the /data/data folder on your phone. Best you do it one by one just to make sure.
Now you can reboot to system. The apps should be fully restored. In my case it worked with Google Authenticator, Blizzard Authenticator, Consorbank Secure Plus (shows undefined error yet), Hue Pro. Maybe I will try more.
Edit: Consorsbank Secure Plus as you might guess is a tan generation banking app. When entering the pin when opening the app it shows "An error has occured". Dunno why, maybe a security checksum error or something. I found com.android.keychain and copied for the sake of trying too but it didn't help.
If you have any questions, suggestions or improvements, feel free to post!