So while i know how to normally backup and restore phones or apps through any number of different applications or recovery software. I had an issue today where i need to backup the state of the phone as it is now, and thrn modify or test with it on an emulated device (if possible, i was thinking my laptop runninng aosp android via some form of emulation.)
Is this possible? What is the difficulty of it?
What i would be taking the device backup from is a nexus 5 with lollipop, and then from there using that as a base, figure out what is going on with the software.
i had that same problem .. and i found a way to backup bootloader and recovery partitions, and i applied it to all partitions and it worked
http://www.theandroidhow.com/2014/05/how-to-make-backup-stock-boot-recovery.html
i had a trouble using flashtool, till i realized the flashtool version itself wasnt good
so i recommend
SP Flash Tool v3.1328.0.183: https://doc-14-c4-docs.googleuserco...8341683716159190/0B_r6upjBMmyGWWpSZHRmTHJLa0k
you will also need
mtkdroid : http://www.mediafire.com/download/w55w2j3l18nt1ws/Mtk_Droid_Tool_v2.5.3.rar
the method in the 1st link is illustrated for bootloader and recovery partition, i used it to backup all partition includidng system(android partition) and other partition i have no idea what are they, i just dont like to lose a useless digit
NOTICE: i didnt try it in restoring , but i think it works like bakcup/restore process of pc HDD
Hi all,
I m facing a trouble with my Honor 9
I first installed the TRWP and magisk on my stock rom. After a day or two my files in the internal storage were been encrypted (except when I look them into twrp). I tried to flash and restore to stock but he didn't let me access to write on the internal storage. I try to move the update.app in the dload folder but it's too big for the fat 32 partition. I tried to extract the recovery.img and the system.img to reflash them with twrp but error each time. Tried to flash the zip directly error on 2 on 3. I tried to flash lineage 14.1 it s flash good until the end but the phone stops and make black screen re-enter after the booting message on bootloader and after 5mn its overheating. Tried another custom rom but it did the same... Any help of what I can do?
I can't restore by wiping its tells me no OS present
EDIT : I was finally success to be able to access back to normal with the HWOTA method. I was able to access to my sd card by a HUAWEI p8 lite 2017, i copied files onto instead of place them on the computer, it works i installed first the B130 update but the back buttons weren't working, finally did again the process with the B120 and it fixes all my troubles. Don't forget to format data one time to not be in my situation of encryption of system storage without a first official update (i have read that if you update your phone the encryption will be disabled because it's by default enabled.
Thanks to all this community because i found the solution here on the Rebrand Honor 9 Thread. Even if i had no answer here, i had to thanks all devs here who make a lot of hard work
You can now close this topic, I can't find where to close it by myself.
I´ve tried to find any specific info on the subject for this phone but found none.
Maybe someone can help.
All was good on my phone when using Havoc custom rom. Yesterday I tested an android 11 custom rom on the device but decided to go back to 10. Orange Fox recovery restore gets stuck in the boot process. When using TWRP it can´t acess Data partition, so I´m unable to make any backups of data partition with it.
I´ve tried two diferent versions of either, and on TWRP after formating data the partition is once again acessible, but as soon as I flash a custom rom (tried two diferent one´s), boot to it and then reboot to recovery the Data partition is once again unacessible (encrypted) showing "0 MB".
Orange Fox recovery allows to access the data partition and so allows for backups to be created, but the restore process always ends up suck at boot (odly enough when enabling MTP on Orange Fox and connecting the phone to my Windows 10 machine two internal storage partitions appear in Explorer along side the SDCard one - all with the same content exactly). Something weird is going on here.
I´ve tried the steps on this post regarding DM verify (I do not know if it has got something to do with it) but it did not work (the fstab file already shows decryption on its entries):
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
Has anyone had similar problems or knows what might be going on on my device?
Is the internal flash memory going bad maybe? I´m at a dead end here.
Apreciate any idea.
Thank you.
I am a bit of a scaredy cat, and I don’t want to pollute the GSI thread with this question.
OnePlus is not offering fast boot flash images for their Nord 2. And the only way to get a custom rom is by flashing a custom vbmeta image and a system image for GSI.
The question now arises, how could one come back from a GSI into stock? I would assume I would need to do ADB push/pull and copy the whole system NAND to a file, then restore that if needed.
Would that be true? Or are there better / faster / safer ways to turn the phone to stock?
I have not yet received my unit, but i want to start tinkering with it as soon as I get my hands on it. So I want to know if there are any ways to undo any and all modifications i would do to the system.
Cheers
Can't twrp backup as system.img
ajaz35 said:
Can't twrp backup as system.img
Click to expand...
Click to collapse
I am unsure if this is being worded as a factual statement, or as a question.
I am telling that TWRP Backs up system as System.img in most Phones.
Same should apply to Nord 2.
ajaz35 said:
I am telling that TWRP Backs up system as System.img in most Phones.
Same should apply to Nord 2.
Click to expand...
Click to collapse
It should apply, but there's the issue of backups needing to be bit-perfect to ensure not to upset dm-verity
I have however found a bunch of commands that i will be testing in about 6 days, once i receive the terminal. I will be placing them for future reference, and for any poor souls who may need this:
Code:
adb backup --twrp -f /directory/to/save/dump.db
Not exactly my cup of tea, but this should combine bit-perfect system and vendor images with space-saving regular file copies of other lesser i mportant partitions, and ignoring the /data/media partition. Should be good enough.
Code:
adb root
adb shell 'dd if=/dev/block/mmcblk0 2>/dev/null' > mmcblk0.img
These two commands should, on an ideal world, with debugging enabled on the target device, and from within TWRP, create a bit-perfect copy of the entire nand and leave them on the CWD. however, the path may differ from what i've found, different chipset and all. However, that's nothing that a good old
Code:
lsblk -l
won't solve. The tricky bit will be actually pulling the file back. Since redirects can seemigly be used to copy the image file to the CWD, redirects may be able to be used to write to disk remotely. This one requires more research.
Alternatively, i will need to buy an OTG cable, get a large enough flash drive, and mount it for the purposes and DD'ing the file out and into the device. If all else fails, with 8GB of RAM it should be able to store 1/16 of the total NAND flash onto ram and slowly stitch the nand in chunks. Not shore how well would that go, too many points of failure. But keeping this for my own musings.
Another possible answer would be to boot into TWRP, running
Code:
lsblk -l
to see all the mount points, and using
Code:
adb push / adb pull
on each of them. Research indicates one can't copy the whole NAND this way, but individual partitions. Should suffice as long as the subsequent coopies are bit-perfect. Assuming one can push the generated image back, this may be the most satisfactory answer.
I will attempt to perform these tasks when i receive the phone and see if it can successfuly restore it's own backup.
ajaz35 said:
I am telling that TWRP Backs up system as System.img in most Phones.
Same should apply to Nord 2.
Click to expand...
Click to collapse
Additionally, one should note that i intend on fully backing up the NAND of the device. Just the system partition is insufficient. as there may be updates on the way that may make restoring the system partition from an OTA image impossible. Therefore, a full NAND copy is needed. altnernatively, if a low-level copy cannot be achieved, individual bit-perfect copies of individual partitions will need to suffice, and hoping no GSI or custom rom maniulates any of the protected partitions.
Do you flash the system.img from my backup?
Oneplus Nord 2 Oxygen 11.3 DN2103 EEA ROM
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! Downloads: The Fastboot restoration file can be downloaded in here: DN2103_11_A.07 DN2103_11_A.10 *deleted DN2103_11_A.11 *deleted...
forum.xda-developers.com
sakarya1980 said:
Do you flash the system.img from my backup?
Oneplus Nord 2 Oxygen 11.3 DN2103 EEA ROM
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! Downloads: The Fastboot restoration file can be downloaded in here: DN2103_11_A.07 DN2103_11_A.10 *deleted DN2103_11_A.11 *deleted...
forum.xda-developers.com
Click to expand...
Click to collapse
As I stated previously. I have yet to receive my terminal. So I haven’t flashed anything yet.
however, disabling dm-verity, installing your system image, see it it fails, and if it fails, backing up, will be a great way to test if my backups are effective.
I want to toy around with your image and PHH’s once I get the terminal. So I’m just trying to preemptively have backups in place for when I inevitably flash something without paying attention and bricking the device.
that reminds me, were you the one who needed a full system dump a few weeks ago on another thread? I can upload my image once I get it working
Edit: just checked it was phhusson who needed the dump. Sorry about the mix up
ZanaGB said:
As I stated previously. I have yet to receive my terminal. So I haven’t flashed anything yet.
however, disabling dm-verity, installing your system image, see it it fails, and if it fails, backing up, will be a great way to test if my backups are effective.
I want to toy around with your image and PHH’s once I get the terminal. So I’m just trying to preemptively have backups in place for when I inevitably flash something without paying attention and bricking the device.
that reminds me, were you the one who needed a full system dump a few weeks ago on another thread? I can upload my image once I get it working
Edit: just checked it was phhusson who needed the dump. Sorry about the mix up
Click to expand...
Click to collapse
I tested rhe gsi Versions, but not good i flash my system.img, dtbo, persist and vbmeta and go back to stock
Just got notified that the phone arrived. So this evening i will get it up and running then worry about backing up later.
Hi. How return the device to stock and lock bootloader? Is there manual?
shnailcheg said:
Hi. How return the device to stock and lock bootloader? Is there manual?
Click to expand...
Click to collapse
Assuming you didn't install any custom ROM, all you have to do is boot onto fastboot and type fastboot OEM lock or fastboot flashing lock. Forgot which exactly.
I have root installed
shnailcheg said:
I have root installed
Click to expand...
Click to collapse
restore your full NAND backup and godspeed
have you tried this method on nord 2?
shnailcheg said:
have you tried this method on nord 2?
Click to expand...
Click to collapse
I made a nand copy but never backed it up.I ended up not needing root for anything and I won't install any ROMs until there's any good ways to have a failsafe for backups. So to all effects I have a backup I haven't tested. I am not gonna risk losing my IMEI or having a zombified phone due to missing blocks on the backup.
To be specific. I have ways to get data OUT of the phone. But I don't have a reliable way to get the data IN and ensure nothing critical is missing or overwritten in the process. And I am too afraid to lose my phone just testing if backups ACTUALLY work.
K
ZanaGB said:
I am a bit of a scaredy cat, and I don’t want to pollute the GSI thread with this question.
OnePlus is not offering fast boot flash images for their Nord 2. And the only way to get a custom rom is by flashing a custom vbmeta image and a system image for GSI.
The question now arises, how could one come back from a GSI into stock? I would assume I would need to do ADB push/pull and copy the whole system NAND to a file, then restore that if needed.
Would that be true? Or are there better / faster / safer ways to turn the phone to stock?
I have not yet received my unit, but i want to start tinkering with it as soon as I get my hands on it. So I want to know if there are any ways to undo any and all modifications i would do to the system.
Cheers
Click to expand...
Click to collapse
Keep nandroid backup evry time you want to go back just restore that nandroid backup using twrp if you gets data restoration error just deselect data emmc win file in backup and restore.
Remember on android 12 gsi twrp data encryption issue so u can't able to access internal storage to restore the backup so first go back to android 11 gsi, now transfer that backup to twrp folder and then boot back to twrp and restore
I personally done this when I stuck on android 12gsi
pankspoo said:
K
Keep nandroid backup evry time you want to go back just restore that nandroid backup using twrp if you gets data restoration error just deselect data emmc win file in backup and restore.
Remember on android 12 gsi twrp data encryption issue so u can't able to access internal storage to restore the backup so first go back to android 11 gsi, now transfer that backup to twrp folder and then boot back to twrp and restore
I personally done this when I stuck on android 12gsi
Click to expand...
Click to collapse
One thing i have been reading from the TWRP Nandroid backups, is that people who install the GSI and then restore, lose their IMEI data and other baked-in addresses.
Is that the case? I would imagine that since TWRP backups aren't bit-for-bit it could cause problems. Have you tested for that?
EDIT: additionally, i guess i absolutely need an OTG adatper to properly restore the backup, since the mere ac of restoring the backup would destroy the backup in the process, wouldn't it?
ZanaGB said:
One thing i have been reading from the TWRP Nandroid backups, is that people who install the GSI and then restore, lose their IMEI data and other baked-in addresses.
Is that the case? I would imagine that since TWRP backups aren't bit-for-bit it could cause problems. Have you tested for that?
EDIT: additionally, i guess i absolutely need an OTG adatper to properly restore the backup, since the mere ac of restoring the backup would destroy the backup in the process, wouldn't it?
Click to expand...
Click to collapse
No if u r on android 12 gsi u need OTG there twrp will not work.
No issue in Restoration on android 11gsi
pankspoo said:
No if u r on android 12 gsi u need OTG there twrp will not work.
No issue in Restoration on android 11gsi
Click to expand...
Click to collapse
So. The way i understand it.
1: Full backup from the stock ROM ( Android 11 Based ) using TWRP
2: Install a GSI, for example, Android 12 GSI
3: In need of going back, first install the Android 11 GSI
4: Once with the 11 GSI installed, recover the TWRP Backup
Would that be correct?
Hi thank you in advance to everyone before hand for your time and assistance.
So I am currently having this issue, I have a Xiaomi Redmi Note 8 Pro, and I installed Ubuntu touch on it a long time ago, and I used to love it however, I realized that the project for that specific model was abandoned since there were no updates, even up to this date it has not received an OTA update and is currently sitting on version 2021/09/21, and despite my efforts to get Waydroid working properly I just managed to get it barely up and running, after seeing no updates, probably due to low demand or usage on that specific device, I gave up and decided to return the device to Android.
It bricked, somehow I managed to get it up and running once more, however on Android using the stock ROM MIUI baseband and IMEI showed as unknown, after looking for a way to restore the IMEI through software, it was possible but it required a backup of the NVRAM and NVDATA partitions, which I did not have access to from Android and sadly I did not back up before installing UT, and the only other solution I found on how to fix it, was through hardware modification which is beyond my level of skill, so I decided to install UT once more to see if it somehow UT had something to do with the IMEI missing on Android, to my surprise on UT the IMEI can be read just fine, it shows on my settings listed and somehow UT is able to communicate with the modem to connect to network through SIM, which makes me wonder if UT encrypts the NVRAM/NVDATA partition in a way that Android can not read it afterwards or just formats in a way that Android can not see it, and this is the reason why I am here.
I need some assistance with the following, in Android is possible to make a back up of the different partitions, and through a rooted device you can re-flash the parameters for the IMEI to restore it, so since UT can read these partitions and files, I need to know if I am able to extract the NVRAM.bin file through UT and the NVDATA.img partition, so that I can after flashing Android back, use this two specific partitions extracted from UT to restore the IMEI on Android. so how can I back up these partitions on UT? is this something even possible? and if possible would these files be compatible with Android?
if you read all the way to this point, I thank you for your time and any advice!
Regards,
having same issue, fortunately i have backup of nvram and nvdata