Related
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.
Mission:
The purpose of this project is to increase efficiency of the Pixel 7 series devices by merging functional patches with minimal bloat.
If you submit bug reports without a log, you may be prosecuted...or executed.
Disclaimer:
If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.
You must have verity and verification disable to flash this for the time being!
To do so you will need to flash vbmeta.img using the command below followed by wiping the device.
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Installation:
-Download ZIP for kernel and extract
-Use the below commands to flash from bootloader/fastboot
-fastboot reboot bootloader
-fastboot flash dtbo dtbo.img
-fastboot flash boot boot.img
-fastboot flash vendor_kernel_boot vendor__kernel_boot.img
-fastboot reboot fastboot
-fastboot flash vendor_dlkm vendor_dlkm.img
Links:
Downloads:
Kernels - Google Drive
drive.google.com
Telegram:
Despair
You can view and join @despairchat right away.
t.me
Source:
https://github.com/DespairFactor/pantah
Credits:
Google
A question, for curiosity sake...
*because it is coming from a very ignorant, noob place
With the change of Magisk now needing to patch the boot_init instead of the usual boot.img, would your kernel need to make the same adjustments? I was just looking at your directions and saw the command line for fastboot flashing boot, and I've been obsessively on the How To guide and there is a certain need of a sensitivity to flashing to the boot instead of the boot_init right now while the initial word gets out of the change...
I also mention this because it seems that this was developed under the Pixel 6 and all your documentation still seem to point to that device still....so....
i have absolutely no experience in kernel building and only dabbled in employing using custom kernels in the past, so I may have no idea what I'm talking about....i was just wondering if it's a possibility or eventuality...
You're source is nill if you didn't notice. And just a bit of an edit needed dude.
SeanHacker said:
You're source is nill if you didn't notice. And just a bit of an edit needed dude.
Click to expand...
Click to collapse
it's uploading still and yeah, I need to update that
simplepinoi177 said:
A question, for curiosity sake...
*because it is coming from a very ignorant, noob place
With the change of Magisk now needing to patch the boot_init instead of the usual boot.img, would your kernel need to make the same adjustments? I was just looking at your directions and saw the command line for fastboot flashing boot, and I've been obsessively on the How To guide and there is a certain need of a sensitivity to flashing to the boot instead of the boot_init right now while the initial word gets out of the change...
I also mention this because it seems that this was developed under the Pixel 6 and all your documentation still seem to point to that device still....so....
i have absolutely no experience in kernel building and only dabbled in employing using custom kernels in the past, so I may have no idea what I'm talking about....i was just wondering if it's a possibility or eventuality...
Click to expand...
Click to collapse
the init_boot is not touched with this so that magisk image that you flashed is untouched! I am hoping to get AnyKernel working soon enough or maybe another dev will hop on it and beat me to it. There is a bit of a problem with how our images are made for this device and how AnyKernel works from the stuff I have tested today.
Nice to see you here.
DespairFactor said:
I am hoping to get AnyKernel working soon enough or maybe another dev will hop on it and beat me to it. There is a bit of a problem with how our images are made for this device and how AnyKernel works from the stuff I have tested today.
Click to expand...
Click to collapse
Would you mind elaborating on that? I'm working on an update to Kernel Flasher, and I'm considering taking a stab at wrapping this kernel in AK3 for testing purposes.
I suppose with init_boot being untouched, one obvious change would be preventing it from patching boot. Would that and adding vendor_kernel_boot into the mix be enough, you think?
Edit: I managed to get it to flash and work with AK3 with verity disabled, but simply patching the hashtree descriptor for vendor_dlkm in vbmeta wasn't enough to get it to work with verity enabled.
your the man @DespairFactor
capntrips said:
Would you mind elaborating on that? I'm working on an update to Kernel Flasher, and I'm considering taking a stab at wrapping this kernel in AK3 for testing purposes.
I suppose with init_boot being untouched, one obvious change would be preventing it from patching boot. Would that and adding vendor_kernel_boot into the mix be enough, you think?
Edit: I managed to get it to flash and work with AK3 with verity disabled, but simply patching the hashtree descriptor for vendor_dlkm in vbmeta wasn't enough to get it to work with verity enabled.
Click to expand...
Click to collapse
So you've packed this kernel on AK3 , flashed through your flasher app and it boots?..( i have also verity disabled )
capntrips said:
Would you mind elaborating on that? I'm working on an update to Kernel Flasher, and I'm considering taking a stab at wrapping this kernel in AK3 for testing purposes.
I suppose with init_boot being untouched, one obvious change would be preventing it from patching boot. Would that and adding vendor_kernel_boot into the mix be enough, you think?
Edit: I managed to get it to flash and work with AK3 with verity disabled, but simply patching the hashtree descriptor for vendor_dlkm in vbmeta wasn't enough to get it to work with verity enabled.
Click to expand...
Click to collapse
init_boot and vendor_boot go untouched, think of vendor_kernel_boot as more or less the replacement for vendor_boot. How did you manage to get this to work? I think AVB is now tied to init_boot and vendor_boot only for now based on what I saw in the fstab.
Just uploaded a 1.02 build to fix a couple issues. This is using the manual flashing method until I can get confirmation on what is needed for AK3 to work. After I have this information I will make it into an AK3 zip.
DespairFactor said:
Just uploaded a 1.02 build to fix a couple issues. This is using the manual flashing method until I can get confirmation on what is needed for AK3 to work. After I have this information I will make it into an AK3 zip.
Click to expand...
Click to collapse
Will we always have to disable verity on this phone for custom kernels to work or will you eventually figure out a way around it?
I really don't feel like wiping my phone.
Gordietm said:
Will we always have to disable verity on this phone for custom kernels to work or will you eventually figure out a way around it?
I really don't feel like wiping my phone.
Click to expand...
Click to collapse
There may be a way around it, we rely on capntrips to help us on this journey. He helped us do it on the Pixel 6 devices. For now, I will keep mine disabled and probably will going forward to avoid any issues.
Like this so far!
Will revisit this once i dont need to Wipe my Device anymore and theres a Flasher for this!
Larakali said:
Like this so far!
Will revisit this once i dont need to Wipe my Device anymore and theres a Flasher for this!
Click to expand...
Click to collapse
You would only need to wipe once when you disable verification, you can update using factory images or flash tool and keep it disabled after the first time and not wipe.
It's great to see a custom kernel for the P7P. Is there a description of the changes in the kernel? I'm coming from the P6P and the Kiri kernel.
After spending 2 days setting up my device, I'm hesitant about wiping. Hopefully there will be a way to flash this kernel with out changing verification.
Does it still hold true that a wipe isn't needed when disabling only verity? I think capntrips mentioned only disabling verity and not verification as well.
Regardless, I disabled both of them on my 1st flash when getting this phone and will keep them that way going forward like I did with Raven, because things ...
swieder711 said:
It's great to see a custom kernel for the P7P. Is there a description of the changes in the kernel? I'm coming from the P6P and the Kiri kernel.
After spending 2 days setting up my device, I'm hesitant about wiping. Hopefully there will be a way to flash this kernel with out changing verification.
Click to expand...
Click to collapse
They are on GitHub, it's pretty close to the stuff I added on my 6 kernels. I have added SSG IOSCHED as well. I cannot list all the changes at the moment. Feel free to check GitHub commit history for the time being.
EDIT: One thing to note, because of the complaints of display being heavy on battery usage, I undervolted the display a little bit, we will have to see how this fares for battery usage. I didn't go crazy with it because we need to maintain stability of the device especially when there can be different binnings.
Lughnasadh said:
Does it still hold true that a wipe isn't needed when disabling only verity? I think capntrips mentioned only disabling verity and not verification as well.
Regardless, I disabled both of them on my 1st flash when getting this phone and will keep them that way going forward like I did with Raven, because things ...
Click to expand...
Click to collapse
I had to disable verification cause I manually flashed. We would need him to confirm or have someone with that setup test.
thanks for the quick release!
I did not disable verity when I did my bootloader unlock and root and dont feel like starting from scatch again so will wait to see if it gets fixed with AK3. if not then will wait until I have time to do a full wipe
Nekromantik said:
thanks for the quick release!
I did not disable verity when I did my bootloader unlock and root and dont feel like starting from scatch again so will wait to see if it gets fixed with AK3. if not then will wait until I have time to do a full wipe
Click to expand...
Click to collapse
I think capntrips will be looking into this over the coming week. You can disable Verity without wiping, but not verification. If he managed to get it to work with just Verity disabled that is good enough for me as it's rather simple to disable even if you forget to after an update.
Hi,
I've done a quick search but can't find anything definitive so a quick response on here would be greatly appreciated.
Are there any reasons not to root on a P7P? Like tripping Knox on Samsung devices? Basically, irreversible side effects of unlocking the BL or installing Magisk? I'm rooted on a Doogee S98 Pro, a Xiaomi MiPad 4 and a Samsung Tab S6 at the moment and I don't think I could go back to having no root. It's pretty much my main reason for not buying an S22 Ultra.
Hi
this is one of the major benefits of the P7P in my perspective: you can unlock, root, unroot, relock without any negative side effects. You don't trip any fuse or have other effects that cannot be undone by a simple reflash.
Plus, maybe due to this, the P7P is one of the phones where the dev community is still quite active.....
Sent from my rooted P7P
s3axel said:
Hi
this is one of the major benefits of the P7P in my perspective: you can unlock, root, unroot, relock without any negative side effects. You don't trip any fuse or have other effects that cannot be undone by a simple reflash.
Plus, maybe due to this, the P7P is one of the phones where the dev community is still quite active.....
Sent from my rooted P7P
Click to expand...
Click to collapse
Perfect answer, thanks!
Pretty hard to brick a Pixel.
Just make sure you don't relock your bootloader unless you're fully stock. I've seen a bunch of people doing that throughout these forums here for some reason.
Yup, if you want to unroot once you're rooted, it's absolutely imperative you flash full stock before toggling OEM Unlock and issuing any ADB commands to re-lock the bootloader. Do that without flashing back to factory stock and you end up with a phone that can't boot because the bootloader is locked with a non-stock build, you can't unlock the bootloader because the OEM is toggled, and you can't flash a stock build because the bootloader is locked. Brick time.
Other than that it's a fairly safe phone to play around with.
I strongly recommend Pixel Flasher, it makes the whole process easier, but make sure you read up on it before doing anything.
📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
GrapheneOS also supports relocking the bootloader, although I can't think of a reason why you'd want to.
The best reason not to root is that it's not needed in 2022. I can't imagine "needing" to do something with root that cannot be accomplished without root. YMMV
jaseman said:
The best reason not to root is that it's not needed in 2022. I can't imagine "needing" to do something with root that cannot be accomplished without root. YMMV
Click to expand...
Click to collapse
Call recording, full backup and restore, hosts based ad blockers.
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month. I've also had updates corrupt the A/B Partitions. The warning screen for unlocked bootloader alone is a nuisance. If you're ok with that, go right ahead.
Guyinlaca said:
disable all Magisk mods, run updates, then re-root every month
Click to expand...
Click to collapse
You're adding steps and no indication of why. Just install the update with modified boot.img and call it good.
96carboard said:
Call recording, full backup and restore, hosts based ad blockers.
Click to expand...
Click to collapse
I went 3 days before rooting my P7P since I was unfamiliar with the process. I was able to root OnePlus blindfolded, but the forums made Pixel seem difficult. It was the most miserable 3 days when everything I wanted to use/customize depended on root.
without root I could not even get 5G working. Furthermore the AOSP Mods on the stock ROM... Systemless Hosts AdBlocking, Re-Vanced, .......
I unlocked and rooted the phone before even booted it the first time
Guyinlaca said:
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month.
Click to expand...
Click to collapse
Updated to November, didn't disable any Magisk mods, no issues.
It's only some mods which cause issues. Not got them installed, you can perform the update without touching Magisk.
Guyinlaca said:
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month. I've also had updates corrupt the A/B Partitions. The warning screen for unlocked bootloader alone is a nuisance. If you're ok with that, go right ahead.
Click to expand...
Click to collapse
You don't have to disable all your Magisk Mods
K1nsey6 said:
I went 3 days before rooting my P7P since I was unfamiliar with the process. I was able to root OnePlus blindfolded, but the forums made Pixel seem difficult. It was the most miserable 3 days when everything I wanted to use/customize depended on root.
Click to expand...
Click to collapse
And wasn't it funny when you realized that root on Pixel is actually easier than everything else?
Hello , i need help for rooting my p7p. If have a video step by step its be very helpfull. Sorry for my bad english " Salut " from Romania thanks
ZoM4cs said:
Hello , i need help for rooting my p7p. If have a video step by step its be very helpfull. Sorry for my bad english " Salut " from Romania thanks
Click to expand...
Click to collapse
Here is a guide you can follow.
96carboard said:
Call recording, full backup and restore, hosts based ad blockers.
Click to expand...
Click to collapse
Umm that's illegal bro.
chivamex10 said:
Umm that's illegal bro.
Click to expand...
Click to collapse
Maybe where you are, but not here and not in most places. So keep your legal advice to yourself, BRO.
chivamex10 said:
Umm that's illegal bro.
Click to expand...
Click to collapse
Actually in most jurisdictions it's what's called a one party consent requirement wherein one of the parties involved must be aware and consent. In this case the person doing the recording qualifies as the consenting party. In other places two party or more consent is required but not everywhere
Will there ever be custom ROMs for the S7 FE?
Is there something certain holding devs back from making one?
Just curious.
I don't know but you can easily flash GSI now. Also I am wondering if S pen is working with GSI...
Incomtus said:
I don't know but you can easily flash GSI now. Also I am wondering if S pen is working with GSI...
Click to expand...
Click to collapse
I've tried dual boot Pixel Experience 13 GSI using DSU Sideloader. It works great. Got UI bugs like the taskbar is cropped, the Settings app is not dual pane.
The S Pen works. if you hover the pen a mouse icon appear. Buttons on the S Pen seems cannot do anything.
Overall the GSI feels very snappy but you will lose some function like protect battery, Dex, S Pen features, better multitasking/multi-windows experience, etc.
fict said:
I've tried dual boot Pixel Experience 13 GSI using DSU Sideloader. It works great. Got UI bugs like the taskbar is cropped, the Settings app is not dual pane.
The S Pen works. if you hover the pen a mouse icon appear. Buttons on the S Pen seems cannot do anything.
Overall the GSI feels very snappy but you will lose some function like protect battery, Dex, S Pen features, better multitasking/multi-windows experience, etc.
Click to expand...
Click to collapse
Hello thanks for your answer, dsu sideloader is working here? I don't see the option in the developer settings, you used the app on GitHub?
Yes i use DSU Sideloader app on the github. No root needed but bootloader must be unlocked
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
It's super cheap on Amazon right now. Hopefully the cheap price can be an appeal enough that releasing a custom ROM is worth it.
I'm no developer, but if you want your Samsung tablet to run AOSP like a Pixel, check out my guide here.
Otherwise, you can install GSIs from LineageOS, PHHTreble, or other projects.
Until ROMS can preserve some OEM capabilities it will be a ways off before custom ROMs are in high enough demand for this device. Sort of like Sony and how rooting can make you lose access to certain camera functions (if I recall).
V0latyle said:
I'm no developer, but if you want your Samsung tablet to run AOSP like a Pixel, check out my guide here.
Otherwise, you can install GSIs from LineageOS, PHHTreble, or other projects.
Click to expand...
Click to collapse
we would need a stable twrp for this, aren't we? :S
Incomtus said:
I don't know but you can easily flash GSI now. Also I am wondering if S pen is working with GSI...
Click to expand...
Click to collapse
Hi my bro. how to flash GSI?
billy996 said:
Hi my bro. how to flash GSI?
Click to expand...
Click to collapse
Hi!
First you have to unlock the bootloader (IT WILL ERASE ALL USER DATA) (method for maybe all Samsung device) by deactivated OEM LOCK in développement options,
then shutting down tablet and press both vol + and - while you plug the usb cable.
You LL see a warning green screen and you LL be able to unlock the bootloader.
After that I don't know if there is a TWRP recovery for that tablet but if there is one, you could flash it with Odin and then flash GSI.
If there is no TWRP, I think you can flash GSI but I don't know the method att all ..... Maybe take a look on internet "how flash GSI with Odin"?
Incomtus said:
Hi!
First you have to unlock the bootloader (IT WILL ERASE ALL USER DATA) (method for maybe all Samsung device) by deactivated OEM LOCK in développement options,
then shutting down tablet and press both vol + and - while you plug the usb cable.
You LL see a warning green screen and you LL be able to unlock the bootloader.
After that I don't know if there is a TWRP recovery for that tablet but if there is one, you could flash it with Odin and then flash GSI.
If there is no TWRP, I think you can flash GSI but I don't know the method att all ..... Maybe take a look on internet "how flash GSI with Odin"?
Click to expand...
Click to collapse
There is an other solution with DSU SIDELOADER but it will just a make a partition with original ROM, and the GSI one.
Bootloader must also be unlocked
Don't hesitate to ask if you don't know what what I am talking about
Typhoon_Master said:
we would need a stable twrp for this, aren't we? :S
Click to expand...
Click to collapse
Not necessarily, you can patch the stock recovery to accept fastboot commands with this
Deleted
billy996 said:
I extracted the recovery.img.lz4 from AP of the Stock firmware, and then tried to patch the recovery.img.lz4 with that script, but the patching failed, and I couldn't find the reason for the error.
Click to expand...
Click to collapse
You'd have to contact the developer of the script
I've flashed the GSI into the S7 FE and it feels great.
billy996 said:
I've flashed the GSI into the S7 FE and it feels great.
Click to expand...
Click to collapse
which GSI?
lukeprokopec said:
which GSI?
Click to expand...
Click to collapse
Lineage A13 GSI
billy996 said:
Lineage A13 GSI
Click to expand...
Click to collapse
First of all, there are several LOS 20 GSI ROMs. Can you give a link to the one you used. And how did you flash it without fastboot? AFAIK, there is no TWRP except for the SM-T735.