[WIP] Unbricking evita

Status
Not open for further replies.
Search This thread
By:
Advanced…
SouL Shadow

SouL Shadow

Senior Member
Jun 17, 2010
466
326
Stratford, CT
www.soulshadow.net
priddyma said:
The JET tool wasn't working for my device for some reason. It detected the phone, and tried to switch modes but it seemed like my PC wasn't executing the code fast enough.
The manual method with emmc_recover worked perfect. Now hboot downgraded.
Click to expand...
Click to collapse

Jet isn't perfect. It was originally developed for Jewel, which is a single carrier (sprint) version of the one x. While it also works on the various qualcomm based one x/xl phones, there appear to be timing issues between the slightly different one x/xl hardware. Coupled with the different speeds of people's computers and the buggy nature of the linux usb 3.0 driver's backward compatibility, it introduces a timing complexity that isn't easy to handle in a single solution. That is why the manual method sometimes works when Jet does not.

-SLS-
 
  • Like
Reactions: jroman8282
E

EjWilkes0121

Member
Feb 4, 2013
19
2
Cebu City
Hi Guys,

Learned a lot from your posts. Thanks to your efforts in providing us ways to get our phones workin. :)

My phone just got bricked hours ago after I tried flashing Siyah vSync Kernel.

It was running JellyBam 4.1 and got no issues at all. It was just my curiosity to try a different kernel.

Is it something that I could fix using the manual method? I'm going to give it a shot once I get home from work.

I just thought I bricked my phone in a different way. Haha! Thanks in advance!



AT&T HTC One X running JellyBam 4.1 <- currently bricked
 
Kole_Ackerson

Kole_Ackerson

Senior Member
Feb 27, 2012
641
189
28
Minden, NV
EjWilkes0121 said:
Hi Guys,

Learned a lot from your posts. Thanks to your efforts in providing us ways to get our phones workin. :)

My phone just got bricked hours ago after I tried flashing Siyah vSync Kernel.

It was running JellyBam 4.1 and got no issues at all. It was just my curiosity to try a different kernel.

Is it something that I could fix using the manual method? I'm going to give it a shot once I get home from work.

I just thought I bricked my phone in a different way. Haha! Thanks in advance!



AT&T HTC One X running JellyBam 4.1 <- currently bricked
Click to expand...
Click to collapse

I have never heard of that kernel. Were you in the international forum or am I just blonde?

sent from my envenomed HTC One XL running ViperXL 3.2.1
 
E

EjWilkes0121

Member
Feb 4, 2013
19
2
Cebu City
Nope, I got the AT&T Version. Got it from eBay. ^.^

Well, guess what? It's up and running like it hasn't bricked. Lotsa thanks to ya'll!


I got interested with the Siyah Kernel when I saw some posts from JellyBam forums that it's got better battery performance.

Flashed it, and boom!! Expensive paperweight showed up.


Do you flash custom kernels as well? I got 3.0.57-g9268db3



AT&T HTC One X running JellyBam 4.1
 
Notorio

Notorio

Senior Member
Oct 23, 2012
233
58
I don't get a "success!" notification after the flashing is done on step 9. In fact, it looks to me as if it's freezing on:

Writing 15616 bytes to offset 0x000FC000
Waiting mode-switch
Device changed mode
Detected mode-switch

After that another empty command line just shows up. Either that's how it's supposed to be or I'm doing something wrong, though I am following the steps to the letter...

EDIT: Also after those steps when it comes down to restoring the original mmcblk0p4

Ready to write 1024 bytes
Resetting device
Cannot reset device
Reset command sent
Waiting device /dev/sdb19.......
Found device!
Writing 1024 bytes to offset 0x00000000
Waiting mode-switch
Device changed mode
Detected mode-switch
Notorio@ubuntu:~/unbrick_evita$

Notice again no "success!" notification here either, just another empty command prompt after the mode switch is detected :(

EDIT 2: Ok, I'm going to completely re-do everything from downloading all the files again to following every letter again. Hopefully the 10th time is the charm :p (I've got to be missing a step so this is a bread crumb run)
 
Last edited:
B

beaups

Senior Recognized Developer
Nov 28, 2007
3,276
7,257
Dublin, OH
Notorio said:
I don't get a "success!" notification after the flashing is done on step 9. In fact, it looks to me as if it's freezing on:

Writing 15616 bytes to offset 0x000FC000
Waiting mode-switch
Device changed mode
Detected mode-switch

After that another empty command line just shows up. Either that's how it's supposed to be or I'm doing something wrong, though I am following the steps to the letter...

EDIT: Also after those steps when it comes down to restoring the original mmcblk0p4

Ready to write 1024 bytes
Resetting device
Cannot reset device
Reset command sent
Waiting device /dev/sdb19.......
Found device!
Writing 1024 bytes to offset 0x00000000
Waiting mode-switch
Device changed mode
Detected mode-switch
Notorio@ubuntu:~/unbrick_evita$

Notice again no "success!" notification here either, just another empty command prompt after the mode switch is detected :(

EDIT 2: Ok, I'm going to completely re-do everything from downloading all the files again to following every letter again. Hopefully the 10th time is the charm :p (I've got to be missing a step so this is a bread crumb run)
Click to expand...
Click to collapse

You sudo first?

Sent from my HTC6435LVW using Tapatalk 2
 
  • Like
Reactions: Notorio
Notorio

Notorio

Senior Member
Oct 23, 2012
233
58
beaups said:
You sudo first?

Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
Yeah. Doing it this time I'm having trouble finding the device number. I'll keep messing with it until I get it right. I've done it before, I think my mind is just getting burned out by the repetition so I'm missing steps...

EDIT: Not sure what I did but now I can't even get past step 3. Ugh this is so frustrating...

---------- Post added at 03:34 PM ---------- Previous post was at 03:03 PM ----------

Ok so it seems the problem is that I can't get out of QDL mode. Any suggestions?
 
Last edited:
D

Deleted member 3452239

Guest
Notorio said:
Yeah. Doing it this time I'm having trouble finding the device number. I'll keep messing with it until I get it right. I've done it before, I think my mind is just getting burned out by the repetition so I'm missing steps...

EDIT: Not sure what I did but now I can't even get past step 3. Ugh this is so frustrating...

---------- Post added at 03:34 PM ---------- Previous post was at 03:03 PM ----------

Ok so it seems the problem is that I can't get out of QDL mode. Any suggestions?
Click to expand...
Click to collapse

Did you flash an international ROM or CWM for endeavoru? I don't understand what you are trying to do.. Downgrade your hboot or recover a brick?

And.. why are you writing to /sdb19..?
Your hboot will be at /sdb12 or /sdc12, just depends on the naming scheme.. and mmcblk0p4 will be at /sdb4 or /sdc4 or /sdd4 or wherever.

They will NOT be at /sda, most likely at /sdb or /sdc
 
  • Like
Reactions: Notorio
Notorio

Notorio

Senior Member
Oct 23, 2012
233
58
mirGantrophy said:
Did you flash an international ROM or CWM for endeavoru? I don't understand what you are trying to do.. Downgrade your hboot or recover a brick?
Click to expand...
Click to collapse
Nah I downgraded my hboot successfully but now it's bricked so I'm trying to recover from that...

---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
mirGantrophy said:
And.. why are you writing to /sdb19..?
Your hboot will be at /sdb12 or /sdc12, just depends on the naming scheme.. and mmcblk0p4 will be at /sdb4 or /sdc4 or /sdd4 or wherever.

They will NOT be at /sda, most likely at /sdb or /sdc
Click to expand...
Click to collapse
I thought the sdb number corresponded with the watch device number (at that point it was 19)...
 
D

Deleted member 3452239

Guest
Notorio said:
Nah I downgraded my hboot successfully but now it's bricked so I'm trying to recover from that...

---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------


I thought the sdb number corresponded with the watch device number (at that point it was 19)...
Click to expand...
Click to collapse

Nope, you use watch to see the device switch in and out of QDL mode so you know when to start writing.
 
  • Like
Reactions: Notorio
Notorio

Notorio

Senior Member
Oct 23, 2012
233
58
mirGantrophy said:
Nope, you use watch to see the device switch in and out of QDL mode so you know when to start writing.
Click to expand...
Click to collapse
Ok, thanks for the help in this area. Do you know any way that I can get out of QDL mode though? I'm currently stuck at "Qualcomm, Inc. Gobi Wireless Modem (QDL Mode)" and in order to move on past step 3 the watch window according to the guide must simply state the device as "Qualcomm, Inc."

Using the ls /dev/sd* command doesn't display all of the sda/sdb listings while im in QDL mode either so if being out of QDL is a prerequisite for that step I'm stuck.

Thanks again...

EDIT: FATAL: Module qserial not found is the error I keep getting. Hopefully I didn't brick it into no return...
 
Last edited:
Notorio

Notorio

Senior Member
Oct 23, 2012
233
58
Quick update. This is what I get after sudo dmesg | grep "qcserial"

[ 7.037046] usbcore: registered new interface driver qcserial
[ 7.037084] qcserial 2-1:1.0: Qualcomm USB modem converter detected
[ 762.099705] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 762.099734] qcserial 2-1:1.0: device disconnected
[ 883.505651] qcserial 2-1:1.0: Qualcomm USB modem converter detected
[ 911.795216] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 911.795241] qcserial 2-1:1.0: device disconnected
[ 931.525335] qcserial 2-1:1.0: Qualcomm USB modem converter detected
[ 1195.600667] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 1195.600685] qcserial 2-1:1.0: device disconnected
[ 1207.071036] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[ 1221.119399] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 1221.119416] qcserial 2-2:1.0: device disconnected
[ 1227.733317] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[ 1349.655162] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 1349.655178] qcserial 2-2:1.0: device disconnected
[ 1356.273714] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[ 1634.585084] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 1634.585097] usbcore: deregistering interface driver qcserial
[ 1634.585137] qcserial 2-2:1.0: device disconnected
[ 1660.474277] usbcore: registered new interface driver qcserial
[ 1660.474347] qcserial 2-2:1.0: Qualcomm USB modem converter detected

*scratches head* I'm wondering if I should just stop trying because I may be making it worse...
 
P

pawel.stefanov

Member
Feb 18, 2013
6
0
When i type ~$ ls /dev/sd* i only get /dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda /dev/sda1 . I don't understand why i'm getting only this. Can someone help me? Thanks in advance!
 
Last edited:
SouL Shadow

SouL Shadow

Senior Member
Jun 17, 2010
466
326
Stratford, CT
www.soulshadow.net
Notorio said:
Quick update. This is what I get after sudo dmesg | grep "qcserial"

[ 7.037046] usbcore: registered new interface driver qcserial
[ 7.037084] qcserial 2-1:1.0: Qualcomm USB modem converter detected
[ 762.099705] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 762.099734] qcserial 2-1:1.0: device disconnected
[ 883.505651] qcserial 2-1:1.0: Qualcomm USB modem converter detected
[ 911.795216] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 911.795241] qcserial 2-1:1.0: device disconnected
[ 931.525335] qcserial 2-1:1.0: Qualcomm USB modem converter detected
[ 1195.600667] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 1195.600685] qcserial 2-1:1.0: device disconnected
[ 1207.071036] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[ 1221.119399] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 1221.119416] qcserial 2-2:1.0: device disconnected
[ 1227.733317] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[ 1349.655162] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 1349.655178] qcserial 2-2:1.0: device disconnected
[ 1356.273714] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[ 1634.585084] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 1634.585097] usbcore: deregistering interface driver qcserial
[ 1634.585137] qcserial 2-2:1.0: device disconnected
[ 1660.474277] usbcore: registered new interface driver qcserial
[ 1660.474347] qcserial 2-2:1.0: Qualcomm USB modem converter detected

*scratches head* I'm wondering if I should just stop trying because I may be making it worse...
Click to expand...
Click to collapse

Your phone is bricked. You are in qdl mode (qualcomm high speed usb download mode) from either the pbl or sbl1 or sbl2. No partitions are showing up because sbl3 has not loaded. Unfortunately there is nothing that we can do at this point. From here we need a special file signed by HTC to repair the phone. I highly doubt we will ever see this file :(

-SLS-
 
  • Like
Reactions: jroman8282
Status
Not open for further replies.

Similar threads

h8rift
[ROM][4.1.2] CyanogenMod 10 for HTC One XL
Replies
8K
Views
2M
exad
exad
h8rift
CyanogenMod 11.0 for AT&T HTC One XL - evita
Replies
2K
Views
447K
jrior001
jrior001
h8rift
[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL
Replies
4K
Views
773K
TonyStark R.I.P.
TonyStark R.I.P.
kennethpenn
  • Locked
[ROOT] One Click HTC One X (AT&T/Rogers/Others) (Win/Mac/Linux)
Replies
870
Views
773K
orangekid
orangekid
FragmentedLogik
[DRIVERS] [UnBrick hoxl project start] QHSUSB_DLOAD
Replies
40
Views
266K
A
angelo.bautista5

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 49
    D
    Deleted member 3452239
    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://xdaforums.com/showthread.php?t=1960897, it overwrites mmcblk0p4, p5, p6 and p7)

    http://xdaforums.com/showthread.php?t=1963088
    http://xdaforums.com/showthread.php?t=1959497
    http://xdaforums.com/showthread.php?t=1727075 (heres a good reason NOT to flash CWM. This occurs when flashing it through Rom Manager, use TWRP instead!)
    http://xdaforums.com/showthread.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..
    1.png


    to seeing this...
    2.png


    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)
    View
    7
    Crappyvate
    Crappyvate
    Beware: Rant !!!!

    cakeballs said:
    so where are we on this now? should i be getting another phone or do you think there will be a solution in the near future?:confused:

    ---------- Post added at 11:01 AM ---------- Previous post was at 10:50 AM ----------

    ok. last question. will htc even repair this? and if they do how much will it cost me?
    Click to expand...
    Click to collapse


    Let me see if I understand you correctly: You have several members here who have dedicated countless man/woman hours (for free) to try and find a solution to help people like YOU (True altruism).

    Why ? Because YOU bricked your phone since you could not be bothered to read and educate yourself on a basic level to the workings of your device.

    You're a now asking for an ETA on a solution ? No eta's at xda..but if you had inform yourself a little more you'd know this !!!

    As far as how much HTC is gonna charge you to fix your phone, I hope it's a lot because you Mr.cakeballs have some big ONES...:mad:
    v
    v
    v @grim I'm sorry for the hijack but I could not stop myself ;)
    v
    v
    v
    View
    5
    D
    Deleted member 3452239
    Partition Table

    Code: 
    u0_a61@android:/ $ su
u0_a61@android:/ # 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
u0_a61@android:/ #
    View
    5
    SouL Shadow
    SouL Shadow
    Ok, Bad News time :(

    After further investigation and some help from other developers, it appears our miracle (the mprg8960.hex) is NOT loading on MSM8960 based phones (including this one). Without the help of that file, we are once again limited to only repairing devices which connect and enumerate their partitions.

    If your phone is connecting to your computer as a Qualcomm Gobi (QDL) device with vid/pid 05c6:9008 and NOT showing it's partitions (/dev/sda1 - /dev/sda36) then there is nothing that can be done at this time.

    Myself and other developers will continue to explore other possible ways to fix these devices, but as of right now there is nothing that can be done.

    My apologies to everyone who has been waiting patiently. Unfortunately we can only work with what Qualcomm and HTC have incorporated into the design and manufacturing of these devices. While they are essentially unbrickable by design, the means to a software based recovery has been disallowed. JTAG appears to be the only currently available method to unbrick these devices.
    View
    4
    18th.abn
    18th.abn
    There is no way to flash ruu's for devices in qshusb mode. They have to atleast be able to make it into bootloader.

    Sent from my HTC One XL using Tapatalk 2
    View

New posts