Hi guys,
Unfortunately my Nexus 5 kinda died on me today and I'm almost devastated. The phone froze and then restarted (I pressed the power button a couple of time, so I’m not sure if I restarted it or it did it by itself) and stayed stuck on the Google logo screen. I tried a couple of things but none works – booting it in recovery -> wipe partition cache; shutting it down and restarting it; leave it like that and praying to God…
I need your help. What can I do in order to fix this and keep my personal data on the phone – apps (with their data – I have a couple of journaling apps that are very important to me), messages, pictures, history, calls and so on…
The most important thing for me is to retrieve this data, so a factory reset is out of the question. Is there any way I can fix this? If not, how can I recover/retrieve all my data from the phone?
P.S. I'm using the latest Android OS, without that last OTA update, the booloader is unlocked and stock...
You could flash twrp, create a nandroid backup, copy the backup to your phone for safe keeping, restore the backup to an identical phone (you'll have to change the serial number of the backup to the phone that will be used for the restore), and hope it all works.
If you don't have access to an identical phone, you could try wiping the phone and restoring the backup.
You could flash twrp and copy off the important data.
Lastly, you could flash a stock rom, flash twrp, and restore your data and apps.
audit13 said:
You could flash twrp, create a nandroid backup, copy the backup to your phone for safe keeping, restore the backup to an identical phone (you'll have to change the serial number of the backup to the phone that will be used for the restore), and hope it all works.
If you don't have access to an identical phone, you could try wiping the phone and restoring the backup.
You could flash twrp and copy off the important data.
Lastly, you could flash a stock rom, flash twrp, and restore your data and apps.
Click to expand...
Click to collapse
Thank you for your kind and quick reply. I'm almost a complete android illiterate so I will bug you with a couple more questions, just for a better understanding.
So flashing TWRP means installing it...
1. Am I able to do this, considering the state of my phone? And will I be able to do the nandroid backup?
2. Is this tutorial good? http://www.xda-developers.com/how-to-install-twrp/
3. My phone is not rooted. Does this matter?
4. My phone has a capacity of 15 gb, of which approx. 1.5 gb were left free... Will I still be able to do the backup?
Thank you
The TWRP tutorial should be good - it's an XDA post...
You don't have to install TWRP, though it's a good idea unless you really don't want it. You can run it temporarily and on the next boot you'll be back to normal stock recovery. Booting temporarily will allow you to make a backup, but the risk is that you also back up the problem and then restoring the backup will also restore the problem - but it's worth a try.
"3. My phone is not rooted. Does this matter?" No, TWRP doesn't need root.
"4. My phone has a capacity of 15 gb, of which approx. 1.5 gb were left free... Will I still be able to do the backup?" Probably not - a backup is probably about 3GB, but if you manage to get as far as connecting to your PC and seeing your internal storage in Windows Explorer, you can copy the essential data (photos, etc.) to the PC and then do the backup and attempt the restore.
Press power & volume down simultaneously until you get to the bootloader screen with the green robot on its back. Connect the device to the PC - I'd recommend a direct laptop connection, not via a USB hub.
Start a CMD window and navigate to your PC adb/fastboot directory.
Type "fastboot devices" (no apostrophes) - if you're properly connected, you'll see something like "459uirgggg4 fastboot", which is your device id. A blank line means no connection.
To boot TWRP temporarily - "fastboot boot twrp.img".
To install TWRP permanently - "fastboot flash recovery twrp.img".
Once complete, use the volume keys to find "Reboot recovery". When you're in recovery, with any luck you may be able to see your internal storage in Windows Explorer, and you can at least retrieve your data. You could then try the restore, and if it doesn't work, a full installation of the latest ROM and rebuild your device from there (though Google automatically restores most of your apps if you had chosen that option).
Double-check these commands against other posts - I offer no guarantees, but at least a bit of hope...
Good luck.
Thank you! One more quick question, if I get as far as connecting and seeing my internal storage, would I be able to erase some data, in order to make room for the backup?
Yes, that's exactly what I meant. Photos are simple to identify, take up quite a lot of room, and can easily be transferred to your PC for safety and then deleted from the device. Anything free-standing (i.e. photos, for example, are independent of the app which captured them) and easily-identifiable, copy and delete from the device. Things like SMSs are trickier, since they may be held in not-obvious places or formats. If you take a copy to your PC, and delete to free space, you may have enough space for the backup, but as I mentioned you may just be backing up the problem as well as the system (backups don't tend to copy user data).
dahawthorne said:
Yes, that's exactly what I meant. Photos are simple to identify, take up quite a lot of room, and can easily be transferred to your PC for safety and then deleted from the device. Anything free-standing (i.e. photos, for example, are independent of the app which captured them) and easily-identifiable, copy and delete from the device. Things like SMSs are trickier, since they may be held in not-obvious places or formats. If you take a copy to your PC, and delete to free space, you may have enough space for the backup, but as I mentioned you may just be backing up the problem as well as the system (backups don't tend to copy user data).
Click to expand...
Click to collapse
Okay, here's the current situation - I managed to connect it to my pc and it's visible.
I saved my photos and cleared up some space. I now have 9 GB of available memory.
I tried TWRP (didn't install it though, as I receive an error, saying that it can't complete the command) and manage to boot it and enter the backup menu.
Unfortunately, it cannot backup my data, as it remains stuck on "updating partition details"...
Not sure what to do... Should I wait longer? It stayed like that for approx. 50 min, before I restarted it. Should I try a previous version of TWRP? Should I try a different program/method of doing a nandroid backup?
Also, there were options to backup my: system, cache, data, boot etc. Choosing to backup only my data would do the trick? As I said, I'm most concerned about my journaling apps, that were not backed up.
Anyways, here is something interesting that happened after I restarted it during the TWRP stuck backup process - the phone started and passed the google logo screen! And I managed to enter it. Things appeared to be normal and I was overwhelmed by hope. However, when I tried to open an app, it froze and started all over again. And one more detail, the battery was low, like 10%. It was low yesterday, too, when it died the first time. Could it be related? Do you guys make anything out of this? Should I proceed by backing up my data and flash a new OS?
Nice to see some progress...
The first thing to do is to get the battery properly charged. Some functions (I'm thinking specifically of encryption, which demands at least 50% charge plus the device plugged in) won't work properly on a low charge. It may not be the cause, but it certainly won't help if the battery is low.
9GB is now plenty to take an entire backup. The TWRP backup screen shows how much data is in each partition. I'm not entirely sure exactly what "data" does back up - I very much doubt (from experience) that it will back up things like photos, but as I said before some data is stored in obscure places and you may be lucky. Back up everything except cache - the defaults in 3.0.2.
Definitely back up EFS. Read around and see the havoc it causes if you have problems and don't have it backed up.
So... you temporarily booted into TWRP? Latest 3.0.2? And the "updating partition details" message was after you pressed the backup button? There shouldn't be any delay - my backups of 6GB on my N6 take only 5 minutes - the N5 is slower but not that much slower, and you have a lot less to back up. If TWRP still continues to be difficult, yes, try the previous version. Even back to a version 2 if necessary.
Try the backup when the device is charged, save it to your PC, and then reboot. Fingers crossed. Good luck.
dahawthorne said:
Nice to see some progress...
The first thing to do is to get the battery properly charged. Some functions (I'm thinking specifically of encryption, which demands at least 50% charge plus the device plugged in) won't work properly on a low charge. It may not be the cause, but it certainly won't help if the battery is low.
9GB is now plenty to take an entire backup. The TWRP backup screen shows how much data is in each partition. I'm not entirely sure exactly what "data" does back up - I very much doubt (from experience) that it will back up things like photos, but as I said before some data is stored in obscure places and you may be lucky. Back up everything except cache - the defaults in 3.0.2.
Definitely back up EFS. Read around and see the havoc it causes if you have problems and don't have it backed up.
So... you temporarily booted into TWRP? Latest 3.0.2? And the "updating partition details" message was after you pressed the backup button? There shouldn't be any delay - my backups of 6GB on my N6 take only 5 minutes - the N5 is slower but not that much slower, and you have a lot less to back up. If TWRP still continues to be difficult, yes, try the previous version. Even back to a version 2 if necessary.
Try the backup when the device is charged, save it to your PC, and then reboot. Fingers crossed. Good luck.
Click to expand...
Click to collapse
Dahawthorne, thank you! I managed to make a backup after following your suggestion regarding the battery.
However, I didn't do a factory reset... not yet. Something strange happened while I tinkering with it (basically starting it and shutting it down with a furry) - it entered the OS! And everything was there and seemed to be fine, I was able to access my apps and saved a couple of things. But... when I clicked on a web page, it froze again and I was back at square one. Could it be that I have too many tabs/web pages in the background?
If it's only Chrome (or other browser?) that's making it freeze, you might want to try installing a different browser.
In the meantime, given your situation, I'd concentrate on recovering all the data you want and copying it to your PC for safety in case you have to resort to a factory reset or full re-flash of the ROM.
In case you can't find the data for the reasons I originally mentioned, you could try the Play Store for backup applications - e.g. there's a good SMS backup app which will back up & restore your texts. There may be something similar for your journaling app.
(And what's a "furry"...? )
Related
i'm reading through all the posts for people updating to the new firmware and wiping away all their data without a care. how can you afford to do that so easily?
I have lots of data like SMS messages I need to keep around, applications that cant be downloaded anymore (such as hello aim beta, wifi tether), settings, etc.. that I just can't wipe my phone. how are you people keeping this data around?
I personally use apps to Sd card and to backup sms and such I use MyBackup Pro available on market for about $5. It works great. Go try it. You can even back up applications with it.
John5788 said:
i'm reading through all the posts for people updating to the new firmware and wiping away all their data without a care. how can you afford to do that so easily?
I have lots of data like SMS messages I need to keep around, applications that cant be downloaded anymore (such as hello aim beta, wifi tether), settings, etc.. that I just can't wipe my phone. how are you people keeping this data around?
Click to expand...
Click to collapse
I usually will run a nandroid backup first then i can just flash it back without any trouble after the wipe.
I also have GSCRIPT on the phone and have a script that backs up all my apps to the SD and then I have a SCRIPT that will reinstall all my APPS when it is all said and done if I need it for those times that I am unable to backup first.
John5788 said:
i'm reading through all the posts for people updating to the new firmware and wiping away all their data without a care. how can you afford to do that so easily?
I have lots of data like SMS messages I need to keep around, applications that cant be downloaded anymore (such as hello aim beta, wifi tether), settings, etc.. that I just can't wipe my phone. how are you people keeping this data around?
Click to expand...
Click to collapse
I always make a nandroid backup. As a matter of fact, I make a nandroid backup weekly or before I do anything drastic to my phone like delete all SMS or try something new. Nandroid backup process takes but 5 minutes. Most of the apps can be downloaded over again and most of SMS are of no importance. All my pics and audio and wallpapers are on SD, so that automatically gets moved.
If I ever need to reference to something, I just flash the nandroid backup, look up what I need and then flash back to the other nandroid backup etc. So far that is my game plan, but i've yet to do this as I've never really had the need to go back.
It is tedious process especially for the apps but I have kept a list and it isn't too bad.
there are other wifi tether programs that are probably better than what you had before.
anything and everything is out there apk wise, if you know where to look.
but, there are backup programs and since I don't use them (other than nandroid), hopefully someone can comment on them.
question, i can do a nandroid backup fine without any problems. i believe i am using jf1.42 recovery image, but lets say my phone bricks, whatever nandroid backed up for me, how do i install it back again? n00b question i know but ive searched around and havnt found that answer yet.
I haven't wiped my phone in over a month.
I use MyBackup Pro. Backs up all your Data, Apps, and settings. And, of course, I make a nandroid backup before I flash anything.
madunix said:
question, i can do a nandroid backup fine without any problems. i believe i am using jf1.42 recovery image, but lets say my phone bricks, whatever nandroid backed up for me, how do i install it back again? n00b question i know but ive searched around and havnt found that answer yet.
Click to expand...
Click to collapse
Here's a quick and easy explanation: http://androidcommunity.com/forums/168953-post6.html
I've tried the Nandroid back up, but for the life of me I can't get ADB working on my computer. Is there a script to run it through recovery mode or through the terminal emulator?
Thanks
Hi Aim beta is still available in the market (Is it different from hello AIM beta?) and wifi tether for root users is still available at google code. If there was a program that I wanted that was no longer available I would just back it up to SD before wiping. For SMS I use SMS backup. That way SMS streams are available all the time in my gmail (not that I consider my SMS messages all that important)
Settings take me a little while to get back but usually if I am wiping to put on a new ROM my workflow will change a bit so redoing settings from scratch is not a big deal.
Given that contacts calendar and mail are synced with gmail, wiping is less a concern for me than it was with WM. Reloading apps takes a bit of time but it is not a major effort since most things are either on the market or on my SD.
...what everyone else said.
Also, I use fastboot on the computer side (Windows XP) to get Nandroid's backups back on my phone. This only works if you have the engineering bootloader, though (the thing with the three skateboarding androids). First, you'll have to copy "boot.img," "data.img," and "system.img" to whatever folder fastboot's in. Open up your command prompt. The command line you use is this:
cd *whatever directory fastboot's in*
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
I use nandroid and mybackup pro.
Heres a question for the ages. If i do a nandroid backup on say...JF's 1.5ADP and then update to Haykuros image, after a wipe, would i have a problem if i was to fastboot flash my data.img file? Would it cause problems? I have yet to try it.
Does mybackup pro back up paid apps?
I dont really care about my txt i mean i got alot of txt but nothing to much to be save..I use appmanger to save my .apk apps to sd. and contacts are sync to google so yeah thats all i do.
If you have apps to sd it's as easy as following any apps to sd tutorial. All your apps that are already on your sd card will pop right back into your phone. In case anyone didn't know this. I tried and found out that it worked. So PM me for more details. I can't do much right now. But I can let you know what commands to type in adb shell or terminal emu.
Using the apps to sd, once I set the links up, everything is back, although my protected apps show up as the .apk name as with a gear icon. I have to uninstall then re-install those. But I am looking around for ways to remedy that. I think I found one post, but haven't wiped since I found it.
As per my title, I'm getting this error message constantly after restoring my most recent backup of CM9 RC2. This was shortly before I started testing other ROM's (Hydro and CleanROM). The message comes back every single second, and I can barely get taps inbetween. Shutting the tablet off is a chore.
There are numerous threads on this error but they are all problems occurring on phones, not tablets, so I felt it appropriate to re-post. Any ideas to get this to go away? I don't have another recent backup so I'd like to be able to fix this without having to re-do all my work
Pertinent information:
Was using TF300T with CM9RC2 beforehand. Made nandroid backups, began testing other ROM's that required me to revert back to stock a few times. Have already tried restoring backup after factory reset, with cache and dalvik wiped. Pushing files to tablet on a Windows 7 PC using ADB, and everything on that end works fine. Also, if I dismiss the com.android.phone error, there are a number of other processes that have stopped working in the background as well, so the tablet is unusable.
Thanks,
Opethfan89
I've got a minor update to this issue, in that I decided to poke around in one of the backups that I know is a working backup, and found where the com.android.phone process is located (the /data partition, I guess).
So my question becomes, is there a way for me to manually load a nandroid backup and select/choose which files I restore from which folder? So if I get a com.android.phone folder from one backup and combine it into the backup that is messing me up, would that potentially work?
Also, how do I get access to the /data, /cache and other partitions on my tablet? Can I browse them through Windows Explorer or do I have to use Root Explorer on the tablet?
It's been four days, *BUMP*? Any responses?
My suggestion is do a clean install of the rom you want, forget about the backups and see if it works with a fresh install
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
While installing different roms on my device i learned to always do a full delete of cache, delvick cache, factory and last system. Always did it in that order. Maybe there is not very much logic to it since system will do all of it but that's what i did. I'm not sure what kind of recovery your using but I would recommend TWRP, but i doubt that's the issue.
Hope this helped
Thanks for the responses, guys.
I was not able to find a resolution to this error code or why it pops up, but I was able to salvage my install. My titanium backup from the 29th (before this error message was on my nandroid backups) was able to save all my apps, the layout, etc. I had to sit there for 3 hours manually allowing each and every app to install, but thats much better than trying to piece together which apps I had and what order they were in.
That being said, I'm now in the habit of making almost daily nandroid backups and titanium backups, as well as backing up any/all settings at every opportunity.
In response to the last post, I use CWM and I thought I clarified that in my original post. Not sure how/why the backups got corrupted, but I don't blame the recovery.
i get this fc when i change my sim with any other network sim card,maybe the phone has network lock?
Hello,
XT1032 CM 12 latest nightly (I think)
I flashed TWRP v2.8.6.0 using their manager app. I entered recovery mode and everything seemed to work fine. I made a NANDroid backup then rebooted. Unfortunately the device was then stuck at the bootlogo and kept looping. I can still access recovery and fastboot but for some reason adb doesn't see the device, nor can my device's data be access under Windows 7. I don't recall if I had USB debugging on or not. I would like to try to backup a few files to my computer (the backup for instance) but I am unable to since I can't use adb as the device is not recognized. MTP through TWRP doesn't seem to work either. I do have the Universal drive pack installed already on Windows.
Any help would be greatly appreciated. Thanks for your time.
To start with, let's make sure the files you want still exist.
1. Boot into TWRP recovery
2. Go to "Mount" and check that your "Data" partition is selected
3. Go back and then go to "Advanced" and then to "File Manager"
4. Navigate around (maybe /sdcard/ ? Depends what you're looking for) and find the files you need
If you can't find your file, you'll need some more help. Let's say you do see your file. Do you have a USB-OTG cable? You could plug a USB drive into your phone and mount that. Then you could copy your file to that drive. If you don't have the cable you do have some other options, but let us know how far you get.
EDIT: I know I haven't addressed the problem of the bootloop at all. Many of those solutions involve wiping so we need to make sure you've backed up all the files you need first.
First of all thanks for the help. :good:
I've been trying to find a solution and in fact flashing CWM worked. I was able to adb pull all the files and make a backup.
I backed up the content of the sdcard. I tried restoring the CWM nandroid with data only so it did reinstall the apps but unfortunately all their data and settings are gone. Making a full restore just goes back to bricking. So I have the nandroid and the data manually backed up to a computer but no idea how to restore it.
I've tried pushing the nandroid back to /mnt/shell/emulated/clockworkmod/backup after an unsuccessful restore but now it doesn't even work. (protocol failure, the push command fails)
honestly at this point I think the best solution is just to make a clean install. In fact it would be a good idea to just reset the whole phone and start with a clean slate with CM13 including wiping system files and maybe manually restore some key files and configuration (I've got all the .com files of relevant apps)
Do you know how to do that? :laugh:
frustratedwhiteman said:
First of all thanks for the help. :good:
I've been trying to find a solution and in fact flashing CWM worked. I was able to adb pull all the files and make a backup.
I backed up the content of the sdcard. I tried restoring the CWM nandroid with data only so it did reinstall the apps but unfortunately all their data and settings are gone. Making a full restore just goes back to bricking. So I have the nandroid and the data manually backed up to a computer but no idea how to restore it.
I've tried pushing the nandroid back to /mnt/shell/emulated/clockworkmod/backup after an unsuccessful restore but now it doesn't even work. (protocol failure, the push command fails)
honestly at this point I think the best solution is just to make a clean install. In fact it would be a good idea to just reset the whole phone and start with a clean slate with CM13 including wiping system files and maybe manually restore some key files and configuration (I've got all the .com files of relevant apps)
Do you know how to do that? :laugh:
Click to expand...
Click to collapse
I'm not really a Nandroid expert, but I can take a few shots in the dark. When you did your backup you got a TAR file for System and one for Data, etc., right? Then you convert those to IMGs? If you upgraded and then restored the system backup I can see why that would result in a boot loop. Restoring the data image shouldn't cause such problems though. Is this what you've tried so far? You're right, though. The safest method is to manually restore the data of just the apps where you need that data, and do it one at a time. This would allow you to pinpoint what is causing the issue. Of course, I may have no idea what I'm talking about. I've never actually needed to restore a Nandroid backup! Hopefully someone with more experience there will chime in.
I thought to hell with it I went and solved the issue by installing CM13
Thanks for taking the time to help and see you next time
Dear community, I am facing several troubles with my OP7pro which I think can be quite easily handled but my knowledge is just too little.
I am running OOS 10.0.2 with Renovate ICE, rooted with Magisk and on TWRP 3.3.1-70 - stock kernel and normally encrypted. I am facing various troubles that started after upgrading from 9.5.13 tot Android 10. I do not know if they are directly related. I do have Nandroids, BUT the phone is my daily driver, also for work, and a factory reset will just take too much time.
What are the troubles you ask?
- I am not able to enter the menu Buttons&Gestures/navigation/set up navigation bar. The screen blinks and I am back in the upper menu. If I press this menu again I get a "Settings stopped". This sucks, because I want to set up my on-screen buttons
- I used to use Plus Beat in combination with RICE on Android 9. Worked perfect. Whatever I set up, Plus Beat just does not work. That sucks big time.
- I am not able to set on screen buttons to for example switch between recent apps or get anything else but horizontal recents (which is slow and to me sucks). QuickSwitch via Magisk doesn't bring anything.
NOW TO THE QUESTIONS:
I GUESS (! but am not sure!) that a factoryreset could and should solve these problems. I could and would do that, but, I need to be up and running and have my settings back quickly. Internal memory (root) I could copy to PC and paste back afterwords. But is there some way I could put my settings (in the menu) and all my apps (250+) back via Nandroid data?
I have the following things backed up in TWRP:
- Boot
- System Image
- Vendor Image
- Data
- Modem
- EFS
If I do a complete new factory set-up (for example via Maurefranio's tool), to refresh my system (I guess the failure is in there), can I put back other parts of the Nandroid to have all the rest back? Also in the menu-settings, color-setting etc. etc. etc.?
I know it sounds rooky, but I hope someone takes time to help me a little. I do use Titaninium etc. but I can't spend hours and hours on a recovery. In that case I'd probably decide to keep using the OP7pro as I do, but it's frustrating that RICE and Plus Beat don't work fully and some other errors. The usability to me is 4 out of 10 - where in Android 9 it was surely 9 out of 10.
Greetings,
existenz
Are you running a substratum theme? That could be the settings issue. But that's about all I could help with. Never restored anything using twrp on this phone. Most I've done is backup my apps with swift backup, factory reset, or MSM tool, and restore my apps.
How quickly do you need your phone up and running? You could backup with swift backup, factory reset and only restore what you need for now then do the rest when you have time.
@GeekMcLeod: no, Substratum not even installed. All this trouble started after the regular update to Android 10.
But more my question is: IF I flash the whole phone back to factory setting (not a reset because the errors might still be there so a complete whipe and re-flash) - which part of Nandroid is usefull to get SETTINGS and APPS back? Just that. The internal memory I can copy and paste back.
I really hope someone can give me a quick instruction of how this works. Much appreciated!
exis_tenz said:
@GeekMcLeod: no, Substratum not even installed. All this trouble started after the regular update to Android 10.
But more my question is: IF I flash the whole phone back to factory setting (not a reset because the errors might still be there so a complete whipe and re-flash) - which part of Nandroid is usefull to get SETTINGS and APPS back? Just that. The internal memory I can copy and paste back.
I really hope someone can give me a quick instruction of how this works. Much appreciated!
Click to expand...
Click to collapse
In that case, I would just use swift backup, backup to your device. Transfer SD card contents to your computer, factory reset. Transfer SD card files back. Swift backup can backup all apps and data. I believe that would work for what you want.
I, however, do not know what parts of the nandroid do what as I usually just don't bother with it.
GeekMcLeod: appreciate your advise, but Nandroid is there for a reason.
Is there anyone who can please help me what to do best? I mean, one of those Nandroid-partitions holds the clue, right?
I am also facing overnight Batterydrain of about 30% (from 80 to 50 in about 7-7,5 hours).
No Nandroid specialists in the house?
You need to wipe your data. Use Swift to backup apps, messages and call logs. Google will do it's best to restore settings upon setup. Your problem is almost guaranteed to be in data. If you need that data, I would recommend going back to whatever version of pie you were on before. Swift won't restore app permissions, as far as I know so be sure to double check if you restore apps with Swift.
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!