[WIP] Unbricking evita

2,103 posts
Thanks Meter: 1,432
 
By mirGantrophy, Senior Member on 31st October 2012, 10:57 PM
Thread Closed Email Thread
IF YOUR PARTITIONS NEVER APPEAR, THAT MEANS YOU WERE RUNNING THE 2.20 FIRMWARE AND FLASHED AN INCORRECT ROM AND BRICKED.. THERE IS NO FIX AT THIS TIME, PLEASE STOP ASKING ME HOW TO FIX IT.


Reference threads

Users on 2.20 flashing IceColdJelly (a ROM for the endeavoru) have been bricked. This ROM effectively writes over mmcblk0p4, mmcblk0p5*, mmcblk0p6*, mccblk0p7* and then attempts to write mmcblk0p12 (which is our hboot, but fails due to write protection)
(according to beaups' post in this thread http://forum.xda-developers.com/show....php?t=1960897, it overwrites mmcblk0p4, p5, p6 and p7)

http://forum.xda-developers.com/show....php?t=1963088
http://forum.xda-developers.com/show....php?t=1959497
http://forum.xda-developers.com/show....php?t=1727075 (heres a good reason NOT to flash CWM. This occurs when flashing it through Rom Manager, use TWRP instead!)
http://forum.xda-developers.com/show....php?t=1960022

As you can see. This clearly is an issue.


Enumerating your partitions

Q: What does enumerate mean?
A:
Code:
enumerate - to specify one after another.
Synonym: list

Prerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID

1. Open up 3 terminal windows

2. On your first window, type
Code:
$ watch -n.1 lsusb
3. Now, hold power down on your phone for about 10 seconds, and let go, Then go to your second window and spam
Code:
$ ls /dev/sd*
You should go from seeing this..


to seeing this...


4. Make note of the following.
for me, my devices was listed as /dev/sdb, yours may be listed as /dev/sdc or even /dev/sdd.
make note of /dev/sd*4 and /dev/sd*12

5. Make sure Linux sees the phone
Code:
$ sudo dmesg | grep "qcserial"
You should see "Qualcomm USB modem converter detected" as the last line of the output. If not, you can unplug and replug the USB cable or run...

Code:
$ sudo modprobe qcserial
to reload the driver

6. Reset the driver
Code:
$ sudo modprobe -r qcserial
7. create the block device
Code:
$ sudo mknod /dev/ttyUSB0 c 188 0
8. Open a third Terminal window and navigate to where you stored the Downgrade_evita folder. I saved it to my desktop, so my code is
Code:
$ cd Desktop/unbrick_evita
$ chmod +x emmc_recover
9. Now we restore the hboot.. replace /sdc12 with your device location that we discovered in step 3 and 4
Code:
$ sudo ./emmc_recover -f ./hboot_1.12.0000_signedbyaa.nb0 -d /dev/sdc12 -c 24576
You can hit enter at all of the prompts here. If it stalls at "Waiting for /dev/sdc12, hold the power button down on your phone about 10 seconds, or until your see "Qualcomm. Inc. Gobi Wireless Modem (QDL mode) disappear from your terminal window, then release it. 10 seconds or less after you do this, emmc_recovery will see your phone and proceed. Flashing Hboot will take several minutes, as it has to load data in ~23K chunks followed by a reset after each.

or you can open a new terminal window and run
Code:
$ sudo ./emmc_recover -r
10. Once that is finished. We have to reset the qcserial driver again.
Code:
$ sudo modprobe -r qcserial
11. And then recreate the block device
Code:
$ sudo mknod /dev/ttyUSB0 c 188 0
12. Now we restore the original mmcblk0p4 that you should have saved as "bakp4"
Code:
$ sudo ./emmc_recover -f ./bakp4 -d /dev/sdc4 -c 24576
13. Again, if it hangs, hold your phone's power button for about 10 seconds, then release. This file will flash very quickly (it's only 1K) and once it completes, you'll immediately notice that your charging light turns back on. You should see "Qualcomm, Inc." or "Qualcomm, Inc. Gobi Wireless modem (QDL mode) disappear from your terminal screen.

14. Press the thanks button for yarrimapirate. These are his tools. If you do not, I will find you and flash ICJ on your phone.


special thanks to
beaups (for helping me understand how to enumerate the partitions)
18th.abn (for getting me the 1.09 hboot and also agreeing to help me)
and yarrimapirate (not only for the scripts which he made for the Evo 4G LTE, but also agreeing to help me in this project and buying a one x with his own money)
The Following 49 Users Say Thank You to mirGantrophy For This Useful Post: [ View ] Gift mirGantrophy Ad-Free
31st October 2012, 11:00 PM |#2  
mirGantrophy's Avatar
OP Senior Member
Thanks Meter: 1,432
 
More
Partition Table
Code:
[email protected]:/ $ su
[email protected]:/ # fdisk -l /dev/block/mmcblk0
Warning: deleting partitions after 60

Disk /dev/block/mmcblk0: 15.6 GB, 15634268160 bytes
1 heads, 16 sectors/track, 1908480 cylinders
Units = cylinders of 16 * 512 = 8192 bytes

              Device Boot      Start         End      Blocks  Id System
/dev/block/mmcblk0p1   *           1          17         128  4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2              17          49         256  51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3              49       16382      130671  5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4           16382     1908480    15136784   5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5           16383       16384          16  5a Unknown
/dev/block/mmcblk0p6           16385       16417         256  73 Unknown
/dev/block/mmcblk0p7           16417       18364       15577+ 5b Unknown
/dev/block/mmcblk0p8           18364       18396         256  5c Unknown
/dev/block/mmcblk0p9           18396       18524        1024  45 Unknown
/dev/block/mmcblk0p10          18524       18556         256  47 Unknown
/dev/block/mmcblk0p11          18556       18812        2048  46 Unknown
/dev/block/mmcblk0p12          18812       18940        1024  4c Unknown
/dev/block/mmcblk0p13          18940       18944          32   0 Empty
/dev/block/mmcblk0p14          18944       19712        6144  34 Unknown
/dev/block/mmcblk0p15          19712       19840        1024  36 Unknown
/dev/block/mmcblk0p16          19840       19968        1024   0 Empty
/dev/block/mmcblk0p17          19968       25728       46080  77 Unknown
/dev/block/mmcblk0p18          25729       27008       10240  7a Unknown
/dev/block/mmcblk0p19          27009       27649        5120   0 Empty
/dev/block/mmcblk0p20          27649       28672        8190+ 74 Unknown
/dev/block/mmcblk0p21          28673       30720       16384  48 Unknown
/dev/block/mmcblk0p22          30721       32768       16383+ 71 Unknown
/dev/block/mmcblk0p23          32769       32896        1022+ 76 Unknown
/dev/block/mmcblk0p24          32896       33408        4096  4a Unknown
/dev/block/mmcblk0p25          33409       33920        4096  4b Unknown
/dev/block/mmcblk0p26          33921       36481       20480  19 Unknown
/dev/block/mmcblk0p27          36481       36481           4   0 Empty
/dev/block/mmcblk0p28          36481       36513         256  23 Unknown
/dev/block/mmcblk0p29          36513       36515          16   0 Empty
/dev/block/mmcblk0p30          36515       36675        1280+  0 Empty
/dev/block/mmcblk0p31          36675       36683          64   0 Empty
/dev/block/mmcblk0p32          36684       49152       99752   0 Empty
/dev/block/mmcblk0p33          49153      262144     1703935  83 Linux
/dev/block/mmcblk0p34         262145      294912      262143+ 83 Linux
/dev/block/mmcblk0p35         294913      606208     2490367+ 83 Linux
/dev/block/mmcblk0p36         606209     1908480    10418176   c Win95 FAT32 (LBA)
/dev/block/mmcblk0p37          16383       16384          16  5a Unknown
/dev/block/mmcblk0p38          16385       16417         256  73 Unknown
/dev/block/mmcblk0p39          16417       18364       15577+ 5b Unknown
/dev/block/mmcblk0p40          18364       18396         256  5c Unknown
/dev/block/mmcblk0p41          18396       18524        1024  45 Unknown
/dev/block/mmcblk0p42          18524       18556         256  47 Unknown
/dev/block/mmcblk0p43          18556       18812        2048  46 Unknown
/dev/block/mmcblk0p44          18812       18940        1024  4c Unknown
/dev/block/mmcblk0p45          18940       18944          32   0 Empty
/dev/block/mmcblk0p46          18944       19712        6144  34 Unknown
/dev/block/mmcblk0p47          19712       19840        1024  36 Unknown
/dev/block/mmcblk0p48          19840       19968        1024   0 Empty
/dev/block/mmcblk0p49          19968       25728       46080  77 Unknown
/dev/block/mmcblk0p50          25729       27008       10240  7a Unknown
/dev/block/mmcblk0p51          27009       27649        5120   0 Empty
/dev/block/mmcblk0p52          27649       28672        8190+ 74 Unknown
/dev/block/mmcblk0p53          28673       30720       16384  48 Unknown
/dev/block/mmcblk0p54          30721       32768       16383+ 71 Unknown
/dev/block/mmcblk0p55          32769       32896        1022+ 76 Unknown
/dev/block/mmcblk0p56          32896       33408        4096  4a Unknown
/dev/block/mmcblk0p57          33409       33920        4096  4b Unknown
/dev/block/mmcblk0p58          33921       36481       20480  19 Unknown
/dev/block/mmcblk0p59          36481       36481           4   0 Empty
/dev/block/mmcblk0p60          36481       36513         256  23 Unknown

Partition table entries are not in disk order
[email protected]:/ #
The Following 5 Users Say Thank You to mirGantrophy For This Useful Post: [ View ] Gift mirGantrophy Ad-Free
31st October 2012, 11:13 PM |#3  
Root-Maniac's Avatar
Senior Member
Flag SO. Cali.
Thanks Meter: 839
 
Donate to Me
More
Awesome job! This will help out allot of people!

Sent from my Galaxy Nexus using xda app-developers app
The Following User Says Thank You to Root-Maniac For This Useful Post: [ View ] Gift Root-Maniac Ad-Free
31st October 2012, 11:15 PM |#4  
18th.abn's Avatar
Senior Member
Thanks Meter: 1,888
 
More
[QUOTE=absolutelygrim;33528546] (heres a good reason NOT to flash CWM, he was put into QHSUSB_DLOAD, which is, more or less, a bricked phone)

This is actually caused by flashing cwm thru Rom manager. Rom manager doesn't support evita, so the only choice is the endeavor HTC one x. Another international killer.....I still recommend twrp but just pointing this out.




Sent from my HTC One XL using Tapatalk 2
The Following 3 Users Say Thank You to 18th.abn For This Useful Post: [ View ] Gift 18th.abn Ad-Free
31st October 2012, 11:16 PM |#5  
mirGantrophy's Avatar
OP Senior Member
Thanks Meter: 1,432
 
More
Quote:
Originally Posted by 18th.abn

(heres a good reason NOT to flash CWM, he was put into QHSUSB_DLOAD, which is, more or less, a bricked phone)

This is actually caused by flashing cwm thru Rom manager. Rom manager doesn't support evita, so the only choice is the endeavor HTC one x. Another international killer.....I still recommend twrp but just pointing this out.




Sent from my HTC One XL using Tapatalk 2

I'll edit that in, thanks
The Following User Says Thank You to mirGantrophy For This Useful Post: [ View ] Gift mirGantrophy Ad-Free
31st October 2012, 11:36 PM |#6  
Crappyvate's Avatar
Senior Member
Flag Isla de Vieques
Thanks Meter: 217
 
More
Well somebody had to do it, glad it's you. Thanks for putting it altogether, hopefully we will advance towards a solution soon..
The Following 2 Users Say Thank You to Crappyvate For This Useful Post: [ View ] Gift Crappyvate Ad-Free
1st November 2012, 02:45 AM |#7  
=JKT='s Avatar
Senior Member
Flag Hamilton
Thanks Meter: 280
 
Donate to Me
More
here is my result from running sudo ./dg112.sh

HTC EVO 4G LTE HBOOT Downgrade Tool v0.2beta

FATAL: File killp4 missing.

I don't like the look of that FATAL, but what does it mean?
1st November 2012, 02:55 AM |#8  
mirGantrophy's Avatar
OP Senior Member
Thanks Meter: 1,432
 
More
Quote:
Originally Posted by =JKT=

here is my result from running sudo ./dg112.sh

HTC EVO 4G LTE HBOOT Downgrade Tool v0.2beta

FATAL: File killp4 missing.

I don't like the look of that FATAL, but what does it mean?

Oh. killp4 is specific to downgrading the EVO.
your p4 is already dead, and i didn't include it in the folder

Code:
sudo ./dg112.sh -u
Stalled at restoring /dev/block/mmclk0p4 - partitions not being detected again..
The Following 3 Users Say Thank You to mirGantrophy For This Useful Post: [ View ] Gift mirGantrophy Ad-Free
1st November 2012, 03:03 AM |#9  
Senior Member
Thanks Meter: 44
 
More
Thank you for doing this, it will help so many people.
1st November 2012, 04:06 AM |#10  
=JKT='s Avatar
Senior Member
Flag Hamilton
Thanks Meter: 280
 
Donate to Me
More
Quote:
Originally Posted by Mike724

Thank you for doing this, it will help so many people.

Although tonight's experimentation did not necessarily succeed, it is very encouraging to see my phone respond in it's limited ways and see that there is still life inside of it, though it appear so dead on the outside. Take heart, all you other brick owners!
The Following User Says Thank You to =JKT= For This Useful Post: [ View ] Gift =JKT= Ad-Free
1st November 2012, 04:45 AM |#11  
yarrimapirate's Avatar
Senior Member
Flag Vancouver, WA
Thanks Meter: 616
 
Donate to Me
More
Quote:
Originally Posted by absolutelygrim

Oh. killp4 is specific to downgrading the EVO.
your p4 is already dead, and i didn't include it in the folder

Code:
sudo ./dg112.sh -u
Stalled at restoring /dev/block/mmclk0p4 - partitions not being detected again..

We actually kill P4 on the EVO by loading an evita P4 backup.

I bet the reverse is true for you guys, loading an EVO P4 backup would cause the desired panic.
The Following User Says Thank You to yarrimapirate For This Useful Post: [ View ] Gift yarrimapirate Ad-Free
Thread Closed Subscribe to Thread

Tags
evita, htc one xl, qhsusb_dload, unbrick
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes