Hello everyone, I bought a brand new IPPO Q78 (Android 4.0.4) via focalprice.com 2 month ago. First day of using it, and by using I mean simply installing a few apps, and after reboot, I got BOOT LOOP problem, so it wasn't able to get to tablets home screen. After lot of reading about similar problems, I was able to successfully unbrick it using (I suggest others with same cheap china tablet that are also soft bricked to use this program, it really was the only one which helped me):
http://forum.gsmhosting.com/vbb/f781/android-tablet-wifi-cpu-a10-a13-wipe-rom-easy-zakir-gsm-1656461
Here is my situation now, you can view it:
http://www.youtube.com/watch?v=cU1KYIrvZWI
Before, when it was soft bricked, at least after this android logo came the android animation that looped forever, but my computer was able to recognize and install the drivers for Android ADB device, now it can't, it won't recognize my tablet no matter what, ONLY when I press volume up and connect it to usb port, then it recognizes and installs vid_1f3a_pid_efe8 driver, which also I cannot use with LiveSuite, why? I really don't know, I've tried every possible solution found on forums (mainly here, but elsewhere also).
Whole this situation is a result of me doing the CWM upgrade/install, I'm a newbie, so I cannot tell for sure what was it, I just know it was from xda--developers forum, more accurately this thread:
http://forum.xda-developers.com/showthread.php?t=2189640
after this, poof. I think it is hard bricked, and my question is, is there a way to flash it (btw, tablet is rooted) by only having access through mentioned driver vid_1f3a_pid_efe8 and without LiveSuit, cause I would have to download and try a 100 ROM's before I pin the one that suits my tablet. It's really a tough program to deal with, but if it's the only one, I would gladly format and reinstall my Windows OS as many times I need to to get it working.
Related
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
i've had a few issues with this on my Droid Pro. with windows connection a connection assistant came up with some options that I was able to get it to work as a drive.
Getting it to work with adb is another issue alone. The phone needs to be in "debug" mode. I would search for a tutorial on this because you need to edit files on the computer.
for example on my windows I needed to edit one set of files, while on my linux I had to edit another set of things.
I leave my phone in debug mode because i use it for my android app dev on both computers. try that and see if it shows up on your mac.
Hi, I'm kinda of a noob at this stuff, but I've learned quite a bit recently from just reading around, so bear with me if I don't understand or need more specific instructions. I have the trio stealth pro 7 and it is always stuck on the boot screen with the android logo when I boot. I was attempting to flash cm9 on the tablet but after I wiped the tablet initially, i couldnt find the cm9 rom on my internal memory while in recovery mode, so I ended up turning off my tablet, which now doesn't boot up anymore (stuck with android logo).
I found a fix where you can use livesuite and adb to fix this issue; however, after installing adb, my tablet is not being detected, (my phone does). My tablet is not being recognized by windows in general, and it doesn't show up under device manager. There was one part of the step where I need to install usb drivers for the tablet; however, I cant find any online. I have used the tablet before with my computer before the attempt to flash cm9, so I am guessing drivers should already be installed. I feel I can get this issue fixed if I can just get adb to recognize my tablet.
Perhaps this fix is not the one I need and maybe there's a simpler fix. I'm just too dumb to have realized it. Another note to add is, pressing the combination of power and volume buttons does nothing. Please help!!! thank you!!
hello,
I hope someone can help me with my AT&T LG Optimus Pro G phone, which I have royally screwed up.
I was experimenting with the cyogen mod and after installation I installed the freegee app and once the cwm recovery was installed, I decided to go into the recovery by holding down up volume and power button.
Once I was in recovery for CWM i couldn't exit out, and the phone constantly booted into recovery after every reboot, even if i took out the battery, and powered it on.
I tried reflashing the cynogen mod through the sd card, and even though I would get success message the phone would still reboot into the cwm recovery.
I started doing research on the internet and i found file exitrecovery.zip that could be used to possibly get the phone out of the cwm recovery.
After installing exitrecovery.zip, I rebooted the phone, and now I have complete black screen. There are no light, no hints the phone is even turning on, and I can't get into recovery( or at least I can't tell). The only thing now is that when i connect the phone to the computer the window tries to install drivers for the device, and eventually prompts to insert a CD for LG drivers. I already have LGUnitedMobileDriver v.3.10.1 connection drivers installed from their website.
Please help, I am really stuck here..... and have no clue what to do. I am fairly new with rooting and modding, and I am extremely miserable.
The phone is still under warranty from LG. Anyone if all else fails, and since the phone has no screen or lights, whether they would replace it?
Attaching the exitrecovery.zip that I used.
sobbing....
babaghanush said:
hello,
I hope someone can help me with my AT&T LG Optimus Pro G phone, which I have royally screwed up.
I was experimenting with the cyogen mod and after installation I installed the freegee app and once the cwm recovery was installed, I decided to go into the recovery by holding down up volume and power button.
Once I was in recovery for CWM i couldn't exit out, and the phone constantly booted into recovery after every reboot, even if i took out the battery, and powered it on.
I tried reflashing the cynogen mod through the sd card, and even though I would get success message the phone would still reboot into the cwm recovery.
I started doing research on the internet and i found file exitrecovery.zip that could be used to possibly get the phone out of the cwm recovery.
After installing exitrecovery.zip, I rebooted the phone, and now I have complete black screen. There are no light, no hints the phone is even turning on, and I can't get into recovery( or at least I can't tell). The only thing now is that when i connect the phone to the computer the window tries to install drivers for the device, and eventually prompts to insert a CD for LG drivers. I already have LGUnitedMobileDriver v.3.10.1 connection drivers installed from their website.
Please help, I am really stuck here..... and have no clue what to do. I am fairly new with rooting and modding, and I am extremely miserable.
The phone is still under warranty from LG. Anyone if all else fails, and since the phone has no screen or lights, whether they would replace it?
Attaching the exitrecovery.zip that I used.
sobbing....
Click to expand...
Click to collapse
Find flow ROM with expansion .exe and try it to sew from a computer.
could you further elaborate please
lykosha said:
Find flow ROM with expansion .exe and try it to sew from a computer.
Click to expand...
Click to collapse
hi, thanks for your reply. Again I very much new to the rooting and android OS tinkering, and nowhere close to an experienced user.
I tried to use google with your information in regards to how to use flow ROM with expansion.exe, but did not get any leads.
I would appreciate if you could elaborate more on this process.
When my phone is connect to the computer via usb is is constantly trying to install drivers. I had already installed LG usb connection drivers in the past and it was successful. It almost seems it tries to install driver yet fails after receiving no input from the phone, and then request LG CD with drivers.
babaghanush said:
hi, thanks for your reply. Again I very much new to the rooting and android OS tinkering, and nowhere close to an experienced user.
I tried to use google with your information in regards to how to use flow ROM with expansion.exe, but did not get any leads.
I would appreciate if you could elaborate more on this process.
When my phone is connect to the computer via usb is is constantly trying to install drivers. I had already installed LG usb connection drivers in the past and it was successful. It almost seems it tries to install driver yet fails after receiving no input from the phone, and then request LG CD with drivers.
Click to expand...
Click to collapse
Try to find driver on the web-site of producer. Set them. Overload a vehicle in Bootloader. In the controller of devices on компе must be determined your device. Then on a computer start sewing - .EXE.
Did you get this problem resolved? I have the exact problem with the exact phone!!!
thank you very much
My tablet got stuck on the boot screen (a 'bootloop') and so I downloaded the Swedish instructions, tools and firmware image files from the manufacturer's website. I installed the driver on my laptop, connected the tablet, flashed the latest firmware and got it working. Annoyingly, the Chrome browser would not work whatever I did, and eventually I tried to flash an older firmware image onto the tablet. This killed it completely. The screen shows nothing at all; you can just about tell that the backlight has come on due to a dim glow, but the screen is still blank.
The worst thing is that the laptop no longer detects that the tablet is connected to it. It does not even report it as an unknown device. This is what really worries me.
I've read other threads on this forum where Flashtools is advised for bricked phones, but will this work with a tablet where the computer cannot even detect the device is attached?
Any help will be much appreciated many thanks.
Go to a repair shop is the only solution
i can do any thing except damaging your device. GOD DOES NOT DO THAT
Pay1 said:
My tablet got stuck on the boot screen (a 'bootloop') and so I downloaded the Swedish instructions, tools and firmware image files from the manufacturer's website. I installed the driver on my laptop, connected the tablet, flashed the latest firmware and got it working. Annoyingly, the Chrome browser would not work whatever I did, and eventually I tried to flash an older firmware image onto the tablet. This killed it completely. The screen shows nothing at all; you can just about tell that the backlight has come on due to a dim glow, but the screen is still blank.
The worst thing is that the laptop no longer detects that the tablet is connected to it. It does not even report it as an unknown device. This is what really worries me.
I've read other threads on this forum where Flashtools is advised for bricked phones, but will this work with a tablet where the computer cannot even detect the device is attached?
Any help will be much appreciated many thanks.
Click to expand...
Click to collapse
Yes, as @droid_god said the only way is a repair shop because they use those jtag devices to fix your phone.
Hi,
Yes, I know, there's a million topics about this and I'm pretty sure I tried them all!
Long story short: been running Lineage OS on my Tab 2 for a while but it's been sitting in a drawer. Saw a video about using old tablets for emulating retro consoles and the Tab works a dream for that. So I bought a Bluetooth controller for better gameplay but it just wouldn't work under Lineage so thought I'd flash the original ROM back onto it to see if that would work. I'm not a n00b, but haven't done it for a while so thought to be safe I'd follow a guide. All seemed to be working well when Odin crashed and left me with the Firmware Upgrade Failed error.
I've been trying for about four hours to get it back, but having no luck. I've tried the latest version of Odin, as well as the old 1.7 version I was using; tried Kies, tried uninstalling Kies; tried uninstalling the stock drivers MS installed when connected, no go. Interestingly Odin doesn't seem to see the Tab at all now, so I tried the UniversalADB installer, tried installing ADB drivers as well as Samsung drivers manually, but nothing works, it just sits at "connecting" but never actually does. Also tried different stock ROMs to no avail. I think my issue is with the ADB drivers, just don't know how to fix it.
I don't know what to try now. Any advice?
Using MS Surface Pro (2017) running Win10.
Not allowed to post screenshots, but do have some.
Thanks.
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Tab_Triggerhappy said:
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Click to expand...
Click to collapse
Hi,
Thanks for your reply and sorry it's taken me so long to respond; I've got several health issues I have to work around!
I can't get into the OS at all, it's just stuck at the "Firmware upgrade..." screen and there's nothing else I can do with it.
It was rooted and I was running TWRP recovery, but can't access it at all now. I did a wipe in TWRP but was still able to boot into it before I ran Odin. Odin worked fine, then it just stopped for reasons unknown and now there's nothing I can do with the Tab at all.
I see this in Device Manager: samsung mobile usb cdc composite device. Have tried manually installing driver but nothing seems to work.
Have tried it on my Mum's Win7 machine, but to no avail. I really need ADB drivers but I can't install them without turning on debugging on the Tab and I can't do that because I can't get out of this blasted error screen!
There's literally nothing else I can say about it as this is all that's happening.
Annnnd, now it doesn't seem to want to hold a charge. :crying:
Thanks again.
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Tabby22020 said:
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Click to expand...
Click to collapse
Maybe a longshot, but you can test if this free version can access the tab:
https://www.tenorshare.com/products/reiboot-for-android.html
No use buying if it can't.
But since Device Manager sees something it's worth a shot.
Do you have to longpress power button to turn it off?
If so... when the screen goes off, have you tried to quickly let go of the power button and immediately press it again together with Volume Up?
Or down, for download instead of Recovery.
With my P3100 it was much easier with no charger plugged in...
Edit:
Tried the software and my tab is OK, but no connection established anyway. Only result was that I couldn't access tab in File Explorer and MTP state... only PTP.
In Device Manager I got a new Android Device: Something like Google Nexus ADB... sorry but I uninstalled it directly without noting exact name.
Replugged USB cable and MTP working again.