yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] SteakFrite:
Where I can find an image file of my Rom ?

This device don't have many popularity on google, and he have no constructor website... Where can I find a ROM or Custom Rom ?

For information, I've one another tablet (Exactely same device) arround of me.. Can I extract the ROM or a backup that could me restore the Android OS ? I don't want do stupid things with the other tablet also like I do this time...

(I want to precise... On my SdCard, a folder named "nandroid" has apparead , he content kernel file, system .img file, cache .img file, etc etc.., if you have any suggest on what can I do with it )
[Android Q&A, Help & Troubleshooting] S0AndS0:
I'll be seeing what I can dig up in the next day or so. Have you any links to shair; such as the guide(s) you've used?

You could try it, though I wouldn't as internal hardware can differ inside identical devices, you could end up 'super' bricking your device which I don't think is a real term it just sounds less scary than 'muten' bricking. The phonomonon can be observed when someone flashes an epic 4g touch rom on to an epic 4g and things are never the same. Not saying that's the case just my perinoa speeking up here.

Actually I think there are guides floting around on how to make and scrub your own custom rom, maybe you could do a full copy of the working device though the usb debug bridge, scrub the user data and dependencies from the copy and push it to the not-yet working device... or you could blase the path allready well troden.

now when you're going to your sd card are you talking removable sd or internal?

Some devices don't have an external or its inaccessible,

other devices make it confusing by also having a partition on the internall memory labled sdcard which looks a lot like the sd card that can be un mounted and re mounted (I believe it to be confusing because the sdcard is also lables sdcard),

And yet others are really easy to spot because its the only thing labled and removeable as an sdcard

Any who if your talking about viewing your sdcard with prisice then likely what your viewing is the old contents of the card (what ever you had on it before this learning experieance snuck up on you) and I would treat it like pizza from last night's party. Meaning that the backed up apps could be used and there could very well be a good backup in there if you made one in the before time, but I wouldn't force my device to choke down leftovers when I could start anew.

You're Welcome; knew you weren't out of options.

Make sure to reroot from the start of what ever guide you used (as a gard against myself and the decisions I make I always keep my costom recovery flash zip for all my devices in the root of my sdcard and labled as update.zip or whatever the manufacture's recovery software by defaults to looking for. That way I can always reinstall if the device still turns on.) as you'll likely want to flash and mod with furver, I know I always do, keep a clear head and it should all work out.

Sent from either my SPH-D700 or myTouch3Gs using XDA app

"it never hurts to help"
[Android Q&A, Help & Troubleshooting] SteakFrite:
... :)

It's a external sd card... And the file and folder are lost.

Exist an universal Custom ROM Android 4.2 ? I didn't found any official rom for this tablet...
[Android Q&A, Help & Troubleshooting] S0AndS0:
Yeah just spent the last hour or so looking for asd mid 162 tablet in google, tried a few modifide search quaries, and such to no avail. Saw your question on a few other boards too. I've a feeling that you've run into the same problem with low popularity and lack of documentation. If you got any other discripters I can use for searching I'll be back on the case after work today :)

Sent from either my SPH-D700 or myTouch3Gs using XDA app

"it never hurts to help"
[Android Q&A, Help & Troubleshooting] SteakFrite:
On recovery screen, is marked "SDK : MID-A13-Android4.2-V1.0-20130121"...

This tablet is the 9' inch model of ASD Digital 142...
[Android Q&A, Help & Troubleshooting] S0AndS0:
Looks like that's the rom, could try flashing it again, just google the 'a13 9 inch tablet' and you'll find info on allwinner.

Happen to know what the ASD stands for? All I'm getting is autism results. (Which putting the word autism in this thread and adding '[minus sine]autism' might help)

Sent from either my SPH-D700 or myTouch3Gs
[Android Q&A, Help & Troubleshooting] SteakFrite:
I haven't understand...

I don't understand what you say... :/

Can you use easiest word or terms ? (If possible)
[Android Q&A, Help & Troubleshooting] S0AndS0:
Sorry about that.

The first part of last post was discribing a search quary I used to find info on the rom you may be using. Looks like a cross platform compatible rom on the face of it but I'm still looking into it.

The second part of last post was stating that when I search for your devices' model 'asd digital' I'm getting results for human medical problems and not hardware related information. So I put the main word that was triggering that into this thread so that I can then search 'asd digital -autizem' and cut those results automaticly from the google search results.

Still working on this with you, just have split atention with trying to finish my first guide for android/linux dulebooting (unrelated to the issuess that curently plage you but still may be worth a look at when you've a system up and running again.)

At this point doing a restore from a working device's backup like you where saying might be the best bet on reviving the simi-bricked device, but I'll have to do some more reading before I really feel comfortible sugesting that you go though all that.

Now that you where able to boot a recovery screen; have you tried anything to get it back up and running? Such as restoring from a backup created after rooting the first time around?

Sent from either my SPH-D700 or myTouch3Gs using XDA app

"it never hurts to help"

link to guide for Debian Kit I'm working on for you.

https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=sharing
[Android Q&A, Help & Troubleshooting] SteakFrite:
So...

Thank's you, I understand the principal in your post but not two or three word... Also, I've tried to make a nand backup... ABD Tools Backup/Restore/Sideload run in recovery mode... The problem is that, when I try to make a nand backup from the other tablet, (without CWM because he can't be installed) I follow many tutorial on different blog or site but I find same probleme all time, a folder in "/proc/" is not found !!

Have you got one method (simple or powerful) to make a nand backup of the other tablet for restor in my tablet ? I've found in google same method on different site (using romdump file) or use CWM recovery (He run on my tablet while he planned for this ?)

[I hope I get to express myself well, I don't use any translation engine...]
[Android Q&A, Help & Troubleshooting] S0AndS0:
You're welcome. I can be hard to understand even to those that consider themselves fluent ;)

On the plus side found you some info on backups without root. Looks like ADB (Android Debug Bridge) will be the best bet.

This link will take you to a good guide on ADB comands

http://developer.android.com/tools/help/adb.html

Look for push and pull commands, they should allow you to copy/paste things regardless of location.

This link will take you though the steps of back up and restore using ADB

http://www.howtogeek.com/125375/how...kup-without-rooting-or-unlocking-your-device/

Looks fairly cut and dry and comes with pictures.

And this link had some content and discussion that might help

http://www.howtogeek.com/125375/how...kup-without-rooting-or-unlocking-your-device/

Hmm the /proc/ issues.... oh now that is cool, google searched it up and learned me something new. No wonder your device has been freaking out. Looks like the proc folder acts as a trainslator (sort'a) between android and the kernel.

Reading up on building kernels and android from ADB here:

http://elinux.org/Android_on_OMAP

Looks to be a fairly easy process, just a lot of typing and duble checking compatibility. But time consuming, some of the things I'm running across is a bit disheartening on how much time it could take to transfer data if not careful about the commands.

So, simple, eh? Don't think so but it looks as though using ADB command:

adb backup -apk -shared -all -f C:\Users\NAME\backup.ab

Might just get you a backup off the working device.

And using:

adb restore C:\Users\NAME\backup.ab

Might just restore it to the non-working device.

Could try pulling the proc file structure from the working device and pushing it on to the non-working one too (mean to say, use the pull comand with ADB to pull the missing folders or directories from the working device and then the push command to the none working device... just don't get mixed up) its like a really fancy copy/past. Though that could cause bad behavior with the proc thinking that you have something you don't anymore because its not on the original device.

Ok back to reading and stuff for a bit. Check that stuff out and maybe post where your getting your info from. I've a feeling we may be close to a solution.

Sent from either my SPH-D700 or myTouch3Gs
[Android Q&A, Help & Troubleshooting] SteakFrite:
Help ?

What I have to do to confirm restore operation ?

It's the recovery stock, I've not option "Backup Or Restore" , I have " Reboot system now", "apply update from ADB", "wipe data/factory reset" , "apply update from external storage", "apply update from cache"... Maybe hidden option or button combo for confirm restore operation , or I can install a "universal" custom recovery ? Or I can made a nandbackup too apply an "update.zip" [Without root] (Exist an software PC to make nandbackup via adb ? ) ?

(On the worked tablet, I can't make nandbackup, I don't have succeeded to root, many application I've tried, method or software, but neither have worked)
[Android Q&A, Help & Troubleshooting] S0AndS0:
ADB shouldn't require root... just enabling the connection on the device or booting it into the correct screen or interrupting the boot process at the right time by plugging it in nearly after boot but before main system loads.

So I've done a lot of digging around and it looks like part of a the solution can be now described :

on the working device, after installing ADB and it's dependencies, you'll want to get into the device settings (menu, settings, development, and enable USB debugging), then plug it into your computer and start ADB on the computer.

in ADB type:

adb shell

su

cat proc/mtd

dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img bs=4096

the commands may need to be adjusted for this task, 'su', may give you errors as you don't have root on the working device but it will likely work without it as ADB is fancy like that.

the 'cat' command should list out what is in the directory that you specify, such as the proc file or folder system that is missing from the none working device.

I think the 'dd' part duplicates a directory to another location. WARNING don't do the entire file structure or try to make a full backup img with this, seen a bunch of things sating that if you try to restore a full system and not just a folder here and there that the device will crash.

Replace the '/dev/mtd/mtd1' part to the path of the file structure that you are trying to backup, such as '/proc/' to maybe get a full backup of everything in that.

Replace the '/sdcard/recovery.img' part to a folder on your computer, such as '/C/dev/backup/proc.img'

not sure what the 'bs=4096' is for link of source(not on XDA)

other source of info(on XDA) that I be using at this moment take a look at the note near the bottom of the first post about passwords and such.

now that might just get you a backup from your stock device that still works, next is getting ADB to connect to your un-working device.

so you can try to boot the non working device into recovery (volume up or down and power) and plugging it into your computer and hopping for the best, not sure, still looking round for a way to ADB into a simi-bricked device. However, if you can get ADB to recognize wile booting, which from what I've been reading is possible for most devices.

then check this thread(on XDA) out, check out chapter 2, author is using of course a different device from yours so modification of examples may need to be done before you can successfully tell ADB what you want it to do.

I've also found some info on manually building a Kernel(on XDA) which might be one route that you could try, only difficulty is so far I've yet to run across the manufacture web site for your specific device so contacting them for a stock recovery img seems to be a long shot.
[Android Q&A, Help & Troubleshooting] S0AndS0:
Back again to drop some more sources to dig though.

Nead derections for fastboot?

Ok next link is a good one. Talks about recovering tablets with adb by fully repartitioning and reflashing. Think its the one. You just need an example of a working device with the same specs (thankfully you have that) put it in fastboot mode, connect to adb, run the 'view' commands from the link, take detailed notes (maybe post screen caps or text dumps of the results so that other users of your device can be educated without cost to themselves too), then make some full backups of working device. After that you'll likely be able to connect the nonworking device and follow along time though most of the guide with modifications to files and file paths (because your system is different) and using your notes or screen captures or text dumps of your working device, you should be able to breath new life into it.

Hope it goes alright and that you document some of it here for the comunity and stuff.

At this point I'm going to need more info. Links to where you've found info, pictures of your device or notes about all the numbers that might be a modle number or manufacture name or screan shots of what your brocken device looks like when it boots and the diferent screens you can get it into. Esentualy to help further I'm going to have to get to know your device in a vertual sence.

Hit me up if you want more links of unbricking info.

Sent from either my SPH-D700 or myTouch3Gs using XDA app

"it never hurts to help"

link to guide for Debian Kit I'm working on for you.

https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=sharing
[Android Q&A, Help & Troubleshooting] SteakFrite:
I've got using Uberizer to make an .img file and autoUpdateCreator for make an update.zip file... The problem now is the tablet reboot 30 seconds after the "adb sideload" command, or if I copy the update.zip file, the screen stay to "-- Install sdcard..."...

I will take photo and screenshot of the tablet

For know, the tablet is a A13F9 device, softwinners, on Jellybean 4.2, and that all I know...
[Android Q&A, Help & Troubleshooting] SteakFrite:
I want to try flashing in download mode with Odin, but... I can't boot in download mode... I've tried many combo button, Press buttons and plug USB cable... Nothing...

One method to boot in download mode ? (It's don't work with "adb reboot download" command, on my Acer Android Device too)

I can't send photos today, I'm not at home and I use 3G connection on my Portable computer..
[Android Q&A, Help & Troubleshooting] SteakFrite:
Finally, The photo it's here... :)

The dead tablet : http://netwab.no-ip.org/tools/file_hosting/file/39337-IMG-20130420-222258.jpg

Splash screen : http://netwab.no-ip.org/tools/file_hosting/file/4624c-IMG-20130420-222202.jpg

Kernel Panic : http://netwab.no-ip.org/tools/file_hosting/file/9b0d8-IMG-20130420-222225.jpg

if you have need some information, I'm here
[Android Q&A, Help & Troubleshooting] SteakFrite:
I studying your link about debian kit.. It's interresant and I will try to realise this... If you have new or suggest for me, thank's yoou
[Android Q&A, Help & Troubleshooting] SteakFrite:
Up ?
[Android Q&A, Help & Troubleshooting] S0AndS0:
Excellent I believe with that info I can correctly look up info on it. Could use screen shots of any other modes you've been able to boot into.

http://www.maipad.net/update-softwares/update-tool.html

http://www.szstzl.com/productlist.asp?ID=Y3V2VU9TSU

Taken from this forum

http://www.techknow.me/forum/index.php?topic=4909.0

Been reading up on the devices that seem to match yours and it looks like aside from rare hardware problems, most people have used roms built for a range of devices but with "universal" or cross platform component to they're titles or description, just be warned that I've run across cases of people flashing a universal rom and losing touch screen support . Have you checked cyanogen? It's what I role with on all my devices currently. Still reading up on your device between working on the thread I put up and stuff so I'll be posting what I find as I find it :)

Sent from either my SPH-D700 or myTouch3Gs

Debian Kit Install guide for all

http://xdaforums.com/showthread.php?t=2240397

Or

https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=drive_web
[Android Q&A, Help & Troubleshooting] SteakFrite:
Greaaaat News !!

I've flashed the tablet with LiveSuite and A13 Uberoid firmware for a another tablet... He boot's and desktop appears but the screen touch don't work...

Actually, I try to restore the firmware of the same working tablet... I will let you know... :)
[Android Q&A, Help & Troubleshooting] S0AndS0:
Sweet. Now your in business.

Touch screen being lost is a common issue. Need to look for "touch drivers" for your device and instructions for installation and you maybe able to restore all functionality. In the mean time you can also try a Bluetooth mouse (like a commuter mouse with bluetooth connectivity instead of a wire) I've seen postings dealing with making a link with Android's Bluetooth, or you can try USB Host mode on your device with some wire splicing of old USB cables, both of which I've not tested but I read up on it as MHL is something I want to get working on my devices. There are remote desktop like apps on the Android market that will allow you some control though a computer and wifi network, and of course there's ADB.

I'm any case user input is a must and re flashing to a better supported ROM if you can't get drivers, but don't forget to make a back up

Sorry not been more helpful as of late, but very glad that you're getting it worked out.

Sent from either my SPH-D700 or myTouch3Gs

Debian Kit Install guide for all

http://xdaforums.com/showthread.php?t=2240397

Or

https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=drive_web
[Android Q&A, Help & Troubleshooting] SteakFrite:
Searching on google doesn't return great result... I've got the backup of the working tablet... Can I do "pull" of different files needed ? I'm so tired to work on this...
[Android Q&A, Help & Troubleshooting] S0AndS0:
Yeah I don't see any reason why you shoun't try it. If you get working like that, might be cool to see a download link once you remove any personal info so that others with your device can just grab and go from all the hard work you've put in.

I don't where those files are on you wooring device. But in a comand line you can usualy use "ls" to list things in the curent directory and "ls -l" for a detailed list. Hopefully its well labled somewhere in the android system. If not:

ADB does have a way to "run" or temperarly "push" files over to a fully turned on system (this is for app developers but will work good for this porpace) what you can do if you've got two cables and two USB plugs is mount the working device and use "dd" (I think) to duplicate directories or files over to your patialy working device, run the new software patches (because that's what I think their called elsswhere) in an emulated enviroment (which actualy uses your devices hardware as the emulated enviroment) test your device to see if the touch screen works after each atempt and when it works you'll want to do a real push of those files that made it work. I sugest ADB because; you can run this debuging process in such a way that it doesn't touch your working device in any negitive way, you can test each debug step without changing or lossing the work you've already done, and once you do find the offending lost files you can then aply them to the device and have it working.

Thanks for sticking with it. Once you've got it working make a backup and you should be good till something happens again but by that point you'll be able to fix it :)

Sent from either my SPH-D700 or myTouch3Gs using XDA app

"it never hurts to help"

link to guide for Debian Kit I'm working on for you.

https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=sharing

---------- Post added at 08:35 AM ---------- Previous post was at 08:08 AM ----------

Oh and you may be able to pull up a task manager (think it is called log cat) on your working device and then tap on the screen and look at the log for a record of your user input and the different system tasks that are listening for your interaction and the different system calls that trickle down because of your interaction. This might be able to help you to nerrow down what spicificly on your working device is controlling and responding to your touching and then with that list you should be able to trace them back to what directory their running from.

Sent from either my SPH-D700 or myTouch3Gs using XDA app

"it never hurts to help"

link to guide for Debian Kit I'm working on for you.

https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=sharing
[Android Q&A, Help & Troubleshooting] SteakFrite:
I go to try... If device doesn't boot after modification, I can reflash with LiveSuite.. It's just take one or two minutes only...

I've ever view Logcat log with Logcat Monitor program (In Uberizer program) and the problem is : "EGL : BAD_DISPLAY_DEVICE (3008)" when I push on lock button...
[Android Q&A, Help & Troubleshooting] S0AndS0:
Cool it's good that you got that part smoothed out.

By chance when you run log cat on your fully working device does it give you any indicator of what is activated or listening for your touches? If it does then you should be able to lock in on target as it where on the specific things that you're missing from the halfway fixed device. The other thing you might be able to dive down are forensic tools for comparing one directory to one that is supposed to be a copy, its a bit round about but there are some good linux tools that should be able to run a drive copy verification, it should then display where they are different (all the way down to the bit or bite in some cases) it might be harder though as you've a different rom structure to your half way recovered device and that could cause false positives on discrepancies. Just another thought.

Hey found one link that may also provide usefulness

http://xdaforums.com/showthread.php?t=2060017

COMPILE From Source For Any Phone On Linux Distros [BUILD ENVIRONMENT TO COMPILE]

Sent from either my SPH-D700 or myTouch3Gs

Debian Kit Install guide for all

http://xdaforums.com/showthread.php?t=2240397

Or

https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=drive_web