LG L40 D160 qusb_bulk, hard brick, formatted partition - General Questions and Answers

Hello,
my phone did not boot after flashing. The only thing I saw was a purple screen with an error message, so I connected my L40 to my Windows 8.1 computer. My PC recognized my mobile as a usb mass storage, but it was write protected. Stupidly I deleted the partition using disk part. That worked perfectly. I thought it would not matter if I deleted a partition. It was only a few kilobytes in size.
Unfortunately my phone did not boot anymore after that.
In the device manager, it' s shown up as qusb_bulk.
Is there any way to fix the issue, so my phone will be able to boot up again?
I sincerely appreciate all your help.
Daniel03s

Daniel03s said:
Hello,
my phone did not boot after flashing. The only thing I saw was a purple screen with an error message, so I connected my L40 to my Windows 8.1 computer. My PC recognized my mobile as a usb mass storage, but it was write protected. Stupidly I deleted the partition using disk part. That worked perfectly. I thought it would not matter if I deleted a partition. It was only a few kilobytes in size.
Unfortunately my phone did not boot anymore after that.
In the device manager, it' s shown up as qusb_bulk.
Is there any way to fix the issue, so my phone will be able to boot up again?
I sincerely appreciate all your help.
Daniel03s
Click to expand...
Click to collapse
Try this thread, follow only the instructions, do not use files from that thread, find the equivalent files for your specific model number/firmware.
Sent from my SM-S903VL using Tapatalk

Related

NEXUS S bricked? Can't be detected on PC

Hi everyone,
I have a Nexus S i9020T that I think I have bricked. What I did is that I was trying to flash a ROM and by mistake I formatted the SD, and USB storage. And since then when I reboot, I only see the GOOGLE sign with a blue bar underneath. I have the clockworkmod working for me but I can't mount my USB storage or SD card to copy any files from computer because the computer does not detect it. I installed ADB properly, and I had PDAnet installed as well. but for some reason when I try to open PDAnet, it gives me errors and asks for reinstallations as there are files that are in conflict or something. and now I have a device that can't be detected on computer but can be rebooted in to recovery. I will be grateful if one of you guys helped me out with this.
here are drivers maybe different than what you have

[Q] please help me recover files off of a broken screen/digit. galaxy s vibrant

Okay well my screen and digitizer are broken. I'm pretty sure I left usb debugging mode always on. I tried downloading kies and plugging it in, but got a connection error saying that the device wasn't in kies mode so it couldn't recognize it.
Also, the internal sd is not visible from my computer, although the computer does play the sound recognizing it being plugged in and trying to download the drivers. Indicating that the sd isn't mounted for access through the computer.
So my problem is, how can I possibly get any internal sd data at this point? I was thinking maybe adb but I'm clueless as to how I would go about doing that. Not to mention, I'm not even sure if adb is the solution I'm looking for...if there is one. Would adb still work even since the computer isn't recognizing it in "my computer"?
My phone is rooted and running some old rom that I don't remember. I had clockwork and voodoo if that even matters.
I know sorry for being a noob. Any help is appreciated
sorry for the double post, but this is a large active forum. 200 views and no answers? I know somebody on here knows the answer to my problem. Tell me if I should post in a different section...
I'm recycling my phone and really want my data that's on the sd and then wipe it after.
Download drivers to Pc. Then see if it can connect. Also I assuming your phone uses Odin. Try putting phone in download mode
Sent from my SPH-D710 using xda premium
tonomon said:
sorry for the double post, but this is a large active forum. 200 views and no answers? I know somebody on here knows the answer to my problem. Tell me if I should post in a different section...
I'm recycling my phone and really want my data that's on the sd and then wipe it after.
Click to expand...
Click to collapse
You will have to try and get your PC to see your device. If you can't then you are out of luck. This is the big problem with only having internal storage and no SD card.
thanks for the replies. Okay so I have the drivers installed. I installed kies and tried connecting that way but it wouldn't connect saying that the phone wasn't in kies mode (and I have no way of doing that with the broken screen).
I tried setting up adb and droid explorer. Droid explorer said my phone had around 300kb of data on it. The sd card folder was a "link" with a small data size. None of the folders or files were found when clicked on in droid explorer.
Any options at this point?
tonomon said:
thanks for the replies. Okay so I have the drivers installed. I installed kies and tried connecting that way but it wouldn't connect saying that the phone wasn't in kies mode (and I have no way of doing that with the broken screen).
I tried setting up adb and droid explorer. Droid explorer said my phone had around 300kb of data on it. The sd card folder was a "link" with a small data size. None of the folders or files were found when clicked on in droid explorer.
Any options at this point?
Click to expand...
Click to collapse
Got the same problem as you did, just with a samsung galaxy s3, and I have tried all the things listed in this thread, with no luck. Did you find a solution to this?

[Q] Still no access to internal phone via usb

Hi all,
To start with, I'm in India and tried to unlock my Verizon S3.. at first, got it rooted, tried to unlock, didn't work and it caused a bunch of connection problems, etc. with the phone, so I did a factory reset, thinking it would wipe the problems I was having.
Lost some files I forgot were on my internal memory I needed, so I wanted to do a file recovery. During this process, I re-downloaded the drivers for the S3 I needed and then found that my phone would connect, but wouldn't connect as a driver and only as a media source. So the recovery software can't find the device to inspect. Even when I debugged, it would only register as a bootloader and wouldn't recognize it as anything more.
I'm trying to figure out what other steps I need to take to either remove something that I tampered with before the factory reset, or if I need to install something new to configure my device to register as a driver, or do something else I can't figure out?
And I'm still trying to recover those files from before the factory reset too.
Anyone have any suggestions? I can explain in more detail if needed.
Thanks for all the help!
Are you trying to recover personal files that were wiped?
Sent from my SCH-I535 using xda app-developers app
Trying to get my computer to register the phone as a driver so then I will be able to recover the files.
djteotancolis said:
Are you trying to recover personal files that were wiped?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You may be out of luck. When google went to Android 4.x, they switched to the MTP protocol which mounts the phone to the computer as a media device, rather than a mass storage device (as in previous versions of Android). As far as I can tell, devs have only been able to figure out how to get the external SD card to be seen as mass storage (and that's built into a rom, not a stand alone mod, I believe).
Is there any file recovery software/app available for Android that you can install directly on the phone, rather than needing to run it from a computer?
Well, that's not a good sign. But I will check into the direct software to the phone and let you know I find anything.
Thanks for the tip!
letinsh said:
You may be out of luck. When google went to Android 4.x, they switched to the MTP protocol which mounts the phone to the computer as a media device, rather than a mass storage device (as in previous versions of Android). As far as I can tell, devs have only been able to figure out how to get the external SD card to be seen as mass storage (and that's built into a rom, not a stand alone mod, I believe).
Is there any file recovery software/app available for Android that you can install directly on the phone, rather than needing to run it from a computer?
Click to expand...
Click to collapse

[Q][Urgent] "Zeus Flash Device" > hardbrick?

Excuse me in advance, for some reason XDA won't save it when I put an enter in this message, it pasted everything into one big text. It's hard and annoying to read. I'm sorry!
Edit: fixed it by typing HTML codes
A few weeks ago I ordered a (micro) SD-card in China, it arrived two days ago.
I backed up the internal storage and external SD from my phone, then replaced the ext-sd with the new Chinese 32gb card, and switched the internal and external memory as per @TeamMex 's thread.
(Of course using the CM10 mountpoints as I was on the PureCyanogenmod+ ROM).
Then I tried to restore my apps with TitaniumBackup, but I found out that the apps now installed on the SD (the 32gb Chinese card that is mounted as internal storage) kept disappearing after a reboot, having me to restore them again.
This also happened most of the time with reinstalling via playstore, and then restoring the data via TiBu.
I figured it might be a disk issue, so I tried fixing the sdcard with windows disk repair, and even linux' "dosfsck", but nothing really happened and the card kept acting strange.
So I was trying to correctly format it via the phone itself, but then it didn't mount anymore. I decided to pull out the card and restore it via a card-reader, hoping that would finally work, so I pulled the battery out of my phone, and pulled the card out.
And now here it comes: I tried to turn on my phone, but it didn't do anything, no led, no screen, no vibration.
I decided to plug it to my PC to see if it did anything, but the phone itself did nothing.
Yet, although I didn't click anything on the phone, the PC started to install drivers, later they turned out to be called "ZEUS flash device" drivers.
As far as I found on google up till now, I've read that means I probably have a hard brick.
Is there any other reason for my phone to list the "ZEUS flash device" drivers or not?
Anyway to restore my phone from here, as it still installs drivers to my PC, meaning there must be some tool that can flash something to it, or is it dead?
I hope someone can help me or explain more of my situation.
Phone: Sony Xperia Tipo, ST21i
ROM: PureCyanogenmod+
PC OS: Windows 7 & Ubuntu 12.10 dual-boot
Thanks in advance,
Regards, Drago
Dragoboss said:
Excuse me in advance, for some reason XDA won't save it when I put an enter in this message, it pasted everything into one big text. It's hard and annoying to read. I'm sorry! A few weeks ago I ordered a (micro) SD-card in China, it arrived two days ago. I backed up the internal storage and external SD from my phone, then replaced the ext-sd with the new Chinese 32gb card, and switched the internal and external memory as per @TeamMex 's thread. (Of course using the CM10 mountpoints as I was on the PureCyanogenmod+ ROM). Then I tried to restore my apps with TitaniumBackup, but I found out that the apps now installed on the SD (the 32gb Chinese card that is mounted as internal storage) kept disappearing after a reboot, having me to restore them again. This also happened most of the time with reinstalling via playstore, and then restoring the data via TiBu. I figured it might be a disk issue, so I tried fixing the sdcard with windows disk repair, and even linux' "dosfsck", but nothing really happened and the card kept acting strange. So I was trying to correctly format it via the phone itself, but then it didn't mount anymore. I decided to pull out the card and restore it via a card-reader, hoping that would finally work, so I pulled the battery out of my phone, and pulled the card out. And now here it comes: I tried to turn on my phone, but it didn't do anything, no led, no screen, no vibration. I decided to plug it to my PC to see if it did anything, but the phone itself did nothing. Yet, although I didn't click anything on the phone, the PC started to install drivers, later they turned out to be called "ZEUS flash device" drivers. As far as I found on google up till now, I've read that means I probably have a hard brick. Is there any other reason for my phone to list the "ZEUS flash device" drivers or not? Anyway to restore my phone from here, as it still installs drivers to my PC, meaning there must be some tool that can flash something to it, or is it dead? I hope someone can help me or explain more of my situation. Phone: Sony Xperia Tipo, ST21i ROM: PureCyanogenmod+ PC OS: Windows 7 & Ubuntu 12.10 dual-boot Thanks in advance, Regards, Drago
Click to expand...
Click to collapse
uhmm try using other SD card and other usb port,
maybe ur sd card was damaged since you sent it
flashtools is used to repair the phone, if that does not work you will have to go to a technician to use medussa box
cheers.
either medusa or setool box, setool also has the bootloader specifically for this qualcomm chipset, so you can reflash if you have access to a setool box.
Steam. said:
either medusa or setool box, setool also has the bootloader specifically for this qualcomm chipset, so you can reflash if you have access to a setool box.
Click to expand...
Click to collapse
i got same problem with my xperia v , sane exactly , where can i download SETool Box ? i downloaded SETOOL and it didnt detected my device please help, thanks
iSpammer said:
i got same problem with my xperia v , sane exactly , where can i download SETool Box ? i downloaded SETOOL and it didnt detected my device please help, thanks
Click to expand...
Click to collapse
It's only purchasable.
Sent from my HTC Desire HD using Tapatalk

Fixed Hard Brick But No Recovery or Download mode

I posted this in the stickied thread, but I'm kind of in a hurry to receive a fix. After fixing my bricked phone it won't enter recovery mode or download mode. It's also having connection issues with Odin, even though it says the device is connected.
I followed this guide to fix it:
http://forum.xda-developers.com/showthread.php?p=50128942
The original brick was caused by installing and using EZ Unlock 1.2 before checking all the facts. I didn't know about the bootloader on the 4.3 at the time. I'm just going to copy and paste what I already wrote in the other thread.
I'm having a few problems still. My phone is up and running and it's rooted using saferoot. Which is all good, but now I can't get into recovery mode or download mode. They both start up. When I enter recovery mode I get the blue text in the top left hand corner, but then the phone just starts up like normal. When I enter download mode the screen flashes the screen for a second before turning off and starting the phone normally.
Also, when I connect my phone to the computer everything works like it should, but when I enter Odin while it says it adds my device when I try to install the stock rom it never connects to the phone and installs it. It just hangs there waiting for the connection.
I have a question about restoring the bootloader and recovery image as well. I downloaded the debrick file and it shows up with the bin extension, but for some reason it wants to use VLC media player to open it. I wrote it to the 16 GB card and it shows up on the card as a folder called "image" with lots of files in it. Nevertheless it worked and my phone booted up.
Then I follow the directions, as best as I can with my inept knowledge of all this. I put the stock bootloader and recovery image on the card (not at the same time) and then put the code in using Terminal Emulator. Here's where I'm confused though.
The first time I moved the debrick folder and the recovery image manually to the phone storage and then entered the codes. Again, one at a time.
The second time I put the files on the external 16 GB card and left them there. Then I put in the codes and then I plugged the phone back into the computer and deleted the originals on the external card.
Either way the phone works. Mostly. I have a feeling I'm doing something wrong and that's why recovery and download mode won't work.
The instructions also say to keep the debrick.bin file on the external card. Do I keep the actual image folder on the card or the file as it was downloaded? Because even after I deleted the debricked image folder off the card it says there isn't any room on there for the file. I formatted the card at a point but when I put it back in the phone it was bricked again.
I hope someone can help me with this. I'd really appreciate it!
lgfuad said:
I posted this in the stickied thread, but I'm kind of in a hurry to receive a fix. After fixing my bricked phone it won't enter recovery mode or download mode. It's also having connection issues with Odin, even though it says the device is connected.
I followed this guide to fix it:
http://forum.xda-developers.com/showthread.php?p=50128942
The original brick was caused by installing and using EZ Unlock 1.2 before checking all the facts. I didn't know about the bootloader on the 4.3 at the time. I'm just going to copy and paste what I already wrote in the other thread.
I'm having a few problems still. My phone is up and running and it's rooted using saferoot. Which is all good, but now I can't get into recovery mode or download mode. They both start up. When I enter recovery mode I get the blue text in the top left hand corner, but then the phone just starts up like normal. When I enter download mode the screen flashes the screen for a second before turning off and starting the phone normally.
Also, when I connect my phone to the computer everything works like it should, but when I enter Odin while it says it adds my device when I try to install the stock rom it never connects to the phone and installs it. It just hangs there waiting for the connection.
I have a question about restoring the bootloader and recovery image as well. I downloaded the debrick file and it shows up with the bin extension, but for some reason it wants to use VLC media player to open it. I wrote it to the 16 GB card and it shows up on the card as a folder called "image" with lots of files in it. Nevertheless it worked and my phone booted up.
Then I follow the directions, as best as I can with my inept knowledge of all this. I put the stock bootloader and recovery image on the card (not at the same time) and then put the code in using Terminal Emulator. Here's where I'm confused though.
The first time I moved the debrick folder and the recovery image manually to the phone storage and then entered the codes. Again, one at a time.
The second time I put the files on the external 16 GB card and left them there. Then I put in the codes and then I plugged the phone back into the computer and deleted the originals on the external card.
Either way the phone works. Mostly. I have a feeling I'm doing something wrong and that's why recovery and download mode won't work.
The instructions also say to keep the debrick.bin file on the external card. Do I keep the actual image folder on the card or the file as it was downloaded? Because even after I deleted the debricked image folder off the card it says there isn't any room on there for the file. I formatted the card at a point but when I put it back in the phone it was bricked again.
I hope someone can help me with this. I'd really appreciate it!
Click to expand...
Click to collapse
Try to use Odin to flash a full stock 4.3 rom again with PIT file. This should reinstall the stock recover. Pit file can be found here http://forum.xda-developers.com/showthread.php?t=2586319
termCuvi Henry
buhohitr said:
Try to use Odin to flash a full stock 4.3 rom again with PIT file. This should reinstall the stock recover. Pit file can be found here http://forum.xda-developers.com/showthread.php?t=2586319
Click to expand...
Click to collapse
Thank you for your help!
I tried your suggestion twice but it wouldn't work. It still gets stuck at SetupConnection.
You have multiple issues going on here.
First thing you should do is make sure your drivers are up to date and you're using a good cable and USB port on your computer. That may fix your issue with it not being recognized, all of those can cause problems.
To clarify your issue with the hardbrick restore method, it's working like it should. It's being recognized as a vlc media file because vlc is set to detect .bin files and this has nothing to do with the function of the file. The debrick image is an actual image that is written by win32, and it's designed to make the phone work around the initial bootloader problem and boot from that source. Since the boot image is now on your external SD card, as soon as you take it out your phone can't boot anymore. This is why it's a much larger file structure than just the .bin file. This may be the issue with your phone. Now on to your other issue.
In that guide there is a section to rewrite the image to your internal card with terminal emulator underneath the initial post. If you do that you wouldn't need the external SD card, and it may fix your connection issue with Odin.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
You have multiple issues going on here.
First thing you should do is make sure your drivers are up to date and you're using a good cable and USB port on your computer. That may fix your issue with it not being recognized, all of those can cause problems.
To clarify your issue with the hardbrick restore method, it's working like it should. It's being recognized as a vlc media file because vlc is set to detect .bin files and this has nothing to do with the function of the file. The debrick image is an actual image that is written by win32, and it's designed to make the phone work around the initial bootloader problem and boot from that source. Since the boot image is now on your external SD card, as soon as you take it out your phone can't boot anymore. This is why it's a much larger file structure than just the .bin file. This may be the issue with your phone. Now on to your other issue.
In that guide there is a section to rewrite the image to your internal card with terminal emulator underneath the initial post. If you do that you wouldn't need the external SD card, and it may fix your connection issue with Odin.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for your help.
The drivers are new, but I could try re-installing them. It comes up fine on the computer though, just not in Odin.
I did move both files to the internal card and removed them from the external SD card already. I think it worked since the phone starts up, it just won't let me into either mode. Could I have caused all this when I moved them?
lgfuad said:
Thank you for your help.
The drivers are new, but I could try re-installing them. It comes up fine on the computer though, just not in Odin.
I did move both files to the internal card and removed them from the external SD card already. I think it worked since the phone starts up, it just won't let me into either mode. Could I have caused all this when I moved them?
Click to expand...
Click to collapse
No it wouldn't, if you can get it to boot you should be good.
Not sure why you aren't able to get into download mode.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No it wouldn't, if you can get it to boot you should be good.
Not sure why you aren't able to get into download mode.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Oy. I don't know what to do. Is there another way to get into download or recovery mode beside the three button method?
Last night I used Titanium Backup to wipe user and system apps and cleared the cache, but it didn't help. I guess I'm going to try a factory reset through the settings menu. Hopefully that will do something?
lgfuad said:
Oy. I don't know what to do. Is there another way to get into download or recovery mode beside the three button method?
Last night I used Titanium Backup to wipe user and system apps and cleared the cache, but it didn't help. I guess I'm going to try a factory reset through the settings menu. Hopefully that will do something?
Click to expand...
Click to collapse
You can download terminal emulator and type in this code to boot, I think you have to be rooted.
Su
reboot download
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
You can download terminal emulator and type in this code to boot, I think you have to be rooted.
Su
reboot download
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I did a factory reset and re-rooted, but it didn't fix anything.
Thank you for your suggestion! Unfortunately I keep getting this error.
sh: download: not found

Categories

Resources