Database Info

Messed up big time?

Hi,
I am really not into flashing and stuff like this, but some weeks ago I successfully rooted my device and installed a custom bootloader (teamwin). Today I wanted to do a clean wipe to install cm11s on my N5. So I launched into recovery, selected "wipe" and unfortunatly I selected "advanced wipe" also. I checked everything and started the wipe process. Dont ask me why I did this, I wasnt thinking obviously. When I boot my device now, only the white Google font is visible and underneath there is a locker. I can start recovery but since I wiped everything I can not install the stock rom again. Also my PC doesnt recognize the N5 as a "harddrive" so I can not move the stock .zip to the device. The device manager is displaying it as ACER DEVICE, and under portable devices it is displayed as Nexus 5 with a yellow exclamation mark. Any tipps how I can get a rom on this device again?

Simple mate...
Download cm rom zip
Reboot into recovery
Mount ur storage
Put cm rom zip somewhere
Install that rom zip via recovery(twrp is recovery not the boot loader )
Flash gapps (optional if u want google services n apps) (u can do this later also)
Reboot

forstyy said:
Hi,
I am really not into flashing and stuff like this, but some weeks ago I successfully rooted my device and installed a custom bootloader (teamwin). Today I wanted to do a clean wipe to install cm11s on my N5. So I launched into recovery, selected "wipe" and unfortunatly I selected "advanced wipe" also. I checked everything and started the wipe process. Dont ask me why I did this, I wasnt thinking obviously. When I boot my device now, only the white Google font is visible and underneath there is a locker. I can start recovery but since I wiped everything I can not install the stock rom again. Also my PC doesnt recognize the N5 as a "harddrive" so I can not move the stock .zip to the device. The device manager is displaying it as ACER DEVICE, and under portable devices it is displayed as Nexus 5 with a yellow exclamation mark. Any tipps how I can get a rom on this device again?
Click to expand...
Click to collapse
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.

Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
Dont knw exactly but is mount storage an option in adb??? I jst suggested it lol

doctor_droid said:
Dont knw exactly but is mount storage an option in adb??? I jst suggested it lol
Click to expand...
Click to collapse
What do you mean lol?

Lethargy said:
What do you mean lol?
Click to expand...
Click to collapse
Like cwm has an option to mount storage...
Similarly does twrp has same option too?

doctor_droid said:
Like cwm has an option to mount storage...
Similarly does twrp has same option too?
Click to expand...
Click to collapse
As in browse files on a PC or what?

Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
Yea sorry, I dont know what I am talking about exactly, just know the terms
So I adb pushed the image-hammerhead-ktu84p.zip to my device to /sdcard. When I want to install it from recovery and select the zip, it just says FAILED

forstyy said:
Yea sorry, I dont know what I am talking about exactly, just know the terms
So I adb pushed the image-hammerhead-ktu84p.zip to my device to /sdcard. When I want to install it from recovery and select the zip, it just says FAILED
Click to expand...
Click to collapse
You don't flash that in recovery lol!
Run this so it flashes and wipes everything:
{
"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"
}

Lethargy said:
You don't flash that in recovery lol!
Run this so it flashes and wipes everything:
Click to expand...
Click to collapse
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
When these are all done, from Recovery's main screen, select "Install ZIP from SD Card" and then "Choose file from SD Card" and select the ROM.zip file you just pushed from your computer to the SD Card. If you do not see the file, go back to Mounts and Storage and toggle them to say "Mount /sdcard/" and "Mount /system/" and then go back and try to fine the ROM.zip file. If you still do not see it, it was not pushed correctly...go back and ensure you were letter for letter with the name and the file path.
Click to expand...
Click to collapse

forstyy said:
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
Click to expand...
Click to collapse
Just push a cm rom made for ur hammerhead...

forstyy said:
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
Click to expand...
Click to collapse
image-hammerhead-ktu84p.zip isn't a flashable ROM zip, it's just a compressed archive of boot.img, cache.img, recovery.img, system.img and userdata.img
What the flash-all script does is:
1. fastboot flash bootloader bootloader-hammerhead-hhz11k.img
2. reboots bootloader
3. fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
4. reboots bootloader again
5. fastboot -w update image-hammerhead-ktu84p.zip (-w = wipe, then "update image-hammerhead-ktu84p.zip" just flashes all the .img files in the zip, same as individually flashing each with fastboot)

Lethargy said:
image-hammerhead-ktu84p.zip isn't a flashable ROM zip, it's just a compressed archive of boot.img, cache.img, recovery.img, system.img and userdata.img
What the flash-all script does is:
1. fastboot flash bootloader bootloader-hammerhead-hhz11k.img
2. reboots bootloader
3. fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
4. reboots bootloader again
5. fastboot -w update image-hammerhead-ktu84p.zip (-w = wipe, then "update image-hammerhead-ktu84p.zip" just flashes all the .img files in the zip, same as individually flashing each with fastboot)
Click to expand...
Click to collapse
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?

forstyy said:
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?
Click to expand...
Click to collapse
Its the bootloader fastboot is what's used in the bootloader. And yeah, flash a custom recovery then you're good to go!

forstyy said:
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?
Click to expand...
Click to collapse
Welcome to flashing world...now since u know how to revive ur phone... U will definately mess up it again...

doctor_droid said:
Like cwm has an option to mount storage...
Similarly does twrp has same option too?
Click to expand...
Click to collapse
Mount storage only works on a non-fuse /sdcard. Meaning either:
- device has removable sdcard
- device is not using fuse for internal storage.
Nexus 5 meets neither.
Sent from my Nexus 5 using Tapatalk

Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
My thoughts exactly
sent from my thumbs

Same here I've messed my n5 up about 5 times these Google images come In handy

Thank you guys for your help, all is working again. Was a bit scary since this was the first time I did this.:fingers-crossed:

forstyy said:
Thank you guys for your help, all is working again. Was a bit scary since this was the first time I did this.:fingers-crossed:
Click to expand...
Click to collapse
The N5 is basically the best contemporary phone to soft brick or break. The support and tools available are great.

[GUIDE] Rooting your Essential PH-1

WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Useful and important general information can be found in the second post here.
NOTES
1. If you flash the TWRP Installer when you've already got Magisk installed, your device will keep booting to the recovery. You should be able to fix this by just simply reflashing Magisk.
2. If you have TWRP installed via the TWRP Installer, you will not be able to install stock OTA updates. You will have to reflash the stock boot image for whatever build you're running beforehand.
3. The prebuilt TWRP image may not have touch functionality if you're using the September 2018 Update or newer. Patching the boot image, however, for these builds with the TWRP Installer will allow touch to work flawlessly. Here is a pre-patched September 2018 Boot Image with TWRP. It should also work with builds newer than September. Since it's based off the September 2018 update, I suggest not using this as your main boot image but rather just as a replacement for the pre-built TWRP image from the official TWRP thread.
4. Simple "flash and forget" boot images pre-patched with Magisk and TWRP are provided by @aer0zer0 and are available here. They are based on ianmacd's variant of Magisk. If you are running stock, you can flash these boot images to get root and TWRP instead of following the guide to patch it yourself. Here is January's.
If you don't care about TWRP and simply want to just root your device, you can just simply patch the boot image for your ROM with the Magisk Manager and flash it in fastboot with
Code:
fastboot flash boot patched_boot.img
The link to the boot images for most stock builds can be grabbed from my Google Drive link in the second post or from the back-to-stock zips.
REQUIREMENTS
An unlocked bootloader
Working adb and fastboot environment, along with knowledge on how they work.
The latest build of TWRP along with the TWRP Installer. Read Note 3 above beforehand.
1. Download the latest build of TWRP and the TWRP Installer. Transfer the TWRP Installer zip to your device.
2. Reboot your phone into fastboot. Once in fastboot, change your device's current slot using the command
Code:
fastboot set_active other
If the command above doesn't work for you, use fastboot getvar current-slot followed by fastboot -aX, replacing "X" with the slot opposite (a or b) from your current slot.
3. Once your device's current slot has been switched, flash the TWRP image you downloaded earlier using the command
Code:
fastboot flash boot twrp.img
Depending on your version of fastboot, the above command might not work either. In that case, you can enter the following command, replacing "X" with your current slot (a or b).
Code:
fastboot flash boot_X twrp.img
4. Once TWRP has been flashed, boot into the recovery.
5. Once you have booted into TWRP, simply flash the TWRP Installer zip.
6. Once you have finished flashing the TWRP Installer zip, boot to recovery on the OPPOSITE slot. You can do this from TWRP by going to "Reboot", then selecting the opposite of the current slot (if on A, select Slot B. If on B, select Slot A), then select "Recovery." You can also do this through fastboot by running the same command from step 2.
7. Once you have booted back into TWRP, simply flash the Magisk zip and you are now good to go! Feel free to flash anything else like kernels while you're at it.
8. Reboot. :good:
NOTE: TWRP WILL remain installed on your device so long as you reflash the installer zip after every update.

Important Information for the Essential PH-1 can be found here. Keep it bookmarked.
Tips on updating via OTA after rooting can be found here.
In the case that you mess something up on your device, you may find it helpful to revert back to stock with the unofficial factory images graciously provided by @invisiblek and @aer0zer0 over here.
Official TWRP XDA Thread for the Essential PH-1
Join the Essential PH-1 Discord Server! -- Lots of cool people here!
Join the Essential PH-1 Development Telegram Channel!
Stock Boot Images for most builds can be found at my Google Drive link here.
Have a Red Verity Warning when booting your device? Click here.
If the link to the boot.fix.red image isn't working, you can also find it here or in my Google Drive link in the first post.
Essential Phone (PH-1) Partition Layout
Dumping Boot Images
1. Find the current slot with
Code:
fastboot getvar current-slot
or
Code:
adb shell getprop ro.boot.slot_suffix
2. Switch to the opposite slot in Fastboot using the command
Code:
fastboot set_active other
3. Flash TWRP using the command
Code:
fastboot flash boot twrp.img
4. Now, boot into TWRP and use the following command from your PC, replacing X in "boot_X" with the original slot from step 1 (a or b). TRIPLE CHECK:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot_X of=/sdcard/boot.img
5. Profit! Don't forget to switch back to the original partition with the same command from step 2!
extractTarFork() error when restoring data from a TWRP backup
1. Reinstall the ROM from which the backup is based on.
2. Wipe your data. You can do this from the recovery or from fastboot using the command
Code:
fastboot -w
3. Boot into the ROM. When going through the initial setup, use the EXACT same security setup as the one from your backup. For example, if you used a Fingerprint + Password in the backed up ROM, use the exact same combo along with the exact same password as well. There is no need to set up anything else, like accounts.
4. Flash, install, and reboot into TWRP. You should now be able to restore the data backup without any issues.

AFH mirrors for images:
Build NMJ32F
NMJ32F patched boot image
NMJ32F factory image
Build NMJ20D
NMJ20D patched boot image
NMJ20D factory image
TWRP (alpha v4)

Thanks for getting the latest boot image up so quickly.

Thanks for the detailed guide, it worked great!
Any idea how to install xposed sdk 25? I tried the adb sideload function and the Magsik Module but both failed. Any ideas?

how to install the NMJ32F ota update when you are already rooted on NMJ20D?
Tried adb sideload but cannot install obviously because boot-loader is unlocked and is rooted.

prgopala said:
how to install the NMJ32F ota update when you are already rooted on NMJ20D?
Tried adb sideload but cannot install obviously because boot-loader is unlocked and is rooted.
Click to expand...
Click to collapse
You need to flash the system and boot images from Invisiblek's stock ROM dump. You'll then be unrooted and will be able to accept the update.

Factory reset no longer required if your bootloader is already unlocked? Does TWRP read encypted storage now? Or is that still a problem?

@bmg1001 , good looks, here are more free XDA points to trade in for that pool table, lol.

gk1984 said:
Factory reset no longer required if your bootloader is already unlocked? Does TWRP read encypted storage now? Or is that still a problem?
Click to expand...
Click to collapse
As far as I know, TWRP still doesn't have decryption fully working just yet, but installing Magisk works fine without any factory resets.

prozo said:
Thanks for the detailed guide, it worked great!
Any idea how to install xposed sdk 25? I tried the adb sideload function and the Magsik Module but both failed. Any ideas?
Click to expand...
Click to collapse
Xposed works fine for me. Make sure you installed the correct Xposed Installer/Manager apk linked in the thread for the Xposed Module. Also, it may take a reboot or two for Xposed to fully activate.

Did anyone manage to disable encryption? I tried everything and failed

bmg1001 said:
Xposed works fine for me. Make sure you installed the correct Xposed Installer/Manager apk linked in the thread for the Xposed Module. Also, it may take a reboot or two for Xposed to fully activate.
Click to expand...
Click to collapse
Maybe I'm not gathering the information correctly, using the Magisk Module itself doesn't work, sideloading the zip file via the adb fastboot TWRP.img doesn't work either, using the actual Xposed APK installer doesn't work either. I rebooted the phone about 4 times before removing it entirely.
Any chance you can walk me through how you got it installed without the TWRP recovery fully installed?

prozo said:
Maybe I'm not gathering the information correctly, using the Magisk Module itself doesn't work, sideloading the zip file via the adb fastboot TWRP.img doesn't work either, using the actual Xposed APK installer doesn't work either. I rebooted the phone about 4 times before removing it entirely.
Any chance you can walk me through how you got it installed without the TWRP recovery fully installed?
Click to expand...
Click to collapse
All I did was install the Xposed APK and then the Xposed Magisk Module. After two reboots, the apk said everything was working. This is the apk I used: https://drive.google.com/file/d/16-OHpswcngp1KLtkWCBDwwl8AvFafR5H/view?usp=drivesdk

bmg1001 said:
All I did was install the Xposed APK and then the Xposed Magisk Module. After two reboots, everything was working. This is the apk I used: https://drive.google.com/file/d/16-OHpswcngp1KLtkWCBDwwl8AvFafR5H/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks for replying so quickly I appreciate it, the file you linked keeps opening on my end and fails to install saying it's corrupt

prozo said:
Thanks for replying so quickly I appreciate it, the file you linked keeps opening on my end and fails to install saying it's corrupt
Click to expand...
Click to collapse
The apk should be the same one found here: https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268

bmg1001 said:
All I did was install the Xposed APK and then the Xposed Magisk Module. After two reboots, the apk said everything was working. This is the apk I used: https://drive.google.com/file/d/16-OHpswcngp1KLtkWCBDwwl8AvFafR5H/view?usp=drivesdk
Click to expand...
Click to collapse
Alright I got it to work
So I didn't use the APK instead I downloaded the zip from the XDA thread that is specifically for Magisk Module and then added via the modules tab on the left side of the Magisk Module APK.
After I restarted I had the newly installed APK to download and install the proper version of Xposed 88.2 sdk25
Another restart and boom I got the active module notification in green.
Thanks man!
Thread for downloads can be found here:
https://www.google.com/amp/s/forum....ed/unofficial-systemless-xposed-t3388268/amp/

Thank you for this!
My PH-1 is arriving today. SooOoo excited!

spotmark said:
You need to flash the system and boot images from Invisiblek's stock ROM dump. You'll then be unrooted and will be able to accept the update.
Click to expand...
Click to collapse
Would using flashfire work to install the ota?

drocny87 said:
Would using flashfire work to install the ota?
Click to expand...
Click to collapse
Couldn't tell you. I just used TWRP to flash the system and boot, and then took the update, and then rerooted.

Lost TWRP and root after update to MIUI 10

Hello,
I have a Mi Mix 3, MIUI global 10.2 stable, 10.2.2.0 PEEMIXM.
I managed to root, install TWRP and gcam after a few days of trying.
* Two days ago I updated from phone settings (About phone, Check updates ...)
* I lost both root and TWRP.
* I tried exactly the previous methods to root and phone stuck at booting (three dots flicking on the screen) - via PC / adb / fastboot.
* After that, I reset phone to factory settings and try again - boot in fastboot, try to flash TWRP and I get this error message: error cannot load TWRP.img file (not available or missing).
I also mention:
1. Phone was already rooted by the same procedure
2. Phone is unlocked
3. Dev options / USB debugging check
4. I renamed TWRP.img with recovery.img
5. I even try "TWRP" without extension ".IMG" (last week before the update I succeeded this way - no .img in the name of the file)
Please help
I need something so that I can root phone again AND won't delete TWRP and root after next update.
Thx very very much.

Any software update on this phone will overwrite TWRP if it has a recovery partition image, which most Xiaomi updates do have. There is a way to block it from getting overwritten by booting the phone, which has been implemented in the latest versions of the Chinese TWRP image. I do not know if they have been implmented on the official TWRP for our device.
Based on what you posted, it sounds like you probably need to reboot into the bootloader and use fastboot flash recovery "TWRPIMAGE.IMG" to install TWRP, then hold VOL Down + Power and reboot into TWRP. Once that is done, you can root again using MAGISK or whatever you choose to use for root.

PWn3R said:
Any software update on this phone will overwrite TWRP if it has a recovery partition image, which most Xiaomi updates do have. There is a way to block it from getting overwritten by booting the phone, which has been implemented in the latest versions of the Chinese TWRP image. I do not know if they have been implmented on the official TWRP for our device.
Based on what you posted, it sounds like you probably need to reboot into the bootloader and use fastboot flash recovery "TWRPIMAGE.IMG" to install TWRP, then hold VOL Down + Power and reboot into TWRP. Once that is done, you can root again using MAGISK or whatever you choose to use for root.
Click to expand...
Click to collapse
Thank you very much for your time and information. I must add that I was able to flash TWRP according to the procedure explained above, but I couldn't enter/access TWRP recovery. Then, I tried to re-flash TWRP and I always get the message: "error cannot load 'twrp.img' no such file or directory"
And I've tried several methods, several TWRP, different USB cables - almost everything you can imagine. Still, I cannot load the TWRP.img - it's not found. I must say I follow exactly the procedure explained in every posts.
What options do I have?

If you are using adb to load twrp, try putting it in the c/ of your pc, and putting twrp image in the adb folder, and if that didnt work, try renaming the img file to pocorecovery

[CLOSED][OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7.1 | Crystal |

{
"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"
}
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
1 . Download twrp-3.4.0-0-CTL_sprout.img & twrp-installer-3.4.0-0-CTL_sprout.zip copy in one folder
2. connect phone to pc boot your phone to download mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot boot twrp-3.4.0-0-CTL_sprout.img
6. now your phone will boot in to twrp
7. now copy twrp installer.zip in to your phone from pc using type c usb cable
8. now flash twrp installer zip ( this will make your twrp permanent )
10. now flash magisk or what ever your wish and press reboot system
11. now if you people want to boot in to twrp? power off your phone connect to pc or charger
& wait for battery logo and press volume up and power button for 8 seconds now you will boot in to twrp
Download Android 10 Twrp-3.4.0-0 From Here
​For More Information About Status Official Click Here​
​
XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 7.1
Contributors
Raghu varma
Source Code: https://github.com/TeamWin/android_device_nokia_CTL_sprout
My build script https://github.com/RaghuVarma331/scripts
Version Information
Status: Stable
Current Stable Version: 3.x
Stable Release Date 2019-01-26
Created 2019-01-26
Last Updated 2020-06-25

Hi Raghu, I appreciate the work you are doing for the Nokia community!
I have a question... if I boot directly into TWRP instead of flashing TWRP over my stock recovery, is it truly necessary to reflash the stock recovery? Like for instance, I only want to load magisk on my device/create a nandroid backup and keep stock recovery and stock OS until the Android Q release. Though, from experience from other devices I have owned... booting directly into TWRP instead of flashing only is temporary and keeps the stock recovery intact. I am not sure from your tutorial if I truly need to flash my stock recovery after just booting TWRP temporarily?

usernamedoesnotexist said:
Hi Raghu, I appreciate the work you are doing for the Nokia community!
I have a question... if I boot directly into TWRP instead of flashing TWRP over my stock recovery, is it truly necessary to reflash the stock recovery? Like for instance, I only want to load magisk on my device/create a nandroid backup and keep stock recovery and stock OS until the Android Q release. Though, from experience from other devices I have owned... booting directly into TWRP instead of flashing only is temporary and keeps the stock recovery intact. I am not sure from your tutorial if I truly need to flash my stock recovery after just booting TWRP temporarily?
Click to expand...
Click to collapse
if you want to get back to your stock recovery just flash your stock boot.img of the respective security patch
for example you flashed twrp on may 2019 pie
and now you want to get back to stock recovery?
so just flash using fastboot flash boot boot.img ( may 2019 boot.img)

Raghu varma said:
if you want to get back to your stock recovery just flash your stock boot.img of the respective security patch
for example you flashed twrp on may 2019 pie
and now you want to get back to stock recovery?
so just flash using fastboot flash boot boot.img ( may 2019 boot.img)
Click to expand...
Click to collapse
Thanks for the info! Unfortunately, I couldn't pull my stock recovery from adb and had to use the terminal inside TWRP to pull my recovery. After successfully getting stock recovery, I patched the stock recovery (after copying) to my external SD with magisk and flashed that via adb. Magisk is now installed and I am satisfied.
Note: this is relatively the first time I am leaving stock recovery on my device vs custom recovery to keep the OTA updates. This is because there isn't much of a dev community here at the moment and not much to do on the device.

New Build Is Up
Based On R40
Android version - pie
twrp- based on June 2019
################ The final Main installation procedure #################
Note - this will work only On June 2019 Security Patch And From Now i will update Twrp Every Month
1 . Download twrp-3.3.1-0-CTL.img & twrp-installer-3.3.1-0-CTL.zip copy in one folder
2. connect phone to pc boot your phone to download mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot boot twrp-3.3.1-0-CTL.img
6. now your phone will boot in to twrp
7. now copy twrp installer.zip in to your phone from pc using type c usb cable
8. now flash twrp installer zip ( this will make your twrp permanent )
10. now flash magisk or what ever your wish and press reboot system
11. now if you people want to boot in to twrp? just power off your phone connect to pc or charger
& wait for battery logo and press volume up and power button for 8 seconds now you will boot in to twrp
congratulations now you are successfully booted in to twrp

@Raghu varma
Any telegram group for development? If that exist, please add me t.me/theHari08.

Note - Twrp Support is back for Nokia 7.1
Changelog
13-12-2019
* Initial android 10 twrp builds are up
* Twrp based on 3.3.1-0
* Supports on Android 10 stock roms and custom roms
* supports on Android 9 stock roms and custom roms
* Follow instructions as i mentioned above in the xda thread for installation
* Omni sources based on latest r47
* Decryption works

Hi,
I used to be into flashing phones back in the day but now I'm a bit rusty so my question is simple:
Do I have to unlock the bootloader first before I can flash twrp? It is a painpoint for me on this phone that there is no simple way to do that.
Thanks.

giant_karlik said:
Hi,
I used to be into flashing phones back in the day but now I'm a bit rusty so my question is simple:
Do I have to unlock the bootloader first before I can flash twrp? It is a painpoint for me on this phone that there is no simple way to do that.
Thanks.
Click to expand...
Click to collapse
Before you can modify anything on a phone you always have to unlock the bootloader. Since Nokia does not allow official bootloader unlocks, we have to go through a paid method (see other threads about unlocking the bootloader here).

this guy will do it for a small fee well worth it ...

Added official support

Android 10 TWRP doesn't work on 7.1 december update
Hey,
Thanks for all the hard work you're putting into this project, really helped me when I was using android 9.
But I can't seem to make the latest version you uploaded work now that I'm on android 10. When I try to boot the image file I'm stuck on the android one logo, no matter how much I wait.
So I was wondering if the latest update isn't supported yet or if I'm doing something wrong.
Really sorry to bother you if it's the former.
Have a nice day.

Reysen said:
Hey,
Thanks for all the hard work you're putting into this project, really helped me when I was using android 9.
But I can't seem to make the latest version you uploaded work now that I'm on android 10. When I try to boot the image file I'm stuck on the android one logo, no matter how much I wait.
So I was wondering if the latest update isn't supported yet or if I'm doing something wrong.
Really sorry to bother you if it's the former.
Have a nice day.
Click to expand...
Click to collapse
*make sure your phone bootloader is unlocked.
* make sure you downloaded twrp files from xda thread download links
* make sure you follow steps as i mentioned above
according to your info i tested again on my Nokia 6.1 Plus android 10 stock rom based on december security patch.
Nokia 7 Plus , Nokia 7.1 , Nokia 6.1 & Nokia 6.1 Plus all sources are same
so it should work on 7.1 too make sure you re flashed stock rom and test again because trying several times on same partition may corrupt and failed to boot.

Hey, thanks for your fast answer.
*make sure your phone bootloader is unlocked.
Click to expand...
Click to collapse
The bootloader is indeed unlocked
* make sure you downloaded twrp files from xda thread download links
Click to expand...
Click to collapse
I tried multiple versions from the sourceforge link.
* make sure you follow steps as i mentioned above
Click to expand...
Click to collapse
I'm stuck at "boot TWRP" step as there is only the android one boot screen and I can only reboot. Though for some reason I can still use some fastboot commands (such as fastboot reboot bootloader).
I never modified the system partition on my phone through fastboot, only flashed a magisk patched boot.img when I was still on android 9.
Before upgrading to android 10, I patched the stock boot.img and did a factory reset. Then I did all the available updates through the phone update system. Never used a custom rom, so everything should be stock.
Forgot to mention but the phone isn't bricked or anything, it work normally without any issue. I just can't run TWRP for some reason.
Here's the oem information if that can help you
Thanks and have a nice day
(Unfortunately I can't upload pictures or post links)

Reysen said:
Hey, thanks for your fast answer.
The bootloader is indeed unlocked
I tried multiple versions from the sourceforge link.
I'm stuck at "boot TWRP" step as there is only the android one boot screen and I can only reboot. Though for some reason I can still use some fastboot commands (such as fastboot reboot bootloader).
I never modified the system partition on my phone through fastboot, only flashed a magisk patched boot.img when I was still on android 9.
Before upgrading to android 10, I patched the stock boot.img and did a factory reset. Then I did all the available updates through the phone update system. Never used a custom rom, so everything should be stock.
Forgot to mention but the phone isn't bricked or anything, it work normally without any issue. I just can't run TWRP for some reason.
Here's the oem information if that can help you
Thanks and have a nice day
(Unfortunately I can't upload pictures or post links)
Click to expand...
Click to collapse
Well i don't want to waste my time infront of sitting xda and answering questions like customer care but still yes i will help you out in this
1. just don't use patched boot images
2. Flash stock rom again for fresh start
3. If you are confused about flashing stock rom process
Go ahead to this link
https://forum.xda-developers.com/nokia-7-1/development/tool-stock-rom-flash-tool-nokia-7-1-t4023959
4. After booting in to stock rom power of your phone & press volume down & power button for download mode
5. now open cmd in twrp download folder
6. type fastboot boot twrpname.img
7. Now your phone reboots to twrp
8. Decrypt your phone using your lock screen password,pin or pattern (if you keep security)
9. Now flash magisk of what ever you want but make sure you flash the stuff according to my loyal steps. Which i mentioned my xda threads in 7.1 xda forums
Peace !

Raghu varma said:
Well i don't want to waste my time infront of sitting xda and answering questions like customer care but still yes i will help you out in this
1. just don't use patched boot images
2. Flash stock rom again for fresh start
3. If you are confused about flashing stock rom process
Go ahead to this link
https://forum.xda-developers.com/nokia-7-1/development/tool-stock-rom-flash-tool-nokia-7-1-t4023959
4. After booting in to stock rom power of your phone & press volume down & power button for download mode
5. now open cmd in twrp download folder
6. type fastboot boot twrpname.img
7. Now your phone reboots to twrp
8. Decrypt your phone using your lock screen password,pin or pattern (if you keep security)
9. Now flash magisk of what ever you want but make sure you flash the stuff according to my loyal steps. Which i mentioned my xda threads in 7.1 xda forums
Peace !
Click to expand...
Click to collapse
Hi,
I flashed my nokia 7.1 like instructed and everything went well (though I noticed it wasn't the latest version, but that's a detail).
Went into the bootloader and tried running TWRP but still had the same issue as before (stuck on the android one boot, it was a totally stock ROM, the one provided on your other post).
So I used the boot.img from the stock ROM you uploaded and patched it, then flashed it in the bootloader and it worked.
So even though TWRP still doesn't work in the end I did what I wanted to do, so thanks for your help.
And again, thanks for all the work you're doing, sorry to bother you.
Have a nice day.

Same problem here - unlocked my sons' Nokia 7.1 today via techmestos service, rebooted into the downgraded Android, entered setup and started the mandatory Android upgrade, went through that successfully, activated ADB, got into Download mode and ran the following command:
Code:
fastboot boot twrp-3.3.1-0-CTL_sprout-10.0-20200109.img
downloading 'boot.img'...
OKAY [ 1.058s]
booting...
OKAY [ 5.058s]
finished. total time: 6.116s
Phone screen changed to the 'bootloader unlocked' screen and then the usual AndroidOne boot screen appeared. But neither TWRP nor Android came up ...
The downloaded files are OK, I checked the sha1sum on both of them
Any hints what to do here?`How can I help to track this down?

husky69 said:
Same problem here - unlocked my sons' Nokia 7.1 today via techmestos service, rebooted into the downgraded Android, entered setup and started the mandatory Android upgrade, went through that successfully, activated ADB, got into Download mode and ran the following command:
Code:
fastboot boot twrp-3.3.1-0-CTL_sprout-10.0-20200109.img
downloading 'boot.img'...
OKAY [ 1.058s]
booting...
OKAY [ 5.058s]
finished. total time: 6.116s
Phone screen changed to the 'bootloader unlocked' screen and then the usual AndroidOne boot screen appeared. But neither TWRP nor Android came up ...
The downloaded files are OK, I checked the sha1sum on both of them
Any hints what to do here?`How can I help to track this down?
Click to expand...
Click to collapse
TWRP went official so technically you can go to the TWRP site and download the current there
In addition to it going official, there is no need to download both the img and zip installer with it.
https://dl.twrp.me/CTL_sprout/
You can now just flash (fastboot flash recovery twrp-3.3.1-0-CTL_sprout.img).
https://twrp.me/nokia/nokia7.1.html
Things to keep in mind: If you have a PIN or Passcode you should disable it on the ROM before booting up to TWRP because of encryption.
If you flash another ROM such as Lineage OS shortly after flashing TWRP, it will replace the TWRP with the Lineage OS recovery. So you will probably have to flash TWRP again.
I hope that this works?!

i have android 9 is there a twrp image for 9?

Alas, this does not help, the same problem, the phone hangs on the logo)
P.S
executed the commands like this:
fastboot flash recovery (error issued)
fastboot boot
and successfully loaded into TWRP

General Official Android 13 firmware is now available

It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/...300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.

MarekPietrzak said:
It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/UL-ASUS_I005_1-ASUS-33.0210.0210.200-1.1.300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.
Click to expand...
Click to collapse
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo

Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse

MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
hey, Thanks for replay, i am facing now another messeges.
1- the phone does not charging at all
2- when i plug in into chrage its reboot again and again.
3- the bootloader is open, but when i try to flash any files through bootloader i get:
FAILED (Status read failed (Too many links))
or
FAILED (remote: 'Warning: battery's capacity is very low
to recovery mode i am unable to go there
i tried boot or flash the twrp.img also only boot.img also flash_raw_and_wipe_data.cmd
nothing helps me!!!

Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.

MarekPietrzak said:
Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.
Click to expand...
Click to collapse
I've tried leaving it on overnight and it never charges, there's even no charging lights.
Yesterday I tried flashing via Bugjeager and it didn't work either (betwenn to android devices)
Although the bootloader is unlocked, it gives me a Not Allowed In Lock State message!
the current version of the installed firmware is that old that i flashed WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw, it is non extractable so i cant get the boot.img of it!

I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system

MarekPietrzak said:
I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system
Click to expand...
Click to collapse
wow you are alive haha i thought you not gonna answer me again. ok just 1 second

rami88436 said:
wow you are alive haha i thought you not gonna answer me again. ok just 1 second
Click to expand...
Click to collapse
Sometimes I can be a bit slow to respond as I am on the university during day. Hopefully your issue seems to be possible to be solved just by flashing raw firmware and wiping data partition.

so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?

rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root

chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse
try root your phone through kirnal su

chairman011 said:
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root
Click to expand...
Click to collapse
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.

I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse

MarekPietrzak said:
I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
Click to expand...
Click to collapse
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
rami88436 said:
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.
Click to expand...
Click to collapse
Oh ok ok makes sense. Usually when I face a brick problem I just flash raw firmware fastboot

Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
chairman011 said:
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
Click to expand...
Click to collapse

MarekPietrzak said:
Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
Click to expand...
Click to collapse
Oh wow thank you man I'll give it a shot.

I found a gui-based app on github to systemlessly debloat, it is easier to use than this script I posted link to. Here is the link: https://github.com/sunilpaulmathew/De-Bloater

Does anyone have the full RAW firmware, flashed via fastboot? Thank you all

ThienAn2023 said:
Does anyone have the full RAW firmware, flashed via fastboot? Thank you all
Click to expand...
Click to collapse
Mod. edit: private link removed. alecxs