Here is the stock Partititon Table for HTC One (M7)
Code:
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1 sbl1
179 2 256 mmcblk0p2 sbl2
179 3 130671 mmcblk0p3 pg1fs
179 4 1 mmcblk0p4 ?
179 5 16 mmcblk0p5 board_info
179 6 256 mmcblk0p6 mfg
179 7 15577 mmcblk0p7 pg2fs
179 8 256 mmcblk0p8 sbl2_update
179 9 1024 mmcblk0p9 sbl3
179 10 256 mmcblk0p10 rpm
179 11 2048 mmcblk0p11 tz
179 12 2080 mmcblk0p12 hboot
179 13 5120 mmcblk0p13 sp1
179 14 1024 mmcblk0p14 wifi
179 15 1024 mmcblk0p15 dsps
179 16 61441 mmcblk0p16 adsp
179 17 8190 mmcblk0p17 radio_config
179 18 32768 mmcblk0p18 reserve_1
179 19 1022 mmcblk0p19 misc
179 20 4096 mmcblk0p20 modem_st1
179 21 4096 mmcblk0p21 modem_st2
179 22 20480 mmcblk0p22 devlog
179 23 4 mmcblk0p23 debug_config
179 24 256 mmcblk0p24 pdata
179 25 16 mmcblk0p25 control
179 26 1280 mmcblk0p26 local
179 27 64 mmcblk0p27 extra
179 28 1024 mmcblk0p28 cdma_record
179 29 98727 mmcblk0p29 reserve
179 30 54270 mmcblk0p30 reserve_2
179 31 76800 mmcblk0p31 radio
179 32 98303 mmcblk0p32 ?
179 33 16384 mmcblk0p33 boot
179 34 16383 mmcblk0p34 recovery
179 35 1900543 mmcblk0p35 system
179 36 655359 mmcblk0p36 cache
179 37 27262976 mmcblk0p37 userdata
Now interestingly enough I've found that the Engineering bootloader posted on the DNA forums that is questionably compatible with our device has this partition table:
Code:
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1 sbl1
179 2 256 mmcblk0p2 sbl2
179 3 130671 mmcblk0p3 pg1fs
179 4 1 mmcblk0p4 ?
179 5 16 mmcblk0p5 board_info
179 6 256 mmcblk0p6 mfg
179 7 15577 mmcblk0p7 pg2fs
179 8 256 mmcblk0p8 sbl2_update
179 9 1024 mmcblk0p9 sbl3
179 10 256 mmcblk0p10 rpm
179 11 2048 mmcblk0p11 tz
179 12 2080 mmcblk0p12 hboot
179 13 5120 mmcblk0p13 sp1
179 14 1024 mmcblk0p14 wifi
179 15 1024 mmcblk0p15 dsps
179 16 61441 mmcblk0p16 adsp
179 17 8190 mmcblk0p17 radio_config
179 18 32768 mmcblk0p18 reserve_1
179 19 1022 mmcblk0p19 misc
179 20 4096 mmcblk0p20 modem_st1
179 21 4096 mmcblk0p21 modem_st2
179 22 20480 mmcblk0p22 devlog
179 23 4 mmcblk0p23 debug_config
179 24 256 mmcblk0p24 pdata
179 25 16 mmcblk0p25 control
179 26 1280 mmcblk0p26 local
179 27 64 mmcblk0p27 extra
179 28 1024 mmcblk0p28 cdma_record
179 29 98727 mmcblk0p29 reserve
179 30 21502 mmcblk0p30 reserve_2
179 31 76800 mmcblk0p31 radio
179 32 16384 mmcblk0p32 boot
179 33 16383 mmcblk0p33 recovery
179 34 1900543 mmcblk0p34 system
179 35 655359 mmcblk0p35 cache
179 36 27394048 mmcblk0p36 userdata
As you can see this bootloader is missing our mmcblk0p32. And has slightly different #blocks in the userdata partition and even more different #blocks in the reserve_2 partition.
I was able to put piece together the names for the blacks by using
Code:
fastboot oem listpartition
while in the engineering bootloader. Doing this resulted in:
Code:
(bootloader) [merge_mfg]:(MERGEMFG, 10) block start=0, size=0 (0 KB)
(bootloader) [merge_emmc]:(RAW, 4) block start=0, size=4849663 (2424831 K
(bootloader) B)
(bootloader) [sbl1]:(RAW, 4) block start=1, size=256 (128 KB)
(bootloader) [sbl2]:(RAW, 4) block start=257, size=512 (256 KB)
(bootloader) [pg1fs]:(PGFS, 4) block start=769, size=261342 (130671 KB)
(bootloader) [board_info]:(RAW, 4) block start=262112, size=32 (16 KB)
(bootloader) [rfg_0]:(RAW, 4) block start=442370, size=2048 (1024 KB)
(bootloader) [rfg_1]:(RAW, 4) block start=444418, size=2048 (1024 KB)
(bootloader) [rfg_2]:(RAW, 4) block start=446466, size=2048 (1024 KB)
(bootloader) [rfg_3]:(RAW, 4) block start=448514, size=2048 (1024 KB)
(bootloader) [rfg_4]:(RAW, 4) block start=450562, size=2048 (1024 KB)
(bootloader) [rfg_5]:(RAW, 4) block start=452610, size=2048 (1024 KB)
(bootloader) [rfg_6]:(RAW, 4) block start=454658, size=2048 (1024 KB)
(bootloader) [mdmsmem]:(RAW, 4) block start=456706, size=2045 (1022 KB)
(bootloader) [dzsystem]:(DEZERO, 8) block start=1048577, size=3801086 (19
(bootloader) 00543 KB)
(bootloader) [dzdata]:(DEZERO, 8) block start=6160384, size=54788096 (273
(bootloader) 94048 KB)
(bootloader) [security_record]:(RAW, 1) block start=0, size=0 (0 KB)
(bootloader) [wcnss]:(RAW, 1) block start=0, size=0 (0 KB)
(bootloader) [wimax]:(RAW, 7E01) block start=0, size=0 (0 KB)
(bootloader) [felica]:(RAW, 1) block start=0, size=0 (0 KB)
(bootloader) [udata_wimax]:(RAW, 7E01) block start=0, size=0 (0 KB)
(bootloader) [spcustom]:(RAW, 1) block start=0, size=0 (0 KB)
(bootloader) [fat]:(RAW, C01) block start=0, size=0 (0 KB)
(bootloader) [imc]:(OTHER, 1) block start=0, size=0 (0 KB)
(bootloader) [nfc_record]:(EXT3, 8301) block start=0, size=0 (0 KB)
(bootloader) [microp]:(OTHER, 1) block start=0, size=0 (0 KB)
(bootloader) [cpld]:(OTHER, 1) block start=0, size=0 (0 KB)
(bootloader) [a1026]:(OTHER, 1) block start=0, size=0 (0 KB)
(bootloader) [nfc]:(OTHER, 1) block start=0, size=0 (0 KB)
(bootloader) [tp]:(OTHER, 1) block start=0, size=0 (0 KB)
(bootloader) [cs]:(OTHER, 1) block start=0, size=0 (0 KB)
(bootloader) [gauge]:(OTHER, 1) block start=0, size=0 (0 KB)
(bootloader) [cir]:(OTHER, 1) block start=0, size=0 (0 KB)
(bootloader) [rcdata]:(OTHER, 1) block start=0, size=0 (0 KB)
(bootloader) [mfg]:(RAW, 7301) block start=262145, size=512 (256 KB)
(bootloader) [pg2fs]:(PGFS, 21) block start=262658, size=31155 (15577 KB)
(bootloader) [sbl2_update]:(RAW, 1) block start=293814, size=512 (256 KB)
(bootloader) [sbl3]:(RAW, 4501) block start=294327, size=2048 (1024 KB)
(bootloader) [rpm]:(RAW, 4701) block start=296376, size=512 (256 KB)
(bootloader) [tz]:(RAW, 4601) block start=296889, size=4096 (2048 KB)
(bootloader) [hboot]:(RAW, 4C01) block start=300986, size=4161 (2080 KB)
(bootloader) [sp1]:(RAW, 3401) block start=305148, size=10240 (5120 KB)
(bootloader) [wifi]:(RAW, 3601) block start=315389, size=2048 (1024 KB)
(bootloader) [dsps]:(RAW, 1) block start=317438, size=2048 (1024 KB)
(bootloader) [adsp]:(RAW, 7A01) block start=319487, size=122882 (61441 KB
(bootloader) )
(bootloader) [radio_config]:(RAW, 7401) block start=442370, size=16381 (8
(bootloader) 190 KB)
(bootloader) [reserve_1]:(RAW, 1) block start=458752, size=65536 (32768 K
(bootloader) B)
(bootloader) [misc]:(RAW, 7601) block start=524289, size=2045 (1022 KB)
(bootloader) [modem_st1]:(EXT3, 4A01) block start=526335, size=8192 (4096
(bootloader) KB)
(bootloader) [modem_st2]:(EXT3, 4B01) block start=534528, size=8192 (4096
(bootloader) KB)
(bootloader) [devlog]:(EXT3, 1901) block start=542721, size=40960 (20480
(bootloader) KB)
(bootloader) [debug_config]:(RAW, 1) block start=583682, size=8 (4 KB)
(bootloader) [pdata]:(RAW, 2301) block start=583691, size=512 (256 KB)
(bootloader) [control]:(RAW, 1) block start=584204, size=32 (16 KB)
(bootloader) [local]:(RAW, 1) block start=584237, size=2561 (1280 KB)
(bootloader) [extra]:(RAW, 1) block start=586799, size=128 (64 KB)
(bootloader) [cdma_record]:(RAW, 1) block start=586928, size=2048 (1024 K
(bootloader) B)
(bootloader) [reserve]:(RAW, 1) block start=588977, size=197455 (98727 KB
(bootloader) )
(bootloader) [reserve_2]:(RAW, 1) block start=786433, size=43004 (21502 K
(bootloader) B)
(bootloader) [radio]:(RAW, 7701) block start=829438, size=153601 (76800 K
(bootloader) B)
(bootloader) [boot]:(RAW, 4801) block start=983040, size=32768 (16384 KB)
(bootloader) [recovery]:(RAW, 7101) block start=1015809, size=32767 (1638
(bootloader) 3 KB)
(bootloader) [system]:(EXT3, 8301) block start=1048577, size=3801086 (190
(bootloader) 0543 KB)
(bootloader) [cache]:(EXT3, 8301) block start=4849664, size=1310719 (6553
(bootloader) 59 KB)
(bootloader) [userdata]:(EXT3, 8301) block start=6160384, size=54788096 (
(bootloader) 27394048 KB)
While I was able to use this bootloader for testing. It will not boot an OS in its current form.
And here are two photos I took while in this engineering bootloader:
{
"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"
}
This engineering bootloader was found at http://forum.xda-developers.com/showthread.php?t=2155214
I do NOT recommend flashing it unless you know what you are doing. This is a true engineering bootloader and it WILL brick your device very easily if you make a mistake.
kozmikkick said:
Here is the stock Partititon Table for HTC One (M7)
Code:
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1 sbl1
179 2 256 mmcblk0p2 sbl2
179 3 130671 mmcblk0p3 pg1fs
179 4 1 mmcblk0p4 ?
179 5 16 mmcblk0p5 board_info
179 6 256 mmcblk0p6 mfg
179 7 15577 mmcblk0p7 pg2fs
179 8 256 mmcblk0p8 sbl2_update
179 9 1024 mmcblk0p9 sbl3
179 10 256 mmcblk0p10 rpm
179 11 2048 mmcblk0p11 tz
179 12 2080 mmcblk0p12 hboot
179 13 5120 mmcblk0p13 sp1
179 14 1024 mmcblk0p14 wifi
179 15 1024 mmcblk0p15 dsps
179 16 61441 mmcblk0p16 adsp
179 17 8190 mmcblk0p17 radio_config
179 18 32768 mmcblk0p18 reserve_1
179 19 1022 mmcblk0p19 misc
179 20 4096 mmcblk0p20 modem_st1
179 21 4096 mmcblk0p21 modem_st2
179 22 20480 mmcblk0p22 devlog
179 23 4 mmcblk0p23 debug_config
179 24 256 mmcblk0p24 pdata
179 25 16 mmcblk0p25 control
179 26 1280 mmcblk0p26 local
179 27 64 mmcblk0p27 extra
179 28 1024 mmcblk0p28 cdma_record
179 29 98727 mmcblk0p29 reserve
179 30 54270 mmcblk0p30 reserve_2
179 31 76800 mmcblk0p31 radio
179 32 98303 mmcblk0p32 ?
179 33 16384 mmcblk0p33 boot
179 34 16383 mmcblk0p34 recovery
179 35 1900543 mmcblk0p35 system
179 36 655359 mmcblk0p36 cache
179 37 27262976 mmcblk0p37 userdata
Click to expand...
Click to collapse
mmcblk0p4 or mmcblk0p32 can be for CIR.
mike1986. said:
mmcblk0p4 or mmcblk0p32 can be for CIR.
Click to expand...
Click to collapse
I could see that for mmcblk0p4 but would seem odd that 32 would be that with it being so large.
Though 32 does seem important as it's missing in the eng hboot and that's the only missing partition that could make it not boot.
Any thoughts on a workaround?
Sent from my HTC One using xda premium
kozmikkick said:
I could see that for mmcblk0p4 but would seem odd that 32 would be that with it being so large.
Though 32 does seem important as it's missing in the eng hboot and that's the only missing partition that could make it not boot.
Any thoughts on a workaround?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
True, mmcblk0p4 seems better candidate for CIR.
Maybe dzdata for 32?
BTW how comes DNA has EXT3 partitions by default?
mike1986. said:
True, mmcblk0p4 seems better candidate for CIR.
Maybe dzdata for 32?
BTW how comes DNA has EXT3 partitions by default?
Click to expand...
Click to collapse
No clue about DNA. I only have the m7.
The 3rd codeset that I posted is from the eng hboot. It's what I used to figure out the labels for the partitions. Combined with the adb partition list.
It'd be nice if our stock hboot had the fastboot oem listpartitions option.
Sent from my HTC One using xda premium
mike1986. said:
True, mmcblk0p4 seems better candidate for CIR.
Maybe dzdata for 32?
BTW how comes DNA has EXT3 partitions by default?
Click to expand...
Click to collapse
Had some free time. So I dumped 32. And its a completely empty partition. Not sure why they added it to our partition table in final release but it is completely unused.
I also dumped 30. Which I noted to be a bit different in block size between the eng and ship hboots.
This paritition was interesting. There is a lot of memory text as well as text regarding the modem/lte/wdma. I'm thinking this could be a cache partition for the radio? Though I could be easily wrong. May try and get a bump of this partition from butterfly and see what it does on m7.
Also did a hexdiff between the eng and stock hboot. It looks like the stock hboot has all of the commands that the eng hboot has, its just that they aren't unlocked for a SHIP hboot.
One other thing I just noticed on the ENG HBoot is that even though it picks up that my device is M7_UL it assigns it as PN07200 which is for M7_WLS. It should be PN07100.
I believe that this is the reason why it won't boot on OS on our device.
hboots won't work if it fails the assertion of partition tables. A single partition missing or at the very least an incorrect block size on a specific partition. I already worked on this when I ported the engineering hboot of HTC Sensation to Mytouch 4g slide and it took me weeks just reverse engineering the block sizes.
And yeah... The issue I had to solve was only an mismatched block size of the cache partition. Now I don't know how hard it is reverse engineeering it by snipping a single partition and mapping all the partitions above mmcblk0p33 and up. Plus I'm not even sure about the block sizes.
It would be easier if we could at least get the eng hboot of those htc one which was distributed before release.
And ohh messing with it without a jtag box is like walking in a rope crossing a 100meter building lol!
Riyal said:
hboots won't work if it fails the assertion of partition tables. A single partition missing or at the very least an incorrect block size on a specific partition. I already worked on this when I ported the engineering hboot of HTC Sensation to Mytouch 4g slide and it took me weeks just reverse engineering the block sizes.
And yeah... The issue I had to solve was only an mismatched block size of the cache partition. Now I don't know how hard it is reverse engineeering it by snipping a single partition and mapping all the partitions about mmcblk0p33 and up. Plus I'm not even sure about the block sizes.
It would be easier if we could at least get the eng hboot of those htc one which was distributed before release.
And ohh messing with it without a jtag box is like walking in a rope crossing a 100meter building lol!
Click to expand...
Click to collapse
Indeed. I've dug into it a bit. But theres no way I'll flash a modified hboot lol. Quick way to brick for sure!
It did boot once into the off. Not sure how but it did finish loading. Slow as help. I hard booted back into fastboot and reverted hboots.
Sent from my HTC One using xda premium
My thought initially was that it was going to change the partition table sizes automatically like it did on the g2 when flashing the eng desire z hboot on it.
Sent from my HTC One using xda premium
kozmikkick said:
My thought initially was that it was going to change the partition table sizes automatically like it did on the g2 when flashing the eng desire z hboot on it.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
it would be great if that's the case Maybe then we could implement a real external sdcard with mass usb storage
Riyal said:
it would be great if that's the case Maybe then we could implement a real external sdcard with mass usb storage
Click to expand...
Click to collapse
Doubtful but maybe.
Sent from my HTC One using xda premium
mike1986. said:
True, mmcblk0p4 seems better candidate for CIR.
Maybe dzdata for 32?
BTW how comes DNA has EXT3 partitions by default?
Click to expand...
Click to collapse
Good catch Mike! It would seem that HTC used ext3 during the development phase.
This might just boot if system cache and data are converted to ext3 since that are current ext4
Sent from my HTC One using xda premium
Mmcbk0p4[Extended]
Mmcbk0p4 is extended partition from 4 - mmcblk0p38. Gsm vs CDMA table differs also
Gsm-
System - mmcbl0p35
Boot - mmcblk0p33
On CDMA
Mmcblk0p35 - boot
Mmcblk0p33 - radio
That is why eng hboot on sprint variant won't boot or recognize radio also
mike1986. said:
mmcblk0p4 or mmcblk0p32 can be for CIR.
Click to expand...
Click to collapse
P4 is empty apart from CID and IMEI and one line encrypted bytes.
This partition was used on 2012 One Series phones to hack SCID into the phone as it wasn't protected there. It now seems to be. The CID offset is still the same as on the older phones.
dzdata files might be a filesystem layout for the the data partition, which is P37. Hence the wipe of the sdcard when flashing those images. There is always 3 flavors: 16, 32 and 64 which i assume correspond to available storage sizes. Well that is my explanation of those otherwise pretty odd images.
Cir.img is located in /system/etc after boot and seems to have no partition on its own. Opened with a hex editor it only reveals nicely ordered codes that look like remote control codes for various devices. I do not understand how RUUmode can inject an image file into an existing partition, not flashing a partition. I understand this must be possible as we have seen various OTA's with an upacked system being flashed, yet those use a meta-inf structure to accomplish that, the RUUmode.zips don't. So i am not too sure about cir.img myself.
Hope those thoughts can help you guys a little.
I picked up some vital info here myself and wish to say thanks.
[EDIT]
Here is my partition listing. I added data i found in Post #1, mainly pg2fs and some others that cannot be seen by cat /proc/emmc.
Hope i can help with this a little and thanks again!
https://docs.google.com/spreadsheet/ccc?key=0AjqWaJywIe10dExiQ0gtZmhBQ0F5NmY1V2pJVkMwdkE&usp=sharing
hi all!!, I have a questions
You know if any partition brings USB drivers?
I have a ONE with more than a month with a problem, not at all my PC detects a USB connection, but if I can connect it to the wall to charge it.
And also detects FASTBOOT mode "fastboot flash recovery recovery.img" for example, so I doubt it's any physical damage, since I detect FASTBOOT mode,
Can be damaged any partition with this libs or else?
I have flashed the official RUU and not fixed,
did ruus flashed all partitions?
bovoro said:
hi all!!, I have a questions
You know if any partition brings USB drivers?
I have a ONE with more than a month with a problem, not at all my PC detects a USB connection, but if I can connect it to the wall to charge it.
And also detects FASTBOOT mode "fastboot flash recovery recovery.img" for example, so I doubt it's any physical damage, since I detect FASTBOOT mode,
Can be damaged any partition with this libs or else?
I have flashed the official RUU and not fixed,
did ruus flashed all partitions?
Click to expand...
Click to collapse
There's probably nothing wrong with the phone. Did you try different USB cables and ports? What about downloading and reinstalling the USB drivers? I had a problem with USB and installing the drivers I found on here fixed it.
yes, I've tried usb cable motorola, nokia, samsung, other computers, installing, uninstalling drivers, to no avail, note that part of the problem is constantly entering Car Dock mode, I think I see this behavior with HTC one X and EVOs.
Or the fifth pin is damaged is the mode that detects CAR DOCK.
bovoro said:
yes, I've tried usb cable motorola, nokia, samsung, other computers, installing, uninstalling drivers, to no avail, note that part of the problem is constantly entering Car Dock mode, I think I see this behavior with HTC one X and EVOs.
Or the fifth pin is damaged is the mode that detects CAR DOCK.
Click to expand...
Click to collapse
Hmm... It sounds like your phone's USB port might be damaged... Normally it takes at least a year for that to happen, but I can't see any other reason why your phone have that problem with all computers and cables. The thing that confuses me is that every phone with a broken USB port that I've seen would not charge either, so I don't know why you can still charge and use fastboot with no problems...
It might be time to restore the stock ROM/firmware and send it in...
Related
I Am Not Responsible For Breaking Your Device, Take Your Own Risks ^__^
Click to expand...
Click to collapse
Hi Folks
Please Follow Below;
To Set SuperCID Or Change Any CID For That Fact;
1. Check you are S-OFF; Follow Moonshine OR Revolutionaries Guide.
2. Reboot Into Bootloader & Check You Are Fastboot USB
3. Type As Below
Code:
fastboot oem writecid 11111111
(Or whatever CID you want to have from the list in the second post)
4. Reboot Into Bootloader Again & Check You Are Fastboot USB
5. Check You Have Your Chosen CID;
Code:
fastboot getvar cid
(This Should Confirm The CID you chose from the list in the second post)
6. Reboot Back To Android By Typing
Code:
fastboot reboot
Files attached in post should anyone be a bit lost
CID List
Description CID
ALL 11111111
BM BM___001
Bouygues-Telecom BOUYG201
Brightstar-SPA BSTAR301
Entel BSTAR306
Tigo BSTAR307
Movistar BSTAR308
Brightstar-PTB BSTAR502
Chunghwa-Taiwan CHT__601
ATT CWS__001
CA_Dave DAVE_001
DCM DOCOM801
DOPOD DOPOD701
Fastweb-IT FASTW401
GOOGLE GOOGL001
H3G-UK H3G__001
H3G-ROI H3G__003
H3G-AT H3G__106
H3G-Italy H3G__402
H3G-DAN H3G__F05
H3G-SWE H3G__G04
HTC-WWE HTC__001
VODA-Africa-South HTC__016
HTC-Australia HTC__023
HTC-EastEurope HTC__032
HTC-Asia-SEA HTC__037
AirTel-India HTC__038
HTC-India HTC__038
HTC-Asia-SEA-WWE HTC__044
HTC-Tesco HTC__052
HTC Israel HTC__K18
HTC-GER HTC__102
HTC-FRA HTC__203
HTC-FRA-Bouygues HTC__247
HTC-FRA-NRJ HTC__249
HTC-SPA HTC__304
HTC-ITA HTC__405
HTC-PTG HTC__506
TWM-TW HTC__621
Asia-HK-CHT HTC__622
HTC-Russia HTC__A07
HTC-Poland HTC__B25
HTC-Czech HTC__C24
HTC-Dutch HTC__E11
HTC-BE HTC__E41
HTC-Denmark HTC__F08
HTC-Sweden HTC__G09
HTC-Norway HTC__H10
HTC-GCC (Gulf Cooperation) HTC__J15
HTC-Turkey HTC__M27
HTC-ELL HTC__N34
HTC-Nor HTC__Y13
Open-Channel HTCCN701
CT HTCCN702
CU HTCCN703
Hutch-Australia HUTCH001
O2-UK O2___001
O2-DE O2___102
Optus-Australia OPTUS001
ORANGE-UK ORANG001
ORANGE-SK ORANG006
ORANGE-PO ORANG008
ORANGE-BE ORANG012
ORANGE-CH-GER ORANG104
ORANGE-AT ORANG113
ORANGE-French ORANG202
ORANGE-CH-FRA ORANG203
ORANGE-ES ORANG309
ORANGE-PL ORANGB10
Rogers ROGER001
SKT_KR SKT__901
SMC-Voda-HK SMCVD001
HTC-Singapore HTC__044
TELEF-Spain TELEF301
Telstra TELST001
TELUS TELUS001
TIM-Italy TIM__401
TMNL T-MOB003
TMCZ T-MOB004
TMUK T-MOB005
TMHR T-MOB006
TMH T-MOB007
TMSK T-MOB008
Era T-MOB009
TMUS T-MOB010
TMD T-MOB101
TMA T-MOB102
TMMK T-MOBL11
CA_Videotron VIDEO001
VIRGIN-UK VIRGI001
VODA-UK VODAP001
VODA-Greece VODAP006
VODA-Swisscom-WWE VODAP015
VODA-Ireland VODAP019
VODA-Australia VODAP021
VODA-New-Zealand VODAP022
VODA-Proximus VODAP024
VODA-SA VODAP026
VODA-Germany VODAP102
VODA-Swisscom-DE VODAP110
VODA-Mobilkom VODAP120
VODA-DE VODAP129
VODA-SFR VODAP203
VODA-Swisscom-FR VODAP212
VODA-Spain VODAP304
VODA-Italy VODAP405
VODA-Swisscom-IT VODAP416
VODA-MTS-RUS VODAPA30
VODA-Portugal VODAPD18
VODA-Netherland VODAPE17
VODA-TR VODAPM27
HTC Australia HTC__039
What CID would HTC_Y13 be?
Theshawty said:
What CID would HTC_Y13 be?
Click to expand...
Click to collapse
HTC__Y13 - Norway I believe / Nordic
Has anyone got dialer issues with super CID enabled?
gianton said:
Has anyone got dialer issues with super CID enabled?
Click to expand...
Click to collapse
Nope , not here,
Enlighten me what seems to be the issue?
Mine is CID-HTC_044
It's for HTC-Asia-SEA-WWE HTC__044 or HTC-Singapore HTC__044 ?
My RUU before using HTC-Asia-SEA-WWE ! !?
Good Guide, I have a question though, now we have s-off and supercid, can we put any cid on our phone for eg my phone came with H3G__001, can I put command for changing it to HTC__001
dryspuri said:
Good Guide, I have a question though, now we have s-off and supercid, can we put any cid on our phone for eg my phone came with H3G__001, can I put command for changing it to HTC__001
Click to expand...
Click to collapse
Yep thats what SuperCID is for it gives you the opportunity to amend you "Region Code" if you want to call it that
wzu7 said:
Mine is CID-HTC_044
It's for HTC-Asia-SEA-WWE HTC__044 or HTC-Singapore HTC__044 ?
My RUU before using HTC-Asia-SEA-WWE ! !?
Click to expand...
Click to collapse
It can mean both have a look at 038 - India
it has the same for 2 x carriers and WWE edition
fkofilee said:
Nope , not here,
Enlighten me what seems to be the issue?
Click to expand...
Click to collapse
Some users with the Dev edition reported after changing to super CID that about an hour later got their dialer disabled and a message of formatting data partition. Reverting to their old CID fixed that.
gianton said:
Some users with the Dev edition reported after changing to super CID that about an hour later got their dialer disabled and a message of formatting data partition. Reverting to their old CID fixed that.
Click to expand...
Click to collapse
Nope nothing on that here... 4.1.2 bug possibly? Or 4.2.2?
fkofilee said:
Nope nothing on that here... 4.1.2 bug possibly? Or 4.2.2?
Click to expand...
Click to collapse
OK great, I think it's device edition related as none other users reported that. Going to revert my CID too. :good:
Don`t want to ruin the Super CID party, but whether we have trie Super CID or not, remains to be seen. It`s true, that both by hex editing the partition or fastboot command now we get Super CID in fastboot, but what is interesting, that when double checking via adb in live system with adb shell getprop "ro.cid", you will still get your original CID. So it seems CID is stored in 2 different locations now and that fastboot forcing the new CID does not fully finish the task.
Try yourself in adb with:
adb shell getprop "ro.cid"
So old CID still hides in one of these...
PHP:
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 61441 mmcblk0p16
179 17 8190 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 1022 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 20480 mmcblk0p22
179 23 4 mmcblk0p23
179 24 256 mmcblk0p24
179 25 16 mmcblk0p25
179 26 1280 mmcblk0p26
179 27 64 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 98727 mmcblk0p29
179 30 54270 mmcblk0p30
179 31 76800 mmcblk0p31
179 32 98303 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 16383 mmcblk0p34
179 35 1900543 mmcblk0p35
179 36 655359 mmcblk0p36
179 37 27262976 mmcblk0p37
he_stheone64 said:
Don`t want to ruin the Super CID party, but whether we have trie Super CID or not, remains to be seen. It`s true, that both by hex editing the partition or fastboot command now we get Super CID in fastboot, but what is interesting, that when double checking via adb in live system with adb shell getprop "ro.cid", you will still get your original CID. So it seems CID is stored in 2 different locations now and that fastboot forcing the new CID does not fully finish the task.
Try yourself in adb with:
adb shell getprop "ro.cid"
So old CID still hides in one of these...
PHP:
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 61441 mmcblk0p16
179 17 8190 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 1022 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 20480 mmcblk0p22
179 23 4 mmcblk0p23
179 24 256 mmcblk0p24
179 25 16 mmcblk0p25
179 26 1280 mmcblk0p26
179 27 64 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 98727 mmcblk0p29
179 30 54270 mmcblk0p30
179 31 76800 mmcblk0p31
179 32 98303 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 16383 mmcblk0p34
179 35 1900543 mmcblk0p35
179 36 655359 mmcblk0p36
179 37 27262976 mmcblk0p37
Click to expand...
Click to collapse
Well fella you're wrong on that one ^__^
Just done it and it came back "11111111"
However you are right and it has been an issue before :/
Done!
he_stheone64 said:
Don`t want to ruin the Super CID party, but whether we have trie Super CID or not, remains to be seen. It`s true, that both by hex editing the partition or fastboot command now we get Super CID in fastboot, but what is interesting, that when double checking via adb in live system with adb shell getprop "ro.cid", you will still get your original CID. So it seems CID is stored in 2 different locations now and that fastboot forcing the new CID does not fully finish the task.
Try yourself in adb with:
adb shell getprop "ro.cid"
So old CID still hides in one of these...
PHP:
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 61441 mmcblk0p16
179 17 8190 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 1022 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 20480 mmcblk0p22
179 23 4 mmcblk0p23
179 24 256 mmcblk0p24
179 25 16 mmcblk0p25
179 26 1280 mmcblk0p26
179 27 64 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 98727 mmcblk0p29
179 30 54270 mmcblk0p30
179 31 76800 mmcblk0p31
179 32 98303 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 16383 mmcblk0p34
179 35 1900543 mmcblk0p35
179 36 655359 mmcblk0p36
179 37 27262976 mmcblk0p37
Click to expand...
Click to collapse
Yes I did what you said and it shows my old CID. Maybe this file stayed there and after a ROM update will go away.
he_stheone64 said:
Don`t want to ruin the Super CID party, but whether we have trie Super CID or not, remains to be seen. It`s true, that both by hex editing the partition or fastboot command now we get Super CID in fastboot, but what is interesting, that when double checking via adb in live system with adb shell getprop "ro.cid", you will still get your original CID. So it seems CID is stored in 2 different locations now and that fastboot forcing the new CID does not fully finish the task.
Try yourself in adb with:
adb shell getprop "ro.cid"
So old CID still hides in one of these...
PHP:
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 61441 mmcblk0p16
179 17 8190 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 1022 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 20480 mmcblk0p22
179 23 4 mmcblk0p23
179 24 256 mmcblk0p24
179 25 16 mmcblk0p25
179 26 1280 mmcblk0p26
179 27 64 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 98727 mmcblk0p29
179 30 54270 mmcblk0p30
179 31 76800 mmcblk0p31
179 32 98303 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 16383 mmcblk0p34
179 35 1900543 mmcblk0p35
179 36 655359 mmcblk0p36
179 37 27262976 mmcblk0p37
Click to expand...
Click to collapse
I did what you say, but before being S-OFF and super-cid-ed, i was with HTC__203 CID.
Now verified in fastboot and with your method, both are giving me the same result CID 11111111.
I've to say that i'm on ARHD10.1. Does it affect the manner to obtain the SUPER-CID?...Really don't know.
he_stheone64 said:
Don`t want to ruin the Super CID party, but whether we have trie Super CID or not, remains to be seen. It`s true, that both by hex editing the partition or fastboot command now we get Super CID in fastboot, but what is interesting, that when double checking via adb in live system with adb shell getprop "ro.cid", you will still get your original CID. So it seems CID is stored in 2 different locations now and that fastboot forcing the new CID does not fully finish the task.
Try yourself in adb with:
adb shell getprop "ro.cid"
So old CID still hides in one of these...
PHP:
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 61441 mmcblk0p16
179 17 8190 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 1022 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 20480 mmcblk0p22
179 23 4 mmcblk0p23
179 24 256 mmcblk0p24
179 25 16 mmcblk0p25
179 26 1280 mmcblk0p26
179 27 64 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 98727 mmcblk0p29
179 30 54270 mmcblk0p30
179 31 76800 mmcblk0p31
179 32 98303 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 16383 mmcblk0p34
179 35 1900543 mmcblk0p35
179 36 655359 mmcblk0p36
179 37 27262976 mmcblk0p37
Click to expand...
Click to collapse
Mine is saying original CID too, O2___001
Isn't Australia HTC__039?
Sent from my HTC One using Tapatalk 4 Beta
H377 said:
Hi Scotty,
First of all really thank you for your kind contribution to the scene!
I have a HTC One DUAL SIM M7C_DUG 802w HTC__032 HBOOT 2.27.000 OS:2.41.402.3.
Recently I was playing around with temproot but couldn't reach my goal I wanted to try if I can permanently root the device somehow from the ADB session. Just playing....
Normally the temproot gives root privileges only within the ADB session you started it, nothing else - as far as I understood. I have to confess that I have mounted the system and root as RW and make some dirs but removed them. And even after a reboot everything was set back to normal: all the new files, dirs were removed. Due to the S-ON I guess...
And now the TAMPERED text is there. Even if the modifications are not on the flash anymore. Is this normal? I mean does the device check the modifications on the fly and if you change anything on the system partition or anywhere else it will flag the device as TAMPERED? I'm still S-ON, lock bootloader....
And I was wondering if I don't get the 4.4.2 OTA becasue of the tampered flag? Can this be?
If yes then I'm thinking of using the Firewater pack to achieve S-OFF and then remove the TAMPERED flag and maybe go back to S-ON to be able to receive the OTA someday.
Do I need anyway to go back to S-ON to receive the OTA? Or is it enough if the bootloader is locked?
Many thanks for your kind reply in advance!
Click to expand...
Click to collapse
starting a new thread for some info...
scotty1223 said:
starting a new thread for some info...
Click to expand...
Click to collapse
ok, @H377 lets start by figuring out where things are on your device.
if you could paste the results of:
adb shell
cat /proc/emmc
cat proc/partitions
scotty1223 said:
ok, @H377 lets start by figuring out where things are on your device.
Click to expand...
Click to collapse
Hey Scotty,
Thanks for helping me out!!!
Code:
cat /proc/emmc
dev: size erasesize name
mmcblk0p20: 000ffa00 00000200 "misc"
mmcblk0p37: 00fffe00 00000200 "recovery"
mmcblk0p36: 01000000 00000200 "boot"
mmcblk0p38: 93fffc00 00000200 "system"
mmcblk0p27: 00140200 00000200 "local"
mmcblk0p39: 17fffe00 00000200 "cache"
mmcblk0p40: 670000000 00000200 "userdata"
mmcblk0p23: 01400000 00000200 "devlog"
mmcblk0p25: 00040000 00000200 "pdata"
mmcblk0p28: 00010000 00000200 "extra"
mmcblk0p34: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p21: 00400000 00000200 "modem_st1"
mmcblk0p22: 00400000 00000200 "modem_st2"
mmcblk0p30: 00040000 00000200 "skylink"
mmcblk0p31: 01900000 00000200 "carrier"
mmcblk0p29: 00100000 00000200 "cdma_record"
mmcblk0p19: 01affe00 00000200 "reserve_1"
mmcblk0p33: 034ffa00 00000200 "reserve_2"
mmcblk0p35: 05fffc00 00000200 "reserve_3"
mmcblk0p32: 04729a00 00000200 "reserve"
Code:
cat proc/partitions
major minor #blocks name
7 0 44730 loop0
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 61441 mmcblk0p16
179 17 8190 mmcblk0p17
179 18 5120 mmcblk0p18
179 19 27647 mmcblk0p19
179 20 1022 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 4096 mmcblk0p22
179 23 20480 mmcblk0p23
179 24 4 mmcblk0p24
179 25 256 mmcblk0p25
179 26 16 mmcblk0p26
179 27 1280 mmcblk0p27
179 28 64 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 256 mmcblk0p30
179 31 25600 mmcblk0p31
179 32 72870 mmcblk0p32
179 33 54270 mmcblk0p33
179 34 76800 mmcblk0p34
179 35 98303 mmcblk0p35
179 36 16384 mmcblk0p36
179 37 16383 mmcblk0p37
179 38 2424831 mmcblk0p38
179 39 393215 mmcblk0p39
179 40 27000832 mmcblk0p40
179 64 31341568 mmcblk1
179 65 31340544 mmcblk1p1
254 0 44730 dm-0
cool,thanks.
to back up your stock recovery,you will run your temp root and at a # prompt enter:
dd if=/dev/block/mmcblk0p37 of=/sdcard/mmcblk0p37
that will make a copy of your stock recovery on your sd card. youll want to copy it over to your PC where you can change the name to "stock-recovery.img" or something to that affect,and keep it safe.
let me take a quick look at the rest of the partitions,and see how they differ.
scotty1223 said:
cool,thanks.
to back up your stock recovery,you will run your temp root and at a # prompt enter:
dd if=/dev/block/mmcblk0p37 of=/sdcard/mmcblk0p37
that will make a copy of your stock recovery on your sd card. youll want to copy it over to your PC where you can change the name to "stock-recovery.img" or something to that affect,and keep it safe.
let me take a quick look at the rest of the partitions,and see how they differ.
Click to expand...
Click to collapse
Thank you sir!
Will give it a try
ok,so this is our best guess as to what the filled out partition table looks like,based on the locations/sizes of partitions compared to the m7 table i have:
Code:
cat proc/partitions
major minor #blocks name
7 0 44730 loop0
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1 sbl1
179 2 256 mmcblk0p2 sbl2
179 3 130671 mmcblk0p3 pg1fs
179 4 1 mmcblk0p4 ?
179 5 16 mmcblk0p5 board_info
179 6 256 mmcblk0p6 mfg
179 7 15577 mmcblk0p7 pg2fs
179 8 256 mmcblk0p8 sbl2_update
179 9 1024 mmcblk0p9 sbl3
179 10 256 mmcblk0p10 rpm
179 11 2048 mmcblk0p11 tz
179 12 2080 mmcblk0p12 hboot
179 13 5120 mmcblk0p13 sp1
179 14 1024 mmcblk0p14 wifi
179 15 1024 mmcblk0p15 dsps
179 16 61441 mmcblk0p16 adsp
179 17 8190 mmcblk0p17 radio_config
179 18 5120 mmcblk0p18 wcnss
179 19 27647 mmcblk0p19 reserve_1
179 20 1022 mmcblk0p20 misc
179 21 4096 mmcblk0p21 modem_st1
179 22 4096 mmcblk0p22 modem_st2
179 23 20480 mmcblk0p23 devlog
179 24 4 mmcblk0p24 debug_config
179 25 256 mmcblk0p25 pdata
179 26 16 mmcblk0p26 control
179 27 1280 mmcblk0p27 local
179 28 64 mmcblk0p28 extra
179 29 1024 mmcblk0p29 cdma_record
179 30 256 mmcblk0p30 skylink
179 31 25600 mmcblk0p31 carrier
179 32 72870 mmcblk0p32 reserve
179 33 54270 mmcblk0p33 reserve_2
179 34 76800 mmcblk0p34 radio
179 35 98303 mmcblk0p35 reserve_3
179 36 16384 mmcblk0p36 boot
179 37 16383 mmcblk0p37 recovery
179 38 2424831 mmcblk0p38 system
179 39 393215 mmcblk0p39 cache
179 40 27000832 mmcblk0p40 userdata
179 64 31341568 mmcblk1
179 65 31340544 mmcblk1p1
254 0 44730 dm-0
you can back them all up,if you want to. just change the x to the number of each partition:
dd if=/dev/block/mmcblk0px of=/sdcard/mmcblk0px
aka,
dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1
dd if=/dev/block/mmcblk0p2 of=/sdcard/mmcblk0p2
and so on.
be aware that the bigger ones will take several minutes to copy,so its not hung if it seems to be taking forever. after youre done move them all to your PC and rename them according to the above table. if you need help here,let me know,but you seem to have a pretty good idea what youre doing.
you can make up your own unsinged ruu(i did this same thing before t mobile had released ruus).
in the home made ruu,youll want to include:
-an android info document(well work on that later)
-adsp
-boot
-hboot
-radio
-recovery
-rpm
-sbl1
-sbl2
-sbl3
-sp1
-system
-tz
i would like to look at mmcblk: 3,4,6,7,and 12 so if you upload those somewhere,and pm me a link(they have some personal info like esn,meid,etc so dont post a link publicly)
hopefully this will all help with the reservations you have about s off,and possibly be of use to some other folks as well. holler if you have questions
scotty1223 said:
ok,so this is our best guess as to what the filled out partition table looks like,based on the locations/sizes of partitions compared to the m7 table i have:
i would like to look at mmcblk: 3,4,6,7,and 12 so if you upload those somewhere,and pm me a link(they have some personal info like esn,meid,etc so dont post a link publicly)
hopefully this will all help with the reservations you have about s off,and possibly be of use to some other folks as well. holler if you have questions
Click to expand...
Click to collapse
Thank you so much really!
I will dump those partitions and will up load it somewhere but I guess it will be only tomorrow. Already started dumping the system and it really takes some time
Thank you so much for your kind help!!!!
H377 said:
Thank you so much really!
I will dump those partitions and will up load it somewhere but I guess it will be only tomorrow. Already started dumping the system and it really takes some time
Thank you so much for your kind help!!!!
Click to expand...
Click to collapse
youre quite welcome for the help. no hurry on the uploads,its more of a curiosity than anything,im pretty sure they will be the same as what ive allready seen.
also,just to make sure i havent accidentally given any false impressions,you will only be able to flash your home made ruu after you s off,as it will not have htcs official signiture and will fail the signiture check on an s on device
also,if you dont mind at some point(no hurry) can you paste for me the results of
fastboot getvar all
make sure to xxx out your esn,meid,imie
scotty1223 said:
youre quite welcome for the help. no hurry on the uploads,its more of a curiosity than anything,im pretty sure they will be the same as what ive allready seen.
also,just to make sure i havent accidentally given any false impressions,you will only be able to flash your home made ruu after you s off,as it will not have htcs official signiture and will fail the signiture check on an s on device
also,if you dont mind at some point(no hurry) can you paste for me the results of
fastboot getvar all
make sure to xxx out your esn,meid,imie
Click to expand...
Click to collapse
Hmm this is very strange: If I start the phone in fastboot mode Windows doesn't recognize the device.... Although the drivers are installed....
H377 said:
Hmm this is very strange: If I start the phone in fastboot mode Windows doesn't recognize the device.... Although the drivers are installed....
Click to expand...
Click to collapse
What windows are you running? 8 and 8.1 are prollematic,as is USB 3.0.
You can try unplug/replug and different ports and cables.
Make sure nothing is running on the pc that talk to the phone- HTC sync,pda net,easy tether,even I tunes
Other than that,make sure the phone is in fastboot and not hboot
Sent from my HTC PG09410 using Tapatalk 2
scotty1223 said:
What windows are you running? 8 and 8.1 are prollematic,as is USB 3.0.
You can try unplug/replug and different ports and cables.
Make sure nothing is running on the pc that talk to the phone- HTC sync,pda net,easy tether,even I tunes
Other than that,make sure the phone is in fastboot and not hboot
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
Yeah unfortunately it's Windows 8 so I will try it with Windows 7. Everything else should be just fine.
Is there a guide on how to create the custom RUU?
Any luck?
Sent from my HTC6435LVW using Tapatalk
scotty1223 said:
Any luck?
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
I am on 802w China Unicom
as the topic is 802w, this is my getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: U3.14.3509.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.21.1402.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7cdug
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) cidnum: HTCCN703
(bootloader) battery-status: good
(bootloader) battery-voltage: 3691mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f6d46eca
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
currently I'm on KitKat OS 4.21.1402.3
If necessary I will downgrade to 2.43 (latest Android 4.2.2)
---------- Post added at 07:27 PM ---------- Previous post was at 06:53 PM ----------
H377 said:
Yeah unfortunately it's Windows 8 so I will try it with Windows 7. Everything else should be just fine.
Is there a guide on how to create the custom RUU?
Click to expand...
Click to collapse
to get adb working on Windows 8.1 you need to download and install Update for Windows 8.1 (KB2917929)
scotty1223 said:
Any luck?
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
I am off from home at the moment. I will give it a try on the weekend.
H377 said:
Yeah unfortunately it's Windows 8 so I will try it with Windows 7. Everything else should be just fine.
Is there a guide on how to create the custom RUU?
Click to expand...
Click to collapse
i just realized i didnt answer this. in a nutshell,you will just rename your mmcblkopx files to the corresponding names based on the chard in post 6. ie,youll name mmcblk0p1 to sbl1.img(make sure you type in the .img extension so the files are converted to images) ,mmcblk0p2 to sbl2.img,and so on.
once youre done,youll just put the images,along with an android info text document together and zip them up. the text file well need to find in an OTApkg for your device,or make one up from scratch. it will contain info such as this:
Code:
modelid: PN0713000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__A07
cidnum: HTC__J15
cidnum: HTC__016
mainver: 1.29.401.12
btype:1
aareport:1
hbootpreupdate:3
but it will have info thats relevant to your device. the images you use are up to you,but you can use the ones i suggested,also in post 6,for a fairly complete homemade ruu.
again,you cant flash it while s on,since it doesnt have htcs official siginture. hope that makes sense.
wewenk said:
I am on 802w China Unicom
as the topic is 802w, this is my getvar all
currently I'm on KitKat OS 4.21.1402.3
If necessary I will downgrade to 2.43 (latest Android 4.2.2)
Click to expand...
Click to collapse
no need to downgrade,i just need to look at a cuople partitions. if you guys want to lock/unlock,remove your tampered banner,and change your MID with adb,then i need to look at mmcblk0p3,mmcblk0p6,and mmcblk0p7
@scotty1223 okay so it mean we can build our own RUU?
Can we do it with s-on device? I want to build an Indonesian 802d ruu then
Sent from my HTC 802w using XDA Premium 4 mobile app
wewenk said:
@scotty1223 okay so it mean we can build our own RUU?
Can we do it with s-on device? I want to build an Indonesian 802d ruu then
Sent from my HTC 802w using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No,you can't do it while s on,as everything but boot,system,and recovery is write protected. In order to make a complete ruu as described above,you'll need to be s off.
What you can do while s on is make a mini-ruu of sorts... Consisting of android info document,boot,system,and recovery. You can flash it while unlocked
Sent from my HTC PG09410 using Tapatalk 2
Okay, now what can I help to continue our research to get 802w unlocked without htcdev?
That will be the first goal for this research correct?
So if success, can we get our stock reset? I mean like htc1guru reset
With htcdev, unlock bl will reset to factory, erase internal phone storage, then we losing htcsoundrecorder, flashlight, calculator etc.
With your method, will it reset too?
Sent from my HTC 802w using XDA Premium 4 mobile app
wewenk said:
Okay, now what can I help to continue our research to get 802w unlocked without htcdev?
That will be the first goal for this research correct?
Click to expand...
Click to collapse
No, sorry if I have that impression. No way to unlock without HTC Dev due to s on write protections.
The purpose here is to be able to flip between locked and unlocked easily, without htcdev, after s off.
Also to be able to achieve locked at all... Without manually changing this flag, best you can do using fastboot command is relocked.
Sent from my HTC6435LVW using Tapatalk
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
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
Seeking sonimxp5800 firehose_8920 file
essential-phone ：The thread is closed, this is the tested version of the firmware, the key cannot be verified
Code:
C:\Users\x\Desktop\fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4157000
(bootloader) variant:QRD eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1ff00000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x40000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x2858d0e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xa0000000
(bootloader) serialno:c3cacaf3
(bootloader) kernel:lk
(bootloader) product:QC_REFERENCE_PHONE
all:
finished. total time: 0.111s
XP5812:/ $ cat /proc/partitions
major minor #blocks name
254 0 524288 zram0
179 0 15388672 mmcblk0
179 1 106496 mmcblk0p1
179 2 1 mmcblk0p2
179 3 8 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 256 mmcblk0p10
179 11 256 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 32 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 16 mmcblk0p17
179 18 11264 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 65536 mmcblk0p21
179 22 65536 mmcblk0p22
179 23 1024 mmcblk0p23
179 24 2621440 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 512 mmcblk0p28
179 29 32 mmcblk0p29
179 30 262144 mmcblk0p30
179 31 32 mmcblk0p31
259 0 512 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 32768 mmcblk0p34
259 3 512 mmcblk0p35
259 4 4096 mmcblk0p36
259 5 256 mmcblk0p37
259 6 256 mmcblk0p38
259 7 256 mmcblk0p39
259 8 256 mmcblk0p40
259 9 256 mmcblk0p41
259 10 256 mmcblk0p42
259 11 256 mmcblk0p43
259 12 256 mmcblk0p44
259 13 8 mmcblk0p45
259 14 9020 mmcblk0p46
259 15 7636 mmcblk0p47
259 16 5824 mmcblk0p48
259 17 4820 mmcblk0p49
259 18 10576707 mmcblk0p50
179 32 4096 mmcblk0rpmb
253 0 2580508 dm-0
253 1 10576691 dm-1
XP5812:/ $
XP5812:/ $cat /proc/cpuinfo
Processor : AArch64 Processor rev 4 (aarch64)
processor : 0
BogoMIPS : 38.40
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 1
BogoMIPS : 38.40
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 2
BogoMIPS : 38.40
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 3
BogoMIPS : 38.40
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Hardware : Qualcomm Technologies, Inc MSM8920
XP5812:/ $
what is a firehose file? and what is the zip file attached?
nijohnson said:
what is a firehose file? and what is the zip file attached?
Click to expand...
Click to collapse
This looks very interesting! I have a dead essential I can use this on if you can confirm it works!!!
I have a dead one as well. But I have no idea what to do with the file.
nijohnson said:
what is a firehose file? and what is the zip file attached?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=80465045&postcount=6
nijohnson said:
I have a dead one as well. But I have no idea what to do with the file.
Click to expand...
Click to collapse
Initial Steps
EDL mode refresh firmware
eleotk said:
Initial Steps
EDL mode refresh firmware
Click to expand...
Click to collapse
Initial step #1 - get pasword ((
Does anybody found it?
I can't find password out. Can you just post it directly? Thanks a lot.
One idea.. Has anyone asked Sonim?
They gave me debug images along with flash tools for the XP8 when I asked about a year ago.. Although not as useful as the early (unlockable) debug images provided by eleotk.. Sonim had to verify I was local in the US and it took a few days but was not an issue. We are seeing now that many variations of the debug image exist for the XP8 so I'm sure it's the same case on this XP5812.
They do seem to keep a tighter grip on the XP5s since custom apps require Sonim direct validation/signing but it may be worth a shot since any debug images they provide would have the required mbn file for flashing.
Obviously you need to give them a developer style excuse as they will likely not help if they know your trying to modify the device.
I would ask them myself however the only XP5s I have is a Sprint XP5800 that's working with the ZTE 8920 mbn file. This issue appears unique to the variant I believe? Aside from the XP5823 label - it looks simular on my end.
Code:
XP5823:/ $ su
XP5823:/ # cat /proc/partitions
major minor #blocks name
254 0 524288 zram0
179 0 15388672 mmcblk0
179 1 106496 mmcblk0p1
179 2 1 mmcblk0p2
179 3 8 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 256 mmcblk0p10
179 11 256 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 32 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 16 mmcblk0p17
179 18 11264 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 65536 mmcblk0p21
179 22 65536 mmcblk0p22
179 23 1024 mmcblk0p23
179 24 2621440 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 512 mmcblk0p28
179 29 32 mmcblk0p29
179 30 262144 mmcblk0p30
179 31 32 mmcblk0p31
259 0 512 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 32768 mmcblk0p34
259 3 512 mmcblk0p35
259 4 4096 mmcblk0p36
259 5 256 mmcblk0p37
259 6 256 mmcblk0p38
259 7 256 mmcblk0p39
259 8 256 mmcblk0p40
259 9 256 mmcblk0p41
259 10 256 mmcblk0p42
259 11 256 mmcblk0p43
259 12 256 mmcblk0p44
259 13 8 mmcblk0p45
259 14 9020 mmcblk0p46
259 15 7636 mmcblk0p47
259 16 5824 mmcblk0p48
259 17 4820 mmcblk0p49
259 18 10576707 mmcblk0p50
179 32 4096 mmcblk0rpmb
253 0 10576691 dm-0
XP5823:/ # cat /proc/cpuinfo
Processor : AArch64 Processor rev 4 (aarch64)
processor : 0
BogoMIPS : 38.40
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 1
BogoMIPS : 38.40
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 2
BogoMIPS : 38.40
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 3
BogoMIPS : 38.40
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Hardware : Qualcomm Technologies, Inc MSM8920
XP5823:/ #
Edit.. Missed the bootloader options. The Sprint variant at least seems to be shipped in an unlocked state with secure boot also disabled. This is likely why it trusts the ZTE mbn file.
Code:
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3745000
(bootloader) variant:QRD eMMC
(bootloader) secure:no
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1ff00000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x40000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x2858d0e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xa0000000
(bootloader) model:XP5800
(bootloader) build:5SA.0.2-03-7.1.2-29.03.00
(bootloader) imei:XXXXXXXXXXXXXXX
(bootloader) serialno:XXXXXXXX
(bootloader) kernel:lk
(bootloader) product:QC_REFERENCE_PHONE
all:
finished. total time: 0.030s
Maybe my English is not well written, password: sonimxp5800
smokeyou said:
One idea.. Has anyone asked Sonim?
They gave me debug images along with flash tools for the XP8 when I asked about a year ago.. Although not as useful as the early (unlockable) debug images provided by eleotk.. Sonim had to verify I was local in the US and it took a few days but was not an issue. We are seeing now that many variations of the debug image exist for the XP8 so I'm sure it's the same case on this XP5812.
They do seem to keep a tighter grip on the XP5s since custom apps require Sonim direct validation/signing but it may be worth a shot since any debug images they provide would have the required mbn file for flashing.
Obviously you need to give them a developer style excuse as they will likely not help if they know your trying to modify the device.
I would ask them myself however the only XP5s I have is a Sprint XP5800 that's working with the ZTE 8920 mbn file. This issue appears unique to the variant I believe? Aside from the XP5823 label - it looks simular on my end.
Code:
XP5823:/ $ su
XP5823:/ # cat /proc/partitions
major minor #blocks name
254 0 524288 zram0
179 0 15388672 mmcblk0
179 1 106496 mmcblk0p1
179 2 1 mmcblk0p2
179 3 8 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 256 mmcblk0p10
179 11 256 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 32 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 16 mmcblk0p17
179 18 11264 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 65536 mmcblk0p21
179 22 65536 mmcblk0p22
179 23 1024 mmcblk0p23
179 24 2621440 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 512 mmcblk0p28
179 29 32 mmcblk0p29
179 30 262144 mmcblk0p30
179 31 32 mmcblk0p31
259 0 512 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 32768 mmcblk0p34
259 3 512 mmcblk0p35
259 4 4096 mmcblk0p36
259 5 256 mmcblk0p37
259 6 256 mmcblk0p38
259 7 256 mmcblk0p39
259 8 256 mmcblk0p40
259 9 256 mmcblk0p41
259 10 256 mmcblk0p42
259 11 256 mmcblk0p43
259 12 256 mmcblk0p44
259 13 8 mmcblk0p45
259 14 9020 mmcblk0p46
259 15 7636 mmcblk0p47
259 16 5824 mmcblk0p48
259 17 4820 mmcblk0p49
259 18 10576707 mmcblk0p50
179 32 4096 mmcblk0rpmb
253 0 10576691 dm-0
XP5823:/ # cat /proc/cpuinfo
Processor : AArch64 Processor rev 4 (aarch64)
processor : 0
BogoMIPS : 38.40
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 1
BogoMIPS : 38.40
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 2
BogoMIPS : 38.40
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 3
BogoMIPS : 38.40
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Hardware : Qualcomm Technologies, Inc MSM8920
XP5823:/ #
Edit.. Missed the bootloader options. The Sprint variant at least seems to be shipped in an unlocked state with secure boot also disabled. This is likely why it trusts the ZTE mbn file.
Code:
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3745000
(bootloader) variant:QRD eMMC
(bootloader) secure:no
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1ff00000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x40000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x2858d0e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xa0000000
(bootloader) model:XP5800
(bootloader) build:5SA.0.2-03-7.1.2-29.03.00
(bootloader) imei:XXXXXXXXXXXXXXX
(bootloader) serialno:XXXXXXXX
(bootloader) kernel:lk
(bootloader) product:QC_REFERENCE_PHONE
all:
finished. total time: 0.030s
Click to expand...
Click to collapse
It seems that I should find the Sprint version XP5800 easier, XP5800 is too little information.
Please forgive my lack of knowledge. This file/process is not something that could fix a bricked phone, correct?
nijohnson said:
Please forgive my lack of knowledge. This file/process is not something that could fix a bricked phone, correct?
Click to expand...
Click to collapse
Yes, refill the wrong partition
Essential_Phone 9008 download
1. First you need to install QPST, and then confirm the following files in the QPST installation directory.
D:\Program Files (x86)\Qualcomm\QPST\bin
QFIL.exe
Fhloader.exe
QSaharaServer.exe
1
2
2. The device needs to switch to port 9008.
3 Download official file extract
https://storage.googleapis.com/essential-static/PH1-Images-QP1A.191005.014.zip
4 I will release 4 files and extract them into the official file.
5 Running QFIL
Set to see pictures
@eleotk something ent wrong... (
st.noigel said:
@eleotk something ent wrong... (
Click to expand...
Click to collapse
devicetype:ufs
eleotk said:
Essential_Phone 9008 download
1. First you need to install QPST, and then confirm the following files in the QPST installation directory.
D:\Program Files (x86)\Qualcomm\QPST\bin
QFIL.exe
Fhloader.exe
QSaharaServer.exe
1
2
2. The device needs to switch to port 9008.
3 Download official file extract
https://storage.googleapis.com/essential-static/PH1-Images-QP1A.191005.014.zip
4 I will release 4 files and extract them into the official file.
5 Running QFIL
Set to see pictures
Click to expand...
Click to collapse
I guess I don't understand? I can't get Qsahara to work? I have everything downloaded and my screen is the same as yours?
tha_mechanic said:
I guess I don't understand? I can't get Qsahara to work? I have everything downloaded and my screen is the same as yours?
Click to expand...
Click to collapse
https://forum.xda-developers.com/z5.../restore-stock-image-lock-bootloader-t3888785
https://mirrors.lolinet.com/software/windows/Qualcomm/QPST/
eleotk said:
https://forum.xda-developers.com/z5.../restore-stock-image-lock-bootloader-t3888785
https://mirrors.lolinet.com/software/windows/Qualcomm/QPST/
Click to expand...
Click to collapse
It looks like my PH-1 is completele dead (
P.S. I`ll try ahain with another PC )
St.Noigel said:
It looks like my PH-1 is completele dead (
P.S. I`ll try ahain with another PC )
Click to expand...
Click to collapse
Replace the file, still can't pass my verification, end