Database Users

[Q] Help Please. Can't mount cache, boot, or detect device

I have a Motorola Defy, and I'm a noob. I was trying to install Cyanogen Mod 7 on it, but something went awry, and here's a little about the situation. I'm using Motorola USB Drivers 4.9.0 and RSD Lite 5.3.1. I'm using a PNY 16 GB class 10 microSD card. I no longer have the stock 2 GB card. I flashed 3.4.2 177-5 Nordic onto the phone. I always forgot to put my phone into recovery mode before ever flashing these different sbf files. Nordic worked fine except it said the sd card was always unmounted even though it was plugged in. I couldn't do much which that so I flashed 2.2.1-3.4.2 107 T-Mobile US onto it (again not from recovery) and the sd began working again.
I allowed usb debugging and rooted with Superoneclick 1.9.5 ShortFuse and installed 2nd Init for Defy. I restarted it twice and then turned off usb debugging. I booted into 2nd Init (not 2nd boot), went to install zip from sd, and opened the cyanogen_jordain-ota-beta5.1.zip file. I then installed Google apps 20110613 and wakeup_fix.zip. I know this is stupid but I wasn't reading the output for each step, but I think I remember it saying that it was updating for the cyanogen. When I wiped the cache and the data, it said things like:
E:can't mount /dev/block/mmcblk1p24
(Invalid argument)
E:Can't mount CACHE:recovery/command
E:Can't mount/dev/block/mmcblk1p24
(Invalid argument)Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
E:Can't mount /dev/block/mmcblk1p24
(Invalid argument)
Now it's stuck on the Motorola boot logo, except it'll still enter 2nd Init boot menu.
It also could not read anything from the sd card including Cynanogen for the second time until the next day after I put the sd card into my computer and viewed it. So now it can read from the sd card again. I have no backup.
I tried reflashing it, but when I put the phone in stock recovery, no device is detected, however, my computer does recognize something's plugged in by that noise the system makes whenever I plug or unplug it. I tried using ADB shell to mount the cache on recovery mode but no luck. It says no device detected. I might not have been doing that right.
I may be forgetting some information because I tried fixing it very late last night.
I don't own very many nice things, but this is one of them, and I'd really like to get it running again. Any help will be very appreciated. Thank you all for reading my post-
Kibogami

whats your email address so i can send u the original sbf

While u boot hold vol up button ull see bootloader n connect to pc
Rsd will recognize...
Sent from my MB525 using XDA Premium App

Thank you. That worked, and the phone went into bootloader mode. RSD Lite recognized it, and then, I flashed 2.2.1-3.4.2-107 T-mobile US. After I flashed it, though, I had to manually power it up. RSD Lite said finished, but now, it's stuck in a bootloop. It shows the motoblur animation, and then, the T-mobile animation and keeps repeating the 2. So I let it do that for a little while. I went to bootloader mode to flash 2.1, but it says battery too low to program, and RSD won't recognize it.
Thanks again
Kibogami

when you power up your phone go into factory recovery vol- and factory reset should boot up fine

Ok. Got everything back to normal. Thanks again everyone. I charged my phone with the wall charger for a little while, and that got things moving again. I went to bootloader, flashed 2.2.1 again with RSD Lite, did a factory reset, and was good to go.
Does anyone know about why CM7 didn't install properly in the first place?
Thanks

the cm7 zip file also flashes a new recovery sometimes you have to reinstall cm7 from the new recovery essentially install once reboot into recovery and repeat works fine have had the same problem myself a while ago anyways glad i could help and enjoy!!!!

having the same problem but rsd isn't recognizing the phone when I connect in bootloader. windows makes a noise but nothing beyond that when i connect

jsteve01 said:
having the same problem but rsd isn't recognizing the phone when I connect in bootloader. windows makes a noise but nothing beyond that when i connect
Click to expand...
Click to collapse
Open RSDLite with administrator priviledges, make sure it is the latest RSDLite and moto drivers (6.1 I think).

Step 2/2 Installing - Update failed - Bricked?

Hi there!
I tried to update firmwmare with lots of different ROM's (B135,B136,B162,B517,B522) but always getting "Update failed" at Step 2/2 - Installing.
Is this phone bricked?
I cannot access internal card.
Any ideas before i threw it away?
Update: On sdcard i am getting error in file: sd_update.log
notes: (dld_file_ptr != -1) !
dload_sd_file_data_proc-(dld_retry >= DLOAD_RETRY) failed!

Try mounting internal throught ubuntu in pink screen. Then Put b138 there, remove anything else from internal. Then remove battery from phone and put it to charger. Then start update. If it fails, start it again. After that go to recovery and do factory reset.
Sorry for my english. Im in a bit hurry.
from my Desire HD using XDA App

As long as you have a working pink screen, anything is solvable .

I do have pink screen and blue screen. I tried to mount internal with vmware ubuntu. But cannot mount it. It doesn't show up at all Don't know how to mount it.
Any ideas or help would be appreciate! Thanks guys!

update the original version you had before custom roms. update without battery. plugin power cord.
Sent from my u8800 using XDA App

Maksimitoisto said:
update the original version you had before custom roms. update without battery. plugin power cord.
Sent from my u8800 using XDA App
Click to expand...
Click to collapse
Hi!
Thanks for try helping me. But as i said earlier. I tried with all official ROM's but stuck at step 2/2. Always getting update failed.

mesnati said:
I do have pink screen and blue screen. I tried to mount internal with vmware ubuntu. But cannot mount it. It doesn't show up at all Don't know how to mount it.
Any ideas or help would be appreciate! Thanks guys!
Click to expand...
Click to collapse
In development section, blefish has tutorial to get usb in pink screen back.
Sent from my Desire HD using XDA App

mesnati said:
Hi!
Thanks for try helping me. But as i said earlier. I tried with all official ROM's but stuck at step 2/2. Always getting update failed.
Click to expand...
Click to collapse
Also tried without battery. It is the only way to update. With battery cannot go further from "step 1/2 Unpacking"

julle131 said:
Try mounting internal throught ubuntu in pink screen. Then Put b138 there, remove anything else from internal. Then remove battery from phone and put it to charger. Then start update. If it fails, start it again. After that go to recovery and do factory reset.
Sorry for my english. Im in a bit hurry.
from my Desire HD using XDA App
Click to expand...
Click to collapse
How to find device to mount? dmesg show me nothing.
Any help would be helpful

[email protected]:/home/xxx# lsusb
Bus 002 Device 002: ID 12d1:1035 Huawei Technologies Co., Ltd.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
I can see device with "lsusb" but cannot mount it
Anyone?

julle131 said:
In development section, blefish has tutorial to get usb in pink screen back.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Thanks julle!
But seems to me that you don't understand the problem.
Here are the steps from blefish:
1 Download update-B518-bootloader.zip from MediaFire.
2 Save it to the root of your SD Card.
3 Start the phone in recovery mode (recommended recovery is 5.5.0.4)
4 Select "install zip from sdcard"
5 Select "chooze zip from sdcard"
6 Select the zip you downloaded before.
7 Select yes.
I am already STUCKED in step 3. Because i do not get to RECOVERY MODE!!!
I am having only PINK screen (VOL +, VOL -, power button) and BLUE screen (VOL +, power button). That's it!
And CANNOT access to internal card on Windows neither on Linux Ubuntu.

Guess Huawei officials has USB drivers to access internal card on Windows or Linux but they don't share them with us
I have android_winusb.inf driver but cannot install it and recognize device in pink or blue screen mode

mesnati said:
I am already STUCKED in step 3. Because i do not get to RECOVERY MODE!!!
I am having only PINK screen (VOL +, VOL -, power button) and BLUE screen (VOL +, power button). That's it!
And CANNOT access to internal card on Windows neither on Linux Ubuntu.
Click to expand...
Click to collapse
I got the blue screen when I accidently forgot to put boot.img back in its place on the image partition.
My hypothesis is, based on that, the first UPDATE.APP (the smaller one) changes the partition layout (which would delete all the files), while the larger UPDATE_G.APP starts installing all the files: /system but - more importantly - the image partition where boot.img, AMSS.mbn and recovery.img are stored. If the update did not take, then they won't be there and the bootloader can't start them up. In my case, I was able to mount the image partition in Linux and put the boot.img back. Hopefully I'm talking out of my ass. :\
Ah! I was able to mount the partition in Linux because I'm using the B512 bootloader; you must have the B540 bootloader (or whatever is its equivalent for the U8800). I guess Huawei's laissez faire attitude towards rooting (you could browse / from the computer!) is going away now that they're moving into the big time (deals with AT&T, the Honor etc.). I don't know how you can downgrade if you can't boot to something like recovery.
mesnati said:
Guess Huawei officials has USB drivers to access internal card on Windows or Linux but they don't share them with us
I have android_winusb.inf driver but cannot install it and recognize device in pink or blue screen mode
Click to expand...
Click to collapse
Actually, these work: http://www.mediafire.com/?j33yo9wy9bspm86
But you can't ADB from the bootloader (or use them to mount a partition); it's for running Qualcomm QPST (though I couldn't figure out how to get it working).

Sorry, but im running out of ideas. It seems you have bootloader locked, and without recovery we cant unlock it... what happens if you install official 2.2 and after error try to install it again? We must get the bootloader unlocked.
Sent from my Desire HD using XDA App

julle131 said:
Sorry, but im running out of ideas. It seems you have bootloader locked, and without recovery we cant unlock it... what happens if you install official 2.2 and after error try to install it again? We must get the bootloader unlocked.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
You are making me laugh )
I cannot install NOTHING!!! That's the main problem

qwerty12 said:
I got the blue screen when I accidently forgot to put boot.img back in its place on the image partition.
My hypothesis is, based on that, the first UPDATE.APP (the smaller one) changes the partition layout (which would delete all the files), while the larger UPDATE_G.APP starts installing all the files: /system but - more importantly - the image partition where boot.img, AMSS.mbn and recovery.img are stored. If the update did not take, then they won't be there and the bootloader can't start them up. In my case, I was able to mount the image partition in Linux and put the boot.img back. Hopefully I'm talking out of my ass. :\
Ah! I was able to mount the partition in Linux because I'm using the B512 bootloader; you must have the B540 bootloader (or whatever is its equivalent for the U8800). I guess Huawei's laissez faire attitude towards rooting (you could browse / from the computer!) is going away now that they're moving into the big time (deals with AT&T, the Honor etc.). I don't know how you can downgrade if you can't boot to something like recovery.
Actually, these work: http://www.mediafire.com/?j33yo9wy9bspm86
But you can't ADB from the bootloader (or use them to mount a partition); it's for running Qualcomm QPST (though I couldn't figure out how to get it working).
Click to expand...
Click to collapse
You are right!
So the device should be bricked now? I cannot give back to warranty 'cause i already did it once If i send also this one they will laugh at me and of course they will not give me another phone

But after i installed those drivers you've attached i am getting no more exclamation mark in Device manager. hmmm. Please look at attached pic. What now?
Is there a chance to getting to device through hyperterm or something?

mesnati said:
But after i installed those drivers you've attached i am getting no more exclamation mark in Device manager. hmmm. Please look at attached pic. What now?
Is there a chance to getting to device through hyperterm or something?
Click to expand...
Click to collapse
qwerty12 said:
But you can't ADB from the bootloader (or use them to mount a partition); it's for running Qualcomm QPST (though I couldn't figure out how to get it working).
Click to expand...
Click to collapse
Actually, I haven't tried HyperTerminal on the COM ports/modem - maybe it could, somehow, let you do something? Changing the USB mode would be great...
If you do figure out QPST, you'll need the firmware in a form it can understand - maybe you'd have to get another device to dump its firmware...
Regarding warranty: Couldn't you make the case that it was an official firmware update that caused your phone to brick?

mesnati said:
You are making me laugh )
I cannot install NOTHING!!! That's the main problem
Click to expand...
Click to collapse
I am bad in english, so it might be the problem cant express my self right. I know it fails, but run it again after the fail. I am hoping it unlocks bootloader. Then you can access the phones whole memory from ubuntu.
Someone, if you understand this sh*t im writing, please translate it to real english
Sent from my Desire HD using XDA App

julle131 said:
I am bad in english, so it might be the problem cant express my self right. I know it fails, but run it again after the fail. I am hoping it unlocks bootloader. Then you can access the phones whole memory from ubuntu.
Someone, if you understand this sh*t im writing, please translate it to real english
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Your english is ok I tried 100 times after it fails and every time same error appears "Update failed"

trying to restore a hard-bricked defy

I'm trying to restore a Defy that was hard-bricked by a failed installation of CM11. As I described in this post, the phone shows absolutely no signs of life; neither the screen nor the led light turn on at all, even though I've tried several different fully-charged batteries. The phone will not go into bootloader mode, even if I try to force it by holding power and volume+ while inserting the battery, so I cannot flash an sbf in RSD Lite.
@skeevydude and @TJKV suggested that I try using this sbf_flash tool in a Linux environment instead of using RSD Lite in Windows. I gave that a try, and unfortunately the phone still is not detected by the PC. Here's the output from sbf_flash:
Code:
[email protected]:~$ chmod +x sbf_flash
[email protected]:~$ ./sbf_flash firmware.sbf
SBF FLASH 1.23 (mbm)
http://opticaldelusion.org
=== firmware.sbf ===
Index[1]: Unexpected chip 32
Index[2]: Unexpected chip 32
Index[3]: Unexpected chip 32
Index[4]: Unexpected chip 32
Index[5]: Unexpected chip 32
Index[6]: Unexpected chip 32
Index[7]: Unexpected chip 32
Index[8]: Unexpected chip 32
Index[9]: Unexpected chip 32
Index[10]: Unexpected chip 32
Index[11]: Unexpected chip 32
Index[12]: Unexpected chip 32
Index[13]: Unexpected chip 32
00: RDL03 0x82000000-0x8204CFFF 4035 AP
01: CG31 0xB0280000-0xB02847FF 9A68 AP
02: CG32 0xC7A00000-0xC7A207FF 4805 AP
03: CG33 0xB2000000-0xB2DC07FF 8BAC AP
04: CG34 0xB0700000-0xB07047FF AB80 AP
05: CG35 0xB1000000-0xB17FFFFF 100C AP
06: CG39 0xB3300000-0xC79C07FF C7E6 AP
07: CG42 0xB0800000-0xB0842FFF 4BB7 AP
08: CG45 0xB0C00000-0xB0F007FF 738D AP
09: CG47 0xB1800000-0xB1FFFFFF 45F0 AP
10: CG53 0xB2F00000-0xB2F007FF FDFF AP
11: CG61 0xB0B00000-0xB0B7FFFF 4A7C AP
12: CG64 0xB0000000-0xB00047FF 85D0 AP
13: CG65 0xB0180000-0xB01847FF 2409 AP
>> waiting for phone:
It just stays on "waiting for phone" forever.
Here's how the brick happened:
After doing a clean install of @Quarx's February 2nd CM11 build (one of the "autobot" builds), I was no longer able to mount the sdcard, so I tried mounting it in TWRP, but that didn't work. I rebooted and tried again, still without success. Then I removed the original sd card and put in another sd card to see if that would mount. Still no. Then I tried partitioning the sdcard from TWRP. (I had read on some other forum that doing so might help TWRP to mount the sdcard.) When I tried to partition the sdcard, TWRP gave a "failed" message, and I later confirmed on my PC that the files on the sdcard had not been erased. After my attempt to partition the sdcard from TWRP, I was suddenly unable to mount any of the partitions! I powered off the phone (perhaps unwisely), and now it is completely dead: no led light, and nothing on the screen, no matter what I do.
I haven't been able to get the phone into bootloader mode, so I can't flash an sbf with RSD Lite in Windows, nor with sbf_flash in Linux.
When I type "lsusb" in the Linux terminal to see what usb devices are connected, the phone is not listed.
However, when I used USBDeview in Windows to see if anything shows up there, I found something interesting. When I try to force bootloader mode (by removing the battery, then replacing it while holding power and volume+), a device called "Motorola Flash Interface" shows up briefly in USBDeview, then disconnects after about a second. So maybe the phone isn't completely dead after all. Does anyone have any ideas how I can get it to stay connected to the PC (in either Windows or Linux) so I can flash an sbf?
Thanks in advance for any help.

The symptoms are similar to those which occur when internal eMMC flash memory is wiped from boot menu via a pc(I've seen this before). That however, does not help at all, since there is no fix for that
Anyways, try the factory cable once before you can use it as the most expensive paperweight you may come to own
Sent from my MB526 using Tapatalk

thekguy said:
The symptoms are similar to those which occur when internal eMMC flash memory is wiped from boot menu via a pc(I've seen this before). That however, does not help at all, since there is no fix for that
Click to expand...
Click to collapse
I was afraid of that. I suspect that TWRP wiped the internal memory instead of the sdcard.
Anyways, try the factory cable once before you can use it as the most expensive paperweight you may come to own
Click to expand...
Click to collapse
I always use the factory cable when flashing an sbf, but unfortunately that didn't help in this case. Thanks anyway for the suggestion.

Now, I'm sure that is a sign of some rather deep seated bug, but the thing is it has neither occurred on other devices, nor were the steps taken by you any different than the standard ones.
Your theory explains the outcome, but the thing is that partitions can't just "switch places", because even if such a corruption occurred, the locked boot loader should have kicked in on reboot, (probably) saving the device.
So how exactly it occurred, is quite a mystery, which lies somewhere on the eMMC chip:what:
Sent from my MB526 using Tapatalk

problem is old: Epsylon was done something like this when he try to change the partition. Result: maybe the ONLY way to hard brick the Defy.

pgreed said:
problem is old: Epsylon was done something like this when he try to change the partition. Result: maybe the ONLY way to hard brick the Defy.
Click to expand...
Click to collapse
Well, he certainly did not trigger eFuses or tamper with the partition table, atleast not by any of the steps taken. So, the diagnostics are similar, but the causes quite different
Sent from my MB526 using Tapatalk

Proverbs2 said:
I was afraid of that. I suspect that TWRP wiped the internal memory instead of the sdcard.
Click to expand...
Click to collapse
I think that is what happened: the way Linux device numbering works, when /dev(/block)/mmcblk0 doesn't exist (because your MMC card or chip was broken), /dev(/block)/mmcblk1 is never created, and becomes mmcblk0 instead. On the Defy, mmcblk0 is the external MMC card, and mmcblk1 is internal memory. TWRP probably never checked and repartitioned mmcblk0, which was your internal memory because the device it should have been never was created.
I've done something similar (tried to repartition /dev/block/mmcblk1), and thought I'd bricked my phone, but two things happened:
1. with the original cable connected to the charger, the white LED would flash for just an instant when connecting/disconnecting the charger
2. when connected to the USB port, mashing the up/down/power keys randomly for a while would eventually result in white-LED (but no screen) SBF-flashable mode. I suppose there's some sort of menu or code, but it's not as simple as holding up while pushing power.
It's recovered now and is running Quarx's CM11. Worth one last try before you give up on it entirely.
Please let me know if I've done something horribly wrong, this is my first post.
ETA: I can confirm that TWRP is misbehaving when no MMC card is inserted in the phone, though for obvious reasons I've stopped short of trying what you did (I've only got this one phone!) It's probably worth a bug report to the right people, though I'm not sure who that is.

+1 for misbehaving TWRP, however it did not mount any partition in my case, and so it was not possible to wipe anything. Not that I would have. Also, the "No OS found" message was triggered, probably because /system wasn't mounted
The difference between a fully wiped device and a partially wiped is the led, and the steady boot loader mode connection, which may or may not display any text on the device. Probably the only way to recover a fully wiped defy is JTAG(if interface exists)
Sent from my MB526 using Tapatalk

Hi
do you try to flash a mb526 sbf?

popov1100 said:
do you try to flash a mb526 sbf?
Click to expand...
Click to collapse
I can't flash any sbf at all, because it seems TWRP deleted the bootloader.

Proverbs2 said:
I can't flash any sbf at all, because it seems TWRP deleted the bootloader.
Click to expand...
Click to collapse
So , you can be happy :silly: .You are the first? one which have a unlocked bootloader on Defy. (sry for the silly)

Seems I am the second.
Today my defy suddenly can not boot into TWRP or andorid. After a sbf flash, I was following Quarx's site instruction of " from sbf to CM11 ", after a command though adb as root: cat /sdcard/bootstrap_ext3.img > /dev/block/mmcblk1p21 , defy got black screen and never responeded from there. No reaction on boot and plug in battery while holding vol+ and power. Still have not find a way to bring it back to life.

x.theme said:
Seems I am the second.
Today my defy suddenly can not boot into TWRP or andorid. After a sbf flash, I was following Quarx's site instruction of " from sbf to CM11 ", after a command though adb as root: cat /sdcard/bootstrap_ext3.img > /dev/block/mmcblk1p21 , defy got black screen and never responeded from there. No reaction on boot and plug in battery while holding vol+ and power. Still have not find a way to bring it back to life.
Click to expand...
Click to collapse
I'm very sorry to hear that. Maybe your battery is dead? You could try charging the battery with an external wall charger, or try the "McGyver" method to charge it.
Good luck!

Proverbs2 said:
I'm very sorry to hear that. Maybe your battery is dead? You could try charging the battery with an external wall charger, or try the "McGyver" method to charge it.
Good luck!
Click to expand...
Click to collapse
Tried both, still no luck, T_T
After the McGyver method, defy has white light on and black screen, can not get into bootloader, RSD still can not recognise anything...
Anyway, thanks for the tips!

x.theme said:
Tried both, still no luck, T_T
After the McGyver method, defy has white light on and black screen, can not get into bootloader, RSD still can not recognise anything...
Click to expand...
Click to collapse
Had the exact same unfortunate experience an hour ago, trying to update to CM11. Did someone found a method to bring the phone back to life ? Tried everything but seems that the command wiped the partition (though i don't know how or why...)
Here is the original thread :
http://forum.xda-developers.com/showpost.php?p=56228383&postcount=6049

[Q] Corrupt bootloader and black screen but live usb -- still hope?

Hi there
@bftb0 : yet another victim of the corrupt bootloader .img ! (see thread #2573015)
bftb0 said:
The versions distributed with JWR66Y and KOT49H* Google factory images are INVALID.
Click to expand...
Click to collapse
Device : Nexus 7 2012 wifi (grouper), stock 4.4.4 KTU84P, never rooted before
Symptoms : black screen, not booting at all even to bootloader. :crying:
Only faint light of hope is that my PC is still reacting to plugging the Nexus in with USB.
Windows beeps and shows an "unknown usb device" error then fails finding a driver.
Windows Device manager shows "APX" with yellow sign below "Other devices".
Question : bricked or any hope left ? Pleeease what can I do ?
How I got there :
NRT hung when flashing bootloader while reinstalling stock 4.4.0 (nakasi-krt16s-factory-da7dee49).
The story, going from bad to worse :
It started with a sudden reboot for not appearent reason (incidentally while an Avast routine scan was running).
Then endless reboot, with the 4 color balls shaking indefinitely (power plugged in or not).
Looked at forums... Reboot into bootloader. Recovery mode, wiped cache. Got plenty of error msg "E:failed to mount /cache"
Bootloop! Sometimes showing just the white Google logo, sometimes showing the rolling colors for a few seconds.
Recovery mode, erase user data (no backup, hate this thing). Again plenty of error msg "E:failed to mount /cache"
Could the missing /cache be related to Avast since the first reboot occurred while it was running? Maybe the theft protection is overly proctective?
Installed Nexus Root Toolkit 1.8.4 (extremely well done utility btw, ***huge congrats*** :good on Win 7 64bits. Installed drivers #1.
Tried flashing a clean 4.4.4 (nakasi-ktu84p-factory-76acdbe9).
FAILED (remote: Bootloader is locked.)
Successfully unlocked bootloader with NRT. Restart with an open lock below the white Google logo. So far so good.
Try flashing 4.4.4 again, same image.
writing 'bootloader'... FAILED (remote: (InvalidState))
What the heck ?!
Found the thread #2573015 I was quoting above on corrupt bootloader .img files from Google.
As it turns out, the bootloader MD5 is also WRONG in KTU84P.
Managed somehow to restart into bootloader again in spite of the bad bootloader...
Maybe the old one was not completely replaced yet?
Quick quick, let's try flashing another bootloader that works !
This time use the latest available with a non-corrupt bootloader .img : 4.4.0 (nakasi-krt16s-factory-da7dee49)
erasing 'boot'... blahblah
sending 'bootloader' (2100 KB)... OKAY [ 0.281s]
writing 'bootloader'... *** STUCK ***
Wait and wait until lost hope
Tried rebooting but nothing happens, just black screen, I end up with the symptoms I described upfront.
When plugged into the pc, keeping power button down makes windows beep, and the "APX" unknown device comes and goes in win device manager. Adding the vol+ or vol- buttons (or both) produces identical results.
Uninstalled APX device from PC. Power button down. Windows beeps "unknown usb device". "APX" shows up again in device manager... And so on.
Screen still pitch black.
Any other USB driver I can try to regain a working connection?
Worth looking into other remedies, like nkFlash?
GedBlake said:
If you corrupt, or erase the bootloader... the Nexus 7 is dead, from which there is known recovery. Although it's been speculated that an nvFlash tool could flash a new bootloader.
Click to expand...
Click to collapse
Thanks for reading me so far, I know it's long, but if you've read to this point maybe you can help?

What a similar story
this is such a coincidence as I have also had the dreaded bad to worse stage as my story started off here http://forum.xda-developers.com/showthread.php?t=2783631 and then got much worse and it continues here http://forum.xda-developers.com/showthread.php?t=2798181 .
I have been searching on the internet for the last month and so far there does not seem to be any general solution (which does not require hardware device surgery) to this particular type of problem as it is not something Google appear to have expected. I found that a lot of people seem to say its hypothetically possible to repair this thing via software means as that is how it was rendered inoperable in the first place and they also say it is not practically possible to hard brick any device through software means although with the nexus 7 there seems to be some kind of issue with crypto-signing which makes it a nightmare to access the hardware through nvflash unless there was some blob file made before hand
I am currently discussing the situation in this thread and you could join it to keep up to date
http://forum.xda-developers.com/showthread.php?t=2798181&page=2

[Q] Nexus 4 doesn't reboot, after cache wipe ot hard reset

Hi,
I am sorry if it's a repetition of something that has already been posted but after a search, I didn't find anything that could answer to my question.
My nexus 4 suddenly got a lot of android errors (like ".com.google.android.something" stopped to work and press ok - the something was something related to the OS of the phone, I don't think it's the first time I've seen it but if I've elready seen it, I usually press ok which lock the phone, I unlock it and it's fine) like 20 times or more and decided to switch off the phone after that because the error messages didn't stop to occur each time I press ok.
I wanted to switch on the phone but it never boots, it stays at the 4 coloured circles that mix to become white and separate and mixing again, etc.
I left it like that for several hours after trying to switch it off an on several times, nothing changes. When I start it on recovery mode, I have the android on the back with a exclamation mark on the red triangle.
I tried to restart bootloader and to start it like that, same result. I tried to wipe the cache and even to do a hard reset, nothing changed. I think the phone wiped data but failed to restart, having errors like (after wipping the cache) :
"E:failed to mount/cache (invalid argument)
E: can't mount / cache / recovery / log
E: can't mount / cache / recovery / log
E: can't mount / cache (invalid argument)
E: can't mount / cache / recovery / last_log
E: can't mount / cache / recovery / last_log
E: can't mount / cache (invalid argument)
E: can't mount / cache / recovery / last_install
E: can't mount / cache / recovery / last_install
Cache wipe complete [Yeeees !!]
E: can't mount / cache / recovery / log
E: can't mount / cache / recovery / log
E: can't mount / cache (invalid argument)
E: can't mount / cache / recovery / last_log
E: can't mount / cache / recovery / last_log
E: can't mount / cache (invalid argument)
E: can't mount / cache / recovery / last_install
E: can't mount / cache / recovery / last_install
E: can't mount / cache (invalid argument) "
And when doing a hard reset, I get the same errors (I read and I didn't find something different but I may have missed something), obviously without the "Cache wipe complete".
I looked online and saw I could do some things using a toolkit but my phone is not recognized by my computer (I tried on several computers and it's not recognized, even by computers which used to recognize it as a phone !). But when I go to "devices and printers", the phone is recognized as "Nexus 4" but the computer considers it at a medi player (??) and says it works properly but I can't access to anything on it (it only appears there, not a storage device).
I tried to intall drivers but when I plug the phone after having intalled them, it's still not recognized. Plus, I don't think the USB debugging thing is authorized in my phone (and I can change that since I can't start the phone) and even if I do the manipulations with the phone allowing it to start as fastboot mode to be recognized by the toolkit, the toolkit still doesn't find it. The device manager doesn't find my phone (says the device doesn't work properly) and installing the drivers manually (looking manually for the folder where they are) doesn't work either.
I am stuck with my phone that doesn't start, the hard reset doesn't seem to work and I can't do anythink using any toolkit or so since any attempt I tried for the phone to be recognized by the computer didn't work.
I am a newbie about android and doing stuff with the computer (I read some useful guides about how everything works, etc. and that's why I tried to use a toolkit, at first to do a hard reset from the toolkit ot use a image of the phone to be like a brand new one) so I may have missed something. Could someone suggest me something to do and maybe know why the phone isn't recognized by computers ?
Many thanks for your help anyone could provide. Plus I'm looking for a job and doing that without a phone is just THE HELL.

I would try to flash the factory image in fastboot. Start by googling 15 second adb install xda. That'll setup fastboot on your pc and hopefully your device will be recognized
Sent from my Nexus 5 using XDA Free mobile app

Many thanks for your answer jd1639.
I think I found it with a very nice guide and I will try it very shortly. I really hope my phone will be recognized by the toolkit after that
My apologizes to ask that again but do you think it's possible to repair my phone if I do everything right ? I am really worried and it's like each phone I have had problems...

It honestly depends on the problem. This kind of error looks like it could either be a hardware related issue (Bad Memory Chip), or simply a broken filesystem. If it is a broken filesystem, flashing the stock image will do the trick and your device should be functioning normally. If it is a hardware issue, unfortunately you will need to RMA the device.
Sent from my Nexus 4 using XDA Free mobile app

lolcakes203 said:
It honestly depends on the problem. This kind of error looks like it could either be a hardware related issue (Bad Memory Chip), or simply a broken filesystem. If it is a broken filesystem, flashing the stock image will do the trick and your device should be functioning normally. If it is a hardware issue, unfortunately you will need to RMA the device.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
RMA the device ? What does RMA stands for ?

AsamiyaL said:
RMA the device ? What does RMA stands for ?
Click to expand...
Click to collapse
Warranty it. http://en.m.wikipedia.org/wiki/Return_merchandise_authorization
Sent from my Nexus 5 using XDA Free mobile app

Thanks Lolcakes203.
I tried to use the 15 second adb install xda and it seems still not to work, there is no change on how the phone is recognized. I haven't read all the pages of the thread about it - maybe someone had the same problem than I am having.
I got a temporary phone and stopped to try to repair the N4 for a moment since I was quite busy but I am continuing to try to fix it.
Do you think switching cables could help ? I tried with two without success but with other drivers, maybe switching the cables could do something ? I am looking for new things to try. I will make sure I have tested all the drivers (even if I already tested all what I have) and will post again the result. Bou has someone any idea about what to do next if the drivers still don't allow the phone to be recognized as a phone ?
Many thanks everyone

Your emmc chip is fried... Take the phone back to LG electronics
Sent from my Nexus 4 using XDA Free mobile app

Hello,
Thanks jd1639 and arkangel72
I cannot give it back to LG because I changed the screen a few months ago. They will not accept to repair it or to do anything on it.
Do you think something by changing the screen may have gone wrong to provoke what happened ? arkangel72 spoke about fried emmc chip, may it have been provoked by something from screen change ?
The phone have worked maybe like 1 or 2 months before dying up to now.
I saw some people changing their chip but I cannot do it. A screen or any other part is fine but nothing from the mothercard.... A mothercard is very expensive...

See.. A bit of nexus 4 devices have this problem.. Their emmc chip is bad.. I don't know why or how that happens.... But yes.. That causes a flash write failure...
Sent from my Nexus 4 using XDA Free mobile app
---------- Post added at 08:21 AM ---------- Previous post was at 08:19 AM ----------
But still try to flash the stock firmware.. From fastboot mode... Look up the guide.. How to flash stock on nexus 4
Sent from my Nexus 4 using XDA Free mobile app