Lenovo A850 Bricked and cannot use USB - Lenovo A850
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.
Related
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.
[Q] S4 Help needed (Warning: Long story)
Hey guys, let me just start off by saying I have spent almost 8 hours straight today trying to figure this out and dig myself out of a hole I've created for myself, that being said, I'm going to try and be as detailed as possible so you guys know EXACTLY where I am and what I've tried. This post looks long but that's because it is. It's pretty much my entire day's worth of trouble typed out. So just bare with me and see if you guys can help me out here! I have a T-Mobile Galaxy S4 model: SGH-M919 it has Android 4.4.2. Now on to the problem: I've had this phone for almost a year now and a few months ago I rooted it. Did a simple Youtube tutorial and used Odin to do the work and everything worked out fine. A couple months down the road (yesterday), after using the phone like a teenager, downloading apps and cluttering it up it started to slow down and not run some apps. After thinking about it I decided to factory reset it. All of my contacts, photos, and videos were backed up on Google so I thought "why not?" Well, this is where $#!% hit the fan.. being rooted then factory reset, right before the phone came online it had me answer two questions about the root. Something to the effect of "Do you want to keep root? (This option is not reversible)" I thought since I wasn't using the features I originally rooted the phone for I figured nah just get rid of the root. So the phone did its T-Mobile boot up and started the Initial setup. Everything up to to this point was fine until I wanted to log in to my Google account during the setup. Please understand that where I am I have full 4G LTE coverage and have access to a pretty fast and sturdy wifi connection. Well, when it came to the google sign in I entered my email and password and it came up with a message reading "Can't Sign in - Can't establish a reliable connection to the server" (believe me i wish that was the only issue) so after reading that, I thought I'd try with my wifi.. nope. Same thing. Since neither my 4g or wifi worked I thought it was Google's servers so I tried again this morning, same thing. (keep in mind at this point i think my phone isn't rooted anymore.) I call the t mobile store and they give me a technical support number, so I call it and I tell them i cant sign into Google. The gentleman told me he cant do anything because he can tell my phones been rooted. Only thing he suggests is to contact Google, well, the customer care number just tells you go to google.com/support and there's nothing there about my problem. This is where I dig my hole even deeper. I tried another factory reset and up in the top left corner i still see that root text. Even the rooted android symbol pops up before the Samsung logo or t mobile. Since I saw that I thought "ohh it just didn't get unrooted all the way." I look up ways to completely remove a root and a lot of them require plugin your phone into the computer and using Odin to flash a stock firmware on to the device. I went to plug my phone into the usb port but my computer didn't recognize the usb device, having experienced this a long time ago I searched around for the latest Samsung usb drivers and I installed those. Device still isn't recognized. Let me just note before people tell me to use MTP mode or Developer tools> usb debugging or connection mode.. The only thing that happens when plugging my phone via usb is the phone starts charging and my computer makes the trumpet noise like something is plugged in. Other than that, there is NO notification of it being plugged in. The reason i stress this is because I called Samsung technical support at this point and the guy (not gentleman) treated me like a 5 year old and ran me through all of these options after i told him I already did everything he was suggesting, including downloading Samsung Kies 3 and having it install the drivers. It does not pick up the device either.. at this point I looked up ways to remove the root without the computer. I found out you can just go into the root app "SU" or something and theres a remove root option. I jumped on that opportunity and had it removed. I restarted the phone and all the problems still persist, it even still has the root text on the top left when you factory reset it again. However now, even if you factory reset and select the option "keep root," thinking it would bring back the"SU" app it does NOT. So lets recap. I have a phone that thinks its rooted and even appears rooted to t mobile but doesn't have any of the root apps or privileges or capabilities to fix my Google log in issue (like the host file in filemanager). And I can't re-root to get that app back because none of my 3 usb ports, 3 different usb cables (one being the cord that came with the phone), or any of the ports/cables on someone else's computer will recognize the darn thing to work on that way! I have all these issues that are supposed to fix each other but I can't do any fixing because they cancel each other out too... I'm at a dead end. In case this isn't the right forum/website/thread/post area etc.. I have this whole message saved in Microsoft Word document so I can repost it anywhere you guys might suggest better results. Any help/advice will be much appreciated.
How to recover my Lenovo A936
Hi, I am looking for some help with a problem I am experiencing with a recently purchased Lenovo A936, (Golden Warrior). I hope this is the right place to post. I bought this smart phone from China and have been SO impressed with its performance, it is fast and has a great camera. However, I kept getting unwanted programs popping up so I installed AVG antivirus. It initially identified some 8 threats about 3 of these threats were apps that were installed by the vendor and were not able to be uninstalled, It was possible to remove the remaining threats apart from one which it stated “1 setting is not secure, the device is running in high privilege mode, it has been rooted” I think Lenovo are responsible manufacturers so I guess the retailer has put some nasty stuff on this phone, I have been able to use the phone for a few months by regularly deleting unwanted programs flagged up by AVG but it has got progressively worse to the point when there are now 10 threats that cannot be removed and there are some pop ups that seem to have hijacked the AVG as they come up on top when I open AVG making it impossible for me to access AVG. I usually switch off at this point! Sorry about the rather lengthy description above but my question is can I recover this phone? Is it possible to wipe everything off, (rather like formatting a computer hard drive), and reinstall the proper android operating system – is the operating system available as a down load? If it is possible to down load, how would this be done, get it on a computer and then connect the phone to the computer? I have android 4.4.4 could I put a later version on? If this is done, can I be sure that al the functions will work – for example does it need drivers for the camera etc. I dont really want to reduce this phone to an expensive paper weight but it looks like I have little to loose now as it is not usable apart from the camera. I would be eternally grateful if someone could offer some advice, (suitable for a not-too-techy). Thanks in anticipation, john.
S5 glitching in and out of monitor mode? or just a patchwork mess?
Im new to all this so pay no attention if its nonsence... My S5 G900f has a qualcomm snapdragon chipset, that doesn't support monitor mode, which i believe means that it doesnt support packet injections or packet capturing (driver related?) using the dsploit.apk for things like session hijacking, replacing web page images of a target and using script 'injection' to inject custom java script into a target web page, all sounds like things you'd need monitor mode to do. and if it is then i was able to do it with my S5. I dont know a lot about coding or how it all fits together and communicates with the hardware, so i may sound completely stupid, but this has done my head in for ages, so why not get it out there. 1. when i attempted to upgrade from my first custom rom, i had a bit of trouble, softbricked my phone and then flashed the two roms in various, alternate, wipe, format and install combinations until it finally booted to set up, and i stopped panicking. but this caused features from the first rom to appear within the second rom. ie: 3minute battery mod was installed through a add-on zip along with the first rom and nothing to do with the second at all. 2. inconsistencies within the file system, like file names that were apps included with the first rom. 3. dsploit.apk was bugged and crashed every 5 or 10 minutes. then would seem to glitch or stutter for a couple seconds before correcting its self and accomplishing its pen test. 4. i also remember watching green text in the terminal as it failed to connect or ID some part of the system but continued to retry in quick succession until it glitched and worked. (i think this was a similar type of app i was trying out at the same time but instead of GUI stutters, i could see the text rapidly stuttering and glitching.) 4. the dsploit.apk worked for me back then, even though it was temperamental. ive downloaded the apk a couple times since with various roms and ive got no where with it... was thinking maybe different aspects of the two roms had been filed or grouped together and created unstable triggers within the software, allowing it to briefly communicate with the chipset. i may be way off, but ive been sat here waiting for someone to solve this issue forever, i thought id share my thoughts, on the off chance it turns out to be something and i can finally get my S5 into monitor mode without OTG cables and other unwanted auxiliary components. thanks in advance G Carter
Do a clean install of you ROM, and please, don't panick. If you want to have a good time flashing ROMs and stuff, panicking is the last thing you want to do, it will cause stress and stress can lead to not being careful enough so stuff like this happens, well, always, if you are experiencing issues do a clean install. Just boot into recovery (I recommend TWRP) and wipe everything except external sd. Open ADB and sideload the ROM (or, if you have enough memory on a flash drive, plug it into your android and flash it from there) and then Google Apps.
Recover files from bootlooping Zenfone6
Dear all, from the occasional reboot my Zenfone performed every now in a while (which didn't bother me too much) it now reboots so fast that it usually has not yet booted to the point where I could get data off the device before it reboots again. As always, the backup is too old and I want to extract some data off the device. Most important are a few KBs worth of text notes. Here come some questions: - It seems to be a hardware fault. Are there educated guesses what may give me a few last moments with the device to extract data? Heat? Freezing? - Are there professional data recovery companies dealing with smartphones such that they can extract data from the chips without the phone working? - As it is a Qualcomm device: Would any access via QDLoader work or would it be as unstable as the rest of the phone? I appreciate any input. And yes, I know that I didn't backup often enough. Thanks, weaker
which rom are you on?
Sorry for the late reply. I'm on stock ROM with Magisk. In the end when it became worse, I let Magisk restore the images but this definitely seems to be hardware-related. I also did no overclocking and I don't use games on the phone so I think that it is also not a thermal issue. To keep the interested ones updated how it evolved: The situation is now as follows: I tried to boot into recovery via fastbooting the TWRP (the one I used many times successfully for my phone) after one of the phone bootings was stable for enough seconds so have ADB contact and go to fastboot mode. I hoped to be able to interact more stabily in the recovery. However, the result was that the phone rebooted (I am unsure if the TWRP transfer was finished before that) and then the charging screen appeared and the charging screen remained constantly on, even when pulling the cable. It didn't react to any keypresses in that state. I let it drain the battery (which was only a few hours as the screen was always on). Then, I plugged the phone in and it booted normally and was stable for 15 minutes or so, which gave me enough time to save the most important data. Phew. This session however seemed to be the last farewell. The phone started to bootloop and I switched it off*. Now the phone has always a black off screen and doesn't respond to anything: Pressing (and holding) the power button, also in combination with Vol+ or Vol-. Also plugging a cable to charge doesn't create any reaction. * switching it off worked the following way: The unlocked bootloader shows that one could press the power button to pause the boot. I can't think of why this might be a useful function in a normal situation. However, in my situation I could pause the boot and after some time it would switch off. That way I could at least break the bootloop.
you will have to boot into qloader to be able to recover your phone... follow step by step exactly what is mentioned in the below link, ypu should be able to recover your phone : Here’s how to unbrick Asus ZenFone 6 (Asus 6z) from QDLOADER 9008 mode - PiunikaWeb Is your Asus ZenFone 6 (Asus 6z) hard-bricked? You can use still flash via QDLOADER 9008 mode to give a new life to your dead handset. piunikaweb.com
Sorry to be the prick here, but next time post this in Q&A section. This one is for posting development (Kernels and ROMs)
OK, no offense taken. I thought that I would need to resort to some TWRP magic to get data off my device. @MOD: Feel free to move thread where it fits best.
For the sake of completeness: The phone is back from RMA. According to the sparse documentation they exchanged the mainboard and battery and some connector. Some firmwares are now newer than on the old mainboard (little surprise here). Bootloader unlock worked also on the new phone (some report that this would not work by default after an RMA, for me it did). So, ASUS did a great job dealing with the issue.