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
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
Can someone please do a cat /proc/partition on their i377 and output it here. I have the s975L and researching it seems they are really identical? I am currently getting with the creator of Safestrap to see if it would work fine for my device.
Thanks
ndowens said:
Can someone please do a cat /proc/partition on their i377 and output it here. I have the s975L and researching it seems they are really identical? I am currently getting with the creator of Safestrap to see if it would work fine for my device.
Thanks
Click to expand...
Click to collapse
I am assuming you are talking about sgh-i337 which is the ATT S4.
Below is the output from my phone (sgh-i337). "jgedlte" would be because this is running GPE rom.
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 20480 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 10219520 mmcblk0p29
179 32 30703616 mmcblk1
179 33 30699520 mmcblk1p1
NOTE: Testers no longer required, now confirmed working for both kitkat and lollipop
This is for the T800/T805/T807 Exynos version only
Basically I have fixed some issues with the official build:
It is not possible to get root access to the shell with adb in the official version, you will get an error. I have fixed this as it is important for adb to be able to get shell access, you never know when it might be needed.
The reboot options have been corrected to change the reboot option from BOOTLOADER to DOWNLOAD . Reboot to Download mode now works.
TWRP still uses outdated Supersu and root files, so I have updated these to the latest versions.
Please use Odin 10.6 for installing: Odin 10.6
unofficial-twrp-2.8.6.0-chagall.tar
Anybody? just 2mins of your time. It won't brick your device. If it flashes with Odin and doesn't boot just reflash the official twrp or stock recovery.
ashyx said:
Anybody? just 2mins of your time. It won't brick your device. If it flashes with Odin and doesn't boot just reflash the official twrp or stock recovery.
Click to expand...
Click to collapse
Had some time before I do chores Fails in odin and flashify. In odin it would say name write start... then fail! And yet official twrp flashes fine
Right this is silly. I'm gonna do a simple repack of the official twrp, no changes. Can you test that? If that fails then at least I know where the problem lies!
ashyx said:
Right this is silly. I'm gonna do a simple repack of the official twrp, no changes. Can you test that? If that fails then at least I know where the problem lies!
Click to expand...
Click to collapse
Yep sure can!
DUHAsianSKILLZ said:
Yep sure can!
Click to expand...
Click to collapse
ok here you go.
https://www.androidfilehost.com/?fid=95916177934548161
ashyx said:
ok here you go.
https://www.androidfilehost.com/?fid=95916177934548161
Click to expand...
Click to collapse
Works!
DUHAsianSKILLZ said:
Works!
Click to expand...
Click to collapse
Good stuff, I have a feeling the lollipop update has changed the size of the recovery partition which is why it was being rejected.
If the link below works then I will see if I can reduce the size, but could really need to know what size the new partition is.
https://www.androidfilehost.com/?fid=95916177934548184
ashyx said:
Good stuff, I have a feeling the lollipop update has changed the size of the recovery partition which is why it was being rejected.
If the link below works then I will see if I can reduce the size, but could really need to know what size the new partition is.
https://www.androidfilehost.com/?fid=95916177934548184
Click to expand...
Click to collapse
Yep this one works also. Rebooting into download mode from twrp works fine. Seems to be the one!
Great, looks like we've discovered the problem. Just need to fix the adb shell issue and if size allows update supersu. Thanks your a great help. I'll update tomorrow.
ashyx said:
Great, looks like we've discovered the problem. Just need to fix the adb shell issue and if size allows update supersu. Thanks your a great help. I'll update tomorrow.
Click to expand...
Click to collapse
When you post the update tomorrow, or whenever you post it. Ill give it a try. Sorry I couldnt be much help on the testing stage at this time. I have been so busy with my own mods that I dont have much time for others at the time.
But I will try it out on your next update.. for sure... thanks for your support on this Machine...
Of course I realise you are busy with other things so appreciate the time.:good:
I have reduced the size of the files below, the first one is slightly large than the second. I cant reduce any more without reducing functionality, so if the first one doesn't work the second should, but at least 2 of the main issues, the adb shell problem and wrong reboot option will be fixed in both.
twrp2860v1
twrp2860v2
thanks again.
ashyx said:
Of course I realise you are busy with other things so appreciate the time.:good:
I have reduced the size of the files below, the first one is slightly large than the second. I cant reduce any more without reducing functionality, so if the first one doesn't work the second should, but at least 2 of the main issues, the adb shell problem and wrong reboot option will be fixed in both.
twrp2860v1
twrp2860v2
thanks again.
Click to expand...
Click to collapse
Hi I have just flashed the first one and it failed but the second one flashed ok.
ashyx said:
Of course I realise you are busy with other things so appreciate the time.:good:
I have reduced the size of the files below, the first one is slightly large than the second. I cant reduce any more without reducing functionality, so if the first one doesn't work the second should, but at least 2 of the main issues, the adb shell problem and wrong reboot option will be fixed in both.
twrp2860v1
twrp2860v2
thanks again.
Click to expand...
Click to collapse
I flashed the 2nd one, and it seemed to work. Matter of fact I just flashed my updated rom with it. Worked so far.
Thanks for taking the time to bring us yet another working TWRP...
Thanks for testing guys. First post updated with final version.
I'm curious as to what the size of the recovery partition has been changed to. Could someone run the following command either in Terminal or ADB if you're running Lollipop?:
cat /proc/partitions
ashyx said:
Thanks for testing guys. First post updated with final version.
I'm curious as to what the size of the recovery partition has been changed to. Could someone run the following command either in Terminal or ADB if you're running Lollipop?:
cat /proc/partitions[/QUOTE
Just sent you a email message.
Click to expand...
Click to collapse
ashyx said:
Thanks for testing guys. First post updated with final version.
I'm curious as to what the size of the recovery partition has been changed to. Could someone run the following command either in Terminal or ADB if you're running Lollipop?:
cat /proc/partitions
Click to expand...
Click to collapse
Here you go:
Code:
cat /proc/partitions
major minor #blocks name
7 0 4180 loop0
7 1 32380 loop1
7 2 32380 loop2
253 0 1048576 vnswap0
179 0 30535680 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 10240 mmcblk0p10
259 3 10240 mmcblk0p11
259 4 4096 mmcblk0p12
259 5 20480 mmcblk0p13
259 6 4096 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 12288 mmcblk0p16
259 9 4096 mmcblk0p17
259 10 2467840 mmcblk0p18
259 11 204800 mmcblk0p19
259 12 337920 mmcblk0p20
259 13 27385856 mmcblk0p21
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179 32 124868096 mmcblk1
179 33 124863488 mmcblk1p1
254 0 4180 dm-0
254 1 32380 dm-1
254 2 32380 dm-2
Eliminater74 said:
Here you go:
Code:
cat /proc/partitions
major minor #blocks name
7 0 4180 loop0
7 1 32380 loop1
7 2 32380 loop2
253 0 1048576 vnswap0
179 0 30535680 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 10240 mmcblk0p10
259 3 10240 mmcblk0p11
259 4 4096 mmcblk0p12
259 5 20480 mmcblk0p13
259 6 4096 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 12288 mmcblk0p16
259 9 4096 mmcblk0p17
259 10 2467840 mmcblk0p18
259 11 204800 mmcblk0p19
259 12 337920 mmcblk0p20
259 13 27385856 mmcblk0p21
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179 32 124868096 mmcblk1
179 33 124863488 mmcblk1p1
254 0 4180 dm-0
254 1 32380 dm-1
254 2 32380 dm-2
Click to expand...
Click to collapse
The recovery partition size hasn't changed it's still 10mb -
2 10240 mmcblk0p10
The strange thing is, as a test I have somehow been able to flash a working 28mb recovery image to a 10mb partition under kitkat. Not sure how this is even possible!
ashyx said:
The recovery partition size hasn't changed it's still 10mb -
2 10240 mmcblk0p10
The strange thing is, as a test I have somehow been able to flash a working 28mb recovery image to a 10mb partition under kitkat. Not sure how this is even possible!
Click to expand...
Click to collapse
Hey buddy. I've flashed your version in the first post ( which was updated in 6th April right? ) but I can't reboot into twrp. Any update on that?
Regards
d3xtr0 said:
Hey buddy. I've flashed your version in the first post ( which was updated in 6th April right? ) but I can't reboot into twrp. Any update on that?
Regards
Click to expand...
Click to collapse
How are you trying to boot into recovery and which version tab s do you have?
You can also try the updated version here: http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Here is the stock partition table from the Xperia Z3 D6603
Code:
major minor #blocks name
253 0 524288 zram0
179 0 15388672 mmcblk0
179 1 2048 mmcblk0p1 TA
179 2 512 mmcblk0p2 sbl1
179 3 256 mmcblk0p3 s1sbl
179 4 64 mmcblk0p4 dbi
179 5 512 mmcblk0p5 aboot
179 6 512 mmcblk0p6 rpm
179 7 512 mmcblk0p7 tz
179 8 512 mmcblk0p8 alt_sbl1
179 9 512 mmcblk0p9 alt_s1sbl
179 10 64 mmcblk0p10 alt_dbi
179 11 512 mmcblk0p11 alt_aboot
179 12 512 mmcblk0p12 alt_rpm
179 13 512 mmcblk0p13 alt_tz
179 14 20480 mmcblk0p14 boot
179 15 10240 mmcblk0p15 ramdump
179 16 16384 mmcblk0p16 FOTAKernel
179 17 32 mmcblk0p17 DDR
179 18 16384 mmcblk0p18 LTALabel
179 19 1536 mmcblk0p19 modemst1
179 20 1536 mmcblk0p20 modemst2
179 21 1536 mmcblk0p21 fsg
179 22 8192 mmcblk0p22 apps_log
179 23 2609152 mmcblk0p23 system
179 24 204800 mmcblk0p24 cache
179 25 12359663 mmcblk0p25 userdata
179 32 4096 mmcblk0rpmb ?
179 64 31260672 mmcblk1 ?
179 65 31256576 mmcblk1p1 ?
This partition table may also work for the D6633, D6653, and D6616. But not having these devices I do not know.
I think mmcblk1 is SD card. Mine has two partitions and I have mmcblk1p2 too.
Hello, Last Night I Powered on My Phone in It Got Stuck at Starting Apps For About an Hour (Nexus Experience ROM)
So I Just Wiped Data and Cache and Rebooted But Now It Struck at Lenovo Log. I Went Again To Wipe But This Time Got Error
Unable to Mount Data/Cache.Tried To Mount It in TWRP But It Didnt only Able To Mount System. Tried To Install Custom Rom and Now Got Error Unable To Mount System/Cache/Data/Davlik Invalid Argument and So On.Now Even My System Partition Cant Be Mount. Tried To Flash Stock Firmware But Same Error and Even Flash From ADB Sideload Didnt Worked.in TWRP only Boot Partition is shown as 32 MB and Every Other is 0 MB. TWRP Says There is No OS Installed and Its stuck at Reboot Loop
TWRP Version 3.0
EDIT : Even Tried To Flash Using QFIL Tool and it Was Done Without any Error But When Phone Booted Up It Had Same Issue and Still Has TWRP.
I Was Able To Push Zip of a Custom Rom Into Data/Media Using Fastboot
Upon Applying Command
cat /proc/partitions it lists 34 Items
/proc # ←[6ncat /proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1 mmcblk0p16
179 17 8 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 32 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 16 mmcblk0p21
179 22 32768 mmcblk0p22
179 23 1843200 mmcblk0p23 (System Partition)
179 24 32768 mmcblk0p24
179 25 268288 mmcblk0p25 (Cache)
179 26 32768 mmcblk0p26
179 27 512 mmcblk0p27
179 28 32 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 12836847 mmcblk0p30 (Data)
179 32 4096 mmcblk0rpmb
179 64 31260672 mmcblk1
179 65 31256576 mmcblk1p1
df shows
/proc # ←[6ndf
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 971956 12 971944 0% /dev
tmpfs 971956 20 971936 0% /tmp
/dev/block/mmcblk1p1 31248384 30779296 469088 98% /external_sd
/dev/block/mmcblk1p1 31248384 30779296 469088 98% /and-sec
/proc # ←[6n
Any Help Would Be Highly Appreciated
zhee9130 said:
Hello, Last Night I Powered on My Phone in It Got Stuck at Starting Apps For About an Hour (Nexus Experience ROM)
So I Just Wiped Data and Cache and Rebooted But Now It Struck at Lenovo Log. I Went Again To Wipe But This Time Got Error
Unable to Mount Data/Cache.Tried To Mount It in TWRP But It Didnt only Able To Mount System. Tried To Install Custom Rom and Now Got Error Unable To Mount System/Cache/Data/Davlik Invalid Argument and So On.Now Even My System Partition Cant Be Mount. Tried To Flash Stock Firmware But Same Error and Even Flash From ADB Sideload Didnt Worked.in TWRP only Boot Partition is shown as 32 MB and Every Other is 0 MB. TWRP Says There is No OS Installed and Its stuck at Reboot Loop
TWRP Version 3.0
EDIT : Even Tried To Flash Using QFIL Tool and it Was Done Without any Error But When Phone Booted Up It Had Same Issue and Still Has TWRP.
I Was Able To Push Zip of a Custom Rom Into Data/Media Using Fastboot
Upon Applying Command
cat /proc/partitions it lists 34 Items
/proc # ←[6ncat /proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1 mmcblk0p16
179 17 8 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 32 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 16 mmcblk0p21
179 22 32768 mmcblk0p22
179 23 1843200 mmcblk0p23 (System Partition)
179 24 32768 mmcblk0p24
179 25 268288 mmcblk0p25 (Cache)
179 26 32768 mmcblk0p26
179 27 512 mmcblk0p27
179 28 32 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 12836847 mmcblk0p30 (Data)
179 32 4096 mmcblk0rpmb
179 64 31260672 mmcblk1
179 65 31256576 mmcblk1p1
df shows
/proc # ←[6ndf
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 971956 12 971944 0% /dev
tmpfs 971956 20 971936 0% /tmp
/dev/block/mmcblk1p1 31248384 30779296 469088 98% /external_sd
/dev/block/mmcblk1p1 31248384 30779296 469088 98% /and-sec
/proc # ←[6n
Any Help Would Be Highly Appreciated
Click to expand...
Click to collapse
CAN SOMEONE With A6000 PLus Upload Complete Image of emmc ? Thats The Hope of Reviving My Device. Thanks