[!] HTC defeats XDA developers community - Android General

XDA can't find a way to overcome wrong CID issue with HTC One V
Ok, this is device specific to the HTC One V, but the One V community at xda is tiny and I've posted there with zero replies after 24 hrs. Maybe someone else familiar with HTC can help me out here.
I'm trying to flash the HTC EU ROM onto my Asia market HTC One V (unlocked bl, rooted, cwm recovery). The two ROMs are compatible as they are both for the same part number (PK7610000). In the android-info.txt inside both ROM.zips the only difference is the rotten CID.
I've searched the forum and Google high and low to solve this and have come up with the following:
1. Running the RUU. Result: "Wrong customer" error.
2. Grabbing rom.zip from RUU temp files, renaming PK76IMG.zip, flashing from bootloader. Result: No dice.
3. Repeat step 2 on a Goldcard. Tried MMC0 and MMC2 (GoldCard generator got errors with MMC1). Result: "CID incorrect! Update Fail!"
4. Flashing zip from command line as follows:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
Result: "CID error"
5. Relocking bootloader and repeating #4. Result: same.
6. Change CID as follows: fastboot oem writecid HTC__001. Result: COMMAND ERROR!
7. Downloaded various other fastboot.exe and re-run step 6. Result: COMMAND ERROR!
8. Flashing with fastboot: fastboot flash system system.img. Result: "FAILED (remote: data length is too large)." This one boggles me because the extracted system.img for the HTC UE ROM (what I'm trying to flash) is identical to the HTC Asia ROM (what I have).
9. What's your idea???????
BTW, can I replace the android-info.txt in the HTC EU ROM with the one from the HTC Asia ROM without negative ramifications?

CafeKampuchia said:
Ok, this is device specific to the HTC One V, but the One V community at xda is tiny and I've posted there with zero replies after 24 hrs. Maybe someone else familiar with HTC can help me out here.
I'm trying to flash the HTC EU ROM onto my Asia market HTC One V (unlocked bl, rooted, cwm recovery). The two ROMs are compatible as they are both for the same part number (PK7610000). In the android-info.txt inside both ROM.zips the only difference is the rotten CID.
I've searched the forum and Google high and low to solve this and have come up with the following:
1. Running the RUU. Result: "Wrong customer" error.
2. Grabbing rom.zip from RUU temp files, renaming PK76IMG.zip, flashing from bootloader. Result: No dice.
3. Repeat step 2 on a Goldcard. Result: "CID incorrect! Update Fail!"
4. Flashing zip from command line as follows:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
Result: "CID error"
5. Relocking bootloader and repeating #4. Result: same.
6. Change CID as follows: fastboot oem writecid HTC__001. Result: COMMAND ERROR!
7. Downloaded various other fastboot.exe and re-run step 6. Result: COMMAND ERROR!
8. Flashing with fastboot: fastboot flash system system.img. Result: "FAILED (remote: data length is too large)." This one boggles me because the extracted system.img for the HTC UE ROM (what I'm trying to flash) is identical to the HTC Asia ROM (what I have).
9. What's your idea???????
BTW, can I replace the android-info.txt in the HTC EU ROM with the one from the HTC Asia ROM without negative ramifications?
Click to expand...
Click to collapse
Off hand I would say that whatever tool/method you used to create the goldcard used the wrong mmc value. That is very common with the newer HTC devices. Try to find a tool that supports MMC0/MMC1 and possibly MMC2

Thanks, I'll give that a try this evening.
Any other suggestions?

tpbklake said:
Off hand I would say that whatever tool/method you used to create the goldcard used the wrong mmc value. That is very common with the newer HTC devices. Try to find a tool that supports MMC0/MMC1 and possibly MMC2
Click to expand...
Click to collapse
MMC1 didn't work. SimpleGoldCard.exe reported errors.
MMC2 produced a different CID and successfully generated a GoldCard, but the install failed again: "CID incorrect! Update Fail!"
Any more ideas? It can't be impossible to do this!

DELETE

Persistence
Last bump before conceding defeat.

Related

trying to go back to stock rom but it fails

i am using the ruu evita 1.73.502.1 zip and my image version is 1.88.707.2 and it gives me an error 155 unknown error.
can it be because its a lower version
lorijuan1024 said:
i am using the ruu evita 1.73.502.1 zip and my image version is 1.88.707.2 and it gives me an error 155 unknown error.
can it be because its a lower version
Click to expand...
Click to collapse
yes it is
you can downgrade using this method:
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
jags_the1 said:
yes it is
you can downgrade using this method:
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
Click to expand...
Click to collapse
Hmm just yesterday I flashed the 1.73 Ruu on top of a rooted 1.85 no hacks needed other than relocking the bootloader

fix bootloops, bricks, sd card mount errors (solved)

* How To Root, Update Firmware, & Flash A Custom ROM
*
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
You must know how to adb fastboot with command promt windows only
Download this :
https://db.tt/XhPpOiVS
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery.
--> Intermission
Your current phone status
Bootloader = Unlocked
S-OFF
HBOOT = 2.15
CID = T-MOB010
Custom Recovery = TWRP 2.3.3
You are now ready to flash any Jelly beam ROM.

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

[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!

I lost my system

DEAR ALL,
I have tried to put a rom in my htc oneE8. i lost every thing.
My htc only booting in recovery . if i tried to boot in system it hnged up at htc logo for more than 6 hours.
please i need simple steps to get my phone back.
my phone is htc one E8. single sim - S-off.
:
flash this ruu for single sim E8
https://mega.co.nz/#!LQoSWThK!yWhYVzz5K3yFQUgpI2hV1c9VlFfeAxW2sKs72wBaVYg
follow these instructions
1. Rename file to RUU.zip
2. Place it in adb folder
3. Reboot phone to fastboot mode
4. S On need to relock bootloader (fastboot oem lock) , S Off lock not needed
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe here : https://www.androidfilehost.com/?fid=95916177934539737
Run the following commands from your adb folder:
6.fastboot oem rebootRUU
7.fastboot flash zip RUU.zip
8.fastboot reboot
re
its always give me remote eroor
Which recovery does it boot into, Stock/ TWRP? Could you post your exact model?

Categories

Resources