Database Info

Failed Downgrading J700F

Hi all. I have Samsung Galaxy J7 2015 (SM-J700F). I just received the recent update (April 2017). However, I don't like it and want to downgrade to the previous one. I have downloaded Odin and the firmware which is J700FXXU2BPH3_J700FOLB2BPH2_XID or whatever you call it. It failed after trying to execute cm.bin file. I have done some research and I found that Samsung has locked the bootloader in order to prevent downgrading process. However, in those threads, they only mentioned about downgrading from Android 6 to Android 5. In my case, I just want to downgrade from the previous security update/patch in the same Android version which is Android 6. Is this still possible in my case to do downgrading to my desired version?

alphamorpho said:
Hi all. I have Samsung Galaxy J7 2015 (SM-J700F). I just received the recent update (April 2017). However, I don't like it and want to downgrade to the previous one. I have downloaded Odin and the firmware which is J700FXXU2BPH3_J700FOLB2BPH2_XID or whatever you call it. It failed after trying to execute cm.bin file. I have done some research and I found that Samsung has locked the bootloader in order to prevent downgrading process. However, in those threads, they only mentioned about downgrading from Android 6 to Android 5. In my case, I just want to downgrade from the previous security update/patch in the same Android version which is Android 6. Is this still possible in my case to do downgrading to my desired version?
Click to expand...
Click to collapse
Probably not possible. It seems that every new bootloader has a software revision number and if you are for example on SW REV 3 you cannot flash a bootloader with SW REV 2. You can read the SW VER from the download mode screen. So in summary, you are now stuck with the new firmware. Sorry about that. That's why I never upgrade my Samsung phones anymore unless I have to.

Could you do it?
I'm having the same problem but with the SM-J710MN version, trying to figure it out a way to downgrade to the previous security patch.
alphamorpho said:
Hi all. I have Samsung Galaxy J7 2015 (SM-J700F). I just received the recent update (April 2017). However, I don't like it and want to downgrade to the previous one. I have downloaded Odin and the firmware which is J700FXXU2BPH3_J700FOLB2BPH2_XID or whatever you call it. It failed after trying to execute cm.bin file. I have done some research and I found that Samsung has locked the bootloader in order to prevent downgrading process. However, in those threads, they only mentioned about downgrading from Android 6 to Android 5. In my case, I just want to downgrade from the previous security update/patch in the same Android version which is Android 6. Is this still possible in my case to do downgrading to my desired version?
Click to expand...
Click to collapse

How to do updates?

I am coming from a Samsung S4 running A5.0.1 which long ago had no more OTA updates.
I just got a new Pixel 4a that came with A11, but I am going to downgrade it to A10 so I can use EdXposed, XprivacyLUA, TWRP, etc., which only fully work in A10.
I want to stay on A10 so those apps will continue to work. But I am concerned about two things:
1) Regular (security?) updates
2) OS updates (A10 -> A11)
Question #1:
If I have a custom boot image (but stock A10 google main OS+radio image) and have Magisk, etc. installed, will it be ok to accept/install #1 type updates (security/OS patches) or will it mess things up like the boot image? If I should not install any updates, then how can I prevent my phone from downloading/installing those updates?
Question #2:
How can I prevent my phone from downloading and auto-updating to A11 (complete OS update)?
Thank you for your advise/help

Samsung Galaxy XCover SM-G398F/FN/DS Adnoird Q boot.img patch, root?

Hi,
What about this device ?
All I could find was "Galaxy XCover 4s SM-G398F/FN Pie 9.0 using Magisk"
All I want to do is install Magisk or LOS but LOS was I think not yet supported (quick search) and old boot.img
device info;
Samsung Galaxy XCover 4s SM-G398F/FN/DS​
One UI 2.0
Android 10
Knox 3.5 API lvl 31 TIMA 4.1.0
Kernel 4.4.177-18237086
Build QP1A.190711.020.G398FNXXS5BTD2
Security software version
- ASKS v3.1 release 20200120
- ADP v3.0 release 20191001
- SMR may-2020 release 1
Android patch level May 1 2020
I haven't updated the rom on the device because this would only makes it harder for me...
Can it run TWRP or any custom recovery unsigned I am willing to experiment with boot.img on my device because without root this phone is useless for me (side load without flashing, like I always do). Have too much phones here for testing but most of them are slow to the snail due to outdated SoC and latest OS/kernel.
let me know I can dump boot.img and we can have fun experiments.
Not sure if this device is able to downgrade rom using odin or if Knox has ARP.
Any hits on next step? Don't feel like wasting lots of time phone is for RE and testing. Nothing special.

How to Patch Stock Boot Image (IMG) using Magisk Manager and root
Once you are sure that you are done with the backup stuff, please proceed to the tutorial below on "How to Patch Stock Boot Image (IMG) using Magisk Manager."
droidfeats.com

As you said there is no lineage os. Just check if your phone supports project treble by downloading treble check app. If supported, you can install variety of andorid 11 roms

Tab E said:
As you said there is no lineage os. Just check if your phone supports project treble by downloading treble check app. If supported, you can install variety of andorid 11 roms
Click to expand...
Click to collapse
Yay just what I needed. System-as-root: supported.
Thanks for that, yeah just got some time to check it out so well, thats neat.

Question [TB-J606L] Downgrade from Android 11

Hello. Yesterday i installed latest OTA Android version (TB-J606L_S320030_210923_ROW) and noticed that it is really slow and it has even more bloatware that i don't want. I don't need to root it (because of bloatware removal) as i also need to revert it to default state as it was before update.
1. It is possible to find which version i had before this upgrade?
2. How could i downgrade system to previous version (i think it was Android 10 but i'm not sure)
PS: I successfully downgraded/rooted some devices but as every brand has it's specific way to perform downgrade, i'm asking here. Any advice would help and i'm aware of dangers of downgrading/rooting devices (bricking). In any case, it would be awesome to also link unbricking guide for TB-J606L, just in case It's always better to have plan B.
Update: I found source of roms for my device but i can't recognize which versions are old Android 10 and which are the new Android 11.

Can we root Pixel 3 with android 12

Hello Guys,
I Just wanted to know how I root my pixel 3 with android 12 just guide mn or is there already a thread than give me a link but plz for android 12

Rooting Android 12 works exactly the same as Android 11 on the Pixel 3.
Since there were no obvious guides, I just wrote one for the Pixel 3. Here you go.

Thanks for help
Can u tell me is there any twrp for android 12

Not that I know of, at least it doesn't work on my rooted P3 running Android 11

Hmm so how we install custom roms

rocketrazr1999 said:
Not that I know of, at least it doesn't work on my rooted P3 running Android 11
Click to expand...
Click to collapse
Update... Android 12 can be rooted using Magisk Canary

I was able to take an OTA update to Android 12 on my BL unlocked, rooted, custom kerneled Pixel 3! I started the update accidentally by hitting that pop up reminder and after a minute of thinking what to do (i did not want to lose my data!!!), I held down the power button to force it to reboot during the update. I have had this work to stop an OTA update and restore it perfectly to previous state. Anyway, it did NOT work this time, and it updated to A12 perfectly! No loss of data, no loss of custom kernel, but i did of course lose root. Also.... when i checked the update version in settings, it wanted to update AGAIN, from Oct 21 to Feb 22 (which is just an Emergency Dialer patch). My phone still shows Oct 21 security patch in settings, but shows the Feb 22 firmware (...016.C1), which suggests the patch was only a tiny fix to the 911 Dialer and did not affect anything else. So this time i let it update, which i started to think was stuck or looping after waiting about an hour, but finally i checked the progress and it was done, requesting a reboot! So i rebooted it and behold, its now running final security update to the Pixel 3, and all i need to do now is root with Magisk and install SafetyNet Fix. Which is the ONLY thing i can think of as to how it was able to do a factory OTA update while rooted and BL unlocked! The SafetyNet Fix patch may be so good that it bypasses the Google security measure that refuses to allow OTA updates on rooted, unlocked Pixel 3s. Yup, on a GOOGLE PIXEL! I used to have to unroot and install the factory kernel to do an OTA sideload on my old Essential in order to update and not lose data, but i was told that you could not update to new Android versions without losing your data on the P3, so Ii just figured my Sept 21 A11 firmware was the final update until a phone upgrade. Anyway, just wanted to pass on the good news that you CAN perform a factory OTA update from A11 to A12 on the Pixel 3 WHILE rooted and unlocked and with a custom kernel, but I of course have to recommend you do so on your own, and if anyone has an unused or non-daily driver P3 that want to confirm this good news, please do so and help convince the disbelievers ! The ONLY thing i would recommend is that you have the latest "Android 12" version of SafetyNet Fix installed with the switches on in Magisk, which is what i had. Its the only thing i can think of that would allow Google's Safety Net to bypass the security restrictions. OK then, hope a few of you give it a try to show im not a nutcase, lol.

Question kind of related to this... Was the P3 kernel updated in Android 12 to fix that race condition that causes freezes if using systemless hosts? With A11 I always had to make sure I installed a custom kernel before Magisk and enabling systemless hosts to keep my P3 from freezing.