First, I apologize if I post this in the wrong forum. Mods please move it for me =D thank you.
Second, I just went through hell to have my RSA key restore and I thought I have to post this instruction right the way in hope of it will save the next person.
For some reason my RSA key were missing and I have no idea why or how. But I did backup my RSA key using RA_Recovery a while ago so this instruction is only good if you did so.
Requirements:
-Root explorer Pro (paid)
-Terminal Emulator (free)
Instructions:
1. Assume you backed up your RSA key and have wimax.img file somewhere
2. Use Root Explorer Pro to copy and paste it to your root SD folder "sdcard"
3. Download "flash_image.zip" file from here: http://wiki.cyanogenmod.com/index.php?title=Flash_image
4. Use Root Explorer Pro to extract it to your root SD folder "sdcard"
5. Then copy flash_image file itself and paste to /system/bin (you change it from R/O (Read Only) to R/W (Read Write), paste the files, then change it back it R/O.
6. Open Terminal Emulator
7. Type su
8. type flash_image wimax /sdcard/wimax.img it will reflash the rsa image key to your phone
9. Download Wimax key check from Market to verify. It should now says your key is present!
Good luck!!!
Credits:NewZJ & jesuspgt for helping me getting this done.
TommyNgo215 said:
5. Then copy flash_image file itself and paste to /system/bin (you need to change the mount to R/O then change it back to R/W)
Click to expand...
Click to collapse
Step 5 is backwards, you change it from R/O (Read Only) to R/W (Read Write), paste the files, then change it back it R/O (optional, but safer).
otherwise pretty easy to follow.
there ya go...i edited it to reflect of what you typed =D
step 8, needs .img after the /sdcard/wimax
yes lol it's been a long day..
wimaxkey location
Well f a duck my keys are missing! I have no ideas but explains why it wouldn't connect when I was near a 4g area. Where can I find my wimax keys?
thank you very much
charles
TommyNgo215 said:
First, I apologize if I post this in the wrong forum. Mods please move it for me =D thank you.
Second, I just went through hell to have my RSA key restore and I thought I have to post this instruction right the way in hope of it will save the next person.
For some reason my RSA key were missing and I have no idea why or how. But I did backup my RSA key using RA_Recovery a while ago so this instruction is only good if you did so.
Requirements:
-Root explorer Pro (paid)
-Terminal Emulator (free)
Instructions:
1. Assume you backed up your RSA key and have wimax.img file somewhere
2. Use Root Explorer Pro to copy and paste it to your root SD folder "sdcard"
3. Download "flash_image.zip" file from here: http://wiki.cyanogenmod.com/index.php?title=Flash_image
4. Use Root Explorer Pro to extract it to your root SD folder "sdcard"
5. Then copy flash_image file itself and paste to /system/bin (you change it from R/O (Read Only) to R/W (Read Write), paste the files, then change it back it R/O.
6. Open Terminal Emulator
7. Type su
8. type flash_image wimax /sdcard/wimax.img it will reflash the rsa image key to your phone
9. Download Wimax key check from Market to verify. It should now says your key is present!
Good luck!!!
Well f a duck my keys are missing! I have no ideas but explains why it wouldn't connect when I was near a 4g area. Where can I find ntt wimax keys?
thank you do much
charles
Credits:NewZJ & jesuspgt for helping me getting this done.
Click to expand...
Click to collapse
ceabbott2 said:
Well f a duck my keys are missing! I have no ideas but explains why it wouldn't connect when I was near a 4g area. Where can I find ntt wimax keys?
thank you do much
charles
Click to expand...
Click to collapse
You will have to pull them from a backup, hopefully you made one!
wimax key back up
Yellowcard8992 said:
You will have to pull them from a backup, hopefully you made one!
Click to expand...
Click to collapse
I know. I made a bunch of back ups but I don't know how long my wimax keys have been gone. Crap, I just deleted a couple of Really Old backups a bout a month ago.
Go to those backup folders and see you have wimax.img
But if you make a nandroid backup of a whole rom.I think.you can just restore that backup. It should be in there.
Sent from my PC36100 using Tapatalk
Thanks!
I could flawlessly restore my Wimax keys back. Thanks for everything!
You're welcome. Im glad you got it fixed.
Sent from my PC36100 using Tapatalk
sorry to revive an old thread, but i was wondering, if i just made a wimax only backup with amon ra, it made a folder that had the md5 and wimax.img. if i zip that and email it to myself, so if something happens, i have it saved on my email server space, would i just need to unzip it to nandroid/whatever the device id is folder and restore from there? would that hurt my regular rom or is this (terminal emulator) the only way to restore the keys?
Related
In the event something happens to your phone, -I'm- not responsible for the damages to it, you are. The end. I've personally tested this method and it works flawlessly.
This tutorial entails gaining full root access on your Evo. That means we -will- be unlocking NAND. But most importantly, we'll be doing it all without the use of a computer. Needless to say, this is going to take a while, especially if you don't have access to a wifi signal. The PC36IMG.zip files are rather hefty and are going to take at least 30 minutes to download. So I suggest you start downloading both of them now.
Prerequisites: Download Astro File Manager from the market. Open it up, hit the menu key on your phone, select more, select preferences, then scroll down and make sure Enable Browser Download is checked.
This is a template for you guys that'll explain to you how to move a file to the root of your SD card using Astro File Manager.
The files that you've downloaded from the links below are going to be located in the Downloads folder that is on the root of your SD card.
Unless you're using a browser like Xscope or Dolphin, then you'd have to navigate to the particular browser's folder that you're using, open it up and find the downloads folder in there.
When you first open the Astro File Manager app, you're going to be staring at what is the actual root of your SD card. Remember that.
Code:
When I tell you to move something to the root of your SD card, you're going to:
Locate and open the appropriate download folder that contains the file I am referring to.
Long press on the file.
Select Edit.
Select Move.
Press the Back key on your phone 'til you've reached the root of your SD card in Astro File Manager.
Click the Menu key on your phone.
Select Edit.
Select Paste.
When I tell you to rename a file you're going to:
Long press on the file.
Select Edit.
Select Rename.
Rename it accordingly and select done.
Step 1. Download this file http://link.geekfor.me/rootedromzip and move it to the root of your SD card.
Step 2. Power down your phone.
Step 3. Hold down the Volume Down and Power key simultaneously and keep holding it down until you've reached a white screen with 3 android dudes on skateboards.
Step 4. It's going to give you some options, whether or not to install the PC36IMG.zip, select yes (volume up is yes) for any prompt you get.
Step 5. Once you've rebooted you will officially have root access. Just not full root access, we still need to unlock NAND.
Step 6. Navigate to the root of your sd card and rename the PC36IMG.zip file whatever you want, doesn't matter. Just don't name it update. You can even delete it if you want.
Step 7. Download the mtd-eng.zip file here. - http://forum.xda-developers.com/attachment.php?attachmentid=342668&d=1276481802 And the flash_image.zip file here. - http://forum.xda-developers.com/attachment.php?attachmentid=342667&d=1276481776
Step 8. Navigate to the root of your SD card and locate both of the .zip files you just downloaded. Open them, and long press on the files inside of them, then select Edit, then Copy, navigate back to the root of your SD card, press menu, select Edit, and then paste. Do the same thing for both files.
Step 9. Open up the Android Market and download the terminal emulator app by Jack Palevick, it's free.
Step 10. Open the terminal emulator app and type in these commands exactly as they are written. If you get an error, try again.
Note: After each line is completed, hit enter. A # sign means you've run the commands successfully.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img[/B]
Step 11. Download the new PC36IMG.zip file here -http://sdx-downloads.com/sdx/evo/troot/eng-PC36IMG.zipand move it to the root of your SD card, then rename it to "PC36IMG.zip" because the is named eng-PC36IMG.zip, which is wrong. Then power down your phone.
Step 12.
Hold volume down and power to boot into hboot.
- It should now find and verify the PC36IMG.zip on the root of your sdcard. It'll show a blue status bar on the top right of the screen.
- After a minute or so it will ask u if u wanna flash Select YES.
- After it flashes the PC36IMG.zip it will ask if you wanna reboot. Select YES.
Click to expand...
Click to collapse
Step 13. Once your phone has rebooted, download the recovery.img file here - http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-evo-v1.7.0.1.img Then move it to the root of your SD card and rename it "recovery.img"
Step 14. Still know how to use terminal emulator? Open it up and type in these commands.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img[/B]
You now have full root access as well as a legit recovery.
If you want to flash a ROM or the newest radio and you don't know how to do that, there's already guides for that. So I won't include that in my tutorial, just click here. http://forum.xda-developers.com/showthread.php?t=710513
ALL CREDIT GOES TO THESE GUYS! toastcfh, keishou, maejrep, Paul, Amon_Ra, Koush, TheBiles, and anybody else I forgot.
PLEASE NOTE THE DONATION SUGGESTION IN MY SIGNATURE.
I must look like a douche what with the bold CAPS asking to note the donation link in my signature, which used to be a link to Dr. Cloverdale's paypal, not mine. Just thought I'd clear that up.
Reserved.
10 char
Great Work!!
Wow, great work!! Seems easy enough to me. I have a quick question as i haven't rooted yet and don't know all it entails.
First, you say after this method that we have a "legit recovery"...does that mean if i hard reboot, that there is a rooted, nand unlocked image you put there already that will flash with a hard reset? And if so, what image did you use? (or is it exactly the same as stock but rooted)
Second, some of the other quides state we need to root, then unlock, then flash a custom recovery...it looks as if you have all 3 steps included right?
Finally, is there anything else you recommend i do after i complete root using your method?? I am looking forward to maximizing this phone!!
Thanks for this guide!!! Can't wait to try it out.
adeyo said:
Wow, great work!! Seems easy enough to me. I have a quick question as i haven't rooted yet and don't know all it entails.
First, you say after this method that we have a "legit recovery"...does that mean if i hard reboot, that there is a rooted, nand unlocked image you put there already that will flash with a hard reset? And if so, what image did you use? (or is it exactly the same as stock but rooted)
Second, some of the other quides state we need to root, then unlock, then flash a custom recovery...it looks as if you have all 3 steps included right?
Finally, is there anything else you recommend i do after i complete root using your method?? I am looking forward to maximizing this phone!!
Thanks for this guide!!! Can't wait to try it out.
Click to expand...
Click to collapse
Legit, as in the most legit recovery on the scene, that being Amon_RA's.
Yup, got all three covered in that order.
Here's a link that shows you an in-depth guide on how to flash ROM's and what-have-you. http://forum.xda-developers.com/showthread.php?t=710513
No problem, man. Let me know how it goes for ya'.
Does this method still work with the latest OTA patch on 6/28/10?
Aren't you supposed to have Superuser Permissions after flashing the first ROM?
and you do get super permissions after you flash a CUSTOM rom....
what's your definition of 'CUSTOM'? This isn't my first time rooting, I unrooted lastnight and decided to try this method to see if it would work. I know for a fact that during the original rooting process the first PC36IMG you flash, you have Superuser permissions. And the second one that is flashed is the ROM to unlock NAND. However, doing this method, after flashing the first PC36IMG, I do not have Superuser permissions
However, it does seem that this method works. So I'm happy. It's good to know that I don't have to rely on a computer to root my phone now. Now the only thing I need to do, is figure out how to UNroot my phone without a computer.
Android believer, did you update to the ota update yesterday? Do you know if this works with the ota v1.47.651.1?
Sent from my Evo using XDA App
gordon1hd1 said:
Does this method still work with the latest OTA patch on 6/28/10?
Click to expand...
Click to collapse
I would assume it doesn't, as this is still toastcfh's method of rooting except it's done without a computer.
@ neckface
Hope you're not tired of hearing from me. First, thanks mass for this.
You say this is Toasts method without computer. I'm on the orig stock ROM, no 1.47 update. I WANT to do the update (for better battery mainly). I want to do whitslacks method. He says you need eng hboot 76.2000. He says use Toasts part 2 to get that.
Should I : use this to get eng hboot, then go to whitslacks for the 1.47 update? You seem to have a pretty good grip on this, so I thought I'd ask your opinion.
(if this is still Toastcfhs method, are these links to the same files he has posted? Meaning, will this get me eng-Hboot 76.2000? )
Thanks a lot.
anybody
Really interested in this. Anyone have success with this from 1.32 SW, and does it give you hboot 76.2000 ?
Thanks in advance.
Scott
OK i must be the dumb one
I have already used the "Unrevoked method" so I thought I could just skip to the Nand unlock. Now the phone(EVO) will not allow me access to my sdCard...and..will not read when I plug it up to my USB PC(windows) instead of it coming up as android like it use to it comes up as Qualcomm CDMA Technologies MSM(new found hardware wizard)....and the phone can only charge when the phone is powered off. Its like the usb is not responding and I can not have access to the SD card via teh device..i need advice
Thank you
Thank you,
I don't know if it was the wrong recovery.img or what, but I could not do a nand unlock. This worked great and did it all off the phone..... Awsome
Hi,
I tried to copy an API to /system/app, but when I did that, the screen just blinks, and the file is not pasted into the directory.
I had temp root, and had remounted R/W.
I eventually was able to do the copy by using ES Explorer, but not with RE itself.
Does anyone have any idea what might be wrong?
Thanks,
Jim
Don't know if this helps but... I recently tried to do some copying of files using AndRootFile, and RootExplorer. And like you they did not "take". I finally figured out that after I selected a file to copy, I would use the back arrow button to move to the target folder. This was the problem. When I used the Parent folder icon instead to move back out of the folder, and move to the destination folder without using the back arrow button. the file copied just fine. Hope this helps.
Reggie,
Thanks for the suggestion, but, no, I wasn't using the "back" to get to the /system/app directory. I was clicking on the parent dir, etc.
Jim
I also am having that problem. I tried both the back buttons and the parent directory. Ive tried factor data reset as well. I wander if it has anything to do with the update yesterday?
Until we/someone figures why, you can use root explorer to mount, then the built in es explorer to do the copy...
Jim
I've been doing some stuff w/command line, and I noticed that my stock Gtab doesn't have a native 'cp' command, so you have to use 'busybox cp' instead. I wonder if that's why the RE copy/paste doesn't work?
Jim
SOLVED - it was no native 'cp'
jimcpl said:
I've been doing some stuff w/command line, and I noticed that my stock Gtab doesn't have a native Cp command, so you have to use 'busybox cop's instead. I wonder if that's why the RE copynpasre doesn't work?
Jim
Click to expand...
Click to collapse
Hi,
I just tried a test, where I created a softlink for 'busybox cp':
ln -s /system/bin/busybox /sbin/cp
I then was able to use RE to copy/paste into /system/app !
CAVEAT: I don't know if busybox is on Gtab by default...
Jim
At the command line us cp vs Cp. If you want to copy an entire directory, use cp -R /indirectory /outdirectory .
NMCBR600 said:
At the command line us cp vs Cp. If you want to copy an entire directory, use cp -R /indirectory /outdirectory .
Click to expand...
Click to collapse
Hi,
That was a typo on my part. The 'cp' command (lowercase c) was really missing in my Gtab .
I've been experimenting w/alternate keyboards, and keep making typos ...
Jim
P.S. I fixed the typos ...
jimcpl,
I was just working on putting Market onto my stock machine and I am having the exact same problem. So far as I can see I have set it up right and followed procedure -- but files just won't move.
Now that I have read y'all's comments, I will try again a time or two.
Rev
butchconner said:
jimcpl,
I was just working on putting Market onto my stock machine and I am having the exact same problem. So far as I can see I have set it up right and followed procedure -- but files just won't move.
Now that I have read y'all's comments, I will try again a time or two.
Rev
Click to expand...
Click to collapse
Hi,
BTW, to create the softlink (using ln), you'll need to use adb shell. Or, you could use a terminal, if one's installed (kind of catch 22, since you'd need market to get a terminal).
Otherwise, what might work is:
- z4root to get root
- root explorer to make /system R/W
- kill then restart es file explorer and use that to copy the apks to /system/app
Jim
SIGH ... softlink doesn't survive a reboot
It looks like the softlink that I created disappears after a reboot... then RE can't copy again.
Sorry...
Jim
Hi,
Can anyone point me in the right direction.
I am looking for the default Inspire 4G at&t boot animation. Would like to put that on my Inspire.
I am currently running CM7 Gingerbread and I'm just not fond of that boot animation.
Thanks in advance.
Search in these threads. I have already posted it for someone else.
Edit: I actually found it quickly so here is the link.
http://forum.xda-developers.com/showthread.php?t=1032720
Wolf_2 said:
Search in these threads. I have already posted it for someone else.
Edit: I actually found it quickly so here is the link.
http://forum.xda-developers.com/showthread.php?t=1032720
Click to expand...
Click to collapse
Thanks for the reply.
I have actually downloaded yours and tried to flash it in CWM. It didn't work. Maybe because I'm on Gingerbread. Any suggestions?
It will not flash through CWM. You need to use a program such as Root Explorer to copy and paste it into the default location which is usually System/Customize/Resource.
Wolf_2 said:
It will not flash through CWM. You need to use a program such as Root Explorer to copy and paste it into the default location which is usually System/Customize/Resource.
Click to expand...
Click to collapse
Thanks!
I found big lou's guide and it worked.
Just used the command: adb push bootanimation.zip /data/local
You can change the bootanimation anytime you like. First, the file has to actually *be* a bootanimation. All you do is place the bootanimation.zip - it must read EXACTLY that way, bootanimation.zip - onto the root of your SD Card. That means, it shouldn't be in a folder or anything. Next using Root Explorer (make sure you have read/write ability (there's a button at the top of the display, when you first open Root Explorer which reads R/O. Push it once, and it changes to R/W, meaning that you have Read/Write permissions). Next go to the SD Card, find the bootanimation.zip that you placed there earlier and long-press on it. This brings up a menu with several choices, I always choose Copy. That copies the bootanimation, and you then back up one level to the first screen you saw, when you chose R/W. Scroll down a little until you find "data", and click on it to open it. Scroll down again until you come to a file called "local", and open it. There should be two or three things in view (a largely empty folder) and that is the place that you push the button saying "Paste". Once it pastes the bootanimation there, back out of Root Explorer, reboot your phone and you should now have your new bootanimation displaying.
-Mike
Ultra Droid said:
You can change the bootanimation anytime you like. First, the file has to actually *be* a bootanimation. All you do is place the bootanimation.zip - it must read EXACTLY that way, bootanimation.zip - onto the root of your SD Card. That means, it shouldn't be in a folder or anything. Next using Root Explorer (make sure you have read/write ability (there's a button at the top of the display, when you first open Root Explorer which reads R/O. Push it once, and it changes to R/W, meaning that you have Read/Write permissions). Next go to the SD Card, find the bootanimation.zip that you placed there earlier and long-press on it. This brings up a menu with several choices, I always choose Copy. That copies the bootanimation, and you then back up one level to the first screen you saw, when you chose R/W. Scroll down a little until you find "data", and click on it to open it. Scroll down again until you come to a file called "local", and open it. There should be two or three things in view (a largely empty folder) and that is the place that you push the button saying "Paste". Once it pastes the bootanimation there, back out of Root Explorer, reboot your phone and you should now have your new bootanimation displaying.
-Mike
Click to expand...
Click to collapse
Thanks for the response, I'll keep that in mind to try next time. I did get it to work without going into root explorer.
Fiasco said:
Thanks for the response, I'll keep that in mind to try next time. I did get it to work without going into root explorer.
Click to expand...
Click to collapse
Good - the important thing is you resolved you problem!
-Mike
yesssss Thank you..!! XD
So, I just flashed the serendipity 7 ROM to my phone today, I love it. It's fast and doesn't drain the battery. Infused seem to drain the battery quickly.
Anyway, the power button to take a picture seemed to work this morning, now it doesn't. Is there some way to get it working again? I have installed lots of apps, but I don't think any of them mess with the camera. I installed the samsung quick office, music, clock and video player. (I downloaded the 4, not sure if I installed all of them.) I used the Android Sideload Wonder Machine, not sure if that is the source of the problem or not. Any help would be appreciated.
The power button doesn't work to take pictures in S7. I remember reading this somewhere and can verify it didn't work for me after flashing S7. What I did to get it working is:
(FIRST, make a nandroid backup just in case!!)
1. Using your favorite file explorer (Root Explorer for me), go to the system/app folder on your phone
2. Mount the directory as R/W.
3. Rename the camera.apk in this folder to something like camera.apk.bak
4. Find a copy of the Infused v2 ROM, unzip it, go to system/app, and copy that camera.apk.
5. Go back to the system/app folder on your phone, make sure it's still mounted as R/W, and paste the Infused camera.apk into the directory.
6. Change the permissions on the camera.apk to match the permissions of the original camera.apk.
7. Next, mount the system/app folder on your phone as R/O.
8. You may have to delete and remake any shortcuts to the camera app you have on your home screens.
This worked for me and has worked perfectly all day, but I've only used it for a day. I won't swear that it won't mess something up in the future. I have taken approx. 10 photos since changing this with no problems, but you never know. Make a nandroid backup just in case, and save the camera.apk.bak in case it does FUBAR something.
PS: I wrote this as if you're a total noob. If you're not, I apologize. Wasn't trying to be condescending, just thorough. lol
02ranger said:
The power button doesn't work to take pictures in S7. I remember reading this somewhere and can verify it didn't work for me after flashing S7. What I did to get it working is:
(FIRST, make a nandroid backup just in case!!)
1. Using your favorite file explorer (Root Explorer for me), go to the system/app folder on your phone
2. Mount the directory as R/W.
3. Rename the camera.apk in this folder to something like camera.apk.bak
4. Find a copy of the Infused v2 ROM, unzip it, go to system/app, and copy that camera.apk.
5. Go back to the system/app folder on your phone, make sure it's still mounted as R/W, and paste the Infused camera.apk into the directory.
6. Change the permissions on the camera.apk to match the permissions of the original camera.apk.
7. Next, mount the system/app folder on your phone as R/O.
8. You may have to delete and remake any shortcuts to the camera app you have on your home screens.
This worked for me and has worked perfectly all day, but I've only used it for a day. I won't swear that it won't mess something up in the future. I have taken approx. 10 photos since changing this with no problems, but you never know. Make a nandroid backup just in case, and save the camera.apk.bak in case it does FUBAR something.
PS: I wrote this as if you're a total noob. If you're not, I apologize. Wasn't trying to be condescending, just thorough. lol
Click to expand...
Click to collapse
Thank you, your explanation makes sense, and I am a total newbc lol. I'll do it tonight. Thanks!
Sent from my SGH-I997 using Tapatalk
How do I change the permissions?
Sent from my SGH-I997 using Tapatalk
If you have root explorer just long press on the file. It should have an option for permissions. The folder that the app is in has to be mounted as R/W to be able to change the permissions. I don't know specifically how to do it in other file managers. If you don't have root explorer yet, it is definitely worth getting. It's the best file manager I've used.
The exact permissions you need to set are:
All 3 rows should have Read checked, only the "Owner" should have Write checked, and nobody should have Execute checked. Make sure the file is already pasted into the system/app folder before you try to change permissions.
02ranger said:
If you have root explorer just long press on the file. It should have an option for permissions. The folder that the app is in has to be mounted as R/W to be able to change the permissions. I don't know specifically how to do it in other file managers. If you don't have root explorer yet, it is definitely worth getting. It's the best file manager I've used.
The exact permissions you need to set are:
All 3 rows should have Read checked, only the "Owner" should have Write checked, and nobody should have Execute checked. Make sure the file is already pasted into the system/app folder before you try to change permissions.
Click to expand...
Click to collapse
Thank you for all your help! It's working just fine. My icon disappeared automatically and I just had to bring it back to the front screen, no problem. Thanks!
steadly2004 said:
Thank you for all your help! It's working just fine. My icon disappeared automatically and I just had to bring it back to the front screen, no problem. Thanks!
Click to expand...
Click to collapse
Yes sir. Happy I could help.
Is it true you lose front camera functionality and HDMI out with S7? :S
***MUNKY-TOOL***
IS AN ONBOARD ANDROID UTILITY
FEATURES
[*]Copy system.img
[*]Copy boot.img
[*]Backup efs
[*]Logcat
[*]Backup and Restore Contacts
[*]Out For A Rip
Munky-tool will locate and copy most partitions without you having to track down paths. This is convenient if you use a ROM kitchen, or just want to make a backup of your system without using custom recovery. Some devices do have weird partition names, and munky-tool will not find them. If this happens to you, run the following command in terminal emulator
Code:
ls /dev/block/platform/*/by-name
Paste the output and your device name in the comments, and I will work your device in if possible.
INSTRUCTIONS
Download zip or clone git
Place extracted munky-tool folder in system partition (must be able to set permissions)
Set permissions of munky-tool script (not the directory) to at least 775 (rwx rwx rw)
Open terminal emulator and key in 'su' for root permissions
cd to the munky-tool directory
Type ./munky-tool to execute the script and start the utility
DOWNLOAD
github
Dude once again you're creativity and hard work is paying off. Great job man
Style point for the rip bud!
Sounds very helpfull and as markbencze already replyed I gues it's working on the O+O too. Have to try it in the next days.
thx markbencze for sharing.
SaschaKH said:
Sounds very helpfull and as markbencze already replyed I gues it's working on the O+O too. Have to try it in the next days.
thx markbencze for sharing.
Click to expand...
Click to collapse
Yes. I tested it on my OPO. It went out for a rip. It will run on any device, and it will find the partitions on most.
Where's the download link dude, i'm not find download link from github ?
itsnie said:
Where's the download link dude, i'm not find download link from github ?
Click to expand...
Click to collapse
On the right side of page near the clone url, there should be a button that says download as zip.
Just realized you have to be in desktop view to see the download as zip button. I will post an additional link a little later.
Just added backup and restore contacts.
N-i-c-e!
Thank you.
I've been working on the same sort of thing, and trying to figure out how to get adb connected to the phone with debugging off, for those people (I won't use the word I'm thinking of) who don't make backups, then break the screen, or bootloop the phone. Your script makes finding the data partition trivial, but I'm still working on the "force debugging on from outside" part.
But munky is going to be part of my phone from now on.
Rukbat said:
N-i-c-e!
Thank you.
I've been working on the same sort of thing, and trying to figure out how to get adb connected to the phone with debugging off, for those people (I won't use the word I'm thinking of) who don't make backups, then break the screen, or bootloop the phone. Your script makes finding the data partition trivial, but I'm still working on the "force debugging on from outside" part.
But munky is going to be part of my phone from now on.
Click to expand...
Click to collapse
Thanks, man. Glad to hear you like it.
mike the inkman said:
***MUNKY-TOOL***
IS AN ONBOARD ANDROID UTILITY
FEATURES
[*]Copy system.img
[*]Copy boot.img
[*]Backup efs
[*]Logcat
[*]Backup and Restore Contacts
[*]Out For A Rip
Munky-tool will locate and copy most partitions without you having to track down paths. This is convenient if you use a ROM kitchen, or just want to make a backup of your system without using custom recovery. Some devices do have weird partition names, and munky-tool will not find them. If this happens to you, run the following command in terminal emulator
Code:
ls /dev/block/platform/*/by-name
Paste the output and your device name in the comments, and I will work your device in if possible.
INSTRUCTIONS
Download zip or clone git
Place extracted munky-tool folder in system partition (must be able to set permissions)
Set permissions of munky-tool script (not the directory) to at least 775 (rwx rwx rw)
Open terminal emulator and key in 'su' for root permissions
cd to the munky-tool directory
Type ./munky-tool to execute the script and start the utility
DOWNLOAD
github
Click to expand...
Click to collapse
Good Tool, do you already plan to support restore EFS? which make a full loop of running time change the EFS setting without a PC,
this can help to me to control the modem band preset selections for network testing purpose.
Azlun said:
Good Tool, do you already plan to support restore EFS? which make a full loop of running time change the EFS setting without a PC,
this can help to me to control the modem band preset selections for network testing purpose.
Click to expand...
Click to collapse
It is usually done in bootloader, but I am pretty sure I can make it work. Just need to test it before I release it. I am also going to release this as an apk soon. (Don't know how soon, but I probably won't have time for a few weeks)
An app that we can point new users to that will back up their userdata partition? Fantastic!
Rukbat said:
An app that we can point new users to that will back up their userdata partition? Fantastic!
Click to expand...
Click to collapse
Yeah, I think it will fill a need. I am going to do an APK to do the things from this script, and a corresponding GUI Linux package for APK modding, and maybe do something for Windows as I get time. In the process of moving somewhat unexpectedly, so it is taking longer than I would have liked.