Related
Hello Everyone,
I have not play with any android devices since android 2.0 and even back then found self rooting tools. I got my Kid Nabi2 tablet. Runs Android 4.0.4 currently. Nice little tablet. Problem is only have 8GB or storage. About 4gb after all system partitions and recoveries. So my question is can I safely back up my recovery partition to external source to free up some space? I assume recovery partition has complete recovery files when I do restore to factory option. I I remember correctly android has few partitions. /boot, /system, /recovery, /sd. is there a way just to have your operating system and whatever apps. Have recovery mode but have files on like sd card. If I decide to root this device dose that changes anything in my recovery partition. If device is rooted can I just go back to completely stock by doing factory reset? I just want to make sure that if I root it and want to go back to complete stock for any reason I can do that.
You can restore from your backup that gets made after you flash the custom recovery.
Here is the original script for using on Windows:
http://forum.xda-developers.com/showthread.php?p=32207344
Though you should use the gapps package from http://forum.xda-developers.com/showthread.php?p=35888524 as it gets rid of the 'android upgrading' messages on every boot.
If you want a more manual method, or are on linux, see http://forum.xda-developers.com/showthread.php?t=2016463
t499user said:
You can restore from your backup that gets made after you flash the custom recovery.
Here is the original script for using on Windows:
http://forum.xda-developers.com/showthread.php?p=32207344
Though you should use the gapps package from http://forum.xda-developers.com/showthread.php?p=35888524 as it gets rid of the 'android upgrading' messages on every boot.
If you want a more manual method, or are on linux, see http://forum.xda-developers.com/showthread.php?t=2016463
Click to expand...
Click to collapse
T499user, thank you for replaying. I do run windows. I did look at the section you direct me to me before. What I don't understand is when you root with his program do I use option 1 or 2. Where dose the back up go and how do I restore it later? when I restore dose that bring it back completely to stock, meaning just like it was when i got it? I'm currently running new nabi software do I have to worry about losing wifi?
Also is there a way of freeing up space on my nabi 2 by keeping a back up somewhere else. I think now there is recovery/back up partition. that works when I do factory reset. is that is how that works?
By installing new custom recovery would other recovery still be there?
Sorry trying to get back after many Apple years..
skull791 said:
T499user, thank you for replaying. I do run windows. I did look at the section you direct me to me before. What I don't understand is when you root with his program do I use option 1 or 2. Where dose the back up go and how do I restore it later? when I restore dose that bring it back completely to stock, meaning just like it was when i got it? I'm currently running new nabi software do I have to worry about losing wifi?
Also is there a way of freeing up space on my nabi 2 by keeping a back up somewhere else. I think now there is recovery/back up partition. that works when I do factory reset. is that is how that works?
By installing new custom recovery would other recovery still be there?
Sorry trying to get back after many Apple years..
Click to expand...
Click to collapse
I prefer to do it manually, but if you are going to use the script, use option 2. Then you can install gapps from TWRP using http://forum.xda-developers.com/showthread.php?t=2065878.
The backup that gets created is of the current system state. It is stored in /sdcard/TWRP/backups/*serialnumber*/backupname
No worries about wifi as long as you did all of the OTA updates.
t499user said:
I prefer to do it manually, but if you are going to use the script, use option 2. Then you can install gapps from TWRP using http://forum.xda-developers.com/showthread.php?t=2065878.
The backup that gets created is of the current system state. It is stored in /sdcard/TWRP/backups/*serialnumber*/backupname
No worries about wifi as long as you did all of the OTA updates.
Click to expand...
Click to collapse
Now do I have to install TWRP or when i root it will do it for me?
It will be done with the script.
t499user said:
It will be done with the script.
Click to expand...
Click to collapse
What dose exactly gets back up?
also do you know why nabi2 only has about 4.45gb of free storage when total is 8gb? 3.55gb seems a lot for system files???
skull791 said:
What dose exactly gets back up?
also do you know why nabi2 only has about 4.45gb of free storage when total is 8gb? 3.55gb seems a lot for system files???
Click to expand...
Click to collapse
The system, boot, and data partitions get backed up. That is the way they set it up for the partitions.
All of your questions have already been answered in the other threads, might want to do a search for 'Nabi' and have a read.
t499user said:
The system, boot, and data partitions get backed up. That is the way they set it up for the partitions.
All of your questions have already been answered in the other threads, might want to do a search for 'Nabi' and have a read.
Click to expand...
Click to collapse
T499user trust me I been reading crazy and still cant find an answer. Want to point me to the right place ?
No problem, I would start with the following:
http://forum.xda-developers.com/showthread.php?t=1905674
http://forum.xda-developers.com/showthread.php?t=2016463
t499user said:
No problem, I would start with the following:
http://forum.xda-developers.com/showthread.php?t=1905674
http://forum.xda-developers.com/showthread.php?t=2016463
Click to expand...
Click to collapse
Thank you. I did read all of them. Do you know where I can find something about android system file. Mostly why I have only 4.45gb out of 8. Is thereba way to move back up patition? To external source to free up some space?
Depreciated!! See this thread for the new recommended package. All of my instruction below is still valid, just use the new package from thread linked here.
http://forum.xda-developers.com/showthread.php?t=3234422
~~DISCLAIMER~~Flashing roms, kernels, and mods come with NO guarantee, NONE, ZILCH, NADA . . Do NOT use this package if you do not grasp and understand this concept. You have been warned.
This is a recovery flashable that will extract your boot.img, unpack all pieces, modify fstab.shamu to disable forced encryption, repackage, and flash boot.img back to system. It does NOT actually unencrypt your device. More on that later.
It will work on ANY kernel for this device, regardless of whether it is the stock kernel, or a custom ROM kernel. Also to date, it has shown to work on any version of android . . it is essentially future proof (unless google throws us a major curve ball in the future and radically alters how encryption is triggered at first boot).
Why use this? Who is this package for?
-If you are running 100% Stock Rom, but have a recovery installed and wish to unencrypt your storage. No root needed.
-Running a custom kernel you like, but it forces encryption and you want to change that.
-Currently unencrypted but want to flash a rom that uses FORCEENCRYPTION by default (cyanogenmod12).
-Just bored and want to toss the dice and see what happens.
That is pretty sweet right? Now you can flash anything and as long as you flash this afterwords, you wont have to worry about booting a rom and seeing that dreaded "Encrypting" screen anymore.
What doesn't this do?
-Well, to be blunt . . it does NOT actually UNENCRYPT your device. You will have to bite that bullet on your own, but I will offer some advice on that front later.
Changelog:
03/30/2015
Remove my ill advised attempt to auto patch nightlies, not possible
01/12/2015
Initial Build/Release
Includes fully working patch to initrd, specifically fstab.shamu to revert FORCEENCRYPTION by default.
Buglist:
Auto patch support removed, would never work anywayaddon.d support not currently working - fix is to flash this package with every nightly to preserve unencryption
How to download and install?
Download - NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
Reboot Recovery - TWRP only has been tested as working
Select "Install" and navigate to where ever you stored that file . . likely /sdcard/downloads/
Take a deep breath and wait for it to finish.
TADA . . done. Reboot and Profit!!
NOTE: You can feel free to flash this as part of a line of other packages.
Example: You are already unencrypted and want to flash Cyanogenmod 12 (assumes you have all packages downloaded already)
-TWRP factory reset (optional but recommended when coming from another rom)
--TWRP's built in factory reset function does quite well, but if you are like me and want a clean slate . .
---TWRP>Wipe>ADVANCED WIPE> and check System, Data, Cache (will leave internal storage intact). This is recommened specifically in conjunction with switching GApps.
-Install> and select all packages at once. I recommend the following order . . Rom, then my Kernel Patcher, then SuperSU (optional), then GApps last.
That was certainly easy right? Well the truth is, unless you are already unencrypted . . nothing will be different. You will still be encrypted. Bummer right? But that is where these next steps come in. They will give you the options available to reach the fabled unencrypted status!!
Below are the only three options I know of unencrypt once you are running a patched kernel. Select one below that works for you.
~~WARNING~~
The below methods WILL erase EVERYTHING from data, including your INTERNAL STORAGE. Backup all important files, pictures, etc before proceeding. You have been told!!
-Go to Android>Settings>Backup & restore>Factory data reset (may not work properly with a custom recovery installed)
-Reboot to recovery and go to TWRP>Wipe>FORMAT DATA . . type "yes" to confirm
-Reboot to bootloader and type . .
Code:
fastboot format userdata
[note - I originally said to use the fastboot erase userdata function. This caused a recovery bootloop. Switching to "format" instead solved this issue. Thanks @aussie1234 for pointing this issue out to me]
Edit: make sure you boot android first after unencrypting before going into recovery. This will allow the proper creation of multiuser partitions, otherwise, twrp will not use the proper /data/media/0/ as root of storage.
Some may notice there is an experimental addon.d included. This NOT WORKING YET. DO NOT TRY AND USE IT. Not quite sure yet where in the chain it is broken, but that will be a problem for another day. In theory it should, but . . read the "disclaimer" at the top of this post. The idea here is to be able to flash nightlies as they roll out without having to re-apply this patch manually every time. This function is NOT supported on Stock Roms. If you try it and it works, let me know. Do NOT come yelling to me that it did not work and crying that you are now encrypted again. No whiner babies allowed.[REMOVED: didn't work and caused conflicts with some packages]
At the core of this tool is a script build by @dk_zero-cool which can be found . . [DEV][INITRD][2013-10-25] Injector - An Android Ramdisk Injection Tool
Ultimately, this package is as much his as it is mine. It is his magic script that did the hard part, I just put it to work in a new way.
Please don't share this package directly, link them back here if needed. That way, they can get proper support and instruction for its use.
Also thanks to @rascarlo . . his github made it easy to find what needed modded.
Nice! Now just to double check, im unencrypted so if i flash cm12 and this cm12 wont encrypt my phone while still using cm's kernel?
That is correct. In my tests it has worked just fine that way.
Edit: In fact, I just tested this exactly and works as expected.
On a side note, I can confirm that addon.d support does NOT work - do not attempt it. I updated the OP to reflect this and add a stronger warning. Right now you MUST flash this everytime you flash a rom that forces encryption.
Just what the doctor recommended for a flash-addict like my self....
Thanx :silly:
. . . uploaded from a hand-held Killer WHALE
Works like a charm much alohas bradah hixanthus
So say I flash a ROM. I want to do ROM, kernel, your boot.IMG, the gapps followed by a factory reset/erase user data if I understand correctly?
Example : DirtyUnicorns then leankernel your zip and then gapps
bmwh0r3 said:
So say I flash a ROM. I want to do ROM, kernel, your boot.IMG, the gapps followed by a factory reset/erase user data if I understand correctly?
Example : DirtyUnicorns then leankernel your zip and then gapps
Click to expand...
Click to collapse
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
hlxanthus said:
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
Click to expand...
Click to collapse
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
bmwh0r3 said:
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
Click to expand...
Click to collapse
Just do the factory rest then if already encrypted unless data is removed it will stay encrypted
Sent from my Nexus 6 using Tapatalk
hlxanthus said:
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
Click to expand...
Click to collapse
bmwh0r3 said:
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
Click to expand...
Click to collapse
hlxanthus said:
Below are the only three options I know of unencrypt once you are running a patched kernel. Select one below that works for you.
~~WARNING~~
The below methods WILL erase EVERYTHING from data, including your INTERNAL STORAGE. Backup all important files, pictures, etc before proceeding. You have been told!!
-Go to Android>Settings>Backup & restore>Factory data reset
-Reboot to recovery and go to TWRP>Wipe>FORMAT DATA . . type "yes" to confirm
-Reboot to bootloader and type . .
Code:
fastboot erase userdata
Edit: make sure you boot android first after unencrypting before going into recovery. This will allow the proper creation of multiuser partitions, otherwise, twrp will not use the proper /data/media/0/ as root of storage.
Click to expand...
Click to collapse
https://github.com/imoseyon/leanKernel-shamu/commit/58ac4f97d882414bdea35d0d1ef0cd6f9027a3bb
Yes, lean kernel doesnt force encryption. If you are currently on lean kernel, so one of the three methods to unencrypted from above (quoted from my OP)
This worked great for me! Thank you SO much!
jtorress said:
This worked great for me! Thank you SO much!
Click to expand...
Click to collapse
It really is that simple isn't it? Glad it was of help!!
Mine is encrypted n6 running cm12 nightly .
So flashing this will format my storage or just data partition ?
I dont wanna loose my personal data's :/
This will not wipe anything. The package only turns an encryption forced kernel into a no force encryption kernel. It is then up to you to follow one of the three options from my OP to reach actual unencryption status.
But you can relatively easily do it, though it will take a little time. Boot to recovery, flash my package, and then create a nandroid backup. Then backup the entirety of your internal storage to your PC or OTG storage device. Once that is done, do one of the 3 methods to unencrypt. Once you do that, boot android (this step is important as it builds proper multiuser partitions) then restore data to your internal storage. Then boot back to recovery and restore your nandroid backup. That will take you back to the exact point you were before but now unencrypted.
I did all steps,but it still shows me that I'm encrypted. What am I doing wrong?
indigo888 said:
I did all steps,but it still shows me that I'm encrypted. What am I doing wrong?
Click to expand...
Click to collapse
Walk me through in your own words what you did. Maybe we can figure out where you went wrong.
hlxanthus said:
Walk me through in your own words what you did. Maybe we can figure out where you went wrong.
Click to expand...
Click to collapse
I flash package and made nandroid backup in recovery.Then made factory reset and boot Android till welcome select language. Then switched off into recovery and restored backup....
And when you say you did a factory reset, how did you do that? A twrp factory reset will not work as it leaves the internal storage in tact. I am very explicit on the 3 ways to do this part (at least I thought I was).
hlxanthus said:
And when you say you did a factory reset, how did you do that? A twrp factory reset will not work as it leaves the internal storage in tact. I am very explicit on the 3 ways to do this part (at least I thought I was).
Click to expand...
Click to collapse
I did it from menu/settings/backup and reset.
indigo888 said:
I did it from menu/settings/backup and reset.
Click to expand...
Click to collapse
Might be worth trying the other two methods as well. TWRP's format data method and the fastboot userdata method are pretty thorough. Should get you up and running
As you know TWRP on our phones allows us to instantly switch between ROMs, backup, etc. instantly. It's like an image based backup for our android devices. And exceptionally handy when wanting to try out different ROMS (Firmware here I guess). I have TWRP recovery installed and I was able to get it to see my nandroid online TWRP backup. I had to run a backup in twrp to see the directory it wanted as It would not let me specify the directory. Turns out it is /mnt/external_sd/TWRP/BACKUPS/n70 for my device when choosing the external option. So I went ahead and confirmed the format of that backup is the same as the online nandroid TWRP backup and it is (mtd.win, ext4.win) so I went ahead and moved boot, cache, data, kernel, and system to that n70 directory. Beautiful TWRP recovery sees them! Making progress, I think. (See pic)
Then I go to restore this and I am met with "Unable to wipe data using function call". FAIL! Anyone have any idea what I may be able to do to make this work? I did check permissions of the TWRP backup directory to ensure all was well and it was. Perhaps TWRP doesn't have access to write to /data? I doubt that, perhaps this is an easy fix and TWRP can actually work well on these devices?
NOTE, you cannot backup from TWRP recovery as it shows /data as 0MB. Which may be part of the reason I get an error during TWRP restores?
Dave
Lets hope one of the dev's pick this up as this would be a great addition to help make life easier!
I agree. I couldn't even decompile the recovery. I fail!!
Dave
so nobody has any desire for this to work?
I pushed for having a working TWRP when these units first came out. The issue is none of the ROM makers have had the desire to move to this type of system for releasing ROMs, so all updates to the ROM force you to flash back the factory recovery to update you ROM, which makes it a PIA anytime you want to update.
fortunately the flash back to stock recovery is easy but twrp is so nice im surprised they aren't wanting to move to it. The backup/restore functionality is amazing as well.
Dave
I would love for them to goto this style of updating as it would make upgrades so much easier as well as could use things like Aroma Installer to keep me from having to nuke half the apps I do not use with Titanium Backup. For example the only stock apps I use are Bluetooth and Radio. And most of the other crap found in the latest roms, I kill as well as I do not use them.
I am so down for this! Would definitely donate to make it happen. Promise. Ask @Malaysk
as would I.
I also like to pay with PayPal ready
TT_Vert said:
As you know TWRP on our phones allows us to instantly switch between ROMs, backup, etc. instantly. It's like an image based backup for our android devices. And exceptionally handy when wanting to try out different ROMS (Firmware here I guess). I have TWRP recovery installed and I was able to get it to see my nandroid online TWRP backup. I had to run a backup in twrp to see the directory it wanted as It would not let me specify the directory. Turns out it is /mnt/external_sd/TWRP/BACKUPS/n70 for my device when choosing the external option. So I went ahead and confirmed the format of that backup is the same as the online nandroid TWRP backup and it is (mtd.win, ext4.win) so I went ahead and moved boot, cache, data, kernel, and system to that n70 directory. Beautiful TWRP recovery sees them! Making progress, I think. (See pic)
Then I go to restore this and I am met with "Unable to wipe data using function call". FAIL! Anyone have any idea what I may be able to do to make this work? I did check permissions of the TWRP backup directory to ensure all was well and it was. Perhaps TWRP doesn't have access to write to /data? I doubt that, perhaps this is an easy fix and TWRP can actually work well on these devices?
NOTE, you cannot backup from TWRP recovery as it shows /data as 0MB. Which may be part of the reason I get an error during TWRP restores?
Dave
Click to expand...
Click to collapse
AFAIK its already been done, a year or 2 ago.
If I remember correctly it was working but it wasnt compatible with the way the MTCB updates work or something, did you search the original thread ?
Whilst I use TWRP on my phone I never tried it on my head unit or saw the need for it personally.
@Dees_Troy or @Captain_Throwback are the only guys I know capable of doing it. Maybe if they could give a hand. I have attached the 800x480 5.1 recovery if they would be so kind.
The wiki says its "now working perfectly" and gives a link to TWRP for Rockchip devices in a Freaktab post from 2014.
As I said earlier I m sure there was some reason why not many people use it, possibly to do with not being able to flash the MCU in TWRP or something.
Has anyone actually searched the original thread yet ? (theres only 11 pages to read through if you search "TWRP").
typos1 said:
The wiki says its "now working perfectly" and gives a link to TWRP for Rockchip devices in a Freaktab post from 2014.
As I said earlier I m sure there was some reason why not many people use it, possibly to do with not being able to flash the MCU in TWRP or something.
Has anyone actually searched the original thread yet ? (theres only 11 pages to read through if you search "TWRP").
Click to expand...
Click to collapse
Can you link me to the wiki? the only one i could find was the huifei one with no info re twrp
are you referring to http://freaktab.com/forum/main-category/freaktab-downloads/11780-twrp-2-7-0-0-for-rockchip-s
cos they are plagued with issues and use the kitkat base
When I use it it backs up a 0MB apps daa folder each time. You could always very quickly swap back to stock recovery for flashing of ROM'/MCU. It never worked for me properly and I don't see any indication anyone actually backed up and restored w/ TWRP. I provided the screen shots of what error was generating while backing up somewhere. It certainly does not restore an online nandroid TWRP backup either.r.
Dave
TT_Vert said:
When I use it it backs up a 0MB apps daa folder each time. You could always very quickly swap back to stock recovery for flashing of ROM'/MCU. It never worked for me properly and I don't see any indication anyone actually backed up and restored w/ TWRP. I provided the screen shots of what error was generating while backing up somewhere. It certainly does not restore an online nandroid TWRP backup either.r.
Dave
Click to expand...
Click to collapse
miffymiffy said:
Can you link me to the wiki? the only one i could find was the huifei one with no info re twrp
are you referring to http://freaktab.com/forum/main-category/freaktab-downloads/11780-twrp-2-7-0-0-for-rockchip-s
cos they are plagued with issues and use the kitkat base
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/Hui_Fei_Type (under "Recovery)
That looks like the page from Freaktab @miffymiffy
Have either of you read all the posts on TWRP in the original thread to get a handle on the TWRP situation for MTCB head units ?
look like somebody also looking for TWRP on Joying HU. I'm also looking on it but seem to be not so much people interested on it. I dont mind that TWRP wont update the MCU but most important it can backup the whole rom & can restore back the rom exactly what it left previously.
does the below TWRP link work for RK3188 1024x600(seem like for RK3088 CPU)
http://huifei.fs-fileserver.de/content/firmware/KK 4.4.4 Dualcore Coudu Rooted /TWRP/1024x600/
lysiong said:
look like somebody also looking for TWRP on Joying HU. I'm also looking on it but seem to be not so much people interested on it. I dont mind that TWRP wont update the MCU but most important it can backup the whole rom & can restore back the rom exactly what it left previously.
does the below TWRP link work for RK3188 1024x600(seem like for RK3088 CPU)
http://huifei.fs-fileserver.de/content/firmware/KK 4.4.4 Dualcore Coudu Rooted /TWRP/1024x600/
Click to expand...
Click to collapse
Dont know sorry, but TWRP will be the same for ALL MTCB and MTCC hedunits, plus there are no "Joying" headunits, Joying are sellers only, they sell Joyous and other MTCB, MTCC and MTCD headunits.
lysiong said:
look like somebody also looking for TWRP on Joying HU. I'm also looking on it but seem to be not so much people interested on it. I dont mind that TWRP wont update the MCU but most important it can backup the whole rom & can restore back the rom exactly what it left previously.
does the below TWRP link work for RK3188 1024x600(seem like for RK3088 CPU)
http://huifei.fs-fileserver.de/content/firmware/KK 4.4.4 Dualcore Coudu Rooted /TWRP/1024x600/
Click to expand...
Click to collapse
just try it, totally not working , blank screen come out when boot into recovery :crying:. Lucky still can restore back previous working recovery.
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?
Hello I have a rooted phone with official miui12 rom.
TWRP is flashed but I can also run TWRP using adb.
How can I flash the New miui13 stock version ? Do I use the official Xiaomi flash tool? Or do I use TWRP to flash the stock rom?
iostrym said:
Hello I have a rooted phone with official miui12 rom.
TWRP is flashed but I can also run TWRP using adb.
How can I flash the New miui13 stock version ? Do I use the official Xiaomi flash tool? Or do I use TWRP to flash the stock rom?
Click to expand...
Click to collapse
Through fastboot, you should use the fastboot ROM, and through TWRP, you should use the recovery ROM.
Thanks. A preferred option ?
Using TWRP do I need to erase stuff before or can I install directly the rom and this is all ?
I guess that recovery room is not the one provided officially by Xiaomi, right ? It the same but packaged a different way ?
Do you know if SD card will be erased during the stock rom flashing process ?
I see on official Xiaomi site that official rom is quite old. Miui11 version so I guess I will need to perform a lot of OTA update... Can I trust recovery rom provided on other websites to have the latest stock rom version ?
iostrym said:
Thanks. A preferred option ?
Using TWRP do I need to erase stuff before or can I install directly the rom and this is all ?
Click to expand...
Click to collapse
Normally, you don't need to erase data, as they just update without erase per se.
iostrym said:
I guess that recovery room is not the one provided officially by Xiaomi, right ? It the same but packaged a different way ?
Click to expand...
Click to collapse
As I said you, there are two official versions, the fastboot and the recovery ROM.
iostrym said:
Do you know if SD card will be erased during the stock rom flashing process ?
Click to expand...
Click to collapse
No.
iostrym said:
I see on official Xiaomi site that official rom is quite old. Miui11 version so I guess I will need to perform a lot of OTA update... Can I trust recovery rom provided on other websites to have the latest stock rom version ?
Click to expand...
Click to collapse
The OTA updates come, either in form of fastboot or recovery ROM, when Xiaomi provides an update, you will, also, find the minimal OTA package, yet included in the whole ROM.
In this site, you will find the most up-to-date releases https://xiaomifirmwareupdater.com/archive/miui/joyeuse/
thanks. I would like to be sure that my flashed TWRP will be erased during the process, will both flashing process (fastboot or TWRP) erase all my phone and put in a new "clean" state ? (except maybe for sdcard content)
iostrym said:
thanks. I would like to be sure that my flashed TWRP will be erased during the process, will both flashing process (fastboot or TWRP) erase all my phone and put in a new "clean" state ? (except maybe for sdcard content)
Click to expand...
Click to collapse
Nope, both the processes, don't wipe per se, either through recovery or fastboot, in the Mi Flash tool, there is an option to format data, if you like it, if not, it remains un-ticked.
Sorry to insist but what are you calling 'data' ? Is it the SD card content (I don't think so) or is it the data partition on my internal memory ? So it could be :
Photo taken in internal memory
Data stored by apps like photo from WhatsApp or stuff like that ?
Temp file of each app like settings of app, etc.
Would it be a problem if I erase all my phone and loose all my apps but data off app are still there, it will take space for nothing right ?
What about flashed TWRP? will it be removed by the flashing process ? I think TWRP is flashed in recovery partition but not sure.
As you see I'm not familiar with android partition even if I did several times this kind of process with different phones.
iostrym said:
Sorry to insist but what are you calling 'data' ? Is it the SD card content (I don't think so) or is it the data partition on my internal memory ? So it could be :
Photo taken in internal memory
Data stored by apps like photo from WhatsApp or stuff like that ?
Temp file of each app like settings of app, etc.
Would it be a problem if I erase all my phone and loose all my apps but data off app are still there, it will take space for nothing right ?
What about flashed TWRP? will it be removed by the flashing process ? I think TWRP is flashed in recovery partition but not sure.
As you see I'm not familiar with android partition even if I did several times this kind of process with different phones.
Click to expand...
Click to collapse
Not exactly what I call data, but, what data means in Android World.
Formatting data, it's deleted all the data from apps stored in /data partition, all the data regards settings, all the apps installed by the user, general configurations and all the data stored in internal storage, also the system apps uninstalled by the user can come again.
As per the SD Card, if you have one inside, it is not touched in the process.
If you flash the recovery ROM using TWRP, it won't be overwritten, if you flash the fastboot ROM, you'll lose the access to TWRP.
Thanks. Tell me if I'm wrong but if a choose to flash stock miui 13 version whereas I'm currently in miui12 I should maybe erase data also ? Maybe apps won't works again from 12 to 13 version ? I should be cleaner to reinstall them again don't you think ?
About fastboot stock rom isn't it strange that the official website provides only miui 11 rom whereas your site has miui13 version? How is it possible ? For recovery rom I understand because people can backup their phone and could create a recovery rom like this with miui13 after doing the ota. But for the fastboot rom, if Xiaomi don't provides it and provides only miui11 one, where does the miui13 come from ?
iostrym said:
Thanks. Tell me if I'm wrong but if a choose to flash stock miui 13 version whereas I'm currently in miui12 I should maybe erase data also ? Maybe apps won't works again from 12 to 13 version ? I should be cleaner to reinstall them again don't you think ?
Click to expand...
Click to collapse
It would work even if you don't erase data, but, I personally prefer erasing it, to avoid some lags/bugs in the future.
iostrym said:
About fastboot stock rom isn't it strange that the official website provides only miui 11 rom whereas your site has miui13 version? How is it possible ? For recovery rom I understand because people can backup their phone and could create a recovery rom like this with miui13 after doing the ota. But for the fastboot rom, if Xiaomi don't provides it and provides only miui11 one, where does the miui13 come from ?
Click to expand...
Click to collapse
Firstly, be sure that your device is Joyeuse.
All the updates, either recovery and fastboot ROM, are provided by Miui, all of them are official updates, not uploaded from users´ devices.
It's A12, not A13, I don't think your device see the light on A13.
Yes android 13. But miui 13 comes with android 12 and my current os is miui12 that comes with android11. (If I'm correct).
I have Redmi note 9 pro, M2003J6B2G (photo is 64M). I don't know where Curtana or joyeuse word can be really found in my phone but after some readings I had the feeling that M2003J6B2G = joyeuse version.
iostrym said:
Yes android 13. But miui 13 comes with android 12 and my current os is miui12 that comes with android11. (If I'm correct).
Click to expand...
Click to collapse
Xiaomi also could update the Miui version, so Miui 13 came with Android 11 for some devices, don't stay there, just check the Android version that is specified in a tab, at the download list.
iostrym said:
I have Redmi note 9 pro, M2003J6B2G (photo is 64M). I don't know where Curtana or joyeuse word can be really found in my phone but after some readings I had the feeling that M2003J6B2G = joyeuse version.
Click to expand...
Click to collapse
There are some apps like Device Info and other similar, from Play Store that can tell you, exactly, which your model is, Anyway, Redmi Note 9 Pro is Joyeuse but, be sure, before to proceed, consult some app like the mentioned.
SubwayChamp said:
Xiaomi also could update the Miui version, so Miui 13 came with Android 11 for some devices, don't stay there, just check the Android version that is specified in a tab, at the download list.
There are some apps like Device Info and other similar, from Play Store that can tell you, exactly, which your model is, Anyway, Redmi Note 9 Pro is Joyeuse but, be sure, before to proceed, consult some app like the mentioned.
Click to expand...
Click to collapse
Cpu-z indicate joyeuse-eea. Should be good.
Ok so I will delete the data partition and I will use fastboot flash using Xiaomi tool. I'm not sure to understand your answer about the SD card. Will it be erased during the process ? I know that sdcard are now crypted so that they could be used only by my phone. If the os is modified, maybe I won't be able to read it even if it is not formated. Don't you think ?
iostrym said:
Cpu-z indicate joyeuse-eea. Should be good.
Click to expand...
Click to collapse
Good, then it is the european version.
iostrym said:
Ok so I will delete the data partition and I will use fastboot flash using Xiaomi tool. I'm not sure to understand your answer about the SD card. Will it be erased during the process ? I know that sdcard are now crypted so that they could be used only by my phone. If the os is modified, maybe I won't be able to read it even if it is not formated. Don't you think ?
Click to expand...
Click to collapse
Just to not confuse, sdcard is the internal memory, that is symlinked as /data/media/0, all the internal memory is gone when we format data, some folders are recreated at the first boot, after performing it.
SD Card refers to Secure Digital card, that is an external media storage, it is absolutely excluded to any operation from Android, when flashing, updating the system or formatting data, of course, you should consider that some apps like camera can store its pictures there, previous authorization from user, but they will stay there yet, and some folder can be created too, at the first boot, but nothing that harms.
Just to know, sdcard as internal memory is not encrypted at all, it's accessible for any user, always, that can bypass the locking feature of the choice of the user, i.e. PIN, pattern, etc.
Thanks I didn't know that sdcard and SD card weren't the same. My concern is about external memory card (SD card). If not formated. I'm afraid that it couldn't be used after reboot. Except if the decryption key is linked to my phone (hardware) and not the software part (os) of my phone
iostrym said:
Thanks I didn't know that sdcard and SD card weren't the same. My concern is about external memory card (SD card). If not formated. I'm afraid that it couldn't be used after reboot. Except if the decryption key is linked to my phone (hardware) and not the software part (os) of my phone
Click to expand...
Click to collapse
The encryption is permanent since A6, it remains, at least, you can do something about it, using a custom recovery, a custom module, script, or something, nothing that the end user can worry about, for the normal use of the device.
Trying to guess, you did encrypt your SD card, then the encryption key is linked, only to your SD card, the SD card, specially, in newer Android versions, is treated as a privacy media user concern, so every time more, apps can't access to, as easy as the older times, it is RO by default.
Sorry I have difficulties to read and understand your last message as my English is bad.
Especially the second part... I don't encrypt anything myself. I just now that recent version of Android encrypt the sdcard and it couldn't be used in a computer for instance or another phone. So I think that maybe after new rom flashed. SD card won't be read or write from the phone and I will have to format it myself so that I can read it from my phone. Correct ?
iostrym said:
Sorry I have difficulties to read and understand your last message as my English is bad.
Click to expand...
Click to collapse
Probably my English is worse than yours.
iostrym said:
Especially the second part... I don't encrypt anything myself. I just now that recent version of Android encrypt the sdcard and it couldn't be used in a computer for instance or another phone. So I think that maybe after new rom flashed. SD card won't be read or write from the phone and I will have to format it myself so that I can read it from my phone. Correct ?
Click to expand...
Click to collapse
You are again mixing the terms, in the first part, you're saying "...recent version of Android encrypt the sdcard" and linking to the second part, you're saying "...after new rom flashed. SD card won't be read or write"
As I said to you previously /sdcard AKA internal storage is not encrypted at all, at any time, the fact that you need to authorize the MTP connection within your device and a PC, doesn't change that, if you or anyone else, have access to the Android interface, then you or anyone else, can see all the data/files/pictures/audio/video stored, in the internal storage, by using a file manager app, or a specific app for every file instance/format, i.e. a music player for videos/sounds/musics, a gallery app for pictures/images, and so on.
As per the SD card, the same, if the user (you, in this case), didn't encrypt it, then, Android, also, doesn't encrypt it, so you and anyone else, can access to the data stored in it, either during the OS functioning normally, and/or after the flashing/formatting process.