Database Info

[Q] Problems with Leedroid 2.0

Hi,
i came to the screen install form zip on sdcard
but then it starts installation
and shows : installation aborted
now i cant start the phone i always get tothis screen
with the red text this build is for ....
what can i do?
edit: now i am again there where i can install zip from sdcard, but now it doesnt recognize the sdcard. What can I do, because i the phoen does not take a microsdcard where I could put a new rom.
how can i get access to the internela storage now wihtour a os?

How did this happen ? Selecting a ROM to flash in recovery cant really cause so much damage if it fails. They usually fail because of a md5 mismatch or something.
try to mount the sd card and you can use adb to push files to it..
you could also try a full wipe..

I did several things. I rooted and unlocked the device
and now it does not boot.
Everytime I tired to flash leedroid or stock rom with choosing install form zip
installation get aborted.
I am only able to get into the boolloader and into the recovery.
how can i restore the phone?
wipe and recovery is not possible i always end in this screen
with the red text.
edit: i think i try to get into booloader and copy another file version with adb to the sd card and hope it was a download error.
but why the hell then did both the leedroid 'AND the stock rom fail?

did you flash the boot.img BEFORE flashing leedroids ROM ??
If not i suggest trying that, If that fails, Just run an RUU and start from the beginning

Thanks for the Idea,
my problem is that i cant get access to the memory wihtout a working rom
on it And now i also dont get into the recovery CWMS.
I thouzhg power+vol up would do it but it doesnt work
I think i destroyed my brand new phone.
but thanks for helping.

It's not broken.
Try Power + Vol. down. Possibly you need to retry this several times to get into the bootloader.

its not destroyed dont worry..
Run an RUU and all will be good again. Whats your CID ?

That is the problem I cannot put up software on the device
so how should i run a ruu?
Where can i get the CID from wihtout starting the phone?
I hope you have a trick how I can save the device.

angeloski said:
That is the problem I cannot put up software on the device
so how should i run a ruu?
Click to expand...
Click to collapse
You run it from your Windows desktop. Download your appropriate RUU here for example (as it takes a loooooong time).
Connect your phone to your computer via USB.
Double Click the RUU-file.
Answer the Questions and the update will start.
Remember: Your device will be reset to factory default and your data on sd card will be gone so.
Edit: You will still have to start it with power + vol. down buttons pressed (as far as I remember).

angeloski said:
That is the problem I cannot put up software on the device
so how should i run a ruu?
Where can i get the CID from wihtout starting the phone?
I hope you have a trick how I can save the device.
Click to expand...
Click to collapse
To get into the bootloader try this.
Press and hold volume down, then power. Hold both down together for 5 secs, let go of the power button then press the power button several times. This always works for me.
If this works then your phone is easy to fix.

Maybe you could try to reflash the boot.img from leedroid via fastboot.
Then flash a proper recovery.img via fastboot (I use clockworkmod)
As I heard you could then push the rom.zip via Adb the sdcard while in recovery. Last step would be install zip from sdcard.
Sent from my HTC One S using XDA

Have you installed supersu via install ZIP from sdcard? I think this needs go be installed before installing the Rom. I Don't Know it exactly. But like this it worked for me when coming from stock rom. Thats how it worked for me:
1. Unlock bootloader via HTCDev
2. flash recovery image via fastboot
3. Install SuperSU from zipfile in recovery
4. Flash boot.img from Leedroid
5. Install Leedroid from sdcard
So maybe you missed one of the steps.
Sent from my HTC One S using XDA

to get CID go into fastboot and type in cmd window ''fastboot getvar cid''
If your phone is branded, you will need that branded RUU, So i assume you will need o2 Germany RUU

Reflash recovery in fastboot, should give you access to sdcard back.
Sent from my HTC One S using xda premium

i did the same thing to my one s yesterday... followed all the steps for leedroid n got same frustration u have...
theres a nandroid file in the dev section... fastboot the boot.img and the recovery.img
ya phone WILL boot back up

ok guys ty for cheeering me up.
i wil try it with a ruu, where can i find a ruu for my htc one s.
the link in the previuos post ist offline.
i think it was 1.78.407.x when i looked the last time in my handy.
thanks

so my cid is
C:\Android\android-sdk\platform-tools>fastboot.exe getvar cid
cid: O2___102
finished. total time: 0.003s
Like i said it is a O2 i hope this helps finding the ruu

well check the Shipped ROM thread.. If its not there you can ask the OP Football if he has it or can get it..
Some RUU's cost $13 so if you know someone else who wants it, you could split the cost ?

so far, now am in the recovery flash but it is the same
count mount /sdcard
how can i put a file onto the sdcard when i have no access?
partionoing sdcard doesn't help
i was looking for this boot.img and recovery.img which was posted before
i dont find it can someone link me to it if he knows what was meant?
thanks
edit: i was desperate and tried:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
but the second order was not successful
ist there another way to fix this usb brick
and to get access to /sdcard
new edit: now i write also in the help thread (noob friendly) i hope that is ok.

Did you already try this
http://forum.xda-developers.com/showthread.php?t=1667929
Or this
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC One S using XDA

help my phone is not recognized by adb

question.. i was told i need a late firmware version in order to use ics roms so i decided to do it but idk why my device cant be found via cmd
i have s off
and hboot 1.27.1100
eMMC boot
i think i bricked my phone cause w.e. rom i install it just keeps looping. idk what to do?
there is no way my phone is being recognized by windows the device is not found and i cant even find a way to put it back to stock someone please help :/
at least i need to put s-on and remove recovery so i can send it back to t-mo but i cant do anything via adb. please im really willing to donate the person that helps me please

lileddy305 said:
question.. i was told i need a late firmware version in order to use ics roms so i decided to do it but idk why my device cant be found via cmd
i have s off
and hboot 1.27.1100
eMMC boot
i think i bricked my phone cause w.e. rom i install it just keeps looping. idk what to do?
there is no way my phone is being recognized by windows the device is not found and i cant even find a way to put it back to stock someone please help :/
at least i need to put s-on and remove recovery so i can send it back to t-mo but i cant do anything via adb. please im really willing to donate the person that helps me please
Click to expand...
Click to collapse
you can go to bootloader right ...then no worries ..you are NOT BRICKED ...
i presume you got GB rom running ..so thats why after flashing the latest firmware ..your device is bootlooping ...
no worries
if you can go to bootloader ...connect the device to pc from there (phone reads fastboot usb after this)
and in adb folder ...open command window there and ..type this "fastboot devices" without quotes.it should show your device
(remember adb wont work ..when in bootloader only fastboot does)
now type this "fastboot getvar all"
and post the complete output here ...except IMEI and SERIALNO
I'll guide you further

Have you tried starting your phone and trying to get into your bootloader so you can run fastboot? or even make it into recovery to restore a back up or different rom? Make sure you have the most updated driver for your phone. You can also put your SD card in another phone or in your computer and put the firmware version on the root of your card, put it in your phone, run your hboot and let it update by itself. Between these two options you should be able to resolve your problem.
Or because I posted like 5 seconds after the guy above... Do what he ^ said

ganeshp said:
you can go to bootloader right ...then no worries ..you are NOT BRICKED ...
i presume you got GB rom running ..so thats why after flashing the latest firmware ..your device is bootlooping ...
no worries
if you can go to bootloader ...connect the device to pc from there (phone reads fastboot usb after this)
and in adb folder ...open command window there and ..type this "fastboot devices" without quotes.it should show your device
(remember adb wont work ..when in bootloader only fastboot does)
now type this "fastboot getvar all"
and post the complete output here ...except IMEI and SERIALNO
I'll guide you further
Click to expand...
Click to collapse
hi, i did as you said but when i type adb devices it just goes blank. i get no device recognized but yea i am able to get to the bootloader

lileddy305 said:
hi, i did as you said but when i type adb devices it just goes blank. i get no device recognized but yea i am able to get to the bootloader
Click to expand...
Click to collapse
read my post again ..did i said adb devices ??? NO i said fastboot devices ..that too this needs to be done with phone in bootloader connected to pc

ganeshp said:
read my post again ..did i said adb devices ??? NO i said fastboot devices ..that too this needs to be done with phone in bootloader connected to pc
Click to expand...
Click to collapse
oh ok sorry i read wrong, ima do that right now.
btw when this works you better have a donate button lol
thank you so much for your help

ganeshp said:
you can go to bootloader right ...then no worries ..you are NOT BRICKED ...
i presume you got GB rom running ..so thats why after flashing the latest firmware ..your device is bootlooping ...
no worries
if you can go to bootloader ...connect the device to pc from there (phone reads fastboot usb after this)
and in adb folder ...open command window there and ..type this "fastboot devices" without quotes.it should show your device
(remember adb wont work ..when in bootloader only fastboot does)
now type this "fastboot getvar all"
and post the complete output here ...except IMEI and SERIALNO
I'll guide you further
Click to expand...
Click to collapse
ok so here are the results that i got

ok i understand your situation completely
you need to flash the 3.32 unlocked firmware
then you need to flash 4EXT recovery
then you need to go to recovery and then flahs the ROM
in order to do that ...this is the perfect guide
FLASH 3.32 FW and ROM
follow the post#1 and post #2 to the letter
then at the end you will come out fine
if you got any problems ..you can post back here ..I'll help you (or simply click the IRC HELP CHANNEL present in my signature and join that ..I'll be online there )
Also donation is not really required a simple thanks to my posts are enough ..but if you do feel like donating ..its much appreciated

Phone stuck in boot cycle

First time post and it's been a hell of a day. I need to figure out how to either sideload the factory ROM, load a 3rd party ROM, or actually factory reset my phone to stock.
I unlocked my bootloader and installed TWRP and SuperSU earlier in the day. I then wanted to try to load Cyanogen11, but there were issues with the load, it constantly failed. I made a backup before I did this, but when I attempted to load the backup, nothing happened, it would just continually boot to recovery.
I attempted a few other things, clearing caches, doing wipes, powering the phone off for 5~ minutes, etc. etc.
Nothing is working, I can't load any ROM now and phone is either stuck at a bootcycle or the HTC Splash screen (Aside from being able to load bootloader/CWP)

jdolbeer said:
First time post and it's been a hell of a day. I need to figure out how to either sideload the factory ROM, load a 3rd party ROM, or actually factory reset my phone to stock.
I unlocked my bootloader and installed TWRP and SuperSU earlier in the day. I then wanted to try to load Cyanogen11, but there were issues with the load, it constantly failed. I made a backup before I did this, but when I attempted to load the backup, nothing happened, it would just continually boot to recovery.
I attempted a few other things, clearing caches, doing wipes, powering the phone off for 5~ minutes, etc. etc.
Nothing is working, I can't load any ROM now and phone is either stuck at a bootcycle or the HTC Splash screen (Aside from being able to load bootloader/CWP)
Click to expand...
Click to collapse
Are you still having issues? If so, PM me and I'll help you out.....

Got everything sorted with the great help of Nelvin. I had previously gone to the twrp support IRC and after answering a few questions, they just stopped talking... Glad there are people out there still willing to help! He spent a good hour or so with me making sure everything was working.

Hey you two!
Did you solve your problem via PM, then maybe send me the log of it please.
I dont know exactly if we have the same problem, but i'll try to explain mine:
I wanted to put a ROM on my mini, because it is branded.
I unlocked the bootloader on the htc one mini and then put the twrp recovery on it. It seems to work.
Next i wanted to put super su on it, but I'm already stuck in a bootcircle, so i cant put any files onto the phone. I tried to move files with Qick ADB Pusher, but always when I try to send the file from PC(win7) to one mini it says "Opeartion Failed! Exit Code 1". I tried this when i was in Bootloader. When I am in Recovery ADB doesnt even recognize the phone via USB.
If there is more explanation needed, please feel free to ask.
Thank you for your help in advance!
Greetins,
just2lose.

just2lose said:
Hey you two!
Did you solve your problem via PM, then maybe send me the log of it please.
I dont know exactly if we have the same problem, but i'll try to explain mine:
I wanted to put a ROM on my mini, because it is branded.
I unlocked the bootloader on the htc one mini and then put the twrp recovery on it. It seems to work.
Next i wanted to put super su on it, but I'm already stuck in a bootcircle, so i cant put any files onto the phone. I tried to move files with Qick ADB Pusher, but always when I try to send the file from PC(win7) to one mini it says "Opeartion Failed! Exit Code 1". I tried this when i was in Bootloader. When I am in Recovery ADB doesnt even recognize the phone via USB.
If there is more explanation needed, please feel free to ask.
Thank you for your help in advance!
Greetins,
just2lose.
Click to expand...
Click to collapse
Hi, can you let me know: Which ROM you want to flash, if you have attempted to s-off, and that you can boot to recovery?
Also, i'd advise against using utilities like the "pusher", please download this http://d-h.st/qmi and create a directory called c:\adb\ - move your ROM and SuperSU zip files here and extract the adb_windows.zip file to the directory.....

I did not attempt s-off, just normal htc dev bootloader.
First i wanted to flash Magio R4, but then i was thinking about Stock Rom Sense 5.5, which tr1gg3r84 uploaded.
i created folder and moved rom there. i also extracted the adb_windows zip there. what to do next? (i just wanna ask, because im a little scared of totaly breaking the phone now)
Thanks for now!

just2lose said:
I did not attempt s-off, just normal htc dev bootloader.
First i wanted to flash Magio R4, but then i was thinking about Stock Rom Sense 5.5, which tr1gg3r84 uploaded.
i created folder and moved rom there. i also extracted the adb_windows zip there. what to do next? (i just wanna ask, because im a little scared of totaly breaking the phone now)
Thanks for now!
Click to expand...
Click to collapse
Boot to recovery, then
adb push therom.zip /sdcard/
adb push UPDATE-SuperSU.zip /sdcard/
Remember to extract the boot.img from the ROM zip file, and after flashing the ROM and SuperSU, boot to bootloader and FASTBOOT menu then:
fastboot flash boot boot.img

you mean to push with the quick ADB Pusher? but in this programm (on PC) it doesnt find the phone whilie it is is recovery boot.

just2lose said:
you mean to push with the quick ADB Pusher? but in this programm (on PC) it doesnt find the phone whilie it is is recovery boot.
Click to expand...
Click to collapse
No, use the adb binary from the download link I posted......
If your phone isn't found, check the windows device manager and verify that you have ADB Android device listed..... if not, download adb drivers for windows and install - then plug your phone back in.....
You are using TWRP 2.6.0.0 recovery image from here right? http://forum.xda-developers.com/showthread.php?t=2418938

the adb.exe just pops up the cmd console, showing a lot of commands for half a second and then its gone again.
the android device is listed on device manager.
no, i did not use this one(twrp). i used some explanation how to do it from another forum and another file.
should i use this one now? how exactly to do that? theres no explanation :/

Open a command prompt in Windows and cd to c:\adb
Then when your phone is in recovery, type the adb commands I posted earlier.....
Sent from my HTC One mini using XDA Premium 4 mobile app

terdingb all
cmd says that the command is wrong or misstyped
(im in c:/adb typing: adb push rom.zip /sdcard/)

Is your ROM zip file called rom.zip? Can you post a screenshot?
Sent from my HTC One mini using XDA Premium 4 mobile app

ok got it.
now the rom and the supersu.zip are on the phone.
i cleared cache and dalvik and flashed both files(Stock Sense 5.5 4.3 Rooted Odex/Deodex;UPDATE-SuperSU-v1.86; both zip files) and , after that i went into fastboot and tried (fastboot folder) "fastboot flash boot boot.img" but cmd only says "waiting for device"

just2lose said:
ok got it.
now the rom and the supersu.zip are on the phone.
i cleared cache and dalvik and flashed both files(Stock Sense 5.5 4.3 Rooted Odex/Deodex;UPDATE-SuperSU-v1.86; both zip files) and , after that i went into fastboot and tried (fastboot folder) "fastboot flash boot boot.img" but cmd only says "waiting for device"
Click to expand...
Click to collapse
Check device manager on your pc, most likely the adb driver device isn't listed - if not, reboot your pc and try again.... This has happened to me several times......

ok now it worked. writing boot and so on .. finished. total time: 2.717.
i shut it down and started the phone again.
now it almost made the starting sound. after 5 boot cycles it played the whole starting sound and also showed the second screen with the "o1ne" and "beatsaudio" on the bottom.
but thats it. boot cycling in a different way now .
seems like it just doesnt want to work.
i'm so sorry that I am bothering you for so long now..
another idea?
thanks again!
edit: im gonna go through everything again with magio rom r5...

ok got it now. thanks a lot dude!
i deleted the rom files now from the phone but still there is 9gb used on the phone. this is way to much, isnt it?
is there a safe method to clean the whole phone .. something like c:format ?
thanks ³

No problem dood.....
Download an app called diskusage from the store - start it and choose storage card.... Post a screenshot please!
Sent via a weather balloon towed by a flock of seagulls. That's how this messaging stuff works, right?

after the phone went out of battery, it was in a boot cycle again after loading and rebooting.
flashed super su.zip again, but it didnt help. stupid me didnt do a backup yet. so do i have to install the rom again and do all the configs from scretch?

What's your hboot status? Locked/unlocked, s-on/s-off etc
Also, did you do, or install anything before your phone powered off?
Sent from my HTC One mini using XDA Premium 4 mobile app

[Q] Bricked...Sorta....

Hi there, long time reader, possibly posted before but I cant remember my account name so I suppose I am a newbie.
1) Unlocked boot loader fine
2) Installed TWRP fine
3) Rooted fine
4) Installed CM11 and Gaaps
5) Restored all my apps from Titanium
Yaaaay ready to rock or so I thought. Only to be faced with "mobile network not available" so my intention was to flash another CM11 or other CM if it was possible to get it actually working to make phone calls. In my attempts to do this I cleared everything, so no OS. I can get into the bootloader and recovery mode still but that
ADB thing refuses to work. So as of now my PC cannot see the device to copy the rom files onto it.
Am I right in thinking if I get a USB OTG and put a rom on it, I can flash it from there??
I would settle for any custom rom at this stage that functions and doesnt have bloatware.
Failing that, would it be allowed here to ask for an image of a working htc one mini m4 to be uploaded somewhere that I can work with?
I wont be able to do anything until i get the USB OTG. Ive tried everything with ADB.
Your help would be so much appreciated.

hi,..
So first I´m not quite sure if an otg will work but it´s really worth to try it...
But after a (maybee) sucsessful flashing of a ROM via OTG there is no way around to get adb and fastboot to work.
Next I have to say is you should post some information about your phone.
h-boot Version
OS version
CID-Number if you know.
Only with this information sombody here can help you to find the right ROM.zip for flash trough recovery.
(if the firmware and the ROM do not match you are running in to multiple issues)
greets

Thank you
*** tampered ***
*** unlocked ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.24.40e.00.26
OpenDSP-V19.2.0268.0927
OS--
eMMC-BOOT 1024MB

So,.....
It would be very interessting what firmware was on your device..
But as we can see the bootloader shows "OS- " so I suppose with h-boot 2.21.0000 it was 3.10.xxx.x.
I ran in same Problem a few weeks ago.
Recovery write: Can´t mount sd card and can´t mount data
I formated data in TWRP-recovery....(formated not only wipe...deletes everything on device).
As far as I remember after that adb returns to work and I sideloaded a new system.
I recommend you to flash first a stock or stock "near" system then and try to get s-off (to get rid of your problems)
But your first goal is to get a working OS on your device and get adb to work
A little help could be:
In fastboot mode :
"fastboot erase cache"
then reflash TWRP 2.7.1.1 with "fastboot flash recovery recoveryname.img"
If this don´t work out the only way is USB-OTG cable.
greets
edit: honestly I think the CM11 thing is a story after getting device back to life...
an other question ....what do you get if you type in adb when device is in recovery mode: "adb devices"
If needed here you can find a working sense 5.5 rooted stock rom (should work with your frimware) to start with:
http://androidfiles.org/getdownload...Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip
could help also:
http://forum.xda-developers.com/htc-one-mini/general/adb-fastboot-device-try-t2800519

shivasrage said:
So,.....
It would be very interessting what firmware was on your device..
But as we can see the bootloader shows "OS- " so I suppose with h-boot 2.21.0000 it was 3.10.xxx.x.
I ran in same Problem a few weeks ago.
Recovery write: Can´t mount sd card and can´t mount data
I formated data in TWRP-recovery....(formated not only wipe...deletes everything on device).
As far as I remember after that adb returns to work and I sideloaded a new system.
I recommend you to flash first a stock or stock "near" system then and try to get s-off (to get rid of your problems)
But your first goal is to get a working OS on your device and get adb to work
A little help could be:
In fastboot mode :
"fastboot erase cache"
then reflash TWRP 2.7.1.1 with "fastboot flash recovery recoveryname.img"
If this don´t work out the only way is USB-OTG cable.
greets
edit: honestly I think the CM11 thing is a story after getting device back to life...
an other question ....what do you get if you type in adb when device is in recovery mode: "adb devices"
If needed here you can find a working sense 5.5 rooted stock rom (should work with your frimware) to start with:
http://androidfiles.org/getdownload...Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip
could help also:
http://forum.xda-developers.com/htc-one-mini/general/adb-fastboot-device-try-t2800519
Click to expand...
Click to collapse
Thanks. adb devices will sometimes show the serial number I think, adb push CMupdate.zip I get "cannot read cmupdate.zip"
Fastboot flash recoery recovery.img works.
I have ordered a USB OTG so hopefully by friday I will have it. Im not sure how to show you the firmware? I thought I listed everything needed?

No, its not your fault...
Normaly firmware ist listed in bootloader under OS-3.10.401.3 (for example).
But sometimes after a bad flash when the partitions are messed up or so OS dissapears from bootloader like we can see in your case.
I know from HTC ONE M_7 that there are also some releases of TWRP-recovery that make dissapear OS-Numer from bootloader
but I don´t know if this is similar to the HTC One Mini.
If you get a a serial nuber from adb in recovery mode.. adb should work.....
Do you know how to sideload a ROM via adb and have you allready tried it?
greets

shivasrage said:
So,.....
It would be very interessting what firmware was on your device..
But as we can see the bootloader shows "OS- " so I suppose with h-boot 2.21.0000 it was 3.10.xxx.x.
I ran in same Problem a few weeks ago.
Recovery write: Can´t mount sd card and can´t mount data
I formated data in TWRP-recovery....(formated not only wipe...deletes everything on device).
As far as I remember after that adb returns to work and I sideloaded a new system.
I recommend you to flash first a stock or stock "near" system then and try to get s-off (to get rid of your problems)
But your first goal is to get a working OS on your device and get adb to work
A little help could be:
In fastboot mode :
"fastboot erase cache"
then reflash TWRP 2.7.1.1 with "fastboot flash recovery recoveryname.img"
If this don´t work out the only way is USB-OTG cable.
greets
edit: honestly I think the CM11 thing is a story after getting device back to life...
an other question ....what do you get if you type in adb when device is in recovery mode: "adb devices"
If needed here you can find a working sense 5.5 rooted stock rom (should work with your frimware) to start with:
http://androidfiles.org/getdownload...Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip
could help also:
http://forum.xda-developers.com/htc-one-mini/general/adb-fastboot-device-try-t2800519
Click to expand...
Click to collapse
shivasrage said:
No, its not your fault...
Normaly firmware ist listed in bootloader under OS-3.10.401.3 (for example).
But sometimes after a bad flash when the partitions are messed up or so OS dissapears from bootloader like we can see in your case.
I know from HTC ONE M_7 that there are also some releases of TWRP-recovery that make dissapear OS-Numer from bootloader
but I don´t know if this is similar to the HTC One Mini.
If you get a a serial nuber from adb in recovery mode.. adb should work.....
Do you know how to sideload a ROM via adb and have you allready tried it?
greets
Click to expand...
Click to collapse
Yes side load does not work.

I have a serious headache now. I tried so many roms and none of them let me make or recieve calls. The 3g mobile data is working. Would this work if the IMEI was blocked?
I also tried to update the firmware and ran into problems error 155 and error 132. I am really close to giving up.

[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