Related
All, I received my Samsung Galaxy 3 last friday and I started to play with it a little.
I googled out some of informations required but still have a few questions to ask
1. As Android has preety good SDK in place, is there a way to test my newly cooked ROM on emaulator instead of flashing it on phone directly (risking brick or sth.)
2. Knowing the kernel (2.6.32.9) - is it safe to upload some new binaries to bin directory along with liblaries (to lib of course) without touching existing ones.
3. I'm about to write an app which communicates with my server via socket. To open socket, root privileges are required. The question is - Having SuperUser in place on my phone, will I be asked for root privs or it will go to "Permission denied". Should some steps should be undertaken?
I searched this forum, but for above ones I found no answers.
Thanks in advance.
XiamUser said:
All, I received my Samsung Galaxy 3 last friday and I started to play with it a little.
I googled out some of informations required but still have a few questions to ask
1. As Android has preety good SDK in place, is there a way to test my newly cooked ROM on emaulator instead of flashing it on phone directly (risking brick or sth.)
2. Knowing the kernel (2.6.32.9) - is it safe to upload some new binaries to bin directory along with liblaries (to lib of course) without touching existing ones.
3. I'm about to write an app which communicates with my server via socket. To open socket, root privileges are required. The question is - Having SuperUser in place on my phone, will I be asked for root privs or it will go to "Permission denied". Should some steps should be undertaken?
I searched this forum, but for above ones I found no answers.
Thanks in advance.
Click to expand...
Click to collapse
1)No way, but if you don't flash the bootloader there will be no problem
2)Yes, if they're compiled for armv[5-6]
3)No idea, i did not try yet.
Thanks very much
As My desire is amoled and unbranded i don't know for sure if this tut gonna help Slcd/Branded desire user if some one with slcd or branded desire fix there brick by follow this tut please leave a comment Here.
*To work this Hole Thing Out You need to setup Adb and fastboot in your pc,if you don't know how to do it follow this nice Guide.
http://androidforums.com/desire-all-things-root/337356-faq-adb-fastboot-windows-updated-1st-june-2011-a.html
Last few days i saw lots of people having usb brick problem even after they flashed the Ruu.exe or PB99IMG.zip update via hboot that because misc.img is corrupted and they stuck on stock rom without any usb function.Few Days ago i was in the same situation and solved my problem thought i should share this Information with people who need help.
Note-If you usb bricked on s-off device then try this fastboot command to solve this
fastboot oem enableqxdm 0(unblock your sd-card)
fastboot oem eraseconfig(fix misc partition)
if above command don't work then you have to flash a ruu.exe or PB99IMG.zip file via hboot to return to stock
rom usally that fix the usb brick but some time that trick also fails,if that happen then you have to go through the process below.
If your device is branded then create a goldcard and flash a unbranded PB99IMG.ZIP cause maybe this not gonna work on branded device.
I solve my usb brick this way
after return to stock rom via PB99IMG.zip file flash via hboot(didn't fix my usb brick so i had to do the steps below)
1.i unlocked my sd card via fastboot command"fastboot oem enableqxdm 0" sd card recognized by phone and i can browse it via file explorer.
note-you can access your sdcard only via file explorer nothing else so after execute the command download a file explorer from android market.
2.then i copied the visionary+(it gave me temporary root access which is needed to work this whole thing out).
root explorer,terminal emulator apk and those usb bricked update file(image_flash,mtd0.img) to sdcard from pc via card reader and installed them.
before copy those update file on sd card i edited the mtd0.img to put correct cid n rom info via hex editor.
To find cid info
If you don't know your Cid then type this command in fastboot-fastboot oem boot this will show you info about your phone cid.when the info shows up look for‘INFOCID HTC___xxx'
To find The Rom version-Go to Settings>About phone>Software Information and note your Software Number.
3.after that i copied those update file in phone memory to copy file in phone memory you have to set permission for r/w.When open root explorer look at the top left corner you will see mount as r/o mount r/w tap on mount r/w that's it you set permission to read/write on your phone memory and copy the file in
/data/data/ folder and set permission for r/w and execute for those file via root explorer.
4.after that i simply typed this command in terminal emulator
"su
/data/data/flash_image misc /data/data/mtd0.img"
Rebooted my phone and voila usb brick is gone htc sync,usb tethering,sd card mount,charge everything is working and now i am rooted and s-off again
Note-you don't need the rageagainstthecage file which only need if you try to get root access via terminal emulator which is lengthy n complicated but with visionary+ you can get root access with 1 click and it's much easier than typing command in T.E.
If above information helps you to fix Your usb brick Please Leave a comment Here and you can also hit the Thanks button
Exiled_SouL said:
before copy those update file on sd card i edited the mtd0.img to put correct cid n rom info via hex editor.
Click to expand...
Click to collapse
how do you edited it? thx
edited it with hex editor software it included in the zip file
I know. but how exactly?
tma24 said:
I know. but how exactly?
Click to expand...
Click to collapse
when you open the mtd0 file with hex editor look for
"HTC_1xx"-your cid
"ClearAutoImage .x.xx.405.x"-your rom value
and edit those according to your cid and rom value information.
i updated the thread with some more useful info so recheck the 1st post.
Thank you very much. While my phone is fine but I'm trying to fix a friend
you welcome,if it work out please leave a reply here
of course
my translated your post in slovak forum
http://smartmobil.sk/forum/viewtopic.php?f=142&t=12610
thank you very much
Regards.
Exiled_SouL said:
you welcome,if it work out please leave a reply here
Click to expand...
Click to collapse
Yes, I fixed it!!! Thx man.
Congrats.thanks for confirming
You've made my day. You need a donate button. Thanks.
Hi, thank you very much for responding my thread, and thank's to you my desire is back to normal..., I have one question, Is it safe to use permanent root using Visionary+ ?
thank's
kebhoganteng said:
Hi, thank you very much for responding my thread, and thank's to you my desire is back to normal..., I have one question, Is it safe to use permanent root using Visionary+ ?
thank's
Click to expand...
Click to collapse
Glad that it worked out for you about V+ root,TBH i don't know but my opinion is it's safer to use unrevocked for root.
Marc. said:
I read it, but a few questions...
( My phone is S-ON )
1. I'm not on a stock rom, but on Insertcoin
2. I can already acces my SD card, so can I skip the first step? Done that yesterday already.
3. Can I use the mtd0.img generator? If yes I have already the file.
4. With step 3, which files must be in /data/data?
5. With step 2, I have super user, so can I use that instead of the root acces thing?
Click to expand...
Click to collapse
Quote from the other topic, maybe you read it here faster.
Edit, just tried it. I generated my mtd0.img out of another topic. Read a lot, and it works perfect again!! Thanks!! You saved my phone!
Exiled_SouL said:
Glad that it worked out for you about V+ root,TBH i don't know but my opinion is it's safer to use unrevocked for root.
Click to expand...
Click to collapse
Hi, again
I have a new problem after fixing the USB Brick. I can't root my desire using Unrevoked 3, it was always failed on process uninstalling unrevoked3 system and showed :
Validation error : Backup CID is Missing
do you have any idea for this problem?
thx for your respond
That same error showed up when i tried to root after usb brick but in my app drawer the super user icon showed that means it worked somehow even after the error,so check your app drawer and recovery if you see the su icon and cwm recovery then it worked don't worry about the error
Sent from my HTC Desire using XDA App
Hello,
Can I try this method on my Desire S (unrooted, s-on v2.3.5-sense3.0) ?
a great big thank you. I am very happy!
rakhan01 said:
Hello,
Can I try this method on my Desire S (unrooted, s-on v2.3.5-sense3.0) ?
Click to expand...
Click to collapse
Yes, if you want to brick your device by flashing a misc meant for another one..
Update: Updated CWM recovery.New version fixes bootloop issue
Rooting:
This technique should work on any stock firmware.
First flash CWM recovery.Instructions are given below
Boot in CWM recovery and connect phone to PC
Download and extract the RootMe.zip package on your PC
Run runme.bat on PC while phone is in recovery mode
Reboot the phone after process is over.
Clockworkmod Recovery:
Download the cwm tar package
Put phone into download mode and connect to the PC
Flash the cwm tar package as PDA and wait for phone to reboot
Recovery download link: cwm-trebon.tar.md5
Note:
[1]The yellow triangle at boot is of no importance.Deal with it
Recovery Mode: volume up+ volume down + home + power
Download Mode: volume down + home + power
Hi i had rooted my phone as mentioned in this thread,i think i have a problem now don't if its related to rooting...
I had a software update notification this morning so i downloaded it but while installing i got an error like update failed...binary mismatch, after the phone booted i tried again now it says no update available...
Is it any way related to ur method of rooting....?
Galaxy ace plus vold.fstab file
HI guys,
I am new to this forum . i have tried swap internal and external SD cards in my galaxy ace plus s7500 . unfortunately i have taken backup to sd card . After modifying /system/etc/vold.fstab phone is unable to mount both sd cards
can any one please upload original vold.fstab of galaxy ace plus plsssss .
Regards,
Appaji .P
Many thanks for the info!
appaji04cn002 said:
HI guys,
I am new to this forum . i have tried swap internal and external SD cards in my galaxy ace plus s7500 . unfortunately i have taken backup to sd card . After modifying /system/etc/vold.fstab phone is unable to mount both sd cards
can any one please upload original vold.fstab of galaxy ace plus plsssss .
Regards,
Appaji .P
Click to expand...
Click to collapse
Here you go....
mb-14 said:
This guide is for rooting the Galaxy Ace Plus GT-S7500
Please follow these instructions carefully:
Download and unzip Odin3.zip package.
Download the ROOT.tar file.
Put the phone into download mode(volume down+home+power on) and connect to the PC.
Open Odin and flash the ROOT.tar file as PDA.Wait for the phone to reboot.
Now root using DooMLoRD's Easy Rooting Toolkit available from here
Enjoy full access to your rooted phone
Click to expand...
Click to collapse
Hey!
What does ROOT.tar includes? Can this be used on other samsung phones?
qzem said:
Hey!
What does ROOT.tar includes? Can this be used on other samsung phones?
Click to expand...
Click to collapse
which model?
i think i know...maybe qzem is trying to get it work on Galaxy S Advance...
logically, it should not work, since the ROOT.tar is built based on Galaxy Ace Plus's own boot.img... however, i am very interested to know how do you manage to modify the boot.img to allow access to DooMLoRD's Easy Rooting Toolkit for rooting purposes... that might help cos i'm actually has started researching rooting methods for Samsung new phones, since i planned to buy Galaxy S Advance as well..
kilsmap said:
i think i know...maybe qzem is trying to get it work on Galaxy S Advance...
logically, it should not work, since the ROOT.tar is built based on Galaxy Ace Plus's own boot.img... however, i am very interested to know how do you manage to modify the boot.img to allow access to DooMLoRD's Easy Rooting Toolkit for rooting purposes... that might help cos i'm actually has started researching rooting methods for Samsung new phones, since i planned to buy Galaxy S Advance as well..
Click to expand...
Click to collapse
You are right, man I am searching and trying every way to root Galaxy S I9070 Advace . Ben even unpacking and repacking system.img.d5, but with no success. Problem is I don't have enaugh knowlage in this, and I don't use linux, everything I did so far was in windows in Cygwin and on the phone it self when the shell was needed. Maybe we could put our heads together and figure this thing out ! You can PM, if you have any good ideas. I was playing with a thought of installing linux vitualy, and make some enviroment for compiling this android stuff. I have some knowlage about computers since I am computer engineer, but i work as system administrator in windows based environment.
Cheers
Well the steps are very easy & it should work on any android phone not just samsung phones.
First unpack the stock boot.img of your device.
Then open the default.prop file and set
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
and save the file.
Now repack the boot image and tar it.
Then you can flash it via Odin
The changes give us root access to adb shell and we can push the su binary and Superuser.apk via adb.
But if you are lazy then run any of the available rooting tools which copy the necessary files via adb(eg Doomlord's toolkit)
whoa...quite simple...thanks bro...but i seemed to read somewhere that everytime our phone reboots, especially for Samsung phones, it will read everything back from the boot.img, so as this exploit is quite simple, will the root stick? sorry for the crudeness of the question...im quite a noob in android development as well..haha...
kilsmap said:
whoa...quite simple...thanks bro...but i seemed to read somewhere that everytime our phone reboots, especially for Samsung phones, it will read everything back from the boot.img, so as this exploit is quite simple, will the root stick? sorry for the crudeness of the question...im quite a noob in android development as well..haha...
Click to expand...
Click to collapse
If using a root browser such as root explorer i make any changes to the files in the boot partition such as init.rc or default.prop then the changes will not persist after a reboot as the phone reads everything back from the original boot.img.
But if we change the the original boot.img(that is what we are doing here) and flash it then the changes will persist.
i see...thanks for the explanation...good job with the root guide for Ace Plus...
To qzem, yeah...im quite as much noob as most of the users here in xda...but maybe we have to do this in a Linux environment, cos i read somewhere for ROM making, its quite difficult to use Windows... now for me, rooting our Galaxy S Advance is quite probable, just that learning how to use Ubuntu just for making these exploits is quite unnerving... there are quite thorough guide for unpacking and repacking those .img files, but you have to be familiar with Linux...
mb-14 said:
Well the steps are very easy & it should work on any android phone not just samsung phones.
First unpack the stock boot.img of your device.
Then open the default.prop file and set
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
and save the file.
Now repack the boot image and tar it.
Then you can flash it via Odin
The changes give us root access to adb shell and we can push the su binary and Superuser.apk via adb.
But if you are lazy then run any of the available rooting tools which copy the necessary files via adb(eg Doomlord's toolkit)
Click to expand...
Click to collapse
How to unpack and repack boot.img? Is there any useful guide here. Can I pull boot.img straight from my phone or can I extract it from firmware (.tar file) on my pc, and how? Or do I need kernel source code, to compile insecure kernel? Thanks for your help!
now i have definitely run into some confusion here...your guide in remaking the boot.img is very clear, but the problem now is that i can't figure out where is boot.img located in Galaxy S Advance firmwares...all i have are system.img, cache.img, hidden.img, kernel.bin and modem.bin... is it in the kernel.bin? if so, how do i extract it?
Im not sure but i think unpacking tools are same as boot.img.There are many guides available online
i see...how do u manage to get CWM working for Ace Plus? do we have to root 1st for flashing CWM, cos i remember that it is not necessary... what are the files we need to port CWM to other devices?
kilsmap said:
i see...how do u manage to get CWM working for Ace Plus? do we have to root 1st for flashing CWM, cos i remember that it is not necessary... what are the files we need to port CWM to other devices?
Click to expand...
Click to collapse
Check this:http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Thanks for the CWM , now all we need is some custom ROMs , hope some developers step in....
Rooting Ace Plus
I am a noob in rooting stuff,i have never used p.c for rooting,despite being with android for 2 years,
My ques is-
will my phone be rooted after flashing root.tar as PDA?
or i have to use doomlord's rooting tool kit also?(i dont know to use)
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.
I want to make the image of android phone (bit by bit image such as using dd command) without rooting the device.Can any one help me. Keep in mind I do not want to use adb pull . I am using samsung galaxy tab 3. I have used oding but dump option is disabled
zudnabukhari said:
I want to make the image of android phone (bit by bit image such as using dd command) without rooting the device.Can any one help me. Keep in mind I do not want to use adb pull . I am using samsung galaxy tab 3. I have used oding but dump option is disabled
Click to expand...
Click to collapse
Which partitions must be included? Why don't you want to use adb?