Stuck in TWRP on LG G2- need a Good Samaritan - G2 Q&A, Help & Troubleshooting

First off. I'm pretty much a layman at this. Anyone that can solve my issues, I'll gladly pay via PayPal or whatever...
Two months ago, I bought a used LG G2 . It was rooted and running Lollipop.
Sadly, I was a PokemonGo junkie, so when the M'F'ng Niantic a**holes put a block on rooted phones, I attempted the Magisk workaround and ended up bricking my device.
Fortunately I found a solution via You Tube and was able to restore to the factory KitKat / AT&T.
THE CURRENT problem is that yesterday I re-rooted the device, installed TWRP, but did something wrong to where it will not fully reboot and I'm stuck in TWRP. I've watched and read about 20 "fix it" instructionals, which rely on using a PC. I'm using a laptop running XP and every time I have downloaded, installed, and tried to update the damn LG USB driver, it won't f*ing update. I'm going mad and ready to jump off a bridge.
Supposedly, this is the place to go. for answers, so ...CAN ANYONE HELP?!! Again, I'm a layman. I need VERY simple, step by step solutions, that account for ANYTHING that might go wrong, since so far, it always does.
Thank you, if you read this.

Ok Can you access to twrp ?
(Sorry for my english i'm french)

If you are in the TWRP, just download some other kk rom, transfer it to your phone and install, one question, what TWRP is it ? 2.8.7.0. ?

Kornelije23 said:
If you are in the TWRP, just download some other kk rom, transfer it to your phone and install, one question, what TWRP is it ? 2.8.7.0. ?
Click to expand...
Click to collapse
Agreed. Also, if there's no communication between PC and device, you may need an OTG to flash from.
Sent from my Nexus 6 using XDA-Developers mobile app

R2MIR2MI said:
Ok Can you access to twrp ?
(Sorry for my english i'm french)
Click to expand...
Click to collapse
Thanks for the reply. Yes, I can access TWRP. I just don't know what to do with it.

Dork6243 said:
Agreed. Also, if there's no communication between PC and device, you may need an OTG to flash from.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's TWRP 2.7.0. I kind of know in theory what needs to be done, but I don't know how to do it. I thought I backed everything up using Titanium and TWRP, but maybe the KK ROM is gone? I dunno... I was actually hoping to install Lollipop

What model do you have?
If it is d802, then there is an easy-to-flash rom here: http://forum.xda-developers.com/lg-g2/development-d802/rom-pure-stock-lg-google-apps-t3477635/page1
To transfer it to the phone, you can use OTG as Dork said: put the rom on a usb-stick and connect it to the phone with an OTG cable. Most versions of twrp support OTG.
Another way is to get linux for your PC. You're really better off with linux than XP, but you can also just boot with a live-cd. In linux, USB generally just works, though sometimes you have to be root because ordinary users may not have permission.

Thanks for the replies, but being very new at all this, I don't know how to do any of the things suggested. I ended up finding a you tube video which walked me through downloading lg flash tool and some .dll file, and on my work computer with windows 7, I was able to install the usb drivers & change the port number which allowed LG flash to work. The crappy XP didn't have that option on the device manager menu and wouldn't install the drivers.
Anyway, I got it restored to ATT stock KitKat. I wanted Lollipop and Magisk, so I tried installing TWRP with AutoRec, then got stuck in TWRP and bricked again. So I did the whole lg flash to KitKat process again. Now Im sick of messing with it and bricking my phone. I cant find any super simple step by step tutorial that makes sense to a layman like me, or that doesn't leave out steps, or provide expired links, or account for anything that could go wrong. I had hoped this was the place to come, but no luck so far. I know its time consuming for someone to make up a truly easy to follow guide for an older device, using layman terms that my grandma could follow, and I work 2 jobs and dont have hours to try to thoroughly learn OS programming, so I guess Ill just leave well enough alone and live with KitKat and without the ability to mask my root.

davizzyus said:
Thanks for the replies, but being very new at all this, I don't know how to do any of the things suggested.
Click to expand...
Click to collapse
Do what everybody here has done: read. And when you say "I can access TWRP. I just don't know what to do with it." you havn't even read the basics.
Just read the provided solutions properly. The Knowledge will grow. Here's a list of methods:
http://forum.xda-developers.com/showpost.php?p=63327417&postcount=4

Jan Philipp said:
Do what everybody here has done: read. And when you say "I can access TWRP. I just don't know what to do with it." you havn't even read the basics.
Just read the provided solutions properly. The Knowledge will grow. Here's a list of methods:
http://forum.xda-developers.com/showpost.php?p=63327417&postcount=4
Click to expand...
Click to collapse
I have tried reading a lot of different threads. As I said before, I don't understand the "tech talk" for lack of a better word. When I'm reading "bootload" this, and " sideboot" that, and kernels, and loki, and CM, and mods, and .kdz and ATD,....I don't know what all that means, & there's no OS dictionary to translate. I can't seem to find any threads that explain it for newcomers trying to learn.
Im an accountant. I can prepare corporate tax returns with my eyes closed, but cell phone programming is Greek to me.

Related

[Q] (HELP) Rooting 4.2.2 Nexus 7

Hi, now most people here are smart with this type of thing soooo i wanted to ask you how i can root the nexus 7 running 4.2.2. I tried to use the wugfresh NRT but when I was installing drivers a problem occurred. Instead of having ADB drivers or something like that I had ADB Composite drivers installed even though i followed the guide completely and I have tried several times to correct this but i havent found a solution. Also i attempted to carry on the rooting process but it said i did not have the correct drivers installed and etc. So can someone give me a fool proof way of getting the right drivers for this thing so i can root so i can finally install some kernels and use the sixaxis controller app! sorry for the essay and all help is appreciated
hrsedJe Something
Use the THE GOOGLE NEXUS 7 TOOLKIT at : http://forum.xda-developers.com/showthread.php?t=1809195 and then use the files from here : http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 and then start the tool and root. easiest solution I know.
If 4.2.2 doesn't show up in the device list, pick 4.2.1, worked fine for me.
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
phonic said:
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
Click to expand...
Click to collapse
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Kaaji1359 said:
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Click to expand...
Click to collapse
Dude, most commands for doing stuff on the N7 manually are four words. It really isn't a lot to remember. Also I don't think you understand the purpose of this site/forum.
..That being said.
Use Wug's toolkit and update the adb files in its install directory. Then just use the 4.2.1 settings if 4.2.2 doesn't show.
Here is a post with the files: http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650
sucks that the toolkit is only for windows, sucky windows
Kaaji1359 said:
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Click to expand...
Click to collapse
There is a big difference between memorizing commands and actually understanding what they mean. Your post made it very clear that in the "years" you've been doing it, you never possessed the latter.
It is not a complicated process. Unlock bootloader, run custom recovery, flash su zip. Voila. In the amount of time it took you to make your original post you could have been done. If it takes you two hours then you are doing something seriously wrong.
This is a developer forum geared towards people who want to learn how things work, not just look for quick one click tools, and then get upset when things don't work out for them using said tools and people tell them to spend some time educating themselves. If people here spent more time actually learning instead of relying on quick fixes, then we would have to deal with hundreds of posts complaining on how OTA updates were failing because of asserts every time a new one came out.
And your last sentence makes no sense. Obviously there is a reason isn't there?
Sent from my Nexus 7 3G using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2019519
had the same problems
Just google fastboot files for n7, get sdk and pack files AND the recovery into the sdk tool folder.
Shift+right click -> start command here
Fastboot flash recovery recovery.img
Start tab abd sideload the SU.zip (google superuser)
Flash
Done ))
Did it yesterday no issues!
phonic said:
There is a big difference between memorizing commands and actually understanding what they mean. Your post made it very clear that in the "years" you've been doing it, you never possessed the latter.
It is not a complicated process. Unlock bootloader, run custom recovery, flash su zip. Voila. In the amount of time it took you to make your original post you could have been done. If it takes you two hours then you are doing something seriously wrong.
This is a developer forum geared towards people who want to learn how things work, not just look for quick one click tools, and then get upset when things don't work out for them using said tools and people tell them to spend some time educating themselves. If people here spent more time actually learning instead of relying on quick fixes, then we would have to deal with hundreds of posts complaining on how OTA updates were failing because of asserts every time a new one came out.
And your last sentence makes no sense. Obviously there is a reason isn't there?
Sent from my Nexus 7 3G using Tapatalk
Click to expand...
Click to collapse
Well said phonic. I prefer the manual way as well. It is always good to know what you are doing, but knowing how it works and learning something is always better.
I would much rather learn something than to have someone do it for me. If ever I need help and ask someone, they say I'll do it for you I say no, please show me how to do it!
Sent from my Nexus 7 using Tapatalk 2
kidujp said:
Use the THE GOOGLE NEXUS 7 TOOLKIT at : http://forum.xda-developers.com/showthread.php?t=1809195 and then use the files from here : http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 and then start the tool and root. easiest solution I know.
If 4.2.2 doesn't show up in the device list, pick 4.2.1, worked fine for me.
Click to expand...
Click to collapse
You may receive an error message "ABD" is offline, in this case download the latest Android SDK manager and upgrade all USB drivers before using the toolkit again.
Sent from my Nexus 7 using xda app-developers app
phonic said:
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
Click to expand...
Click to collapse
Never ceases to amaze me how many pretentious pricks use XDA.... Reminds me of Apple snobs.
command line is the way to go
command line is the way to go m8!!
cheers,
geek endangered

An overwhelmed noob

I have this shinny new powerful phone and I have no idea what to do with it. I've never got too deep into cell phones. But I want to get the most out of this phone. I pay a lot to be able to use it and I want to get the most enjoyment out of it. I've had it a while now and I haven't really done much to it.
I want to get rid of programs that is just taking up space. I want to get the best apps, learn about the phone. Customize it in cool ways.
Should I root it? Am I too much of a noob and or have too good of a phone to even need to worry about it?
Will you guys hold my hand and walk me through this phone or link me to some "lg g2 starter guide" threads to really have fun with this phone?
Thanks
Aye! First of all, welcome to the G2 community!
It's 4 in the morning for me right now, can we 'go for a walk' after I get my sleep?
Just wanted to reply so you won't feel lost and lonely, been there, done that.
In the meantime, enjoy your G2 first for what it is right now.
Sent from my LG-D802 using xda app-developers app
I feel the exact same way! Except I've had the phone for one month now.
Sent from my LG-D802 using XDA Premium 4 mobile app
Thanks. I bought my phone about two weeks ago. Switched from sprint to verizon after 7 years with sprint
honestly the phone is fast enough by itself with amazing battery, but if you like to get into flashing things first off
http://forum.xda-developers.com/showthread.php?t=2449670 this will teach you how to install TWRP. after that just download a rom of your choosing, more than likely the developer already root the rom for you so you dont need to do it. enjoy from there. make sure you know how to enter TWRP the hard button way... for tmobile is hold down and power button, once LG logo flash quickly let go and press the two button again. thats tmobile though.
I'm a bit of noob to the whole custom ROMS thing as well. I was just wondering what is a good program to make a back up before rooting and installing new ROMS?
TWRP (Team Win Recovery Project) and CWM (Clockwork Mod) both have backup utilities baked in. The stock full system backup will be quite large. Aside from being a best practice, it's too large to archive on the device, in my opinion. I would recommend offloading it to your PC and learn how to put it back using ADB (Android Debug Bridge) and the TWRP sideload feature in the event of a soft brick condition. Recommend you also backup and save your EFS/IMEI.
http://forum.xda-developers.com/showthread.php?t=2451390
First step, ioroot.
Read and re-read on how to root and flash if you've never rooted or flash ROMS before to reduce to risk of bricking.
Sent from my JEE TWO
G1_enthusiast said:
http://forum.xda-developers.com/showthread.php?t=2449670 this will teach you how to install TWRP. after that just download a rom of your choosing.
Click to expand...
Click to collapse
Hi. As someone who has very little understanding about this stuff, I'm struggling to get any use out of that guide. Is anyone else finding this?
For example:
"Ok, so if you look in the download page for your device and you are getting a zip file, this is a flashable zip, but it cannot be treated the same as an IMG file in this guide. You need to flash an older one that is a .img file, and then use that to flash the newer zip."
I have no idea how to do what it says in that last sentence, or what it even means.
Then where it starts describing option one, I don't understand what it's telling me to do. What does it mean to "push" the loki patch and the img? Where am I supposed to type that stuff in the code box?
I figured I'd just get my g2 rooted and back it up, then start reading about the stuff I didn't understand. But just getting started seems really complicated, and I'm struggling find the info I need to understand that guide. Is there a more detailed, baby step guide for idiots out there? Or can someone just quickly explain the things I mentioned about that guide?
Thanks for replies.
http://forum.xda-developers.com/showthread.php?p=45692679. If you need root, try this guide.
Sent from my LG-D800 using Tapatalk

[Q] KitKat on a rooted Note 3.

Hi Guys,
First, I beg of you not to say RTFM on similar questions here regarding this. I have read them, and read them in their entirety. The problem I have is that none of them list how to get me though my issues on my Galaxy Note 3 SM-N900A.
My problem is that I (as many others) really want to upgrade to the Kit Kat OTA released from AT&T a week or so ago. The thing is, I did root my device and as everyone know's this fails any OTA updates.
My question is two fold, but first I would like to explain that I rooted my device NOT for being able to install any custom ROM's. In fact I never had an interest in doing so as I actually like the stock OS's which right now I am still running 4.3. I rooted it specifically to be able to run network / packet sniffers on my own home network as a method to learn a little more about how things go over a network, seeing what I can learn and see if I can find any vulnerabilities. I also used it to try and clean bloat ware and other programs that with out root I can not uninstall or use, such as certain fast reboot apps. So, I really had no intention of using the Root to get me a custom ROM, as I wouldn't even know where to begin.
So my questions are this. Is there anyway that I can "un do" the root in order to let the device act as if it were never rooted? Or, is there anyway to force the OTA regardless of the device being rooted. My biggest fear is losing all the apps and files that I have on my device and I have never been able to get any kind of back up app to work, especially to restore anything from them.
I had read that one can use ODIN to flash the Kit Kat ROM, but while I have installed ODIN on my laptop, I am clueless on how to use it. I tried everything, but even with the USB drivers installed and working (I know this because plugged into the USB port, I am able to browse all the files on my device, yet ODIN continues to tell me that no device has been found.
Can someone please help me to understand what I need to do? Again, I don't care if I lose Root, I care that I don't lose all the stuff I spent months installing and getting my device where I want it. I really need someone to explain somethings to me as if I were a two year old, with out scalding me and making me feel like a complete idiot. I came here because everyone I have talked to told me that you guys would be the ones that could help me, and if you can't, then I am screwed and will have to just wipe the entire device and I just can't do that. I may wind up having to buy a new device and just transfer over what ever I can, however, in the mean time that is not an option.
To this end, I come begging for some serious help since I know you guys are the literal gods of Androids. If I must take some kind of custom ROM in order to get Kit Kat, I am somewhat willing, but I do not fully understand or know what ROM I would want to install as I have never in my life seen a custom ROM and what the benefits of having one are which is kind of why I really want to stick with the stock ROM and just keep getting the updates via OTA.
I have all the faith in the world you guys can help, I just don't know if anyone is willing to help since I know similar questions have been asked, but I do not know how to use what I learned for my particular device.
Thanks very much.
EU
Dardwizzle said:
Hi Guys,
First, I beg of you not to say RTFM on similar questions here regarding this. I have read them, and read them in their entirety. The problem I have is that none of them list how to get me though my issues on my Galaxy Note 3 SM-N900A.
My problem is that I (as many others) really want to upgrade to the Kit Kat OTA released from AT&T a week or so ago. The thing is, I did root my device and as everyone know's this fails any OTA updates.
My question is two fold, but first I would like to explain that I rooted my device NOT for being able to install any custom ROM's. In fact I never had an interest in doing so as I actually like the stock OS's which right now I am still running 4.3. I rooted it specifically to be able to run network / packet sniffers on my own home network as a method to learn a little more about how things go over a network, seeing what I can learn and see if I can find any vulnerabilities. I also used it to try and clean bloat ware and other programs that with out root I can not uninstall or use, such as certain fast reboot apps. So, I really had no intention of using the Root to get me a custom ROM, as I wouldn't even know where to begin.
So my questions are this. Is there anyway that I can "un do" the root in order to let the device act as if it were never rooted? Or, is there anyway to force the OTA regardless of the device being rooted. My biggest fear is losing all the apps and files that I have on my device and I have never been able to get any kind of back up app to work, especially to restore anything from them.
I had read that one can use ODIN to flash the Kit Kat ROM, but while I have installed ODIN on my laptop, I am clueless on how to use it. I tried everything, but even with the USB drivers installed and working (I know this because plugged into the USB port, I am able to browse all the files on my device, yet ODIN continues to tell me that no device has been found.
Can someone please help me to understand what I need to do? Again, I don't care if I lose Root, I care that I don't lose all the stuff I spent months installing and getting my device where I want it. I really need someone to explain somethings to me as if I were a two year old, with out scalding me and making me feel like a complete idiot. I came here because everyone I have talked to told me that you guys would be the ones that could help me, and if you can't, then I am screwed and will have to just wipe the entire device and I just can't do that. I may wind up having to buy a new device and just transfer over what ever I can, however, in the mean time that is not an option.
To this end, I come begging for some serious help since I know you guys are the literal gods of Androids. If I must take some kind of custom ROM in order to get Kit Kat, I am somewhat willing, but I do not fully understand or know what ROM I would want to install as I have never in my life seen a custom ROM and what the benefits of having one are which is kind of why I really want to stick with the stock ROM and just keep getting the updates via OTA.
I have all the faith in the world you guys can help, I just don't know if anyone is willing to help since I know similar questions have been asked, but I do not know how to use what I learned for my particular device.
Thanks very much.
EU
Click to expand...
Click to collapse
does ur kies run? if so turn it off.
USB debugging off? turn it on.
are u in download mode of ur phone? if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen.
after that u can plug in ur phone.
Sent from somewhere under the sky, at the corner of this rounded earth.
antique_sonic said:
does ur kies run? if so turn it off.
USB debugging off? turn it on.
are u in download mode of ur phone? if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen.
after that u can plug in ur phone.
Sent from somewhere under the sky, at the corner of this rounded earth.
Click to expand...
Click to collapse
Hi antique_sonic, I would just like to clarify a couple things as well as answer your questions.
>does ur kies run? if so turn it off. <--- If you mean is it installed on my laptop and work? Yes it is, and yes it does, however, I almost never use it. Mainly because I was told that once you root a Samsung Device, Kies is no longer able to be used.
>USB debugging off? turn it on. <--- It is and has been turned on in an effort to try to sideload KitKat, but that was a hug fail. But I will leave it on for this discussion.
>are u in download mode of ur phone? <---- I have gotten here before but don't exactly know what to do once I am there since I don't know where to get a Kit Kat ROM, where to put it once I have it, or how to use anything in d/l mode.
> if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen. after that u can plug in ur phone. <--- Are these instructions for wiping the device back to the factory default? Will I lose everything currently installed and loaded on my Note 3? Or does this some how fix / allow for the OTA update to install completely because it no longer can tell the device is rooted?
Again, I must apologize because this is so greek to me.I am just trying to understand at this point what infact the instructions you gave me do, and what they are intended for. Is this just to get the USB drives to work properly? Or is this something that will help me undo root so that I would be able to install KitKat via the AT&T OTA. If now the latter, where I can I get a complete Kit Kat ROM and use ODIN to flash the ROM? This outcome would suck because I believe that this will cause me to lose everything on my device I worked so hard to get where I wanted. I have just over looked the fact that in rooting my device I there by killed my ability to keep my device updated with the latest OTA releases / patches.
Again, I appreciate you reply, but sadly I am in need of a bit more info if you could please.
Thank you so very much. I hope one day to be able to pay it forward, passing along the knowledge you have shared with me,
Regards,
EU
Dardwizzle said:
Hi antique_sonic, I would just like to clarify a couple things as well as answer your questions.
>does ur kies run? if so turn it off. <--- If you mean is it installed on my laptop and work? Yes it is, and yes it does, however, I almost never use it. Mainly because I was told that once you root a Samsung Device, Kies is no longer able to be used.
Click to expand...
Click to collapse
do check, is it running in background ? check your task manager. if so, kill the process. Kies should not run together with ODIN. Otherwise sometimes will give problem to your ODIN process.
I normally only install the USB driver only, as this is the only thing needed to connect your phone to comp (as MTP, or as ODIN connection).
Dardwizzle said:
>are u in download mode of ur phone? <---- I have gotten here before but don't exactly know what to do once I am there since I don't know where to get a Kit Kat ROM, where to put it once I have it, or how to use anything in d/l mode.
Click to expand...
Click to collapse
ok, in a very simple word. download mode is basically a state whereby your phone is ready to download system files and install the system files on your device.
This is the only state possible to get a connection to your ODIN PC to flash stock firmware, recovery (in .tar/.md5 format).
How to get the KK ROM ?
1) identify your device. which model it is. N9005? N900T? N900A? N900 blablabla?
2) goto samfirmware.com (register there if you don't have account. it is free). after that you can just find your firmware by typing on the search device textbox your device model (e.g N9005), and it will come out the list of your device firmware (normally they will show for the latest firmware list)
3) choose the firmware that you want to download (if your device N9005 international 32 gb, try to avoid the Hongkong / Taiwan firmware, as they have different PIT partition).
4) once you have the downloaded zip file from samfirmware, extract the zip, and then you will get the (.tar/.md5) file. Now you can use to flash this one over ODIN.
Dardwizzle said:
> if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen. after that u can plug in ur phone. <--- Are these instructions for wiping the device back to the factory default? Will I lose everything currently installed and loaded on my Note 3? Or does this some how fix / allow for the OTA update to install completely because it no longer can tell the device is rooted?
Click to expand...
Click to collapse
no. no. no.
This is how to go into download mode in your device
Not yet talking about factory reset.
But yes, you have to backup your internal storage, as sometimes upgrading will cost you to do factory reset, and your internal storage will be gone.
Dardwizzle said:
Again, I must apologize because this is so greek to me.I am just trying to understand at this point what infact the instructions you gave me do, and what they are intended for. Is this just to get the USB drives to work properly? Or is this something that will help me undo root so that I would be able to install KitKat via the AT&T OTA. If now the latter, where I can I get a complete Kit Kat ROM and use ODIN to flash the ROM? This outcome would suck because I believe that this will cause me to lose everything on my device I worked so hard to get where I wanted. I have just over looked the fact that in rooting my device I there by killed my ability to keep my device updated with the latest OTA releases / patches.
Click to expand...
Click to collapse
up to this point, I just remembered that you have N900A (AT&T) version. hahaha.
I go check the samfirmware, no release of KK yet at the samfirmware.
I'm sorry, I own N9005, and I never explore too much on the N900A, so I won't know what is the latest release, and where to get it other from samfirmware.
Dardwizzle said:
Again, I appreciate you reply, but sadly I am in need of a bit more info if you could please.
Thank you so very much. I hope one day to be able to pay it forward, passing along the knowledge you have shared with me,
Regards,
EU
Click to expand...
Click to collapse
no problem. you just get your latest firmware first, once you have it, you let me know, i can give you step by step in detail, on how to flash to your device.
antique_sonic said:
up to this point, I just remembered that you have N900A (AT&T) version. hahaha.
I go check the samfirmware, no release of KK yet at the samfirmware.
I'm sorry, I own N9005, and I never explore too much on the N900A, so I won't know what is the latest release, and where to get it other from samfirmware.
no problem. you just get your latest firmware first, once you have it, you let me know, i can give you step by step in detail, on how to flash to your device.
Click to expand...
Click to collapse
Sure sure, just laugh at me why don't ya!! LOL I will continue to try to find the appropriate firmware. I guess if I learned one valuable lesson in all this, it is just don't root your device if you don't plan on using custom ROM's. I had no idea that there would be no way to "unroot" your device once it's rooted. I was really hoping that you could just undo what ever is done to actually root the device, this way the OTA's will just start working again. Or that there would be a way to just force the OTA regardless of whether the device is rooted. I am not sure I truly understand why the OTA just won't install just because the device is rooted.I mean sure it adds SU to the device, and unlocks (I think) the boot partition or the boot loader, which ever, but regardless, why should the OTA package care and fail to install just because of that change?
Anyway, that's probably a discussion for another thread. I actually did find a Kit Kat zip that is like 150MB's it has a boot.img inside the zip, but it has nothing with an extension that ODIN can recognize. I would love to show you the zip, but it's too large to attach or email. The file name is 2400258.zip, but I forgot where I downloaded it from. It may be what I need to do the job, but with out someone seeing the zip I have no way of knowing if it's the files I need. I was not about to find any files with in it that are in txt readable format for me to say exactly what it is. It does have subfolders names Google and Android and the like but I am sure that is pretty useless with out seeing the full zip.
I will keep my eye on this thread and when I find something I can work with, or if you guys find anything I can work with I will come back and see where we can go next.
Thanks again bud!
Dardwizzle said:
Sure sure, just laugh at me why don't ya!! LOL I will continue to try to find the appropriate firmware. I guess if I learned one valuable lesson in all this, it is just don't root your device if you don't plan on using custom ROM's. I had no idea that there would be no way to "unroot" your device once it's rooted. I was really hoping that you could just undo what ever is done to actually root the device, this way the OTA's will just start working again. Or that there would be a way to just force the OTA regardless of whether the device is rooted. I am not sure I truly understand why the OTA just won't install just because the device is rooted.I mean sure it adds SU to the device, and unlocks (I think) the boot partition or the boot loader, which ever, but regardless, why should the OTA package care and fail to install just because of that change?
Anyway, that's probably a discussion for another thread. I actually did find a Kit Kat zip that is like 150MB's it has a boot.img inside the zip, but it has nothing with an extension that ODIN can recognize. I would love to show you the zip, but it's too large to attach or email. The file name is 2400258.zip, but I forgot where I downloaded it from. It may be what I need to do the job, but with out someone seeing the zip I have no way of knowing if it's the files I need. I was not about to find any files with in it that are in txt readable format for me to say exactly what it is. It does have subfolders names Google and Android and the like but I am sure that is pretty useless with out seeing the full zip.
I will keep my eye on this thread and when I find something I can work with, or if you guys find anything I can work with I will come back and see where we can go next.
Thanks again bud!
Click to expand...
Click to collapse
I don't like spoonfeeding too much actually.
but I find u r quite funny. no offence.
I have no idea this will work or not, but I found this as the 1st search result on Google.
http://www.droidviews.com/install-android-4-4-2-kitkat-ota-on-att-galaxy-note-3-sm-900a/
just have a look first nd don't do anything till u understand the article.
Sent from somewhere under the sky, at the corner of this rounded earth.
antique_sonic said:
I don't like spoonfeeding too much actually.
but I find u r quite funny. no offence.
I have no idea this will work or not, but I found this as the 1st search result on Google.
(I had to remove the link as the website thought I was adding it and gave me a no no warning that I can't post outside links cause I be a newbie!) BAH!!!
just have a look first nd don't do anything till u understand the article.
Sent from somewhere under the sky, at the corner of this rounded earth.
Click to expand...
Click to collapse
Hey antique_sonic, no offence taken my friend, I am a giant goof ball, but I am also someone who doesn't mind working out my own problems. It's just sometimes with things like this where I am clueless and need a little hand holding. It's nice to know that there are people like you around to help out the dopes like me My apologies for not getting back to you sooner, and I will be looking into the link you sent tonight. I haven't been feeling well lately, I have two herniated disks in my back and I have End Stage Liver disease and I am only 39, so I sometimes get a bit under the weather and am down for the count for a few days. So I do appreciate your patience with me and all the help and direction you are giving me. I try never to abuse the help as that is no way to learn, and learning is actually one of favorite hobbies! Weird huh.... So, I am off to go read the link you provided me and update the stock on my website and hope I make some more sales so I can get some money to buy a new phone when I brick this one! LMAO! Thanks again Sonic, I really appreciate everything!
Dardwizzle said:
Hey antique_sonic, no offence taken my friend, I am a giant goof ball, but I am also someone who doesn't mind working out my own problems. It's just sometimes with things like this where I am clueless and need a little hand holding.
Click to expand...
Click to collapse
No worries and yeah you should try to find first. by this way, you will learn faster, compare if someone do the spoonfeed.
Dardwizzle said:
It's nice to know that there are people like you around to help out the dopes like me My apologies for not getting back to you sooner, and I will be looking into the link you sent tonight.
Click to expand...
Click to collapse
My pleasure to help. And no worries for late reply, as I will do the same when I busy with my real life job.
Dardwizzle said:
I haven't been feeling well lately, I have two herniated disks in my back and I have End Stage Liver disease and I am only 39, so I sometimes get a bit under the weather and am down for the count for a few days. So I do appreciate your patience with me and all the help and direction you are giving me.
Click to expand...
Click to collapse
you are welcome mate. I'm sorry to read the news about your conditions. I can't say anything about this, but wish you all the best. Don't ever feel down in whichever state you are, just do the best in life, and we will never regret that 1 more day has passed.
Dardwizzle said:
I try never to abuse the help as that is no way to learn, and learning is actually one of favorite hobbies! Weird huh.... So, I am off to go read the link you provided me and update the stock on my website and hope I make some more sales so I can get some money to buy a new phone when I brick this one! LMAO! Thanks again Sonic, I really appreciate everything!
Click to expand...
Click to collapse
GOOD !!!
go and grab sales, rather than you brick the phone.
Once again, u r welcome mate.

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.

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