[HBOOT, eMMC][11/14/2012] JET - The Jewel/Evita Toolkit

Search This thread
By:
Advanced…
Genetic517

Genetic517

Senior Member
Nov 2, 2011
1,093
297
ok got it, says "please connected device" after inputting that command. i tried holding it for 10 seconds.
 
D

Deleted member 3452239

Guest
Tachi91 said:
I get stuck at


When attempting step 9.
my phone briefly shows its partitions /dev/sdgX ... but i replace the letter so its sdg12
Click to expand...
Click to collapse

Code: 
sudo modprobe -r qcserial

Code: 
sudo mknod /dev/ttyUSB0 c 188 0

I'd also like to ask to please post anything relating to the manual method in the unbrick thread, that way this one doesn't overflow with me repeating stuff
 
Last edited by a moderator:
  • Like
Reactions: Genetic517, Tachi91 and MyronJ906
Genetic517

Genetic517

Senior Member
Nov 2, 2011
1,093
297
thanks to absolutelygrim im now on old hboot! made my weekend! thanks everybody :good:
 
D

Deleted member 4541696

Guest
So once you do this can you can flash kernels inside of recovery instead of using command prompt?

Sent from my Galaxy Nexus using xda app-developers app
 
yarrimapirate

yarrimapirate

Senior Member
May 29, 2009
178
614
Vancouver, WA
Hi guys. :good:

There are a few different places where "Waking Device" happens.

Could someone send me via PM a copy of their logfile.txt? It will be in the working directory.


EDIT: I think I found the bug. Squashing now.
 
Last edited:
  • Like
Reactions: XsMagical
M

Mister J

Senior Member
Mar 6, 2011
583
131
I got this

Code: 
Do NOT interrupt this process or reboot your computer.

Corrupting /dev/block/mmcblk0p4...

23 KB/s (1024 bytes in 0.042s)
Rebooting...

Success.


Your phone should now appear to be off, with no charging light on.

Press Enter to continue...
Device detection started...
Waking Device...

./jet: 192: ./jet: Printboth: not found
./jet: 194: ./jet: arithmetic expression: expecting primary: "0+1+"

Oh and I'm bricked, phone won't even turn on.
 
yarrimapirate

yarrimapirate

Senior Member
May 29, 2009
178
614
Vancouver, WA
Mister J said:
I got this

Code: 
Do NOT interrupt this process or reboot your computer.

Corrupting /dev/block/mmcblk0p4...

23 KB/s (1024 bytes in 0.042s)
Rebooting...

Success.


Your phone should now appear to be off, with no charging light on.

Press Enter to continue...
Device detection started...
Waking Device...

./jet: 192: ./jet: Printboth: not found
./jet: 194: ./jet: arithmetic expression: expecting primary: "0+1+"

Oh and I'm bricked, phone won't even turn on.
Click to expand...
Click to collapse


Run "sudo ./jet -r" and see if it picks back up.
 
  • Like
Reactions: Mister J
M

Mister J

Senior Member
Mar 6, 2011
583
131
yarrimapirate said:
Run "sudo ./jet -r" and see if it picks back up.
Click to expand...
Click to collapse

Code: 
JET - Jewel/Evita Toolkit v0.3beta

**Recovery Mode**

Device detection started...
Waking Device...













306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]306.060403]./jet: 192: ./jet: Printbo: not found
./jet: 194: ./jet: arithmetic expression: expecting primary: "0+1+"

what am I missing?
 
M

Mister J

Senior Member
Mar 6, 2011
583
131
**Unbrick Mode**

Code: 
Device detection started...
Waking Device...

Timeout.  Retrying...

it's been stuck at this screen for a while now.

I might head over to the unbricking thread and give that a try.
 
yarrimapirate

yarrimapirate

Senior Member
May 29, 2009
178
614
Vancouver, WA
Mister J said:
**Unbrick Mode**

Code: 
Device detection started...
Waking Device...

Timeout.  Retrying...

it's been stuck at this screen for a while now.

I might head over to the unbricking thread and give that a try.
Click to expand...
Click to collapse

Interesting that your phone isn't being detected.


If you can't get it going from the unbrick thread, PM me.

Edit: Actually, PM sent. I'd like to see what is up here.
 
Last edited:
M

Mister J

Senior Member
Mar 6, 2011
583
131
I unbricked my phone, so in the spirit of XDA, I'll try to downgrade again.

And you were right, I did have a corrupted download before.

EDIT: Lol needless to say, I downgraded successfully.
 
Last edited:
  • Like
Reactions: yarrimapirate
D

Deleted member 4541696

Guest
^^^^^^
No. Read first post.

Sent from my Galaxy Nexus using xda app-developers app
 
Last edited by a moderator:
You must log in or register to reply here.

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
hasoon2000
  • Locked
[TOOL] HTC One X (Evita) All-In-One Toolkit V3.0.1 [7-7-2013] [PERM ROOT][Noob-Proof]
Replies
464
Views
283K
kinfauns
kinfauns
Turge
  • Poll
[ROM][SEP 22] Team Venom ViperXL 4.2.0 | Sense 5 | Venom Tweaks | OTA Updates
Replies
19K
Views
2M
T
Tmobilefan906
X
[DRIVER] HTC Driver 4.0.1.001 (2012-11-07)
Replies
25
Views
378K
D
Darkrapier11

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 74
    yarrimapirate
    yarrimapirate
    Disclaimer: This is BETA. It works well, but may still set fire to your house if you anger it.


    UPDATE 11/14/12 - Updated OP with SLS's device detection code fixes.

    Update 2: Fixed bug in device detection loop causing freeze at "Waking Device"


    JET - The Jewel/Evita Tool "kit."

    This all started as a downgrade script for the Jewel. You can follow the original JET thread in the EVO 4G LTE forums. I'm creating this thread to track/support issues from Evita users.

    JET performs several useful functions, including:
    • Downgrading your HBOOT to 1.09 for easier radio flashing.
    • SuperCID (For HTCDev unlocking)
    • Partition/IMEI backup.
    • Detection of eMMC partitions on a phone stuck in Qualcomm download mode
    • Possible unbricking of your device (depending on circumstances)


    JET is and always will be 100% open source and with full support given here on XDA.

    Changelog
    11/9/12 - Name change to better reflect the direction of this project. Ported to Evita. Rewrote device detection code.
    11/1/2012 - Added SuperCID capability
    10/24/2012 - Modified emmc_recover to catch stalls at "Wait device /dev/sdXXX......" and try to recover.
    10/21/2012 - Added --recover and --unbrick command line options
    10/19/2012 - Beta posted
    Click to expand...
    Click to collapse


    Credits:
    Credit for the original EVO downgrading idea belongs to Mac_Gyver as seen in this post:
    http://xdaforums.com/showthread.php?t=1932914

    This post refined that process and can still be referenced for manual downgrading:
    http://xdaforums.com/showpost.php?p=32761598&postcount=107

    Closeone for code submissions and a steady flow of awesome ideas.

    SouL Shadow for some slick logging code

    Initial Testers (AKA People willing to let a total stranger intentionally brick their phone for SCIENCE!)
    AZ Fadeout
    benny3
    kjcmusic17
    michael.stollaire
    My lovely wife (distract with shiny object, snatch phone, cackle wildly, proceed to brick)
    Some local folks not on XDA

    absolutelygrimm and 18th.abn for consulting on the Evita side of things.

    The XDA community for rallying behind this project and offering support to your fellow members
    Click to expand...
    Click to collapse



    Requirements

    • Unlocked bootloader and a recent TWRP already flashed. (For most functions.)
    • A NATIVE Linux installation, or a LiveCD/Wubi install. Virtual Machines are NOT SUPPORTED.
      [*]A 32 bit Linux installation/CD, or install ia32-libs or ia32-libs-multiarch
    • Linux Kernel v3.0 or higher (Ubuntu 12.04 LiveCDs meet this requirement)
    • USB Debugging turned on
    Click to expand...
    Click to collapse



    FAQ
    Q: Help! The tool keeps saying "Failed to flash HBoot" repeatedly. What do I do?
    A: This is a timing issue. If the tool can't get a good lock on your phone, it will give and error and then try again. It will keep trying until it locks onto the phone and can flash. In addition, it is safe to unplug and replug the USB cable during this step, even to another USB port.


    Q: This thing is taking forever!! Is it supposed to?
    A: The process usually takes about 10 minutes but can take 15 or longer depending. Unfortunately the process for flashing the bootloader is rather painful, and has to be done in very small pieces. Thank HTC for that one. Ubuntu is also partially to blame.


    Q: Is this a bootable CD? Can I use this from Windows?
    A: This is NOT a bootable LiveCD. A LiveCD version (with further enhancements) is in the works.


    Q: Is there/Will there be a Windows version?
    A: No. Nor are there plans to make a Windows native version. There are some inherent issues with the way Windows deals with USB devices that prohibits us from accessing QDL. If you're not comfortable trying/using Linux, I suggest you wait for the LiveCD to be finished.
    Click to expand...
    Click to collapse



    Instructions:
    1. Boot Linux.
    2. Download attached package.
    3. Unzip to somewhere you have write access (/home/ubuntu for Ubuntu LiveCD users)
    4. Open terminal.
    5. cd to working directory.
    6. $ chmod +x jet
    7. $ sudo ./jet
    8. Follow the onscreen instructions.
    9. /happydance
    Click to expand...
    Click to collapse

    Command Line Options
    Code: 
    -b or --backup  :  Backup mode only  (make bakp4 and fsp4, don't force QDL)
-c or  --cidpreserve : Don't SuperCID the backup P4 file
-d or  --detect   :  Find device (/dev/sd?)
-k or  --kill     :  Soft brick the phone by corrupting P4  (be careful with this)
-r  or  --recover  :  Load HBOOT 1.09 and existing backup P4 (for people who stalled after QDL force)
-s or  --supercid : SuperCID mod for nonbricked phones
-u or --unbrick  :  Load existing backup P4 file ONLY.  (Quit QDL without downgrade)
    Click to expand...
    Click to collapse

    To do:
    • P4 file generation from user entered MEID.
    • Merge both HW versions of JET and detect device at load.
    • LiveCD
    • All requests for features considered!
    Click to expand...
    Click to collapse



    Source:
    You can follow code revisions for the shell script here:
    https://github.com/yarrimapirate/JET

    LiveCD Development is underway. You can follow the code here:
    https://github.com/closeone/JET

    I use a modified version of Fuses emmc_recover. I have forked his source here:
    https://github.com/yarrimapirate/emmc_recover
    Click to expand...
    Click to collapse

    A big Thank You to all who've sent donations! Caffeine and beer help generate code, and a few extra bucks convinces the wife it's worth the time I spend glued to my PC/phone. Your donation money is also being used to buy devices to further test/develop with. :good:
    View
    9
    XsMagical
    XsMagical
    oh sweet, video coming right up!

    Just one step closer to S-Off!
    View
    7
    yarrimapirate
    yarrimapirate
    Reserved.
    View
    6
    D
    Deleted member 3452239
    yarrimapirate said:
    Since I'm not entirely familiar with the problem, I'll ask grim to expalin it to me so I can properly document it in the OP. Thanks for the heads up!
    Click to expand...
    Click to collapse

    ----

    Hboot protects itself, I thought sbl3 verified hboot, then it protected itself but that's not the case. Sbl3 is controlling emmc mode from my understanding...

    p9 (sbl3) sets emmc mode before p12(hboot) sets protection...........p1,2,3 will never be vulnerable to the same exploit as they have already set their protection well before emmc mode. They are the first 3 partitions so you cannot brick anything earlier in the chain. So, just say, hboot was p7, it would protect itself before emmc mode, and would never be vulnerable. -18th.abn


    ----

    However, if for any reason you cannot flash Kernels/Radios.. Just run the 1.85 RUU and your issues will be solved.

    ----

    To RUU downgrade, you will need to pull mmcblk0p23 from your phone and hex edit it. To do so, open terminal emulator on your phone..

    Code: 
    $ su
# dd if=/dev/block/mmcblk0p23 of=/sdcard/mmcblk0p23

    Open this in a hex editor of your choice.
    at 0x0A0 you will see
    ClearAutoImage..2.20.xxx.x...................... x being whatever number is listed..
    change it to 1.00.000.0

    Place back on your sdcard
    open terminal emulator
    Code: 
    $ su
# dd if=/sdcard/mmcblk0p23 of=/dev/block/mmcblk0p23

    reboot to fastboot and lock your bootloader. Boot into your ROM and RUU downgrade
    View
    5
    yarrimapirate
    yarrimapirate
    This one too...
    View

New posts