Persist partition,faulty? - ZTE Axon 7 Questions & Answers

Persist partition,faulty? - ZTE Axon 7 Questions & Answers

Hello guys
Some time ago i flashed DotOS 2.5 with the according bootstack and oki's twrp,and used inbuild party zip to create vendor.
Before i did this,i was sitting on RDX rom 7.1 and i had no any complains.
When i wiped my partitions for setting up dotos,i also mounted persist partition.
After the flash installation of dotos was done,and booted in the system...my battery drops 20% in 3 minutes,and when i put it on charger, it charged 10% in like 4 seconds.
I complained about this in the schwifty group and on xda...and at this moment i still think its software related.
After searching and searching i cam acros a forum on xda that tells the work of any partition
ive read this:
PERSIST - contains data which shouldn't be changed after the device is shipped, e.g. DRM related files, sensor reg file (sns.reg) and calibration data of chips; wifi, bluetooth, camera etc.
Some package installers such as OpenGapps also make use of this partition to read configuration file.
I have the idea,because i mounted persist partition and allowed twrp to change system files....these calibration issues popped up on my device.
Now i want to try to put back stock persist partition....but is that possible? I dont have any backup,and also dont know how to replce this partition.
Is there somewehere a persist partition to download? Or maybe someone can share it that didnt touched ther persist partition?

Related

[Problems & Questions] With Official 2.3 Update V2

Hello !
I am feeling really down today after been trying to get my phone working again.
There is a huge problem currently, I am really annoyed that it doesn't work at all.
First thing, my phone won't start after update it just boot loops and never seem to end it.
First thing I noticed /boot, /cache /system and most things are gone, I can load up recovery but nothing more. I have no idea what happened but the whole image folder was wiped and I had to myself put in the CWM recovery.
I can't do an upgrade "again" as it will be stuck @ the unpacking part without starting it at all.
I been trying with 2.3 V2 and with B133(My stock rom I got).
If anyone has a solution that can solve this problem please help out if you could. Also if you are about to tell me get this and that, please most cases I haven't seen any of the Firmware roms in @modaco wiki links work. Means I can't download them, so if you happen to have spare copy please upload it and link it to me. I have been googling and looking through this section twice, nothing really worked out.
Thanks in advance !

If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.

dancer_69 said:
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
Click to expand...
Click to collapse
Hello, thanks for the reply.
I have no idea about this .cust_backup partition and how I am supposedly to access it via windows. Also the thing you said about fixing partition within Windows, the check disk thing. I am not sure about that part either as I can load CWM and it can read the partitions but they are empty. Also there is nothing in this forums that contains original things, only way for me to fix this if someone have extra copy and can guide me on how and where to place the all needed files. I am pretty sure it's only things that are missing and I can't get a grip out of this.
So to sum up what my problem is.
I did an upgrade from 2.2 to 2.3 with official firmware, it worked out normally but after a reboot my phone became stuck in an endless loop, I can't do anything and it will not I repeat it will not allow me to "re flash" any firmware I tried so far, the 2.3 V2 and B133.
I am begging someone in this forum section, please if you have the knowledge about this problem care to help?
I can't get a refund out the phone warrenty is off and I do not have that much spare money.
Thanks in advance !

If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk

Blefish said:
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Click to expand...
Click to collapse
The most common things I have already done, but do enlighten me what this "custom" parition is. Because in windows I do not see such partition I see a removable partition which I have now added a folder called image with these containing files.
http://forum.xda-developers.com/showthread.php?t=1370960
EDIT ** Also regarding to first person who said about Windows partition manager. The thing is I see a lot of partitions and there is no labeling for them, might be because they are ext2/3 or even something else? In anycase I can't do so much I just find it really odd I have many duplicates and I am guessing that must be errors... Because I am seeing the main recovery partition which has no label too... its at 240 MB where 135MB is used. Lastly there is my internal SD card empty and healthy still I can't reach it within Windows if I do not mount it...And can't now without going into the android OS. I Have loads of free space "partitions I don't understand why they are there".
**
Thanks for helping out, it feels not good to have a half dead phone, it's still not solved :'-(

The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.

dancer_69 said:
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
Click to expand...
Click to collapse
I have placed all things that I got from here.
http://forum.xda-developers.com/showthread.php?t=1370960
And I can't run the upgrade firmware, it gets stuck at first stage which is to unpack the the update.app thing.
It just stays like that not blinking and frozen.

Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.

dancer_69 said:
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
Click to expand...
Click to collapse
You are not understanding me :-(, I have wiped already millions of times in millions of different ways just to get it work. And no, I don't have the device connrected when I upgrade, it won't work properly then, I have tried to wait for the progress bar to "start" move it won't happen the battery will die, and nothing happened.
I can't go in with normal Recovery mode, can only go in with CWM, the normal recovery mode is really small, I mean only 3mb, while the froyo version is 5mb. Now I am asking if you have the time to upload the image files from 2.3 V2, the ones in forums are for V1. Which I don't know might conflict.
Thanks again for trying to help me out, this is really frustrating to get it to work.
**EDIT**
I worked it out !
I think I understood what you meant, I did as you told I started first with pluggin in the charger forced it to upgrade and now it's upgrading, thank you so much dancer_69. I was going to go tomorrow to buy a new 2nd hand smartphone. But now I can save my money for other things !
**EDIT of EDIT **
I seem to have downgraded to B133, I will try now with B158 2.3 V2 again and hopefully it will work now.

Yes, wasn't clear because I don' t remember what I've done and solve it. But I think that I did it like you discribed too.
Anyway I'm glad that was helpful(kind of)..
And don' t give up so soon with smartphone' s bricks, I've faced brick kind of problems many times and if the device it' s not completely dead, there is something you can do. Maybe need more search or many tries(sometimes the same things) but at the end(and of course If there isn't a hardware problem) device can unbrick.

[GUIDE] Re-partition your device using REPIT

You might have seen this guide on XDA, but is out-dated and only seems to work on stock firmware. What about people people running CM13, will it work, or will it brick your device?
This guide is updated and works with CM13 tested by me, it was also written with the i9300 16GB model in mind.
FAQ: next post
I take NO responcebility for any bricks, that's on you. Exactly like rooting, or installing anything 3:rd party (right?). Either is is my responsibility if any data is lost.
If you don't follow the guide, and adventure on your own, there's no one to blame but yourself when **** hits the fan.
Now, let's have a look at my partitions before modifying them (kB):
Code:
Filesystem Total Used Available Use% Mounted on
mmcblk0p8 1032088 17732 1014356 2% /cache
mmcblk0p12 11901576 6355436 5546140 53% /data
mmcblk0p12 11901576 6355436 5546140 53% /sdcard
mmcblk0p10 564416 8964 555452 2% /preload
mmcblk0p9 1548144 632704 915440 41% /system
mmcblk0p3 20144 9568 10576 47% /efs
As you can see, stock paritioning is bad. /preload and /cache has a lot of available space which takes up a lot of unnecessary space.
We can minimize all the partitions and use the space to increase your internal storage, neat; let's do it!
1. Check for buggy eMMC chip
First of all we'll be checking if your chip is possible to SDS (sudden death syndrome) which basicly corrupts your eMMC (internal storage) chip.
This only effects the 16GB model, if you're on another model just skip to the flashing part.
A. Download the app eMMC Brickbug Check app from the Play Store.
B. Check eMMC
Check if your device has the following under eMMC chip:
Type: VTU00M
FwRev: 0xF1
If the values match, you should update to the latest ROM + kernel available ASAP, which should fix SDS, if you don't; your eMMC chip might corrupt under the process of flashing REPIT.
2. Flashing guide
A. Before we begin
- Make sure that you're running the latest version of TWRP (i9300, i9305). Any other recovery and the script will NOT work.
- Do NOT continue if you're running stock, or planning to do so. This script is only tested on official CM13.
- Make sure you're plugged into a power source, and not a computer; or else partitions may fail to un-mount.
- Do a backup of your rare cat images so they don't get lost in the worst scenario.
- (optional) If you want to configure the script, see this.
B. Download required tool
We'll be using ourselves with the tool REPIT made by @Lanchon.
Without it I wouldn't make this guide as it is the only(CN) flexible tool for modifying partitions in Android.
Download the required flashable zip file: [updated 2017-01-22]
- i9300 - here
- i9305 - here
Make sure you DON'T rename it; copy it to your device.
C. Boot into recovery - volume up + home button + power button when powered off
D. Flash the zip file
- This process is a really long one, do NOT interrupt the process.
- If the flashing fails, it may tell you that it copied itself to /tmp, navigate to /tmp and flash the script again.
- If x partition fails to un-mount, try un-mounting it via TWRP > Mount.
Inside TWRP navigate to Install > Navigate to saved REPIT and select > Swipe to confirm flash.
3. Done!
You may now restart your device and verify the extra utilized internal storage.
It's not that hard eh? That's because @Lanchon did a great job on his project available on GitHub. Him and I worked closely on #22 to add support for the i9300.
After re-partitioning (still kB):
Code:
Filesystem Total Used Available Use% Mounted on
mmcblk0p8 32240 4200 26404 14% /cache
mmcblk0p12 13457732 574316 12199796 4% /data
mmcblk0p12 13457732 574316 12199796 4% /sdcard
mmcblk0p10 8048 4120 3520 54% /preload
mmcblk0p9 1548144 638168 909976 41% /system
mmcblk0p3 20144 9568 10576 47% /efs
It seems like we've gained 1.5GB in local storage, hoorah! Totally didn't steal from other partitions
Worth it? (my opinion)
Unless you REALLY need that 1.5GB of extra storage; NO, not at all.
On Android 6+ (CM13) sd-cards are now implemented like normal internal storage. Just buy a 8GB micro sd-card which costs a couple of bucks these days and save yourself some trouble.
Not only that, recently a user possibly got SDS (sudden death syndrome, do your own research) after flashing REPIT. Did my own research and I updated the guide with a step to check for this buggy eMMC chip.
Credit:
- @Lanchon for REPIT.
- @forumber2 for original guide.

QnA:
The questions are kinda copied from the old guide.
Q: Why is /cache a large partition?
A: It's because stock software updates saves in the partition. The partition was extended(CN) when upgrading to Android 4.3, as the update was so large, the cache partition had to be as well. AOSP does NOT use the partition when updating.
Q: What is the /preload partition for?
A: It's only really used if you bought the phone locked. Many mobile operators put in extra apps, and bloatware too in the partition only utilized in stock firmware; and even then... There's some random Samsung crap too. REPIT minimizes the partition.
Q: Any consequences of flashing?
A: Yes, you will NOT be able to install stock firmwares (assuming that you're not running stock). A undo is easy as the script is so flexible.
You will also burn a lot of eMMC life cycles using REPIT so don't do it often, and I hope you've read 1. where I covered the buggy eMMC chip thingy.
Q: Something went wrong with flashing the zip file!
A: Please upload the REPIT log usally found in the folder where you placed the flashable zip file to dropbox, or https://paste.tinyw.in; apparently pastebin doesn't like long logs. Can also be in /tmp. Otherwise you can copy the whole TWRP log found in /tmp/recovery.log, /cache/recovery/log or /cache/recovery/last_log. NEVER copy the whole log and make a post out of it, you're spamming the thread by doing so. Issues with REPIT should NOT be reported here, instead go to the REPIT GitHub page here.
Q: I want to undo these changes!
A: Since @Lanchon is taking over this thread :laugh:, ask him. Sorry for me not doing my homework.
Q: How about the x GB model?
A: They all work, REPIT is designed to assign any leftovers to the partition we use.
More questions? Bring them on.

Reserved #2

May be it's better to give proper credits too considering it was a big mess up in past.
Sent from my "i9300/1+2" powered by Carbon/Temasek
Fueled by 7000mAh ZeroLemon Battery

nicesoni_ash said:
May be it's better to give proper credits too considering it was a big mess up in past.
Sent from my "i9300/1+2" powered by Carbon/Temasek
Fueled by 7000mAh ZeroLemon Battery
Click to expand...
Click to collapse
Woops, I made the guide in notepad++, and accedently removed some lines when editing it; including a better credit to @Lanchon; adding in a new one now.

Hawaii_Beach said:
Woops, I made the guide in notepad++, and accedently removed some lines when editing it; including a better credit to @Lanchon; adding in a new one now.
Click to expand...
Click to collapse
I meant in your op too.
Sent from my "i9300/1+2" powered by Carbon/Temasek
Fueled by 7000mAh ZeroLemon Battery

Btw, is it possible to modify this script somehow so that you can reformat the /cache partition to f2fs? Afaik the minimum size is 100mb.

Sincci said:
Btw, is it possible to modify this script somehow so that you can reformat the /cache partition to f2fs? Afaik the minimum size is 100mb.
Click to expand...
Click to collapse
No, I'm sorry. It is already known, on GitHub: #8.
The minimum size of /cache? The script sets /cache to 32240kB which is 32MB..

nicesoni_ash said:
I meant in your op too.
Click to expand...
Click to collapse
OP?

Hawaii_Beach said:
No, I'm sorry. It is already known, on GitHub: #8.
The minimum size of /cache? The script sets /cache to 32240kB which is 32MB..
Click to expand...
Click to collapse
After I read your conversation with @Lanchon on git, it seems to me that there is no need to wipe data and it will still work, it's that right?
OP - Original Post basically referred to first post.
Sent from my "i9300/1+2" powered by Carbon/Temasek
Fueled by 7000mAh ZeroLemon Battery

nicesoni_ash said:
After I read your conversation with @Lanchon on git, it seems to me that there is no need to wipe data and it will still work, it's that right?
OP - Original Post basically referred to first post.
Click to expand...
Click to collapse
Yes, you don't need to wipe /data. It just makes things faster; as you wont have to move the content around. Without wiping, it will take a longer time to re-partition.
The script will NOT wipe /data except you add +wipe to -data=max (-data=max+wipe-i9300)
OP has so many meanings, it's f***ed.

Hawaii_Beach said:
On Android 6+ (CM13) sd-cards are now implemented like normal internal storage. Just buy a 8GB micro sd-card which basicly costs a couple of bucks and save yourself some trouble.
Click to expand...
Click to collapse
hi, thanks for the guide!
actually, the external sdcard will always be slower than the internal eMMC. also, the extra free space gets auto-TRIMmed in /data, making the whole eMMC (and thus your phone) faster. also, adopted storage diminishes the total reliability of your phone and data (more devices can fail).
in all, i'd recommend anybody with less than 2 or 3GB free space in /data to REPIT; it's safe and easy.
---------- Post added at 05:35 PM ---------- Previous post was at 05:22 PM ----------
Sincci said:
Btw, is it possible to modify this script somehow so that you can reformat the /cache partition to f2fs? Afaik the minimum size is 100mb.
Click to expand...
Click to collapse
REPIT does not support f2fs for now.
(future support will not include wipe without resizing, as f2fs does not support that yet.)
but you can get what you want anyway:
"-cache=0.03125+wipe"
actually means
"-cache=0.03125+wipe+ext4"
given that ext4 is the default FS for "cache".
"wipe" means format, and never mind what was there before. even if it was something that wasn't ext4 at all, it will succeed.
so you can use:
"-cache=0.0976+wipe"
to get exactly 100MiB-sized cache (in ext4)
then, afterwards, use TWRP to format cache in F2FS
and you'd get what you want.
but...
DON'T!!!
dont use F2FS in ANY partition besides /data! it makes NO sense!
F2FS has an overhead of about 100MB, so basically you would be creating a /cache that is unable to hold any files at all. (ext4 has 5MB overhead.)
and why have a dysfunctional /cache? what for? to have problems? incompatibilities?
certainly not performance, because cache is NEVER used in android. so why do it?
it's soft of a crazy fad, like /system in f2fs.
/system, the one partition we never write to, lol
---------- Post added at 05:39 PM ---------- Previous post was at 05:35 PM ----------
nicesoni_ash said:
May be it's better to give proper credits too considering it was a big mess up in past.
Sent from my "i9300/1+2" powered by Carbon/Temasek
Fueled by 7000mAh ZeroLemon Battery
Click to expand...
Click to collapse
thanks!
no credit required!!! the GPL allows him to do as he pleases, as long as he doesn't remove the license or claims copyright.
but anyway, thanks for the credit appreciated!
and thanks for invaluable help to port to i9300!!
---------- Post added at 05:43 PM ---------- Previous post was at 05:39 PM ----------
btw, i should start thanking the people who helped with the ports in the comments of the device port file. so far 2. i will back-credit when i get the time.
and i9305 and others are probably trivially supported, i just need the dumps done.

Lanchon said:
really long stuff going on
Click to expand...
Click to collapse
The thing is that not only could REPIT be ported to i9300, but any other Samsung device, right? They all run TouchWiz; for example s4, s5, s6? Have anyone even checked partitions on those devices?
The thing with partitions and the Android community is that almost no one discusses it. If you do a google on partitions on Android; very Little information / threads exist.

Lanchon said:
hi, thanks for the guide!
actually, the external sdcard will always be slower than the internal eMMC. also, the extra free space gets auto-TRIMmed in /data, making the whole eMMC (and thus your phone) faster. also, adopted storage diminishes the total reliability of your phone and data (more devices can fail).
in all, i'd recommend anybody with less than 2 or 3GB free space in /data to REPIT; it's safe and easy
Click to expand...
Click to collapse
To be honest, I never cared about storage speed (same goes for trim), not a heavy user on my phone, and have never been, just doesn't go well when I'm the operator. As long as it doesn't take 1 year to copy my secret .mp4's (ransom.mp4 and many more), there's no worries.
About failure, it's like running a computer. If you shut down a computer without sending signals (unplug from wall etc), it may damage the harddrive; right? Same here. Right?
Any how, If I ever run out of space on my i9300, I'd just add a sd-card. I don't save anything important on my device that doesn't get backed up via TWRP. But..
that's never going to happen! Because my OnePlus One is coming back from RMA service! (finally after 4 months (not kidding)). kinda off topic, but hey; it's my thread right :good:

Hawaii_Beach said:
The thing is that not only could REPIT be ported to i9300, but any other Samsung device, right? They all run TouchWiz; for example s4, s5, s6? Have anyone even checked partitions on those devices?
The thing with partitions and the Android community is that almost no one discusses it. If you do a google on partitions on Android; very Little information / threads exist.
Click to expand...
Click to collapse
lol about the quote
besides the name playing on samsung's PIT files, REPIT can actually work on any device with TWRP support. but the partition layout in most newer devices is friendly enough not to bother. even the stock i9300 layout is sort of friendly. highly problematic are only the devices that shipped before ICS with android 2.x (galaxy S2) or devices that shipped with non-emulated internal sdcard.
discussion is low volume because partitioning is considered 'dangerous'. and it can be, you can brick if you mess up. the idea of REPIT was to make it safe by encapsulating a bit of knowledge of each device in the device port file. motivation was that S2 users suddenly all needed to repit: their devices stopped working after a nightly flash because of /system being too small, it was a mess, lol.
btw, since you asked before, that's the reason why porting is needed: because you can't trust users not to make mistakes with full freedom. users that want full freedom have other tools: gdisk, parted, mkfs.xxx, resize2fs, etc.

Lanchon said:
lol ab...
Click to expand...
Click to collapse
Yeah, I know that other devices doesn't even need to touch the partitions, as it is a waste of time. (so is this??)
edit: still, maybe I want a extra 1.5gb on my s6 Active or whatever.
edit: by for today, it's 00:00 here..
discussion is low volume because partitioning is considered 'dangerous'. and it can be, you can brick if you mess up. the idea of REPIT was to make it safe by encapsulating a bit of knowledge of each device in the device port file. motivation was that S2 users suddenly all needed to repit: their devices stopped working after a nightly flash because of /system being too small, it was a mess, lol.
Click to expand...
Click to collapse
Dangerous!? I've seen way more people fu** their IMEI number (including ME on MINE i9300) by doing something dumb to the /efs content (totally didn't try to unlock the phone), that's dangerous. (got 0049)
The phone was just lying round until I got around to fix it, not going to get into details as XDA doesn't allow this stuff. It was really fustrating as people said that reflashing stock would get back the IMEI (should apparantly work, etc etc).
yet again side tracked, but i'm the operator right? :good: :highfive:

@Lanchon
Since we are talking abt partitions, I would like to ask a question that's not related to this tool but the other way mentioned in first post by flashing a zip file with manually entering the size in script file.
I tried that a while back on my s3 and it worked great. I was on kitkat that time and it was fine till lollipop came. So I flashed lollipop but since the system size was only about 500mb, it failed to flash so I made another zip with system size to 800mb and flashed it again. Although everything went fine but after flashing a new rom or restoring my old backup phone always showed some encryption error and asked to factory reset and even after doing that, still showed the same error even though I never encrypted anything. So the only option was to flash stock with pit file and change the partitions to stock size and then restore or flash a new rom.
I was never able to partition my phone after that coz that error always came back. I have op2 now so all molding goes on it and s3 is like a backup phone but I am still interested to know what was that all about and what could I do to fix that or whether my emmc worn out?
Sent from my "i9300/1+2" powered by Carbon/Temasek
Fueled by 7000mAh ZeroLemon Battery

Hawaii_Beach said:
Dangerous!? I've seen way more people fu** their IMEI number (including ME on MINE i9300) by doing something dumb to the /efs content (totally didn't try to unlock the phone), that's dangerous. (got 0049)
The phone was just lying round until I got around to fix it, not going to get into details as XDA doesn't allow this stuff. It was really fustrating as people said that reflashing stock would get back the IMEI (should apparantly work, etc etc).
yet again side tracked, but i'm the operator right? :good: :highfive:
Click to expand...
Click to collapse
well... effing the bootloader i way worse than borking /efs, believe me.
now, trying to hack /efs WITHOUT A BACKUP (!!) is big jesus f*cking christ sh*t u talking lol!!!

Lanchon said:
well... effing the bootloader i way worse than borking /efs, believe me.
now, trying to hack /efs WITHOUT A BACKUP (!!) is big jesus f*cking christ sh*t u talking lol!!!
Click to expand...
Click to collapse
Hahahaha yep. Didn't know the risk dude.

nicesoni_ash said:
@Lanchon
Since we are talking abt partitions, I would like to ask a question that's not related to this tool but the other way mentioned in first post by flashing a zip file with manually entering the size in script file.
I tried that a while back on my s3 and it worked great. I was on kitkat that time and it was fine till lollipop came. So I flashed lollipop but since the system size was only about 500mb, it failed to flash so I made another zip with system size to 800mb and flashed it again. Although everything went fine but after flashing a new rom or restoring my old backup phone always showed some encryption error and asked to factory reset and even after doing that, still showed the same error even though I never encrypted anything. So the only option was to flash stock with pit file and change the partitions to stock size and then restore or flash a new rom.
I was never able to partition my phone after that coz that error always came back. I have op2 now so all molding goes on it and s3 is like a backup phone but I am still interested to know what was that all about and what could I do to fix that or whether my emmc worn out?
Sent from my "i9300/1+2" powered by Carbon/Temasek
Fueled by 7000mAh ZeroLemon Battery
Click to expand...
Click to collapse
well i cannot answer about scripts and procedures unknown to me but...
an encrypted disk typically is made of 2 things:
-the encrypted disk 'surface' or area (ie: the data)
-and metadata (data describing the data, ie: data describing the encrypted disk)
metadata typically contains:
-cipher info
-and the disk surface encryption key (generated at random), itself encrypted with the access key (such as a passphrase).
why the indirect key? without it:
-changing the passphrase (say, your phone lock pattern) would be a very dangerous operation that would require reading, reencrypting and writing the complete disk, would take a huge amount of time and would drain your battery completely
-erasing the disk would similarly take a long time.
with it:
-when changing the passphrase you just need to reencrypt the surface key with the new passphrase and rewrite the metadata.
-when erasing, just wipe the metadata.
for example the metadata in recent android phones with hardware backing store for keys probably contains:
-cipher info
-and the disk surface encryption key (generated at random), itself encrypted with a secondary key (also random).
the secondary key lives in the hardware keystore. it's generated there and can never leave that processor. the keystore will decrypt the surface key during boot, only if the main processor informs the right passphrase (say, the PIN or pattern). a 4-digit PIN would be very easy to bruteforce, except that the keystore throttles down guesses, and can even wipe the key (rendering the disk forever unreadable) after so many bad guesses.
the keystore should be tamper-proof: a silly small processor, but resistant to voltage spike attacks, rays, etc and decapping to read the storage, to pick up signals in traces, to inject signals in traces, to chip modifications, etc. think of it as the chip in any recent credit card or even some sim cards, but on the main circuit board.
anyway back to metadata in android: it needs to be stored somewhere. the obvious place is an ultra small metadata partition containing just the raw metadata, no file system or anything of the like. this is simple and works great, except for one detail: older phones don't have this partition. basically this means that an android upgrade couldn't give you encryption.
so android can use a "crypto footer": with this scheme the encryptable partition (say /data) has a file system that is 16KiByte short of filling the actual partition, and the 16KiB footer follows. the footer is the metadata.
when you repartitioned before, you probably created a file system that used the complete partition area. there was no space left for the footer, so encryption couldn't be enabled.
you could have solved your issue today by flashing repit with all-default parameters: repit always resizes the encryptable partition's file system to make room for the footer, if not already there.
in REPIT, these commits add general and ext4-particular support for crypto footers:
https://github.com/Lanchon/REPIT/commit/591961adb180a6a03594053a846b698240b4d507
https://github.com/Lanchon/REPIT/commit/de3d3af9813afef7de3a798ce5314c0fb210e30f
https://github.com/Lanchon/REPIT/commit/5c3360b572ff25c7c01d796cabb9400066451ec3
this configures the footer on the i9300:
https://github.com/Lanchon/REPIT/blob/f46b0aafdfeb7860be17a315b4aceb43966325f9/device/i9300.sh#L85

[HOW-TO]Android 8.1 for Z00VD/ZC500TG

Hello people of XDA,
as I promised here, here's a tutorial for getting Android Oreo 8.1 up and running to your device.
NOTE: I DID NOT MAKE THIS TUTORIAL! This is a translated guide from 4PDA by nik-kst. I've also rehosted some of the files on Google Drive so you won't have to register on 4PDA(hopefully).
Code:
[B]Your warranty is now void. [/B]
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Now that the disclaimer is dealt with, let's get on with this tutorial shall we?
First things first, we need to grab a bunch of things:
SP Flash Tool;
MediaTek VCOM Drivers;
The Stock Kernel(it will make sense to you soon!);
Scatter file for repartitioning, drop it inside the stock kernel folder(credit to fca.sjc);
ADB and Fastboot of your choice;
New recovery;
Oreo's Backup, drop it inside a MicroSD card or drop it once you have re-partitioned the device successfully;
Once you have everything setup and extracted, you're ready to go!
First, we gotta go ahead and install VCOM drivers - we won't be able to do anything to our phone without them.
If you're running Windows 8/10, make sure to disable Driver Signature Verification.
Go to Device Manager, click Action at the top and click Add legacy hardware. A new wizard window will appear.
Choose Install the hardware that I manually select from a list(Advanced);
In the next window, choose Show all devices and click Next, then click Have disk...
Then you will be prompted to direct to the driver install info, so click Browse...
Now go to the folder of drivers and select the Setup Information file that's fitting for your computer, x86 for 32-bit and x64 for 64-bit.
You should now find 5 new devices in the list, add them one by one by repeating steps 2 to 6 until you have all of them installed.
Windows might complain about unsigned drivers, just allow their installation and proceed.
If your ports list looks similar to the picture below, then you're set for the next step!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, we'll want to back up the NVRAM partition, because AFAIK, it keeps important unique data about your device such as WiFi, IMEI etc. data.
Note: You may want to take out your MicroSD card and SIM cards prior to this just in case. Also, might be the possible fix if readback for NVRAM fails(needs confirmation).
First, open up Flashtool.exe as admin and go to Readback tab;
Click on Add, a new item in the list will appear. You want to double-click on it, so that a Save File window would appear.
Save that file anywhere you want, name it whatever you like, for convenience I've named mine ROM_NVRAM.
Now, you'll want to find the address in the memory for NVRAM partition. To do this, open up the stock firmware(credit to fca.sjc) scatter file in a text editor(like Notepad++), and find line partition_name: nvram
In that paragraph, find two values: linear_start_addr and partition_size they should be 0x380000 and 0x500000 respectively.
Punch in those values into the Readback block start address window, so it should look something like this:
Now, click Read Back, it should gray out along with Add and Remove.
Now, turn off your device, pull out the battery for about 30 seconds, reinsert it and DO NOT TURN IT ON YET! With the Volume Down "-" button pressed, plug in your device into the USB port.
The NVRAM partition should've been read and you'll get a giant green tick sign when it's done.
Now that that's done, we can start repartitioning our device.
Make sure your SP FlashTool is running as admin, otherwise restart it as admin.
Open up the Download tab and in the line Scatter-loading File click Choose and navigate to the 8.1 scatter file, it should be named MT6580_Android_scatter_8.1.txt.
From the dropdown list, select Format All + Download.
Again, take out the battery for 30 seconds and put it back in WITHOUT turning it back on.
Now click Download, and with the Volume down "-" button held down, plug the device into your PC. There should be a bunch of colored progress bars at the bottom of the window.
Once it's done, you should get the giant tick pop-up, after which you can disconnect the device, and start it normally.
NOTE: it takes a while for the first launch, so give it some time!
Once it starts up into the first launch wizard, we can now restore the NVRAM.
In order to activate the memory writing function of SP FlashTool, re-start it with admin and press Ctrl + Alt + V, the window header should have (Advanced mode) now.
From the Window drop-down, select Write Memory, it should redirect you to a new tab named accordingly.
In the File Path field, browse to the ROM_NVRAM backup that you made earlier.
In the Begin Address (HEX) field, copy the linear_start_addr value off the scatter file.
The region should be left at EMMC_USER.
Now, click the Write memory button, turn off the device, re-insert the battery just like before, and connect the device with the Volume Down "-" button pressed.
It should begin the writing of the NVRAM and once it's done a giant tick pop-up will appear.
Now after that is done, boot into the OS, check that everything works, including IMEI and WiFi.
Also, during the setup wizard or later in the settings setup a screen lock with a pattern or a PIN or a password(credit to fca.sjc), because the partitions may remain encrypted and show 0mb(needs confirmation)
Now you'll want to unlock the bootloader and flash the TWRP recovery.
Now this is a standard recovery flash, but for a quick summary:
Enable Developer options;
Enable OEM unlocking;
Reboot into bootloader mode(I like to use ADB for adb reboot-bootloader);
Make sure your device is detected via fastboot devices, if not, google some drivers for ADB;
Unlock the bootloader via fastboot oem unlock, and press the Volume up button to confirm the bootloader unlocking.
Now, reboot the phone, it will take a while to reboot, DO NOT PANIC AND WAIT.
Now that we have bootloader unlocked, we can flash the TWRP:
Go into bootloader mode;
Confirm you are being detected again by fastboot devices;
Flash the recovery with fastboot flash recovery [twrp recovery name].img;
now, WITHOUT booting into system we boot into recovery and confirm it works.
Now that you've done all this, you propably want to run Oreo now, eh? Well, here's what we do now:
Note: make sure you have the Oreo's backup zip extracted at it's own folder inside your MicroSD card or inside the phone's internal storage by now(thanks @ZappaDong for letting me know)
From recovery, select Wipe > Advanced Wipe and select system and vendor, and wipe them. Logs may complain about not seeing vendor, ignore that message.
Then, we restore everything from the Oreo backup;
Finally, do a factory reset(aka wipe Data, Dalvik and cache);
And reboot!
Now, fingers crossed, you should be booting into a fully functional 8.1 Oreo! if you did, congratulations!
Please let me know if I've made any mistakes and/or this has worked for you.
All credits go to the awesome people at 4PDA, especially nik-kst(if you're reading this, you the real MVP!), below I've linked the sources I've written this guide from.
Nik-kst's guide to repartitioning the device for Oreo;
Nik-kst's post about the Stable Oreo ROM.

Reserved for possible FAQ in the future

@aurismat, Hey man it worked as expected ! However, I was a bit confused on the repartitioning part when selecting ''Format all+download'' option then clicking ''start'' will only give an error stating that the IMG file of ''vendor'' is missing. (I am using SP FLASH v5.1744)
But nevertheless, I tried the ''Download only'' option and lucky it worked as well. I just wanted to clarify should it be Format all +download or Download only? Or is there a missing corresponding IMG file for vendor ?

Hey @JustAnormalGuy,
It should've been Format All + Download.
Also I'm glad that my post has helped at least one person.
Thanks for pointing out this omitted detail though, I'll edit the post ASAP.

Thanks for the translation!
--- solved ---
I have tried it three times but never managed to back up the NVRAM partition.
Error: s_dl-get_fram_setting_fail (5054) see attached screenshot
-----------
I have used Win 10 on my Mac and it worked.
Now I am stuck at step "5. Unlock the bootloader via fastboot oem unlock, and press the Volume up button to confirm the bootloader unlocking."
this looks O.K. to me
----------------------------------
>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 16.047s]
finished. total time: 16.047s
-----------------------------------
But now nothing happens after
-----------------------------------
> fastboot reboot
rebooting...
finished. total time: 0.000s
-----------------------------------
It's stuck in
[Fastboot Mode] <<==
=> FASTBOOT Moe ...
and nothing happens.
UPDATE
O.K. I have used the Power Button to switch it off and on again, there was a small Android for a few seconds and the phone rebooted the second time. Now I am waiting for it to finish booting.
UPDATE 2
TWRP is working now
And what TWRP.img should I use for
"3. Flash the recovery with fastboot flash recovery [twrp recovery name].img;"
in the next paragraph? Is this the "New recovery;" from the download section at the top?
Thank you!

Missing tips:
- Put both scatter files inside the stock kernel folder before starting.
-I used the stock scatter file for the NVRAM backup then the 8.1 scatter only for the Formal all+Download step.
- When you first run the stock ROM, set up a pin or a password, otherwise you will have failed to mount data in twrp and data will show as 0mb due to its encryption.

@aurismat does that WW file includes the new vendor release?
In the vendor, a bug was detected, the camera with the auto flash turned on, did not turn on (rather, it turned on and off immediately), the flash when shooting video.
Now everything works as it should: yes2:
Fixed vendor: 07/07/2018
https://yadi.sk/d/DUGRYLnc3YtADV

I did everything according with this tutorial. Sadly my mobile network is not connecting idk why. I get an error saying Simprocessor and it doesnt connect on mobile network. It detects the networks but wont connect. Im going back to stock until someone can help me fix it.

@ZappaDong:
Yes, you should use the one I provided the link at the list of downloads.
Also, a bit late and I may be wrong, but your DRAM reads may be hindered by a MicroSD card(confirmation needed). Try ejecting it before you read off the NVRAM.
@fca.sjc:
First of all, thanks for pointing out my missing tips.
I'm not really sure if it includes the fixed vendor. I didn't really have any issues with the camera's flash, so they already included it(?)(again, needs confirmation).
For failed connections, make sure you flashed the NVRAM correctly(hence why you should test the telephony after you've repartitioned to stock 5.0 with the NVRAM backup flashed).If you failed to do that, I was told you should be able to recover the NVRAM data with Maui(?) software(confirmation needed, once again).
Thanks to both of you for pointing out these tips, I'll update the guide and credit you when I'll have more time. Cheers!

[*]For failed connections, make sure you flashed the NVRAM correctly(hence why you should test the telephony after you've repartitioned to stock 5.0 with the NVRAM backup flashed).If you failed to do that, I was told you should be able to recover the NVRAM data with Maui(?) software(confirmation needed, once again).
[/LIST]
Click to expand...
Click to collapse
After repartition, wifi, 3g and mobile signal works fine. I just cant flash twrp after unlocking bootloader otherwise i get a bootloop (unable to mount data and storage). So after i installed twrp and wiped/restore vendor and system, i reflashed stock recovery to acess android and then, restarted again to recovery. At this point, i did the write memory step again, using old vendor and the new vendor. None seem to work. I even backed up NVRAM using TWRP at first to make sure i did it right and tried to restore from there and it doesnt seem to be an IMEI issue. Maybe it has something to do with the frequency. Im on Brazil right now and idk
It does recognize my Sim card, my number, it downloads the data operators and etc but it doesnt connect to the mobile signal idk why. The bug starts at the restore step so it has something to do with this part.
I just test stuff but im pretty experienced at flashing and reflashing, etc. I guess only a dev can help and i actually went back to 7.1 UHANS rom, wich i got from 4pda.ru. Before using this rom, I was having a bluetooth audio stream bug and Ive tested like 4-5 roms, one for each kernel that was there. Lets see if someone can help me with this, cause i want oreo for better bluetooth audio stream.
Thanks for your help so far. I really apreciate it. This device is very good and we dont see many mods here on xda for it.

aurismat said:
@ZappaDong:
Yes, you should use the one I provided the link at the list of downloads.
Also, a bit late and I may be wrong, but your DRAM reads may be hindered by a MicroSD card(confirmation needed). Try ejecting it before you read off the NVRAM.
Click to expand...
Click to collapse
Thanks again!
I am using Windows 10 (bootcamp on the iMac) now and I have read the description in the 'old' [ROOT/TWRP] thread but used the files you have provided.
TWRP is working now, but I got an error that the ZIP file on the SD card was corrupted. Maybe I have damaged it when copying it to the SD card under OS X.
I am just redownloading it with Windows 10 and give it another try. (Yandex is very slow now, about 60 KB/s)
------------------------------------------------------------------
UPDATE
I have downloaded "WW_Phone-user_810_O11019_1528478718_release.zip" again, put in on the SD card, booted into Recovery, wiped system and vendor and chose "Install" , selected the "WW_Phone-user_810_O11019_1528478718_release.zip" file.
But I still get an error message.
Installing zip file '/external_SD/WW ... release.zip'
Checking for digest file
Skipping Digest Check: no Digest file found
[IN RED]Invailid zip file format!
Error installing zip file '/ 'external_SD/WW ... release.zip' [/IN RED]
Updating partion details...
...done
I have just copied the zip file from the download folder to the SD card - have I missed anything?

ZappaDong said:
And what TWRP.img should I use for
"3. Flash the recovery with fastboot flash recovery [twrp recovery name].img;"
in the next paragraph? Is this the "New recovery;" from the download section at the top?
Thank you!
Click to expand...
Click to collapse
Yup that one

@ZappaDong, yeah I kind of forgot to mention again - you should've extracted the .zip in which the backup came in. It's a backup, not an installation zip.
It needs to be extracted into its own folder inside the MicroSD card, so that then it could be used by TWRP to recover the partitions.
Thanks for pointing this out to me though, gonna edit it ASAP.

@fca.sjc bro AFAIK that problem of yours could be because of one or more of the following:
1. Your IMEI is missing or null. I would suggest SN Write tool (since I already tried it). Is quite effective, it is comparable to Maui Meta although I haven't tried it yet. (Tutorial here ==> https://forum.hovatek.com/thread-12306.html )
It is better to use PC restore tools since it writes directly to the nvram unlike apks like Chamelephon which (according to what I know) writes only to nvdata.
2. You need to switch the sims. What i mean is just if you have 2 sims on your phone, switch sim 1 in with sim 2. I forgot the explanation on it but it helps.
3. You need to switch off data connection on the other sim. On the several roms I tried on 4pda including this 8.1 pixel based rom, upon first bootup, the data connection on both sims are already on, therefore 3G cannot work. So first turn both sim's connection off then check if network mode is set to 3G. If not do the Solution #2.

JustAnormalGuy said:
@fca.sjc bro AFAIK that problem of yours could be because of one or more of the following:
1. Your IMEI is missing or null. I would suggest SN Write tool (since I already tried it). Is quite effective, it is comparable to Maui Meta although I haven't tried it yet. (Tutorial here ==> https://forum.hovatek.com/thread-12306.html )
It is the best IMEI restore tool since it writes directly to the nvram. (Meaning it retains even after wipes to data, system etc. via twrp)
2. You need to switch the sims. What i mean is just if you have 2 sims on your phone, switch sim 1 with sim 2. I forgot the logic on how that helps but I've seen it as a solution as the phone rereads the sims.
3. You need to switch off data connection on the other sim. On the several roms I tried on 4pda including this 8.1 pixel based rom, upon first bootup, the data connection on both sims are already on, therefore 3G cannot work. So first turn both sim's connection off then check if network mode is set to 3G. If not do the Solution #2.
Click to expand...
Click to collapse
Thanks for your help bro. I did check the IMEI while i was on this oreo rom. It seem to be ok. Number was there but i did not check if it was the right number. I might check it when i try to flash again. Probably later today when i'm home.
The problem wasnt just data connection, it was the connection itself. I couldnt call or receive SMS to activate whatsapp, for example. Like i said previously, those features were ok after repartitioning (on stock repartitioned). After the restore step, i did check all network options, including data, network mode, network connections available,etc. I'll follow your tutorial to restore the IMEI if the numbers are different then. I'll remember to take some screenshots next time so you guys can help me figure out what the problem is. Thanks again

aurismat said:
@ZappaDongIt's a backup, not an installation zip.
Click to expand...
Click to collapse
Yes, that did the trick. The installation went through and everything seems to work now.
Thank you again for your patience.

I saw there in the forum 4pda that are doing roms project treble pro zenfone go, only that I can not understand the mode of installation, you know how?

Ricardo Flowers said:
I saw there in the forum 4pda that are doing roms project treble pro zenfone go, only that I can not understand the mode of installation, you know how?
Click to expand...
Click to collapse
Yeah, it is possible -
FIrstly you'd need a vendor image that has fixed RIL(telephony) - vendor off this thread's 8.1 has RIL broken in Treble ROMs.
Luckily you can get it off any 8.1 custom ROM off ska-vova in 4pda. Just download any of his .zips(i.e. his ResurrectionRemix ROM(which imo is just official ResRemix with their Russian preference for a browser, but fine)), flash them and then backup the /vendor off it(and /boot for good measure)
Buuuuut then you need a TWRP that supports system image flashing - not sure if the one I provided here has it, if it hasn't - I'll post it here.
Then all you need to do is flash the Treble image, restore the /vendor(and /boot if you need to) and hope for the best!
Sadly the Havoc OS 2.0, the only ARM A-Only Pie-based ROM available here didn't work for me - just straight bootloops.
Your mileage may vary - if you get the Havoc OS 2.0 instaled, I'd love to read about it.

aurismat said:
Yeah, it is possible -
FIrstly you'd need a vendor image that has fixed RIL(telephony) - vendor off this thread's 8.1 has RIL broken in Treble ROMs.
Luckily you can get it off any 8.1 custom ROM off ska-vova in 4pda. Just download any of his .zips(i.e. his ResurrectionRemix ROM(which imo is just official ResRemix with their Russian preference for a browser, but fine)), flash them and then backup the /vendor off it(and /boot for good measure)
Buuuuut then you need a TWRP that supports system image flashing - not sure if the one I provided here has it, if it hasn't - I'll post it here.
Then all you need to do is flash the Treble image, restore the /vendor(and /boot if you need to) and hope for the best!
Sadly the Havoc OS 2.0, the only ARM A-Only Pie-based ROM available here didn't work for me - just straight bootloops.
Your mileage may vary - if you get the Havoc OS 2.0 instaled, I'd love to read about it.
Click to expand...
Click to collapse
Can you do a tutorial? I did not quite understand how it installs. Sorry, google translate does not help.

Deleted

Axon 7 how to fix persist partition?need help

Hi!
trying to fix my imei I accidentally wiped my "persist" partition
A2017 Chinese model convert to A2017u
twrp 3.2.3.0 bootloader unlocked
persist partition is missing in my twrp backup
error:failed to mount '/persist' (invalid argument)
realy need help
Regards!

@netphone: You can format the persist partition from TWRP, with mke2fs or mkfs.ext4, as ext4 filesystem. But then your device's auto-rotate, sensors, etc probably won't be working. This is because some of the persist partition's contents aren't automatically regenerated even after it is formatted.
Quite some time ago I made a backup of this partition in case of issues listed above, and then subsequently wiped it by accident. Luckily I had a backup I could restore. You can find it at:
https://forum.xda-developers.com/showpost.php?p=75981746&postcount=1844
Several members tried it and said it works fine. Just flash the zip in TWRP.
I have an A2017U, and since you are converting to A2017U from A2017, then it should work. It's not like you have anything to lose, your partition is already wrecked anyway, the most that happens is it doesn't work out. In the future, I would advise making your own backup. It (the partition) is only 32MB in size.

AnonVendetta said:
@netphone: You can format the persist partition from TWRP, with mke2fs or mkfs.ext4, as ext4 filesystem. But then your device's auto-rotate, sensors, etc probably won't be working. This is because some of the persist partition's contents aren't automatically regenerated even after it is formatted.
Quite some time ago I made a backup of this partition in case of issues listed above, and then subsequently wiped it by accident. Luckily I had a backup I could restore. You can find it at:
https://forum.xda-developers.com/showpost.php?p=75981746&postcount=1844
Several members tried it and said it works fine. Just flash the zip in TWRP.
I have an A2017U, and since you are converting to A2017U from A2017, then it should work. It's not like you have anything to lose, your partition is already wrecked anyway, the most that happens is it doesn't work out. In the future, I would advise making your own backup. It (the partition) is only 32MB in size.
Click to expand...
Click to collapse
can i also use it on G version? i think something messed up in my persist partition.
i have read this on xda:
PERSIST - contains data which shouldn't be changed after the device is shipped, e.g. DRM related files, sensor reg file (sns.reg) and calibration data of chips; wifi, bluetooth, camera etc.
Some package installers such as OpenGapps also make use of this partition to read configuration file.
also contains calibration data etc.I like to try this as i counter calibration issues.
If yes,any recommend on what OS i should flash this? And should i wipe my persist partition before flashing yours?
I try to backup my own persist partition in TWRP,but in backup it shows my perist partition is 0mb.On diskinfo it says my partition is 27,5mb in size,but others report theirs are 32mb in size.
EDIT; i still did a backup in twrp even though it says the size is 0mb.The backup map is like 300kb.
how did you wiped persist partition? In twrp wipe section persist is not showed

@Predatorhaze: My zip may work on G, or not, you can try and let me know.
You can "wipe" persist with the command:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist
And back it up with:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Run these commands from TWRP terminal. dd is a famous Linux command line utility.
The partition is exactly 32MB in size.

AnonVendetta said:
@Predatorhaze: My zip may work on G, or not, you can try and let me know.
You can "wipe" persist with the command:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist
And back it up with:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Run these commands from TWRP terminal. dd is a famous Linux command line utility.
The partition is exactly 32MB in size.
Click to expand...
Click to collapse
and after the command,i mount persist and flash the zip?
thanks!

@Predatorhaze: If you wipe persist with my command, then it will be unmountable prior to flashing the zip. This is because dd destroys persist's ext4 filesystem by zeroing it out. After the zip is mounted TWRP should mount persist automatically, but if not you can do it manually.
You should Google the difference between partition, volume, and filesystem.

AnonVendetta said:
@Predatorhaze: If you wipe persist with my command, then it will be unmountable prior to flashing the zip. This is because dd destroys persist's ext4 filesystem by zeroing it out. After the zip is mounted TWRP should mount persist automatically, but if not you can do it manually.
You should Google the difference between partition, volume, and filesystem.
Click to expand...
Click to collapse
When i used your command it says no more space left,32mb copied,0mb.Then i flashed your persist zip and rebooted twrp.
Now i flashed ROM and gapps magisk etc.I see playstore mounts persist (dont know why),after flashing all files i manually wiped all folders and files from persist folder and flashed your persist zip again,then ive powered off my phone,turned on and booted.Thanks
I already noticed the size is different,my persist folder was smaller in size,and also the thermal kicked in when booted on os.Phone was warm and CPU limited to 1036mhz.I noticed this thermal kick in was gone since i complained about battery.

My battery was sitting on 12%,i run geekbench cpu bench...half way of the bench my phone shut down (shows 0% battery,but half way in bench it was still 12%).I decided to just power on my phone and boot.My phone booted the os and shows 10% battery.Dont know if this is a bug in geekbench or something else..
I reached 4+ hours sot with 2 hour of gaming (from 100% to 10%).
Also i charged my phone at night ( i do this rarely).when i woked up my battery was 100% and unplugged the charger,when i unplugged it droppped direct to 99%.Is this normal? I can remember with my previous devices when i charged at night,and unplugged in the morning,it sits on 100% for a while

@Predatorhaze: It is possible for a computer (which a phone is) to shut down while running stress testing software, if this happens then it means your setup is unstable and couldn't handle the tests. Sometimes the OS will intentionally crash itself (BSOD) to prevent damage to itself or hardware. I like to overclock PCs as a hobby, and while there's a lot I don't know, I've been at it long enough to master the basics. I regularly do benchmarking and stress testing to see if my setups are rock solid, or need more tuning.

AnonVendetta said:
@Predatorhaze: It is possible for a computer (which a phone is) to shut down while running stress testing software, if this happens then it means your setup is unstable and couldn't handle the tests. Sometimes the OS will intentionally crash itself (BSOD) to prevent damage to itself or hardware. I like to overclock PCs as a hobby, and while there's a lot I don't know, I've been at it long enough to master the basics. I regularly do benchmarking and stress testing to see if my setups are rock solid, or need more tuning.
Click to expand...
Click to collapse
Thanks.
Can you maybe share your stock /sys folder also?

@Predatorhaze: Why do you need my sys directory? I'm not running a stock ROM, BTW.

AnonVendetta said:
@Predatorhaze: Why do you need my sys directory? I'm not running a stock ROM, BTW.
Click to expand...
Click to collapse
To compare with mine and maybe replace it

@Predatorhaze: Umm...no. That directory contains thousands of subdirectories and quite a few files. As well as a bunch of symbolic links that point to other places. It wouldnt be quick or convenient to make a zip. Do you even know what Android/Linux use /sys for? I do, and I'm pretty sure you don't even understand what you're really asking for. In any case, sys won't hold the answer to your questions. It seems to me that you are off on a wild goose chase.

AnonVendetta said:
@Predatorhaze: Umm...no. That directory contains thousands of subdirectories and quite a few files. As well as a bunch of symbolic links that point to other places. It wouldnt be quick or convenient to make a zip. Do you even know what Android/Linux use /sys for? I do, and I'm pretty sure you don't even understand what you're really asking for. In any case, sys won't hold the answer to your questions. It seems to me that you are off on a wild goose chase.
Click to expand...
Click to collapse
No,i dont really know,and you are right.Im still trying to find out my battery % problems (And no,its not because my battery is degraded)
i used in terminal cat /sys/class/power_supply/bms/charge_full and it showed something with 29xxxxxx,where i think my battery cap is around 2900mah and i believe this,as i reach more than 4 hours sot with gaming included.
Thank anyway for all your help!

AnonVendetta said:
@Predatorhaze: It is possible for a computer (which a phone is) to shut down while running stress testing software, if this happens then it means your setup is unstable and couldn't handle the tests. Sometimes the OS will intentionally crash itself (BSOD) to prevent damage to itself or hardware. I like to overclock PCs as a hobby, and while there's a lot I don't know, I've been at it long enough to master the basics. I regularly do benchmarking and stress testing to see if my setups are rock solid, or need more tuning.
Click to expand...
Click to collapse
this shutdown only happens when its less than 20% or something.I also noticed when its less than 20%,geekbench shows 3 clusters where one of them is at 0.0ghz.
maybe some problem with fuel gauge.
i tried to reset the gauge at 100%,but sot is just worse now

@Predatorhaze: I recently received a private message from @Choose an username..., his unedited PM is below:
heads-up about ter
Just some info, do what you want with it:
This Predatorhaze guy is the most toxic user in our side of xda, he thinks his battery is pristine, asks for help, then refuses it and tries to find a culprit anywhere
A couple months ago he claimed that Oki's "Deep Wipe" function made his battery go bad (which he claimed beforehand too) and his explanation was that it made the system believe he had two batteries...
His shutdown problem when he ran a benchmark is not because of system instability or whatever, that's rather overclock/volt specific as we don't really have any oc kernel. The problem he has is that BCL acts when voltage goes below the safe threshold, because his battery is so wrecked that it can't withstand high current usage (i.e. high internal resistance and other stuff). I'm not going to tell this to him because he'll branch out as he usually does.
He's blaming the persist partition because his lockscreen says 5V charging speed, that's what he said in Telegram ? i mean we appreciate you keeping him busy, but you're just wasting your time. if anything just try to convince him that his battery is K.O., maybe he can change it and stop destroying whatever's left of this...
My response:
Re: heads-up about ter
I don't really need a heads up about anyone, although he is a waste of time. He doesn't know much of anything, but he is looking for any excuse at all that will explain his battery issues. If you ask me his battery is bad, I already tried telling him this. I only continue to try to help him because I figure he might listen at some point, but he's wearing my patience thin.
You dont need to tell him anything directly, I've decided I'm going to forward him a verbatim copy of your PM, and maybe my response as well. I really don't feel that it's OK to trash talk someone behind their back, especially when you wouldn't say the same things to them directly. If I have an issue with someone, then I take it to them direct, I'm not known for mincing words. Maybe he will just "lose it" on the forum and get himself permabanned. But then it will be his fault.
Mind if I ask what Telegram group you are a member of? Is it related to LOS?
His response:
Re: heads-up about ter
Who says I wouldn't say it to him directly? All of us did, he eventually got banned on the Schwifty group, made a different account, got banned again. It's borderline bullying on the GSI testing group. Now he's going around every old ROM thread commenting how they don't work
Also attach a verbatim copy of your comment, of course ?
Which has led up to now...honestly, your battery is going bad, you are just unwilling to accept it. Please stop wasting people's time, being antagonistic in general, and being more stubborn than a pack mule. Your request for my /sys directory is asinine, up until this point I've just been trying to help you, but you are deluding yourself. The sooner you replace your battery, the sooner your issues will be resolved. I will no longer continue to post in threads where you complain about your battery and post about weird off the wall **** that you think are supposedly causing your problems. Enough is enough.....

ok enough said.
i already told 100 times,these problem occurs on different setups,what they say is wrong.
that thing about geekbench,doesnt happen always.
and i have changed my battery...it sits on 50%.Doesnt chharge up,doesnt go down,just sits on 50%.
also sometimes when i change bootstack+vendor partition,my battery shows different % after.

[GUIDE] Introduction to the OnePlus 8T - Why is it so?

What it ain't: it's not a "how-to" manual. There are lots of threads out there that explain how to do things.
What it is: a fairly simple explanation of how things are on this phone written for those who, like me, have come from a phone with no A/B partitions (a far simpler world).
"Toto, I've a feeling we're not in Kansas anymore"The OnePlus 8T is an AB device. This means that a large number (but not all) of its hardware partitions have an A and a B version. The A set of partitions are called slot a, the B set are slot b.
The reason for this is to support seamless over-the-air (OTA) updates. These are updates to the operating system (OS) that can be installed while the phone is being used! Once the update has been installed the phone is rebooted (it automatically switches slots) and comes up on the newly updated version of the OS. If the update fails, the phone will simply revert to the original slot.
To implement this a number of things have changed:
The AB partitions have a currently active/running version (called the active slot) and an inactive version (the inactive slot) where the updates can be written to.
An update module (update_engine) is included in the OS to process the updates. Previously this would have been handled by code running in the recovery partition.
To avoid doubling up on large system partitions (system, system_ext, odm, product, vendor) and to can cater for increases in these partions, these are now carved out dynamically from a large super partition. This allows more effective use of the hardware space.
This has some important implications:
While it looks like you could have two versions of the operating system installed on the phone (one on slot a, one on slot b), this is not in fact the case. And that's because the super partition isn't large enough to hold two sets of system partitions. Just like there's only one version of the data partition, so there's only one version of the super partition (containing the system partitions).
You can write to hardware partitions in bootloader/fastboot mode using fastboot flash <partition> <file>, but you can't use this mode to write a specific file within a partition. And, therefore, you can't use this mode to write to the system partitions because they are files within the super partition. For these, you need to use fastbootd which is part of recovery.
Flashing/installing a ROM using the update engine (as done by System update of OOS or a recovery from LineageOS or TWRP) will alwaysbe written to the inactive slot. So, if you are flashing a custom ROM and want it to use the latest OOS firmware installed on the phone, then you will have to either:
Copy the firmware from the currently active slot to the inactive one, or
Swap slots before you do the install so that it gets installed on what was the active slot containing the correct firmware.
If you are used to using TWRP to backup your system partitions, then the way to do it now is to backup the super partition and not the system, system_ext, odm, product, or vendor partitions.
"It's complicated""Delta variants"Updates (whether Over-the-air (OTA) or from the OnePlus download site) come in two flavours:
Full update: the files for each updated partition contain the full image. These are quite large, typically about 3-4GB.
Delta update: the files contain only the changes to be applied to each partition and can be quite small in size (MB rather than GB).
Since a delta update only contains changes, it is imperative that the update process check that the current partition contains the expected data that will be updated. The update_engine will check that the current partition hash is what the update is expecting. If it isn't, the update will fail.
If a partition has been modified (you have installed Magisk which changes the boot partition, or installed TWRP which changes the recovery partition), then you will have to restore the changed partition back to their original stock version before starting the update process.
That's why it is best practice to take a copy of the stock partition before you modify it.
"Good memories"The 8T came out originally with LPDDR4X memory, but OnePlus then decided to improve it by using LPDDR5 memory. As a result of this change, the xbl and xbl_config partitions now hold different data depending on the type of memory used in the phone. Note: you can find out what type of memory your phone has using:
on OOS 11: getprop ro.boot.ddr_type - 0 means LPDDR4X, 1 means LPDDR5.
on OOS 12 (and later): cat /proc/devinfo/ddr_type - you need to run this as root.
The way this is implemented is by including files for both LPDDR4X (files named xbl, xbl_config) and LPDDR5 (files named xbl_lp5, xbl_config_lp5) in updates/downloads. OnePlus had to make custom changes to update_engine to cater for this. It is only as of 2021-12-22 that a version of TWRP was produced that could handle these files correctly.
"Hitting the books"Google has some great documentation about AB devices. If you are using your phone to read this, make sure you use your browser in desktop mode so that you can see the Google documentation's navigation pane on the left hand side.
A/B (Seamless) System Updates: https://source.android.com/devices/tech/ota/ab
Dynamic Partitions: https://source.android.com/devices/tech/ota/dynamic_partitions
Fastbootd: https://source.android.com/devices/tech/ota/dynamic_partitions/implement#fastbootd and https://source.android.com/devices/bootloader/fastbootd
Virtual A/B Overview: this covers how the system partitions in super get updated and it's fairly complex https://source.android.com/devices/tech/ota/virtual_ab

Thanks Bill. Very helpful and that is why I'm still on OOS for now. I'm sure I am missing something but I have several questions.
1. How is the 8T different from the 8 or 8Pro as far as OOS is concerned? Is it a different OS architecture?
2. When you use another OS like LineageOS, how does it compare to OOS as far as the internals go (super partition, etc.). Is the OS completely different in the way it uses the hardware and the way updates occur?
3. When we refer to firmware what do we actually mean (code designed exactly for the specific harware interface or what)? Does the firmware stay the same for any OS that is used and if so how is that accomplished? Are there certain areas of the system that are not touched by any new OS for that phone except the OEM?
I'm trying to wrap my head around how this phone seems to be so different from even other OP phones.
Thanks John

zzjea said:
Thanks Bill. Very helpful and that is why I'm still on OOS for now. I'm sure I am missing something but I have several questions.
1. How is the 8T different from the 8 or 8Pro as far as OOS is concerned? Is it a different OS architecture?
2. When you use another OS like LineageOS, how does it compare to OOS as far as the internals go (super partition, etc.). Is the OS completely different in the way it uses the hardware and the way updates occur?
3. When we refer to firmware what do we actually mean (code designed exactly for the specific harware interface or what)? Does the firmware stay the same for any OS that is used and if so how is that accomplished? Are there certain areas of the system that are not touched by any new OS for that phone except the OEM?
I'm trying to wrap my head around how this phone seems to be so different from even other OP phones.
Thanks John
Click to expand...
Click to collapse
I am not Bill, but I will still attempt to answer your questions.
1. There are no real difference between OOS for 8T compared to the 8/8 Pro. They all use the same SOC (Snapdragon 865). For the last few OOS updates the changelog has been the same between 8/8Pro and 8T. Only thing that is different compared to the 8/8Pro is that the 8T device can have either LPDDR4X or LPDDR5 ram. While the 8 and 8 Pro only have either of them depending on the model. There are also plenty of unified custom kernels that work for all 3 devices as well.
2. I am no custom rom expert but I think they still handle the super partition and updates in the same way, but it is best to check the thread for the rom and read the update instructions there.
3. The FAQ in this thread should answer your questions. It also contain flashable firmware packages. These packages are extracted from the stock OOS rom and can be used to update firmware if you are on a custom rom https://forum.xda-developers.com/t/firmware-oneplus-8t-kebab-ddr0-ddr1-updated.4299231/

zzjea said:
Thanks Bill. Very helpful and that is why I'm still on OOS for now. I'm sure I am missing something but I have several questions.
1. How is the 8T different from the 8 or 8Pro as far as OOS is concerned? Is it a different OS architecture?
2. When you use another OS like LineageOS, how does it compare to OOS as far as the internals go (super partition, etc.). Is the OS completely different in the way it uses the hardware and the way updates occur?
3. When we refer to firmware what do we actually mean (code designed exactly for the specific harware interface or what)? Does the firmware stay the same for any OS that is used and if so how is that accomplished? Are there certain areas of the system that are not touched by any new OS for that phone except the OEM?
I'm trying to wrap my head around how this phone seems to be so different from even other OP phones.
Thanks John
Click to expand...
Click to collapse
1. I don't know anything about the other OP 8 devices. I'm only interested in the 8T because that's what I have.
2. The hardware determines how the OS must be structured. So all ROMs have to support the A/B structure and dynamic system partitions.
3. I think of Firmware as phone specific software/data related to the underlying vendor-specific hardware components/chip set. It's required by the OS to access the hardware, but is not included in custom ROMs. It's vendor-specific.

BillGoss said:
What it ain't: it's not a "how-to" manual. There are lots of threads out there that explain how to do things.
What it is: a fairly simple explanation of how things are on this phone written for for those who, like me, have come from a phone with no A/B partitions (a far simpler world).
"Toto, I've a feeling we're not in Kansas anymore"The OnePlus 8T is an AB device. This means that a large number (but not all) of its hardware partitions have an A and a B version. The A set of partitions are called slot a, the B set are slot b.
The reason for this is to support seamless over-the-air (OTA) updates. These are updates to the operating system (OS) that can be installed while the phone is being used! Once the update has been installed the phone is rebooted (it automatically switches slots) and comes up on the newly updated version of the OS. If the update fails, the phone will simply revert to the original slot.
To implement this a number of things have changed:
The AB partitions have a currently active/running version (called the active slot) and an inactive version (the inactive slot) where the updates can be written to.
An update module (update_engine) is included in the OS to process the updates. Previously this would have been handled by code running in the recovery partition.
To avoid doubling up on large system partitions (system, system_ext, odm, product, vendor) and to can cater for increases in these partions, these are now carved out dynamically from a large super partition. This allows more effective use of the hardware space.
This has some important implications:
While it looks like you could have two versions of the operating system installed on the phone (one on slot a, one on slot b), this is not in fact the case. And that's because the super partition isn't large enough to hold two sets of system partitions. Just like there's only one version of the data partition, so there's only one version of the super partition (containing the system partitions).
You can write to hardware partitions in bootloader/fastboot mode using fastboot flash <partition> <file>, but you can't use this mode to write a specific file within a partition. And, therefore, you can't use this mode to write to the system partitions because they are files within the super partition. For these, you need to use fastbootd which is part of recovery.
Flashing/installing a ROM using the update engine (as done by System update of OOS or a recovery from LineageOS or TWRP) will alwaysbe written to the inactive slot. So, if you are flashing a custom ROM and want it to use the latest OOS firmware installed on the phone, then you will have to either:
Copy the firmware from the currently active slot to the inactive one, or
Swap slots before you do the install so that it gets installed on what was the active slot containing the correct firmware.
If you are used to using TWRP to backup your system partitions, then the way to do it now is to backup the super partition and not the system, system_ext, odm, product, or vendor partitions.
"It's complicated""Delta variants"Updates (whether Over-the-air (OTA) or from the OnePlus download site) come in two flavours:
Full update: the files for each updated partition contain the full image. These are quite large, typically about 2.8GB.
Delta update: the files contain only the changes to be applied to each partition and can be quite small in size (MB rather than GB).
Since a delta update only contains changes, it is imperative that the update process check that the current partition contains the expected data that will be updated. The update_engine will check that the current partition hash is what the update is expecting. If it isn't, the update will fail.
If a partition has been modified (you have installed Magisk which changes the boot partition, or installed TWRP which changes the recovery partition), then you will have to restore the changed partition back to their original stock version before starting the update process.
That's why it is best practice to take a copy of the stock partition before you modify it.
"Good memories"The 8T came out originally with LPDDR4X memory, but OnePlus then decided to improve it by using LPDDR5 memory. As a result of this change, the xbl and xbl_config partitions now hold different data depending on the type of memory used in the phone. Note: you can find out what type of memory your phone has using getprop ro.boot.ddr_type - 0 means LPDDR4X, 1 means LPDDR5.
The way this is implemented is by including files for both LPDDR4X (files named xbl, xbl_config) and LPDDR5 (files named xbl_lp5, xbl_config_lp5) in updates/downloads. OnePlus had to make custom changes to update_engine to cater for this. It is only as of 2021-12-22 that a version of TWRP was produced that could handle these files correctly.
"Hitting the books"Google has some great documentation about AB devices. If you are using your phone to read this, make sure you use your browser in desktop mode so that you can see the Google documentation's navigation pane on the left hand side.
A/B (Seamless) System Updates: https://source.android.com/devices/tech/ota/ab
Dynamic Partitions: https://source.android.com/devices/tech/ota/dynamic_partitions
Fastbootd: https://source.android.com/devices/tech/ota/dynamic_partitions/implement#fastbootd and https://source.android.com/devices/bootloader/fastbootd
Virtual A/B Overview: this covers how the system partitions in super get updated and it's fairly complex https://source.android.com/devices/tech/ota/virtual_ab
Click to expand...
Click to collapse
Device OnePlus 8 Pro
OOS 11.0.10.10 IN11BA
TWRP 3.6
Root Magisk 23.0
Hello
Hello
I noted in your information above
“If you are used to using TWRP to backup your system partitions, then the way to do it now is to backup the super partition and not the system, system_ext, odm, product, or vendor partitions. »
It is precisely the use of TWRP that I took to back up my old LG or Samsung devices (S7, EDG or Tab 4 tablet)
Before the appearance of "dynamic partitions", there were no questions to ask to make a "Nandroid Backup" of your smartphone.
Now, since the arrival of OOS 10 and 11, things are different.
So here is my question for you:
If I check all the boxes by doing the backup and restore with TWRP (version 3.6.0), will the smartphone return to its general and precise state at the time of the backup? (See attached screenshots from TWRP)
If I understood correctly, TWRP performs a global image (super partition including A and B ) of all partitions at the time of backup, similar to an image of an SSD or HDD with several partitions… That's good that ?
I thank you in advance for your information and explanations and your instructions so that I can perform a "Nandroid Backup" and a possible restoration in complete safety.
Best regards
Jean-Noel

nadnan said:
Device OnePlus 8 Pro
OOS 11.0.10.10 IN11BA
TWRP 3.6
Root Magisk 23.0
Hello
Hello
I noted in your information above
“If you are used to using TWRP to backup your system partitions, then the way to do it now is to backup the super partition and not the system, system_ext, odm, product, or vendor partitions. »
It is precisely the use of TWRP that I took to back up my old LG or Samsung devices (S7, EDG or Tab 4 tablet)
Before the appearance of "dynamic partitions", there were no questions to ask to make a "Nandroid Backup" of your smartphone.
Now, since the arrival of OOS 10 and 11, things are different.
So here is my question for you:
If I check all the boxes by doing the backup and restore with TWRP (version 3.6.0), will the smartphone return to its general and precise state at the time of the backup? (See attached screenshots from TWRP)
If I understood correctly, TWRP performs a global image (super partition including A and B ) of all partitions at the time of backup, similar to an image of an SSD or HDD with several partitions… That's good that ?
I thank you in advance for your information and explanations and your instructions so that I can perform a "Nandroid Backup" and a possible restoration in complete safety.
Best regards
Jean-Noel
Click to expand...
Click to collapse
TWRP does image backups generally, but does file-based backups for data and some others (if I remember correctly, persist and EFS).
The "system" partitions on the OP8T are, as I mentioned, boot, dtbo, and super. This means that a "full" backup like in the "old days" is data plus the "system" partitions.
You could backup the other items in the TWRP backup list, but I'm going to ask you: Why do you want you do that?

BillGoss said:
TWRP does image backups generally, but does file-based backups for data and some others (if I remember correctly, persist and EFS).
The "system" partitions on the OP8T are, as I mentioned, boot, dtbo, and super. This means that a "full" backup like in the "old days" is data plus the "system" partitions.
You could backup the other items in the TWRP backup list, but I'm going to ask you: Why do you want you do that?
Click to expand...
Click to collapse
Hello
Thank you for your feedback.
I have taken note of the three system partitions you indicate.
With devices without a dynamic partition, I was "used" to saving all the data "as a precaution" on an external memory card and I was not limited in storage.
On the OnePlus 8 Pro, I have 256 GB of storage (without an external SD Card) and I could effectively limit the backup to the “Boot”, “DTBO” and “Super (System Syystem_ext product vendor)” partitions that you specify.
But I think that if I want to protect myself from any malfunction of the device after the restoration, it is better that I select all the partitions and then copy to PC the whole TWRP folder created by the " Nandroid”.
I could also buy a USB C / OTG adapter / SD card reader to store the backup…
Do you think I'm wrong?
Thanks again for your advice….
Best regards,

nadnan said:
Hello
Thank you for your feedback.
I have taken note of the three system partitions you indicate.
With devices without a dynamic partition, I was "used" to saving all the data "as a precaution" on an external memory card and I was not limited in storage.
On the OnePlus 8 Pro, I have 256 GB of storage (without an external SD Card) and I could effectively limit the backup to the “Boot”, “DTBO” and “Super (System Syystem_ext product vendor)” partitions that you specify.
But I think that if I want to protect myself from any malfunction of the device after the restoration, it is better that I select all the partitions and then copy to PC the whole TWRP folder created by the " Nandroid”.
I could also buy a USB C / OTG adapter / SD card reader to store the backup…
Do you think I'm wrong?
Thanks again for your advice….
Best regards,
Click to expand...
Click to collapse
Backing up partitions that you don't understand how they are used is rather pointless in my mind.
Restoring a partition that you don't understand how it's used is asking for trouble.
So I would never do that. But this is your phone and you can do whatever you want with it. Though learning more about how your device works and how the various partitions are used is a really good idea.
PS: you say you have an 8 Pro. You do realise that this is an 8T forum and that I'm writing about the 8T, not any other phone?

BillGoss said:
Backing up partitions that you don't understand how they are used is rather pointless in my mind.
Restoring a partition that you don't understand how it's used is asking for trouble.
So I would never do that. But this is your phone and you can do whatever you want with it. Though learning more about how your device works and how the various partitions are used is a really good idea.
PS: you say you have an 8 Pro. You do realise that this is an 8T forum and that I'm writing about the 8T, not any other phone?
Click to expand...
Click to collapse
Thank you for your remarks
Yes, I know about the 8T forum but I got here while researching the web and read that the OOS build is the same for both devices...
On the other hand, I have retained your words to know what each partition was used for and I will also direct my research on this subject.
Thanks again for your availability...
Sincerely...

Very intersting topic, and great explenation so far. I've came from old-school smartphone (Pocophone F1, without A/B partitions) and everything was so simple back then... I was about to switch from ROM to ROM on my brand new OP 8T , but I came into your topic and I realised that's something different. I have to search for some more info, because I'm looking forward to switch to colorOS (Or just other ROM in general. I just like switching and modifying my phone xD), but I'm wondering if, and how can I restore everything to stock, will I loose some widevine, mobile payment etc. I think everything is possible, I just have to make proper research. Anyway thank you again for that very interesting article!

Database Users

welcome