Database Info

[Solved] help me from bricking my emmc

I have just flashed my Desire S with Bindroid ROM after EXT4 Wipe. Now phone only shows HTC screen, Now Im very carefull about emmc issue...its neary 30 minute as it is hanging. I have read all the threads and in this situation
1) I can not pull my battery coz it fires my emmc
2) Pressing Power+vol down is not working, power+vol up+vol down is not working
3) Connected phone to pc and ADB is not reconizing my phone
Now what should i do?

Hope that this will
Code:
sagarda7 said:
I have just flashed my Desire S with Bindroid ROM after EXT4 Wipe. Now phone only shows HTC screen, Now Im very carefull about emmc issue...its neary 30 minute as it is hanging. I have read all the threads and in this situation
1) I can not pull my battery coz it fires my emmc
2) Pressing Power+vol down is not working, power+vol up+vol down is not working
3) Connected phone to pc and ADB is not reconizing my phone
Now what should i do?
Click to expand...
Click to collapse
For a start don't panic (just yet)
[Questons]
Do you have a safe Nandroid Backup that you can restore to?
You obviously have a custom RECOVERY (which one?)
Do you know which eMMC card you have?
Options Left
[1]
Pull Battery (which is risky - if you do - then pull evenly and quickly and do not re-insert for over 10 seconds)
Assuming that you have a Nandroid Backup then:
[2]
Let battery completely run out until phone shuts down on it's own.
plug into power supply for a hour or so (until battery full (green light)
Restart and force entry to bootloader (volume down + power)
Restore safe point backup from RECOVERY
Reboot
If you have no backup
[3]
Download another (safe) Custom ROM and place on SD card
Let battery completely run out until phone shuts down on it's own.
plug into power supply for a hour or so (until battery full (green light)
Restart and force entry to bootloader (volume down + power)
Ensure- that you manually WIPE SYSTEM, DATA, CACHE, , DALVIK CACHE, SYSTEM
flash new ROM
Reboot
If you don't know which eMMC chip that you have, then once you device is booted you should run the following commands from you PC to find out (you don't want these results, which is what I have) as this is run that fails:
Code:
C:\Program Files\Microsoft Support Tools>adb shell
# cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
[B][COLOR="Red"]M4G2DE[/COLOR][/B]
#
I'll be online this morning, so will be able to assist......

- Did you activate "USB debugging" mode in the menu Settings-Applications-Development?
If NOT so you can not connect by the ADB command.
- Did you press and hold down VOL UP and VOL DOWN first, and then press Power button?
If none of the above method is working, the only option for you is pulling the battery out. Remember to not re-insert so quickly.

Thanks, My chip M4G2DE or like that Coz forgot. I am sure it is the faulty one. Anyway problem its solved, thanks again

sagarda7 said:
Thanks, My chip M4G2DE or like that Coz forgot. I am sure it is the faulty one. Anyway problem its solved, thanks again
Click to expand...
Click to collapse
How did you solve it? Reboot by ADB? by Vol up/Vol down/Power combination or pulling out the battery?

Yes, how did you solve it? So that people will know what to do when they're in this situation. Thanks!

Probably adb reboot recovery command thru terminal.
Sent from my HTC Desire S using XDA Premium App

Been there myself
I went down the same rabbit hole a couple of days ago brother. Exactly the same problem you were having.
This is what saved me... Read.

how I solved it
vndnguyen said:
How did you solve it? Reboot by ADB? by Vol up/Vol down/Power combination or pulling out the battery?
Click to expand...
Click to collapse
First of all I think my Emmc may be good one or I'm lucky for that being labeled as M4G2DE. I had already nandroid backup in my sd card.
A) I waited and waited till battery was completely zero.
B) after phone turned off, waited for 2 minute.
c) connected phone to the charger and charged for 1 hour
d) opened recovery by pressing vol down first, then pressed power and released power and after getting hboot screen, released vol down.
e) went to clockwork mod and restored nandroid.

You downloaded the wrong Rom, according to your post in the other thread.
You want a ROM for the DS, not DHD
Sent from my HTC Desire S

Please provide me the link for desire s

sagarda7 said:
First of all I think my Emmc may be good one or I'm lucky for that being labeled as M4G2DE. I had already nandroid backup in my sd card.
A) I waited and waited till battery was completely zero.
B) after phone turned off, waited for 2 minute.
c) connected phone to the charger and charged for 1 hour
d) opened recovery by pressing vol down first, then pressed power and released power and after getting hboot screen, released vol down.
e) went to clockwork mod and restored nandroid.
Click to expand...
Click to collapse
Tks for your explaining, however I didn't ask for restoring procedure to stock backup.
As you've said in your 1st post, your DS has hang on the HTC screen. How did you do to bypass this issue and recharge your phone? Wait until the battery completely discharged itself?

sagarda7 said:
Please provide me the link for desire s
Click to expand...
Click to collapse
Simple - go to this page and download this one - BinDroid DS 2.3.5 GB V1.0.
But there's an imminent update, so prob better to wait.
Peace

vndnguyen said:
Tks for your explaining, however I didn't ask for restoring procedure to stock backup.
As you've said in your 1st post, your DS has hang on the HTC screen. How did you do to bypass this issue and recharge your phone? Wait until the battery completely discharged itself?
Click to expand...
Click to collapse
Ya, waited till battery is discharged completely

sagarda7 said:
Ya, waited till battery is discharged completely
Click to expand...
Click to collapse
This is not a good idea, because the risk is the same as you pull out the battery. And this will also affect the battery lifetime (because of completely discharge).

[Q] Phone in not responding - led is on.

Hi, I've got a little sceary problem with my desire s.
I installed reaper v 1.2 ROM, configured it, everything was ok. But now phone is not responding. Only black screen. I tried vol up/down and power button configuration - nothing happend. I connected phone to the charger and led turned on, I tred the same configuration - nothing happend. I discconnect phone - led is still on and phone is not responding.
I downloaded latest android sdk tools, latest htc drivers, installed, connected phone to computer, run sdk tool and type adb reboot recovery - error device not found.
When I connect phone to computer it found Qualcomm CDMA Technologies MSM, I try to install soft automaticly but comp find nothing.
Wha else I can do? I don't want pull battery. I have never done it.
Help, please.

adix631 said:
Hi, I've got a little sceary problem with my desire s.
I installed reaper v 1.2 ROM, configured it, everything was ok. But now phone is not responding. Only black screen. I tried vol up/down and power button configuration - nothing happend. I connected phone to the charger and led turned on, I tred the same configuration - nothing happend. I discconnect phone - led is still on and phone is not responding.
I downloaded latest android sdk tools, latest htc drivers, installed, connected phone to computer, run sdk tool and type adb reboot recovery - error device not found.
When I connect phone to computer it found Qualcomm CDMA Technologies MSM, I try to install soft automaticly but comp find nothing.
Wha else I can do? I don't want pull battery. I have never done it.
Help, please.
Click to expand...
Click to collapse
Don't panic brother. I've been in a similar situation many times. Whatever you do... DO NOT PULL THE BATTERY till the phone is switched off!!
Just disconnect the phone from the laptop or wall socket (remove the usb cable from the phone) and leave the phone. Don't sit and stare at it, and don't try to reason it into rebooting. Also, stop pestering God...he doesn't do phones. (I think) Just relax, and go watch T.V. or something.
One out of two things may happen :
1. It may reboot on it's own. Has happened to me... Sometimes it happes in 5 mins, sometimes in 20, and sometimes, never.
2. The battery will eventually run out of charge and your phone will switch off by itself. Now remove the battery, reinsert after 2 mins and boot up into recovery. From here, you can restore your previous nandroid backup.
P.S. If you do not have a nandroid backup, just reflash the ROM after a full format ("format all partitions, except sdcard" option in recovery). Note that if you have unlocked using HTC site, this will not work until you manually flash boot.img (you can find it in the ROM (Reaper_v1.2.zip) file) from fastboot.
Let me know what happens.

Now I' still waiting, without phone touching. Led is ON (orange colour). Phone is disconected (and me too ). Battery level was 13% before this insydent.
When LED will turn off (I don't know when) I'll reinsert battery and let you know what's up.
I hope, I did't bricked it...

adix631 said:
Now I' still waiting, without phone touching. Led is ON (orange colour). Phone is disconected (and me too ). Battery level was 13% before this insydent.
When LED will turn off (I don't know when) I'll reinsert battery and let you know what's up.
I hope, I did't bricked it...
Click to expand...
Click to collapse
Don't worry. I am virtually a 100% sure you have NOT bricked it.
Just don't panic and let the phone switch off first.
BTW, you didn't say if you unlocked your bootloader with HTC Dev site or Revolutionary?
Do you have a Nandroid backup of your previous ROM ?
How new are you to all this (flashing etc)?
Is this the first custom ROM you have flashed on this device?

enigmaamit said:
Don't worry. I am virtually a 100% sure you have NOT bricked it.
Just don't panic and let the phone switch off first.
BTW, you didn't say if you unlocked your bootloader with HTC Dev site or Revolutionary?
Do you have a Nandroid backup of your previous ROM ?
How new are you to all this (flashing etc)?
Is this the first custom ROM you have flashed on this device?
Click to expand...
Click to collapse
My phone was s-off by xtc clip (I did't use revolutionary), boot loader was unlocked on HTC Dev site.
I flashed at first CMW recover, than 4EXT Touch recovery and used it.
I tried a lot of roms, virtuous, endymnion, runny. The best for the beast was CM7.1, nightly. I flashed it month ago and updated succefully. Two days ago I decided to try REAPER. I wiped cache and dalvik's, than flashed reaper v 1.1. Today I updated it to 1.2 version (the same way as always) and I had a problem with dialer, so I wiped everything. Format all ex. sd card was done and I flashed reaper 1.2. I confogured it, just I like (set a new gov reaper, freq 118 (I don't remember) low and 1074 high) and thats it. I tried laucher, sms, phone and thats all.

adix631 said:
My phone was s-off by xtc clip (I did't use revolutionary), boot loader was unlocked on HTC Dev site.
I flashed at first CMW recover, than 4EXT Touch recovery and used it.
I tried a lot of roms, virtuous, endymnion, runny. The best for the beast was CM7.1, nightly. I flashed it month ago and updated succefully. Two days ago I decided to try REAPER. I wiped cache and dalvik's, than flashed reaper v 1.1. Today I updated it to 1.2 version (the same way as always) and I had a problem with dialer, so I wiped everything. Format all ex. sd card was done and I flashed reaper 1.2. I confogured it, just I like (set a new gov reaper, freq 118 (I don't remember) low and 1074 high) and thats it. I tried laucher, sms, phone and thats all.
Click to expand...
Click to collapse
Well in that case, don't worry your phone is safe. Just wait for it to switch off. Then after booting into recovery, just restore the last working ROM backup that you have. Don't flash the Reaper 1.2 that you downloaded till you have confirmed that the md5 checksum matches the one posted by Lowveld.

Hmm. Strange.
Phone turned off - LED was off, so I pulled battery, wait 2-5 minutes (without battery) and tried to turn it on. I saw a black screen. I press vol up/down power buttons, phone vibrated 3 times (quick) and I saw a green LED. I tried turn it on (with vol down button and without it) - nothing. I waited a while then a Led turned off.
I pluged device to the charger - orange led started blinking, so I tried to on phone - nothing. I restarted it (3 buttons) - it vibrated 3 times quickly and the same story from my first post.
Phone is unplugged, orange led is on (not blinking) and no react.
Any ideas??

Can you still boot to recovery?

adix631 said:
Hmm. Strange.
Phone turned off - LED was off, so I pulled battery, wait 2-5 minutes (without battery) and tried to turn it on. I saw a black screen. I press vol up/down power buttons, phone vibrated 3 times (quick) and I saw a green LED. I tried turn it on (with vol down button and without it) - nothing. I waited a while then a Led turned off.
I pluged device to the charger - orange led started blinking, so I tried to on phone - nothing. I restarted it (3 buttons) - it vibrated 3 times quickly and the same story from my first post.
Phone is unplugged, orange led is on (not blinking) and no react.
Any ideas??
Click to expand...
Click to collapse
Well, the blinking signifies inadequate charge for a bootup. Wait till the orange LED stopsa blinking and turns on constantly... then boot into bootloader (Voulme up and Power button - don't let go of the volume button even after releasing the power button) - I don't want you to restart by using three button combo...otherwise you'll be back to the same problem, trying to boot into a broken OS... Just disconnect again and wait for it to switch off.... then reinsert battery, connect to charger, then wait for the LED blinking to stop. Have a little patience! and DON"T RESTART with three button combo. Just boot into bootloader with Voulme up + Power key.
You have to follow these instructions carefully, exactly as i have written. Report back what happens.

enigmaamit said:
Well, the blinking signifies inadequate charge for a bootup. Wait till the orange LED stopsa blinking and turns on constantly... then boot into bootloader (Voulme up and Power button - don't let go of the volume button even after releasing the power button) - I don't want you to restart by using three button combo...otherwise you'll be back to the same problem, trying to boot into a broken OS... Just disconnect again and wait for it to switch off.... then reinsert battery, connect to charger, then wait for the LED blinking to stop. Have a little patience! and DON"T RESTART with three button combo. Just boot into bootloader with Voulme up + Power key.
You have to follow these instructions carefully, exactly as i have written. Report back what happens.
Click to expand...
Click to collapse
I did it exactly like you've written. Waited till phone, switch off, connected it and charged till led stopped blinking, disconnect, and try to boot it into recovery (vol up + power). Phone wibrated 3 times (screen did't react) and the same story. Now waiting for discharging and I'll try again.
Anyway thanks for your help and interest.
What else I can do? If the phone is not responding I can send it to warranty service. Meybe they will honour it... If not...ehss very expensive play.

adix631 said:
I did it exactly like you've written. Waited till phone, switch off, connected it and charged till led stopped blinking, disconnect, and try to boot it into recovery (vol up + power). Phone wibrated 3 times (screen did't react) and the same story. Now waiting for discharging and I'll try again.
Anyway thanks for your help and interest.
What else I can do? If the phone is not responding I can send it to warranty service. Meybe they will honour it... If not...ehss very expensive play.
Click to expand...
Click to collapse
Well, it that's not workin, Wait till the phone switches off again. Then configure adb, make sure it detects your device (use the command: adb devices) and then type the following at the cmd prompt :
adb reboot recovery
This should take you to recovery.

Ok, what can I say? Youe last thread worked!! I restared device, connect to computer - it was found as usb disk. In sdk tool divece was also found, this time as my ds Just restarted a recovery. First I saw an error in 4ext recovery, but it started with orange letters. I wiped all, formated all, recover old system, restart phone. And it works! Now I flshesd last jorgens CM7 and starting to config my phone. But a heart attack was close... Thanks man

adix631 said:
Ok, what can I say? Youe last thread worked!! I restared device, connect to computer - it was found as usb disk. In sdk tool divece was also found, this time as my ds Just restarted a recovery. First I saw an error in 4ext recovery, but it started with orange letters. I wiped all, formated all, recover old system, restart phone. And it works! Now I flshesd last jorgens CM7 and starting to config my phone. But a heart attack was close... Thanks man
Click to expand...
Click to collapse
You're welcome brother! And Congratulations!!
I know what you must have gone through till you reclaimed your phone. I remember the first time i was in a situation like yours... had to figure out this discharge the phone, LED blinking etc... thing on my own..., everyone else said battery pull was my only option. But i sitll didn't do it. I had around 60% battery remaining before this happened, so you can only imagine how many sleepless hours i spent waiting for the damn battery to run dry. http://forum.xda-developers.com/showthread.php?t=1271360
The important thing is to resist the temptation of pulling battery. Everything can be salvaged if you don't do that, but once you fry your eMMC, there is nothing anyone can do without physically repairing the phone.
May I suggest you edit the topic your OP and add the word [SOLVED] to the title. This will ensure anyone in trouble can easily locate this thread out of the cacophony on xda!

[S3] Bricked phone - only ADB is working

Hi,
my phone died yesterday because the battery was empty - so I charged it a little but the phone won't turn back on. The only thing I see are the touch buttons flashing when I hold the power button. And when I hold it long enough, the screen just flashes... When I tried to connect it my computer I got the ADB to work - I even managed to get to the recovery one time (i used the command adb reboot recovery for almost a hundred times before it came on). I wiped everything, reinstalled the rom (TrickDroid 4.0.0), but when I tried to reboot it nothing changed... it's still not working. Fastboot is not working.
Is there anything I can do about it?
Thanks.

Mmm, are you using CWM perhaps? If so, once you get the phone into fastboot - flash twrp.
Some suggestions you can try:
keep trying vol- + power untill you get into fastboot, it should work eventually.
Charge the phone a bit, unplug the usb cable, try and boot it <- This worked for me when my phone acted up like this, took a couple of tries though.
Have you tried spamming adb reboot bootloader ? That should also put you into fastboot eventually.
Once in fastboot, reflash the boot.img for the rom as well.
And once it works again, dont let the battery go flat, this seems like quite a common issue when the battery runs out.

Thanks for suggestions - I wrote a script that tired adb reboot bootloader every 20s .. and after like 400 runs it booted - I have no idea what this is about - but I should buy a new phone...
Tahnks again!

[Q] Probably bricked P3113 - Need Confirmation

So, been running CM10 for a long time on tab. Decided to go back to stock, and downloaded the JB stock rom. Flashed via ODIN. Everything seemed to go OK, except that after the flash the screen went black for ages, and didn't reboot. So I hard powered it off. Probably what did it, but it wasn't going anywhere for about 15 minutes, so figured it was the next step.
Now, I get the battery charging icon. The system goes through the Galaxy Tab 2 7.0 white logo, the swirling then glowing Samsung logo, and then loops through that forever.
It wouldn't be such a problem if I could back into ODIN and do another flash, but I can't get into download mode (normally I do it via adb but that isn't working since there is no USB connection at all). Tried all combinations, power/up, power/down etc. It just boot loops as above. I'm pretty sure I bricked it, but just wanted some confirmation.
Been doing this on and off for a long time, and it's the first time I've ever got stuck like this.
Thanks in advance.

Plug USB charger, your device will boot into charge mode. From charge mode you can boot into recovery by keep holding VOLUME UP button and than press POWER button. Clear data and cache in recovery, reboot.

ketut.kumajaya said:
Plug USB charger, your device will boot into charge mode. From charge mode you can boot into recovery by keep holding VOLUME UP button and than press POWER button. Clear data and cache in recovery, reboot.
Click to expand...
Click to collapse
Thanks, but I tried all combinations of Power/Volume UP and Power/Volume DOWN, it just goes through a normal boot cycle until it starts looping.
I guess it's possible I'm not using the right timing. I'm assuming that you hold Volume UP or DOWN and then press and hold Power until the screen goes black, and then release? I've done it like that many times, and also continued to hold everything down as the logo appears, and then system goes back to the battery charging icon as if it powers off again. I sound like such a noob when I type stuff like that!
I saw ODIN successfully write system.img, boot.img, and recovery.img, so I'm thinking any CWM recovery I had on there is toast.

sl0ttedpig said:
Thanks, but I tried all combinations of Power/Volume UP and Power/Volume DOWN, it just goes through a normal boot cycle until it starts looping.
I guess it's possible I'm not using the right timing. I'm assuming that you hold Volume UP or DOWN and then press and hold Power until the screen goes black, and then release? I've done it like that many times, and also continued to hold everything down as the logo appears, and then system goes back to the battery charging icon as if it powers off again. I sound like such a noob when I type stuff like that!
I saw ODIN successfully write system.img, boot.img, and recovery.img, so I'm thinking any CWM recovery I had on there is toast.
Click to expand...
Click to collapse
You must pull usb cable before start.
You can try to re-flash.

tuxafgmur said:
You must pull usb cable before start.
You can try to re-flash.
Click to expand...
Click to collapse
Well, don't I feel like the idiot!
How did I not think to disconnect the USB before trying this? tuxafgmur, your first "Thanks" has been registered, I've got it from here!
P.S. Welcome to the forum!

it sounds strange. never heard of such a strange boot problem. anyway it could be that while transferring boot.img it became damaged due to some error. i know you probably tryed but you may try and connect it to linux or mac os x in order to check if you could retrive more data about the tab. for example the mac could find if it is totally corrupted. normally when i plug my samsung devices it ask me to add the samsung-modem also if they are turned off. meybe if it happens the same to you you can try to adb fastboot it also if i doubt myself about it working, but give it a shot
i hope my bad english is not preventing you to understand what i'm saying!
give us new feedback!

[Help] Bricked my Nexus what's next? :(

Hi, this situation is kind of strange and I hope it's just the battery and not the whole goddamn phone.
What I'm dealing with at the moment is:
The phone doesn't boot
When plugged onto charger or USB cable it boots but stuck at Google logo after a blink and stays there. Also, Home, Back and other buttons are lighten.
When "forcefully" put into fastboot mode, e.g. after plugging it onto USB and instantly pressing Vol Up + Power it stuck there as well, volume rocker no more response neither does the power button. Also, I notice there are no commands at the end like "USB int" etc we see normally.
Fastboot or ADB returns no device found
Please help. I personally believe it could be due to battery, what do you guys think?
Thank you.

As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.

ej8989 said:
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
Click to expand...
Click to collapse
Thanks. My OS is Windows 8.1 Update 1. The last thing was to install UPDATE-SuperSU to root so that I can install ROM Manager to update Recovery but the installation was aborted so I attempt to flash it via Fastboot with success. Then, wanted to install SlimKat but it couldn't let me mount USB storage so that I can put the .zip file. I, then stupidly click on install via ADB but didn't know how to go back so I pulled the battery and powered up; used ADP push command to transfer said the file, but again for some reason I had to pull the battery and since then I am in above position.
Sent from my XT1032 using Tapatalk

Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app

Setting.Out said:
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.

BaghiXDA said:
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
Click to expand...
Click to collapse
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...

Setting.Out said:
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Click to expand...
Click to collapse
The problem is, even the Toolkit doesn't recognize the device no matter what. Even the keys for ODIN don't work, aren't they Home+VOL+ and Power?
EDIT1:
Kept plugged in for little longer as suggested but it heats up (it's too hot here) so I plugged out. Going to be running it off of Linux and lets see how it goes. :fingers-crossed:
EDIT2:
Tried Adam's UnBrickable method on Linux and even that couldn't find device. But that was to be expected since Adam clearly mentioned in his post that this tool isn't for those who see anything on their screen.

Whelp! Currently I can only see I:\ drive in device manager and that's all under portable devices and that's all. I see the same even in BIOS boot options, it's listed as "Google".

Guess need to close this thread now.