Hi guys!
I have an old M7UL (HBOOT 1.39), that has been in my closet for a year..
Now i pulled it out, to use it for home entertainment, no problems - now its semi bricked..
When i pulled it from the closet, it was on a custom 4.x ROM (AICP), but it kept having issues..
I then did a CWM backup (Philz touch) of the ROM, just in case, and decided to install VIPER (used it on my M9 and One Plus One and loved it!).
I tried to flash the VIPER rom from Philz, but it failed with error 7, so i decided to update the recovery, as it was just as old as the phone..
I then flashed multiple recoveries from fastboot (starting with TWRP, then tried CWM, and also stock recoveries, just for the fun).
ALL of the flashes fails with the error remote: err = 0xa.
I am a skilled android user, and i have been using custom roms for years, and i have never seen this error code before... Im thinking i might have messed up the partition layout, flashing a wrong recovery? Either that, or im missing something really basic here...
What my phone CAN do:
- Turn on, in fastboot mode
- Communicate with Windows via USB and fastboot
What my phone CANNOT do:
- Boot android (no OS, its formatted)
- Boot recovery (its not there or corrupted, it stays on the HTC logo screen) - also tried via fastboot boot recovery.img, no dice
Status of the phone:
- S-ON
- Unlocked tampered bootloader
- HBOOT 1.39
What im thinking my options are:
- Flash some recovery that works, and install a ROM (yay!)
- Get ADB access somehow (cant be done without recovery AFAIK) - but IF possible, gain S-OFF via revone
- Flash correct RRU (help me find one, im uncertain which one to choose here: http://ift.tt/1grJRJT )
Kind Regards
TwinAdk
I have an old M7UL (HBOOT 1.39), that has been in my closet for a year..
Now i pulled it out, to use it for home entertainment, no problems - now its semi bricked..
When i pulled it from the closet, it was on a custom 4.x ROM (AICP), but it kept having issues..
I then did a CWM backup (Philz touch) of the ROM, just in case, and decided to install VIPER (used it on my M9 and One Plus One and loved it!).
I tried to flash the VIPER rom from Philz, but it failed with error 7, so i decided to update the recovery, as it was just as old as the phone..
I then flashed multiple recoveries from fastboot (starting with TWRP, then tried CWM, and also stock recoveries, just for the fun).
ALL of the flashes fails with the error remote: err = 0xa.
I am a skilled android user, and i have been using custom roms for years, and i have never seen this error code before... Im thinking i might have messed up the partition layout, flashing a wrong recovery? Either that, or im missing something really basic here...
What my phone CAN do:
- Turn on, in fastboot mode
- Communicate with Windows via USB and fastboot
What my phone CANNOT do:
- Boot android (no OS, its formatted)
- Boot recovery (its not there or corrupted, it stays on the HTC logo screen) - also tried via fastboot boot recovery.img, no dice
Status of the phone:
- S-ON
- Unlocked tampered bootloader
- HBOOT 1.39
What im thinking my options are:
- Flash some recovery that works, and install a ROM (yay!)
- Get ADB access somehow (cant be done without recovery AFAIK) - but IF possible, gain S-OFF via revone
- Flash correct RRU (help me find one, im uncertain which one to choose here: http://ift.tt/1grJRJT )
Kind Regards
TwinAdk
from xda-developers http://ift.tt/28NvfdB
via IFTTT
No comments:
Post a Comment