Database Info

Really screwed up, what to do? CID:BM__001

Ok, so I tried to unlock my bootloader and install a custom rom, of course, somewhere along the way I screwed up and now I don't know what to do. So what I did was I unlocked my bootloader using the HTCDev unlock token, that went fine, then I installed CWM, again, that was fine, then installed superSU and flashed CM10, rebooted, nothing, I realized I had to flash the boot.img from CM so I did that, then that's what when the problems began. The CM boot animation just starts and never ends (i.e. over 15min). So all I can do now is get into bootloader, and from there recovery; although my /sdcard partition seems to be screwed too. Can't 'flash from SDcard' in recovery, I looked at that thread that says to flash a stock recovery to fix this but I can't find a stock recovery or RUU for my CID...
I guess my question is, how can I get my phone booting again? Is it easier to just go straight to S-OFF? Which I don't think I can do with my phone in this state, or just go back to stock? Which I can't find a proper RUU for my phone....
Obviously... any help is greatly appreciated
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT27DWxxxxxx
(bootloader) imei: ----------------------
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4133mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s

stock recovery--
https://www.dropbox.com/sh/yhrq0tia8512rj9/go28kc1NeP/ville_recovery_signed.img
would also fastboot twrp recovery after you are sorted--2.3.3.0 works good
http://techerrata.com/browse/twrp2/ville
you will lose sdcard hope you have a bu and a nandroid on pc--i always keep copies on my pc or you may have to push a rom to sdcard
you need to fastboot stock recovery
then thru command window boot into bootloader and clear storage
reboot into into bootloader and factory reset, that should get your sdcard mountable again
you can use this but use fastboot and not toolkit and fastboot twrp not cwm
http://forum.xda-developers.com/showthread.php?t=1630459

rugmankc said:
stock recovery--
https://www.dropbox.com/sh/yhrq0tia8512rj9/go28kc1NeP/ville_recovery_signed.img
would also fastboot twrp recovery after you are sorted--2.3.3.0 works good
http://techerrata.com/browse/twrp2/ville
you will lose sdcard hope you have a bu and a nandroid on pc--i always keep copies on my pc or you may have to push a rom to sdcard
you need to fastboot stock recovery
then thru command window boot into bootloader and clear storage
reboot into into bootloader and factory reset, that should get your sdcard mountable again
you can use this but use fastboot and not toolkit and fastboot twrp not cwm
http://forum.xda-developers.com/showthread.php?t=1630459
Click to expand...
Click to collapse
thank you sir, questions:
how do I boot into bootloader thru command window? Won't I be still be in bootloader after I fastboot the stock recovery?
Also what should/can I do after? Can I try re-installing CM10 again? I guess that's the only thing I can do since I don't have a RUU that works with my CID...??

i forget how phone reacts after clearing storage, but need to get back to bl or see if you stay there
assume you are familiar with adb/fatsboot, i soon have to call it a nite. someone else may have to chime in
but, basically you need to open command window and change directory to where your adb/fastboot folder is. If using android sdk it is usually in platform tools
take the boot image from the link i provided and put in your fastboot folder on pc
once there you should be able to type adb devices and see that your phone is recognized. then you can type adb reboot bootloader and you should boot into fastboot screen where FASTBOOT is highlighted red
then you can type fastboot devices to again verify your are in fastboot
then type fastboot flash boot boot.img
the boot.img part will be the exact name of the boot image you put into the adb/fastboot folder, the one i gave you the link to.
you can change the name of that image to boot.img or just copy and paste the name as is into the command line instead of boot.img
fastboot twrp the same way if you get sdcard recognized
if you can now mount card you can copy rom to sdcard from pc
you may not have wiped properly when you flashed cm10
wipe all including system 3x from recovery before flashing roms
Awesome has a kernel and system wipe zips you can also use if you want. I wipe all thru recovery first then run the kernel then wipe script then flash rom. wouldn't use them yet.

rugmankc said:
stock recovery--
https://www.dropbox.com/sh/yhrq0tia8512rj9/go28kc1NeP/ville_recovery_signed.img
would also fastboot twrp recovery after you are sorted--2.3.3.0 works good
http://techerrata.com/browse/twrp2/ville
you will lose sdcard hope you have a bu and a nandroid on pc--i always keep copies on my pc or you may have to push a rom to sdcard
you need to fastboot stock recovery
then thru command window boot into bootloader and clear storage
reboot into into bootloader and factory reset, that should get your sdcard mountable again
you can use this but use fastboot and not toolkit and fastboot twrp not cwm
http://forum.xda-developers.com/showthread.php?t=1630459
Click to expand...
Click to collapse
rugmankc said:
i forget how phone reacts after clearing storage, but need to get back to bl or see if you stay there
assume you are familiar with adb/fatsboot, i soon have to call it a nite. someone else may have to chime in
but, basically you need to open command window and change directory to where your adb/fastboot folder is. If using android sdk it is usually in platform tools
take the boot image from the link i provided and put in your fastboot folder on pc
once there you should be able to type adb devices and see that your phone is recognized. then you can type adb reboot bootloader and you should boot into fastboot screen where FASTBOOT is highlighted red
then you can type fastboot devices to again verify your are in fastboot
then type fastboot flash boot boot.img
the boot.img part will be the exact name of the boot image you put into the adb/fastboot folder, the one i gave you the link to.
you can change the name of that image to boot.img or just copy and paste the name as is into the command line instead of boot.img
fastboot twrp the same way if you get sdcard recognized
if you can now mount card you can copy rom to sdcard from pc
you may not have wiped properly when you flashed cm10
wipe all including system 3x from recovery before flashing roms
Awesome has a kernel and system wipe zips you can also use if you want. I wipe all thru recovery first then run the kernel then wipe script then flash rom. wouldn't use them yet.
Click to expand...
Click to collapse
I was just about to reply, I got the TWRP going so I have that recovery on there now and I think my SDcard is working now... so should I wipe and run the kernal and flash rom? what about flashing the boot.img of the new rom? Do I still need to do that?

You'll have to read OP page for flashing instructions for that rom. Some have a boot script you can run as opposed to fastbooting boot image. And if you are .13 hboot or higher you will need to flash boot image. Fastboot is best way. However some are using Flash Image GUI to do that. From Market. For now fastboot it as you are obviously proficient at fastboot.
I would normally wipe all 3x including system/flash rom in recovery(don't boot into OS (System)yet)/boot into bootloader and flash boot image. After flashing boot image in command window type fastboot erase cache. then type fastboot reboot-bootloader. Once back in recovery you can reboot into System (OS).
Usually after rom boots and I set up wifi, I usually reboot to recovery and wipe caches then reboot into rom and continue setup.

rugmankc said:
You'll have to read OP page for flashing instructions for that rom. Some have a boot script you can run as opposed to fastbooting boot image. And if you are .13 hboot or higher you will need to flash boot image. Fastboot is best way. However some are using Flash Image GUI to do that. From Market. For now fastboot it as you are obviously proficient at fastboot.
I would normally wipe all 3x including system/flash rom in recovery(don't boot into OS (System)yet)/boot into bootloader and flash boot image. After flashing boot image in command window type fastboot erase cache. then type fastboot reboot-bootloader. Once back in recovery you can reboot into System (OS).
Usually after rom boots and I set up wifi, I usually reboot to recovery and wipe caches then reboot into rom and continue setup.
Click to expand...
Click to collapse
Ok I've tried all the steps and I can get into recovery and flash roms but any rom I try to flash (and following all wipe and boot.img steps) always results in a bootloop when I first boot the rom... any ideas?? I can reflash different roms but no matter which one I try they end up in bootloops...
Is there a way to go to S-OFF in my state?

pookguy88 said:
Ok I've tried all the steps and I can get into recovery and flash roms but any rom I try to flash (and following all wipe and boot.img steps) always results in a bootloop when I first boot the rom... any ideas?? I can reflash different roms but no matter which one I try they end up in bootloops...
Is there a way to go to S-OFF in my state?
Click to expand...
Click to collapse
Are you sure your flashing the boot img for the ROM you are trying to flash? Use fastboot.
HTC_One_S | S-OFF | Root_Box | Bubba_3.7b_SoftOV

ryanshew said:
Are you sure your flashing the boot img for the ROM you are trying to flash? Use fastboot.
HTC_One_S | S-OFF | Root_Box | Bubba_3.7b_SoftOV
Click to expand...
Click to collapse
Yup.. I always take the boot img out of the ROM zip file itself and fastboot it before I reboot..
I've tried Carbon and CM10 so far... both get stuck in bootloops at boot.. I know the boot.img is being flashed because the fastboot goes through ok and the boot animation for each ROM is different

maybe im repeating some one else but
try it without wiping after the install of rom and boot.img
so, wipe all (data/cache/system/dalvik/unsecure) then factory reset
then flash rom in twrp
then fastboot flash boot boot.img in fastboot usb mode
reboot device.
btw what rom are you flashing?

I am not up on hboots/cid's/etc
but see you have an EU radio
you are version s4 not s3
sorry if that was easily recognized on your 1st post

real187 said:
maybe im repeating some one else but
try it without wiping after the install of rom and boot.img
so, wipe all (data/cache/system/dalvik/unsecure) then factory reset
then flash rom in twrp
then fastboot flash boot boot.img in fastboot usb mode
reboot device.
btw what rom are you flashing?
Click to expand...
Click to collapse
I've been trying CM10 (http://forum.xda-developers.com/showthread.php?t=1799139) nightlies...
So for the wiping part, isn't a factory reset (in TWRP) just a data/cache wipe? what does unsecure do? I haven't done that before..

rugmankc said:
I am not up on hboots/cid's/etc
but see you have an EU radio
you are version s4 not s3
sorry if that was easily recognized on your 1st post
Click to expand...
Click to collapse
yeah, just realized I have a S4... are you sure I have a EU radio though? I got mine from a Canadian (Bell) carrier..

Ok I'm going to try re-locking the bootloader and RUU-ing this:
RUU_Ville_U_BM_1.70.666.1_R_Radio_0.16.31501S.06_3_10.20.31501S.09L_release_255222_signed.exe
hopefully that will work.. downloading it now

pookguy88 said:
yeah, just realized I have a S4... are you sure I have a EU radio though? I got mine from a Canadian (Bell) carrier..
Click to expand...
Click to collapse
.11 was EU I thought--it doesn't matter though
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
pookguy88 said:
I've been trying CM10 (http://forum.xda-developers.com/showthread.php?t=1799139) nightlies...
So for the wiping part, isn't a factory reset (in TWRP) just a data/cache wipe? what does unsecure do? I haven't done that before..
Click to expand...
Click to collapse
gfactory reset is your date
dalvik cache and cache are different and don't impact your personal data

pookguy88 said:
Ok I'm going to try re-locking the bootloader and RUU-ing this:
RUU_Ville_U_BM_1.70.666.1_R_Radio_0.16.31501S.06_3_10.20.31501S.09L_release_255222_signed.exe
hopefully that will work.. downloading it now
Click to expand...
Click to collapse
That will not work...you cannot ruu to a lower hboot...you are on the highest hboot, so ruu is not an option for you since there is no bell mobility ruu for jb out yet...your doing something wrong...probably something very simple you are overlooking.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4

ryanshew said:
That will not work...you cannot ruu to a lower hboot...you are on the highest hboot, so ruu is not an option for you since there is no bell mobility ruu for jb out yet...your doing something wrong...probably something very simple you are overlooking.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
Click to expand...
Click to collapse
@all
is there any way i can get an Europe RUU on this phone? or any custom rom will work on this? if yes then pls inform! if there's a way!
WBR
ReyTech.

[SOLVED] I can't enter into recovery mode. Please help

I broke the digitizer, so I replaced it (I think successfully). I was able to boot it once and everything worked fine. Now all I get is a bootloop with the htc logo on white background.
I wanted to install a newer rom, but I'm unable to enter recovery
If I try to enter recovery pressing vol down and power, and then select recovery and press power, I get the htc logo bootloop again
I was in rom CM 10.2 by Sultan. With S-off. I can't remember which recovery I had installed (4ext or twrp?)
What could I do?
Are there any pc tools like flashtool for Sony devices or Odin/Heimdall for Samsung ones? (preferably for ubuntu)

First eject your battery than reinsert and try again volume and power button
Sent from my HTCSensation using xda app-developers app

Mile_zdr said:
First eject your battery than reinsert and try again volume and power button
Sent from my HTCSensation using xda app-developers app
Click to expand...
Click to collapse
I've done so many times, that's the first thing I've tried.
I was thinking about using adb and fastboot commands to see if I can get to the recovery that way or at least they prompt some errors that tell me what's wrong.
But I don't know what should I do, I've always used some gui (like flashtool or heimdall or odin for other devices, no idea if there's anything like that for htc devices)

devrruti said:
I've done so many times, that's the first thing I've tried.
I was thinking about using adb and fastboot commands to see if I can get to the recovery that way or at least they prompt some errors that tell me what's wrong.
But I don't know what should I do, I've always used some gui (like flashtool or heimdall or odin for other devices, no idea if there's anything like that for htc devices)
Click to expand...
Click to collapse
from fastboot try the command
fastboot reboot recovery
otherwise reflash the recovery again
see only step 2 from here
http://forum.xda-developers.com/showthread.php?t=1631861
for tool see here
http://forum.xda-developers.com/showthread.php?t=1668276

k
rzr86 said:
from fastboot try the command
fastboot reboot recovery
otherwise reflash the recovery again
see only step 2 from here
http://forum.xda-developers.com/showthread.php?t=1631861
for tool see here
http://forum.xda-developers.com/showthread.php?t=1668276
Click to expand...
Click to collapse
ok I've tried everything i could on ubuntu, windows 7 and windows 8.1. Please more ideas?
on Ubuntu
I've installed adb and fastboot and added the file 51-android. rules. I enter fastboot mode on phone and it is recognised by pc.
sudo fastboot reboot recovery does nothing
I've downloaded 4ext recovery and uncompressed
sudo fastboot flash recovery recovery.img
sending 'recovery'
okay
writing 'recovery'
FAILED (remote: not allowed)
I've also placed the 4ext recovery zip file on the sd renamed as PG58IMG.zip, no luck either. it just says parsing, but doesn't do anything else
on windows 7 and 8 I've tried with kgs utility with the option 3 to install a recovery. however this tool didn't work. Sometimes it just closed. other times it complained about md5. I think this tool tries to download Juopunutbear windows version and fails because it is no longer available a link for the windows version
phone was rooted, bootloader unlocked, supercid... using Juopunutbear
it had a recovery installed (i think it was 4ext, but i don't remember)
it had CM 10.2 by sultanxda
i replaced the digitizer. first boot everything was working.
I rebooted to enter the recovery to install a new rom but i can't
i can't boot to rom or recovery. i just get the htc logo bootloop
fastboot tells me remote not allowed
image attached
the bootloader was unlocked, but the "Locked" word was always there if i remember well, i read this was because of unlocking with Juopunutbear instead of htc dev, but that this didn't matter

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
image boot

Try to flash 3.33 universal firmware (check md5 sum before flashing important ) that will give you patched hboot (unlocked) after that try to flash recovery
Edit: here is link for firmware , read the steps carefull Firmware
Sent from my HTCSensation using xda app-developers app

yes do as Mile_zdr suggested
with locked bootloader you can't do almost nothing
before flashing 3.33 universal firmware check md5 sums(important)
by the way i thought you still had unlocked bootloader
edit: because of locked bootloader you don't have access to the rom and recovery

I had unlocked the bootloader with unlimited.io juopunutbear, this is very strange. As I said, I read somewhere that the locked word is there if you use the juopunutbear method, but it was supposedly unlocked. the only thing I did was change the digitizer.
but yeah it looks like it is locked if i can't use fastboot nor recovery. thank you very much, I'll try that firmware and tell you

devrruti said:
I had unlocked the bootloader with unlimited.io juopunutbear, this is very strange. As I said, I read somewhere that the locked word is there if you use the juopunutbear method, but it was supposedly unlocked. the only thing I did was change the digitizer.
but yeah it looks like it is locked if i can't use fastboot nor recovery. thank you very much, I'll try that firmware and tell you
Click to expand...
Click to collapse
also in order to have access in all fastboot commands you need unlocked bootloader or the patched hboot

rzr86 said:
also in order to have access in all fastboot commands you need unlocked bootloader or the patched hboot
Click to expand...
Click to collapse
I am not able to flash the universal firmware 3.33 either
How should I do it?
I put it in the sd card root directory, but it doesn't do anything special either, what should I expect?
I tried this method also with the 4ext recovery zip
I wasn't able to flash 4ext recovery img with fastboot
sudo fastboot flash recovery recovery.img
gives me the remote not allowed error
~$ sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.401.3
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4091mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.485s
Am I unlocked or not? I'm lost
How should I unlock bootloader if that is the case (I had already done so with unlimited.io juopunutbear)
All instructions are for when you are on stock locked firmware
Thanks for your patience. I bought this phone recently and everything was good until I crashed the screen. I don't want to give up but I really don't know what else I can do to fix it.

devrruti said:
I am not able to flash the universal firmware 3.33 either
Click to expand...
Click to collapse
why you are not able to flash 3.33 firmware?

Mile_zdr said:
why you are not able to flash 3.33 firmware?
Click to expand...
Click to collapse
How should i flash it?
what are the options to do it?
should i do it with fastboot? what would be the command?
So far, if i select recovery, all i get is the htc logo bootloop
Whatever I've tried with fastboot gives me remote not allowed
If i place it as a zip on the microsd with the proper name, nothing happens either
I don't know what else to do.
I know it's confusing to help this way.
I could show you a video or maybe with videocall somehow to show everything?

devrruti said:
How should i flash it?
what are the options to do it?
should i do it with fastboot? what would be the command?
So far, if i select recovery, all i get is the htc logo bootloop
Whatever I've tried with fastboot gives me remote not allowed
If i place it as a zip on the microsd with the proper name, nothing happens either
I don't know what else to do.
I know it's confusing to help this way.
I could show you a video or maybe with videocall somehow to show everything?
Click to expand...
Click to collapse
put the firmware.zip in the root of your sdcard as you did(name it as pg58img.zip if it doesn't already)
then boot into bootloader and it will scan and detect it automatically
it will ask you to update
edit: for the command i think is fastboot flash zip pg58img.zip but i am not so sure

rzr86 said:
put the firmware.zip in the root of your sdcard as you did(name it as pg58img.zip if it doesn't already)
then boot into bootloader and it will scan and detect it automatically
it will ask you to update
edit: for the command i think is fastboot flash zip pg58img.zip but i am not so sure
Click to expand...
Click to collapse
yeah I did something! Now I have 3.33, but still bootloop when turning it on and when selecting recovery.
I already had tried like you said puting the recovery or the 3.33 firmware on the sd as zip with that name but it didn't fix anything.
I was able to flash universal firmware 3.33 this way, not sure if that would be fine but i risked:
now boot looks like this compared to the image i attached on the first page
then I was able to flash 4ext recovery this way
sudo fastboot flash recovery recovery.img
it said sending ok, writing ok, finished
it didn't give me the remote not allowed error
however i still have the green htc on white bootloop. I also have this bootloop when i try to select recovery
this happens when i put the recovery zip renamed on the sd root, but nothing else
Excuse the potato camera

devrruti said:
yeah I did something!
I already had tried like you said but it didn't do anything.
I was able to flash universal firmware 3.33 this way, not sure if that would be fine but i risked:
View attachment 2670274
now boot looks like this compared to the image i attached on the first page
View attachment 2670281
then I was able to flash 4ext recovery this way
sudo fastboot flash recovery recovery.img
it said sending ok, writing ok, finished
it didn't give me the remote not allowed error
however i still have the green htc on white bootloop. I also have this bootloop when i try to select recovery
this happens when i put the recovery zip renamed on the sd root, but nothing else
View attachment 2670289
View attachment 2670290
Click to expand...
Click to collapse
now after you flashed 3.33 firmware flash recovery via fastboot step 2 from the link http://forum.xda-developers.com/showthread.php?t=1631861

Mile_zdr said:
now after you flashed 3.33 firmware flash recovery via fastboot step 2 from the link http://forum.xda-developers.com/showthread.php?t=1631861
Click to expand...
Click to collapse
I already tried that way, it says that I flashed it and went ok, however I still get the green htc on white bootloop when I select recovery or just boot.
Your phone will (re)boot, wait until you see a white screen which says "FASTBOOT USB"
Type in: fastboot flash recovery recovery.img
Wait until the flashing is finished
Type in: fastboot reboot
I had problems uploading the images on the post before, they should appear now if reloaded
I'm out of ideas, any suggestion?

devrruti said:
I already tried that way, it says that I flashed it and went ok, however I still get the green htc on white bootloop when I select recovery or just boot.
Your phone will (re)boot, wait until you see a white screen which says "FASTBOOT USB"
Type in: fastboot flash recovery recovery.img
Wait until the flashing is finished
Type in: fastboot reboot
I had problems uploading the images on the post before, they should appear now if reloaded
I'm out of ideas, any suggestion?
Click to expand...
Click to collapse
Did you delete the PG58IMG file? you got to delete. it eject your sd card and if you have sd card reader delete the file or try to go to recovery without sd card

Mile_zdr said:
Did you delete the PG58IMG file? you got to delete. it eject your sd card and if you have sd card reader delete the file or try to go to recovery without sd card
Click to expand...
Click to collapse
yeah I've tried putting different recoveries on the sd, no luck.
then I've deleted them and tried to flash them via fastboot
it all says ok, transfered and installed succesfully (no remote not allowed errors now), but i still get the htc bootloop then if i select recovery or boot normally
i also tried to fastboot flash the recovery without sd card, but still the same

devrruti said:
yeah I've tried putting different recoveries on the sd, no luck.
then I've deleted them and tried to flash them via fastboot
it all says ok, transfered and installed succesfully (no remote not allowed errors now), but i still get the htc bootloop then if i select recovery or boot normally
i also tried to fastboot flash the recovery without sd card, but still the same
Click to expand...
Click to collapse
did you try to go to recovery without sd card or use another sd card (not to flash just go to recovery with other sd card)
otherwise i don't have any other thoughts mate... :/

Won't boot into recovery

It all started yesterday where i was trying to update (InsertCoin) which for some reason made my phone shut down mid-way through the installation process...
I had to reboot my phone back into recovery to wipe system/cache/data to reinstall...For some reason this wiped/damaged everything but the bootloader ofc.
(Bye go all my pictures, whatsapp conversations etc...)
This made me not being able to boot into my recovery aswell
I still can't get back into my recovery, and i've tried flashing the recovery over and over again via fastboot flash recovery twrp.img
When i try to flash the recovery, it succeeds but when i try to boot into it, it blinks the splash screen with odd intervals, i dont know if this means that its trying over and over again...I'm sort of desperate here...any help?
sidenote here: I'm in linux

you should've updated firmware to hboot 2.22 needed for IC, then you need to install the latest recovery 2.7.1.1 from twrp website
twrp here: http://techerrata.com/browse/twrp2/m4ul
new firmware here :http://forum.xda-developers.com/showthread.php?t=2759131

I have not updated it, will go and do that now,

Code:
[email protected]:/media/leon/*censor*/Android/ROMS/Millium$ sudo fastboot flash zip firmware.zip
[sudo] password for leon:
target reported max download size of 800227328 bytes
sending 'zip' (19549 KB)...
OKAY [ 2.466s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 4.305s
Right.....!?
I really don't want to reboot to bootloader at the moment...since the update failed...

Apparently i am S-ON and therefor need to obtain s-off, but i don't have an android system installed..how

s-off required to flash firmware or if s-on, bootloader needs to be re-locked, sorry i assumed you knew that! maybe create a signature giving details of your device for future, it does help.
If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.

Code:
FAILED (remote: 12 signature verify fail)
This ahappens when flashing the firmware
*edit: I have fixed that, but i cannot flash the 2.22 included y you because it has a different modelid, presumably because my m4 isn't the at&t variant.
Will this work?

`leon said:
Code:
FAILED (remote: 12 signature verify fail)
This ahappens when flashing the firmware
Click to expand...
Click to collapse
not work ?? ok, then you will need to s-off the device, unlock first,you need SUPERCID also

Braddison said:
not work ?? ok, then you will need to s-off the device, unlock first
Click to expand...
Click to collapse
It did, sorry, didnt edit the post quick enough

`leon said:
Code:
FAILED (remote: 12 signature verify fail)
*edit: I have fixed that, but i cannot flash the 2.22 included y you because it has a different modelid, presumably because my m4 isn't the at&t variant.
Will this work?
Click to expand...
Click to collapse
no that firmware will not update everything that is required, use the firmware zip in the link i gave previously.
you need to change your cid to supercid,,,,very simple to do
Enter the command "fastboot oem readcid". Make a note of your original CID.
enter the command "fastboot oem writecid 11111111" make sure it is 8 ones (1)
enter the command "fastboot read cid" [it should confirm your CID is 11111111]

Braddison said:
no that firmware will not update everything that is required, use the firmware zip in the link i gave previously.
you need to change your cid to supercid,,,,very simple to do
Enter the command "fastboot oem readcid". Make a note of your original CID.
enter the command "fastboot oem writecid 11111111" make sure it is 8 ones (1)
enter the command "fastboot read cid" [it should confirm your CID is 11111111]
Click to expand...
Click to collapse
Yeah, i just tried that 5 minutes ago, though...:
Code:
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
Gosh...my device doesn't like me..
oh, wait, don't i have to unlock bootloader?
i'll try that now
OMG IM IN RECOVERY
cant seem to do anything with my data partition, same goes for internal storage

well you've done everything that i done when i tried out Insertcoin rom for a few days and never had any of your issues. so not sure whats going on.
- unlocked bootloader
- get s-off
- get supercid
- update firmware
- get latest twrp recoverry
- install Insert Coin
use the fix miniwhooper posted on her firmware thread ....Flash stock recovery and factory reset from boot loader. It will fix you /data partition.. then flash custom recovery and it should be fixed

`leon said:
Yeah, i just tried that 5 minutes ago, though...:
Code:
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
Gosh...my device doesn't like me..
oh, wait, don't i have to unlock bootloader?
i'll try that now
OMG IM IN RECOVERY
cant seem to do anything with my data partition, same goes for internal storage
Click to expand...
Click to collapse
Make sure you are in the folder your rom zip is located.
Run the command...
adb push filename.zip /sdcard
Wait around 10 minutes as it will not give you progress
go back to TWRP main page and install, choose SDcard and the zip file you just uploaded should be there.

hello @AnGrY sCoTsMaN
i have the exact same problem but i flashed cm.12.1 cant boot in recovery or flash anything using adb
hboot os 2.22 it says unlocked but it seems not
can you please help me out
Edit: problem solved without doing anything

HTC One XL Evita - Boot loop - Can't flash/sd corrupt?

Hey all,
Have a htc one xl evita that has been running fine for quite a while on CM11 nightlies.
Can't remember which kernal is on there.
My phone went flat a few days ago and then went into a bootloop.
I didnt think much of it, figuired id just reflash a different rom and it would be fine.
Its a very strange scenario.
I can flash different roms, they either fail or flash ok, but the flash doesn't actually work.
Eg. It might say it flashed ok, but on reboot, nothing is different.
I have tried flashing the latest TWRP, CWM, CWM touch recovery, it says it flashes ok, but it doesnt actually flash.
I have tried to run an RUU exe....
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe
Can't detect the phone.
I have seen you can manually try and flash a ruu by getting the files from the zip in the temp file but i cant extract anything from the zip, says it corrupt,
I have tried to follow a few guides that say to run the fastboot oem rebootRUU command, but that just reboots the phone and tried to load CM.
I also cant mount SD card from recovery.
I also cant actually wipe anything from the sd card. It says it wipes, but doesnt actually do anything.
I am maybe thinking the sd card is corrupt?
I get a few odd errors in recovery when trying to flash. Things like ...
e error in /cache/recovery/log read-only file system
Tried to flash a rom just now - error - E: could not extract 'meta-inf/com/google/android/update-binary.
3 different roms do that.
I seem to be able to ADB push files to the phone, they dont seem to stay there though.
The only thing i have been able to get the phone to do is run a temp recovery by using the Windroid HTC one xl toolkit.
It will reboot into whichever kernal i pick. But no changes i make in there actually do anything
Sorry for the wall of text, just wanted to put it all up there to answer as many questions as i can.
Any help would be great.
Fastboot details below.
------------------------------------------------
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: deleted
(bootloader) imei: deleted
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8312000
(bootloader) cidnum: 22222222
(bootloader) battery-status: low
(bootloader) battery-voltage: 3537mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s

What were you doing with the phone when it started acting up? Was an app installed...did you install a certain mod?
---------- Post added at 10:52 AM ---------- Previous post was at 10:49 AM ----------
I see a problem already. Maybe its cuz your cid is 2222222 and not 11111111. Look under timaaas signature. In his beginners thread it will help you

Absolutely nothing had been changed, Hadn't installed an app for a week or so. The phone just went flat one night.
Wouldn't boot the next morning.
Yeah the cid 22222222 thing, rooted it over a year ago and cant remember why i made it 22222222, i think i had problems with it going to 11111111 but 2222222 worked ok.
I have flashed many roms and kernals in the last 12 months. All with a cid of 22222222. So that shouldnt be a problem
-+------------------------
marknoll said:
What were you doing with the phone when it started acting up? Was an app installed...did you install a certain mod?
---------- Post added at 10:52 AM ---------- Previous post was at 10:49 AM ----------
I see a problem already. Maybe its cuz your cid is 2222222 and not 11111111. Look under timaaas signature. In his beginners thread it will help you
Click to expand...
Click to collapse

I don't think your device is properly rooted.

Over time the flashing affected your device. At times when one thinks the phone is properly rooted, it will run for a while. But after time it may corrupt the phone and or SD cards

Ok, so what do i do to FIX my root?
Also i worried that when i try and run the fastboot oem rebootruu command that it just reboots the phone.
Won't i need that command to fix things?

marknoll said:
I don't think your device is properly rooted.
Click to expand...
Click to collapse
What makes you say that?
marknoll said:
Over time the flashing affected your device. At times when one thinks the phone is properly rooted, it will run for a while. But after time it may corrupt the phone and or SD cards
Click to expand...
Click to collapse
What do you mean by properly rooted? Being rooted only means you have root privileges on the device. Do you mean something else?
neo__04 said:
Ok, so what do i do to FIX my root?
Also i worried that when i try and run the fastboot oem rebootruu command that it just reboots the phone.
Won't i need that command to fix things?
Click to expand...
Click to collapse
My guess is that your sd card has become corrupt at some point. Exactly which version of TWRP are you running? When you say you can't mount the sd card from TWRP do you mean to your pc?
Sent from a crappy Samsung because my Evita died

timmaaa said:
What makes you say that?
What do you mean by properly rooted? Being rooted only means you have root privileges on the device. Do you mean something else?
My guess is that your sd card has become corrupt at some point. Exactly which version of TWRP are you running? When you say you can't mount the sd card from TWRP do you mean to your pc?
Sent from a crappy Samsung because my Evita died
Click to expand...
Click to collapse
I meant properly configured. Why does he have 22222222?

I am running twrp 2.7.0.8
A further little update, i did manage to mount my sd card (in windows im talking about)
I ran the windroid all in one kit to do a temp recovery boot with cwm touch.
I managed to mount the internal storage and format it.
But i dont think it actually did it.
I then tried to flash a rom, and it gave me a symlink error in cwm.
I do think its problems somehow with the sd card or write permissions or something of the kind.

marknoll said:
I meant properly configured. Why does he have 22222222?
Click to expand...
Click to collapse
22222222 is just another form of SuperCID, it's just like having 11111111 as your CID.
Sent from a crappy Samsung because my Evita died
---------- Post added at 08:58 AM ---------- Previous post was at 08:56 AM ----------
neo__04 said:
I am running twrp 2.7.0.8
A further little update, i did manage to mount my sd card (in windows im talking about)
I ran the windroid all in one kit to do a temp recovery boot with cwm touch.
I managed to mount the internal storage and format it.
But i dont think it actually did it.
I then tried to flash a rom, and it gave me a symlink error in cwm.
I do think its problems somehow with the sd card or write permissions or something of the kind.
Click to expand...
Click to collapse
Flash TWRP 2.7.1.0 and use that to format your sd card. What ROM are you flashing?
Sent from a crappy Samsung because my Evita died

The problem is that nothing i flash actually sticks.
I can flash twrp 2.7.1.0, reboot to bootloader, then go into recovery, still 2.7.0.8.
Nothing i do actually sticks.
The only thing that works is a temporary recovery flash from the All in one toolkit, it will boot to any recovery then, but only the once.
i have a few roms on the sd card. I have tried flashing a stock telstra rom, Aokp, CM11, viper 3.2.7. Whatever was on my phone ive tried.
When i adb push files to it, it says it works, but doesnt actually come up on the sd card.
something very odd is happing.
Soooo annoying, nothing seems to work!

Exactly how are you flashing the recovery?
Sent from a crappy Samsung because my Evita died

the normal command
fastboot flash recovery xxxxxx.img

Are you giving the "fastboot erase cache" command after?
Sent from a crappy Samsung because my Evita died

have tried that yes, normally i hadn't needed to do that in the past.
But have tried that in the last few days while trying to fix the problem

Could he(neo) try and download min adb and fastboot so he could successfully run Ru u?

Ok, so im home for a lunch break so i'll try and rerun a recovery flash. Twrp 2.7.1.0
- So i put the phone in fastboot.
------
C:\android>fastboot flash recovery twrp2710.img
sending 'recovery' (8588 KB)...
OKAY [ 1.041s]
writing 'recovery'...
OKAY [ 3.461s]
finished. total time: 4.502s
--------
C:\android>fastboot erase cache
erasing 'cache'...
OKAY [ 0.841s]
finished. total time: 0.841s
---------------------------------
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.074s]
finished. total time: 0.074s
---------------------------------------------
Phone didnt actually reboot, just turned off, i powered it on while holding the vol down.
selected recovery from hboot menu.
Booted to recovery with twrp 2.7.0.8
Flash done nothing.....
Im lost

marknoll said:
Could he(neo) try and download min adb and fastboot so he could successfully run Ru u?
Click to expand...
Click to collapse
He already has fastboot installed.
Sent from a crappy Samsung because my Evita died
---------- Post added at 01:35 PM ---------- Previous post was at 01:32 PM ----------
neo__04 said:
Ok, so im home for a lunch break so i'll try and rerun a recovery flash. Twrp 2.7.1.0
- So i put the phone in fastboot.
------
C:\android>fastboot flash recovery twrp2710.img
sending 'recovery' (8588 KB)...
OKAY [ 1.041s]
writing 'recovery'...
OKAY [ 3.461s]
finished. total time: 4.502s
--------
C:\android>fastboot erase cache
erasing 'cache'...
OKAY [ 0.841s]
finished. total time: 0.841s
---------------------------------
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.074s]
finished. total time: 0.074s
---------------------------------------------
Phone didnt actually reboot, just turned off, i powered it on while holding the vol down.
selected recovery from hboot menu.
Booted to recovery with twrp 2.7.0.8
Flash done nothing.....
Im lost
Click to expand...
Click to collapse
It looks like you have corrupt partitions, which I don't think you're gonna be able to repair yourself. A jtag repair is probably a good option for you at this strange. But, the corruption could have been caused by an emmc that's going bad, so the problem could reappear.
Sent from a crappy Samsung because my Evita died

Any suggestions on someone in Australia/Melbourne to get a jtag repair done?
Happy to pay if its going to fix it

I don't know of any personally, a Google search should uncover them though. If you do find one, let me know, I'm in Melbourne too all I'd be interested to know what turns up.
Sent from a crappy Samsung because my Evita died

[GUIDE][S4] How to install HBOOT 2.16 | For first time users

HBOOT 2.16 Installation guide​
Requirements before installing​
Back up your files, your SD Card will be WIPED!
Charge your phone to AT LEAST 30%
Your bootloader MUST be unlocked
You NEED to be S-OFF or else it won't work
You need basic knowledge of Fastboot commands
Windows 10/8/7/Vista/XP: You need drivers installed
Windows 8.1: You need drivers installed AND update kb2967917 from Microsoft
Linux: You need "51-android.rules" or "99-android.rules" configured
Mac: Nothing needed that I know of
I am NOT responsible if you break your phone
​
This guide will be from a Windows point of view
Installation Guide​
Download the HBOOT 2.16 firmware file from here: Download from Mega.co.nz
Place it in your adb and fastboot folder. For example C:\Users\(Your Username)\Fastboot
Now open a Command Prompt window and then type in:
Code:
cd C:\(Location of your Fastboot folder)
Now take your phone and connect it to your computer (with USB Debugging ON) and type in:
Code:
adb reboot bootloader
Once you are in the bootloader and it displays "Fastboot USB", type in:
Code:
fastboot oem rebootRUU
Once your computer recognizes your phone type in:
Code:
fastboot flash zip Firmware_4.06.401.1.zip
If you changed the file name make sure to type in the name of it instead of the one above
You will then get an error:
Code:
"FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
Don't worry, this is normal. DO NOT unplug your phone. Simply type in once again:
Code:
fastboot flash zip Firmware_4.06.401.1.zip
If you changed the file name make sure to type in the name of it instead of the one above
Then wait until the Command window says "finished" and type in:
Code:
fastboot reboot-bootloader
Next we need to download TWRP recovery. You can download it from MDMower's website and MAKE SURE to get TWRP for "/data/media storage (HBOOT 2.16.0000)" and TWRP 2.8.0.1 or above.
Now we must go back to the command window with your phone still plugged in displaying "Fastboot USB" on the screen
Then we type:
Code:
cd C:\Users\(Your Username)\Downloads
or if the TWRP Recovery file isn't in the above location just direct it to the folder its stored in
Now we type:
Code:
fastboot flash recovery twrp-2.8.x.x-ville-dm.img
just replace the "x" with the numbers on the file. e.g. - 2.8.0.1
Once it flashed successfully press the power button and use the volume buttons to scroll down to recovery and to boot into it, simply press the power button
Now go into "Mounts" and select Enable MTP if it isn't already.
Now copy a ROM of your choice (That supports HBOOT 2.16) and flash it. If MTP doesn't work, simply sideload the ROM
That's it, now you just reboot after installing your ROM.
Hope this helps anybody having difficulty with HBOOT 2.16

Getting a different error when flashing.
c:\adb>fastboot flash zip Firmware_4.06.401.1.zip
sending 'zip' (46472 KB)...
OKAY [ 2.598s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 4.304s

urlyisis said:
Getting a different error when flashing.
c:\adb>fastboot flash zip Firmware_4.06.401.1.zip
sending 'zip' (46472 KB)...
OKAY [ 2.598s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 4.304s
Click to expand...
Click to collapse
You need to change your cid
To change it go into bootloader, then fastboot, connect it to your computer and type
Code:
fastboot oem writecid 11111111
that is eight 1s
If that didnt work then type instead
Code:
fastboot oem writecid HTC__001
that is 2 underscores after HTC

I get this:
Code:
Z:\One_S_All-In-One_Kit_v1.1\Data>fastboot flash zip Firmware_4.06.401.1.zip
sending 'zip' (46472 KB)... OKAY [ 6.507s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 8.020s
No matter how often I attempt it. Redownloaded the zip to make sure it is not corrupt...
Any pointer?
Ah, damn, because I followed the instructions to the end despite the HBOOT not flashing I can also now not access recovery anymore. It seems the new version of recovery was properly flashed, but as it relies on higher HBOOT I can't get into it anymore. It is still in HBOOT 1.03.
Can anyone help me to get this phone ready for Cyanogenmod?

I was able to load the hboot, but now the bootloader is locked again and I can't flash the recovery.
FAILED (remote: not allowed)

Walter_White said:
I get this:
Code:
Z:\One_S_All-In-One_Kit_v1.1\Data>fastboot flash zip Firmware_4.06.401.1.zip
sending 'zip' (46472 KB)... OKAY [ 6.507s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 8.020s
No matter how often I attempt it. Redownloaded the zip to make sure it is not corrupt...
Any pointer?
Ah, damn, because I followed the instructions to the end despite the HBOOT not flashing I can also now not access recovery anymore. It seems the new version of recovery was properly flashed, but as it relies on higher HBOOT I can't get into it anymore. It is still in HBOOT 1.03.
Can anyone help me to get this phone ready for Cyanogenmod?
Click to expand...
Click to collapse
Get s-off change your cid to HTC__001 as shown above and run this ruu, then follow the instructions above

urlyisis said:
I was able to load the hboot, but now the bootloader is locked again and I can't flash the recovery.
FAILED (remote: not allowed)
Click to expand...
Click to collapse
It looks like your s-on

UPDATE: I had to unlock the bootloader via the HTC unlock. RESOLVED
dd98 said:
It looks like your s-on
Click to expand...
Click to collapse
Actually, the bootloader shows the following.
***** Tampered ******
Locked
VLE PVT SHIP S-OFF RL
CID-HTC__001
HBOOT-2.16.000

dd98 said:
HBOOT 2.16 Installation guide​
Requirements before installing​
Back up your files, your SD Card will be WIPED!
Charge your phone to AT LEAST 30%
Your bootloader MUST be unlocked
You NEED to be S-OFF or else it won't work
You need basic knowledge of Fastboot commands
Windows 10/8/7/Vista/XP: You need drivers installed
Windows 8.1: You need drivers installed AND update kb2967917 from Microsoft
Linux: You need "51-android.rules" or "99-android.rules" configured
Mac: Nothing needed that I know of
I am NOT responsible if you break your phone
​
This guide will be from a Windows point of view
Installation Guide​
Download the HBOOT 2.16 firmware file from here: Download from Mega.co.nz
Place it in your adb and fastboot folder. For example C:\Users\(Your Username)\Fastboot
Now open a Command Prompt window and then type in:
Code:
cd C:\(Location of your Fastboot folder)
Now take your phone and connect it to your computer (with USB Debugging ON) and type in:
Code:
adb reboot bootloader
Once you are in the bootloader and it displays "Fastboot USB", type in:
Code:
fastboot oem rebootRUU
Once your computer recognizes your phone type in:
Code:
fastboot flash zip Firmware_4.06.401.1.zip
If you changed the file name make sure to type in the name of it instead of the one above
You will then get an error:
Code:
"FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
Don't worry, this is normal. DO NOT unplug your phone. Simply type in once again:
Code:
fastboot flash zip Firmware_4.06.401.1.zip
If you changed the file name make sure to type in the name of it instead of the one above
Then wait until the Command window says "finished" and type in:
Code:
fastboot reboot-bootloader
Next we need to download TWRP recovery. You can download it from MDMower's website and MAKE SURE to get TWRP for "/data/media storage (HBOOT 2.16.0000)" and TWRP 2.8.0.1 or above.
Now we must go back to the command window with your phone still plugged in displaying "Fastboot USB" on the screen
Then we type:
Code:
cd C:\Users\(Your Username)\Downloads
or if the TWRP Recovery file isn't in the above location just direct it to the folder its stored in
Now we type:
Code:
fastboot flash recovery twrp-2.8.x.x-ville-dm.img
just replace the "x" with the numbers on the file. e.g. - 2.8.0.1
Once it flashed successfully press the power button and use the volume buttons to scroll down to recovery and to boot into it, simply press the power button
Now go into "Mounts" and select Enable MTP if it isn't already.
Now copy a ROM of your choice (That supports HBOOT 2.16) and flash it. If MTP doesn't work, simply sideload the ROM
That's it, now you just reboot after installing your ROM.
Hope this helps anybody having difficulty with HBOOT 2.16
Click to expand...
Click to collapse
Whatever which recover i choose, my internal storage was always 48mb, i can not push rom, can not sideload rom,

ad346544521 said:
Whatever which recover i choose, my internal storage was always 48mb, i can not push rom, can not sideload rom,
Click to expand...
Click to collapse
You need the hboot 2.16 specific recovery, you can download it here

Never mind, I found what I needed...

Hi, do you have the firmware for t-mobile to downgrade to 2.15? I tried https://mega.co.nz/#!s54F3YqK!QrNjMlieIG65jsaGWS8eXDdLc5FcYM7IEmqTk_pHbFA but doesnt work. I think because is not for tmobile. I cant downloade the full RUU because the download always fails and my internet is so slow.
EDIT: I dont need it anymore, a friend download the file for me. Just a question. in hboot 2.16, gave me more space for my data, i like that, there is no way to make old roms to work on hboot 2.16?

Cannot get this method to work. I'm unlocked and S-OFF. But whenever I try to flash the firmware*.zip I get the message
FAILED (remote: not allowed)
I'm about ready to give up on HBoot 2.16.

confused on twrp for hboot 2.16
Hi thanks a lot for this very clear tuto that help me successfully upgrade to hboot 2.16 without any error issue. everything followed attentively and step by step .
However i am a littlee confused at the step bellow.
When i reached the download section of specified url , concerning TWRP , there is only twrp 2.7 concerning hboot 2.16
But in the tuto you talk about twrp 2.8.. or above. So please can you clarify me on this ?
Thanks
dd98 said:
HBOOT 2.16 Installation guide​
[*]Next we need to download TWRP recovery. You can download it from ......and MAKE SURE to get TWRP for "/data/media storage (HBOOT 2.16.0000)" and TWRP 2.8.0.1 or above.
Click to expand...
Click to collapse

delacosta4526 said:
Hi thanks a lot for this very clear tuto that help me successfully upgrade to hboot 2.16 without any error issue. everything followed attentively and step by step .
However i am a littlee confused at the step bellow.
When i reached the download section of specified url , concerning TWRP , there is only twrp 2.7 concerning hboot 2.16
But in the tuto you talk about twrp 2.8.. or above. So please can you clarify me on this ?
Thanks
Click to expand...
Click to collapse
Sorry, this is an old tutorial. Go to this link, download the latest file and flash it in fastboot mode by typing: fastboot flash recovery twrp-2.8.x.x.img (or whatever the file name is)

thanks..but
dd98 said:
Sorry, this is an old tutorial. Go to link, download the latest file and flash it in fastboot mode by typing: fastboot flash recovery twrp-2.8.x.x.img (or whatever the file name is)
Click to expand...
Click to collapse
thanks that is what i did.
But i though this would have help fix wifi, bluetooth not working since stock rom before i flash with "LIBERTY ROM - The Sixth Element" (that did not fix the problem)
Did you anything that can help ? My phone is Htc one s (actually : hboot 2.16 , TWRP 2.8.0.5, radio 1.20, unlocked, s-off, rooted, and with LIBERTY ROM - The Sixth Element" .

delacosta4526 said:
thanks that is what i did.
But i though this would have help fix wifi, bluetooth not working since stock rom before i flash with "LIBERTY ROM - The Sixth Element" (that did not fix the problem)
Did you anything that can help ? My phone is Htc one s (actually : hboot 2.16 , TWRP 2.8.0.5, radio 1.20, unlocked, s-off, rooted, and with LIBERTY ROM - The Sixth Element" .
Click to expand...
Click to collapse
No the recovery version will NEVER affect anything that does/doesn't work on the rom. Since you are using Liberty rom, make sure you are using the 4.4.2 version because the 4.4.3 version is very buggy

of course
dd98 said:
No the recovery version will NEVER affect anything that does/doesn't work on the rom. Since you are using Liberty rom, make sure you are using the 4.4.2 version because the 4.4.3 version is very buggy
Click to expand...
Click to collapse
Yes surely . i am using 4.4.2. I have carefully read i lot of things including that.
Thanks

Guys can someone please help me?
I am on Windows 10 desperately trying to find a solution on the ''WAITING DEVICE'' response after I type
fastboot oem rebootRUU
I have tried installing a bunch of drivers , driver updates on device manager etc with no luck.
The device is just not responding.
Thanks

File Offline
Unfortunately the HBoot 2.16 file is offline. Can someone please reupload it?
Thank you!