Related
Tutorial/Walkthrough for flashing back to stock using RSD Lite (Unrooting a rooted phone by .sbf)
Tutorial Video can be found here... kind of... very close!
http://www.kimete.com/sbfrsd.html
= = =
The fine print: This information is provided without warranty. I can not be held responsible if you **** up. I simply wrote a walkthrough/tutorial. I did not produce the procedure or the steps. I just simply consolidated all the information into a single place with notes to make things easier to understand and execute. You are welcome to share this information anywhere you want. Please do credit me for writing it. Lastly, please link back to the original site if possible. I try to format the text in such a way that it is more easy to understand. Lastly, I ask that everyone who uses this pays it forward by helping others figure out their own phones. Now on to the procedure.
I am running Windows XP SP3/32bit.
= = =
Steps 1 and 2 can be skipped. You just need to download the latest version of the SBF file (currently 2.3.20). Link coming soon.
1. Download 2.3.20 SBF file for D2
You can find it here: http://www.iamthewalcs.com/Support-Files/Droid 2 2.3.2 SBF.zip
2. Extract the .zip file and put the .sbf file somewhere where you can easily find it.
3. Download RSD Lite 4.7. (RSD Lite 4.7 is not the same as RSD Lite 4.7.2)
[RSD Lite 4.9 works as well]
Reference: http://www.mydroidworld.com/forums/droid-2-how-tos/4393-how-sbf-flash-droid-2-a.html
RSD Lite 4.9 Here!
http://droid2files.com/tools/RSD Lite 4.9.zip
New: Download to RSDLite 4.7 with patch.
http://kimete.com/droid/RSDLite47patch.zip
There is a link to download RSD Lite 4.7 + patch here as well. Includes an installer (.msi) and the patch (.ini).
4. Install the program (rsdlite_4.7.msi) or RSDLite 4.9. Follow instructions until completion.
5. Next, extract the patch (pst_flash.ini) to the Motorola/RSD Lite folder. It'll ask you if you want to overwrite the file. Choose yes. (Don't think you need this for version 4.9, but don't quote me on that).
(My file path to place the file was: My Computer -> C Drive -> Program Files -> Motorola -> RSD Lite)
6. You'll need to have the Motorola Drivers. You probably already have them, but if you don't, you can get them here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
KalenXI noted that you can't use the same Motorola drivers that you used for root from the other thread. You must use these updated drivers with MotoConnect. Thank you sir!
7. Now would be a good time to back up anything on your SD card to your computer. Plug in your Droid2 to the computer via USB cable. Pull down the notification menu/blind, choose USB connection, and then choose USB Mass Storage Device. Now there should be a removable storage in your "My Computer." Go through your SD card and back up your important things. Probably the DCIM and download folder. You should also make sure that your phone is set up to "Back Up Data." Go to the system menu (the 4 squares icon/button in the lower left), choose Settings, then Privacy, then make sure the "Back up my data" and "Automatic restore" are checked.
8. You now need to put your phone in bootload mode. In order to do so, power down your phone. Slide open your keyboard, hold the "up" key (the arrow closest to the enter button), and power on your phone. You should come up with a black background and text with something along the line of d2.35 and usb okay.
9. Now you can open RSD Lite. Go to your Start Menu, Program Files, and you should see RSD Lite. In the title of the newly open window, make sure the version is 4.7.
Edit: If you opened RSDLite and your device is not showing, you might need to open it as an admin. Go to program files/motorola/rsdlite/sdl.exe, and right cllick and run as an administrator. Reference by JonandRoid. http://forum.xda-developers.com/showpost.php?p=8000565&postcount=12
10. Wait a few minutes until your device shows in the table. It should say A955, port 1, connected, etc.
11. Toward the top of the window, there is filename/blank field. To the right of it, there is "..." button. Click it. Now find your .sbf with the open window that popped up. Select "Droid2_X6_2.2...SECURE.sbf", or the latest version of your sbf, and press open. Back to the program window, press Start (right next to the "...") Your phone should now start flashing the firmware to the phone. Just let it run it's course. It's going to reboot and start up again. You'll know when it is done when the Progress field in the table of RSD Lite says complete. This may take a little bit. Maybe 5-10 minutes.
After your phone reboots and doesn't get past the boot animation (wait at least 5 or 10 minutes),
a. Turn off your phone
b. Hold down X on the keyboard
c. Turn on your phone while continuing to hold X
d. When you get the Android guy with a '!' in a triangle push the search button on the keyboard (the magnifying glass button, two keys to the left of the space bar)
e. Select both 'wipe cache' and 'wipe data' from the menu.
f. Reboot your phone
If you do steps a-f, you probably won't need to do these following steps.
12. I do not know if this will work or not, but if it does, you guys might not need to do the rest unless you truly do want to fully factory reset your phone. This step is UNCONFIRMED.
To get back onto the Verizon Wireless network, dial *22899 and press send. It should update your phone and you'll be back on the network. (Referenced from ITGuy11 at the link below.)
http://forum.xda-developers.com/showpost.php?p=7933189&postcount=12
13. Your phone still has everyone on it. You'll probably realize that you now have no 3G or phone service and are roaming. Now you need to Factory Reset your phone. Go to the system menu (the 4 squares icon/button in the lower left), choose Settings, then Privacy, the choose Factory Data Reset. Follow the instructions and agreeing to wipe your phone clean. It will ask you to confirm, and/or ask you to enter your security pin/security pattern. It'll reboot itself and run its course.
14. Your phone will eventually be put back to factory settings. You'll then be greeted by the new user/account wizard. Follow the directions. They'll ask you to program/update your phone, enter in some login info, and then your phone will be back to brand new, just like the day you walked out of the Verizon store, except with the BackUp Manager service, all your applications and contacts will be downloaded back onto the phone!
That's it! That wasn't so bad was it?!
= = =
If you found this tutorial helpful, and would like to do something for me, please donate to my PayPal. I am short on rent by $100 this month. I am a student, and moving to a new place and I need to produce first months rent, last months, and a deposit. I am not expecting to profit from this tutorial. Honestly, I am just doing this to help others. I just need some help with rent this month. All donations are appreciated, even if it is a dollar. If everyone donated even a dollar or two, I'd be set! PayPal info coming soon!
Another edit: PayPal: [email protected]
Another quick note, I'll be adding references sometime soon. It is almost 5 in the morning and I want to go to bed!
This is awesome, thank you. This tutorial and your rooting instructions (with all of the extra clarification) are very helpful. I know it's not much but I am going to try to send a few bucks your way (from one poor college student to another? ).
USB debugging should also be enabled. It's found in the Settings -> Applications -> Development.
bcs296 said:
This is awesome, thank you. This tutorial and your rooting instructions (with all of the extra clarification) are very helpful. I know it's not much but I am going to try to send a few bucks your way (from one poor college student to another? ).
Click to expand...
Click to collapse
Thank you. Any little bit is appreciated. Just need to get to the end of the week.
wsfanatic said:
USB debugging should also be enabled. It's found in the Settings -> Applications -> Development.
Click to expand...
Click to collapse
Thank you, sir. I will post that in the tutorial in a moment.
= = =
Also, according to ITGuy11, you can dial *22899 to update your phone to get it back on the Verizon network.
http://forum.xda-developers.com/showpost.php?p=7933189&postcount=12
I am a fail. Didn't read the whole tutorial. Assumed it was like the D1 sbf. Ok still have an issue though, When i get to the bootloader RSDlite and my phone do nothing, still says im missing a certain driver for the phone S Flash driver not found. Anyone know why thats happening?
LosAngeles said:
I am a fail. Didn't read the whole tutorial. Assumed it was like the D1 sbf. Ok still have an issue though, When i get to the bootloader RSDlite and my phone do nothing, still says im missing a certain driver for the phone S Flash driver not found. Anyone know why thats happening?
Click to expand...
Click to collapse
I had that same error, upgrading to the latest Motorola drivers fixed it. I'd post a link but the forums won't let me so just search for "motorola drivers" on google, go to the first link, go to "USB Drivers and PC Charging Drivers" and download the "Motorola 4.6.5 Driver with MotoConnect" drivers.
KalenXI said:
I had that same error, upgrading to the latest Motorola drivers fixed it. I'd post a link but the forums won't let me so just search for "motorola drivers" on google, go to the first link, go to "USB Drivers and PC Charging Drivers" and download the "Motorola 4.6.5 Driver with MotoConnect" drivers.
Click to expand...
Click to collapse
That makes sense. I got my drivers from when I installed Easy Tether. Driver files were on the phone. That's probably why it worked. So, solution to the problem is downloade the latest drivers!
I think a youtube video of this is possible. Would people be interested in that?
darkonion said:
I think a youtube video of this is possible. Would people be interested in that?
Click to expand...
Click to collapse
I think your instructions are comprehensive and clear here, I wouldn't do it unless you've got time to burn. my 02.cents
Thanks! What is everyone's experiences with this tutorial? I want to make sure that it makes sense and is complete. I wrote it from memory after flashing my phone.
20:56:42, September 03, 2010
Line: 587
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x19EC00 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
its still working afterwards, but lost root, etc. its now running 2.2.20, but I'm wary somethings messed up. should I root, install bootstrapper, and wipe, or just let it go (it still has all my apps and settings)
this is great....thank you sooo much. worked out perfect. just an fyi if you cant get rsd lite to recognize your phone on vista go to the ...motorola/rsdlite/sdl.exe and right click as administrator. wouldnt work before i did that. but everything was so smooth and great instructions, would donate but broke too..lol
kageurufu said:
20:56:42, September 03, 2010
Line: 587
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x19EC00 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
its still working afterwards, but lost root, etc. its now running 2.2.20, but I'm wary somethings messed up. should I root, install bootstrapper, and wipe, or just let it go (it still has all my apps and settings)
Click to expand...
Click to collapse
I'd just let it go. Reroot and move on with your life! If something did go wrong, reflash again.
JonandRoid said:
this is great....thank you sooo much. worked out perfect. just an fyi if you cant get rsd lite to recognize your phone on vista go to the ...motorola/rsdlite/sdl.exe and right click as administrator. wouldnt work before i did that. but everything was so smooth and great instructions, would donate but broke too..lol
Click to expand...
Click to collapse
Glad to hear it works. I'll add the note onto the tutorial.
Ughh this is frustrating.. When i get to the part where i have to select the Droid2....SBF file, the start button isn't highlighted so i cant press it. but when i choose the other SBF file, it's highlighted
knoxx said:
Ughh this is frustrating.. When i get to the part where i have to select the Droid2....SBF file, the start button isn't highlighted so i cant press it. but when i choose the other SBF file, it's highlighted
Click to expand...
Click to collapse
Do you have updated drivers? Don't quote me on this, but maybe flash one file and then flash the other?
That's what I did, I flashed the other file (successfully) and rooted. Didn't bother factory resetting or anything.
Sent from my DROID2 using XDA App
And today I was having problems, so I used the bootstrap recovery to wipe cache and data, and then sbf'd from the bootloader
Sent from my DROID2 using XDA App
How exactly do you download the device drivers? Ive tried a million times and the link given on the motorola website just keeps giving me zipped up documents. Really starting to piss me off.
joeld82 said:
How exactly do you download the device drivers? Ive tried a million times and the link given on the motorola website just keeps giving me zipped up documents. Really starting to piss me off.
Click to expand...
Click to collapse
You are moving in the right direction. Inside the zipped file, there is the install file, .msi, I believe, that you double click to install your drivers and MotoConnect.
Hello My Friends I've Heard You Are Having Troubler Installing The New Upgrade Or Understanding What Is Needed To Be Done.
Note: THIS IS A WINDOWS BASED HOW TO AND WILL WORK ON WINDOWS ONLY
Before I Start I must Say, This Is a combination of process and I have not created any of those files or own the right to them so all the links are the same links found on other posts from where i got the info, so by downloading those files you are, supporting them not me i take no credit for this work
Well Here Is the quick Easy Guide In How To Do This
-Fist we Need To Get The Tools To Perform This Operation
pulled From This Tread we need
1. Motorola Drivers For Either 32 or 64 Bits
2. RSD Lite, witch is a tool for flashing your phone.
3. The GOT Open Recovery ToolUpdate: Added Latest version from G.O.T.'S Blog
4.The Firmware Files From Got
2.2.1 FIRMWARE FILES
DACH – GERMANY
http://www.multiupload.com/G9PP7JN78C
DACH AUSTRIA
http://www.multiupload.com/P8DDXCWW03
RETAIL EUROPE (RTEU)
http://www.multiupload.com/6X7H39HGCG
FRANCE RETAIL
http://www.multiupload.com/PK28LXE4SE
ITALY WIND
http://www.multiupload.com/3KYMZNRZW2
UK RETAIL (RTUK)
http://www.multiupload.com/60B78PRKNY
TELUS CANADA
http://www.multiupload.com/5S2CYGP3VW
Click to expand...
Click to collapse
EDIT: G.O.T. Has Added the burnerable open recovery to these sfb files so no need to flash it latter
-Now That We Have The Stuff We Need We are going to do it, fist i must say that unlike other roms that are applied by a backup restore (corect me if im whrong) this is a full flash and its going to reset everything so no apps will remain no setting will remain and is highly recommended that you uninstall every app you have, don't back them up(except for apps some apps that have a create backup file, those seem to work) just uninstall them, and when we are done have them installed again, Here Is A Tool That Will Help You Get There Faster
1.ok you have everything uninstalled right? now time for some action
2.install the proper divers (32 or 64)
3.install the RSD Lite tool
4.unzip the 2.2.1 FIRMWARE FILES you downloaded and you will find a ".sbf" file
5.now connect your phone to USB cable and turn it off
6.boot it in boot-loader mode (press the D-PAD UP key while pressing the power button), some night need you to release the button after a minute, a black screen will be shown on your phone and you will see the divers being installed on your computer.
7.when drivers are done open the RSD Lite tool and your device should appear you can click on it to see details.
8.now click on the "..." buttons that are close to the start button and look for the ".sbf" file, after a couple of seconds it should be ready to start
9.press the start button and do not unplug the cable or let your computer show the screen saver or go to sleep, the posses must not be stopped while it has started .
10.when the posses is done the devise will restart and voala, you have 2.2
-As GOT stands there are some bugs on the firmware and they have developed a fix to them and get root and overclock, here is what you have to do.
1. unzip the got open recovery tool into the root of your SD card
2.check this quote
NOTE: On some devices, we have encountered that rooting directly after flashing without rebooting after the initial flash can bring some issues with RootExplorer not asking for root permissions. To be safe, reboot after flash so that the “welcome to milestone” menu comes up, set up the device in general, then reboot to recovery and root the device as well as apply our 2.2.1 tweaks with Launcher, Services.jar fix and Wireless Tethering app.
Click to expand...
Click to collapse
this means if the fist time your milestone got restarted and you saw "Welcome to Milestone" Message You are good an you can root.
but if you didn't then restart you phone and see if the message comes out, if not , a factory reset should have that scree message shown.
3. open the open recovery by pressing camera and power button at the same time while the device id off. you should see a scree with a "!" symbol on it then press fist volume rocker up button a leave it pressed then press camera button, some letter will pop out.
4. using the pad scroll down to "apply update.zip", after a couple of seconds the GOT menu should pop out (everything from now on uses the pad)
5.root your phone (why not)
6.go down to "Launch 2.2.1 Menu" Option.
7.Here you will see the "Fix Bugs They Are Talking About
One of the first things you should do is use the “Fix 2.2.1 bugs” selection in the new OR 2.2.1 menu after you flash the sbf file.
This tweak will fix some of the issues with the generic sbf build such as dual USB notifications, replacing some stock Motorola applications such as the old launcher/mediagallery and adding the Wireless Tethering application.
Click to expand...
Click to collapse
8. there is the overclock too.
Now your device should have all the things you need to start playing with it,I encourage you to check on some tweaks the GOT team might have, and you might want.
I Hope This Was Helpful enjoy ^_^
To Do For This thread:
Code:
1. Make It More Easy To Use, and clear to read
2. Add Suggestions
3. Add screenshots
4. Add Other OS Options
5. Add Attachments (For Some reason I Can't Now)
Please Post And Rate If This Was Useful
Bug Counter:
Common Problems Found On Thread
http://forum.xda-developers.com/showthread.php?t=810726
1. AppBrain Market Sync Not Connecting To server.
2. Google Chrome To Phone Not Working.
3. WiFi Having Trouble To Connect On Some Routers, Sometimes Not Connecting At All on WPA2
4. Activating The Camera From The The Albums Will "Force Close"
5. Facebook Sync Is Not Working
6. The menu button on the keyboard activates the voice recognition option, and cannot be used to trigger shortcuts anymore (To me its more like a change on the way the keyboard works instead of a bug since you can use the menu button on the screen to trigger keyboard shortcuts)
7. No Vibration On key press
8. Russian Language Will Have Problems with phone and contacts apps
9. problem with android id
If Any Of Those Work On Yours Please Report Witch version you installed maybe yours can help fix others,you think you found a bug and its not listed? post it here and post
Fixing Problems:
1. Problem with android ID:
A. If Not Installed The Update Yet(Needs Root)
-Install This AppAndroidID
-Back your android ID up, and put ir somewhere safe
-follow the guide to update to froyo
-Install This App againAndroidID
-restore your android id
B. If Already did it(Needs Root)
-install this appAndroidID
-invent a number that might serve as your android ID (you need numbers and letters)
-input it on the app
okay nice tut, butttttt... im stuck at the part where i should install openrecovery. at first, to come to the "!" screen, camera screen + power did not work. i got there by pressing X + Power... but now i dont know how to access the menu where i should install update.zip..
please help!
November91 said:
okay nice tut, butttttt... im stuck at the part where i should install openrecovery. at first, to come to the "!" screen, camera screen + power did not work. i got there by pressing X + Power... but now i dont know how to access the menu where i should install update.zip..
please help!
Click to expand...
Click to collapse
okay i got it, im so sorry, i used the up button on the dpad
Also I did not see a launch 2.2.1 menu option. But I have currently launched the GOT open recov without an issue. I have rooted as well as many other things but didn't see that specific menu.
FoTwoZero said:
Also I did not see a launch 2.2.1 menu option. But I have currently launched the GOT open recov without an issue. I have rooted as well as many other things but didn't see that specific menu.
Click to expand...
Click to collapse
Silly question are you suing the newest version?
if you press down should on the open recovery menu it should be your sixth option, I have recorded a video about it this morning but its backwards I'm Going To Try And Have it Fixed and up today hopefully
For Tmobile USA ?
Which SBF for a german Mlestone on TMobile USA ? Will telus do fine ?
gbzygil said:
Which SBF for a german Mlestone on TMobile USA ? Will telus do fine ?
Click to expand...
Click to collapse
your Should use the rom depending on which band your phone has
German milestone should work with Europe ROM
under setting about phone check the Build Number
and look for that same number in here
http://and-developers.com/sbf:milestone
it will give us an idea where the phone is actually from
hi there. i have instaled europe GOT_RTEU_2_2_1FULL.zip version and now sometimes my touchscreen does not work. i mean that if i put the phone in standby and i try to unlock the touchscreen is not responding. i have to power off/on to make it work again. thanks in advance
Facebook app wont Synch with my contacts on first launch of FB app.
No other bugs so far...
Israel milestons should use retail europe?
Sent from my Milestone using XDA App
protozeloz said:
2. Google Chrome To Phone Not Working.
Click to expand...
Click to collapse
for me it's working perfectly. RTEU
Thank for this tutorial.
My milestone works fine so far, but 3g mobile hotspot and wireless tether not working.
Flash on milestone is so cool
something i don't get
I updated the firmware with RSD Lite, and used the one click tool, because:
whenever i try to hit update.zip i will get an errormessage, stating that these blocks couldn't be found -> ergo, the card not be mounted.
The HTC stuff i always managed, but this one is a mistery to me. Also, i did format fat32, pushed the stuff and then straight on bootup trying to hit the update.zip, without success.
I've read about how other people solved that problem, none of those approaches helped me.
Any hint is more than welcome.
2 bugs i've discovered so far: Battery drain like almost to be declared useless, some market apps "vanish" after installing them. I suppose those fixes would have done the job. I might attempt to use root explorer and execute the scripts like that, still I'd like to know why I'm unable to get the update.zip, resp. the G.O.T or any other "intelligent" boot menu installed.
Edit2: Even when installing the vulnerable sbf, i still get the error: E: Can't mount /dev/block/mmcblk0p1 ....
plvt_florian said:
hi there. i have instaled europe GOT_RTEU_2_2_1FULL.zip version and now sometimes my touchscreen does not work. i mean that if i put the phone in standby and i try to unlock the touchscreen is not responding. i have to power off/on to make it work again. thanks in advance
Click to expand...
Click to collapse
This could be for any reason try this
-Re download and re flash the files(do the whole thing again)
-there is an app i have called sd dual mount that makes my screen go crazy wen i connect the phone to an usb port, it was stable on 2.1 but now goes crazy on 2.2 check some of your apps to ensure they are not the ones responsible for this
hanslast said:
Facebook app wont Synch with my contacts on first launch of FB app.
No other bugs so far...
Click to expand...
Click to collapse
yurasts said:
Israel milestons should use retail europe?
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
you can try with the retail Europe,
evolucja said:
for me it's working perfectly. RTEU
Click to expand...
Click to collapse
can you tell me if you have an android ID? it should work when your device has it
czescdziadek said:
Thank for this tutorial.
My milestone works fine so far, but 3g mobile hotspot and wireless tether not working.
Flash on milestone is so cool
Click to expand...
Click to collapse
you can try and uninstall the wireless teeter app an have it reinstalled that should sort it out
MenoDev said:
I updated the firmware with RSD Lite, and used the one click tool, because:
whenever i try to hit update.zip i will get an errormessage, stating that these blocks couldn't be found -> ergo, the card not be mounted.
The HTC stuff i always managed, but this one is a mistery to me. Also, i did format fat32, pushed the stuff and then straight on bootup trying to hit the update.zip, without success.
I've read about how other people solved that problem, none of those approaches helped me.
Any hint is more than welcome.
2 bugs i've discovered so far: Battery drain like almost to be declared useless, some market apps "vanish" after installing them. I suppose those fixes would have done the job. I might attempt to use root explorer and execute the scripts like that, still I'd like to know why I'm unable to get the update.zip, resp. the G.O.T or any other "intelligent" boot menu installed.
Edit2: Even when installing the vulnerable sbf, i still get the error: E: Can't mount /dev/block/mmcblk0p1 ....
Click to expand...
Click to collapse
have you tried re downloading the files and doing all over again?, it could be a broken file
thats why i tell devs and chefs they should add an MD5 sum to their files larger than 20MB some errors are caused by just having downloaded broken files
Root phone from the GOT OR menu doesn't seem to actually root my phone (2.2.1 UK version)
Superuser whitelist app FCs instead of prompting to allow access. Have tried using Better Terminal for root access & also Wireless Tether app.
Anyone else getting this? Any ideas? Do any of the 1-click root apps still work with this build of Froyo? Which can we use?
aboycalledsu said:
Root phone from the GOT OR menu doesn't seem to actually root my phone (2.2.1 UK version)
Superuser whitelist app FCs instead of prompting to allow access. Have tried using Better Terminal for root access & also Wireless Tether app.
Anyone else getting this? Any ideas? Do any of the 1-click root apps still work with this build of Froyo? Which can we use?
Click to expand...
Click to collapse
i can confirm this. Simply trying it a second time worked for me
I'd like to add something for Linux users:
Using a virtual machine (virtualizing WinXP) that has USB support (eg Oracle VM VirtuaBox, since VirtualBox OSE does not support USB forwarding) can do this pretty easy. So no worries when trying this via a VM.
i try to instal GOT and its succesfull.
but why i install the application not bring to SD card
but still bring to internal memory
many said 2.2 automatic have app2sd
can you help me?
THX
m0jo said:
i can confirm this. Simply trying it a second time worked for me
Click to expand...
Click to collapse
not for me unfortunately!
weird...
Ok these steps are very important but before anything I also have to thank Lyriquidperfection & Ausdim for setting up their important parts of the instructions inside the links below:
So before you flash anything, or start playing with your gem, follow these important steps below to get all the important parts backed up and safe, so that you will not have to return your device back to samsung broken. Believe me I have seen it happen PLENTY of times in this forum, so read carefully
Make sure you have a Good USB cable and a stable PC and that don't get any power outages or surges, you dont want to be half way through something and you loose power or get a bad connection.
1st: Install Samsung Kies on your PC this will then Install the Samsung USB drivers you will need to connect your device to your PC OR you can get the samsung drivers on there own from the Link in 2nd step, but I recommend you install kies as it may be useful to you in the future.
2nd: Now as your IMEI number is like the heart of your device lets back it up right now: Follow only part of these steps in this link, you will finish the rest of the backups at the end when your rooted. I have copied and bolded the parts you will need to do right now, once finished this section of the backup you should be left with a *.qcn file which is roughly around 250kb of size.
http://forum.xda-developers.com/showpost.php?p=33048706&postcount=1
*Setting up QPST with your PC:*
*Backing Up IMEI / NV Data:*
*Restore USB Settings after Backup / Restore:*
Now keep that page open because you will return here in step 6 once you are rooted to complete the backup process.
3rd: Now Install Odin V3.04 - You can get the link for odin in the 4th step link, So you may aswell just continue on to 4th step as the instructions inside that link advice you to install Odin aswell.
4th: Now you must Root your device and install CWM recovery , Follow these steps carefully > http://forum.xda-developers.com/showpost.php?p=32235061&postcount=1
5th: Once you have root I recommend you instantly make a full backup of your device also known as a Nandroid backup. You must go into recovery mode to do this with the CWM recovery you have just installed in 4th step above. (In recovery mode just click backup/restore and then choose backup, after its done your backup will be placed on your ext sd card , if you dont have ext sd card then choose backup onto internal sd card.)
6th Now lets finish the backup process since we are now rooted, I am going to say this again, this is VERY important incase something goes wrong and you loose your Imei and Data, you need to back it all up. By doing this it will save you returning your device back to samsung like many have done previously because they have not done this, Remember where you left off in 2nd step above? Well now you can go back and complete the partition backup of the efs folders. You should be left with 4 backup files for this final section of the backup process >>> http://forum.xda-developers.com/showpost.php?p=33048706&postcount=1
--------====FINISHED====--------
Congratulations you now have your Imei/Nv data backed up , You are rooted and Nandroided. Now you can play around but off-course DO NOT be reckless make sure you know what you are playing with
Peace
PS: Only trust what you see in this I9305 XDA forum, as i have been following the device from day one and I can only recommend the information you see here.
can't find step 4..
Sorry I just fixed all the links
stuck on whether to install the I9305_CWM_Recovery.tar.md5 software and what I risk
EDIT: thread Readers please note. I was a NOOB and I initially and accidentally credited "Lyriquidperfection" (who has also been very considerate in assisting) for the thread when "btemtd" was the original thread creator. "btemtd", I have edited to show appropriate. I am sorry please forgive my oversight.
**
Dear "btemtd"
*Note the following pre-install procedures and verifications confirmed:
1) My phone is NOT bricked and is running stock OEM i9305 installed software with details for the device posted at the end of this reply.
2) prior to doing ANYTHING I verified I can Dial *#7284# on phone and can see the 'Qualcomm USB Settings' button
3) KIES drivers installed and i9305 to PC works in KIES application and drag and drop modes
4) I have downloaded the Param_Bin_I9305.tar.md5 file in case I need it.
5) I have downloaded the I9305_CWM_Recovery.tar.md5 file for use when I install the CWM.
6) I have downloaded the CWM-SuperSU-v0.96 application but have not yet installed it and have not yet learned about how to operate it (I will study and follow your instructions prior to doing so)
7) I have read this entire thread and all replies.
8) I have also read the entire thread and all replies to: [WARNING! + GUIDE] Backup and Restore IMEI / NV Data Procedure for GT-I9305
9) I don’t care about losing any of the media or pictures or applications (whatsapp) installed on my phone as these can all be reinstalled later on.
I have successfully executed the following so far:
1) I installed QPST v2.7.378 program on my PC and backed up a .qcn file. I then restored the .qcn file back to the i9305 and it accepted the restoration without problem. I can see my IMEI number by dialing Dial *#06#
2) I DID NOT back up any of these files below because I was NOT rooted and I DO NOT have a terminal emulator application (I can learn the emulator application if it is necessary and if someone can provide a link to where to get it). IF it is required for me to back up these files PRIOR to proceeding using ODIN please direct me to do so. I would prefer to not have to learn the emulator program unless it is required.
m9kefs1 - Located at: '/dev/block/mmcblk0p4'
m9kefs2 - Located at: '/dev/block/mmcblk0p5'
m9kefs3 - Located at: '/dev/block/mmcblk0p6'
3) I installed ODIN version Odin3 v3.04 (but I still have no clue how to operate this software)
*
This is where I stopped. Why? Well, after reading the instructions "btemtd"provided in thread I became concerned. My primary objective is to first save a backup of my phone. Since I am such a noob I don’t even know what a backup file extension is named (for example a backup for PC might be named xxxxx.img). I suspect that the backup extension file might be named xxxxx.tar.md5 but I still don’t know.
*
As I read "btemtd"instructions further I became concerned about the following items:
1) "btemtd"states in the In the 4th that one should “Now you must Root your device and install CWM recovery”. Well, since I am still such a noob I don’t know how I should root my device. Ideally, I want to make a backup of my phone (I think that will eventually be called a “nandroid”) as quickly as possible so if I inadvertently damage something during an install I will have an original source file to revert to (and hopefully be able to restore). I have a few questions:
A) Is there a special “rooting” software I should be using it or is “rooting” just a process name (like “flashing” a drive for example)? It might help me if I could have some noob instruction on how to root an i9305 without bricking it.
B) If I “root” my phone at this stage (without having made any backups other than the xxxx.qcn file) do I risk bricking my phone and not being able to revert to the stock OEM i9305 software?
2) Another area of concern was as follows. "btemtd"advocates installing the CWM (I presume that is short for clockwork module) application and provides a hyperlink for it (which I read). In this instruction it advocates downloading the file named “I9305_CWM_Recovery.tar.md5”. This is where things get a little murky and hence the advance questions (which hopefully will help other noobs beyond myself and allow "btemtd"to concentrate on the i9305 problems I couldn’t solve in a lifetime). My critical question is as follows: IF I follow the instructions that "btemtd" hyperlinked to (these instructions were posted by senior member “ausdim”) and IF I install the CWM (install via ODIN) file named “I9305_CWM_Recovery.tar.md5” WILL I be replacing my stock i9305 OEM software with this new one created as “I9305_CWM_Recovery.tar.md5”? Could you please apprise on this instruction (remember, my first goal is to make a full backup of my existing stock i9305 OEM software on the i9305 so that I can restore if I late noobify any of the instructions). I want to confirm that by proceeding with the procedures kindly laid out by audsim I will NOT be wiping out my OEM software on the i9305 supplied when the phone was new. IF the answer to that question is “YES, you will be essentially replacing the stock OEM software for the i9305” with the new one created under “I9305_CWM_Recovery.tar.md5.”” then I might have to consider the implications of losing all of the factory OEM software that came on the phone. Please note that I am hoping that this procedure will result in the phone OS changing from:
FROM: stock OEM i9305 software
TO: stock OEM i9305 software + CWM module
*
This post is lengthy, yes, but I hope accurate and hopefully it will provide some clearance, comfort, or guidance to other noobs looking to backup their phone prior to risk bricking it on more risky adventures.
Thanks in advance and donations to "btemtd" for his hard and thankful efforts.
DEVICE MODEL BUILD is as follows:
Samsung Galaxy S3 LTE Hong Kong Version
Model number:GT-19305
Android version: 4.1 .1
Baseband version: 19305ZHALl1
Kernel version
3.0.31-177985
[email protected] #1
SMP PREEMPT Thu Sep 20 23:04:05 KST 2012
First of all I am the one who made this guide with all the links to the appropriate places, You cannot see this? LOL
Anyways.... You asked
" Is there a special “rooting” software I should be using it or is “rooting” just a process name (like “flashing” a drive for example)? It might help me if I could have some noob instruction on how to root an i9305 without bricking it.
B) If I “root” my phone at this stage (without having made any backups other than the xxxx.qcn file) do I risk bricking my phone and not being able to revert to the stock OEM i9305 software?"
A)There is no special rooting software, its basically a file which you flash onto your phone which gives you the root access. If you follow the instructions 100% and nothing on your side fails well then you should not brick your device, reason people brick is becuase they have done the wrong thing or have flashed the wrong thing or it could be bad flash files. But I can confirm none of these files are bad as they have all been used with success.
B) we would hope that the qcn is enough, but maybe not. Only because we have not seen it happen yet, everyone who has lost imei so far has made the mistake and not made any type of backup, But lyriquid says JUST TO MAKE SURE you should also backup those partitions after u root just incase it comes to the point where you need them.
You want a Noob instruction on how to root without bricking it? ummmm What the hell is that! LOL Mate this guide is almost as NOOB as it gets, and OF COURSE if you follow this guide and all the links you wont brick it.
Reason you want root is this will then allow you to further back up the partitions and also allow you to make a nandroid (FULL BACKUP) of your current software/ROM
Only way to do this FULL BACKUP is by having CWM installed:
CWM is NOT firmware it is only recovery module, CWM will only replace your stock recovery module it is Only 7mb. it will NOT replace your stock firmware. Also this recovery module has much more capabilities then your stock recovery. It will also allow you to flash Mods, tweaks,roms if you wish to do so in the future.
Even if you do all of this you can still even return it back to OEM with stock recovery firmware and UNROOT. anything is possible. So my recommendations if you want to start flashing software and want to backup your rom is to follow my steps fully in this thread and click on the links and follow those guides as well. Each link will guide you as well. Once you have root and CWM installed and you want to make a FULL BACKUP of your OEM Softwareall you need to do is boot into recovery mode, then choose Backup/restore and then >>> Backup Thats it very simple which is why i didn't include it in the thread because as soon as you go into recovery mode you will be able to figure it out yourself
By the end of all this procedure you will have
Rooted Stock OEM software + CWM REcovery
EDIT: I reccomend you do what the full guide says, and install a terminal emulator because you dont need to learn code Lyriquidperfection has written down exactly what you type inside the terminal and thats IT your done. Its that easy!!!
For now you type the commands anyway. I am working on updating EFS Pro to have Qualcomm support so you can back up all NV Items from there and also backup and restore other important partitions just with a few clicks. I'll keep everyone updated when something good enough for a beta develops.
Sent from my GT-I9305 using Tapatalk 2
lyriquidperfection said:
For now you type the commands anyway. I am working on updating EFS Pro to have Qualcomm support so you can back up all NV Items from there and also backup and restore other important partitions just with a few clicks. I'll keep everyone updated when something good enough for a beta develops.
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
This would be awesome. must say
Thanks btemtd, great post!
I am also a recent convert (from iphone) to a galaxy s3 and have an i9305T model. I have been doing a bit of research in order to prepare myself to safely root my phone and was stoked to see such a helpful post. I will admit that I am also a noob with this sort of stuff but still do my best to learn what I can.
I just wanted to confirm that the process you have listed will support my aforementioned phone model with telstra as the carrier? I only ask because I remember a previous rooting guide that was only applicable to Optus phones and just want to make sure.
Thanks again for your help
Yes this will work on all i9305 models. No probs bro i was starting to get amazed on how many ppl were flashing the wrong stuff and braking there imei lol so i thought this may come handy
Sent from my GT-I9305 using xda app-developers app
nvmd, stupid noob
Sorry about this post. Misread something between steps 4 and 5.
Now fully rooted. Thanks for the great post. Very helpful to someone entirely new to this daunting process. Makes jailbreaking a walk in the park xD
Unroot
"btemtd" Thanks for you above tutorial.
Is it possible to add and process on how to unroot the GT-i9305, if required
Thanks btemtd, I am working on a YouTube Video, to help noobs like me to root their I9305. Would I be able to pm you just incase I need some help on anything regards to rooting and roming?
bleepsake said:
Thanks btemtd, I am working on a YouTube Video, to help noobs like me to root their I9305. Would I be able to pm you just incase I need some help on anything regards to rooting and roming?
Click to expand...
Click to collapse
yes offcourse you can PM me.. Thats a good Idea I might add your video to this guide if you dont mind, this will make it totally complete!!...
FOR NOOBS only
This is written by a noob for other noobs. It contains a set of very detailed instructions and is compilation of varies inputs from lyriquidperfection, audsim, btemtd, and nnnevvv. Without them I would be nowhere. I hope this guide, despite being very detailed, can help others so they don't have to hunt and pester devs for answer. This guide is only an expansion and extrapolation of this post which was kindly created by btemtd.
*
It also involves other work from the developers I credited above.
*
This guide is NOT for you if you have:
1) Bricked your phone
2) have an i9300
3) lost your IMEI
4) installed a custom ROM
5) already have CWM or SU installed.
*
Please remember it is only an expanded set of instructions built upon btemtd original work. Its only intention is to help get it done, right, without using up other's time. If the thread creator or OP ed suggests I amend or remove anything please let me know.
*
Pre-install instructions:
1) Your device is NOT bricked and is running stock OEM i9305 installed software with details for the device posted at the end of this reply.
2) Prior to doing ANYTHING you can Dial *#7284# on device and can see the 'Qualcomm USB Settings' button
3) KIES drivers installed and i9305 to PC works in KIES application OR you have verified that USB drivers work fine for PC to device
4) You have downloaded on to your PC the Odin3 v3.04. application.
5) You have downloaded the I9305_CWM_Recovery.tar.md5 file to your PC.
6) You downloaded the CWM-SuperSU-v0.96. zip file and stored it on the device’s internal memory card. You can store it directly on the device’s INTERNAL SD card (don’t worry, CWM will allow you to navigate to it).
7) You don’t care about losing any of the media or pictures or applications (whatsapp) installed on my device as these can all be reinstalled later on.
8) Battery is charged to 80 percent or more
9) Solid dual use power and data cable tested and working.
10) Back up all of the contacts to SIM Card in case Data wipe.
11) You are okay with warranty being void and binary counter reset being added
Installation procedure
1) Get coffee
2) Install the latest version of Samsung KIES and check that complete cable communication works and that all drivers on the PC are installed. Confirm that KIES communicates with device on PC. DO NOT update your device using KIES to the latest Samsung or Android software.
3) install QPST v2.7.378 program on your PC. The QPST software is a qualcomm product and is a diagnostic tool that has a variety of subtools that you can use to test, manage and edit the form factor device. Click the setup.exe file and follow instructions. This is a qualcomm product and it is not complicated. A user manual (in case you feel like exploring) is available in .pdf.
4) Dial *#7284# on your device to access DeviceUtil and select 'Qualcomm USB Settings' at the bottom. Now scroll down and select 'RNDIS + DM + MODEM' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit DeviceUtil. Your device is now in DIAG Mode.
5) Connect your device to PC via USB. Note, it may showing “loading drivers” on your PC. Wait for USB drivers to load and install.
6) Find the QPST application on your PC and navigate to the 'QPST Configuration' menu. Select it and navigate to the 'Ports' tab. Press 'Add New Port...' button. Select the COM Port that has 'USB/QC Diagnostic' next to it, change the Port Label name (if you wish to) to 'Samsung GT-I9305 diagnostic” then press 'OK'. You should now see your device listed in the 'Ports' tab and the 'State' should indicate 'Enabled'. Close this QPST application.
7) The next step will help you to BACK UP the IMEI/NV Data.
8) Go back to the QPST application Folder and navigate to the 'Software Download' application and then select the 'Backup' tab. You will need to select and name the file. I chose “i9305-qcn-back-up-file.qcn”. Press the 'Browse' button and select a Save Location for your QCN File. Press the 'Start' button and wait for it to finish. DON’T TOUCH YOUR DEVICE during this process. This will back up all your devices NV Items and save them to the QCN Backup File you just named. The resulting QCN Backup File should be about 250KB in size. The QPST application will show the backup has been completed. Verify that the file was actually backed up by looking in the directory to where you selected to store it. Then close the program.
9) The next step will help you to check to RESTORING IMEI / NV Data:
10) Go back to the QPST application Folder and navigate to the 'Software Download' application and then select the ‘Restore’ tab. Press the 'Browse' button and search for the QCN Backup File you created (remember I named mine “i9305-qcn-back-up-file.qcn”). Press the 'Start' button and wait for it to finish. This will restore all your devices NV Items from the QCN Backup File. Your IMEI / NV Data should now be fully restored. Dial *#06# on your device's keypad to check your IMEI is restored. It should show your 17 digit long IMEI number on screen. Write it down and store for future purposes in case you need to recall it one day.
11) The next step is to Restore the USB Settings after you have performed the above QPST Backup / Restore procedure. Dial *#7284# on your device to access DeviceUtil and select 'Qualcomm USB Settings' at the bottom. Now select 'MTP + ADB' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit DeviceUtil. The device will reboot as you ask it to save and reset. Your device is now back to default USB operation.
12) Exit the QPST application.
13) The next step is to install ODIN which you will use to flash the CWM files from your PC to the device.
* Note that ODIN packages can be device specific. For the GT-i9305 I used “Odin3 v3.04.exe”. Navigate to where you have stored the ODIN application and select “Odin3 v3.04.exe” file and double click. ODIN will open.
NOTE: ODIN will not self install on your computer like a standard-install.exe folder. You will need to run the “Odin3 v3.04.exe” file every time to open ODIN up. Forgive my noobness for not knowing what the name of this procedure it.
14) Search for the ‘ I9305_CWM_Recovery.tar.md5 ‘ file you have downloaded previously in the “pre-install” instructions. For logistics purposes you may wish to drag and drop this file from its current storage location over the ODIN folder directory.
15) If KIES is running shut it down or suppress it on your PC.
16) The next step will involve “installing” the ‘ I9305_CWM_Recovery.tar.md5’ file. Actually, this is just a “module” that is intended to “replace” the stock recovery module. To do this, you will need to first set up your device to boot in what is called the “download” mode. To do this you must: POWER off the device first. Then after power is completely off, PRESS and HOLD the ‘power’ + ‘volume down’ + ‘home’ buttons all at the same time. I suggest that you start by pressing the “volume” + “home” buttons first instead of pressing the “power” button as you may inadvertently just power the device up (instead of booting it up into “download” mode). If you did it right you will boot up in “download” mode and Android will then ask if you if you “want to download a custom OS”. You will confirm “continue” by pressing the volume up key.
NOTE: it’s possible your PC computer may want to install device driver software. If so, just let it install and wait for it to finish.
NOTE: to navigate the menus in “download” mode (and also in “recovery” mode) you should use the VolUp / VolDown to go “up” or “down” the menu. Press the “power” button to select items (kind of like a “go” or “enter” function).
17) Now Connect your device (make sure battery is at least 80% charged) to your PC ( it is preferable to connect directly to the computer and not through a USB HUB or port replicator).
18) Open the ODIN application by navigating to the Odin3 v3.04.exe file . Make sure your device is detected and you should see a blue (older models may show yellow color) square in the top left corner.
NOTE: Make sure only the “auto-reboot” and “f reset time” boxes should be checked in the ODIN Application.
19) Click on the box next to “PDA”. And then click the “PDA” and navigate to the area where the ‘ I9305_CWM_Recovery.tar.md5’ file is stored. Select it and it will auto populate into the ODIN application. Then, on the ODIN application, press “start”. You will see a series of command actions showing in the ODIN Application which should show the status. Upon completion it should show that CWM was installed in the ODIN application. You may have to repeat this process once again as CWM may not “stick”.
20) There has been considerable debate about different units requiring the battery to be pulled due to the fact that some factory units have been shown to reboot back into its own factory state and therefore exclude the CWM file that you just tried to install in the previous steps. I read of many users who were experiencing this problem. See For further reading please see: http://forum.xda-developers.com/showpost.php?p=32235061&postcount=1 to show how to deal with and manage this problem. I, along with another user that I confirmed with, DID NOT have to do the battery pull method. Why? Well, I think that some factory models require this process and others do not. My device (specifications at end of post) did not require it. Also, the problem may have been created by user’s updating their device software through the KIES application which I recommend not doing until the device has been rooted and CWM and SU installed in this process.
21) After instructing ODIN to install the ‘ I9305_CWM_Recovery.tar.md5’ onto the device the device should reboot. If it does not reboot after awhile you can power down your device. What will happen? Well, you have either successfully installed the ‘ I9305_CWM_Recovery.tar.md5’ file or your device has reverted back to the factory restore option. You shouldn’t have much risk of bricking the device during this step. The key is to get the ‘ I9305_CWM_Recovery.tar.md5’ file to stick during the “download” process. If it does not stick you will need to refer to the thread For further reading please see: http://forum.xda-developers.com/showpost.php?p=32235061&postcount=1 as to how to employ the “2 different battery pull during the reboot process” methods he suggested (again, fortunately I did not need to do this).
22) Now you need to put the device in “recovery mode”. Unplug the device from the USB Cable attached to the PC. To put it in recovery mode you must: POWER off the device and the PRESS and HOLD the ‘power’ + ‘volume up’ + ‘home’ buttons all at the same time. Again, I suggest that you start by pressing the “volume” + “home” buttons first instead of pressing the “power” button as you may inadvertently just power the device up (instead of booting it up into “recovery” mode). If you did it right you will boot up in “recovery” mode and you will clearly see the words “CWM-based Recovery” written in white on the top line. If you don’t see that then your installation of the ‘ I9305_CWM_Recovery.tar.md5’ did not work and you will need to repeat the steps above until you get it right.
23) Next you will be installing the SUSuperuser module while your device is in "recovery mode". Remember you should have stored the “CWM-SuperSU-v0.96.zip” (DO NOT unzip it yourself) on the Device’s internal memory card. Using the volume up/down keys and the “power” button for enter/go you should scroll down and select menu option "install zip from SD card"
select menu option "choose zip from internal SD card"
scroll down to the “CWM-SuperSU-v0.96.zip file and select that using the “power” button. It will then ask you “if you are sure you want to install, it can’t be done”. Scroll down to the “YES” and then select the power button to confirm. It will then mount and install it. Once it is done installing you will then need to scroll to the “go back” choice on the menu. Then go back to the “reboot” device and select that. It will reboot.
24) Your device should reboot and you should be able to confirm that SUSuperuser is installed by looking at the apps page on your device. You should be able to see a little blue Android with a red cape. If you see it, you have successfully installed.
25) Once you have root and CWM + SU installed and you want to make a FULL BACKUP of your settings and software. Using the same methods above, boot into “recovery mode”, then choose Backup/restore (select it with the “power button”). Then, it will begin the “back up” process which will take about (7 ) minutes (it takes longer if you are backing up lots of items). Note that the program will back up the backup items onto the EXTERNAL SD Card in a folder named “2012-11-07.10.57.45 (“time stamped”) and it will contain 6 items including boot image, recovery image, nandroid.md5, and 3 others. Mine was about 1.17 gb in size and DID NOT include any music, videos, or pictures. MAKE SURE that your external SD Card has enough free space to store the CWM back up folders. I suggest that you then copy the entire back up folder over to another secure location on your PC (which you can copy over to the SD card anytime) in the event your current external SD card or device goes whacky.
26) Well, it was not brief but it was detailed and concise and I hope it helps other noobs like myself to successfully install and execute this process as it will lead to further dev opportunities to trying out other ROM’s while being able to reverse the process if things goes really wrong.
27) If I was of help just say “thanks”. Will try to answer PM if you have them but I am just a noob and may be of little use. This was written by a noob and for other noobs. Hope I haven’t annoyed anyone else in the process.
*
Model number:GT-I9305
Android version: 4.1 .1
Baseband version: I9305ZHALI1
Kernel version
3.0.31-177985
[email protected] #1
SMP PREEMPT Thu Sep 20 23:04:05 KST 2012
Build number: JRO03C.I9305ZHALI7
Woahh thats alot of writing, but thanks for your time, I didnt know that myself and the guides in the links that LyriquidPerfection and Ausdim created were that hard to understand But i guess I dont know how a PURE noob thinks, Even though I was a noob in August this year i kind of know my way around a computer but I still think i am a noob compared to these programming devs, Maybe I am not the Noobiest noob anymore if thats a word LOL oh well the more information in this thread the more valuable. I think they should get this entire thread Stickied, I have already asked
btemtd said:
yes offcourse you can PM me.. Thats a good Idea I might add your video to this guide if you dont mind, this will make it totally complete!!...
Click to expand...
Click to collapse
Thanks buddy. Of course I dont mind you adding the video to this thread. I want to make a few videos actually that you might be able to help with. =)
working on a pm now.
Sent from my Beautiful GT-I9305 using Tapatalk
Ok I will reply when I wake up thanks
Sent from my GT-I9305 using xda app-developers app
hey droid!
This is awesome, I hope I can use this for my youtube guide for iOS refugees like me.
Sent from my Beautiful GT-I9305 using Tapatalk
bleepsake, can't wait to see your video.
Is unrooting unique per phone or is it the same? When I search unroot, I've seen guides to unroot only for certain phones.
mrbarbz said:
bleepsake, can't wait to see your video.
Is unrooting unique per phone or is it the same? When I search unroot, I've seen guides to unroot only for certain phones.
Click to expand...
Click to collapse
mrbarbs all you need to do to unroot is use odin and flash Official samsung firmware over the top of what you have. Done... its that easy no need for a guide lol
this will also get rid off CWM and put the stock original recovery back in and also stock kernel.... as a matter of fact stock EVERYTHING
Hello All, Before you ask no the phone is not stolen. I'm a idiot but not a thief. So I wanted this phone for a while and I saw it at a pawn shop while in Oregon on vacation. So I purchased it sorta cheap with the original box cables books the works in mint condition. The phone did not come with the prior users information so I did a Hard Reset from the Boot menu and now it ask for the prior persons info which I obviously don't have. Called Bullitt who informed me that they can't fix it that it is an android issue and to contact google. Which I can't seem to find information for. So tried a few of the unlock methods for other phones on youtube to no avail. Can't return the phone so unless I somehow fix it I'm out $350 bucks. =/ Any help would be appreciated.
Phone Details:
Android Version 6.0.1
08/05/2016 Security Patch
Baseband 025.01
Kernel Version: 3.10.84-perf-gb111a7d
Build Number: LTE_D0201121.0_S60_0.025.01
Solution in post #7
Re: FRP bypass
Sorry to hear. Not too long ago in the past, you could hit google and bypass FRP in minutes on the first attempt. Now, FRP bypass how-to's have become a great ad pusher, and 95% of the info has been patched.
Save yourself multiple headaches, and put your research into learning how to flash a new rom. That info will be much more reliable, you'll get a much better Android version, and frp will be gone.
Hic_Svnt_Dracones said:
Sorry to hear. Not too long ago in the past, you could hit google and bypass FRP in minutes on the first attempt. Now, FRP bypass how-to's have become a great ad pusher, and 95% of the info has been patched.
Save yourself multiple headaches, and put your research into learning how to flash a new rom. That info will be much more reliable, you'll get a much better Android version, and frp will be gone.
Click to expand...
Click to collapse
Thanks for the reply, I actually did try to see if I could just unlock the boot loader and flash a new Nougat Rom to it since it's almost a vanilla version of Android OS but couldn't really find anything along the lines of posts that might break down how to go about unlocking the boot loader. =/
There was a guy here who showed how to overwrite GAM as a user app using DirtyCow. I can confirm it is possible to get a root shell with DirtyCow and replace files in memory on the S60. His FRP bypass looked like it would work for you. Look on youtube, it's about a 15 minute long video.
The version of DirtyCow that worked on my S60, partially, was found here in D1kiy's "Universal Debloater" package. I don't have a Windows machine so I just used those files manually through ADB to replace run-as. There's nothing made specifically for this phone, so you'll have to use your brain and cobble these methods together. Basically, where he goes into the shell and uses the cat command, I would try to create that file and use the "dirtycow64 <file> <location>". You could TRY to install D1kiy's run-as and use "run-as exec cat <file> >> <location>", but I don't know if that will work or not. It didn't work to disable packages on my phone, and it's more steps.
What I'm trying to do is replace my hosts file with a larger one, which of course can't be done directly with DirtyCow. If you get any farther towards real root than removing FRP, please let me know. Good luck!
aff3p said:
There was a guy here who showed how to overwrite GAM as a user app using DirtyCow. I can confirm it is possible to get a root shell with DirtyCow and replace files in memory on the S60. His FRP bypass looked like it would work for you. Look on youtube, it's about a 15 minute long video.
The version of DirtyCow that worked on my S60, partially, was found here in D1kiy's "Universal Debloater" package. I don't have a Windows machine so I just used those files manually through ADB to replace run-as. There's nothing made specifically for this phone, so you'll have to use your brain and cobble these methods together. Basically, where he goes into the shell and uses the cat command, I would try to create that file and use the "dirtycow64 <file> <location>". You could TRY to install D1kiy's run-as and use "run-as exec cat <file> >> <location>", but I don't know if that will work or not. It didn't work to disable packages on my phone, and it's more steps.
What I'm trying to do is replace my hosts file with a larger one, which of course can't be done directly with DirtyCow. If you get any farther towards real root than removing FRP, please let me know. Good luck!
Click to expand...
Click to collapse
Hey Thanks for that info. been trying to get this method to work for the past 4 hours to no avail, but I do see progress. I think I just need to find all the correct files to overwrite. I'll do a write up as soon as I figure out the FRP Removal process.
aff3p said:
There was a guy here who showed how to overwrite GAM as a user app using DirtyCow. I can confirm it is possible to get a root shell with DirtyCow and replace files in memory on the S60. His FRP bypass looked like it would work for you. Look on youtube, it's about a 15 minute long video.
The version of DirtyCow that worked on my S60, partially, was found here in D1kiy's "Universal Debloater" package. I don't have a Windows machine so I just used those files manually through ADB to replace run-as. There's nothing made specifically for this phone, so you'll have to use your brain and cobble these methods together. Basically, where he goes into the shell and uses the cat command, I would try to create that file and use the "dirtycow64 <file> <location>". You could TRY to install D1kiy's run-as and use "run-as exec cat <file> >> <location>", but I don't know if that will work or not. It didn't work to disable packages on my phone, and it's more steps.
What I'm trying to do is replace my hosts file with a larger one, which of course can't be done directly with DirtyCow. If you get any farther towards real root than removing FRP, please let me know. Good luck!
Click to expand...
Click to collapse
Finally after about 30 hours of playing with this Phone I managed to bypass the FRP I will do a write up so others have an easier time.
Solved: Caterpillar S60 FRP Unlock / Bypass / Removal
Must Have:
1. Security update no later then November 2016
2. OTA Cable
3. Download of files https://we.tl/oNjiyfTk57 (None are mine, Credit goes to their developers)
Getting to Settings:
Log into wifi, once at prompt for prior users account info go back to Network setting go down and click on other network setting type anything highlight select all and click the 3 dot menu and select “Assist”
You will be taken to google. Just click no thanks and type settings and select settings.
1. Go to apps and click Android Pay, force stop and disable.
2. Scroll down to Drive and click, force stop and disable.
3. Go to Security and enable unknown sources
4. Go to Storage to access your OTA Cable USB drive you added programs to and hold and select all of them and copy to downloads.
5. Go back to google and type downloads and install all apps except gam6 and dirty cow and click done leaving apex launcher for last which you will open.
6. go to apps in Apex launcher and select Termux
Termux Commands:
1. apt update
2. apt install coreutils debianutils
3. Go back to downloads and hold and select gam6.apk and share to Termux
3. Go back to downloads and hold and select dirtycow.apk and share to Termux
4. Type ls (you should see both files installed)
5. type chmod 777 * (Both files should not be green)
6. back out and go to terminal
Terminal commands
1. cd ~
2. cat /sdcard/Download/dirtycow > dcow
3. cat /sdcard/Download/gam6.apk > gam6.apk
4. touch file
5. echo FFFFFFFF >> file
6. chmod 777 *
7. ./dcow gam6.apk /system/priv-app/GoogleLoginService/GoogleLoginService.apk
8. ./dcow file /system/priv-app/GoogleLoginService/oat/arm64/GoogleLoginService.odex
Back to Termix
1. ./dirtycow /system/priv-app/GoogleLoginService/GoogleLoginService.apk gam6.apk
Go to Setting:
1. Go to Downloads and install gam6.apk
2. Go to Apps and force quit and disable Google Account Manager and reinstall from factory.
3. Go to Downloads again and re-install gam6.apk
4. Go to Apps and force quit and uninstall Google Account Manager
5. Go to Apex and run “Test DPC” set up work account.
6. It should take you to accounts tab after completed. Allow it to sync to your google account
7. Click on the personal account that is not set up above the work account and set it up with your google account information and allow it to sync.
8. Go back to downloads and install gam6.apk again.
9. Go to About this phone and tap Build No. until developer options are opened.
10. Go to developers options and check the OEM Unlocking
11. Power off and restart and you should be in with your account it will prompt you to choose launcher start with google launcher and go to setting.
12. Go to “Back up and reset” and do a Factory Data Reset
13. after Factory Reset you should have FRP Removed.
I posted a wetransfer link for the files should be good for a month if you need them or if the link is taken down PM me. Most of the ideas for this FRP Bypass came from Ghostlyhaks.com I just complied what worked and what didn’t to get FRP Removed. Thanks to @aff3p for giving me a push in the right direction. Also thanks to XDAdevelopers whom I have constantly learned a few tricks from.
Once it is FRP unlocked it will download updates so if you don't want them make sure to block them upon factory reset.
Caterpillar S60 FRP Unlock / Bypass / Removal
hi everybody here is mine experiment Security update March 1,2017
Getting to Settings:
Log into wifi, once at prompt for prior users account info go back to Network setting go down and click on other network setting type anything highlight select all and click the 3 dot menu and select “Assist”
You will be taken to google download es file explorer install it open in settings left side open network and remote manager turn on. in pc ftp client copy files in to the phone
Android_6_G.A.M.apk and testdpc.apk, nova launcher.apk before dowloaded. install testdpc and nova launcher.
1. Go to Downloads and install gam6.apk
2. Go to Apps and force quit and disable Google Account Manager and reinstall from factory.
3. Go to Downloads again and re-install gam6.apk
4. Go to Apps and force quit and uninstall Google Account Manager
5. Go to Apex and run “Test DPC” set up work account.
6. It should take you to accounts tab after completed. Allow it to sync to your google account
7. Click on the personal account that is not set up above the work account and set it up with your google account information and allow it to sync.
8. Go back to downloads and install gam6.apk again.
9. Go to About this phone and tap Build No. until developer options are opened.
10. Go to developers options and check the OEM Unlocking
11. Power off and restart and you should be in with your account it will prompt you to choose launcher start with google launcher and go to setting.
12. Go to “Back up and reset” and do a Factory Data Reset
13. after Factory Reset you should have FRP Removed.
sorry for little copy paste im not good writer
Awesome work @cesarq glad to know it works with the March update too!
YZFNYC said:
Awesome work @cesarq glad to know it works with the March update too!
Click to expand...
Click to collapse
Yes thats why i write people know that working i march update not for how its do you
guys, has anyone figured out yet if this phone is rootable and if there's any way to install Nougat on it? I got 7 days more to return it if not happy with it and camera is just really bad
it work but different way. Thanks you
My friends i found a way to bypass that and is actualy very simple
So i found solution to frp on cat s60 contact me at [email protected] and i tell you how
help with FRP removal
Hello Sirs,
I have just bought a CAT S60 from my carrier as a used handset, and I've ran into this FRP problem too. I could take it back, since I have a 2 weeks guarantee for this, and they would pay me back its price, but since it was a good price, I'd rather keep it.
I've tried the solution above, I've managed to get to the google app, and searched for ES file manager, but when I click on the app, the phone tries to open google play which directs me back to the point where I should enter the previous user's data.
As far as I can tell, my ROM version is after 01. June, 2017. Or at least, I've entered android recovery, and the latest recovery log sais: ro.bootimage.build.date= Thu Jun 1 12:12:51 CST 2017.
Do you have any suggestions?
Thanks in advance
P
Solved
@Calinalex, Thank You very much for the help, worked like a charm.
:highfive:
cat s 60 frp remove SOLUTION FOUND
Much more easy and done in 5 min use instructions in video : So go to youtube and there is cat s60 frp remove , good luck AND PLS IF IT WORKS DONT FORGET TO LIKE THE VIDEO
march 1 2018
hey it work on march too
Hello, This is a work in progress guide to help you with rooting your phone for whatever reason (i root it to use the Automate app as i am lazy)
I hope this is not a total mess, i will edit this if you have too much trouble reading
DISCLAIMER /!\
• Please consider that you follow this guide at your own risks, i am a random person in the internet, if you do not trust any part of this guide, dont follow it!
• I am adressing this guide to experimented users, i have probably missed a lot of steps and i will try to correct myself, (or not, it takes time sry)
• i am from Europe; not a native english speaker + a noob in the field. feel free to criticize, but be elaborate to help others
I did this on the GALAXY A53 5G phone with :
• Build ver. SP1A.210812.016.A536BXXU1AVCC
• One UI 4.1
• Android Version 12
The following is needed in order to speedrun this :
+MAGISK25.1
+LZ4
+ODIN3.14
+YOUR BOOT.IMG (FROM THE AP_ FILE OF THE FIRMWARE)
1) On your phone go to Settings -> About phone
2) Then -> Software info
3) Check at (the 6th line) ; BUILD Versionfor me it was:
SP1A.210812.016.A536BXXU1AVCC
4) You will have to download yours at sammobile or any other website you trust more : (needs an account but then is free to download)
Download Samsung Galaxy A53 5G SM-A536B firmware
Download the latest Samsung firmware for Galaxy A53 5G with model code SM-A536B. Check out our free download or super fast premium options.
www.sammobile.com
Then when you have you files , the one that matters is the one starting with AP_
5) extract the boot.img.lz4
6) download one of the versions of LZ4 from : https://github.com/lz4/lz4/releases
7) extract all files into a folder
8) drag and drop the extracted file from part 5) INTO the .exe file from part 7)
YOU HAVE YOUR BOOT.IMG
9) Now drag and drop this Boot.img INTO your phone
The version 25.1 of Magisk (or above is needed ? as i used that version of magisk to root my phone i guess)
10) Install it on your A53 you can download it from :
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
11) inside the app, click on INSTALL (written in blue on top right)
12) select the only option
13) go to the boot.img (that you dropped into your phone at part 9)
14) wait
15) when it is done, plug your phone again if you unplugged it and drop the new file generated by MAGISK into your computer and rename it boot.img.tar
Unlock the bootloader of your phone by either ;
• Watch a tutorial it helped me understand why i kept having an error while doing the next steps (i "unlocked" OEM only within dev options, that wasn't enough)
and skip to 22)
• Or follow these steps
on your A53 go developper mode by clicking 7-10 times on the VERSION in settings -> about phone -> Software
turn on the switch for OEM unlocking (wifi must be connected if the button doesnt appear)
and i am not sure if we need to but , turn on the switch for USB DEBUGGING as well (for adb)
16) stay pressed on both VOL UP + VOL DOWN
17) plug your phone to computer
18) wait
19) long press VOL UP
20) wait
21) press VOL UP
ez
So now get ODIN 3.14 on ur computer
I got the official website but cant remember where from, i will look into it, maybe you can find it on google but be carefull of malicious ones i swear !
(if you are kind enough you will share it below ♥)
22)after launching ODIN
23)The on the AP button put your boot.img.tar file that you got from part 15)
24) on your A53 go developper mode by clicking 7-10 times on the VERSION in settings -> about phone -> Software
25) check that you wave wifi connected
26) go to dev options and check if OEM unlock is grey'd out
30) turn OFF your A53 phone
wait for it to BZZZZZZZZ (viber)
31)STAY PRESSED onto the 2 buttons VOL UP + POWER
on recovery choose the 2nd option with your volume keys, "reboot to bootloader"
then if odin recognise the phone press start
This looks like a great guide. Too bad OEM Unlocking doesn't appear on US carrier phones, or else I'd totally do this :/
sorry if i sound stupid but how do i get the boot.img.lz4 file?
This does NOT work on VD7 or most likely later with Magisk 25.1/25.2 (the BL is unlocked on this SM-A536B as I get the warning on reboot and the OEM unlocked is on and greyed out in developer options).
I used the patch the entire AP file method in Magisk and flashing the patched AP file (you can google T505N XDA root Samsung; I will find the forum link later and remember to post it here (this method works on VD7 and probably higher)
I am now rooted with TWRP, thanks to this site, https://www.droidwin.com/install-twrp-recovery-and-root-samsung-galaxy-a53-5g/
Still cannot delete system/app, system/priv-app (not even in twrp) but am able to access data/app (and remove .digest and .dm files)
crazyut said:
I used the patch the entire AP file method in Magisk and flashing the patched AP file (you can google T505N XDA root Samsung; I will find the forum link later and remember to post it here (this method works on VD7 and probably higher)
Click to expand...
Click to collapse
Confirmed, works with VG1 and latest VGA. I used patched AP along with BL, CP and (Home) CSC. Please note that you have to do a factory reset after this, so remember to backup your data properly.
Hlo I rooted my a53 5g thanks to you but cannot remount system partition as read write
I get this output after running
Code:
mount -o remount,rw / <
'/dev/block/dm-0' is read-only
Please help me with it
And also cannot disable dm-verity flashed disable-dm-verity.zip but after formatting data device stuck in bootloop...
Hello. I am new to programming. I have a rudimentary knowledge of android, i.e. whatever I figured out while jailbreaking JP5 and JP6 Securus tablets, and I await academic coursework for formal education in computer hardware and software engineering.
Clarity and redundancy is greatly APPRECIATED regarding any replies to my post.
The question(s) are, what benefits would I obtain from rooting my A53, what about the Cons? I Can I improve the performance of my phone, processing data, etc.
Afterwards in the future, can I still flash the Android 13 firmware? Does Samsung find out?
I know I have to read up, I am being lazy.
THANK YOU.
JoseAndDiezel104 said:
Hello. I am new to programming. I have a rudimentary knowledge of android, i.e. whatever I figured out while jailbreaking JP5 and JP6 Securus tablets, and I await academic coursework for formal education in computer hardware and software engineering.
Clarity and redundancy is greatly APPRECIATED regarding any replies to my post.
The question(s) are, what benefits would I obtain from rooting my A53, what about the Cons? I Can I improve the performance of my phone, processing data, etc.
Afterwards in the future, can I still flash the Android 13 firmware? Does Samsung find out?
I know I have to read up, I am being lazy.
THANK YOU.
Click to expand...
Click to collapse
While I don't have a Galaxy A53, I can speak from experience that almost all Samsung phones suffer from the same pros and cons to rooting
Let's start with the pros:
Using a system-wide adblocker like Adaway is much more battery friendly and more effective using it on root mode than any non-root alternative. This one is the main reason a lot of people root and I think it merits it, it's a really amazing ad blocker.
You'd be able to activate some features that Samsung likes to disable on A-series, like full edge lighting and the camera privacy toggle (I don't know if it's disabled on A53 by default but I'm leaning towards yes)
You get to experiment with GSI and maybe some custom ROMs in the future
You can install some neat Magisk modules like the Pixelify module for example, that tricks Google Photos and lets you have unlimited space like the Pixels have.
With root, you have almost unlimited possibilities of modding your phone, it's just a matter of knowing what you want to modify and finding the right mods to it.
Now, the cons:
Samsung phones have an e-fuse. Flashing custom firmware automatically trips this fuse and it is impossible to recover from unless you change the motherboard. When this fuse is blown, you will never be able to use Samsung's security features like Samsung Pass, Pay, Secure Folder, Secure Wifi, etc...
Even if you flash your stock firmware and even if you re-lock your bootloader, the fuse will still be blown.
There are some regions which even deny any warranty claims if they find out that this fuse is blown, but some places in Europe still accept the phone in this condition.
Another con is that sometimes some apps refuse to work if they detect you are rooted like Google Pay and I believe Netflix and others too (like banking apps). Some are easy to fool/bypass root detection and some are more complicated. It all depends on the app.
And to answer your final question. Fortunately for you, you still should be able to flash the latest stock firmware and if you re-lock your bootloader, you should still be able to receive updates via OTA, just keep in mind of the services that will never work again I mentioned above
Hello. I am following up with my previous post.
I found the exact zip and Odin file at Sammobile. Would this be a good start? My understanding is that the bootloader option is not available yet
...
I am learning as I go and before I move forward (big IF) I want as many redundancies as I can.
JoseAndDiezel104 said:
Hello. I am following up with my previous post.
I found the exact zip and Odin file at Sammobile. Would this be a good start? My understanding is that the bootloader option is not available yet
...
I am learning as I go and before I move forward (big IF) I want as many redundancies as I can.
Click to expand...
Click to collapse
I din't have unlocking bootloader option. But I did:-
1)factory reset phone
2)insert sim
3)restart phone
4)enable developer mode
5)And you will get a message "Welcome to Samsung your device is registered"
6)that's it OEM unlocking option will be avilable
7)power off phone
8)holding vol +&- keys connect usb to pc
9) leave both keys after you see waring messages
10)press and hold volume + key , bootloader will be unlocked and phone will be factory resetted.
aryanrh said:
I din't have unlocking bootloader option. But I did:-
1)factory reset phone
2)insert sim
3)restart phone
4)enable developer mode
5)And you will get a message "Welcome to Samsung your device is registered"
6)that's it OEM unlocking option will be avilable
7)power off phone
8)holding vol +&- keys connect usb to pc
9) leave both keys after you see waring messages
10)press and hold volume + key , bootloader will be unlocked and phone will be factory resetted.
Click to expand...
Click to collapse
Would this work for US phones?
nsfxpython said:
Would this work for US phones?
Click to expand...
Click to collapse
Unless you find a a hack, any U/U1 (USA/United States/The States/States/American/America) and W series (Canada) phones have not been bootloader unlock or root for the last 5+ years or more. If you want root options, get a B (EU/UK) or E series phone.
crazyut said:
Unless you find a a hack, any U/U1 (USA/United States/The States/States/American/America) and W series (Canada) phones have not been bootloader unlock or root for the last 5+ years or more. If you want root options, get a B (EU/UK) or E series phone.
Click to expand...
Click to collapse
Is there any way to recover deleted pictures in the Samsung A53 5G (USA version) if it is impossible to root this version of the phone?
I accidentially manually deleted some photos in my phone today with my computer (so it doesn't appear in the photo's trash bin), and every single recovery program I encountered says I need to root my phone in order to use a deep scan to look for the deleted files.
I have litte hope that there is anything to recover. Despite the fact that us versions can't be unlocked what would be necessary for rooting, flash storage management (also garbage collection, trim etc.) tends to shift data all the time to other/new cells making it unlikely for you to recover lost data on an active device. Better backup from time to time, always your best bet.
Hello! Im having an issue, maybe im doing somthing wrong. I'm at 13) After giving the img.boot.lz4 i wait and wait and the memory of the phone fills completly (Around 120+Gb) and the patched img do not comes out, any thougths?
This is a deprecated method. You have to patch the whole AP file with magisk and flash it along with BP, CP and (Home) CSC after you've unlocked the bootloader.
Andoreid said:
This is a deprecated method. You have to patch the whole AP file with magisk and flash it along with BP, CP and (Home) CSC after you've unlocked the bootloader.
Click to expand...
Click to collapse
That's right, but for folks with no experience rooting new Samsung devices, please:
- DO read OP's "Unlock bootloader" section. Visitors to this page who skip to the end and have never rooted non-Samsung or older devices might think "adb reboot fastboot" followed by "fastboot flashing unlock" or "fastboot oem unlock" will do the trick. It won't. To clarify: fastboot will NOT recognize this phone, which is normal because it doesn't have a standard fastboot mode, and simply enabling "Allow OEM unlock" in developer settings is necessary but not enough.
Do follow OP's steps for unlocking.
- For rooting, I followed the instructions here https://samsungusbdriver.me/root-samsung-galaxy-a53-5g/ (second method).
But the instructions on that page for getting the actual model number and CSC for Frija are unclear. Finding that information was not straightforward. Depending on the method I used, the model number would be SEPF_SM-A536B_12_0001, SM-A536B/DS, A536B... and you need to know CSC stands for "country-specific code" and it's a 3-character code. I eventually figured out my model was SM-A536B and CSC was EUX. But it took quite a bit of research.
-If you're not familiar with Magisk's DenyList, google it. You might have to use it some apps, particularly banking apps. I think you need it for Netflix, too. Speaking of Netflix, the version that comes preinstalled won't work after rooting. The way I got it to work was uninstalling that version and sideloading the Netflix APK from Apkpure. And adding it to Magisk's DenyList.
Hello,
I have a rooted (Magisk) A53 with TWRP. For a week, I get a notification asking me to update to security patch level of May 1st, 2023. I thought that with unlocked bootloaders, OTA wasn't possible, but whatever. My question is if it's possible to perform the update without losing TWRP and Magisk, and also if it's possible to keep all user data and installed apps. I have little time to spare after work and really don't want to go again through the process of resetting my phone.
Thanks.