Database Info

[Q] Stock Recovery for sensation?

Was wondering if there is a way to flash back to stock recovery or if anyone can point me to a thread/link that has the stock recovery and i can install it. I am considering taking the phone back and getting the G2X (mainly cause of battery issues) Phone is 2 days old.
Any help would be appreciated thanks!

svoulis said:
Was wondering if there is a way to flash back to stock recovery or if anyone can point me to a thread/link that has the stock recovery and i can install it. I am considering taking the phone back and getting the G2X (mainly cause of battery issues) Phone is 2 days old.
Any help would be appreciated thanks!
Click to expand...
Click to collapse
If you are wanting to take the phone back, I would really go the whole way and completely restore the phone to stock (including S-ON). You can do this by installing ENG HBOOT, then issuing command fastboot oem writesecureflag 3, then installing the correct region stock RUU for your device. You will have complete stock then, not just recovery.
But if you want to just restore stock recovery, you could pull the recovery.img from an RUU and use fastboot flash recovery recovery.img

Do you happen to have any idea where I can find the eng hboot v 1.17.0008 and english rom version 1.29.531.2 I am having problems with the screen that are becoming unbearable and I feel its time to return it for a replacement
Thanks in advance for any input.
also just point me in the right direction if this has already been discussed.

noob question
prank1 said:
If you are wanting to take the phone back, I would really go the whole way and completely restore the phone to stock (including S-ON). You can do this by installing ENG HBOOT, then issuing command fastboot oem writesecureflag 3, then installing the correct region stock RUU for your device. You will have complete stock then, not just recovery.
But if you want to just restore stock recovery, you could pull the recovery.img from an RUU and use fastboot flash recovery recovery.img
Click to expand...
Click to collapse
One more quick question how do you issue the command fastboot oem writesecureflag 3 ? with the terminal? sorry for the noob question

happyendin21 said:
One more quick question how do you issue the command fastboot oem writesecureflag 3 ? with the terminal? sorry for the noob question
Click to expand...
Click to collapse
You need to issue it through command prompt, make sure you have Android SDK installed, there is a guide somewhere in the Android Development forum which explains how to do this in more detail, but basically you want to:
Download and install this: http://dl.google.com/android/installer_r12-windows.exe
If you need JDK then the installer will tell you and give you the link to download it
Then you need to copy all of the contents of the platform-tools to the tools folder, both of which can be located where you installed the Android SDK. Yes to overwrite if asked.
Put your phone in bootloader, then choose fastboot. Then connect via USB
Go to PC command prompt, then use command cd [tools folder]
e.g. mine would be cd C:\Program Files (x86)\Android\android-sdk\tools
Then you can issue fastboot commands
If you want to issue ADB commands, do the same except connect your phone whilst its running android, and choose 'charge only'
ENG S-OFF HBOOT download link:
http://api.viglink.com/api/click?fo...http://81.89.105.12/~bin4ry/hboot/PG58IMG.zip
1.29.531.2 Download Link
http://api.viglink.com/api/click?fo...ww.filefactory.com/file/cb7a...714_signed.exe

[Q] Fastboot Problem [SOLVED]

I have posted in the emergency thread but haven't got much out of it, sorry about the double post but I think this deserves its own thread.
When I plug my one S into the computer I see FASTBOOT AC. This should say FASTBOOT USB. The two devices wont recognise each others presence and the one s thinks the computer is a wall supply... fastboot devices returns no message at all. However in twrp 2.4.1.0 the devices communicate fine.
I tried to update cyanogenmod and got stuck in a bootloop because I can't flash the boot.img. I have tried reverting back to the old rom but to no avail.
Here are some of the things i have tried. If you can think of a way to achieve the same goal please let me know:
1) ensured drivers are up to date by installing and uninstalling the htc sync manager
2) someone pointed me in the way of s-off. apparently this would negate the need to manually flash a boot.img. However I need to use fastboot to do this so looked no further.
3) I have seen that TWRP doesnt require you to flash a boot.img if you are using version 1.3 or below (or something like that). However to alter the recovery i need guess what... fastboot
4) I saw a page on stack exchage titled 'Flash boot.img without using fastboot USB' which looks promising but i am not entirely confident with what I am doing and am scared I will make the situation worse. I can't work out exactly what it wants me to do. I would link except xda wont let me as I am a new user.
This is what my bootloader looks like on the fastboot screen
*** Tampered ***
*** Unlocked ***
VLE PUT SHIP S-ON RL
HBOOT-2.15.0000
RADIO1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012,17:57:-1
FASTBOOT AC
and then the usual stuff
Thanks for your time & thanks for help in advance

I have found a solution with some guidance from this thread
TWRP has a terminal emulator within it.
I first placed the boot.img in the sdcard and opened a terminal emulator here. I then had to find out what block the boot.img lives in
Code:
cat /proc/emmc
I found that the answer was /dev/block/mmcblk0p21
Then it was just a case of using dd
Code:
dd if=boot.img of=/dev/block/mmcblk0p21
The phone booted fine and it seems to have done the trick, fingers crossed!

pretty amazing, you were able to flash a boot.img from recovery while being s-on.
Good job.

[Q] Stuck in the red letters screen on my HTC One X

hello my friends, i need your help to fix my celphone, when i turned on the phone doesnt boot up always saty stuck in the screen with the red letters, i tried changing the kernel, i tried to install another ROM but always stuck in the same point, i wiped the cache, the system even the SD card and doesnt work,
Anyone can help me?
------Updated-----
according with some posts that i read i need to flash the RUU but i tried downloading the stock att ruu 2.20 but doesnt reconize any phone conected exists a way to flash directly over the TWRP?or maybe i missing something and because of that doesnt detect my celphone?

Reboot the phone and hold volume down while it's rebooting, this will take you to the bootloader, from there you can enter recovery and restore a backup or flash ROM.
What ROM were you on and what kernel did you flash?
Sent from my Evita

timmaaa said:
Reboot the phone and hold volume down while it's rebooting, this will take you to the bootloader, from there you can enter recovery and restore a backup or flash ROM.
What ROM were you on and what kernel did you flash?
Sent from my Evita
Click to expand...
Click to collapse
thanks for your help, i tried to flash the JB 4.22 plus sense 5 but i think my problem is the RUU because even if i flash the Rom still stuck in the same point when i tried to turn on the celphone, do you know how i can flash the RUU?

What are your bootloader details please, just the first five lines.
Sent from my Evita

timmaaa said:
What are your bootloader details please, just the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
Tampered
Unlocked
Evita put ship s-on RL
hboot- 1.14.0002
Radio-0.19as.32.09.11_2
openDSP-v29.1.0.45.0622
eMMC-boot

You're s-on so did you flash the boot.img via fastboot after flashing the ROM?
Sent from my Evita

timmaaa said:
You're s-on so did you flash the boot.img via fastboot after flashing the ROM?
Sent from my Evita
Click to expand...
Click to collapse
eehm nop, so how i do that? from where i can get the boot.img and how can flash via fastboot?
Sorry for my noob questions

The boot.img can be found in the root of the ROM zip, unzip it on your pc and you'll see it straight away. You then need to copy the boot.img into the folder where adb and fastboot are. Then open a command prompt from within that folder (shift + right click anywhere in that folder, select open command prompt here), put your phone into bootloader mode and connect it to the pc, then issue this command in the command prompt:
Code:
fastboot devices
It should return your device serial number, this confirms that you're connected properly. If it doesn't return the serial number you need to work out why. If it does return the serial number you can issue this command:
Code:
fastboot flash boot boot.img
Now you can enter recovery on your phone, flash the ROM, and reboot the phone. Now it should boot up.
Sent from my Evita

timmaaa said:
The boot.img can be found in the root of the ROM zip, unzip it on your pc and you'll see it straight away. You then need to copy the boot.img into the folder where adb and fastboot are. Then open a command prompt from within that folder (shift + right click anywhere in that folder, select open command prompt here), put your phone into bootloader mode and connect it to the pc, then issue this command in the command prompt:
Code:
fastboot devices
It should return your device serial number, this confirms that you're connected properly. If it doesn't return the serial number you need to work out why. If it does return the serial number you can issue this command:
Code:
fastboot flash boot boot.img
Now you can enter recovery on your phone, flash the ROM, and reboot the phone. Now it should boot up.
Sent from my Evita
Click to expand...
Click to collapse
Ok, let me try ill keep posted

It works !!!!!1
Thanks so much for your help now i will update the firmware with most recently one

fjej78 said:
It works !!!!!1
Thanks so much for your help now i will update the firmware with most recently one
Click to expand...
Click to collapse
Glad to see it worked
PS. If someone helps you on XDA, press the thanks button :thumbup:
Sent from my Evita

[Completed] error: cannot load unlock_code.bin

So I've read the other threads about this and tried pretty much everything what am I doing wrong?
1: type in "/k cd c:\" to switch from C:\Users\johan> to C:
2:C:\>adb\fastboot flash unlocktoken Unlock_code.bin (which gives error cannot open "Unlock_code.bin")
file is in C:adb along with:
adb.exe
adbwinapi.dll
adbwinusbapi.dll
fastboot
fastboot.exe
additional info:
the unlock file is only 1kb is this normal?
"adb devices" shows no devices but fastboot works don't know why
any of the above causing the problem?

I assume you're simply trying to unlock the bootloader? Could you post more details please about your device, e.g. manufacturer, exact model, then I'll be able to help you. Also can you show me what guide you're following and exactly what you're trying to accomplish?
(I'm assuming you're missing drivers which is why I'm asking you for this info).

HTCDreamOn said:
I assume you're simply trying to unlock the bootloader? Could you post more details please about your device, e.g. manufacturer, exact model, then I'll be able to help you. Also can you show me what guide you're following and exactly what you're trying to accomplish?
(I'm assuming you're missing drivers which is why I'm asking you for this info).
Click to expand...
Click to collapse
It's a HTC ONE S that I got and since I hadn't used android b4 I instead of doing a system update I updated some kind of CID that was on the phone which locked the phone in to "this build is for developers only..."
trying to bring it back to stock installing an RUU failed for some reason(the RUU being the one already in use since the phone is S-ON)
fastboot and adb drivers are installed, I can find my device in fastboot but not adb. enabling USB debugging should fix this but I can't enter the phone while it's looping and I've found no way of enabling it via cmd
this is what the phone shows while in boot:
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28 (RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release_301814_signed_2_4 is the RUU I tried running)
OpenDPS-v31.1.0.45.0815
eMMC-boot
Dec 14 2012. 17:10:57:-1
and correct I'm trying to unlock bootloader through htcdev then repeating the process and locking the loader, running the RUU again... if this doesn't work I guess I can go S-OFF (but then I need USB debugging) and picking any RUU see if that works
and prior to getting this phone I had never touched an android so I have 0 experience
I have downloaded the SDK and htc sync
tried following these guides:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
http://forum.xda-developers.com/showthread.php?t=1315947
and this is my original asking thread trying to get my phone back to stock:
http://forum.xda-developers.com/htc-one-s/help/help-purchased-dev-phone-accidently-t2813586

I am retarded
since I got this phone second hand I didn't know what had been done with it other than what I installed to cause my problems...
one of the things that had been done previously was unlocking bootloader.. hence the very obvious "Unlocked" in the boot menu.... sooo unlocking an unlocked bootloader was kinda redundant
tried oem locking the boot b4 but missed to specify where the files where (C:adb), lock worked and RUU installed without a hing!
thanks for your help!

[Q] HTC One X (ATT) No OS

Long story short, I had an issue with my HTC One X that I received from a friend. It would load up and then immediately restart about 15 seconds after getting to lock screen. I was just stuck in a boot loop.
So I decided to flash a new rom onto the phone, but neither I nor my friend had created a backup so now my OS is wiped.
I can boot into recovery mode, though. I'm not sure what the first screen is called, but it's the one with the skating androids. It tells me:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse
When I enter into recovery, it appears that I have TWRP v2.3.1.0.
In here, I cannot install any roms. They appear to fail. Installing says:
Zip Install Complete
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/sdcard/pac.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip '/sdcard/pac.zip'
Updating partition details...
Click to expand...
Click to collapse
Failed
Click to expand...
Click to collapse
I had read somewhere that I need to upgrade my TWRP in order to properly install roms, but at the current moment, running adb devices in a command prompt pointed at my adt bundle folder does not work. It just has a blank list.
Attached is a photo with what I think are the most relevant things I've downloaded/installed so far.
It does look like I can connect my phone to the computer via Mount USB Storage, but sideloader does not work since adb devices is blank.
Any thoughts?

kpxexpress said:
Long story short, I had an issue with my HTC One X that I received from a friend. It would load up and then immediately restart about 15 seconds after getting to lock screen. I was just stuck in a boot loop.
So I decided to flash a new rom onto the phone, but neither I nor my friend had created a backup so now my OS is wiped.
I can boot into recovery mode, though. I'm not sure what the first screen is called, but it's the one with the skating androids. It tells me:
When I enter into recovery, it appears that I have TWRP v2.3.1.0.
In here, I cannot install any roms. They appear to fail. Installing says:
I had read somewhere that I need to upgrade my TWRP in order to properly install roms, but at the current moment, running adb devices in a command prompt pointed at my adt bundle folder does not work. It just has a blank list.
Attached is a photo with what I think are the most relevant things I've downloaded/installed so far.
It does look like I can connect my phone to the computer via Mount USB Storage, but sideloader does not work since adb devices is blank.
Any thoughts?
Click to expand...
Click to collapse
The first screen with the skating Androids is your bootloader, FYI. Adb commands aren't used for flashing a recovery, fastboot commands are used. You do indeed need to update TWRP, the version you currently have installed isn't compatible with any current ROMs. Click the guide link in my signature, there are instructions on anything you need to do there.
Transmitted via Bacon

timmaaa said:
The first screen with the skating Androids is your bootloader, FYI. Adb commands aren't used for flashing a recovery, fastboot commands are used. You do indeed need to update TWRP, the version you currently have installed isn't compatible with any current ROMs. Click the guide link in my signature, there are instructions on anything you need to do there.
Transmitted via Bacon
Click to expand...
Click to collapse
I think I have my phone on Fastboot right now. I have the white screen that has FASTBOOT USB written on it with
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWERDOWN
Click to expand...
Click to collapse
underneath the control options. I've attached a picture below.
I Shift + Right Clicked to open command prompt in the folder with fastboot.exe and my recoveryfilename.img file.
In the command prompt, I enter in the command
Code:
fastboot flash recovery "recoveryfilename.img"
and it just stays on
Code:
< waiting for device >
I still can't figure out how to update my TWRP without an OS.

kpxexpress said:
I think I have my phone on Fastboot right now. I have the white screen that has FASTBOOT USB written on it with
underneath the control options. I've attached a picture below.
I Shift + Right Clicked to open command prompt in the folder with fastboot.exe and my recoveryfilename.img file.
In the command prompt, I enter in the command
Code:
fastboot flash recovery "recoveryfilename.img"
and it just stays on
Code:
< waiting for device >
I still can't figure out how to update my TWRP without an OS.
Click to expand...
Click to collapse
What OS are you running on your PC? Did adb/fastboot work at any point?

timmaaa said:
What OS are you running on your PC? Did adb/fastboot work at any point?
Click to expand...
Click to collapse
I'm running Windows 8.1 Pro. ADB worked once. I was able to get it to detect in recovery. ADB Devices would give me the customary string of numbers followed by "RECOVERY" and then I rebooted the phone for some reason and it stopped working. Oh, during that time I was also able to move stuff to the phone via ADB Sideload, but I would get pretty much the same errors when installing, which I later found out was because my TWRP was too old. I can't seem to get it to connect via ADB/Fastboot anymore. I can, however mount via TWRP.

kpxexpress said:
I'm running Windows 8.1 Pro. ADB worked once. I was able to get it to detect in recovery. ADB Devices would give me the customary string of numbers followed by "RECOVERY" and then I rebooted the phone for some reason and it stopped working. Oh, during that time I was also able to move stuff to the phone via ADB Sideload, but I would get pretty much the same errors when installing, which I later found out was because my TWRP was too old. I can't seem to get it to connect via ADB/Fastboot anymore. I can, however mount via TWRP.
Click to expand...
Click to collapse
There's your problem. Windows 8.1 isn't compatible with fastboot. You'll need to get access to a PC with a lower version of Windows so you can update TWRP.

timmaaa said:
There's your problem. Windows 8.1 isn't compatible with fastboot. You'll need to get access to a PC with a lower version of Windows so you can update TWRP.
Click to expand...
Click to collapse
Oh, really? Will 8 or 7 work?
I used a Windows 7 laptop and was able to update my TWRP to v2.7.0.8!
Seem to still be unable to detect devices via adb devices command.
Ok. Had to update my drivers.
I'm following your instructions on How To Install A ROM with TWRP Recovery, and now my issue is that it is saying
Code:
error flashing zip '/sdcard/pac.zip'
I've included a picture below.

kpxexpress said:
Oh, really? Will 8 or 7 work?
I used a Windows 7 laptop and was able to update my TWRP to v2.7.0.8!
Seem to still be unable to detect devices via adb devices command.
Ok. Had to update my drivers.
I'm following your instructions on How To Install A ROM with TWRP Recovery, and now my issue is that it is saying
Code:
error flashing zip '/sdcard/pac.zip'
I've included a picture below.
Click to expand...
Click to collapse
You're gonna need to get s-off so you can update your firmware. In order to get s-off you'll need to flash the Kickdroid ROM. Once you've flashed Kickdroid you can go to the Rumrunner s-off site and get s-off. Then follow the instructions in my guide thread to update your firmware.

timmaaa said:
You're gonna need to get s-off so you can update your firmware. In order to get s-off you'll need to flash the Kickdroid ROM. Once you've flashed Kickdroid you can go to the Rumrunner s-off site and get s-off. Then follow the instructions in my guide thread to update your firmware.
Click to expand...
Click to collapse
Alright, so I managed to get the Kickdroid ROM working! So right now I at least have a working phone that I can use! Thanks a TON for getting me this far.
Rumrunnner seems to not be working right for me. I'm in ADB recovery and can confirm an ADB connection, but it's still displaying
Code:
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
But it's a start. I'll have to make sure I'm following all instructions carefully.