{
"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"
}
LG-US997 17A RomHello everyone
LG rolled out a new update to 17A
Changelog from LG:
Code:
[Feature]
- Phone usability and functionality has been further improved
Changelog what I noticed and found:
Code:
*New Security Patch
*Do not have the Phone say it to me an
i will edit it :p
This zip is created from the original KDZ. I changed the Boot.img, so you do not have to reinstall TWRP. . .
I had made this for users who can not get ota's because they have Custom Recovery / Root installed
Sorry for my bad english i'm out of practice Features *Stock build made from official KDZ
*Stock Build.prop
*Unrooted
*Boot.img modified to keep TWRP
*Remove dm-verity
*Remove forceencryptInstallation What you need *Unlocked Bootloader [How to do]
*Working TWRP installed [Link to unofficial TWRP]
*When you need Root, Latest SuperSU [Download] or Magisk [Download]
*US997 17A (TWRP).zip [Download]
How to install Reboot to recovery using button combo or reboot app (need root)
Backup Dalvik,ART, Cache, System & Data (include not your internal memory) and Boot
in to your external sd or copy the backup from internal sd to your PC!
For clean install: Wipe Dalvik/ART, Cache, System and Data (Recommend)
You can also keep your data by dirty flashing the zip.
Flash US997 17A (TWRP).zip
Flash SuperSU or Magisk zip when you need root
Reboot System
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no
Here you can find my other [Downloads.] There are IMG´s, KDZ´s and more!
Rom Version
Android Version: 7.0
Android security patch level: 2018-01-01
Build date: 2018-01-04
Build number: NRD90U
Product model: LGUS997
MD5 SUMS:
Code:
[SIZE="4"][B][COLOR="Black"]
boot.img 707beea1c5015fadaee2254707bfc6ae
modem.img 0d5d7c7188fa162e70a77d0f3f5dd6e4
persist.img 63c5ba281159f22b0fd20979fb197190
rct.img 15bc82584049ec3a7c62d921c2897267
system.img e8bd34896b5b634b637346ad6bb9d085
aboot.img f0939946543a9742f34c5ddd60fcbf66
apdp.img 4055e51f849f725c60c869ebc7a1479f
cmnlib.img ac9bffdbb1ecda4f804e5382598c091a
cmnlib64.img 82595b03cb24ba81a404550e047bcca5
devcfg.img ff779136ffd03f3769a515da23b114b6
factory.img 15bc82584049ec3a7c62d921c2897267
hyp.img b3f4dbe64fe64f739f55cded4936c9e3
keymaster.img a9424b1b15d6e9b959d3817ab5faf8b7
laf.img 5847de1fcfaf15595ef9ad6ea0253f9b
msadp.img 5038a3e079a0c0d13fb2df601af6e7fc
pmic.img 4bf032502d8633bb892dbc58c63e031a
raw_resources.img 579715447bb6fab9ec91403542eb6c80
rpm.img fe6f10c14bf27ea539503e29191deb1b
sec.img 628756d1475c7e6ffa2f974c63261bf6
tz.img 2ad066a14c7c83f01cee651aa0b24bd9
xbl.img d811c2afd65698ab62615fd7b9971b0c[/COLOR][/B][/SIZE]
Credits:
@autoprime
@nima0003
@Chainfire
@topjohnwu
@Me :laugh:
Don´t forget to hit the thanks-button if you like my work! :good:
You want to help me with a [donation?] Feel free to make it.
Confirmed working!
A few roadbumps, though. I came from the TWRP build that @nima0003 and @zefie compiled. I flashed the ROM after wiping Dalvik/ART, Cache, System and Data but once I rebooted, I was back in TWRP! This happened over and over again, even after a format and full restore of a good backup. After several failed attempts to get into Download Mode to flash the stock KDZ (button combo just wouldn't work) I decided to just go into fastboot and use 'fastboot flash recovery x.img' on the TWRP recovery image(older version) I used to initially get custom recovery, after that I was able to flash the ROM and get into Android.
It may be an issue with the boot.img having TWRP preloaded, but I'm not sure if I somehow overwrote something. Hopefully this helps someone!
Friendly reminder to quadruple backup, Titanium Backup and LG Backup & Restore made it a whole lot less of a hassle than it could've been.
Any particularly noticeable changes with this update? I'm asking because I got it over OTA, and I wanna know whether or not it's worth updating. How's battery life, performance? It's a 771MB update, if I'm not mistaken, which is not a small package. Any changes in the interface?
duff105 said:
Any particularly noticeable changes with this update? I'm asking because I got it over OTA, and I wanna know whether or not it's worth updating. How's battery life, performance? It's a 771MB update, if I'm not mistaken, which is not a small package. Any changes in the interface?
Click to expand...
Click to collapse
People have been complaining about lag from the OTA update on forums, but I myself have not noticed any changes. I may be glossing over it and assuming that it's standard Android lag. I updated mostly for the latest security patch and the OTA update notification was bothering me. If anyone who has better sensitivity to lag can test it, that would be appreciated.
So I updated 2 days ago or so, and it's just like you've said. No changes, and no unusual lags. Which is great, I guess, means they havent forgotten about G6 users.
westwood24 said:
LG-US997 17A RomHello everyone
LG rolled out a new update to 17A
Changelog from LG:
Code:
[Feature]
- Phone usability and functionality has been further improved
Changelog what I noticed and found:
Code:
*New Security Patch
*Do not have the Phone say it to me an
i will edit it :p
This zip is created from the original KDZ. I changed the Boot.img, so you do not have to reinstall TWRP. . .
I had made this for users who can not get ota's because they have Custom Recovery / Root installed
Sorry for my bad english i'm out of practice Features *Stock build made from official KDZ
*Stock Build.prop
*Unrooted
*Boot.img modified to keep TWRP
*Remove dm-verity
*Remove forceencryptInstallation What you need *Unlocked Bootloader [How to do]
*Working TWRP installed [Link to unofficial TWRP]
*When you need Root, Latest SuperSU [Download] or Magisk [Download]
*US997 17A (TWRP).zip [Download]
How to install Reboot to recovery using button combo or reboot app (need root)
Backup Dalvik,ART, Cache, System & Data (include not your internal memory) and Boot
in to your external sd or copy the backup from internal sd to your PC!
For clean install: Wipe Dalvik/ART, Cache, System and Data (Recommend)
You can also keep your data by dirty flashing the zip.
Flash US997 17A (TWRP).zip
Flash SuperSU or Magisk zip when you need root
Reboot System
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no
Here you can find my other [Downloads.] There are IMG´s, KDZ´s and more!
Rom Version
Android Version: 7.0
Android security patch level: 2018-01-01
Build date: 2018-01-04
Build number: NRD90U
Product model: LGUS997
MD5 SUMS:
Code:
[SIZE="4"][B][COLOR="Black"]
boot.img 707beea1c5015fadaee2254707bfc6ae
modem.img 0d5d7c7188fa162e70a77d0f3f5dd6e4
persist.img 63c5ba281159f22b0fd20979fb197190
rct.img 15bc82584049ec3a7c62d921c2897267
system.img e8bd34896b5b634b637346ad6bb9d085
aboot.img f0939946543a9742f34c5ddd60fcbf66
apdp.img 4055e51f849f725c60c869ebc7a1479f
cmnlib.img ac9bffdbb1ecda4f804e5382598c091a
cmnlib64.img 82595b03cb24ba81a404550e047bcca5
devcfg.img ff779136ffd03f3769a515da23b114b6
factory.img 15bc82584049ec3a7c62d921c2897267
hyp.img b3f4dbe64fe64f739f55cded4936c9e3
keymaster.img a9424b1b15d6e9b959d3817ab5faf8b7
laf.img 5847de1fcfaf15595ef9ad6ea0253f9b
msadp.img 5038a3e079a0c0d13fb2df601af6e7fc
pmic.img 4bf032502d8633bb892dbc58c63e031a
raw_resources.img 579715447bb6fab9ec91403542eb6c80
rpm.img fe6f10c14bf27ea539503e29191deb1b
sec.img 628756d1475c7e6ffa2f974c63261bf6
tz.img 2ad066a14c7c83f01cee651aa0b24bd9
xbl.img d811c2afd65698ab62615fd7b9971b0c[/COLOR][/B][/SIZE]
Credits:
@autoprime
@nima0003
@Chainfire
@topjohnwu
@Me :laugh:
Don´t forget to hit the thanks-button if you like my work! :good:
You want to help me with a [donation?] Feel free to make it.
Click to expand...
Click to collapse
Hello! My name is Tuan living in Vietnam. I can describe some money to buy the LG G6 US997. I followed the instructions on XDA to unlock the Bootloader successfully. Now I want to install TWRP Recovery to run Fulmics 3.5 rom. But difficult to try to try. Please give me a guide that can actually install TWRP Recovery. Thank you very much.
Awesome! Thanks! How do I put xposed on it without getting into a bootloop?
DAXX said:
Awesome! Thanks! How do I put xposed on it without getting into a bootloop?
Click to expand...
Click to collapse
There is a post here by rovo89 somewhere about the bootloop. You have to literally have wait for 15-20 minutes while it's trying to boot up. I've done it myself, and seems like it won't boot up but it will. Just make sure your battery is full when doing it.
Sent from my LG G6 using XDA Labs
jurington said:
There is a post here by rovo89 somewhere about the bootloop. You have to literally have wait for 15-20 minutes while it's trying to boot up. I've done it myself, and seems like it won't boot up but it will. Just make sure your battery is full when doing it.
Click to expand...
Click to collapse
I did that and it worked like a charm! It was very confusing at first. Sucks that you have to wait though. Thanks for your reply!
DAXX said:
I did that and it worked like a charm! It was very confusing at first. Sucks that you have to wait though. Thanks for your reply!
Click to expand...
Click to collapse
Awesome!! Yeah I tried about 4 or 5 times thinking it was in a infinite bootloop until I found out you had to wait a long time. Cheers man
Sent from my LG G6 using XDA Labs
Nice job...just dumped a custom Rom and flashed this, then installed SU...simple and smooth, Thanks!!
Thanks, do you know where I can find the stock boot.img? Or the entire KDZ without it modified?
cory733 said:
Thanks, do you know where I can find the stock boot.img? Or the entire KDZ without it modified?
Click to expand...
Click to collapse
I can't find a hosted 17A stock boot.img, the most recent I can find is the 15A hosted on @westwood24 's AndroidFileHost here. As for the KDZ the only one I can find is the 16A hosted by @zefie here.
Just installed , rooted , and xposed.
Very nice !!! I like !!!
eridnis said:
I can't find a hosted 17A stock boot.img, the most recent I can find is the 15A hosted on @westwood24 's AndroidFileHost here. As for the KDZ the only one I can find is the 16A hosted by @zefie here.
Click to expand...
Click to collapse
In case anyone is looking, this is where I found the stock firmware that I used
https://lg-firmwares.com/lg-us997-firmwares/
Anyone else having trouble downloading this file? The download hangs at 81 % for me and I have tried multiple times.
Can anyone confirm dirty flash of this update working? I'm currently at 12a if that matters.
eridnis said:
I can't find a hosted 17A stock boot.img, the most recent I can find is the 15A hosted on @westwood24 's AndroidFileHost here. As for the KDZ the only one I can find is the 16A hosted by @zefie here.
Click to expand...
Click to collapse
The strange part is, if you flash the 16a KDZ, then do a update request either on the phone or with LG Bridge, it will report there is no newer version. So I am not sure what happened to 17a, maybe LG revoked it?
Aw, crud!
I spent all day setting this up and advanced calling does not work for US997 and Verizon???
ADVANCED CALLING is greyed out in main settings menu and the test menu eventually comes up, but when PHONE is selected, an error message states that function is not available on this device.
Is there a way to fastboot flash just the modems, like I could on a Motorola?
If not, do I flash official firmware from LG with LGUP or fastboot?
Related
{
"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"
}
LG-H870 OPEN EU 10L ROMHello everyone
This is my first work in things like Android.
I am just about to learn how to develop and port for Android.
This zip is created from the original KDZ. I changed the Boot.img, so you do not have to reinstall TWRP.
Later I will create other zips without modifications so you can flash
the ROM without TWRP/Root to be absolutely stock and one with Aroma installer or something,
so that you can choose between Supersu and Magisk.
Next I will build a stock Custom ROM with some tweaks and mods. :good:
If I have done this I will try to develop a fully Custom ROM with various ports and/or
mods made by me if I can do it :fingers-crossed:. I would also like to try to port LineageOS for our sexy device.
Sorry for my bad english i'm out of practice
Features *Stock build made from official KDZ
*Stock Build.prop
*Unrooted
*Boot.img modified to keep TWRP
*Remove dm-verity
*Remove forceencryptInstallation What you need *Unlocked Bootloader [How to do]
*Working TWRP installed [Link to official TWRP]
*When you need Root, Latest SuperSU [Download] or Magisk [Download]
*H870 10L OPEN EU (TWRP).zip [Download]
How to install Reboot to recovery using button combo or reboot app (need root)
Backup Dalvik,ART, Cache, System & Data (include not your internal memory) and Boot
in to your external sd or copy the backup from internal sd to your PC!
For clean install: Wipe Dalvik/ART, Cache, System and Data (Recommend)
You can also keep your data by dirty flashing the zip.
Flash H870 10L OPEN EU (TWRP).zip
Flash SuperSU or Magisk zip when you need root
Reboot System
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no
Rom Version
Android Version: 7.0
Android security patch level: June 1, 2017
Build date: June 22, 2017
Build number: NRD90U
MD5 SUMS:
Code:
[SIZE="4"][B][COLOR="Black"]
boot.img 92335edb10b951f221da1aab0b1ad2c3
modem.img c095697d700c0b08408142f44a9f7cdf
OP_OPEN_EU.img 2519a561fb581fae313183ef2c8b5c64
persist.img 5715f5a60eba5a41b4906d8ba6bbcfad
rct.img 15bc82584049ec3a7c62d921c2897267
system.img f21c639430b366d4e8c7b9a0ff93efc7
aboot.img 601548da68fdfa7a02d8db4a6e90d5db
apdp.img 23ca67412df6c59c2cbe5d98e45037c1
cmnlib.img 7eda51ce363f36baa39b5e886426ec8f
cmnlib64.img 7007c9dd3da6a45f0466688c3ca5126c
devcfg.img 63f2a9180a51e1788610c4e18de4ea78
factory.img 15bc82584049ec3a7c62d921c2897267
hyp.img 11a14e0b9e07f6c96b4f018b53cb33b6
keymaster.img 7efa6121ca4abe49b897f7fd3ccc2d66
laf.img 9199b8cc446f8fce5fb98a0904977084
msadp.img 0dada3ac5e1fdbcf337cbb3c8e27d5e5
pmic.img 6625757b0a85af9dbd1965a01885bc5d
raw_resources.img f9aa74c82c39fdd96220406c03419713
rpm.img 75016588a3eab3509f3310b2f2f54dba
sec.img 628756d1475c7e6ffa2f974c63261bf6
tz.img 950dfdba97fd496bb0ae4e97b5163bd3
xbl.img 0422d1b7f47ff5bfcc1da94cec11e14e[/COLOR][/B][/SIZE]
Credits:
@autoprime
@J0SH1X's
@Chainfire
@topjohnwu
@Me :laugh:
Don´t forget to hit the thanks-button if you like my work! :good:
You want to help me with a [donation?] Feel free to make it.
Awsome mate! Continue this good work!
I will keep that in mind. Thank you
westwood24 said:
LG-H870 OPEN EU 10L Rom Hello everyone
This is my first work in things like android.
I am just about to learn how to develop and port for android.
This zip is from the original KDZ. I have changed the boot.img so that you do not have to reinstall TWRP. Later I will still create zip's without modification and with an aroma installer so you can choose between supersu and magisk.
Next I will build a stock rom with tweaks and mods
If I have done this I will try to develop a costum rom or port lineageOS to our device.Features *Stock build made from official KDZ
*Stock Build.prop
*Unrooted
*Boot.img modified to keep TWRP
*Remove dm-verity
*Remove forceencryptInstallation What you need *Unlocked Bootloader [How to do]
*Working TWRP installed [Link to official TWRP]
*When you need Root, Latest SuperSU Download or Magisk of your choice V12 stable # V13 beta
*H870 10L OPEN EU (TWRP).zip [Download]
How to install Reboot to recovery using button combo or reboot app
Backup Dalvik,ART, Cache, System & Data (include not your internal memory) and Boot
Fullwipe (Dalvik,ART, Cache, System & Data)
Flash H870 10L OPEN EU (TWRP).zip
Flash SuperSU or Magisk zip when you need root
Reboot System
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it. If TWRP asks if you want to install SU, hit no it
Rom Version
Android Version: 7.0
Android security patch level: June 1, 2017
Build date: June 22, 2017
Build number: NRD90U
MD5 SUMS:
boot.img 92335edb10b951f221da1aab0b1ad2c3
modem.img c095697d700c0b08408142f44a9f7cdf
OP_OPEN_EU.img 2519a561fb581fae313183ef2c8b5c64
persist.img 5715f5a60eba5a41b4906d8ba6bbcfad
rct.img 15bc82584049ec3a7c62d921c2897267
system.img f21c639430b366d4e8c7b9a0ff93efc7
aboot.img 601548da68fdfa7a02d8db4a6e90d5db
apdp.img 23ca67412df6c59c2cbe5d98e45037c1
cmnlib.img 7eda51ce363f36baa39b5e886426ec8f
cmnlib64.img 7007c9dd3da6a45f0466688c3ca5126c
devcfg.img 63f2a9180a51e1788610c4e18de4ea78
factory.img 15bc82584049ec3a7c62d921c2897267
hyp.img 11a14e0b9e07f6c96b4f018b53cb33b6
keymaster.img 7efa6121ca4abe49b897f7fd3ccc2d66
laf.img 9199b8cc446f8fce5fb98a0904977084
msadp.img 0dada3ac5e1fdbcf337cbb3c8e27d5e5
pmic.img 6625757b0a85af9dbd1965a01885bc5d
raw_resources.img f9aa74c82c39fdd96220406c03419713
rpm.img 75016588a3eab3509f3310b2f2f54dba
sec.img 628756d1475c7e6ffa2f974c63261bf6
tz.img 950dfdba97fd496bb0ae4e97b5163bd3
xbl.img 0422d1b7f47ff5bfcc1da94cec11e14e
Credits:
@autoprime
@J0SH1X's
@Chainfire
@topjohnwu
Click to expand...
Click to collapse
actually su is excluded from twrp because NO LOVE FOR THE WICKED
J0SH1X said:
actually su is excluded from twrp because NO LOVE FOR THE WICKED
Click to expand...
Click to collapse
But the people who use a different recovery, could get the message (If TWRP asks if you want to install SU, hit no).
Hi,
thank you for you work!
So, is it confirmed that you can dirty flash over 10f without need to wipe?
Thanks
Sure I've tried it, you should still make a backup if something goes wrong
westwood24 said:
But the people who use a different recovery, could get the message (If TWRP asks if you want to install SU, hit no).
Click to expand...
Click to collapse
I already run official twrp with SuperSU 2.82 with issue on 10f firmware, can I just flash 10l with only cache/dalvik wipe?
jimbomodder said:
I already run official twrp with SuperSU 2.82 with issue on 10f firmware, can I just flash 10l with only cache/dalvik wipe?
Click to expand...
Click to collapse
You mean the Supersu remains? I have not tested now. If you mean that, and SuperSU is not installed, then reboot recovery and flash newest SuperSU.zip
@westwood24 thanks for this, I simply flashed in recovery, then reflashed SuperSU as I had before and now my G6 is up to date. ??
Sent from my Nexus 6 using XDA-Developers Legacy app
Xposed
Hello !
I know it's too early yet, but, it would be really cool to have a stock based rom, xposed and 3minit battery compatible. :good::good::good:
sorry for my English
3minit should work, I'll check it, but xposed-framework is unfortunately not compatible yet
Everything works perfect here ? i would apreciate the 3minit support , thnx for the good work
Sent from my LG-H870 using XDA-Developers Legacy app
Thank you very much. I really appreciate the great work.
And dirty flash works too, I can confirm that.
Samsung Gear App does not work (not compatible) and if you install the apk manually, it does not connect to the Gear S3 (simply does not recognize it). BT is working fine and does "see" the Gear S3.
Maybe related to "root".
dragon-tmd said:
Samsung Gear App does not work (not compatible) and if you install the apk manually, it does not connect to the Gear S3 (simply does not recognize it). BT is working fine and does "see" the Gear S3.
Maybe related to "root".
Click to expand...
Click to collapse
How did you flash the zip?
This zip is absolutly stock.
i have test gear app from store
and it installs it and works for me.
root with magisk!
Edit: my g-watch working also and connected
westwood24 said:
How did you flash the zip?
This zip is absolutly stock.
i have test gear app from store
and it installs it and works for me.
root with magisk
Click to expand...
Click to collapse
I'm still thinking about whether I'm rooting. The main reason is the often described incompatibility with Magisk. As I see it works with you. Does Magisk hide also work with banking apps?
pittrich67 said:
I'm still thinking about whether I'm rooting. The main reason is the often described incompatibility with Magisk. As I see it works with you. Does Magisk hide also work with banking apps?
Click to expand...
Click to collapse
of course. you must enable magisk hide and
then choose in magisk hide the app you need.
westwood24 said:
of course. you must enable magisk hide and
then choose in magisk hide the app you need.
Click to expand...
Click to collapse
Have there problems with TWRP. One always reads from mount errors. Also the fact that the bootloader can no longer be closed makes me hesitate. Until now, I've always bought Nexus devices. There was never problem with closing the BL before I got it Had sold.
TWRP works well if you do the tutorial correct. The bootloader is currently not able to close, but is only a question of timei think
{
"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"
}
All seems to be working except Encryption.
So that means you have to erase usedata!
If you don't know how to return back to a working state if something is broken, please think twice before flashing this.
Please do read the installation guide note !
IMPORTANT NOTE :
Warning: Make sure you make a backup of all your important data manually before flashing anything, making any backups or restoring.
I'm not responsible for any data loss, bricks, or whatever went wrong on your device. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
If you plan on using this on stock and have no root you wont be able to see any files due to encryption. To fix this FORMAT not wipe userdata then either flash supersu and not pass safety net or flash one of my roms(New one incoming)
Working
Everything except what's not working, see below
Not working / issues
Encryption
Logs
To get logs: Advanced ---> Copy log
Installation Guide :
1. Download all files below on pc.
2. BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
2.5 BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
3. Boot your phone to fastboot mode.
3.a If you already have twrp disregard the next 2 lines
4. Flash the twrp from below. Using the command "fastboot flash boot /path/to/twrp.img
5. Boot to recovery through the fastboot menu.
6. Go to wipe---Format data(FOR UNENCRYPTION)
6.a IF ALREADY UNENCRYPTED JUST MAKE SURE YOU REFLASH YOUR ROOT OPTION
7. When it says type in yes do it.
8. Wait to finish then plug phone into pc.
9. Transfer supersu to your phone.
9.a Transfer magisk if you use it
10. go to install and find the supersu/magisk zip you just pulled over.
11. Flash it and reboot.
12. Profit!
12.25 Go through the setup process to get to settings. Go to security and check it your phone says encrypt. If it does your good.
IF WANTING UNENCRYPTION ON STOCK YOU HAVE TO FLASH SUPERSU AS MAGISK DOESNT FULLY UNENCRYPT THINGS YET IF ON A ROM LIKE MINE FLASH WHAT EVER LOL
Update Guide:
1. Download new twrp
2. Boot to twrp
3. click on downloaded twrp
4. flash
5. REFLASH WHATEVER ROOT YOU HAD SUPERSU OR WHATEVER OR ELSE YOU WILL BOOT LOOP!
Download Links :
Newest TWRP FLASHABLE PLEASE TAKE A LOOK AT NUMBER 5 ABOVE
FASTBOOT FLASHABLE TWRP 3.2.0.0
Newest SuperSu
Newest Magisk
CHANGELOG:
V3.2
UPGRADED TO LATEST 3.2.0.0
ADDED LATEST UPSTREAM FROM @Uzephi
V3.1
FIXED BOOTLOOP
NEWEST KERNEL AT THIS TIME OF WRITING
V3
Ability to flash bootlogos!
Ability to backup and restore bootlogos
Ability to Backup,Restore and wipe OEM partition.
Ability to flash magisk(must be stock with oem partition in tact to PASS if your ok with cts profile mismatch then modify all you want)(Our phones use the new AVB Verity DM Verity 2.0 pretty much lol)
Bug Fixes and other stuff im forgeting.
Twrp is now flashable! just download the zip in the current twrp and flash!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:JBATS
Source:JOEMOSSJR
Kernel Source:JOEMOSSJR
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-11-10
Nice
Sent from my SM-N930F using XDA-Developers Legacy app
Woow, very nice present GREAT JOB!!!
Great job man. The people in our group can't thank you or your people enough. We appreciate all the hard work you guys did to get this working for us. Thank you again!
In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.
Uzephi said:
In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.
Click to expand...
Click to collapse
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.
jbats said:
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.
Click to expand...
Click to collapse
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.
Uzephi said:
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.
Click to expand...
Click to collapse
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:
jbats said:
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:
Click to expand...
Click to collapse
My kernel source can be built after a clone with any Linux install. I was actually going to upstream it this weekend, so no kernel work was needed besides the upstream.
joemossjr said:
All seems to be working except Encryption.
So that means you have to erase usedata!
Please do read the installation guide note !
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
Installation Guide :
Make sure you have unlocked bootloader
Backup all the data because it will be formatted
Reboot to bootloader
Use the command fastboot erase userdata
fastboot flash boot TWRP3.1.1.0nash.img (if you want permanent flash) or fastboot boot TWRP3.1.1.0nash.img (if you want temporary boot)
Then use @Chainfire cfar we have and run it normally (if you need instructions there here)
Once this does its thing you will have root and twrp!
boot to system and go through the setup process and make it to settings ----> security and see if you see encrypt.
If you do that means your good! You can now reboot to recovery and do what you want!
Download Links :
TWRP 3.1.1-0
CFAR
Bugs: Right now if you flash magisk it wont boot up due to the kernel not being decryptable still working on it atm!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:https://github.com/jbats/android_device_motorola_nash-twrp
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-10-11
Click to expand...
Click to collapse
(instructions were not clear I got my **** stuck in the toaster) jk but could I still do it if I didn't use cfar and got SuperSU a alternate way or will it not affect it
Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good
joemossjr said:
Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good
Click to expand...
Click to collapse
Another question would I be able to flash this with flashfire my computer isn't booting up and if yes what would I select? (And yes I'm very new to all this I only started last year with all this Android modifications)
How are you rooted
joemossjr said:
How are you rooted
Click to expand...
Click to collapse
I'm on the stock boot image with SuperSU installed just a normal root no Xposed and no magisk either although I had magisk originally
( I used a friend's computer when I went to visit him if that's what you meant)
thread updated if any questions please pm me
Thanks ..getting device tomorrow ....
Sent from my Nexus 6 using Tapatalk
kenbrownstone said:
Thanks ..getting device tomorrow ....
Click to expand...
Click to collapse
No problem!
Is this all I need to do to get root and twrp?/seems simple or to simple to be honest.I know nothing about how to root/ROM a motoz..Had a z droid but was verizion..Got a tmo zforce2 coming ..
Sent from my Nexus 6 using Tapatalk
Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?
Amd4life said:
Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?
Click to expand...
Click to collapse
your files are all jumbled because you didnt format data. xposed wont write right for some reason idk about the sound mod tho. Im about to update twrp here shortly
{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're 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.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.3.1
PitchBlack version: 2.9.0
For device: onclite
Maintainer/Authors build: Ashu Sharma
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/PitchBlackRecoveryProject/android-device-xiaomi-onclite-pbrp
PitchBlack Team: @rezaadi0105, @firewolfxda, @manjot.gni, @androiabledroid, Arbaz Khan
Features
Supports Treble and non-Treble ROMs
Up-to-date Oreo kernel, built from sources (Pie is on the way)
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From Fastboot
Extract the Downoaded zip file
Grab the recovery.img from extracted folder
Reboot device in fastboot
Run "fastboot flash recovery recovery.img" from fastboot
Boot into recovery
Changelog
Code:
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Downloads
Flashable zip
PitchBlack-onclite-2.9.0-20190624-0606-OFFICIAL
Post Installation Instructions
BACKUP YOUR Boot.img BEFORE DOING THIS
To decrypt data:
1. Backup Boot.img
2. Wipe data and flash patched boot.img by magisk or Magisk zip file (You Can Patch boot.img through magisk app)
3. Reboot
Hit Thanks Button If I Helped You:good:
:laugh::laugh::laugh:
Nice thread, kindly explain the process of patching the the boot.IMG
And will I be able to use OTA from notification using this recovery even after I've flashed magisk?
Thanks for your anticipated response
Stephinnoye said:
Nice thread, kindly explain the process of patching the the boot.IMG
And will I be able to use OTA from notification using this recovery even after I've flashed magisk?
Thanks for your anticipated response
Click to expand...
Click to collapse
To patch boot.img
1. Open magisk
2. Click in install and select patch image
3. Find your boot.img
4. Done
5. Boot into recovery, wipe data and flash patched image
To apply OTA:
https://c.mi.com/thread-1782169-1-1.html
ashu7073 said:
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.3.1
PitchBlack version: 2.9.0
For device: onclite
Maintainer/Authors build:Ashu Sharma
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
......
..... . .
... . . .
Post Installation Instructions
BACKUP YOUR Boot.img BEFORE DOING THIS
To decrypt data:
1. Backup Boot.img
2. Wipe data and flash patched boot.img by magisk or Magisk zip file (You Can Patch boot.img through magisk app)
3. Reboot
Click to expand...
Click to collapse
After installing RECOVERY via fastboot, Is it necessary to backup boot image ?
There is no decrypt. Zip to flash after recovery coz i don't want to use magisk to decrypt data ?
[email protected] said:
After installing RECOVERY via fastboot, Is it necessary to backup boot image ?
There is no decrypt. Zip to flash after recovery coz i don't want to use magisk to decrypt data ?
Click to expand...
Click to collapse
Decrypt.zip is included in PitchBlack zip file. You've to flash again zip from any recovery or From Pitchblack to Get decrypt zip and other files which included in PitchBlack recovery zip file
Or you can use this : https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
It is Not Necessary to Backup boot.img after Flashing recovery But it is Recommended to Backup boot.img Before Flashing ForceDecrypt zip, patched boot image or Magisk.
In Case your Device got Stuck in Bootloop after flashing decrypt zip, You can Restore Boot.img.
ashu7073 said:
To patch boot.img
1. Open magisk
2. Click in install and select patch image
3. Find your boot.img
4. Done
5. Boot into recovery, wipe data and flash patched image
To apply OTA:
https://c.mi.com/thread-1782169-1-1.html
Click to expand...
Click to collapse
Thanks bro
But must u patch the boot.IMG? Wats the need for doing that?
All I want is root (using magisk) and a custom recovery
Thanks
---------- Post added at 15:38 ---------- Previous post was at 15:36 ----------
ashu7073 said:
Decrypt.zip is included in PitchBlack zip file. You've to flash again zip from any recovery or From Pitchblack to Get decrypt zip and other files which included in PitchBlack recovery zip file
Or you can use this : https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
It is Not Necessary to Backup boot.img after Flashing recovery But it is Recommended to Backup boot.img Before Flashing ForceDecrypt zip, patched boot image or Magisk.
In Case your Device got Stuck in Bootloop after flashing decrypt zip, You can Restore Boot.img.
Click to expand...
Click to collapse
What is d essence of this decrypt zip of a thing?
Stephinnoye said:
Thanks bro
But must u patch the boot.IMG? Wats the need for doing that?
All I want is root (using magisk) and a custom recovery
Thanks
Click to expand...
Click to collapse
It's optional and alternative to direct magisk zip
It's upto you. Flash magisk or patched image
ashu7073 said:
It's optional and alternative to direct magisk zip
It's upto you. Flash magisk or patched image
Click to expand...
Click to collapse
So once uve this pitch recovery, and I flashed magisk, I'm gud to go?
Thanks
Please help bro
I've pitchblack recovery now,but whenever I boot to recovery,it keep asking me to decrypt data .
I've tried to backup my boot.img but to no avail
Also, whenever I flashed anything,I get this response "unable to mount storage" and recovery can't read my internal storage
Kindly help pls
Thanks in anticipation
Stephinnoye said:
Please help bro
I've pitchblack recovery now,but whenever I boot to recovery,it keep asking me to decrypt data .
I've tried to backup my boot.img but to no avail
Also, whenever I flashed anything,I get this response "unable to mount storage" and recovery can't read my internal storage
Kindly help pls
Thanks in anticipation
Click to expand...
Click to collapse
This is problem in PitchBlack recovery. It can't decrypt data. I'm working on a fix. Untill then you can wipe data in pitchblack once to decrypt it.
Or go back to another recovery
ashu7073 said:
This is problem in PitchBlack recovery. It can't decrypt data. I'm working on a fix. Untill then you can wipe data in pitchblack once to decrypt it.
Or go back to another recovery
Click to expand...
Click to collapse
I've wiped data, but whenever I go-to recovery,it will still ask me to decrypt
And what abt the inability of the recovery to read my internal storage?
I opted in for pitchblack so that I can use OTA (tho I still don't get the procedures to enable me use OTA,but I'm sure u will still put me tru personally,that site seems complicated)
Stephinnoye said:
I've wiped data, but whenever I go-to recovery,it will still ask me to decrypt
And what abt the inability of the recovery to read my internal storage?
Click to expand...
Click to collapse
You've to flash magisk to disable force encryption
Or just flash your stock boot.img, pitchblack automatically disables force encryption
ashu7073 said:
You've to flash magisk to disable force encryption
Or just flash your stock boot.img, pitchblack automatically disables force encryption
Click to expand...
Click to collapse
I've flashed magisk, lemme see if the recovery can read my internal storage now
Modified: still can't read my internal storage
Stephinnoye said:
I've flashed magisk, lemme see if the recovery can read my internal storage now
Modified: still can't read my internal storage
Click to expand...
Click to collapse
Flashing magisk is not going to help with decrypting data. Either your recovery can decrypt, or it can't. If it can't, and you want to remain encrypted, then you will need another recovery which can decrypt. If you don't mind not being encrypted, then you can format your data ("format", not "wipe"). That will obliterate all the contents of your internal storage - so you had better backup all your photos, videos, etc, before formatting data.
For me works the recovery...but pc doesn't recognize device then...
Work in redmi 7 Global EEA
So whats up with this recovery is it usable or not? Can encryption be removed with formatting data? And also does miui ota survival work? I would like to use this recovery with xiaomi eu rom
Immortal0907 said:
So whats up with this recovery is it usable or not? Can encryption be removed with formatting data? And also does miui ota survival work? I would like to use this recovery with xiaomi eu rom
Click to expand...
Click to collapse
Yes, you can
Wipe data and flash any encryption disabler zip
Or patch boot.img with magisk and flash with PB recovery
Pb disables dm-verity so it may cause boot loop on miui. you've disable dm-verity disabler
ashu7073
How Disable Dm-verify method here, automatically or from where?!.
Don`t use this recovery if you are flashing xiaomi.eu rom fingerprint / Pin won`t work no matter what you do use LR Team TWRP.
{
"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"
}
Notes:
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for metadata encryption (which causes mounting errors in log)
Downloads:
twrp_3.7.0_12-2_X200XXS1CWA3.tar.md5
twrp_3.7.0_12-2_X200XXS1CWA3.img
Change Log:
v3.7.0_12-2 (2023-02-28):
Updated to X200XXS1CWA3 (Android 13) OEM stock kernel (Jan 2023 Update).
v3.7.0_12-1 (2023-01-22):
Updated to X200XXU1CVL5 (Android 13) OEM stock kernel (Dec 2022 Update).
v3.7.0_12-0 (2023-01-01):
Fixed issue with MTP sometimes not starting until state is toggled in the Mount panel.
Switched to TWRP 3.7.0 release built from new AOSP-12.1 branch.
Updated to X200XXS1BVJ1 (Android 12) OEM stock kernel (Oct 2022 Security Update).
v3.7.0_11-1 (2022-10-24):
Adjusted dynamic partition size and removed redundant backup image.
v3.7.0_11-0 (2022-10-09):
Updated to TWRP 3.7.0 release built from AOSP-11 branch.
Updated to X200XXU1BVI6 (Android 12) OEM stock kernel.
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
v3.6.2_11-0 (2022-09-04):
Initial TWRP 3.6.2 release built from AOSP-11 branch.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to Recovery
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.
Source:
android_device_samsung_gta8wifi
Donations:
Your support is always appreciated! Just click here.
Additional Notes:
Ian's Multidisabler script has an issue on this device preventing it from disabling stock recovery auto-restoration. I'm hoping that a fix is forthcoming.
If you root this device with Magisk, be sure to patch only the boot.img file. Patching the AP tarball will generate a blank vbmeta.img, which this device's bootloader doesn't like for some reason.
Works on LTE version sm-x505 ??
Also which is better tab A7 or tab A8 ??
works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.
Magendanz said:
Notes:
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for metadata encryption (which causes mounting errors in log)
MTP doesn't start until you disable and reenable in the Mount panel
Downloads:
twrp_3.6.2_11-0_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-0_X200XXU1AVG1.img
Change Log:
v3.6.2_11-0 (2022-09-04):
Initial TWRP 3.6.2 release built from AOSP-11 branch.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to Recovery
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.
Source:
android_device_samsung_gta8wifi
Donations:
Your support is always appreciated! Just click here.
Click to expand...
Click to collapse
I am so delighted to see that there is major development for this device.
This will open the door for future custom ROMs.
Thank you Magendanz for your effort in bringing this to us.
I can say that is working as expected, thank you so much man. I thought that with TWRP we could be able to install a GSI ROM at least, but nothing at all lol
Tony Ronaldo Matute said:
I can say that is working as expected, thank you so much man. I thought that with TWRP we could be able to install a GSI ROM at least, but nothing at all lol
Click to expand...
Click to collapse
I think it's possible, but just using ChonDow_Flasher didn't work for me...I suspect because the bootloader isn't seeing an AVB hash footer on the GSI image. I had a similar experience when I built TWRP without the hash footer.
Unfortunately, I'm getting a segmentation error when trying to add a hash footer to the GSI using avbtool. It's probably a partition size issue, but I haven't had the time to troubleshoot.
Magendanz said:
I think it's possible, but just using ChonDow_Flasher didn't work for me...I suspect because the bootloader isn't seeing an AVB hash footer on the GSI image. I had a similar experience when I built TWRP without the hash footer.
Unfortunately, I'm getting a segmentation error when trying to add a hash footer to the GSI using avbtool. It's probably a partition size issue, but I haven't had the time to troubleshoot.
Click to expand...
Click to collapse
I had tried different ways also but I give up, the only thing that I can think now is try to use the "reboot to bootloader" feature in TWRP. But well, this processor is going me crazy.
Magendanz said:
Reserved
Click to expand...
Click to collapse
Once we get TWRP can't we just flash Magisk's zip file within TWRP like normally we do?
Also, after restart the tablet, when I tried to get back into TWRP it took me back to Android regular recovery. I had to flash TWRP again using Odin, after enabling MTP, local storage doesn't mount, I wasn't able to copy data in it.
zfk110 said:
Once we get TWRP can't we just flash Magisk's zip file within TWRP like normally we do?
Also, after restart the tablet, when I tried to get back into TWRP it took me back to Android regular recovery. I had to flash TWRP again using Odin, after enabling MTP, local storage doesn't mount, I wasn't able to copy data in it.
Click to expand...
Click to collapse
No, you should patch the boot.img using the Magisk app, then flash it using TWRP or pack in a tarball and use Odin. Don't patch the whole AP, as Magisk will substitute a blank vbmeta.img that the bootloader on this device doesn't like.
Rularick5 said:
works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.
Click to expand...
Click to collapse
Was just going to try this method but I'm on AVC1...I'm assuming I need to be on AVG1?
As long as the binary number is the same, im assuming dont quote me, you should be able to flash avg1 then magisk then twrp. Just update to the latest firmware.
I figured that's what I had to do but was trying to avoid that....just rooted a week ago and had no idea about AVG1.
So if I want to upgrade to AVG1 or any other firmware in the future I have to do the whole process again of patching boot.img, flashing through Odin, factory reset and setting up everything again? There's no way to upgrade and retain root?
Not unless you can recieve ota while rooted.
New release is posted...
Downloads:
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-1_X200XXU1AVG1.img
Change Log:
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
Magendanz said:
New release is posted...
Downloads:
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-1_X200XXU1AVG1.img
Change Log:
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
Click to expand...
Click to collapse
Any news for GSI?
Tony Ronaldo Matute said:
Any news for GSI?
Click to expand...
Click to collapse
I successfully tested fastbootd with OEM images, but the LineageOS GSI I tried was still getting kernel panics. I assume it has to do with this bootloader's AVB 2.0 requirements, which we can't seem to work around in the usual way with a blank vbmeta.img.
Magendanz said:
I successfully tested fastbootd with OEM images, but the LineageOS GSI I tried was still getting kernel panics. I assume it has to do with this bootloader's AVB 2.0 requirements, which we can't seem to work around in the usual way with a blank vbmeta.img.
Click to expand...
Click to collapse
"OEM images", so the Google GSI? Also, maybe could the vb meta zip disabler works?
Tony Ronaldo Matute said:
"OEM images", so the Google GSI? Also, maybe could the vb meta zip disabler works?
Click to expand...
Click to collapse
No, the OEM for this device is Samsung. Please provide a link for this vbmeta disabler, since I've just been using the ones generated by Magisk and my own using avbtool make_vbmeta_image --out vbmeta.img.
Magendanz said:
No, the OEM for this device is Samsung. Please provide a link for this vbmeta disabler, since I've just been using the ones generated by Magisk and my own using avbtool make_vbmeta_image --out vbmeta.img.
Click to expand...
Click to collapse
So, first you can try this disabler:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
as well, you can try to use this fastbootd command:
[Solved] VBmeta Flashing and Disable Verity Verification Command Problem
Thought to share with you guys, as many of people like me face problem while disabling the verification while flashing VBMETA.img. Most of the time the below command does not work and causes bootloop, when Installing Custom recovery. So i...
forum.xda-developers.com
Non-Official Lineage 20.0 for EMUI 9 Huawei (ANE, FIG, POT, VTR, STF)
{
"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"
}
LeaOS is a project which based on LineageOS 20.1 with Andy Yan's and TrebleDroid GSI patches. I have added my personnals patches for Huawei devices : Encryption, Signal Strengh, Speed Boot, Assisted GPS, NFC, CAST/Miracast, Media App fixes, Camera HDR, SafetyNet etc..)
Changelog :
LeaOS Maarch 2023 version
Move to Android r35 (SPL Maarch)
Add offline charging
Add spoof model to pass safetynet
LeaOS February 2023 version
First release
Pre-requisite :
You must have TWRP installed if you want install patch. and a phone with unlock bootloader
Installation (crypt or uncrypt)
Download the version that corresponds to your Huawei phone model here and extract img file. You can choose with ou without GoogleApps
Flash system image : fastboot flash system <drag system.img here>
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Boot into twrp: power + vol+ while NOT connected to pc
Resize system: Wipe > Advanced Wipe > System > Repair or Change File System > Resize File System > Swipe
Wipe cache, dalvik/art cache, internal storage
Wipe data
(option) Install DRM patch for EMUI 9.1 to support DRM : 8-Huawei-FixPreav-AB-v1.3-signed.zip
(option) Install single modem patch for multi-sim device : 11-Huawei-MonoSim-AB-v1.1-signed.zip
reboot to System and set up the phone with Lineage first start assistant.
Enjoy !!!
Source Code:
https://github.com/Iceows
ROM OS Version: Android 13
ROM Kernel: Linux Huawei 4.9.148 or Phenix 4.9.319
ROM Firmware Required: EMUI 9.1
Based On: Lineage 20.0 and TrebleDroid
Credits:
@Frax3r (Testing)
@PHH
@eremitein
@RakinTheGreat (GCam)
@TureX (Kernel)
And all the others who tested my patches and helped me improve this ROM
Support Group
Channel update
Testting on FIG-XXX, will post results
Mafworld said:
Testting on FIG-XXX, will post results
Click to expand...
Click to collapse
How did you manage to install it? I began with EMUI 9.1 .115, unlocked the bootloader flashed the system, flashed twrp, resized system partition, wiped cache, dalvik/art cache, internal storage, installed stock recovery but I can't wipe data. It says reset failed. As far as I remember not wiping data from stock recovery wont work, phone is just stuck in a TWRP loop
EDIT: Well it just booted right in without formatting data. Guess it's fine
Shume said:
How did you manage to install it? I began with EMUI 9.1 .115, unlocked the bootloader flashed the system, flashed twrp, resized system partition, wiped cache, dalvik/art cache, internal storage, installed stock recovery but I can't wipe data. It says reset failed. As far as I remember not wiping data from stock recovery wont work, phone is just stuck in a TWRP loop
EDIT: Well it just booted right in without formatting data. Guess it's fine
Click to expand...
Click to collapse
Not need reset data from stock recovery
AltairFR said:
Not need reset data from stock recovery
Click to expand...
Click to collapse
Well the storage isn't accessible through the file manager, 0 space for images, can't download from browser, and if data is wiped from twrp the device loops into twrp
EDIT: Wiping data from twrp and reflashing the stock recovery took me out of the loop, everything seems to be working now. I'll report bugs if I find any
Shume said:
Well the storage isn't accessible through the file manager, 0 space for images, can't download from browser, and if data is wiped from twrp the device loops into twrp
EDIT: Wiping data from twrp and reflashing the stock recovery took me out of the loop, everything seems to be working now. I'll report bugs if I find any
Click to expand...
Click to collapse
Can you upload stock recovery. It just boots in twrp but it is frozen
acidhell said:
Can you upload stock recovery. It just boots in twrp but it is frozen
Click to expand...
Click to collapse
Its on Haky86's sourceforge
Does anyone know how can I get root access with this custom ROM? I need recovery.img file but I don't know how to get it. Appreciate all the help.
Why you say recovery ? Just enable adb in root mode
When I was on EMUI 9.1 I extracted recovery image from UPDATE.APP so i could root with magisk. I figured I'd do the same now that I am on this custom ROM but yeah, got stuck.
I have many Bluetooth disconnections. In order to make a connection I have to stop Aufio FX, then scan bluetooth device and untick HD audio. After a restart I have to do these steps all over again.
Can I use this on EMUI 12?
I managed to install it on FIG-LX1, but my screen constantly goes blurry for a few seconds and then goes back to being sharp. Any fix for that?
Hello, any bugs/not working?
Everything works fine, I don't have any issue with my P Smart 2018 (FIG-LX1).
However, I lost a huge amount of time to root my phone. And I don't succeed. Does anyone have tutorial/information to help ?
JeyJer said:
Everything works fine, I don't have any issue with my P Smart 2018 (FIG-LX1).
However, I lost a huge amount of time to root my phone. And I don't succeed. Does anyone have tutorial/information to help ?
Click to expand...
Click to collapse
Root with magisk
Skole said:
Does anyone know how can I get root access with this custom ROM? I need recovery.img file but I don't know how to get it. Appreciate all the help.
Click to expand...
Click to collapse
As Skole previously, and according to the official Magisk procedure, I should have the "recovery.img" file to patch with Magisk. Unfortunately, this file is nowhere ?
-----------------------
EDIT: after discussing with @Skole yesterday (thank you again!), I finally got the point. If you want to root your FIG-LX1, you should download the official Huawei's stock ROM and then extract the RECOVERY_RAMDIS.img from it (you can use tools like Huawei Update Extractor to do so).
Then, use Magisk to patch the RECOVERY_RAMDIS.img file. At last, you should flash it in fastboot mode with the command
Bash:
fastboot flash recovery_ramdisk /path/to/magisk_patched.img
Note that the command below doesn't work
Bash:
fastboot flash recovery /path/to/magisk_patched.img
Next, when your phone is off, press Power + Vol+ buttons ; realease them when you see the splash screen Huawei.
You can follow this popular tutorial to root your phone, but keep in mind the advices above
If something went wrong (like me yesterday ), look at the "dload" method to unbrick your phone thanks to EMUI !
Merci beaucoup AltairFR for LeaOS ! You and Skole give my huawei a new life !
Hello, I have been trying to install this with no luck. I have an FIG-LX1 (bootloader & FRP unlocked) with TWRP already installed.
I'm stuck on the second step, where I need to flash the .img file I downloaded. This is the output I get from fastboot flash system LeaOS-20.0-20230331-iceows-google-fig.img: (the same also happens with the image that doesn't have gapps)
Code:
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 13.743s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
Can someone point me in a direction to go? I've been googling for hours with no avail.
(the phone currently cannot boot into any OS. only TWRP I got from this post)
kuylar said:
Hello, I have been trying to install this with no luck. I have an FIG-LX1 (bootloader & FRP unlocked) with TWRP already installed.
I'm stuck on the second step, where I need to flash the .img file I downloaded. This is the output I get from fastboot flash system LeaOS-20.0-20230331-iceows-google-fig.img: (the same also happens with the image that doesn't have gapps)
Code:
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 13.743s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
Can someone point me in a direction to go? I've been googling for hours with no avail.
(the phone currently cannot boot into any OS. only TWRP I got from this post)
Click to expand...
Click to collapse
Your system partition is two small, try to install leao-phh without gapps to see if boot
I think your system partition is too small.
You can use this tool. https://forum.xda-developers.com/t/huawei-partition-kit-enlarge-system-partition.4545993/ made by AltairFR pretty sure.
You will need OS first , you can install this one without google aps. https://forum.xda-developers.com/t/...fig-lx1-leaos-phh-android-13-version.4558685/