Database Info

Allwinner Boxchip A10 10.2" Mini Netbook

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.

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.

[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?

Unable to enter EDL

xt2043-4 unable to get into EDL mode. It died during a restore with the Lenovo "smart" software.
When plugged in I something's get a single led blink. Nothing however when I plug it into my PC. I have an edl cable that doesn't seem to do anything either. Are there test points/jtag? I don't want to open it up unless I can actually do something.

kaleamity said:
xt2043-4 unable to get into EDL mode. It died during a restore with the Lenovo "smart" software.
When plugged in I something's get a single led blink. Nothing however when I plug it into my PC. I have an edl cable that doesn't seem to do anything either. Are there test points/jtag? I don't want to open it up unless I can actually do something.
Click to expand...
Click to collapse
Download Qualcomm qloader drivers....see if device shows up as Qualcomm 9008 In Windows Device manager or maybe it says Qualcomm bulk hub...if it is you are in edl mode and you need to download blank flash file from the rom archive on lionnet moto firmware under our device...unzip the file and run the .bat file with admin privileges it will run the file and reload the critical bootloader files to get you to bootloader screen ...then reflash STOCK...I did this last week because I rebooted to edl from TWRP...

Nothing shows up. I get a few led blinks but nothing in device manager or otherwise.

Anyone found the answer to this? Im having the same issue

kaleamity said:
xt2043-4 unable to get into EDL mode. It died during a restore with the Lenovo "smart" software.
When plugged in I something's get a single led blink. Nothing however when I plug it into my PC. I have an edl cable that doesn't seem to do anything either. Are there test points/jtag? I don't want to open it up unless I can actually do som
Shane8705 said:
Anyone found the answer to this? Im having the same issue
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hi there! I myself have a hard-bricked G Stylus (US model). After reading this and related threads, as well as doing a LOT of independent research on this. I have a feeling that the only hope lies in potential EDL test points located on the motherboard. I've looked at a teardown video on Youtube, and I see several sets of potential test points. From further research, it appears that test points for EDL are always located right next to each other.
I'm purchasing some iFixit tools this month, which include the required T3 driver bit. Once I get access to the motherboard, I fully intend to test every possible set of EDL points. I'll post my findings on this and any related thread in the G Stylus forums here on XDA. If I'm successful in restoring the phone, I will post a photo of the points that need to be bridged to enter EDL mode.
Wish me luck!

Have you had any luck with this? And I'm wondering if you mind describing how you got into this situation.
On my phone (I think it's a Moto G Stylus, XT2043-4, that I got through Google Fi in the US), I was trying to modify an app on the phone. So I used "adb pull" to get the APK. Then I extracted, edited, and recompiled it with apkeasytool, but then I couldn't write it back to the proper directory because the filesystem was read only. At that point I went through the process of unlocking the bootloader via the Motorola website, and then tried to root the phone. That's where my problems started.
I can go through the details if anyone thinks it would matter, but essentially, I wasn't paying attention and flashed the incorrect files... multiple times... I ended up with a phone that appeared to be dead (nothing on the screen no matter what I did). However, I noticed that when I plugged it in it popped up as the "Qualcomm 9008 Port" thing in Windows Device Manager. After reading up on that I realized that it was in EDL mode and I tried to run the blank-flash.bat file I found. After some trial and error, it appeared to work, however, I was holding the power button at the time and the phone may have restarted in the middle of the script. At that point, it stopped appearing in Device Manager and I haven't gotten it back, except that after disconnecting the battery, I get an LED flash when it's plugged in as well as some other strange behavior that I'll describe below.
Anyway, after all the previous catastrophes, I decided to open it up and look for these mythical test points. I'm attaching some pictures in case they help anyone. One after exposing the mainboard, another after lifting the obvious cables, and finally one with the obvious test point candidates numbered.
I'll describe what I've figured out so far:
- When I disconnect the ribbon that covers 6, 7, 8, and 9, I don't even get the LED flash when connecting/disconnecting the phone to the computer. So I don't think those are likely to be test points, but I don't know what that cable is for.
- The middle ribbon appears to connect the battery, and I don't get the LED flash when that is connected. It doesn't happen when I connect the USB to the computer OR when I hold the power button. I don't understand why this happens.
- The rightmost ribbon doesn't cover anything. So I leave it connected.
- When USB is connected and not the middle ribbon, all the points seem to show 0V except 3 (0.417V) and 5 (1.803V). 6 is 1.792V when the middle ribbon is connected, but dissipates during measuring when the middle ribbon is disconnected. 10 also seems to dissipate when the middle ribbon is disconnected, and I can't measure it when connected because it gets covered up.
- If I short or ground 10 or 12 while plugging in, the LED flashes until I remove the short or ground.
Anyone have any thoughts? Anything else I can check?

moorevineyard said:
Have you had any luck with this? And I'm wondering if you mind describing how you got into this situation.
On my phone (I think it's a Moto G Stylus, XT2043-4, that I got through Google Fi in the US), I was trying to modify an app on the phone. So I used "adb pull" to get the APK. Then I extracted, edited, and recompiled it with apkeasytool, but then I couldn't write it back to the proper directory because the filesystem was read only. At that point I went through the process of unlocking the bootloader via the Motorola website, and then tried to root the phone. That's where my problems started.
I can go through the details if anyone thinks it would matter, but essentially, I wasn't paying attention and flashed the incorrect files... multiple times... I ended up with a phone that appeared to be dead (nothing on the screen no matter what I did). However, I noticed that when I plugged it in it popped up as the "Qualcomm 9008 Port" thing in Windows Device Manager. After reading up on that I realized that it was in EDL mode and I tried to run the blank-flash.bat file I found. After some trial and error, it appeared to work, however, I was holding the power button at the time and the phone may have restarted in the middle of the script. At that point, it stopped appearing in Device Manager and I haven't gotten it back, except that after disconnecting the battery, I get an LED flash when it's plugged in as well as some other strange behavior that I'll describe below.
Anyway, after all the previous catastrophes, I decided to open it up and look for these mythical test points. I'm attaching some pictures in case they help anyone. One after exposing the mainboard, another after lifting the obvious cables, and finally one with the obvious test point candidates numbered.
I'll describe what I've figured out so far:
- When I disconnect the ribbon that covers 6, 7, 8, and 9, I don't even get the LED flash when connecting/disconnecting the phone to the computer. So I don't think those are likely to be test points, but I don't know what that cable is for.
- The middle ribbon appears to connect the battery, and I don't get the LED flash when that is connected. It doesn't happen when I connect the USB to the computer OR when I hold the power button. I don't understand why this happens.
- The rightmost ribbon doesn't cover anything. So I leave it connected.
- When USB is connected and not the middle ribbon, all the points seem to show 0V except 3 (0.417V) and 5 (1.803V). 6 is 1.792V when the middle ribbon is connected, but dissipates during measuring when the middle ribbon is disconnected. 10 also seems to dissipate when the middle ribbon is disconnected, and I can't measure it when connected because it gets covered up.
- If I short or ground 10 or 12 while plugging in, the LED flashes until I remove the short or ground.
Anyone have any thoughts? Anything else I can check?
Click to expand...
Click to collapse
Hi there! I actually did find some more potential EDL points underneath the speaker grill (underneath the black plastic piece below the battery).
I've tested them all... and no luck so far... The only reproducible result I can share is:
When the battery is unplugged, attempting to use any two points results in an LED flash every 15 seconds or so. No other behaviors.
Motorola came so close to having a perfectly repairable phone... What a disappointment.

This seems strange to me. Most of what I've read about other phones with the EDL mode and test point access seems to indicate that it's not possible to mess it up with any of the normal tools (adb, fastboot, recovery, blank-flash, etc.). Is that incorrect?
Basically, I had the impression that the Qualcomm EDL mode was provided by a more segregated component on the board that could reprogram the rest of the system, but not incorrectly reprogram itself the way you can incorrectly reprogram the bootloader.

moorevineyard said:
This seems strange to me. Most of what I've read about other phones with the EDL mode and test point access seems to indicate that it's not possible to mess it up with any of the normal tools (adb, fastboot, recovery, blank-flash, etc.). Is that incorrect?
Basically, I had the impression that the Qualcomm EDL mode was provided by a more segregated component on the board that could reprogram the rest of the system, but not incorrectly reprogram itself the way you can incorrectly reprogram the bootloader.
Click to expand...
Click to collapse
It appears that certain models aren't failproof. Similar situation with a mislabled black-flash. Flashed it multiple times and ended up unable to do anything going forward. I saw the edl points on a similar phone the moto g power on youtube and hoped that they were somewhat easily identified. Unfortunately doesn't seem to be the case, I too have tried every combo that I saw on the board. Same blinking lights as described, but nothing shows on the PC. I am able to get it working on other devices however as I have two.

Today I started researching repairing a hard brick of a moto g stylus after letting it sit around for a couple months. I came across the android doctor video that shows how to do this on a g8+ but unfortunately I found out that the mobos aren't laid out similarly. Subsequently found this thread. Bummed to find out the EDL points haven't been discovered. Hopefully someone does find them and posts here. I guess I'll do a little more research but otherwise I guess it's back to the shelf this phone goes.

FWIW I found this thread, but the points illustrated here don't seem to work for me: https://forum.xda-developers.com/t/sofia-edl-points-found.4457105/

Well I tried most points on the board. I was cycling through when I hit either I-J or J-K and my pc said there was a short on a USB port. I removed the ribbon cable to reveal that the jumper I made had melted. The led no longer flashes and the phone is now totally dead jim. Charging for a while doesn't seem to have any effect, nor letting it sit. Whatever shorted killed it. I was incredibly careful but clearly not careful enough.
That said I have another 2020 stylus (bootlocked unfortunately). So I'll be part harvesting as my current phone degrades. Thank you all for your help and good luck to you on this phone! Shame on Moto for really trying to keep people out of it... The glue, the edl cable not working, the points being potentially behind the battery ribbon. Just unnecessary nonsense imo.

EDL es el 10 y 12 me pasa que no se mantiene se desconecta despues de 5 segundos

Pixel 4a Not Charging after Beta update

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.