I updated my phone's SPL to "Danger SPL" and now my phone wont turn back on! I press power and the black Android screen with the little green android next to it comes up but wont boot my phone! The only thing I can do is get the white screen with the 3 android's skateboarding by pressing camera + power.
Ontop of that, I had tried to update my phone's recovery image too, and I erased the old one and now it would let me upload the NEW one! So not only do I have NO PHONE but NO RECOVERY either!
What do I do!? HELP!
can you get into fastboot? (back+power)
if you can, get adb running and flash your recovery image with fastboot
you are gonna have to fast boot in the screen with the three androids on it, either a rom or a recovery
guess you betta learn how to use adb
Yea I can get into fastboot, thats the ONLY thing I can get into. How do I flash my recovery image?
http://forum.xda-developers.com/showthread.php?t=566669
boot your phone into fastboot. plug in your usb cable to your pc. this should change the fastboot icon on the screen to fastboot usb. from there, load up adb on your pc and make sure you have the fastboot option available by typing fastboot devices. it should list your phone. once that is good, type:
fastboot flash recovery and the correct name of your recovery file.
for example:
fastboot flash recovery recovery-RA-dream-v1.2.3.img
**also note...put the recovery image in your android sdk\tools folder**
this should give you a recovery to boot into.
if you dont have adb on your pc, read this and follow the instructions
http://forum.xda-developers.com/showthread.php?t=532719
I did that already, it wont work.
C:\Android>fastboot flash recovery recovery123.img
error: cannot load 'recovery123.img'
i am gonna be the one to ask this question but did you put .s between 123 like 1.2.3.
you need to be in the tools directory, not the android directory.
c:\Android\tools>fastboot flash recovery recovery-RA-dream-v1.2.3.img
and you need the recovery file IN your tools folder for it to be found as well.
No I didn't put .'s between each number I renamed my file recovery123.img so thats the way I put it in.
ok, so go to the correct directory and input what you had the first time, WITH the file IN that same folder. and then report back.
i justed rename my recovery the shortest way i can like for amon ra"s i just put amon, less typing is always better
It says C:\Android\tools is not recognized as an internal or external command, operable program or batch file.
from your c:\> prompt type this:
cd c:\android\tools
(this is assuming you have the android sdk in the c:\android folder on your pc)
if it is saying its not a folder, then that is not where you installed the android sdk.
knowfear said:
and you need the recovery file IN your tools folder for it to be found as well.
Click to expand...
Click to collapse
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
If you use the above SPL you will need new drivers for Windows. They are located here.
Click to expand...
Click to collapse
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
what he said.
Binary100100 said:
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
Click to expand...
Click to collapse
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
innerspace said:
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
Click to expand...
Click to collapse
No problem. I just hate it when something this simple drags onto multple pages. Call it a peev. So many people get intimidated by the "Danger SPL" because they don't want to risk bricking their phones. The odds of bricking your phone are extremely small if you follow directions and read everything. And sure the possibility of accomplishing this by different means exists. But when you try to tell someone to put this file in that folder and type in the full names of the files to include all the dots and dashes, it's going to get confusing and intimidating and thus these posts keep popping up.
If someone follows those very short and simple directions they shouldn't have any problems. Granted that "**** happens" and things don't always go as they should. So in that case, search for your answer. If you've searched on XDA then search Google. Out of the MILLIONS of G1's that have been sold, I am fairly certain that someone out there has had a similar problem. If not then you and your phone are literally "1 in a million" (technically it was 1 in 1.5 million a year ago so you can bet that it's well over 2 if not 3 million by now). And if you really fall into that catagory then please post a new thread (in the appropriate catagory of course) .
well the good news is u didnt brick ur phone but try a enter adb and do a nadroid back up if u hav 1 that will bring u back 2 the way u want it
either flash a nadroid or flash dreaming.nbh....i had the same problem and a nadroid worked just fine
Hey XDA ,
I have only been here for a couple of weeks (2-3 weeks ) and I must say, this place has a fantastic community. Everyone is always very nice and respectful. :highfive:
However, I have looked through this place and sometimes, some guides may be outdated (new ROMs, recovery, HBOOTs etc.) so I want to create this thread and hopefully maintain it to my best abilities. I will try and come back here at least once everyday to help anyone
DISCLAIMER: IF YOU SCREW UP YOUR PHONE IN ANYWAY FOLLOWING THIS GUIDE I AM NOT TO BE HELD RESPONSIBLE!!! Please understand this!!!
CREDITS: I take absolutely no credit for anything that I write here. I took it from other people's threads and from here, here, and here.
Your phone should be HBOOT 2.02.0002 or HBOOT 2.03.0000 with official ICS 4.0.4 with HTC Sense 3.6.
This method will also work if you have Gingerbread but you may still have HBOOT that is not 1.13.0000
Throughout this guide I will give u (hopefully) working links that will give you everything you need, Backup your data, Unlock your bootloader, Flashrecovery, Install Superuser, Backup Stock ROM, Downgrade your HBOOT, Use revolutionary to gain S-OFF, flash custom ROM, and (optional) install Blackrose 2.03.0000.
Just a few suggestions and little information here:
Be aware that this could take quite a bit of time and everything might not go through as planned. If it does not go as planned, then try googling it, search XDA for an answer, or ask people on XDA. Everyone on XDA is very nice and is always willing to help (as long as it coems within forum rules).
Secondly, I suggest u remove your SIM card from the phone so you will not be receiving any phone calls or messages or whatnot that could possibly mess the process up (optional. I did it just in case).
Thirdly, make sure to have a full battery charge even though you will have your phone connected to the computer from time to time.
1. Download and Set Everything up
On your C: drive, create an "android" folder. I will be referring to this throughout the guide.
This next part is really optional but it will help you be more tidy and orderly.
In C:/android create a "Blackrose" folder
In C:/android create a "Revolutionary" folder
In C:/android create a "Downgrade" folder
In C:/android/Downgrade, create a "Downgradekit" folder and an "RUU" folder.
Get HTC Sync here
Get IncS_MVDTKv3.4.1.zip and the RUU here. For the RUU, download the Typical IncS one unless you are with Sasktel or Bell in Canada or a South American user.
Get ClockworkMod Recovery here. Scroll to HTC Incredible S. At time of writing, the latest version was 5.0.2.0.
***You are also more than welcome to try ClockworkMod Recovery v6.0.2.7 If you would like the link, here it is. However this is not an official release but remains pretty much bugless. You may also choose to flash 4ext (touch) recovery, though you better read up on how to flash it cause it is slightly different (although more automated and simple). I will NOT help you if you choose to flash 4ext (cause if you screw it up, then you better stop right there... This is not joke, thats how simple it is)
Get SuperUser here here
Get CyanogenMod ROM here
Get Blackrose here
Install HTC Sync, then uninstall it. We only need the drivers so the actual application is uneeded. (In the control panel, make sure you only select the one with the icon!)
Extract the files from the IncS_MVDTKv3.4.1.zip into the C:/android/Downgrade/Downgradekit. In the downgradekit folder, you should now have the "runme.cmd" and the "files" folder
Put the clockworkmod recovery on the root of C:/android (no folders or anything)
Put Superuser-3.1.3-arm-signed.zip on the root of your SD card on the Incredible S. DO NOT EXTRACT ANY FILES
Put CyanogenMod ROM on the root of your SD card. DO NOT EXTRACT ANY FILES
Take note of your devices serial number. It is either under the phone's battery or in the settings>About Phone. I forget the exact location of the serial number in the About Phone section of the settings but it should not take too long to find it. It started off with "HT......."
Enable USB Debugging on your phone. On Gingerbread this can be found under Settings>Applications> Enable Unknown Sources> Development and check USB Debugging. On ICS 4.0.4, it is found under Settings>Developer Options>Check Android Debugging
2. Backup your data
This step is completely optional and I will not post any apps whatsoever here. Google Play Store will help you here. I did not back up any thing on my phone (I do not have anything important so I did not really care).
3. Unlock Bootloader
Go to htcdev.com/bootloader. Create a free account and unlock the Bootloader. The steps are very simple and you should not run into any trouble. At some point during this process, you will receive confirmation on your phone that will ask you If you want to Unlock your Bootloader. Click Volume up and Power (these are hardware buttons on the side and top, just in case) to click yes.
Note: they tell you to download some thing like Android SDK. Put it all in your C:/android folder
Congrats. You just unlocked your bootloader.
4. Flash a recovery
Switch off your phone and go into bootloader. You will now see, highlighted in pink, UNLOCKED. Tog et into the bootloader, power down, then hold Volume Down and press Power button at the same time.
Plug your phone to the computer via USB cable, highlight fasboot and press power button to confirm. On your PC go to C:/android. Press Shift and right click. Press "Open Command Window here"
then type "fastboot devices". Your devices serial number should show up.
Then type in fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img (assuming you did not change the name of the recovery image. If you did change it, type what you changed it too and do not forget the .img at the end
After a few seconds, the recovery should have been flashed to your phone.
5. Install Superuser and Test Root Access
From the fastboot menu, click volume down and press power button. This should bring you back to the bootloader screen.
Press volume down once to highlight RECOVERY and press power button. The HTC Splash screen should come up for a few seconds, the you will see the ClockworkMod interface. To navigate through this, use the volume up and down buttons to scroll and press the power button to confirm something.
Select "Install zip from sdcard"
Select "Choose zip from sdcard"
Select the Superuser-3.1.3-arm-signed.zip (this should be on the root of your sd card)
Select yes in the field of no's (lool i know XD)
Once it is done installing, reboot your phone. In the app drawer, you will notice that a new app called Superuser or SuperSU has showed up.
You should have root access but lets just be sure anyways. Go to C:/android and Shift, right click to Open Command Window here.
Type in adb.exe shell and press enter
You should get $ meaning adb has connected to your phone.
Next, type in su. If you obtain #, this means you have root access. Hooray
EXTREMELY IMPORTANT IF YOU ARE PLANNING TO STOP GUIDE HERE. LIKE REALLY IMPORTANT!!!!!!!!!!!!!!!!!!!!!!!
At this point you will be able to flash most ROMs. The exceptions are the one that require S-OFF (the ROM requirements in the thread will state so). Also you will have to flash the boot.img manually
To do this download your select ROM. Extract the boot.img to where you have the fastboot.exe, adb.exe, and AdbWinApi.dll (you should have gotten these 3 files when you unlocked the bootloader). Then open the command window (shift, right click, open command window here) and type:
fastboot flash boot boot.img
the boot.img can be renamed to whatever you would like. I keep all my boot images and the fastboot.exe, adb.exe, and AdbWinApi.dll in 1 folder because i download a lot of ROMs. If you do rename the boot.img, i suggest renaming it to the name of the ROM its for. When you type in the fastboot command, just remember to put the .img at the end. This is necessary or it will not work.
If you want to gain S-OFF continue through the guide.
6. Backup Stock Rom
(optional but highly advised just in case something does not work right, then you have something to fall back on)
Go back to ClockworkMod Recovery (reboot into bootloader>select recovery)
Scroll to Backup and Restore
Then press Backup.
7. Run Nonverbose's script
***IF YOU HAVE HBOOT 1.13.0000 THEN YOU DO NOT DO THIS STEP***
Plug your phone into PC if it is not already. Select Charge Only, enable USB Debugging, and make sure fastboot is OFF (Settings>Power)
In C:/android/downgrade/downgradekit, launch runme.cmd
This part should be relatively simple. Just answer the questions honestly, and the script will do its stuff. If i recall correctly, the first question was are you running official ICS unlocked bootloader. I typed n.
Are you rooted?-n
Do you want to create a goldcard?- answer "y" or else you will get a customer ID error (which I believe is either Error 130 or Error 131) while running the downgrade RUU
Are you running HTC bootloader unlocked (or something similar to that)?-y (unless your version main comes out as something other than 2.00000000... in which case, type "n")
Note: Use this second method ONLY if the script did not work.
This script has worked for a lot of people, but it did not seem to work for me. So i typed in the command prompt
Navigate to the downgradekit folder or alternatively, shift right click within the folder to opwen command window here
adb push misc_version /data/local/tmp <------ copies the file to the device
adb.exe shell <------ you will get $ prompt
su <------ gain root access
chmod 777 /data/local/tmp/misc_version <------ changing permissions of the file to execute
/data/local/tmp/misc_version -s 1.00.000.0 <------ you are faking the device to run the RUU installler to "upgrade" to Gingerbread
reboot bootloader <------ self-explanatory
In the bootloader>fastboot, check to see if the misc_version worked, type:
fastboot getvar version-main
If it returns
version-main: 1.00.000.01
then you are good to go
8. Run the RUU
***IF YOU HAVE HBOOT 1.13.0000 THEN YOU DO NOT DO THIS STEP***
After you run Nonverbose's script, reboot into the bootloader>fastboot and launch the RUU file from the C:/android/Downgrade/RUU
This process takes about 10 minutes so be patient. At the end of that, reboot to bootloader and the you should read somewhere
HBOOT-1.13.0000
This indicates you successfully downgraded the HBOOT.
9. Use Revolutionary to gain S-OFF
Put phone in normal charge mode, USB debug ON, fastboot off
Go to revolutionary.io
Scroll down to Downloads. Click download from Windows
Fill out the Beta Key form:
Your Operating System- Windows
Your Device- HTC Incredible S
HBOOT version- 1.13.0000
Serial number- Enter your serial number
Click Generate Key. Copy and Paste the Key to notepad or something.
Now I, for some reason could not get Revolutionary to work just by opening the exe file..... Since pictures are worth a thousand words, i have decided to post a Youtube clip which gives you verbal and graphical instructions on how to run Revolutionary.
The clip is right here. It is really simple the way the person describes the process. Just follow exactly how he does it and you will be fine.
If you reboot your phone into bootloader after running revolutionary, you will see **REVOLUTIONARY** where it once said **UNLOCKED**
After you have successfully run Revolutionary, check for root access by repeating step 5. If you get # at the end you are good to go If you do not have root, then re-flash the superuser-3.1.3-arm-signed.zip in ClockworkMod Recovery.
**Please keep in mind that during the revolutionary, it asks you whether you want to flash a recovery. This flashes, (if i remember correctly) version 4.XXXXXX.... of ClockworkMod. You can choose to select yes to this, but i would suggest saying "no" because its an older version. After you successfully run revolutionary, reboot into bootloader>fastboot and do step 4 again where you flash CWM 5.0.2.0. **
At step 5, i mentioned the command line fastboot flash boot boot.img. This is now unnecessary if you gain S-OFF. Now you can flash any ROM you want on the go.
10. Flash a Custom ROM
Here is a nice index of ROMs, Kernels, Radios etc. This is updated once a month by the OP and has everything you need to get started.
I did request that you download CyanogenMod 7.2 so let's just use that for now.
Go back to ClockworkMod Recovery and make another backup. Keep in mind that this should be done everytime you decide to flash a new ROM to your phone.
Once you are done, go back and select Wipe data/factory reset, Wipe Cache Partition, and under advanced, wipe dalvik cache.
Go back to main recovery menu, select Install Zip from sd card.
Choose the CM7 zip (cm-7.2.0-vivo.zip if you did not rename it to something else)
Wait for it to be installed to your phone. When it is finished, reboot your phone and voila! You are running your first ROM.
11. Install Blackrose 2.03.0000
This eleventh step is optional as most ROMs do not require Blackrose HBOOT. However, if you have blackrose HBOOT and you flash a ROM that has just S-OFF as a requirement, nothing should go wrong. The ROM should still work perfectly fine.
To install BlackRose 2.03.0000
Plug your phone, charge only, USB debug on
In your C:/android/blackrose, run BlackRose_IS.exe
If it tells you, you need HTC Sync, just reinstall it, not that hard.
After that, wait for it the Blackrose.exe to finish executing
If everything ran correctly, turn off your phone, then back in bootloader mode.
Where it said **REVOLUTIONARY**, it should now say **BLACKROSE** Your HBOOT will also change from 1.13.0000 to HBOOT-2.03.0000
Some people have stated that they get stuck on the HTC splash screen. If so, just reinstall CyanogenMod 7 ROM like you did in step 10 and reboot.
After this you should now have BlackRose HBOOT, S-OFF, and a CM7 ROM flashed to your phone. Congratulations!!!
***Do not ask why Blackrose is not running unless you are sure you are running a rooted ROM (just use CM7, like cmon, its known to work so just use it to have less headaches)
Hey guys. Heres a great edition to this guide that can supplement or pretty much replace this section of Blackrose installation. This guide was made Sandeep_Jagtap. Give thanks to him :good:
If you would like to try a different ROM go to the index and select a ROM.
Happy Hunting
Note: Never compare ROMs. That means no: which ROM is best for this or that or what ROM is smoothest or anything like that.
You don't compare ROMs because:
1. Developers spend a lot of time making their respective ROMs.
2. Its disrespectful and rude to the developers.
3. XDA is not a competition ground for who can make the best ROM. Its here to give us the ability to discuss how we do so and so or whatever, just not comparing things with another.
In essence, the only comments going up about ROMs should be "Great ROM but I had so and so problem" (assuming so and so problem existed of course)
Appreciate the contribution, but you should have posted this in the General section. This is not a Development topic and should not have been posted here.
super
super super super !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
thanks ................................ Спасибо все отлично
072665995 said:
Hey XDA ,
I have only been here for a couple of weeks (2-3 weeks ) and I must say, this place has a fantastic community. Everyone is always very nice and respectful. :highfive:
However, I have looked through this place and sometimes, some guides may be outdated (new ROMs, recovery, HBOOTs etc.) so I want to create this thread and hopefully maintain it to my best abilities. I will try and come back here at least once everyday to help anyone
DISCLAIMER: IF YOU SCREW UP YOUR PHONE IN ANYWAY FOLLOWING THIS GUIDE I AM NOT TO BE HELD RESPONSIBLE!!! Please understand this!!!
CREDITS: I take absolutely no credit for anything that I write here. I took it from other people's threads and from here, here, and here.
Your phone should be HBOOT 2.02.0002 or HBOOT 2.03.0000 with official ICS 4.0.4 with HTC Sense 3.6.
This method will also work if you have Gingerbread but you may still have HBOOT that is not 1.13.0000
Throughout this guide I will give u (hopefully) working links that will give you everything you need, Backup your data, Unlock your bootloader, Flashrecovery, Install Superuser, Backup Stock ROM, Downgrade your HBOOT, Use revolutionary to gain S-OFF, flash custom ROM, and (optional) install Blackrose 2.03.0000.
Just a few suggestions and little information here:
Be aware that this could take quite a bit of time and everything might not go through as planned. If it does not go as planned, then try googling it, search XDA for an answer, or ask people on XDA. Everyone on XDA is very nice and is always willing to help (as long as it coems within forum rules).
Secondly, I suggest u remove your SIM card from the phone so you will not be receiving any phone calls or messages or whatnot that could possibly mess the process up (optional. I did it just in case).
Thirdly, make sure to have a full battery charge even though you will have your phone connected to the computer from time to time.
1. Download and Set Everything up
On your C: drive, create an "android" folder. I will be referring to this throughout the guide.
This next part is really optional but it will help you be more tidy and orderly.
In C:/android create a "Blackrose" folder
In C:/android create a "Revolutionary" folder
In C:/android create a "Downgrade" folder
In C:/android/Downgrade, create a "Downgradekit" folder and an "RUU" folder.
Get HTC Sync here
Get IncS_MVDTKv3.4.1.zip and the RUU here. For the RUU, download the Typical IncS one unless you are with Sasktel or Bell in Canada or a South American user.
Get ClockworkMod Recovery here. Scroll to HTC Incredible S. At time of writing, the latest version was 5.0.2.0.
Get SuperUser here here
Get CyanogenMod ROM here
Get Blackrose here
Install HTC Sync, then uninstall it. We only need the drivers so the actual application is uneeded. (In the control panel, make sure you only select the one with the icon!)
Extract the files from the IncS_MVDTKv3.4.1.zip into the C:/android/Downgrade/Downgradekit. In the downgradekit folder, you should now have the "runme.cmd" and the "files" folder
Put the clockworkmod recovery on the root of C:/android (no folders or anything)
Put Superuser-3.1.3-arm-signed.zip on the root of your SD card on the Incredible S. DO NOT EXTRACT ANY FILES
Put CyanogenMod ROM on the root of your SD card. DO NOT EXTRACT ANY FILES
Take note of your devices serial number. It is either under the phone's battery or in the settings>About Phone. I forget the exact location of the serial number in the About Phone section of the settings but it should not take too long to find it. It started off with "HT......."
Enable USB Debugging on your phone. On Gingerbread this can be found under Settings>Applications> Enable Unknown Sources> Development and check USB Debugging. On ICS 4.0.4, it is found under Settings>Developer Options>Check Android Debugging
2. Backup your data
This step is completely optional and I will not post any apps whatsoever here. Google Play Store will help you here. I did not back up any thing on my phone (I do not have anything important so I did not really care).
3. Unlock Bootloader
Go to htcdev.com/bootloader. Create a free account and unlock the Bootloader. The steps are very simple and you should not run into any trouble. At some point during this process, you will receive confirmation on your phone that will ask you If you want to Unlock your Bootloader. Click Volume up and Power (these are hardware buttons on the side and top, just in case) to click yes.
Note: they tell you to download some thing like Android SDK. Put it all in your C:/android folder
Congrats. You just unlocked your bootloader.
4. Flash a recovery
Switch off your phone and go into bootloader. You will now see, highlighted in pink, UNLOCKED. Tog et into the bootloader, power down, then hold Volume Down and press Power button at the same time.
Plug your phone to the computer via USB cable, highlight fasboot and press power button to confirm. On your PC go to C:/android. Press Shift and right click. Press "Open Command Window here"
then type "fastboot devices". Your devices serial number should show up.
Then type in fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img (assuming you did not change the name of the recovery image. If you did change it, type what you changed it too and do not forget the .img at the end
After a few seconds, the recovery should have been flashed to your phone.
5. Install Superuser and Test Root Access
From the fastboot menu, click volume down and press power button. This should bring you back to the bootloader screen.
Press volume down once to highlight RECOVERY and press power button. The HTC Splash screen should come up for a few seconds, the you will see the ClockworkMod interface. To navigate through this, use the volume up and down buttons to scroll and press the power button to confirm something.
Select "Install zip from sdcard"
Select "Choose zip from sdcard"
Select the Superuser-3.1.3-arm-signed.zip (this should be on the root of your sd card)
Select yes in the field of no's (lool i know XD)
Once it is done installing, reboot your phone. In the app drawer, you will notice that a new app called Superuser or SuperSU has showed up.
You should have root access but lets just be sure anyways. Go to C:/android and Shift, right click to Open Command Window here.
Type in adb.exe shell and press enter
You should get $ meaning adb has connected to your phone.
Next, type in su. If you obtain #, this means you have root access. Hooray
At this point you will be able to flash most ROMs. The exceptions are the one that require S-OFF (the ROM requirements in the thread will state so). Also you will have to flash the boot.img manually
To do this download your select ROM. Extract the boot.img to where you have the fastboot.exe, adb.exe, and AdbWinApi.dll (you should have gotten these 3 files when you unlocked the bootloader). Then open the command window (shift, right click, open command window here) and type:
fastboot flash boot boot.img
the boot.img can be renamed to whatever you would like. I keep all my boot images and the fastboot.exe, adb.exe, and AdbWinApi.dll in 1 folder because i download a lot of ROMs. If you do rename the boot.img, i suggest renaming it to the name of the ROM its for. When you type in the fastboot command, just remember to put the .img at the end. This is necessary or it will not work.
If you want to gain S-OFF continue through the guide.
6. Backup Stock Rom (optional but highly advised jsut in case something does not work right and you have something to fall back on)
Go back to Clockworkmod Recovery (reboot into bootloader>select recovery)
Scroll to Backup and Restore
Then press Backup.
7. Run Nonverbose's script
***IF YOU HAVE HBOOT 1.13.0000 THEN YOU DO NOT DO THIS STEP***
Plug your phone into PC if it is not already. Select Charge Only, enable USB Debugging, and make sure fastboot is OFF (Settings>Power)
In C:/android/downgrade/downgradekit, launch runme.cmd
This part should be relatively simple. Just answer the questions honestly, and the script will do its stuff. If i recall correctly, the first question was are you running official ICS unlocked bootloader. I typed n.
Are you rooted?-n
Do you want to create a goldcard?- optional though i would suggest it
Are you running HTC bootloader unlocked (or something similar to that)?-y (unless your version main comes out as something other than 2.00000000... in which case, type "n")
This script has worked for a lot of people, but it did not seem to work for me. So i typed in the command prompt
Navigate to the downgradekit folder or alternatively, shift right click within the folder to opwen command window here
adb push misc_version /data/local/tmp <------ copies the file to the device
adb.exe shell <------ you will get $ prompt
su <------ gain root access
chmod 777 /data/local/tmp/misc_version <------ changing permissions of the file to execute
/data/local/tmp/misc_version -s 1.00.000.0 <------ you are faking the device to run the RUU installler to "upgrade" to Gingerbread
reboot bootloader <------ self-explanatory
In the bootloader>fastboot, check to see if the misc_version worked, type:
fastboot getvar version-main
If it returns
version-main: 1.00.000.01
then you are good to go
Note: Use the second method ONLY if the script did not work.
8. Run the RUU
***IF YOU HAVE HBOOT 1.13.0000 THEN YOU DO NOT DO THIS STEP***
After you run Nonverbose's script, launch the RUU file from the C:/android/Downgrade/RUU
This process takes about 10 minutes so be patient. At the end of that, reboot to bootloader and the you should read somewhere
HBOOT-1.13.0000
This indicates you successfully downgraded the HBOOT.
9. Use Revolutionary to gain S-OFF
Put phone in normal charge mode, USB debug ON, fastboot off
Go to reviolutionary.io
Scroll down to Downloads. Click download from Windows
Fill out the Beta Key form:
Your Operating System- Windows
Your Device- HTC Incredible S
HBOOT version- 1.13.0000
Serial number- Enter your serial number
Click Generate Key. Copy and Paste the Key to notepad or something.
Now I, for some reason could not get Revolutionary to work just by opening the exe file..... Since pictures are worth a thousand words, i have decided to post a Youtube clip which gives you verbal and graphical instructions on how to run Revolutionary.
The clip is right here. It is really simple the way the person describes the process. Just follow exactly how he does it and you will be fine.
If you reboot your phone into bootloader after running revolutionary, you will see **REVOLUTIONARY** where it once said **UNLOCKED**
After you have successfully run Revolutionary, check for root access by repeating step 5. If you get # at the end you are good to go
At step 5, i mentioned the command line fastboot flash boot boot.img. This is now unnecessary if you gain S-OFF. Now you can flash any ROM you want on the go.
10. Flash a Custom ROM
Here is a nice index of ROMs, Kernels, Radios etc. This is updated once a month by the OP and has everything you need to get started.
I did request that you download CyanogenMod 7.2 so let's just use that for now.
Go back to ClockworkMod Recovery and make another backup. Keep in mind that this should be done everytime you decide to flash a new ROM to your phone.
Once you are done, go back and select Wipe data/factory reset, Wipe Cache Partition, and under advanced, wipe dalvik cache.
Go back to main recovery menu, select Install Zip from sd card.
Choose the CM7 zip (cm-7.2.0-vivo.zip if you did not rename it to something else)
Wait for it to be installed to your phone. When it is finished, reboot your phone and voila! You are running your first ROM.
11. Install Blackrose 2.03.0000
This eleventh step is optional as most ROMs do not require Blackrose HBOOT. However, if you have blackrose HBOOT and you flash a ROM that has just S-OFF as a requirement, nothing should go wrong. The ROM should still work perfectly fine.
To install BlackRose 2.03.0000
Plug your phone, charge only, USB debug on
In your C:/android/blackrose, run BlackRose_IS.exe
If it tells you, you need HTC Sync, just reinstall it, not that hard.
After that, wait for it the Blackrose.exe to finish executing
If everything ran correctly, turn off your phone, then back in bootloader mode.
Where it said **REVOLUTIONARY**, it should not say **BLACKROSE** Your HBOOT will also change from 1.13.0000 to HBOOT-2.03.0000
Some people have stated that they get stuck on the HTC splash screen. If so, just reinstall CyanogenMod 7 ROM like you did in step 10 and reboot.
After this you should now have BlackRose HBOOT, S-OFF, and a CM7 ROM flashed to your phone. Congratulations!!!
If you would like to try a different ROM go to the index and select a ROM.
I have personally tried all the Jellybean 4.1.X ROMs, almost all the Ice Cream Sandwich 4.0.X with Sense 4.X Roms, almost all the ROMs from the Ice Cream Sandwich 4.0.X with Sense 3.6/3.5 and Rebased Multilang MIUI4 ROM under MIUI ROM's. I really liked all of them. Great job out there devs :good: :good: :good: :good:
Ones i liked in particular are
From Jellybean 4.1.X: Unofficial CyanogenMod 10 (seems to have the least problems) Android Open Kang Project Release v2 (great customizability though browse through the pages as there are still a number of bugs), and Paranoid Android v1.9.7 (again great number of features here)
From ICS 4.0.X with Sense 4.X: Sabsa Prime v12 (very few bugs as well as a number of different mods that you can add from the installer) and ViperVIVO 1.3.0 (for its great level of customizability clearly evident through the creation of the Venom Hub).
From ICS 4.0.X with Sense 3.6/3.5: Incredible Bliss v1 (its stable, adds a new look, and its really smooth like Project Butter), Android Revolution HD 4.0 (its essentially the same thing as HTC Sense 3.6 except the developper added a lot of hardware speed upgrades and improved its stability) as well as the Second Sun V2.5 (all that's got to be said is that its a great ROM that is similar to Android Revolution HD; improced stock sense 3.6)
These are just my favorites but you really have to try them all out to know which ones you like best Happy Hunting
Please note this is my first guide. If I am missing anything here please inform me and I will correct it. Thank you very much!
Click to expand...
Click to collapse
I tried, but it said thats error [131] Customer ID ERROR in step 8 (run RUU)
My IS Hboot 2.0.2 - S on
I think It might have goldcard?
V77V77 said:
I tried, but it said thats error [131] Customer ID ERROR in step 8 (run RUU)
My IS Hboot 2.0.2 - S on
I think It might have goldcard?
Click to expand...
Click to collapse
Yes you need a goldcard to proceed.
V77V77 said:
I tried, but it said thats error [131] Customer ID ERROR in step 8 (run RUU)
My IS Hboot 2.0.2 - S on
I think It might have goldcard?
Click to expand...
Click to collapse
Yes you do need a goldcard. Did you select yes when nonverbose's script asked you do you want a goldcard? If you pressed no, then I would suggest you rerun the script and press "y" when it asks you.
Starting Now
Im Trying now, wish me luck! :good:
072665995 said:
Yes you do need a goldcard. Did you select yes when nonverbose's script asked you do you want a goldcard? If you pressed no, then I would suggest you rerun the script and press "y" when it asks you.
Click to expand...
Click to collapse
Thank you very much.
I have done jet.:victory:
Ah, when i run nonverbose's script, make the gold card, the script run very fast.So where did the goldcard save?How can i backup it?
V77V77 said:
Thank you very much.
I have done jet.:victory:
Ah, when i run nonverbose's script, make the gold card, the script run very fast.So where did the goldcard save?How can i backup it?
Click to expand...
Click to collapse
The script turned your SD card into a goldcard. It wrote a special signature to the SD Card. You can continue to use it as a normal SD card.
tpbklake said:
The script turned your SD card into a goldcard. It wrote a special signature to the SD Card. You can continue to use it as a normal SD card.
Click to expand...
Click to collapse
Ahh tpbklake, u always beat me to it but its always great that everyone's always willing to help those who need it
Hi there,
I am following the guide but somehow i don't know why the computer cannot detect the devices during the fastboot mode. But the device can be found if it is booted into the android OS. I am using a mac and thus using a VM with Windows XP. I don't know if it may cause the issue.
When I was trying to type "fastboot devices", it actually doesn't work in XP (connected to Xp). But it's able to work in Mac where I type "fastboot-mac devices" (connected to mac). Thus I can go thru the step 4.
Now I am stuck at Step 7 where the script boot the device into the fastboot mode.
Could anyone help?
chpchai said:
Hi there,
I am following the guide but somehow i don't know why the computer cannot detect the devices during the fastboot mode. But the device can be found if it is booted into the android OS. I am using a mac and thus using a VM with Windows XP. I don't know if it may cause the issue.
When I was trying to type "fastboot devices", it actually doesn't work in XP (connected to Xp). But it's able to work in Mac where I type "fastboot-mac devices" (connected to mac). Thus I can go thru the step 4.
Now I am stuck at Step 7 where the script boot the device into the fastboot mode.
Could anyone help?
Click to expand...
Click to collapse
Go to fastboot menu in bootloader. Does it say fastboot usb. If it does not, then there might be something wrong with your phone miniHDMI port, the computers USB port, or the cable. If it does then i must ask, in command prompt, did u navigate to the location of the adb.exe, fastboot.exe, AdbWinApi.dll (during bootlaoder unlock process, they should have asked for these files)??
072665995 said:
Go to fastboot menu in bootloader. Does it say fastboot usb. If it does not, then there might be something wrong with your phone miniHDMI port, the computers USB port, or the cable. If it does then i must ask, in command prompt, did u navigate to the location of the adb.exe, fastboot.exe, AdbWinApi.dll (during bootlaoder unlock process, they should have asked for these files)??
Click to expand...
Click to collapse
I figured out the issue that it should be related to the driver installation was not successful in fastboot mode. I changed to a Windows 7 notebook then it is fine. And I was able to install the ROM successfully following your instruction. Thanks. :victory:
chpchai said:
I figured out the issue that it should be related to the driver installation was not successful in fastboot mode. I changed to a Windows 7 notebook then it is fine. And I was able to install the ROM successfully following your instruction. Thanks. :victory:
Click to expand...
Click to collapse
Alright. its great to know that you have resolved your problem. Congratulations on obtaining S-OFF :good:
Help on this step.
wong post .... oops
Thanks a lot for this instructions!
It's the first time i'm dealing with this things (got completely pissed of after that ****ty HTC ICS upgrade) and it went all right.
The only two places which were not completely clear to me and you might suppose to put more details:
1. Step 8 RUU should run in bootloader->fastboot
2. After step 9 (revolutionary) Recovery should be flashed again: either answer yes during that script execution or repeat step 4.
andropol said:
Thanks a lot for this instructions!
It's the first time i'm dealing with this things (got completely pissed of after that ****ty HTC ICS upgrade) and it went all right.
The only two places which were not completely clear to me and you might suppose to put more details:
1. Step 8 RUU should run in bootloader->fastboot
2. After step 9 (revolutionary) Recovery should be flashed again: either answer yes during that script execution or repeat step 4.
Click to expand...
Click to collapse
Alright thank you. I will update it.
excuse me guys. my device is rooted and s-on
if i make my device s-off ihave to root it again or not????
shmetal said:
excuse me guys. my device is rooted and s-on
if i make my device s-off ihave to root it again or not????
Click to expand...
Click to collapse
Nope. If you are already rooted, Start from where it says to run Nonverbose's script. This will fake the ID of your device to run the RUU to "upgrade" to HBOOT 1.13.0000. Then run revolutionary.
Thank you and its all going great for a noob here.
Thank you for the detailed process. I've done a Mimmi root and custom kernel and CM-7 mod before and for the Vivo that I got recently this was really useful as all the information was out there.
As far as this process goes, all went well except that when you do the RUU upgrade by fooling the upgrader that your Hboot is 1.00 or something and then it copies all those system files of stock 2.3 to the phone - somehow I lost the recovery and root (which I hassled about for some time and realized I can do the following :
1. Bootloader > Fastboot
2. USB connect
3. cmd.exe
4. fastboot flash recovery recovery-image.img
(ONCE AGAIN after the RUU) and everything seems to have worked like butter thereafter.
ROM's I could install after that:
1. MIUI roms (tried the MAUI WOWIE 2.9) Then tried the MIUI3.2.8 - worked well but little laggy - both work well except some apps wont install - very stable, battery lasted as good as stock, slightly better
2. Cyanogenmod 7.2 (hats off to these guys. worked most awesome but wanted to try so moved on) battery great, no bugs, plain simple fast.
3. Virtuous for - the Quattro. This was amazingly fast but there are bugs that need to be ironed out
here I installed 4EXT recovery and
4. Stock gingerbread with SENSE. - boring
5. Now running JellyTime 4.2.1. Not buggy, smooth, Battery seems to be doing well so far and call sound is okay and till now this one I liked a lot.
NOTE: Offline Dictation - Even after enabling google now and updating all google apps, there is no option do downlod offline speech recognition data in google voice typing settings........ If someone has got this to work I'd be glad to know.
I looked around and everyone seems to be suggesting that there is a check box within the google voice input options dialogue. But all I see is Language (automatic) and Block Offensive Words
Overall, seems like this is a great tutorial for anyone starting on their VIVO. Go Incredible! You've got my Flashing
I've been running CM 11 for a little more than a month and have been really enjoying it. So, I have no idea why I decided to download the MythTools and revert back to stock At&t. Doing so, I messed something up on my phone.
To start, I'm using Windows 7 64bit and when selecting option 1 (install ADB-fastboot-apkTools) I get the new cmd window that states "please select install button after new window is opened press any key to continue...." when I press any key the cmd window would just close. Hoping it would help, I then chose option 6 to update my Motorola drivers. When my browser window opened I got the ADB installer window and clicked install. It seemed to have installed fine. I then updated my moto drivers. Thinking I was all set I went for option 2 to flash the stock firmware which I had put in the firmware folder. With my phone in fastboot I started the process and it failed. Reading through the cmd prompts I had noticed it said something like 'you selected 2- instal cwm.img cannot load cwm.img' . I unplugged my phone and tried to restart it and it was stuck on the bootloader screen. I then restarted into recovery and my PhilZ recovery did start up. However it displays "E: could not mount /data to setup /data/media path!" . I was still able to go through the process of a clean re-install of CM 11 but am stuck on the startup splash screen for CM.
I definitely got myself in way too deep and am clueless on how to fix this. Would someone mind instructing me on what to try next? Many thanks in advance.
I am not sure if it would make a difference in your situation but I do everything for my phone on an x86 system. I have had issues with LG and Samsung phones in the past when trying things on an x64 computer.
ifixgse said:
I've been running CM 11 for a little more than a month and have been really enjoying it. So, I have no idea why I decided to download the MythTools and revert back to stock At&t. Doing so, I messed something up on my phone.
To start, I'm using Windows 7 64bit and when selecting option 1 (install ADB-fastboot-apkTools) I get the new cmd window that states "please select install button after new window is opened press any key to continue...." when I press any key the cmd window would just close. Hoping it would help, I then chose option 6 to update my Motorola drivers. When my browser window opened I got the ADB installer window and clicked install. It seemed to have installed fine. I then updated my moto drivers. Thinking I was all set I went for option 2 to flash the stock firmware which I had put in the firmware folder. With my phone in fastboot I started the process and it failed. Reading through the cmd prompts I had noticed it said something like 'you selected 2- instal cwm.img cannot load cwm.img' . I unplugged my phone and tried to restart it and it was stuck on the bootloader screen. I then restarted into recovery and my PhilZ recovery did start up. However it displays "E: could not mount /data to setup /data/media path!" . I was still able to go through the process of a clean re-install of CM 11 but am stuck on the startup splash screen for CM.
I definitely got myself in way too deep and am clueless on how to fix this. Would someone mind instructing me on what to try next? Many thanks in advance.
Click to expand...
Click to collapse
you said you are stuck on startup splash meaning bootloop? if it is you should try again with rsd lite.
else you may lose all your data in the memory but do a format media/data and sdcard, so that it can mount /data, it worked for me. then format system mount everyting and do a fresh install of any rom you can sideload or just have it in the sdcard.
I'm pretty sure I am doing something wrong with MythTools. When I select option 2 in the tool to install stock firmware the following happens,
- asks for fimware folder example and I select "N"
- asks if firmware files are finished copying.. I press enter and continue
-then it says "the system cannot find the path specified
the system cannot find the path specified
the system cannot find the path specified
'7z' is not recognized as an internal or external command
operable program or batch file
Are you ready to flash stock fimware...
at this point i stupidly hit enter and that was it with my phone. I'm guessing the tool could not locate the firmware .xml file for extracting and I have no idea why. The compressed folder is IN the firmware folder.
One other question with Mythtools, when installing the tools what path do you want them installed in? I did them in the same file the Myth tools are in.
ifixgse said:
I'm pretty sure I am doing something wrong with MythTools. When I select option 2 in the tool to install stock firmware the following happens,
- asks for fimware folder example and I select "N"
- asks if firmware files are finished copying.. I press enter and continue
-then it says "the system cannot find the path specified
the system cannot find the path specified
the system cannot find the path specified
'7z' is not recognized as an internal or external command
operable program or batch file
Are you ready to flash stock fimware...
at this point i stupidly hit enter and that was it with my phone. I'm guessing the tool could not locate the firmware .xml file for extracting and I have no idea why. The compressed folder is IN the firmware folder.
One other question with Mythtools, when installing the tools what path do you want them installed in? I did them in the same file the Myth tools are in.
Click to expand...
Click to collapse
Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock. Any questions don't hesitate to ask.
If this helps you hit that thanks button!
My HTC One M7 (UK O2) was prompting me to update to the latest operating system.
Eventually I succumbed and installed the update. The phone is stock although I had unlocked the bootloader in preparation for experimenting with new operating systems (I'm a noob but curious about experimenting).
After installing, the phone rebooted and wound up on a screen with a red exclamation mark in a picture of a phone.
Sometimes it boots into the white Android startup screen, then shuts down and goes throught the whole startup cycle in a loop
I can get it into bootloader mode but none of the options presented there such as factory reset seem to do anything.
I don't think it's a hardwear problem as it seems to be a direct result of trying to install the update.
I would send it in for a warranty repair but I think that as I have unlocked then relocked the bootloader and it shows a 'relocked' flag then that voids the warranty, is that right?
Any help to sort this mess out would be appreciated.
Thanks
jimbobly
During unlocking bootloader some files deleted and during update ota checks file integrity so file found missing and update stops
So basically you have to restore that files
Or RUU update can be found here
But it will delete your all data photo songs contact apps so backup them
http://forum.xda-developers.com/showthread.php?t=3053944
Thanks Yatindroid,
I don't think I can restore the files so I need to use the RUU. Can you tell me how to identify the correct file?
Thanks
jimbobly said:
Thanks Yatindroid,
I don't think I can restore the files so I need to use the RUU. Can you tell me how to identify the correct file?
Thanks
Click to expand...
Click to collapse
this file: https://www.androidfilehost.com/?fid=95916177934541097
instructions on how to flash it are at the top of the page in Yatindroid's link.
RUU
Seanie280672 said:
this file androidfilehost.com/?fid=95916177934541097
instructions on how to flash it are at the top of the page in Yatindroid's link.
Click to expand...
Click to collapse
This file seems to be corrupt/ can't be opened, downloaded it 3 times, can you link an alternative or explain the things that I need to consider in order to be able to choose an RUU myself.
Thanks
jimbobly said:
This file seems to be corrupt/ can't be opened, downloaded it 3 times, can you link an alternative or explain the things that I need to consider in order to be able to choose an RUU myself.
Thanks
Click to expand...
Click to collapse
This file is not corrupted, its encrypted, you can't open it. Want to know if its corrupted? MD5 value is what you want to check.
If the MD5 is ok then flash the zip.
md5: 399fa4bc8e841cc993a358e7c09fc4ca
alray said:
This file is not corrupted, its encrypted, you can't open it. Want to know if its corrupted? MD5 value is what you want to check.
If the MD5 is ok then flash the zip.
md5: 399fa4bc8e841cc993a358e7c09fc4ca
Click to expand...
Click to collapse
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?
jimbobly said:
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?
Click to expand...
Click to collapse
First is the Md5 good?
RUU
jimbobly said:
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?
Click to expand...
Click to collapse
Also, when I try to unpack the zip file I get the message that the compressed file is empty!
jimbobly said:
Also, when I try to unpack the zip file I get the message that the compressed file is empty!
Click to expand...
Click to collapse
To eliminate any doubt about corrupted file, the only thing you have to do is to check the md5 value. ANd like we already said, the file is encrypted you can't open an encrypted zip. Just check the md5 to confirm the file is good.
alray said:
To eliminate any doubt about corrupted file, the only thing you have to do is to check the md5 value. ANd like we already said, the file is encrypted you can't open an encrypted zip. Just check the md5 to confirm the file is good.
Click to expand...
Click to collapse
Unfortunately, this is a bit advanced for me. How can I do this?
jimbobly said:
Unfortunately, this is a bit advanced for me. How can I do this?
Click to expand...
Click to collapse
http://www.winmd5.com/
alray said:
http://www.winmd5.com/
Click to expand...
Click to collapse
OK, I checked the md5 with the tool and they match. But I still get the message 'preprocess file cannot open zip'.
How should I be handling the file, with the fastboot commands?
jimbobly said:
OK, I checked the md5 with the tool and they match. But I still get the message 'preprocess file cannot open zip'.
How should I be handling the file, with the fastboot commands?
Click to expand...
Click to collapse
you need learn flashing RUU zip
reboot your phone to fastboot mode (same as you posted pic )
setup adb folder find miniSDK HERE and Here
Download htc fastboot HERE copy it adb folder rename it fastboot.exe (rename old fastboot to other name)
open adb folder put your RUU zip there rename it RUU.zip
connect your phone with PC
your phone should be locked/relocked
at adb folder open CMD (shift + right click)
type command below
Code:
fastboot devices
(will show attached phone to PC match serial no)
Code:
fastboot oem rebootRUU
(reboot phone to flashing ruu mode)
Code:
fastboot flash zip RUU.zip
(wait it will take time 8-10 minutes it will show successfully at last if not repeat same command immediately)
Code:
fastboot reboot-bootloader
( it is last and important step of flashing)
now see new version showing at phone details
reboot to system
RUU
Thanks for taking the time to look at this Yatindroid.
I followed your instructions but there seems to be a problem with the RUU file.
When I execute the 'flash zip' command I get an 'unable to read zip message!
The file I have has been recommended by several people.
Am I handling this file incorrectly?
This is the file I am using. https://www.androidfilehost.com/?fid=95916177934541097
All I did was rename the file RUU.zip and move it to the ADB folder.
Thanks for the help.
jimbobly said:
Thanks for taking the time to look at this Yatindroid.
I followed your instructions but there seems to be a problem with the RUU file.
When I execute the 'flash zip' command I get an 'unable to read zip message!
The file I have has been recommended by several people.
Am I handling this file incorrectly?
This is the file I am using. https://www.androidfilehost.com/?fid=95916177934541097
All I did was rename the file RUU.zip and move it to the ADB folder.
Thanks for the help.
Click to expand...
Click to collapse
put RUU.zip in fastboot/adb folder
name should be RUU.zip not RUU.zip.zip
use htc fastboot rename that to fastboot
RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.
yatindroid said:
put RUU.zip in fastboot/adb folder
name should be RUU.zip not RUU.zip.zip
use htc fastboot rename that to fastboot
Click to expand...
Click to collapse
RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.
jimbobly said:
RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.
Click to expand...
Click to collapse
check md5
fastboot flash zip ( pressing tab will show files in fastboot folder press tab until you got ruu.zip )
Already checked the md5 and it's ok.
What is the best thing to do? Just try a new RUU?