1. Are you ready for the Galaxy S20? Here is everything we know so far!

Help With bricked M8!

Discussion in 'Android Devices' started by tkane45, Oct 29, 2014.

  1. tkane45

    tkane45 Lurker
    Thread Starter

    okay, so i was on the GPE RUU and i wanted to return to sense, and when i went in to return through TWRP, i deleted everything on my phone including my os, in order to flash the new stock RUU, unaware that there was a different process to return to stock. I now have no system, and every time i try to flash either the stock RUU or the GPE RUU, it gives me either
    "FAILED (remote: 32 header error)" (GPE RUU)
    or
    "FAILED (remote: 24 parsing android-info fail)" (Stock RUU)
    I also cannot flash a rom through TWRP, i get a FAILED error every time.

    I am s-off and have an unlocked bootloader. my other credentials are:
    (bootloader) version: 0.5
    (bootloader) version-bootloader: 3.18.0.0000
    (bootloader) version-baseband: 1.14.21331931.LA02_2G
    (bootloader) version-cpld: None
    (bootloader) version-microp: None
    (bootloader) version-main:
    (bootloader) version-misc: PVT SHIP S-OFF
    (bootloader) serialno: FA43MWM00700
    (bootloader) imei: --
    (bootloader) imei2: --
    (bootloader) meid: 00000000000000
    (bootloader) product: m8_ul_ca
    (bootloader) platform: hTCBmsm8974
    (bootloader) modelid: 0P6B12000
    (bootloader) cidnum: CWS__001
    (bootloader) battery-status: good
    (bootloader) battery-voltage: 0mV
    (bootloader) partition-layout: Generic
    (bootloader) security: off
    (bootloader) build-mode: SHIP
    (bootloader) boot-mode: FASTBOOT
    (bootloader) commitno-bootloader: 6e0f5a3d
    (bootloader) hbootpreupdate: 11
    (bootloader) gencheckpt: 0
    all: Done!

    Thanks in advance for any help you can provide! I miss my M8!

     


  2. Best Answer:
    Post #10 by Rubens Fredrick, Jul 4, 2015 (1 points)

    1. Download the Forums for Android™ app!


      Download

       
  3. saltire

    saltire Android Expert

  4. tkane45

    tkane45 Lurker
    Thread Starter

    Thanks for your quick reply,
    when i tried to flash that file, i got this response:

    target reported max download size of 1830617088 bytes
    sending 'zip' (50747 KB)...
    OKAY [ 2.325s]
    writing 'zip'...
    (bootloader) zip header checking...
    (bootloader) zip info parsing...
    FAILED (remote: 24 parsing android-info fail)
    finished. total time: 2.507s
     
  5. Yatezy

    Yatezy Android Enthusiast

    Gain super CID, it maybe the CID number in the android-info file not matching up.

    Or add you cid number to the file.
     
  6. tkane45

    tkane45 Lurker
    Thread Starter

    changed the CID to 11111111, and still the same
    "target reported max download size of 1830617088 bytes
    sending 'zip' (50747 KB)...
    OKAY [ 2.329s]
    writing 'zip'...
    (bootloader) zip header checking...
    (bootloader) zip info parsing...
    FAILED (remote: 24 parsing android-info fail)"

    what does the failure message mean? Any thoughts?
     
  7. Yatezy

    Yatezy Android Enthusiast

    From what I've read, it's bottling it because something in the android-info isn't matching up with your phones details.

    Open up the android-info file and see if everything in it matches your phone.
     
    saltire likes this.
  8. saltire

    saltire Android Expert

    If it's not CID it's maybe the model ID then. As long as your phone is GSM and the ruu is for a GSM variant i think it should be ok editing the text file to add your model ID into it. Be good if someone else could confirm though.
     
  9. tkane45

    tkane45 Lurker
    Thread Starter

    Alright, i have been able to get around the "FAILED (remote: 24 parsing android-info fail)," by adding my CID to the android-info.txt.
    Im now running into this issue

    sending 'zip' (573239 KB)...
    OKAY [ 17.750s]
    writing 'zip'...
    (bootloader) zip header checking...
    (bootloader) shift signature_size for header checking...
    FAILED (remote: 32 header error)
    finished. total time: 17.875s

    Any thoughts on this error?
     
  10. alang92jr

    alang92jr Member

    Flash it again
     
  11. whenever you flash an RUU file. Always remember 3 things

    1. lock your bootloader
    fastboot oem lock
    2. use htc_fastboot.exe for flashing RUU, not the normal fastboot.
    https://www.androidfilehost.com/?fid=95897840722646249
    htc_fastboot flash zip ruu.zip
    3. Always flash the version equal or above ur current android. Downgrading is not allowed as it will fail check in start. If u have to downgrade, u have to be S-Off
     
  12. anrok2

    anrok2 Lurker

    I HAVE TRIED EVERYTHING BUT THIS WORKED MAN! THANKS A MILLION!

    Using htc_fastboot.exe worked. :)

    Can't tell you how happy I am.
     

HTC One M8 Forum

The HTC One M8 release date was March 2014. Features and Specs include a 5.0" inch screen, 4MP camera, 2GB RAM, Snapdragon 801 processor, and 2600mAh battery.

March 2014
Release Date
0
Reviews
Loading...
Similar Threads - Help bricked
  1. Willowsdad
    Replies:
    5
    Views:
    345
  2. alepabrahao
    Replies:
    1
    Views:
    378
  3. spman
    Replies:
    2
    Views:
    330
  4. Cameron bare
    Replies:
    4
    Views:
    399
  5. JoannaDoe
    Replies:
    5
    Views:
    475
  6. AngieDudovski
    Replies:
    9
    Views:
    562
  7. spman
    Replies:
    4
    Views:
    509
  8. jonjuanthedon
    Replies:
    3
    Views:
    495
  9. Milo Williamson
    Replies:
    5
    Views:
    514
  10. Charan Sai Pedireddi
    Replies:
    16
    Views:
    2,469

Share This Page

Loading...