[DISCUSSION][SOLVED] Let's use all 4gb of memory! - G2 and Desire Z General

Edit: See Wiki for information on why this can not be accomplished: "summary: 2gb have stuff. other 2gb make phone faster. phone have more faster ram. Phone go faster." (Thanks wrsg)
First, I feel this needs to be in the development section because it's most likely going to require some commands/.zip/custom ROM/whatever to actually be able to use that other 2gb of memory we don't see.
Correct me if I'm wrong but from my understanding, that other 2gb of memory has a backup of STOCK G2 Software (OS/Recovery/etc) and reserved space for updates. Basically meaning memory that's only touched by an OTA or ... gingerbread when that drops.
How would we go about "unlocking" that other half of internal memory? It could be used for apps or possibly even mountable storage (if possible...)
I'm sure this is already a work in progress and I have nothing to offer in the endeavor. Just opening the door for someone to walk through.
If a mod believes this to be in the wrong section, please feel free to move it.
Sent from my T-Mobile G2 using XDA App

philosophics said:
First, I feel this needs to be in the development section because it's most likely going to require some commands/.zip/custom ROM/whatever to actually be able to use that other 2gb of memory we don't see.
Correct me if I'm wrong but from my understanding, that other 2gb of memory has a backup of STOCK G2 Software (OS/Recovery/etc) and reserved space for updates. Basically meaning memory that's only touched by an OTA or ... gingerbread when that drops.
How would we go about "unlocking" that other half of internal memory? It could be used for apps or possibly even mountable storage (if possible...)
I'm sure this is already a work in progress and I have nothing to offer in the endeavor. Just opening the door for someone to walk through.
If a mod believes this to be in the wrong section, please feel free to move it.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
what do you propose?

I believe this thread will be where brains come together. As stated above, I have nothing to offer in the endeavor. Just opening a door for someone to walk through.
When something comes up that works, I will post it in the OP and change the thread title...
Sent from my T-Mobile G2 using XDA App

I think we are getting ahead of ourselves...we need a base/stock rom with su/busybox installed badly! I know the soft bricks are already happening and no one has anything to revert to (that isn't insanely tedious). Besides, nandroid/titanium backup can't fix it every time. I hope someone is working on that first. I'm sure people are looking into accessing the total rom space but if its just partitioned that way... there may be no easy solution. Or at least one that isn't dangerous...

Isn't this supposedly HTC and T-mobile's job!?!
Aren't they supposed to acknowledge this problem already?!
Up until now I have seen NO official words from either HTC or T-mobile. what's up with that? are these guys playing the silence game?

HA!
I just posted same question in "dev question" sticky which has almost no dev questions in it. I believe their may be a barrier to entry to our other 1.9 gigs and that is the actual architecture that our g2 radios live, on the eemc.
Pls feel free to correct me if I am wrong here.

i feel as if the other 2 gigs are partitions that are used for data and cache; jus a thought

s0xpan said:
i feel as if the other 2 gigs are partitions that are used for data and cache; jus a thought
Click to expand...
Click to collapse
all told system, data, and cache 1 gig would be a huge amount. still leaving an unaccounted gig
thats not even taking into account the 512 of rom

haensgn said:
all told system, data, and cache 1 gig would be a huge amount. still leaving an unaccounted gig
thats not even taking into account the 512 of rom
Click to expand...
Click to collapse
true this is true

philosophics said:
Correct me if I'm wrong but from my understanding, that other 2gb of memory has a backup of STOCK G2 Software (OS/Recovery/etc) and reserved space for updates. Basically meaning memory that's only touched by an OTA or ... gingerbread when that drops.
Click to expand...
Click to collapse
I don't think that's been proved, has it, it's just speculation ? i.e. what that extra space is for ?
If anyone has links to proof then of course I'd be very interested, and apologise if I'm wrong.
The "missing" memory might even be unintentional and/or a bug, from what I've seen.

well sir speculation is a part of this whole "think tank" process
nothing needs proof. although if you have any documentation...
From what i saw going through the emmc in 4kbits of code at a time, done by the rooting team. it seems to be part of the architecture but i am waiting for wiser ppl whom have physically cracked this puppy open.

For anyone interested in specifics, you can do some reading here
I believe what you are referring to is the space beyond mmcblk0p28 (on the G2) which begins at block 264551 and ends at block 1048577

reukiodo said:
For anyone interested in specifics, you can do some reading here
Click to expand...
Click to collapse
and also at http://tjworld.net/wiki/Android/HTC/Vision/InstallingCustomOperatingSystem

Though, interestingly I get something a little different when I fdisk -l mmcblk0:
Code:
# busybox fdisk -l /dev/block/mmcblk0
busybox fdisk -l /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk mmcblk0: 2256 MB, 2256535552 bytes
1 heads, 16 sectors/track, 275456 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
mmcblk0p1 * 1 63 500 4d Unknown
Partition 1 does not end on cylinder boundary
mmcblk0p2 63 71 64 45 Unknown
Partition 2 does not end on cylinder boundary
mmcblk0p3 71 634 4500 46 Unknown
Partition 3 does not end on cylinder boundary
mmcblk0p4 634 1048577 8383544 5 Extended
Partition 4 does not end on cylinder boundary
mmcblk0p5 634 4384 30000 49 Unknown
mmcblk0p6 4384 5946 12500 50 Unknown
mmcblk0p7 5946 6202 2048 51 Unknown
mmcblk0p8 6202 6586 3072 52 Unknown
mmcblk0p9 6586 6842 2048 53 Unknown
mmcblk0p10 6842 6970 1024 54 Unknown
mmcblk0p11 6971 7098 1024 56 Unknown
mmcblk0p12 7099 8192 8751+ 55 Unknown
mmcblk0p13 8193 8577 3072 4a Unknown
mmcblk0p14 8577 8961 3072 4b Unknown
mmcblk0p15 8961 9089 1024 74 Unknown
mmcblk0p16 9089 10208 8957+ 75 Unknown
mmcblk0p17 10209 10240 256 76 Unknown
mmcblk0p18 10241 10369 1024 47 Unknown
mmcblk0p19 10369 10497 1024 34 Unknown
mmcblk0p20 10497 10657 1280 36 Unknown
mmcblk0p21 10657 11744 8701 71 Unknown
mmcblk0p22 11744 12256 4096 48 Unknown
mmcblk0p23 12257 12288 256 73 Unknown
mmcblk0p24 12289 12321 256 31 Unknown
mmcblk0p25 12321 65536 425726+ 83 Linux
mmcblk0p26 65537 235777 1361920+ 83 Linux
mmcblk0p27 235777 261991 209715+ 83 Linux
mmcblk0p28 261991 264551 20480 19 Unknown
mmcblk0p29 634 4384 30000 49 Unknown
mmcblk0p30 4384 5946 12500 50 Unknown
mmcblk0p31 5946 6202 2048 51 Unknown
mmcblk0p32 6202 6586 3072 52 Unknown
mmcblk0p33 6586 6842 2048 53 Unknown
mmcblk0p34 6842 6970 1024 54 Unknown
mmcblk0p35 6971 7098 1024 56 Unknown
mmcblk0p36 7099 8192 8751+ 55 Unknown
mmcblk0p37 8193 8577 3072 4a Unknown
mmcblk0p38 8577 8961 3072 4b Unknown
mmcblk0p39 8961 9089 1024 74 Unknown
mmcblk0p40 9089 10208 8957+ 75 Unknown
mmcblk0p41 10209 10240 256 76 Unknown
mmcblk0p42 10241 10369 1024 47 Unknown
mmcblk0p43 10369 10497 1024 34 Unknown
mmcblk0p44 10497 10657 1280 36 Unknown
mmcblk0p45 10657 11744 8701 71 Unknown
mmcblk0p46 11744 12256 4096 48 Unknown
mmcblk0p47 12257 12288 256 73 Unknown
mmcblk0p48 12289 12321 256 31 Unknown
mmcblk0p49 12321 65536 425726+ 83 Linux
mmcblk0p50 65537 235777 1361920+ 83 Linux
mmcblk0p51 235777 261991 209715+ 83 Linux
mmcblk0p52 261991 264551 20480 19 Unknown
mmcblk0p53 634 4384 30000 49 Unknown
mmcblk0p54 4384 5946 12500 50 Unknown
mmcblk0p55 5946 6202 2048 51 Unknown
mmcblk0p56 6202 6586 3072 52 Unknown
mmcblk0p57 6586 6842 2048 53 Unknown
mmcblk0p58 6842 6970 1024 54 Unknown
mmcblk0p59 6971 7098 1024 56 Unknown
mmcblk0p60 7099 8192 8751+ 55 Unknown
Partition table entries are not in disk order
It looks like my partition table repeats itself, but refers to the same sectors. Does anyone else see this oddity?
cheat sheet:
Code:
adb shell
su
busybox fdisk -l /dev/block/mmcblk0

$ export PATH=/data/local/bin:$PATH
$ su
#busybox fdisk -l /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2332 MB, 2332033024 bytes
1 heads, 16 sectors/track, 284672 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 63 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 63 71 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 71 634 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 634 284672 2272311 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 634 4384 30000 49 Unknown
/dev/block/mmcblk0p6 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p7 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p8 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p9 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p10 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p11 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p12 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p13 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p14 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p15 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p16 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p17 10209 10240 256 76 Unknown
/dev/block/mmcblk0p18 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p19 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p20 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p21 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p22 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p23 12257 12288 256 73 Unknown
/dev/block/mmcblk0p24 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p25 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p26 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p27 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p28 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p29 264673 264704 256 23 Unknown
/dev/block/mmcblk0p30 634 4384 30000 49 Unknown
/dev/block/mmcblk0p31 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p32 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p33 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p34 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p35 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p36 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p37 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p38 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p39 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p40 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p41 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p42 10209 10240 256 76 Unknown
/dev/block/mmcblk0p43 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p44 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p45 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p46 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p47 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p48 12257 12288 256 73 Unknown
/dev/block/mmcblk0p49 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p50 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p51 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p52 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p53 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p54 264673 264704 256 23 Unknown
/dev/block/mmcblk0p55 634 4384 30000 49 Unknown
/dev/block/mmcblk0p56 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p57 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p58 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p59 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p60 6842 6970 1024 54 Unknown
Partition table entries are not in disk order
Sent from my HTC Vision using XDA App

... very, very weird.
It reminds me of some of Samsung's boneheaded decisions on the filesystem in their Galaxy S series. Just some real head-scratchers -- like using a journaled FAT filesystem that blocks on write for some stupid reason.

If you really want to be sleuthy, read the #g2root logs from last night, particularly scotty2's diagnosis.

What's the difference between our memory and the vibrants. What makes it mountable on a computer. I know he have an sd card for pix and stuff.who on earth is gunna use 4 gigs on just apps. It would make sense to be able to use it for pix and downloads

I figure it is there for the huge cache. Is that cache disabled when the phone is rooted?

Anomaly said:
I figure it is there for the huge cache. Is that cache disabled when the phone is rooted?
Click to expand...
Click to collapse
... to what huge cache are you referring?

Related

[Q] borked internal sd card on Atrix

Hi all,
I posted this in the Atrix Q&A but it doesn't seem to have had many hits, thought I'd try my luck here (here is the original thread: http://forum.xda-developers.com/showthread.php?t=1594675) ...basically my Atrix emmc internal memory card is borked and I am trying to find a way to restore it other than SBFing to factory (which is risky and a hassle...).
rickywyatt kindly told me to execute these commands in an adb shell and to post the results:
adb shell
# cat /proc/partitions
# fdisk /dev/block/mmcblk0
p
q
well my results are as follows:
1|[email protected]:/ $ su
su
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2048 loop0
253 0 98304 zram0
179 0 15541760 mmcblk0
179 1 3584 mmcblk0p1
179 2 512 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 327680 mmcblk0p12
179 13 786432 mmcblk0p13
179 14 20480 mmcblk0p14
179 15 655360 mmcblk0p15
179 16 2097152 mmcblk0p16
179 17 353280 mmcblk0p17
179 18 11233792 mmcblk0p18
179 32 7772160 mmcblk1
179 33 7771136 mmcblk1p1
[email protected]:/ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 1942720.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): ←[6np
p
Disk /dev/block/mmcblk0: 15.9 GB, 15914762240 bytes
1 heads, 16 sectors/track, 1942720 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 512 3584 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 513 576 512 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 577 832 2048 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 833 1937856 15496192 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 897 1024 1024 83 Linux
/dev/block/mmcblk0p6 1025 1088 512 83 Linux
/dev/block/mmcblk0p7 1089 1152 512 83 Linux
/dev/block/mmcblk0p8 1153 1280 1024 83 Linux
/dev/block/mmcblk0p9 1281 1536 2048 83 Linux
/dev/block/mmcblk0p10 1537 2560 8192 83 Linux
/dev/block/mmcblk0p11 2561 3584 8192 83 Linux
/dev/block/mmcblk0p12 3585 44544 327680 83 Linux
/dev/block/mmcblk0p13 44545 142848 786432 83 Linux
/dev/block/mmcblk0p14 142849 145408 20480 83 Linux
/dev/block/mmcblk0p15 145409 227328 655360 83 Linux
/dev/block/mmcblk0p16 227329 489472 2097152 83 Linux
/dev/block/mmcblk0p17 489473 533632 353280 83 Linux
/dev/block/mmcblk0p18 533633 1937856 11233792 83 Linux
Command (m for help): ←[6nq
q
[email protected]:/ #​
anyone know what I need to do next? If anyone can interpret the output for me I'd be so grateful.
Thanks,
Mark
I'd say flashing an sbf is alot easier then that haha.
Sent from my MB860 using XDA
If i where you i'd try to leave it as if was new and take it to motorola service, they change it to a new one. If you did unlocked the bootload (i guess you did) i think that there was a way to hidde the unlocked at boot.
GL with that!

[Q] [L5] [E612F] Can KDZ update change (apparent) internal SD size?

Hello!
TL/DR version: I updated a L5 (E612F - Vivo BR) with a V20 KDZ file and the internal storage, that was 8GB is seen by fdisk as ~3GB. There seems to be something wrong with the partition table. Is it possible to revert it back to the original value?
Detailed version:
My girlfriend bought a L5 (E612F - Vivo BR) and urged me to remove all the LG crap that came with the phone.
E612f is known for not being easily rootable and so on, so it was a struggle to put CM10.x in it. After many attempts and a few boot loops, I managed to use an E610 KDZ + E610 recovery and other images from this thread: http://forum.xda-developers.com/showthread.php?t=2186161
The problem is that fdisk reports that the internal SD has only ~3GB of size, but the device ghas 8GB internal SD. Because of that, she gets low space errors all the time:
Code:
1|[email protected]:/ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
1 heads, 16 sectors/track, 477184 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 3 20 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 3 128 1003+ 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 256 1024 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 257 465152 3719168 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 8193 8704 4096 47 Unknown
/dev/block/mmcblk0p6 8705 9216 4096 2c Unknown
/dev/block/mmcblk0p7 9217 9728 4096 58 Unknown
/dev/block/mmcblk0p8 9729 12800 24576 77 Unknown
/dev/block/mmcblk0p9 12801 13824 8192 48 Unknown
/dev/block/mmcblk0p10 13825 14336 4096 4a Unknown
/dev/block/mmcblk0p11 14337 14848 4096 4b Unknown
/dev/block/mmcblk0p12 14849 18432 28672 49 Unknown
/dev/block/mmcblk0p13 18433 22016 28672 6c Unknown
/dev/block/mmcblk0p14 22017 100096 624640 83 Linux
/dev/block/mmcblk0p15 100353 101376 8192 83 Linux
/dev/block/mmcblk0p16 101377 114176 102400 83 Linux
/dev/block/mmcblk0p17 114177 115200 8192 60 Unknown
/dev/block/mmcblk0p18 115201 116224 8192 83 Linux
/dev/block/mmcblk0p19 116225 117760 12288 6b Unknown
/dev/block/mmcblk0p20 117761 470656 2823168 83 Linux
/dev/block/mmcblk0p21 471041 471552 4096 ff Unknown
/dev/block/mmcblk0p22 471553 471680 1024 ff Unknown
/dev/block/mmcblk0p23 472065 474112 16384 83 Linux
Could the KDZ from another version (E610) be the culprit for this? Any idea how to deal with it? Thanks!

Working on unbricking hard bricked Moto E

UPDATE:
Working on QPST tools now:
* Need to find prog_emmc_firehose_8x10.mbn
The goal of this project is to gather all the information and tools required in unbricking a hard bricked Moto E (1st Generation).
Possible methods:
1. Blankflash
Requires: singleimage_8x10.mbn, qboot utility for Moto E, programmer_8x10.mbn
2. MiFlash
Requires: fastboot script, fastboot or mfastboot, MPRG8x10.hex, 8x10_msimage.mbn, rawprogram0.xml, patch0.xml
3. QPST
Requires: QPST tool, rawprogram0.xml, patch0.xml, prog_emmc_firehose_8x10.mbn, flat build/single image, multi build/sparse images.
Click to expand...
Click to collapse
XDA:DevDB Information
Unbrick Moto E, Tool/Utility for the Moto E
Contributors
206bone
Version Information
Status: Testing
Created 2016-02-02
Last Updated 2016-02-05
Reserved
Creating partition.xml file:
1. Post from senior member darkspr1te:
http://forum.xda-developers.com/showpost.php?p=36019312&postcount=13
2. Another post from a blog.
Reserved
For reference:
eMMC Partition tool (QPST tools)
Qcom Partition Type Cross Reference (To find Partition IDs for creating partition.xml)
Moto G blank flash tutorial
Creating PIT
Moto E PITs
Moto G PIT
R&D on using Qualcomm
Unbrick Qualcomm Snapdragon devices
Decompiler
GPT Parser
PartitioningTool.py
Moto E source code distros
Sparse Converter
R&D Building Qualcomm Bootloaders
GUID Partition Table (GPT)
Master Boot Record (MBR)
EFI System Partition
Unified Extensible Firmware Interface (UEFI)
UEFI Programming
Test Boot loader
X86_Assembly/Bootloaders
Tell me how I can help and i'll try my best dude
iTudorS said:
Tell me how I can help and i'll try my best dude
Click to expand...
Click to collapse
Thank you so much bro... Could you please provide me the full partition information table? More the information, more better..
Here's the link on how to do it: Partition table
I've just dissected a 8x10_msimage.mbn file. And I found 4 partitions:
1. SBL1
2. DDR (No info on DDR.)
3. RPM
4. TZ
I don't know what this DDR file is. I'd like to see the size of this file(in Kb) on the partition table.
206bone said:
Thank you so much bro... Could you please provide me the full partition information table? More the information, more better..
Here's the link on how to do it: Partition table
I've just dissected a 8x10_msimage.mbn file. And I found 4 partitions:
1. SBL1
2. DDR (No info on DDR.)
3. RPM
4. TZ
I don't know what this DDR file is. I'd like to see the size of this file(in Kb) on the partition table.
Click to expand...
Click to collapse
Hi, I love to help and more in electronics field. Here's my contribution for MotoE XT1022 Condor Device.
Code:
major minor #blocks name
7 0 85648 loop0
7 1 22980 loop1
7 2 32380 loop2
7 3 91916 loop3
7 4 27160 loop4
7 5 4180 loop5
7 6 15668 loop6
7 7 3136 loop7
253 0 524288 zram0
179 0 3866624 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 512 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 512 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 465024 mmcblk0p33
259 2 917504 mmcblk0p34
259 3 8192 mmcblk0p35
259 4 2350464 mmcblk0p36
179 32 512 mmcblk0rpmb
179 64 30466048 mmcblk1
179 65 30465024 mmcblk1p1
254 0 85648 dm-0
254 1 22980 dm-1
254 2 32380 dm-2
254 3 91916 dm-3
254 4 27160 dm-4
254 5 4180 dm-5
254 6 15668 dm-6
254 7 3136 dm-7
7 8 20892 loop8
254 8 20892 dm-8
7 9 61628 loop9
254 9 61628 dm-9
7 10 19848 loop10
254 10 19848 dm-10
7 11 36560 loop11
254 11 36560 dm-11
7 12 35516 loop12
254 12 35516 dm-12
7 13 7312 loop13
254 13 7312 dm-13
Here is the detailed partition info obtained from msm_sdcc.1:
Code:
DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p11
boot -> /dev/block/mmcblk0p31
cache -> /dev/block/mmcblk0p33
cid -> /dev/block/mmcblk0p25
clogo -> /dev/block/mmcblk0p28
dhob -> /dev/block/mmcblk0p20
fsc -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p21
hob -> /dev/block/mmcblk0p19
kpan -> /dev/block/mmcblk0p35
logo -> /dev/block/mmcblk0p27
logs -> /dev/block/mmcblk0p9
misc -> /dev/block/mmcblk0p30
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p17
modemst2 -> /dev/block/mmcblk0p18
padA -> /dev/block/mmcblk0p10
padB -> /dev/block/mmcblk0p16
pds -> /dev/block/mmcblk0p26
persist -> /dev/block/mmcblk0p29
recovery -> /dev/block/mmcblk0p32
rpm -> /dev/block/mmcblk0p5
rpmBackup -> /dev/block/mmcblk0p12
sbl1 -> /dev/block/mmcblk0p2
sdi -> /dev/block/mmcblk0p7
sdiBackup -> /dev/block/mmcblk0p14
sp -> /dev/block/mmcblk0p24
ssd -> /dev/block/mmcblk0p23
system -> /dev/block/mmcblk0p34
tz -> /dev/block/mmcblk0p6
tzBackup -> /dev/block/mmcblk0p13
userdata -> /dev/block/mmcblk0p36
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15
Here is the detailed partition info obtained from msm_sdcc.2:
Code:
mmcblk1 -> /dev/block/mmcblk1
mmcblk1p1 -> /dev/block/mmcblk1p1
DDR partition contain DDR.bin. This image addresses the Physical RAM Memory in the device... common on Elpida Ram Powered Devices. Correct me if I'm wrong please.
Tell me anything that you need.
try this files
206bone said:
Can you please help me out with finding the IDs of each partition in mmcblk0 in the boot record?...
Click to expand...
Click to collapse
Hi friend, as requested:
IDs from mmcblk0:
Code:
Disk /dev/block/mmcblk0: 7733248 sectors, 3776M
Logical sector size: 512
Partition table holds up to 36 entries
First usable sector is 34, last usable sector is 7733214
Number Start (sector) End (sector) Size Code Name
1 256 131327 64.0M 0700 modem
2 131328 132351 512K 0700 sbl1
3 132352 132415 32768 0700 DDR
4 132608 133631 512K 0700 aboot
5 135608 136007 200K 0700 rpm
6 136608 137407 400K 0700 tz
7 137608 137671 32768 0700 sdi
8 137672 138695 512K 0700 utags
9 138696 142791 2048K 0700 logs
10 142792 147455 2332K 0700 padA
11 147456 148479 512K 0700 abootBackup
12 150456 150855 200K 0700 rpmBackup
13 151456 152255 400K 0700 tzBackup
14 152456 152519 32768 0700 sdiBackup
15 152520 153543 512K 0700 utagsBackup
16 153544 155647 1052K 0700 padB
17 155648 158719 1536K 0700 modemst1
18 158720 161791 1536K 0700 modemst2
19 161792 162767 488K 0700 hob
20 162768 162831 32768 0700 dhob
21 163072 166143 1536K 0700 fsg
22 166144 166145 1024 0700 fsc
23 166146 166161 8192 0700 ssd
24 166162 168209 1024K 0700 sp
25 168210 168465 128K 0700 cid
26 168466 174609 3072K 0700 pds
27 174610 182801 4096K 0700 logo
28 182802 190993 4096K 0700 clogo
29 191232 207615 8192K 0700 persist
30 207616 208639 512K 0700 misc
31 208640 229039 9.9M 0700 boot
32 229040 249599 10.0M 0700 recovery
33 249600 1179647 454M 0700 cache
34 1179648 3014655 896M 0700 system
35 3014656 3031039 8192K 0700 kpan
36 3031040 7731967 2295M 0700 userdata
Info from mmcblk0p1:
Code:
Disk /dev/block/mmcblk0p1: 67 MB, 67108864 bytes
4 heads, 16 sectors/track, 2048 cylinders, total 131072 sectors
Info from mmcblk0p2:
Code:
Disk /dev/block/mmcblk0p2: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p3:
Code:
Disk /dev/block/mmcblk0p3: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p4:
Code:
Disk /dev/block/mmcblk0p4: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p5:
Code:
Disk /dev/block/mmcblk0p5: 0 MB, 204800 bytes
4 heads, 16 sectors/track, 6 cylinders, total 400 sectors
Info from mmcblk0p6:
Code:
Disk /dev/block/mmcblk0p6: 0 MB, 409600 bytes
4 heads, 16 sectors/track, 12 cylinders, total 800 sectors
Info from mmcblk0p7:
Code:
Disk /dev/block/mmcblk0p7: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p8:
Code:
Disk /dev/block/mmcblk0p8: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p9:
Code:
Disk /dev/block/mmcblk0p9: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders, total 4096 sectors
Info from mmcblk0p10:
Code:
Disk /dev/block/mmcblk0p10: 2 MB, 2387968 bytes
4 heads, 16 sectors/track, 72 cylinders, total 4664 sectors
Info from mmcblk0p11:
Code:
Disk /dev/block/mmcblk0p11: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p12:
Code:
Disk /dev/block/mmcblk0p12: 0 MB, 204800 bytes
4 heads, 16 sectors/track, 6 cylinders, total 400 sectors
Info from mmcblk0p13:
Code:
Disk /dev/block/mmcblk0p13: 0 MB, 409600 bytes
4 heads, 16 sectors/track, 12 cylinders, total 800 sectors
Info from mmcblk0p14:
Code:
Disk /dev/block/mmcblk0p14: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p15:
Code:
Disk /dev/block/mmcblk0p15: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p16:
Code:
Disk /dev/block/mmcblk0p16: 1 MB, 1077248 bytes
4 heads, 16 sectors/track, 32 cylinders, total 2104 sectors
Info from mmcblk0p17:
Code:
Disk /dev/block/mmcblk0p17: 1 MB, 1572864 bytes
4 heads, 16 sectors/track, 48 cylinders, total 3072 sectors
Info from mmcblk0p18:
Code:
Disk /dev/block/mmcblk0p18: 1 MB, 1572864 bytes
4 heads, 16 sectors/track, 48 cylinders, total 3072 sectors
Info from mmcblk0p19:
Code:
Disk /dev/block/mmcblk0p19: 0 MB, 499712 bytes
4 heads, 16 sectors/track, 15 cylinders, total 976 sectors
Info from mmcblk0p20:
Code:
Disk /dev/block/mmcblk0p20: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p21:
Code:
Disk /dev/block/mmcblk0p21: 1 MB, 1572864 bytes
4 heads, 16 sectors/track, 48 cylinders, total 3072 sectors
Info from mmcblk0p22:
Code:
Disk /dev/block/mmcblk0p22: 0 MB, 1024 bytes
4 heads, 16 sectors/track, 0 cylinders, total 2 sectors
Info from mmcblk0p23:
Code:
Disk /dev/block/mmcblk0p23: 0 MB, 8192 bytes
4 heads, 16 sectors/track, 0 cylinders, total 16 sectors
Info from mmcblk0p24:
Code:
Disk /dev/block/mmcblk0p24: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders, total 2048 sectors
Info from mmcblk0p25:
Code:
Disk /dev/block/mmcblk0p25: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders, total 256 sectors
Info from mmcblk0p26:
Code:
Disk /dev/block/mmcblk0p26: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders, total 6144 sectors
Info from mmcblk0p27:
Code:
Disk /dev/block/mmcblk0p27: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders, total 8192 sectors
Info from mmcblk0p28:
Code:
Disk /dev/block/mmcblk0p28: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders, total 8192 sectors
Info from mmcblk0p29:
Code:
Disk /dev/block/mmcblk0p29: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders, total 16384 sectors
Info from mmcblk0p30:
Code:
Disk /dev/block/mmcblk0p30: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p31:
Code:
Disk /dev/block/mmcblk0p31: 10 MB, 10444800 bytes
4 heads, 16 sectors/track, 318 cylinders, total 20400 sectors
Info from mmcblk0p32:
Code:
Disk /dev/block/mmcblk0p32: 10 MB, 10526720 bytes
4 heads, 16 sectors/track, 321 cylinders, total 20560 sectors
Info from mmcblk0p33:
Code:
Disk /dev/block/mmcblk0p33: 476 MB, 476184576 bytes
4 heads, 16 sectors/track, 14532 cylinders, total 930048 sectors
Info from mmcblk0p34:
Code:
Disk /dev/block/mmcblk0p34: 939 MB, 939524096 bytes
4 heads, 16 sectors/track, 28672 cylinders, total 1835008 sectors
Info from mmcblk0p35:
Code:
Disk /dev/block/mmcblk0p35: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders, total 16384 sectors
Info from mmcblk0p36:
Code:
Disk /dev/block/mmcblk0p36: 2406 MB, 2406875136 bytes
4 heads, 16 sectors/track, 73452 cylinders, total 4700928 sectors
Hope it helps!
Thanks dude...
Ready To Help
Hey Friend I dont know how to make this files But I hav trust on You so Please If you Make this File I have a hard Bricked Moto E and I an Ready to Test jst Give Me File And Instructions What to Do ... Thank You
206bone said:
Thanks dude...
Click to expand...
Click to collapse
You're welcome. :good:
Maybe its helpfull
Will this method mentioned for LG G2 with Qualcomm(QHSB BULK) fix the file or here it's totally different thing? I am really keen in this project because my device has been dead since 5 months.
Have you got a solution?
I would like to participate in this project
Can i be of some use in this project ? Ive tried all possible ways to get my phone to life but failed .
Keep it up Guys..... We all are waiting. ..
Thanks guyzz to start the project of reviving moto e back to life i too bricked it 2-3 month ago. ill help u guzz in testing and collecting data and giving it here.lets unbrick our device....
[Edit]- if u need files from moto e tell me ..... i have a spare working moto e also.
You can recreate all the files needed, but you can't sign them. Non-signed files won't pass verification and it won't work.
Don't let that demotivate you though, you may come up with something that we didn't see when the first Moto G bricks came around more than year ago.
Try and report back
Did anyone try this method for One Plus, please report back.
Klock2 said:
Did anyone try this method for One Plus, please report back.
Click to expand...
Click to collapse
those files are for one plus one, wont work on moto e
iTudorS said:
those files are for one plus one, wont work on moto e
Click to expand...
Click to collapse
Its not even proper for OnePlus One but ColorOS plays is its role here. So I think it might work as Qualcomm Device i.e QHSBULK

Elephone P9000 Partition Layout

Partition Layout for Elephone P9000
Code:
major minor #blocks name fsname
7 0 1254 loop0
7 1 32768 loop1 su
254 0 1988256 zram0
179 0 30535680 mmcblk0
179 1 16384 mmcblk0p1 recovery
179 2 512 mmcblk0p2 para
179 3 10240 mmcblk0p3 expdb
179 4 1024 mmcblk0p4 frp
179 5 256 mmcblk0p5 ppl
179 6 32768 mmcblk0p6 nvdata
179 7 32768 mmcblk0p7 metadata
179 8 8192 mmcblk0p8 protect1
179 9 12512 mmcblk0p9 protect2
179 10 8192 mmcblk0p10 seccfg
179 11 8192 mmcblk0p11 oemkeystore
179 12 3072 mmcblk0p12 proinfo
179 13 24576 mmcblk0p13 md1img
179 14 4096 mmcblk0p14 md1dsp
179 15 3072 mmcblk0p15 md1arm7
179 16 5120 mmcblk0p16 md3img
179 17 5120 mmcblk0p17 nvram
179 18 1024 mmcblk0p18 lk
179 19 1024 mmcblk0p19 lk2
179 20 16384 mmcblk0p20 boot
179 21 8192 mmcblk0p21 logo
179 22 5120 mmcblk0p22 tee1
179 23 5120 mmcblk0p23 tee2
179 24 6144 mmcblk0p24 secro
179 25 10240 mmcblk0p25 keystore
179 26 2621440 mmcblk0p26 system
179 27 442368 mmcblk0p27 cache
179 28 27226095 mmcblk0p28 userdata
179 29 16384 mmcblk0p29 flashinfo
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 128 31166976 mmcblk1
179 129 31162004 mmcblk1p1
Code:
Model: MMC RX14MB (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 32.8kB 16.8MB 16.8MB recovery
2 16.8MB 17.3MB 524kB para
3 17.3MB 27.8MB 10.5MB expdb
4 27.8MB 28.9MB 1049kB frp
5 28.9MB 29.1MB 262kB ppl
6 29.1MB 62.7MB 33.6MB ext4 nvdata
7 62.7MB 96.2MB 33.6MB metadata
8 96.2MB 105MB 8389kB ext4 protect1
9 105MB 117MB 12.8MB ext4 protect2
10 117MB 126MB 8389kB seccfg
11 126MB 134MB 8389kB oemkeystore
12 134MB 137MB 3146kB proinfo
13 137MB 163MB 25.2MB md1img
14 163MB 167MB 4194kB md1dsp
15 167MB 170MB 3146kB md1arm7
16 170MB 175MB 5243kB md3img
17 175MB 180MB 5243kB nvram
18 180MB 181MB 1049kB lk
19 181MB 182MB 1049kB lk2
20 182MB 199MB 16.8MB boot
21 199MB 208MB 8389kB logo
22 208MB 213MB 5243kB tee1
23 213MB 218MB 5243kB tee2
24 218MB 224MB 6291kB secro
25 224MB 235MB 10.5MB keystore
26 235MB 2919MB 2684MB ext4 system
27 2919MB 3372MB 453MB ext4 cache
28 3372MB 31.3GB 27.9GB ext4 userdata
29 31.3GB 31.3GB 16.8MB flashinfo

Need help putting phone into USB Diag Mode

I have looked at and tried every manual or how to I could find all over the web. Nothing seems to be working. Even if I run a getprop sys.usb.config it shows that the phone is in Diag,adb. However, I am not getting a comport showing up in Windows device manager. Does ASUS disable this process?
Have you enabled developer options in settings and selected "USB debugging" ?
If so, sounds like it might be a Windows driver issue. Grab the latest ones off the ASUS website and post back.
wang1chung said:
Have you enabled developer options in settings and selected "USB debugging" ?
If so, sounds like it might be a Windows driver issue. Grab the latest ones off the ASUS website and post back.
Click to expand...
Click to collapse
Yes, yes, and yes. Have done all that. Once in Diag mode it is suppose to show up as a Qualcomm comport device. Didn't doesn't even show up for me to install drivers.
when you plug your phone in, do you see "usb debugging" in the pull down menu?
Maybe another member can help with the Windows issue as I don't use that OS.
What are you trying to do?
wang1chung said:
when you plug your phone in, do you see "usb debugging" in the pull down menu?
Maybe another member can help with the Windows issue as I don't use that OS.
What are you trying to do?
Click to expand...
Click to collapse
Yes, USB debugging is activated, and I can ADB just fine. What I am trying to do is put the phone in USB Diagnostic(Diag) Mode, not USB debugging. When in USB Diag Mode the phone will communicate to the PC as a serial comport. This will allow me to use the Qualcomm Utilities to possibly edit and unlock LTE bands on it.
Ah, my apologies, I thought you meant debugging mode.
Maybe someone else can chime in to assist.
Have you tried a different computer? Post a link to the software, I'll try it on my Linux box. I could really use this software on the ZenFone Ultra if it works.
wang1chung said:
Ah, my apologies, I thought you meant debugging mode.
Maybe someone else can chime in to assist.
Have you tried a different computer? Post a link to the software, I'll try it on my Linux box. I could really use this software on the ZenFone Ultra if it works.
Click to expand...
Click to collapse
Yes it is the Ultra that I am trying to use it for. Posted here because there is more traffic, and thought maybe the devices are close enough that if someone figured it out on the Zenfone, that it could translate to the Ultra as well. There are multiple guides on XDA, but this is the main one I was trying to follow:
https://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
Although I do admit I have been bouncing around from guide to guide, basically everything that Google search could uncover.
You'll be my wife's hero if you can get this done. Post back how it goes.
Edit: I see the ZenFone 3 ultra zu680kl on willmyphonework.net shows different 4g bands than the phones for sale on gearbest. Which bands did you need and do you have any idea why they're different? I was looking at the global version not the China one.
wang1chung said:
You'll be my wife's hero if you can get this done. Post back how it goes.
Edit: I see the ZenFone 3 ultra zu680kl on willmyphonework.net shows different 4g bands than the phones for sale on gearbest. Which bands did you need and do you have any idea why they're different? I was looking at the global version not the China one.
Click to expand...
Click to collapse
I need 2, 4, and 17
I need the same, lol
In my researching, there was one guy that said he got it to work with an asus rom with an app called "ASUS log tool e". I downloaded that firmware, extracted the app and tried to install. It didn't work, said the app already existed. Maybe there's a hidden one already on our phones?
I also tried win7 32bit and linux, can't detect my phone either.
On updating to nougat, I have lost root explorer (latest version from the play store doesn't work). I'll keep messing with it.
You find anything?
{
"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"
}
doctahjeph said:
..... There are multiple guides on XDA, but this is the main one I was trying to follow:
https://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
Click to expand...
Click to collapse
so, I think I got it to work. Using your guide you referenced, I can browse the nv files with qpst and read the data from ID 01877 in qxdm. I stopped there because all my LTE bands work and I didn't want to mess anything up, lol.
I forced windows to install "Qualcomm hs-usb qdloader 9008" drivers after I executed a script I found that enables (I think) diag mode.
Can you take a look with your zu680kl ?
I used the script from doroid.org/2017/01/24/zenfone-3-ze520kl-rooted-diag-mode/
wang1chung said:
so, I think I got it to work. Using your guide you referenced, I can browse the nv files with qpst and read the data from ID 01877 in qxdm. I stopped there because all my LTE bands work and I didn't want to mess anything up, lol.
I forced windows to install "Qualcomm hs-usb qdloader 9008" drivers after I executed a script I found that enables (I think) diag mode.
Can you take a look with your zu680kl ?
I used the script from doroid.org/2017/01/24/zenfone-3-ze520kl-rooted-diag-mode/
Click to expand...
Click to collapse
Awesome!! I will definitely take a look at this today. Thanks!
wang1chung said:
so, I think I got it to work. Using your guide you referenced, I can browse the nv files with qpst and read the data from ID 01877 in qxdm. I stopped there because all my LTE bands work and I didn't want to mess anything up, lol.
I forced windows to install "Qualcomm hs-usb qdloader 9008" drivers after I executed a script I found that enables (I think) diag mode.
Can you take a look with your zu680kl ?
I used the script from doroid.org/2017/01/24/zenfone-3-ze520kl-rooted-diag-mode/
Click to expand...
Click to collapse
yes yes yes!!! finally!! you are the man!! I freaking love you dude!!
No way, it works? So you have successfully enabled those LTE bands? Omg, I'm buying that phone now!
wang1chung said:
No way, it works? So you have successfully enabled those LTE bands? Omg, I'm buying that phone now!
Click to expand...
Click to collapse
wait, lol. sorry the computer seeing the phones an a comport part works. I am in the process now of trying to edit the bands. I will report back soon, hopefully with good news.
Lol
Ok, well to test that you have successfully enabled them, the app "network signal guru" is the only one I've found that displays the correct in use LTE band.
Good luck!
wang1chung said:
Lol
Ok, well to test that you have successfully enabled them, the app "network signal guru" is the only one I've found that displays the correct in use LTE band.
Good luck!
Click to expand...
Click to collapse
Not looking good​ so far. I get right up to rewriting the NV values, but Everytime I reboot to set the new values they always resort back to the original values. From what I have read this maybe a fail safe setup in the kernel by ASUS. In which case I can get around it with a stock custom kernel. Non of those lying around. I have no clue how to even compile one myself. So more research I must do.
doctahjeph said:
Not looking good​ so far. I get right up to rewriting the NV values, but Everytime I reboot to set the new values they always resort back to the original values. From what I have read this maybe a fail safe setup in the kernel by ASUS. In which case I can get around it with a stock custom kernel. Non of those lying around. I have no clue how to even compile one myself. So more research I must do.
Click to expand...
Click to collapse
Did you happen to get the correct SPC code for QPST? I have read there are issues writing the NV values without the correct SPC code, how did you get it? I tried reading 00085 (sec_code) and get a "no diag response". Edit: I updated qxdm and confirmed it is 000000.
I am trying to do a full NV backup through the "software download" part of QPST and it doesn't complete. Have you been able to? I'd feel more comfortable if I had a full and proper QCN backup before I started messing with it.
Are we assuming Asus injected the anti-tamper code into the stock kernel only? So compiling the stock kernel with unmolested source code should be all we need?
---------- Post added at 04:00 AM ---------- Previous post was at 03:43 AM ----------
forgot to add some partition info I got when I was bored. I made some dd backups of all the partitions too, just missing the QCN backup file.
EDIT: From what I've read, the IMEI info is stored in the modemst1, modemst2, and fsg partitions (mmcblk0p24, mmcblk0p26 and mmcblk0p27). If a QCN backup is not possible, I would definitely advise backing up these.
Code:
ASUS_Z012D:/ # cat /proc/partitions
major minor #blocks name
7 0 98304 loop0
254 0 786432 zram0
179 0 61071360 mmcblk0
179 1 1280 mmcblk0p1
179 2 1280 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 256 mmcblk0p7
179 8 256 mmcblk0p8
179 9 256 mmcblk0p9
179 10 256 mmcblk0p10
179 11 256 mmcblk0p11
179 12 256 mmcblk0p12
179 13 256 mmcblk0p13
179 14 256 mmcblk0p14
179 15 128 mmcblk0p15
179 16 128 mmcblk0p16
179 17 32 mmcblk0p17
179 18 8 mmcblk0p18
179 19 5120 mmcblk0p19
179 20 5120 mmcblk0p20
179 21 16 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 1024 mmcblk0p23
179 24 1536 mmcblk0p24
179 25 1 mmcblk0p25
179 26 1536 mmcblk0p26
179 27 1536 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 1024 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 1024 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 1024 mmcblk0p34
259 3 1024 mmcblk0p35
259 4 1024 mmcblk0p36
259 5 1024 mmcblk0p37
259 6 512 mmcblk0p38
259 7 512 mmcblk0p39
259 8 32 mmcblk0p40
259 9 512 mmcblk0p41
259 10 1024 mmcblk0p42
259 11 512 mmcblk0p43
259 12 4096 mmcblk0p44
259 13 256 mmcblk0p45
259 14 256 mmcblk0p46
259 15 8 mmcblk0p47
259 16 11264 mmcblk0p48
259 17 2048 mmcblk0p49
259 18 1536 mmcblk0p50
259 19 2048 mmcblk0p51
259 20 16384 mmcblk0p52
259 21 65536 mmcblk0p53
259 22 16384 mmcblk0p54
259 23 32768 mmcblk0p55
259 24 32768 mmcblk0p56
259 25 32768 mmcblk0p57
259 26 32768 mmcblk0p58
259 27 32768 mmcblk0p59
259 28 49152 mmcblk0p60
259 29 16384 mmcblk0p61
259 30 86016 mmcblk0p62
259 31 32768 mmcblk0p63
259 32 212992 mmcblk0p64
259 33 131072 mmcblk0p65
259 34 3932160 mmcblk0p66
259 35 56233967 mmcblk0p67
179 32 4096 mmcblk0rpmb
179 64 62521344 mmcblk1
179 65 62520320 mmcblk1p1
253 0 56233951 dm-0
ASUS_Z012D:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1716480 5876 1710604 1% /
tmpfs 1826588 644 1825944 1% /dev
tmpfs 1826588 0 1826588 0% /mnt
/dev/fuse 55220256 26700280 28519976 49% /mnt/runtime/default/emulated
/dev/fuse 55220256 26700280 28519976 49% /mnt/runtime/read/emulated
/dev/fuse 55220256 26700280 28519976 49% /mnt/runtime/write/emulated
/dev/block/vold/public:179,65 62505024 56435648 6069376 91% /mnt/media_rw/ADCA-0A16
/dev/fuse 62505024 56435648 6069376 91% /mnt/runtime/default/ADCA-0A16
/dev/fuse 62505024 56435648 6069376 91% /mnt/runtime/read/ADCA-0A16
/dev/fuse 62505024 56435648 6069376 91% /mnt/runtime/write/ADCA-0A16
/dev/block/mmcblk0p66 3749404 3443272 306132 92% /system
/dev/block/loop0 92656 2392 90264 3% /system/bin/su
/dev/block/mmcblk0p65 124912 408 124504 1% /cache
/dev/block/mmcblk0p56 28144 340 27804 2% /persist
/dev/block/mmcblk0p54 12016 5052 6964 43% /dsp
/dev/block/mmcblk0p62 85968 75008 10960 88% /firmware
/dev/block/mmcblk0p61 12016 40 11976 1% /persdata/absolute
/dev/block/mmcblk0p53 60400 4020 56380 7% /asdf
/dev/block/mmcblk0p28 16048 5328 10720 34% /factory
/dev/block/mmcblk0p60 12016 8344 3672 70% /asusfw
/dev/block/mmcblk0p63 27632 44 27588 1% /ADF
/dev/block/mmcblk0p64 199648 163352 36296 82% /APD
/dev/block/dm-0 55220256 26700280 28519976 49% /data
ASUS_Z012D:/ #
ASUS_Z012D:/data # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Model: MMC HCG8a4 (sd/mmc)
Disk /dev/block/mmcblk0: 62.5GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 1328kB 1311kB sbl1
2 1328kB 2639kB 1311kB sbl1bak
3 2639kB 3163kB 524kB rpm
4 3163kB 3687kB 524kB rpmbak
5 3687kB 5785kB 2097kB tz
6 5785kB 7882kB 2097kB tzbak
7 7882kB 8144kB 262kB devcfg
8 8144kB 8406kB 262kB devcfgbak
9 8406kB 8668kB 262kB keymaster
10 8668kB 8930kB 262kB keymasterbak
11 8930kB 9192kB 262kB cmnlib
12 9192kB 9455kB 262kB cmnlibbak
13 9455kB 9717kB 262kB cmnlib64
14 9717kB 9979kB 262kB cmnlib64bak
15 9979kB 10.1MB 131kB lksecapp
16 10.1MB 10.2MB 131kB lksecappbak
17 10.2MB 10.3MB 32.8kB DDR
18 10.3MB 10.3MB 8192B ssd
19 10.3MB 15.5MB 5243kB aboot
20 15.5MB 20.8MB 5243kB abootbak
21 20.8MB 20.8MB 16.4kB sec
22 33.6MB 34.6MB 1049kB devinfo
23 50.3MB 51.4MB 1049kB sysinfo
24 51.4MB 53.0MB 1573kB fsg
25 53.0MB 53.0MB 1024B fsc
26 53.0MB 54.5MB 1573kB modemst1
27 54.5MB 56.1MB 1573kB modemst2
28 56.1MB 77.1MB 21.0MB ext4 factory
29 77.1MB 78.1MB 1049kB asuskey
30 78.1MB 79.2MB 1049kB asuskey2
31 79.2MB 80.2MB 1049kB asuskey3
32 80.2MB 81.3MB 1049kB asuskey4
33 81.3MB 82.3MB 1049kB asuskey5
34 82.3MB 83.4MB 1049kB asuskey6
35 83.4MB 84.4MB 1049kB persistent
36 84.4MB 85.5MB 1049kB asusgpt
37 85.5MB 86.5MB 1049kB misc
38 86.5MB 87.0MB 524kB keystore
39 87.0MB 87.6MB 524kB config
40 87.6MB 87.6MB 32.8kB limits
41 87.6MB 88.1MB 524kB mota
42 88.1MB 89.2MB 1049kB dip
43 89.2MB 89.7MB 524kB syscfg
44 89.7MB 93.9MB 4194kB mcfg
45 93.9MB 94.1MB 262kB apdp
46 94.1MB 94.4MB 262kB msadp
47 94.4MB 94.4MB 8192B dpo
48 94.4MB 106MB 11.5MB splash
49 106MB 108MB 2097kB abootdebug
50 108MB 110MB 1573kB fsgCA
51 110MB 112MB 2097kB abootlog
52 117MB 134MB 16.8MB oem
53 134MB 201MB 67.1MB ext4 asdf
54 201MB 218MB 16.8MB ext4 dsp
55 218MB 252MB 33.6MB mdtp
56 252MB 285MB 33.6MB ext4 persist
57 285MB 319MB 33.6MB ftm
58 319MB 352MB 33.6MB boot
59 352MB 386MB 33.6MB recovery
60 386MB 436MB 50.3MB ext4 asusfw
61 436MB 453MB 16.8MB ext4 persdata
62 453MB 541MB 88.1MB fat16 modem
63 541MB 575MB 33.6MB ext4 ADF
64 575MB 793MB 218MB ext4 APD
65 793MB 927MB 134MB ext4 cache
66 927MB 4953MB 4027MB ext4 system
67 4953MB 62.5GB 57.6GB userdata
doctahjeph, have you made any progress? Did you write "0" value to 6828/6829 before writing 134283487 value? Have you tried the new Lineage OS rom (https://forum.xda-developers.com/zenfone-3/development/unofficial-lineageos-14-1-ze520kl-t3587178), maybe it'll allow you to write if you just flash the kernel from this rom? It'll definitely FC like a mofo but might be enough to write the NV values.
I tried this on my wife's phone, the Le Max x900, got into diag mode, re-wrote the nv values , even got the new LTE bands to show up in network signal guru but it won't switch to them (I deselected band 7 and it wouldn't switch to 2/4/17 like my zf3 does). I'm not sure this works for all the phones, unless you've found some other info out? I'm wondering about NV 1878 which I've read needs to be changed, but if there is no version of the phone that comes with those bands enabled, there's no way to know what the value should be. I tried flashing a modem from a similar phone with those bands enabled and soft-bricked it, lol.
anyways, if you need any values from zf3, let me know.
Any luck with this. I am donating 500 bucks to anyone who solves this. Enabling all Lte bands to work

Categories

Resources