Develop Bugs

[REF] SGS2 PIT File

SGS2 has changed a lot from SGS1 with filesystems, since there is no RFS anymore. The PIT file looks pretty different now too.
Code:
GANG : emmc.img
BOOT : boot.bin
EFS : efs.img
SBL1 : Sbl.bin
SBL2 : bl.bin (?)
PARAM : param.lfs
KERNEL : zImage
RECOVERY : (blank, unlike SGS1 which was a copy of zImage)
CACHE : cache.img
MODEM : modem.bin
FACTORYFS : factoryfs.img
DATAFS : data.img
HIDDEN : hidden.img
Preliminary notes:
Recovery is blank instead of zImage. Not sure what this could mean - it's possible that this is now unflashable? It's also possible that this is no longer used, and the kernel is used directly.
Something called GANG is at the top of the file. No idea what this is. Stuff at the top is usually lower level. It does have the image file name emmc though, http://en.wikipedia.org/wiki/MultiMediaCard#eMMC
eMMC describes an architecture consisting of an embedded storage solution with MMC interface, flash memory and controller, all in a small ball grid array (BGA) package.[4]
Embedded MultiMediaCard (e-MMC) e-MMC/Card Product Standard, High Capacity, including Reliable Write, Boot, Sleep Modes, Dual Data Rate, Multiple Partitions Supports and Security Enhancement
Click to expand...
Click to collapse
Sounds interesting, anyway.
FactoryFS and Data are now seperate, when in the SGS1 they were the same thing. (SGS1 copied over /data from inside factoryfs when it was not found - this means that factory reset might work differently here.)
hidden.img is part of the CSC, not sure what this could be, or even why it's here. Will have to look inside the img file to find out, I guess. CSC is usually just extra files placed in /system
SBL2 is bl.bin instead of Sbl.bin - typo by Samsung?
Since this is all EXT4 now, we might actually be able to re-size things properly now, as in the SGS1 with it's RFS stuff the /system partition couldn't actually be resized.
EDIT: Adding some reference stuff from the device.
All partitions appear to be directly off mmcblk0 - there are 12 of them. Output follows:
Code:
brw------- root root 179, 12 2011-05-08 10:35 mmcblk0p12
brw------- root root 179, 11 2011-05-08 10:35 mmcblk0p11
brw------- root root 179, 10 2011-05-08 10:35 mmcblk0p10
brw------- root root 179, 9 2011-05-08 10:35 mmcblk0p9
brw------- root root 179, 8 2011-05-08 10:35 mmcblk0p8
brw------- root root 179, 7 2011-05-08 10:35 mmcblk0p7
brw------- root root 179, 6 2011-05-08 10:35 mmcblk0p6
brw------- root root 179, 5 2011-05-08 10:35 mmcblk0p5
brw------- root root 179, 4 2011-05-08 10:35 mmcblk0p4
brw------- root root 179, 3 2011-05-08 10:35 mmcblk0p3
brw------- root root 179, 2 2011-05-08 10:35 mmcblk0p2
brw------- root root 179, 1 2011-05-08 10:35 mmcblk0p1
Partitions map as follows:
Code:
/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
Not sure what the unmapped partitions are for yet.

Nice, i had a look at the partitions table to, and can verify your find. Lets see if we can make some useful of this.

Doc! I hope you got your SGS2 as SGS2 definitely need you
RyanZA! I hope you also got your SGS2, as Dev forums cannot live without you
DocRambone said:
Nice, i had a look at the partitions table to, and can verify your find. Lets see if we can make some useful of this.
Click to expand...
Click to collapse

nasgilani said:
Doc! I hope you got your SGS2 as SGS2 definitely need you
RyanZA! I hope you also got your SGS2, as Dev forums cannot live without you
Click to expand...
Click to collapse
Hahah, I've got one. To be honest though, I'm having a hard time finding anything I actually want to mod. Samsung has actually done a very good job this time around.

i can think of a few..
1. sound is not as good as my sgs with voodoo sound.
2. 2e recovery right on the phone would be nice
3. lower minimim brightness level
4. transparent status bar...
5. correctly working vpn and wpa_supplicant with adhoc mode working.
6. extra batteris i can charge with a wall charger so i can always have a spare in my pocket (they appear to be not out yet.. the idiots on ebay are selling the wrong battery and chargers for the phone)
7. working sip stack built into gingerbread like it should be.

Nothing to mod? Sounds like a boring phone.

RyanZA why did you leave the SGS scene? I miss you

jaju123 said:
RyanZA why did you leave the SGS scene? I miss you
Click to expand...
Click to collapse
With all the mods/devs for the SGSI, everything on that device already works perfectly (imo anyway). There was nothing left that I wanted to change, and all the cool projects are well in hand by people who don't want help/don't need help.
And the main problem: I got an SII, which makes it hard to look at the SI these days.

sorry for question maybe answer is allready at the forum. But can i RESIZE system ?? Now i want put there somethink (3mb) by xplore but i cant. Its says that temp file cant be writen.... when i delete somthink (3mb) from system its ok. So system is full... can i resize it?

Alcatel 960C/ One Touch Authority

Has anyone created a clockworkmod for this? This phone can be rooted, thru two apps, poot, and ministro(Qt). It still has gingerbread 2.3.6, and I need clockworkmod, or the source code, to use clockworkmod's builder. It is the cdma variant of the alcatel 995(which is gsm). can anyone point me in the right direction?

Source Code
I have it rooted, with adb insecure running, to see everything. My bootloader seems to be locked, and the recovery is unknown, with limited options. I can do most things, except change roms, wipe data, or cache in recovery. I would like to be directed to good repository.

reggjoo said:
I have it rooted, with adb insecure running, to see everything. My bootloader seems to be locked, and the recovery is unknown, with limited options. I can do most things, except change roms, wipe data, or cache in recovery. I would like to be directed to good repository.
Click to expand...
Click to collapse
how did you get it rooted?

rooting alcatel authority (960c)
squidbutt said:
how did you get it rooted?
Click to expand...
Click to collapse
First make sure you have USB Debugging checked and your allowing instalation of unknown sources
DL these from the play store:
Minstro2
Superuser
DL poot.apk: View attachment poot.zip
Run poot, click yes to download the extra librarys, click "click here to poot" you will need to restart the phone when it prompts. You should be rooted now :good:
You can DL ES File Explorer(from play store) and in the settings check: Root Explorer, Up to Root and Mount File System. Now you can manage all the files on your phone but be careful of what you delete, some of the stock apk's are very hard to recover if you delete them.
Hope this helps

Download superuser first
Download superuser first, you won't be able to run it until the phone's rooted. after it's rooted, it will work. This way, seems to stop a problem, when you go thru the steps to root. Some people had a error. If you plan to open the /data, /system, or dalvik cache, on your computer, install chainfire's adb insecure. These folders don't open without this, on a computer.

I have the kernel source here, they have it released on SourceForge I'm guessing you're right saying the bootloader is locked.
Here's some information I've found on the partitions:
mmcblk0 Internal Memory
mmcblk0p1 Mounted using VFAT Contains files pertaining to FOTA (FOTA partition?)
mmcblk0p2 500 blocks ?
mmcblk0p3 1500 blocks ?
mmcblk0p4 1 BLOCK ?
mmcblk0p5 1000 blocks ?
mmcblk0p6 2000 blocks ?
mmcblk0p7 3072 blocks ?
mmcblk0p8 5120 blocks Possible Recovery*
mmcblk0p9 7000 blocks ?
mmcblk0p10 3027 blocks ?
mmcblk0p11 3072 blocks ?
mmcblk0p12 5120 blocks ?
mmcblk0p13 1500 blocks ?
mmcblk0p14 8192 blocks Mounts to /persist
mmcblk0p15 5120 blocks?
mmcblk0p16 1024 blocks?
mmcblk0p17 409600 blocks, Mounts to /system
mmcblk0p18 307200 blocks, Mounts to /cache
mmcblk0p19 892928 blocks, Mounts to /data
mmcblk0p20 122880 blocks, partition appears empty with a sting at the bottom of it reading ANDROID-BOOT!
mmcblk1 SD Card
mmcblk1p1 SD Card Partition
build.prop (Alltel phone):
build.prop
Source Code:
SourceForge Download Link
* In a recent patch I have found, the following code was in the install-recovery.sh file:
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p15:2048:afbffa74556cd8e77ef7e1a9d0964d9a2bd446b8; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Any other information needed?
I'll look into getting a recovery working, but this is by no means a promise.
EDIT:
Something interesting:
The build.prop says the phone has a MSM7630_SURF board, and the Huawei U8800 has the same board, but not quite the same specs:
960C:
480x800
Multitouch
1400 Mhz CPU Sapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
3G
U8800:
480x800
Multitouch
800 Mhz CPU Snapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
AT&T has a 3g version
I'm betting these two are compatible, and the files I found contain some boot information.
Update:
I found the recovery.fstab for the U8800, doesn't look quite right does it:
Code:
# mount point fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
I'm not sure how exactly to make this resemble the above partition table...
Update:
More information:
U-boot seems to support this board? Maybe this is good?
http://lists.denx.de/pipermail/u-boot/2012-February/118168.html
Also if anyone else wants to take a stab at this, by all means. I'm having trouble getting the tools set up, but if someone with a little more experince wants to that would be great.

Haven't seen this
aldude999 said:
I have the kernel source here, they have it released on SourceForge I'm guessing you're right saying the bootloader is locked.
Here's some information I've found on the partitions:
mmcblk0 Internal Memory
mmcblk0p1 Mounted using VFAT Contains files pertaining to FOTA (FOTA partition?)
mmcblk0p2 500 blocks ?
mmcblk0p3 1500 blocks ?
mmcblk0p4 1 BLOCK ?
mmcblk0p5 1000 blocks ?
mmcblk0p6 2000 blocks ?
mmcblk0p7 3072 blocks ?
mmcblk0p8 5120 blocks Possible Recovery*
mmcblk0p9 7000 blocks ?
mmcblk0p10 3027 blocks ?
mmcblk0p11 3072 blocks ?
mmcblk0p12 5120 blocks ?
mmcblk0p13 1500 blocks ?
mmcblk0p14 8192 blocks Mounts to /persist
mmcblk0p15 5120 blocks?
mmcblk0p16 1024 blocks?
mmcblk0p17 409600 blocks, Mounts to /system
mmcblk0p18 307200 blocks, Mounts to /cache
mmcblk0p19 892928 blocks, Mounts to /data
mmcblk0p20 122880 blocks, partition appears empty with a sting at the bottom of it reading ANDROID-BOOT!
mmcblk1 SD Card
mmcblk1p1 SD Card Partition
build.prop (Alltel phone):
build.prop
Source Code:
SourceForge Download Link
* In a recent patch I have found, the following code was in the install-recovery.sh file:
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p15:2048:afbffa74556cd8e77ef7e1a9d0964d9a2bd446b8; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Any other information needed?
I'll look into getting a recovery working, but this is by no means a promise.
EDIT:
Something interesting:
The build.prop says the phone has a MSM7630_SURF board, and the Huawei U8800 has the same board, but not quite the same specs:
960C:
480x800
Multitouch
1400 Mhz CPU Sapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
3G
U8800:
480x800
Multitouch
800 Mhz CPU Snapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
AT&T has a 3g version
I'm betting these two are compatible, and the files I found contain some boot information.
Update:
I found the recovery.fstab for the U8800, doesn't look quite right does it:
Code:
# mount point fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
I'm not sure how exactly to make this resemble the above partition table...
Update:
More information:
U-boot seems to support this board? Maybe this is good?
http://lists.denx.de/pipermail/u-boot/2012-February/118168.html
Also if anyone else wants to take a stab at this, by all means. I'm having trouble getting the tools set up, but if someone with a little more experince wants to that would be great.
Click to expand...
Click to collapse
Hello, I haven't looked into this thread for a while. I see that you have some info for these blocks. that I couldn't get. I tried using root explorer, to look into some files, and they couldn't load, and tried to use too much memory, just to attempt to open, which, my phone said it was low on memory. Hate gingerbread, and kwansi choi( maker of this rom), This phone could easily handle a later os.
The usb ID's, are "Device 007: ID 1bbb:9018" .

USB ID's
The usb ID's are 1bbb/9018 . I built a clockworkmod File, and the status is ok, but it still won't flash, because of the bootloader.

reggjoo said:
The usb ID's are 1bbb/9018 . I built a clockworkmod File, and the status is ok, but it still won't flash, because of the bootloader.
Click to expand...
Click to collapse
I noticed that:
mmcblk0p15
mmcblk0p12
mmcblk0p8
all have the same number of blocks.
The FOTA code shows
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
Click to expand...
Click to collapse
applypatch useage is as follows:
applypatch [-b <bonus-file>] <src-file> <tgt-file> <tgt-sha1> <tgt-size> [<src-sha1>:<patch> ...]
or applypatch -c <file> [<sha1> ...]
or applypatch -s <bytes>
or applypatch -l
Click to expand...
Click to collapse
Apply patch from blk8 to blk15.
So maybe I was mistaken with what I thought was the partition. Blk8 seems to be where fota grabs it's updated partition from?
This shows that blk15 may actually be the recovery partition. Still useless unless the bootloader can be worked on.

Battery terminals
As we know, if the battery is out, the phone will do nothing( unlike my old huawei, it didn't matter). I wondered if that was the reason why, it's so hard to unlock it. I think the bootloader has been set up to not respond to attempts. The bootloader condition treats the phone as if there's no power to it(?) . I found out that the middle terminals, of the battery contacts, will power the phone, if they're connected, but only for a few seconds.
Maybe there's some code that's unknown, or procedure. The phone doesn't respond to fastboot commands, and I can't enable it(function), on it. In the default.prop file, I see that ro.secure, is 1. Whenever I try to change it to 0( in rewritable mode), it never takes. So this is a little info.

reggjoo said:
The bootloader condition treats the phone as if there's no power to it(?)
Click to expand...
Click to collapse
You know, it's interesting that you mention that. I remember watching a Ben Heck episode, and on an Xbox 360 controller keypad, he had to open it up and connect power to the PIC chip manually. It almost makes me wonder if there's possibly a jumper of some sort on the motherboard somewhere that when connected allows writing? It would be an extremely long shot, I'm even pretty sure that it's the exact board in the Huawei but it's weird that fastboot can't be entered. I've heard that their drivers might be messed up (maybe even on purpose) that could keep you from using fastboot.

aldude999 said:
You know, it's interesting that you mention that. I remember watching a Ben Heck episode, and on an Xbox 360 controller keypad, he had to open it up and connect power to the PIC chip manually. It almost makes me wonder if there's possibly a jumper of some sort on the motherboard somewhere that when connected allows writing? It would be an extremely long shot, I'm even pretty sure that it's the exact board in the Huawei but it's weird that fastboot can't be entered. I've heard that their drivers might be messed up (maybe even on purpose) that could keep you from using fastboot.
Click to expand...
Click to collapse
Yes, I think alcatel's a little shady. I use a dual boot pc, and I found out, using the lsusb command, that the usb id's were different, than what the id's were for the supposedly official usb drivers. Sent them a msg, and they said I was wrong( can't be wrong if everything works!). They take no responsibility for their hardware, and I let people know, every chance I get, whenever I see a review of a phone from them. I found out the id's were wrong, when, before I even rooted it, I installed their onetouchmanager, and it couldn't find my phone( what! out the box!). That's not the way you do things.

Bringing 960C Back To Life!!!
Did anyone ever find a ROM that's compatible with the 960C? I recently found one floating around a storage unit and, naturally, I immediately rooted it only to find out that no one ever bothered developing a custom ROM.
I'm sure if an official ROM was never created specifically for the 960C, it's definitely not gonna happen at this point. I'm thinking that the only hope for the 960C is if it was similar enough to a more popular phone that HAS a custom ROM, maybe someone, somewhere, was successful in modding it just enough to make it compatible with the 960C...
During my research/investigation into a ROM, there was at least one (*HERE*) forum post mentioning someone attempting to mod an existing ROM (for a more popular phone) to make it compatible but it seems that everyone lost interest back in 2013...

thealexday said:
Did anyone ever find a ROM that's compatible with the 960C? I recently found one floating around a storage unit and, naturally, I immediately rooted it only to find out that no one ever bothered developing a custom ROM.
I'm sure if an official ROM was never created specifically for the 960C, it's definitely not gonna happen at this point. I'm thinking that the only hope for the 960C is if it was similar enough to a more popular phone that HAS a custom ROM, maybe someone, somewhere, was successful in modding it just enough to make it compatible with the 960C...
During my research/investigation into a ROM, there was at least one (*HERE*) forum post mentioning someone attempting to mod an existing ROM (for a more popular phone) to make it compatible but it seems that everyone lost interest back in 2013...
Click to expand...
Click to collapse
I still am using my 960c. I wouldn't mind finding the original stock rom or finding out how to upgrade to a newer android version. Currently running version 2.3.6
Too bad I don't know much about modding save for rooting and flashing. I gather there are still some of us here who really like our 960c phones otherwise.

Miroslav's CM11 flashing methods

Hello friends,
I have tried to flash every update of the Miroslav's rom unsuccessfuly. These are the metods I have tried:
SWETNES METHOD: ...Format system partition FIRST then flash ROM, then format cache, then do a FACTORY RESET (format data). First boot takes almost 10 min so be patient...
Click to expand...
Click to collapse
NOTZIPPY METHOD: ...After flash and reboot my phone did not get past the cm logo, I noticed a lot of errors in logcat , so I reboot into recovery and formatted cache and rebooted again, them ROM booted
Click to expand...
Click to collapse
MR.201 METHOD: ...factory reset then just flash the rc1 rom. gaaps is not needed as miroslav already added light gaaps...
Click to expand...
Click to collapse
_CRASS_ METHOD:
As for installing here is exactly what I did:
1) soft reboot to recovery
2) backuped everything through clockwork recovery
3) cleared cache
4) cleared dalvic
5) factory reset
6) install miroslav rom
7) rebooted...it got stuck on the CM logo
8) After about 10 minutes of no go I pulled battery
9) booted to clockwork recovery
10) factory reset
11) installed miroslav rom
12) installed latest kitkat gapps from CM website
13) rebooted
14) after 3-4 minutes I was in the pin screen of CM
Click to expand...
Click to collapse
LILOWEK METHOD: ...There was no rhyme or reason of why it installed. I simply installed it with gapps. No go. Format, clear all cache, install with gapps. Still the same. Did it again, and this time it went through. It booted in about 3 minutes. I suggest if you are having problems installing it to boot to just do it over and over as it will likely take at some point...
Click to expand...
Click to collapse
_CRASS_ METHOD ON RC2:
Installed it today.
Wiped factory data.
Wiped cache
Wiped dalvic
installed miroslav rom
installed gapps
and it booted right away.
Click to expand...
Click to collapse
REALYPSSD METHOD:
It took 2 tries:
Wiped System
Wiped factory data.
Wiped cache
Wiped dalvic
installed miroslav rom
installed gapps
Doing that didn't work, waited 15-20 minutes, was stuck at the CM logo.
Then I tried without flashing GAPPS, and it worked. I flashed GAPPS after I'd initially booted up once.
Click to expand...
Click to collapse
After I tried all these methods, I only softbricked the phone and had to unbrick it. I have a LG NITRO HD P930 and I use Philz Touch 6.19.3. SWETNES user suggest to use CWM 6.0.1.5 because he says CWM 6.0.4.5 has a lot of bugs, and MIROSLAV says he uses CWM 6.0.4.8 (I can't find it)
Also I want to know if in case I flash it successfuly, the rom MUST boot inmediatly first to LG logo then to CM logo or I have to wait watching the LG logo booting over and over for some minutes??
Any comments, suggestions?
Thank you guys.

I am having the same issue as OP

You did not try my suggestion Try flashing the rom then the gapps with adb sideload after wiping everything.

i use philztouch cwm and have had no problem flashing 4.3/4.4 roms with it. i also rooted my n what not when it was on ICS. i think the option in developer section to update cwm wich gave me the newest 6.0.4.8 i think but have been using philztouch till now.
Ive only wiped everything and flashed rom with no problems so far

Thank you for your comments.
Truepeace said:
You did not try my suggestion Try flashing the rom then the gapps with adb sideload after wiping everything.
Click to expand...
Click to collapse
Yeah, I noticed your method but I am kinda stupid and realy dont get clear the steps. I found this guide to flash via sideload and I wonder if it will work with philz touch:
http://android-revolution-hd.blogspot.mx/2013/12/ow-to-use-adb-sideload.html
xxAirwickxx said:
i use philztouch cwm and have had no problem flashing 4.3/4.4 roms with it. i also rooted my n what not when it was on ICS. i think the option in developer section to update cwm wich gave me the newest 6.0.4.8 i think but have been using philztouch till now.
Ive only wiped everything and flashed rom with no problems so far
Click to expand...
Click to collapse
So you recomend Philz Touch?

chortiman said:
Thank you for your comments.
Yeah, I noticed your method but I am kinda stupid and realy dont get clear the steps. I found this guide to flash via sideload and I wonder if it will work with philz touch:
http://android-revolution-hd.blogspot.mx/2013/12/ow-to-use-adb-sideload.html
So you recomend Philz Touch?
Click to expand...
Click to collapse
Maybe you got the same case as I am. Try to use CWM touch 6.0.1.5 . Then factory reset, format /system , then flash the rom. Loading might take several minute(mine was 10 min) then it will boot up properly. I already use philztouch,cwm 6.0.4.5,latest twrp but all of them not working for me in flashing this rom.
Here, I include the attachment for cwm touch 6.0.1.5 in case you're wondering where you want to find it.put it in the root of your sd card.
Then just run adb . Next, run the following command in the adb cmd :
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
Best of luck, not all guide work for many people and devices

chortiman said:
Thank you for your comments.
Yeah, I noticed your method but I am kinda stupid and realy dont get clear the steps. I found this guide to flash via sideload and I wonder if it will work with philz touch:
http://android-revolution-hd.blogspot.mx/2013/12/ow-to-use-adb-sideload.html
So you recomend Philz Touch?
Click to expand...
Click to collapse
I wonder if this has to do with the way the phones r "unbricked" ? But personally yes I say latest philztouch. Worked great for me. I have latest cwm installed right now 6.0.4.9 & I can't backup so I'll be going back to philztouch.

Another try
I would try hereric's unbricking guide.
Start on step 9, and instead of flashing the provided KDZ use the v10i , download it at lg-phone-firmware.com/index.php?id_mod=17
Good luck

xxAirwickxx said:
I wonder if this has to do with the way the phones r "unbricked" ? But personally yes I say latest philztouch. Worked great for me. I have latest cwm installed right now 6.0.4.9 & I can't backup so I'll be going back to philztouch.
Click to expand...
Click to collapse
Well, I have used the latest philz and it has not worked for me so I will try using CWM 6.0.1.5. And well, it is very complicated to me that stuff about the unbricking because of the "baseband" and other things I dont understand and everybody mentions. I am beginning to believe that it HAS to be flashed over an specific baseband, or am I getting it wrong?
Mr.201 said:
Maybe you got the same case as I am. Try to use CWM touch 6.0.1.5 . Then factory reset, format /system , then flash the rom. Loading might take several minute(mine was 10 min) then it will boot up properly. I already use philztouch,cwm 6.0.4.5,latest twrp but all of them not working for me in flashing this rom.
Here, I include the attachment for cwm touch 6.0.1.5 in case you're wondering where you want to find it.put it in the root of your sd card.
Then just run adb . Next, run the following command in the adb cmd :
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
Best of luck, not all guide work for many people and devices
Click to expand...
Click to collapse
I will try with this CWM 6.0.1.5. Thank you very much for the download So, with this method I can flash the RC3 directly? the 10 minutes you mention are with the LG Logo screen booting up over and over?
danilo96 said:
I would try hereric's unbricking guide.
Start on step 9, and instead of flashing the provided KDZ use the v10i , download it at lg-phone-firmware.com/index.php?id_mod=17
Good luck
Click to expand...
Click to collapse
The link you provide mention a P936 and mine is a P930. If I install this, will the phone work allright? As I was saying to xxAirwickxx, is it necesary to install this previously to flash the miroslav's rom???
Thank to every one for helping me to get a stable rom in my phone. I really apreciate it. :good:

chortiman said:
Well, I have used the latest philz and it has not worked for me so I will try using CWM 6.0.1.5. And well, it is very complicated to me that stuff about the unbricking because of the "baseband" and other things I dont understand and everybody mentions. I am beginning to believe that it HAS to be flashed over an specific baseband, or am I getting it wrong?
I will try with this CWM 6.0.1.5. Thank you very much for the download So, with this method I can flash the RC3 directly? the 10 minutes you mention are with the LG Logo screen booting up over and over?
The link you provide mention a P936 and mine is a P930. If I install this, will the phone work allright? As I was saying to xxAirwickxx, is it necesary to install this previously to flash the miroslav's rom???
Thank to every one for helping me to get a stable rom in my phone. I really apreciate it. :good:
Click to expand...
Click to collapse
It's not necessary, but the KDZ provided is not the most recent build of the GB, the v10i is most recent.
There's no problema flashing it, there is the p930, the p935 and the p936 which are all variants of the same phone, 930 is for america 935 for canada and 936 for europe i believe.
I couldn't install SphinX , always got bootloop or it booted but some system apps like phone didn't start...
Try that and you will probably succed
also , i use PhillZ and i have no problema :laugh:

In order to flash via sideload, I use this guide very easy once you install everything (android sdk and components)
http://forum.xda-developers.com/showthread.php?t=2318497

I tried hard and failed miserably
Well, its been a while since I started this thread. I tried the adb sideload, tried the CWM 6.0.1.5, tried a clean flash (factory reset, format system), waited boot loops for over 30 minutes and nothing. I did not flash KDZ v10i because that process has been always a pain to me. I will get back to CM 10.1.3 + Wind kernel + adreno drivers (the most stable configuration I know) and wait and see if miroslav fix this issue.
Thank you all for your time.

Yeah,I have tried all this methods but no luck......Just got the LG logo bootloop everytime!!(btw,my phone is su640)

I think people have changed there partition sizes in the past that is why the rom is failing to flash - here is mine and I can flash it
adb shell su -c "df"
Filesystem Size Used Free Blksize
/dev 383.8M 128.0K 383.6M 4096
/sys/fs/cgroup 383.8M 12.0K 383.8M 4096
/mnt/asec 383.8M 0.0K 383.8M 4096
/mnt/obb 383.8M 0.0K 383.8M 4096
/mnt/fuse 383.8M 0.0K 383.8M 4096
/system 662.3M 537.7M 124.6M 4096
/cache 157.6M 6.7M 151.0M 4096
/data 2.2G 935.6M 1.2G 4096
/persist 7.9M 4.9M 3.0M 4096
/mpt 15.8M 10.5M 5.3M 1024
/tombstones 71.9M 68.3M 3.7M 4096
/firmware 64.0M 22.8M 41.2M 16384
/modem 199.8M 27.7M 172.0M 4096
/mnt/media_rw/sdcard0 29.7G 16.9G 12.8G 32768
/mnt/secure/asec 29.7G 16.9G 12.8G 32768

Thanks for helping figure that out.
Sent from my LG-P930 using Tapatalk 2

Finally it works!
After having my su640 kdz(30D/4.1.2)，I'm finally succeeded！:victory:

notzippy said:
I think people have changed there partition sizes in the past that is why the rom is failing to flash - here is mine and I can flash it
adb shell su -c "df"
Filesystem Size Used Free Blksize
/dev 383.8M 128.0K 383.6M 4096
/sys/fs/cgroup 383.8M 12.0K 383.8M 4096
/mnt/asec 383.8M 0.0K 383.8M 4096
/mnt/obb 383.8M 0.0K 383.8M 4096
/mnt/fuse 383.8M 0.0K 383.8M 4096
/system 662.3M 537.7M 124.6M 4096
/cache 157.6M 6.7M 151.0M 4096
/data 2.2G 935.6M 1.2G 4096
/persist 7.9M 4.9M 3.0M 4096
/mpt 15.8M 10.5M 5.3M 1024
/tombstones 71.9M 68.3M 3.7M 4096
/firmware 64.0M 22.8M 41.2M 16384
/modem 199.8M 27.7M 172.0M 4096
/mnt/media_rw/sdcard0 29.7G 16.9G 12.8G 32768
/mnt/secure/asec 29.7G 16.9G 12.8G 32768
Click to expand...
Click to collapse
Was able to flash Miro's cm11 Final with this method. Worked first time like a charm.
(My post explaining what I did)
http://forum.xda-developers.com/showthread.php?p=55404877
Sent from my LG-P930 using Tapatalk 2

[help] Gnex brick/softbrick/emmc problem

Hello guys, Im a experienced user with ROMs, recovery, boot and etc but i have a problem now, and i will try to explain shortly:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I have a connection with pc(win8.1)
- The computer can communicate with the phone in fastboot mode and adb(recovery)
- the drivers are installed correctly
- BOOTLOOPIN ON GOOGLE
How this happened:
I was minding my own business and my phone was on my desk when it suddenly rebooted itself and then it bootlooped forever. I had some situations when it rebooted itself but always ended in a successful boot, this time it didnt wanted to start.
What have i done till now:
- First thing i entered recovery(TWRP) and dirtyflashed my current rom version and wiped dalvik/cache. (unsuccessful)
- after several times doing the dirtyflash i finally decided to make a complete hard/factory reset the result was none (after i rebooted to recovery again ALL THE DATA WAS THERE WITHOUT ANY DIFFERENCE, like nothing happened)
- Second thing i tried flashing with Odin3 in Download mode - result was unsuccessful (Operation failed at ~45% and the phone freezed) - I tried this several times with different versions of the software and firmware on 2 different computers (same result)
- Third thing i tried to push img with ADB - no result
- Fourth thing i tried the NexusToolKit and using the UNROOT/GOBACK TO STOCK/SOFTBRICK option - operation was SUCCESSFUL (that's what the cmd console said) BUT, after around 15 mins booting on GOOGLE it started booting my old custom ROM that i had (CarbonROM) with its custom boot animation and i was WTF?! - after several minutes it finally booted the rom. As i tried to unlocked it the touchscreen and processing was very slow and unresponsive, it took around 10-15sec. to unlock the phone and then opening the home menu, and in a short delay the phone restarted itself.
- I tried deleting system,data,userdata,cache and etc with the toolkit but same resault - when i rebooted the information was still there.
- I readed alot on the forums and i found that it maybe caused my my eMMC but long ago i checked with a google store app that my chip is from the safe ones and cant go brickbug.
Some information about the phone:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version - I9250XXLJ1
carrier info - none
serial number - 0149C7ED0D020018
signing - production
lock state- unlocked
if anything needed pls ask

valkata1212 said:
Hello guys, Im a experienced user with ROMs, recovery, boot and etc but i have a problem now, and i will try to explain shortly:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I have a connection with pc(win8.1)
- The computer can communicate with the phone in fastboot mode and adb(recovery)
- the drivers are installed correctly
- BOOTLOOPIN ON GOOGLE
How this happened:
I was minding my own business and my phone was on my desk when it suddenly rebooted itself and then it bootlooped forever. I had some situations when it rebooted itself but always ended in a successful boot, this time it didnt wanted to start.
What have i done till now:
- First thing i entered recovery(TWRP) and dirtyflashed my current rom version and wiped dalvik/cache. (unsuccessful)
- after several times doing the dirtyflash i finally decided to make a complete hard/factory reset the result was none (after i rebooted to recovery again ALL THE DATA WAS THERE WITHOUT ANY DIFFERENCE, like nothing happened)
- Second thing i tried flashing with Odin3 in Download mode - result was unsuccessful (Operation failed at ~45% and the phone freezed) - I tried this several times with different versions of the software and firmware on 2 different computers (same result)
- Third thing i tried to push img with ADB - no result
- Fourth thing i tried the NexusToolKit and using the UNROOT/GOBACK TO STOCK/SOFTBRICK option - operation was SUCCESSFUL (that's what the cmd console said) BUT, after around 15 mins booting on GOOGLE it started booting my old custom ROM that i had (CarbonROM) with its custom boot animation and i was WTF?! - after several minutes it finally booted the rom. As i tried to unlocked it the touchscreen and processing was very slow and unresponsive, it took around 10-15sec. to unlock the phone and then opening the home menu, and in a short delay the phone restarted itself.
- I tried deleting system,data,userdata,cache and etc with the toolkit but same resault - when i rebooted the information was still there.
- I readed alot on the forums and i found that it maybe caused my my eMMC but long ago i checked with a google store app that my chip is from the safe ones and cant go brickbug.
Some information about the phone:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version - I9250XXLJ1
carrier info - none
serial number - 0149C7ED0D020018
signing - production
lock state- unlocked
if anything needed pls ask
Click to expand...
Click to collapse
first question is, what do you mean by download mode and odin? are you not using the google galaxy nexus? for all i know, that device has fastboot but not download mode, which is a proprietary fork of fastboot (i think). am i wrong? how do you boot into download mode?
your emmc might be locked in read-only mode. when the emmc firmware data structures get corrupted beyond the firmware capacity to fix them, the firmware downgrades to read-only mode, in which you can at least recover the stored information (or part of it).
grab a different custom recovery version than the one in your phone and "fastboot flash" it. then get into the recovery. do you get the newly flashed recovery or the old one that was already on your phone?

Lanchon said:
first question is, what do you mean by download mode and odin? are you not using the google galaxy nexus? for all i know, that device has fastboot but not download mode, which is a proprietary fork of fastboot (i think). am i wrong? how do you boot into download mode?
your emmc might be locked in read-only mode. when the emmc firmware data structures get corrupted beyond the firmware capacity to fix them, the firmware downgrades to read-only mode, in which you can at least recover the stored information (or part of it).
grab a different custom recovery version than the one in your phone and "fastboot flash" it. then get into the recovery. do you get the newly flashed recovery or the old one that was already on your phone?
Click to expand...
Click to collapse
Im using the Samsung galaxy nexus and under "download mode odin" i mean VOLUME DOWN + power button. Phone got both odin and fastboot. Fastboot works in bootloader mode ( volume up + volume down + power button).
I already tried with another custom recovery different from the one currently using, yes it flashes the new one - i tried with philz and cw recovery, both booted but again i couldnt wipe everything.

Lanchon said:
first question is, what do you mean by download mode and odin? are you not using the google galaxy nexus? for all i know, that device has fastboot but not download mode, which is a proprietary fork of fastboot (i think). am i wrong? how do you boot into download mode?
your emmc might be locked in read-only mode. when the emmc firmware data structures get corrupted beyond the firmware capacity to fix them, the firmware downgrades to read-only mode, in which you can at least recover the stored information (or part of it).
grab a different custom recovery version than the one in your phone and "fastboot flash" it. then get into the recovery. do you get the newly flashed recovery or the old one that was already on your phone?
Click to expand...
Click to collapse
the galaxy nexus certainly has download mode/Odin.
it is a Samsung device, they all have this.
just like even the HTC nexus device have hboot
to the op, I wish you much luck, I cannot comment much on this, I had similar happen once and I used "fastboot boot recovery.img" and luckily was able to fix my device from there, but I see this happen sometimes to others (few threads on here about it) where they weren't able to get her back up and running I hope that is not the case for you.
---------- Post added at 12:13 AM ---------- Previous post was at 12:08 AM ----------
oh, also, do you have multiple batteries? have you tried another battery? seems simple enough, but I've heard of devices acting awry similar to this when the battery has taken a crap. (sometime the battery will act as if it's charging and holding charge just fine, but it never actually gets itself to fully charged, for example I think fully charged battery should read about 4.12 with a voltmeter, but one that's gone faulty doesn't reach that, is as if it just cannot provide enough juice needed to get things done causing the device to fail while trying to use that battery)

ashclepdia said:
the galaxy nexus certainly has download mode/Odin.
it is a Samsung device, they all have this.
just like even the HTC nexus device have hboot
to the op, I wish you much luck, I cannot comment much on this, I had similar happen once and I used "fastboot boot recovery.img" and luckily was able to fix my device from there, but I see this happen sometimes to others (few threads on here about it) where they weren't able to get her back up and running I hope that is not the case for you.
---------- Post added at 12:13 AM ---------- Previous post was at 12:08 AM ----------
oh, also, do you have multiple batteries? have you tried another battery? seems simple enough, but I've heard of devices acting awry similar to this when the battery has taken a crap. (sometime the battery will act as if it's charging and holding charge just fine, but it never actually gets itself to fully charged, for example I think fully charged battery should read about 4.12 with a voltmeter, but one that's gone faulty doesn't reach that, is as if it just cannot provide enough juice needed to get things done causing the device to fail while trying to use that battery)
Click to expand...
Click to collapse
I have one and only stock battery. TWRP has a battery counter and it seems ok it stays always on 100% when plugged in the usb. I will try to check it with a voltmeter but i doubt that the problem is from the battery.
Waiting Lanchon to asnwer

valkata1212 said:
Im using the Samsung galaxy nexus and under "download mode odin" i mean VOLUME DOWN + power button. Phone got both odin and fastboot. Fastboot works in bootloader mode ( volume up + volume down + power button).
I already tried with another custom recovery different from the one currently using, yes it flashes the new one - i tried with philz and cw recovery, both booted but again i couldnt wipe everything.
Click to expand...
Click to collapse
ok! i had 2 galaxy nexus and never realized they had download mode lol, or at least i dont remember knowing!
so to confirm: you flash any recovery and it sticks and works. you flash it using "fastboot flash recovery x.img". you ARE NOT booting it directly with "fastboot boot x.img". confirm?
this means that your emmc is not fully locked down, and is good news.

Lanchon said:
ok! i had 2 galaxy nexus and never realized they had download mode lol, or at least i dont remember knowing!
so to confirm: you flash any recovery and it sticks and works. you flash it using "fastboot flash recovery x.img". you ARE NOT booting it directly with "fastboot boot x.img". confirm?
this means that your emmc is not fully locked down, and is good news.
Click to expand...
Click to collapse
BAD NEWS: NOPE, i do not confirm, i only did fastboot boot x.img!! Now i tried fastboot flash recovery x.img, restarted bootloader, and entered to recovery and - bang - old recovery is there. It's seems that my phone is a goner right??

valkata1212 said:
BAD NEWS: NOPE, i do not confirm, i only did fastboot boot x.img!! Now i tried fastboot flash recovery x.img, restarted bootloader, and entered to recovery and - bang - old recovery is there. It's seems that my phone is a goner right??
Click to expand...
Click to collapse
ok your emmc is locked in read-only mode. i had a gnex brought to me in that condition and there was absolutely nothing i could do to fix it. writes are ignored by the emmc (but return "ok" to the kernel) and take near zero time. i tried issuing emmc erase commands, etc, and they were all ignored. i tried booting via USB (via an OMAP debugger) and i couldn't accomplish anything. there is a thread here in xda that details what i tried and what i found out. in the end, i had to replace the motherboard of that phone.
but... i know more now
there is one thing you could try: completely reset the emmc. but really, given that you didnt follow a simple fastboot flash instruction and did a fastboot boot instead makes me think that you wont be able to correctly follow the procedure to completion, but we can try.
the trick is to resize the boot partitions, and during that operation the complete emmc will be wiped. this includes the corrupted FTL data structures inside the emmc that i suspect are causing the read-only lock.
so, caveats:
-this has never ever been tried on this device or this emmc. but it was done successfully in some kindles of the same era, which have a different but similar emmc (both are samsung emmcs). take a look here but DO NOT follow that procedure:
http://forum.xda-developers.com/showthread.php?t=2413453
-everything gets wiped! including bootloaders, partition table, partitions, etc.
-the kindle can boot from usb, but the gnex cant. if the gnex is shut down or rebooted after wiping the emmc but before reconstituting the boot chain, THE DEVICE WILL BE BRICKED FOREVER and never boot again.
-if something goes wrong, BRICK.
-the procedure we will improvise and try can be plain wrong, and the device might BRICK.
-the emmc might ignore the boot partition resize command, in which case it wont brick any further, but this whole adventure would be a failure.
-actually i lied. if the device is rebooted without a proper boot chain, there is a boot-over-USB OMAP debugger that can boot it into a monitor. but reconstituting the boot chain from there might be impossible.
read everything twice and make sure you understand everything i write. ASK instead of guessing!
FROM NOW ON: everything you do, you will do it in latest release of TWRP for your device. before doing ANYTHING here, each time you boot your phone you will enter fastboot mode and "fastboot boot" this TWRP image. then you will "adb shell" to it, or "adb push/pull" to/from it.
first i need a map of your emmc. adb shell then run this and paste the output:
ls -l /dev/block/mmc*
ls -l /dev/block/platform/[whatever device name]/by-name
fdisk -l /dev/block/mmcblk0
---------- Post added at 03:25 PM ---------- Previous post was at 03:19 PM ----------
please post outputs in [ CODE ] tags so that its more readable.

Lanchon said:
ok your emmc is locked in read-only mode. i had a gnex brought to me in that condition and there was absolutely nothing i could do to fix it. writes are ignored by the emmc (but return "ok" to the kernel) and take near zero time. i tried issuing emmc erase commands, etc, and they were all ignored. i tried booting via USB (via an OMAP debugger) and i couldn't accomplish anything. there is a thread here in xda that details what i tried and what i found out. in the end, i had to replace the motherboard of that phone.
but... i know more now
there is one thing you could try: completely reset the emmc. but really, given that you didnt follow a simple fastboot flash instruction and did a fastboot boot instead makes me think that you wont be able to correctly follow the procedure to completion, but we can try.
the trick is to resize the boot partitions, and during that operation the complete emmc will be wiped. this includes the corrupted FTL data structures inside the emmc that i suspect are causing the read-only lock.
so, caveats:
-this has never ever been tried on this device or this emmc. but it was done successfully in some kindles of the same era, which have a different but similar emmc (both are samsung emmcs). take a look here but DO NOT follow that procedure:
http://forum.xda-developers.com/showthread.php?t=2413453
-everything gets wiped! including bootloaders, partition table, partitions, etc.
-the kindle can boot from usb, but the gnex cant. if the gnex is shut down or rebooted after wiping the emmc but before reconstituting the boot chain, THE DEVICE WILL BE BRICKED FOREVER and never boot again.
-if something goes wrong, BRICK.
-the procedure we will improvise and try can be plain wrong, and the device might BRICK.
-the emmc might ignore the boot partition resize command, in which case it wont brick any further, but this whole adventure would be a failure.
-actually i lied. if the device is rebooted without a proper boot chain, there is a boot-over-USB OMAP debugger that can boot it into a monitor. but reconstituting the boot chain from there might be impossible.
read everything twice and make sure you understand everything i write. ASK instead of guessing!
FROM NOW ON: everything you do, you will do it in latest release of TWRP for your device. before doing ANYTHING here, each time you boot your phone you will enter fastboot mode and "fastboot boot" this TWRP image. then you will "adb shell" to it, or "adb push/pull" to/from it.
first i need a map of your emmc. adb shell then run this and paste the output:
ls -l /dev/block/mmc*
ls -l /dev/block/platform/[whatever device name]/by-name
fdisk -l /dev/block/mmcblk0
---------- Post added at 03:25 PM ---------- Previous post was at 03:19 PM ----------
please post outputs in [ CODE ] tags so that its more readable.
Click to expand...
Click to collapse
Im doing the adb shell commands now but I have 1 question: How to find my DEVICE NAME?? im not sure what to type from all the data i get, i will wait until you respond to proceed.
EDIT: This is what i get for now:
Code:
~ # ←[6nls -l /dev/block/mmc*
ls -l /dev/block/mmc*
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
brw------- root root 179, 0 2015-02-05 15:26 mmcblk0
brw------- root root 179, 8 2015-02-05 15:26 mmcblk0boot0
brw------- root root 179, 16 2015-02-05 15:26 mmcblk0boot1
brw------- root root 179, 1 2015-02-05 15:26 mmcblk0p1
brw------- root root 259, 2 2015-02-05 15:26 mmcblk0p10
brw------- root root 259, 3 2015-02-05 15:26 mmcblk0p11
brw------- root root 259, 4 2015-02-05 15:26 mmcblk0p12
brw------- root root 259, 5 2015-02-05 15:26 mmcblk0p13
brw------- root root 179, 2 2015-02-05 15:26 mmcblk0p2
brw------- root root 179, 3 2015-02-05 15:26 mmcblk0p3
brw-rw---- radio radio 179, 4 2015-02-05 15:26 mmcblk0p4
brw------- root root 179, 5 2015-02-05 15:26 mmcblk0p5
brw------- root root 179, 6 2015-02-05 15:26 mmcblk0p6
brw------- root root 179, 7 2015-02-05 15:26 mmcblk0p7
brw------- root root 259, 0 2015-02-05 15:26 mmcblk0p8
brw-rw---- radio radio 259, 1 2015-02-05 15:26 mmcblk0p9
~ # ←[6n
Code:
~ # ←[6nls -l /dev/block/platform/
ls -l /dev/block/platform/
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x root root 2015-02-05 15:26 omap
~ # ←[6n
Code:
~ # ←[6nls -l /dev/block/platform/omap
ls -l /dev/block/platform/omap
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x root root 2015-02-05 15:26 omap2_mcspi.3
drwxr-xr-x root root 2015-02-05 15:26 omap_hsmmc.0
~ # ←[6n
Code:
~ # ←[6nfdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
~ # ←[6n
Tell me if you need something

valkata1212 said:
How to find my DEVICE NAME??
Click to expand...
Click to collapse
you should try all options!
but i think it is probably omap/omap_hsmmc.0
are you sure you are "fastboot boot" booting into the latest TWRP recovery before doing adb shell??? your fdisk command doesn't support GPT disks, that is very strange.
also do:
cat /proc/partitions
cat /proc/mounts
also from the pc (are you using linux or windows?):
create a PC folder and cd into it, then:
adb pull -p /dev/block/mmcblk0boot0
adb pull -p /dev/block/mmcblk0boot1
tell me the exact size of the two downloaded files. KEEP THESE FILES SAFE!

Lanchon said:
you should try all options!
but i think it is probably omap/omap_hsmmc.0
are you sure you are "fastboot boot" booting into the latest TWRP recovery before doing adb shell??? your fdisk command doesn't support GPT disks, that is very strange.
also do:
cat /proc/partitions
cat /proc/mounts
also from the pc (are you using linux or windows?):
create a PC folder and cd into it, then:
adb pull -p /dev/block/mmcblk0boot0
adb pull -p /dev/block/mmcblk0boot1
tell me the exact size of the two downloaded files. KEEP THESE FILES SAFE!
Click to expand...
Click to collapse
I can 100% confirm Im on the newest TWRP recovery version v2.8.4.0 flashed with fastboot boot x.img
And here are the results i got, and also those new commands:
Code:
~ # ←[6nls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx root root 2015-02-05 18:06 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-02-05 18:06 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-02-05 18:06 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-02-05 18:06 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-02-05 18:06 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-02-05 18:06 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-02-05 18:06 param -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-02-05 18:06 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-02-05 18:06 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-02-05 18:06 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-02-05 18:06 system -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-02-05 18:06 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-02-05 18:06 xloader -> /dev/block/mmcblk0p1
~ # ←[6n
Code:
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
31 0 1024 mtdblock0
179 0 15388672 mmcblk0
179 1 128 mmcblk0p1
179 2 3584 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 12224 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 669696 mmcblk0p10
259 3 442368 mmcblk0p11
259 4 14198767 mmcblk0p12
259 5 64 mmcblk0p13
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
~ # ←[6n
Code:
~ # ←[6ncat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
/dev/block/mmcblk0p11 /cache ext4 rw,seclabel,relatime,user_xattr,barrier=1,data
=ordered 0 0
/dev/block/mmcblk0p12 /data ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=
ordered 0 0
/dev/block/mmcblk0p12 /sdcard ext4 rw,seclabel,relatime,user_xattr,barrier=1,dat
a=ordered 0 0
~ # ←[6n
AND THIS IS WHAT I GET WHEN I TRIED TO PULL THE FILES U ASKED: (both mmcblk0boot0/1)
Code:
E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb pull -p /dev/block/mmcbl
k0boot0
remote object '/dev/block/mmcblk0boot0' not a file or directory

lol please repeat:
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
using a wider terminal so that the output can be read
your partitions are:
Code:
major minor #blocks name
31 0 1024 mtdblock0
179 0 15388672 mmcblk0
179 1 128 mmcblk0p1 xloader
179 2 3584 mmcblk0p2 sbl
179 3 20480 mmcblk0p3 efs
179 4 8192 mmcblk0p4 param
179 5 4096 mmcblk0p5 misc
179 6 4096 mmcblk0p6 dgs
179 7 8192 mmcblk0p7 boot
259 0 12224 mmcblk0p8 recovery
259 1 16384 mmcblk0p9 radio
259 2 669696 mmcblk0p10 system
259 3 442368 mmcblk0p11 cache
259 4 14198767 mmcblk0p12 userdata
259 5 64 mmcblk0p13 metadata
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
---------- Post added at 03:34 PM ---------- Previous post was at 03:28 PM ----------
cat /proc/mtd
cat /proc/emmc
dd if=/dev/block/mmcblk0boot0 of=/tmp/mmcblk0boot0
dd if=/dev/block/mmcblk0boot1 of=/tmp/mmcblk0boot1
from the PC:
adb pull /tmp/mmcblk0boot0
adb pull /tmp/mmcblk0boot1
---------- Post added at 03:36 PM ---------- Previous post was at 03:34 PM ----------
get the latest philz touch recovery for gnex. fastboot boot into it, then try this again:
fdisk -l /dev/block/mmcblk0

Lanchon said:
lol please repeat:
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
using a wider terminal so that the output can be read
your partitions are:
Code:
major minor #blocks name
31 0 1024 mtdblock0
179 0 15388672 mmcblk0
179 1 128 mmcblk0p1 xloader
179 2 3584 mmcblk0p2 sbl
179 3 20480 mmcblk0p3 efs
179 4 8192 mmcblk0p4 param
179 5 4096 mmcblk0p5 misc
179 6 4096 mmcblk0p6 dgs
179 7 8192 mmcblk0p7 boot
259 0 12224 mmcblk0p8 recovery
259 1 16384 mmcblk0p9 radio
259 2 669696 mmcblk0p10 system
259 3 442368 mmcblk0p11 cache
259 4 14198767 mmcblk0p12 userdata
259 5 64 mmcblk0p13 metadata
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
---------- Post added at 03:34 PM ---------- Previous post was at 03:28 PM ----------
cat /proc/mtd
cat /proc/emmc
dd if=/dev/block/mmcblk0boot0 of=/tmp/mmcblk0boot0
dd if=/dev/block/mmcblk0boot1 of=/tmp/mmcblk0boot1
from the PC:
adb pull /tmp/mmcblk0boot0
adb pull /tmp/mmcblk0boot1
---------- Post added at 03:36 PM ---------- Previous post was at 03:34 PM ----------
get the latest philz touch recovery for gnex. fastboot boot into it, then try this again:
fdisk -l /dev/block/mmcblk0
Click to expand...
Click to collapse
Code:
~ # ←[6ncat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00001000 "w25q80"
~ # ←[6n
hmm :?
Code:
~ # ←[6ncat /proc/emmc
cat /proc/emmc
cat: can't open '/proc/emmc': No such file or directory
~ # ←[6n
I downloaded and fastboot booted latest phillz and i did the command again, but the resault is the same:
Code:
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
~ #
So i pulled both mmcblk files, they are 2,048 KB each.

this is going to be redundant, buy do it just in case:
adb pull -p /dev/block/mmcblk0p##
where ## is 1 to 9 and 13 (skip 10, 11, 12)

Lanchon said:
this is going to be redundant, buy do it just in case:
adb pull -p /dev/block/mmcblk0p##
where ## is 1 to 9 and 13 (skip 10, 11, 12)
Click to expand...
Click to collapse
Done. had to do the trick with dd if=/dev/block/mmcblk0p of=/tmp/mmcblk0p first then adb pull /tmp/mmcblk0p, but i got the files now, their size range are from 64 KB to 20,480 KB (largest one)
Whats next:?

EDIT: first reboot into clean latest TWRP
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-beg bs=1M count=96
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
from the PC:
adb pull -p /tmp/mmcblk0-beg
adb pull -p /tmp/mmcblk0-end
beg should be 96MB
end should be 28MB
verify, that on the PC.
DO NOT REBOOT THE PHONE FROM THIS POINT FORWARD!
we want those files in the ramdrive

Lanchon said:
EDIT: first reboot into clean latest TWRP
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-beg bs=1M count=96
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
from the PC:
adb pull -p /tmp/mmcblk0-beg
adb pull -p /tmp/mmcblk0-end
beg should be 96MB
end should be 28MB
verify, that on the PC.
DO NOT REBOOT THE PHONE FROM THIS POINT FORWARD!
we want those files in the ramdrive
Click to expand...
Click to collapse
downloaded beg and i confirm its 98 MB but i have a problem with END, it doesnt want to copy it im tmp, i deleted the "skip=15000 part" and it came out 250 MB!! but couldnt pull it cuz it game me "no space left on device"
What should i do? Reboot and do this again or ?

valkata1212 said:
downloaded beg and i confirm its 98 MB but i have a problem with END, it doesnt want to copy it im tmp, i deleted the "skip=15000 part" and it came out 250 MB!! but couldnt pull it cuz it game me "no space left on device"
What should i do? Reboot and do this again or ?
Click to expand...
Click to collapse
reboot
redo first dd
no need to pull again
redo second dd, and tell me the error message or whatever it outputs. form now on, i recommend you dont try to fix things without posting first, one error can mean BRICK.

Lanchon said:
reboot
redo first dd
no need to pull again
redo second dd, and tell me the error message or whatever it outputs. form now on, i recommend you dont try to fix things without posting first, one error can mean BRICK.
Click to expand...
Click to collapse
Code:
E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb shell
~ # ←[6ndd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
It doesnt start the operation dont know why, just like the first time i did. Beg finished for 2-3 sec but -end just doesnt show up.

valkata1212 said:
Code:
E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb shell
~ # ←[6ndd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
It doesnt start the operation dont know why, just like the first time i did. Beg finished for 2-3 sec but -end just doesnt show up.
Click to expand...
Click to collapse
you are saying:
-no error displayed
-no file created
?
does the phone stop responding?

Fix Persist, resolve IMEI=0, Volte, 4G, Explanation, Requirements

I have created this thread in order to have one thread that details just the solution to fixing your persist, identifying whether or not you have an issue with your persist, and how you can restore your IMEI without hacks. This guide is written for Motorola Moto G5 Plus (Potter). The issue also affects other models, e.g. G5, G5S, G5S Plus, but the guide appears to apply consistently to all of these models. Note that links in this thread are of course for potter.
For information on the history of this issue, refer to the following thread:
[dev][info] imei 0
IMPORTANT: There are a number of poor copy/paste jobs of parts of this guide floating around. Please link to this guide rather than posting only select parts of this (i.e. flashable zips, list of commands with no explanation). One of the lessons we all should have learned from this issue is to not just blindly follow guides because of "Hey this really works you should do it too trust me it works". The explanation and understanding is important, which is why I have taken the time to be as detailed as I have.
This thread is broken down into the following sections:
Asking for help
Pre-requisites
How to tell if you have an issue with your persist, and if it is recoverable
How to fix persist
Explanation
Before starting though, there is one thing to keep in mind - for this to work YOU MUST HAVE YOUR OWN PERSIST. If you flashed someone else's persist, or a persist from another device, the fix will not work. Your only hope is to have a backup of your own persist that you can restore.
0) Asking for help
If you need to ask for help in following this guide (specifically about any problems you have trying to restore your persist and/or IMEI), please provide the following information (preferably copy/paste this into your post):
- Which version of STOCK rom are you on?
- Are you rooted, and running the commands under root privileges?
- Have you ever flashed someone else's, or another device's persist?
- What functionality are you missing and trying to restore (e.g. IMEI=0, VolTE, etc)?
- Do you get any error messages when trying to execute the commands?
Please also include the full output of the commands below. Ideally wrap the output in 'code tags' so it is nicely formatted
Update 2018-09-16
Now that stock Oreo is starting to roll out (ever so slowly...), it is an important point to note that you can now simply upgrade to stock Oreo to overcome the issue described in this guide. Stock Oreo changes the ownership of the relevant folders in persist on every boot.
TWRP flashable Oreo builds are available here [Oreo][Stock][Rom] TWRP Flashable Stock Builds. Do also read the first two posts in detail, as they also cover how to revert to stock Nougat, should you ever wish to move to a custom Oreo rom.
1) Pre-requisites
You must currently be on a Stock Nougat ROM. Either the fastboot or TWRP flashable stock roms. You can get the latest TWRP flashable stock roms from this thread: [New][Stock][Rom] TWRP Flashable Stock Builds
You must be using your own persist.
You must have root access within the stock ROM. All scripts below MUST be run with root permissions
2) How to tell if you have an issue with your persist, and if it is recoverable
From a shell (either adb, or a terminal app on your device), type in the following commands:
Code:
su
ls -l /persist
The su command is to get root, and the 'ls' command lists details about the files in persist, including owners and permissions. On a fully operational persist, you will get a listing like this:
Code:
potter_n:/ # ls -l /persist
total 168
drwxrwx--- 2 system system 4096 2018-08-04 16:44 alarm
drwxr-xr-x 2 mot_pwric mot_pwric 4096 1970-01-01 12:03 batt_health
drwxrwx--- 2 bluetooth bluetooth 4096 2018-08-04 16:44 bluetooth
drwx------ 2 root system 4096 1970-01-01 12:03 bms
drwxr-xr-x 2 mot_tcmd bluetooth 4096 1970-01-01 12:03 bt
drwxr-xr-x 4 mot_tcmd mot_tcmd 4096 2018-08-04 16:44 camera
drwx------ 6 system system 4096 2018-08-04 16:44 data
drwxrwx--- 2 system system 4096 1970-01-01 12:03 drm
drwxr-xr-x 5 mot_tcmd mot_tcmd 4096 2018-08-04 16:44 factory
[COLOR="red"]drwxrwx--- 3 rfs rfs_shared 4096 2018-08-04 16:44 hlos_rfs[/COLOR]
drwxrwx--- 2 root root 4096 2018-08-04 16:44 lost+found
drwxrwx--- 2 radio radio 4096 2018-08-04 16:44 mdm
drwxrwx--- 2 system system 4096 1970-01-01 12:03 misc
drwxrwx--- 2 system system 4096 1970-10-15 07:43 properties
drwxr-xr-x 8 mot_tcmd mot_tcmd 4096 2018-08-04 16:44 public
[COLOR="red"]drwx------ 6 rfs rfs 4096 2018-08-04 16:44 rfs[/COLOR]
drwxrws--- 2 mot_tpapi mot_tpapi 4096 2018-08-04 16:44 security
drwxrwxr-x 2 root root 4096 2018-08-04 16:44 sensors
drwxrwx--- 2 system system 4096 2018-08-04 16:44 time
drwxr-xr-x 2 mot_tcmd mot_tcmd 4096 1970-01-01 12:03 wifi
drwxrwxr-x 2 mot_drm mot_drm 4096 1970-01-01 12:03 wmdrm
The key here, is the rfs folder, and to a lesser degree, the hlos_rfs folder. Notice how the owner is rfs, and in the case of hlos_rfs, the group is rfs_shared.
Important - if you ran these commands from within an Oreo rom, you will see owners such as oem_2903 etc. These owners are valid for Oreo (custom or stock). The point of this guide is so that you know whether or not you have an ownership / permissions issue on Stock Nougat.
Additionally, if you run the following to look for files within persist:
Code:
find /persist -type f
You will see something like this:
Code:
potter_n:/ # find /persist -type f
/persist/sensors/sensors_settings
/persist/data/prov/eyBMMa7Jo5Dwo4LigJCHx3WxPUdQ9y8GJKIBae9bic
/persist/data/prov/prov
/persist/data/prov/prov.bak
/persist/data/prov/eyBMMa7Jo5Dwo4LigJCHx3WxPUdQ9y8GJKIBae9bic.bak
/persist/data/prov/T2pluw0BDr+EpzrrpM4aIMo1xKHY-DMHg3Uk3GF5yq
/persist/data/prov/T2pluw0BDr+EpzrrpM4aIMo1xKHY-DMHg3Uk3GF5yq.bak
/persist/data/widevine/Saljqyb2k7jJt0wZSxpXq0sdCZJH4urJjb-qcgkn7H
/persist/data/widevine/Saljqyb2k7jJt0wZSxpXq0sdCZJH4urJjb-qcgkn7H.bak
/persist/data/widevine/+CdCfjxBGljLnuTN7yCnhuY3WzhxbvHOjc-rac35xw
/persist/data/widevine/+CdCfjxBGljLnuTN7yCnhuY3WzhxbvHOjc-rac35xw.bak
/persist/camera/ledcal/rear
/persist/mdm/oma_dm_update
/persist/factory/regulatory/regulatory_info.png
/persist/factory/fti
/persist/public/hiddenmenu/data/mobile_data_rx
/persist/public/hiddenmenu/data/mobile_data_tx
/persist/public/hiddenmenu/data/wifi_data_rx
/persist/public/hiddenmenu/data/wifi_data_tx
/persist/security/18.bin
/persist/bluetooth/.bt_nv.bin
/persist/alarm/powerOffAlarmSet
/persist/alarm/timezone
/persist/alarm/powerOffAlarmInstance
/persist/time/ats_1
/persist/time/ats_2
/persist/time/ats_15
/persist/time/ats_12
/persist/time/ats_13
/persist/rfs/shared/server_info.txt
/persist/rfs/msm/mpss/datablock/id_00
/persist/rfs/msm/mpss/datablock/id_01
/persist/rfs/msm/mpss/server_check.txt
[COLOR="red"]/persist/rfs/msm/mpss/dhob.bin
/persist/rfs/msm/mpss/shob.bin
/persist/rfs/msm/mpss/dhob.bin.bak
[/COLOR]
The key files here are those in the /persist/rfs folder, mainly the dhob.bin file, which is used in creation of the EFS (i.e. the modemst1 and modemst2 partitions).
If you do not have the files under the /persist/rfs folder, then you will not be able to restore your persist through this method. Also see post #3 for information on when you have a dhob.bin but no dhob.bin.bak.
Now, if you run the ls command on a 'bad persist', you will get the following output from the ls command:
Code:
potter_n:/ # ls -l /persist
total 208
drwxrwx--- 2 system system 4096 2018-08-05 11:48 alarm
drwxr-xr-x 2 mot_pwric mot_pwric 4096 1970-01-01 12:03 batt_health
drwxrwx--- 2 bluetooth bluetooth 4096 2018-08-05 11:48 bluetooth
drwx------ 2 root system 4096 1970-01-01 12:03 bms
drwxr-xr-x 2 mot_tcmd bluetooth 4096 1970-01-01 12:03 bt
drwxr-xr-x 4 mot_tcmd mot_tcmd 4096 2018-08-05 11:48 camera
drwxrwx--- 2 system system 4096 2018-08-05 11:48 chargeonly
drwx------ 6 system system 4096 2018-08-05 11:48 data
drwxrwx--- 2 system graphics 4096 1971-01-22 16:48 display
drwxrwx--- 2 system system 4096 1970-01-01 12:03 drm
drwxr-xr-x 5 mot_tcmd mot_tcmd 4096 2018-08-05 11:48 factory
[COLOR="Red"]drwxrwx--- 3 2951 2952 4096 2018-08-05 11:48 hlos_rfs[/COLOR]
drwxrwx--- 2 root root 4096 2018-08-05 11:48 lost+found
drwxrwx--- 2 radio radio 4096 2018-08-05 11:48 mdm
drwxrwx--- 2 system system 4096 1970-01-01 12:03 misc
drwxrwx--- 2 system system 4096 1970-10-15 07:43 properties
drwxr-xr-x 11 mot_tcmd mot_tcmd 4096 2018-08-05 11:48 public
[COLOR="Red"]drwx--x--x 6 2951 2951 4096 2018-08-05 11:48 rfs[/COLOR]
drwx------ 2 root root 4096 1971-01-22 16:48 sds
drwxrwx--- 2 system system 4096 1971-01-22 16:48 secnvm
drwxrws--- 2 mot_tpapi mot_tpapi 4096 2018-08-05 11:48 security
drwxrwxr-x 2 root root 4096 2018-08-05 11:48 sensors
drwxrwx--- 2 system system 4096 2018-08-05 11:48 time
drwxrwx--- 2 media media 4096 1971-01-22 16:48 vpp
drwxr-xr-x 2 mot_tcmd mot_tcmd 4096 1970-01-01 12:03 wifi
drwxrwxr-x 2 mot_drm mot_drm 4096 1970-01-01 12:03 wmdrm
The lines above in red, show that the ownership of the rfs and hlos_rfs folders are numbers, i.e. they are unknown to the system. To resolve, we need to change the ownership.
3) How to fix your persist
To fix the ownership, use the following commands (use su if not in a root shell):
Code:
chown -R rfs:rfs /persist/rfs
chown -R rfs:rfs_shared /persist/hlos_rfs
ls -l /persist
Now when the ls command shows the ownership of the folders, you should see the correct ownership.
Fixing your IMEI if it was zero
If your IMEI was zero, reboot, and cross your fingers that you will have your IMEI back (Settings > About Phone > Status > IMEI information).
NEW - TWRP flashable Stock Persist Fix
I've created a TWRP flashable zip that does the above ownership fixes. The script has slight differences, it uses the AIDs (Android IDs) of rfs and rfs_shared in stock.
potter-stock-persist-fix.zip
4) Explanation
4a) What happened to persist.
To understand what happened, you need to know a few things about filesystem permissions in Linux. Files and folders have user and group ownership, and permissions. Examples of owners are the system, root, user, etc. Examples of permissions are read access, write access, execute access. The permissions are applied at three levels 1) the user, 2) the group, 3) everyone else.
@rachitrawat's investigation into the failures showed that the issue was relating to the persist partition, specifically some files dhob.bin etc that are under the rfs sub folder in this partition. Under stock, these files/folders are owned by a user called rfs, and have group ownership under a group also called rfs. Additionally, the permissions on these files/folders are limited - only the rfs user can read/write/execute these files. Other users, groups, or everyone else, cannot access the files.
Edit: This part here wasn't quite correct, it is fixed below. It kind of still applies, but only if looking from within TWRP (I wrongly assumed that TWRP had the same user names as Lineage, my bad!):
So something happened in the Oreo roms. If you flash and boot into an Oreo rom, and you look at the permissions/ownership, you will see exactly the same ownership patterns as stock. But there's a catch!
There was a change in the Oreo roms. If you flash and boot into an Oreo rom, and you look at the permissions/ownership, you will see that a user and group oem_2951 owns the rfs folder, and a group oem_2952 owns the hlos_rfs folder. Now this is a different name, but on its own, a different name does not mean different ownership.
In Linux, all users and groups are assigned an ID, i.e. a number. So for example, on my phone, the rfs user has ID 3012 under stock. In lineage oreo, the oem_2951 user has ID 2951. So something happened in lineage that changed the user IDs that are applied to the rfs folder.
If you look at the ownership of persist files/folders within TWRP, you will see that a STOCK PERSIST has the owner of the rfs folder as rfs_old. Similarly in TWRP, a LINEAGE PERSIST has the owner of the rfs folder as rfs. So TWRP is seeing owners differently again to stock and Lineage. Trying to run the above commands in TWRP will not fix the issue, as it will use ID 2951 for the user rfs, but we need it to be 3012 in stock (which TWRP sees as rfs_old).
In addition to the rfs folder, there is also another folder that is impacted - hlos_rfs. Its user owner is rfs, but its group owner if rfs_shared. A stock rfs_shared is shown as rfs_shared_o in TWRP. It appears that this folder is not as important in getting the IMEI back, but I have included the commands to restore ownership, to ensure there are no future errors.
4b) What happened to IMEI.
Despite the issue above, many people who flashed Oreo roms would have had no problems (other than I guess, bugs in the roms themselves). The change of ownership of the rfs folder didn't change the actual file content, so essentially all is intact. In fact, I verified that my dhob.bin and other files had the same md5sum in stock and lineage persist.
The issue of the IMEI changing to zero has only happened when people have flashed Stock roms. All of the guides that I have seen, have included the following commands (and equivalent commands have been included in the TWRP flashable stock builds as well):
Code:
fastboot erase modemst1
fastboot erase modemst2
The partitions modemst1 and modemst2 are your EFS. Normally, if your persist is pure stock, if either is erased, the modem re-creates them. But, referring to the above about permissions, if the rfs user (which is presumably used by the modem) cannot access the files (because the owner of the files is someone else, and the permissions on the files mean that only the owner can access them), then the modem cannot recreate the EFS, and the IMEI is left as zero.
4c) Restoring IMEI.
Changing the ownership of your otherwise untouched persist allows the rfs user to access those files. Rebooting will result in the modem checking the EFS, and when it sees that it is still blank, it will recreate the IMEI.
However, the dhob.bin file in persist is encrypted, and goes through some sort of hash check. You can only use your own dhob.bin to recreate the IMEI. This is why it is essential that you have your own persist, and no one else's will work.
5) Other info
Other things that may be good to know about this issue.
5a) Why did flashing another device's persist fix Volte?
Or rather, why did flashing another device's persist "fix Volte" at the expense of permanently breaking key functionality of your device?
Flashing another device's persist gave the impression of working, but most probably this was due to one thing alone - the permissions on the persist partition of Moto devices is similar. That is, other Moto devices have rfs and hlos_rfs folders, and the owner is the same (both in name and AID - Android ID).
So, after flashing a custom Oreo rom, then going back to stock, Volte would not work. However, if they hadn't erased modemst1/2 (EFS) they would still have IMEI, but other functionality would be broken (Volte, 4G, possibly others). Flashing the other persist changed the permissions to the right ones, and boom all of a sudden Volte worked. The regret comes after, when the user has erased EFS through an update or other flash.
XDA:DevDB Information
The Persist Project, Tool/Utility for the Moto G5 Plus
Contributors
NZedPred, rachitrawat
Version Information
Status: Stable
Created 2018-08-05
Last Updated 2018-09-15

Backing up your persist
One thing that cannot be emphasized enough is that you must keep backups of your persist. (Your efs is even more important to backup if you no longer have your own persist.) Once backed up, make a copy on your PC or laptop, and keep a private cloud copy somewhere as well.
Recent versions of TWRP have made it easy to back up your persist partition. Older versions may not have had native functionality to back it up, however there was also an alternative. Relevant details below.
TWRP backup of persist (recommended)
The official TWRP thread is below. You should consult this thread to check for the latest versions.
[RECOVERY][OFFICIAL][potter] TWRP 3.2.2-0 touch recovery
At the time of writing (2018-08-05), there was a special build made that fixed backing up with encryption. This is the one that I have used in my testing. Link below:
https://forum.xda-developers.com/showpost.php?p=77207112&postcount=199
You will see persist as an available option in Backup and Restore. The backup file will be called persist.ext4.win. It is in fact a tar archive, so you can extract it with tar if you want to examine the contents on your PC.
Image backup of persist
If you don't have TWRP handy, or an older version of it, you can instead use the dd command from a root shell (either within stock or within TWRP)
The following can be used to create a backup and place it at /sdcard/persist.img:
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
The following can be used to restore a backup placed at /sdcard/persist.img:
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
dd backups are bit-perfect, and can also be mounted if you need to look at a filesystem from e.g. your PC.

From post #77 - dhob.bin but no dhob.bin.bak
I'm repeating some findings from another post of mine further down the thread at post #77. It seems to be a common occurrence that unfortunately hasn't been solved.
OK, have done some more investigation into cases where there is a dhob.bin, but no dhob.bin.bak. This will be a long-ish post
So, a normal dhob.bin file looks like this in a hex editor / hex dump (limited to first 20 lines)
Code:
/persist/rfs/msm/mpss # hexdump dhob.bin | head -n20
0000000 7d60 fb6a 1c50 f9f9 54b0 04e1 76f3 7943
0000010 ae7b cb9b 7634 69e4 e6cc ac41 e54e 4444
0000020 860e 82c8 56d1 0cc0 0430 a6af 2652 7739
0000030 4936 1666 ee73 1e9e ef7f 2450 cc8b a999
0000040 56a0 d3ce 3e55 3852 bd23 fe5f 9c89 bdb9
0000050 b345 51e7 c056 43e6 6eba 9e3e 26cd fb9c
0000060 ea05 4edb 3dea 6cd5 a6ed 4b2f 1b16 8232
0000070 9203 d088 7477 5497 5ad6 cfa1 f176 98da
0000080 6d50 226e 8580 3ba3 c034 2176 b73d ec66
0000090 034c 97c7 a670 230a 04f0 318e c08e 930d
00000a0 7d51 3dc0 dd5c 2eb5 4fd2 b70a f929 83e3
00000b0 99fc 06dd a69d d5b5 4aca 8b35 f5bb c9cc
00000c0 3dcb ae6f 8d2d 5b00 55e8 bff3 7824 4ff5
00000d0 0399 cddd b337 709f 1b1c c828 972f 1cd7
00000e0 2420 c7fe 9981 1c42 5f8f a980 86c8 e416
00000f0 dccc 9847 cd26 a2b9 f6cc ecc5 7099 b466
0000100 d606 2fb4 dd08 048e d178 8d29 68c3 ed7e
0000110 2096 5751 39bd 6559 5e7d f43d 2184 e7e5
0000120 f6be ed1c 9722 92a9 a38a 4e7f d053 52a3
0000130 24d0 8347 62af 0f02 5e26 c3a9 b09a 1a26
A normal dhob.bin.bak looks like this (again, first 20 lines):
Code:
/persist/rfs/msm/mpss # hexdump dhob.bin.bak | head -n20
0000000 c0de 0002 3fb0 000c 1545 0006 d00d beef
0000010 0000 beef 0000 0000 0000 0000 0000 0000
0000020 0000 0000 0000 beef 0000 0000 0000 beef
0000030 0000 0000 0000 0000 0000 0000 0000 0000
0000040 0000 beef 0000 0000 0000 0000 0000 0000
0000050 0000 0000 0000 beef 3001 3030 3030 0030
0000060 beef 3001 3030 3030 0030 beef 0000 beef
0000070 0801 153a 0958 8248 0353 beef 0801 153a
0000080 0958 8248 0453 beef 5301 4283 5908 3518
0000090 0000 beef 5701 0000 beef 0000 beef 0000
00000a0 0000 0000 0000 0000 0000 0000 0000 0000
*
0000480 0000 0000 0000 0000 beef 0000 beef 0000
0000490 0000 0000 0000 0000 0000 0000 0000 0000
*
0000640 0000 0000 0000 0000 beef 0000 0000 0000
0000650 0000 0000 0000 0000 0000 0000 beef 0000
0000660 0000 0000 0000 0000 beef 0000 0000 0000
0000670 beef 0000 0000 0000 beef 0000 0000 0000
*
Reading the hexdump:
The left-most column is the address, so 0000000 is the top of the file, and it goes up in increments of 16 (10 hex).
The asterisks * in the latter just represent that the previous row was repeated up until it reached the row underneath. So row 00000a0 (which was all zeroes) was repeated right up until row 0000480 (which differed).
So, the summary of the two is this. 1) A dhob.bin looks like random stuff. 2) A dhob.bin.bak looks like slightly random stuff with a lot of zeroes. They are very distinct, and unlike what the bak extension may suggest, it is NOT a backup of dhob.bin.
So, as I mentioned a few posts previous, a couple of people have a dhob.bin, but no dhob.bin.bak. And interestingly, their dhob.bin does not look like a dhob.bin, it looks more like a dhob.bin.bak. I did a few experiments...
Experiment 1) - Change something in the dhob.bin and dhob.bin.bak
I changed a single byte in my dhob.bin and dhob.bin.bak (to ensure they were invalidated), erased EFS, and rebooted. In this case, the IMEI was of course not restored, and on checking the /persist/rfs/msm/mpss folder, the dhob.bin and dhob.bin.bak were both there.
Experiment 2) - Restore normal files, but delete dhob.bin
I restored my files, and removed the dhob.bin file, leaving the dhob.bin.bak and shob.bin. After rebooting, the dhob.bin file was restored, and so was my IMEI.
Experiment 3) - Delete dhob.bin, edit dhob.bin.bak
No dhob.bin, but a corrupt dhob.bin.bak. After reboot, there was a dhob.bin file, and no dhob.bin.bak. And, it seems, that the dhob.bin.bak file was simply renamed to dhob.bin.
So it appears that, for the dhob.bin.bak to become the dhob.bin file, someone/something has to remove the dhob.bin file. Keeping in mind that the dhob.bin.bak file appears to be used to recreate dhob.bin (probably with the help of shob.bin, I haven't experimented that much yet), and we know that the dhob.bin is encrypted in some way so that only the device it was made for can use it, it would appear that there has been some sort of manual intervention in the phones.
I suspect that is either 1) someone has restored another similar device's persist partition and manually or a custom rom has removed the dhob.bin file in an effort to get it recreated, or 2) well, I don't think there's a 2... (or rather, I can't think of it).
So at this point, if you only have a dhob.bin, and no dhob.bin.bak, and the guide doesn't work, something has been messed with, and at this point I have no solution.
Sorry for those that I'm working with at the moment, but I'm out of ideas.
Edit: Just to mention the obvious, for the couple of people that I have tried fixing by renaming dhob.bin to dhob.bin.bak, it didn't work. The dhob.bin.bak was simply renamed to dhob.bin again, indicating that the persist is probably not the one for the device, however that may have happened...
Click to expand...
Click to collapse

@NZedPred : As I said before, really nice catch.
One question: I made a img backup of persist using the dd commands. As you recommend the way saving it through TWRP, for me it's not clear if it's possible to backup persist with the 3.2.2.0 official TWRP or the special build is needed. I'm on the official one and would like to use it if there's no need to flash the other one. As there's no special " persist" backup option in it is it included somewhere else in the nandroid backup?

Well that's me screwed, I lost my persist before anyone knew wtf was going on.
Edit: If I fastboot stock while also using all the erase commands, will that leave me with original persist?. I am assuming so since after doing this in the past, I am left with 0 imei and 0 imei sv. If I use one of the shared persists, my imei sv changes to 8. If this is the case am I right to then assume this guide can work for anyone, even if they have no backup of original persist, since they can back up there own borked persist in twrp after a full fastboot job?.
Edit2: I think I am confusing persist with efs and how it rebuilds on erase. Is there a way to erase persist and let it rebuild much like efs folder would upon erase?

I got that error chown: bad user 'rfs' My phone is not g5 plus it's g5 and i was trying to fix it
here is the cmd window
Code:
1|cedric:/ # ls -l /persist
total 112
drwxrwx--- 2 system system 4096 1970-01-01 02:21 alarm
drwxr-xr-x 2 mot_pwric mot_pwric 4096 2018-08-05 08:29 batt_health
drwxrwx--- 2 bluetooth bluetooth 4096 1970-01-01 02:21 bluetooth
drwx------ 2 root system 4096 1970-01-01 02:21 bms
drwxr-xr-x 2 mot_tcmd bluetooth 4096 1970-01-01 02:02 bt
drwxr-xr-x 5 mot_tcmd mot_tcmd 4096 1970-01-02 01:43 camera
drwxrwx--- 2 system system 4096 1970-01-02 01:43 chargeonly
drwxr-xr-x 2 root root 4096 2017-11-22 11:25 coresight
drwx------ 4 system system 4096 2017-11-22 11:25 data
drwxrwx--- 2 system graphics 4096 1970-01-01 02:02 display
drwxrwx--- 2 system system 4096 1970-01-01 02:02 drm
drwxr-xr-x 5 mot_tcmd mot_tcmd 4096 1970-01-01 02:21 factory
drwxrwx--- 3 oem_2903 oem_2904 4096 2017-11-22 11:25 hlos_rfs
drwxrwx--- 2 root root 4096 2017-11-22 11:25 lost+found
drwxrwx--- 2 radio radio 4096 2017-11-22 11:25 mdm
drwxrwx--- 2 system system 4096 1970-01-01 02:21 misc
drwxrws--- 2 mot_tcmd mot_tcmd 4096 1970-01-02 01:43 paks
drwxrwx--- 2 system system 4096 1970-07-07 12:32 properties
drwxr-xr-x 11 mot_tcmd mot_tcmd 4096 1970-01-02 01:43 public
drwx--x--x 6 oem_2903 oem_2903 4096 2017-11-22 11:25 rfs
drwx------ 2 root root 4096 1970-01-02 01:43 sds
drwxrwx--- 2 system system 4096 1970-01-02 01:43 secnvm
drwxrws--- 2 drmrpc drmrpc 4096 1970-01-01 02:02 security
drwxrwxr-x 3 system system 4096 1970-01-02 01:43 sensors
drwxrwx--- 2 system system 4096 2018-08-05 08:30 time
drwxrwx--- 2 media media 4096 1970-01-02 01:43 vpp
drwxr-xr-x 2 mot_tcmd mot_tcmd 4096 1970-01-01 02:02 wifi
drwxrwxr-x 2 mot_drm mot_drm 4096 1970-01-01 02:02 wmdrm

Wolfcity said:
@NZedPred : As I said before, really nice catch.
One question: I made a img backup of persist using the dd commands. As you recommend the way saving it through TWRP, for me it's not clear if it's possible to backup persist with the 3.2.2.0 official TWRP or the special build is needed. I'm on the official one and would like to use it if there's no need to flash the other one. As there's no special " persist" backup option in it is it included somewhere else in the nandroid backup?
Click to expand...
Click to collapse
Hey, it may be that that special build is required. Perhaps my comment about 'recent versions of TWRP' wasn't quite correct, and only 'unofficial' versions have the persist option. The partition is not backed up anywhere else if it is not selected (or selectable).
Cupcake 1.5 said:
Well that's me screwed, I lost my persist before anyone knew wtf was going on.
Edit: If I fastboot stock while also using all the erase commands, will that leave me with original persist?. I am assuming so since after doing this in the past, I am left with 0 imei and 0 imei sv. If I use one of the shared persists, my imei sv changes to 8. If this is the case am I right to then assume this guide can work for anyone, even if they have no backup of original persist, since they can back up there own borked persist in twrp after a full fastboot job?.
Edit2: I think I am confusing persist with efs and how it rebuilds on erase. Is there a way to erase persist and let it rebuild much like efs folder would upon erase?
Click to expand...
Click to collapse
Yes, efs and persist are two completely different things. However, DO NOT ERASE PERSIST EVER!!! It is unique to your device, and without it you will lose functionality. If you have erased efs and it recreates on boot then chances are your persist is fine, and you should back it up.
My advise would be that, as long as your persist is your own, back it up and keep it safe.

AhmedtSadek said:
I got that error chown: bad user 'rfs' My phone is not g5 plus it's g5 and i was trying to fix it
here is the cmd window
Code:
1|cedric:/ # ls -l /persist
total 112
drwxrwx--- 2 system system 4096 1970-01-01 02:21 alarm
drwxr-xr-x 2 mot_pwric mot_pwric 4096 2018-08-05 08:29 batt_health
drwxrwx--- 2 bluetooth bluetooth 4096 1970-01-01 02:21 bluetooth
drwx------ 2 root system 4096 1970-01-01 02:21 bms
drwxr-xr-x 2 mot_tcmd bluetooth 4096 1970-01-01 02:02 bt
drwxr-xr-x 5 mot_tcmd mot_tcmd 4096 1970-01-02 01:43 camera
drwxrwx--- 2 system system 4096 1970-01-02 01:43 chargeonly
drwxr-xr-x 2 root root 4096 2017-11-22 11:25 coresight
drwx------ 4 system system 4096 2017-11-22 11:25 data
drwxrwx--- 2 system graphics 4096 1970-01-01 02:02 display
drwxrwx--- 2 system system 4096 1970-01-01 02:02 drm
drwxr-xr-x 5 mot_tcmd mot_tcmd 4096 1970-01-01 02:21 factory
drwxrwx--- 3 oem_2903 oem_2904 4096 2017-11-22 11:25 hlos_rfs
drwxrwx--- 2 root root 4096 2017-11-22 11:25 lost+found
drwxrwx--- 2 radio radio 4096 2017-11-22 11:25 mdm
drwxrwx--- 2 system system 4096 1970-01-01 02:21 misc
drwxrws--- 2 mot_tcmd mot_tcmd 4096 1970-01-02 01:43 paks
drwxrwx--- 2 system system 4096 1970-07-07 12:32 properties
drwxr-xr-x 11 mot_tcmd mot_tcmd 4096 1970-01-02 01:43 public
drwx--x--x 6 oem_2903 oem_2903 4096 2017-11-22 11:25 rfs
drwx------ 2 root root 4096 1970-01-02 01:43 sds
drwxrwx--- 2 system system 4096 1970-01-02 01:43 secnvm
drwxrws--- 2 drmrpc drmrpc 4096 1970-01-01 02:02 security
drwxrwxr-x 3 system system 4096 1970-01-02 01:43 sensors
drwxrwx--- 2 system system 4096 2018-08-05 08:30 time
drwxrwx--- 2 media media 4096 1970-01-02 01:43 vpp
drwxr-xr-x 2 mot_tcmd mot_tcmd 4096 1970-01-01 02:02 wifi
drwxrwxr-x 2 mot_drm mot_drm 4096 1970-01-01 02:02 wmdrm
Click to expand...
Click to collapse
Hi there, I see you're responding to my comment in the cedric forum. It appears that your are also impacted, with the folders being owned by oem_2903 and oem_2904. However, I need to get the details of the correct owner from a fully working cedric device, to know who to change the owner to. Please keep replies in the thread I posted in the cedric forum. I'll keep monitoring that thread as well.

NZedPred said:
Yes, efs and persist are two completely different things. However, DO NOT ERASE PERSIST EVER!!! It is unique to your device, and without it you will lose functionality. If you have erased efs and it recreates on boot then chances are your persist is fine, and you should back it up.
My advise would be that, as long as your persist is your own, back it up and keep it safe.
Click to expand...
Click to collapse
As I said, my device was borked before anyone knew what was happening. At that time we was using other uploaded efs and persist files. My persist is not my own, probably well and truly screwed lol.

NZedPred said:
Hey, it may be that that special build is required. Perhaps my comment about 'recent versions of TWRP' wasn't quite correct, and only 'unofficial' versions have the persist option. The partition is not backed up anywhere else if it is selected (or selectable).
Click to expand...
Click to collapse
Also I should also clarify that I recommend TWRP only because you get a nice gui, and for novices entering dd commands with root privileges carries a high level of risk.

NZedPred said:
Also I should also clarify that I recommend TWRP only because you get a nice gui, and for novices entering dd commands with root privileges carries a high level of risk.
Click to expand...
Click to collapse
Ok, understand that. One more question, you changed the dd commands from the first time you posted them in the old thread.
The old ones were
Code:
dd if=/dev/block/mmcblk0p30 of=/sdcard/persist.img
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p30
Now they look like this:
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
Is the change significant so that there's a need to make a new backup?
Sent from my Moto G5 Plus using XDA Labs

Hi bro
Maximum people's are not have persist and efs backup
You have any solutions please tell me
Me also same problem
I tried your commands
It's just rebooting
Nothing happens
And i flashed xda forums persist
Its showing dhob.bin file
But it's not creating imei's
I tried on stock (old 33 ver and 92-10 ver) and pixel experience also
Nothing worked..
Please help me
Sorry for my bad english....

Wolfcity said:
Ok, understand that. One more question, you changed the dd commands from the first time you posted them in the old thread.
The old ones were
Code:
dd if=/dev/block/mmcblk0p30 of=/sdcard/persist.img
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p30
Now they look like this:
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
Is the change significant so that there's a need to make a new backup?
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Hmm, I don't think so. If I understand it correctly - the first set of commands point to the partition directly (i.e. the first line is find partition mmcblk0p30, dd copy to an image, name image 'persist.img'. 2nd line is the reverse). The second set should be the same - just this time you're asking the device to look up a partition of the name 'persist' from the partition list, then copy and output that as the image.
I imagine the second set of commands are more useful generally, e.g. if you don't have a partition list handy or if you want to use it on another device with a persist partition. They should in practice give you the same partition on the G5 Plus. Still, as NZedPred has noted above, requesting the partition by name may be safer for those users unused to dd, since fat fingering the partition name may have some protection. If you fat finger the first set of commands (e.g. you overwrite partition 39 instead of 30), that's not good...
One thing I was thinking about was is it possible to make a permissions fix script for stock ROMs or perhaps patch the custom ROMs so that they don't change the permissions? Or is that permissions change a result of updating to Oreo (as in that you need that change for an Oreo ROM to work)?

Wolfcity said:
Ok, understand that. One more question, you changed the dd commands from the first time you posted them in the old thread.
The old ones were
Code:
dd if=/dev/block/mmcblk0p30 of=/sdcard/persist.img
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p30
Now they look like this:
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
Is the change significant so that there's a need to make a new backup?
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Hi - no there's no difference. The new commands differ only in that they are referring to the 'named partition', rather than a partition block number. The named partition is a symbolic link that points to the same place:
Code:
potter_n:/ $ su
potter_n:/ # ls -l /dev/block/bootdevice/by-name/persist
lrwxrwxrwx 1 root root 21 1971-01-25 16:38 /dev/block/bootdevice/by-name/persist -> /dev/block/mmcblk0p30
potter_n:/ #
I find the named partitions easier to understand and more distinct, so no one's going to accidentally backup/restore the wrong partition because they typed in the wrong number.

echo92 said:
One thing I was thinking about was is it possible to make a permissions fix script for stock ROMs or perhaps patch the custom ROMs so that they don't change the permissions? Or is that permissions change a result of updating to Oreo (as in that you need that change for an Oreo ROM to work)?
Click to expand...
Click to collapse
This is something that I'm considering. With the help of @rachitrawat we now know exactly where the Oreo custom roms have been changing the ownership of the rfs folder. However, I don't know if the 'fix' is as simple as changing the IDs to the correct ones, as there could be implications for those who are currently happily running the Oreo custom roms. Also, it would mean that every rom developer would have to make the change.
If TWRP scripts have the ability to change file ownership, then I will look to build a separate TWRP flashable that does it.

bro im using motog5s plus and while im lost my imei im tried lot of methods and also flashed presist from xda pages.. now i think my presist is gone (
but via trying your method my imei is changed from 0 to 000000876e5501 like this on 1st sim 2nd 1 remain 0 flashing a my efs backup showing a efs2 partition dosnt exist error
---------- Post added at 12:59 AM ---------- Previous post was at 12:59 AM ----------
bro im using motog5s plus and while im lost my imei im tried lot of methods and also flashed presist from xda pages.. now i think my presist is gone (
but via trying your method my imei is changed from 0 to 000000876e5501 like this on 1st sim 2nd 1 remain 0 flashing a my efs backup showing a efs2 partition dosnt exist error
---------- Post added at 01:00 AM ---------- Previous post was at 12:59 AM ----------
bro im using motog5s plus and while im lost my imei im tried lot of methods and also flashed presist from xda pages.. now i think my presist is gone (
but via trying your method my imei is changed from 0 to 000000876e5501 like this on 1st sim 2nd 1 remain 0 flashing a my efs backup showing a efs2 partition dosnt exist error

Would this work if I restored my EFS via TWRP? Or should I go back to the stock EFS to run these commands?
Side note: Very grateful for the hard work of all the people involved in this: @rachitrawat, @NZedPred, and the people who reported their experiences!

5P4RT0N said:
bro im using motog5s plus and while im lost my imei im tried lot of methods and also flashed presist from xda pages.. now i think my presist is gone (
but via trying your method my imei is changed from 0 to 000000876e5501 like this on 1st sim 2nd 1 remain 0 flashing a my efs backup showing a efs2 partition dosnt exist error
Click to expand...
Click to collapse
Is your persist your own one? If not, you need it. If you don't have a backup of it, you're out of luck. No idea about the efs2 partition error. Try this in a shell, and post back with the results:
Code:
su
ls -l /dev/block/bootdevice/by-name/modemst*
Jrhotrod said:
Would this work if I restored my EFS via TWRP? Or should I go back to the stock EFS to run these commands?
Side note: Very grateful for the hard work of all the people involved in this: @rachitrawat, @NZedPred, and the people who reported their experiences!
Click to expand...
Click to collapse
Not quite sure what you're getting at by restoring your EFS. The EFS is recreated on boot with a fully working persist.

NZedPred said:
Not quite sure what you're getting at by restoring your EFS. The EFS is recreated on boot with a fully working persist.
Click to expand...
Click to collapse
I mean that I restored the "cached" EFS in order to temporarily restore my IMEI. After flashing stock with the modemst commands, it gives you IMEI 0, so I restore my backed-up EFS to treat it.
So if I have that cached EFS, and with that my IMEI, can I still run this procedure? Because I still do get IMEI 0 after taking OTAs, flashing stock, etc.
I hope I'm making sense :silly:

Jrhotrod said:
I mean that I restored the "cached" EFS in order to temporarily restore my IMEI. After flashing stock with the modemst commands, it gives you IMEI 0, so I restore my backed-up EFS to treat it.
So if I have that cached EFS, and with that my IMEI, can I still run this procedure? Because I still do get IMEI 0 after taking OTAs, flashing stock, etc.
I hope I'm making sense :silly:
Click to expand...
Click to collapse
Ok you probably can run through this procedure as long as your persist is yours. If in doubt, post the info that I ask for in the OP including the output of the commands.