Database Info

[Q] Bricked? By trying to get s-on

Dear xda-community,
as said in the title i dont know if i bricked my device by trying to get s-on again.
At first i read some threads here about getting s-on again and revert to stock.
I was s-off by revelutionary and flashed the ENG-hboot a few days ago (0.98.2000). After that i flashed the stock 1.47 rom and was trying to get s-on and stock again with the 1.47 RUU. I read that if i have the ENG-hboot i can run the RUU and then i get back to stock and s-on. But after i was running the RUU, i get to the bootloader again (on the phone). In the header stands now "*** Security Warning ***" and i'm s-on again like i want it with hboot 0.98.0002.
But the problem is that i cant get out of the bootloader, i can only acsses fastboot and the bootloader. If i click 'recovery', 'reboot' or anything else it only restarts the bootloader. I cant even turn the phone off, only with pulling the battery :/
So i'm stucked in the hboot 0.98.0002 with s-on and i dont know what i can do now or if i bricked my desire s permanently
Can anyone help me please?

are you sure that you have used the right RUU?

amidabuddha said:
are you sure that you have used the right RUU?
Click to expand...
Click to collapse
yes, i used the htc_saga_europe... 1.47 and im on a unbranded phone, so this is the right, isnt it?

Jahai said:
yes, i used the htc_saga_europe... 1.47 and im on a unbranded phone, so this is the right, isnt it?
Click to expand...
Click to collapse
It should be if you bought it in Europe. What happens when you try the RUU again? You should do this when "FASTBOOT USB" is written on your phone screen.

amidabuddha said:
It should be if you bought it in Europe. What happens when you try the RUU again?
Click to expand...
Click to collapse
yes, i bought and use it in germany. if i try it again it get aborted after receiving the information from the phone and tells me something about a error 140: bootloader error and in the manuel isnt an entry for error 140 :S

Jahai said:
yes, i bought and use it in germany. if i try it again it get aborted after receiving the information from the phone and tells me something about a error 140: bootloader error and in the manuel isnt an entry for error 140 :S
Click to expand...
Click to collapse
Ok there is what you can do:
run RUU without a connected phone. Let the screen open. Go to WIndows Explorer, C drive and type in the search box : rom.zip. When you find it copy it to another place and close the RUU window.
Then extract from the rom.zip these images: system.img, boot_signed.img, recovery_signed.img
If you do not have fastboot command use the Guide in my signature. Then in cmd on your PC with phone in "fastboot usb" mode type:
Code:
fastboot flash system {path to the file}\system.img
fastboot flash boot {path to the file}\boot_signed.img
fastboot flash recovery {path to the file}\recovery_signed.img
where {patho to the file}\ should be replaced with the the actual path to the file from your Windows Explorer (like C:\android\images)
then, if the flashing is successful try to reboot to OS (wait several minutes on the white screen it can take some time to load)
This solution is taken from here, credits to degit

amidabuddha said:
Ok there is what you can do:
run RUU without a connected phone. Let the screen open. Go to WIndows Explorer, C drive and type in the search box : rom.zip. When you find it copy it to another place and close the RUU window.
Then extract from the rom.zip these images: system.img, boot_signed.img, recovery_signed.img
If you do not have fastboot command use the Guide in my signature. Then in cmd on your PC with phone in "fastboot usb" mode type:
Code:
fastboot flash system {path to the file}\system.img
fastboot flash boot {path to the file}\boot_signed.img
fastboot flash recovery {path to the file}\recovery_signed.img
where {patho to the file}\ should be replaced with the the actual path to the file from your Windows Explorer (like C:\android\images)
then, if the flashing is successful try to reboot to OS (wait several minutes on the white screen it can take some time to load)
This solution is taken from here, credits to degit
Click to expand...
Click to collapse
thank you for your help!
i will try that and report back in a few minutes

hm
i cant get it to work in this way :/
if i write fastboot flash system C:\android-tools\system.img
it tells me:
"sending 'system' (571388 KB)...
OKAY [93.130s]
writing 'system'...
(bootloader) signature cheking...
FAILED (remote: signature verify fail)
finished. total time: 166.095s"
its the same with boot_signed.img and recovery_signed.img

if i try fastboot getvar version-main i get : 11.10.401.4
think there is a typo, shouldnt it be 2.10.401.4? could it be this and if yes how could i change it?

So you problem maybe sounds the same, but it is not.
Try
Code:
fastboot oem rebootRUU
Your phone will reboot to a black screen with silver HTC logo. Then run the RUU.
Other options is to go to the repair centre and tell them that this happened during OTA update.
Sent from my HTC Desire S using Tapatalk

Jahai said:
if i try fastboot getvar version-main i get : 11.10.401.4
think there is a typo, shouldnt it be 2.10.401.4? could it be this and if yes how could i change it?
Click to expand...
Click to collapse
Hmm that's new. Have you flashed a new radio recently? Anyway try the latest RUU 2.10.401.8.
Sent from my HTC Desire S using Tapatalk

amidabuddha said:
Hmm that's new. Have you flashed a new radio recently? Anyway try the latest RUU 2.10.401.8.
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
will try it with that. since now i tried it until 2.10.401.4
Edit: it took me ages to download that ruu from filefacrtory :/

i got the same error 140 with the last 2.10.401.8 RUU
looks like it is stucked in that bootloader for ever

Jahai said:
i got the same error 140 with the last 2.10.401.8 RUU
looks like it is stucked in that bootloader for ever
Click to expand...
Click to collapse
Go to repair center and say that the OTA update did this (it is the same as RUU) They should repair it for free
Sent from my HTC Desire S using Tapatalk

maybe there is any way to get s-off from fastboot or bootloader?

got to new hboot with this instruction: http://forum.xda-developers.com/showpost.php?p=20850548&postcount=22
managed to get the unlocktoken from htcdev but if i flash it everything themes fine, but i cant choose the option yes (unlock bootloader).
if i choose "no" and press the power button it reboots like it should but if i choose "yes" and press the power button nothing happens. i can still choose between the options but nothing happens :/
anyone know how i can get it working to unlock this bootloader and flash a custom recovery?

[Q] My desire s wont boot, ruu error 170

I tried to downgrade my desire s so i could s-off and root, using these guides
http://androidforums.com/desire-s-all-things-root/438830-guide-how-root-desire-s.html
http://forum.xda-developers.com/showthread.php?t=1399331
However when running the RUU, and i used the correct europe wwe version, it encountered the 170 usb error after rebooting, I tried running it again but wouldn't connect, so now my phone when it boots gets stuck on on the white splash logo, but I can enter HBOOT, is there anyway to get my phone back? all help will be much appreciated
Thanks

Try this - http://androidforums.com/incredible-tips-tricks/161463-ruu-error-170-171-solution-windows-7-a.html

those instructions still say that i need to be able to use the device to put it into HTC sync mode, however I don't get anywhere near that when booting. I'll still try it tho, but will the RUU still find it in HBOOT mode?

i had same problem..
see this.......http://forum.xda-developers.com/showthread.php?t=1467351&page=2 and follow FRAKEARTH reply only...remaining u ignore...
do oem lock an drun your RUU make sure that your RUU is fine and USB cable too...as i had a cable with shield disconnected i could able to charge but gave lot of trouble...
Paste the error u get..

thanks for the reply
one question though, i dont have this fastboot, only the adb, is there a guide to get it, im not used to the desire s, have had a desire original until now, and also booting into fastboot mode, how is that done on the s?
thanks

@tht13
To start fastboot, (boot into hboot (power+vol down) then plug phone in "HBoot USB plug" shows once phone is plugged in and press the power button (fastboot is highlighted by default) then it says "Fastboot USB")
Then RUN the command "fastboot oem lock"
If that doesn't work run the command (assuming you have your fastboot set up on the PC right) "fastboot getvar all" and paste the results (removing wout serial/imei)
Search how to setup adb/fastboot on the PC

Help Required - Stuck and splash

Greetings.
This is a long (and sad) story, take a breath..
Me and my wife both have Sensation for over two years.
Mine is Revolutionized s-off etc for a very *VERY* long time...
Her Sensi was stock till some stock apps drove her mad and a couple of months back I got it HTC dev unlocked, with 4ext, but JB method for s-off (with the wire trick) was giving me a hard time, so I just kept it s-on and tmp rooted, killing some stock apps.
Now the mess begins.
After some complaints that it's slow and gets stuck, I wanted to add some nice kernel to the pack - Sebastian's.
Since it's s-on, I picked "SmartFlash" BUT completely forgot about USB-Debugging...
So flashing the kernel made a whole mess, and it's stuck on splash. Also fastboot-usb is impossible as the usb-debugging is off.
I know.. I know.. RUU right?
I'm on Linux - which makes running RUUs virtually impossible...
Nonetheless, I extracted the rom.zip out of an ruu_pyramid_le_ics_35_s_htc_asia_wwe_3.32.707.110_r2_radio_11.69a.3504.00u_11.23.3504.07_m2_release_254511_signed.exe I had around, renamed it PG58IMG.zip - and with all the joy put it on the root of the SDCard.
The phone's CID is HTC__044 and it matches the one in the RUU rom (asia wwe).
But.. hboot, while taking its time to figure out what that PG58IMG file contains.. does nothing at all once it process it.
Current situation - I restored my wife's backup on my phone, and gave it to her, leaving me with.. a semi-brick.
I could not find an RUU for 3.33.707.51 which was the version on the phone prior to this fiesco, if you know where to get it - please let me know..
Other than that I know this is solvable, as I am able to get into recovery and hboot, but how?
Phone details:
HBoot 1.27.0000
CID HTC__044
4ext recovery touch
Firmware 3.33.707.51
Radio 11.76A.3504.00U_11.24A.3504.31_M
Stock Rom & Kernel

Why fastboot usb is not possible? Usb debugging is not at all required for fastboot command access
Do this
Extract the boot.img of any rom which has sebastian kernel as default (elegancia rom i think?)
Then copy it to your adb/fastboot folder of your pc
Then boot your phone to bootloader (remove battery, reinsert it then hold volume down + power button)
then connect the device to your pc (as your pc is linux.. It's more easy now.. No need to fetch drivers and all)
When connection is proper the phone says fastboot usb.. If it says hoot.. Press power button once
Then this command
fastboot flash boot boot.img
Sent from my Nexus 7 using xda premium

ganeshp said:
Why fastboot usb is not possible? Usb debugging is not at all required for fastboot command access
Do this
Extract the boot.img of any rom which has sebastian kernel as default (elegancia rom i think?)
Then copy it to your adb/fastboot folder of your pc
Then boot your phone to bootloader (remove battery, reinsert it then hold volume down + power button)
then connect the device to your pc (as your pc is linux.. It's more easy now.. No need to fetch drivers and all)
When connection is proper the phone says fastboot usb.. If it says hoot.. Press power button once
Then this command
fastboot flash boot boot.img
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Would fastboot commands would work for an s-on device?

Raven2k said:
Would fastboot commands would work for an s-on device?
Click to expand...
Click to collapse
Yes if it's htcdev unlocked upto certain extent where flashing boot.img is indeed permitted
Sent from my HTC Sensation 4G using xda premium

[Q] Device not recognized in fastboot

I have, in the past had fastboot working on my Desire S in Windows 7 so perhaps this is a Windows 8.1 driver compatibility issue?
Firstly, I tried to downgrade from a very slow Jelly Bean to the Ice Cream Sandwich RUU, but the device got stuck in a bootloop showing the HTC logo and the RUU USB connection times out. So I figured that I might need to re-lock my device for the RUU to work. So I tried, but fastboot devices, and fastboot oem lock dont work. Windows 8.1 says Device unrecognized and I have tried reinstalling different versions of the drivers.
adb devices works when the phone is in Jelly Bean. It's just fastboot that doesn't work.
Please help?

i have the same problem,only i have ice cream sandwich perfecto linaro edition,and my phone is not recognised on 5 different pc,and 3 macs.
fastboot does not work,neither adb debugging.
i don-t have a notification when i plug in the cable,and also i can-t use mass storage.i tried flashing a new kernel,but it wont-t flash.
recovery works,i can flash other roms,but i get a boot loop and cannot start the phone.
any help would be greatly appreciated.
thanks.
htc desire s

try this
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe

i will try this tonight.
i copied PG88IMG.ZIP to sd card,and i booted in bootloader,and it finds the file,it says loading then just parsing for 1 sec and nothing happens.
will post results tomorrow.
saga pvt ship s-on rl
hboot 2.02.0002
radio 3831.19.00.110
eMMC-boot

unfortunately it didn't work.
the driver provided didn't detect my phone.
if i format the sd card will it work?
is there any method to relock the bootloader from hboot or fastboot?i can enter recovery but every time i flash a new rom,i get a bootloop .

alllexander said:
i will try this tonight.
i copied PG88IMG.ZIP to sd card,and i booted in bootloader,and it finds the file,it says loading then just parsing for 1 sec and nothing happens.
will post results tomorrow.
saga pvt ship s-on rl
hboot 2.02.0002
radio 3831.19.00.110
eMMC-boot
Click to expand...
Click to collapse
Sorry for the newbish question, but have you both tried using different cables? I had this problem once, and it was the cable that was faulty. Charged fine, sdcard mounted fine - but neither adb nor fastboot worked.
allexander: I dont think PG88img.zip will run with s-on unless its an official, signed update thing. I think thats correct, anyway.

hello.
the pg88img.zip file is in fact the rom.zip renamed after a stock RUU installation.
I tried usint 3 different cables for the phone.
i can however connect through wifi adb.
can i do something to flash a different boot.img and then flash a ROM i know it works with usb connection and adb debugging?

alllexander said:
hello.
the pg88img.zip file is in fact the rom.zip renamed after a stock RUU installation.
I tried usint 3 different cables for the phone.
i can however connect through wifi adb.
can i do something to flash a different boot.img and then flash a ROM i know it works with usb connection and adb debugging?
Click to expand...
Click to collapse
Hmm interesting problem. Generally when the hboot says 'parsing PG88img.zip' but then that flashes for a second and goes away again, its because its trying to find a valid PG88IMG.zip but cant find one it thinks is valid enough to use. So I still think this relates to you being S-ON. For example maybe the hboot file is too old for your current version, in which case there may be fixes available using misc_version hack. That's just my instinct though. My radio has always been s-off via a cheap hardware clip, but I still struggled at first to flash PG88IMG.zip because I didnt understand the file format.
There is alot you could do if you could get PG88IMG.zip working.
Regarding your strange bootloop: are you certainly using 4EXTRecovery to wipe all partitions except the SD card before flashing a new rom?

nothing worked for me in windows 8.1 , cannot recognise the device in fastboot. only recognised in adb.
so just installed windows 7 in another partition. then fastboot recognised the phone. and i could flash the 4ext recovery. :good:

I am using twrp 2.4 and i can't flash another recovery.every time i try,it says recovery flashed then i get the same recovery when i reboot

rimpy said:
I have, in the past had fastboot working on my Desire S in Windows 7 so perhaps this is a Windows 8.1 driver compatibility issue?
Firstly, I tried to downgrade from a very slow Jelly Bean to the Ice Cream Sandwich RUU, but the device got stuck in a bootloop showing the HTC logo and the RUU USB connection times out. So I figured that I might need to re-lock my device for the RUU to work. So I tried, but fastboot devices, and fastboot oem lock dont work. Windows 8.1 says Device unrecognized and I have tried reinstalling different versions of the drivers.
adb devices works when the phone is in Jelly Bean. It's just fastboot that doesn't work.
Please help?
Click to expand...
Click to collapse
Hi your biggest issue is with windows 8 and Fastboot. They don't play nice. You will need a windows 7 PC to proceed. Once you have that. Reunlock your bootloader and flash a stock ROM from the dev section.
alllexander said:
i have the same problem,only i have ice cream sandwich perfecto linaro edition,and my phone is not recognised on 5 different pc,and 3 macs.
fastboot does not work,neither adb debugging.
i don-t have a notification when i plug in the cable,and also i can-t use mass storage.i tried flashing a new kernel,but it wont-t flash.
recovery works,i can flash other roms,but i get a boot loop and cannot start the phone.
any help would be greatly appreciated.
thanks.
htc desire s
Click to expand...
Click to collapse
It sounds like your micro USB port may be damaged. Is it loose feeling at all?
radical.entropy said:
Hmm interesting problem. Generally when the hboot says 'parsing PG88img.zip' but then that flashes for a second and goes away again, its because its trying to find a valid PG88IMG.zip but cant find one it thinks is valid enough to use. So I still think this relates to you being S-ON. For example maybe the hboot file is too old for your current version, in which case there may be fixes available using misc_version hack. That's just my instinct though. My radio has always been s-off via a cheap hardware clip, but I still struggled at first to flash PG88IMG.zip because I didnt understand the file format.
There is alot you could do if you could get PG88IMG.zip working.
Regarding your strange bootloop: are you certainly using 4EXTRecovery to wipe all partitions except the SD card before flashing a new rom?
Click to expand...
Click to collapse
You are correct good sir, s-on is the issue here. If the IMG.zip passed to the hboot is a lower version that the img installed to the device the hboot will skip it anyway. A misc hboot downgrade would work but you would need a unlocked hboot+ working recovery and to make a gold card to bypass the cid check of the ruu.
Its not that hard to do once you have done it before, but it can be daunting at first
Sent from my HTC Desire S using Tapatalk

i flashed just now flinny cm,and i got passed the htc logo,and the boot animation started but it was in a very low resolution and not centered on the screen.
i get to the point where my charging led is on,then nothing.it remains the same,through the boot process.
i am usint twrp 2.4 and i cannot flash another recovery ,not via terminal or apps in the phone.i will try to flash in recovery.can i do that?

ContactFront said:
try this
HTCDriver3.0.0.007.exe
Click to expand...
Click to collapse
Tried this and it didn't work.
DroidArmy said:
nothing worked for me in windows 8.1 , cannot recognise the device in fastboot. only recognised in adb.
so just installed windows 7 in another partition. then fastboot recognised the phone. and i could flash the 4ext recovery. :good:
Click to expand...
Click to collapse
Sounds like I need to do this. It worked for me last time I checked in Windows 7.
heavy_metal_man said:
Hi your biggest issue is with windows 8 and Fastboot. They don't play nice. You will need a windows 7 PC to proceed. Once you have that. Reunlock your bootloader and flash a stock ROM from the dev section.
Click to expand...
Click to collapse
Makes sense. I'm surprised there isn't a fix for it in Windows 8. My phone is already unlocked and I am wanting to install the RUU. Are you suggesting that I can't downgrade with RUU and need to install a stock ROM instead?

rimpy said:
Makes sense. I'm surprised there isn't a fix for it in Windows 8. My phone is already unlocked and I am wanting to install the RUU. Are you suggesting that I can't downgrade with RUU and need to install a stock ROM instead?
Click to expand...
Click to collapse
correct. while you could do it, its alot of hassle you would need to edit your misc partition so it states that your mainversion is lower than it really is. then the ruu is considered an "upgrade" and gets flashed. you would also need to make a goldcard using your sdcard and the goldcard tool in order to bypass the hboots cid check on your ruu. then it would run.
but much easier to flash a rooted stock rom go for one of these

alllexander said:
i have the same problem,only i have ice cream sandwich perfecto linaro edition,and my phone is not recognised on 5 different pc,and 3 macs.
fastboot does not work,neither adb debugging.
i don-t have a notification when i plug in the cable,and also i can-t use mass storage.i tried flashing a new kernel,but it wont-t flash.
recovery works,i can flash other roms,but i get a boot loop and cannot start the phone.
any help would be greatly appreciated.
thanks.
htc desire s
Click to expand...
Click to collapse
It is the incompatible of the driver with either Windows 8 & 8.1. I have to PCs, one with Windows 7 and the other with Windows 8.1; under either bootloader or recovery mode plugged in works with Win 7. On the other hand on win 8.1, recovery mode plugged in works fine but bootloader mode win 8.1 does not recognize the phone. I have tested them with the same phone and the same rom C11 by Devin Kin. No matter which HTC drivers installed, I got the same result.

i have now windows 7 64 bit,and it doesn't recognise my phone.
if i install usb mass storage app on the phone,if i connect the usb cable the phone notifies me about mass storage toggle,but not the usual from the ROM,the one from the app.
if i enable the usb mass storage the device isn't recognised,if i disable it it is also not recognised.
i can connect through adb wifi,i will post the logcat here,maybe someone can help.
also,can i use a command in adb shell to relock the bootloader?
if i can do that i cand try to flash PG88IMG through hboot .
i noticed i can push files through adb,can i flash boot.img from a different rom then flash the rom vie recovery immediately after?like fastboot flash after flashing a rom in recovery.

hello all.
i found the problem
it was the umt connector on the phone.

alllexander said:
hello all.
i found the problem
it was the umt connector on the phone.
Click to expand...
Click to collapse
Please tell us how to solve the problem.

[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