Database Info

[Q] Hard Bricked or not ??????

Until yesterday,my nexus 5 16GB (Imported from Canada to India) runs fine, but it give some error after rebooting a device. "UID's inconsistent Error (I'm feeling Lucky)" .
I searched on XDA Forum and find a solution that it needs to fix permission through TWRP recovery.
The error had gone but my internal SD storage shows empty in any file manager but works fine on PC (it shows all files and folders on PC).
I got this storage problem second time in last two months and it happens when i do some task through TWRP like cleaning cache,Dalvik cache etc.
Last time i fixed it by simply re-installing the firmware.
But this time i read somewhere to use a command "dd if=/dev/zero of=/dev/block/mmcblk0" in Terminal emulator app.
So i go for this solution.But after this when i reboot my device,it never turns ON.
No combination of button works to get in recovery or bootloader.
It is detected as " Qualcomm hs-usb qdloader 9008" port in device manager.
and if i press and hold volume up then connect it via usb to pc ,it shows unknown device.
other than this, nothing works and no screen activity.
i had already tried LG flash Tool,but it says device is in unknown mode.
Please tell me if my device is Hard Bricked or not?
If Yes ,how much it will cost to get repaired here in INDIA?
Device Details:
Nexus 5 16GB Android L LPV81C (rooted with custom TWRP recovery)
Bootloader Unlocked.

Looks like you nuked your eMMC...
Where did you find that command?

Bhupideol said:
Until yesterday,my nexus 5 16GB (Imported from Canada to India) runs fine, but it give some error after rebooting a device. "UID's inconsistent Error (I'm feeling Lucky)" .
I searched on XDA Forum and find a solution that it needs to fix permission through TWRP recovery.
The error had gone but my internal SD storage shows empty in any file manager but works fine on PC (it shows all files and folders on PC).
I got this storage problem second time in last two months and it happens when i do some task through TWRP like cleaning cache,Dalvik cache etc.
Last time i fixed it by simply re-installing the firmware.
But this time i read somewhere to use a command "dd if=/dev/zero of=/dev/block/mmcblk0" in Terminal emulator app.
So i go for this solution.But after this when i reboot my device,it never turns ON.
No combination of button works to get in recovery or bootloader.
It is detected as " Qualcomm hs-usb qdloader 9008" port in device manager.
and if i press and hold volume up then connect it via usb to pc ,it shows unknown device.
other than this, nothing works and no screen activity.
i had already tried LG flash Tool,but it says device is in unknown mode.
Please tell me if my device is Hard Bricked or not?
If Yes ,how much it will cost to get repaired here in INDIA?
Device Details:
Nexus 5 16GB Android L LPV81C (rooted with custom TWRP recovery)
Bootloader Unlocked.
Click to expand...
Click to collapse
Try this: download android driver,change usb port ad use nexus root tolkit http://forum.xda-developers.com/goo...olkit-wugs-nexus-root-toolkit-v1-8-3-t2517778 . The software has a system to try to recover bricked nexus. Sorry for my incomprensible english, i'm italian

All Bricks are hard.
If you cant fix with LG flashtool, yes it's bricked

Hi,
Try this [bootloader] [unbrick] Second Bootloader on Nexus 5
With those instructions I was able to recover my nexus 5.

ZammyHedgeFox said:
Looks like you nuked your eMMC...
Where did you find that command?
Click to expand...
Click to collapse
Somewhere a post on androidforums.com

manolito1998 said:
Hi,
Try this [bootloader] [unbrick] Second Bootloader on Nexus 5
With those instructions I was able to recover my nexus 5.
Click to expand...
Click to collapse
He destroyed mmcblk0 which is the entire eMMC partition...
So, no second bootloader.

manolito1998 said:
Hi,
Try this [bootloader] [unbrick] Second Bootloader on Nexus 5
With those instructions I was able to recover my nexus 5.
Click to expand...
Click to collapse
I had tried this but no luck....

Bhupideol said:
I had tried this but no luck....
Click to expand...
Click to collapse
Man, if your phone enter in fastboot mode, download theka first firmware from google site, maybe 4.4, and install it via fastboot, i didn't read all the thread but it save me when something similar happens to me, but if your phone didn't enter in fastboot, soo I think it's hard bricked

eng.Colombo said:
Man, if your phone enter in fastboot mode, download theka first firmware from google site, maybe 4.4, and install it via fastboot, i didn't read all the thread but it save me when something similar happens to me, but if your phone didn't enter in fastboot, soo I think it's hard bricked
Click to expand...
Click to collapse
Ok Thanks!
as none of the method works, I assumed phone is hard bricked.
Should i go for a warranty claim in Canada (i can manage to send it to canada through relative to my brother (who live in canada) for this purpose)????
Or just give here in India to LG service center for repair or motherboard replacement ????
Anyone knows how much motherboard replacement will cost ???

Bhupideol said:
But this time i read somewhere to use a command "dd if=/dev/zero of=/dev/block/mmcblk0" in Terminal emulator app.
So i go for this solution.But after this when i reboot my device,it never turns ON.
Click to expand...
Click to collapse
This here alarms me... You read "Somewhere? where exactly? you obviously didn't know what it was or what it could have done, so why do it?
Yeah, seems it's hard bricked, but you've been taught a lesson here.. make sure you know what you're doing... and don't just "read" something and try it..
If in doubt, read, then read again, then read some more.. if you are stuck. Ask.

radicalisto said:
This here alarms me... You read "Somewhere? where exactly? you obviously didn't know what it was or what it could have done, so why do it?
Yeah, seems it's hard bricked, but you've been taught a lesson here.. make sure you know what you're doing... and don't just "read" something and try it..
If in doubt, read, then read again, then read some more.. if you are stuck. Ask.
Click to expand...
Click to collapse
Yep because what he has done here is overwrite the entire partition layout.

Bhupideol said:
Ok Thanks!
as none of the method works, I assumed phone is hard bricked.
Should i go for a warranty claim in Canada (i can manage to send it to canada through relative to my brother (who live in canada) for this purpose)????
Or just give here in India to LG service center for repair or motherboard replacement ????
Anyone knows how much motherboard replacement will cost ???
Click to expand...
Click to collapse
LG in indai will not do anything because the D820 variant sold in canada and the D821 variant sold in india. It does not matter if you have LG warranty or not. Maybe they will offer you to replace the D820 board with a D821 board, but you have to pay the costs of the repair and motherboard change. The price can go above 100 USD.
If you facing this "UID's inconsistent Error (I'm feeling Lucky)" problem in the future then you have to make a factory reset. You get this error if you dirty flash roms

Bhupideol said:
But this time i read somewhere to use a command "dd if=/dev/zero of=/dev/block/mmcblk0" in Terminal emulator app.
Click to expand...
Click to collapse
somewhere... sounds fishy
Actually when I saw this I was reminded of how I used to tell folks on MMO's that I played that pressing ALT+F4 was how you pick up rare items when they drop and that you had to press it repeatedly so no one else got it...

Dude i had the same problem and fixed it with TWRP ( Fix Permissions ). Sorry for your phone btw. Looks like a nuked emmc as others said...

If it turn on I recommend you try nexus toolkit
I use that for my N7

MasterX007 said:
If it turn on I recommend you try nexus toolkit
I use that for my N7
Click to expand...
Click to collapse
Dude, it doesnt turn on. It's hard bricked. You do the dd command he did and I guarantee it'll hard brick it every time.
Sent from my Nexus 5 using XDA Free mobile app

Ok

Ok,
I got all of this.
Thanks for your replies.
Learned a lesson from my stupidity.
Now,I am sending it back to Canada.

It's kinda said that you can wipe the most important partition of the device without it warning you about the possible outcome.
Tapatalk-kal küldve az én Nexus 5-el

Flashed wrong bootstack/modem, Pls HELP unbrick m8

Hi there,
I accidentally flashed (inside twrp) my HTC m8 with a bootstack/modem of a different phone (39a,LG G2). I'm pretty embarrassed about it, didn't mean to do it...I thought I was following instructions to install a new rom for the m8,except I was in the wrong forum..
details: in TWRP I flashed the wrong file, then went on to install a new rom and an error appeared: this is not vs980, this device is m8wl...so I thought, what? strange....
I turned off the phone (without realizing yet what happened. Sorry, stressful couple of weeks) and when I tried to turn it back on, it wouldn't. No matter how long I held the power button, or power and vol down. It will not go in download mode, neither detect it is plugged in to charger or a computer. Basically totally off without any response.
My question: is there any way possible to resuscitate this phone? please help me! any advice is appreciated.
before I had the m8 with s-off,rooted,with a 5.1 rom installed.
Thank you in advance!!!

HTC m8
danielr324 said:
Hi there,
I accidentally flashed (inside twrp) my HTC m8 with a bootstack/modem of a different phone (39a,LG G2). I'm pretty embarrassed about it, didn't mean to do it...I thought I was following instructions to install a new rom for the m8,except I was in the wrong forum..
details: in TWRP I flashed the wrong file, then went on to install a new rom and an error appeared: this is not vs980, this device is m8wl...so I thought, what? strange....
I turned off the phone (without realizing yet what happened. Sorry, stressful couple of weeks) and when I tried to turn it back on, it wouldn't. No matter how long I held the power button, or power and vol down. It will not go in download mode, neither detect it is plugged in to charger or a computer. Basically totally off without any response.
My question: is there any way possible to resuscitate this phone? please help me! any advice is appreciated.
before I had the m8 with s-off,rooted,with a 5.1 rom installed.
Thank you in advance!!!
Click to expand...
Click to collapse
You need all in one kit 2.0
M8 firmwareTWRP or probably RUU file
my choice will be firmware TWRP
you can flash it with help of All in one tool kit 2.0

ok_then_so said:
You need all in one kit 2.0
M8 firmwareTWRP or probably RUU file
my choice will be firmware TWRP
you can flash it with help of All in one tool kit 2.0
Click to expand...
Click to collapse
No, a toolkit won't help. He needs a new phone.
Sent from my HTC6535LVW using Tapatalk

beaups said:
No, a toolkit won't help. He needs a new phone.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
thanks for the help so far guys!
Here's another funny thing. After a few attempts of plugging it in to a computer, it was recognized and it showed up in the device manager. The phones still did not turn on though. Additionally it seems that the phone is seen as an LG model (even though it's not), but I am not sure yet. I will get the HTC drivers installed,and if it doesn't work, I will try the LG drivers.
by the way, isn't there a way to flash the correct modem/bootstack with ones of those kits? i also remember from downloading the wrong LG G2 modem/bootstack that it didn't come with fastboot in it.
I will try a few things and report it back.
thanks again,

danielr324 said:
thanks for the help so far guys!
Here's another funny thing. After a few attempts of plugging it in to a computer, it was recognized and it showed up in the device manager. The phones still did not turn on though. Additionally it seems that the phone is seen as an LG model (even though it's not), but I am not sure yet. I will get the HTC drivers installed,and if it doesn't work, I will try the LG drivers.
by the way, isn't there a way to flash the correct modem/bootstack with ones of those kits? i also remember from downloading the wrong LG G2 modem/bootstack that it didn't come with fastboot in it.
I will try a few things and report it back.
thanks again,
Click to expand...
Click to collapse
If your device doesn't light the power button but for a single flash when you try to power it on your board is toast.
If it shows up in device manager as a qusb bulk device the board is toast.
Sent from my HTC6535LVW using Tapatalk

dottat said:
If your device doesn't light the power button but for a single flash when you try to power it on your board is toast.
If it shows up in device manager as a qusb bulk device the board is toast.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I got it to be recognized on a computer again, and windows installs a driver. The name of the device is forge hs-usb qdloader 9008.
I tried the all in one 2.0 kit, adb sideload, etc but anything I try I get a "device not found".
I think I am giving up unless someone finds a way to unbrick this kind of severe problem in the future. I also researched a bit on google, and there's a way to unbrick the LG G2 when it's seen as forge hs-usb qdloader 9008, which is known as a board unbrick. I found nothing for the HTC m8 though.
We tried all we could Thanks all for the help, it's very much appreciated! You guys are the best and this forum is awesome. I also ordered a new phone...and I will root it too

dottat said:
If your device doesn't light the power button but for a single flash when you try to power it on your board is toast.
If it shows up in device manager as a qusb bulk device the board is toast.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Might be completely wrong on this.
Wouldn't he be able to JTAG the appropriate boot image back onto the device?
Also, I know we had a hard brick recovery for the S3 back in the day. Worked consistently on full hard brick's.
http://forum.xda-developers.com/showthread.php?t=2581166
Isn't it possible to dump a debrick image from a working device and follow the guide with that? I know the two devices are completely different, but the premise is the same.
My technical know-how isn't anywhere near your level, just thought I'd throw these ideas out there is case it hasn't been thought of yet. I'd be happy to put together a guide on how to do this if it can work on the M8.

BadUsername said:
Might be completely wrong on this.
Wouldn't he be able to JTAG the appropriate boot image back onto the device?
Also, I know we had a hard brick recovery for the S3 back in the day. Worked consistently on full hard brick's.
http://forum.xda-developers.com/showthread.php?t=2581166
Isn't it possible to dump a debrick image from a working device and follow the guide with that? I know the two devices are completely different, but the premise is the same.
My technical know-how isn't anywhere near your level, just thought I'd throw these ideas out there is case it hasn't been thought of yet. I'd be happy to put together a guide on how to do this if it can work on the M8.
Click to expand...
Click to collapse
Not likely with the nand used on this device.
Sent from my HTC6535LVW using Tapatalk

Moto G Stuck in Boot Loop

Hello, I am not to sure if I am posting in the correct place. Anyways, on to my issue, I have a Moto G (1st Gen), I tried to do a Factory/Hard Reset and unfortunately, My device is now stuck in a Boot Loop? I can access Fast boot Mode, if that is the correct term. Can someone please get back to me asap? I am in some serious need of help..
Also, I tried to flash the stock rom and just got "Waiting for device" I suppose that would me my drivers for the device are not installed.

crazyphysc said:
Hello, I am not to sure if I am posting in the correct place. Anyways, on to my issue, I have a Moto G (1st Gen), I tried to do a Factory/Hard Reset and unfortunately, My device is now stuck in a Boot Loop? I can access Fast boot Mode, if that is the correct term. Can someone please get back to me asap? I am in some serious need of help..
Also, I tried to flash the stock rom and just got "Waiting for device" I suppose that would me my drivers for the device are not installed.
Click to expand...
Click to collapse
Hi, and thank you for using XDA Assist
To restore your phone I suggest you to head over Here where you can find everything you need to flash back the stock ROM including also the download link for the proprietary drivers
Hope that helps
Regards

nilac said:
Hi, and thank you for using XDA Assist
To restore your phone I suggest you to head over Here where you can find everything you need to flash back the stock ROM including also the download link for the proprietary drivers
Hope that helps
Regards
Click to expand...
Click to collapse
This does not work, unfortunately. I have already tried this. Please help. ADB is not recognizing my device. Nothing is. But my device is in Fastboot and says USB connected???

crazyphysc said:
This does not work, unfortunately. I have already tried this. Please help
Click to expand...
Click to collapse
Are you sure? Have you done everything step by step? Drivers properly installed etc..?
If so then check up the Q&A and try to ask by explaining what happened and I'm sure you will get an answer.
Regards

nilac said:
Are you sure? Have you done everything step by step? Drivers properly installed etc..?
If so then check up the Q&A and try to ask by explaining what happened and I'm sure you will get an answer.
Regards
Click to expand...
Click to collapse
I don't know about the drives. Nothing I use not even ADB recognizes that my device is connected. Except my computer. And in "Device Manager" all is says is "Unknown Device"

Restoring 1 A0001 from two bad ones...

Hi Fellow forum members!
I am trying to restore my doughters phone ( sat on it, bend the phone, and cracked glass+lcd ).
I, by odd luck, was sent a bricked A0001 for parts like ten days before that.
The bricked phone is in a very good shape.
It just did not respond to anything.
I tried to mount my doughters motherboard into the bricked phone, thinking that would unbrick it.
But not so....
It does wake up now, but only in Cyanogen Recovery mode.
I could rip out all and just go for the lcd but that is a repair that never has a good outcome, as you really are taking glued in parts out that never will fit back in a 100%
now ...
is that my only option?
i could try to reinstall thru cyanogen recovery ( thats the mode it is in right now )
adb sideload is something i have no experience with...
or is it simpeler to unbrick the bricked one?
All help is appreciated!
Marc.

Try the bacon root toolkit first, it will simplify sideloading a new rom, most important is that you have a recovery working.

amd-dude said:
Try the bacon root toolkit first, it will simplify sideloading a new rom, most important is that you have a recovery working.
Click to expand...
Click to collapse
Hi amd-dude!
tx for the intel.
i do not have a working recovery from neither the bent nor the bricked one.
i also own a oneplus one. ( if necessary i can retrieve one from there )
i will try try bacon root toolkit first.
your next virtual beer is on me!
// i find it odd that switching the motherboard puts the "combo- phone" in recovery mode...
// isn't the motherboard compatible?

amd-dude said:
Try the bacon root toolkit first, it will simplify sideloading a new rom, most important is that you have a recovery working.
Click to expand...
Click to collapse
i tried the bacon root toolkit.
stuck at no bootloader...

LabRatNo9 said:
i tried the bacon root toolkit.
stuck at no bootloader...
Click to expand...
Click to collapse
Just replace LCD display from bricked one.Use YouTube for DIY.

Mr.Ak said:
Just replace LCD display from bricked one.Use YouTube for DIY.
Click to expand...
Click to collapse
tx Ak!
gonna give it another hour to try to restore it
clean driver install
and hopefully the fastboot will be working
if not
then the screen replace is next ( yes i know youtube )
don't think it will make a difference as i wiped the working motherboard ...
tx again

LabRatNo9 said:
tx Ak!
gonna give it another hour to try to restore it
clean driver install
and hopefully the fastboot will be working
tx again
Click to expand...
Click to collapse
What's the issue with fastboot mode?

Mr.Ak said:
What's the issue with fastboot mode?
Click to expand...
Click to collapse
I can't see the correct google driver when i want to setup driver software for A0001.
even-thou i installed the google drivers and am showed the thumbs up for a good install.
i do get a 'google galaxy nexus ADB interface' option for driver
but when i use that, it wont get into fastboot.
the phone is completely empty btw....

LabRatNo9 said:
I can't see the correct google driver when i want to setup driver software for A0001.
even-thou i installed the google drivers and am showed the thumbs up for a good install.
i do get a 'google galaxy nexus ADB interface' option for driver
but when i use that, it wont get into fastboot.
the phone is completely empty btw....
Click to expand...
Click to collapse
Uh,no.To boot into fastboot press volup+power button.No need of drivers and stuff.

well actually you dont need to worry about glued in parts..
i had a broken screen too , and i found a screen with frame / bezel on ebay..
very easy to replace no glue , just click click click.
Just be carefull when you open the backplate.. especially in the sides as there are "ribbons" for the power button and volume button, those are easily destroyed with the tools you use ..
good luck

Is my stock phone bricked?

It's a stock phone, unrooted bootloader locked. The phone was updated to the latest firmware a few days ago and was working well since.
Today I left the phone on the desk for a while. When I came back, the phone had rebooted and was in the fastboot mode screen.
I tried to restart but it just loops back to same screen. Does not even go into recovery!!
What snapped it, cant understand!
Is it bricked? How do I revive the phone now?
Please help!
Thanks

Could be some CRC glitch in the main memory which prevents your phone from boot.
Being in FB mode try to flash some stock ROM (download the latest stock or Beta 9). Don't try to go to Recovery, flash from FB with fastboot utility.
https://downloads.oneplus.com/devices/oneplus-6/

sms2000 said:
Could be some CRC glitch in the main memory which prevents your phone from boot.
Being in FB mode try to flash some stock ROM (download the latest stock or Beta 9). Don't try to go to Recovery, flash from FB with fastboot utility.
https://downloads.oneplus.com/devices/oneplus-6/
Click to expand...
Click to collapse
Do I also need to flash stock recovery from fastboot?
Thanks again.

observingi said:
Do I also need to flash stock recovery from fastboot?
Thanks again.
Click to expand...
Click to collapse
No, recovery is part of the ROM, so not needed.

If it's a completely stock device, why not contact OnePlus and get a replacement?

Are you guys suggesting ADB sideload command? My USB debugging seems to be off, returns empty on "adb devices"
I am unaware of fastboot command to flash the stock rom, googled it but could not figure out the right command.
Thanks

maigre said:
If it's a completely stock device, why not contact OnePlus and get a replacement?
Click to expand...
Click to collapse
That's right.
If am not able to fix it myself with members help, I'll have to go through customer support drill.

observingi said:
Do I also need to flash stock recovery from fastboot?
Thanks again.
Click to expand...
Click to collapse
(a) there is no such thing as "bricked" when it comes to any OP Qualcomm devices
(b) as with ANY OP Qualcomm, OnePlus can reflash remotely directly to the Qualcomm or you can do the same thing yourself. Just follow the simple instructions.
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051

jerrywmilton said:
(a) there is no such thing as "bricked" when it comes to any OP Qualcomm devices
(b) as with ANY OP Qualcomm, OnePlus can reflash remotely directly to the Qualcomm or you can do the same thing yourself. Just follow the simple instructions.
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
Thanks for the assistance.
I tried the unbrick tool, but device manager (Windows 7 64bit) shows the device as Oneplus Android Bootloader Interface (under Samsung Android Phone )
Therefore, MSMDownloadTool does not show any device in the list.
Driver https://androidfilehost.com/?fid=889964283620777981
Edit: Phone recognized now

observingi said:
Thanks for the assistance.
I tried the unbrick tool, but device manager (Windows 7 64bit) shows the device as Oneplus Android Bootloader Interface (under Samsung Android Phone )
Therefore, MSMDownloadTool does not show any device in the list.
Driver https://androidfilehost.com/?fid=889964283620777981
Edit: Phone recognized now
Click to expand...
Click to collapse
Fingers crossed mate! Hope you get it right!

observingi said:
Thanks for the assistance.
I tried the unbrick tool, but device manager (Windows 7 64bit) shows the device as Oneplus Android Bootloader Interface (under Samsung Android Phone )
Therefore, MSMDownloadTool does not show any device in the list.
Driver https://androidfilehost.com/?fid=889964283620777981
Edit: Phone recognized now
Click to expand...
Click to collapse
yeah, I was gonna say....just follow directions carefully....it works....same set up has been working for years for each different model.

Thanks to each one of you.
The issue is resolved
I used the unbrick tool i.e. MSMDownloadTool to fix the problem. Hope it does hot happen again!
Thanks