IMEI Backup - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Is it possible just to open a file manager and go to /system/ and copy efs.bin file to extSdCard?
Also is there an app that may do this or an actual backup, I tried 5IromToolBox hoping it works if anything ever happens.

All you need is here
http://forum.xda-developers.com/showthread.php?t=1801997
[FIX/TOOL] Backup/Restore/Fix IMEI & Data Restore Tool v3.0 - Updated 11/01/2012!!!

jethro650 said:
All you need is here
http://forum.xda-developers.com/showthread.php?t=1801997
[FIX/TOOL] Backup/Restore/Fix IMEI & Data Restore Tool v3.0 - Updated 11/01/2012!!!
Click to expand...
Click to collapse
Idk how to do it for AOSP roms,

check out the second post in that thread. I just did it last night running CM10. it's a bit harder but it works. just enter the commands one by one in the terminal. any questions ask in the thread. The OP is very helpful.

Yes, second post, I did mine while running task and ktoonsez aokp.

I don't understand what it means by eject first. Eject before what and if I eject then adb command won't work
Sent from my SGH-I747 using Tapatalk 2

tehsprayer said:
I don't understand what it means by eject first. Eject before what and if I eject then adb command won't work
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I think it simply means unhook your phone from your computer. When you run the first script it changes how your computer recognizes your phone. I don't think adb will work properly after running it(not sure here). So you will have to run the second script through terminal emulator. What I did was run the first script through terminal emulator (free on play store) then did the back up, unhooked from my computer then ran the second script from terminal emulator....done.

Related

[Q] Bricked my galaxy s3 while editing the build.prop Please Help!

I have a major problem but i think there is a way to fix it, i just cant figure it out. i was adding google wallet on my rooted s3 and when reverting the build.prop file to its original form, i just copied and pasted the backup and renamed it to the original build.prop to replace the new one using root explorer. my phone does not boot up now i get the samsung startup screen and it shuts off. i could get into cwm recovery mode. any way to fix the build.prop without being able to fully boot the phone? i am on a mac but i could have access to a pc tomorrow if i need.
Its simple if u have a backup. I have not heard of anyway of getting to build.prop thru recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
You need to restore from backup (nandroid) or start over if you don't have a backup..
Did you copy the original file to ur sd card then back over?
Chances are you did.. I did the same thing lol.. And when u do that it doesn't save original permissions of the file.
The reason the wallet post says to use root explorer is because it saves the file in the same folder permissions and all and you can just rename it back.
Sorry dude u are sol.. Restore from back up or flash a new rom and start over.
Sent from my SAMSUNG-SGH-I747 using xda premium
Get into recovery, do a factory reset.
mrhaley30705 said:
Get into recovery, do a factory reset.
Click to expand...
Click to collapse
Any resolution. I have the same problem.
mrhaley30705 said:
Get into recovery, do a factory reset.
Click to expand...
Click to collapse
I don't think that would work, as far as I know a factory reset only wipes data and cache. The build.prop is part of the system, so it will not change.
Sent from my SPH-D710 using xda premium
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Side note--> twrp recovery has a built in terminal and the ability to copy/paste files from internal and external SD cards. Not so sure about changing permissions easily....but through the built in terminal....might be able to load what you need (plus twrp flashable found in android dev forum) on external SD card with an adapter on a computer. Flash twrp and transfer files or use built in terminal to change perms. Good luck....
I know editing build props with es file explorer will cause That.
Sent from my SAMSUNG-SGH-I747 using xda premium
Fixed it!
Thanks everyone for your help, i feel like an idiot for not replying to anyone i didnt have it set up to notify me of replies, i figured out it was the build prop that was messed up, im not sure how this worked but i figured i would try to root again and flash the root files using the simple root steps using odin and it actually fixed the file and booted up fine! i appreciate everyones help and hope this thread helps other people because i know many people screw this up the same way i did. (i will never do anything like this without doing a nandroid backup again). THANKS AGAIN!
thanks but..
ibanezbass said:
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Click to expand...
Click to collapse
So the problem with this route was that for some reason the device was not being recognized by adb, i dont know why, i thought it was a driver issue but once i fixed the phone, i was able to get adb access, so i guess that boot error was preventing it from getting recognized (which i didnt understand because my friend screwed up like me the next day and was able to adb.) but finally fixed it a few days later after trying many things and the fix for some reason was a simple process with odin, i think this article shows what i did, i dont remember exactly tho - http://smartphonefix.blogspot.com/2...r-Recover-Bricked-ATT-Galaxy-S3-SGH-I747.html
ibanezbass said:
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Click to expand...
Click to collapse
Okay, I got the adb shell to run, but I run into this snag:
"Unable to chmod build.prop: Operation not permitted"
Anyone know what this means?
prior to running that command, type su then hit enter
If I made a CWM flashable unedited build.prop from a stock SGS3 rom would that help anyone? It just seems easier than all those ADB commands assuming you can still access recovery.
stratatak7 said:
If I made a CWM flashable unedited build.prop from a stock SGS3 rom would that help anyone? It just seems easier than all those ADB commands assuming you can still access recovery.
Click to expand...
Click to collapse
I'm sure that'll probably helpful to a lot of people. Unfortunately, I'm using the stock recovery so it probably wouldn't help me...
lyrictenor1 said:
I'm sure that'll probably helpful to a lot of people. Unfortunately, I'm using the stock recovery so it probably wouldn't help me...
Click to expand...
Click to collapse
If you're not comfortable with ADB: You should try to flash recovery (recommended TWRP but at this point take anything you can get) from ODIN. I know I've seen it around here somewhere. Once you do that, then flash the attached file.
This will flash in CWM/TWRP etc. I haven't tested it, so send me a PM if it doesn't work and I'll fix it up.
Edit: I've located the proper recovery file for you to flash. It's cwm, but you flash this with ODIN. Download it from here http://k0nane.info/rom/ecm/CWM-Recovery-LTE-SGS3-v5.tar.md5 . ODIN will increase your flash counter, but Chainfire's Triangle Away app takes care of that like it never happened. Odin can be found in the development thread. If you want to automate this process even further just download the qcom toolkit which walks you through the process of installing recovery. I hope this helps.
Lastly, here's the latest TWRP image file with ADB instructions. Short, sweet and simple. http://teamw.in/project/twrp2/104
crammer04 said:
I have a major problem but i think there is a way to fix it, i just cant figure it out. i was adding google wallet on my rooted s3 and when reverting the build.prop file to its original form, i just copied and pasted the backup and renamed it to the original build.prop to replace the new one using root explorer. my phone does not boot up now i get the samsung startup screen and it shuts off. i could get into cwm recovery mode. any way to fix the build.prop without being able to fully boot the phone? i am on a mac but i could have access to a pc tomorrow if i need.
Click to expand...
Click to collapse
_________________________________________________________________________________________________________________
If you got no back up give us your phone information one of us can send you one I have aTT D2att you
?
Its all in my sig get mobile odin bellow, get the tar for which ever recovery you got. I got all three. CWM, CWM Touch and TWRP for d2att (only) if different phone then use other ones.
Thats my build prop im D2att SG3 ok so just make sure. But you can grab mobile odin bellow and fix it.
_________________________________________
Just get mobile odin HERE
and flash your reocvery there CWM, TWRP, CWM TOUCH... all of them latest all in my sig bro
Here is all drop box to get any of the recoverys --------------------> Recoverys Drop Box
Get mobile odin Here along with the s3 kernal extension its all in here -----------------------> Mobile Odin
If you get hardware id missing error install these old samsung dricers this is a bonus, don't update it ----------------> Hardware ID samsung driver fix
__________________________________________________________
S3 build prop here --------------> here
Mobile odin is simple if download zip in my drop box just install it (or get it form market) download the driver you need (in my drop box) or go mobile odin thread and find it if your on a different phone. Rest is simple just load what your going to flash click the OPEN FILE option in mobile odin click tar and run it.
_________________________________________________________
Get android comander. You can mod build prop easy with it its nice GUI for installing programs or uninstalling or backups or moving files around. awesome try out here --------------------------------> ANDROID COMANDER
need anything else?
---------- Post added at 09:42 PM ---------- Previous post was at 09:20 PM ----------
lyrictenor1 said:
Okay, I got the adb shell to run, but I run into this snag:
"Unable to chmod build.prop: Operation not permitted"
Anyone know what this means?
Click to expand...
Click to collapse
Tiy need to remount system Read Write i don't think its a SU problem it could be but normaly you already got su i forget comand in adv its mount system -r i beleive. I dunno I run a script that mounts it for me let me check it out real fast
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
crammer04 said:
So the problem with this route was that for some reason the device was not being recognized by adb, i dont know why, i thought it was a driver issue but once i fixed the phone, i was able to get adb access, so i guess that boot error was preventing it from getting recognized (which i didnt understand because my friend screwed up like me the next day and was able to adb.) but finally fixed it a few days later after trying many things and the fix for some reason was a simple process with odin, i think this article shows what i did, i dont remember exactly tho - http://smartphonefix.blogspot.com/2...r-Recover-Bricked-ATT-Galaxy-S3-SGH-I747.html
Click to expand...
Click to collapse
Just so you no a common problem when doing commands you forget to do it just trying help didn't know fixed
#!/system/bin/sh
busybox mount -o remount,rw /system
My build.prop got messed up while trying to install Google Wallet on my rooted sg3 and my phone became soft bricked. I had to reinstall the stock jellybean ROM with root that I had been running before this happened, through Odin. Solved my problem. Never got wallet to work though.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Would this work on S3 T-Mobile T-999?
stratatak7 said:
If you're not comfortable with ADB: You should try to flash recovery (recommended TWRP but at this point take anything you can get) from ODIN. I know I've seen it around here somewhere. Once you do that, then flash the attached file.
This will flash in CWM/TWRP etc. I haven't tested it, so send me a PM if it doesn't work and I'll fix it up.
Edit: I've located the proper recovery file for you to flash. It's cwm, but you flash this with ODIN. Download it from here http://k0nane.info/rom/ecm/CWM-Recovery-LTE-SGS3-v5.tar.md5 . ODIN will increase your flash counter, but Chainfire's Triangle Away app takes care of that like it never happened. Odin can be found in the development thread. If you want to automate this process even further just download the qcom toolkit which walks you through the process of installing recovery. I hope this helps.
Lastly, here's the latest TWRP image file with ADB instructions. Short, sweet and simple. http://teamw.in/project/twrp2/104
Click to expand...
Click to collapse
I am having the same problem.... as the person above... Will this .Tar file below work for S3 T-Mobile T-999? Can you make one for that phone?
Thanks for your help!!
Boosoth1st said:
I am having the same problem.... as the person above... Will this .Tar file below work for S3 T-Mobile T-999? Can you make one for that phone?
Thanks for your help!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1746682
Try downloading the toolkit from there. It should contain the necessary T-Mobile files. If you are having an issue, please PM me. Make sure you flash the right one! Be careful and read the whole thread.

[Q] Help with bootlooping WFS - CM7

I put CM7 on my daughter's Wildfire S a year ago, and everything has been fine until now - and it just bootloops on the CM7 animation.
I have tried wiping dalvik & cache, fixing permissions in CWM, reflashing CM7 (the version from last year - cm-7-20120717-UNOFFICIAL-marvel.zip) and gapps. Nothing helps. Any ideas please, before I try a full wipe? I am trying to avoid that since she has no backups...
fjuniper said:
I put CM7 on my daughter's Wildfire S a year ago, and everything has been fine until now - and it just bootloops on the CM7 animation.
I have tried wiping dalvik & cache, fixing permissions in CWM, reflashing CM7 (the version from last year - cm-7-20120717-UNOFFICIAL-marvel.zip) and gapps. Nothing helps. Any ideas please, before I try a full wipe? I am trying to avoid that since she has no backups...
Click to expand...
Click to collapse
Try flashing the latest version, it'll have less bugs anyway. I don't think you absolutely need to wipe when updating a ROM but it would probably be advisable.You can try this however.
-Download the Android Debug Bridge (adb) from Google's site onto your computer.
-Plug your phone into the computer and open the Terminal Emulator.
-Type cmd in the little window that appears and press enter.
-Navigate to the folder that you downloaded ADB to. (Example: cd C:\Users\Guest\Downloads\platform-tools )
-Type "adb backup" without the quotes to take a copy of your phone's data onto the computer.
-Now you can safely do whatever you want.
99Aaron99 said:
Try flashing the latest version, it'll have less bugs anyway. I don't think you absolutely need to wipe when updating a ROM but it would probably be advisable.You can try this however.
-Download the Android Debug Bridge (adb) from Google's site onto your computer.
-Plug your phone into the computer and open the Terminal Emulator.
-Type cmd in the little window that appears and press enter.
-Navigate to the folder that you downloaded ADB to. (Example: cd C:\Users\Guest\Downloads\platform-tools )
-Type "adb backup" without the quotes to take a copy of your phone's data onto the computer.
-Now you can safely do whatever you want.
Click to expand...
Click to collapse
Thanks. That is the latest version of the ROM unfortunately - old ROM on an old phone now.... If I go to e.g. CM10, I will have to do a full wipe anyway.
I have ADB already installed. It does respond to ADB commands like adb reboot, but using adb backup just results in the full set of commands being listed i.e. it doesn't know what to do. Are there other parameters to use? backup isn't in the list presented.
...
I found a suggestion to use
adb backup –apk –shared –all –f /backup/mybackup.ab
But I just get the response
adb: unable to connect for backup
fjuniper said:
Thanks. That is the latest version of the ROM unfortunately - old ROM on an old phone now.... If I go to e.g. CM10, I will have to do a full wipe anyway.
I have ADB already installed. It does respond to ADB commands like adb reboot, but using adb backup just results in the full set of commands being listed i.e. it doesn't know what to do. Are there other parameters to use? backup isn't in the list presented.
...
I found a suggestion to use
adb backup –apk –shared –all –f /backup/mybackup.ab
But I just get the response
adb: unable to connect for backup
Click to expand...
Click to collapse
I'll be honest, I've never used that command before. I just know how it works, I took a Nandroid backup when I first rooted my phone so have never needed it. I can't really help from this point on.. However if your phone will boot into recovery, assuming you have ClockWorkMod installed you can do a backup through that.
99Aaron99 said:
I'll be honest, I've never used that command before. I just know how it works, I took a Nandroid backup when I first rooted my phone so have never needed it. I can't really help from this point on.. However if your phone will boot into recovery, assuming you have ClockWorkMod installed you can do a backup through that.
Click to expand...
Click to collapse
Hi, I was hoping to do an app+data kind of backup like Titanium. I did take a nandroid in CMW and then restored it, but it perfectly reproduced the bootloop behaviour haha. In the end I did a full wipe and told my daughter that she needed to start from scratch. 14 year olds are more pragmatic that I would be - she was just grateful she had her phone back and could get on FB. Google restored her contacts, which is the main thing. So all sorted, but the bootloop cause remains a mystery...

Need instuctions for ADB pull cracked screen

i have an e4gt screen cracked and i need to get internal sd card data. i have done several searches and have come across ADB pull but not clear on how to perform this. i am rooted w stock 4.1 using whatever recovery came with the stock+rooted ROM. (SPH-D710_GB27_1014481_Rooted_Nodata.tar.md5 from Rwilco12's Android Repository). If I could just remember the exact steps to mount usb from recovery i would be good lol... any suggestions would be greatly appreciated!
Ive the same problem if someone would help.
Sent from my GT-I9300 using xda premium
No need. Just power up your device and connect to your pc. It will connect using mtp and allow you to access your files that way (as long as you hadn't deactivated it prior to cracking your screen.)
Sent from my SPH-D710 using Tapatalk 2
There's a way to get your screen to pc...
Sent from my GT-I9300 using xda premium
hlxanthus said:
No need. Just power up your device and connect to your pc. It will connect using mtp and allow you to access your files that way (as long as you hadn't deactivated it prior to cracking your screen.)
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
i have done that and i get a box that says "there was a problem installing this MTP device." then another box says MTP was not installed correctly. Well i do have the Samsung drivers installed. Even installed a fresh copy direct from samsung support. Maybe something to do with my screen being locked with pin? Just got the Galaxy4 cant wait to get my data back...lol
Okay, assuming you already have android SDK set up and working ( you get adb this way), flash a recovery. I would likely use the direct boot for simplicity.
http://www.rwilco12.com/downloads.p...overy Kernels/GB/Noobnl Direct Boot/One-Click
That is for the one click version of the direct boot kernel/recovery. It is gingerbread based, but that shouldn't matter if it will boot the ROM later a due to kernel mismatch due to the broken screen lol.
Give it some time too verify you are in the recovery. Now the magic. Find where your adb is at, usually within android/platform_tools if memory serves. You can do a system search for adb and it should pop up. Move to that location. Make a note of the exact path to that location. Now open a command prompt (search for cmd.exe). You then need to switch to the location of your adb. It should be something like the "cd c:/path/to/adb" (no quotes) where you fill in the path you noted earlier. Once there, give this a go. Type "adb devices" (again no quotes) and if you get a string of numbers that means you have adb access!!! Then you can just type "adb pull /sdcard/" and that will drop the contents of your internal storage into the folder holding your adb files (kind of a mess but it is the easiest way to do it). If you would rather it be dropped in a location of your choosing, use this "adb pull /sdcard/ /path/to/desired/location/" and note there is a space between /sdcard/ and your path to desired location.
I am not expert at this, but let me know if you get stuck somewhere in this and I will try to help.
Sent from my Nexus 7 using Tapatalk 2
Hi thanks for the detailed response. i will need to make some time to go through these steps lol however i will update!

Getting md5 sum error cwm

I am trying to put my original ROM back on my phone. When I go into recovery and select the backup using cwm I get bad md5 error and then it reboots back to Cyanogen mod. Looking for some help. Thanks
Try This: http://www.ikevinshah.com/fix-how-to-recover-from-md5-mismatch-cwm-backup-nandroid-backup.html
I've tried it, it works. Good Luck. There is alot of information on this error. Ever since using OBackup, ive never ran into this problem again.
youngnex said:
Try This: http://www.ikevinshah.com/fix-how-to-recover-from-md5-mismatch-cwm-backup-nandroid-backup.html
I've tried it, it works. Good Luck. There is alot of information on this error. Ever since using OBackup, ive never ran into this problem again.
Click to expand...
Click to collapse
Thank you... Im a little new at this but where do i find the "via adb"? Thank you!
sugewhite said:
Thank you... Im a little new at this but where do i find the "via adb"? Thank you!
Click to expand...
Click to collapse
If you use terminal emulator from Google Play, no need to worry about ADB. ADB is android debug bridge, Android command line for Windows computer. In other words, terminal emulator does the same thing on your phone that ADB does on computer for your phone. Most of the time you can input same commands on your phone through terminal emulator, that you would input if your phone was connected to computer via ADB. In this case it says CMD/terminal, meaning it should work either way.
Sent from my hybrid GalaxyS3
joeyhdownsouth said:
If you use terminal emulator from Google Play, no need to worry about ADB. ADB is android debug bridge, Android command line for Windows computer. In other words, terminal emulator does the same thing on your phone that ADB does on computer for your phone. Most of the time you can input same commands on your phone through terminal emulator, that you would input if your phone was connected to computer via ADB. In this case it says CMD/terminal, meaning it should work either way.
Sent from my hybrid GalaxyS3
Click to expand...
Click to collapse
What im trying to rstore is my original rom. I dont have a bckup folder in CWM. It is actually in download/recovery.
If I'm not mistaken I believe your nandroid would be in clock work mod folder?
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
sugewhite said:
What im trying to rstore is my original rom. I dont have a bckup folder in CWM. It is actually in download/recovery.
Click to expand...
Click to collapse
I will leave this ? alone because I haven't ran CWM in a long time.
Sent from my hybrid GalaxyS3
I still havent figured out how to get it back. My backups for some reason is in mnt/shell/emulated/clockworkmod/backup/sg3-orig
When i go to do the rm nandroid.md5 I get a no file exists... Any ideas?

Problem installing Root

I'm having a problem putting root in my phone (Asus zenfone 2)
I made the whole process, 7 clicks, enabled usb, and downloaded a zipped folder with one of the files named "Root_zenfone" which opens a cmd asking to press a key to start, but when I press it says "Fastboots is not known as a Internal command, or external an operable program or a batch file "and so I can not install root, can someone help me, please?
dashlatrell said:
I'm having a problem putting root in my phone (Asus zenfone 2)
I made the whole process, 7 clicks, enabled usb, and downloaded a zipped folder with one of the files named "Root_zenfone" which opens a cmd asking to press a key to start, but when I press it says "Fastboots is not known as a Internal command, or external an operable program or a batch file "and so I can not install root, can someone help me, please?
Click to expand...
Click to collapse
Which Android version is your phone running? Where did you download the zip file? Search for the right rooting method in this forum, never trust those unknown sites found in Google
Yes I downloaded the Zip file and my android is 5.0.
A good and bad news, I was able to activate root but I'm trying to use the emulator terminal to change my MAC address and the message that appears is "tmp-mksh NOT FOUND"
I use the "su" command and soon after when I will use the "busybox iplank show wlan0" and this message appears above. Can you help me?
Have you installed adb and the drivers on your computer? It would be easier to use the modder tool found in the general section. Everything you need is in the pkg.
Sent from my ASUS_Z00A using Tapatalk
Reply
kenbo111 said:
Have you installed adb and the drivers on your computer? It would be easier to use the modder tool found in the general section. Everything you need is in the pkg.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I did not install the drivers because I did not find it and I was able to activate root, now my problem is to change the MAC address of the mobile phone, I am using the android terminal and busybox, I was able to install the busybox but at the time of using the terminal only the message works "Su" later to use "busybox iplink show wlan0" does not work. The following message appears (tmp-mksh NOT FOUND)
What do I need to stop using, or am I using the wrong code?
dashlatrell said:
I did not install the drivers because I did not find it and I was able to activate root, now my problem is to change the MAC address of the mobile phone, I am using the android terminal and busybox, I was able to install the busybox but at the time of using the terminal only the message works "Su" later to use "busybox iplink show wlan0" does not work. The following message appears (tmp-mksh NOT FOUND)
What do I need to stop using, or am I using the wrong code?
Click to expand...
Click to collapse
That's why your fastboot commands were not working. As far as the other MAC address problem is concerned, I don't know about that
Sent from my ASUS_Z00A using Tapatalk

Categories

Resources