• 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

if you were able to control the screen that way, then i'll make a nandroid of the att avail system with debugging active and you can proceed with my method as it will not work with that rom because the system won't pass verification when the image.bin tries to install.

i'll post a link in a bit.

then you can proceed.

that was exactly what I was thinking, thanks for all the help, and yes I tried your method like that and it did fail verification, but I hope we can fix it with the debugging enabled nandroid.
 
that was exactly what I was thinking, thanks for all the help, and yes I tried your method like that and it did fail verification, but I hope we can fix it with the debugging enabled nandroid.

att.avail.rooted.usbdebug.zip

download this and restore it using the recovery i gave you before

then follow the directions i gave you to flash the image.bin using the screencast work-around you mentioned

let me know the results

and no problem :D, i just hope i can get you squared away and back to a properly working device
 
will sure do, am now downloading now, my internet isn't the fastest but it should download in 30 min or so, will get back to you, and I have my fingers crossed :)
 
Android is easy my friend, it doesn't take so much to learn and its really exciting to break things and fix them ;), I for one am so happy with it, but yet again everybody is entitled to their own opinions and I respect that
 
Android is easy my friend, it doesn't take so much to learn and its really exciting to break things and fix them ;), I for one am so happy with it, but yet again everybody is entitled to their own opinions and I respect that

so, did you get fixed, or no???
 
so, did you get fixed, or no???
for some reason the verification still fails, I have it with the nandriod you just sent also it has the avail stock recovery, would you say if I use the merit stock recovery with make a difference? how about the stock kernels?
 
for some reason the verification still fails, I have it with the nandriod you just sent also it has the avail stock recovery, would you say if I use the merit stock recovery with make a difference? how about the stock kernels?


no, that image.bin is only for avail systems, merit recovery won't make a difference

and

you shouldn't have any custom kernels installed if you restored the avail nandroid i gave you


let me see if it passes verification on my end and i'll get back to you shortly
 
no, that image.bin is only for avail systems, merit recovery won't make a difference

and

you shouldn't have any custom kernels installed if you restored the avail nandroid i gave you


let me see if it passes verification on my end and i'll get back to you shortly
sure then, I only installed what you asked me to install, which are the stock recovery and the nandroid
 
well, back to the drawing board i guess

try this:

restore the avail usb debugging nandroid one more time

then

reboot the phone and use the screencast workaround again and enter this code

*987*123456#

see if that changes anything

if not, try this one

*983*673636#

if still nothing, enter this one

*983*2567336#

then try

*983*10#,

if still nothing changes or that last one doesn't work,

run touchpaint test with this one

*983*0# and actually touch the phone's screen and see if it works

and then if nothing still changes,

you need to reenter the original code that caused your problem, and let it FINISH COMPLETELY--REGARDLESS IF IT FAILS OR COMPLETES, LET IT FINISH--do not do a battery pull or anything, no matter how long it takes. if it takes more than a few hours, chances are it will never complete, but you must let it try to

beyond that i'm out of suggestions for now.

but more will follow as i think of them

(i honestly hate to revert back to dialer codes, but it may be necessary and it's definitely worth a try considering your situation can't get much worse lol)
 
well, back to the drawing board i guess

try this:

restore the avail usb debugging nandroid one more time

then

reboot the phone and use the screencast workaround again and enter this code

*987*123456#

see if that changes anything

if not, try this one

*983*673636#

if still nothing, enter this one

*983*2567336#

then try

*983*10#,

if still nothing changes or that last one doesn't work,

run touchpaint test with this one

*983*0# and actually touch the phone's screen and see if it works

and then if nothing still changes,

you need to reenter the original code that caused your problem, and let it FINISH COMPLETELY--REGARDLESS IF IT FAILS OR COMPLETES, LET IT FINISH--do not do a battery pull or anything, no matter how long it takes. if it takes more than a few hours, chances are it will never complete, but you must let it try to

beyond that i'm out of suggestions for now.

but more will follow as i think of them

(i honestly hate to revert back to dialer codes, but it may be necessary and it's definitely worth a try considering your situation can't get much worse lol)
yeah I guess so lol, will try the steps you just mentioned and will report back once am done, I really appreciate the patience and must certainly the help stayboogy :)
 
yeah I guess so lol, will try the steps you just mentioned and will report back once am done, I really appreciate the patience and must certainly the help stayboogy :)

no problem at all, glad i can help (hopefully lol).

i still say you are NOT "bricked"

it will just take some time to figure it out
 
am sure we will eventually lol, so non of the above codes did make any difference, I will try the original one that got me into this lol and then we shall see what happens
 
hey guys I managed to pull out a log from the phone when I enter the code *983*29873283#, am not sure if this helps but I hope it does you can download the file from here
 
D/ViewRoot( 231): Dispatching pointer MotionEvent{2b3d6ed0 action=2 x=290.0 y=337.0 pressure=1.0 size=1.0} to com.android.internal.policy.impl.KeyguardViewManager$KeyguardViewHost@2b18daa0
D/ViewRoot( 231): Dispatching pointer MotionEvent{2b3d6ed0 action=2 x=290.0 y=337.0 pressure=1.0 size=1.0} to com.android.internal.policy.impl.KeyguardViewManager$KeyguardViewHost@2b18daa0
D/ViewRoot( 231): Dispatching pointer MotionEvent{2b3b8738 action=2 x=291.0 y=337.0 pressure=1.0 size=1.0} to com.android.internal.policy.impl.KeyguardViewManager$KeyguardViewHost@2b18daa0
D/ViewRoot( 231): Dispatching pointer MotionEvent{2b3b8738 action=2 x=292.0 y=337.0 pressure=1.0 size=1.0} to com.android.internal.policy.impl.KeyguardViewManager$KeyguardViewHost@2b18daa0 D/ViewRoot( 231): Dispatching pointer MotionEvent{2b3b8738 action=2 x=291.0 y=337.0 pressure=1.0 size=1.0} to com.android.internal.policy.impl.KeyguardViewManager$KeyguardViewHost@2b18daa0 D/ViewRoot( 231): Dispatching pointer MotionEvent{2b3b8738 action=2 x=292.0 y=337.0 pressure=1.0 size=1.0} to com.android.internal.policy.impl.KeyguardViewManager$KeyguardViewHost@2b18daa0

This stuff comes up when you tap on the screen. its like registering your touches.

I get those if I just tap on a blank spot on the screen. So it would seem like it knows your touching it, just wont respond.
 
Did someone manage to check out the log posted?

im checking it out now.

sorry, im super busy--full time job, full time student, no time to play lol

but i'm taking a look at. are you sure this a log of when you performed the initial action though and not of all the recent activity we've been through???

where did you get the log from? this will tell the answer to the above question...
 
Does it make a difference that the touchscreen.apk app is not install on the phone? I've reading that it seems to be linked with the *983*29873283# code. Also it seems to be available to all stock ZTE roms.
 
im checking it out now.

sorry, im super busy--full time job, full time student, no time to play lol

but i'm taking a look at. are you sure this a log of when you performed the initial action though and not of all the recent activity we've been through???

where did you get the log from? this will tell the answer to the above question...

The log was taken out through an adb command while the phone was connected to the computer in debug mode..

lol.. I understand the busy life.. we all are..
 
Does it make a difference that the touchscreen.apk app is not install on the phone? I've reading that it seems to be linked with the *983*29873283# code. Also it seems to be available to all stock ZTE roms.

< /br>
Nothing like that on Net10 merits, but if its on your stock or maybe even a roamer/avail it might be worth a shot pushing it on your phone.
 
Does it make a difference that the touchscreen.apk app is not install on the phone? I've reading that it seems to be linked with the *983*29873283# code. Also it seems to be available to all stock ZTE roms.

no such apk on any stock rom as far as the merit/avail goes

i have no idea where you are getting this bogus information...

anyway, that log has nothing of interest to me. sorry.

not sure what can be done about your phone at this point honestly.

it may have something to do with the OEM partition, which is mtd8. or the PERSIST partition. not really sure at this point. i'll pm you something in a day or so though
 
no such apk on any stock rom as far as the merit/avail goes

i have no idea where you are getting this bogus information...

anyway, that log has nothing of interest to me. sorry.

not sure what can be done about your phone at this point honestly.

it may have something to do with the OEM partition, which is mtd8. or the PERSIST partition. not really sure at this point. i'll pm you something in a day or so though

Thank you for the reply.. will be waiting on that message so we can check what other options are available..
 
I don't mean to be mean with anyone here guys but please lets stay on focus, I respect each and everyone's opinion here and at Area51 and to me they are both great sites. thanks
 
Probably should find someone that knows DD. I've used out but not much. I would think you could clone from one & DD that file into the other.
 
Back
Top Bottom