Hello from Ukraine, guys.
So now I'm on last global A11 2125 with root (magisk), custom recovery (twrp) and the last custom kernel blu_spark.
So how can I update to the last c47 via OTA without data loss.
As I know twrp and blu_spark kernel doesn't support android 12.
Thanks for help.
I needed to update to A12 recently when I was on Arter's kernel and also had twrp. Youll need to return to stock A11, for me I just flashed stock boot.img vendor_boot.img and dtbo.img and then updated normally through oxygen updater. I'm assuming blu spark modifies different things so just check how to return to stock and then you should be fine to update as usual.
Zesty59 said:
I needed to update to A12 recently when I was on Arter's kernel and also had twrp. Youll need to return to stock A11, for me I just flashed stock boot.img vendor_boot.img and dtbo.img and then updated normally through oxygen updater. I'm assuming blu spark modifies different things so just check how to return to stock and then you should be fine to update as usual.
Click to expand...
Click to collapse
Did you flash it using fastboot? Where did you get this files? Did you flash stock recovery or not?
Sergykm said:
Did you flash it using fastboot? Where did you get this files? Did you flash stock recovery or not?
Click to expand...
Click to collapse
Yeh i flashed it with fastboot, i just downloaded the Oxygen os version i was on (theres a repo on xda) and unpacked the payload.bin. Theres a lot of methods for doing so that you can find on google.
Zesty59 said:
Yeh i flashed it with fastboot, i just downloaded the Oxygen os version i was on (theres a repo on xda) and unpacked the payload.bin. Theres a lot of methods for doing so that you can find on google.
Click to expand...
Click to collapse
Thanks for the answer, mate) Have a nice day
Sergykm said:
Thanks for the answer, mate) Have a nice day
Click to expand...
Click to collapse
No worries
Related
i am assuming now that i have installed twrp, i cannot install the new Oxygen OS update, is that correct and i will have to wait for a twrpable update or stock recovery is available to flash? thank u
wondering the same
Bradl79 said:
i am assuming now that i have installed twrp, i cannot install the new Oxygen OS update, is that correct and i will have to wait for a twrpable update or stock recovery is available to flash? thank u
Click to expand...
Click to collapse
gkillerx said:
wondering the same
Click to expand...
Click to collapse
Flash the full zip 3.1.2 available here:
https://www.androidfilehost.com/?fid=24591020540821926
Flash SuperSu after this to maintain root
Funk Wizard said:
Flash the full zip 3.1.2 available here:
https://www.androidfilehost.com/?fid=24591020540821926
Flash SuperSu after this to maintain root
Click to expand...
Click to collapse
The question is, can we use ATO with TWRP installed?
Only custom roms have OTA available with TWRP installed.
gkillerx said:
The question is, can we use ATO with TWRP installed?
Click to expand...
Click to collapse
Oxygen Os fails to install the OTA when detected root ot any changes to system patrition, thus you have to wait for the full zip and dirty flash over the existing. Fairly simple.
I can still do a nandroid backup and restore stock OxygenOS, correct?
Funk Wizard said:
Flash the full zip 3.1.2 available here:
https://www.androidfilehost.com/?fid=24591020540821926
Flash SuperSu after this to maintain root
Click to expand...
Click to collapse
Thank u! Can I do a clean install with the zip or is it update only, also if I go to cm13 can I just clean flash that zip to go back to stock or do I have to get the firmware somewhere
Bradl79 said:
Thank u! Can I do a clean install with the zip or is it update only, also if I go to cm13 can I just clean flash that zip to go back to stock or do I have to get the firmware somewhere
Click to expand...
Click to collapse
You can clean flash. It is a full zip. I have restricted access to it now as I don't see anyone getting the OTA. So, it might be a mistake build. Lol.
Sent from my OnePlus2 using XDA Labs
yeah i can't get it now anymore either, is there anyway someone can post a mirror link
Bradl79 said:
yeah i can't get it now anymore either, is there anyway someone can post a mirror link
Click to expand...
Click to collapse
OxygenOS 3.1.2 http://downloadmirror.co/android/2zUL/OnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a.zip.
gee2012 said:
OnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a.zip https://drive.google.com/file/d/0B6Ufgy16r712WjNHUXBQdC1pNjA/view?usp=sharing or from here http://downloadmirror.co/android/2zUL/OnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a.zip.
Click to expand...
Click to collapse
Hey @gee2012,
I'm on PA's 6.0.1 build right now, looking for a stock OOS ROM, newer the better. Can I flash this zip through TWRP? Just need to get back to stock somehow.
Thankyou.
chr0 said:
Hey @gee2012,
I'm on PA's 6.0.1 build right now, looking for a stock OOS ROM, newer the better. Can I flash this zip through TWRP? Just need to get back to stock somehow.
Thankyou.
Click to expand...
Click to collapse
No, you need to flash the stock recovery.img in fastboot first and then you can flash the zip in recovery/flash from local.
gee2012 said:
No, you need to flash the stock recovery.img in fastboot first and then you can flash the zip in recovery/flash from local.
Click to expand...
Click to collapse
Much appreciated. Could you also link me to the stock recovery?
chr0 said:
Much appreciated. Could you also link me to the stock recovery?
Click to expand...
Click to collapse
I`am looking for it myself atm, so i can`t help you with that i`am afraid
I (call me moron) am bricked (TWRP is installed) and looking for stock recovery also. Could someone post it, please? Otherwise I'm unable to flash a stock ROM. (TWRP does flash it, but after that it says "No OS installed".)
At least I have to wait for my new SIM cards for a few days anyway, so... never mind...
hasenbein1966 said:
I (call me moron) am bricked (TWRP is installed) and looking for stock recovery also. Could someone post it, please? Otherwise I'm unable to flash a stock ROM. (TWRP does flash it, but after that it says "No OS installed".)
At least I have to wait for my new SIM cards for a few days anyway, so... never mind...
Click to expand...
Click to collapse
Nandroid ?
Funk Wizard said:
Nandroid ?
Click to expand...
Click to collapse
Obviously that's why you can call me a moron - obviously I didn't do a Nandroid
hasenbein1966 said:
Obviously that's why you can call me a moron - obviously I didn't do a Nandroid
Click to expand...
Click to collapse
At least you have a problem that can be solved I posted a request for the stock recovery.img so maybe will upload it.
lol i guess everyone got excited and just installed TWRP off the bat, now that i have learned to pull .img files, its too late for me since i installed twrp instead of booting up, there has to be someone who had done it, i wonder why no is providing it, its a simple task.
Hi,
I want to go from a fully rooted OP3 to stock and then do a system-less root so I can receive OTA updates without problems.
I've already removed the non system-less SuperSU but I have to flash the stock images and forgot to back them up before rooting :fingers-crossed:.
I am on OxygenOS 3.1.2 and believe I need the following images:
recovery.img
system.img
boot.img
Can someone upload theirs for me? :highfive:
AeonLucid said:
Hi,
I want to go from a fully rooted OP3 to stock and then do a system-less root so I can receive OTA updates without problems.
I've already removed the non system-less SuperSU but I have to flash the stock images and forgot to back them up before rooting :fingers-crossed:.
I am on OxygenOS 3.1.2 and believe I need the following images:
recovery.img
system.img
boot.img
Can someone upload theirs for me? :highfive:
Click to expand...
Click to collapse
3.1.2 original firmware
https://s3.amazonaws.com/oxygenos.o...6_OTA_007_all_1606062247_8f031965d7db4420.zip
3.1.2 original recovery
https://s3.amazonaws.com/oxygenos.oneplus.net/recovery.img
angelsanges said:
3.1.2 original firmware
3.1.2 original recovery
Click to expand...
Click to collapse
Thanks, but how do I extract the required images from the original firmware?
Edit: Nevermind. I flashed the original firmware with TWRP and flashed the original recovery after that. Should be okay now.
Thanks!
AeonLucid said:
Thanks, but how do I extract the required images from the original firmware?
Edit: Nevermind. I flashed the original firmware with TWRP and flashed the original recovery after that. Should be okay now.
Thanks!
Click to expand...
Click to collapse
Really, you ought to flash the stock recovery first, but that's a technicality. If TWRP worked for you, then great :good:
Hey all! I'm trying to root my OnePlus 7t but I'm on 10.0.5 stock and I can't find a patched boot.img, or even a stock one to patch in Magisk. I'm on the global variant. If someone could point me in the right direction, that would be grand. I have already read mostly all the posts...
I have the US version which I think is also the global version. Here's my patched boot.img for 10.0.5
https://drive.google.com/file/d/12tZN5D7dmovIeqsx8sTF-B0z2gxA6LG8/view?usp=sharing
Here's the stock boot for 10.0.5 as well if you screw something up.
https://drive.google.com/file/d/1nS0hqVCyntXHjbTzOH7H8-b29-IlAOIt/view?usp=sharing
Don't ask why the file sizes are so different. It just gets smaller for some reason after patching it in magisk.
I just booted with an older one and flashed the latest magisk
Need 10.0.5 boot.img stock & magisk patched for indian varient
Hey .... Can you help me with the 10.0.5 boot.img , stock & magisk patched for indian varient HD1901 of 7t
ChongoDroid said:
I just booted with an older one and flashed the latest magisk
Click to expand...
Click to collapse
I had tried booting with 10.0.3 while on 10.0.5 , Did not turn out well .
Has anyone on 10.0.5 tried booting w/ the above 10.0.5 patched img ?
Stock and Magisk patched boot.img files for HD1905 7T update version 10.0.5:
dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0
SkippRunning said:
Stock and Magisk patched boot.img files for HD1905 7T update version 10.0.5:
dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0
Click to expand...
Click to collapse
Do I only need to flash the patched img or both ?
And do they need to be flashed to both A and B slots ?
Thanks for sharing
hightech316 said:
Do I only need to flash the patched img or both ?
And do they need to be flashed to both A and B slots ?
Thanks for sharing
Click to expand...
Click to collapse
I would try fastboot boot before you use fastboot flash just to make sure that the device will boot successfully with the images. You should only need to fastboot boot magisk_patched.img, then open Magisk Manager and install Magisk by choosing the direct install option in the list. You only need the steps I mentioned to have root, and if you flash it to A and B at once you can get stuck in a bootloop. I had that happen at one point from flashing both partitions, and I dont recommend trying it.
SkippRunning said:
I would try fastboot boot before you use fastboot flash just to make sure that the device will boot successfully with the images.
Click to expand...
Click to collapse
Thanks , this can save a headache !
hightech316 said:
Thanks , this can save a headache !
Click to expand...
Click to collapse
Ya, I tried every relevant boot image I could find in the forums, and the device didnt work properly with any of them. The only one that allowed the device to boot successfully caused the wifi and sounds to not work. So I downloaded the full update from OnePlus and extracted it to a folder, then used payload dumper to extract all of the individual images out of the payload.bin file from OnePlus. I copied the boot.img into the phone storage and installed Magisk Manager, then patched the stock boot.img and copied it from the phone to my pc. Then I used fastboot boot magisk_patched.img to make sure the image I made would work. I booted the device and inside Magisk Manager I chose direct install in the list of options and everything went smoothly, and I didnt need to rely on finding images online that would hopefully work.
smokeythebear3 said:
I have the US version which I think is also the global version. Here's my patched boot.img for 10.0.5
https://drive.google.com/file/d/12tZN5D7dmovIeqsx8sTF-B0z2gxA6LG8/view?usp=sharing
Here's the stock boot for 10.0.5 as well if you screw something up.
https://drive.google.com/file/d/1nS0hqVCyntXHjbTzOH7H8-b29-IlAOIt/view?usp=sharing
Don't ask why the file sizes are so different. It just gets smaller for some reason after patching it in magisk.
Click to expand...
Click to collapse
Thanks a bunch for the share. That was the missing piece that I've been looking for. I have the HD1905 variant and I just used Magisk to patch the stock file you provided. After testing, I'm finally rooted. Thanks again.
I recently bought a Chinese phone from a relatively unknown manufacturer, so I was unable to find any TWRP images that match the device, I was wondering if it was possible to extract the boot image directly from a GSI ROM. My end goal is to install Magisk so if there is a better way to go about this please let me know.
can you tell model and brand
Hsnmastoor said:
can you tell model and brand
Click to expand...
Click to collapse
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.
XDA-Developer30 said:
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.
Click to expand...
Click to collapse
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter
Hsnmastoor said:
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter
Click to expand...
Click to collapse
Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek
If you wish to root your Mediatek Android phone, we'd dropped a guide on rooting using Magisk and stock boot.img at https://www.hovatek.com/forum/thread-21427.html , no custom recovery is required. Se
forum.hovatek.com
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
Thank you for the reply, I forgot to mention that I used Hsnmastoor's method successfully.
LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?
elmapq said:
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?
Click to expand...
Click to collapse
And your device is...???
LinhBT said:
And your device is...???
Click to expand...
Click to collapse
Tecno Spark 6 ke7
LinhBT said:
And your device is...???
Click to expand...
Click to collapse
I have a Vortex V22 MTM6761 There is no stock rom. It has unofficial GSI Pixel experience plus 13.0 running on it. I too would like to root. How can I retrieve the boot.img file from the GSI rom? Or how can I pull it from the phone via terminal and fastboot? All help is greatly appreciated! Happy Saint Patricks Day!
For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device
LinhBT said:
For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device
Click to expand...
Click to collapse
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?
defcondoc said:
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?
Click to expand...
Click to collapse
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!
.
LinhBT said:
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!
Click to expand...
Click to collapse
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!
defcondoc said:
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!
Click to expand...
Click to collapse
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.
LinhBT said:
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.
Click to expand...
Click to collapse
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?
I have 2 models I cannot find stock ROM's for:
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB - manufacture date year 2022
Moxee M2160 Model MH-T6000 2APQU-MH-T6000 Q6006_V1.0 - manufacture date year 2022
Can anyone find anything? I have scoured the web for months!
I can't believe there is nothing available for these phones.
Please let me know if you can find a stock ROM. I would love to learn where and how you found them. As I've have found nothing for months and months.
Thank you!!!
defcondoc said:
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?
Click to expand...
Click to collapse
You CAN extract the boot.img via terminal ONLY IF you're on a ROOTED devices!
Currently on CN MR2 version of JOYUI 12.5. Using the old TWRP for Android 10 only shows black screen when booting up via "fastboot boot twrp.img" then reboots normally to the system preventing me to pull the stock boot for MR2, make backups via TWRP to proceed with rooting the device. Any help would be appreciated.
Here's the recovery.img I've extracted from Payload.bin for the latest CN MR2 update. Hopefully someone can patch a TWRP img for this. And feel free to ask if you guys need more img files from the latest update.
hi bro..
may you want to get ota link of update rom. use adb to get the link. the guide is also on this forum.. thank you..
Jhem OP5 said:
Here's the recovery.img I've extracted from Payload.bin for the latest CN MR2 update. Hopefully someone can patch a TWRP img for this. And feel free to ask if you guys need more img files from the latest update.
Click to expand...
Click to collapse
Tried to flash over mr0 to update but bootloop