Related
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
[Solved] Thank you all for helping me through, I finally, I can made it. See the last post of the actually summary of my own journey.
Without all of your value input, I will never made it.
imkr said:
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
Click to expand...
Click to collapse
At the first place, why and how did you flash an HTC HD rom to Desire S without even knowing it?! You should have know from the start that you should have taken precautions, and known that its an HTC HD. It should be PORTED first.
To answer,
Try flashing the recovery again on fastboot. Check my guides on how to on my sig (preferrably the second one). Then see if it works. If it did, flash the CORRECT rom.
I am a bit new with this sir, sorry need a bit detail explanation.
The point is I cannot get on the recovery mode, so when I read this guide (http://forum.xda-developers.com/showthread.php?t=1314629) I feel not clear enough
Can you give me a bit more clear process, sir?
imkr said:
I am a bit new with this sir, sorry need a bit detail explanation.
The point is I cannot get on the recovery mode, so when I read this guide (http://forum.xda-developers.com/showthread.php?t=1314629) I feel not clear enough
Can you give me a bit more clear process, sir?
Click to expand...
Click to collapse
What I'm trying to say is to flash the recovery again. 4ext recovery recommended. And start from there. Clear instructions were given on that thread on how to flash a recovery image via fastboot, and I believe I can't simplify it much further.
imkr said:
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
Click to expand...
Click to collapse
Mate don't worry, it happened to me many times.see this thread to know how I got a solution.forum.xda-developers.com/showthread.php?t=1281688
I used nandroid backup but you can flash another ROM
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
imkr said:
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
Click to expand...
Click to collapse
After you get the phone in FASTBOOT mode, open the cmd window and type:
FASTBOOT FLASH RECOVERY c:\recovery.img
I find it very worrying that some one who can claim to have made this mistake many times is prepared to offer advice!
nandroid backups, you now see the importance of taking them
Swyped from my Desire S using XDA Premium
imkr said:
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
Click to expand...
Click to collapse
The message you got is because you try to "run" in an windows command prompt an ".img" (image files). If you do so, windows try to launch the associated program with .img files. Obiviously this is the DVD burning software you have on your PC (the default windows one I think). That's why you get the error.
Now, you should pay attention very carefully to the instructions in that thread. You should NOT type "C:\recovery.img" but "fastboot flash recovery C:\recovery.img". That means you should already have installed "fastboot" application on your PC (or else you'll get a message say somthing like "'fastboot' is not recognized as an internal or external command, operable program or batch file." "fastboot" command is part of the Android SDK and should reside on your PC in the same place as "adb", that is in the "tools" (or "platform-tools" depending on what version of SDK you got) folder.
Simply, you first have to find where on your PC is installed the Android SDK. Browse with Explorer on your PC to there and look in the folders till you find the one in which "adb" and "fastboot" are. Keep the SHIFT key pressed and RIGHT click on that folder. From the menu that pops up, select "Open comand prompt here..."
Only now you can run the "fastboot" command...and if you have copied Recovery.img on the root of your C drive perform the command as instructed (an as I've wrote above). If Recovery.img is somwhere else on your pc than use it like this (after you perform steps 1-3 you've said):
fastboot flash recovery <folder_in_which_recovery.img_is stored>\recovery.img
Replace what I've wrote in italics above with the actual path to your recovery.img file.
After running this command, type the following one:
fastboot reboot-bootloader
You'll end up in 4EXT recovery from where you can flash the ROM of your will (hopefully one for Desire S this time)
Rapier said:
The message you got is because you try to "run" in an windows command prompt an ".img" (image files). If you do so, windows try to launch the associated program with .img files. Obiviously this is the DVD burning software you have on your PC (the default windows one I think). That's why you get the error.
Now, you should pay attention very carefully to the instructions in that thread. You should NOT type "C:\recovery.img" but "fastboot flash recovery C:\recovery.img". That means you should already have installed "fastboot" application on your PC (or else you'll get a message say somthing like "'fastboot' is not recognized as an internal or external command, operable program or batch file." "fastboot" command is part of the Android SDK and should reside on your PC in the same place as "adb", that is in the "tools" (or "platform-tools" depending on what version of SDK you got) folder.
Simply, you first have to find where on your PC is installed the Android SDK. Browse with Explorer on your PC to there and look in the folders till you find the one in which "adb" and "fastboot" are. Keep the SHIFT key pressed and RIGHT click on that folder. From the menu that pops up, select "Open comand prompt here..."
Only now you can run the "fastboot" command...and if you have copied Recovery.img on the root of your C drive perform the command as instructed (an as I've wrote above). If Recovery.img is somwhere else on your pc than use it like this (after you perform steps 1-3 you've said):
fastboot flash recovery <folder_in_which_recovery.img_is stored>\recovery.img
Replace what I've wrote in italics above with the actual path to your recovery.img file.
After running this command, type the following one:
fastboot reboot-bootloader
You'll end up in 4EXT recovery from where you can flash the ROM of your will (hopefully one for Desire S this time)
Click to expand...
Click to collapse
It's working for me now, thanks for your clear instructions:
I've type up the exact process that I experienced here
1. Get 4EXT
2. Extract to C:
3. Find android-win-tools
4. SHIFT + Right click to open cmd from here
5. Type 'fastboot flash recovery C:\recovery.img', then appeared:
sending 'recovery'... OKAY (keep looking around 10mn), another command appeared
writing 'recovery'...OKAY
6. fastboot reboot-bootloader
DONE!
I rooted a while back using revolutionary, and currently have hboot 6.98.1002.
I could really do with getting back to s-on and stock etc etc, but every guide I follow just doesn't seem to work.
I have searched, and searched and searched, but I'm a week down the line and still unable to change my hboot.
I'm at pains to start a new thread, but this thing is drving me bonkers.
I've read the instrcutions here for Alphareved:
http://forum.xda-developers.com/showthread.php?t=1236890
but typing the 'adb devices' in cmd but it just doesn't work. Is there some kind of zip file i should be extraxcting to get the sdk (i think it's called that?).
did u try this exe?
http://dl.google.com/android/installer_r16-windows.exe
edit: what is the output of "adb devices"?
-Download this file, it has the adb and fastboot files needed to proceed
-Extract the file to "c:\" so that the path looks like this C:\android-tools
-Install HTCDriver (Fastboot drivers) (should already be installed from revolutionary) but here's the link again
-Open cmd and type "cd/"
-then type "cd android-tools"
*To test whether you have set up all the files correctly and your phone is connected correctly you can do the following;
*Plug your phone in (when plugging in select CHARGE ONLY (i.e. leave on the home screen)
*In cmd type "adb" and press enter, it should show a list of commands, then type "fastboot"and press enter, it should also show a list of commands)
*If both these commands work you have extracted the files to the right place and have setup cmd right.
*then type "adb devices"
*Should show connected phone serial if not then try get the latest HTCdrivers
Flash the ENG HBoot
To flash the ENG HBoot you can use one of these methods;
1) Fastboot
-Place the .img file (extracted from PG88IMG.zip) in C:\android-tools
-Boot phone into fastboot
-Run command "fastboot flash hboot engHBOOToverARX.img" in CMD
2) Android Flasher
-Download from here
-Select phone, select Hboot .img (bootloader)
-Boot phone into fastboot and select FLASH
3) Updater file (PG88IMG.zip)
-Download the PG88IMG.zip (make sure is called that EXACTLY, not pg88img.zip or PG88IMG.zip.zip)
-Place file on your SD card root, and boot into HBoot, and follow onscreen instructions
4) adb shell (LAST LAST resort, one typo and you can brick your phone, do some reserch before doing it
-Place the hboot on your SD card and remane it to "hboot.img"
-Boot into recovery
-adb devices - Must show your serial
-adb shell
-su (it should show #, that means you have the right permission, if it shows $ afterwards you dont have permission)
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img (backup your current hboot)
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18 (flashes new hboot)
If you have any problems first check out this thread for answers
Install the RUU
How to check if downloaded RUU is compatible with your phone:
To avoid errors etc, you need to confirm your phone is unbranded, i.e. check if your CID matches the CID check list in the RUU you downloaded.
To do this Run the installer, then go to your Windows Temp Folder, sort the folder by date and pick the folder with the latest date, and locate the rom.zip file inside, open it up and open the android-info.txt file. Your CID should be in the list, if not then you need to create a GoldCardto install that RUU.
Here is a list of RUU's you can download for your phone [ROM]Shipped Desire S ROM Collection - xda-developers
Here and here are two great threads for HTC Desire S Guides
Thanks so much for the replies fellas. I'm away from my comp until this evening, but I'll relpy once I've tried these out.
This will work
hycaet said:
I rooted a while back using revolutionary, and currently have hboot 6.98.1002.
I could really do with getting back to s-on and stock etc etc, but every guide I follow just doesn't seem to work.
I have searched, and searched and searched, but I'm a week down the line and still unable to change my hboot.
I'm at pains to start a new thread, but this thing is drving me bonkers.
I've read the instrcutions here for Alphareved:
http://forum.xda-developers.com/showthread.php?t=1236890
but typing the 'adb devices' in cmd but it just doesn't work. Is there some kind of zip file i should be extraxcting to get the sdk (i think it's called that?).
Click to expand...
Click to collapse
I just did for my HTC Desire S (India).
This should help . Read
foX2delta said:
Flash the ENG HBoot
To flash the ENG HBoot you can use one of these methods;
1) Fastboot
-Place the .img file (extracted from PG88IMG.zip) in C:\android-tools
-Boot phone into fastboot
-Run command "fastboot flash hboot engHBOOToverARX.img" in CMD
Click to expand...
Click to collapse
This did it. Perfect. You're a star. This has bugged me for so long. You've made my bloody day. God bless and seasonal greetings.
foX2delta said:
Install the RUU
How to check if downloaded RUU is compatible with your phone:
To avoid errors etc, you need to confirm your phone is unbranded, i.e. check if your CID matches the CID check list in the RUU you downloaded.
To do this Run the installer, then go to your Windows Temp Folder, sort the folder by date and pick the folder with the latest date, and locate the rom.zip file inside, open it up and open the android-info.txt file. Your CID should be in the list, if not then you need to create a GoldCardto install that RUU.
Click to expand...
Click to collapse
How can i check my CID number to match with the RUU version?
terragady said:
How can i check my CID number to match with the RUU version?
Click to expand...
Click to collapse
Not sure of the command right now, Google it, like how to check you cId, then when you run the RUU go to your temp folder, I think there is a file called android.txt in the folder with the rom.zip is and it has the list.
Welcome !!!!!!!!!!!!!!!
I'm not taking credit for any files or programs here I just simply constructed a full guide on how to downgrade etc. for noobs and also people that is struggeling like I did .
Please be warned that you might damage your phone and also that your waranty voids after you unlocked your bootloader so I don't take any responsibility !!!!! But be assured if you follow my instructions you'll just be fine !!!!!!!!!!!!!!!!!!!!!!!!!!!
It took me 5 weeeeeeeekssss to find all of these and figure everything out so be greatfull !!!!
I'm going to tell you excacly how i did it !
First things first ....
Copy Cyanogen mod 7 android 2.3.3.zip to your sd card
Open "HTC DESIRE S - All in one toolkit" and run it.Remember you should be in bootloader for this ( volume down + power ) and the navigate with arrow keys to fastboot and select it using power button. Follow all the instructions in the lefthand corner on how to unlock your bootloader
Next you have to flash custom recovery . Look in the right hand corner and select TWRP 2.4.0.0 and let it flash.Sometimes it will say your phone is not detected just exit that command promt and the next command window will flash it.
Now you have to go to your recovery ... While in fastboot select bootloader and then recovery ... A htc logo will appear and about 10 sec from that an TWRP logo .
Go to
After all that is done go to install select zip and find the cyanogen mod 7... .zip you pasted earlier on your sd card and then flash it . wait untill it completes.
Now you have to reboot your phone look for reboot in the TWRP menu and select reboot then bootloader . Once your in bootloader again go to the folder where all my tools are located that I provided for you .
Go to android tools and press shift then right click and select open command window here .
copy and paste the following :
fastboot flash boot boot.img
After its completed select the reboot option using your arrow keys.
Wait until cyanogen mod 7 fully boots up
Now go to settings > applications > developer options and enable usb debugging
After that go to android tools folder again and open the command window again paste the following :
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
exit
exit
adb reboot-bootloader
After that the phone will be in bootloader again already in fastboot and then just type :
Fastboot oem lock
After that the phone will be in bootloader again already in fastboot
Now open the ruu I have provided for you and run it until it completes and whalah !!! You have hboot 0.98.0002
Now if you want to root it use the superoneclick app I provided and after that s-off also your bootloader with revolutionary i provided just follow the clear instructions(Your phone must be turned on and not in bootloader ! also remember to turn on usb debugging again !!!! )
after all of thos when you reboot into bootloader things will look like :
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02.11_M
eMMC-boot
(current date),(current time)
Thank you very much:good::good::good::good::good::good::good::good::good::good::good:
lY-AssassiN-Yl
files are all in one .zip file
link to files ........ mediafire.com/?ijic67sr55676um (just copy and paste in your browser)..........
Edited Version
I just wanted to post similar one but You did it for me. Anyway i edited it cause it was a mess Still I wonder will this work without GoldCard on any phone...
This is a simple guide for newcomers to Android. Please be warned that you might damage your phone and also that your waranty voids after you unlock your bootloader and the author doesn't take any responsibility for that. Still things shouldn't go wrong.
Link for the necessary files.
1. Copy Cyanogen mod 7 android 2.3.3.zip to your SD card.
2. Go here and click THANKS button for hasoon2000. This is his tool and he takes all credit for his hard work.
3. Now open "HTC DESIRE S - All in one toolkit" and double click on Desire S.exe.
4. Follow all the instructions in the left hand corner on how to unlock your bootloader
5. Now we are going to flash recovery. Look in the right hand corner, select TWRP 2.4.0.0 and click Flash Recovery button and follow the instructions.
6. It's time to go to the recovery. While in fastboot select bootloader and then recovery. A htc logo will appear and then TWRP should start.
7. When you're in the recovery MAKE BACKUP. Then go to Wipe section. Now wipe these four: Cache, Dalvik Cache, Factory Reset, System. After that go back, click Install and select Cyanogenmod 7.zip you placed on your SD card. Slide to flash and wait.
8. After flash is complete go back to TWRP main menu and select Reboot and then Bootloader.
9. When you're in bootloader go to the folder where all my tools are located.
Go to android tools and press shift then right click and select open command window here.
10. In the Command Window copy and paste the following :
fastboot flash boot boot.img
11. After it's completed select the reboot option using your arrow keys.
Wait until cyanogenmod 7 boots up. This is first boot so it may take a while. Don't get nervous.
12. When Cyanogenmod 7 will start go to Settings > Applications > Developer options. Enable USB Debugging
13. After that go to android tools folder again and open the command window and paste the following :
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
exit
exit
adb reboot-bootloader
14. When your phone will be in bootloader in fastboot USB mode type:
Fastboot oem lock
15. After that the phone will give you Warning. It's fine. Stay in bootloader in fastboot USB.
16. Open the RUU I have provided and run it until it completes flashing.
17. You have hboot 0.98.0002 now. Use the superoneclick app I provided.
18. After that run revolutionary tool and follow the instructions. After it's complete reboot into bootloader. Things should look like this:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02.11_M
eMMC-boot
(current date),(current time)
Big thanks to:
lY-AssassiN-Yl
hasoon2000
Thanks for this guide. I've seem to have run into an issue though...
11. After it's completed select the reboot option using your arrow keys.
Wait until cyanogenmod 7 boots up. This is first boot so it may take a while. Don't get nervous.
Click to expand...
Click to collapse
It been 20-30 minutes now, and still booting. Is it now time to get nervous?
warjar said:
Thanks for this guide. I've seem to have run into an issue though...
It been 20-30 minutes now, and still booting. Is it now time to get nervous?
Click to expand...
Click to collapse
Yes it's too long. Try connecting your device to PC and in command line (adb) type: adb reboot recovery.
If this doesn't work try Three button reset. Push power, volume up and down simultaneously. If this doesn't work too follow these steps
1. Connect phone to USB
2. Remove battery
3. Phone will still be running
4. Shutdown PC to cut the USB power
Now boot into recovery (hold vol down and click power). I'm sorry this is partially my fault. I just switched my brain off during writing this assuming this was right and n00b proof :silly:. It isn't. There is one more step before flashing Cyanogenmod that you may not be familiar with. When you manage to get into recovery go to Wipe section. Now wipe these four: Cache, Dalvik Cache, Factory Reset, System. After that flash (install) cyanogenmod again. This time it will boot. I'm updating guide right now and I'm sorry for your stress and inconvenience. If it works please report back.
VnnAmed said:
Yes it's too long. Try connecting your device to PC and in command line (adb) type: adb reboot recovery.
If this doesn't work try Three button reset. Push power, volume up and down simultaneously. If this doesn't work too follow these steps
1. Connect phone to USB
2. Remove battery
3. Phone will still be running
4. Shutdown PC to cut the USB power
Now boot into recovery (hold vol down and click power). I'm sorry this is partially my fault. I just switched my brain off during writing this assuming this was right and n00b proof :silly:. It isn't. There is one more step before flashing Cyanogenmod that you may not be familiar with. When you manage to get into recovery go to Wipe section. Now wipe these four: Cache, Dalvik Cache, Factory Reset, System. After that flash (install) cyanogenmod again. This time it will boot. I'm updating guide right now and I'm sorry for your stress and inconvenience. If it works please report back.
Click to expand...
Click to collapse
Thanks for the anwser, although I managed to solve this shortly after posting last nigth. Basicly I just removed the battery break the loop, wiped data and cache and reflashed.
Yes, I will have to ID myself as somewhat of a noob on the andoid-front and want to point out some parts of the guide that aint 100% noob-proof. A couple of times I was actually forced to think for myself. That's outrageous!
1. Place the folder "Desire_S_All-In-One_Kit_v2.0" at your C:/ root and run the .exe from there. Won't work baked into some other directory I believe.
2. Replace "adb push C:\downsaga\misc_version /data/local/tmp" with "adb push misc_version /data/local/tmp". Otherwise you will be looking in the wrong dir the way this rest of this guide is set up.
3. At step 11. If stuck on loop, follw these steps:
A. boot into recovery
B. wipe data/factory reset
C. wipe cache
D. go into partitions menu, and format boot and format system. (I skiped this part this time)
E. install rom zip from sdcard
F. reboot
4. At the end of step 13 there seem to be one "exit" to many. (this is just a trivial thing ofc)
5. Step 17: I had to run this one several times before it got propper rooted. What seem to make the difference was actually the in order i did things during the su test after the "successful" root. Go to your phone app-list >>superuser>>Preferences>>Automatic responce>>Allow befor you click away the warning on your computer.
I also ran all programs as admin, didnt test if it would work without, but it's generally a good idea with these things.
Remember, when you write for noobs you have to include the obvious
It's the first time i've touched this root-stuff so take this for what it is. It solved it for me, but may not always be the correct fix.
I've been wanting to root without using HTCdev, but resigned to this after beeing thrown around to some 10-15 differnet sites and guides, with missing software etc..
Now to figure out what ROM to use as this one had Sense 2.1, and why TiBu crashes when I attempt to remove bloatware. But that will have to be another story...
Thanks for the guide guys, and for providing all the software needed in one package, that's probably the most useful part for a newcomer =)
RUU
Hey guys,
got up to the RUU part and it says when updating rom from "13.10.401.8" to "1.31.206.1" Cannot be updated due to it being the wrong RUU, please find one for your phone
Also Im in the UK
Background :
Flashed it before to run primo s 4.1. Did not have the S-OFF
had ext4 ? then it changed TWRP
hmz12 said:
Hey guys,
got up to the RUU part and it says when updating rom from "13.10.401.8" to "1.31.206.1" Cannot be updated due to it being the wrong RUU, please find one for your phone
Also Im in the UK
Background :
Flashed it before to run primo s 4.1. Did not have the S-OFF
had ext4 ? then it changed TWRP
Click to expand...
Click to collapse
Wrong can mean two things:
1. Did you misc_version from a root/temproot environment? If you didn't have the right privileges, you can't do this step.
2. Your phone is Branded (to your carrier), you need to either choose a RUU that matches your carrier (see "+files" then RUU in my sig) or create a goldcard, which should let your phone ignore the carrier/region check.
VnnAmed said:
I just wanted to post similar one but You did it for me. Anyway i edited it cause it was a mess Still I wonder will this work without GoldCard on any phone...
This is a simple guide for newcomers to Android. Please be warned that you might damage your phone and also that your waranty voids after you unlock your bootloader and the author doesn't take any responsibility for that. Still things shouldn't go wrong.
Link for the necessary files.
1. Copy Cyanogen mod 7 android 2.3.3.zip to your SD card.
2. Go here and click THANKS button for hasoon2000. This is his tool and he takes all credit for his hard work.
3. Now open "HTC DESIRE S - All in one toolkit" and double click on Desire S.exe.
4. Follow all the instructions in the left hand corner on how to unlock your bootloader
5. Now we are going to flash recovery. Look in the right hand corner, select TWRP 2.4.0.0 and click Flash Recovery button and follow the instructions.
6. It's time to go to the recovery. While in fastboot select bootloader and then recovery. A htc logo will appear and then TWRP should start.
7. When you're in the recovery MAKE BACKUP. Then go to Wipe section. Now wipe these four: Cache, Dalvik Cache, Factory Reset, System. After that go back, click Install and select Cyanogenmod 7.zip you placed on your SD card. Slide to flash and wait.
8. After flash is complete go back to TWRP main menu and select Reboot and then Bootloader.
9. When you're in bootloader go to the folder where all my tools are located.
Go to android tools and press shift then right click and select open command window here.
10. In the Command Window copy and paste the following :
fastboot flash boot boot.img
11. After it's completed select the reboot option using your arrow keys.
Wait until cyanogenmod 7 boots up. This is first boot so it may take a while. Don't get nervous.
12. When Cyanogenmod 7 will start go to Settings > Applications > Developer options. Enable USB Debugging
13. After that go to android tools folder again and open the command window and paste the following :
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
exit
exit
adb reboot-bootloader
14. When your phone will be in bootloader in fastboot USB mode type:
Fastboot oem lock
15. After that the phone will give you Warning. It's fine. Stay in bootloader in fastboot USB.
16. Open the RUU I have provided and run it until it completes flashing.
17. You have hboot 0.98.0002 now. Use the superoneclick app I provided.
18. After that run revolutionary tool and follow the instructions. After it's complete reboot into bootloader. Things should look like this:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02.11_M
eMMC-boot
(current date),(current time)
Big thanks to:
lY-AssassiN-Yl
hasoon2000
Click to expand...
Click to collapse
Will this method works on ICS Desire S updated via ICS RUU and unlocked via HTC DEv
zeus.lny said:
Will this method works on ICS Desire S updated via ICS RUU and unlocked via HTC DEv
Click to expand...
Click to collapse
Sure. Actually it's how I did it
i am already running Andromadus AOSP 4.2.2 with S-On for for me to S-Off my phone i have to follow from step 12 of your guide as i already have 4Ext recovery installed, Also 1 thing.. Do i have to make a gold card to run the RUU of my regions to Downgrade my hboot ?
@paulie uk
hi, i figured i dont need s-off, just had to flash the boot.img
NOOB mistake
thanks anyways guys!!!
VnnAmed said:
13. After that go to android tools folder again and open the command window and paste the following :
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
exit
exit
adb reboot-bootloader
Click to expand...
Click to collapse
Hello all, everything works fine for me until this step: first, I was surprised to see the program is named "misctool" and not "misc_version" as specified in the example. Also, the option to use seems to be "w" and not "-s". Anyway, when I run "./misctool w 1.27.405.6" as root, I get "Error opening misc partition... must be run as root" twice... And I know I am running it as root since when I run "whoami" it returns "root"...
What am I doing wrong here..?
EDIT:
I was able to make it work using the commands using "adb shell" from the cmd prompt...
But now I am running into another problem, when I try to install the RUU I get :ERROR [131]: CUSTOMER ID ERROR
Apparently this occurs when you have the wrong RUU. How do I get the correct RUU for my device ?
Thanks in advance
how to get token ID?
Apperantly I got stuck on the 3rd step. How do I get token ID? What is the command and on which dir do I type it?
ghhhaaaa i can get past step 17. I realy need some help. i think comodo tought this files was a treath an placed them in quarantine
and i can get it to un quarantine them.. :crying: ( aahhh i needed to unlock bootloader again "crap.. now i need to figure out how i did that")
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RUU Update takes forever!
I've been sitting here for 15 min and the RUU updater are still "Sending" something -.-
Is this normal?
10x
htc desire s i'm s-off now 10x to you.:good:
great tutorial, but
great tutorial, thank you, but in the step
13. After that go to android tools folder again and open the command window and paste the following :
adb push C:\downsaga\misc_version /data/local/tmp
I get "device not found"
what is the problem? thank you
gezginsirin said:
Apperantly I got stuck on the 3rd step. How do I get token ID? What is the command and on which dir do I type it?
Click to expand...
Click to collapse
As far as i remember... U get token ID when u unlock your bootloader via HTCDev.. Go to HTCDev http://http://www.htcdev.com/bootloader/ select all other supported model and follow the steps a mentioned. u need to have a login account to do that.
maysider said:
great tutorial, thank you, but in the step
13. After that go to android tools folder again and open the command window and paste the following :
adb push C:\downsaga\misc_version /data/local/tmp
I get "device not found"
what is the problem? thank you
Click to expand...
Click to collapse
The error would usually appear if USB debugging isn't ticked or you don't have the right drivers.
Cheers
FromBeyondThisWorld
maysider said:
great tutorial, thank you, but in the step
13. After that go to android tools folder again and open the command window and paste the following :
adb push C:\downsaga\misc_version /data/local/tmp
I get "device not found"
what is the problem? thank you
Click to expand...
Click to collapse
Tick usb debugging in setting and re install htc sync which will install the required drivers also make sure u have android sdk installed and updated.
Sent from my Desire S using Tapatalk 4
Below is a cheat sheet I've made to help others keep the commands they'll need and general information organized and consolidated in one place... When I first started using Android years ago I kept one of these so I could refer to it if I forgot a command or a small piece of info and I thought I'd share one for the m8.
Make sure to check out the note at the end of this post regarding Dottat's updated ADB files. They prevent the need to flash ruu's twice as you'll see outlined in this post.
Edit Note:I highly recommend running ruu's via adb. It may look more intimidating than the exe or hboot methods,
but if they were to fail you'd see exactly where it failed in the running log. You can avoid having to wait
for an initial boot of the stock rom if your intentions are to wipe to stock and then install a custom
recovery and whatever your rom/rom(s) of choice are. I personally wipe my phone from recovery, then
wipe via the adb commands below, run the ruu, and then factory reset from stock recovery. I'll then
install a custom recovery and my rom of choice. It's up to you, but I've found this to be the quickest
method of insuring a full-wipe to stock and then into my rom of choice. The wiping above is redundant
and not necessary, but I'll do it if I've got a problem I simply cannot figure out. To be honest the ruu should
wipe everything for you and then running a factory reset w/stock recovery installed should fix any
4g/LTE issues. ***Verizon ADB Information***
--MOST but NOT ALL of this is Universal (Not Carrier Dependent)--
All commands beginning with "fastboot" must be performed at Bootloader
All commands beginning with ADB are performed from a phone that is in Rom
-You may skip the "adb reboot bootloader" step if you're already
at the bootloader
Firmware/RUU/Recovery instructions are available in their specific threads
*This is just a cheat sheet*
Basic ADB Commands:
Recovery Flashing: (TWRP Current Standard)
adb reboot bootloader
fastboot flash recovery recoveryimgname.img
Firmware Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
*you should be prompted to flash a second time here*
fastboot flash zip firmwarename.zip
fastboot reboot-bootloader
HBoot Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip hbootfilename.zip
RUU Commands
Wipe By ADB:*optional*(though a wipe is recommended either by recovery or adb)
adb reboot bootloader
fastboot oem task 28
fastboot oem task 29
Install RUU via ADB:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.zip
Install RUU via HBoot:
Rename ruu .zip to 0P6BIMG.zip and copy to root of external sdcard
Boot to your bootloader and enter hboot if you're in fastboot mode
Hboot should automatically read the RUU file and begin unpacking (progress bar at top right)
Follow onscreen prompts after it unpacks...
*sdcard must be formatted to fat32 to read RUU* formatting the sdcard through the android os
will accomplish this. It will mount vfat when you read it by computer or in twrp this is okay.
SELinux Terminal Commands:
1) Grant su level permissions via terminal by typing "su"
2) Enable SELinux status by typing "setenforce x" where x is the variable below
setenforce 0 =Permissive
setenforce 1 =Enforcing
GPE Install Instructions:
Begin with SuperCID:***May no longer be necessary***
1) Get current cid information via;
fastboot oem readcid
Write down your current cid reading
2) Change your cid to 11111111 via;
fastboot oem writecid 11111111
(check cid again with fastboot oem readcid to varify)
3) Reboot to the bootloader
4) Following the reboot back to the bootloader
verify your cid is 11111111
And Then Install Rom Via:
5)Wipe /data; /cache; /system; Dalvik
6)Format /system; /data; /cache to f2fs -optional *Must use Elite Kernel for GPE 5.1*
7)Install Rom
8)Reboot
Remove GPE:***these are just my recommendations***
1) Revert CID via fastboot oem writecid (your stock cid ex: fastboot oem writecid VZW__001
2) Wipe everything /data, /cache, /system, /dalvik
Click Here for dottat's firmware and ruu master collection
Below, on this first page, dottat has linked a file containing updated adb files to be used when installing his ruu's. They correct the issues many have had requiring two flashes of his ruu's. Full information available through his posts in this thread. You can either replace the files in his .zip with your current adb folders files, or use it (after unzipping) as an updated lightweight adb interface folder.
jcole20 said:
Below is a cheat sheet I've made to help others keep the commands they'll need and general information organized and consolidated in one place... When I first started using Android years ago I kept one of these so I could refer to it if I forgot a command or a small piece of info and I thought I'd share one for the m8.
***Verizon ADB Information***
--MOST but NOT ALL of this is Universal (Not Carrier Dependent)--
All commands beginning with "fastboot" must be performed at Bootloader
All commands beginning with ADB are performed from a phone that is in Rom
-You may skip the "adb reboot bootloader" step if you're already
at the bootloader
Firmware/RUU/Recovery instructions are available in their specific threads
*This is just a cheat sheet*
Basic ADB Commands:
Recovery Flashing: (TWRP Current Standard)
adb reboot bootloader
fastboot flash recovery recoveryimgname.img
Firmware Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
*you should be prompted to flash a second time here*
fastboot flash zip firmwarename.zip
fastboot reboot-bootloader
HBoot Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip hbootfilename.zip
RUU Commands
Wipe By ADB:*optional*
adb reboot bootloader
fastboot oem task 28
fastboot oem task 29
Install RUU via ADB:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.zip
Install RUU via HBoot:
Rename ruu .zip to 0P6BIMG.zip and copy to root of external sdcard
Boot to your bootloader and enter hboot if you're in fastboot mode
Hboot should automatically read the RUU file and begin unpacking (progress bar at top right)
Follow onscreen prompts after it unpacks...
*sdcard must be formatted to fat32 to read RUU* formatting the sdcard through the android os
will accomplish this. It will mount vfat when you read it by computer or in twrp this is okay.
SELinux Terminal Commands:
1) Grant su level permissions via terminal by typing "su"
2) Enable SELinux status by typing "setenforce x" where x is the variable below
setenforce 0 =Permissive
setenforce 1 =Enforcing
GPE Install Instructions:
Begin with SuperCID:***May no longer be necessary***
1) Get current cid information via;
fastboot oem readcid
Write down your current cid reading
2) Change your cid to 11111111 via;
fastboot oem writecid 11111111
(check cid again with fastboot oem readcid to varify)
3) Reboot to the bootloader
4) Following the reboot back to the bootloader
verify your cid is 11111111
And Then Install Rom Via:
5)Wipe /data; /cache; /system; Dalvik
6)Format /system; /data; /cache to f2fs -optional *Must use Elite Kernel for GPE 5.1*
7)Install Rom
8)Reboot
Remove GPE:***these are just my recommendations***
1) Revert CID via fastboot oem writecid (your stock cid ex: fastboot oem writecid VZW__001
2) Wipe everything /data, /cache, /system, /dalvik <-- Optional
*(suggested to use oem task commands)*
3) Format back to ext4 for everything if you changed to f2fs for any reason
4) Run ruu
If ruu doesn't work properly...
5) Run ruu a second time
Some General Tips
-When typing a command like "fastboot flash recovery recoveryname.img" you can use the TAB key to
autocomplete a name or file directory... (This is true in just about every operating systems
command line or terminal interface) ex: if trying to go to C:\Windows and you're already in the
C:\ directory you simply need type "cd C:\w" and hit TAB and it should automatically complete the
field. If you happen to have a directory that comes before Windows alphabetically like "C:\Warez"
(not likely) hit Tab again and it will cycle through directories alphabetically.
Another example is I have twrp-2.8.5 and twrp-2.8.6 in my adb directory. So if it autocompletes
to "twrp-2.8.5.img", I hit tab again it will change to "twrp-2.8.6.img". In some instances you can
use this autocomplete feature to issue commands ie when using an apk decompiler/recompiler tool.
Instead of typing mkdir you can simply autotab to the correct command after typing "m" or "mk" etc.
-If you use the up arrow on your keyboard in Terminal/Command Prompt it will cycle through previous commands.
Example: When flashing firmware after "fastboot flash zip firmware.zip" when prompted to flash a second time you
can just hit UP Arrow on your keyboard and it will automatically go to your previous entry.
-I keep the latest RUU for my device in my adb/android studio (*/platform-tools) directory already
named "0P6BIMG.zip". This is a good practice simply because it streamlines the whole process so you
don't have to wait as a rather large file copies to said directory. I also keep a copy of said RUU
in a folder on my external sd-card. I do this so that if my computer, for whatever reason, was not
able to read the phones storage I can use the file manager in recovery to move it to root and RUU.
-If you have TiTanium Backup Pro you can set it to automatically update your apps. I like to keep an
updated copy of my apps on my external sd-card, my computer, and in cloud via GoogleDrive. This
makes restoring apps from a backup a painless process as I always have them available to me.
-I also keep a running backup of everything important to me on my computer. I have a folder
I've set up specifically for my running backups. Inside said folder I have a copy of my favorite
roms, my music, all the firmware for our device, the HBoot.zip(s), my pictures, all available RUUs,
an MD5 checking program, GApps packages, TWRP backups, TWRP .img(s), TWRP themes, and any other
tweaks/flashable.zips I find important. I highly suggest everyone who doesn't do this make this a
practice. It truly helps a lot.
EDIT: If someone wants me to upload the above as a .txt file I will.
Click to expand...
Click to collapse
That would be great in .txt format.
aaronpw0621 said:
That would be great in .txt format.
Click to expand...
Click to collapse
When I get home (about an hour) I'll upload a .txt of the commands.
HTC One (M8) CM12.1.1
Edit: Okay downloadable .txt file is in OP
jcole20 said:
When I get home (about an hour) I'll upload a .txt of the commands.
HTC One (M8) CM12.1.1
Edit: Okay downloadable .txt file is in OP
Click to expand...
Click to collapse
:good: :good:
@jcole20 a lot of your fastboot reflashing can be removed by the use of the HTC_fastboot I have posted in various places. It does it automatically
dottat said:
@jcole20 a lot of your fastboot reflashing can be removed by the use of the HTC_fastboot I have posted in various places. It does it automatically
Click to expand...
Click to collapse
Thanks @dottat I didn't know. I've only had to reflash once. And that was the first time I ran your ruu (5.0.1). Following that initial hiccup, everytime after it's completed successfully on the first try.
I'll check into that and note it in op. I just wanted to consolidate all the commands we commonly use for people who have trouble remembering them.
HTC One (M8) CM12.1.1
Edit: oh I didn't know you were talking about your ruu.exe(s) ... Yeah, I'm so used to using adb for everything. I've got your exe for lollipop but I've only run it once. (Prior to my pm about something lingering after a ruu) ... I still haven't figured that out BTW. I'll make note in the op that your exes make the ruu adb info obsolete. Thank you again for all your help and work.
jcole20 said:
Thanks @dottat I didn't know. I've only had to reflash once. And that was the first time I ran your ruu (5.0.1). Following that initial hiccup, everytime after it's completed successfully on the first try.
I'll check into that and note it in op. I just wanted to consolidate all the commands we commonly use for people who have trouble remembering them.
HTC One (M8) CM12.1.1
Edit: oh I didn't know you were talking about your ruu.exe(s) ... Yeah, I'm so used to using adb for everything. I've got your exe for lollipop but I've only run it once. (Prior to my pm about something lingering after a ruu) ... I still haven't figured that out BTW. I'll make note in the op that your exes make the ruu adb info obsolete. Thank you again for all your help and work.
Click to expand...
Click to collapse
No that's not what I am talking about. Lol
Download this. Unzip it and you will see what I mean
https://www.androidfilehost.com/?fid=95916177934554784
dottat said:
No that's not what I am talking about. Lol
Download this. Unzip it and you will see what I mean
https://www.androidfilehost.com/?fid=95916177934554784
Click to expand...
Click to collapse
Lol... okay. Why isn't this in your 5.0.1 ruu thread? I wish I had known about this a couple of weeks ago... Thanks though. I did a quick google search for htc_fastboot and what came up was a question you asked someone in one of your ruu threads. I went to the op and all I saw was the exe and ruu.zip so I assumed you were talking about the .exe. Hah
jcole20 said:
Lol... okay. Why isn't this in your 5.0.1 ruu thread? I wish I had known about this a couple of weeks ago... Thanks though. I did a quick google search for htc_fastboot and what came up was a question you asked someone in one of your ruu threads. I went to the op and all I saw was the exe and ruu.zip so I assumed you were talking about the .exe. Hah
Click to expand...
Click to collapse
Have you read the stickied thread in general section?
dottat said:
Have you read the stickied thread in general section?
Click to expand...
Click to collapse
To be honest dottat, I've read so much with regards to this phone in the last month since I got it I don't remember everything that I've read through. I think, with regards to your ruu's, I've mainly used your posted threads in the Verizon Android Development section. I linked your ruu's in the OP now and I used the stickied master list here, but I've only had this phone for a month so I never needed a 4.4.4 ruu (hence not needing to find that master list). Your lollipop ruu has been bumped somewhat regularly so it's the only one I've ever really looked through except when googling something and your 4.4.4 ruu in the same section has come up.
jcole20 said:
To be honest dottat, I've read so much with regards to this phone in the last month since I got it I don't remember everything that I've read through. I think, with regards to your ruu's, I've mainly used your posted threads in the Verizon Android Development section. I linked your ruu's in the OP now and I used the stickied master list here, but I've only had this phone for a month so I never needed a 4.4.4 ruu (hence not needing to find that master list). Your lollipop ruu has been bumped somewhat regularly so it's the only one I've ever really looked through except when googling something and your 4.4.4 ruu in the same section has come up.
Click to expand...
Click to collapse
Here's the post....
http://forum.xda-developers.com/showthread.php?p=56890497
I just gave you the latest and greatest above. Its the awesome sauce man.
dottat said:
Here's the post....
http://forum.xda-developers.com/showthread.php?p=56890497
I just gave you the latest and greatest above. Its the awesome sauce man.
Click to expand...
Click to collapse
Thank you! Heh, I've got the .exes and .zips of your 4.4.4 and 5.0.1 ruus saved. I will probably ruu back to stock again using the above just because... I've still never figured out what broke audiofx for me even after reverting to stock via your ruus. It's been driving me nuts.
HTC One (M8) CM12.1.1
Edit: I'm thinking I flashed V4A via a .zip and didn't realize it, so audiofx wasn't working, it was working as the drivers for audiofx and audiofx was working as the gui for v4a. That's the only explanation I can think of, because your ruu's have been great and I know they are working to revert me completely to stock.
Edit 2: I went ahead and ran a ruu with your updated adb file(s). As usual went off without a hitch and everything seems perfect... booting into my rom of choice now. As usual everything is perfect dottat... thanks!
DISCLAMER: DOING THIS MIGHT RESET YOUR PHONE SO PLEASE BACKUP YOUR FILES BEFORE DOING THIS
now lets get started
download this tool (even if you already have adb and fastboot)*
https://forum.xda-developers.com/showthread.php?t=2317790
and go to your phone's settings then System > about phone and press on build number until it tells you: "you have developer options"
now go to System > developer options and enable android debugging and OEM Unlocking
now plug your phone into the pc and open the file: "cmd-here.exe" from the tool you downloaded
now type adb devices and it will probably tell you unauthorized, if it does then open your phone and click on accept
if you dont see any thing other than "list of devices attached" then download this
open it and input in, N and then Y so you dont install adb but you do install the phone's drivers
now type adb devices and you should see random numbers, if it says unauthorized just go back to when I said how to fix it
so now that everything is working type in the command prompt: adb reboot bootloader
now you should see a russian cat fixing a android machine with blue text: "FASTBOOT"
now type "fastboot oem unlock" and it should unlock your phone
now type "fastboot reboot"
--------------------------------------------------------
good, Now you have the bootloader unlocked
--------------------------------------------------------
If you are now put in the setup screen don't do it, just shut down your phone and then when it's shutdown hold on the power button and volume down buttons until you enter fastboot again
now go to this page: https://github.com/CosmicDan-Android/android_device_xiaomi_tissot/releases and download the latest boot only and regular versions
put them both in the adb (tool) folder and type in the command prompt: "fastboot boot boot-recovery.img"
if your phone doesnt do anything (doesn't do anything in the 30s after you input the command) then restart it and get it back in fastboot and type fastboot --set-active=b
and then type the previous command again, if that doesnt work then restart your phone back to fastboot again
and then type fastboot --set-active=a and the command "fastboot boot boot-recovery.img" and it should work
so now you will be in twrp, good!
type "adb push (regular twrp zip name, remember to put .zip at the end!) /sdcard/"
example:"adb push TWRP-Installer-3.2.1-with-Tissot-Manager-2.5.zip /sdcard/"
and then in your phone go to install and you should already be in /sdcard if not then go there and then tap on the zip and swipe on the thing
after it finishes installing go to reboot and then tap on recovery
--------------------------------------------
good now you have TWRP installed!
-------------------------------------------
Now its up to you, do you want to install only root or rom and root? its up to you
Root Only:
Download Magisk (you can also use SuperSU but I strongly recommend magisk)
put it in your adb (tool) folder and type "adb push (magisk's zip name, remember to put .zip at the end!) /sdcard/"
example:"adb push Magisk-v17.1.zip /sdcard/"
go to install, press on the zip file and swipe on the thing and click on restart system at the end
and congrats! you have root on your phone!
Rom:
If were talking about a treble rom then you should follow this guide: https://forum.xda-developers.com/mi-a1/how-to/treble-stock-to-treble-everything-to-t3793734 but if not you can continue using this one
download your favorite rom and download magisk (you can also use SuperSU but I strongly recommend magisk)
also go to opengapps.org choose arm64 and the android version your rom is and I recommend the nano variant
now in twrp tap on Wipe and Advanced Wipe and choose everything there (you dont have to choose micro SDcard tho) and swipe THIS WILL RESET YOUR PHONE AGAIN BUT YOU PROBABLY DONT CARE ABOUT THAT RIGHT NOW
now in the command prompt type: "adb push (rom zip name, remember to put .zip at the end!) /sdcard/"
example:"adb push RR-O-v6.1.0-20180709-Official /sdcard/"
and install it, some roms include gapps and other things in their installation for example: pixel experience. but most roms don't have that
so if you check the xda page and they say nothing about including opengapps in the rom then you should be able to fully follow the next steps.
type "adb push (magisk zip name, remember to put .zip at the end!) /sdcard/" and install it
then type "adb push (opengapps zip name, remember to put .zip at the end!) /sdcard/" and install it
now tap on reboot system and congrats! you just rooted and custom rom-ed your phone!
* "even if you already have adb and fastboot" the reason for this is because that link uses the newest version (or new enough) that is surprisingly not common in other places I downloaded adb and fastboot. the new version adds a new command that is used in the guide if you are experiencing a certain problem
I hope I helped you, if you have any questions or problems post them in the comments
a big THANK YOU
Months ago I rooted and installed a new ROM for first time in my life and, although I read another guides, with them I always break my phone, so I must flash and start again. And your guide, 4 months later, saved me again. I don't know why, really. Maybe because is super friendly. But thank you, again. The only thing I'll add is wtf to do when TWRP asks if install in slot a or b because that's the point I always mess it :'(
Thank you forever
vainille said:
The only thing I'll add is wtf to do when TWRP asks if install in slot a or b because that's the point I always mess it :'(
Click to expand...
Click to collapse
You mean when you flash the rom it asks you which slot to install to?