I was on android 11 which was just way to buggy eo i used the rollback file and since iv rolled back to coloros 7.1 there has been a couple of apps freezing and things, so i tried to install the latest versions from other regions and it says i cant downgrade because this version is lower than the one im on, so basically im looking for a tool like odin so i can flash any firmware i want (besides chinese roms obvs)
Mod edit: THREAD CLOSED as duplicate of https://forum.xda-developers.com/find-x2-pro/help/tools-odin-t4136407
Related
Hey guys,
Samsung Galaxy S4 GT-i9505 International
I was experimenting with LineageOS and SlimROM recently. Decided to go back to my stock ROM. Kies doesn't support restoring my phone in this way. I went on SamMobile, got what I thought was the correct ROM, flashed in via ODIN, and thought all was well.
Ran into problems with WiFi not turning on, then got an error when attempting to update OTA: 'The operating system on your device has been modified in an unauthorised way.' Both the Bootloader and in-OS device status show 'Custom'.
I have a couple of concerns:
Is this ROM potentially compromised or otherwise unsafe?
I've logged in to my Google, Reddit, Discord, etc, accounts on this new ROM. Are these accounts potentially at risk?
How can I find a reliable and trusted ROM for my device?
your phone has a custom recovery or modified bootloader some leftovers
something didn't get flashed from the official ROM in ODIN , maybe a reflash (could also fix wifi maybe)?
did you wipe/clear/format everything also before the ODIN flash sometimes helps for me.
my samsung shows Custom with official (Clean) rom but its to be expected , i have custom recovery TWRP. but i don't use OTA so i don't care its broken.
did you mind that it was custom when using LineageOS and SlimROM , it just wasn't displayed.
i suggest sticking with LOS > TOUCHWI(zzzZzz)
also you can fake system status to Official if you use Xposed touchwiz module
but i don't know if fixes the broken OTA. but it will show Official in your settings.
never had any problems.
hope this helps some.
LineageOS and SlimROM were (7.1.2) ? Official ROM version ? samsung also likes to make it difficult to downgrade sometimes (wifi,modem issues)
Thanks!
So you don't think I need to worry about my data being compromised?
I should mention I was getting a lot of CloudFlare screens while trying to access SamMobile to download this ROM, so I was concerned the file may have been compromised.
i prefer updato to SamMobile , but have used so many roms from both of those sites
they are both legit
SamMobile roms are clean no worries. site is good.
ive lost count how many different roms / models / versions i have flashed from there all perfect.
plus you can verify the MD5 checksum of the (exact) ROM with other sites , sources also. if you want even more proof
forceLaser said:
i prefer updato to SamMobile , but have used so many roms from both of those sites
they are both legit
SamMobile roms are clean no worries. site is good.
ive lost count how many different roms / models / versions i have flashed from there all perfect.
plus you can verify the MD5 checksum of the (exact) ROM with other sites , sources also. if you want even more proof
Click to expand...
Click to collapse
Cheers guys!
I may have screwed up and not formatted as cleanly as I should have before flashing the stock ROM. What's the recommended process for this?
FIXED!
I'm going to make a semi-educated guess as to what happened.
I figure that the first time I flashed the stock ROM after running SlimROM, I had to boot into the download mode/bootloader that was running alongside (or was a part of?) TWRP.
This meant that a little bit of TWRP couldn't be removed during the flash, because it was helping manage the flashing process.
So I went back into the now-stock bootloader and used ODIN to flash the stock ROM a second time, purging the last few traces of TWRP.
I'm now getting WiFi connectivity, OTA updates, and my Device Status has changed to Official. I'm so happy that it was my ****-up and not ROM file that had been messed with.
Hello from Miami
I just brought this monster of a phone, and I've been browsing the different threads; I'm a bit lost.
I own a g1917 version that is on 9.5.13 gm21aa, and naturally I'd like to upgrade to Oxygen. Since ota finds nothing, I'll have to force it. But I see oos roms and dp roms, but I don't know what the difference is.
Can someone kindly point me in a direction? Naturally, I want to root it and load TWRP amd experiment with roms. I previously owned a Huawei mate 10 pro, which was quite restricted.
Thank you
If you want to stay on OxygenOS then download Oxygen updater from playstore and that will let you download the latest update and flash via local storage.
You have the Global version not EU
There are many posts on how to root, twrp and update. Dig a little and u will find some useful information.
*SOLVED: see reply*
The ROM I used before was LineageOS [10.0] and used a custom ROM with Android 9 before that. Needed to unlock my phone, and couldn't do that on Lineage, and had troubles flashing firmware with Odin, so I ended up using FrankensteinS6. The Stock kernel seems to let me input the NCK, and unlock the phone. So that's luckily finally over.
For about 4 days now I've been formatting phone and trying again and again. FrankensteinS6 works, some other 6.0/7.0 ROMs work. But LineageOS now enters a bootloop, and Pixel Experience (9.0 and 10.0) and Evolution X 10.0 don't detect the SIM. The ones that don't detect SIM also show no IMEI, which was worrying at first because I though I lost a partition.
Possibly related, the ROM of Pixel Experience Android 10.0 for G920W8 will not install because (paraphrasing) "This device is zeroflte, this file is for zerofltecan, zeroflte***, zeroflte***" claiming that my phone isn't one of those models. I got this S6 from Bell Canada, and I still have even the sticker that says it is a G920W8, not G920F. However, the Pixel Experience ROM for G920F flashes fine (sans the main problem).
I don't know the exact LineageOS ROM I used before, but I've tried all of their 10.0 releases, tried redownloading, and I get the bootloop every time. I see some info online of flashing modem firmware, but... I don't even know where to start with that. As I mentioned at the start, Odin is crapping out. I couldn't flash firmware with it, because it would reject the phone right after I started flashing. Anything I could do within TWRP would be great. I moved it back to FrankensteinS6 for my sanity, I started doing this Sunday and I'm starting to repeat steps over and over hoping that it just solves itself.
I tried to keep this straightforward, and I'm sure I did a bad job. I can extrapolate on what I have attempted. Please tell me what I have to do to get an android 10 ROM working on this old beauty again.
I do not have all the solutions. As per my tests with my SM-G920W8. I have managed to find ROMS and try them out. I have only seen Nougat 7.0 ROMS to work almost flawlessly. NOT 7.1.2, important, 7.0 only.
I have also tested some Pie and v10 ROMS like Pixel Experience. The ROMS boot nicely but since I do not use a SIM card to call as I use SIP phone numbers and require WiFi. But that left asside, I came upon serious camera issues no matter what I try. Up to now, SamStock ROM is pretty much the best Stock ROM I found but I always need to run the Magisk UNINSTALLER before re-installing the latest Magisk version..
As for Kernels, well, Anything that is oriented with Lineage OS, I've had camera issues even with Nougat v7.0. So basically, the only ROMS I found good, as of today, for now, are stock ROMS v7.0. But, to do your tests, Even if you have a 920F ROM, you can download a 920W8 kernel as long as you download a kernel which supports your installed Android version. Also make sure to download the proper Stock or AOSP kernel (AOSP for LineageOS). There's not many but there's a few ones that work properly.
Another option is to download an AOSP ROM that works for W8 phones, unzip the file and grab the boot file inside corresponding to the W8 or T-Mobile version. You simply unzip your real ROM you want top install, replace the boot file for the one you got and rezip it. This made my phone boot properly for some F version ROMS but again, not without issues. That's why, I really suggest v7.0 Srock ROMS. I hope this helps you a bit. Again, you can have your own tests and other users may have other answers, but this is based off over 30 bootloops in my case of trying to mod a ROM for the W8 model. It's not easy to find a good one for Canada, I admit!!!
I flashed TWRP years ago, and I found out that I had a G920F version flashed. I don't know why Lineage allowed me to use SIM before, but rectifying this issue seems to made the SIM work in newer versions.
I don't know what the S6's predisposition to having crashing cameras is, but I have avoided this in the past by using custom camera apps, like Open Camera. This has saved me every time.
As for the boot loops... I think another thing that helped is that "format data" doesn't wipe the OS. When you are in recovery, having issues with bootloops in various ROMs, try advanced wipe, and wipe the system. It didn't fix right away, but the time I got Pixel Experience 10 up and running that was the trick.
I was having a bunch of issues updating my phone. I kept receiving a System Update Installation Failed error. I tried local using the zip downloaded directly from OnePlus support and it wouldn't work. It said that there was no update available when trying to use the update setting. Long story short...it just wasn't working. I then proceeded to use the MSM Tool to completely erase and reset the phone. STILL wouldn't work. I randomly came across someone saying you needed OxygenOS 9.0.9 before 10..tried it and it worked perfectly. Sigh.
I wanted to save someone else the hassle and document it here with the error I was receiving. Good luck! I got OOS 9.0.9 HERE if anyone needs it and I'm allowed to link.
@bam099
Thanks for sharing the link for 9.0.9
Out of interest which version were you upgrading from and which version MSM tool were you trying?
My OP6 is still on 9.0.8 as I've not had the inclination to go through the hassle of a full reset to restore to factory (BL is unlocked, TWRP is installed, was rooted but got rid of that due to constant hassle with banking apps detecting root and magisk hide not working for all my bank apps)
Now that 11 is released as stable I'm probs going to to the full return to factory stock and then upgrade straight to 11 (once the early adopters have found the first bugs and OP patch them ) but if 9.0.9 was needed to update to 10.x.x I guess the same will be needed for 11.
Surprisingly I took a little bit of notes so I could go back if I wanted to (and I wouldn't waste time searching for issues like this weird 9.0.9 thing I found). I was on 9.0.6 (Build Number A6003_22_190528).
I would imagine that 9.0.9 is going to be needed to get to 11 (I'm on 11 now but I went from 10 so I'm not positive about what is required).
If you download the stock ROM for 9.0.9 can't you upgrade it? I THINK TWRP can flash the update but I'm sure there's some kind of an issue with an unlocked BL and upgrading via the stock app.
I don't recall what version of the MSM tool I used...I was frustrated at that point and not taking notes haha. I keep remembering 4.0.4 so if that sounds right for MSM then that's what I used. But I think any of the ones you see on a guide would work. Good luck with it!
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
wizardknight said:
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
Click to expand...
Click to collapse
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
mattie_49 said:
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
Click to expand...
Click to collapse
Ok. Thanks. I will run the update multiple times, and see if I can get to F18.
I can't believe the naming is all buggered up. Ok, well maybe I can believe it. Seems like OnePlus is just not doing a good job anymore, but there are not many other flagship grade phones with unlocked boot loaders and custom roms anymore (and I have been using custom android roms since the touch pro 2 days). It's making me a sad panda.
I just upgraded from a OnePlus 7t to the 9 because I got a crazy good price for an open box phone on clearance. Now I am starting to wonder if I made the wrong decision.
If I have to download 5+ updates every time something doesn't flash right I am going to burn though my 1TB internet cap in no time.
Update:
After ~10gb of updates I got to F18.
Now to go and get a custom rom on this thing, and hope I don't have to unbrick it again.