How to upload LineageOS to i337 with locked bootloader I337UCSGOK3 and other things.. - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Hello to all forum members. :highfive:
Recently I got into my hands the Samsung S4 SGH-I337 version of AT&T, at least I think so. The current version of Android on it is 5.0.1.
When I set the phone to recovery mode, I think I see the modem version: I337UCSGOK3. Correct me if this is not the modem version, but I am sharing it because I guess this information will be helpful to make alternative software installation.
I've already spent 7 days trying to change the software, reading one by one what I will find about such an update. I tried tons of instructions and they all didn't let me do upload/change somehow software nor even install TWRP.
Tried to upload TWRP (I think I found 6 different files) using different applications from the original Android system - Failed. ie. I used TWRP straight from the system, I also used Flashify. When I use this Flashify app I installed TWRP, but it didn't let my phone go into recovery mode, it just went straight to the download. For me it looks like there is something to not let flash/change this to TWRP.
I tried to upload TWRP via ODIN, it doesn't work, it crashes during installation with error messages.
I also tried to upload lineageos version lineageos.17.1.recovery.img via the normal recovery mode, but every time I try I get an error about the signature not matching.
I tried to upload the software by ADB, I have had connection, I was able to see the phone, but I can only use adb sideload recover.img command and although I tried different images and .zip files, unfortunately nothing works. I think I also get an error that the signature does not match.
Can I ask you for some hints, maybe some instructions that will really work. Many instructions were based on specific versions of the bootloader, is what I called the modem above maybe I named this wrong and this is the bootloader version? If so, does anyone know about the instructions for this version of the bootloader? It seems to me after my problems that it is strangely blocked. Maybe someone knows how to make it work. I would like to change the software to change the system language to Polish. Unfortunately, the apps: MoreLocale2 and Language Enabler and probably about 4 others from the play store are not working.
Of course, the phone is rooted with Kingoroot, the applications detect that there is root, after all, after selecting the Polish language, it does not work in the system.
I would like to change Androind 5.x to LineageOS, because there you can do much more and it works better, more efficiently and saves battery. And I will be able to change language defenetly.
this is not the first time when I do that things. I have changed the regular S4 jfltexx many times, this is not the slightest problem for me.
Summarizing:
1. I would like to change the language to Polish, if it doesn't work or it won't be possible, it's a waste of time or something else
2. I would like to unlock the bootloader and upload TWRP, it can be CWM if anyone knows it will work and has an instruction that I can test
3. Then I would like to upload lineageos.
I'd appreciate any hints to test these things above.
On page:
https://forum.xda-developers.com/showpost.php?p=81418691&postcount=29
I read that it will be possible to upload TWRP, but if it is a special version of TWRP prepared for this phone. Will someone be so nice and tell me if something like this exists and if so, where can I find such TWRP for uploading via ODIN.
Thank yo all for your time spending to read this.:good:
PS: Dear Moderators if this thread is not in proper place please correct this. Thank you.

Those instructions are for another bootloader. Your bootloader is locked, which is why TWRP won't install. There is no way to unlock it or downgrade. You also can't boot AOSP based ROM like Lineage OS. What you can do is root the phone and install touch wiz based ROM like Golden eye ROM by using the flash fire app if you're on lollipop or safe strap recovery if you're on kit kat.

StoneyJSG said:
Those instructions are for another bootloader. Your bootloader is locked, which is why TWRP won't install. There is no way to unlock it or downgrade. You also can't boot AOSP based ROM like Lineage OS. What you can do is root the phone and install touch wiz based ROM like Golden eye ROM by using the flash fire app if you're on lollipop or safe strap recovery if you're on kit kat.
Click to expand...
Click to collapse
Big Thank You for your suggestion and answer on my question.:good:
Right now I have Lolipop installed on the phone so related to this above I can only install something with touchwiz. Hope it will let me to change language to the Polish.
Would you be able to point me some links to instruction, please. I try to find this on forum but failed (getting ROM for nintendo). At least links to the software so I can try using flashfire app. The best it will be instruction, as I have situation in which when I use this app phone want boot after. Maybe it was related to the software, which I shouldn't use or maybe I do this in not proper way.
For everything what I get I'm saying thank you. :highfive:

No problem, I help when I can. The flash fire app you can get from the Google play store I believe, but your phone might need a specific version like the Verizon S4 does I don't know. The touch wiz ROMs are in this forum under Android development, go there and you should see ROMs like golden eye which is a touch wiz based ROM.
Here's a link that might help you, but the S4 is an old phone so it's hard to find links and guides that aren't buried deep in the forum posts.
https://forum.xda-developers.com/ga...guide-to-install-custom-rom-i337-att-t3483736

StoneyJSG said:
No problem, I help when I can. The flash fire app you can get from the Google play store I believe, but your phone might need a specific version like the Verizon S4 does I don't know. The touch wiz ROMs are in this forum under Android development, go there and you should see ROMs like golden eye which is a touch wiz based ROM.
Here's a link that might help you, but the S4 is an old phone so it's hard to find links and guides that aren't buried deep in the forum posts.
https://forum.xda-developers.com/ga...guide-to-install-custom-rom-i337-att-t3483736
Click to expand...
Click to collapse
Let me check this and back with the details what is working.

Alright man, good luck! I may not be able to help much further though, as I now have a Galaxy S10 and my S4 is just my storage phone, but I can try if it's something I know.

Related

[Q] ANNOYING S4!! Help needed

Ok guys, here's the deal. i bought a secondhand s4 which was advertised as a google edition. it has a couple of annoying issues, first i noticed it switching itself off and on. the worst problem with it is that when my battery goes reeeally dead it just bootloops when i have recharged. the only way i can get it back on is to start it in recovery mode (which is clockworkmod v6.0.4.4) then do a factory wipe. so yeah thats a major pain. the s4 itself is a red model and behind the battery it says its a gt-19505, however in the settings on the phone it says its a gt-19505g.
my goal is to install an official firmware if possible that i may be able to update easily, the worry that i have is that i dont know if it would then accept my network as although it appears to run google edition custom firmware it may not once i install something official on it. this may be a nooby statement i know but a noob i am lol.
if its at all possible could i keep the cwm recovery?
and if its any help when i load the other boot loader thingy (with the green android on it) in the top left it says gt-19505, im just sayin cus im sure its vital which ever this phone actually is.
here are as many details as i can give but please ask if im missing anything
ANDROID VERSION 4.4.2
KERNEL VERSION 3.4.0-faux123-KK44-GE-Custom
[email protected]omain #20
Sun Dec 1 02:30:28 CST 2013
BASEBAND VERSION 19505XXUFNA1
BUILD NUMBER KOT49H.S001.131204
also upon booting in the top left it says "kernel is not seandroid enforcing
set warranty bit:kernel"
THANKS FOR YOUR TIME And please tell me where to start as i tried updating it via kies to fix it but it just wont connect, i assume due to custom firmware.
The Google Play Edition S4 devices didn't come in any color but white. Therefore, this is an I9505 with a custom ROM on it. The download mode screen reading GT-I9505 confirmed it.
Since this is an I9505 and not an I9505G, the main question is whether this device will work with your SIM card. For that, simply insert your SIM card and boot the device. If you get signal, you're good. Otherwise you'll have to unlock the device, either by purchasing an unlock code from one of the sites that sells them, or by trying the unlock methods available on the forums.
This will also help answer the question of which stock ROM you can install on the device. If the S4 doesn't prompt you to unlock the device, then you can install one of the unbranded S4 ROMs available on sammobile.com. After that, you can put the recovery of your choice on the S4, though I recommend TWRP over the other options.
Thanks for your help. I'm a little confused though, at the moment with this custom google edition ROM it does take my sim, in fact I bet it takes any sim, I heard that was a feature of google play devices. What I meant was after I install the stock ROM will it then not take my sim. So if it has already been unlocked How would I know which ROM to install? As I now know its not a google edition, is it possible to install an official google edition ROM? Do i use this download mode, Odin, or cwm to install a firmware. I'm just not sure what my starting point is. I don't wanna follow someone's guide yet to installing something just in case I'm jumping the gun and need to uninstall this custom ROM somehow.
Sorry for asking questions that I'm sure seem dumb I'm really just trying to learn at the moment I'm green as they come with android. BTW thanks for your suggestions so far, you def seem like you know what you're talking about, cheers
Google Play devices are carrier unlocked, but this is not a Google Play Edition S4. Therefore the device was carrier unlocked at some point in its past. The unknown here is how the original owner unlocked the device. If he or she used the unlocking methods found on XDA there is a chance the lock will be lost when installing a stock ROM.
If the S4 is unlocked, you aren't restricted to a particular region and can install any I9505 ROM using Odin, though I recommend the carrier unbranded ROMs. You cannot install a stock Google Play Edition ROM on the device as the model number of a GPE device is not the same as the device you have. However, you're already rooted and have a custom recovery installed. In I9505 Development here on XDA there is a Google Play Edition ROM that can be installed on your device. Download it to your S4, wipe everything in recovery, then flash the ROM's flashable zip in recovery. I've used said ROM and it works quite well.
OK I have found the 5.0.1 ge ROM , but in there it says I must use latest recovery or whatever plus it recommended one different to mine, is it safe to install using my version of cwm or do I need to learn how to change it??
Deleted by user
TWRP is recommended as there are people who are still maintaining it, unlike Clockworkmod and Philz. While you probably can get the ROM installed using the version of Clockworkmod you have, learning how to change recoveries is useful.
OK thank you for all your help my friend, I will now find out how to do this, I'm sure there is a section on this somewhere, BTW I think you are right about my device being rooted, but I wanted to check and I followed a guide and used super su but apparently its not rooted so I guess something must've gone wrong. Bit scary if I try to change my recovery or my firmware and this causes a brick hmmmmm
It's virtually impossible to brick the S4, especially as the recovery is flashed through Odin.
Phew that's a relief. Thanks man.... Well I'm gonna just risk using cwm for now as I'm new to this........ Thanks a whole lot for your time I really mean that.
KlLLFRENZY said:
Phew that's a relief. Thanks man.... Well I'm gonna just risk using cwm for now as I'm new to this........ Thanks a whole lot for your time I really mean that.
Click to expand...
Click to collapse
Use TWRP. CMW is outdated.
Lennyz1988 said:
Use TWRP. CMW is outdated.
Click to expand...
Click to collapse
I want to, I really do but I'm struggling here. Before I wrote that last comment I tried to find a guide on this forum for swapping to twrp, but couldn't and didn't wanna bug this guy as he had helped enough. Anyway I went to the place he told me and have hit another wall anyway because I don't know how to use the firmware the relevant kernel or the git. My life is so busy and I'm getting about an hour on this subject a day and its gonna take forever lol
If you can help me on my way even a little its much appreciated, I would like to use twrp and the 5.0.1 ge plus the right kernel of course
KlLLFRENZY said:
I want to, I really do but I'm struggling here. Before I wrote that last comment I tried to find a guide on this forum for swapping to twrp, but couldn't and didn't wanna bug this guy as he had helped enough. Anyway I went to the place he told me and have hit another wall anyway because I don't know how to use the firmware the relevant kernel or the git. My life is so busy and I'm getting about an hour on this subject a day and its gonna take forever lol
If you can help me on my way even a little its much appreciated, I would like to use twrp and the 5.0.1 ge plus the right kernel of course
Click to expand...
Click to collapse
https://twrp.me/devices/samsunggalaxys4internationalqualcomm.html
Follow the Odin guide. It's excactly the same when you flashed CWM.
@Lennyz1988: The S4 was bought secondhand and already had CWM on it from the original owner.
@killfrenzy: Follow the guide Lenny mentioned, but don't worry about the second paragraph. Our device isn't one of those that restores the original recovery on boot.
ok will do, i just tried the app install method but as i suspected, it said root is required for this app and promptly exited so i shall do the odin method, i heard that some people remove root or it could be that it was done wrong. also after reading a few posts here and there i found out that someone had similar issues with their phone random re-booting and they had custom ge with the wrong kernel so it seems once im done my issues should be history if i learn how to install fw + kernel, after this twrp thing i will be one step closer for sure. i also know ppl slate lollipop but once im all done with this im sure i will have picked up enough terminology to install cfw's to my hearts content. hooray for forums and people like you, sounds like im kissin ass but its just gratitude
so using the twrp install guide i gotta install using the odin method i have now got 3.07 odin but this is the next step.........
Odin Install Method (No Root Required):
You will need to download and install Odin on your PC. Once you have Odin installed, download the proper .tar file for your device from the download link above. Power off your device. Turn on your device using the proper key combo to get into download mode and attach the device to your computer via a USB cable. Use the PDA tab or button to browse to and select the tar file that you downloaded and flash the device.
lololol nothins ever simple i see the list of tar files in the link above but no mention at all as to which is the proper .tar for my device, i guess they assume the guide is for people who have done it before. more research tomorrow maybe i gotta be up early ugh
Lennyz1988 said:
https://twrp.me/devices/samsunggalaxys4internationalqualcomm.html
Follow the Odin guide. It's excactly the same when you flashed CWM.
Click to expand...
Click to collapse
Think you misunderstood, I have flashed nothing yet I got it like this. I'm completely green
Don't suppose anybody knows which is the tar file for my device?? S4gt-19505
OK now I get it, the list of tars in that section are all the same just newer builds of the same version. Seems obvious if you have done this before, but I wasn't to know that and cannot assume things. I'm also gonna guess and say Lenny thinks my s4 needs this particular version for an international, am I right?? Anyway it would've made a lot of sense but how does he know. I have no idea what this phone was I have never owned it new.
Different devices have different codes. For example, jfltexx is the I9505. A T-Mobile S4 would be jfltetmo, and so on.The link Lenny provided is for the I9505. Download the 2.8.6.0 version as its the latest.
As to how you were supposed to know, having never owned one, you weren't. There are tutorials in the General forum though that can help.

Need Beginner's Guide, so Custom Rom can be installed

***UPDATE***
Thanks to reply, I have now successfully done everything I set out to do, and created follow-up guide!
You can find it HERE
Original Post below:
Hello Everyone!
I'd like to start off saying I used to have a Nexus 4, with TWRP and Lollipop-based CyanogenMod. I was able to install this all by myself, and keep both TWRP and the ROM updated. I also flashed custom radio to unlock the LTE capability on that phone. My tool of choice to help customize the phone was Nexus Root toolkit.
I was able to follow guides posted long ago on these forums, to do what I wanted with the Nexus 4 back in 2013/2014, but it seems I'm not so capable these days. I've hit such a roadblock with lack of root and constant stutters/slowdowns with everyday use on my current device, the Axon 7, that I must get away from the stock software. I heard it was not so easy with other devices, and while a few devs have posted wonderful guides for users, it's just not enough for a true beginner like me. From skimming guides posted, it seems like devs already expect you to have installed custom recovery, or unlocked bootloader. Then when I try to do these things, so I can move onto custom ROM, it seems the guides are out of date or just not step-by-step enough for me to use, and I don't want to take a risk and brick my device trying things that I'm not sure about. I'm a power user through and through, but not so up-to-date or knowledgeable enough to be able to follow the guides already on the forums. Consider me 1 out of 5 on tech level for Android software.
Here's the model/software already on my device: Stock everything, from bootloader and recovery, to ROM.
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
will my ROM of choice have Daydream VR support? if not what would be needed?
this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through how to use it once installed to help me unlock bootloader/root on another device, Zenphone Zoom if anyone is interested.
PLEASE, don't link me to other guides for any part of this process, if the steps are thorough and relevant, please copy here, of course with all due credit given to original poster.
Feel free to let me know if more info about my knowledge level or device is needed to help you work on my request.
Thanks for reading, here's to several years more of everyone enjoying this wonderful device!
ok there is three real steps, but it can be aheadache, mainly because you didn't unlock before going to nougat.
Step 1. Downgrade to B29 Marshmallow - go here https://www.zteusa.com/axon-7/ and on the support tab in software updates is a full B29 software package. Download it, unzip it once, then put the update.zip file on your SD card.
- on the phone, in developers options, turn on OEM unlocking (it is needed to flash from sd card)
- boot phone to recovery, choose update from sd card, pick the update.zip from the sdcard, the phone will flash the B29 software. It is a bit slow, let it do what it needs to do.
Step 2. Unlock phone and install TWRP - go here https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514 download the miflash program, fastboot unlock program, and twrp for B29.
- instructions are all there, just do what it says.
Step 3, Install LineageOS - https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679 very straight forward. Don't forget to install first the bootloader, then the rom, then gapps.
What makes this so hard is not being easily able to unlock in nougat. Most of us here unlocked way before marshmallow
No need to downgrade to b29.
lafester said:
No need to downgrade to b29.
Click to expand...
Click to collapse
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.
gpz1100 said:
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.
Click to expand...
Click to collapse
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Help needed
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?
kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers
kaiso said:
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?
Click to expand...
Click to collapse
Did you downgrade to Marshmallow B29 first or skip this step?
[email protected] said:
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers
Click to expand...
Click to collapse
I'm praying that someone will compile the information spread about into 3 guides that are model specific so people like us won't rack our heads trying to figure out what on earth to do.
[email protected] said:
Hello Everyone!
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
1with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
2will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
3will my ROM of choice have Daydream VR support? if not what would be needed?
4this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
5NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through
Click to expand...
Click to collapse
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
nolimit78 said:
I'll keep on saying this as much as I need to, I get where you're coming from. There's a lot of data about the correct way of doing things. Best thing to do is read and search. When I got my phone B29 was the new hotness and there was a bunch of older data floating around that I had to sift through. But I did it, I sifted and found my own way and combined two different methods to get my phone rooted and flashed with LOS. Honestly, the trial and error, the searching, the sifting is totally worthwhile because while this device is /DIFFERENT/ compared to methods for HTC and Samsung products, it's not harder. It's better to get yourself properly antiquated to the device you plan on flashing/hacking/rooting because there is /always/ a chance for bricking. Then another thread will be created asking for help to unbrick. Take the time, read now, read everything, understand your device, then push forward.
Click to expand...
Click to collapse
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.
nolimit78 said:
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.
Click to expand...
Click to collapse
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????
KyJelly69 said:
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????
Click to expand...
Click to collapse
Yup.
kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
[email protected] said:
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Click to expand...
Click to collapse
Thank you for the guide, but I managed to get everything done without having to downagrade from Nougat. I was having issues with my Windows variant recognizing my phone after drivers were installed so I used Linux Mint 18.1 and everything went smooth as a whistle. I think the mods should pin your thread post.
I followed the rootjunkie YouTube videos, worked perfectly and the files were all available.
Sent from my ZTE A2017U using Tapatalk

How to unlock the bootloader of the SM-N910F (Samsung Galaxy Note 4)?

Hey guys!
At first, this is my first post here so please be lenient if I posted this in the wrong section or whatever. I still need to get used to this forum.
Second, English is not my native language so it could become some gibberish from time to time. I also have to mention that my Android skills are somewhere between newbie and advanced, so please keep that in mind.
But let's get ahead to my problem:
Some days ago, I decided to install Linage OS 14 on my SM-N910F because I don't like the Stock Android 6.0.1 of it.
As you know, a custom ROM requires an unlocked bootloader an that's where my struggle starts.
I simply can't find any tutorial or similar for my phone. The only one I found didn't work (It was with adb fastboot, the process got stuck at "<wating for device>" after the command "fastboot unlock oem" which was described in the tutorial).
I retried it about three or four times before I gave up. It feels like I searched the entire internet, including this forum, but I couldn't find anything useful.
Maybe it's my fault because I didn't look properly, but yeah, know I'm here to ask directly:
Do you guys have any tricks, tipps, ideas or tutorials for me to try?
If it helps you, my phone is already rooted. (chainfire's CF Autoroot)
It'd make me really, really happy and already thank you for your (hopefully) incoming answers.
Vygravlil said:
Hey guys!
At first, this is my first post here so please be lenient if I posted this in the wrong section or whatever. I still need to get used to this forum.
Second, English is not my native language so it could become some gibberish from time to time. I also have to mention that my Android skills are somewhere between newbie and advanced, so please keep that in mind.
But let's get ahead to my problem:
Some days ago, I decided to install Linage OS 14 on my SM-N910F because I don't like the Stock Android 6.0.1 of it.
As you know, a custom ROM requires an unlocked bootloader an that's where my struggle starts.
I simply can't find any tutorial or similar for my phone. The only one I found didn't work (It was with adb fastboot, the process got stuck at "<wating for device>" after the command "fastboot unlock oem" which was described in the tutorial).
I retried it about three or four times before I gave up. It feels like I searched the entire internet, including this forum, but I couldn't find anything useful.
Maybe it's my fault because I didn't look properly, but yeah, know I'm here to ask directly:
Do you guys have any tricks, tipps, ideas or tutorials for me to try?
If it helps you, my phone is already rooted. (chainfire's CF Autoroot)
It'd make me really, really happy and already thank you for your (hopefully) incoming answers.
Click to expand...
Click to collapse
Pretty certain your bootloader isn't locked, you just need to install twrp with odin and then you are good to flash lineage
sawdoctor said:
Pretty certain your bootloader isn't locked, you just need to install twrp with odin and then you are good to flash lineage
Click to expand...
Click to collapse
Thank you for your fast reply. I'll try it once again, moreover I'll let you know if it worked.
It's me again. Flashing the ROM worked, my phone now runs under Linage OS 14.1. But now I've got another problem: Gapps. Somehow I can't flash the Gapps package, TWRP always tells me that the file is corrupted. I downloaded both the Pico and the Nano package for ARM Android 7.1* devices. Both don't work. I also tried the Android 7.0.* version, but that didn't work ofcourse. (Error 20: Wrong Android version installed on the device.) Is it my fault because I downloaded the wrong packages or what's the issue?
It'd be awesome if you could help me again.
Vygravlil
EDIT:
Okay, now it works. TWRP was right, the file was corrupted. I figured out that my PC kinda messed up the download of the package. I downloaded it with another computer and now everything works fine.

N00b w/ "new SGH-I337 that is running original kernel & 4.2.2 & needs to be updated

N00b w/ "new SGH-I337 that is running original kernel & 4.2.2 & needs to be updated
I am going to apologize from the start. I've read through a lot of threads here and have ended up more confused (and somewhat scared lol). I am a tad more skilled than average when it comes to PCs but I'm a complete mess when it comes to phones!
For various reasons, I like my old ATT Samsung S4 SGH-I337 but am hard on them and need to replace them about every 2 years (I usually wear out the power port among other things). I buy a replacement, copy over my apps, etc, maybe run a minor update and I'm good to go. This time, I bought a "new" open box S4 on Ebay for a great price but when I went to install all my apps, discovered that it was STILL (since it was "brand new") running Android 4.2.2 and the original kernel from the release in 2013! Ok, no big I thought, I will just run the ATT update and I will be good. Nope. Too far out of date and no one at ATT or Samsung is willing to help. I did learn that if I can get 4.4.4 on the phone, then I should be able to update it via ATT to 5.0.1 but I can't even find those files (or at the least any links to them that are still any good!)
Due to life issues, it is critical that I get this phone updated ASAP. Please, can someone spell out step by step in N00b-speak where I can get the needed files and how I update this phone to 5.0.1 or better? I'd really rather not root it if I can avoid it but will do what is needed. I'll buy you a beer (or reasonable beverage of your choice! )
Samsung Galaxy S4 (ATT) SGH_I337
Android 4.2.2
Baseband ver: I337UCUAMDL
Kernel ver: 3.4.0-453947
[email protected]#1
Sat April 27 17:06:05 KST 2013
SilkRoadDog said:
I am going to apologize from the start. I've read through a lot of threads here and have ended up more confused (and somewhat scared lol). I am a tad more skilled than average when it comes to PCs but I'm a complete mess when it comes to phones!
For various reasons, I like my old ATT Samsung S4 SGH-I337 but am hard on them and need to replace them about every 2 years (I usually wear out the power port among other things). I buy a replacement, copy over my apps, etc, maybe run a minor update and I'm good to go. This time, I bought a "new" open box S4 on Ebay for a great price but when I went to install all my apps, discovered that it was STILL (since it was "brand new") running Android 4.2.2 and the original kernel from the release in 2013! Ok, no big I thought, I will just run the ATT update and I will be good. Nope. Too far out of date and no one at ATT or Samsung is willing to help. I did learn that if I can get 4.4.4 on the phone, then I should be able to update it via ATT to 5.0.1 but I can't even find those files (or at the least any links to them that are still any good!)
Due to life issues, it is critical that I get this phone updated ASAP. Please, can someone spell out step by step in N00b-speak where I can get the needed files and how I update this phone to 5.0.1 or better? I'd really rather not root it if I can avoid it but will do what is needed. I'll buy you a beer (or reasonable beverage of your choice! )
Samsung Galaxy S4 (ATT) SGH_I337
Android 4.2.2
Baseband ver: I337UCUAMDL
Kernel ver: 3.4.0-453947
[email protected]#1
Sat April 27 17:06:05 KST 2013
Click to expand...
Click to collapse
I too was lucky enough to snag a S4 off ebay with the original kernel still on it. So with that said....do NOT update your phone! You're on the very special Android 4.2.2 jelly bean MDL bootloader! If you update, you will lose the ability to boot AOSP ROMs and install a custom recovery like TWRP.
AOSP ROMs can take you past Android 5.0.x lollipop and give you Android 6.0.x marshmallow or 7.0.x nougat. You can also boot custom touchwiz ROMs that will take you to Android 5.0.x lollipop. Use the towel root app to root the phone and then freeze any OTA with the titanium backup app. You can also benefit from my guide here:
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
StoneyJSG said:
I too was lucky enough to snag a S4 off ebay with the original kernel still on it. So with that said....do NOT update your phone! You're on the very special Android 4.2.2 jelly bean MDL bootloader! If you update, you will lose the ability to boot AOSP ROMs and install a custom recovery like TWRP.
AOSP ROMs can take you past Android 5.0.x lollipop and give you Android 6.0.x marshmallow or 7.0.x nougat. You can also boot custom touchwiz ROMs that will take you to Android 5.0.x lollipop. Use the towel root app to root the phone and then freeze any OTA with the titanium backup app. You can also benefit from my guide here:
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
Click to expand...
Click to collapse
Thank you for your reply. So I root it, then where do I go from there? How do I know what ROM is what and which one will give me at the least what I had on the old phone (less bloatware would be nice but right now I am so up a creek that I would be ok with stock)? Also, do you have good links to the tools you recommend? One issue I have been having searching here is that the 3-4-year-old posts here have sketchy or dead links.
SilkRoadDog said:
Thank you for your reply. So I root it, then where do I go from there? How do I know what ROM is what and which one will give me at the least what I had on the old phone (less bloatware would be nice but right now I am so up a creek that I would be ok with stock)? Also, do you have good links to the tools you recommend? One issue I have been having searching here is that the 3-4-year-old posts here have sketchy or dead links.
Click to expand...
Click to collapse
No problem, I always try to help when possible. After rooting you can follow my guide to get Loki doki installed. Then you can install a custom recovery like TWRP or clock work mod. My guide gets you clock work mod recovery installed but it's an old version. I use it though and it works fine for me. If you want TWRP recovery, you will have to search the web on how to install it with loki doki.
After a custom recovery is installed you can choose to boot touchwiz based ROMs or AOSP based ROMs like cyanogen mod. Custom touchwiz ROMs will look just like stock only modified (deodex, debloated, etc.) and AOSP ROMs will look like bone stock Android only with added features.
You can find AOSP ROMs in the original Android development forum here in the s4 forums. You can find touchwiz ROMs in Android development which is right under original Android development forum. Sorry, but I don't have any links to tools handy except for the link to my guide which I posted above in my last post. I use golden eye ROM on my s4 which is a stock based touchwiz ROM on Android 5.0 lollipop.
When booting ROMs, be sure that they do not have a bootloader update or else it'll override everything and will patch the loki doki exploit and lock down everything for good.
StoneyJSG said:
No problem, I always try to help when possible. After rooting you can follow my guide to get Loki doki installed. Then you can install a custom recovery like TWRP or clock work mod. My guide gets you clock work mod recovery installed but it's an old version. I use it though and it works fine for me. If you want TWRP recovery, you will have to search the web on how to install it with loki doki.
After a custom recovery is installed you can choose to boot touchwiz based ROMs or AOSP based ROMs like cyanogen mod. Custom touchwiz ROMs will look just like stock only modified (deodex, debloated, etc.) and AOSP ROMs will look like bone stock Android only with added features.
You can find AOSP ROMs in the original Android development forum here in the s4 forums. You can find touchwiz ROMs in Android development which is right under original Android development forum. Sorry, but I don't have any links to tools handy except for the link to my guide which I posted above in my last post. I use golden eye ROM on my s4 which is a stock based touchwiz ROM on Android 5.0 lollipop.
When booting ROMs, be sure that they do not have a bootloader update or else it'll override everything and will patch the loki doki exploit and lock down everything for good.
Click to expand...
Click to collapse
Thank you so much for the reply. While I am very grateful, with all due respect, I understood only about half of it. Here is the deal. I'm an older guy N00b with chronic pain issues under an extreme amount of stress, and my cognitive abilities are not what they should be. There was a step by step guide posted back in 2015 that is what I need but most of the links are bad or sketchy. Like I said above, I really need something along the lines of "go here and here to get this software and put it in "X" place. Then press these keys and do "Y", then press those keys and do "Z". I'm really sorry to be so difficult but I am trying my best to get it.
SilkRoadDog said:
Thank you so much for the reply. While I am very grateful, with all due respect, I understood only about half of it. Here is the deal. I'm an older guy N00b with chronic pain issues under an extreme amount of stress, and my cognitive abilities are not what they should be. There was a step by step guide posted back in 2015 that is what I need but most of the links are bad or sketchy. Like I said above, I really need something along the lines of "go here and here to get this software and put it in "X" place. Then press these keys and do "Y", then press those keys and do "Z". I'm really sorry to be so difficult but I am trying my best to get it.
Click to expand...
Click to collapse
I gotcha, no problem. Okay so what's the status of your phone now? Rooted? Not rooted? To root, goto https://towelroot.com on your phone and click the big red thing in the middle of the page. Make sure you have a Wi-Fi or data connection to the internet, as this will root your phone. Then goto https://galaxys4root.com/galaxy-s4-...tt-or-verizon-galaxy-s4-sgh-i337sch-i545/amp/ to get loki doki installed and clockwork mod recovery. You can also install TWRP recovery instead of clockwork mod recovery, I THINK this is the link: https://galaxys4root.com/galaxy-s4-...rp-on-rooted-galaxy-s4-using-goo-manager/amp/
Galaxys4root.com is a reputable site ran by Mr. HIGH ON ANDROID himself, Xedomax aka Max Lee. The tools you need should be on his site for download and the links shouldn't be dead. He also has a YouTube channel with videos on how to do different things with your phone. My guide I wrote that I linked before, has step by step instructions on how to root and install a custom recovery and how to boot custom ROMs.
StoneyJSG said:
I gotcha, no problem. Okay so what's the status of your phone now? Rooted? Not rooted? To root, goto https://towelroot.com on your phone and click the big red thing in the middle of the page. Make sure you have a Wi-Fi or data connection to the internet, as this will root your phone. Then goto https://galaxys4root.com/galaxy-s4-...tt-or-verizon-galaxy-s4-sgh-i337sch-i545/amp/ to get loki doki installed and clockwork mod recovery. You can also install TWRP recovery instead of clockwork mod recovery, I THINK this is the link: https://galaxys4root.com/galaxy-s4-...rp-on-rooted-galaxy-s4-using-goo-manager/amp/
Galaxys4root.com is a reputable site ran by Mr. HIGH ON ANDROID himself, Xedomax aka Max Lee. The tools you need should be on his site for download and the links shouldn't be dead. He also has a YouTube channel with videos on how to do different things with your phone. My guide I wrote that I linked before, has step by step instructions on how to root and install a custom recovery and how to boot custom ROMs.
Click to expand...
Click to collapse
Ok, It's not rooted yet so I will start down the path laid out. What do you recommend as a source for Touchwiz (wth is that anyway? lol) ROMs? I don't know enough about Android 6.0.x marshmallow or 7.0.x nougat to make the call there but I do want to be able to access the Google apps and play store as before.
SilkRoadDog said:
Ok, It's not rooted yet so I will start down the path laid out. What do you recommend as a source for Touchwiz (wth is that anyway? lol) ROMs? I don't know enough about Android 6.0.x marshmallow or 7.0.x nougat to make the call there but I do want to be able to access the Google apps and play store as before.
Click to expand...
Click to collapse
Your instructions say " Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you." Do I do that before "loki doki installed and clockwork mod recovery."? If so, where is a good source for them? If not, when do I do I install them?
".
StoneyJSG said:
I gotcha, no problem. Okay so what's the status of your phone now? Rooted? Not rooted? To root, goto https://towelroot.com on your phone and click the big red thing in the middle of the page. Make sure you have a Wi-Fi or data connection to the internet, as this will root your phone. Then goto https://galaxys4root.com/galaxy-s4-...tt-or-verizon-galaxy-s4-sgh-i337sch-i545/amp/ to get loki doki installed and clockwork mod recovery. You can also install TWRP recovery instead of clockwork mod recovery, I THINK this is the link: https://galaxys4root.com/galaxy-s4-...rp-on-rooted-galaxy-s4-using-goo-manager/amp/
Galaxys4root.com is a reputable site ran by Mr. HIGH ON ANDROID himself, Xedomax aka Max Lee. The tools you need should be on his site for download and the links shouldn't be dead. He also has a YouTube channel with videos on how to do different things with your phone. My guide I wrote that I linked before, has step by step instructions on how to root and install a custom recovery and how to boot custom ROMs.
Click to expand...
Click to collapse
Ok, forget anything I typed here in the last hour lol. Somehow there were two locals and I was in the wrong one. So far so good. So back to the other question above. " " Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you."" I still need to do that, right? if so, where do I find those apps?
Thank you so much.
SilkRoadDog said:
Ok, It's not rooted yet so I will start down the path laid out. What do you recommend as a source for Touchwiz (wth is that anyway? lol) ROMs? I don't know enough about Android 6.0.x marshmallow or 7.0.x nougat to make the call there but I do want to be able to access the Google apps and play store as before.
Click to expand...
Click to collapse
Touchwiz is the "skin" user interface that Samsung puts on top of Android. It is the stock SAMSUNG rom. Just Google touchwiz then Google stock Android, you'll see a difference. I like touchwiz so I am running a custom ROM called "Golden eye". You can download it from the Android development forum here in the S4 section. Other people like stock Android. The magic of being on the MDL bootloader is that you can boot touchwiz and bone stock Android ROMs. Most custom ROMs both stock Android and touchwiz based will let you access Google apps and the play store.
---------- Post added at 10:36 PM ---------- Previous post was at 10:21 PM ----------
SilkRoadDog said:
Ok, forget anything I typed here in the last hour lol. Somehow there were two locals and I was in the wrong one. So far so good. So back to the other question above. " " Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you."" I still need to do that, right? if so, where do I find those apps?
Thank you so much.
Click to expand...
Click to collapse
You can get all those app except towel root on the play store. Once installed you can use ES file explorer to back them up to apk files then use the my files app that's on ya phone to move them to your SD card for use with your new ROM or keep them where they are since my guide tells you how to keep your data in tact...well for touch wiz ROMs anyway.
StoneyJSG said:
Touchwiz is the "skin" user interface that Samsung puts on top of Android. It is the stock SAMSUNG rom. Just Google touchwiz then Google stock Android, you'll see a difference. I like touchwiz so I am running a custom ROM called "Golden eye". You can download it from the Android development forum here in the S4 section. Other people like stock Android. The magic of being on the MDL bootloader is that you can boot touchwiz and bone stock Android ROMs. Most custom ROMs both stock Android and touchwiz based will let you access Google apps and the play store.
---------- Post added at 10:36 PM ---------- Previous post was at 10:21 PM ----------
You can get all those app except towel root on the play store. Once installed you can use ES file explorer to back them up to apk files then use the my files app that's on ya phone to move them to your SD card for use with your new ROM or keep them where they are since my guide tells you how to keep your data in tact...well for touch wiz ROMs anyway.
Click to expand...
Click to collapse
Since this is a "new" phone and I have nothing to back up yet, do I need to run a backup or can I follow your guide from that point, clean things up and install the ROM of choice?
SilkRoadDog said:
Since this is a "new" phone and I have nothing to back up yet, do I need to run a backup or can I follow your guide from that point, clean things up and install the ROM of choice?
Click to expand...
Click to collapse
It's always good to make a backup in case anything goes wrong with your phone down the road you can get back to where you started without having to flash the MDL stock Rom in ODIN by connecting your phone to your computer. You should though keep a copy of ODIN and the MDL bootloader .tar ODIN file. However, it's entirely optional to make a back up so you could just follow the guide from that point and clean up for a ROM install if you don't want to make a backup.
You can also boot a ROM and then make a backup after you have everything set up. You can back up the stock Rom or any ROM you boot/install. That's the magic of having a custom recovery like TWRP or clock work mod.
StoneyJSG said:
It's always good to make a backup in case anything goes wrong with your phone down the road you can get back to where you started without having to flash the MDL stock Rom in ODIN by connecting your phone to your computer. You should though keep a copy of ODIN and the MDL bootloader .tar ODIN file. However, it's entirely optional to make a back up so you could just follow the guide from that point and clean up for a ROM install if you don't want to make a backup.
You can also boot a ROM and then make a backup after you have everything set up. You can back up the stock Rom or any ROM you boot/install. That's the magic of having a custom recovery like TWRP or clock work mod.
Click to expand...
Click to collapse
Unfortunately, since I already started the install before seeing this, I have no idea what I backed up or where it is. :crying:
First off, I want to thank you so much for the help. I owe you and would like to buy you a beer or the like. I have my phone back now! There were issues with the Golden Eye install (it froze at the Samsung logo for over an hour) and I had to wipe everything and start over then I was able to get it up and running. Is this the right one? https://forum.xda-developers.com/showthread.php?t=2313469
Quick question: Do you know if that ROM supports an external SD card larger than 32gig?
I am having some issues and so far am not thrilled with this ROM and am wondering if it's the right one or if I screwed up. It hasn't been worked on since 2015 and the dev is hasn't been responsive in years. On my phone, it's really buggy. It boots slow, apps hang when loading, a few don't work right, the screen can flash or freeze and TouchWiz keeps crashing like it was doing at the end on my old phone's life. Any ideas as to why?
SilkRoadDog said:
Unfortunately, since I already started the install before seeing this, I have no idea what I backed up or where it is. :crying:
First off, I want to thank you so much for the help. I owe you and would like to buy you a beer or the like. I have my phone back now! There were issues with the Golden Eye install (it froze at the Samsung logo for over an hour) and I had to wipe everything and start over then I was able to get it up and running. Is this the right one? https://forum.xda-developers.com/showthread.php?t=2313469
Quick question: Do you know if that ROM supports an external SD card larger than 32gig?
I am having some issues and so far am not thrilled with this ROM and am wondering if it's the right one or if I screwed up. It hasn't been worked on since 2015 and the dev is hasn't been responsive in years. On my phone, it's really buggy. It boots slow, apps hang when loading, a few don't work right, the screen can flash or freeze and TouchWiz keeps crashing like it was doing at the end on my old phone's life. Any ideas as to why?
Click to expand...
Click to collapse
If you made a nandroid backup with TWRP recovery or clockwork mod recovery, then the backup file will be on your phone SD card or internal memory. Use the my files app to find it. It should be under a folder called TWRP or clockwork mod.
Hey no problem man, I know how it is to goto a forum and have 87,000 people view your post yet nothing is said. Yes that link is the correct link to golden eye ROM. When booting a ROM for the first time it will get stuck at the Samsung logo for awhile, this is normal but it shouldn't be more than 20 minutes. I think the S4 can handle SD cards up to 128GB, it might only be 64GB though.
Very odd golden eye ROM is giving you issues, I have only had one problem with it and that was the text message app acting up every so often. When you booted golden eye did you use the Aroma installer so it just asks you questions and you pick what you want? If not wipe and start over using aroma, it's built into the ROM. Also be sure to tell Aroma you want to use the "imperium kernel". That's the kernel I am using. Golden eye ROM doesn't have a bootloader update in it, so you'll stay on MDL and not have to worry about your phone patching the loki exploit.
I think you can also use the hybrid max kernel, but I don't think it's in the Aroma installer so if you want it you will have to download it from the forums here and flash it separately.
Another thing you can try is just "nuking your phone" as explained in my guide that wipes everything and gives you a nice clean install. The only reason I included the "keep your data" method in my guide is because I just stumbled upon it by doing it on my phone.
If all else fails and as a last ditch effort, you could send the phone to me and I will see if I can get it up and running with golden eye ROM, then send it back. No guarantees though as I'm no developer or anything, just a guy that knows the basics of Android ROMs and root.
Final report. It turns out the problems I've been having were related to the SU Super App. There have been complaints about the recent version. I thought that it was a corrupt install of Golden Eye so got a clean DL from another mirror and was getting ready to start all over. This time I was going to follow the dev's install instructions step by step instead of yours and his. However, I couldn't install TWRP as he instructed. It hung at 100% and never completed. I thought that maybe Super SU was the issue there so I uninstalled it and all of my other problems went away! So happy. Thank you for everything. I do owe you a drink!
SilkRoadDog said:
Final report. It turns out the problems I've been having were related to the SU Super App. There have been complaints about the recent version. I thought that it was a corrupt install of Golden Eye so got a clean DL from another mirror and was getting ready to start all over. This time I was going to follow the dev's install instructions step by step instead of yours and his. However, I couldn't install TWRP as he instructed. It hung at 100% and never completed. I thought that maybe Super SU was the issue there so I uninstalled it and all of my other problems went away! So happy. Thank you for everything. I do owe you a drink!
Click to expand...
Click to collapse
Hey glad it finally worked out for you. You will need superSU though, try a different version of it and that might fix the issue you're having with the latest version. That is unless you have the kingroot super user app, then you can use that but it's not as good as superSU. I had problems with it authorizing my root apps so I got rid of it and installed superSU. No problem glad to help and no thanks needed but if you really wanna buy me a beer go for it lol.

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.

Categories

Resources