Hi Everyone,
Just wondering if there has been any update about custom recoveries for pixel 6. I've been checking the TWRP website and what not but there no info on the subject that I can see.
Just curious to know if anyone else has heard anything about custom recoveries yet
I asked about on one Telegram, I think that TWRP is out-of-date for newest Android version (main dev is on hiatus)
Newrooter22 said:
Hi Everyone,
Just wondering if there has been any update about custom recoveries for pixel 6. I've been checking the TWRP website and what not but there no info on the subject that I can see.
Just curious to know if anyone else has heard anything about custom recoveries yet
Click to expand...
Click to collapse
TWRP for Android 11 only came out in late 2021. It should come soon for 12. No ETAs obviously but they have a chat here: https://rebrand.ly/teamwin-recovery-zulip-community and make announcements here: https://twrp.me/
Thanks guys, it's good to know that it might still be a while away hopefully not too long. It does have some good features so fingers crossed it's sooner rather than later.
TWRP has been dead for the Pixels for over two years.
You need to learn adb and fastboot if want to mod the Pixels.
If you are lazy, you can use this program to do what TWRP can do,
📳🔥PixelFlasher for Google Pixel 6 Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
nutzcase said:
TWRP has been dead for the Pixels for over two years.
You need to learn adb and fastboot if want to mod the Pixels.
If you are lazy, you can use this program to do what TWRP can do,
📳🔥PixelFlasher for Google Pixel 6 Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
Click to expand...
Click to collapse
Got any recomendations for getting shell access on a phone that doesn't boot normally? That's about the only use I have for twrp, its ability to be fastboot booted without an install.
adamf663b said:
Got any recomendations for getting shell access on a phone that doesn't boot normally? That's about the only use I have for twrp, its ability to be fastboot booted without an install.
Click to expand...
Click to collapse
adb reboot bootloader
fastboot boot boot.img (I think that's the syntax but if not then fastboot help will show you)
bobbarker2 said:
adb reboot bootloader
fastboot boot boot.img (I think that's the syntax but if not then fastboot help will show you)
Click to expand...
Click to collapse
That won't help on a system that has boot issues.
there was a custom recovery ( lineage recovery i think) that came with a custom rom. i was reading about the rom a few weeks back(forget where), but the developer would not release the recovery separately.
so really there is no reason why TWRP or some other custom recovery could not be developed.
but with the lack of roms on XDA and limited custom roms elsewhere, i feel that the pixel 6 will have very very little support.
nutzfreelance said:
there was a custom recovery ( lineage recovery i think) that came with a custom rom. i was reading about the rom a few weeks back(forget where), but the developer would not release the recovery separately.
so really there is no reason why TWRP or some other custom recovery could not be developed.
but with the lack of roms on XDA and limited custom roms elsewhere, i feel that the pixel 6 will have very very little support.
Click to expand...
Click to collapse
Statixos or staticos , something like that.
nutzcase said:
TWRP has been dead for the Pixels for over two years.
You need to learn adb and fastboot if want to mod the Pixels.
If you are lazy, you can use this program to do what TWRP can do,
📳🔥PixelFlasher for Google Pixel 6 Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
Click to expand...
Click to collapse
Only thing I ever really used it for was a nandroid
I have a question that is probably really stupid. Twrp and other custom recoveries allow installing custom roms, staticos and the like are out. How do they do it without a custom recovery?
alarmdude9 said:
I have a question that is probably really stupid. Twrp and other custom recoveries allow installing custom roms, staticos and the like are out. How do they do it without a custom recovery?
Click to expand...
Click to collapse
You push it as a zip file on fastboot. They're is dotos, deep, statixos, grapheneos, protons, crdroid etc for device
So basically bypassing the recovery altogether.
twrp lets you flash your device without needing a pc.
not to mention backup , on device formatting. amoung very many other useful tools
nutzfreelance said:
twrp lets you flash your device without needing a pc.
not to mention backup , on device formatting. amoung very many other useful tools
Click to expand...
Click to collapse
The feature I miss most is adb and having access to the decrypted file system. Decryption was always a problem for twrp; I used to unset my phone unlock method to get around that.
nutzfreelance said:
twrp lets you flash your device without needing a pc.
not to mention backup , on device formatting. amoung very many other useful tools
Click to expand...
Click to collapse
I miss having the ability to do a complegte image of your phone. Comes in handy when you get stuck in a boot loop and have to do a factory reset. Is there any other program that can do a full backup like TWRP?
I really do not see the need for a backup of andoid on the Pixel 6.
Backup your data.
There are several ways now days to restore the Pixel 6 with Android 12 and above.
adb and fastboot are your friends.
Kernel manager apps have a flash tool built into them.
vandyman said:
I really do not see the need for a backup of andoid on the Pixel 6.
Backup your data.
There are several ways now days to restore the Pixel 6 with Android 12 and above.
adb and fastboot are your friends.
Kernel manager apps have a flash tool built into them.
Click to expand...
Click to collapse
none of the ways you mention are possible with only a pixel6 and nothing else.
i cant tell you how many time when i was away for vacation or on a trip where i have flashed a rom on my S7. even a few times when some new software borked my phone and i could boot to recovery and RECOVER my device.
you can go to the custom kernel posts here and look at how many people have soft bricked their phone in April with a bad kernel. with a TWRP recovery they could have flashed a backup and never left their chair.
how can anyone say that more tools to fix things is in anyway a bad thing.
nutzfreelance said:
none of the ways you mention are possible with only a pixel6 and nothing else.
i cant tell you how many time when i was away for vacation or on a trip where i have flashed a rom on my S7. even a few times when some new software borked my phone and i could boot to recovery and RECOVER my device.
you can go to the custom kernel posts here and look at how many people have soft bricked their phone in April with a bad kernel. with a TWRP recovery they could have flashed a backup and never left their chair.
how can anyone say that more tools to fix things is in anyway a bad thing.
Click to expand...
Click to collapse
Why would you attempt to mod your cell while on vacation?
I was referring to the general user.
Related
Don't forget to hit the thanks button.
http://superstarmobility.weebly.com/
New thread: http://forum.xda-developers.com/android/development/twrp-m1-lg-k7-t3462130.
(Above TWRP can be flashed with Flashify from Playstore)
Instructions from video:
With phone powered off, hold POWER and VOLUME DOWN buttons until LG logo shows. Release POWER then quickly press and hold again until factory reset menu comes up. Select YES and you will be booted into recovery instead of a factory reset ; )
Thanks @czarsuperstar!
V2 with the proper cmd line from m1 aka LG K7
Reserved.
This the real deal?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
Of course. You looked at the video?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
I've used it and can confirm, first tested it with fastboot without flashing of course(use adb to get to the bootloader: adb reboot bootloader , then fastboot:fastboot boot "twrp.img file, tested then rebooted into bootloader, then flashed via fastboot:fastboot flash "twrp.img file") instructions are for any random person that come by i know you know how to do all this
concerned xda citizen
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
The first twrp was from a htc phone. This is from lg leon lte. Same manufacturer. I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon twrp is missing the options seen on this one. Don't use it. But I'm working on cm_m1 so continue to use the old one and when your phone can't come on have fun getting in recovery. Make it better.
Recovery log
Make a log.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
Check out the LG L70 it's the same way to get in recovery. This must be your first LG phone.
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Go spam the other thread. Over 200 downloads and no problems but there was problems right away with the first version. For your info download Twrp c50 from the Twrp site examine it and ask why it's incomplete. That's why I linked the video of the Twrp from the site and same problems. Bye and leave me be. Hd2 check it out. Czarsuperstar's HTC HD2 android custom roms. Check it out and leave me alone. Thanks for your concern. Oh and for your info we have the same keyboard configuration as the LG Leon. There's a device tree. Google it. Google is your friend bro.
NASSTYROME said:
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Click to expand...
Click to collapse
not saying a official twrp isn't preferable, but man you got to learn how to talk to people, you were just short of cursing the dude out, and as far as the recovery the thing is solid(tested backup, flash and restore/ anyhow we got LGUP if you **** up so its not a huge deal), but anyone on this site shouldn't take someones word for things like recovery's and you should always test boot before you flash, also you don't seem to understand the first rule of xda-whatever happens to your device is on you, been that way since the og day's- talking politely to others is the way to go about things, people wont listen if you combative.
Kernel
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Didn't work, after selecting yes twice, my phone just starts like normal, doesn't go to TWRP or factory restore, it is there though because I can boot to it from the flashify app, ah well.
wait...my bad, I was highlighting the wrong one, lol, works great, thanks
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
callihn said:
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
Click to expand...
Click to collapse
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
[email protected] said:
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
Click to expand...
Click to collapse
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
callihn said:
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
Click to expand...
Click to collapse
I'm working on building it from source but keep getting errors and I'm trying it with another device that has Twrp (Moto E 2015) and followed the directions to the T and no luck. So I am trying......... Will let everyone know how it's going.
[email protected] said:
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Click to expand...
Click to collapse
kernel??????????????????????????
im down!
UPDATED 2/19/2018
Almost enough here to start attempting debug builds... any other builders/devs out there working on this device? Hopefully some of this will be useful.
Minimal Omni device tree for TWRP (full lineage branch in progress as of 2/19/2018)
https://github.com/mightysween/android_device_motorola_payton
Proprietary blobs/vendor (initial push 2/19/2018):
https://github.com/mightysween/android_vendor_motorola_payton
Partition names/locations/mounts...maybe a few missing still:
https://docs.google.com/document/d/1EkPOkc8uUStKIjRGC2-4jkcXpxmj8v3piGPqZi9ctQM/edit?usp=drivesdk
7.1 KERNEL SOURCE:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/7.1.1-nougat-release-payton
8.0 KERNEL SOURCE:
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OPW27.57-40
So what's the deal with the A/B partitions? I've seen that there are some lineage OS commits to handle the A/B partitions. Would it be possible to load an OS to the A partition and put the recovery on the B partition. I'm not familiar enough to know how much control of the boot process we can have with boot time commands. Does the bootloader have a boot to recovery option?
There doesn't seem to be a recovery partition in the list that you provided. I wonder what the fastboot commands look like... just thinking out loud on the internet. I don't have the phone yet, but I did have a look at Best Buy, so that practically makes me an expert. I have a N5X, so I'm lining up the successor for after its sudden, but inevitable betrayal.
gee one said:
So what's the deal with the A/B partitions? I've seen that there are some lineage OS commits to handle the A/B partitions. Would it be possible to load an OS to the A partition and put the recovery on the B partition. I'm not familiar enough to know how much control of the boot process we can have with boot time commands. Does the bootloader have a boot to recovery option?
There doesn't seem to be a recovery partition in the list that you provided. I wonder what the fastboot commands look like... just thinking out loud on the internet. I don't have the phone yet, but I did have a look at Best Buy, so that practically makes me an expert. I have a N5X, so I'm lining up the successor for after its sudden, but inevitable betrayal.
Click to expand...
Click to collapse
There is no traditional recovery partition...handled by boot. A/B is mainly to allow 'seamless' updates (as in OTA that downloads to the other partition for instant reboot). Bit more to it... if you want to read more, check out the Pixel forums.
Well... progress is being made. Wish there were others (there must be!) working on this.
I have the stock kernel, a VERY basic device tree, and cobbled-together vendor... syncing repos and will try to compile TWRP over the weekend. I do not expect it to work
Dealing with this right now on brunch...runs fine up until this point, appreciate any thoughts:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/mightysween/android/omni/out/target/product/payton/obj/SHARED_LIBRARIES/libcryptfs_hw_intermediates/export_includes', needed by '/home/mightysween/android/omni/out/target/product/payton/obj/SHARED_LIBRARIES/libcryptfslollipop_intermediates/import_includes', missing and no known rule to make it
build/core/ninja.mk:157: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Click to expand...
Click to collapse
Do I really need the lollipop libs???? Especially if I just want to compile TWRP and not full omni. Ahhhhhhh....so much fun
OK, got TWRP to compile
Need to do some testing in the emulator and double and triple check all sources and configs before even thinking about trying to boot it on the actual device.
But just troubleshooting at this point, so looking good for TWRP in coming days!
UPDATE: oops, totally compiled it with the wrong kernel. Haha... working through some defconfig issues, but hopefully nothing too crazy.
mightysween said:
OK, got TWRP to compile
Need to do some testing in the emulator and double and triple check all sources and configs before even thinking about trying to boot it on the actual device.
But just troubleshooting at this point, so looking good for TWRP in coming days!
Click to expand...
Click to collapse
I hope you can do it! Is the first step to get backups and ROMs. I don´t have the phone yet, but later the normal version that is sell in México and want to flash the Android One version (previously anyone get it working).
I'm returning my Amazon version of this phone and getting Project Fi version. I am willing to help in testing.
Well, my boot.img compiles fine... but will not boot to recovery. Given the fact that it is mostly guesswork on the device tree, I am not shocked.
Pushed my working tree to GitHub and will keep working on it...
https://github.com/mightysween/android_device_motorola_payton
Been looking at Pixel 2 TWRP Alpha... holy cow. So much more to it with this partitioning scheme.
mightysween said:
Well, my boot.img compiles fine... but will not boot to recovery. Given the fact that it is mostly guesswork on the device tree, I am not shocked.
Pushed my working tree to GitHub and will keep working on it...
https://github.com/mightysween/android_device_motorola_payton
Been looking at Pixel 2 TWRP Alpha... holy cow. So much more to it with this partitioning scheme.
Click to expand...
Click to collapse
Have not even peeked into the Pixel 2 forums. I'm afraid this seems to be another ballgame entirely. Do the new Pixel owners even have root passing safety net while allowing these security updates new android phones now get? Gah this is a mess
SR3TLAW said:
Have not even peeked into the Pixel 2 forums. I'm afraid this seems to be another ballgame entirely. Do the new Pixel owners even have root passing safety net while allowing these security updates new android phones now get? Gah this is a mess
Click to expand...
Click to collapse
TWRP has been worked on for Pixel2 by several people, including expert Dees Troy, and is still a heavy alpha. I feel pretty good about booting compiled boot images and not bricking on x4 (as far as I have gotten)
I have been compiling my own stuff for many years, and yes -- this new stuff is foreign. But, we will all learn and in a few weeks/months, there will be plenty of action on this device
mightysween said:
TWRP has been worked on for Pixel2 by several people, including expert Dees Troy, and is still a heavy alpha. I feel pretty good about booting compiled boot images and not bricking on x4 (as far as I have gotten)
I have been compiling my own stuff for many years, and yes -- this new stuff is foreign. But, we will all learn and in a few weeks/months, there will be plenty of action on this device
Click to expand...
Click to collapse
try using fixes from https://github.com/TeamWin/android_device_xiaomi_tissot tree. similar android one device!!
i.snehal.kiran said:
try using fixes from https://github.com/TeamWin/android_device_xiaomi_tissot tree. similar android one device!!
Click to expand...
Click to collapse
Thanks, picked up 3 changes from here already... will test them out soon!
So, I have checked out several XDA threads on this Xiaomi device (tissot) and I think it is going to help quite a bit with the A/B issues.
I am still, unfortunately stuck on getting TWRP to boot. Boot.img compiles fine and I can extract it and see TWRP has replaced stock recovery in the ramdisk, but it will not boot into recovery.
Ideally, we need a way to boot a TWRP image without flashing anything... easier said than done with devices that have recovery baked into the boot image. But once that works, we can extract just the ramdisk from my build and write a script to patch it into the stock boot image from the temporary TWRP running on the device.
Progress! New TWRP thread coming soon...
BTW, there is still a long way to go here... this was just a rudimentary test to get TWRP to boot. Need to start totally fresh with partitions before there is any attempt to actually use it!
Also -- my build environment is a total cluster after weeks of messing around. I need to wipe it and start over. That alone will take me a few days, and TWRP might take a few weeks more.
Incredible! Looking forward to having a custom recovery!
mightysween said:
Progress! New TWRP thread coming soon...
BTW, there is still a long way to go here... this was just a rudimentary test to get TWRP to boot. Need to start totally fresh with partitions before there is any attempt to actually use it!
Also -- my build environment is a total cluster after weeks of messing around. I need to wipe it and start over. That alone will take me a few days, and TWRP might take a few weeks more.
Click to expand...
Click to collapse
I hope later we can flash the Android One firmware on the retail Moto X4, I supose that OTA update will not work but at least we will have the lastest updates if someone make a flashable version
f3r.and0 said:
I hope later we can flash the Android One firmware on the retail Moto X4, I supose that OTA update will not work but at least we will have the lastest updates if someone make a flashable version
Click to expand...
Click to collapse
At the very least, we have the ability to create "nandroid" style backup from A1 device. Theoretically, that could allow anyone to install it...
But yes, in the long run, hopefully the actual firmware is released
mightysween said:
At the very least, we have the ability to create "nandroid" style backup from A1 device. Theoretically, that could allow anyone to install it...
But yes, in the long run, hopefully the actual firmware is released
Click to expand...
Click to collapse
Doesn't the nandroid (or for that matter Flashfire) backup contain personally unique identifiers?
DiDGR8 said:
Doesn't the nandroid (or for that matter Flashfire) backup contain personally unique identifiers?
Click to expand...
Click to collapse
Yes, technically... obviously would need to start with a fresh system and limit to non-data partitions.
No one needs to restore someone else's apps... just their boot/oem/system_image
mightysween said:
Yes, technically... obviously would need to start with a fresh system and limit to non-data partitions.
No one needs to restore someone else's apps... just their boot/oem/system_image
Click to expand...
Click to collapse
This just came to my mind, since this phone has 2 partitions for boot etc. --
Code:
mmcblk0p44: boot_a SIZE:65536 blocks
mmcblk0p45: boot_b
can't we make backup of boot_b ? it will be same as boot_a but unmodified i think ? i mean, use magisk/cf-autoroot/whatever to gain root on boot_a. and make backup of boot_b. so in case if we want to receive update, just restore back boot_b.img to boot_a slot and update through ota ? that way we can practically make full backup which is unmodified. ofc this is until we have fastboot image available and working TWRP.
also it seems all x4's are having same kernel according to this thread. although their build time is different.
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1......
Click to expand...
Click to collapse
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
I'm also looking for that. But if I can get TWRP on it I'd probably try SU.
How did you get to install the TWRP? I found a few posts but was apprehensive about whether I can use SPFT to flash original stock ROM if things go wrong. I suppose that would be the easiest way.
For what I paid for the phone, it's a decent enough device.
Using SD card as internal memory always result in the total capacity being reported wrongly..256GB becomes 512GB with 50% occupied, 200GB becomes 256GB with 64GB occupied. Still waiting for their tech support to reply but unlikely they would.
Cheers!
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Ibuprophen said:
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thanks for the input I will have a read.
Charlie-Boy said:
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Click to expand...
Click to collapse
Thanks for the info.
Cheers!
chooks06 said:
Thanks for the info.
Cheers!
Click to expand...
Click to collapse
No problem.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
abhijeet715 said:
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
Click to expand...
Click to collapse
Code:
https://www.needrom.com/download/twrp-armox-x/
There are other places listed on Google.
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Charlie, could share how you got the TWRP working?
Have been fiddling around until battery showed -1%.. Had to go back to stock.
Thanks mate!
Choo ks
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Follow the guide here. I did it a few times before success as I followed a guide from another site.
https://www.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
Click to expand...
Click to collapse
I think I installed magisk using this method, clearing dalvik and cache.
https://www.stupdroid.com/2018/02/magisk-16.0-download.html
Click to expand...
Click to collapse
Charlie-Boy said:
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Click to expand...
Click to collapse
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Charlie-Boy said:
Follow the guide here. I did it a few times before success as I followed a guide from another site.
I think I installed magisk using this method, clearing dalvik and cache.
Click to expand...
Click to collapse
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
You ignore the password and change the language to English from Russian. Just don't enter a password at all. The recovery won't stick as Android replaces it when you reboot. After you've completed other steps maybe OEM unlocking then it stays, or so I read somewhere.
chooks06 said:
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
Click to expand...
Click to collapse
All of them are encrypted by default now. The password in TWRP should be ignored and just change the language and select storage etc.
abhijeet715 said:
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Click to expand...
Click to collapse
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Charlie-Boy said:
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Click to expand...
Click to collapse
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
abhijeet715 said:
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
Click to expand...
Click to collapse
Mine is the same encryption is enabled. I select external SD storage and I am shown the contents using the same procedure as yourself, I cannot tell you why this is so. I am using the same technique, same phone, same settings, same TWRP, maybe we have different SD card?
That is all I can think of by way of an explanation. It works perfectly for me. I also made a backup which I can select and restore without a problem.
I have been looking into rooting my N20 with twrp, but I found no support for this device on the teamwin website. I have unlocked the bootloader and was looking for the entry but it isn't there. Are there any alternatives or other routes I can take? Thanks.
Yeah just flash your boot img with magisk and then just boot to fastboot and flash boot.img and disable vbmeta..
DrScrad said:
Yeah just flash your boot img with magisk and then just boot to fastboot and flash boot.img and disable vbmeta..
Click to expand...
Click to collapse
Will try, thanks for the reply.
Devs r working on it now but the Oscar TWRP can be used temporarily if you just have to have TWRP before it's finished but take this into consideration that it won't work perfectly because it's for the CE2 lite which is the euro sister to the N20. I recommend copying your stock boot image to your inactive slot and flashing the Oscar TWRP to the active slot and use TWRP for whatever u need it for then change slots in TWRP to get back to system... This is a temporary workaround.. there's an app you can download to switch slots from Android too but you need the bootctl magisk mod
PsYk0n4uT said:
Devs r working on it now but the Oscar TWRP can be used temporarily if you just have to have TWRP before it's finished but take this into consideration that it won't work perfectly because it's for the CE2 lite which is the euro sister to the N20. I recommend copying your stock boot image to your inactive slot and flashing the Oscar TWRP to the active slot and use TWRP for whatever u need it for then change slots in TWRP to get back to system... This is a temporary workaround.. there's an app you can download to switch slots from Android too but you need the bootctl magisk mod
Click to expand...
Click to collapse
Is there any way to see progress updates on that or is there a way to use Oscar TWRP as normal recovery (don't feel very good about not having custom recovery available in case something goes wrong).
Toothless_NEO said:
Is there any way to see progress updates on that or is there a way to use Oscar TWRP as normal recovery (don't feel very good about not having custom recovery available in case something goes wrong).
Click to expand...
Click to collapse
well u would have to search for the TG group. im not allowed to post links to it here any more. mods delete or censor my posts if i do even though i always ask that anyone getting live help in TG post their problem and solution here if they get help... idk lol.... as soon as its finished it will get posted in a new thread though. everything works except booting to system with twrp in ramdisk so we are trying to get some device specific things swapped out and testing as we go. i dont see it being much longer now that we have some more help.
PsYk0n4uT said:
well u would have to search for the TG group. im not allowed to post links to it here any more. mods delete or censor my posts if i do even though i always ask that anyone getting live help in TG post their problem and solution here if they get help... idk lol.... as soon as its finished it will get posted in a new thread though. everything works except booting to system with twrp in ramdisk so we are trying to get some device specific things swapped out and testing as we go. i dont see it being much longer now that we have some more help.
Click to expand...
Click to collapse
Oh I see, well that's too bad since I don't have telegram. Although it's good to hear that it might be done soon.
Toothless_NEO said:
Oh I see, well that's too bad since I don't have telegram. Although it's good to hear that it might be done soon.
Click to expand...
Click to collapse
Ok well maybe it will be longer than I thought. Nobody left whos very interested in working on it. I don't really have the time for it any more. Anyone who is interested can either copy their own boot image to the inactive slot and flash Oscar TWRP to active so magisk and such flashes correctly then switch active and boot off the inactive slot. You can use magisk bootctrl mod along with an app that switches active slot from Android to boot to TWRP without a PC and then change slots in TWRP to get back to android and always keep a good copy of ur boots image on the sdcard and never forget to flash your stock/patched boot image in TWRP to the inactive slot before rebooting if you flash anything that flashes over both slots. .....OR find Spector and others in TG or on GitHub and see if they wanna work with u to get TWRP fixed for our device... Or you can find a fork of Spector's Oscar TWRP that says experiment for N20 and you can use/experiment/continue on our efforts. Shout out to Scrad, JuiceBox, Spector, pjgowtham, the guys in CE2 liteband Nord groups, and many others who have devoted so much time to learning and working with me on this and answering so many questions and giving advice.. Shout out to PizzaG who tried his best to teach me and work on a device he has no experience with and to Eduardo for the initial attempt. Shout out to Ghetti for being Ghetti, if he ever sees this he will know what I mean. If I left anyone out I apologize but you know who you are and I thank you. Someone got me banned on TG probably related to this device and my refusal to help when people start acting like Im obligated to help them and act a monkey . so I'm done pushing anything out for it or spending any more effort on it. Good luck everyone. I may check in from time to time but I've wasted the last 7 months learning more than I ever thought I needed to know about android and OnePlus. Also just to note, the N20 experimental fork of the Oscar TWRP has the GN2200 kernel dumped from a July patched boot image along with dtbo and some other things, you can do a diff to see what got swapped out from Spector's fork if anyone wants to play with it. Everything works except booting to system in the OSCAR TWRP on the N20 and I haven't been able to try to build the TWRP I was experimenting with so I don't even know if those changes fixed it. If anyone wants to be the guinea pig and try it be my guest or if someone wants to build it and post it I will test it one of these days
PsYk0n4uT said:
Devs r working on it now but the Oscar TWRP can be used temporarily if you just have to have TWRP before it's finished but take this into consideration that it won't work perfectly because it's for the CE2 lite which is the euro sister to the N20. I recommend copying your stock boot image to your inactive slot and flashing the Oscar TWRP to the active slot and use TWRP for whatever u need it for then change slots in TWRP to get back to system... This is a temporary workaround.. there's an app you can download to switch slots from Android too but you need the bootctl magisk mod
Click to expand...
Click to collapse
Oscar sadly even when used on your non acrtive partition has limitations that a device specific TWRP will hopefully address.
ScarletWizard said:
I am going to learn to port TWRP
Click to expand...
Click to collapse
It does seem a fun undertaking the TWRP site and various posts give a general overview on adding it to a new device.
elzeekador said:
I have been looking into rooting my N20 with twrp, but I found no support for this device on the teamwin website. I have unlocked the bootloader and was looking for the entry but it isn't there. Are there any alternatives or other routes I can take? Thanks.
Click to expand...
Click to collapse
How did you unlock your bootloader?
jayram1408 said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
unlock token - OnePlus (United States)
www.oneplus.com
I have my bootloader unlocked.
I've downloaded the AOSP 13 Borneo Monthly Build.
I used
Code:
fastboot -w update .\aosp_borneo-img-Feb-Week4.zip
to install it. I don't have GApps now (as expected).
I've tried NUMEROUS things, but I always end up back to having to reinstall AOSP 13. And all the posts are almost 1-2 years old so outdated information. I tried to use the TWRP Android 11 based, but I of course got an error of "Cannot mount /data" despite no matter what I've done.
Is there any way to get GApps on the ASOP 13 build? I don't care about a custom rom and my phone has been wiped numerous times multiple different ways over the last our, so losing data (not that I did) isn't a problem.
EDIT: I don't mind if it's A11 or A12, A13 would be nice if possible. But I'd just like ASOP with GApps. Though I couldn't even find where the ASOP A11 and A12 builds for this phone would be (if there is any).
Try flashing BitGapps through TWRP and see if it works
traman124 said:
Try flashing BitGapps through TWRP and see if it works
Click to expand...
Click to collapse
I actually just install AOSP 13 and then flashed the Pixel Experience system image.
I've been doing this for like 8 hours of trial and error. I think what was confusing me most of the time was I didn't realize that you use fastboot in Bootloader and in fastboot. But you can only run certain fastboot commands in bootloader and only some in Fastboot mode. Which took me quite a bit to realize. Which means I would run a fastboot command in something like bootloader and it was meant for fastboot mode so it'd give me random errors that no one else got because they apparently knew the difference.
But that was confusing lol
EDIT: WELL ****E, NOW THE KEYBOARD DOESN'T WORK.
You didn't say that you wanted a PE GSI in the original post.
Also that was confusing for me the first time too (and moreso with the TCL Revvl 4)
traman124 said:
You didn't say that you wanted a PE GSI in the original post.
Also that was confusing for me the first time too (and moreso with the TCL Revvl 4)
Click to expand...
Click to collapse
Well I attempted PE GSI because there's no TWRP for AOSP 13 for this phone, the latest is A11 and that won't mount /data/
As well as the TWRP you listed doesn't work with my touchscreen and the other one avail doesn't do decryption.
There’s an SHRP build with decryption support for your phone… Would that work?
traman124 said:
There’s an SHRP build with decryption support for your phone… Would that work?
Click to expand...
Click to collapse
I've tried that myself, and decryption doesn't seem to be any better than twrp. That and it doesnt read AOSP 13 /data anyway. I've had the same problem trying to get gapps, even MagiskGapps doesn't seem to work. Is there a gapps package that can be flashed via fastboot maybe?
Not as far as I know... I’m sorry I can‘t help much further
ErraticFox said:
I actually just install AOSP 13 and then flashed the Pixel Experience system image.
I've been doing this for like 8 hours of trial and error. I think what was confusing me most of the time was I didn't realize that you use fastboot in Bootloader and in fastboot. But you can only run certain fastboot commands in bootloader and only some in Fastboot mode. Which took me quite a bit to realize. Which means I would run a fastboot command in something like bootloader and it was meant for fastboot mode so it'd give me random errors that no one else got because they apparently knew the difference.
But that was confusing lol
EDIT: WELL ****E, NOW THE KEYBOARD DOESN'T WORK.
Click to expand...
Click to collapse
Mind if I ask what you mean by "pixel experience system image"? Are you talking about the PE GSI?
Yes he means the GSI.
So. This works and you end with aosp 13 and gapps? For those of us with zero adb experience, is there a step by step on how to do this?
graewulf1 said:
So. This works and you end with aosp 13 and gapps? For those of us with zero adb experience, is there a step by step on how to do this?
Click to expand...
Click to collapse
I'm not sure how to get gapps, but you can flash aosp with fastboot update aosp.zip (replace aosp with the aosp file name). Just power off your phone, then power on while holding the volume down key to boot into the bootloader and perform this command.
LethalGamer2121 said:
I'm not sure how to get gapps, but you can flash aosp with fastboot update aosp.zip (replace aosp with the aosp file name). Just power off your phone, then power on while holding the volume down key to boot into the bootloader and perform this command.
Click to expand...
Click to collapse
right, i get that. i need to load gapps as well, i have too many paid apps there to not use it. since there is no TWRP for android 13, I need to figure out how to flash AOSP, then Gapps before the first boot.
graewulf1 said:
right, i get that. i need to load gapps as well, i have too many paid apps there to not use it. since there is no TWRP for android 13, I need to figure out how to flash AOSP, then Gapps before the first boot.
Click to expand...
Click to collapse
Well, let me know if you figure it out, cause i'm just as clueless about it as you are. I'm kind of suprised nobody's made a fastboot flashable gapps package yet.