Hi everyone,
I have a Pixel 4a that I recently bought and a couple of weeks ago I decided to try the new Android 13Beta version so I opt-in and I updated via OTG. However, after a couple of days, all of a sudden my phone stopped charging and since the phone's charge was less than 15% it didn't let me reset the phone or opt-out and get back to stable Android 12.
Now the phone is dead. I tried everything but it doesn't charge.
For the first couple of days, when I plugged in the charger, the battery icon appeared on the screen and then it showed 0% and then the icon again and 0% again and looped for over well 8 hours but didn't charge.
Now it even doesn't show the icon or the percentage.
Does anyone experience the same problem? or can anyone help me with this, please?
I've rebuilt many pixel 4a's ,, If u have adb on your puter the first place I go when there is no power is to the android flash tool just to see if there is any reaction when I hook it up, if not I break it open unplug the battery let it sit then reconnect , , you would not believe how many I revived just by doing that. But I realize everyone can't do that, when you have it hooked up to the aft hold the power button and volume down button and see if you get a reaction
hammered58 said:
I've rebuilt many pixel 4a's ,, If u have adb on your puter the first place I go when there is no power is to the android flash tool just to see if there is any reaction when I hook it up, if not I break it open unplug the battery let it sit then reconnect , , you would not believe how many I revived just by doing that. But I realize everyone can't do that, when you have it hooked up to the aft hold the power button and volume down button and see if you get a reaction
Click to expand...
Click to collapse
Thank you for your reply but as you said, unfortunately, I don't have access to flash tools and stuff like that.
I live in Turkey and since it's not a popular phone over here I believe I can't find a repair shop that has such a tool either.
GreatMimir said:
Thank you for your reply but as you said, unfortunately, I don't have access to flash tools and stuff like that.
I live in Turkey and since it's not a popular phone over here I believe I can't find a repair shop that has such a tool either.
Click to expand...
Click to collapse
Ok ,, But I would try different cables , different chargers , just to make sure,,, even if they worked before
hammered58 said:
Ok ,, But I would try different cables , different chargers , just to make sure,,, even if they worked before
Click to expand...
Click to collapse
I already did but unfortunately no luck there
after trying some methods now I managed to enter the recovery mode and everything but when I want to factory reset from recovery mode it shows this error, it doesn't even mount the system
I also can't opt-out or downgrade via system update because it doesn't charge and it says the battery level is too low.
{
"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"
}
GreatMimir said:
after trying some methods now I managed to enter the recovery mode and everything but when I want to factory reset from recovery mode it shows this error, it doesn't even mount the system
I also can't opt-out or downgrade via system update because it doesn't charge and it says the battery level is too low.
View attachment 5685913
Click to expand...
Click to collapse
I just wonder if the otg didn't damage or dirty your charging port, maybe try cleaning with some compressed air or maybe insert a toothpick or something small enough and non conductive to clean out the port or maybe there's a bent pin ??
If you're uncertain if it's a hardware or a software issue yet, I would actually suggest you do what @hammered58 suggested about physically cleaning the USB port.
Just a few weeks ago I noticed that after plugging in the type-c cable that Google provided, I had to fiddle with it so that the phone would recognize it. Tried with different cables and chargers as well, but the issue still persisted.
I think I used a paper clip to sort of "scratch" inside the port.
Lada333 said:
If you're uncertain if it's a hardware or a software issue yet, I would actually suggest you do what @hammered58 suggested about physically cleaning the USB port.
Just a few weeks ago I noticed that after plugging in the type-c cable that Google provided, I had to fiddle with it so that the phone would recognize it. Tried with different cables and chargers as well, but the issue still persisted.
I think I used a paper clip to sort of "scratch" inside the port.
Click to expand...
Click to collapse
Thank you for your suggestion to be honest I did, I even tried to clean the inside but there's no luck on that front
GreatMimir said:
Thank you for your suggestion to be honest I did, I even tried to clean the inside but there's no luck on that front
Click to expand...
Click to collapse
I bought a 4a from a guy that said he had his wireless dongle plug into his charging port and that he drop it sticking the dongle dead center on the floor, he said since then it quit charging,, when I opened it to repair I found not only the charging port loose on the mb but it also had bent a couple of pins, after reattaching a straighting its been working
hammered58 said:
I bought a 4a from a guy that said he had his wireless dongle plug into his charging port and that he drop it sticking the dongle dead center on the floor, he said since then it quit charging,, when I opened it to repair I found not only the charging port loose on the mb but it also had bent a couple of pins, after reattaching a straighting its been working
Click to expand...
Click to collapse
Plus, AFAIK, there are no wireless charging "adapters" for the 4a that actually do work?
GreatMimir said:
Thank you for your suggestion to be honest I did, I even tried to clean the inside but there's no luck on that front
Click to expand...
Click to collapse
Have you tried using the Android Flash Tool to completely reset your device?
If that doesn't solve your issue, I think it's safe to say that you have a hardware fault.
(Edit: Deleted due to l accidentally post it in a wrong post)
Zoranix7232 said:
Thank you so much! This works really great on my SM-T580 and SM-P585Y! The only glitch l could find is that when l slide the brightness bar to the darkest the screen just go completely dark, it's like the screen is turned off (this only occur in my SM-P585Y though). l hope you'll fix this in the future.
Click to expand...
Click to collapse
Wrong thread, friend
Oh sorry l was about to post this in a thread for LineageOS for my devices. Didn't know how it went here. Sorry!
Lada333 said:
Have you tried using the Android Flash Tool to completely reset your device?
If that doesn't solve your issue, I think it's safe to say that you have a hardware fault.
Click to expand...
Click to collapse
Unfortunately I can't because it's dead and it doesn't charge at all
GreatMimir said:
it doesn't charge at all
Click to expand...
Click to collapse
Yup, sorry, I'm an idiot.
GreatMimir said:
For the first couple of days, when I plugged in the charger, the battery icon appeared on the screen and then it showed 0% and then the icon again and 0% again and looped for over well 8 hours but didn't charge.
Click to expand...
Click to collapse
This still makes me think it's a software issue, as the phone clearly detected that it's connected to a charger.
I'm not sure if you've done anything like this, but maybe give it a shot?
"
Step 2: If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :
How to Disable Driver Signature Verification on 64-Bit Windows 8 or 10 (So That You Can Install Unsigned Drivers)
64-bit versions of Windows 10 and 8 include a “driver signature enforcement” feature. They’ll only load drivers that have been signed by Microsoft. To install less-than-official drivers, old unsigned drivers, or drivers you’re developing yourself, you’ll need to disable driver signature enforcement.
www.howtogeek.com
Step 3: Press the power button for 40 seconds to turn off the phone.
Step 4: Press the volume up button for 10 seconds, while connecting the device with the computer.
Step 5: Open your device-manager and make sure in "Unknown devices" is one device with the name "QHUSB_BULK".
"
Do keep in mind that this guide was written for a totally different device and for a totally different issue.
What I'm trying to get at is maybe if you manage to boot the device into this.. debug mode (?), it will bypass whatever software lock is preventing you from charging it. Again, this mode might not even be a thing for the 4a, or might not help at all. It just came to mind, curious to see if it can be of any help.
Lada333 said:
Yup, sorry, I'm an idiot.
This still makes me think it's a software issue, as the phone clearly detected that it's connected to a charger.
I'm not sure if you've done anything like this, but maybe give it a shot?
"
Step 2: If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :
How to Disable Driver Signature Verification on 64-Bit Windows 8 or 10 (So That You Can Install Unsigned Drivers)
64-bit versions of Windows 10 and 8 include a “driver signature enforcement” feature. They’ll only load drivers that have been signed by Microsoft. To install less-than-official drivers, old unsigned drivers, or drivers you’re developing yourself, you’ll need to disable driver signature enforcement.
www.howtogeek.com
Step 3: Press the power button for 40 seconds to turn off the phone.
Step 4: Press the volume up button for 10 seconds, while connecting the device with the computer.
Step 5: Open your device-manager and make sure in "Unknown devices" is one device with the name "QHUSB_BULK".
"
Do keep in mind that this guide was written for a totally different device and for a totally different issue.
What I'm trying to get at is maybe if you manage to boot the device into this.. debug mode (?), it will bypass whatever software lock is preventing you from charging it. Again, this mode might not even be a thing for the 4a, or might not help at all. It just came to mind, curious to see if it can be of any help.
Click to expand...
Click to collapse
Thank you so much,
Since I couldn't do anything to revive the phone, I had to send the phone back to Germany (where I bought the phone) so I would be able to file a repair request.
I'll let you guys know what was the exact problem when I get a detailed assessment of the issue from Google
GreatMimir said:
Thank you so much,
Since I couldn't do anything to revive the phone, I had to send the phone back to Germany (where I bought the phone) so I would be able to file a repair request.
I'll let you guys know what was the exact problem when I get a detailed assessment of the issue from Google
Click to expand...
Click to collapse
Aww, man, I wish I'd thought of this sooner.
Was your device still under warranty?
Absolutely be sure to update us when you get the info from Google.
Hi, Is it resolved? How much they charged for the repair? I am facing the same issue after my phone updated to Android 13.
Related
Does anyone have this A10 Netbook:
{
"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"
}
Specifications:
CPU – Allwinner Boxchip A10 @ 1.0GHz (Cortex A8 with Mali 400 GPU
System Memory – 1GB RAM
Storage – 4GB Flash + SD Card slot (up to 32 GB)
Display – 10″ LCD Display (non-touchscreen) with 1024×600 resolution.
Connectivity
*10/100M Ethernet RJ45
*Wi-Fi 802.11 b/g/n built-in
*3G support via external 3G dongle: E1916, ZTE AC2736, HUAWEI E1750, HUAWEI EC122, HUAWEI EM770W…
USB – 3x USB 2.0 Host ports
Camera – 0.3 MP front camera
Audio I/O – 3.5mm headphone and microphone jacks, built-in microphone and speaker,
Sensors – Gravity Sensor
Battery – 2800mAh – Up to 3 hours usage
Dimensions - 278 x 188 x 25 mm
Weight – 807g
Detailed description is here:
http://tinyurl.com/8lul4v2
Here is AndroidAnalyzer (Androidfragmentation.com) report:
http://tinyurl.com/8lg9x4r
I have been trying to find the original factory image, but have not been successful so far.
Got the the boot.img pulled and unpacked it, going to try to build proper CWM recovery (it has the "<3e>/ PUB101" recovery).
This is from build.prop: "ro.build.fingerprint=softwinners/crane_pub101/crane-pub101:4.0.3/IML74K/20120607:eng/test-keys"
I think it may be compatible with some other A10 tablets as far as the OS, minus the touch display properties.
My impressions so far:
- it's light weight, QWERTY keyboard is nice (no fingerprints!)
- WiFi reception is pretty good
- processor and RAM are fast enough
- additional storage with full SD Card
- 3 full USB host ports and LAN port
- built in camera and mic are pretty decent for Skype
- built in speaker is kind of weak
If anyone else has this gadget, please share your thoughts...
Help~~~~ i have a problem
i got this device few days ago and i immediately realised it was a mistake to buy this. now when i open the device it gets stuck at the big Android logo and never boots...i tried hard resetting but it is not solving my problem. i tried googling out but in vein. i really need to get this thing working can anyone pls help.
NUMN said:
i got this device few days ago and i immediately realised it was a mistake to buy this. now when i open the device it gets stuck at the big Android logo and never boots...i tried hard resetting but it is not solving my problem. i tried googling out but in vein. i really need to get this thing working can anyone pls help.
Click to expand...
Click to collapse
I'm sorry to hear that you are having problems and bootloop.
I haven't spent much time playing with this, but mine boots and works fine.
When you say "Big Android Logo", is it the square logo in middle of screen, the greenish screen with Android in bottom right corner or the Letters "ANDROID" flashing in middle of screen? And how did you "reset" it?
I agree, there is not any usable information about this device on the interwebs, maybe because is so new and uncommon.
I'm trying to figure out how to connect it to a PC so we can get adb access, but with the 3 USB ports being host only, I haven't had any luck.
Hopefully some more people get this device so we can get some development.
./B
any luck
yes mine got stuck at the point when "ANDROID" flashes in middle, is there any firmware i can flash on it or maybe links to the original firmware?
i really feel stupid now having bought this plastic crap.
kozmo2k4 said:
I'm sorry to hear that you are having problems and bootloop.
I haven't spent much time playing with this, but mine boots and works fine.
When you say "Big Android Logo", is it the square logo in middle of screen, the greenish screen with Android in bottom right corner or the Letters "ANDROID" flashing in middle of screen? And how did you "reset" it?
I agree, there is not any usable information about this device on the interwebs, maybe because is so new and uncommon.
I'm trying to figure out how to connect it to a PC so we can get adb access, but with the 3 USB ports being host only, I haven't had any luck.
Hopefully some more people get this device so we can get some development.
./B
Click to expand...
Click to collapse
NUMN said:
yes mine got stuck at the point when "ANDROID" flashes in middle, is there any firmware i can flash on it or maybe links to the original firmware?
i really feel stupid now having bought this plastic crap.
Click to expand...
Click to collapse
I have not found the factory image and there is no manufacturer to contact.
Have you tried to boot it up while it's plugged in?
..
Lo and behold, I just found this:
http://elinux.org/Hack_A10_devices:good:
From what I read there so far, it can be booted from USB (like the Nook Color from µSD card), so bricking it is almost impossible.
We need to find a way to boot into recovery; then you should be able to
Gotta read through it some more and try to get the system image....
./B
Dead?
Well, I went tot turn it on this morning and.... nothing!!! Only the green LED.
Plugged it it, let it charge for over 4 hours (normally it would take about 2- 2.5 to get full charge while turned off) and it will not come on.
Crap, I thought I was starting to make a little headway here...
Going to pop the cover and inspect the "guts" to see if anything maybe got disconnected and test the battery... (fingers crossed)...
./B
Yup, dead netbook
Still dead, can't see anything "fried" inside, battery check out OK, don't know what else to do...
Here are some pictures from the inside:
and this is the battery:
Maybe these can help someone in the future...
Hello, anyone still following this thread?
I got a tablet like this from a friend to play with. At least I think it's the same, I found this, it has no stickers except "Boxchp A10" on the bottom and white, but similar otherwise.
It also bootloops after using it a little while and first reboot. Does any one know a key combo to boot it with to factory reset or has any one managed to boot it to recovery? I have some image on a sdcard which the supplier claims it should boot if you just insert it to the sdslot but it has no effect what so ever.
I tried booting it while holding each of the mouse buttons down. Left mouse button has no effect but with right mouse button it just starts with black screen.
labbe- said:
Hello, anyone still following this thread?
I got a tablet like this from a friend to play with. At least I think it's the same, I found this, it has no stickers except "Boxchp A10" on the bottom and white, but similar otherwise.
It also bootloops after using it a little while and first reboot. Does any one know a key combo to boot it with to factory reset or has any one managed to boot it to recovery? I have some image on a sdcard which the supplier claims it should boot if you just insert it to the sdslot but it has no effect what so ever.
I tried booting it while holding each of the mouse buttons down. Left mouse button has no effect but with right mouse button it just starts with black screen.
Click to expand...
Click to collapse
Hi labbe-
Head on over to the link I posted from elinux.org and read up on how to re-image the device.
Mine is dead, so I can't be of any more help. Over the holidays I'll try to spend some time on it to see if I can resurrect it.
Where did you get a copy of the vendor image? Do you mind sharing it?
I bought that minibook to have as a tool to learn how to develop on Android devices, but only got as far as pulling the recovery/kernel and system images before it decided to die. Hoping I can figure it out somehow...
Best regards
./B
kozmo2k4 said:
Hi labbe-
Head on over to the link I posted from elinux.org and read up on how to re-image the device.
Mine is dead, so I can't be of any more help. Over the holidays I'll try to spend some time on it to see if I can resurrect it.
Where did you get a copy of the vendor image? Do you mind sharing it?
I bought that minibook to have as a tool to learn how to develop on Android devices, but only got as far as pulling the recovery/kernel and system images before it decided to die. Hoping I can figure it out somehow...
Best regards
./B
Click to expand...
Click to collapse
Ok, missed that link, will look a look at it tomorrow. Will also share the image, hopefully it is the right one.
It's been a small project and a huge pain in the ass to get that to come to life. I actually found a reset button on the bottom like 15 seconds after posting on this thread but it didn't help
I have the Iberry 7inch TAB with SIM made in India. I have the latest IMG file from the the vendor on this link
http://forum.xda-developers.com/showthread.php?t=1993621
It may be of some help
/R
vkrajuu said:
I have the Iberry 7inch TAB with SIM made in India. I have the latest IMG file from the the vendor on this link
http://forum.xda-developers.com/showthread.php?t=1993621
It may be of some help
/R
Click to expand...
Click to collapse
I would not recommend trying to flash the Iberry AX03 image onto the Minibook, hardware specs are quite different.
Ok, so I now got the PC recognizing the device when doing the special startup with holding down mouse2, pressing power button for two seconds and after that pressing powerbutton repeatedly, but I don't have usb drivers for it and the ones with livesuit don't work :E will try to locate some drivers before my friend comes to get it for himself to tinker with during the holidays :E
EDIT: got it working!! found the usb drivers and it upgraded from the image i had! the software model is SoftwinterEvbV13 so i think it's safe to assume this is indeed an allwinter tablet?
an archive with working livesuit and image included: https://docs.google.com/open?id=0BzNwI5q-RJBvcnJVWHNuQURvTFU
IT WORKS
THANKS LABBE IT WORKED MAN >>YOUR LINK IS REAL :good: JUST WONDERING IF THRERE IS ANY OTHER ROM WE CAN TRY ON TBIS ONE>
How are you connecting it via USB? My version dont have any kind of input USB, I had this laptop openned and there is free space with pinout, but without it. I also can't make it boot from SD. It does not have COM port, so I even can't connect console, to specify uBoot parametters. Any way to get linux running on it?
Virnik0 said:
How are you connecting it via USB? My version dont have any kind of input USB, I had this laptop openned and there is free space with pinout, but without it. I also can't make it boot from SD. It does not have COM port, so I even can't connect console, to specify uBoot parametters. Any way to get linux running on it?
Click to expand...
Click to collapse
i just used a cable with a normal usb connector on both ends when connecting it to my PC
Sent from my Nexus 4
yes i hav the same machine received today i want to set a linux distrib which one seems to be the best for you
dont hesiate to contact me jean.michel.78 at gmail.com
i have also the same netbook i am sure it can boots from the sdcard but i have not succeeded yet
i will find a solution
i am sure it can boot because i have tried with an img the boot is unsuccessful but i have seen some logs on the sdcard
that make me hope . i keep you informed i am on gmail
hello i have this netbook i have put linux linaro on it it works very well
i try to copy linaro on /dev/block/nandi but it is erased by /init.sun4i.rc
i wonder how this file is generated
contact me thanks
Reviving a very old thread., but it might come in handy for someone.
I just got this Netbook (OP) come back to life!!!
Steps:
1. download the SoftwinterEvbV13 zip from this post https://forum.xda-developers.com/showpost.php?p=35634915&postcount=13
2. Extract it
3. Make sure the Netbook is powered OFF. Remove back cover from the Netbook.
4. Insert USB A-to-A cable to Port #2, the closest on to the charging port; the other end insert to your (Windows) PC.
5. Open the LiveSuit tool and locate/select the (included) "suni4i_a10.img" (it's in the IMAGE folder).
6. Looking at the PC board in the picture of Post #7 https://forum.xda-developers.com/showpost.php?p=33468211&postcount=7 , there a are two SWITCHES,
marked "SW5" and "UBOOT".
7. Press and hold the "UBOOT" switch and press the "SW5". You should notice the power light should come on, also your PC should discover a new device.
Here, if your PC can't install the proper drivers, open up Device Manager, and manually install/update the driver from the UsbDriver folder.
8. At this point, if LiveSuit didn't recognize the Netbook, unplug the USB, and re-connect. LiveSuit will take over and flash the image.
9. Unplug USB and reboot the Netbook. Will take a while, might be on black screen for a bit, but eventually will boot to factory Android 4.0.3 ICS.
It worked for me.
Good luck.
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?
Yeah, so I feel really dumb as I cannot figure this out and I have searched the web and here. Found some really old posts, but damn...
When I plug any USB Storage Device into my phone, I get the following:
"Security policy prevents use of USB host storage"
Any ideas? I have stuff I want to transfer off my phone and can't use an external storage or even USB to PC.
Thanks!
Talderon said:
Yeah, so I feel really dumb as I cannot figure this out and I have searched the web and here. Found some really old posts, but damn...
When I plug any USB Storage Device into my phone, I get the following:
"Security policy prevents use of USB host storage"
Any ideas? I have stuff I want to transfer off my phone and can't use an external storage or even USB to PC.
Thanks!
Click to expand...
Click to collapse
Try on your pc, and you've installed USB drivers? And your phone is not rooted or anything? Once connected to pc, in phone drop down select file transfer. And see if you can transfer.
Jostian said:
Try on your pc, and you've installed USB drivers? And your phone is not rooted or anything? Once connected to pc, in phone drop down select file transfer. And see if you can transfer.
Click to expand...
Click to collapse
So, here it is:
Note 20 Ultra 5G
Stock Android 11 (Sprint OTA)
Non-Rooted
I have installed the drivers and have tried to connect it. No dice.
Anything USB as far as Storage goes, it denies me. I can see the phone and it comes up, but there is NO storage listed (Internal or SD Card). In order to get what I needed, I ended up pulling the SD Card and copying things, but that was so much slower and more of a pain, I normally use my 1TB USB SSD and it is so much faster.
(https://www.amazon.com/SanDisk-Extreme-Portable-External-SDSSDE60-1T00-G25/dp/B08GTYFC37)
Thanks!
Maybe Q's security screwing with you... not sure.
Go into Developer options and check USB settings.
Go into drive management and connect from there; use rescan for drives option.
Sounds like a PC driver issue. Check event Viewer for errors messages.
Try another cable/port.
Does Smart switch work? Load that on the PC to get the driver.
Muck around in device manager if that doesn't work.
Very Strange, I am running TMB version of Android 11 on Note 20 Ultra and USB Storage works fine? Didn't have to do anything to enable it...
Talderon said:
Yeah, so I feel really dumb as I cannot figure this out and I have searched the web and here. Found some really old posts, but damn...
When I plug any USB Storage Device into my phone, I get the following:
"Security policy prevents use of USB host storage"
Any ideas? I have stuff I want to transfer off my phone and can't use an external storage or even USB to PC.
Thanks!
Click to expand...
Click to collapse
I know this is 3 years old but I am having this exact issue. Did you ever find a solution?
jesus2282 said:
I know this is 3 years old but I am having this exact issue. Did you ever find a solution?
Click to expand...
Click to collapse
Unfortunately, while I had my Note20U, I never found the solution.
Since then, I have had a Z Fold 3 and now an S23 Ultra and no issues. Not sure what happened here.
Talderon said:
Unfortunately, while I had my Note20U, I never found the solution.
Since then, I have had a Z Fold 3 and now an S23 Ultra and no issues. Not sure what happened here.
Click to expand...
Click to collapse
Thanks for the response. Did you ever try to do a factory reset? That is what I am going to try next. I also can't enable usb debugging. Not sure if it's related.
jesus2282 said:
Thanks for the response. Did you ever try to do a factory reset? That is what I am going to try next. I also can't enable usb debugging. Not sure if it's related.
Click to expand...
Click to collapse
I did reset it before I traded it in, but, alas, I didn't try to use it afterwards. Sorry mate and good luck!
Talderon said:
Unfortunately, while I had my Note20U, I never found the solution.
Since then, I have had a Z Fold 3 and now an S23 Ultra and no issues. Not sure what happened here.
Click to expand...
Click to collapse
USB settings in Developer options?
Possible bad port PCB.
{
"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"
}
I also faced a similar problem. with my Note 20 ultra 5G. After a long time of searching found that the "Smart Switch" App was in deep sleep. so I opened that, it was asking for an update and done. my all USB drives can be connected to my phone now.
razoan1987 said:
I also faced a similar problem. with my Note 20 ultra 5G. After a long time of searching found that the "Smart Switch" App was in deep sleep. so I opened that, it was asking for an update and done. my all USB drives can be connected to my phone now.
Click to expand...
Click to collapse
Man I thought this comment was going to save me. I opened up my smart switch app. It was all up to date but my usb drive still won't connect. My wife has the exact same phone as me and when I plug it into her phone. It comes up no problem like it suppose to. I'm stomped here.
shinuske said:
Man I thought this comment was going to save me. I opened up my smart switch app. It was all up to date but my usb drive still won't connect. My wife has the exact same phone as me and when I plug it into her phone. It comes up no problem like it suppose to. I'm stomped here.
Click to expand...
Click to collapse
Sounds like a configuration or permissions issue on your device. Check special permissions in accessibility. Try in safe mode. Try disabling Developer options temporarily. Clear system cache. Do some gookill searches, doesn't have be that same model but should be same OS version. Possibility of malware. More remotely a possibility a C port pcb failure, these rarely fail; is it clean? Inspect. A soft bristle tooth brush can be used to clean it and a blower bulb.
Play with it. Do you remember when it was first noticed? Were any updates or apps added?
This could provide clues. Relax, think of it a game, eventually you'll find.
Here are the edl (emergency download mode) test points for Motorola Moto G Stylus 5G XT2131.
{
"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*
Thank you @vache and all at Motorola Blankflash (telegram) for everything
. . . . Only for this specific release
XT2131-1_DENVER_BOOST_11_RRES31.Q3-60-47-2-2-2_subsidy-BOOST_DISH_regulatory-DEFAULT_cid50_CFC
1. Decompress "blankflash_file".zip
2. Short the edl test points. while holding the "tweezers" on the 2 test points plug the device into PC.
3. After you see the device connected , or hear the connected sound , release the "tweezers" from the test points.
4. Run blank-flash.bat/.sh (choose which one depending on what os you have on your PC.)
!!WARNING!!
DO NOT turn off!! DO NOT unplug!!
5. Wait for device to reboot to fastboot mode. (if your Denver/Osaka does not reboot to the bootloader then you do not have the correct blank flash file)
6. Flash the stock firmware to your device (flash with lmsa, tiny-fastboot-script, platform-tools or cli. it's up to you)
Now your device should be working again. I HOPE this small bit of information helps you out as much as it helped me.
For the love of Moto!
Guide by @sosthenisRR aka sosRR (yeah like the flying kind )
This did work on my mine which I bricked a month ago. I was able to run the bat file on my windows PC so it said "Waiting for devices", short the pins, plug in my usb cable and then wait a minute or 2 for it to boot into fastboot. Then I ran the lenovo recovery tool and flash it back to life.
duffman452001 said:
This did work on my mine which I bricked a month ago. I was able to run the bat file on my windows PC so it said "Waiting for devices", short the pins, plug in my usb cable and then wait a minute or 2 for it to boot into fastboot. Then I ran the lenovo recovery tool and flash it back to life.
Click to expand...
Click to collapse
Yeah it did work with me too he is the greatest.
Thank you so much it did work with me LOVE..
Hmmm..
So I tried this method about a week ago BUT I didn't see this post then and I used a blanlflask from lolinet...it didn't turn out good. It began just fine, but it only flashed the first item, it seemed like it was flashing the partition scheme and it concluded, ending with
"Finished." then said rebooting to fastboot but the screen went black...and stayed black. I can only get a blink from charging led if I hold down power long enough....might this file be worth a shot? I can still get into EDL. Appreciate any advice?
I have a terrible situation at hand thanks to Motorola really screwing me, hard, in regards to a Repair. Long story short, I went from having a moto One 5G Ace to being sent a VERY used, worn, older and completely different model device. Motorola has some balls, let me tell ya. Anyways, the device does not boot and it is not bootloader unlocked. I received it and immediately called Motorola Repair/Tech Support within about 20-30 minutes of it being delivered to me; they tell me to send it in for repair in it's original box. I won't mention how they kept the original box, claiming to have thrown it away because it had a hand-written note on a white sticker on the side that clearly indicated this was a "loaner" device...oh wait, I mentioned it. Anyways, I can't unlock the bootloader, because OEM Unlock was not open in Developer Settings. I also can't boot, flash, or load anything. LMSA recognizes the device as the XT2131-1 and downloads the appropriate firmware. It begins the rescue, but at 32% it fails, rebooting the phone to the "NO VALID OS FOUND" black/red screen and LMSA states something like "We're sorry, but it's unsafe to rescue this device at this time."
I've tried multiple Windows machines, Windows 8, 10 and Windows 11 hosts. I've tried MX Linux, Linux Mint, Ubuntu, etc., but I can't get anything to flash/rescue. I then found this page and, at first, still couldn't reach blankflash. However, here we are two-three months later and with a friend's help I am able to get into EDL. I ran this blankflash, which is the ONLY blankflash that actually recognized the device, but it finishes and simply reboots back to the Bootloader screen. I'm afraid maybe I unplugged it too quickly. Is there any advice that anyone has about what I could be doing wrong? Or what I should try? Any opinions on the BEST Linux/Windows OS to use for things like this? Thanks, in advance, to everyone and anyone reading this, if you have any pointers, please do help me out. Motorola really screwed me but I've filed complaints appropriately about that-in the meantime though it'd be nice to have a phone again after almost 6 months of not having one at all...I keep refraining from buying a different device on principal...and things have been so tight for me, financially, this year. So any help I would greatly, greatly appreciate!
Thank you,
Clint
csann said:
I have a terrible situation at hand thanks to Motorola really screwing me, hard, in regards to a Repair. Long story short, I went from having a moto One 5G Ace to being sent a VERY used, worn, older and completely different model device. Motorola has some balls, let me tell ya. Anyways, the device does not boot and it is not bootloader unlocked. I received it and immediately called Motorola Repair/Tech Support within about 20-30 minutes of it being delivered to me; they tell me to send it in for repair in it's original box. I won't mention how they kept the original box, claiming to have thrown it away because it had a hand-written note on a white sticker on the side that clearly indicated this was a "loaner" device...oh wait, I mentioned it. Anyways, I can't unlock the bootloader, because OEM Unlock was not open in Developer Settings. I also can't boot, flash, or load anything. LMSA recognizes the device as the XT2131-1 and downloads the appropriate firmware. It begins the rescue, but at 32% it fails, rebooting the phone to the "NO VALID OS FOUND" black/red screen and LMSA states something like "We're sorry, but it's unsafe to rescue this device at this time."
I've tried multiple Windows machines, Windows 8, 10 and Windows 11 hosts. I've tried MX Linux, Linux Mint, Ubuntu, etc., but I can't get anything to flash/rescue. I then found this page and, at first, still couldn't reach blankflash. However, here we are two-three months later and with a friend's help I am able to get into EDL. I ran this blankflash, which is the ONLY blankflash that actually recognized the device, but it finishes and simply reboots back to the Bootloader screen. I'm afraid maybe I unplugged it too quickly. Is there any advice that anyone has about what I could be doing wrong? Or what I should try? Any opinions on the BEST Linux/Windows OS to use for things like this? Thanks, in advance, to everyone and anyone reading this, if you have any pointers, please do help me out. Motorola really screwed me but I've filed complaints appropriately about that-in the meantime though it'd be nice to have a phone again after almost 6 months of not having one at all...I keep refraining from buying a different device on principal...and things have been so tight for me, financially, this year. So any help I would greatly, greatly appreciate!
Thank you,
Clint
Click to expand...
Click to collapse
Motorola Blankflash
Request blankflash by giving device informations
t.me
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Start from scratch but remember need to use the last firmware that was on the phone when you choose a blankflash file
Hello. I have been able to get this tool to work with my own specific flash file for an XT2131-1 RETUS. When I boot the flash file, it still shows that the bootloader is locked. Is there any way too boot into fastboot with a blankflash file and make sure that it is unlocked?
Please help I have model xt2163dl and can't find the test points. Please help
Kireej said:
Please help I have model xt2163dl and can't find the test points.
Click to expand...
Click to collapse
You may have to find them yourself.
A voltmeter can help. You need one point that measures 1.8V (voltage source) and another that's close to 0V (GPIO).
If you have a resistor (maybe 470 ohms to 2.2k) you can connect things together without worrying too much about vaporizing anything.
That's a low enough resistrance for the GPIO for EDL boot.
Renate said:
You may have to find them yourself.
A voltmeter can help. You need one point that measures 1.8V (voltage source) and another that's close to 0V (GPIO).
If you have a resistor (maybe 470 ohms to 2.2k) you can connect things together without worrying too much about vaporizing anything.
That's a low enough resistrance for the GPIO for EDL boot.
Click to expand...
Click to collapse
Not sure of what any of that means. I can't find anything on Google or anywhere else. Seems as if someone here has to have the same model as me. The waiting game begins lol.
Renate said:
You may have to find them yourself.
A voltmeter can help. You need one point that measures 1.8V (voltage source) and another that's close to 0V (GPIO).
If you have a resistor (maybe 470 ohms to 2.2k) you can connect things together without worrying too much about vaporizing anything.
That's a low enough resistrance for the GPIO for EDL boot.
Click to expand...
Click to collapse
Ok I got a voltmeter but not sure how to use it. Here is the meter and the phone.
Oops, my apologies.
The original post was talking about the XT2131 (which is Qualcomm SDM480) and EDL.
The XT2163DL is a Mediatek Helio G25,
There are similarities, but also differences.
I can say with high confidence that Qualcomm EDL is (always?) using a 1.8V voltage source and a GPIO with a pull-down resistor.
I don't really know what Mediatek is doing. Assuredly no voltage is over 1.8V but I don't know if it's pull-up or pull-down,
In any case, I would still look for conspicuously adjacent test points where one measures 1.8V and one near zero.
I would still not want to connect random things together without checking and without a resistor.
The absolute worse would be hitting a test point for a backlight (which could be as high as 30+V).
Some Mediatek things show BROM and Preloader when they boot up anyway.
Are you sure that you're not seeing them?
Good luck
Renate said:
Oops, my apologies.
The original post was talking about the XT2131 (which is Qualcomm SDM480) and EDL.
The XT2163DL is a Mediatek Helio G25,
There are similarities, but also differences.
I can say with high confidence that Qualcomm EDL is (always?) using a 1.8V voltage source and a GPIO with a pull-down resistor.
I don't really know what Mediatek is doing. Assuredly no voltage is over 1.8V but I don't know if it's pull-up or pull-down,
In any case, I would still look for conspicuously adjacent test points where one measures 1.8V and one near zero.
I would still not want to connect random things together without checking and without a resistor.
The absolute worse would be hitting a test point for a backlight (which could be as high as 30+V).
Some Mediatek things show BROM and Preloader when they boot up anyway.
Are you sure that you're not seeing them?
Good luck
Click to expand...
Click to collapse
Yes all I get when I plug the phone in is a whitesh blue led light blinking on the top right corner. If I hold vol+ or vol- and power it will stop blinking for a minute then start again. Computer will not recognize the device and I am completely unable to get into fastboot to flash stock firmware. This all started when I accidentally flash firmware from a different year.
If you're on Windows, you should count the "bongs" when your device boots.
My usblog.exe can be helpful in identifying things that pop up.
My enumusb.exe can show what has ever popped up on your Windows.
Both can be found here.
Code:
C:\>enumusb /l /v0e8d
0E8D:2000 7&279c4dc7&2&6 2023-02-08 04:14 MT65xx Preloader
0E8D:201C 1483GR123456789 2023-02-08 04:14 Port_#0006.Hub_#0005
0e8d is Mediatek
Ok fount the points then I run the flash blank boot script then it says this after I let go of tweazers
Renate said:
If you're on Windows, you should count the "bongs" when your device boots.
My usblog.exe can be helpful in identifying things that pop up.
My enu
musb.exe can show what has ever popped up on your Windows.
Both can be found here.
Code:
C:\>enumusb /l /v0e8d
0E8D:2000 7&279c4dc7&2&6 2023-02-08 04:14 MT65xx Preloader
0E8D:201C 1483GR123456789 2023-02-08 04:14 Port_#0006.Hub_#0005
0e8d is Mediatek
Click to expand...
Click to collapse
Thank you I got usblog to work but the other opens then closes. Also I'm not quite sure what to do with this information. It shows up as an unknown USB device and as soon as I take the tweazers off it disconnects from computer. The blank flash exe never detects the device.
0000/0002 is often a USB gadget under Linux that is not initialized at all.
Renate said:
0000/0002 is often a USB gadget under Linux that is not initialized at all.
Click to expand...
Click to collapse
Any idea at all of how to get this thing unbricked? Test points is where I keep ending up but again as soon as I let go of tweazers it disconnects.
Hi everyone,
This is the setup:
Phone: Samsung S4 mini (GT-i9195)
OS: Lineage OS (can't remember the version, but I guess 17.1 or 18.1)
Recovery: TWRP (can't remember which version)
After I had a phone call I put the phone on the table. Some minutes later when I came back the app switcher and back button backlight was on, but there was no reaction when I touched the screen or any other buttons. Removing and returning battery had no impact, as well as using the charger.
I noticed when I connected it to my Windows PC via USB cable, I hear the windows sound for connecting and some seconds later the sound for disconecting.
When pressing the phones power button for 10 seconds while connected to pc, I hear sound for disconnecting and a moment later the sound for connecting. In any case I can't see the device on my PC as it would normally be the case.
Before, when the phone was working I had a working setup for scrcpy, with ADB debugging activated, but this doesn't seem to work as well, so my noobish guess is that the phone does not load Lineage OS at all.
So here I am at the end of my knowledge and I want to ask here, what are my option in order to recover my data (all on phones memory, not SD card)?
Thanks so much for any help!
Sounds like a hardware failure, if so if you can correct the problem... maybe a connector making poor contact. If it's the mobo you're boned.
Is the battery known good?
Always use the SD card as a data drive; all critical data goes there. Then redundantly backup the SD card to at least two hdds that are physically and electronically isolated from each other and the PC. Otherwise this can happen again.
Thank you very much @blackhawk for your answer and the attempt to help!
blackhawk said:
Is the battery known good?
Click to expand...
Click to collapse
Yes, battery is OK
blackhawk said:
If it's the mobo you're boned.
Click to expand...
Click to collapse
really, there is no way to get data from the internal chip?
wouldn't it maybe be possible to unsolder the chip and put it in a working s4 mini?
blackhawk said:
Always use the SD card as a data drive; all critical data goes there. Then redundantly backup the SD card to at least two hdds that are physically and electronically isolated from each other and the PC. Otherwise this can happen again.
Click to expand...
Click to collapse
Yes, you're absolutely right. For long time I want to have a setup exactly as you have described. I started with it, but unfortunatley not everything was set to be synced with my NAS. Most of the stuff is on external SD, but some is not. With some apps you even have the issue that can't use external SD and which force you to use the onboard memory, like for example Signal does.
The chipset is likely a BGA form factor, all the solder pads are underneath it. You need use a hot air station and have the skillset to use it.
It would then need to be reflowed onto the donor board. Some overseas houses might do it relatively cheaply. Not a common practice except by data recovery $pecialists.
The SD card should contain no running apps as it's bandwidth is limited. Apps that allow backup there like ColorNote can be auto backed up though.
Step one: When a crippled device makes a "bong" when connected to a PC, find out what it is.
Is it the bootloader, charger, fastboot, ADB, MTP or who knows what?
I find usblog.exe helpful. See: http://www.temblast.com/windows.htm
If you're on Linux, just do lsusb -v when it bongs.
Renate said:
Step one: When a crippled device makes a "bong" when connected to a PC, find out what it is.
Is it the bootloader, charger, fastboot, ADB, MTP or who knows what?
I find usblog.exe helpful. See: http://www.temblast.com/windows.htm
If you're on Linux, just do lsusb -v when it bongs.
Click to expand...
Click to collapse
Thank you @Renate , good tip!
When phone without battery gets connected to PC, this is what usblog 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"
}
But what does it tell me now? How exactly can I find out in what state my phone currently is?
Next I wil try to get some linux running and see what lsusb -v shows me.
blackhawk said:
The chipset is likely a BGA form factor, all the solder pads are underneath it. You need use a hot air station and have the skillset to use it.
It would then need to be reflowed onto the donor board. Some overseas houses might do it relatively cheaply. Not a common practice except by data recovery $pecialists.
Click to expand...
Click to collapse
Looks to me like an acceptable solution if I can't get it any other way and really want to get the data.
Oh, this is an older device. You may have a chance. Do you think that /data is encrypted?
Right now you have the silly VCOM driver installed. I'm prejudiced against them. You'll still be able to reinstall it if this doesn't work.
Get Zadig https://zadig.akeo.ie/ and install the WinUsb driver on 05c6/9008
Get edl.exe from my sig.
Code:
C:\>edl.exe /lhello
Copy the output (minus the serial number if you care) and paste it here.
If it gives you can't read/can't write, do a LONG power press until it bongs and try again.
That slash-ell-hello is just something to get it moving. Next you'll use slash-ell-loader-with-a-serious-name.
Thanks again for your guidance @Renate !
I deinstalled the COM driver, installed WinUsb driver and run edl.exe as you have explained. Unfortunately it seems I always get:
Found EDL 9008
Could not read device
even if I do the LOOong power press until bong-move.
What does this mean and what options do I have left?
That's strange. It's possible that you have a recalcitrant device.
I put some motivation in the code.
Go and download the new version of edl.exe
Make sure you have the new one, 136,704 bytes.
MD5 028533aaec778cc0c1357525a7bf503c
Thanks for the new version, but the output is unfortunatley not much different to before:
Code:
Found EDL 9008
Resetting Sahara
Could not read device
Eventually worth mentioning: I have a second Samsung S4 mini (with broken display). If I connect it to my PC, I get the connecting-bang, if I then run edl with your parameter the output is always:
Code:
Could not find EDL device
I think that this is so old it's using a different protocol.
Maybe you should check out https://github.com/bkerler/edl which is the "standard" EDL client.
(I was so frustrated with this Python version that I wrote my own native Windows version, YMMV.)
On your 2nd device it's probably in fastboot mode or something or even ADB.
That's why you should run usblog.exe on it.
A broken screen is not a big deal, you can view the screen even without installing any software.
Try adbgrab.exe It's much slower than scrcopy or something, but it works on (most) anything.
I looked to see if that unit supports Sahara. I found this thread: https://forum.xda-developers.com/t/...-pc-as-qualcomm-hs-usb-qdloader-9008.3508606/
Maybe you should try getting your 2nd unit in EDL? If it connects then you know there is a problem with your 1st unit.
Maybe Samsung intentionally crippled EDL for security reasons?