[Sony Xperia S, Acro S, Ion] testing567:
Help. Screen display is blank, but it's still working underneth.

I'm having a major problem with my device. It's a cheep Chineese tablet (NextBook Next8P12 with an AM Logic M3 chip). I attempted to root using this script on my

Linux pc

. I used the RunMe.sh included. The first time I ran it I had permission issues on my pc trying to run the ADB binary included in the folder, so I opened the script and replaced all instances of "./stuff/adb" with "adb" so it would use the instance of ADB i already have installed on my pc rather than the included one since I would rather not run the script with "sudo". That problem was solved easialy. At this point, the script would run and connect to my tablet correctly.

All is good to this point. This is where my problems begin. Now that I have the script working as intended, I used the normal rooting method in the menu options of the script. Everything seems to be going as expected. Then I get the restrore screen on the device and I click to procede as instructed. The device reboots and I see the splash screen but then the screen goes blank but the backlight is still luminated. I eventually figure out that it actually booted normally and the screen is just not displaying anything. I swiped my finger accross the blank screen as if the lock screen was displayed, and I hear the unlock sound effect click. I also connedted to adb shell just to see if I had root or busybox and I had neither. I looked back at the output of the script on my pc's console and I see:

Successful, going to reboot your device in 10 seconds!

connect: Invalid argument

and I remember that when I ran the script, the device rebooted imediatly after I clicked ok for restore on my tablet. I looked at the script and found the problem. It uses the command "ping -n 10" to cause a delay of 10 seconds before rebooting. "ping -n 10" is the

WINDOWS

command to ping 10 times. The Linux command to ping 10 times is "ping -c 10" Baiscly what has happened here is the script forciably rebooted my device the instant I pressed proced for the restore because the Linux/Unix script used a WINDOWS command to issue a delay of 10 seconds!. I am wondering if this is what damaged my system.

I made the appropriate corrections to the script and tried it again. After some fumbling around with the blank screen, I managed to find the on screen button to procede with the restore. This time after rebooting, the screen was still blank after the spash screen but busybox was installed sucessfully, but I don't have root or the su binary. I don't really understand how it happened that way.

Edit: I was wrong about busybox. It seems that this device already had busybox preinstalled.

Is there anything I can do to make it funcional again? I'm assuming it happened when the script erroneously rebooted the device during the restore command. Is their anything else that happens in this script that could posibly have done damage to my system? The phone runs and I have access to ADB, but the screen displays blank after the splash screen. Flashing the factory firmware is not an option because the Chinese manufacture of this device does not make it available to download. In fact, the reason I was rooting it was so I could use "dd" to make a dump of the stock firmware so I could send it to someone who was going to edit it to include the marketplace and superuser.

UPDATE:

It is working again. It turns out that the delay issue was not the cause of my problems. (but the script probably still should be updated) It was restoring the fake backup that caused it. I completly accidentally discovered that runing the following command fixed it:

adb shell "echo 'ro.sys.atvc_allow_all_adb=1' > /data/local.prop"

Also, I can confirm that my device with Android version 4.04 and a software build date of 9/17/12 is not vounerable to this exploit.