[Official]TWRP 3.1.1-0 for MATE 8
Modified to work with Nougat firmwareTeam Win Recovery Project 3.1.1-0
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
WHY IS IT MODIFIED?
Like you know, the official TWRP here doesn't work on Huawei Mate 8 device, it's why I modified in order it works on our device. This one only works with Nougat firmware.
SUPPORTED DEVICES
Mate 8
DOWNLOAD
twrp-3.1.1-0-next.img - MD5: 82808bdc7ff1452ea15081f033c4f826
What's new in 3.1.1-0 (TeamWin - TWRP):
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
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
My changes:
Code:
TWRP 3.1.1-0
* modified to work on Nougat
* kernel updated from eRecovery (B581 firmware) for proper loop support
* native_package.xml has been added to device specific version from eRecovery (B581 firmware)
* Replaced system folder by the one of eRecovery (B581 firmware)
KNOWN ISSUES
Doesn't work with Marshmallow
Doesn't enable to correctly read the decrypted data - displaying 0 MB when you push the "Install" button - Only with decrypted data
CREDITS
TeamWin - TWRP
Franzyroy (me)
Version Information
Status: Official modified - beta version
Release Date: 2017-05-26
If you like that, hit the THANKS button below !
I can't say anything about this TWRP yet, I haven't tested it, so I do not know what it is worth ... but it is official.
I tried but it doesn't work for me with Nougat.
franzyroy said:
I tried but it doesn't work for me with Nougat.
Click to expand...
Click to collapse
Maybe it's only support for HTC? The twrp we have now (3.0.2) also good enough but only need to improve on the restore data part. As the path restore data broken but of course restore using twrp 3.0.3. Only problem with twrp 3.0.3 doesn't work well with data encryption.
Edit : Yeah. I tried it too. Doesn't work. Maybe it's for MM.
What a pc of junk waste of time to post its not 1985
franzyroy said:
I tried but it doesn't work for me with Nougat.
Click to expand...
Click to collapse
we defo need a port for nougat then... thx for testing
Sent from my Huawei Mate 8 NXT-AL10
dexz said:
Maybe it's only support for HTC? The twrp we have now (3.0.2) also good enough but only need to improve on the restore data part. As the path restore data broken but of course restore using twrp 3.0.3. Only problem with twrp 3.0.3 doesn't work well with data encryption.
Edit : Yeah. I tried it too. Doesn't work. Maybe it's for MM.
Click to expand...
Click to collapse
I checked inside, I confirm it's for MM . But it's really for our device.
c|nder said:
What a pc of junk waste of time to post its not 1985
Click to expand...
Click to collapse
???? WTF ¿¿¿ I would like to understand but I don't see!
jbmc83 said:
we defo need a port for nougat then... thx for testing
Click to expand...
Click to collapse
Maybe it could help us to have a stable version of Nougat.
Not working on MM, I couldn't boot onto recovery
Sent from my Nexus 6P using Tapatalk
M.Noury said:
Not working on MM, I couldn't boot onto recovery
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Really? It doesn't work on Marshmallow? What is this bazaar?
M.Noury said:
Not working on MM, I couldn't boot onto recovery
Click to expand...
Click to collapse
Now that's a surprise.
dexz said:
Now that's a surprise.
Click to expand...
Click to collapse
I made a report here.
franzyroy said:
I made a report here.
Click to expand...
Click to collapse
I think all we need is some dev to look into it. 1% of the report will be reply from the official but then again 1% is better than 0% right. :laugh:
I confirm, 3.1.0.0 hangs on boot.
dexz said:
I think all we need is some dev to look into it. 1% of the report will be reply from the official but then again 1% is better than 0% right. :laugh:
Click to expand...
Click to collapse
Yes I know but well, we must try.
paulcl said:
I confirm, 3.1.0.0 hangs on boot.
Click to expand...
Click to collapse
Unfortunately.
Well, already a good new for us, if I can say, the TWRP 3.1.0-0 doesn't work also for other models, like the Huawei Honor 8. It's not really a good info but at least, we aren't alone with this issue. So we can hope to have a fix nextly or later.
I have flashed TWRP 3.1.0.0 from the honor 8 thread. I managed to boot to recovery. The only thing that not working is data partition not able to format. Got an error unable to find crypto file or something. I know it's for honor 8 but just trying my luck :laugh:
dexz said:
I have flashed TWRP 3.1.0.0 from the honor 8 thread. I managed to boot to recovery. The only thing that not working is data partition not able to format. Got an error unable to find crypto file or something. I know it's for honor 8 but just trying my luck :laugh:
Click to expand...
Click to collapse
Seriously, this one? if it's like the official, I perhaps know the cause, I hope.
Edit:
I decompiled it. This is what I think is the cause, in the recovery.fstab file.
Code:
/data f2fs /dev/block/dm-0
Look into the frd-twrp by example and you'll see fully different. Already, your data isn't a f2fs partition.
franzyroy said:
Seriously, this one? if it's like the official, I perhaps know the cause, I hope.
Click to expand...
Click to collapse
Yes the one.
Edit:
I decompiled it. This is what I think is the cause, in the recovery.fstab file.
franzyroy said:
Look into the frd-twrp by example and you'll see fully different. Already, your data isn't a f2fs partition.
Click to expand...
Click to collapse
I have tried to change data partition to f2fs using twrp 3.0.2 then flashed twrp 3.1.0 and format data but it doesn't work too. Maybe you are right recovery.fstab need to modify?
Related
Hi there,
I wanted to install the latest image of Nethunter (found on build.nethunter.com/nightly) but when I install it with TWRP I keep getting the message : "Unpacking boot image failed" in the log screen.
What I did in order:
- Unlock fastboot mode
- Flash TWRP recovery (found on build.nethunter.com/twrp)
- Reboot on TWRP
- Install kernel ( kernel-nethunter-oneplus3-nougat-3.15.4-20170126-2226 )
- Install ROM ( nethunter-generic-armhf-kalifs-minimal-rolling-3.15.4-20170202-1604 )
- Reboot
It is when I install the rom that I get the error message "Unpacking boot image failed". Even if at the end it says "install completed - Success", it keep loading (with the nethunter loading screen) indefinitely...
I tried many differents versions of TWRP and even different builds of Nethunter, I found nothing on the net, so what should I do ?
Should I post an issue on the kali-nethunter github ?
Hope you have some ideas of what I can try...
However if you need any other information (log file ...), tell me what.
Aiscargeauh said:
Hi there,
I wanted to install the last image of Nethunter (found on build.nethunter.com/nightly) but when I install it with TWRP (found on build.nethunter.com/twrp) I keep getting the message : "Unpacking boot image failed" in the log screen.
I tried many differents versions of TWRP and even different builds of Nethunter, I found nothing on the net, so what should I do ?
Should I post an issue on the kali-nethunter github ?
Hope you have some ideas of what I can try...
However if you need any other information (log file ...), tell me what.
Click to expand...
Click to collapse
What ROM are you using?
Last time i installed it i was on OOS 3.2.2. You have to flash kernel and then the big file (generic nethunter.....)
Found that in https://forum.xda-developers.com/showpost.php?p=68451978&postcount=6
It worked perfectly but since 3.2.2 i havent touched it again so not sure what rom is compatible atm
fuarkgl3 said:
What ROM are you using?
Click to expand...
Click to collapse
I'm trying with the "nethunter-generic-armhf-kalifs-minimal-rolling-3.15.4-20170202-1604.zip"
Also tried with the full version, instead of minimal but same result.
Aiscargeauh said:
I'm trying with the "nethunter-generic-armhf-kalifs-minimal-rolling-3.15.4-20170202-1604.zip"
Also tried with the full version, instead of minimal but same result.
Click to expand...
Click to collapse
I mean version of OOS, not nethunter overlay. See my screenshot. You have to download one of the following kernels depending if you are on MM or nougat. Flash it before flashing the nethunter overlay
fuarkgl3 said:
I mean version of OOS, not nethunter overlay
Click to expand...
Click to collapse
I'm trying with the latest OTA version, so actually the 4.0.2.
I also installed the kernel before, I'm gonna edit my first post with informations on what I did.
Aiscargeauh said:
I'm trying with the latest OTA version, so actually the 4.0.2.
I also installed the kernel before, I'm gonna edit my first post with informations on what I did.
Click to expand...
Click to collapse
Ok i just read it. And it seems strange indeed. Will try to install it today since i use also oos 4.0.2 and will report back asap
Just out of curiosity what twrp are you using?
fuarkgl3 said:
Ok i just read it. And it seems strange indeed. Will try to install it today since i use also oos 4.0.2 and will report back asap
Just out of curiosity what twrp are you using?
Click to expand...
Click to collapse
Thank's for the support anyway
I'm using the TWRP provided by Nethunter on build.nethunter.com/twrp/oneplus/
Also tried with official 3.0.3 for the OnePlus 3 from twrp.me/devices/oneplusthree.html
Aiscargeauh said:
Thank's for the support anyway
I'm using the TWRP provided by Nethunter on build.nethunter.com/twrp/oneplus/
Also tried with official 3.0.3 for the OnePlus 3 from twrp.me/devices/oneplusthree.html
Click to expand...
Click to collapse
Got it working. Only problem is i dont find the option to enable OTG-USB lol
fuarkgl3 said:
Got it working. Only problem is i dont find the option to enable OTG-USB lol
Click to expand...
Click to collapse
And I'm here sitting with my error and my infinite boot, lol.
Can you please put the installation process you did ? With the files you used ?
I'm getting my phone to full-stock.
Aiscargeauh said:
Can you please put the installation process you did ? With the files you used ?
I'm getting my phone to full-stock.
Click to expand...
Click to collapse
Sure. Just give me time to post what i did, currently restoring my nandroid because something went wrong when updating metapackages, so im going to download full version instead of minimal and enable OGT-USB to check if wifite works. I will post the steps asap :good:
meanwhile..... how the **** do i enable usb-otg? i dont find the option in settings/storage/3dot
Good and bad news: OTG does not work (it worked for me on MM) but nethunter runs "well" ... it stucks while rebooting and some weird things more. It runs laggy as well...
Steps and config i have
-Experience ROM v10.1(oos 4.0.2 with some adds) and custom TWRP by blu_spark v14
1-Download these 2 files from https://build.nethunter.com/nightly/3.15.4-20170202-1604/
-kernel-nethunter-oneplus3-nougat-3.15.4-20170202-1604.zip
-nethunter-generic-arm64-kalifs-full-rolling-3.15.4-20170202-1604.zip
2-Reboot to recovery and install nethunter-generic-arm64.....
3-Not sure if you have to reboot and then install kernel but i flashed nethunter+kernel without rebooting to system
4-Reboot to system and open supersu, then open nethunter app and grant superuser permissions
5-Done.
I Dont really know why my external adapter or pendrive are not recognized, because it did in MM with same hardware lol. Maybe now only works with official usb-c adapter, who knows
I will try this when I can, but it is close to what I already did.
I will edit this post when done.
I seen that you used the arm64 version, perhaps the problem is that I use the armhf ?
Aiscargeauh said:
I will try this when I can, but it is close to what I already did.
I will edit this post when done.
I seen that you used the arm64 version, perhaps the problem is that I use the armhf ?
Click to expand...
Click to collapse
may be, but im not sure. Finally got USB-OTG working but it runs very laggy and dont find any network. So problem is nh build or oos 4.0.2
fuarkgl3 said:
may be, but im not sure. Finally got USB-OTG working but it runs very laggy and dont find any network. So problem is nh build or oos 4.0.2
Click to expand...
Click to collapse
Do you think flashing another ROM before flashing nh-generic will help ?
Aiscargeauh said:
Do you think flashing another ROM before flashing nh-generic will help ?
Click to expand...
Click to collapse
Dont think so. But latest build i installed NH i didnt use arm64 version but armhf. So maybe try what i did but using custom TWRP by blu_spark v14 and armhf.... im not sure
Tested with 2 antennas and result is the same in both (see SS)
Ok, so I've recovered the necessary files from this thread :
https://forum.xda-developers.com/nova-plus/help/lineage-os-t3556105
Thank's to @Grarak and @Xelfmade.
Now I've downloaded the necessary sources from Lineage github and I've successfully build a development environnement
If I succeed in building a rom I will share it with you, be patient and wish me good luck: D
EDIT: I've successfuly builded a rom but I can't flash it :s
-I can flash the recovery.img but when I want to flash lineage.zip in cm recovery it's stuck at "Patching system image unconditionally".
Good luck for sure! Get mine this week in Canada and happy to do any testing as it's not my daily driver.
This thread is kind of unecessary..
Please do not make placeholder threads
I've successfuly builded a rom but I can't flash it :s
I can flash the recovery.img but when I want to flash lineage.zip in cm recovery it's stuck at "Patching system image unconditionally".
If someone have an idea, for the moment I will retest with lineage 14.1
bluesmoothie said:
I've successfuly builded a rom but I can't flash it :s
I can flash the recovery.img but when I want to flash lineage.zip in cm recovery it's stuck at "Patching system image unconditionally".
If someone have an idea, for the moment I will retest with lineage 14.1
Click to expand...
Click to collapse
Can you sent it to me?
Xelfmade said:
Can you sent it to me?
Click to expand...
Click to collapse
Yes I've uploaded it to : https://www.dropbox.com/sh/84smgyxf3uy7vee/AAA8rA_GsxKmph6iU_9o8b5sa?dl=0
bluesmoothie said:
Yes I've uploaded it to : https://www.dropbox.com/sh/84smgyxf3uy7vee/AAA8rA_GsxKmph6iU_9o8b5sa?dl=0
Click to expand...
Click to collapse
I thought it would be a fault by @Grarak..
He chooses "can" as codename for the nova, the official codename instead is hwcan.
TWRP can't deal with this..
Edit: but there are more things not right here..I wonder how he has got a booting build out of it?!
Xelfmade said:
I thought it would be a fault by @Grarak..
He chooses "can" as codename for the nova, the official codename instead is hwcan.
TWRP can't deal with this..
Edit: but there are more things not right here..I wonder how he has got a booting build out of it?!
Click to expand...
Click to collapse
But with the recovery.img compiled with it's not a problem and I can recompile with hwcan if it's the problem.
EDIT: I've tested with cm 14.1 but the build fail
bluesmoothie said:
But with the recovery.img compiled with it's not a problem and I can recompile with hwcan if it's the problem.
EDIT: I've tested with cm 14.1 but the build fail
Click to expand...
Click to collapse
Yeah, I tried to modify the zip for not checking the codename, but it doesn't work..I think it's not working, because his fstab isn't really right, at least the console says that it can't mount any partition..
Xelfmade said:
Yeah, I tried to modify the zip for not checking the codename, but it doesn't work..I think it's not working, because his fstab isn't really right, at least the console says that it can't mount any partition..
Click to expand...
Click to collapse
I think I can add your device repo for recovery
EDIT: I've fused the @Grarak device folder with your device folder, I've modified .mk files in consequence, it's building...
EDIT:Build fail
Sent from my HUAWEI CAN-L11 using XDA-Developers Legacy app
bluesmoothie said:
I think I can add your device repo for recovery
EDIT: I've fused the @Grarak device folder with your device folder, I've modified .mk files in consequence, it's building...
EDIT:Build fail
Click to expand...
Click to collapse
I don't understand what you wanna tell me..
Xelfmade said:
I don't understand what you wanna tell me..
Click to expand...
Click to collapse
Anyway, if you have an idea to make it functionnal i hear you
bluesmoothie said:
Anyway, if you have an idea to make it functionnal i hear you
Click to expand...
Click to collapse
First, let me gain official twrp support for the nova afterwords I'll take the time to make this happening somehow..
Xelfmade said:
First, let me gain official twrp support for the nova afterwords I'll take the time to make this happening somehow..
Click to expand...
Click to collapse
Ok, so I can't do anything ?
And you @Grarak can you help me ? I know the "problem" in the previous thread but you have build a working rom, your help can be precious
bluesmoothie said:
Ok, so I can't do anything ?
And you @Grarak can you help me ? I know the "problem" in the previous thread but you have build a working rom, your help can be precious
Click to expand...
Click to collapse
It's a liitle bit difficult to help, without sitting in front of the monitor where the error message is displayed on..
Btw: Is your nova still encrypted?
Xelfmade said:
It's a liitle bit difficult to help, without sitting in front of the monitor where the error message is displayed on..
Btw: Is your nova still encrypted?
Click to expand...
Click to collapse
Yes, after some researchs I can confirm that :
-In android 6 the device is encrypted by default but when the userdata is formated the device work and the partition rest unencrypted.
-In android 7 the device is encrypted by default and when the userdata is formated the device won't boot, the only solution is to reformat by the official recovery and, after that, the partition remain encrypted.
PS: I'm french, so what mean "btw" ?
EDIT: I've build the rom with cm 13.0 and the files of grarak, used to build his rom, so I don't know why the flash fails.
Can you build a twrp with 'can' for the device name, I think we can test that ?
bluesmoothie said:
Yes, after some researchs I can confirm that :
-In android 6 the device is encrypted by default but when the userdata is formated the device work and the partition rest unencrypted.
-In android 7 the device is encrypted by default and when the userdata is formated the device won't boot, the only solution is to reformat by the official recovery and, after that, the partition remain encrypted.
PS: I'm french, so what mean "btw" ?
EDIT: I've build the rom with cm 13.0 and the files of grarak, used to build his rom, so I don't know why the flash fails.
Can you build a twrp with 'can' for the device name, I think we can test that ?
Click to expand...
Click to collapse
Okay nice to know for a little later..just a little bad, that the encryption doesn't work anymore
Btw means "by the way"
That won't change much, I think..
I don't know what happened with this guy named Garrak, seems like a pretty weird situation... To bad for the Nova and all the community but he surely have his reasons.
I'm not a developer but I truly thank you all to try to build something good for this beautiful device.
As its my main phone, I can't flash anything everyday but if I can help in any ways, I'm here.
Thanks
I've found some other people's with the "Patching system image unconditionally" problem and a solution was to flash via Flashfire app but I have the error "This package is for can....." There is a trick to deactivate this verification ?
EDIT: I have tested to format system partition on f2fs format but not working too.
DisclaimerThis software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [filename].img --> ex: fastboot flash recovery_ramdisk twrp_blanc_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Note: There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9.
Credits
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
Download links Mate 10 Pro (BLA)
twrp_blanc_0.1.img - initial release
twrp_blanc_0.2.img - OEMinfo partition is now available for backup
twrp_blanc_0.3.img - /cache mounting is fixed,backup for vendor_ image (vendor still can't be mounted)
twrp_blanc_0.4.img - /vendor mounting&unmounting is now fixed (thx @ante0 for the script)
twrp_blanc_0.5.img - mounting/unmounting issues shound be fixed , added a new option to exclude OEM path from wiping with Factory Reset and can be enabled/disabled in settings (thx Team OpenKirin for this), this version will work even with newer updates that bump security patch version.
twrp_blanc_0.6.img - wipe cache is now fixed
twrp_bla_alp_0.7.img - fixed decryption on EMUI 8.1 (now you can use the same password/pin/pattern to decrypt in TWRP), /recovery_ramdisk no longer available for backup./vendor no longer available for backup (use /vendor_image instead),/system and /data can be unmounting issue with 8.1 devices is now fixed.
Download links Mate 10 (ALP)
twrp_alp_test_0.1.img - test build,/vendor and /system can't be unmounted but everything else is working
twrp_alp_0.5.img - mounting/unmounting issues shound be fixed , added a new option to exclude OEM path from wiping with Factory Reset and can be enabled/disabled in settings (thx Team OpenKirin for this), this version will work even with newer updates that bump security patch version ,now we have an unified version that work on both ALP and BLA
twrp_alp_0.6.img - wipe cache is now fixed
twrp_bla_alp_0.7.img - fixed decryption on EMUI 8.1 (now you can use the same password/pin/pattern to decrypt in TWRP), /recovery_ramdisk no longer available for backup./vendor no longer available for backup (use /vendor_image instead),/system and /data can be unmounting issue with 8.1 devices is now fixed.
How is this different from the official build?
tristan202 said:
How is this different from the official build?
Click to expand...
Click to collapse
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
tristan202 said:
How is this different from the official build?
Click to expand...
Click to collapse
This one is fully working! [emoji6]It has decryption support, so you can backup, restore your data, mtp support, etc.
Has anyone tested it already? Looking forward to installing it
Στάλθηκε από το BLA-L29 μου χρησιμοποιώντας Tapatalk
mefistofelis said:
Has anyone tested it already? Looking forward to installing it
Στάλθηκε από το BLA-L29 μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
working perfectly great job to the OP
---------- Post added at 10:53 PM ---------- Previous post was at 10:52 PM ----------
@Pretoriano80
perhaps you could do a pull request for official integration?
ngoralph said:
working perfectly great job to the OP
---------- Post added at 10:53 PM ---------- Previous post was at 10:52 PM ----------
@Pretoriano80
perhaps you could do a pull request for official integration?
Click to expand...
Click to collapse
I couldn't manage to make decryption work with the current TWRP base, mostly because of some proprietary binaries. So no source for now.
Can you test if Oeminfo shows in the backup screen?
Pretoriano80 said:
I couldn't manage to make decryption work with the current TWRP base, mostly because of some proprietary binaries. So no source for now.
Can you test if Oeminfo shows in the backup screen?
Click to expand...
Click to collapse
nope it does not appear, and by the way is it normal that it will ask the password every time you boot into twrp?
ngoralph said:
nope it does not appear, and by the way is it normal that it will ask the password every time you boot into twrp?
Click to expand...
Click to collapse
Ok,i will upload a new version so people can backup OEMinfo.Yes,it's normal,that's how it works.
Pretoriano80 said:
Ok,i will upload a new version so people can backup OEMinfo.Yes,it's normal,that's how it works.
Click to expand...
Click to collapse
2nd linked is borked, so you know.
Some extra characters added to it
ante0 said:
2nd linked is borked, so you know.
Some extra characters added to it
Click to expand...
Click to collapse
Fixed,thank!
stuck in teamwin screen
after reboot stuck in teamwin screen. device found under ADB but unable to fastboot. Any advise how to fix? tx
gogoffm said:
after reboot stuck in teamwin screen. device found under ADB but unable to fastboot. Any advise how to fix? tx
Click to expand...
Click to collapse
I had the same!
TWRP stays stuck at the logo. Now I'm trying the official one and that one is booting.
Gonna try some other things and let you know!
Edit: Using a Huawei Mate 10 Pro (Dutch)
gogoffm said:
after reboot stuck in teamwin screen. device found under ADB but unable to fastboot. Any advise how to fix? tx
Click to expand...
Click to collapse
Balthazard said:
I had the same!
TWRP stays stuck at the logo. Now I'm trying the official one and that one is booting.
Gonna try some other things and let you know!
Edit: Using a Huawei Mate 10 Pro (Dutch)
Click to expand...
Click to collapse
Which software version do you guys have? And are you on stock EMUI or some Treble enabled rom?
Pretoriano80 said:
Which software version do you guys have? And are you on stock EMUI or some Treble enabled rom?
Click to expand...
Click to collapse
I have the Unofficial Berkeley Lineage 15.1 OS . I was able to get into fastboot and flashed the official TWRP and it's booting.
gogoffm said:
I have the Unofficial Berkeley Lineage 15.1 OS . I was able to get into fastboot and flashed the official TWRP and it's booting.
Click to expand...
Click to collapse
This version will not work with 8.1 roms,at least not yet.
Wen i enter the password or have to do backup it says error device or resource busy and backup failed. Do i have to do vipe?
grossvs said:
Wen i enter the password or have to do backup it says error device or resource busy and backup failed. Do i have to do vipe?
Click to expand...
Click to collapse
Are you trying a full backup?
Or just /data?
For some reason /vendor doesn't want to mount for me. (Might be because of recovery_vendor? not sure)
First i trying backup data, system and vendor and its failed then data and system and its ok but i have many error - system, device or resource busy and vendor, device or resource busy.
Pretoriano80 said:
This version will not work with 8.1 roms,at least not yet.
Click to expand...
Click to collapse
Yes, just what I thought.
Running RROS from the View 10 forum.
So I switched to the official twrp and all works fine now! Only needed it for Magisk.
I have found this android 10 Rom for which you are uninterested in the probe on my p20 EML L09 and it works correctly
https://www.haky86.com/kirin-gsi/#Android_100
Does it work with L29? What version of the recovery has to be used?
Thanks in advance for your answer?
Screens?
I can confirm the ROM is working pretty fine !
Flashed via fastboot then I flashed TWRP (downloaded the P20 Pro version from the official TWRP website) and sideload Gapps since touchscreen isn't working
Some screenshots
ectoplasma22 said:
I can confirm the ROM is working pretty fine !
Flashed via fastboot then I flashed TWRP (downloaded the P20 Pro version from the official TWRP website) and sideload Gapps since touchscreen isn't working
Click to expand...
Click to collapse
How have you done to load the gapps?
I don't have twrp, how can I do it?
this rom also works https://sourceforge.net/projects/am...tagOS-10.0.1-arm64-ab-vanilla.img.xz/download
mir2480 said:
this rom also works https://sourceforge.net/projects/am...tagOS-10.0.1-arm64-ab-vanilla.img.xz/download
Click to expand...
Click to collapse
Where did you find that one ? Seems interesting ! Any flashing specifications ? Or juste flash system.img ?
---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------
mir2480 said:
How have you done to load the gapps?
I don't have twrp, how can I do it?
Click to expand...
Click to collapse
Get the official TWRP app, choose Berkeley as your device and download latest TWRP 3.3.10 I think
Then flash it via fastboot, reboot into recovery by holding volume down while powering up. Plug back into your PC, adb sideload gapps.zip , you might have to adb shell twrp sideload before
ectoplasma22 said:
I can confirm the ROM is working pretty fine !
Flashed via fastboot then I flashed TWRP (downloaded the P20 Pro version from the official TWRP website) and sideload Gapps since touchscreen isn't working
Click to expand...
Click to collapse
re-size system partition to fix it.
edit:
or get the "KSSI" aex 7.x (Kirin Specific System Image) which gapps is fixed there.
https://www.haky86.com/kssi/emui-pie/
haky 86 said:
re-size system partition to fix it.
edit:
or get the "KSSI" aex 7.x (Kirin Specific System Image) which gapps is fixed there.
https://www.haky86.com/kssi/emui-pie/
Click to expand...
Click to collapse
How can I make twrp work? and also how can I make magisk work on a gsi rom with android 10?
haky 86 said:
re-size system partition to fix it.
edit:
or get the "KSSI" aex 7.x (Kirin Specific System Image) which gapps is fixed there.
https://www.haky86.com/kssi/emui-pie/
Click to expand...
Click to collapse
Do you intend to develop more around the P20 or Kirin ? Would love to try new ROMs and I can still run your AEX as daily routine, battery is not as good as emui9 but close and everything is running fine
ectoplasma22 said:
Do you intend to develop more around the P20 or Kirin ? Would love to try new ROMs and I can still run your AEX as daily routine, battery is not as good as emui9 but close and everything is running fine
Click to expand...
Click to collapse
https://sourceforge.net/projects/am...tagOS-10.0.1-arm64-ab-vanilla.img.xz/download
this rom also works!!!
one despises you lot with your unlocked bootloaders phhhfffff
mir2480 said:
How have you done to load the gapps?
I don't have twrp, how can I do it?
Click to expand...
Click to collapse
This rom also works, the arm64 ab: https://www.pling.com/p/1376076/#files-panel . I installed gapps by rooting with magisk then installing weebgapps module. I havent seen a bug yet in this gsi. Get the vanilla version
jackching said:
This rom also works, the arm64 ab: https://www.pling.com/p/1376076/#files-panel . I installed gapps by rooting with magisk then installing weebgapps module. I havent seen a bug yet in this gsi. Get the vanilla version
Click to expand...
Click to collapse
Did you try the gapps version ? I'm downloading it now from official havoc gsi
ectoplasma22 said:
Did you try the gapps version ? I'm downloading it now from official havoc gsi
Click to expand...
Click to collapse
Ya it wont install. The .img has to be smaller then 2.5 or 2.6 GB in order to install on this phone. Something like that
jackching said:
Ya it wont install. The .img has to be smaller then 2.5 or 2.6 GB in order to install on this phone. Something like that
Click to expand...
Click to collapse
How can I increase the partition size to install larger roms?
mir2480 said:
How can I increase the partition size to install larger roms?
Click to expand...
Click to collapse
wipe, advanced wipe, repair or change file system, resize file system, swipe. Thats if you somehow got twrp working on 9.x...
jackching said:
wipe, advanced wipe, repair or change file system, resize file system, swipe. Thats if you somehow got twrp working on 9.x...
Click to expand...
Click to collapse
Using twrp shell could be possible
Did you install magisk with a patched boot.img ? In this case what did you use ?
New KSSI rom, checkout the new link for change log. have fun
https://www.haky86.it/kssi/emui-9-1/
So I just found a TWRP 3.5.0 file (I don't know who made this) from QQ ydss (China). Yeah I actually doing a leaking this file for you guys so you could have a try if you want to
Download here (GDrive)
Translated from Chinese:
The model structure is the factory (OEM) Android 11's structure. Partition structure is the latest virtual-A/B and doesn't have recovery partition, this is a special point.
Support latest Magisk Root.
This is the first beta build, please use the command "fastboot boot xxxx.img" to start using the recovery.
Support Dynamic Partition Plugins, auto-decrypt is not supported, you need to format Data to access to Data manually.
Sorry for bad English!
P/S: I will not response as your device is bricked, do it at YOUR OWN RISK
Link is working now, I forgot to enable public sharing, sorry guys
now not unlock phone still wait unlock to test
waiting for the 7-day restriction xiaomi bleat lifting
twrp boots up but this IT does not support decryption yet. You can't install anything yet
Chinese K40 users have done twrp3.5. They can swipe the temporary image of twrp into the mobile phone, but they can't decrypt it. I try to format the data and use the computer's ADB push / sacrd/ xx.zip It will prompt that the mobile phone is out of space
And does the version work?
bringchen said:
Chinese K40 users have done twrp3.5. They can swipe the temporary image of twrp into the mobile phone, but they can't decrypt it. I try to format the data and use the computer's ADB push / sacrd/ xx.zip It will prompt that the mobile phone is out of space
Click to expand...
Click to collapse
It just the interface test for sure, and flash is pretty useless right now until there would be a ROM support it
And that's could be a long while that we have to waiting for big-hands devs
CHGICEMAN said:
And does the version work?
Click to expand...
Click to collapse
Of course bruh, how could I put here if it doesn't work??
DumbHokage said:
Of course bruh, how could I put here if it doesn't work??
Click to expand...
Click to collapse
and why is everyone saying that this twrp has no decryption and does not work? who is lying?
any update to this version sir?
Hey, guys, has anyone tried this twrp to read USB devices?
T-HeaD said:
and why is everyone saying that this twrp has no decryption and does not work? who is lying?
Click to expand...
Click to collapse
And don't u read the italic description above???
Hopefully there is an official twrp
This recovery working properly, I got the phone on March 4 and unlocked it on March 13 and used this to flash into magisk.
It can't unlock the data partition, but you can use otg to flash zip.
Alpha Another said:
This recovery working properly, I got the phone on March 4 and unlocked it on March 13 and used this to flash into magisk.
It can't unlock the data partition, but you can use otg to flash zip.
Click to expand...
Click to collapse
Wow how can you get the phone that early, is literally the sametime those reviewers are getting the phone to be tested.
When do we can expect an offical TWRP version?
bl3d2death said:
When do we can expect an offical TWRP version?
Click to expand...
Click to collapse
It probably never will,
they are not even for older models
DeathStroke47 said:
This twrp is ****. It can't flash xiaomi.eu rom from otg.
Click to expand...
Click to collapse
Ure stupid, it's a fastboot option not a flashable rom.
Please applaud me
............delete