[ROM][OFFICIAL] LineageOS 17.1 for Nexus 6 (shamu) - Nexus 6 Original Android Development

LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Wiki.
Recovery
The LineageOS 17.1 reovery is recommended
If you still want to use TWRP never install the TWRP app as system app. Otherwise your device won't boot
Current lineage 17.1 shamu nightlies are based on the N6F27M October 2017 update from google.
So you should be using the radio and bootloader img from that update.
Before you flash a bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one and don't need to flash it again.
They can be extracted from the factory image on google's site here.
Or you can use the ones linked below that I already extracted:
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/shamu
Google apps: Opengapps Use an ARM (not ARM64) package for Android 10
HEADS UP: When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.
Changelog
Builddate: 2020.06.17
Changes:
[new] June security updates
[new] LineageOS clock
Builddate: 2020.05.29
Changes:
[new] May security updates
[fix] ULL audio fixes
[new] Add back serif fonts
[fix] Screen turning itself on when no lockscreen is set
[new] Etar calendar
Builddate: 2020.04.12
Changes:
[new] April security updates ROM & kernel
Builddate: 2020.04.08
Changes:
[new] Initial LineagOS 17.1 release
Known Issues:
[bug] Trusted voice is not working and probably never will
[bug] TWRP is not able do decrypt your data if you encrypted it with lineage-16.0
[bug] IMS is not working - if you need it you have to stay on lineage-15.1
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, elektroschmock, npjohnson
Source Code: http://github.com/lineagos
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2020-04-08
Last Updated 2020-04-08

Reserved
First build isn't out yet, but I don't want the LineageOS 16.0 thread to be spammed with 17.1 questions
Will waiting for the build you might want to read the Changlog for the first LineageOS 17.1 release:
Changelog 24

Will there be a possibility to root?

Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?

Thanks @Elektroschmock and @npjohnson for keeping the Nexus 6 alive in 2020. :good:

Eazy said:
Will there be a possibility to root?
Click to expand...
Click to collapse
Yes you can use your root solution of choice.
Only thing coming with the ROM is adb root.
dlbarron said:
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Click to expand...
Click to collapse
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]

Elektroschmock said:
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Click to expand...
Click to collapse
Actually, I've been running Lineage and CM before that since I brought the phone home. So there's no way I had the latest stock image installed ever.
Thanks, I'm all set

Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.

BootloopedMillennials said:
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
Click to expand...
Click to collapse
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work

xrenoix said:
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
Click to expand...
Click to collapse
My system got corrupted by the previous process. So I had to do a fresh install.

BootloopedMillennials said:
My system got corrupted by the previous process. So I had to do a fresh install.
Click to expand...
Click to collapse
Hello you have test wipe system with twrp ? Or test repair ? And use pico gapps for trébuchet launcher not work with mirco gapps but pixel launcher work ? !

whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .

mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Best would be to use built in update. Unless you want to do a clean install, there's no reason to do it.

the update inside of lineage is blocking updating to lineage 17.1 , i tried tha earlier and i jsut tried it again. then it gives the link to the wiki page.so thats not going to work.i will have to do the old method of flashing through twrp or hoping that there is a command line approach to flashing lineage through lineage recovery.

mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Sorry, I didn't ignore your question, but I first had to check.
It's kind of hard to imagine how a blind person would do it if you can see.
If you have Lineage recovery installed and are able to boot into recovery do the following steps:
Press the Volume Down button 1 time
Press the power button two times
You are now in the adb apply update mode.
There you can install all the zip files you want. I guess you script does the rebooting to system itself.
If you need further help just ask.

@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!

s_dino said:
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
Click to expand...
Click to collapse
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.

Elektroschmock said:
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Click to expand...
Click to collapse
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.

I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).

s_dino said:
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
Click to expand...
Click to collapse
You still have those options:
Go to "Factory Reset"
There you can choose which partition you want to wipe.
- Wipe data/factory reset
- Wipe cache
- Wipe system
I guess you want the "wipe system" option
Sorry we don't support modifying our builds for obvius reasons. If you want to do that you are on your own. Sorry.
runekock said:
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
Click to expand...
Click to collapse
It's just a test. Non of us was able to trigger the loss of audio. Youl'll still have stereo but it won't switch channels if you turn your device.

Related

[How to] Root, TWRP, Flash A300FU / A300Y Noob friendly guide

Bevor you do something with your Device do a Backup of all your Data (Contacts, Pic´s ect.) outside of your Device (in a Cloud or on your PC)​I'm not responsible for bricked devices, dead SD Cards, broken phone chargers etc.​You do all at your own Risk!​
If you are new, just work the first 3 steps from top to bottom.​
Flash Root & Odin3:
At the https://autoroot.chainfire.eu/ site you can Download the the Root File for your Device (Link to A300FU). When you Downloaded the "CF-Auto-Root-xxx.zip" File unzip it. In this zip you will find the Odin3xxx.exe and the Root .tar.md5 File
You need this Odin3 tool also for TWRP and going Back to Stock Rom
For Root: Make sure your device is in ODIN download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3xxx.exe file, press the PDA/AP button, select the Root .tar.md5 file, and click Start, never interrupt this action! You can find more detailed instructions and assistance at [CENTRAL] CF-Auto-Root Thread
Flash TWRP:
You can Download the TWRP File at the [RECOVERY][ROOT][TWRP 3.0.2-1]Samsung Galaxy A3(2015) SM-A300F/FU/G/H/M Thread. I recommend the Build from Post 80 it has working MTP & OTG for the FU Device!
To Install Start download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the Odin3xxx.exe file, press the PDA/AP button, select the TWRPxxx.tar file, and click Start, never interrupt this action! After Reboot you can get there by holding VolUp+Home+Power when the device is turned off.
There are also a TWRP 2.8.7.0 and a TWRP 3.0.0-0 but both have small bugs so i recommend TWRP 3.0.2-1 only if you have Problems try to downgrade
TWRP Bugs:
TWRP 2.8.7.0 Can only Install CM12.1 ROMs, it has no MTP & no OTG
TWRP 3.0.0-0 Can only Install CM13 ROM & it has no MTP but OTG is Working
TWRP 3.0.2-1 Can not install @cbolumar ROMs and the Build from Opening Post has no OTG
TWRP 3.1.0 Only tested with LineageOS, it still has no MTP!!!
Flash a Custom ROM:
You can Install a ROM now with TWRP you can enter TWRP by holding VolUp+Home+Power when the device is turned off.
In TWRP IT IS HIGHLY RECOMMEND TO DO FIRST A BACKUP! (I Recommend to placed at the SD Card)
Backup -> Storage : Micro SDcard -> Ok -> [x] Boot, [x] System, [x] Data, [x] Cache, [x] Recovery, [x] EFS, [x] MODEM, [x] APNHLOS -> Swipe to Backup
If anything goes wrong you can easy Restore your Device in TWRP without losing anything, so it's also recommended to Backup your Custom ROM
Now you need your Custom Rom, Google Apps like Opengapps for ARM and i recommend latest Magisk[/URL, OR (if you prefer) [URL="http://download.chainfire.eu/supersu"]SuperSU to Manage Root Access.
Place this zip Files at your Device (I Recommend to placed at the SD Card)
Now you enter TWRP and go to:
Wipe -> Advanced Wipe -> [x] Dalvik / ART Cache, [x] System, [x] Data, [x] Cache -> Swipe to Wipe
Now go back to main menu and select:
Install -> Storage : Micro SDcard -> Ok -> now choose your ROM zip first, you can "Add More Zips" and choose Gapps zip and if you want you can Add direct Magsik OR SuperSU zip as well -> Swipe to Confirm Flash
After placing files the Device need a Reboot, at the First Start it will Install your Rom, so be patiently at first start!
Flash Xposed:
Magisk user on Android M (6.x) or better follow this Thread [2018.5.6][Magisk] Systemless Xposed v89.3/v90.2-beta3 (SDK 21-27) by topjohnwu
SuperSU user on Android M (6.x) or better follow this Thread [OFFICIAL] Xposed for Lollipop/Marshmallow/Nougat/Oreo [v90-beta3, 2018/01/29]
info:
SDK 21: Android 5.0 | SDK 22: Android 5.1 | SDK 23: Android 6.0 | SDK 24: Android 7.0 | SDK 25: Android 7.1 | SDK 26: Android 8.0 | SDK 27: Android 8.1
at CM12.1 ROM's Offical Xposed works fine.
Download the "sdk22-arm" zip, and Install it with TWRP first start need a long time! be patient!
After the Framework is installed you install the "XposedInstaller" apk, done.
For stock rom you should visit [UNOFFICIAL] Xposed for Samsung Lollipop by arter97 but it´s for deodex'ed ROMs for this you should visit [Deodex][SM-A300] Deodex Thread for Samsung Galaxy A3
emtepe35 said:
Working only on MM touchwiz (tested by me on A300FU with TWRP 3.0.2-1)
How to install:
- Install this Xposed Installer App version http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
- Make a nandroid backup
- Copy the Xposed file and the uninstaller to your sdcard
- Flash "xposed-vxx.x-sdkxx-tw-armxx-custom-build-by-wanam-xxxxxxxx.zip" through a custom recovery (TWRP/CWM...)
- Reboot and Waiiiiiiiiit, it may take several minutes to boot up depending on your Rom size.
xposed.zip download (ARM SDK23)
https://www.androidfilehost.com/?fid=24591000424962808
Official thread link:
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Click to expand...
Click to collapse
Flash Stock ROM:
Download your Firmware at Sammobile than i recommend you to Wipe all (Advanced Wipe) in TWRP except the SDcard!
Boot your Device in ODIN download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the Odin3xxx.exe file, press the PDA/AP button, select the .tar.md5 file, and click Start, never interrupt this action!
After doing this you lose TWRP and Root so if you need it you have to install it new.
You should not try to Flash 4.x ROMs it could Brick your Device!
With a Stock Marshmallow ROM it is recommended to use a Custom Kernel
A300FU / A300Y Custom Kernel:
Kraken Kernel R1 from @bulgar
Will only work with at Stock Marshmallow (6.x) ROM
-soon- LineageOS Support
hadesKernel from @corsicanu
Will only work with at Stock Marshmallow (6.x) ROM
A300FU / A300Y Modification:
[MOD][Stock Rom] Enable More Quick Tiles on Touchwiz from @astrit1
Will only work with at Stock Lollipop (5.x) ROM
There are still the following Bugs:
No Bugs
[ROM][A300FU][6.0.1] [GS]Mod from @[GS]
There are still the following Bugs:
Private Mode Not Work
WHASISTROM We have a simple stock rom [A300FU/OL3/OJ5] from @nowheel Discontinued
nowheel said:
Bad news i abbandoned project.. after my hdd is broken with project and all whasistrom file, work document and other.
Click to expand...
Click to collapse
A300FU / A300Y Custom ROMs:
Check also in All Samsung Galaxy A3 (2015)'s ROMs Thread from @Falaysia
-Recommended-
LineageOS 15.1 Unofficial for Samsung Galaxy A3 (2015) from @vl_w
There are still the following Bugs:
* FM works only on headphones
* Unable to capture video in 1080p (only 720р works)
* Incorrectly work with secondary sim (incall sound issues)
* On FU and H doesn't adjusting flahlight brightness
* On H incorrectly detecting battery temperature
* Hardware keystore doesn't work (only software)
* NFC sometimes doesn't work
LineageOS 14.1 Unofficial for Samsung Galaxy A3 from @vl_w
There are still the following Bugs:
no Bugs
CyanogenMod 12.1 for Samsung Galaxy A3 from @evilracer123 Discontinued
Meizirkki said:
OP is no longer working on a300fu
Click to expand...
Click to collapse
In the Opening Post is not the latest Build!
This is the post with the last Build from 19th January 2016
evilracer123 said:
Here's the newest build:
https://mega.nz/#!OcJ0BKKQ!hkQN4SnzY-40tm9v79vzP_erZxIxtpa0_jPwMvLQaiU
Click to expand...
Click to collapse
There are still the following Bugs:
-SoD´s (can be Fixed for the most users by using CPU Awake - Wake Lock with Unlimited time & Activate on Reboot (Clean Master turns it off btw) or Wake Lock - PowerManager with "PARTIAL_WAKE_LOCK")
-Preview in stock camera (can be Fixed by change Resolution to 16:9 in Settings)
-FM Radio not Working (can be Fiexed by using Spirit2)
-Folders are not displayed correctly with LCD density 260 DPI (can be Fixed by changing it to 240 DPI)
-When screen is off touch buttons still working, at touch the phone vibrates.
-USB Conection adb only working MTP, PTP, OTG or UMS not Working (you can use MTP and OTG in TWRP 3.0.2-1 Recovery)
-for some users "com.qualcomm.timeservice" fc time to time (can be Fixed by disable the automatic services in Time settings)
-for some users gps are not Working
at my device:
-Cast screen is not Working
CyanogenMod 12.1 Resurrection Remix from @cbolumar Discontinued
garbanura said:
he switched to a5 and abandoned a3 for good, i know from first hand sorry.
Click to expand...
Click to collapse
There are still the following Bugs:
-SoD´s (can be Fixed for the most users by open integrated Kernel Adiutor and allow Root access)
-Preview in stock camera (can be Fixed by change Resolution to 16:9 in Settings)
-FM Radio not Working (can be Fiexed by using Spirit2)
-When screen is off touch buttons still working, at touch the phone vibrates.
-USB Conection adb only working MTP, PTP, OTG or UMS not Working (you can use MTP and OTG in TWRP 3.0.2-1 Recovery)
at my device:
-Cast screen is not Working
Note: can only installed with TWRP 2.8.7.0 after installing you can upgrade your Recovery to TWRP 3.0.2-1
CyanogenMod 12.1 from @cbolumar Discontinued
garbanura said:
he switched to a5 and abandoned a3 for good, i know from first hand sorry.
Click to expand...
Click to collapse
There are still the following Bugs:
-SoD´s (can be Fixed for the most users by using CPU Awake - Wake Lock with Unlimited time & Activate on Reboot (Clean Master turns it off btw) or Wake Lock - PowerManager with "PARTIAL_WAKE_LOCK")
-Preview in stock camera (can be Fixed by change Resolution to 16:9 in Settings)
-FM Radio not Working (can be Fiexed by using Spirit2)
-When screen is off touch buttons still working, at touch the phone vibrates.
-USB Conection adb only working MTP, PTP, OTG or UMS not Working (you can use MTP and OTG in TWRP 3.0.2-1 Recovery)
-for some users "com.qualcomm.timeservice" fc time to time (can be Fixed by disable the automatic services in Time settings)
at my device:
-Cast screen is not Working
Note: can only installed with TWRP 2.8.7.0 after installing you can upgrade your Recovery to TWRP 3.0.2-1
Hope this will Help to answering the most Questions
By the way i'm not a Dev, i'm only a regular user that wants to help!
You will also get Information and Help at the Everything Samsung a3 Thread :good:
Nice guide. Which one would you recommend between the CM12.1 and CM12.1 RR?
Also, for downgrading TWRP, you just need to flash the older version, right?
King-V said:
Nice guide. Which one would you recommend between the CM12.1 and CM12.1 RR?
Also, for downgrading TWRP, you just need to flash the older version, right?
Click to expand...
Click to collapse
Definitely CM12.1 RR!
Right just flash first TWRP 2.8.7.0 via Odin3 install the ROM and than Flash TWRP 3.0.2-1 via Odin3, btw. the Build from post 80 has a working MTP and OTG in TWRP (only in TWRP not at the ROM!)
And you can anytime time flash TWRP 2.8.7.0 again if you have to Install new
So only good ROM for daily driver will be @mygalaxya cm13?
emtepe35 said:
So only good ROM for daily driver will be @mygalaxya cm13?
Click to expand...
Click to collapse
This could need some time, i recommend to try CyanogenMod 12.1 Resurrection Remix, or a Stock MM with aresKernel :good:
Jonny_Hood said:
This could need some time, i recommend to try CyanogenMod 12.1 Resurrection Remix, or a Stock MM with aresKernel :good:
Click to expand...
Click to collapse
It's lot to do with RR to make it stable without SOD etc. (I really need normal usb connection for daily usage)
What's twrp should I use with stock mm to flash ares kernel and can I go back to lollipop via odin? (Mygalaxya's cm13 needs LP bootloader and modem)
emtepe35 said:
It's lot to do with RR to make it stable without SOD etc. (I really need normal usb connection for daily usage)
What's twrp should I use with stock mm to flash ares kernel and can I go back to lollipop via odin? (Mygalaxya's cm13 needs LP bootloader and modem)
Click to expand...
Click to collapse
Best is TWRP 3.0.2-1 and yes you can go back anytime via odin
Jonny_Hood said:
Best is TWRP 3.0.2-1 and yes you can go back anytime via odin
Click to expand...
Click to collapse
Thanks I tried this but I flashed wrong firmware and wifi was broken but I know how to repair it.
Tomorrow I'll try flash compatible firmware and try again.
After flash MM and reflash LP it was a bootloop in first boot. I went to download mode and flash twrp then restore backup and it boots up.
Thanks
emtepe35 said:
Thanks I tried this but I flashed wrong firmware and wifi was broken but I know how to repair it.
Tomorrow I'll try flash compatible firmware and try again.
After flash MM and reflash LP it was a bootloop in first boot. I went to download mode and flash twrp then restore backup and it boots up.
Thanks
Click to expand...
Click to collapse
This Bootloop thing happened at my Device sometimes too, if i flashed a stock ROM via Odin, thats why i started to Wipe all Partitions via TWRP before flashing, that works for me flawless
Than happy flashing tomorrow
Jonny_Hood said:
This Bootloop thing happened at my Device sometimes too, if i flashed a stock ROM via Odin, thats why i started to Wipe all Partitions via TWRP before flashing, that works for me flawless
Than happy flashing tomorrow
Click to expand...
Click to collapse
OK I've got one last question the wipe in twrp means it deleting it to zero and if I accidentally go to system and not to download I'll get hard brick? Or wipe means it restoring it to factory files? Wipe modem too?
Sorry for noob questoms but I want to be sure before do anything
emtepe35 said:
Wipe in twrp means it deleting it to zero?
Click to expand...
Click to collapse
Yes
emtepe35 said:
If I accidentally go to system and not to download I'll get hard brick?
Click to expand...
Click to collapse
No it will not brick, if you accidentally go to system it will stuck at A3 logo, than you can go to Download Mode with pressing "VolDown+Home+Power" for 30 Sec
emtepe35 said:
Or wipe means it restoring it to factory files? Wipe modem too?
Click to expand...
Click to collapse
Wipe -> Advanced Wipe -> [x] Dalvik / ART Cache, [x] System, [x] Data, [x] Internal Storage, [x] Cache -> Swipe to Wipe -> go back -> go back -> Format Data -> yes
Added to Sticky Roll-Up Thread
Cheers
Razvan
Forum Moderator
Razvan said:
Added to Sticky Roll-Up Thread
Cheers
Razvan
Forum Moderator
Click to expand...
Click to collapse
Thank you very much
What about stock marshmallow xposed?
Sorry I'm noob and I can't find it alone.
emtepe35 said:
What about stock marshmallow xposed?
Sorry I'm noob and I can't find it alone.
Click to expand...
Click to collapse
As far i know, it will not working with Stock MM.
Known issues:
- Bootloops on Samsung stock ROMs. That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
Jonny_Hood said:
As far i know, it will not working with Stock MM.
Known issues:
- Bootloops on Samsung stock ROMs. That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
Click to expand...
Click to collapse
I had a LP stock Samsung touch wiz and it was working. Some people tells they have MM xposed. I'll try to ask them
emtepe35 said:
I had a LP stock Samsung touch wiz and it was working. Some people tells they have MM xposed. I'll try to ask them
Click to expand...
Click to collapse
Let me know if and how it work
I'm happy with this.
Working only on MM touchwiz (tested by me on A300FU with TWRP 3.0.2-1)
How to install:
- Install this Xposed Installer App version http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
- Make a nandroid backup
- Copy the Xposed file and the uninstaller to your sdcard
- Flash "xposed-vxx.x-sdkxx-tw-armxx-custom-build-by-wanam-xxxxxxxx.zip" through a custom recovery (TWRP/CWM...)
- Reboot and Waiiiiiiiiit, it may take several minutes to boot up depending on your Rom size.
xposed.zip download (ARM SDK23)
https://www.androidfilehost.com/?fid=24591000424962808
Official thread link:
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Hi, what I have to do to downgrade my A300FU to lollipop (Brand Italy Vodafone)?
InfamousMykol said:
Hi, what I have to do to downgrade my A300FU to lollipop (Brand Italy Vodafone)?
Click to expand...
Click to collapse
Stock ROM:
Download your Firmware at Sammobile than i recommend you to Wipe all (Advanced Wipe) in TWRP except the SDcard!
Boot your Device in ODIN download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the Odin3xxx.exe file, press the PDA/AP button, select the .tar.md5 file, and click Start, never interrupt this action!
After doing this you lose TWRP and Root so if you need it you have to install it new.

[Unofficial] [05.10.2017]TWRP 3.1.1-0 Moto G5 [cedric]

Unofficial TWRP 3.1.0-0 Moto G5 (cedric) ​
Latest TWRP changelog :
New features of 3.1.1-0 (adb backup, tweaked MTP startup routines and plenty of bug fixes - for full changelog)
Download Link
twrp-3.1.1-0-cedric.img
Working/Bugs
I have just tested on 16 GB variant and all seems to be working. If something is broken lemme know.
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) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide
Make sure you have unlocked bootloader
Reboot to bootloader
fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary
boot)
XDA:DevDB Information
[Unofficial] TWRP 3.1.1-0 Moto G5, Tool/Utility for the Moto G5
Contributors
Santhosh M
Source Code: http://Using prebuilt stock kernel and hence no kernel source available
Version Information
Status: Stable
Stable Release Date: 2017-10-05
Created 2017-03-17
Last Updated 2017-10-05
Reserved
Reserved
Even though I have the plus variant, it's cool to see these features popping up.
Johny Cipeli said:
Even though I have the plus variant, it's cool to see these features popping up.
Click to expand...
Click to collapse
+1
Grt @Santhosh M
Santhosh M said:
Reserved
Click to expand...
Click to collapse
Gonna get that g5+ Bro? it would be awesome if you will be there for support too.
xt1670 model
Hi Santhosh
Will this TWRP work on Moto G5 model xt1670?
If so, can it be rooted using twrp temporary boot?
EDIT: I have tried this several time, I'm always getting stuck at boot, after the first data wipe, only solution is to install stock system again.
I have the Modem Version: M8937_8000.122.02.40R, 32GB
I'm offering to test
Thanks
Works fine for the most part, though reboot options Bootloader and Power Off doesn't work, just restarts normally.
XT1676
KawaiiNeko said:
Works fine for the most part, though reboot options Bootloader and Power Off doesn't work, just restarts normally.
XT1676
Click to expand...
Click to collapse
Plz share the procedure you had followed.
Did you able to achieve root access?
fAIyaZ said:
Plz share the procedure you had followed.
Did you able to achieve root access?
Click to expand...
Click to collapse
Unlocked bootloader, flashed twrp, factory reset, good to go. Sadly no root though.
KawaiiNeko said:
Unlocked bootloader, flashed twrp, factory reset, good to go. Sadly no root though.
Click to expand...
Click to collapse
Try phh su.
Flash it through twrp: https://superuser.phh.me/superuser.zip
Then installed the phh superuser app: https://play.google.com/store/apps/d....phh.superuser
fAIyaZ said:
Try phh su.
Flash it through twrp: https://superuser.phh.me/superuser.zip
Then installed the phh superuser app: https://play.google.com/store/apps/d....phh.superuser
Click to expand...
Click to collapse
worked perfectly! https://i.imgur.com/71G0cN2.png
I'll get my G5 16gb lunar grey tomorrow and can't wait to root
Thanks for testing out
Bootlooping
Hi guys, I got bootloop in my moto g5 after TWRP boot/install, should I open a new thread or somebody can help here?
linsspinho said:
Hi guys, I got bootloop in my moto g5 after TWRP boot/install, should I open a new thread or somebody can help here?
Click to expand...
Click to collapse
Depending on your phone version, you might need to flash system using fastboot.
KawaiiNeko said:
worked perfectly! https://i.imgur.com/71G0cN2.png
Click to expand...
Click to collapse
So i believe TWRP works as intended and root is also achieved via phh/whatever?
If all works fine for you would like you to make reply in the thread with detailed flashing instructions as i am not sure why few in thread have issues
can this version of twrp be used for POTTER version of moto G5 plus?
After installing TWRP my Phone stucks at the "Your device has been unlocked" screen. My system seems to be gone. I've downloaded the image from the other thread and tried to sideload it, but twrp says it's in the wrong format. TWRP boots fine
(Anyone who can upload a fully working NANDROID or sth like that?)
What can i do :/?
Edit: Solved. Unzipped the firmware and flashed manually via fastboot. Working fine!
But then again at the startup of the recovery, there's the encryption message. What to wipe now, that it'll work? Wiping /data ends in boot loop...
.sirhc said:
After installing TWRP my Phone stucks at the "Your device has been unlocked" screen. My system seems to be gone. I've downloaded the image from the other thread and tried to sideload it, but twrp says it's in the wrong format. TWRP boots fine
(Anyone who can upload a fully working NANDROID or sth like that?)
What can i do :/?
Edit: Solved. Unzipped the firmware and flashed manually via fastboot. Working fine!
But then again at the startup of the recovery, there's the encryption message. What to wipe now, that it'll work? Wiping /data ends in boot loop...
Click to expand...
Click to collapse
Did you tried wiping data, and formatting data? Remember that wiping /data is where your apps and settings are stored, and formatting /data/media is the massive storage... Maybe if you wipe both it would work
Enviado desde mi Moto G (5) Plus mediante Tapatalk
After
fastboot flash recovery twrp.img
I'm booting into recovery, cancel the encryption password verification, swipe to allow modification, wipe & format data -> Bootloop
Flashing system (and only system, not recovery etc) -> Phone boots normally, twrp ist gone ...
Greetings

[RECOVERY][UNOFFICIAL][Sanders] TWRP-3.2.1-r20 (64bit Supported!)

Unofficial TWRP for Moto G5S Plus (Sanders)​
Additional Features over Official TWRP:
Supports flashing of both 32bit and 64bit ROMs and Kernels.
OREO Images/ROMs support.
Decryption and Encryption support.
No SuperSU by default.
No TWRP app.
No HTC Dumlock cruft.
Updated pigz compressor (slightly faster and more tolerant of corruption).
NTFS support(Both Read and Write).
Covers more partitions for nandroid backup (OEM, FSG and FSC).
Experimental support for SD cards that are partitioned for partial adopted storage and partial removable storage.
Faster I/O performance.
Fixed Gapps/aroma freeze issues.
IMPORTANT!!! : READ INSTRUCTIONS CAREFULLY BEFORE PROCEEDING TO FLASHING PROCESS..!!
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) . To avoid this you have to flash either Magisk or flash any of the verity disabler zips available on xda.
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Flashing Instructions:
Using Existing TWRP:
Reboot to recovery > Click on Install > Install Image > recovery > select recovery image and flash > reboot to recovery
Other Methods(Fastboot) :
Make sure you have unlocked bootloader
Reboot to bootloader
Enter following command in terminal: fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary boot)
Incase your device is encrypted (while coming from stock rom), Follow these steps to decrypt:
Reboot to recovery > cancel the password prompt > mount all partitions > Format Data/Userdata (on f2fs) > Reboot Recovery > Mount all partitions again > Flash Magisk > Reboot
Now you are free to use Stock ROM (Decrypted) or Flash any custom rom you want.
Download Links: https://www.androidfilehost.com/?w=files&flid=216298
TWRP Themes: Check 3rd post
Known Issues: None || Report if you find any.
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][Sanders] TWRP-3.2.1-r20 (64bit Supported!), Tool/Utility for the Moto G5S Plus
Contributors
CheckYourScreen
Source Code: https://github.com/CheckYourScreen/twrp_device_motorola_sanders
Version Information
Status: Stable
Current Stable Version: r20
Stable Release Date: 2018-04-04
Created 2017-10-26
Last Updated 2018-04-04
|| Changelog ||
r20:
Fixed Encryption support on custom roms.
Updated kernel
Updated build fingerprint for latest bootloader support.
Reverted pigz changes.
Switched back to original twrp themes. (TWRP Themes can be found in 3rd post )
Various bug fixes and improvements.
r16:
Fixed compatibility with New Bootloader (C2.07-December patch)
Merged october patches in kernel.
Various twrp upstream patches and fixes.
Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)
r15:
Added 64bit Support (You can flash both 32bit/64bit roms or kernels with it).
Fixed Encryption Support! (No need to format data to decrypt and mount).
Updated to 3.2.1 upstream changes with full oreo support.
Remove android reboot during password check on multiple wrong inputs.
r9:
Fixed F2FS mount issues(You can flash magisk modules or SuperSu now).
Enabled NTFS Write Support (You can make backups on sdcard/pendrives formatted on NTFS).
Fixed size of various partitions.
Switched to LZMA compression to decrease size.
r7: Initial Public Release
|| Themes ||
Here are some of the twrp themes:
Preview images: https://photos.app.goo.gl/DLrfDseGzfxE8Uq93
Download link: https://androidfilehost.com/?w=files&flid=233551
:good:
Only one that has actually be working for me ever since I got the phone. Thank you for your efforts.
this seems to suffer from the same thing the stock rom/kernel suffers from, the weird f2fs bug that makes certain mounts fail. geneticengineer has shared a kernel that fixes this in stock rom , maybe you could get in touch with him about how he updated f2fs
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
revengineer said:
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
Click to expand...
Click to collapse
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Schrotty35 said:
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Click to expand...
Click to collapse
Well my guess is that the kernel in the present twrp is from the -26 firmware posted in the other thread. That firmware was US Retail also. The OP in the other thread states in can be used on other models. But I am not going to tell you that because I do not know. I have not found any other firmware for the sanders model.
Ae3NerdGod said:
this seems to suffer from the same thing the stock rom/kernel suffers from, the weird f2fs bug that makes certain mounts fail. geneticengineer has shared a kernel that fixes this in stock rom , maybe you could get in touch with him about how he updated f2fs
Click to expand...
Click to collapse
Afaik it doesnt affect TWRP, you just need to be on a custom kernel if you are running stock rom.
Twrp has nothing to do with it.
If you face any problem flashing anything then post a screenshot or log.
revengineer said:
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
Click to expand...
Click to collapse
Schrotty35 said:
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Click to expand...
Click to collapse
Stock kernel is same in both the firmwares.
-45 is just for US variant, i dont recommend you to even flash that firmware on other variants.
CheckYourScreen said:
Afaik it doesnt affect TWRP, you just need to be on a custom kernel if you are running stock rom.
Twrp has nothing to do with it.
If you face any problem flashing anything then post a screenshot or log.
Click to expand...
Click to collapse
but i have a custom stock kernel, and things that fail in TWRP work in flashfire or magiskmanager
its mostly magisk modules im having problems with, ill reproduce an error when i get the chance
Ae3NerdGod said:
but i have a custom stock kernel, and things that fail in TWRP work in flashfire or magiskmanager
its mostly magisk modules im having problems with, ill reproduce an error when i get the chance
Click to expand...
Click to collapse
Flash the magisk module via twrp > take screenshot when flashing completes > go to advance section of twrp and take recovery log > reboot system > send that screenshot and recovery log here.
CheckYourScreen said:
Flash the magisk module via twrp > take screenshot when flashing completes > go to advance section of twrp and take recovery log > reboot system > send that screenshot and recovery log here.
Click to expand...
Click to collapse
will do, it happens with every magisk package i try. they used to fail in stock too till i used geneticengineers kernel from telegram now they work
didnt know you could screenshot in recovery, i assume its the same buttons
Ae3NerdGod said:
will do, it happens with every magisk package i try. they used to fail in stock too till i used geneticengineers kernel from telegram now they work
didnt know you could screenshot in recovery, i assume its the same buttons
Click to expand...
Click to collapse
Yes, same buttons to take a screenshot in TWRP
TWRP backup is frozen at 13% completed. The progress bar is still showing its animation.
I unlocked the bootloader, and then rebooted. Android came up with the language selection screen. I powered off, connected the phone to the PC, and booted into TWRP (not flashed yet):
Code:
fastboot boot twrp-3.1.1-sanders-r7.img
I did not let TWRP format /data.
Then I started a backup, selecting all partitions, so that I could always go back after flashing TWRP and Magisk.
Does anyone know why backup is stuck at 13%? Last log line says "Backing up System..."
I tapped "Cancel" after two hours. That stopped the progress bar animation, but not the backup itself.
BTW: I used TWRP from this thread, the one in another thread freezes at the TWRP boot logo.
Edit: after two hours I killed the backup by powering down (the only way it seemed). On retry it froze at 21%.
Edit 2: Retried, this time backing up everything except system. No problem. I then tried to backup system. Frozen at 1%. What is the problem here?
Edit 3: Finally, a complete backup of system! Only one to go: system_image. But unfortunately that froze at 0%. Every subsequent try freezes at 1666MB (40%). The card has over 30GB free. I tried backup to USB-OTG, but that also froze.
gewe said:
TWRP backup is frozen at 13% completed. The progress bar is still showing its animation.
I unlocked the bootloader, and then rebooted. Android came up with the language selection screen. I powered off, connected the phone to the PC, and booted into TWRP (not flashed yet):
Code:
fastboot boot twrp-3.1.1-sanders-r7.img
I did not let TWRP format /data.
Then I started a backup, selecting all partitions, so that I could always go back after flashing TWRP and Magisk.
Does anyone know why backup is stuck at 13%? Last log line says "Backing up System..."
I tapped "Cancel" after two hours. That stopped the progress bar animation, but not the backup itself.
BTW: I used TWRP from this thread, the one in another thread freezes at the TWRP boot logo.
Edit: after two hours I killed the backup by powering down (the only way it seemed). On retry it froze at 21%.
Edit 2: Retried, this time backing up everything except system. No problem. I then tried to backup system. Frozen at 1%. What is the problem here?
Edit 3: Finally, a complete backup of system! Only one to go: system_image. But unfortunately that froze at 0%. Every subsequent try freezes at 1666MB (40%). The card has over 30GB free. I tried backup to USB-OTG, but that also froze.
Click to expand...
Click to collapse
Might be due to data partition being encrypted, you cant write anything in it without decrypting it first.
Format data and reboot recovery, then make the backup. You can flash magisk after taking the backup.
Btw r9 new release on its way with some really important changes
CheckYourScreen said:
Might be due to data partition being encrypted, you cant write anything in it without decrypting it first.
Format data and reboot recovery, then make the backup. You can flash magisk after taking the backup.
Btw r9 new release on its way with some really important changes
Click to expand...
Click to collapse
I was not trying to write the backup to the data partition, but to external SD card (tried OTG-USB as well without success).
I have flashed TWRP, formatted the data partition, and flashed Magisk. I have not tried to create a new backup yet. First I want to find out why Magisk does not pass the Safetynet check.
Can't wait to see what r9 brings. Thanks for your efforts. :good:
gewe said:
I was not trying to write the backup to the data partition, but to external SD card (tried OTG-USB as well without success).
I have flashed TWRP, formatted the data partition, and flashed Magisk. I have not tried to create a new backup yet. First I want to find out why Magisk does not pass the Safetynet check.
Can't wait to see what r9 brings. Thanks for your efforts. :good:
Click to expand...
Click to collapse
Magisk won't pass safety net with stock boot.img (kernel). Here is a modified kernel.
https://forum.xda-developers.com/showthread.php?p=73930507
After flashing new kernel Magisk passes no problem.
Sent by way of magic
lilcdroid said:
Magisk won't pass safety net with stock boot.img (kernel). Here is a modified kernel.
https://forum.xda-developers.com/showthread.php?p=73930507
After flashing new kernel Magisk passes no problem.
Sent by way of magic
Click to expand...
Click to collapse
When I flash this my WiFi stops working completely. I'm running aosp extended rom. I'm not sure if I can achieve battery life as good as I can on the stock ROM as I can on this one so im not sure what I should do about that..
Brycearuuni said:
When I flash this my WiFi stops working completely. I'm running aosp extended rom. I'm not sure if I can achieve battery life as good as I can on the stock ROM as I can on this one so im not sure what I should do about that..
Click to expand...
Click to collapse
Sorry I wasn't aware you weren't still on stock. That kernel will only work on stock. I would verify with the maintainer of AOSP extended ROM that the kernel is patched to work with Magisk.
Sent by way of magic

[UNOFFICIAL] TWRP 3.2.3-0 [TREBLE][64bits]

Latest TWRP changelog :
New features of 3.2.3-0:
Changelog)
Download Link - 64 bits version (non-treble)
twrp-3.2.3-0-64bits.img
Download Link - Treble version (64bits too)
twrp-3.2.3-0-treble.img
Working/Bugs
I have just tested on 16 GB variant and all seems to be working. If something is broken lemme know.
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) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide
Make sure you have unlocked bootloader
Reboot to bootloader
fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary
boot)
XDA:DevDB Information
[Unofficial] TWRP 3.2.3-0 Moto G5, Tool/Utility for the Moto G5
Contributors
ZJRDroid
Source Code: Local manifests
Version Information
Status: Stable
Stable Release Date: 2019-01-18
Created 2019-01-18
Last Updated 2019-01-18
Thanks for the updated TWRP! Works like a charm
Are there any circumstances which would make it necessary to use the non-treble version?
image not signed or corrupted moto g 5 cedric. is this for cedric?
edit2: my friend used the fastboot boot recovery option the recovery booted and asked a password, then he pressed back and the other screen with the swipe button has appeares (allow system modifications) and now what to do? the sdcard folder doesn't have nothing inside, neither the external sd
update3: after requering the password he pressed back and then formatted the phone, phone booted into the stock rom, and the twrp is gone.
update4: tried install viperos cedric android 9.0.0 gave error 7 I don't know what to do twrp is working, he tried this https://www.youtube.com/watch?v=VCqROwIGLLE and now stock rom is gone. we are loosing hope ;-;
update 5: tried using the twrp provided by this guy https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737/page11 but nothing. still error 7 even doing the procedure above ^^
update 6: Forget everything you read, upthere^^^^ he downloaded the rom for a different phone XD
so anone tested any treble roms from the project forum on our phones with this twrp?
luigge said:
edit2: my friend used the fastboot boot recovery option the recovery booted and asked a password, then he pressed back and the other screen with the swipe button has appeares (allow system modifications) and now what to do? the sdcard folder doesn't have nothing inside, neither the external sd
Click to expand...
Click to collapse
What did he do exactly to avoid the password screen?
so...does this fix some of the issues present in the previous treble recovery? such as the camera not working? flashlight not working? crashes? can i use it as a daily driver?
I tried this ones. Camera working and no crashes, really stable.
[PORTED][semi-GSI][PPR2.181005.003][UNOFFICIAL]P sGSI PR2[A-ONLY]
......
[8.1][sGSI]MIUI10 for Project Treble
......
[9.0] [UNOFFICIAL] [ARM64 A-ONLY] AOSiP Pizza Alpha [EXPERIMENTAL] (Camera crashes but open camera works with videos)
.......
[GSI] OmniROM 8.1 [Unofficial] [ARM64]-[A-Only] [21.10.18]
Those i tested for like 1 hour and in this time everything works good. Iam staying with Omni cuz it feels uber fast and stable.
alright so here's a question: the lineage treble build to flash before the img is down, so where can i find a treble-ised rom to flash before the actual image?
fenerbuuh said:
I tried this ones. Camera working and no crashes, really stable.
[PORTED][semi-GSI][PPR2.181005.003][UNOFFICIAL]P sGSI PR2[A-ONLY]
......
[8.1][sGSI]MIUI10 for Project Treble
......
[9.0] [UNOFFICIAL] [ARM64 A-ONLY] AOSiP Pizza Alpha [EXPERIMENTAL] (Camera crashes but open camera works with videos)
.......
[GSI] OmniROM 8.1 [Unofficial] [ARM64]-[A-Only] [21.10.18]
Those i tested for like 1 hour and in this time everything works good. Iam staying with Omni cuz it feels uber fast and stable.
Click to expand...
Click to collapse
how'd you get the MIUI10 sGSI working on your phone? mine keeps rebooting into twrp
Links for both versions are down. Can you re-upload, please?
actuallynxthing said:
Links for both versions are down. Can you re-upload, please?
Click to expand...
Click to collapse
here
Both of these are not working for me.
All I get is the normal, stock recovery screen.
But yeah, do note that I had installed the 3.3 official which worked for just one boot. After that, I'm getting the stock recovery screen too.
---------- Post added at 04:58 AM ---------- Previous post was at 04:14 AM ----------
eljoantonyn said:
Both of these are not working for me.
All I get is the normal, stock recovery screen.
But yeah, do note that I had installed the 3.3 official which worked for just one boot. After that, I'm getting the stock recovery screen too.
Click to expand...
Click to collapse
Spoke too soon !
Got it working.
Now I need to see why it says "wrong password" while trying to decrypt.
Link fallen
Would you people kindly stop deleting your files from android file host, sick of broken links
Cloudane said:
Would you people kindly stop deleting your files from android file host, sick of broken links
Click to expand...
Click to collapse
I would use the 64bit twrp in the link below
It's not treble but then there's no stable treble roms for this device anyway (which is probably why this twrp is not maintained)
The following 64bit twrp will work with all 64bit custom roms
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Treble version works good in XT 1670 (2GB 32GB). Some laggy gui, but good. Ty for your hard work!
He.Art said:
Treble version works good in XT 1670 (2GB 32GB). Some laggy gui, but good. Ty for your hard work!
Click to expand...
Click to collapse
If you want an never version use Jarl's TWRP - it works perfectly fine except if you encrypt backups (not the same as backing up encrypted data)

[RECOVERY] - [UNOFFICIAL] TWRP gauguin - Dhollmen

Disclaimer:
The use and installation of this software product is at the exclusive responsibility of the user.​I am not responsible for any damage that may occur to your device resulting from the use of this software.​This software product is "as is". Its first goal is to allow the xiaomi.eu Rom be installed via recovery.​If you have any doubts regarding the above lines, you should not use or install it.​​
Recovery:
Unofficial release 3.7.0 for Xiaomi Mi 10T Lite and Redmi Note 9 Pro 5G devices. ​​Status : Stable​Version : 3.7.0.4G​Release Date : 2022.12.26​​​Features:
​Android 12 decryption​Android 13 decryption (Not tested by myself)​Flashing​Adb​Otg (Not tested by myself)​Mtp​Backup / Restore to / from microSD​Backup / Restore through adb​Sideload​Device boot Logo changer​Magisk tools and theme from @ Brigudav (Not tested by myself)​
Notes:
I concluded that custom roms (without Miui) are unable to decrypt /data with this recovery.​Checking LineageOS and ArrowOS, it seems that they use a different encryption mode than Miui.​I haven't found how to check on Twrp booting what encryption mode /data uses and adjust to it.​Therefore, I have uploaded another release for non Miui devices.​Can't tested by myself, I don't know if it decrypts fine.​However, it is likely the Miui variant will work correctly on the rest.​
About official TWRP: ​The current official release https://twrp.me/xiaomi/xiaomimi10i.html does not work anymore since Miui 13. Use instead this TWRP.​
Twrp not decryping on miui 14: Please, read this post​
Downloads:
Last release from Xda (Post #2)​
Older releases from androidfilehost​
Release 3.7.0.3F for CUSTOM NOT Miui rom from Xda (Post #2) ​​
Installation:
Updating this Twrp release:​​Downloaded to phone:​​Click on Install and locate the .zip file.​​Downloaded to PC (no need to copy it to the phone):​​ On phone: ​start install via ADB (sideload).​ On PC execute: ​adb sideload file_name.zip​
Try without installing: (does not alter the phone unless you want to do)​​Extract recovery.img from .zip file downloaded​Enter fastboot mode.​Execute: ​fastboot boot recovery.img​
Installing this for the first time:​
Your bootloader must be open.​ Extract recovery.img from downloaded .zip file.​ Enter fastboot mode​ Execute: ​fastboot flash recovery recovery.img​​​​​Credits:
​Team Win Recovery​Minimal Manifest Platform​Alexander Brigudav​
Latest release 3.7.0.4G for MIUI rom
Release 3.7.0.3F for CUSTOM Non Miui rom
Nice work
Flashed R2 release, but it doesn't decrypt my data (it doesn't ask about my PIN). I am Polish xiaomi.eu translator and tester, and will ask Xiaomi.eu team about recovery ROM if the storage is decrypted... but can't for now...
Also, I was unable to boot to system after flash that TWRP, I had to use OrangeFox to be able to boot.
kacskrz said:
Flashed R2 release, but it doesn't decrypt my data (it doesn't ask about my PIN). I am Polish xiaomi.eu translator and tester, and will ask Xiaomi.eu team about recovery ROM if the storage is decrypted... but can't for now...
Also, I was unable to boot to system after flash that TWRP, I had to use OrangeFox to be able to boot.
Click to expand...
Click to collapse
Hello. I'm Spanish xiaomi.eu translator and user.
I don't understand how is possible your issue...
When I boot TWRP it asks me for the PIN to decrypt.
I would not have uploaded the image without testing it first.
Also the reboot buttons do what they say..
I have so far tested it without installing, because I have not yet dumped the Stock Recovery partition.
In theory, it is supposed to work exactly the same in boot mode as in flash mode.
Can you try it without installing?
As stated in the third disclaimer lines:
"Its intention is to allow the Rom xiaomi.eu be installed via recovery."
I retired here due to lack of free time and have only become involved now for this reason.
Best regards
tuxafgmur said:
Can you try it without installing?
Click to expand...
Click to collapse
Same situation, unfortunately... (except the reboot button which boots system, as i've just booted recovery, not flashed).
Edit: removed all screen lock methods I've set, still same. Looks like it isn't able to decrypt my data even without screen lock... Maybe something works differently between beta (which I use) and stable (which you use) release?
Edit2: logs there with set PIN as screen lock method https://miuipolska.pl/d/Orjon/gauguin_twrp.zip
Edit 3 24.07. 9:00am CEST: reboot to system works fine now after flashing your recovery, maybe the fact i've used "fastboot reboot-recovery" command was the reason to fail before...
kacskrz said:
Same situation, unfortunately... (except the reboot button which boots system, as i've just booted recovery, not flashed).
Edit: removed all screen lock methods I've set, still same. Looks like it isn't able to decrypt my data even without screen lock... Maybe something works differently between beta (which I use) and stable (which you use) release?
Edit2: logs there with set PIN as screen lock method https://miuipolska.pl/d/Orjon/gauguin_twrp.zip
Click to expand...
Click to collapse
Your logs do not seem to give relevant information about the issue.
It is clear that booting are completely ignoring the security lockout..
During the night I dumped and unpacked the stock recovery.
After studying it, I found nothing significant except that the kernel is not exactly the same as in boot.img.
I'm now downloading the latest weekly release to unpack it and compare vs stable release.
kacskrz said:
Edit 3 24.07. 9:00am CEST: reboot to system works fine now after flashing your recovery, maybe the fact i've used "fastboot reboot-recovery" command was the reason to fail before...
Click to expand...
Click to collapse
I'm not sure I understand what this paragraph means..
Regards.
Pixel Experience 12 data decrypted successfully.
Thanks
Lineage os data decrypted successfully.
Unfortunately, the weekly xiaomi.eu does not decipher the date.
For @kacskrz , @nolan2112 and anyone else using weekly xiaomi.eu:
I would appreciate the test of the new Release 3 I just uploaded.
Thanks in advance.
@tuxafgmur Unfortunately, nothing changed. I've posted logs on the xiaomi.eu thread.
The latest version also cannot decode the date. firmware weekly 22.7.21
New release 3.6.2.1B uploaded
In addition to some other minor changes,
fixed decryption on xiaomi.eu weekly.
New release 3.6.2.1B-R2 uploaded
No relevant changes.
Tested to flash xiaomi.eu from storage and sideload.
tuxafgmur said:
New release 3.6.2.1B-R2 uploaded
No relevant changes.
Click to expand...
Click to collapse
Everything is fine, the recovery is fully working. Thanks Amigo!
New release 3.6.2.1B-R3 uploaded
Revision
New release 3.6.2.1C uploaded
Format: Zip file to install from TWRP.
Some reviews.
Since xiaomi.eu rom replaces boot Logo on global devices, showing "Redmi"
this release includes options to switch logo between "MI" and "Redmi".
Each has two versions to choose from:
1 - Factory stock.​2 - Like stock but hiding the padlock shown when bootloader is open.​​
The only recovery that works (and decrypts) on the newest MIUI 13 Android 12. Thank you!
Fantastic work, congratulations!

Categories

Resources