Database Users

New to Nexus 7 - root/ROM suggestions?

Hey, I just got a Nexus 7 16GB, yesterday. I'm familiar with CWM, Nandroids, flashing, etc...
I don't have ADB installed and am hoping to get opinions on the toolkits I've seen. Are they a good way to go, to obtain root and get in a position to flash ROMs. And which one would you maybe suggest? I'm running Win XP.
I want to run this kernel: http://www.derkernel.com/jb-seven.php (Trinity Seven)
I'd like suggestions on which ROM to run. Something stable, barebones and running 4.2. AOKP would be nice.
Thanks for hearing me out. Excited to get off of stock. :good:

T679noob said:
Hey, I just got a Nexus 7 16GB, yesterday. I'm familiar with CWM, Nandroids, flashing, etc...
I don't have ADB installed and am hoping to get opinions on the toolkits I've seen. Are they a good way to go, to obtain root and get in a position to flash ROMs. And which one would you maybe suggest? I'm running Win XP.
I want to run this kernel: http://www.derkernel.com/jb-seven.php (Trinity Seven)
I'd like suggestions on which ROM to run. Something stable, barebones and running 4.2. AOKP would be nice.
Thanks for hearing me out. Excited to get off of stock. :good:
Click to expand...
Click to collapse
If you are already familiar with CWM, flashing, etc., then don't use a toolkit. You don't need one. Use adb and fastboot to unlock the bootloader, flash a custom recovery of your choice and the superuser zip you prefer. You could do it in a few minutes. There are multiple guides if you require assistance. It's a Nexus, so there are no tricks - it's simple and straightforward.
Once you get the custom recovery installed, you can then flash your kernel.
I prefer stock on mine. I've had a 16GB, 32GB and now I have a 32/3G. While I do replace boot/kernel with more enhanced ones, I prefer the stock image. But if you want to try out various ROMs, that's up to you and your preferences. Just make sure it's 4.2 compliant.
Congrats, the N7 is awesome.

phonic said:
If you are already familiar with CWM, flashing, etc., then don't use a toolkit. You don't need one. Use adb and fastboot to unlock the bootloader, flash a custom recovery of your choice and the superuser zip you prefer. You could do it in a few minutes. There are multiple guides if you require assistance. It's a Nexus, so there are no tricks - it's simple and straightforward.
Once you get the custom recovery installed, you can then flash your kernel.
I prefer stock on mine. I've had a 16GB, 32GB and now I have a 32/3G. While I do replace boot/kernel with more enhanced ones, I prefer the stock image. But if you want to try out various ROMs, that's up to you and your preferences. Just make sure it's 4.2 compliant.
Congrats, the N7 is awesome.
Click to expand...
Click to collapse
Well, I can't even get the USB drivers to work lmao off to bed. Frustrated and delirious =D
I used http://www.ibtimes.co.uk/articles/4...ndroid42-jop40c-jellybean-ota-cwmrecovery.htm as a guide, but really have no idea what to do with these drivers. Toolkit isn't even working right to install them.

T679noob said:
Well, I can't even get the USB drivers to work lmao off to bed. Frustrated and delirious =D
I used http://www.ibtimes.co.uk/articles/4...ndroid42-jop40c-jellybean-ota-cwmrecovery.htm as a guide, but really have no idea what to do with these drivers. Toolkit isn't even working right to install them.
Click to expand...
Click to collapse
What operating system and version are you on

nba1341 said:
What operating system and version are you on
Click to expand...
Click to collapse
Windows XP 2002 Service Pack 3
If you mean Android, it's 4.2 (JOP40C)

Whenever I choose the folder containing the drivers, when trying to update in device manager, it won't let me select the folder.

OK so I got the drivers installed. Appears it wasn't working because I had the floppy drive checked. Now I still don't see the device in My Computer and I have the yellow exclamation point on MTP, in device manager. I read that you need WMP 11, which I have. Not sure where to go from here.

T679noob said:
Whenever I choose the folder containing the drivers, when trying to update in device manager, it won't let me select the folder.
Click to expand...
Click to collapse
Try PDAnet for drivers also make sure usb debuging is enable on the nexus

flicnflack said:
Try PDAnet for drivers also make sure usb debuging is enable on the nexus
Click to expand...
Click to collapse
I was actually just getting on to say that turning OFF usb debugging now shows my device in my computer

Now I can't get ADB to work. This is a little ridiculous. Gonna change to a Win 7 PC, I guess.

I would strongly suggest you spend a week just using the device before you consider putting a new rom on it.
You will have no basis for comparison unless you know what you are starting with.

rmm200 said:
I would strongly suggest you spend a week just using the device before you consider putting a new rom on it.
You will have no basis for comparison unless you know what you are starting with.
Click to expand...
Click to collapse
Yeah, I'm actually going to stay on stock for the time being, but I want to flash the OC kernel. Noticing a little more game lag than expected.

T679noob said:
Windows XP 2002 Service Pack 3
If you mean Android, it's 4.2 (JOP40C)
Click to expand...
Click to collapse
I can never understand why someone with the latest gadget would insist on trying to make it work on such an antiquated PC.:silly:

Miami_Son said:
I can never understand why someone with the latest gadget would insist on trying to make it work on such an antiquated PC.:silly:
Click to expand...
Click to collapse
While I personally run Linux on most of my computers, I honestly prefer to use WinXP if I need to run Windows.
First, I like the GUI. It's straight, simple and to the point. It's also widely considered to be Microsoft's best OS. The corporate market continues to use it a lot, and went ballistic when MS decided to end-of-life it. Also, on the rare occasions when I use Windows personally, it's usually because I need to run some app or connect to some device that is picky. And when that happens, I've found XP to be the most supported version around. In fact, I run it in a VM because a DVR system we use at the front gate of our HOA, which requires some specialized software, won't run on Vista or 7.
And in regards to the Android SDK, I imagine it's much easier to get running on that platform as well.

I'm unlocked, rooted, with a custom recovery. Thanks to anyone who had input.

Miami_Son said:
I can never understand why someone with the latest gadget would insist on trying to make it work on such an antiquated PC.:silly:
Click to expand...
Click to collapse
Thanks for your help. I dunno what I'd do without you.

phonic said:
It's also widely considered to be Microsoft's best OS.
Click to expand...
Click to collapse
By whom? I've been using W7 since Beta and RC1 and have had few issues with it (Vista is another story). On the rare occasion something won't run on it there is compatibility mode. The point of my post was that if you insist on using an OS that is now 3 iterations behind the most current version and you are having an issue with a newer device that wasn't really designed for that OS, then expect to have issues with driver support, compatibility and general operation. I just thought it was interesting (funny, actually) that in a forum where so many members are hell-bent on getting the latest greatest version of Android on their devices someone would still be using XP on their PC.:silly:

[Q] Help unrooting phone

okay well i rooted my phone a while ago with motochopper and yesterday i tried to download the cyanogenmod from the rom manager and it downloaded but once it rebooted it wen into a boot loop of the cyanogenmod logo so i tried to to restore from the factory clockworkmod backup and it wont restore back. im on a mac so what can i do i got the phone back to the original samsung software but its now stuck on the ATT logo. also it will load all the way up to a new setup but then the setting stop working and i cant go any further. can anyone lead me in the right direction

In the future, don't use rom manager for anything other than getting a custom recovery on your phone. I've seen more people cause problems on their phone using it. Search for heimdal. It is similar to odin for putting stock recoveries on your phone using a Mac. I've never used it so can't be of much additional help.

i tried using hemdall to put a stock tar file on the phone and it still wont restore. its stuck on the custom driver and i dint know what to do

jb0322 said:
i tried using hemdall to put a stock tar file on the phone and it still wont restore. its stuck on the custom driver and i dint know what to do
Click to expand...
Click to collapse
Ate you sure the rom you got from rom manager was for your specific device?

i mean it was the latest CM 10.2 idk if that had anyting to do with it

jb0322 said:
i mean it was the latest CM 10.2 idk if that had anyting to do with it
Click to expand...
Click to collapse
The thing I don't like about rom manager is it's too easy to grab a Rom that is not for your phone. I'm guessing that's what you did and you've messed up the partitions on it. I hate to say it, but I think jtag is your option at this point. Look up mobiltechvideos.com.
There are also some pit files floating around here, but they scare me and can do more harm than good.

Hi! jb0322
I use a Mac (a couple of them, actually) and found that heimdal can be made to work, but it just is not as user friendly as Odin. (Btw, you should not need a custom driver to use Heimdal -its a mac and should see your phone w/o driver issues!)
Maybe it's just my experience, but sometimes when you have everything set up correctly, Heimdal still seems to choke, or just not complete the task (or see the tar file that you want to use!). The newer versions seem better, but I have not found it particularly easy to use. [Also, are you using a current version of Heimdal? Heimdal front end package? Here is a Heimdal link in case you want to check: http://www.glassechidna.com.au/products/heimdall/ . Please check your file -the stock image or rom image that you want to load and make sure it's the right one and also that its in a form Heimdal can use. . .
Conversely, Odin seems to work great -especially (or even) the older versions. This is why I think you could save yourself tons of time and open your options up significantly if you can either: (1) use bootcamp and boot into a windows OS, or (2) use Parallels/VM Ware Fusion and use windows in a virtual window.
Bootcamp is 100% windows running on your mac and is rock-solid, while the VM machine approach also is mature and pretty good, if occasionally temperamental...:good:
If you can do this, then you can use Odin and work to restore you phone with all the tools that most folks here have and use to good effect.
Agree with the advice on being real careful on using Rom Manager, it works, but also seems to have a knack for surprising you with a bad outcome when least expected.
Good Luck!
---------- Post added at 09:45 AM ---------- Previous post was at 09:27 AM ----------
Here is another very good, informative thread right here on this forum sharing someone's experience restoring his i337 using Heimdal!
it might be helpful (and it is just a few posts down from yours
http://forum.xda-developers.com/showthread.php?t=2374441

jd1639 said:
In the future, don't use rom manager for anything other than getting a custom recovery on your phone. I've seen more people cause problems on their phone using it. Search for heimdal. It is similar to odin for putting stock recoveries on your phone using a Mac. I've never used it so can't be of much additional help.
Click to expand...
Click to collapse
I have read so many posts of people using Rom Manager/Goo Manager and soft bricking their devices with it by just trying to install custom recoveries...I wouldn't touch either.
There are tools available to automatically install custom recoveries...seems much more stable and safe, especially for rookies.
This one is my favorite - lets you pick OUDHS auto-loki CWM or TWRP:
http://forum.xda-developers.com/showthread.php?t=2297033&highlight=oudhs

[Q] Bricked my SGH-I337... things I have tried to so far

Been searching and trying various things to fix my bricked phone. For some background of what initially went wrong.
I had the phone rooted following these steps.
http://forum.xda-developers.com/galaxy-s4-att/general/how-to-root-i337ucufni1-t2881298
and then also had installed safetrap. I then wanted to use a custom rom http://forum.xda-developers.com/showthread.php?t=2616221 from here so I booted into safetrap recovery. (Was running 4.4.2 at this point.)
First I did backup my existing system to the sd card (maybe this will come in handy later in fixing things?)
Then I went to install and selected the three files I was suppose to use.
After i selected them, I realized I hadn't wiped things, so I left the safetrap install and went to the wipe option. I wanted to make sure I wiped everything except the SD card and here is where I probably screwed up... in the advanced wipe I selected everything to be wiped except for the sd card. It did it's thing. I then went back and selected "install" and here is where things looked different... I figured I'd be back to the option to select what to install, but instead it just went to a terminal window and it showed 'something processing' (Can't recall exactly what it said) and it was just stuck there. I left it for a quite a while (10 minutes or so) and still nothing, so I decided I'd try to start over, so I popped battery out and rebooted.
That's when all I got was the samsung splash screen.
At this time I "was" able to get into both recovery mode and download mode (Not longer can get to recovery mode... probably broke it based on stuff I did coming up.)
So then I was at the stage of googling and researching what to do. The option that seemed to come up over and over was this one http://forum.xda-developers.com/showthread.php?t=2663545 and I would repeatedly try it and everything looked to go well (saw stuff in odin installing) but at then end it just says "failed."
This led me to try the keis approach which I also so recommended. The initial attempt failed so I then tried the keis emergency firmware recovery option, but apparently something is wrong here since I don't see my device listed and have no idea what the recovery code would be.
I also had tried first installing the two kernels I had used that enabled me to first root my phone (listed in the first link NC1 stock and NI1 stock) and then using odin as described above, but same result.
Note lastly, if I now try get into recovery mode, I get the yellow message about keis failed to install (I can get the exact verbiage if it helps.)
Sorry for the lengthy explanation but figured some background might help. I can still get to download mode and use Odin so I figure there must be something I can probably do? Any ideas what to try would be greatly appreciated. Maybe I need to try and flash with a different PIT and different firmware? I'm just not sure what to try.

First, this should be in q&a, not the general forum. It gets lost here.
See this and flash the nb1 tar file in Odin. http://forum.xda-developers.com/showthread.php?p=56453100
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
First, this should be in q&a, not the general forum. It gets lost here.
See this and flash the nb1 tar file in Odin. http://forum.xda-developers.com/showthread.php?p=56453100
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for trying to help JD. I'll maybe repost in the questions forum (sorry I didn't see that.)
Note from the link above I tried both
NB1 ROOTED WITH SAFESTRAP
nb1 I337UCUFNB1_TWRootable_Full_Odin
and
NB1 STOCK (and optional upgrade to NJ4)
AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5
Both of them run through their motions but end up with failed as shown here ...
https://dl.dropboxusercontent.com/u/86998/Screen%20Shot%202014-11-27%20at%2012.13.45%20AM.png
:crying:

Thread moved to Q&A
Please remember the word "bricked" is used to describe a phone that can no longer power on at all
Soft--bricked or sponged is used to describe a phone that at least can still get into download mode or LEDs light, etc.
Thanks
FNSM

rickcr said:
Thanks for trying to help JD. I'll maybe repost in the questions forum (sorry I didn't see that.)
Note from the link above I tried both
NB1 ROOTED WITH SAFESTRAP
nb1 I337UCUFNB1_TWRootable_Full_Odin
and
NB1 STOCK (and optional upgrade to NJ4)
AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5
Both of them run through their motions but end up with failed as shown here ...
https://dl.dropboxusercontent.com/u/86998/Screen Shot 2014-11-27 at 12.13.45 AM.png
:crying:
Click to expand...
Click to collapse
Try a different usb cable and ports. Odin can be finicky. It looks like you're doing everything correctly
Sent from my Nexus 9 using XDA Free mobile app

Thanks!
jd1639 said:
Try a different usb cable and ports. Odin can be finicky. It looks like you're doing everything correctly
Click to expand...
Click to collapse
First off THANKS for not just giving up on me and stating the above.
After trying several USB cables it got me thinking, what else could maybe interfering with how Odin is working? When I originally rooted and flashed some kernels using Odin in my windows VM (using VMware Fusion) on Macbook Pro things had gone just fine, but I realized I might have done all of that before having upgraded to Mavericks.
So on a whim, I figured I'd try the trial version of Parallels and use my windows image with that.
Sure enough BINGO it worked!!
I would have guessed the VM as the problem sooner if my old windows vm under Fusion would have said that it couldn't connect, but what threw me off is that it DOES connect... but obviously some kind of USB protocol is getting messed up. The fact you mentioned bad cables and "finicky" prompted me to try Parallels.
Regardless I'm happy now. I'll spend the $70 and just use windows on Parallels from now on.
Thanks again!!!

rickcr said:
First off THANKS for not just giving up on me and stating the above.
After trying several USB cables it got me thinking, what else could maybe interfering with how Odin is working? When I originally rooted and flashed some kernels using Odin in my windows VM (using VMware Fusion) on Macbook Pro things had gone just fine, but I realized I might have done all of that before having upgraded to Mavericks.
So on a whim, I figured I'd try the trial version of Parallels and use my windows image with that.
Sure enough BINGO it worked!!
I would have guessed the VM as the problem sooner if my old windows vm under Fusion would have said that it couldn't connect, but what threw me off is that it DOES connect... but obviously some kind of USB protocol is getting messed up. The fact you mentioned bad cables and "finicky" prompted me to try Parallels.
Regardless I'm happy now. I'll spend the $70 and just use windows on Parallels from now on.
Thanks again!!!
Click to expand...
Click to collapse
Glad you finally got it working
Sent from my Nexus 9 using XDA Free mobile app

Unable to downgrade from 7.1.1 to 6.0.1

I can't seem to figure out how to downgrade back to a stock ROM after installing this:
lineage-14.1-20170331-UNOFFICIAL-trltetmo.zip (can't post link yet)
I believe it's the Nougat 7.1.1
I want to downgrade to 6.0.1 or 5.1.1
One message I see is "Recovery is not Seandroid Enforcing". Seems like all fixes suggest reinstalling stock ROM, which I'm trying to do, but can't.
Phone is a Samsung Note 4 SM-N910W8 (Rogers)

What's your steps to downgrade to 6.0.1? Did you download Rogers ROM and ODIN it(google is your best friend)?

- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...

If ODIN starts and stops immediately, you have a different problem. Did you install the Samsung Android USB driver properly. Anyway, you have a software issue, fix it first. I suggest you watch a few related video on youtube.
ziggy1971 said:
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
Click to expand...
Click to collapse

Currently no response.
In the freezer... I'm waiting.

Not sure which I should follow first:
Debrick here: https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
or
The following from https://forum.xda-developers.com/showpost.php?p=72338162&postcount=2622
SUREFACE said:
It Sounds that You have a "FULL BRICK" !
The Only way, that REALY can Help is a "USB-JIG".
And Hope, that this One Brings Your Device back in Download-Mode!
You can Build Your Own One, see here : https://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707
Or Buy One! See Here: https://www.amazon.de/Download-Repair-Stecker-Samsung-Galaxy/dp/B004VN5ZYS
And You need a REPAIR ROM ! Take A Look here for Your Variant : https://mega.nz/#F!Ax0gxSzZ!Qq_eJWX678bQHBhn7BHNDQ
Hope that this will Work!
Click to expand...
Click to collapse
Since yesterday I did the following:
- reset my system with a backup image (Bare Metal Restore with True Image) I only have some basic software installed.
- downloaded and installed SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0

Is your phone booting up and functioning? If it is, why are you talking about debrick? I'm assuming that you're "new" to all this. I suggest you read up(especially the stickies) and be comfortable before you go further.
ziggy1971 said:
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
Click to expand...
Click to collapse
ziggy1971 said:
Not sure which I should follow first:
Debrick here: https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
or
The following from https://forum.xda-developers.com/showpost.php?p=72338162&postcount=2622
Since yesterday I did the following:
- reset my system with a backup image (Bare Metal Restore with True Image) I only have some basic software installed.
- downloaded and installed SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0
Click to expand...
Click to collapse

No, it doesn't boot up at all now.
I know I initially said "I" installed the custom ROM, I didn't, I bought it that way. The previous owner won't do anything to help. The only thing he did was provide a link to the ROM he had installed, nothing more, not even the tutorial related to it, I found that on my own (wait, he's made it more than clear how incompetent/ignorant I am as a person).
I've been searching and reading for 3 days straight now. Getting to the point again where I accept defeat, assume the money lost.
Moving on... I've rooted other phones before without issues.
I follow a tutorial on how to downgrade to a stock ROM.
http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
Odin stops with various errors.
I could still boot device into TWRP-3.1.0
Reflashed LineageOS 14.1 ROM from SD to get it working again.
LineageOS 14.1 ROM would boot up, run for almost a minute and a half and shut down.
Pull battery, reboot into LineageOS 14.1 ROM, same thing.
Run Odin, connect device to computer, try to flash stock ROM, error again (different one). Somehow, it says "There is no PIT partition"
I followed this tutorial: https://forum.xda-developers.com/no...te-4-pit-files-repartiton-f-g-c-t-w8-t3282641
Odin says FAIL.
Now, it does NOTHING.
I follow this tutorial: Debrick here: https://forum.xda-developers.com/not...k-img-t3488114
Yes, the whole freezer thing overnight.
I have the latest USB drivers installed.
When I connected to the PC, an error popped up saying "...drivers not installed properly..." so I let Windows Update install the correct drivers.
I can connect to the PC now, press the power button for more than 10 seconds, eventually a popup message says "USB Device Not Recognized by Windows"
I've tried the following stock ROMs, 4.4.4, 5.1.1. I finally managed to download 6.0.1, but haven't been able to try it.

All I can say is that if you can boot into TWRP(I assumed you install the N910T version), then your phone is not bricked. All these "debricking" you're doing is potentially harming than fixing.
You assume the risk, when you buy 2nd hand. But based on what you're saying, it sounds like it may also have hardware issues(I don't think software will fix). Was it working when you got it? If you can return it, I suggest you do.

Another pc or windows version may work

A more trustworthy guide on using ODIN:
http://forums.androidcentral.com/am...w-flash-stock-rom-via-odin-new-interface.html

mnopy said:
Another pc or windows version may work
Click to expand...
Click to collapse
I will try with another PC, two batteries, different USB cables, different versions of the USB drivers, and so on.
Anything I missed?

ziggy1971 said:
I will try with another PC, two batteries, different USB cables, different versions of the USB drivers, and so on.
Anything I missed?
Click to expand...
Click to collapse
QualcommDrv
this is the Qualcomm Drivers(x86 and x64, choose your system's version and install) .
Without that your pc will not recognize your phone.
Uninstall everything related to samsung from your pc.
Kies, smart link, usb drivers. Use revo-unistaller for this to be sure nothing have left behind.
Go to control panel>system>device manager and remove anything that is related to your phone . If prompt delete drivers associated with that, say yes. Reboot your pc
Have saved QualcommDrv, samsung usb drivers and Odin. These are the tools you are going to need and must have.
after uninstall everything, unzip and install QualcommDrv.
Take off your battery, press power buton for 10 sec . Connect the phone to pc (without battery)
QualcommDrv will install the correct drivers for your phone. After that If in devices and printers it is recognized as Qualcomm 8084 .... its ok to proceed . if not , check again drivers and their installation
If windows says device drivers are not correctly installed and prompt to download and install, stop and cancel it.
IT will replace the QualcommDrv and you will not be able to see your phone correctly.
You need to keep QualcommDrv installed. When this is done and you are sure its correct and working, unplug your phone and install Samsung usb drivers. Reboot pc
unzip odin in desktop (or where ever its easy to access).
with your phone freezed and battery charged try to go to download mode. If succeed, connect to pc and with odin try to flash stock rom. If not ......
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
That what you need to have correct and working in order to START. THIS IS ONLY THE FIRST STEP
YOU HAVE TO UNDERSTAND
this is a hardware failure of the motherboard and will never will be completely fixed. These steps will only help you resurrect your phone and maybe give you the chance to be able to use it again.
It has nothing to do with software that failed to install. It was just the result and not the real problem, which is a diffect motherboard like thousand others. Sadly this is a common problem with Note 4 that happened to many users.
I have the same problem and I also bought it second hand knowing its problematic but not how much.
After that I realized the problem and the solutions to it. Every one of us is having a slightly different behavior of the phone.
I, for example cannt use the phone without the ext sdcard with unbrick image in it. When I take it out phone, will not start, reboot , do nothing.With the card in it its working almost perfect.
So have patience and read and search to know what you are dealing with.
Good luck

I managed to revive the Note 4 using a stock ROM.
Now, I have more questions like;
- Is this a problem on ALL models of the Note 4 or is it limited to a certain model?

ziggy1971 said:
I managed to revive the Note 4 using a stock ROM.
Now, I have more questions like;
- Is this a problem on ALL models of the Note 4 or is it limited to a certain model?
Click to expand...
Click to collapse
I don't believe you truly downgraded. I'm assuming you were on a 6.0.1 bootloader running a compiled 7.1.1 ROM. It probably hosed some partitions, and other things. Flashing the Stock ROM normalized it.
Most of time flashing a stock touchwiz rom will fix the "damage" that results in flashing a CM ROM.

dicksteele said:
I don't believe you truly downgraded. I'm assuming you were on a 6.0.1 bootloader running a compiled 7.1.1 ROM. It probably hosed some partitions, and other things. Flashing the Stock ROM normalized it.
Most of time flashing a stock touchwiz rom will fix the "damage" that results in flashing a CM ROM.
Click to expand...
Click to collapse
I have no idea what kernel, bootloader, etc. were/are used in the LineageOS ROM.
What I'd like to do is take a stock ROM and remove the unnecessary BLOATWARE and keep all the rest as it is.
Personal blurb: Why can't OS makers simply do that, make an OS!!! Windows, Android, it really doesn't matter, they're all the same.

ziggy1971 said:
I have no idea what kernel, bootloader, etc. were/are used in the LineageOS ROM.
What I'd like to do is take a stock ROM and remove the unnecessary BLOATWARE and keep all the rest as it is.
Personal blurb: Why can't OS makers simply do that, make an OS!!! Windows, Android, it really doesn't matter, they're all the same.
Click to expand...
Click to collapse
There is nothing stopping you from doing that but you.
Don't waste your breath saying I don't know how. There are TONS of guides on XDA.
That's exactly how I started learning. With that desire.
And here's what was most likely on it
https://forum.xda-developers.com/note-4/orig-development/rom-cyanogenmod-14-1-t3506613

dicksteele said:
There is nothing stopping you from doing that but you.
Don't waste your breath saying I don't know how. There are TONS of guides on XDA.
That's exactly how I started learning. With that desire.
And here's what was most likely on it
https://forum.xda-developers.com/note-4/orig-development/rom-cyanogenmod-14-1-t3506613
Click to expand...
Click to collapse
"I don't know how" generally isn't in my vocabulary. It's more like, where do I start, what do I need, where's a good tutorial explaining the what, how, and why of doing things.
Do I need to go all the way into the Java source code or are there other ways of removing some of the built-in apps?
Any tutorial/info suggestions are more than welcome. I'm not that familiar with the lingo of ROM customizing, so my searches are pretty much limited to that; "Android ROM customizing" is about the jist of it right now.

ziggy1971 said:
"I don't know how" generally isn't in my vocabulary. It's more like, where do I start, what do I need, where's a good tutorial explaining the what, how, and why of doing things.
Do I need to go all the way into the Java source code or are there other ways of removing some of the built-in apps?
Any tutorial/info suggestions are more than welcome. I'm not that familiar with the lingo of ROM customizing, so my searches are pretty much limited to that; "Android ROM customizing" is about the jist of it right now.
Click to expand...
Click to collapse
take a look here,
https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885
here:
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and here:
https://forum.xda-developers.com/showthread.php?t=2467004
and maybe here:
https://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
I cannt built but I can test, so go for it and tell us if we can help in the next step

logosA said:
take a look here,
https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885
here:
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and here:
https://forum.xda-developers.com/showthread.php?t=2467004
and maybe here:
https://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
I cannt built but I can test, so go for it and tell us if we can help in the next step
Click to expand...
Click to collapse
Those are good.
Some more are here
https://forum.xda-developers.com/general/xda-university
https://forum.xda-developers.com/chef-central/android
https://forum.xda-developers.com/showthread.php?t=1272270
https://forum.xda-developers.com/showthread.php?t=2069130
https://forum.xda-developers.com/showpost.php?p=5626301&postcount=4
https://forum.xda-developers.com/showthread.php?t=1590192
https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
There are essentially two ways to do what you want.
Use the unpack tool above, extract the system.img from a Stock ROM
https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
I get my stock ROMs from here
http://updato.com/firmware-archive-select-model?q=n910c&rpp=15&order=date&dir=desc
Remove the bloatware or apps you don't want.
Use the app same app that you used to extract the system.img to repack it.
Use the https://forum.xda-developers.com/chef-central/android/tool-afaneh-tar-kitchen-t3603649
to build a tar and flash with ODIN.
Second option use a kitchen. I'm testing the one below today to see if it works.
https://forum.xda-developers.com/ch...0-0-deluxe-kitchen-graphic-interface-t3579100
SuperR works great. But you need a Linux environment to run it.
I use virtualbox on my Win10 machine. I use premade images from here
http://www.osboxes.org/virtualbox-images/
Personally I use the Ultimate Edition.
Or use cygwin. I gave you plenty of links to learn how that works. It's a pain that's why I use virtualbox.

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.