Database Users

[Guide][How-To] Root Android 8 Oreo - Pixel (XL) + SafetyNet Pass

This is how to root with SuperSU and includes flashing SuperSU Hide for Android O
Requirements:
Unlocked BootLoader
Latest fastbook/adb drivers (https://forum.xda-developers.com/android/software/guide-how-to-set-fastboot-adb-to-wide-t3591240)
Android O image (https://developer.android.com/about/versions/o/download.html#top)
SuperSU 2.82 SR3 (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133)
Modded Version of the TWRP that works for Pixel/XL DP4/O (https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896)
If you want SuperSU Hide for safety net passing (as of (8/21/2017 this is working) for Android Pay, Pokemon GO, Snapchat download SuperSU Lite from here (https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855)
The How to part
Flash the Android O factory image on your device
Let the divice boot and go through setup and i advise you set a lockscreen method (Pin, Pattern, Password whatever you want but this will allow TWRP to decrypt your data more consistently) then reboot to bootloader
boot into the TWRP linked above
Go to "Wipe" select "Advanced wipe" check just "internal storage" and swipe to wipe
your device's internal storage should now be accessible via your PC/Mac/Linux so copy of the linked SuperSU SR3 we downloaded from above
Back to TWRP and the device, flash the SuperSU you copied over
let it finish then swipe to reboot to system (do not install the TWRP installer app it asks you to install before the reboot)
let the system boot up and check to make sure supersu is there
reboot back to bootloader and boot into the TWRP
Enter your lockscreen login (Pattern will show up if you used a pattern otherwise type in you password or pin when it asked for password)
copy the supersu hide lite from your PC/Mac/Linux to the internal storage of the device
flash it in twrp then swipe to reboot to system
Finally when it boots you should have supersu and SUHide installed!
Few Notes:
-It is very important to know that we are not flashing TWRP to our system when in fastboot/bootloader. If you're coming from an older device or just new to the Pixel in general this will be kinda weird to you I'm sure. The reason we do no do this is (long story short) A/B partition devices like the Pixel's are a whole new ball game and there is still development being done to get traditional methods of installing aftermarket recoveries working. But till then we have to boot into things so the change is temporary and does not alter the device's recovery partition.
-How SuperSU Hide works is pretty self explanatory but if you're like me, the whole safety net thing is annoying and i haven't felt like reading about it. So using the "suhide" app you now have, you want to make sure root is hidden from the apps that watch for it and stop themselves from running is they see root (Snapchat, Android Pay and Pokemon GO are all examples of these apps)
the "About" tab in the "suhide" app is very helpful
Old instructions for Android O DPs
Early reports say boot-to-root (the method covered here) works for DP4
Rooting DP1-4 is very easy.
Make sure bootloader is unlocked
Make sure Fastboot/adb drivers are fully up to date. (Follow this guide to make sure: https://forum.xda-developers.com/android/software/guide-how-to-set-fastboot-adb-to-wide-t3591240 )
Download dp1-3 (https://developer.android.com/preview/download.html)
Download SuperSU 2.82 SR 1 for Pixel (or pixel xl) (https://forum.xda-developers.com/showpost.php?p=72686197&postcount=10481) [Updated to new fixed version that repaird system mounting issue]
Just flash Dev Preview like normal
boot into system and setup android
Reboot to bootloader
Exact the downloaded supersu
Reboot to bootloader
open a cmd in the extracted supersu location and type
Code:
fastboot boot boot-to-root.img
it will take about 7 minutes to boot but when it does you should have root
Original Instructions for rooting DP1
So after a few weeks of being without root on Android O for the Pixel user Sachi315 discovered how to get root on O by installing 7.1.2 on one slot and android O on the other. This allows Android O to fully boot after installing SuperSU. I wont go into the details of how it works because thus far its all speculation on my part and hopefully someone out there who knows more about these new partitions could better explain it. But for now I'm just going to show you how to do it.
Requirements
+Download 7.1.2 for your Pixel (XL)
-----N2G47E (https://developers.google.com/android/images)
+Download Android O for your Pixel (XL)
-----(https://developer.android.com/preview/download.html)
+SuperSU RS4 2.79 Extra Delay
-----(https://download.chainfire.eu/1024/...-SR4-20170323220017-ODP1-5X-6P-ExtraDelay.zip)
+TWRP RC1 bootable image & RC2 Flashable zip
-----For Pixel (https://dl.twrp.me/sailfish/)
-----For Pixel XL (https://dl.twrp.me/marlin/)
+Backup everything on you device, it will be purged
-----Make sure you have the latest fastboot binaries (I HIGHLY recomend you set this up manually. How to do so can be found in my tutorial here)
+Unlocked bootloader
To make sure you have the latest fastboot binaries press the windows key and type cmd. In the command line type "fastboot" This should return you get. Showing all the available fastboot commands including the new "--slot" commands. If this list has the options --set-active[=<slot>], --slot <slot> listed towards the bottom then you're all ready to move on. (see screenshot for list of other commands you should see)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
Editing the flash-all.bat from your downloaded 7.1.2 and android o factory images
-Extract both to your working folder
-Find the "flash-all.bat" in the extracted 7.1.2 (N2G47E) right click and select "Edit"
-At this point we are going to clean the flash all up a bit. Its not a necessity but if you don't add some much needed line breaks it can get messy and confusing.
-Below i have a screen shot of what mine looks like cleaned up. Just press enter in the places i did. *Adding the line breaks does NOT mess with the code at all*
-----Toward the end of the commands you will see i added '--skip-reboot" between "update" and "image-sailfish-n2g47e.zip" This command makes it to where the device will not restart after the flash-all is finished. It is important you add this in the same place.
​-Now that we have this cleaned up, go ahead and save it really quick before we start adding to it.
-We are going to add a few "--slot" commands to it so it only installs to one slot. Below you can see what mine looks like after i added the commands. Match yours to mine (highlighted by red boxes)
-If you are on marlin, your image and zip names will be different but it's the same principal
​-after you add what i have above, save the flash-all.bat and close out of it.
Now we move over to the android o dev preview
-Open the extracted dev preview and right click on its flash-all.bat. Select "Edit"
-We are basically doing the exact same thing in this one BUT instead of the new commands being "slot _a" they will be "slot _b" (See below for the difference and we are still adding the "--skip-reboot" command)
​-Once your changes have been made in this flash-all.bat, save and close out.
Flashing the Images
Go ahead and get your Pixel into bootloader mode and plug it in.
before we start flashing we are going to clean the device up. This step will erase everything on the device.
Go into command prompt and type:
Code:
fastboot --slot _a -w
let it finish its thing then type
Code:
fastboot --slot _b -w
Device is cleaned. Now staying in bootloader type
Code:
fastboot --set-active=_b
then
Code:
fastboot reboot-bootloader
Now close out of this command prompt and run the flash-all.bat from the android o dev preview folder.
Let it do its thing and after its done, it should be left in bootloader.
now run the flash-all.bat from the 7.1.2 image folder you have.
Same thing; let it run its course and finish up.
Now you should be still in bootloader.
type in cmd
Code:
fastboot --set-active=_a
now type
Code:
fastboot reboot-bootloader
when it comes back up look at the phone and make sure is says the slot is "a" if it does, you're good to move on!
Installing TWRP and Root
From here; boot into TWRP (RC1)
-Make sure youre in slot A by going to "Reboot" then looking at the bottom (It should be slot A at this point, if its not something wasnt done correctly in the above steps)
+At this point i had the issue that my pixel would show up under "This PC" in explorer and was recognized by adb BUT none of the internal storage could be interacted with via my PC (this includes adb commands) so i couldnt get TWRP RC2 or SuperSU SR4 2.79 Extra Delay on the device to be flashed.
-To fix this: got to wipe>advanced wipe>check internal storage ONLY then wipe this partition.
-Unplug your phone and plug it back in and Windows Explorer should be able to work with the internal storage now.
-Now transfer TWRP RC2 and SuperSU sr4 2.79 Extra Delay to your Pixel
-From TWRP on your device, flash just TWRP RC2 for now. After it is installed, switch to slot b in TWRP. Then reboot to recovery.
-When TWRP comes back up, check to make sure youre in slot B still.
-If you are, now flash SuperSU SR4 2.79 Extra Delay.
-Now reboot.
-It should boot into android o, walk through setup and make sure supersu is installed.
-If it is, Congratulations you have rooted android O on your Pixel!
This method has was discovered by @Sachi315 (here)
Make sure you give him tons of thanks for getting the method up and running!
Im storing this here for my own sake testing wise please ignore https://forum.xda-developers.com/showpost.php?p=72604085&postcount=10323
Off Topic is welcome as long as its still Pixel/Root/TWRP/Development/Questions but back and forth bickering will be and should be reported.

finally, thx for this guide! will give it a try and feedback. BTW, can I share this guide with my native language? source url and your ID will be declaimed, of course.

can it be done on a locked BL?
like EE (uk) or Verizon?

y2grae said:
can it be done on a locked BL?
like EE (uk) or Verizon?
Click to expand...
Click to collapse
Nope, nor would you want to.

Queentus said:
finally, thx for this guide! will give it a try and feedback. BTW, can I share this guide with my native language? source url and your ID will be declaimed, of course.
Click to expand...
Click to collapse
As long as credit is given, by all means!!!

bobby janow said:
Nope, nor would you want to.
Click to expand...
Click to collapse
Why is that? Just curious.

bobby janow said:
Nope, nor would you want to.
Click to expand...
Click to collapse
awakenedwithin said:
Why is that? Just curious.
Click to expand...
Click to collapse
Yes I too am curious

awakenedwithin said:
Why is that? Just curious.
Click to expand...
Click to collapse
Because with a locked bootloader there are no means to recover if you screw something up. I mean none other than return the device and plead for mercy. If you want to play around, and I certainly do with my 5x, then make sure the bl is unlocked or that you can fastboot and unlock it if needed. The EE and Verizon models cannot be unlocked. I have one.

bobby janow said:
Because with a locked bootloader there are no means to recover if you screw something up. I mean none other than return the device and plead for mercy. If you want to play around, and I certainly do with my 5x, then make sure the bl is unlocked or that you can fastboot and unlock it if needed. The EE and Verizon models cannot be unlocked. I have one.
Click to expand...
Click to collapse
Oh I miss understood what you were trying to say.
Right. I should probably put unlocked bt as a requirement

eqbirvin said:
Oh I miss understood what you were trying to say.
Right. I should probably put unlocked bt as a requirement
Click to expand...
Click to collapse
You can, sure. But hopefully your walk through is read before attempting to do this and it clearly states to boot into TWRP. That's impossible with a locked bootloader.

bobby janow said:
Because with a locked bootloader there are no means to recover if you screw something up. I mean none other than return the device and plead for mercy. If you want to play around, and I certainly do with my 5x, then make sure the bl is unlocked or that you can fastboot and unlock it if needed. The EE and Verizon models cannot be unlocked. I have one.
Click to expand...
Click to collapse
Thank you for the reply!

Thanks for this. I just got a sailfish this evening. I should be trying this out tomorrow. :good:

sheesh.....becoming harder and harder to root now.....yikes

mikeprius said:
sheesh.....becoming harder and harder to root now.....yikes
Click to expand...
Click to collapse
Dev previews are always a bear at first, I do hope this doesn't become the norm though. Pixel doesn't make it any easier haha

Thanks
@eqbirvin
I successfully rooted my new sailfish with o preview following your instructions. :highfive:
One place I got stuck was not knowing that there is no recovery partition in Pixel. I tried
fastboot flash recovery twrp-3.0.2-0-RC1-fastboot-sailfish.img and obviously failed.
A little bit of searching led me to the right command
fastboot flash boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
Thank you for decoding the rather cryptic post https://forum.xda-developers.com/showpost.php?p=71865004&postcount=1266 from @Sachi315 and creating a step-by-step process that works. :good::good::good:

Is that fastboot boot twrp or fastboot flash boot twrp?
Sent from my Pixel using XDA-Developers Legacy app

bobby janow said:
Is that fastboot boot twrp or fastboot flash boot twrp?
Click to expand...
Click to collapse
Boot TWRP.img, flash doesn't work on pixels

Do you always let the phone boot up normally after stock, then go into bootloader and boot TWRP, the flash the TWRP zip ?
Afterwards, do you reboot TWRP into recovery again then stock, or just flash the .zip of TWRP then go right into stock ?
The process for this has been more confusing than the Nexus b/c there are slots a and b.

eqbirvin said:
Boot TWRP.img, flash doesn't work on pixels
Click to expand...
Click to collapse
That's what I thought. Just correcting the above post is all.

mikeprius said:
Do you always let the phone boot up normally after stock, then go into bootloader and boot TWRP, the flash the TWRP zip ?
Afterwards, do you reboot TWRP into recovery again then stock, or just flash the .zip of TWRP then go right into stock ?
The process for this has been more confusing than the Nexus b/c there are slots a and b.
Click to expand...
Click to collapse
Don't boot into system after 7.1.2 flash or Android O flash. Just boot into TWRP, flash the TWRP rc2 (after dealing with internal storage issue) change to slot b (while still in TWRP) then reboot to recovery and make sure you are in slot b again. Finally flash SuperSU package.
Ugh I know. I love the pixel but is slot/partition change is a headache haha

[Root][Oreo][Guide] How to flash and root G5 with (opt. remove encryption)

Hello guys,
after testing around for days i thought it might be helpfull to post the honestly pretty easy procedure to install stock Oreo, root it and remove encryption if needed.
Disclaimer:
I am not responsible for bricked devices, dead SD-cards, lost data, etc.
Back up your data, app settings, be sure you remember your passwords, your device will be empty!​
Edit: It seems, theres a bug that, if you read this post on XDA labs, won't show you everything, it seems like it randomly skips some parts.
What you need:
Unlocked Bootloader
Motorola USB drivers
15 sec adb and fastboot uploaded by myself since the original links aren't working anymore https://multifilemirror.com/hgxxyrfyd7rx.
I originally got them from here (you may have to go into your device manager and select the adb drivers for your phone f.e. when you want to use adb push in recovery, see original xda site).
This will also install the google drivers.
TWRP 32bit (v.3.2.3-0)
TWRP 64bit (v.3.2.1-0)
Disable Dm-Verity & ForceEncrypt from here
Magisk and MagiskManager. Newest should probably work, i used Magisk-18.0 and MagiskManager-6.1.0
Most recent Oreo firmware (edit 08.19)
(I used this Oreo firmware found in this post)
Steps:
Be sure you backed up your data and app settings, your pictures, downloads, etc. It will all be lost!
Please read all steps before you begin.
Extract the firmware into your adb folder (where you installed adb, should contain 4 files), copy both twrp (32 & 64 bit) in there, too.
Boot into bootloader (hold power+vol down) and open a terminal inside your adb folder (shift+rightclick) and type in
Code:
fastboot flash recovery name_of_twrp64bit_file.img
Boot into recovery (select recovery with vol buttons, then press power) and make a backup of EFS partition and persist folder (use file manager under advanced) and make another backup of system, boot and data and save both backups and persist to your SD-card or better your computer, too.
reboot into bootloader and check if your bootloader version is B.8.31 or above.
If it is B.8.31 or above DON'T FLASH BOOTLOADER!!! Because if you flash bootloader of the same version or below, it would hardbrick your device!
That also means if you f.e. want to downgrade to Nougat, just ignore following lines:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Also, unless youre sure your persist is absolutly ok (check here), please also omit the following lines:
Code:
fastboot erase modemst1
fastboot erase modemst2
They would reset your IMEI and usually it gets restored from your persist, but only if its not buggy.
Even if your persist is fine, as far as i know theres no harm in not using this commands (my persist is fine and i didnt use them).
Now paste following commands in your command promt in adb, in case you are BELOW B.8.31, add the bootloader commands from above between the first and second line:
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Please make sure that it really flashed all sparsechunk 0-8.
Let your phone reboot itself after installation is done, then return to bootloader and flash twrp 64bit:
Code:
fastboot flash recovery name_of_twrp64bit_file.img
Boot into recovery, since your device is encrypted it will ask for a password, click cancel, then go to WIPE and click on FORMAT DATA and confirm with yes.
This will remove the encryption of your data partition.
Go back to twrp main page and click on REBOOT then RECOVERY.
Once back in twrp, either copy Disable Disable_Dm-Verity_ForceEncrypt.zip and Magisk-18.zip and MagiskManager-6.1.apk to your SD-card or use
Code:
adb push name_of_file /external_sd
or
adb push name_of_file /sdcard
to copy the files to your SD-card (external_sd) or Internal-Storage (sdcard). For this you may have to manually configure your adb drivers in device manager, see here under Notes.
In twrp go now to INSTALL and flash "disable-dm-verity&encrypt" an then REBOOT and SYSTEM.
Return to recovery and flash "Magisk-18.0.zip", wipe Cache/Dalvik at the end and reboot System
Once System has rebooted, install MagiskManager-6.1.0.apk from your SD-card.
MagiskManager should say that Magisk is installed and in settings under security, your phone should be decrypted.
Note: MagiskManager will only show full information when it has internet access, all you see without is if Magisk is installed.
If you want to encrypt your device again, do it but flash twrp 32bit, too, if it asks for a password, it should be your usual password which you also have to enter on every boot.
Some explanation:
Why twrp 64bit?
Because twrp 32bit is able to bypass encryption, however, it causes some problems:
In fact, probably every twrp without the bypass encryption feature would work f.e. older 32bit version 3.1.0. but 64bit offers some features as EFS backup.
If you flash 32bit directly it can bypass the standard encryption but formatting data fails every time when you booted System previously.
When you reboot recovery and format data again it works, but it needs to fail first, just rebooting into recovery 2 times doesnt work.
I dont know what would happen if you (after using your phone normally) reboot recovery and f.e. want to do a backup from data, though im sure i testet it out, but i probably forgot.
You need it later when you want to encrypt your phone again, for me it didnt decrypt data after i reencrypted my phone using my password.
Why reboot System between flashing Disable-encryption and Magisk?
If you do not, you get heavy lags in the first 2 minutes after rebooting System, MagiskManager will say that Magisk isnt installed and then your phone will crash and reboot. But after that 2. reboot everything works fine again, Magisk is back, no lags.
I remembered this post from Johny Cipeli, between flashing no-verity and magisk he wrote to reboot, so i tried and it worked without lags and crash.
You don't need to remove encryption:
You can root your phone without flashing Disable_dm-verity_and_force-encrypt, use then twrp 32bit, dont format data, just flash magisk.
I can say that it should work, because that was one of my first attempts (and it worked for me), however i didnt write down what i was doing so i cant tell you step by step.
Additional:
In case you're searching Viper4Arise for Oreo, the Aroma installer won't work, use the Magisk module and install in MagiskManager. You can download it here from Zackptg5
If youre also annoyed by that One-Nav vibration, you can try using ExKernelManager app and activate the powersave mode. Although i think its officially not for G5, the app works, maybe that only refers to the Kernel and not to the app.
I tried Flyhigh Kernel, it didnt boot after flashing it, if you know a working Kernel for G5 which can disable One-Nav vibration, please write an answer.
My device:
Rooted Stock Oreo 8.1.0: OPP28.85-16
Bootloader: B.8.31
Model: XT1676 reteu
Stock Kernel
Thanks to:
Snoop05 for 15 sec adb and fastboot.
TheFixItMan for twrp.
Zackptg5 for "Universal DM-Verity, ForceEncrypt, Disk Quota Disablers".
topjohnwu for Magisk.
freeZbies for Official Oreo 8.1.0 OPP28.85-16 Fastboot Firmware.
Wolfcity, woozie.2007 and TheFixItMan for answering many of my questions!

- reserved -

ok friend, thank you for this. I think you dont need to flash twrp 64, i only flash official twrp 32, which indeed doesnt have the option for backup persist, but only efs. Maybe is someone else that will try your method to decrypt, I will try next time when I flash the stock, maybe to the next patch update. Good luck and A happy new year !!!
---------- Post added at 01:31 AM ---------- Previous post was at 01:26 AM ----------
LE: You cant root without format data partition, because flashing twrp, when twrp decrypt data you cant see anything on data partition, so you need to format it even if dont need to decrypt the phone

Nice guide @G5-User7080 .
For me everything seems to be correct, I can´t say anything device specific as I own a potter but there shouldn´t be big differences.
There´s one sentence I´m not sure about:
G5-User7080 said:
Because if you flash bootloader of the same version or below, it would hardbrick your device!
That also means if you f.e. want to downgrade to Nougat, just ignore following lines.....
Click to expand...
Click to collapse
It´s clear that downgrading the bootloader can hardbrick your device but why should there be any risk in flashing the same bootloader?
If I flash the fastboot firmware I´m on shouldn´t it be ok? Where did you get that information from?
I´m about to do that on a device of a friend of mine , he is rooted on 7.0 and wants to go the way to flash the firmware he´s on and after that take the OTA up to Oreo.
He could flash the Oreo firmware directly but he prefers to use the firmware from which he knows it´s working and is the correct one.
Very careful guy.
Edit: I just recognized that the part you called steps incl.the part I quoted isn't visible in XDA Labs, I'm only able to see it in mobile browser. Also some download links aren't there, on XDA Labs there is only the one for the 64bit recovery visible, not the one for 32bit. Maybe it's some kind of format problem, bb codes or else.

Some screenshots from XDA Labs and Chrome mobile to show the differences.

Wolfcity said:
It´s clear that downgrading the bootloader can hardbrick your device but why should there be any risk in flashing the same bootloader?
If I flash the fastboot firmware I´m on shouldn´t it be ok? Where did you get that information from?
Click to expand...
Click to collapse
I read this more then one time, although i could just find one source for now: "Flashing bootloader of equal or minor version will hardbrick your device" from Oreo Fastboot firmware.
I dont know why flashing bootloader of the same version would do lead to a hardbrick, but didnt want to try it out myself, also i see no problem in not flashing the bootloader when you already have the same version.
Wolfcity said:
Edit: I just recognized that the part you called steps incl.the part I quoted isn't visible in XDA Labs, I'm only able to see it in mobile browser. Also some download links aren't there, on XDA Labs there is only the one for the 64bit recovery visible, not the one for 32bit. Maybe it's some kind of format problem, bb codes or else.
Click to expand...
Click to collapse
Thats weird, i dont have XDA labs (thats the mobile app, right?), i wrote it on XDA desktop version and only used the size, code, color and list tags, hmm maybe it has problems with the sorted list, for every other part i used the unsorted ones with dots instead of numbers.
Quick test:
Test One:
this is made
in an unordered
list, using
list tags
Test Two:
this is now made
in an ordered list
counting from one to four
using list=1 tags
Can you read both lists with each four points?
And thanks for mentioning the bootloader thing,.. i realized i forgot to paste the lines in to flash bootloader in case you are below b8.31 ehee..

Wolfcity said:
Some screenshots from XDA Labs and Chrome mobile to show the differences.
Click to expand...
Click to collapse
wtf, it just skips random parts ?!!!
I have no idea what could cause this.. ill better add a note at the beginning of the post...wow

To flash the same vers of bootloader is not a problem, only the below one will hardbrick the phone

G5-User7080 said:
wtf, it just skips random parts ?!!!
I have no idea what could cause this.. ill better add a note at the beginning of the post...wow
Click to expand...
Click to collapse
Your lists are both readable.
I took a look at the BB codes as it's known that some of them are not working on XDA Labs like SIZE or HIGHLIGHT. In that case the BB codes are shown in the text but there's nothing missing.
Maybe it has something to do with the use of
[*] in your text?
Edit: Have you changed something in your text now? It seems to be complete on XDA Labs now too...

Wolfcity said:
Your lists are both readable.
I took a look at the BB codes as it's known that some of them are not working on XDA Labs like SIZE or HIGHLIGHT. In that case the BB codes are shown in the text but there's nothing missing.
Maybe it has something to do with the use of
[*] in your text?
Edit: Have you changed something in your text now? It seems to be complete on XDA Labs now too...
Click to expand...
Click to collapse
the [*] just create new lines for a list, and yes, i edited it two times, first, i added that one should use the bootloader commands in case of being below b831 and then i added the info about missing things on xda labs, but i didnt change anything on the lists itself,...

[GUIDE] Simpler Way to Get Rid of T-Mobile USA Branding

For those who only want custom roms - an easier way to convert from T-Mobile USA. You don't need to flash system/product/vendor partitions. No restoring modem to get signal, data will work on first boot after you install a custom rom.
This could be easily done on Linux and Windows too. I don't recommend flashall. Just do it manually. For this discussion, I am converting T-Mobile to Euro:
1. Get T-Mobile MSM package from HERE. Get Euro package (for converting) from HERE
2. Flash T-Mobile MSM (you can't transfer the MSM package via flash drive, as some files will be corrupted and you won't be able to start the package. Just download straight, unzip and execute the exe. file)
3. Boot, enable OEM unlock (you'll have to connect to the internet for a few minutes) and unlock bootloader (get unlock bin from Oneplus)
4. Once unlocked, boot again, connect to PC, enable Developer options, enable ADB. Open terminal and execute adb command:
Code:
adb reboot fastboot
You will get into 'fastbootd' recovery, but that's how it should be. Your fastboot commands will be accepted.
5. Now, unzip the downloaded Euro version, go to that directory, open terminal and execute manually the following commands separately (just copy and paste a single command from the code below) followed by pressing 'enter', i.e. paste the command, press enter, paste the next command, press enter. Watch the terminal to make sure that each command went through:
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash modem modem.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
6. Once done, don't reboot in system. Instead, reboot into bootloader. From that, follow directions to install a custom rom. If Lineage, for example, flash their recovery first (fastboot flash recovery...), then boot into that recovery. Don't flash their 'copy partitions' files. Instead, just install the latest release via 'adb-sideload' (factory reset before or after flashing is required). Then boot into System normally. Your phone will have normal IMEI/Baseband and it will be listed as IN2013.
This is only for those who want custom roms. No stock OOS updates, which vendor is not needed any way, as all custom roms for Oneplus 8 provide their own vendor.

How to Unlock Oneplus 8 tmobile Bootloader without unlock token​

farhansaeeddnp3021 said:
How to Unlock Oneplus 8 tmobile Bootloader without unlock token​
Click to expand...
Click to collapse
Short answer - Forget it, for good. Here is the long one:
Tmobile branded Oneplus 8's bootloader is tied to a key generated based on the unique numbers, which in turn, are tied to your device's unique IMEI. This is why it is a 2 step process: first, you generate a sequence of 2 long numbers on the phone. Second, you send those numbers together with your IMEI to Oneplus. Only after that, you get the token, which could only work on your phone.
This is why, at Oneplus online store, unbranded Oneplus 8 is $100 more expensive than the branded one. The latter is software crippled, and on other sites, the difference is up to $200. You get what you paid for.

optimumpro said:
Short answer - Forget it, for good. Here is the long one:
Tmobile branded Oneplus 8's bootloader is tied to a key generated based on the unique numbers, which in turn, are tied to your device's unique IMEI. This is why it is a 2 step process: first, you generate a sequence of 2 long numbers on the phone. Second, you send those numbers together with your IMEI to Oneplus. Only after that, you get the token, which could only work on your phone.
This is why, at Oneplus online store, unbranded Oneplus 8 is $100 more expensive than the branded one. The latter is software crippled, and on other sites, the difference is up to $200. You get what you paid for.
Click to expand...
Click to collapse
thanks for replay. recently i unlock oneplus 7t pro Mclarn without unlock token. so that why i was thinking about it.

farhansaeeddnp3021 said:
thanks for replay. recently i unlock oneplus 7t pro Mclarn without unlock token. so that why i was thinking about it.
Click to expand...
Click to collapse
That's because there is a modified MSM tool for Oneplus 7 with a removed device name check. That enables you to flash global firmware on any Oneplus 7 variant. This is not possible on Oneplus 8.

Hi. Im on oxygen os 11.0.4.6IN55CB. do i need to downgrade to TMO android 10 before proceed with this? My device is TMO unlocked and bootloader locked (I don't mind about the bootloader, i can unlock it anytime)

aikattx said:
Hi. Im on oxygen os 11.0.4.6IN55CB. do i need to downgrade to TMO android 10 before proceed with this? My device is TMO unlocked and bootloader locked (I don't mind about the bootloader, i can unlock it anytime)
Click to expand...
Click to collapse
No. You don't. The tool already includes the downgrade software.

Why did you link to and suggest the Euro version of this ROM? The global version is recommended if converting from T-Mobile and should be used instead. Also creates a discrepency from the title of this thread, you did not make a guide on how to convert to global, you made a guide on how to convert to the European version.
to be fair tho shouldn't really cause issues

FoxyDrew said:
Why did you link to and suggest the Euro version of this ROM? The global version is recommended if converting from T-Mobile and should be used instead. Also creates a discrepency from the title of this thread, you did not make a guide on how to convert to global, you made a guide on how to convert to the European version.
to be fair tho shouldn't really cause issues
Click to expand...
Click to collapse
You are right, but as you said, there would be no difference in the outcome, except that your phone will show IN2013 instead of IN2015.

optimumpro said:
You are right, but as you said, there would be no difference in the outcome, except that your phone will show IN2013 instead of IN2015.
Click to expand...
Click to collapse
That's not the ONLY difference, the differences there are will probably be imperceivable in daily use however. Honestly only brought it up because I saw the title of the thread and the a link to the euro ROM and was a tad confused for a sec
Edit: "or Euro" I actually audibly laughed when I saw that, that's great. Great tutorial man haha

FoxyDrew said:
That's not the ONLY difference, the differences there are will probably be imperceivable in daily use however. Honestly only brought it up because I saw the title of the thread and the a link to the euro ROM and was a tad confused for a sec
Edit: "or Euro" I actually audibly laughed when I saw that, that's great. Great tutorial man haha
Click to expand...
Click to collapse
All right. Thanks for a very useful comment. Ha-Ha!

optimumpro said:
All right. Thanks for a very useful comment. Ha-Ha!
Click to expand...
Click to collapse
Ouch you seem salty lol, I could say the same

FoxyDrew said:
Ouch you seem salty lol, I could say the same
Click to expand...
Click to collapse
That's because you seamed to sound sarcastic. "Great guide, ha-ha"

optimumpro said:
That's because you seamed to sound sarcastic. "Great guide, ha-ha"
Click to expand...
Click to collapse
oh no that was genuine lol

FoxyDrew said:
oh no that was genuine lol
Click to expand...
Click to collapse
All right. My apologies. Sometimes it's difficult to figure out intentions on the internet.

Hi and thank you so much for this guide! I'm having a problem with flashing the global rom, it tells me flashing isnt allowed for critical partitions, despite having done both the unlock (fastboot menu confirms it) and fastboot oem unlock_critical.
Has anyone seen this before?

ManlyP0tato said:
Hi and thank you so much for this guide! I'm having a problem with flashing the global rom, it tells me flashing isnt allowed for critical partitions, despite having done both the unlock (fastboot menu confirms it) and fastboot oem unlock_critical.View attachment 5426977 Has anyone seen this before?
Click to expand...
Click to collapse
Step 4: adb reboot fastboot
This has to be done on a live device with adb enabled, connected to PC and typed on PC terminal. As a result, you are not rebooting into fastboot, but in recovery with fastboot commands enabled.

optimumpro said:
Step 4: adb reboot fastboot
This has to be done on a live device with adb enabled, connected to PC and typed on PC terminal. As a result, you are not rebooting into fastboot, but in recovery with fastboot commands enabled.
Click to expand...
Click to collapse
Thanks for your reply!
Is this the difference between fastboot and fastbootd?
Despite using the command and going into fastboot I still can't seem to make it work, even selecting recovery mode in fastboot only brings me back here. I of course installed a fresh MSM version beforehand and unlocked the bootloader.
this is the screen I'm getting, is this fastboot with recovery or only fastboot?
Before reaching fastboot though it takes me to the oneplus language select screen, then gives me the option to wipe, fastboot or recovery, maybe it has something to do with this?
Thanks again for your time.

ManlyP0tato said:
Thanks for your reply!
Is this the difference between fastboot and fastbootd?
Despite using the command and going into fastboot I still can't seem to make it work, even selecting recovery mode in fastboot only brings me back here. I of course installed a fresh MSM version beforehand and unlocked the bootloader. View attachment 5426993 this is the screen I'm getting, is this fastboot with recovery or only fastboot?
View attachment 5426995
Before reaching fastboot though it takes me to the oneplus language select screen, then gives me the option to wipe, fastboot or recovery, maybe it has something to do with this?
Thanks again for your time.
Click to expand...
Click to collapse
Wrong action. You'll never be able to flash critical partitions from fastboot, i.e., the screen in your picture. After executing the adb command in step 4, your phone will enter recovery (not fastboot) and you must stay there. Nowhere my instructions say reboot to fastboot. So, stay in recovery and execute all further commands from your PC.
Edit: Yes, that's the difference between fastboot (your screen shot) and fastbootd, which is Recovery with fastboot commands support.

optimumpro said:
Wrong action. You'll never be able to flash critical partitions from fastboot, i.e., the screen in your picture. After executing the adb command in step 4, your phone will enter recovery (not fastboot) and you must stay there. Nowhere my instructions say reboot to fastboot. So, stay in recovery and execute all further commands from your PC.
Edit: Yes, that's the difference between fastboot (your screen shot) and fastbootd, which is Recovery with fastboot commands support.
Click to expand...
Click to collapse
Ooh! I see I misunderstood that, it works just fine from the recovery screen!
I tried flashing the entire global rom because I don't want a custom rom but I just got a qualcomm crashdump mode . Currently using MSM to fix that. Is it even possible to use the global rom with the Tmobile model? Otherwise I'll just use Lineage.

[ROM][STOCK][FASTBOOT] Stock OxygenOS Fastboot ROMs For OnePlus 8T

Ever wanted to unbrick your device or switch to stock ROM from a custom ROM without using MSM Unbrick tool and keeping your bootloader unlocked after that well fastboot ROMs are here to help you . 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 unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
1). Download the zip
2). Unpack the zip in a folder
3). Reboot the OnePlus 8T in fastboot-bootloader mode (Power and volume + and volume-)
4). Connect the OnePlus 8T to PC
5). Run flash-all.bat flasher
6). Wait until the process end
7). Voila! your OnePlus 8T will now boot into OxygenOS
POINTS TO REMEMBER
* "Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
* These ROMs can't be used to update or downgrade your phone but just to restore your phone.
* This can’t be used to switch from ColorOS to OxygenOS you can use MSM unbrick tool to do that.
* !!! IMPORTANT !!!
Before flashing make sure you know about which type of ram your device supports i.e LPDDR4X/LPDDR5 as flashing wrong xbl config will hardbrick your device.
Here’s how you can check what type of ram your device has:-
Now, as to exactly find out which variant that you have, turn on USB debugging and enter this command:-
Code:
adb shell getprop ro.boot.ddr_type
If the value is 0, that means you have LPDDR4X. If the value is 1, that means you have LPDDR5.
This command is more reliable than the Devcheck and other apps.
DOWNLOAD:- https://sourceforge.net/projects/op8t-9r-fastboot-roms/files/

Thank you for this...
Is there also a DL for the OP8T+ 5G firmware? Or does this ROM contain the firmware?
TIA

Wisiwyg said:
Thank you for this...
Is there also a DL for the OP8T+ 5G firmware? Or does this ROM contain the firmware?
TIA
Click to expand...
Click to collapse
This already contains firmware

Not working here, installation stops by error, and phone enters qualcomm crashdump mode.

mzmudzin said:
Not working here, installation stops by error, and phone enters qualcomm crashdump mode.
Click to expand...
Click to collapse
hmm what error? can u share a screenshot pls

Didnt make a screenshot. Tried to used this rom on op8T european version, with ddr5. Tried flash two times, both failed. Sorry that i can`t help you more.

mzmudzin said:
Didnt make a screenshot. Tried to used this rom on op8T european version, with ddr5. Tried flash two times, both failed. Sorry that i can`t help you more.
Click to expand...
Click to collapse
so u have no idea at which point it failed?

Doesn't work for me too. Flash is going well but after reboot, after splashscreen (the one of security related to unlocked bootloader) i got i crashdump. Fastboot is working, recovery is not. So i had to restore with MSM

HELLBOY017 said:
Ever wanted to unbrick your device or switch to stock ROM from a custom ROM without using MSM Unbrick tool and keeping your bootloader unlocked after that well fastboot ROMs are here to help you . 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 unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
1). Download the zip
2). Unpack the zip in a folder
3). Reboot the OnePlus 8T in fastboot-bootloader mode (Power and volume + and volume-)
4). Connect the OnePlus 8T to PC
5). Run flash-all.bat flasher
6). Wait until the process end
7). Voila! your OnePlus 8T will now boot into OxygenOS
POINTS TO REMEMBER
* "Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
* These ROMs can't be used to update or downgrade your phone but just to restore your phone.
* This can’t be used to switch from ColorOS to OxygenOS you can use MSM unbrick tool to do that.
* !!! IMPORTANT !!!
Before flashing make sure you know about which type of ram your device supports i.e LPDDR4X/LPDDR5 as flashing wrong xbl config will hardbrick your device.
Here’s how you can check what type of ram your device has:-
Now, as to exactly find out which variant that you have, turn on USB debugging and enter this command:-
Code:
adb shell getprop ro.boot.ddr_type
If the value is 0, that means you have LPDDR4X. If the value is 1, that means you have LPDDR5.
This command is more reliable than the Devcheck and other apps.
DOWNLOAD:- https://sourceforge.net/projects/op8t-9r-fastboot-roms/files/
Click to expand...
Click to collapse
Thank you!!! I've been going crazy trying to use msm tool and it didnt work. Great job!

xin chào, sau khi tôi flash nó, điện thoại của tôi không khởi động được, màn hình đen

Can you make one for the new 8t global update 11.0.11.11

Is this for ddr4 or ddr5. Tells you to check but doesn't say specific.

Thanks for this! Came in clutch tonight, wish I had seen this about a week ago! lol

kjslabber said:
Is this for ddr4 or ddr5. Tells you to check but doesn't say specific.
Click to expand...
Click to collapse
I am wondering the same thing... i can see when I look in the folder the xpl_ld5 file and the other lp5 file... do I just delete those if I have the ddr4x version???

I found out, when you run the script it will ask which DDR you have. It's all good.

kjslabber said:
Is this for ddr4 or ddr5. Tells you to check but doesn't say specific.
Click to expand...
Click to collapse
Both

Thanks @HELLBOY017 .
It worked like a charm with just a single click.

Tmobile version?
Can this be used to convert the Tmobile version to some other variant ? MSM does not work for me

how do i fix no sim error on 8t?

This worked smoothly for me and fixed my bricking. Thanks very much.
I had some issues getting fastboot to recognise my device on Windows. Turns out, USB drivers are a bit of a hassle to install, but following this thread did the trick for me: https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/

How To Guide [GUIDE][HowTo] Unlock and root Nothing Phone (1)

ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK.
THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!)
GOOD CONTINUATION TO ALL​
Hey everyone,
It's been a few days since the Phone(1) went on sale. And already, Nothing is doing things right by making the Phone(1) Kernel available. The next step was to unlock the bootloader and root it. Both are already available and ready to use.
So don't deprive yourself and here is the process of the two operations.
You've already unlocked the bootloader and rooted a carrierless variant of either a Google Pixel or OnePlus, you should have no problem unlocking your Nothing Phone (1) and installing Magisk. For those of you with a memory lapse, here is a tutorial to guide you through the process.
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine - ​
Click to expand...
Click to collapse
How to bootloader unlock and root the Nothing Phone 1​After unlocking the bootloader, you can use Magisk to root the device.
You must first unlock the bootloader in order to be able to start third-party software. Here's how to do it:
Step 1: Unlock the Nothing Phone 1’s bootloader​
Open the Settings app on your Nothing Phone 1.
Tap on About phone.
Locate the section named Software info and tap on it.
On the next screen, tap on the Build number 7 times until it says you’re now a developer.
Go back to the main Settings page, tap on System, and near the bottom of the list, you should see Developer options. Tap on it.
You should see an OEM unlocking option. Enable it. For security purposes, it may ask you to input your lock screen PIN/password if you have one set.
Scroll down a bit until you see USB debugging. Enable it as well.
Plug in your Nothing Phone 1 into your PC/Mac/Chromebook. Make sure you have the Latest version of ADB and Fastboot (33.0.3) binaries installed.
Now open up a terminal window/Command Prompt instance and enter the following command: adb devices
If you see your device’s serial number and it says “authorized,” then you’re good to go. If this is your first time setting up ADB for this device, then you may see a prompt on your phone to enable USB Debugging for your PC. Grant it permission.
If you’re having trouble getting your Windows PC to recognize your device, try installing the latest Android USB Drivers.
Now, reboot to the bootloader menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing unlock
In case you need to flash low-level firmware partitions like the bootloader images, you will have to execute another command afterwards: fastboot flashing unlock_critical
[NOT A MANDATORY TO UNLOCK CRITICAL, IT'S FOR ME BETTER TO NOT USE THIS COMMAND, THIS COMMAND COULD BE THE REASON SOME PEOPLE HAVE BRICK OR NOT WHEN GO BACK STOCK NOS]
You should now see text on screen warning you about the potential risks of unlocking the bootloader. On the screen next to the power and volume buttons, you should see some text. Press the volume up key until it says “unlock the bootloader.” Once it says this, press the power button.
The phone will unlock the bootloader and reboot back to the bootloader menu. This time, the bootloader will show a red warning icon and “unlocked” text.
Now, reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
Congratulations, your Nothing Phone 1 now has an unlocked bootloader!
You’ll see a warning message that your phone’s bootloader is unlocked on every boot, but don’t worry about that as it doesn’t affect your day-to-day use.
Step 2 - Rooting your Nothing Phone 1 with Magisk​With an unlocked bootloader, you can now boot modified boot images. For Magisk to work, you’ll need to patch the Nothing Phone 1’s stock boot image.
Since your device has been wiped earlier, you’ll need to go back and re-enable Developer Options and then re-enable USB Debugging. Make sure your Nothing Phone 1 is still recognized by your PC.
Download the full OTA package corresponding to the installed software version on the Nothing Phone 1.
Depending of your model, you have Global or EEA (European) firmware availables.
You can download the latest full OTA firmware package here.
Extract the stock boot image from the OTA package. For more information, take a look the “You have access to the recovery-flashable ZIP file” section our “How to Install Magisk on your Android Phone” tutorial.
In case you don’t want to download the whole OTA file, you can separately download the boot image just to the post #2 or from this post. However, to avoid version mismatch and other unforeseen errors, it is always advised to extract the boot image yourself.
Now that we have the stock boot image to patch, push it to your device with this command: adb push <path_to_file> /sdcard/Download
Download and install the Magisk app on the Nothing Phone 1.
Open the Magisk app and tap on the Install button.
Choose Select and Patch a File. A file manager will pop up.
Select the boot image that you pushed earlier and let Magisk patch it.
Pull it off your phone with this command: adb pull /sdcard/Download/magisk_patched_[random_strings].img
Reboot the Phone 1 into the bootloader: adb reboot bootloader
Flash the patched boot image: fastboot flash boot /path/to/magisk_patched_boot.img
Reboot the phone: fastboot reboot
Open the Magisk app and your Nothing Phone 1 should be rooted.
Keep in mind that unlocking the bootloader and rooting your Nothing Phone 1 will impact how you take advantage of updates. You'll have to learn to manually load monthly security patch updates. But don't worry, it's easy enough to do.​
-=o#0#o=-​
WARNING: I wrote this step to allow you to re-lock your bootloader, but it seems that for this step, there are some problems. So after this warning, if you continue on this path, I could not be held responsible for what you will have as a result: soft-bricked, bootloop, etc.​
Spoiler: Relock the bootloader of your Phone(1)
menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
[*]Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing lock
[*]Reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
Many thanks to Skanda Hazarika for his tutorial which you can read on the xda news page.
And thanks to Qiyue_ for the 1st Boot Magisk Patched for the Phone1
#root #nothingphone

Unbricking Nothing phone 1: Flash Stock Firmware with Fastboot
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -​
Click to expand...
Click to collapse
Warning : The process below will erase all the data on your device. So, I invite you to make a full backup of the device beforehand.
Unfortunately, as I don't own the Phone(1) yet, I am unable to take screenshots with the Phone(1) at the moment. As soon as I can, I will put them online to finalize the tutorial. Thank you for your understanding
STEP 1: What you need and read before the process.
It’s really important for a process without problems
Install Android SDK and the Platform-tools folder
Download the Nothing OS version you need (see this post)
Extract the "payload bin" file from the rom
Extract the Firmware Stock "boot.img" from the rom (see this tutorial)
Unlock the bootloader of your Phone(1) (see this tutorial)
STEP 2: Boot the bricked phone 1 into Fastboot mode
Very often, a soft-bricked or boot-looped device may already be in Fastboot mode. However, if you are stuck in a boot-loop, long press the Power key to turn it off.
Then press and hold the Power and Volume Down keys (or Power and Volume Up keys on some devices) simultaneously to boot your device into Fastboot mode.
In case you are unable to turn off your device, let the battery discharge. Once it is drained, connect it to the charger. Then, as soon as it is about to start, use the Power and Volume Up/Down keys and it will start directly in Fastboot mode.
STEP 3: Format the device via Fastboot
1.Go to the platform-tools folder where the extracted ROM is located.
2.Then go to its address bar, type CMD in its address, and press Enter. This will launch the CMD window.
3.Now run the following command to perform a factory reset (optional but recommended)
Code:
fastboot -w
STEP 4: Flash the Nothing Phone 1 firmware via the Fastboot commands
Run the commands below in the CMD window [which is open in the platform-tools folder] to flash the partition file.
Very Important: Only run one command at a time. If you get an error, however, do not exit the process halfway, but go on to the next flashing command instead.
Don't forget to check your command line before validating it, because often a small error blocks you!
Spoiler: Command Lines
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash devcfg devcfg.img
flash fastboot dsp dsp.img
flash fastboot dtbo dtbo.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img fastboot
fastboot flash product product.img
fastboot flash qupfw qupfw.img
flash fastboot shrm shrm.img
flash fastboot system system.img
flash fastboot system_ext system_ext.img
flash fastboot tz tz.img
flash fastboot uefisecapp uefisecapp.img
flash fastboot vbmeta vbmeta.img
flash fastboot vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash vendor_boot vendor_boot.img
flash fastboot xbl xbl.img
fastboot flash xbl_config xbl_config.img
Step 5: If you have not had any errors, then you can run the command below to boot your device onto the operating system.
Code:
fastboot reboot
Well done , you have just debricked your Nothing Phone 1 by flashing the stock firmware via the fastboot commands.
I hope this tutorial has helped you find your Phone(1).
Thanks

Reserved

FILES FOR NOTHING OS - (stock-boot, etc. )
UPDATE 15/12/2022
Stock_Boot for Nothing OS here
Be carefull, be sure to select the good Stock Boot "Global" or "EEA" for your device.​

Extract Payload.bin via Payload Dumper Go
To start, download the payload-dumper-go 1.0.0 from Github [Credits: XDA Member @ssssut].
Then extract it to any convenient location on your PC. The file name will be something like payload-dumper-go_1.0.0_windows_amd64.
Rename it to payload-dumper-go.
Next, download the liblzma-5.dll file and transfer it to the same folder where the payload-dumper-go.exe file is located.
After that, transfer the payload.bin file to this folder as well.
So, from now on, you should have the 3 files payload-dumper-go.exe, payload.bin and liblzma-5.dll in one folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to the address bar of that folder, type "cmd" and press Enter. This will launch the command prompt window.
Type the command below to extract the payload.bin file:
Code:
payload-dumper-go payload.bin
The extraction process will now begin and will only take a few seconds.
Once this is done, all extracted files will be placed in a folder named extract_date_time which is created in this directory like this name : extracted_20220731_145751
The process is very simple and very fast. Anyone can do it. So don't hesitate, you have everything you need to do this yourself.
it's up to you now
If this has helped you, and if you appreciate my help.
Thanks

Is it possible to relock the bootloader?
Is it possible to relock the bootloader on an third party ROM?

@Sib64 does the device keep Widevine L1 when the bootloader has been unlocked?

Krullendhaar said:
Is it possible to relock the bootloader?
Click to expand...
Click to collapse
Yes.
Krullendhaar said:
Is it possible to relock the bootloader on an third party ROM?
Click to expand...
Click to collapse
No.

Could you also do a tutorial on how to update the OS when you're rooted?

I hope to find an EDL QPST full rom... better to stay safe and restore It in any case...
Mod is coming...

I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.

ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Is rooting success with 1.1.0 Rom?

Naveenakash said:
Is rooting success with 1.1.0 Rom?
Click to expand...
Click to collapse
I didn't try it with an actual app, but it was showing properly in Magisk. But bootloader needs to stay unlocked.

ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Did you fix that issue?

Naveenakash said:
Did you fix that issue?
Click to expand...
Click to collapse
I didn't. I'm trying to factory reset the phone, but I can't seem to flash the ROM from bootloader.

ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Hi! I don't know what the best solution would be, but I would definitely try it if I access the fastboot mode from recovery, reunlock the previously modded and closed bootloader, that is currently on the phone. Ater restarting the phone and its boots up, i would put back the one corresponding to the original software's in recovery fastboot mode and then close it. if the phone started, I do the next sw ota update, restart it and patch its bootloader with magic, then open again the new sw's bootloader from fastboot then flash the magisk patched one. But with thiese solution, you will lose all of your data and application from the phone, same like after you first unlocked the bootloader. ( like factory reset ). I hope it's understandable, unfortunately my English is not very good.

No matter from which partition (A/B)
lba810701 said:
Hi! I don't know what the best solution would be, but I would definitely try it if I access the fastboot mode from recovery, reunlock the previously modded and closed bootloader, that is currently on the phone. Ater restarting the phone and its boots up, i would put back the one corresponding to the original software's in recovery fastboot mode and then close it. if the phone started, I do the next sw ota update, restart it and patch its bootloader with magic, then open again the new sw's bootloader from fastboot then flash the magisk patched one. But with thiese solution, you will lose all of your data and application from the phone, same like after you first unlocked the bootloader. ( like factory reset ). I hope it's understandable, unfortunately my English is not very good.
Click to expand...
Click to collapse
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.

ErChisus said:
No matter from which partition (A/B)
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
Click to expand...
Click to collapse
And what if you flash back the original bootloader to over the unlocked one, and after it you close it, not the modded one?

ErChisus said:
No matter from which partition (A/B)
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
Click to expand...
Click to collapse
Also, doing a factory reset from recovery doesn't relock the bootloader either.

I've tried now to sideload the .zip but it seems that even the supposed 1.1.0 full OTA zip available in the other post is older than my current ROM, so it can't be flashed like that. I'll have to wait for the next update.