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.

[RECOVERY][unofficial][anthias / zenwatch] TWRP 3.0.2

TWRP recovery 3.0 zenwatch
How to install ​Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!​
update
Twrp 3.0.2 For android wear 1.4
NOT INSTALL ON ANDROID WEAR 1.3 !
Download twrp 3.0.2
installation
Code:
fastboot flash recovery twrp-3.0.2_anthias.img
Photos
{
"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"
}
Stock Recovery for Android Wear 1.4
installation stock recovery
Download stock recovery
Code:
fastboot flash recovery recovery_MEC23S.img
OLD VERSION FOR ANDROID WEAR 1.5 / TWRP 3.0 /TWRP 3.0.1
Download twrp 3.0.1-0 Zenwtach AW 1.4
Download twrp 3.0
OLD VERSION FOR ANDROID WEAR 1.3 / TWRP 2.8.7.0
old version (for android wear 1.3) download twrp mega.nz
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
source https://github.com/asyan4ik/asus_anthias/tree/master

acbka said:
Twrp recovery 2.8.7.0 zenwatch
How to install ​
Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!
download twrp basketbuild.com
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
Click to expand...
Click to collapse
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!

btonetbone said:
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!
Click to expand...
Click to collapse
Same. Thanks.

Ups , i fix this today ...
Sorry

hecksagon said:
Same. Thanks.
Click to expand...
Click to collapse
reload to mega . sorry

Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.

CSX321 said:
Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.
Click to expand...
Click to collapse
Yes, I pulled a system image and another user modified to successfully pass the checks that occur during updates (the original pull didn't pass). Check out this thread: http://forum.xda-developers.com/zenwatch/development/root-t3163248
Makes sure you read up on it, though, as it sounds like you'd need to do some legwork to get the system image to work. Relevant posts in that thread are 32, 52, and 54.
Hopefully, though, having TWRP means that someone smarter-than-I-am may develop even more elegant solutions!
Cheers!

Now that we have twrp we can do a system pull from an unrooted device. The system image posted in the other thread will only work on the previous version of Android Wear. Do not flash if you are up to date.

Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.

itechnoguy said:
Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.
Click to expand...
Click to collapse
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.

hecksagon said:
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.
Click to expand...
Click to collapse
Make sure you're using this zip file to install SuperSU (it seems to be the same binary as Chainfire's) since the app itself doesn't work, and this one doesn't require authorizations (not completely safe, but it works).
(also, don't forget to unroot from the KingRoot app first; the unroot seems to be clean enough to use Wear SuperSU)

itechnoguy said:
Make sure you're using this zip file to install SuperSU
Click to expand...
Click to collapse
That's the one I used, and it works. (Though there's no authorization popups, as you said.)

Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..

Talysdaddy said:
Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..
Click to expand...
Click to collapse
It'll probably remove KingRoot successfully, but the Zenwatch can't launch the SuperSU app, so root authorization dialogs never show up (the su binary still gets installed, but it can't do anything without permission from the app first).

Boooooo moto 360. It's sooo damn big.

@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).

itechnoguy said:
@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).
Click to expand...
Click to collapse
hi . i update first message .
add my github

Message for all you zenwatch 2 people.. Don't try to flash this recovery. You will have a soft brick. And with no resources at this time. There is no fix.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2

Has anyone pulled the stock system partition? I, stupidly, didn't do it before I installed SuperSU. I'd like to be able to go back to stock, if there's another firmware update.

I need a link to the stock recovery.IMG file

Question installation failed w/ magisk active (pixel 6 pro, magisk v24.3)

I'm always getting this error while i trying to download & install updates via the pixel updater.
It always returns "Installation failed"
Im currently downloading the ota & sideloading it and reflashing the latest stock boot to re root.
Is there any fix to just use magisk ota patcher instead of the workaround im using?
{
"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"
}

Venipa said:
I'm always getting this error while i trying to download & install updates via the pixel updater.
It always returns "Installation failed"
Im currently downloading the ota & sideloading it and reflashing the latest stock boot to re root.
Is there any fix to just use magisk ota patcher instead of the workaround im using?
Click to expand...
Click to collapse
You pretty much have to be completely stock to use the "Install to Inactive Slot" method (except being rooted with Magisk of course). That means no modifications of /system, /vendor, etc.. Having a custom kernel will also make it fail because dtbo, vendor_boot & vendor_dklm images are usually modified with custom kernels on the Pixel 6 series. Any modifications like these will make the pre-OTA verification check fail and thus the installation fail.
Also, if you are using Canary versions 24304/5, it's been reported that these versions aren't playing well with the "Install to Inactive Slot" method for the March and April builds.

Lughnasadh said:
You pretty much have to be completely stock to use the "Install to Inactive Slot" method (except being rooted with Magisk of course). That means no modifications of /system, /vendor, etc.. Having a custom kernel will also make it fail because dtbo, vendor_boot & vendor_dklm images are usually modified with custom kernels on the Pixel 6 series. Any modifications like these will make the pre-OTA verification check fail and thus the installation fail.
Also, if you are using Canary versions 24304/5, it's been reported that these versions aren't playing well with the "Install to Inactive Slot" method for the March and April builds.
Click to expand...
Click to collapse
im on stock + magisk 24300, it still showed the (ota) install failed error
edit: could it be that the "Universal SafetyNet Fix" module could alter system or smth related to the pre-ota verification process?

Venipa said:
im on stock + magisk 24300, it still showed the (ota) install failed error
Click to expand...
Click to collapse
Not really sure then. Since that method was re-added to Magisk (in January I believe), it seems to be hit or miss for a lot of folks.

Venipa said:
edit: could it be that the "Universal SafetyNet Fix" module could alter system or smth related to the pre-ota verification process?
Click to expand...
Click to collapse
Anything is possible. Try all Magisk Modules disabled, then reboot, and then try it again.

roirraW edor ehT said:
Anything is possible. Try all Magisk Modules disabled, then reboot, and then try it again.
Click to expand...
Click to collapse
I'll try that on the next update

roirraW edor ehT said:
Anything is possible. Try all Magisk Modules disabled, then reboot, and then try it again.
Click to expand...
Click to collapse
new update dropped and yet the issue persists, i've disabled magisk modules and it still happened
i guess its time to manually flash the update again :sigh:

Venipa said:
new update dropped and yet the issue persists, i've disabled magisk modules and it still happened
i guess its time to manually flash the update again :sigh:
Click to expand...
Click to collapse
If I were in your shoes, I would first try updating using the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own), and choose the option to not wipe (and don't flash all partitions, and don't relock the bootloader). And then try rooting using Magisk Stable v24.3. The Android Flash Tool has fixed many folks' problems, even when manually flashing the full firmware zip didn't fix the problem.
Good luck!

roirraW edor ehT said:
If I were in your shoes, I would first try updating using the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own), and choose the option to not wipe (and don't flash all partitions, and don't relock the bootloader). And then try rooting using Magisk Stable v24.3. The Android Flash Tool has fixed many folks' problems, even when manually flashing the full firmware zip didn't fix the problem.
Good luck!
Click to expand...
Click to collapse
Ah that's not what I meant, I've already everything setup to manually patch the ota without wiping my data. It's just inconvenient to do the ota and downloading the stock firmware to patch only the boot again for magisk.

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