• 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

micallan_17

Well-Known Member
as the title says, I was experimenting with some of the *983*------# codes and I tried this one *983*29873283# and said something about firmware update and to not touch the screen (things went sour after that) I got scared and took out the battery and when it rebooted, the screen wasn't working anymore, I no that code did something to the firmware and that's why the screen isn't responding no matter what I do. I do warn anybody that don't try this code cause it might brick your merit/avail. I came here to ask for help and see if anybody has had this issue and if there is a fix to it. I would greatly appreciate any help. thanks
 
I dont have it installed, but if its needed to get the phone's screen back to work I can install it, which version is needed?
 
micallan_17 said:
I dont have it installed, but if its needed to get the phone's screen back to work I can install it, which version is needed?
Click to expand...


TouchNav-1.3-ext3.zip

download this file, rename it to "update.zip" and copy to the root of your sdcard

merit.stock.rooted.rar

download this file, unrar it, put it on your sdcard in this file structure

sdcard
-folder named "clockworkmod"
--folder named "backup"
---folder named "merit.stock.rooted"
----all seven files from the rar

power off phone

hold volume up and menu keys, power up the phone while continuing to hold those two keys and wait for stock recovery to boot

install the new recovery by pressing the back key on the second option in the recovery menu (ie. wipe data:factory reset--no it will not wipe anything but it will install the new recovery update.zip)

then choose the reboot system now option, and immediately start holding volume up and menu keys afterward to reboot into the new recovery

once in the new recovery, choose "recovery tools", then choose "restore", then choose "merit.stock.rooted", then choose "yes" and let it restore

then reboot your phone

you will be completely stock and rooted

PROBLEM SOLVED
 
well it did bring the phone back to stock but still no response from the screen, am sure it has to do with the base firmware, which of course Tracfone has it locked, is only there was a way to get into FTM mode, that would work wonders
 
micallan_17 said:
well it did bring the phone back to stock but still no response from the screen, am sure it has to do with the base firmware, which of course Tracfone has it locked, is only there was a way to get into FTM mode, that would work wonders
Click to expand...


there is a way to get into FTM, but that won't fix your issue.

you have to have stock recovery

then you just hold volume down and power key until FTM loads

***edit***

this apparently doesn't work, but i know that i have gotten into FTM about three times, but i can't remember the button combo to make it load. stock recovery is mandatory for it though, as the images for FTM are in the ramdisk of the stock recovery.img
 
you shouldn't have been using the blade 2.1 rom update dialer codes in the first place.

but there's surely a way to get your phone working again.

maybe try installing one of my roms and then see if your screen is still not working

also try pushing the reset button for several seconds (take off back cover, little button by camera lens)

do those things, then get back to me

if they don't work, we'll try a few more things
 
hold the menu button first, then hold the power button, and hold both until the phone boots completely and you see "safe mode" in the bottom left corner--the phone will vibrate after the boot animation if done correctly

see if the touchscreen is working then
 
stayboogy said:
you shouldn't have been using the blade 2.1 rom update dialer codes in the first place.

but there's surely a way to get your phone working again.

maybe try installing one of my roms and then see if your screen is still not working

also try pushing the reset button for several seconds (take off back cover, little button by camera lens)

do those things, then get back to me

if they don't work, we'll try a few more things
Click to expand...
thanks for all the help, stayboogy, yup I learned my lesson alright, can you provide your links to your roms, and also instructions on how to get it to FTM mode, am willing to try anything it might be worth the try
 
stayboogy said:
hold the menu button first, then hold the power button, and hold both until the phone boots completely and you see "safe mode" in the bottom left corner--the phone will vibrate after the boot animation if done correctly

see if the touchscreen is working then
Click to expand...

do I need to be on the stock rom/stock recovery for this?
 
stayboogy said:
hold the menu button first, then hold the power button, and hold both until the phone boots completely and you see "safe mode" in the bottom left corner--the phone will vibrate after the boot animation if done correctly

see if the touchscreen is working then
Click to expand...

it does go into safe mode but nothing still
 
stayboogy said:
there is a way to get into FTM, but that won't fix your issue.

you have to have stock recovery

then you just hold volume down and power key until FTM loads

***edit***

this apparently doesn't work, but i know that i have gotten into FTM about three times, but i can't remember the button combo to make it load. stock recovery is mandatory for it though, as the images for FTM are in the ramdisk of the stock recovery.img
Click to expand...
yup I tried that too, and do you have a link to a stock recovery image file?
 
I headed over at Android Area 51's website and one of the Developers told me its bricked and the only way to fix it is by jtagging it, which he said is expensive.
 
micallan_17 said:
I headed over at Android Area 51's website and one of the Developers told me its bricked and the only way to fix it is by jtagging it, which he said is expensive.
Click to expand...

i don't really agree with this assessment at all,


**real, true bricks are not common with android systems. 80% of the time what people consider to be a brick is nothing more than a problem that beginners can't solve**

but i do have one more suggestion that may just fix your issue. but it will require some work. and sadly i won't have time to help for several days.

essentially i'll have you restore a nandroid of the att avail system, that i've made

then flash an official image.bin that includes a number of things that are not included in any nandroid or update that may just correct your problem.

but i'll have to get the image.bin uploaded first. and that won't be until tomorrow evening some time.

just be patient and don't do anything drastic, unless you purchased the extended warranty (and it's still active)--which if you did and it is, then you need to just return the phone for a new one following the instructions on the warranty card

EDIT--SEE NEXT POST
 
download this and restore using the same method as before

avail.unrooted.rar

download this, copy to your sdcard, and install it from the custom recovery using the "install a zip" option--this will give you the stock avail recovery, install this after restoring the above nandroid

Avail_stock_recovery_update.zip

download this, unzip it, and put the image.bin in this file structure on your sdcard

P020111107491720801969.zip

sdcard
-(folder named) image
--image.bin

go to settings, about phone, system updates, storage card updates, press ok, and follow the directions

once the phone reboots and the image installs, reboot the phone and see if all is working correctly again

if so,

you will need to install the custom recovery just like you did before, then restore the merit.stock.rooted nandroid just like before to get back to the standard ST/Net10 system image and operation
 
I will try your method and see what happens it after mid night here so I will it tomorrow and will report back, I myself wont be available for a week so take all the time you need, I appreciate all the help thanks
 
I don't think we are sub par at all. We are small but we work very hard to help people. We aren't sponsored so it it's money from our own pocket that keeps the site & IRC going. Everything is free to everyone.

I don't think the phone is beyond repair ether. I'm not sure who told him that or if it was even a dev.
 
kingmt said:
I don't think we are sub par at all. We are small but we work very hard to help people. We aren't sponsored so it it's money from our own pocket that keeps the site & IRC going. Everything is free to everyone.

I don't think the phone is beyond repair ether. I'm not sure who told him that or if it was even a dev.
Click to expand...
I did appreciate the help from the IRC channel over at website I visited, the guy that told that stuff went by user name Phydeux, am sure he is a known developer, weather the information he gave me was accurate or not I still appreciate it.
 
is there any other way to flash the image.bin on the phone since the screen isn't working I cannot get to the settings, about phone, system updates, storage card updates, I have a feeling we are close guys
 
micallan_17 said:
is there any other way to flash the image.bin on the phone since the screen isn't working I cannot get to the settings, about phone, system updates, storage card updates, I have a feeling we are close guys
Click to expand...

hey guys just a quick update, I was doing some research and found something interesting here and since it requires USB debugging I had to flash it with this rom PhydeuxROM-2.1.2-Unified-CWM6.zip since it seems the developer enabled USB debugging by default it was able to connect to my PC and using the above instructions I was able to control the screen from the PC a pic can be found here. the screenshot shows the actual screen I got when I entered the dialer code of which am talking about.
 
micallan_17 said:
hey guys just a quick update, I was doing some research and found something interesting here and since it requires USB debugging I had to flash it with this rom PhydeuxROM-2.1.2-Unified-CWM6.zip since it seems the developer enabled USB debugging by default it was able to connect to my PC and using the above instructions I was able to control the screen from the PC a pic can be found here. the screenshot shows the actual screen I got when I entered the dialer code of which am talking about.
Click to expand...

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.
 
You must log in or register to reply here.
Back
Top Bottom