Greetings,
Firstly, sorry for the noob question, but I recall that the snapshot versions of CM had their own custom recovery (CM Recovery) that could be updated via OTA together with the ROM itself for stability reasons. I haven't seen this on any other ROM and I'd like to ask if Lineage will have it's own recovery the same way CM did or not.
I particularly liked the feature because it allowed me to factory reset the phone without needing twrp (even though i'm not sure that the rom having it's own recovery has to do with being able to factory reset the same way stock roms do).
Once again, sorry for my "noobishness" and thank you to all who took their time to read this
Why not TWRP ?
We learn by asking - welcome to the club. Anyway, if there is a TWRP or Philz or an existing CM recovery for your device, why not just load one of them? I've never had a problem with the interaction between TWRP and CM, so I assume that will hold for the Lineage build(s) as well. That even includes my clumsy hacks of TWRP to get it onto unsupported devices. It seems to be remarkably robust and forgiving, and since a recovery really doesn't do a whole lot in comparison to a complete ROM, difficult to go far wrong. If there's no TWRP for you device, as long as you have the same processor there are VERY useful guides out here for porting it. The more the hardware you've got is similar to something that already works, the easier it is to do this. I frankly assumed I would brick everything I tried but so far I've been 100% successful - proof of blind luck. Oh yeah, it REALLY helps to have a stable working ROM image to revert to if your efforts to do this go South. That 100% success rate is after a few: "whew, glad I had this to go back to" moments along the way. :cyclops:
Good Luck !!
nezlek said:
We learn by asking - welcome to the club. Anyway, if there is a TWRP or Philz or an existing CM recovery for your device, why not just load one of them? I've never had a problem with the interaction between TWRP and CM, so I assume that will hold for the Lineage build(s) as well. That even includes my clumsy hacks of TWRP to get it onto unsupported devices. It seems to be remarkably robust and forgiving, and since a recovery really doesn't do a whole lot in comparison to a complete ROM, difficult to go far wrong. If there's no TWRP for you device, as long as you have the same processor there are VERY useful guides out here for porting it. The more the hardware you've got is similar to something that already works, the easier it is to do this. I frankly assumed I would brick everything I tried but so far I've been 100% successful - proof of blind luck. Oh yeah, it REALLY helps to have a stable working ROM image to revert to if your efforts to do this go South. That 100% success rate is after a few: "whew, glad I had this to go back to" moments along the way. :cyclops:
Good Luck !!
Click to expand...
Click to collapse
Actually, i have twrp on my phone and i love it, but i'm aiming to pass along this device to my elders that are not as tech sawy as i am. Só i wanted to give'em something functional, and there's where CM recovery saved me - everytime they need to factory reset their CM flashed phone they won't even need to enter bootloader to do it! I just hope it will be possible to do the same with LineageOS.
PS: i tried to do a factory reset from the settings menu with twrp on my phone and it didn't work. The phone remained exactly the same, just as if i hadn't done anything.
PS2: i know that twrp offers a factory reset option on it's menu but it would be hard to teach them how to use the recovery.
Or, if the devs intend to make a "Lineage Recovery" for whatever other reasons, i'd be curious to know them as well :good:
Thanks for the answer ?
well .....
"Actually, i have twrp on my phone and i love it, but i'm aiming to pass along this device to my elders that are not as tech sawy as i am. Só i wanted to give'em something functional, and there's where CM recovery saved me - everytime they need to factory reset their CM flashed phone they won't even need to enter bootloader to do it! I just hope it will be possible to do the same with LineageOS. "
I guess the magic question would be "how often are they going to be using it?" In the case of TWRP, the periodic (weekly or monthly) backup is about as blind simple as it can get - even I can do it without too much concentration
As for points of entry, CM / Lineage can easily be set to reboot to the recovery mode, whatever you use. It's down there in Developer Settings - piece of cake. Once done, tell TWRP to reboot to the System. a second piece, a la mode.
Good Luck.
It will be nice if Lineage produce their own recovery as CM .
In my case with Oppo R5 there isnt any recovery availaible yet to flash LineageOS
Existing TWRP and CM recoveries are useless
NO, but there are lots of options for the Honor 5X which seems to be very similar. Maybe you could port one of those? WHY, specifically, are they "useless" ?? If you would care to itemize what you tried and how they failed, maybe we could help.
nezlek said:
NO, but there are lots of options for the Honor 5X which seems to be very similar. Maybe you could port one of those? WHY, specifically, are they "useless" ?? If you would care to itemize what you tried and how they failed, maybe we could help.
Click to expand...
Click to collapse
Thanks for your response. With cm recovery we are getting signature verification failure. When we flash existing twrp recovery for our devise the phone stuck in oppo logo. Furthermore I don't have the knowledge to port recovery and our community is short of developers
Sent from my R5 using XDA-Developers Legacy app
mermigas said:
Thanks for your response. With cm recovery we are getting signature verification failure. When we flash existing twrp recovery for our devise the phone stuck in oppo logo. Furthermore I don't have the knowledge to port recovery and our community is short of developers
Sent from my R5 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Seems to be a somewhat common occurrence among octa-core devices, although I have more experience with MTK chipsets. In many cases they are still using the quad-core versions of code in their stock recoveries. Curiosity question: do you also find that the stock recovery mysteriously replaces the TWRP you just installed after it fails? Some MTK devices appear to stash a hidden copy of the stock recovery away and do this for (to) you. Not fun. :crying:
Does anyone know a custom ROM that has it's own recovery? I've been searching but haven't found anything yet.
I'm in doutbt that such rom even exists after CM got out of the picture since it was the only one that had it's own recovery..
A lineageOS specific custom recovery would be good, mainly because TWRP versions greater than 2.8 cause several banking and security apps to fail because they think the device is rooted even if its not. Many of these apps, like blackberry uem client (formerly known as GFE) falsely detect root simply because of something that TWRP has done in versions after 2.8 and this has nothing to do with unlocked bootloader flags. While lineageOS without the root addon passes safteynet now, in future it will be good if lineage has its own recovery rather than a third party recovery like TWRP.
Plus it would be nice to have one integrated system without the need to maintain/update two different pieces of software. It would just be cleaner, but that is a matter of taste.
Sent from my Nexus 9 using Tapatalk
I saw somewhere that they had plans for this but, after they've completed most/all the ROM releases.
I can't remember where I read it but, i do know that their still working on releases for more devices.
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
********************************************
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
********************************************
It is literally necessary, because recoveries depend on kernels, and currently TWRP use binary kernels in the repository (github:TeamWin/android_device_xiaomi_lithium) which may render it unusable due to kernel mismatch. Why not compile our own kernel when we have source code, and why not use the same kernel in the recovery? The best solution is to collect them together, under an unified organization.
test123321123123213 said:
It is literally necessary, because recoveries depend on kernels, and currently TWRP use binary kernels in the repository (github:TeamWin/android_device_xiaomi_lithium) which may render it unusable due to kernel mismatch. Why not compile our own kernel when we have source code, and why not use the same kernel in the recovery? The best solution is to collect them together, under an unified organization.
Click to expand...
Click to collapse
That is the dumbest thing you could imagine. Mainly when soo many different things effect the kernel. Also the kernel that you flash for the OS is not the same as what is needed in recovery.
Also cm recovery was the cause for many bricked devices. They have become more of a laughing g stock to android the miui, which is saying a lot. Many thing Los and Xiaomi should Tema up to make the ultimate joke device.
nezlek said:
We learn by asking - welcome to the club. Anyway, if there is a TWRP or Philz or an existing CM recovery for your device, why not just load one of them? I've never had a problem with the interaction between TWRP and CM, so I assume that will hold for the Lineage build(s) as well. That even includes my clumsy hacks of TWRP to get it onto unsupported devices. It seems to be remarkably robust and forgiving, and since a recovery really doesn't do a whole lot in comparison to a complete ROM, difficult to go far wrong. If there's no TWRP for you device, as long as you have the same processor there are VERY useful guides out here for porting it. The more the hardware you've got is similar to something that already works, the easier it is to do this. I frankly assumed I would brick everything I tried but so far I've been 100% successful - proof of blind luck. Oh yeah, it REALLY helps to have a stable working ROM image to revert to if your efforts to do this go South. That 100% success rate is after a few: "whew, glad I had this to go back to" moments along the way. :cyclops:
Good Luck !!
Click to expand...
Click to collapse
It sounds like you have a lot of luck in this area, I spent ages looking for a TWRP porting guide but couldn't quite find one that worked. Would you be able to get me a link to a good TWRP porting guide for a octa-core Samsung?
Cheers
Related
As topic says, is there a custom recovery available for R819 ?
I found TWRP for Chinese R819T version, but is it compatible also with the R819 ?
samusalo said:
As topic says, is there a custom recovery available for R819 ?
I found TWRP for Chinese R819T version, but is it compatible also with the R819 ?
Click to expand...
Click to collapse
Not yet. Dees_Troy is working on it now, he got an R819 a day or two ago. (Edit: oops, he doesn't have his yet, he was just working with someone else.)
I just got mine earlier today. Right now I am trying to get a complete return-to-stock package from Oppo. Yeah, I could extract everything and eventually build one myself, but it's SO much easier when the manufacturer provides it for you. Unfortunately it's the weekend and the Oppo guys are in a complete different timezone than I am. I think that was the main reason Dees_Troy is halted too - Trying to boot the image using "fastboot boot" doesn't work, and he's (understandably) nervous about flashing a recovery when he doesn't have a return-to-stock image.
Edit: FYI, motochopper works for rooting. It's a royal pain to get it working with this device on Windows machines, but on Linux, you only need to get ADB running by adding 0x22d9 to ~/.android/adb_usb.ini
Entropy512 said:
Not yet. Dees_Troy is working on it now, he got an R819 a day or two ago. (Edit: oops, he doesn't have his yet, he was just working with someone else.)
I just got mine earlier today. Right now I am trying to get a complete return-to-stock package from Oppo. Yeah, I could extract everything and eventually build one myself, but it's SO much easier when the manufacturer provides it for you. Unfortunately it's the weekend and the Oppo guys are in a complete different timezone than I am. I think that was the main reason Dees_Troy is halted too - Trying to boot the image using "fastboot boot" doesn't work, and he's (understandably) nervous about flashing a recovery when he doesn't have a return-to-stock image.
Edit: FYI, motochopper works for rooting. It's a royal pain to get it working with this device on Windows machines, but on Linux, you only need to get ADB running by adding 0x22d9 to ~/.android/adb_usb.ini
Click to expand...
Click to collapse
What about Kernel SOurces and Other Trees ?
GuneetAtwal said:
What about Kernel SOurces and Other Trees ?
Click to expand...
Click to collapse
https://github.com/oppo-source/R819-Kernel-Source-4.2
MediaTek's kernel build system gives me a headache... It's a mess. Also, there are some nasty licensing conflicts between various files there. It's better than no source at all, but there are some issues a few of us are in contact with Oppo to resolve. (Oppo has been EXTREMELY cooperative so far.)
The biggest problem is that right now fastboot won't allow you to flash or boot any kernel images, whether normal boot or recovery. This means that if you hose up a device by flashing a bad recovery or kernel, you've got a brick. Supposedly Oppo is also working on fixing this too.
I successfully wrote a test TWRP image that Dees_Troy provided me, but I'm not going to make it public for the following reasons:
1) MTK's dumchar driver used to read/write kernel and recovery partitions does not do any size enforcement. Backing up a kernel in recovery will result in a 4GB backup image at the moment... I've figured out how to fix the driver, however:
2) Being unable to recover from bricks using fastboot means that this thing is extremely dangerous
3) The fstab is probably still not right for the device
The biggest blocker is 2) above - once that's resolved it should be a matter of only a few days.
Edit: I was partially wrong. It's not possible to flash recovery from fastboot, but you can flash replacement boot images.
Entropy512 said:
https://github.com/oppo-source/R819-Kernel-Source-4.2
MediaTek's kernel build system gives me a headache... It's a mess. Also, there are some nasty licensing conflicts between various files there. It's better than no source at all, but there are some issues a few of us are in contact with Oppo to resolve. (Oppo has been EXTREMELY cooperative so far.)
The biggest problem is that right now fastboot won't allow you to flash or boot any kernel images, whether normal boot or recovery. This means that if you hose up a device by flashing a bad recovery or kernel, you've got a brick. Supposedly Oppo is also working on fixing this too.
I successfully wrote a test TWRP image that Dees_Troy provided me, but I'm not going to make it public for the following reasons:
1) MTK's dumchar driver used to read/write kernel and recovery partitions does not do any size enforcement. Backing up a kernel in recovery will result in a 4GB backup image at the moment... I've figured out how to fix the driver, however:
2) Being unable to recover from bricks using fastboot means that this thing is extremely dangerous
3) The fstab is probably still not right for the device
The biggest blocker is 2) above - once that's resolved it should be a matter of only a few days.
Edit: I was partially wrong. It's not possible to flash recovery from fastboot, but you can flash replacement boot images.
Click to expand...
Click to collapse
WEll it is same as Xperia C's Source and other Leaked Source :/ i Don't know why Mediatek don't make a Simple Filesystem like that of Nvidea and Qualcomm
i think it comes with cwm right,thats what a developer told me:fingers-crossed:
Zpik said:
i think it comes with cwm right,thats what a developer told me:fingers-crossed:
Click to expand...
Click to collapse
No, it does not. Stock Android "3e" recovery.
There's a TWRP image nearly ready, but who knows when it will be fully ready for public consumption. I won't be working on it (or anything else) at all this week for various reasons.
Unofficial CWM 6.0.2.8 & TWRP 2.6.1.0 for HTC Desire 300 (g3u)
device_htc_g3u v0.77b (05/10/14)
fixed double buffering for twrp
(graphics.c tamed once more, still with 0% overscan involved)
device_htc_g3u v0.77b (25/9/14)
rearranged entries in recovery.fstab
(to speed up manual mounting via recovery menu)
fixed sideload's driver log spam
(errors are only surpressed but it should do the trick)
fixed ext-sd log spam
(blinkfeed-data repurposed as ext-sd)
device_htc_g3u v0.7b (28/8/14)
fixed double buffering
(graphics.c tamed with 0% overscan involved)
fixed stability issues
(cwm's ueventd.rc was evil and a worthy foe)
Full Disclosure
This is my first android project, so go easy on me.
Project Status CWM
Main Features are working.
Backup,Wipe,Restore,Install,ADB,USB-MS,USB-SL
(Tested by factory resetting my device, installing CM10 and reverting back to my backup)
Project Status TWRP
It's still completly untested. So please let me know if everything works as expected.
(Since it's based on the same boardconfig as cwm chances are very high that it'll work fine)
TODO
[CWM] md5 check is slow (by design? missing crypto mods?) [no priority]
Disclaimer
Use at you own risk.
I can not be held accountable for any damage you might cause to your device if you decide to flash this file.
Installation
Your mission, if you choose to accept it, is to infiltrate the bootloader and meet the contact fastboot.
Initiate a conversation by saying fastboot flash recovery recovery.img and wait for his response.
End the conversation with fastboot reboot-bootloader and navigate to the exfiltration point recovery.
Special Thanks
go out to whoever actually fixed the framebuffer issue by teaching minui how to properly align the frames for double buffering.
device_htc_g3u
kernel_htc_g3u
Branch: Android 4.1.2
Version: 3.4.0-g12f638f
Config: g3u_defconfig
Toolchain: arm-eabi-4.6
Click to expand...
Click to collapse
compiled by 4m8
(When I think of Maureen I think of two things: asphalt... and trouble.)
Make it flashable throughout CWM? also, is it possible to load backups i made with PhilZ CWM v.6.0.3.7 ?
I have no clue if they work. but knowing that philz is just a variation of cwm and the backups should be just misnamed tar archives.
I guess they could. It's worth a try.
Worst thing that can happen is that it won't boot until you restore a different backup you hopefully made before you started such an attempt
I simply flashed your recovery now and I#M now making a Backup with yours
Your Recovery is already better bc it doesnt have this annoying bug with the jumping screen
Is it possible to upgrade new CWM through old PhilZ CWM v.6.0.3.7 or I have to use ADB?
You have to use adb (fastboot)
luxb said:
You have to use adb (fastboot)
Click to expand...
Click to collapse
Thanks for info.
TWRP is now available but I didn't have the time to fully test it.
Please let me know if everything is working fine.
Also I've yet to find out how to pack recoverys as flashable zips as it was requested, so I guess you'll still need fastboot to get it running.
This shouldn't be that big of a deal since I'm not updating the recoverys that often anyways.
GUYS
I thought this might help you sooner or later.
Due to my expedition into the lands of an unrestorable backup with mismatching md5sums, I conquered this tool
https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore&hl=de
it can halp you in mainly 2 ways
regenrating md5sums (just in case something goes wrong like in my case, you'll need it)
Convert TWRP backups into CWM backups and Vice Versa
this is actually really neat, as you dont have to switch between both recoveries anymore
This is a Freemium app, means not all features are free, but the available features in the free version are good enough, the Premium features are Nice to have
hope i can help
Guys, is TWRP tested now, is it working properly?
junk031 said:
Guys, is TWRP tested now, is it working properly?
Click to expand...
Click to collapse
That's exactly what I should be asking, oh wait, I already did in the OP.
Looks like no one has reported any problems so I guess you could say it works without problems.
I have not tested restore so far. But it can install my rom via sideload and it's able to start aromafm, that much is certain.
So, where can i find a stock recovery img? I want to go back full stock before i hand down the mobile.
once again, source?
Crazy good
Installed on my Desire 301s
my reaction is
WHAT?
TWRP has a touch GUI
WHAT?
TWRP does not ANNOYINGLY start when I stick a usb cable into it while it's turned off
unlike what stupid CWM used to do
WHAT?
This is AWESOME
:good:
qwerty123443 said:
once again, source?
Click to expand...
Click to collapse
yeah, we need the source for rebuild our CM...
Hello Community,
I am new here and would like to install a custom rom onto my Note 10.1 2014 Wifi Only.
The main reason why I want to do that is because I would like to use of the side button of the S-Pen in my apps (mainly Squid). Is that possible?
If so, where do I start? I would like to try this ROM is it appropriate for my needs?
Code:
[lt03wifi][P600][ROM][CM13.0][6.0.1]Temasek's UNOFFICIAL Builds [Almost Daily]
I previously tried to root my device but i guess that failed. So now I cant do any updates anymore. I think I also tried to Install TWRP but when I boot to recovery it gives me the standard Android system recovery telling me it couldnt mount /data/. Is that a problem? And what TWRP will I need to install the latest ROM?
This is whats on my device:
Model: SM P600
Android version: 4.4.2
Kernel Version 3.4.29.2612580
Buildnumber: KOT49H.P600XXUCNH3
Thank you for reading my post and thanks in advance,
Crackm4n
Hi, I cant really help you, other than to suggest you try posting in another forum, this one does not seem very helpful, Ive posted problems here and have not really found much help. You may get some help from here below, they are very friendly and very helpful and a few really really smart people with great information. Good Luck!
forums.androidcentral.com/samsung-galaxy-note-10-1-2014/
Hi and welcome,
I'm not sure what it is you're looking for with the side button? Generally, the implementation of the s-pen is a bit more complete in Samsung's own Touchwiz ROMs. You can get a decent experience with the s-pen in ROMs like the temasek ROM you posted, but you won't get all the functions you have in Touchwiz (and you might to have to install some extra apps).
The info about TWRP should be in the thread for @joshndroid's temasek ROM that you refer to, including the appropriate downloads. Not sure what happened to your /data partition, but if you can still boot into Touchwiz, you should be fine and could just flash TWRP again.
So I can just take the latest TWRP and flash it? The Samsung ROM just catches the signal of the sidebutton before any app can fetch it. Im looking for a way to make that accessible because some apps use the button but these functions never work.
crackm4n said:
So I can just take the latest TWRP and flash it? The Samsung ROM just catches the signal of the sidebutton before any app can fetch it. Im looking for a way to make that accessible because some apps use the button but these functions never work.
Click to expand...
Click to collapse
Yes, I would think so. You just need to find the proper format for Odin, I think that's tar.md5 if I remember correctly? At some point the newer TWRP versions were only available as img, but in that case you can flash a slightly older version (I think 2.8.6 was definitely working) and then flash the newer version directly from TWRP.
If the Samsung specific functions of the spen are interfering with what you want to do, AOSP or CM ROMs should indeed solve your problem, as they don't have those Samsung features. There are some apps to get some of that working, but if you essentially want to get rid of these functions in favour of your other apps, I suspect you should be fine.
So I've read enough posts to get this first - GLOBAL ONLY I got my phone on Amazon its a global unlocked NOTE8PRO. Any of you with something else like China or India try this method and brick your phone don't cry to me over it. After trial and error, bricking my device and paying some guy in Spain 30EUR to unbrick it (thanks brother you rock) I thought I'd share my final experience and how you can get your GLOBAL RN8P to a stable place to install the ROMS available at this time. I will include at the end my thoughts on the 2 ROMS I installed and used over the past week. Honestly if you're on a global version I'm not sure it's worth it although as I type this I kinda want to flash Pixel Experience again, I really liked it. But more on that later. I compiled this guide from sources here, if I don't give you credit I apologize in advance please just let me know.
First let's make sure we don't brick this mofo.
Hit the MEGA thread if you haven't read it then you shouldn't be flashing your phone, and do this from a clean install of MIUI-V11.0.6.0PGGMIXM and do yourself a favor and get it from Xiaomi or a reliable source, not everyone on here has good intentions. There are some "official" ROMS out there that have been played with and will break your phone.
1. Do it how you want I did this from fastboot. Dump the official MIUI global ROM in a folder, and (I'm on linux box so adjust yourself if you're sadly using Windows) I executed this command from FASTBOOT in the MIUI ROM folder with ADB and FASTBOOT installed for my system.
./flash_all.sh (I think its flash_all.bat for Windows)
This going to wipe your stuff out, have it backed up. I'm dedicated to Google and GDRIVE I don't care I get everything back when I wipe including sms and phone records etc, but to each his own.
It's going to wipe and restore to factory image on that ROM version and you're going to go throught setup again, tedious (I say that having done it 4 times this week) but none the less it is what it is. After you are up and running on that ROM version keeping in mind if you're going to flash a new ROM like PE then don't set it up all the way because you're going to do it all over again anyways move to the next step.
2. From the MEGA thread flash this and reboot. Read the thread download the files and do what Agent_fabulous (awesome guy btw) says. Reboot. Make sure you can reboot to SYSTEM and all is well, don't worry about recovery or bootloader yet.
Code:
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash lk2 lk.img
3. OK kids we're almost there, now you need to install TWRP and there are MANY versions floating around. Honestly the official version sucks IMHO. go to this thread and download TWRP and do exactly what it says in the thread. Assuming you're device is unlocked already and if its not then come back later follow EXACTLY steps 2 and 3. From there you will update MAGISK after the reboot and be fully rooted and pass SaftyNet checks.
You are stable and rooted. All you do next is enjoy your rooted device and or install a custom ROM. If you do install a custom ROM - READ READ READ and FOLLOW directions I hate to add to the confusuion but there are so many threads on this phone (becasue it sucks to MOD it) and it's frustrating because all of it assumes you know everything or they just don't give you all the steps and you end up bricking your phone. I have never by the way rooted or flashed a phone in my life before this one.
At this time all the custom ROMS need to be flashed after flashing the Indian Vendor image, this is in fact the only way I know and it worked for me everytime. So at this point if you're flashing a new ROM first flash the India Vendor image then flash the new from all from TWRP. But in my experience just follow what it says because Agent_fabulous and friends may crack this tomorrow and it won't be the same. What I am giving you is a VERY stable platform to start flashing ROMS from or just to be rooted and happy. As an FYI from this you can install RIRU and EdXposed if you want to do that, I wasn't impressed other than dark mode in GMail on A9 and ad-blocking in YouTube, I get the ads in YouTube but Google no dark mode in GMail on A9? WTF??
Happy rooting and ROMing.
DC.
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Auerox said:
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Click to expand...
Click to collapse
Given how aggressive the battery optimizer is on stock, I doubt you'll get more juice out of it.
Auerox said:
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Click to expand...
Click to collapse
It's fine to flash ROMs I felt PE was way faster the audio was better over Bluetooth and it was pretty stable. Battery improvement was negligible.
@dcindallas glad you had such a nice experience. have you tried flashing miui 12 on it? seems there are some beta versions for it. seems to bring a lot of eye candy, privacy and performance fixes. give it a go.
@dcindallas hi, can you please add a portion for updating miui rom through twrp (when new version available) the procedure. thanks.
I've not flashed anything but custom ROMS I had to wipe go back to A9 stock ROM due to Pixel Experience dropping wifi constantly.
Well, I appreciate all the effort going into this thread and this device. Thru all the reading I've done on this simple project with different advice, it almost seems there's too much info on it. Anyway, I'm having a dickens of a time with it, just getting it to load up TWRP! I thought I followed all the directions.. y'know... hold this button, dont hold this one, release this one, then repress that one... but I got a bootloop just from flashing TWRP. I had to re-flash the whole MIUI (an older one even) with Mi Flash, the only one I could find that had a flash-all script in it.
I'm a little gun shy, but I'd sure like to give it a go again.
I flashed twrp-3.3.1-0-begonia.img, then rebooted. Any advice why I bootlooped? Was it the TWRP version or did I mess up the button press?
Cheers
I am grateful and I bought this because next tk Samsung s22 yktra this phone is definitely #2 in my opinion, which is saying a lot.
However the root process is tedious because I am not around a computer I am just lazy to get ito do flashing etc.
My question is, why do. We not have a a real recovery and ability to back up and restore various roms we or flash zips senselessly.
So my question is (since I just bought this) do you guys rhibj we will have to dastboir flash everything or at least much harder then with cwmod or twrp recovery. Is it not possible to have a recovery like those on t his phone?
Is there a better phone in the us that is unlockaable but has the quality like this phone and screen or the Samsung s22 yktra phone?
Thanks
Without a PC you can't run fastboot commands to unlock bootloader and root it. Twrp isn't available for stock a12, let alone the upcoming release of a13
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
I don't think that you will find too many phones from the primary companies (Google, Samsung, etc) nowadays that will have TWRP builds. As time progresses, the technology (and what is available) progresses as well.
jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
This is the most recent news about Android 12 compatibility for TWRP:
TWRP 3.6.2 Released
TWRP 3.6.2 is out now for most currently supported devices.
twrp.me
We are continuing work on Android 12. There is no ETA currently. You can follow our status on Zulip
Click to expand...
Click to collapse
Disclaimer: I am not advocating signing up for "Zulip", and I won't be doing so myself. When/if TWRP for Android 12 becomes available, I'll hear about it whether I sign up on there or not. It's also likely Android 13 will be stable by then.
Supposedly, the Official TWRP App (not itself updated since 2020) will notify when there's a new version - but I don't know if that applies to when there's no current version of TWRP Recovery already installed.
The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.
96carboard said:
The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.
Click to expand...
Click to collapse
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have
Pixel devices do not have a recovery partition; recovery lives in /boot with the kernel, as well as whatever patches you've applied. Currently, TWRP and Magisk cannot coincide for whatever reason. You can patch a boot image with TWRP, and it'll work AFAIK....but if you try to patch it with Magisk too, you'll get a boot loop.
Because we have full fastboot access, there's not really any need for TWRP. You can dump and backup partition contents using fastboot, but it's tedious.
jgrimberg1979 said:
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have.
Click to expand...
Click to collapse
ADP, Nexus, and Pixel devices have NEVER needed a recovery to function fully. This goes right back to the first Android phone in 2008. So nothing really has changed in this respect. Its mostly the "other" brands that need a recovery to work around various restrictions.
Backups can be taken from within the main OS, and restored similarly, and this is actually much preferred since the backup can be stored to a remote location such as a self-hosted Nextcloud server. You can look into seedvault (integrated solution) and neobackup (root solution).
Since Android 11 you cannot have TWRP and Magisk installed at the same time or it will lead to a bootloop. However, you can fastboot boot TWRP (without installing it) and have Magisk installed without getting into a bootloop. At least this is the way it was on Android 11 with the Pixel 2 XL.
Haven't used TWRP in a long time and don't miss it at all, to be honest.