Database Info

Root official ics for desire s

has anyone already tried to root there official ics Rom that was released yesterday? And how?
Sent from my HTC Desire S using xda premium

Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.

SimonTS said:
Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.
Click to expand...
Click to collapse
anyone can confirm this is working?

mayurh said:
anyone can confirm this is working?
Click to expand...
Click to collapse
Yes. I can - that's why I posted the solution.
Or you can just use the search button. :banghead:

SimonTS said:
Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.
Click to expand...
Click to collapse
Simon your DS was S-ON and you got it S-OFF with this procedure.
You pushed the 4ext recovery on a S-ON bootloader, right?
thank you

linqdesires said:
Simon your DS was S-ON and you got it S-OFF with this procedure.
You pushed the 4ext recovery on a S-ON bootloader, right?
thank you
Click to expand...
Click to collapse
No, my DS was S-Off - done with XTC-Clip 18 months ago.

Go to recovery mode;
choose .zip from sd card
Flash this
100%

potencia said:
Go to recovery mode;
choose .zip from sd card
Flash this
100%
Click to expand...
Click to collapse
give thanks is for free

For the people, like me, who have only done the HTCdev unlock ( S-ON ), it's quite easy to update the software/ROM using the RUU.
After downloading the RUU from here : http://forum.xda-developers.com/showthread.php?t=1857478 I just immediately ran it, but it failed with an error along the lines of : RUU, security fail! update fail!
So after a bit of googling around I figured that the RUU might simply not be happy with the phone being in an unlocked state, so after doing the following the RUU ran successfully :
1. Re-lock the bootloader with the "fasboot oem lock" command. The output after running the command shows the lock process was successful but moaned about something else failing, still not sure what that was. So after doing this my phone was kinda stuck in the bootloader, where it says ***relocked*** at the top and ***security warning!*** right underneath it. Everytime I reboot or powercycle it would just boot straight back into the bootloader with the warnings, which worried me a little bit.
2. In the bootloader I selected fastboot and connected the USB cable, and then I ran the RUU again. This time it completed successfully after some time. My HTC sync was installed but not running, so seems like that isn't even needed ?
And that's actually it. This process obviously puts the phone in a relocked state, and an overall factory configuration, it also restores the recovery ROM to the factory image or whatever.

No success
Hi,
I try to root my S-off /XTC Clip/ device, BUT:
1. 4ext pushed with adb - OK
2. I try to install recovery - 4ext wants busybux
3. I downloaded busybox - but it wants a rooted devices I got a message that "unrooted device" and busybox is closed
So I don't have recovery menu
What could be the solution ?

w_hy said:
Hi,
I try to root my S-off /XTC Clip/ device, BUT:
1. 4ext pushed with adb - OK
2. I try to install recovery - 4ext wants busybux
3. I downloaded busybox - but it wants a rooted devices I got a message that "unrooted device" and busybox is closed
So I don't have recovery menu
What could be the solution ?
Click to expand...
Click to collapse
Read the instructions correctly. Install RUU. Put phone into FastBoot mode. Use ADB to push recovery to phone. Reboot into recovery. Flash superuser from zip. Reboot phone properly. Install BusyBox from Play Store.

steps made by me
SimonTS said:
Read the instructions correctly. Install RUU. Put phone into FastBoot mode. Use ADB to push recovery to phone. Reboot into recovery. Flash superuser from zip. Reboot phone properly. Install BusyBox from Play Store.
Click to expand...
Click to collapse
1. Install RUU. -- OK
2. Put phone into FastBoot mode. -- OK
3. Use ADB to push recovery to phone. -- OK
4. Reboot into recovery. -- NOT OK -- there is no recovery menu just the red triangle.

w_hy said:
1. Install RUU. -- OK
2. Put phone into FastBoot mode. -- OK
3. Use ADB to push recovery to phone. -- OK
4. Reboot into recovery. -- NOT OK -- there is no recovery menu just the red triangle.
Click to expand...
Click to collapse
Post the exact steps and output of what you're doing. Recovery obviously isn't getting successfully installed. Which recovery are you using as well?

Isn't fastboot flash recovery recovery.img the command to flash a recovery?
Sent from my Desire S using xda app-developers app

c.m.b said:
Isn't fastboot flash recovery recovery.img the command to flash a recovery?
Click to expand...
Click to collapse
Yes

SimonTS said:
Post the exact steps and output of what you're doing. Recovery obviously isn't getting successfully installed. Which recovery are you using as well?
Click to expand...
Click to collapse
Steps made by me:
1. installed RUU -- OK
2. downloaded recovery.zip, extracted recovety.img (same directory as adb/fastboot)
3. restart phone to bootloader, fastboot usb mode
4. used "fastboot flash recovery recovery.img" command
5. got the next output:
G:\0\1>fastboot flash recovery recovery.img
sending 'recovery' (3768 KB)... OKAY [ 0.655s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.655s
In the recovery.zip file there is a version file:
ext.version=1005.3.0
ext.build=0
and recovery.md5:
3fd4750734837f6bce55b63def1e0a8b

w_hy said:
Steps made by me:
1. installed RUU -- OK
2. downloaded recovery.zip, extracted recovety.img (same directory as adb/fastboot)
3. restart phone to bootloader, fastboot usb mode
4. used "fastboot flash recovery recovery.img" command
5. got the next output:
G:\0\1>fastboot flash recovery recovery.img
sending 'recovery' (3768 KB)... OKAY [ 0.655s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.655s
In the recovery.zip file there is a version file:
ext.version=1005.3.0
ext.build=0
and recovery.md5:
3fd4750734837f6bce55b63def1e0a8b
Click to expand...
Click to collapse
What#s your current hBoot? And make sure you using the recovery files from 4EXT_Recovery_v2.2.7_RC5.zip

SimonTS said:
What#s your current hBoot? And make sure you using the recovery files from 4EXT_Recovery_v2.2.7_RC5.zip
Click to expand...
Click to collapse
hboot is 2.00...
Can you give me a link for EXT_Recovery_v2.2.7_RC5.zip, please?

w_hy said:
hboot is 2.00...
Can you give me a link for EXT_Recovery_v2.2.7_RC5.zip, please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=21895635&postcount=172

SimonTS said:
http://forum.xda-developers.com/showpost.php?p=21895635&postcount=172
Click to expand...
Click to collapse
So:
hboot: 2.02.0002
s-off /xtc clip/
recovery.img: what you said /puted in new directory togeather with adb.exe and fastboot.exe/
command: as before
result: the same:
G:\0\4>fastboot flash recovery recovery.img
sending 'recovery' (5624 KB)... OKAY [ 0.987s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.988s

Recover a 4.4.4 downgrade brick! (Temporal solution)

So, i have noted a increased number of threads about people who have soft-bricked their phones downgrading from 4.4.4 GPE after recieving the OTA, since it includes a new partition table and there's no firmware image yet.
Worry not, i have found a solution for your problem. This method only let's you use custom ROMs (sadly), but it's meant to be a temporal solution while we wait for a 4.4.4 GPE image anyways.
So, without further ado, here's my fix:
You will need:
-The good ol' Android SDK
http://developer.android.com/sdk/index.html#download
-Motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
-A custom recovery. I recommend TWRP, since is the only one i have tested.
Official TWRP Images for Moto G: http://techerrata.com/file/twrp2/xt1032/openrecovery-twrp-2.7.1.1-xt1032.img
-The gpt.bin from 4.4.4 (this is the partition table)
I extracted it from the OTA file and uploaded to my Dropbox: https://dl.dropboxusercontent.com/u/82658555/gpt.bin
-A custom ROM of your choice (obligatory) + GApps (optional)
What to do:
Once you have the Android SDK, decompress the folder sdk/platform-tools in a place of your choice.
Inside this folder, put gpt.bin, the custom recovery image and the ROM and GApps zip's.
Start your phone on fastboot. Connect it.
Inside your decompressed platform-tools folder, hold shift and right click inside the folder. Select "Open command window here".
Make sure your phone is properly connected by typing "fastboot devices" (without the quotation marks). The command prompt should show your phone serial number.
Now we start the real deal. Fist of all, flash gpt.bin using this command:
fastboot flash partition gpt.bin
Make sure it ends on "OKAY"
Now, flash the recovery
fastboot flash recovery nameoftherecoveryfile.img
Once this is done, enter recovery using the fastboot menu on your phone (use Vol- to highlight "Recovery", and then press Vol+)
Now your phone should boot on recovery mode. If you recieve an error like "Can't mount /system/", don't worry, this is normal (there's no system partiton yet, after all). Now you can use ADB command with your PC. Once again, to be sure everything is connected properly,tyipe on the console:
adb devices
Once that is done, it's time to give your phone the custom ROM, so you can flash it. Type (or copy/paste)
adb push NameoftheROMfile.zip /sdcard/ NameoftheROMfile.zip
If you have GApps, do the same for those
adb push GApps.zip /sdcard/ GApps.zip
Now you can finally disconnect your phone from the PC! You are almost done, select "Install" in your recovery, and flash your ROM zip, then the GApps if you have them.
Once it's done, you can reboot to system.
And you will have a working Moto G again!!
Enjoy it, and don't brick it again

the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file

maurocds said:
the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file
Click to expand...
Click to collapse
From my experience, you don't have to enter sideload mode in recovery to push a file, sideload mode is for pushing OTAs. And remember, the ADB push command requires you to put the exact name of the file to transfer twice, that could have failed for you.
You can't use fastboot devices on recovery because you can only use ADB commands in recovery, you were supposed to use "adb devices".

Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.

masa86 said:
Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.
Click to expand...
Click to collapse
Not many people do NAND backups these days.
Sad, because they're really useful, and there wouldn't be as many "HALP BRICKED PHONE" threads.

It Doesn't work only say failed xD

Fresroqir said:
It Doesn't work only say failed xD
Click to expand...
Click to collapse
Care to explain what failed?

tatazeuz said:
Care to explain what failed?
Click to expand...
Click to collapse
The install for the custom rom and gapps

Fresroqir said:
The install for the custom rom and gapps
Click to expand...
Click to collapse
What error did you receive? Did you flashed gpt.bin correctly?

tatazeuz said:
What error did you receive? Did you flashed gpt.bin correctly?
Click to expand...
Click to collapse
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)

Fresroqir said:
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)
Click to expand...
Click to collapse
got.bin is the partition table of the Moto G. Its the file that indicates to the phone the size, name and number of partitions it should have.
So, I know TWRP said in red letters Failed, but I'm interested what is the specific error, what did it said on the command prompt of TWRP.

Error flashing zip sdcard pa falconzip
and then there comes this updating partitution details and do i need to put the rom twice in the cmd?

and do i need a cutom rom with 4.4.4????????

yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading

Fresroqir said:
and do i need a cutom rom with 4.4.4????????
Click to expand...
Click to collapse
maurocds said:
yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading
Click to expand...
Click to collapse
I used the latest version of PA + Stock GApps

Thanks!
Edit: Nope... Still same problem. Looks like the gpt file flashed but everything else is the same.

It still doesn't work for me i got th whole time failed and i don't know what i need to do ;(
It says: Z:\New folder\Android>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.025s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.372s]
finished. total time: 0.399s
is that good?
EDIT:it looks that sideload works and not that push command
EDIT: nvm i am stuck at bootanimation
EDIT: this wont work it says failed all the time at twrp

I'm kind of confused. Why couldn't people downgrade and go back to stock by reflashing all of the files from an older stock image, including the motoboot and gpt? I would think this would work...although with people saying that they are unable to downgrade I'm not willing to try upgrading to 4.4.4 myself.
What errors are people seeing if they try to flash gpt and motoboot from, say, 4.4.2 stock or 4.4.2 GPE?
-- Nathan

not work for me..
every recovery stay on black screen and return vibration on touch screen
:/
help > http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228

i think this fix doesn't work because i can only sideload my roms and gapps xD

[Q] OnePlus One - Unable to unlock bootloader again after relocking

Hi Guys,
Hope to get some help here.
So i unlocked the bootloader of my one plus one and installed supersu + Twrp recovery. All worked fine until i decided to relock the bootloader.
I've put the device into fastboot mode and executed "fastboot oem lock" with twrp recovery still in there.
Now i am trying to unlock the bootloader again using "fastboot oem unlock" to be able to flash the stock recovery and having issues.
output of commands:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>
After this it boots straight to twrp recovery. I then hit reboot system and go back to fastboot mode and run the below:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (12260 KB)...
OKAY [ 0.389s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.404s
Anyone has an idea how i can unlock the bootloader again ?
Thanks
Vik

Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out

I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.

lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
Thanks i'll give that a try as soon as am home..

YrrchSebor said:
Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out
Click to expand...
Click to collapse
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks

Vikmeister said:
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks
Click to expand...
Click to collapse
Be careful if you updated your phone to XNPH30O OTA,
!!! Warning !!!
In the NEW OTA CM11S XNPH30O, the bootloader (aboot) img size changed....
We request all not to apply the unlocker scripts on the new bootloader , until we confirm/find the new bit position.
It might brick your phone and corrupt bootloader...
Click to expand...
Click to collapse
It won't work.. do not try it if you updated to XNPH30O using the OTA.

zephiK said:
Be careful if you updated your phone to XNPH30O OTA,
It won't work.. do not try it if you updated to XNPH30O using the OTA.
Click to expand...
Click to collapse
Thanks for letting me know ZephiK i haven't updated to that version yet. I still have XNPH25R. I should all good.

Fantastic.. Thanks a lot guys.. That worked like a treat.. Bootloader is now unlocked.
:laugh::good:

lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
I ran this command:
Code:
fastboot.exe boot TWRP-2.7.1.0.img
But the next step does not work:
Code:
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or from sdcard...
I got:
downloading 'boot.img'...
OKAY [ 0.484s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.487s

That's because you can't boot a recovery with the recent bootloader unless you're unlocked.
Transmitted via Bacon

Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo

Im have the same issue but I have no recovery installed..Anyway to do this

i have same issue plz give me any solution if you found any???plz let me know plzzzzz
​
piriri007 said:
Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo
Click to expand...
Click to collapse
plz help same issue

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

how to flash magisk patched boot.img?

boys please can u write me steps to flash patched boot. img with fastboot? thank you (european model)

Transfer the patched boot image to PC using 'adb pull' from the path showen in Magisk, boot phone into download mode and flash the patched boot image. 'fastboot flash boot patched_boot.img'

flas patched boot image
Slok 00 said:
boys please can u write me steps to flash patched boot. img with fastboot? thank you (european model)
Click to expand...
Click to collapse
If you flash Magisk from your sd-card, the boot.img is automatically patched by magisk.
Root HTC U11+ European model software number 1.10.401.23
To root your HTC U11+ thru twrp use version 3.2.0.0
1. make sure you got Magisk-15.2 on you sd-card
2. boot into TWRP and leave system read only
3.goto install and install Magisk (in my case 15.2) boot.img is automatically patched
4. you will get error, like "can't mount data" (not to worry)
5. after install GO BACK!! DO NOT REBOOT!!
6. format data AND THEN reboot!!
7 You'll have to setup your phone as a new one; finish that and install Magisk_Manager
8 your now rooted!!! check with root checker
Hope this will help you;
Click to expand...
Click to collapse

milesd said:
Transfer the patched boot image to PC using 'adb pull' from the path showen in Magisk, boot phone into download mode and flash the patched boot image. 'fastboot flash boot patched_boot.img'
Click to expand...
Click to collapse
I have unlocked my U11+ via htcdev.com
I have extracted the boot.img from my RUU
I have installed MagiskManager and patched boot.img
I am having problems flashing the patched_boot.img file ..
I boot to download mode and fastboot flash fails .. see below..
Code:
fastboot flash boot patched_boot.img
target reported max download size of 2399200000 bytes
sending 'boot' (37409 KB)...
FAILED (data write failure (Too many links))
finished. total time: 1.006s
E:\Temp
Can anyone help please!!
I am presently on 2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_HTC_India_SEA_1.24.400.2_Radio_8998-002772-1712011153_release_519104_signed_2_4

I boot to download mode and fastboot flash fails .. see below..
Code:
fastboot flash boot patched_boot.img
target reported max download size of 2399200000 bytes
sending 'boot' (37409 KB)...
FAILED (data write failure (Too many links))
finished. total time: 1.006s
E:\Temp
Can anyone help please!!
Click to expand...
Click to collapse
Try to get a newer htc-fastboot

milesd said:
Try to get a newer htc-fastboot
Click to expand...
Click to collapse
I have tried the fastboot bundled with HTC Sync Manager v3.1.88.3 as well as using the fastboot from platform-tools-v27.0.1-windows but no joy
AFIK there are the latest of the HTC one and the SDK one.
Should also point out I cannot flash the twrp recovery image either.. same error
---------- Post added at 10:56 PM ---------- Previous post was at 10:11 PM ----------
Another thing to mention is that I can erase the partitions without problem using fastboot erase but cannot flash any partitions. The only way I can restore the partitions is to reflash the RUU by putting the RUU zip o the SD card.
I wonder if there is an issue having the 128G sd card in the phone. Will try again tomorrow without the SD card inserted.
The CID's are HTC__060.

You are enable oem unlock in developer option?
Test the connectivity using the following command (provided your phone screen is unlocked)
adb devices
--------------------------------------------------------------------------------------------------------------------------
I think you must rename file patch_boot.img to boot.img
cmd: fastboot flash boot boot.img

newyesor said:
You are enable oem unlock in developer option?
Test the connectivity using the following command (provided your phone screen is unlocked)
adb devices
--------------------------------------------------------------------------------------------------------------------------
I think you must rename file patch_boot.img to boot.img
cmd: fastboot flash boot boot.img
Click to expand...
Click to collapse
I am not new to unlocking and rooting HTC phones I have been doing this since the beginning .. I had an original O2 XDA phone
The phone bootloader is unlocked 100% did it via htcdev and the bootloader screen on both phones says unlocked. There is no issue with connectivity either, adb devices shows the connected phone and other adb commands work fine .. as I said I can even fastboot erase partitions, but am unable to flash them...
I am now thinking it might be my drivers as I am using the windows drivers that came with the latest HTC Sync manager. Later today or tomorrow I might try uninstalling them and using the Universal Naked or the Universal ADB drivers..

Sidewindr said:
I am not new to unlocking and rooting HTC phones I have been doing this since the beginning .. I had an original O2 XDA phone
The phone bootloader is unlocked 100% did it via htcdev and the bootloader screen on both phones says unlocked. There is no issue with connectivity either, adb devices shows the connected phone and other adb commands work fine .. as I said I can even fastboot erase partitions, but am unable to flash them...
I am now thinking it might be my drivers as I am using the windows drivers that came with the latest HTC Sync manager. Later today or tomorrow I might try uninstalling them and using the Universal Naked or the Universal ADB drivers..
Click to expand...
Click to collapse
Have you tried flashing with
fastboot flash boot YOUR_DIRECTORY / patched_boot.img
Just an idea....

Yes tried absolute and relative paths.
Sent from my HTC One M8 using Tapatalk

Switch to another usb port and/or try with another usb cable
https://plus.google.com/+ArtemRussakovskii/posts/RwJ28EdYgCb
https://www.youtube.com/watch?v=5Omhpv7oYdc

Problem solved ... Tried it again after reboot and on a different USB port and it worked .. odd ..

Patched

milesd said:
Transfer the patched boot image to PC using 'adb pull' from the path showen in Magisk, boot phone into download mode and flash the patched boot image. 'fastboot flash boot patched_boot.img'
Click to expand...
Click to collapse
HI I would just like to clarify before I try the download mode.
I have been trying to patch the magisk patched_boot.img in bootloader mode on a HTC U11 with no joy.
This is the error I receive
PS E:\HTC\ADB tools with latest twrp.img Use this one 2019\platform-tools> fastboot flash boot magisk_patched.img
target reported max download size of 536870912 bytes
sending 'boot' (37589 KB)...
OKAY [ 0.915s]
writing 'boot'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 0.924s
Is it safe to patch in the download mode as stated?
Thanks