Develop Bugs

[December 6,2013][ROM] [PrimoC] Stock-Rooted Virgin Mobile HBOOT 1.57.0000

View attachment primoc_boot_unsecure.imgPlease excuse my absence. I will not be watching this thread for the time being. Hopefully if you have any questions, they can be answered by using the search option or someone else with this device that happens to check this thread will be kind enough to help.
!#I'M BACK#!​
soon enough we won't need this thread, because we will all be able to RUU lol-Dec 6, 2013
beaups said:
posted on rumrunner.us. should work for both primou and primoc. Note, it is highly recommended (mandatory?) to be on a normal sense-based ICS rom and using an unsecure (preferably stock based) kernel. If you get poor results with other configurations, don't bother asking for help please!
Click to expand...
Click to collapse
S-OFF is here rumrunner.us
Huge thanks to beaups
This rom is probably most compatible with rumrunner
The boot.img inside is unsecure so flash away and GO GET S-OFFED!!!
Here's the unsecure boot.img that I used to achieve s-off.
View attachment primoc_boot_unsecure.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Added init.d support
Added Root Permissions with Chainfire's SuperSu
This ROM was cooked with dsixda's Android Kitchen
Thank you and credit goes out to the both of them.
CLICK HERE TO DOWNLOAD

I have posted this ROM for safetynet/fall-back purposes.
I've noticed fellas posting please help, I forgot/didn't make a backup.
This is for you. Worried and maybe even a little scared that your phone is now a beautiful paper weight.
This ROM is completely stock with added init.d support and root.
It is still odexed, and with stock kernel.( I'm still learning/attempting to build one with extra governors and over clocking abilities ).
Instructions below....

1. Unlock your Bootloader by following the instructions at htcdev
1a. If you've succesfully unlocked your Bootloader, that means you have your fastboot files on your PC and know in general how to use them.
2. Download an openrecovery of your choice. I personally use TeamWinRecoveryProject 2.2.0 without any issues at all. (See the attached File)
3. Place the recovery.img that you have chosen into your fastboot folder.
3a. Change the name of the .img to recovery.img (just easier that way when sending the flash command)
4. Now open a terminal while in the fastboot folder.
4a. On Windows- hold shift+right click the mouse then click open command terminal here.
4b. On Ubuntu- CTRL+ALT+T to open a terninal then cd fastboot.
5.fastboot flash recovery recovery.img​
5a. ^^^^^ Type this into the terminal. ^^^^^
5b. You now have a custom/openrecovery.
6. After the recovery.img is flashed, reboot your Bootloader.
6a. fastboot reboot-bootloader​
7. After booted back into bootloader, use your volume-down button to highlight Recovery.
Now press your Power button to select it.
7a. Now your are in Recovery!
8. Click Wipe, then Cashe, then Dalvick, then Factory Rest, then System.
8a. This will wipe all of your phone nice and clean for a fresh install.
9. Click Home, then Install, and find the ROM.zip, click it, then install. Let it finish installing the click Wipe Cashe/Dalvick.
10. Navigate back to the Home screen and click Reboot, then Bootloader
10a. I hope you have a copy of the ROM.zip on your PC.
11. Open the ROM.zip and copy/extract the boot.img from inside it and place it in your fastboot folder.
12. Open a terminal once again.
13.fastboot flash boot boot.img​
13a. Let it finish.
14. fastboot reboot​
15. Enjoy.
These instructions are for use with TWRP (TeamWinRecoveryProject) They may be different using CWMrecovery (ClockWorkMod).

I made a backup of my stock rom via twrp. Updated the kernel and installed shpongle. When I tried to go back to my stock via twrp it would not boot due to the kernel. I wonder if that will be the case here

lostboybinns said:
I made a backup of my stock rom via twrp. Updated the kernel and installed shpongle. When I tried to go back to my stock via twrp it would not boot due to the kernel. I wonder if that will be the case here
Click to expand...
Click to collapse
u flashed shpongle? that means u are GSM not CDMA so this ROM just simply won't work
as for returning to stock, u can always flash a sense kernel duh

This is for primoc CDMA Virgin Mobile

I just downloaded and flashed to test, everything is working....Just like stock

This should allow me to update my PRL, right?

YUP!

Turns out it was a network fluke?

wont flash for me, i get:
"error executing updater binary in zip
and
error flashing zip
going to try a full format of the sd card...

russellvone said:
Turns out it was a network fluke?
Click to expand...
Click to collapse
What was a network fluke?

I'll cross reference the updater-script to another one I've used on a different Rom I cooked and have been running for over two weeks..... See if there are any differences between the two.

lilrob1213 said:
What was a network fluke?
Click to expand...
Click to collapse
I was replying to zombiegirl's question about updating her/his PRL

Matt_the_Geek said:
wont flash for me, i get:
"error executing updater binary in zip
and
error flashing zip
going to try a full format of the sd card...
Click to expand...
Click to collapse
Ok I found a difference in the updater-script, the update binaries are identical so that shouldn't be the issue. Problem I have is that I don't have a working computer to fix the updater-script. It won't be until June 26th that I can apply it. Sorry for the inconvenience.
P.S. are you flashing with TWRP?

Yes sir, TWRP. and no worries, it apparently just isn't your ROM. Angry HTC and jmz's stock ROM both give the same error. even after a full format of the SD. Rhythmic Rom 1.4 works though, and is what I was running. Was trying to return the device to somewhat stock tho as im either going to sell it or let my gf use it, so I was hoping for stable and to have the charge LED and icons working, hopefully.

Matt_the_Geek said:
Yes sir, TWRP. and no worries, it apparently just isn't your ROM. Angry HTC and jmz's stock ROM both give the same error. even after a full format of the SD. Rhythmic Rom 1.4 works though, and is what I was running. Was trying to return the device to somewhat stock tho as im either going to sell it or let my gf use it, so I was hoping for stable and to have the charge LED and icons working, hopefully.
Click to expand...
Click to collapse
If you downgrade TWRP to 2.3 you should be fine.
Sent from my One V using xda premium

ah, I'm on 2.5, so I'll look into that...

did the downgrade to TWRP 2.3.0.0, still the only thing i can install is Rhythimc Rom, everything else fails to install... unless i just got some really crappy downloads, so i'm off to try to dl the roms again...

Actually, instead I swapped out recoveries for CWM. aaaand it worked.

Help! Just cannot get rooted!

Hello, I have tried every root on the internet for my samsung galaxy s3 spring android 4.3 and I have the cwm installed and working, and I can flash without the error that you cannot mount the sdcard. I have tried every root and it still says that my phone is not rooted, through root checker and supersu also says that it is not rooted. Please, help! I've used the instructions at www . epiccm . org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
I am very frustrated with this, and am about to give up. Please help.
Thanks.
-1998golfer

When i open supersu (i donwloaded it from the app store) it says:
"There is no SU binary installed and SuperSU cannot install it. This is a problem!"

Try flashing THIS in Recovery.

Try the repository for a odin one click @ http://rwilco12.com/

prboy1969 said:
Try flashing THIS in Recovery.
Click to expand...
Click to collapse
Nope. Didn't work =/ Still says I do not have root access in root checker.

still not working
Drennan said:
Try the repository for a odin one click @
Click to expand...
Click to collapse
I can't find what you're talking about but I tried all of the superuser flashable zips (supersu, superuser, and MIUI. None of them worked. They said updating android when I booted, but it still doesn't show as root. It tells me no su is installed and then KNOX comes up telling me that it tried to access a secure area.
Please help

So it sounds like knox is what is killing your attempts. You need to disable it and then reinstall your super user of choice (I like supersu, but I'm sure you can find experts to tell you more about them....). Assuming you have a super user app there, but it is just being squashed, this may work for you...
Go into your explorer of choice (I use explorer es), go into /system/app and find superuser.apk. Select it and force it to install again. When it installs, it will open and tell you that knox is there and ask you if you want to try to disable it. Click ok or yes... I don't recall which, but just get that thing out of there. My guess is at this point, you'll need to actually repeat this process (I did) to get everything "happy"... (repeat the install - but the next time the knox question won't come up).

Cluefree said:
So it sounds like knox is what is killing your attempts. You need to disable it and then reinstall your super user of choice (I like supersu, but I'm sure you can find experts to tell you more about them....). Assuming you have a super user app there, but it is just being squashed, this may work for you...
Go into your explorer of choice (I use explorer es), go into /system/app and find superuser.apk. Select it and force it to install again. When it installs, it will open and tell you that knox is there and ask you if you want to try to disable it. Click ok or yes... I don't recall which, but just get that thing out of there. My guess is at this point, you'll need to actually repeat this process (I did) to get everything "happy"... (repeat the install - but the next time the knox question won't come up).
Click to expand...
Click to collapse
How do i disable knox. I've stopped all the processes and even (tried to) delete all the files pertaining to it. i dont have permission to do so. I tried terminal emulator and it doesnt let me do it.... i type su and it tells me i dont have permission. ive tried flashing zips that claim to disable knox and they dont work.

Cluefree said:
So it sounds like knox is what is killing your attempts. You need to disable it and then reinstall your super user of choice (I like supersu, but I'm sure you can find experts to tell you more about them....). Assuming you have a super user app there, but it is just being squashed, this may work for you...
Go into your explorer of choice (I use explorer es), go into /system/app and find superuser.apk. Select it and force it to install again. When it installs, it will open and tell you that knox is there and ask you if you want to try to disable it. Click ok or yes... I don't recall which, but just get that thing out of there. My guess is at this point, you'll need to actually repeat this process (I did) to get everything "happy"... (repeat the install - but the next time the knox question won't come up).
Click to expand...
Click to collapse
I tried installing superuser.apk using that explorer and it installed. it doesnt ask about knox nor does it mention it... Nothing people suggest seems to help =/

Please... Anyone know what to do?

1998golfer said:
Please... Anyone know what to do?
Click to expand...
Click to collapse
Try going into the Play Store, uninstalling SuperSU and then reinstalling from the Play Store. I think it is also possible to flash an older version of SuperSU and then let the Play Store automatically update it. Just spitballing here.

Mr. Struck said:
Try going into the Play Store, uninstalling SuperSU and then reinstalling from the Play Store. I think it is also possible to flash an older version of SuperSU and then let the Play Store automatically update it. Just spitballing here.
Click to expand...
Click to collapse
Didn't work

1998golfer said:
Didn't work
Click to expand...
Click to collapse
What recovery are you using out of curiosity?
Sent from my SPH-L710 using Tapatalk

Mr. Struck said:
What recovery are you using out of curiosity?
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Cwm - the version for new s3's

1998golfer said:
Cwm - the version for new s3's
Click to expand...
Click to collapse
I would highly recommend switching to Philz Touch recovery, then starting over with flashing the most recent SuperSU zip. Once you boot back into system, open the SuperSU app, choose yes when it asks if you want to disable Knox, and then let it update the binaries for you via the TWRP/CWM option.

This is the repository thanks to @rwilco12, http://rwilco12.com/ in case if the above option doesn't work. Odin down to a rooted jb, then flash a recovery I use Philz Touch (cwm based) and it works flawless, then choose a ROM. Also able to restore cwm or twrp. Be sure to clean install ROMs and always nandroid.

Good luck. I also recommend using philz. Although this process can be frustrating at times, these members @xda are amazing and will get where you need to be. Again, good luck.

Jessooca said:
These guys are definitely leading you in the right path.
From stock on the latest update. I used CF Auto-Root for the Sprint S3 by chainfire in Odin.... uncheck everything.... then after it's flashed take out your battery and boot into recovery and flash the latest supersu zip file then reboot after it reboots open Supersu and it should ask you if you'd like it to disable Knox.
This is what I did it worked for me with no issues
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Nothing has worked. supersu keeps getting:
1) blocked by knox
2) crashing
please link me to what you are talking about (latest supersu, cf auto root, what version of odin.)
when i try to open supersu knox blocks it. how can i open supersu to get knox disabled?
can i reinstall the latest firmware to get rid of anything i may have screwed up?

1998golfer said:
Nothing has worked. supersu keeps getting:
1) blocked by knox
2) crashing
please link me to what you are talking about (latest supersu, cf auto root, what version of odin.)
when i try to open supersu knox blocks it. how can i open supersu to get knox disabled?
can i reinstall the latest firmware to get rid of anything i may have screwed up?
Click to expand...
Click to collapse
Yes, Odin rooted MK3. Use the Knox Removal in this post after Odining a custom recovery-http://forum.xda-developers.com/showthread.php?p=47812894
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What I do,
Download stock rooted deodexed ram from this site, also download knox app remover, also download wifi fix.
Load TWRP 2.6.3.0 Recovery. Flash that using odin.
Reboot to recovery (TWRP)
Having the stock ram on the SD card or the internal storage .. install it than before rebooting install knox app remover and wifi fix and boot..
Make sure than to update the supersu and all should be good.
I hope this helps.

How To Guide TWRP + Root

Hi all. Hope you are good and safe from Covid-19.
If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP as your recovery and if you flash TWRP then you will lose root access. For the advance users, they probably already know how to do this but I haven't seen any guides so I am creating one myself.
Disclaimer:
I am a Textile engineer and do not have the slightest idea about computer engineering but my passion for computers and gadgets has taught me all this.
So, if anything happens to your device, it's not on me. I have done this on my device and it worked, so I am sharing this knowledge with you guys.
Let's cut to the chase and start our work:
Before we start, I am hoping you have your bootloader unlocked and have previous experience on flashing roms.
Step 1: Installing Stock/Xiaomi.EU/Custom rom
Go ahead and install one for your favorite roms from the threads. Luckily, Poco F3 has so many roms to choose from and they're all good.
Step 2: Installing magisk.apk
Install Magisk.apk from here
Step 3: Installing TWRP
Install TWRP from @vasishath's thread. (You'll lose root access if you had any).
Step 4: Backing up your boot image
- Boot into TWRP recovery and select backup.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Tick on boot and untick rest of the boxes.
- This will create 3 files in your TWRP folder on the phone. "boot.emmc.win" is your main file that you want to patch via magisk.
- After creating a backup of your boot image, boot into system normally.
Step 5: Patching the backed up boot image
- Open Magisk app and tap on install next to magisk.
- Now select "Select and Patch a file".
- Go ahead and select the boot.emmc.win file that is in your TWRP folder created earlier via TWRP backup.
- This is patch the boot.emmc.win and name it something like "magisk_patched-23000_randomalphanumeric.img"
- Rename the file via any file explorer to boot.img because something when the phone is plugged into the pc, your pc can't read the file. So, just to be safe, unplug the phone and re-plug to read the drive again.
- Copy this boot.img and take it to the folder where fastboot is installed/saved.
Final Step: Flashing the boot.img
- Reboot your phone to fastboot mode via pressing and holding the volume down + power buttons (or if you have custom roms installed and have the option to boot into fastboot mode directly).
- Once in fastboot mode, type following to flash the boot.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
- once the flashing is done (in about 5-10 seconds), type the following:
fastboot reboot
Click to expand...
Click to collapse
Congratulations! you now have TWRP installed as your recovery and have root access as well. To verify this you should have the below screen in your magisk app
If my guide helped you in any way, please do like it as it motivates me to write more guides to take my time out from my busy work life.
Thanks.

Very detailed and comprehensive guide indeed, however I just unlocked my almost a week now. Initially, I have 3 choices on how I will run my device after unlocking bootloader.
Either I use XiaoMi.EU testing non-root, AOSP non-root or worse can scenario I'll root and run it on stock firmware.
No I do not think that F3 users are lucky, instead I think the reality is the trend of really good coders and programmers have past. You think F3 have a huge variety of custom roms to choose? 90%+ above are based on AOSP, which I don't understand why we have 10+ AOSP roms, with only 1-2 difference. It's such a waste of time. They are only interested in making new custom roms, never in maintaining them. Always abandon project and go missing after a while. This generation is full of "enthusiasts", "wanna-be" developers most noticeable after POCO entered India's market. You can try search in YouTube, poco f3 then you will get 70-80% of tech/mobile influencers with tons of guides. The sad part is, most of them are literally talking about the same stuff, and what I hate the most they love to decorate their website with tons of ads.

Hi,
thanks for your guide I really needed it because I already have custom ROM, root, Magisk... but TWRP I used to start it from the computer every time I needed it.
If I follow your method I don't lose the installed apps and my data, right?

pegasoc said:
Hi,
thanks for your guide I really needed it because I already have custom ROM, root, Magisk... but TWRP I used to start it from the computer every time I needed it.
If I follow your method I don't lose the installed apps and my data, right?
Click to expand...
Click to collapse
No, you won't lose your data.

regedit12345 said:
...
Step 3: Installing TWRP
Install TWRP from @vasishath's thread. (You'll lose root access if you had any).
...
Click to expand...
Click to collapse
Hi,
to be sure I understand correctly, at point 3 where there is to install the TWRP I always started the TWRP from PC I do not have to do it again, right?

pegasoc said:
Hi,
to be sure I understand correctly, at point 3 where there is to install the TWRP I always started the TWRP from PC I do not have to do it again, right?
Click to expand...
Click to collapse
Yeah, once you boot from pc and "install current twrp", you dont have to do it again.

When i have bootloader unlocked how do i flash xiaomi.eu rom without twrp installed?

__halvar__ said:
When i have bootloader unlocked how do i flash xiaomi.eu rom without twrp installed?
Click to expand...
Click to collapse
You have to install TWRP through fastboot, look for a guide, there's a couple

still works like a charm

thank you for the guide!
I already have xiaomi.eu and TWRP installed but my first time installing Magisk on this device.
do I have to wipe /data ?

katcj said:
thank you for the guide!
I already have xiaomi.eu and TWRP installed but my first time installing Magisk on this device.
do I have to wipe /data ?
Click to expand...
Click to collapse
No. Just install magisk.apk and patch the boot image extracted via twrp and go ahead and flash it.

regedit12345 said:
No. Just install magisk.apk and patch the boot image extracted via twrp and go ahead and flash it.
Click to expand...
Click to collapse
PLEASE stop patching the BOOT image
.
.
.
DIRECT INSTALL (Recommendend) is the option on your screen.
that's all you needed.
and your TWRP is OLD
please, use new officel TWRP from
and there you will find the correct instructions for installing TWRP
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com

Thank you for taking your time to contribute value to community resources!
There seem to be so many different guides and methods
I followed nebrassy's guide for TWRP
0. miflash latest stock -> flash desired rom
1. fastboot boot twrp.img (3.6 official)
2. advanced -> flash current twrp (now its permanent)
3. flash latest magisk alpha zip (usb otg or put in storage pre fastboot)
4. reboot.. launch magisk app -> update -> direct install -> reboot
5. profit

Hello. Could you help me with rooting my phone, please?
I'm on Xiaomi.eu 21.12.8 (the last android 12 weekly update). I tried flashing Magisk.zip with the TWRP but it didn't work at all.
It's like I never flashed it. So I decided to try your method to see if it would go any different, and it didn't.
I could root Evolution X (android 12), ArrowOS 11 and 12 with this method of flashing Magisk.zip on TWRP but I can't understand why it didn't worked on Xiaomi.eu 21.12.8. I could even root Xiaomi.eu 21.9.17, which was the last android 11 weekly update.
Desperate, I went to the "advanced" section of TWRP and there was an option of "Flash magisk alpha" and it ended up rooting the phone but I don't understand why the previous 2 methods didn't work.
Could you help me understand that?

Root only works with magisk canary in Android 12
Latest Magisk Canary release adds support for Android 12, drops MagiskHide
The newest update on Magisk's "bleeding edge" canary release channel brings in support for Android 12 and the new Zygisk feature. Read on!
www.xda-developers.com

Thank you!!
Using canary worked on xiaomi.eu, although, I still cannot understand why using the magiskv23.apk can root aosp android 12 rom but not xiaomi.eu android 12, if you could explain me, I'd greatly appreciate it.
Also, canary seems to have the magiskhide function removed, is there a way to hide it for certain apps (banks, mostly) with a module or is it disabled permanently now?

Wiilsoonj said:
Thank you!!
Using canary worked on xiaomi.eu, although, I still cannot understand why using the magiskv23.apk can root aosp android 12 rom but not xiaomi.eu android 12, if you could explain me, I'd greatly appreciate it.
Also, canary seems to have the magiskhide function removed, is there a way to hide it for certain apps (banks, mostly) with a module or is it disabled permanently now?
Click to expand...
Click to collapse
yes the new "hide" is zygisk in the options

How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.

Aceyalone said:
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Click to expand...
Click to collapse
Either use usb OTG.

Aceyalone said:
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Click to expand...
Click to collapse
You can use this TWRP.
Download this: twrp-3.6.0_11-v3.2_A12-alioth-skkk.img
From this link: https://androidfilehost.com/?w=files&flid=322193
This one is able to see the internal storage of the phone with android 12. But you need to remove your screen lock to do so, you must not have a password set up so TWRP can see your internal storage, then just flash magisk normally and afterwards set up your screen lock again. Everytime you want to see the internal storage, disable screen lock. Also, you could follow the tutorial in the first post, but instead of making a backup of boot with TWRP, just use boot.image from the desired ROM, patch it with magisk and then flash the boot using adb.
Hope it helps.

TUTORIAL- How To- Downgrade To Lolipop 5.1.1, Galaxy S6 edge+ [UPDATED GUIDE]

- WARNING -
This Guide is not failproof, if you do anything wrong with your device while following this guide, i won't be held responsible if you brick or hard damage your device. I insist about that but you must extract all of your data (Photos, Videos, Music, Apps, Accounts, Messages, ETC) Before proceeding or else you will end up with a loss of data, again i'm still not responsible if you lose all of your data without backing up. I WARNED YOU.
Well, you have a Galaxy S6 edge+ lying around and you want to get back to Lolipop? You want to downgrade? Well then you're in the right place!
So......downgrading to lolipop...... some people claimed it can be done by deleting some file in the odin .tar but that never worked for me.
If you have the sw rev check fail error upon downgrading....this is the guide for you!
This will wipe all your data including internal storage (depending on how you do it)
Confirmed working on my Galaxy S6 edge+ SM-G928F [It should work on Note5 but no promises from now on]
Advantages :
Downgrade procedure is safe, simple.
Your phone should boot faster
battery life should last longer [i said it should]
You can get the animated lock screen animations back.
Get old touchwiz back. [i like the 5.1.1 version]
disadvantages:
1. You cannot boot TWRP while on the downgraded bootloader
2. You will only have system-wide root. DO NOT flash systemless or it will not boot (but nobody cares)
3. Fingerprint is not working (still working on that)
4. You can only flash stock nougat from odin. You cannot flash lolipop, marshmallow tar,twrp tar,cf auto root tar or anything else [except if you have a combination firmware]
Ok, let's get started.
Requirements :
A laptop or home PC : At least running Windows 8/8.1 or Windows 10
Your device
Genuine Samsung charging cable [NOT SPONSERED]
Stable internet connection.
Files :
The lastest SAMSUNG Drivers which can be found here : https://developer.samsung.com/android-usb-driver
Odin3 : https://www.samsungodindownload.com/fr/download-for-windows
The firmware you want to downgrade to : I will link my ROM so u can install it.
TWRP [Newest version] : https://twrp.me/samsung/samsunggalaxys6edgeplus.html
Classy Kitchen [for bulding your rom] : https://forum.xda-developers.com/t/...kitchen-for-android-roms-development.3862584/
Now let's get started!
Let's start first by cooking the ROM! Open Classy Kitchen, and then open the ROM you want to use :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Normally the first time you open the program, there shouldn't be any project [except if you used this app before]
Next click "Create new project", "From PC (Browse for one)"
And then chose the path where you saved your firmware. After chosing your firmware, Classy Kitchen will open the firmware automaticly.
After the ROM is now open, click on "ROM utils" and then click on "Deodex ROM" After you Deodex the ROM, we will have to de-bloat it.
On Classy Kitchen, click on "Debloat / Re-Bloat ROM" to Debloat your ROM.
Last step [optional] We will have to De-Knox our ROM. (again optional) But De-Knoxing our ROM can save a lot of space in our phone storage. So i recommend you do.
After De-Knoxing our ROM, we will have to disable DM-Verity Force Encryption in order to Boot into the ROM [Otherwise if you don't your phone will never boot]
Click on "Remove DM-Verity / Force Encryption"
Next that we disabled DM-Verity, We will have to remove the "meta-inf installer"
Click on "Re-Build META-INF installer" and click on remove.
Finally once we have done the modifications on our ROM, we just have to save.
Click on "Build (system.new.dat) ROM (for recovery)"
and then we are done cooking our ROM!
But the guide is not done yet. We will have to install TWRP in the phone.
HOW-TO-PROCEED?
Step-1 Press and hold the power button on your device
Step-2 Chose "Power Off"
Wait for your device to completly Shut-Off.
Step-3 Re-Boot in download mode "odin mode"
Step-4 connect the phone to your computer
Step-5 open Odin3
In Odin, we will have to install TWRP, click on the AP box and chose your TWRP file [the one that you downloaded]
Don't forget to disable "Auto-Reboot" after installation, otherwise your phone will re-boot normal into Android.
At this point, Knox is tripped in your device meaning that your warranty is now expired. Also the Knox features are no longer usable.
On TWRP, click on wipe, "Format Data". A keyboard will pop-up, type "yes"
Type "yes"
Once Data Format is completed, hit home, reboot, recovery.
your phone will reboot into recovery again, hit wipe again, this time we won't format data. Instead we're going to wipe the phone's partitions
Chose in TWRP,
Then swipe to wipe. Then hit home again. Next hit "Install"
Install the ROM you just made with Classy Kitchen. It can be found in "Documents" - "Output" - "Your-ROM"
Transfert it to your phone
Click on the ROM / ZIP file and "swipe to confirm flash"
After the flashing procedure is complete, you will have to wipe the "cache" / Dalvik.
Hit "wipe dalvik/cache"
Then "swipe to wipe"
After you wiped the cache, hit "Reboot System" and hit "Do Not Install"
One last step before you get back to Lolipop. You will need a custom Bootloader in order to boot.
Just download my "custom Bootloader" https://drive.google.com/file/d/1207Guvk8J_L9FSJv2C9BpkeLpWkXtViQ/view?usp=drive_link
After you downloaded my "custom bootloader" you will have to install it.
so get Odin3 and install my bootloader!
After the Bootloader installation is complete, you just have to reboot your device, cross your fingers and hope it boots!
Congratuations! You are back on Lolipop! Enjoy!
1 : If you want to flash a mod in TWRP, you will have to put your phone in download mode, install the stock bootloader in BL tab, install TWRP in AP tab and then click on "start"
2 : If you want to get back into marshmallow / Nougat, you just have to flash stock firmware in Odin3
If you have any issues or any questions, you can DM me but it isn't guaranteed that i will reply.

Here are some screenshots of Lolipop :

Here the device i used.

what about system sound because on 6.1.1 (sorry 6.0.1) sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader

iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Nevermind. This comment is deleted

iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Actually
iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Try download downloading my bootloader again. I made it public

TheWiiGuy said:
Actually
Try download downloading my bootloader again. I made it public
Click to expand...
Click to collapse
Why sound coming like creepy from buzzer only on 6.1.1 interesting..

iskender4444 said:
Why sound coming like creepy from buzzer only on 6.1.1 interesting..
Click to expand...
Click to collapse
Have you downgraded to Lollipop yet?

TheWiiGuy said:
Have you downgraded to Lollipop yet?
Click to expand...
Click to collapse
i had bootloop on samsung galaxy s6 edge plus here the photo:

and can you share the twrp? and is this correct one?
"twrp-3.1.1-0-zenlte.img"

iskender4444 said:
and can you share the twrp? and is this correct one?
"twrp-3.1.1-0-zenlte.img"
Click to expand...
Click to collapse
Yes. This is The Good TWRP. Are you trying to get into recovery? If not then there is a problem with my bootloader
Mind if i upload the New bootloader tomorrow?

iskender4444 said:
i had bootloop on samsung galaxy s6 edge plus here the photo:
Click to expand...
Click to collapse
It looks like the phone is trying to get into stock recovery.

TheWiiGuy said:
It looks like the phone is trying to get into stock recovery.
Click to expand...
Click to collapse
idk and i dont get it why doing this i just re-download twrp official website and still same issue i just flash the twrp but can't enter twrp recovery right know.

iskender4444 said:
idk and i dont get it why doing this i just re-download twrp official website and still same issue i just flash the twrp but can't enter twrp recovery right know.
Click to expand...
Click to collapse
Actually i forgot to mention that you can't boot into TWRP on My custom bootloader. Get back in odin. Re-flash stock bootloader in BL Tab and flash TWRP in the AP Tab. Then try to re-boot onto Custom recovery. Tell me some news.

TheWiiGuy said:
Actually i forgot to mention that you can't boot into TWRP on My custom bootloader. Get back in odin. Re-flash stock bootloader in BL Tab and flash TWRP in the AP Tab. Then try to re-boot onto Custom recovery. Tell me some news.
Click to expand...
Click to collapse
Oh yes. Have you backed up all of your partitions on TWRP?

TheWiiGuy said:
Oh yes. Have you backed up all of your partitions on TWRP?
Click to expand...
Click to collapse
i solved twrp but can't boot same as issue on picture

iskender4444 said:
i solved twrp but can't boot same as issue on picture
Click to expand...
Click to collapse
So you can boot onto TWRP ?
OK. I see the problem.
I Will upload my New bootloader tomorrow.
The current bootloader does not allow to Boot onto TWRP and it can't boot into stock recovery either.
Hopefully the New bootloader should fix your problem. It has stock recovery

TheWiiGuy said:
So you can boot onto TWRP ?
OK. I see the problem.
I Will upload my New bootloader tomorrow.
The current bootloader does not allow to Boot onto TWRP and it can't boot into stock recovery either.
Hopefully the New bootloader should fix your problem. It has stock recovery
Click to expand...
Click to collapse
i have another problem i was trying to flash stock 7.0 rom but gives error same like this.

iskender4444 said:
i have another problem i was trying to flash stock 7.0 rom but gives error same like this.
Click to expand...
Click to collapse
Nevermind this comment is deleted

TheWiiGuy said:
What is your phone model number? I see you are installing firmware for a sm-g780f.
Click to expand...
Click to collapse
no this is for example man mine was g928c

How To Guide OxygenOS 13.1 (LE2125_13.1.0.500) for global with boot.img files

Hi,
I share with you the files for those who want to update from F21 to Android 13.1 and root the phone.
LE2125 OxygenOS 13.1.0.500
For those who get the message that the backup does not exist when uninstalling magisk by selecting image restore, you will not be able to install the update by uninstalling magisk completely , it will fail.
Here's how to do.
-uninstall magisk by selecting uninstall completely
- once the phone restarts, restart in fastboot mode
- flash the original F21 version boot image (9Pro_F21_Global ) by typing these two command lines
fastboot flash boot_a original_F.21_boot.img
fastboot flash boot_b original_F.21_boot.img
- restart the phone
-now you can install the update (you will need this apk to install the update OPLocalUpdate_For_Android13.apk)
- once the update is installed, you can root the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks for share

this update available for op9? if yes then can you provide me link of this latest ota?

Daniha said:
this update available for op9? if yes then can you provide me link of this latest ota?
Click to expand...
Click to collapse
NO, for op9 pro...don't use them for op9.

buu'buu said:
NO, for op9 pro...don't use them for op9.
Click to expand...
Click to collapse
no no I'm asking for this ota rom for op9?

@Daniha
Sorry, I don't have the op9, you have to wait OnePlus or Oxygen Updater provide it.

buu'buu said:
Hi,
I share with you the files for those who want to update from F21 to Android 13.1 and root the phone.
LE2125 OxygenOS 13.1.0.500
For those who get the message that the backup does not exist when uninstalling magisk by selecting image restore, you will not be able to install the update by uninstalling magisk completely , it will fail.
Here's how to do.
-uninstall magisk by selecting uninstall completely
- once the phone restarts, restart in fastboot mode
- flash the original F21 version boot image (9Pro_F21_Global ) by typing these two command lines
fastboot flash boot_a original_F.21_boot.img
fastboot flash boot_b original_F.21_boot.img
- restart the phone
-now you can install the update (you will need this apk to install the update OPLocalUpdate_For_Android13.apk)
- once the update is installed, you can root the phone.
View attachment 5914697
View attachment 5914699
View attachment 5914703
Click to expand...
Click to collapse
Thanks for the info... unfortunately I don't have a computer but, what I do is install F21 stock boot image using Ex Kernel manager and after doing that it allows me to install the update. It's doing the same thing that flashing thru fastboot does except I'm just flashing the stock boot image with a kernel flasher...

TENlll423 said:
Thanks for the info... unfortunately I don't have a computer but, what I do is install F21 stock boot image using Ex Kernel manager and after doing that it allows me to install the update. It's doing the same thing that flashing thru fastboot does except I'm just flashing the stock boot image with a kernel flasher...
Click to expand...
Click to collapse
Thanks, i'll test that at next update.

It keeps displaying: System update installation failed at 0% progress. I have removed magisk completely

Pourek said:
It keeps displaying: System update installation failed at 0% progress. I have removed magisk completely
Click to expand...
Click to collapse
Are you using the System update application? (system update apk.for Android 12)
If not use that...
Also, if you have TWRP installed that will keep the update from working correctly you'll have to install the stock boot image in a kernel manager like EKM. Besides that I'm not sure what else would cause that.. I just updated no problem it took like 2 minutes I didn't even have to flash my stock boot image this time. I thought I would have to after reading
Buu buu's post earlier.

TENlll423 said:
Are you using the System update application? (system update apk.for Android 12)
If not use that...
Also, if you have TWRP installed that will keep the update from working correctly you'll have to install the stock boot image in a kernel manager like EKM. Besides that I'm not sure what else would cause that.. I just updated no problem it took like 2 minutes I didn't even have to flash my stock boot image this time. I thought I would have to after reading
Buu buu's post earlier.
Click to expand...
Click to collapse
I am, i'm probably just going to factory reset and apply the update

Can we assume that updating to this, if rooted, can take the usual route?
1. Restore images in magisk
2. Download update in oxygen updater.
3. Install the update using that other update tool, not the system one.
4. Install magisk to inactive stlot
5. And only then reboot?

nabril15 said:
Can we assume that updating to this, if rooted, can take the usual route?
1. Restore images in magisk
2. Download update in oxygen updater.
3. Install the update using that other update tool, not the system one.
4. Install magisk to inactive stlot
5. And only then reboot?
Click to expand...
Click to collapse
Yeah and I guess you can skip "Restore images" part.
At least I did that every time i updated OSS before I went to a custom rom.

Smedslund said:
Yeah and I guess you can skip "Restore images" part.
At least I did that every time i updated OSS before I went to a custom rom.
Click to expand...
Click to collapse
I was asking about those of us on OOS.

nabril15 said:
I was asking about those of us on OOS.
Click to expand...
Click to collapse
I was on OSS until 2 weeks ago. But nvm.

Did you buy a 2125 model in Europe or are you from Canada?

Thank you for sharing this! How can I use this without root. Thank you

naxos said:
Thank you for sharing this! How can I use this without root. Thank you
Click to expand...
Click to collapse
Can you tell me what exactly you want to do. Version installed? Root?

buu'buu said:
Can you tell me what exactly you want to do. Version installed? Root?
Click to expand...
Click to collapse
Thank you for your time to answer me, I want to install just the new version. My firmware version is LE2123_11.F.75_2750_202303081536
Thanks