Related
FIRST TRY... Edited system.img (KERNEL 2.6.36.3 only!!!)
WARNING: ONLY USE THIS IF YOU HAVE A BACKUP OF YOUR /DEV/BLOCK/MMCBLK0P3 IF YOU DONT HAVE ONE YET, MAKE ONE BY USING THIS:
IF FROM ADB:
ADB SHELL
SU
IF=/DEV/BLOCK/MMCBLK0P3 OF=/SDCARD/SYSTEM.IMG
IF FROM TERMINAL EMULATOR:
SU
IF=/DEV/BLOCK/MMCBLK0P3 OF=/SDCARD/SYSTEM.IMG
THIS IS A FUNCTIONAL FILE SYSTEM, I AM WORKING ON A CUSTOM ROM WITHOUT HAVING TO HAVE THE BOOTLOADER UNLOCKED.
THE ONLY THING THAT HAS CHANGED ON THIS SYSTEM.IMG IS THE BOOT ANIMATION (INSTEAD OF "ANDROID" IT HAS THE HONEYCOMB BEE) AND THE FONT HAS CHANGED ALSO...
AGAIN, THIS IS JUST A TEST, IT IS THE FULL FILE SYSTEM TO BE USED ON A DAILY BASIS BUT DOES NOT HAVE ANY OPTIMIZED FILES AT THIS TIME.
Alright, now that you have read the warning... download this file here:
LINK = http://www.megaupload.com/?d=1YZSDVZI = LINK
You can then push the file through ADB by typing:
dd if=/sdcard/blk0p3_sys.img of=/dev/block/mmcblk0p3
Post if it worked for you or if it did not, this will help me troubleshoot...
PLEASE MAKE SURE THAT YOU MAKE A BACKUP OF YOUR FILES FIRST!!! THIS FILE IS BASED ON USA MODEL 1.104.05_GEN1 ACER A500. I RECOMMEND TO TRY ONLY IF YOU HAVE HAD TO UNBRICK YOUR TABLET BEFORE. I DONT WANT TO MESS UP YOUR TABLET!!! YOU HAVE BEEN WARNED!!! JEJEJE
Please post if it has worked for you or if it glitched, I am currently in trial and error so... my tablet gets bricked 1-3 times a day because I am testing different things on the system images... hopefully, I can find a way to have root on the image or at least include:
1. File manager
2. ROOT or at least the Gingerbreak.apk already installed.
3. Terminal emulator
4. Custom background upon boot
As stated, it works for me but I have only 1 tablet so if you are daring enough, please dont hessitate to help me in getting this up and running...
I AM NOT A DEVELOPER SO PLEASE BARE WITH ME AS I AM TRYING TO LEARN AS I GO... JEJEJE
props to you!
u crazy.
I don't see any attachment or link...
Euclid's Brother said:
I don't see any attachment or link...
Click to expand...
Click to collapse
Sorry about that, i've updated the post... jejeje
Beta Rom
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
tomlogan1 said:
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
Click to expand...
Click to collapse
THANKS!!! this is what I am needing... at this time, there is NOTHING ELSE that has been changed on the file system... I am just testing making sure that my changes stick... I am hoping to be able to change some more things... As long as its working... I will continue changing things ... Until I can get an image that is worthy of "Custom ROM" status... jejeje
tomlogan1 said:
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
Click to expand...
Click to collapse
Did you fix your issue if you haven't I'm on gtalk if you want help I pulled my hair out for 2.5 days before I fixed it
Sent from my A500 using XDA Premium App
cant figure out how to multiquote as clicking the buttons dont do anything.
but just look at "Crsdr37"'s post in general with the imgs and update zip to get back to stock and updates!!!
and to the person who made the IMG keep up the good work. im not gonna flash it and im happy with being stock and getting updates now ;D
Have you figured out how to apply the incremental updates to the img?
I suspect it's just replacing files, I'll look at it when I get to a PC.
Ive been away from my tablet today. I put the post up and went out tonight... jejeje
Thank you guys that tested my image... if it worked for you, THANKS!!! if ou didnt, then let me know what did not work...
THIS IS NOT NOT NOT AN UPDATED IMAGE, IF YOU CHECK THE DESCRIPTION, THIS IS A TEST IMAGE TO GET A CUSTOM ROM OVER TO THE ACER A500... I AM TESTING SO I WILL NOT ANSWER QUESTIONS ABOUT UPDATES... THAT IS FOR MY OTHER POST... SORRY PEOPLE.
Never did. Am back now on the EMEA version and going to wait until someone cracks the code. I have reflashed so much I can do it with my eyes closed.
i am going to try it as well nice thing you guys do
Great
Cheers man, !
So, pulling your system image from /DEV/BLOCK/MMCBLK0P3, then modifying it, then pushing it back works?
Let me try and understand here:
I thought the whole locked bootloader thing checked signatures on the images that are about to be loaded into memory, such as the image in /system.
According to this:
http://www.reddit.com/r/Android/comments/hkbf3/so_you_want_to_know_about_bootloaders_heres_the/
It says:
What does a bootloader do with digital signatures?
It uses them to check any update that passes through it.
So: dd any partition we want to modify, back it up in a safe place, mount the img we get from that, make changes within the img, and dd it back, = all good?
ie: signed bootloaders only have to do with installing update.zips on the sdcard?
Can someone clear this up for me?
Thanks!
Unfortunately, I don't know how to answer that... I have to make my changes through the tab and then pull the system.img. Everytime I make edits externally, my tablet crashes... That's why I'm in testing right now.
sorry guys, I'm not a developer so there are going to be some things I can't answer but if someone is willing to explain it, please do as it is a learning experience for us all... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express
If you'd read my question before making an all-caps rude response you'd see that I was asking if you've made any headway into applying the updates, not if you had already done them.
netham45 said:
If you'd read my question before making an all-caps rude response you'd see that I was asking if you've made any headway into applying the updates, not if you had already done them.
Click to expand...
Click to collapse
Dude, chill man... You are right, your question does ask about headway for the updates but here are the facts:
You are asking about updates on a BETA Rom that is just in testing...
I took your question to be if the ROM file had the updates (My fault for sure). I was not yelling per say nor trying to be rude but rather making sure that people are aware this is in no way an updated image and should not be treated as such... THIS IS A TEST ROM and since your question was posted within its thread, I took it as if it was directed to the image itself and not toward me and my development...
Look, as stated, im not a developer man, this stuff is a little hard for me to do. I do apologize because I did not answer your question correctly/completely but as far as the comment... Its what I meant. jejeje
tomlogan1 said:
Never did. Am back now on the EMEA version and going to wait until someone cracks the code. I have reflashed so much I can do it with my eyes closed.
Click to expand...
Click to collapse
Have restored to complete US stock. Had a lot of problems related to SD cards, had to swap them out to avoid errors on the actual update.zip file, but am back to normal. Now if I can just keep my hands off until the 3.1 update comes out, or there is custom ROM...
mapaz04 said:
Unfortunately, I don't know how to answer that... I have to make my changes through the tab and then pull the system.img. Everytime I make edits externally, my tablet crashes... That's why I'm in testing right now.
sorry guys, I'm not a developer so there are going to be some things I can't answer but if someone is willing to explain it, please do as it is a learning experience for us all... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express
Click to expand...
Click to collapse
That's what I've doing for a while now....I guess I should have shared xD
been installing custom fonts and trying to change some of the system settings from other customized roms directly from the tablet.
Instead of reflashing wouldn't it be easier to just provide the files to push into the tablet? just my 0.02
Yeah, I can provide files for you guys to install but what I was going for was an image that contained everything already setup so you can just flash it over ur old one allowing the "customization" to appear upon install/pushin the file... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express
ok, this method does not work - there was an attempt to flash a rooted system.img.ext4 image from a developer edition to a retail, it failed... with the exception of the members of this forum who verified that this method did not / does not work (thanks to all) the following set of instructions does not work...
again, sorry -
Note: I am not responsible for anything that might happen to your device. Please make a backup if possible or please make sure you know how to restore your phone back to factory using the correct stock roms. This Note 4 Developer forum does have resources to do so. Before proceeding below, please ensure you have tried to restore from stock roms via ODIN 3.09 (or correct version), as it may be the only way to recover your device.
The post here suggests (but untested / verified on a retail Verizon Note 4 NJ5) that a system.img.ext4 image, with root (Super SU), can be flashed using ODIN 3.09 to a retail device. I ask more experienced developers to try this first, and post your responses here. I will cite / note the steps which I have done below. I really hope other developers assist in the verification process - let me know if this works or not. I will pull this post if in fact this process fails
Using EFS Professional v2.1.80 Beta and a Verizon Note 4 Developer Edition SM-N910V, on the 4.4.4 version N910VVRU1ANJ5, did the following.
0. Restored the SM-N910V (Developer) to near stock - the only thing different was the recovery partition which had been previously flashed to TWRP
1. Downloaded UPDATE-SuperSU-v2.16.zip from this post (also where TWRP came from), and with my Note 4 connected to a PC, copied the zip file to the phone; rebooted into recovery, flashed Super SU with TWRP. Now it's rooted, right? restarted phone. Installed Busybox (required by EFS Professional), prompted me for root access, permission granted. Busybox ran. Good.
2. - instruction no longer available...
3. Using TWRP, reflashed my phone back to stock before root. Used ODIN 3.09 with my phone in download mode, flashed the SM-N910V_2015130_0116.tar back to my Developer edition, performed a factory reset, rebooted, did a minimal phone setup (bailed out of setup when I could) but Used the busybox.apk (stericson) to test root; installed it using the unknown resources option, ran it, it asked for root, I assume this was a sign that the ODIN flash went well and root held...
So, what remains - asking the developer community to test flashing the SM-N910V_2015130_0116.tar on a retail device using ODIN AP Mode, I do not have one to test...
Here is what I'm hoping for. That the SM-N910V_2015130_0116.tar can be successfully flashed to a retail device, which will then be fortified with root, yes. Maybe that can lead to the "promised land" where a developer, again - more talented than me, can find a weakness in the retail version, from within, to obtain root by other means; unless what I have done, is it!! If it is. Excellent...
If this does work on a retail verizon Note 4 (NJ5), excellent, glad to have helped. If there is a bounty due, ok, I suppose I could accept but not expecting it. I am more excited to give back to the community who has so given their precious time / resources... and so it goes...
Again, please let me know if this worked. I will down this thread immediately if it is detrimental to devices...
Rob
Bump for our possible savior!
Sent from my Note 4.
thanks
Subiegsr said:
Bump for our possible savior!
Sent from my Note 4.
Click to expand...
Click to collapse
Well, thanks, but not yet... And I'm just a measly Note 4 user who spent 700 bones on a device, had some willingness to try something different. actually, it was more common, right? I have seen other developers like beanstown106 (Nathan) and hsbadr do similar, in just handing us a pre-rooted system image only. Hey, if it's a minimum, great - it's a start. I cannot really take credit in that sense, but thanks for the sentiment just the same... greatly appreciated.
We really have to hope that the system.img.ext4 in that flashable package can be put onto a retail - let the games begin (keeping fingers crossed..)
thanks
Any testers yet? I will later today if no one tries before me.
Sent from my SM-N910V using XDA Free mobile app
This won't work. The reason it went okay on your device is because it's a DE with an unlocked bootloader. On retail, it won't boot.
bobbarker2 said:
This won't work. The reason it went okay on your device is because it's a DE with an unlocked bootloader. On retail, it won't boot.
Click to expand...
Click to collapse
ok, that's what we need to find out. what about the image will the retail edition not like?
comment - I remember flashing different modems on a locked note 3, that worked but at the same time I do remember flashing different boot or recovery on a note 3 and it not starting ( validating your claim here... ) - would it be like that experience?
here was my thinking:
1. the worst that'd happen is, yes the phone won't start, but not a brick per se, as Samsung unit's are pretty resilient, and a re-odin of the original system.img.ext4 ( belonging to the retail ed. ) can be easily restored, right?
2. this is an Identical version that goes on both phones, and correct me if I am wrong but the system partition can be flashed on both ( getting that sense looking at hsbadr's thread - to be clear, not that he said it would, he has not indicated that in any post, just my interpretation of what is flashed between the two phones )
lastly, if in fact it does not work, I will simply pull / close this post - with a final comment / statement and we move on.
thanks for your information, this is what we need to know...
anticloud said:
ok, that's what we need to find out. what about the image will the retail edition not like?
comment - I remember flashing different modems on a locked note 3, that worked but at the same time I do remember flashing different boot or recovery on a note 3 and it not starting ( validating your claim here... ) - would it be like that experience?
here was my thinking:
1. the worst that'd happen is, yes the phone won't start, but not a brick per se, as Samsung unit's are pretty resilient, and a re-odin of the original system.img.ext4 ( belonging to the retail ed. ) can be easily restored, right?
2. this is an Identical version that goes on both phones, and correct me if I am wrong but the system partition can be flashed on both ( getting that sense looking at hsbadr's thread - to be clear, not that he said it would, he has not indicated that in any post, just my interpretation of what is flashed between the two phones )
lastly, if in fact it does not work, I will simply pull / close this post - with a final comment / statement and we move on.
thanks for your information, this is what we need to know...
Click to expand...
Click to collapse
As bobbarker2 said two posts above it worked for you because you have a unlocked DE device. Authorization fails without the proper signature on the retail phone. This can only be attained from Samsung or Verizon. Thanks for trying but it's a no go.
EDIT: Yes, I did try to flash it on the retail version.
thanks.
howellcp said:
Any testers yet? I will later today if no one tries before me.
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
I saw bobbarker2's comment - thinking it won't work. I'd say, as long as you can reflash / recover your phone back to normal / working condition, go for it. My comment to bobbarker2 was that this may be worth a shot. I'd try it as long as I had a way to recover. I am not thinking this will lock a phone or anything like that, just make it not boot, like he claims, and a recovery of what should be on the phone will make it right...
Like I suggested to bobbarker2 - I am thinking this would flash and possibly boot (be ok) as it is just the system image, not any other file, and more so, I think it's the same system that goes on the retail and the developer. I am not knowledgeable enough to know yet (some might think dangerous enough) for sure, but just the same that's why I asked someone who has more knowledge than I, and I suspect you and bobbarker2 are better suited than I to know, plus, if it were that easy, it'd already be done this way, right? or is it the case where not too many people have a both a retail and a developer edition to find out on their own, it's a medium but recoverable risk.
just my two cents - proceed with caution.
The file won't flash. It gives an auth error in Odin.
gotcha.
Misterxtc said:
As bobbarker2 said two posts above it worked for you because you have a unlocked DE device. Authorization fails without the proper signature on the retail phone. This can only be attained from Samsung or Verizon. Thanks for trying but it's a no go.
Click to expand...
Click to collapse
ok, thanks - now I know, all in favor of closing this set of posts?
I will also pull the download too, to be safe.
ok.
WarlockLord said:
The file won't flash. It gives an auth error in Odin.
Click to expand...
Click to collapse
now I know.
thanks
sorry guys, chalk one up for too much knowledge not enough experience (referring to me )
anticloud said:
now I know.
thanks
sorry guys, chalk one up for too much knowledge not enough experience (referring to me )
Click to expand...
Click to collapse
No need to be sorry, thanks for trying.
So the whole reason I rooted this damn phone was to be able to install working stock apps. Not just the Music and Gallery apps either--ALL THE LG APPS. Which LS997-compatible 100%-working ROM can I flash and get them all, if any? I keep hearing one exists, but no one bothers sharing that info and when I search I find nothing.
Really? No one?
bgibson72 said:
Really? No one?
Click to expand...
Click to collapse
Look in the development section it's like the 5th one down has ls997 in the title
@bgibson72
Im the only person developing a STOCK LS997 rom currently.. It contains the LG base apps and all the removed ones that we didnt get shipped with out model . Includes a ton of extras as well, alternatively we have 3 or 4 aosp roms you can use, but make sure you use twrp and backup your efs before flashing as it tends to jumble your programming up and cause issues. Otherwise you can flash the stock rom the Dev who provided the dirty santa unlock method.
Theres a good bit of info here to locate everything you need to have a awesome experience with the LG V20!
My link
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
READ THE ENTIRE FIRST 3 POSTS!!! A LOT OF TIME WENT INTO THIS TO CLEAR UP ANY CONFUSION!
I also itemized a list of 15 or so mods and add-ons that we can use to increase our enjoyment with perspective links to their home locations and the devs that built and maintain them.
jerrycoffman45 said:
Look in the development section it's like the 5th one down has ls997 in the title
Click to expand...
Click to collapse
This one?
{ROMS}[LS997] Stock-ish Magisk+3minit+ModControl 3/10/17
Other than DirtySanta, this is the only other one with LS997 in the title on that page. I'll give it a shot, and thanks for answering.
Team DevDigitel said:
@bgibson72
Im the only person developing a STOCK LS997 rom currently.. It contains the LG base apps and all the removed ones that we didnt get shipped with out model . Includes a ton of extras as well, alternatively we have 3 or 4 aosp roms you can use, but make sure you use twrp and backup your efs before flashing as it tends to jumble your programming up and cause issues. Otherwise you can flash the stock rom the Dev who provided the dirty santa unlock method.
Theres a good bit of info here to locate everything you need to have a awesome experience with the LG V20!
My link
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
READ THE ENTIRE FIRST 3 POSTS!!! A LOT OF TIME WENT INTO THIS TO CLEAR UP ANY CONFUSION!
I also itemized a list of 15 or so mods and add-ons that we can use to increase our enjoyment with perspective links to their home locations and the devs that built and maintain them.
Click to expand...
Click to collapse
Hey thanks--I was fairly sure this was the ROM in question. Thank you for providing this! I was hesitant to flash because I'm always a little skeptical about the amount of help I'll get should I get stuck. I'm not exactly a noob at this, but I have plenty to learn. It looks like you've done a lot of work to provide a positive experience, so I'll give it a shot and see how it goes. I promise to read and re-read the instructions on the first 3 posts, and to NOT bother you with questions that have already been addressed in the thread. . Thanks!!
bgibson72 said:
Hey thanks--I was fairly sure this was the ROM in question. Thank you for providing this! I was hesitant to flash because I'm always a little skeptical about the amount of help I'll get should I get stuck. I'm not exactly a noob at this, but I have plenty to learn. It looks like you've done a lot of work to provide a positive experience, so I'll give it a shot and see how it goes. I promise to read and re-read the instructions on the first 3 posts, and to NOT bother you with questions that have already been addressed in the thread. . Thanks!!
Click to expand...
Click to collapse
if you made it through dirty santa the rest should be cake. 99% of the issues i covered for people were
after going to AOSP and not having a backup of their programing info in their efs and having to find a way to
manually go in and fix each fd up piece.
The other is being on older software and downloading a OTA and rebooting with it in your internal storage.
This one causes a endless boot loop into twrp, so be advised to delete the update if your on older software or be prepared to
hit my post # 3 for fixes and be near a pc as you need to fastboot erase the fota and misc directories to resolve the boot loop. A twrp wipe will not fix it and restores etc wont either lol.
Otherwise theres now a lil over 100 pages of chatting and troubleshooting, fixes and things that have gone on, and mostly its all outdated as ive provided the fixes for 99% of everything in the latest version 7.5
Just be prepared to take 15-20 minutes for the phone to boot up the 1st time. My rom is deodexed, and the 1st boot is doing 298 things before you get to the optimization part. There is not boot animations as the phone will always have the static screen issue on reboots so i went ahead a placed a disabled command there to just save time/batt life. The setup wizard is stripped and only there to give you the notice its done booting and time to get to playing around.
Magisk is kinda finicy being its systemless design. It takes some time to get used to it, and be aware that some older apps that dont support exotic root or systemless root may not request root and not fully work. Titanium backup is one i know is getting attacked by googles app scanning and needs to have that turned off before it will work, most of my apps have a option to set "force root" so it asks for a root request regardless if it understands MagiskSu's root methods.
just some food for thought. Hope everything goes well, and there is a ton of people on the forum here that have great knowlege and can help with troubleshooting issues you may have
Team DevDigitel said:
if you made it through dirty santa the rest should be cake. 99% of the issues i covered for people were
after going to AOSP and not having a backup of their programing info in their efs and having to find a way to
manually go in and fix each fd up piece.
Click to expand...
Click to collapse
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
The other is being on older software and downloading a OTA and rebooting with it in your internal storage.
This one causes a endless boot loop into twrp, so be advised to delete the update if your on older software or be prepared to
hit my post # 3 for fixes and be near a pc as you need to fastboot erase the fota and misc directories to resolve the boot loop. A twrp wipe will not fix it and restores etc wont either lol.
Click to expand...
Click to collapse
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
Otherwise theres now a lil over 100 pages of chatting and troubleshooting, fixes and things that have gone on, and mostly its all outdated as ive provided the fixes for 99% of everything in the latest version 7.5
Click to expand...
Click to collapse
That's what I like to hear! :good:
Just be prepared to take 15-20 minutes for the phone to boot up the 1st time. My rom is deodexed, and the 1st boot is doing 298 things before you get to the optimization part. There is not boot animations as the phone will always have the static screen issue on reboots so i went ahead a placed a disabled command there to just save time/batt life. The setup wizard is stripped and only there to give you the notice its done booting and time to get to playing around.
Click to expand...
Click to collapse
Appreciate the heads up. Familiar with the long boot process from DS, lol.
Magisk is kinda finicy being its systemless design. It takes some time to get used to it, and be aware that some older apps that dont support exotic root or systemless root may not request root and not fully work. Titanium backup is one i know is getting attacked by googles app scanning and needs to have that turned off before it will work, most of my apps have a option to set "force root" so it asks for a root request regardless if it understands MagiskSu's root methods.
Click to expand...
Click to collapse
Magisk is a new animal for me, as I've had zero experience with it. I do have Titanium Backup installed, so I'll make a mental note on that.
just some food for thought. Hope everything goes well, and there is a ton of people on the forum here that have great knowlege and can help with troubleshooting issues you may have
Click to expand...
Click to collapse
Thanks again--I appreciate your hard work and dedication to this!
bgibson72 said:
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
YES, dont boot into twrp until you remove it, or its back into the twrp loop you go hehe
Click to expand...
Click to collapse
Team DevDigitel said:
bgibson72 said:
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
YES, dont boot into twrp until you remove it, or its back into the twrp loop you go hehe
Click to expand...
Click to collapse
Weeeeeeeeeeeeee!!!
Will do!
Click to expand...
Click to collapse
Hello,
First, let me preface this by saying that this is not for those who are already technically capable of flashing U firmware from U1 firmware. This will serve as a tutorial for those who are not sure how to go about doing so. This could at least be a means to access U One UI 3.0 firmware, as it will be posted here for for faster download and bypassing decryption process. I've already done that for you.
So I have a N986U(VZW) and wanted to get an early look at Android 11 One UI 3.0. So, I went through the process of flashing U1 firmware, enrolled in Beta Program, and OTA'd up to latest beta (beta 3). Then, I see that carrier locked devices (to date, ATT, TMB, SPR, VZW) have begun receiving the official One UI 3.0 firmware OTA. Now don't get me wrong, I love U1 firmware, no carrier bloat, more features, typically, than what carrier branded have, among so many others. Alas, carrier branded firmware is generally more safe for me.
So, if you are like me, I wanted to have a means to be able to convert back to U firmware, while still remaining on One UI 3.0. Many of us already know how to go about doing so, but some may not, so I figured I'll outline the steps to go from U1 One UI 3.0 to U Carrier Branded One UI 3.0. I've provided links to the firmware and Odin for easy access and I'm always around, in case any of you have questions or have issues with any links.
Now, we have to have the essentials:
1. Odin(3.14.1_3B Patched is what I used)
2. Frija, or at the very least the firmware to convert over to
4. An archive extractor (Winzip, Winrar, 7zip, etc.) I'll explain why we don't want to use Windows Archive Tool in this explanation.
3. Some form of technical aptitude to be able to download and flash firmware using a tool
After you've gathered all of these, we need to ensure that no fingerprints or other forms of security are on the device. The reason we do this is the avoid any FRP (factory reset protection) issues after flashing. The way we do this is by disabling fingerprint unlock from settings. Change your unlock preferences to Swipe No Security. Do not forget to do this, because if you do, you will need to have an internet connection to the device during initial setup to authenticate your google account.
1.Once you've done this, you want to power down your device. For those who have enabled side button power menu, this is pretty self explanatory. Those who haven't, swiping down from your notification tray will reveal your power button. You know what to do from there.
2.Next, you want to press and hold Vol+, Vol-, and plug a USB-C cable into your device and subsequently into an available USB-A port on your PC. Allow Windows a moment to setup your device if your haven't plugged your device into your PC while in Download Mode before. You should see your device boot into Download Mode, and you will be presented with a Vol+ and Vol- and Power option. You will need to press Vol+ to continue into Download Mode.
3.Then, you will need to open Odin. When you do so, you should see a blue bar indicating that your device is recognized (represented by COM). If you don't see this within Odin, try re-inserting your USB cable into your PC, either into another USB port or changing your USB cable for another.
4.Once you are successfully able to see the blue COM indicator in Odin, you are to choose the applicable partitions (BL, AP, CP, and CSC). These will be archived in the firmware downloaded by Frija or link I provided. Each partition is labeled by it appropriate partition. Clicking each label in Odin will direct you to Windows Explorer, where you can browse for the directory where the downloaded files are locally stored.
THIS IS IMPORTANT!!! IF YOU DO NOT HAVE A ATT, TMB, OR SPR, DO NOT CHOOSE A USERDATA PARTITION. THIS IS POINTLESS TO FLASH, AND IT WILL SERVE NO BENEFIT IN THE USE OF THE DEVICE AFTER SETUP.
5.In Odin, you will see three tabs under the COM blue bar, named Log, Options, and PIT. I want to direct your attention to the tab labeled PIT. You will need to apply a PIT file in this tab. This file is located in the CSC partition. I have uploaded this file as well. But, if you want to learn how to extract it from the CSC partition, use the aforementioned Archive Extractors to open the CSC partition, and it should be the second in the list of files. Right click this file and select Extract to... From there, you are able to choose the folder you would like to extract to.
The reason you want to use the extractors I mentioned rather than Windows embedded extractor is due to Windows not being able to handle .md5 or .tar files. You will get an error if you attempt to open these types of files with Windows Extractor.
6. Once you've chosen all the partitions in Odin, you will click Start. It may take some time to complete the flashing process, so be patient. Once it completes, you will see Success in the field above COM, and the COM field will change from blue to green. If it doesn't change to green, and instead changes to red, be sure to let it be known to the thread, so that I can assist in the best way I can.
7. At this time, your device may reboot to recovery. This is fine, it just means that you will need to factory reset. Use Vol- to select Factory Reset. Select the option using the Power button. Upon successfully doing so, your device will reset to the setup screen.
8.Your device will be an Out-of-Box state upon reboot. Setup the device as normal.
9.All done! You are now on U firmware One UI 3.0! Congratulations!
I understand that this is a very lengthy explanation and that some, if not all, of this will be redundant to some users. That is okay. Not all of the users on XDA are educated on how to flash firmware on Samsung devices. I hope that after following this guide, that may soon change.
Below are all the files needed in order to flash what is needed in this guide. If you have any issues with downloading them, let me know. I'll be happy to re-upload them on another file sharing client for you.
Update: I've also uploaded the CTL4 firmware for U1 for those who want the updated unlocked firmware, in case you want to switch back to U1.
Odin:
Odin 3.14.1_3B
Frija:
Frija 1.4.3
N986U One UI 3.0:
N986USQU1CTL2
N986U1 One UI 3.0:
N986U1UEU1CTL4
PIT File for Repartitioning:
PIT C2Q_USA_SINGLE.pit
Just wanted to say "thank you" for posting this! I knew what to do already, however, I just didn't have any links for the zipped update that I needed!
I first had gotten a phone notification (Friday morning) that I could tap on to download the update OTA, however, I was at work so I had dismissed that notification... Unfortunately, after doing so, I was unable to get the update as no available updates even showed up in the settings... So I figured that I'd just need to manually push it through since OTA updates have consistently been skipping my device... Regardless, we're working now! So thanks again for the download links and I hope that you enjoy the holidays!
NippleSauce said:
Just wanted to say "thank you" for posting this! I knew what to do already, however, I just didn't have any links for the zipped update that I needed!
I first had gotten a phone notification (Friday morning) that I could tap on to download the update OTA, however, I was at work so I had dismissed that notification... Unfortunately, after doing so, I was unable to get the update as no available updates even showed up in the settings... So I figured that I'd just need to manually push it through since OTA updates have consistently been skipping my device... Regardless, we're working now! So thanks again for the download links and I hope that you enjoy the holidays!
Click to expand...
Click to collapse
Thanks so much. Just wanted to provide a means for new users a detailed explanation on how to change firmware, preventing the needs for QAs on bricked devices. Even though it's bound to happen eventually.
Just to verify, I have the verizon snapdragon variant and frija does not find the firmware, is the firmware you linked for the verizon snapdragon variant?
j3ffm1ll said:
Just to verify, I have the verizon snapdragon variant and frija does not find the firmware, is the firmware you linked for the verizon snapdragon variant?
Click to expand...
Click to collapse
This version is for anyone who has N986U or N986U1 devices. Bear in mind that this firmware is CTL2, whereas Verizon locked firmware is CTL4. Can confirm that I have a Verizon N20Ultra and am on CTL2 and all features are working except RCS, but even users on CTL4 are having this same error.
Update: I've linked the CTL4 U1 firmware for faster access. When and if I come across U CTL4 VZW firmware, I'll be sure to upload to the file repository. Thanks! Merry Christmas and Happy Holidays!
I am curious as to why you say it is safe for you. I am currently on Sprint/Tmobile. I converted to U1 to get update because I am impatient. What would be the benefits of doing this for me? This is a honest question even though as I reread this, it sounds a-holish. My apologies if it sounds like i am being a jerk. I am not. I do want to know.
sclarktay4 said:
I am curious as to why you say it is safe for you. I am currently on Sprint/Tmobile. I converted to U1 to get update because I am impatient. What would be the benefits of doing this for me? This is a honest question even though as I reread this, it sounds a-holish. My apologies if it sounds like i am being a jerk. I am not. I do want to know.
Click to expand...
Click to collapse
Sure thing. When I say safer, I mean that in an RMA lens. Based on your DID, Samsung knows what your devices CSC, model, and whether your device is U branded or U1 unlocked. There is a chance that your device can be deemed "tampered" with in the case where you send it for repairs and alterations have been made, like firmware. So, only spoken from that perspective. I've would've included this use case scenario, but as you and others can see, this post was extremely wordy to begin with
denson9874 said:
Sure thing. When I say safer, I mean that in an RMA lens. Based on your DID, Samsung knows what your devices CSC, model, and whether your device is U branded or U1 unlocked. There is a chance that your device can be deemed "tampered" with in the case where you send it for repairs and alterations have been made, like firmware. So, only spoken from that perspective. I've would've included this use case scenario, but as you and others can see, this post was extremely wordy to begin with
Click to expand...
Click to collapse
@sclarktay4 This is not true and incorrect info. I have personally Verified multiple times on multiple Samsung devices. I also have some insider info how they verify tampered devices but won't get into that. Even unlocked bootloader went through fine with RMA except once but flashing u1 on u will not cause RMA issues.
As far as this thread is concerned, this information is already posted so you wasted time in writing this wordy thread. Just saying cause no point wasting time in duplicating work and causing confusion to many here who aren't advanced users.
warriorvibhu said:
@sclarktay4 This is not true and incorrect info. I have personally Verified multiple times on multiple Samsung devices. I also have some insider info how they verify tampered devices but won't get into that. Even unlocked bootloader went through fine with RMA except once but flashing u1 on u will not cause RMA issues.
As far as this thread is concerned, this information is already posted so you wasted time in writing this wordy thread. Just saying cause no point wasting time in duplicating work and causing confusion to many here who aren't advanced users.
Click to expand...
Click to collapse
My dear friend, we meet again. I must disagree because I, being a former support technician for a vendor who handled RMA for carriers (Asurion), have seen devices regretted due non-carrier firmware being loaded on them. As a senior user on this forum, it is important to address all possibilities so that users are informed. As I stated in the beginning of my post, this is to serve as a means to educate users on the process, not for those who already know the process, like yourself. I, for one, respect all comments given, but those who come on to the forum to play repeat police, I can't waste time on that. Educating new users, I'll continue to waste my time on. Good holiday, sir.
denson9874 said:
My dear friend, we meet again. I must disagree because I, being a former support technician for a vendor who handled RMA for carriers (Asurion), have seen devices regretted due non-carrier firmware being loaded on them. As a senior user on this forum, it is important to address all possibilities so that users are informed. As I stated in the beginning of my post, this is to serve as a means to educate users on the process, not for those who already know the process, like yourself. I, for one, respect all comments given, but those who come on to the forum to play repeat police, I can't waste time on that. Educating new users, I'll continue to waste my time on. Good holiday, sir.
Click to expand...
Click to collapse
Well then your process was unique at Asurion, even Samsung stores here in NYC dont know about that unique process of yours. All they care about is if there is rooting or water ingress/ physical damage. Your means to educate others is by posting duplicate threads? Please dont be suggestive by saying you respect all comments as if others dont. Repeat police?? LOL ..Stop repeating same things then.. go read and educate yourself bro, if someone is playing repeat police by urging you to not post something twice to avoid confusion that too in the same device forum, same subsection where it was already posted. You want to feel important find other ways (being senior member is not an achievement you are trying to show off here buddy) may be make efforts to help people by posting in cross device forums.
And if we meet again that means you are lucky. Happy Holidays to you too.
warriorvibhu said:
Well then your process was unique at Asurion, even Samsung stores here in NYC dont know about that unique process of yours. All they care about is if there is rooting or water ingress/ physical damage. Your means to educate others is by posting duplicate threads? Please dont be suggestive by saying you respect all comments as if others dont. Repeat police?? LOL ..Stop repeating same things then.. go read and educate yourself bro, if someone is playing repeat police by urging you to not post something twice to avoid confusion that too in the same device forum, same subsection where it was already posted. You want to feel important find other ways (being senior member is not an achievement you are trying to show off here buddy) may be make efforts to help people by posting in cross device forums.
And if we meet again that means you are lucky. Happy Holidays to you too.
Click to expand...
Click to collapse
I prefer to stay in lane and educate on what I know rather than come half-stepped. It is clear we won't see eye to eye, which after our two encounters to this point, I'm glad for that. As long as forums will exists, there will always be users like you and I, quarreling over someone else's IP who make money on the both of us. All of this is beneath us. I wish you well, I truly mean that.
denson9874 said:
I prefer to stay in lane and educate on what I know rather than come half-stepped. It is clear we won't see eye to eye, which after our two encounters to this point, I'm glad for that. As long as forums will exists, there will always be users like you and I, quarreling over someone else's IP who make money on the both of us. All of this is beneath us. I wish you well, I truly mean that.
Click to expand...
Click to collapse
Very well said. Cheers to that. This is amazing and we both agree on. Moving on wishing you well too stay safe and have an amazing holiday season.
Just wanted to say thank you for the easy to follow and use instructions and files. Took only 3 minutes to complete once all was downloaded and extracted as instructed. Cheers and thanks for taking the time to help those of us out who enjoy dabbling but don't really have the know-how to do these things without a great community of people! Thank you good sir and have a great holiday.
ethos7788 said:
Just wanted to say thank you for the easy to follow and use instructions and files. Took only 3 minutes to complete once all was downloaded and extracted as instructed. Cheers and thanks for taking the time to help those of us out who enjoy dabbling but don't really have the know-how to do these things without a great community of people! Thank you good sir and have a great holiday.
Click to expand...
Click to collapse
Glad to see that you were able to find the instructions useful and informative. I hope that you have a happy holidays as well!!!
I am curious about something and hope you can give me an explanation. This is regarding your instructions for flashing the PIT file.
I have been flashing Samsung devices for many years and in all the time I have flashed firmware, I have never extracted and then added the PIT file in Odin. Can you tell me the reasons it is necessary to do that based on the steps you outline? What does flashing the PIT file do that would not be done if you don't flash it that way?
I am not saying it is wrong to flash the PIT file, only that I would like to know the reasons it is necessary. If you can explain that I would really appreciate it.
Thanks
Geekser said:
I am curious about something and hope you can give me an explanation. This is regarding your instructions for flashing the PIT file.
I have been flashing Samsung devices for many years and in all the time I have flashed firmware, I have never extracted and then added the PIT file in Odin. Can you tell me the reasons it is necessary to do that based on the steps you outline? What does flashing the PIT file do that would not be done if you don't flash it that way?
I am not saying it is wrong to flash the PIT file, only that I would like to know the reasons it is necessary. If you can explain that I would really appreciate it.
Thanks
Click to expand...
Click to collapse
Sure, I don't mind providing an explanation. So, essentially, PIT files provide the table or map and allocation size for each partition that Odin require to have a more successful flash process. Think of it as the roadmap for the firmware. This file is included in the CSC file, so extracting is not completely necessary, as it will be accessed during the flashing process. The reason I suggest applying the PIT file along with assigning CSC is for redundancy. Also, for these reasons:
1. To avoid a "Get PIT for mapping" error when flashing.
2. Prevent "Invalid EXT4 image" issues
3. Re-partitioning/NAND Erasing
4. Avoid possible boot loops
5. Proper internal storage allocation (Ensure if you have a 512GB device, you don't end up with 128GB visible.)**
** This is only an issue if you elect to download a PIT file from the web, rather than extracting it from the firmware.
denson9874 said:
Sure, I don't mind providing an explanation. So, essentially, PIT files provide the table or map and allocation size for each partition that Odin require to have a more successful flash process. Think of it as the roadmap for the firmware. This file is included in the CSC file, so extracting is not completely necessary, as it will be accessed during the flashing process. The reason I suggest applying the PIT file along with assigning CSC is for redundancy. Also, for these reasons:
1. To avoid a "Get PIT for mapping" error when flashing.
2. Prevent "Invalid EXT4 image" issues
3. Re-partitioning/NAND Erasing
4. Avoid possible boot loops
5. Proper internal storage allocation (Ensure if you have a 512GB device, you don't end up with 128GB visible.)**
** This is only an issue if you elect to download a PIT file from the web, rather than extracting it from the firmware.
Click to expand...
Click to collapse
Thank you for an easy to understand and complete explanation. Your response is one of the reasons I love XDA - getting these kinds of answers help me and anyone else reading (who doesn't already know) to get a much better understanding of our phones and the way things work.
Thank you very much!
Geekser said:
Thank you for an easy to understand and complete explanation. Your response is one of the reasons I love XDA - getting these kinds of answers help me and anyone else reading (who doesn't already know) to get a much better understanding of our phones and the way things work.
Thank you very much!
Click to expand...
Click to collapse
Well thank you so much. As long as I'm helping someone here, then this thread is serving its purpose. I care a lot about the why as much as I care about the what. This is the reason why I make lengthy post. Maybe a far amount of users don't really care about the details, I think it's important the understand the methodology. I hope that more and more people begin to share that same ethos.
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.