Database Users

twrp-2.8.7.2-angler.img overwritten by stock recovery

So I have flashed TWRP 2.8.7.2 on my 6P, and was able to go into it. However, if I shut the phone down then boot into the bootloader, arrow down to Recovery Mode and press the power button, I get the android lying on his back with a red triangle with an exclamation mark above his open front, with "No command." written below it. I can hold down the power button and press the volume up button to get to stock android recovery, then reboot to bootloader just fine.
If I connect the phone to my pc and flash TWRP again, I can get into TWRP, however, next time I reboot, it is gone. I read on TWRP's Nexus 6P page the following:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
Click to expand...
Click to collapse
So, I flashed TWRP, then entered fastboot reboot in the cmd window, it rebooted to the bootloader. Then I pressed the volume down button to Recovery mode, pressed power and it went into TWRP. In TWRP I went to Reboot and selected Power Off. I booted it back into the bootloader, selected Recovery mode and it went back to the android with the red triangle and "No command."
I'm at a complete loss. I've read through hundreds of posts here on xda, with one person having the same issue, but fixed it by re-downloading the TWRP .img file and flashing it, Which I've tried... I even flashed the 2.8.7.1 version and had the same problem, then again with the 2.8.7.2 version and still same problem. I've searched for a more detailed explanation of "the proper key combo to enter recovery" and couldn't find anything.
I would really appreciate any help you guys can give me. The biggest thing I have come to understand after reading hundreds (literally) of posts, this community of people are really helpful.
My Android version is 6.0 and my Build number: is MDB08L.
Thanks for any help you guys can give.

this happened to me as well. i fixed it but i don't remember how. I think you need to flash twrp again and there is a tick box or setting that you need to check that will prevent the stock recovery from overwriting twrp. sorry i couldn't be more help.

jrc27 said:
this happened to me as well. i fixed it but i don't remember how. I think you need to flash twrp again and there is a tick box or setting that you need to check that will prevent the stock recovery from overwriting twrp. sorry i couldn't be more help.
Click to expand...
Click to collapse
Thanks for the quick reply. I just flashed TWRP again, entered it through recovery mode, but do not see a tick box or setting... I've looked through the options so many times that I may just be overlooking it by now. Any idea what the tick box or setting might have been labeled as?

I'm having the same issue and cannot seem to find a solution as well. I feel like I'm missing something very obvious...

You will need root explorer and go to the system folder. Then from there you need to rename this file to recovery-from-boot.bak or just delete.
Sent from my Nexus 6P using Tapatalk

I recently experienced the same issue with my Nexus 5 (as I was upgrading it from Kitkat to Marshmallow). I finally solved it by flashing TWRP via Flashify (https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=fr)
So, here are the steps I used : flashed TWRP via bootloader (via PC with USB cable) and boot straight into recovery... flash my rom (with root included) then reboot normally. Then downloaded flashify from the playstore, then flashed TWRP again using flashify... Done, never had this issue since then... I can now reboot into TWRP without problem from the rom, the bootloader or TWRP itself
I don't have a Nexus 6P yet (should do next week ), but it could be worth testing Flashify

Thanks for the suggestions guys.
I'm sorry, I should have mentioned that I haven't gone any further than trying to flash TWRP. This is the first phone I've even unlocked the bootloader on, so I'm extremely new at this.
I'm guessing that Root Explorer and Flashify both require root, which I don't have. Is there a way to get root access with TWRP not staying installed? Is it possible to root the phone while TWRP is installed? The reason I ask is if rooting the phone requires the phone to be rebooted, then TWRP will no longer be installed.
Please excuse the rudimentary questions, I just don't want to mess anything up. I've read so many things over the past several years that warn people to be careful because the phone could be bricked.

j.r.pitcher said:
Thanks for the suggestions guys.
I'm sorry, I should have mentioned that I haven't gone any further than trying to flash TWRP. This is the first phone I've even unlocked the bootloader on, so I'm extremely new at this.
I'm guessing that Root Explorer and Flashify both require root, which I don't have. Is there a way to get root access with TWRP not staying installed? Is it possible to root the phone while TWRP is installed? The reason I ask is if rooting the phone requires the phone to be rebooted, then TWRP will no longer be installed.
Please excuse the rudimentary questions, I just don't want to mess anything up. I've read so many things over the past several years that warn people to be careful because the phone could be bricked.
Click to expand...
Click to collapse
Don't worry, we have all been junior at this at some point... (and I don't pretend to be an expert, but I've gone through this whole process a few days back with my nexus 5... so it's fresh for me)
I'm guessing that if you have unlocked the bootloader and are trying to install TWRP, you ultimately want to root your phone.
To root your phone you have 2 options,
- either root your stock rom, by following the instruction here [GUIDE] Unlock/Root/Flash for Nexus 6P (read the (section 6) instructions carefully and make sure the version (build) of your rom is the correct one to flash a modified boot.img)
- or you can directly replace the stock rom with a pre-rooted rom that you can find in the XDA Developer section (the Chroma rom for instance could be a good one)
In both cases, you'll need to flash some files via TWRP...
Since you have an issue with rebooting into TWRP, you will have to first boot into your stock rom, copy or download on your phone SD card the zip files that you'll need to flash with TWRP and then reboot into bootloader, and follow the instruction for rooting or install a modified pre-rooted rom. Whenever you'll need to boot into recovery during the process, you will need flash TWRP again via adb and boot directly into TWRP (the flash and direct boot adb instruction from cmd on your PC is: fastboot boot <twrp name>.img).
Once you have a rooted rom, you can test Flashify to make TWRP recovery permanent
Enjoy your new rooted phone
PS: don't worry too much about bricking your phone. I believe this occurs when people don't read instructions carefully enough and don't flash the correct zip files or img files... You may find some video tutorials on how to root, but XDA guides are usually great

Well said surfinette!

Surfinette said:
Don't worry, we have all been junior at this at some point... (and I don't pretend to be an expert, but I've gone through this whole process a few days back with my nexus 5... so it's fresh for me)
I'm guessing that if you have unlocked the bootloader and are trying to install TWRP, you ultimately want to root your phone.
To root your phone you have 2 options,
- either root your stock rom, by following the instruction here [GUIDE] Unlock/Root/Flash for Nexus 6P (read the (section 6) instructions carefully and make sure the version (build) of your rom is the correct one to flash a modified boot.img)
- or you can directly replace the stock rom with a pre-rooted rom that you can find in the XDA Developer section (the Chroma rom for instance could be a good one)
In both cases, you'll need to flash some files via TWRP...
Since you have an issue with rebooting into TWRP, you will have to first boot into your stock rom, copy or download on your phone SD card the zip files that you'll need to flash with TWRP and then reboot into bootloader, and follow the instruction for rooting or install a modified pre-rooted rom. Whenever you'll need to boot into recovery during the process, you will need flash TWRP again via adb and boot directly into TWRP (the flash and direct boot adb instruction from cmd on your PC is: fastboot boot <twrp name>.img).
Once you have a rooted rom, you can test Flashify to make TWRP recovery permanent
Enjoy your new rooted phone
PS: don't worry too much about bricking your phone. I believe this occurs when people don't read instructions carefully enough and don't flash the correct zip files or img files... You may find some video tutorials on how to root, but XDA guides are usually great
Click to expand...
Click to collapse
Thanks for the detailed instructions, I really appreciate it.
To be perfectly honest, I was really nervous trying all of that out. I know you said that I shouldn't worry too much about bricking the phone, but it was still a fear.
I have TWRP installed now and it is sticking. Below is a description of how I got it to stay installed.
I didn't have access to my pc this weekend, so was planning on doing it yesterday (Monday). However, Sunday I was re-reading through the posts in this thread and jrc27 mentioned a tick box or setting that you need to check, and I remembered that when I installed TWRP the first time there was a screen that gave you a choice of "Keep Read Only" or "Swipe to Allow Modifications", then remembered someone posting elsewhere about doing the "Swipe to Allow Modifications" is what let's TWRP overwrite the part of Android that resets the recovery mode to the stock recovery mode upon reboot. Well, everytime I would reboot the phone it would be back to the stock recovery mode, so I must have hit "Keep Read Only" that first time, and checked the "Never show this screen during boot again" checkbox. In another post someone was having a different problem with TWRP and someone else told them to delete the .twrps file in the TWRP folder.
So, I flashed TWRP again, and in Advanced, I went into the File Manager, found the .twrps file and deleted it. Rebooted the phone, flashed TWRP again and had the screen that gave me a choice of "Keep Read Only" or "Swipe to Allow Modifications". I did the "Swipe to Allow Modifications", and it booted into TWRP just fine. I rebooted the phone, went to recovery mode and it again booted into TWRP. So, finally it is sticking.
Again, thanks for all of the suggestions, I do appreciate it greatly, as well as welcoming comments and tone of voice (or text as it may be).
Here is what that screen looks like:
{
"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"
}

warpanda said:
I'm having the same issue and cannot seem to find a solution as well. I feel like I'm missing something very obvious...
Click to expand...
Click to collapse
I'm new to xda, so not sure how the forums work. I just posted a reply to Surfinette with how I fixed the issue on my phone. I don't know if you get a message saying a new post was added or not, so I am replying to your post to let you know about it.

u must have the zip in SD card for rooting..
simply....
after flashing twrp do not reboot, or stock recovery will be flashed again... (thats how it works stock)
instead:
after flashing twrp, scroll down and click recovery to boot it... once in twrp, flash the root zip.... the zip used for rooting the device already includes the script that fixes the code that reflashes the factory recovery
(this is assuming you already download the root zip. when i say root zip i mean the proper SuperSU at the time... either system or systemless versions)

chaco81 said:
u must have the zip in SD card for rooting..
simply....
after flashing twrp do not reboot, or stock recovery will be flashed again... (thats how it works stock)
instead:
after flashing twrp, scroll down and click recovery to boot it... once in twrp, flash the root zip.... the zip used for rooting the device already includes the script that fixes the code that reflashes the factory recovery
(this is assuming you already download the root zip. when i say root zip i mean the proper SuperSU at the time... either system or systemless versions)
Click to expand...
Click to collapse
Thanks for the info, chaco81!

[TUTORIAL] [OP2] [BACKUP ST1/ST2 NEEDED] Reverting back from H2O 2.5.1. to other OS.

{
"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"
}
I MEAN NO HARM AND DON'T WANT TO FLOOD THE FORUMS BY CREATING ANOTHER THREAD. I COULDN'T FIND A CLEAR TUTORIAL FOR REVERTING BACK TO ANOTHER ROM FROM H2O 2.5.1. SO I MADE THIS.
MY ORIGINAL POST OnePlus Forums
Just wanted to let know that I managed to revert back to CM 14.1 Official & OOS 3.1.0 without problems!
First make sure you have a terminal made EFS backup & TWRP made /persist backup!
Make sure you have made those before you flashed H2O 2.5.1.
If you don't have a valid backup, I really don't recommend following my steps in any way!
WARNING DO NOT FOLLOW MY STEPS IF YOU DON'T KNOW WHAT YOU ARE DOING!
IF YOU IGNORE THIS AND DON'T HAVE BACKUPS, YOUR PHONE WILL BE NOTHING MORE THAN BRICK!​
WHAT I DID
- Make sure you have a custom recovery. I'm using HybridRecovery_v3.4.imghttp://forum.xda-developers.com/one...0-2-hybrid-supports-oos-t3362904/post66466393
- Make sure that OEM unlock is enabled under developer settings in your phone.
- Make sure that ADB debugging is enabled under developer settings in your phone.
- Connect phone to PC and grant permission to communicate with your phone.
- Grab your modemst1.bin & modemst2.bin files and put them in the same directory where ADB is installed/unpacked.
- Boot phone in bootloader/fastboot
- Start a new ADB session
- fastboot devices
- Check if any device is recognized
- This is the moment where you still can return to H2O.
Side note: H2O 2.5.1. is a fine OS and worked great for me. Maybe I'll return to it some day, but for now I'll be using CM 14.1
LET'S BEGIN
- Fastboot erase modemst1
- Fastboot erase modemst2
- Fastboot flash -S 512M modemst1 modemst1.bin
- Fastboot flash -S 512M modemst2 modemst2.bin
- Unplug your phone and then turn it off you by holding the power button
- Boot your phone into recovery
- Restore the /persist partition with TWRP/HybridRecovery
- Flash a ROM
One thing to mention is that when I restored a backup of CM 14.1 my data connection seemed forever lost.
I managed to fix that by deleting my network settings in the "Settings" app of Android. I also rebooted in recovery and deleted Dalvik/Art cache & cache.
Reboot your phone to system.
Voila, your phone is reverted and both of the IMEI's are still intact!
Any questions? I'll try to answer them as quickly as possible!

Restore the /persist partition with TWRP [NEW STEP]
how???

aliasgertaj said:
Restore the /persist partition with TWRP [NEW STEP]
how???
Click to expand...
Click to collapse
install Hybrid TWRP and then you will see the option. Search the forum for it. You'll find it

aliasgertaj said:
Restore the /persist partition with TWRP [NEW STEP]
how???
Click to expand...
Click to collapse
-Do you have a backup from your whole system made in TWRP?
-Do you have the modem files backed up via terminal?
If both are yes, you can follow my steps.
If not, stop.

aliasgertaj said:
Restore the /persist partition with TWRP [NEW STEP]
how???
Click to expand...
Click to collapse
Thread HybridRecovery (Use the 3.4 Version)
http://forum.xda-developers.com/one...0-2-hybrid-supports-oos-t3362904/post66466393

ok thnx dude

Stupid question whats the command to backup the modem

MRDICKHEAD said:
Stupid question whats the command to backup the modem
Click to expand...
Click to collapse
Not my video, but here you go!

Just FYI, I flashed back to OxyGenOS 3.1.0 and it works perfectly fine!
The last numbers proof it.
I've cut away the other part of my screenshot due to privacy.

Tunatje said:
Not my video, but here you go!
Click to expand...
Click to collapse
Thanks

Hi,
Thank you for your thread.
I am assuming this tutorial won't apply if I already erased my modemst without taking a backup? Because if I were to backup anything now it would just be an empty file?

rajatdixit said:
Hi,
Thank you for your thread.
I am assuming this tutorial won't apply if I already erased my modemst without taking a backup? Because if I were to backup anything now it would just be an empty file?
Click to expand...
Click to collapse
So sorry to hear that. Indeed, you will have a empty file.. You never made a Nandroid backup? If not, this is a hard lesson you have learned to read always the threads about flashing stuff for the first time. It's always mentioned that you have to make sure you have a full Nandroid backup.

Tunatje said:
So sorry to hear that. Indeed, you will have a empty file.. You never made a Nandroid backup? If not, this is a hard lesson you have learned to read always the threads about flashing stuff for the first time. It's always mentioned that you have to make sure you have a full Nandroid backup.
Click to expand...
Click to collapse
No, unfortunately I didn't. Yes its a hard lesson. I only have 1 IMEI working now.
Thank you for your input

I tried this one and it actually worked
http://forum.xda-developers.com/oneplus-2/general/howto-revert-firmware-hydrogenos-2-5-to-t3512065

please help...
i flashed into h2os for volte in mu oneplus two and then i flashed cm official 14.1 but then my phone started frequenlt rebooting . i though that might be a rom bug so i flashed rescuration remix rom but then too my phone is frequently rebooting . please help me tired of this. give me step by step solution for this. thank you.

.bin file Copy Paste ???
I dont know this is a proper Question (If not I m Sorry)
My other OPT have RR rom (before H2OS 2.5) is there any way that can enable me to copy .bin file from the other OPT & get both sim working.
Please Help
TIA

Sunil Jagtap said:
I dont know this is a proper Question (If not I m Sorry)
My other OPT have RR rom (before H2OS 2.5) is there any way that can enable me to copy .bin file from the other OPT & get both sim working.
Please Help
TIA
Click to expand...
Click to collapse
You mean, duplicate the IMEI?

Tunatje said:
You mean, duplicate the IMEI?
Click to expand...
Click to collapse
No, I mean can, I edit it with what no. my OPT has before.
Or
how can, I revert back to H2OS 2.5 with both sim working, tried every thing but after boot only SIM 1 is working
Thanks in Advance

Sunil Jagtap said:
No, I mean can, I edit it with what no. my OPT has before.
Or
how can, I revert back to H2OS 2.5 with both sim working, tried every thing but after boot only SIM 1 is working
Thanks in Advance
Click to expand...
Click to collapse
Hi,
You can't edit a IMEI. At least, not that I'm aware of. I've read that people used a HEX editor but not sure how that works or how much time that costs.
My thread is only for people with a modemst1.bin/modemst2.bin backup made through terminal..
However, there is a new guide for people without a backup, but think it's applicable if you haven't used the "erase" command.
https://forums.oneplus.net/threads/...r-flashing-hydrogen-os-video-included.477463/

rrbjerry said:
i flashed into h2os for volte in mu oneplus two and then i flashed cm official 14.1 but then my phone started frequenlt rebooting . i though that might be a rom bug so i flashed rescuration remix rom but then too my phone is frequently rebooting . please help me tired of this. give me step by step solution for this. thank you.
Click to expand...
Click to collapse
I've send you a PM.

[STOCK][N][ARB01] H830 20N ZIPs + KDZ (2017-12-01 Security Patch)

First off, a HUGE thank you to @autoprime (for paving the way) and @waylo (for his assistance on getting this going after I found the KDZ)
I am currently storing these in my google drive account, so please be gentle till I have a better host location:
Below are the downloads for the LG-H83020N firmware
Folder with all the LG830 firmware I have so far:
LG830 (G5)
LG-H83020N-Flashable.COMPLETE-ARB01.zip
As always, COMPLETE is 100% stock
Flash COMPLETE zip -> wipe cache partition -> flash Magisk ZIP (or SuperSU if you insist) to root and keep TWRP
OPTIONAL: After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks
LG-H83020N-Flashable.Bootloader-ARB01
LG-H83020N-Flashable.Modem-ARB01.zip
LG-H83020N-Flashable.Boot.zip
H830N_00_1017.kdz (HUGE Thank you to @Azul Baseem for the upload)
For instructions, follow the same instructions as you would in any other KDZ/ZIP thread. For Example
Feel free to hit thanks.
Also feel free to hit up autoprime's All in One thread HERE

Thank you very much bedwa!

Kdz link updated!

Thank you @bedwa as always.
I fear my only true contribution here is MD5 confirmation of the files:
LG-H83020N-Flashable.COMPLETE-ARB01.zip 8a49733028bef23d775bf542eb62b726
LG-H83020N-Flashable.Boot.zip ddea9d814f66266de34a154f0c7f6b41
H830N_00_1017.kdz 732b717af8d77501342be445002c4fae
Edit: Also, since someone will definitely miss it in the title, this is confirmed to still be on Anti-Rollback 1. You're free to flash back and forth between 20A if you need to Dirtycow your phone again.

Keeping me honest, I swear I'll remember them next time.

Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.

shinji257 said:
Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.
Click to expand...
Click to collapse
Fixed. That's what I get for using the copypasta method. Missed the one. :silly:

help me
{
"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"
}
i had this issues when i try to flash it i already use uppercut

solved
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?

abced123 said:
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?
Click to expand...
Click to collapse
That would be trickier. All of these are the partition images. To make a slim zip like that I'll have to either unpack and build or unpack and attempt to repack. I might, but not likely at this time.

Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)

fc3211 said:
Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)
Click to expand...
Click to collapse
Quite welcome... It's more time consuming than hard work, but the appreciation and thanks is greatly appreciated as well.

@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.

Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?

nizarp said:
@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.
Click to expand...
Click to collapse
Backup is always good, shouldn't have to restore it as it's updating from a previous version and doesn't wipe data when upgrading. But that's the correct process with or without #6.
azizo07 said:
Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?
Click to expand...
Click to collapse
Shouldn't, but it would always be a good idea to backup beforehand. I would however only flash the bootloader, as the boot is the kernel and will be different than what LineageOS uses though.

I just boot into TWRP and flashed the complete zip and then flashed the latest SuperSU Zip. I pressed Reboot System after that, but, I am now stuck in a boot loop. Phone shows LG logo and reboots again and again.
I tried the Power button + Vol Down method, but, it doesn't work too. It gets to Factory reset screen, and after Yes and Yes, it goes to back to boot loop again. I am able to get into Download Mode and Fastboot Mode. Can I do something from here?
Can someone help please? Anyway to get into TWRP or recovery?

Sounds like you will need to LGUP or Uppercut your phone back to stock 20A. Then dirtycow back TWRP. Then try flashing the new ZIP again. Skip Supersu this time and try Magisk instead.

Thanks. I flashed back to 20A using LGUP and KDZ file. Need to dirtycow back TWRP now. I'm still wondering what went wrong in my process.
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
Click to expand...
Click to collapse
Do I need to reboot to TWRP once after flashing instead of Reboot System directly after flash? Any idea?

No, rebooting into TWRP wouldn't do anything. There's a script you might need to get into and delete prior to rebooting. But that only ensures that TWRP stays.
"After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks"
That having been said, I've done this before and STILL not had TWRP stay. Some recommend wiping /cache as well.
OR, again, use Magisk instead and don't use SuperSU.
Even if TWRP didn't stick, you should have been booting into system fine. You wouldn't be rooted, TWRP would be gone, but system shouldn't have been messed up. So something got borked, I'd have to guess, because of SuperSU.

New security patch update alert

Need help with flashing/updating.

Hello,i used moto g 5plus toolkit to root my phone.t he ROM that I installed is POTTER_NPN25.137675_cid50_subsidyDEFAULT_regulatoryDEFAULT_CFC
After installing it my camera stopped working.it just says camera is busy.So I want to try installing some other custom Roms.i just want to know can I flash https://forum.xda-developers.com/g5-plus/development/rom-pie-9-x-arrowos-9-x-t3838052 this ROM without bricking my phone with twrp.
Imgur links of device https://imgur.com/a/d9fJ0UI
{
"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"
}

Indransu said:
Hello,i used moto g 5plus toolkit to root my phone.t he ROM that I installed is POTTER_NPN25.137675_cid50_subsidyDEFAULT_regulatoryDEFAULT_CFC
After installing it my camera stopped working.it just says camera is busy.So I want to try installing some other custom Roms.i just want to know can I flash https://forum.xda-developers.com/g5-plus/development/rom-pie-9-x-arrowos-9-x-t3838052 this ROM without bricking my phone with twrp.
Imgur links of device https://imgur.com/a/d9fJ0UI
Click to expand...
Click to collapse
You may have flashed the wrong stock firmware for your device, depends on your location.
If you don't want to give the (correct) stock firmware another try and flash a custom ROM instead make sure to backup everything incl. EFS and persist (very important if you want to go back to stock) in TWRP.
How to flash ArrowOS is written in the first post in it's thread:
Clean Flash
Download The ROM & GApps
Wipe: System, Data, Dalvik, Cache
Flash ROM + GApps
(+Magisk if you want root)
Reboot & Enjoy
Dirty Flash
Download the ROM
Wipe: Dalvik and Cache
Flash ROM (+Magisk if rooted previously or if want root)
Reboot & Enjoy
Downloadlinks are just below there, you have to do a clean flash.
There's no guarantee to not brick your device but if you read everything carefully, get all informations that are needed and follow the steps exactly everything should work fine. I flashed dozens of custom ROMs on several devices and didn't brick one of them.
If you never flashed a custom ROM before or haven't rooted with magisk I recommend you to read everything you can find about this procedures here on XDA before doing anything!

Wolfcity said:
You may have flashed the wrong stock firmware for your device, depends on your location.
If you don't want to give the (correct) stock firmware another try and flash a custom ROM instead make sure to backup everything incl. EFS and persist (very important if you want to go back to stock) in TWRP.
How to flash ArrowOS is written in the first post in it's thread:
Clean Flash
Download The ROM & GApps
Wipe: System, Data, Dalvik, Cache
Flash ROM + GApps
(+Magisk if you want root)
Reboot & Enjoy
Dirty Flash
Download the ROM
Wipe: Dalvik and Cache
Flash ROM (+Magisk if rooted previously or if want root)
Reboot & Enjoy
Downloadlinks are just below there, you have to do a clean flash.
There's no guarantee to not brick your device but if you read everything carefully, get all informations that are needed and follow the steps exactly everything should work fine. I flashed dozens of custom ROMs on several devices and didn't brick one of them.
If you never flashed a custom ROM before or haven't rooted with magisk I recommend you to read everything you can find about this procedures here on XDA before doing anything!
Click to expand...
Click to collapse
Actually my software status in bootloader says it is modified as I have flashed that Potter roam I have listed above.My imei and 4g is working fine.Can I do a efs and persist backup now or am I screwed?
Also if I flash arrow os(Android 9 from Android 7)will I lose my 4g and imei?
If so I don't want to do it.

Indransu said:
Actually my software status in bootloader says it is modified as I have flashed that Potter roam I have listed above.My imei and 4g is working fine.Can I do a efs and persist backup now or am I screwed?
Also if I flash arrow os(Android 9 from Android 7)will I lose my 4g and imei?
If so I don't want to do it.
Click to expand...
Click to collapse
Back them up.

[email protected] said:
Back them up.
Click to expand...
Click to collapse
I have adb backup(backup.ab around 1.8gb)does it contain efs and persist?

Indransu said:
I have adb backup(backup.ab around 1.8gb)does it contain efs and persist?
Click to expand...
Click to collapse
You can backup persist (the most important file) by ADB using this command:
Code:
adb shell
dd if=/dev/block/mmcblk0p30 of=/sdcard/persist.img
To restore it use
Code:
adb shell
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p30
Another way to backup both, EFS and persist is by TWRP, you need the latest version, 3.2.3.1:
https://eu.dl.twrp.me/potter/twrp-3.2.3-1-potter.img.html
Make a backup of all partitions and a separate one containing EFS and persist.
If you loose your IMEI and/or 4g by moving back from custom ROM to stock you can use these backups to get them back.
This problems are only related to stock Nougat, once you're on stock Oreo with working IMEI nothing should happen anymore.
When you flash a custom ROM check what you need as base, Oreo or Nougat. Some ROMs need Oreo as a base so you have to update your device in that case.
Arrow OS needs Oreo, see the first line in their OP.

Wolfcity said:
You can backup persist (the most important file) by ADB using this command:
Code:
adb shell
dd if=/dev/block/mmcblk0p30 of=/sdcard/persist.img
To restore it use
Code:
adb shell
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p30
Another way to backup both, EFS and persist is by TWRP, you need the latest version, 3.2.3.1:
https://eu.dl.twrp.me/potter/twrp-3.2.3-1-potter.img.html
Make a backup of all partitions and a separate one containing EFS and persist.
If you loose your IMEI and/or 4g by moving back from custom ROM to stock you can use these backups to get them back.
This problems are only related to stock Nougat, once you're on stock Oreo with working IMEI nothing should happen anymore.
When you flash a custom ROM check what you need as base, Oreo or Nougat. Some ROMs need Oreo as a base so you have to update your device in that case.
Arrow OS needs Oreo, see the first line in their OP.
Click to expand...
Click to collapse
Thanks a lot man.i was about to flash arrow from nougat.

Indransu said:
You can backup persist (the most important file) by ADB using this command:
To restore it use
Thanks a lot man.i was about to flash arrow from nougat.
Click to expand...
Click to collapse
You're welcome. Just hit the thanks button.

Question Fixed fastboot loop, Now fingerprint sensor wont read

As the titles states, I recently recovered my Nothing phone 1 from a fastboot loop after trying to go back to stock, locked bootloader from the latest android 13 PE rom.
I ended up somehow "seemingly" deleted all the partitions on the phone. While using most of THIS unbrick method. Although i supplied my own 1.1.4 full ROM, and matching super image.
I manually flashed all of the partitions for Slot A and they all completed with no issues.
I manually flashed all of them again on Slot B and got a few partition errors.
I set slot A as active and the phone booted up fine and booted into Nothing OS, However my finger print reader doesnt read my finger now and i cant boot slot B into recovery/fastbootd. it just reboots back into bootloader.
I found that i needed to flash the persist.img partition but ive done that and it still does the same thing, and i still cannot get Slot b into recovery/fastbootd.
I am both unlocked and Critical unlocked.
Verified that I used the correct global ROM and super.img for both 1.1.4 and 1.5.1
Ive tried re-doing everything, Flashing all the images before the super.img. After the super.img, the persist.img before and after as well.
Ive tried re-flashing everything but using the 1.5.1 Beta 2 hotfix, and matching boot.img and the same issue.
i tried re-flashing everything from the bootloader screen instead of fastbootd and same issue.
All my other sensors seem to work fine, including SIM Data, gyroscope, light sensors, camera flash, wifi. Everything except fingerprint.
Can anyone help me get this figured out? Ill try to answer any questions the best i can.
Thanks!

Tested all the sensors with a couple applications all of which aren't recognizing the fingerprint sensor as being in the phone at all.
Can anyone tell me when the persist image is supposed to be flash and possibly upload their persist image here so I can try it?
1.5.1 global version.
{
"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"
}

Hey, did you by chance change the kernel?

Ofdas23 said:
Hey, did you by chance change the kernel?
Click to expand...
Click to collapse
Not as far as I know. At least not manually, unless they were part of one of the batch files that ran.

Decree said:
Not as far as I know. At least not manually, unless they were part of one of the batch files that ran.
Click to expand...
Click to collapse
Hmm, no, that's not the problem then
I don't know, flashing persist.img can have implications if not done properly and by no means am I any expert on this at all
I read that doing so improperly might end your device lose widevine L1 forever, which has impacts on DRM protected content, such as Netflix streams etc.

You could also try to recalibrate, I don't know the implications of that though, as it goes deeper into the system
I don't know if I would mess with that

Ofdas23 said:
You could also try to recalibrate, I don't know the implications of that though, as it goes deeper into the system
I don't know if I would mess with that
Click to expand...
Click to collapse
I have no clue how I would do that unfortunately

Decree said:
I have no clue how I would do that unfortunately
Click to expand...
Click to collapse
I think for that, you would have to be on stock ROM
also, how did you flash the images? In bootloader or fastbootd?
Fastbootd should be used
Edit:
Also I know, I am sending mixed signals, but when it comes to your slot b, maybe a recovery of a custom rom could fix it?

Ofdas23 said:
I think for that, you would have to be on stock ROM
also, how did you flash the images? In bootloader or fastbootd?
Fastbootd should be used
Edit:
Also I know, I am sending mixed signals, but when it comes to your slot b, maybe a recovery of a custom rom could fix it?
Click to expand...
Click to collapse
I am on stock 1.5.1 beta now
I flashed all images on slot a in fastbootd I tried to do that for slot B as well but I was unable to boot into it before. I would try to boot to recovery to do that and it would just loop back into bootloader.
Tonight, I flashed the PE room again per their instructions and then reflashed stock everything as if I was going back to stock with unlocked, and critical unlocked bootloader
Flashed boot and vendor boot for slot a, rebooted into fastbootd, flashed super.img, (which shows 25) then flashed all other images. Rebooted to bootloader and then flashed super again (this time it shows only 9) and then persist.
Did the same for slot B BUT this time I was actually able to boot to slot B recovery/fastbootd.
Phone boots up to stock Nothing OS again but still no working fingerprint.
Im honestly not sure if super should be flashed in fastbootd or bootloader or what order it should be flashed either. And the same for persist.Img

Decree said:
I am on stock 1.5.1 beta now
I flashed all images on slot a in fastbootd I tried to do that for slot B as well but I was unable to boot into it before. I would try to boot to recovery to do that and it would just loop back into bootloader.
Tonight, I flashed the PE room again per their instructions and then reflashed stock everything as if I was going back to stock with unlocked, and critical unlocked bootloader
Flashed boot and vendor boot for slot a, rebooted into fastbootd, flashed super.img, (which shows 25) then flashed all other images. Rebooted to bootloader and then flashed super again (this time it shows only 9) and then persist.
Did the same for slot B BUT this time I was actually able to boot to slot B recovery/fastbootd.
Phone boots up to stock Nothing OS again but still no working fingerprint.
Im honestly not sure if super should be flashed in fastbootd or bootloader or what order it should be flashed either. And the same for persist.Img
Click to expand...
Click to collapse
Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue
Decree said:
I am on stock 1.5.1 beta now
I flashed all images on slot a in fastbootd I tried to do that for slot B as well but I was unable to boot into it before. I would try to boot to recovery to do that and it would just loop back into bootloader.
Tonight, I flashed the PE room again per their instructions and then reflashed stock everything as if I was going back to stock with unlocked, and critical unlocked bootloader
Flashed boot and vendor boot for slot a, rebooted into fastbootd, flashed super.img, (which shows 25) then flashed all other images. Rebooted to bootloader and then flashed super again (this time it shows only 9) and then persist.
Did the same for slot B BUT this time I was actually able to boot to slot B recovery/fastbootd.
Phone boots up to stock Nothing OS again but still no working fingerprint.
Im honestly not sure if super should be flashed in fastbootd or bootloader or what order it should be flashed either. And the same for persist.Img
Click to expand...
Click to collapse
Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue
Als, could you please run this code in the phone dialer?
*#*#0#*#
Also, super is supposed to be flashed in fastboot, as far as I am concerned, no Guanajuato
Edit:
Also, do you have Telegram or something, for easier messaging?

Ofdas23 said:
Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue
Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue
Als, could you please run this code in the phone dialer?
*#*#0#*#
Also, super is supposed to be flashed in fastboot, as far as I am concerned, no Guanajuato
Edit:
Also, do you have Telegram or something, for easier messaging?
Click to expand...
Click to collapse
It should be. Although I found it posted in one of the threads I'll have to find. It's literally the only one I could find, I'm unsure of how to extract a working one from a ROM.
From what I read it stores the calibration for most of not all the sensors on the device, but literally ALL of mine work except the fingerprint.
I'll do the dialer thing in a couple minutes.
So in what order should someone be flashing the images?
Super, images, persist?
Or
Persist, super, images?
And everything should be flashed via fastbootd?
I Don't have telegram but Ill set one up!

Ofdas23 said:
Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue
Click to expand...
Click to collapse
Here is the persist I've used. I did also flash this on 1.1.4 like the post says but now since slot B goes into fastboot I'll try it again tomorrow?
Post in thread 'How to unbrick Nothing Phone 1 fastboot bootloop' https://forum.xda-developers.com/t/...one-1-fastboot-bootloop.4501439/post-87527709
I also just made a telegram. Not sure what you need to add me or start a chat but my username is Anfurnyy

Decree said:
Here is the persist I've used. I did also flash this on 1.1.4 like the post says but now since slot B goes into fastboot I'll try it again tomorrow?
Post in thread 'How to unbrick Nothing Phone 1 fastboot bootloop' https://forum.xda-developers.com/t/...one-1-fastboot-bootloop.4501439/post-87527709
I also just made a telegram. Not sure what you need to add me or start a chat but my username is Anfurnyy
Click to expand...
Click to collapse
Use this app to restore it!
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
But use 1.1.4, as you said ^^

Ofdas23 said:
Use this app to restore it!
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
But use 1.1.4, as you said ^^
Click to expand...
Click to collapse
So you're saying use that app to put the persist. Img back into the file system and not flash it through fastboot?

Decree said:
So you're saying use that app to put the persist. Img back into the file system and not flash it through fastboot?
Click to expand...
Click to collapse
Yes, exactly, but it requires root!

Ofdas23 said:
Yes, exactly, but it requires root!
Click to expand...
Click to collapse
Shouldn't be a problem. Plenty of patched boots for 1.1.4 lol I'll give it a go tomorrow. Thanks for the idea!

Ofdas23 said:
Yes, exactly, but it requires root!
Click to expand...
Click to collapse
So I was able to get it back to 1.1.4 today with root, and restore the 1.1.4 persist.img from that post using that app and still doesn't work. Only thing left I can think of is try to extract one from another ROM file and after that try to send it back to Nothing.

Just wanted to add a bit of closure to this post. I ended up having to send the phone back to Nothing for an RMA and they just flat replaced it with a new device. There was no fix for the fingerprint sensor that they told me.
Of course, everything is up and working great now.