Code:
[SIZE=3]
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/[/SIZE]
Here is the TWRP 3.1.1-0 Recovery for Nokia 3 (heart) smartphone.
You can update it from old TWRP recovery else install it as fresh by using adb or flashify app from google play store.
</> CHANGELOG ? : </>
Code:
[SIZE=4]
*/
* Backups will now include adopted storage keys (Dees_Troy)
* Fixed an adb restore issue (bigbiff)
* Fixed line wrapping in the GUI terminal (_that)
* Updated TWRP source code to AOSP 7.1.2 (Dees_Troy) Updated TWRP source code to AOSP 7.1.2
*/
[/SIZE]
</> DOWNLOAD ? </>
TWRP-3.1.1-0-UNOFFICIAL-Heart.img
</> NOTE ? : </>
I have already worked on TWRP and tested for some weeks ago before my Nokia 3 got broken , but forgot to post it.
Kindly report any bug seen.
Contributors
iykeDROID™
ROM Kernel: Linux 3.18.x
Based On: LineageOS
Version Information
Status: Stable
Created 2018-03-13
Last Updated 2018-03-13
tnx for twrp, it works great, btw there is still bug with wrong battery percentage, but it doesn't affect flash performance.
ok, after some testing, i found a serious issue, i successfully reflashed xposed, but other zips that i flashed failed because it couldn't unzip file while it unzipped successfully on other twrp by @mediafire007
Here is a screenshot of that problem
okay, i will look into it.
but first, try to rename the file without "spaces" , save and flash it again.
report back.
thanks
SkaboXD said:
tnx for twrp, it works great, btw there is still bug with wrong battery percentage, but it doesn't affect flash performance.
Click to expand...
Click to collapse
with the battery, its a bug in the kernel, AFAIK.
ok, i found another bug, when i wanted to rename file in different ways to flash file, it didn't worked. But when i wanted to rename file with letters and numbers without spacing, it would display this error starting "mv".
Comparation between mediafire007 twrp and iykeDROID™ twrp:
mediafire007 twrp:
- battery percentage is incorrect
- have a bug that touch doesn't work for 5-10 seconds but then it works good
- it loads internal storage and sd card fast
- it flashes any file without problems
- it uses older twrp version
iykeDROID™ twrp:
- battery percentage is incorrect
- touch works smoothly
- it loads internal storage and sd card a bit slower
- it mostly fails at flashing files
- it uses newer twrp version
About backing up, only partition that can't be backed up is system image (system.img) on both twrp.
That's not twrp issue, it's because system image is protected by encryption.
I didn't tried flashing backup without system image so you will risk to bootloop. (Edit: it works, you can flash backup without problems)
I will update this post if new twrp version comes out and hopefully fix bugs.
nokia 3
ihave been received the new oreo update for my nokia 3 ta-1032
Bug report.
Hello developer of old TWRP for Nokia 3, i am going to report some bugs based on what i have seen and experienced, if you do see this message, please note that i am willing to become a tester for the recovery of this device, i am now going to start stating the problems, please also note that i am using Nokia 3 with Pie ROM, Bootloader unlocked, rooted with Magisk, i am using TWRP 3.2.3 from https://unofficialtwrp.com/nokia-3-root-twrp-3-2-3/, i also believe this is the same with the TWRP that @RevanthTolety made, i know that the TWRP you made is old, but still hopefully you could do something about this, let's begin.
i have attached the pictures of the bugs, as well as logs, to help you all regarding about this problem, i have messaged all five of you in hopes that some of you are still willing to develop a proper, working recovery for the Pie ROM of this device, or at least team up in making one, anything as long as this project will still continue or something will be done.
Bugs i have found:
1. Decrypting of data, the recovery is asking me for a password and i have no idea what to do, i have never encrypted my device, or anything, and here is what i have done so far:
1a. Formatted data through TWRP, rebooted into recovery and applied root.
1b. Wiped data through TWRP, rebooted into recovery, then applied with root.
1c. All of the above, except this time i flashed no verity opt encrypt, didn't work.
1d. Formatted data through fastboot, rebooted into recovery immediately and applied root.
For the most part, by the time i managed to format or wipe my data/userdata, i am able to gain access on it through TWRP, and the recovery isn't asking me for a password, but once i am able to fully set up my device and it reaches the home screen, not putting any screen locks, just Swipe, rebooting into recovery again, and now it asks me for a password, i tried "default_password" and "password" but it didn't work, at this moment, i can only flash zips through my MicroSD Card, the recovery doesn't have access to my internal storage and i couldn't make a backup with my userdata.
2. TWRP gets replaced with stock recovery if you do not boot into it immediately after flashing, trust me, this is where i got frustrated the most, i was about to smash the phone because of this! I still had to root to ensure that the recovery will stay, or else at next boot the stock recovery will be back.
3. Battery percentage is shown incorrectly, based on the 5 forums i've seen which is all related to porting TWRP for this phone, this error has been very consistent.
4. The recovery keeps showing me a prompt of asking whether to keep System read-only or not, even though i selected the box "Don't show me this screen again.", it still comes back anyway.
5. The recovery complains about '/hidden/emmc_hidden" not being found and all that.
6. I cannot save my language, even though i already toggled it through the settings of the recovery.
7. Touch is very slow during the first screen which is the "Keep System read-only?"
Here are the things i confirmed to be working:
MicroSD Card access
OTG access
Installing .zips
I cannot test the backup and restore option since i can't access data through it, i don't want to lose progress.
That's all of the bugs i have seen so far, i am going to use my friend's phone who happens to own a Nokia 3 for testing the recovery, if i still haven't received a response within 1 week i will return the cellphone, you could contact me through Telegram, Facebook and other social media sites such as Instagram, i am willing to take the risk, please contact me if you all are still willing to continue with the development of TWRP for this cellphone.
Can you give for nokia 3 android 9
Can you give for nokia 3 android 9 twrp please
Good job on this! I wouldn't have used this phone anymore without your recovery
I've tried flashing numerous types of stock Nokia 3 ROMS I've managed to lay my hands on. Every time I try it through this version of TWRP, from an sd card, it returns an error stating that it is an invalid ZIP file format. Attempting to flash the stock ROM through "fastboot flash the_name_of_the_.zip" gives an error stating it cannot determine the image filename.
Can anyone help me?
When i type fastboot flash recovery twrp.img it shows image file is corrupted
Please help me!!!!
I have unlocked bootloader of my Nokia 3. I have also flashed the TWRP successfully, but when I boot my Nokia 3 in recovery mode, it enters the stock recovery!
Please HELP!!!!
This is worked with nokia 3 ta-1032 android 9.0?
hello, I need help with my nokia 3 TA-1020, I think I lost the system, because It's booting straight to twrp So I wanna ask if there's any twrp backup of the stock android, so i can recover it and use it (even better if rooted)
Related
Hey,
I wanted to create an nandroid backup in TWRP and got error 255 in the process.
I got the log of the failed update:
cloud.directupload.net/dfZq
So i searched for a solution, and the internet said that i should remove the file wich causes backup to fail. The logs said it was '/system/app/AndroidPay'
This is a file, not a folder.
So i removed the file, keeping an backup of it, booted into TWRP and the backup still failed.
To my surprise the boot into OxygenOS fails now. It shows the Oneplus Powerd by Android logo, turns black and reboots into twrp. Recovery and Bootloader seems to work fine.
So I connected my device with my computer and tried to get the file back to '/system/app' using adb.
I tried 'adb push AndroidPay /system/app' and it seems to be transferred succesfully, however the boot into oxygenOS is still not working.
I think it can be fixed by formatting the device and flash OxygenOS new to it, but I really don't wanna do that.
General Information:
Oneplus 3
OxygenOS 3.3.4
Rooted
Xposed Installed
No custom kernal
TWRP 3.0.2-0
File wich may be broken: cloud.directupload.net/dfZs
Is there an easyer way than resetting my whole phone to get it to work ?
I'm sorry for language mistakes or maybe leaving relevant information.
Thank you for help
I've had same problem today, my solution is restore "System" part (only system) from old backup, it saved my data and OP3 works fine after that
Wipe system, then flash OOS and it should work fine. If it doesn't Im afraid you need to do a full clean install since it isn't system related then.
Hello,
I am a happy owner of OnePlus 3 and at the beginning when I got this Smartphone and run it, I had to set-up a Pin which was also used for Encryption,
due to the decision that I wanted to change it, I have tried numerous things to do this, either via System -> Security, System -> Lock Screen or TWRP Recovery.
Then I have stumbled upon a wiping feature in TWRP. (TWRP Menu -> Wipe) where there was a couple of options like Advanced Wipe, Format Data and Swipe to Factory Reset. So I have
decided to see what Format Data does which showed me the following statement before I continued with it "Format Data will wipe all of your apps, backups, pictures, videos, media and
removes encryption on internal storage". Well when it said it removes the encryption I have proceeded because at this point where all of the methods failed I wanted to remove and
re-encrypt my OnePlus 3 again in order to change my encrypting pin. Ok, cool this worked perfectly except that now I can't restore my original rom or encrypt my OnePlus 3 again ....
Then I have flashed CyanogenMod 13 Nightly from August (The latest one on the CyanogenMod website) and when I went into System -> Security there was Encrypt button instead of saying
Encrypted at the top of the menu then I have played around with setting up a new Pin/Password and when I went throug all the process at the end the following happens within a few
seconds: a green dissasembled android shows then screen turns black and returns to lock screen. I checked if OnePlus 3 is encrypted and is not. This is not the normal as usually
encrypting takes some time.
Also, I have tried to restore my original rom which came with my smartphone and was encrypted, when I restored it, OnePlus 3 stucks on the first screen showing OnePlus logo on the
middle of the screen and text "Powered by Android" on the bottom of the screen.
I presume that CyanogenMod 13 encryption is broken or that I shouldn't have format Data ?
Is there any way that I can encrypt my smartphone again ?
P.S I know that OnePlus 3 encryption is handled by Hardware.
You can try downloading the official OxygenOS ROM, flashing it and trying to encrypt again. Last I tried doing it on Sultan's CM13, it didn't work, so it might be a CM problem.
As per my knowledge, if you flash stock OxygenOS rom and also be on stock oneplus recovery. Performing a Factory Reset will automatically encrypt your device again. But you must be on stock recovery + stock kernel + stock rom in order for it to work.
abhibnl said:
As per my knowledge, if you flash stock OxygenOS rom and also be on stock oneplus recovery. Performing a Factory Reset will automatically encrypt your device again. But you must be on stock recovery + stock kernel + stock rom in order for it to work.
Click to expand...
Click to collapse
Why do I need to be on stock recovery ?
Won't TWRP work just fine ?
formating data with TWRP -28 will decrypt your phone, it's madethis way so it can work on beta 9 and f2fs ...
that said i had encrypted device before on CM
so if you're not using beta 9 and your data partition is not f2fs, you can have an ecrypted device, the easiest way is to sideload official rom 3.2.8 (make sure you're on stock recovery and start adb sideload from there) , after the sideload the phone will be encrypted, if you're staying at MM, fastboot TWRP .22 or 23 or just the official in case .28 decrypts the phone.
Gliop022 said:
Why do I need to be on stock recovery ?
Won't TWRP work just fine ?
Click to expand...
Click to collapse
Well man i want you be on as much safe side as possible. When you perform factory data reset on stock recovery, it will wipe and reformat your internal memory as well. TWRP only wipes data partition, and you need to format whole internal memory manually. But stock is recommended for full compatibility.
Ok, I have finally re-encrypted my smartphone.
So for the future people who have the same problem as I have, do the following:
SIDE NOTE: You don't need to unroot anything, just re-flash original Oxygen OS and go forwards from there
1) Download Oxygen OS from official website (downloads.oneplus.net)
2) Copy it over to internal storage
3) Enter Recovery Mode => Volume Down + Power Button
4) Flash downloaded .zip file via Recovery Mode (SIDE NOTE: The flashing progress might look like it have a loop but it takes a little bit of time to flash it, more than CyanogenMod anyway).
5) Now, after you have flashed the system .zip file and rebooted your smarpthone, it will take some time to load so don't panic that you have stuck in bootloop as it again, takes some time to load the first time.
SIDE NOTE: My suspicions are that it takes some time to flash and run the first time because it needs to set-up some encryption parameters or something like that but I might be wrong.
6) Then when you finally get to the wizard screen and go through the initial setup like wi-fi, sim card etc, the system will ask you if you want to protect device before it turns on, you choose yes and type your PIN or Password. After that step your smartphone is successfully encrypted again, enjoy !
Gliop022 said:
Ok, I have finally re-encrypted my smartphone.
So for the future people who have the same problem as I have, do the following:
SIDE NOTE: You don't need to unroot anything, just re-flash original Oxygen OS and go forwards from there
1) Download Oxygen OS from official website (downloads.oneplus.net)
2) Copy it over to internal storage
3) Enter Recovery Mode => Volume Down + Power Button
4) Flash downloaded .zip file via Recovery Mode (SIDE NOTE: The flashing progress might look like it have a loop but it takes a little bit of time to flash it, more than CyanogenMod anyway).
5) Now, after you have flashed the system .zip file and rebooted your smarpthone, it will take some time to load so don't panic that you have stuck in bootloop as it again, takes some time to load the first time.
SIDE NOTE: My suspicions are that it takes some time to flash and run the first time because it needs to set-up some encryption parameters or something like that but I might be wrong.
6) Then when you finally get to the wizard screen and go through the initial setup like wi-fi, sim card etc, the system will ask you if you want to protect device before it turns on, you choose yes and type your PIN or Password. After that step your smartphone is successfully encrypted again, enjoy !
Click to expand...
Click to collapse
Hello Gliop022,
Do you know if flashing OxygenOs stock from TWRP 3.1.0 encrypts the phone or do I have to be on stock recovery?
Then once the phone is encrypted, are you able to flash an OOS based ROM (e.g. FreedomOs) and keep the encryption?
Hi guys,
Since 2 days I ****'d up my phone. I have been totally disconnected since then.
Trying to fix this situation ASAP.
I wanted to update from OmniROM Android 6.0 to 7.1.2.
I had unified storage or LVM, i don't know which, 1 single internal SD.
Wiping too much stuff in TWRP was the start of my problems is my guess.
Result: no internal memory visible (0mb)
After some time I fixed that. I went through the whole lot: brick phase, bootloop, etc.
I even poked out the power button and disassembled the phone thinking the power button was broke!
Then with a combination of the unbrick tool and others I am now in the following situation:
I can get into fastboot mode, but no ROM is installed, when flashing TWRP 3.1.1 I get a black screen when booting into recovery.
When flashing stock omni recovery 1.0 this works, but I can't do anything. (Installation failed)
So how do I go on from here?
I'm suspecting the unified storage/lvm is the culprit, keeping me from being able to install stock coloros 2.1.5i or others.
A lot of useful information from the old Oppo forums is gone..
Thank god for XDA! :good:
Any help to restore my daily driver would be greatly appreciated!
I've been roaming the forums for multiple hours and days at this point, flashing everything that has .img or .zip I can find... :silly:
*** Update: Using recovery 4.4, I now have stock oppo recovery v1.2.
When I try to merge/unmerge the partition, I get stuck in "Wiping, please wait" for more than 45 minutes, so I quit.
The status tells me: non-unified partition. So I don't know the current state of my Internal memory...
Still installing OMNI or coloros roms doesn't work..
Now, pushing files to the device gives me: no permission.
You need an SD card for this:
Get into TWRP using the recovery installer for find 7 (via fastboot) than flash the setup LVM zip after that use the recovery installer again to flash the color os recovery then flash project spectrum 1.3 for Oppo find 7/7a then everything should be repaired
This is the LVM zip:
https://androidfilehost.com/?fid=24052804347800902
Edit: I'll send you a personal message with a Google drive Link for project spectrum if you want
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Unlocked bootloader is required.
This device has 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore.
There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring.
You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B.
Changing the slot in TWRP also tells the bootloader to boot that slot.
Warning:
Do NOT switch slots unless you have installed copy-partitions-AB.zip or manually flashed the bootloader on both the slots:
This device comes out of the box with the bootloader installed only on the active slot (eg: bootloader_a).
Once you manually switch slots, your device will use the other bootloader partition (eg: bootloader_b) which is empty because of this factory setup therefore the device won't be able to boot in any way.
For this reason you should install the bootloader on your own on both the slots with fastboot or copy the currently installed one to the inactive slot by flashing copy-partitions-AB.zip at least once.
Note:
Decryption only works when TWRP is permanently installed.
Installation
To temporarily boot this recovery:
Code:
fastboot boot twrp-[B]version[/B]-[B]build[/B]-river.img
To permanently install it:
Temporarily boot TWRP
Put the TWRP image in your external SD Card or, in case you don't have one, push it to /data with adb this way:
Code:
adb push twrp-[B]version[/B]-[B]build[/B]-river.img /data/
Tap Advanced -> Install Recovery Ramdisk -> Navigate to /data or /external_sd and select TWRP -> Swipe to Install
If you previously installed Magisk: Select Fix Recovery Bootloop from Advanced to fix/avoid recovery bootloops
Done! Optionally you can delete TWRP from /data or from your external SD Card now.
Download
AndroidFileHost
XDA:DevDB Information
TWRP for Moto G7, Tool/Utility for the Moto G7
Contributors
Alberto97
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2019-04-14
Last Updated 2019-07-02
I went insane to figure out decryption was not possible by just fastboot booting the image. I hope the hard work paid off
this is a blessing, i was working on twrp as well but hdd fail and it was music to my ears when it was mentioned this post went up in the tele group. so thanks bro
Awesome. Getting mine today now!! )
Sent from my LG-VS980 using Tapatalk
So here's my experience so far.
Backup, works just fine, afaik.
Restore, System,etc results in bootloop. Data restore, gets "extractTarFork() process ended with ERROR: 255"
Not sure if this is already known but figured id share what ive experienced. also feel free to tell me if im doing stuff wrong, it's been a while since i messed with android more than just using it.
Edit: This is with it perm installed.
Is this for all moto g7 versions
Hello
Very happy to see we now have TWRP. In the interest of avoiding bootloops though, I'll wait to install until it's more stable
BTW, I don't know if you guys get this, but on a us retail Moto g7 (unlocked bl obv) every time I try to boot an unofficial image I get
Code:
Command failed: remote error ' '
Any idea on what is happening?
Awesome!
This is exciting stuff. Can't wait to get busy working on it
sd86 said:
So here's my experience so far.
Backup, works just fine, afaik.
Restore, System,etc results in bootloop. Data restore, gets "extractTarFork() process ended with ERROR: 255"
Not sure if this is already known but figured id share what ive experienced. also feel free to tell me if im doing stuff wrong, it's been a while since i messed with android more than just using it.
Edit: This is with it perm installed.
Click to expand...
Click to collapse
Does flashing work?
Sent from my moto g(7) using XDA Labs
Alberto97 said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Unlocked bootloader is required.
This device has 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
Decryption only works when TWRP is permanently installed.
Installation
To temporarily boot this recovery:
Code:
fastboot boot twrp-[B]version[/B]-[B]build[/B]-river.img
To permanently install it:
Temporarily boot TWRP
Put the TWRP image in your external SD Card or, in case you don't have one, push it to /data with adb this way:
Code:
adb push twrp-[B]version[/B]-[B]build[/B]-river.img /data/
Tap Advanced -> Install Recovery Ramdisk -> Navigate to /data or /external_sd and select TWRP -> Swipe to Install
If you previously installed Magisk: Select Fix Recovery Bootloop from Advanced to fix/avoid recovery bootloops
Done! Optionally you can delete TWRP from /data or from your external SD Card now.
Download
AndroidFileHost
XDA:DevDB Information
TWRP for Moto G7, Tool/Utility for the Moto G7
Contributors
Alberto97
Source Code: [url]https://github.com/TeamWin[/URL]
Version Information
Status: Beta
Created 2019-04-14
Last Updated 2019-04-14
Click to expand...
Click to collapse
I followed steps to unlock bootloader, then flashed stock AMZ river. Did a Google restore. Followed steps to install TWRP no issues. Follow steps exactly. Booted into system, no issues. Have not done a backup yet to test. Overall it went perfectly.
Thanks so Much!
Was able to install Magisk through manager. Again all went well and rooted. Successful backup ALSO made through TWRP.
clcombs262 said:
Does flashing work?
Sent from my moto g(7) using XDA Labs
Click to expand...
Click to collapse
I didn't test yet, I'm sure someone will and let us know
Edit: Flashing works, tested flashing Magisk 19 via zip and it installed correctly.
Sent from my moto g(7) using Tapatalk
sd86 said:
I didn't test yet, I'm sure someone will and let us know
Edit: Flashing works, tested flashing Magisk 19 via zip and it installed correctly.
Click to expand...
Click to collapse
Flashing works for me too....
Magisk v19 or v18.1 tho sends me into bootloops. Mind you, I'm running the RR GSI I flashed via TWRP
sd86 said:
So here's my experience so far.
Backup, works just fine, afaik.
Restore, System,etc results in bootloop. Data restore, gets "extractTarFork() process ended with ERROR: 255"
Not sure if this is already known but figured id share what ive experienced. also feel free to tell me if im doing stuff wrong, it's been a while since i messed with android more than just using it.
Edit: This is with it perm installed.
Click to expand...
Click to collapse
Did you restore "system" or "system image"? In the first case It's normal you get a bootloop, you changed the content of the system partition and that triggers verity. You can use "system image" that makes a bit per bit copy of the partition to avoid problems. Obviously that does not work if you manually changed even just a file.
TLDR: Just disable verity, you should be able to do that easily with Magisk.
About the extractTarFork() error instead it's something that I've seen on every device I used TWRP. I never figured out what means, I guess data was not backed up properly but I would not worry about that, it rarely happens. Just to know, did you backup on an external sd or internal storage?
B__B said:
Is this for all moto g7 versions
Click to expand...
Click to collapse
It is for all G7 variants. G7 Play/Power/Plus are different devices and require different builds.
I hope that answered your questione somehow (I'm not sure what you meant with 'versions').
I ment the for the basic g7 and thanks it helps that's what I have
Alberto97 said:
Did you restore "system" or "system image"? In the first case It's normal you get a bootloop, you changed the content of the system partition and that triggers verity. You can use "system image" that makes a bit per bit copy of the partition to avoid problems. Obviously that does not work if you manually changed even just a file.
TLDR: Just disable verity, you should be able to do that easily with Magisk.
Click to expand...
Click to collapse
This can be done with ADB interface as well....
Code:
adb disable-verity
Work moto g7 power??
Alberto97 said:
Did you restore "system" or "system image"? In the first case It's normal you get a bootloop, you changed the content of the system partition and that triggers verity. You can use "system image" that makes a bit per bit copy of the partition to avoid problems. Obviously that does not work if you manually changed even just a file.
TLDR: Just disable verity, you should be able to do that easily with Magisk.
About the extractTarFork() error instead it's something that I've seen on every device I used TWRP. I never figured out what means, I guess data was not backed up properly but I would not worry about that, it rarely happens. Just to know, did you backup on an external sd or internal storage?
It is for all G7 variants. G7 Play/Power/Plus are different devices and require different builds.
I hope that answered your questione somehow (I'm not sure what you meant with 'versions').
Click to expand...
Click to collapse
Internal and thank you very much for the information.
Sent from my moto g(7) using Tapatalk
Do I just flash the standard Magisk zip after installing TWRP? The install process seems to have broken Magisk within Android and it is no longer detected.
Omegapsy said:
Do I just flash the standard Magisk zip after installing TWRP? The install process seems to have broken Magisk within Android and it is no longer detected.
Click to expand...
Click to collapse
Yes, install Magisk after TWRP and yes, Magisk might no longer work after installing TWRP. This happens because of some patching Magisk does to the kernel that gets reverted when you tap on "Fix recovery bootloop".
I haven't had any time to play with my G7 but is there recovery Treble enabled? I'm assuming yes. Has anyone try any of the GSI's for PIe out there? or even the Q beta GSI?
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
C:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:- TWRP boots
- Decryption works
- Rom flashing should work
- Backups should work
- Flash partition should work
- Format/wipe data works
- Backup Restore
- Fastbootd
- System and vendor image flash should work
- Decryption works only in Android 11. Decrytprion for later versions of Android WIP
-USB-OTG - I cannot test, because I have not a USB-OTG cable. Please, send me a result to PM
Note: boot takes about one minute - it required by decryptionInstall guide:You can install it from fastboot using command
Code:
fastboot flash recovery_$(slot) path_to_recovery/recovery.img
Or you can directly boot it:
Code:
fastboot boot path_to_recovery/recovery.img
Download:Link
Sources:
angpysha/android_device_OnePlus_Nord_N100 at android-11 (github.com)
Thanks:hellisabove - for initial device tree
infectedmushi - for device tree for OnePlus 8 with working encryption
TeamWin
Reserved
Reserved
I've tried to boot / flash this on my BE2013. It's just stuck on TWRP splash screen, but with ADB active and seemingly usable.
thomaskmaagaard said:
I've tried to boot / flash this on my BE2013. It's just stuck on TWRP splash screen, but with ADB active and seemingly usable.
Click to expand...
Click to collapse
Disregard. It seems I should have been armed with more patience. People should note it might take quite a while for it to load up.
thomaskmaagaard said:
Disregard. It seems I should have been armed with more patience. People should note it might take quite a while for it to load up.
Click to expand...
Click to collapse
Oh, yes. I forgot to write that boot takes about one minute. Thanks
Thanks for releasing this. Used it this weekend on OnePlus Nord N100 Model BE2013 Oxygen OS 11.0.10.BE83BA
# TWRP recovery-3.7.0-11-08012023 worked for multiple flashed
Was working fine flashing 4 or 5 ROMs to taste test them. CAOS rom worked like a charm. Nothing else worked. Somewhere along the line I deleted a logical partition to make room for Pixel Experience. It suffered flickering / dimming issues so reflashed CAOS.
TWRP was working so well I flashed it to my phone.
# TWRP recovery-3.7.0-11-08012023 stopped being able to mount volume
Then TWRP couldn't mount the partitions for writing anymore. Volume showed 0 bytes available. Fastboot could not recreate logical partitions. Weird thing was I could write a test file in /system but I couldn't flash /system. Fastboot error messages said it could not find partition or there was no room left. Somehow TWRP's ADB shell could get into the /system partition but its flashing could not ?!?
# TWRP recovery-3.7.0-11-08012023 did not see USB drive through OTG cable
Tried to access ROM through USB drive through OTG cable. TWRP could not mount it.
# Recovery
* Had to use MSM tool to cover phone to Stock today.
* After recovery, I flashed CAOS using Fastboot instead of TWRP because I'm not sure if I did something wrong or if TWRP wasn't working properly.
# Can't boot after TWRP backup (no restore)!?!
I booted into TWRP through fastboot boot twrp.img so that it wouldn't write anything. Used TWRP to do a backup and saved backup to external sd card (not the /sdcard directory but the separate external sd card).
So I didn't flash recovery or anything else. I did a backup to an external sdcard. I did not flash or write anything to the phone's memory.
Now when booting it gets stuck on the logo!?!
How do you recover from that?
Looking at /tmp/recovery log shows that twrp wasn't able to mount /data /product
This recovery works well, it flashs every partition except the super partition you can flash it with the terminal of the recovery.
There is one obstacle, which is you need to replace stock product with gsi product to be able to flash lineage 19.1, and to be able to flash larger ROMs you need to delete the system_ext partition (I suppose ). I will attach it to my reply.
The second obstacle is the backup when restored it show some bugs. and the last one is that Android 13 is a little bugy in this slot unlike the other slot.
I flashed successfully the super image with this recovery, thank you guys.
Hi guys, I have good news for you, this recovery works in both slots ( with boot _A10 and boot_A11), so weird but true.
This recovery is fully working, I mean you can flash Zips and IMGs and you even use its built-in terminal to pull or push partitions.
There is one problem which is the resizing, you can do it with CMD command
fastboot resize-logical-partition system_a 4210000000
or
fastboot resize-logical-partition system_b 4210000000
And this can be done anly by flashing the product_a, product_b and the system_ext_b partitions with small size IMGs like product_gsi.img(you need to put this file in the adb-fastboot folder) . (you can flash it in product_a, product_b and system_ext_b. It does not serve anything, it just reduces the size of this useless partitions. You can find it with a working adb-fastboot tool.
Well, this TWRP is flashing Magisk, and I can make a backup, but when I want to restore the backup, errors occur, including the bootloop. Has anyone encountered this problem?