Related
Okay let me preface this post by saying, I did a good deal of research before I began this process, and was confident that I knew the steps sufficiently, and also the "plan B" recovery options.
Every video I watched on YouTube, every guide I found on various forums, and everyone I talked to made this process seem like cake. I have grown to disagree.
I am not a moron, nor am I incapable of following instructions. Every time I had a problem, I consulted with Google/YouTube/Forums, and researched how to fix it. I generally consider myself tech literate, but this is new to me. As such, I find it quite astonishing that, after so many years of development/home projects/general interest, there is NOT A SINGLE valuable 'getting started' guide. Granted, this is probably considered an advanced process, but even *nix development has more information than this FFS.
Anyway.
My task was simple; I wanted to update My GF's HTC One (m7spr) from 4.06xx to 4.4x. (Way overdue)
First things first; Settings -> About Phone -> Update -> Download it -> Install
Somehow this process got botched??? And the phone refused to accept 4.4, despite it being officially supported for several months.
Phone stuck at 4.06. Google had no information on failing to update, nothing relevant/useful anyway.
After dealing with that for 2 weeks, with zero progress, I decided to try the Root+Custom ROM process. That was, I believe, my only mistake.
The steps I followed, not necessarily in order*** :
-Install TWRP (so many problems with this, can't even find the words)
-Root phone (didn't work after multiple attempts, despite following directions perfectly, finally got it to work, and it didn't accomplish anything?!)
-Attempted to install SLIMkat ROM (took several attempts, finally got it running) This ROM was --no offense to the developer(s)--, for my purposes, disfunctional/broken, decided to attempt to rid myself of it
-Followed guides on YouTube to remove a ROM // flash stock
-Found several RUU's (all claimed to be valid, functioning and "simple solutions". None of which worked, and in every case, my device would 'lock' at the white screen/fastboot menu, and rebooting was a serious problem. During one failed attempt, my device would not reboot, causing me to be forced to let the battery drain before attempting again. (Hence the significance of removable batteries, but that's a whole other matter)
This is where it gets interesting
-SOMEHOW(???) "Chameleon OS" was attempting to be installed on the device. I had never heard of it, I had never seen it, I had no prior knowledge of it, I had not intentionally or even unintentionally collected this ROM, and surely did not have any intention of installing it. I wish to warn the community of potential maliciousness on the part of Chameleon OS. I did not give it permission to install, I was not even aware of its existance until the animated Chameleon came up, upon boot. I could not exit the install process, and it never finished booting. I had to simply let the battery die before I could re-enter the boot console/white screen. To be clear, I am not accusing the developers of anything malicious, I am simply pointing it out that this happened and the community should be aware of it.
Moving on.
-Using TWRP, I reset data, then factory reset the phone, then used the backup function, to boot into stock 4.06x Official.
-At this point, every time I restart the device, trying to enter TWRP, I can only access the white screen/fastboot menu -- I consider this to be progress, although it created a new problem; I am able to see the 4.4x update, and after it downloads, it asks me to restart the device so it can install. In doing so, it does NOT apply the update, however it stalls at the white screen/fastboot menu. I can reboot device and get back into Android, and the process repeats.
-
Allow me to sum up my current state;
-Device is fully functional within 4.06x, but for intents and purposes this is unacceptable
-Device can not be updated to newer version of Android, stuck at 4.06x
This process has been so long and drawn out, I am completely turned around with what problem requires what solution, and frankly I am exausted of trying to figure it out.
The real problem at hand is that the people who create guides/tutorials expect you to know certain things, and if you don't know certain things, they expect you to pause the video you're watching, go watch another video they made (irritating way to make your channel look like it has more traffic), and then resume what you were watching. As a first-time ROOTer, you're expected to pick up a ton of information that is not properly laid out in chronological order. Terms are not defined, and you're expected to just go with it.
This is why I did so much research beforehand. I was under the impression that the process was as simple as follows:
-ROOT device
-Install recovery option
-Create backup
-Install ROM
-Enjoy
Guides/forums/videos make it seem like a 10 minute proceedure. Lolnope. Going on several days of dealing with the current state. I waited so long to post because I was sure I was missing something, or messing it up. But I'm out of ideas now. :/
*** = Please understand that the process became frustratingly convoluted with various "I have B* problem, so I have to google the answer, which led me to learn about Y* treatment/process, and to complete Y* steps I needed Z* program, and to get Z* program I had to find Q* obscure information about my device, which requires me to go into BLUE* menu...and so on" ... it's irritating, to say the least.
I am frustrated, stuck and confused. The process is way more complex than the guides led on, and I have no idea what my next move should be. I'm humbly asking for help.
I would be more than glad to offer any non-personal information about my device's current state, in order to help you help me. Although as it stands I don't know what you need. Just ask. All I want to do is make the device COMPLETELY STOCK/FACTORY 4.4
Please forgive me if this post sounded ranty/salty. I'm honestly just tired of dealing with it, and I'm hoping to find some help from the people who know what they're doing.
Please and thank you.
Super_Annoyed said:
Okay let me preface this post by saying, I did a good deal of research before I began this process, and was confident that I knew the steps sufficiently, and also the "plan B" recovery options.
Every video I watched on YouTube, every guide I found on various forums, and everyone I talked to made this process seem like cake. I have grown to disagree.
I am not a moron, nor am I incapable of following instructions. Every time I had a problem, I consulted with Google/YouTube/Forums, and researched how to fix it. I generally consider myself tech literate, but this is new to me. As such, I find it quite astonishing that, after so many years of development/home projects/general interest, there is NOT A SINGLE valuable 'getting started' guide. Granted, this is probably considered an advanced process, but even *nix development has more information than this FFS.
Anyway.
My task was simple; I wanted to update My GF's HTC One (m7spr) from 4.06xx to 4.4x. (Way overdue)
First things first; Settings -> About Phone -> Update -> Download it -> Install
Somehow this process got botched??? And the phone refused to accept 4.4, despite it being officially supported for several months.
Phone stuck at 4.06. Google had no information on failing to update, nothing relevant/useful anyway.
After dealing with that for 2 weeks, with zero progress, I decided to try the Root+Custom ROM process. That was, I believe, my only mistake.
The steps I followed, not necessarily in order*** :
-Install TWRP (so many problems with this, can't even find the words)
-Root phone (didn't work after multiple attempts, despite following directions perfectly, finally got it to work, and it didn't accomplish anything?!)
-Attempted to install SLIMkat ROM (took several attempts, finally got it running) This ROM was --no offense to the developer(s)--, for my purposes, disfunctional/broken, decided to attempt to rid myself of it
-Followed guides on YouTube to remove a ROM // flash stock
-Found several RUU's (all claimed to be valid, functioning and "simple solutions". None of which worked, and in every case, my device would 'lock' at the white screen/fastboot menu, and rebooting was a serious problem. During one failed attempt, my device would not reboot, causing me to be forced to let the battery drain before attempting again. (Hence the significance of removable batteries, but that's a whole other matter)
This is where it gets interesting
-SOMEHOW(???) "Chameleon OS" was attempting to be installed on the device. I had never heard of it, I had never seen it, I had no prior knowledge of it, I had not intentionally or even unintentionally collected this ROM, and surely did not have any intention of installing it. I wish to warn the community of potential maliciousness on the part of Chameleon OS. I did not give it permission to install, I was not even aware of its existance until the animated Chameleon came up, upon boot. I could not exit the install process, and it never finished booting. I had to simply let the battery die before I could re-enter the boot console/white screen. To be clear, I am not accusing the developers of anything malicious, I am simply pointing it out that this happened and the community should be aware of it.
Moving on.
-Using TWRP, I reset data, then factory reset the phone, then used the backup function, to boot into stock 4.06x Official.
-At this point, every time I restart the device, trying to enter TWRP, I can only access the white screen/fastboot menu -- I consider this to be progress, although it created a new problem; I am able to see the 4.4x update, and after it downloads, it asks me to restart the device so it can install. In doing so, it does NOT apply the update, however it stalls at the white screen/fastboot menu. I can reboot device and get back into Android, and the process repeats.
-
Allow me to sum up my current state;
-Device is fully functional within 4.06x, but for intents and purposes this is unacceptable
-Device can not be updated to newer version of Android, stuck at 4.06x
This process has been so long and drawn out, I am completely turned around with what problem requires what solution, and frankly I am exausted of trying to figure it out.
The real problem at hand is that the people who create guides/tutorials expect you to know certain things, and if you don't know certain things, they expect you to pause the video you're watching, go watch another video they made (irritating way to make your channel look like it has more traffic), and then resume what you were watching. As a first-time ROOTer, you're expected to pick up a ton of information that is not properly laid out in chronological order. Terms are not defined, and you're expected to just go with it.
This is why I did so much research beforehand. I was under the impression that the process was as simple as follows:
-ROOT device
-Install recovery option
-Create backup
-Install ROM
-Enjoy
Guides/forums/videos make it seem like a 10 minute proceedure. Lolnope. Going on several days of dealing with the current state. I waited so long to post because I was sure I was missing something, or messing it up. But I'm out of ideas now. :/
*** = Please understand that the process became frustratingly convoluted with various "I have B* problem, so I have to google the answer, which led me to learn about Y* treatment/process, and to complete Y* steps I needed Z* program, and to get Z* program I had to find Q* obscure information about my device, which requires me to go into BLUE* menu...and so on" ... it's irritating, to say the least.
I am frustrated, stuck and confused. The process is way more complex than the guides led on, and I have no idea what my next move should be. I'm humbly asking for help.
I would be more than glad to offer any non-personal information about my device's current state, in order to help you help me. Although as it stands I don't know what you need. Just ask. All I want to do is make the device COMPLETELY STOCK/FACTORY 4.4
Please forgive me if this post sounded ranty/salty. I'm honestly just tired of dealing with it, and I'm hoping to find some help from the people who know what they're doing.
Please and thank you.
Click to expand...
Click to collapse
Did you try the latest RUU? No need to root etc...Just download the file, run the setup and you're good to go!
http://forum.xda-developers.com/showthread.php?t=2658910
Super_Annoyed said:
Okay let me preface this post by saying, I did a good deal of research before I began this process, and was confident that I knew the steps sufficiently, and also the "plan B" recovery options.
Every video I watched on YouTube, every guide I found on various forums, and everyone I talked to made this process seem like cake. I have grown to disagree.
I am not a moron, nor am I incapable of following instructions. Every time I had a problem, I consulted with Google/YouTube/Forums, and researched how to fix it. I generally consider myself tech literate, but this is new to me. As such, I find it quite astonishing that, after so many years of development/home projects/general interest, there is NOT A SINGLE valuable 'getting started' guide. Granted, this is probably considered an advanced process, but even *nix development has more information than this FFS.
Anyway.
My task was simple; I wanted to update My GF's HTC One (m7spr) from 4.06xx to 4.4x. (Way overdue)
First things first; Settings -> About Phone -> Update -> Download it -> Install
Somehow this process got botched??? And the phone refused to accept 4.4, despite it being officially supported for several months.
Phone stuck at 4.06. Google had no information on failing to update, nothing relevant/useful anyway.
After dealing with that for 2 weeks, with zero progress, I decided to try the Root+Custom ROM process. That was, I believe, my only mistake.
The steps I followed, not necessarily in order*** :
-Install TWRP (so many problems with this, can't even find the words)
-Root phone (didn't work after multiple attempts, despite following directions perfectly, finally got it to work, and it didn't accomplish anything?!)
-Attempted to install SLIMkat ROM (took several attempts, finally got it running) This ROM was --no offense to the developer(s)--, for my purposes, disfunctional/broken, decided to attempt to rid myself of it
-Followed guides on YouTube to remove a ROM // flash stock
-Found several RUU's (all claimed to be valid, functioning and "simple solutions". None of which worked, and in every case, my device would 'lock' at the white screen/fastboot menu, and rebooting was a serious problem. During one failed attempt, my device would not reboot, causing me to be forced to let the battery drain before attempting again. (Hence the significance of removable batteries, but that's a whole other matter)
This is where it gets interesting
-SOMEHOW(???) "Chameleon OS" was attempting to be installed on the device. I had never heard of it, I had never seen it, I had no prior knowledge of it, I had not intentionally or even unintentionally collected this ROM, and surely did not have any intention of installing it. I wish to warn the community of potential maliciousness on the part of Chameleon OS. I did not give it permission to install, I was not even aware of its existance until the animated Chameleon came up, upon boot. I could not exit the install process, and it never finished booting. I had to simply let the battery die before I could re-enter the boot console/white screen. To be clear, I am not accusing the developers of anything malicious, I am simply pointing it out that this happened and the community should be aware of it.
Moving on.
-Using TWRP, I reset data, then factory reset the phone, then used the backup function, to boot into stock 4.06x Official.
-At this point, every time I restart the device, trying to enter TWRP, I can only access the white screen/fastboot menu -- I consider this to be progress, although it created a new problem; I am able to see the 4.4x update, and after it downloads, it asks me to restart the device so it can install. In doing so, it does NOT apply the update, however it stalls at the white screen/fastboot menu. I can reboot device and get back into Android, and the process repeats.
-
Allow me to sum up my current state;
-Device is fully functional within 4.06x, but for intents and purposes this is unacceptable
-Device can not be updated to newer version of Android, stuck at 4.06x
This process has been so long and drawn out, I am completely turned around with what problem requires what solution, and frankly I am exausted of trying to figure it out.
The real problem at hand is that the people who create guides/tutorials expect you to know certain things, and if you don't know certain things, they expect you to pause the video you're watching, go watch another video they made (irritating way to make your channel look like it has more traffic), and then resume what you were watching. As a first-time ROOTer, you're expected to pick up a ton of information that is not properly laid out in chronological order. Terms are not defined, and you're expected to just go with it.
This is why I did so much research beforehand. I was under the impression that the process was as simple as follows:
-ROOT device
-Install recovery option
-Create backup
-Install ROM
-Enjoy
Guides/forums/videos make it seem like a 10 minute proceedure. Lolnope. Going on several days of dealing with the current state. I waited so long to post because I was sure I was missing something, or messing it up. But I'm out of ideas now. :/
*** = Please understand that the process became frustratingly convoluted with various "I have B* problem, so I have to google the answer, which led me to learn about Y* treatment/process, and to complete Y* steps I needed Z* program, and to get Z* program I had to find Q* obscure information about my device, which requires me to go into BLUE* menu...and so on" ... it's irritating, to say the least.
I am frustrated, stuck and confused. The process is way more complex than the guides led on, and I have no idea what my next move should be. I'm humbly asking for help.
I would be more than glad to offer any non-personal information about my device's current state, in order to help you help me. Although as it stands I don't know what you need. Just ask. All I want to do is make the device COMPLETELY STOCK/FACTORY 4.4
Please forgive me if this post sounded ranty/salty. I'm honestly just tired of dealing with it, and I'm hoping to find some help from the people who know what they're doing.
Please and thank you.
Click to expand...
Click to collapse
if you are s-on you need to relock your bootloader, you also need to flash stock recovery for the ruu you are using, also if ypu are s-on you'll need the latest ruu, will not let you downgrade,
Muchas gracias amigos
indy1811 said:
Did you try the latest RUU? No need to root etc...Just download the file, run the setup and you're good to go!
http://forum.xda-developers.com/showthread.php?t=2658910
Click to expand...
Click to collapse
Aldo101t said:
if you are s-on you need to relock your bootloader, you also need to flash stock recovery for the ruu you are using, also if ypu are s-on you'll need the latest ruu, will not let you downgrade,
Click to expand...
Click to collapse
I greatly appreciate the responses.
I will try both and report back.
Super_Annoyed said:
I greatly appreciate the responses.
I will try both and report back.
Click to expand...
Click to collapse
LOG:
-RUU listed above was successful, booted into 4.06.651.4
-Attempting to update to 4.06.651.9
-Update unsuccessful, upon reboot, still 4.06.651.4, no error message
-Attempting to update to 4.06.651.9 again
-Update successful
-Attempting to update to 5.03.651.3
-Update successful (THANK YOU!)
Oh wow, such a huge relief. I feel a bit dumb having been so close to the actual solution, lol.
I would like to extend a huge helping of gratitude to both users indy181 AND Aldo101t.
Yall really knew what my problem was and how to fix it, so yall both have my gratitude.
I guess in my frustration I misunderstood the purpose of the RUU files, and ignored the version labels.
To a frustrated noob, the filename "1_29_651_10" has no real meaning. I suppose my research failed at this critical point.
It doesn't explain why the device failed to update in the first place, but since it's all set now it makes no difference.
Thanks so much, fellas!
worked like a charm)
Just a quick comment:
I didn't see any mention of HTC Dev unlock. Did you do that?
Did u ever get any offers from any publishers? Haha holy cow that was a long post! Glad u got straightened out!
Sent from my Nexus 7 using Tapatalk
Summary: Started root, didn't complete it (?), then update downloaded.
I began root process last night--my first try--using Towelroot. When I pressed the "Make it Rain" button, I got an error message that my device was not supported (I don't recall the exact words). Using Android 4.4.4.
I've not found a way to continue this, although I see some alternate methods in another thread.
What is apparently going to be a 2-hour over Wifi update from AT&T, is in process. Are there any problems regarding this and proceeding with the root process?
halfmybrain said:
Summary: Started root, didn't complete it (?), then update downloaded.
I began root process last night--my first try--using Towelroot. When I pressed the "Make it Rain" button, I got an error message that my device was not supported (I don't recall the exact words). Using Android 4.4.4.
I've not found a way to continue this, although I see some alternate methods in another thread.
What is apparently going to be a 2-hour over Wifi update from AT&T, is in process. Are there any problems regarding this and proceeding with the root process?
Click to expand...
Click to collapse
You started two threads asking the same question and your answer is in the AT&T General threads
http://forum.xda-developers.com/showthread.php?t=3076803
I did not start two threads with the same question. They were related but distinct., and the second one quoted the first for CONTEXT but the question was different.
They both regarded partial root. One regarded the major upgrade [4.4.4 --> 5.0], the other regarded an SD card. Thanks, and I will look where you pointed me and hope the answers are specific, like my questions were.
OPOfreak said:
You started two threads asking the same question and your answer is in the AT&T General threads
http://forum.xda-developers.com/showthread.php?t=3076803
Click to expand...
Click to collapse
OPOfreak said:
You started two threads asking the same question and your answer is in the AT&T General threads
http://forum.xda-developers.com/showthread.php?t=3076803
Click to expand...
Click to collapse
I do not see answers to my questions in General AT&T. I'm new here, but I am trying to follow basic forum etiquette. 1. Only one question initiated per thread. 2. Post to the forum that fits best. I feel my post fits under troubleshooting. I'm not just asking out of curiosity, I've put myself into two corners (as I see it). One is, partially rooted my phone then updating my software. The other is, how is my SD card related to the root--should it be (have been) installed prior to my attempt to root. I am here combining my issues in one post to show my belief that they are troubleshooting issues AND I need help before I proceed.
Perhaps there's an underlying question, and I hope I get some feedback. Have I indeed partially rooted, if I got as far as Towelroot's "Make it Rain" command but (not supported) it did not go further? Thanks so much in advance, I'm sure "newbie" would be a compliment.
halfmybrain said:
I do not see answers to my questions in General AT&T. I'm new here, but I am trying to follow basic forum etiquette. 1. Only one question initiated per thread. 2. Post to the forum that fits best. I feel my post fits under troubleshooting. I'm not just asking out of curiosity, I've put myself into two corners (as I see it). One is, partially rooted my phone then updating my software. The other is, how is my SD card related to the root--should it be (have been) installed prior to my attempt to root. I am here combining my issues in one post to show my belief that they are troubleshooting issues AND I need help before I proceed.
Perhaps there's an underlying question, and I hope I get some feedback. Have I indeed partially rooted, if I got as far as Towelroot's "Make it Rain" command but (not supported) it did not go further? Thanks so much in advance, I'm sure "newbie" would be a compliment.
Click to expand...
Click to collapse
If you pressed make it rain and then it said device not supported you're not rooted
Not sure? Download Root checker from Playstore
I am a newbie and this is the first time I have tried anything out of the way to update my phone. I have an unlocked S6 edge AT&T version which was running MM 6.0.1. I wanted to update it to the latest Android Nougat and in order to do that I started searching online, but there was no such straight post or article where I can get everything in one place. I found a lot of information and many ways to upgrade the firmware but not all the steps were perfectly placed.
Anyways, I referred to many articles and posts and realized that it could be risky but doable so I went ahead and did it successfully. Though I faced few errors and issues but I found most of the resolution here at xda-developers and other online forums. I am writing this post to help all S6 edge owners who want to upgrade to Android 7.0.
My Phone Details:
Model: SM-G925A (S6 Edge AT&T)
Build: G925AUCS5DPJ1
Android: 6.0.1
There are two major steps involved to upgrade to the latest android version.
1. Flash the firmware with the higher security patch (keeping the device at Android 6) using ODIN software.
2. Upgrade the firmware to Android 7 using ADB software.
[Note: I might be using flash, upgrade interchangeably]
Downloads
Tools :
Latest ODIN tool (I used 3.10.6)
ADB tool (I used 25.0.3 but you can find latest version here)
Firmware:
First you need to flash you ROM to reach G925AUCS5DPK5 build. You can download this file from here.
Refer to Post:
https://forum.xda-developers.com/att-galaxy-s6-edge/general/g925a-pk5-stock-repair-ota-7-0-t3564102
Then you have to update the firmware to get Android 7 using this fie SS-G925AUCS5DPK5-to-U5EQA8-UP (put a .zip after this file to make it recognizable by the tool)
Step 01: Flash latest security patch
ODIN Working:
Link 01: http://droidvendor.com/how-to-install-stock-firmware-using-odin-on-a-samsung-device/
Link 02: http://www.droidviews.com/install-android-nougat-on-att-galaxy-s6-s6-edge-sm-g920ag925a/
My recommendations:
1. Use 3.10.6 version.
2. Unpack the G925AUCS5DPK5.zip file and you will find 4 different .tar.md5 files namely AP, BL, CP and CSC.
3. Use all 4 files at once in ODIN. Do not use only AP. If you use only AP file then your phone will be updated to the latest security patch and will work fine but it won't update the baseband version and will still show it as G925AUCS5DPJ1 even though your latest build is G925AUCS5DPK5. This will create problem while going to Android 7.0.
4. Take proper back up of all your files before going ahead using Samsung SmartSwitch.(Download Links : Windows, Mac). This way you can take back up easily as well as your pc will have the latest USB drivers.
5. Make sure your phone baseband and build are same as G925AUCS5DPJ1.
6. Charge you phone at least 70% before going ahead. It is just a precaution in case this process takes longer than expected. (Mine was finished in 4 minutes)
Step 02: Update to Android 7.0
ADB Working:
Link 01: http://www.droidviews.com/download-latest-adb-and-fastboot-sdk-platform-tools-win-mac-linux/
Link 02: http://www.droidviews.com/install-apk-files-using-adb-commands/
My Recommendations:
1. Use the version I have recommended above instead of going to the latest version (I faced some issue with the latest one and had to go back to this version)
2. Instead of opening the command prompt from shift+right click. Use run or search cmd and open it as administrator.
3. Change the SS-G925AUCS5DPK5-to-U5EQA8-UP.zip to OTA.zip or any shorter name. It will be easy to type the command.
4. If you face any error try using adb kill-server and then use adb sideload <ota.zip>.
5. Be patient this process will take some time. Mine took 25 minutes to complete.
6. Again keep your phone battery charged enough to survive the process.
7. After restart my phone stuck at black screen AT&T logo for 5 minutes. So don't get worried just wait, it will work.
8. Read all the instructions twice on the links provided before going ahead. If you are not sure of any instruction you can search xda forum and you will find relevant information.
Problems/Issues I faced
1. Reduced Storage: After updating my phone to build G925AUCS5DPK5, I realized the phone is only showing 16gb storage while my phone internal storage was 64gb. ( I found the root cause when I got my 3rd error, for the storage issue I was not bothered enough but wanted to go ahead so that I can get Nougat soon)
2. ADB Terminated: My phone got this error when I was updating it to Nougat. (The error looked like this : terminate called after throwing an instance of std::logic_error what() ). I searched online I found out that this is happening because of the adb version I am using, so I downloaded another version and it went through without this error but gave me the below one.
3. Status 7 Error: Again in adb I faced this error. And the error looked like this: 'Verifying current system..."/system/csc/contents.db" has unexpected contents. Error Pic Link.
I searched online and found out that this could be related to CSC file which I have not updated in my first step. So this time I again performed my first step using Odin tool but I selected the 3 files except the AP and ran the process. Yippy, I got my storage back and in adb there was no any error going forward.
Conclusion: I got Nougat on my At&T S6 Edge but I faced few issues. Being a new comer it was not much difficult provided you have the information and passion to do it. The steps mentioned here are very specific to S6 Edge but it can be used for other versions as well. You only have to make sure you have the current files and build combination otherwise your phone could be bricked. I hope this post will be helpful for the users.
Thanks for the detailed instruction on how to upgrade. Very useful! I do have one question though. Does Samsung pay work after upgrading using the method stated above?
Thanks for the great step by step guide. The only amendments/extra things that might help a little more:
Step 1) I used ODIN v3.12 as described above. Loaded all 4 files, BL AP CP CSC
***Basic missing step in the guide was to use ODIN correctly, you need to put your phone into upload mode.***
***Basic step, to prepare to use adb you must enable USB debugging while you have the Step 1 complete before you start Step 2***
Step 2) I was getting the errors thrown with ADB terminated and did some research. You have to use v25.0.3 or else it throws the std::logic_error what() error. It was challenging to track down that version of the adb but I found it here: https://www.izzysoft.de/ftp/local/android/
***Basic Step, in order to use adb, you must put your phone in recovery mode*** (and be sure you use v25.0.3)
Thanks again for the great tutorial!
Shame you cannot start out with latest version of Baseband version: G925AUCS6DQC1 that is in the phone and not have to go Back a version first to PK5
techwire said:
1. Use the version I have recommended above instead of going to the latest version (I faced some issue with the latest one and had to go back to this version)
Click to expand...
Click to collapse
i am curious, what specific issues did you have? should i stay on EQA8?
i had success with this method following the instructions and commentary going from DPK5 > EQA8. One additional thing to note is that each step of the process (odin, adb) will wipe the contents of the phone. I backed up with samsung switch, but it doesn't quite capture all the settings so you may want to use something else.
Hi
great post, i followed your instructions and i was able to get from DPK1 ( 6.01) to QA8. Now I noticed that G625AUCU5EQA8 is not the official ROM so would like to get at least to G925AAUCS6DQC1.
Do you know how to get from G625AUCU5EQA8 to G925AAUCS6DQC1?
thank you for your advice.
here is another DPK5 mirror
https://ulozto.net/!PpQ4SbJJOQyD/g925aucs5dpk5-6-0-1-4file-usa-att-7z
G925Aucu4dph5 is my build number, what can I do?
GoRi7o3 said:
G925Aucu4dph5 is my build number, what can I do?
Click to expand...
Click to collapse
You can Odin to Nougat 7.0 from here : http://forum.xda-developers.com/showthread.php?p=72406969
On Edge of Galaxy
You have any tutorial video of this or something that prove this method?
GoRi7o3 said:
You have any tutorial video of this or something that prove this method?
Click to expand...
Click to collapse
What proof do you need?
I don't now much things about this, can I jump to my baseband number g925aucu4dph5 to the baseband you mention in the post, or I have to do this method many times jumping from baseband to baseband to get the one you post
GoRi7o3 said:
I don't now much things about this, can I jump to my baseband number g925aucu4dph5 to the baseband you mention in the post, or I have to do this method many times jumping from baseband to baseband to get the one you post
Click to expand...
Click to collapse
Yes. You can jump from whatever baseband you have to most of full Odin files.
On Edge of Galaxy
Ok thank you, I will use this method soon, I wish that work
I am still rooted with OE2 5.0.1
Is there any way to update my device using ODIN without losing the root? Just curious. Switching to Fi and I unlocked my phone from the carrier, but since its 5.0.1 it wont run the Project Fi app which requires 5.1+ to activate and operate.
Illiteracy and instruction...
I would like to know why it seems like the only threads on how to upgrade a SM-G925A from 5.1.1 to Nougat lack clear language, in an organized fashion, that would allow those most challenged by the process to accomplish the task with the least amount of frustration. I really cannot comprehend how it is that someone considered a "Senior Member" is permitted to instruct on complex procedures, when it is apparent the person does not have a fluency in the language being used. I don't say this as an insult to anyone's culture or ethnicity, it just adds to the difficulty. Where are the moderators (Admins) when you need clarity. There must be someone who can impart the step-by-step procedure concisely. This forum is not useful for its intended purpose otherwise.
Alias_REBaker said:
I would like to know why it seems like the only threads on how to upgrade a SM-G925A from 5.1.1 to Nougat lack clear language, in an organized fashion, that would allow those most challenged by the process to accomplish the task with the least amount of frustration. I really cannot comprehend how it is that someone considered a "Senior Member" is permitted to instruct on complex procedures, when it is apparent the person does not have a fluency in the language being used. I don't say this as an insult to anyone's culture or ethnicity, it just adds to the difficulty. Where are the moderators (Admins) when you need clarity. There must be someone who can impart the step-by-step procedure concisely. This forum is not useful for its intended purpose otherwise.
Click to expand...
Click to collapse
What you talking about? This is very easy process. But there is even easier of you read another threads and learn from XDA or YouTube how to use ODIN. When you ready to try Odin you can flash firmware from here : http://forum.xda-developers.com/showthread.php?t=3611271 . This is 100% stock AT&T Nougat 7.0 Odin firmware use by Best Buys or Smasung to restore phones.
BTW Senior Members are mostly who build this forum. So just follow instructions, sit back and enjoy. If you need more clarification use your best friend Google or YouTube.
On Edge of Galaxy
Clarity wins
First of all, not admitting your English grammar is in need of some fine tuning doesn't help to clarify the issue. Additionally, combining both ADB sideloading and Odin, without clearly delineating which zip files need to be acquired for accomplishing the task using one or the other method, just adds to the confusion. I upgraded my phone using Odin and the "OCF" "tar" files. But, I was getting confused as to whether I also needed to use ADB to get to "OCF". I started off at "BOJ9". Not wanting to brick my phone led to much trepidation. I wanted to be absolutely sure. The main question I needed clarified was whether I could go from "BOJ9" to "OCF" without needing to go through each iteration. Many people had asked this question, but no specific answer was ever given. Thus, my frustration. I did eventually figure it out, but coming to XDA looking for a clear answer was not the solution. I see a lot of posturing, responders getting snarky telling the confused it's in some thread yet to be dug into or just being rude. Just help. Really, if that's not why you're here, move on.
Alias_REBaker said:
First of all, not admitting your English grammar is in need of some fine tuning doesn't help to clarify the issue. Additionally, combining both ADB sideloading and Odin, without clearly delineating which zip files need to be acquired for accomplishing the task using one or the other method, just adds to the confusion. I upgraded my phone using Odin and the "OCF" "tar" files. But, I was getting confused as to whether I also needed to use ADB to get to "OCF". I started off at "BOJ9". Not wanting to brick my phone led to much trepidation. I wanted to be absolutely sure. The main question I needed clarified was whether I could go from "BOJ9" to "OCF" without needing to go through each iteration. Many people had asked this question, but no specific answer was ever given. Thus, my frustration. I did eventually figure it out, but coming to XDA looking for a clear answer was not the solution. I see a lot of posturing, responders getting snarky telling the confused it's in some thread yet to be dug into or just being rude. Just help. Really, if that's not why you're here, move on.
Click to expand...
Click to collapse
First of all English is my sixth language I know 5 more, how much more you know, second this is international forum open for whole world, third I'm almost 55 years old and understand all process ( this telling me one or two things about you) . You must be millennial who thinks he is most important person on world. If you don't like it move on to different place.
And yes you can go strait by ODIN from your build to QCF with out any problem, but seems like you not read enough.
O! One more you must be Polish because only this people critique other people's language ability, I know because I was like this once.
Edit: Also I see inability to follow instruction or search. You need to have everything put for you on silver platter.
On Edge of Galaxy
Attitude instead of resolution.
So, here it starts, attitude. I'm 56 and will shortly be 57. I am no millennial. Secondly, perhaps you should focus on your English grammar skills. While you may speak several languages, your skill with written English is atrocious. Even if your English grammar was passable, you have no skill at writing an organized and cohesive text. A simple, step-by-step guide to accomplish the task. Putting up a few links mixed with gibberish is not helpful. It's lazy and sloppy. Have some pride in your work. Exhibit some maturity and avoid superfluous writing.
Hello everyone,
I have to say I am completely lost regarding the whole rooting process for the XZ1C. I usually manage to get where I want just by carefully reading the forums, but with this device, I feel overwhelmed by information. And I sometimes feel like what I am reading contradicts what I though I understood from previous reads...
I will try to sum up what I know so far.
First of all, I have a just-out-of-the-box Sony model G8441 with firmware 47.1.A.12.179 / Oreo 8.0.0 (never been connected to the outside world yet), and I want to properly root the device and install TWRP with no loss of feature.
What I think I understand:
To root, I first need to unlock the bootloader, which seems to be a trivial operation. However, this will break some functionalities due to DRM keys being erased. Once it is done, there is no way, ever, to get them back. There are however ways to "trick" DRM-related functionalities into believing DRM keys are still there.
Alternatively, there seems to be a way to backup the DRM keys prior to unlocking the BL, and this backup can somehow be reused and injected back into the unlocked device. If true, then this would certainly be a preferable method than the previous one, which would then be obsolete. However, it obviously doesn't look obsolete when I read the related topics, so I must be missing something...
Another thing I noted (but do not quite understand): There are ROMs for this device that "include" a DRM fix.
Last important thing I read: there is a paid "do-it-all" tool which takes my locked device and, with one click, makes it unlocked - rooted - DRM-fixed - TWRP-enabled. Now that sounds really good! Maybe too good?
As far as i know (but I learn new stuff every day on this topic) this DRM stuff is the main difficulty here. I understand that the rest of the process (root + TWRP) will be much simpler (although I'm old-school and completly missed all this magisk trend...!)
What I don't understand:
I read that some people downgrade to Oreo to be able to root properly, and at the same time, I read that Pie removed the restrictions on unlocked bootloader. So I still have no idea if I should connect and receive Sony updates, or avoid them.
Another thing I don't get, is how many ways do we have to root this thing? In the past, I was used to see, for a specific device, always one major and widly used rooting method. Here I fail to identify it...
What I think I will do:
1. Backup TA partition with j4nn's tool. This will probably imply flashing an older firmware right? Is there any link that could help me with this flashing process? (I only know Odin - did I mention old-school?) I saw this page for generic sony Z devices, but the thread is from 2013 and now closed. Is it still up-to-date or is there a newer thread?
2. Unlock bootloader and restore TA partition.
3. Wait for Sony updates? Or should I first hide unlock status?
3bis. Alternaltively to waiting for updates, maybe I can just flash the latest build? (47.2.A.8.24 if I am not mistaken)
4. Flash modpunk's TWRP.
5. Flash janjan's Boot.img to get root functionalities?
Alternaltively to all the above (except maybe step 1 that I will probably do in any case), buy the paid all-in-one tool (Xperifix), plug, click and wait... But will I really end up the same as with the manual way?
I saw a few other methods in the forums but it seems my brain is currently refusing to bring them back...
That's all I have right now. I would really appreciate if you guys could share some insight and tell me what you think about this, whether there are missing steps, useless steps, incorrectly ordered steps, silly steps, or if I'm just completely wrong about the whole thing.
Feel free also to correct me on the assumptions I made at the beginning.
Thank you very much for reading this repulsive piece of text.
SunJu22 said:
I would really appreciate if you guys could share some insight and tell me what you think about this
Click to expand...
Click to collapse
By the looks of it you have done a great deal of research on the project.
Yes, go down the route of backing up your TA partition first, but that is not a small step in itself, it's pretty complicated and if you get that working then the rest of the project will be a breeze.
You don't say what version of firmware you want to end up on. If you want to end up on Pie then forget the DRMfix . But if you're staying on Oreo and can't be bothered with lots of files & flashing, then this is the easy way out, I bought the paid version and can verify it works.
More recently I ended up janjan's kernel (Oreo build). Hidden root (Google Pay works), lots of performance tweaks, DRM completely working.
It's unlikely that anyone will bother making a DRM fix for Pie as the camera works and there are only a couple of other features that get disabled.
It sounds like you're not the sort of person who's only going to read the first couple of pages of a thread (or the last) flash the xxxxxx and then complain when it's broken.
The people on the forum here are very helpful and if you go into any of the threads you mentioned in your post with a question, you'll get a reply.
Good luck.
I agree, there is a lot of information out there and different methods of achieving what you want - very confusing if you have not been following the threads since the beginning.
In my opinion, the preferred method is j4nn's method outlined here: https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
Use that post as your main guide (the final step in that guide, #13, is how you will achieve root). You will use Newflasher to flash the various firmwares along the way (this is linked from j4nn's procedure in step #2). User munted made a very detailed pdf file that fills in some of the details on j4nn's procedure - see the following post and download the pdf attached: https://forum.xda-developers.com/showpost.php?p=78255334&postcount=382
Most of the other methods out there came before j4nn's work - they didn't include DRM backup/restore.
If you follow j4nn's procedure, you won't need to use the janjan kernel as you assumed - janjan method is different and does not overlap with j4nn.
SunJu22 said:
Feel free also to correct me on the assumptions I made at the beginning.
Click to expand...
Click to collapse
Sorry, I didn't point out that I was one of the early 'jumpers' who unlocked their bootloader without any backups, so I have been forced into always using fixes and all the information I have is based on having to fix your phone for it to work, but that's all changed now. I'm so out of date :-/
@camaro322hp is right, if you follow j4nn's method correctly you'll be rooted with no DRM loss. All of the other stuff is not required.
Thank you Digesteve and camaro322hp for your help.
From what I understand the XZ1C didn't get as much love as other devices, thus there was a long period of tinkering before a "do-it-all guide" could be considered "the" solution. That could explain all these different approaches that are proposed. Like you said camaro322hp it's rather difficult to jump on this train, and I can only guess how interesting this ride has been.
Anyway, I didn't see that the TA backup thread from j4nn also encompassed all the information I needed; I am glad to finally know that there is indeed a centralized "do-it-all guide" . To make it easier for XZ1C newcomers, I think j4nn should update his opening post to make this clearer.
Since I managed to grab the attention of 2 XZ1C power users, I would like to ask you: Did you keep stock? Did you try alternative ROMs? Do you like some of them? Do you prefer Oreo or Pie?
For information, the most up-to-date experience I have on a Android phone is my LG90 with CyanogenMod 11 (KitKat 4.4.4! Yes sir!). I heard that it's becoming less and less useful to flash a custom ROM due to major OS improvements, but I would still enjoy the simplest and lightest Android possible.
SunJu22 said:
Did you keep stock? Did you try alternative ROMs?
Click to expand...
Click to collapse
I've always been on stock, the camera is an important part of what I want from my phone and although there's lots of alternative camera apps, there's no competition to the stock camera app. Then I theme it black with swift installer and just uninstall or freeze any apps I don't want with Titanium Backup. I have stuck with Oreo, everything works perfect and I remember seeing so many people jumping to 9 then wanting to go back to 8 because they didn't like it. Something about changing the way the drop down menu works, among other things, but having never installed it, I'm not the person to comment on if it's any good or not.
I have been watching the XZ1c thread and Lineage is gaining ground, it even has a stock camera now. I would have thought something like that with miniGapps is going to be pretty lightweight and very similar to your carbon rom of before. At the moment this is based on 8, but is working well. Depends how keen you are to move to Pie.
Thank you Digesteve.
One thing I still don't understand. Part of the process is to hide unlock status. If I do this, FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
@SunJu22 I've stuck with the Sony ROM. A rooted stock ROM meets all my needs, so I've never felt the need to experiment with custom ROMs. There are some custom options out there that people seem fairly happy with, so if that's your thing, I'd encourage it.
Without going into too much detail, I'm still on Oreo for the moment, for a variety of reasons, but I don't know of anything that would keep me from recommending Pie.
One thing you should note is that once you unlock, there is no going back. AFAIK there is no known or working method to relock the bootloader.
SunJu22 said:
FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
Click to expand...
Click to collapse
Yes, I'm not entirely sure why having your rooted phone try and update itself is an advantage, but something I'd recomend avoiding.
Stock camera is the Sony camera, yes.
Thank you everyone, I believe I now have enough information to jump into this with confidence. The adventure begins, and will be reported in this thread for future reference, in the hope that it will help others like me!
Well, I am a bit sad... I wanted to report my "adventure" here in detail, but I'm afraid I have nothing to say.
Indeed, following the procedure from j4nn with a printed copy of munted's awesome guide, I managed to do all I wanted on the first attempt.
I don't have anything to add to this guide, everyone wanting to root their XZ1C can do it just by reading the opening post from j4nn and the mentioned guide. It takes a bit of time but nothing complicated thanks to the clear and detailed explanations.
I now have a fully functional rooted XZ1C (including camera) on Pie with Magisk root and TWRP.
Thank you all again from pointing me to the right direction.
I however have a slight disappointment. I wanted to start with Oreo and make an Nandroid backup before moving to Pie, but I didn't find Oreo builds on Xperifirm. So I jumped straight to Pie.
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea?
Last but not least: I looked for the latest Oreo build version number but couldn't find it. Do you guys know what it is and where I can download it?
I guess this will be all for this thread after this. Although it is very convenient to have my own thread to ask questions rather than finding the relevant page for each one, I don't want to annoy you too much...
EDIT: Please ignore the last question. I found out last Oreo build is 47.1.A.16.20, and I found the files via the download link in the opening post of the Lineage thread.
SunJu22 said:
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea? Lineage thread.
Click to expand...
Click to collapse
There is an easy solution to downgrade:
Newflasher
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
mEREHAIGE said:
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
Click to expand...
Click to collapse
No, you can flash a kernel to hide the bootloader unlock flag, this will mean that you will receive OTA updates, although depending on how you're rooted an update will most likely break your phone, so not that useful.
*made a thread*
Thanks--rooted withOUT adventure too
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
kirkzp said:
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
Click to expand...
Click to collapse
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
kernel with hide-unlock
T_Tank said:
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
Click to expand...
Click to collapse
Full disclosure: I don't use Google pay or too many banking apps, so YMMV. But, I am using j4nn's kernel with unlock hidden. (See link in my note 6.) You can flash this, or you can leave in your stock kernel and merely fastboot to this. From what I have seen, it hides most - if not all -- indicators that the phone is rooted and the BL in unlocked.
Does somebody has :
G8441_1310-7123_47.1.A.16.20-R7B_Customized_CE1.ftf ?
Only backup i did not make, and its gone from XperiFirm.
Still have the feeling battery life was better in Oreo, and would be nice for experimenting.
Would be nice.
Thanks in advance.
Hello,
sorry if the questions may be redundant, but with all the threads on this matter I am a bit confused as to what "macro" operations to perform in order to have a rooted and fully operational device.
So, let us assume that I am going to buy a new, unbranded S10E (Exynos) tomorrow. What I aim to is the following:
have my device rooted
have TWRP
have no bloatware
being able to turn the device on-off normally, without having to perform any "specific" operations (in the rooting guide, I noticed that you have to power on the device with a specific combination of keys in order to boot it with root. I would like to turn it on - in rooted mode - by simply pressing the Power button)
have the latest official updates (at least those compliant with the points above)
So, having said this, can anyone tell me what macro operations to perform in order to meet all these "requirements"?
By "macro operations" I don't mean to describe every individual step; just something like "(i) update firmware normally; (ii) root by following this guide; (iii) TWRP by following this guide; (iv) then do this by following this guide; ... " and so on.
Any additional tips are (very) appreciated!
Thank you in advance!
This is fairly easy.
There are videos on YouTube on how to install everything you need.
TheUndertaker21 said:
This is fairly easy.
There are videos on YouTube on how to install everything you need.
Click to expand...
Click to collapse
Thanks for the heads up.
I know that YouTube is a goldmine of guides, but I still asked my questions here because I was looking for some "up-to-date" answers. YouTube videos/guides tend to get old pretty quickly (especially those regarding techy stuff), and with all the changes occurring regularly, I don't want to risk anything on a ~500€ device
Can I ask you to kindly provide me with a link to the most up-to-date videos that answer all my questions? :laugh:
I dont think u can break this device that easily. If anything happens reflash stock firmware, it is good as new.
Note: do NOT flash SNAPDRAGON firmware on to a exynos device. You will definitely destory it