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
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
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...
Hi guys,
I am in desperate need of a raw img of mmcblk0. All I need one of you to do is get an adb shell or in terminal emulator with root type:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img count=524288
This creates a raw image dump I can use to help unbrick my device. It does NOT contain any sensitive data like IMEI or ESN, etc... I need MJE on Verizon Note 3 specifically. Thank you very much in advanced!
EDIT: 2/14 11:15am CST I am still in need of MJE N900V image. Surely would appreciate anyone with the time.
ryanbg said:
Hi guys,
I am in desperate need of a raw img of mmcblk0. All I need one of you to do is get an adb shell or in terminal emulator with root type:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img
This creates a raw image dump I can use to help unbrick my device. It does NOT contain any sensitive data like IMEI or ESN, etc... I need MJE on Verizon Note 3 specifically. Thank you very much in advanced!
Click to expand...
Click to collapse
Dev Edition matter? I can offer one up if that is acceptable
TechSavvy2 said:
Dev Edition matter? I can offer one up if that is acceptable
Click to expand...
Click to collapse
It's worth a shot, I sure would appreciate it.
/dev/mmcblk0 is the entire device - 32 GB
Is that really what you mean?
ryanbg said:
It's worth a shot, I sure would appreciate it.
Click to expand...
Click to collapse
aight, give me a minute
Edit: Sorry give me another minute, had to re-root really quick
Edit: PS, any other dd's you want me to run for you while I'm at it?
---------- Post added 14th February 2014 at 12:12 AM ---------- Previous post was 13th February 2014 at 11:58 PM ----------
bftb0 said:
/dev/mmcblk0 is the entire device - 32 GB
Is that really what you mean?
Click to expand...
Click to collapse
This.
TechSavvy2 said:
aight, give me a minute
Edit: Sorry give me another minute, had to re-root really quick
Edit: PS, any other dd's you want me to run for you while I'm at it?
---------- Post added 14th February 2014 at 12:12 AM ---------- Previous post was 13th February 2014 at 11:58 PM ----------
This.
Click to expand...
Click to collapse
Cancel that!!! I gave you a bad command. Just delete unbrick.img
ryanbg said:
Cancel that!!! I gave you a bad command. Just delete unbrick.img
Click to expand...
Click to collapse
Already cancelled it out when I realized the size and time it was gonna take. Another memory block you need perhaps?
Code:
major minor #blocks name Label
7 0 21861 loop0
7 1 3150 loop1
7 2 26019 loop2
7 3 9387 loop3
7 4 2111 loop4
7 5 4190 loop5
7 6 26019 loop6
179 0 30535680 mmcblk0
179 1 15360 mmcblk0p1 apnhlos
179 2 58816 mmcblk0p2 modem
179 3 512 mmcblk0p3 sbl1
179 4 32 mmcblk0p4 dbi
179 5 32 mmcblk0p5 ddr
179 6 2048 mmcblk0p6 aboot
179 7 512 mmcblk0p7 rpm
179 8 512 mmcblk0p8 tz
179 9 10240 mmcblk0p9 pad
179 10 10240 mmcblk0p10 param
179 11 14336 mmcblk0p11 efs
179 12 3072 mmcblk0p12 modemst1
179 13 3072 mmcblk0p13 modemst2
179 14 11264 mmcblk0p14 boot
179 15 13312 mmcblk0p15 recovery
179 16 13312 mmcblk0p16 fota
179 17 7159 mmcblk0p17 backup
179 18 3072 mmcblk0p18 fsg
179 19 1 mmcblk0p19 fsc
179 20 8 mmcblk0p20 ssd
179 21 8192 mmcblk0p21 persist
179 22 9216 mmcblk0p22 persdata
179 23 2777088 mmcblk0p23 system
179 24 1048576 mmcblk0p24 cache
179 25 26521583 mmcblk0p25 userdata
179 32 512 mmcblk0rpmb
179 64 30702592 mmcblk1
179 65 30701568 mmcblk1p1
254 0 21861 dm-0
254 1 3150 dm-1
254 2 26019 dm-2
254 3 9387 dm-3
254 4 2110 dm-4
254 5 4189 dm-5
254 6 26019 dm-6
TechSavvy2 said:
Already cancelled it out when I realized the size and time it was gonna take. Another memory block you need perhaps?
Code:
major minor #blocks name Label
7 0 21861 loop0
7 1 3150 loop1
7 2 26019 loop2
7 3 9387 loop3
7 4 2111 loop4
7 5 4190 loop5
7 6 26019 loop6
179 0 30535680 mmcblk0
179 1 15360 mmcblk0p1 apnhlos
179 2 58816 mmcblk0p2 modem
179 3 512 mmcblk0p3 sbl1
179 4 32 mmcblk0p4 dbi
179 5 32 mmcblk0p5 ddr
179 6 2048 mmcblk0p6 aboot
179 7 512 mmcblk0p7 rpm
179 8 512 mmcblk0p8 tz
179 9 10240 mmcblk0p9 pad
179 10 10240 mmcblk0p10 param
179 11 14336 mmcblk0p11 efs
179 12 3072 mmcblk0p12 modemst1
179 13 3072 mmcblk0p13 modemst2
179 14 11264 mmcblk0p14 boot
179 15 13312 mmcblk0p15 recovery
179 16 13312 mmcblk0p16 fota
179 17 7159 mmcblk0p17 backup
179 18 3072 mmcblk0p18 fsg
179 19 1 mmcblk0p19 fsc
179 20 8 mmcblk0p20 ssd
179 21 8192 mmcblk0p21 persist
179 22 9216 mmcblk0p22 persdata
179 23 2777088 mmcblk0p23 system
179 24 1048576 mmcblk0p24 cache
179 25 26521583 mmcblk0p25 userdata
179 32 512 mmcblk0rpmb
179 64 30702592 mmcblk1
179 65 30701568 mmcblk1p1
254 0 21861 dm-0
254 1 3150 dm-1
254 2 26019 dm-2
254 3 9387 dm-3
254 4 2110 dm-4
254 5 4189 dm-5
254 6 26019 dm-6
Click to expand...
Click to collapse
Sorry I'm in a bit of a panic. Trying to remember how to piece together a debrick image. Appreciate your patience again.
EDIT: Here we go Link
ryanbg said:
Hi guys,
I am in desperate need of a raw img of mmcblk0. All I need one of you to do is get an adb shell or in terminal emulator with root type:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img
This creates a raw image dump I can use to help unbrick my device. It does NOT contain any sensitive data like IMEI or ESN, etc... I need MJE on Verizon Note 3 specifically. Thank you very much in advanced!
Click to expand...
Click to collapse
Actually it DOES contain sensitive data since it contains ALL 32GB of the internal flash
You need to be rooted and with a decent busybox and do more like:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img count=524288
(this will create a 256MB image).
IMHO you also need to create the debrick image on the same family product - it would be VERY interesting if that would work from a verizon developer edition model (and I would really want to see that tested) but I have some doubts. I would also be interested if any other debrick image would work - I assume you have N900V but IMHO it would be again VERY interesting to try with a N900W8 debrick image (but be very, very careful when you later write stuff with the modem-related stuff, which is very different in N900W8 and you really want to keep your N900V modem and stuff ).
xclub_101 said:
... it would be VERY interesting if that would work from a verizon developer edition model (and I would really want to see that tested) but I have some doubts. I would also be interested if any other debrick image would work ...
Click to expand...
Click to collapse
I guess I need to go looking for the right threads, but is it correct to say that the SDcard unbrick method (Qualcomm phone versions) only provides a kind of volatile boot scaffolding so that the device owner can enter Odin/download mode... and that no flashing of the device occurs until the owner actually performs the subsequent flash operation using Odin? (That is, none of the content of the unbrick image is ever written to the device being rescued?)
A second question is whether version locking occurs - I thought I saw someone claiming that a prior release unbrick image, even if taken from the same device (e.g. MI9 or MJ7 prior to a MJE upgrade) will not launch into download mode - is that right?
bftb0 said:
I guess I need to go looking for the right threads, but is it correct to say that the SDcard unbrick method (Qualcomm phone versions) only provides a kind of volatile boot scaffolding so that the device owner can enter Odin/download mode... and that no flashing of the device occurs until the owner actually performs the subsequent flash operation using Odin? (That is, none of the content of the unbrick image is ever written to the device being rescued?)
A second question is whether version locking occurs - I thought I saw someone claiming that a prior release unbrick image, even if taken from the same device (e.g. MI9 or MJ7 prior to a MJE upgrade) will not launch into download mode - is that right?
Click to expand...
Click to collapse
That is somehow true, but IMHO if all relevant partitions are wiped on the internal flash (from SBL1 to ABOOT) then all those will be read from microSD and have the code and signatures from there, and the "Odin mode" itself will be the version from microSD.
And here we have a number of interesting paths:
- the signature/hash on SBL1 itself is similar among Note 3 versions - that would result on all steps up to and including ABOOT being valid, so the "special Odin mode" will be entered; if the signature/hash on SBL1 is NOT similar between Note 3 families (or even before and after a major bootloader version) not even the "special Odin mode" will be started;
- if "special Odin mode" is started we can see another fork - if the "downgrade limitations" are part of the microSD code itself then you will be able to write any single firmware you were able to write when the internal SBL1/ABOOT was at the same version as the microSD SBL1/ABOOT - in other words you will be able to downgrade as far back as the microSD SBL1/ABOOT will let you!
- however there are some reports that the "downgrade restrictions" are actually stored in the internal flash in the "invisible/protected" regions there - and can be reset with special JTAG-like hardware:
http://forum.gsmhosting.com/vbb/f672/regarding-knox-s4-1775213/
Even in that last case there would still be a small chance that the "downgrade restrictions" might be skipped when booting from microSD since the internal flash could be considered at that point "less reliable" (or hopefully somebody at Samsung forgot to read that extra info on this special path - we can all hope )
So yes, I have also seen some people claiming stuff but I would still like to see more detailed tests on it with detailed reports on what is failing at what point! And especially on the microSD with the N900W8 "happy bootloader" or even with some much earlier "early development bootloader" (I have seen something like that mentioned somewhere)!
bftb0 said:
I guess I need to go looking for the right threads, but is it correct to say that the SDcard unbrick method (Qualcomm phone versions) only provides a kind of volatile boot scaffolding so that the device owner can enter Odin/download mode... and that no flashing of the device occurs until the owner actually performs the subsequent flash operation using Odin? (That is, none of the content of the unbrick image is ever written to the device being rescued?)
A second question is whether version locking occurs - I thought I saw someone claiming that a prior release unbrick image, even if taken from the same device (e.g. MI9 or MJ7 prior to a MJE upgrade) will not launch into download mode - is that right?
Click to expand...
Click to collapse
My theory on this (for public, bftb0 already knows) is you can boot anything that isn't fused to a lower binary counter, and since these values are inconsistent with firmware updates, it gives you a little wiggle room. AKA if A flag in ODIN is A2, you can not use an A1 aboot (MI9), but I (think) could use MJ7 since it's counter value is 2, same as MJE. These values are stored in AP RAW ANTI ROLLBACK in QFPROM. It is my belief that these values are also accessed from the shadow register as opposed to being read every time, since I was able to downgrade and replicate. I'm almost positive it's pulling these flags from RPMB. I'm extremely curious what P is since I may have full control. P1 changed to P0 when I downgraded my SBL1, TZ, and RPM to the testbit bootloader leaked by designgears, which doesn't make much since I believe all three of those have their own counters.
well ryanbg can summarize when he gets some free time (and I think that there are further experiments in the queue) but an initial attempt at performing a rescue of his bricked retail SM-900V phone (which was on MJE prior to hard bricking by a TZ partition mod) using a 200 MiB dump of mmcblk0 from a MJ7 device resulted in .... nothing.
I haven't seen anything in any of the posts so far about folks talking extra precautions involving repair of the secondary GPT (after doing a raw dump of the unbrick.img to their SDcard media), so I suppose that means that the SDCard unbrick method is - when it works - supposed to be insensitive to the fact that the unbrick SD Card does not have a complete UEFI set of primary & secondary GPTs - and might even have garbage sitting at the secondary GPT offsets.
For the MJ7 trial, we used dd if=/dev/block/mmcblk0 bs=4096 count=50000 (200 MiB) which is sufficiently large to capture everything including some amount of slop at the beginning of /system (p23). I thought I saw a post where someone was using 300 MB unbrick images, making the claim that smaller sizes didn't seem to work. Doesn't make much sense though, as only about ~ 180 MB are needed for everything up to and including p22. (p1 - p22 are ordered contiguously in LBA address space on the SM-900V, and p23 is 2.7GB, so clearly an intact copy of /system can't be needed).
any ideas welcome
sorry to resurrect this thread, but I can't seem to find a sm-n900v debrick/unbrick img anywhere. i've found the 900T, 900A, 9005 images, but nothing for 900v.
my retail edition n900v is definitely hard bricked and I could use some assistance.
Does any one have a note 3 verizon mj7 debrick/unbrick.img
Title edit: Shell command to output Partition Map?
I'm looking to get a similar output to this on my LG G2.
Code:
#cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 04380000 00020000 "system"
mtd4: 04380000 00020000 "cache"
mtd5: 04ac0000 00020000 "userdata"
Except the mtd file does not exist. I tried /proc/emmc but that also doesn't exist.
However /proc/partitions/ does exist but gives me an output like so,
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 1 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1 mmcblk0p19
179 20 512 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 32768 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 512 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 8 mmcblk0p29
179 30 2834432 mmcblk0p30
179 31 622592 mmcblk0p31
259 0 81920 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 49152 mmcblk0p34
259 3 26460160 mmcblk0p35
259 4 61423 mmcblk0p36
179 32 512 mmcblk0rpmb
~ #
Could anyone decode these names for me so I can clearly tell which partitions are which? :victory:
EDIT: Found the answer after googling mmcblk parititon layout (I feel stupid). If it helps anyone out in the future, here are the corresponding names (below). I ran
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
.
mmcblk0p4: DDR
mmcblk0p5: aboot
mmcblk0p7: boot
mmcblk0p31: cache
mmcblk0p34: cust
mmcblk0p3: dbi
mmcblk0p26: dbibak
mmcblk0p21: drm
mmcblk0p0: encrypt
mmcblk0p24: fota
mmcblk0p17: fsc
mmcblk0p16: fsg
mmcblk0p36: grow
mmcblk0p23: laf
mmcblk0p13: misc
mmcblk0p1: modem
mmcblk0p10: modemst1
mmcblk0p11: modemst2
mmcblk0p25: mpt
mmcblk0p9: pad
mmcblk0p12: pad1
mmcblk0p19: pad2
mmcblk0p14: persist
mmcblk0p29: rct
mmcblk0p15: recovery
mmcblk0p6: rpm
mmcblk0p27: rpmbak
mmcblk0p2: sbl1
mmcblk0p22: sns
mmcblk0p33: spare
mmcblk0p18: ssd
mmcblk0p30: system
mmcblk0p32: tombstones
mmcblk0p8: tz
mmcblk0p28: tzbak
mmcblk0p35: userdata
THREAD IS NOW AT ->
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I will help out. I have been reading all the threads about bricking. I have a working phone running skop and elemental. My computer is a little netbook running windows 7 32. I wont have access to it till later though.
Sent from my Nexus 6
Casper34 said:
I will help out. I have been reading all the threads about bricking. I have a working phone running skop and elemental. My computer is a little netbook running windows 7 32. I wont have access to it till later though.
Sent from my Nexus 6
Click to expand...
Click to collapse
sure no problems, i will need some comands to be run, not flashing or anything.
and thanks
opssemnik said:
sure no problems, i will need some comands to be run, not flashing or anything.
and thanks
Click to expand...
Click to collapse
I will PM you when I get near my computer, or can I run them in terminal emulator?
Sent from my Nexus 6
Casper34 said:
I will PM you when I get near my computer, or can I run them in terminal emulator?
Sent from my Nexus 6
Click to expand...
Click to collapse
which you prefer, tho the output will be a bit big
opssemnik said:
which you prefer, tho the output will be a bit big
Click to expand...
Click to collapse
Check PMs
Sent from my Nexus 6
Casper34 said:
Check PMs
Sent from my Nexus 6
Click to expand...
Click to collapse
can you show me the output of:
ls /dev/block
cat /proc/partitions
ls /dev/block/platform
So we just need to flash 5.0 bootloader before we flash cm Roms? can we still flash asop 5.0?
Sent from my Nexus 6 using Tapatalk
kenbrownstone said:
So we just need to flash 5.0 bootloader before we flash cm Roms? can we still flash asop 5.0?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
once you flash the 5.1 bootloader you can not go back to 5.0.x bootloader. i tried and got a motorola error saying mismatch. so if you flash the 5.1 bootloader that's what you're stuck on. what i want to know is, can you still flash a 5.0.x system/boot image even though you're on 5.1 bootloader?
I flashed back to stock other day after running it ..Should that have been affected
Sent from my Nexus 6 using Tapatalk
looking foward to unbricking it. Thanks a lot
opssemnik said:
can you show me the output of:
ls /dev/block
cat /proc/partitions
ls /dev/block/platform
Click to expand...
Click to collapse
Here you go...... this from 5.0.1
Spoiler
[email protected]:/ $ su
[email protected]:/ # ls /dev/block
bootdevice
dm-0
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 27807616 mmcblk0p42
179 32 4096 mmcblk0rpmb
254 0 27807616 dm-0
[email protected]:/ # ls /dev/block/platform
msm_sdcc.1
[email protected]:/ #
Sent from my Nexus 6
My nexus is also bricked after flash cm12 on top of the 5.2 bootloader. I hit reboot in TWRP and the phone shut down and hasn't done anything since. I cannot get anything to show on the screen and my computer is not recognizing it through fastboot or adb commands. I am running Ubuntu if that helps but again, I cannot see the device connected at all. I am starting to think I need to send this in for RMA
Any help is appreciated.
EDIT: When I run "lsusb" command, I get the following line when my phone is plugged in-
Bus 002 Device 006: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Casper34 said:
Here you go...... this from 5.0.1
Spoiler
[email protected]:/ $ su
[email protected]:/ # ls /dev/block
bootdevice
dm-0
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 27807616 mmcblk0p42
179 32 4096 mmcblk0rpmb
254 0 27807616 dm-0
[email protected]:/ # ls /dev/block/platform
msm_sdcc.1
[email protected]:/ #
Sent from my Nexus 6
Click to expand...
Click to collapse
Thanks, im preparing the QPST / Drivers zip, im also looking into the factory images
ccb1208 said:
My nexus is also bricked after flash cm12 on top of the 5.2 bootloader. I hit reboot in TWRP and the phone shut down and hasn't done anything since. I cannot get anything to show on the screen and my computer is not recognizing it through fastboot or adb commands. I am running Ubuntu if that helps but again, I cannot see the device connected at all. I am starting to think I need to send this in for RMA
Any help is appreciated.
EDIT: When I run "lsusb" command, I get the following line when my phone is plugged in-
Bus 002 Device 006: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Click to expand...
Click to collapse
yep, in that mode we need a program that acts as QPST (or QPST itself) a 2nd_loader.hex (new bootloader) and a APQ8974_image hex that matches ours nexus 6, once there we can send the basic stuff and get rsd mode / fastboot to work, then we just flash factory images
Your best bet would be to try the Moto X/G blankflash program. It uses an executable called qboot which is a USB loader. It may be possible to use the 8226 programmer to flash the bootloader image back to the device from bulk mode. I'd doubt it'd work, but worth checking out.
freebee269 said:
once you flash the 5.1 bootloader you can not go back to 5.0.x bootloader. i tried and got a motorola error saying mismatch. so if you flash the 5.1 bootloader that's what you're stuck on. what i want to know is, can you still flash a 5.0.x system/boot image even though you're on 5.1 bootloader?
Click to expand...
Click to collapse
Yes, you can go back to the 5.0.x system after updating to 5.1
I just flashed the ENTIRE 5.0.1 factory image, minus the bootloader.
You must obviously already be bootloader unlocked to do so.
No ill-effects whatsoever.
If you do go back to 5.0.x, make sure you flash the radio for it as well. There's a chance you'll not be able to receive calls if on LTE with 5.1's radio, as was the case for me. Only on 3g/4g did calls go through (I'm on TMO, btw)
I had the same calls issue on T-Mobile, I was on a 5.0.2 ROM and had flashed the 5.1 bootloader and radio and a friend said she called me but I didn't get a call. When she came over I had her call me again but got nothing, I could call her though. I booted to a 5.1 rom and had her call me and my phone rang.
Hey I have a fully working N6 running stock 5.1, what can I do to help?
opssemnik said:
can you show me the output of:
ls /dev/block
cat /proc/partitions
ls /dev/block/platform
Click to expand...
Click to collapse
swimdude1120 said:
Hey I have a fully working N6 running stock 5.1, what can I do to help?
Click to expand...
Click to collapse
Run those commands if you are rooted and quote opssemnik, the one with the commands, so he can see them.
If you do, put the word SPOILER in brackets [] and then the output, the /SPOILER in the brackets []
Sent from my Nexus 6