Database Users

[Stock][prerooted][D5503] 14.5.A.0.283 from T-Mobile_PL

Hi guys,
I've downloaded with XperiFirm the latest available firmware for T-Mobile Poland - D5503_14.5.A.0.283 and created a prerooted .zip with PRFCreator. This does not have any branding at boot, themes etc., only a few apps that you can remove or disable as per your choice, I didn't remove anything so you can choose yourself.
What's included:
D5503_14.5.A.0.283_T-Mobile_PL
UPDATE-SuperSU-v2.46.zip
Z1C-lockeddualrecovery2.8.20-RELEASE.flashable.zip
You need to have custom recovery to flash it, and please remember to backup your device, you use the file at your own risk.
Download link: https://mega.nz/#!bF0lBbxI!8YfxjyDl7kDrPasOsx8g29UJuF3DZ9S4suYkDl3-fJo
Enjoy!

thank you very much! seems to work very well!!!!

Nice. One question xposed is working with this rom?

At first I was satisfied with this rom, but after few hours I've come across few problems with it.
1. TOO many unnecessary apps mostly due to t-mobile origin
2. NDR Utils did not work for me
3. Recovery option does not work any more - had to flash it again
4. SU did not work since the beginning.
I start to think that KitKat is the best choice for me right now.

As it was already rooted, I removed the unnecessary apps.
NDR Utils, Recovery, SU all worked for me.
I had problems with the wifi connection: it always dropped the connection even with good reception.
I couldn't charge the phone with a USB2.0 port, only with a USB3.0 port.
Now back to KitKat and no problem at all.....waiting for 5.1 ...

@denishome Additional apps are there, but can be disabled, I wrote about it in the first post. NDR Utils, Recovery, SU all should be working. Looks like something went wrong while you were flashing this ROM. Re-flashing should help.
@bodrovics I didn't notice any problems with WiFi, as for charging issue - I've had some problems while charging via docking station, but that's not specific to this ROM, also earlier when using .270 it was the same. It charges but slower than straight via USB and not always to full 100%. Have to look a bit more into it, possible that it's a fault of my docking station.
The only real problem for me is battery drain in Lollipop 5.0 in general. After I updated to this ROM battery life improved over .270, possible that it was due to the fact that I have made full wipe. I didn't do full wipe while upgrading from 4.4.4 to 5.0 for the first time, firmware .270 and battery life was tragic. Now I can reach 24 hours, but it's more or less 60%-70% of what I was getting with 4.4.4 (I do use Stamina Mode).
@oiseau Xposed works, I'm using it. Seems Amplify helps with battery life while we're at Xposed modules
@doenen thank you for your kind words. What are your observations after few days, still no issues?

denishome said:
At first I was satisfied with this rom, but after few hours I've come across few problems with it.
1. TOO many unnecessary apps mostly due to t-mobile origin
2. NDR Utils did not work for me
3. Recovery option does not work any more - had to flash it again
4. SU did not work since the beginning.
I start to think that KitKat is the best choice for me right now.
Click to expand...
Click to collapse
1. Unistall them
2. They work ok
3. It works as always
4. SU working fine.

Ok, now sh*t got really messy
I'm unable to run any sort of recovery. No matter what I do, I can't go into recovery mode. I've tried flashing via fastboot TWRP recovery and still no result.
I've also tried to "install" recovery from the instructions from this link -> http://forum.xda-developers.com/showthread.php?t=2647480 with no luck doe.
any suggestions?

@denishome off the top of my head, what I would do
1. Read the sticky Z1 Compact Resource Thread -|-Rooting-BL Unlocking-Firmware & More...
2. Proceed with flashing stock ROM (FTF file)
3 root the device
4. install Recovery.
5. (optional) flash other pre-rooted ROM if needed.
Maybe you wanted shorter method but this one will surely work.
Just read the sticky before you start, download all needed files to your hard drive, it shouldn't be a problem for you it's not a hard process to follow.

Hey! The ROM was working well for me however I think KitKat is a lot more efficient concerning battery life. Since I find this to be one of the most important aspects of a ROM I switched back to modified stock KitKat.
Xposed, CWM, root, everything was working fine...

ok just to give a little heads up for the future users. If you encounter by any chance same problems as I did, simply update your kernel to be able to go into recovery - for me this worked flawlessly -> [5.0][Kernel Z1C][.283 source][V 3.1] RockZ1L Kernel [29/06/2015]

Hi, just a quick question I don't have any custom recovery installed at the moment since I lost my root when I upgraded to the .270 FW, but would I still be able to flash my phone with the .283 FW via FlashTool?

Can I flash it via Flashtool? (sorry, I'm a beginner to this )

kornelkahh said:
Can I flash it via Flashtool? (sorry, I'm a beginner to this )
Click to expand...
Click to collapse
No, You require a recovery(TWRP) to flash it.

Stock ROMs Factory v6.1 , v8.3 , v8.4 , v8.5 , v8.7, V9.0, V9.2-patch : v21

CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs

I flashed this but I didn't get the custom boot logo.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine

Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.

It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo

mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?

Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )

linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out

linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0

Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.

Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?

detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.

The app downloaded from f-droid worked for me as well, many thanks!

Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.

Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.

Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!

OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install

Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3

mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.

Installing the best ROM nowadays for Defy (+)

Hello everybody I got brand new Motorola Defy+ and I want to have newest version of android on it. I am not familiar with rooting etc and unsure if this is possible theres instruction in videos description on youtube "How to Install Android Nougat on Motorola DEFY+ (Android 7.1.1/CM14.1)" ( I can not post links) If not I am curious what is the safest and easiest way to root the device and if theres available newer system than KitKat for my device
Moreover I wanted to install roehsoft ram expander as the phone got only 512 MB of RAM but test says it has to have compatible kernel from what I remember. Not sure if I have to install new operating system in the first place and then root the phone or the opposite and what kernel it has to have to work properly. As I said before I am not experienced android user its my first device with this system
Thank you in advance ppl peace!

Amazing, Motorola Defy+ is cool in its segment but can this slim hardware keep up with such a bulky Android version?
It's said in KittyKat threads here phone has a tendency to stutter with KK (as such a demanding OS), and how about Nougat?
Anyway it'd be nice if somebody adjust Nougat to work worth Defy+. Especially it is needed to optimize battery consumption in idle.

And about rooting, you can just run apk called FramaRoot and job is done
Afterwards run SndInitDefy_2.3 and you will have custom recovery installed (CWM), it is just as simple as it!
http://cloud.tapatalk.com/s/5965fe184202f/Framaroot-1.9.3.apk
http://cloud.tapatalk.com/s/5965fe43f2a32/SndInitDefy_2.3.apk
Afterwards, make a nandroid backup and, using already installed custom recovery CWM (which is clumsy, without touch support), you may want to flash TWRP. If so then flash defy_twrp_recovery_2.6.3.0.zip, e.g. from this link:
http://d-h.st/users/tejus.k.v
Although attention: this flashes recovery TWRP to the system partition (probably the phone's recovery partition is to small) overwriting the android system which is already there, so after doing this you must flash some ROM.
It is described in the second post of this KittyKat ROM thread: [ROM] [4.4.2] SlimKat (jordan) [STABLE 4.0] [Weekly 3.85] [Unofficial]
And see Installation Instructions section, good luck! ?

pawwaap said:
And about rooting, you can just run apk called FramaRoot and job is done
Afterwards run SndInitDefy_2.3 and you will have custom recovery installed (CWM), it is just as simple as it!
http://cloud.tapatalk.com/s/5965fe184202f/Framaroot-1.9.3.apk
http://cloud.tapatalk.com/s/5965fe43f2a32/SndInitDefy_2.3.apk
Afterwards, make a nandroid backup and, using already installed custom recovery CWM (which is clumsy, without touch support), you may want to flash TWRP. If so then flash defy_twrp_recovery_2.6.3.0.zip, e.g. from this link:
http://d-h.st/users/tejus.k.v
Although attention: this flashes recovery TWRP to the system partition (probably the phone's recovery partition is to small) overwriting the android system which is already there, so after doing this you must flash some ROM.
It is described in the second post of this KittyKat ROM thread: [ROM] [4.4.2] SlimKat (jordan) [STABLE 4.0] [Weekly 3.85] [Unofficial]
And see Installation Instructions section, good luck!
Click to expand...
Click to collapse
Thank you for your help! My phone dont want to turn on anymore. I've done everything carefully up to the following point"Wipe /data, /cache, and /system in TWRP or use defy_safewipe.zip" (after that I wanted to flash this: "Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip" cos its ROM right?), but and when it asked me to slide back to the right blue arrow to confirm, my phone booted up and then died after motorola logo. Green led lighted up before death. It seems that it wasnt safe thing despite the name. What to do now? Can I recovery it?
--
UPDATE: ok its working again :angel:, Ive tried combo "up volume" and "power" buton.
Now Ive got no idea what "Gapps" or "Slimroms addons you want" are, but after mad long startup (with SlimKAT logo on the screen), it seems that this system is working. Its much faster than befo I can see. It's RUNNING! :laugh:
--
UPDATE 2: Play Store refuses to open on this new system after I installed it. "Unfortunately, Google Play Store has stopped."

I have just flashed this ROM:
[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+), it is the most advanced so far as I can see, the freshest release is cm-11-20161124-NIGHTLY-mb52x so half a year old.
If you read instructions on this thread you can see it's installation is somewhat tricky.
It includes rearranging partitions layout and sizes.
If you really want experimenting with flashing Nougat you will probably need the technique to change partitions sizes, and you may edit the values inside the resize.zip according to individual needs (post #5595)
And the half of the links from the first post are empty, however in the middle of the thread there are still working links.
After all it's better to follow this version of installing instructions (post #5584)
Also you can find some files here: http://defy.svolkov.name/quarx2k.ru/
I have done partitions resizing, bootstrap, and managed to flash the first ROM, version: cm11.0-defy-newlife.zip,
however wrongly have done cache & Dalvik reset just after resizing (and before ROM flashing): the result is ROM is working well but cannot boot into recovery anyway (and can't recreate recovery anyway either, even doing:
Code:
cat /sdcard/bootstrap_ext3.img > /dev/block/mmcblk1p1
as suggested in the post: https://forum.xda-developers.com/showpost.php?p=57221743&postcount=6510)
And I'd like have the freshest version, the only way is to flash stock and do everything from a start again. Please if you can, how to flash stock? It is said elsewhere the most critical in it is choosing the right version of sbf file, choosing inappropriate would brick a phone irreversibly! And how to know which one to choose, tutorials here are so convoluted and discussions so chaotic! Afraid of touching anything though!
As far as the ROM itself, although it is the first only cm11.0-defy-newlife.zip it works amazingly well!
It boots quickly, is fast, RAM friendly, nice!
(It has little overclocked processor and this makes using the phone so comfortably, just little overclocked so hardware friendly too!)

pawwaap said:
I have just flashed this ROM:
[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+), it is the most advanced so far as I can see, the freshest release is cm-11-20161124-NIGHTLY-mb52x so half a year old.
If you read instructions on this thread you can see it's installation is somewhat tricky.
It includes rearranging partitions layout and sizes.
If you really want experimenting with flashing Nougat you will probably need the technique to change partitions sizes, and you may edit the values inside the resize.zip according to individual needs (post #5595)
And the half of the links from the first post are empty, however in the middle of the thread there are still working links.
After all it's better to follow this version of installing instructions (post #5584)
Also you can find some files here: http://defy.svolkov.name/quarx2k.ru/
I have done partitions resizing, bootstrap, and managed to flash the first ROM, version: cm11.0-defy-newlife.zip,
however wrongly have done cache & Dalvik reset just after resizing (and before ROM flashing): the result is ROM is working well but cannot boot into recovery anyway (and can't recreate recovery anyway either, even doing:
Code:
cat /sdcard/bootstrap_ext3.img > /dev/block/mmcblk1p1
as suggested in the post: https://forum.xda-developers.com/showpost.php?p=57221743&postcount=6510)
And I'd like have the freshest version, the only way is to flash stock and do everything from a start again. Please if you can, how to flash stock? It is said elsewhere the most critical in it is choosing the right version of sbf file, choosing inappropriate would brick a phone irreversibly! And how to know which one to choose, tutorials here are so convoluted and discussions so chaotic! Afraid of touching anything though!
As far as the ROM itself, although it is the first only cm11.0-defy-newlife.zip it works amazingly well!
It boots quickly, is fast, RAM friendly, nice!
(It has little overclocked processor and this makes using the phone so comfortably, just little overclocked so hardware friendly too!)
Click to expand...
Click to collapse
Again I want to thank you for your response. On the verion of system Ive installed I cant use my camera for video recording because of lack of some codecs it says and I cant watch YouTube. 'Google Services' crashes. The only way I could download some decent apps was from 'Aptoide'. 'Roehsoft Ram Expander' needed Google services so it wont open (ive download 'Kernel audiutor' however I dont have class 10 card yet so I dont know if its good at all). I wont be fighting with this anymore, I am going to try mentioned 'CM11 Android 4.4 for the Defy(+)'.
So I have to go "Recovery" in this secret startup menu before I install it? I mean do I have downgrade my system before instalation of new one? Or just follow the instructions straight from the beggining I dunno. But I dont want any complicated things you know..
--
The links are dead, but Ive found them files:
defy.7z
Now, you metrioned two rom's but which one is less tricky, cm11.0-defy-newlife.zip or cm-11-20161124-NIGHTLY-mb52x.zip?

You know, I have installed cm-11-20161124-NIGHTLY-mb52x.zip at last, after exciting night of attempting flashing any stock ROM and then following the procedure exactly from the first post of "[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+)"
and the updated files: new_bootstrap and resize, found here
It costed many efforts of blindly "trial and error" flashing one by one stock ROMs, until found the one which turned on my phone with anything else than black screen!
And everything it was to have possibility of flashing cm-11-20161124-NIGHTLY-mb52x.zip instead of already running cm11.0-defy-newlife.zip.
And you know what? The version cm11.0-defy-newlife.zip seemed running better than the freshest one!
It was, what is most important: faster!!!
And anything else seems the same (so far)!!!
Is the any rationale behind hustle and bustle of flashing the "NIGHTLY" and exactly for what?
Question of stability which user gets know only after some time?
Anyway the speed is everything in such thin hardware like Defy+ and i can't resist an impression cm11.0-defy-newlife.zip is way faster!
And what's more, you probably can flash cm11.0-defy-newlife.zip without the whole convoluted procedure of resizing partitions! (needs checking, if you want simplest way you had better resize partitions )
In fact this version of ROM is the same as:
Quarx said:
8. Install cm11.0-defy-newlife.zip (It's latest cm11 from 23sep with changes for new table)
Click to expand...
Click to collapse
but cm11.0-defy-newlife.zip was to try if the only resizing procedure itself worked at all (and for users to send feedback).
In fact resizing partitions is needed only for the next ROM versions (of which the freshest is cm-11-20161124-NIGHTLY-mb52x.zip):
"the nightlies AFTER 01 Oct are for the new partition table".
(Aha, cm-11-20161124-NIGHTLY-mb52x.zip probably is odexed, while cm11.0-defy-newlife.zip is deodexed, it needs confirmation)

And if you needed flashing stock and had doubts how, then write, I'd gladly help and share the knowledge painstakingly acquired this night.
It is amazingly simple and safe, there're few simple basic things but if you needed found them by yourself in this forum you would probably get panicked
It is about how simple things people can mess up! ?

pawwaap said:
And if you needed flashing stock and had doubts how, then write, I'd gladly help and share the knowledge painstakingly acquired this night.
It is amazingly simple and safe, there're few simple basic things but if you needed found them by yourself in this forum you would probably get panicked
It is about how simple things people can mess up!
Click to expand...
Click to collapse
Thank you my friend. Ive installed cm11.0-defy-newlife.zip. Its fine because my camera can now record videos but still it cant play it. :crying:
YouTube videos also wont load, however internet is fast and so on.
--
Google Play still dont work, same error. I kinda came to terms with it as I have Aptoide, but I want to use YouTube..

And what do you use to watch YouTube videos? Advise third party apps, e.g. SnapTube etc, instead of YouTube application. In fact forgot installing gapps at all and it makes me happy You only now made me think about it In such thin hardware it is better to have microG (μG) (for apps refusing running without Google Services) and/or Yalp Store for Play Market access
If you insist using bulky Google then try opengapps.org

pawwaap said:
And what do you use to watch YouTube videos? Advise third party apps, e.g. SnapTube etc, instead of YouTube application. In fact forgot installing gapps at all and it makes me happy You only now made me think about it In such thin hardware it is better to have microG (μGl) (for apps refusing running without Google Services) and/or Yalp for Play Market access
Click to expand...
Click to collapse
I guess gapps are apps for new software? Ok so now that I have downloaded SnapTube I still cant play any video. Its loading but wont start just like videos on my phone storage or just recorded
Hah I think its a bit off topic what we made here, I should change name of the tread
--
Ive read on some native forum that after codecs instalation he problem disappeared I try to find some

I have just recorded a video of my dog, sent it via email (AquaMail), received it in a mail to myself and played it with system player, pretty well!
It is possible freshest NIGHTLY ROM has issues solved, how to check it (without Google)?
And can you play videos self recorded with this phone?
OpenGapps.org provides you ability to choose what package, how complex (I always choose "pico"), and for what platform (yes, KittyKat is still supported) you download.

pawwaap said:
I have just recorded a video of my dog, sent it via email (AquaMail), received it in a mail to myself and played it with system player, pretty well!
It is possible freshest NIGHTLY ROM has issues solved, how to check it (without Google)?
And can you play videos self recorded with this phone?
OpenGapps.org provides you ability to choose what package, how complex (I always choose "pico"), and for what platform (yes, KittyKat is still supported) you download.
Click to expand...
Click to collapse
OK its seems that Google Play cant be downloaded straight to the phone (.apk) after installing new system but gapps worked for me and I got my Google Play working again now. Still no luck with videos on YouTube but vlc is working on files Ive recorded.

Tritius46 said:
Ive installed cm11.0-defy-newlife.zip.
Click to expand...
Click to collapse
And how have you installed this ROM: with partitions resizing first or on stock layout?
Tritius46 said:
Hah I think its a bit off topic what we made here, I should change name of the tread
Click to expand...
Click to collapse
Yes, you can change for e.g.
"Installing the best ROM nowadays for Defy (+)"
And it is said Defy and Defy+ is the same hardware, just plus is rebranded and has overclocked processor (to 1GHz) and bit bigger battery, see section "Facts" in [GUIDE] All-in-One Defy Beginner's guide
or "Yielding Defy competitive nowadays"
It is still phone unique on the market, searched something for summer, a little waterresistant phone which could suit to any even tiniest pocket. And found Defy is just the only one in this kind, nowadays producers offer big smartphones and if you want something little & watertight then you can buy modern smartwatch - thanx, prefer Defy: bigger battery, faster, and of incomparable comfort of usage, for peanuts! [emoji106]

pawwaap said:
And how have you installed this ROM: with partitions resizing first or on stock layout?
Click to expand...
Click to collapse
Ive just followed the steps here did exactly what is written step by step from the beggining.
I think now the only is playing videos. Videos I have recorded (on the phone) can be played back only in vlc but still with lags. Same for vids online, however if I choose mobile version of YouTube and try to play stream in vlc it worx but very poor quality. I tried many things without any success, for eg. Flash Fox but the problem is rather in system files than settings and apps itself.
In my custom system I could playback any video.

Tritius46 said:
Ive just followed the steps here did exactly what is written step by step from the beggining.
Click to expand...
Click to collapse
It's irrelevant for video playing but I think it is better to follow the first post from the thread and use the files:
new_bootstrap & resize (instead of PrepareZip_1 & PrepareZip_2),
new_bootstrap has different size than PrepareZip_1 and is newer, something has been changed.
Tritius46 said:
I think now the only is playing videos. Videos I have recorded (on the phone) can be played back only in vlc but still with lags.
Click to expand...
Click to collapse
You see, I play with phone system player any videos recorded with phone system camera application without any problem.
Is the newest NIGHTLY ROM better in the sense the issues have been ultimately repaired?
If so, make android backup of data partition, reboot into TWRP, wipe cache, Dalvik, data (factory reset), and flash the newest NIGHTLY!
(Yet if you enjoy playing with comparing the two system you may wait )
And maybe before flashing next ROM do these newer new_bootstrap.zip & resize.zip flashing (just in case: of avoiding extra issues).
Tritius46 said:
Ive just In my custom system I could playback any video.
Click to expand...
Click to collapse
And in Defy?

pawwaap said:
It's irrelevant for video playing but I think it is better to follow the first post from the thread and use the files:
new_bootstrap & resize (instead of PrepareZip_1 & PrepareZip_2),
new_bootstrap has different size than PrepareZip_1 and is newer, something has been changed.
Sent from my E2303 using Tapatalk
Click to expand...
Click to collapse
OK so I will try now cm-11-20161124-NIGHTLY-mb52x with new_bootstrap and resize. Do I have to just install them like before right? It will replace system I have now?
--
UP:
pawwaap said:
wipe cache, Dalvik, data (factory reset), and flash the newest NIGHTLY!
Click to expand...
Click to collapse
Ok I get it

If so, make nandroid backup of data partition, reboot into TWRP, wipe cache, Dalvik, data (factory reset), and only then (but immediately without rebooting after wiping) do these newer new_bootstrap.zip & resize.zip flashing!
The files you can find here
After flashing NIGHTLY successfully, boot it, follow the initial wizard etc, check if it works ok, and if so reboot into TWRP again to restore your data nandroid backup.
If you don't care about previous data give in with it and configure your Android anew

pawwaap said:
And in Defy?
Click to expand...
Click to collapse
Dont get me wrong, I meant my system version android which came to me with my phone purchase (android 2.3.6 or something dont remember). And its definitely not prob with camera but system video player, plus YouTube dont play too so definitely some playback issue..

Omg omg E:Error executing updater binary in zip '/sdcaed/kitkat 4.4/cm-11-20161124-NIGHTLY-mb52x.zip' 'FAILED' what todo? Reboot and try again?
Maybe file was corrupted

Simple way?

Hi everyone,
So couple of year ago I worked at a start-up company that had an Android project. So I'm not new to flashing images (ROM, Recovery, radio...), and I know most basic tools like ADB (and I'm technical person in my daily life). That being said - I remember the pain when the Radio image doesn't fit the firmware, and you have to play around with stuff to make reception work again. or the Recovery image won't fit the ROM etc etc. I'm not sure if any of this probably still happen TODAY, but back then when I got my LG-G2 - I decided not to touch it. I don't need anything besides the basic options (making calls, taking pictures).
I'm still using Stock with 4.4.2 - and the phone is getting lagy each passing day to the point it's time to root it and install a custom rom.
As I mentioned above, I want it to be quick and painless. Sadly, I don't have the time to do insane amount of research right now, mainly because I have a 3 weeks old born at home - and I prefer to use my free time hanging with it that Q&N issues with my phone
So here's what I need your help with:
1. A recommendation for a tool to save all phone settings. Mostly - App settings, and OS settings (even though I probably not going to go for Stock again, but it doesn't hurt to back it up).
2. An instruction how to flash D802 (there' so many options this days...). My Kernel version is 3.4.0.
3. Recommended ROM to use. Here's what I need from a ROM.
a. I probably want to upgrade to more safe rooted Android version (I can't for example handle permissions on 4.4.2).
b. With that, I don't want to install the latest Android only to figure it's running slowly on LG G2, I want the interface to be snappy (the Stock was snappy for a while).
c. I prefer Minimal ROM if possible with Google Apps installed. If I'll need something, I can install it myself.
d. One of the reason I didn't root up until now, was because people mentioned camera quality is meh with non stock roms. If possible, I will like to have a decent Camera quality.
e. I use my phone as a music player often. So good sound quality is important to me (and maybe even build in Parametrized EQ?).
Thank you!

Reading around the forum would have taken just about the same amount of time than writing your post. A post, mind you, that will get you the same as what you can already find with ease.
You managed to write with your kid around. Last time I checked, browsing takes less effort.
Rant out.

Instead of a rant, here's an actual help for people who might find it useful in the future and lack the time to do some proper research (as it took more than the 5 minutes it took me to write the original post). Please note that I won't take any responsibility for possible damages you may do to your system. Please use at your own risk. Also, note that I only tried it on LG G2 802 with Stock Kit Kat (4.2.2) and other version/OS version might not work.
I wasn't clear to me if 'One Click Root' work with Kit Kat bootloader, so I used 'ioroot'. When your done rooting your phone, you will need to flash a TWRP recovery. The easiest way to do it is by using AutoRec. However, the TWRP recovery installed with AutoRec doesn't have Thermal protection, and is dangerous to use according to the forums. So the next thing will be flashing a new TWRP version from the recovery. Blastgater have tweaked TWRP Recovery for LG devices. You can download the latest version here. It's basically a zip file you flash from within your old TWRP.
Regarding ROM, after doing some research - it looks like Lineage will be the best 'all-around' rom to use. Liveage 15/16 were too slow for my liking, so I went with 14.1 (Android 7.1) which was enough for me and snappy to use. However, the tricky part if your plan on using Lineage, is to flash a bootstack as the one coming with Stock won't work. It's just another zip to flash directly from the recovery and can be found here.
So this is just the high-level process, and I highly suggest checking the specific on the links I sent. It also helps if you know how to handle 'adb' and know the basic stuff like what bootloader and recovery are
Good luck.

Hi all. I'm new to rooting can any one please help and point me to the right tutorial to root a samsung s7

Hi All
Looking for a best tutorial to follow and the right one for my phone really don't want to brick it, obviously :/. as there seems to be a few versions for the S7
I have the following: S7 android 8.0.0 SM-G930F not sure what else I need to know! I'm in the UK so I assume UK phones come with Exynos cpu's
and as far as I am aware android 8 is Oreo! but when they say Stock Rom I assume they mean the same as what came with the phone the original rom?
if so is there an alternative stable rom without the crap included or is it just as simple to delete every thing you don't want now it's rooted! and does that mean if I reset the phone its back to normal with all the crap included! or is there a way to keep it rooted even after reset! and should anything be disabled I.e prepare the phone before attempting to root like any kind of auto encryption that needs disabling and just one more question
if at anytime the rooting process hangs for a ridiculous amount of time when should I throw in the towel! and what are the chances of retrieving the phone back to original state! or does a dirty shutdown brick it?.
I started the root process but failed at first hurdle!, followed instructions install Odin3_v3.13.1 but when I connected the phone nothing showed up in Odin? though I will have another go just to confirm I followed it correctly, I'll update this when it's done.
this was the tutorial I followed:
Easy 4 Newbie [Root Guide]SM-G930F, G935F, G930FD, G935FD (Samsung Galaxy S7 Edge)
Warning ! Please note that the official TWRP for Nougat on Galaxy S7/ S7 Edge is not available yet but based on my experience the Marshmallow version is working on Nougat. By installing a custom recovery on your S7 and S7 Edge and rooting it...
forum.xda-developers.com
I know alot of questions I would really appreciate any help and clarification on the above.
many thanks
Regards
Daz

Look pal, rooting the phone is just like being an adult, it means you will get rid of Samsung's "Child Care".
Yes, UK models use Exynos chip, but you have to be sure, look at your baseband version, if it is G930FXXX, then you are good.
ROMs are in two shapes:
Stock-based: These are just like the one you are using, or other Samsung phones does, like Samsung Experience, One UI, TouchWiz. Maybe MIUI and FlymeOS will come into account, as there are ROMs based on them + Samsung's.
AOSP: These are pure Android ROMs, with few modifications to the core, but keeping the UI as close to the source as possible, Google & OnePlus phones come with a near-to-pure operating systems.
Changing a ROM is not risky, as long as you follow the instructions, without any unaccounted improvising.
Before you install a ROM, read the working and bug list, to make sure you are installing something you have an idea of.
You need to install TWRP recovery (or any other one you like), and format data, in order to be able to travel among ROMs and/or root your device.
Formatting is only required because the phone is forcibly encrypted, and TWRP can not decrypt it, at least not for this device.
Rooting is simply about flashing a 5-MB file, Magisk, then rebooting to system, no need to wipe data.
No need to do any additional steps, unless you are trying to hide root from some apps and/or pass SafetyNet.

Mohamedkam000 said:
Look pal, rooting the phone is just like being an adult, it means you will get rid of Samsung's "Child Care".
Yes, UK models use Exynos chip, but you have to be sure, look at your baseband version, if it is G930FXXX, then you are good.
ROMs are in two shapes:
Stock-based: These are just like the one you are using, or other Samsung phones does, like Samsung Experience, One UI, TouchWiz. Maybe MIUI and FlymeOS will come into account, as there are ROMs based on them + Samsung's.
AOSP: These are pure Android ROMs, with few modifications to the core, but keeping the UI as close to the source as possible, Google & OnePlus phones come with a near-to-pure operating systems.
Changing a ROM is not risky, as long as you follow the instructions, without any unaccounted improvising.
Before you install a ROM, read the working and bug list, to make sure you are installing something you have an idea of.
You need to install TWRP recovery (or any other one you like), and format data, in order to be able to travel among ROMs and/or root your device.
Formatting is only required because the phone is forcibly encrypted, and TWRP can not decrypt it, at least not for this device.
Rooting is simply about flashing a 5-MB file, Magisk, then rebooting to system, no need to wipe data.
No need to do any additional steps, unless you are trying to hide root from some apps and/or pass SafetyNet.
Click to expand...
Click to collapse
Hi Mohamedkam000
Thanks for replying. I'm not confused about why I want to root the phone. I'm just trying to understand the inner workings and the risks as I'm not as clued up with phone OS's as I am windows. I don't care about warrantees or hiding the the fact it's rooted I just want a clean rooted phone free of big brother well inside at least I know you will never completely keep them out but making it hard is a start lol.
Thank you very much for all the above especially on clarifying about the roms and the reason TWRP formats due to encryption nice one
My Baseband version slightly different though it's G930FXXU8ETI3 not sure if having a U instead of a third X makes any difference!
and I posted wrong tutorial I'm actually following this one below again not sure if that matters.
Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )
Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1...
forum.xda-developers.com
Again many thanks for clarifying that lot up very informative and much appreciated.
Kind regards
Daz

CitizenSmith said:
Hi Mohamedkam000
Thanks for replying. I'm not confused about why I want to root the phone. I'm just trying to understand the inner workings and the risks as I'm not as clued up with phone OS's as I am windows. I don't care about warrantees or hiding the the fact it's rooted I just want a clean rooted phone free of big brother well inside at least I know you will never completely keep them out but making it hard is a start lol.
Thank you very much for all the above especially on clarifying about the roms and the reason TWRP formats due to encryption nice one
My Baseband version slightly different though it's G930FXXU8ETI3 not sure if having a U instead of a third X makes any difference!
and I posted wrong tutorial I'm actually following this one below again not sure if that matters.
Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )
Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1...
forum.xda-developers.com
Again many thanks for clarifying that lot up very informative and much appreciated.
Kind regards
Daz
Click to expand...
Click to collapse
It doesn't matter which version of Android you are using, root is the same.
However, on stock ROMs, it might sometimes get rough, as you may end up with Wi-Fi not working (happened to me Q1 2020).
If you really want to learn how Android OS works, then rooting the stock ROM is not your way.
Try AOSP ROMs, preferably start with Oreo ones, you can root in 3 common way, LineageOS SU Add-on, Magisk, Super SU.
But before you tickle your phone, you have to make a backup of your current device, of every partition, EFS is the most important partition, so make sure it is safe.
Baseband version doesn't matter a lot, unless you're paranoid with updates, it is sorted alphabetically, each string on its own.
The phone is more similar to a linux machine than to a Windows PC.
Edit: To root stock ROM, you have to flash dm verity, so you don't end up encrypted again.

Mohamedkam000 said:
It doesn't matter which version of Android you are using, root is the same.
However, on stock ROMs, it might sometimes get rough, as you may end up with Wi-Fi not working (happened to me Q1 2020).
If you really want to learn how Android OS works, then rooting the stock ROM is not your way.
Try AOSP ROMs, preferably start with Oreo ones, you can root in 3 common way, LineageOS SU Add-on, Magisk, Super SU.
But before you tickle your phone, you have to make a backup of your current device, of every partition, EFS is the most important partition, so make sure it is safe.
Baseband version doesn't matter a lot, unless you're paranoid with updates, it is sorted alphabetically, each string on its own.
The phone is more similar to a linux machine than to a Windows PC.
Edit: To root stock ROM, you have to flash dm verity, so you don't end up encrypted again.
Click to expand...
Click to collapse
Thanks again for clearing quite a few things up I thought rooting stock rom would have been far safer way forward wow how wrong was I! but I guess I am just trying to find any kind simile to windows in any way but as you pointed out again it's more like Linux which again I've only played around with ubuntu and mint for a short period so again not to up on Linux lol.
It's funny I was just reading up on AOSP ROMs then got your message. I see they have a stable but not complete! Android 10 not that I would consider it need as I need a stable OS so Oreo is fine for me.
I have backed up phone using Smart Switch on the PC I assume that copy's every thing that's needed, I reset the phone in anticipation all be it prematurely but at least it restored all my data so if anything that was a good test of the back up at least .
I will have look at some AOSP ROMs and see what's involved there, I'll check out their tutorial hopefully it will include the whole process including root.
I gather by your comment using a AOSP ROM you don't need to use dm-verity or will that still be needed!.

The first thing to do is to flash (install) TWRP, it's a custom recovery (think of it as a mini OS that can boot before Android), that will be the base for any of your future tinkering.
Here is the thread, read the FP carefully: [Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
Once TWRP installed, you can do many things:
Install addons like Magisk. Magisk is the tool you use to obtain root. Forget SuperSU, its outdated, and don't works in modern versions of Android.
Install a custom ROM (this subforum is the perfect place to find them).
Backup & restore an image of your current ROM (very useful).

mooms said:
The first thing to do is to flash (install) TWRP, it's a custom recovery (think of it as a mini OS that can boot before Android), that will be the base for any of your future tinkering.
Here is the thread, read the FP carefully: [Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
Once TWRP installed, you can do many things:
Install addons like Magisk. Magisk is the tool you use to obtain root. Forget SuperSU, its outdated, and don't works in modern versions of Android.
Install a custom ROM (this subforum is the perfect place to find them).
Backup & restore an image of your current ROM (very useful).
Click to expand...
Click to collapse
Thanks Mooms for the input
I tried to follow your links tutorial which he gives three options only one is any good to me and that was installing twrp using Odin but I'm having issues at every turn!. I can't even get Odin to recognise my phone it just wont pick it up I have Samsung driver installed and I have reinstalled many times I found an article claim to have a workaround but that was BS just selling some other app I even change the driver as described on there page,
7 Tips to Fix Odin Not Detecting Phone
Are you using Odin flash tool to flash your Samsung phone but it is not recognized by Odin? Here are 7 tips to fix Odin not detecting phone.
www.imyfone.com
.
but that did nothing so reinstall normal driver again.
feels like it's just not meant to be :/
Thanks again.

CitizenSmith said:
Thanks again for clearing quite a few things up I thought rooting stock rom would have been far safer way forward wow how wrong was I! but I guess I am just trying to find any kind simile to windows in any way but as you pointed out again it's more like Linux which again I've only played around with ubuntu and mint for a short period so again not to up on Linux lol.
It's funny I was just reading up on AOSP ROMs then got your message. I see they have a stable but not complete! Android 10 not that I would consider it need as I need a stable OS so Oreo is fine for me.
I have backed up phone using Smart Switch on the PC I assume that copy's every thing that's needed, I reset the phone in anticipation all be it prematurely but at least it restored all my data so if anything that was a good test of the back up at least .
I will have look at some AOSP ROMs and see what's involved there, I'll check out their tutorial hopefully it will include the whole process including root.
I gather by your comment using a AOSP ROM you don't need to use dm-verity or will that still be needed!.
Click to expand...
Click to collapse
AOSP ROMs are pure, you can't say they are not complete. They are complete, and what OEMs do, like Samsung and Xiaomi is just a customization that you can do, too.
It is preferred that when you take a backup, take it with TWRP, just to ensure you backed up phone's partitions, along with "EFS".
The root procedure on Android 6+ is done by patching the Kernel (boot.img), so unless you take backup of that, you cannot keep root.
There are stable custom ROMs, custom ROMs are meant for custom adjustments, however the stability depends on your phone, and the way you use it, you can compare AOSP vs. Stock and see the difference.
AOSP ROMs doesn't need dm verity, well, at least not if the developer did not mention the encryption part.

Mohamedkam000 said:
AOSP ROMs are pure, you can't say they are not complete. They are complete, and what OEMs do, like Samsung and Xiaomi is just a customization that you can do, too.
It is preferred that when you take a backup, take it with TWRP, just to ensure you backed up phone's partitions, along with "EFS".
The root procedure on Android 6+ is done by patching the Kernel (boot.img), so unless you take backup of that, you cannot keep root.
There are stable custom ROMs, custom ROMs are meant for custom adjustments, however the stability depends on your phone, and the way you use it, you can compare AOSP vs. Stock and see the difference.
AOSP ROMs doesn't need dm verity, well, at least not if the developer did not mention the encryption part.
Click to expand...
Click to collapse
Some of the roms I have looked at mention external touch buttons at bottom of phone do not work or something else in the phone I'm just reading their comments.
I understand about the stock & custom rom's now that's not my problem at least not at the moment as I am miles away from choosing a rom! as I can't even get out the starting gate!. I can not get TWRP on my phone as the only way I can see to get it on a unrooted! phone is to use Odin but as I said Odin doesn't work at least not for me it does not see my phone. I would love to take a back up using twrp but that won't happen until I find a way to get TWRP on a unrooted phone. what crazy paradox is this!. you can't root phone without twrp installed and twrp won't install on a unrooted phone!. that makes perfect sense.

CitizenSmith said:
Some of the roms I have looked at mention external touch buttons at bottom of phone do not work or something else in the phone I'm just reading their comments.
I understand about the stock & custom rom's now that's not my problem at least not at the moment as I am miles away from choosing a rom! as I can't even get out the starting gate!. I can not get TWRP on my phone as the only way I can see to get it on a unrooted! phone is to use Odin but as I said Odin doesn't work at least not for me it does not see my phone. I would love to take a back up using twrp but that won't happen until I find a way to get TWRP on a unrooted phone. what crazy paradox is this!. you can't root phone without twrp installed and twrp won't install on a unrooted phone!. that makes perfect sense.
Click to expand...
Click to collapse
Does your phone allow MTP communication? I mean can you transfer files when the phone is turned on?
Does the phone show any notification about a usb connection?
If not, then you have probably a bad USB cable, at least, or you have a hardware issue that can go as deep as a burned charging port.
If yes, then either your USB cable is not as fast as the phone requires, or you haven't installed the Samsung USB Drivers on your PC.
Unfortunately, you cannot root your device without PC, at least not since Lollipop.

CitizenSmith said:
Thanks Mooms for the input
I tried to follow your links tutorial which he gives three options only one is any good to me and that was installing twrp using Odin but I'm having issues at every turn!. I can't even get Odin to recognise my phone it just wont pick it up I have Samsung driver installed and I have reinstalled many times I found an article claim to have a workaround but that was BS just selling some other app I even change the driver as described on there page,
7 Tips to Fix Odin Not Detecting Phone
Are you using Odin flash tool to flash your Samsung phone but it is not recognized by Odin? Here are 7 tips to fix Odin not detecting phone.
www.imyfone.com
.
but that did nothing so reinstall normal driver again.
feels like it's just not meant to be :/
Thanks again.
Click to expand...
Click to collapse
Which version of Odin are you using ?
Use this version (latest): Odin v3.14.4
Which version of the Samsung USB drivers are you using ?
Use this version (latest): https://developer.samsung.com/mobile/android-usb-driver.html

Mohamedkam000 said:
Does your phone allow MTP communication? I mean can you transfer files when the phone is turned on?
Does the phone show any notification about a usb connection?
If not, then you have probably a bad USB cable, at least, or you have a hardware issue that can go as deep as a burned charging port.
If yes, then either your USB cable is not as fast as the phone requires, or you haven't installed the Samsung USB Drivers on your PC.
Unfortunately, you cannot root your device without PC, at least not since Lollipop.
Click to expand...
Click to collapse
Hi
Yes I can transfer files.
Yes phone asks to allow or block file transfer and it ohone shows up in Devices and Drives list and I can access the phone directory and shows up as Samsung s7 icon.
I will try another USB lead but the one I'm using is new and wasn't cheap but still a possibility I have had leads that weren't suitable for other things I was trying so it is worth a try.
Thanks

mooms said:
Which version of Odin are you using ?
Use this version (latest): Odin v3.14.4
Which version of the Samsung USB drivers are you using ?
Use this version (latest): https://developer.samsung.com/mobile/android-usb-driver.html
Click to expand...
Click to collapse
When I downloaded Odin this was latest one Odin3_v3.13.1 though I have doubts that one version update will fix this issue as I did not see many if any people having my issue so they all used Odin and I believe theirs are fine even with older versions! but as I said Mohamedkam it's worth a try I will down load that version and give it a try.
As for the Samsung usb driver I believe that is where I got mine
SAMSUNG_USB_Driver_for_Mobile_Phones no version visible under properties on file version 1.7.23.0.
The USB connection seems to be fine I have uninstalled then re-download and reinstalled a couple of times.
I can transfer files no problem it shows up as Galaxy S7 Icon with card and phone drive inside.
I'll update shortly thank you.
Update:
I just went to try new Odin and whilst checking my phone have seen I have Offical TWRP app installed? I have no clue as to how that's got in there! as Odin did not show phone so I could select nothing!.
In the phone I open app and if i select backup existing recovery it opens and Select Folder tab and under that Selected Folder: /sdcard Filename: Recovery .img and at the bottom of screen Root access required.
I just hope it's installed correctly!. it is showing in playstore my apps as well just to confirm. if this is now installed what should I do next Now not sure what tutorial to start following.
I am just going to try the new odin and see if it picks up the phone back soon.

OK Seem that it now shows up in the new Odin. at least I think it has! in the log window I see this: <ID:0/004> Added!!
I didn't see that before.
Would be grateful if you could tell me how to proceed from here!

Correct, you don't need he latst version of Odin or the Samsung drivers, bit it was just to be sure.
You need to be in download mode, but before, you must have checked OEM unlock & USB debug in developer options (mandatory).
I've written a tutorial with images here (in French):
Samsung Galaxy S7 (edge) - Mangez un Oreo! [Topic Unique] - Page : 487 - Téléphone Android - Technologies Mobiles - FORUM HardWare.fr

mooms said:
Correct, you don't need he latst version of Odin or the Samsung drivers, bit it was just to be sure.
You need to be in download mode, but before, you must have checked OEM unlock & USB debug in developer options (mandatory).
I've written a tutorial with images here (in French):
Samsung Galaxy S7 (edge) - Mangez un Oreo! [Topic Unique] - Page : 487 - Téléphone Android - Technologies Mobiles - FORUM HardWare.fr
Click to expand...
Click to collapse
As I said the older version did not show any kind of data what's so ever and the phone was in download mode. phone displayed "Downloading" which I believe it says that even if it's not doing anything! so a tutorial explained. I think it must have installed the Official TWRP app even though phone did not show up in Odin everything was blank however when I installed the new version of Odin like you suggested it then showed up as <ID:0/004> Added!!. so your suggestion work thanks for that and I did enable OEM unlock & USB debug I did long time ago.
I would check out your tutorial but unfortunately I don't speak French and translating instructions is too risky but thank you for the offer but I'll carry on look around still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.

CitizenSmith said:
As I said the older version did not show any kind of data what's so ever and the phone was in download mode. phone displayed "Downloading" which I believe it says that even if it's not doing anything! so a tutorial explained. I think it must have installed the Official TWRP app even though phone did not show up in Odin everything was blank however when I installed the new version of Odin like you suggested it then showed up as <ID:0/004> Added!!. so your suggestion work thanks for that and I did enable OEM unlock & USB debug I did long time ago.
I would check out your tutorial but unfortunately I don't speak French and translating instructions is too risky but thank you for the offer but I'll carry on look around still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
Click to expand...
Click to collapse
Take a note that, when you flash TWRP, you have to boot immediately to the recovery, so as to enforce its existence, cause I remember they phone has an original recovery backed up somewhere, and gets triggered when you reboot directly to system instead of the unofficial binary.
I advise you to watch guides on YouTube, it's more .. understandable.

CitizenSmith said:
still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
Click to expand...
Click to collapse
I recommend to go with ALEXNDR ROM: zero bugs, everything works perfectly (it's based on stock ROM).
[ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 * Encryption support [Jul-10]
Important notes for Developers / Chefs !!! This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it...
forum.xda-developers.com

Mohamedkam000 said:
Take a note that, when you flash TWRP, you have to boot immediately to the recovery, so as to enforce its existence, cause I remember they phone has an original recovery backed up somewhere, and gets triggered when you reboot directly to system instead of the unofficial binary.
I advise you to watch guides on YouTube, it's more .. understandable.
Click to expand...
Click to collapse
Yer I read that but I've ended up with TWRP installed and did not do that process because I was unaware it installed until it showed up.
As I said I'll just keep looking for now I know I'll find one that works for me from start to finish.
and I've been checking youtube but wouldn't want to use any links their providing but it may help familurise myself with the whole process if i watch enough of them.
Thanks again for your help.

mooms said:
I recommend to go with ALEXNDR ROM: zero bugs, everything works perfectly (it's based on stock ROM).
[ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 * Encryption support [Jul-10]
Important notes for Developers / Chefs !!! This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi Mooms
I will check that out many thanks. I wonder if you could help me here. I am in the middle of the rooting process but have hit a snag. again!
I have now installed TWRP successfully then no-verity-opt-encrypt-3.1 all went fine and I'm at point of flashing Magisk but have an issue when I swipe to flash is gives me a error in red saying "invalid zip file format !"
I downloaded it from github here.
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I click on "code" tab and then "download zip" and I placed that in a download folder on my sd card when I select it I get the above error any ideas as to why I am getting this am I downloaded the correct file?
thanks for any assistance you could give.