Related
I was reading rotohammer's post about an easy on-device backup method (using dd) that can restore data at a bit more of a lower level (Odin) than a nandroid backup. (EFS partitions, etc.)
It's possible to get your EFS partition in such a state that the /dev/block/bml3 and /dev/block/stl3 devices are no longer exposed on the device at all. This results in such nice behavior as the Cellular portion of the device not functioning at all. Providing you made a dd backup of all bml and stl devices (i.e. you have a backup of stl3 specifically,) you can recover from this situation.
Odin can recognize any file defined in the .pit file, when they are flashed to the PDA slot in a .tar, and place them in their proper partitions. One benefit to this is that if you get the EFS partition to a place where the device nodes aren't exposed to the OS anymore, you can restore it to working functionality.
These are the possible filenames that Odin recognizes: (from 512.pit, other .pits may have differing partition schemes.)
Code:
ries.pit
efs.rfs (this is the file we are going to restore to fix a broken EFS with a dd backup)
sbl.bin
param.lfs
zImage (kernel and recovery)
factoryfs.rfs
dbdata.rfs
cache.rfs
modem.bin
Any of these files are flashable by Odin3 1.7 if you place them in a .tar and put in the PDA slot.
rotohammer's post details which device matches up with which filename, in this case what we want to do is name the /dev/block/stl3 backup efs.rfs, and add it to a tar file (efs.tar) then flash it.
Assuming you have adb installed, and the stl3.bin file in the current folder:
adb push stl3.bin /sdcard/efs.rfs
adb shell
$ su
#
# cd /sdcard
# tar -cf efs.tar efs.rfs
# exit
$ exit
adb pull /sdcard/efs.tar
Now, get into download mode, open odin, stick efs.tar in PDA slot, and press start. Bam! EFS fixed
Note that in normal conditions you won't need a backup this extreme (copies of the files inside will be ok) but i've seen a number of users who have gotten their phones into this state (and did it myself during testing!) - This works with all the partitions you back up with dd that have support in your .pit file.
I've also used this to make an odin backup of my ROM, and flash it back later. This way you can have a pre-lagfixed ROM, for example
Dedicated to cerjam
how to obtain stl3 and bml3
in adb
adb shell
su (allow the root access)
cat /dev/block/stl3 > /sdcard/stl3.bak
cat /dev/block/bml3 > /sdcard/bml3.bak
rename .bak by .bin
sorry for my english.
Da_G said:
I was reading rotohammer's post
I've also used this to make an odin backup of my ROM, and flash it back later. This way you can have a pre-lagfixed ROM, for example
Dedicated to cerjam
Click to expand...
Click to collapse
How can I make ODIN back of my ROM, a little guide would help. Thanks in advance for your response.
trip007in said:
How can I make ODIN back of my ROM, a little guide would help. Thanks in advance for your response.
Click to expand...
Click to collapse
hi please use the search button , you will easily find how to , this is a 5 month old thread ....
Gonna go out on a limb and assume they are using search, hence the 5 month old post bump.
whiteguypl said:
Gonna go out on a limb and assume they are using search, hence the 5 month old post bump.
Click to expand...
Click to collapse
I dunno how they used it but htere s a 2 weeks old post by darky in the i9000 section .
can someone upload efs.rfs?efs.tar?
i screwd mine and i dont have backup
Every device has there own efs folder (IMEI and stuf).
So if you don't have a backup I don't know what to tell you...
thats not nv_data.bin or imei and product code stuffi want efs partition structure
wich come from stl3.bin
This thread may be almost a year old, but it just saved my Infuse.
Once again it just proves that if you serach, read, try and search, read and try somemore, you can find the answers.
Truckerglenn said:
This thread may be almost a year old, but it just saved my Infuse.
Once again it just proves that if you serach, read, try and search, read and try somemore, you can find the answers.
Click to expand...
Click to collapse
Someone gets it lolz .
Sent from my SAMSUNG-SGH-I897 using xda premium
moeinf said:
thats not nv_data.bin or imei and product code stuffi want efs partition structure
wich come from stl3.bin
Click to expand...
Click to collapse
Sorry im late...but adamoutler was going to post a blank efs partition in another thread . Dont know what happenwd to it tho.
Sent from my SAMSUNG-SGH-I897 using xda premium
Da_G said:
I was reading rotohammer's post about an easy on-device backup method (using dd) that can restore data at a bit more of a lower level (Odin) than a nandroid backup. (EFS partitions, etc.)
It's possible to get your EFS partition in such a state that the /dev/block/bml3 and /dev/block/stl3 devices are no longer exposed on the device at all. This results in such nice behavior as the Cellular portion of the device not functioning at all. Providing you made a dd backup of all bml and stl devices (i.e. you have a backup of stl3 specifically,) you can recover from this situation.
Odin can recognize any file defined in the .pit file, when they are flashed to the PDA slot in a .tar, and place them in their proper partitions. One benefit to this is that if you get the EFS partition to a place where the device nodes aren't exposed to the OS anymore, you can restore it to working functionality.
These are the possible filenames that Odin recognizes: (from 512.pit, other .pits may have differing partition schemes.)
Code:
ries.pit
efs.rfs (this is the file we are going to restore to fix a broken EFS with a dd backup)
sbl.bin
param.lfs
zImage (kernel and recovery)
factoryfs.rfs
dbdata.rfs
cache.rfs
modem.bin
Any of these files are flashable by Odin3 1.7 if you place them in a .tar and put in the PDA slot.
rotohammer's post details which device matches up with which filename, in this case what we want to do is name the /dev/block/stl3 backup efs.rfs, and add it to a tar file (efs.tar) then flash it.
Assuming you have adb installed, and the stl3.bin file in the current folder:
adb push stl3.bin /sdcard/efs.rfs
adb shell
$ su
#
# cd /sdcard
# tar -cf efs.tar efs.rfs
# exit
$ exit
adb pull /sdcard/efs.tar
Now, get into download mode, open odin, stick efs.tar in PDA slot, and press start. Bam! EFS fixed
Note that in normal conditions you won't need a backup this extreme (copies of the files inside will be ok) but i've seen a number of users who have gotten their phones into this state (and did it myself during testing!) - This works with all the partitions you back up with dd that have support in your .pit file.
I've also used this to make an odin backup of my ROM, and flash it back later. This way you can have a pre-lagfixed ROM, for example
Dedicated to cerjam
Click to expand...
Click to collapse
If I could Ill kiss you! Thank you it really did the trick!
Is there some way i can make a backup of my firmware?? Tried using Clockworkmod and the sorts but seems it isn't compatible
You'll need to root your device.
and use dd to pull from the /dev/block/bml* devices and copy them to an SD card.. The main ones you'd want are the zImage, and factoryfs ones. The bootloader ones aren't so necessary.
bml5 = zImage
bml6 = factoryfs
bml7 = datafs
I'm pretty sure..
precurse said:
You'll need to root your device.
and use dd to pull from the /dev/block/bml* devices and copy them to an SD card.. The main ones you'd want are the zImage, and factoryfs ones. The bootloader ones aren't so necessary.
bml5 = zImage
bml6 = factoryfs
bml7 = datafs
I'm pretty sure..
Click to expand...
Click to collapse
and...for recovery would be adb push?
For recovery you can use ODIN. You put those files into a single tar file, and tell it to flash. Lots of documentation on this on the forums.
File names would be:
zImage
factoryfs.rfs
datafs.rfs
what exact commands i should use to back up everything from my phone? so that i could restore it if something happens...
#cat /dev/block/* > /sdcard/*.img
* for stl4, bml4, bml5, bml6, bml7 ??? more? how about imei/efs folder?
Any noob-friendly instructions for this? I'd like to flash 2.2 to my i5800 but would like to make a backup first. What commands should I use?
I've got terminal emulator and busybox installed, do they do any help?
Is this method of NAND Backup for i5800 really working?
Hi,
I just want to check if this method of NAND Backup for i5800 is really working?
I would like to save my ROM before I upgrade to JPF.
Is this way of saving safe?
And is the ODIN restore of these savings safe?
I wouldn't like to make my phone brick.
I made that backup, weight something about 400MB
I had an bootloop, and want to restore this. Putted zImage, factoryfs.rfs and datafs.rfs to one .tar file and choosed One Package option.
But it was uploading Datafs for about 10 minutes, and nothing.
The progress bar in download mode, was taking second round, and stopped at ~160% D)
Now I have only 5 apps installed because I am messing with editing system apps, and flashing my phone every hour haha
How can I upload this?
Lots of documentation on this - Where?
precurse said:
For recovery you can use ODIN. You put those files into a single tar file, and tell it to flash. Lots of documentation on this on the forums.
File names would be:
zImage
factoryfs.rfs
datafs.rfs
Click to expand...
Click to collapse
Please, help! I googled a lot and still do not know which partitions to save, how to make the tar, and how to restore it using ODIN.
If someone knows these info, share with me. Please!
Edit:
I was not able to save stl5:
# dd if=/dev/block/stl5 of=/sdcard/zImage
dd if=/dev/block/stl5 of=/sdcard/zImage
/dev/block/stl5: cannot open for read: Invalid argument
JoHnNy08PL said:
I made that backup, weight something about 400MB
I had an bootloop, and want to restore this. Putted zImage, factoryfs.rfs and datafs.rfs to one .tar file and choosed One Package option.
But it was uploading Datafs for about 10 minutes, and nothing.
The progress bar in download mode, was taking second round, and stopped at ~160% D)
Now I have only 5 apps installed because I am messing with editing system apps, and flashing my phone every hour haha
How can I upload this?
Click to expand...
Click to collapse
Im noob in this but i heard that 200 MB is maximum.
Sent from my GT-I5800
Can someone post how one can backup efs? I did it thru adb on my one. Just want to make sure how to do it on the two. Thank you
From TWRP recovery choosing into backup only EFS
damsolu said:
From TWRP recovery choosing into backup only EFS
Click to expand...
Click to collapse
Thanks, had already done that and the files that it created didnt say modem.bin etc like it did when I backed up one my One a few months ago. Just want to make sure that what twrp created will be all i need to do? Thanks again
i lost my efs with no backup anyhelp?
godzulu said:
Thanks, had already done that and the files that it created didnt say modem.bin etc like it did when I backed up one my One a few months ago. Just want to make sure that what twrp created will be all i need to do? Thanks again
Click to expand...
Click to collapse
The last time I looked, the EFS backup option in TWRP didn't actually backup the two EFS partitions, so don't rely on it.
There's a flashable zip here that will backup your EFS partitions (modemst1 & modemst2). It also includes a Restore_EFS.bat file that can restore your EFS via fastboot.
Spannaa said:
The last time I looked, the EFS backup option in TWRP didn't actually backup the two EFS partitions, so don't rely on it.
There's a flashable zip here that will backup your EFS partitions (modemst1 & modemst1). It also includes a Restore_EFS.bat file that can restore your EFS via fastboot.
Click to expand...
Click to collapse
yeah..i have backup EFS from twrp but only realize that the EFS backup from TWRP is not EFS, now my IMEI2 lost & i dont know how to solve it. really head ache
I've done a complete device backup and could you tell me which files indicate efs has been backed up ? Is it modem.emmc.win or sbl1.emmc.win or some other file ?
akashpopat21 said:
I've done a complete device backup and could you tell me which files indicate efs has been backed up ? Is it modem.emmc.win or sbl1.emmc.win or some other file ?
Click to expand...
Click to collapse
Did you read the last few posts?
there is one more option, you can backup via flashfire
On creating a back up using TWRP it makes a file named "oem_stanvbk.emmc.win".... Maybe it is having two modems.....any idea how to explore this file? @Spannaa
Droidlover123 said:
On creating a back up using TWRP it makes a file named "oem_stanvbk.emmc.win".... Maybe it is having two modems.....any idea how to explore this file? @Spannaa
Click to expand...
Click to collapse
The oem_stanvbk partition contains the modem (static_nvbk.bin) which is included in OOS roms.
Not sure why you'd want to explore it...
I guess they lost the imei2 (h2o/erase modemst) and they are trying to find out, if this twrp backup file contains the imei2.
pryggi said:
I guess they lost the imei2 (h2o/erase modemst) and they are trying to find out, if this twrp backup file contains the imei2.
Click to expand...
Click to collapse
It doesn't, it's just the modem/radio.
AFAIK, the IMEIs are in modemst1 & modemst2 (The two modem firmware data partitions).
Yep, this is my understanding too. On op2 the modem firmware is in
oneplus2:/ # ls -l /dev/block/platform/soc.0/f9824900.sdhci/by-name
..
lrwxrwxrwx 1 root root 20 1970-08-26 21:51 modem -> /dev/block/mmcblk0p1
And the modem settings/imeis are in:
lrwxrwxrwx 1 root root 21 1970-08-26 21:51 modemst1 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-08-26 21:51 modemst2 -> /dev/block/mmcblk0p18
The question is, if it is possible to figure out the format of the data on p17/p18 and edit it by adding the imei2 back.
It doesn't seem to be a file system:
Oneplus2:/ # fdisk -l /dev/block/mmcblk0p17
Disk /dev/block/mmcblk0p17: 1 MB, 1572864 bytes
4 heads, 16 sectors/track, 48 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device /dev/block/mmcblk0p17: doesn't contain a valid partition table
file -L /dev/block/mmcblk0p17
/dev/block/mmcblk0p17: block special
and
blkid -o value -s TYPE /dev/block/mmcblk0p17
does not return anything.
And if you open the modemst1/2.bin files it seems to be binary data, which does not make sense even in hex editor.
I wonder if oneplus staff could help the poor souls who have lost the imei2 and disclose this info how to get imei2 back...
After a failed update and some flashing my 4G Connection is gone (sim is locked, no baseband).
Howeever I made a backup of persist.img, modemst1.img and modemst2.img months ago.
Couldn't figure out so far how to restore the files, could someone tell me how to do?
Code:
dd if=/path/to/persist.img*modemst1.img of=/path/to/persist*modemst1-partition
Thanx for the reply, so do I need to do this step 3 Times for all 3 Files?
dd if=/path/to/persist.img*modemst1.img of=/path/to/persist*modemst1-partition
would that mean then for modemst2:
dd if=/path/to/persist.img*modemst2.img of=/path/to/persist*modemst2-partition ???
Do I need another command for the persist.img too?
Sorry for asking, but I don't wanna mess up even more with my persist file.
How did you backup these partitions?
A .img file is a bit to bit copy of a partition or a drive.
Are you sure you have a backup ending with .img? That's very important for the way you restore your backup!!
If you have .img backups then you will restore them like this:
First copy your .img files to /sdcard (internal storage).
persist.img:
Code:
dd if=/sdcard/persist.img of=/dev/block/by-name/persist
modemst1.img
Code:
dd if=/sdcard/modemst1.img of=/dev/block/by-name/modemst1
modemst2.img
Code:
dd if=/sdcard/modemst2.img of=/dev/block/by-name/modemst2
Restart your device!
Thanx for the reply,
My files are definately .img files, I backed them up months ago when starting with the Custom Rom Stuff, too be (hopefully) save.
Backed them up with this 3 commands
dd if=/dev/block/mmcblk0p2 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/modemst2.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/persist.img
Was long ago so I couldn't remember exactly everything in Detail.
One Question left, setting the Commands while in Bootloader, TWRP or normal in system?
Dave-C said:
Thanx for the reply,
My files are definately .img files, I backed them up months ago when starting with the Custom Rom Stuff, too be (hopefully) save.
Backed them up with this 3 commands
dd if=/dev/block/mmcblk0p2 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/modemst2.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/persist.img
Was long ago so I couldn't remember exactly everything in Detail.
One Question left, setting the Commands while in Bootloader, TWRP or normal in system?
Click to expand...
Click to collapse
Are you sure you backed up mmcblk0p2/3/4?? Because these partitions are definitively not the persist or modemst ones! If you execute the commands above you will override your partitions with the wrong data!!
WoKoschekk said:
Are you sure you backed up mmcblk0p2/3/4?? Because these partitions are definitively not the persist or modemst ones! If you execute the commands above you will override your partitions with the wrong data!!
Click to expand...
Click to collapse
Yes backed up with these 3 Commands, found them somewhere in this board.
Had these commands saved on my PC, so definately used them but probably good that I didn't used them yet.
Howeever, I also have a TWRP Backup with EFS and persist files (efs1.emmc.win, efs2emmc.win, persist.ext4.win).
How could I use them, simply via TWRP or better way to do this?
Can't Believe it....
After lots of flashing (Back to Stock etc.) I got my 3G/4G/Baseband Connections back!
Could you tell me the right Commands to backup the Persist/EFS/Modem Parts?
Anyways thank you so much for patiently helping me through this.
Thanx!
Use the TWRP backups. They're perfect!
Did the TWRP Backups now.
In case you know the commands for the img output, i'd still like to know.
I'd like an independent solution, since I had two TWRP Backups each with the EFS/Partition Backup, while 1 of them was somehow not working (error output).
So i'd like to be as secure as possible.
You need the dd command to create an image of each partition. The partitions on your device are numbered consecutively:
persist= /dev/block/mmcblk0p38
modemst1= /dev/block/mmcblk0p34
modemst2= /dev/block/mmcblk0p35
Open a terminal app and type:
for persist:
Code:
dd if=/dev/block/[B]mmcblk0p38[/B] of=/sdcard/persist.img
if= input file (partition)
of= output file (.img backup)
Hello, I am having the same problem but only with a backup with no IMEI. Does anyone know how to solve this? Or to merge these two backups to form one with IMEI and stable signal. The backups are encrypted I guess because nothing makes sense in them
juampapo546 said:
Hello, I am having the same problem but only with a backup with no IMEI. Does anyone know how to solve this? Or to merge these two backups to form one with IMEI and stable signal. The backups are encrypted I guess because nothing makes sense in them
Click to expand...
Click to collapse
What kind of backup do you have?? What is a backup with no IMEI?
WoKoschekk said:
What kind of backup do you have?? What is a backup with no IMEI?
Click to expand...
Click to collapse
TWRP backup of persist and efs
When I made the backup I had no IMEI but the wifi was working (I actuall made the backup after the signal drop issue)
juampapo546 said:
TWRP backup of persist and efs
When I made the backup I had no IMEI but the wifi was working (I actuall made the backup after the signal drop issue)
Click to expand...
Click to collapse
If you don't have a backup of /persist with a IMEI then you won't be able to restore it.
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
WoKoschekk said:
If you don't have a backup of /persist with a IMEI then you won't be able to restore it.
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Click to expand...
Click to collapse
But isn't there a way to edit the backup or merge both backups I have?
(However when I erase modemst1 and 2 IMEI comes back but with the signal drop, a fix for that would also help me)
For the right understanding:
You have two different TWRP backups for /persist and /efs. The first one restores IMEI but signal is lost and the other one restores your signal without IMEI??
WoKoschekk said:
For the right understanding:
You have two different TWRP backups for /persist and /efs. The first one restores IMEI but signal is lost and the other one restores your signal without IMEI??
Click to expand...
Click to collapse
I am so sorry I answered this late, yes that is correct and I have been using my phone with WiFi only for months now
Try to merge them manually if you know the corresponding files. I've no idea how to figure them out...
TWRP won't merge your backups.
Hello,
I managed to break my fingerprint reader. I don't think the problem is my /persist because all sensors work fine. But unfortunately, I had never backed up the rest of the sensitive partitions: vbmeta, vbmeta_system, keystore, keymaster, odm, core_nhlos, secdata, abl, cmnlib, cmnlib64, devcfg, dsp, hyp, xbl, xbl_config, tz, rpm, aging, aging_mod.
Could someone on a TMO 7t Pro 5G McLaren (with a working fingerprint reader preferably running the latest 10.0.35 software, please pull and post these partition img files? If you don't know how, it's very simple, please ask.
I point to this because my previous phone, Essential PH1, had similar issues, but at least Essential had posted all of the firmware images on their website every month, and flashing the above partitions would fix it. 1+ doesn't provide anything and even the MSM doesn't restore all of these partitions.
Thanks so very very much in advance!
Edit: If possible, could one extract all partition img files from 10.0.35 in addition to those requested above?
EDIT2: ODM partition has 1st priority for anyone who can help.
Edit3: odm is fine. After looking through some logs,
I need keystore, keymaster (_a or _b, whichever is your current slot), vbmeta (a or b), and vbmeta_system (a or b). None are very large I think.
You're making me want a backup. I thought MSM was supposed to be that for us. Irritating.
A couple of those look like they could have sensitive data. Anyone know of a reason not to post them? Looks like they are all available via /dev/block..
ttabbal said:
You're making me want a backup. I thought MSM was supposed to be that for us. Irritating.
A couple of those look like they could have sensitive data. Anyone know of a reason not to post them? Looks like they are all available via /dev/block..
Click to expand...
Click to collapse
If you don't already have a backup of every partition, please please please do so urgently. Or an RMA will most likely be in your future. That should be in huge bold print with a link to instructions at the very top of the root and bootloader unlock threads.
I've never had a device with these issues before. It's starting to get ridiculous.
Edit: If you didn't take backups before unlocking the bootloader, Widevine L1 support (being able to watch Netflix in HD instead of 480p crap on our giant beautiful screens) is lost forever (except for RMA). And just flashing a "bad" canary version of magisk was enough to kill the fingerprint sensor. Of course I didn't learn any of this until it was too late.
MSM will get your phone back to life but not fully heal it. Basically all the MSM is guaranteed to do is get the phone to boot. No sensors, no fingerprint, no Widevine L1, no IMEI and wifi Mac address fix (if one is really screwed). And 1+ didn't take any measures to protect the sensitive partitions once bootloader is unlocked. It's all just a clusterf**k
Same issues on 7T and 8 and 8pro if that makes you feel any better ¯\_(ツ)_/¯
Well, that's irritating. WTF wouldn't you have a recovery tool for all those? Interestingly, I don't seem to have odm in there at all. Ah, scratch that, it's in /dev/block/mapper and there are 3. _a, _b, -verity.
It's rpm I don't seem to have. 10.0.35.
ttabbal said:
Well, that's irritating. WTF wouldn't you have a recovery tool for all those? Interestingly, I don't seem to have odm in there at all. Ah, scratch that, it's in /dev/block/mapper and there are 3. _a, _b, -verity.
It's rpm I don't seem to have. 10.0.35.
Click to expand...
Click to collapse
Yeah, system, vendor, product, and odm are stored in super.img on Android 10. But u found it. Find out what slot you are on, running 10.0.35, and you'd want the _a or _b files that match your current slot.
ttabbal said:
Well, that's irritating. WTF wouldn't you have a recovery tool for all those? Interestingly, I don't seem to have odm in there at all. Ah, scratch that, it's in /dev/block/mapper and there are 3. _a, _b, -verity.
It's rpm I don't seem to have. 10.0.35.
Click to expand...
Click to collapse
I think you are right. Rpm doesn't exist possibly on this phone. Don't have time to research right now.
But I noticed in /dev/block/mapper, I only have _a and _b. No -verity file. For system, vendor, odm, nor product. Could you post the -verity file(s)?
What files/file sizes do you have in /odm/ ?
starcms said:
I think you are right. Rpm doesn't exist possibly on this phone. Don't have time to research right now.
But I noticed in /dev/block/mapper, I only have _a and _b. No -verity file. For system, vendor, odm, nor product. Could you post the -verity file(s)?
What files/file sizes do you have in /odm/ ?
Click to expand...
Click to collapse
Doesn't look really interesting to me, but here's the ls output.
Code:
OnePlus7TProNR:/sdcard/img # ls -l /odm
total 20
drwxr-xr-x 4 root root 4096 2008-12-31 17:00 etc
drwx------ 2 root root 16384 2008-12-31 17:00 lost+found
OnePlus7TProNR:/sdcard/img # ls -l /odm/etc
total 12
-rw------- 1 root root 2735 2008-12-31 17:00 build.prop
-r--r--r-- 1 root root 0 2008-12-31 17:00 fs_config_dirs
-r--r--r-- 1 root root 0 2008-12-31 17:00 fs_config_files
drwxr-xr-x 2 root root 4096 2008-12-31 17:00 selinux
drwxr-xr-x 2 root root 4096 2008-12-31 17:00 vintf
OnePlus7TProNR:/sdcard/img # ls -l /odm/etc/selinux/
total 728
-rw-r--r-- 1 root root 733547 2008-12-31 17:00 precompiled_sepolicy
-rw-r--r-- 1 root root 65 2008-12-31 17:00 precompiled_sepolicy.plat_sepolicy_and_mapping.sha256
-rw-r--r-- 1 root root 65 2008-12-31 17:00 precompiled_sepolicy.product_sepolicy_and_mapping.sha256
OnePlus7TProNR:/sdcard/img # ls -l /odm/etc/vintf/
total 16
-rw-r--r-- 1 root root 5300 2008-12-31 17:00 manifest.xml
-rw-r--r-- 1 root root 1369 2008-12-31 17:00 manifest_ese.xml
-rw-r--r-- 1 root root 622 2008-12-31 17:00 manifest_noese.xml
I can try, but my upstream sucks. It might be faster for someone else to grab them.
-rw-r--r-- 1 travis travis 816K Jun 4 15:40 img/odm-verity.img
-rw-r--r-- 1 travis travis 1.3G Jun 4 15:41 img/product-verity.img
-rw-r--r-- 1 travis travis 2.2G Jun 4 15:40 img/system_root-verity.img
-rw-r--r-- 1 travis travis 884M Jun 4 15:43 img/vendor-verity.img
After looking through some logs, you can ignore most of that.
I need keystore, keymaster (_a or _b, whichever is your current slot), vbmeta (a or b), and vbmeta_system (a or b). None are very large I think.
Thanks for all of your time @ttabbal. Sorry if I'm driving you crazy Been driving myself crazy trying to fix this for 2 weeks now lol
My /odm seems to be fine. Matches yours. I was mainly concerned about those 2 files with 0 size. But I don't have any of the -verity.imgs from /dev/block/mapper. I'm pretty sure they are supposed to be created and mounted at boot (from super.img and by verity/vbmeta). I'm hoping those 2 vbmeta partitions will fix things up. If not, then I'll try keystore and keymaster. And then I'll have to send it in...
Edit:. Just curious, I'm assuming you are bootloader unlocked and running Magisk? Just confirming since you have those -verity.imgs
ok.. Hope it helps.
https://drive.google.com/file/d/1a9FTbvdEM2n12wjc4SL7kNMu3SAtfuAY/view?usp=sharing
https://drive.google.com/file/d/15Ssumik6iMY7kWgldHfFajsbyNdh9aTz/view?usp=sharing
Yes, I am unlocked and rooted with Magisk.
ttabbal said:
ok.. Hope it helps.
https://drive.google.com/file/d/1a9FTbvdEM2n12wjc4SL7kNMu3SAtfuAY/view?usp=sharing
https://drive.google.com/file/d/15Ssumik6iMY7kWgldHfFajsbyNdh9aTz/view?usp=sharing
Yes, I am unlocked and rooted with Magisk.
Click to expand...
Click to collapse
Well, not exactly lol.
Flashed your two images via fastboot, still broken fingerprint and still missing -verity files from /dev/block/mapper/ , went to flash my backups of vbmeta and vbmeta_system via fastboot, got into a bootloop, and after a couple hours of screwing with it, finally got back where I started from...except using your images.
I don't understand. vbmeta and vbmeta_system are NOT device specific. One from my phone, one from your phone, one from anyone's phone running 10.0.35 should be exactly the same.
What exact method did you use to pull the images? dd to a tmp dir on device and then adb pull img? dd directly to computer? or adb pull the partitions themselves direct to computer? Shouldn't all 3 methods return the same results?
I swear, after the RMA I really don't know if I am going to risk unlocking the bootloader again (this is coming from someone who has had s-off/bootloader unlock/root/su/Magisk on every single android device ever owned over the past 10 years...without ever having any problem I couldn't fix by myself)
It should all be the same img, but I did "dd bs=1M if=/dev/<partition> of=/sdcard/img/" and adb pull them to the computer. Pretty much the same dd command I use for most image work. I am on 10.0.35.
One of the biggest reasons I gave this device a shot was the ability to reflash back to stock. Now I hear that doesn't work. That's really annoying. This is something Oneplus should just provide as a backup. They don't even have to keep it up to date. We can OTA our way to the latest. They have to have something like that to flash the phones before shipping them out. I guess they could flash to storage chips before installing them on the PCBs.
I was also hoping to see some development, I didn't realize that the A/B thing or A10 was going to cause so many problems. Not the devs fault, just one more thing to shake my head at. Sadly, I think root stuff is going to start phasing out. I don't mind no support for modified software, but I hate that I don't own my devices.
ttabbal said:
It should all be the same img, but I did "dd bs=1M if=/dev/<partition> of=/sdcard/img/" and adb pull them to the computer. Pretty much the same dd command I use for most image work. I am on 10.0.35.
One of the biggest reasons I gave this device a shot was the ability to reflash back to stock. Now I hear that doesn't work. That's really annoying. This is something Oneplus should just provide as a backup. They don't even have to keep it up to date. We can OTA our way to the latest. They have to have something like that to flash the phones before shipping them out. I guess they could flash to storage chips before installing them on the PCBs.
I was also hoping to see some development, I didn't realize that the A/B thing or A10 was going to cause so many problems. Not the devs fault, just one more thing to shake my head at. Sadly, I think root stuff is going to start phasing out. I don't mind no support for modified software, but I hate that I don't own my devices.
Click to expand...
Click to collapse
What is the need or result of the "bs=1M" in the command? I've never seen that before in other threads. I'm assuming it means block size equal to 1MB. Is that definitely required to get a good pull? Same bs for any/all partitions?
If you have persist and both EFS images backed up, you should be okay. The MSM tool can restore I think everything else. I'd keep a backup especially of any partitions that don't end in _a or _b. The MSM tool definitely takes care of the rest (those ending in _a and _b). I just hate using it because there's no way to make it not wipe userdata. And without being able to make a nandroid backup due to no fully working twrp due to A10, it's just a giant pain.
And unfortunately we can't just OTA our way to the latest, at least not by manually downloading an OTA from 1+. Only way to update is with a real OTA update from T-Mobile.
The A/B partitioning isn't the problem with development. That's been around since Android 7 or 8. It's the new dynamic partitioning format that all phones that launch with Android 10 (or newer) have. Even the Pixel 4 doesn't have fully working twrp yet. It's coming soon though...
Edit: Also, for the dd commands, did you use /dev/block/actual_partition or /dev/block/by-name/friendly_name_of_partition? Again, should it really make a difference?
Edit2: All of these issues have a root cause from Android 10. The new required partitioning system for any phones that launch with it. That's why unlocking the bootloader wipes reserve.img. Because it's in userdata (cause of A10) and 1+ forgot about that and didn't rewrite the algorithm used when the bootloader is unlocked. It's also their negligence (combined with A10) which causes persist (and other key partitions) to become so easily corrupted. Virtually all devices launched since Android 7 use "fastboot flashing unlock" and then "fastboot flashing unlock_critical" to allow changes to device specific partitions. For some reason 1+ still is using the antiquated "fastboot oem unlock" command which unlocks literally everything, even some stuff that unlock_critical doesn't, and which in the old days, didn't matter. A10 especially should not ever be used with fastboot oem unlock. Google says so lol.
If it makes you feel better, this isn't unique to this phone. It's a problem on every device 1+ has launched with A10 and still is (OP7T/TPro/OP8/Pro). Because of A10 partitioning combined with the use of an antiquated bootloader that only supports "fastboot oem unlock"
The block size doesn't matter for the pull and doesn't change the image at all. It just reads in chunks, making it faster.
Yes, I used by-name and it shouldn't matter if you use that or the sd# names.
It's your persist and it's unique. The rest of your sensors won't care. If you didn't back it up, you're screwed. An MSM restore doesn't fix this.
LLStarks said:
It's your persist and it's unique. The rest of your sensors won't care. If you didn't back it up, you're screwed. An MSM restore doesn't fix this.
Click to expand...
Click to collapse
The issue is I had a backup of my unique persist. And restoring it doesn't fix the dang fingerprint. That's why I was thinking the issue had to be elsewhere