Related
So,
I am at a loss on how to get the GN to activate USB storage in CM Recovery.
parted shows:
Code:
~ # parted /dev/block/platform/omap/omap_hsmmc.0/mmcblk0 print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB ext4 cache
12 1218MB 15.8GB 14.5GB ext4 userdata
so, I see part 12 as my "/mnt/sdcard" partition..
previous versions I looked at had syntax like:
Code:
case $1 in
on)
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
echo "USB Mass Storage enabled"
;;
off)
echo "" > /sys/devices/platform/usb_mass_storage/lun0/file
echo "USB Mass Storage disabled"
;;
--)
;;
On this device, there is:
Code:
[email protected]:/sys/devices/platform/omap/omap_hsmmc.0
lrwxrwxrwx root root 2012-01-26 10:15 driver -> ../../../../bus/platform/drivers/omap_hsmmc
-r--r--r-- root root 4096 2012-01-26 10:15 microamps_requested_omap_hsmmc.0-vmmc
drwxr-xr-x root root 2012-01-26 09:49 mmc_host
-r--r--r-- root root 4096 2012-01-26 10:15 modalias
drwxr-xr-x root root 2012-01-26 09:49 power
lrwxrwxrwx root root 2012-01-26 10:15 subsystem -> ../../../../bus/platform
-rw-r--r-- root root 4096 2012-01-26 09:49 uevent
Anyone have any ideas how to do this before I spend a day figuring it out?
Thanks!
Anyone have any ideas how to do this [...] ?
Click to expand...
Click to collapse
You can't. There is no UMS/mass storage support with the Galaxy Nexus.
(This thread should be in the q&a section.)
gokpog said:
You can't. There is no UMS/mass storage support with the Galaxy Nexus.
(This thread should be in the q&a section.)
Click to expand...
Click to collapse
+1
(10 chars)
use adb push pull for your basic requirements
It's also not CM Recovery. It's Clockwork Recovery.
Also wrong section.
gokpog said:
You can't. There is no UMS/mass storage support with the Galaxy Nexus.
(This thread should be in the q&a section.)
Click to expand...
Click to collapse
There actually is.. It is in the kernel I am using, and I can successfully send a block device out it using /sys/devices/platform/omap/musb-omap2430/musb-hdrc/gadget/lun0/file
The nexus has to have it's persistent usb modes set properly (turn off MTP)..
I just cannot make it work in recovery even though it's kernel has the feature as well. Recovery is the only place I want it too
Oh well, I'll keep using ad like I have been.
Thanks
ghost_o said:
There actually is.. It is in the kernel I am using, and I can successfully send a block device out it using /sys/devices/platform/omap/musb-omap2430/musb-hdrc/gadget/lun0/file
The nexus has to have it's persistent usb modes set properly (turn off MTP)..
I just cannot make it work in recovery even though it's kernel has the feature as well. Recovery is the only place I want it too
Oh well, I'll keep using ad like I have been.
Thanks
Click to expand...
Click to collapse
ghost_o, I really want to know how you can make it work. I setted the persistent usb config to only adb (no mtp) and tried to sent the userdata block device to that lun0 but the block device is not properly sent to the usb connected computer. My goal is to be able to use an app called usb sharer or something similar.
Any help will be appreciated :good:
As you know backup and restore partitions can be done using dd command in linux.
I know it's not noob friendly, but since custom kernels and recoveries raises flash counter, it's a good idea.
rotohammer has made a detailed explanation here for Galaxy Tab.
So all we need the block device list for note 2
/dev/block/mmcblk0 Whole Internal Storage
/dev/block/mmcblk0p1 4194kB BOTA0
/dev/block/mmcblk0p2 4194kB BOTA1
/dev/block/mmcblk0p3 21.0MB EFS
/dev/block/mmcblk0p4 4194kB m9kefs1
/dev/block/mmcblk0p5 4194kB m9kefs2
/dev/block/mmcblk0p6 4194kB m9kefs3
/dev/block/mmcblk0p7 8389kB PARAM
/dev/block/mmcblk0p8 8389kB BOOT (Kernel)
/dev/block/mmcblk0p9 8389kB RECOVERY
/dev/block/mmcblk0p10 92.3MB RADIO (Modem)
/dev/block/mmcblk0p11 4194kB TOMBSTONES
/dev/block/mmcblk0p12 1434MB CACHE
/dev/block/mmcblk0p13 2147MB SYSTEM
/dev/block/mmcblk0p14 587MB HIDDEN
/dev/block/mmcblk0p15 8389kB OTA
/dev/block/mmcblk0p16 11.4GB USERDATA (User Accessible Storage and /DATA folder)
[email protected] said:
As you know backup and restore partitions can be done using dd command in linux.
I know it's not noob friendly, but since custom kernels and recoveries raises flash counter, it's a good idea.
rotohammer has made a detailed explanation here for Galaxy Tab.
So I need all the block device list for note 2
So far I know
/dev/block/mmcblk0p13 = /system
/dev/block/mmcblk0p12 = /cache
/dev/block/mmcblk0p16 = /data
/dev/block/mmcblk0p3 = /efs
/dev/block/mmcblk0p9 = /recovery
/dev/block/mmcblk0p8 = /boot (kernel)
I'm not a linux expert, can somebody confirm/correct these?
Click to expand...
Click to collapse
Perhaps you should find out what the mount command does before you start using dd to read and write directly to the partitions. These sort of commands don't take prisoners
I said I'm not a linux expert, it doesn't mean I'm totally noob. I'm using Lubuntu on my netbook.
I'm well aware of risks, I'm using dd on PC time to time.
Mount only shows mounted partitions. I'm asking those partitions. I couldn't find a full partitions list anywhere
There are many partitions and I want to know what they are
Code:
cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 8192 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 90112 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 1400832 mmcblk0p12
179 13 2097152 mmcblk0p13
179 14 573440 mmcblk0p14
179 15 8192 mmcblk0p15
259 0 11141120 mmcblk0p16
179 16 62367744 mmcblk1
179 17 62351360 mmcblk1p1
[email protected]:/ # ls -l /dev/block/mmcblk*
ls -l /dev/block/mmcblk*
brw------- root root 179, 0 2013-04-01 00:14 mmcblk0
brw------- root root 179, 1 2013-04-01 00:14 mmcblk0p1
brw-rw---- system radio 179, 10 2013-04-01 00:14 mmcblk0p10
brw-rw---- system radio 179, 11 2013-04-01 00:14 mmcblk0p11
brw------- root root 179, 12 2013-04-01 00:14 mmcblk0p12
brw------- root root 179, 13 2013-04-01 00:14 mmcblk0p13
brw------- root root 179, 14 2013-04-01 00:14 mmcblk0p14
brw------- root root 179, 15 2013-04-01 00:14 mmcblk0p15
brw------- root root 259, 0 2013-04-01 00:14 mmcblk0p16
brw------- root root 179, 2 2013-04-01 00:14 mmcblk0p2
brw------- root root 179, 3 2013-04-01 00:14 mmcblk0p3
brw-rw---- system radio 179, 4 2013-04-01 00:14 mmcblk0p4
brw-rw---- system radio 179, 5 2013-04-01 00:14 mmcblk0p5
brw-rw---- system radio 179, 6 2013-04-01 00:14 mmcblk0p6
brw-rw---- system root 179, 7 2013-04-01 00:14 mmcblk0p7
brw------- root root 179, 8 2013-04-01 00:14 mmcblk0p8
brw------- root root 179, 9 2013-04-01 00:14 mmcblk0p9
brw------- root root 179, 16 2013-04-01 00:14 mmcblk1
brw------- root root 179, 17 2013-04-01 00:14 mmcblk1p1
For some reason listing partitions by-label doesn't work either for android or block devices.
Code:
[email protected]:/ # ls -l /dev/block/by-label
ls -l /dev/block/by-label
/dev/block/by-label: No such file or directory
[email protected] said:
...So far I know
/dev/block/mmcblk0p13 = /system
/dev/block/mmcblk0p12 = /cache
/dev/block/mmcblk0p16 = /data
/dev/block/mmcblk0p3 = /efs
/dev/block/mmcblk0p9 = /recovery
/dev/block/mmcblk0p8 = /boot (kernel)
I'm not a linux expert, can somebody confirm/correct these?
Click to expand...
Click to collapse
These partitions are correct. Radio/modem partition is missing. /dev/block/mmcblk0p10 = /modem/baseband/radio
Edit:
For the list of all partitions, use 'parted' command.
Partitions from the international GNote2 N7100 are:
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\cargo>cd tools
C:\Users\cargo\tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VTU00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB RADIO
11 164MB 168MB 4194kB TOMBSTONES
12 168MB 1602MB 1434MB ext4 CACHE
13 1602MB 3750MB 2147MB ext4 SYSTEM
14 3750MB 4337MB 587MB ext4 HIDDEN
15 4337MB 4345MB 8389kB OTA
16 4345MB 15.8GB 11.4GB ext4 USERDATA
(parted)
cargobr151 said:
These partitions are correct. Radio/modem partition is missing. /dev/block/mmcblk0p10 = /modem/baseband/radio
Edit:
For the list of all partitions, use 'parted' command.
Partitions from the international GNote2 N7100 are:
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\cargo>cd tools
C:\Users\cargo\tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VTU00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB RADIO
11 164MB 168MB 4194kB TOMBSTONES
12 168MB 1602MB 1434MB ext4 CACHE
13 1602MB 3750MB 2147MB ext4 SYSTEM
14 3750MB 4337MB 587MB ext4 HIDDEN
15 4337MB 4345MB 8389kB OTA
16 4345MB 15.8GB 11.4GB ext4 USERDATA
(parted)
Click to expand...
Click to collapse
Thank you a lot, parted is not working on mine. Probably busybox related?
Edit: Nevermind I found the executable file of parted . Worked fine. Thanks again.
You must have installed a custom recovery. (with parted command included)
Like cwm or twrp v2.4.4.0. I use twrp v2.4.4.0.
@OP updated my thread with this thread info...You can visit here
@[email protected]
So continue here
Question is if we makes tar file form dump file we have created like system.img, can we flash it with odin?
dr.ketan said:
@[email protected]
So continue here
Question is if we makes tar file form dump file we have created like system.img, can we flash it with odin?
Click to expand...
Click to collapse
Roger that
here http://forum.xda-developers.com/showthread.php?t=1777579 @das7982 well explained the instructions for Galaxy SIII
According to his post, he's recommending to make an ODIN package from only system.img
To make system.img of note 2
Code:
dd if=/dev/block/mmcblk0p13 of=/storage/extSdCard/system.img bs=4096
Here we need a linux pc or Cygwin for Windows. If we going to use Cygwin, we need to install it along with tar, md5sum commands
Code:
tar -H ustar -c system.img > system.img.tar
Then we need to make Md5 checksum
Code:
md5sum -t system.img.tar >> system.img.tar
rename it
Code:
mv system.img.tar system.img.tar.md5
I haven't tried this yet but I'll try soon
I have already made this and also in try to test it.
Sent from my GT-N7100 using xda premium
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
I have read it, I think it shouldn't raise counter unless we have custom recovery /kernel
B'coz I don't think custom tar will raise counter, i am regularly extract recovery and kernel from stock and packing it separately in tar, it never raised counter.
Sent from my GT-N7100 using xda premium
dr.ketan said:
I have already made this and also in try to test it.
Sent from my GT-N7100 using xda premium
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
I have read it, I think it shouldn't raise counter unless we have custom recovery /kernel
B'coz I don't think custom tar will raise counter, i am regularly extract recovery and kernel from stock and packing it separately in tar, it never raised counter.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
You're correct, stock kernel and recovery shouldn't increase the flash counter.
To backup /data we can use
Code:
adb shell
stop
busybox tar -cZvf /storage/extSdCard/data.ext4.tar --exclude media --exclude dalvik-cache /data
reboot
To restore
Code:
adb shell
stop
busybox tar -xvf /storage/extSdCard/data.ext4.tar -C /
reboot
Hi,
recently i updated via CWM my unblocked, rooted xperia m (C1905). Phone has FXP317, earlier i updated radio installing stock 4.3 and it going well, besides fatal GPS, as usual
After upgrade form FXP317 to FXP319 and reboot phone, it running veeeryy slow and suddenly hangs up. After restart to CWM (it lasts couple minutes), i try to install it again (install from zip) and it failed - it shows problem with mounting /DATA.
Now i attempt to format /DATA but it failed - CWM says that partition can't be mounted.
Another try - flash stock rom (Flasher form Androxyde) gives
Code:
19/048/2014 07:48:57 - INFO - Device connected in flash mode
19/049/2014 07:49:06 - INFO - Selected Bundle for Xperia M C1905. FW release : Google Android 4.3 (Jelly Bean). Customization : 15.4.A.0.23
19/049/2014 07:49:06 - INFO - Preparing files for flashing
19/049/2014 07:49:53 - INFO - Please connect your device into flashmode.
19/049/2014 07:49:54 - INFO - Opening device for R/W
19/049/2014 07:49:54 - INFO - Reading device information
19/049/2014 07:49:54 - INFO - Phone ready for flashmode operations.
19/049/2014 07:49:54 - INFO - Current device : Unknown: Mar 7 2014/10:51:59 - YT910M7GB9 - Unknown: Mar 7 2014/10:51:59 - Unknown: Mar 7 2014/10:51:59 - Unknown: Mar 7 2014/10:51:59
19/049/2014 07:49:54 - INFO - Start Flashing
19/049/2014 07:49:54 - INFO - Processing loader.sin
19/049/2014 07:49:54 - INFO - Checking header
19/049/2014 07:49:54 - INFO - Flashing data
19/049/2014 07:49:55 - INFO - Processing of loader.sin finished.
19/049/2014 07:49:55 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8227_5 / Bootloader status : ROOTED
19/049/2014 07:49:55 - INFO - Processing partition-image.sin
19/049/2014 07:49:55 - INFO - Checking header
19/049/2014 07:49:55 - INFO - Flashing data
19/049/2014 07:49:55 - INFO - Processing of partition-image.sin finished.
19/049/2014 07:49:55 - INFO - Parsing boot delivery
19/049/2014 07:49:55 - INFO - Phone boot version : S1_Boot_MSM_8227_5. Boot delivery version : S1_Boot_MSM_8227_5
19/049/2014 07:49:55 - INFO - Boot delivery up to date. Nothing to do
19/049/2014 07:49:55 - INFO - Processing kernel.sin
19/049/2014 07:49:55 - INFO - Checking header
19/049/2014 07:49:55 - INFO - Flashing data
19/049/2014 07:49:55 - ERROR - Processing of kernel.sin finished with errors.
19/049/2014 07:49:55 - INFO - Ending flash session
19/049/2014 07:49:55 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x8020001C ";
Soft from SONY - SUS, PC Companion, EMMA did't recognize my phone and gives up.
Meanwhile i flash kernel and i made fatal mistake (i thought so) - i tried to flash wrong kernel (it has 83 bytes), but after choosing the right file I could install the appropriate kernel.
Now i have CWM 6.0.4.8, and i can connect phone in flash mode, also in fastboot but i can't flash any rom because i can't mount /data
Command adb devices -l gives
List of devices attached
YT910M7GB9 recovery product:C1905 model:C1905 device:nicki
How to mount /data or how to do the re-partition? What should I do to flash the stock rom?
Have you flashed the stock ROM again? Does it still show the same error?
elmkzgirxp said:
Have you flashed the stock ROM again? Does it still show the same error?
Click to expand...
Click to collapse
Yes, i did and same again. I have stock ROM 4.1.2, stock ROM 4.3. One thing - phone starts and - after maybe 30 min or so - stops on "Encryption unsuccessful bla bla bla". I try even recovery backup form http://forum.xda-developers.com/showthread.php?p=51574842 but it failed - folder /system cannot be restored.
I'm thinking about partitioning internal memory, but i don't know how. I have an access via flashmode and i'm looking for solution about using adb
Encryption? How'd that get there?
elmkzgirxp said:
Encryption? How'd that get there?
Click to expand...
Click to collapse
In my case - remove battery, wait 5 sec, i turn on the phone and wait about 30 min - after that long boot this is all i see.
TomekParuszewski said:
In my case - remove battery, wait 5 sec, i turn on the phone and wait about 30 min - after that long boot this is all i see.
Click to expand...
Click to collapse
Why not refer here... This might solve your problem.
elmkzgirxp said:
Why not refer here... This might solve your problem.
Click to expand...
Click to collapse
Thx, so far i don't find exactly the same problem as mine, but now i try rubber band trick. I don't know how this will help, will see
Exact same problem
With fxp 18
TomekParuszewski said:
Thx, so far i don't find exactly the same problem as mine, but now i try rubber band trick. I don't know how this will help, will see
Click to expand...
Click to collapse
Hmm, according to the definition of soft brick, and therefore that I can enter fastboot mode and flashmode and CWM, the phone is not soft bricked, but there is a problem with partitions or privileges SU, because I can not reflash rom. The system is still not able to mount the directory / data.
I will try connect to phone by the adb command and see, err, i don't know what - i must check available commands. Right now i'm waiting for CWM
After get into adb shell i get:
Code:
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nsu
su
/sbin/sh: su: not found
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
~ # ←[6nls -l
ls -l
__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 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
C:\SDK\sdk\platform-tools>adb remount
remount failed: Success
C:\SDK\sdk\platform-tools>adb devices -l
List of devices attached
YT910M7GB9 recovery product:C1905 model:C1905 device:nicki
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls -l
ls -l
__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 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6ndf -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 430.6M 128.0K 430.4M 0% /dev
tmpfs 430.6M 8.0K 430.6M 0% /tmp
tmpfs 430.6M 0 430.6M 0% /storage
tmpfs 430.6M 0 430.6M 0% /mnt/secure
tmpfs 430.6M 0 430.6M 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
246.2M 4.6M 241.7M 2% /cache
~ # ←[6nfdisk
fdisk
BusyBox v1.22.1 static (2014-04-06 21:24 +0200) multi-call binary.
Usage: fdisk [-ul] [-C CYLINDERS] [-H HEADS] [-S SECTORS] [-b SSZ] DISK
Change partition table
-u Start and End are in sectors (instead of cylinders)
-l Show partition table for each DISK, then exit
-b 2048 (for certain MO disks) use 2048-byte sectors
-C CYLINDERS Set number of cylinders/heads/sectors
-H HEADS
-S SECTORS
~ # ←[6nfdisk -l
fdisk -l
~ # ←[6nfdisk -l
fdisk -l
~ # ←[6n^C
C:\SDK\sdk\platform-tools>
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls
ls
boot logo.rle
boot.txt mnt
cache proc
charger property_contexts
data recovery
datadata res
default.prop root
dev sbin
emmc sd-ext
etc sdcard
external_sd seapp_contexts
file_contexts sepolicy
fstab.qcom storage
init sys
init.qcom.syspart_fixup.sh system
init.rc tmp
init.recovery.qcom.rc ueventd.qcom.rc
internal_sd ueventd.rc
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
~ # ←[6ncd data
cd data
/data # ←[6nls
ls
media
/data # ←[6n^C
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls -l
ls -l
__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 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
I don't have any information about partitions (filesystem tmpfs)!
TomekParuszewski said:
I don't have any information about partitions (filesystem tmpfs)!
Click to expand...
Click to collapse
Firstly you need mount partitions through recovery: item mounts and storage
Also from there try to format all of them and then flash via flashtool / via ZIP / restore backup.
Here is possibility that your NAND-flash (internal 4GB memory chip) broken or have a lot bad sectors.
Bonoboo said:
Firstly you need mount partitions through recovery: item mounts and storage
Also from there try to format all of them and then flash via flashtool / via ZIP / restore backup.
Here is possibility that your NAND-flash (internal 4GB memory chip) broken or have a lot bad sectors.
Click to expand...
Click to collapse
Unfortunately, I can not mount / data or / system. After a very long time the command mount / data, then throws an error, the contents of which I can not remember now. I will try to rewrite its contents exactly as it appears. is below:
(i'm wainting rught now - 14:29)
I have version 6.0.4.8 CWM and I see no formatting options. I tried to upload the CWM 6.0.4.7 from this post http://forum.xda-developers.com/showthread.php?t=2494793 but I could not do that. I still have my version. My bad, of course i have format command.
Does this mean that my phone died? Do I still have any chance to fix it?
TomekParuszewski said:
After a very long time the command mount / data, then throws an error, the contents of which I can not remember now. I will try to rewrite its contents exactly as it appears.
Click to expand...
Click to collapse
Command from ADB? Try from recovery menu.
And output of command will be helpful.
TomekParuszewski said:
Does this mean that my phone died?
Click to expand...
Click to collapse
Don't give up for now.
UPD: I googled ERR_DYNAMIC=0x8020001C and found 7 threads with same problem with Xperia M:
1, 2, 3, 4, 5, 6, 7
All them have error while flashing different parts: kernel and data.
And no solution there for now.
Bonoboo said:
Command from ADB? Try from recovery menu.
And output of command will be helpful.
Don't give up for now.
Click to expand...
Click to collapse
thank you for your words of encouragement - I'm gonna fight to the end
BTW - in time when i'm waiting to output for command mount /data from recovery, I have access to the phone via adb (but it's normal after all, i suppose)
Bonoboo said:
UPD: I googled ERR_DYNAMIC=0x8020001C and found 6 threads with same problem with Xperia M:
1, 2, 3, 4, 5, 6
All them have error while flashing different parts: kernel and data.
And no solution there for now.
Click to expand...
Click to collapse
yes, most of them i've seen, thx
Just info :
Re-partition method not available for now.
Maybe when flashing via flashtool keep tick only on partition-image.sin restore stock.
There is some method to erase internal memory via adb, but it for other model.
And I don't know will it help here.
Questions:
1. So your device not was encrypted, right?
2. Try mounts and storage > format all
3. Try mount via menu in recovery
Bonoboo said:
Just info :
Re-partition method not available for now.
Maybe when flashing via flashtool keep tick only on partition-image.sin restore stock.
There is some method to erase internal memory via adb, but it for other model.
And I don't know will it help here.
Questions:
1. So your device not was encrypted, right?
3. You sure that in mounts and storage no format options?
4. Try mount via menu in recovery?
2. How about post error while mounting?
Click to expand...
Click to collapse
Answers:
If i'm wait long enough, phone boot to screen "Encryption unsuccessful", so i don't know - I do not encrypt the phone as I remember
Sorry, of course there is format command in recovery, my bad
I will try again and write exact message from the screen
Sorry for messing numbers, I edited post.
TomekParuszewski said:
in time when i'm waiting to output for command mount /data from recovery, I have access to the phone via adb (but it's normal after all, i suppose)
Click to expand...
Click to collapse
Seems not. Reboot.
Try formatting.
Just note about adb output earlier.
ls shows temporary FS that recovery creates in RAM.
By fact blocks devices in /dev/block/ and we can do something with them, like recreate partitions using mke2fs
Or erase them by dd if=/dev/zero
Try commands:
cat /proc/partitions
mount
fdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p5
And try flashing via flashtool:
– untick wipe data and cache
– tick all in Exclude section except partition
Here useful commands (similar problem for Samsung, restoring partition table helps)
And here list of all our partitions relatively number:
FOTAKernel -> /dev/block/mmcblk0p23
LTALabel -> /dev/block/mmcblk0p16
TA -> /dev/block/mmcblk0p1
aboot -> /dev/block/mmcblk0p6
alt_aboot -> /dev/block/mmcblk0p12
alt_rpm -> /dev/block/mmcblk0p15
alt_s1sbl2 -> /dev/block/mmcblk0p10
alt_sbl1 -> /dev/block/mmcblk0p8
alt_sbl2 -> /dev/block/mmcblk0p9
alt_sbl3 -> /dev/block/mmcblk0p11
alt_tz -> /dev/block/mmcblk0p13
boot -> /dev/block/mmcblk0p17
cache -> /dev/block/mmcblk0p26
fsg -> /dev/block/mmcblk0p21
modem -> /dev/block/mmcblk0p18
modemst1 -> /dev/block/mmcblk0p19
modemst2 -> /dev/block/mmcblk0p20
persist -> /dev/block/mmcblk0p24
ramdump -> /dev/block/mmcblk0p22
rpm -> /dev/block/mmcblk0p14
s1sbl2 -> /dev/block/mmcblk0p4
sbl1 -> /dev/block/mmcblk0p2
sbl2 -> /dev/block/mmcblk0p3
sbl3 -> /dev/block/mmcblk0p5
system -> /dev/block/mmcblk0p25
tz -> /dev/block/mmcblk0p7
userdata -> /dev/block/mmcblk0p27
Bonoboo said:
Sorry for messing numbers, I edited post.
Seems not. Reboot.
Try formatting.
Just note about adb output earlier.
ls shows temporary FS that recovery creates in RAM.
By fact blocks devices in /dev/block/ and we can do something with them, like recreate partitions using mke2fs
Or erase them by dd if=/dev/zero
Try commands:
cat /proc/partitions
mount
fdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p5
And try flashing via flashtool:
– untick wipe data and cache
– tick all in Exclude section except partition
Here useful commands (similar problem for Samsung, restoring partition table helps)
And here list of all our partitions relatively number:
Click to expand...
Click to collapse
ok, here the log from CWM - i don't know when each event occurred
Code:
persist.audio.low.latency.rec=false
persist.debug.wfd.enable=1
persist.radio.apm_sim_not_pwdn=1
persist.timed.enable=true
persist.fuse_sdcard=true
keyguard.no_require_sim=true
telephonu.lteOnCdmaDevice=0
DEVICE_PROVISIONED=1
I: Checking for extendedcommand
I:Skipping for extendedcommand, file not found...
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1
I:using /data/media for /sdcard/0/clockworkmod/.no_confirm.
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (File exists)
I:using /data/media for /sdcard/0/clockworkmod/.many_confirm.
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (File exists)
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1
And here is the result of your command
Code:
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
YT910M7GB9 recovery
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>adb shell
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 3866624 mmcblk0
179 1 2048 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 128 mmcblk0p8
179 9 256 mmcblk0p9
179 10 256 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 512 mmcblk0p14
179 15 512 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 20480 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 3072 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 5120 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 1228800 mmcblk0p25
179 26 256000 mmcblk0p26
179 27 2183151 mmcblk0p27
179 32 1955840 mmcblk1
179 33 1954816 mmcblk1p1
~ # ←[6nls -la /dev/block/mmcblk*
ls -la /dev/block/mmcblk*
__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------- 1 root root 179, 0 May 21 11:43 /dev/block/mmcblk0
brw------- 1 root root 179, 1 May 21 11:43 /dev/block/mmcblk0p1
brw------- 1 root root 179, 10 May 21 11:43 /dev/block/mmcblk0p10
brw------- 1 root root 179, 11 May 21 11:43 /dev/block/mmcblk0p11
brw------- 1 root root 179, 12 May 21 11:43 /dev/block/mmcblk0p12
brw------- 1 root root 179, 13 May 21 11:43 /dev/block/mmcblk0p13
brw------- 1 root root 179, 14 May 21 11:43 /dev/block/mmcblk0p14
brw------- 1 root root 179, 15 May 21 11:43 /dev/block/mmcblk0p15
brw------- 1 root root 179, 16 May 21 11:43 /dev/block/mmcblk0p16
brw------- 1 root root 179, 17 May 21 11:43 /dev/block/mmcblk0p17
brw------- 1 root root 179, 18 May 21 11:43 /dev/block/mmcblk0p18
brw------- 1 root root 179, 19 May 21 11:43 /dev/block/mmcblk0p19
brw------- 1 root root 179, 2 May 21 11:43 /dev/block/mmcblk0p2
brw------- 1 root root 179, 20 May 21 11:43 /dev/block/mmcblk0p20
brw------- 1 root root 179, 21 May 21 11:43 /dev/block/mmcblk0p21
brw------- 1 root root 179, 22 May 21 11:43 /dev/block/mmcblk0p22
brw------- 1 root root 179, 23 May 21 11:43 /dev/block/mmcblk0p23
brw------- 1 root root 179, 24 May 21 11:43 /dev/block/mmcblk0p24
brw------- 1 root root 179, 25 May 21 11:43 /dev/block/mmcblk0p25
brw------- 1 root root 179, 26 May 21 11:43 /dev/block/mmcblk0p26
brw------- 1 root root 179, 27 May 21 11:43 /dev/block/mmcblk0p27
brw------- 1 root root 179, 3 May 21 11:43 /dev/block/mmcblk0p3
brw------- 1 root root 179, 4 May 21 11:43 /dev/block/mmcblk0p4
brw------- 1 root root 179, 5 May 21 11:43 /dev/block/mmcblk0p5
brw------- 1 root root 179, 6 May 21 11:43 /dev/block/mmcblk0p6
brw------- 1 root root 179, 7 May 21 11:43 /dev/block/mmcblk0p7
brw------- 1 root root 179, 8 May 21 11:43 /dev/block/mmcblk0p8
brw------- 1 root root 179, 9 May 21 11:43 /dev/block/mmcblk0p9
brw------- 1 root root 179, 32 May 21 11:43 /dev/block/mmcblk1
brw------- 1 root root 179, 33 May 21 11:43 /dev/block/mmcblk1p1
~ # ←[6nmount
mount
rootfs on / type rootfs (rw,seclabel,relatime)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,seclabel,re
latime,data=ordered)
~ # ←[6nfdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p17
Disk /dev/block/mmcblk0p17: 20 MB, 20971520 bytes
4 heads, 16 sectors/track, 640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p17 doesn't contain a valid partition table
~ # ←[6nfdisk -l /dev/block/mmcblk0p5
fdisk -l /dev/block/mmcblk0p5
Disk /dev/block/mmcblk0p5: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p5 doesn't contain a valid partition table
~ # ←[6n
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>
If both partitions are incorrect, should I try to flash?
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?
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.