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.
Related
Hi,
It's my first Android tablet... so pls be gentle.
I got the Transformer last night and I rooted it based on the guide :
[GUIDE] ROOT for ASUS eee pad transformer (TF101)
http://forum.xda-developers.com/showthread.php?t=1035197
I got it working with BLOB_V5.
But I just found out my back camera is not working (front working fine)
I think the reason is my Build number HRI66.US_epad-8.2.2.6.1-20110325.
I didnt update to the latest one which is 8329.
So, I would like to know how can I update it to 8329?
I tried just put the zip file in and ran it, then it reboots and goes into the CWM Recovery. And seems like it wont allow me to update...
So, my guess is to remove CWM and unroot it.
BUt how can I get back to the stock?
It's my first time rooting... so I am not sure what should I do next...
Thanks in advance
Bump
10 characters
I believe you have to download the official update off the asus site push the blob included in the update and run the dd command using the asus blob instead of the cwm blob
Also the easiest way to fix the camera is to just flash a rom (prime or titx) my camera and bluetooth were shot after i rooted. Flashing prime fixed and is running great
lordgodgeneral said:
I believe you have to download the official update off the asus site push the blob included in the update and run the dd command using the asus blob instead of the cwm blob
Click to expand...
Click to collapse
^This and I just did it.
Sent from my HTC Eva 4G using Tapatalk
toni8284 said:
Hi,
It's my first Android tablet... so pls be gentle.
I got the Transformer last night and I rooted it based on the guide :
[GUIDE] ROOT for ASUS eee pad transformer (TF101)
http://forum.xda-developers.com/showthread.php?t=1035197
I got it working with BLOB_V5.
But I just found out my back camera is not working (front working fine)
I think the reason is my Build number HRI66.US_epad-8.2.2.6.1-20110325.
I didnt update to the latest one which is 8329.
So, I would like to know how can I update it to 8329?
I tried just put the zip file in and ran it, then it reboots and goes into the CWM Recovery. And seems like it wont allow me to update...
So, my guess is to remove CWM and unroot it.
BUt how can I get back to the stock?
It's my first time rooting... so I am not sure what should I do next...
Thanks in advance
Click to expand...
Click to collapse
hmm... Maybe, you can try reset to default of TF101 as following step.
settings -> Privacy -> personal data -> factory data reset
Just to be clear...
lordgodgeneral said:
I believe you have to download the official update off the asus site push the blob included in the update and run the dd command using the asus blob instead of the cwm blob
Also the easiest way to fix the camera is to just flash a rom (prime or titx) my camera and bluetooth were shot after i rooted. Flashing prime fixed and is running great
Click to expand...
Click to collapse
I just want to be clear before I attempt to unroot. If I understand the above post correctly, I would modify the instructions to read:
Code:
Return to the shell from step 6 and do the following commands:
11. run “dd if=/data/local/blob of=/dev/block/mmcblk0p4″
12. reboot the device, on reboot you should see a progress bar indicating the flashing of the “blob”
That is, of course, after downloading the zip from Asus and unzipping it to get to the actual blob named "blob" and pushing that to /data/local with adb. Am I correct? And someone has done this successfully? I just want to be 100% clear.
Buee said:
I just want to be clear before I attempt to unroot. If I understand the above post correctly, I would modify the instructions to read:
Code:
Return to the shell from step 6 and do the following commands:
11. run “dd if=/data/local/blob of=/dev/block/mmcblk0p4″
12. reboot the device, on reboot you should see a progress bar indicating the flashing of the “blob”
That is, of course, after downloading the zip from Asus and unzipping it to get to the actual blob named "blob" and pushing that to /data/local with adb. Am I correct? And someone has done this successfully? I just don't want to be 100% clear.
Click to expand...
Click to collapse
Yup. That's exactly what you do.
seshmaru said:
Yup. That's exactly what you do.
Click to expand...
Click to collapse
I purchased a previously rooted transformer and wish to unroot it. This is my first android device so I have read up and done my homework and now I believe I am ready to un root the device. These questions may be redundant, but all I have to do is push the blob from the most recent asus firmware update to the transformer, and then run it as outlined in step 11? Or do I have to follow steps 6 through 11 to a T in order for it to un root properly. I am fairly sure I can disregard the steps 1-5, correct? I just need a little (lot) of clarification since I am an Android virgin so to say.
edit: deleted because it's not working
followed it to a tee and it is boot looping now what?????/
Oh No!
fullthrottleenergy said:
Yup. First thing is download the asus firmware and extract the blob and then push it to data/local
7. run “adb push blob /data/local”
This takes about 5-10 minutes as it's a pretty big file.
Once that's complete type in adb shell and you should be in root (#). then just type or copy and paste from below and reboot.
11. run “″
flashing of the “blob”
Optional but I did it. After it reboots I reset it to factory (in settings). Then I copied the Asus folder (newest firmware) and placed it on my microsd card and let it do its thing. Remember to back up anything on the internal memory as it's going to get wiped when you do a factory reset.
Click to expand...
Click to collapse
I pushed the blob with no problem then typed "adb shell" to get to root and copied and pasted "dd if=/data/local/blob of=/dev/block/mmcblk0p4" and pressed enter. Upon reboot, I saw the progress bar fill up and then the Transformer rebooted. Now it is in a continual loop where it restarts (and my windows xp recognizes it), makes a click noise, shows the EEE Pad with the ASUS below start up screen, then after about ten seconds restarts to the home screen all over again. If i try to start in recovery mode it attempts it enter it, then I get the triangle with the exclamation point in it next to the android logo. I seriously think I'm fuc*ed. I knew I shouldn't have tried this. AND I REALLY NEED HELP! please I'm begging anyone. I've only had the thing for a week!
this is how I fixed mine.
same issue.
put on your micro sd card in the root of the card the update normally found in the asus/update/ folder you download from asus. I used the .9 us update worked fine, you must then rename it to EP101_SDUPDATE make sure you leave it a zip dont change the extension make sure it is on the root of the card.
then put your card in your transformer, hold the down volume and power till it prompts you in the upper left let go and push down on the volume again, which will load the factory recovery and will begin to flash the update do not bother it. it will restart and your good.
For anyone else that wants to unroot, the step mentioned previously work, I've done it myself and my Transformer no longer has root or CWM and it kept all of my information intact. You just download the firmware from Asus, extract to the point that you get a large file (mine was ~500MB) named 'blob', push that to your SD card, run the dd command swapping out the name of the file. My dd command if section looked like this "if=/sdcard/blob" and change nothing else of that command, reboot and it'll do its thing. Not sure about the bootloops. That is the ONLY command I modified and issued, nothing else from the tutorial, just that command.
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.
Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things
Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.
Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks
What recovery are you using? I suck with adb so I got nothing on that front.
It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied
BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.
So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium
So I accidentally bricked the new Samsung Stellar and my backups got wiped during the process.
Can anyone find the stock firmware/kernel for the Samsung Stellar?
Much appreciated.
sovereign73811 said:
So I accidentally bricked the new Samsung Stellar and my backups got wiped during the process.
Can anyone find the stock firmware/kernel for the Samsung Stellar?
Much appreciated.
Click to expand...
Click to collapse
mines isnt bricked but im looking for the same thing. Deleted some stuff I shouldnt have and no getting system ui force close. Let me know if you have an luck. Ill do the same
Do you still have the stock recovery? I may be able to get into my old OS if you can get the stock recovery pulled off.
Unfortunately I'm not sure how you will extract the recovery ROM off of your phone...I'll keep looking around.
mcarrion78 said:
mines isnt bricked but im looking for the same thing. Deleted some stuff I shouldnt have and no getting system ui force close. Let me know if you have an luck. Ill do the same
Click to expand...
Click to collapse
I'm curious, have you reinstalled the pesky stock apps to see if the OS crashes would stop? There may be something to that.
Also I possibly can help you get an image but I need a recovery image. If you're still rooted, download this:
http://android.podtwo.com/romdump/
Download Terminal Emulator from the Google Play Store and then follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1771347
If I can get back into my phone by restoring the stock recovery, I may be able to get you an image that works.
Uh...OK...feel free to; it keeps the topic up fresh on the first page! lol.
Anyways I managed to theorize that a recovery is all I need....dang, looks like that's both of us now eh?
Im still rooted. im trying to figure out how to pull the recovery myself to possibly help in building CWM for the phone. I know removing some stock apps is what caysed my force close i just dont know all of the ones i deleted. I didn't think to back any of them up
I've got something up there that should help you pull out the stock recovery as well.
Romdump should work and should not brick anything so please give it a try.
sovereign73811 said:
Also I possibly can help you get an image but I need a recovery image. If you're still rooted, download this:
http://android.podtwo.com/romdump/
Download Terminal Emulator from the Google Play Store and then follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1771347
If I can get back into my phone by restoring the stock recovery, I may be able to get you an image that works.
Click to expand...
Click to collapse
used romdump and this is what i get. it leaves me a text file thats 2.46 know that cant be it
c:\SDK\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # /data/local/romdump
/data/local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
Device : IMM76D.I200VRALG4
Creating required files... cat: can't open '/proc/mtd': No such file or directory
Opening mtd table... Segmentation fault
139|[email protected]:/ #
mcarrion78 said:
used romdump and this is what i get. it leaves me a text file thats 2.46 know that cant be it
c:\SDK\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # /data/local/romdump
/data/local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
Device : IMM76D.I200VRALG4
Creating required files... cat: can't open '/proc/mtd': No such file or directory
Opening mtd table... Segmentation fault
139|[email protected]:/ #
Click to expand...
Click to collapse
That's complicated. It looks like you use ADB from your PC. I'm curious, is your phone stable enough to run the Romdump from the phone itself? You will need terminal emulator to do this.
There is also a method that just works for recovery and boot partitions (the ones I and a few others need). Take a look here and scroll down to the heading that says "Alternative Method If The Above Does Not Work:".
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
i get the same thing using terminal on my phone
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Have you looked at this link? It even has an alternate way to use romdump.
I don't know if this has anything to do with what we need for a stock ROM but here's something interesting:
http://androidforums.com/elite-all-things-root/551775-well-lets-get-ball-rolling-11.html
Again to any of you who have a rooted Samsung Stellar, please help us with a Stock ROM image!
heres the verizon stuff you were looking for
https://www.dropbox.com/sh/chkru9gi16k9ar8/G-DHp6SgnD
Thanks, although we already have that and we got a phone fixed for it...too bad not mine.
Hey did you get the message? Here I'll post it again:
OK people: here's a tip I've received from an XDA developer expert:
Quote:
a quick and dirty explanation (need root)
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/output.img
this will save the partition mmcblk0p1 to output.img
now, to determine what partitions are
on my device its:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
but you're scheme and directory structure there might be a little different, so adjust accordingly
Longer Version:
http://www.darkyrom.com/index.php?th...with-adb.8059/
yeah i got that message and i got the output.img just havent uploaded it
What were you able to extract by chance?
If you could find a recovery partition, that would be great.
even in recovery its actually loaded to RAM and not mounted (this allows you to flash to it while in recovery)
do:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name
(its msm_sdcc.1 on my device, yours may be different but it should be similar)
Click to expand...
Click to collapse
Another tip to extract and backup the stock recovery.
stock rom
hey so im reading the threads and i wanted to know some kind of update. Did people test out the stock rom yet? Any good news?
Yes, thankfully we've got them working (thanks invisiblek!) and I'll make a further update in a few hours.
Where is the thread for this at?
Has this been dropped all together? I was looking for some stock and/or stock-rooted roms for this thing. Any hope out there?
Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.
irepressed said:
Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.
Click to expand...
Click to collapse
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.
tobdaryl said:
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.
Click to expand...
Click to collapse
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!
irepressed said:
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!
Click to expand...
Click to collapse
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!
tobdaryl said:
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!
Click to expand...
Click to collapse
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.
irepressed said:
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.
Click to expand...
Click to collapse
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
http://www.mediafire.com/?tk3cifzci0vw24e
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server
tobdaryl said:
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server
Click to expand...
Click to collapse
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Ok, I just killed my adb.exe, tried the command again and that got rid of the out of date error.
But, still stuck with the "device not found".
irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
http://www.mediafire.com/?ybplc1ws8uvskhf
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.
tobdaryl said:
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.
Click to expand...
Click to collapse
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks
irepressed said:
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks
Click to expand...
Click to collapse
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.
tobdaryl said:
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.
Click to expand...
Click to collapse
Yep, that's the file I was talking about.
I now need to flash and reboot, your file is at the root of an SDcard in my TF300T, I go through the Install menu and then, can't seem to view the content of my sdcard. Tried to mount it first but can't select it either, it will simply stay on "Internal Storage".
EDIT: The RCK icon is the only one right now that boots me into something. If I try the USB icon, it just stays on that screen forever.
Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
http://www.mediafire.com/?hagehu5qu5ky6sf
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?
tobdaryl said:
Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?
Click to expand...
Click to collapse
Zips trashed, kept only the one provided in your latest answer.
No cord between PC and tablet. Still unable to click on "Using external SD" or "Mount SDCard". It simply won't let me check the box or switch the bullet.
As for using this SDcard before, yes in a PC, but no, first time in my Asus. Also tried with another one just in case and same result.
As for backups and flashable zips, I kept everything from when I did my root and rom install.
I do know that I have a backup in the Restore menu of TWRP, which seems about the time I installed it. I suppose I could simply do a restore and avoid additional headaches, but my question is, what exactly will it restore? At this point, I'm mentally prepared to go back to what I had after installing Hydro 4.1, as long as I can use the tablet ASAP.
Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!
tobdaryl said:
Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!
Click to expand...
Click to collapse
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.
irepressed said:
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.
Click to expand...
Click to collapse
Great I'm glad you are happy. I had hoped for the outcome you expressed but this works also.
You're welcome!
So I got my self this nice tab ASUS Memo Pad HD 7 (ME173x), rooted the thing as soon as I got home, removed some bloatware and then after few hours a notification for an OTA upgrade hits me (wich ofc was not available manually).
You are obviously reading this 'couse the upgrade fails, just a broken droid when it tries to flash the upgrade.
Maybe the upgrade is like of a patch (it's just 56MB) and it fails me because I have removed some (well lots actually...) of those nice installed apps?
What to do? Wait for a maybe more substantial upgrade? Look for a full factory image? Just swap the tablet with a new one claiming that "OMG doesn-t-work" (hmm and what after I root the new one, de-bloat, and an other new upgrade hits the air...).
Thanks!
I found the upgrade, wich is cached in /cache/dlpkgfile (and it's a *.zip).
If I browse it I found a lot of apps patches in system/app : would it be safe to erase just those I've disinstalled, re-zip and try to upgrade?
Well the whole upgrade has a checksum, which is not easy to recreate as the script makepatch works (I guess) with a full source / dest combo. Nor it would be simply to re-install some of the apps from market as the versions could mismatch with those provided in the base.
This means that we should need backups from a original un-upgraded device, and see if that would get through the patching.
A factory image would be useful actually.
Hey, ea_.
Sorry that I can't really help you with the update or anything, but I was wondering if you could upload that dlpkg file somewhere for me.
A friend of mine has a MeMO Pad 7 HD here, and he messed up when (improperly) installing Chainfire 3D, rendering the device soft-bricked. Now it's all cool, because I can still access the system and manipulate it, and it's rooted on top of that, so I'm still in control. The problem is as you've mentioned: those idiots at ASUS don't have any upgrade/recovery images posted, so while I am capable of restoring the stupid thing, there's absolutely nowhere [that I can see] to restore FROM!
I was hoping to find someone with a tablet like this, who could share his system files or a recovery image of some sort from which I could recover the device...
IceDrake said:
Hey, ea_.
Sorry that I can't really help you with the update or anything, but I was wondering if you could upload that dlpkg file somewhere for me.
Click to expand...
Click to collapse
Too bad: I gave back my unit yesterday for a replacement (so I could back-up the whole thing as stock) but my shop was out of stock.
They say maybe they'll get some more by 9 August.
IceDrake said:
Hey, ea_.
Sorry that I can't really help you with the update or anything, but I was wondering if you could upload that dlpkg file somewhere for me.
A friend of mine has a MeMO Pad 7 HD here, and he messed up when (improperly) installing Chainfire 3D, rendering the device soft-bricked. Now it's all cool, because I can still access the system and manipulate it, and it's rooted on top of that, so I'm still in control. The problem is as you've mentioned: those idiots at ASUS don't have any upgrade/recovery images posted, so while I am capable of restoring the stupid thing, there's absolutely nowhere [that I can see] to restore FROM!
I was hoping to find someone with a tablet like this, who could share his system files or a recovery image of some sort from which I could recover the device...
Click to expand...
Click to collapse
I have one unit. Let me know what files you need, and I'll help you out.
ericmaxman said:
I have one unit. Let me know what files you need, and I'll help you out.
Click to expand...
Click to collapse
Sweet!
Essentially, I wanted the entire /system (/system/*) so I could compare all the files and find the ones that were modified, or in the worst case: replace them all with the working ones and keep the image for future recovery.
Seeing that the /system partition here is nearly 700MB in .tar.gz form, it might be a bit cumbersome to upload, so if there's a problem with that, these seem more essential to me than the rest:
/system/bin
/system/etc
/system/lib
/system/vendor
/system/build.prop
Click to expand...
Click to collapse
Also, /system/usr seems like it may contain device-specific/personal stuff, so you might want to skip this one either way.
Many thanks!
P.S. Sorry for shamelessly hijacking and derailing the thread. The one I created is here and may be more appropriate.
2 options:
1) restore the removed "bloatware" to its original location
I had the same problem. You can check the update log on the device after the update. I believe it is in /cache/recovery/last_log and you will find the problem.
In Android 4.2 you can better disable bloatware via app manager and disable apps you don't need. Or just rename .apk to .apk.ORG in /system/app (after used stop command and then rm /data/dalvik-cache/* and reboot)
2) restore complete firmware with these tools:
http://4pda.ru/forum/index.php?showtopic=486532
Latest full firmware is ME173X_WW_user_4.2.4.06716_20130918
If you use flash_tool.exe from ULK173_20130618_2123_CSC then load scatter file (MT6589_Android_scatter_emmc.txt) from the main firmware, then flash it.
See attached picture. It is a factory reset process!
Pandawill also has a section in the forum describing flash process: http://www.pandawillforum.com/showt...er-PX2-MTK8389-Quad-Core-(update-Sep-6th-2013)