Related
How To Root All 2011 Xperia Devices (Unlocked Boot-loader)
Just thought I would tell you how to root your Xperia Play no matter what version of android your are on.
For this guide i will be using official firmware xx.xx.xx.62 which will be flashed via wotan.
You have many ways you can do this so i will give two.
Method 1 : Using a auto-root Kernel (doomlord, KeiranFTW)
After flashing your ROM.
Depending on your ROM, download a appopiate kernel with recovery and auto root. for this i will be using Doomlord's Advanced stock kernel.
Once downloaded extract to your fastboot folder (check my other guides for a small fastboot package)
Run fastboot.exe via cmd or use the run_me.bat file
Connect your phone to your computer while switched off and while the search (may be different for other devices) key is being pressed5. When Blue LED switches on type
Code:
fastboot flash boot FILENAME.img
where the file-name is the name of the downloaded file. e.g.
Code:
fastboot flash boot boot.img
6. type in the below command
Code:
fastboot reboot
7. your phone should reboot and you should now have superuser and SU.
Method 2 : Using a Root Zip File
After flashing your ROM.
1. Firstly download this file Bootable ClockworkMod Recovery
2. Next download this file and copy it to your sdcard of your phone.
3. Using the fastboot package downloaded from a previous tutorial run the run_me.bat file
4. Put phone in fastboot mode.
3. Type in the following command
Code:
fastboot boot recovery.img
5. Then "install zip from sd card" on the phone
6. After installation is completed press "reboot phone"
7. Your phone should reboot and have Superuser and SU.
Enjoy your rooted phone,
-Fma965
[no longer linking tutorials to my site as currently messing around with my site so links may break, to prevent this i will post them here since i found a html to vbcode converter aswell ]
Thanks my Phone is roofde.
---------- Post added at 08:55 PM ---------- Previous post was at 08:54 PM ----------
Rooted
sanderpunto said:
Thanks my Phone is roofde.
---------- Post added at 08:55 PM ---------- Previous post was at 08:54 PM ----------
Rooted
Click to expand...
Click to collapse
Thanks again , Glad it worked as usual
oow
Man, im not gay. But i love u. the man of a perfect tutorial
Hi, tnx for the tutorial, but 3 questions :
1. Will it work for .69 (or above)?
2. You wrote "after flashing your ROM", do I have to flash ROM? And how do I do that?
3. You wrote "... from previous tutorial", which tutorial?
YechiamTK said:
Hi, tnx for the tutorial, but 3 questions :
1. Will it work for .69 (or above)?
2. You wrote "after flashing your ROM", do I have to flash ROM? And how do I do that?
3. You wrote "... from previous tutorial", which tutorial?
Click to expand...
Click to collapse
Good questions.
Putting a custom ROM is after rooting it right? So why would i want to flash my ROM?
I am getting Error: cannot load recovery.img. i guess this has something to do with not having flashed my rom?
YechiamTK said:
Hi, tnx for the tutorial, but 3 questions :
1. Will it work for .69 (or above)?
2. You wrote "after flashing your ROM", do I have to flash ROM? And how do I do that?
3. You wrote "... from previous tutorial", which tutorial?
Click to expand...
Click to collapse
1. Yes but you will need a unlocked bootloader (information may be out of date as no longer own this phone)
2. No
3. http://cyanlabs.net/Thread-Unlock-Xperia-Play-Boot-Loader
Paynemaster said:
Good questions.
Putting a custom ROM is after rooting it right? So why would i want to flash my ROM?
I am getting Error: cannot load recovery.img. i guess this has something to do with not having flashed my rom?
Click to expand...
Click to collapse
1. you don't need root to install a new ROM just need recovery
2. Sounds like you don't have a unlocked bootloader.
2. Sounds like you don't have a unlocked bootloader.
Click to expand...
Click to collapse
well i think i do got it unlocked i followed all steps with the imei number. Not sure if it worked then. how can i check if it works?
on the other hand i also have superuser app on my android phone now. But that app is just empty
Paynemaster said:
well i think i do got it unlocked i followed all steps with the imei number. Not sure if it worked then. how can i check if it works?
on the other hand i also have superuser app on my android phone now. But that app is just empty
Click to expand...
Click to collapse
to be fair mate you better off asking for help in QnA as my information will be outdated now, since i no longer own the xperia play or the g2 but own a htc one m8.
fma965 said:
to be fair mate you better off asking for help in QnA as my information will be outdated now, since i no longer own the xperia play or the g2 but own a htc one m8.
Click to expand...
Click to collapse
Yeah already working on a thread thanks for the reply. and keep up the good work
tomorrow i will be receiving my Galaxy S4 in the mail, and basically i just want to make sure i will be rooting this phone with the most recent and preferred method.
i found this guide from 2 different sticky threads "[HOW-TO] The ULTIMATE All-In-One Guide - I337M & MDL - MF3 - MK2" and "Frequently Asked Questions"
http://forum.xda-developers.com/showthread.php?t=2297900
but i started to see thing different than what i'm used to on the GS3:
(1) "This will not work on Build Number I337UCUAMF3"
is this comparable to the bootloader on the GS3? kinda like how there's a different guide to root a GS3 on the MJB bootloader.
(1b) what version will come out of the box?
should i root it before even putting my SIM card in it so it doesn't have a chance to auto-update?
(2) CASUAL
it sounds like this is an all-in-one, do-it-all Windows application? so i won't need the use of Odin to flash any files?
(3) what's the preferred custom recovery?
i've been using CWM for so many years now, it's just my go-to custom recovery.
SOLVED, see my last post.
mrhomiec said:
tomorrow i will be receiving my Galaxy S4 in the mail, and basically i just want to make sure i will be rooting this phone with the most recent and preferred method.
i found this guide from 2 different sticky threads "[HOW-TO] The ULTIMATE All-In-One Guide - I337M & MDL - MF3 - MK2" and "Frequently Asked Questions"
http://forum.xda-developers.com/showthread.php?t=2297900
but i started to see thing different than what i'm used to on the GS3:
(1) "This will not work on Build Number I337UCUAMF3"
is this comparable to the bootloader on the GS3? kinda like how there's a different guide to root a GS3 on the MJB bootloader.
(1b) what version will come out of the box?
should i root it before even putting my SIM card in it so it doesn't have a chance to auto-update?
(2) CASUAL
it sounds like this is an all-in-one, do-it-all Windows application? so i won't need the use of Odin to flash any files?
(3) what's the preferred custom recovery?
i've been using CWM for so many years now, it's just my go-to custom recovery.
Click to expand...
Click to collapse
Chances are you'll get an S4 with a newer firmware. This means you won't be able to use TWRP or CWM, and you can't run AOSP ROMs. You can still root and flash other Touchwiz ROMs.
1) Yes, that's exactly what it is in fact. Bootloaders MF3 and above do not support the only exploit we have to install AOSP ROMs.
1b) Like i said, probably a newer one. Check on the outside of the box and it will have a label somewhere about the software version. If it's not MDB or MDL then you can't use the exploit to get an AOSP ROM.
2) Yes, it is an AIO Windows app, but it won't work unless you get one on MDL or MDB again.
3) If you get the newer firmware, Safestrap is the only recovery, and Touchwiz ROMs are all that's compatible
If you want a better explanation of anything, PM me and I'll be glad to respond as soon as I finish the essay i should be typing at the moment.
so in short, MDB/MDL = awesome.
i really hope i get one of these then. i always flash CM on whatever phone i use.
if i do receive a phone that's MDB/MDL, i should NOT insert my SIM card, and NOT connect to wifi then? that way i can root first?
mrhomiec said:
so in short, MDB/MDL = awesome.
i really hope i get one of these then. i always flash CM on whatever phone i use.
if i do receive a phone that's MDB/MDL, i should NOT insert my SIM card, and NOT connect to wifi then? that way i can root first?
Click to expand...
Click to collapse
Exactly, do not let it connect. Just use CASUAL and then either use your root to disable the OTA updater or go straight to a ROM. Then just remember that if you ever have issues and need to flash stock firmware only flash the same and never a newer one.
aw man. just got the phone in, and it's already been updated.
came in on 4.4.2, I337UCUFNB1
found these threads:
http://forum.xda-developers.com/showthread.php?p=52167774
http://forum.xda-developers.com/showthread.php?t=2663545 (edit, upon more searching, this method seems the most mentioned/preferred)
and i'm wondering if i should even "root" this phone anymore. i feel like if/when a real root method comes out, i can root it then?
i guess the benefit of rooting now, would be to freeze/uninstall Samsung apps. also, would it be any easier to real root after sorta rooting?
edit, some more searching around, rooting right now (and with Safestrap Recovery installed) has a whole bunch of scenarios to be aware of. this is kinda overwhelming coming from the GS3 and Nexus phones/tablets.
edit, what are ROM slots? this sounds like dual-boots to me.
and also, since my phone came with NB1, what is the proper terminology for this situation? because i'm reading references like "NB1 users who took the OTA" and "NB1 users who started out there".
another edit! so i think i'm going to just root, and stop there, is that possible? or do i have to go one step further and install Safestrap Recovery?
i tried to follow the guide above (2nd link), and in Odin i got a FAIL message when i loaded the *.pit file to the PIT slot, and the *.md5 file to the AP slot.
mrhomiec said:
aw man. just got the phone in, and it's already been updated.
came in on 4.4.2, I337UCUFNB1
found these threads:
http://forum.xda-developers.com/showthread.php?p=52167774
http://forum.xda-developers.com/showthread.php?t=2663545 (edit, upon more searching, this method seems the most mentioned/preferred)
and i'm wondering if i should even "root" this phone anymore. i feel like if/when a real root method comes out, i can root it then?
i guess the benefit of rooting now, would be to freeze/uninstall Samsung apps. also, would it be any easier to real root after sorta rooting?
edit, some more searching around, rooting right now (and with Safestrap Recovery installed) has a whole bunch of scenarios to be aware of. this is kinda overwhelming coming from the GS3 and Nexus phones/tablets.
edit, what are ROM slots? this sounds like dual-boots to me.
and also, since my phone came with NB1, what is the proper terminology for this situation? because i'm reading references like "NB1 users who took the OTA" and "NB1 users who started out there".
another edit! so i think i'm going to just root, and stop there, is that possible? or do i have to go one step further and install Safestrap Recovery?
i tried to follow the guide above (2nd link), and in Odin i got a FAIL message when i loaded the *.pit file to the PIT slot, and the *.md5 file to the AP slot.
Click to expand...
Click to collapse
To root, you'll need to downgrade to mk2 with Odin. See the second post in this
http://forum.xda-developers.com/showthread.php?p=50667360
Then root using saferoot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
To root, you'll need to downgrade to mk2 with Odin. See the second post in this
http://forum.xda-developers.com/showthread.php?p=50667360
Then root using saferoot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
i tried following that guide, and i mentioned i got a FAIL message. i'm trying the other guide i linked to see if that method works.
mrhomiec said:
i tried following that guide, and i mentioned i got a FAIL message. i'm trying the other guide i linked to see if that method works.
Click to expand...
Click to collapse
Sorry man,I have you the wrong link. Use the all in one tar file from here http://forum.xda-developers.com/showthread.php?p=49687770
Sent from my Nexus 5 using XDA Free mobile app
mrhomiec said:
i tried following that guide, and i mentioned i got a FAIL message. i'm trying the other guide i linked to see if that method works.
Click to expand...
Click to collapse
The way most people follow on that thread is
1. Flash full NB1 post #2
2. Downgrade to MK2 post # 1
3. Root with safe root
4. Fix wife
5. Install safe strap
6 flash Tw rom of your preference.
7. Flash kernel if needed
8. Flash deadly venom magic tool.
9. Flash super su update.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
netomel said:
6 flash Tw rom of your preference.
7. Flash kernel if needed
8. Flash deadly venom magic tool.
9. Flash super su update.
Click to expand...
Click to collapse
flashing DVMT is optional. any modifications to the kernel will void his warranty (Knox 0x1). i'd advise looking into PurifieD or any 'stock' variant rom that does not require a custom kernel to be flashed, at least until your year of warranty goes by. Any post saying 'flashing period will void your warranty' is incorrect. On PurifieD with knox 0x0.
Rhymey said:
flashing DVMT is optional. any modifications to the kernel will void his warranty (Knox 0x1). i'd advise looking into PurifieD or any 'stock' variant rom that does not require a custom kernel to be flashed, at least until your year of warranty goes by. Any post saying 'flashing period will void your warranty' is incorrect. On PurifieD with knox 0x0.
Click to expand...
Click to collapse
We can't flash custom kernels on kit kat stock anyway.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
---------- Post added at 01:22 AM ---------- Previous post was at 01:20 AM ----------
netomel said:
We can't flash custom kernels on kit kat stock anyway. I flashed deadly venom and knox still intouched.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
i am totally lost right now. i finally got this guide to work:
http://forum.xda-developers.com/showthread.php?t=2663545
(i was being dumb, and i forgot to put the phone into Download Mode for Odin)
now, i'm having a problem with the last step...
1. Download all three files above
2. Open ODIN3v3.09
3. Load both Pit and AP together to corerct slot ( Pit >>PIT SLOT.....AP>>PDA SLOT ) and hit start.....
5. When is done....reboot to stock recovery and choose Full Wipe/Factory Reset.
6. Re-Root using Saferoot Method
7. Re-install Safestrap-v3.71
8. Try restoring your back up from safestrap recovery....CONFIRMED WORK...
9. Special Thanks to @Michael3214 @rebel1699 @Maribou @dolph8886 @Surge1223 @jeboo for his bypasslkm exploit and others that help to get WiFi Fixed....
Click to expand...
Click to collapse
Flash in Safe Strap then reboot open universal init.d toggle on then press nb1wififix then press the play icon on the top right grant su. After that you'll have wifi on boot.
https://mega.co.nz/#!dct3ALRT!e81l_V...LaYu_yKvCYeHhg
Click to expand...
Click to collapse
Code:
adb push bypasslkm /data/local/tmp
cd /data/local/tmp
chmod 755 bypasslkm
./bypasslkm
i cannot get wifi to work on the phone, and also, LTE/data is nowhere to be seen as well, and i'm hoping if i get the wifi fixed, it'll fix the data part too. i tried to flash the bypasslkm.zip via Safestrap Recovery, and it said it was successfully flashed, but still no wifi.
OR, i'm not sure if i did this all backwards. i received the phone today, and instead of putting my SIM card in right away, i booted up the phone, didn't connect to wifi, and attempted this whole rooting process.
then, i can't apply the update.zip for some reason with these instructions...
1. U need Samsung USB driver install to your PC ......Install SAMSUNG KIES and plug your phone, it will install latest driver for your phone....
2. Make sure u unable USB debugging mode on ur phone.....go to menu>settings>more> it should be on top of about device
( Developer options ) but if u dont have it go to about device and click build number 5 time....so that will unable developer options and CHECK USB DEBUGGING.
3. Make sure u have latest ADB ( Android Debugging Bridge ) version 1.0.31.... ANDROID SDK
4. IF you like to update to NB1 coming from MK2 ....Reboot to recovery>>>Apply Update From ADB....( MAKE SURE U DOWNLOAD update.zip AND PLACE IT INSIDE YOUR SD CARD)
5. Go to your PC >>> ADB folder >>> Shift+Right Click >>> Open Command Window Here
Click to expand...
Click to collapse
Code:
adb devices
adb sideload update.zip
i get this error...
* cannot read 'update.zip' *
mrhomiec said:
i am totally lost right now. i finally got this guide to work:
http://forum.xda-developers.com/showthread.php?t=2663545
(i was being dumb, and i forgot to put the phone into Download Mode for Odin)
Click to expand...
Click to collapse
Hi there! If you have safestrap installed and you still have root on whatever you're currently on, please update to 3.72 (if you haven't already) found here (click), and flash the stock rooted NC1 100% rom via Safestrap over your stock slot found here. This [should] fix your issues 100%. If not, scroll down to where it has the NC1 modem and flash that too.
Rhymey said:
Hi there! If you have safestrap installed and you still have root on whatever you're currently on, please update to 3.72 (if you haven't already) found here (click), and flash the stock rooted NC1 100% rom via Safestrap over your stock slot found here. This [should] fix your issues 100%. If not, scroll down to where it has the NC1 modem and flash that too.
Click to expand...
Click to collapse
i am on Safestrap Recovery 3.72, and i'm downloading that 100% ROM right now.
so i don't need to worry about the "update.zip" or the "bypasslkm.zip" files anymore?
just flash this ROM via Safestrap Recovery and i'm good to go?
back to my original post then, so i'm used to using CWM as a custom recovery, do i follow the usual steps with Safestrap?
* wipe data/factory reset
* wipe cache
* wipe dalvik cache
* flash ROM
* reboot
mrhomiec said:
i am on Safestrap Recovery 3.72, and i'm downloading that 100% ROM right now.
so i don't need to worry about the "update.zip" or the "bypasslkm.zip" files anymore?
just flash this ROM via Safestrap Recovery and i'm good to go?
back to my original post then, so i'm used to using CWM as a custom recovery, do i follow the usual steps with Safestrap?
* wipe data/factory reset
* wipe cache
* wipe dalvik cache
* flash ROM
* reboot
Click to expand...
Click to collapse
Yup, you got it. Go into advanced wipe on Safestrap and tick all of those. I never bothered with either of those zips. The only thing you might need to do is reflash SuperSU, but I never had an issue using the stock rom, just custom ones. SuperSU DL here.
Rhymey said:
Yup, you got it. Go into advanced wipe on Safestrap and tick all of those. I never bothered with either of those zips. The only thing you might need to do is reflash SuperSU, but I never had an issue using the stock rom, just custom ones. SuperSU DL here.
Click to expand...
Click to collapse
i found a link somewhere (and i forgot where no with how many tabs i had open originally), for a version of "UPDATE-SuperSU-v1.93.zip", but i downloaded the v1.89 from your link anyways (just in case).
the 100% ROM is still downloading, and i noticed something, you said to flash the NC1 modem if i continued to have problems, but i didn't see a mention of that in the link you provided. there's a kernel link if that's what you meant.
mrhomiec said:
i found a link somewhere (and i forgot where no with how many tabs i had open originally), for a version of "UPDATE-SuperSU-v1.93.zip", but i downloaded the v1.89 from your link anyways (just in case).
the 100% ROM is still downloading, and i noticed something, you said to flash the NC1 modem if i continued to have problems, but i didn't see a mention of that in the link you provided. there's a kernel link if that's what you meant.
Click to expand...
Click to collapse
Oh, guh. You're gonna need that kernel too. It's samsung signed so no voiding there. Modem here, just in case.
wipe everything except ext sd > flash rom > download mode, flash kernel in AP slot > boot, see if wifi works. If not, go flash the modem.
Rhymey said:
Oh, guh. You're gonna need that kernel too. It's samsung signed so no voiding there. Modem here, just in case.
wipe everything except ext sd > flash rom > download mode, flash kernel in AP slot > boot, see if wifi works. If not, go flash the modem.
Click to expand...
Click to collapse
looks like i'm good to go! thank you! :highfive:
i am on 4.4.2, baseband NC1, build NC1, LTE works, wifi works.
only took me 6 hours. :victory:
mrhomiec said:
looks like i'm good to go! thank you! :highfive:
i am on 4.4.2, baseband NC1, build NC1, LTE works, wifi works.
only took me 6 hours. :victory:
Click to expand...
Click to collapse
good to hear! if you have any issues with root just reflash SuperSU in safestrap. you can also jump around on TouchWiz roms now if you want to, but don't let any of them touch your kernel. And if you do, you'll need to flash an AT&T wifi module found here to get wifi working, and a build.prop to get LTE working found here. Have fun!
i think i'ma stay on this 100% ROM. i don't want to screw anything up. everything about rooting this phone is wayyyy out of my comfort zone. all the years of rooting i've done up until now was pretty much the same steps on different devices.
with that, i figure my last post should summarize this adventure.
basically, if you're in the same situation as me, getting a brand new Galaxy S4, automatically updated to 4.4.2 (NB1), here is what i went through. please see the original threads for all the download links.
NB1►DOWNGRADE★UPDATE◄MK2 ★ NB1 FULL ODIN ★ Apr.24.2014 said:
http://forum.xda-developers.com/showthread.php?t=2663545
1. Download all three files above
2. Open ODIN3v3.09
2b. put phone into Download Mode (from a shut down state, hold the Volume Down + Home Button + Power Button to start up)
3. Load both Pit and AP together to corerct slot ( Pit >>PIT SLOT.....AP>>PDA SLOT ) and hit start.....
4. (i don't know where step 4 is)
5. When is done....reboot to stock recovery and choose Full Wipe/Factory Reset.
5b. phone may freeze at the ATT screen, i left it alone for a good few minutes. then i took the chance to power down via holding Power Button, then putting the phone into stock recovery (hold the Volume Up + Home Button + Power Button).
6. Re-Root using Saferoot Method (not really re-rooting since this is a new phone, see below)
7. Re-install Safestrap-v3.71 (and not really re-installing either, also see below)
8. Try restoring your back up from safestrap recovery....CONFIRMED WORK...
8b. i skipped step 8.
9. Special Thanks to @Michael3214 @rebel1699 @Maribou @dolph8886 @Surge1223 @jeboo for his bypasslkm exploit and others that help to get WiFi Fixed....
9b. i skipped step 9 too.
10. download custom ROM, a kernel, and follow directions here:
http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3
10b. and if needed, download modem here:
http://forum.xda-developers.com/showpost.php?p=52167761&postcount=2
11. and DONE, you should be on 4.4.2 again, but this time on NC1.
Click to expand...
Click to collapse
ROOT Saferoot: Root for VRUEMJ7 said:
http://forum.xda-developers.com/showthread.php?t=2565758
Step 1 - setting up the USB drivers
Before you try using this rooting program, you'll need to have the USB drivers installed for your phone.
The easiest way to do this is to install Samsung Kies (Kies 3, fyi). If Kies sees your phone, you're OK for the drivers.
If you don't have the drivers working, the root installer will hang at "waiting for device..."
Step 2 - Enable USB Debugging
The second thing you must do is to enable USB debugging on your phone. Go to "Settings", "More...", then "Developer Options".
If "Developer Options" doesn't appear, then you'll need to enable it - go to "Settings", "More", "About Phone". Scroll down so the "Build Number" is visible, then tap on that several times until developer mode is enabled.
In Developer Options, make sure "USB Debugging" is checkmarked.
Step 3 - Enable USB ADB Access
Make sure that your computer is allowed to use USB debugging on your phone. To do this, unplug your phone (from the phone end, not the computer end) and unlock it. Then, plug in the USB cable back into the phone.
If you see an "Alllow USB debugging?" window pop up, tap on the "Always allow from this computer" to check it, then tap OK.
If you don't see that popup, it's OK, you should be OK to proceed.
That's it for the phone.
Step 4 - Unzip the saferoot.zip
Then you need to unpack the attached ZIP file somewhere onto your PC.
You should have the following when done:
- a file called "install.bat"
- a file called "install.sh"
- a folder called "files"
Step 5 - Root your phone
Double click on the "install.bat" to run the root. It will root and reboot your phone. Once that's done, you're rooted!
The first thing that the install script will ask you is whether or not to install Busybox. Busybox is a program that provides a fairly extensive set of Linux shell utilities that a Unix user would expect to see. If you're not going to be using the shell (terminal emulator or adb shell) then you may not want to install Busybox. You may, however, find that some root-required utilities assume that Busybox is installed.
If SuperSU asks you to update the su binary, choose the "Normal" method.
If SuperSU asks you about disabling Knox, allow it.
This exploit will NOT set the Knox Warranty Void flag. It will set the "Custom" flag, but that's nothing to worry about.
While you're running this, you'll need to keep the phone awake and watch both the computer running the rooting script and your phone.
You shouldn't unplug the phone unless you're prompted by the rooting script. Leave it connected until it's done.
Click to expand...
Click to collapse
RECOVERY LOCKED Safestrap Recovery v3.71/v3.72 2014-04-02 KK Beta said:
http://forum.xda-developers.com/showthread.php?t=2448925
1. Requirement: Root
2. Requirement: Allow APK install from Unknown Sources
3. Download the Safestrap APK
4. Find the APK using a Filemanager tool and open it on your device, then click "Install".
5. (If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this
message.)
6. Once installed, open up the Safestrap application as you would any other app.
7. Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
8. Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
9. From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap
10. Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
(this part was pretty straight forward)
Click to expand...
Click to collapse
Hey all. So I'm attempting to flash "JellyBeans" ROM on my Note 3 N900V. These are the steps I have followed:
1st of all I am rooted.
And I am using Safestrap.
1. Connect your device to your PC via USB cable.
2. Copy the Custom ROM .zip file from your Desktop over to the root of your SD card.
3. Once the .zip file has been copied, disconnect your device from your PC.
4. Turn OFF your device.
5. Turn it back on by holding down Volume Up, Home, and Power buttons together.
6. Your device should reboot into recovery mode.
In the recovery mode, the Volume buttons are used for navigation and the Power button to make a selection.
7. Select Backup and Restore.
8. Select Backup.
9. Hit Yes when prompted and let it backup your device.
10. Once done, head back to the main menu by selecting Back.
11. Select Wipe data/factory reset.
12. Hit Yes when prompted and let it wipe off all the data on your device.
13. Once done, head back to the main menu by selecting Back.
14. Select install zip from sdcard followed by choose zip from sdcard.
15. Choose the Custom ROM .zip file you copied earlier to be flashed on your device.
16. Select Yes when prompted and it should begin flashing the ROM on your device.
17. When the ROM has been flashed, reboot your device by selecting reboot system now.
Once I reboot its starts up "Samsung Galaxy Note 3" and then the screen just goes black and my notification light starts pulsing blue. But nothing happens. I cant turn the phone off or anything. I have to pull the battery out to reset.
Any idea's?
If you're on a retail device, you need to Odin back to stock and root again. Install safestrap. Then have fun being a crack flasher
eh?
bmwh0r3 said:
If you're on a retail device, you need to Odin back to stock and root again. Install safestrap. Then have fun being a crack flasher
Click to expand...
Click to collapse
Ok, I just recovered from safestrap back to my stock ROM. Im back at square 1. But why would I need to run odin back to stock. And then wth is a "crack flasher"?
OK you're using safestrap? Didn't read that. My bad. Are you on mje jb trying to update to the nc2/nc4 KitKat?
bmwh0r3 said:
OK you're using safestrap? Didn't read that. My bad. Are you on mje jb trying to update to the nc2/nc4 KitKat?
Click to expand...
Click to collapse
I'm running Stock atm. Trying to install JB. Everytime I have tried to install a custom ROM on this damn phone I get the same result. I had no issues with my HTC One.
Stock can be jellybean or KitKat. If on KitKat, you can't flash a jb rom
/facepalm
bmwh0r3 said:
Stock can be jellybean or KitKat. If on KitKat, you can't flash a jb rom
Click to expand...
Click to collapse
haha, my bad. Yea im on kitkat. I didnt think it mattered seeing as its a custom rom. Do you have a ROM you would recommend?
running 4.4.2 currently.
Biggins for great theming and a few s5 ported features or delta for stock nc4 themed beautifully. Alliance is great too. Hyperdrive was good. And eclipse is highly modified touchwiz to have aosp features. Here's where the term crack flasher comes in... Flash one and try it. Then try the next. See which suits ya man.
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
And please make sure you Odin the nc2/nc4 kernel recommended by all nc4 Roms. In other words... Follow the directions completely.
bmwh0r3 said:
Biggins for great theming and a few s5 ported features or delta for stock nc4 themed beautifully. Alliance is great too. Hyperdrive was good. And eclipse is highly modified touchwiz to have aosp features. Here's where the term crack flasher comes in... Flash one and try it. Then try the next. See which suits ya man.
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
And please make sure you Odin the nc2/nc4 kernel recommended by all nc4 Roms. In other words... Follow the directions completely.
Click to expand...
Click to collapse
Yea I read about the nc4 kernal somwhere else. I just didnt try it. Guess I forgot. I'll try flashing again tomorrow. Thx for your time.
Its all good man. Glad to help. XDA members are great here.
THIS IS FOR DEVELOPER EDITION NOTE 4 ONLY. RETAIL OWNERS DO NOT TRY THIS, IT WILL BRICK YOUR PHONE!!!!
**UPDATED 2/14/2015
MAKE SURE REACTIVATION LOCK IS NOT, I SAY AGAIN, IS NOT SELECTED IN YOUR SECURITY SETTINGS (MENU>SYSTEM SETTINGS>SECURITY If your REACTIVATION LOCK is selected you will lock yourself out of TWRP and root while doing the process below.
To get a custom recovery (TWRP) and obtain root follow these steps:
1. Download USB drivers from Samsung: http://www.samsung.com/us/support/downloads and install
2. Using ODIN V 3.10.6 : download here: http://odindownload.com/download/Odin3_v3.10.6.zip , power off phone and then boot into download mode (volumn down plus menu)
3. Connect phone to computer using stock USB cable
4. Make sure ODIN recognizes your phone, this could take a few second
5. In "Options" box make sure "Auto Reboot" and "F.Reset Time" are checked
6. In ODIN, Check "AP" box. Click on the long box to the right and locate where you have the TWRP.tar file saved, highlight the file and click open
7. Click "Start" to flash the latest Verizon version of openrecovery-twrp-located here:http://www.techerrata.com/browse/twrp2/trltevzw
8. Do not interrupt ODIN or disconnect your phone. Wait until you get a green "PASS" indicator on the status bar
9. Unplug phone and enjoy
This gives a fully functional custom TWRP recovery. Now do a backup in TWRP. This gives you a stock backup with no root. Now go to step 10 to obtain root.
10. Using TWRP, flash the the current SuperSU .zip file that has been saved to your internal or external sdcard found here http://download.chainfire.eu/supersu. Or, download the latest SuperUser app from the Play Store and install. Some users have had better results just downloading SuperSU from the Play Store and installing.
You should now have a fully rooted, custom TWRP recovery, SuperSU Developer Edition Note 4.
11. Optional , but recommended: Now, do another backup. You will have a stock backup with root (you can never have to many backups at this point in the Note 4 development).
12. One last step, it's optional, but highly recommended. If you ever lock your bootloader you'll need a copy of your aboot to recover and unlock the bootloader. This is phone specific so it won't work on your buddy's phone. Backup your aboot partition using radionerd's method posted here: http://forum.xda-developers.com/not...veloper-edition-verizon-t2881708/post57080306 (updated)
Has this been verified by anyone else
Sent from my SM-N910V using XDA Free mobile app
shug2oo6 said:
Has this been verified by anyone else
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Absolutely, by at least a half-dozen.
jpcalhoun said:
Absolutely, by at least a half-dozen.
Click to expand...
Click to collapse
On Non Developer Edition Note 4's?
Krustys_ said:
On Non Developer Edition Note 4's?
Click to expand...
Click to collapse
No, sorry not on Retail version of Note 4. Only for Developer Edition on Verizon.
Any takers on trying this ?
usmc2k said:
Any takers on trying this ?
Click to expand...
Click to collapse
It only works on DEVELOPERS EDITION bought straight from Samsung......DO NOT use on regular retail version.
Sent from my SCH-I605 / Galaxy Note 2 / JB 4.3 / Unlocked, Rooted, ROMed and AGNi-fied !!... using Tapatalk v 2.4.13
It's probably a good idea to state in the title that its for the Dev Edition, I'm sure some new folks might not read everything and try it on their retail edition :good:
Confirmed on my brand new Note 4 DE
????? Your retail or Dev?
TPR300C said:
It's probably a good idea to state in the title that its for the Dev Edition, I'm sure some new folks might not read everything and try it on their retail edition :good:
Click to expand...
Click to collapse
Good point. Thanks, I changed the OP.
I don't recall seeing any developer edition device having their own section. It's always been devs specifying devices in the op
I've updated the thread title to state *DEV ONLY* for you, OP. (Hope you don't mind. ) Just don't want anything bad happen to these precious devices.
On the other subject (dev only section), we'll see what we can come up with. Thank you for the patience, peeps. :highfive:
One way to do it!!!
jpcalhoun said:
THIS IS FOR DEVELOPER EDITION NOTE 4 ONLY. RETAIL OWNERS DO NOT TRY THIS, IT WILL BRICK YOUR PHONE!!!!
To get a custom recovery (TWRP) and obtain root follow these steps (we know that the .tar file you flash in ODIN is a T-Mobile file, but it works):
1. Download USB drivers from Samsung: http://www.samsung.com/us/support/ow...SM-N910VMKEVZW
2. Using ODIN V 3.09 (link courtesy @GirLuvsDroid): http://www.mediafire.com/download/vw...din3_v3.09.zip
ODIN setting AP, Phone in Download mode
3. Install openrecovery-twrp-2.8.1.1-trltetmo.img.tar (Thank you @fz798): http://www.techerrata.com/browse/twrp2/trltetmo
This gives a fully functional custom TWRP recovery. Now do a backup in TWRP. This gives you a stock backup with no root. Now go to step 4 to obtain root.
4. Using TWRP in recovery, install SU.zip(2.16) (Thank you @mrlaigle): http://download.chainfire.eu/589/Sup...erSU-v2.16.zip
You should now have a fully rooted, custom TWRP recovery, SuperuserSU Developer Edition Note 4.
5. Optional , but recommended: Now, do another backup. You will have a stock backup with root (you can never have to many backups at this point in the Note 4 development).
Click to expand...
Click to collapse
This is one way to do it. I have built a custom SecSettings.apk that won't trip SysScope so my device will remain Official with no unlocked padlock on boot. I will Odin CF Auto Root, then Odin TWRP , Backup, Then flash my Custom SecSettings.apk.
EMSpilot said:
This is one way to do it. I have built a custom SecSettings.apk that won't trip SysScope so my device will remain Official with no unlocked padlock on boot. I will Odin CF Auto Root, then Odin TWRP , Backup, Then flash my Custom SecSettings.apk.
Click to expand...
Click to collapse
Nice!
framework-res mods
I also finished my framework-res.apk mods that includes native hotspot, battery warning changed from 15% to 5% and will run the phone unitl 1%. Also included is the maximum sound limitation and all rotations!!
I don't get my phone until tomorrow and most likely won't test until Sunday.
I am happy to post a zip for those that want to test. But only do so if you have a working backup on TWRP that you have tested.
EMSpilot said:
This is one way to do it. I have built a custom SecSettings.apk that won't trip SysScope so my device will remain Official with no unlocked padlock on boot. I will Odin CF Auto Root, then Odin TWRP , Backup, Then flash my Custom SecSettings.apk.
Click to expand...
Click to collapse
Would that just be a cosmetic fix during boot or does it turn back any counters we might have tripped?
optimusv45 said:
I don't recall seeing any developer edition device having their own section. It's always been devs specifying devices in the op
Click to expand...
Click to collapse
I've seen some other sites provide a separate "Developer Edition" sections under their Mods/Development etc. sections. The reason is pretty sound...it helps prevent retail owners from flashing/installing mods that would brick their phones and likewise, it isolates mods that are safe for Developer Edition phones to flash. Flashing a retail version of a ROM for instance on a Developer Edition phone will most often lock the bootloader...not a good thing to have happen. The other reason is it facilitates finding information about your particular phone. As you can tell, looking through thousands of threads lumped under general or question and answer sections can be very time consuming and not always easy to ferret out what applies and what doesn't apply.
No it does not turn back any counters. It prevents them from being tripped in the first place. If you tripped it already, you must get back to stock via Odin and start all over.
Sent from my SM-G900V using Tapatalk 2
EMSpilot said:
This is one way to do it. I have built a custom SecSettings.apk that won't trip SysScope so my device will remain Official with no unlocked padlock on boot. I will Odin CF Auto Root, then Odin TWRP , Backup, Then flash my Custom SecSettings.apk.
Click to expand...
Click to collapse
Can you upload that SecSettings.apk?
Thanks
So, I'd like to root my phone, but I've never done something like this. I've once rooted a phone with KingRoot, but I don't wanna do that again, since that's a pretty shady app. I'd like to root it the normal way, with SuperSU or something.
Also, I don't wanna lose any of my data. I know that anything can go wrong, but I'd just like a method that generally doesn't wipe your phone.
Thanks for any help
botetta said:
So, I'd like to root my phone, but I've never done something like this. I've once rooted a phone with KingRoot, but I don't wanna do that again, since that's a pretty shady app. I'd like to root it the normal way, with SuperSU or something.
Also, I don't wanna lose any of my data. I know that anything can go wrong, but I'd just like a method that generally doesn't wipe your phone.
Thanks for any help
Click to expand...
Click to collapse
Flash the latest TWRP recovery via Odin. Download magisk/super su. Go to recovery, put the files you downloaded and flash. Done
sm-a510f said:
Flash the latest TWRP recovery via Odin. Download magisk/super su. Go to recovery, put the files you downloaded and flash. Done
Click to expand...
Click to collapse
Thanks! But doesn't flashing TWRP require an unlocked bootloader? (and unlocking it wipes the phone as far as I know) Or is there a way to flash TWRP without unlocking the bootloader/wiping the phone?
botetta said:
Thanks! But doesn't flashing TWRP require an unlocked bootloader? (and unlocking it wipes the phone as far as I know) Or is there a way to flash TWRP without unlocking the bootloader/wiping the phone?
Click to expand...
Click to collapse
No you just need to unlock the OEM in developer settings and go to download mode to flash the recovery. You will lose guaranty but no data
sm-a510f said:
No you just need to unlock the OEM in developer settings and go to download mode to flash the recovery. You will lose guaranty but no data
Click to expand...
Click to collapse
Thanks, I'll try it out
sm-a510f said:
No you just need to unlock the OEM in developer settings and go to download mode to flash the recovery. You will lose guaranty but no data
Click to expand...
Click to collapse
Could you please link me the TWRP and the SuperSU that supports Samsung Galaxy A5 2016 7.0? :angel:
For model SM-A510F/FD/Y/M use this guide: https://forum.xda-developers.com/sa...overy-samsung-sm-a510f-fd-exynos7580-t3314399 . For model SM-A510 use this guide: https://forum.xda-developers.com/sa.../twrp-3-0-0-0-galaxy-a52016-sm-a510f-t3313781
---------- Post added at 09:51 AM ---------- Previous post was at 09:42 AM ----------
Also you aren't allowed to post questions in the General section. Look at the sticky post
botetta said:
Could you please link me the TWRP and the SuperSU that supports Samsung Galaxy A5 2016 7.0? :angel:
Click to expand...
Click to collapse
TWRP : https://forum.xda-developers.com/sa...overy-twrp-3-1-0-0-samsung-galaxy-a5-t3606792
Super SU : https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
If you want to play games like Pokemon go or Super Mario run, you will need magisk instead of superSU
Now, I followed the instructons, and I was able to root my phone succesfully. (Thanks )
In case someone reading this thread wants to know I used:
Odin 3.10.7
twrp_3.0.2-1_sm-a510_mm_1816
SR3-SuperSU-v2.79-SR3-20170114223742.zip
It all worked fine, no data loss, no wifi/camera error, no nothing, but when I turned off my phone, It wouldn't boot back anymore, It said "custom binary is blocked by FRP Lock"
As I've read, this is because I turned off OEM Unlock after rooting, but I'm not sure about this. Appearantly, if I'd leave it on it'd not cause this problem
Since then, my phone is working again, I just had to flash the Stock ROM, and I (fortunatly) didn't lose any data.
But obviously now my root is gone too. Could someone who has tried this confirm that it indeed works (boots up) normally if I leave OEM Unlock on forever?
CrystalGTX said:
Also you aren't allowed to post questions in the General section. Look at the sticky post
Click to expand...
Click to collapse
Sorry about that
botetta said:
Now, I followed the instructons, and I was able to root my phone succesfully. (Thanks )
In case someone reading this thread wants to know I used:
Odin 3.10.7
twrp_3.0.2-1_sm-a510_mm_1816
SR3-SuperSU-v2.79-SR3-20170114223742.zip
Click to expand...
Click to collapse
I've sent you the latest twrp and super SU, why did you choose another one ? They are working perfectly (pm if you want to upgrade your TWRP)
sm-a510f said:
I've sent you the latest twrp and super SU, why did you choose another one ? They are working perfectly (pm if you want to upgrade your TWRP)
Click to expand...
Click to collapse
Well, that's what the other guy sent, I had to choose one of them. BTW, do you always have OEM Unlock turned on, or have you turned it off. If you have it on, I'm pretty sure it's not the TWRP version, it's that I turned OEM off. If it boots without OEM on for you, then I guess I screwed it up, and I should have used the other version
botetta said:
Well, that's what the other guy sent, I had to choose one of them. BTW, do you always have OEM Unlock turned on, or have you turned it off. If you have it on, I'm pretty sure it's not the TWRP version, it's that I turned OEM off. If it boots without OEM on for you, then I guess I screwed it up, and I should have used the other version
Click to expand...
Click to collapse
Next time take my links they are up-to-date. Yes you always need the OEM unlock on, TWRP are nothing to do here.
sm-a510f said:
Next time take my links they are up-to-date. Yes you always need the OEM unlock on, TWRP are nothing to do here.
Click to expand...
Click to collapse
Okay, I'm not sure if I'll try root again, I might, and if I do, I'll use the newer versions, if you say they work perfectly. But the main problem wasn't the older version here, but that I turned off OEM, I guess.
And thanks for all the help, appreciate it
botetta said:
Okay, I'm not sure if I'll try root again, I might, and if I do, I'll use the newer versions, if you say they work perfectly. But the main problem wasn't the older version here, but that I turned off OEM, I guess.
And thanks for all the help, appreciate it
Click to expand...
Click to collapse
Well, If you want to turn off the OEM unlocking and be still rooted. You need to flash stock recovery after rooting. I've never tried it cause I don't care that much. Anyway you don't loose anything if you end up with frp lock. Again flash stock ROM you are good to go. And I've A5-510FD android 7.0 rooted. You may also want to backup to your Samsung account in case you mistakenly format your phone you can restore. That's what I always do.
botetta said:
So, I'd like to root my phone, but I've never done something like this. I've once rooted a phone with KingRoot, but I don't wanna do that again, since that's a pretty shady app. I'd like to root it the normal way, with SuperSU or something.
Also, I don't wanna lose any of my data. I know that anything can go wrong, but I'd just like a method that generally doesn't wipe your phone.
Thanks for any help
Click to expand...
Click to collapse
The best way is to flash Cf Auto root that is compatible with your device using Odin PC.
Download a exact version of CF AUTO ROOT for model number of your device.
Run Odin on your pc and thenConnect your phone to Pc with usb and then go to download mode(Turn off your phone>hold Volume down and Home button and Power button together, a new page will be shown press volume Up for confirmation.
Then press on AP In Odin and select the CF AUTO ROOT file and then press start the process will be started.
Be aware that in this way you will lose your warranty for ever due to Knox warranty void will be tripped and there is no way to return it to back.
UPDATO said:
The best way is to flash Cf Auto root that is compatible with your device using Odin PC.
Download a exact version of CF AUTO ROOT for model number of your device.
Run Odin on your pc and thenConnect your phone to Pc with usb and then go to download mode(Turn off your phone>hold Volume down and Home button and Power button together, a new page will be shown press volume Up for confirmation.
Then press on AP In Odin and select the CF AUTO ROOT file and then press start the process will be started.
Be aware that in this way you will lose your warranty for ever due to Knox warranty void will be tripped and there is no way to return it to back.
Click to expand...
Click to collapse
On the contrary. The best way in my opinion is flashing SuperSU with TWRP.
The reason is TWRP is your safety net should anything go wrong. You will always be able to boot to recovery regardless of the Bootable state of the device.
The whole device can be backed up and restored in minutes as long as /data encryption is not in force.
Then SuperSU can be flashed.
While CF-AUTOROOT is the goto root for simplicity and beginners it's not the preferred way.
Root is rather pointless without a custom recovery to go with it imo.
Once you've rooted the stock recovery becomes dead in the water and useless.
hello everybody!
I'm new here and want to root my Samsung Galaxy A5 (2016) and try some custom ROM.
Here is my phones details:
-Samsung Galaxy A5 (SM-A510F)
-Android 7.0
-Security patch: 1 April 2017
Also on Settings > Software Update, I have set manual update and there is a notification about one new software updates (last check 11/08/2018).
Do you know if its a Operation System update or just a security patch?
Should I do that update or will cause any problems with rooting and custom ROM?
What TWRP should I use and what custom ROM?
Any good guide?
Thanks in advance
Terranti said:
hello everybody!
I'm new here and want to root my Samsung Galaxy A5 (2016) and try some custom ROM.
Here is my phones details:
-Samsung Galaxy A5 (SM-A510F)
-Android 7.0
-Security patch: 1 April 2017
Also on Settings > Software Update, I have set manual update and there is a notification about one new software updates (last check 11/08/2018).
Do you know if its a Operation System update or just a security patch?
Should I do that update or will cause any problems with rooting and custom ROM?
What TWRP should I use and what custom ROM?
Any good guide?
Thanks in advance
Click to expand...
Click to collapse
im like him, any news guys?
any way to root the phone?
thanks!
mironkraft said:
im like him, any news guys?
any way to root the phone?
thanks!
Click to expand...
Click to collapse
Enable "Developer Options" on your phone and enable "OEM Unlock" (Don't disable it ever.)
Go here https://twrp.me/samsung/samsunggalaxya52016exynos.html
Download the latest twrp file (Use the links that says "Primary Download US/EU") (Currently it's twrp-3.2.3-0-a5xelte.img.tar 14/8/2018)
Go here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the latest Magisk file (Currently it's 16.0 / 16.7 if you want to use beta 14/8/2018)
Download Odin
Boot your phone into download mode (Volume Down + Home Button + Power Button)
Plug your device to your computer and open Odin
Go to "Options" tab in Odin and disable "Auto Restart"
Select the TWRP file you have downloaded (Click AP!!!)
Start...
When it's done DON'T BOOT TO SYSTEM YET, boot into recovery!!! (Volume Up + Home Button + Power Button)
Now you should have booted into TWRP
Go to "Install" tab and flash the Magisk file you downloaded
Boot into your system.
You have successfully rooted and installed TWRP to your device. (Hopefully)
TanByv said:
Enable "Developer Options" on your phone and enable "OEM Unlock" (Don't disable it ever.)
Go here https://twrp.me/samsung/samsunggalaxya52016exynos.html
Download the latest twrp file (Use the links that says "Primary Download US/EU") (Currently it's twrp-3.2.3-0-a5xelte.img.tar 14/8/2018)
Go here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the latest Magisk file (Currently it's 16.0 / 16.7 if you want to use beta 14/8/2018)
Download Odin
Boot your phone into download mode (Volume Down + Home Button + Power Button)
Plug your device to your computer and open Odin
Go to "Options" tab in Odin and disable "Auto Restart"
Select the TWRP file you have downloaded (Click AP!!!)
Start...
When it's done DON'T BOOT TO SYSTEM YET, boot into recovery!!! (Volume Up + Home Button + Power Button)
Now you should have booted into TWRP
Go to "Install" tab and flash the Magisk file you downloaded
Boot into your system.
You have successfully rooted and installed TWRP to your device. (Hopefully)
Click to expand...
Click to collapse
Thanks for your response.
That about the software update notification?
Do you know if its a Operation System update or Security patch update?
Should I run it, before root and install a custom ROM or better leave like this?