Related
Mount USB storage does not work with CWM. Will sort out soon... maybe...
First thing.
Question | Answer
Click to expand...
Click to collapse
Users:
Q: Why not make 2 separate posts?
A1: Normally I'd say "I Didn't feel like it", but its more like "I didn't see the need to."
A2: You all should be adult enough to say which you're using if problems arise.
Q: Why label beta.
A: Cause testing is really needed and I don't count myself as a test.
Q: What works?
A: Flashing, USB mount, wiping.... you know recovery stuff....
Developers:
Q: We've been trying and havent been able to get usb mounting to work... How did you?
A1: I didnt really... I figured the problem didnt come from any of the setup used to build the recovery... but the recovery kernel itself.
A2: I used the stable CWM5504, pulled the kernel from that and used the prebuilt kernel in place of building from source. Hopefully a real genius *cough*kornyone*cough* hits the nail *IF* he ever has spare time. PS thanks to xmcwildchild's stable.
Now your toys!
Click to expand...
Click to collapse
Clockworkmod 6.0.4.6 (MD5: 9d37a1029b9f5e79bbef8cb55632e7d7)
Team Win Recovery Project 2.6.3.0 (MD5: 2a227d0607e10892e7d5e15d0d3a4625)
Team Win Recovery Project 2.6.3.0 w/ DumLock (MD5: f3af450c43c03d790f8e1241a60d6efc)
TWRP Update info @ http://teamw.in/project/twrp2
Backups (there are some changes in future roms that made it problematic to flash with older recoveries, noobie kieranmenor reported a problem not being able to flash older roms with the current TWRP.)
Clockworkmod 6.0.3.6
Team Win Recovery Project 2.6.3.0
Team Win Recovery Project 2.6.3.0 w/ DumLock
Typical disclaimers apply. Good luck.
Downloading twrp now. Any difference between this and riyals version?
mattlowry said:
Downloading twrp now. Any difference between this and riyals version?
Click to expand...
Click to collapse
Aside from being the latest, I dont think so. I didnt even remember about Riyal's until you mentioned it otherwise I may have just not done it at all.
ahh yes thanks for making these! i contacted riyal about twrp 2.3, he said he didn't know it was out of beta and that he would look into it (and then i think his phone died?) and now you picked it up! will test and let you know how it goes.
btw does it have offline charging? i remember riyal made an offline charging version of his twrp
---------- Post added at 02:29 PM ---------- Previous post was at 02:23 PM ----------
for those who want to flash this but don't know how, here are instructions (from an old recovery thread by xmc_wildchild22
From Terminal Emulator
su
dd if=/sdcard/RECOVERY.img of=/dev/block/mmcblk0p21
reboot recovery
From ADB
adb reboot bootloader
fastboot flash recovery RECOVERY.img
fastboot reboot
where "RECOVERY.img" is the respective name of the recovery you want to flash
anitgandhi said:
ahh yes thanks for making these! i contacted riyal about twrp 2.3, he said he didn't know it was out of beta and that he would look into it (and then i think his phone died?) and now you picked it up! will test and let you know how it goes.
btw does it have offline charging? i remember riyal made an offline charging version of his twrp
Click to expand...
Click to collapse
No, it does what the phone normally does. Orange blinking light where you cant do squat til you take it off the charger.
I also dont know how he did it, and... may not be able to add it myself. :/
SilverL said:
First thing.
Users:
Q: Why not make 2 separate posts?
A1: Normally I'd say "I Didn't feel like it", but its more like "I didn't see the need to."
A2: You all should be adult enough to say which you're using if problems arise.
Q: Why label beta.
A: Cause testing is really needed and I don't count myself as a test.
Q: What works?
A: Flashing, USB mount, wiping.... you know recovery stuff....
Developers:
Q: We've been trying and havent been able to get usb mounting to work... How did you?
A1: I didnt really... I figured the problem didnt come from any of the setup used to build the recovery... but the recovery kernel itself.
A2: I used the stable CWM5504, pulled the kernel from that and used the prebuilt kernel in place of building from source. Hopefully a real genius *cough*kornyone*cough* hits the nail *IF* he ever has spare time.
Clockworkmod 6.0.2.7
Team Win Recovery Project 2.3.3.0
Typical disclaimers apply. Good luck.
Click to expand...
Click to collapse
What are the technical benefits/detractions (pluses/minuses) of these compared to CWM 5.5.0.4 or 5.0.2.7?
Fuzi0719 said:
What are the technical benefits/detractions (pluses/minuses) of these compared to CWM 5.5.0.4 or 5.0.2.7?
Click to expand...
Click to collapse
Aside from reading somewhere that the newer versions of android(4.2+) will require a recovery update.
Also saw it here too.
Both of these recoveries have installing from sideload, ability to delete backups from within the recovery, higher version numbers(always means better -_-) and some other minor things.
TWRP you can name backups immediately. Full touch interface, extremely theme-able. Works well with GooManager. Queue multiple zips.
CWM has another backup type option dedupe(not a fan of it). Looks better...
Essentially about as technical as going from ICS to JB and JB to new JB. -_-
post the boardconfig.mk you used with this, let me see if you're missing any flags
xmc wildchild22 said:
post the boardconfig.mk you used with this, let me see if you're missing any flags
Click to expand...
Click to collapse
Its the default one on TeamDS. Minor changes because I had to use that prebuild kernel. Its currently a mess. What do you think would be missing? Have you encountered any problems?
SilverL said:
Its the default one on TeamDS. Minor changes because I had to use that prebuild kernel. Its currently a mess. What do you think would be missing? Have you encountered any problems?
Click to expand...
Click to collapse
When I turned on the theme prom and the emulate processes or something like that in twrp I had problems flaking a rom I even rebooted the recovery so I turned that option off then my roms flash again
Sent from my MyTouch 4G Slide using xda premium
butch87402 said:
When I turned on the theme prom and the emulate processes or something like that in twrp I had problems flaking a rom I even rebooted the recovery so I turned that option off then my roms flash again
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Exact options would be helpful...
Anyway. If you turned on a theme and the simulate actions for theme testing.
Then I assume the simulate options is what caused the not problem you had.
Before you start creating a custom theme, you should tap on settings and tap the checkbox for "Simulate most actions for theme testing" to enable simualation mode. This setting will cause TWRP to simulate most actions including installing zips, backup, restore, partitioning sdcards, etc. In this mode you can safely test a theme without wearing out the memory chips on your device. There's also a checkbox for simulating failure that will appear on the settings page when you turn on simulation mode. This checkbox will cause TWRP to report a failure for all simulated actions instead of success so that you can provide the appropriate message on the screen. Don't forget to disable simulation mode when you're done!
Click to expand...
Click to collapse
- Source
SilverL said:
Aside from reading somewhere that the newer versions of android(4.2+) will require a recovery update.
Also saw it here too.
Both of these recoveries have installing from sideload, ability to delete backups from within the recovery, higher version numbers(always means better -_-) and some other minor things.
TWRP you can name backups immediately. Full touch interface, extremely theme-able. Works well with GooManager. Queue multiple zips.
CWM has another backup type option dedupe(not a fan of it). Looks better...
Essentially about as technical as going from ICS to JB and JB to new JB. -_-
Click to expand...
Click to collapse
Is the new CWM or TWRP compatible with the backups done with CWM 5.5.0.4/5.0.2.7? All of my nandroid backups are done with 5.5.0.4.
Fuzi0719 said:
Is the new CWM or TWRP compatible with the backups done with CWM 5.5.0.4/5.0.2.7? All of my nandroid backups are done with 5.5.0.4.
Click to expand...
Click to collapse
TWRP is not compatible with CWM and vice versa. The CWM backups should still be compatible. One way to test is to flash, see what happens if it doesnt work... go back? Doesnt kill. I did it when testing and swapped between TWRP and CWM and back to old 5.5.0.4 then back to these again. Now I'm on TWRP, hopefully permanently.
Flashed TWRP and immediately backed up my CM9 nightly without a problem. Mounted USB storage and transferred over a new ROM, went back and forth to bootloader since I'm S-ON, no problem. This recovery doesn't feel beta to me, in a good way. I haven't tried restoring from my backup yet but I'm not worried. I got spoiled using 4EXT on my old phone and going back to CWM never felt right. This TWRP is definitely a step in the right direction. Being able to boot into bootloader from recovery is awesome from a S-ON standpoint. No more waiting to power off and then restart holding buttons or screwing it up and having to remove my case for a batpull. Full touch support speaks for itself.
Thanks so much for getting us a new recovery option. This is the biggest update for our device in a while :good:
aawillma said:
Flashed TWRP and immediately backed up my CM9 nightly without a problem. Mounted USB storage and transferred over a new ROM, went back and forth to bootloader since I'm S-ON, no problem. This recovery doesn't feel beta to me, in a good way. I haven't tried restoring from my backup yet but I'm not worried. I got spoiled using 4EXT on my old phone and going back to CWM never felt right. This TWRP is definitely a step in the right direction. Being able to boot into bootloader from recovery is awesome from a S-ON standpoint. No more waiting to power off and then restart holding buttons or screwing it up and having to remove my case for a batpull. Full touch support speaks for itself.
Thanks so much for getting us a new recovery option. This is the biggest update for our device in a while :good:
Click to expand...
Click to collapse
Overall they should be stable, I listed them as beta because I cannot account my successes as testing. I would like to see a few more pages before classifying as stable.
I'd also like to possibly build them completely from source at some point too.
@SilverL
I just noticed your thread and I'm glad you saved me time updating my TWRP recovery. I lost all the source code of my previous twrp and was frustrated porting it again from scratch Downloading it now...
By the way the offline charging version of my TWRP is here
http://forum.xda-developers.com/attachment.php?attachmentid=1374782&d=1349346744
just extract the ramdisk and you should see the workaround I made. There's no additional binary added. The offline charging I made is just pure shell script and edits on the rc files so it should be pretty easy for you.
Regarding a full compile use a CM7 kernel and add the doubleshot board files and drivers and you should be good to go. Also I used the boardconfig of MT4G(non slide).
Anyways the boardconfig isn't the issue but the kernel. The USB driver of ICS isn't compatible with twrp and that's the issue. Even Dees_Troy couldn't even make a build with fully working USB on CM9
Riyal said:
@SilverL
I just noticed your thread and I'm glad you saved me time updating my TWRP recovery. I lost all the source code of my previous twrp and was frustrated porting it again from scratch Downloading it now...
By the way the offline charging version of my TWRP is here
http://forum.xda-developers.com/attachment.php?attachmentid=1374782&d=1349346744
just extract the ramdisk and you should see the workaround I made. There's no additional binary added. The offline charging I made is just pure shell script and edits on the rc files so it should be pretty easy for you.
Regarding a full compile use a CM7 kernel and add the doubleshot board files and drivers and you should be good to go. Also I used the boardconfig of MT4G(non slide).
Anyways the boardconfig isn't the issue but the kernel. The USB driver of ICS isn't compatible with twrp and that's the issue. Even Dees_Troy couldn't even make a build with fully working USB on CM9
Click to expand...
Click to collapse
Thanks, I figured it needed a gb kernel to do its thing. Especially after I realize the android usb kernel driver is also responsible for adb(which didnt work either). Also its not just with twrp, it affects cwm as well. Both of these use the exact same kernel.
If getting an old kernel if required then I wont even worry about it. I'll just keep my CM10 build environment the way it is just in case I have to update these in the future. I will also check out the shell script and the rc edit. Thanks, if you want to take twrp back its all yours.
to be more specific it's this one
init.rc
service detect_charge /sbin/detect_charge
oneshot
Click to expand...
Click to collapse
and on
/sbin/detect_charge
#!/sbin/sh
if [ `cat /sys/class/power_supply/battery/charging_enabled` = '1' ]
then
start offmode_charging
else
start recovery
fi
kill -9 $$
Click to expand...
Click to collapse
Can't do anything as of the moment since I don't have any working MT4GS at hand. Also I have lots of different projects planned so I might leave twrp to you as it is here.
Riyal said:
to be more specific it's this one
init.rc
and on
/sbin/detect_charge
Can't do anything as of the moment since I don't have any working MT4GS at hand. Also I have lots of different projects planned so I might leave twrp to you as it is here.
Click to expand...
Click to collapse
I'll try to throw this in for the guys that want it....
And since no one has complained(except for that one guy who couldnt flash because he put his phone in the 'feature' to simulate those events rather than actually do them) or died. I'll consider these stable.
Might also have to add my usual, "I am a jerk. Will laugh at you if you do something dumb, etc." disclaimer to this as well since.... most people dont know that I am. -_-
Flashed CWM 6!!!
everything is fine
however, transfering titanium backup files from pc to microsd class 10 is kinda of slow when i mounted it as usb storage inside the recovery
and
thank you for your good work. What's next? CWM touch?
For the sake of discussion, y'all ever see Tassadar's Multirom making a comeback ever? It was the absolute coolest thing ever!
That said, the new way Android works most likely killed this off entirely. A/B partitions that share userdata, and encryption that locks you out of your phone unless the security patch at least matches. Kinda hate the new way Android works to be honest.
If you remove encryption and AVB/Verity shouldnt it still work?
virtyx said:
If you remove encryption and AVB/Verity shouldnt it still work?
Click to expand...
Click to collapse
See now you got me thinking... Since Multirom mounts the userdata as system and then isolates the userdata for secondaries, it should right? Although people who have removed encryption on these newer devices have said you can't even have a screen lock or fingerprint at all with encryption gone, that's a big trade off. Hmm...
H4X0R46 said:
See now you got me thinking... Since Multirom mounts the userdata as system and then isolates the userdata for secondaries, it should right? Although people who have removed encryption on these newer devices have said you can't even have a screen lock or fingerprint at all with encryption gone, that's a big trade off. Hmm...
Click to expand...
Click to collapse
Hello, so what do you think is a good thing or a bad thing?
Personally, I'm a little afraid about that
H4X0R46 said:
See now you got me thinking... Since Multirom mounts the userdata as system and then isolates the userdata for secondaries, it should right? Although people who have removed encryption on these newer devices have said you can't even have a screen lock or fingerprint at all with encryption gone, that's a big trade off. Hmm...
Click to expand...
Click to collapse
On my pixel 3, removing encryption wouldn't let me use a pin or finger print to unlock, so no gpay.
On my 7 pro I tested out removing encryption and everything still worked perfectly, even removed Verity/ AVB too, fingerprint and pin worked fine.
I think the reason it didn't work on my pixel 3 is the Titan chip - but I'm unsure.
virtyx said:
On my pixel 3, removing encryption wouldn't let me use a pin or finger print to unlock, so no gpay.
On my 7 pro I tested out removing encryption and everything still worked perfectly, even removed Verity/ AVB too, fingerprint and pin worked fine.
I think the reason it didn't work on my pixel 3 is the Titan chip - but I'm unsure.
Click to expand...
Click to collapse
So you were able to keep your screen lock? That's neat! [emoji848] How do you remove encryption on these newer devices? I remember it used to just be a flag in the boot image, but has that changed?
H4X0R46 said:
So you were able to keep your screen lock? That's neat! [emoji848] How do you remove encryption on these newer devices? I remember it used to just be a flag in the boot image, but has that changed?
Click to expand...
Click to collapse
Firstly, you need to have twrp
Format data
Then
Make sure vendor is mounted
You need to pull the vendor/etc/fstab file to your PC
Rename "fileencryption" to "encryptable"
Then push it back to the vendor/etc location
I also make it a habit to do this before flashing magisk when unencrypted
Echo "KEEPVERITY" = false>>/data/.magisk
Echo "KEEPFORCEENCRYPT" =false>>/data/.magisk
Install magisk
And it's done.
To keep unencrypted between updates, you need to do the fstab move again in twrp and flash magisk again before first boot.
I suspect the pixels Titan chip prevents us from using a screen lock when decrypted
Which is silly, but I understand the security behind it.
virtyx said:
Firstly, you need to have twrp
Format data
Then
Make sure vendor is mounted
You need to pull the vendor/etc/fstab file to your PC
Rename "fileencryption" to "encryptable"
Then push it back to the vendor/etc location
I also make it a habit to do this before flashing magisk when unencrypted
Echo "KEEPVERITY" = false>>/data/.magisk
Echo "KEEPFORCEENCRYPT" =false>>/data/.magisk
Install magisk
And it's done.
To keep unencrypted between updates, you need to do the fstab move again in twrp and flash magisk again before first boot.
I suspect the pixels Titan chip prevents us from using a screen lock when decrypted
Which is silly, but I understand the security behind it.
Click to expand...
Click to collapse
Shoot I might just do this! I've always hated having to match the security patch when flashing a rom, or getting locked out of my phone, this might actually be better since Incan try roms and scrap em easily if I don't like em like I used to do in the older days of Android. Thanks so much! Gonna screenshot these steps and give it a go when I have time. Worst case, I restore a backup or use the MSM Tool, so no biggie! [emoji4]
H4X0R46 said:
Shoot I might just do this! I've always hated having to match the security patch when flashing a rom, or getting locked out of my phone, this might actually be better since Incan try roms and scrap em easily if I don't like em like I used to do in the older days of Android. Thanks so much! Gonna screenshot these steps and give it a go when I have time. Worst case, I restore a backup or use the MSM Tool, so no biggie! [emoji4]
Click to expand...
Click to collapse
No worries! Shoot me a PM if you have trouble
There is a noverity zip lying around somewhere but I prefer to do the steps manually gives me piece of mind.
virtyx said:
No worries! Shoot me a PM if you have trouble
There is a noverity zip lying around somewhere but I prefer to do the steps manually gives me piece of mind.
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
This is the zip you mentioned right? Since the change is made in the vendor partition, flashing a stock boot image wouldn't set it back to forced right? Or wrong?
H4X0R46 said:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
This is the zip you mentioned right? Since the change is made in the vendor partition, flashing a stock boot image wouldn't set it back to forced right? Or wrong?
Click to expand...
Click to collapse
Right, but full rom zip will revert it back
Would this possibly mean multirom would be possible?
Has anyone tried the Android 11 dp1 gsi on there Google pixel? I'm going to try later but thought would ask here 1st.
ttocs99 said:
Has anyone tried the Android 11 dp1 gsi on there Google pixel? I'm going to try later but thought would ask here 1st.
Click to expand...
Click to collapse
Yeah, I have. System partition isn't big enough for it, we'd need to resize it with like fdisk or something.
Voltz100999 said:
Yeah, I have. System partition isn't big enough for it, we'd need to resize it with like fdisk or something.
Click to expand...
Click to collapse
Besides partition resizing and flashing GSI (as described on official developer website), is there any other steps required for it to boot successfully?
I've tried flashing the smaller official GSI without GMS, but it is not booting at all. Can't figure out the cause yet.
I even repartioned my phone and can't get any GSI working. Someone did open a ticket with phhusson here however:
github.com/phhusson/treble_experimentations/issues/1161
oasisfeng said:
Besides partition resizing and flashing GSI (as described on official developer website), is there any other steps required for it to boot successfully?
I've tried flashing the smaller official GSI without GMS, but it is not booting at all. Can't figure out the cause yet.
Click to expand...
Click to collapse
Yeah no, it doesn't boot for me either, I think it might be an AVB issue but i'm not certain of that.
Voltz100999 said:
Yeah no, it doesn't boot for me either, I think it might be an AVB issue but i'm not certain of that.
Click to expand...
Click to collapse
AVB should not bother on Pixel 1 if bootloader is unlocked, especially if any custom ROM can be flashed without problem. I think it's probably SELinux-related issue, maybe set to permissive could help. (I've not tried)
oasisfeng said:
AVB should not bother on Pixel 1 if bootloader is unlocked, especially if any custom ROM can be flashed without problem. I think it's probably SELinux-related issue, maybe set to permissive could help. (I've not tried)
Click to expand...
Click to collapse
Interesting, though I don't know how we would set SELinux to permissive without booting first, maybe we'd need a kernel to set it for us? I dunno, this whole thing is really confusing.
Yeah so much for Google phones and universal treble support LOL
Pathetic
Flipz77 said:
Yeah so much for Google phones and universal treble support LOL
Pathetic
Click to expand...
Click to collapse
Can't argue with that, but it wont help us figure out how to get this working.
Clue
Here's a clue:
According to this certain audio libraries are needed to boot the quack GSI so maybe its the same for 11?
github.com/phhusson/treble_experimentations/issues/1196
xtremeed2705 said:
Here's a clue:
According to this certain audio libraries are needed to boot the quack GSI so maybe its the same for 11?
github.com/phhusson/treble_experimentations/issues/1196
Click to expand...
Click to collapse
I gave that a look and even tried it, its missing the libeffectsconfig.so file, yet I couldn't add it because /system is not mountable in twrp. We need another way.
Google has released the final build for android 11, will there be a port for the Pixel?
Deleted.
I was wondering if anyone knew about the partition schemes and whether there is enough room on the boot image to install custom recovery on the P4a?
The Pixel 3A did not have enough room on the RAM disk on the boot image. So installing TWRP, even a stripped down version compressed, on the P3a was a no-go.
Custom recovery was not necessary on the P3a. Just having and unlocked bootloader and root via Magisk gives a lot of options including custom ROMs.
However, I'm still curious if custom recovery will ever come to the P4a?
12paq said:
I was wondering if anyone knew about the partition schemes and whether there is enough room on the boot image to install custom recovery on the P4a?
The Pixel 3A did not have enough room on the RAM disk on the boot image. So installing TWRP, even a stripped down version compressed, on the P3a was a no-go.
Custom recovery was not necessary on the P3a. Just having and unlocked bootloader and root via Magisk gives a lot of options including custom ROMs.
However, I'm still curious if custom recovery will ever come to the P4a?
Click to expand...
Click to collapse
LMAO. Give it up. We're going to be on 11. Good night
Golf c said:
LMAO. Give it up. We're going to be on 11. Good night
Click to expand...
Click to collapse
Not everyone will move to 11 right away if thet can get TWRP working on A10 first.
digger16309 said:
Not everyone will move to 11 right away if thet can get TWRP working on A10 first.
Click to expand...
Click to collapse
Good luck my friend. Stay on 10
We don't even have kernel source yet..
I don't think there was twrp for a pixel for a couple years was there? Pixel 2? And that didn't get past rc I don't think.
Golf c said:
LMAO. Give it up. We're going to be on 11. Good night
Click to expand...
Click to collapse
Thanks! As I said TWRP has not been needed and I was just curious.
However I did enjoy your insecure condescending attitude. It made me LMAO.
Again, thanks! ??
dmb219 said:
I don't think there was twrp for a pixel for a couple years was there? Pixel 2? And that didn't get past rc I don't think.
Click to expand...
Click to collapse
I know, it looks like TWRP has been doing a long slow death spiral.
We have TWRP on Android 10 for the Pixel C tablet. But of course among other things, there's no A/B partitions and Google abandoned support for the device a while ago.
Might be a while, pixel 3+ devices haven't had a 100% working TWRP for a long time.
They can still sideload ROMs and patch boot images with adb/fastboot
I'll miss this moving on from my 2xl. Nice to flash and update things without needing a PC
Golf c said:
Good luck my friend. Stay on 10
Click to expand...
Click to collapse
I will until there is EdXposed for 11 + module updates.
digger16309 said:
I will until there is EdXposed for 11 + module updates.
Click to expand...
Click to collapse
Yucky
Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?
Is it at least possible to unlock the bootloader right away? Is that just standard fastboot ADB procedure or is there something Pixel specific(first one)
dpaine88 said:
Is it at least possible to unlock the bootloader right away? Is that just standard fastboot ADB procedure or is there something Pixel specific(first one)
Click to expand...
Click to collapse
Just unlocked my Pixel4a using the standard ADB commands. Will say that OEM Unlocking stayed grayed out, until I connected to my WiFi (No SIM) and let the phone connect to the mother-ship.
Archangel said:
Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?
Click to expand...
Click to collapse
yea i believe you are correct, i think same steps for the pix4 can be applied on the 4a https://www.xda-developers.com/google-pixel-4-root-magisk/
im not sure if there are other ways to get the boot img but id rather just wait for the factory images to release & mess with it then. gonna make a cronjob script to watch / notify me once its up.
renzyyy said:
yea i believe you are correct, i think same steps for the pix4 can be applied on the 4a https://www.xda-developers.com/google-pixel-4-root-magisk/
im not sure if there are other ways to get the boot img but id rather just wait for the factory images to release & mess with it then. gonna make a cronjob script to watch / notify me once its up.
Click to expand...
Click to collapse
If I get around to it this weekend, I may just do a rom dump to extract the boot.img. Haven't done it in a while. I'm still waiting for some screen protectors to arrive before I mess with my phone.
Archangel said:
Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?
Click to expand...
Click to collapse
I can't find them either.
Isn't Android 11 going to make it more difficult to hide root anymore? I am tempted to root, but heard (or read) somewhere that with android 11 that it may not be worth it as any app (or something like that) will be able to see and not work.
This is the first phone I've owned that I think I'll be satisfied with stock. Ad guard does everything I need as ad away did. And it doesn't need root. Everything is fast! Now I don't have to hack Google pay.
edufur said:
This is the first phone I've owned that I think I'll be satisfied with stock. Ad guard does everything I need as ad away did. And it doesn't need root. Everything is fast! Now I don't have to hack Google pay.
Click to expand...
Click to collapse
Curious about adguard. I just tried it and won't install with chrome as browser.
Sent from my OnePlus 5T using XDA Labs
Hi all, I hope this isn't a thread that has already been posted... I found it interesting that there is no TWRP or any custom recovery for Pixel 7/7 Pro. I understand it's not needed to flash different rom's such as Paranoid Android or Spark OS but I figure it would be helpful no? My prior device was a iPhone 12, haven't run a rooted android since my Galaxy s4 way back in the day. Is this something somebody is actively pursuing or no as it's not needed? Curious on what the situation is with this, loving my p7 pro. Cheers!
TWRP has been nearly an entire Android version behind for awhile now so I haven't been able to use it on my last couple phones. I believe it is still being worked on but since it's been so far behind due to the changes to Android and it's migration to ramdisk installation it's mostly fallen out of use sadly. I do miss it sometimes as well.
jake.99x3 said:
I figure it would be helpful no?
Click to expand...
Click to collapse
No, its useless. Pixel devices have unlocked bootloaders and support fastboot, therefore recovery is not needed.
Well, a lot of old and new Samsung phones and tablets are running TWRP and root. Yes, with Android 13. Is it strictly because there is that A and B split thing going on ? Personally I have not written to my B partition in many months if ever.
Can there be a lesson learned from that ?
96carboard said:
No, its useless. Pixel devices have unlocked bootloaders and support fastboot, therefore recovery is not needed.
Click to expand...
Click to collapse
I don't know about that. It may not be needed but the advantages are profoundly easier than having to learn terminal commands
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
JakeDHS07 said:
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
Click to expand...
Click to collapse
Exactly! I used to do a complete backup, periodically. One day I screwed something up playing around at work, went to Recover and flashed my backup. Fixed it in a few minutes
Yeah it would be nice to have for sure
Same here, a nice custom recovery would be sweet. If I had any clue how to build one I would be all over it.
JakeDHS07 said:
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
Click to expand...
Click to collapse
Is it even possible to do a nandroid backup anymore with the changes to Android filesystems and permissions? I mean you can't even flash a full firmware package in fastboot anymore, part of it has to be done from fastbootd.
old_fart said:
Well, a lot of old and new Samsung phones and tablets are running TWRP and root. Yes, with Android 13. Is it strictly because there is that A and B split thing going on ? Personally I have not written to my B partition in many months if ever.
Can there be a lesson learned from that ?
Click to expand...
Click to collapse
The A/B system is not for power users who manually flash things. It's so that updates for the 99% who use their phones normally can be done in the background. It also adds a failsafe in case one slot gets corrupted since it will automatically boot the other slot after so many failures. Previously such a failure would be an automatic brick.
Also, I think most of us power users are using the A/B system normally at this point too. You have to go out of your way to not flash an update to the other slot, all the defaults do.
HipKat said:
I don't know about that. It may not be needed but the advantages are profoundly easier than having to learn terminal commands
Click to expand...
Click to collapse
That's insane. And dangerous. When it messes up, good luck fixing it.
96carboard said:
That's insane. And dangerous. When it messes up, good luck fixing it.
Click to expand...
Click to collapse
Ummmm, what??
TWRP is a big miss for me. Nandroid Backups and phone based file explorer without having to boot to Android were just two of the numerous features I used regularly. To say it would be useless is ridiculous.
I for one would be very happy to have it make an appearance on the Pixel 7 Pro. I'm not holding my breath though, the Pixel 6 and 6 Pro still don't have it I believe.
I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"
Renate said:
I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"
Click to expand...
Click to collapse
You sure you've used it? TWRP is fully touch screen.
Beefheart said:
You sure you've used it? TWRP is fully touch screen.
Click to expand...
Click to collapse
You're right. I'm conflating stock recovery with TWRP.
I do remember big tiles and tapping on them.
Still, I prefer to keep my fingers on the (desktop) keyboard.
Renate said:
You're right. I'm conflating stock recovery with TWRP.
I do remember big tiles and tapping on them.
Still, I prefer to keep my fingers on the (desktop) keyboard.
Click to expand...
Click to collapse
I'm as much of a command line fan as the next nerd, but TWRP offers multiple features not available via ADB.
Renate said:
I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"
Click to expand...
Click to collapse
Because when you don't have a computer to connect to do a restore, for example, it's imperative to have a Recovery that does backups so you can
HipKat said:
Because when you don't have a computer to connect to do a restore, for example, it's imperative to have a Recovery that does backups so you can
Click to expand...
Click to collapse
Ok. You're doing backups to a USB flash drive? Fair enough.
But, since this thread is questioning whether any custom recovery is in development wouldn't it be helpful if someone knocked off at least a custom recovery to the extent that I mentioned?
Renate said:
Ok. You're doing backups to a USB flash drive? Fair enough.
But, since this thread is questioning whether any custom recovery is in development wouldn't it be helpful if someone knocked off at least a custom recovery to the extent that I mentioned?
Click to expand...
Click to collapse
No, doing backups to internal storage, actually. How am I going to access a USB flash drive with a telephone if I’m sitting at a friend’s house and something gets corrupted, phone won’t boot, and I have to reboot to recovery where I can access an internal back up? Which cannot be done with stock recovery.