Related
[GUIDE] How to upgrade, root & flash Samsung Galaxy Ace S5830 [DOWNLOAD LINKS | CWM5]
Hey guys,
in this tutorial I will show you how to upgrade and root your Samsung Galaxy Ace S5830. This method is the simplest way to do it.
Shall not be liable for any resulting damage to your phone! Everything you do at your own risk!
If you want to upgrade to newer version then Gingerbread I suggest you to make full procedure, not only flash recovery.
WARNING
If you don't understand what is root, ROM, phone, flash, CMD etc. watch this movie
You will need these files:
Brain
PC with Windows XP SP2 or later
Samsung Galaxy Ace GT-S5830
USB to Micro-USB cable
.Net Framework 2.0 or later
Android Software Development Kit (SDK)
Samsung Kies or Samsung Android USB Drivers
ODIN 4.38 + OPS
SuperOneClick (for 2.2> firmwares) or Universal Gingerbread Root or Unroot (for 2.3< firmwares)
ClockworkMod Recovery 5.0.2.6 (Fixed!)
New firmware
*Optional Custom ROM
Newest firmware:
Release name: S5830DXKT7
Release date: November 2012
Country: Vietnam
CSC: S5830OLBKT3
Android Version: Gingerbread 2.3.6
DOWNLOADS
Dropbox
Google Drive
YouTube Tutorial
Thanks to GadgetCheck!
A. Preparing your PC:
Install .Net Framework 2.0
Install Android SDK
Download SDK Tools & Platform-tools in Android SDK
Right click on Computer and select Properties
Select Advanced System Settings then Advanced and Click the Environment Variables button.
Click on the variable called 'Path' and then click on Edit. Now add the target directory to the value of the variable, using a semi-colon as a separator.
Add system path to Android SDK and Android SDK Tools folders
x86
Code:
C:\Program Files\Android\android-sdk
C:\Program Files\Android\android-sdk\platform-tools
x64
Code:
C:\Program Files (x86)\Android\android-sdk
C:\Program Files (x86)\Android\android-sdk\platform-tools
Now your PC is ready!
B. Preparing your phone (only for 2.2.x users! If you only want to root your phone, go to step D, if your phone don't have root skip this steps):
Install Samsung Kies
Turn on your phone
Enable Debugging at Apliccations>Programming
Connect your phone into PC via cable
Launch SuperOneClick
Click "Unroot"
Wait
When the process is complete turn off SOC and unplug your phone
Reboot to apply changes
Now you have unrooted phone!
C. Flashing the newest firmware:
Turn off your phone
Remove your SIM Card and SD Card
Extract previously downloaded firmware
Open ODIN 4.38 on your PC and change OPS file name to
Code:
Cooper_v1.0.ops
Select from extracted archive: OPS-OPS, Boot-APBOOT, Phone-MODEM, PDA-CODE, CSC-CSC (leave EFS and One Package empty)
If archive contains only <filename>.tar.md5 select it as PDA and OPS as OPS, leave other fields EMPTY
Connect your phone via USB into PC
When the screen is turned on hold POWER+VOLUME DOWN+HOME and wait until the phone enters the Download Mode
If ODIN detected and recognized your phone should light up the first square to the left side
Press "Start" button and wait, the process should take ~5 minutes
If all goes well your phone should reboot automatically
Square should change the color to blue and display "PASS" it means that flashing process was successful and we have the newest firmware
Disconnect your phone
Turn off your phone
Insert your SIM Card and SD Card again
Turn on your phone
Now you have the newest firmware!
Da. Rooting for 2.2.1:
Turn on your phone
Enable Debugging at Apliccations>Programming
Connect your phone into PC via cable
Launch Super One Click 2.3.3
Click "Root"
Wait until the program will root your phone
When the process is complete turn off SOC and unplug your phone
Reboot
Now you have root!
Db. Rooting for 2.3.x (NEW METHOD!):
Download file called universal_gb_root_v25.zip and copy it to your sdcard
Turn off your phone
Press POWER+HOME BUTTON
Select update from sdcard, select the file universal_gb_root_v25.zip
After the update completed - reboot
Now you have rooted S5830
OPTIONAL Unrooting for 2.3.x:
Download file called universal_gb_unroot_v9.zip and copy it to your sdcard
Turn off your phone
Press POWER+HOME BUTTON
Select update from sdcard, select the file universal_gb_unroot_v9.zip
After the update completed - reboot
Now you have unrooted S5830[/QUOTE]
OLD ROOTING METHOD FOR 2.3.x
Rooting for 2.3.x (Thanks to russian forum-user with nickname may213) (if it doesn't work try D method):
Code:
upd_1.zip [URL="https://hotfile.com/dl/193725879/700f6be/upd_1.zip.html"]HotFile[/URL]
Download file called upd_1.zip and copy it to your sdcard
Turn off your phone
Press POWER+HOME BUTTON
Select update from sdcard, select the file upd_1.zip
After the update completed - reboot
Now you have rooted S5830
Unrooting for 2.3.x (Thanks to ingbrzy) (if it doesn't work try D method):
Code:
unroot.zip [URL="https://hotfile.com/dl/193725835/d31c709/unroot.zip.html"]HotFile[/URL]
Download file called unroot.zip and copy it to your sdcard
Turn off your phone
Press POWER+HOME BUTTON
Select update from sdcard, select the file unroot.zip
After the update completed - reboot
Now you have unrooted S5830
Click to expand...
Click to collapse
E. Flash Custom Recovery:
Put recovery-clockwork-5.0.2.6-galaxyace.zip into SD Card
Turn off your phone
Press POWER+HOME BUTTON
Select Update Zip From SD-Card option. [If you are on previous version of CWM recovery then you might need to select Install Zip From SD Card and then Choose Zip From SD Card Option simultaneously. ]
Select recovery-clockwork-5.0.2.6-galaxyace.zip and flash it
Reboot your device
F*. Flash Custom ROM:
Select Custom ROM
Put Custom ROM .zip into SD Card
Turn off your phone
Press POWER+HOME BUTTON
Wipe All
Select "Install zip from sd card"
Select "Choose zip"
Select .zip with your Custom ROM
Select "Yes"
Reboot into system
That's ALL!!!
Now you have the newest firmware and root and probably Custom ROM!
Please don't send me messages on IM because i don't have much time to read it and reply. I've maded special thread for problems and issues: http://forum.xda-developers.com/showthread.php?p=22230605#post22230605
If I helped you, click "Thanks" also you can vote it into main page, rate this thread or donate me
If you have problems with one of this steps post it in this thread I will try help you!
about to root mine.will let u know wat happens.
jnrphil said:
about to root mine.will let u know wat happens.
Click to expand...
Click to collapse
What do you mean?
it worked!!!thanx
You're welcome
Sent from my GT-S5830 using XDA App
hubix said:
You're welcome
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Why I cannot find the DXKC1 firmware?
Hello, i need FW DXKC1. Can you help me? I don't find it on samfirmware . Please!!!
P/S: Sorry for my bad english ~.~
Where are you from? I need to know this to tell you the newest available ROM for your phone.
Sent from my Samsung Galaxy Ace GT-S5830 using XDA App
i'm from Vietnam, my FW is XXKC1 but i need DXKC1
I have found the problem, sometime my ACE freeze
when the phone freezes,and i have to take the battery out to get it work.
hi hubix, do you know where to find this galaxy rom: S5830DXKA9 if you know please post a link. or do you know how to extract a rom from galaxy ace because i want to share my S5830DXKB1 firmware which i currently have now.
If you can't find it at samfirmware it doesnt exist. Link: http://www.samfirmware.com/WEBPROTECT-S5830.htm
The newest Asia firmware is S5830ZCKA7
I've related names of the newest ROM for any continent in the 1st post.
Sent from my Samsung Galaxy Ace GT-S5830 using XDA App
hubix said:
If you can't find it at samfirmware it doesnt exist. Link: http://www.samfirmware.com/WEBPROTECT-S5830.htm
The newest Asia firmware is S5830ZCKA7
I've related names of the newest ROM for any continent in the 1st post.
Sent from my Samsung Galaxy Ace GT-S5830 using XDA App
Click to expand...
Click to collapse
Actually, i'm from the philippines and when i connec to Kies its prompting me to upgrade my firmware from xxxxDKA9 to xxxxDKC1, so i assume it is an asian firmware, but when i check in samfirmware.com this xxxDKC1 is under the European firmware. Nonetheless, i have upgraded my firmware via kies and now it is xxxDKC1, and i dont see any issue/s on it so far.
It fixes wifi disconnecting bug, LED Flashlight + stock camera program bug and it's more stable for me
Sent from my Samsung Galaxy Ace GT-S5830 using XDA App
Congratulations body, very good explained , very good tutorial!
Thank you very much
can't open downloaded attachments
i can't open downloaded attachments, another mirror please...
I've edited 1st post. Now you have official mirrors there
hubix, thank you...
tomdotnet said:
hubix, thank you...
Click to expand...
Click to collapse
No problem
i've followed all the steps and Odin detects the device, but when i start the process the phone never reboots - keeps the "Downloading..." text in the screen - and i'm "stuck" at the first step, "mibib download..". any ideas?
this is the debug message..
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> mibib download..
I flashed the UK sbf via RSDLite and then when I tried flashing the brazil sbf again I could not, right now I can no longer flash via RSDLite. Keeps on gettiing a 0x71000 error.
info5i2002 said:
I flashed the UK sbf via RSDLite and then when I tried flashing the brazil sbf again I could not, right now I can no longer flash via RSDLite. Keeps on gettiing a 0x71000 error.
Click to expand...
Click to collapse
I was running into the same problem, with Win7 x64, RSD Lite 4.6, latest drivers. Did some investigation into the error log and looks like I found a bug in their programming. Go into the directory you installed RSD Lite (for Win7 x64 the default is C:\Program Files (x86)\Motorola\RSD Lite\) and look for a file that starts with "FlashErrorLog". Open it, and if you see something like this:
Code:
Code:
Line: 865
ERROR: \\?\c:\SPRecovery_ESE81.sbfwtƒyoþÿÿÿ‚qawñrawðiµ was not found.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashFi leIO.cpp
then you are experiencing this same bug that I had (looks like adr3nalin3 had this problem too). For those fellow programmers out there, looks like they are copying the filename into uninitialized memory and not explicitly adding the NULL terminator, meaning it's pure luck whether the filename is recognized or not. Since the uninitialized memory produces random results, this explains why people have had it work after restarting their computer, trying several times, using a different computer, etc. Hopefully if you follow my instructions below, you will be able to make it work right away.
So the work around for this problem is to rename the file so that the real filename overwrites all the unwanted junk characters at the end. These junk characters are random, and they are likely to change each time you open RSD Lite.
Here are step by step instructions:
Go to the folder where you installed RSD Lite
Delete any files that start with "FlashErrorLog"
Right click on "SDL.exe" and click "Run As Administrator"
Move your recovery file to the root C:\ directory
Rename the recovery file to something short, like "r.sbf", so that you will have space left for the filename to overwrite the junk characters
Try flashing the file with RSD Lite - it will most likely fail, don't worry (if it works then good job, you are lucky )
In the RSD Lite folder, open the newly created FlashErrorLog... file
Count the number of junk characters after the real filename - for example if you have this error:
Code:
Code:
ERROR: \\?\c:\r.sbfqawñraï was not found.
then the junk characters are "qawñraï" and there are 7 of them, so we are going to add 7 extra letters to the real filename
Rename the file to add the same number of letters/numbers as junk characters in the log file. In this case, we need to add 7, so change the filename to something like "r1234567.sbf" - make sure you add the characters BEFORE the file extension (".sbf"), not after!
Point RSD Lite to the renamed file, click Start, and it should work!
Note that some of the junk characters can't be displayed in the log, so there might actually be 8 of them when you can only see 7, etc. Just repeat the process from step 6, adding 1 character at a time (don't remove any), and it should work after a few tries.
Note that just making the filename really long won't work, you need to be precise so that you only overwrite the extra stuff, nothing more and nothing less.
Click to expand...
Click to collapse
Find Original post here: http://androidforums.com/droid-all-things-root/74153-if-you-get-failed-flashing-process-0x7100-rsd-lite.html
At #32 reply.
I just mis-clicked thanks when I want to quote your post.
Haha I returned the favour by thanking you too. By the way, all I had to do was to delete the error logs and then enter the
Code:
cd C:\Program Files\Motorola\RSDlite\
SDL.exe -f [FILENAME].sbf -t 2
and it starting flashing again.
Good luck!
I tried manualy updating my I9000 to gingerbread through odin. the update fail however and now kies wont reccognise my phone. when i try to boot the phone it show a picture with a phone, a pc and an exclamation mark. what should i do?
Since u can see that pc icon means u can get into download mode also... Ie volume down + home + power... Now see that biggest file frm ur download ie pda/code......tar has the boot.bin and sbl.bin files... If yes just reflash it again... If now download sme othr gingerbread version with those two files and flash... just search for ramads thread in this section...
I mean this thread...
http://forum.xda-developers.com/showthread.php?t=1102881
thank you. i was trying to find that thread lol. Is going from eclair to gingerbread going to work or not? trying to find what the problem was.
If you're going between major versions you should do a factory reset (clear the /data section) as your apps may work differently and take advantage of new features. Not doing a factory reset may cause certain apps to FC.
Should work going straight from E to G though.
cheers guys. got everything working now.
Hi, may i know what happen if i can't go into download mode? But i still have the pc image.
Any solution?
fuuuuuuuuuuuuuuuuuuu. i think i have finaly ****ed up my phone. my dad accidently turned off my pc while i was flashing a galnet miui build with heimdall. i got into download mode but had to go out. when i came back my battery was dead and i cant charde the phone or get it into download mode. Any suggestions ?
edit: got it into download mode but odin doesnt recognise it
Try this:
prerequisite : the tools I used will only work on linux, so get yourself a ubuntu, or run one using virtual machine on windows, also install java (running sudo apt-get install openjdk-7-jre should be enough).
download UnBrickable Ressurector, code . google . com/p/hummingbird-hibl/downloads/list -> this is the reason for ubuntu only
run the downloaded jar file using sudo (it need root permission to run properly).
remove your phone battery, plug the usb cable in (connected to your computer), then reinsert your phone battery
now you have about 2s windows of opportunity to click that "Perform Ressurection" button.
wait and your phone should now be in download mode.
now this download mode is a bit weird.. if you unplug the usb cable, the phone will go straight back to the blank screen, and you have to do the whole process all over again.. which is why, we're going to reflash and fixed the phone using heimdall. the flashing process is a bit different with odin, here's how :
download heimdall www glassechidna com au/products/heimdall/ and the frontend
open it using sudo (sudo heimdall-frontend)
extract the rar files you got here, and you will get 3 tar.md5 files.
extract all those files, BUT make sure that you extract the csc files LAST, also choose OK when you're asked to overwrite. you will get 8 files
now we're going to download the correct pit file : in heimdall choose the "utilities" tab, click on "detect", and it should print out "device detected". click save as, choose a name (don't need to put .pit as part of its name), and click download
switch to "flash" tab, then browse for the created pit file. the "add" button should be enabled now.
now you need to add all the extracted files one by one and it has to be in the correct partition name, here's the list :
kernel -> zImage
IBL + PBL -> boot.bin
CACHE -> cache.rfs
dbdatafs -> dbdata.rfs
factoryfs -> factoryfs.rfs
modem -> modem.bin
param -> param.lfs
SBL -> Sbl.bin
hit start, and the flashing should start. if all goes well, your phone should boot normally now
stef.t97 said:
edit: got it into download mode but odin doesnt recognise it
Click to expand...
Click to collapse
Gadget serial at Devica Manager - missing driver files, install SAMSUNG_USB_Driver_for_Mobile_Phones
I have a method for rooting stock 2.3.4 on Droid 2/R2D2, but I can't post howto/links because my account is new. There's now a bootable EzSBF image that will update your phone to stock 621 and give you the option of rooting it, courtesy of beh (bhigham)
The thread is here:
rootzwiki.com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/
Not to be rude but....I have to call BS.
Sent from my Droid Incredible using xda premium
months formaj
Albinoman said:
Not to be rude but....I have to call BS.
Sent from my Droid Incredible using xda premium
Click to expand...
Click to collapse
Understandable since I appeared out of nowhere.
Well, I posted it on rootzwiki. It's an exploit in loadpreinstall.sh. You can make a symlink in /data/preinstall_md5/ to /data/local.prop, create a dummy file in the preinstall /app dir and instead of a md5sum, put a copy of local.prop that contains ro.sys.atvc_allow_all_adb=1. When the system thinks it's copying an md5 sum to your preinstall md5 cache, it hits the symlink and overwrites the local.prop, giving adb root access on next reboot. It seems you can put whatever you want in CG66 and the phone boots just fine. This probably works on quite a few motorola devices
phifc said:
Understandable since I appeared out of nowhere.
Well, I posted it on rootzwiki. It's an exploit in loadpreinstall.sh. You can make a symlink in /data/preinstall_md5/ to /data/local.prop, create a dummy file in the preinstall /app dir and instead of a md5sum, put a copy of local.prop that contains ro.sys.atvc_allow_all_adb=1. When the system thinks it's copying an md5 sum to your preinstall md5 cache, it hits the symlink and overwrites the local.prop, giving adb root access on next reboot. It seems you can put whatever you want in CG66 and the phone boots just fine. This probably works on quite a few motorola devices
Click to expand...
Click to collapse
Well it looks like I have to retract my previous statement. Great job!
Sent from my Droid Incredible using xda premium
D2 "ezSBF" 2.3.4/4.5.621 with magic md5 root option
updated many times see change log
root created by phifc modified by bhigham
3 options mirror links posted Magic MD5 Root 2.3.4 for D2, R2D2, D2G, DX and 2.3.5 for DX2 - Google Docs
Multi-Device Root (54mb)
Droid2_621_SBF-and-RootCD.iso (213mb)
Droid2_R2D2_A957_2.3.4_SBF_and-or_RootCD.iso (250mb
How this works
Originally Posted by phifc
There's an exploit in loadpreinstall.sh. It compares md5 sum files of preinstalled apps and if they're different, copies the md5 to the local cache. The preinstall just has an empty file in app/ so it will parse the md5 for it. Instead of an md5 sum, it contains a local.prop that allows adb root shell. So the system thinks it's copying the md5sum to the cache when it bounces off the symlink and overwrites the /data/local.prop, giving adb root on next reboot
Click to expand...
Click to collapse
what is ezSBF?
original [TOOL] ezSBF (not for 2.3.4)
1KDS said:
Don't let the word Linux scare you, this is just a cd you burn, nothing installs to your pc. Once you burn this CD you are ready to SBF flash anywhere you have a computer, no net connection needed to download any files.
This is an .iso file. It is a complete Linux operating system that you will download, burn to CD (or USB) then boot your pc from CD or USB, this allows your pc to reboot into a different operating system.
Click to expand...
Click to collapse
1KDS said:
Instructions (Mac):
Download .iso
Use Disk Utility (built in) to burn iso file to a CD (instructions)
Shut computer down
Hold c key, push power and hold c until you see the Linux OS start
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Instructions (Windows):
Download .iso
Burn iso image to a disk (Instructions, Windows 7 - Vista and XP) or (Load to a USB flash drive)
Reboot PC
Hit F12 (sometimes F8 or esc) during boot to go to boot menu (possibly google search how to boot your specific pc from CDROM)
Select boot from CDROM (or USB if you used a flash drive)
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Live USB Instructions (Windows):
(Instructions from pendrivelinux.com)(thanks)
Download UNetBootin for Windows
Download your favorite Linux ISO
Double click the Unetbootin Executable to start the program
(1) Click the Diskimage radio box
(2) browse to select your ISO
(3) Set your target USB drive
(4) click OK to start the creation
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(5) After the USB drive is done select reboot.
(6) During boot enter the boot menu and change USB to boot first, save and reboot.
(7) When booting from UNetbootin select SliTaz
________________________________________________
You will now be in the script and ready to flash.
Click to expand...
Click to collapse
select D2 for multi device root cd or /select root for the Droid2_621_SBF-and-Root CD
don't use numbers on right side of you keyboard, just use the ones above qwerty
turn phone on, connect to pc with usb cable
on phone check usb debugging (settings/apps/development)
on phone select charge only usb mode
on pc press continue
program will use adb to push
Code:
data/local.prop /data/preinstall_md5/magic.md5
program will prompt you to
manually reboot phone to bootloader, To put your D2G(/D2) in bootloader mode, power down and power on while either holding both volume buttons, or the up arrow on the keyboard.
program will flash repacked sbf (less than 50mb)
program will reboot twice, very important (reboot just replaces the local.prop, but the old local.prop is still in memory, till second reboot)
adb pushes su,superuser, and busybox
program will reboot to recovery,
manually press both volume buttons when you see !, triangle, & android andy
manually select wipe cache
manually select reboot
rooted
error info
when running program you may see these errors
rm failed for /data/preinstall_md5/magic.md5 no such file or directory
no root.img.gz no such file or directory
rm failed for /data/preinstall_md5/magic.md5 read only file system
that is fine, it will still work
by bhigham -One item of note with this CD, it does require at least 1GB of RAM in order to work properly. Also, if you only have 1GB of memory, and you need to both SBF and root your phone, it will be necessary to reboot the computer after flashing the .629(or .621)SBF. If you are unsure of the amount of RAM that you have, go ahead and reboot to be on the safe side.
Also, I noticed that I neglected to put instructions for putting your phone in bootloader in the SBF Step. To put your D2G(/D2) in bootloader mode, power down and power on while either holding both volume buttons, or the up arrow on the keyboard.
Click to expand...
Click to collapse
if you plan on creating nandroid backups or flashing roms read
[HOW TO] Install/Use Droid 2 Bootstrap
Using Oracle VM VirtualBox, and Magic MD5 root iso
Older Methods see instruction by phifc below
windows Batch file (uses rsd lite)
Linux batch file (adb and sbf_flash)
Linux manual (adb and sbf_flash)
original thread New root method for stock 2.3.4 (621/622) found (Droid2, R2D2) - Droid 2 / R2D2 / Milestone 2 / Droid 2 Global - RootzWiki
Posted by phifc (OP)
This is for original Droid2 and Droid R2D2. If you have issues b
ooting after root, check the end of this post.
I've been working on root for a few days after having to flash stock 621. I've tested this with my R2D2 running 621.
7/25/2012 - Thanks to beh for putting together an EzSBF cd for this! Just burn, boot from CD and follow the directions. It can flash to the stock 621 update for those that want the stock Gingerbread image, then gives you the option to root if you like. You can also create a bootable USB stick with the iso using UNetbootin - Homepage and Downloads
Droid 2 621 EzSBF with root option
The MD5 is
e50bc7914c4852ca32e9f08f7744c056
The instructions below work, but beh's EzSBF is far superior.
If you want to use CyanogenMod 7.2 after root with this method check this post.
I've been working on root for a few days after having to flash stock 621. I've tested this with my R2D2 running 621.
Windows
Install Motorola drivers and RDS Lite.
Get RootDroid2 file, extract folder, run RootDroid2.bat and follow the instructions.
You'll have to flash the phone as part of the process.
Linux (Easy way)
You'll need adb and sbf_flash.
1) Download the RootDroid2 file, extract it wherever you like.
2) Using adb enter
Code:
adb shell ln -s /data/local.prop /data/preinstall_md5/magic.md5
3) Flash using sbf file in download.
4) Reboot
5) adb shell will now be root
Linux (Long way)
What you need: Stock SBF (thanks to droid-developers.org), custom preinstall.img, adb (from android sdk), and sbf_flash
1) Enable USB debugging on your phone and send this adb command:
Code:
adb shell ln -s /data/local.prop /data/preinstall_md5/magic.md5
2) Unpack the custom preinstall file, then reboot your phone into flash mode by holding the up arrow on the keypad. Then send the custom SBF file with sbf_flash:
Code:
sbf_flash -r --preinstall preinstall.img <stock sbf filename>
(For example, I used 1FF-p2a_droid2_cdma_droid2-user-2.3.4-4.5.1_57_DR4-51-120117-release-keys-signed-Verizon-US.sbf so the command is "sbf_flash -r --preinstall preinstall.img 1FF-p2a_droid2_cdma_droid2-user-2.3.4-4.5.1_57_DR4-51-120117-release-keys-signed-Verizon-US.sbf")
3) Wait for phone to boot after flashing, then reboot again one final time.
4)
Code:
adb shell
should give you a root prompt (# instead of $)
5)Send superuser utils from Superuser
Code:
adb shell mount -o remount,rw /dev/block/system /system
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
Code:
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 644 /system/app/Superuser.apk
adb shell mount -o remount,ro /dev/block/system /system
Thanks to Dan Rosenberg (djrbliss) and those that helped him researchhttp://vulnfactory.o...ng-the-droid-3/ for ideas
Click to expand...
Click to collapse
for basic SBF and RSD lite info read The DROID Wiki
First, where do i download all these tools like motorola drivers and RSDlite? Do i put them on my phone or my PC?
Click to expand...
Click to collapse
use pc, links are baked into text just click on name of file
moto drivers USB and PC Charging Drivers - Motorola Mobility, Inc. USA
...Where do i enter this adb command?...
Click to expand...
Click to collapse
abd in command prompt start/search cmd.exe
...What version of software will be on my droid 2...
Click to expand...
Click to collapse
same version, rooting alone doesn't change that, rooting just gives you access to change system files/settings
My Links
Magic MD5 Root 2.3.4 for D2, R2D2, D2G, DX and 2.3.5 for DX2 - Google Docs
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs
edited:
02 Oct 2012 added mac info
10 Oct 2012 added error info
19 Oct 2012 total reorganized post
26 Oct 2012 added mirror
05 Nov 2012 added 622 sbf
09 Dec 2012 major rewrite of instructions
It should....I've looked it over.
Sent from my Droid Incredible using xda premium
works!!!
Thanks for the root
Sent from my newly rooted droid 2
I can confirm it works, I just registered to let you guys know
I have been lurking here for like 3-4 months looking for a root method, and this morning I checked rootzwiki and saw this. So glad! Thanks OP!
I am currently not at home(vacation in Germany) so I can't take a picture of root checker, but it works, very easy as well.
I can confirm that this works also except I still can't install CM7 because apparently I'm not on the OTA kernel and I'm on a leaked GB one.
Sent from my Senseless Rezound
circa881 said:
I can confirm that this works also except I still can't install CM7 because apparently I'm not on the OTA kernel and I'm on a leaked GB one.
Sent from my Senseless Rezound
Click to expand...
Click to collapse
Give LiquidICS a try, I really like it so far. Or CM9, I think LiquidICS is based on that though with some improvements.
I can't post links yet, but check droidforums. net for that
I will, thanks.
phifc said:
I have a method for rooting stock 2.3.4 on Droid 2/R2D2, but I can't post howto/links because my account is new.
Click to expand...
Click to collapse
Big thanks for this! No issues rooting, and got CM9 up and running on the D2.
big thanks for this.
finally can swap over to cricket
phifc said:
I have a method for rooting stock 2.3.4 on Droid 2/R2D2, but I can't post howto/links because my account is new.
Click to expand...
Click to collapse
You my friend, don't just deserve a nice cold root beer, you deserve stock in A&W.
Thank you so much, can't wait till I get home from vacation to try it.
hey guys im having an issue.
i have a droid 2 with .621
I ran the .bat, rebooted, and attempt the sbf. it goes all the way through verifying the checksums then i get this error:
"Failed flashing process. Interface BP: Checksum error in the RAM Downloader for Flash Bootloader. File: 0x13AD (0x702C)"
The phone says SW Update In progress..
so i pulled the battery and put back in and now it goes to the bootloader and says corrupt code
I tried the sbf 3 times and redownloaded all the files 3 times.
I dont know what to do........
EDIT: i was able to sbf back to the unrooted .621. then i tried the root process again but still got the error. should i do a full factory reset then try??
EDIT: I tried flashing the root sbf one more time, and this time i still got the error, but the phone rebooted and booted up ok. i installed voodoo rootkeeper and protected root :]
yes you will get rsd lite errors, it's a repacked sbf
just ignore the errrors
if you bootloop, go to to recovery and wipe cache or data
if you can't get to recovery, reflash sbf
jwagman1 said:
hey guys im having an issue.
i have a droid 2 with .621
I ran the .bat, rebooted, and attempt the sbf. it goes all the way through verifying the checksums then i get this error:
"Failed flashing process. Interface BP: Checksum error in the RAM Downloader for Flash Bootloader. File: 0x13AD (0x702C)"
The phone says SW Update In progress..
so i pulled the battery and put back in and now it goes to the bootloader and says corrupt code
I tried the sbf 3 times and redownloaded all the files 3 times.
I dont know what to do........
EDIT: i was able to sbf back to the unrooted .621. then i tried the root process again but still got the error. should i do a full factory reset then try??
EDIT: I tried flashing the root sbf one more time, and this time i still got the error, but the phone rebooted and booted up ok. i installed voodoo rootkeeper and protected root :]
Click to expand...
Click to collapse
You will get that error you have to wait for device to say it is finished which takes maybe 5 mins or so after you get the error
supergear said:
You will get that error you have to wait for device to say it is finished which takes maybe 5 mins or so after you get the error
Click to expand...
Click to collapse
I got the "Failed flashing process. Interface BP: Checksum error in the RAM Downloader for Flash Bootloader. File: 0x13AD (0x702C)" message as well. I waited for the phone to reboot, finished the flashing process, got errors from the .bat file saying to send the info.txt file to the OP, and tried installing Titanium Backup regardless. It asked for root permission, which I granted. Then I got a message saying "BusyBox works but the "su" command does not elevate to root." I've tried it twice now with the same RSD Lite error. I'll give it another go after it finishes charging.
scubamike said:
I got the "Failed flashing process. Interface BP: Checksum error in the RAM Downloader for Flash Bootloader. File: 0x13AD (0x702C)" message as well. I waited for the phone to reboot, finished the flashing process, got errors from the .bat file saying to send the info.txt file to the OP, and tried installing Titanium Backup regardless. It asked for root permission, which I granted. Then I got a message saying "BusyBox works but the "su" command does not elevate to root." I've tried it twice now with the same RSD Lite error. I'll give it another go after it finishes charging.
Click to expand...
Click to collapse
I don't know if this means anything, but after rooting, I had to reinstall busybox (there's an app in the market) but the newest version didn't work. I had to install 1 version back.
Sent from my rooted DROID 2! Much thanks to phifc from rootzwiki for the 2.3.4 .621 root!
fixed sbf fails everytime and I've waited 10this to 15you min after each fail msg in rsdlite..phone never reboots and when I pull the battery and reboot the phone it gos straight into bootloader which says its corrupt..
Hi,
I would like install at the Samsung SM-A515F the Lineage OS and the TWRP. I found only TWRP for the SM-A50. And the flashing dose not work for this phone.
I has try it with Heimdall and Odin.
The recovery I had downloaed from this Page:
https://www.droidthunder.com/install-twrp-recovery-on-galaxy-a51/
Need help or better information, if there exist an TWRP and lineage for this device.
Regards tiptel170
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
sankhauaa said:
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
Click to expand...
Click to collapse
s 10 page? which one is that? can u please provide the link?
Go here for odin flash method without twrp
sankhauaa said:
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
Click to expand...
Click to collapse
sankhauaa said:
Go here for odin flash method without twrp
Click to expand...
Click to collapse
so does this method work for lineage os on A515F too?
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
ibtsam3301 said:
so does this method work for lineage os on A515F too?
Click to expand...
Click to collapse
I m not tried. But someone in this a51 group tried.Its working. But not so easy .
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
tiptel170 said:
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
Click to expand...
Click to collapse
Don't pay.Its fake
tiptel170 said:
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
Click to expand...
Click to collapse
of course it would be fake
How can I open the img-files in the Linux desktop?
Found here this link, for the Magisk in the A515F:
https://forum.xda-developers.com/ga...w-to-root-samsung-a51-sm-a515f-t4032389/page2
I'll found this:
1. https://www.androlite.com/2020/01/twrp-root-samsung-galaxy-a51.html
2. https://appslova.com/install-twrp-on-samsung-galaxy-a51/
This links look likes good, because, my phone will not start or the heimdall goes into the error (likes in de page one, the screenshots ).
I found this, and I used basic from this page: https://forum.xda-developers.com/showpost.php?p=82241115&postcount=70
My first steps to install the lineage os 17 on the SM-A515F
Lineage: https://sourceforge.net/projects/andyyan-gsi/
All commands in the linux terminal, the path please use your own paths you like it!
Unpack lineage****.xz:
unxz lineage*.xz
1) Extract the AP_file.tar.md5 from your firmware.zip file using 7zip
2) Extract the super.img.lz4 file from the AP_file.tar.md5 file using 7zip
3) Put super.img.lz4 file in LZ4 folder and run in CMD the command
lz4 -d super.img.lz4 superLZ4.img
4) Put superLZ4.img file in Simg2img folder and run in CMD the command
chmod 777 ~/bin/otatools/bin/simg2img
~/bin/otatools/bin/simg2img superLZ4.img superSIMG.img
In Linux OR Bash shell:
1) Put superSIMG.img in otatools/bin folder and extract it in Linux terminal using the command
chomd 777 ~/bin/otatools/bin/lpunpack
~/bin/otatools/bin/lpunpack --slot=0 superSIMG.img ~/1
2) Put, in the folder where you extracted superSIMG.img, the GSI file you downloaded and rename it to system.img. Now you should have odm.img, system.img, vendor.img and product.img files in the same folder.
You may also need to delete/remane the original system.img file before renaming the GSI file.
3) Now you’re going to make a brand new super.img file containing all 4 files of the previous step. This is a critical and tricky step. Run Linux terminal and type:
chomd 777 ~/bin/otatools/bin/lpmake
~/bin/otatools/bin/lpmake ~/bin/otatools/bin/lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:4294967296 --group main:4293513600 --partition system:readonly:1959841792:main --image system=./system.img --partition vendor:readonly:680239104:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
4) Make an tar file:
tar -H ustar -c super.img > lineageos17.1_SMA515F.tar
5) Goto Windows -> Odin -> AP, put the file lineageos17.1_SMA515F.tar in to the AP-slot -> Start
This is what I has done:
But, by the compiling, I got this error:
Code:
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition system will resize from 0 bytes to 1959841792 bytes
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition vendor will resize from 0 bytes to 680239104 bytes
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition odm will resize from 0 bytes to 4349952 bytes
Invalid sparse file format at header magic
Invalid sparse file format at header magic
And the phone is into the boot-loop, it will not starting the system.
Any help please...
Update:
System requirements:
- Fedora 32 with current kernel
- VirtualBox 6.1 with USB support
- Windows 7
- ODIN 3.14
Enable Root:
I) On mobile phone
1. carry out firmware update
1.1 Set up device, WITHOUT Google Accounts, WITHOUT security settings, set up WLAN only
1.2 Settings -> Phone info -> Software information -> Build number (press 7x )
1.3 Settings -> developer option -> enable OEM unlocking and USB debugging
2. copy the files from the root directory to the external SD card
2.1 Install MagiskManager
2.2 Starting MagiskManager
2.3 Installing Magisk Select
II) In the Fedora area
3. unpack the boot.img from the AP***.tar, on the PC
3.1 lz4 -d boot.img.lz4 boot.img
3.2 Copy the boot.img to the SD card from the phone
4. patching the boot.img in MagikMager
4.1 Select the boot.img, wait until "Done" appears.
4.2 Then copy the magisk_patch.img to the workstation (Fedora)
5.1 Rename the original boot.img to boot_original.img
5.2 renaming magisk_patch.img to boot.img
5.3 Transfer the new boot.img to the PC for the ODIN or HEIMDALL
5.4 Convert the boot.img to boot.tar: tar -H ustar -c boot.img > boot.tar (here for ODIN)
III) Virtual environment Win7
6.1 Copy the boot.tar from the Fedora workstation to the Odin directory of Win7
6.2 Open the boot.tar in the AP slot, Auto Reboot must be off
6.3 Press Vol + & Vol - simultaneously and plug in the USB cable (On SM-A515F), then click on "Start" in the ODIN.
IV) On the Mobile Phone
7.1 If ready, restart with Vol - & Hold PWR for more than 7 sec
7.2 Putting the device into recovery mode (switch off, press vol up and pwr simultaneously, Samsunglog appears, release pwr again)
7.3 Wipe your data: Wiped data/factury reset
Note: Device makes a boot loop for the first time - is normal. The first start takes quite long, be patient!
7.4 Settings -> Phone info -> Software information -> Build number (press 7x )
7.5 Settings -> Developer option -> Enable OEM unlock, USB debugging and system auto update to OFF
7.6 Installing and starting MagiskManger
The device will restart once!
Check it: Whether root is present
Fedora workstation:
Call Terminal, enter adb shell followed by su
If everything went well, the MagiskManager should answer the phone and ask for authorization.
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
tiptel170 said:
Update:
System requirements:
- Fedora 32 with current kernel
- VirtualBox 6.1 with USB support
- Windows 7
- ODIN 3.14
Enable Root:
I) On mobile phone
1. carry out firmware update
1.1 Set up device, WITHOUT Google Accounts, WITHOUT security settings, set up WLAN only
1.2 Settings -> Phone info -> Software information -> Build number (press 7x )
1.3 Settings -> developer option -> enable OEM unlocking and USB debugging
2. copy the files from the root directory to the external SD card
2.1 Install MagiskManager
2.2 Starting MagiskManager
2.3 Installing Magisk Select
II) In the Fedora area
3. unpack the boot.img from the AP***.tar, on the PC
3.1 lz4 -d boot.img.lz4 boot.img
3.2 Copy the boot.img to the SD card from the phone
4. patching the boot.img in MagikMager
4.1 Select the boot.img, wait until "Done" appears.
4.2 Then copy the magisk_patch.img to the workstation (Fedora)
5.1 Rename the original boot.img to boot_original.img
5.2 renaming magisk_patch.img to boot.img
5.3 Transfer the new boot.img to the PC for the ODIN or HEIMDALL
5.4 Convert the boot.img to boot.tar: tar -H ustar -c boot.img > boot.tar (here for ODIN)
III) Virtual environment Win7
6.1 Copy the boot.tar from the Fedora workstation to the Odin directory of Win7
6.2 Open the boot.tar in the AP slot, Auto Reboot must be off
6.3 Press Vol + & Vol - simultaneously and plug in the USB cable (On SM-A515F), then click on "Start" in the ODIN.
IV) On the Mobile Phone
7.1 If ready, restart with Vol - & Hold PWR for more than 7 sec
7.2 Putting the device into recovery mode (switch off, press vol up and pwr simultaneously, Samsunglog appears, release pwr again)
7.3 Wipe your data: Wiped data/factury reset
Note: Device makes a boot loop for the first time - is normal. The first start takes quite long, be patient!
7.4 Settings -> Phone info -> Software information -> Build number (press 7x )
7.5 Settings -> Developer option -> Enable OEM unlock, USB debugging and system auto update to OFF
7.6 Installing and starting MagiskManger
The device will restart once!
Check it: Whether root is present
Fedora workstation:
Call Terminal, enter adb shell followed by su
If everything went well, the MagiskManager should answer the phone and ask for authorization.
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
Click to expand...
Click to collapse
It is work ???
GreggBorowski said:
It is work ???
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
sankhauaa said:
I m not tried. But someone in this a51 group tried.Its working. But not so easy .
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
Don't pay.Its fake
Click to expand...
Click to collapse
sar please send me a51 group
Mehran` said:
sar please send me a51 group
Click to expand...
Click to collapse
Go to s10 page
sankhauaa said:
Go here for odin flash method without twrp
Click to expand...
Click to collapse
Not working. I has done step by step in this guide.
ibtsam3301 said:
so does this method work for lineage os on A515F too?
Click to expand...
Click to collapse
No. Withe manipulation from the vbmeta.img, the system is unwilling to start. It gos in to the bootloader, with error-codes. Like in first thread I describe. Olny the SAMSUNG original system works with the kernel modification for the MagiskManager.
I saw black for the future, there will be exist an custom rom for this device.
I have no idea, what can I do for this device. But I use and spend a lot of time for modification, without an good result. Has anyone an idea what can I do? But it look likes, it has an great secure system intern for not using an customer rom. This is my intention.