ANYTHING THAT HAPPENS FROM HERE ON WE WILL ATTEMPT TO SEE WHAT CAN BE FIXED BUT DO TAKE NOTE THAT BRINGING IT TO A SERVICE CENTER AFTER MODIFYING ANYTHING AND THEY WILL TELL YOU THE PHONE NEEDS A NEW MOTHERBOARD FOR THE PRICE OF A NEW C3. YOU HAVE BEEN WARNED, SO TAKE EXTRA CAUTION
Hi everyone, this is a general thread for those wishing to break into your new C3 device now that a window has opened in terms of firmware.
Be advised, Sony has stated there will be no rear camera fix and no Marshmallow for the C3
This guide will assume your bootloader is unlocked, if you do not have any idea what it means or how to get about it, you must divert your attention HERE for a bit. Use that link for know-how to unlock your bootloader, and only proceed after successful unlocking. For bootloader codes, select the Z3 Compact as your device, because it shares the same unlock key generation algorithm.
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Now, first thing's first, let’s get root + custom recovery. This is important, because people have been recommending KingRoot and as far as I'm concerned that is the most asinine way to provide system privileges. You wouldn't believe the pain I endured just to remove it and install SuperSU, which is far more reliable. Anyone who wishes to disagree or feels offended by this preference may kindly sod off, no offence.
STOP!
This section is only for Lollipop 5.1 firmwares, anything else and we can't guarantee safety.
Now that you read the warning, let's continue with recovery.
Head HERE for the D2533 files, and HERE for the D2502/D2503 files.
D2533:
1. If you want root as well, get SuperSU and copy it to your SD (Internal/External)
2. Unzip the .zip archive, this contains everything you need.
3. Turn off your phone and plug it into your PC/Laptop while holding the VOLUME DOWN button. It will install a driver first.
4. Double-click the .bat file in the folder of the extracted archive.
5. Read and accept the T’s&C’s
6. The recovery will now install XZDR. When your phone reboots, hold VOLUME DOWN. The green LED should turn PURPLE.
7. You will now be in TWRP recovery. At this point, you can install SuperSU, Custom ROMs, or anything you may otherwise want.
8. Once done, reboot your phone.
D2502/D2503:
1. You need these files first. If you want root, get SuperSU as well.
2. Add the .img file into your fastboot folder.
3. Now, turn off your phone and plug it into your PC/Laptop while holding the VOLUME DOWN button. It will install a driver first.
4. Right-click the space inside the folder while holding SHIFT then click 'Open Command Window Here'
5. You will see a command prompt window so just type
Code:
fastboot flash boot boot.img
6. It will send the .img files and let you know when done
7. Now type
Code:
fastboot reboot
to reboot your phone
8. When your phone turns on, a green LED will light up. Hold VOLUME DOWN, the LED should turn PURPLE.
9. You will now be in TWRP recovery. At this point, you can install SuperSU, Custom ROMs, or anything you may otherwise want.
10. Once done, reboot your phone.
Soooo, what now?
If you are a dev or would like to become a dev for this device, head HERE to restart CM12.1 development.
Come to THIS THREAD for information on deodexing your device and give it a fresh look. This is a relatively new development so be patient and check in once in a while for forum news.
Check out the custom stock kernel for the 5.1.1 stock ROM here.
In addition, with a recovery you can now instant reinstall your system for your D2533 or D2502 via zip flashing without adding root and recovery all over again.
Did you know that our phone is missing the Bravia Engine? Yes, a Sony without Sony's best feature. Fortunately it can be fixed, with your recovery just download and flash the files provided in this thread.
This thread is a work in progress, any questions are welcome. It is encouraged and we'll try our best to help so anyone can learn on what to do and what to improve.
Credits:
• @wwwhana
• @Riccorbypro
• @Gaurav007
• @cezer kiran
Upgrading and downgrading your firmwares
Warning:
Code:
Your bootloader must be unlocked.
Doing this has the potential to brick your device if not careful.
All your data and settings will be wiped as well.
So now you realise you prefer the simpler and uglier KitKat version, or miss the horrible camera in Lollipop 5.0, or you just want to use the weirdo Lollipop 5.1 for the LOLZ.
This is simple enough but will require some a lot of internet bandwidth so be prepared.
Download Xperifirm and find your phone model, it will tell you what are the available firmwares you can download for your country. Just download them, remember where you place those files.
Next you will need Flashtool by Androxyde, just unpack it and install.
Running it will synchronise the updates so just wait a while for it to load. Once done, click the lightning symbol and select Flashmode.
A window will open up asking you to select firmware, which is the .ftf file you downloaded using Xperifirm a while ago.
The only options you modify is Wipe: Tick all and Exclude: Untick all. After that, click flash and it will instruct you to insert your phone.
Make sure your phone is turned off, then plug in while holding the VOLUME DOWN button.
The process will automatically start so you just have to wait until it's done then it will auto reboot and start setting up your phone like new.
Optimising your device
First off, download Kernel Adiutor and grant it root access. Open it, and look in the Build Prop Editor section.
Look for this code and edit it to this value:
Code:
ro.min_freq_0=300000
Now reboot your device, this will make your phone unlock minimum speed to save some battery.
All good?
Now, let's look at the CPU section. Set the CPU maximum frequency to 1190 and the minimum to 300, then set CPU governor to Interactive. Open up CPU Governor Tunables and edit the values according to this picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That completes the CPU section, now we have to edit the Kernel Samepage Merging. Go into that tab, and enable KSM. Set Page scans to 100, and Sleep to 500.
After editing each tab here, make sure you tick Apply on Boot so the settings will stay there.
This section is still under construction.
awesome!
RE
Thank you for the reply in my email sir. :good: :good: I will try this method but i want to wait for other replies.
It's not that I don't trust your thread but I just want to have a little bit safety. I hope you understand....
E-Bin said:
Thank you for the reply in my email sir. :good: :good: I will try this method but i want to wait for other replies.
It's not that I don't trust your thread but I just want to have a little bit safety. I hope you understand....
Click to expand...
Click to collapse
I don't mind. First time I came here to root the C3 I trusted nobody.
Install TWRP XZDual
Hello. I have a Sony D2502 with 5.1.1. Used Kingroot to root my phone so I can disable annoying Sony Bloatwares and without having to unlock the bootloader. So I am not sure if bootloader got unlocked as well. I have 3 concerns and would to ask for your assistance and proficiency.
1. Is possible to install TWRP with a locked bootloader? If so, how? I'd like to request for the procedure without the android tech jargons.
2. If it can't be done, what is my contingency plan in installing twrp without having to reformat my phone.
3. Tried several methods on how to enter default/stock recovery mode on my Sony D2502. Tried, press and hold Volume Down and Power, Volume Up and Power, Pressed All 3 at the same, it only vibrates. No problem with rebooting to safe mode and normal mode. How do I enter the stock android/experia recovery mode?
RK_D2502 said:
Hello. I have a Sony D2502 with 5.1.1. Used Kingroot to root my phone so I can disable annoying Sony Bloatwares and without having to unlock the bootloader. So I am not sure if bootloader got unlocked as well. I have 3 concerns and would to ask for your assistance and proficiency.
1. Is possible to install TWRP with a locked bootloader? If so, how? I'd like to request for the procedure without the android tech jargons.
2. If it can't be done, what is my contingency plan in installing twrp without having to reformat my phone.
3. Tried several methods on how to enter default/stock recovery mode on my Sony D2502. Tried, press and hold Volume Down and Power, Volume Up and Power, Pressed All 3 at the same, it only vibrates. No problem with rebooting to safe mode and normal mode. How do I enter the stock android/experia recovery mode?
Click to expand...
Click to collapse
1. I think it's possible with the T2U Dualrecovery, it contains TWRP already. I was perturbed at first about android lingo as well, but most guides are simplified enough and there will be people who are willing to answer your questions.
2. You can use the guide you found in the nut-xperiafiles website. Other than that, there's no other way.
3. The C3 does not come with a stock recovery. Sony hates anything that isn't their flagship phone.
T2U-lockeddualrecovery2.8.26-RELEASE.combined.zip <--- Is this the correct/compatible release for Sony D2502? If so, I would like to write down the steps as I understand them:
1. Extract Zip file and Run .bat file
2. Connect Phone, with USB Debugging Enabled. (Should the phone be turned off or leave it on?)
3. Select 1 from the CMD Menu? Follow the process and it will reboot for the first time to TWRP?
RK_D2502 said:
T2U-lockeddualrecovery2.8.26-RELEASE.combined.zip <--- Is this the correct/compatible release for Sony D2502? If so, I would like to write down the steps as I understand them:
1. Extract Zip file and Run .bat file
2. Connect Phone, with USB Debugging Enabled. (Should the phone be turned off or leave it on?)
3. Select 1 from the CMD Menu? Follow the process and it will reboot for the first time to TWRP?
Click to expand...
Click to collapse
Yes, the phone should be left on. Just select 1, it should be the same though I've never used KingRoot.
AutumQueen92 said:
Yes, the phone should be left on. Just select 1, it should be the same though I've never used KingRoot.
Click to expand...
Click to collapse
Ok. Many thanks. Several apps would tell me I am rooted. Not sure if XZdual would work on Kingroot.
Thanks. I was ablt o install TWRP. How Kingroot is still installed. I thought SUPERSU was going to delete annoying kingroot.
RK_D2502 said:
Thanks. I was ablt o install TWRP. How Kingroot is still installed. I thought SUPERSU was going to delete annoying kingroot.
Click to expand...
Click to collapse
Kingroot will stay until you do a full reinstall or brute force uninstall. It would be better to just do a full wipe, and flash the prerooted stock roms instead. Just make sure to backup any apps you might have.
Sent from my Xperia C3 using XDA Labs
AutumQueen92 said:
Kingroot will stay until you do a full reinstall or brute force uninstall. It would be better to just do a full wipe, and flash the prerooted stock roms instead. Just make sure to backup any apps you might have.
Sent from my Xperia C3 using XDA Labs
Click to expand...
Click to collapse
I was able o install XZDUAL easily but had to install SUPERSU with a different approach though. KINGROOT was blocking it somehow. Used Terminal Emulator apk to install SUPERSU and updated via Play store. and it worked. Uninstalled KINGROOT. Restarted/Rebooted phone about 10x just to make sure it wasn't a fluke. All up and running at the moment. Thanks.
RK_D2502 said:
I was able o install XZDUAL easily but had to install SUPERSU with a different approach though. KINGROOT was blocking it somehow. Used Terminal Emulator apk to install SUPERSU and updated via Play store. and it worked. Uninstalled KINGROOT. Restarted/Rebooted phone about 10x just to make sure it wasn't a fluke. All up and running at the moment. Thanks.
Click to expand...
Click to collapse
No problem. I forgot about the terminal emu method lel
Sent from my Xperia C3 using XDA Labs
LTE Unlock
AutumQueen92 said:
No problem. I forgot about the terminal emu method lel
Sent from my Xperia C3 using XDA Labs
Click to expand...
Click to collapse
Hello Autumn. Have you tried unlocking the LTE aspect of D2502? If so, how? I have 5.1.1 Os, XZdual and SUPERSU. Good riddance to kingroot.
RK_D2502 said:
Hello Autumn. Have you tried unlocking the LTE aspect of D2502? If so, how? I have 5.1.1 Os, XZdual and SUPERSU. Good riddance to kingroot.
Click to expand...
Click to collapse
I've no idea, my D2533 came with LTE already.
Kernel Adiutor Optimal Settings
Hello Autumn.
Based on your snapshot below, is this a balanced setting? if so, then i'd most likely replicate this. Phone is working well so far after the twrp installation and SUPERSU replacement on Kingroot., feels like brand new when i got the D2502 about 2 years ago. I'd like to make some speed improvements while having stability at the same time. thanks
RK_D2502 said:
Hello Autumn.
Based on your snapshot below, is this a balanced setting? if so, then i'd most likely replicate this. Phone is working well so far after the twrp installation and SUPERSU replacement on Kingroot., feels like brand new when i got the D2502 about 2 years ago. I'd like to make some speed improvements while having stability at the same time. thanks
Click to expand...
Click to collapse
It worked for me, but I'm in the midst of testing out a new setting so hopefully it can be updated soon.
Sent from my Xperia C3 using XDA Labs
Kingroot Leftovers
Hello Autumn, after fiddling around with my settings, came across CPU Processes and ran into KINGRot. I am all set, I have XZDUAL, SuperSU. Everything is running great except having the remnants of Kingroot. Please see attached file. How can delete this? Is it safe without bricking my phone? If so, how?
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Vodafone Smart first 6* NL *(EU) Rooting and More!
Done & Closed!After a wild chase finding the correct tools and apk's this took me 2 days to complete an fully rooted and Simlock free Vodafone branded Smart Firt 6.
Most of the files can be downloaded from below here on XDADISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's have risks and may Void your warranty and can result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
It may be that you get an *softbrick *(bootloop) because Vodafone still pushing update's for their Firmware patching and upgrading the software!
To be safe please use methods given by: Androrooter and or Kirito9 !
#Rooting:
1# Download the root.apk onto your phone or SD card and install.
2# Now start the app and you will see it's all in Chinese, just click on the Root Shield Badge ontop of the screen.
3# Let it do its magic installing the scripts most likely it will auto reboot your phone without rooting it,
you must restart the root app again and click on the Badge (like done at step 2#).
~Now you are Rooted but the Superuser is Chinese and what i have noticed it's a temporary Root, if you lose root again just redo step 2#!
4# Download and install SuperSu-2.46 now launch an root app most likely the Chinese app will popup granting
for root permission, you must click on the colored (grant) button to accept.
5# Download an Root browser i.e. File Manager and let it gain Root permission, if SuperSu wont ask for Root it's now save to uninstall the Chinese app.
~From now on you permanently Rooted, don't go installing/modding stuff yet until you made an systems backup!
#Twrp or Cwm Recovery (PC version):
1# Download ADB Driver and install on PC. Download from here; http://www.datafilehost.com/d/2267ab98
2# Download TWRP Setup (thanks to Dees_Troy & Yuweng) and unzip on your PC.
3# Activate USB debugging under developer mode* and connect with USB to your PC.
(done by *tapping 7 times on the build number in the about phone section)
3a# Open the Twrp setup.exe and click on the next button.
3b# Just wait till the installation is completed followed by credits.
3c# On the next window, click on yes to proceed.
3d# Select Start Easy Magic TWRP Installer for MediaTek and click on ok
3e# Click on Yes to auto port.
3f# Now make sure your phone is connected, adb driver installed and usb debugging enabled, then click on OK.
~if you get any pop up msg on your phone screen just click on yes.
Just wait for a few seconds while the setup is been completed,
if the process was successful, your phone should automatically reboot into recovery.
~Now you need to make an full backup with Twrp so that all the files are safe!
#More Updates following Soon! To be safe please use methodes given by: Androrooter and or Kirito9 !
-reserved
does not work
It says root failed on my VF695 and therefore cannot install TWRP.
QuantumRevenger said:
It says root failed on my VF695 and therefore cannot install TWRP.
Click to expand...
Click to collapse
Kingroot 4.8 worked, so I ran the TWRP Setup and guess what another way to ruin the phone even further. Stuck in a boot loop now.
STAY AWAY FROM THIS GUYS GUIDE! It will most likely break your phone from start to finish!
Please provide a reset copy of your system.img and recovery.img for people who have lost their phones due to this guide, it would be very useful as the devices can be restored if adb / fastboot access can be achieved.
At Your Own Risk!
QuantumRevenger said:
It says root failed on my VF695 and therefore cannot install TWRP.
Click to expand...
Click to collapse
QuantumRevenger said:
Kingroot 4.8 worked, so I ran the TWRP Setup and guess what another way to ruin the phone even further. Stuck in a boot loop now.
STAY AWAY FROM THIS GUYS GUIDE! It will most likely break your phone from start to finish!
Please provide a reset copy of your system.img and recovery.img for people who have lost their phones due to this guide, it would be very useful as the devices can be restored if adb / fastboot access can be achieved.
Click to expand...
Click to collapse
Well well QuantumRevenger,
Sorry to hear that this method didn't worked out nicely for you.
Maybe your firmware got upgraded and the recovery didn't stick?!
Did you try the combination Power + Vol Up while the phone is off and enter
the Recovery menu clear Cache + Dalvik after this reboot.
I can't help you with the systems files because i ditched the vodafone firmware for Vanilla 4.4.2 Android.
The only thing i can do for you is point to this thread where i moved towards myself-> MTK devices
Here you will learn an little how your MTK device works, also you can search XDA for an different Easy Magic TWRP or CTR or even Philz!
Enjoy
&
Good luck!
Do you know if this will also work on the UK model?
At Your Own Risk!
RHodgett said:
Do you know if this will also work on the UK model?
Click to expand...
Click to collapse
Hello RHodgett,
It most likely would work because this model bought by Vodafone for their (EU) market.
As we all know it's a cheap china phone suited for Vodafone requirements!
~Not speaking for the firmware updates they push once an while~
But rooting can be done very easy with the given root from my post or even now with the updated
Kingroot 4.8 said by QuantumRevenger. And like for the custom recovery it can get tricky mentioned by QuantumRevenger, i had no problem with this at that moment.
But i urge you to read my answer to QuantumRevenger problem from above, after that you can decide at your own risk.
Enjoy
&
Good Luck!
Thanks, I'll give this a go when the handset arrives in a few days and report back.
Can you explain how to then install the Vanilla 4.4.2 Android firmware? (or any other suitable stock firmware for the device)
Come to the otherside
RHodgett said:
Thanks, I'll give this a go when the handset arrives in a few days and report back.
Can you explain how to then install the Vanilla 4.4.2 Android firmware? (or any other suitable stock firmware for the device)
Click to expand...
Click to collapse
No Problem & you're welcome!,
For flashing roms you need an custom recovery otherwise you can't Flash.
Nobody here is tailoring for our Vodafone branded(China) smart first 6 so you have to go where i send QuantumRevenger towards and where i am. (See post answering QuantumRevenger).
Here you can use the roms and learn more about our MTK devices in general.
For flashing roms you must install in the recovery as an zip file and then you're done!
MTK has other methodes to install but that's for advance users only.
Enjoy
&
Goodluck.
Hi, I've root using the Chinese apk and root checker says the device is rooted but I wasn't able to install SuperSU 2.46, it keeps saying the binaries need to be updated and it fails every time I update.
Rebooting using the TWRP setup just shows the Powered by android splash. I'm not sure what to do now?
Edit: Ok I've flashed a recovery from the threads you linked, finally got a bootloader working. Now to flash a ROM Got CM12.1 running, thanks!
DID not work for me
So I followed all the steps and everything seemed to work fine. The TWRP software said it was going to reboot into recovery but it is stuck at the android logo screen.
When I hold power button + up key its the same, stuck at the android screen.
When I hold power button + down key it boots into vodafone android.
I'm kind of stuck to what to do now (sorry I am really new to this)?
RHodgett said:
So I followed all the steps and everything seemed to work fine. The TWRP software said it was going to reboot into recovery but it is stuck at the android logo screen.
When I hold power button + up key its the same, stuck at the android screen.
When I hold power button + down key it boots into vodafone android.
I'm kind of stuck to what to do now (sorry I am really new to this)?
Click to expand...
Click to collapse
Darn that's a bummer! It worked for me and had everything running xposed, SuperSu etc. :/
Try another Magic installer use CWM or Phillz, they can be found here or via google.
So weird i bet Vodafone did a firmware push on there bootloader or not all EU firmwares are the same(dat would be pretty nonlogical).
Sorry for the troubles please try the above solution and report back if that fixed it.
Goodluck!
How to load and unzip
Menroid said:
Vodafone Smart first 6* NL *(EU) Rooting and More!
Done & Closed!After a wild chase finding the correct tools and apk's this took me 2 days to complete an fully rooted and Simlock free Vodafone branded Smart Firt 6.
Most of the files can be downloaded from below here on XDADISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's have risks and may Void your warranty and can result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
It may be that you get an *softbrick *(bootloop) because Vodafone still pushing update's for their Firmware patching and upgrading the software!
#Rooting:
1# Download the root.apk onto your phone or SD card and install.
2# Now start the app and you will see it's all in Chinese, just click on the Root Shield Badge ontop of the screen.
3# Let it do its magic installing the scripts most likely it will auto reboot your phone without rooting it,
you must restart the root app again and click on the Badge (like done at step 2#).
~Now you are Rooted but the Superuser is Chinese and what i have noticed it's a temporary Root, if you lose root again just redo step 2#!
4# Download and install SuperSu-2.46 now launch an root app most likely the Chinese app will popup granting
for root permission, you must click on the colored (grant) button to accept.
5# Download an Root browser i.e. File Manager and let it gain Root permission, if SuperSu wont ask for Root it's now save to uninstall the Chinese app.
~From now on you permanently Rooted, don't go installing/modding stuff yet until you made an systems backup!
#Twrp or Cwm Recovery (PC version):
1# Download ADB Driver and install on PC. Download from here; http://www.datafilehost.com/d/2267ab98
2# Download TWRP Setup (thanks to Dees_Troy & Yuweng) and unzip on your PC.
3# Activate USB debugging under developer mode* and connect with USB to your PC.
(done by *tapping 7 times on the build number in the about phone section)
3a# Open the Twrp setup.exe and click on the next button.
3b# Just wait till the installation is completed followed by credits.
3c# On the next window, click on yes to proceed.
3d# Select Start Easy Magic TWRP Installer for MediaTek and click on ok
3e# Click on Yes to auto port.
3f# Now make sure your phone is connected, adb driver installed and usb debugging enabled, then click on OK.
~if you get any pop up msg on your phone screen just click on yes.
Just wait for a few seconds while the setup is been completed,
if the process was successful, your phone should automatically reboot into recovery.
~Now you need to make an full backup with Twrp so that all the files are safe!
#More Updates following Soon!
Click to expand...
Click to collapse
I loaded into the Phone memory, but not it says cant ready such a file. SO how does one unzip the root file whilst in the Android phone? OR is is that we unzip whilst on the PC and then transfer all of it into the ANdoird phone?
Can you explain how you achieved this? WIll halp tremendously.
Thanks
onlydongles said:
I loaded into the Phone memory, but not it says cant ready such a file. SO how does one unzip the root file whilst in the Android phone? OR is is that we unzip whilst on the PC and then transfer all of it into the ANdoird phone?
Can you explain how you achieved this? WIll halp tremendously.
Thanks
Click to expand...
Click to collapse
Hello Onlydongles,
for root you can use kingroot 4.8 or the given Root apk from above.
Just install like any app for Android and follow the instruction.
Enjoy
&
Goodluck!
Menroid said:
Hello Onlydongles,
for root you can use kingroot 4.8 or the given Root apk from above.
Just install like any app for Android and follow the instruction.
Enjoy
&
Goodluck!
Click to expand...
Click to collapse
That's the problem. SiInce the file is in ZIP format, downloading into the SD card and then doing the Power+Vol up, and update from SD zip, gives me an aborted message.
Putting the Zip file in the Phone memory (not the sd card) just doesn't open the file, saying format not supported.(casue it is ZIP)
What am I missing? please help with a step by step idiots guide, if you can .
Thanks
---------- Post added at 09:38 PM ---------- Previous post was at 09:31 PM ----------
onlydongles said:
That's the problem. SiInce the file is in ZIP format, downloading into the SD card and then doing the Power+Vol up, and update from SD zip, gives me an aborted message.
Putting the Zip file in the Phone memory (not the sd card) just doesn't open the file, saying format not supported.(casue it is ZIP)
What am I missing? please help with a step by step idiots guide, if you can .
Thanks
Click to expand...
Click to collapse
Further info. I have downloaded from your links onto the PC and transferred into the SD card & phone.
onlydongles said:
That's the problem. SiInce the file is in ZIP format, downloading into the SD card and then doing the Power+Vol up, and update from SD zip, gives me an aborted message.
Putting the Zip file in the Phone memory (not the sd card) just doesn't open the file, saying format not supported.(casue it is ZIP)
What am I missing? please help with a step by step idiots guide, if you can .
Thanks
---------- Post added at 09:38 PM ---------- Previous post was at 09:31 PM ----------
Further info. I have downloaded from your links onto the PC and transferred into the SD card & phone.
Click to expand...
Click to collapse
The root is an normal APK there are only two zip files here; the TWRP and the SuperSu.
TWRP.zip is an magic installer for your PC with the given USB drivers and Debuging turned on(See my guide).
Now SuperSu.zip can only be installed via an custom recovery like TWRP.
I'm noticing you're trying to flash without an
custom recovery?, that's an no go.
1# Root with given or Kingroot 4.8.
2# Install custom recovery TWRP, CWM or Phillz (Must be an magic installer version via PC) all these versions can be found on Xda.
3# Flash SuperSu via custom recovery and replace the first installed Root!
That's all there is to it, no deeper layers on how-to install.
Enjoy
&
Good luck!
OK got it. THe only way I could get the APK into my phone is via the phones own browser from this site. I could only move from my pc as a ZIP file only. Hence could not install. But now its done. I think I am rooted now. Root checker still says not rooted, but I can use ES file explorer and have managed to remove a few app. Does this mean it is Rooted?
Can I remove the Rooting apk from the phone now without any adverse impact?
I have also managed to load the TWRP on the SD card. IF I want to Flash a rom, how do I go about it? Can you link and stable ROM which I can use? Need a small tutorial.
AND very many mahy thanks for your support on here and input.
Regds
onlydongles said:
OK got it. THe only way I could get the APK into my phone is via the phones own browser from this site. I could only move from my pc as a ZIP file only. Hence could not install. But now its done. I think I am rooted now. Root checker still says not rooted, but I can use ES file explorer and have managed to remove a few app. Does this mean it is Rooted?
Can I remove the Rooting apk from the phone now without any adverse impact?
I have also managed to load the TWRP on the SD card. IF I want to Flash a rom, how do I go about it? Can you link and stable ROM which I can use? Need a small tutorial.
AND very many mahy thanks for your support on here and input.
Regds
Click to expand...
Click to collapse
Okay Onlydongles,
I don't think you have Root (yet!), Es browser has an side menu.
Here you must scroll down and select Root Explorer, that's the real test if you got Rooted!
If not install Kingroot 4.8 via your phone browser.
For ROMs you have to go where I send everybody towards ->MTK Devices (link given in answers above).
Flashing ROMs is easy done by custom recovery select the downloaded ROM zip and flash with the given creator instructions B).
Enjoy
&
Good luck!
Nomnuds said:
Edit: Ok I've flashed a recovery from the threads you linked, finally got a bootloader working. Now to flash a ROM Got CM12.1 running, thanks!
Click to expand...
Click to collapse
How's CM12.1 running for you? Everything working OK?
The updated cross-device Sony thread tested with Nougat is here.
Guide updated on 21 October 2016.
PREFACE
First of all, this guide will probably work for all recent Sony phones.
This guide is based on a work of number of people. The information how to get this goal achieved is very sparse and it is scattered across the Internet. There are lot of guides, but typically they require a strong familiarity with many things, so inexperienced users may became confused. I decided to assemble a detailed newbie-friendly guide myself. So here it is.
Get rooted stock Sony firmware is not a straightforward and easy task, but if all steps covered in this guide are performed well, the goal will be achieved. Since the creation of this guide, stock firmware versions got bumped multiple times, but nothing has changed fundamentally in terms of rooting.
In this guide I (and you) will use the stuff from these notable people:
@Androxyde — Flashtool
@IgorEisberg — XperiFirm (integrated into Flashtool)
@Dees_Troy et al. — TWRP
@Chainfire — SuperSU
@tobias.waldvogel — Kernel repack script and DRM fix
@zxz0O0 — iovyroot
The whole process divided into the following steps:
Getting your phone recognized by your computer (driver installation).
Backup your DRM keys.
Unlocking a bootloader.
Flashing stock firmware with Flashtool.
Repacking and flashing a kernel.
Rooting with SuperSU.
Restore your DRM keys.
Optional tasks.
The one thing to consider before the flashing of your Xperia phone is the unlocking of the bootloader. There is the official way of doing this provided by Sony. It's easy and straightforward. Check step #3 below.
Before unlocking, one should know the main caveat: once you have unlocked your phone, you have lost your DRM keys. These keys are used to make certain proprietary Sony functions to work, such as X-Reality for Mobile, camera noise suppression and some others. It is possible to backup your keys in beforehand and restore them once the phone is rooted. This will be covered in this guide.
The repack script mentioned before, incorporates a so called DRM fix which effectively emulates lost DRM keys and most of proprietary functions remain in a working state. This fix will suffice for most users, so you probably may want to root your phone straight away, nevermind the keys. I hadn't myself extracted and restored DRM keys ever, since DRM fix works perfectly for me, so you may want to forget about these keys too. Some users are not ready to just erase them, however. The choice is up to you, but if the camera performance is your sole concern, I can confirm that with DRM fix it works perfectly.
After the completion of this guide, your phone contents will be completely erased, so you may want to backup all what is important to you to some external locations. External microSD card will not be erased, so you may copy your stuff to it. If you are on a rooted Lollipop or older Android, you may want to use some specialized tools like Titanium Backup or like. TWRP also have a nice backup features, if you have one already installed.
The guide was tested on Windows 10 Pro 64-bit and Sony Xperia Z5 Premium Dual-SIM E6883 official model for the Russian market. During the course of this guide you will get a specific firmware for your particular market so don't worry, this guide is market-agnostic. It is even model-agnostic. I believe this guide works for most Xperia phones on the market, but I personally tested it just with my Z5 Premium.
Let's go.
1. GETTING YOUR PHONE RECOGNIZED BY YOUR COMPUTER (DRIVER INSTALLATION)
During the course of this guide, your phone will comminicate with your computer in Fastboot and Flashmode connection modes. When connected in these modes, for the phone to be properly recognized by a computer, you have to provide special drivers. Thanks to Flashtool creators, it comes bundled with generic drivers compatible with all recent Windows operating systems, so at first you should install Flashtool. You can get installer from the official website.
Next, you should install Fastboot and Flashmode drivers for your phone.
One caveat here however, these drivers are not from a "recognized Windows developer", that is they are not Windows-certified, so to get them installed on Windows 8/10, you should reboot with the disabled driver signature enforcement. Use Google to know how to perform this.
Once booted in the aforementioned mode (or in a regular mode if you are still on Windows 7), proceed to the actual driver installation. The drivers are packed into the Flashtool\drivers\Flashtool-drivers.exe executable, but it didn't work on my system, perhaps because it is 64-bit (but feel free to try it yourself), so I simply unarchived it with 7-Zip (right-clicked it and chose 7-Zip > Extract to "Flashtool-drivers"). I got a Flashtool-drivers folder, which contained all the drivers from the executable.
Once drivers are unpacked, connect your phone in a Fastboot mode. Recent Sony devices can boot in Fastboot just like this: shutdown the phone, press and hold Volume Up rocker button and connect USB cable to the phone while the other end is connected to a running PC. The phone's LED will turn blue shortly. That's it, you are in a Fastboot mode. Open Device Manager (Win + X, Device Manager) and check if there is some unknown device (with the name S1Fastboot or something like this).
Double-click this unknown device in the Device Manager, click Update Driver..., then Browse my computer for driver software, and choose the Flashtool-drivers folder created earlier with 7-Zip (leave Include subfolders checked). Shortly you will get a red warning dialog window, which inform you that this driver doesn't have a proper signature:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Very scary. Just proceed with the install despite all the red flags, it's safe.
Once Fastboot driver is installed, plug out the USB cable off the phone and connect it in a FlashMode mode. This is done just like for Fastboot, but in this case you should press and hold Volume Down rocker button during the cable plugging in. The LED in this case will be green and not blue. The procedure to install the driver is exactly the same.
After the successful installation, try to reconnect the phone in these modes again couple more times to make sure all devices get properly recognized by Windows. If all seems good, proceed to the next step.
2. BACKUP YOUR DRM KEYS
There is a tool called iovyroot, with which you can backup your DRM keys from an unrooted phone, but at the time of the writing it doesn't support latest firmwares. It does support a lot of older firmwares so it may be useful to not upgrade your phone before checking up this tool.
If you're into this backup DRM thing, go to the original thread, download the latest version and check if it is working for you. For now I just skip this step. Basically, you want to download the zip, connect your phone in USB Debugging mode, run the tabackup.bat script and see the output.
I will not cover DRM keys extraction/restore in details, since I never did it, so I don't want to write about something I haven't myself performed. Please check corresponding threads.
Note that most proprietary Sony features will work even without DRM keys, such as X-Reality for Mobile, camera denoise filter and some others. DRM fix will be covered later in this guide. Some features will not work with DRM fix, Widevine for example. Most users will not even notice these.
3. UNLOCKING A BOOTLOADER
Sony does provide its own guide. It is a plain and simple and — good news! — if you have followed the previous steps, you just got all the prerequisites covered!
4. FLASHING STOCK FIRMWARE WITH FLASHTOOL
The Flashtool was installed on the completion of the first step, so let's start it. If you are on 64-bit Windows, start Flashtool64 (there is a shortcut in the Start menu). It does require administrator privileges.
Once you are in Flashtool, at first you need to obtain the most recent official stock firmware from Sony. Press the "XF" icon (the right-most one in the toolbar) to start XperiFirm. The window will open, choose the phone from the left part of the window (Xperia Z5 Premium (Satsuki)), then choose your particular model (I chose E6883 Dual) and after that choose your market and operator from the right part of the window. I chose 1299-4828 Russia Customized RU. Of course, you don't have to choose exactly this, click on the entries of your own choice. The entry will become highlighted and shortly there will be some info in the last column (Latest Firmware). This definition will be also in the right-most part of the window just under the phone thumbnail, click on it. Not a brilliant design decision, but that's it. Here is a screenshot for your reference:
The new window will pop up, press Download. The stock firmware will be downloaded to your computer and unpacked. Once the download is completed, close all XperiFirm windows to return to the main Flashtool window. Flashtool will begin creation of the .ftf file from the downloaded files which will be used for a (subsequent) flashing. FTF-files are similar to ZIP-files, and may be opened with 7-Zip. I've got E6883_32.2.A.0.305_1299-4828_R4C.ftf after the completion of this procedure. Flashtool places firmwares in the C:\Users\<Your Windows Username>\.flashTool\firmwares.
Now, once the stock firmware is downloaded, packed into .ftf and ready to be installed, let's do this. Disconnect the phone for now, physically extract microSD card (if any) and press the left-most button on the Flashtool's toolbar (the "Lightning" one) and choose Flashmode. The Firmware Selector window will appear with a selected default folder and list of all firmware available for a flashing. I've got a single entry, the firmware I just downloaded. Before actual flashing, you can check some checkboxes from the Wipe section, I usually check all to start clean (all the data on the phone is erased). Once again, just to be safe, extract the microSD card from the phone at this moment. It is not needed for a flashing anyway. Here is how the window looked to me:
After all is set up, press Flash. The flashing process will begin. At first Flashtool will prepare files for a flashing. After a while, window will appear which will ask you to connect the phone in the Flashmode mode. Shutdown the phone, hold the Volume Down button, connect the USB cable. Once Flashtool detects the phone in the Flashmode mode, it will start the actual flashing automatically.
After the completion of the flashing procedure after some minutes, you'll get a stock Sony firmware installed, and now it is perfect time to proceed to the next step. You may leave your phone off at this moment, but if you are curious, start it up and check if the new Android is actually there. Note however that first start after the firmware installation takes a long time.
5. REPACKING AND FLASHING A KERNEL
To get the stock firmware rooted, you need a way to install SuperSU. SuperSU is some tool which enables root access to the Android system. To install SuperSU, you need TWRP. To run TWRP, you need a kernel, which supports both TWRP and your Android version.
You can extract the kernel from .ftf file, prepared by Flashtool earlier, repack it and integrate TWRP (and DRM fix) into it, and finally flash it to your phone back modified. Sound like a complex task but it's definitely achievable.
At first you should extract the actual kernel from the .ftf file. Reminder: it's in the C:\Users\<Your Windows Username>\.flashTool\firmwares folder and may be titled E6883_32.2.A.0.305_1299-4828_R4C.ftf or something like this. Open it as an archive (right-click on a file, 7-Zip > Open archive) and extract kernel.sin. It's your phone's packed kernel.
If it is packed, obviously you need to unpack it. Thankfully the almighty Flashtool can do this. Open Flashtool, navigate to the Tools > Sin Editor, select a kernel.sin you've just extracted and press Extract data. As a result, you'll get a kernel.elf file in the directory where your packed kernel was. As you may have guessed, kernel.elf is an unpacked kernel. It can be modified, repacked and flashed back to the phone. Let's do this.
You will need a Stock kernel repack script from @tobias.waldvogel. Here is the original thread. Grab the script there. I used v5.0 and it worked perfectly for .253 and older.
Once the contents of the zip-file are extracted to some directory, copy the kernel.elf there and summon command prompt in this directory (right-click in the empty space of this folder in File Explorer with the Shift button pressed and choose Open command windows here).
In the command line type the following:
Code:
rootkernel.cmd kernel.elf boot.img
You'll get some questions about adding some features/tools to your kernel, feel free to answer "Yes" (type Y) to all of them. Screenshot for your reference:
If all went smoothly, you'll get a repacked kernel, boot.img in the script folder, supercharged with TWRP and DRM fix, and most importantly, which also supports rooting. Now it is time to flash it to your phone.
Turn off your phone and connect it in a Fastboot mode: hold the Volume Up rocker button and connect USB cable. The LED on the phone will turn blue.
Flashing images in this mode is typically done with a fastboot.exe from the Android SDK. Android SDK weighs many gigabytes but thankfully you don't need to download it. Fortunately Flashtool contains fastboot.exe from the SDK. It's in the Flashtool\x10flasher_lib folder. For the brevity of the following steps, copy the newly generated boot.img to this folder. Shift-right-click in the empty space of this folder window and choose Open command window here entry from the context menu. Windows console will appear.
At first try this command:
Code:
fastboot.exe devices
If all is good, there will be one device in the output of this command, just like this:
If not, perhaps there is some driver issue, so head back to the step #1 and make sure the drivers are installed correctly.
If your device is shown correctly, let's flash some files to the phone. Execute the following command to flash the modified kernel:
Code:
fastboot.exe flash boot boot.img
The proper output of this command will be like this:
If you get any errors, the first and more likely reason is that you still have a locked bootloader. Head to the step #3 to verify its state and unlock it if necessary.
If there were no errors, you now just flashed a custom kernel with TWRP recovery and DRM fix. You're almost done! You may plug out the cable from your phone. If you are attentive to the details, you'll notice that now, once your phone is started, its LED turns amber for 2-3 seconds. This is a special signal for those looking to boot into a recovery (TWRP).
Although @tobias.waldvogel claims his script is able to also integrate SuperSU during the kernel repacking, I didn't managed to get this working, so the SuperSU installation is a separate step in my guide. The next step.
6. ROOTING WITH SUPERSU
Now when you have TWRP in place and Marshmallow installed, let's root it. SuperSU distributed in a TWRP-friendly .zip archives, so you should copy one to your microSD card. I used beta version 2.78 SR1 from here. At the time of your reading, there probably will be some newer versions available, try them instead.
Once SuperSU zip-file is copied to your microSD card, reboot to recovery (TWRP). To do this restart or power up your phone and look at the LED. Once it lights amber, press Volume Up rocker button and you'll get into recovery — TWRP 3.0.
To install SuperSU, press Install, go to the /external_sd and select the .zip (in my case SR1-SuperSU-v2.78-SR1-20160915123031.zip). Swipe right to confirm installation. Once it is installed, press Reboot System button. Phone will reboot twice. Do not interfere with the phone during these multiple reboots, the things are getting done right, so just wait once Android is started. Once it's started, the phone is rooted and functional!
7. RESTORE YOUR DRM KEYS
If you had successfully backed up your DRM keys in step #2, it is now time to restore it back to the device. There is a flash_dk.cmd script shipped with the Root kernel repack script you used in the previous step. flash_dk.cmd can be used to flash the DRM partition back to your phone.
At first prepare the flashable .ftf:
Code:
flash_dk.cmd <ta backup image> dk.ftf
And then flash dk.ftf via Flashtool, just like you flashed the whole firmware in the step #4, but don't wipe anything this time.
8. OPTIONAL STEPS
8.1. Xposed installation
Since Z5P uses Lollipop and later, you should install Xposed APK from here. At the time of writing there is XposedInstaller_3.0_alpha4.apk installer there.
Once APK is installed, grab the latest .zip from the repository, I've got xposed-v86-sdk23-arm64.zip. Install it in a regular TWRP way covered in step #6.
Once all these steps are done, you should have Xposed Installer app in your phone, and if you open it and check Framework section, if everything is alright, there will be text in green, something like "Xposed framework version 86 is active".
Installation of actual Xposed modules can be performed in different ways. For example you may install HideSimIcons module from @tobias.waldvogel if you've got dual-SIM Z5P and you're mad at SIM-card icons in the system tray. Get the APK from the original thread and install it just like you install regular APKs.
8.2. Resolving Voice Search and random volume up/down issues while using regular headphones
See this thread.
8.3. Disable startup notification if there is a newer firmware available
Some people get annoyed by a persistent notification, which is displayed once the new firmware become available (new Android version from Sony). Rooted users cannot just tap it and update over-the-air, because they need to perform a complex rooting procedure in beforehand (covered in this guide). It is possible to disable this notification. You may get these notifications by email anyway.
The easiest and safest way is to use some autorun manager. I used Autorun Manager Pro and disabled all receivers of system apps com.sonymobile.fota.service, fota update service and Software update. Notification vanished after a restart.
You may even freeze or remove these apps via some app manager like Titanium Backup Pro.
THAT'S IT
At this point you have a stock Sony Android enhanced with root privileges. SuperSU app is also installed, so you are ready to use root right away. SuperSU now can be updated in a regular way via Play Store.
P.S. WHEN NEW FIRMWARE IS AVAILABLE
Once the new firmware is released, you may perform the same procedure for it beginning from the step #4, but if it is a minor upgrade, you may want not to wipe anything during Flashtool flashing this time. If it is a major upgrade, e.g. Marshmallow > Nougat, you probably may want to start with a clean system and wipe all.
Hello
THX for this guide
ihave this problem
C:\Android\sdk\platform-tools>fastboot.exe flash boot E6883_MM_ROOTABLE_PERMISSIVE_boot.img
target reported max download size of 536870912 bytes
sending 'boot' (15548 KB)...
OKAY [ 0.353s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.384s
---------- Post added at 12:01 PM ---------- Previous post was at 11:59 AM ----------
I dont have this folder with"Flashtool\x10flasher_lib f"
get2easy said:
Hello
THX for this guide
ihave this problem
C:\Android\sdk\platform-tools>fastboot.exe flash boot E6883_MM_ROOTABLE_PERMISSIVE_boot.img
target reported max download size of 536870912 bytes
sending 'boot' (15548 KB)...
OKAY [ 0.353s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.384s
---------- Post added at 12:01 PM ---------- Previous post was at 11:59 AM ----------
I dont have this folder with"Flashtool\x10flasher_lib f"
Click to expand...
Click to collapse
Hello. This seem like a driver problem to me. Or maybe bootloader is locked. Was fastboot driver installed from the Flashtool package? Do you have your bootloader unlocked?
Hy THX for ure answer.
Drivers are installed, but myBL is LOCKED!! Must i have UL BL??
get2easy said:
Hy THX for ure answer.
Drivers are installed, but myBL is LOCKED!! Must i have UL BL??
Click to expand...
Click to collapse
Sure, I've explicitly stated in the preface section of this guide, that you need to unlock your bootloader to get things done.
OK THX. I dont will loose my performance and the quality from the cam. I wait when is available from the Locked BL.
Hey thank you for posting this it helped a lot! But I don't really know what happened after I flashed the custom kernel and TWRP my phone won't recognize the microSD, not even when booting at recovery. Help.
renezada88 said:
Hey thank you for posting this it helped a lot! But I don't really know what happened after I flashed the custom kernel and TWRP my phone won't recognize the microSD, not even when booting at recovery. Help.
Click to expand...
Click to collapse
I heard about this issue with some large microSD cards of sizes >=128 GB. What is your card?
128gb indeed
renezada88 said:
128gb indeed
Click to expand...
Click to collapse
That's probably a kernel issue. You can try to ask support from its creators, but don't expect anything, because this all is a volunteer work.
get2easy said:
OK THX. I dont will loose my performance and the quality from the cam. I wait when is available from the Locked BL.
Click to expand...
Click to collapse
Just updated the guide, adding the last section (P.S.). Check it out, you may be interested.
Fragmentation said:
That's probably a kernel issue. You can try to ask support from its creators, but don't expect anything, because this all is a volunteer work.
Click to expand...
Click to collapse
Solved it! I needed the E6583 kernel not the E6883. Thanks for everything now root is working with that kernel and it reads the microSD.
Fragmentation said:
Just updated the guide, adding the last section (P.S.). Check it out, you may be interested.
Click to expand...
Click to collapse
sir are all the drm protected features restored by the mod????, and my phone is already MM can I proceed to the 3rd step??
renezada88 said:
Solved it! I needed the E6583 kernel not the E6883. Thanks for everything now root is working with that kernel and it reads the microSD.
Click to expand...
Click to collapse
That's good. I will update the guide and explicitly mention, that it is needed to pay attention to what particular model the phone is. There are different kernel options for different models of Z5P.
1dave said:
sir are all the drm protected features restored by the mod????, and my phone is already MM can I proceed to the 3rd step??
Click to expand...
Click to collapse
I think they are all restored, however I applied the mod just yesterday and checked only photo quality in dark conditions. X-Reality is also seems like works properly, but honestly I didn't tested it before and after the mod. So far so good.
If you already have stock MM, proceed to the stage 3 directly. But of course you should have fastboot drivers properly installed, if not, head to the stage one.
Does anybody have some problem with whatsapp notification when the smartphone is wifi connected?
Sometimes I don't receive any message until I enter the application. This does not happen if I am connected via 3g.
Edit: Sometimes I received delayed whatsapp notification even if the smartphone is connected through 3g.
Inviato dal mio E6853 con Tapatalk 2
We needs this! A light for LB users... Someone can port for Z5? ?
http://forum.xda-developers.com/showthread.php?t=3337357
Enviado de meu E6853 usando Tapatalk
Guto ViP said:
We needs this! A light for LB users... Someone can port for Z5? ?
http://forum.xda-developers.com/showthread.php?t=3337357
Enviado de meu E6853 usando Tapatalk
Click to expand...
Click to collapse
1. There is no dm-verity on Z3 Beta MM but we have it
2. Flashing needs working recovery for locked bootloader (it needs root to install recovery!)
Is it possible to make a flashable.zip of twrp? For a pre-rooted stock rom
Black_Focus_X said:
Is it possible to make a flashable.zip of twrp? For a pre-rooted stock rom
Click to expand...
Click to collapse
That'd be great !
Black_Focus_X said:
Is it possible to make a flashable.zip of twrp? For a pre-rooted stock rom
Click to expand...
Click to collapse
If you are talking about the PRFCreator, then no, currently it doesn't work with Marshmallow for some reason. Check the corresponding thread.
Caution when modifying your phone, although you can revert 99% of issues you may come across, be cautious.
I take no credit other than compiling info and making a guide. All credit goes to http://forum.xda-developers.com/member.php?u=4911585 (br3w3r, Chainfire and Princecomsy)
http://forum.xda-developers.com/att-galaxy-s7/how-to/g935a-root-t3410403
Well, root has been achieved on all of the variants. All the information is spread, therefore I will compile it.
It is confirmed working for the G935T/A/ (All firmwares so far) can anyone verify it works for Verizon?
DOWNLOAD LINKS
Complete Package with all needed files ( http://d-h.st/am7i - click the blue download link to avoids the ads. (Credit to billa)
ADB Files http://forum.xda-developers.com/showthread.php?t=2588979
Samsung Device Drivers http://developer.samsung.com/technical-doc/view.do?v=T000000117#none
http://d-h.st/gsDA Modified ODIN
http://d-h.st/lQY8 EngBootIMG
https://download.chainfire.eu/968/SuperSU/SuperSU-v2.74-2-S7QC.zip Chainfire's SuperSU
MAKE SURE TO BACKUP YOUR PHONE, YOU MAY NEED TO FACTORY RESET AFTER FLASHING THE ENGBOOT FILE. ( MAY BE FOR THOSE WHO HAVE DISABLED SYSTEM APPS)
1- Put your device in to download mode ( Power off--- Hold Down arrow + Home + Power button)
2-Open the provided ODIN and where it says "AP" select and open the file "Samsung_G935x_QC_Rooted_BOOT.TAR" -- FLASH it--
3- The phone should now reboot
Installing SuperSU
easiest way to put it for flashing su.
https://www.youtube.com/watch?v=nLvRuzQMPLk
1- make sure you have the adb toolkit installed( place it in the root of the "C:/" drive. Mine is "C:/adb"
2- place the superuser folder you downloaded in to c:/adb and rename it "super" to make things easier
3- open the command prompt. Either search for it or press windows key + r and type in "cmd"
4- once cmd is open, navigate to the "super" folder. To do so type cd c:/ , then type cd adb and finally type cd super
5- type in root.bat
You should now be rooted.
To remove the security warning, use a package disabler like titanium backup and disable SecurityLogAgent
NOTE
For those having lag, heat, and battery drain issues. Try doing this.
I had those issues on PD6.
What I did was, ODIN'd a factory PD8 file and rerooted, then I used KERNEL TOOLKIT and changed to the ONDEMAND Governor, next I increased the CPU(small cores / and large cores) to max FREQUENCY allowed and reduced the min core frequencies to the lowest setting. Be sure to apply settings on boot so they stick.
The phone is very fast now.
I disabled the KNOX packages and tmobile package.
It fixed 95% of my issues, im even running xposed
For anyone that needs the complete firmware from Sammobile:
http://www.sammobile.com/firmwares/database/SM-G935T/
I also attached the root files necessary in the zip file here.
BUT... you also need to unrar it. Stinking forum set the zip limit to 20MB for zip files but it zips to about 23MB.
Rar limit is 8MB but in a rar it was reduced to about 18. So... rar'ed it up, hid it in a zip.
Will this work on PC8? That's the one I'm on.
mrlugo88 said:
Will this work on PC8? That's the one I'm on.
Click to expand...
Click to collapse
No guts, no glory. Try it and let us know. Root hasn't been out but for a couple of hours so it's hard to know for sure. Make a backup with Smart Switch and try it out! My guess is that you shouldn't have any issue.
If anyone has disabled any of their apps, make sure you re-enable them.
If you get stuck at the white T-Mobile screen for longer than 5 minutes then reboot back to stock recovery and factory reset. Sucks... but some of us had to do it. Afterwards, it should boot fine.
By the way... HAPPY INDEPENDENCE DAY!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Binary100100 said:
No guts, no glory. Try it and let us know. Root hasn't been out but for a couple of hours so it's hard to know for sure. Make a backup with Smart Switch and try it out! My guess is that you shouldn't have any issue.
If anyone has disabled any of their apps, make sure you re-enable them.
If you get stuck at the white T-Mobile screen for longer than 5 minutes then reboot back to stock recovery and factory reset. Sucks... but some of us had to do it. Afterwards, it should boot fine.
Click to expand...
Click to collapse
I'm all in. Thanks. Will go for it.
mrlugo88 said:
I'm all in. Thanks. Will go for it.
Click to expand...
Click to collapse
May the root be with you.
Does it work on tmo S7 edge on PD7?
Sent from my SM-G935T using XDA Free mobile app
Do I need a laptop for this. I'm so sorry about my super noobish question. Don't kill me
Lmax579 said:
Does it work on tmo S7 edge on PD7?
Sent from my SM-G935T using XDA Free mobile app
Click to expand...
Click to collapse
It's been confirmed to work.
Chocolatetai said:
Do I need a laptop for this. I'm so sorry about my super noobish question. Don't kill me
Click to expand...
Click to collapse
A Windows machine with administrative rights to install device drivers are required.
Thankyou for your nice reply. I guess I have to wait till my brother gets home
whats the weird icon in the status bar and anybody found lag after they flash the boot file?
Binary100100 said:
No guts, no glory. Try it and let us know. Root hasn't been out but for a couple of hours so it's hard to know for sure. Make a backup with Smart Switch and try it out! My guess is that you shouldn't have any issue.
If anyone has disabled any of their apps, make sure you re-enable them.
If you get stuck at the white T-Mobile screen for longer than 5 minutes then reboot back to stock recovery and factory reset. Sucks... but some of us had to do it. Afterwards, it should boot fine.
By the way... HAPPY INDEPENDENCE DAY!!!
Click to expand...
Click to collapse
How would I boot back to stock recovery?
Sent from my HTC 10 using XDA Free mobile app
That's for compiling the info.
Might be a good idea to add a list of builds it's been confirmed working on.
Lmax579 said:
How would I boot back to stock recovery?
Sent from my HTC 10 using XDA Free mobile app
Click to expand...
Click to collapse
Switch your Samsung Galaxy S7 or S7 edge completely.
Boot into Galaxy S7 recovery mode by pressing and holding Volume Down, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S7 screen flickers and you see a warning sign.
Press Volume Up to continue to the main screen of Recovery mode. Or, press Volume Down if you aren’t sure and want to go back to the normal mode.
That’s just about it!
Read more: http://wccftech.com/how-to-enter-galaxy-s7-recovery-mode/#ixzz4DORIJ3Dx
http://wccftech.com/how-to-enter-galaxy-s7-recovery-mode/
Chocolatetai said:
Do I need a laptop for this. I'm so sorry about my super noobish question. Don't kill me
Click to expand...
Click to collapse
Yes, specifically the root.bat is Windows based, but you could read the .bat and figure out how to do it in linux. Either way, yes.
Worked flawlessly with the guide. Thanks for compiling it
Edit/Update:
I am getting the same lag that others have reported previously. One thing I'm seeing that stands out in logcat is Secure Storage Daemon throwing warnings and then an error "Kernal binary has been changed. Please use the same version of platform/kernel binaries"
uaktags said:
Yes, specifically the root.bat is Windows based, but you could read the .bat and figure out how to do it in linux. Either way, yes.
Worked flawlessly with the guide. Thanks for compiling it
Click to expand...
Click to collapse
So just followed the guide? Do I need anything else? I just follow the guide and download what the guide says? Do I need to turn my phone off? Do I need a specific app on my phone for anything? Sorry for the questions
Chocolatetai said:
So just followed the guide? Do I need anything else? I just follow the guide and download what the guide says? Do I need to turn my phone off? Do I need a specific app on my phone for anything? Sorry for the questions
Click to expand...
Click to collapse
If you follow the guide, you'll have everything you need and there wouldn't be any questions needed.
I guess more specific to ask, where are you getting hung up?
On a windows machine:
Download all the files listed and get them installed
Follow the instructions (boot phone into download mode, put adb folder into c:\, rename the SuperSU folder from the zip archive to "super" for easy access, execute the cd's and then execute root.bat)
uaktags said:
If you follow the guide, you'll have everything you need and there wouldn't be any questions needed.
I guess more specific to ask, where are you getting hung up?
On a windows machine:
Download all the files listed and get them installed
Follow the instructions (boot phone into download mode, put adb folder into c:\, rename the SuperSU folder from the zip archive to "super" for easy access, execute the cd's and then execute root.bat)
Click to expand...
Click to collapse
How would I put my phone in download mode
Chocolatetai said:
How would I put my phone in download mode
Click to expand...
Click to collapse
It's in the guide.
Please just read the guide and understand it before you move forward. Ask what you don't understand from the guide so that the writer could make it more clear if it's needed. But what you just asked is literally written clearly with what to do.
Damn can't wait to do this and install xposed only got another hour left
T-Mobile S7 Edge
Latest Update PD8
Eng Boot - System Custom
Knox 0x0
INTRODUCTION (don't skip it if you want understand what you are reading)
Here we are, as promised.
A guide for beginners who hardly understand all the brief steps described in guides: root Galaxy S5 G-900V, unlock-bootloaders, etc. thanks for everyone who helped me with big patience (jrkruse, Bryanx86, XeCuTioN, youdoofus and all other guys) and who developed the scripts/guides. This guide is to help you keep focusing there
I'll try to be as brief as possible, remembering me when I entered in theis world without knowing this phone, and eager of flashing quickly the desidered ROM. I admit I've spent different days and a bounch bad words around figuring out all the obstacles that appeared time by time: you should know from the beginning that a small variation of the process described here may force you start from zero, loosing an amount of time, and that there are different phone models and also with different chipset, so you need carefully understand which phone you have before learning the process or losing time with wrong experiments, they will not work.
Anyway this guide will help many figuring out different aspects of phone, useful to everyone who is appraching flash the S5, it's a collection of important things I've read arond and experimented myself.
PHONE:
I have a S5 G900V with Toshiba chipset "CID11", and I tested all the following only on this phone, for questions/explanations read this article:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
I'm not going to give any support to other versions, but post me if I forgot something
DEFINITIONS:
PHONE: unfortunately there are a moltitude of Galaxy S5 released, they are dedicated to particular geographic areas and particular service operators, the 900V is created for Verizon brand and it has a native ROM with SIM locked. If you bought one with SIM unlocked (and you may even read under "about" it is a 900F for example! check the right one starting the download mode) and you want root it/upgrade you should consider that the first rom uploaded to begin the following process is Verizion original, and it contains SIM lock: you will not use your phone later till you flash the final desidered rom! Chances are also, if you have like I do a CID11 chipset, the SD card will stop be recognized, and that's a boring thing. EDIT: the SD card will work, it was my phone with the SD gold contacts spoiled, accurately I lift them up and sd worked always later.
CHIPSET: as I know there are two variants around, one with Chipset Sasmung "eMMC" and one with Toshiba "eMMC". Before you start you need to read the file /sys/block/mmcblk0/device/cid under the root path, the first two bytes will be 11 or 15, if you have 15 you're lucky and you may even remove the locked bootloader, if you have 11 there are not solutions yet for unlock, but you can install Marshmellow 6.0.1 (unrooted/without root). To check the file CID I suggest to install xplore from Lonelycatgames (you may find a copy around, google it and download apk, open the folder root, the path /sys/block/mmcblk0/device/ and at file cid push long and use the hex editor.
BOOTLOADER: The Verizon phones accept ROMs only containing their certificate (it's more complex but let's say it's like that), they are called stock ROM (ROMs coming from brend, original, untouched). To load other custom roms you need to unlock the Bootloader to avoid checks on certifications, and this is possible only if you have a CID 15 and only after rooting phone, and unlock bootloader. Then you will you are able to flash TWRP which is a nice console for upload any kind of rom.
Anyway, anyCID, there is a "workaround" called Safestrap that loads a TWRP console instead of the classic Android operative system (OS).. and it happens when you will reboot from its Safestrap applications: the console will load instead of Android on next reboot, and when you will reboot from Safestrap console, itself will restores Android the next boot. It's the only way to load ROMS when your CID is 11, but only very particular releases (read about down); and the way to unlock bootloader on CID15. We're waiting that someone in future will unlock also the CID11..
the "bootloader" or "download mode" can be opened only from phone switched off by pressing VolDwn+Home and when u sure u're pressing them correctly then press power keeping them pressed(!) until u see the bootloader, press then volume up.
"recovery console" or "recovery" is reached from phone switched off in the same way, but pressing Volup+Home (the power) until u see the recovery.
ROM: it's a file containing usually the kernel, the system with main applications (excluded google apps), some scripts (commands) to cancel datas before installing.
GOOGLE APPS: you have to flash them after flashed the rom (if the rom asking explicitly for them because made without (it means it doesn't contain inside any google apps that may be crucial for booting), or.. you have to flash them if you're targeting the final result (the last flash) and you want have apps updated in your "new flashed phone". It's not necessary when u're in process of root phone/unlocking.
FLASH A BOOT IMAGE/package: it's a file used to replace the bootloader, when it's needed, for example if you are upgrading from Lollipop to Marshmellow the bootloader can't stay in lollipop version, the versions should match, be sure to have both compatible already downloaded.
ROOT: it means gain the administrators privileges to edit system files on phone.
TWRP: it's a smart console to manage the phone with full control, allows to change the Android versions and many other things.
RECCOMENDATIONS:
1) have battery on phone around 100%, looks because it seems that at lower values make the phone react sometime unexpectly (power safe) during operations, that means you may loose after a lot time to figure out what problem occured/process skipped.
2) During the flashing, in download mode, the phone may not be charged from USB, and the PC power is much less powerful then the charger, you may see a quite impressive battery draining even when connected to PC, this is why is better to start near 100%.
3) During update, the USB up/downs may use lot of CPU of your PC due to driver recognition, keep then your Windows "clean" for the process, no apps in backgroud which use lot of RAM and CPU (for example browsers with many tabs opened), so the driver detection could be faster, avoid programming interruptions (for example installing apps in root.bat)
NOTICE: any time u'll use Odin you don't need to change its flags/settings (for example auto reboot), leave them as they are. If you uploaded something wrong/not certifed under download mode and the phone refuses that, you need to switch off the phone and restart in download mode again, it's not up to software Odin in your PC; you can leave it opened.
Odin will check the checksum of files that are loaded, so for big rom files you have to be patient and give it time to read all file.
When Odin is open and USB connected, you have to see the phone connected by COM, if it doesn't connect the phone may be bricked or you have to install the latest Samsung drivers (!! **you can't forget installing them if it's the first time using a Samsung device!!)
HOW IT WORKS:
useful to understand how is reached the goal here to prevent bricks, solve easier problems, find yourself an overcome. This root kit targets to install 3 applications on the phone, then use a temporary "bricked" kernel to allow edit system files and root the phone before it loads all Android, then restore the previous kernel working, and it ends by using applications installed before to install Safestrap into boot, to have a TWRP console even if the phone is locked.
As the Safestrap substitute the normal Android boot, if there is any problem on the process (=Safestrap will not boot when it's supposed to boot = you started it from its application) the phone may brick here, because when Safestrap stars it need to restore Android normal usage: if it will hapen the Android won't load again, the phone is bricked, read in that section how to solve it.
The first application, Kingoroot,it's made for allow the root permission into other two applications, it's a supervisor. If you use it gently and its installation succeded ok in the beginning of root.bat it will be enough for do all the job (even if the main Guide author suggest to buy SuperSUme).
Busybox it's a software that allows Safestrap to install, whothout it Safestrap won't work.
Safestrap it's a simple application, that if used in right way (I failed lot of times, but I always recovered my phone) permits to have a powerful console on next reboot.
IMPORTANT:
Whne in process, wait always that the USB drivers finishing detecting phone and become "stable" (CPU and hard disk aren't working, keep check them to be sure, as well the icon of the phone should appear in Windows resouces). You may need to start from zero if u miss this, a really stupid reason to lose time.
FILES YOU NEED:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 as the main old rom, that works as starting point.
OK3_ROOT_V5.exe: set of tools and scripts for rooting.
Find them all in the first post here:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
PROCEDURE:
1) Open OK3_ROOT_V5.exe in one folder, if you use windows with particular language and not latin chars avoid to extract it on desktop, prefer a path like C:\galaxy for example.
2) Switch off phone, remove SIM card and SD, switch on in recovery mode and wipe data system and cache, then boot to bootloader
2) open Odin, open under AP G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 and wait until it finished read file, connect phone USB, be sure phone is recognized, start flashing. Wait until phone boots, wait until it shows the beginning screen.
3) choose english, then wi fi button down, then skip the connetcion and everything else asked, insert any fake name.
4) When setup ends don't activate Wi fi, go to settings, about, press 8 times build number, get the development menu active, go into it and enable usb debug, wait for popup and allow your PC always, then disable the verify usb application installation in the same menu. The driver may set itself again after this, wait some seconds befor go over and be sure the phone is seen by Windows resources, when you see the icon of the phone on Windows file explorer and the CPU is low again it's time to run root.bat, not before! Go into OK3_ROOT folder, run root.bat, a black old DOS window will open (this is not Odin! Not confuse this window and what you read there with Odin messages, please!) and follow the steps you read in this new DOS window..
it will install apps, reboot in download mode and show you a new Odin window, select NK2_kernel.tar and flash it, now put your eyes over DOS window of root.bat, it should recognize your firmware and after some seconds display a full page of ########, if it doesn't something went wrong, you need to go to recovery console, wipe everything, and flash again the main big flash (=start from zero).
If succeed, and you will read it in the DOS window, as the last step, you have to disconnect USB, pull battery, switch phone on in download mode and flash VZW_BOK3_KERNEL_ONLY.tar with Odin
5) After reboot open KingRoot application already installed, Click The Up Arrows a couple of time until you get to Try It and yes click Try It, then on the main circle, go back with arrow and you will have confirm that is rooted. Close Kingroot, open busybox free app, allow the root access, click on install (even if it start scannig) and wait some seconds, when it say it completed close it. Open Safestrap, allow root, click on install, the app will quit itself, open it again and click on install, it will quit again. Now reboot phone by the power key, hen rebooted open again Safestrap and now you'll be finally ready to click on the button "Reboot to recovery". Before doing it be ready to organize the next step, like files for unlocking bootloader or flashing a locked phone to 6.0.1.
END rooting phone procedure.
BRICK/RECOVERY: if it happens during root, before you upload any other ROM, there may be three ways to solve that:
Pull the battery out (it's almost safe) and:
1) Light: go under download mode and flash VZW_BOK3_KERNEL_ONLY.tar, see if the phones later boot up normally.
Chances are, with "dirty" chache data that lead the phone to brick, you can't start the root.bat procedure again succesfully (use root2.bat to avoid the install of the three applications that supposed already installed). Then you may try to:
2) medium: go under recovery console, wipe data and cache, boot fom there to download mode and flash again VZW_BOK3_KERNEL_ONLY.tar.
Or, if still not successful:
3) Strong: go under recovery console, wipe data and cache, boot fom there to download mode and flash flash full G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 (that means start from zero)
SAFESTRAP WORLD:
WARNING: you should follow at the letter the above process above, any difference may result in a fail of Safestrap recovery to open and phone bricked at samsung logo (+custom). If so don't worry, you have just to start the download mode and flash VZW_BPB1_KERNEL_ONLY.tar.md5 again to see the phone working. But chances you probably now have to repeat all the procedure from zero because your phone is "dirty" and Safestrap won't work more, proceed to what I called "strong" reflashing in brick section.
NOTICE: when you reboot to Safestrap, after Samsung logo, you need to wait 5-10 seconds to see Safestrap.
FLASH FIRE METHOD:
You may prefer to use FF (Flash Fire) to flash your room, it is a app (apk) that needs t be installed on phone when the phone works in normal mode, it allows you to create a list of different "orders" to execute exactly one after the other after you give it the final "ok". The app reboot the phone and starting itself to flash. It may be faster then Safestrap, but when I tried once it didn't work for me, it flashed partially and rebooted before it finished, I had a soft brick and I should restart from zero. Probably it was me pretending to flash something wrong, there is only one way to upload 6.0.1 on a CID11 phone and I did only once with Safestrap.
For dealing with FF you need the phone rooted, after you followed the process above you don't need to install Busybox, neither Safestrap, but you need to find and install SuperSUme.apk, which is another "root manager" program as Kingoroot is, but FF doesn't work with Kingoroot.
After loading kingoroot copy the Flashfire apk and SuperSUme in your phone, install both of them, start first SuperSUme, allow the root, and let it remove Kingoroot in its procedure, when it finished launch FF and let him the root as well.
You need to find these two apk, google them, since SUperSUme is available only paying you should know what you are doing. I used these versons and they worked: supersume-6.0.apk, flashfire-0-50-android-apk-download (notice there is 0.52, but I tested 0.50)
PS: if you feel this useful, please thank me pressing the button
For uploading 6.0.1 to my locked phone I folowed this guide:
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
I would just add that having the SD card "not recognized" I simply copied files of ROM and GAPPS into the phone folder accessed by Windows resources. And when I reboot to Safestrap I flashed as last step the GAPPS, nothing more to add.
When you wipe Data you actually don't delete the /sdcard folder, so the ROM files are safe there.
if you accidentally delete files under safestrap you can upload them by adb, but it will be really slow (around 500KB/s), here is the command: adb push /path/to/local/filename.zip /sdcard/filename.zip
You may evaluate to flash also this before GAPPS:
Tethering_Fix_Knox_Removal_Slight_Debloat_V2.zip to remove Knox and useless apps from this ROM
If you need to put your default system language (the ROM is in english) download from google MoreLocale 2, open a DOS windows with the path to the folder of root.bat, activate the developer menu (point N°4 of post above), connect the USB, and type
pm grant jp.co.c_lis.ccl.morelocale android.permission.CHANGE_CONFIGURATION
Do you know any details about the new pf4 modem?
no, Im not that expert, here is just a guide to help people into the process..
thank you for the great guide. I was able to root my phone with the clear instruction.
However, I am running into one trouble.
When my phone is setting up the language and etc, it requires me to insert sim or wifi. I can't skip that step without doing one or the other. When I do turn on the wifi, the phone then upgrades itself to android 5.0 but the root is still there. I am using T-mobile sim card.
Is there a way to get around the check up? I made sure to follow all the steps correctly too.
if u're talking about the first beginning steps, after the first big ROM loaded, yes you can skip. Select wi fi button, but after skip all the rest. I've never had to connect to internet or inserted a sim card for the process.
I connected/inserted sim only after the flash to desidered rom
thewebsiteisdown said:
Do you know any details about the new pf4 modem?
Click to expand...
Click to collapse
What kind of details did you want to know? Mine works fine.
Very informative read, and also put in plain english for people that dont understand the usual processes for root, in layman's terms. But you're forgetting one thing available for locked bl that i found very useful before i unlocked mine, and that is flashfire. I was able to flash roms which could or would not flash through safestrap, through flashfire. Other than that, good job writing this
Bryanx86 said:
Very informative read, and also put in plain english for people that dont understand the usual processes for root, in layman's terms. But you're forgetting one thing available for locked bl that i found very useful before i unlocked mine, and that is flashfire. I was able to flash roms which could or would not flash through safestrap, through flashfire. Other than that, good job writing this
Click to expand...
Click to collapse
I added the FF guide
Hey! Thanks for this great guide! Could you help me understand how the check the file CID if my phone is still unrooted? Is it possible to do it?
nachoalt said:
Hey! Thanks for this great guide! Could you help me understand how the check the file CID if my phone is still unrooted? Is it possible to do it?
Click to expand...
Click to collapse
you didn't read well the first post. Read it back.
Barabba11 said:
INTRODUCTION (don't skip it if you want understand what you are reading)
FILES YOU NEED:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 as the main old rom, that works as starting point.
OK3_ROOT_V5.exe: set of tools and scripts for rooting.
Find them all in the first post here:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Click to expand...
Click to collapse
Seems like the file name for OK3_ROOT_V5.exe changed. They call it GS5_LOLLIROOT.tar.gz now (must unzip twice to get all the files) but I looks like what is needed is in this zipped file.
Might take the plunge tomorrow so wish me luck, and thanks again for the explanation!
By "run root.bat" in point 4 do you mean "3 - Root Process.bat"?
Thanks for clarifications
Barabba11,
Since you seems to have a genuine desire of helping people, (and because I want to have my phone rooted), I want to comment your instructions and also try to find what I did wrong, since my phone is locked in the black “Samsung Galaxy S5” screen when trying to accomplish step 4 (no worries, I have been there before…).
Here I go…
FILES YOU NEED
Samsung Drivers: No comments here, straight forward thing to accomplish.
From the original post Here, under “Installing PB1”:
1. Download G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip and unzip it
Click to expand...
Click to collapse
This is what you get today (161108) if you download and unzip that file:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
From the same previously mentioned post, now under “Rooting Instructions”:
1. Download this zip GS5_LOLLIROOT_BLACKCAT.7z
Click to expand...
Click to collapse
This is what you get today (161108) if you download and unzip that file:
Then, under “crc” folder you will find:
And finally, “System” folder is empty.
At this stage my series of comments:
1. I don’t see anything called OK3_ROOT_V5.exe mentioned in step 4 of your procedure. I assume you’re referring to the zipped file GS5_LOLLIROOT_BLACKCAT.7z but since almost every suggestion here indicates to read thoroughly, I don’t want to miss any detail. Can you please confirm if what you call OK3_ROOT folder is the unzipped GS5_LOLLIROOT_BLACKCAT.7z?
2. I don’t see anything called root.bat in the unzipped folders above, mentioned in the same step 4. Can you confirm which one of the .bat files are you referring to? Is it 1 - Install APK's.bat, 2 - Flash NK2.bat, 3 - Root Process.bat or 4 - Flash PB1.bat?
Since my phone got stuck in the black screen when reaching this point and I had to get back to square 1, I’ll wait for comments.
Warmest regards, it is really appreciated what you do here, it is just my humble opinion that detailed instructions in plain English, with proper file names, punctuation etc, would save this world a lot of time and frustration, leaving you developers more time to deal with the important stuff, I’ll be happy to help rewriting or reviewing anything in this regard.
PD: Not sure if the images are going to appear, I don't see them in the preview. If that's the case, you can check here
This thread is out of date since the rooting method has entirely been changed
Can you please indicate where can I find the updated method? Rgds
I'm sorry for the inconvenience, since they changed the main files I'm disoriented too. If they removed the bat files it means everything is different now, and honestly I'm hearing now about that..
Would know too why they changed the process, it was working, complicated but working, and I still have my phone at unrooted Android 6 waiting for a major update, like root or Android7.. I don't have enough time to experiment something that may appear useless for me later.
Anyway reading the instructions may warn you about different aspects to consider.. and reduce the waste of time if some conditions happened.
Kindly write in this thread they way you proceed and I'll have care to edit the first post reminding it. Thank you
Great thread, need some help still
How do I check my chipset when I don't have root access? I downloaded xplore but I need root access to check the root folder.
go into the xplore settings and change the root inside, I've no-rooted phone and I can see it. In the beginning, it's just a way for them to push you install rooting apps
If I root my S5 900V using this method can I then reflash it with 4.4.2?
Respected Forum Members and Readers,
I am an Android Rooting Enthusiast and I am totally new to this realm of hacking into the device and gaining its full access. I have just known about it through videos on youtube and have myself tried to root my device Samsung Galaxy J7 Pro by following videos not knowing really how the things work in actual and ended up losing original firmware. But since then I have been trying to find how to actually root a system by even reading the Book on Hacking by XDA Developers written by Jason Tyler. I have somewhat came to know the internal working but I am also a bit afraid as to try again to root my device as i really don't know how to do it till now and this time i can really not lose my device. But i still want to gain access of it and explore the infinite advantages of having a rooted device. Plz if anybody can help me walk my way through it.
Rooting a device's Android simply means to add "superuser" ( AKA root ) functionality to Android OS, will say add an Android user with elevated rights ( comparable to Administrator in Windows OS).
Because your phone runs Android 7 ( Nougat ) IMO the most easiest method to root your device's Android: Replace Android's Toybox binary - what is a restricted version by default - by unrestricted Toybox v0.8.5.
jwoegerbauer said:
Rooting a device's Android simply means to add "superuser" ( AKA root ) functionality to Android OS, will say add an Android user with elevated rights ( comparable to Administrator in Windows OS).
Because your phone runs Android 7 ( Nougat ) IMO the most easiest method to root your device's Android: Replace Android's Toybox binary - what is a restricted version by default - by unrestricted Toybox v0.8.5.
Click to expand...
Click to collapse
Thank You So Much for your reply but I am sorry as i might have said i just do not know anything about these technical terms like IMO and how to replace Android's Toybox Binary..., i would be really grateful if you could help me by elaborating a bit more as to what I have to exactly do.. Thank You Again
Arihant0908 said:
Respected Forum Members and Readers,
I am an Android Rooting Enthusiast and I am totally new to this realm of hacking into the device and gaining its full access. I have just known about it through videos on youtube and have myself tried to root my device Samsung Galaxy J7 Pro by following videos not knowing really how the things work in actual and ended up losing original firmware. But since then I have been trying to find how to actually root a system by even reading the Book on Hacking by XDA Developers written by Jason Tyler. I have somewhat came to know the internal working but I am also a bit afraid as to try again to root my device as i really don't know how to do it till now and this time i can really not lose my device. But i still want to gain access of it and explore the infinite advantages of having a rooted device. Plz if anybody can help me walk my way through it.
Click to expand...
Click to collapse
it's very simple, i will try to be less technical but bear with me,
so, rooting is simply gaining access to systems core, by core i mean ability to access, modify and write into system (structure and file).
it is a great responsibility, as a simple stupid move can cause system to crash and may also brick your device.
------------------------------ but, don't worry as we here in XDA are there to help you,
as, the device in question is a Samsung j7 pro, normal rooting methods will not work as Samsung by default make it difficult to root it's phone.
you may refer this article to root your phone click here.
----------------------------- but it's some what technical so, i will explain, what is written there in next post.
so, about what's in the article,
--------------------- first things first, you may cause damage to your device so, just to make sure i will not be responsible for any damage.
let's begin, what i will tell you about?
ODIN (a software by Samsung to flash original firmware {that comes with phone})
TWRP(custom recovery, a tool that is installed (flashed using odin )on phone to flash custom rom)
Some tweaks files like RMM State By-Pass.zip and no-verity-opt-encrypt don't think much about them, they just bypass some restriction set by Samsung so, that rooting is successful. you can flash them through TWRP.
you can get link through the article for all required files so,
Download Samsung driver from here,
install them on your PC
download ODIN from here,
after it, open settings app >> about phone >> software info >> then click build number 5-10 times till you are a developer option appears.
after enabling developer option go to developer option, find it using search bar in settings app, it should be inside about phone section.
inside developer option enable USB debugging and also enable OEM unlock option.
after enabling OEM unlock option -----part 2 below.
this was part one if you got all till now you are good to go,
Connect your USB cable with PC. Switch off your device. Then, enter into Download mode. To do this; press and hold down the Volume Down +Home+ Power buttons and connect your micro USB Cable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Press the Volume Up button to continue when you see the warning message.
Now, connect the Samsung Galaxy J7 Pro mobile to the computer via USB cable.
download and extract odin downloaded earlier.
launch odin by clicking on odin.exe file
After connecting the Samsung device, click on the PDA/PA button to browse/search and get the TWRP from where you saved it on your PC. Also, navigate to “options” and save settings like shown below.
after all this your phone should reboot automatically, and voila you have successfully flashed twrp on your device.
now power off your phone,
boot into twrp by pressing Volume Up + Home+ Power Button
then, it will boot into twrp.
Select Wipe->Advance Wipe->Select Cache Data
Return to Home of TWRP select Install
Select Magisk.zip (you can download magisk from github of magisk or from here )
slide to install.
same process for RMM State By-Pass.zip and no-verity-opt-encrypt install file one by one.
after all the process you should reboot into system.
then download magisk app and now you have root access, enjoy and like the post if you want.
@[email protected]
Thank You for taking pains to elaborate the process. i just want to ask one question are you sure this method won't brick my device this time. Sorry i am being like that because the phone i have mentioned is my mother's so she would be really pissed if it does not go right. And if my device gets stuck in boot loop rather being bricked can it still be recovered...
Arihant0908 said:
@[email protected]
Thank You for taking pains to elaborate the process. i just want to ask one question are you sure this method won't brick my device this time. Sorry i am being like that because the phone i have mentioned is my mother's so she would be really pissed if it does not go right.
Click to expand...
Click to collapse
don't worry bro if you follow every step properly it will not brick, but to be on safe side backup internal storage and app data before starting to root your moms phone.
and if some thing goes wrong i am here for you, generally speaking phones does not brick during magisk installation.
[email protected] said:
and if some thing goes wrong i am here for you, generally speaking phones does not brick during magisk installation.
Click to expand...
Click to collapse
And do have to download rmm and no verity encrypt files or should i leave them.... and how to download their required versions along with the right twrp version
bro first use odin to flash twrp
then use twrp to flash magisk then rmm then no verity encrypt each after other no reboot.
Arihant0908 said:
And do have to download rmm and no verity encrypt files or should i leave them.... and how to download them
Click to expand...
Click to collapse
download from website
Root Samsung Galaxy J7 Pro SM-J730F/FM/GM Pie 9.0 using TWRP and Magisk
Most of the people thought, When mobile get slow, we can rectify this by rooting. Nope. There are plenty of optimizations available without root. Even
www.androidinfotech.com
One last thing, do I require to download Samsung USB Driver even if ODIN is able to detect my device
Arihant0908 said:
One last thing, do I require to download Samsung USB Driver even if ODIN is able to detect my device
Click to expand...
Click to collapse
no and yes, if twrp flashes properly no
else yes
@Arihant0908
take note that in order to root Android by means of Magisk, as recommended / advised by @[email protected], neither ODIN nor TWRP is needed: flashing TWRP in this case - as a necessary prerequisite - is an absolute overkill.
All you need is to install Magisk Root app.
jwoegerbauer said:
@Arihant0908
take note that in order to root Android by means of Magisk, as recommended / advised by @[email protected], neither ODIN nor TWRP is needed: flashing TWRP in this case - as a necessary prerequisite - is an absolute overkill.
All you need is to install Magisk Root app.
Click to expand...
Click to collapse
take note mr./mrs. @jwoegerbauer
if you know anything about magisk then you should know that it is not a one click root tool, you need to flash magisk for you to gain root access.
next, yes you only need to boot twrp but in case of samsung we need custom recovery to fix errors so it's good to have it flashed. odin helps remove complexity, and is safe to use.
i was trying to provide best stable and tested path and don't interfere if you don't know anything about topic, i humble request not to confuse people @jwoegerbauer
[email protected] said:
take note mr./mrs. @jwoegerbauer
if you know anything about magisk then you should know that it is not a one click root tool, you need to flash magisk for you to gain root access.
next, yes you only need to boot twrp but in case of samsung we need custom recovery to fix errors so it's good to have it flashed. odin helps remove complexity, and is safe to use.
i was trying to provide best stable and tested path and don't interfere if you don't know anything about topic, i humble request not to confuse people @jwoegerbauer
Click to expand...
Click to collapse
Ok so... in the end what i have understood is that:
1. I need to have Magisk.zip, RMM and no verity encrypt files on Phone.
2. I need TWRP, odin and android usb driver by samsung for windows 10 installed on pc.
3. I need to first flash TWRP using odin. Boot up my device
4. Then boot to TWRP, wipe cache, and flash Magisk.zip, RMM and no verity one by one as in one thing at a time using TWRP. Boot up and install magisk app.
If i missed something, disordered anything or have any suggestions then plz reply. Thank You
Arihant0908 said:
Ok so... in the end what i have understood is that:
1. I need to have RMM and no verity encrypt files on Phone.
2. I need TWRP, odin and android usb driver by samsung for windows 10 installed on pc.
3. I need to first flash TWRP using odin. Boot up my device
4. Then boot to TWRP, wipe cache, and flash RMM and no verity. Boot up and install magisk app.
If i missed something, disordered anything or have any suggestions then plz reply. Thank You
Click to expand...
Click to collapse
on 4th point first flash magisk zip file download from
https://github.com/topjohnwu/Magisk (click on code and download)
flash magisk zip through TWRP then RMM and no verity encrypt file
then boot
if magisk app is present after booting then no need to download app else download the app from google
[email protected] said:
on 4th point first flash magisk zip file download from
https://github.com/topjohnwu/Magisk (click on code and download)
flash magisk zip through TWRP then RMM and no verity encrypt file
then boot
if magisk app is present after booting then no need to download app else download the app from google
Click to expand...
Click to collapse
which magisk zip do i have to download... magisk, magisk beta, magisk canary
Moreover i am unable to select right TWRP specific to my device on its official page twrp.me . My device Model Number is SM-J730GM.
jwoegerbauer said:
@Arihant0908
take note that in order to root Android by means of Magisk, as recommended / advised by @[email protected], neither ODIN nor TWRP is needed: flashing TWRP in this case - as a necessary prerequisite - is an absolute overkill.
All you need is to install Magisk Root app.
Click to expand...
Click to collapse
Totally agree with this.