Hi my fellow rog 2 friends.
Just want to tell you how you update ur WW Rog 2 and keep root.
1. Be rooted (unlocked bootloader + magisk) and have ur device on a WW Fingerprint. (CN Device or WW Device)
2. Download the newest full.zip(19.08WW) update to the root of your phone and reboot
3. After the reboot u get asked if you want to update press yes and wait til 100%
4. When u get to 100% dont restart! Press on later and open Magisk Manager
5. Press Install and choose "install on inactive slot (ota)
6. Wait til its done and reboot over magisk.
Tadaaaa, you update the rom and keeped root.
Have fun.
(Should work on CN devices on CN Rom as well)
Olee
{
"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"
}
Enviado desde mi ASUS_I001DE mediante Tapatalk
Wow, so easy! Thanks!
Thank you I was worried about updating because of that. Will do so this weekend though!
secXces_debaki said:
Hi my fellow rog 2 friends.
Just want to tell you how you update ur WW Rog 2 and keep root.
1. Be rooted (unlocked bootloader + magisk) and have ur device on a WW Fingerprint. (CN Device or WW Device)
2. Download the newest full.zip(19.08WW) update to the root of your phone and reboot
3. After the reboot u get asked if you want to update press yes and wait til 100%
4. When u get to 100% dont restart! Press on later and open Magisk Manager
5. Press Install and choose "install on inactive slot (ota)
6. Wait til its done and reboot over magisk.
Tadaaaa, you update the rom and keeped root.
Have fun.
(Should work on CN devices on CN Rom as well)
Click to expand...
Click to collapse
Thanks for the guide, but this is for the latest CN firmware not WW. I will try this update when the WW firmware is released.
sesz said:
Thanks for the guide, but this is for the latest CN firmware not WW. I will try this update when the WW firmware is released.
Click to expand...
Click to collapse
It's universal. Just insert latest ww rom.
It's not only for Chinese. I used the tutorial with WW firmware. Where can I find rom downloads and changelog? The 1908 update for WW there is not at ASUS website. Thanks
https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_BIOS/
not work update fail. can you have a vdo tutorial?
not work update fail.
can you have a vdo tutorial?
If the update fails you don't have matching fingerprint.
U can see how to change the Fingerprint on other threads here on xda.
secXces_debaki said:
It's universal. Just insert latest ww rom.
Click to expand...
Click to collapse
Thanks will do that now
tsoureki said:
It's not only for Chinese. I used the tutorial with WW firmware. Where can I find rom downloads and changelog? The 1908 update for WW there is not at ASUS website. Thanks
https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_BIOS/
Click to expand...
Click to collapse
WW-16.0631.1908.12 just released on Asus website
Improved Item:
1.Added the AirTriggers/Key Mapping/Macro tabs, and Share/Import features to the Scenario Profiles in Armoury Crate
2.Added setting options for AirTriggers squeeze gesture
3.Added the option to switch between different Bluetooth devices in Calling Screen
Perfect it worked great, thanks for sharing!
secXces_debaki said:
Hi my fellow rog 2 friends.
Just want to tell you how you update ur WW Rog 2 and keep root.
1. Be rooted (unlocked bootloader + magisk) and have ur device on a WW Fingerprint. (CN Device or WW Device)
2. Download the newest full.zip(19.08WW) update to the root of your phone and reboot
3. After the reboot u get asked if you want to update press yes and wait til 100%
4. When u get to 100% dont restart! Press on later and open Magisk Manager
5. Press Install and choose "install on inactive slot (ota)
6. Wait til its done and reboot over magisk.
Tadaaaa, you update the rom and keeped root.
Have fun.
(Should work on CN devices on CN Rom as well)
Click to expand...
Click to collapse
Thanks a lot, I updated my ROG Phone 2 without root and magisk. I didn't know before how to do it. I downloaded update from asus site and then extracted payload and flashed all files and that bricked my phone. so I went back to older version. today I saw your post and just copied file to root directory of device and restarted and once phone reboots, I saw update prompt.. and now I'm on latest build
People throw the brick term around here freely. A brick, is well a brick. Completely dead, like a brick.
suzook said:
People throw the brick term around here freely. A brick, is well a brick. Completely dead, like a brick.
Click to expand...
Click to collapse
..... Which occurs when users ignore the instructions given along with the tools or files !
Yup, worked a treat from 1907 to 1908 WW (fingerprint was altered prior)
Why does it not ask for update on reboot?
EDIT: had to use CN version even tho my current is WW? is it because my phone was originally CN? confused someone explain.
Nyuha said:
Why does it not ask for update on reboot?
EDIT: had to use CN version even tho my current is WW? is it because my phone was originally CN? confused someone explain.
Click to expand...
Click to collapse
Did you change the fingerprint as well to ww?
Nyuha said:
Why does it not ask for update on reboot?
EDIT: had to use CN version even tho my current is WW? is it because my phone was originally CN? confused someone explain.
Click to expand...
Click to collapse
OK, so you must first change the finerprint of the whole device to WW, not just the ROM. You can use this app here where, under system, after flashing WW rom only, you will see that a couple of parts are still designated to CN fingerprint. Follow this guide to the letter and you will have 1907 installed with true WW fingerprint (i didn't follow steps to unroot and lock bootloader - i am still rooted). Then use this guide which you were on, download the zip of 1908 WW and follow instructions. Then you'll have WW up to date and rooted with BL unlocked. Happy days! Good luck
suzook said:
People throw the brick term around here freely. A brick, is well a brick. Completely dead, like a brick.
Click to expand...
Click to collapse
I agree, I don't think I would want to play games on a brick!
DO NOT TRY THIS ON VERSION 20 magisk update, it's just left my device unbootable on 1908 WW saying Slot _a is unbootable
Related
Guys there are too many threads on this topic but nothing makes everything clear.
So please share your thoughts here.
Present scenario
I'm on the Indian ROM ZUI 2.0.093
I just got the handset with this ROM installed.
When I check for updates this is what I get.
Screenshot attached
Please tell me if flashing this CN ROM will get me OTA and warranty services.
Z2131_CN_OPEN_USER_Q01002.1_M_ZUI_1.9.044_ST_160523_qpst.rar
Qn: after I flash the this CN ROM,
1.How will I get Google services.
2. Should I continue to use this CN Rom and do OTA with VPN enabled or
Flash any specific Indian ROM in any specific method to get the services.
I think the seller has unlocked the bootloader.
But there is no custom recovery installed and there is no SuperSU and not sure if the bootloader is locked or unlocked.
(I'll check on this and will update the scenario)
Please help
Also please provide links to flashing guide (CN Rom) qpst qfil if possible.
Thanks in advance.
Sent from my ZUK Z2132 using Tapatalk
Updater screenshot
{
"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"
}
Sent from my ZUK Z2132 using Tapatalk
rameeskr said:
Updater screenshot
Sent from my ZUK Z2132 using Tapatalk
Click to expand...
Click to collapse
- Flash Chinese stock ROM 1.9.044 using QFIL
- Flash Indian Stock ROM 2.0.093
- Install FlyVPN in your phone after booting the previously insatlled Indian ROM.
- Connect to any China server using FlyVPN
- Open updater app and you'll see an update to Version 2.0.133, hit update and let the phone update.
- AFter update, connect to Chinese server through FlyVPN again, and open the updater app again.
- You should see an update to Version 2.5.104 this time, hit update and let the phone download and install the update.
rockingpiyush13 said:
- Flash Chinese stock ROM 1.9.044 using QFIL
- Flash Indian Stock ROM 2.0.093
- Install FlyVPN in your phone after booting the previously insatlled Indian ROM.
- Connect to any China server using FlyVPN
- Open updater app and you'll see an update to Version 2.0.133, hit update and let the phone update.
- AFter update, connect to Chinese server through FlyVPN again, and open the updater app again.
- You should see an update to Version 2.5.104 this time, hit update and let the phone download and install the update.
Click to expand...
Click to collapse
Thanks mate.
Can you please give link to download the indian stock rom 2.0.093.
Thanks
Sent from my ZUK Z2132 using Tapatalk
rameeskr said:
Thanks mate.
Can you please give link to download the indian stock rom 2.0.093.
Thanks
Sent from my ZUK Z2132 using Tapatalk
Click to expand...
Click to collapse
ZUI_2.0.093_ST
There you go!
Got it.
And is successful flash done.
I'm receiving OTA through china VPN though very slow .
But the Nougat OTA 2.5.104ST is failing (3 times).
I think I'll stick with marshmallow for a while since the 2.0.133 build is just fine
Sent from my ZUK Z2132 using Tapatalk
rameeskr said:
Got it.
And is successful flash done.
I'm receiving OTA through china VPN though very slow .
But the Nougat OTA 2.5.104ST is failing (3 times).
I think I'll stick with marshmallow for a while since the 2.0.133 build is just fine
Sent from my ZUK Z2132 using Tapatalk
Click to expand...
Click to collapse
so u got same stock n regained warranty back??
romanpatel said:
so u got same stock n regained warranty back??
Click to expand...
Click to collapse
Yes, same question in my mind for @rameeskr
I just got this phone and before rooting wanted to be sure.
mGforCe said:
Yes, same question in my mind for @rameeskr
I just got this phone and before rooting wanted to be sure.
Click to expand...
Click to collapse
I got the warranty back. You're safe to root. Cheers
sammessi10 said:
I got the warranty back. You're safe to root. Cheers
Click to expand...
Click to collapse
one last query,
Can you pls tell us how did you know that you got warranty back?
abhimanyu.singh said:
one last query,
Can you pls tell us how did you know that you got warranty back?
Click to expand...
Click to collapse
After you unlock your bootloader, the phone shows a message on boot stating that you unlocked your bootloader. This shows that your warranty is void. After flashing stock ROM through QPST, you no longer get this message. You get your warranty back.
How to root and flash through QPST
jiteshsr said:
flash through QPST
Click to expand...
Click to collapse
Search in "Guides" section.
jiteshsr said:
How to root
Click to expand...
Click to collapse
Via TWRP. Search in "Guides" too.
Thanks
Getting its easy way
Flash any zui version like 2.0.93 with mi-flash or qpst .
Then go to update app and clear it's data ( turn on mobile data or wifi ) .you will receive update notification in notifications .
Update it .
Again after updating clear the updater app's data .
You will get ota fine .
sammessi10 said:
After you unlock your bootloader, the phone shows a message on boot stating that you unlocked your bootloader. This shows that your warranty is void. After flashing stock ROM through QPST, you no longer get this message. You get your warranty back.
Click to expand...
Click to collapse
Take a look at below post, it says otherwise:
https://forums.lenovo.com/t5/Moto-G...locking-Bootloader-void-warranty/td-p/3546705
ams73 said:
Take a look at below post, it says otherwise:
https://forums.lenovo.com/t5/Moto-G...locking-Bootloader-void-warranty/td-p/3546705
Click to expand...
Click to collapse
ZUK isn't Moto. Read the mail that you get when you requested the bootloader unlock image
sammessi10 said:
ZUK isn't Moto. Read the mail that you get when you requested the bootloader unlock image
Click to expand...
Click to collapse
ZUK, Lenovo, Moto all belong to Lenovo now and the unlocking process is the same for all of them.
If what you're claiming is correct then that's a great news.
ams73 said:
ZUK, Lenovo, Moto all belong to Lenovo now and the unlocking process is the same for all of them.
If what you're claiming is correct then that's a great news.
Click to expand...
Click to collapse
Oppo, Vivo and OP all are owned by the same company.. they do have difference..
sammessi10 said:
Oppo, Vivo and OP all are owned by the same company.. they do have difference..
Click to expand...
Click to collapse
Sure, please refer to the screen shot below, if the 2nd command output is all "false" after reverting to stock, only then probably warranty can be reclaimed. (of course unless they maintain a registry of unlock_bootloader images issued phones). :good:
[ROM] Stock Rom 9.0 Flash and Repair [Full] @XDAfriends hello my friends
New Update Stock is disponible in Sammobile.com
https://www.sammobile.com/firmwares/
Version Android 8.1 e 9.0
Build date Mon, Jul 2019 12:24:39 +0700
All variantes J730G / F / GM / K / FM update
Install and enjoy your new Samsung update for j730x
[Flash]
To Flash or Repair your original system
1. Download Samsung drivers
2. Download Odin
3. Download your firmware ROM Official
4. Power Off your mobile J7
5. Restart Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
6. Install Samsung Drivers
7. Connect Your phone with USB cable to PC
8. Open Odin and Add the firmware file to AP / PDA
9. Select too CP partition in the firmware folder
10. Select too CSC partition in the firmware folder
11. Select too Userdata partition in the firmware folder
12. Click the start button, sit back and wait few minutes
13. This method reinstall your rom to original state
[Recomendation]
Install Your stock 9.x or Install 9.x Custom Stock
Install TWRP
Install Root Magisk
Install Kernel Helios 3.x
[Information]
About Odin details - This informations is very usefull
According to this XDA-Developers forum post and this Droidguiding article:
BL stands for bootloader
AP represents the system partition, under previous Odin versions, this was called "PDA"
CP represents your modem
CSC stands for Consumer Software Customization, this specifies the features your Android device gets according to its geographical location and carrier
Download Odin v3.13.1
https://www.filesbeast.net/download/1/Odin 3.13.1.zip
Servers
https://www.stockrom.net/samsung
Press F3 and search your model
https://www.sammobile.com/firmwares/
J730G
https://www.sammobile.com/firmwares/galaxy-j7-pro/SM-J730G/
J730F
https://www.sammobile.com/firmwares/galaxy-j7-pro/SM-J730F/
J730GM
https://www.sammobile.com/firmwares/galaxy-j7-pro/SM-J730GM/
J730FM
.https://www.sammobile.com/firmwares/galaxy-j7-pro/SM-J730FM/
Search your model on page
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What file of the 5 that come must be put in the box USERDATA?
Thank you
ismago said:
What file of the 5 that come must be put in the box USERDATA?
Thank you
Click to expand...
Click to collapse
you do not need to put anything in this box, when unpacking, come 5 files plus you will only use 4, in the CSC box you use HOMECSC.
NathyAndrade said:
you do not need to put anything in this box, when unpacking, come 5 files plus you will only use 4, in the CSC box you use HOMECSC.
Click to expand...
Click to collapse
Ok. Thank you
I have followed all the steps and now the problem I have is that it does not let me root or install TWRP.
Previously I had Root done and installed TWRP and it worked correctly.
When I try to root with Odin, the installation does it correctly, but when I restart it I get a black screen that tells me the following.
Verification error
Can not restart the device. Error to
verify integrity. It is necessary to restore
the device to the default settings of
factory. This will delete all your data.
RESTORE
And if I want to install TWRP it is also installed correctly, but when it is restarted, it remains in a loop with the SAMSUNG screen and constantly restarts.
If I do not root or install TWRP the device boots and works properly.
Do you know what can happen to him?
Thank you so much
Hello,
Odin's link is bad.
Should be:
https://dl.sammobile.com/Odin3-v3.13.1.zip
not very clear: you don't say anything about the BL file or the options for Odin
ismago said:
I have followed all the steps and now the problem I have is that it does not let me root or install TWRP.
Previously I had Root done and installed TWRP and it worked correctly.
When I try to root with Odin, the installation does it correctly, but when I restart it I get a black screen that tells me the following.
Verification error
Can not restart the device. Error to
verify integrity. It is necessary to restore
the device to the default settings of
factory. This will delete all your data.
RESTORE
And if I want to install TWRP it is also installed correctly, but when it is restarted, it remains in a loop with the SAMSUNG screen and constantly restarts.
If I do not root or install TWRP the device boots and works properly.
Do you know what can happen to him?
Thank you so much
Click to expand...
Click to collapse
I using root normaly steps
1. Access onfiguration and developer options
2. Select - unlock by oem
3. Reboot in stock recovery
4. Wipe and factory reset
5. Reboot in download mode
6. Flash twrp and reboot in twrp directly
7. Flash supersu 2.82 and root is perfectly
My iPhone is j730g and root is ok
Forget about supersu and install magisk instead. Follow the steps here: https://forum.xda-developers.com/ga...-3-1-1-1-j7-pro-sm-j730f-g-gm-t3662621/page14
arwandar said:
not very clear: you don't say anything about the BL file or the options for Odin
Click to expand...
Click to collapse
Read first post about BT CP CSC and AP details
New OS upgrade for j730xx
hacker812c said:
BL option no necessary, the BL is ok
i no rewrite my bootloader
The version is the same
Thanks
Click to expand...
Click to collapse
@NathyAndrade hello my friend
New update stock is disponible in Sammobile.com
https://www.sammobile.com/firmwares/
Version Android 7.0
Changelist 13203669
Build date Mon, 12 Mar 2018 13:25:39 +0000
Security Patch Level 2018-03-01
Product code All variants
PDA J730GUBU3ARC2
CSC J730GZTO3ARC2
All variantes J730G / F / GM / K / FM update
Install and enjoy your new Samsung update for j730xx
new OS upgrade for j730xx
hacker812c said:
BL option no necessary, the BL is ok
i no rewrite my bootloader
The version is the same
Thanks
Click to expand...
Click to collapse
@NathyAndrade hello my friend
New update stock is disponible in Sammobile.com
https://www.sammobile.com/firmwares/galaxy-j7-pro/SM-J730G/ZTO/download/J730GUBU3ARC2/214163/
All variantes J730G / F / GM / K / FM update
Install and enjoy your new Samsung update for j730xx
arwandar said:
not very clear: you don't say anything about the BL file or the options for Odin
Click to expand...
Click to collapse
News my friends around the world
The new updates 7.1.1 for J730xx
https://samsung-firmware.org/model/SM-J730G/
Perhaps the biggest change introduced in 7.1 is long press on app icons to reveal app-specific-action shortcuts. Kind of what Apple does via 3d touch. Interestingly those actions can be moved to create new separate icons.
Nougat 7.1.1 for J730G region Brazil Oi
https://samsung-firmware.org/model/SM-J730G/region/ZTR/
hacker812c said:
News my friends around the world
The new updates 7.1.1 for J730xx
https://samsung-firmware.org/model/SM-J730G/
Perhaps the biggest change introduced in 7.1 is long press on app icons to reveal app-specific-action shortcuts. Kind of what Apple does via 3d touch. Interestingly those actions can be moved to create new separate icons.
Nougat 7.1.1 for J730G region Brazil Oi
https://samsung-firmware.org/model/SM-J730G/region/ZTR/
Click to expand...
Click to collapse
What are you talking about? All these roms are Android 7.0.
Greight said:
What are you talking about? All these roms are Android 7.0.
Click to expand...
Click to collapse
Hello Greight Thanks for reply
Really until yesterday the site was with the roms available. thanks for the feedback
does this way allow me keeping updating OTA ?
eraganxs said:
does this way allow me keeping updating OTA ?
Click to expand...
Click to collapse
Yes,
Absolutely the rewriting of the original rom returns the system update support
Re flash your rom totaly and receive updates from samsung
hacker812c said:
Hello Greight Thanks for reply
Really until yesterday the site was with the roms available. thanks for the feedback
Click to expand...
Click to collapse
No, there wasn't bro. I'm more or less obsessed with updates and check there regularly. Up till now, all the roms have been 7.0.
hacker812c said:
Yes,
Absolutely the rewriting of the original rom returns the system update support
Re flash your rom totaly and receive updates from samsung
Click to expand...
Click to collapse
Thanks bro
FAQ. about Android 7.0 encryption
Many users still do not understand why they try to root in
Android 7.0 and go through problems like bootloop
One of the causes of this problem is the encryption of Nougat android 7.x
Recomendations for Root or TWRP
Boot your device to RECOVERY [Stock] mode then select
FACTORY RESET. THIS WILL WIPE YOUR DEVICE AND YOU WILL LOSE ALL DATA.
(This procedure is required to remove encryption or your device won't boot)
From RECOVERY, IMMEDIATELY Boot your device to DOWNLOAD mode then
connect your USB cable. (DO NOT LET YOUR DEVICE REBOOT NORMALLY
OR YOUR DEVICE WILL RE-ENCRYPT
After this point flash Recovery TWRP and open TWRP immediately
and flash Supersu 2.82.zip [Recomended]
At this point your root is perfectly
-------------------------//--------------------------
About Odin details - This informations is very usefull
According to this XDA-Developers forum post and this Droidguiding article:
BL stands for bootloader
AP represents the system partition; under previous Odin versions, this was called "PDA"
CP represents your modem
CSC stands for Consumer Software Customization, this specifies the features your Android device gets according to its geographical location and carrier
I got the NA build for 11.2.6.6 this morning. Installed and rooted without issue via the normal restore image, update, install active/inactive method.
Not seeing it yet on oxygen updater...
I'm past ready!
galaxys said:
Not seeing it yet on oxygen updater...
I'm past ready!
Click to expand...
Click to collapse
I never use Oxygen Updater, I just got it through the normal OTA/System Updates thing.
It was released some days ago and started with IN region, below is the changelog
{
"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"
}
Still not out for EU, Why is India prioritised now? Most users?
djsubterrain said:
Still not out for EU, Why is India prioritised now? Most users?
Click to expand...
Click to collapse
Because it's the best android flagship in Indian market right now with good price.
djsubterrain said:
Still not out for EU, Why is India prioritised now? Most users?
Click to expand...
Click to collapse
There are various reasons which should not be discussed here but let me just say no 5G in India yet definitely plays a role as the builds don’t have to be certified separately with carriers if that makes sense.
Appropriately, NA = Not Available!
avid_droid said:
What does that even mean? NA? NORTH AMERICAN? Sorry to burst your bubble but try to be specific with a model or region number/code. There is no NA model in OnePlus.
Click to expand...
Click to collapse
NA stands for the Global devices (LE2125) with build tag LE15AA sold outside the below regions.
LE2123: EU is the European Version (Build Tag BA)
LE2121: IN is the India Version (Build Tag DA, generally the first to receive the update)
Chinese units (LE2120) run ColourOS out of the box.
LE2127 units are T-Mobile units running LE5ACB builds and will be the last to receive the update.
Hope this clarifies all the confusion
Could someone grab the package before it gets deleted from their phone?
avid_droid said:
What does that even mean? NA? NORTH AMERICAN? Sorry to burst your bubble but try to be specific with a model or region number/code. There is no NA model in OnePlus.
Click to expand...
Click to collapse
11.2.6.6 NA Rolling Out
I got the NA build for 11.2.6.6 this morning. Installed and rooted without issue via the normal restore image, update, install active/inactive method.
forum.xda-developers.com
I am sure you probably had an idea anyway. NA is also the common reference used by OnePlus as well.
Don't worry, my bubble is ok.
dmarden said:
I got the NA build for 11.2.6.6 this morning. Installed and rooted without issue via the normal restore image, update, install active/inactive method.
Click to expand...
Click to collapse
Is anyway you could write exact instructions please how to update the system not using full zip? I'm still on 11.2.4.4 and rooted.
netgar said:
Is anyway you could write exact instructions please how to update the system not using full zip? I'm still on 11.2.4.4 and rooted.
Click to expand...
Click to collapse
I go into magisk and choose the uninstall/restore images option.
Let system update download and install. Once it's done, I do not reboot.
I go into magisk and install to both the active and inactive slots (this works because until you reboot, you're still loaded into the OS with root).
Reboot
Hope it helps
avid_droid said:
Yeah that's still stupid because if referenced as NA the LE2127 should also be referenced the same as it is a NA model also. It's just dumb in my opinion
Click to expand...
Click to collapse
Your opinion is fine and valid, you just don't need to take it out on me is all. I forgive you.
After this update, i noted no real changes on the connectivity, still low signal, still some lags and stutter when scrolling, the camera i don't know i don't use it that much, and also still got the dead spot on touch near at the bottom ledt corner or right where the enter and the ?123buttons are on keyboard, some times i need to push 3 or 4 times for it to work, on the keyboard or even to launch an app or when using an app
BA-Version is now offered via Oxygen updater
dmarden said:
I go into magisk and choose the uninstall/restore images option.
Let system update download and install. Once it's done, I do not reboot.
I go into magisk and install to both the active and inactive slots (this works because until you reboot, you're still loaded into the OS with root).
Reboot
Hope it helps
Click to expand...
Click to collapse
U mean to install incremental update or full zip update?
As far as I know if my phone is rooted I need to install full zip update, otherwise I can screw up.
Correct me if I am wrong please
netgar said:
U mean to install incremental update or full zip update?
As far as I know if my phone is rooted I need to install full zip update, otherwise I can screw up.
Correct me if I am wrong please
Click to expand...
Click to collapse
Just the incremental update via the stock updater. That's how I always do it, it's fine.
dmarden said:
Just the incremental update via the stock updater. That's how I always do it, it's fine.
Click to expand...
Click to collapse
I thought you always need to install full zip update ones you are rooted. That's ev
dmarden said:
Just the incremental update via the stock updater. That's how I always do it, it's fine.
Click to expand...
Click to collapse
Last question...
Does the stock image boot always get restored during rooting process?
I am not sure if my stock boot image was restore during rooting.
Thank you for your help
Hello Vivo X80 Pro community,
I'm having issues flashing the rollback file from the Android 13 Developer Preview: https://developer.vivo.com/doc/detail?id=120
{
"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"
}
My guess is that the hyperlink is linking towards a W30 ROM instead of a W20 ROM. PD2185F_EX_A_12.0.12.5.W20.V000L1-update-full.zip.
Does anyone have a rollback file for the W20 version of the X80 Pro that they can upload to androidfilehost or Google Drive please?
I heard 12.0.11.2 is the best version to do a bootloader unlock so I'm hoping someone has this one, but right now I'll be happy just to go back to Android 12.
Thanks in advance!
it's best to write to Vivo. I couldn't find anything on the internet. Vivo linked an incorrect file.
Service Center | vivo Global
vivo provides comprehensive after-sales services and technical support for products. Check where our service centers are in your location here.
www.vivo.com
I thing the problem is you have a PD2185BF, the roll back is PD2185F....
morpheus620 said:
it's best to write to Vivo. I couldn't find anything on the internet. Vivo linked an incorrect file.
Service Center | vivo Global
vivo provides comprehensive after-sales services and technical support for products. Check where our service centers are in your location here.
www.vivo.com
Click to expand...
Click to collapse
That was the first thing I tried but I was thinking that surely someone had the ROM downloaded.
dzontra83 said:
I thing the problem is you have a PD2185BF, the roll back is PD2185F....
Click to expand...
Click to collapse
This was the A13 file I used to update successfully, so it is likely that PD2185F is my model number.
PD2185F_EX_A_13.1.8.7.W20.V000L1-update-full.zip
hamisgood said:
Hello Vivo X80 Pro community,
I'm having issues flashing the rollback file from the Android 13 Developer Preview: https://developer.vivo.com/doc/detail?id=120
View attachment 5690991
My guess is that the hyperlink is linking towards a W30 ROM instead of a W20 ROM. PD2185F_EX_A_12.0.12.5.W20.V000L1-update-full.zip.
View attachment 5690989
Does anyone have a rollback file for the W20 version of the X80 Pro that they can upload to androidfilehost or Google Drive please?
I heard 12.0.11.2 is the best version to do a bootloader unlock so I'm hoping someone has this one, but right now I'll be happy just to go back to Android 12.
Thanks in advance!
Click to expand...
Click to collapse
Try doing a reset of network only. That worked for me in the past with this issue.
diopskill said:
Try doing a reset of network only. That worked for me in the past with this issue.
Click to expand...
Click to collapse
Would you still happen to have the file you used for the rollback? I have tried to factory reset and it still did not help with the boot issue. I've also reported this to their support and they are working on a fix, but I am not sure how long it would take.
Edit - They fixed the link for the rollback file. I will now try to unlock the bootloader.
Edit 2 - I tried flashing unlocking the bootloader but it seems like it cannot be unlocked due to the June security patch. I am still hoping someone here has the 12.0.11.2 version firmware and it works to flashback...
hamisgood said:
Would you still happen to have the file you used for the rollback? I have tried to factory reset and it still did not help with the boot issue. I've also reported this to their support and they are working on a fix, but I am not sure how long it would take.
Edit - They fixed the link for the rollback file. I will now try to unlock the bootloader.
Edit 2 - I tried flashing unlocking the bootloader but it seems like it cannot be unlocked due to the June security patch. I am still hoping someone here has the 12.0.11.2 version firmware and it works to flashback...
Click to expand...
Click to collapse
Yes I have it ..
PD2185F_EX_A_12.0.11.2-BWDATA.W20.V000L1-update-full_1652274124.zip
drive.google.com
hamisgood said:
Would you still happen to have the file you used for the rollback? I have tried to factory reset and it still did not help with the boot issue. I've also reported this to their support and they are working on a fix, but I am not sure how long it would take.
Edit - They fixed the link for the rollback file. I will now try to unlock the bootloader.
Edit 2 - I tried flashing unlocking the bootloader but it seems like it cannot be unlocked due to the June security patch. I am still hoping someone here has the 12.0.11.2 version firmware and it works to flashback...
Click to expand...
Click to collapse
Did you download it?
diopskill said:
Yes I have it ..
PD2185F_EX_A_12.0.11.2-BWDATA.W20.V000L1-update-full_1652274124.zip
drive.google.com
Click to expand...
Click to collapse
Hi I just requested access! Many thanks for uploading it
Really strange, I am getting this error when trying to flash the package.. I'm gonna try to reboot to recovery and see if this can be flashed..
hamisgood said:
View attachment 5695503
Really strange, I am getting this error when trying to flash the package.. I'm gonna try to reboot to recovery and see if this can be flashed..
Click to expand...
Click to collapse
I flashed thru recovery. Only way it worked for me.
diopskill said:
I flashed thru recovery. Only way it worked for me.
Click to expand...
Click to collapse
Strange I can't flash through recovery, the only option I get is update through network.. Did u get to recover via "adb reboot recovery" or is there different recovery I need to access?
hamisgood said:
Strange I can't flash through recovery, the only option I get is update through network.. Did u get to recover via "adb reboot recovery" or is there different recovery I need to access?
Click to expand...
Click to collapse
I did a reset settings Not the erase all option. That did it for me
diopskill said:
I did a reset settings Not the erase all option. That did it for me
Click to expand...
Click to collapse
What I meant is this, I don't have the option to select the rom file apparently.
A few days ago I did have the option which is why I'm confused now
hamisgood said:
What I meant is this, I don't have the option to select the rom file apparently.
A few days ago I did have the option which is why I'm confused now
Click to expand...
Click to collapse
Oh...
I have that after every time I switch between beta and stable. Reset all settings fixes it every time.
diopskill said:
Oh...
I have that after every time I switch between beta and stable. Reset all settings fixes it every time.
Click to expand...
Click to collapse
Thanks! I will try resetting tonight or tomorrow if I have the time.
I do want to root (been using rooted Android since the Kindle Fire -> Galaxy S3 -> G2 -> V20 -> OP3T -> OP5T -> OP7T), but I seem to be surviving without root after blocking Ads through using AdGuard on private DNS settings.
Not being able to freeze apps on Titanium Backup is a bit of a pain but my banking apps work perfectly is pretty good upside.
hamisgood said:
Thanks! I will try resetting tonight or tomorrow if I have the time.
I do want to root (been using rooted Android since the Kindle Fire -> Galaxy S3 -> G2 -> V20 -> OP3T -> OP5T -> OP7T), but I seem to be surviving without root after blocking Ads through using AdGuard on private DNS settings.
Not being able to freeze apps on Titanium Backup is a bit of a pain but my banking apps work perfectly is pretty good upside.
Click to expand...
Click to collapse
I'm in the exact same boat. As you!! Nothing else to add lol!
diopskill said:
Try doing a reset of network only. That worked for me in the past with this issue.
Click to expand...
Click to collapse
Did reset network, all settings, but nothing helped
After I try to install A13 zip and failed of course I am receiving notification for a new version. I install this version and after another failed try of A13 is giving me the same version to download and install. And this is every time I try to install A13 I get PD2185F_EX_A_12.0.13.1.W30.
We don't recommend installing this on your main device, and especially if you're not familiar with development or alpha/beta testing. There are quite a few known issues right off the bat:
{
"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"
}
Developer Preview 1
WLAN malfunctions in certain scenarios
Connection fails when casting to a TV display
Red screen is seen when switching from Guest mode to Owner mode in certain scenarios
Manual connection fails after the phone is disconnected from the tablet
WeChat calls may not ring with Bluetooth headsets
Red screen flashes when creating a new calendar
Screen freezes when taking picture with the front camera in WhatsApp
Which devices support the preview?
OnePlus 11 (all variants except carrier-branded e.g. TMO/VZW)
Where can I get the preview?Before installing, be aware that installing a developer preview carries a risk of bricking your phone. Make sure you know what you're doing, and backup your files/media before proceeding. Also ensure your battery level is at least 30% and you have at least 5GB space left on your device.
Refer to the forum threads for more information:
OnePlus 11:
Developer Preview 1
Can I revert to the stable version of OxygenOS?Yes, please read the forum thread of your device as linked above for detailed instructions. Rolling back will completely wipe all your data, so please take a backup before proceeding.
Below is the rollback/downgrade packages for the OnePlus 11. Make sure you choose the correct rollback package for your device and region. We are providing these links purely for your convenience, as rolling back isn't natively supported by our app. After downloading the correct rollback package, move the file from the "Downloads" directory to the topmost directory of internal storage (the same directory that the "Downloads" folder is in). You may also have to rename ".jar" to ".zip".
Then, open Settings -> About device -> Version and tap "Build number" 7 times. This will enable Android's built-in "developer mode" (you might have to enter your phone's PIN/password too). Once this is done, "Local upgrade" will once again be visible in Settings -> About device -> Software update -> top-right button. It it doesn't show up, download & install OPLocalUpdate_For_Android13.apk, and use that to install updates locally.
Rollback packagesThe following packages will rollback your device to Android 13, and will wipe all your data. Note that these rollback ZIPs will take you back to A.09 even though the latest OOS13 stable version at the time of writing is A.10. These are not the packages you should download if you're looking to update to Android 14/U.
OnePlus 11 / Rollback packages :
OnePlus 11 NA Version (A.09)
OnePlus 11 IN Version (A.09)
OnePlus 11 EU Version (A.09)
OnePlus 11 GLO Version (A.09)
Thumbnail and image credits: Google/AOSP/OnePlus
Source: Oxygen updater/OnePlus firum
Rollback packages can be very helpful to convert CN Modele to IN, EU or GLO and also to be flashed to solve softbrick devices.
Init_boot_CPH2449_Android 14_DP1
Steve0007 said:
Init_boot_CPH2449_Android 14_DP1
Click to expand...
Click to collapse
do you think flashing 2449glo on my 2451 would change it to a 2449glo? or is it just the reverts that work like that?
kevp75 said:
do you think flashing 2449glo on my 2451 would change it to a 2449glo? or is it just the reverts that work like that?
Click to expand...
Click to collapse
The rollback packages are very fresh, so untill someone try, it is difficult to say.
But theoretically it could work. At least with 2551 you will be able to get full OTA updates
Steve0007 said:
The rollback packages are very fresh, so untill someone try, it is difficult to say.
But theoretically it could work. At least with 2551 you will be able to get full OTA updates
Click to expand...
Click to collapse
exactly what I was thinking lololol
In the meantime... here's CPH2451 A14 Stock and Magisk Patched init_boots
@Steve0007
Could you please rename the topic to something more understandable and manageable?
E.g. "Android 14 beta 1 (DP) for OnePlus 11"
I don't understand why you called it "Google 14" - it just makes no sense.
Thanks.
Hey finally I can convert my phone back to the US firmware.
My OP 11 is stucked/rebooting in fastboot mode after flashed 14 beta EU. Booting to black screen. Can reboot to fastboot mode.
Tried to repaired via Fastboot Enhance and roll back package with no success.. I have to ignore some partinations. Any solutions?
lassetth said:
My OP 11 is stucked/rebooting in fastboot mode after flashed 14 beta EU. Booting to black screen. Can reboot to fastboot mode.
Tried to repaired via Fastboot Enhance and roll back package with no success.. I have to ignore some partinations. Any solutions?
Click to expand...
Click to collapse
Try switching fastboot slot. This fixed for me, although it will take you back to a13
JPower123 said:
Try switching fastboot slot. This fixed for me, although it will take you back to a13
Click to expand...
Click to collapse
Thanks, fixed!
cabagekiller said:
Hey finally I can convert my phone back to the US firmware.
Click to expand...
Click to collapse
what are/were you on for firmware?
Steve0007 said:
The rollback packages are very fresh, so untill someone try, it is difficult to say.
But theoretically it could work. At least with 2551 you will be able to get full OTA updates
Click to expand...
Click to collapse
mmm... 2451 only gets incrementals. I'm testing the 2449 A.09 downgrade right now
kevp75 said:
mmm... 2451 only gets incrementals. I'm testing the 2449 A.09 downgrade right now
Click to expand...
Click to collapse
Steve0007Welp... I can confirm.
The downgrade for CPH2449 GLO for my CPH2451 US boots.
Tested: calls, texts, wifi, camera, bluetooth, etc... all work fine.
About to root, and then upgraded to A.10
kevp75 said:
Steve0007Welp... I can confirm.
The downgrade for CPH2449 GLO for my CPH2451 US boots.
Tested: calls, texts, wifi, camera, bluetooth, etc... all work fine.
About to root, and then upgraded to A.10
Click to expand...
Click to collapse
Rooted fine, and upgraded to A.10 fine... (and now I have a full OTA package! lololol)
kevp75 said:
Rooted fine, and upgraded to A.10 fine... (and now I have a full OTA package! lololol)
Click to expand...
Click to collapse
Yep, as we thought
Hi, a stupid question, will running the downgrade from color os directly works fine? ;-D
t0ng00 said:
Hi, a stupid question, will running the downgrade from color os directly works fine? ;-D
Click to expand...
Click to collapse
Most probably yes if you want to go back to Color os. There is already an Android 14 DP 1 available.
Steve0007 said:
Most probably yes if you want to go back to Color os. There is already an Android 14 DP 1 available.
Click to expand...
Click to collapse
Sorry for not making myself clear, I mean, downloading the apk from the forum and take it to a CN color os device and forcefully "downgrade" it to the 13 ROM - could it be even possible?
Or forcefully for to DP1 NA first and then, down?