Good day
I have a .bin backup from a mtk 6735 processor, screwed the phone up real hard, no longer is being recognized at all by the computer (the program crashed while I was writing the bin back onto the phone, it no longer displays anything and isn't recognized by windows anymore)
The program I used called the bin a backup. That's what it is, sure. But it ain't no scatter...
How do I access the system.img? I just need back these documents. I'll pay a reasonable amount for the solution here
To my knowledge a bin has literally no information in it to simply instruct someone as to its contents? I think I'm screwed here since the phone is in a completely unrecognizable state, I can't write the bin back to it or anything
Related
Hello, I have several questions about rooting and backing up my Android tablet but I'm not really sure where to begin.
My (current) goal is to back up the firmware that's currently on the tablet so that I can later restore to it in the event that something goes wrong. The only problem is I seem to have a newer version than the latest-offered version that was posted on the manufacturer's website, but the latest-offered version doesn't work. To make matters worse, the manufacturer's website is no longer online so there's no chance that the firmware I have will ever be uploaded. In other words, I need to root my tablet so that I can make a backup of the stock firmware to revert to if necessary.
The tablet in question is a Panimage Media Tablet R79RT2W5 that I picked up for $20. Before you tell me not to bother or that it's a piece of crap, don't worry; I'm VERY aware. The entire reason I bought this to begin with was BECAUSE it was a piece of crap. I was hoping that at the very least I could screw around with it and use it as a testbench to learn Android programming on with hardware I don't care about possibly bricking. (In other words, I wanted a cheap tablet to play around with so I wouldn't risk bricking my phone.)
I'll try to give you all the possible information I have on it. If you need any more information, pictures, screenshots, uploaded files, etc. I'll try to get what I can for you.
Panimage Media Tablet
Model Number R79RT2W5 (according to the physical sticker on back)
Model Number R79RTW5 (according to the 'About Device' page; note the lack of the 2 in the model number there.)
256MB of RAM
Firmware Version 1.6 (Donut, apparently?)
Kernel Version 2.6.29
Build Number WMT2.1.7_PD
2GB Internal Flash Memory (according to the box)
- Apparently it's a Gome Flytouch clone?
- It has a whole bunch of software made by WonderMedia Technlogies. (Which makes sense considering that it has a WMT-based processor.)
- It has "App Market" com.wonderappstore instead of Google Market. In other words, I basically have to sideload apks to get anything worth using.
Click to expand...
Click to collapse
Things to take note of:
- It has no USB port so I can't hook it directly to a computer (meaning regular ADB won't work), but it does take microSD cards.
- I can sideload applications, but they need to be able to work on 1.6, obviously.
- I have FTPServer installed so I can send files to/from my computer, but I can't access protected directories.
- I have run BOTH Universal Androot and z4root. Neither program rooted the tablet. z4root DID install SuperUser (which I'm assuming only worked because USB debugging was turned on), but SuperUser doesn't work.
- I'm willing to work with terminals or command prompts so long as I have someone able to walk me through the process.
Is rooting this thing a possibility?
Alternatively, the way that the firmware update process works is that you put a folder named "script.zip" on the root of the microSD card and then boot the tablet with the card inserted. The tablet will then proceed to automatically install the firmware on it.
Would it be possible to take advantage of this function to allow me to run a script that will back up the firmware to the microSD card before it boots that I would then later be able to restore onto the tablet as necessary?
I can upload a copy of the latest script.zip I have so that you can take a look at it if you'd like.
What do you mean by their isn't a USB port what do you use to charge.
Sent from my HTC Velocity 4G using Tapatalk 4 beta
WildfireDEV said:
What do you mean by their isn't a USB port what do you use to charge.
Click to expand...
Click to collapse
It has a generic electrical plug; one of the round ones with a single prong in the middle.
It doesn't charge through USB like most other phones/tablets, because there's no USB port on it.
you can possibly back up your phone's firmware even without a usb port...
using the stock recovery, you can flash a custom recovery like clockworkmod which gives you a back-up option... and you can also root it with that...
WisdomSky said:
you can possibly back up your phone's firmware even without a usb port...
using the stock recovery, you can flash a custom recovery like clockworkmod which gives you a back-up option... and you can also root it with that...
Click to expand...
Click to collapse
That's a bit of a problem... the tablet doesn't appear to have a stock recovery available.
I've tried as many button combinations upon boot as I can think of (Power + Vol. Down among many other things) and none of them boot into any sort of recovery mode.
I've even gone as far as trying to force my way in using the SysRq trick that someone got to work for the Ouya:
http://forum.xda-developers.com/showpost.php?p=42516267&postcount=6
...but unfortunately that doesn't work either. No mater what Alt + SysRq combination I use (out of the ones that actually work, that is), the tablet automatically restarts. Every time.
However, as I said in my OP, I think that there may be a small bit of hope.
Alternatively, the way that the firmware update process works is that you put a folder named "script.zip" on the root of the microSD card and then boot the tablet with the card inserted. The tablet will then proceed to automatically install the firmware on it.
Would it be possible to take advantage of this function to allow me to run a script that will back up the firmware to the microSD card before it boots that I would then later be able to restore onto the tablet as necessary?
I can upload a copy of the latest script.zip I have so that you can take a look at it if you'd like.
Click to expand...
Click to collapse
After a bit of messing around, I've found that the firmware update process looks for a file named "prepare.bin" and then loads it, which starts the automatic firmware update process.
While I'd rather try doing some sort of manual root on the tablet if possible, I'd be willing to try to make my own version of "prepare.bin" that will allow me to essentially hijack the firmware update process before it begins, which should essentially give me system-level control over the tablet.
...In theory, that is.
Do you think this would be a possibility?
I'd post pictures and screenshots and links and other information I've found, but I don't seem to have enough posts to do that yet...
edit- To be more direct, I'm willing to try to hijack the boot process to run my own code if possible, but I'd much rather do some sort of manual root or something if possible so I don't risk screwing up my tablet. As I said before, neither z4root nor Universal Androot work for my tablet, so I was wondering if there's some sort of manual exploit I can use to get in from within Android. If that's possible, I'd much rather take that approach as opposed to basically brute forcing my way into system-level access and risk bricking something.
This has been posted elsewhere on XDA however it was suggested that this would be a better location to post so here goes:
'Good day all,
I have the above tablet which has been bricked . (We sell these and a customer has returned a unit to claim warranty so I am not 100% sure what has occurred to make the device what it currently is.) Basically I have another identical unit and have created a backup image with MTK Droid Tools. However when I try to load this image with SP Flash Tools I get errors. These state that the image I have is not correct (as it is from an identical unit I can safely say this is not correct) to the device storage not being available. The second error is the one I believe may be the problem. Is there a way that the internal storage may have been compromised and if is is there a way the storage can be fixed?'
I have tried to study the posts relating to partition dumping but am simply not bright enough to figure it out. Is there a way I can make a 'ghost' image of the working tablets partition table and then tranfer that to the bricked unit?
Thanks in advance for the help and time.
Alternately is anyone able to confirm a partition backup and restore tool?
Short story. Bought a local cheap china tablet based on MTK6852 chipset with 8GB internal storage, running KitKat 4.4.2, but only 500MB available for apps. Being a complete android noob, but a savvy computer guy, started investigating and playing with link2sd, which did not work. Eventually found out I can simply edit EBR1 and EBR2 and that will increase internal storage to ~4G which would be great. Again, being an android noob, I installed droid tools for MKT, did a scatter backup and a whole system backup.
then, just when I was about to manually edit EBR files, I discovered this app: youtube video id: V9aFPNcwajw (sorry as I a new poster I am unable to post outer links) Being super happy about it and forgot to read comments I just went to run it. It failed. Later I discovered its only for MTK6577 devices and it most likely messed up my EBR.
Now I am stucked; I cen get into recovery mode, but factory reset does not work, leading into "mount /data error force format /data" error (my guess is because my EBR is messed up recovery cannot find /data folder?). SP flash tools worked and I have downloaded a couple of different EBR files, but none worked.
The biggest problem: my recovery seems to be incorrect, no idea why thou. All I see is: firmware.info mount.info, phone.info, scatter.txt file and a big "system" folder. Now to do a SP flash tools ready file I would have to select "prepare blocks for flash" in the MTK droid tools, but that requires "files.md5" file, which I dont have (again, no idea why not as I've done a complete backup from same droid tools, unless I forgot to thick something?)
Also the company that makes this tables, actually brands them, refuses to send me any files and wants me to bring in the tablet.
Is there anything else I can do on my own or its time for repair service? My guess is I cant do much without EBR files, but have no idea where to find the correct ones as this is a small country based company and I have yet not found under what other brands it is sold.
Is it possible to restore an android phone back to its original factory state if all of its internal EMMC flash memory has become corrupted?
Firstly, I apologise for the verbose way in which I’ve phrased the question. However, there are literally hundreds of guides on the web that misleadingly claim to show how to backup and restore everything on a phone, but which actually do nothing of the sort. So I felt it best to try and be as precise as possible.
When I buy a new PC, the first thing I generally do is to boot into a Linux live USB distribution and save an image of the entire hard disk. This enables me to restore the PC back to its factory state if something goes horribly wrong.
[As an aside, this is a massive pain in the ass to do and shouldn’t really be necessary. But since PC manufacturers stopped providing separate OS install disks with their computers (presumably this is a deliberate Microsoft policy), a disk image has become the only 100% reliable way of restoring a PC back to its factory state when something goes wrong.]
Anyway, I would like to do something similar with my Android phone (which is a Motorola Moto G4). But what is a relatively simple (if time consuming) task in the PC world is proving to be surprisingly difficult in the Android world. What I’ve done to my phone so far is the following:
I unlocked the bootloader, and installed TWRP.
I then booted into TWRP and created a ‘nandroid’ backup.
I assumed this would be enough to enable me to restore it back to a factory state. But I’ve since done some more research, and it turns out that TWRP does not actually allow you to backup all the partitions on the internal flash memory. And at least one of the excluded partitions stores important stuff like the phone’s IMEI number! So whilst a nandroid backup is useful, it is definitely not a backup of the entire phone.
I’ve noticed that there are some guides on how to copy the entire EMMC flash drive (mmcblk0) to an image file. This process seems somewhat similar to how I would take a disk image on a PC. However, no one explains how to flash the image file back to mmcblk0 if the phone gets bricked.
It also throws up some other question that I can’t find definitive answers to. For example, where is the bootloader actually stored? Is it somewhere on mmcblk0, or is it stored on an entirely separate (and hopefully read-only) flash chip in the same way that a PC’s BIOS would be? If it’s the former, then how would you boot the phone if the mmcblk0 chip became entirely corrupted? Also, where is the Android Debug Bridge utility stored? Is that also on the mmcblk0 chip, or somewhere else?
It’s frustrating that, despite hours of googling, I can’t find definitive answers to these fundamental questions. I would be grateful if anyone here could point me in the right direction.
Thnaks in advance.
Hello there,
I'm wondering if there's anyone knowledgeable to point me in the right direction. Coronavirus (or I) messed up the build.prop file in a Chinese-made JTY-K107 (MT6580 architecture) tablet and now stuck in a soft-brick state. I cannot use adb push or adb sideload (doesn't detect device probably because I had attached another MT device, a Huawei on the PC before and that is the device I pulled the build.prop from to mess with the bigger tablet and now all seems jumbled driver-wise on my Win 10). In any case, I am able to copy to the SD card an update.zip but factory recovery installation is not possible ("installation aborted" - signing issue?). I tried these two zips inside which the original build.prop files are now nestled. It's maybe the commands/scripts that are at fault or it's some signing issue (that hopefully can be tackled). I don't know. I am very reluctant to think about flashing ROMs at this stage. (Porting MT-architecture ROMs are not exactly easy or risk-free, from what I have seen around other threads/forums.)
The link to the folder with the non-working update zips I pulled from other sites or threads (not knowing how I should go about building these files from scratch on my own):
https://app.box.com/s/7byabibx2j0jfo2zlgmg0oi0ca66vkyn
Thanks very much for any info (or possibly a fix of the zips to make it compatible with MT6580 to install the update).
Cheers,
Zoltán
@zanodor
IMHO a simple factory reset may solve your problems.
jwoegerbauer said:
@zanodor
IMHO a simple factory reset may solve your problems.
Click to expand...
Click to collapse
Today I was thinking, people like overcomplicating things: there must be some easy solution. I actually had done that out of frustration (knowing that I had a Titanium Backup on SD) but the boot issue persists (I tried again but all I see is the Android logo for minutes now).
I thought maybe there was a way to repackage my full Titanium Backup into a zip that could be used in Factory Recovery for a restore solution? I perused the net in vain for that too.
I really don't fancy reinstalling Win 10 to fix the driver issues or trying on one of my Linux machines (I am a noob on those too).
Thanks for the answer, anyway.
In the end I managed to restore the tablet (took me 2-3 days of looking around). I'm only writing this up so others facing adb probs can solve their issues on their MTK-built devices. (Actually probably this will work on any device that is not Samsung or whatever old famous brands.)
The first thing to do was sorting out VCOM drivers. There's a Nigerian-sounding guy whose forum Hovatek I followed for tricks on how to go about it (had to download and install Virtual Serial Port Driver to sort out connection issues in Miracle Box/Thunder). Whenever you have some problem, I suggest you include Hovatek in the search string, cause chances are he has a tool and a tut.
Using Miracle Thunder and acting on Hovatek's instructions I made a copy of my firmware. All I really needed was the sytem.img, of course. My bootloader being fine (messing up your device with build.prop only results in a soft brick), it didn't need fixing. Using Assayyed's Kitchen and Hovatek's tutorial again I unpacked the system.bin I extracted with Miracle (which must be all the time used with virus protection off) after renaming system.bin to sytem.img. I exchanged the build.prop and repacked system but didn't wait for the update.zip to be made, instead I took the img file I wanted in the Kitchen. Then tried SP Flash tool to flash system.img on the device but I had issues with the scatter file. So I downloaded a firmware from Boycracked or whoever and used that scatter (in the meantime I overwrote the system.img with mine). I flashed device, turned on the tablet and voila. I hope this helps peeps out there with similar issues.