Credits go to @nlooooo for starting this thread!
WARNING
I’m not responsible for bricked devices, all you do is on your own responsibility. Most of the processes I’ll mention will work with some vital parts of your phone, so if you don’t have enough courage or until you don’t understand all the things you should do I recommend not to get involved with this.
Click to expand...
Click to collapse
Ok, there's a tool for almost all of that. Tool is updated, but you need to be sure to click the button for the right recovery, explanation below.
1. UNLOCKING OF BOOTLOADER
Everything starts with this. Unlocking of bootloader will allow you to make changes to some critical partitions of your phone (boot, system and recovery) and will allow you to flash custom recovery that can be used for installing of custom roms, mods and all kind of flashable zips. However, it won't s-off your phone, and other critical partitions (bootloader, radio) remain inaccessible.
So, I won't explain how to do that. Why? Because if you successfully unlock bootloader on your phone it means that you received enough knowledge for the rest of the process and you're qualified to go further.
This process will factory reset your phone (erase data partition) so backup your stuff before you proceed.
Ok, now go to htcdev.com, register your account, go to unlock bootloader section, for the device choose 'All other supported models' and follow the instructions carefully everything is explained in details. Pay attention to 'Required resources' on the first page after confirmation - you need Android SDK platform tools Java Runtime Environment and HTC Sync installed and there are all needed links. Files mentioned in step 5 you will find in Android Bundle zip you downloaded in folder adt-bundle-windows-x86_64\sdk\platform tools.
Here are some useful links about Android SDK platform tools, you won’t be needing most of it but it won't be bad to read.
http://developer.android.com/tools/help/adb.html
http://android-dls.com/wiki/index.php?title=ADB
http://android-dls.com/wiki/index.php?title=Fastboot
http://wiki.cyanogenmod.org/wiki/fastboot
Remark: once unlocked bootloader can be relocked but can never be locked again. This can be done issuing command from fastboot:
fastboot oem lockThis means that on the top of you bootloader screen you’ll have a sign RELOCKED instead of LOCKED, which is a notice to HTC that you unlocked it once. Plus they have data about all users that requested unlock_code so they can deny your warranty whenever they want.
If you’ve successfully unlocked your phone bootloader we can proceed to the next step.
Click to expand...
Click to collapse
2. CUSTOM RECOVERY INSTALLING
- Go to this address:
http://forum.xda-developers.com/showthread.php?t=2502327There you can find custom recoveries for DesX. Some of them have a few bugs but they are generally functional. Download one of your choice, rename it to recovery.img and put it on the root of c: drive on your PC. Before downloading, read the thread linked to carefully, as it is important to check your hboot before installing a custom recovery.
Remark: you can use recovery image provided in WindyCityRockr's tool.
- Go here:
http://download.chainfire.eu/370/SuperSUdownload SuperSU, connect your phone to PC and put it somewhere on your phone sd card.
- Do not disconnect your phone from PC, reboot phone to fastboot on one of this ways :
1. choose restart from power menu and when the screen comes off wait for the buttons to turn off and immediately push volume down, the phone will boot to bootloader, then select fastboot from bootloader menu
2. issuing command
adb reboot-bootloaderfrom command prompt that will take you directly to fastboot
- once you’re in fastboot mode open command prompt, lead it to folder where you installed adb and fastboot (remark: unlocking bootloader guide pointed you to make a folder c:\Android for this) and issue commands
fastboot flash recovery c:\recovery.img
fastboot reboot-bootloader
fastboot erase cache
The second and third commands are not quite necessary but they don’t harm and leave your phone with no trails of previous recoveries. Now you can disconnect your phone from your PC.
Click to expand...
Click to collapse
3. BACKING UP STOCK ROM
Now it is really important to backup your stock ROM. Dependent on your CID and hboot version, you can't use RUU to get back to stock, especially if your phone is branded by your carrier. Also, RUUs are only available for ICS bootloader (hboot 1.24 and lower). For JB there are only nand backups for a few CIDs uploaded by some nice xda members. So if you definitely want to be able to get back to stock any time, you'll have to backup your current configuration first. That's done by:
Reboot your phone to recovery
Backup -> Select all partitions -> Swipe to BackupThat will take some time. After that's finished, you should make a copy of that backup somewhere safe (it's located on the sdcard in folder TWRP, just copy the whole folder somewhere).
Click to expand...
Click to collapse
4. ROOTING YOUR PHONE
- From fastboot menu choose bootloader and then recovery to reboot phone to recovery
- If you successfully boot to recovery choose options:
Install zip from sd card
Choose zip from sd cardNavigate to UPDATE-SuperSU-vx.xx.zip you stored on sd card and choose it. Once the installation is finished reboot your phone. Now you should see SuperSU app in app drawer and your phone is rooted.
Click to expand...
Click to collapse
5. CUSTOM ROMS INSTALLING
There are already quite a few ROMs available for our device. But watch out... many of them are discontinued, mostly the CM ROMs as well as the ROMs based off CM. Go here for the index:
http://forum.xda-developers.com/showthread.php?p=35735267#post35735267That’s the Index thread I created for all user to track development for our device. There you’ll find roms that can be installed.
I have to emphasize that every chef gives an instruction how to install his rom, so here I’ll just give you the basics for custom rom installing using custom recovery.
- Download the rom of your choice and put it on the sd card of your device
- Unpack boot.img from rom.zip and put it on the root of c: drive on your PC
- Reboot phone to recovery
- Choose option ‘wipe data/factory reset’
- Choose option ‘wipe cache partition’
- Choose option ‘advanced’ and in next menu choose ‘wipe dalvik cache’
- Go back to main menu and choose ‘install zip from sd card’ and then ‘choose zip from sd card’
- Navigate recovery to rom zip you put on sd card and choose it
- Wait until the installation is finished
- Reboot your phone to fastboot and connect it to your PC
- Open command prompt, lead it to folder where you installed adb and fastboot (remark: unlocking bootloader guide pointed you to make a folder c:\Android for this) and issue commands
fastboot flash boot c:\boot.img
fastboot reboot-bootloader
fastboot erase cache- Reboot your phone
The last few steps are needed since there is no way to s-off our device, so boot.img included in rom.zip has to be flashed separately via fastboot.
Remark: don’t ever forget for the golden rule of flashing ‘Always make a nand backup before you flash something'.
Click to expand...
Click to collapse
6. S-OFF
As S-OFF makes your device vibrating 7 tmes on each boot, you should really think about if you need it. If you are not sure about it, then it's not for you. If you still want to do it, go here:
http://forum.xda-developers.com/showthread.php?t=2630531
http://forum.xda-developers.com/showthread.php?t=2667156Use the first link to get to the files needed to do your S-OFF. In the second link you'll find the things you can do after the S-OFF procedure including downgrading the hboot in order to install RUUs etc.
Click to expand...
Click to collapse
Ok, I did what I had promised, all suggestions and corrections are more than welcome.
All this came as 2 years experience with HTC phones (had Desire and Incredible S before), unlocking, rooting and taking their guts out .
Sources and links posted:
- HTC Developers site
- WinDroid HTC Desire X Toolkit v2.1 made by WindyCityRockr
- Android Developers site
- Cyanogen Wiki site
- SuperSU made by Chainfire
- Thanks to ckpv5 for nand ICS backup thread
- Thanks to Izzy Stinson for pointing me to things not explained enough
- Sources for recoveries can be found in my recovery thread
- Thanks to GtrCraft for the idea to include the backup of stockrom
- Thanks to nightwalkerkg and the rumrunners team for getting us the S-OFF
- Again thanks to ckpv5 for the S-OFF tutorial
Going back to stock for official update
Now to say more about a reverse part. The point of this is to make your phone available for official updates, and make it possible to do. Thanks to Ranalakshay36 and Bedroom we have information that you can apply OTA without need to relock bootloader on the phone. However, relocking is still mandatory if you want to install a fresh new rom using RUU.
The first important thing for this is: PEOPLE, MAKE A NAND BACKUP OF STOCK ROM BEFORE REMOVING OF ANY APP FROM SYSTEM OR INSTALLING A CUSTOM ROM!!! This will make this process much easier to do.
RECEIVING AND OFFICIAL UPDATES INSTALLING
Part one:
Ok, you just unlocked bootloader and rooted your phone (no custom rom installed), but you received a notification that you have an official update available and you want to install it. No problem at all if you didn't touch the apps on system partition (some of them are necessary for official support), and all you have to do are these 2 things:
1. Reinstall stock recovery - I attached it. Remember the part about custom recovery? The process for this is the same:
- download recovery I attached, rename it to recovery.img and put it on the root of c: drive on your PC
- reboot phone to fastboot
- connect it to a PC
- open command prompt and guide it to the folder where you have adb platform tools installed
- issue commands
fastboot flash recovery c:\recovery.img
fastboot reboot-bootloader
fastboot erase cache
Now your phone should be ready to apply official update.
Click to expand...
Click to collapse
Part two:
1. You installed a custom rom, however you made a nand backup of your intact stock rooted, so all you need is to restore your nand backup and go to "Part one", that will do a thing.
2. You installed a custom rom, however you didn't make a nand backup of your intact stock rooted, or you deleted some important files from system partiton. So, you're almost scre**d. I said almost because you can ask some of your geeky friends to borrow you his nand backup that you can use for restore.
The best option is to revert back to stock using RUU, but that's currently limited only for devices with Europe based firmware. Here is the thread I made where you can find info about 1.18.401.1 RUU and CID compatibility and a way to check CID of your phone to make sure you can use it:
Get CID and RUU 1.18.401.1 Compatibility
RUU Download page
To run RUU you need to relock your bootloader. This is how you can do it:
- reboot phone to fastboot
- connect it to a PC
- open command prompt and guide it to the folder where you have adb platform tools installed
- issue command
fastboot oem lock- the phone should restart automatically and you'll have a sign RELOCKED on the top of bootloader screen.
After you successfully relock bootloader you can run RUU directly from fastboot. With earlier HTC models there was I a way to bypass CID checking and use any RUU to revert back to stock using a GoldCard, but someone told me that it's not possible with Desire X.
Remark: once you relock bootloader it can be unlocked again in the same way you did it for the first time, and, of course, it will factory reset you phone. Also, going in this order is mandatory, cause if you relock bootloader before you flash stock recovery, you won't be able to do that with relocked bootloader
Click to expand...
Click to collapse
If you can't run a RUU because of incompatible CID, you have to have a nand backup ready for restoring or else to find one in the forums. Here is a thread with different nand backups incompatible from the RUUs:
ICS nandroid backups
Follow the instructions in the above thread to restore your backup.
Click to expand...
Click to collapse
Credits:
- Cobje - stock recovery img from latest update (1.18.xx)
http://forum.xda-developers.com/showpost.php?p=35031493&postcount=25
- Ranalakshay36 and Bedroom for the intel.
Reserved once more...
Nice on nlo, will hopefully stop alot of the questions
Good job writing this tutorial!
One small remark: unlocking bootloader via htcdev will hard-reset the device so all data on the phone will be lost. Might be useful to mention this so users can back-up as much as possible on an un-rooted device.
nightcrow said:
Good job writing this tutorial!
One small remark: unlocking bootloader via htcdev will hard-reset the device so all data on the phone will be lost. Might be useful to mention this so users can back-up as much as possible on an un-rooted device.
Click to expand...
Click to collapse
Thanks, forgot about that while I was writing all this stuff.
I can imagine it's quite a story
Anyway well done and it will definitely be useful to the ones that are about to dive into the rabbit-hole.
thanks for the tutorial! very easy to understand and very simple. :good::good::good:
thanks for the tutorial! nice Job men.:good:
a very well written master piece tutorial. absolutely easy use of english as well without most technical jargon. keep up the good work.
here after m gonna redirect such noob questions to this page.
ayyu3m said:
a very well written master piece tutorial. absolutely easy use of english as well without most technical jargon. keep up the good work.
here after m gonna redirect such noob questions to this page.
Click to expand...
Click to collapse
When an English gentleman says that's an easy use of English I somehow get delighted...
Updated, added flashing boot.img via fastboot for custom roms installing.
thx man, its very helpful for noobs like me who cant follow every thread
there is one more thing i need you help to do it .. how to install busybox ?
I tried all the market apps but i keep getting they same problem "failed to install, try other version or different location"
AxR979 said:
thx man, its very helpful for noobs like me who cant follow every thread
there is one more thing i need you help to do it .. how to install busybox ?
I tried all the market apps but i keep getting they same problem "failed to install, try other version or different location"
Click to expand...
Click to collapse
Try here, here you can find it as a flashable zip.
http://forum.xda-developers.com/showthread.php?t=1929852
nlooooo said:
Try here, here you can find it as a flashable zip.
http://forum.xda-developers.com/showthread.php?t=1929852
Click to expand...
Click to collapse
it worked !! thx
any idea how to keep the changed font after restarting ? it appears the system revert any change i do
I have one question, after I done process 1 and 2, can I factory reset again from the settings without losing root and still keep bootloader unlocked?
Sent from my HTC Desire X using xda app-developers app
Izzy Stinson said:
I have one question, after I done process 1 and 2, can I factory reset again from the settings without losing root and still keep bootloader unlocked?
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
Of course you can, factory reset deletes only data partition while all others stay intact, and Superuser app is located on system partition, while bootloader can't be accessed from there, only from fastboot.
nlooooo said:
Of course you can, factory reset deletes only data partition while all others stay intact, and Superuser app is located on system partition, while bootloader can't be accessed from there, only from fastboot.
Click to expand...
Click to collapse
thanks. and one last question. you gave 3 links to download for cwm recovery. which of those three are the best cwm for you?
For me the best is 4ext, but it's not released yet for our device.
I would go with Claudyy's version.since it doesn't have a screen shift bug.
nlooooo said:
For me the best is 4ext, but it's not released yet for our device.
I would go with Claudyy's version.since it doesn't have a screen shift bug.
Click to expand...
Click to collapse
so i guess im gonna download clauddy cwm then.
so it is CWM-protou.img, i should rename it to recovery.img right?
sorry for asking so many questions, i dont like to make mistakes when doing this kind of things.. :silly:
Related
Preamble
This is the S-OFF upgrade from GingerBread to HoneyComb
Do not perform this procedure if you have the official HTC hboot, it will not work. You must have a revolutionary hboot (see prerequisites).
***If you performed this procedure with previously and have hboot version 6.14.5555 please update to the new hboot, 6.14.5555 is no longer supported***
Upgrade instructions at the bottom of the procedures.
Prerequisites
You must have performed Revolutionary S-OFF
If running on windows you will need these fastboot drivers
If running the procedure on Linux or MacOS you must have fastboot working.
There are no other software prerequisites for this procedure, it does not matter what ROM/Kernel or recovery you are using.
Don't bother asking for help if you try to do this on a virtual machine, you won't get any.
Run on a real machine.
Windows Instructions
Download this file MD5=c62cc1d0453799a7277abfea444d20e4
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the RUU_Express_B02 directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Alternative Installation Instruction (Any OS)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the RUU_Express_B02_RAW.zip file PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Do not mirror files from this post.
No discussion of Honeycomb content or changes or the relative merits of Gingerbread and Honeycomb. This thread is for the procedure and support thereof only! Also please don't quote the first post because your post becomes an automatic TLDR.
Update Instructions
Use these instructions if you currently have hboot 6.14.5555 - Your data should be preserved but take a backup first just in case.
Method 1
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Copy the file to the root of your external SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
Method 2
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip PG41IMG.zip
[I][COLOR="Red"]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/COLOR][/I]
fastboot reboot
[Revision History]
B02 - updated full version: hboot 6.14.5556
New bootloader to patch bugs with fastboot flashing
- Fastboot flashing splash1 fixed
- Fastboot flashing hboot fixed
Patch for upgrading from a previous version added.
B01 - Initial full version: hboot 6.14.5555
BETA- Developer preview
Special thanks: contradude for the early and riskiest testing, and Maine_Coon for all the ongoing testing
Downgrade to Gingerbread
Preamble
This is the S-OFF downgrade from HoneyComb to S-OFF GingerBread if you are not S-OFF and have a HTC (not revolutionary) hboot then do not do this it will not work.
The full versions of these files will give you a fully functional Gingerbread installation with S-OFF, CWM recovery and boot image with the secure flag turned off.
Windows Instructions
Download this file MD5=f5afc4b457a17f88cc611b40e6c7cdc8
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the Express_Downgrade directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Alternative Installation Instruction (Any OS)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the file downloaded in step1 to PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Do not mirror files from this post.
wow you are really fast, excellent men.
One for me please
reserved 2
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
vancraft said:
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
Click to expand...
Click to collapse
This is an attempt to make downgrading easier for us.
spartan1987 said:
This is an attempt to make downgrading easier for us.
Click to expand...
Click to collapse
Right. That's the "recovery" part.
But its also described as "root, and all". I'm wondering if this allows the installer to root the OTA Honeycomb? Or will more work be required before the install can be further changed (i.e. s-off, eventually upgraded to ICS, etc.)?
It works
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
risb577 said:
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
Click to expand...
Click to collapse
so, does that mean you could, in theory, flash a custom HC rom once we get one?
Throw up some screenshots or a video would you?
edit: oh and test rom manager and titanium backup if you don't mind.
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
stuck on soft brick..
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Maine_Coon said:
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
Click to expand...
Click to collapse
No, as it says in the OP, You MUST be s-off and THEN run an RUU. Accept all updates to include the HC update and the view will be soft bricked. THEN use fastboot to push the mini ruu.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
myowin said:
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Click to expand...
Click to collapse
If it says it's an unrecognized command, then either you do not have fastboot installed, or you haven't gone into environment variables (assuming it's a windows box) and added those commands to the path. try that first (google is your friend and you can google in XDA). Good luck.
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
thank you so much for quick respond..
I think I found it here how to do that.. (for someone like me... )
http://forum.xda-developers.com/showthread.php?t=532719
root
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
I haven't done this yet, but I'm dling the RUU right now to do it and help people troubleshoot.
To answer your question, if you hold down the power button long enough, the view will power off, then you can hold power + vol down to get back into the bootloader and select fastboot mode, then open cmd, type fastboot devices and check to make sure yours shows up, then proceed with pushing the mini-ruu. If I'm wrong guys, correct me. Hope it works out for you.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
Im not sure if this matters, but when I was in soft brick, I rebooted a few times and could not get into the bootloader. It just seemed to ignore the vol down keypress. I then unplugged the usb, powered off from soft brick, and held the vol. down button down even before I hit the power button as I was turning it on. Once I was in bootloader, I just plugged the usb back in.
EDIT: More tips:
1.After I flashed the initial stock ruu, and before I accepted any updates, I turned off fastboot in the power options and enabled usb debugging.
2. I did this from a Windows 7 laptop. When I initially tried to perform the softbrick steps, I got an access denied error message. The files were sent ok, but errored on saving. I closed the command prompt, and re-lauched the command prompt as administrator. The commands sent successfully.
3. Also, once you send the mini ruu over, the Tablet sat in the the oem loader with a 70% full progress bar after I successfully sent the mini ruu. I waited about 10 minutes because I was unsure how to proceed. I finally issued:
fastboot reboot-bootloader
Once back into bootloader, I mounted usb storage, copied SU to the card, and flashed from zip
risb577 said:
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
Click to expand...
Click to collapse
Yeah, rom manager won't work bc we don't have official support from Koush for CWM recovery so that's no issue, I was just curious is all lol. I'm glad to hear titanium detects root, as that was an issue initially for the view. Try to backup your apps, test radios (3g, 4g, wifi, bluetooth, GPS, ETC), run quadrant. I don't know how familiar you are with honeycomb to test out all of it's functions, but we are going to need a few people to test this out for globatron so he can make fixes and/or adjustments as necessary, which is why he specifically asked for devs and people familiar with troubleshooting to do this first. That's the beauty of open source, we're all guinea pigs.
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
soft brick screen
ElAguila said:
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
Click to expand...
Click to collapse
It looks like this pic. Plus another clue you are soft bricked is it stays here longer than 10 minutes if you care to wait lol
My problem:
http://forum.xda-developers.com/showthread.php?p=22444589
1) I cannot boot my phone, the best i can is going to the bootloader
2)USB debugging can't function since i can't boot my phone
My phone:
HTC EVO 3D GSM
Hboot 1.49.0012
LOCKED
S-ON
Thread I have read:
http://forum.xda-developers.com/showthread.php?p=22444589
http://forum.xda-developers.com/showthread.php?t=1372097
http://forum.xda-developers.com/showthread.php?t=1467293
In conclusion, I understand the following:
boot my phone to fastboot
(turn off first.make sure completely off, then press volume down and power button)
connect my phone to pc, open cmd.exe
Sth I dk how to use:
(fastboot flash boot [location of boot.img]\boot.img
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands)
However, I would like to do a fastboot flash boot to solve the problem of stuck in HTC startup screen.
Difficulties: 1) .img file 2) command 3) would it "brick"? 4) KEEP SHIPPED
Targets: 1) Do not erase (mmssms.db) 2)mmssms.db backup and recovery 3) Functions my phone
Nokiawithandroid said:
My problem:
http://forum.xda-developers.com/showthread.php?p=22444589
Thread I have read:
http://forum.xda-developers.com/showthread.php?p=22444589
http://forum.xda-developers.com/showthread.php?t=1372097
http://forum.xda-developers.com/showthread.php?t=1467293
In conclusion, I understand the following:
boot my phone to fastboot
(turn off first.make sure completely off, then press volume down and power button)
connect my phone to pc, open cmd.exe
Sth I dk how to use:
(fastboot flash boot [location of boot.img]\boot.img
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands)
However, I would like to do a fastboot flash boot to solve the problem of stuck in HTC startup screen.
Difficulties: 1) .img file 2) command 3) would it "brick"? 4) KEEP SHIPPED
Targets: 1) Do not erase (mmssms.db) 2)mmssms.db backup and recovery 3) Functions my phone
Click to expand...
Click to collapse
Are you CDMA sounds like your on hboot 1.5? I dunno are you gsm or CDMA?
I know CDMA users make sure you have a copy of your recovery in your adb folder...
Make sure debug is turned on
Then when your in hboot
and plugged into computer using adb...
Type
fastboot boot recovery.img
This way you can flash whatever you want rom wise without taking the boot.img out of it... Also wipe before you go flashing...... This won't brick you... Only way to brick which is hard to do is you would have to flash the wrong radios or be in the middle of a flash or radio flash and pull the battery or your battery dies.... A brick is a useless phone that won't turn back on....
No such thing as a soft brick either lol.. Those are called bootloops or aka stuck on splash screen.... As long as your phone boots to Hboot your safe...
reaper24 said:
Are you CDMA sounds like your on hboot 1.5? I dunno are you gsm or CDMA?
I know CDMA users make sure you have a copy of your recovery in your adb folder...
Make sure debug is turned on
Then when your in hboot
and plugged into computer using adb...
Type
fastboot boot recovery.img
This way you can flash whatever you want rom wise without taking the boot.img out of it... Also wipe before you go flashing...... This won't brick you... Only way to brick which is hard to do is you would have to flash the wrong radios or be in the middle of a flash or radio flash and pull the battery or your battery dies.... A brick is a useless phone that won't turn back on....
No such thing as a soft brick either lol.. Those are called bootloops or aka stuck on splash screen.... As long as your phone boots to Hboot your safe...
Click to expand...
Click to collapse
Sorry, update the status apologize for the mistakes
Any expertise?
Helpppppppppppppppp pleaseeeeeeeee!!!!!!!!!!!!!!!!!!!!! (((
Nokiawithandroid said:
My problem:
http://forum.xda-developers.com/showthread.php?p=22444589
1) I cannot boot my phone, the best i can is going to the bootloader
2)USB debugging can't function since i can't boot my phone
My phone:
HTC EVO 3D GSM
Hboot 1.49.0012
LOCKED
S-ON
Thread I have read:
http://forum.xda-developers.com/showthread.php?p=22444589
http://forum.xda-developers.com/showthread.php?t=1372097
http://forum.xda-developers.com/showthread.php?t=1467293
In conclusion, I understand the following:
boot my phone to fastboot
(turn off first.make sure completely off, then press volume down and power button)
connect my phone to pc, open cmd.exe
Sth I dk how to use:
(fastboot flash boot [location of boot.img]\boot.img
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands)
However, I would like to do a fastboot flash boot to solve the problem of stuck in HTC startup screen.
Difficulties: 1) .img file 2) command 3) would it "brick"? 4) KEEP SHIPPED
Targets: 1) Do not erase (mmssms.db) 2)mmssms.db backup and recovery 3) Functions my phone
Click to expand...
Click to collapse
Seems to be conflicting information provided in the OP. Not sure the best route. Here is the information that seems to conflict, perhaps I misread?
1)If you're S-ON and LOCKED, I don't think you'll have access to use fastboot or any other HTC officially supported method of flashing the kernel. Normally, if you had previously unlocked the device to load a custom kernel and re-locked, it will show RELOCKED instead of LOCKED. Unless, you went the revolutionary route and then reflashed back to stock removing their S-OFF?
2) The kernel/boot partition will not touch the /data partition where (mmssms.db) is stored.
3) The device is pretty difficult to "brick". The common users you'll find claiming they have a brick, is generally due to their ignorance in not following proper directions to restore their device. Some find it easier to claim they "bricked" their device rather than do the proper research to resolve their issues.
4) The HTC splash screen freezing is generally either a bad/incompatible kernel or a bad/incompatible kernel/ROM combination. To fix either of this situations, the device will need to be UNLOCKED and/or S-OFF to allow write access to at least the kernel partition and, if needed, the system partition.
Hope that helps clarify some more!
joeykrim said:
Seems to be conflicting information provided in the OP. Not sure the best route. Here is the information that seems to conflict, perhaps I misread?
1)If you're S-ON and LOCKED, I don't think you'll have access to use fastboot or any other HTC officially supported method of flashing the kernel. Normally, if you had previously unlocked the device to load a custom kernel and re-locked, it will show RELOCKED instead of LOCKED. Unless, you went the revolutionary route and then reflashed back to stock removing their S-OFF?
2) The kernel/boot partition will not touch the /data partition where (mmssms.db) is stored.
3) The device is pretty difficult to "brick". The common users you'll find claiming they have a brick, is generally due to their ignorance in not following proper directions to restore their device. Some find it easier to claim they "bricked" their device rather than do the proper research to resolve their issues.
4) The HTC splash screen freezing is generally either a bad/incompatible kernel or a bad/incompatible kernel/ROM combination. To fix either of this situations, the device will need to be UNLOCKED and/or S-OFF to allow write access to at least the kernel partition and, if needed, the system partition.
Hope that helps clarify some more!
Click to expand...
Click to collapse
I am having something close to that issue. i have Hboot 1.49.0008 it is Unlocked but with s-On
now i can boot farther then the htc white. mine goes to the htc + quietly brilliant screen. then hits a boot loop.
what are my options and how do i do it?
thanks
joeykrim said:
Seems to be conflicting information provided in the OP. Not sure the best route. Here is the information that seems to conflict, perhaps I misread?
1)If you're S-ON and LOCKED, I don't think you'll have access to use fastboot or any other HTC officially supported method of flashing the kernel. Normally, if you had previously unlocked the device to load a custom kernel and re-locked, it will show RELOCKED instead of LOCKED. Unless, you went the revolutionary route and then reflashed back to stock removing their S-OFF?
2) The kernel/boot partition will not touch the /data partition where (mmssms.db) is stored.
3) The device is pretty difficult to "brick". The common users you'll find claiming they have a brick, is generally due to their ignorance in not following proper directions to restore their device. Some find it easier to claim they "bricked" their device rather than do the proper research to resolve their issues.
4) The HTC splash screen freezing is generally either a bad/incompatible kernel or a bad/incompatible kernel/ROM combination. To fix either of this situations, the device will need to be UNLOCKED and/or S-OFF to allow write access to at least the kernel partition and, if needed, the system partition.
Hope that helps clarify some more!
Click to expand...
Click to collapse
ok...then what can I do to fetch the data out or save my phone?
Nokiawithandroid said:
ok...then what can I do to fetch the data out or save my phone?
Click to expand...
Click to collapse
based on what has been said in the thread, you can flash a new system.img and that should give you access to the phone even if it starts FC like hell, all you need to do from there is to connect via adb backup the SMS database and continue with wiping everything and installing a new ROM (after you unlock of course)
just in case: once you get the system.img you need, apply it by typing
Code:
fastboot flash system [x:\path to file\]system.img
That should help you out.
megabiteg said:
based on what has been said in the thread, you can flash a new system.img and that should give you access to the phone even if it starts FC like hell, all you need to do from there is to connect via adb backup the SMS database and continue with wiping everything and installing a new ROM (after you unlock of course)
just in case: once you get the system.img you need, apply it by typing
Code:
fastboot flash system [x:\path to file\]system.img
That should help you out.
Click to expand...
Click to collapse
How can i flash the system.img? My phone isn't rooted or unlocked. It's totally original. Also, no way to get the debug or adb. The only connection I've got is the "fastboot usb" at the htc original bootloader.
Hopeless, right?
Nokiawithandroid said:
How can i flash the system.img? My phone isn't rooted or unlocked. It's totally original. Also, no way to get the debug or adb. The only connection I've got is the "fastboot usb" at the htc original bootloader.
Hopeless, right?
Click to expand...
Click to collapse
You posted this same question in a separate thread: http://forum.xda-developers.com/showthread.php?t=1525176
In an effort to keep the threads organized, I answered in that thread as follows:
Background on system.img: The system partition is generally only distributed in the system.img format for stock system images. Most aftermarket ROMs perfer to distribute their system content in the form of an update .zip file.
Background on bootloader: The system.img can't be flashed until you unlock the device. This is a standard security feature on any device with a "locked" bootloader, as yours shows from the information you posted.
One option: Once the bootloader is unlocked, the command should be as simple as: fastboot flash system c:\system.img
Hope that helps. Good luck!
Click to expand...
Click to collapse
Not sure how many times this can be repeated or how many different ways the same thing can be repeated. Without unlocking the device, HTC will not allow you to selectively modify any of the partitions from the bootloader or fastboot.
With these three conditions:
1) Without unlocking the device
2) Having the device freeze on the HTC splash screen
3) Never having previously loaded a custom recovery
The only option HTC provides is to run the RUU which will return the device to 100% stock erasing all information currently on the device.
If you're able to unlock the device (condition #1), you would be able to either flash a custom recovery (condition #3), or a stock/new system.img which would allow you access to the device where you can retrieving the stored SMS and MMS.
Using the stock RUU should resolve condition #2, if it didn't, there could be a more serious hardware issue with the device.
I might have missed some aspect. I'm sure somebody will post up if I did.
Hope that helps make more sense!
Dear Memeber
i find that my htc legend is un rooted and i need to root it to install a room to it i try many ways i find other the internet and it doesn't success to do it so am look for how and the way to root it
and will be thankful for you
-Unlock the boot loader using HTCDev
-Use HTCSuperTools v3 to gain root access
-Flash ClockworkMod Recovery
-Flash any ROM you want.
These are the basic steps. I might write up an updated, more detailed guide for others when I get back to a computer.
Sent from my Legend using XDA
Go to http://www.htcdev.com/bootloader/
Register, select your device and unlock the bootloader
Get HTC Super Tools from
http://forum.xda-developers.com/showthread.php?t=1343114
Run it, do options 1 and 3, in that order, to root your phone
Get Clockwork Recovery Mod from
http://forum.xda-developers.com/showthread.php?t=1290841
Use 1st step for S-OFF method to install ClockworkRecovery
Boot into Recovery mode and take a backup of your ROM
Download the ROM of your choice and copy it to your SD card
Boot into Recovery Mode, do a data wipe/factory reset and a cache wipe
Select Install from zip in Recovery, navigate to your ROM in SD Card and install it. Hope this helps.
This is a long process, at least for the first timers. You may get stuck at various places, please let us know if you do
Unlock the boot loader using HTCDev
-Use HTCSuperTools v3 to gain root access
i download this two items and i try to root it but it dosen't work with me or maybe i did something wrong
what is the steps that i have to follow by using them
and thanks for your replies
Regards
sometimes it says like this
C:\Android>fastboot oem get_identifier_token
< waiting for device >
...
and it stuck for along time and nothing changed
and other times when i press power button for the fastboot it change to be like this
(bootloader) [ERR] Command error !!!
OKAY [ 0.008s]
finished. total time: 0.008s
C:\Android>fastboot oem get_identifier_token
...
FAILED (status read failed (Too many links))
finished. total time: 4.670s
All I can think of is that you should start again reading every step carefully.
Also, jc36 that's a great guide
Sent from my Legend using XDA
clarify jc36 clockwork recovery mod step
I need to clarify something important for the "Get Clockwork Recovery Mod step which says to follow the 1st step for S-OFF method to install ClockworkRecovery.
On the linked page http://forum.xda-developers.com/show....php?t=1290841
Where it says the following:
"How to use S-OFF user
Download file and move on adb fastboot folder"
Does "move on adb fastboot folder" mean, put the file into the folder? And if so where is the folder?
There is no such folder: "adb fastboot folder"?
Does it mean:
1. put it in the Android folder created (C:\android) to hold the files instructed by HTC Dev for unlocking the bootloader?
2. Or put it in the android-sdk folder, somewhere? May be the Platform Tools folder where adb.exe exists?
Thanks to anyone who can help clarify this step for me
Yes it means put the recovery into the folder with adb.exe and fastboot.exe
Sent from my Legend using XDA
Thanks again
Thanks for clarifying that. As you can imagine I am a noob. It would be awesome if the brief procedure by jc36 could be expanded upon into an exact step-by-step (hand-holding) for all the noobs out there. Jumping back and forth between the forum links can get confusing -- especially some of the posts are old... leaving one wonder if the instructions are outdated etc!
May be I will do it if I get through this safely....
xdadufus said:
Thanks for clarifying that. As you can imagine I am a noob. It would be awesome if the brief procedure by jc36 could be expanded upon into an exact step-by-step (hand-holding) for all the noobs out there. Jumping back and forth between the forum links can get confusing -- especially some of the posts are old... leaving one wonder if the instructions are outdated etc!
May be I will do it if I get through this safely....
Click to expand...
Click to collapse
Brief is good although I do understand how a noob would want a step-by-step guide. In relation to date, none of the links I gave you were really outdated. The datestamp at the top of the thread might say '6th October 2011, 10:00 AM' but if you look at the bottom of the post it'll say something like 'Last edited by (username); 21st March 2012 at 09:32 AM' on threads/posts that get updated. Welcome to the Legend forums!
Further Clarification
I am continuing with my quest to clarify and document the whole jc36 procedure accurately.
1. After you have unlocked the bootloader are there any mode changes to be made before running SuperTools?
2. After running SuperTools, following the 1st step for S-OFF Clockwork Recovery Mod how do you put the phone into "fastboot" mode? Does the phone have to be disconnected again, powered down, restart with volume held down, highlighting Fastboot then press Power button and reconnecting to computer? Is this the procedure or is there another way while it still connected to the computer?
3. Continueing with Clockwork Recovery Mod code where it says:
"In fastboot mode:
Code:
adb reboot bootloader
fastboot flash recovery recovery_legend_5.0.2.8.img"
I'm guessing the code above is for command prompt for the c:\android directory as done previously for HTC Dev unlocking of the bootloader?
Open up command prompt. ( Start> Run> Type CMD,).
Command Prompt: cd c:\Android)
Type in Command Prompt:
adb reboot bootloader
fastboot flash recovery recovery_legend_5.0.2.8.img
Correct?
4. After completing Clockwork recovery Mod it says to "Boot into Recovery mode and take a backup of your ROM" -- again do you disconnect the phone to do this and boot into the bootloader to select Recovery mode? And how to you backup? Is it to an SD card or is the phone connected to the computer to take the backup to your hardrive?
Thank you to all in advance who take the time to go over these questions.
1. By mode changes I'm assuming you mean something like enabling USB debugging which is definitely recommended.
2.You get into fastboot mode by rebooting into the bootloader (Hold volume down+trackball+power button). Fastboot is the first selected option so all you have to do is press the power button to choose it and then it will go into fastboot mode
3.Yes in command prompt you navigate to the folder that has adb.exe, fastboot.exe and the recovery image and then carry out those commands
4.If you've flashed a ROM that supports it then in phone options(hold down power button) you can select Reboot and then Recovery. Otherwise to get to recovery you would have to go through the bootloader. To backup you go to Backup and Restore in CWM and select Backup or alternatively you can use ROM Manager to do a backup. The phone doesn't have to be disconnected and the backups are made to the micro SD Card.
Sent from my Legend using XDA
run in to trouble at the beginning
I have run into an error with the command provided with HTC Dev Unlock Bootloader.
I have followed all instructions very carefully. When in command prompt I get this error after entering:
fastboot oem get_identifier_token
...
<bootloader> [ERR] Command error !!!
I am in the android directory in c:\android and have the three files there:
adb.exe
adbWinApi.dll
fastboot (which I extracted from an older version of SDK as instructed by HTC because it doesn't exist in the latest SDK software)
Is your phone connected with USB Debugging on and HTC drivers installed on your computer?
bootloader now unlocked successfully
I just flashed the RUU that HTC Dev recommended for my phone, the version it should have before attempting to unlock the bootloader.
My phone originally had this updated version anyway so I never updated it on my first attempt.
After reading the forums here for people having similar issues I flashed their recommended RUU for the Legend and from that point on the command in command prompt worked. I have now unlocked the bootloader ...
what about gapps?
I finally rooted my phone and flashed cm7.2 ROM successfully after some nail biting experiences... it is not as simple as the instructions posted earlier in this forum make it appear... There were some issues I ran into. I will post an explanation of how I resolved them soon.
What good is a new android ROM without essential Google apps? I know they are not packaged due to licensing but I can not find a reasonable explanation of how to get them on my phone. I thought it would be simple but it is not. Right now I can not download any apps...
I read the gapps packages should be installed during the flashing of the ROM... that point is missing from the instructions here! So what now? Do I have to run through the process of flashing the ROM again along with the gapps package this time?
I tried installing the latest Google Play app but it would not connect to the server -- whatever that means -- after entering in my google account.
Is there any way to get the apps downloaded directly to my computer so I can copy them to the SD card? I did find a couple of solutions to do this but you need to enter google account details and some id number for the phone which I can not find... what is the identifier for the phone and where?
Any assistance on this would be greatly appreciated because at this point the whole new fresh ROM is useless...
You can flash GApps at any time. Whether it's during installation, right after first boot, or years later. Make sure you flash the appropriate .zip.
You can use APK Downloader to get them straight from the Play Store to your computer in .APK format.
http://codekiem.com/2012/02/24/apk-downloader/
All the latest Gapps packages can be found here. Use the 'gapps-gb-20110828-signed.zip' package if you're running Gingerbread and 'gapps-ics-20120429-signed.zip' if you're running ICS.
I need a bit more help please!
I have had the legend for ages and wanted to breath new life into it. I am using a ssensation as my everyday phone and that was a doddle to root compared to this!
I have gotten as far as flashing recovery. I dl'd the S-OFF .img from here and placed it in my adb folder. I tried running the adb command and only got as far as
"fastboot flash recovery" when
"error: neither -p product specified or ANDROID_PRODUCT_OUT set" shows up.
Any help? the HTCdev and Supertools seemed to go flawlessly for me. My HBOOT was 1.01 and HTCdev changed it to 1.02. It also now has *** LOCKED (OOW) *** at the top. I'm still S-ON too. What's going wrong? There is no su app in the app drawer like there was when I rooted my sensation. do I have to start over? any help would be great!
icanttinkofaname said:
I need a bit more help please!
I have had the legend for ages and wanted to breath new life into it. I am using a ssensation as my everyday phone and that was a doddle to root compared to this!
I have gotten as far as flashing recovery. I dl'd the S-OFF .img from here and placed it in my adb folder. I tried running the adb command and only got as far as
"fastboot flash recovery" when
"error: neither -p product specified or ANDROID_PRODUCT_OUT set" shows up.
Any help? the HTCdev and Supertools seemed to go flawlessly for me. My HBOOT was 1.01 and HTCdev changed it to 1.02. It also now has *** LOCKED (OOW) *** at the top. I'm still S-ON too. What's going wrong? There is no su app in the app drawer like there was when I rooted my sensation. do I have to start over? any help would be great!
Click to expand...
Click to collapse
You do see the words "locked"? that means its "locked" you need to follow the steps provided by htcdev in the email they would have sent you including the unlock.bin file with out those steps you can't do anything, its like its still not rooted.
Sent from my Legend using XDA
Sorry for repeated threads but i am stuck on this.
The procedure is -
Installing mySENSE-dx boot.img
Download the attached Boot.img_Installer_RC3.5.zip and extract it to your desktop
Boot into bootloader/fastboot mode
Connect your DX to PC
Open the Boot.img_Installer_RC3.5 folder and run the Install Boot.img.bat
What does 1st instructions mean, The full thread is below
http://forum.xda-developers.com/showthread.php?t=2081430
If you can't understand the basic instructions, you may end up with a non-working DX
The instructions are for installing/flashing boot.img to your device. For experience users they just do fastboot command but as I know there are a lot of new users like you... I made that instructions to help newbies.
Before you proceed, do you know what is bootloader and how to get there ?
If you did unlock your device, you should know.
ckpv5 said:
If you can't understand the basic instructions, you may end up with a non-working DX
The instructions are for installing/flashing boot.img to your device. For experience users they just do fastboot command but as I know there are a lot of new users like you... I made that instructions to help newbies.
Before you proceed, do you know what is bootloader and how to get there ?
If you did unlock your device, you should know.
Click to expand...
Click to collapse
Yes, I unlocked it yesterday and also installed a custom recovery( cmw 6.15). Now i just need to flash a good ROM and i found this great because of full sense. I have downloaded both Mysense ROM and boot.IMG installer and extrated both of them on desktop as folders.
What should be the next steps to take. Please explain.
ShivaPower said:
Sorry for repeated threads but i am stuck on this.
The procedure is -
Installing mySENSE-dx boot.img
Download the attached Boot.img_Installer_RC3.5.zip and extract it to your desktop
Boot into bootloader/fastboot mode
Connect your DX to PC
Open the Boot.img_Installer_RC3.5 folder and run the Install Boot.img.bat
What does 1st instructions mean, The full thread is below
http://forum.xda-developers.com/showthread.php?t=2081430
Click to expand...
Click to collapse
or try hansoons kit (its somewhere in original android development), it has nice gui and its working (especialy helpfull when your not experienced user)
I won't be responsible for something goes wrong
Basic things in flashing ROMs
1. Put the downloaded ROM on your sdcard
2. Put your device is fastboot mode/bootloader where you see the word Fastboot USB in red when you connect your device to PC.
3. Flash the boot.img (follow the earlier written instruction)
4. Press power once, you'll be on hboot screen, select recovery
5. In recovery, install the ROM
mindlesSheep said:
or try hansoons kit (its somewhere in original android development), it has nice gui and its working (especialy helpfull when your not experienced user)
Click to expand...
Click to collapse
Yes i have hasoons kit. I flash the recovery through it. How to install above mentioned ROM through kit.
put rom.zip on sdcard (doesnt matter when, but at some stages on flashing rom, you wont be able to acces card via phone, so you would have to use some sdcard reader)
use "flash kernel" option in kit to flash boot.img
then boot into recovery (manualy, or via command in kit), make a backup (more important than it sounds), then wipe system and cache, then install zip which you put on sd card
mindlesSheep said:
put rom.zip on sdcard (doesnt matter when, but at some stages on flashing rom, you wont be able to acces card via phone, so you would have to use some sdcard reader)
use "flash kernel" option in kit to flash boot.img
then boot into recovery (manualy, or via command in kit), make a backup (more important than it sounds), then wipe system and cache, then install zip which you put on sd card
Click to expand...
Click to collapse
Sorry i dont have sdcard, any other way
ShivaPower said:
Sorry i dont have sdcard, any other way
Click to expand...
Click to collapse
Put it in phone internal memory then. Or use adb sideload in recovery as final step, but thats the harder option
Thank You it was successfully done.
cheers.
unlocked
hboot 1.58
s on
htc evo 3d - virgin mobile
1. A small sectioin of the touch screen was not working for 3rd party apps. So, I thought a factory reset would help, however, I can't set the phone up b/c the sector isnt working.
2. Was hoping that if I root/flash that perhaps that sector will work - I have no idea what I'm doing/never done it.
3. So I can only work with the screen that you get when you hold the power button and volume down.
4. I have unlocked the phone using the htc development tools but I have no idea what to do next.
5. I go to mini-adb vigor ...use the command line adb devices .... but The adb devices command line is not showing any device
I've read so many damn tutorials on how to do this and they all have different routes and none of them seem to work, ie I cant figure them out.
So, can anyone help me figure out this issue ... what do I do next? The phone is unlocked using the htc dev tools ... I've downloaded a rom...Cool ICS ... what do I need to do in numberical order? Recovery ? (how do I do that) .... flash the rom (how do I do that?).
Thanks ...
1.
2. I suppose it's possible but I'd say unlikely as it sounds more like a hardware issue.
3. That is the bootloader
4. First step done!
5. Might be wrong here but there are a lot of possibilities. I will start with the one I think it probably is. After you htcdev unlock it factory resets your phone. You need to go back into your settings and enable usb debugging and disable the fastboot setting.
If that doesn't work we can troubleshoot other things but considering you were able to unlock with no problems (meaning you have the proper drivers etc) I'm guessing it's just your settings.
You are dead on with the order.
-Unlock bootloader
-Flash recovery
-Flash Super user (or a rooted rom)
*Unlock bootloader (done)
Download sulerSU: http://forum.xda-developers.com/showthread.php?t=1538053
*Flash recovery: http://db.tt/1QYlMnp5
Download that, rename to recovery.img
Put in your adb folder and use command: fastboot flash recovery recovery.img
Then use command: fastboot boot recovery.img
*Flash superSU While in recovery. That will root your phone. Alternatively flash cool ICS that you already downloaded.
That's basically it. That's pretty much the procedure for any htc phone. Unlock, recovery, root...
Let me know if you have any more questions