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
Related
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.
l7777 said:
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.
Click to expand...
Click to collapse
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!
bluh5d said:
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!
Click to expand...
Click to collapse
The similarities are only on the surface my friend. When dealing with computers, similar and close is rarely good enough. You need exact.
bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.
evilwombat said:
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.
Click to expand...
Click to collapse
Can I root with latest supersu without recovery ?
Someone's bound to hose up their phone. Wondering where factory images are?
Born<ICs said:
Someone's bound to hose up their phone. Wondering where factory images are?
Click to expand...
Click to collapse
Yes. I agree. Might be me right. I wasn't planning on flashing recovery though just booting it.
If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.
If your bootloader is unlocked and you want root.
Try installing Chain fire's Supersu from the play store or install the apk.
I do not have my P2 yet to try.
Sent from my Nexus 5X using Tapatalk
me_droid said:
If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.
Click to expand...
Click to collapse
I think this may be a waste of time because it was modded to work on Oreo. They have already released a version that works on Oreo 3-1-1 that I already tried it wouldnt boot it. I will probably just wait even though i want to play. So i guess I can just say yep I have a pixel 2 with the bootloader unlocked and thats about it.
This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(
The_Fuzz22 said:
This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(
Click to expand...
Click to collapse
Yeah, I take having root completely for granted. I guess I've never bought a phone right at the moment of release before. If I didn't really need a new phone, I suppose I would have waited. Anyway, I figured out that you can block ads, without root, with apps that run all your traffic through a vpn (that's really only running locally on the phone). The best options after much research seem to me to be Netguard and AdGuard (though I haven't tried them yet). They both also include a firewall (Netguard is primarly a firewall), which I want.
https://github.com/M66B/NetGuard/blob/master/ADBLOCKING.md
https://adguard.com/en/adguard-android/overview.html
DNS66 also seems to be higly regarded, but it doesn't include a firewall. There are other firewall only apps, which work with the VPN method, but you can only run one VPN on Android at a time, so if you want both functions, without root, you need an app that does both.
https://forum.xda-developers.com/android/apps-games/app-dns66-source-host-ad-blocker-root-t3487497
Anyway, that's my plan until root comes along. Then I will go back to AdAway and AFWall+.
There is no kernel source released for the Pixel 2/XL yet. It is based on the 4.4 kernel, this should make development very smooth.
https://forum.xda-developers.com/pixel-2/development/psa-fastboot-booting-bad-image-confuse-t3692932
Hi everyone,
I have a the Google edition of Pixel, and have unlocked the bootloader successfully. I would like to root the device somethow, as well as get tether working. I am on Vzw's original unlimited data plan, and this phone has replaced my wife's Samsung Galaxy S3 phone on verizon. We held on to the S3 for so long as it is rooted and with the ROM we could tether using Vzw's tether and pay nothing extra.
What can I do to get back into a similar situation with this Google Pixel?
Thanks so much in advance.
statustray said:
Hi everyone,
I have a the Google edition of Pixel, and have unlocked the bootloader successfully. I would like to root the device somethow, as well as get tether working. I am on Vzw's original unlimited data plan, and this phone has replaced my wife's Samsung Galaxy S3 phone on verizon. We held on to the S3 for so long as it is rooted and with the ROM we could tether using Vzw's tether and pay nothing extra.
What can I do to get back into a similar situation with this Google Pixel?
Thanks so much in advance.
Click to expand...
Click to collapse
Install twrp and flash magisk for root. Any root tether app should be able to treat your tether data as standard data
KittyRgnarok said:
Install twrp and flash magisk for root. Any root tether app should be able to treat your tether data as standard data
Click to expand...
Click to collapse
Thanks KittyRgnarok,
Do you have a link for Twrp for Google Pixel and also one for majisk? It seems some threads are old, and I don't want to mess things up.
Thanks so much in advance.
statustray said:
Thanks KittyRgnarok,
Do you have a link for Twrp for Google Pixel and also one for majisk? It seems some threads are old, and I don't want to mess things up.
Thanks so much in advance.
Click to expand...
Click to collapse
Haha good on you for asking cuz quite a few people have gotten close to bricking their devices using the boot-to-root method from the day the phone released lmao. A quick Google search for "twrp sailfish" will bring u to the latest version of official twrp. As far as magisk just look up magisk on XDA and the official thread will have the dl link (don't download magisk from anywhere else)
There's a Magisk "Tethering Enabler" module which I recommend you try, after you're rooted.
KittyRgnarok said:
Haha good on you for asking cuz quite a few people have gotten close to bricking their devices using the boot-to-root method from the day the phone released lmao. A quick Google search for "twrp sailfish" will bring u to the latest version of official twrp. As far as magisk just look up magisk on XDA and the official thread will have the dl link (don't download magisk from anywhere else)
Click to expand...
Click to collapse
mike.s said:
There's a Magisk "Tethering Enabler" module which I recommend you try, after you're rooted.
Click to expand...
Click to collapse
Thanks fur the info KittyRgnarok and mike.s,
I will try to do that tomorrow. Got sidetracked by a few other honey dos. Will try my very best to get back on this tomorrow. I hope you don't mind me reaching tomorrow evening after I get off work.
TIA
statustray said:
Thanks fur the info KittyRgnarok and mike.s,
I will try to do that tomorrow. Got sidetracked by a few other honey dos. Will try my very best to get back on this tomorrow. I hope you don't mind me reaching tomorrow evening after I get off work.
TIA
Click to expand...
Click to collapse
No problem man and no worries. If you find yourself needing any help feel free to quote me in the thread or pm me.
KittyRgnarok said:
No problem man and no worries. If you find yourself needing any help feel free to quote me in the thread or pm me.
Click to expand...
Click to collapse
Hi KittRgnarok,
I have downloaded the following to my computer:
twrp-3.2.1-2-sailfish.img
twrp-pixel-installer-sailfish-3.1.1-2.zip
Magisk-v16.0.zip
My computer is a macbook pro so I don't believe I need any additional drivers as supposedly they are already available in the Mac OS. I was able to unlock my bootloader using a terminal session & adb.
How should I now proceed?
Thanks in advance.
statustray said:
Hi KittRgnarok,
I have downloaded the following to my computer:
twrp-3.2.1-2-sailfish.img
twrp-pixel-installer-sailfish-3.1.1-2.zip
Magisk-v16.0.zip
My computer is a macbook pro so I don't believe I need any additional drivers as supposedly they are already available in the Mac OS. I was able to unlock my bootloader using a terminal session & adb.
How should I now proceed?
Thanks in advance.
Click to expand...
Click to collapse
Correct MacBook shouldn't needed additional drivers. Put the magisk and twrp zip files on your phone. Then reboot into bootloader. From there use the command fastboot boot twrp-3.2.1-2-sailfish.img which should put you into ram version of twrp. From here decrypt your device and install the twrp installer zip file. Once that's done reboot into recovery and flash magisk and you should be good to go
I finally got it figured out I have installed TWRP, as well as Majisk. I've tested root using a root tester, and now I need to see about the module that mike.s was referring to- specifically "tethering enabler".
All this stuff is totally new to me, so I am creeping along at a slow pace... lol
statustray said:
I finally got it figured out I have installed TWRP, as well as Majisk. I've tested root using a root tester, and now I need to see about the module that mike.s was referring to- specifically "tethering enabler".
All this stuff is totally new to me, so I am creeping along at a slow pace... lol
Click to expand...
Click to collapse
In magisk manager there is a downloads tab and a modules tab. Go to the downloads tab and look for tether and you'll find it
KittyRgnarok said:
Correct MacBook shouldn't needed additional drivers. Put the magisk and twrp zip files on your phone. Then reboot into bootloader. From there use the command fastboot boot twrp-3.2.1-2-sailfish.img which should put you into ram version of twrp. From here decrypt your device and install the twrp installer zip file. Once that's done reboot into recovery and flash magisk and you should be good to go
Click to expand...
Click to collapse
You must've been posting as I was typing my message to you. I'm just now seeing that you provided some steps. Yes, I had figured that out and got it done. Life's good now.
I am doing some searching trying to figure out tethering, that's the last piece of the equation for now... hehehe..... On the old vzw unlimited data plan and I don't want to switch over to their new plans. If I can get this going, then my better half will be super happy, and then I will look into getting me a Google Pixel (but the XL version).
KittyRgnarok said:
In magisk manager there is a downloads tab and a modules tab. Go to the downloads tab and look for tether and you'll find it
Click to expand...
Click to collapse
Thanks so much KittyRgnarok,
You pointed me in the right direction and I really appreciate that. It worked with no problems as I tested it and all's well. I then demonstrated it to my better half and she is super happy!!
Now I will order me one as well, but I am going to get the Google Pixel XL. I see the screen is larger on the Pixel 2, but heard there's been some "screen issues"? For me the lack of a phone jack is not all that big of a deal as I never hookup a wired headset and only use the bluetooth. *Ahem* on my phone I've only used a wired headset once or twice years ago when my bluetooth messed up. Lol....
Thanks again for everything!
:good:
statustray said:
Thanks so much KittyRgnarok,
You pointed me in the right direction and I really appreciate that. It worked with no problems as I tested it and all's well. I then demonstrated it to my better half and she is super happy!!
Now I will order me one as well, but I am going to get the Google Pixel XL. I see the screen is larger on the Pixel 2, but heard there's been some "screen issues"? For me the lack of a phone jack is not all that big of a deal as I never hookup a wired headset and only use the bluetooth. *Ahem* on my phone I've only used a wired headset once or twice years ago when my bluetooth messed up. Lol....
Thanks again for everything!
:good:
Click to expand...
Click to collapse
Glad to hear both you and her are happy with the results . As far as the pixel 2 xl a lot of the screen issues were software side but there are also issues with burn in(which I've experienced a decent amount of on the og as well) I have a friend with the pixel 2 and I highly recommend it but be aware that it is modding hell if you intend to be messing with a lot of that. As far as staying on stock rom+magisk+Xposed though it works great.
Hi everyone
Can anyone please let me know if the files he downloaded is the same files i need to do the same procedure, i have a normal google pixel 32gb from verizon which i unlocked the bootloader on 7.1 then upgraded to 8.1
S7sadly said:
Can anyone please let me know if the files he downloaded is the same files i need to do the same procedure, i have a normal google pixel 32gb from verizon which i unlocked the bootloader on 7.1 then upgraded to 8.1
Click to expand...
Click to collapse
Same files.
Thank you
KittyRgnarok said:
Glad to hear both you and her are happy with the results . As far as the pixel 2 xl a lot of the screen issues were software side but there are also issues with burn in(which I've experienced a decent amount of on the og as well) I have a friend with the pixel 2 and I highly recommend it but be aware that it is modding hell if you intend to be messing with a lot of that. As far as staying on stock rom+magisk+Xposed though it works great.
Click to expand...
Click to collapse
Thanks for the heads up on the Pixel 2 issues. I will probably stay with stock like on my better half's phone, and just want to root and tether. Now the burn ins, that kind of worries me. Hmmmm... decisons, decision... hehe...
To prevent burn in you can get the magisk module that hides the navbar and toggle that occasionally as that's the only place I really notice it aside from the statusbar which idk a way to hide. I've also heard inverting colours often can help prevent it
KittyRgnarok said:
To prevent burn in you can get the magisk module that hides the navbar and toggle that occasionally as that's the only place I really notice it aside from the statusbar which idk a way to hide. I've also heard inverting colours often can help prevent it
Click to expand...
Click to collapse
Thanks for that information. I did not realize that. And sorry for the delay in responding. I didn't get on xda yesterday as I got back home late last night. I will certainly look for that magisk module you mentioned.
Oh and by the way, I just got me a Google Pixel XL today
Now I need to work the same magic on this one. I've already got it activated at the VZW Store near where I live. *Woohoo*
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.
Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R
Try nother USB C cable. Some not able to handle data.
rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.
BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,
Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone
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.