Need Insight On A/B Slots - Newly Unlocked Bootloader - OnePlus 7 Pro Questions & Answers

I now have two OnePlus 7 Pro mobile devices. One is my 'daily driver', and through pure dumb luck and perseverence I have it setup exactly the way I want it with Resurrection Remix 8.6.7, Magisk, and TWP. I take regular TWRP backups, and save them to my NAS. Because RR has released new version(s), and the last one took a day of mucking about with a near-bricked device, screwed up everything on the device - started with hang system on boot animation, etc... lost TWRP, lost Magisk,.. I decided to buy a second OnePlus 7 Pro as a 'sandbox' to learn what I need to know to make working changes to my 'daily driver' without having no mobile device for a day or more.
Today's goal was: Take the TWRP backup from the 'daily driver' device and restore it to the new device with unlocked bootloader. Simple.
So, I booted into fastboot mode. On the PC, I typed: fastboot boot twrp-3.5.2_9-0-guacamole.img
This did not work. At all. Why? I don't want someone to just tell me what I did wrong or what I need to do. I want someone to explain WHY I need to do something different and WHY what I did here did not work?
From here, I have no idea how I managed to get TWRP to run, but I can indeed get it to run. Once I did, I copied the backup directory to the device and tried to restore it in TWRP. I assume(!) that a TWRP backup is a full byte-for-byte image of the storage system. Needless to say, I could not restore the image with TWRP. Why? What is going on here? What did I do wrong? What do I need to do differently, but more importantly WHY do I need to do something different?
At this point, I can get TWRP to run, but only if I set the current slot to B. If set to A, I cannot boot the TWRP image from PC. Why? Why does the active slot affect whether the device can boot the recovery image from an external file?
Thank you for anyone who can provide the insight I am desperately looking for!

You're better off just backing up the ROM on the older device using the Seedvault app then restoring after a fresh install.

Is that twrp.img a 3X Mb file from official website?
I failed with that and I found another twrp.img which is 9X mb and work
which is this:
Downloads for : OnePlus OnePlus 7 Pro | 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.
androidfilehost.com

hkdoublecat said:
Is that twrp.img a 3X Mb file from official website?
I failed with that and I found another twrp.img which is 9X mb and work
which is this:
Downloads for : OnePlus OnePlus 7 Pro | 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.
androidfilehost.com
Click to expand...
Click to collapse
That TWRP image is twrp-3.5.2_9-0-guacamole.img and it is about 33.2 MB. It is from the official Team Win web site at this address: https://dl.twrp.me/guacamole
That is the only place you should be getting TWRP from as far as I know.

Alpha_Geek1 said:
That TWRP image is twrp-3.5.2_9-0-guacamole.img and it is about 33.2 MB. It is from the official Team Win web site at this address: https://dl.twrp.me/guacamole
That is the only place you should be getting TWRP from as far as I know.
Click to expand...
Click to collapse
i know, but it doesnt work. when i use it, my screen come up with blank oneplus logo and word fastboot mode. nothing else happen.

hkdoublecat said:
i know, but it doesnt work. when i use it, my screen come up with blank oneplus logo and word fastboot mode. nothing
else happen.
Click to expand...
Click to collapse
I had the same problem. I did a number of 'random' things because - again - I can't find anyone to explain enough for me to actually know what I need to do and why I need to do it at any given point, much less definitively answer any of my questions here on XDA.
I think one of the things I did (not sure) that may have gotten me over that hump was to switch active slot with a fastboot command: fastboot active_slot = b or something like that. I think I also did some commands like fastboot flash boot_a twrp_blah_version.img and fastboot flash boot_b twrp_blah_version.img. I literally just kept trying different things until I was able to boot the external recovery image file.
I have no earthly idea why booting the external recovery image doesn't immediately work after unlocking the bootloader. Maybe someday before the sun turns into a cold hard lump of nickel and iron someone on XDA will provide complete detailed answers to my questions (above, https://forum.xda-developers.com/t/questions-on-using-twrp-and-a-b-slot-switching.4286595/, https://forum.xda-developers.com/t/255-error-with-twrp-backup-restore-999.3801632/post-85379577). Until then, I believe we're stuck with wild-ass guesses, conjecture, and borderline superstition - all the plightful domain of ignorance.

Related

Installed TWRP to Boot, want to boot myself in the a**.

Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Thank you, the tool worked like a charm.
BTW: I did search and find other "methods" but none of them worked
noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.
MrSteelX said:
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.
Click to expand...
Click to collapse
That is exactly what I wanted to do.
I could get into TWRP, but I couldn't see the phone on the PC and couldn't move files (ROM) to the phone (although fastboot was working and I could see the device using adb) but I couldn't figure out how to have TWRP look for or find the ROM on the PC.
There's no recovery partition on A/B phones remember.
RusherDude said:
There's no recovery partition on A/B phones remember.
Click to expand...
Click to collapse
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.
noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/
MrSteelX said:
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.
Click to expand...
Click to collapse
Thanks.
I will give this a try. After I learn a little more about the A/B partitions & recovery on this phone, I want to try one on the custom ROMs.
pankspoo said:
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/
Click to expand...
Click to collapse
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).
noncomjd said:
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).
Click to expand...
Click to collapse
I have to unzip the downloaded fastboot ROM at any folder on computer and open that folder u will see named [flash all bat]
Now connect phone in fastboot mode to computer and just click [flash all bat] file
noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.
RusherDude said:
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.
Click to expand...
Click to collapse
Thanks for the information.
and this is what I did, originally I thought I had accidentally selected the wrong partition, but it seems since there is no recovery partition, I did it wrong from the start.
Q: I'm guessing this is why when you do load TWRP (the correct way, which I did once, following a guide) without a custom ROM (still using Oxygen OS) that the OEM recovery overwrites TWRP or the OEM recovery is called up at the next reboot into recovery?
Q: I understand, at least in theory the benefit of the A/B partitions, what is the benefit of eliminating the recovery partition other than giving more control of the phone to the OEM and OS? Is this setup limited to the stock kernel or mandated to be copied by any potential replacement kernels (this information is new to me, I haven't yet read up on kernels).

[Guide]Alcatel Idol 5 6060C Bootloader Unlock and TWRP[/Guide]

New From A-TEAM: lehmancurtis147​
ALCATEL IDOL 5 : 6060C​ACCESS FASTBOOT
UNLOCK BOOTLOADER
INSTALL TWRP
Special thanks to the mVirus Team for the reboot tool.
Ok, here we go!!!
Start fastboot:
1.*Unpack and launch the boot mode tool.
2.*Power off your 6060C.
3.*While holding vol- plug in device to PC.
4.*While continuing to hold vol- press power until the device starts and release power (not vol-).
5.*Once you see fastboot at the bottom of the device you can release vol-.
Unlock Bootloader:
Now that you are in fastboot mode, we need to unlock the bootloader.
Code:
fastboot oem unlock
Install Custom Recovery:
I forgot to mention I also built a working TWRP.img for this device.
1.*Unzip the recovery.zip.
2.*To install it.
Code:
fastboot flash recovery recovery.img
3.*then...
Code:
fastboot oem reboot-recovery
4.*Welcome to team win recovery!
DOWNLOADS:
This is the boot-mode tool:
https://androidforums.com/attachments/mtk-bootmode-tool-zip.153347/
twrp link:
https://drive.google.com/file/d/1teI23ASm2IbIy_r4xV0jlzz_TzS3cvTc/view?usp=sharing
NOTE:
Unless you remove verity (and a handful of other annonyances) you will loose twrp. Luckily, I've already built a replacement system.img to solve this. Once its working right I'll share it.
I have the system image working, but it's huge. Probably why system and vendor were split in android 8. It's a 4.6 gigabyte image so as soon as I decide the best way to host it I will post it.
In the mean time, the way to keep updated is our telegram group.
A-Team General Discussion
Anything Alcatel, AIO ToolKit, Android, CricketRom
https://t.me/Android_General_Chat
Recoveries
!!!ANNOUNCEMENT!!!
New Recovery Options Available​
I now have managed to build a fully functional Pitch Black Recovery Image and and Orange Fox Recovery Image (the later is built from mostly 9.0 branch) and will be making them available soon if I see that anyone is actually interested.
The recovery image files are compiled from source and not a Frankenstein type. So I can address any recovery issues (within the scope of reason).
Thanks for the thread!! I don't have this device but to my amazement, this utility booted my Alcatel 3t 8 tablet into fastboot mode and I was bootloader unlocked in seconds! I can't thank you enough. This tool should be shared around. It may just be the key to unlocking the bootloader on a plethora of 2018+ MTK devices.
mickeybeats said:
Thanks for the thread!! I don't have this device but to my amazement, this utility booted my Alcatel 3t 8 tablet into fastboot mode and I was bootloader unlocked in seconds! I can't thank you enough. This tool should be shared around. It may just be the key to unlocking the bootloader on a plethora of 2018+ MTK devices.
Click to expand...
Click to collapse
Hi mickeybeats, I happen to have the Alcatel 3t 8 as well! I've been looking for a copy of the stock ROM/firmware everywhere and I'm unable to find it. Is it possible that you have a copy/know where I could download it? My tablet starting throwing up the feared "System UI has stopped" error and it seems reflashing stock ROM is the only way to fix it
I can confirm that the bootloader thing works for the 6058D model (MTK 6753)
For stock ROMs on Alcatel mtk devices, you need Sugar-mtk from Alcatel. It goes through the reflash process and as a bonus you can grab the firmware file from inside the flash tools program folders. The files don't use human readable formatting for the names but they end in either .bin or .mbn. A once over with a hexeditor should be enough to get a general idea of what they are. All the ones I've delt with had the boot.img label with a b at the beginning of the name and r for recovery, but gets a bit scattered from there.
stevegsames said:
I can confirm that the bootloader thing works for the 6058D model (MTK 6753)
Click to expand...
Click to collapse
Post your boot.img if you don't already have a custom recovery and I will build one for yours.
lehmancurtis said:
Post your boot.img if you don't already have a custom recovery and I will build one for yours.
Click to expand...
Click to collapse
I did make one, thank you though. If anyone's interested, here it is:
Idol 5 6058D TWRP
So, I recently revisited this phone and saw that there was a new exploit to access the bootloader. I tried it and it worked. After some time of trial and error, I was able to dump the stock recovery. With this, I started to port TWRP to it. This...
forum.xda-developers.com
stevegsames said:
I did make one, thank you though. If anyone's interested, here it is:
Idol 5 6058D TWRP
So, I recently revisited this phone and saw that there was a new exploit to access the bootloader. I tried it and it worked. After some time of trial and error, I was able to dump the stock recovery. With this, I started to port TWRP to it. This...
forum.xda-developers.com
Click to expand...
Click to collapse
Good to hear.
Hi all!
Is there anything similar to 'boot-mode too'l for Linux machines?
What would be a proper command-foo for this task?
The usual method with adb/fastboot obviously doesn't work with
Alcatel IDOL 5 (6058D/MT6753).
To install TWRP on Alcatel Idol 5, you first need to unlock the bootloader.The process is a bit more involved for this device than it is on most others.
Click to expand...
Click to collapse
Thanks!
elocnix said:
Hi all!
Is there anything similar to 'boot-mode too'l for Linux machines?
What would be a proper command-foo for this task?
The usual method with adb/fastboot obviously doesn't work with
Alcatel IDOL 5 (6058D/MT6753).
Thanks!
Click to expand...
Click to collapse
I don't know if it will work with wine. But you should be able to run it from a VM.
Don't be a idiot like me and accidently flash the recovery image on the Alcatel 3T 8. it will permanently brick the device and sugar-mtk will not restore .

Coming from an OP3T need help regarding the new partitions

I own a 3T currently and am planning to get an 8T as it is getting good custom rom traction. One thing I am really confused about the is the new partitioning scheme. Can someone please link me an article where I can read more about it? Also what's with the specific twrp's and installer zips for each rom and how does one flash magisk, xposed and other things?
What I am used to doing on my 3t is, wipe data, system, cache and then flash rom zip + gapps + magisk. I would really appreciate it if anyone can explain the additional steps that would be required to do this on the 8T
It's a very different world with the 8T (I also come from a 3T).
The 8T has A/B partitions as well as virtual A/B partitions. It also supports streaming OTA and seamless OTA updates. It has fastboot and fastbootd.
There's lots of good information on all of this in:
Virtual A/B Overview | Android Open Source Project
source.android.com
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
platform/system/update_engine - Git at Google
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
And more on this at the same site.
And, if you get into serious trouble, the unbricking tool is really easy to use and works wonderfully.
pratyush28 said:
I own a 3T currently and am planning to get an 8T as it is getting good custom rom traction. One thing I am really confused about the is the new partitioning scheme. Can someone please link me an article where I can read more about it? Also what's with the specific twrp's and installer zips for each rom and how does one flash magisk, xposed and other things?
What I am used to doing on my 3t is, wipe data, system, cache and then flash rom zip + gapps + magisk. I wouls really appreciate it if anyone can explain the additional steps that would be required to do this on the same thing on an 8T.
Click to expand...
Click to collapse
I'm going to try to give you a brief, yet precise enough guide to doing the basics on a device with partitions like the 8T.
Okay, so basically, the 8T custom ROMs, when flashed, are going to consist of the following partitions:
boot
dtbo
system
system_ext
product
recovery
vendor
odm
vbmeta
vbmeta_system
So when performing fastboot/adb commands with these newer devices, you're going to start off in the normal bootloader (i use the volume +/- and power at the same time command to enter this from a powered off state).
Now there's also a mode called fastbootd mode. It's often just called fastboot, especially when booting from bootloader (fastboot reboot fastboot now takes you to this fastbootd mode). This is where you're going to do the majority of flashing/modding from.
So to start off, enter bootloader, then perform this command in terminal to do a wipe of data:
fastboot -w
Then, flash recovery partition:
fastboot flash recovery recovery.img (this is the recovery.img from the ROM zip you are attempting to flash)
Then, reboot to fastbootd:
fastboot reboot fastboot
Next, I like to make sure I'm on partition A for flashing. This is just something I've been told to do and it works so I stick with it. So do this by:
fastboot set_active a
Now you can start flashing the paritions:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
Then, boot up the ROM:
fastboot reboot
So that's the basic rundown.
Now for a few things to keep in mind:
Always make sure you're on the latest version of OxygenOS before doing any of this. I like to start off by unlocking bootloader, then setting up phone. Then I do an update to both partitions to the latest version of OOS (must be on both partitions. Not just on one). So I just put the latest OOS zip on my phone via USB transfer from PC, do an upgrade with that file (Settings > System > Update > Top right menu button > Select Internal Storage or whatever it says like that, then select the file (make sure the OOS zip file is in the MAIN root directory of your phone. So basically, the folder that contains the Pictures, Downloads, Music, etc. folders.
So after you do this system update, it will prompt you to reboot phone. Do this. Then, go to settings and do the same thing again. Select the OOS zip and do an internal storage update, let it do its thing, it'll ask to reboot, go ahead and do so. Now this second update you do will either start from 0% and go to 100% like the first time, or it will go from 0% directly to 99%, then 100% after a few seconds. This is okay, it just means you already had the latest OOS on one of your partitions. So anyway, go ahead and do that reboot when it tells you. Now you are unlocked and on the latest firmware and ready to flash.
Oh, and btw, to unlock bootloader, do the normal steps through developer options, then reboot to bootloader and this is the command used:
fastboot flashing unlock
That will let you confirm to unlock bootloader, etc. like I'm sure you've done on the 3T.
So anyway, after unlocking and updating to latest OOS (Open Beta or Stable usually both work fine btw), you can reboot to bootloader, then do the steps I told you above for wiping, flashing recovery, flashing partitions, booting, etc.
Oh, and to get these partition images from the custom ROM zip you choose to flash, you need to first unzip the ROM zip file, then take the payload.bin file that will result of the unzip, and use a payload_dumper script. Those are linked all over or can be found on a google search or Github. It'll take your payload.bin and turn it into these .IMG files that I list in the flashing steps. Each partition will have a file named PARTITIONNAME.img. These are all you need to flash a custom ROM over OOS.
To flash an update to a rom, do all the same stuff but don't do the
fastboot -w
and you also don't need to do the
fastboot flash recovery recovery.img
part because the recovery partition is already there from the ROM when you originally flashed.
I realize this is all a bunch of random notes and guides, and my brain kind of works in a weird way, but it's pretty much all there I think. If you need help clarifying any of this or just have any questions in general, PM me or respond back here and tag me. I'll help as much as I can or point you to someone who can help if I can't.
Hope this helps. Take care.
dpryor88 said:
I'm going to try to give you a brief, yet precise enough guide to doing the basics on a device with partitions like the 8T.
Okay, so basically, the 8T custom ROMs, when flashed, are going to consist of the following partitions:
boot
dtbo
system
system_ext
product
recovery
vendor
odm
vbmeta
vbmeta_system
So when performing fastboot/adb commands with these newer devices, you're going to start off in the normal bootloader (i use the volume +/- and power at the same time command to enter this from a powered off state).
Now there's also a mode called fastbootd mode. It's often just called fastboot, especially when booting from bootloader (fastboot reboot fastboot now takes you to this fastbootd mode). This is where you're going to do the majority of flashing/modding from.
So to start off, enter bootloader, then perform this command in terminal to do a wipe of data:
fastboot -w
Then, flash recovery partition:
fastboot flash recovery recovery.img (this is the recovery.img from the ROM zip you are attempting to flash)
Then, reboot to fastbootd:
fastboot reboot fastboot
Next, I like to make sure I'm on partition A for flashing. This is just something I've been told to do and it works so I stick with it. So do this by:
fastboot set_active a
Now you can start flashing the paritions:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
Then, boot up the ROM:
fastboot reboot
So that's the basic rundown.
Now for a few things to keep in mind:
Always make sure you're on the latest version of OxygenOS before doing any of this. I like to start off by unlocking bootloader, then setting up phone. Then I do an update to both partitions to the latest version of OOS (must be on both partitions. Not just on one). So I just put the latest OOS zip on my phone via USB transfer from PC, do an upgrade with that file (Settings > System > Update > Top right menu button > Select Internal Storage or whatever it says like that, then select the file (make sure the OOS zip file is in the MAIN root directory of your phone. So basically, the folder that contains the Pictures, Downloads, Music, etc. folders.
So after you do this system update, it will prompt you to reboot phone. Do this. Then, go to settings and do the same thing again. Select the OOS zip and do an internal storage update, let it do its thing, it'll ask to reboot, go ahead and do so. Now this second update you do will either start from 0% and go to 100% like the first time, or it will go from 0% directly to 99%, then 100% after a few seconds. This is okay, it just means you already had the latest OOS on one of your partitions. So anyway, go ahead and do that reboot when it tells you. Now you are unlocked and on the latest firmware and ready to flash.
Oh, and btw, to unlock bootloader, do the normal steps through developer options, then reboot to bootloader and this is the command used:
fastboot flashing unlock
That will let you confirm to unlock bootloader, etc. like I'm sure you've done on the 3T.
So anyway, after unlocking and updating to latest OOS (Open Beta or Stable usually both work fine btw), you can reboot to bootloader, then do the steps I told you above for wiping, flashing recovery, flashing partitions, booting, etc.
Oh, and to get these partition images from the custom ROM zip you choose to flash, you need to first unzip the ROM zip file, then take the payload.bin file that will result of the unzip, and use a payload_dumper script. Those are linked all over or can be found on a google search or Github. It'll take your payload.bin and turn it into these .IMG files that I list in the flashing steps. Each partition will have a file named PARTITIONNAME.img. These are all you need to flash a custom ROM over OOS.
To flash an update to a rom, do all the same stuff but don't do the
fastboot -w
and you also don't need to do the
fastboot flash recovery recovery.img
part because the recovery partition is already there from the ROM when you originally flashed.
I realize this is all a bunch of random notes and guides, and my brain kind of works in a weird way, but it's pretty much all there I think. If you need help clarifying any of this or just have any questions in general, PM me or respond back here and tag me. I'll help as much as I can or point you to someone who can help if I can't.
Hope this helps. Take care.
Click to expand...
Click to collapse
I cannot thank you enough for taking out so much time and explaining everything in detail. I really appreciate it and this will be very very helpful for me.
Unfortunately, I purchased the 8T from OnePlus' official website and they sent me a refurbished piece with a cracked back panel and scratched screen. I was stupid to opt for OnePlus' site just because there was a small discount, now to get a replacement I have to go through a painful process of contacting their incompetent support and an eternal wait until they decide to revert. I'm glad that I recorded the unboxing video, so at least they cannot blame this on me.
pratyush28 said:
I cannot thank you enough for taking out so much time and explaining everything in detail. I really appreciate it and this will be very very helpful for me.
Unfortunately, I purchased the 8T from OnePlus' official website and they sent me a refurbished piece with a cracked back panel and scratched screen. I was stupid to opt for OnePlus' site just because there was a small discount, now to get a replacement I have to go through a painful process of contacting their incompetent support and an eternal wait until they decide to revert. I'm glad that I recorded the unboxing video, so at least they cannot blame this on me.
Click to expand...
Click to collapse
Ah man! I'm so sorry to hear that! Their support is horrible I must admit. Not as bad as Google Fi's support haha (that's another story), but it's bad yeah.
I got mine from the OP website also (North America model as I live in California) but I got it shortly after the phone was released. I can't believe they're selling refurbished, broken devices now. That's horrible. The company has been going a bit downhill with some aspects I've realized in the past few years.
Anyway, I really hope you get that sorted out (sooner than later hopefully). It's a nice device. Software support/updates are a little iffy with OP these days, but no one's perfect. But once you start flashing some custom goodness on the phone, it really shines. Nothing wrong with Oxygen in my opinion, but choice is nice
Let me know if/when you get the device if you need any help with anything.
dpryor88 said:
Ah man! I'm so sorry to hear that! Their support is horrible I must admit. Not as bad as Google Fi's support haha (that's another story), but it's bad yeah.
I got mine from the OP website also (North America model as I live in California) but I got it shortly after the phone was released. I can't believe they're selling refurbished, broken devices now. That's horrible. The company has been going a bit downhill with some aspects I've realized in the past few years.
Anyway, I really hope you get that sorted out (sooner than later hopefully). It's a nice device. Software support/updates are a little iffy with OP these days, but no one's perfect. But once you start flashing some custom goodness on the phone, it really shines. Nothing wrong with Oxygen in my opinion, but choice is nice
Let me know if/when you get the device if you need any help with anything.
Click to expand...
Click to collapse
Thanks mate, I won't hesitate to ask if I need help once I get the new device
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
pratyush28 said:
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
Click to expand...
Click to collapse
I have the other model. Unbrick tool works fine on mine.
pratyush28 said:
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
Click to expand...
Click to collapse
My 8T has ddr_type of 1 and I've had no problems using the unbrick tool (and I've used it a lot as I've been testing/learning lots of stuff with TWRP) on my KB2000.
BillGoss said:
My 8T has ddr_type of 1 and I've had no problems using the unbrick tool (and I've used it a lot as I've been testing/learning lots of stuff with TWRP) on my KB2000.
Click to expand...
Click to collapse
That's some good news, mine is KB2001 I wonder if that will make a difference. Also, have you tried flashing custom roms? If yes, was there any firmware incompatibility?
pratyush28 said:
That's some good news, mine is KB2001 I wonder if that will make a difference. Also, have you tried flashing custom roms? If yes, was there any firmware incompatibility?
Click to expand...
Click to collapse
Yes, I installed a couple of custom ROMs and they were fine.
The only place I know that matters is the xbl and xbl_config partitions. The full OOS ROMs have an extra -lp5 set of files that get flashed on lp5 phones instead of the "normal" xbl files.
But since this only applies to firmware and the xbl partitions are never touched by custom ROMs, there cannot, therefore, be incompatibilities due to lp4 vs lp5.

Question How to install custom ROM in OnePlus 9 android 12?

I have OnePlus 9 and would like install custom ROM and kernel on my OnePlus 9 with android 12 but I don't know how go to fastboot. Do I need android 11?
Unless I'm mistaken, every custom ROM in this thread is using android 11 firmware so you would need to downgrade (and unlock bootloader ofc).
If you just want to go to fastboot mode, you can do that on any android version. To get to fastboot you can either use the physical keys or the developer option.
To use physical keys, start by powering off your device. Then hold volume up + power, and let go of power once the device vibrates or whatever to show it's turning on. I recommend to keep holding volume up until you see the fastboot screen.
The developer options method is to turn on advanced reboot in developer options, then hold down power, select reboot, and then fastboot/bootloader.
If at any point you find yourself in recovery, there is an option to reboot to fastboot there so no matter where you go it should be pretty easy to get to fastboot.
D3G0N said:
Unless I'm mistaken, every custom ROM in this thread is using android 11 firmware so you would need to downgrade (and unlock bootloader ofc).
If you just want to go to fastboot mode, you can do that on any android version. To get to fastboot you can either use the physical keys or the developer option.
To use physical keys, start by powering off your device. Then hold volume up + power, and let go of power once the device vibrates or whatever to show it's turning on. I recommend to keep holding volume up until you see the fastboot screen.
The developer options method is to turn on advanced reboot in developer options, then hold down power, select reboot, and then fastboot/bootloader.
If at any point you find yourself in recovery, there is an option to reboot to fastboot there so no matter where you go it should be pretty easy to get to fastboot.
Click to expand...
Click to collapse
ok, i unlocked the bootloader and i would like to upload a good custom rom and kernel, can you give me a tutorial?
Not gonna lie, it's all up to you what ROM and kernel you want, I'm still on stock for the camera because I use that a lot, so I do not know what roms are good as it all boils down to personal preference. It would be up to you what ROM you want to try.
As far as a tutorial goes, the only things I can say are to make sure that MSM tool works before flashing anything just so that you don't suffer from a brick, and that after you flash the required firmware, before flashing roms use the copy partitions zip that's floating around all over the place in the OP9 forums as that will save you a lot of time and trouble. Other than that, just follow instructions for each individual ROM because they all have slightly different instructions.
If you have problems with the ROM you try, maybe try to ask in the respective thread for that ROM and you can get specialized or specific help there. Just have fun and see what you like!
D3G0N said:
Not gonna lie, it's all up to you what ROM and kernel you want, I'm still on stock for the camera because I use that a lot, so I do not know what roms are good as it all boils down to personal preference. It would be up to you what ROM you want to try.
As far as a tutorial goes, the only things I can say are to make sure that MSM tool works before flashing anything just so that you don't suffer from a brick, and that after you flash the required firmware, before flashing roms use the copy partitions zip that's floating around all over the place in the OP9 forums as that will save you a lot of time and trouble. Other than that, just follow instructions for each individual ROM because they all have slightly different instructions.
If you have problems with the ROM you try, maybe try to ask in the respective thread for that ROM and you can get specialized or specific help there. Just have fun and see what you like!
Click to expand...
Click to collapse
after uploading twrp to oneplus the computer does not see the phone as a disk.
there is just something like a printer and i can't upload custom roma to phone to install via twrp. I can only turn on in fastboot mode.
please help me
matt_rac said:
after uploading twrp to oneplus the computer does not see the phone as a disk.
there is just something like a printer and i can't upload custom roma to phone to install via twrp. I can only turn on in fastboot mode.
please help me
Click to expand...
Click to collapse
Hey I'm sorry to hear that but you should seek help in the thread where you found the twrp. I don't use it but people in that thread probably do. They are more knowledgeable about this than I am. As far as I know it's not compatible with android 12 on this device and I am pretty sure you are on android 12. I really recommend you go to that thread with the recovery that you installed, they probably can help.
matt_rac said:
after uploading twrp to oneplus the computer does not see the phone as a disk.
there is just something like a printer and i can't upload custom roma to phone to install via twrp. I can only turn on in fastboot mode.
please help me
Click to expand...
Click to collapse
How did you flash Twrp? Did you follow the steps correctly or did you accidentally flash over boot? If so you need to extract boot from payload.bin in rom with a payload dumper and flash extracted boot.img from stock rom, or find a boot.img off the net that matches your rom. Last resort MSMtool back to stock A11.
To flash boot
Fastboot flash boot boot.img
To flash recovery
Fastboot flash recovery recovery.img
If you flashed while you were on Android 12.1 or android 12 you will have to use MSM tool which is a firmware flasher for OnePlus devices, stock firmwares for different models are posted within this forum make sure you install correct drivers. And make sure you take step by step very carefully and be patient with the program sometimes slow while flashing

Question How to unbrick One Plus Nord CE 2 Lite ?

I have bricked this device (One Plus Nord CE 2 Lite) by flashing the unofficial twrp image for this device. Device bootloops in TWRP.
Previously, I had succesfully unlocked the bootloader and rooted this device by flashing the patched magisk boot.img by following the method mentioned in this post (https://forum.xda-developers.com/t/rooting-oneplus-nord-2-ce-lite.4500297/)
How to restore the factory image and recover from this?
Any help is appreciated.
Thanks
...reboot to fastboot, flash the original boot and vbmeta and you're done ...maybe you have to change back the slot, but it's almost impossible to brick the device
...don't mess around with "Recovery" ...this device has already the newest partitioning system and there is no recovery partition
best regards
I messed up by flashing the wrong twrp image made. (Device was stuck on 1+ logo screen)
Thanks to your post i was able to rescue this device.
I used Oxygen Updater App, payload-dumper-gui and minimal adb fastboot.
Flashed boot and vbmeta with stock img files.
Restarting the device now will boot into fastboot mode.
Changing slots helped a lot.
(fastboot set-active=a/b)
After that, Device booted normally into OS.
... you're very welcome, Sir ...but really, don't mess around with "old school" recovery systems ...they are not needed anymore and furthermore they can't handle the "dynamic super partitioning" ...and again: nobody needs them after the year 2015 anymore
...best regards
NickR01 said:
I messed up by flashing the wrong twrp image made. (Device was stuck on 1+ logo screen)
Thanks to your post i was able to rescue this device.
I used Oxygen Updater App, payload-dumper-gui and minimal adb fastboot.
Flashed boot and vbmeta with stock img files.
Restarting the device now will boot into fastboot mode.
Changing slots helped a lot.
(fastboot set-active=a/b)
After that, Device booted normally into OS.
Click to expand...
Click to collapse
Hey can you help me pls, I am in the exact same situation as you but I can't get the stock img files, whenever I use payload-dumper it just gives me system.img and nothing else, could you maybe share your img files ?
Edit: I manged to get some files but still not the boot.img, I don't undestand why it just refuses to give them to me, I redownloaded everything at least 3 times...
Use Payload-Dumper-GUI instead of Payload-Dumper-Go
Hey @NickR01 if possible can you send me an boot.img and vbmeta
I don’t have windows pc so can’t use Payload-Dumper
It will also help future users to unbrick device.
NickR01 said:
Use Payload-Dumper-GUI instead of Payload-Dumper-Go
Click to expand...
Click to collapse
@vikas_anakin What's your device version?
cph2381 cph2409
NickR01 said:
@vikas_anakin What's your device version?
cph2381 cph2409
Click to expand...
Click to collapse
cph2381
@vikas_anakin I have files for eu variant, can't help you there bud. If flashed it can mess up your device.
If you are stuck with payload.bin extraction... try it with an android device.
Here's the tool for Android.
Payload-Dumper-Android
Here's the guide for it.
XDA Guide
Newb Guide
Follow the guide and download this app to extract the .bin file
Termux App: Termux Github
After the extraction, type fastboot (pc required) commands to flash and change current active slots from A to B if it's stuck in bootloop after flashing.
I hope this helps you recover your device.
NickR01 said:
@vikas_anakin I have files for eu variant, can't help you there bud. If flashed it can mess up your device.
If you are stuck with payload.bin extraction... try it with an android device.
Here's the tool for Android.
Payload-Dumper-Android
Here's the guide for it.
XDA Guide
Newb Guide
Follow the guide and download this app to extract the .bin file
Termux App: Termux Github
After the extraction, type fastboot (pc required) commands to flash and change current active slots from A to B if it's stuck in bootloop after flashing.
I hope this helps you recover your device.
Click to expand...
Click to collapse
Extracting the payload.bin is not an issue, The issue is I don't have stock firmware.
I used https://www.getdroidtips.com/oneplus-nord-ce-2-lite-5g-firmware-flash-file/ but my wifi and Bluetooth are not working after installing it.
Do you have any suggestions on how can i resolve these issues?
@vikas_anakin Download authentic firmware from this app. Files are pulled from OnePlus servers.
Google Playstore: Oxygen Updater
Oxygen Updater Settings -> Enable Advanced Mode
Select device region.
Latest update for holi is CPH2381_11_A.13 as of now.
I extracted the images from the payload.bin found in the Oxygen Updater file (that I had actually successfully used to update my device) and flashed 2 partitions:
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
I then rebooted and now it's stuck in a boot loop & I can't even access fastboot anymore. Can someone please help?
Thanks
EDIT:
I managed to access fastboot & flash the rest of the partitions to fix it.
Hi everyone, just to piggy back on this thread, I also have the same device, and I have unofficial twrp and boot loader unlocked, however I have no back up rom and just want to get the phone back to normal really. Ive been following guides all over the place, but could someone point me in the right direction ? can I just download a rom for the OP nord ce 2 lite 5g, put it on my phone and have twrp install it? could someone guide me please. many thanks!
lemonmuffs said:
Hi everyone, just to piggy back on this thread, I also have the same device, and I have unofficial twrp and boot loader unlocked, however I have no back up rom and just want to get the phone back to normal really. Ive been following guides all over the place, but could someone point me in the right direction ? can I just download a rom for the OP nord ce 2 lite 5g, put it on my phone and have twrp install it? could someone guide me please. many thanks!
Click to expand...
Click to collapse
Yes, that will work.
vikas_anakin said:
Yes, that will work.
Click to expand...
Click to collapse
Or else you can extract img files from the oneplus rom file.
and flash them using fastboot.
Okay thank you for the reply, would you be able to point me to a official img file ? Or maybe someone has one extracted I could use please? I have looked online, but the ones I have gotten don't seem to work. I have also looked on the oneplus website for an official img but I could not find one.
So after a little more research, I can use another android device with the app Oxygen updater, download the full img.... So I am currently doing that and then ill try use fastboot or twrp to flash. Just wanted to spread info incase anyone else is having issues getting latest official roms for this device.
Hey guys, i have bricked my Oneplus Nord ce 2 lite 5g (Cph2381)
I tried using the fastboot enhance tool to flash a payload.bin file i thought was the right one for the device ..the device went to blackscreen..ive tried switching it on but its not working..ive done alittle research and found out that i should use an msm tool to force flash the initial stock firmware so that it can boot up ...problem is i cant seem to find the right msm tool for Oneplus nord ce 2 lite 5g , which msm tool can i use ? help please
Jazzyjuis said:
Hey guys, i have bricked my Oneplus Nord ce 2 lite 5g (Cph2381)
I tried using the fastboot enhance tool to flash a payload.bin file i thought was the right one for the device ..the device went to blackscreen..ive tried switching it on but its not working..ive done alittle research and found out that i should use an msm tool to force flash the initial stock firmware so that it can boot up ...problem is i cant seem to find the right msm tool for Oneplus nord ce 2 lite 5g , which msm tool can i use ? help please
Click to expand...
Click to collapse
Hey man, I would suggest not going with msm tool or anything.
Just download the latest update file of your device using oneplus updater app, or you can ask for the file if some of your friends has the same device.
use this tool to extract payload files https://github.com/vm03/payload_dumper
Now you can follow the same procedure as here https://forum.xda-developers.com/t/...ock-oxygenos-firmware-on-oneplus-10r.4465077/

Categories

Resources