How might one apply the DJ05 update without using Odin v3?
Clearly the ROM and Kernel can be updated through CWM, but all searchable info seems to indicate that the modem file can only be altered via Odin on M$ Windoze. What is the methodology behind applying this kind of change using only tools available on a Linux platform?
Can I just overwrite a file on the Fascinate via adb?
cheers
I have only ever heard of modem.bin being flashed via Odin. I could be wrong, but I think it occupies its own partition, hence the need to actually flash rather than copy an individual file.
You can use redbend_ua to flash without Odin, but I recall (perhaps incorrectly) reading in IRC that redbend doesn't work for modem flashes in practice, at least not yet.
Hopefully someone can give more authoritative info, but I think you are stuck with Odin for good reasons. Just be nice to one of your friends with a PC. Don't have any? Shame! Windows users need love too ya know.
Swyped w/ XDA App. When in doubt, mumble.
Google search keyword: heimdall
Sent from my SCH-I500 using XDA App
Heimdall:
http://forum.xda-developers.com/showthread.php?t=755265
Awesome. That's a good question, why don't we just speak in terms of Heimdall in general... and use that instead? Strangely more soothing to say anyway, like "goos fraba"
You might find post 3 here useful as well.
That thread Soba49 posted is about 60 pages now, but reading through it all will give you a lot of good info on how it works. About page 56 or 57, you will see some specific questions I posed regarding flashing DJ05 modem.bin onto the Fascinate. It's almost too simple to use, so best to understand it as this is also the tool that will be saving your arse if you 'almost' brick your phone.
Heimdall actually emulates Odin in some areas & Kies in others and aims to eventually do more than either of those tools, w/o all the buggy Samsung coding. I believe the modem.bin is flashed using Kies methodology, FWIW.
So, I've been searching all over this forum and through the 60 pages of the Heimdall thread, but can't find an answer to this simple question - how do I just flash DJ05 onto my fascinate from OSX 10.6? When I try to connect in download mode and turn on Heimdall frontend, I just get "no compatible device connected" Do I need to flash bootloaders too or some other complicated stuff? Or am I just missing something easy?
SupraLance - What happened when you commanded: "heimdall flash --verbose --modem modem.bin"?
That command flashed the new modem for me. I am running DJ05 now and my phone has never been violated by a Windows device, lol.
I just re-read a bit of that thread regarding OSX, and it seems that Samsung released these phones with a crappy secondary boot loader. It will communicate with Linux and Windows, but not OSX. The only way around this is to flash a fixed boot loader through Linux or Windows, then you can use OSX from there out. Big problem is the only fixed boot loader verified to work with Heimdall & OSX is for the International Galaxy S. You need one specific for the Fascinate.
So this leaves American OSX users hoping that Samsung fixed this in the 2.2 Froyo code they have released. Heimdall & Odin cannot be made to work on OSX without it and boot loaders are not something you want to experiment with. Messing with the boot loader = quickest way to truly brick your phone.
If I was at your computer trying to do this, I would set up a dual-boot on your Mac with Ubuntu (completely free and similar to OSX interface) and do it through Ubuntu.
Heimdall Success!
fragmented post
Code
fragmented post
Notes on Code.
fragmented post
Next step.
fragmented post
fragmented post
Heimdall Success!
Installed Heimdall 1.1.0 for Debian.
http://www.glassechidna.com.au/products/heimdall/
Flashed modem using:
Code:
heimdall flash --verbose --modem modem.bin
Making sure that SF is in DL mode and the current directory contains "modem.bin" file.
Then flash ROM (and Kernel) via CWM.
Additional possibly helpful info here:
http://mobiletech.knguyentu.com/2010/12/fascinate-rom-dj05-and-beyond-all-you.html
Cheers
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.
Hey guys,
Right now I'm on a custom GPe rom (i9505G). I need to get back to Touchwiz.
You're probably wondering ... why...? Well, last night I bought a Fitbit Flex, and it's supported by GS4 (wireless syncing), http://www.fitbit.com/devices. Could it be because I'm on a custom rom?
Any feedback is appreciated.
Thanks,
gameriot
Yes, it doesn't work because you're on a custom Rom. Fitbit doesn't support it. You can flash the stock firmware in Odin.
Those fitbit's only work on stock or stock-based roms. There's some good ones in the Android Development section. Cheers
jd1639 said:
Yes, it doesn't work because you're on a custom Rom. Fitbit doesn't support it. You can flash the stock firmware in Odin.
Click to expand...
Click to collapse
I have a Mac, so I can't get Odin.
xBeerdroiDx said:
Those fitbit's only work on stock or stock-based roms. There's some good ones in the Android Development section. Cheers
Click to expand...
Click to collapse
I'll check it out. Could you link it?
gameriot said:
I have a Mac, so I can't get Odin.
I'll check it out. Could you link it?
Click to expand...
Click to collapse
Best Touchwiz-based ROM, in my opinion, right here:
http://forum.xda-developers.com/showthread.php?t=2313469
gameriot said:
I have a Mac, so I can't get Odin. I'll check it out. Could you link it?
Click to expand...
Click to collapse
#1. The TW rom that I find best for me is Shostock2.1 It's already very mature, stable and zero issues.
Here's the link if you want another option:
http://forum.xda-developers.com/showthread.php?t=2305752
#2. As to the Mac and no Odin thing. . . . I use a Mac (a couple of them, actually) and found that Heimdal can be made to work, but some folks feel it is not as user friendly/easy to use as Odin. (Btw, you should not need a custom driver to use Heimdal -its a mac and should see your phone w/o driver issues!)
I have used it, but maybe it's just my experience, there have been sometimes when you have everything set up correctly, Heimdal still seems to choke, or just not complete the task (or see the tar file that you want to use!).
Anyway, the newer versions seem better, please check out the current version of Heimdal and the Heimdal front end package?
Here is a Heimdal link in case you want to check: http://www.glassechidna.com.au/products/heimdall/.
The site should have instructions on how to get your file -the stock image or rom image that you want to load and make sure it's the right one and also that its in a form Heimdal can use. . .
Also, here is another very good, informative thread of someone's experience restoring his i337 using Heimdal! It might be helpful (and it is just a few posts down from yours
http://forum.xda-developers.com/show....php?t=2374441
#3. But even on a MAC you CAN use Odin! Odin generally works well and if Heimdal seems to complicated or you can't get it working, then you could open your options up significantly if you can either:
(1) use bootcamp and boot into a windows OS, or
(2) use Parallels/VM Ware Fusion and use windows in a virtual window.
Bootcamp is 100% windows running on your mac and is rock-solid, while the VM machine approach also is mature and pretty good, if occasionally temperamental...
If you can do this, then you can use Odin and work on phone with all the tools that most folks here have and use to good effect.
Good Luck!
markbc01 said:
#1. The TW rom that I find best for me is Shostock2.1 It's already very mature, stable and zero issues.
Here's the link if you want another option:
http://forum.xda-developers.com/showthread.php?t=2305752
#2. As to the Mac and no Odin thing. . . . I use a Mac (a couple of them, actually) and found that Heimdal can be made to work, but some folks feel it is not as user friendly/easy to use as Odin. (Btw, you should not need a custom driver to use Heimdal -its a mac and should see your phone w/o driver issues!)
I have used it, but maybe it's just my experience, there have been sometimes when you have everything set up correctly, Heimdal still seems to choke, or just not complete the task (or see the tar file that you want to use!).
Anyway, the newer versions seem better, please check out the current version of Heimdal and the Heimdal front end package?
Here is a Heimdal link in case you want to check: http://www.glassechidna.com.au/products/heimdall/.
The site should have instructions on how to get your file -the stock image or rom image that you want to load and make sure it's the right one and also that its in a form Heimdal can use. . .
Also, here is another very good, informative thread of someone's experience restoring his i337 using Heimdal! It might be helpful (and it is just a few posts down from yours
http://forum.xda-developers.com/show....php?t=2374441
#3. But even on a MAC you CAN use Odin! Odin generally works well and if Heimdal seems to complicated or you can't get it working, then you could open your options up significantly if you can either:
(1) use bootcamp and boot into a windows OS, or
(2) use Parallels/VM Ware Fusion and use windows in a virtual window.
Bootcamp is 100% windows running on your mac and is rock-solid, while the VM machine approach also is mature and pretty good, if occasionally temperamental...
If you can do this, then you can use Odin and work on phone with all the tools that most folks here have and use to good effect.
Good Luck!
Click to expand...
Click to collapse
I already tried hiemdall. It kept coming up with error whatever I did. Also my TWRP keeps failing when I'm trying to flash. I'm trying goomanager.
Sent from my GT-I9505G using Tapatalk 4
gameriot said:
I already tried hiemdall. It kept coming up with error whatever I did. Also my TWRP keeps failing when I'm trying to flash. I'm trying goomanager.
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
OK, I have been there! If Heimdall does not work, then:
a) find a windows machine for a while or
b) use your machine with bootcamp (if you're on a MBP) or
c) use your machine but install/open a virtual desktop (Parallels or VMware Fusion) to get a windows or linux environment.
Please BE CAREFUL when using goomanager (or Rom Manager, for that matter). These apps are useful, but they also are prone to suddenly creating havoc on the phone - usually when least expected . I have used both -but only very carefully and for limited functions. (I recently used GM to update my TWRP to the latest (I think 2.6?) -no issue --so try that at least!)
But for loading roms, initially loading recoveries or the like it is better to use the "manual" processes that we have available here.
Good Luck!
markbc01 said:
OK, I have been there! If Heimdall does not work, then:
a) find a windows machine for a while or
b) use your machine with bootcamp (if you're on a MBP) or
c) use your machine but install/open a virtual desktop (Parallels or VMware Fusion) to get a windows or linux environment.
Please BE CAREFUL when using goomanager (or Rom Manager, for that matter). These apps are useful, but they also are prone to suddenly creating havoc on the phone - usually when least expected . I have used both -but only very carefully and for limited functions. (I recently used GM to update my TWRP to the latest (I think 2.6?) -no issue --so try that at least!)
But for loading roms, initially loading recoveries or the like it is better to use the "manual" processes that we have available here.
Good Luck!
Click to expand...
Click to collapse
Thanks for the help. I got Touchwiz on my phone and got the sync to work but I just hate Touchwiz and went back by restoring my nandroid. Can't wait till they get Bluetooth 4.0 on custom roms, then it'll work.
Sent from my GT-I9505G using Tapatalk 4
Great..and if you still need a TW Rom, you still can switch launchers to Nova or something like that...
Then you hardly see the Samsung footprint...yet have the TW needed for the device..
Sent from my SAMSUNG-SGH-I337 using XDA Premium HD app
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.