Related
I've seen a lot of stuff using 'dd' but nothing that uses that for backuping the entire phone.
When I connect my phone I see both the external SDcard and the internal and just to be sure to take the correct one I pull the external out,
unless you know by its size, can I use this: (this assumes that /dev/sdb is the internal SDcard)
Code:
dd if=/dev/sdb of=/some/place/phone.image bs=4096 conv=notrunc,noerror
and later use that for a total recovery?
I've done this for lots of my Linux systems even just to backup some partitions (but then sdbN...)
but never on a phone and since it's Linux based....
//B52
Of course you can backup using dd, I suggest though that you do partitions seperately since restoring a single image be problematic if possible since some partitions are hidden and writing to the bootloader partitions is not a good idea incase of problems
Here is a list of the partitions with names.
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
The ones I suggest backing up are:
EFS this is a must and the most important without it your phone could be unusable if the files become corrupt and you don't have a backup
DATAFS is user data
FACTORYFS is the system partition
HIDDEN if you are on Jelly Bean this adds to and extends the system partition
UMS is your internal sdcard (probably better ways to backup then a dd)
Even if you backup don't restore the SBL partitions since if something goes wrong it will screw your phone and they are not damaged if your phone boots at all if they get damaged you will be paying to get your phone jtaged
One thing though, since this is not under /dev/sdX, is it possible to use dd on these /dev/block/ ?
Never done that before and what is the difference between a block and a device?
So normally, nexus devices have easy partition names... For example, the /dev/block/platform/by-name directory contains things like system, boot, recovery, data, modem, efs, etc.. Well here is the result of "ls -al" of the partition directory on my nexus 9.
[email protected]_lte:/ # ls -al /dev/block/platform/sdhci-tegra.3/by-name
lrwxrwxrwx root root 2014-12-30 12:10 APP -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2014-12-30 12:10 CAC -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2014-12-30 12:10 CDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-12-30 12:10 DIA -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-12-30 12:10 DTB -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-12-30 12:10 EF1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-12-30 12:10 EF2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-12-30 12:10 EKS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-12-30 12:10 EXT -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-12-30 12:10 FST -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-12-30 12:10 GPT -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2014-12-30 12:10 KEY -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-12-30 12:10 LNX -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-12-30 12:10 MD1 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-12-30 12:10 MD2 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-12-30 12:10 MFG -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-12-30 12:10 MSC -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-12-30 12:10 NCT -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-12-30 12:10 OTA -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2014-12-30 12:10 PG1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-12-30 12:10 PST -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2014-12-30 12:10 RCA -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-12-30 12:10 RV1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-12-30 12:10 RV2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-12-30 12:10 RV3 -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2014-12-30 12:10 SER -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-12-30 12:10 SOS -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-12-30 12:10 SP1 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-12-30 12:10 TOS -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-12-30 12:10 UDA -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2014-12-30 12:10 VNR -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-12-30 12:10 WB0 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-12-30 12:10 WDM -> /dev/block/mmcblk0p7
My question is, which is which? How can i tell which is the recovery block, system block, recovery and so on? Is there a list of translations for these partition names? Thanks
Not sure what need you are trying to fulfill but read this http://www.all-things-android.com/content/review-android-partition-layout as a starter.
peterk-1 said:
Not sure what need you are trying to fulfill but read this http://www.all-things-android.com/content/review-android-partition-layout as a starter.
Click to expand...
Click to collapse
For example, nexus 5 has a symlinks like /dev/block/platform/msm_sdcc.1/by-name/boot that is linked to /dev/block/mmcblk0p19. Clearly this is the kernel block. Because its called "boot". Right? So, the nexus 9 is different from most other nexus devices. The by-name folder has 3 character names that dont really translate to "boot" or "system" or "recovery". It has names like "dia" and "vnr". I know that the "vnr" is the Vendor block. So which one is the "boot" block, is it "dia", or is it"svn". Do you understand what im asking? How in the heck is one supposed to figure out which block device is which???
bynarie said:
How in the heck is one supposed to figure out which block device is which???
Click to expand...
Click to collapse
The "clever ****" reply is "google" but I've found that many pages go silent on the key issue and and others are way over my head.
Some pointers:
Reboot your device and look at the dmesg log and :
Search "target=" (6 hits in 1 file)
\\CORSAIR\CorsairG\junk\dmesg.txt (6 hits)
Line 1077: <14>[ 5.168004] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/APP,target=/system,type=ext4)=0
Line 1080: <14>[ 5.172727] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/VNR,target=/vendor,type=ext4)=0
Line 1114: <14>[ 5.507472] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/CAC,target=/cache,type=ext4)=0
Line 1127: <14>[ 5.527126] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=f2fs)=-1
Line 1145: <14>[ 5.550663] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=ext4)=-1
Line 1488: <14>[ 111.676664] fs_mgr: __mount(source=/dev/block/dm-0,target=/data,type=f2fs)=0
http://newandroidbook.com/Articles/Nexus9.html - note "tegra" names and Nvidia Shield.
https://android.googlesource.com/device/htc/flounder/+/android-5.0.2_r1/fstab.flounder
thanks!
peterk-1 said:
The "clever ****" reply is "google" but I've found that many pages go silent on the key issue and and others are way over my head.
Some pointers:
Reboot your device and look at the dmesg log and :
Search "target=" (6 hits in 1 file)
\\CORSAIR\CorsairG\junk\dmesg.txt (6 hits)
Line 1077: <14>[ 5.168004] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/APP,target=/system,type=ext4)=0
Line 1080: <14>[ 5.172727] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/VNR,target=/vendor,type=ext4)=0
Line 1114: <14>[ 5.507472] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/CAC,target=/cache,type=ext4)=0
Line 1127: <14>[ 5.527126] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=f2fs)=-1
Line 1145: <14>[ 5.550663] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=ext4)=-1
Line 1488: <14>[ 111.676664] fs_mgr: __mount(source=/dev/block/dm-0,target=/data,type=f2fs)=0
http://newandroidbook.com/Articles/Nexus9.html - note "tegra" names and Nvidia Shield.
https://android.googlesource.com/device/htc/flounder/+/android-5.0.2_r1/fstab.flounder
Click to expand...
Click to collapse
Thanks!! That fstab flounder page is a really good starting list of exactly what i was looking for. {{Presses Thanks Button}}
Is it possible to delete some partitions like system image and resize data partition?
wizzardsk said:
Is it possible to delete some partitions like system image and resize data partition?
Click to expand...
Click to collapse
No, system image system is a partition with android system. Other partitions are too small for redesigning to make sense.
Vartom said:
No, system image system is a partition with android system. Other partitions are too small for redesigning to make sense.
Click to expand...
Click to collapse
I am not sure about the name, but there are 2 system partitions on nexus 9 that i have not seen on other devices.
wizzardsk said:
I am not sure about the name, but there are 2 system partitions on nexus 9 that i have not seen on other devices.
Click to expand...
Click to collapse
you are mistaken, he has one system partitions (APP).
What is this?
wizzardsk said:
What is this?
Click to expand...
Click to collapse
Same thing. One is a regular backup, one is to backup as an image (system.img) pick the way you want to backup.
So both system partitions are necessary?
Edit: i understand, so there is only 1 system partition
wizzardsk said:
So both system partitions are necessary?
Edit: i understand, so there is only 1 system partition
Click to expand...
Click to collapse
Yes there is only 1 system partition. TWRP is offering 2 ways to make a system backup, either a standard backup, or backup as an image.
Hi, I have bought a prototype z ultra, probably BROWN - the tech support said customers aren't allowed to have these, and there's no way to update it. Can I install any custom roms on it? Please, help me, I'm really despaired...
UPDATE:
I flashed cyanogenmod 10.2 on it, but it didn't recognize my sim card, the radio was off, mobile service not working.
Then I flashed the AOSB ROM, now the IMEI has gone lost. Before I made any changes I backed up that TA partiton, maybe that can help in some way? Then I unlocked the bootloader, and flashed the cyanogen.
Does someone know if it's safe to flash an ftf file on a prototype device?
dkanas said:
Hi, I have bought a prototype z ultra, probably BROWN - the tech support said customers aren't allowed to have these, and there's no way to update it. Can I install any custom roms on it? Please, help me, I'm really despaired...
UPDATE:
I flashed cyanogenmod 10.2 on it, but it didn't recognize my sim card, the radio was off, mobile service not working.
Then I flashed the AOSB ROM, now the IMEI has gone lost. Before I made any changes I backed up that TA partiton, maybe that can help in some way? Then I unlocked the bootloader, and flashed the cyanogen.
Does someone know if it's safe to flash an ftf file on a prototype device?
Click to expand...
Click to collapse
Was it on the latest firmware?
I thought that prototypes mostly couldn't unlock the BL, but then there as some on here that could...? confused...
blueether said:
Was it on the latest firmware?
I thought that prototypes mostly couldn't unlock the BL, but then there as some on here that could...? confused...
Click to expand...
Click to collapse
It was on some early software, 14.1.B.1.263, android 4.2.2. I couldn't update it with pc companion and the update center on the phone. The imei was beginning with 0044.
dkanas said:
It was on some early software, 14.1.B.1.263, android 4.2.2. I couldn't update it with pc companion and the update center on the phone. The imei was beginning with 0044.
Click to expand...
Click to collapse
restoring the correct, or even a new, FTF will bring back the imei.
the next issue is if flashtool will flash a new FTF, if it will then you can then use a 4.4.4 or 5.0 ROM hopefully
blueether said:
restoring the correct, or even a new, FTF will bring back the imei.
the next issue is if flashtool will flash a new FTF, if it will then you can then use a 4.4.4 or 5.0 ROM hopefully
Click to expand...
Click to collapse
Yes, i know. But I don't know if the partitions in this prototype match the production models partitions, there could be a difference, like in the gpe model. I don't want to brick this device, it's worth a half of the usual monthly salary in my country Does someone know what exactly is the difference between the regular and the gpe editions?
Update: I think I pulled out the partition layout from my prototype:
Code:
lrwxrwxrwx root root 1970-01-02 04:33 DDR -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:33 FOTAKernel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:33 LTALabel -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:33 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:33 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:33 alt_aboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:33 alt_dbi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:33 alt_rpm -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:33 alt_s1sbl -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:33 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:33 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:33 apps_log -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:33 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:33 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:33 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:33 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:33 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:33 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:33 ramdump -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:33 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:33 s1sbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:33 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:33 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:33 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:33 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 04:33 DDR -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:33 FOTAKernel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:33 LTALabel -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:33 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:33 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:33 alt_aboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:33 alt_dbi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:33 alt_rpm -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:33 alt_s1sbl -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:33 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:33 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:33 apps_log -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:33 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:33 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:33 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:33 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:33 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:33 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:33 ramdump -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:33 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:33 s1sbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:33 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:33 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:33 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:33 userdata -> /dev/block/mmcblk0p25
What further information can I provide you?
I flashed cyanogenmod 10.2 back, the IMEI is now back - but still no mobile service. Any ideas what could be wrong?
Settings -> About phone -> Status:
Network: unknown
Mobile network type: unknown
Service state: radio off
Roaming: no roaming
Mobile network state: disconnected
IMEI: 0044***********
IMEI SV: 17 (before messing with custom roms it was 01, or 11, can't recall now...)
Baseband version: 8974-AAAAANAZQ-10220006-17
Signal strenght: 2147483647 ASU 255 - that's weird.
Also, network mode is set on WCDMA preferred and I can't switch to another option - it immediately switches back.
Update:
Dial *#*#4636#*#* ---> phone info ---> there is a switch to turn on/off radio - >didn't work either
dkanas said:
I flashed cyanogenmod 10.2 back, the IMEI is now back - but still no mobile service. Any ideas what could be wrong?
Settings -> About phone -> Status:
Network: unknown
Mobile network type: unknown
Service state: radio off
Roaming: no roaming
Mobile network state: disconnected
IMEI: 0044***********
IMEI SV: 17 (before messing with custom roms it was 01, or 11, can't recall now...)
Baseband version: 8974-AAAAANAZQ-10220006-17
Signal strenght: 2147483647 ASU 255 - that's weird.
Also, network mode is set on WCDMA preferred and I can't switch to another option - it immediately switches back.
Update:
Dial *#*#4636#*#* ---> phone info ---> there is a switch to turn on/off radio - >didn't work either
Click to expand...
Click to collapse
I cant see that the partition layout would have changed can uou use adb shell to list the partitions?
Code:
adb shell
su
fdisk -l /dev/block/platform/msm_sdcc.1/mmcblk0
output should be:
Code:
Found valid GPT with protective MBR; using GPT
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 30535680 sectors, 2622M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 25 entries
First usable sector is 34, last usable sector is 30535646
Number Start (sector) End (sector) Size Code Name
1 256 4351 2048K 0700 TA
2 4352 5375 512K 0700 sbl1
3 5376 5887 256K 0700 s1sbl
4 5888 6015 65536 0700 dbi
5 6016 7039 512K 0700 aboot
6 7040 8063 512K 0700 rpm
7 8064 9087 512K 0700 tz
8 9088 10111 512K 0700 alt_sbl1
9 10112 10623 256K 0700 alt_s1sbl
10 10624 10751 65536 0700 alt_dbi
11 10752 11775 512K 0700 alt_aboot
12 11776 12799 512K 0700 alt_rpm
13 12800 13823 512K 0700 alt_tz
14 13824 54783 20.0M 0700 boot
15 54784 75263 10.0M 0700 ramdump
16 75264 108031 16.0M 0700 FOTAKernel
17 108032 108095 32768 0700 DDR
18 114688 147455 16.0M 0700 LTALabel
19 147456 150527 1536K 0700 modemst1
20 155648 158719 1536K 0700 modemst2
21 163840 166911 1536K 0700 fsg
22 172032 188415 8192K 0700 apps_log
23 188416 4947967 2324M 0700 system
24 4947968 5357567 200M 0700 cache
25 5357568 30535646 12.0G 0700 userdata
[email protected]:/ #
@blueether
Code:
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 15.6 GB, 15634268160 bytes
255 heads, 63 sectors/track, 1900 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/msm_sdcc.1/mmcblk0p1 1 1901 15267839+ ee EFI GPT
This is what I got
I see I have EFI, and not MBR, which doesn't sound good, am I right?
dkanas said:
@blueether
Code:
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 15.6 GB, 15634268160 bytes
255 heads, 63 sectors/track, 1900 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/msm_sdcc.1/mmcblk0p1 1 1901 15267839+ ee EFI GPT
This is what I got
I see I have EFI, and not MBR, which doesn't sound good, am I right?
Click to expand...
Click to collapse
not sure on the effect of EFi vs MBR
@blueether
I got this from parted: (sorry it's only a screenshot)
Althought diskinfo utility for android is showing the same values as your fdisk results
{
"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"
}
dkanas said:
@blueether
I got this from parted: (sorry it's only a screenshot)
Althought diskinfo utility for android is showing the same values as your fdisk results
Click to expand...
Click to collapse
@blueether
I flashed the newest FTF and it's working! I'll be grateful to death!
for partitions you can also use parted
Code:
adb shell
cd /dev/block
# you can use
Code:
ls
if you want to see which partitions are in this folder. mmcblk0 is the one were everyting in is stored, mmcblk1 is your sdcard.
Code:
parted mmcblk0
print
.
now you see your partitions, with parted you can also adjust them (Don't do that, you'll brick when you make a mistake)
for commando options in parted use
Code:
help
or
Code:
parted
(i forgot)
Anyway good that you fixed your phone, just wanted to share
Can brown devices receive OTA updates? Ever since I have my prototype XZL, I never received a single update from sony, the only updates I receive are those from apps installed via the playstore.
This partition apparently holds the IMEI (well on the Moto G 2013 it does) but I don't even see that it exists on this phone (xt1527). I can't seem to make a backup of it but the phone works so, is it even there or have they changed how it works?
bump, same issue
seems a bunch of us have this issue.
sad there seems to be no answer anywhere..
edit:
here is what i got listing partitions.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]_umts:/ $ su
[email protected]_umts:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-06-10 11:47 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-06-10 11:47 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-06-10 11:47 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-06-10 11:47 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-06-10 11:47 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-06-10 11:47 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-06-10 11:47 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-06-10 11:47 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-06-10 11:47 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-06-10 11:47 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-06-10 11:47 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-06-10 11:47 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-06-10 11:47 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-06-10 11:47 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-06-10 11:47 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-06-10 11:47 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-06-10 11:47 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-06-10 11:47 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-06-10 11:47 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-06-10 11:47 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-06-10 11:47 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-06-10 11:47 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-06-10 11:47 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-06-10 11:47 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-06-10 11:47 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-06-10 11:47 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-06-10 11:47 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-06-10 11:47 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-06-10 11:47 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-06-10 11:47 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-06-10 11:47 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-06-10 11:47 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-06-10 11:47 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-06-10 11:47 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-06-10 11:47 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-06-10 11:47 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-06-10 11:47 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-06-10 11:47 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-06-10 11:47 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-06-10 11:47 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-06-10 11:47 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-06-10 11:47 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-06-10 11:47 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-06-10 11:47 utagsBackup -> /dev/block/mmcblk0p17
[email protected]_umts:/ #
Not up to speed on this device yet but it seems to me that if you know where the PDS partition is from a terminal you should be able to use a form like:
dd if=/dev/block/mmcblk??? of=pds.img
provided your current working directory has enough room in it to hold the .img file
conductive said:
Not up to speed on this device yet but it seems to me that if you know where the PDS partition is from a terminal you should be able to use a form like:
dd if=/dev/block/mmcblk??? of=pds.img
provided your current working directory has enough room in it to hold the .img file
Click to expand...
Click to collapse
on another phone it's mmcblk12 (i have been doing a LOT of searching on this)
i looked at the root folder on my phone and i see a shortcut to "pds"
when i open it it's empty.
i have some experience with Linux but i am no pro and it's been a while for my nix activity.
and i have almost no experience with Android.
i am good with computer stuff though. cracking, coding reversing, graphics etc.
i love modding everything i can.
i say that to give a bit of context to this..
if anyone else has any idea or leads on what i can do or where to look i am all ears.
i posted that partition command because i found it on Google
and i remember using it (ls) before trouble shooting driver issues on Linux in the past.
you guys will notice the console log i posted does not list a pds partition by-name..
is it because it's not mounted maybe ? or is it using a different name on this phone ?
i'd love to try and update to 5.1 (from 5.0..2) on my Telus XT1527 but i think it's time i make a PDS backup before i carry on any further.. so far i have installed a custom kernel and TWRP + root.
So i can't continue until i figure out a way to back that stuff up (irresponsible otherwise i think)
Based on this post http://forum.xda-developers.com/showthread.php?t=1138220 the OS uses /dev/block/mmcblk0p3 and it was dumped to the /tmp directory.
from here you can use dd to flash it to an sd card where you can read it to see if it has pds information. You can also use (mount -a) to mount all partitions and do another ls -l
conductive said:
Based on this post http://forum.xda-developers.com/showthread.php?t=1138220 the OS uses /dev/block/mmcblk0p3 and it was dumped to the /tmp directory.
from here you can use dd to flash it to an sd card where you can read it to see if it has pds information. You can also use (mount -a) to mount all partitions and do another ls -l
Click to expand...
Click to collapse
That says Atrix though and on another posting i found it was mmcblk0p12
If you look at the log i posted earlier that number mmcblk0p3 is mapped to DDR
I have been dumping the partitions and checking them (if the file size is roughly correct)
I heard it was suppose to be about 8mb as an .img on another device.
and i have one downloaded as an image and extracted (some other guys data)
so if i find the files on my phone i think i can match them to my downloaded files.
i also got a windows tool to extract the images ready..
One last thing i said i seen a shortcut to "pds" on the filesystem of my Telus XT1527
so i take it that it's there just that i can't see it or something.
I'm basically poking around in the dark LOL
edit:
oh and i seen on other phones that pds partition can be backed up with TWRP.
The TWRP i have installed does not show it for me (i am using Squid's TWRP)
The partitions are probably associated with the OS version and not the hardware so you should probably compare your version to a similar version.
If you can find fstab file you should be able to (cat fstab) and see what the partitions are mounted as.
The partition should be mounted or else your device will not work.
I've modded fstab on linux before but i am not finding it i think on the XT1527
found a couple with "fstab" in the title and it don't say much..
just one line about mounting the sdcard.
Thanks but i am lost.. i wonder how it's created because it's prob not files in the Firmware package right ?
So then i'd have to assume the contents of PDS would be created on the phones first boot maybe.
i don't know what else to do really i am going around in circles ..i might just say screw it and give up.
too bad guys here who DO have the ability to find it can't help
100% of Moto-E users seem to carry on flashing their phones with out it
so i take it backing up the PDS is pointless ?
Just kind of dumb i see tutorials on how to do it all over but no one can claim it actually works LOL
If you google it you will see what i am saying (people tell you to you to do it becuase it's sooooo important..
then it doesn't work ahahaha
thanks for your help conductive.
edit:
Oh and guys.. i tried to do this because... Q13:
http://forum.xda-developers.com/moto-e-2015/help/faq-frequently-questions-moto-e-2015-t3044929
The stickied topic here tells us all how to do it.
..but did anyone at all bother to verify it actually works ?
Ok so i think i got it.. sort of.
I installed "Root Explorer Pro" and when i opened it this time it showed files/folders.
I then selected .zip it up and copied it manually to my sdcard then to my PC.
I have been hex viewing the contents with UltraEdit and the files contain data.
I also compared to a pds dump from an Atrix and they are some what similar.
I did see a reference in one of the root config files about the pds partition though..
I can't recall which file it was but it said something about
setting the dummy directory "pds" as persistent.
I don't know what is going on but i got the content off the phone i think.
edit:
Here is what the root of that folder looked like (folder names)
Code:
.bt_nv.bin
batt_health
bt
camera
data
factory
lost+found
public
security
WCNSS_wlan_dictionary.dat
wifi
wmdrm
First of all credit for this goes to arpruss - https://github.com/arpruss/cve2019-2215-3.18.
Just download and install the apk from here https://github.com/arpruss/cve2019-2215-3.18/raw/master/release/app-release.apk
Then open the app and click install. You are done
WARNING: once you have a root shell do not modify system files as that will result in a bricked system until we figure out a way to unlock the bootloader.
Permanent root suggestion
Hi, guys, after this great achievement, permanent root might be desirable.
I'll tell you a story...I've always loved qwerty phones and one of the rare phones I've always wanted is NEC Terrain (distributed by AT&T). Unfortunately AT&T has locked it to its network and I found no working solution for unlocking it for other SIM cards (please let me know if you know of a working SIM unlock service!), BUT I've always wanted to gain permanent root privileges for this device. The story of NEC Terrain is very similar to Palm Phone PVG100 (Pepito):
NEC Terrain was released by AT&T and the bootloader locked, while Palm Phone PVG100 (Pepito) was released by Verizon and the bootloader locked...
NEC company is not on the market anymore and Palm company is in a similar condition, which makes contacts with the company difficult and the hope of updates to be released unlikely...
Code for NEC Terrain was developed by enthusiasts (https://github.com/android-rooting-tools/android_run_root_shell) similar to arpruss code for Palm Phone PVG100 (Pepito) (https://github.com/arpruss/cve2019-2215-3.18)...
Temporary root solution for NEC Terrain was achieved (https://github.com/x29a/nec_terrain_root) like root solution for Palm Phone PVG100 (Pepito) was achieved (https://github.com/arpruss/cve2019-2215-3.18/tree/master/release)...
For NEC Terrain a creative permanent root solution was developed by x29a (https://github.com/x29a/nec_terrain_root/blob/master/terroot/README.md) and now my suggestion is that we might want to follow his steps for Palm Phone PVG100 (Pepito)!
Here are the details of "HOW ALEX-KAS DID IT"!:
https://forum.xda-developers.com/showpost.php?p=61542922&postcount=186
Does anyone of you find this path convincing?
greatjack1 said:
First of all credit for this goes to arpruss - https://github.com/arpruss/cve2019-2215-3.18.
Just download and install the apk from here https://github.com/arpruss/cve2019-2215-3.18/raw/master/release/app-release.apk
Then open the app and click install. You are done
WARNING: once you have a root shell do not modify system files as that will result in a bricked system until we figure out a way to unlock the bootloader.
Click to expand...
Click to collapse
Hi there, please have a look at the attached pictures and let me know what might be wrong...I mean, what is the app-release.apk file you added to your post supposed to be doing?
And what exactly does the "Install on boot" optional tickbox do?
StormSeeker1 said:
Hi there, please have a look at the attached pictures and let me know what might be wrong...I mean, what is the app-release.apk file you added to your post supposed to be doing?
And what exactly does the "Install on boot" optional tickbox do?
Click to expand...
Click to collapse
Really wierd, it worked for me. Let me look a little deeper
greatjack1 said:
Really wierd, it worked for me. Let me look a little deeper
Click to expand...
Click to collapse
Do I have to run or install that .apk AFTER having spawned the root privileged shell or in substitution for it?
What is it supposed to be doing?
---------- Post added at 11:14 PM ---------- Previous post was at 11:11 PM ----------
greatjack1 said:
First of all credit for this goes to arpruss - https://github.com/arpruss/cve2019-2215-3.18.
Just download and install the apk from here https://github.com/arpruss/cve2019-2215-3.18/raw/master/release/app-release.apk
Then open the app and click install. You are done
WARNING: once you have a root shell do not modify system files as that will result in a bricked system until we figure out a way to unlock the bootloader.
Click to expand...
Click to collapse
May I ask you to please put the list of the commands needed for spawning the root privileged shell back in your tutorial? I think it helps people a lot
Oh, and, people, do you know why, when I have the root shell, I'm not able to get the following command executed?
setprop sys.usb.config diag,adb
I get the following response:
setprop: failed to set property 'sys.usb.config' to 'diag,adb'
Why is there three threads about this?
Mattzees said:
Why is there three threads about this?
Click to expand...
Click to collapse
People started them independently and each one is on a specific thing, but all things are connected (there are interconnections and it's not always clear if rooting helps unlocking bootloader or if unlocking bootloader helps permanently rooting or if for compiling custom recoveries (TWRP) one needs root or bootloader unlocking), so these threads have a reason to exist and there are overlaps, but feel free to let people know if you want to merge something!
StormSeeker1 said:
Do I have to run or install that .apk AFTER having spawned the root privileged shell or in substitution for it?
What is it supposed to be doing?
---------- Post added at 11:14 PM ---------- Previous post was at 11:11 PM ----------
May I ask you to please put the list of the commands needed for spawning the root privileged shell back in your tutorial? I think it helps people a lot
Oh, and, people, do you know why, when I have the root shell, I'm not able to get the following command executed?
setprop sys.usb.config diag,adb
I get the following response:
setprop: failed to set property 'sys.usb.config' to 'diag,adb'
Click to expand...
Click to collapse
try dial this code
Code:
###2324#
freezex said:
try dial this code
Code:
###2324#
Click to expand...
Click to collapse
IT WORKS! WHERE DID YOU FIND THIS CODE (AND OTHERS), freezex?! (I had tried lots of them from other phones with no success)
StormSeeker1 said:
IT WORKS! WHERE DID YOU FIND THIS CODE (AND OTHERS), freezex?! (I had tried lots of them from other phones with no success)
Click to expand...
Click to collapse
Guys, I was finally able to read Non-Volatile memory values using freezex's secret code for enable debugging, installing the USB drivers that popup when you choose on the phone the USB option "Drivers CD-ROM" after connecting it to the PC, using "QPST Configuration" tool and "QXDM" tool.
I tried to replace the initial value "2251799813754906" with "68787503589", which, according to my understanding, should cover all Italian LTE bands (please confirm and let me know if there is a way to reverse lookup code 2251799813754906 to see what bands are included inside of it).
The value I entered persisted after reboot and I was able to read the new value with QXDM.
Unfortunately I'm still seeing only a 3G icon on the notification bar...any idea on the cause of this behavior, guys?
A lot of values are there, can you please let me know if changing any of those values might help unlocking the bootloader?
PAY ATTENTION: After having enabled Diagnostic Mode (with freezex's secret code), Windows Device Manager recognizes the phone as "ALCATEL HS-USB Diagnostics 903A (COM6)"; does the fact that it comes from Alcatel give us any hint on what to do?
Also, people, do you find any free space not used by any partition to try NEC Terrain trick?
Here's some information I took from my PVG100:
127|Pepito:/data/local/tmp # df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1358904 2764 1356140 1% /
tmpfs 1439680 752 1438928 1% /dev
/dev/block/dm-0 2999516 2218028 781488 74% /system
/dev/block/dm-1 1499760 881984 617776 59% /vendor
tmpfs 1439680 0 1439680 0% /mnt
/dev/block/mmcblk0p52 1998672 6156 1992516 1% /fotadata
/dev/block/mmcblk0p29 237536 400 237136 1% /cache
/dev/block/mmcblk0p12 12016 8448 3568 71% /dsp
/dev/block/mmcblk0p1 85968 81600 4368 95% /firmware
/dev/block/mmcblk0p30 28144 480 27664 2% /persist
/dev/block/dm-2 21667804 7631300 14036504 36% /data
/data/media 21667804 7631300 14036504 36% /mnt/runtime/default/emulated
See also this output:
Pepito:/dev/block/platform/soc/7824900.sdhci/by-name # ls -l
total 0
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 DDR -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 aboot -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 abootbak -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 apdp -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 boot -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 cache -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 cmnlib -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 cmnlib64 -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 cmnlib64bak -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 cmnlibbak -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 config -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 devinfo -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 dip -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 dpo -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 dsp -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 fotadata -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 fsc -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 keymaster -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 keymasterbak -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 keystore -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 limits -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 logdump -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 mcfg -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 mdtp -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 mota -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 msadp -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 oem -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 persist -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 redbend -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 sbl1 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 sbl1bak -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 sec -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 simlock -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 splash -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 ssd -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 syscfg -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 system -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 traceability -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 tunning -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 userdata -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 vendor -> /dev/block/mmcblk0p28
I was able to push the "parted" utility to the phone, after having found a version already compiled for ARMv8 processors (and the Qualcomm SnapDragon 435 inside the PVG100 is an ARMv8).
This is the output I get:
127|Pepito:/data/local/tmp # ./parted /dev/block/mmcblk0 print
Model: MMC GD6BMB (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 67.1MB 155MB 88.1MB fat16 modem msftdata
2 201MB 201MB 1024B fsc
3 201MB 201MB 8192B ssd
4 201MB 202MB 524kB sbl1
5 202MB 202MB 524kB sbl1bak msftdata
6 202MB 203MB 524kB rpm
7 203MB 203MB 524kB rpmbak msftdata
8 203MB 206MB 2097kB tz
9 206MB 208MB 2097kB tzbak msftdata
10 208MB 208MB 262kB devcfg
11 208MB 208MB 262kB devcfgbak
12 208MB 225MB 16.8MB ext4 dsp msftdata
13 225MB 227MB 1573kB modemst1
14 227MB 228MB 1573kB modemst2
15 268MB 268MB 32.8kB DDR
16 268MB 270MB 1573kB fsg
17 270MB 270MB 16.4kB sec
18 270MB 272MB 1573kB tunning
19 272MB 273MB 1049kB traceability
20 336MB 337MB 1049kB simlock
21 337MB 340MB 3170kB redbend msftdata
22 340MB 351MB 11.5MB splash
23 403MB 404MB 1049kB aboot
24 404MB 405MB 1049kB abootbak msftdata
25 405MB 472MB 67.1MB boot
26 472MB 539MB 67.1MB recovery
27 539MB 3760MB 3221MB ext4 system
28 3760MB 5371MB 1611MB ext4 vendor
29 5436MB 5704MB 268MB ext4 cache
30 5704MB 5738MB 33.6MB ext4 persist
31 5771MB 5772MB 1049kB devinfo
32 5838MB 5840MB 1049kB misc
33 5840MB 5840MB 524kB keystore
34 5840MB 5840MB 32.8kB config
35 5840MB 6109MB 268MB oem
36 6174MB 6174MB 32.8kB limits
37 6241MB 6242MB 524kB mota msftdata
38 6242MB 6243MB 1049kB dip
39 6243MB 6276MB 33.6MB mdtp
40 6276MB 6277MB 524kB syscfg
41 6277MB 6281MB 4194kB mcfg msftdata
42 6308MB 6309MB 1049kB cmnlib
43 6309MB 6310MB 1049kB cmnlibbak
44 6310MB 6311MB 1049kB cmnlib64
45 6311MB 6312MB 1049kB cmnlib64bak
46 6312MB 6313MB 1049kB keymaster
47 6313MB 6315MB 1049kB keymasterbak
48 6375MB 6376MB 262kB apdp
49 6376MB 6376MB 262kB msadp
50 6376MB 6376MB 8192B dpo
51 6376MB 6443MB 67.1MB logdump
52 6443MB 8590MB 2147MB ext4 fotadata msftdata
53 8590MB 31.3GB 22.7GB userdata
StormSeeker1 said:
Do I have to run or install that .apk AFTER having spawned the root privileged shell or in substitution for it?
What is it supposed to be doing?
---------- Post added at 11:14 PM ---------- Previous post was at 11:11 PM ----------
May I ask you to please put the list of the commands needed for spawning the root privileged shell back in your tutorial? I think it helps people a lot
Oh, and, people, do you know why, when I have the root shell, I'm not able to get the following command executed?
setprop sys.usb.config diag,adb
I get the following response:
setprop: failed to set property 'sys.usb.config' to 'diag,adb'
Click to expand...
Click to collapse
StormSeeker1 said:
IT WORKS! WHERE DID YOU FIND THIS CODE (AND OTHERS), freezex?! (I had tried lots of them from other phones with no success)
Click to expand...
Click to collapse
I was googling something like "alcatel diagnostic code",and found it in this funny page. LoL
http://huaweisolarinverter.com/q16el/zav.php?juc=alcatel-6055u
freezex said:
I was googling something like "alcatel diagnostic code",and found it in this funny page. LoL
http://huaweisolarinverter.com/q16el/zav.php?juc=alcatel-6055u
Click to expand...
Click to collapse
Well...congratulations
Folks, might this be helpful?
https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-chains.html
https://www.emergingdefense.com/blog/2019/5/20/how-to-put-a-qualcomm-phone-into-edl-mode
People, I had an idea! Look here:
https://www.verizonwireless.com/support/knowledge-base-200052/
From the previous page, it looks like Verizon allows for enabling fastboot!
I tried chatting with them or getting a contact, but it looks like they require you to be their customer to listen to you. Can you find a way to contact them and kindly ask for a fastboot enable solution for Palm PVG100? Is there any user of this forum able to help us (possibly somebody who is currently using Verizon as a provider)?
https://www.verizonwireless.com/support/contact-us/
All those GitHub links are dead. Please advise.
Also what is the root.zip with a file names root in it? Is that the APK or something else (no extension).
Thanks again. Very exciting stuff.
greatjack1 said:
First of all credit for this goes to arpruss - https://github.com/arpruss/cve2019-2215-3.18.
Just download and install the apk from here https://github.com/arpruss/cve2019-2215-3.18/raw/master/release/app-release.apk
Then open the app and click install. You are done
WARNING: once you have a root shell do not modify system files as that will result in a bricked system until we figure out a way to unlock the bootloader.
Click to expand...
Click to collapse
bensdeals said:
All those GitHub links are dead. Please advise.
Also what is the root.zip with a file names root in it? Is that the APK or something else (no extension).
Thanks again. Very exciting stuff.
Click to expand...
Click to collapse
Hi, bensdeals
unfortunately arpruss removed his repository from github:
https://forum.xda-developers.com/showpost.php?p=80702567&postcount=164
Luckily another user, which I thank a lot (ilikenwf) has a mirror of what has been done so far:
https://forum.xda-developers.com/showpost.php?p=80702567&postcount=167
The root.zip file contains a file with no extension, which is not an apk package, but an executable compiled for the architecture of the CPU and for the operating system that PVG100 has.
Here's how to run the "root" file inside the package:
On windows open a CMD shell in the folder where "adb.exe" and "root" files are, then:
adb push root /data/local/tmp
adb shell
chmod +x /data/local/tmp/root
cd /data/local/tmp
./root
See below what you get (notice the # sign, meaning root user as opposed to the $, meaning regular user):
adb shell
Pepito:/ $ chmod +x /data/local/tmp/root
Pepito:/ $ cd /data/local/tmp
Pepito:/data/local/tmp $ ./root
MAIN: detected kernel version 3
MAIN: starting exploit for devices with waitqueue at 0x98
PARENT: soon will be calling WRITEV
CHILD: Doing EPOLL_CTL_DEL.
CHILD: Finished EPOLL_CTL_DEL.
CHILD: initial portion length 0x12000
CHILD: task_struct_ptr = 0xffffffc059c51980
CHILD: clobbering with extra leak structures
PARENT: clobbering at 0xffffffc03d8db4a0
CHILD: Doing EPOLL_CTL_DEL.
CHILD: Finished EPOLL_CTL_DEL.
CHILD: wrote 69688
PARENT: readv returns 69688, expected 69688
PARENT: clobbering test passed
CHILD: clobbered
PARENT: writev() returns 0x13008
PARENT: Reading leaked data
CHILD: task_struct_ptr = 0xffffffc066664000
CHILD: Finished write to FIFO.
PARENT: leaking successful
MAIN: task_struct_ptr = ffffffc059c51980
MAIN: stack = ffffffc066664000
MAIN: Clobbering addr_limit
PARENT: clobbering at 0xffffffc066664008
CHILD: Doing EPOLL_CTL_DEL.
CHILD: Finished EPOLL_CTL_DEL.
CHILD: wrote 69648
PARENT: readv returns 69648, expected 69648
PARENT: clobbering test passed
MAIN: thread_info = 0xffffffc066664000
MAIN: should have stable kernel R/W now
MAIN: searching for cred offset in task_struct
MAIN: search_base = ffffffc000000000
MAIN: searching for selinux_enforcing
MAIN: setting root credentials with cred offset 670
MAIN: UID = 0
MAIN: enabling capabilities
MAIN: SECCOMP status 0
MAIN: disabled selinux enforcing
MAIN: no whitelist, so all callers are welcome
MAIN: root privileges ready
MAIN: popping out root shell
Pepito:/data/local/tmp #
Does this help?
Thanks, that does work in achieving root. Question, you indicated modifying any system files would brick the device. Without an app to grant root access to other apps (supersu), then there isn't much we can do. Have you attempted to do anything else besides running this script?
... About your unlocking bands via editing nv data. Once you have root you can use the Network Signal Guru app to see if you have unlocked the bands. This doesn't necessarily mean those bands will work.
bensdeals said:
Thanks, that does work in achieving root. Question, you indicated modifying any system files would brick the device. Without an app to grant root access to other apps (supersu), then there isn't much we can do. Have you attempted to do anything else besides running this script?
... About your unlocking bands via editing nv data. Once you have root you can use the Network Signal Guru app to see if you have unlocked the bands. This doesn't necessarily mean those bands will work.
Click to expand...
Click to collapse
I'll have a look at the Network Signal Guru app, thanks. About that warning, it wasn't me writing it...and I'm a bit worried of trying modifying the system without having any ROM to reflash in case of brick (nor a working way to perform the flashing)...is there anyone who can help us with this?
I've just installed the Network Signal Guru app...but it looks like it requires root privileges, do you confirm? Also, how should I use it to get the LTE bands I'm using? Is it part of the free functionalities? What are paid functionalities?
It gives you the ability to disable active bands.. what it will do for you is tell you if you did successfully unlock and enable a band. You can then disable all the other bands with th tool. All via the free version with root.
Not sure if you can run it after rooting from the adb shell with root or what is consider problematic towards bricking your device.
StormSeeker1 said:
I'll have a look at the Network Signal Guru app, thanks. About that warning, it wasn't me writing it...and I'm a bit worried of trying modifying the system without having any ROM to reflash in case of brick (nor a working way to perform the flashing)...is there anyone who can help us with this?
I've just installed the Network Signal Guru app...but it looks like it requires root privileges, do you confirm? Also, how should I use it to get the LTE bands I'm using? Is it part of the free functionalities? What are paid functionalities?
Click to expand...
Click to collapse
StormSeeker1 said:
Well...congratulations
Folks, might this be helpful?
https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-chains.html
https://www.emergingdefense.com/blog/2019/5/20/how-to-put-a-qualcomm-phone-into-edl-mode
People, I had an idea! Look here:
https://www.verizonwireless.com/support/knowledge-base-200052/
From the previous page, it looks like Verizon allows for enabling fastboot!
I tried chatting with them or getting a contact, but it looks like they require you to be their customer to listen to you. Can you find a way to contact them and kindly ask for a fastboot enable solution for Palm PVG100? Is there any user of this forum able to help us (possibly somebody who is currently using Verizon as a provider)?
https://www.verizonwireless.com/support/contact-us/
Click to expand...
Click to collapse
The context of that fast boot was an older Qualcomm feature which put your phone into a hibernation state so that it would boot quicker it isn't releated to the bootloader fastboot. Also to answer your question about the alcatel driver that is just what windows picks the driver to be by default when it sees one of the many qualcomm debug modes..
deadman96385 said:
The context of that fast boot was an older Qualcomm feature which put your phone into a hibernation state so that it would boot quicker it isn't releated to the bootloader fastboot. Also to answer your question about the alcatel driver that is just what windows picks the driver to be by default when it sees one of the many qualcomm debug modes..
Click to expand...
Click to collapse
Thank you for clarifying; anyway, about the drivers, when you set the USB mode on the phone after connecting it to the PC, you have the option to connect it as a virtual CD drive, containing the drivers, so drivers (I don't know which ones) come from the phone itself (maybe this is unusual, but that read-only emulated CD partition exists on this phone).
StormSeeker1 said:
Thank you for clarifying; anyway, about the drivers, when you set the USB mode on the phone after connecting it to the PC, you have the option to connect it as a virtual CD drive, containing the drivers, so drivers (I don't know which ones) come from the phone itself (maybe this is unusual, but that read-only emulated CD partition exists on this phone).
Click to expand...
Click to collapse
That is used fairly often normally it's a setup exe to install them. Which depending on if it contains a driver for the mode your in it would override the Alcatel branded one which in reality is just there because both Alcatel and palm are TCL brands now.