Need help with bricked LG MS323 L70 - Android Q&A, Help & Troubleshooting

Hi all, I will try to be as detailed as possible.
I have a MetroPCS LG MS323 which I bought as a second phone to use when I travel as my regular phone is CDMA and I wanted a GSM phone that I could use with a sim card. While on an overseas trip I paid a cellphone place to unlock the phone so I could use other carriers' sim card, it was working fine since then. However, as I don't use the phone on a regular basis it ended up sitting and the battery lost its charge. When I tried to charge it by usb, it started bootlooping (vibrate, LG logo, repeat). After that I pulled the battery and charged it using an external charger. The phone is not rooted. I tried the factory reset key combo, but it gets stuck on the screen which says factory reset processing........ endlessly. I tried to download kdz file and flash with LG flash tool but phone cannot get into download mode. When I press vol key and plug usb cable, it says LOADING.......... press volum up key until download mode starts But it gets stuck there and download mode never starts.
I downloaded adb and fastboot to a Windows 7 laptop, and LG drivers, but when I connect phone and open a terminal adb devices shows no phone connected.
I also downloaded Laf.img for this phone and Laf recovery tool for Windows but again I cannot seem to get computer to see the phone. If I try to use the tool it says "waiting for device"
One difficulty is to trying to plug phone to computer the right way.
Most of the threads say to have phone in battery charge mode with usb debugging enabled, but I can't select any settings if the phone is bricked.
If I just plug the phone to usb when it is turned off it shows a picture of battery but no sign of charging, and computer doesn't detect phone.
If I plug phone to usb first, then hold vol and power key the LG logo will go black and it vibrates, in that case sometimes the Windows laptop will see 2 folders, verinfo and image.
When I plug usb cable to Linux computer and phone is off, same thing just picture of battery but terminal only shows sda1 sda2 sda3 etc no sdb no sdc just like not detected.
If I hold vol down then plug usb it vibrates and stuck on LG logo.
I have also tried to plug usb, then press vol down and power until phone vibrates, then try to let go buttons before LG logo shows up. but it doesn't mount.
If I hold vol up and power, then plug usb. it vibrates and goes to LG logo.
Last night somehow I got it to mount on the linux computer but the file manager was going crazy opening multiple windows and a list of folders would show up for a second, disappear and reappear as if the system was trying to read the folders but having difficulty. Today I am not able to get it to mount.
I have downloaded a linux livecd with adb and fastboot, I haven't tried it yet because I am not sure the path to flash an img file from a different directory on the hard drive on the windows laptop.
I have downloaded aboot.img but don't know how I can flash it if I can't see the phone on any computers.
I have spent days searching for solutions but have not seen the exact same problem, other threads suggest things but often the symptoms are slightly different or with a different phone. So, first of all I need to know what kind of brick I have, because other solutions I have seen posted for completely black screen, or phone detected as qhsusb qualcomm etc. which seems like a different problem.
So the 2 main things are 1, to know which kind of brick because many of the solutions I see posted seem like a different problem.
second, what is the best way to plug to computer so I can see the phone?

I burned a live CD of FWUL and ran adb from linux, still says adb devices nothing shows up. usb cable is plugged in and phone is turned off. Am I doing this wrong? I held down power and vol down until phone vibrates and LG logo appears. adb devices - "list of devices attached" still has nothing showing.. I don't know why even in Linux I can't see any device attached. Also I tried with pressing vol up and power until phone vibrates.
ls /dev/sd* only shows sda sda1 sda2 etc
I have also looked at past threads about unlocking the L70 bootloader, but the bootloader.zip no longer links and the phone does not have busybox installed.
I tried to see it Windows Device Manager but it does not show up anywhere.

This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.

equitube said:
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
Click to expand...
Click to collapse
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
A tiny bit of progress to report, after getting a perfect timing to release the power and vol down keys I was finally able to connect to Windows machine. while waiting for drivers to install it was detected as QHSUSB_BULK in device manager, after drivers loaded now it is listed as LGE AndroidNet USB Serial {port (COM4). However when I run adb I still cannot see an attached device. I will look at solutions for the specific type of brick problem which has now been identified.

fofopuka said:
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
Click to expand...
Click to collapse
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r

equitube said:
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
Click to expand...
Click to collapse
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.

fofopuka said:
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
Click to expand...
Click to collapse
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.

equitube said:
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
Click to expand...
Click to collapse
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?

fofopuka said:
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
Click to expand...
Click to collapse
Of course, I had forgotten about that. In order to use fastboot, most flashing tools, you HAVE to have USB debugging on.
There are occasional ways around this, though they are few. I do seem to recall oding it on that LG Leon. OR it may have been a Moto e or G, let me look back at previous threads i've asked for help in.
(Hmm, perhaps taking notes, or just leaving a webcam running while I'm doing a new device might be valuable in the future, I think with remarkable hindsight.) :cyclops:
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
And no, you can't do anything to Android files in Windows, except see them. they are generally a different file system

One of the difficulties is just plugging it to a PC. 9 out of 10 times it is not recognized and nothing happens. So far the only way that seems to occasionally work is to plug the usb cable to the Windows 7 laptop, hold vol down and power, release both as soon as it vibrates. Most of the time I can't get it timed exactly right, but if I'm lucky sometimes Windows will detect the usb connection by following these steps. If I try on a Linux machine nothing happens, phone stays invisible. The most I've gotten with Linux is to charge the battery, but will not mount.
It is just a stock phone, not rooted, no busybox, no developer options enabled.

Related

Hero USB Connection Not Recognized

Hi all
I have a problem with my hero not being recognized by my PC. This happened after a weekend trip and i charged the phone with iphone USB adapter as i lost my one and now after returning from my trip i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message.
Also my Amon_Ra recovery i used has been wiped and i cant get into recovery or install any rom at all.
I am thinking this might be the same USB brick that affected some Desire owners but i am not sure.
So please if anyone can help me, please do.
Thanks in advance.
fizzle101 said:
Hi all
I have a problem with my hero not being recognized by my PC. This happened after a weekend trip and i charged the phone with iphone USB adapter as i lost my one and now after returning from my trip i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message.
Also my Amon_Ra recovery i used has been wiped and i cant get into recovery or install any rom at all.
I am thinking this might be the same USB brick that affected some Desire owners but i am not sure.
So please if anyone can help me, please do.
Thanks in advance.
Click to expand...
Click to collapse
this happen to me. What i did was switch my phone off, plug in the usb and switched it back on. then wait for windows to say it not recognised. then go to to device and printers and uninstall the drivers for the phone. Disconnect and reconnect the usb back to the phone and it it will pick it up.
Can you try booting in fastboot and tell me if that is recognized?
it still doesnt recognize it in fastboot
fc_Kuro said:
this happen to me. What i did was switch my phone off, plug in the usb and switched it back on. then wait for windows to say it not recognised. then go to to device and printers and uninstall the drivers for the phone. Disconnect and reconnect the usb back to the phone and it it will pick it up.
Click to expand...
Click to collapse
i have tried that and it doesnt help
fizzle101 said:
i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message
Click to expand...
Click to collapse
Sounds like its just a driver issue. Have you tried plugging it in, when you get that message open DEVICE MANAGER,... Find the yellow "!", right click it, uninstall, unplug phone, reboot PC.
.... Then use BTDAG's [Guide] How to Setup Correct Hero Drivers (for x86 & x64 users)
I hav the same problem. In recover mode it works but then turn on the phone, there is no popup options as before. Tried around with drivers but didnt work either. But found a solution which is very convenient. I dont know if it works on other ROM versions but I'm on 2.1 (Villain10).
- Install extended control widget (dont remember where I got it but you can google, it seems I cannot find it on the market)
- Add this widget to the home screen: Menu/Add to Home/Widget/ Extended Control bar (you can choose the size from 1x1 to 1x4) then select "Mass storage" at the bottom, apply.
Now you have a widget to turn on/off USB storage. When you connect Hero to the PC, just click on this widget then the PC will connect to the SD card, and click one more to turn it off.
ok i will give that a try
crk23 said:
I hav the same problem. In recover mode it works but then turn on the phone, there is no popup options as before. Tried around with drivers but didnt work either. But found a solution which is very convenient. I dont know if it works on other ROM versions but I'm on 2.1 (Villain10).
- Install extended control widget (dont remember where I got it but you can google, it seems I cannot find it on the market)
- Add this widget to the home screen: Menu/Add to Home/Widget/ Extended Control bar (you can choose the size from 1x1 to 1x4) then select "Mass storage" at the bottom, apply.
Now you have a widget to turn on/off USB storage. When you connect Hero to the PC, just click on this widget then the PC will connect to the SD card, and click one more to turn it off.
Click to expand...
Click to collapse
that didnt work. o well i guess i am stock with the rom i have there.
fizzle101 said:
that didnt work. o well i guess i am stock with the rom i have there.
Click to expand...
Click to collapse
i've got this problem once and it was as simple as the cable was damaged...
i changed the cable and since then, everything works try that.
robocik said:
i've got this problem once and it was as simple as the cable was damaged...
i changed the cable and since then, everything works try that.
Click to expand...
Click to collapse
i have tried everything. changed the cable, used different pc but nothing works. i think is a hardware problem, something might be broken inside or something like that
Did you ever got this solved? I have the same problem only i use stock rom 2.1 Hero.. driving me nuts ...
baklap said:
Did you ever got this solved? I have the same problem only i use stock rom 2.1 Hero.. driving me nuts ...
Click to expand...
Click to collapse
No i havent and i gave up trying because i dnt think there is a fix for it. if yours is unrooted and the warranty is still valid you should consider returning it to HTC maybe they might replace it
got the same problem. Any solution so far ??
ddotpatel said:
Sounds like its just a driver issue. Have you tried plugging it in, when you get that message open DEVICE MANAGER,... Find the yellow "!", right click it, uninstall, unplug phone, reboot PC.
.... Then use BTDAG's [Guide] How to Setup Correct Hero Drivers (for x86 & x64 users)
Click to expand...
Click to collapse
Did you try that?..... You need to do the reboot PC/Laptop after uninstalling ALL HTC drivers! Then when you reboot PC, plug phone back in, should say "not recognised" again,... then follow BTDAG's guide. T'is definitely a driver issue!
tried flashing 3 roms, modaco, radug and now kimera... none working.
can connect in fastboot, it shows up in device manager as android 1.0
ive tried 3 different usb cables and 4 differet pcs, still there is no response on my phone !!!
using villian rom 10.0 rite now.
okay it boots up into fastboot and fastboot usb shows up on the screen in red,
BUT when i use the "adb devices" command in adb it doesnt show the device,
it is showing as android 1.0 in devices and printers (windows 7)
You need to use....
fastboot devices
....when your are in fastboot.
What happens when you go into your recovery, select "Toggle MS/USB" with USB connected to PC?
okay
fastboot devices command shows some serial number.
then i tried adb remount, it gave an error....
enabling usb-ms with cable attached gives no response
ok i think it might be USB driver like ddotpatel said but i am not sure.
i reinstalled my whole windows 7 to 32bit now instead of the 64bit version i was using before and today i just connected my hero to my PC and windows 7 did its thing and installed the drivers and finally my hero can mount the SD card in my PC again although i kept getting this can perform faster in USB 2.0 port or something like that i didn’t care as long as i can mount my SD card again.
now went into fastboot and used the fastboot device command and i could see my hero serial no. but when i try to flash the amonra recovery i got the permission error (i cant really remember). i tried flashing using the adb method but still no luck.
so i went to market and downloaded rom manager and used it to flash clockwork recovery and now i could boot to clockwork recovery.
from this recovery i can now flash any rom i want and although there are still a few more problems i am glad now that i can flash custom roms again.
the problem i can see so far but i can deal with is
1. i don’t think fastboot commands work even if the phone is detected.
2. SD card mounts at USB 1.1 speed. (i have tried different ports and cable but still the same thing and this is the ports i use for my N1, Desire and my other android phones with USB 2.0 speed)
PS: adb commands for pushing and removing apps is working.
Hope this can be helpful to those experiencing the same problem.
Instead of re-installing your entire OS just use usbdeview to remove the failing drivers.
Also remove any old HTC Sync installs and install the latest version.

[Q] Is this thing f**ked?

Firstly I apologise if this has been covered anywhere - I read a load of posts and did a load of searches but came up empty handed about this specific issue.
I bought a Galaxy Ace (GT-S5830 Baseband:S5830NEKA3 OS:2.2.1) as a dev device and it's been working fine up until today, and at some point it decided it doesn't want to be able to connect to my computers. I've tried three different computers, two different operating systems, and ever tried installing Kies (urk) with no luck.
The phone can charge over USB, saying that it's charging over AC, but that's all that happens.
I can't boot in to recovery mode as holding the power+middle button+vol up just gives me a ramdump message.
Can anyone help me out?
Martyn.h said:
Firstly I apologise if this has been covered anywhere - I read a load of posts and did a load of searches but came up empty handed about this specific issue.
I bought a Galaxy Ace (GT-S5830 Baseband:S5830NEKA3 OS:2.2.1) as a dev device and it's been working fine up until today, and at some point it decided it doesn't want to be able to connect to my computers. I've tried three different computers, two different operating systems, and ever tried installing Kies (urk) with no luck.
The phone can charge over USB, saying that it's charging over AC, but that's all that happens.
I can't boot in to recovery mode as holding the power+middle button+vol up just gives me a ramdump message.
Can anyone help me out?
Click to expand...
Click to collapse
When phone is turned off. Press and hold home+power/lock button untill it reaches recovery menu.
Check - that works. Thanks.
I'm now unsure as to how to proceed - neither adb devices nor fastboot devices are reporting anything back.
Connect device to pc. Open device manager (windows). Remove all drivers related to the ace and Samsung.
Remove the device and reboot the pc. Then connect the device. Windows update will detect the device and install the necessary drivers. If it doesn't automatically do that then open up device manager and install them manually by right clicking on the device and selecting update drivers from internet.
From the Galaxies to your Ace...!!
Thanks for your reply.
In windows there's no sign of any Samsung or Galaxy Ace drivers. Plugging it in to my Kubuntu machine gives me identical lsusb results as when not plugged in.
Have done a data wipe, checked that USB debugging is on and tried different cables
think it's screwed.
Think I could stick a ROM on the SD card and flash it? Would that work?
Martyn.h said:
Thanks for your reply.
In windows there's no sign of any Samsung or Galaxy Ace drivers. Plugging it in to my Kubuntu machine gives me identical lsusb results as when not plugged in.
Have done a data wipe, checked that USB debugging is on and tried different cables
think it's screwed.
Think I could stick a ROM on the SD card and flash it? Would that work?
Click to expand...
Click to collapse
hmm.. kies didnt work right? So i guess only option IMO would be card reader or CWM
Yep , the phone's USB port is frayed
This was sent from a Galaxy Ace. Problem?

[Q] Huawei Vision (U8850) bricked

Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
petoxxx said:
Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
Click to expand...
Click to collapse
mine is not working i think mine is bricked completly
bricked my mobile...Help!!!!
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
sivakarthick said:
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
Click to expand...
Click to collapse
The thread called 'Problem with huawei vision' still seems to be active. You may want to try asking your question over there.
Huawei (u8850) unbricked
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
how to turn off huawei u8850 completely
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
bikeshrt said:
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
Click to expand...
Click to collapse
it's actually not difficult to remove the battery...
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Anyone here interested in developing a 3.x kernel? seems other phones with msm8255 have successfully got one...
u8850 power off
btsimonh said:
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Click to expand...
Click to collapse
now i have tried it, and no success.
However, what i have found to work - if your non-boot is actually booting the kernel, but failing to initialise the phone, then you can still use adb with it... I ran adb shell, and then used 'poweroff' to power off my phone, which then meant i could boot into CWM recovery....
i HAVE THE SAME PROBLEME? PLEASE CAN U HELP ME TO SOLVE IT BY GIVING ME DETAILS.
it is working, thank you bro
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
it is working thanks bro
Stock rom download plz.
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
HOLY GOD! F**K ME!!! I finally did it! THANKS A LOT, BRO! YOU'RE AWESOME!!!

[Q] Nexus wont boot

Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
aaronthew said:
Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
Click to expand...
Click to collapse
You can't go into your recovery?
Install ADB and try to connect your Nexus to your PC and enter "adb devices". See if your tablet is recognized like that.
How to setup ADB
Do not use toolkits with Nexus devices.
cheers for the advice but nope no luck still wont connect
aaronthew said:
cheers for the advice but nope no luck still wont connect
Click to expand...
Click to collapse
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
es0tericcha0s said:
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
Click to expand...
Click to collapse
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
aaronthew said:
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
Click to expand...
Click to collapse
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
es0tericcha0s said:
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
Click to expand...
Click to collapse
if i choose recover, to gets stuck on the google screen
Tried different cables, Pc and PC ports no luck
I could try get linux on vm when i get home? never used it thou
Sucks man. Such a random thing and not typical of most Nexus issues. This is the only other option I can think of then: http://mobiletechvideos.mybigcommerce.com/asus-nexus-7-2012/ - Brick service. These guys are legit. They have a great reputation and I've personally used their services twice (different devices) and one was fixed while the other was a lost cause, but Josh was nice enough to refund some of the money since it didn't work. I'm guessing they would need to do what's called a JTAG service where they hook up (usually solder) a special cable to a specific port on the board and it kind of circumvents the other issues and reloads the OS back on.
Thanks for all you hep mate will prob give them a try
No problem. Good luck!

Question Did I brick my phone?

I seem to have gotten my N200 in a state where it will not power on. No screen display, no vibrations, and unresponsive to volume and power buttons (standalone or combination). It's a DE2118, T-Mobile variant, network locked and not rooted.
Here are the conditions leading up to it:
The phone was plugged in to my PC via USB, (through a USB hub).
My Sim/SD tray was ejected.
I had been using an ADB shell to disable-user some apps and check out some various PM commands.
I did not terminate the ADB shell before powering down from the phone.
Once powered off, I held the volume up+volume down+power buttons to attempt to check out the recovery mode. I've never entered recovery mode before on this device.
The USB cable was still plugged in and I could hear the USB new device sounds on my PC a few times while I did this but didn't think anything of it.
Nothing ever appeared on the screen and pushing any of the buttons seem to provide no response.
Battery usage was at least 80%, if not closer to 90% before this happened.
It almost seems like the device is powered on and running as there feels like there's some very slight warmth on the back panel, near the center just under the camera area but I might just be imagining the warmth.
I'm aware that it needs to be network unlocked before it can be rooted as per other threads and I have not tried any root methods.
I still have my ADB shell dialog up but there really isn't much interesting in it besides a lot of the command help dialog.
What are my options?
Note: I recently installed the Jan 6th android 11 security update maybe a day before.
Edit: For anyone looking at this later, the phone came back after a complete battery drain and partial recharge and I was able to replicate the bricked state performing the same thing, usb debugging on, plugged in to usb hub on pc, shut down phone, then holding all 3 buttons down for a while.
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
mthous01 said:
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
Click to expand...
Click to collapse
I'm using Windows 7 mainly.
It shows up in device manager when I plug in the USB but with error code 28, unknown driver.
In Win7, "adb devices" lists a blank line for devices.
In Linux, "adb devices" lists a blank line for devices.
In Linux, "fastboot devices" has no output at all.
If your phone is showed in device manager you should be able to give him his life back...had the same situation long time ago with my oppo find 7..
Try this, and see if it'll recognize you for MSM download.
mthous01 said:
Try this, and see if it'll recognize you for MSM download.
Click to expand...
Click to collapse
Will give it a try. Going to be a few hours to DL the file as I'm on an extremely slow connection atm.
Well, I think that made it worse. Couldn't get the Qualcomm CAB drivers working on Windows 7, but got it through Windows Update. The MSM tool went through the process fully but afterward I unplugged the device and tried to boot, still no response, nothing on screen, no vibration. Now when I plug my device back in to the USB, I have an endless new usb device noise and windows says "Unknown Device". Device manager refreshes constantly while its plugged in. Looking back I should have probably tried ADB first before running the MSM tool.
After almost 24 hours of being unplugged, I tried plugging it in again and it finally had some signs of life with the low battery warning and then TMobile splash screen+vibration+sound after about 5 minutes. Still waiting on it to charge up for now. Probably just needed to be power cycled in the end instead of attempting to flash anything. I sure do miss the days of removable batteries.
Mtrlns said:
Probably just needed to be power cycled in the end instead of attempting to flash anything.
Click to expand...
Click to collapse
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
lzgmc said:
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
Click to expand...
Click to collapse
I had tried that yesterday to no avail. Was very strange. Everything seems to be working as normal now, though factory reset from running the MSM tool. I'm wondering if I'd be able to duplicate the issue again.
Could not replicate with USB debugging off and plugged directly in to my PC's USB port, but turning on USB debugging and plugging in to my USB hub, shutting down the phone, and then power cycling with all three buttons brought the same bricked state.
Don't know for sure if the USB port matters but while bricked plugging in to the USB hub always gives a USB device error sound. Going directly on PC it connects fine as a new device (as QUSB_BULK without drivers or Qualcomm HS USB QDLoader 9008 with drivers). ADB/Fastboot commands from PC's command line don't seem to do anything.
I did notice the fastboot menu show up on screen for a second when power cycling this time and I don't recall it appearing the first time. I think i may have had "advanced reboot" turned on the first time, while it was off this time.
Powercycling actually reset it this time.
Possible solution
It would seem that you can force MSM to write both a and b slots, which might fix your issue. Might be worth a shot
Note: If this swaps you to the Tmobile software, there's no guarantee you'll have anything but a phone that cannot be bootloader unlocked again. Since unlocked have no unlock token, trying to do so with a phone that isn't technically Tmobile may be an issue.
Just had the same problem. Holding all buttons for 30 seconds worked.
if you bricked it and you have tmobile variant you can restore it weather you have a locked or unlocked bootloader.
you have to get your phone in EDL mode, once in EDL mode you will see the "QUSB_BULK_CID" in device manager. you will then need to install qualcomm drivers (if done manually you will have to endable windows test mode, if you use the qualcomm USB driver installer then it will do it for you and you will be in test mode upon next windows reboot.) Reboot windows in TEST MODE. NOTE: i said WINDOWS TEST MODE... Once in windows test mode the driver should function and look normal in device manager. From there just open the MSM tool for your version of Nord N200 and flash and wait about 3-5 minutes. Reboot the phone and you are back in Oxygen OS.
Tips and extra Files needed below:
for the tmobile NORD N200 MSM tool
Index of /list/Unbrick_Tools/OnePlus_Nord_N200
The installer for the QUALCOM USB drivers can be found here at this website (ONLY use the QUALCOMM drivers from here, do not use any other file as it is for a different phone):
droidwin.com/unbrick-oneplus-7-pro/
once done unbricking and restoring your phone you can then exit windows test mode by running
bcdedit -set TESTSIGNING OFF
at the windows command prompt as ADMINISTRATOR.

Categories

Resources