Related
This will be for the SM-G935D/SC-02H Japanese variant of the s7 edge.
Stock ODIN firmware: https://www.androidfilehost.com/?fid=457095661767130814 (Marshmallow)
TWRP 3.0.3-0: https://www.androidfilehost.com/?fid=817550096634747128
Rooted Rom: https://www.androidfilehost.com/?fid=385035244224413763
HKernel for hero2qltedcm:https://www.androidfilehost.com/?fid=745425885120706416
Kernel includes:
CVE updated
Permissive
F2FS support
Ramdisk changes the same as hero2qltechn variant. (All changes are the same)
Kernel Change-log:
https://github.com/travismills82/android_kernel_samsung_msm8996/commits/tw-6.0
TWRP Unofficial:
F2FS Support
More partitions supported for backup and restore compared to official version
How to root this device: https://forum.xda-developers.com/s7-edge/how-to/guide-sm-g9350-s7-edge-qualcomm-sd820-t3410969
Reserved
travis82 said:
This will be for the Japanese variant of the s7 edge this is an unlocked model also.
Stock ODIN firmware: https://www.androidfilehost.com/?fid=457095661767130814 (SC02HOMU1APL2)
TWRP: Coming soon
Debloated Rom: Coming soon
Kernel: Coming soon
Click to expand...
Click to collapse
Can this be used for sm g9350 hongkong?
Sent from my SM-G9350 using Tapatalk
Please use common sense and read ITS FOR THE JAPANESE VARIANT.. READ THE MODEL #. Good gosh stop posting stupid questions dude.
Thanks I'll try this when I get to work.
I can't seem to unlock my bootloader, I'm unable to flash TWRP and enter the recovery. It just says Recovery mode -> Warranty bit set: Recovery and enters into a normal boot after trying it a few times.
Edit:
used the official TWRP and recovery now works. Now trying to install the rom
Edit2:
When trying to install it keeps giving me the following error:
This package is for "SC-02h,hero2qledcm" devices; this is a "hero2qltedcm"
Update process ended with ERROR: 7
Error installing zip file '/sdcard/TWRP/SC-02H_Debloated.zip'
Edit3:
I edited the update-script and removed the assert.
However I don't notice any changes in the rom itself. It still has some bloatware (docomo stuff)
ahh ok i thought it would use sco2h not dcm I can fix that sorry, and I assume twrp is doing the same. I will use a dcm kernel in twrp, let me know if that kernel boots please I dont have the device in hand so I am relying on you all to let me know.
USE crom.apk to unlock bootloader you should find it in galaxy apps store. I'm pretty sure others have unlocked their bootloader doing the same thing. I also used to have someone install my hkroms and kernels on the jap variant so I know you can unlock the bootloader.
CROM: https://www.androidfilehost.com/?fid=385035244224394932
can you unlock the bootloader with that, its a link to what we used to unlock ours.
I need you to unlock your bootloader first please. Sounds like that is the issue.
If I run that app it just exits with Crom Service has stopped working.
Your rom works fine, it has root which is what I needed the most.
Just wish there was a way to remove the sim lock from the device without having to beg Docomo.
I bet I have my asserts all messed up here man I'm sorry. I see SC-02H than hero2qltedcm, than SM-G935D soo I need to get this in the correct order. Would you mind shooting me a pm so I can hangouts you so we can knocks this out quickly?
updated op with twrp recovery and kernel.
This works, root and most of the bloated software is gone
Off topic question (need some insight)
You have started to make a working TWRP for the Docomo variant - thank you for your work (hopefully people in JP using the Docomo version find success).
I know this is off topic but I thought you could provide me with a better understanding.
I am currently using the au KDDI variant (SCV33-Snapdragon) and have successfully installed TWRP (3.0.2-0) with ability to mount /data following xda, youtube, and a Vietnamese forum using google translate; BUT I am unable to keep TWRP ability to mount /data after flashing re-engineered boot file via odin to apply root (Snapdragon Variant Root). TWRP can still be used to go into recovery, mount /ext sdcard, and reboot. I've tried many different styles of rooting after and before installing TWRP, in addition to flashing in different ways - but I still failed. It's either have full working TWRP that can mount /data but without root; or, have root but TWRP that can't mount /data (basically useless as it cannot install anything nor, make backups).
I apologize for such long response, any insight or somewhere you can point me to where I can do more research, as this is how far I have come so far, but still fail to acquire both (Yes I have watched numerous YT vids and read countless post stating devs have not yet found a way on the US-Snapdragon variants, which I understand this may apply to the JP variant too) . Thank you.
With the development of ROMs for the Exynos variants (SG935F/FD) moving along apace... I'm wondering if it is feasible to use one of those ROMs with this kernel.
I did something similar to get a custom ROM made for an AT&T S4 onto my DoCoMo S4 (SC-04E) without issues.
Is that a stupid question?
SCV33 looks exactly the same as SC-02H. What's the difference? single sim dual sim? Can you use sc-02h roms for it? I need more information unless you guys want to start donating me devices.
bu06034 said:
With the development of ROMs for the Exynos variants (SG935F/FD) moving along apace... I'm wondering if it is feasible to use one of those ROMs with this kernel.
I did something similar to get a custom ROM made for an AT&T S4 onto my DoCoMo S4 (SC-04E) without issues.
Is that a stupid question?
Click to expand...
Click to collapse
You guys should never flash an engineering kernel anymore. There is no need since you have a custom kernel and ramdisk and twrp now since I made them. Also those are exynos not qualcomm you can port it but it will be a major task to do.
travis82 said:
You guys should never flash an engineering kernel anymore. There is no need since you have a custom kernel and ramdisk and twrp now since I made them. Also those are exynos not qualcomm you can port it but it will be a major task to do.
Click to expand...
Click to collapse
First, I really apprecate the work you have put in on bringing ROOT and TWRP to users in Japan. If I can help by doing some testing for you with my DoCoMo model, I'd be happy to do so!
Regarding my original question, I was not talking about an engineering kernel. I was thinking that if I flashed a custom ROM for the SG-935F Hong Kong (Exynos) model, and then flashed your kernel over it, would it work?
As I understand it, the kernel is the interface between the OS and the hardware. Maybe that is ignorant? The reason I ask is because this process was quite common for Japanese S4 users to employ custom ROMs for US S4s; i.e. Flash the US custom ROM (e.g. Mokee or Albee95) and then flash the Japanese S4 kernel onto it.
I understand the question might seem silly to you, but I don't have the hundreds of hours required to reach your level of expertise. I have invested sufficient time to understand much of the jargon; and the tools and methods employed to get root and flash ROMs. More than that, I rely on asking the experts, like you. :good:
you would have to port firmware framework and a bit of other things, secondly hong kong does not self exynos versions here. It's all Qualcomm.
SCV33 waiting for someone to flash this kernel on it to let me know if its compatible or not.
Anyways updated main thread with BETA 2.
Enjoy,
Travis82
SCV33 test 1
travis82 said:
SCV33 waiting for someone to flash this kernel on it to let me know if its compatible or not.
Anyways updated main thread with BETA 2.
Enjoy,
Travis82
Click to expand...
Click to collapse
Travis,
TESTED (Semi-working)
I've done some testing on my SCV33 variant using what you've made for the SC-02H.
[Kernel]
I flashed the HKernal Beta 2, using the SC-02H FW, and TWRP Unofficial you've provided onto my SCV33 Galaxy S7e and it is really snappy and fast. Very nice kernel. Any DoCoMo users out there should flash this - though still beta it does the job. I had no problems flashing this in TWRP.
[TWRP Unofficial]
I was able to mount all partitions - works. I had no problem flashing this using Odin.
[Problems I've Encountered]
* After rebooting into TWRP Unofficial many times. My log reads "Unable to mount /steady." I have no idea what this is or what partition it belongs too; but, TWRP is still able to do everything else such as mount /data, wipe /system, etc. - I don't think its a big issue to be honest. Just wanted to let you know.
* After installing everything and everything working fine. I do not/cannot communicate with networks (cannot connect to wifi, cannot call, and no data). I had check SIM status = not available, IMEI = Unknown, SN = Unknown. I had made an EFS back up of my KDDI rom with working network communication and restored with with TWRP Unofficial. Installation via TWRP log has stated successful, but upon reboot problem has not been fixed. Any ideas I should try? I also believe the software from the SC-02H OS handles how im about to connect to data towers and catch frequencies. Putting in my own APN does not work.
* Crom Service.apk you've provided at an earlier comment to unlock bootloader, which I've installed, does not work. All it does is FC when trying to open the app - installation is fine. I had also tried getting one from the internet, and looking for it at the Samsung Galaxy App Store - the internet one does the same, FC. Samsung Galaxy App Store does not have Crom Service available. I am assuming SCV33 wont ever be able to unlock bootloader.
* Debloated Rom Zip does not work, after doing a clean install to Stock Odin, installing TWRP Unofficial, system ext4 format, wiping /system /data /internal storage /dalvikArt /cache, and flashing Debloated Rom Zip with TWRP - states installed successful and boots up. Though upon booting I still have all the bloat there. In addition, many FCs from many different apps, even after reboot (e.g. tap and play, google play store, google services). The rom still functions after a couple more reboots after a /dalvikART cache wipe, but it just doesn't seem as fast as the stock one though. I believe this maybe a conflict due to my device, and myself as well.
----
Oh BTW the SCV33 is:
*SM-G935J
*OS 6.0.1
*Single SIM only
I will try my best do to other methods on trying to get this to fully work, but the Network Communication thing always halts my progress. I really dig this kernel man.
Again, thank you for your hard work and dedication to the Snapdragon Variant its very much appreciated :highfive:. Looking at the Exynos sub-forum I get so jelly at times.
OK is yours has a different modem then the rest. Also your partitions might be a bit different, I really need that device in my hands to look at the partition layout. If you can find SCV33 kernel source I will be more than happy to make a kernel for this variant also. I call my kernels beta because it's just how I do it.
Ok found your source for the kernel I'll check out the configs and maybe make a kernel later on this week.
SM-G935J (SCV33)
Here is a test kernel: https://www.androidfilehost.com/?fid=529152257862698452
Rooted rom: https://www.androidfilehost.com/?fid=529152257862698453
Let me know if there is any issues.
Hello!
Here is the full G925VVRS4DQD1 Odin manual update to 7.0 Nougat for everyone to enjoy. You can flash from any current version you have now it doesn't matter whether you are on 5.1.1 or 6.0.1.
https://www.androidfilehost.com/?fid=529152257862722630
If for whatever reason you want to downgrade or don't like 7.0, you can safely downgrade to any of the below versions without any issues. After you flash a lower android version using Odin, phone might get stuck on Verizon logo. If that happens, all you need to do is boot into recovery and do a factory wipe/reset and phone will boot right up after that.
G925VVRS4CQA3 (6.0.1) - https://www.androidfilehost.com/?fid=529152257862700500
G925VVRS4CPL3 (6.0.1) - https://www.androidfilehost.com/?fid=673368273298921946
G925VVRU4CPK2 (6.0.1) - https://www.androidfilehost.com/?fid=385035244224407601
G925VVRU4CPD2 (6.0.1) - https://www.androidfilehost.com/?fid=24566454284190657
G925VVRU4BOK7 (5.1.1) - https://www.androidfilehost.com/?fid=24269982087018504
G925VVRU4BOG9 (5.1.1) - https://www.androidfilehost.com/?fid=24052804347845467
Thanks a lot! I downloaded one from sammobile but there was one only one file, modified date 4/07...
I notice the files within the zip from your link mention REV02 and are dated 4/26.
G925V_G925VVRS4DQD1_VZW_USA_v7.0_IMEIAUTHORITY.COM.zip
2.54 GB (2,732,088,886 bytes)
MD5: 145a137d2c639b30ef5addac9094f331
I have attached the results from HashMyFiles for the 4 within the archive (Filename, MD5, SHA1, CRC32, SHA-256, SHA-512, SHA-384, Modified Time, File Size).
@toutanje Out of curiosity, how did you determine which builds you can safely downgrade to from 7.0? Is it something you personally tested or did someone recently go through the hard work and post their results somewhere? BTW, you can now add G925VVRS4CQA3 (6.0.1) - https://www.androidfilehost.com/?fid=529152257862700500 as two people have confirmed downgrade success here: https://forum.xda-developers.com/verizon-galaxy-s6-edge/help/downgrading-nougat-t3601096 . One used firmware from sammobile and the other directly from the link above. This is the very last build available for Marshmallow.
Hi there. I installed the new update on my s6 edge 7.0 via verizon software updating tool.am noticing the sound quality of mt s6 edge has been changed.before the sound quality was thick and now its not that thick anymore.i want to bring back the thick quality sound on my s6 edge.there is setting called sound quality and effects but i cant manage to get back that sound quality i had with 6.0. Is there anyone who able to notice this change in the sound?
blkt said:
@toutanje Out of curiosity, how did you determine which builds you can safely downgrade to from 7.0? Is it something you personally tested or did someone recently go through the hard work and post their results somewhere? BTW, you can now add G925VVRS4CQA3 (6.0.1) - https://www.androidfilehost.com/?fid=529152257862700500 as two people have confirmed downgrade success here: https://forum.xda-developers.com/verizon-galaxy-s6-edge/help/downgrading-nougat-t3601096 . One used firmware from sammobile and the other directly from the link above. This is the very last build available for Marshmallow.
Click to expand...
Click to collapse
With a very a simple observation, no testing or anything needed
G925VVRS4DQD1 <-- you see the 4 towards the end of firmware build? That is the revision bit number. This means you can flash ANY firmware for that model with a 4 or higher. Take this 5.1.1 firmware for example ---> G925VVRU3BOG5. Even though this firmware is also 5.1.1 like the ones from above, this particular one will NOT work because it is on an older firmware revision bit (3).
The same is true and goes for ALL Samsung phone/tablet models and firmwares.
toutanje said:
With a very a simple observation, no testing or anything needed
G925VVRS4DQD1 <-- you see the 4 towards the end of firmware build? That is the revision bit number. This means you can flash ANY firmware for that model with a 4 or higher. Take this 5.1.1 firmware for example ---> G925VVRU3BOG5. Even though this firmware is also 5.1.1 like the ones from above, this particular one will NOT work because it is on an older firmware revision bit (3).
The same is true and goes for ALL Samsung phone/tablet models and firmwares.
Click to expand...
Click to collapse
That is very good to know. Yeah I noticed it about the firmware naming convention but I had no idea what the value means (or the character before revision bit, U has become S). My phone out of the box was on G925VVRU3BOG5, so I guess I could go all the way back to G925VVRU4BOG7 if "needed" lol.
One of my fears about Nougat is about all the work they did to automate and place updates into the background. This could allow disabling of downgrades, or anything else at the discretion of Samsung and/or the carrier. I think this has already been done in Marshmallow, just on a smaller scale for security fixes. Anyway, it seems to me like an attack vector waiting to happen: less control over my phone combined with an easy way to break things. Imagine all the troubleshooting fun we will have.
So I upgraded to nougat. I'm having battery issues and just want to go back to marshmallow. but I'm having problems. The nougat rom installs just fine with odin. But when I try with any of the 6.0.1 roms it was failing. Then I noticed that re-partition was chcekd. So I unchecked it and now it goes through the process just fine. But now the complains with dm-verity verification failed. I can install nougat on it no problem. It's just the downgrade that's not working... any clues?
toutanje said:
With a very a simple observation, no testing or anything needed
G925VVRS4DQD1 <-- you see the 4 towards the end of firmware build? That is the revision bit number. This means you can flash ANY firmware for that model with a 4 or higher. Take this 5.1.1 firmware for example ---> G925VVRU3BOG5. Even though this firmware is also 5.1.1 like the ones from above, this particular one will NOT work because it is on an older firmware revision bit (3).
The same is true and goes for ALL Samsung phone/tablet models and firmwares.
Click to expand...
Click to collapse
I actually managed to get the N925V to downgrade all the way back to the firmware version G925VVRU3BOG5.. May have cost some money for some very specific files but my phone's back on G925VVRU3BOG5 and it's really only a test phone for someone I do work for! I have it rooted with SuperSU and not kingroot and I created a script to keep the phone set to "permissive" so it's able to do full reboots and not just hot reboots using xposed... Unfortunately it seemed like no one cared about it when I posted it in the other thread so it's probably not worth it to a lot of people but I think it is with the amount of fine tuning I did to get it to where it is today!!
MrMike2182 said:
I actually managed to get the N925V to downgrade all the way back to the firmware version G925VVRU3BOG5.. May have cost some money for some very specific files but my phone's back on G925VVRU3BOG5 and it's really only a test phone for someone I do work for! I have it rooted with SuperSU and not kingroot and I created a script to keep the phone set to "permissive" so it's able to do full reboots and not just hot reboots using xposed... Unfortunately it seemed like no one cared about it when I posted it in the other thread so it's probably not worth it to a lot of people but I think it is with the amount of fine tuning I did to get it to where it is today!!
Click to expand...
Click to collapse
Mike! Can you explain how you did it? I'm stuck on nougat. Every time I try to downgrade, I get the dm verity error. I've tried all the 6.0.1 version and the 5.0.1. No luck . I'm back on nougat. Can you please let us know your process... Thanks!
Did you have to select anything special in the options? I just left it at default which is Auto reboot & F. Reset Time.
strandedhuman said:
Mike! Can you explain how you did it? I'm stuck on nougat. Every time I try to downgrade, I get the dm verity error. I've tried all the 6.0.1 version and the 5.0.1. No luck . I'm back on nougat. Can you please let us know your process... Thanks!
Did you have to select anything special in the options? I just left it at default which is Auto reboot & F. Reset Time.
Click to expand...
Click to collapse
I mean I could but I had to shell out some money for this firmware and I don't even know if you can flash it with odin because I don't use odin I bought a box to do my flashing since I work on so many phone's and odin just doesn't cut it.
No Worries. Finally figured it out. Good luck to you
MrMike2182 said:
I mean I could but I had to shell out some money for this firmware and I don't even know if you can flash it with odin because I don't use odin I bought a box to do my flashing since I work on so many phone's and odin just doesn't cut it.
Click to expand...
Click to collapse
I was able to use this to flash my Samsung Galaxy S6 Edge from 5.1.1 to 7.0.
Not that I want to upgrade again, but is there a 7.1.2 available? Is there a routine schedule for that sort of thing or was the 7.0 Nougat think kind of a special case?
Thanks!
--
Furry cows moo and decompress.
WyrdWyrd said:
I was able to use this to flash my Samsung Galaxy S6 Edge from 5.1.1 to 7.0.
Not that I want to upgrade again, but is there a 7.1.2 available? Is there a routine schedule for that sort of thing or was the 7.0 Nougat think kind of a special case?
Click to expand...
Click to collapse
I haven't been keeping up, but now curious. Verizon shows DQH1 as current (a 7.0 build), while sammobile and androidfilehost show four builds available (all 7.0).
Ok, so I updated my G925V with nougat, now I'm just wondering if anyone has come out with a way to root this build? That's what I'm waiting for. Plz fill me in when that happens. Thanks.
MrMike2182 said:
I mean I could but I had to shell out some money for this firmware and I don't even know if you can flash it with odin because I don't use odin I bought a box to do my flashing since I work on so many phone's and odin just doesn't cut it.
Click to expand...
Click to collapse
I've been wanting to get one too. Which box plus tool do you use?
Delgoth said:
I've been wanting to get one too. Which box plus tool do you use?
Click to expand...
Click to collapse
I use the Z3x box and Octoplus box I have 2 of them for different phone makers but I have so many different wire connectors that I lost count because what works on Samsung doesn't work on LG, HTC etc etc.. You can find them pretty cheap but I'd avoid buying from eBay because of to many scams selling broken or bad boxes that can't be activated.
Team Z3x .com
MrMike2182 said:
I use the Z3x box and Octoplus box I have 2 of them for different phone makers but I have so many different wire connectors that I lost count because what works on Samsung doesn't work on LG, HTC etc etc.. You can find them pretty cheap but I'd avoid buying from eBay because of to many scams selling broken or bad boxes that can't be activated.
Team Z3x .com
Click to expand...
Click to collapse
was this the only way to downgrade? im on 6.0.1 and im not able to downgrade to 5.1.1 for root lol
raven213 said:
was this the only way to downgrade? im on 6.0.1 and im not able to downgrade to 5.1.1 for root lol
Click to expand...
Click to collapse
You unfortunately cannot downgrade the bootloader once you updated to 6.0.1 you lost the ability to go back and there's so far, no way possible to do it.
Hi All,
I urgently need some help to downgrade Samsung Galaxy Note 9 phone Model No: SM-N960F/DS from currently running OS Android 10 to Android (Oreo) 8.1 or 8.0.
Following are the current versions running:
Software version: SAOMC_SM-N960F_OXM_XSA_QQ_0016
Knox Version: Knox 3.4.1, Knox API Level: 30, TIMA: 4.10.
I have downloaded the XSA version of Android 8.1 from Sammobile, followed all the instructions by running Odin3 V3.14.4, gone into the Download mode of the phone. The phone connects to Odin as I can see on Odin status of Blue Colour Com connection established, Odin then displays "Recovery", unfortunately the phone gets stuck at this status showing "Recovery". I have let the phone run for hours or even a full day but the status never changes from "Recovery"
Could anyone please assist me to complete the downgrade. Am I missing any step here?
Thanking you in advance
I don't think downgrade to oreo is possible. Pie is possible if baseband version's 5th character from the back is 4.
Rosli59564 said:
I don't think downgrade to oreo is possible. Pie is possible if baseband version's 5th character from the back is 4.
Click to expand...
Click to collapse
Thank you for the prompt reply. I just check the digit, its 6 not 4. What are my options here?
None. Your options are only firmwares with the number 6, which date to April/May, last OneUI 2.0 firmwares.
I did read that one can flash custom roms that are older, if one leaves Bootloader untouched to v6, but that is something i wouldn't encourage to do.
PlutoDelic said:
None. Your options are only firmwares with the number 6, which date to April/May, last OneUI 2.0 firmwares.
I did read that one can flash custom roms that are older, if one leaves Bootloader untouched to v6, but that is something i wouldn't encourage to do.
Click to expand...
Click to collapse
Thank you PlutoD, I am happy to read about it as well, if you want to post the link or let me know where to find the info.
CrazynWild said:
Thank you PlutoD, I am happy to read about it as well, if you want to post the link or let me know where to find the info.
Click to expand...
Click to collapse
I have no links except the Development board here, my input came as something that i've seen discussed somewhere in there.
As you can see, there are some Oreo Custom ROMs, i'm not sure if they are actively maintained (if one can say anything active about that), but if you are determined to do what you want, i would start by choosing the ROM first, put a question there or the last resort, contact the developer.
I'll be very blunt with you, i see no reason for people to revert to older roms, but i dont want to get in to that argument, but having a v6 Bootloader (and maybe Modem too) with a v1/v2 system firmware is something that could give you unpredictable issues nobody could help you with.
Could boot a pie custom rom with android10 bootloader. Not sure about oreo though
I didnt spot the message about losing GearVR and now having upgraded my GearVR is not functional. It says I cannot go back but... this is XDA so, can i ??
Also not sure if I can re-install the Oculus GearVR app (can't see it on PlayStore) so does anyone know which APKs I need to install as well?
on my s10+ i get se same Issue. According official samsung information, it seems that gear VR do not run on android 12. I did not find any solution for now.
Methanoid said:
I didnt spot the message about losing GearVR and now having upgraded my GearVR is not functional. It says I cannot go back but... this is XDA so, can i ??
Also not sure if I can re-install the Oculus GearVR app (can't see it on PlayStore) so does anyone know which APKs I need to install as well?
Click to expand...
Click to collapse
Sorry don't know anything about gearVR, but no, if the bootloader version has increased, which I believe it does when going to A12, then you can't downgrade.
I'm pretty sure there is no xda 'work'a'round' for that, haven't seen one and everything I've read indicates not possible. Do some searching I guess to be positive, but one prereq to bootloader unlock is being on a specific BL version, and even their directions indicate if you're above that version, nothing you can do.
cheers
Thanks for replying... I guess I am boned
I successfuly reverted to Android 11 G975XXSEFUJ2 from Android 12 since I saw issue about GearVR...IF you are on first release of A12 you can downgrade.
Flash all A11 stock firmware package and choose CSC instead Home_csc !
tin2404 said:
I successfuly reverted to Android 11 G975XXSEFUJ2 from Android 12 since I saw issue about GearVR...IF you are on first release of A12 you can downgrade.
Flash all A11 stock firmware package and choose CSC instead Home_csc !
Click to expand...
Click to collapse
You have the S10+, from what I see, the most recent BL version is 6 on both a11 and the new a12, so that fits the requirements.
It looks like for at least some of the S10 firmware upgrades, the BL version changes, thus u cannot go back if that's the case. Not all A12 updates are out for the S10, so we don't know yet if the BL version will change for them.
Yes.I think they left compatible downgradable bootloader for those users who didn't saw info about GearVR support as a last chance to revert.
I presume,as we learned from previous updates, in future releases of A12 downgrade will not be possible because of their privacy paranoia.
AsItLies said:
You have the S10+, from what I see, the most recent BL version is 6 on both a11 and the new a12, so that fits the requirements.
It looks like for at least some of the S10 firmware upgrades, the BL version changes, thus u cannot go back if that's the case. Not all A12 updates are out for the S10, so we don't know yet if the BL version will change for them.
Click to expand...
Click to collapse
I have the S10 and from what I can tell the BL version is also 6 on my A12 update.
Does this mean I can just use odin to load a "compatible downgradable bootloader" and I will be able to downgrade back to 11? Does my phone have to be unlocked to do this?
Assuming I back up all my data, will I be able to go back to 11 without compromising my xfinity number, security, ect.? I am simply looking for the best way to just revert back to 11 and reload everything I was using before.
Johnm77 said:
I have the S10 and from what I can tell the BL version is also 6 on my A12 update.
Does this mean I can just use odin to load a "compatible downgradable bootloader" and I will be able to downgrade back to 11? Does my phone have to be unlocked to do this?
Assuming I back up all my data, will I be able to go back to 11 without compromising my xfinity number, security, ect.? I am simply looking for the best way to just revert back to 11 and reload everything I was using before.
Click to expand...
Click to collapse
Well as far as I know you can, but that's from what I've read, not from doing the exact scenario you speak of. Sometimes we just have to try it to know for sure. I have read for sure the if the BL isn't the same version, you can't go back. And no, the phone does not have to be unlocked.
good luck
AsItLies said:
Well as far as I know you can, but that's from what I've read, not from doing the exact scenario you speak of. Sometimes we just have to try it to know for sure. I have read for sure the if the BL isn't the same version, you can't go back. And no, the phone does not have to be unlocked.
good luck
Click to expand...
Click to collapse
Thank you for your help!
I figured the most recent update of A11 from
Galaxy Firmware - Samsung Galaxy S10 SM-G973U (CHA) | G973USQU6GUJ3
This Firmware flash for Samsung Galaxy S10 with the Phone Model Number SM-G973U for region 🇺🇸 United States with CSC code CHA and R(Android 11) OS.
galaxyfirmware.com
is what I would need.
The Baseband I have from A12 currently is G973USQU6HULD, so from what was said here the BL ver. 6 means I should be able to do it.
Model #, Country, region/carrier from the above link all match my specs. So if I'm to understand correctly all I should have to do is backup and then use the firmware with odin to flash to my device using tin2404's procedure from above? (Flash all A11 stock firmware package and choose CSC instead of Home_csc !)
tin2404 said:
I successfuly reverted to Android 11 G975XXSEFUJ2 from Android 12 since I saw issue about GearVR...IF you are on first release of A12 you can downgrade.
Flash all A11 stock firmware package and choose CSC instead Home_csc !
Click to expand...
Click to collapse
Doesn't choosing CSC clear all the app data and basically factory reset it? Wouldn't I want to use Home_CSC, or does it not then work properly?
Johnm77 said:
Doesn't choosing CSC clear all the app data and basically factory reset it? Wouldn't I want to use Home_CSC, or does it not then work properly?
Click to expand...
Click to collapse
Update:
Successfully used odin to revert to os11, had to factory reset after odin completed, then I just reloaded my backup.
After more research I decided to block all future updates using ADB and this method:
No more headaches with my software!
Actually, it is neccessery to choose clear CSC to erase leftovers..Choosing Home_CSC brings various of errors possible.
Workaround is doing TWRP backup on SD Card then after clear flashing restoring ONLY data partition.
I'm looking for a good source of firmwares, i know the famous sites but some firmwares doesn't seem to be listed. I know in the time os Samsung KIES there were tools which communicated directly with samsung.
For example these firmware builds for the SM-G975Ux aren't listed on most firmware sites but have the December secutiry update with binary/bootloader version 8: G975USQS8IVL1 and G975USQS8IVL2
All the big sites have ROMs for that phone (same one I have). There is no "Ux" model... it's *U or *U1, with the latter being unlocked. IF you search for U1 ROMs you have many selections, but most get the XAA version which will usually change carriers automatically based on the SIM card.
The latest BL=8 version I see there is https://www.sammobile.com/samsung/g...M-G975U1/XAA/download/G975U1UEU8IWB6/1741280/ which is the February 2023 security update. I believe this is the last one we are getting (but I could be mistaken as there may be 1 more security patch, I don't remember).
There's U U1 0 W F N .... I'm looking for the oldest firmware with binary version 8, but it seems the sites don't show all firmwares available.... i'm looking for the oldest firmware with U8 bootloader (or any compatible bootloader with binary 8 version), i could have a look at all sites and try my luck... but they don't seem to have all data. but like i said i prefer some original source xml files... i saw some url's to original samsung servers but can't find them anymore.
There is already a firmware available with the march update.... but you have to be lucky to find them... i'm looking for original sources. like update.zip's and such
Found the first one....
https://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G975U/version.xml
I'd recommend around sammobile and samfw. These are the two sources I use the most
hey!
after I wanted to update my g973f from "G973FXXUGHVK1" to "G973FXXSGHWC2" (I tried odin 3.13 and odin 3.14) and an error occurred, I can't install anything anymore... recovery and download mode work, and I can also flash the original firmware, but the device no longer boots into the system! even custom roms don't want to boot anymore
Can anybody help me further?
Ben1987 said:
hey!
after I wanted to update my g973f from "G973FXXUGHVK1" to "G973FXXSGHWC2" (I tried odin 3.13 and odin 3.14) and an error occurred, I can't install anything anymore... recovery and download mode work, and I can also flash the original firmware, but the device no longer boots into the system! even custom roms don't want to boot anymore
Can anybody help me further?
Click to expand...
Click to collapse
Do you mind explaining a bit more? Do you mean like that it boots you into recovery only or?
WooBLOATERRRR said:
Do you mind explaining a bit more? Do you mean like that it boots you into recovery only or?
Click to expand...
Click to collapse
if i flash a new rom (whether original or custom rom) nothing happens after the reboot... download mode works too, flashing twrp works too! however, the system boot does not work via twrp either... not even a bootloop, the cell phone does not react at all! the task combination for
Right now I don't even care if I get the original firmware or a custom rom running... I hope I didn't brick it (((
My old device was a G930F, its unbreakable make sure you flash the right rom and wipe data and dalvik cache after flashing.... THis ons is locked so it doesn't have fastboot. My G-930F came with fastboot enabled so you can always fastboot a recovery.img. like TWRP
Did you try to download TWRP from twrp.me and "fastboot boot twrp-3.7.0_9-0-herolte.img" ? it should boot to twrp in fastboot mode (hold volume down + home + power).
Ben1987 said:
if i flash a new rom (whether original or custom rom) nothing happens after the reboot... download mode works too, flashing twrp works too! however, the system boot does not work via twrp either... not even a bootloop, the cell phone does not react at all! the task combination for
Click to expand...
Click to collapse
1. is your KG status is broken?
2. Is your bootloader unlocked?
You know how to flash lineageos through twrp right? and how to use odin?
Maybe flash lineageos to see if everything works.... and then revert to original software. Be sure to wipe cache/dalvik and userdata
DaanNL said:
There's U U1 0 W F N .... I'm looking for the oldest firmware with binary version 8, but it seems the sites don't show all firmwares available.... i'm looking for the oldest firmware with U8 bootloader (or any compatible bootloader with binary 8 version), i could have a look at all sites and try my luck... but they don't seem to have all data. but like i said i prefer some original source xml files... i saw some url's to original samsung servers but can't find them anymore.
There is already a firmware available with the march update.... but you have to be lucky to find them... i'm looking for original sources. like update.zip's and such
Found the first one....
https://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G975U/version.xml
Click to expand...
Click to collapse
Yes, I know there are many other variant firmwares out there, but for a U phone (snapdragon) there is really only U and U1... the rest are incompatible.
There is no "older" firmware with binary 8, because the firmwares are packaged with the proper/compatible binary already. Basically, the "binary" is the bootloader version. On Snapdragon phones, you must have the proper BL/binary to flash, as you already know. You can't interchange the binary/BL with the ROM and security updates because they are not made that way.
The update.zip you're looking for are updates sent by Samsung directly, and they can update the ROM (and Binary) from one stock version to another... but, again, they will update both the binary/BL as well as the ROM, so they can't be broken up to only do one or the other.
It sounds like you're trying to get to an older ROM version (for whatever reason) with an older security patch level as well? Basically, this cannot be done on Snapdragon phones. Once you're on an updated binary/BL, you're stuck there (at least today you are).
WooBLOATERRRR said:
I solved the problem! I had unlocked the bootloader, but I also had to deactivate verity via CMD with twrp+adb "adb disable-verity"
ok i've solved the problem now, but does anyone know why i couldn't even start the original stock roms? Actually, the stock ROM should set everything to factory settings...
Click to expand...
Click to collapse
WooBLOATERRRR said:
1. is your KG status is broken?
2. Is your bootloader unlocked?
Click to expand...
Click to collapse
Thank you for helping so quickly with ideas... I would not have expected such quick help with such an old model, even samsung customer service didn't want to help me yesterday
Ben1987 said:
Thank you for helping so quickly with ideas... I would not have expected such quick help with such an old model, even samsung customer service didn't want to help me yesterday
Click to expand...
Click to collapse
Samsung/apple support in a nutshell
schwinn8 said:
Yes, I know there are many other variant firmwares out there, but for a U phone (snapdragon) there is really only U and U1... the rest are incompatible.
There is no "older" firmware with binary 8, because the firmwares are packaged with the proper/compatible binary already. Basically, the "binary" is the bootloader version. On Snapdragon phones, you must have the proper BL/binary to flash, as you already know. You can't interchange the binary/BL with the ROM and security updates because they are not made that way.
The update.zip you're looking for are updates sent by Samsung directly, and they can update the ROM (and Binary) from one stock version to another... but, again, they will update both the binary/BL as well as the ROM, so they can't be broken up to only do one or the other.
It sounds like you're trying to get to an older ROM version (for whatever reason) with an older security patch level as well? Basically, this cannot be done on Snapdragon phones. Once you're on an updated binary/BL, you're stuck there (at least today you are).
Click to expand...
Click to collapse
I've tried different firmwares, its all about snapdragon. You can also flash SM-G975W parts and other snapdragon variants.... there's a lot of variants out there.
I first upgraded and then downgraded to the parts i wanted and am on a rom now with security patch level December 2022, as long as the binary version is the same there's no problem. I've got the latest modem installed and the oldest firmare and bootloader for the latest binary version, i can upgrade or downgrade my bootloader. I already asked someone before if this was possible and if he could confirm because before i was only able to flash CSC and AP i think.
If there's no updates comming anymore why not downgrade and wait for a new leak
I'm also sure we can unlock the bootloader, i'm trying to make an lposed module. I've installed lspatch and lposed and they work fine for some modules. The bootloader unlock has several prerequisites (properties and such) if i can make it look for other properties or something like that we might get an unlock option. Also it looks for an encrypted file on EFS, if someone with an unlocked samsung phone could copy that file we would be a lot further.
It's called /efs/sec_efs/sktdm_mem/encmembership.txt and should be an encrypted file, also if anyone knows how to set ro properties without root (like a stub before the preference controller starts) this would be very usefull.