Database Info

Best guide to start

Hi fellows^^
Coming from many years of different Nexus(es), I got bored with my Honor 10 and I am considering to switch to pocophone.
Before doing that step, I would like to check if modding pocophone would be sufficient my knowledge.
I read so far 2 guides and I have the feeling they do not flash TWRP forever, but just boot it temporary, so it comes my question, could you point me to a guide where I can start from stock to full modded (TWRP, Root, customs rom like AOSP, or Lineage or Pixel exp).
2 small spin off questions are,
is it relevant the build I start with? (Ex: do not update the phone before modding)
which rom would let me use Google Camera? (this is main thing that I am considering a pixel 3a XL instead!)
Thanks and sorry for n00b question :highfive:

phaleg said:
Hi fellows^^
Coming from many years of different Nexus(es), I got bored with my Honor 10 and I am considering to switch to pocophone.
Before doing that step, I would like to check if modding pocophone would be sufficient my knowledge.
I read so far 2 guides and I have the feeling they do not flash TWRP forever, but just boot it temporary, so it comes my question, could you point me to a guide where I can start from stock to full modded (TWRP, Root, customs rom like AOSP, or Lineage or Pixel exp).
2 small spin off questions are,
is it relevant the build I start with? (Ex: do not update the phone before modding)
which rom would let me use Google Camera? (this is main thing that I am considering a pixel 3a XL instead!)
Thanks and sorry for n00b question :highfive:
Click to expand...
Click to collapse
Hi,
This is the most detailed guide : https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
Some highlights:
1. Force encryption disabler is NOT needed. It's optional. You can act like it doesn't exist if you want.
2. Twrp official supports encryption. Make sure that your twrp supports encryption before you start.
3. The newest vendor firmware you have, the better. The needed firmware required by each rom, is the minimum.
4. Gcam is supported by all ROMs, including miui ones. So does gcam playground.
5. Some ROMs don't pass safety net without magisk, so flashing magisk is highly recommended as a rooting method.

Any updates on TWRP?

Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds

in_dmand said:
Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds
Click to expand...
Click to collapse
I was just thinking this the other day. The whole scene of Rooting and flashing ROMs seems to be coming to a dead end. Kinda sucks, I've always enjoyed tweaking my phone in my spare time..

in_dmand said:
Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds
Click to expand...
Click to collapse
Used to take 1-2 weeks when things were simple and easier.
Your comment about factory builds doesn't make sense considering you don't need TWRP to flash custom ROMs etc

Mackay53 said:
Used to take 1-2 weeks when things were simple and easier.
Your comment about factory builds doesn't make sense considering you don't need TWRP to flash custom ROMs etc
Click to expand...
Click to collapse
True, but it does seem like it has greatly hindered rom development... It wasn't until very recently there were any roms even available.

in_dmand said:
True, but it does seem like it has greatly hindered rom development... It wasn't until very recently there were any roms even available.
Click to expand...
Click to collapse
More cheaper phones will have a higher user base so more development activity.
I think Pixels already has solid software so not much to add and the high price point will hold it back a little

in_dmand said:
Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds
Click to expand...
Click to collapse
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html

Root-Maniac said:
I was just thinking this the other day. The whole scene of Rooting and flashing ROMs seems to be coming to a dead end. Kinda sucks, I've always enjoyed tweaking my phone in my spare time..
Click to expand...
Click to collapse
No we all just have to move on to next generation rooting an modding. Magisk can be flashed, or the Manager App is used to patch the boot.img manually and flash it afterwards. GSIs ROMs can be flashed via fastboot from fastboot mode as well. So in my opinion it is fastboot flashing an GSI.img, Custom (optionally Magisk patched) boot, or Stock Magisk patched boot. That's it. It's even more, as it's back to the roots of adb and fastboot. TWRP has been there on U12+ for as long as the device exists, bit I never used it, as I switched to GSIs instead, and of on Stock the Magisk ROMs of LeeDrOiD and Team Viper could be easily installed through Magisk Manager. We should all have taken a look at phhussons work much earlier to accommodate to the things that got moving by Googles change in architecture when they introduced treble. We've only been to lazy, and many of today's users on this board, hardly know anything in-depth about adb and fastboot, but only scratch the three or four superficial standard commands. Technical affinity is more in demand again, and our good old adaptability.
Sent from my Pixel 4 XL using XDA Labs

uicnren said:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Click to expand...
Click to collapse
Oh wow, thanks for posting that! I certainly don't expect dees Troy to handle that difficult of a problem by himself with his wife pregnant and everything. Thanks again

5m4r7ph0n36uru said:
No we all just have to move on to next generation rooting an modding. Magisk can be flashed, or the Manager App is used to patch the boot.img manually and flash it afterwards. GSIs ROMs can be flashed via fastboot from fastboot mode as well. So in my opinion it is fastboot flashing an GSI.img, Custom (optionally Magisk patched) boot, or Stock Magisk patched boot. That's it. It's even more, as it's back to the roots of adb and fastboot. TWRP has been there on U12+ for as long as the device exists, bit I never used it, as I switched to GSIs instead, and of on Stock the Magisk ROMs of LeeDrOiD and Team Viper could be easily installed through Magisk Manager. We should all have taken a look at phhussons work much earlier to accommodate to the things that got moving by Googles change in architecture when they introduced treble. We've only been to lazy, and many of today's users on this board, hardly know anything in-depth about adb and fastboot, but only scratch the three or four superficial standard commands. Technical affinity is more in demand again, and our good old adaptability.
Click to expand...
Click to collapse
I agree on most points of you. GSIs are wonderful especially for phones at release start when there are no custom roms available yet.
And luckily device specific custom roms can be flashed over fastboot, too.
But for one reason i want a twrp for our device:
I find data backups with twrp much more easier as without. At least on my pixel 4 xl i miss a twrp somehow because Titanium Backup doesn't work on the gsi which i'm using.
I must create all my app folders again on my phone when i update it and backup all my stuff manually on my pc in extra folders and files.
I could spare me all that with twrp.
(I know there is the Google Cloud too as possibility but i refuse to use it)

dhacke said:
I agree on most points of you. GSIs are wonderful especially for phones at release start when there are no custom roms available yet.
And luckily device specific custom roms can be flashed over fastboot, too.
But for one reason i want a twrp for our device:
I find data backups with twrp much more easier as without. At least on my pixel 4 xl i miss a twrp somehow because Titanium Backup doesn't work on the gsi which i'm using.
I must create all my app folders again on my phone when i update it and backup all my stuff manually on my pc in extra folders and files.
I could spare me all that with twrp.
(I know there is the Google Cloud too as possibility but i refuse to use it)
Click to expand...
Click to collapse
Why do you refuse to use Google cloud

ceelos218 said:
Why do you refuse to use Google cloud
Click to expand...
Click to collapse
Because i don't want to feed Big G with my data.
And GSIs give me the possibilty to use my pixel without all the Gapps and the Google Play Service. That's a reason too why i like GSIs.

dhacke said:
Because i don't want to feed Big G with my data.
And GSIs give me the possibilty to use my pixel without all the Gapps and the Google Play Service. That's a reason too why i like GSIs.
Click to expand...
Click to collapse
Privacy is an illusion unless you go completely offline.

zetsumeikuro said:
Privacy is an illusion unless you go completely offline.
Click to expand...
Click to collapse
So we should stop fighting for this? Sry but that isn't a option for me.
Yes complete privacy isn't possible mostly but there are ways to improve it. With privacy friendly services, FOSS Apps such as AfWall, AdAway and Ad and Tracking Blockers in Browsers, Linux instead if Windows and no use of Gapps etc.
I know that my comment is probably off topic so sry.

dhacke said:
So we should stop fighting for this? Sry but that isn't a option for me.
Yes complete privacy isn't possible mostly but there are ways to improve it. With privacy friendly services, FOSS Apps such as AfWall, AdAway and Ad and Tracking Blockers in Browsers, Linux instead if Windows and no use of Gapps etc.
I know that my comment is probably off topic so sry.
Click to expand...
Click to collapse
No worries man my comment was also off topic. I too used to a lot of what you currently do. Even using the magisk script Energized which does blocking of ads,trackers etc. But when I saw the sheer amount of information Google has collected even when I opted out of it, just made me realize how futile it almost all is. These companies will never be 100% transparent and honest with us since they're making money off selling our information.

zetsumeikuro said:
No worries man my comment was also off topic. I too used to a lot of what you currently do. Even using the magisk script Energized which does blocking of ads,trackers etc. But when I saw the sheer amount of information Google has collected even when I opted out of it, just made me realize how futile it almost all is. These companies will never be 100% transparent and honest with us since they're making money off selling our information.
Click to expand...
Click to collapse
I have a hobby of reversing stuff, Ive given up trying to go private. With gms code I've seen, they check for so much it's ridiculous. I think a better method for the future is us (the custom rom community) coming together to find a way to block outgoing traffic via an open source app

Surge1223 said:
I think a better method for the future is us (the custom rom community) coming together to find a way to block outgoing traffic via an open source app
Click to expand...
Click to collapse
I think we already have this with AfWall+.

I just wanted to chime in here with a tip to help fill the TWRP void that many are facing right now, especially with Android 10. You can use a manual file flashing app to do most of the same things that TWRP allows you to do, minus the recovery part, of course. You can flash all the TWRP mods you want using this method without needing a custom recovery. Just in case some people didn't know.
You can even install image files too, which means you don't need to be tethered to a computer once you get all set up. This guide should help you understand the power of manual file flashers without having to rely on TWRP for installing certain mod files.

StrifeSoldierVII said:
I just wanted to chime in here with a tip to help fill the TWRP void that many are facing right now, especially with Android 10. You can use a manual file flashing app to do most of the same things that TWRP allows you to do. You can flash all the TWRP mods you want using this method without needing a custom recovery. You can even install image files too, which means you don't need to be tethered to a computer once you get all set up. This guide should help you understand the power of manual file flashers without having to rely on TWRP.
Click to expand...
Click to collapse
It's not Just about flashing. It's about recovery. You can't use a flashing app if you are in a bootloop.

Tulsadiver said:
It's not Just about flashing. It's about recovery. You can't use a flashing app if you are in a bootloop.
Click to expand...
Click to collapse
Oh definitely! Nothing worse than a bootloop. I was just specifically talking about the flashing part. I know a lot of people have been lost without TWRP, so they aren't installing certain mods as much right now since it takes more steps without it. But you can at least do the installing part without TWRP using a file flasher. I don't think as many people are aware of this. It's handy to know. You can use it as a stop-gap until TWRP arrives for any device you want.

the backup and restore functionality of twrp is what i am missing most. just in case something goes wrong with a flash.
is there a way to backup/restore without a custom recovery?

Questions About Bootloader, Root and Roms

Looks like I'm gonna get a free P2 from my son. It maybe has 1 update left before Google abandons it. When I get it I want to root and put Lineage on it, or maybe a different rom based on opinions provided.
I have some questions:
1- I'm looking for the simplest method to unlock the bootloader and root, as I am not the most knowledgable Android/Linux user. I'm familiar with adb, although best if I can follow a written script. I would appreciate a recommendation on which method posted on XDA. I've seen Deuces and Nathanchance's methods. They seem easy enough to follow along with.
2- I'm a little confused about the Pixel factory images that folks mention in their posts. I see that Google has images catalogued on their site for downloading. How do you choose which one to flash to the phone after bootloader/root process? Does it matter? I'm located in Canada if that makes a difference.
3- I have used TWRP and never used Magisk for loading roms. I also see from one of the bootloader unlock/root methods that TWRP may not be all that reliable. Would TWRP be good enough to flash the factory image with, or should I get familiar with Magisk?
4- Am I correct in thinking that the Google image is flashed first to get the phone up and running, followed by Lineage (and gapps), or an different rom that would be flashed thereafter with TWRP/Magisk?
5- If I screw up during the unlock/root is there a recovery method available?
Thanks for any help provided.

jjcdennis said:
Looks like I'm gonna get a free P2 from my son. It maybe has 1 update left before Google abandons it. When I get it I want to root and put Lineage on it, or maybe a different rom based on opinions provided.
I have some questions:
1- I'm looking for the simplest method to unlock the bootloader and root, as I am not the most knowledgable Android/Linux user. I'm familiar with adb, although best if I can follow a written script. I would appreciate a recommendation on which method posted on XDA. I've seen Deuces and Nathanchance's methods. They seem easy enough to follow along with.
2- I'm a little confused about the Pixel factory images that folks mention in their posts. I see that Google has images catalogued on their site for downloading. How do you choose which one to flash to the phone after bootloader/root process? Does it matter? I'm located in Canada if that makes a difference.
3- I have used TWRP and never used Magisk for loading roms. I also see from one of the bootloader unlock/root methods that TWRP may not be all that reliable. Would TWRP be good enough to flash the factory image with, or should I get familiar with Magisk?
4- Am I correct in thinking that the Google image is flashed first to get the phone up and running, followed by Lineage (and gapps), or an different rom that would be flashed thereafter with TWRP/Magisk?
5- If I screw up during the unlock/root is there a recovery method available?
Thanks for any help provided.
Click to expand...
Click to collapse
Would appreciate some help...

Pixel 2 was updated to android 11, and will likely continue to to get monthly security updates until the release of android 12, so you should have about another year if staying stock.
As far as rooting, the xda guides as you mentioned are pretty straightforward and comprehensive.
Pixel factory images are the stock system images that are provided by google. They are what you would flash if you wanted to run a stock system, and also the means for 'resetting' the phone back to a factory state in the event of a screwup. On the site, you'll notice that google has each of the images organized by phone type (the Pixel 2 is walleye) and within each phone type is operating system version going from oldest at the top to newest at the bottom. Typically you'd want to flash the newest os version unless you have a special use case. There are also cases where a particular version is only for a particular carrier, in which case google will note it under the version number.
As far as flashing lineage, I'm not too sure. I run stock (rooted) on my P2, but lineage is it's own rom so would be flashed directly via twrp. I would image the lineage thread would have install instructions and q/a.

clcdev said:
Pixel 2 was updated to android 11, and will likely continue to to get monthly security updates until the release of android 12, so you should have about another year if staying stock.
As far as rooting, the xda guides as you mentioned are pretty straightforward and comprehensive.
Pixel factory images are the stock system images that are provided by google. They are what you would flash if you wanted to run a stock system, and also the means for 'resetting' the phone back to a factory state in the event of a screwup. On the site, you'll notice that google has each of the images organized by phone type (the Pixel 2 is walleye) and within each phone type is operating system version going from oldest at the top to newest at the bottom. Typically you'd want to flash the newest os version unless you have a special use case. There are also cases where a particular version is only for a particular carrier, in which case google will note it under the version number.
As far as flashing lineage, I'm not too sure. I run stock (rooted) on my P2, but lineage is it's own rom so would be flashed directly via twrp. I would image the lineage thread would have install instructions and q/a.
Click to expand...
Click to collapse
Thanks very much for the help.

Question TWRP coming?

Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup.
That said, does anyone know how long it typically takes for TWRP to be supported on a new device (i.e. G-Stylus 2021)? Just curious what the norm is. Thanks!

That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.

DM.IDOL said:
That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.
Click to expand...
Click to collapse
I'd look around on github

THIS is a TEST build for the Moto G stylus XT2115-1 minsk_t
(please mind that i have never done this before and i am at least trying to figure out how to create custom recoveries. i just need a good teacher with a little time. .)​
*Touch Screen does not work. OTG mouse necessary.*
(not too sure how to fix this error)
*Mount points were for testing*
(modied fstab files in ramdisk to fix mount points)
*modified ramdisk and split_image from Moto G 9 plus unofficial 3.5.1 twrp*
https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-g9-plus-odessa.4195729/
i tried to put a recovery together for this device but im not sure where i went wrong or what to do next. booting into this recovery works but /vendor and /system_root have denied permissions. when it is flashed within twrp and rebooted to recovery or system the screen says no OS installed press power to power off. If anyone can help me figure this one out i would be greatly appreciative. If you need anything i can pull from my device just let me know. Anyone willing to help work on this recovery and figure out what needed to be fixed i would greatly appreciate it!
*EDIT*
i got /data to back without digest verification. Was not able to try to restore the backup as i got NO OS error when i rebooted to restore.
*EDIT*
i was able to figure out pretty much everything except the touch part of the recovery. it has a novatek_ts (NVT-ts)
not sure what to do to enable the drivers for twrp. any feed back would be great.
*EDIT*
Found the driver. I'll post it here and see what you can do. I'll also work on it as I'm still learning where stuff should go in the recovery. And also seems to b that i cannot access external sd from twrp either.
*EDIT*
resolved sd card issues. mountpoint was incorrect. only thing left to get working is touchscreen and not have to use otg mouse.
updated twrp for minsk_t is in files now.
*EDIT*
I found the proper elements to configure the recovery's touchscreen capabilities. Will be recompiling later on today. After I have tested it I will post the new working TWRP recovery. Thanks everybody.

*deleted*

sosthenisRR said:
*deleted*
Click to expand...
Click to collapse
So this is fully functioning now right? Is there any reason to use this over the OrangeFox recovery that has been posted?
Also, if I did install OrangeFox, and decided I wanted to install this later, would it be as simple as flashing using fastboot from ADB, overtop of OrangeFox? Or would the procedure be a little more complex?

Unbrick OnePlus 8 5G UW [IN2019] after failed LineageOS install

I was under the impression my phone was compatible and began the install instructions for LineageOS after unlocking my phone through this guide. I flashed the two partitions, flashed the recovery, attempted to boot into recovery and it gets stuck on boot. After attempting to ask the LineageOS community I realized Verizon's version is not supported, woo. I then tried to follow the unlock guide to flash back the stock image and Msm fails on Param preload with the error "Device not match image." Googling that I only found someone implying they were using the incorrect global image, however, I know I'm not. Is it possible to recover my phone now and if so, how?

LineageOS is a base ROM for many other custom ROMs such as crDroid. Try using their recoveries and installation guides; crDroid worked perfectly in the past.

Xryphon said:
LineageOS is a base ROM for many other custom ROMs such as crDroid. Try using their recoveries and installation guides; crDroid worked perfectly in the past.
Click to expand...
Click to collapse
I'm waiting for the phone to recharge now before attempting. I feel like it will fail however as the crDroid steps require you having stock 11 on "both slots." I am too new to this scene to understand what that means or if I can even do that anymore.

rusty-op8 said:
I'm waiting for the phone to recharge now before attempting. I feel like it will fail however as the crDroid steps require you having stock 11 on "both slots." I am too new to this scene to understand what that means or if I can even do that anymore.
Click to expand...
Click to collapse
You might want to the follow this guide as a basic requirement for flashing any Custom ROM on 'instantnoodle'.
It's always good to re-read, proofread and re-read again before proceeding.

rodken said:
You might want to the follow this guide as a basic requirement for flashing any Custom ROM on 'instantnoodle'.
It's always good to re-read, proofread and re-read again before proceeding.
Click to expand...
Click to collapse
Thank you for the resource. I will attempt this instead once I can. I see that it makes a very important note about copying slot a to b to prevent potential hard-bricks. Since the "official" guide I started with did not mention that before I attempted going down this route, does this mean I'm ruined anyways? I only flashed 2 "boot" images and then the recovery image when this happened. This is all because I was using 19.1 without realizing that a) it's A12 and b) one of the maintainers said the Verizon version wasn't supported. Seeing as I can grab the last 18.1 from the link you provided me, maybe there's hope after all.

rusty-op8 said:
Thank you for the resource. I will attempt this instead once I can. I see that it makes a very important note about copying slot a to b to prevent potential hard-bricks. Since the "official" guide I started with did not mention that before I attempted going down this route, does this mean I'm ruined anyways? I only flashed 2 "boot" images and then the recovery image when this happened. This is all because I was using 19.1 without realizing that a) it's A12 and b) one of the maintainers said the Verizon version wasn't supported. Seeing as I can grab the last 18.1 from the link you provided me, maybe there's hope after all.
Click to expand...
Click to collapse
All is not lost as long as your device can power on and is not completely bricked.