arm64 Checkra1n - Google Pixel XL Questions & Answers

I have been trying to use my Google Pixel XL (Marlin) too jailbreak iOS devices using the arm64 version of checkra1n exploit using the Terminux app however when I'm using my Pixel which is Magisk rooted and using a custom Kernel (I have tried EX and Kirisaiura) on Android 10, It seems to linger and then throw errors -21, 28 and -78.
I have looked up these errors on the projects GitHub issues page and noted that most of the people who get these errors are people using older RaspberryPi models.
I'm not sure why but I can't seem to get it too work, on the YouTube guides/tutorials on even on the threads on here talking about running the exploit on an iOS device using an Android device they are using varying models of Samsung and Sony phones - are there maybe missing drivers which allow the phone to 'see' the iOS devices in DFU mode? Is it maybe the Kernals I have tried?
Im unsure and stuck but am keen to find an answer to will attempt any information people throw my way.
Thanks for reading!
- Ian.

checkra1n can't run on kernel 3.xx environment, you must use device with kernel 4.xx

Ah, right - thanks for the answer.
Follow-up question: is Kernal 4.xx available/ever going to be possible on this device?

Related

Regarding Root and Android 7

So I read an Article
That states
Using a feature called verified boot, Android 7.0 Nougat will check the cryptographic integrity to detect if your device has been tampered with.
Click to expand...
Click to collapse
With that said, will there ever be root again for android 7 and up?
so, with cm14 at least, i believe root is included. If anything i think it will just disable certain features if the device has been rooted. although i suppose that it would depend on the manufacturer. It will certainly be more difficult with samsung, anyways. I'm done with samsung after this one, though. samsung has been bending root users over the table since knox was first included with consumer phones - since before then, but it was a minor inconvenience before then.
when they didn't include adoptable storage with their marshmallow update, i was OUT! looking at the lg v20 now, i sampled it for a bit and it literally made me want to throw my note 4 in the trash
Look at the Pixel, Android 7.1 + root, It's possible. We're not getting official Android 7.x more likely than not, but it's possible to root 7.x.
I'm running CM14.1 on this device and SuperSU is just fine.
RDChase said:
Look at the Pixel, Android 7.1 + root, It's possible. We're not getting official Android 7.x more likely than not, but it's possible to root 7.x.
Click to expand...
Click to collapse
Thank you this is the answer I was looking for.

Pixel C Meltdown/Spectre

Hey guys,
I'm running Rexmix OS on my Pixel which means that i won't get an security update for Meltdown/Spectre...
Can i just put an fixed Kernel on it and go on with my marshmallow based Remix?
I found this one: https://android.googlesource.com/kernel/tegra/+/android-tegra-dragon-3.18-oreo-r6
I couldn't find out if it even has the fix...
How do i flash it, I'm used to the one file fasboot flashing stuff :/
And btw does anybody know if Phoenix OS (seems like they are continueing the Remix OS) has planned to support Pixel C (they didn't reply to my email...)?
sry for all my n00b questions
could please somebody just tell me if i CAN update the kernel and keep the os? ...
I think kernels are specific to devices and android versions. So as long as the kernel you use is for the pixel c and the same android version as the rom you use, it should work. That said,you might struggle to find a pixel c kernel with fixes to those vulnerabilities...
Good luck, let is know if it works..
We are only vulnerable to Spectre you'd have to pull the patches from the common tree and merge in
live is a risk (spectre)?
ok thanks a lot for the answeres, guys; good to know that meltdown doesn't affect the pixel
since the only thing i know is copy and paste, i guess that's it for me :silly:
still didnt get an answer from the phoenix OS guys :/ I guess they are busy enough already
So whats your guys opinion: could I just stay on my remix OS marshmallow, be carefull using the web and untrusted app sources and just deal with the spectre thread? Live is a risk? :silly:
btw: are you guys cool with aosp roms? Personally i use the pixel like a laptop so normal android with the status bar and the weired button setup seems very unhandy for me...
I am Stock Oreo with freeform windows enabled via adb and "taskbar" app installed from play store to launch apps in freeform mode and quiet happy. Stock freeform is buggier than the implementation found on RemixOS or PhoenixOS but I get the latest android version, on the upside. RemixOs is dead and PhoenixOS doesn't even have a pixelC version, I think..
If you are worried about security , you can root and install a custom kernel too..
L

Regular TWRP vs Codeworkx

My 5T will be arriving today (coming from the Moto X Pure Edition...just under 2 years old. Yucky!) and I'm reading about rooting. ADB/oem unlocking/fastboot/etc. are familiar territory for me. I just wanted to make sure of something quick: I saw the guide saying to get Codeworkx TWRP, but I also see TWRP has a dumpling recovery image. I'm kind of thinking regular TWRP is fine, but I'm always careful when unlocking bootloader/custom recovery/rooting. I figured I'd ask just to be sure.
The official TWRP has always had issues with encryption on this device. Basically it's been behind the curve on updates. Last I heard it's gotten better, but it's generally still recommended to use Codeworkx or Blu's version. Personally I'm using Codeworkx.
[RECOVERY][dumpling] TWRP 3.2.3 by codeworkx
Blu seems to be more updated at the moment and has Amoled, and Treble support for 5.1.5.
Not sure if codeworkx has amoled and treble...
https://forum.xda-developers.com/oneplus-5t/development/kernel-t3706295
DOWNLOAD KERNEL ZIP and RECOVERY
https://forum.xda-developers.com/devdb/project/?id=21949#downloads
twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img works really nice for me on 5.1.5
Thanks for the replies! :highfive: I went with blu's version and have had no problems. I think I read somewhere (I can't find it agian, obviously...) that for a nandroid backup all screen lock safety has to be removed or encryption will prevent a restore. Would this be accurate? There's a lot of new stuff I'm trying to get used to with my 5T, coming from a closer to stock Android MXPE, especially the world of encryption. I wanted to try out some custom ROMs and wanted to make sure if I didn't like it I could restore to OOS easy. Apologies if there's a guide somewhere on the 5T forums...I've had this for 2 days now. Love it.
Another question about custom ROMs; are they as snappy as OOS? Every other Android phone I've had sacrificed speed for customization with custom ROMs. I miss the closer to stock Android look, but it's no deal breaker. I also really miss the option to make the volume buttons only control media. I tried Gravitybox for Oreo (Magisk + Systemless Xposed), but it wouldn't work.
@Moppusan with experience anything is just as snappy as anything else...
I deblot OOS and run microG on it, then if you know your way around Kernels, you can stick in EX Kernel Manager, or Kernel Adiutor and tweak up the stock kernel and get it smoother, or faster, overclock, get real crazy... RenderZenith seems like a nice kernel for OOS, it's a newer kernel version with newer features that seem to perform over stock.
It seems like, if OnePlus gave us a newer kernel version then we could have some nice newer kernel features in a stock kernel. OOS 5.1.5 is on 4.4.78 So maybe the next release of OOS will see a nicer more up to date version... Maybe some one running the latest beta can tell us what version it's on?
I'm getting ready to put up a guide, hopefully in a few weeks about doing the debloating and microG on OOS.
Remember OOS is a Custom Rom, from OnePlus...
@DoR3M3, well...yeah that is another way to look at it. OOS being a custom ROM.
I'm probably in the intermediate level of Kernel knowledge. I bought the pro/premium/donate/whatever-he-calls-it version of Kernel Adiutor and have read plenty of guides on cpu/gpu governors, hot plugs, over/underclocking, input boost, voltage, storage...governors?, net congestion and blah blah blah. I think the only thing that's really over my head is the tunables for the cpu governors. I've just found settings other people have tested and try it myself.
It would be great seeing such a guide ! Was thinking about a journey into the mirco land but my laziness holds me back :/
Moppusan said:
@DoR3M3, well...yeah that is another way to look at it. OOS being a custom ROM.
I'm probably in the intermediate level of Kernel knowledge. I bought the pro/premium/donate/whatever-he-calls-it version of Kernel Adiutor and have read plenty of guides on cpu/gpu governors, hot plugs, over/underclocking, input boost, voltage, storage...governors?, net congestion and blah blah blah. I think the only thing that's really over my head is the tunables for the cpu governors. I've just found settings other people have tested and try it myself.
Click to expand...
Click to collapse
OOS is a Custom ROM, the only difference is that OnePlus is a manufacture, and because of Google's licensing, has to include the Gapps. But, I wonder if OnePlus can put up OOS for download on their site, that is GappsFree, now that would be nice!
If you're not running Linux and you are into Android, I highly recommend it. Of course there are things specific to Android, but it comes from Linux and running Linux makes the journey easier.
AlMustansir said:
It would be great seeing such a guide ! Was thinking about a journey into the mirco land but my laziness holds me back :/
Click to expand...
Click to collapse
I'm still working on it, been typing away on it today. Also added in an extra section for the Privacy Geeks, I figured out how to do the Play Store anonymously for getting paid apps...
DoR3M3 said:
OOS is a Custom ROM, the only difference is that OnePlus is a manufacture, and because of Google's licensing, has to include the Gapps. But, I wonder if OnePlus can put up OOS for download on their site, that is GappsFree, now that would be nice!
If you're not running Linux and you are into Android, I highly recommend it. Of course there are things specific to Android, but it comes from Linux and running Linux makes the journey easier.
Click to expand...
Click to collapse
I've tried Linux many times and I just can't get into it. The biggest drawback is the lack of serious DAWs (Digital Audio Workstations, if you didn't know) and gaming support (I don't think my PC could handle running anything smoothly through Wine).
Moppusan said:
I've tried Linux many times and I just can't get into it. The biggest drawback is the lack of serious DAWs (Digital Audio Workstations, if you didn't know) and gaming support (I don't think my PC could handle running anything smoothly through Wine).
Click to expand...
Click to collapse
If you need to be on Windows all the time, then run a VM like VirtualBox and run Linux on it, or dual boot Linux/Windows...
Moppusan said:
I've tried Linux many times and I just can't get into it. The biggest drawback is the lack of serious DAWs (Digital Audio Workstations, if you didn't know) and gaming support (I don't think my PC could handle running anything smoothly through Wine).
Click to expand...
Click to collapse
Well, Steam play can run many games with almost same performance than on windows.

[Q] What's needed to build a custom rom for S9+?

Hi Im curious what's required to build a custom rom (pie or later) for the Qualcomm China varient? Are there any guides tailored or something towards these devices (basically less of generalized one)?
What I know i need:
A 64bit Linux box i have that: Debian 10 currently.
Custom rom source (I'll decide on it later probably will be Lineage)
Samsung S9 Source Code etc <== Not sure how to get it.
A way to Flash said custom rom once built (TWRP would be easiest since i have it already plus saves me trying to make a flash package for the Linux's varient of Odin)
End of what I know im sure that there's more i will need hence the reason for the thread lol.
Anyway Thanks to anyone for any help they can offer in advance.
darkensx said:
Hi Im curious what's required to build a custom rom (pie or later) for the Qualcomm China varient? Are there any guides tailored or something towards these devices (basically less of generalized one)?
What I know i need:
A 64bit Linux box i have that: Debian 10 currently.
Custom rom source (I'll decide on it later probably will be Lineage)
Samsung S9 Source Code etc <== Not sure how to get it.
A way to Flash said custom rom once built (TWRP would be easiest since i have it already plus saves me trying to make a flash package for the Linux's varient of Odin)
End of what I know im sure that there's more i will need hence the reason for the thread lol.
Anyway Thanks to anyone for any help they can offer in advance.
Click to expand...
Click to collapse
two things. 1: an unlocked bootloader 2: asking your question in the right place just messing with you on the latter, of course.
Id poke around in the Galaxy devices built specifically for non US markets as they have unlocked bootloaders and that level of development is awash in those areas.
Youdoofus said:
two things. 1: an unlocked bootloader 2: asking your question in the right place just messing with you on the latter, of course.
Id poke around in the Galaxy devices built specifically for non US markets as they have unlocked bootloaders and that level of development is awash in those areas.
Click to expand...
Click to collapse
actually i have the unlocked bootloader SM-G9650 (star2qltechn) i forgot to mention that lol my bad..

Question Dual booting Windows 11 or running virtualized

Hi all,
As we know MS has released and has been maintaining an ARM version of Windows for a while now, I was curious if anyone knew if it was possible to dual boot the ARM version? If dual booting isn't an option, what would be the best way to run it? I'm not worried about performance as such, as it's not something I plan to really use until KVM is supported for more than the pixel anyway, I was purely looking to test and see how it would look on such a device.
Any recommendations would be appreciated.
Dual booting is 99.999% won't work - the ARM image maintained by Microsoft is incredibly limited and lacks a lot of drivers, drivers that one would need to write from scratch, since they don't exist for Windows.
Virtualizing it would be possible on Android 13's new built in emulation stack, but you'd still need to root the phone for that, and beyond losing warranty in many places, you'd also lose access to a number of functions.
Has anybody on the Android 13/OneUi 5 Beta managed to root their device and try if the KVM feature works on the Z Fold 4?

Categories

Resources