Related
Hi,
I have searched in the forums but i couldnt find any solution to my problem.
My phone is a LG Optimus 7 unbranded on mango.
I want to backup my phone, update it to the latest rom with tethering enabled and after that i want to restore from backup.
How can i do that?
Thanks in advance!
There is no tool that can do that right now. The backup only happens when a new updates come in and Zune does that. It cannot be done manually.
Thanks for the fast answer!
So do i have to wait for the tethering update to appear in Zune or do i have to flash another firmware?
xtrcentral said:
Thanks for the fast answer!
So do i have to wait for the tethering update to appear in Zune or do i have to flash another firmware?
Click to expand...
Click to collapse
Only Zune will be able to do it. So I guess unless they do you have no choice. And No Firmware can enable it.
wpxbox is actually incorrect, there is a tool to create an image-based backup (like Zune does when updating) on demand. Search the Development and Hacking sub-forum, and you can find it. Note that it requires a program, updatewp.exe, that was once distributed by Microsoft and no longer is, so you'll need to find a copy of it (and the version for that copy must exactly match your Zune version).
However, what you're asking for isn't actually useful anyhow, unless you want to install the update and then immediately remove it. A WP7 backup is really more properly called a restore point - it's a full image of the phone's entire storage, including the parts that are normally read-only (the ROM). Restoring that image overwrites everything, including the ROM. Updates are modifications to the ROM, and restoring a backup will therefore remove the update.
That cleared the things... Thanks.
Thanks for correcting me. Apprciate that.
Yes there is a tool which you can find here but to make it work you need to use Old version of Zune and replace couple of DLL.
I personally have tried it but for some reason it did not work for and hence I was not recommending it. But thats me.
Go ahead and give it a shot to see if it works for you. If yes let me know how you did.
--wpxbox
GoodDayToDie said:
wpxbox is actually incorrect, there is a tool to create an image-based backup (like Zune does when updating) on demand. Search the Development and Hacking sub-forum, and you can find it. Note that it requires a program, updatewp.exe, that was once distributed by Microsoft and no longer is, so you'll need to find a copy of it (and the version for that copy must exactly match your Zune version).
However, what you're asking for isn't actually useful anyhow, unless you want to install the update and then immediately remove it. A WP7 backup is really more properly called a restore point - it's a full image of the phone's entire storage, including the parts that are normally read-only (the ROM). Restoring that image overwrites everything, including the ROM. Updates are modifications to the ROM, and restoring a backup will therefore remove the update.
Click to expand...
Click to collapse
Thanks for providing the direct link. I was able to get it working, although it took a lot of work to find matching versions of the tool installer (v1, not v2) and Zune software. It's possible, though. Take a look at the Backup header in this thread: http://forum.xda-developers.com/showthread.php?t=1271963. It has instructions and links that you may be able to use to make the tool work.
Hi,
I finally poured in one complete day figuring out what was in that thread and made it work. I have written my version of making it work here
And Have also created a Video Demo as a Proof that How I made it work. Any feedback is appreciated.
The video is like 11:28 Minutes long. Where I have :
First showed what is my phone
Then created a Backup
Showed where the backup is actually stored i.e. Zune Default restore point
Reset my Phone
Used the Backup to bring it normal state.
I just received my new TF700 shipped from BestBuy.com
I've already noticed several funny behaviors, as compared with the TF300 I tested out last month.
Battery was at 0% when I opened the box
No typical Android first-time welcome screen stuff
Gallery has a picture taken of a camera calibration test pattern
Dev Options had USB Debugging, Stay Awake, and Allow Mock Locations all checked.
Cannot set the Screen Lock>Slide
Screen seems to flicker a bit when I return to the home screen.
Serial number is reported as 11111111111111111
ADB also identifies the device as 11111111111111111
Several generic actions cause crashes, such as accessing Settings>Accounts and Sync
Browser crashes directly after opening
Red border around the screen, similar to this thread
http://forum.xda-developers.com/showthread.php?t=1442185
Numerous pre-loaded apps that look well outside of standard
AtCmdSender
ATS_Discharge
ATS_MMI_TF700
bmmi.v2.3
BTtest
Command
DevTools (I know this one, but can't remember if this is included as standard app now or not, I doubt it)
FTM
GPS Test v5.12
Log Tool 2.21.1
MTTestTool
RunIn_v2.5
Spare Parts (as with DevTools, I know this one but don't think this is standard)
TF700_Gsensor_TestV1.22
TF700T (ATS logo)
TF700T_Ecompas_Kv1.3
TF700T_GsensorKv1.23
WLAN RF Test Tool BCM4329
And of course, the Build Number is identified as
OPEN_epad-eng 4.0.3 IML74K OPEN_epad-9.0.4.104.15-20120618 test-keys
Several other threads I found regarding OPEN_epad builds
http://forum.xda-developers.com/showthread.php?t=1577386
http://forum.xda-developers.com/showthread.php?t=1685600
http://www.transformerforums.com/forum/transformer-pad-300-help/24112-solved-update-firmware.html
http://www.transformerforums.com/fo...prime-not-offering-update-new-firmware-2.html
I would like to get this thing into a more standard operating condition for myself (before I start looking at custom ROMs, of course).
I thought I would post in case any Devs here thought there might be useful stuff I could dump.
I'll also try freenode.net #asus-transformer
reserved
I don't know the status of root, or whether the bootloader is unlocked.
Looks like the device is NOT unlocked.
ADB just spit back
Code:
/system/bin/sh: cp: not found
so maybe I need some BusyBox up in here to keep working
UPDATE: So now it looks like I'm finding that the tab won't charge past 59%.... :/
If your device is unlocked, you can see it in the upper right corner when turning the device is turned on
"Your device is unlocked"
Sent from my ASUS Transformer Pad TF700T using xda premium
hillbicks said:
If your device is unlocked, you can see it in the upper right corner when turning the device is turned on
"Your device is unlocked"
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
Upper left corner
Not unlocked
I got the same advice about upper left corner on IRC.
Doesn't look like the tablet is unlocked right now. Of course, that may change
Can you zip some of those apps and post them somehwere please? Would like to take a look if you don't mind. PM me.
EDIT: and eng in the firmware typically means an engineering build.
If the bootloader comes pre unlocked, you've found yourself a pretty good device. Warranty+custom roms.
system-app and data-app
I pulled everything from these two folders.
data-app.zip
15,307 kB
system-app.zip
136,636 kB
UPDATE: removed links to DL files, may replace later
PM sent
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Dev apps
I've PM'd links to download everything from /data/app and /system/app to a couple of people.
I'll be curious to know if anyone finds anything interesting or useful.
Is there anything else I should try to dump from this tab?
I'd like to start using it (which probably means wiping), but want to make sure I pull all of the helpful stuff for XDA members first.
ScottHW said:
I've PM'd links to download everything from /data/app and /system/app to a couple of people.
I'll be curious to know if anyone finds anything interesting or useful.
Is there anything else I should try to dump from this tab?
I'd like to start using it (which probably means wiping), but want to make sure I pull all of the helpful stuff for XDA members first.
Click to expand...
Click to collapse
Hi,i'm not a developer and so far most of that soft looks like diagnostic tools but a dev should know better.As for using the tablet i don't know if it's a good idea to keep it (i would return it) mostly because of the serial number (have you checked the logs to see if the device try to communicate with Asus server?) and because is clear that such a device was used for testing so maybe it was an early sample...anyway it's your call.If you keep it you can try to root ,unlock and than install the custom recovery so you can do a nandroid backup before wipe everything.
I would root, try to unlock get recovery installed and take a backup and post it.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Return.... Nandroid
Thanks for the suggestions, that is basically what I was thinking.
I agree that this will most likely get returned. Just want to get all the goodies first.
I do think I'll have to return it. Too many screwy things going on here.
As for dumping, I thought the same lines a la Nandroid.
Of course, if I unlock the bootloader to install a custom recovery, then I wouldn't be able to return it....
ScottHW said:
Thanks for the suggestions, that is basically what I was thinking.
I agree that this will most likely get returned. Just want to get all the goodies first.
I do think I'll have to return it. Too many screwy things going on here.
As for dumping, I thought the same lines a la Nandroid.
Of course, if I unlock the bootloader to install a custom recovery, then I wouldn't be able to return it....
Click to expand...
Click to collapse
IMO you've done your best to help the community so just return it and start enjoy your tablet. Also i don't think that the tablet is a developement enviroment so it can't be such a valuable resource for devs.
Update and/or return
Pretoriano80 said:
IMO you've done your best to help the community so just return it and start enjoy your tablet. Also i don't think that the tablet is a developement enviroment so it can't be such a valuable resource for devs.
Click to expand...
Click to collapse
Glad to do what I can to help. I really appreciate those whose skills exceed my own, and do the dev work from which we all benefit.
Another way of saying that: I can't wait to get some sweet sweet CM up on this tab!
Only problem is... BestBuy doesn't have these in stock, which is why I had to order it shipped from BestBuy.com
Now I'll have to wait more days for another one to ship
I might try to "update" the software OTA, but I've read several other threads mentioning that OPEN_epad cannot be easily updated OTA.
I don't have any internet connection on this thing turned on yet, in case it tries to dial home and updates before I dump useful stuff, or gets remotely locked and/or wiped.
I'll flip on some wifis and see what System Update does for me.
UPDATE: System Firmware Update simply returns "There is no update available for your device currently." Guess I'll have to try harder to wipe away the OPEN_epad build.
adb pull /system
I just pulled everything on /system. A log is attached.
If anyone wants anything in there, let me know.
/system
413,136,276 bytes
UPDATE: I had a problem pulling /data, so here's a list for now (attached)
[email protected]:/ # cd /data
[email protected]:/data # ls -alR
UPDATE: removed attached lists of files for security
dumps
Alright.... I got some help and I dumped /system /data first32 (half the bootloader, recovery, boot, provisioning certificate...)
The dev I worked with over on freenode.net#asus-transformer is much more skilled than I, so now these are .img dumps, rather than just pulling individual files.
If anyone thinks they can find diamonds in that rough, let me know.
ScottHW said:
Alright.... I got some help and I dumped /system /data first32 (half the bootloader, recovery, boot, provisioning certificate...)
The dev I worked with over on freenode.net#asus-transformer is much more skilled than I, so now these are .img dumps, rather than just pulling individual files.
If anyone thinks they can find diamonds in that rough, let me know.
Click to expand...
Click to collapse
PM sent
Sent from my GT-P1000 using xda app-developers app
ScottHW said:
Alright.... I got some help and I dumped /system /data first32 (half the bootloader, recovery, boot, provisioning certificate...)
The dev I worked with over on freenode.net#asus-transformer is much more skilled than I, so now these are .img dumps, rather than just pulling individual files.
If anyone thinks they can find diamonds in that rough, let me know.
Click to expand...
Click to collapse
Thanks alot. I will take a look. You can pull your Dropbox links if you would like so you don't use up your bandwidth.
Go ahead and proceed with what you want to do...will let you know if I find anything interesting to us
so two weeks have passed did you get a replacement for the tablet or updated or something? how that went.
also : was any of those files useful for developers?
Hey xda. Sorry if this post has been misplaced, but I noticed there is no device forum for the tablet I am asking about today, and that is understandable. My girlfriend recently got an eMatic eGlide Pro II XL tablet for her birthday and it is running Android Ice Cream Sandwich 4.0.3. I noticed that it had a lot of bloatware and no google play store on it, and she wanted the play store, so I rooted the device for her and installed the play store and it works like a charm. The only problem I seem to have run into is this read only folder called "oem". The path for this partition is /oem/ and there are a few bloatware apps in there. For some reason though, I cannot edit or delete anything in that partition as it says it is read only even though i am using the root functions of ES File Explorer. I am able to modify other system apps though root explorer. I even tried using terminal emulator commands to remove the items but it still didn't work. Is there a way I can mount this folder as read/write? If I can, that would be a blessing, as I could delete the crapware that came with the tablet and the old version of YouTube that is buggy and not updateable thanks to being placed in the oem folder. Thanks for reading all this guys, I know it's a wall of text, haha.
Ematic: What is the browser?
What is the browser that is install from factory.. on Ematic devices ..as it is not "Chrome" [It almost looks like Dolphin], when I tried to do a regular .apk install of "Chrome" from the Google store it dies which almost tells me that it need to be pushed into the device. So am I correct that I need to find a downloadable .apk of "Chrome" for Android 4.0.3 ?
bfrench1990 said:
Hey xda. Sorry if this post has been misplaced, but I noticed there is no device forum for the tablet I am asking about today, and that is understandable. My girlfriend recently got an eMatic eGlide Pro II XL tablet for her birthday and it is running Android Ice Cream Sandwich 4.0.3. I noticed that it had a lot of bloatware and no google play store on it, and she wanted the play store, so I rooted the device for her and installed the play store and it works like a charm. The only problem I seem to have run into is this read only folder called "oem". The path for this partition is /oem/ and there are a few bloatware apps in there. For some reason though, I cannot edit or delete anything in that partition as it says it is read only even though i am using the root functions of ES File Explorer. I am able to modify other system apps though root explorer. I even tried using terminal emulator commands to remove the items but it still didn't work. Is there a way I can mount this folder as read/write? If I can, that would be a blessing, as I could delete the crapware that came with the tablet and the old version of YouTube that is buggy and not updateable thanks to being placed in the oem folder. Thanks for reading all this guys, I know it's a wall of text, haha.
Click to expand...
Click to collapse
How did you root the tablet? it seems there are several Ematic tablets being sold at wal-mart and I think people would like to know how you rooted it. (I know I would.)
fsuinnc said:
How did you root the tablet? it seems there are several Ematic tablets being sold at wal-mart and I think people would like to know how you rooted it. (I know I would.)
Click to expand...
Click to collapse
I used a tool called Root with Restore by Bin4ry. It took me a couple times. The first time I did it, all it managed to do was slow the tablet down, then i just performed a factory reset and tried again using the same process until it worked. It didn't take all that long. The hardest part is getting the adb drivers to recognize the tablet. I will attach my adb drivers so you don't have to go through all the rigamarole.
Navigate to wherever your android sdk folder is. Mine is at C:\Program Files (x86)\Android\android-sdk
Within the android-sdk folder, look for extras, then google, then usb_driver. Make a backup of everything in your usb_driver folder, just in case.
Next just extract the contents of the zip I attached to this post. Make sure USB debugging is on, and plug it in. It should be recognized assuming there isn't some other problem i haven't encountered or forgot to mention.
Once your computer recognizes the adb interface for your tablet, use the Root with Restore tool until it works.
bfrench1990 said:
I used a tool called Root with Restore by Bin4ry. It took me a couple times. The first time I did it, all it managed to do was slow the tablet down, then i just performed a factory reset and tried again using the same process until it worked. It didn't take all that long. The hardest part is getting the adb drivers to recognize the tablet. I will attach my adb drivers so you don't have to go through all the rigamarole.
Navigate to wherever your android sdk folder is. Mine is at C:\Program Files (x86)\Android\android-sdk
Within the android-sdk folder, look for extras, then google, then usb_driver. Make a backup of everything in your usb_driver folder, just in case.
Next just extract the contents of the zip I attached to this post. Make sure USB debugging is on, and plug it in. It should be recognized assuming there isn't some other problem i haven't encountered or forgot to mention.
Once your computer recognizes the adb interface for your tablet, use the Root with Restore tool until it works.
Click to expand...
Click to collapse
Thanks, that's great info. I will try it out. (I have a Ematic egs005 7" on it's way to me. they seem to be very cheap right now at under $60)
fsuinnc said:
Thanks, that's great info. I will try it out. (I have a Ematic egs005 7" on it's way to me. they seem to be very cheap right now at under $60)
Click to expand...
Click to collapse
I'll bet that you can get it rooted. You may have to edit those drivers though since I don't think my girlfriend's tablet isn't the same as the one you mentioned.
If the drivers I posted don't work for you, then open up "android_winusb.inf" from that zip file in your favorite text editor.
Somewhere under the "[Google.NTx86]" and "[Google.NTamd64]" sections, add this:
;eMatic egs005
Remember where you put those, cause what goes under those entries is the hardware ID of your tablet. You can get that by going under device manager and right clicking on your tablet, if it is unrecognized it should have a yellow triangle on it or something like that. Go to properties and go to the details tab, then from the drop down menu, select hardware IDs. In my case, two came up. Just pick one. If that one ends up not working later, use the one you didn't try.
Now, your entries should look like this:
;eMatic egs005
%CompositeAdbInterface% = USB_Install, (your hardware ID)
Next, try to update the drivers on your tablet via device manager. Right click on your tablet like we did last time, and click properties. Go to the driver tab, and hit the update driver button. You'll have to manually navigate to where your drivers are. Select the folder where you extracted the zip to (make sure you have the edited file in there!) and follow the procedure to update the driver.
Next, open up an adb window and type in adb devices. If you have something showing up, congrats! You should be able to try the root tool now. As always, be careful!
eglide pro ll xl
I just bought the eglide pro ll xl also. From what I have read and done to my tab so far, it is already rooted from the factory. It sounds like a lot of the ematic tabs are. I've been researching different operating systems to put on my tab but there isn't anything that says it is specifically for mine. They pretty much just list the types of tablets the ROMS will work for. The question I have is what type of tablet is this. Allwinner a10? LY F1? TREQ? I would really like to know this and a good way to back up my current system so if I screw it up I can go back and try again.
-Z
Livinbad said:
I just bought the eglide pro ll xl also. From what I have read and done to my tab so far, it is already rooted from the factory. It sounds like a lot of the ematic tabs are. I've been researching different operating systems to put on my tab but there isn't anything that says it is specifically for mine. They pretty much just list the types of tablets the ROMS will work for. The question I have is what type of tablet is this. Allwinner a10? LY F1? TREQ? I would really like to know this and a good way to back up my current system so if I screw it up I can go back and try again.
-Z
Click to expand...
Click to collapse
I didn't add most of those entries in the drivers file, it originated as a sort of "fix all" driver that was posted on xda to connect many many types of different devices to adb without hassle. I added a few of the entries using the hardware ID method I described above to accommodate some less popular devices that my friends and family asked me to root.
I think I heard talk somewhere about custom roms for the eGlide, but I have no clue how to flash them, and seeing as how that tablet wasn't mine, I did not want to try to flash one and brick it, lol. I couldn't find any recoveries or any other tool to flash things to it. If you do find a way, all I can say is be careful.
As far as backing up goes, root with restore supports unrooting as well. I never performed that function though, since root hasn't done anything bad for the tablets I put them on, haha. I'm not certain there is an easy backup method since as I said a second ago, no custom recoveries. To be safe, I would recommend a factory data reset before attempting any rooting/unrooting of this tablet.
I hope I helped with my feedback.
bfrench1990 said:
I didn't add most of those entries in the drivers file, it originated as a sort of "fix all" driver that was posted on xda to connect many many types of different devices to adb without hassle. I added a few of the entries using the hardware ID method I described above to accommodate some less popular devices that my friends and family asked me to root.
I think I heard talk somewhere about custom roms for the eGlide, but I have no clue how to flash them, and seeing as how that tablet wasn't mine, I did not want to try to flash one and brick it, lol. I couldn't find any recoveries or any other tool to flash things to it. If you do find a way, all I can say is be careful.
As far as backing up goes, root with restore supports unrooting as well. I never performed that function though, since root hasn't done anything bad for the tablets I put them on, haha. I'm not certain there is an easy backup method since as I said a second ago, no custom recoveries. To be safe, I would recommend a factory data reset before attempting any rooting/unrooting of this tablet.
I hope I helped with my feedback.
Click to expand...
Click to collapse
I actually installed CWM 6.0.1.2 by Flowish on to my tab and it works great except for the process he has to get in to the recovery. I have to use the terminal emulator to launch it. That's why I am leery about installing a different ROM. If I can't get the thing to boot up properly I then can't get to the terminal emulator to get to recovery to restore my backup. I'm still searching and learning though. I'll figure it out eventually.
Livinbad said:
I actually installed CWM 6.0.1.2 by Flowish on to my tab and it works great except for the process he has to get in to the recovery. I have to use the terminal emulator to launch it. That's why I am leery about installing a different ROM. If I can't get the thing to boot up properly I then can't get to the terminal emulator to get to recovery to restore my backup. I'm still searching and learning though. I'll figure it out eventually.
Click to expand...
Click to collapse
Check if there's fastboot for this tablet. There's a fastboot command to boot into the recovery. If not, then I would just not flash a Rom
A rough description of how I solved this specific problem can be found here:
http://forum.xda-developers.com/showpost.php?p=44784112&postcount=14
Also, you don't need the huge system dump to fix this!
Click to expand...
Click to collapse
Hey everyone.
TL;DR: I quite desperately need an image (or a tarball) of a working /system partition from an ASUS MeMO Pad 7 HD (MD173x) for the recovery of a soft-bricked unit I have here. Apparently there's none available anywhere. Any help would be very much appreciated.
I have an ASUS MeMO Pad 7 HD here (ME173x) that got soft-bricked by an improper installation of Chainfire3D [not by me]. The device won't finish booting up, but it gives me shell/root access to the entire system through ADB, so it's salvageable. I have a serious problem, though: while I have access to the entire system, I have no images to restore it from - absolutely nothing!
I've tried looking for any manual updates or SD-card-based recovery images on the ASUS website, but only found something for the regular MeMO Pad. I've tried that option still, but the pad ignores it, so probably incompatible. For the MeMO Pad 7 HD, ASUS have no images at all - just user manuals and the source code! I suppose that's the catch to its otherwise cheap price, and I'll spare you my opinions about that.
When it comes to the boot loader, there are 3 options that it offers: normal boot, FASTBOOT or Recovery (which is anything but: it just pops a dead Android icon with "NO COMMAND" underneath it - not particularly helpful). Can't do a whole lot with that, I suppose.
So yeah... My options, as I see them, are to either beg somebody else with a MeMO Pad 7 HD for their /system partition (either a dd dump, tar.gz archive of all the files within, or a CWM recovery file perhaps), in hopes that they are rooted and need little to no guidance on obtaining that data. Failing that, I may have to beg the guys behind Chainfire3D to perhaps give me a list of all the files they introduce into the system and modify, and try to undo those changes manually, and if there's anyone here that reads this and can help me with any of those options, I'll be forever grateful to them.
I assume contacting ASUS themselves about this is a waste of time, since I highly doubt that they'll take this well from a warranty perspective, nor do I think they will be keen to provide me with any recovery images or be useful/helpful in any "non-generic" way...
Anyway, here's my problem, so if anyone has any ideas on getting this solved, I'm all ears [or in this case - eyes].
Thanks!
-- Ice
P.S. Please spare me the lectures about backing up, rooting, bricking, "being careful", etc. This isn't my device - I'm not the one who bricked it. I'm the person people hand these devices to when they've screwed up...
I have a rooted Memo Pad. Can I somehow save an full image of it and share with you?
Gesendet von meinem ME173X mit Tapatalk 2
GermanGigaDepp said:
I have a rooted Memo Pad. Can I somehow save an full image of it and share with you?
Gesendet von meinem ME173X mit Tapatalk 2
Click to expand...
Click to collapse
Many thanks for your response.
You can make a tarball (tar.gz archive) of /system by using the built-in tools. Assuming you have at least a gigabyte of free space in internal memory, here's what you can do:
Get a Terminal Emulator application (if you don't have one): https://play.google.com/store/apps/details?id=jackpal.androidterm
Tell the pad to archive /system files:
Run the Terminal app
Type the following commands:
su
tar czvf /sdcard/system.tar.gz /system
Click to expand...
Click to collapse
Locate and upload the system.tar.gz file to Dropbox or some other place that allows you to upload large files and post a link to it - either here or in private.
Now I've noticed that such a file can take around 700MB, which is quite a bit. If that becomes a problem, you can try getting a smaller archive by picking just the more important folders within /system. In that case, this is how your tar command will look instead:
tar czvf /sdcard/system-partial.tar.gz /system/bin /system/etc /system/lib /system/vendor /system/build.prop
Click to expand...
Click to collapse
Again, many thanks for wanting to do this!
P.S. What these commands do is essentially "zipping up" the contents of the /system folder into am archive file. You can do this with a root-capable file explorer, but it's just easier to do it through the command line, because we all know what exactly to expect from these commands...
P.P.S. To remove that system.tar.gz file through the terminal, type rm /sdcard/system.tar.gz
IceDrake said:
Many thanks for your response.
You can make a tarball (tar.gz archive) of /system by using the built-in tools. Assuming you have at least a gigabyte of free space in internal memory, here's what you can do:
Get a Terminal Emulator application (if you don't have one): https://play.google.com/store/apps/details?id=jackpal.androidterm
Tell the pad to archive /system files:
Run the Terminal app
Type the following commands:
Locate and upload the system.tar.gz file to Dropbox or some other place that allows you to upload large files and post a link to it - either here or in private.
Now I've noticed that such a file can take around 700MB, which is quite a bit. If that becomes a problem, you can try getting a smaller archive by picking just the more important folders within /system. In that case, this is how your tar command will look instead:
Again, many thanks for wanting to do this!
P.S. What these commands do is essentially "zipping up" the contents of the /system folder into am archive file. You can do this with a root-capable file explorer, but it's just easier to do it through the command line, because we all know what exactly to expect from these commands...
P.P.S. To remove that system.tar.gz file through the terminal, type rm /sdcard/system.tar.gz
Click to expand...
Click to collapse
I get a invalid option -- z error.
Followed all the step, I did.
EDIT : Scratch that, I used this code instead.
#tar -cvf /sdcard/system.tar /system
Wait while I upload the dump.
---------- Post added at 08:20 AM ---------- Previous post was at 07:30 AM ----------
here's the link to the dump
btw, I've renamed some APKs as bak, since there is no option to disable some of those apps.
I've removed the link to the file. PM me if anyone wants it.
So I guess my help is not needed anymore.
If you still need my help just ask me, I will do it.
Thank you both.
I will grab the file once I get access permission (click the blue SHARE button in GDrive and change the visibility to "Those with the link" or add ice3715 at gmail com to it) and will hopefully be able to continue bringing this thing back to life. If I'll stumble over anything else, I will certainly know whom to rely on.
Very much appreciated!
IceDrake said:
Thank you both.
I will grab the file once I get access permission (click the blue SHARE button in GDrive and change the visibility to "Those with the link" or add ice3715 at gmail com to it) and will hopefully be able to continue bringing this thing back to life. If I'll stumble over anything else, I will certainly know whom to rely on.
Very much appreciated!
Click to expand...
Click to collapse
Alrighty. Already added your email address. Pls check
Sent from my ME173X using xda app-developers app
ericmaxman said:
Alrighty. Already added your email address. Pls check
Sent from my ME173X using xda app-developers app
Click to expand...
Click to collapse
Checked and done downloading. :good:
Post-recovery
Alrighty then!
Thanks to the image provided, I've managed to get the device to finish its boot sequence: when comparing the files of the two, I found a shell script at /system/lib/cf3d_uninstall.sh that basically gave me instructions on how to uninstall CF3D.
The files it overwrote were:
/system/lib/libGLESv1_CM.so
/system/lib/libGLESv2.so
Click to expand...
Click to collapse
The backups of the originals were stored as:
/system/lib/libGLESv1_CM_ORG_CF3D.so
/system/lib/libGLESv2_ORG_CF3D.so
Click to expand...
Click to collapse
Restoring these files and changing the permissions as specified in cf3d_uninstall.sh brought the device back to life. The OS was somewhat unstable (appcrashes and spontaneous reboots), but a few reboots, updates and dalvik-cache wipes later, it seemed to have stabilized on its own.
Again, many thanks to ericmaxman for providing the system image and GermanGigaDepp for being willing to do the same. You guys are awesome!
Lesson of the week: When rooting your device (or even before that), always back up your entire system! (or at least your entire /system) It is not guaranteed that the manufacturer will offer any recovery images for it or help you in any way, and if you mess up, you'll get stuck just like me!
tar cvf /sdcard/system-backup.tar /system
Click to expand...
Click to collapse
IceDrake said:
Alrighty then!
Thanks to the image provided, I've managed to get the device to finish its boot sequence: when comparing the files of the two, I found a shell script at /system/lib/cf3d_uninstall.sh that basically gave me instructions on how to uninstall CF3D.
The files it overwrote were:
The backups of the originals were stored as:
Restoring these files and changing the permissions as specified in cf3d_uninstall.sh brought the device back to life. The OS was somewhat unstable (appcrashes and spontaneous reboots), but a few reboots, updates and dalvik-cache wipes later, it seemed to have stabilized on its own.
Again, many thanks to ericmaxman for providing the system image and GermanGigaDepp for being willing to do the same. You guys are awesome!
Lesson of the week: When rooting your device (or even before that), always back up your entire system! (or at least your entire /system) It is not guaranteed that the manufacturer will offer any recovery images for it or help you in any way, and if you mess up, you'll get stuck just like me!
Click to expand...
Click to collapse
Good to hear that you managed to get yours fixed. :thumbup:
Sent from my ME173X using xda app-developers app
Desperate for help (Asus MeMo Pad 7 HD)
Hi everyone (may be IceDrake can help!)
I am new into the forum. I have a dead new Asus ME173X.
I have the same problem like IceDrake (Chainfire3D problem!). I am desperate for help getting "MeMO Pad 7 HD for their /system partition" like IceDrake AND PLEASE STEP BY STEP help bringing my new MemO Pad 7 into life again.
Much appreciate any help I can get.
Regards,
Medhat
----------------------------------------------------------------------
IceDrake said:
Hey everyone.
TL;DR: I quite desperately need an image (or a tarball) of a working /system partition from an ASUS MeMO Pad 7 HD (MD173x) for the recovery of a soft-bricked unit I have here. Apparently there's none available anywhere. Any help would be very much appreciated.
I have an ASUS MeMO Pad 7 HD here (ME173x) that got soft-bricked by an improper installation of Chainfire3D [not by me]. The device won't finish booting up, but it gives me shell/root access to the entire system through ADB, so it's salvageable. I have a serious problem, though: while I have access to the entire system, I have no images to restore it from - absolutely nothing!
I've tried looking for any manual updates or SD-card-based recovery images on the ASUS website, but only found something for the regular MeMO Pad. I've tried that option still, but the pad ignores it, so probably incompatible. For the MeMO Pad 7 HD, ASUS have no images at all - just user manuals and the source code! I suppose that's the catch to its otherwise cheap price, and I'll spare you my opinions about that.
When it comes to the boot loader, there are 3 options that it offers: normal boot, FASTBOOT or Recovery (which is anything but: it just pops a dead Android icon with "NO COMMAND" underneath it - not particularly helpful). Can't do a whole lot with that, I suppose.
-------------------------------------------------------------------------------------
So yeah... My options, as I see them, are to either beg somebody else with a MeMO Pad 7 HD for their /system partition (either a dd dump, tar.gz archive of all the files within, or a CWM recovery file perhaps), in hopes that they are rooted and need little to no guidance on obtaining that data. Failing that, I may have to beg the guys behind Chainfire3D to perhaps give me a list of all the files they introduce into the system and modify, and try to undo those changes manually, and if there's anyone here that reads this and can help me with any of those options, I'll be forever grateful to them.
I assume contacting ASUS themselves about this is a waste of time, since I highly doubt that they'll take this well from a warranty perspective, nor do I think they will be keen to provide me with any recovery images or be useful/helpful in any "non-generic" way...
Anyway, here's my problem, so if anyone has any ideas on getting this solved, I'm all ears [or in this case - eyes].
Thanks!
-- Ice
P.S. Please spare me the lectures about backing up, rooting, bricking, "being careful", etc. This isn't my device - I'm not the one who bricked it. I'm the person people hand these devices to when they've screwed up...
Click to expand...
Click to collapse
Help needed for newbie
Hello everyone,
I´m a newbie and need some help.
I installed Chainfire 3 D on my new Memo Pad HD 7 and it wont boot anymore. I think I need a system image!
I´m thankful for any help and advice. Where I can download the system image file? Is there somewhere a step by step guide for installing the system image file ?
Thank you
Tom Hell
TomHell said:
Hello everyone,
I´m a newbie and need some help.
I installed Chainfire 3 D on my new Memo Pad HD 7 and it wont boot anymore. I think I need a system image!
I´m thankful for any help and advice. Where I can download the system image file? Is there somewhere a step by step guide for installing the system image file ?
Thank you
Tom Hell
Click to expand...
Click to collapse
I don't have my PC with me now...will grant u access to the file tomorrow evening
Sent from my ME173X using xda app-developers app
medhatfawzy said:
Hi everyone (may be IceDrake can help!)
I am new into the forum. I have a dead new Asus ME173X.
I have the same problem like IceDrake (Chainfire3D problem!). I am desperate for help getting "MeMO Pad 7 HD for their /system partition" like IceDrake AND PLEASE STEP BY STEP help bringing my new MemO Pad 7 into life again.
Much appreciate any help I can get.
Regards,
Medhat
----------------------------------------------------------------------
Click to expand...
Click to collapse
If you have the same problem as me, then you don't really need the /system partition. I needed it only to do some comparisons, and I found a CF3D uninstall script that way.
I'll tell you right away that unless you're OK with using the command line, ADB and Linux shell (adb shell), you should really try finding someone who is more familiar with these things, because "experimenting" with such a tablet may cost you dearly - ASUS offers no recovery for it whatsoever! Trying to recover it manually without knowing what you're doing there is a bad idea!
Also, the commands below may eventually become outdated, so instead of using those, see if you can cat /system/lib/cf3d_uninstall.sh and do what it says instead (except for stop - don't type that in the shell )
To recover it from the problem I was having, you should gain access to the tablet over adb first:
Plug the tablet into your PC using a USB cable
Open Command Prompt: press WIN+R to pop up the Run dialog, then type cmd and press ENTER
Type adb shell into the command prompt.
If you don't have ADB installed, then Google about for some guides on how to get it installed first. This is one of them:
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Once inside the shell, go root, remount the /system partition for writing and restore the backed up drivers by typing these (VERY slowly and carefully!):
Code:
su
mount -o rw -o remount /[email protected] /system
cat /system/lib/libGLESv1_CM_ORG_CF3D.so > /system/lib/libGLESv1_CM.so
chown 1000:1000 /system/lib/libGLESv1_CM.so
chown system:system /system/lib/libGLESv1_CM.so
chmod 644 /system/lib/libGLESv1_CM.so
cat /system/lib/libGLESv2_ORG_CF3D.so > /system/lib/libGLESv2.so
chown 1000:1000 /system/lib/libGLESv2.so
chown system:system /system/lib/libGLESv2.so
chmod 644 /system/lib/libGLESv2.so
After that, the tablet should be able to boot as it did for me. Otherwise, you may want to type reboot and let it restart completely.
Hope this helps in some way. It didn't damage the device I was working with, but I can't possibly offer any guarantees about yours (especially if it isn't MeMO Pad 7 HD, or one with a different firmware).
P.S. For people asking for "system images", etc: please understand that it's not a recovery image or anything! You can't just flash it into the device and make it work! What I was asking for is a bunch of files to compare against - manually, so if you don't really know what you're doing, do try to find someone who does.
TomHell said:
Hello everyone,
I´m a newbie and need some help.
I installed Chainfire 3 D on my new Memo Pad HD 7 and it wont boot anymore. I think I need a system image!
I´m thankful for any help and advice. Where I can download the system image file? Is there somewhere a step by step guide for installing the system image file ?
Thank you
Tom Hell
Click to expand...
Click to collapse
Okay, granted you access to the file already.
ericmaxman said:
Okay, granted you access to the file already.
Click to expand...
Click to collapse
can I have permission to access it as well?
---------- Post added at 06:22 PM ---------- Previous post was at 05:41 PM ----------
Icedrake can you upload or mirror ericmaxman's dump file, I would like to try this steps first as I'm still trying to downlod all nccessary files for the adb to work on my machine.
Hi iceDrake, I'm a noob and dont know anything about ADB, can you help I got the system.tar from Eric, but dont know what to do with it. I have the same issue as you. But I can seems to have my tab be recognize by my PC. I can still go to the recovery though
I killed my HD7 with my stupidity and chainfire
Hello IceDrake and everyone else who can help,
My HD7 wont boot it´s in a endless loop because of that the usb/adb driver cannot be installed. (adb shell is not possible - no connection with device)
Does this mean I can my save my device just with recovery or fastboot ?
Can i recover my HD7 with the system.tar file offered here in the forum? What have I to do ???
Thanks for any advice!
Tom Hell
chainfire suck on asus memo pad hd 7
You need adb to use the system.tar. I have the same problem as you. I tried fastboot but each time I try to use the recovery flash I'll get an error download Error please re-pluggin USB cable.
I have not choice than to send it to Asus service center. say if you do a factory reset and wipe cache, can they still know if you rooted your device?
Hello, I have a big problem, I rooted my memopad HD7 and later I removed some asus applications, I had some problems with my excahange account so I restored to factory, but now I am not able to install or update any app from play store, I get a 491 Error code, I also tried to install Amazon App Store but the download always fails, same with any other file that I try to download.
I have googled about 491 error code but the answer is always to wipe dalvik cache but i am not able to do so, as I have no recovery.
Ant suggestion? any chance to restore to factory defaults with some image file?
Edited: well, I managed to return it at the store where I bought it and get.another one later. What I have learned from this is that I would never root again until there is no way to recover the device, preferably CWM recovery.
Hi, first of all, thank you for reading me.
I think i messed up big time.
I had Havoc OS 4.1 installed since more than a year and it was kinda messy e.g. the sim card card wasnt recognized anymore so wasnt able to make calls because i played to much in the settings.
Having some stupid but incredibly addictive games on this smartphone i decided to keep it like this and since i'm a complete n00bs and being afraid of security risk of rooting my device i never rooted it.
Big mistake.
So, recently, one games needed an update (like they all do at least once a week) and since i'm anti-google/f***book (no comment please) i nvever saved my progress in the cloud and "that" game required absolutely an update.
I installed the update from an alternative apk source and , (applause if you want and laugh), it screwed up the game.
Now the nightmare begin.
Since the device isnt rooted i made a backup of /data partition. Gone crazy and before i might explode in an uncontrollable fury and madness i used LMSA to rescue the phone. And myself, lol.
Now i have stock android and i am googled to the bone. My butt hurts. My head too.
THE (first) simple question is : how can i restore this backup because i have the error 255?
Notes and observations; logically i would say because the device is back with stock rom and doesnt have the same os/rom installed and/or the partition and whatever is not the same wich may explain the error 255.
SECOND QUESTION: can i extract/uncompress this backup and take the precious data wich is my games progresses and restore it somehow?
I know i have to give as much information possible but i dont what else to give. If you need logs, or everything else just say it nicely and i will give it to you with immense pleasure.
Oh yeah, model : XT2113-2 5g Kiev RETCA 128gb a/b type and maybe was crypted before because twrp asked me the password to make backup or else.
Thank you in advance and i really hope somebody would help, if not i just loosed 1.5 years of stupid gaming because i messed up like an idiot. (A lesson well learned, the hard way...)
Thank you so much for not answering this simple question.
Kerplunk83 said:
Thank you so much for not answering this simple question.
Click to expand...
Click to collapse
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
Finally a sign of life from someone here.
Thank you sd_shadow
sd_shadow said:
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
Click to expand...
Click to collapse
These precious brief and concise 2 lines of a simple answer is immensely welcomed.
Wich point me to reply that to my knowledge i interpret it as a security chip with big chances that its in relation to the knox technology.
It also point me to ask WHY, if i cant back up because of that, why/how is it possible to install a custom rom or gsi (sorry i still dont make the difference because i dont understand it) on this very protected smartphone?
That must explain why i had problems trying to root it and fail each time.
Finally i think that i should use another device for android gaming since i dont want to depend on f***book and google.
Thanks again sd_shadow. Even if it was a very simple answer it enlightens me alot.
Note: sorry for my bad english.
Kerplunk83 said:
how can i restore this backup because i have the error 255?
Click to expand...
Click to collapse
This error code means that at some point your backup of /data could not be extracted further. But for more detailed infos you must provide a recovery.log which will be generated when doing a backup of e.g. /boot.
>>> Please DO NOT copy+paste it here!! <<<Rename it (recovery.log > recovery.log.txt) to be able to upload it within "Attach files".
Kerplunk83 said:
can i extract/uncompress this backup and take the precious data wich is my games progresses and restore it somehow?
Click to expand...
Click to collapse
Yes, use Titanium Backup (TB). Although it's very outdated it still features a restore of single apps out of a TWRP backup. Here's how you do it:
1. IMPORTANT: TB will only search for TWRP backup files on internal storage!! Use the default path created by TWRP, e.g.: /sdcard/TWRP/BACKUPS/ZY322V8K28/2023-04-08--06-53-20/
2. Install and open Titanium Backup.
3. In the upper right corner tap
MENU > scroll down to "Extract from Nandroid backup" > choose your backup folder
##############
Notes:
- Usually a TWRP backup of /data consists of several parts (data.ext4.win000, ~win001, ~win002 etc). TB requires all of them (or at least those ones with the /data/data/ path inside).
- If you are facing this error message:
Could not find any data in this TWRP backup
then your TWRP backup is compressed with gzip. To decompress it you must rename the file
data.ext4.win001 > data.ext4.win001.gz
and extract it with any archiver tool, e.g.:
- ZArchiver (Android)
- 7zip (Windows)
- Problems finding any TWRP backup data with Titanium Backup? Then please check your path!! (see above section)
Good luck!!
Thank you very much WoKoschekk i'll do it as soon i'll have the time for since i'm working today.
Thank you so much again, i'll keep you posted with logs and such.
I'm sorry i didnt gave news since, i'm not doing very well.
there's those 2 question i still have in my head;
1-With all the instructions you gave me is it worthy to continue because when i did the backup i wasnt rooted?
2- i'm sure i read many time to use Titanium Backup (wich is a paid app?) i have to be rooted or have root access.
Ultimately, how can i be rooted if there's a chip preventing me to do so?
I'll keep you posted when i'll be of better health, thank you.
Kerplunk83 said:
-With all the instructions you gave me is it worthy to continue because when i did the backup i wasnt rooted?
Click to expand...
Click to collapse
TWRP backup = *.tar archive
TB unpacks the needed app's data and nothing else. You must be rooted to have access on /data for restoring your apps. But for the backup process it doesn't matter if you were rooted. Root is part of your boot.img.
Kerplunk83 said:
2- i'm sure i read many time to use Titanium Backup (wich is a paid app?) i have to be rooted or have root access.
Click to expand...
Click to collapse
TB is for free. But a paid version unlocks additional features (not related to the TWRP restoring feature).
And yes... root is mandatory for TB. As I said before you must have r/w access on /data/*.
Kerplunk83 said:
if there's a chip preventing me to do so?
Click to expand...
Click to collapse
Which chip?? You already have root access via TWRP. Magisk is only needed in system and just a patched boot.img (custom kernel).
Get well soon!
WoKoschekk thank you for this insanely fast reply.
All those answers and infos have now a gigantic value for me, if only i knew that before.
To describe a bit more my situation i slept only few hours since 5 days, vomiting, heavy coughs and fever.
I'm sure i'm not supposed to but i will anyway, i engage myself and promise to reward you (in particular) and others for the help you're bringing me. It wont be much but very important to me.
I'll go try to get (again) some rest. Just before i go, why was there a mention about my device;
"
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
"
I dont ask you (WoKoschekk) or other to explain in the most explicit and endless details of what is exactly this "chip" and all the history that goes with it cause i dont want to be a pain but just why it was mentionned. Only, why?, it has ben mentionned.
I cant wait to get better since i finally see possibilities to get back those files.
Have a nice week-end and thanks again.
@Kerplunk83 To reveal the mystery behind "the chip": Motorola released two variants (Snapdragon/Mediatek CPU) of this model. Since the CPU largely determines the system structure, building a functional TWRP for both of them is very challenging. It seems that TWRP for the SD's variant got some bugs while the MT's variant runs more smooth. Due to this fact the error 255 is caused by something that you weren't be able to fix.
Regarding your problem: To restore an app and its specific app data you need the proper permissions to write in /data/data and /data/app. For this permissions you either need TWRP or Magisk installed. TWRP seems to be unable to write in that specific directory. On the other hand you don't want to install Magisk. I'm sorry but with this setup your problem can't be fixed.
Just out of curiosity, could you provide me a recovery.log showing error 255 during the restore process?
Please DO NOT copy/paste the whole log and post it here!! Instead of this you should rename the file (recovery.log => recovery.txt) because a file called *.log isn't allowed for upload. But a *.txt file is.
Options to create a recovery.log:
1. adb pull /tmp/recovery.log
=> copies a recovery.log into your ADB/fastboot folder
2. Do a backup of sth. like "boot" because the backup process will create a recovery.log by default
3. TWRP mainscreen > advanced > create log (kernel log isn't needed here)
=> log is stored on the default storage (internal or external) that you have choosen for backups etc.