• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Merit] ZTE Merit Touchscreen Bricked after *983*29873283# code

micallan_17 said:
hey can you do me another favor, go to this directory /proc/touchscreen and tell me what all you got in there
Click to expand...

Just one file:
RwDyqwT.png
 
redfield88 said:
USB debug is always enabled on my phone. As for dumping the phone, explain how you want me to do so. I have nandroid backups, but I don't think that's what you mean.
Click to expand...

it may seem a dump won't help will keep trying other things and then let you know k, thanks for the awesome help so far though :)
 
okay, i have a test solution

I DO NOT GUARANTEE THIS WILL WORK, NOR THAT IT WON'T DAMAGE YOUR DEVICE, NOR THAT IT WILL FIX YOUR ISSUE

but

it is worth a try at least

download these img files
misc.img
oem.img
persist.img

copy to your sdcard

on pc terminal

adb shell
su
dd if=/sdcard/persist.img of=/dev/mtd/mtd8
dd if=/sdcard/oem.img of=/dev/mtd/mtd7
dd if=/sdcard/misc.img of=/dev/mtd/mtd3
reboot

(copy and paste the commands so that you get them right)

and see what happens

post any errors or successes.
i'm not sure if these will flash like this or not. if they don't we'll try something else.

also, sorry, i've been so busy that i had forgot about this debacle
 
got these errors:

C:\Users\Allen>adb shell
adb server is out of date. killing...
* daemon started successfully *
# su
su
# dd if=/sdcard/persist.img of=/dev/mtd/mtd8
dd if=/sdcard/persist.img of=/dev/mtd/mtd8
/dev/mtd/mtd8: write error: Invalid argument
1+0 records in
0+0 records out
0 bytes transferred in 0.003 secs (0 bytes/sec)
# dd if=/sdcard/oem.img of=/dev/mtd/mtd7
dd if=/sdcard/oem.img of=/dev/mtd/mtd7
/dev/mtd/mtd7: write error: Invalid argument
1+0 records in
0+0 records out
0 bytes transferred in 0.003 secs (0 bytes/sec)
# dd if=/sdcard/misc.img of=/dev/mtd/mtd3
dd if=/sdcard/misc.img of=/dev/mtd/mtd3
/dev/mtd/mtd3: write error: Invalid argument
1+0 records in
0+0 records out
0 bytes transferred in 0.008 secs (0 bytes/sec)
#

I followed the steps as you asked
 
well, i'm out of ideas

you can try it this way

adb shell
su
flash_image oem /sdcard/oem.img
flash_image persist /sdcard/persist.img
flash_image misc /sdcard/misc.img

and see if that works, but i'm doubting it will. worth a shot i guess
 
did that and came out like this:

C:\Users\Allen>adb shell
# su
su
# flash_image oem /sdcard/oem.img
flash_image oem /sdcard/oem.img
# flash_image persist /sdcard/persist.img
flash_image persist /sdcard/persist.img
# flash_image misc /sdcard/misc.img
flash_image misc /sdcard/misc.img
#

from what I know it flashed I think

Edit: seems it didn't change anything, did a reboot and all but still the same, but thanks for the help stayboogy
 
micallan_17 said:
did that and came out like this:

C:\Users\Allen>adb shell
# su
su
# flash_image oem /sdcard/oem.img
flash_image oem /sdcard/oem.img
# flash_image persist /sdcard/persist.img
flash_image persist /sdcard/persist.img
# flash_image misc /sdcard/misc.img
flash_image misc /sdcard/misc.img
#

from what I know it flashed I think

Edit: seems it didn't change anything, did a reboot and all but still the same, but thanks for the help stayboogy
Click to expand...

doesn't appear that i've been much help lol


i'd say your device is truly "bricked" at this point

i don't know of anything else to do that could potentially fix it. of course i'm not expert either...
 
stayboogy said:
doesn't appear that i've been much help lol


i'd say your device is truly "bricked" at this point

i don't know of anything else to do that could potentially fix it. of course i'm not expert either...
Click to expand...

Not at all, believe me you've been great at helping me, and since the start of this I've learned so much from what I used to know before lol and I really appreciate all your help, its been great, no worries though am getting a new merit in like 3 weeks or so I wont make that same mistake lol, but will definitely flash it to an avail just like this one lol, some have suggested that it might be something with the kernel but who knows am no expert either lol.
 
micallan_17 said:
Not at all, believe me you've been great at helping me, and since the start of this I've learned so much from what I used to know before lol and I really appreciate all your help, its been great, no worries though am getting a new merit in like 3 weeks or so I wont make that same mistake lol, but will definitely flash it to an avail just like this one lol, some have suggested that it might be something with the kernel but who knows am no expert either lol.
Click to expand...

i highly doubt it's kernel related at all.

since i've built a few, i'm almost sure it has nothing to do with it.

the firmware file for your touchscreen got deleted in the update process is what i think. but such a file must be super hidden / untraceable / or loaded into memory via hidden module. that's all i can think of. that or it's a pseudo hardware level upgrade that is beyond my knowledge base.

i've messed with the system so much though and looked at all the files on it, and i can't think of anything that would be related to touchscreen functionality.

who knows, it may actually be something really simple that just no one knows how to fix

either way, i'm sorry for you loss.
 
micallan_17 said:
hey it seems your one has different info than mines, can you post a screen shoot of where you got this info?
Click to expand...

I just went to /proc/touchscreen and opened that up as a txt in ES file explorer.

I'd say its worth a shot changing yours to that, deleting the other file and reboot. But really have no clue. Seems logical, but it might just be a generated file and not matter.
 
can someone with a ZTE merit do a nandroid backup with ADB enabled? preferably with root access, that would be sweet. thanks
 
anyone with a rooted avail/merit can please do me a favor, am still investigating the issue, so i need for someone to check f there is a file named config.gz found in this directory /proc/config.gz, mines have it bu for what is this folder for?

**EDIT**
i manged to open the file in the config.gz file, i saved the info as text on my dropbox here am trying to see what i get but i prefer someone with more knowledge of this to be able to checl it out and see if we get any usefull info, its worth a shot i say.

**EDIT2**

more info probably useless lol but here it goes:

C:\Users\April>adb shell
# ls -l /dev/input
ls -l /dev/input
crw-rw---- root input 13, 69 1980-01-05 18:00 event5
crw-rw---- root input 13, 68 1980-01-05 18:00 event4
crw-rw---- root input 13, 67 1980-01-05 18:00 event3
crw-rw---- root input 13, 66 1980-01-05 18:00 event2
crw-rw---- root input 13, 65 1980-01-05 18:00 event1
crw-rw---- root input 13, 64 1980-01-05 18:00 event0
#

also # cat /dev/input/event0 shows no input or what so ever
 
That config file in the gz is autogenerated too it seems.

Don't know if it will help, but do you want a copy of mine?
 
I mentioned this to micallan yesterday, but the proc/config.gz is a copy of the kernel configuration. Awesome for us devs, useless for debugging (aside from telling you the equipped hardware).
 
Yeah, I remember am just trying all, I can to get the screen fixed and anything is worth a shot, am starting to think that it may be the digitizer is busted lol, everything seems to work just fine, I was doing some logging last night and it seems it detect the touchesbut it just wont respond, so am not sure what the problem can be
 
You must log in or register to reply here.
Back
Top Bottom