Forgot Your Password? Here's A [GUIDE] To Remove Password Without Data Loss. [ROOT] - Samsung Galaxy A10 Guides, News, & Discussion

Sometimes Password lags or something and you will not be able to use your phone, here's a ROOT-ONLY method.
Are you a veteran? Here's a short guide. (in "/data/system" delete locksettings.db, locksettings.db.shm, locksettings.db.wal)
Not a veteran? (Don't know a lot about phone stuff)
Read this guide.
Code:
Alert, do NOT delete any file from system to "free up space", this will kill your device. I'm not responsible if you do something -outside this guide- that might damage your phone, read carefully and good luck!
REQUIREMENTS:
-You will need a recovery that can delete files (has a 'file manager' feature), Recommend: TWRP Recovery
GUIDE:
Step 1: Reboot to recovery mode,
This can be done -on the galaxy a10- by turning your phone off and long-clicking volume up button THEN power button (at the same time), but it might ask for password while turning it off, so we need to reboot it manually.
While the phone is on... long click power and volume down for 7.5 seconds, it will turn off. Immediately when it turns off you need to keep clicking power but click volume up instead of down, when the phone boots it will get in the recovery mode, for sure.
Step 2: Locate the password file
The password file is the file your phone stores your pin/pattern/password at. it is called 'locksettings.db'
We need to delete it -and all it's "variants"- from your device.
In twrp... choose 'ADVANCED'.
choose 'FILE MANAGER' after that.
it will show you the files on your phone. If you look at the top file (the highest one) it will be called (up a level), click it again and again until it disappears. If you don't see that file that means you are at the deepest folder (ROOT).
choose "data" folder
choose "system" folder
Scroll down until you find "locksettings.db" tap it and click DELETE.
Do the same for "locksettings.db.shm" and "locksettings.db.wal" (delete them too)
Step 3: Rebooting into the os
To turn your phone on again click the back button and return to the home screen.
Click "REBOOT"
Click "SYSTEM"
That's all now the password is removed.
Tested on Samsung Galaxy A10
Need more help? Contact me on my telegram, https://t.me/BrudherBoard

"-You will need a recovery that can delete file"
You can't install a custom recovery without Usb Debugging and OEM unlocking.
What's the point of the tutorial ?

gsmer87 said:
"-You will need a recovery that can delete file"
You can't install a custom recovery without Usb Debugging and OEM unlocking.
What's the point of the tutorial ?
Click to expand...
Click to collapse
well you can see [ROOT] at the end of the title, so
rooting your phone means unlocking bl, so [ROOT] means your bootloader is unlocked and you have a custom recovery that can install zips such as magisk so you can grant root access to apps.
now tell me what's the point of your message?

BrotherBoard said:
well you can see [ROOT] at the end of the title, so
rooting your phone means unlocking bl, so [ROOT] means your bootloader is unlocked and you have a custom recovery that can install zips such as magisk so you can grant root access to apps.
now tell me what's the point of your message?
Click to expand...
Click to collapse
The point of my message is that your tutorial is useless. You can't root your phone without data loss and putting the [ROOT] in your [GUIDE] doesn't make it less useless.
PLEASE prove me wrong ! I wold realy like to be wrong about this .

Total useless nowadays
Now all device's have FRP & KG enable
And with this you can't flash any custom image

gsmer87 said:
The point of my message is that your tutorial is useless.
Click to expand...
Click to collapse
Mr Hassan said:
Total useless nowadays
Click to expand...
Click to collapse
I have to disagree a bit with these statements. It's not entirely useless but the demographic this targets is very limited.
For this tutorial to work you have to
1) Have your phone rooted with a custom recovery
2) Have your data unencrypted by going out of your way to keep it unencrypted
Not everyone meets these 2 criteria but for those who do, this is somewhat helpful so that you know which files exactly are responsible for your lock method in lockscreen.
I'd probably add those 2 as perquisites so that you don't get bombarded with noobs asking why they can't access their data partition even if they have a custom recovery.

ShaDisNX255 said:
I have to disagree a bit with these statements. It's not entirely useless but the demographic this targets is very limited.
For this tutorial to work you have to
1) Have your phone rooted with a custom recovery
2) Have your data unencrypted by going out of your way to keep it unencrypted
Not everyone meets these 2 criteria but for those who do, this is somewhat helpful so that you know which files exactly are responsible for your lock method in lockscreen.
I'd probably add those 2 as perquisites so that you don't get bombarded with noobs asking why they can't access their data partition even if they have a custom recovery.
Click to expand...
Click to collapse
i've literally put a [ROOT] at the title

gsmer87 said:
The point of my message is that your tutorial is useless. You can't root your phone without data loss and putting the [ROOT] in your [GUIDE] doesn't make it less useless.
PLEASE prove me wrong ! I wold realy like to be wrong about this .
Click to expand...
Click to collapse
in new phones that are not rooted, there is no way to remove lock screen without data loss, sir imagine locking your house up with the key inside, how would you get in?

BrotherBoard said:
in new phones that are not rooted, there is no way to remove lock screen without data loss, sir imagine locking your house up with the key inside, how would you get in?
Click to expand...
Click to collapse
There are so many ways to get into a house without a key; you can't even imagine.
Wait.. Is the house rooted? :]

Timmmmaaahh! said:
There are so many ways to get into a house without a key; you can't even imagine.
Wait.. Is the house rooted? :]
Click to expand...
Click to collapse
maybe but I'm talking about not being able to use your phone, not breaking in a house :]

BrotherBoard said:
maybe but I'm talking about not being able to use your phone, not breaking in a house :]
Click to expand...
Click to collapse
Hey, you started the house analogy. And it was over 2 months ago, you're too late for a retort

Timmmmaaahh! said:
Hey, you started the house analogy. And it was over 2 months ago, you're too late for a retort
Click to expand...
Click to collapse
ok bro no hate, you have replied to a thread that I was just bored and like why not to write that up on xda and I have put a [ROOT] in the title, I see I have made no mistakes at this.

BrotherBoard said:
Sometimes Password lags or something and you will not be able to use your phone, here's a ROOT-ONLY method.
Are you a veteran? Here's a short guide. (in "/data/system" delete locksettings.db, locksettings.db.shm, locksettings.db.wal)
Not a veteran? (Don't know a lot about phone stuff)
Read this guide.
Code:
Alert, do NOT delete any file from system to "free up space", this will kill your device. I'm not responsible if you do something -outside this guide- that might damage your phone, read carefully and good luck!
REQUIREMENTS:
-You will need a recovery that can delete files (has a 'file manager' feature), Recommend: TWRP Recovery
GUIDE:
Step 1: Reboot to recovery mode,
This can be done -on the galaxy a10- by turning your phone off and long-clicking volume up button THEN power button (at the same time), but it might ask for password while turning it off, so we need to reboot it manually.
While the phone is on... long click power and volume down for 7.5 seconds, it will turn off. Immediately when it turns off you need to keep clicking power but click volume up instead of down, when the phone boots it will get in the recovery mode, for sure.
Step 2: Locate the password file
The password file is the file your phone stores your pin/pattern/password at. it is called 'locksettings.db'
We need to delete it -and all it's "variants"- from your device.
In twrp... choose 'ADVANCED'.
choose 'FILE MANAGER' after that.
it will show you the files on your phone. If you look at the top file (the highest one) it will be called (up a level), click it again and again until it disappears. If you don't see that file that means you are at the deepest folder (ROOT).
choose "data" folder
choose "system" folder
Scroll down until you find "locksettings.db" tap it and click DELETE.
Do the same for "locksettings.db.shm" and "locksettings.db.wal" (delete them too)
Step 3: Rebooting into the os
To turn your phone on again click the back button and return to the home screen.
Click "REBOOT"
Click "SYSTEM"
That's all now the password is removed.
Tested on Samsung Galaxy A10
Need more help? Contact me on my telegram, https://t.me/BrudherBoard
Click to expand...
Click to collapse
Was useful for me bro

SsamsungA10 said:
Was useful for me bro
Click to expand...
Click to collapse
are you Samsung A10 from telegram

...was also helpful for me. Thank you!

Related

[HOWTO] Easy Root Instructions (Sprint or T-Mobile) [Updated 24 June 2012]

First off, let me say that I did not develop this schtuff and all thanks should go to those that did. Special thanks to noobnl (his thread here), mskip and TeamEpic for all their work.
A note about these instructions:
They're long and may seem a little daunting to those that aren't experienced. Please don't let that deter you as they've been written to be as simple and easy to follow as is reasonably possible assuming you can work a Windows PC and extract a zip file.
==> If you encounter problems with these instructions, please check the FAQ in the post following this one. <==
For video instructions (courtesy of qbking77) scroll to the bottom of this post.
General Disclaimer:
Use these tools and this guide at your own risk. Doing these things wrong/improperly/etc. has the ability to completely ruin your device and YOU assume all risk and responsibility if that happens.
Also note that rooting WILL violate the manufacturers warranty on the device making it ineligible for warranty repair. If you have insurance on the device however, they MAY still replace it for the cost of your deductible.
Click to expand...
Click to collapse
Non-ADB Root instructions (Windows Only):
First, the non-dangerous, standard user stuff:
Download and install the Samsung USB drivers from Samsung's website: http://downloadcenter.samsung.com/c...nt_L710_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Turn on Debugging on your Phone
Open Settings
Select "Developer options" in the System section
Check the box for "USB Debugging"
Press "OK" to confirm.
Plug you phone up to your computer using the USB cable and allow the drivers to install.
Download CMW_SuperUser_v3.07.zip from the bottom of this post
I recommend making yourself a nice little GS3 folder in your downloads folder for all this stuff so it's easy to find
DO NOT UNZIP!!
Copy CMW_SuperUser_v3.07.zip on to the Root of your GS3s INTERNAL storage (if you put it into a folder, you may have a hard time finding it later, but that's on you).
DO NOT UNZIP!!
Unplug your phone
Power off your phone
Now, this is the part that can BRICK your phone so follow ALL instructions CAREFULLY!!
Download Odin3-v3.04 from the bottom of this post
Extract Odin3-v3.04 into it's own folder somewhere where you can easily find it.
Download clockworkmod.tar from the bottom of this post to somewhere you can easily find it.
Reboot your phone into download mode
Hold down Volume Down, Home and then the Power button until the Warning!! message is displayed
Press Volume Up to continue.
Your phone should now be in download mode, displaying a green Android and say Downloading. If it is not, power off your phone by holding down the power button and then try to get into Download mode again. Do NOT progress until you have done so.
Go into the folder you extracted Odin3 into and run Odin3 v3.04.exe (you may have to Right-Clik => Run as Administrator)
Connect your phone to your computer via USB. Drivers may install again; if this happens, allow them to finish before progressing.
In Odin, the COM box all the way to the left should turn blue and it should say Added!! in the Message area.
Click on PDA and in the Open window that pops up navigate to and open the clockworkmod.TAR file you downloaded earlier
Verify that Auto Reboot and F. Reset Time are checked
Click Start. Once the process is completed you device should automatically reboot and there will be a green PASS! box in the upper left of the window. You can then close Odin.
Power off your device and boot into Recovery mode
To boot into Recovery mode: Hold down Volume Up, Home and then the Power button until the device begins to power on then release all 3.
You'll know you're in recover mode when it says "CWM-based Recovery" at the top of the screen
Install CMW_SuperUser_v3.07.zip that you copied onto your internal memory
Navigating ClockWorkMod Recovery: Use the Volume Up and Down rocker to change the highlighted option and the Home button to select an option. The Back softkey works, but will not be lit and will take you back one screen.
Installing a zip:
Select "Install zip from sdcard" (Yes, I know it's on the internal storage.)
Select "Choose zip from sdcard"
Select the zip you want to install; in this case CWM_SuperUser_v3.0.7.zip
Select "Yes" to begin installing
Once the process has completed use the Back arrow to get back to the main recovery screen (Remember: it works, but it's not lit) and select "reboot system now." Once your device boots up you should now be 'Rooted,' but there's still a few more things to be done
Install BusyBox. There are actually several ways to do this, but the BusyBox app in the Google Play Market is quick and easy.
Install BusyBox (this is a link to the online verison of the Google Play store. You can actually follow this link and install it from there and it will get pushed to your phone. Alternatively, just search for BusyBox in the Google Play store and it should be the first app in the search results from author Stephen (Stericson))
Open BusyBox Free from your App Drawer
Allow it Root access when it prompts you
Tap the red "X" to close the dialog window that pops up
Allow BusyBox to scan you phone
Tap "Install" to install BusyBox and make the necessary file changes.
Update your Binaries.
Open the Superuser App from the App Drawer
Get into settings (the wrench icon in the upper right of the screen)
Select Su binary under the General section towards the bottom of the list
Select Update
Your device is now rooted and all set.
How to video (YouTube): http://www.youtube.com/watch?v=7Soapch0c5U
Thanks again to qbking77 for the instructions video!
P.S. If you are a developer or I have used some of your material and/or you feel you should be credited, please let me know and I will update this post.
Frequently Asked Questions
This FAQ is in the works as more questions roll in so I'll do my best to keep it updated.
Q: Odin failed! What do I do!?
A: Try plugging your USB cable into a different USB port on your computer and/or try a different USB cable (Odin's picky about the cable). The drivers may install again; if so, wait for them to finish. After that, verify that the device shows as Added in Odin again and click start again. If that still fails, try unchecking F. Reset Time box and removing any MicroSD card you have in the device, plug the device into (yet another) USB port and try again.
Q: Will these instructions work for other US (LTE) versions of the GS3?
A: I have not personally tested this method on any other versions of the GS3 but uoY_redruM and carrrnuttt (and others) have confirmed that this method works for the T-Mobile version as well. It should in theory also work for the AT&T and Verizon versions, though that's unconfirmed at this point.
Q: Ok, so I've got Root. What now?
A: That's entirely up to you. Root allows a near endless amount of customizatoin, but some of the most commonly sought after benefits of Root are these:
Root Only applications. These allow you to simply do more with your phone or tweak the way it functions. Some that I personally recommend are:
Titanium Backup and its Pro Key => For making backups of your apps, app data and system data and uninstalling or freezing Bloatware.
Quick Boot => For booting drectily to recovery or Download Mode (listed as Bootloader in the App)
Removing Bloatware => I recommend Titanium Backup for this
Loading custom ROMs. There aren't many floating around just yet, but I expect that'll change soon as the ball gets rolling.
Excellent write-up. Thanks. Now can we install custom roms from other forums or do we have to specifically wait for any to come up here.
Great write up! very easy and simple
daniel06gt said:
Excellent write-up. Thanks. Now can we install custom roms from other forums or do we have to specifically wait for any to come up here.
Click to expand...
Click to collapse
You should wait for any specific Sprint Galaxy S3 ROMs that get posted if you want to ROM your phone. I'm sure some will be popping up by the end of the weekend so I wouldn't expect that you'll have to wait too long
Excellent write up, though I don't see the difference in methods; maybe because I speed read it but if you follow noobnl's method, you basically do the same thing, minus the adb to set the permissions, though if you install busybox, its the same goal. Again great because some people are afraid of adb.
Very nice work... I'll get a how to video going very soon!
(repost, sorry)
Great write-up! Thanks for taking the time to do this.
Thanks for writing this up!
teh roxxorz said:
Excellent write up, though I don't see the difference in methods; maybe because I speed read it but if you follow noobnl's method, you basically do the same thing, minus the adb to set the permissions, though if you install busybox, its the same goal. Again great because some people are afraid of adb.
Click to expand...
Click to collapse
Yes, this and noobl's method are pretty much the same, the main reason for this post is to put the method into an easy-to-read step-by-step format that's easy for beginners to follow. Remember, we were all beginners at some point
I come from HTC so Odin is new to me, this guide is little more friendly than noobl's method. Although either would suffice this is just pretty clearly laid out.
Look forward to root.
Very nice and simple
Thank you. Now let the games begin....
cypher_zero said:
[...]Remember, we were all beginners at some point
Click to expand...
Click to collapse
While I expect a fair amount of carry-overs from Sprint Epic's and Epic Touch's, I also expect a large influx of excited users who haven't used a Galaxy S phone before.
:highfive:
How to video is done! Just have to compile and upload it
qbking77 said:
How to video is done! Just have to compile and upload it
Click to expand...
Click to collapse
Always on the ball qbking77 gotta add galaxy s 3 to your signature now =)
teh roxxorz said:
Excellent write up, though I don't see the difference in methods; maybe because I speed read it but if you follow noobnl's method, you basically do the same thing, minus the adb to set the permissions, though if you install busybox, its the same goal. Again great because some people are afraid of adb.
Click to expand...
Click to collapse
I hate adb that shiit is tedious LOL
tj.iscool said:
I hate adb that shiit is tedious LOL
Click to expand...
Click to collapse
You can always script a bat file or two, saves always rewriting commands.
tj.iscool said:
I hate adb that shiit is tedious LOL
Click to expand...
Click to collapse
I actually prefer adb over one click roots.
Something about seeing what your doing and sense of accomplishment lol
cypher_zero said:
Yes, this and noobl's method are pretty much the same, the main reason for this post is to put the method into an easy-to-read step-by-step format that's easy for beginners to follow. Remember, we were all beginners at some point
Click to expand...
Click to collapse
No qualms there, just making sure I didn't miss anything. Though you are right, it may be hard for a beginner to follow noob's more experienced cut throat guide. Kudos.

[GUIDE][ROOT][CWR/TWRP][DEODEX][OVERCLOCKING] SGH-S730M - Samsung Galaxy Discover

Note: This is an old phone. It's no longer being supported by Samsung, and I see that nobody is selling this phone except for eBay or Amazon. I also have a new phone now and my Discover is simply sitting there for me to have fun with. I won't be actively developing for this phone. However, I will provide support with any issues you may encounter. This thread will be kept here for future reference if anyone needs help.
Update (2022): ​I am no longer using Android. This is my last update here.​Copies of the relevant files are shared in this google drive link:​
SGH740M Root Files - Google Drive
drive.google.com
​
Please thank Ivdoan he is the mastermind behind finding and implementing root for this phone.
Thanks to JohnnyGalto for giving us updated CWM, TWRP, and Partition Tables!
THIS THREAD IS INTENDED TO USE ONLY FOR THE SGH-S730M, AND NOT FOR ANY OTHER PHONE. I CANNOT CONFIRM THAT IT WILL WORK ON ANY OTHER SGH-S730 VARIANTS, SO USE THIS THREAD AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR ANY DATA LOSS, OR BRICKING THAT IS A RESULT FROM YOU CHOOSING TO ROOT. HOWEVER, IF YOU SOFT BRICK YOUR PHONE, IT CAN BE FIXED VIA CLOCKWORK RECOVERY. WARNING ABOUT USING ODIN: IF YOU ARE A NOOB, ONLY CLICK ON THE BUTTONS I TELL YOU TO CLICK, AND NOTHING ELSE. I ACCIDENTALLY SOFT BRICKED MY PHONE BECAUSE I HIT THE WRONG BUTTON WHILE USING ODIN - AND DONT WANT YOU TO DO THE SAME THING. AND LASTLY, ROOTING AND MODDING THIS PHONE WILL VOID YOUR WARRANTY. SINCE THERE IS NO OFFICIAL WAY TO RETURN TO STOCK, ONCE YOU MODIFY YOUR PHONE: YOU ARE ON YOUR OWN FATE!
IF YOU HAVE THE 730G VARIANT (Tracfone, Net10), GO HERE: http://forum.xda-developers.com/showthread.php?p=47417608
Click to expand...
Click to collapse
Issues and Bugs (Known Problems)
Okay, with deodexing - sometimes the SamsungIME.apk in the /system/app directory can be a pain to deal with! I put a warning in my deodex CWR script that tells about this issue. It does seem to correct itself overtime, so I am not too worried at the moment (but still very annoyed).
Also, it seems that many users have been experiencing strange battery problems (such as the phone suddenly losing half of its charge in 3 minutes). I hope it is an software issue (correctable), or just a battery issue (fixable), rather than a hardware issue (hard to fix).
Rooting, Custom Recovery, and Unbricking Guide (Everyone)
]If you want to root your phone then follow part A.
If you want to root your phone and add custom recovery then follow parts A and B.
If you have soft bricked your phone, then please complete all steps outlined below (if not already done yet).
The tutorial is done on a Windows computer and is meant for a Windows computer. Steps will vary slightly or tremendously if it is done on any other OS.
Part A - Rooting the SGH-S730m
1. Download and install UnlockRoot Free on your PC. YOU DO NOT HAVE TO INSTALL BLOATWARE!!! PLEASE READ SETUP INSTRUCTIONS CAREFULLY!!!
2. Download and Install Samsung USB Drivers. If it prompts you to reboot for any reason, then reboot your Computer.
3. After all of this is over, you have to prepare yourself for the hardest part of this whole process, and maybe the most complicated dilemma you will ever face in the entirety of your lives.
4. Turn on your phone if it isn't already. Wait for the phone to fully boot.
5. Plug your phone into the computer via USB.
6. Run UnlockRoot on your computer and click the "Root" Button (when it prompts you to install bloatware apps on your device, say no).
DO NOT UNPLUG YOUR PHONE UNTIL UnlockRoot SAYS IT IS OK TO DO SO!!!!
Congratulations, you have should now have a rooted SGH-730m in proximity to your hands! :fingers-crossed:
How to verify your 730M is rooted
If by any reason, you feel unsure as to if your phone is actually rooted or not:
Install a root checking app.
These apps will tell you if your phone has root access or not.
Try Root Checker from the Google Play Store.
Install a terminal emulation app.
In these apps, type the command "su" (without quotes). If you get "permission denied" you have not rooted your device. If it prompts you for root privileges (ie a popup appears) then your device is rooted!
Try Terminal Emulator from the Google Play Store.
If you are a n00b (like me occasionally), and you fail to understand why something works, or, the exact opposite: Don't worry! You probably thought the auxiliary headphone jack was the USB port, or, thought you should unplug your phone early, despite me warning you not to do that. That's okay, you can get it fixed.
Part B - Installing a Custom Recovery
If you are not already acquainted with the idea of Custom Android Recovery, don’t be afraid. It allows developers, tweakers and noobs alike to backup, restore, fix, and to install custom ROMs and Kernels designed specifically for their device. It becomes extremely useful, because it allows people to remove “soft bricks†from their devices (which occurs when someone flashes data to the wrong device, or wrong parts of the device respectively).
I know you probably just want to not read this stuff anyways But I need to pay tribute to the developers Ivdoan and JohnnyGalto for there amazing work at compiling these custom binaries for the Samsung Galaxy Discover. Thanks guys.
So, lets get started – shall we?
Click to expand...
Click to collapse
YOU MUST ROOT YOUR PHONE BEFORE YOU DO THIS!!!!!
1. Download either the SGH_S730M.CWM_6.0.3.1.custom.recovery.tar.zip or the SGH_S730M.TWRP_2.5.0.0.custom.recovery.tar.zip file, and extract its contents to your desktop (if you don’t know what a desktop is, then please leave. You will probably break your device).
Just to clarify for those noobs out there: CWR stands for “ClockWork Recovery†and TWRP stands for “Team Win Recovery Projectâ€. They both are custom recoveries, and basically do the same thing. Personally, I would recommend the CWR for people that just want simplicity, and the TWRP for people that want more appeal. TWRP for this device is still under development, so be careful!
Click to expand...
Click to collapse
2. Then, download the Odin Flashing Program attached to this post. Extract its contents to wherever you find necessary.
DO NOT MESS WITH ODIN! IT IS NOT A TOY! IT CAN BRICK YOUR PHONE!
Odin, is a flashing tool. It is not made to be user friendly, and is meant for people who know how to use it. I will be very blunt by saying that I AM NOT RESPONSIBLE FOR YOU NOT DOING EXACTLY WHAT I TELL YOU! PROCEED WITH CAUTION!
Click to expand...
Click to collapse
3. Right Click on Odin, and click “Run as Administrator†(if available).
4. CLICK ON THE PDA BUTTON
5. When the file window appears, browse to the desktop directory (your desktop) and select either the S730M-CWR.tar.md5 or the S730M-TWRP.tar.md5 (depending on what version you downloaded).
6. Now shutdown your phone. Plug your phone into your computer. Boot into download mode by turning on the phone (release the power button as the phone vibrates) and holding the lower volume button and home key. Follow the instructions (press the upper volume button) to continue with download mode.
7. If your phone has been detected by Odin, the proceed.
8. Inside of Odin, press the Start button.
DO NOT DISCONNECT, UNPLUG, PLAY WITH ANY BUTTONS, OR CLICK ANYTHING ON EITHER THE PHONE OR COMPUTER UNTIL ODIN HAS FINISHED FLASHING CLOCKWORK RECOVERY ON YOUR PHONE.
8. To boot into clockwork recovery, hold down the upper volume and power key until the first vibration, then just hold the volume key.
That should be IT! :highfive:
Part C - Soft Brick Recovery (CWM Recovery Only!)
YOU MUST HAVE A MICRO SD CARD WITH AT LEAST 400 MB OF FREE STORAGE SPACE TO DO THIS!
build.prop restore script
You need busybox installed on your phone in order to use this script! If you dont have busybox, it wont work.
If you messed up your build.prop file (If you did, then you will know that you did), then you can use this script to restore you build.prop file to the original stock format.
1. Download the build.prop restore script, to your device (preferably a computer).
2. Place the zip file to the root (/) directory of your micro SD Card.
3. Remove the SD card from the computer, and turn off the SGH-S730M.
4. Remove the back plating from the phone, and insert the micro SD card into the phone. It should be named SGH-S730M CWR stock build.prop.
5. After putting the phone back together, boot into recovery by holding down the upper volume and power key until the first vibration, then just hold the volume key.
6. Using the volume buttons as scrolling keys, scroll down using the lower volume until you see install zip from sdcard as highlighted text. Using the power key as the enter button, click the power button.
7. Then, also using the volume keys, scroll down to the choose zip from sdcard option, and click the power button.
8. If you placed the zip file exactly where I told you to: you should see SGH-S730M CWR stock build.prop as an item. Scroll down to the file and click the power button. Then, when it prompts you to "Confirm Install", scroll down to "Yes - install".
9. Press the power button.
WAIT FOR THE PHONE TO BE 100% DONE EXECUTING THE SCRIP! YOU COULD MESS UP THE PHONE. DO NOT TURN OFF THE PHONE.
Full Restore (If all else fails)
To reduce confusion, please remove any backups that you may already have (which would be funny, you wouldnt have to do this anyways).
1. Download the rooted stock CWM Recovery Image (.zip) from here, to your device (preferably a computer). http://forum.xda-developers.com/showthread.php?t=2677332
2. Extract ALL of the contents of the zip file to the root (/) directory of your micro SD Card. The folder should be named "clockworkrecovery".
3. Remove the SD card from the computer, and turn off the SGH-S730m.
4. Remove the back plating from the phone, and insert the micro SD card into the phone.
5. After putting the phone back together, boot into recovery by holding down the upper volume and power key until the first vibration, then just hold the volume key.
6. Using the volume buttons as scrolling keys, scroll down using the lower volume until you see backup and restore as highlighted text. Using the power key as the enter button, hit the power button.
7. Then, also using the volume keys, scroll down to the restore option, and click the power button.
8. If you extracted the zip file the exact way I told you to: you should see a menu option. If you didn't do what I told you to, you may see "No files found". If it says "cant mound /sd" (or something similar), you probably have a bad SD Card, or, forgot to put it in correctly.
9. Press the power button.
WAIT FOR THE PHONE TO BE 100% DONE RESTORING YOUR BACKUP TO THE PHONE! YOU COULD HARD BRICK THE PHONE (BECAUSE CWM RECOVERY WRITES TO THE BOOTLOADER). DO NOT TURN OFF THE PHONE. THE PHONE IS NOT FROZEN IF IT WONT RESPOND FOR A WHILE.
10. If you did this correctly, you should have a rooted, and restored SGH-S730m!
Part E - Removing that annoying triangle from the boot sequence
Use the triangleaway script in the attatchments. (triangleaway.zip)
It resets flash counter and resets binary status to official.
Might have to do a factory reset to return current status to official.
Boot your phone into recovery mode
Extract triangleaway.sh from the zip file.
Open up ADB Shell
push triangleaway.sh /tmp
chmod 755 triangleaway.sh
execute triangleaway.sh
Reboot Phone.
Overclocking and Modding (DEVELOPERS ONLY)
SYSTEM MODS
If you don't know what you are doing, then, please don't read any further. its for your own good
The CSC directory can be deleted (and the files in the main /system directory that are associated with it). It does not affect the phone at all. Also, If you go to /system/etc/feature_default.xml you can change the phones features. So far, I have done many tweaks to the Messaging, Phone, Settings, People (Contacts) and Lock screen of the phone! If you are a developer (or tweaker like me), you should be able to enable/disable whatever you like using the feature_default.xml.
Overclocking
FitAmp has made a overclocking script for 1GHz (1000MHz). There is quite a noticeable difference in response, but, the phone still tends to lag a bit. File is attatched to the thread (S730M-OC-1000MHz.zip)
Custom ROMs
Custom ROMS by atmu5fear. All flashable ZIPs. - http://forum.xda-developers.com/showthread.php?t=2677332
I'm also making one for the Discover. It should be coming soon.
Please click :good: if it works for you!
Where can I find the OC script? Thanks
evertking said:
Where can I find the OC script? Thanks
Click to expand...
Click to collapse
The Script it attached to this post.
Procedures (using ADB)
put boot.img on sdcard:
adb push boot.img /sdcard/boot.img
Then, from adbshell:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
then reboot device.
shifattk said:
the op of this post decided to dump this thread and developing, so i decided to take over & repost this, as requested by the op.
I will also organize and add more of my stuff. That might take at least a week or so since everything is a mess right now, but i will do it.
***** original thread is here *****
please thank ivdoan he is the mastermind behind finding and implementing root for this phone.
Thanks to johnnygalto for giving us updated cwm, twrp, and partition tables!
issues and bugs (known problems)[
okay, with deodexing - sometimes the samsungime.apk in the /system/app directory can be a pain to deal with! I put a warning in my deodex cwr script that tells about this issue. It does seem to correct itself overtime, so i am not too worried at the moment (but still very annoyed).
Also, it seems that many users have been experiencing strange battery problems (such as the phone suddenly losing half of its charge in 3 minutes). I hope it is an software issue (correctable), or just a battery issue (fixable), rather than a hardware issue (hard to fix).
rooting, custom recovery, and unbricking guide (everyone)
if you want to root your phone then follow part a.
If you want to root your phone and add custom recovery then follow parts a and b.
If you have soft bricked your phone, then please complete all steps outlined below (if not already done yet).
The tutorial is done on a windows computer and is meant for a windows computer. Steps will vary slightly or tremendously if it is done on any other os.
part a - rooting the sgh-s730m
1. Download and install unlockroot free on your pc. You do not have to install bloatware!!! Please read setup instructions carefully!!!
2. Download and install samsung usb drivers. If it prompts you to reboot for any reason, then reboot your computer.
3. After all of this is over, you have to prepare yourself for the hardest part of this whole process, and maybe the most complicated dilemma you will ever face in the entirety of your lives.
4. Turn on your phone if it isn't already. Wait for the phone to fully boot.
5. Plug your phone into the computer via usb.
6. Run unlockroot on your computer and click the "root" button (when it prompts you to install bloatware apps on your device, say no).
do not unplug your phone until unlockroot says it is ok to do so!!!!
congratulations, you have should now have a rooted sgh-730m in proximity to your hands! :fingers-crossed:
how to verify your 730m is rooted if by any reason, you feel unsure as to if your phone is actually rooted or not:
install a root checking app.
these apps will tell you if your phone has root access or not.
Try root checker from the google play store.
install a terminal emulation app.
in these apps, type the command "su" (without quotes). If you get "permission denied" you have not rooted your device. If it prompts you for root privileges (ie a popup appears) then your device is rooted!
Try terminal emulator from the google play store.
If you are a n00b (like me occasionally), and you fail to understand why something works, or, the exact opposite: Don't worry! You probably thought the auxiliary headphone jack was the usb port, or, thought you should unplug your phone early, despite me warning you not to do that. That's okay, you can get it fixed.
part b - installing a custom recovery
you must root your phone before you do this!!!!!
1. Download either the sgh_s730m.cwm_6.0.3.1.custom.recovery.tar.zip or the sgh_s730m.twrp_2.5.0.0.custom.recovery.tar.zip file, and extract its contents to your desktop (if you don’t know what a desktop is, then please leave. You will probably break your device).
2. Then, download the odin flashing program attached to this post. Extract its contents to wherever you find necessary.
3. Right click on odin, and click “run as administrator” (if available).
4. Click on the pda button
5. When the file window appears, browse to the desktop directory (your desktop) and select either the s730m-cwr.tar.md5 or the s730m-twrp.tar.md5 (depending on what version you downloaded).
6. Now shutdown your phone. Plug your phone into your computer. Boot into download mode by turning on the phone (release the power button as the phone vibrates) and holding the lower volume button and home key. Follow the instructions (press the upper volume button) to continue with download mode.
7. If your phone has been detected by odin, the proceed.
8. Inside of odin, press the start button.
do not disconnect, unplug, play with any buttons, or click anything on either the phone or computer until odin has finished flashing clockwork recovery on your phone.
8. To boot into clockwork recovery, hold down the upper volume and power key until the first vibration, then just hold the volume key.
That should be it! :highfive:
part c - soft brick recovery (cwm recovery only!)
you must have a micro sd card with at least 400 mb of free storage space to do this!
build.prop restore script
you need busybox installed on your phone in order to use this script! If you dont have busybox, it wont work.
if you messed up your build.prop file (if you did, then you will know that you did), then you can use this script to restore you build.prop file to the original stock format.
1. Download the build.prop restore script, to your device (preferably a computer).
2. Place the zip file to the root (/) directory of your micro sd card.
3. Remove the sd card from the computer, and turn off the sgh-s730m.
4. Remove the back plating from the phone, and insert the micro sd card into the phone. It should be named sgh-s730m cwr stock build.prop.
5. After putting the phone back together, boot into recovery by holding down the upper volume and power key until the first vibration, then just hold the volume key.
6. Using the volume buttons as scrolling keys, scroll down using the lower volume until you see install zip from sdcard as highlighted text. Using the power key as the enter button, click the power button.
7. Then, also using the volume keys, scroll down to the choose zip from sdcard option, and click the power button.
8. If you placed the zip file exactly where i told you to: You should see sgh-s730m cwr stock build.prop as an item. Scroll down to the file and click the power button. Then, when it prompts you to "confirm install", scroll down to "yes - install".
9. Press the power button.
wait for the phone to be 100% done executing the scrip! You could mess up the phone. Do not turn off the phone.
full restore (if all else fails)
to reduce confusion, please remove any backups that you may already have (which would be funny, you wouldnt have to do this anyways).
1. Download the rooted stock cwm recovery image (.zip) i made from here, to your device (preferably a computer).
2. Extract all of the contents of the zip file to the root (/) directory of your micro sd card. The folder should be named "clockworkrecovery".
3. Remove the sd card from the computer, and turn off the sgh-s730m.
4. Remove the back plating from the phone, and insert the micro sd card into the phone.
5. After putting the phone back together, boot into recovery by holding down the upper volume and power key until the first vibration, then just hold the volume key.
6. Using the volume buttons as scrolling keys, scroll down using the lower volume until you see backup and restore as highlighted text. Using the power key as the enter button, hit the power button.
7. Then, also using the volume keys, scroll down to the restore option, and click the power button.
8. If you extracted the zip file the exact way i told you to: You should see a menu option. If you didn't do what i told you to, you may see "no files found". If it says "cant mound /sd" (or something similar), you probably have a bad sd card, or, forgot to put it in correctly.
9. Press the power button.
wait for the phone to be 100% done restoring your backup to the phone! You could hard brick the phone (because cwm recovery writes to the bootloader). Do not turn off the phone. The phone is not frozen if it wont respond for a while.
10. If you did this correctly, you should have a rooted, and restored sgh-s730m!
part d - soft brick recovery (twrp recovery only!)coming soon..
part e - removing that annoying triangle from the boot sequence..to a thread near you! (it's already here. I'm just organizing them so it is easier to understand and to use)
deodexing, overclocking and modding (developers only)
deodexing you rom
you must have a micro sd card with at least 100 mb of free storage space to do this!
so, after some work (and tons of patience), i managed to make a deodexed version of this phone. So, ive made a deodex script for cwr, that will remove you old /system/app and /system/framework directories, and makes new ones, with the new deodexed files.*
now, since this is considered a more "advanced" tweak, i am not going to post a step-by-step guide on how to do this.
Why? Well, if you really needed instructions to do this: You probably shouldn't be doing it anyways!
For developers: Make sure you have busybox installed, then install the zip here via cwr (its easy to see what file it is). Remember to wipe dalvik cache. There are some temporary bugs with the samsungime.apk, which wont work right for a while. Mysteriously though, the problem corrects itself after some time using the phone. Reply your findings!
For noobs: Don't do this, it will just make no difference, and i honestly don't feel like solving problems that don't need to be solved (or, ones due to illiteracy). Wait until you know what you are doing (and what an odex file is), then try this yourself.
system mods
if you don't know what you are doing, then, please don't read any further. Its for your own good
the csc directory can be deleted (and the files in the main /system directory that are associated with it). It does not affect the phone at all.
Also, if you go to /system/etc/feature_default.xml you can change the phones features. So far, i have done many tweaks to the messaging, phone, settings, people (contacts) and lock screen of the phone! If you are a devleloper (or tweaker like me), you should be able to enable/disable whatever you like using the feature_default.xml.
overclocking
fitamp has made a overclocking script for 1ghz (1000mhz). There is quite a noticeable difference in response, but, the phone still tends to lag a bit. File is attatched to the thread (s730m-oc-1000mhz.zip)
please click :good: If it works for you!
Click to expand...
Click to collapse
and where is the odin did you the number
thanks
manuelelitaliano said:
and where is the odin did you the number
thanks
Click to expand...
Click to collapse
Hi there,
Sorry for the late reply. I've been quite busy lately.
http://forum.xda-developers.com/showthread.php?t=2189539
^ That thread has the downloads for Odin.
???
Hey guys,
have we found a way to fix my problem with the phone, I still have no access to download, recovery, normal boot and it stays on for 7 secs max. This has ocured because I flashed the wrong file to modem. Let me know as I want to start working on development again.
camvar97 said:
Hey guys,
it stays on for 7 secs max.
Click to expand...
Click to collapse
^ That, to me looks like the battery is not charged (unless I am wrong).
camvar97 said:
Hey guys,
... I still have no access to download, recovery, normal boot and it stays on for 7 secs max. ... This has ocured because I flashed the wrong file to modem.
Click to expand...
Click to collapse
I've searched around a bit, and the best option would be to send it for repair IMO.
shifattk said:
^ That, to me looks like the battery is not charged (unless I am wrong).
I've searched around a bit, and the best option would be to send it for repair IMO.
Click to expand...
Click to collapse
as for the battery thats what samsung says might be the problem and that i need a new one
SGH-730G Users ONLY
Here is a thread I started this morning about the SGH-730G (Tracfone, Net10, Straight Talk) variant of the Discover. I created this thread so there wouldn't be confusions due to the slight differences between the 730G and the 730M variants. Right now there is a root method listed, and I am working on an Odin flashable recovery from soft brick. I will also be posting things that I have figured out so far, and in the next day or so a full deodexed version of the stock firmware. Coming later will be a custom rom. If anyone in this thread has dev experience and has the 730M variant, PM me about this custom rom as I would like to make it compatible with both versions of the phone but will have to work out the differences between the two to make it fully compatible. New thread for the 730G - http://forum.xda-developers.com/showthread.php?p=47417608
TheGeekyNimrod said:
Here is a thread I started this morning about the SGH-730G (Tracfone, Net10, Straight Talk) variant of the Discover. I created this thread so there wouldn't be confusions due to the slight differences between the 730G and the 730M variants. Right now there is a root method listed, and I am working on an Odin flashable recovery from soft brick. I will also be posting things that I have figured out so far, and in the next day or so a full deodexed version of the stock firmware. Coming later will be a custom rom. If anyone in this thread has dev experience and has the 730M variant, PM me about this custom rom as I would like to make it compatible with both versions of the phone but will have to work out the differences between the two to make it fully compatible. New thread for the 730G - http://forum.xda-developers.com/showthread.php?p=47417608
Click to expand...
Click to collapse
I've added a link to your thread to the original post such that people don't get confused and/or break their phones. Thank you fore making the thread.
shifattk said:
I've added a link to your thread to the original post such that people don't get confused and/or break their phones. Thank you fore making the thread.
Click to expand...
Click to collapse
Word. I know some people were confused in another thread. Root methods are basically the same but there are structual differences between them when it comes to mounting points for restore and such. Thanks for addinthe link to the OP. I'll go back in a few and add a link here in my OP for the same purpose.
Does anyone know how to carrier unlock for this phone yet.
question?when i try to install CMW it keeps failing nand rite mode and restarting! any solution or different ay to try,still showing stock recovery but rooted!
Hello guys is there any way to unroot??? thanks
alexandros050 said:
Hello guys is there any way to unroot??? thanks
Click to expand...
Click to collapse
You can use unlockroot software to unroot.
I tested rooted and unrooted.
x1745 said:
You can use unlockroot software to unroot.
I tested rooted and unrooted.
Click to expand...
Click to collapse
Ok thank you very much for your reply
Take a look at This, I've created a flashable zip that both roots the phone and installs the overclock kernel found in this thread. Thought you might be interested
edit: I also just posted a flashable stock rom here. it's deodexed, rooted, and overclocked.
Restl3ss said:
Take a look at This, I've created a flashable zip that both roots the phone and installs the overclock kernel found in this thread. Thought you might be interested
edit: I also just posted a flashable stock rom here. it's deodexed, rooted, and overclocked.
Click to expand...
Click to collapse
I tried flashing your ROM, get error status 255, installation aborted...
shifattk said:
The Script it attached to this post.
Procedures (using ADB)
put boot.img on sdcard:
adb push boot.img /sdcard/boot.img
Then, from adbshell:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
then reboot device.
Click to expand...
Click to collapse
Phone wont boot past samsung logo after this. Followed your instructions exactly
atmu5fear said:
Phone wont boot past samsung logo after this. Followed your instructions exactly
Click to expand...
Click to collapse
Did you make a CWM backup before doing it? If you did, boot into CWM recovery and flash the recovery package.

[Q] Unlocking BL - need clarification

Hi,
I am going to unlock my Arc S BL. I read many here, but need some clarifications:
My goal is to have XUHD 5.0.1 with suggested kernel (Lupus). Right now I have XUHD 3 (with mod), phone is rooted (I did it somehow:laugh. It got slow and buggy after a while, so I need to refresh it totally.
THE PLAN:
1. Unlock BL using SE Bootloader Unlocking v1.6 by quangnhut123 (seems easier for a newbie than "sony" way, not mentioning the test point one).
2. Using the same tool flash LuPuS Kernel Stock.
Now to be confirmed: All I have to do is to enter IMEI and select file LuPuS_anzu_Stock-iCsv16-full.img. Done?
What would I get after that? Shell I turn on the phone as usual (and it is supposed to run as normal, maybe fresh)?
Should I remove my SD card while doing steps 1-2? Is the contentt of the SD card erased after the process?
Gaps - totally new to me - should I do something with them?
3. Flash the ROM. Well I did it earlies and it worked, so I believe when I will get confirmatoion of above I might succeed.
To be confirmed: to "make phone as new" - what pratition should I wipe? I am going to backup everything possible earlier.
I would like to add my own ringtone. How to do that? (I was told it can be done after installing ROM - via CWM - need suggestions...)
Do I miss something? Do I have to check anything before I start (dont want to finish with not working device...)
Any help would be VERY appreciated.
big thanks in advance.
tman_pl said:
1. Unlock BL using SE Bootloader Unlocking v1.6 by quangnhut123 (seems easier for a newbie than "sony" way, not mentioning the test point one).
Click to expand...
Click to collapse
That is the "sony" way but all the process is done with this app. You lose same features as with the "sony" way.
tman_pl said:
Now to be confirmed: All I have to do is to enter IMEI and select file LuPuS_anzu_Stock-iCsv16-full.img. Done?
Click to expand...
Click to collapse
Put phone into fastboot mode, enter IMEI, then get unlock code, then unlock BL, then select the file and flash the kernel.
tman_pl said:
What would I get after that? Shell I turn on the phone as usual (and it is supposed to run as normal, maybe fresh)?
Click to expand...
Click to collapse
You get unlocked bootloader, custom kernel installed. When you have installed the custom kernel, enter Recovery (press Volume Down button many times during kernel boot logo), wipe the necessary partitions (depends on the ROM) and install new ROM.
tman_pl said:
Should I remove my SD card while doing steps 1-2? Is the contentt of the SD card erased after the process?
Click to expand...
Click to collapse
Not necessary. No SD Data is touched during this process. Unlocking bootloader though does remove all data from your phone inside (not SD), so make backups if necessary.
tman_pl said:
Gaps - totally new to me - should I do something with them?
Click to expand...
Click to collapse
Gapps stand for Google Apps. They are only required, if you install non-stock based ROM (CyanogenMod aka CM or any other).
tman_pl said:
3. Flash the ROM. Well I did it earlies and it worked, so I believe when I will get confirmatoion of above I might succeed.
To be confirmed: to "make phone as new" - what pratition should I wipe? I am going to backup everything possible earlier.
Click to expand...
Click to collapse
For most ROMs, you need to wipe /data, /cache and /system. Non-stock based may require you to not wipe /system.
tman_pl said:
I would like to add my own ringtone. How to do that? (I was told it can be done after installing ROM - via CWM - need suggestions...)
Click to expand...
Click to collapse
If it is on your SD card, your phone can find it. Alternatively, you can put it to /system/media/audio/ringtones folder with any file explorer, that can edit system directory (I personally use ES File Explorer).
tman_pl said:
Do I miss something? Do I have to check anything before I start (dont want to finish with not working device...)[/B]
Click to expand...
Click to collapse
Seems fine for now, nothing that I can think of.
THANK YOU VERY MUCH, your help is very appreciated. All issues adressed perfectly:highfive:!
I am downloading the tools and backing up data (want to format as much as possible)..
Someguyfromhell said:
If it is on your SD card, your phone can find it. Alternatively, you can put it to /system/media/audio/ringtones folder with any file explorer, that can edit system directory (I personally use ES File Explorer).
Click to expand...
Click to collapse
The reason to put it to device memory instead of card one it that when phone is connected to PC in mass storage mode it switches the default ringtone (phone does not have acces to the card)
Well, I did try copy to devuce filesystem, but I get Read Only file system warning, no files copied. I used ES with root permission. I was told it can be done by flashing, but dont know how to do that..
BIG, BIG thanks for your help
tman_pl said:
The reason to put it to device memory instead of card one it that when phone is connected to PC in mass storage mode it switches the default ringtone (phone does not have acces to the card)
Well, I did try copy to devuce filesystem, but I get Read Only file system warning, no files copied. I used ES with root permission. I was told it can be done by flashing, but dont know how to do that..
BIG, BIG thanks for your help
Click to expand...
Click to collapse
Open ES File Explorer, press the Menu button, make sure Root Explorer is turned on, then click on Root Explorer, Mount R/W, make sure /system is set to RW.
SUPERB, thanks again. Working like a charm.
I backed up all I needed. I started SE Bootloader Unlockin Tool, but after I enter my IMEI and hit Get Unlock Code the text-area where the code should appear chnaged color to light-gray only, and nothing more.
I am running win764 if matters...
Should I proceed as told? (hit unlock BL even if Unlock code is not displayed?
I sould I get the code via http://unlockbootloader.sonymobile.com/, paste it and than proceed?
tman_pl said:
SUPERB, thanks again. Working like a charm.
I backed up all I needed. I started SE Bootloader Unlockin Tool, but after I enter my IMEI and hit Get Unlock Code the text-area where the code should appear chnaged color to light-gray only, and nothing more.
I am running win764 if matters...
Should I proceed as told? (hit unlock BL even if Unlock code is not displayed?
I sould I get the code via http://unlockbootloader.sonymobile.com/, paste it and than proceed?
Click to expand...
Click to collapse
Yes get the code from official website
Cheers,
AJ
yep, I got the code from website, But I woder wheter I should use SE BU to unlock if it doesnt get the code properly...?
Well... I will try... What I need is the flashing kernel button
All swept, but I used SEBU with the code I got from official site.
And it seems it all worked!
Just installed the rom and can see configuration screen.
BIG thanks to ALL
delete
well easy to do it

Explain like I'm a three year old, I beg of you.

I politely ask any person able to help to explain to me, like I am a three year old, exactly how to update a Samsung Glide from 4.0.4 to whatever newer version is able to work on the phone, that is rooted? AGAIN... I ask this politely.
Allmystical1 said:
I politely ask any person able to help to explain to me, like I am a three year old, exactly how to update a Samsung Glide from 4.0.4 to whatever newer version is able to work on the phone, that is rooted? AGAIN... I ask this politely.
Click to expand...
Click to collapse
No problem, we are all new at this once, right?
First Step: Downloads!
TWRP:
http://dualhoki.vim.hu/bubor/dev/twrp-i927/twrp-2.8.4-for_odin.tar.md5
ROM:
Here is a matter of preference. If you want the latest *working* version, you can upgrade to 5.0, but you lose the camera. I presume you want the camera to work, so I suggest Bubor's CM11 for KitKat. There are other good roms too, like PAC and SediRom, but we will start with Bubor's CM11.
http://dualhoki.vim.hu/bubor/dev/11.0/cm-11-20160126-UNOFFICIAL-i927.zip
http://dualhoki.vim.hu/bubor/dev/11.0/cm-11-20160126-UNOFFICIAL-i927.zip.md5sum
ODIN:
http://www.mediafire.com/download/7us5q44aab1xl9d/Odin304.zip
Second Step: Prepare.
I am presuming that you are using a Windows computer. If you are using a Linux computer, I can tell you what to do also, but these instructions are for Windows. I am also presuming that you have an external SD card in your phone, if you do not, go buy one and put it in your phone.
Unzip the Odin304.zip by right clicking on it and say unzip/extract, etc. If your Windows does not have this option, you need to download a program like winzip or 7zip so you can unzip this file. If you need those programs, they can be googled and downloaded.
Third step: Further preparation.
Turn on your phone and plug it into a usb cord and plug the usb cord into your computer. If you are using Windows, it will try to find drivers for the phone. It should be automatic and just work. If it does not, then you need the drivers, which are here:
http://www.mediafire.com/download/0up21ccc9gajwjv/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
*If you downloaded this file, just double click it like a program, it should open and install drivers for your phone. Do not do this unless your computer cannot find drivers for your phone!
Fourth step: Charge your phone.
Plug in your phone and FULLY charge it. ALL the way to 100% CHARGED. No exceptions. No shortcuts. Do it. Then UNPLUG YOUR PHONE AND TURN IT OFF.
Fifth step: Put TWRP on your phone.
a. Your phone should now be unplugged and off. Open the ODIN folder that you unzipped earlier and double click on ODIN to open the program.
b. Click on the PDA button ( you and I both know that your phone is not a PDA, this is not a typo ) and it will open a browser. Find the twrp-2.8.4-for_odin.tar.md5 file and select it. It should now fill in the blank line next to PDA with this info.
c. WHILE HOLDING THE UP VOLUME BUTTON ON YOUR PHONE, press and hold the power button. When you see "SAMSUNG" you can release the power button, but KEEP HOLDING THE UP BUTTON, untill you see a yellow triangle and warning notice. If you hold too long, that is okay as it will take you straight to the download mode with the green android that says "ODIN" at the top and "Downloading" in the middle. If you got stopped at the yellow warning/triangle, press up again to go to download mode.
d. Plug your phone into the usb, and the usb into your computer.
e. In the Odin program, press start.
You should now see a serries of verbage going by on the left, at the top a green bar may fill in, and hopefully, in the end it says "success" or "pass". Your phone should reboot all by itself. If ODIN says fail, ask for further instructions. If passed, close Odin.
Sixth step: Put your CM11 files on your phone.
Your phone should have rebooted and looks just like it did before, now powered on, and in your stock Ice Cream Sandwich firmware. As with any file transfer, plug your USB into the phone and computer. Drag the CM11 files to the phone. Anywhere will do, but if you have an external SD card in your phone, I recommend you put it there.
Seventh Step: Boot into TWRP.
a. Turn off your phone.
b. Unplug the USB.
c. HOLD THE DOWN VOLUME BUTTON and press the POWER BUTTON. When you see "Samsung" release the POWER BUTTON, but keep holding the VOLUME DOWN BUTTON. At the top of the screen, white letters should say something like "entering recovery".
d. When you see "Team Win Recovery Project" release the down volume button.
Eighth step: Make a backup!
a. Press "Backup" button on screen.
b. Check all checkboxes (system, cache, data, boot, Android Secure)
c. Press "Storage: sdcard (xxxx mb)" bar.
d. Select "External_sd" to choose to backup to your external sd card.
e. Slide the swipe bar to the right to backup. This will take a few minutes, with progress bar.
NOTE: if the screen dims, when you touch it, you will see a TWRP lock icon, swipe right to unlock it.
f. When backup is completed, it will say "reboot system", do not click that. Click the "home" icon in the lower left corner.
g. Click the "Wipe" button.
h. Swipe right to factory reset.
i. Click the "home" icon in the lower left corner.
j. Click the "install" button.
k. At the top, click on the "Storage: sdcard (xxxx mb)" bar.
l. Select "External_sd"
m. choose the cm-11-20160126-UNOFFICIAL-i927.zip
n. When that is done, click on the "reboot system" button.
The system will reboot. You should now see CM11's boot screen. The first boot takes a bit of time.
Ninth step: Thank Bubor.
a. Log into XDA.
b. Go to http://forum.xda-developers.com/captivate-glide/development/dev-cm-11-0-t2802184
c. Slap every thanks button that is for a post by Bubor untill it tells you that you cannot slap any more thanks buttons (that is only 8 thanks per day).
Tenth step: Enjoy your phone!
....I think you know how to do that.....
If you have ANY questions, please just post them here and we will see if we can answer them.
I am thanking you so very much! Also... I do apologize for such a time lapse in my reply. Life happened.
I followed the above procedure and have CM11 installed. But my problem is I can't use my SIM card anymore because it's like my phone doesn't see it at all. I checked my settings and saw that I no longer had an IMEI number. I used the restore feature and the stock ROM had an IMEI number. What should I do? I saw a few threads about using a program to rewrite the IMEI or others to copy the file containing the IMEI but I wasn't really sure what I should do or how to copy files to and from that partition from my computer. I should add that the phone is unlocked.
tr3sie7e said:
I followed the above procedure and have CM11 installed. But my problem is I can't use my SIM card anymore because it's like my phone doesn't see it at all. I checked my settings and saw that I no longer had an IMEI number. I used the restore feature and the stock ROM had an IMEI number. What should I do? I saw a few threads about using a program to rewrite the IMEI or others to copy the file containing the IMEI but I wasn't really sure what I should do or how to copy files to and from that partition from my computer. I should add that the phone is unlocked.
Click to expand...
Click to collapse
Great question, and an interesting problem!
First, I am really glad that you followed the instructions and made a backup! It is good to know that you can always go back to the way it was.
I recommend that you download another rom from the developer section here, such as Sedi-rom, omni-rom, etc., and try flashing that. If you flash one of those roms, does your IMEI stay for those roms?
Try this one: http://forum.xda-developers.com/showthread.php?t=2789727
You can do steps 7 through 10 with any of the roms in the developer thread. If this other rom works, you can use it, or download others and try them. If the SediRom does not work also, then we will need to sit down and figure this out.
I really appreciate the fact that you're here to help.
I downloaded and installed SediRom 2.1.2 and my IMEI still shows as "Unknown." However this time I should add there is a serial number, which I don't believe was present in CM11 or in the stock ROM, although I'm not sure if that's at all significant. I made an external backup of the efs file from the stock ROM, is there some way I could just reinstall CM11 and replace/overwrite the efs to give it an IMEI number? I'd really like to use CM11 if possible, I was enamored by how good it looked and how functional it was, especially since the last time I tried CM a long time ago I didn't have such a good opinion of it. Plus the bootloader is friggin sweet !
I recently got the phone unlocked off eBay, so I don't know its past history but I was able to access the network when I had the SIM card in prior to initially installing CM11 but not afterwards. I'm trying to use a T-Mobile SIM but like I said I was able to successfully access the network prior to installing CM11. But the IMEI doesn't show at all regardless if the SIM is in at all.
Is there some kind of different hardware/firmware like in a newer slightly different version of the phone that came out resulting in compatibility issues? I'm not the most experienced but I've dipped by toes in this before, so I would be willing to go the extra mile if it meant I could get CM11 to work, because honestly it looked like everything I could ever want from this phone with a good looking theme too...
Do you have a full backup of the efs partition?
If so it should be enough to restore it.
Sent from my LG-H815 using XDA Labs
xdajog said:
Do you have a full backup of the efs partition?
If so it should be enough to restore it.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes I believe so. I used the procedure from this thread to back it up. I tried copying the efs directly over using the built in file manager with root access, but when I try to copy the entire efs folder over I get a non-descriptive error "this operation has failed." I tried copying the nv_data.bin folder by itself to overwrite the one currently there (which copied successfully), then rebooted the phone but the IMEI still shows as "unknown." Do I need to copy the efs while the phone is in recovery mode or via PC or something because of file in-use errors or something else I don't know about?
tr3sie7e said:
Yes I believe so. I used the procedure from this thread to back it up. I tried copying the efs directly over using the built in file manager with root access, but when I try to copy the entire efs folder over I get a non-descriptive error "this operation has failed." I tried copying the nv_data.bin folder by itself to overwrite the one currently there (which copied successfully), then rebooted the phone but the IMEI still shows as "unknown." Do I need to copy the efs while the phone is in recovery mode or via PC or something because of file in-use errors or something else I don't know about?
Click to expand...
Click to collapse
Well restoring efs have to be done in recovery only! Do not try to do this while android is running!!
To be honest the absolute best way is having a dd partition dump of the whole partition. When you have followed the mentioned guide do you have used also dd like this?
dd if=/dev/block/mmcblk0p1 of=/storage/external_SD/efs.img
I don't know if copying the efs folder alone would work.. better is restoring the whole partition if possible. Do you have such kind of backup?
Sent from my LG-H815 using XDA Labs
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
azwindsor said:
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
Click to expand...
Click to collapse
try to rename to recovery.tar.md5
try older version, and flash the latest from recovery.
azwindsor said:
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
Click to expand...
Click to collapse
Redownload. Maybe the file you had downloaded gets corrupted or is incomplete ..
.
Sent from my LG-H815 using XDA Labs
bubor said:
try to rename to recovery.tar.md5
try older version, and flash the latest from recovery.
Click to expand...
Click to collapse
Many thanks bubor! Renaming worked like a charm.
FYI, I tried re-downloading it, but that didn't seem to work yesterday.
I really appreciate all of your work, everything is working great.
Thanks for the quick responses.
All the best!
So I'm really late here but the phone got thrown to the backburner and I forgot about it. Lol but anyways, I created the EFS backups using dd like it said, but I'm not sure how to restore them? Do I unpack them and then use ADB to move them there? I'm kind of confused. Also, for some reason going through the TWRP to the stock ROM doesn't let me root it, it crashes every time I get to that screen, don't know if that's important to the operation. Hope I can finally get this stupid thing working right with the custom ROM...
tr3sie7e said:
So I'm really late here but the phone got thrown to the backburner and I forgot about it. Lol but anyways, I created the EFS backups using dd like it said, but I'm not sure how to restore them? Do I unpack them and then use ADB to move them there? I'm kind of confused. Also, for some reason going through the TWRP to the stock ROM doesn't let me root it, it crashes every time I get to that screen, don't know if that's important to the operation. Hope I can finally get this stupid thing working right with the custom ROM...
Click to expand...
Click to collapse
Check my faq here:
http://forum.xda-developers.com/showthread.php?t=2789727&p=54075993
Scroll down to restore efs.
.
Okay so I used TWRP to do a factory restore, flashed SuperUser, then flashed CM11, went into TWRP and did the terminal commands you listed in the guide for backing up the EFS... to no avail. Would it be better to copy the EFS while I'm still on the rooted stock ROM using a terminal app? I don't understand what the problem is...
tr3sie7e said:
Okay so I used TWRP to do a factory restore, flashed SuperUser, then flashed CM11, went into TWRP and did the terminal commands you listed in the guide for backing up the EFS... to no avail. Would it be better to copy the EFS while I'm still on the rooted stock ROM using a terminal app? I don't understand what the problem is...
Click to expand...
Click to collapse
Please paste the output of the results. Doing this in twrp is the correct way.

How To Guide SM-F926B ONLY!! Android 12 update and ROOT GUIDE - BVA9 rooted firmware provided - if you missed the good news, camera works :)

Hi All!!
This thread will now contain pre rooted Odin files for F926B users to flash and update
Before you start, download "420rom_F926B_BVA9_Odin_EUY.zip" from HERE
THIS IS FOR F926B ONLY
The process requires knowledge of basic adb and YOU MUST HAVE ADB INSTALLED BEFORE TRYING THIS
This will no longer wipe data but it is advisable to backup first anyway - i wont be responsible for any data lost that could have been backed up
PROCESS to update from rooted a11 or a12
1 - Unzip the 4 odin files from the zip provided in the link above & connect phone to PC
2 - load ODIN on PC and disable AUTO Reboot - Next load BL.tar in BL, AP.tar in AP, Stock CP in CP and Stock HOMECSC in CSC
3 - Click start to flash the files - when completed, keeping phone connected to PC, press and hold power and volume down and as soon as the screen turns off, press and hold vol up and power UNTIL in TWRP
4 - Head to the TWRP mount menu disable MTP
5 - ONLY IF YOU DONT HAVE A MAGISK.ZIP ON INTERNAL STORAGE copy app-debug.zip to your adb folder and then open a command window and first confirm adb is working by typing adb devices you should see your device listed and "recovery" next to the device in command window - this means adb is working - type adb push app-debug.zip /sdcard this should send the app-debug.zip to internal storage (or sdcard if you prefer)
6 - go to the TWRP flash menu and you should see the app-debug.zip, flash it to root your A12 device - this needs to be done everytime TWRP is flashed in Odin it seems
7 - reboot to system from TWRP power menu
You will boot rooted, updated and with intact data if all the steps above are followed correctly
------------------------------------------------------------------------------------------------------------------
PROCESS IF COMING FROM STOCK A12
1 - Unzip the 4 odin files from the zip provided in the link above & connect phone to PC (please ensure dev settings are enabled and that you have unlocked bootloader and checked "Oem unlock" is faded out under dev settings)
2 - load ODIN on PC and disable AUTO Reboot - Next load BL.tar in BL, AP.tar in AP, Stock CP in CP and Stock HOMECSC in CSC
3 - Click start to flash the files - when completed, keeping phone connected to PC, press and hold power and volume down and as soon as the screen turns off, press and hold vol up and power UNTIL in TWRP
4 - Head to the TWRP wipe menu and format device (type yes and press enter) - then reboot TWRP
5 - when TWRP has rebooted, go to the mounts menu and disable MTP -> this will allow us to send app-debug.zip (magisk) to your sdcard
6 - copy app-debug.zip to your adb folder and then open a command window and first confirm adb is working by typing adb devices you should see your device listed and "recovery" next to the device in command window - this means adb is working
7 - type adb push app-debug.zip /sdcard this should send the app-debug.zip to internal storage (or sdcard if you prefer) - go to the TWRP flash menu and you should see this app-debug.zip, flash it to root your A12 device
8 - as stated previously, i have disabled encryption therefore we just need to boot STRAIGHT to SYSTEM from the TWRP POWER MENU
9 -When phone reboots, set up as normal and you should now see a magisk stub in the app drawer meaning you are rooted
PLEASE NOTE THAT THE MAGISK PATCHED AP FILE IS UPLOADING AND WILL BE AVAILABLE IN A FEW HOURS
Reuploading patched AP file to Mega and will be available shortly
G-drive too a dump on me last night - apologies for the delay
@ianmacd is working on his disabler soon so we will be able to simplify things a bit also - thanks for bearing with me!!
ok my teammate has built a tested and working AP file to use in the guide above - this will be up very shortly
mine was fine however my internet connection is not lol
Ok guys - sorry for the muck about!! the patched AP file is now live in the first post - therefore you can go ahead and root!
Follow the steps carefully, please also read and make sure you have everything prepared before you start
Had a couple of peeps join my telegram chat asking about OEM option being missing.
Please note that this guide only covers the WWE F926B at the moment (US models have a locked bootloader afaik)
Thanks a lot for your work, Just got my hands on with the device.
Is losing the camera option inevitable?
There is no way to keep it enabled?
JazonX said:
Thanks a lot for your work, Just got my hands on with the device.
Is losing the camera option inevitable?
There is no way to keep it enabled?
Click to expand...
Click to collapse
At the moment there is sadly no camera til the bootloader is relocked. Hopefully a fix is found soon
exocetdj said:
Reuploading patched AP file to Mega and will be available shortly
G-drive too a dump on me last night - apologies for the delay
@ianmacd is working on his disabler soon so we will be able to simplify things a bit also - thanks for bearing with me!!
Click to expand...
Click to collapse
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
白い熊 said:
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
Click to expand...
Click to collapse
Hi mate have you managed to access it yet? if not ill try sort links out
白い熊 said:
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
Click to expand...
Click to collapse
try this alternative link
If not ill ask my teammate to mirror to Mega
exocetdj said:
Hi mate have you managed to access it yet? if not ill try sort links out
Click to expand...
Click to collapse
Yeah, after an hour or so it let me in again, and didn’t fail this time. :O)
Killing the camera after unlocking the bootloader is a stupid and crappy move by Samsung.
I remember, oh so long ago, when Samsung actually supported us here on XDA, found quite a large number of things done by devs here suddenly appearing on their "next big thing", then they quietly withdrew their support and went over to the dark side of the Apple-verse.
ultramag69 said:
Killing the camera after unlocking the bootloader is a stupid and crappy move by Samsung.
I remember, oh so long ago, when Samsung actually supported us here on XDA, found quite a large number of things done by devs here suddenly appearing on their "next big thing", then they quietly withdrew their support and went over to the dark side of the Apple-verse.
Click to expand...
Click to collapse
They don't seem to care as much about the modding community nowadays it seems.
Iv had Sammy phones since s8 and been modding with roms since March last year and they've all been a ***** in some way to root
exocetdj said:
They don't seem to care as much about the modding community nowadays it seems.
Iv had Sammy phones since s8 and been modding with roms since March last year and they've all been a ***** in some way to root
Click to expand...
Click to collapse
See, now I'm starting to feel old.
Been here since S2.
Samsung actually had representatives on the forum. They actively helped with rooting and used features that were developed here on XDA, assuming with the dev's permission, in their latest phones (suffice to say most of the features we take for granted today were developed here).
Rooting was EASY. As simple as flashing CWM on to your phone. No worries about KNOX or losing any features. That came around the time of the Note 3 along with region locking.
ultramag69 said:
See, now I'm starting to feel old.
Been here since S2.
Samsung actually had representatives on the forum. They actively helped with rooting and used features that were developed here on XDA, assuming with the dev's permission, in their latest phones (suffice to say most of the features we take for granted today were developed here).
Rooting was EASY. As simple as flashing CWM on to your phone. No worries about KNOX or losing any features. That came around the time of the Note 3 along with region locking.
Click to expand...
Click to collapse
So from my understanding, Knox was actually designed for dual rom booting, as a way to keep the original firmware in tact and safe, but also be able to flash a custom rom for dual boot. But investors, carriers, and the like decided they weren't happy with that and saw that it could also be used to lock the device down to make everything more secure for their intents. After like 4 iterations where Samsung kept being pushed, it became what it is today.
I'm assuming they thought if they just impliment everything that a person would root for, that it would make people OK with it, but of course not the case. In the end, just like any other major corporation, they let money push them around
If we root, remove bloat, and then re-lock the bootloader, would the bloat still be gone? Knowing Sammy, they would prevent us from removing bloat.
I can handle holding out on flashing a sweet ROM if I can remove garbage like Bixby.
As soon as you flash any custom binary then your software is classed as custom and will not boot at all with a locked bootloader. It would soft brick requiring a stock odin flash to revive device most likely
dirtybudha said:
If we root, remove bloat, and then re-lock the bootloader, would the bloat still be gone? Knowing Sammy, they would prevent us from removing bloat.
I can handle holding out on flashing a sweet ROM if I can remove garbage like Bixby.
Click to expand...
Click to collapse
You can remove and/or disable bloat with adb commands for now. There is a thread about it somewhere in our forum
Samkey apparently now supports f926b but I'm getting unsupported firmware errors on AUG8 and AUHF. I really want to get rid of this three bloat

Categories

Resources