Related
I have an iconia tab getting shipped to me as of this post. I fairly knowledgeable about rooting and roms ( have done many roms and recovery from my cell phone).
I am sorry if some was explained on different threads, figured I would just ask them all here.
Since I haven't messed with the os at all, is there a lot of advantages from stock os to custom os?
Is there any reason to create a ext partition on sd.?
Is custom recovery installed easy, hopefully not uninstall to easy.?
Is there anyways to get data from Titanium backup on the tablet.
I am sure I may have a few more questions when I receive the tablet.
Any help on these questions would be great.
Sent from my LS670 using Tapatalk
All your questions are answered in the forums. You'll get your answers MUCH faster if you follow the rules and actually search before asking.
To be helpful, I'll give you ONE of the answers.
Custom recovery is very easy to install IF you don't have a 3.2.1 ROM preinstalled. If you have this version, you can still install but it's a more complex process. Read the guides in the development section and DO NOT attempt to use ROM manager or a generic CWM.
if you root you can use drivemount to be able to use external hd's formatted in ntfs. Which is the reason I rooted.
1. There's no general answer, as it depends on the ROM you use (some are more-or-less stock, others aren't even based on Acer stock)
2. I haven't had any reason to do anything like that, as I keep basically only my apps (with their data) and my linux chroot on the internal memory... Other than that, search the forum for instructions on how to switch internal <-> external memory (just a config hack, nothing spectacular and completely reversible)
3. It used to be almost ridiculously easy, but a recent update made it more complex. Details are in the forum (and partly in FloatingFatMan's post above).
4. As Titanium backup even runs fine on ICS, you'd expect it to work on HC... which it does.
FloatingFatMan said:
All your questions are answered in the forums. You'll get your answers MUCH faster if you follow the rules and actually search before asking.
.
Click to expand...
Click to collapse
I did do a some searches already , and found a lot of information. The people here are always helpful so I thought instead of just asking one question that I didn't know the answer to I would ask all of them I had.
To be honest I do love loading roms and enjoy the phone rooted atm, but a tablet is much more expensive device and want to try to avoid any conflicts with roms (There are so many I do not know where to start).
Here is my plans on the tablet atm.
Root it, load custom recovery (Clockwork?)
Doing a Nandroid backup of stock rom.
Loading Titanium backup and possibly transfering some data from the phone SD to acer sd, such as psx roms, and other misc stuff.
will look into different roms and see what works for my needs and hopefully avoid the rom cycle that I see with phone roms ,( Seems 3 month and support drops and different projects happen).
Plan on trying stock rom a little rooted before going into custom roms.
This is my current plan, but if anyone else has some suggestions that would be great.
FloatingFatMan said:
Custom recovery is very easy to install IF you don't have a 3.2.1 ROM preinstalled.
Click to expand...
Click to collapse
No, actually its still really easy you just have an extra step.
download the 3.0 downgrade
place it on sd card root directory
reboot holding volume down and power
?????
profit!
after that, just run iconiaroot and acer recovery installer (install both before downgrading) and you're golden, root with CWM. flash a rooted 3.2.1 stock or custom, its that easy.
you are right about one thing though, you can easily find the answer to every question in this thread on these forums.
edit- also, TC, i've found the most stable and functional roms to be stock. i ran a few customs (the best of which was flexstriker) but always found stock to run better and be the most stable, both the rooted 3.2.1 a500 rom and the rooted 3.2.1 a200 port have been great for me. you can go custom if you want, I'm just putting in my two cents.
So after blowing off the second half of my duties at work today, I managed to allocate enough time to get my SM-N910V rooted.
I have a few basic questions about what I should expect to see happen.
Allegedly, Verizon is rolling out an OTA upgrade to 6.0.1 Marshmallow sometime soon. Now that I have 'custom' boot and root achieved, will my device still receive and adhere to this OTA upgrade?
I have not applied any custom ROMs to the device. All I have done is follow the steps on this forum to unlock the bootloader and permroot.
If yes, cool!
If no, could someone please share with me a uniform resource identifier (lol) that links to a guide for installing CM13 to this device?
I will use my mind to beam eternal luck at anyone who helps me out. Thankyas.
Have you ever used Odin?
If you have twrp just load onto an sd or the phone and make sure to clear cache and wipe.
Bicknasty said:
Have you ever used Odin?
Click to expand...
Click to collapse
Yessir Mr. Nasty,
I followed a guide on this part of the forum that had me use Odin. After using Odin successfully I was able to get TWRP up before normal boot!
vIgGeN7 said:
If you have twrp just load onto an sd or the phone and make sure to clear cache and wipe.
Click to expand...
Click to collapse
Just to clarify, you're saying that if I boot into TWRP again and clear the cache/wipe, I'll go back to factory settings and get the OTA?
If you have a microSD card, use TWRP to backup all of your current data to it if you'd like to preserve it and have something to restore if anything goes awry. Download a custom ROM zip and whatever other zips you'd need for that particular ROM, and put them on the card. Use TWRP to format data and wipe everything EXCEPT FOR THE CARD, and then reboot into recovery mode again and open the TWRP install menu.
In that menu, navigate to external_sd (or whichever root level folder it is that contains the strings "ext" and "sd", referring to the microSD card), and select the zip or zips (in the proper order) that you want to flash. Then flash them, wipe cache/dalvik, and reboot.
I wouldn't stay on a stock ROM if I were you. You might avoid getting the OTA, but you're guaranteed to avoid it by running a custom ROM. JasmineROM seems to be the go-to ROM for stability, but hsbadr's CM13 builds are very functional.
Bicknasty said:
-snip-
Click to expand...
Click to collapse
Thank you for being so specific and clear, and for helping me out. I am new to this, used to working on computers that I can tear apart more easily and change things inside of.
I will keep this in mind and consider switching. I have a lot of free time with a 1GB/1GB
Futtermax said:
So after blowing off the second half of my duties at work today, I managed to allocate enough time to get my SM-N910V rooted.
I have a few basic questions about what I should expect to see happen.
Allegedly, Verizon is rolling out an OTA upgrade to 6.0.1 Marshmallow sometime soon. Now that I have 'custom' boot and root achieved, will my device still receive and adhere to this OTA upgrade?
I have not applied any custom ROMs to the device. All I have done is follow the steps on this forum to unlock the bootloader and permroot.
If yes, cool!
If no, could someone please share with me a uniform resource identifier (lol) that links to a guide for installing CM13 to this device?
I will use my mind to beam eternal luck at anyone who helps me out. Thankyas.
Click to expand...
Click to collapse
I dont know what everyone is thinking, but OTA will not work with rooted device. It will failed and in most case you will nee to flash full stock rom to fix it, then your bootloader will locked again. The best bet is to wait until Samsung released the rom and Dev here will modified it the right way so you can flash with TWRP.
Sent from my SM-N920V using Tapatalk
Honestly, don't bother with CM13 yet. It's buggy. I was on it for a short while, tried a couple different builds but I got sold on the Note 5 port which is on 5.1.1. If you have any apps that don't allow mock locations, they won't work on any 6.0/Marshmallow ports (i.e. CM13) from my short experience. I could be wrong. I couldn't find a way to allow mock locations on CM13, so I went somewhere else.
JOSHSKORN said:
Honestly, don't bother with CM13 yet. It's buggy. I was on it for a short while, tried a couple different builds but I got sold on the Note 5 port which is on 5.1.1. If you have any apps that don't allow mock locations, they won't work on any 6.0/Marshmallow ports (i.e. CM13) from my short experience. I could be wrong. I couldn't find a way to allow mock locations on CM13, so I went somewhere else.
Click to expand...
Click to collapse
I think CM13 is worth giving a chance.
I'm about 90% sure the MM update will come with a new bootloader (a locked one). I highly advise against trying to accept it if/when it comes. Someone here will tear it apart and make odin flashable images to get us on 6.0.1 TW rom. Until then, flash TWRP and CM13. I've been using it daily and it's one of the better CM roms I've used on any device.
Also look into Dual Boot Patcher so you can crack flash roms without affecting your primary one.
Sent from my SM-N910V using Tapatalk
Bicknasty said:
If you have a microSD card, use TWRP to backup all of your current data to it if you'd like to preserve it and have something to restore if anything goes awry. Download a custom ROM zip and whatever other zips you'd need for that particular ROM, and put them on the card. Use TWRP to format data and wipe everything EXCEPT FOR THE CARD, and then reboot into recovery mode again and open the TWRP install menu.
In that menu, navigate to external_sd (or whichever root level folder it is that contains the strings "ext" and "sd", referring to the microSD card), and select the zip or zips (in the proper order) that you want to flash. Then flash them, wipe cache/dalvik, and reboot.
I wouldn't stay on a stock ROM if I were you. You might avoid getting the OTA, but you're guaranteed to avoid it by running a custom ROM. JasmineROM seems to be the go-to ROM for stability, but hsbadr's CM13 builds are very functional.
Click to expand...
Click to collapse
I might add to that storing a copy of that backup on another device... your desktop computer, perhaps, so that if something really goes bad and wipes your sd card, you still have a backup.
Do not, no matter how much your phone nags you to, take an OTA now that you're rooted. The odds are good that they've closed the exploit used to get root.
If you're looking for stability, Jasmine ROM is the best that I've tried. It's not being supported anymore, but it really doesn't need it. Everything works. I froze, then deleted every single Samsung and Google app that I don't use and it is just smooth.
CM 13? The last I looked, the camera doesn't work well, Bluetooth is problematic, you can't set your sd card as internal storage and a few other niggling issues. I've been doing this since my Droid Incredible and have found that ROMs ported from other devices will have issues until the developers marry the software to the hardware. I'm now waiting for the official Marshmallow to drop and let the developers take a crack at it.
joshw0000 said:
I'm about 90% sure the MM update will come with a new bootloader (a locked one). I highly advise against trying to accept it if/when it comes. Someone here will tear it apart and make odin flashable images to get us on 6.0.1 TW rom. Until then, flash TWRP and CM13. I've been using it daily and it's one of the better CM roms I've used on any device.
Also look into Dual Boot Patcher so you can crack flash roms without affecting your primary one.
Click to expand...
Click to collapse
Dual boot patcher has worked pretty reliably for me. Just be sure to thoroughly read the directions to make doubly sure that nothing goes wrong.
douger1957 said:
CM 13? The last I looked, the camera doesn't work well, Bluetooth is problematic, you can't set your sd card as internal storage and a few other niggling issues. I've been doing this since my Droid Incredible and have found that ROMs ported from other devices will have issues until the developers marry the software to the hardware. I'm now waiting for the official Marshmallow to drop and let the developers take a crack at it.
Click to expand...
Click to collapse
Bluetooth is flawless. I can't see why anyone would set their sd card as internal (defeats the point of being able to move info between other phones and/or computers). Camera works very well (for CM). I've had very few issues with taking pictures. Recording video doesn't work for me. I've modded every phone I've used (I've owned many that I wouldn't carry due to no root) since the Eris and this is IMO the best CM port ever.
Sent from my SM-N910V using Tapatalk
I am using PaulPizz 5.1.1 ROM and it's working almost flawlessly. I'm happier than ever with this phone. I want to wait for the OTA 6.0.1 to hit and the teardown of that to begin before I switch.
I'll look into dual boot.
As a bog standard user I naively assumed that I could put apps on my SD card as and when I wanted. Instead the majority refuse to be put there or cause problems.
If I root my Samsung J500fn (Marshmallow) will I be able to chose the location for putting apps? Can I get rid totally of the stuff Google/Samsung think I need but I never use? Can I make better use of my SD card that is practically empty? Are there any drawbacks to keeping Marshmallow as installed or would rooting overwrite it? Is there a better way than to root? Is "One Click root" safe to use? Am I better of using various programs like Odin, TWRP etc. mentioned in various threads here?
Thanks to any and all who can answer my questions. :fingers-crossed:
Anne
webelan said:
As a bog standard user I naively assumed that I could put apps on my SD card as and when I wanted. Instead the majority refuse to be put there or cause problems.
If I root my Samsung J500fn (Marshmallow) will I be able to chose the location for putting apps? Can I get rid totally of the stuff Google/Samsung think I need but I never use? Can I make better use of my SD card that is practically empty? Are there any drawbacks to keeping Marshmallow as installed or would rooting overwrite it? Is there a better way than to root? Is "One Click root" safe to use? Am I better of using various programs like Odin, TWRP etc. mentioned in various threads here?
Thanks to any and all who can answer my questions. :fingers-crossed:
Anne
Click to expand...
Click to collapse
Hi Anne,
We all have the same trouble with storage on our J5.
If you chose to root your phone then yes you will be able to uninstall alot of the bloat ware that is on your phone.
You will also have the option of using adaptable storage.
There are lots of threads on here that will guide you through the process. Just make sure that you read the guides properly and download and install the CORRECT zips.
I don't know if the one click root is safe to use.
I would advice installing TWRP and then flashing super su. Again all of the guides are on here.
If you do install TWRP via Odin then you will have the option of flashing custom ROMs..
Have a good look at the guides. Ask all the questions that you need to. People in here will be happy to help.
It's really nice to see you on here
Have fun
John
Don't need root for adoptable storage.
Hi
Did u get the info that you need ?
Rooting
johnhux7 said:
Hi
Did u get the info that you need ?
Click to expand...
Click to collapse
Hi again, thanks for asking.
I downloaded TWRP from https://www.androidfilehost.com/?w=files&flid=55922, version for SM-J500FN dated May 6, 2016. Also ODIN-v3.10.7 and SU SR4-SuperSU-v2.78-SR4-20161115184928 as well as the Samsung USB drivers. All check sums were fine. Odin 3 installed fine on my PC. I used Odin 3 to install the TWRP on my phone. However, when I try to go into Volume up - home - power on - I get a screen that does not resemble at all what I thought TWRP should look like.
I get the yellow/green Android thingy which says "installing system update" follows by "no command" followed by a screen which says:
Android Recovery
MMB29M.J500FNXXU1BPH1
samsung/j5nltexx/j5nlte
6.0.1/MMB29M/J500FNXXU1BPH1
user/release-keys
Use volume up/down and power. (all in yellow)
Followed by a menu which includes "apply update from SD card" but which doesn't install the SU zip file that I put in the download section of the SD card.
--------
So I am a bit lost and bewildered. Is the menu correct for TWRP? I haven't seen anything on the web or in YouTube that looks at all like what I'm getting. Did TWRP install properly - Odin 3 seemed to think so, but I'm beginning to wonder.
Any help, comment appreciated.
Anne
webelan said:
Hi again, thanks for asking.
I downloaded TWRP from https://www.androidfilehost.com/?w=files&flid=55922, version for SM-J500FN dated May 6, 2016. Also ODIN-v3.10.7 and SU SR4-SuperSU-v2.78-SR4-20161115184928 as well as the Samsung USB drivers. All check sums were fine. Odin 3 installed fine on my PC. I used Odin 3 to install the TWRP on my phone. However, when I try to go into Volume up - home - power on - I get a screen that does not resemble at all what I thought TWRP should look like.
I get the yellow/green Android thingy which says "installing system update" follows by "no command" followed by a screen which says:
Android Recovery
MMB29M.J500FNXXU1BPH1
samsung/j5nltexx/j5nlte
6.0.1/MMB29M/J500FNXXU1BPH1
user/release-keys
Use volume up/down and power. (all in yellow)
Followed by a menu which includes "apply update from SD card" but which doesn't install the SU zip file that I put in the download section of the SD card.
--------
So I am a bit lost and bewildered. Is the menu correct for TWRP? I haven't seen anything on the web or in YouTube that looks at all like what I'm getting. Did TWRP install properly - Odin 3 seemed to think so, but I'm beginning to wonder.
Any help, comment appreciated.
Anne
Click to expand...
Click to collapse
If your phone is looking like that then you have the wrong version of TWRP for the version of android that your using.
I did the same thing.
I hadn't got the time at the mo to find you the correct version but that is the problem for sure.
You want the one by Garnesh Varma which if on the Roms & kernels thread
John
johnhux7 said:
If your phone is looking like that then you have the wrong version of TWRP for the version of android that your using.
I did the same thing.
I hadn't got the time at the mo to find you the correct version but that is the problem for sure.
You want the one by Garnesh Varma which if on the Roms & kernels thread
John
Click to expand...
Click to collapse
Hi john,
Following your suggestion I downloaded the TWRP version http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 by searching for Garnesh Varma. It successfully installed, but the problem remains the same. I do not get the TWRP recovery page just the same as before.
I shall continue to look to see if I can find another version from Garnesh, although it seemed correct ie SM-J500FN Android version 6.0.1 Build number MMB29M.J500FNXXU1BPH1, security patch level 1 August 2016.
Will let you know how I get on.
Thanks again,
Anne
webelan said:
Hi john,
Following your suggestion I downloaded the TWRP version http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 by searching for Garnesh Varma. It successfully installed, but the problem remains the same. I do not get the TWRP recovery page just the same as before.
I shall continue to look to see if I can find another version from Garnesh, although it seemed correct ie SM-J500FN Android version 6.0.1 Build number MMB29M.J500FNXXU1BPH1, security patch level 1 August 2016.
Will let you know how I get on.
Thanks again,
Anne
Click to expand...
Click to collapse
Ahah! The trick was to turn off the phone and not to permit ODIN to do a reboot. I didn't know how to turn off so I pulled the battery. Then went into volume up - home - power on and got the correct menu. Whew. Rooted now according to root checker. Now to get some of the stuff off the phone and make some space.#
Thanks for your help,
Anne
webelan said:
Ahah! The trick was to turn off the phone and not to permit ODIN to do a reboot. I didn't know how to turn off so I pulled the battery. Then went into volume up - home - power on and got the correct menu. Whew. Rooted now according to root checker. Now to get some of the stuff off the phone and make some space.#
Thanks for your help,
Anne
Click to expand...
Click to collapse
Nice one. I'm pleased that you got it sorted !
Next you will be on the custom roms ! If you need any help just shout !
John
@webelan
Hello Anne!
Once you are rooted you can remove any Google/Samsung app. But removing some system apps can lead to bootloop. You can recover from bootloop by re-flashing stock rom.
I can make a flashable zip which removes unnecessary system apps, including the Google/Samsung apps which you want (you flash the zip in recovery and you're done). So let me know which Google/Samsung apps you wanna remove.
You can find some more basic informations in our Q&A thread: http://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-qa-thread-galaxy-j5-series-t3382922 .
I recommend you to try cm 12.1 (5.1.1 lollipop) by Nick Verse if you don't care about Samsung Camera, Memo and Browser. I use Open Camera, Color Note and Dolphin Browser (has sound/brightness sliders in videos) as alternatives. Unlike Touchwiz, CM 12.1 is faster than Touchwiz and has more free ram. But latest release has a bug (random reboot reported by users) which can be fixed manually. I'm running latest release without any problem.
Have a nice day!
Robert.
PS: You have a nice name
more woe
johnhux7 said:
Nice one. I'm pleased that you got it sorted !
Next you will be on the custom roms ! If you need any help just shout !
John
Click to expand...
Click to collapse
Don't know if I should start another thread but...
I used Aps2SD to create a second partition on my phone after making a backup of the SD card using that program. Restored the SD card and then I linked various apps to the new partition. When everything was done, and working, I used the option "Broken ap cleaner" just in case there were any residue files with "select all"
My error may have been to do a hard shutdown afterwards because now I get "Android System There's an internal problem with your device, and it may be unstable until you factory data reset." Then several aps, including a Google app, Photos, CM security and Gmail stop, in fact all those that run automatically at startup. Gmail and Google are on the internal drive now but were previously linked; CM is on the external partition still. The first thing after that I noticed after the hard shut down was that the icons for linked aps had disappeared and the aps keep stopping if I try to run them.
I read the Aps2SD FAQ and followed the two suggestions regard SU, ie "enable su at boot" and disabled "namespace separation" option.
Any suggestions? Should I
(a) do a "factory data reset"
(b) wipe the SD card and partition and completely reinstall the aps I want? Although if Google app is not working don't know if it can be reinstalled as I'm not sure which oneis meant.
(c) Bite the bullet and install a custom rom?
(d) something else?
Any help as usual very much appreciated,
Anne
webelan said:
Don't know if I should start another thread but...
I used Aps2SD to create a second partition on my phone after making a backup of the SD card using that program. Restored the SD card and then I linked various apps to the new partition. When everything was done, and working, I used the option "Broken ap cleaner" just in case there were any residue files with "select all"
My error may have been to do a hard shutdown afterwards because now I get "Android System There's an internal problem with your device, and it may be unstable until you factory data reset." Then several aps, including a Google app, Photos, CM security and Gmail stop, in fact all those that run automatically at startup. Gmail and Google are on the internal drive now but were previously linked; CM is on the external partition still. The first thing after that I noticed after the hard shut down was that the icons for linked aps had disappeared and the aps keep stopping if I try to run them.
I read the Aps2SD FAQ and followed the two suggestions regard SU, ie "enable su at boot" and disabled "namespace separation" option.
Any suggestions? Should I
(a) do a "factory data reset"
(b) wipe the SD card and partition and completely reinstall the aps I want? Although if Google app is not working don't know if it can be reinstalled as I'm not sure which oneis meant.
(c) Bite the bullet and install a custom rom?
(d) something else?
Any help as usual very much appreciated,
Anne
Click to expand...
Click to collapse
It sounds like the app has been corrupted, don't really know how to best advice you.
It sounds like you have to do s factory reset.
I would install a custom ROM.
The only trouble with this is that all the roms have just been shut down so you will have trouble downloading any.
Why model do you have ?
If you want to use a custom ROM pm me and I will send you a link.
The custom roms are much better (in my opinion )
John
Sent from my j5nltexx using XDA Labs
#Henkate said:
@webelan
Hello Anne!
Once you are rooted you can remove any Google/Samsung app. But removing some system apps can lead to bootloop. You can recover from bootloop by re-flashing stock rom.
I can make a flashable zip which removes unnecessary system apps, including the Google/Samsung apps which you want (you flash the zip in recovery and you're done). So let me know which Google/Samsung apps you wanna remove.
You can find some more basic informations in our Q&A thread: http://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-qa-thread-galaxy-j5-series-t3382922 .
I recommend you to try cm 12.1 (5.1.1 lollipop) by Nick Verse if you don't care about Samsung Camera, Memo and Browser. I use Open Camera, Color Note and Dolphin Browser (has sound/brightness sliders in videos) as alternatives. Unlike Touchwiz, CM 12.1 is faster than Touchwiz and has more free ram. But latest release has a bug (random reboot reported by users) which can be fixed manually. I'm running latest release without any problem.
Have a nice day!
Robert.
PS: You have a nice name
Click to expand...
Click to collapse
Hi Robert,
Thanks for the offer. So far I have not deleted anything but have used software to partition my SD card and to move stuff out of internal memory onto it - or rather link it. I managed to mess up a bit but seem to have recovered - or at least got a phone with items I want to use. Next week when I've more time I'm hoping to install a Custom ROM. In the meantime I've spent what little time available trying to read as much as I can so that when I do put a Custom ROM on, it goes right first time.
Best wishes,
Anne
webelan said:
Hi Robert,
Thanks for the offer. So far I have not deleted anything but have used software to partition my SD card and to move stuff out of internal memory onto it - or rather link it. I managed to mess up a bit but seem to have recovered - or at least got a phone with items I want to use. Next week when I've more time I'm hoping to install a Custom ROM. In the meantime I've spent what little time available trying to read as much as I can so that when I do put a Custom ROM on, it goes right first time.
Best wishes,
Anne
Click to expand...
Click to collapse
Hi Anne!
Note that once you flash TWRP, Knox will become 0x1 (initially is 0x0) which means that you void the warranty. In my opinion, I don't care about the warranty because I prefer to have a better experience with my phone. I cannot live without root after I rooted a phone for first time
Regarding the ROM, if you wanna try cm12.1 (which I recommend it, best ROM which is closest to AOSP and never lagged) I'll recommend you to wait some more time because I'll download CM 12.1 sources and build a new update with the help of Nick Verse . He doesn't have enough space on his PC to have both cm12 & cm13 sources. I'm currently trying to extend my Linux partition to have enough space to build though. Is needed about 80gb in total average and I have about 20 and can't resize my partition. I might try to reinstall Linux.
If you have any other question, feel free to ask here (new thread if it's related to something else) or PM me.
Have a nice day!
Robert.
Having a similar issue, i have got my phone so it boots to TWRP 3.1.1-0 but cannot find a ROM file that will install, they all seem to be for j5nlte, even if the file name states j5nltexx. I have tried to ammend/remove the assert lines in the install package to no avail...
any advice would be good
Thanks in advance
PB
ashyx said:
Don't need root for adoptable storage.
Click to expand...
Click to collapse
Then what to do
#Henkate said:
Hi Anne!
Note that once you flash TWRP, Knox will become 0x1 (initially is 0x0) which means that you void the warranty. In my opinion, I don't care about the warranty because I prefer to have a better experience with my phone. I cannot live without root after I rooted a phone for first time
Regarding the ROM, if you wanna try cm12.1 (which I recommend it, best ROM which is closest to AOSP and never lagged) I'll recommend you to wait some more time because I'll download CM 12.1 sources and build a new update with the help of Nick Verse . He doesn't have enough space on his PC to have both cm12 & cm13 sources. I'm currently trying to extend my Linux partition to have enough space to build though. Is needed about 80gb in total average and I have about 20 and can't resize my partition. I might try to reinstall Linux.
If you have any other question, feel free to ask here (new thread if it's related to something else) or PM me.
Have a nice day!
Robert.
Click to expand...
Click to collapse
Please work on camera that is the only thing cm 12.1 lackss thank youu
Hello guys,
I'm a complete novice on rooting or flashing cellphones, I'm just a regular user of a Moto X Play XT1563 (bought in Colombia / South America) that wants to upgrade to Nougat 7.1.2.
I want the 7.1.2 just for a regular usage: apps, internet, bluetooth, NFC, camera, GPS, phone calling and of course a good battery performance.
I want to kindly ask for your guidance in all steps required for the backup and upgrade, so if you can please guide me about the whole process I will appreciate it a lot.
Thanks
jramirezdev said:
Hello guys,
I'm a complete novice on rooting or flashing cellphones, I'm just a regular user of a Moto X Play XT1563 (bought in Colombia / South America) that wants to upgrade to Nougat 7.1.2.
I want the 7.1.2 just for a regular usage: apps, internet, bluetooth, NFC, camera, GPS, phone calling and of course a good battery performance.
I want to kindly ask for your guidance in all steps required for the backup and upgrade, so if you can please guide me about the whole process I will appreciate it a lot.
Thanks
Click to expand...
Click to collapse
Hello!
In short, the process for our phone would be...
0. Backup data.
1. Unlock bootloader. This will void your warranty. Unlocking bootloader allows you to use fastboot mode to flash custom images to your phone from a computer.
2. Flash TWRP Recovery. This is done in fastboot mode. Once you have TWRP, you can flash on to or modify the system partition (and other partitions) of your phone on the go.
3. Format the /system partition to get rid of the existing ROM (stock in your case) and then flash whatever ROM you want. This is done using TWRP.
4. There's no fourth step.
Its pretty straightforward, detailed guides to each of the steps are available in this forum. You should use the Index Thread pinned on the General forum to get the links to the required guides at one place. Use the search if you encounter trouble. Then there's the forum to ask.
DragonClawsAreSharp said:
Hello!
In short, the process for our phone would be...
0. Backup data.
1. Unlock bootloader. This will void your warranty. Unlocking bootloader allows you to use fastboot mode to flash custom images to your phone from a computer.
2. Flash TWRP Recovery. This is done in fastboot mode. Once you have TWRP, you can flash on to or modify the system partition (and other partitions) of your phone on the go.
3. Format the /system partition to get rid of the existing ROM (stock in your case) and then flash whatever ROM you want. This is done using TWRP.
4. There's no fourth step.
Its pretty straightforward, detailed guides to each of the steps are available in this forum. You should use the Index Thread pinned on the General forum to get the links to the required guides at one place. Use the search if you encounter trouble. Then there's the forum to ask.
Click to expand...
Click to collapse
Thanks for your response,
I bought my cellphone two years ago so It already went out of warranty so no issues with that step, I already found the guide to "Unlock bootloader" but before I start with it I would like to ask if after that the phone will be unuseful? I mean, after unlocking the bootloader can I start the phone and continue using it? It's my only cell phone so I want to be aware if I will stay long time uncommunicated.
My second question is about the new ROM I will flash, I've no idea about what "versions" exists or where I can download them... so is there some kind of "most stable" version using Nougat 7.1.2? or some "ROM Reliable supplier"?
Thanks
jramirezdev said:
Thanks for your response,
I bought my cellphone two years ago so It already went out of warranty so no issues with that step, I already found the guide to "Unlock bootloader" but before I start with it I would like to ask if after that the phone will be unuseful? I mean, after unlocking the bootloader can I start the phone and continue using it? It's my only cell phone so I want to be aware if I will stay long time uncommunicated.
My second question is about the new ROM I will flash, I've no idea about what "versions" exists or where I can download them... so is there some kind of "most stable" version using Nougat 7.1.2? or some "ROM Reliable supplier"?
Thanks
Click to expand...
Click to collapse
Unlocking bootloader will wipe all your data (it will trigger Factory Reset on your phone). Other than that, your phone will be 100% usable.
Roms are available in Android Development and Original Android Development sections of this forum. Just check the threads that include [ROM] in their title. You have to decide for yourself which rom suits you the best - read its description and what users say in comments.
jramirezdev said:
Thanks for your response,
I bought my cellphone two years ago so It already went out of warranty so no issues with that step, I already found the guide to "Unlock bootloader" but before I start with it I would like to ask if after that the phone will be unuseful? I mean, after unlocking the bootloader can I start the phone and continue using it? It's my only cell phone so I want to be aware if I will stay long time uncommunicated.
My second question is about the new ROM I will flash, I've no idea about what "versions" exists or where I can download them... so is there some kind of "most stable" version using Nougat 7.1.2? or some "ROM Reliable supplier"?
Thanks
Click to expand...
Click to collapse
As said, after unlocking bootloader the device will be wiped- You will have to reenter your Google account and reinstall applications etc. Not a big deal.
Custom ROMs sometimes take a few iterations until some bugs here and there are ironed out. Sometimes it happens, in others one may end up switching to a complete fresh ROM. In such instances, you will usually have to make a "clean install" (i.e. a factory reset) and then reenter the Google account and reinstall everything again... It sounds irritating, but nowadays it's pretty much straight forward, and if you don't have hundreds of apps it usually is finalized in 10-15 minutes and is semi automatic.
Updating to a newer version of the same ROM sometimes can be "dirty flashed" (i.e. without wiping all your data) so in a couple of minutes you are set up and ready to go. More convenient, but if something isn't working right and you complain in the thread, certain chances are you will be politely asked to make a clean install first amd some users may flame or grill you alive for dirty flashing and complaining at that :laugh:
Most custom ROMs are usually based on either AOSP or Lineage OS (aka LOS) with some custom modifications. The first post in a ROM thread usually mentions all the rich features (or lack of), how to install (pretty much the same: make a backup in twrp, wipe data/system/cache/dalvik, flash ROM zip file, flash Google gapps zip, flash some additional optional zips such as supersu/magisk/whatever for root etc). Then some download links, faq etc.
It's good practice to read the first post (aka OP), then at least the last page to get a feel of the ROM (e.g. see what others are praising or complaining about this or that), then search for specific stuff that may concern you. For example, some ROMs had this cellular data bug that it got disconnected and required restart. You may decide this os crucial for you and choose another ROM, others may use the device for other things and couldn care less about cellular data bug...
Enjoy, it always feels good tp flash a new ROM, a new version . F!ck LeMoto for delaying the update for so long- You may have been waiting for update to Nougat as early as last year's November or October. Well, on custom ROMs it's here for many months!
On the other hand, they usually say stock ROM is more stable, and in many cases it is also true...
Now you know more or les what you're dealing with: free choice vs. waiting forever.
jaibar said:
As said, after unlocking bootloader the device will be wiped- You will have to reenter your Google account and reinstall applications etc. Not a big deal.
Custom ROMs sometimes take a few iterations until some bugs here and there are ironed out. Sometimes it happens, in others one may end up switching to a complete fresh ROM. In such instances, you will usually have to make a "clean install" (i.e. a factory reset) and then reenter the Google account and reinstall everything again... It sounds irritating, but nowadays it's pretty much straight forward, and if you don't have hundreds of apps it usually is finalized in 10-15 minutes and is semi automatic.
Updating to a newer version of the same ROM sometimes can be "dirty flashed" (i.e. without wiping all your data) so in a couple of minutes you are set up and ready to go. More convenient, but if something isn't working right and you complain in the thread, certain chances are you will be politely asked to make a clean install first amd some users may flame or grill you alive for dirty flashing and complaining at that :laugh:
Most custom ROMs are usually based on either AOSP or Lineage OS (aka LOS) with some custom modifications. The first post in a ROM thread usually mentions all the rich features (or lack of), how to install (pretty much the same: make a backup in twrp, wipe data/system/cache/dalvik, flash ROM zip file, flash Google gapps zip, flash some additional optional zips such as supersu/magisk/whatever for root etc). Then some download links, faq etc.
It's good practice to read the first post (aka OP), then at least the last page to get a feel of the ROM (e.g. see what others are praising or complaining about this or that), then search for specific stuff that may concern you. For example, some ROMs had this cellular data bug that it got disconnected and required restart. You may decide this os crucial for you and choose another ROM, others may use the device for other things and couldn care less about cellular data bug...
Enjoy, it always feels good tp flash a new ROM, a new version . F!ck LeMoto for delaying the update for so long- You may have been waiting for update to Nougat as early as last year's November or October. Well, on custom ROMs it's here for many months!
On the other hand, they usually say stock ROM is more stable, and in many cases it is also true...
Now you know more or les what you're dealing with: free choice vs. waiting forever.
Click to expand...
Click to collapse
Thanks for your thoughts,
After reading here and there I finally was able to flash AOSP Extendend v4.4 on my cellphone, it seems to be working fine.
As I said I was not looking something specific I was just annoyed of waiting so long for the official update (it seems it will never happen) and wants to be in touch with Android Nougat, maybe now I will use my piggy bank to save for a Pixel phone
Thanks guys for your guidance
jramirezdev said:
After reading here and there I finally was able to flash AOSP Extendend v4.4 on my cellphone, it seems to be working fine.
Click to expand...
Click to collapse
Hi,
How it is working? Did you found any bugs? eg. problem with battery, with mobile data, lte, camera?
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.