Database Info

[Q] my phone is locked again, should i use htc dev?

Hello, my phone randomly just became locked (bootloader) and my recovery has disappeared. Should I use htc DEV to unlock it? I am s-off and my hboot is 1.17.0011.

No need. Just flash CWM or 4EXT with a PG58IMG through bootloader. You can do the same with your hboot.

GROGG88 said:
No need. Just flash CWM or 4EXT with a PG58IMG through bootloader. You can do the same with your hboot.
Click to expand...
Click to collapse
recoveyr manager didnt work and neither did through adb, on adb it said not allowed or something when i typed fastboot flash recovery recovery.img
Edit: I tried HTC DEV, i had used it before but now my bootloader is locked so i tried again. I got to the last stage and wrote fastboot get_oem_identifier_token or something and it just came up with error.
What can I DO!!!!

[Q] unroot htc wildfire s(asia_india version,s-on)

i have htc wildfire s.its asia_india version.and i unlock my bootloader through htcdev.and root it.but now i want to unroot it.i flash ruu euro version(build:2.13.401.2 and baseband:57.23a.35.3035H_7.53.39.03M) by flashy tool.
by this method:
http://forum.xda-developers.com/showthread.php?t=1467844
but still i cant get stock recovery.when i select recovery from hboot its opens clockwork mod recovery.
i tried to flash recovery.img but nothing work.
so how do i get my phone back as before rooting device.and regularly gets ota updates.
please help.

crossfire77 said:
i have htc wildfire s.its asia_india version.and i unlock my bootloader through htcdev.and root it.but now i want to unroot it.i flash ruu euro version(build:2.13.401.2 and baseband:57.23a.35.3035H_7.53.39.03M) by flashy tool.
by this method:
http://forum.xda-developers.com/showthread.php?t=1467844
but still i cant get stock recovery.when i select recovery from hboot its opens clockwork mod recovery.
i tried to flash recovery.img but nothing work.
so how do i get my phone back as before rooting device.and regularly gets ota updates.
please help.
Click to expand...
Click to collapse
What command did you use to flash recovery?
Make sure than when you flash a recovery through Fastboot, you use the following:
fastboot flash recovery recovery.img
The recovery must be in the same folder as fastboot/ADB
Let me know if you need any more help!

not using manual method
i didnt used manual method for install ruu.i just used flashy tool mentioned in given thread see it.
http://forum.xda-developers.com/showthread.php?t=1467356
but it just stock me euro ruu.but when i hboot n select recovery here still showing me clockwork mode.
so again i rooted my phone and installed clockwork mode and try to remove by
flash_image recovery /sdcard/recovery.img but it isnt work.(by terminal emulator)
i doing this because if once clockwork mode removed i can unroot and relock my bootloader and its same as before and i will have ota updates.
but nothing is work.
and see i found these three methods.please see them all and then tell which one is preffered i tried them all but cant remove clock work mode.
first one is here:
http://forum.xda-developers.com/showthread.php?t=1567628
and second is here:
http://androidforums.com/htc-wildfi...arvel-a510e-gsm-software-version-2-3-5-a.html
(in second method i dont use: Procedure 3: Flashing the ROM manually from a command prompt using fastboot)
and last one is here:
http://forum.xda-developers.com/showthread.php?t=1467844
it is fine.get ruu europe but still clockwork recovery mode.
so now tell me what should i do?
and there are no ruu asia_india.exe file so i have to use europe rom version coz its same as mine.

I'd go with the third method - it's the easiest, and you don't have to flash anything manually

done!!
hey thnx.i choose third but it wont work with my ruu.so i used your command with fastboot
fastboot flash recovery recovery.img
and its done..thanks it restored my wfs with factory state and able to update via fota.

crossfire77 said:
hey thnx.i choose third but it wont work with my ruu.so i used your command with fastboot
fastboot flash recovery recovery.img
and its done..thanks it restored my wfs with factory state and able to update via fota.
Click to expand...
Click to collapse
I'm glad it worked for you!
There is no substitute for 'manual' flashing in my eyes, it shows you every step and you can actually see whether it has worked or not Plus, it's a handy skill to have for when you change devices, or when there's no tools available
Enjoy!

stuck at teamwin screen

i have a rogers it was at 3.17 i unlocked the bootloader and then installed twrp now i cant get past that screen
what can i do i need my phone
thanks
p.s it was at 2.14 hboot also

babarnard said:
i have a rogers it was at 3.17 i unlocked the bootloader and then installed twrp now i cant get past that screen
what can i do i need my phone
thanks
p.s it was at 2.14 hboot also
Click to expand...
Click to collapse
what command did you run to flash twrp? "fastboot flash recovery <twrpfilename>.img" if you ran "fastboot flash boot <twrpfilename>.img" then you need to run "fastboot flash boot boot.img" to allow you to boot again then run the correct command "fastboot flash recovery <twrpfilename>.img" to flash recovery.

i used the hasoon 2000 aio kit if that means anything
thanks for your quick reply though

So is it just chilling at twrp curtain pull down? Can you navigate through twrp?

i can navigate through twrp but thats all i can do and i am lost now

babarnard said:
i used the hasoon 2000 aio kit if that means anything
thanks for your quick reply though
Click to expand...
Click to collapse
sorry i haven't used the kit, did you hit reboot system in twrp?

yes and i try reboot system and recovery and it still just goes to the teamwin and thats it

babarnard said:
yes and i try reboot system and recovery and it still just goes to the teamwin and thats it
Click to expand...
Click to collapse
i think recovery is flashed where boot is supposed to be, you need to flash boot.img from fastboot.

Reflash everything manually reflash recovery reflash boot.I'mg

i am new to this stuff so please be patient with me
how do i reflash manually
thanks

look at my first post and this post for the files http://forum.xda-developers.com/showpost.php?p=38217541&postcount=297

ok sorry but im confused i tried to reflash but i get nothing to happen its the same as before stuck on teamwin screen

so you confirmed flashing in fastboot recovery to recovery and boot to boot? if so, i would just fastboot oem lock then run ruu and start over without the kit this time. all you need to do afterwards is use ur token to reunlock, flash recovery in fastboot then copy rom to sdcard and flash, if you get booted into sense somehow turn off fast boot in power and turn on usb debugging in developer options then issue adb reboot bootoader or adb reboot recovery depending on where you are trying to go.

i dont have the ruu for rogers 3.17 though any idea where i can find this
thanks for your patience so far

hi guys i really hate to be such a pain but i need my phone back can anyone give me a idiots guide to getting it back working again i am still stuck at the teamwin screen or the fastboot screen cant go anywhere else
thanks in advance guys

babarnard said:
i dont have the ruu for rogers 3.17 though any idea where i can find this
thanks for your patience so far
Click to expand...
Click to collapse
http://spadacapa.blogspot.co.uk/2012/06/at-and-rogers-htc-one-x-lte-stock-ruu.html
AT&T HTC OneX
Android 4.1.1
ViperXL

how do i install it now that i downloaded it

Fastboot oem lock than run the ruu

really new to this what do i run the ruu with
thanks

No offense but that's simple computer knowledge... But exe files on the computer can be ran just double click on it and run it

[Q] HTC One Mini not booting up fully and no access to recovery

Hello,
My phone was updating and crashed. The phone turns on but only the HTC logo appears and then goes to a black screen. I can't fastboot into the device as it is not recognised. I can't access TWRP recovery any more and goes to a downloading screen and then restarts again. While in the bootloader the phone shows the following:
***TAMPERED***
*** RELOCKED***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.19.0000
RADIO-1.22.40e.00.07
OpenDSP-v19.2.0268.0927
OS-1.31.401.1
eMMC-boot 1024MB
Aug 7 2013, 17:37:54.0
Please help me, any help greatly appreciated!
Update:
The phone is working and has an update but it can not update on the device, is there a way i can get the downloaded OTA file on to my PC?

CoolAndroid1 said:
Hello,
My phone was updating and crashed. The phone turns on but only the HTC logo appears and then goes to a black screen. I can't fastboot into the device as it is not recognised. I can't access TWRP recovery any more and goes to a downloading screen and then restarts again. While in the bootloader the phone shows the following:
***TAMPERED***
*** RELOCKED***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.19.0000
RADIO-1.22.40e.00.07
OpenDSP-v19.2.0268.0927
OS-1.31.401.1
eMMC-boot 1024MB
Aug 7 2013, 17:37:54.0
Please help me, any help greatly appreciated!
Click to expand...
Click to collapse
Hi,
What do you want to flash stock sense 6...??
greets

shivasrage said:
Hi,
What do you want to flash stock sense 6...??
greets
Click to expand...
Click to collapse
Hello,
Yes I would like to go back to Sense 6 or any stock firmware preferably 4.4.2
Thanks

CoolAndroid1 said:
Hello,
Yes I would like to go back to Sense 6 or any stock firmware preferably 4.4.2
Thanks
Click to expand...
Click to collapse
Ok
First I recommend you to unlock your bootloader.
So if you are in bootloader and your device is not recognised I think it´s a driver issue.
If you allready checked it check it once more or update your tools (ADB, fastboot)
If nothing helps you could go to recovery and format your device (not only wipe format) should be clear that all data on device is lost.
Try different recoverys some people report that philz also works fine on M_4. (try install new rom option on philz).
DONT flash stock sense 6 ROM (wrong partition layout for this hboot) with this hboot rather take 5.5.
I´m sorry but without get connectet via ADB or fastboot I think there is no chance to get it working again.
greets

shivasrage said:
Ok
So if you are in bootloader and your device is not recognised I think it´s a driver issue.
If you allready checked it check it once more or update your tools (ADB, fastboot)
If nothing helps you could go to recovery and format your device (not only wipe format) should be clear that all data on device is lost.
Try different recoverys some people report that philz also works fine on M_4. (try install new rom option on philz).
DONT flash stock sense 6 ROM (wrong partition layout for this hboot) with this hboot rather take 5.5.
With out get connectet via ADB or fastboot I think there is no chance to get it working again.
greets
Click to expand...
Click to collapse
I can not access recovery to wipe anything out, on bootloader if i choose to wipe it attempts to load recovery which goes into download mode. The device comes up as "Device failed emulation" on Windows 8

CoolAndroid1 said:
I can not access recovery to wipe anything out, on bootloader if i choose to wipe it attempts to load recovery which goes into download mode. The device comes up as "Device failed emulation" on Windows 8
Click to expand...
Click to collapse
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets

Ok, I will use a win 7 pc and let you know

shivasrage said:
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets
Click to expand...
Click to collapse
After i fix my drivers issue what can i do afterwards?

shivasrage said:
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets
Click to expand...
Click to collapse
I can now do the fastboot command from CMD

CoolAndroid1 said:
After i fix my drivers issue what can i do afterwards?
Click to expand...
Click to collapse
If you have a connection via fastboot you first have to decide what ROM you want, search for the matching firmware.
for example flash the latest firmware for M_4... 4.09.401.3 from here (new partition layout for e.g. sense 6):
https://docs.google.com/file/d/0BzCFBBNdXagdcEMybkdBME5iUE0/edit
After that flash TWRP 2.7.1.1 or philz and format all you have to try one of this recoverys should work.
Next push or sideload a ROM via adb I recommend you one them:
http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921
You can decide what you want rooted or not it doesn´t matter.
After installing with succsess try to reboot that´s it.
greets

I encountered a similar issue when playing around with returning my device to stock. I flashed stock recovery, then re-locked my bootloader. What is the downloading screen you're seeing? Is it the stock recovery screen?
To fix, i had to change CID back to stock (for me that was, CWS__001)
Unlock bootloader again, using HTC unlock.bin (unlock.bin wouldn't work when i was on super cid)
Flash custom recovery TWRP 2.6.3.0 (I'm not sure if 2.7.1.1 works with the old partition layout, so i used this version until i had upgraded to hboot 2.22, then I flashed 2.7.1.1. This may be an unnecessary step, but it always worked for me)
Once twrp was working again...
Flash stock hboot 2.22 found in the dev section
Flash TWRP 2.7.1.1 (again, might be an unnecessary step)
Boot to recovery
From TWRP, adb push the sense 6 rom i wanted to flash (IC 3.07 in my case)
After the push completed, flash ROM and reboot and all was good
As you can see, the steps i took require that fastboot and adb drivers work flawlessly, especially when pushing ROM to the device using abd.
If any of this seems unfamiliar, then don't do these steps. Again, this is just what i did when i flashed stock recovery and re-locked bootloader with a ROM that wouldn't boot.

jollywhitefoot said:
I encountered a similar issue when playing around with returning my device to stock. I flashed stock recovery, then re-locked my bootloader. What is the downloading screen you're seeing? Is it the stock recovery screen?
To fix, i had to change CID back to stock (for me that was, CWS__001)
Unlock bootloader again, using HTC unlock.bin (unlock.bin wouldn't work when i was on super cid)
Flash custom recovery TWRP 2.6.3.0 (I'm not sure if 2.7.1.1 works with the old partition layout, so i used this version until i had upgraded to hboot 2.22, then I flashed 2.7.1.1. This may be an unnecessary step, but it always worked for me)
Once twrp was working again...
Flash stock hboot 2.22 found in the dev section
Flash TWRP 2.7.1.1 (again, might be an unnecessary step)
Boot to recovery
From TWRP, adb push the sense 6 rom i wanted to flash (IC 3.07 in my case)
After the push completed, flash ROM and reboot and all was good
As you can see, the steps i took require that fastboot and adb drivers work flawlessly, especially when pushing ROM to the device using abd.
If any of this seems unfamiliar, then don't do these steps. Again, this is just what i did when i flashed stock recovery and re-locked bootloader with a ROM that wouldn't boot.
Click to expand...
Click to collapse
I cant unlock my bootloader as its relocked and fails, I cant install TWRP either

CoolAndroid1 said:
I cant unlock my bootloader as its relocked and fails, I cant install TWRP either
Click to expand...
Click to collapse
Did you get fastboot working yet? Does "fastboot devices" show your device? You can't do anything until fastboot works...but I imagine it worked at some point, since you unlocked and re-locked your device.
You can't install recovery because your bootloader is locked. And you can't unlock your bootloader until you change your CID back to whatever it was when you created the unlock.bin file on the HTC website.
Are you getting this error when you attempt to unlock?
FAILED (remote: unlock token check failed)

jollywhitefoot said:
Did you get fastboot working yet? Does "fastboot devices" show your device? You can't do anything until fastboot works...but I imagine it worked at some point, since you unlocked and re-locked your device.
You can't install recovery because your bootloader is locked. And you can't unlock your bootloader until you change your CID back to whatever it was when you created the unlock.bin file on the HTC website.
Are you getting this error when you attempt to unlock?
FAILED (remote: unlock token check failed)
Click to expand...
Click to collapse
Hello,
I did have the error code above but i used FUU to flash back to stock and all is fine now!!

CoolAndroid1 said:
Hello,
I did have the error code above but i used FUU to flash back to stock and all is fine now!!
Click to expand...
Click to collapse
Cool. Did you use fuu from here?
http://forum.xda-developers.com/showthread.php?t=2659109

jollywhitefoot said:
Cool. Did you use fuu from here?
http://forum.xda-developers.com/showthread.php?t=2659109
Click to expand...
Click to collapse
Yep! Windows 8 sucks with drivers and didn't work so had to switch to a different laptop!

CoolAndroid1 said:
Yep! Windows 8 sucks with drivers and didn't work so had to switch to a different laptop!
Click to expand...
Click to collapse
That's what i had to do when i first tried to root my phone. I was on Windows 7, but it was an old install and had all kinds of software on it that might have been preventing usb from working (iTunes, HTC Sync, some other random software, etc.) Sometimes, I would even have trouble connecting an external HD!
I ended up installing a clean copy of XP on an old computer that i now use strictly for flashing stuff to my phone.

New problem
I have 4.3 on my HTC now and have received an update for 4.4.2, however when I try this it goes a quarter of the way then comes up with a red triangle and exclamation point. The device is still rooted somehow. Can you help me update?

CoolAndroid1 said:
New problem
I have 4.3 on my HTC now and have received an update for 4.4.2, however when I try this it goes a quarter of the way then comes up with a red triangle and exclamation point. The device is still rooted somehow. Can you help me update?
Click to expand...
Click to collapse
I don't think OTA will work on unlocked/tampered device with custom recovery.I think you need to run ruu.exe if one is available for you to get 100% stock before OTA will work again.

jollywhitefoot said:
I don't think OTA will work on unlocked/tampered device with custom recovery.I think you need to run ruu.exe if one is available for you to get 100% stock before OTA will work again.
Click to expand...
Click to collapse
Hello,
I found an FUU for 4.4 Kitkat on the link you posted earlier, It does all the necessary actions with no failures and completes with a Congrats screen but the firmware is the same?

[Q] Unlocked, reflashed, app ran into problem phone restarted and bricked?

Hi there,
Im still kinda a noob with android...
but i managed to unlock my htc sensation trough the steps @HTC,
changed the recovery, tried to flash a rom.
it failed due to my phone not being S-off. so i flashed it back :/
no problem there i thought just a rooted htc.
downloaded an app to remove bloat. and all seemed fine...
I was playing Clash of Clans, and it gave a message that the Google play services stopped and the phone rebooted.
when booted the lock screen was frozen, i pulled out the battery to find out my phone is unresponsive..
When i connect to windows 8, it cant recognize my phone at all
When i connect it to a charger i dont see the charging light.
and the worse thing is.. i cant get into the recovery.
any idea's what i can try?
i checked out the [unbrick] tread but i cant seem to figure out which "Package" i need and the links on the bottom of the page dont work when i click them
Thanks in advance
-Aline

At first you have not to be S-OFF in order to flash a rom.
Your rom will get installed just fine.You just need to flash the kernel of your rom manually through fastboot using the command fastboot flash boot boot.img.
What exactly do you mean by telling "so i flashed it back"?
Did you relocked your bootloader with fastboot oem lock and you flashed an RUU?
You said you are just rooted.If my theory was right you probably unlocked your bootloader again by flashing the unlock.bin and a cwm recovery and then you had to use a (Superuser , SuperSU zip).
The first time you unlocked your device was you using the same computer with windows 8?
If yes this is a problem.Check your device manager for unrecognised devices.Can you see the device?
Check this out.You can also check this.
(You can try with win7 or a linux destribution instead.)
Are you still able to boot into bootloader (hboot) using (Power)+(Vol-) Buttons?
If you have enabled usb-debugging and a working adb shell despite you are in a bootloop you can try:
Code:
adb shell
su ------>(If you don't see # instead of $)
reboot oem-78 -------> To get in RUU mode
or
reboot bootloader -------->(To reboot into hboot)
* reboot recovery could bring you to recovery *
If you can get into hboot or RUU mode give the command fastboot getvar all and copy-paste what it prints.

I know it was possible to flash with S-on,
thats what i tried and it failed (manually flashed the boot.img resulted in a bootloop)
so i flashed back to the "stock" rom.
resulting in a "normal" rooted device
since i've replaced my recovery and got root access
it never has been oem locked again.(still isnt)
i cant get into my bootloader/ruu mode. nor start up.
when i plug it into my computer (windows 8) it makes the sound as it does when you connect a device.
but in device manager it shows nothing, not even a yellow ! as it normally would if it can recognize a device.

aline1996 said:
I know it was possible to flash with S-on,
thats what i tried and it failed (manually flashed the boot.img resulted in a bootloop)
so i flashed back to the "stock" rom.
resulting in a "normal" rooted device
since i've replaced my recovery and got root access
it never has been oem locked again.(still isnt)
i cant get into my bootloader/ruu mode. nor start up.
when i plug it into my computer (windows 8) it makes the sound as it does when you connect a device.
but in device manager it shows nothing, not even a yellow ! as it normally would if it can recognize a device.
Click to expand...
Click to collapse
As you have not access to bootloader but your device is still seems to get connected i think you can only try HTC Unbricking Project.If the brickdetect.sh is not working you can try a different linux destribution.

Gatosbil said:
As you have not access to bootloader but your device is still seems to get connected i think you can only try HTC Unbricking Project.If the brickdetect.sh is not working you can try a different linux destribution.
Click to expand...
Click to collapse
Well, i just wonder which package i need, tried the links at the bottom of the post but those are no longer valid :/

aline1996 said:
Well, i just wonder which package i need, tried the links at the bottom of the post but those are no longer valid :/
Click to expand...
Click to collapse
Oups!I downloaded those packages some days before and I didn't see the links are broken now.
You can download them from the attachments here.
For Sensation and Sensation 4G

Gatosbil said:
Oups!I downloaded those packages some days before and I didn't see the links are broken now.
You can download them from the attachments here.
For Sensation and Sensation 4G
Click to expand...
Click to collapse
Well im afraid my phone is offically dead
this is what i get when i use ./brickdetect
[email protected]:/media/sdc$ ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
[email protected]:/media/sdc$
please tell me i did something wrong xD
edit:
after some digging in knoppix i did find this:
http://imgur.com/DR7T4QK