Database Info

Lenovo A850 Bricked and cannot use USB

I have a bricked Lenovo A850 with a faulty USB connector, while it can charge it cannot connect to the computer. It goes into a bootloop and all I can access is the Android System Recovery 3e. Without a custom recovery installed and without the possibility to connect this phone via SP Flash Tool/ADB I feel clueless about what should I attempt. I ordered a replacement part, a dock charging board which I believe could bring back this phone to life. It is not a driver issue, I do not reach the point where I can see something in Device Manager or USBDeview. All I see in USBDeview is "Unknown USB Device (Device Descriptor Request Failed). Meanwhile can anyone provide me some hints about what is possible to do.
Since the Android System Recovery can only load a update.zip file I have no idea if is possible to flash a stock ROM from the Android System Recovery. Without CWM/TWRP I feel totally lost. I tried to install some image file for CWM/TWRP, by renaming them to update.zip but I did not work. I got the impression that a stock phone does want us to push a custom recovery and flash a ROM. The fact that the Android System Recovery starts gives me some hope that it is not a hard brick yet.

René Droidz said:
I have a bricked Lenovo A850 with a faulty USB connector, while it can charge it cannot connect to the computer. It goes into a bootloop and all I can access is the Android System Recovery 3e. Without a custom recovery installed and without the possibility to connect this phone via SP Flash Tool/ADB I feel clueless about what should I attempt. I ordered a replacement part, a dock charging board which I believe could bring back this phone to life. It is not a driver issue, I do not reach the point where I can see something in Device Manager or USBDeview. All I see in USBDeview is "Unknown USB Device (Device Descriptor Request Failed). Meanwhile can anyone provide me some hints about what is possible to do.
Since the Android System Recovery can only load a update.zip file I have no idea if is possible to flash a stock ROM from the Android System Recovery. Without CWM/TWRP I feel totally lost. I tried to install some image file for CWM/TWRP, by renaming them to update.zip but I did not work. I got the impression that a stock phone does want us to push a custom recovery and flash a ROM. The fact that the Android System Recovery starts gives me some hope that it is not a hard brick yet.
Click to expand...
Click to collapse
I can only assume four things:
1. Your phone had OTA and you installed it, therefore ANY kind of flashing will not work before you flash stock.
2. You have the generic chinese (non-ROW) unit, therefore there is 2% success rate of flashing anything with the generic tools, not the specific tools made by Chinese devs.
3. In the USB department, your work does not end there, as there is few more steps you have to do, GreatApo made a post about that.
4. As I said, SPFlashtool is the wrong tool. Use the tool made specifically for MTK phones like the MTKDroidtools.
And FYI, this particular model (some units) does not support flashing via ADB commands, as those libs are removed by SOME manufacturer, well they want you to STICK WITH THEIR FLASHY STOCK ROM WHICH ISN'T PRACTICAL.

Thanks for shedding a bit of light on my dead Lenovo’s phone. I really appreciate your insight. :good:
I have a 15 years of experience as a Windows desktop application developer, while I love Android there are some issues on their platforms that sometime can be counter intuitive. I personally only had Samsung and HTC phones, was always a breeze to flash, root and maintain. This MTK phone is giving me headaches. If ADB libs were indeed removed I will need to go through a yoga sessions before I throw this phone on the wall! :silly:
This is my girlfriend’s phone, everything was stock, standard and unrooted. If OTA was installed, well I really don’t know for sure but it was certainly not her who install it.
If Chinese or ROW I got no idea. This phone was bought here in Vietnam from a reputable Lenovo authorized retailer and my girlfriend said it was "Chinese". I assume that the proximity with China’s market would point out to a non-ROW model. Android System Recovery 3e is posting some message at the bottom in Vietnamese, it really makes me wonder if it could be ROW? I wish there could be some kind of indication into the model/serial number to sort this out once for all. Anyway, I ran unto MTKDroidtools, looks interesting but it remains useless for the time being. I will try my 1st best shot at MTKDroidtools once I restore the USB connection.
The USB connector has been loose and had intermittent charging issues for very long time. For more than a year my girlfriend gave to it all sort of bending, twisting and tilting at every possible angles in order to fully charge her phone. She even played into the connector with some hair pins! I guess the charging board had enough beating and at 4$ a replacement part it may worth to replace it and pray for a miracle. :angel:
Beside the USB connectivity issues, for long time her phone was constantly out of internal storage and that was triggering all sort of problems. Removing applications was never freeing enough space to keep the phone functional long enough. She had this problem 18 months long, before even meeting me! Lenovo prevents to move apps to SD. With all those issues and with the battery draining bloatware I have seen enough of Lenovo’ crap. I was considering to schedule a full flash on this phone with possibly a custom ROM on her next day off in two weeks. I assumed her phone would hold it up till then. Meanwhile I finally managed to free a good chunk of memory by removing Viber’s pictures and logs, something like 300mb. I felt her phone was breathing and running smooth again, it did well for two weeks until the recent fatal boot loop incident happen. After I freed some space her phone went into many updates, I did not really pay attention to what needed to be updated. I guess after 18 months a lot of updates where pending. If firmware updates were pushed in her phone through OTA, I have no idea but it sounds plausible.
The one thing that puzzled me was the fact that this phone says it has two SD cards, one must be some kind of software emulation. I noticed that when her phone was still functional but I never had the time to dig into this. Even Android System Recovery is looking for updates.zip on two different SD, so it looks like some kind of low level partition to me. Was there something on that second SD that I could have deleted by accident that could have created this boot loops?
I will work more on my USB connectivity issues and I will share my findings about my outcomes!
Thank you so much!

René Droidz said:
Thanks for shedding a bit of light on my dead Lenovo’s phone. I really appreciate your insight. :good:
I have a 15 years of experience as a Windows desktop application developer, while I love Android there are some issues on their platforms that sometime can be counter intuitive. I personally only had Samsung and HTC phones, was always a breeze to flash, root and maintain. This MTK phone is giving me headaches. If ADB libs were indeed removed I will need to go through a yoga sessions before I throw this phone on the wall! :silly:
This is my girlfriend’s phone, everything was stock, standard and unrooted. If OTA was installed, well I really don’t know for sure but it was certainly not her who install it.
If Chinese or ROW I got no idea. This phone was bought here in Vietnam from a reputable Lenovo authorized retailer and my girlfriend said it was "Chinese". I assume that the proximity with China’s market would point out to a non-ROW model. Android System Recovery 3e is posting some message at the bottom in Vietnamese, it really makes me wonder if it could be ROW? I wish there could be some kind of indication into the model/serial number to sort this out once for all. Anyway, I ran unto MTKDroidtools, looks interesting but it remains useless for the time being. I will try my 1st best shot at MTKDroidtools once I restore the USB connection.
The USB connector has been loose and had intermittent charging issues for very long time. For more than a year my girlfriend gave to it all sort of bending, twisting and tilting at every possible angles in order to fully charge her phone. She even played into the connector with some hair pins! I guess the charging board had enough beating and at 4$ a replacement part it may worth to replace it and pray for a miracle. :angel:
Beside the USB connectivity issues, for long time her phone was constantly out of internal storage and that was triggering all sort of problems. Removing applications was never freeing enough space to keep the phone functional long enough. She had this problem 18 months long, before even meeting me! Lenovo prevents to move apps to SD. With all those issues and with the battery draining bloatware I have seen enough of Lenovo’ crap. I was considering to schedule a full flash on this phone with possibly a custom ROM on her next day off in two weeks. I assumed her phone would hold it up till then. Meanwhile I finally managed to free a good chunk of memory by removing Viber’s pictures and logs, something like 300mb. I felt her phone was breathing and running smooth again, it did well for two weeks until the recent fatal boot loop incident happen. After I freed some space her phone went into many updates, I did not really pay attention to what needed to be updated. I guess after 18 months a lot of updates where pending. If firmware updates were pushed in her phone through OTA, I have no idea but it sounds plausible.
The one thing that puzzled me was the fact that this phone says it has two SD cards, one must be some kind of software emulation. I noticed that when her phone was still functional but I never had the time to dig into this. Even Android System Recovery is looking for updates.zip on two different SD, so it looks like some kind of low level partition to me. Was there something on that second SD that I could have deleted by accident that could have created this boot loops?
I will work more on my USB connectivity issues and I will share my findings about my outcomes!
Thank you so much!
Click to expand...
Click to collapse
Human breathren, I see that thee art having a problem with thy phone, and I knoweth jump what thee hath felt. As such, alloweth me pray pardon me to thee what actually is going on.
Lenovo is technically a Chinese company, but the good one. They make great smartphones at such a price you can say "YEP, TOTALLY WORTH IT, 1080P SCREEN AT $100!", and that's a success Lenovo made. Because of that, unauthorized shippers ( and recently manufacturers) taking this advantage and gain money by "sideloading" units of their phones, that is SUPPOSEDLY for the country China only, to shippers who chooses to pay minimum shipping taxes, to WORLDWIDE.
Thus you may see Lenovo smartphones at 20% cheaper than original retail price plus taxes. These discounted phones are TOTALLY Chinese models that contain bloatwares that somewhat nonsense and useless.:silly::silly:
Chinese ROMs that come with it is really paced to straightforward users, that are not planning to customize their phone at framework level. So all bloatwares you see now is actually making sense for them, only, not for us power users.
First problem that I see now is your USB port. Well it's all about construction of the USB port opening (the plastic inner housing). The thing is, there is a significant little gap between the metal port and the housing, so for a long period of time, the metal housing bends thus damages the port until it becomes unusable. I lived with this, experienced this....it's so painful I know. See pic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Second problem I see is storage problems. This particular phone has TWO partitions of system storage, namely internal and USB storage, totals up your 4GB you are getting. The one that ALWAYS getting full is your internal or C drive or '/sdcard0' (That's why if you want to move apps to SD card, the option is 'Move to USB storage') . Only Chinese ROMs have these because the second partition can emulate the functionality of a real SD card, and the point you ask? Well, easy for them to bulk flash their modified Chinese ROMs, with their special type of recovery and kernel which TILL NOW I cannot understand HOW it works.
What is left is 300MB+ of space for your apps, appdata and appcache. Bummer right?
So my workaround is, getting root, remove most of the bloatwares via Uninstaller[Thats the app icon colour]. And also (in planning, because I do not want to take risks before I confirm it'll work), moving entire /data from /system to /sdcard1.
SO THERE YOU HAVE IT.:victory:
huuhh.....
Source code for this phone just recently released. So I waiting a CM for this phone.:laugh::laugh:

Updates and problem solved!
UPDATES
After successfully replacing my charging board for 4$, I was finally able to flash a stock ROM and bring this phone back to life. Unfortunately, it wasn't smooth as I expected. I was challenged by two more issues:
1) MT65xx Preloader Problems: Dispite been able to update the driver to the right version "MediTek PreLoader USB VCOM Port" could not stay connected more than five seconds. I could clearly see in USBView that I could get a green connection but there was no obvious way that I could maintain it. Feeling hopeless, I started SP Flash Tool v3 1316, loaded the scatter file from a stock ROM and launched the download process knowing that nothing would happen since SP Flash Tool would be searching endlessly for a connection. Then I unplug/replug my phone, by some kind of magic the download process started and finished without a glitch! First boot went well and this phone was back in business. It seems that the USB connection could not stand being idle in Pre Loading, that some kind of command must be issue to keep the connection alive. After the first boot from a fresh Android, my computer correctly recognized my device as "Lenovo A850" without any issue.
2) Invalid IMEI. For some reasons I could not use my two SIM cards as previously since IMEI of both SIM slot were not identified by my new OS. I had to do some engineering tricks by using "Engineer Mode MTK Shortcut" and tutorial on Youtube. Lucky enough, my sticker inside my phone was still intact and could set those IMEI digits back on this phone. Everything seems to be functional now.
Will I buy a Lenovo phone again in my life? No! :crying: While the process of restoring this phone was interesting, the amount of time I spent on this phone was not worth it. My time is worth more than hours of trials and errors and having to deal with "Chinese customization" was not by cup of tea. I will get my girlfriend an Asus Zenfone 2 once this Lenovo gives up again.

René Droidz said:
UPDATES
After successfully replacing my charging board for 4$, I was finally able to flash a stock ROM and bring this phone back to life. Unfortunately, it wasn't smooth as I expected. I was challenged by two more issues:
1) MT65xx Preloader Problems: Dispite been able to update the driver to the right version "MediTek PreLoader USB VCOM Port" could not stay connected more than five seconds. I could clearly see in USBView that I could get a green connection but there was no obvious way that I could maintain it. Feeling hopeless, I started SP Flash Tool v3 1316, loaded the scatter file from a stock ROM and launched the download process knowing that nothing would happen since SP Flash Tool would be searching endlessly for a connection. Then I unplug/replug my phone, by some kind of magic the download process started and finished without a glitch! First boot went well and this phone was back in business. It seems that the USB connection could not stand being idle in Pre Loading, that some kind of command must be issue to keep the connection alive. After the first boot from a fresh Android, my computer correctly recognized my device as "Lenovo A850" without any issue.
2) Invalid IMEI. For some reasons I could not use my two SIM cards as previously since IMEI of both SIM slot were not identified by my new OS. I had to do some engineering tricks by using "Engineer Mode MTK Shortcut" and tutorial on Youtube. Lucky enough, my sticker inside my phone was still intact and could set those IMEI digits back on this phone. Everything seems to be functional now.
Will I buy a Lenovo phone again in my life? No! :crying: While the process of restoring this phone was interesting, the amount of time I spent on this phone was not worth it. My time is worth more than hours of trials and errors and having to deal with "Chinese customization" was not by cup of tea. I will get my girlfriend an Asus Zenfone 2 once this Lenovo gives up again.
Click to expand...
Click to collapse
*cries with you*:crying:
Just..give up man. Lenovo A850 is an architectural failure for me. Just wait for K3 Note for the CM to be released. Mine's dead already because of the USB failure and I gave up.

Death of g930f. Red writing in bootload. Wont boot

So yesterday my g930f uk version, died and i have no hope in getting it back up and running... Kinda hoping someone here can help me...
All that happens is its stuck on a bootload screen and i cant get no further. I can hard reset but thats it. No recovery and no download mode.
Any help at all would be appreciated
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Update:
Well my battery finally ran out. I put it on charge for 10 mins and turned it on and there was life. Booted straight up to home screen. Using the phone right now to write this.
Ran without sd card and sim and no freezing or crashes.
Powered down, put sim card and sd card in and it crashes.
Took sd card out and it's running fine now !!!!!
So must be something to do with the sd card, which works fine in my s4 and laptop
Sent from my SM-G930F using XDA-Developers mobile app

Ignore / deleted picture (now in OP)

How did it die though? What were you doing with it when it happened? Did you flash anything? We need more details.

Try USB JIGG METHOD for download mode

-Ric- said:
How did it die though? What were you doing with it when it happened? Did you flash anything? We need more details.
Click to expand...
Click to collapse
All started 5 days ago.
Day 1, working as normal then Facebook froze on a video, sound frozen on. Phone unresponsive. Forced restart, stuck on boot load loop couple of times and started normally. Normal operation rest of day.
Day 2, froze while on home screen, wouldn't boot back up, stuck on boot loop. Got into standard recovery mode, cleared cache and factory reset, had to do this a few times till finally back up and running normally.
Day 3, same as day 2. Plugged in to smart switch and went on to emergency/reinitialisation and re flashed firmware. Stuck on boot loop, cleared cache and factory reset. Back working after a few times.
Day 4 same as day 3
Day 5, downloaded evr firmware version and used odin (debug mode on and oem unlock turned off) flashed OK but still kept crashing and freezing as before.
So btu rom this time. All went OK, same problems as before, force reboot a few times and loading up to home screen before freezing again after 1 min of use. Then 4th time round that red writing came on boot loader.
I can force boot but withing half a second that writing comes back up. Can't get into recovery mode or download. No samsung logos come up. I can't turn the device off either.
All firmware was the latest version from Samsung server btu/evr/xeu. (Xeu being original firmware)
Btu and evr didn't have WiFi calling in the phone settings so wasn't going to keep them anyway.
Sent from my GT-I9505 using XDA-Developers mobile app

Sounds like a defective unit, do you have warranty? If so, just send it in and let Samsung have a look at it

-Ric- said:
Sounds like a defective unit, do you have warranty? If so, just send it in and let Samsung have a look at it
Click to expand...
Click to collapse
Yeah I was thinking about doing that. I've had the device since release (pre ordered) so 2 and a half months it was fine. There was no OTA update 5 days ago. So that's what I couldn't understand.
However if I return it and it doesn't have the correct firmware on (being xeu, and I have btu on it at the moment) and they figure out ive changed firmware then it would be warranty void job.
The pc still discovers the device in that re writing mode but it won't let me flash anything to it.
Sent from my GT-I9505 using XDA-Developers mobile app

Update:
Well my battery finally ran out. I put it on charge for 10 mins and turned it on and there was life. Booted straight up to home screen. Using the phone right now to write this.
Ran without sd card and sim and no freezing or crashes.
Powered down, put sim card and sd card in and it crashes.
Took sd card out and it's running fine now !!!!!
So must be something to do with the sd card, which works fine in my s4 and laptop
Sent from my SM-G930F using XDA-Developers mobile app

Tell us more about the SD card.
Is it partitioned? how long have you had it? does it work correctly with a laptop? have you attempted to clean the file systems in use? are many of your apps installed on it? etc etc otherwise its very difficult to say, could be anything from one app messing things up to a card that is totally frozen and needs throwing.
I've had one where it all looked good but write changes were not persistent (i.e. it was buggered) at least I could rescue the data
Having said that I have had a great many samsung phones and I have never seen the types of screen shot above.....

curioct said:
Tell us more about the SD card.
Is it partitioned? how long have you had it? does it work correctly with a laptop? have you attempted to clean the file systems in use? are many of your apps installed on it? etc etc otherwise its very difficult to say, could be anything from one app messing things up to a card that is totally frozen and needs throwing.
I've had one where it all looked good but write changes were not persistent (i.e. it was buggered) at least I could rescue the data
Having said that I have had a great many samsung phones and I have never seen the types of screen shot above.....
Click to expand...
Click to collapse
I'm going to take all the data off it tonight and format the sd card.
I bought about 3 months ago from tesco, it's a San disk ultra 32gb.
I'll update later on, as far as I know, I don't have many apps stored on it, it's mainly just for music, pictures, videos and backup of sms/contacts/etc.
Sent from my SM-G930F using XDA-Developers mobile app

Oh and no its not partitioned
Sent from my SM-G930F using XDA-Developers mobile app

mattharper228 said:
I'm going to take all the data off it tonight and format the sd card.
I bought about 3 months ago from tesco, it's a San disk ultra 32gb.
I'll update later on, as far as I know, I don't have many apps stored on it, it's mainly just for music, pictures, videos and backup of sms/contacts/etc.
Sent from my SM-G930F using XDA-Developers mobile app
Click to expand...
Click to collapse
probably worth running chkdsk / scandisk on it first.... might be as simple as a file system error.
if you're unsure you want chksk f: /f
where f: is the drive letter of the card
If you have regularly filled the drive you might also defrag it etc ... also worth checking the LOST+FOUND folder you probably wont be able to do much with it but it may give you a clue as the fact it's been having issues

curioct said:
probably worth running chkdsk / scandisk on it first.... might be as simple as a file system error.
if you're unsure you want chksk f: /f
where f: is the drive letter of the card
If you have regularly filled the drive you might also defrag it etc ... also worth checking the LOST+FOUND folder you probably wont be able to do much with it but it may give you a clue as the fact it's been having issues
Click to expand...
Click to collapse
Well unfortunately it wasn't the sd card. Phone started freezing last night while not being used and no sd card in.
Either way I checked the sd card. 0 errors on it and 10% fragmented.
I formatted it anyway to make sure there is no android conflicts on there.
So I decided to flash the bootloader, flashed the rom again, and also cp/phone partition data.
This seems to have rectified the crashing for now. I've got 6 hours use out of the device with no crashes so far.
Sent from my SM-G930F using XDA-Developers mobile app

[FIX] Pixel 3 QUSB_BULK_CID:xxxx_SN:xxxxxxxx

Hi, I have a Pixel 3 that won't turn on, won't charge, won't get into recovery mode, and gets recognized as QUSB_BULK_CID:xxxx_SN:xxxxxxxx when connected to a pc. I am an ignorant regarding phones, flashing, etc... Is there any way of getting this phone to work again?

aespinal said:
Hi, I have a Pixel 3 that won't turn on, won't charge, won't get into recovery mode, and gets recognized as QUSB_BULK_CID:xxxx_SN:xxxxxxxx when connected to a pc. I am an ignorant regarding phones, flashing, etc... Is there any way of getting this phone to work again?
Click to expand...
Click to collapse
if it doesnt power on then how are you connecting to the pc? i dunno about this but you might need to do some hard troubleshooting. replace the battery and if that doesnt work then you might have a bad motherboard.

droidbot1337 said:
if it doesnt power on then how are you connecting to the pc? i dunno about this but you might need to do some hard troubleshooting. replace the battery and if that doesnt work then you might have a bad motherboard.
Click to expand...
Click to collapse
I'm just connecting it through USB to my pc, I have never rooted it, it was in perfect condition, the battery was healthy, it just happened overnight.

aespinal said:
I'm just connecting it through USB to my pc, I have never rooted it, it was in perfect condition, the battery was healthy, it just happened overnight.
Click to expand...
Click to collapse
Oh.... Okay. In that case, get into recovery by pressing vol+ and powering on. If that doesn't work, then get into fastboot and see if your pc detects your device.

aespinal said:
Hi, I have a Pixel 3 that won't turn on, won't charge, won't get into recovery mode, and gets recognized as QUSB_BULK_CID:xxxx_SN:xxxxxxxx when connected to a pc. I am an ignorant regarding phones, flashing, etc... Is there any way of getting this phone to work again?
Click to expand...
Click to collapse
Interesting. I have the same problem and it started a few days back. Nothing would appear on screen, not even the charging sign if I plug it in. However, when i connect it to my PC, i get the same popup. It was a perfectly healthy phone until this. I have given it in to a repair shop here in Dubai as there's nothing much I could do with a black screen.

I have this same issue. I was able to install QFIL and the Qualcomm driver, but I can't located the firehose (.mdn of .elf?) files to complete the steps in this guide: https://forum.xda-developers.com/t/guide-how-to-return-to-stock-flash-images-with-qfil.3901510/.
Am I on the wrong track? Should I use this as an excuse to get a 4a?

averaVT said:
I have this same issue. I was able to install QFIL and the Qualcomm driver, but I can't located the firehose (.mdn of .elf?) files to complete the steps in this guide: https://forum.xda-developers.com/t/guide-how-to-return-to-stock-flash-images-with-qfil.3901510/.
Am I on the wrong track? Should I use this as an excuse to get a 4a?
Click to expand...
Click to collapse
Did this just happen to you today? I'm having the same issue. Wondering if google pushed an update or had a security breach or something that killed multiple phones.

Last night around 11pm (EST). The phone was charging, I went to unlock it and nothing, just a blank screen.

Sorry to necro this thread, but this literally just happened to me over night. Did anyone find any solutions or am I SOL?

twizted786 said:
Sorry to necro this thread, but this literally just happened to me over night. Did anyone find any solutions or am I SOL?
Click to expand...
Click to collapse
I was SOL. The 4a is nice ¯\_(ツ)_/¯

OK, this is really getting weird. My wife's phone just did the exact same thing. I've never seen anything like this so I thought it was an oddball thing, but this thread tells me otherwise. I wonder if the Pixel 3 is just a ticking time bomb or if we all did something to brick them. I know in my case, I just recently (2 weeks ago) replaced her charger with an Anker charger from Amazon. Figured maybe that could be part of the reason. Anyone else have any suspicions as to what might have caused the issue? I'm going to work on trying to bring it back to life or at the very least recover as much information from the device as possible, so if anyone's already working on that, please share with the group!

Another Pixel 3 here, same symptoms - died overnight last night, no visible signals on the device but plugging to a pc shows QUSB_BULK. Can't detect the device with adb. Attempts to power cycle don't seem to achieve anything.
As far as causes, no idea. It picked up the monthly update earlier in the week and was rebooted then. No change to the way it had been getting charged.

Same thing happened to my Pixel 3XL last night. Reached out to Google support and they said the only option was to get it repaired for $380. Ended up picking up a Pixel 5 today instead.

Wow! This has to be some kind of major update done by Google to brick people's phone like this. This happened on my POCO F1 phone after connecting to a OnePlus Dash Charger. Be careful guys just take warranty services and hope you will at least get a refund on the amount you have invested.

Oh wow this literally just happened to me today. I picked my phone up from my desk and checked my notifications, put it down and then picked it up 10 minutes later and it was completely bricked. This is what Device Manager shows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone was at 50-60%. I've tried everything. I guess next would be to let it die and see if it boots back up. I have some important data on this phone that wasn't backed up. I hope there's a fix .

Same thing happened to my Pixel 3 this morning. Everything was fine last night, woke up this morning and the phone won't turn on or reboot. Power button isn't responsive, Power button + Volume down to get into recovery mode is also not responsive. When I connect my phone to my PC I also get QUSB_BULK_CID:xxxx_SN:xxxxxxxx.
I did some searching around and it sounds like the phone might be stuck in Emergency Download Mode? Anyone have a solution on how to fix this issue?

Phone is stuck in Qualcomm's Emergency Download (EDL) mode. We need a signed, model specific "firehose" programmer to be able to restore an OS. While some manufacturers publish these files, Google does not. Unless one leaks for our specific model, Google has just destroyed our phones and rendered them useless while we slept. Don't go out and by another Google phone because they just killed your current one.
Exploiting Qualcomm EDL Programmers (1): Gaining Access & PBL Internals
Research & Exploitation of Qualcomm EDL Firehose Programmers: From PBL (Boot ROM) Extraction, Research & Analysis to Secure Boot Bypass in Nokia 6. (Part 1)
alephsecurity.com

Anyone have any luck finding the "firehose" / "mbn" file for the pixel 3? Mine crapped out a few days ago just like others described above. It had no physical damage whatsoever.

Same thing happened to my Pixel 3 this morning. Everything was fine last night, the phone won't turn on or reboot. Power button isn't responsive, Power button + Volume down to get into recovery mode is also not responsive. When I connect my phone to my PC I also get QUSB_BULK_CID:xxxx SN:xxxxxxxx.
Stuck in Emergency Download Mode? Anyone has a solution on how to fix this issue?
Anyone has the solution !! Please help !!!​

Same issue here, set it on the table and came back 15 minutes later. Black screen, QUSB_BULK_CID when attached to PC USB, and reboot into recovery attempts unsuccessful. Mine also did an OTA update within the last week.
Very frustrated but more than that... have important files and can't get them off the device. Has anyone been able to retrieve their files at least?

Phone hard bricked after new stock GPS update

Hi!
My wife woke up this morning with a bootlooping S7 (G930F). She had scheduled the new samsung GPS update to be installed tonight.
This morning the phone showed "failed to mount /efs", similar to this image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After showing this log, the phone went back to a android logo and it looped to the log/error again.
I tried booting it to download mode, but that seemed to have bricked the phone completely. It is no longer recognized by any PC, it doesn't react to any button press (or a combination thereof).
Do people have a similar problem with their S7 and the new stock update of Samsung? Any idea how to possibly fix this? Is there any data left on the device to salvage?
I was thinking of opening the back and trying to reconnect the battery, in the hope to get it recognized again by a PC.
Thanks!

Fineness5618 said:
(...)
I tried booting it to download mode, but that seemed to have bricked the phone completely. It is no longer recognized by any PC, it doesn't react to any button press (or a combination thereof).
(...)
Click to expand...
Click to collapse
Charge the battery and try again.

I'll try it without a new one first, as I'll have to buy that on aliexpress or something. However if there is nothing to salvage on the device, I don't really want to buy a new battery just to maybe get it unbricked.

i have the exact same failure with this update

I'm having the same issue. Did anyone figure this out?
Fineness5618​tight13​ze7zez​

Nope, tried to open the phone and disconnect and reconnect the battery. However this sadly didn't fix it. I'm really not sure what broke in the phone, maybe the battery or maybe another part of the thing.
I've since broken down the phone in pieces, pierced the memory chips and recycled it.
Sorry for the bad news.

Fineness5618 said:
Nope, tried to open the phone and disconnect and reconnect the battery. However this sadly didn't fix it. I'm really not sure what broke in the phone, maybe the battery or maybe another part of the thing.
I've since broken down the phone in pieces, pierced the memory chips and recycled it.
Sorry for the bad news.
Click to expand...
Click to collapse
Thanks for letting me know. I'm thinking about calling Samsung or the carrier since it seems like the GPS update broke the phone. I know they don't support the phone any longer but since they issued a update to it maybe they will help I'm also thinking about using odin to reload either the stock rom or a custom rom.

shaggy2 said:
Thanks for letting me know. I'm thinking about calling Samsung or the carrier since it seems like the GPS update broke the phone. I know they don't support the phone any longer but since they issued a update to it maybe they will help I'm also thinking about using odin to reload either the stock rom or a custom rom.
Click to expand...
Click to collapse
Good luck! It sure seems to be Samsungs fault so you can definitely try that route.
In my case I wasnt even able to use Odin so I hope you can get it working with your device.

Fineness5618 said:
Good luck! It sure seems to be Samsungs fault so you can definitely try that route.
In my case I wasnt even able to use Odin so I hope you can get it working with your device.
Click to expand...
Click to collapse
If it didn't work for you it probably won't work for me. I found this link in a reddit thread for the same issue. The person who shared it said it shows the same issue at the beginning of the video. Video seems to be how to fix it.
https://www.reddit.com/r/GalaxyS7/comments/wsclmm/_/il6ivrm

shaggy2 said:
If it didn't work for you it probably won't work for me. I found this link in a reddit thread for the same issue. The person who shared it said it shows the same issue at the beginning of the video. Video seems to be how to fix it.
https://www.reddit.com/r/GalaxyS7/comments/wsclmm/_/il6ivrm
Click to expand...
Click to collapse
Yeah found that too. Didn't work for me sadly.

shaggy2 said:
If it didn't work for you it probably won't work for me. I found this link in a reddit thread for the same issue. The person who shared it said it shows the same issue at the beginning of the video. Video seems to be how to fix it.
https://www.reddit.com/r/GalaxyS7/comments/wsclmm/_/il6ivrm
Click to expand...
Click to collapse
Same issue with my S5 or similar. Final software update kills the phone.

Is this related to Lineage on the phones, or are you talking about bricked phones with original stock ROM?

FRQD75 said:
Is this related to Lineage on the phones, or are you talking about bricked phones with original stock ROM?
Click to expand...
Click to collapse
literally says stock in the thread name

Fineness5618 said:
Hi!
My wife woke up this morning with a bootlooping S7 (G930F). She had scheduled the new samsung GPS update to be installed tonight.
This morning the phone showed "failed to mount /efs", similar to this image:
After showing this log, the phone went back to a android logo and it looped to the log/error again.
I tried booting it to download mode, but that seemed to have bricked the phone completely. It is no longer recognized by any PC, it doesn't react to any button press (or a combination thereof).
Do people have a similar problem with their S7 and the new stock update of Samsung? Any idea how to possibly fix this? Is there any data left on the device to salvage?
I was thinking of opening the back and trying to reconnect the battery, in the hope to get it recognized again by a PC.
Thanks!
Click to expand...
Click to collapse
try leaving it to charge while in recovery as kernel is loaded there and handles charging.
after device is somewhat charged download full latest firmware from samfw.com and try flashing it with odin if device gets recognized, use csc and not home csc to format data

Ok, so LOS does not use the part of the Stock ROM for GPS?
I thought, GPS, NFC, etc... are "recycled" from the original SW

note 20 android 13 0 B storage Bug

Hi all
I updated my note 20 ultra 5g from 12 to 13 by OTA PDA: N986BXXS5GVK9 and working fine but when I wake up morning while my device charged I found it 0 B storage so I restart my device and memory again normal. This practice am doing daily without any improvement.
If I go into the Settings > Storage section, all I see are 0 B everywhere. Calls, and receiving & sending messages in WhatsApp/SMs app works fine too. All apps that needs to store on internal user storage can't do it because its not there.
I did some actions like below:
I disabled the 4GB of extra RAM.
I cleared applications cache by ccleaner.
in the apps section in settings, 3 dots top right, special access and activate access to all media storage.
I am attaching some images if they can be of any help to anyone.
still issue not solved and I don’t want to reset format my device
regards
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

That last image is showing -1B available storage.
Try clearing the system cache on the boot menu. Otherwise you're headed for a factory reset. Make sure all critical data is redundantly backed up... now.
Lol, Android the 13th

blackhawk said:
That last image is showing -1B available storage.
Try clearing the system cache on the boot menu. Otherwise you're headed for a factory reset. Make sure all critical data is redundantly backed up... now.
Lol, Android the 13th
Click to expand...
Click to collapse
thanks a lot
but these pictures not mine but same my issue 0 B.
i tried yesterday to off my device and push power & + volume tell Samsung display appear but i cant find recovery and device start normal

the dreamer said:
thanks a lot
but these pictures not mine but same my issue 0 B.
i tried yesterday to off my device and push power & + volume tell Samsung display appear but i cant find recovery and device start normal
Click to expand...
Click to collapse
You need to have a usb cable plugged in to get to recovery. Can't remember when they changed this .....

dvhttn said:
You need to have a usb cable plugged in to get to recovery. Can't remember when they changed this .....
Click to expand...
Click to collapse
Samsung's a mess. It's not like that on the N10+ Android 9/10. I think it's hardware mod rather than firmware?
Lol, I forgot abut that because I don't have to do it. Guess some fools were pocket factory resetting. Can't have that

yesterday i wiped cash & repair apps by connecting USB cable to my laptop by recover mode and working ok
but
today early morning 2:30AM i used my devise and found it -1 B like the picture so i did wipe cash again and waiting today if again memory storage lost or not

the dreamer said:
yesterday i wiped cash & repair apps by connecting USB cable to my laptop by recover mode and working ok
but
today early morning 2:30AM i used my devise and found it -1 B like the picture so i did wipe cash again and waiting today if again memory storage lost or not
Click to expand...
Click to collapse
Yeah, that's not acceptable behavior.
Dismount and remove SD card. See if that helps.
If you're stateside take it to a Samsung Experience center at a Best buy. They have advanced diagnostics, allegedly.
Factory reset. This could be malware. Reload with care, keep the trashware like WhatsApp off it. Bare bones load at first and then gradually add more apps. Social media apps are malware and should never be installed; login by browser only if you must visit them. This saves your battery and decreases your exposure.
If all that fails reflash firmware to last known good version ie older than is on it preferably. This is another reason I don't upgrade/update firmware; less variables and you can spot odd behavior faster . A known playing field makes troubleshooting much easier. Troubleshooting new firmware can be very time consuming*...
That last possibility is a hardware failure. However I still think the most likely suspect is a 3rd party app. If you do a reload lockdown all updates for all apps. Do a few or one at a time over the course of days. Keep a log*.
*this can get bloody. Consider using more advanced tools to find the app or process responsible for the behavior. I never had to do this with Android but you may need to. With Windows I did it more than once.

blackhawk said:
Yeah, that's not acceptable behavior.
Dismount and remove SD card. See if that helps.
If you're stateside take it to a Samsung Experience center at a Best buy. They have advanced diagnostics, allegedly.
Factory reset. This could be malware. Reload with care, keep the trashware like WhatsApp off it. Bare bones load at first and then gradually add more apps. Social media apps are malware and should never be installed; login by browser only if you must visit them. This saves your battery and decreases your exposure.
If all that fails reflash firmware to last known good version ie older than is on it preferably. This is another reason I don't upgrade/update firmware; less variables and you can spot odd behavior faster . A known playing field makes troubleshooting much easier. Troubleshooting new firmware can be very time consuming*...
That last possibility is a hardware failure. However I still think the most likely suspect is a 3rd party app. If you do a reload lockdown all updates for all apps. Do a few or one at a time over the course of days. Keep a log*.
*this can get bloody. Consider using more advanced tools to find the app or process responsible for the behavior. I never had to do this with Android but you may need to. With Windows I did it more than once.
Click to expand...
Click to collapse
thanks a lot for support
since my last wipe for cash my note working fine and no issue for memory tell now

the dreamer said:
thanks a lot for support
since my last wipe for cash my note working fine and no issue for memory tell now
Click to expand...
Click to collapse
Did you try to clear the davlik cach in recovery mode sometimes it help to refresh it

next_1989 said:
Did you try to clear the davlik cach in recovery mode sometimes it help to refresh it
Click to expand...
Click to collapse
i don't remember if i saw this option or no
but i did 2 steps only
wipe catch
&
repair apps
working fine tell now

Sometimes it happens like this because of flashing wrong pit files or after you remove frp or change the system files so the best way to make sure is do s backup with switch on your pc and flash the stock rom and restore your backup and check again

Try it and let me know

next_1989 said:
Sometimes it happens like this because of flashing wrong pit files or after you remove frp or change the system files so the best way to make sure is do s backup with switch on your pc and flash the stock rom and restore your backup and check again
Click to expand...
Click to collapse
why should i flash my device while its working fine

the dreamer said:
why should i flash my device while its working fine
Click to expand...
Click to collapse
If its working fine then dont flash sir