Before I begin I should mention that I have been scouring the interwebz for an answer and while I've been to XDA forums multiple times with no avail, I still feel it is the most appropriate place to ask.
Basically, like many people I've seen on XDA, I've purchased a "GooPhone i5c" from Aliexpress. I put that in quotations because I believe from the research that I've done, the phone I have is a knock of (of a knock off) and no GooPhone ROMS have worked so far.
I'm lost and seeking help, the phone is in a state of complete death, pressing buttons does nothing (no screen back light!), my computer does seem to recognize it, however. Basically, when I plug it into the PC, I it's recognised as "MTK USB Port (Com 5)" and that's about it. The phone was working when I originally got it but being stupid like I am, I attempted to flash a new ROM with no knowledge of the process whatsoever. It was stupid and I don't plan on doing it again.
I've attached a little image with the specs rundown from the Aliexpress page. What do guys?
Related
Hello XDA forum! I am new here but I have enjoyed reading through many of the great posts you have available. I have a problem and I'm hoping you can help me. I'm learning quite a bit about the android OS and dabble in some minor tablet repairs but I still consider myself a noob, especially after reading some of the more technical posts! I have a couple of tablets here that are locked up after too many pattern attempts and I'd like to do a factory reset, but I just can't seem to get them into recovery mode. All the normal keystrokes yield no results. For example:
Tablet 1 is a 7" Noria by Chromo that identifies by my computer MID-X15. It's recognized in device manager as being installed with correct drivers. To the best of my knowledge USB debugging is not activated as I have tried both Multi Tools and platform-tools adb, while the device is not shown on either program. I have also tried numerous different key combinations from a powered-down state (vol - & vol + with power, just vol + and power, just vol - and power, and repeatedly pressing different combinations both at and before the manufacturer splash screen). The internet has proven to be less than helpful as I'm on my 3rd hour of forum surfing. I have never flashed a tablet before and I'm not precisely sure if can be done without USB debugging on or without being able to access the system. I am perfectly willing to purchase a TF card and attempt the process but there's not a ton of information about this relatively obscure little tablet.
Tablet 2 is a Klu by Kurtis. It is also a 7" tablet and I have the same problems with the USB debugging being off. On this device I can get into the screen with the android on his back with the red exclamation mark, but the recovery console never starts. Numerous hours of surfing and countless attempts at alternate keystrokes have also yielded no results.
If someone would be so kind as to offer a few suggestions or point me in the correct direction I would seriously appreciate it. Thank you so much!
(close to) 24 hour bump. Hopefully someone may have a suggestion for me. Thanks in advance!
One more bump. Anyone?
Unfortunately, after researching both tabs, I have found that neither tablet is very good quality.
Chromo Noria - This is a very well-known tablet to be problematic for no reason at all, and once this problem occurs, nobody has discovered how to retrieve the system.
Curtis KLU - This also is not the greatest tablet ever. Fortunately, I've found this thread for you to take a look at - it contains instructions on how to boot ClockworkMod.
Hope this helps.
Thank you for the link, thenookieforlife3! I will read over that and give it a shot. I realize these tablets are virtually worthless. It's one reason I don't mind experimenting on them with some more aggressive techniques if any exist. The biggest problem is just getting into the darn things to do anything (aggressive or not, lol). Perhaps something in that thread will give me a technique I can use.
I'm still open for other suggestions as well. These are throw-aways so I'm willing to get creative. I'm wishing there were jumpers or, heck, a couple traces i could short out with a screwdriver to force it back to a factory setting, lol.
[email protected] said:
Thank you for the link, thenookieforlife3! I will read over that and give it a shot. I realize these tablets are virtually worthless. It's one reason I don't mind experimenting on them with some more aggressive techniques if any exist. The biggest problem is just getting into the darn things to do anything (aggressive or not, lol). Perhaps something in that thread will give me a technique I can use.
I'm still open for other suggestions as well. These are throw-aways so I'm willing to get creative. I'm wishing there were jumpers or, heck, a couple traces i could short out with a screwdriver to force it back to a factory setting, lol.
Click to expand...
Click to collapse
I can see that. It's always fun to be aggressive every once in a while.
Don't we all wish that there was a hardware method to factory restore our devices? :laugh:
Am I right?
I too have been tinkering with a chromo noria 7" tablet in my spare time, as my son got one of these last christmas and its been stuck in a boot loop for no reason for almost six months now. Today I decided to play and discovered that adb could see it while it was boot looping and tried adb reboot recovery command and to my surprise it booted the recovery menu. That being said, does anyone know what I can flash from there cuz a wipe/factory reset does not fix the loop. Any advice would be happily welcome and im sorry if I'm posting wrong in any way. Hope at least my findings are helpful.
Sent from my Moto G using XDA Free mobile app
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
kimber015 said:
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
Click to expand...
Click to collapse
Before I start: DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR YOUR ACTIONS BY FOLLOWING MY INSTRUCTIONS. YOU ARE FULLY RESPONSIBLE FOR YOUR ACTIONS.
Now we got that out of the way...
Try upgrading to 4.4.2: http://sbf.droid-developers.org/phone.php?device=14 (Get the firmware here)
Use the thread you mentioned: http://forum.xda-developers.com/showthread.php?t=2542219
Hello xda!
Apologies if I mess up on technical terminology, I'm still quite new to this stuff and am trying my best to communicate. If anyone could help this noob figure this problem out it would be greatly appreciated!
Long story short:
Bought OPO September 2015, hard-bricked March 2016
Ran stock (COS?) though it randomly froze and restarted before the brick (No time to investigate, just waited on update)
No damage done as far as I know- physical or water
No response to anything such as fastboot
I tried all the basic solutions such as charging, fastbooting, power cycling, etc. but the device showing as QHSUSB_BULK and no response to any stimulus told me it's completely hard bricked.
So the next logical step was to attempt unbricking through Netbuzz's guide:
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
I got to the point of installing the driver correctly (Qualcomm 9008) after downloading from the Qualcomm 2012 drivers (running windows 7 so the driver.iso wasn't really on par) but after trying to run Msm8974DownloadTool (as administrator of course) it would get stuck at trying to flash(?) the first image(?) 8974_msimage.mbn and disconnect each time, just looping over and doing this each time. (The line doesn't turn red and does not read "Sahara" like other's experiences, it just tries to flash(?) again and the disconnect sound is heard.)
I browsed the forum more and found this recovery tool by Zyxxeil:
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
to see if it just needed an updated version of the tool, but that didn't work either.
I have tried different COM ports and different wires but the same 8974_msimage.mbn issue occurs each time. I have yet to try another computer or OS like Windows XP but I doubt it'll yield any results. I've browsed the forums and found other people experiencing this same problem but no solution to it exists as far as I know.
Reading Heisenberg's post here:
http://forum.xda-developers.com/showpost.php?p=54561962&postcount=7
it seems to me that if the image is having trouble flashing then something is wrong with the actual hardware.
Is it that I've likely destroyed my partitions somehow? (which I understand as some kind of storage)
If so does that mean what I need is called a JTAG repair? (If someone could explain that too, that'd be great!)
Is it still possible for me to still unbrick on my own as far as anyone here knows?
I am reluctant to send to Oneplus repair in that they would simply charge me for a replacement motherboard if that is unnecessary and costly. If a JTAG repair is cheaper than that and could work for my device, then it would be optimal.
Thank you for reading, and in advance if you respond!
Anyone please?
Well long story short i busted the lcd when replacing the charge port flex.. The owners mother is sick and she really needs the contacts. Charge port is now functional and commucates with my pc but kies and other backup utilities are not cutting it and i think its guna be more complex then that becuase nothings ever easy for me.
Phone does respond.. Led comes on/sound works.
Ive installed/reinstalled all the legitimate drivers i could find but 'mtp device' never actually installs in device manager.
Ive had a good bit of experience rooting and backing up android stuff before. No worries i can understand whats happening.
If anyone can help me with some info on how to go about it with making a minimal footprint(meaning root.?) you would be a hero.. Normally i would do more research but im limited on time. I ate the cost of a new screen so if all else fails ill have the phone back together friday/Saturday.
are the contacts backed up to google? if they are, they can be accessed from any device, phone, tablet, computer.
i believe its the same if its backed up to a samsung account
I'm new to this forum and this is my 2nd attempt to get help to solve my problem. I have read ALL the rules posted in the XDA New User Guide - Getting Started On XDA, as well as all of the linked pages that are suggested to read before posting. It was very informative but I'm more confused then ever about the right place to seek help. This is all very overwhelming and I'm afraid I'm going to say something to offend someone or post in the wrong place and get in trouble, or worse, ignored. I suspect I did just that in my last post because I never got a response. I apologize in advance if I have done something wrong.
Ok, I'll do my best to explain my problem. I have an LG K20 Plus (I'll refer to this as my original phone) that I bought, brand new, from T-Mobile in May. In August I cracked the screen but continued to use it because besides the crack, it worked fine. By September the crack had worsened significantly and I decided to replace the outer glass as I had successfully done that with my older LG G3.
In that process, while trying to get that dreadful glue off, I scraped off some of the black stuff under the glue on the LCD which caused a white spot, about the size of a 1/2 dollar, on my screen. Although it was bothersome, the phone itself still worked fine. I continued to use it while I searched for the easiest way to fix it within my budget. After reading posts here and realizing it would work, I bought a used LG K20 Plus (I'll refer to this as my used phone) with a bad esn. The plan was to put my original logic board into the used phone and be on my way. That didn't happen.
When the used phone arrived, I turned it on to verify everything worked. I then put my original logic board into the used phone and turned it on. I saw my orignal wallpaper and was so happy I had my phone back. Then I tried to swipe to unlock and nothing happened. I booted it up a couple more times and still nothing. I connected a mouse via an OTG cable and verified that there were no more obvious issues with the phone except the digitizer. To confirm the dispaly wasn't faulty on the used phone, I put the used logic board back into the used phone it came with and booted it up. The digitizer was back to working again. I ran through as much as I could on a locked phone and the digitizer worked like new.
I, carefully, put my original logic board back into the used phone and, again, no touch capability. Again, I researched this problem to no avail. I realized I was way over my head and I decided to ask for help instead of making things worse by trying to fix it without knowing what I was doing. So, I put the phone in a drawer and asked for help here. That was a month ago. I know you are all very busy and, like I said earlier, I'm sure it's my fault and I messed up somewhere because my post didn't receive any replies.
I can't use my original phone because I have no touch ability and I can't use the used phone because it has an esn lock. At this point I decided to try and (I'm sure I'm using the wrong terminology here) flash the used phone and root it to bypass the bad esn lock. After researching that and seeing the word "illegal" A LOT, I decided I just didn't know if it was legal or not, so I decided to not take the risk of doing something that may get me into trouble.
At this point I decided I didn't have much to lose so I backed up my original phone and, with only the display of the used phone attached, I started the process of flashing it with TWRP and rooting it via this guide https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-k20-plus-t3616248 So, it is now successfully rooted but it still has no touch ability. The really weird thing is, while I was in TWRP Recovery mode, the touch ability worked again. But as soon as I rebooted the phone into regular mode, the digitizer stopped working again. I'm so confused and I don't even no where to start looking because I can't define the problem or the exact thing that is failing. I don't even know if it's hardware or software related.
So, I guess my question is, does anybody have any experience with this kind of problem you could share with me. I'd settle for someone being patient enough to explain to me exactly what is going on so I could research it better myself. Asking for help was not my first step. I have been looking and looking for 6 weeks now. I'm way out of my league with this stuff. It's really difficult to find a solution to a problem you don't quite understand. It's a little bit like being told to look up a word in the dictionary to find the spelling.
*LG K20 Plus
*LG-TP260
*T-Mobile
*Rooted
Baseband: MPSS.JO.
2.0c1.2-00012-8937_GENNS_PACK-1.85468.1
I think it's my original ROM
Kernel Version 3.18.31
I flashed TWRP
USB debugging enabled
OEM Lock Off
Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.
zelendel said:
Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.
Click to expand...
Click to collapse
I'm so sorry but I have run into a few problems .. firstly, on my phone I have to use a mouse connected via OTG cable because I have no touch ability and my usb connection is set to "charge only". Apparently you can't change that until the phone is plugged in and obviously I need the mouse so I can't connect to computer. I downloaded an app called LogCatX and made a log file but I don't know how to attach a file and when I copy/paste it into the reply it says it is too long and reduce by 30000 characters. Any advice?
HelpNeededPlz said:
I'm so sorry but I have run into a few problems .. firstly, on my phone I have to use a mouse connected via OTG cable because I have no touch ability and my usb connection is set to "charge only". Apparently you can't change that until the phone is plugged in and obviously I need the mouse so I can't connect to computer. I downloaded an app called LogCatX and made a log file but I don't know how to attach a file and when I copy/paste it into the reply it says it is too long and reduce by 30000 characters. Any advice?
Click to expand...
Click to collapse
I think the new touch screen will need a calibration.
PS: i liked how you explained your problem
Sorry for my confusion but I'm not sure if you were telling me what I should do to figure out where the incompatibility issue may be or if you were asking me to upload the catlog so you could look at it and help me. I don't know what a catlog is, nor how to interpret it. At any rate, 6 hours later, I have, finally, figured out how to upload a file. :victory: I've been looking at how to fix a kernel incompatibility issue and I've read you can flash a custom kernel. If I did something like that, would that resolve my problem. Are they specific to the version of operating system your phone has (ie nougat, marshmallow etc) or do you need to use one for your specific phone model? Would flashing a custom ROM do the same thing? And is that model specific or OS specific? Where would I go to find something like that?
NOTE... In looking for differences in my phone to try and figure out where this kernel compatibility issue might be, I noticed that there are two different numbers on the midframe of my phones. I don't know if this means anything. I'm just trying to help someone help me.
zelendel said:
Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.
Click to expand...
Click to collapse
Hello? Was this the extent of your help? I'm not sure if you were asking me to run a catlog to upload so you could help me figure out what was wrong or if you were just telling me what to do and then moving on. Because if it was the later, all you've done is piled more stuff on my steadily growing mound of confusion. To make matters worse, my posts is showing as getting a response, so, I fear, nobody else will look at it and I will be left in the same place as before. If someone happens upon this post, could you give me advice that will actually help me solve my problem, along with instructions on how to do whatever I need to do. Thank you in advance. Until then, I'll be anxiously awaiting your reply....