Develop Bugs

[TUTORIAL] How to S-OFF your HTC Desire

Hi there !
Many people here want to be S-OFF on their HTC Desire but don't know how to be, this thread is for you !
Credits goes to all AlphaRev developpers.
What is S-OFF ?
(Quotes from original AlphaRev website)
HTC implemented security on their newer generation phones. This flag, called @secuflag, controls whether your phone has
it's NAND or flash unlocked. Most noticeably, S-ON (security on) will read-lock your /system and /recovery partition, to name a few. Also, secuflag controls whether zip files being flashed through recovery or fastboot, are signed by HTC.
The now notorious S-OFF (security off) will disable this NAND security.
Since we are unable to access the Radio NVRAM itself (where secuflag is stored), we turned our attention to HBOOT.
Click to expand...
Click to collapse
For more informations about AlphaRev S-OFF, read the OFFICIAL Thread HERE.
There is many solutions to install S-OFF, this tutorial will show you few methods.
TRY AT YOUR OWN RISK ! I'am not responsible of bricked phone, for more help try the OFFICIAL Thread.
PREREQUISITES :
a ROOTed HTC Desire ROM with debugging option enabled on it.
a computer running Windows XP/Vista/Seven (32 or 64 bits), Linux, or Emulation via WMware etc.
a computer which can boot USB devices (for USB method only)
a branded USB Key 32Mb or more (for USB method) or a CD to burn (for CD method).
EASIEST method so far seems to be now by "Revolutionary" method.
Please check this out before trying solutions below (they are manual and maybe outdated, because I don't have the time keep updated this topic, moreover I don't own anymore a HTC Desire).
STEP-BY-STEP GUIDES :
.: USB METHOD :.
Be sure to Nandroid backup your device from recovery (just in case).
Download the latest Universal USB Installer or UnetBootin.
Download ISO Reflash Utility from AlphaRev website.
Install the software of your choice.
Open it, and select your USB device and your AlphaRev ISO freshly downloaded.
Create your bootable USB key.
Reboot your computer and boot on the USB key you freshly created.
Press any key to accept the disclamer.
Once you are in your ROM, plug your Desire with the USB cable on your computer.
/!\ DON'T TOUCH ANYTHING TILL YOU GET THE FINISH MESSAGE AT STEP 3 /!\
(Some users reports it can take over 1 hour. Passed this time, pull out the battery and reboot your phone).
The USB key method worked 100% for me, I personally installed my S-OFF exactly like that on my Desire.
.: CD METHOD :. (by jshields)
Clic HERE
.: VirtualBox METHOD :. (by Stewge)
Clic HERE
.: VMWare METHOD :. (by -V-O-Y-A-G-E-R-)
Clic HERE
Congratulations ! you are done !
Note : If for some unknown reasons you cannot access your Recovery anymore, it's normal, you must flash your Recovery using "fastboot" (SDK Android Kit must be installed on your running computer).
You have the choice between flashing a custom recovery like ClockWork one or put the original one but I sugger you the custom one which gives you much many more features
How to flash your recovery using ClockWork's image :
Download Clockworkmod 2.5.0.7 recovery image from official AlphaRev thread for bravo.
Move the file into "C:\android-sdk-windows\tools" (default sdk android folder's installation).
Verify MD5 checksum of the image with a freeware like HashCalc or something (IMPORTANT !).
Go to the main menu of your AlphaRev HBOOT (turn on your device with return button pressed).
Go to "FASTBOOT" mode.
Go to your computer and open a new terminal (Administrator privileges required if Windows Vista or 7).
Enter exactly this (without ") : "fastboot flash recovery recovery-clockwork-2.5.0.7-bravo.img".
Now you will have a ClockWork Recovery image installed and working
Note 2 : If your device freeze on boot logo, apply your Nandroid backup that your did before S-OFF.. that should do the trick.
If one day you want to S-ON your phone again, just reflash an original RUU rom !
Need supports ? all kind of questions must be posted on this thread directly. Be sure to read the whole thread (or at least 5 latest pages) before asking any question.
If you enjoy this guide, don't forget to rate it
{
"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"
}
stars, and clicking the
button (right below) is always appreciated to keep this thread maintained
LIKE MY WORK ?
OFFER ME A
!​​

Thank you so much, been waiting for this, will try it out later

nice tut but you can avoid installing anything, You can just use UnetBootin

Or CD version
1.download Alpha Rev.iso
2.burn .iso image to CD using a iso burning software eg. Power ISO
3.boot from CD eg. Hold F12 at boot
4.press the Legendary enter
TIPS connect USB when the CD has booted
Any problems just pm me
Sent from my HTC Desire s-off

Beaverman20 said:
nice tut but you can avoid installing anything, You can just use UnetBootin
Click to expand...
Click to collapse
It's nearly the same, you don't have to install universal usb installer, however, it is Windows-only.
Sent from my HTC Desire using XDA App

Really good work... a simple and clear guide

jshields said:
Or CD version
1.download Alpha Rev.iso
2.burn .iso image to CD using a iso burning software eg. Power ISO
3.boot from CD eg. Hold F12 at boot
4.press the Legendary enter
TIPS connect USB when the CD has booted
Any problems just pm me
Sent from my HTC Desire s-off
Click to expand...
Click to collapse
Yeah, I found it much easier to just burn to a rewrittable CD. F8 on bootup to load up my boot menu, then I selected my CD Rom.

nice tut, simple and very clearly...
oh don't forget to put in the first post for ppl who gets stuck at stage 3 (it happen to me) just to wait for about 30 minutes or more (don't know exactly how long, just for safety), and then pull out the battery and reboot the phone...
many ppl report it work....
Sent from my HTC Desire using Tapatalk

I think I'm done with the flashing of the hboot from alpharev
But now my phone keeps rebooting to the fastboot screen.
I've tried removing the battery and rebooting again, reboot from fastboot, reboot from clockwork recovery... but i still cant boot up my rom.......
Anyone can shed me a light on what went wrong?

All options to apply S-off should be included, this is a 'how to', and this is not THE only way to do it, personally I found virtual box the easiest method for me. I just think that some other options should be made clear to people, maybe people that have used a different method could add their own ' how to' to this thread?
Great idea though to help people.
sent from my HTC Desire, powered by a SuperVillain using XDA App.

Sorry to noob it up here but what are the benefits of S-OFF. im guessing it means security. does this enable us to hack the kernal? as a user who doesnt do programming but likes to mod my phone alot what could i gain out of this?
thankyou in advance

Yeah sorry for newbies here but what is the benefits of this s-off?

eozen81 said:
Yeah sorry for newbies here but what is the benefits of this s-off?
Click to expand...
Click to collapse
Maybe its a good thing to sum up the benefits on the first page, to stop these kind of questions and making it a 500 page topic where you cant find answers...
I know if you read the forum, or use google you can find all the info
Info from the http://alpharev.shadowchild.nl/ site
HTC implemented security on their newer generation phones. This flag, called @secuflag, controls whether your phone has
it's NAND or flash unlocked. Most noticeably, S-ON (security on) will read-lock your /system and /recovery partition, to name a few. Also, secuflag controls whether zip files being flashed through recovery or fastboot, are signed by HTC.
The now notorious S-OFF (security off) will disable this NAND security.

I gonna change a bit the tutorial, and add the other solutions. Will do a link directly of posters with the solution he use, will be easier for me

AndroidGX said:
I gonna change a bit the tutorial, and add the other solutions. Will do a link directly of posters with the solution he use, will be easier for me
Click to expand...
Click to collapse
allrighty then

Ok, many changes on the tutorial, hope you like it
Tried to do as clear as possible, and add some features.
If any method to add please PM me, I will add it with your name directly from your post here.
Thanks!

AndroidGX said:
Ok, many changes on the tutorial, hope you like it
Tried to do as clear as possible, and add some features.
If any method to add please PM me, I will add it with your name directly from your post here.
Thanks!
Click to expand...
Click to collapse
looks great !

I have now read all the information i can find about S-OFF - Only advantage i can find is that you can change bootscreen.. What are the options if i choose to make S-OFF on my phone - What else can i change ? My phone is rooted, and i have flashed roms and kernels with S-ON - So you guys really need to show more advantages to this than what has already been written..

Nobody is trying to sell you anything. Why don't you GTFO?

ionhide said:
I have now read all the information i can find about S-OFF - Only advantage i can find is that you can change bootscreen.. What are the options if i choose to make S-OFF on my phone - What else can i change ? My phone is rooted, and i have flashed roms and kernels with S-ON - So you guys really need to show more advantages to this than what has already been written..
Click to expand...
Click to collapse
You post in the wrong thread, go say that in the original S-OFF thread (gave in first post).
Here is just a help for people who want to install S-OFF feature on their Desire. Nothing else.

[Tutorial] Unlock Bootloader Issue?

Hi XDA
You said:
I Wish to unlock my Bootloader so I can Flash new ROM's like Cyanogenmod etc.
Click to expand...
Click to collapse
My Phone is a HTC Wildfire S A510e (PG76100) Marvel
S-ON
Hboot version - 1.02.0000
Radio - 7.53.39.03M
I Live in South Africa
I'm running Stock(Updated) Android 2.3.5 and HTC Sense 2.1.
As far as I know this Phone is not locked to my Carrier (MTN)
------------------------------------------------
I have been helped by a forum member to validate my token. Thanks __DS__!
------------------------------------------------
Here's a Little Guide to help you unlock your HTC Wildfire S's Bootloader.
THIS WILL NOT S-OFF YOUR PHONE, it will however enable you to use non HTC roms and recovery systems!
The first step is to go to HTC Developer Portal, click on Unlock Bootloader icon.
Now click on Get Started tab that appears after clicking on Unlock Bootloader icon.
Now we recommend that you read through all the content on this page and understand that you are virtually voiding your device’s warranty after getting the bootloader unlocked. (EDIT: Update Your Bootloader by Following this link: Here, It's a relatively straight forward process.)
After you have read through the message from HTC, verify your HTC Wildfire S model. You can verify the model and FOTA by going to Menu > Settings > About Phone.
Once you are confirmed that you have the same device with exactly the same FOTA(EDIT: This step is useless If you followed step 3!). click on Begin Unlock Bootloader on HTC Dev Portal.
In case you aren’t already registered on the HTC Dev Portal, then register and fill the details.
After this you will be given some legal documentation, accept them to proceed.
On the next page, follow the instructions as given in steps.
Remove and reinsert your phone’s battery.
After this, press Volume Down Button and Power Button on your phone together to boot into bootloader mode.
Once you are in the bootloader mode, use Volume button to select Fastboot option and then press power button.
Now connect your phone to the computer via USB Cable that comes with the phone to avoid any unforeseen disruptions.
After you are done, click on the green tab that says “Proceed to Step 5”.
On the resulting page, you will see a Required Resources section on the right column. Download Google Android SDK, Java Runtime Environment and HTC Sync from the links provided.
Install Java RT Environment first followed HTC Sync. You will need HTC Sync only if you are attempting this method on Windows.
Now run SDK Manager.exe
Once SDK Manager is up and running, reject everything else and only install Android SDK Platform tools (Latest Revision).
Once the installation is complete, go to C:\Android-SDK-Windows\Platform-Tools and copy ADB.exe plus ADBWinAPI.dll files and paste them in C:\Android. You will need to make a new folder named Android in C drive.
After this go to C:\Android-SDK-Windows\Patform-tools and copy Fastboot.exe to C:\Android.
Once you are done with all this, open command prompt. Go to Run and type CMD for command prompt.
Also press Proceed to Step 8 On the HTC Dev portal.
In command prompt, type
Code:
cd C:\Android
Press enter
Now Type
Code:
fastboot oem get_identifier_token
Press enter.
As a result, you will get a whole block of text that you need to copy from Identifier Token Start to Identifier Token End. Please make sure to not to copy Bootloader prefixes following each line in the text block.(HINT: Right click, select all, then just select the identifier token from Identifier Token Start to Identifier Token End)
Now scroll down and you will see My Device Identifier Token on HTC Developer portal page.
Paste the text block your copied in My Device Identifier Token Field available.
Now press Submit.
Now you will be on a Process Unlock Key page.
You will recieve an E-Mail from HTC dev with a file named Unlock_code.bin attached. Copy that file to C:\Android. (where we put the Fastboot.exe etc.)
Go back to your CMD window and type in
Code:
fastboot flash unlocktoken Unlock_code.bin
Hit enter.
{
"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"
}
Look over to your phone!
Click to expand...
Click to collapse
Please hit the Thanks button if this helped!
You Again said:
I had a problem acquiring the Identification token.
I would get this error in the command line:
Code:
C:\Android)fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.017s]
finished. total time: 0.017s
Click to expand...
Click to collapse
This problem is caused by the outdated HBoot.
But I managed to upgrade it to 1.08.0099 by downloading this package: Here.
At the top of the 1.08.0099 HBoot there is a Pink bar [*** Locked (OOW) ***]
That's the only HBoot version that seems to support the get_identifier_token command. If you don't have the pink bar, the bootloader unlocker will not work!
Took me forever to find so please thank me If you use it!

You cannot bypass this step because a code is generated out of your device on the website.
does not look like an HTCDEV error. just check if your browser accepts cookies. delete all cookies from htcdev and try to login again

Thanks for your reply.
I tried it on my M$ Internet Explorer X86 and X64, no luck. I Cleared the cookies in my Firefox 9.01, No luck there either. I recieved a strange error in the error console though
Code:
Error: WebDestroyerChrome.BrowserOverlay is undefined
Source File: chrome://webdes/content/wdPageListener.js
Line: 74
Error: WebDestroyerChrome.BrowserOverlay is undefined
Source File: chrome://webdes/content/wdPageListener.js
Line: 69
Did you by any chance use use Google Chrome when you were going through this bootloader unlocking process? If not, please tell me which Internet browser you were using.

No, I used Firefox. So if the problem persists between browsers it should not be a cokkie issue. can you try from a different pc?

I will Give it a shot tomorrow morning from another PC and update with the results, Thanks For your Time!

Still No luck, even on a different system, I created another account on the Dev site with United Kingdom/Ireland set as my location (Perviously defined as "Other").
Same problem.
I'm starting to think It might just be my ISP. Does the webportal still work for you guys?

try it in another browser, chrome or IE.

sourabh1510 said:
try it in another browser, chrome or IE.
Click to expand...
Click to collapse
Downloading Chrome now, Will update ASAP.
Edit: No Luck with chrome. :/

You can ask someone trustable to send/receive unlock code for you
If not found anyone in vicinty - post to my PM.

__DS__ said:
If not found anyone in vicinty - post to my PM.
Click to expand...
Click to collapse
Thanks, PM Sent

100% Unlocked, downloading a ROM and CWM Recovery Right now, Big thanks to __DS__!

Hey all,
I've hit a brick wall whilst trying to unlock a friends Bootloader, I do everything in the exact way I'm supposed to but after entering my token, i get the following error message:
Error Code: 173
Error Reason: Check Rule Fail with exception
What does this mean and is there any way of resolving this?
Thanks In Advance,
Beans

error 155
bootloader unlock 100%.....HELP,ERROR 155
---------- Post added at 12:17 PM ---------- Previous post was at 11:37 AM ----------
Error 155 when flashing RUU file

HTC EU HBOOT 1.09.0099 for RUU 2.13.401.3
Here is the link to the new HTC Wildfire S (EU) HBoot necessary if this problem happens to you with RUU 2.13.401.3:
http ://goo.gl/vXEnk (remove space from URL)
(click thanks if it helps)

[Share] Verizon XT610 unbrick. (For Code Corrupt)

[UPDATED 19MAR2012 GMT+8 20:00]
Unbrick Tutorial on Linux Environment
1. Boot your PC into Knoppix Linux with the CD you burnt.
{
"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"
}
http://i224.photobucket.com/albums/dd144/wilson_temp/2012-03-19_19-24-25_140.jpg
(Let it boot, it can be some 5 minutes. Not yet. No need to click anything yet)
2. Browse to the folder where you saved the SBF_FLASH by windows.
Copy the location address. You need it for Terminal below
http://i224.photobucket.com/albums/dd144/wilson_temp/2012-03-19_19-26-09_656.jpg
3. Execute Terminal here
http://i224.photobucket.com/albums/dd144/wilson_temp/2012-03-19_19-26-49_633.jpg
http://i224.photobucket.com/albums/dd144/wilson_temp/2012-03-19_19-24-39_544.jpg
4. Run commands like this.
You will see exactly how this look like. I can only lead you to "Waiting your phone"
I cant afford to flash my phone again. LOL
http://i224.photobucket.com/albums/dd144/wilson_temp/2012-03-19_19-28-23_878.jpg
-----[Stop here for the hour, I will tell you guys how to apply update.zip after a break]-----
[Background and Scenario]
*For who with Code Corrupt. / Bootloader stuck / M logo stuck
Dear all, lately I got my XT610 bricked.
Reason:
Originally I was on 4.6.8 (newest rom). I was then doing the worst thing on earth,
I SBF-ed the whole thing with a 2.26 sbf with RSD-Lite (as how we flash sbf as usual)
Night mare:
1. PC: RSD of every version would not recognise my phone. Driver of every version neither work.
Linux: some people may have heard of sbf_flash under linux. Flashing was ok under linux. Hoever the phone just still wont boot.
2. My phone starts with Bootloader code corruption. Nothing works, RSD wont work. As mentioned, I tried with Linux sbf_flash command (google around what is sbf_flash, plenty of tutorial/explanation around)=], the flashing process was fine but the phone just stuck in M logo for minutes, then bootloader appears again with error code. "ERR :00 1d 00 00 xx" (something like this)
No matter how much times I tried to sbf_flash back the 4.6.8 sbf file, no luck. I was around the edge of collasp and ready to go psycho. I have been double-wiping data and cache for thousands of times....
[What makes it working again?]
I was wondering, as long as Stock recovery is still working (Pressing R+M key), I was going to try out the last "meaningless thing".
I copied the update.zip (the file used to update from 3.87 to 4.6.8 with SD card), I installed this file again by recovery (install update.zip something like this)
In theory, this file should only deal with system part, not the booting part. However I was thinking, bootload is locked, there should be no problem with it.
Recovery works, seems the rom is intact.
M logo changes from white to Red after sbf_flash, means booting was partially done. Only problem left should be the OS. (think in PC way, Bios is intact, Windows is dead)
I was holding my breath, watching the update.zip going. When it comes to update BP complete, I was almost sure the thingie's gonna work again, since RSD showed "Flash BP fail" before, and likely being recovered by this update. Some lines after, there was an error from reading. I ignored it, double-wiped again and restart.
I left my phone on the desk for some seconds. Suddenly, the most unpleasant scream on earth "DROOOOID~" suddenly yells in the air. The most unpleasant scream suddenly becomes the most joyful yell on earth!
[Happy-ending, hurray]
The remaining would be the same as you did before.
Root, install apps, enjoy.
[Conclusion]
1. Linux-environment, sbf_flash the 4.6.8 sbf which you used for RSD/SDL in Windows. (for those commands , try googling. If You still have no idea, drop me a line, I will post that up)
2. Bootlap after Linux flash, , got ERR code in Bootloader after M logo. dont worry.
3. Hold R+M+Power, reboot into recovery.
Do a double wipe.
4. copy update.zip to SD card, install the update.zip.
once the process pass through Update BP complete, ignore any error code there after.
5. Double Wipe again, reboot
6. "DROOOOID~", Root, and have you facebook on!.
*Drop me a line if you got any questions. Though I have no technical background, nor knowledge in programming. Trying and sharing is what we do.
#Only tested on Verizon Droid Pro. Euro/ARG Droid Pro please proceed to the other threads.
*Sorry for the bad English, I am not native speaker.

i tried to flash my motorola droid pro version to Android 2.3.6 ---- Blur_Version.0.22.2.XT610.Personal.en.AR and now the mobile stuck a code corrept. can i use RSD Lite with the back files mentioined up to go back to the original mobile software and how
i have windows 7
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
i tried to flash my motorola droid pro version to Android 2.3.6 ---- Blur_Version.0.22.2.XT610.Personal.en.AR and now the mobile stuck a code corrept. i have windows 7

aymanfoa said:
i tried to flash my motorola droid pro version to Android 2.3.6 ---- Blur_Version.0.22.2.XT610.Personal.en.AR and now the mobile stuck a code corrept. can i use RSD Lite with the back files mentioined up to go back to the original mobile software and how
i have windows 7
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
i tried to flash my motorola droid pro version to Android 2.3.6 ---- Blur_Version.0.22.2.XT610.Personal.en.AR and now the mobile stuck a code corrept. i have windows 7
Click to expand...
Click to collapse
Some ppl said yes, some ppl said not. Im not sure for RSD, since its kinda crap sometimes, as it often fail to detect your phone.
Cant detect = cant flash your phone.
[Mine Suggestion]
1. Download "Knoppix", a Linux build boot on CD (No installation needed) and runs on ram
2. Open terminal, use SBF_FLASH to flash the stock verizon SBF back to the phone. (I dont have the command with me now in office. I upload them once back in home.
3. Connect USB. (No detection needed. 100% successful)
4. You will see the red M logo boot back. (But some chances for stuck there and ERR code afterwards)
5. Apply update.zip as abovesaid (If needed, I will upload that too tonite)
6. Double Wipe. and There you go.
*Should work anyway, even if you have flashed the sbf from any martian devices (joke) beforehand.
Since Bootloader is locked, Moto should be unbrickable. Your stock Verizon sbf will recover anything at long as you still see Bootloader (Code corrupt counts)

how to do please step one and two above:
1. Download "Knoppix", a Linux build boot on CD (No installation needed) and runs on ram
2. Open terminal, use SBF_FLASH to flash the stock verizon SBF back to the phone. (I dont have the command with me now in office. I upload them once back in home.

aymanfoa said:
how to do please step one and two above:
1. Download "Knoppix", a Linux build boot on CD (No installation needed) and runs on ram
2. Open terminal, use SBF_FLASH to flash the stock verizon SBF back to the phone. (I dont have the command with me now in office. I upload them once back in home.
Click to expand...
Click to collapse
1. Google for "Knoppix", you should get an ISO image around 700mb. (No specific version needed. Any)
Burn this to a blank CD/DVD, let it handful on your desk first. You will use this CD to boot your PC into Linux environment when every tool is ready.
*Relax, this would only run on RAM and CD, nothing will be installed on your PC. Your Windows and everything gonna be fine.
2A. Download SBF_FLASH from this post:
http://forum.xda-developers.com/showthread.php?t=775913
-extract the Zip, make it convenient, store it in your C:\SBF
When you later boot into linux on your PC with the abovesaid Knoppix CD,
you gonna execute a program built-in Linux, that is the Terminal. (something look like DOS)
2B. Have your 4.6.8 SBF file ready in the abovesaid C:\SBF folder of PC.(you can get it in an other thread in this Droip Pro forum)
- rename the SBF file to a short name for convenience, say 468.sbf from now on in this post.
-
2C. Execute the Terminal program in Linux.
-execute the following commands. One line means one single command. Dont miss out spacebars or "DOTS"
- command lines below, when ever you see <<< ENTER#xxxxxx, that means press enter and behind these are descriptions for your reference, DONT COPY
---------------Command starts below. dont copy this line-------------
su
cd sda1\SBF <<<ENTER #Or the location where you stored SBF folder in C. (sda* means Disk number in Linux, there is nothing known as C:\ D:\)
chmod +x sbf_flash <<< ENTER # dont miss out the spacebars, dont miss out underscroll
./sbf_flash 468.sbf <<<ENTER #dont miss out the . at the beginning.
---------------Command Stops here. dont copy this line--------------
2D. Connect your phone to usb and your phone(At Code Corrupt screen), let it run.
*Sorry for the bad English, I am not native.
Tonite I will try to upload screenshots for illustration if possible.

aymanfoa said:
how to do please step one and two above:
1. Download "Knoppix", a Linux build boot on CD (No installation needed) and runs on ram
2. Open terminal, use SBF_FLASH to flash the stock verizon SBF back to the phone. (I dont have the command with me now in office. I upload them once back in home.
Click to expand...
Click to collapse
Instructions with screenshot updated in #1 post.

i try but it is not working it is keep showing reborting

aymanfoa said:
i try but it is not working it is keep showing reborting
Click to expand...
Click to collapse
Would you capture the screen /take a picture of both the PC and your phone?
Let me study it

picture of pc and mbile is here
http://i1066.photobucket.com/albums/u416/aymanfoa/pc.jpg
http://i1066.photobucket.com/albums/u416/aymanfoa/mobile1.jpg

aymanfoa said:
picture of pc and mbile is here
http://i1066.photobucket.com/albums/u416/aymanfoa/pc.jpg
http://i1066.photobucket.com/albums/u416/aymanfoa/mobile1.jpg
Click to expand...
Click to collapse
1. Saying reboot is normal. PC part is done.
2.download this file(update.zip)
ht#tp://ww#w.badongo.#com/file/26628385
(Remove hash)
Put it on SD
3. Press R+M+Power to boot the phone into Recovery, when seeing Android+Triangle screen, press Vol Up+Down together.
4a. Wipe Data+Cache
4b. Update with ZIP, select update.zip
5 when done, double wipe again.
restart.
This shuold be the last ressort, good luck

when i Press R+M+Power to boot the phone into Recovery, the phone not accepting to boot into recovery and give the message shown in the picture below.
http://i1066.photobucket.com/albums/u416/aymanfoa/mobile1.jpg
---------- Post added at 10:44 AM ---------- Previous post was at 10:43 AM ----------
when i Press R+M+Power to boot the phone into Recovery, the phone not accepting to boot into recovery and give the message shown in the picture below. my mobile is from usa version.
http://i1066.photobucket.com/albums/...oa/mobile1.jpg

I have never tacked with this ERR code,
But I did some research online, this code should be solved by SBF reflash
Try to reflash sbfs of every versions starting from 2.26 / 3.87 till 4.68.
*Make sure that u remove your battery, press hold R+M and insert battery then with Power (Three buttons) until M logo is gone.
As long as I saw your bootloader is still 03.A0,
Bootloader should be intact from the wrong version rom flashed, since South American/European Bootloader is not 3.A while 3.A is Verizon phone.
Keep on trying, dont be so pissed (pad), I had been trying with mine code corrupted phone for four days day to night until it works again. Your phone is just Undead Zombie LOL

please note i have motorola droid pro version and i have i tried to flash my motorola droid pro version to european flash Android 2.3.6 ---- Blur_Version.0.22.2.XT610.Personal.en.AR and now the mobile stuck a code corrept. i cant back to the original mobile software unless i have flash for usa with same version flash for 2.3.6. usa flash version now only 2.2.3.
---------- Post added at 06:18 PM ---------- Previous post was at 06:18 PM ----------
i need flash for usa mobile with version 2.3.6.sbf

aymanfoa said:
please note i have motorola droid pro version and i have i tried to flash my motorola droid pro version to european flash Android 2.3.6 ---- Blur_Version.0.22.2.XT610.Personal.en.AR and now the mobile stuck a code corrept. i cant back to the original mobile software unless i have flash for usa with same version flash for 2.3.6. usa flash version now only 2.2.3.
---------- Post added at 06:18 PM ---------- Previous post was at 06:18 PM ----------
i need flash for usa mobile with version 2.3.6.sbf
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1558183
Seems Linux Reflash european version would bring your phone back to live , only u cant root.

nothing will work unless we have flash for usa version mobile 2.3.6

aymanfoa said:
nothing will work unless we have flash for usa version mobile 2.3.6
Click to expand...
Click to collapse
Not likely then. I suspect the recent 4.7.3 is the last "mercy" from Moto for our oldie.
It would be too great if ICS comes, but I dont think it is possible.

In my european pro I've done (with 2.26.20 sbf) (I've locked with 2.3.3 locked sbf...)
Only In a terminal emulator i've added sudo " sudo ./sbf_flash ***.sbf" ...
Thank you

i try every thing nothing will work unless we have flash for usa version mobile 2.3.6

2.download this file(update.zip)
ht#tp://ww#w.badongo.#com/file/26628385
(Remove hash)
Put it on SD
Click to expand...
Click to collapse
Any chance anybody still has a copy of this update file?

V500 im not able to get into bootloader

Hi,
I just want to unlock bootloader on my g pad and flash custom rom. I did this many times on Nexus devices, also sony.
I installed sdk, next Google drivers and my tablet is detected by computer as adb interface.
But when I type command - adb reboot bootlader
Tablet just reboots. I'm not able to get into fastboot. Plz help. It's v500 version. My software version is v50020d.
Earlier I didn't know that LG locks bootloader and I tried many times to flash custom recovery. One time I had made a mistake and using flashify - I flashed twrp for v510. But LG support tool helped me to repair it. Probably it flashed stock with full wipe becsuse I lost data so everything should be fine now but as You can see - it isn't...
HTC One M8

Also command adb reboot oem-unlock only reboots it
HTC One M8

The v500 has a locked bootloader. You need to root first and then install a older aboot and recovery in order to flash roms. This device like the g2 uses loki to bypass the lg lock.

Ok. I've already rooted my device but every time I try to flash twrp using "loki" method I end with screen like this...
{
"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"
}
HTC One M8

WKD622 said:
Ok. I've already rooted my device but every time I try to flash twrp using "loki" method I end with screen like this...
HTC One M8
Click to expand...
Click to collapse
Okay, so that message providing you wait a bit and see twrp start, means that you have successfully bypassed the locked bootloader...
If it freezes there and nothing happens that would be something different... The second sentence reads differently if Loki has bypassed things. The screen above seems to indicate that Loki is not successfully bypassing (hence my edits to this post) it should say something different in the second line if Loki is successful. My tablet is at home right now so I can't take a picture of a working Loki bypass...
A successful bypass should say something like: Device unlock so boot success!

After this screen twrp turns on.
Edit
Okey... Maybe I've done something wrong. Could you tell me how to flash this recovery in points?
I'm not very familiar with LG...
HTC One M8

WKD622 said:
Twrp turns on.
HTC One M8
Click to expand...
Click to collapse
Excellent, then you have successfully installed twrp and you can get into twrp recovery. Next do a backup to an sdcard (if you have one), download a rom to that card and install it...
---
Does TWRP start can you get into it?

muiriddin said:
Excellent, then you have successfully installed twrp and you can get into twrp recovery. Next do a backup to an sdcard (if you have one), download a rom to that card and install it...
Click to expand...
Click to collapse
I had also done this and flash cm but nothing changed.
Maybe this screen was a result of flashing twrp using flashify.
Yesterday I flashed stock so now I want to begin this process one more time . Could You tell me how to do it?
HTC One M8

----
Yes. But now it come to my mind that this problem with booting was a result of twrp for v510 flashed using flashify and next Loki method. Because maybe at the end twrp was for v500 and it worked but I wasn't able to flash anything because it "thought" that I'm using v510. But next i delete line in updater-script connected with authorization and as a result I flashed cm for my v500 but this boot screen didn't changed.
So as you know next thing I've done was flashing stock and now I want to start from beginnig without problems .
Could you tell me how? :/
HTC One M8

WKD622 said:
Yesterday I flashed stock so now I want to begin this process one more time . Could You tell me how to do it?
HTC One M8
Click to expand...
Click to collapse
Okay, my process from a fresh install of 4.4.2 is:
make sure to download everything you need before you start this process and read through it carefully...
1. Root device using stumproot, thread located here:
http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
Other root approaches potentially will work as well, I use stump since it also works on my phone...
2. Download and use step 3 from idioterror's thread here:
http://forum.xda-developers.com/showthread.php?t=2698267
You will need to modify his batch file to properly work the details for that are in the thread, the download by itself will not work without changing a line in the batch file (if I recall from memory find the query for 50010b and change it to 50010d.)
If that worked the batch file ends with an attempt to reboot into recovery. Unplug the cable after the batch file sends the reboot command so the adb reboot recovery command can properly complete and get you into recovery...
if the tablet boots back into stock try another adb reboot recovery manually(or use flashify to reboot into recovery), again unplug once the reboot starts.
If that does not get you into TWRP but instead gets you into stock recovery you need to do the steps in idioterror's batch file manually go here for details:
http://forum.xda-developers.com/showpost.php?p=56707177&postcount=15
(be really careful with the dd comands if you do this a mistype with them will be very dangerous)).
Once you have this working recovery you need to decide which base you are going to use with your tablet, the 4.2.2. base (for AOSP based roms) or the 4.4.2 base (for recent stock based roms). The recoveries for the 4.2.2. and 4.4.2 are different see the details in this thread:
http://forum.xda-developers.com/showthread.php?t=2551499
You can run AOSP based roms on the 4.4.2 firmware but you will typically need to flash a 4.4.2 replacement kernel like redkernel or mani... See the proper threads in the development section...
If you are going to run AOSP based roms with the standard kernel skip to 3b...
3a. I am running a 4.4.2 firmware base and a redkernel on lollipop myself, make sure to install the latest 2.8.0 recovery for the 4.4.2 firmware base... You can now flash stock based roms, or AOSP roms with a 4.4.2 capable kernel do not do step 3b for stock based roms...
3b. Install the 4.2.2. base (will actually install a different recovery partition and aboot partition, however it will get your firmware back to 4.2.2. which is what almost all of the AOSP roms expect...) thread and download details here:
http://forum.xda-developers.com/showthread.php?t=2719411
That download is huge and takes a while to flash, don't panic, but make sure that the MD5's match since a failed flash for that one can brick the tablet...
4. Enjoy your rooted and rommable tablet!

muiriddin said:
You will need to modify his batch file to properly work the details for that are in the thread, the download by itself will not work without changing a line in the batch file (if I recall from memory find the query for 50010b and change it to 50010d.)
If that worked the batch file ends with an attempt to reboot into recovery. Unplug the cable after the batch file sends the reboot command so the adb reboot recovery command can properly complete and get you into recovery...
if the tablet boots back into stock try another adb reboot recovery manually(or use flashify to reboot into recovery), again unplug once the reboot starts.
If that does not get you into TWRP this step failed and youwill have to manually walk through what the batch file does... Stop and ask me or someone else for further assistance (or open up idioterror's batch file and figure out what it does so you can do it manually (be really careful with the dd comands if you do this a mistype with them will be very dangerous)).
Click to expand...
Click to collapse
You need to know that yesterday back to stock was my second one. 1st time few days ago I edited script as You wrote here form v50020b to d and it didn't boot to recovery. The same result was when it comes to booting to recovery using app like flashify.
So unfortunately I need to do it with the hardest way . I will try. It will be very nice experience.
I belong to crx team as a (very) novice member so I hope Cr3pt will help me looking at instruction You wrote for me if something goes wrong.
Thanks a lot. Probably everything will be okey but there is an option that I will be back here with more questions. :E
Thanks a lot.
HTC One M8

Does it boot into the stock recovery instead with two really strange errors?
WKD622 said:
You need to know that yesterday back to stock was my second one. 1st time few days ago I edited script as You wrote here form v50020b to d and it didn't boot to recovery. The same result was when it comes to booting to recovery using app like flashify.
So unfortunately I need to do it with the hardest way . I will try. It will be very nice experience.
I belong to crx team as a (very) novice member so I hope Cr3pt will help me looking at instruction You wrote for me if something goes wrong.
Thanks a lot. Probably everything will be okey but there is an option that I will come with more questions.
Thanks a lot.
HTC One M8
Click to expand...
Click to collapse

HTC One M8

WKD622 said:
HTC One M8
Click to expand...
Click to collapse
Yeah, idioterror's script is failing, when I had that happen I had to manually do what was in the batch file via an adb shell. I can't write those instructions until later tonight (assuming my little girl sleeps tonight that is)...
Something has changed which causes his script to fail that I haven't tracked down yet (there is a thread on this somewhere in the LG GPAD forums)... It is either the newest LG drivers, or a newer adb.exe install or something that is conflicting with idioterror's script... his approach still works, you just have to manually do it...
One additional thing, when I manually did it, I had already installed busybox so I did not use his tools (dd etc) I used the ones that I had already installed (I use the BusyBox Pro from Stericson in the play store for this, his free version should also work).

Step by Step Aboot/Recovery when the script fails
WARNING: I'm trying to help, I assume that you know how to recover from mistakes by reverting to stock with LG's software if needed. This is the procedure I followed by manually doing what Id10tError had in his batch file... If anything fails below I messed up in translating the instructions. I did not run the dd commands on my tablet to check since I have already done this process. Please be careful... If you find errors I will try and help... the dd command does have the ability to completely destroy your tablet if you use it incorrectly... if you have questions or see a difference between my instructions and the batch file ask and I'll be glad to answer questions. This was translated from idioterror's script, any errors are mine not his.
I assume that you have installed busybox, (this gives you a working dd on the device)
you have rooted your tablet
and you have adb working on your computer.
You could potentially also do this from the tablet itself if you copy the files needed to the proper locations (skip the push part below) and use a terminal directly. I also assume that you have downloaded idioterror's aboot replacement stuff from my earlier instructions. On the computer go to the directory that you opened the zip file and do a directory listing you should see:
the dd lines below may wrap depending upon how you are displaying this...
The directory should contain:
11/12/2014 09:59 PM <DIR> .
11/12/2014 09:59 PM <DIR> ..
05/16/2014 08:48 PM 524,288 aboot.img
05/16/2014 08:48 PM 815,104 adb.exe
05/16/2014 08:48 PM 96,256 AdbWinApi.dll
05/16/2014 08:48 PM 60,928 AdbWinUsbApi.dll
05/16/2014 08:48 PM <DIR> busybox
05/16/2014 08:48 PM 11,001,856 recovery.lok
07/07/2014 04:41 PM 4,156 runme.bat
then type
adb shell
su
mkdir /sdcard/flash_tmp/
exit
exit
adb push ./aboot.img /sdcard/flash_tmp/aboot.img
adb push ./recovery.lok /sdcard/flash_tmp/recovery.lok
adb shell
su
chmod -R 777 /sdcard/flash_tmp
dd if=/sdcard/flash_tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/flash_tmp/recovery.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
rm -rf /sdcard/flash_tmp/
exit
exit
adb reboot recovery
unplug the cable once it starts rebooting and enter TWRP recovery...
It will be dim if you are coming from the 4.4.2 base, go to a dark room if needed so you can see it and flash a newer 4.4.2 recovery next if you are planning on using stock roms, or flash the 4.2.2. base otherwise... see my earlier post for a link to the recovery thread or the 4.2.2 base.

Thanks!
Everything works perfect
HTC One M8

Step 3 of idioterror's thread doesn't work.
You said:
2. Download and use step 3 from idioterror's thread here:
http://forum.xda-developers.com/showthread.php?t=2698267
However, I am unable to download the file from the link.
Do you know of another location where the file can be downloaded?
Thanks in advance!
Morty.

[Q&A] New Storage Layout for HOX Endeavoru

Q&A for New Storage Layout for HOX Endeavoru
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for New Storage Layout for HOX Endeavoru. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

this is great. so we don't need move to sd card app? ill make review as soon as i getting this done

donkey09 said:
this is great. so we don't need move to sd card app? ill make review as soon as i getting this done
Click to expand...
Click to collapse
Correct. No need to move apps.

Thanks teemo ... works like a charm

So New Layout needs a special rom? right? are there any ways get CM11/12 compatible with this layout? or how/where to get ROMS compatible with New Layout? if /sdcard becomes /data where is /sdcard?

maniel said:
So New Layout needs a special rom? right? are there any ways get CM11/12 compatible with this layout? or how/where to get ROMS compatible with New Layout? if /sdcard becomes /data where is /sdcard?
Click to expand...
Click to collapse
No more sd card

maniel said:
So New Layout needs a special rom? right? are there any ways get CM11/12 compatible with this layout? or how/where to get ROMS compatible with New Layout? if /sdcard becomes /data where is /sdcard?
Click to expand...
Click to collapse
As Thant say, the SD Card as we know it is gone. It has changed from FAT to ext4, which mean that you can not use USB Mass Storage to copy files. It is done only with MTP now.
Yes it need special made ROMs. I list all compatible ROMs on this page.
There will also be some FAQ in post #2 of the same page.
I am currently running CM12 20150208 on the New Layout. No problems till now. Not available yet.

I have a problem, after installing twrp2843-Big phone does not want to boot into recovery. I unplug the phone from the PC, boot into bootloader, push recovery and nothing happens, the phone just restarts again in the bootloader. What could be the problem? Thx.

wramp said:
I have a problem, after installing twrp2843-Big phone does not want to boot into recovery. I unplug the phone from the PC, boot into bootloader, push recovery and nothing happens, the phone just restarts again in the bootloader. What could be the problem? Thx.
Click to expand...
Click to collapse
Flash it again with fastboot and make sure there is no errors after flashing:
Code:
C:\>fastboot flash recovery twrp2843-BiG.img

teemo said:
Flash it again with fastboot and make sure there is no errors after flashing:
Code:
C:\>fastboot flash recovery twrp2843-BiG.img
Click to expand...
Click to collapse
flashing it twice, without errors. always trying twrp2810-HOX - same here.
flashing CWM, CWM loaded but now can not connect as a removable drive
I was able to restore the android through sideload from cwm. Now everything works. But still can not get to go to the new layout.
Everything Everywhere says okay, but the result is zero. And by the way I have not mounted as a USB flash drive from the CWM 6.0.4.7 and 6.0.4.8
Some information:
HTC One X 16Gb
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.72.0000
RADIO-5.1204.167.31
cid: HTC__A07
UPD: just redownload recovery from another PC, flashed and it WORKS....seems it's probably my fault antivirus, it is not fully allowed to download recovery//

wramp said:
flashing it twice, without errors. always trying twrp2810-HOX - same here.
flashing CWM, CWM loaded but now can not connect as a removable drive
I was able to restore the android through sideload from cwm. Now everything works. But still can not get to go to the new layout.
Everything Everywhere says okay, but the result is zero. And by the way I have not mounted as a USB flash drive from the CWM 6.0.4.7 and 6.0.4.8
Some information:
HTC One X 16Gb
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.72.0000
RADIO-5.1204.167.31
cid: HTC__A07
UPD: just redownload recovery from another PC, flashed and it WORKS....seems it's probably my fault antivirus, it is not fully allowed to download recovery//
Click to expand...
Click to collapse
What happens now, does it boot to the recovery?
If not, maybe you have a bad download?

teemo said:
What happens now, does it boot to the recovery?
If not, maybe you have a bad download?
Click to expand...
Click to collapse
The problem was my antivirus which blocked the download recovery. Now everything works perfectly, thank you!

I format data, reboot to recovery and connect device to PC. On the PC does not appear any drives, in Device Manager has a unknown device "One", as I understand it on the PC driver is not installed, where to get them? twrp 2.8.1.0 with the old layout worked fine and twrp2811.BiG worked fine too...
{
"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"
}

I am not at my windows PC right now, but you can try this (you may have to pick a different driver though):
Small guide for solving problem with usb not working in Windows.
Aat work, my Windows7 like to change settings as it think is best for me. I guess it just don't know me well enough. Here is what I do when Windows get confused and forget what I want.
First make sure you have the latest drivers from Google and HTC.
Install latest drivers from HTC for your PC. http://www.htc.com
Next, get your adb/fastboot drivers updated.
Locate "android.bat", mine is in C:\Android\android-sdk\tools, but yours will be wherever you initially installed your adb drivers.
Run the file and install any suggested updates.
Windows device manager (run devmgmt.msc from start menu or a command window).
Connect your phone and check where it get attached. For a working connection, it should say "Android USB Devices" -> "My HTC", but since you read this, chances are, that your device is in "Other Devices" -> "Android Phone".
That is what this guide will correct.
1. Wrong driver - double click "Android Phone"
2. Update Driver
3. Browse (for your HTC driver, which is already installed)
4. Pick the driver yourself
5. Select "Android USB Devices" -> Next
6. Select "My HTC" -> Next
7. Choose Yes - You know you want the HTC driver
8. Ahhh, success - test your adb/fastboot/MTP/UMS
9. Here is what happened. We make Windows choose the correct driver and Windows will place it under Android USB Devices.
Let me know if it works or not.

Unable to copy the rom from my pc
Hi!
I installed the rom of the 2nd February and everything worked well for me! no problem and I was very happy of that! but the lack of storage bothered me a lot and I tried the new layout with twrp recovery. I flashed the recovery and then when I want to copy the rom and the gapps on my one x , IMPOSSIBLE!!!
When the phone is connected there is just a repetitive sound of disconnection usb storage! I don't know what to do

Patinho888 said:
Hi!
I installed the rom of the 2nd February and everything worked well for me! no problem and I was very happy of that! but the lack of storage bothered me a lot and I tried the new layout with twrp recovery. I flashed the recovery and then when I want to copy the rom and the gapps on my one x , IMPOSSIBLE!!!
When the phone is connected there is just a repetitive sound of disconnection usb storage! I don't know what to do
Click to expand...
Click to collapse
Hi. Sorry it did not turn out well for you. But hang on, it will.
First, it is not enough to flash the recovery. You also need to prepare the memory for the new layout. This is all described in this guide: http://shares.teemo.dk/s#d676c36c-e...rive.teemo.dk/Switch to SuperSized Layout.pdf
Try to follow it and see if that helps. Just remember that it will delete everything on the sdcard. Copy your data to PC first

teemo said:
I am not at my windows PC right now, but you can try this (you may have to pick a different driver though):
Small guide for solving problem with usb not working in Windows.
Aat work, my Windows7 like to change settings as it think is best for me. I guess it just don't know me well enough. Here is what I do when Windows get confused and forget what I want.
First make sure you have the latest drivers from Google and HTC.
Install latest drivers from HTC for your PC. http://www.htc.com
Next, get your adb/fastboot drivers updated.
Locate "android.bat", mine is in C:\Android\android-sdk\tools, but yours will be wherever you initially installed your adb drivers.
Run the file and install any suggested updates.
Windows device manager (run devmgmt.msc from start menu or a command window).
Connect your phone and check where it get attached. For a working connection, it should say "Android USB Devices" -> "My HTC", but since you read this, chances are, that your device is in "Other Devices" -> "Android Phone".
That is what this guide will correct.
1. Wrong driver - double click "Android Phone"
2. Update Driver
3. Browse (for your HTC driver, which is already installed)
4. Pick the driver yourself
5. Select "Android USB Devices" -> Next
6. Select "My HTC" -> Next
7. Choose Yes - You know you want the HTC driver
8. Ahhh, success - test your adb/fastboot/MTP/UMS
9. Here is what happened. We make Windows choose the correct driver and Windows will place it under Android USB Devices.
Let me know if it works or not.
Click to expand...
Click to collapse
it does not work. in the Device Manager now 2 "My HTC", and in my computer there is nothing
and I am not alone, some of my friends have a same problem

teemo said:
Hi. Sorry it did not turn out well for you. But hang on, it will.
First, it is not enough to flash the recovery. You also need to prepare the memory for the new layout. This is all described in this guide:
Try to follow it and see if that helps. Just remember that it will delete everything on the sdcard. Copy your data to PC first
Click to expand...
Click to collapse
thanks! it was a problem of drivers! everything works fine now! thanks a lot! :good:
---------- Post added at 11:42 AM ---------- Previous post was at 11:36 AM ----------
Hi!it's me again ! Thanks again for your help but i want to know if we can't use the 2GB extra data space. i have the 16GB version and the layout shows me 10GB. is that space useless?

Patinho888 said:
thanks! it was a problem of drivers! everything works fine now! thanks a lot! :good:
---------- Post added at 11:42 AM ---------- Previous post was at 11:36 AM ----------
Hi!it's me again ! Thanks again for your help but i want to know if we can't use the 2GB extra data space. i have the 16GB version and the layout shows me 10GB. is that space useless?
Click to expand...
Click to collapse
At the moment, you can use it only if you have given the apps root access. Developer options - Root access:adb+apps. Then you can access it from a root filemanager.
The recovery can use it to store anything you like. I use it for different ROMs. Your PC can (currently) only access it via TWRP.
And as Thömy suggest in his document, you can keep your old data (from old layout) on it. Then, if you want to go back to the old layout, you can use the data directly (xtradata is the old data).

@popcee.p
look in cm12 thread