Hello, this is not a guide for noobs.
At this point, i assume your BlackShark 1 is running a custom ROM, or a modification, and not it cannot update over OTA.
This guide helps you restore your BS1 SKR-H0 to Stock ROM, hopefully you can update it when the next OTA comes out.
This guide sets one of your partitions at system update G66X1906170OS00MPX.
You agree that by performing these operation, you risk bricking your device. I will probably not be there to help you recover.
There are a few steps:
Flash the stock images
Re-encrypt storage
Re-flash the stock files
Flash the stock images
Download the full backup from here: https://mega.nz/#!IZFAEAoC!UMHJ0drlhoHyGtV-0KYrtteC1VMP8-eqFWWrMXLZikQ
Extract the backup
Enter fastboot mode on your phone
Check which slot you are on, and which slot is definitely working. Try this on a slot that is broken, or that is not 100% working (in my case, slot a)
Run the following command for every partition:
Code:
fastboot flash <partitionname>_<slotname> <filename>
example: fastboot flash boot_a boot_a (if the slot you are overwriting is slot a)
or fastboot flash boot_b boot_a (if the slot you are overwriting is slot b)
Once finished, boot twrp, flash disableforceencrypt and magisk, and reboot into the system.
Reencrypt storage
First of all, backup ALL YOUR INTERNAL STORAGE, as it WILL GET WIPED IN THIS STEP. i warned you.
Once the system boots with the new version, go into stock recovery (adb reboot recovery, or enter bootloader > select start recovery)
Then reboot into the system. once the system boots, go to settings, security, encryption, and enable encryption. The phone should encrypt now. Wait for it to start encryption, finish, and get stuck at boot animation. This is the end of step 2.
Re-flash the stock files
This is the final and easiest step. If previous steps were performed correctly, then all you have to do now it the following:
from the stuck bootanimation, reboot to bootloader.
Flash 1 more time system, boot and vendor partition. This time DO NOT flash disableforceencrypt and magisk.
reboot into stock recovery
perform a wipe 1 more time.
reboot the system.
If done correctly, your phone should go into first time setup, with the stock OS, no internal error on boot, and you should be able to accept OTAs when they come. If OTA fails, Follow step 4:
(Optional) OTA Shows up again after finishing, and keep failing
If you restored your BlackShark to stock, and OTA does not finish (keeps coming back up), do the following:
If your backup is from slot a, and you are on it right now, run the following commands:
Make sure you are on the correct slot, with the correct backup!
Code:
fastboot flash boot boot_a.img
fastboot flash system system_a.img
fastboot flash vendor vendor_a.img
fastboot flash dsp dsp_a.img
fastboot flash devcfg devcfg_a.img
fastboot flash bluetooth bluetooth_a.img
fastboot flash dtbo dtbo_a.img
fastboot flash modem modem_a.img
fastboot flash vbmeta vbmeta_a.img
For the partitions dtbo and devcfg, i'm not sure if they need reflashing, however i found out that the others might be changed indirectly, and cause OTA to fail.
So just reflash those partitions from backup (Make sure to use the correct version/slot!)
Finally, if update still fails, you can connect your phone to pc, run adb logcat, and watch the logs just after update download is finished. If it fails, you will find some lines about a failed partition, with the partition name.
Special thanks to @leipnacht who provided me with stock file, so that i could restore my phone.
Big Thanks to this! I'm glad the stock files helped restoring your phone. This will surely help xda users as well when somethings go wrong with root coz some games will ban you if your phone is detected as rooted phone. This is very useful reference for everyone.
i need this for CN version too:crying::crying:
help
How do I install and recover my black shark please?
when I have install via fastboot I get a message
FAILED remote flashing is not allowed for critical partitions.
way of doing the command on fastboot
fastboot flash partitionabl_a abl_a
fastboot flash partitionsystem_a system_a
Sorry, I do not understand much about this.
metamorfose123 said:
How do I install and recover my black shark please?
when I have install via fastboot I get a message
FAILED remote flashing is not allowed for critical partitions.
way of doing the command on fastboot
fastboot flash partitionabl_a abl_a
fastboot flash partitionsystem_a system_a
Sorry, I do not understand much about this.
Click to expand...
Click to collapse
It's fastboot flash abl_a abl_a
Etc... If you want to overwrite slot a, or
Fastboot flash abl_b abl_a
If you want to overwrite B.
needful guide for restoring black shark. Big thumb up for this post.
@gilbert32 thanks for your hard work! I'll check to see if I can find someone with a stock CN rom and see if this will work for it. I haven't had the phone until now because a family member temporarily needed one :good:
hi, i have a problem, after flash system i get only on S logo
geed301 said:
hi, i have a problem, after flash system i get only on S logo
Click to expand...
Click to collapse
What version are you on? Which black shark?
SKR-H0 in oreo 8.1, but i resolved hahaha, i was used
fastboot flash boot boot_a.img
fastboot flash system system_a.img
fastboot flash vendor vendor_a.img
Just copy and pasted hahaha , today i updated to P and its great
Thnks for the tutorial and sorry for my bad english
Hi! I do not understand. One month ago I used this tutorial and I could get the previous little OTA update. Now I tried again do the same steps, all of them, and I can't get the OTA. I tried it 5 times… I have a question, in this new update of android Pie is the camera slow motion enabled? Can someone upload the android Pie backup for flashing directly?
FasterBit said:
Hi! I do not understand. One month ago I used this tutorial and I could get the previous little OTA update. Now I tried again do the same steps, all of them, and I can't get the OTA. I tried it 5 times… I have a question, in this new update of android Pie is the camera slow motion enabled? Can someone upload the android Pie backup for flashing directly?
Click to expand...
Click to collapse
I didn't find any slow motion option in camera. When you try OTA, open adb logcat at the same time. It should show you an error regarding which partition was modified when OTA fails.
It's probably one of: Boot, System, Modem, DSP, DTBO, Bluetooth, Vendor (maybe also other ones)
i need stock global ota package
do you have it yet?
hoangtieubao said:
i need stock global ota package
do you have it yet?
Click to expand...
Click to collapse
I have a backup of the global pie rom, i can upload it within this week.
gilbert32 said:
I have a backup of the global pie rom, i can upload it within this week.
Click to expand...
Click to collapse
i have solution to full convert rom to global
but i still dont have skr-h0 ota package full base
i need it to do
i have cn version OTA package, after flash
it can use *#1027# to fully convert to chinese version , ota works fine.
maybe you need to ask blackshark to provide a Full OTA request to your phone. just say your phone is rooted ,and cannot update anymore, need a full ota to restore it.
we use this trick to get cn version full ota package and it works
Vlin.Wang said:
i have cn version OTA package, after flash
it can use *#1027# to fully convert to chinese version , ota works fine.
maybe you need to ask blackshark to provide a Full OTA request to your phone. just say your phone is rooted ,and cannot update anymore, need a full ota to restore it.
we use this trick to get cn version full ota package and it works
Click to expand...
Click to collapse
this trick is very nice
and could you do it to get full ota for us?
i think too many people to want it
Any chance to find the global rom for black shark 2 pro.. DLT-A0
Any chance to find the global rom for black shark 2 pro.. DLT-A0
I need to make the phone supports multi language
Please help
Help Needed
Hi All,
Hope all is well.
Could anyone please help post a noob guide for this. I've flashing rooting etc thinf before but this one's really confusing for me. I would appreciate it greatly. I have a facebook group of BS1 Global user and they all wanted to restore their smartphone, I referred them to this thread but none of them seems to understand this tutorial. Pardon our ignorance. We would really appreciate it greatly.
Thanks in advance!
Hi Gilbert,
Thank you so much for posting this.
Your effort is greatly appreciated by us.
I am new to BS1 Global and I haven't done flashing rooting etc to this phone.
It would really help if there could be a step by step tutorial for users like me.
I would like to ask what files/tools are needed for this tutorial. I probably need pc? And probably need to install something on pc like drivers? What are they?
I'm guessing I need to unlock bootloader and root my bs1 global?
Also need to install twrp for bs1 global? And I don't know this disablforceencrypt and magisk thing.
Please please help post a noob tutorial for bs1 global that haven't been modified yet.
That would really be helpful, I look forward to your response. Thank you so much in advance.
Related
Code:
Warning! any damage done to your device is not my fault, use at your own risk!
This zip should be used mainly if you wiped system for some reason and didn't back up, its TA-1060 May patch system image + kernel + vendor files
Unlocked bootloader required!
TWRP
1. Boot into TWRP
2. Format /data partition in TWRP
3. Use 'adb push ta_1060_oreo_may_18.zip /sdcard/' in windows/linux/mac
4. Go to sdcard in TWRP and flash ta_1060_oreo_may_18.zip
5. Reboot to bootloader
6. use 'fastboot flash recovery recovery.bin' (Link bellow)
7. Optional: fastboot oem lock
8. reboot
9. on boot you will get encryption, click on the reset button when android loads
10. You will reboot into recovery then back into system, done
Fastboot
1. Extract zip file
2. flash system.img, boot.img, vendor.img in fastboot
3. fastboot reboot
Links:
Stock ROM zip May
Recovery image
Good luck
XDA:DevDB Information
[ROM][STOCK][TWRP][27/06/18]TA-1060 Stock Oreo 8.1, ROM for the Nokia 1
Contributors
sooti
ROM OS Version: 8.x Oreo
Version Information
Status: Stable
Created 2018-06-27
Last Updated 2018-06-27
So we can flash either through TWRP or Fastboot right?
Zeenat11 said:
So we can flash either through TWRP or Fastboot right?
Click to expand...
Click to collapse
I haven't tested fastboot but it should work. TWRP works 100%
Thank you very much, you are a life saver!!
I was stuck in a TWRP loop.
I tried flashing through TWRP but it didn't work but the fastboot method worked like a charm!
My phone is running again.
Thank you very much.
Is there any userdata.img available?
alexstarc said:
Thank you very much.
Is there any userdata.img available?
Click to expand...
Click to collapse
Nope but do you really need it? just format in fastboot or TWRP.
sooti said:
Nope but do you really need it? just format in fastboot or TWRP.
Click to expand...
Click to collapse
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
alexstarc said:
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
Click to expand...
Click to collapse
I wrote in the instructions...
If you get a password just enter a random one, then it will ask you to wipe the device, click ok and it will reboot to recovery and then wipe userdata and boot fine.
just make sure you flash the recovery.bin and not twrp before you wipe
alexstarc said:
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
Click to expand...
Click to collapse
Same happened to me. I solved it by a hard reset via the stock recovery.
Make sure you flash the recovery.bin like Sooti said.
Wiping through twrp doesn't work.
Nice, working twrp for Nokia 1.
I buyed this phone today. Waiting for customs
A little warning.
It looks like the recovery.bin I took from another nokia 1 device doesn't match the checksum check which causes a failed during ota updates, please only flash this rom if you soft bricked your device.
If anyone can get me TA-1060 stock recovery image that should solve it. for now you can't update the phone until a fix is found
I have Nokia Ta 1066. Will this rom work on mine? Also I read somewhere Ta 1060 is single sim variant. What about the second sim?
Has anyone with TA 1066 tried it?
Thanks. Both methods work fine. Don't ask how I found out.....
Can you share how you managed to backup stock recovery file. Maybe after all the steps above we can flash our own device recovery to make ota work again...
coolboyforeva said:
Can you share how you managed to backup stock recovery file. Maybe after all the steps above we can flash our own device recovery to make ota work again...
Click to expand...
Click to collapse
I don't have stock recovery from our device i have from another variant of Nokia 1
Hey guys i have a TA-1056 and after unlocking bootloader and flashing TWRP it booted to recovery and came up encrypted, after looking around the only solution was to format data, afterwards when rebooting it always boots to recovery, i tried flashing this zip and i get the same issue and i can't find the stock ROM for the 1056 anywhere online, can anyone help me out? i really appreciate it
Kurajmo said:
Nice, working twrp for Nokia 1.
I buyed this phone today. Waiting for customs
Click to expand...
Click to collapse
got any custom roms?
Does Nokia 1 support DT2W?
Sir, is that possible to get a stock rom of TA 1056 ?
I have searched everywhere but whole thing available over net just left my phone bricked. All i need is a working rom source. Even if that’s a custom rom too to flash via sp flash tool. Thanks in advance
Can any please repost the firmware , the link isn't working
Links to Firmware & OTA & TWRP & Magisk & Bootloader - Z3 PLAY BECKHAM (All Variants)
Firmwares
the latest firmware as of time of writing is February's 2020 OTA (BECKHAM_RETAIL_9.0_PPWS29.131-27-1-18_subsidy-DEFAULT_regulatory-DEFAULT_CFC) = https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
previous OTAs RETAIL variant can be found here = https://mirrors.lolinet.com/firmware/moto/beckham/official/RETAIL/
future OTAs possibly here = https://androidfilehost.com/?w=search&s=beckham
other variants = https://mirrors.lolinet.com/firmware/moto/beckham/official/
Unlock Bootloader
first you need to install Motorola Drivers = https://support.motorola.com/us/en/solution/MS88481
- ATTENTION - use the most up-to-date ADB Drivers otherwise will brick if older version is used; instead of downloading ADB elsewhere which is often old version, get it directly from GOOGLE, here = https://dl.google.com/android/repository/platform-tools-latest-windows.zip
now you can proceed to unlock bootloader = https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
TWRP
get the official TWRP here = https://dl.twrp.me/beckham/
- ATTENTION - if you just want root access, then there's no need to install TWRP, just boot from the .img once using the latest version
use TWRP to make a backup of EFS partition before installing anything, store the backup files outside of the device
if you want custom ROMs or GSI, then you will need to install TWRP installer .zip into the recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the latest .zip version in the recovery partition. Unfortunately the only official installable version of TWRP that exists is bugged, and the TWRP developers haven't fixed it yet, go talk to them ask for some love, be respectful = https://github.com/TeamWin/android_device_motorola_beckham/issues
Magisk
install Magisk using the new&correct method AKA "Boot Image Patching Method" to be able to install OTA later = https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
when OTA arrives, you may manually install it whilst retaining Magisk by carefully following these instructions = https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
- ATTENTION - you won't be able to install stock OTAs if you use older method or if system partition is modified, be really careful to not alter the hash of the partitions
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
@heynando, what is the difference between "retail" and "retus"? Also, does anyone know the numbering system? All the uploads on lolinet.com for Pie have 131 as the first three numbers, but the few posted about here have 183. Maybe 183 is an ota number?
ritchea said:
@heynando, what is the difference between "retail" and "retus"?
Click to expand...
Click to collapse
RETUS is short for Retail + US.
The difference between RETUS and RETAIL is, I imagine, cannot confirm, the same RETAIL firmware with some US regional modifications such as bloatware or CSC thing
you can check which model is yours in SETTINGS > SYSTEM > ABOUT PHONE > SOFTWARE CHANNEL. Or in the bootloader by running the command
Code:
fastboot getvar product
you can find the entire list of product codes here = https://mirrors.lolinet.com/firmware/moto/readme-en.html#listone
XT1929-4(Canada, SS, 4+32GB) XT1929-3(NA/Sprint, SS, 4+32GB)
XT1929-4(NA/AMZ/BWACA/RETCA/RETUS/USC, SS, 4+64GB)
XT1929-5(BRAZIL/RETBR/TIMBR/TEFBR, DS, 4+64GB / 6+128GB)
XT1929-6(LATAM/AMXLA/NIIPE/ATTMX//TEFCL/TEFPE/RETLA/RETAR/RETMX/RETCL/AMXMX, DS, 4+64GB)
XT1929-6(LATAM/RETLA/TEFCO/TIGCO, DS, 6+128GB)
XT1929-8(EMEA_APAC/RETEU/DTEU, DS, 4+32GB / 4+64GB)
ritchea said:
Also, does anyone know the numbering system? All the uploads on lolinet.com for Pie have 131 as the first three numbers, but the few posted about here have 183. Maybe 183 is an ota number?
Click to expand...
Click to collapse
I believe that's the internal version of the software. If the number changes that emphasizes there has been software changes and/or tweaks in the system and/or firmware. If the number doesn't change, then it's just a regular security patch with no further modifications in system and/or firmware.
Thanks for that info. Yeah, I know mine has the retus software channel. I just couldn't find or figure out if Retail was actually one word or if it was a combo of ret+ail. That version has a LOT of software posted.
I flashed retail on an EU model. And after it the software channel say Reteu just like the original. Also the model number is as it should be. In my opinion you can flash retail firmware on us and EU models.
confirmed that this firmware is working on XT1929-4
these are the steps I took:
downloads and setup
install moto drivers (in windows, not needed for linux)
install android tools (adb and fastboot)
downloaded official TWRP
downlaoded and extracted the firmware
backup of partitions (including efs)
Code:
adb reboot bootloader
fastboot boot twrp_recovery.img
backed up lots of partitions
rebooted system
copied the TWRP backup files to my pc for safe keeping
set the fastboot slot (i did this because many of teh fastboot commands below were failing)
Code:
adb reboot bootloader
fastboot --set-active=a
rebooted back into bootloader
installed the firmware
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot reboot
installed magisk the new good way
did the initial device setup
installed magisk manager
copied the boot.img from the extracted firmware above to the phone.
followed these steps for boot img patching and install of magisk https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
sirkuttin,
Thanks for the detail how to. That worked perfectly for me, and my moto z3 play, same model as yours. I could not get the ota or even lenovo smart assistant to work on my phone. It basically had it locked up, stuck on the boot logo. I'm assuming its the old way of install magisk that caused that. This got me on the latest firmware release, and then installed magisk the new way. Lenovo smart assistant was useful in downloading the firmware.
Thanks.
Hi I tried the new magisk install way. I'm on XT1929-4_BECKHAM_RETUS_9.0_PPW29.183-29-1, copy boot.img and patched it to magisk_patched.img. Then after fastboot flash boot /path/to/magisk_patched.img and a reboot, i'm not stuck on the motorola powered by android screen. Verity mode is set to disabled.
I tried holding down the power button to simulate a battery pull but no luck, the screen just stays on. Can anybody give me any advise? I think now I have to just wait till the device is out of juice. Never experience this before.
---------- Post added at 02:16 PM ---------- Previous post was at 01:31 PM ----------
So the battery pull is "Power + Vol Down". I was able to flash the PPW29.183-29-1 firmware and get it going again. I noticed it tried to upgrade me to PPW29.183-29-1-2 so I must have been on newer firmware. I flashed the magisk_patched and am rooted now.
It seems there is TWRP 3.3.1-1 with an Installer. Does it mean it can be flashed to recovery partition? Tried booting it, but got stuck on TWRP logo (3.3.1-0 boots fine).
ch3mn3y said:
It seems there is TWRP 3.3.1-1 with an Installer. Does it mean it can be flashed to recovery partition? Tried booting it, but got stuck on TWRP logo (3.3.1-0 boots fine).
Click to expand...
Click to collapse
I haven't tested it myself, though you're correct, the installer .zip can be installed on recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the .zip in the recovery partition.
PS only do it if you have a reason to, I'm not sure if the firmware OTA checks the hashing of the recovery partition so altering it could potentially prevent you from installing OTAs of the official ROM.
heynando said:
I haven't tested it myself, though you're correct, the installer .zip can be installed on recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the .zip in the recovery partition.
PS only do it if you have a reason to, I'm not sure if the firmware OTA checks the hashing of the recovery partition so altering it could potentially prevent you from installing OTAs of the official ROM.
Click to expand...
Click to collapse
It, unfortunately, does... However I csnnot update (continous update unsuccesful) :f Have to check if Xposed module is not a reason.
And You probably could use Installer to flash stock recovery? If not TWTP itself however I've never checked if one for Play has access to recovery partiotion to flash images. It should gave if it can be done using the installer...
Sent from my Moto Z3 Play using Tapatalk
ch3mn3y said:
However I csnnot update (continous update unsuccesful)
Click to expand...
Click to collapse
Me too and it drove me nuts, I did patch the /boot partition with the original file, but the OTA app still failed to install, even after reboot. And there's no useful data in the logcat to debug the app. So I gave up and had to use Titanium to freeze the OTA app otherwise it would keep trying to download and install infinitely.
ch3mn3y said:
:f Have to check if Xposed module is not a reason.
Click to expand...
Click to collapse
It's probably not because I don't use it and the OTA method didn't work me either
ch3mn3y said:
And You probably could use Installer to flash stock recovery?
Click to expand...
Click to collapse
Yes you're right, I agree there..
heynando said:
Yes you're right, I agree there..
Click to expand...
Click to collapse
Just checked the inside of the installer zip file and it won't work. Still once every 3 months it wouldn't be a problem to connect device to PC and flash recovery.img with fastboot.
Is there a list with a commands and order how to flash Z3 Play images of official firmware? I want July patches and have some problems, so clean reflash is what I need.
Additional question is if I have to use "-u" when flashing second and other system images? Remember I had to do it with my X Play coz of unlocked bootloader and here I have one in the same state as well. If yes than could someone tell me where to put it, coz I'm not sure...
tb110188 said:
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
Click to expand...
Click to collapse
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?
tb110188 said:
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
Click to expand...
Click to collapse
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?
Ramble2k said:
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?
Click to expand...
Click to collapse
This one, make sure to get the latest. https://mirrors.lolinet.com/firmware/moto/beckham/official/RETUS/
Hi, I'm trying to unlock my Moto Z3 Play bootloader, but I don't get the code on CMD, but only a few numbers ... The version of my device is PPW29.131-27-1-11, channel RETBR software.
Someone went through this, can you tell how to reverse this situation?
I couldn't get the bootloader unlocked for xt1929-4. I tried different computers, Linux and win. Have latest adb and fastboot. When fastboot OEM get_unlock_data is given, I says counttas slot not found etc., can someone help?
It may seem obvious, but you
checked OEM unlocking and USB Debugging?
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.
It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/...300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.
MarekPietrzak said:
It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/UL-ASUS_I005_1-ASUS-33.0210.0210.200-1.1.300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.
Click to expand...
Click to collapse
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse
MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
hey, Thanks for replay, i am facing now another messeges.
1- the phone does not charging at all
2- when i plug in into chrage its reboot again and again.
3- the bootloader is open, but when i try to flash any files through bootloader i get:
FAILED (Status read failed (Too many links))
or
FAILED (remote: 'Warning: battery's capacity is very low
to recovery mode i am unable to go there
i tried boot or flash the twrp.img also only boot.img also flash_raw_and_wipe_data.cmd
nothing helps me!!!
Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.
MarekPietrzak said:
Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.
Click to expand...
Click to collapse
I've tried leaving it on overnight and it never charges, there's even no charging lights.
Yesterday I tried flashing via Bugjeager and it didn't work either (betwenn to android devices)
Although the bootloader is unlocked, it gives me a Not Allowed In Lock State message!
the current version of the installed firmware is that old that i flashed WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw, it is non extractable so i cant get the boot.img of it!
I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system
MarekPietrzak said:
I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system
Click to expand...
Click to collapse
wow you are alive haha i thought you not gonna answer me again. ok just 1 second
rami88436 said:
wow you are alive haha i thought you not gonna answer me again. ok just 1 second
Click to expand...
Click to collapse
Sometimes I can be a bit slow to respond as I am on the university during day. Hopefully your issue seems to be possible to be solved just by flashing raw firmware and wiping data partition.
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root
chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse
try root your phone through kirnal su
chairman011 said:
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root
Click to expand...
Click to collapse
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.
I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse
MarekPietrzak said:
I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
Click to expand...
Click to collapse
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
rami88436 said:
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.
Click to expand...
Click to collapse
Oh ok ok makes sense. Usually when I face a brick problem I just flash raw firmware fastboot
Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
chairman011 said:
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
Click to expand...
Click to collapse
MarekPietrzak said:
Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
Click to expand...
Click to collapse
Oh wow thank you man I'll give it a shot.
I found a gui-based app on github to systemlessly debloat, it is easier to use than this script I posted link to. Here is the link: https://github.com/sunilpaulmathew/De-Bloater
Does anyone have the full RAW firmware, flashed via fastboot? Thank you all
ThienAn2023 said:
Does anyone have the full RAW firmware, flashed via fastboot? Thank you all
Click to expand...
Click to collapse
Mod. edit: private link removed. alecxs
Good morning all I need some help unbricking my pixel 5. I have exhausted all possible avenues that I'm aware of to restore my phone out of bootloop. At the time I messed it up I was attempting to use twrp. In an attempt to fix the phone I tried flashing the system,and boot to no avail repeatedly getting the error "boot.img missing command-line or os version" as well as using the flash all from the stock firmware file. The current active slot is b and the a/b partition thing is new to me so I'm sure somewhere along the way I missed something. Any help is greatly appreciated .
Could you try this fastboot command and see if it works?
fastboot --set-active=a
I did try that however I'm not sure i was doing it correctly is it typed the way you typed it out?
Reboot the phone into the bootloader, look up how to do that if you don't know how, and then manually flash a rom or use the Android Flash Tool. The latter option is recommended if you are a novice.
I wouldn't say I'm novice lol but more out of the game too long either way thank you for your assistance I will try that as soon as I get a chance and report back
UPDATE your advice worked and I was able to reboot properly thank you in a side note is it impossible at this time to install twrp on a pixel 5?
musiv2 said:
UPDATE your advice worked and I was able to reboot properly thank you in a side note is it impossible at this time to install twrp on a pixel 5?
Click to expand...
Click to collapse
Yes. The Pixel series, as with most A/B devices, do not have a bespoke recovery partition. The recovery kernel is compressed into the boot image. TWRP does not support compression in this way so it cannot be used as a replacement for the stock recovery. The only effective way to use TWRP is to live boot the image, use TWRP to do whatever you need to do, without installing it to /boot.
BTW the next time you need to restore your phone you can use the Android Flash Tool.
Ok thank you for the explanation as I stated before I am new to the a/b partitioning way of android life so I have alot to learn
I used twrp in the past( on no A/B devices) but would recommend learning fastboot/adb. First step: always make sure USB debugging is enabled after every flash. This will make it so you can fix a lot of mistakes and recover your device. It's the first thing I do after every boot on a new install.
Here's the commands to flash stock to both slots. NOTE: this is for android 13. 12 and before will be a little different. Bootloader, radio and rom names should be exact to file, this is just for example.
fastboot --slot=all flash bootloader bootloader.img
fastboot reboot bootlaoder
fastboot --slot=all flash radio radio.img
fastboot reboot bootlaoder
fastboot --slot=a --skip-reboot update stock-image.zip
fastboot reboot bootlaoder
fastboot --slot=b --skip-reboot update stock-image.zip
fastboot -w
fastboot reboot
One final note: I put slot a first but I always start with the active slot(it's in the bootloader screen). If you want the android 12 instructions, let me know but it's not much different, you just use the stock recovery.