PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Galaxy S4 Mini
i9190 (serrano3gxx)
i9192 (serranodsub)
i9195 (serranoltexx)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
To fix size detection during backup of /boot and /recovery, someone post output from terminal command:
Code:
su
ls -l /dev/block/platform/msm_sdcc.1/by-name
Here ya go:
Code:
lrwxrwxrwx root root 2013-09-29 20:14 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-09-29 20:14 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-09-29 20:14 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-09-29 20:14 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-09-29 20:14 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-09-29 20:14 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-09-29 20:14 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-09-29 20:14 hidden -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-09-29 20:14 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-09-29 20:14 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-09-29 20:14 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-09-29 20:14 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-09-29 20:14 param -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-09-29 20:14 persdata -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-09-29 20:14 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-09-29 20:14 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-09-29 20:14 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-09-29 20:14 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-09-29 20:14 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-09-29 20:14 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-09-29 20:14 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-09-29 20:14 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-09-29 20:14 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-09-29 20:14 userdata -> /dev/block/mmcblk0p24
Also output of /proc/partitions if needed:
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 12800 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 10240 mmcblk0p13
179 14 10240 mmcblk0p14
179 15 10240 mmcblk0p15
179 16 7160 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 8 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 12288 mmcblk0p20
179 21 1536000 mmcblk0p21
179 22 204800 mmcblk0p22
179 23 36864 mmcblk0p23
179 24 5685231 mmcblk0p24
179 32 1955840 mmcblk1
179 33 1955809 mmcblk1p1
arco68 said:
Here ya go:
Code:
lrwxrwxrwx root root 2013-09-29 20:14 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-09-29 20:14 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-09-29 20:14 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-09-29 20:14 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-09-29 20:14 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-09-29 20:14 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-09-29 20:14 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-09-29 20:14 hidden -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-09-29 20:14 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-09-29 20:14 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-09-29 20:14 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-09-29 20:14 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-09-29 20:14 param -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-09-29 20:14 persdata -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-09-29 20:14 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-09-29 20:14 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-09-29 20:14 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-09-29 20:14 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-09-29 20:14 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-09-29 20:14 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-09-29 20:14 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-09-29 20:14 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-09-29 20:14 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-09-29 20:14 userdata -> /dev/block/mmcblk0p24
Also output of /proc/partitions if needed:
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 12800 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 10240 mmcblk0p13
179 14 10240 mmcblk0p14
179 15 10240 mmcblk0p15
179 16 7160 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 8 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 12288 mmcblk0p20
179 21 1536000 mmcblk0p21
179 22 204800 mmcblk0p22
179 23 36864 mmcblk0p23
179 24 5685231 mmcblk0p24
179 32 1955840 mmcblk1
179 33 1955809 mmcblk1p1
Click to expand...
Click to collapse
This was fast, thank you :good:
Just finished downloading stock recovery.img to repack with better exfat support than fuse
Meanwhile, you can get a cm build in above links, I just populated
Have one question:
i9190 and i9195 can use same kernel? Do they have same /proc/partitions links?
If no, anyone can upload recovery.img from a recent Samsung stock firmware for i9190?
New files
- i9195: repack with stock Samsung ramdisk for faster exfat support + enable mount usb storage for external sd
- serranoltexx: cm-10.1 repack
http://d-h.st/users/philz_touch/?fld_id=25693#files
Please, test these in both versions:
- adb shell is root?
- adb sideload works?
- mount usb storage for external sd is ok?
Why this: Samsung kernel has support for exfat using kernel modules, which is way faster than fuse, used by cyanogenmod builds
However, on the S4 (i9505), Samsung introduced wired policies that could cause adb shell to fail to have root rights
I also disabled wired Samsung policies to enable flashing cm-10.2 ROMs and maybe get adb shell as root
I am not sure if both above versions have usb storage mount working + adb sideload
A detailed report about each of these will make it possible to improve support
Phil3759 said:
New files
- i9195: repack with stock Samsung ramdisk for faster exfat support + enable mount usb storage for external sd
- serranoltexx: cm-10.1 repack
http://d-h.st/users/philz_touch/?fld_id=25693#files
Please, test these in both versions:
- adb shell is root?
- adb sideload works?
- mount usb storage for external sd is ok?
Why this: Samsung kernel has support for exfat using kernel modules, which is way faster than fuse, used by cyanogenmod builds
However, on the S4 (i9505), Samsung introduced wired policies that could cause adb shell to fail to have root rights
I also disabled wired Samsung policies to enable flashing cm-10.2 ROMs and maybe get adb shell as root
I am not sure if both above versions have usb storage mount working + adb sideload
A detailed report about each of these will make it possible to improve support
Click to expand...
Click to collapse
hi thx for the good job.
install with your script doesnt worked on i9195 but with cm10.1 head it worked.
i have not tested things you want because i am not at home. but recovery working. first boot need 3-5min. install rom worked but it doesnt mount my 64gb samsung microsd. only internal.
this one is working install to i9195
Code:
assert(getprop("ro.product.device") == "serranolte" || getprop("ro.build.product") == "serranolte" ||
getprop("ro.product.device") == "serranoltexx" || getprop("ro.build.product") == "serranoltexx" ||
getprop("ro.product.device") == "i9195" || getprop("ro.build.product") == "i9195" ||
getprop("ro.product.device") == "GT-I9195" || getprop("ro.build.product") == "GT-I9195");
Sent from my GT-I9195 using xda premium
proxuser said:
hi thx for the good job.
install with your script doesnt worked on i9195 but with cm10.1 head it worked.
i have not tested things you want because i am not at home. but recovery working. first boot need 3-5min. install rom worked but it doesnt mount my 64gb samsung microsd. only internal.
this one is working install to i9195
Code:
assert(getprop("ro.product.device") == "serranolte" || getprop("ro.build.product") == "serranolte" ||
getprop("ro.product.device") == "serranoltexx" || getprop("ro.build.product") == "serranoltexx" ||
getprop("ro.product.device") == "i9195" || getprop("ro.build.product") == "i9195" ||
getprop("ro.product.device") == "GT-I9195" || getprop("ro.build.product") == "GT-I9195");
Sent from my GT-I9195 using xda premium
Click to expand...
Click to collapse
I am re-uploading zip files with correct serranolte and serrano3g most often used tags
Should be online soon
Let me know about questions I asked above so that we can look to fix things
tested: philz_touch_5.15.9-i9195.zip
- boot to recovery need 2-3 minutes.
- E:can't mount /external_sd/
mount sdcard and internal (cant test it now but in ubuntu it doesnt show)
- adb shell is root?
look attachaed picture 1
- sideload works ?
yes it works
look attached picture 2
install cm10.2 works, it boots
if boot time be fixed its very usable and fast recovery. thx
proxuser said:
tested: philz_touch_5.15.9-i9195.zip
- boot to recovery need 2-3 minutes.
- E:can't mount /external_sd/
mount sdcard and internal (cant test it now but in ubuntu it doesnt show)
- adb shell is root?
look attachaed picture 1
- sideload works ?
yes it works
look attached picture 2
install cm10.2 works, it boots
if boot time be fixed its very usable and fast recovery. thx
Click to expand...
Click to collapse
Sadly, it is probably a kernel issue. Only fix is custom kernel to fix these, compiled from Samsung sources, with a few fixes to enable exfat loading, root and probably disable flashing sensors which causes the delay
Meanwhile, I will drop to a pure cyanogenmod based ramdisk instead of Samsung
Any news for i9190 ? Philz please make safe stock kernel
So, any more feedback to confirm mounting external storage works or not?
Hi Phil3759,
For my S4 Mini I9195 only the philz_touch_5.15.9-serranoltexx.zip worked.
With this recovery i could make a backup to the ext. SD, but it took about 25 minutes.
When i flash philz_touch_5.15.9-i9195.zip, then the phone stuck always on booting to recovery
and i have to remove the battery an reflash with odin.
stiff
Phil3759 said:
So, any more feedback to confirm mounting external storage works or not?
Click to expand...
Click to collapse
Hi Philz, i use i9190 (serrano3gxx) but not install from stock rom why?
Hi @Phil3759
we also get 5.17.6
Sent from my GT-I9195 using XDA Premium 4 mobile app
GT-i9192
@Phil3759
does this work on the GT-i9192?
Thanks
v5.17.8 - cwm 6.0.4.4 *** Beta Untested ***
http://d-h.st/users/philz_touch/?fld_id=26444#files
This version is based on a custom kernel compiled from Samsung sources
I enabled exfat/ntfs support through ko modules and adb root (credits to @wanam)
This version is built on cm-10.2 tree and has fixes for a massive backup speed enhancement
Please report for any issue
STAticKY said:
@Phil3759
does this work on the GT-i9192?
Thanks
Click to expand...
Click to collapse
if not, you might want to change i919x in the title to i9190/i9195 as i9192 falls under the category of i919x...
Sent from my RM-915_apac_australia_new_zealand_214 using Tapatalk
Phil3759 said:
v5.17.8 - cwm 6.0.4.4 *** Beta Untested ***
http://d-h.st/users/philz_touch/?fld_id=26444#files
This version is based on a custom kernel compiled from Samsung sources
I enabled exfat/ntfs support through ko modules and adb root (credits to @wanam)
This version is built on cm-10.2 tree and has fixes for a massive backup speed enhancement
Please report for any issue
Click to expand...
Click to collapse
Hi Philz please make for i9190 models
citymen34 said:
Hi Philz please make for i9190 models
Click to expand...
Click to collapse
LoL
I don't even know if i9195 version works
Will wait for feedback. Seems really a non popular device
Related
I have an LG Motion and I would like a copy of your aboot file to try to see if I can get the bootloader unlocked while it's flashed on the motion.
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
and send that file to me please
Thanks in advaced.
Screw LG's locked bootloaders!!!
Also this may be in the wrong place. If it belongs in development, I'm sorry.
dev/block/platform/msm_sdcc.1/by-name/aboot: cannot open for read: No such file
or directory
reas0n said:
dev/block/platform/msm_sdcc.1/by-name/aboot: cannot open for read: No such file
or directory
Click to expand...
Click to collapse
tegra platform...and we have no partition named aboot
i have x-loader.img and u-boot.img. here:
https://www.box.com/s/a6pyad63qwauos7zdw2b
Tim_Pan said:
tegra platform...and we have no partition named aboot
Click to expand...
Click to collapse
Hmmmm, you think it will still work?
Edit: what are the blocks and names of your partitions?
Sent from my LG-MS770
[email protected]:/ # cat proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
179 1 10240 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 1572864 mmcblk0p3
179 4 393216 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 81920 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 13062144 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 20480 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 47104 mmcblk0p13
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 15645696 mmcblk1
179 49 15644672 mmcblk1p1
Code:
ls -l /dev/block/platform/sdhci-tegra.3/by-name
lrwxrwxrwx root root 2013-03-10 23:24 APP -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-03-10 23:24 CAC -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-03-10 23:24 CAL -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-03-10 23:24 DRM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-03-10 23:24 FOT -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-03-10 23:24 LNX -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-03-10 23:24 MLT -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-03-10 23:24 MSC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-03-10 23:24 NVA -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-03-10 23:24 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-03-10 23:24 UDA -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-03-10 23:24 UDB -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-03-10 23:24 USP -> /dev/block/mmcblk0p6
reas0n said:
[email protected]:/ # cat proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
179 1 10240 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 1572864 mmcblk0p3
179 4 393216 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 81920 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 13062144 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 20480 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 47104 mmcblk0p13
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 15645696 mmcblk1
179 49 15644672 mmcblk1p1
Click to expand...
Click to collapse
No name of partitions?
Guess I'll have to figure out which partition is which on my own
I figure if your bootloader even does boot, I gotta make sure the partitions are still the same, and if not the same, flash things to the correct partitions according to your bootloader.
Sent from my LG-MS770
Can't flash the file given....our bootloader is 512KBs...yours is 10MBs............
sammyz said:
Can't flash the file given....our bootloader is 512KBs...yours is 10MBs............
Click to expand...
Click to collapse
i dont know if u still need, but download .tot or kdz for your phone and use lg binextractor(is not from lg,search google)extract the tot or kdz and get the aboot.i only have the nexus 4 and l5 so i cant help u much.
Our bootloader cannot be dumped from partitions. It's built into a lower level on the device. The two devices are in no way similar. Ours has a Tegra 3 chipset, yours is MSM.
If you really want to take a look at our bootloader, you can find a dump somewhere in the development section. But even if you find it and it fits for your device, DO NOT flash it by any means!!! It's one of the worst ideas one can come up with. You can very easily brick your device.
reas0n said:
i have x-loader.img and u-boot.img. here:
https://www.box.com/s/a6pyad63qwauos7zdw2b
Click to expand...
Click to collapse
Where did you get these from? It's not for the O4X.
Sent from my OmniROM-powered LG Optimus 4X HD
HTML:
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 4096 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 13312 mmcblk0p9
259 2 15360 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 4096 mmcblk0p12
259 5 20480 mmcblk0p13
259 6 4096 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 12288 mmcblk0p16
259 9 4096 mmcblk0p17
259 10 2560000 mmcblk0p18
259 11 204800 mmcblk0p19
259 12 51200 mmcblk0p20
259 13 12423168 mmcblk0p21
179 24 512 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
/dev/block/platform/12200000.dwmmc0 # ls -l by-name
ls -l by-name
lrwxrwxrwx 1 root root 20 Jan 2 03:31 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 Jan 2 03:31 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jan 2 03:31 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 2 03:31 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 20 Jan 2 03:31 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 2 03:31 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 Jan 2 03:31 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 2 03:31 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jan 2 03:31 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Jan 2 03:31 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 2 03:31 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 2 03:31 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 2 03:31 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 2 03:31 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 2 03:31 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 2 03:31 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 2 03:31 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 2 03:31 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Jan 2 03:31 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 2 03:31 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 2 03:31 m9kefs3 -> /dev/block/mmcblk0p6
DUMP CODE
HTML:
adb shell dd if=/dev/block/mmcblk0p9 of=/sdcard/BOOT
adb shell dd if=/dev/block/mmcblk0p1 of=/sdcard/BOTA0
adb shell dd if=/dev/block/mmcblk0p2 of=/sdcard/BOTA1
adb shell dd if=/dev/block/mmcblk0p19 of=/sdcard/CACHE
adb shell dd if=/dev/block/mmcblk0p7 of=/sdcard/CARRIER
adb shell dd if=/dev/block/mmcblk0p12 of=/sdcard/CDMA-RADIO
adb shell dd if=/dev/block/mmcblk0p3 of=/sdcard/EFS
adb shell dd if=/dev/block/mmcblk0p20 of=/sdcard/HIDDEN
adb shell dd if=/dev/block/mmcblk0p11 of=/sdcard/OTA
adb shell dd if=/dev/block/mmcblk0p8 of=/sdcard/PARAM
adb shell dd if=/dev/block/mmcblk0p16 of=/sdcard/PERSDATA
adb shell dd if=/dev/block/mmcblk0p13 of=/sdcard/RADIO
adb shell dd if=/dev/block/mmcblk0p10 of=/sdcard/RECOVERY
adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/RESERVED2
adb shell dd if=/dev/block/mmcblk0p18 of=/sdcard/SYSTEM
adb shell dd if=/dev/block/mmcblk0p15 of=/sdcard/TDATA
adb shell dd if=/dev/block/mmcblk0p14 of=/sdcard/TOMBSTONES
adb shell dd if=/dev/block/mmcblk0p4 of=/sdcard/m9kefs1
adb shell dd if=/dev/block/mmcblk0p5 of=/sdcard/m9kefs2
adb shell dd if=/dev/block/mmcblk0p6 of=/sdcard/m9kefs3
adb shell dd if=/dev/block/mmcblk0 of=/sdcard/G900H_1G bs=512 count=2097152
all files download link: http://pan.baidu.com/s/1hq1dBZu passwork: bvet
and i want make system.tar by make_ext4fs,but it can not work on Odin. if somebody know how to make the system.img ,plz tell me .thx
Hi all,
I bought a moto g 2nd gen in USA. I live in Ireland. The phone works fine but mobile data is extremely slow. I get E but no 3G whatsoever. I was wondering if I was able to change baseband to an EMEA one would it solve the problem. I am attaching a screenshot of my settings.
Many thanks..
You got dual sim or single sim? If dual put your card sim in first slot (on the left)
wiemar said:
You got dual sim or single sim? If dual put your card sim in first slot (on the left)
Click to expand...
Click to collapse
Hi, Its a single sim.
Settings>sim>settings connection>mobile networks
wiemar said:
Settings>sim>settings connection>mobile networks
Click to expand...
Click to collapse
Hi, did that. See attached.
Go to the dialer and enter:
*#*#4636#*#*
Click on Phone Information, then look for Set preferred network type, then select ‘WCDMA only’
The problem is that the US uses different frequencies from the rest of the world, so your US phone may not be able to use it on a hardware level. If after selecting WCDMA only you can't connect at all, there is nothing you can do to fix it as it is a physical issue with the radio.
SeanWatson said:
Go to the dialer and enter:
*#*#4636#*#*
Click on Phone Information, then look for Set preferred network type, then select ‘WCDMA only’
The problem is that the US uses different frequencies from the rest of the world, so your US phone may not be able to use it on a hardware level. If after selecting WCDMA only you can't connect at all, there is nothing you can do to fix it as it is a physical issue with the radio.
Click to expand...
Click to collapse
Thanks Sean, I tried that but the code just disappears after pressing the last *.
It seems I have the US version of the phone and not the Global version therefore I am screwed. - according to Motorola support.
gdublin said:
Thanks Sean, I tried that but the code just disappears after pressing the last *.
It seems I have the US version of the phone and not the Global version therefore I am screwed. - according to Motorola support.
Click to expand...
Click to collapse
Do I need to root my phone first?
After you enter the last * the dialer will disappear and a new activity will appear with Phone Information, Battery Information, etc. Touch the Phone Information and then preferred network to WCDMA only.
It doesn't need root. There is an app that does the same thing, but this forum won'tlet me post direct links. Search for Philipp Mangelow in Google Play, and install Network
gdublin said:
Hi all,
I bought a moto g 2nd gen in USA. I live in Ireland. The phone works fine but mobile data is extremely slow. I get E but no 3G whatsoever. I was wondering if I was able to change baseband to an EMEA one would it solve the problem. I am attaching a screenshot of my settings.
Many thanks..
Click to expand...
Click to collapse
Yeah, it sounds like the 2100MHz band is disabled in firmware. Others have been said they've lost 'mobile data' when flashing OTA packages willy-nilly from the XT1063/64 onto the XT1068. You need an EMEA (Europe, Middle East and Asia) firmware package... Do they exist? Flashing an XT1068 baseband firmware might work as the phone still has a single radio, I dunno, but I wouldn't bank on it. IF the partition sizes match between the XT1063/64 and XT1068, you could always try it and flash the old firmware back if it screws things up...
My XT1068 is running firmware with same version number, but with the EMEA_DSDS_CUST suffix. I believe DSDS denotes dual sim dual standby.
CDMA support is the difference between the MSM8226 and the MSM8626 chipsets and they both use the same WTR2605 multi-mode radio, AFAIK. Motorola's support response is typically inaccurate. I'm pretty sure the issue is the firmware, not the hardware, but good luck getting an EMEA firmware out of Motorola -- they'd obviously much rather you buy another handset!
rufflove said:
Yeah, it sounds like the 2100MHz band is disabled in firmware. Others have been said they've lost 'mobile data' when flashing OTA packages willy-nilly from the XT1063/64 onto the XT1068. You need an EMEA (Europe, Middle East and Asia) firmware package... Do they exist? Flashing an XT1068 baseband firmware might work as the phone still has a single radio, I dunno, but I wouldn't bank on it. IF the partition sizes match between the XT1063/64 and XT1068, you could always try it and flash the old firmware back if it screws things up...
My XT1068 is running firmware with same version number, but with the EMEA_DSDS_CUST suffix. I believe DSDS denotes dual sim dual standby.
CDMA support is the difference between the MSM8226 and the MSM8626 chipsets and they both use the same WTR2605 multi-mode radio, AFAIK. Motorola's support response is typically inaccurate. I'm pretty sure the issue is the firmware, not the hardware, but good luck getting an EMEA firmware out of Motorola -- they'd obviously much rather you buy another handset!
Click to expand...
Click to collapse
Thanks for the reply. My phone is a single sim. IS it still XT1068? If I find suitable firmware but its for dual sim do you think that would matter?
SeanWatson said:
After you enter the last * the dialer will disappear and a new activity will appear with Phone Information, Battery Information, etc. Touch the Phone Information and then preferred network to WCDMA only.
It doesn't need root. There is an app that does the same thing, but this forum won'tlet me post direct links. Search for Philipp Mangelow in Google Play, and install Network
Click to expand...
Click to collapse
Thanks Sean, That app worked. Unfortunately WCDMA only did not work. I'll have to go with rufflove's suggestion and try and find EMEA firmware that will activate the radio frequency I need.
gdublin said:
Thanks for the reply. My phone is a single sim. IS it still XT1068? If I find suitable firmware but its for dual sim do you think that would matter?
Click to expand...
Click to collapse
I believe your phone is the XT1064 version. That version is for US only.
Sent from my XT1068 using XDA Free mobile app
gdublin said:
Thanks for the reply. My phone is a single sim. IS it still XT1068? If I find suitable firmware but its for dual sim do you think that would matter?
Click to expand...
Click to collapse
The XT1068 has a white sticker under the backpiece that includes the model code. It definitely sounds like you have the XT1064, but you can confirm by checking the sticker. I honestly do not know what effect(s) shoehorning an XT1068 baseband firmware onto an XT1064 would have. For starters, it depends whether the XT1064 and XT1068 share the exact same partition map. It is highly likely that they do. Could you post the output of the following command? You'll need the adb tools installed.
Code:
adb shell cat /proc/partitions
Alternatively, install a terminal emulator app on the phone and issue 'cat /proc/partitions'. If I remember correctly, the first partition (mmcblk0p1 ) holds the baseband firmware. It should have a block size of 65536. You'd also need to overwrite the fsg partition, but I can't remember which partition it maps to right now! I'd check mine, but I'm in Windows whilst gaming and my Android tools are installed on my usual linux desktop instead.
rufflove said:
The XT1068 has a white sticker under the backpiece that includes the model code. It definitely sounds like you have the XT1064, but you can confirm by checking the sticker. I honestly do not know what effect(s) shoehorning an XT1068 baseband firmware onto an XT1064 would have. For starters, it depends whether the XT1064 and XT1068 share the exact same partition map. It is highly likely that they do. Could you post the output of the following command? You'll need the adb tools installed.
Code:
adb shell cat /proc/partitions
Alternatively, install a terminal emulator app on the phone and issue 'cat /proc/partitions'. If I remember correctly, the first partition (mmcblk0p1 ) holds the baseband firmware. It should have a block size of 65536. You'd also need to overwrite the fsg partition, but I can't remember which partition it maps to right now! I'd check mine, but I'm in Windows whilst gaming and my Android tools are installed on my usual linux desktop instead.
Click to expand...
Click to collapse
Thank . Its a XT1064 . Im not very technical but i will have a go at what you suggested and will get back to you.
gdublin said:
Thank . Its a XT106 . Im not very technical but i will have a go at what you suggested and will get back to you.
Click to expand...
Click to collapse
The full model number has 4 digits. You should definitely get hold of a copy of the 4.4.4 OTA, or root your device and backup everything, before attempting anything adventurous.
rufflove said:
The XT1068 has a white sticker under the backpiece that includes the model code. It definitely sounds like you have the XT1064, but you can confirm by checking the sticker. I honestly do not know what effect(s) shoehorning an XT1068 baseband firmware onto an XT1064 would have. For starters, it depends whether the XT1064 and XT1068 share the exact same partition map. It is highly likely that they do. Could you post the output of the following command? You'll need the adb tools installed.
Code:
adb shell cat /proc/partitions
Click to expand...
Click to collapse
hi, all,
im in same shi*, i have *64 version of device, bought in US, now in EU only EDGE is working...
here is list of partitions:
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 1012 mmcblk0p4
179 5 200 mmcblk0p5
179 6 400 mmcblk0p6
179 7 32 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2332 mmcblk0p10
179 11 1012 mmcblk0p11
179 12 200 mmcblk0p12
179 13 400 mmcblk0p13
179 14 32 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1052 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 488 mmcblk0p19
179 20 32 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 1 mmcblk0p22
179 23 8 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 128 mmcblk0p25
179 26 3072 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 4096 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10200 mmcblk0p31
259 0 10280 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 546944 mmcblk0p35
259 4 1130496 mmcblk0p36
259 5 8192 mmcblk0p37
259 6 5774208 mmcblk0p38
179 32 2048 mmcblk0rpm
179 64 15440896 mmcblk1
179 65 15436800 mmcblk1p1
can you share list from *68...
if flashing only baseband, is this part enough from flashing Stock with fastboot:
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
if this will work, i will make flashable zip for those basebands...
oh yeah, happy new year!!!
I'm short on time right now, but here's the partition table:
Code:
179 0 7634944 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 1012 mmcblk0p4
179 5 200 mmcblk0p5
179 6 400 mmcblk0p6
179 7 32 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2332 mmcblk0p10
179 11 1012 mmcblk0p11
179 12 200 mmcblk0p12
179 13 400 mmcblk0p13
179 14 32 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1052 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 488 mmcblk0p19
179 20 32 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 1 mmcblk0p22
179 23 8 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 128 mmcblk0p25
179 26 3072 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 4096 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10200 mmcblk0p31
259 0 10280 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 546944 mmcblk0p35
259 4 1130496 mmcblk0p36
259 5 8192 mmcblk0p37
259 6 5774208 mmcblk0p38
179 32 2048 mmcblk0rpmb
179 64 15449088 mmcblk1
179 65 15448064 mmcblk1p1
Here's the mappings (obtained via 'ls -l /dev/block/platform/msm_sdcc.1/by-name'):
Code:
lrwxrwxrwx root root 1970-01-25 22:05 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-25 22:05 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-25 22:05 abootBackup -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-25 22:05 boot -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-25 22:05 cache -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-25 22:05 cid -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-25 22:05 clogo -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-25 22:05 deviceinfo -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-25 22:05 dhob -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-25 22:05 fsc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-25 22:05 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-25 22:05 ftmlog -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-25 22:05 hob -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-25 22:05 kpan -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-25 22:05 logo -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-25 22:05 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-25 22:05 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-25 22:05 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-25 22:05 modemst1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-25 22:05 modemst2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-25 22:05 padA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-25 22:05 padB -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-25 22:05 pds -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-25 22:05 persist -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-25 22:05 recovery -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-25 22:05 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-25 22:05 rpmBackup -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-25 22:05 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-25 22:05 sdi -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-25 22:05 sdiBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-25 22:05 sp -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-25 22:05 ssd -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-25 22:05 system -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-25 22:05 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-25 22:05 tzBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-25 22:05 userdata -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-25 22:05 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-25 22:05 utagsBackup -> /dev/block/mmcblk0p15
IIRC, Motorola's OTA system also writes to the fsg partition, which appears to include service definitions for various carriers. My retgb device has files for European carriers. I'd read up on that, too.
Any update here? I bought a moto g 2014 in the US and it was supposed to be an international version but 3g doesn't work in Europe.... Anyone kept trying this baseband change solution?
3/4 GB is taken up by something, how to partition the internal storage and get my space back? I have did a full wipe, format, deleted the OS, it still only give me ~1GB. For the HTC Desire 510, Boost Mobile.
Thanks
ddvche said:
3/4 GB is taken up by something, how to partition the internal storage and get my space back? I have did a full wipe, format, deleted the OS, it still only give me ~1GB. For the HTC Desire 510, Boost Mobile.
Thanks
Click to expand...
Click to collapse
Not possible, you don't have access to the specific partition.
MrMike2182 said:
Not possible, you don't have access to the specific partition.
Click to expand...
Click to collapse
how do I gain access? or how does HTC gain access?
ddvche said:
how do I gain access? or how does HTC gain access?
Click to expand...
Click to collapse
You won't be able to do it no matter what so you might as well just get an SD Card like the rest of us and have your phone install only important apps to internal storage. The not so important ones can be sent to the SD Card. You're never going to get that other space seriously!
well, there isn't a point for a 3gb inaccessible black box, including HTC. so, it's there to serve a purpose. stock rom and bloatware only need 1GB at the most to restore itself. that leaves 2gb of space for HTC to do things? like 2gb of spyware to sell our info to the NSA?
any insight is greatly appreciated.
ddvche said:
well, there isn't a point for a 3gb inaccessible black box, including HTC. so, it's there to serve a purpose. stock rom and bloatware only need 1GB at the most to restore itself. that leaves 2gb of space for HTC to do things? like 2gb of spyware to sell our info to the NSA?
any insight is greatly appreciated.
Click to expand...
Click to collapse
I've already called HTC and b!tched at them about it and they still wouldn't say nothing other than it's part of the rom and restore crap or something and all the carrier bloatware and they wouldn't give me a way to get it off.
Answering my own question here are the partition names and block sizes,
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 2015-10-26 21:18 adsp -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-10-26 21:18 board_info -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-10-26 21:18 boot -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2015-10-26 21:18 cache -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-10-26 21:18 carrier -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-10-26 21:18 cdma_record -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-10-26 21:18 control -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-10-26 21:18 custdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-10-26 21:18 ddr -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-10-26 21:18 debug_config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-10-26 21:18 devlog -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-10-26 21:18 dsps -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-10-26 21:18 extra -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-10-26 21:18 fataldevlog -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-10-26 21:18 fsc -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-10-26 21:18 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-10-26 21:18 hboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-10-26 21:18 local -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-10-26 21:18 mfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-10-26 21:18 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-10-26 21:18 modem_st1 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-10-26 21:18 modem_st2 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-10-26 21:18 pdata -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-10-26 21:18 pg1fs -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-10-26 21:18 pg2fs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-10-26 21:18 radio -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-10-26 21:18 radio_config -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-10-26 21:18 recovery -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2015-10-26 21:18 reserve -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-10-26 21:18 reserve_1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-10-26 21:18 reserve_2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-10-26 21:18 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-10-26 21:18 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-10-26 21:18 sbl1_update -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-10-26 21:18 sdi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-10-26 21:18 skylink -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-10-26 21:18 sp1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-10-26 21:18 ssd -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-10-26 21:18 system -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-10-26 21:18 tool_diag -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-10-26 21:18 tz -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-10-26 21:18 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-10-26 21:18 wcnss -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-10-26 21:18 wifi -> /dev/block/mmcblk0p13
sizes
cat /proc/partitions
major minor #blocks name
253 0 262144 zram0
179 0 3817472 mmcblk0
179 1 1024 mmcblk0p1
179 2 32768 mmcblk0p2
179 3 16 mmcblk0p3
179 4 15327 mmcblk0p4
179 5 256 mmcblk0p5
179 6 24255 mmcblk0p6
179 7 256 mmcblk0p7
179 8 256 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 32 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 5120 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 32 mmcblk0p14
179 15 1024 mmcblk0p15
259 0 61441 mmcblk0p16
259 1 5120 mmcblk0p17
259 2 8192 mmcblk0p18
259 3 1536 mmcblk0p19
259 4 76801 mmcblk0p20
259 5 4096 mmcblk0p21
259 6 10240 mmcblk0p22
259 7 7167 mmcblk0p23
259 8 1024 mmcblk0p24
259 9 1536 mmcblk0p25
259 10 1536 mmcblk0p26
259 11 20480 mmcblk0p27
259 12 4 mmcblk0p28
259 13 256 mmcblk0p29
259 14 16 mmcblk0p30
259 15 1281 mmcblk0p31
259 16 64 mmcblk0p32
259 17 1024 mmcblk0p33
259 18 1 mmcblk0p34
259 19 8 mmcblk0p35
259 20 256 mmcblk0p36
259 21 25600 mmcblk0p37
259 22 30720 mmcblk0p38
259 23 14498 mmcblk0p39
259 24 16384 mmcblk0p40
259 25 16384 mmcblk0p41
259 26 110592 mmcblk0p42
259 27 2097152 mmcblk0p43
259 28 1179648 mmcblk0p44
179 16 4096 mmcblk0rpmb
match up the gibberish block names and you can sorta make sense of it, it adds up to ~4million blocks, I suppose that accounts for the 4gb we supposedly have
ddvche said:
Answering my own question here are the partition names and block sizes,
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 2015-10-26 21:18 adsp -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-10-26 21:18 board_info -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-10-26 21:18 boot -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2015-10-26 21:18 cache -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-10-26 21:18 carrier -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-10-26 21:18 cdma_record -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-10-26 21:18 control -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-10-26 21:18 custdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-10-26 21:18 ddr -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-10-26 21:18 debug_config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-10-26 21:18 devlog -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-10-26 21:18 dsps -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-10-26 21:18 extra -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-10-26 21:18 fataldevlog -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-10-26 21:18 fsc -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-10-26 21:18 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-10-26 21:18 hboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-10-26 21:18 local -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-10-26 21:18 mfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-10-26 21:18 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-10-26 21:18 modem_st1 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-10-26 21:18 modem_st2 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-10-26 21:18 pdata -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-10-26 21:18 pg1fs -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-10-26 21:18 pg2fs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-10-26 21:18 radio -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-10-26 21:18 radio_config -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-10-26 21:18 recovery -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2015-10-26 21:18 reserve -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-10-26 21:18 reserve_1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-10-26 21:18 reserve_2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-10-26 21:18 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-10-26 21:18 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-10-26 21:18 sbl1_update -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-10-26 21:18 sdi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-10-26 21:18 skylink -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-10-26 21:18 sp1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-10-26 21:18 ssd -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-10-26 21:18 system -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-10-26 21:18 tool_diag -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-10-26 21:18 tz -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-10-26 21:18 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-10-26 21:18 wcnss -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-10-26 21:18 wifi -> /dev/block/mmcblk0p13
sizes
cat /proc/partitions
major minor #blocks name
253 0 262144 zram0
179 0 3817472 mmcblk0
179 1 1024 mmcblk0p1
179 2 32768 mmcblk0p2
179 3 16 mmcblk0p3
179 4 15327 mmcblk0p4
179 5 256 mmcblk0p5
179 6 24255 mmcblk0p6
179 7 256 mmcblk0p7
179 8 256 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 32 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 5120 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 32 mmcblk0p14
179 15 1024 mmcblk0p15
259 0 61441 mmcblk0p16
259 1 5120 mmcblk0p17
259 2 8192 mmcblk0p18
259 3 1536 mmcblk0p19
259 4 76801 mmcblk0p20
259 5 4096 mmcblk0p21
259 6 10240 mmcblk0p22
259 7 7167 mmcblk0p23
259 8 1024 mmcblk0p24
259 9 1536 mmcblk0p25
259 10 1536 mmcblk0p26
259 11 20480 mmcblk0p27
259 12 4 mmcblk0p28
259 13 256 mmcblk0p29
259 14 16 mmcblk0p30
259 15 1281 mmcblk0p31
259 16 64 mmcblk0p32
259 17 1024 mmcblk0p33
259 18 1 mmcblk0p34
259 19 8 mmcblk0p35
259 20 256 mmcblk0p36
259 21 25600 mmcblk0p37
259 22 30720 mmcblk0p38
259 23 14498 mmcblk0p39
259 24 16384 mmcblk0p40
259 25 16384 mmcblk0p41
259 26 110592 mmcblk0p42
259 27 2097152 mmcblk0p43
259 28 1179648 mmcblk0p44
179 16 4096 mmcblk0rpmb
match up the gibberish block names and you can sorta make sense of it, it adds up to ~4million blocks, I suppose that accounts for the 4gb we supposedly have
Click to expand...
Click to collapse
It doesn't really make sense to me because if you go look at the partition where the radio is, you'll find that it has free space of 199.8 MB!!! What the hell do they need almost 200 MB in free space for when the largest radio file size is only 13 MB?!?! Then they have almost 30 freaking spots with 259 MB as you see but there is NO point in taking all of that internal free space from us. It just makes no sense to me!!
MrMike2182 said:
It doesn't really make sense to me because if you go look at the partition where the radio is, you'll find that it has free space of 199.8 MB!!! What the hell do they need almost 200 MB in free space for when the largest radio file size is only 13 MB?!?! Then they have almost 30 freaking spots with 259 MB as you see but there is NO point in taking all of that internal free space from us. It just makes no sense to me!!
Click to expand...
Click to collapse
The part we have access to is mmcblk0p44/userdata around 1.17GB. System itself allocates 2.1GB. you can actually see this in some of the storage tools, however it is all write protected, and majority of it >1.3GB is free space. But I guess if we flash anything custom, we are only allowed the 1.17
Radio and radio config are 76.8 and 8.2mb respectively. for HTC sensation it is 41.mb and 8.2mb. The allocation ratio is the same with all other HTC phones pretty much, they always get their 3gb to hog the free space. HTC too much headache, *throws phone off the roof*.
even if we get a way to partition it, you need back up all 46 of those things separately, re partition in to the same blocks but with the space adjustments, and hope it doesn't corrupt something and brick your phone. yeah no...
Edit: at-least they didn't label it spyware, selling your information to the NSA. Then again we probably will never know their exact functions. Free space is better than malware :/
ddvche said:
The part we have access to is mmcblk0p44/userdata around 1.17GB. System itself allocates 2.1GB. you can actually see this in some of the storage tools, however it is all write protected, and majority of it >1.3GB is free space. But I guess if we flash anything custom, we are only allowed the 1.17
Radio and radio config are 76.8 and 8.2mb respectively. for HTC sensation it is 41.mb and 8.2mb. The allocation ratio is the same with all other HTC phones pretty much, they always get their 3gb to hog the free space. HTC too much headache, *throws phone off the roof*.
even if we get a way to partition it, you need back up all 46 of those things separately, re partition in to the same blocks but with the space adjustments, and hope it doesn't corrupt something and brick your phone. yeah no...
Edit: at-least they didn't label it spyware, selling your information to the NSA. Then again we probably will never know their exact functions. Free space is better than malware :/
Click to expand...
Click to collapse
Trust me I won't be getting another HTC phone. I have the new Motorola X Style so I'm not to worried about the Desire anymore!
del.
DISCLAIMER
All, what you do with your Phone : doing at your own RISK !
the only chance, that i see : https://forum.xda-developers.com/9-lite/development/honor-9-lite-update-zip-lld-l31-8-0-0-t3767781
extract the *.img , that you need and flash it
Attention : this is for C432 ( Country europ )
PLEASE : if you flash (or use dd) is your Risk ! Never flash other Partitions as "recovery_ramdisk" and "system" ! Here is the Risk little for kill phone .
most error : bootloop . you have huawei-images - than you can self-repair
NEVER flash images from other Phone-Model ! only you 100% secure that is 100% same hardware inside .
you flash other partition-images : you can kill your phone ! now only repair is - send to huawei-service and pay !
huawei-repair is change MotherBoard : cost over 100 €
i hope this help you
Partition-List from H9L
HWLLD-H:/ # cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
254 0 1572864 zram0
179 0 30535680 mmcblk0
179 1 256 mmcblk0p1
179 2 256 mmcblk0p2
179 3 256 mmcblk0p3
179 4 768 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 6144 mmcblk0p7
179 8 65536 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 32768 mmcblk0p13
179 14 2048 mmcblk0p14
179 15 2048 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 14336 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 65536 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 24576 mmcblk0p21
179 22 61440 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 2048 mmcblk0p24
179 25 16384 mmcblk0p25
179 26 12288 mmcblk0p26
179 27 24576 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 24576 mmcblk0p30
179 31 16384 mmcblk0p31
179 32 32768 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 28672 mmcblk0p34
179 35 4096 mmcblk0p35
179 36 98304 mmcblk0p36
179 37 1024 mmcblk0p37
179 38 1024 mmcblk0p38
179 39 2048 mmcblk0p39
179 40 16384 mmcblk0p40
179 41 4096 mmcblk0p41
179 42 131072 mmcblk0p42
179 43 131072 mmcblk0p43
179 44 2048 mmcblk0p44
179 45 2048 mmcblk0p45
179 46 4096 mmcblk0p46
179 47 32768 mmcblk0p47
259 0 2048 mmcblk0p48
259 1 16384 mmcblk0p49
259 2 30720 mmcblk0p50
259 3 3620864 mmcblk0p51
259 4 196608 mmcblk0p52
259 5 32768 mmcblk0p53
259 6 802816 mmcblk0p54
259 7 196608 mmcblk0p55
259 8 24637440 mmcblk0p56
179 144 4096 mmcblk0rpmb
179 96 4096 mmcblk0boot1
179 48 4096 mmcblk0boot0
179 192 125041664 mmcblk1
179 193 125040640 mmcblk1p1
HWLLD-H:/ #
HWLLD-H:/ # ls -al /dev/block/platform/hi_mci.0/by-name
total 0
drwxr-xr-x 2 root root 1160 2018-03-21 08:52 .
drwxr-xr-x 4 root root 1280 2018-03-21 08:52 ..
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 bootfail_info -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 cache -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 cust -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 dfx -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 dto -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 dts -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 erecovery_kernel -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 erecovery_ramdisk -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 erecovery_vbmeta -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 erecovery_vendor -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 fw_hifi -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 fw_lpm3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 hisitest0 -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 hisitest1 -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 hisitest2 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 kernel -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 modem_fw -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 modem_om -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 modem_secure -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 odm -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 patch -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 product -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 ramdisk -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 recovery_ramdisk -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 recovery_vbmeta -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 recovery_vendor -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 reserved2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 reserved3 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 reserved4 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 reserved5 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 reserved8 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 reserved9 -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 rrecord -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 sensorhub -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 system -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 teeos -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 trustfirmware -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 userdata -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 vbmeta -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 vendor -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 version -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 vrl_backup -> /dev/block/mmcblk0p2
HWLLD-H:/ #
He asked the question yesterday in telegram group and got answer.
He damaged his persist partition and need to restore it step by step.