/dev/block/platform/msm_sdcc.1/by-name:
lrwxrwxrwx root root 2012-11-13 19:02 DDR -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2012-11-13 19:02 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-11-13 19:02 abootb -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-11-13 19:02 boot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-11-13 19:02 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2012-11-13 19:02 grow -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2012-11-13 19:02 m9kefs1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-11-13 19:02 m9kefs2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-11-13 19:02 m9kefs3 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-11-13 19:02 metadata -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2012-11-13 19:02 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2012-11-13 19:02 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-11-13 19:02 persist -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2012-11-13 19:02 recovery -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-11-13 19:02 rpm -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-11-13 19:02 rpmb -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-11-13 19:02 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-11-13 19:02 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-11-13 19:02 sbl2b -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-11-13 19:02 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-11-13 19:02 sbl3b -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-11-13 19:02 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2012-11-13 19:02 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-11-13 19:02 tzb -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2012-11-13 19:02 userdata -> /dev/block/mmcblk0p23
Also provided by c900712 is the Voodoo Report file for the Nexus 4 it may be interesting reading for some people.
EDIT:
Originally posted by Houstonn in post#28
Code:
LG Nexus 4 Mako - LGE960 JVP15Q
Number Start (sector) End (sector) Size Code Name
1 1024 132095 64.0 MiB 0700 modem
2 132096 133119 512.0 KiB FFFF sbl1
3 133120 134143 512.0 KiB FFFF sbl2
4 134144 138239 2.0 MiB FFFF sbl3
5 138240 139263 512.0 KiB FFFF tz
6 139264 184319 22.0 MiB FFFF boot
7 184320 229375 22.0 MiB FFFF recovery
8 229376 230935 780.0 KiB FFFF m9kefs1
9 230936 232495 780.0 KiB FFFF m9kefs2
10 232496 234055 780.0 KiB FFFF m9kefs3
11 234496 235519 512.0 KiB FFFF rpm
12 235520 236543 512.0 KiB FFFF aboot
13 236544 237567 512.0 KiB FFFF sbl2b
14 237568 241663 2.0 MiB FFFF sbl3b
15 241664 242687 512.0 KiB FFFF abootb
16 242688 243711 512.0 KiB FFFF rpmb
17 243712 244735 512.0 KiB FFFF tzb
18 244736 245759 512.0 KiB 8301 metadata
19 245760 278527 16.0 MiB FFFF misc
20 278528 311295 16.0 MiB 8300 persist
21 311296 2031615 840.0 MiB 8300 system
22 2031616 3178495 560.0 MiB 8300 cache
23 3178496 15267839 5.8 GiB 8300 userdata
24 15267840 15268863 512.0 KiB FFFF DDR
25 15268864 15269854 495.5 KiB 8300 grow
Mark.
check ur email
Sent from my Nexus 4 using xda premium
c900712 said:
check ur email
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you thats everything I needed.
Mark.
That's really helpful, thank you! And I am interest to know how to get mount point from a new device? Thanks again.
Sent from my DROID2 GLOBAL using xda app-developers app
Anyone fancy being nice and making a file to use with dsixda's kitchen? Wanna play about with stock ROM build before I get my N4
EddyOS said:
Anyone fancy being nice and making a file to use with dsixda's kitchen? Wanna play about with stock ROM build before I get my N4
Click to expand...
Click to collapse
Just extract system img and then you must make a file for mako to make kitchen work (maybe)
Sent from my HTC Explorer A310e using xda app-developers app
All that's the easy part, it's getting the right mount points so it'll flash correctly. Comparing the OP to existing device files doesn't mean a lot to me unfortunately! Here's the edify_defs file for the Galaxy Nexus if someone wants to help out?
# Samsung Galaxy Nexus (GSM/HSPA+)
change_mnt=yes
param1=ext4
param2=HSMMC
sys_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/system
cache_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/cache
boot_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/boot
data_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/userdata
sdcard_mnt=???
fix_boot3=yes
zyy757 said:
That's really helpful, thank you! And I am interest to know how to get mount point from a new device? Thanks again.
Sent from my DROID2 GLOBAL using xda app-developers app
Click to expand...
Click to collapse
Just download Voodoo Report from the Market and save the output to your usb storage. It will save a zip file to your Internal Storage that has all the info you need.
Mark.
Also got the issue of not being able to deodex the ROM using the kitchen as it's not supporting SDK17 yet...d'oh!
Any ETA for your tool kit please?
vinnyutd6899 said:
Any ETA for your tool kit please?
Click to expand...
Click to collapse
Im working on it right now and have everything set up im just going through all the procedures and adding the FAQ section in the Toolkit.
I will need 1 or 2 testers to make sure the insecure boot image works properly and the nand backup and 1-click works as I dont have a device to test on. As like many others I waited up to order it on the Play Store but had to take my son to school and when I got back it had sold out
Any testers available tonight?
Mark.
mskip said:
Im working on it right now and have everything set up im just going through all the procedures and adding the FAQ section in the Toolkit.
I will need 1 or 2 testers to make sure the insecure boot image works properly and the nand backup and 1-click works as I dont have a device to test on. As like many others I waited up to order it on the Play Store but had to take my son to school and when I got back it had sold out
Any testers available tonight?
Mark.
Click to expand...
Click to collapse
I can test if you want. Just send me an email when you would like to.
mskip said:
Im working on it right now and have everything set up im just going through all the procedures and adding the FAQ section in the Toolkit.
I will need 1 or 2 testers to make sure the insecure boot image works properly and the nand backup and 1-click works as I dont have a device to test on. As like many others I waited up to order it on the Play Store but had to take my son to school and when I got back it had sold out
Any testers available tonight?
Mark.
Click to expand...
Click to collapse
i will test it
Can someone who has fastboot drivers set up please try BOOTING (not flashing) this insecure boot image to see if it boots into Android. If it gets stuck just long press the power button the reboot normally.
Mark.
mskip said:
Can someone who has fastboot drivers set up please try BOOTING (not flashing) this insecure boot image to see if it boots into Android. If it gets stuck just long press the power button the reboot normally.
Mark.
Click to expand...
Click to collapse
Yeah thats worked for me
[vertigo] said:
Yeah thats worked for me
Click to expand...
Click to collapse
+1
Gesendet von meinem Nexus 4 mit Tapatalk 2
[vertigo] said:
Yeah thats worked for me
Click to expand...
Click to collapse
P0MM3S said:
+1
Gesendet von meinem Nexus 4 mit Tapatalk 2
Click to expand...
Click to collapse
Thank you very much I can finish building the toolkit now. I will post when its ready for testing and see who is available. The initial version will have custom recovery operations blocked as it isnt available yet but it shouldnt be long before a working recovery is built.
Mark.
I'm up for testing mskip, also any insight as to why these insecure boot images aren't booting after being flashed yet?
Sent from my Nexus 4 using Tapatalk 2
Kstarz said:
I'm up for testing mskip, also any insight as to why these insecure boot images aren't booting after being flashed yet?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Which insecure boot images arent booting? They dont need to be flashed, just booted to boot the phone and give adb root access.
The one I made and posted a few posts back has been reported to work fine.
Mark.
mskip said:
Which insecure boot images arent booting? They dont need to be flashed, just booted to boot the phone and give adb root access.
The one I made and posted a few posts back has been reported to work fine.
Mark.
Click to expand...
Click to collapse
Yes booting it works fine but flashing it doesn't and I am unsure why it doesn't.
Sent from my Nexus 4 using Tapatalk 2
Related
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
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!
Hello,
I tried to flash C432 ROM on my current C109 ROM, but the Update.app process always fails at 5%...
I extracted update.app,
I tried to flash with fastboot but I probably made something wrong when I tried to wipe data/factory reset with factory recovery...
I can only flash boot / recovery / cust / system
My issue is now the ROM tries to boot, then bootloop to eRecovery...
I can't find a way to revive it...
I tried to flash C109B110 and C432B120 but it does not change my bootloop issue
The original ROM is WAS-LX1AB109C100, I can't find it anywhere ...
Can someone help me ?
Thank you
Edit : My bootloader is unlocked btw
Hey, look here
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=WAS-LX1&firmware_page=0
Try to flash a newer version
aburezk said:
Hey, look here
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=WAS-LX1&firmware_page=0
Try to flash a newer version
Click to expand...
Click to collapse
Already tried, didn't find a solution...
The Update mode always fails at 5%... I can flash with fastboot, but still no luck currently...
Orphee said:
Already tried, didn't find a solution...
The Update mode always fails at 5%... I can flash with fastboot, but still no luck currently...
Click to expand...
Click to collapse
Are you using the original recovery?or TWRP?
Tried both, i think my biggest mistake was to format /data with TWRP...
Orphee said:
Tried both, i think my biggest mistake was to format /data with TWRP...
Click to expand...
Click to collapse
I remember I did something similar when I had lg g2 the solution was to run some commands in adb and it worked bypassed the loop
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
These are the commands
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
aburezk said:
I remember I did something similar when I had lg g2 the solution was to run some commands in adb and it worked bypassed the loop
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
These are the commands
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Click to expand...
Click to collapse
You do this while in TWRP ? Cause I don't think I have access to ADB when booting.
Orphee said:
You do this while in TWRP ? Cause I don't think I have access to ADB when booting.
Click to expand...
Click to collapse
Yes from twrp
aburezk said:
Yes from twrp
Click to expand...
Click to collapse
in /dev/block/platform/hi_mci.0/by-name/
Code:
lrwxrwxrwx 1 root root 20 May 31 14:24 vrl_backup -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 31 14:24 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 May 31 14:24 version -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 May 31 14:24 vendor -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 May 31 14:24 userdata -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 May 31 14:24 trustfirmware -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 May 31 14:24 teeos -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 May 31 14:24 system -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 May 31 14:24 splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 May 31 14:24 sensorhub -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 May 31 14:24 secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 May 31 14:24 rrecord -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved9 -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved8 -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved7 -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved6 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved5 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved4 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 May 31 14:24 reserved3 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved2 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved1 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 May 31 14:24 recovery2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 May 31 14:24 recovery -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 May 31 14:24 product -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 May 31 14:24 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 May 31 14:24 patch -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 20 May 31 14:24 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 31 14:24 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 May 31 14:24 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 May 31 14:24 modem_om -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 May 31 14:24 modem_fw -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 May 31 14:24 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest2 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest1 -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest0 -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 May 31 14:24 fw_lpm3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 31 14:24 fw_hifi -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 May 31 14:24 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 31 14:24 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 May 31 14:24 dts -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 May 31 14:24 dfx -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 May 31 14:24 cust -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 May 31 14:24 cache -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 May 31 14:24 bootfail_info -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 May 31 14:24 boot -> /dev/block/mmcblk0p28
I don't have fota.
Orphee said:
in /dev/block/platform/hi_mci.0/by-name/
Code:
lrwxrwxrwx 1 root root 20 May 31 14:24 vrl_backup -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 31 14:24 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 May 31 14:24 version -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 May 31 14:24 vendor -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 May 31 14:24 userdata -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 May 31 14:24 trustfirmware -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 May 31 14:24 teeos -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 May 31 14:24 system -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 May 31 14:24 splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 May 31 14:24 sensorhub -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 May 31 14:24 secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 May 31 14:24 rrecord -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved9 -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved8 -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved7 -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved6 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved5 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved4 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 May 31 14:24 reserved3 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved2 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved1 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 May 31 14:24 recovery2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 May 31 14:24 recovery -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 May 31 14:24 product -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 May 31 14:24 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 May 31 14:24 patch -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 20 May 31 14:24 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 31 14:24 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 May 31 14:24 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 May 31 14:24 modem_om -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 May 31 14:24 modem_fw -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 May 31 14:24 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest2 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest1 -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest0 -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 May 31 14:24 fw_lpm3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 31 14:24 fw_hifi -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 May 31 14:24 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 31 14:24 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 May 31 14:24 dts -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 May 31 14:24 dfx -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 May 31 14:24 cust -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 May 31 14:24 cache -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 May 31 14:24 bootfail_info -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 May 31 14:24 boot -> /dev/block/mmcblk0p28
I don't have fota.
Click to expand...
Click to collapse
Thats was for LG G2, it's different here
Hello,
I fixed it with DC Phoenix and the right FW.
Thanks !
Orphee said:
Hello,
I fixed it with DC Phoenix and the right FW.
Thanks !
Click to expand...
Click to collapse
:good:
can you please give me the link for dc phoenix?
Orphee said:
Hello,
I fixed it with DC Phoenix and the right FW.
Thanks !
Click to expand...
Click to collapse
i have the same problem with my p10 lite. please give me the link of dc phoenix.
geanish95 said:
i have the same problem with my p10 lite. please give me the link of dc phoenix.
Click to expand...
Click to collapse
https://www.dc-unlocker.com/file-list/DC-unlocker_softwares/DC_Phoenix
Good evening I have a huawei p10 lite and I installed another firmware of another phone.
Now the p10 lite phone does not turn on, it is off, can anyone help me restore it?
Thanks so much
Angel
---------- Post added at 06:49 PM ---------- Previous post was at 06:37 PM ----------
I wanted to tell you that the phone Huawei p10 lite does not go into fastboot mode and do not know how to restore it.
I installed the firmware of another telephone DC Phoenix.
And now she does not turn on
Thank you and sorry for my English not perfect
Angelo_Thanks said:
Good evening I have a huawei p10 lite and I installed another firmware of another phone.
Now the p10 lite phone does not turn on, it is off, can anyone help me restore it?
Thanks so much
Angel
---------- Post added at 06:49 PM ---------- Previous post was at 06:37 PM ----------
I wanted to tell you that the phone Huawei p10 lite does not go into fastboot mode and do not know how to restore it.
I installed the firmware of another telephone DC Phoenix.
And now she does not turn on
Thank you and sorry for my English not perfect
Click to expand...
Click to collapse
Try plugging USB hold power+vol down
What's your model?
Hi my model is Huawei p10 Lite WAS-LX1A a few days ago I received the upgrade to C432B131 I wanted to install it as a please but did not allow me with unlocked and root recovery TWRP.
Then I installed it I do not know how to do it after several attempts but the phone did not work well. When I clicked on developer options she returned to the home page. So that I then installed a firmware of another phone and so no longer signs of life. I tried various keystrokes but nothing turned on.
Can you help me please?
Thanks the phone is new.
Angel
I DC Phoenix active on the PC does not know yet how long the activation with credits. How can I restore the Huawei P10 Lite phone that does not turn on?
The phone does not go in fastboot mode !!!
Thank you very much for helping
Angel
I tried to charge the Huawei p10 lite phone
but will not charge does not light any LED while it is charging anything.
can you help me?
Is there a way to restart the phone with a Toolkit or something else?
I thank you for the answer.
Angelo_Thanks said:
I tried to charge the Huawei p10 lite phone
but will not charge does not light any LED while it is charging anything.
can you help me?
Is there a way to restart the phone with a Toolkit or something else?
I thank you for the answer.
Click to expand...
Click to collapse
You may send a message on dc phoenix support website, I know he has another tool (HCU? ), if there is a way to revive it, he will probably know how...
$ ls -al /dev/block/platform/13500000.dwmmc0/by-name
total 0
drwxr-xr-x 2 root root 680 2019-07-08 13:45 .
drwxr-xr-x 3 root root 780 2019-07-08 13:45 ..
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 2019-07-08 13:45 bota0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2019-07-08 13:45 bota1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2019-07-08 13:45 bota2 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 bota3 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 cache -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2019-07-08 13:45 cm -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 cp_debug -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 20 2019-07-08 13:45 cpefs -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 dtb -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 dtbo -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 2019-07-08 13:45 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2019-07-08 13:45 m9kefs1 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2019-07-08 13:45 m9kefs2 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 m9kefs3 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 misc -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 nad_fw -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 nad_refer -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 omr -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 param -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 persistent -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 product -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 radio -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 reserved2 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 2019-07-08 13:45 sec_efs -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 steady -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 system -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 up_param -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 userdata -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 vbmeta -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2019-07-08 13:45 vendor -> /dev/block/mmcblk0p26
Edit:
More detailed output from fdisk with start / end sector , size, name.:
a40:/system/xbin # fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 122142720 sectors, 2296M
Logical sector size: 512
Disk identifier (GUID): 52444e41-494f-2044-4d4d-43204449534b
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 122142686
Number Start (sector) End (sector) Size Name
1 8192 16383 4096K bota0
2 16384 32767 8192K bota1
3 32768 73727 20.0M efs
4 73728 114687 20.0M sec_efs
5 114688 131071 8192K cpefs
6 131072 147455 8192K bota2
7 147456 163839 8192K cm
8 163840 172031 4096K m9kefs1
9 172032 180223 4096K m9kefs2
10 180224 188415 4096K m9kefs3
11 188416 190463 1024K nad_refer
12 190464 206847 8192K param
13 206848 223231 8192K up_param
14 223232 227327 2048K misc
15 227328 301055 36.0M boot
16 301056 409599 53.0M recovery
17 409600 425983 8192K dtb
18 425984 442367 8192K dtbo
19 442368 534527 45.0M radio
20 534528 535551 512K persistent
21 535552 543743 4096K steady
22 543744 544767 512K vbmeta
23 544768 545791 512K bota3
24 545792 557055 5632K reserved2
25 557056 10633215 4920M system
26 10633216 11976703 656M vendor
27 11976704 12992511 496M product
28 12992512 13811711 400M cache
29 13811712 13914111 50.0M omr
30 13914112 13924351 5120K cp_debug
31 13924352 13965311 20.0M nad_fw
32 13965312 122132479 51.5G userdata
Could this be potentially helpful for the developers behind Magisk? I would do anything to see a fully functional root on the A40, but don't know how to help with it.
Thank you for being active! :good:
marekmeli said:
Could this be potentially helpful for the developers behind Magisk? I would do anything to see a fully functional root on the A40, but don't know how to help with it.
Thank you for being active! :good:
Click to expand...
Click to collapse
Not sure it's needed. I rooted my A40 with Magisk Canary and it worked fine for me by patching boot.img
No need to boot to recovery or anything like that.
The partition list was more meant like a reference if anyone wants to back up partitions after root or something like that.
Right now I'm working on a modded param.bin without that ugly "secured by knox" on bootlogo, and also remove the red boot warning text.
That's awesome that the canary version is stable and fully functional.
Are there any drawbacks? For example, there are often issues with Google Pay and Knox not working. If it all works, I will happily apply the canary Magisk!
marekmeli said:
That's awesome that the canary version is stable and fully functional.
Are there any drawbacks? For example, there are often issues with Google Pay and Knox not working. If it all works, I will happily apply the canary Magisk!
Click to expand...
Click to collapse
Not sure about google pay as I don't use it, and knox is basically screwed as soon as you flash any custom binary like patched boot or twrp. Samsung pass, secure folder etc won't work.
All I've tried is to open SHealth though, but it says unauthorized changes has been made to my device so it won't work.
It used to work on my A310 and I think it still does, but I guess they've tightened security for knox even more.
Play store came up as certified even with root, but Netflix can't be found anyway for some reason. Works fine to install from other places.
I never cared for knox features anyway so I don't mind the drawbacks.
Here's the boot logo mod I was talking about earlier.
Galaxy A40 [SM-A405FN] Bootlogo mod
tys0n said:
Not sure it's needed. I rooted my A40 with Magisk Canary and it worked fine for me by patching boot.img
No need to boot to recovery or anything like that.
The partition list was more meant like a reference if anyone wants to back up partitions after root or something like that.
Right now I'm working on a modded param.bin without that ugly "secured by knox" on bootlogo, and also remove the red boot warning text.
Click to expand...
Click to collapse
How to make a backup without TWRP? Any suggestions?
S Q 3 O P H said:
How to make a backup without TWRP? Any suggestions?
Click to expand...
Click to collapse
I guess easiest way would be to use something like titanium backup, swift backup or similar to backup/restore apps and app data.
Titanium backup and FlashFire not working on my phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
S Q 3 O P H said:
Titanium backup and FlashFire not working on my phone
Click to expand...
Click to collapse
I have no idea about flashfire as I've never used it myself. May be it's just outdated. No updates in almost two years, which I guess was when Chainfire sold SuperSU and stopped developing root apps etc.
Titanium on the other hand works for me. Make sure you have usb debug on, and you could also try to grant permissions for app before open it.
Samsungs Smart Switch app actaully does a really good job for backing up the Apps and stuff.
I just backup the android folder of the internal storage (for the data files of games etc)
Then after i need to do a fresh install i just need to restore via the Samsung app and copy back the folder
@Skolotaie I'll try. Thanks
Hiii has anyone tried to connect and eduroam wifi? Is the one that is in the universities. To connect to this wifi i need to change advanced settings in wifi section in the galaxy a40, but every time i try to change some setting the settigns app stop working. Can someone try to change for example EAP method? When I try that it stop working and I dont know what can i do.
Thanks
tys0n said:
Not sure it's needed. I rooted my A40 with Magisk Canary and it worked fine for me by patching boot.img
No need to boot to recovery or anything like that.
The partition list was more meant like a reference if anyone wants to back up partitions after root or something like that.
Right now I'm working on a modded param.bin without that ugly "secured by knox" on bootlogo, and also remove the red boot warning text.
Click to expand...
Click to collapse
Do you need to unlock bootloader or install a CustomRecovery for that? How does it works?