Develop Bugs

SIM Unlock / SIM Relock scripts for Samsung Galaxy Xcover S5690

Prerequisites:
- the phone should be connected to the computer via the USB cable provided in the commercial package;
- the Settings / Applications / Development / USB Debugging option should be enabled;
- the USB drivers for the S5690 phone should already be installed on the host computer.
Instructions:
0. download the S5690_unlock.zip file attached to this post;
1. unzip the S5690_unlock.zip archive in any place on your local hard drive;
2a. if you wish to UNLOCK the phone, execute the s5690_unlock.bat script as Administrator (right-click on the script file and select Run as Administrator);
2b. if you wish to RELOCK your phone, execute the s5690_relock.bat script as Administrator (right-click on the script file and select Run as Administrator);
3. follow the on-screen instructions and NEVER restart the phone by yourself.
WARNINGS:
- at the beginning the script waits for the sdcard to be mounted in your phone. If you have no sdcard at all, the script will wait forever! In this case you should disconnect the usb cable, turn off the phone, insert an already formatted microsd card, turn on the phone and finally reconnect the usb cable. The script will resume by itself when the card is detected;
- do not reboot the phone by yourself at any step! (neither in Recovery nor in standby); the script will do that automatically everytime it needs it;
- the ROOT.zip and UNROOT.zip files which are attached to the S5690_unlock.zip archive can be used ONLY on S5690/S5690L/S5690M phones. They won't work on other phone models;
- do not try to Relock a neverlocked phone, simply because the effects could be unpredictable (since there is no PLMN ID stored in the /dev/bml25 memory that would normally tell the phone on what network is it locked to);
- the scripts should also work on the S5690L and S5690M phone models. Please post some feedback here if you unlock/relock one of these models.
After the complete execution of the unlock/relock script, the tmp subdirectory will contain two files:
- bml25_before.bin -> backup of the original /dev/bml25 dump;
- bml25_unlocked.bin OR bml25_locked.bin -> dump of /dev/bml25 block device AFTER the unlock/relock operation.
What the script does:
1. installs root on the phone;
2. dumps the /dev/bml25 block device to a binary file;
3. changes the first two bytes of that file from 01 to 00 (for unlock) or viceversa (for relock);
4. writes back the binary file to the /dev/bml25 block device;
5. removes the root from the phone;
6. removes ROOT.zip and UNROOT.zip files from your sdcard.
If your phone is already rooted then skip the ROOT.zip installation step (from the Recovery menu) and just press any key in the script window to go to the next step.
After the execution of the script, the phone will be UNROOTED! If you want to keep the root, then you should either break the script (CTRL+C) when it reaches the INSTRUCTIONS FOR ROOT REMOVAL step or you should press any key in the script window without actually installing the UNROOT.zip from the Recovery menu.
There is no problem if you run the unlock script on an already unlocked phone or if you run the relock script on an already locked phone. In either of those cases, the phone will have the same status in the end as before running the script (either unlocked or locked). If you compare the bml25_before.bin and bml25_[un]locked.bin files you should have no differences.
I've already tested both unlock and relock scripts on several S5690 Xcovers and everything works OK.
UPDATES:
20130208 -> added support for the S5690R variant (Rogers Canada) - thanks to theshowman

Thanks a lot for the scripts! Excellent job. One question though: if my phone is already rooted (with your update.zip ) what should I (if possible) remove from the unlock script in order to perform strictly the steps for unlocking? Thank you in advance.

You don't have to remove anything. When the script displays the instructions for Root, just press any key in the script window (without actually following the instructions, i.e. without installing the ROOT.zip archive in the recovery menu) so the script goes directly to the next step (the unlocking step).
Also if you want to keep the Root in the end, do exactly the same at the Unrooting step.
The script does not verify if you really root / unroot the phone when it asks you to do so.
Regards

Thanks for your work.
Respect!

I tried the script but unfortunatelly it didn't work on my phone. In attach there is one print screen of the operation. My Xcover is locked on Orange RO. What could be the problem?

Copy the text from the cmd.exe screen and post it here or upload a full size print screen. The image resolution is too small and I can't understand what's the problem.
It seems that the "su -c" commands are executed directly under the cmd.exe and NOT within the adb shell prompt as they should be.
Post the WHOLE output of the script (from the beginning to the end). Do more consecutive print screens if necessary.

I tried again and you are absolutely right. The script is executed in cmd.exe, not in adb as it should. I didn't pay attention earlier. What can I do to force it to start in adb? The screenshot has been taken and saved at 1280x800 but it has been resized automatically at upload.

Upload the image(s) on imageshack and post only the links here. I need the whole output of the script.

http://imageshack.us/photo/my-images/846/unlocking.png/
First link. If neccessary, I will make/upload the missing screens from cmd.exe (the missing parts are the root and unroot ones, that I skiped by pressing a key without following instructions as my phone is rooted).

never mind

@PaulTT: I think I've found the problem. The double quotes were not interpreted correctly (probably due to different regional settings).
Please download again the zip archive from the first post (I've replaced it with a newer version) and try again.
Regards

Now it worked flawlessly! I have the 2 .bin files in temp file and the phone is working with any non Orange SIM. Thanks a lot for your help!

It is working, but i had to write every command in cmd, after i got su acces, thank you tlc76

Thanks !
it worked flawless ! many thanks

Worked like a charm. Thanx!.
Offtopic: no CFW so far for this phone? I'd like to try an 4.0.x ROM.

thanks for the post, do you think it will work with any career in american countries?

Problem
Hey tlc76,
first of all, i'd like to say thank you for the script, but unfortunately it doesn't work.
So i did everything in the description. (Turning on USB-Debugging, Inserting SD-Card, Installing the Drivers from Samsung)
But everytime i open the unlock.bat file, the screen turns white and the script doesn't do anything. The PC says, that adb doesn't work sometimes.
With the standard software from samsung or the adb in eclipse it functions quite well.
I would be thankful for some advice.
Thanks,
greendot_189

nice tool! my phone is more happy now

So, i eradicated the problem from yesterday, by running the script with a different version of adb, which was already on my harddisk.
There are good and bad news.
The good ones first:
It doesn't freeze and turn white anymore.
The bad ones:
The script waits endlessly searching for a SdCard. (It is inserted, and the phone works with it)
greez,
greendot
Edit:
It works now. Thank you very much!
Problem:
It didn't find the device. I installed Android SDK (with the USB Drivers) + JDK7 on another computer. Then everything worked fine.
Thanks!

If the script waits endlessly for the SdCard and the dots on the screen ARE NOT expanding, then you can try the following (in this particular order):
- stop the script (CTRL+C and Y) and restart it;
- unplug and replug the USB cable (with the script still running);
- reboot the host computer.
It seems that sometimes the
Code:
adb -d shell "mount"
command freezes and the script cannot advance. Normally every two seconds a new dot should be displayed:
Waiting for the SdCard to be mounted.................
so if you see only 4 dots which are NOT expanding
Waiting for the SdCard to be mounted....
then the script is waiting endlessly for the output of the mount command and is not actually running, so you can do one of the 3 actions described above.
The problem is most probably caused by the adb interface.

[HOWTO] Unlock, Root, and Install CWM on Galaxy Nexus using a Mac

[highlight]IMPORTANT! DATA LOSS![/highlight] For security purposes, this process will delete everything on your phone, including everything on the internal sd card! If you haven't backed up, do so now! Any pictures, videos, and documents not backed up will be unrecoverable...
First things first... This is mostly adapted from this guide by loveubuntu. Many Thanks!
[highlight]WARNING:[/highlight] Rooting your device probably violates your provider's acceptable use policy. It also voids your warranty. If you damage your device while following this guide, you are responsible!
That said, this process worked for me, without any problems.
[size=+2]Install the Java SDK[/size]
You may not need to do this if you're on a version before 10.7 (Lion)... I'm not sure.
You'll need an Apple Developer account, but they're free... Go to the Apple Developer Download page. The current version for Lion at the time of this writing is Java for OS X 2012-003.
Download and install.
[size=+2]Download and Setup Android SDK[/size]
Download the Android SDK. Make sure you get the one for Mac OSX.
Open the file to unzip it. For convenience, move the folder to your home directory. Open terminal and use the following command. You can leave terminal open... We'll be using it again, and again, and again...
Code:
mv Downloads/android-sdk-macosx ~
[size=+2]Get Connected[/size]
On your phone:
Open Settings | Developer Options
Turn on USB Debugging
Plug your phone into your mac.
In terminal, on your mac, run the following commands:
Code:
cd ~/android-sdk-macosx/platform-tools
adb devices
You should see your phone's serial number. If not, make sure everything is installed correctly and your phone is connected correctly.
[size=+2]Download Files[/size]
Download the latest Touch Recovery from ClockworkMod. Be sure to get the one for Google Galaxy Nexus (Verizon).
Download su.zip.
[size=+2]Unlock your Phone[/size]
Here's the part where you void your warranty and wipe your phone, so... here come the warnings again...
[highlight]IMPORTANT! DATA LOSS![/highlight] For security purposes, this process will delete everything on your phone, including everything on the internal sd card! If you haven't backed up, do so now! Any pictures, videos, and documents not backed up will be unrecoverable...
[highlight]WARNING:[/highlight] Rooting your device probably violates your provider's acceptable use policy. It also voids your warranty. If you damage your device while following this guide, you are responsible!
Turn off your phone (Are you sure you've backed up everything important on your phone???).
Hold Volume Up and Volume Down while pressing the power button to turn your phone on. Let go of the power button when the phone vibrates, but keep holding the volume buttons until you see stuff on the screen.
You should now see a big arrow and some text on your screen. The bottom line is the lock state. Congratulations, you're in the bootloader.
[highlight]Are you sure you backed everything up? Last chance...[/highlight]
If you're not plugged into your mac still, hook it up and run the following command in your terminal.
Code:
fastboot devices
You should see your phone's serial number, just like you did with adb (which doesn't work in the bootloader, of course).
[highlight]Okay, this is really your last chance. Backup any data you don't want to lose. The next command will erase everything.[/highlight]
Run the following command in terminal:
Code:
fastboot oem unlock
Use the volume up button on your phone to select YES and press the power button to accept.
Including the following, since I probably did it... Not sure if it is entirely necessary:
Use the volume up to change the value appearing in the arrow to recovery and press the power button to accept. You are taken to laying down android with a red triangle. This is the stock recovery. Now carefully press the volume up, volume down, and the power button to get to a menu. Choose wipe data and factory reset. 2 things: I had a hard time getting to the menu. Do it a few times and try pressing the power button JUST a fraction of a second earlier than the 2 volume buttons. Also wiping and resetting takes a few minutes, be patient.
[size=+2]Flash CWM Recovery[/size]
Well, if you made it this far, you've already voided your warranty and wiped your phone... why stop now?
Turn the phone off (pull battery if necessary). Boot back into the bootloader by holding the volume buttons and power again (see previous step, if you forgot how). Connect to your mac, if you're not still connected and run the following in terminal:
Code:
fastboot devices
See your device? Great! Now let's flash ClockworkMod Recovery. If you haven't moved it, it'll be in your downloads directory. You can run the following from terminal (the version may have changed, so double check):
Code:
fastboot flash recovery ~/Downloads/recovery-clockwork-touch-5.8.0.2-toro.img
[size=+2]Get Root[/size]
You're still in the bootloader, right? If not, get there and use the volume keys to select recovery. Press power to open it. Yay! CWM Touch! FTW
Okay, reboot and allow Android to create the folder structure it needs. When you get to the welcome screen, pull the battery to shutdown and boot back into the bootloader (you should be a pro at this by now). Use the volume keys to select recovery and power to get there.
If you're not connected to your mac, do so and run the following:
Code:
adb push ~/Downloads/su.zip /data/media
Yep, adb works in recovery... This just transfers the file to the root of your internal sd card.
Now run:
Code:
adb reboot recovery
Now use the menus to install su.zip. Choose zip from sd card, su.zip, etc... oh yea, and it's touchscreen.
Congratulations! You now have full administrator permissions on your phone.
[size=+2]Install Helpful Tools from Play Store[/size]
Boot your phone normally and go through the whole activation and getting started process.
Then install some tools that will help, now that you have a rooted phone. Just open the play store and search for rom manager. This is made by ClockworkMod and it works great with their recovery. Next you'll want to search for titanium backup. This will allow you to backup application data to help make loading new roms a little less of a hassle. There are free and paid versions of both of these apps. The paid versions give you more functionality, as well as, no ads.
Last, install solid explorer beta (or some other file manager). We need it for the last step.
Also, while you're in the play store, go ahead and update superuser if there is an update available.
[size=+2]Delete recovery.sh[/size]
Your phone may have a file called recovery.sh, which will flash the default recovery on reboot if you don't get rid of it.
Open Solid Explorer Beta.
Tap the Jump button at the bottom of the screen. Then Device and System Root.
Open the system folder, then open etc.
Scroll down and look for recovery.sh. If it doesn't exist, no worries... If it does, tap and hold on it, then either rename or delete it, whichever your more comfortable with.
That's it! Your unlocked and rooted. You can enjoy many benefits from just this process.
However, if you want a real benefit. Find a nice ROM and flash it using ROM Manager or by rebooting into the recovery if you need to install 2 zips, like most require. I'd like to recommend TeamBAMF.

Nice guide! I just did this myself like 2 days ago (with my replacement phone). It was really fun, I already had SDK set up n stuff though.

yes very nice guide, i hate switching between my pc & mac for just my phone.
i wonder if there is a way to do this w/o Java.

I'm pretty sure the platform tools are coded in Java, but we're not compiling anything... You may just need the jre. I already had the ask installed...
Wouldn't hurt to try.
Sent from my Galaxy Nexus using Tapatalk 2

anton2009 said:
Nice guide! I just did this myself like 2 days ago (with my replacement phone). It was really fun, I already had SDK set up n stuff though.
Click to expand...
Click to collapse
I already had the JDK setup too, so I'm not positive that step is necessary...
Sent from my Galaxy Nexus using Tapatalk 2

[TUTORIAL]How to setup SP_Flash_Tool_Linux (MTK/MediaTek Soc)

This works only on Linux 64-bit
DISCLAIMER: It is always risky to flash your mobile device. I do not and will not take any responsibility for bootloops and bricks.
Please check carefully that the ROM or recovery.img you want to flash is suitable for your specific device and for the sp_flash_tool. The firmware directory should neither contain meta-inf nor system folder, but something_with_a_scatter.txt and a system.img
Backup your phone before flashing!
Your phone's battery should be at least half charged (50 percent) before you start this.
I successfully ran these steps on my UMI Hammer with Linux Ubuntu 14.04 and 16.04. I do not have other devices or Linux derivates and do not plan to buy/install any.
CREDITS and a zillion thanks to Sergio Rivero for his excellent tutorial on mibqyyo.com!!!!
Also many thanks to N2K1 for giving me some more background information!
So here we go:
Step 1:
If you haven't done so before, install the Linux generic usb-drivers package:
Code:
sudo apt-get update
sudo apt install libusb-dev
Download SP Flash Tool Linux (latest version): http://mtk2000.ucoz.ru/load/soft/soft_mtk/sp_flash_tool/5-1-0-14 (Password to extract currently is mtk2000v3)
or here https://androidmtk.com/smart-phone-flash-tool
In case you haven't done before, install unrar:
Code:
sudo apt install unrar
Extract the downloaded file -> graphic file manager (e.g. Nautilus): double-click and extract. Terminal:
Code:
unrar x path_to_file
(from now on: please adapt paths to your own settings)
Move the new folder „sp_flash_tool“ to a directory of your choice.
Code:
mv /home/username/Downloads/sp_flash_tool /home/username/...
You might also need to install libqtwebkit4 (it just happened to me on Linux Ubuntu 16.04):
Code:
sudo apt install libqtwebkit4
[Only For Ubuntu 16.10 and newer]
Run
Code:
dpkg -x libpng12-0_1.2.54-1ubuntu1.1_amd64.deb /tmp/libpng2
cp /tmp/libpng2/lib/x86_64-linux-gnu/libpng12.so.0.54.0 lib
cd lib
ln -s libpng12.so.0.54.0 libpng12.so.0
These libraries are still required for the flash tool but have been removed from new Ubuntu versions.
Thanks @hanalinqu, @z3r0c00l_2k https://forum.xda-developers.com/showpost.php?p=73484473&postcount=216 and @opticyclic https://forum.xda-developers.com/showpost.php?p=81543495&postcount=285 for this information!
Step 2:
Change into the newly created directory:
Code:
cd /sp_flash_tool
We make one file executable by typing:
Code:
chmod +x flash_tool
In order to avoid running the flash_tool as root user, you need to add a standard user to the usergroup "dialout" (thanks to @egalus for this bit!)
Code:
sudo adduser username dialout
For Arch Linux:
Code:
gpasswd -a username uucp
and activate the membership immediately
Code:
newgrp - dialout
(Arch Linux):
Code:
newgrp - uucp
Step 3:
Now you can open the tool:
Code:
./flash_tool
or double-click on the flash_tool icon.
You can try at this stage if the flash tool connects to your phone:
In the user interface, choose tab „Download“. Hit "scatter-loading", navigate to a directory with a valid firmware for your device and choose the scatter-file.
For testing purposes uncheck "name" and check one of the smaller files in the list below (for example "logo")
Switch off your device. Hit the "Download" button in SP_Flash_Tool and connect your phone to the computer. Some devices require you to take off the battery for about 10 seconds, with others you need to press Vol+ or Vol- while plugging the cable into the phone. Please look up device-specific threads and try out different options.
If nothing happens at all, open a second terminal, run
Code:
dmesg | grep usb
and look out for a MediaTek entry. If there is none → did you install libusb-dev (Step 1?)
If the answer is yes, you might need to create a persistent udev rule for the MTK Preloader:
Code:
sudo gedit /etc/udev/rules.d/80-persistent-usb.rules
Add the following line to the file:
Code:
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0e8d", ATTR{idProduct}=="*"
Save the file and exit.
Reload the usb-rules:
Code:
sudo service udev restart
Disconnect the usb data cable from the computer and the smartphone. Close the flash tool. Switch on your phone (fastboot mode will do). Repeat the first paragraph of Step 3.
If the tool connects, within a few seconds a red progress bar will appear. Unfortunately, in my case an error message came along with it:
S_BROM_CMD_JUMP_DA_FAIL (2035)
There is a connection, but also one more obstacle to overcome...
Step 4:
Now we come to the interesting part, which cost me 2 weeks of (futile) research and frustration. Finally I found Sergio Riveros tutorial on mibqyyo. Thanks to him again and again and again for this priceless piece of information
The “modemmanager” package integrated by default within Linux Ubuntu 14.04 and later is not compatible with the MTK Flash Tool for Linux
Click to expand...
Click to collapse
To put it in different words: The modem manager controls port /dev/ttyACM0 and disables the Flash Tool. So we blacklist it for the two MTK vendor IDs the flash tool uses:
Code:
sudo gedit /etc/udev/rules.d/20-mm-blacklist-mtk.rules
You insert these two lines:
Code:
ATTRS{idVendor}=="0e8d", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="6000", ENV{ID_MM_DEVICE_IGNORE}="1"
Save the file, exit and restart udev:
Code:
sudo service udev restart
Switch your phone on (fastboot mode will suffice) and off again.
Step 5:
Code:
./flash_tool
or double-click on the flash_tool icon.
Now everything should run smoothly. In case you encounter
Code:
BROM ERROR : S_SECURITY_SF_CODE_FORMAT_FORBIDDEN (6012) , MSP ERROE CODE : 0x00
change the download agent to MTK_AllInOne_DA.bin (screenshot #4)
There are plenty of tutorials on the web for the further steps.
Happy flashing! When a green circle with a white checkmark appears, you are done. You can close the flash tool and disconnect your phone. For a clean start with a new ROM boot into recovery and wipe data/factory reset.

Kudos for the udev rules, I finally managed to root my phone and disable some vendor crap thanks to you!

Thanks, I'm glad to read that it worked for you as well

Great post!
Just wanted to say you saved me HOURS OR DAYS OR WEEKS of time on the modemmanager thing. I have Arch Linux, successfully ported over this tutorial, but I had no idea the modemmanager package was causing the issue. SP Flash Tool was the last frontier for using my Android devices on Linux. Thanks so much!

You are very welcome! Since it took me two weeks to find the cause for "S_BROM_Error [2035]" I wanted to spare other "victims" the experience

This is a very nice, HQ post. Keep up the good work.
But I would like to suggest two corrections:
1) The mv command is unnecessary. you don't have to copy the folder to the root directory to run it as root.
2) Please also add a final step to delete the udev rules so as to re-enable the modem manager after rooting.
Though most of the people who would be reading your thread would be knowledgeable linux users, they won't need these suggestions, but anyways, it would make your guide complete.

Thanks for your feedback @daltonfury42
1) Of course you don't need to move to move the folder to / .As I wrote, you can also use your /home/user directory. But you shouldn't keep it in "/Downloads" or "/tmp", since you might have deleted the folder by the next time you want to use the flash-tool.
Step 2), as you suggest it, is redundant on a private computer, because you blacklist the modemmanager for the flash-tool only, and for nothing else. SP_Flash_Tool uses different Vendor and Product IDs than MTP/USB/ADB/Fastboot mode, and these IDs are not related to your specific device. So the modem manager is up and running - even while you flash - on every other active (network-relevant) usb-port of your computer And it will be up and running on the usb-port you use for the flash-tool when you disconnect the phone and then plug in something else - or the same phone in a different mode... But due to the permanent
Code:
/etc/udev/rules.d/20-mm-blacklist-mtk.rules
entry the modem manager will be automatically blocked if you connect your phone to the SP_Flash_Tool a second time - no matter which port: no further preparations necessary
If you want to check it out, take a look the output of
Code:
dmesg | grep usb
connecting your phone "normally" and compare it with the same command -> output connecting your phone to the SP_Flash_Tool - and/or to the contents of the file "usb_setting.xml" in the SP_Flash_Tool directory My udev rule simply tells the modem manager to ignore two vendor IDs named in that file.
edit: if you "flash" your linux computer more often than your Android device, you should remember to backup the folder and the udev rules

Miss Montage said:
Thanks for your feedback @daltonfury42
1) Of course you don't need to move to move the folder to / .As I wrote, you can also use your /home/user directory. But you shouldn't keep it in "/Downloads" or "/tmp", since you might have deleted the folder by the next time you want to use the flash-tool.
Step 2), as you suggest it, is redundant on a private computer, because you blacklist the modemmanager for the flash-tool only, and for nothing else. SP_Flash_Tool uses different Vendor and Product IDs than MTP/USB/ADB/Fastboot mode, and these IDs are not related to your specific device. So the modem manager is up and running - even while you flash - on every other active (network-relevant) usb-port of your computer And it will be up and running on the usb-port you use for the flash-tool when you disconnect the phone and then plug in something else - or the same phone in a different mode... But due to the permanent
Code:
/etc/udev/rules.d/20-mm-blacklist-mtk.rules
entry the modem manager will be automatically blocked if you connect your phone to the SP_Flash_Tool a second time - no matter which port: no further preparations necessary
If you want to check it out, take a look the output of
Code:
dmesg | grep usb
connecting your phone "normally" and compare it with the same command -> output connecting your phone to the SP_Flash_Tool - and/or to the contents of the file "usb_setting.xml" in the SP_Flash_Tool directory My udev rule simply tells the modem manager to ignore two vendor IDs named in that file.
edit: if you "flash" your linux computer more often than your Android device, you should remember to backup the folder and the udev rules
Click to expand...
Click to collapse
@Miss Montage, very informative. Thankyou.

You're welcome - but please do not post full quotes

Hi. Thanks for the tutorial :good:
I'm getting "PMT changed" error with the right scatter when tried to flash bootimg/recovery only.

Where did you get the scatter file? Generally this error code means that the partition table is different to the one on your device. This should only be the case - occasionally - if you flash a complete firmware.
(Or replace Android through Ubuntu / vc. vs.)

Miss Montage said:
Where did you get the scatter file? Generally this error code means that the partition table is different to the one on your device. This should only be the case - here and then - if you flash a complete firmware.
(Or replace Android through Ubuntu / vc. vs.)
Click to expand...
Click to collapse
I know this error, so I am surprised
scatter is from my stock rom. Same i used to flash.

Hmm, dunno why that is. Can you compare the scatter.txt to the /proc/emmc file on your phone?
And at what stage do you get the error? Immediately after connecting or later?

Miss Montage said:
Hmm, dunno why that is. Can you compare the scatter.txt to the /proc/emmc file on your phone?
And at what stage do you get the error? Immediately after connecting or later?
Click to expand...
Click to collapse
Right now I remembered in windows long ago got the same problem.
This happens if I try to use flash sp tool new versions
In windows:
Working: v5.1352.01
Not Working: v5.1512.00.000
Click to expand...
Click to collapse

The sp_flash_tool_linux 5.1520..... worked perfect for me though... Have you tried an earlier version?

Miss Montage said:
The sp_flash_tool_linux 5.1520..... worked perfect for me though... Have you tried an earlier version?
Click to expand...
Click to collapse
SP_Flash_Tool_Linux_v5.1452.00.100 tested, same problem.
SP_Flash_Tool_Linux_v5.1436.00.100 also tested and same.
No older versions found

The version v5.1504.00.100 works on my 64-bit-system, too... But the error seems to be caused by something else. Have you checked the SP logfile?

Have you also tried the newest version? I just involuntarily re-flashed my UMI Hammer with it... Wanted to choose the twrp only, but too much multi-tasking leads to no good

Miss Montage said:
The 32bit-version v5.1504.00.100 works on my 64-bit-system, too... But the error seems to be caused by something else. Have you checked the SP logfile?
Click to expand...
Click to collapse
Tested and same.
Here logs

Hmm, I will compare these lines to a successful log:
08/13/15 23:57:01.942 BROM_DLL[6767][6774]: FlashTool_ReadPartitionInfo(0x7f7b840038a0,0x7f7b84013310,0x7f7b00000013): mutex: LOCK ... (mutex.cpp:151)
08/13/15 23:57:01.942 BROM_DLL[6767][6774]: FlashTool_ReadPartitionInfo(0x7f7b840038a0,0x7f7b84013310,0x7f7b00000013): mutex: UNLOCK. (mutex.cpp:166)
08/13/15 23:57:01.943 BROM_DLL[6767][6774]: FlashTool_Disconnect(0x840038A0): mutex: LOCK ... (mutex.cpp:151)
Click to expand...
Click to collapse

[ROOT]G955U/G955U1 SnapDragon SamPWND Root IS HERE!

FINALLY!
We Present To You
SamPWND!
Root for the USA Variants of the S8 & S8 Plus Devices!
(This thread will focus only on the S8+)
This thread had been closed/locked until further notice. The thread and links should remain active and the thread has served it's purpose. You will need to search the thread if you have any questions pertaining to root or any errors/issues that you are facing. The other reason I have decided to close the thread is because it has gone off topic one too many times, people like to argue and debate and MODS have had to come in here 1 too many times to clean it up so as to make life easier, I will just shut it down. Please do not bombard me with PM's for root assistance because if it has been answered in this thread already (and it most likely has) I will just direct you to search in the thread if I am able to respond at all.
ALSO, please do not utilize our firmware/root files/method without gaining permission first or I will ask for the thread to be removed/locked. Just because the thread gets closed does not mean we didn't spend a lot of time to get to this point.
Thank you and enjoy SamPWND root!​
DISCLAIMER:
We are not responsible for any damage done to your device as no one is "forcing" you to root your phone! If you are not sure of how to follow instructions or use ADB then I would suggest waiting for someone to help you or that you read up on how these things work before diving head first. The ENG system is not very stable when it comes to root as well as it has a ton of tools and binaries not available on stock devices so we are not responsible if you break something while on any firmwares but especially while on the ENG firmware.
DISCLAIMER 2:
Please do not take our work and post it elsewhere. We spent a lot of time on this for people to take it and use it as if it is their own. With that being said, if you have a better process for something or find any issues/errors, please PM myself or one of the listed contributors of this root method, do NOT post it directly in the thread because it causes confusion. We know with 100% certainty the files and method presented WORK. If it is not working for someone there are a number of possible reasons why. If users start modifying our files/scripts and posting them and you decide you are going to use someone else's files/scripts, do not post in our threads asking for us to help you because we will have no idea what was modified or changed and will just tell you to use the original files.
Returning to Stock:
- It is possible to return to 100% stock and it is very EASY to do.
- This is the reason why I provide both Normal, and Comsey ODIN's.
- All you need is a full stock 4 files firmware of your choice.
- Extract those files. Open ODIN and select the 4 files in their respective slots.
* IF YOU GET ERRORS such as model mismatch, start with 1 partition at a time to find out which one is throwing the error. (In my experience, it is the BL file that causes the error.) Once you find the culprit, throw that partition into the other ODIN. (For example, the BL file is giving an error in Comsey ODIN, throw the BL file in NORMAL ODIN and flash it by itself.)
* Typically you might have to throw individual partitions into either of the ODIN's but in the end you will be back on full stock firmware.
What doesn't work while rooted?
- On ANY ROOTED device, anything that utilizes "SafetyNet" will NOT work.
- Magisk and/or SuHide will NOT work. Our bootloader is still locked and these two modify the boot.img which would cause our devices to not boot up and having to start the root process over again, you have been warned!
- Systemless root also does NOT work. Again, this patched the boot.img which we cannot do because of our locked bootloader.
- Battery currently only charges to 80%. There are a few that feel it legit doesn't charge fully but others are claiming they get the same amount of life as they did with a 100% battery so the 80% might just be a visual issue or "fake" when it is really at 100%. Either way, we are still looking into this.
Main Contributors:
@elliwigy
@Harry44
@akiraO1
@BotsOne
@GSMCHEN
@jrkruse (for uploading system.img.ext4 and his root zip for the part 2 instructions)
@V0idst4r (for help in creating a "1 click" method for part 1!)
Initial Description on the process:
We are essentially flashing a modified 4 file firmware package in ODIN and then utilizing a few binaries in conjunction with SU binary and a permissive kernel. We will then be running some ADB commands and in order to have a fully working, amazing root with all things working we will be utilizing a stock system.img & a root script in conjunction with Flashfire. If you want to know all the technical details, you can take apart the files if you would like. It is released, so it is no longer a secret!
PART 1 Instructions: NEW
Flashing SamPWND 4 Files Firmware:
1) Download the PART 1 FILES Listed Below (this includes SamPWND_Root.zip and Initial ODIN 4 Files FIRMWARE and ODIN's if you do not already have them.)
2) Extract the 4 Files ODIN Firmware Package (also extract the ODIN's if you do not have them already.)
3) Open Comsey ODIN and select each partition and then select the files from the 4 File Firmware Package you extracted (BL goes in BL slot, AP in AP, CP in CP & CSC in CSC.) The options you select in ODIN shouldn't matter but I typically select F. Reset Time, Auto Reboot, Re-Partition, Nand Erase All & Update Bootloader.
4) Press Start and Wait for it to Finish. Once it finishes, if it boots into stock recovery simply select "Reboot System"
Take a breather, the ODIN portion is done (unless you have to start over for some reason...)
Now the NEW Root Process:
1) Once the phone is booted up, make sure you have ADB Enabled and connected to your PC. It should have prompted you to accept USB debugging as soon as it booted up.
2) Unzip the SamPWND_Root.zip
3) Double click "step1"
4) Wait for it to finish and once it reboots and comes back on you will be rooted with SuperSU!
5) Continue to PART 2 for "EVEN BETTER ROOT"
* It is a Windows bat file so not sure if it works on MAC. If you can't run bat files, use the OLD instructions.
* The bat will take about 30 seconds to run it's course. This is due to giving enough time for the remount script to mount the system as RW.
PART 1 Instructions: OLD
1) Download the PART 1 FILES Listed Below (this includes Systemroot + ADB zip, Initial ODIN 4 Files FIRMWARE and ODIN's if you do not already have them)
2) Extract the 4 Files ODIN Firmware Package, Also extract the ODIN's if you don't have them already.
3) Open Comsey ODIN and select each partition and then select the files from the 4 File Firmware Package you extracted (BL goes in BL slot, AP in AP, CP in CP & CSC in CSC.) The options you select in ODIN shouldn't matter but I typically select F. Reset Time, Auto Reboot, Re-Partition, Nand Erase All & Update Bootloader.
4) Press Start and Wait for it to Finish. Once it finishes, if it boots into stock recovery simply select "Reboot System"
Take a breather, the ODIN portion is done (unless you have to start over for some reason...)
Now the ADB Process to actually Root:
1) Extract the Systemroot + ADB zip listed below in an easy to find directory.
2) Make sure phone is connected to PC and ensure USB Debugging is enabled.
3) In the folder you extracted, you should see a "cmd-here" file. Double click it and it should open up an ADB cmd window.
4) Now we will start with the ADB commands:
- Type
Code:
adb push systemroot /data/local/tmp
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb push systemroot /data/local/tmp
/data/local/tmp/systemroot/: 8 files pushed. 0 files skipped. 10.0 MB/s (7072263 bytes in 0.673s)
- Type
Code:
adb shell chmod -R 7777 /data/local/tmp
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb shell chmod -R 7777 /data/local/tmp
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>
- Type
Code:
adb shell setsid su
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb shell setsid su
(It will be blank with the blinking cursor, move to next step)
- Type
Code:
id
(you should at this point see that your are in a root shell!)
What it will look like:
id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:shell:s0
- Type
Code:
echo /data/local/tmp/systemroot/remount2.sh > /sys/kernel/uevent_helper
What it will look like:
echo /data/local/tmp/systemroot/remount2.sh > /sys/kernel/uevent_helper
(Again, it will be blank with a blinking cursor after you type the command in, move to next step)
- WAIT ABOUT 30 SECONDS BEFORE MOVING TO THE NEXT COMMAND
- Type "
Code:
mount
" (you should now see rw next to rootfs and system partitions)
What it will look like:
mount
(After we type in mount, we are looking for the below two items to say rw like they do in the next two lines)
rootfs on / type rootfs (rw,seclabel,size=1586716k,nr_inodes=396679)
/dev/block/sda19 on /system type ext4 (rw,seclabel,relatime)
- Type
Code:
sh /data/local/tmp/systemroot/root.sh
What it will look like:
sh /data/local/tmp/systemroot/root.sh
rm: /system/bin/install-recovery.sh: No such file or directory
cp: /system/bin/.ext/.su: No such file or directory
chmod: /system/bin/.ext/.su: No such file or directory
chcon: /system/bin/.ext/.su: No such file or directory
touch: '/data/.supersu': Permission denied
/data/local/tmp/systemroot/root.sh[55]: can't create /data/.supersu: Permission denied
chmod: /data/.supersu: No such file or directory
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot\NEWSAMPWNDFILES>
5) If you followed all of the above commands to the T, your device will reboot and you will have SuperSU installed.
6) Install Flashfire from the Play Store.
7) Up to this point, you are on an ENG system.img with root that doesn't function the way we would like it to. This means you will feel a vibrate every time you try to gain SU access as well as it will take quite a while for an SU prompt. You can stay on this root if you would like to experiment with the ENG system, but outside of that I would HIGHLY recommend you proceed to the STEP 2 PROCESS.
PART 2 Instructions:
1) Download the PART 2 FILES listed below (this includes the system.img.ext4 and the add CSC Systemroot zip both provided courtesy of @jrkruse , view post #195 for specifics on what these are but essentially they are stock QD2 system.img and the zip has multi CSC, root, and a bunch of other goodies!)
2) Extract the System.img.ext4 zip and place that actual "system.img.ext4" onto the Internal SD Card (might work from external but some users have reported issues with chainfires root.zip and FF with external sd cards, this is not a fault of the SamPWND files/process.)
3) Place the entire Add CSC Systemroot zip onto Internal or Externdal SD Card (THIS FILE DOES NOT NEED TO BE UNZIPPED, THROW THE WHOLE ZIP FILE ONTO SD CARD OR INTERNAL)
4) Open Flashfire and grant it root when it prompts you. IF FLASHFIRE IS NOT LOADING FILES AND YOU JUST SEE A CIRCLE OR LIKE ITS CONSTANTLY LOADING, PUT THE PHONE IN AIRPLANE MODE AND THEN GO BACK INTO FLASHFIRE AND THE FILES SHOULD NOW APPEAR.
5) Press the + sign and select "Flash Firmware Package" & navigate to where you placed the system.img.ext4 and select it
6) Press the + sign and select "Flash ZIP or OTA" & navigate to where you placed the Add CSC Systemroot zip and select it, select Mount System as r/w
7) Press the + sign and select "Wipe" and select System data, 3rd party apps, Dalvik cache, Cache partiton, Cache Partiton format
8) Now, long press on "Wipe" and make sure it is on the top by dragging it. The order should be Wipe, Flash Firmware Package & finally Flash ZIP or OTA
9) Make sure the "Everoot" is disabled!
10) Flash away!
If you followed all of PART 1, then followed all of PART 2, then you will be updated to QD2, rooted with busybox (and have some other goodies) and the phone will be running great! Root will be stable and snappy as ever. Adaway, Root Checker, V4A etc. etc. are now all possible.
XDA:DevDB Information
S8 Plus SamPWND ROOT, ROM for the Samsung Galaxy S8+
Contributors
elliwigy
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 7.0, Any Current Firmware
Based On: Stock Touchwiz
Version Information
Status: Beta
Current Stable Version: 1
Stable Release Date: 2017-08-19
Current Beta Version: 1
Beta Release Date: 2017-08-19
Created 2017-08-19
Last Updated 2017-08-19

DOWNLOADS SECTION:
PART 1 FILES:
SamPWND_Root.zip
https://mega.nz/#!8YcgTSwI!hIfbdJZ466sr1AyfiHLdtr1p-To0QdthTPDmVwtv0dc
Initial ODIN 4 Files FIRMWARE
https://mega.nz/#!5cUjnCwK!Zgw5_CaINbES08gwDzl7yMN0N4nzm56Fa12ow-gppKA
Mirror: https://www.androidfilehost.com/?fid=961840155545589828
AFH MD5: 73720c409782b751355b9443a003a6e8
Normal + Comsey ODIN
https://mega.nz/#!cFN2DD4C!I7AT4TgNSzBp7Py0UhC7pHZ0M4WDQhEC5qj2xD_qluM
Systemroot + ADB zip - OLD
https://mega.nz/#!1MVDhZxQ!Wd4Umvju1sS1DAe-jBcTue9NKSJ4co0I2gwiyC3c2pE
PART 2 FILES: (Potentially will be providing a rom.zip soon that will have latest updated U1 with multi CSC pre-rooted with other goodies)
system.img.ext4
https://www.androidfilehost.com/?fid=817550096634794132
Add CSC Systemroot
https://www.androidfilehost.com/?fid=745425885120757028
For more info on these files please see @jrkruse post located here:
https://forum.xda-developers.com/showpost.php?p=73489978&postcount=925
THANK HIM WHILE YOU'RE AT IT!

@elliwigy @Harry44 @akiraO1 @BotsOne
These months these four people are very hard, and I very relaxed!! lol

Cool Job!

GSM CHEN said:
@[email protected]@[email protected]
These months these four people are very hard, and I very relaxed!! lol
Click to expand...
Click to collapse
haha but we know it wouldnt be possible without you man

Dam it, if I wasnt drunk, and tired, I eould vet myself out of bed and do this now, lol. Thanks for all your hard work.
One thing i would suggest would be to either put the commands that need to be typed in as bold face type or im not sure if its possible on here, as im on my phone atm, but there are Code/code tags avaiable that will make them easier to copy and paste.
Again, thanks for this......I did not think it was going to be possible. This will be my morning present when i wake up, feels like Xmas.......

theboz1419 said:
Dam it, if I wasnt drunk, and tired, I eould vet myself out of bed and do this now, lol. Thanks for all your hard work.
One thing i would suggest would be to either put the commands that need to be typed in as bold face type or im not sure if its possible on here, as im on my phone atm, but there are Code/code tags avaiable that will make them easier to copy and paste.
Again, thanks for this......I did not think it was going to be possible. This will be my morning present when i wake up, feels like Xmas.......
Click to expand...
Click to collapse
to be honest its late haha, threw it together lol ill try to tidy it up when i get time lol

Awesome can't wait to try this out soon!

elliwigy said:
to be honest its late haha, threw it together lol ill try to tidy it up when i get time lol
Click to expand...
Click to collapse
You are forgiven, lol. I figured it would be out in the morning, just not this early in the morning.
You guys should have gotten some sleep you may need it after this weekend.

What a nice thing to wake up to when I'm getting ready to head to work at 530 in the morning lol. Can't wait to give this a shot once I get off work 12 hours later. Thanks for everything devs.

S8 thread will be posted tomorrow, too late to do it tonight

You guys are the ****. Thanks for all of your hard work.

Just want to know if Knox will be triggered or not? Please also add this to the first post [emoji397]

Where's the best place to get the stock firmware we might need just in case? As far as best download speed etc.

Wow,. I honestly didn't think it was possible. Amazing accomplishment ellwigy.
Sent from my SM-G955W using XDA-Developers Legacy app

powerstroke said:
Where's the best place to get the stock firmware we might need just in case? As far as best download speed etc.
Click to expand...
Click to collapse
I got mine here... Took awhile to download... Someone gave me the link in the 955U1 thread
http://updato.com/firmware-archive-select-model?record=F6B451FD73EE11E7963AFA163EE8F90B
Also do we need to back up our EFS/Imei stuff? I know its recommended when flashing roms in recovery but our bootloader is locked.... Is there a way to back up without root?
Edit* I asked about the backup before in a previous thread but didn't get an answer.... Sorry to ask again

Techvir said:
Just want to know if Knox will be triggered or not? Please also add this to the first post [emoji397]
Click to expand...
Click to collapse
Knox is not triggered

Kjc99 said:
I got mine here... Took awhile to download... Someone gave me the link in the 955U1 thread
http://updato.com/firmware-archive-select-model?record=F6B451FD73EE11E7963AFA163EE8F90B
Click to expand...
Click to collapse
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol

powerstroke said:
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol
Click to expand...
Click to collapse
If you have the system.img for the latest update then correct, if not and you want those features with root you will have to download the AP and CSC from thw firmware you want

powerstroke said:
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol
Click to expand...
Click to collapse
I have the U1 model so I'm not sure...
Edit* Deleted

Samsung Galaxy Tab 3 7.0 SM-T210 problem

I recently found my old tablet and it had kingoroot installed and then I flashed stock rom to my tablet but now it randomly restarts and every time i try to setup it i got error "Unfortunately, the process com.android.systemui has stopped" and "settings has stopped"
Here is the tutorial I followed:
Code:
The following instructions are for Windows only. Please don't use a virtual machine as these can cause problems communicating with the device. There is an alternative method for Linux or macOS. Just tell me if you aren't on Windows, I can easily change the instructions. Please make sure you have Windows set to display all file extensions. This can really help for debugging purposes.
First we need to download the tool that downloads the stock firmware. It's called SamFirm and it downloads it using Samsung's servers. You can download the latest version [here](http://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462). Please also make sure you have the [Microsoft Visual C++ 2008](https://download.microsoft.com/download/1/1/1/1116b75a-9ec3-481a-a3c8-1777b5381140/vcredist_x86.exe) and [Microsoft Visual C++ 2010](https://download.microsoft.com/download/5/B/C/5BC5DBB3-652D-4DCE-B14A-475AB85EEF6E/vcredist_x86.exe) x86 Redistributable packages installed. Now to download the tool that flashes to the devices different partitions. On most devices you use a tool called fastboot, but Samsung devices aren't like most devices (excluding the Galaxy Nexus). This tool is called Odin, it's Windows only and leaked from Samsung so you need to get it from a trusted source. You can download the latest version [here](https://build.nethunter.com/samsung-tools/Odin_3.12.3.zip). Extract the "Odin_3.12.3.zip" file. You should now have a folder called "Odin_3.12.3". Treat this as your working directory and download all other files to this folder. While you're here, extract the contents of "SamFirm_v0.3.6.zip" into this folder.
Now to download the stock firmware. Open "SamFirm.exe" and make sure "Auto" is checked and "Manual" and "Binary Nature" isn't checked. In "Model" put `SM-T210` and in "Region" put `BTU`. Click "Check Update" and wait for it to find the firmware on the server. Now check "Check CRC32" and "Decrypt automatically". Then click "Download" and save it. Let it finish downloading, checking, and decrypting. Once it finishes you can now close SamFirm. Extract the zip file it gave you. You should now have a single file ending in `.tar.md5` (you may also have `.dll` file, ignore it). This tar.md5 file is your firmware. Do not modify it. If you have more than one .tar.md5 file, tell me.
Now shutdown the device and then hold the Volume Down, Home/Bixby, and Power buttons. This should put the device into download mode. Accept any warnings then plug the device in. Open "Odin.exe" from the "Odin_3.12.3" folder. In the log, it should say `Added!` and have a blue COM thing near the top, meaning it detected your device. If it didn't detect it, then you may need to configure drivers (you can ask me for the drivers if you need them). Click the "Option" tab and make sure "F. Reset Time" and "Auto Reboot" is enabled. Also check the checkbox next to the "AP" button and then click the button. Select the tar.md5 file. Now click "Start" in Odin.
It should now reboot and go to the boot animation. If it doesn't boot in 15 minutes, shutdown the device. Then hold the Volume Up, Home/Bixby, and Power buttons. Then use the keys to select "Factory reset". Please note this will wipe all user data. Once it finishes you can select "Reboot" and now it should boot correctly.
I have been battling with this problem so long I only wanted to root my tablet to have some fun with root required apps
Any help with the problem? I only need to root the device or get it to work with stock rom