☆★☆ [ROM|RADIO|FIRMWARE][6.0] Stock-Rooted Marshmallow | Sense 7 | m8vzw | 07-03-16
6.21.605.3
-Stock Rooted-
Android 6.0 Marshmallow
{
"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"
}
Firmware files moved to Post #2
ROMS:
Stock Rom Revamped/Final
6.21.605.3_M8_WL_M60_SENSE70_VZW_MR_AROMA-FINAL.zip
I've included a few Aroma options for your choosing:
- Stock System.img and Boot.img without root
- Stock System.img and Boot.img with Chainfire SuperSu root
- Stock System.img and Boot.img with Magisk + Phh Superuser root installed and enabled (will pass SafetyNet w/magisk Hide enabled)
- Encrypted/Decrypted - Choose whether to use Encryption or not
- Debloat - Removes excessive carrier bloat from Vzw and Amazon
- User App Removal - Allows you to choose which Google/Market apps you don't want installed
- Tether Unlock - Enables wireless tethering regardless of your Vzw account type
OLDER FULL STOCK VERSIONS:
Pure Stock Rooted
6.21.605.3_M8_WL_M60_SENSE70_VZW_MR_Full
Pure Stock Rooted
4.17.605.9_M8_WL_L50_SENSE60_MR_Full
Pure Stock
Rooted with Systemless SuperSu v2.67
BusyBox
Nothing else added or removed
___________________
OLDER DEBLOATED STOCK VERSIONS:
Stock Rooted and Debloated
NuSense_of_Stock_M8vzw_6.21.605.3_Debloated
NuSense of Stock Wifi Tether Patch: LINK
4.17.605.9_M8_WL_L50_SENSE60_MR_Debloated
Debloated of Vzw/and downloadable junk (35 apps in all + tutorial vids)
Rooted with SuperSu
BusyBox
System R/W (insecure kernel)
Updated ALL Market Apps in System incl: Sense Home w/themes
Stock m8 boot animation/splash (non-vzw)
Wifi Tether - enabled for all users
10 Unlock Fail device wipe - disabled
Full stagefright patch integrated (fixes remaining vulnerability left from stock OTA)
Replaced Sense 6 wallpapers with ones from Sense 7
Probably a few other minor enhancements...to improve the stock experience
XDA:DevDB Information
★ ☆ Stock-Rooted Marshmallow | Sense 7 | m8vzw ☆ ★, ROM for the Verizon HTC One (M8)
Contributors
santod040
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 6.21.605.3
Based On: Sense 7.0
Version Information
Status: Stable
Created 2015-09-09
Last Updated 2017-04-30
Firmware
FIRMWARE:
MARSHMALLOW:
Combined Marshmallow Firmware Zip
If coming from a previous Android version, you can use the following zip to get caught up on all previous firmwares in one shot.
This zip contains all firmware files from the first OTA through the latest, with the newest files replacing the older ones, while keeping the ones that did not get replaced in newer firmwares.
This will give you all needed firmware files for the current Marshmallow release, no matter what you had previously.
m8vzw_AllInOne_Firmware_6.21.605.3 (will NOT wipe the device)
Otherwise, you can just flash the incremental firmware update posted below:
6.21.605.3_NoBoot-TWRP3.0.0-1_firmware.zip
6.21.605.3_NoBoot-NoRecovery_firmware.zip
6.21.605.3_FULL_firmware.zip
LOLLIPOP:
Combined Lollipop Firmware Zip
If coming from a previous Android version, you can use the following zip to get caught up on all previous firmwares in one shot.
This zip contains all firmware files from the first OTA through the last, with the newest files replacing the older ones, while keeping the ones that did not get replaced in newer firmwares.
This will give you all needed firmware files for the last Lollipop release, no matter what you had previously.
m8vzw_AllInOne_Firmware_4.17.605.9 (will NOT wipe the device)
Otherwise, you can just flash the incremental firmware update posted below:
4.17.605.9 Modified Firmware - Removed stock boot.img and stock recovery and WILL NOT WIPE device
(suitable firmware update for most cases, especially if running custom rom and recovery)
4.17.605.9 Full Firmware - Includes stock boot.img and recovery and WILL WIPE device
No Red Text and Faux Locked Hboots - my m8 hboot thread
4.17.605.9 Stock Recovery
4.17.605.9 Stock Boot.img/Kernel
How to manually flash firmware zips:
(sd card method also works, but I recommend fastboot)
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip to make it simple/optional)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
Click to expand...
Click to collapse
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and will be running the latest firmware and radios.
If you have any questions or issues, let me know.
OTAPkg
For those that want to apply the OTA manually:
Old files:
LOLLIPOP:
4.17.605.9_OTAPkg.zip:
To be applied on stock device with stock recovery only
LOLLIPOP:
Stagefright Patch:
Recovery Flashable Patch
Fixes the one remaining vulnerability that the OTA didn't patch.
__________
Thanks, santod040! Nice to see you around in these parts again!
Awesome! But, what is it? Latest firmware appears to be 4.17.605.5. First guess was Stagefright fix, but that would be done in ROM, not firmware. Did our phone get an OTA today?
dragontology said:
Awesome! But, what is it? Latest firmware appears to be 4.17.605.5. First guess was Stagefright fix, but that would be done in ROM, not firmware. Did our phone get an OTA today?
Click to expand...
Click to collapse
Yeah our phone received a update today
Sent from my HTC6525LVW using Tapatalk
dragontology said:
Awesome! But, what is it? Latest firmware appears to be 4.17.605.5. First guess was Stagefright fix, but that would be done in ROM, not firmware. Did our phone get an OTA today?
Click to expand...
Click to collapse
Yes, there was an OTA to .9 with the stagefright patch/security update.
I'll be posting a full stock rooted rom in a bit...
Awesome thanks santod. Can't wait to get your latest nusense seven. And with this I'll be ready to flash..
Sent from my HTC6525LVW using XDA Free mobile app
I tried the non-wipe fastboot method. It updates through the console correctly, the software version shows the .9 in the boot loader, but when I go to settings and check the version, it still shows the .5 and I get the upgrade nag screen.
Edit: I think I fixed it, I had to go into recovery and wipe my cache and dalvik cache.
Edit2: Nvm, I thought it was fixed because I saw the updating apps window, but it's still .5 in Settings
liquidrezin said:
I tried the non-wipe fastboot method. It updates through the console correctly, the software version shows the .9 in the boot loader, but when I go to settings and check the version, it still shows the .5 and I get the upgrade nag screen.
Edit: I think I fixed it, I had to go into recovery and wipe my cache and dalvik cache.
Click to expand...
Click to collapse
Your updated firmware will show in fastboot mode only.
You will need to update/flash a rom based on the new OTA for Settings/Software info to change.
That is merely showing what rom base/software you are running, not firmware.
They are not one in the same thing.
Full rooted stock rom should be uploading shortly...
santod040 said:
Your updated firmware will show in fastboot mode only.
You will need to update/flash a rom based on the new OTA for Settings/Software info to change.
That is merely showing what rom base/software you are running, not firmware.
They are not one in the same thing.
Full rooted stock rom should be uploading shortly...
Click to expand...
Click to collapse
Ok, thanks for the clarification.
OP Updated
Full Stock Rooted is now live in the OP: - 4.17.605.9_M8_WL_L50_SENSE60_MR_Full
Debloated: - should be up before I have to head off to work. (3 hours until then...)
Debloated version is up!
Stock Rooted and Debloated is now live in the OP
4.17.605.9_M8_WL_L50_SENSE60_MR_Debloated
Debloated of Vzw/and downloadable junk (35 apps in all + tutorial vids)
Rooted with SuperSu
BusyBox
System R/W (insecure kernel)
Stock m8 boot animation/splash (non-vzw)
Updated ALL Market Apps in System incl: Sense Home w/themes
Wifi Tether - enabled for all users
10 Unlock Fail device wipe - disabled
Full stagefright patch integrated (fixes remaining vulnerability left from stock OTA)
Replaced Sense 6 wallpapers with ones from Sense 7
Probably a few other minor enhancements...to improve the stock experience
Hey Santo! Is the OTA that you posted the same one I posted or have you rooted that so we can just install that instead of the full version?
jrg67 said:
Hey Santo! Is the OTA that you posted the same one I posted or have you rooted that so we can just install that instead of the full version?
Click to expand...
Click to collapse
I posted the OTAPkg.zip that I downloaded from Vzw in it's stock patch form, for users that want to apply it manually with stock recovery.
That is in the third post.
I also made a complete full stock rooted rom from it, after applying it to the previous RUU/software version.
That is in the OP, and not only did I post the full stock rooted flashable rom, but I also posted a debloated version of the rom as well, with a few small goodies added.
The links in the OP are full Twrp flashable stock roms.
The files in the second post are firmware from the OTA.
The files in the 3rd post are the OTAPkg.zip which should only be applied if you have the previous stock rom running and stock recovery.
In other words, I posted full rooted Twrp flashable roms and fastboot flashable firmware, so that everyone doesn't have to worry about completely wiping their devices to take an OTA or getting stuck in the process.
Also, in the 3rd post, I posted a stagefright patch, to fix the remaining stagefright vulnerability that HTC/Vzw still left us with, after this OTA. (included in the debloated rom I posted as well)
santod040 said:
I posted the OTAPkg.zip that I downloaded from Vzw in it's stock patch form, for users that want to apply it manually with stock recovery.
That is in the third post.
I also made a complete full stock rooted rom from it, after applying it to the previous RUU/software version.
That is in the OP, and not only did I post the full stock rooted flashable rom, but I also posted a debloated version of the rom as well, with a few small goodies added.
The links in the OP are full Twrp flashable stock roms.
The files in the second post are firmware from the OTA.
The files in the 3rd post are the OTAPkg.zip which should only be applied if you have the previous stock rom running and stock recovery.
In other words, I posted full rooted Twrp flashable roms and fastboot flashable firmware, so that everyone doesn't have to worry about completely wiping their devices to take an OTA or getting stuck in the process.
Also, in the 3rd post, I posted a stagefright patch, to fix the remaining stagefright vulnerability that HTC/Vzw still left us with, after this OTA. (included in the debloated rom I posted as well)
Click to expand...
Click to collapse
Thank you again for all your hard work! Just a fast question about the firmware, can it be loaded via hboot by changing the file name to the 0P6..etc or can it only be loaded via fastboot/pc?
jrg67 said:
Thank you again for all your hard work! Just a fast question about the firmware, can it be loaded via hboot by changing the file name to the 0P6..etc or can it only be loaded via fastboot/pc?
Click to expand...
Click to collapse
No problem. You're quite welcome.
I believe I mentioned in the firmware post, that sd card method works as well. [emoji5]
Sent from my HTC6525LVW using Tapatalk
I must have missed that, you did say sd method works.. That's what I get for skimming quickly for the links and not reading the entire post!
Thanks again sir. Updated firmware and removed red text using SD card method. Worked fine, but just to be safe I ran the hboot install twice for the firmware.
Sent from my HTC6525LVW using Tapatalk
...so the ROM kernel isn't 3.10.X right? Seems to be 3.4.0 from the screenshot
Related
{
"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"
}
4.3 Stock Firmware for Australian S34G (I9305T) users
WARNING !! DO NOT USE THIS ON ANY OTHER I9305 DEVICE, IT MAY CAUSE PROBLEMS !!
INFORMATION
The official 4.3 Firmware has now been released for the Australian S34G (I9305T).
Here's a safe way to update your phone and not be forced to install the KNOX (4.3) Bootloader.
The whole ROM has been taken apart so you can easily choose what you want to flash.
REQUIREMENTS
- Samsung S34G I9305T
- About 840mb - 1.5gb on your SDCard to copy the files
- Custom Recovery (CWM, Philz, TWRP, Mobile ODIN)
INSTALLATION INSTRUCTIONS
- Copy required zip files to your internal SD Card
- Reboot into recovery
- Perform a full wipe (Optional, but recommended)
- Install ROM
- Reboot and enjoy
If you wish to use addional files, the best order to flash them is this:
Kernel - Recovery - CSC - Odex - KNOX (make sure you used the Odexed KNOX version if you are using the Odex patch)
DOWNLOADS - DVUENC1
Main ROM: DOWNLOAD HERE - MD5: CC0EE566F8BA28FCEC909785898B3D48
- Boeffla 5.3 Beta 3 Custom Kernel *FIXED* (Built 2014-05-20)
- Deodexed, Zipaligned, SU, BusyBox, init.d
- No apps have been removed (except for KNOX protection)
- Extra CSC apps from TEL and XSA added
Odex Patch: DOWNLOAD HERE - MD5: 319A753F4FA8662A2201719BC2660008
- Turns the ROM into an Odexed ROM (like it originally comes stock)
KNOX: DOWNLOAD HERE - MD5: 0232AD5E46E2D812FE25DA851778D4B8
KNOX (Odexed): DOWNLOAD HERE - MD5: 913B85F228BF449A3B9668976ACB64F3
- Use this if you are one of the unfortunate ones with the 4.3 Bootloader
Stock Kernel: DOWNLOAD HERE - MD5: DE1EBF4A99FE6E763F3613B6EF191FA8
DOWNLOADS - DVUEMK4
Main ROM: DOWNLOAD HERE - MD5: 94FC96B7F9136049B3C245971CF3C431
- Boeffla 5.2 Custom Kernel (Built 2014-04-24)
- Deodexed, Zipaligned, SU, BusyBox, init.d
- No apps have been removed (except for KNOX protection)
- Extra CSC apps from TEL and XSA added
Odex Patch: DOWNLOAD HERE - MD5: 017AB49D9144D5581DBD7A55918EB0FB
- Turns the ROM into an Odexed ROM (like it originally comes stock)
KNOX: DOWNLOAD HERE - MD5: 4646030A29E68C8DF1163BC85099D581
KNOX (Odexed): DOWNLOAD HERE - MD5: D9FE90293427C774B5365D82CE9320D9
- Use this if you are one of the unfortunate ones with the 4.3 Bootloader
Stock Kernel: DOWNLOAD HERE - MD5: EA9AAEA3D20F6DD8A59E20A36742942D
DOWNLOADS - OTHER
SDCard Files: DOWNLOAD HERE - MD5: 8B67AFAC39C5D8A223B245898E1CDAC8
- Unpacked hidden.img installed to your SD Card
- Includes data for Navagon plus some sample music and video
Stock Recovery: DOWNLOAD HERE - MD5: 794C3C42C455E9D5C9AB63628A138028
- Just in case anyone needs them
CSC (TEL): DOWNLOAD HERE - MD5: 9C337956C923A9C614327449731278BC
CSC (XSA): DOWNLOAD HERE - MD5: 2D2C9A5DEE10B7F80F10E9C33681ED37
- The specific Australian CSCs. TEL is for Telstra CSC, and XSA is for the generic Australian CSC.
- With some recoveries, you may have to manually mount the /system partition as these original CSC files don't seem to do that automatically
Modem (DVUEML1): DOWNLOAD HERE - MD5: E6B263802912EF2B43759B31D336FED2
Modem (DVUEMK2): DOWNLOAD HERE - MD5: 561DFD09A7011566B63E406354526C8E
Modem (DVUENC1): DOWNLOAD HERE - MD5: DB088658B5025D679721EA66FB42E690
- DVUEML1 and DVUENC1 came with the TEL Firmware, and DVUEMK2 came with the XSA Firmware.
Reserved...
Cheers man!:good::laugh:
Added the OPS CSC
djb77 said:
[
ORIGINAL ODIN FILES
These should only be used for development purposes, or if you have already installed a previous 4.3 Firmware on your phone via ODIN
I9305TDVUEMK4-TEL - DOWNLOAD HERE
I9305TDVUEMK4-XSA - DOWNLOAD HERE
Click to expand...
Click to collapse
what's the difference with the 2 odin files?
Thanks heaps by the way
billyhoyle said:
what's the difference with the 2 odin files?
Thanks heaps by the way
Click to expand...
Click to collapse
Different CSC's in them.
djb77 said:
Different CSC's in them.
Click to expand...
Click to collapse
Sorry for the stupid questions -
CSCs?
Does it matter which I flash?
billyhoyle said:
Sorry for the stupid questions -
CSCs?
Does it matter which I flash?
Click to expand...
Click to collapse
Use the TEL CSC if you're a Telstra user, OPS for Optus, and XSA for Australian generic.
Like I said before, DONT flash the ODIN files unless you already have previously flashed a 4.3 FW via ODIN. Use the zips I made instead.
djb77 said:
Use the TEL CSC if you're a Telstra user, OPS for Optus, and XSA for Australian generic.
Like I said before, DONT flash the ODIN files unless you already have previously flashed a 4.3 FW via ODIN. Use the zips I made instead.
Click to expand...
Click to collapse
Thanks heaps.
Hadn't flashed 4.3 via ODIN (just Telstra update), trying to flash other rom, got stuck in recovery mode, flashing this via ODIN worked.
billyhoyle said:
Thanks heaps.
Hadn't flashed 4.3 via ODIN (just Telstra update), trying to flash other rom, got stuck in recovery mode, flashing this via ODIN worked.
Click to expand...
Click to collapse
And now you have the 4.3 bootloader flashed to you phone.
The whole point of this thread was to save people from doing that and installing KNOX on their phone (which is a new protection from Samsung).
It's too late now to go back to a 4.1.2 bootloader now too.
I updated with stock Optus 4.3 through Odin. Got the Knox apps but managed to disable it then froze it intitanium backup.
Perhaps silly question but what does the CSC mean and what does it do?
Sent from my GT-I9305 using Tapatalk
harlz said:
I updated with stock Optus 4.3 through Odin. Got the Knox apps but managed to disable it then froze it intitanium backup.
Perhaps silly question but what does the CSC mean and what does it do?
Sent from my GT-I9305 using Tapatalk
Click to expand...
Click to collapse
CSC is a sales code and its different for each country and some providers.
Do a google search and you'll find some more info
djb77 said:
And now you have the 4.3 bootloader flashed to you phone.
The whole point of this thread was to save people from doing that and installing KNOX on their phone (which is a new protection from Samsung).
It's too late now to go back to a 4.1.2 bootloader now too.
Click to expand...
Click to collapse
Ive just upadate from 4.1.2 to 4.3 does it mean I have the 4.3 bootloader? thanks
dbp said:
Ive just upadate from 4.1.2 to 4.3 does it mean I have the 4.3 bootloader? thanks
Click to expand...
Click to collapse
Depends on if you flashed the update with ODIN or not, if you did, you'd have the 4.3 bootloader
djb77 said:
Depends on if you flashed the update with ODIN or not, if you did, you'd have the 4.3 bootloader
Click to expand...
Click to collapse
I've have updated it from the device and there is KNOX app but haven't installed it yet and is there rooting for this version?
dbp said:
I've have updated it from the device and there is KNOX app but haven't installed it yet and is there rooting for this version?
Click to expand...
Click to collapse
Just for the fact there is a sign of KNOX isnt good. A custom kernel still might be able to save you and SuperSU for root.
djb77 said:
Just for the fact there is a sign of KNOX isnt good. A custom kernel still might be able to save you and SuperSU for root.
Click to expand...
Click to collapse
I must have a bad rooting last version because when I run SystemApp Remover it prompted my device is not rooted, don't know what to do, very much appreciated
dbp said:
I must have a bad rooting last version because when I run SystemApp Remover it prompted my device is not rooted, don't know what to do, very much appreciated
Click to expand...
Click to collapse
Try flashing the latest version of SuperSU
http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
djb77 said:
Try flashing the latest version of SuperSU
http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
Click to expand...
Click to collapse
damn the security blocked the superSU
The way I rooted my stock 4.3 Optus (with Knox)
I used the cf root recovery that you flash through Odin. Once that's done and you reboot you so don't have root because of Knox. Go to app store and update SuperSu.
From there open SuperSu and it should now ask if you want to have Knox disabled. It worked for me. Then use titanium and delete or freeze all Knox related rubbish.
Sent from my GT-I9305 using Tapatalk
This Is Very Important!!! If You Are On BOE1 BOG5 Or BOK3 Bootloaders Do Not Flash Any Firmware Zips Found Here Or In My Other Threads Or Other Threads They May Have Older Bootloaders In Them And They Will Brick Your Phone!!!!! Only Flash The Ones That Specifically Say They Are For BOE1 Or Later Bootloaders!!!
Stock Verizon 5.0 BOG5 Based Lollipop Rom
Features
Rooted/Busybox/Init.d
Deodexed
Fixed Tethering
Fixed Private Mode
Added SBrowser
SD Card Fix
Updated All apps
Download Rom
VZW_BOG5_STOCK_ROM_DEODEXED.zip
VZW_BOG5_STOCK_ROM_ODEXED.zip (Only Flash Dark It Up Themes V3 or Higher)
Paches/Updates
SafeStrap Flashable Firmware Update For This Rom
This will Update Modem And NON-HLOS.bin And Kernel. No bootloaders will be updated, so device can still be downgraded.
BOG5_Firmware_No_Bootloaders.zip
SafeStrap Flashable Kernel For This Rom
G900V_OG5_Stock_KERNEL_SafeStrap-Flashable.zip
Odin Flashable Full Retail Tar Image With BOD5 Bootloaders
If your comming from KitKat or cannot get HD Calling working you may have to flash this VZW_BOG5_RETAIL_FULL_FIRMWARE_WITH_BOD5_BL.tar.zip then activated HD calling then Flash NCG_Rescue_Tar_And_NCG_For_Root.tar and start over with rooting procedure
Install And Upgrade Instructions
All Firmwares and all Instructions for Upgrading from KitKat Or Lollipop rom can be found Here
XDA:DevDB Information
[VZW_Stock Based TW Rom][5.0 Lollipop BOG5 Build Deodexed], ROM for the Verizon Samsung Galaxy S 5
Contributors
jrkruse
ROM OS Version: 5.0.x Lollipop
ROM Firmware Required: BOC4 or Higher
Version Information
Status: Stable
Created 2015-08-17
Last Updated 2015-08-16
Extras/Mods/Addons
Themes
VZW_JOKER_THEME_PURPLE_GREEN_V3.zip
(Big thanks to @parkerj7uc and @jimwick for letting me use their stuff go to their thread and thank them)
here are some layers themes that will change launcher grid layout this is not a flashable zip there are three different styles in this zip just add the one you want to the system/vendor/overlay folder.
Launcher_Grid_Layout_Overlays.zip
Screens Shots Here
Red_Dark_It_Up_BOE1_V3.zip
Screenshots
Teal_Dark_It_Up_BOE1_V3.zip
Screenshots
Debloater Zips
Debloater.zip
@jrkruse Today I was like i wonder when Jr will release the newest OG5? You're the man Kruse!
Sent from my SM-G900V using XDA Free mobile app
Happy
I am glad that the best is working hard at making this rom for us.
Haha, yeah, I was wondering what the turnaround time was going to be.
BTW, I found transparent overlays that actually work. This is the first time I applied one that touched framework-res that didn't result in spectacular failure. It's $0.99, but I paid the toll.
https://play.google.com/store/apps/details?id=com.spada.transparent
nice work as usual ... just in case anyone asks i was able to dirty flash from jk's boe1 stk deox without any problems. i just reflashed xposed and rebooted a 2nd time and everything is working great. oh i also used flashfire to flash everything and it worked great (i did wipe cache and dalvik after flashing all 3 files inside flashfire)
it hung up on the verizon animation for several minutes on first boot so be patient..
What order did you flash the files in Flashfire, Splink007? And what version of Flashfire? V19 or the current one?
ejc1214 said:
What order did you flash the files in Flashfire, Splink007? And what version of Flashfire? V19 or the current one?
Click to expand...
Click to collapse
im using flashfire v.21 and i queued the bog5 rom , the og5 kernel and then the firmware and lastly clear dalvik and cache. took about 10 mins to reboot back to loading applications screen and then once i was back up i used flashfire to reload xposed and when it rebooted everything was working in full and all my settings and wanam were up and running. probably the easiest flash evah. probably because i was running the last version of this.
btw this version shows as not vulnerable to stagefright.. so if your looking to close the loophole on your phone this is worth the upgrade
Added odexed version of rom
Added Red Dark It Up Theme will work on both deodex and odex roms
Updated Teel Dark It Up Theme to work with deodex and odexed rom also improved some theming
splink007 said:
btw this version shows as not vulnerable to stagefright.. so if your looking to close the loophole on your phone this is worth the upgrade
Click to expand...
Click to collapse
Not vulnerable to all stagefright problems or just the ones that were in the OG5 update?
There's one that wasn't patched with the update.
I'm trying to upgrade from BOE1 Deodexed using FlashFire 21, but it keeps failing when installing System saying that some symlinks could not be created. It then reboots. Any ideas? I was able to install the firmware but not the ROM.
Thanks a bunch. So it looks like this firmware is safe to flash on the developer edition because it doesn't touch the bootloader. Is this correct? Any help would be appreciated. Thanks.
7bigjohn said:
Thanks a bunch. So it looks like this firmware is safe to flash on the developer edition because it doesn't touch the bootloader. Is this correct? Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Do not flash any of my firmware packages or firmware zips on Dev edition. They contain bootloaders. The roms zips are fine as they only flash rom and kernels
MekaByte said:
I'm trying to upgrade from BOE1 Deodexed using FlashFire 21, but it keeps failing when installing System saying that some symlinks could not be created. It then reboots. Any ideas? I was able to install the firmware but not the ROM.
Click to expand...
Click to collapse
I use safestrap but I just successfully flashed both odex and deodexed roms using Flashfire, so I would check md5 of zip
I tried downloading three times and the MD5 always matches.
MekaByte said:
I tried downloading three times and the MD5 always matches.
Click to expand...
Click to collapse
Are you on my BOE1 rom? Try uninstalling Flashfire and reinstall it or try safestrap
Flashed OE1 deodexed (from the muniz thread last night) and noticed folks were having issues flashing the deodexed from this thread over that with flashfire.
I am going to give the deodexed one a shot shortly via Flashfire v21
Update; Flashed Successfully
Order of operation in Flashfire v.21 (after setting screen timeout to 10 minutes in System -.> Display)
* BOG5_Firmware.zip (automount unchecked)
* VZW_BOG5_STOCK_ROM_DEODEXED.zip (automount unchecked)
* Wipe Dalvik Cache and Cache partition options selected (uncheck others)
* Reboot Normal as I am coming from OE1
After phone reboots, verizon logo for 3-4 minutes, then "Android is upgrading Optimizing app xxx of 327 " for 7 -8 minutes., then "starting apps" and finally "finishing boot" to home screen.
Build Reported: OG5
Kernel: 3.4.0 July 31 build.
Root: preserved. If coming from OE1, this was not a complete factory reset. Data and apps are preserved.
I am guessing the problems in the other thread are because this ROM needs the firmware first if coming from a muniz stock ROM.
.
jrkruse said:
Do not flash any of my firmware packages or firmware zips on Dev edition. They contain bootloaders. The roms zips are fine as they only flash rom and kernels
Click to expand...
Click to collapse
Thanks a bunch for the clarification. Much appreciated!
I did a dirty flash (wipe dalvik + cache) from muniz_ri's OE1 deodexed to the deodexed OG5 here using Flashfire v0.21, flashed the safestrap update, flashed xposed framework, then debloated/debloated the extra junk that came with OG5. Hotspot is working, and everything seems to be fine.
@jrkruse, what exactly is SBrowser, I've been trying to figure it out, but haven't been able to find any information on it after searching. Also, what is SBrowserTry.apk, I assume it's something I can get rid of? Sounds like some trial or instructions bloat.
Edit: is SBrowser just the stock Samsung browser? Cause it's literally the first time I've seen it.
Spartan117H3 said:
I did a dirty flash (wipe dalvik + cache) from muniz_ri's OE1 deodexed to the deodexed OG5 here using Flashfire v0.21, flashed the safestrap update, flashed xposed framework, then debloated/debloated the extra junk that came with OG5. Hotspot is working, and everything seems to be fine.
@jrkruse, what exactly is SBrowser, I've been trying to figure it out, but haven't been able to find any information on it after searching. Also, what is SBrowserTry.apk, I assume it's something I can get rid of? Sounds like some trial or instructions bloat.
Click to expand...
Click to collapse
Sbrowser is the stock Internet browser that for some reason isn't available on Verizon roms. You can delete the Sbrowsertry apk I'm not sure what it does but Sbrowser seems to work without it
Pulled from my US X Pure Edition.
Place in Internal Storage and flash in recovery.
Untested with flashing via TWRP as I've waited all day on complete stock ROM to capture and pull this zip.
MUST BE ON STOCK RECOVERY TO FLASH IT. If you flash it in TWRP and boot loop, without making a backup beforehand, you're on your own. You should've made a backup AS ALWAYS.
Screenshots:
{
"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"
}
February 2016 Security Update OTA
Google Drive: blur_version.24.11.18.clark_retus.retus.en.us (flash in stock recovery ONLY)
MD5: e08d5e837d59d9b4ecd88f15ba2906f7
Stock odexed ROM with the February 2016 Security Update applied. No root. Flash in TWRP.
Google Drive: stock_marshmallow_for_moto_x_pure_edition-mphs24.49-18-3 (flash in TWRP)
MD5: 2a1505d2626aa1ef1d18da904a3d5093
Modified boot.img post for use with traditional SuperSU root by DaMadOne here:
http://forum.xda-developers.com/showpost.php?p=65541582&postcount=61
Stock 6.0 Marshmallow Recovery:
IMG version
Google Drive: stock-6.0-mph24.49-18-recovery.img (flash in fastboot or TWRP)
MD5: 2ac9b589a3dc14d4000cbbe082b36ba9
ZIP version
Google Drive: stock-6.0-mph24.49-18-recovery.zip (flash in TWRP)
MD5: a59bb1d9eca25608658cd67f7b4707c2
NOTE: If you get "No command" while booting into stock recovery, hold the power button and press up on the volume key. Options should now be available. I'm not sure why it does that but it used to do it on Nexus devices (and probably still does.)
Spasticdroid said:
Pulled from my US X Pure Edition.
Place in Internal Storage and flash in recovery.
Untested with flashing via TWRP as I've waited all day on complete stock ROM to capture and pull this zip.
Screenshots:
Google Drive: blur_version.24.11.18.clark_retus.retus.en.us
Click to expand...
Click to collapse
So is this captured ota or a stock twrp backup
Google~Android said:
So is this captured ota or a stock twrp backup
Click to expand...
Click to collapse
Spasticdroid said:
capture and pull this zip.
Click to expand...
Click to collapse
It's the OTA.
Hi do you know how to flash this using twrp? I tried and it failed. Thank you in advance.
Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.
I flashed supersu 2.66 as I had done previous but wouldn't boot past the logo. Anyone gotten this rooted?
Nexus 10
Vinrock2244 said:
Hi do you know how to flash this using twrp? I tried and it failed. Thank you in advance.
Click to expand...
Click to collapse
What error? Where's your recovery log?
Doesn't work with TWRP 3.x? Use an older version.
Doesn't work with the older TWRP 2.x? Use TWRP 3.x.
Not working with TWRP period? Flash stock recovery, flash the OTA, put TWRP back.
blkcr said:
Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.
Click to expand...
Click to collapse
I don't use Xposed so I wouldn't know if the OTA will work even after uninstalling it. Also, if you're not using systemless root, you'll have to wipe clean. Back up data apps using Titanium or similar. Systemless root however restores original kernel and files.
rocketsaucev2 said:
I flashed supersu 2.66 as I had done previous but wouldn't boot past the logo. Anyone gotten this rooted?
Nexus 10
Click to expand...
Click to collapse
2.67 systemless works fine.
Spasticdroid said:
2.67 systemless works fine.
Click to expand...
Click to collapse
Do you have a link handy? Is it just twrp flashable?
Nexus 10
Also in for a twrp flashable version
rocketsaucev2 said:
Do you have a link handy? Is it just twrp flashable?
Nexus 10
Click to expand...
Click to collapse
Google SuperSU Beta. Should be the first link to Chainfire's thread.
Run this in a Terminal app (with su) or TWRP's Terminal
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Then flash SuperSU 2.67.
Spasticdroid said:
Google SuperSU Beta. Should be the first link to Chainfire's thread.
Run this in a Terminal app (with su) or TWRP's Terminal
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Then flash SuperSU 2.67.
Click to expand...
Click to collapse
Got it. Thanks
Nexus 10
Just popped up on mine as well. Small.
Interesting, the zip contains baseband patches but the version in the OP remained the same. Anyone notice any differences in reception?
Decided to give this a go... Have combined storage and was on a custom stock rom with xposed and viper.
Flashed stock system and recovery, did not wipe data.
Reboot system, let everything update, verify combined storage untouched.
Stock recovery could not find the update since I have combined storage.
Tried TWRP with no success
Flashed stock recovery and sideloaded the update
Update flashed succesfully
Reboot to bootloader and flash TWRP and kernel of choice.
Reboot system
Reboot to bootloader and flash super su, xposed etc.
2.67 non systemless did not work for me. 2.64 worked fine as usual. Well maybe not, getting a lot of system fc's. Will update once I have it worked out.
So flashing 2.62-3, then flashing 2.64 got me out of bootloops and system fc's. Seems to be good to go now.
I am very interested in systemless root specifically for the security updates and benefits of root.
Using this guide
http://forum.xda-developers.com/showpost.php?p=64624664&postcount=454
and SuperSU beta should all be ok?
I am ATM on trupurexmm 2.6.2, frankenclark v0.7, xt1575 and twrp 3.0.0-1.
Can someone on an untouched stock system pull /system after the update and upload it for me? I would like to create a flashable zip so we don't have to go through all this nonsense to update.
Is there any detailed guide on how to make this OTA update work on a machine with root + twrp?
blkcr said:
Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.
Click to expand...
Click to collapse
Same boat here. Stock rooted with Xposed. Rooted with 2.62.
---------- Post added at 09:02 AM ---------- Previous post was at 08:54 AM ----------
There is a stock 6.0 twrp backup file available. Perhaps you could restore that, take the OTA, then root again?
bostonirishguy13 said:
Same boat here. Stock rooted with Xposed. Rooted with 2.62.
---------- Post added at 09:02 AM ---------- Previous post was at 08:54 AM ----------
There is a stock 6.0 twrp backup file available. Perhaps you could restore that, take the OTA, then root again?
Click to expand...
Click to collapse
I was thinking of this same thing.
For I, I have a stock non root twrp backup. Was thinking of flashing the stock ota mm that I have then flashing the recovery to stock then take the ota. Install twrp, then root.
Sent from XT1575,TPXMM 2.6.2,Frankenclark v0.7
shoman94 said:
Can someone on an untouched stock system pull /system after the update and upload it for me? I would like to create a flashable zip so we don't have to go through all this nonsense to update.
Click to expand...
Click to collapse
I was going to keep this to myself and one other person on here. It's unmodified, meaning no root, and odexed. Only converted to be flashable.
Also note that I have included other items in the ROM including radios/modem and an unmodified logo.bin, meaning you will get the "bootloader unlocked" splash.
Too lazy to make a thread for it. Any one wants to? Have at it.
https://drive.google.com/file/d/0B5AiGacWcBRzMTBlWmppOC1DS3c/view?usp=docslist_api
Sent from my XT1575 using Tapatalk
A new official ColorOS udpate from OPPO is available in my region and at least all Europe I guess.
This is version F1fEX_11_170327. A copy of the OTA update package is here if anyone needs it: F1EX_11_OTA_896-897_patch_201703271119_3cf702307f.zip on MEGA (56.0 MB).
A few screenshots if you want to see the changelog: http://imgur.com/a/5UiiQ
Before:
{
"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"
}
After, full about phone capture: http://imgur.com/CIbWrWX
This is still Android 5.1.1 with a 3.10.28 kernel. No Marshmallow
I'm a bit amazed by the continuous support from OPPO, and especially the security patches integrated in those updates. I was not expecting this from this brand. This is part of what's preventing me from completely switching to LineageOS. This is my only smartphone and I need it to just work.
Now I wish I can unroot my phone, lol
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
Thank you!
But where can I get stock recovery?
You can extract recovery.img from the ColorOS zip.
If someone were to flash this via twrp. When they have followed this thread
https://forum.xda-developers.com/op...pdates-rooted-unlocked-devices-t3395034/page8
They would loose twrp and lose he unlocked bootloader correct?
This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.
kdd998 said:
This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.
Click to expand...
Click to collapse
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?
MiniBlu said:
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?
Click to expand...
Click to collapse
It would be nice if we ever go back to color os. But don't rush it. Take your time. Its not a big rush. But I would rather the time be spent in lineage first. Up to you
MiniBlu said:
I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now).
Click to expand...
Click to collapse
I have a 010 to 896 patch here if needed: https://mega.nz/#!hxxDxAwb!nLa3aDvz3GubMcTaxqaLowRujDt6UKcn0DohuhkclXY
Thanks for all the info. From my point of view, I don't think it's worth the effort. I'd rather work on LineageOS (maybe I'll have time on monday to try new things)
Deleted
kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.
wakaranay said:
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.
Click to expand...
Click to collapse
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete
Jamie_oppo said:
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete
Click to expand...
Click to collapse
both not working. i cant still update tru ota
wakaranay said:
both not working. i cant still update tru ota
Click to expand...
Click to collapse
Have you unlocked your bootloader?
Jamie_oppo said:
Have you unlocked your bootloader?
Click to expand...
Click to collapse
locked bootloader
wakaranay said:
locked bootloader
Click to expand...
Click to collapse
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work
Jamie_oppo said:
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work
Click to expand...
Click to collapse
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware
wakaranay said:
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware
Click to expand...
Click to collapse
Read post 3 of this thread. Miniblu made a firemware zip. Oops sorry didn't include a link
https://forum.xda-developers.com/oppo-f1/development/rom-unofficial-cyanogenmod-13-t3542718/page23
How to re install the original recovery :crying:
This is for Europe (11.2.2.2.LE25DA). If you are on Global, EU version works, but up to you. It appears for last year, unless you are from India, OnePlus doesn't care. It might be a while before a Full OTA update for Global is released, you'll notice updates come without it for Global or on their Global support site, the firmware is outdated.
- On T-Mobile have full 5G. I don't know about AT&T and Verizon. Should be same.
If you are on Global and you just received your phone. Do all the updates from the incremental through device. If you want root, you can flash with the EU patched boot.img and everything will work as normal
**** but once you do this, you will need to wait for Global full OTA to update next time, unless you managed to have a backup copy of the unpatched boot.img
Do the usual to unlock your OnePlus 9: oem unlock, usb debugging from developer. Boot into bootloader and use adb command /fastboot flashing unlock
This will wipe your phone and reboot. Setup your phone
Install Magisk from his official github: https://github.com/topjohnwu/Magisk/releases/tag/v22.0
- Topjohn provides full instructions on how to do this yourself as well.
Reboot into bootloader
Flash boot the magisk modified boot.img. /fastboost flash boot boot.img
Go into Magisk app and install via direct install and all done.
Return to stock
- Restore boot.img from Magisk
- Uninstall Magisk
- Flash the stock boot.img
- Relock the bootloader, will wipe and return to factory reset.
Stock 11.2.33 Boot.img
boot11233_stock.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Magisk Patched 11.2.33 boot.img
boot11233_patched.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Spoiler: Previous Boot Images
Patched Boot.img for Europe (11.2.2.2.LE25DA)
boot93.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Stock Boot.img for Europe (11.2.2.2.LE25DA)
boot.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Future Full OTA Updates
- Update as usual
- Go into Magisk and choose direct install and then install to inactive slot after OTA
- This will retain root
How to do it yourself:
Download full OTA, usually Oxygen Updater App, XDA has links or from https://www.oneplus.com/support/softwareupgrade
Download Payload Dumper
payload_dumper-win64.zip | Tool by geminids14 for Utilities
Extract payload.bin in xiaomi weekly build zip for MI A1
androidfilehost.com
Extract and place payload.bin in input folder
{
"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"
}
Run the payload_dumper.exe
In the output folder will be boot.img, move that onto your phone, folder of your choice
Go to Magisk app, click install
Choose Select and Patch a File
Choose the file and it will patch it, Magisk will say where the file is located.
That is your patched boot.img file. Use that to flash / root your phone.
Remember only have do this once, you don't have to do this again with subsequent updates.
zymphad said:
Do the usual to unlock your OnePlus 9: oem unlock, usb debugging from developer. Boot into bootloader and use adb command /fastboot flashing unlock
This will wipe your phone and reboot. Setup your phone
Install Magisk from his official github: https://github.com/topjohnwu/Magisk/releases/tag/v22.0
Reboot into bootloader
Flash boot the magisk modified boot.img. /fastboost flash boot boot.img
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Go into Magisk app and install via direct install and all done.
Click to expand...
Click to collapse
What version/region of the OP9 is this boot.img for? Where did you get the original unmodified one? I need Canadian.
Slikkster2k said:
What version/region of the OP9 is this boot.img for? Where did you get the original unmodified one? I need Canadian.
Click to expand...
Click to collapse
So there seems to be confusion about version. The boot image doesn't matter. When you flash a custom rom, there isn't a EU or US version. The only difference I can think of if it's T-Mobile, so when you flash, then it would just be an international/global. This is from XDA.
Honestly I would bet the Indian version is same as well.
This is the EU, which is the same boot.img for US unlocked.
If the future you should be able to do this yourself once OnePlus adds the 9 series to their global firmware downloads list.
Good to know, thanks! I'm not planning to flash a custom rom, I just want root. So I just have to make sure the bootloader is unlocked, and then follow the steps for Magisk.
Yep, working great here. Mobile payments working fine. Using energized for adblock.
So I successfully rooted yesterday, all is working great. Today my phone prompts me that system update 11.2.1.1 is available. Of course, I cannot upgrade while rooted. However, I also can't restore my stock boot.img because I don't have a copy of it... Any way to update without doing a factory reset, or am I screwed?
Edit: From what I've found, factory reset doesn't touch the boot partition. So that won't help.
This method worked for me, though I'm now running the same issue as Slikkster2k, since I don't have an unpatched boot.img, I can't uninstall magisk to update via OTA.
I would suggest, for those wanting to be able to update in the future (until we get a custom recovery), that instead of /fastboot flash boot boot.img, use /fastboot boot boot.img and then let Magisk finish the install. When Magisk patches the boot image, it will take a backup of the stock one to be used for uninstallation.
Slikkster2k said:
So I successfully rooted yesterday, all is working great. Today my phone prompts me that system update 11.2.1.1 is available. Of course, I cannot upgrade while rooted. However, I also can't restore my stock boot.img because I don't have a copy of it... Any way to update without doing a factory reset, or am I screwed?
Click to expand...
Click to collapse
Install magisk module-a/b install-before you reboot, then select direct install to second slot and reboot. Works beautifully.
[email protected] said:
Install magisk module-a/b install-before you reboot, then select direct install to second slot and reboot. Works beautifully.
Click to expand...
Click to collapse
I can't install the OTA update at all -- I'm on global ROM, so it fails because it's attempting a partial OTA update, rather than flashing a full ROM.
@zymphad
Do you also have a copy of the unpatched boot.img file?
Slikkster2k said:
I can't install the OTA update at all -- I'm on global ROM, so it fails because it's attempting a partial OTA update, rather than flashing a full ROM.
Click to expand...
Click to collapse
With rooted phone you need to do full not partial.
We are on the February security update. The latest update for OP9 is still on it, so disappointing.
We have to wait until the March security update that is already out for other oneplus devices.
You can unroot and re-lock your bootloader and then install the partial and then do the whole process again. I am not going to do that, seems waste of time.
Uninstall Magisk -- Flash stock boot.img -- lock bootloader.
This will wipe your phone back to factory reset!!!
But I expect we will see March update soon since Nord and 8 series have them already.
zymphad said:
With rooted phone you need to do full not partial.
We are on the February security update. The latest update for OP9 is still on it, so disappointing.
We have to wait until the March security update that is already out for other oneplus devices.
You can unroot and re-lock your bootloader and then install the partial and then do the whole process again. I am not going to do that, seems waste of time.
Uninstall Magisk -- Flash stock boot.img -- lock bootloader.
This will wipe your phone back to factory reset!!!
But I expect we will see March update soon since Nord and 8 series have them already.
Click to expand...
Click to collapse
The issue is that even if we wanted to do this, Slikkster2k and I (and possibly others), don't have the stock boot.img, since we flashed the magisk patched boot.img directly. Since you provided the patched boot.img originally, do you have the unpatched version available?
That way if anyone still on the original version that came pre-loaded wants to flash back to fully stock (and maybe re-lock bootloader) they can.
Those of us on the Global/US variant (AA) don't have the full zip available, and since we can't flash incremental while rooted, we currently have no way of actually reverting to stock until OnePlus publishes the full ROM zip.
Will post the stock.
I mean dunno why would want to since to do the incremental think have to relock bootloader which would factory reset.
And the to root again would factory reset again...
The March security update is already out for Nord and 8 series. Would just wait.
The incremental is still the Feb security update which you are already on.
Thanks, I mostly just wanted to redo the root process, but use /fastboot boot boot.img instead of /fastboot flash boot boot.img, so that magisk has a backup of the stock bootloader. That way, if for some reason I need to flash back to stock before the March Security update comes out, I can do so from my phone without needing my PC.
zymphad said:
I mean dunno why would want to since to do the incremental think have to relock bootloader which would factory reset.
Click to expand...
Click to collapse
Ah, was not aware of that. In that case we'll just have to wait, hopefully OnePlus posts it soon.
Besides, the patched bootloader you posted is from 11.2.1.1 (I compared the hash to the one in the other thread), so I assume the stock image is the same. So it's no good to us anyways.
Slikkster2k said:
Besides, the patched bootloader you posted is from 11.2.1.1 (I compared the hash to the one in the other thread), so I assume the stock image is the same. So it's no good to us anyways.
Click to expand...
Click to collapse
Ahh, I didn't realize that, I guess it's just a good thing that the 11.2.1.1 boot.img doesn't cause any issues when flashed onto 11.2, since we would have had no way to undo it
reffu said:
Ahh, I didn't realize that, I guess it's just a good thing that the 11.2.1.1 boot.img doesn't cause any issues when flashed onto 11.2, since we would have had no way to undo it
Click to expand...
Click to collapse
Actually I tested it using fastboot boot boot.img before I flashed it, just to make sure it would work (I didn't know it was from 11.2.1.1 at the time, but I'm paranoid).
Seems the rest of the world is getting the March update except US again. Still no full package, and this time not even partial. Dunno what is going on with OnePlus and US, but it's annoying.
Will update for EU AB firmware in the OP. And then put disclaimer for Global to do all their updates prior to rooting.