Related
I have an unrooted hero I have had since launch day. I am now thinking about rooting my hero with use of the latest Sprint leak. my understanding is if you update to the leak of even the official builld whenever that may come out, it will close all current rooting holes available. I guess that doesn't mean in the future there won't be other possibilities. do these new build give the same sense of stability as the official roms because we can now use an official 2.1 kernal?
so from what I have been reading there appears to be only one Rom that is based on the current 2.1 leak and that is flipz Rom? I have a few questions or statements before I do anything to my phone. one, will this help get rid of the lag when typing? two, I need to make sure Bluetooth is still going to work as I have a home phone that I connect my cell to when I enter the door. if I decided to flash back to the official release, is that possible?
dbldown768 said:
I have an unrooted hero I have had since launch day. I am now thinking about rooting my hero with use of the latest Sprint leak. my understanding is if you update to the leak of even the official builld whenever that may come out, it will close all current rooting holes available. I guess that doesn't mean in the future there won't be other possibilities. do these new build give the same sense of stability as the official roms because we can now use an official 2.1 kernal?
Click to expand...
Click to collapse
As of right now; many people are cautious about testing the latest 2.1 leak; because of the concerns you expressed earlier -- having your phone unrooted by the 2.1 leak when you flash the new update. So, with that said; the current 2.1 ROM's are all pretty stable. This new leak, however probably is as well, but again... I don't know whose all tested it, for fear of loosing root access.
dbldown768 said:
so from what I have been reading there appears to be only one Rom that is based on the current 2.1 leak and that is flipz Rom?
Click to expand...
Click to collapse
No. Damageless ROM's are also based on the latest Sprint leaks. All ROM's you see should tell which ROM they are based off of. Almost all 2.1 ROM's are currently built from any of the Damageless ROM's -- just read the front page of the ROM you're looking into.
dbldown768 said:
I have a few questions or statements before I do anything to my phone. one, will this help get rid of the lag when typing? two, I need to make sure Bluetooth is still going to work as I have a home phone that I connect my cell to when I enter the door. if I decided to flash back to the official release, is that possible?
Click to expand...
Click to collapse
1. Possibly. The lag problem is relative to the person/device. Not everyone experiences this problem. However, turning off "Vibrate when typing" apparently helps with the lag issues. YMMV.
2. Please see first post I made.
Thanks for the quick reply. I'm investigating the best way of rooting my phone. I see there are a few ways listed on the wiki, but then i just ran across Fresh Kitchen (http://geekfor.me/new-release/fresh-kitchen-105)? This is suppose to root your phone for you? Is this a stable way of rooting or should i just use the command line mehods? Also, i have read that you should do a nandroid backup of your phone? Not sure if fresh is doing this for you? The other thing i should mention is that i just have a stock microSD card, so I dont plan on using app2sd, i dont think this is a problem correct?
I also see people load their roms using their microSD card and just putting some update.zip file on there. Is this the standard procedure once you root your phone and get a rom loaded?
Actually, Fresh 2.1, and 2.1.1 are the only ones as of right based off of the newest leak (signed with release keys rather then test), Damageless and Treve are currently working on improving DCUpdater, DConfig, and building a new ROM from the release-keys build.
As far as how to root, I recommend the command line method. While the auto-root methods are nice, actually doing it yourself will give you some experience with things you're gonna be using.
Yes, loading the update.zip to the root of the SDCard is the standard way to flash.
No, not using Apps2SD is not a problem, most people use it because they have a faster SDCard, which gives better performance when loading apps.
A Nandroid backup is something that you will do before you flash any update.zip (At least you're supposed to). It's basically an "Image" of your phone exactly how it was the point in time that you made it, so if you flash something and everything goes horribly wrong, you can restore said nandroid, and it will be like it never happened. (The exceptions are flashing a radio and screwing with the PRL/PRI, nandroid doesn't touch those.)
dbldown768 said:
Thanks for the quick reply. I'm investigating the best way of rooting my phone. I see there are a few ways listed on the wiki, but then i just ran across Fresh Kitchen (http://geekfor.me/new-release/fresh-kitchen-105)? This is suppose to root your phone for you? Is this a stable way of rooting or should i just use the command line mehods? Also, i have read that you should do a nandroid backup of your phone? Not sure if fresh is doing this for you? The other thing i should mention is that i just have a stock microSD card, so I dont plan on using app2sd, i dont think this is a problem correct?
Click to expand...
Click to collapse
Fresh's kitchen will allow you root your phone and yes it's stable. However, it's best you try doing it via ADB commands, as there will come a time when you'll want to create things for the community and wished you had prior experience using it. I recommend you trying to root via this tutorial HERE If you follow the directions, you shouldn't have any problems whatsoever.
Stock card is perfectly fine; you're able to use Apps2sd, but don't have to.
dbldown768 said:
I also see people load their roms using their microSD card and just putting some update.zip file on there. Is this the standard procedure once you root your phone and get a rom loaded?
Click to expand...
Click to collapse
To try out different ROM's -- the process is to download the file (which is a update.zip file in itself), but has been renamed to match the name of the ROM. All you have to do is; copy to your sd card, boot into recovery, flash ROM from the sd card, reboot.
abcdfv said:
Actually, Fresh 2.1, and 2.1.1 are the only ones as of right based off of the newest leak (signed with release keys rather then test), Damageless and Treve are currently working on improving DCUpdater, DConfig, and building a new ROM from the release-keys build.
Click to expand...
Click to collapse
There's your real answer. Thanks.
I'm having a hard time understanding why i would need the flash recover image in this tutorial (http://forum.xda-developers.com/showthread.php?t=583291)? I understand i would want to do a backup of the current phones state, but why would i flash anything before actually making this backup? Maybe i'm not understanding the process correctly, but i just want to get "su" ability and then do the nandroid backup? Is the nandroid backup an app i use?
Nandroid is built into the recovery image you're flashing. Before flashing the recovery image, there is no way for you to nandroid.
thanks! after watching the youtube video posting that mad more sense. So i know there is a chance of bricking your phone during all of this, where does that chance increase? Is it during the flashing of the customs roms, not so much the rooting process?
It is safe to say once the "official" 2.1 android comes out there will always be a custom rom based on it? meaning that if chosen by developers here there could be a build off the "official" 2.1 with the only difference is the rooted user is still allowed? I know that most dev are going to change the build in someway to "improve" on what the official build is done.
The only proven way to brick this phone is by flashing a GSM radio, or by having a failed RUU. I've never heard of anyone getting a "true" brick from rooting/flashing ROMs.
Yes, once the official build is released, all ROMs from then on are most likely going to be based of off it.
Ok, stupid question. I just followed the guide to rooting my phone, doing the nandroid backup and copying the backup to my pc. There are a lot of guide to root, but how to you actually flash the custom rom? I saw something about holding down the 'home' button when starting up? Does this bring you to the recovery image again? Do the roms have to be named something specifically?
Place the ROM in the root of your sdcard, and boot into recovery by holding Home+Power. From then select the "Flash update.zip" option and it will show all of the .zip files in the root of your sdcard. Just pick which one you want to flash.
great! thanks for all the help.
ok, so i decided to load damage's sprint leak that would still give me root access, well it doesnt boot. just goes to the "sprint now" screen and reboots over and over again? any ideas?
Did you wipe data and Dalvik?
Anytime you go from one ROM version to another (1.5 to 2.1, 2.1 to 1.6, 1.6 to 1.5, etc etc) you have to wipe, or if there's major changes between rom versions.
what do you wipe the data? i just picked the flash from zip file from sd card?
In recovery there's a catagory for wipe. Wipe data and Dalvik, then reflash and you'll be fine.
cool. thanks. trying that now.
so everything is working now. So i know one of the main benefits of having a rooted is phone is wifi teathering. Are apps like this in the market place or only on here?
There's Easytether and PDAnet. I haven't tried Easytether, since last I've heard it's x86 only, but PDAnet was a horrible experience. I just flashed an Eris based ROM, broke my PRI, and it enabled the built in USB tethering.
dbldown768 said:
so everything is working now. So i know one of the main benefits of having a rooted is phone is wifi teathering. Are apps like this in the market place or only on here?
Click to expand...
Click to collapse
go to market and download barcode scanner
open up barcode scanner and go here and then just point the camera at the qr code and it'll download to your phone.
remember to check 'unknown sources' > setting > applications
wifitether 1.6. works flawlessly on either fresh or damageless latest 2.1
Should I root My Samsung Galaxy Note 10.1 ?
Model : GT-N8000
Country : Malaysia
BTW will root cause the Tab to become slow ?
Do I need stock recovery to get OTA ?
As always if you have to ask then the answer is no .
You root when apps or mods require root only .
Root voids warranty ..
This is not the Tab forum do not use any firmware or mods from here on a Tab .
Do I need stock recovery to get OTA
Yes stock and original with no root for OTA .
jje
If you are happy with your Note, than it's not necessary.
I rooted mine, because it was still on 4.0.3, and that is the reason for the many bad reviews on the internet.
After upgrading to 4.1.2, it was like a whole new tablet.
JJEgan said:
As always if you have to ask then the answer is no .
You root when apps or mods require root only .
Root voids warranty ..
This is not the Tab forum do not use any firmware or mods from here on a Tab .
Do I need stock recovery to get OTA
Yes stock and original with no root for OTA .
jje
Click to expand...
Click to collapse
This is not the Tab forum
Click to expand...
Click to collapse
What you mean ? I tot I am at the correct forum ?
ic3tea said:
What you mean ? I tot I am at the correct forum ?
Click to expand...
Click to collapse
You're from Malaysia..me too.
Btw you're in correct forum.When you wrote tab people will confuse it with galaxy tab and root will not slowing down your note.
Sent from my GT-I9100 using xda premium
I actually liked my Note even at 4.0.3.. but I rooted so I could use the Multiwindow manager for multiwindow.. EVERYWHERE!
asdfuogh said:
I actually liked my Note even at 4.0.3.. but I rooted so I could use the Multiwindow manager for multiwindow.. EVERYWHERE!
Click to expand...
Click to collapse
So that I will try and root but BTW just asking is HighXXXXXXXX CMW Recovery good or Darkman Recovery Good ?
TWRP is only for stock rom right ?
There are many benefits to root. All the flashable files here require it.
But technically you will void your warranty.
However there are ways to get back to stock and "unroot" so mostly no one will know the difference if you have to return it.
Both recoveries are good, but HighOnAndroid supported a couple ROMs that Darkman didn't, though I'm not sure this is still the case
blud7 said:
There are many benefits to root. All the flashable files here require it.
But technically you will void your warranty.
However there are ways to get back to stock and "unroot" so mostly no one will know the difference if you have to return it.
Both recoveries are good, but HighOnAndroid supported a couple ROMs that Darkman didn't, though I'm not sure this is still the case
Click to expand...
Click to collapse
How about TWRP Recovery ? TWRP Recovery only work in stoock rom ?
ic3tea said:
So that I will try and root but BTW just asking is HighXXXXXXXX CMW Recovery good or Darkman Recovery Good ?
TWRP is only for stock rom right ?
Click to expand...
Click to collapse
You will need to flash the HighXXXXXXXX CMW in ODIN to get root and cwm. You can then flash either darkman recovery with CWM, TWRP recovery or stay as is..
TWRP recovery isa modified recovery like the other 2 and requires root to use. If you look around you'll find the stock recovery too.
I root my tab with Darkman Recorvey is easy then I tot . Thx you guys .
Sent from my GT-N8000 using XDA Premium HD app
Yes! Rooting is the way to go. There are ways around the warranty issues.
My main reason for rooting is for these essential apps:
Titanium Backup
Ad Blocker
Mobile ODIN
Triangle Away
ROM Toolbox Pro
and many more apps that have useful extended capabilities once rooted.
Some Con's of rooting
1) good mobile app no longer works after rooting.
So if u use good mobile for checking corporate emails, rooting device will break this.
2) there will be some overhead for you to upgrade device when any new firmwares are released. If u are a very busy professional, then this is an overhead you can live without.
3) there are and there always will be chances that you may brick your device.
4) I think u legaly void warranty on device by unlocking it. (I am assuming u want to root to load different firmware)
I am not discouraging.. just givin you other side of the coin.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
smrsxn said:
Some Con's of rooting
1) good mobile app no longer works after rooting.
So if u use good mobile for checking corporate emails, rooting device will break this.
Click to expand...
Click to collapse
Sorry to bump a three month old thread, but would anyone know whether the Lotus Traveler app used for syncing corporate email and calendar works after rooting? Good is trash, so I'm not surprised it wouldn't work. There's not much of a downside finding out for myself by rooting my Note 10.1 because I intend to keep flying stock on my Note 2; but I thought someone might save me the time and trouble.
JasW said:
Sorry to bump a three month old thread, but would anyone know whether the Lotus Traveler app used for syncing corporate email and calendar works after rooting? Good is trash, so I'm not surprised it wouldn't work. There's not much of a downside finding out for myself by rooting my Note 10.1 because I intend to keep flying stock on my Note 2; but I thought someone might save me the time and trouble.
Click to expand...
Click to collapse
For Lotus Traveler - I have no idea. I am unlucky enough to have Lotus Domino for our corporate e-mail and I hate it with a passion.
I have installed and configured Aqua Mail to connect to our Domino server (IMAP) and I can confirm that it works perfectly after rooting. You just need your IT guys to ensure that you have web access enabled. I set mine to check for mail every 15 minutes, if it's more urgent than that then why is it an email anyway.
Rom Noob tips, from a noob, please feel free to correct, add or expand on any points
General rooting options
Titbits
- rooting under normal circumstances shouldnt slow your system, in fact most devs i believe will attempt to make their roms bring out the best performance from that particular tab/phone you may own, throught software optimizations, in cojunction with working as best as it can with your specific hardware, although, sometimes you may have a N8013(american wifi version), the dev may have the n8000(3g version).......n810 is the european wifi version...................weve been mixing and matching rom versions here, i.e. using a n8000 rom on a n8010 hardware, ive done it, as far as i know, no adverse effects, well at least no obvious signs of em
- Usually, the process of flashing a rom will first involve rooting your tablet, and then flashing a recovery, which replaces the official one that may already be on your tab, the official one is usually pretty limited in what you can do, the custom RECOVERY is flashed because it gives you these options, but not limited
-factory reset
used when, flashing new rom, best to use the recovery when ever you wanna factory reset, i dont know if this was a oje of, or just specific to my situation, but ive used the android factory reset on my tf201 asus prime, after having rooted, custom recovery and been running a custom rom for some time, and it soft brick, since thats happenened ive been shy to do it on any android device, which is cool, as the custom recovery is a beatiful thing.......maybe someone can expand on or correct that suspicion
- wipes
cache- wipe your app cache
Davlik - someone gonna have to chime in there
factory/data reset- brings back your android back to its original state, wipes your data, that means, all apps installed, all settings changed
format - allows you to format the different seperate sections of your android rom, example of the different sections would be......kernel, os, sd hardrive ........
nandroid - the best part of a custom recovery in my opinion, the ability to completely back up your rom, settings, apps, homescreens, widgets......essentially, restoring your android EXACTLY where you left off, the few seconds before, it takes to boot into recovery and start the backup procedure..........you can also backup and restore only certain sections of your rom, so you may decide to back up just the kernel, or you may decide to restore, JUST the kernel from a FULL previous backup (that is, all sections backed up, minus, the sd hardrive,
Unless you specifically FORMAT the sd card, it usually wont be touched......id advice caution and reading up, before making a decision to format sd harddrive, with a custom RECOVERY, that may not know the requirements to your android device, i.e. a custom kernel ported from another android device from another company....plus, formatting sd harddrive is not really a thing done all the time, not unless you are thinking about starting from scratch, i mean, REALLY fresh, disclaimer:this would wipe any files you have stored on your android devices, specifically, documents, pics, vids so on so forth
- stock rom
the original android OS shipped with the device
- stock based rom
tweaked stock rom, speed, battery other mods
-CM (CynogenMod)
third party rom, built from the ground up, kinda....there are other different flavors of third party roms, CM is one of them
-when flashing a new rom, it is strongly advised by most devs to wipe cache/davlick and factory reset....before flashing, this helps avoid any conflicts with the previous rom and the new rom......at this point, if you were to reboot, rather then flash the rom, you would have essentially reset the rom to its original state, that means re-entering your wifi, changing settings, installing apps, generally a pain in the ass, if you find your self having to do it to many times in a short period.....titanium backup(root) is your friend, does a good job at backing up your apps and wifi.....havent figured out how to backup the settings i change in the android setting
https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup
-quick boot
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
This free app, is a life saver when your new rom doesnt give you the option to reboot into your recovery, sometime found in hold power button/restart/recovery.......just more quicker then the manual way......especially when your having to google up the hardware method because you've not done it in a while and forgotten......which i believe is power off/hold volume down key/then press hold power button/wait for samsung logo/then let go of all buttons and reapettedly press volume up key untill the recovery shows up.......if you end up in DOWNLOAD mode, hold power to switch off, and repeat the process, changing the volume key, its one or the other, one takes you to the recovery, the other to download mode......so just reverse the volume keys, same method, just up instead of down
- supersu/superuser
installable app, that hands out root permission to apps that ask for root, if you dont expresly give persmision, using a supersu app, the app asking for root permission most likely will not work.... .....this app is installed as part of the rooting process
- afwall+ (free)
third party wifi/3g firewall, requires root........allows you to control what apps are able to use your wif/3g......i think its a passive firwall, as in, it uses very little of your resources, in the way it operates
https://play.google.com/store/apps/details?id=dev.ukanth.ufirewall
- rom flashing
sometimes, if you have already flashed a custom rom, and the dev has released the next version of his custom rom, as long as no drastic changes have been made between the two versions, you are able to flash the new version over the old version, keeping all your settings/apps/homescreen/widgets.......although a cache and davlik wipe is usually suggested if doing so
ive forgotten half of what i was originally going to write, so ill just leave it there before i rack my brains .......goodluck whatever you decide
Yes :good:
if it was me?
yea i would do it. it brings life to an old tablet. the 80XX tablets were abandoned by samsung. there are custom roms for Oreo the latest Android OS for N8000. i have a 8020 but no custom roms at the moment.
Good been waiting a whole 5 years for a reply .
Hi, I need the ROM for this phone, more specifically, the boot.img file, as the current kernel is for the older, Indian revision of the On5, and my revision, the USA version SM-G550T1, seems not to have any copies of its firmware floating around. I'm running an OS for the SM-G550FY, which has no audio or camera support. Even if the version isn't an exact match, if you bought this phone in the USA, new, in 2016, your boot.img will probably work. I need this kernel guys. Please, if someone has an On5 in the USA, can I please get a copy of your boot.img and possibly system.img? I really care about the boot.img.
Thanks guys
-Subsentient
Firstly, did you try the updated ones at these locations:
http://www.theandroidsoul.com/galaxy-on5-stock-firmware-2-86761/
http://firmwarefile.com/samsung-sm-g550fy
Secondly, why exactly do you need the boot.img, what problem do you think it'll solve? Is there any specific issue with your current ROM that you are trying to solve?
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Subsentient said:
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Click to expand...
Click to collapse
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
prahladyeri said:
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Subsentient said:
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Click to expand...
Click to collapse
There you are! I just cannot emphasize enough that why don't you guys backup your existing ROMs before flashing a new one? It hardly takes five minutes with CWM/TWRP recovery.
In any case, what happens when you flash the Indian ROM (5.1.1)? I guess that could be your only option.
Otherwise, you can put a request on the CyanogenMod thread for your particular Samsung model.
For future reference, perform device backups and all the research before flashing a custom ROM, not after the fact.
EDIT
If you can contact Samsung support, see if you can manage to get a stock ROM from them that you can flash using ODIN or something.
I contacted them already, they basically told me to go **** myself. The missing ROM is a result of bad parameters I accidentally put in to Heimdall/ODIN flasher. I wanted to back up, but ironically, my first attempt at installing TWRP is what destroyed my ROM.
I've downloaded the kernel source code from Samsung and I'll try compiling it myself. If I create a working boot.img, I'll post it here.
prahladyeri said:
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
boot.img is where the kernel is stored. I know, I decompressed it.
Subsentient said:
boot.img is where the kernel is stored. I know, I decompressed it.
Click to expand...
Click to collapse
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
prahladyeri said:
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
Click to expand...
Click to collapse
The kernel on this device does not have loadable module support. It's entirely monolithic. And, I'm having one hell of a time building a kernel this thing is willing to boot.
I really would love just to get a ROM from someone else's SM-G550T or SM-G550T1.
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
bandtab said:
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
Click to expand...
Click to collapse
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Subsentient said:
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Click to expand...
Click to collapse
thank you!
however, i can't install twrp to my recovery partition anymore because i got FRP locked, and i can't go into my settings to disable it now. so i think my only option really is via odin. i'll see what i can do with this though, thank you very much. i did have twrp on there before but after i got frp locked i can't go into recovery mode at all.
I've been losing my mind trying to make this work.
I think if I installed the stock recovery.img it may work, but I can't find it in the files you sent. Would you or anyone else be able to make a copy of it for me? I would be eternally indebted to whoever could.
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
holydude92 said:
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
Click to expand...
Click to collapse
unfortunately smart switch is incompatible with this model phone for the time being.
I got four of these from T-Mobile when we switched from Verizon ($120 for 4 lines). Three of our Verizon phones worked well on T-Mobile (after a few APN tweaks), but my dad's old Galaxy S3 barely worked at all, and when it did, only got Edge for data. So I set one of the On5 phones up for him.
Everything was going great. I put the TWRP recovery on it, rooted it, froze all the bloatware, and backed up/restored his apps from the old S3. However, he wanted me to see if I could restore all his SMS/MMS. I tried restoring that, and the stock Messaging app started FC'ing. I installed Textra, which worked (and saw the old messages), but he never received new texts (even though he could send). So I tried removing Messaging and Textra, as well as the SMS cache (which seemed to be in "Dialer Storage (Phone SMS/MMS). I removed it, but now I'm getting an error every five seconds about "com.android.phone" and can't seem to get rid of it. I tried to restore the dialer storage backup again, but it just seems to sit forever without installing.
I've looked far and wide for a stock ROM... hoping I could just put this mess behind me, but I'm surprised to find it is nowhere to be found.
My other alternative would be to fix the com.android.phone error, but nothing seems to fix it.
Which cynogenmod or any custom os suits for Samsung Galaxy on 5.......please tell me guys.....I am bored with this official os
I was really hoping to come back to this forum and finally see stock ODIN files for this phone. I really, really want to get rid of the MetroPCS ROM I used to fix it.
Has anyone been able to find it?
Tracfone version
I'm having no luck with Kingroot. It says no root available for device.
According to 'one-click-root' website, the device has no way of rooting it.
Is there any updated information?
.
device specifics:
model: SM-S920LZAATFN
android: 5.0.2
build: LRX22G.S920LUDU1APK2
hardware version: S920L.03
.
[edit: was hoping to change the title to reflect that this post is about the tracfone version]
TWRP recovery method?
TWRP recovery method?
I've read that a phone may possibly be able to be rooted by using odin to download a TWRP recovery, then booting into that new recovery using hardware keys, instead of rebooting normally. And this results in a rooted phone?
I think I have seen a TWRP that may work with this phone. Any help is appreciated. I'd like to be able to update this thread to include a step by step approach to this and other versions of the same model 920.
I'll continue to post updates as I discover more information.
DIY time : crash course in brain surgery
Ok, so I've read a bit of stuff in the forums on the SM-S920L, mostly about the StraightTalk variant, which apparently uses the same system rom, though I'm not so sure.
At any rate, rather than just throw carp at the phone and hope it sticks, I'm going to teach myself how to do it all myself, a-z, 1,2,3... etc., starting with making stock images of the various components, for recovery purposes. Perhaps the phone can be used as a TracFone again someday, though I have no desire to do so, having already bought another for cheaper that even works better, though not as fancy, just newer.
So, I'll leave it here for now and just update the primary with new information as I discover it, starting with the extraction of the stock images, hopefully without goofing up the phone, lol.
This is an unpopular phone, at least for hackers. But it will be a good tool for expanding my knowledge.
Any help appreciated, such as, 'Is this even necessary? There are files here here and here that will do it all'.
(lol, nope... so far I've discovered there is no root option, kingroot no work, etc. There seems to be no posts with information specifically regarding the TracFone 'variant' of this model. It suggests that i can use the StraightTalk files for it, which may work, but there are many questionable unanswered problems.)
friimynd said:
Ok, so I've read a bit of stuff in the forums on the SM-S920L, mostly about the StraightTalk variant, which apparently uses the same system rom, though I'm not so sure.
At any rate, rather than just throw carp at the phone and hope it sticks, I'm going to teach myself how to do it all myself, a-z, 1,2,3... etc., starting with making stock images of the various components, for recovery purposes. Perhaps the phone can be used as a TracFone again someday, though I have no desire to do so, having already bought another for cheaper that even works better, though not as fancy, just newer.
So, I'll leave it here for now and just update the primary with new information as I discover it, starting with the extraction of the stock images, hopefully without goofing up the phone, lol.
This is an unpopular phone, at least for hackers. But it will be a good tool for expanding my knowledge.
Any help appreciated, such as, 'Is this even necessary? There are files here here and here that will do it all'.
(lol, nope... so far I've discovered there is no root option, kingroot no work, etc. There seems to be no posts with information specifically regarding the TracFone 'variant' of this model. It suggests that i can use the StraightTalk files for it, which may work, but there are many questionable unanswered problems.)
Click to expand...
Click to collapse
Definitely don't use kingroot.
Do you have a laptop or pc? If so I can help you out. I have the same phone. Mine is straight talk, but it's sm-s920l a tracefone just through straight talk.
c3p0u812 said:
Definitely don't use kingroot.
Do you have a laptop or pc? If so I can help you out. I have the same phone. Mine is straight talk, but it's sm-s920l a tracefone just through straight talk.
Click to expand...
Click to collapse
Ya I got the straight talk, I have been using king root but I totally bricked and wiped my phone on purpose because I wanted to start fresh and let it update. Having a problem though I used twrp and nuked all my ****, or so I thought. I'm trying to OTA update I'm currently on 5.0.2 and it's saying I have a system update and even after I checked everything to be deleted it still says error and one of my files is modified or some**** like that. I think it's like admin.prop so **** it. I do however want to go systemless root. What do you suggest is the best root and rom for our device?
To answer op question yes your phone is the same as ours. Mine even shows tracphone on boot.
Inuyashian said:
Ya I got the straight talk, I have been using king root but I totally bricked and wiped my phone on purpose because I wanted to start fresh and let it update. Having a problem though I used twrp and nuked all my ****, or so I thought. I'm trying to OTA update I'm currently on 5.0.2 and it's saying I have a system update and even after I checked everything to be deleted it still says error and one of my files is modified or some**** like that. I think it's like admin.prop so **** it. I do however want to go systemless root. What do you suggest is the best root and rom for our device?
To answer op question yes your phone is the same as ours. Mine even shows tracphone on boot.
Click to expand...
Click to collapse
Well for our phone there is only one custom ROM and it's LineageOS 13.0 https://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-13-0-galaxy-t3491494 It's android 6.0 and it can be rooted too. It's not being updated anymore for our device as far as I know. There is Lineage 14.* but not for our variant.
For systemless root you'll want to go with Magisk. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 I had Lineage, and don't get me wrong it's worth checking out, but I downgraded back to stock and went with Magisk. You can even get Xposed throughMagisk.
If I was you, I would flash back to stock. You can go to this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and download the first two, Stock Boot and Stock Recovery. Make sure to unzip them because you need the md5 files they extract. I'd wipe everything again and then get into download mode. On your PC fire up Odin, I'm using version 3.10 http://odindownload.com/download/clean/Odin_3.10.0.zip Click BL use the stick boot md5 and then under ap use the stock recovery md5. When it reboots and you set it up do not turn reactivation lock on.
If you don't already have Magisk on your sd card get it on there and install through twrp. It will ask if you want to root. Might make a back up after. I always make backups and then transfer from sd to my pc. I can restore to like 6 different versions of my phone right now lol I'm no expert, I haven't been messing around with all this for long so I hope that all makes sense. :fingers-crossed:
c3p0u812 said:
Well for our phone there is only one custom ROM and it's LineageOS 13.0 https://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-13-0-galaxy-t3491494 It's android 6.0 and it can be rooted too. It's not being updated anymore for our device as far as I know. There is Lineage 14.* but not for our variant.
For systemless root you'll want to go with Magisk. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 I had Lineage, and don't get me wrong it's worth checking out, but I downgraded back to stock and went with Magisk. You can even get Xposed throughMagisk.
If I was you, I would flash back to stock. You can go to this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and download the first two, Stock Boot and Stock Recovery. Make sure to unzip them because you need the md5 files they extract. I'd wipe everything again and then get into download mode. On your PC fire up Odin, I'm using version 3.10 http://odindownload.com/download/clean/Odin_3.10.0.zip Click BL use the stick boot md5 and then under ap use the stock recovery md5. When it reboots and you set it up do not turn reactivation lock on.
If you don't already have Magisk on your sd card get it on there and install through twrp. It will ask if you want to root. Might make a back up after. I always make backups and then transfer from sd to my pc. I can restore to like 6 different versions of my phone right now lol I'm no expert, I haven't been messing around with all this for long so I hope that all makes sense. :fingers-crossed:
Click to expand...
Click to collapse
Haha ya it does I just wish they didn't treat our phone like it has Ebola or some****. All kinds of **** for the other ones. I agree on the magisk because I really want to try that out. Alright thanks for all the helpful links I come to this site to find **** for ours and I end up looking at a bunch of cool stuff I can't have.
I'm waiting on the pixel 2 XL before I upgrade. We just missing out on too much stuff. I think magisk will keep me busy in the meantime though. Thanks again man I'm Soo add once I get here on all the stuff then I wonder well will this work or this work and by then just like awwww **** it.
Inuyashian said:
Haha ya it does I just wish they didn't treat our phone like it has Ebola or some****. All kinds of **** for the other ones. I agree on the magisk because I really want to try that out. Alright thanks for all the helpful links I come to this site to find **** for ours and I end up looking at a bunch of cool stuff I can't have.
I'm waiting on the pixel 2 XL before I upgrade. We just missing out on too much stuff. I think magisk will keep me busy in the meantime though. Thanks again man I'm Soo add once I get here on all the stuff then I wonder well will this work or this work and by then just like awwww **** it.
Click to expand...
Click to collapse
Hey, I thought I'd let you know LineageOS 14.1 is available to us now. I can't find a specific thread on it, but you can download it from http://grandprime.ddns.net/jenkins/job/LOS_Builds/# Flash it with twrp. You will want to flash that and then flash open gapps [ARM - 7.1] and then whichever from here http://opengapps.org/ I did all that first, set it up rebooted and then installed Magisk.
It has Substratum pre-installed and it let's you theme it nicely. There is only an unofficial xposed version so far.
Anywho, thought I'd throw that out there.
thanks for the replies, gives me inspiration to keep on trying; the phone is pretty ho-hum with default stuff and the general blah blah of social media, etc.;
thanks for the tips, feel free to post more details as they come in
My Turn
I'm about to try and put 14.1 and Magisk on mine. Wish me luck!
downloading twrp recovery and rooting
in google search up twrp click on the first link then click on devices on the top right corner then search up your phone download the twrp.img.tar file
power off your phone and press volume down + home button + power button to boot into download mode
in odin select AP then select the twrp.img.tar you downloaded then press start
your phone will reboot then download the SuperSU zip file
then go to settings then go to find my mobile you have to get a samsung account then you will see reactivation lock option turn that off
then power off your phone then press volume up + home button + power button to reboot into twrp recovery
once booted tap the install option then select where you downloaded the supersu zip file swipe to flash it once done flashing you will see the reboot system option to reboot your phone
then your phone should be rooted!
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.