How do I flash back stock? v.SignatureMismatch,BootLoop,etc

[tobdaryl]

One more thing, is all of this for signature mismatch, or the no touch ones?

I'm slowly grasping this!

No but they are sometimes harder(much harder). We should divide them into groups and work with a group at a time. Trying to overlap them may result in hard bricking a unit when the situation is different and may require a different technique.
All of them will probably require adb and or fastboot.
With adb working we might be able to push the file you used earlier to your internal sdcard and get asus recovery to fix the unit by reinstalling the full stock firmware. Of course that would be the easiest outcome.

 

[kmad86]

Note 2: You need to think about getting adb and fastboot working properly.
adb can be accessed when powered on and just sitting there
and when booted into cwm or twrp
fastboot get into the bootloader (power and volume down) press volume down to choose the usb icon then volume up to select - this would be on the 4.0 and 4.1 bootloader - if you have the 4.2 bootloader there is no usb icon and the tablet if left will auto turn on fastboot (look in upper left for the message) (DO NOT USE WIPE DATA IN THE BOOTLOADER)
test if adb is working by typing
adb devices
test if fastboot is working by typing
fastboot devices[/COLOR]
each will return the unit serial number or all zeros when working

I'm sorry to do a piece at a time but there are so many options etc

Searching
go to general (example) without choosing a thread look in the upper right for search to the right of this there is a gear select that (advanced search) - in search by keyword type mismatch (example) - scroll to the bottom and click search.
This example searches all general threads and all posts within these threads.

Wow, this is fun and nerveracking at the same time! Ha.

Ok so I assume in Command I need to type something to actually get it linked to the tablet.

My android SDK Path is : C:\users\admin\desktop\tf300t stuff\adt bundle\sdk (if that helps)

Right now on Command Terminal I am looking at:
C:\users\admin>


15 years ago, I could navigate through command, anymore I am lost. I need a brush up. I think what I am needing to do is get it to point to that SDK path.Right?

 

[tobdaryl]

Wow, this is fun and nerveracking at the same time! Ha.

Ok so I assume in Command I need to type something to actually get it linked to the tablet.

My android SDK Path is : C:\users\admin\desktop\tf300t stuff\adt bundle\sdk (if that helps)

Right now on Command Terminal I am looking at:
C:\users\admin>


15 years ago, I could navigate through command, anymore I am lost. I need a brush up. I think what I am needing to do is get it to point to that SDK path.Right?

Command prompt admin will normally drop you in c:\Windows\system32.
cd \users\admin\desktop\tf300t stuff\adt bundle\sdk\platform-tools - this should work as long as you are on the proper drive and I'm reading your path correctly.
adb and fastboot are located in platform-tools - if platform-tools does not exist you missed the step where you run android.bat.
Don't worry I'm still trying to remember the / has to be \ in windows path.
I don't think it will but if this fails you may need to remove the spaces in your path (from the 8086 days).

 

[kmad86]

Command prompt admin will normally drop you in c:\Windows\system32.
cd \users\admin\desktop\tf300t stuff\adt bundle\sdk\platform-tools - this should work as long as you are on the proper drive and I'm reading your path correctly.
adb and fastboot are located in platform-tools - if platform-tools does not exist you missed the step where you run android.bat.
Don't worry I'm still trying to remember the / has to be \ in windows path.
I don't think it will but if this fails you may need to remove the spaces in your path (from the 8086 days).

I got that part finally, I don't know how and I wish I did but I just copied and pasted the path you gave me and it auto corrected it I guess.

Anyhow, I ran adb devices and it says

* daemon not running. starting it now on port 5037 *
*daemon started successfully *
list of devices attached
C40KCT038725 device


Then, I typed in fastboot device.. and it's booting into it fine. It gives me some options and commands to choose.


(I'm testing this all on the device that I put the SD card in, and it ended up fixing the touch the first time it installed it. I just figured it wouldn't hurt to test it all on a working unit while my signature mismatch problem is charging.)

 

[tobdaryl]

I got that part finally, I don't know how and I wish I did but I just copied and pasted the path you gave me and it auto corrected it I guess.

Anyhow, I ran adb devices and it says

* daemon not running. starting it now on port 5037 *
*daemon started successfully *
list of devices attached
0123456abcdef device


Then, I typed in fastboot device.. It didn't do anything.

(I'm testing this all on the device that I put the SD card in, and it ended up fixing the touch the first time it installed it. I just figured it wouldn't hurt to test it all on a working unit while my signature mismatch problem is charging.)

Good! Remove the serial number(safety).
For fastboot to work you need to get into the bootloader. I described the process earlier but if necessary I'll try again.
Check fastboot first and then we'll push your zip to your internal sdcard and give recovery(stock) a chance.
adb push EP201_768_SDUPDATE.zip /sdcard/EP201_768_SDUPDATE.zip
this assumes your zip is in the platform-tools directory with adb and fastboot.
from power off - boot into recovery - power and volume down when you get the menu volume up to select RCK.

 

[kmad86]

Good! Remove the serial number(safety).
For fastboot to work you need to get into the bootloader. I described the process earlier but if necessary I'll try again.
Check fastboot first and then we'll push your zip to your internal sdcard and give recovery(stock) a chance.
adb push EP201_768_SDUPDATE.zip /sdcard/EP201_768_SDUPDATE.zip
this assumes your zip is in the platform-tools directory with adb and fastboot.
from power off - boot into recovery - power and volume down when you get the menu volume up to select RCK.

Ok, so I got the signature mismatch tablet charged and turned it on while holding power and down. It booted and said it's "Push volume up" which I did. From there, the screen is now just blank but the backlight is glowing.

I got into command and ran fastboot device and it's hung on waiting for device.



If I boot it back on, it tells me "Signature Mismatch, Unrecoverable Bootloader error 00x00000" and then in a few seconds goes to a dark screen with the black backlight.

edit:

I took the SD card out and put it back in. It boots Signature Match. Then shuts off and back on and says the signatue mismatch, unrecoverable bootloader error

 

[tobdaryl]

Ok, so I got the signature mismatch tablet charged and turned it on while holding power and down. It booted and said it's "Push volume up" which I did. From there, the screen is now just blank but the backlight is glowing.

I got into command and ran fastboot device and it's hung on waiting for device.



If I boot it back on, it tells me "Signature Mismatch, Unrecoverable Bootloader 00x00000" and then in a few seconds goes to a dark screen with the black backlight.

That unit appears to have no recovery and a bootloader mismatch. It could have a JB(4.1) bootloader and JB(4.2)os or....

Fastboot is on the same menu but you press volume down to move through the choices until you are over the usb symbol and then volume up. Or if the bootloader is 4.2 there will not be a usb icon and you just wait ten seconds and see fastboot started in the upper left.

 

[kmad86]

That unit appears to have no recovery and a bootloader mismatch. It could have a JB(4.1) bootloader and JB(4.2)os or....

Fastboot is on the same menu but you press volume down to move through the choices until you are over the usb symbol and then volume up. Or if the bootloader is 4.2 there will not be a usb icon and you just wait ten seconds and see fastboot started in the upper left.

There isn't a USB icon thus making me think maybe it's 4.2. I assume I should go back now and download the .zip tailored to 4.2 and put it on a MicroSD and then hold power+down and run RDK.

 

[tobdaryl]

There isn't a USB icon thus making me think maybe it's 4.2. I assume I should go back now and download the .zip tailored to 4.2 and put it on a MicroSD and then hold power+down and run RDK.

Of course you can try. If we have a recovery it appears to not be functional(it should have reared it's ugly head when we chose RCK earlier). Go back to the bootloader menu and let it sit without touching any buttons, in ten seconds you should see entering fastboot in the upper left(if this is the 4.2 bootloader). We haven't discussed ICS and may not but that is another bootloader menu.

What happened to the other unit we were working with in the beginning? The one with stock recovery.
You should start to see why no one thing will fix them all.

 

[kmad86]

Of course you can try. If we have a recovery it appears to not be functional(it should have reared it's ugly head when we chose RCK earlier). Go back to the bootloader menu and let it sit without touching any buttons, in ten seconds you should see entering fastboot in the upper left(if this is the 4.2 bootloader). We haven't discussed ICS and may not but that is another bootloader menu.

What happened to the other unit we were working with in the beginning? The one with stock recovery.
You should start to see why no one thing will fix them all.

Two things.

One, when I hold power and volume down it prompts me with the two icons. I let it run 10 seconds after the icons pop up and it just resets. It doesn't go into a fastboot mode.

Second thing, I just noticed that my MicroSD card is labeled (for 4.2) TF300T_US_epaduser_10_6_1_8_Sdupdate.zip should this file be renamed to something else to recognize?


Although little, I feel like I am gaining some ground finally!

 

[tobdaryl]

Two things.

One, when I hold power and volume down it prompts me with the two icons. I let it run 10 seconds after the icons pop up and it just resets. It doesn't go into a fastboot mode.

Second thing, I just noticed that my MicroSD card is labeled (for 4.2) TF300T_US_epaduser_10_6_1_8_Sdupdate.zip should this file be renamed to something else to recognize?


Although little, I feel like I am gaining some ground finally!

One sounds like locked ICS. The ICS bootloader does not display the usb icon until unlocked.

Two you need to unzip that file once and your new zip will be named EP201_768_SDUPDATE.zip. If stock recovery is in place it should deny flashing if my info is correct. Why? The EP201_768_SDUPDATE.zip includes an assert in updater-script to deny installation except from JB 10.4.2.20. Another thing to consider here is the first JB (10.4.2.9) repartitioned the drive (mmcblk0) for the JB system and the following updates.

At the very least you are gaining knowledge which is a positive direction. Considering what you have on your plate everything you can learn is positive.

 

[kmad86]

One sounds like locked ICS. The ICS bootloader does not display the usb icon until unlocked.

Two you need to unzip that file once and your new zip will be named EP201_768_SDUPDATE.zip. If stock recovery is in place it should deny flashing if my info is correct. Why? The EP201_768_SDUPDATE.zip includes an assert in updater-script to deny installation except from JB 10.4.2.20. Another thing to consider here is the first JB (10.4.2.9) repartitioned the drive (mmcblk0) for the JB system and the following updates.

At the very least you are gaining knowledge which is a positive direction. Considering what you have on your plate everything you can learn is positive.

If it is 4.1, it wouldn't have just two icons, right?

I'm asking because If it is 4.2 I figure the 4.2 sdcard won't hurt to try.


So is my move now to get it to JB 10.4.2.20?

 

[tobdaryl]

If it is 4.1, it wouldn't have just two icons, right?

I'm asking because If it is 4.2 I figure the 4.2 sdcard won't hurt to try.


So is my move now to get it to JB 10.4.2.20?

JB(4.1) has four icons. Since this unit has the bootloader signature error it probably is a mix of ICS and JB or a mix of JB(4.1) and JB(4.2). Two icons makes me think of ICS.
You can try, as I said there is an assert that should stop the update if my guess is correct. I'm not guessing about the assert as I just verified as being correct. I'm guessing about ICS and JB being the mix.

 

[kmad86]

JB(4.1) has four icons. Since this unit has the bootloader signature error it probably is a mix of ICS and JB or a mix of JB(4.1) and JB(4.2). Two icons makes me think of ICS.
You can try, as I said there is an assert that should stop the update if my guess is correct. I'm not guessing about the assert as I just verified as being correct. I'm guessing about ICS and JB being the mix.

Yeah, nothing. Didnt work.

 

[tobdaryl]

Yeah, nothing. Didnt work.

I need to verify no fastboot on this one and blank screen when we tried to get into recovery (volume up on RCK).
If adb works try this command and see if we can enter recovery by another path.
adb reboot recovery

 

[kmad86]

I need to verify no fastboot on this one and blank screen when we tried to get into recovery (volume up on RCK).
If adb works try this command and see if we can enter recovery by another path.
adb reboot recovery

When I do that, I keep the sd card out, right?


Says : "error device not found"

 

[tobdaryl]

When I do that, I keep the sd card out, right?

I don't think it will matter but try with it in for fun. If you can get into recovery we'll use this path and push our file to the internal sdcard.

 

[kmad86]

I don't think it will matter but try with it in for fun. If you can get into recovery we'll use this path and push our file to the internal sdcard.

Says "Error: device not found"

However it now just sticks on the ASUS logo and loops to another ASUS logo and I don't see the Mismatched at the top in red anymore

 

[tobdaryl]

Says "Error: device not found"

However it now just sticks on the ASUS logo and loops to another ASUS logo and I don't see the Mismatched at the top in red anymore

This is not unusual for these tablets to change as we flog them.
We once again want to know about recovery, adb, and fastboot access. One or more of these probably changed as well and we need to know which.

 

[kmad86]

This is not unusual for these tablets to change as we flog them.
We once again want to know about recovery, adb, and fastboot access. One or more of these probably changed as well and we need to know which.

When I type in fastboot device, it just says "Waiting for device"

ADB shows a bunch of stuff. I'm trying to read through it all right now. It says 1.0.31 for ADB version. I don't know if that's the tablet or the computer?

I'm not sure what to type for recovery? Unless that's the same thing I typed above "adb reboot recovery"