Database Users

I can't find model number for tablet and it won't boot.

The Sticker Info:
MFG.DATE: KS 110609 MM10
"Barcode"
S/N: 814PT01007G123A01472000
"Barcode"
SNID: 12365568720
I have two Acer tablets but can't find the model number for it.
Although It has sticker with SNID, S/N with other few info. It just hangs when I turn on the unit. I only see "ACER" logo with a code(ish) starting with letter and numbers. It reads: "MM.03.60.05.14.24" below "ACER" logo. I already tried the hard reset: VOL(up) + PWR. Whenever I do that step, the screen blinks suddently and it turns off. In chat with Acer, they couldn't help becuase the tablets were assembled and sold at another country. Please I want to know wether the unit is fixable.
I don't have cable at the moment. If this is firmware problem, is there a way to flash new firmware or recover into orignial mode?
These two tablet were given from a friend and he is no longer living in USA.
Please Help.

without a cable options are limited.
but head over too this thread http://forum.xda-developers.com/showthread.php?t=1839313
you will need an ext. SD card, place the update.zip on it and button combo to recovery. this will put a stock HC rom on yr tabs.....do a nandroid backup from HC to retrieve yr CPUID. This is important. if u brick it, having the cpuid is imperative.
all insructons are in the thread.
there's also a gr8 guide to flash the unlocked bootloader at post #20.
I've not heard of numbers appearing on the boot screen before and the hard reset not working could mean ICS is on there....if that's the case you will need a micro USB cable to fix.AND the cpuid....but try update.zip first
Sent from my GT-I9300 using Tapatalk 2

Also, without knowing what model you have, you can look in the Micro SD card flap, and see if it takes a SIM card. If not, then that should distinguish between a 500 and 501.
But without seeing a photo of the tabs, could be an a100 or 200.
Right now, we're just guessing with little information.
MD

The Tablet model number is Acer m500.
The model is m500.
Moscow Desire said:
Also, without knowing what model you have, you can look in the Micro SD card flap, and see if it takes a SIM card. If not, then that should distinguish between a 500 and 501.
But without seeing a photo of the tabs, could be an a100 or 200.
Right now, we're just guessing with little information.
MD
Click to expand...
Click to collapse

[Q] Boot not completing - likely hardware problem

In brief:
The N4 is stuck on the whirling circles during boot. It is likely due to some broken bit of hardware. I would like to determine where it's stuck. After that I can decide if repair is possible or if I don't need that feature and it can be skipped one way or another or toss the brick altogether.
In full:
While out of town S.O. dropped the phone and the digitizer shattered. She said the screen appeared to still work, but no input was possible. She ordered a new digitizer and dumped it on me to repair, little realizing the difficulty of replacing only the digitizer. Still, I gave it the ol' college try on a slow day at work, heating the glass shards to yield the glue and get them off the screen. After installing new digitizer I was not surprised that I had damaged the screen and just a few colored stripes displayed.
So I ordered and installed a digi/lcd assembly and I now have a functioning screen and digitizer. The problem is the system won't completely boot and is stuck on the infamous whirling circles. I am fairly certain that during boot some device is being queried and is broken, and the boot has no timeout to skip it and move on. I would like to know where it's stuck. I *think* the way to do that is to somehow direct kernel messages out the phone's USB so I can use PuTTY to display them on a workstation. I do not know how to do that. If there's some other way, like getting the messages to display on the phone's screen, I don't know that either. Hence my post.
The techie bits:
Long story short here's a summary of relevant actions I've done so far.
Phone still goes into the mako bootloader and I can use fastboot.
Used TWRP recovery to wipe everything (including itself)
Flashed factory 4.4.2 OS
Reinstalled TWRP recovery and had it root for me
I now have two ways to access the phone - fastboot when in the stock mako bootloader, and adb when I fire up TWRP.
Now what can I do to find where the system boot is hanging? Suggestions welcome.

first thing to look at - proximity / light sensors connector . phone will not boot if they are disconnected from mainboard.

RolF2 said:
first thing to look at - proximity / light sensors connector . phone will not boot if they are disconnected from mainboard.
Click to expand...
Click to collapse
I will check that. Thanks for the reply.
Edit: I just checked, and you were right on the money. The tab with the connector for that device had flipped under the mainboard so I didn't connect it. All fixed now and I have a working phone. I owe you a couple beers. Thanks.

Hi, you are lucky
I have a similar problem.
Yesterday i restarted my phone and >problem, stuck at X-boot-logo<
Already tried different roms.
Can get into fastboot-mode and therefore can have ADB with CMW-recovery.
I replaced my screen a few months ago.
Already checked proximity sensor cable.
btw:
at the beginning, one time I got it to "optimizing apps...", but it was stuck at "starting apps"
How can I see if my proximity/light sensor is dead?
can I use the Nexus 4 serial?
Any other solution?
Regards

You can try to downgrade to stock 4.2 android, phone most likelly will boot, but looks like you have lost your IMEI.

RolF2 said:
You can try to downgrade to stock 4.2 android, phone most likelly will boot, but looks like you have lost your IMEI.
Click to expand...
Click to collapse
OK, I'll try to go back to 4.2.
Anything I can do if I really lost IMEI?
I think you could be right.
I rebooted my phone because i got no network connection. (even after airplanemode on/off)
---------- Post added at 07:05 PM ---------- Previous post was at 06:45 PM ----------
OK, 4.2 booted successfully
Thanks.
but phone does not connect to network.
IMEI seems to be lost (*#06# shows nothing for imei)
What do you think about restoring IMEI with dd-command from "somewhere"?

take a look here : http://forum.xda-developers.com/wiki/LG_Nexus_4/Partition_Layout
do you have baseband version unknown too ?
if yes, first I would try dd mmcblk0p1 (modem / radio.img) and only after that next step would be m9kefs1/mmcblk0p8 , m9kefs2/mmcblk0p9 = IMEI
this is only speculation, never tried that ...

RolF2 said:
take a look here : http://forum.xda-developers.com/wiki/LG_Nexus_4/Partition_Layout
do you have baseband version unknown too ?
if yes, first I would try dd mmcblk0p1 (modem / radio.img) and only after that next step would be m9kefs1/mmcblk0p8 , m9kefs2/mmcblk0p9 = IMEI
this is only speculation, never tried that ...
Click to expand...
Click to collapse
no baseband too.
imei empty, not zero
I don't think dd mmcblk0p1 would be useful as it is only the radio.img.
You can find it in the stock image
The first step now is backupping the efs-partitions
do you mean directly writing IMEI to it?
I can try to copy the IMEI(or all partitions) from my brother's phone to mine
Thx

don't hurt to try dd modem partition first, maybe it's corrupted in some way ... why it's unknown ?

LG G2 D802 No Display, Bricked, Recovered

Hello,
This is my first post on this forum so hello everyone! This forum has helped me numerous times with various devices, it is a valuable source of information and the people here seem very helpful. I have searched but cant find a thread relating to my current issue so I decided to start a thread and hopefully get some answers.
Ill try to keep this short while still providing enough information, first things first my device is a D802T 32GB model. Timeline of steps ive taken are as follows.
-Running Ressurection Remix ROM
-Downloaded ROM update and flashed with TWRP
-Device would get to "Upgrading Apps" step then restart half way through, back to upgrading app, restart again and so on
-Flashed stock ROM with LG Flash tool 2014, Froze at 49%
-Tried again to flash Stock ROM, this time it froze at 10%
-This caused the phone to loose Download mode & Recovery.... HARD BRICKED
-Phone would show as Qualcomm HS-USB 9006 in device manager
-Used Ubuntu to flash Partitions
-Must have flashed wrong partitions, after I flashed them the phone seemed to be 100% bricked with no signs of life at all
-Managed to jump pins on chip inside phone to get it into Qualcomm HS-USB 9008 mode
-Downloaded BIN_LGD802AT-00-V10b-SEA-XX-SEP-04-2013-32G+0 TOT File and extracted partitons
-Used BoardDiag to re flash Partitions I extracted from TOT file above
-Phone now seems 100% fixed except for one issue NO DISPLAY!
The phone boots, I hear the boot sound, the touch screen works as it should but I have no display whatsoever not even a black screen. My question is can flashing partitions cause you to loose display but the phone still boot and retain digitizer function?
I repair phones for a bit of extra money on the side so I know what im doing but I wanted another opinion or two before I go ordering parts. Does this sound like I may have damaged something while jumping the pins or could it be the partitions I flashed? Also if I have damaged something how can I tell if its the screen or if I damaged the charge port flex as this carry's the display signal. Keep in mind everything else works on that lower board such as the USB port etc. It seems a massive coincidence I loose display after flashing partitions but then again I was fiddling with the insides but I have done that many many times before so what are peoples thoughts on this?
I appreciate anyone who takes the time to help

42 views and no one has any ideas at all?

Sorry m8.....the last time i had 9006 brick i flashed correct partitions and got my phone working through TOT.......
You could try a new flex cable or even a new screen to diagnose whether its a hardware problem, black screen usually indicates damaged LCD connector pins on LCD panel or flex cable.
Also having "white tv noise" indicates a damaged flex cable.
Next time you have 9006, use this! https://www.youtube.com/watch?v=_d5b_osUTug
You don't need Ubuntu and you have less chance of super bricking.

Hey mate thanks for replying,
I did try that method but kept getting an error (something about cannot find file specified) so I just went the Ubuntu method. I did plan on just ordering a new screen but wanted to be a bit more certain of the issue first. I wish I had of kept my old damaged screens so I could fit one to determine if the screen really is the issue.
I didn't need to touch the bottom part where the LCD flex cables plug onto the board but stranger things have happened, unfortunately the G2 doesn't seem to be very popular in my area as I dont know anyone else that has one that I could possibly put my motherboard in to know for sure its the screen.
I might completely disassemble it and inspect it under a magnifier to make sure I haven't knocked any resistors or anything off the board, ill probably end up just ordering a screen as it seems the only way to know.
Thanks for your help

LG G2 with null IMEI after crash

Hello
I have an LG G2 D802 that was working perfectly but some days ago, after a crash with broken screen the phone suddenly show the message "Service Disabled" and the code *#06# returns IMEI Null.
By the time of the crash it was kit kat, and I made a factory reset that did not solve the problem. After that I use LG Flash tool to install the lollipop 5.0.2 rom, but the problem remains.
Then I took a lot of time trying to understand the problem and I found out that it could have a EFS backup, but in fact I didn't have one.
The next thing was root the device (it is allready out of warranty) and use alternative tools. I have tried to rewrite the IMEI I have in the box with QPST , Qualcomm NV tools and did not work.
- QPST (2.7.4.11) works and shows the device but doesn't work the Backup QCN (To get QPST to show the device I needed to apply this with adb shell - http://forum.xda-developers.com/lg-...ct-g2-d800-t3175064/post62250384#post62250384, but it works and shows the phone in the ports list);
- RF NV manager returns and error "NvManager::getNvItemsFromPhone( const string comPort ) - QpstServer::sendSyncImpl - Bad response from phone (DM packet commands 19-24)";
- Qualcomm NV tools works and reads the device, then I write ESN, MEID and IMEI with good confirmation messages, but when I rebbot it remains with Null IMEI.
By this time I am in the search for more wise help and experience.
I also have "Unknown Baseband", and by reading some threads I thing the problem is that the phone has Null IMEI and the tools are unable to writr data to partitions. The only way is to write NV1 and NV2 by dd command into mmcblk0p10 and mmcblk0p11.
The phone works perfectly in all aspects (sensors, camera, wifi, screen) except for the phone signal "service disabled" with an X above the 4 signal bars. I gess it is not a hardware problem
I am struggling with this because it is a very nice device, and I need to bring it back to life before replacing the broken screen.
Any help?
thanks

aquelhas said:
Hello
I have an LG G2 D802 that was working perfectly but some days ago, after a crash with broken screen the phone suddenly show the message "Service Disabled" and the code *#06# returns IMEI Null.
By the time of the crash it was kit kat, and I made a factory reset that did not solve the problem. After that I use LG Flash tool to install the lollipop 5.0.2 rom, but the problem remains.
Then I took a lot of time trying to understand the problem and I found out that it could have a EFS backup, but in fact I didn't have one.
The next thing was root the device (it is allready out of warranty) and use alternative tools. I have tried to rewrite the IMEI I have in the box with QPST , Qualcomm NV tools and did not work.
- QPST (2.7.4.11) works and shows the device but doesn't work the Backup QCN (To get QPST to show the device I needed to apply this with adb shell - http://forum.xda-developers.com/lg-...ct-g2-d800-t3175064/post62250384#post62250384, but it works and shows the phone in the ports list);
- RF NV manager returns and error "NvManager::getNvItemsFromPhone( const string comPort ) - QpstServer::sendSyncImpl - Bad response from phone (DM packet commands 19-24)";
- Qualcomm NV tools works and reads the device, then I write ESN, MEID and IMEI with good confirmation messages, but when I rebbot it remains with Null IMEI.
By this time I am in the search for more wise help and experience.
I also have "Unknown Baseband", and by reading some threads I thing the problem is that the phone has Null IMEI and the tools are unable to writr data to partitions. The only way is to write NV1 and NV2 by dd command into mmcblk0p10 and mmcblk0p11.
The phone works perfectly in all aspects (sensors, camera, wifi, screen) except for the phone signal "service disabled" with an X above the 4 signal bars. I gess it is not a hardware problem
I am struggling with this because it is a very nice device, and I need to bring it back to life before replacing the broken screen.
Any help?
thanks
Click to expand...
Click to collapse
Today I tried this method with adb shell, to make sure Qualcomm NV tool writes IMEI to the phone...
setprop sys.usb.config diag,adb
ls -al /dev/block/platform/msm_sdcc.1/by-name
dd if=/dev/zero of=/dev/block/mmcblk0p10 (no space left on device)
dd if=/dev/zero of=/dev/block/mmcblk0p11 (no space left on device)
dd if=/dev/zero of=/dev/block/mmcblk0p16 (no space left on device)
Can anyone tell me why the "no space left on device" occurs?
Thanks

Hello!!!
First sorry for my poor english!
I think that you have a bad connection after crash!!!!
1. Remove the Backcover of your phone.
2. Remove the backplastic on upper part of phone using screw driver.
after remove back cover and upper plastic
3. Remove Battery Connector.
4.Remove all connectors except camera connector, Proximity sensor and face camera
After removing connectors
6.Reattach all connectors! Firmly press all the connectors
7.Reattach battery connector!!
Et voilÃ*!!! This is a way I do after losing IMEI and Baseband! IMEI: null and baseband should be implemented!!!
I had tried most method to fix but nothing happens,
Hope to help you!

aquelhas said:
Hello
I have an LG G2 D802 that was working perfectly but some days ago, after a crash with broken screen the phone suddenly show the message "Service Disabled" and the code *#06# returns IMEI Null.
By the time of the crash it was kit kat, and I made a factory reset that did not solve the problem. After that I use LG Flash tool to install the lollipop 5.0.2 rom, but the problem remains.
Then I took a lot of time trying to understand the problem and I found out that it could have a EFS backup, but in fact I didn't have one.
The next thing was root the device (it is allready out of warranty) and use alternative tools. I have tried to rewrite the IMEI I have in the box with QPST , Qualcomm NV tools and did not work.
- QPST (2.7.4.11) works and shows the device but doesn't work the Backup QCN (To get QPST to show the device I needed to apply this with adb shell - http://forum.xda-developers.com/lg-...ct-g2-d800-t3175064/post62250384#post62250384, but it works and shows the phone in the ports list);
- RF NV manager returns and error "NvManager::getNvItemsFromPhone( const string comPort ) - QpstServer::sendSyncImpl - Bad response from phone (DM packet commands 19-24)";
- Qualcomm NV tools works and reads the device, then I write ESN, MEID and IMEI with good confirmation messages, but when I rebbot it remains with Null IMEI.
By this time I am in the search for more wise help and experience.
I also have "Unknown Baseband", and by reading some threads I thing the problem is that the phone has Null IMEI and the tools are unable to writr data to partitions. The only way is to write NV1 and NV2 by dd command into mmcblk0p10 and mmcblk0p11.
The phone works perfectly in all aspects (sensors, camera, wifi, screen) except for the phone signal "service disabled" with an X above the 4 signal bars. I gess it is not a hardware problem
I am struggling with this because it is a very nice device, and I need to bring it back to life before replacing the broken screen.
Any help?
thanks
Click to expand...
Click to collapse
What should I do? If the same problems on RF NV manager got the same error. bad response from phone. How do i fix it?

Wow! What a coincidence!
I also have a LG G2 (D802) and the EXACTLY SAME problems!
Background:
It's been about a year since I am on Lineage OS 14.1.
Since 6 months ago, I started having issues with my antenna. Sometimes, antenna bar got empty and sometimes I couldn't get 3G signal on locations that I had before (and others had with no problem)
Fast forward 3 months ago and one day my phone couldn't detect sim card and IMEI was vanished. I had to restart it few times to make it come again.
And a month ago, I dropped my phone and screen shattered, Exactly Like you. After changing broken LCD with new one, and also a new battery, I couldn't get sim card detected anymore, No matter how much i restarted the phone.
IMEI was null and no baseband version was showed on about page. Also back of the phone (under camera started to get suspiciously hot.
I started applying pressure to different parts and sometimes phone hanged and restarted and maybe one in 20 times I could get antenna and sim card back.
Things I've done and their result:
Opening the phone numerous times and checked the connectors and unplugged/plugged them: nothing changed
Flashing back to stock (found lollipop kdz and flashed it via lg flashtool): nothing changed
Flashing Radio (Some images were available on XDA): nothing changed
Restoring ROM to an old backup I had (year ago): same as above
Trying to use QPST/NV Tools: They cant talk to modem.
Showing the phone to some repairmen: they cant talk to modem to set the IMEI either.
Still, sometimes by applying pressure to phone randomly, the IMEI comes back, which prevents me to cut hope and drop the phone into trash!
I would really love to know your result! were you able to fix it?

euphoria360 said:
Wow! What a coincidence!
I also have a LG G2 (D802) and the EXACTLY SAME problems!
Background:
my phone couldn't detect sim card and IMEI was vanished. I had to restart it few times to make it come again.
And a month ago, I dropped my phone and screen shattered, Exactly Like you. After changing broken LCD with new one, and also a new battery, I couldn't get sim card detected anymore, No matter how much i restarted the phone.
IMEI was null and no baseband version was showed on about page. Also back of the phone (under camera started to get suspiciously hot.
I started applying pressure to different parts and sometimes phone hanged and restarted and maybe one in 20 times I could get antenna and sim card back ...
Click to expand...
Click to collapse
How to Fix LG G2 no IMEI and not detecting SIM Card!
After I posted this reply here, I found a solution on some other topic about how to fix LG G2 WiFi issue. He opened the phone, and applied constant pressure (by putting a tape between WiFi chip and Metal Cover).
And I thought maybe my problem is similar too. So, this is the things I've done:
Download the Service Manual for your phone model. you can find it on Internet. Here is the one for LG G2
Look at the Service manual and find the chipsets related to IMEI/Service Issue. Usually they classify board components based on their common issues. For example, in G2 service manual, in pages 38 and 263, you can see this info.
For LG G2, The chips/IC's related to IMEI and Service were: U2003 (Bypass Booster), U2002 (WTR1605L), FL1014 (B3 DPX), U1101 (SP4T B7), FL1015 (B2/B3 Filter), FL1010 (DPX B20), U1005, U1000, U1001, U2002.
Most of these parts are under a metal shield which can be easily unmounted and mounted back on.
Make a thick piece of Tape and put it between the chips and the metal cover. The goal is to apply pressure to them to stick to the board.
Put the metal cover back on and close assemble the board. Done!
In my case, it worked, although after lots of repair men simply rejected my phone, I fixed it with just a little tape. Now, the IMEI is back, SIM Card is detected the moment phone is on, and I guess the phone consumes less power, since it doesn't get hot anymore.
Why this works? Well when you use your phone for a long time and it undergoes a of of heat/cooling cycle, the pins of some of these chips that tend to get hot, become a bit loose and get disconnected from the board. by doing above instructions you simply push them back.

No service, No IMEI and No clue

Hi,
My friend has bought a SGS7 because his SGS4 faced a problem, so he gave to me to fix it
The problem is as follows:
The phone sees the sim after maybe 5-10 minutes AFTER booting up and then 5-10 min after that it vibrates twice and than reboots its self. When the phone boots up and i try to view the imei by *#06# there is no response however a while after that when the sim is recognised the imei box pops up. Even without the sim the exact same things happen
#*The top part of the screen is gone slightly pink I think thats because its due to overheating as the phone is hot when for example is charging and not being used or when the phone is used to play spotify with the screen turned off dont know if this will help anyone the casue of the modem disfunctioning but the screen is pinkish where the processor and the sim is so...*#
Now i have tryed some troubleshooting withut success i have done as follows:
I've changed the sim tray which didnt help at all
I put tape on the sim/sdcard conncetor to add more pesssure (worked for other) without success
Tried to downgrade to 4.4.2 to change modem as there is no mode for the lolipop version of the stock rom
And lastly i have applyed the 4.4.2 modem to 5.0.1 that did nothing to the system
Please help me i have searched trough google and found out that this only happens when downgrading for lolipop to kitkat but he has never done anything to the phone no root not even a screen repair (where im based there are may scamers who replase the screen and than say the for the screen to work that had to modify the system thanks to that they charge more for the repair)
Please help, anyhelp is useful
cheers

Anyone?
the_ziom said:
Hi,
My friend has bought a SGS7 because his SGS4 faced a problem, so he gave to me to fix it
The problem is as follows:
The phone sees the sim after maybe 5-10 minutes AFTER booting up and then 5-10 min after that it vibrates twice and than reboots its self. When the phone boots up and i try to view the imei by *#06# there is no response however a while after that when the sim is recognised the imei box pops up. Even without the sim the exact same things happen
#*The top part of the screen is gone slightly pink I think thats because its due to overheating as the phone is hot when for example is charging and not being used or when the phone is used to play spotify with the screen turned off dont know if this will help anyone the casue of the modem disfunctioning but the screen is pinkish where the processor and the sim is so...*#
Now i have tryed some troubleshooting withut success i have done as follows:
I've changed the sim tray which didnt help at all
I put tape on the sim/sdcard conncetor to add more pesssure (worked for other) without success
Tried to downgrade to 4.4.2 to change modem as there is no mode for the lolipop version of the stock rom
And lastly i have applyed the 4.4.2 modem to 5.0.1 that did nothing to the system
Please help me i have searched trough google and found out that this only happens when downgrading for lolipop to kitkat but he has never done anything to the phone no root not even a screen repair (where im based there are may scamers who replase the screen and than say the for the screen to work that had to modify the system thanks to that they charge more for the repair)
Please help, anyhelp is useful
cheers
Click to expand...
Click to collapse

I'm having the same issue.
Fresh wipe and install corrects the error but once the battery goes flat I lose all connection except WiFi.
Non of the *# codes seem to work either.
Any help would be appreciated.
Thanks