Database Users

[solved] Flash CWM despite green android bot in recovery?

Hello,
I updated my UK Xoom 3G (MZ601) via OTA to 3.2 (H.6.5-17-3) last year.
Since I got interested in rooting the device I read I have to install CWM first.
However, when going into recovery mode (for testing) all I get is a green android bot.
Thanks to some googling I found some website that mentions to hold the power button (while the green android bot is shown) and press volume up, then release the power key. Now I see the stock 3e recovery menu.
Is it safe to simply unlock the bootloader and flash CWM via ADB? Or am I required to flash back to the xoom dev stock rom because of the green fella? My question refers to this part:
Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Not sure why I would have to do that? In the end, I'd want to have a rooted stock 3.2.

First unlock it indeed while seeing the green bot in recovery.
(using the commands you posted yourself)
Then, you back into recovery, and push the new cwm recovery using adb
(look on the xda xoom's section: you'll find the right tutorial; should start with downloading adb, downloading cwm into the same directory as where you put the adb drivers for the xoom. Then open command as administrator, etc.)
After that, you should have CWM (or I recommend the touch Rogue recovery! ) on your Xoom, instead of the ugly little green bot, now allowing you to flash many, many ROMs, zips and many other to your device!
Enjoy. Hope this is clear enough and helps you towards the right direction! (if so, please do thank me, since I only just made an XDA account and would like at least one thanked post lol.
If not, please PM me or ask further explanations in this thread! )

adelancker said:
First unlock it indeed while seeing the green bot in recovery.
(using the commands you posted yourself)
Click to expand...
Click to collapse
I suppose you only refer to the adb commands without flashing the img files, right?
I still don't know why that other thread suggested to flash back to an older version first (see quote in my first posting)? Can anyone tell me if I have to downgrade at all?

Landorin said:
I suppose you only refer to the adb commands without flashing the img files, right?
I still don't know why that other thread suggested to flash back to an older version first (see quote in my first posting)? Can anyone tell me if I have to downgrade at all?
Click to expand...
Click to collapse
First unlock it using those fastboot commands you posted. You should in this series of commands not flash anything yet. Just unlock it first. When rebooting and showing the Moto logo:
Get back into recovery and then push the new recovery.img using adb commands
As far as I know, there is not one reason to downgrade. Should work just fine.
---------- Post added at 01:23 PM ---------- Previous post was at 01:05 PM ----------
adelancker said:
First unlock it using those fastboot commands you posted. You should in this series of commands not flash anything yet. Just unlock it first. When rebooting and showing the Moto logo:
Get back into recovery and then push the new recovery.img using adb commands
As far as I know, there is not one reason to downgrade. Should work just fine.
Click to expand...
Click to collapse
Otherwise, use this as your guideline and you should be fine:
http://forum.xda-developers.com/showthread.php?t=1249798

Thank you! All worked out fine. I followed the guide step by step, I did not downgrade the existing ROM.
In case someone else gets into the same situation and wonders how to do it:
once everything is set up for ADB and the device is found (command adb devices) type this in your command prompt window:
Code:
adb reboot bootloader
waited for fastboot protocol text to show up on Xoom device, then:
Code:
fastboot oem unlock
Confirmed the warning. Then had the device booting up normally to re-enable USB debugging. Then continued:
Code:
adb reboot bootloader
again waited for fastboot protocol text to show up on Xoom device, then:
Code:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
When it said flashing done I restarted the Xoom (holding power button + volume up). About 3-4 sec after seeing the Motorola pic I hit volume down ("android recovery" is displayed), then volume up and CWM showed up.
Since I was already in CWM I also applied the universal root method ("install zip from sdcard" -> "choose zip from sdcard", then selected the actual file on the sd card, installed it, rebooted). Root works.
P.S.: just realized silly me forgot to do a nanddump before rooting.

something like forgetting a nanddump only happens once!
Glad to see it worked for you!
Even happier to see you didn't need to downgrade.
Once you flash a custom ROM, you'll have 3G and ICS!
I did the same a couple of months ago, and my device felt brand new!

Going back to Sense from [RUU] Google Edition Conversion.Graffixync UPDATE 12th May

EDIT - UPDATED INSTRUCTIONS 12th May 2014
Due to the partition sizes being different in the GPE RUU it is not simply a case of flashing a sense rom in recovery. You will experience problems if you do this. This might involve getting the storage encrption message, bootloops, freezing etc etc.
This thread is specifically for users who have problems getting back to sense. Solution is below. If you have alternative solutions that have worked without issues please post.
I have tried to make them as simple as possible. This guide assumes you are S-Off otherwise how did you get here. (
This does not apply if you have installed a GPE ROM. You can flash as normal through recovery. (using instructions of new rom)
Thanks to @exad for his continuing support/assistance throughout the thread, as well as @graffixnyc for the GPE RUU and both he and @navalynt for finding the initial fixes.
It will be much easier if you have your new Rom on your external sdcard prior to starting this. It will also stop a number of problems if you have SuperCID (11111111) If you don't know how to - FASTBOOT Commands
1. Enter the command "fastboot oem readcid". Make and KEEP a note of your original CID.
2. Enter the command "fastboot oem writecid 11111111"
3. Enter the command "fastboot read cid" [it should confirm your CID is 11111111]
4. Press the volume down button twice on your phone and navigate to reboot bootloader, then hit power button to reboot the bootloader.
5. Bootloader will also say "CID-11111111" now to confirm (Thanks to @xl VipeR lx ) Also to @umjammerlammy for the GENTLE reminders to include this
Make sure the firmware file and twrp recovery are in your Android directory on your PC - Mine is
C:\Users\Grentuu\AppData\Local\Android\android-sdk\platform-tools\
During this process you may find that when you reboot the phone starts to boot into android. Mine did but simply had the GPE animated logo but never entered GPE. All you do is press Vol up and power for about 10 seconds to reset. As soon as it resets press vol down and power to get back to bootloader.
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Some users have stated this firmware (1.54.401.5) did not work for them as they weren't GSM and reboots just threw them back to recovery. If this happens try a stock (your original e.g. T-mobile) firmware then follow the rest of the process.
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
These have worked for me everytime (Change count =19)

Thanks for this. I'm about to give it a shot now.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 04:40 PM ----------
For some reason the firmware wont flash in twrp. Should I sideload the firmware?
Sent from my GT-P5210 using XDA Premium 4 mobile app

To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader

exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firnwarefilename.zip
Then again
Fastboot flash zip firnwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks. Understood, I was just reviewing my steps for the conversion. I really just want to try out that new Sense rom and then I'll probably revert back. BRB...I'll let you know how it goes.

Bear in mind you must have S-off to flash a firmware that way.

exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Those are the instructions in post 1 the original thread.
The issue is with people wanting to go back to sense

This thread is about returning to sense. Flashing a firmware is always the same. It's the firmware itself that's different...

Here is where I am at..
I converted to GP easily and it worked well.. I wanted to convert back so I installed twrp first, then through twrp installed the 1.54.401.5 firmware.
Installing that firmware removed twrp and the rom. So I am without an OS at all, and have stock recovery.
Is there anyway I can flash a custom recovery or a rom via the stock firmware/recovery?
My computer will not recognize adb devices. But it used to obviously.
I have an SD card.
Any help and I will be sooo grateful. (maybe even donate)
Thanks!

You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.

Thanks will try it out.

exad said:
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Click to expand...
Click to collapse
So what do I do in this situation with no rom installed only 1.54 firmware and stock recovery.

Flash twrp

exad said:
Flash twrp
Click to expand...
Click to collapse
I have no rom installed, so it wont show in adb devices.

PunchLick said:
I have no rom installed, so it wont show in adb devices.
Click to expand...
Click to collapse
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.

Dmaxon said:
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Click to expand...
Click to collapse
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.

PunchLick said:
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
Click to expand...
Click to collapse
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...

Why post steps if your not willing to help?
The steps in the OP can still cause issues for some people.
Sent from my HTC One_M8 using Tapatalk

Ideas4ya said:
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Click to expand...
Click to collapse
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!

PunchLick said:
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
Click to expand...
Click to collapse
When you open the all in one...the 3rd option on the top right is what you need. Follow the step, even if fastboot says device is not connected, this will still send the recovery to your device as long as you're in the bootloader.

I will never understand why people play with there phones and have no understanding of adb and fastboot commands with the bootloader. if people would learn that first there wouldn't be so many threads when they get stuck. tool kits are bad it makes people lazy. but I appreciate the devs who make them

[HOW TO] How to Root 5.1 with (unlocked bootloader)

I've seen posts requesting "how to" and posts of problems attempting to root after installing the 5.1 OTA update. This post outlines the steps to root with an UNLOCKED BOOTLOADER.
NOTE: This will only work if your bootloader is already unlocked. It is based on -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 but slightly updated.
Don't know if your bootloader can be unlocked? see -> HERE
Requirements...
the latest TWRP fastboot IMG file (Alternate Link) UPDATE: There is an issue with TWRP 2.8.7.0 (SEE THIS POST Thanks @jodaboda ). Please use TWRP 2.8.6.0 for now!
the latest Installable ZIP of SuperSU (Alternate: http://download.chainfire.eu/supersu )
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools will likely work, but Moto's fastboot is always suggested!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The steps...
NOTE: replace TWRP.IMG in the below steps, with the name of the file you downloaded!! Example: twrp-2.8.6.0-ghost.img
NOTE: failure to perform these steps EXACTLY as written can result in the apparence of the Android in distress (logo with Exclamation mark) with the caption "No Command" and the inability to enter recovery, OR it will enter STOCK recovery even though you have flashed TWRP!
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you downloaded your TWRP.IMG file.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery TWRP.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device should enter TWRP.
If your device is not rooted, TWRP may prompt you to root now or install SuperSU. Do it.
Use the menu options to Reboot to system.
You will likely be prompted to UPDATE SuperSU. Please update it, and reboot.
IF TWRP doesn't prompt you to root/install SuperSU.... (more exact instructions coming later...)
With your phone booted normally, connect it via USB cable to your PC.
Drag/Drop the SuperSU.zip you downloaded onto the phone's internal storage
Reboot the phone into TWRP
Use the menu option to install zip, navigate to and select the SuperSU zip.
Boot to System.
EDIT: 9-17-2015 edited first TWRP link.

KidJoe said:
I've seen posts requesting "how to" and posts of problems attempting to root after installing the 5.1 OTA update. This post outlines the steps to root with an UNLOCKED BOOTLOADER.
NOTE: This will only work if your bootloader is already unlocked. It is based on -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 but slightly updated.
Don't know if your bootloader can be unlocked? see -> HERE
Requirements...
the latest TWRP fastboot IMG file (Alternate Link)
the latest Installable ZIP of SuperSU (Alternate: http://download.chainfire.eu/supersu )
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools will likely work, but Moto's fastboot is always suggested!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The steps...
NOTE: replace TWRP.IMG in the below steps, with the name of the file you downloaded!! Example: twrp-2.8.6.0-ghost.img
NOTE: failure to perform these steps EXACTLY as written can result in the apparence of the Android in distress (logo with Exclamation mark) with the caption "No Command" and the inability to enter recovery, OR it will enter STOCK recovery even though you have flashed TWRP!
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you downloaded your TWRP.IMG file.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery TWRP.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device should enter TWRP.
If your device is not rooted, TWRP may prompt you to root now or install SuperSU. Do it.
Use the menu options to Reboot to system.
You will likely be prompted to UPDATE SuperSU. Please update it, and reboot.
IF TWRP doesn't prompt you to root/install SuperSU.... (more exact instructions coming later...)
With your phone booted normally, connect it via USB cable to your PC.
Drag/Drop the SuperSU.zip you downloaded onto the phone's internal storage
Reboot the phone into TWRP
Use the menu option to install zip, navigate to and select the SuperSU zip.
Boot to System.
Click to expand...
Click to collapse
I still haven't unlocked my Bootloader (being on 5.1). In the linked post it's been mentioned that "TWRP custom recovery for KitKat" - my question is, is there a TWRP Custom Recover for OTA 5.1 update? And I'm on XT1052, same procedure follows?

Do you know where I can find mfastboot for Mac OSX?

kidjoe, your a priceless resource!
i installed an older verison of twrp and had all the issues you speak off, installed 2.8.6 with success but would not root upon reboot, installed the super su zip in op via twrp, one last thing i had to enter the super su app and tap enable superuser and now all is good:good::good

Thanks, worked like a charm

Thanks.. It's been ages since I used I last used adb commands and flashed something. I couldn't figure out how to boot into recovery.

Vampirexox said:
I still haven't unlocked my Bootloader (being on 5.1). In the linked post it's been mentioned that "TWRP custom recovery for KitKat" - my question is, is there a TWRP Custom Recover for OTA 5.1 update? And I'm on XT1052, same procedure follows?
Click to expand...
Click to collapse
twrp-2.8.6.0-ghost.img works on Lollipop too. (just used it last night on my sister-in-law's GSM Dev Edition XT1053 that got the lollipop update)

jay_em said:
Do you know where I can find mfastboot for Mac OSX?
Click to expand...
Click to collapse
Here is a copy on my Box 'drive':
https://app.box.com/s/5nlgy2avccupw4box8z2be50ezt4qn7p
EDIT: I just got an e-mail saying it had been downloaded. :good:
---------- Post added at 08:54 AM ---------- Previous post was at 08:45 AM ----------
kyzn said:
Thanks.. It's been ages since I used I last used adb commands and flashed something. I couldn't figure out how to boot into recovery.
Click to expand...
Click to collapse
EDIT: [If you are still running the stock Recovery] You can also use:
Code:
adb reboot recovery
When you see the horizontal robot hold the Volume Up key for 3 seconds and then tap Power and the Recovery Menu will display.

Thanx for this how-to. Everyone has been getting confused in root process for 5.1 although it is nearly same as 4.4.4.
Sent from my XT1052

I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!

jodaboda said:
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
Click to expand...
Click to collapse
I had the same issue with my XT1053. Following your advice did the trick. Not being able to modify my dpi since upgrading has been killing me. Its the only thing i really want root for. Thanks for everything both you and op!

jodaboda said:
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
Click to expand...
Click to collapse
Ahh... 2.8.7 wasn't out when I tried.. 2.8.6 was the latest at that time. Maybe there is a bug in 2.8.7 that will get fixed in future versions?

Sunshine unlocked bootloader
Does anyone know if there are any issues resulting from a Sunshine unlocked bootloader? I saw one post that had a warning but it was a warning because there was no information at the time. Has this change?

i installed TWRP successful, but after normal reset, TWRP is gone, it's only stock recovery (Android down image). Please help me. My phone is running 5.1 update OTA, unlocked bootloader

md07 said:
i installed TWRP successful, but after normal reset, TWRP is gone, it's only stock recovery (Android down image). Please help me. My phone is running 5.1 update OTA, unlocked bootloader
Click to expand...
Click to collapse
When you say "installed TWRP successful"... do you mean that fastboot didn't error? or that fastboot completed the install, you did a mfastboot reboot-bootloader, and tried entering TWRP but it still gave you the "dead android" image?

Is there any unofficial way to unlock bootloader?
Sent from my Nexus 7 using Tapatalk

I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!

djibril13 said:
Is there any unofficial way to unlock bootloader?
Click to expand...
Click to collapse
Sunshine... IF you're phone has never been upgraded to 4.4.4.
BUT if you can get unlock code from Moto, while it can void your warranty (depending on your local laws), that is FREE, and the best way.

SX86 said:
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
Click to expand...
Click to collapse
help me understand your situation...
You are doing.. Mfastboot flash recovery -> mfastboot reboot-bootloader -> you get battery charging screen rather than fasboot/bootloader menu/screen?
or ??

SX86 said:
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
Click to expand...
Click to collapse
after flashing did you but to recovery befour booting system? with my experience i had to boot to recovery first befour system

Do you know how recovery essential phone from the corrupt?

After several steps after installed twrp, now my essential phone is like these:
{
"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"
}

Chiminwon said:
After several steps after installed twrp, now my essential phone is like these:
Click to expand...
Click to collapse
Could you rephrase what your question is? I would like to help but can't figure out what you are explaining. I'm assuming you have unlocked the bootloader. I had some problems with this phone at first too. Most of the problems when compared to other phones is that Essential Phone has 2 partitions, like the Pixel. For simplicity, one is sort of the ACTIVE side and the other INACTIVE side. It has some learning. If you are just trying to get up and running try these steps...
1- Wipe data using fastboot command fastboot -w ---- locate the Stock ROM section in Essentials forum here on XDA and get the current STOCK build for your needs. Download it. And flash it in fastboot using the flash-all.bat file. Most will flash the files to both partitions, if it does not use the command in the next step to switch partitions and flash the other side too. This will set your phone back to stock and it should boot nicely. If you wish to root then proceed. BOOT INTO THE STOCK OS EVEN IF YOU ARE STILL GOING TO ROOT THE DEVICE. JUST BOOT UP, THEN REBOOT TO THE BOOTLOADER. DONT SIGN INTO YOUR GOOGLE AND DO NOT SET LOCK OR PASSWORD OR FINGERPRINT YET
2- Follow step one and then reboot into fastboot and use command fastboot set_active other --------- this will do two things. It will switch your partition and also tell you which one it switched to. There is an A side and a B sideFOR THIS EXAMPLE WE WILL PRETEND THAT AFTERYOU SWITCHED YOU ARE ON SIDE B
3- Stay in fastboot and flash twrp11mata using fastboot command fastboot flash boot exactTWRPfilename.img ------ this will boot you into TWRP on the B side
This next rule is very importantTWRP flashes a zip and a img file different. ZIP ROM FILES FLASH TO THE OPPOSITE PARTITION, IMG FILES flash to the partition that you are currently using. So, if you booted into TWRP on the "b" side and without switching flashed a new kernel or boot image it would install to the same "b" side you are on. If you did the same with a ROM it would install to the 'a" side. So, at some point you have to switch sides from within TWRP in the Reboot tab.
4- Copy your Roms/files to your phones internal memory and then flash using twrp. Flash the ROM not sideload. Flashing is for new roms, sideload is for updates to existing ROM. Back to our example, you booted into TWRP on side b, if you install new rom it will install on side A. Lets keep that idea going for the example. BE AWARE THAT IN THIS TYPE OF DEVICE, using our example where we flashed the rom to the A side (from TWRP on the B side), that side will not have TWRP. It will have stock recovery.
5- once the rom is flashed reboot system. (wipe cache / dont wipe cache.. I havent noticed a difference with either mindset) It will switch your partitions upon reboot if you don't do anything else in twrp.
So for our example this is what happened:
Wiped data from both partitions of the PH-1, side "a" and side "b"
Went BACK-TO-STOCK on BOTH sides
BOOTED INTO STOCK ROM ON THE SIDE WE WISH TO BE OUR ACTIVE SIDE***DID NOT SET UP GOOGLE OR PIN/FINGERPRINT/PASSCODE****
reboot into bootloader
Used Fastboot to switch partitions and installed TWRP to the INACTIVE side. Boot into twrp.
In TWRP, copied new files to phone storage the flashed new ROM Remember it will install it to the other side which is our ACTIVE side
reboot system.
If this helped at all and got you running great. Rooting is simple from here. This phone was the first device I ever rooted so I took my lumps so I hope I offered some tips that I didn't find or understand fully at first. Happy exploring. Ask away if I can help further.

KingBeefy said:
Could you rephrase what your question is? I would like to help but can't figure out what you are explaining. I'm assuming you have unlocked the bootloader. I had some problems with this phone at first too. Most of the problems when compared to other phones is that Essential Phone has 2 partitions, like the Pixel. For simplicity, one is sort of the ACTIVE side and the other INACTIVE side. It has some learning. If you are just trying to get up and running try these steps...
1- Wipe data using fastboot command fastboot -w ---- locate the Stock ROM section in Essentials forum here on XDA and get the current STOCK build for your needs. Download it. And flash it in fastboot using the flash-all.bat file. Most will flash the files to both partitions, if it does not use the command in the next step to switch partitions and flash the other side too. This will set your phone back to stock and it should boot nicely. If you wish to root then proceed. BOOT INTO THE STOCK OS EVEN IF YOU ARE STILL GOING TO ROOT THE DEVICE. JUST BOOT UP, THEN REBOOT TO THE BOOTLOADER. DONT SIGN INTO YOUR GOOGLE AND DO NOT SET LOCK OR PASSWORD OR FINGERPRINT YET
2- Follow step one and then reboot into fastboot and use command fastboot set_active other --------- this will do two things. It will switch your partition and also tell you which one it switched to. There is an A side and a B sideFOR THIS EXAMPLE WE WILL PRETEND THAT AFTERYOU SWITCHED YOU ARE ON SIDE B
3- Stay in fastboot and flash twrp11mata using fastboot command fastboot flash boot exactTWRPfilename.img ------ this will boot you into TWRP on the B side
This next rule is very importantTWRP flashes a zip and a img file different. ZIP ROM FILES FLASH TO THE OPPOSITE PARTITION, IMG FILES flash to the partition that you are currently using. So, if you booted into TWRP on the "b" side and without switching flashed a new kernel or boot image it would install to the same "b" side you are on. If you did the same with a ROM it would install to the 'a" side. So, at some point you have to switch sides from within TWRP in the Reboot tab.
4- Copy your Roms/files to your phones internal memory and then flash using twrp. Flash the ROM not sideload. Flashing is for new roms, sideload is for updates to existing ROM. Back to our example, you booted into TWRP on side b, if you install new rom it will install on side A. Lets keep that idea going for the example. BE AWARE THAT IN THIS TYPE OF DEVICE, using our example where we flashed the rom to the A side (from TWRP on the B side), that side will not have TWRP. It will have stock recovery.
5- once the rom is flashed reboot system. (wipe cache / dont wipe cache.. I havent noticed a difference with either mindset) It will switch your partitions upon reboot if you don't do anything else in twrp.
So for our example this is what happened:
Wiped data from both partitions of the PH-1, side "a" and side "b"
Went BACK-TO-STOCK on BOTH sides
BOOTED INTO STOCK ROM ON THE SIDE WE WISH TO BE OUR ACTIVE SIDE***DID NOT SET UP GOOGLE OR PIN/FINGERPRINT/PASSCODE****
reboot into bootloader
Used Fastboot to switch partitions and installed TWRP to the INACTIVE side. Boot into twrp.
In TWRP, copied new files to phone storage the flashed new ROM Remember it will install it to the other side which is our ACTIVE side
reboot system.
If this helped at all and got you running great. Rooting is simple from here. This phone was the first device I ever rooted so I took my lumps so I hope I offered some tips that I didn't find or understand fully at first. Happy exploring. Ask away if I can help further.
Click to expand...
Click to collapse
Hello
I have an essential ph1 phone I bought new from a friend
I registered my google account and secured the phone with a fingerprint
While the update request protection orio8.1 agreed to download and update
Complete the phone Download the update The installation process then stuck a logo ,,
Now the phone is working on fastboot mode only
I can not log into recovery
bootloader lock
oem lock
usb debogen lock
I could not flash any picture ....
I hope anyone who can help me help me solve the problem and thank you

@mouraj2 have you done both commands:
Fastboot flashing unlock
Fastboot flashing unlock critical
---both are needed
Also, I'd recommend getting the current build for your ph-1 from here on xda or essential. Find the firmware you need/want and flash the BTS (back to stock) flash-all.bat. That flashes from fastboot lol. Don't download the OTA get the images file. Easier.
I don't know much about modding phones in general but i can work my way around a ph-1 for sure lol. PM me if u have any more questions

KingBeefy said:
@mouraj2 have you done both commands:
Fastboot flashing unlock
Fastboot flashing unlock critical
---both are needed
Also, I'd recommend getting the current build for your ph-1 from here on xda or essential. Find the firmware you need/want and flash the BTS (back to stock) flash-all.bat. That flashes from fastboot lol. Don't download the OTA get the images file. Easier.
I don't know much about modding phones in general but i can work my way around a ph-1 for sure lol. PM me if u have any more questions
Click to expand...
Click to collapse
The bootloader does not open
C:\Program Files (x86)\Minimal ADB and Fastboot>Fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: -0.000s

mouraj2 said:
The bootloader does not open
C:\Program Files (x86)\Minimal ADB and Fastboot>Fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: -0.000s
Click to expand...
Click to collapse
You need to boot the phone and get into developer mode.
You will need to go into settings, about and tap the build 7 times.
Then go into developer settings and enable boot loader unlock.

tech_head said:
You need to boot the phone and get into developer mode.
You will need to go into settings, about and tap the build 7 times.
Then go into developer settings and enable boot loader unlock.
Click to expand...
Click to collapse
I can not phone stuck on the logo
It does not go into recovery also attached to the logo

mouraj2 said:
The bootloader does not open
C:\Program Files (x86)\Minimal ADB and Fastboot>Fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: -0.000s
Click to expand...
Click to collapse
Go to the essential website and download the latest windows drivers for the PH-1. It's not communicating with the phone. When you type the command "fastboot devices" it is probably not showing any connection to the device , right ?

KingBeefy said:
Could you rephrase what your question is? I would like to help but can't figure out what you are explaining. I'm assuming you have unlocked the bootloader. I had some problems with this phone at first too. Most of the problems when compared to other phones is that Essential Phone has 2 partitions, like the Pixel. For simplicity, one is sort of the ACTIVE side and the other INACTIVE side. It has some learning. If you are just trying to get up and running try these steps...
1- Wipe data using fastboot command fastboot -w ---- locate the Stock ROM section in Essentials forum here on XDA and get the current STOCK build for your needs. Download it. And flash it in fastboot using the flash-all.bat file. Most will flash the files to both partitions, if it does not use the command in the next step to switch partitions and flash the other side too. This will set your phone back to stock and it should boot nicely. If you wish to root then proceed. BOOT INTO THE STOCK OS EVEN IF YOU ARE STILL GOING TO ROOT THE DEVICE. JUST BOOT UP, THEN REBOOT TO THE BOOTLOADER. DONT SIGN INTO YOUR GOOGLE AND DO NOT SET LOCK OR PASSWORD OR FINGERPRINT YET
2- Follow step one and then reboot into fastboot and use command fastboot set_active other --------- this will do two things. It will switch your partition and also tell you which one it switched to. There is an A side and a B sideFOR THIS EXAMPLE WE WILL PRETEND THAT AFTERYOU SWITCHED YOU ARE ON SIDE B
3- Stay in fastboot and flash twrp11mata using fastboot command fastboot flash boot exactTWRPfilename.img ------ this will boot you into TWRP on the B side
This next rule is very importantTWRP flashes a zip and a img file different. ZIP ROM FILES FLASH TO THE OPPOSITE PARTITION, IMG FILES flash to the partition that you are currently using. So, if you booted into TWRP on the "b" side and without switching flashed a new kernel or boot image it would install to the same "b" side you are on. If you did the same with a ROM it would install to the 'a" side. So, at some point you have to switch sides from within TWRP in the Reboot tab.
4- Copy your Roms/files to your phones internal memory and then flash using twrp. Flash the ROM not sideload. Flashing is for new roms, sideload is for updates to existing ROM. Back to our example, you booted into TWRP on side b, if you install new rom it will install on side A. Lets keep that idea going for the example. BE AWARE THAT IN THIS TYPE OF DEVICE, using our example where we flashed the rom to the A side (from TWRP on the B side), that side will not have TWRP. It will have stock recovery.
5- once the rom is flashed reboot system. (wipe cache / dont wipe cache.. I havent noticed a difference with either mindset) It will switch your partitions upon reboot if you don't do anything else in twrp.
So for our example this is what happened:
Wiped data from both partitions of the PH-1, side "a" and side "b"
Went BACK-TO-STOCK on BOTH sides
BOOTED INTO STOCK ROM ON THE SIDE WE WISH TO BE OUR ACTIVE SIDE***DID NOT SET UP GOOGLE OR PIN/FINGERPRINT/PASSCODE****
reboot into bootloader
Used Fastboot to switch partitions and installed TWRP to the INACTIVE side. Boot into twrp.
In TWRP, copied new files to phone storage the flashed new ROM Remember it will install it to the other side which is our ACTIVE side
reboot system.
If this helped at all and got you running great. Rooting is simple from here. This phone was the first device I ever rooted so I took my lumps so I hope I offered some tips that I didn't find or understand fully at first. Happy exploring. Ask away if I can help further.
Click to expand...
Click to collapse
mouraj2 said:
Hello
I have an essential ph1 phone I bought new from a friend
I registered my google account and secured the phone with a fingerprint
While the update request protection orio8.1 agreed to download and update
Complete the phone Download the update The installation process then stuck a logo ,,
Now the phone is working on fastboot mode only
I can not log into recovery
bootloader lock
oem lock
usb debogen lock
I could not flash any picture ....
I hope anyone who can help me help me solve the problem and thank you
Click to expand...
Click to collapse
The computer knows the phone in fastboot mode Shaper that the bootloader is closed and did not accept the opening and did not accept the update There is no way to cancel the update from the fastboot commands to complete the update

KingBeefy said:
Could you rephrase what your question is? I would like to help but can't figure out what you are explaining. I'm assuming you have unlocked the bootloader. I had some problems with this phone at first too. Most of the problems when compared to other phones is that Essential Phone has 2 partitions, like the Pixel. For simplicity, one is sort of the ACTIVE side and the other INACTIVE side. It has some learning. If you are just trying to get up and running try these steps...
1- Wipe data using fastboot command fastboot -w ---- locate the Stock ROM section in Essentials forum here on XDA and get the current STOCK build for your needs. Download it. And flash it in fastboot using the flash-all.bat file. Most will flash the files to both partitions, if it does not use the command in the next step to switch partitions and flash the other side too. This will set your phone back to stock and it should boot nicely. If you wish to root then proceed. BOOT INTO THE STOCK OS EVEN IF YOU ARE STILL GOING TO ROOT THE DEVICE. JUST BOOT UP, THEN REBOOT TO THE BOOTLOADER. DONT SIGN INTO YOUR GOOGLE AND DO NOT SET LOCK OR PASSWORD OR FINGERPRINT YET
2- Follow step one and then reboot into fastboot and use command fastboot set_active other --------- this will do two things. It will switch your partition and also tell you which one it switched to. There is an A side and a B sideFOR THIS EXAMPLE WE WILL PRETEND THAT AFTERYOU SWITCHED YOU ARE ON SIDE B
3- Stay in fastboot and flash twrp11mata using fastboot command fastboot flash boot exactTWRPfilename.img ------ this will boot you into TWRP on the B side
This next rule is very importantTWRP flashes a zip and a img file different. ZIP ROM FILES FLASH TO THE OPPOSITE PARTITION, IMG FILES flash to the partition that you are currently using. So, if you booted into TWRP on the "b" side and without switching flashed a new kernel or boot image it would install to the same "b" side you are on. If you did the same with a ROM it would install to the 'a" side. So, at some point you have to switch sides from within TWRP in the Reboot tab.
4- Copy your Roms/files to your phones internal memory and then flash using twrp. Flash the ROM not sideload. Flashing is for new roms, sideload is for updates to existing ROM. Back to our example, you booted into TWRP on side b, if you install new rom it will install on side A. Lets keep that idea going for the example. BE AWARE THAT IN THIS TYPE OF DEVICE, using our example where we flashed the rom to the A side (from TWRP on the B side), that side will not have TWRP. It will have stock recovery.
5- once the rom is flashed reboot system. (wipe cache / dont wipe cache.. I havent noticed a difference with either mindset) It will switch your partitions upon reboot if you don't do anything else in twrp.
So for our example this is what happened:
Wiped data from both partitions of the PH-1, side "a" and side "b"
Went BACK-TO-STOCK on BOTH sides
BOOTED INTO STOCK ROM ON THE SIDE WE WISH TO BE OUR ACTIVE SIDE***DID NOT SET UP GOOGLE OR PIN/FINGERPRINT/PASSCODE****
reboot into bootloader
Used Fastboot to switch partitions and installed TWRP to the INACTIVE side. Boot into twrp.
In TWRP, copied new files to phone storage the flashed new ROM Remember it will install it to the other side which is our ACTIVE side
reboot system.
If this helped at all and got you running great. Rooting is simple from here. This phone was the first device I ever rooted so I took my lumps so I hope I offered some tips that I didn't find or understand fully at first. Happy exploring. Ask away if I can help further.
Click to expand...
Click to collapse
Hi King,
I am hoping you can help. I never enabled USB debugging. I did wipe the phone but cannot run any ADB commands, only fastboot commands. The phone will not run recovery and I'm really hoping I can get some help to recover this phone. Essential won't help as the phone is off warranty. I was able to unlock the phone but cannot seem to load anything via Fastboot as the phone won't allow loading due to the USB debugging not being enabled. I was hoping for a way to enable it via Fastboot.
Thanks,
Grant

mouraj2 said:
Hello
I have an essential ph1 phone I bought new from a friend
I registered my google account and secured the phone with a fingerprint
While the update request protection orio8.1 agreed to download and update
Complete the phone Download the update The installation process then stuck a logo ,,
Now the phone is working on fastboot mode only
I can not log into recovery
bootloader lock
oem lock
usb debogen lock
I could not flash any picture ....
I hope anyone who can help me help me solve the problem and thank you
Click to expand...
Click to collapse
I have the same problem here,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cant flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you

You are both out of luck. I don't know what everyone is thinking by telling you to do all the normal instructions to fix your phones when you plainly say that you get a CORRUPT red warning a boot and at recovery, and you never OEM unlocked your phones to be able to unlock the boot-loader. So I am sorry to tell you this but your phones are garbage. I have the same red corrupt warning at boot and recovery just goes to boot-loader, but I DID unlock my boot-loader, so I am going to erase my critical partitions and flash them on both slots to see if that works. Funny thing, I finally figured out a way to boot into the OS... I just boot and when the red corrupt warning comes on I press the volume buttons randomly and hold them down randomly and at some odd point it just boots up. So weird, it is definitely a bad flash that didn't stick or the image was corrupt, or maybe the image was modded incorrectly. I flashed a patched boot image and that's when the red corrupt warning came up. I am not saying it was the patched boot file, I might have flashed it wrong, like over an already patched boot, which I read is a no no. But now I wonder....should I erase the critical partitions and flashall? And does that "erase" command wipe the partition's data or the partition as a whole??? Or, should I try formatting the critical partitions instead? Anyone know what the correct course of action is here? Or even just what is the BEST one is??? I was lucky to get into the OS because I lost USB debug when I flashed the latest security update trying to fix this. Also, I burned through a data cable somehow too. SMH. OK, Please advise me as to what I should do so that I don't Essentially end up using this phone as part of my chimney. TYIA!
---------- Post added at 03:40 PM ---------- Previous post was at 03:35 PM ----------
A.I.M said:
I have the same problem here,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cant flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you
Click to expand...
Click to collapse
OEM locked is unchecked and you have no access to it? Thats a brick. Unless you can get an ADB connection while your phone bootloops.
SOMEtimes I could get in before my phone booted but highly unlikely.

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.