Question TWRP? - ASUS ZenFone 8

Hi,
how long does it usually take for a new phone till TWRP is released?
Regards,
Hyper

HyperCriSiS said:
Hi,
how long does it usually take for a new phone till TWRP is released?
Regards,
Hyper
Click to expand...
Click to collapse
Sometimes 0day. Sometimes never.

It takes as long as it takes. Posts like this don't make me want to work any faster, btw.

Captain_Throwback said:
It takes as long as it takes. Posts like this don't make me want to work any faster, btw.
Click to expand...
Click to collapse
Take your time, there isn't much we can flash yet anyway

Captain_Throwback said:
It takes as long as it takes. Posts like this don't make me want to work any faster, btw.
Click to expand...
Click to collapse
Hurry up already, gosh.

Captain_Throwback said:
It takes as long as it takes. Posts like this don't make me want to work any faster, btw.
Click to expand...
Click to collapse
Sorry if this offended you but I was not asking for an ETA. This was a normal open question.

In the eventuality that a TWRP may come in the future, what are the chances that the internal sd location will be erased in the process? I was looking at the previous Zenfone TWRP threads and apparently it supports encryption. I assume that *if* TWRP supports encryption then the internal sd card will be preserved?

wind0zer said:
In the eventuality that a TWRP may come in the future, what are the chances that the internal sd location will be erased in the process? I was looking at the previous Zenfone TWRP threads and apparently it supports encryption. I assume that *if* TWRP supports encryption then the internal sd card will be preserved?
Click to expand...
Click to collapse
I don't understand the question. TWRP doesn't erase internal storage unless you do it intentionally. There's no connection between TWRP supporting encryption and internal storage being erased.

@Captain_Throwback, sorry my bad; I'm coming from a Samsung device and the initial TWRP flashing required users to flash a vbmeta_disabled_R.tar followed by wiping the internal storage. Also the TWRP didn't support encryption. Thanks for the info by the way.

Captain_Throwback said:
It takes as long as it takes. Posts like this don't make me want to work any faster, btw.
Click to expand...
Click to collapse
Hi. Don't have at least an alpha or beta version? I installed the module in magisk. And got a bootloop. If I return the original boot, then the phone can boot, but I do not have root rights to remove the problem module. None of the instructions I found for disabling magisk modules helped me. There remains only a way through twrp.

This instruction helped me https://forum.xda-developers.com/t/...-for-modules-gone-wrong.3966867/post-83468771

Related

Encryption not succesfull

I am trying to encrypt my m7, but somehow it doesnt work. After i started the process, i see this wired android and then the device boots up normally , saying that ecryption was unsuccessful, but i can still use it and no (aparent) data is lost.
My Phone is s-off, with 1.56Hboot and running cm11 nightlies.
Adromir said:
I am trying to encrypt my m7, but somehow it doesnt work. After i started the process, i see this wired android and then the device boots up normally , saying that ecryption was unsuccessful, but i can still use it and no (aparent) data is lost.
My Phone is s-off, with 1.56Hboot and running cm11 nightlies.
Click to expand...
Click to collapse
why did you think CM11 would support encryption ?
http://forum.xda-developers.com/showthread.php?t=2773203
http://forum.xda-developers.com/showthread.php?t=2777904
clsA said:
why did you think CM11 would support encryption ?
Click to expand...
Click to collapse
Well having the Option in there was quite some kind of a hint. So if i am reading this topic right http://forum.xda-developers.com/showthread.php?t=2773203 i can encrypt it via adb
shell?
Adromir said:
Well having the Option in there was quite some kind of a hint. So if i am reading this topic right http://forum.xda-developers.com/showthread.php?t=2773203 i can encrypt it via adb
shell?
Click to expand...
Click to collapse
no that's how you rescue your phone after it won't boot from failed encryption attempt
To be honest i have not kept up on all the nightly releases ..encryption bug may be fixed now
but I would never risk it. A simple pattern lock screen is all i need
clsA said:
no that's how you rescue your phone after it won't boot from failed encryption attempt
Click to expand...
Click to collapse
Oh okay, thanks i dont need it then, because it doesnt do anything on my phone and i havent lost any data yet.
clsA said:
but I would never risk it. A simple pattern lock screen is all i need
Click to expand...
Click to collapse
I had that opinion too, but then i thought, that my phone is unlocked and having a custom recovery, what kind of help is a lockscreen, when someone with a bit of knowledge just have to boot into recovery and then all of your data is exposed. Then i dont have to trouble myself with a lockscreen either or at least encrypt the space
Adromir said:
Oh okay, thanks i dont need it then, because it doesnt do anything on my phone and i havent lost any data yet.
I had that opinion too, but then i thought, that my phone is unlocked and having a custom recovery, what kind of help is a lockscreen, when someone with a bit of knowledge just have to boot into recovery and then all of your data is exposed. Then i dont have to trouble myself with a lockscreen either or at least encrypt the space
Click to expand...
Click to collapse
If a hacker / law enforcement finds your phone encryption is not going to help you
the average joe has no idea how to enter recovery or what to do when they get their

[Q] Stock Rooted Rom

Any way to get a stock rooted flashable zip? Even if it doesn't contain root. I am not sure how they are created.
nhpctech said:
Any way to get a stock rooted flashable zip? Even if it doesn't contain root. I am not sure how they are created.
Click to expand...
Click to collapse
take a few minutes and root your device. you fastboot unlock your bootloader, fastboot oem device. then you flash a recovery, then flash the supersu binaries in that recovery, then boot up. thats it. now you have a stock rooted rom.
simms22 said:
take a few minutes and root your device. you fastboot unlock your bootloader, fastboot oem device. then you flash a recovery, then flash the supersu binaries in that recovery, then boot up. thats it. now you have a stock rooted rom.
Click to expand...
Click to collapse
I know how to root, unlock bootloader and flash roms. Im looking to create a flashable zip of the stock rom. Not only have a stock rooted device.
bump...
There is no flashable zip of the stock ROM.
Take simms22's advice.
zephiK said:
There is no flashable zip of the stock ROM.
Take simms22's advice.
Click to expand...
Click to collapse
Is there a reason for this? Is it just the amount of time the phone has been out? It just seems that I used to see Stock Rom .zip's for Stock everywhere on every device i've owned that had an unlocked bootloader except for this phone so far.
nhpctech said:
Any way to get a stock rooted flashable zip? Even if it doesn't contain root. I am not sure how they are created.
Click to expand...
Click to collapse
I think this is what you're looking for:
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-5-1-lmy47e-root-t3057902
Nameless crowd face said:
I think this is what you're looking for:
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-5-1-lmy47e-root-t3057902
Click to expand...
Click to collapse
I think you're only 8months late.
sent from my nexus
crashercarlton said:
Is there a reason for this? Is it just the amount of time the phone has been out? It just seems that I used to see Stock Rom .zip's for Stock everywhere on every device i've owned that had an unlocked bootloader except for this phone so far.
Click to expand...
Click to collapse
Primarily because, factory images are provided by Google and flashed with fastboot. In the same fastboot session, you can install custom recovery. Then boot to recovery and flash SuperSU zip.
Takes less than 5 minutes.
The_Merovingian said:
Primarily because, factory images are provided by Google and flashed with fastboot. In the same fastboot session, you can install custom recovery. Then boot to recovery and flash SuperSU zip.
Takes less than 5 minutes.
Click to expand...
Click to collapse
less than 2 minutes :angel:
Roobwz said:
I think you're only 8months late.
sent from my nexus
Click to expand...
Click to collapse
Had to throw that in there, huh...Why do some ppl love responding to posts not directed at them, knowing they aren't contributing anything of value. Should be a name for ppl who do that.. Oh wait, there is...
Nameless crowd face said:
Had to throw that in there, huh...Why do some ppl love responding to posts not directed at them, knowing they aren't contributing anything of value. Should be a name for ppl who do that.. Oh wait, there is...
Click to expand...
Click to collapse
This thread is old. At the time, there were no rooted stock roms. There are many by now and everyone can see them all in the android development forum. Generally, digging up old threads doesn't serve any purpose becuase the questions are no longer valid, thus answering them is superfluous and just adds to forum clutter
simms22 said:
less than 2 minutes :angel:
Click to expand...
Click to collapse
Two minutes! Ha! If only! Rebuilding the dalvic cache (is it still called that?) on first boot takes my phone like 5 minutes alone...
My problem with flashing factory images is having my /sdcard/ wiped. Is there a way around it? Like a way to flash /data/ without touching /sdcard/?
Backing everything up, transferring it to my laptop, flashing the image and twrp, booting, transferring everything back and restoring my TiBu takes waaaaaayyyy longer than just flashing a zip and restoring TiBu
danarama said:
This thread is old. At the time, there were no rooted stock roms. There are many by now and everyone can see them all in the android development forum. Generally, digging up old threads doesn't serve any purpose becuase the questions are no longer valid, thus answering them is superfluous and just adds to forum clutter
Click to expand...
Click to collapse
(Polite) point taken. I should've looked at dates. My apologies
Morganmachine91 said:
Two minutes! Ha! If only! Rebuilding the dalvic cache (is it still called that?) on first boot takes my phone like 5 minutes alone...
My problem with flashing factory images is having my /sdcard/ wiped. Is there a way around it? Like a way to flash /data/ without touching /sdcard/?
Backing everything up, transferring it to my laptop, flashing the image and twrp, booting, transferring everything back and restoring my TiBu takes waaaaaayyyy longer than just flashing a zip and restoring TiBu
Click to expand...
Click to collapse
Yes. If you're simply updating, just flash the system image and boot image if it's updated. Same goes for bootloader and radio. If you don't flash userdata, you won't lose data.
Nameless crowd face said:
(Polite) point taken. I should've looked at dates. My apologies
Click to expand...
Click to collapse
Not the end of the world

Trouble Decrypting Nexus 6

I recently received my nexus 6 a couple days ago and I LOVE it. The problem I am having at the moment is that I can't seem to get it to go decrypt. I downloaded the tool kit and my devices build isn't present. As a result, the tool kit it won't allow me to run the decrypt option on the fastboot window.
It's anyone running into this. My build is a LNX***.
First, what toolkit are you talking about?
Second, to decrypt the N6 you need to flash a modified boot image and then wipe your phone.
Thirdly, what's build LNX***?
Didgeridoohan said:
First, what toolkit are you talking about?
Second, to decrypt the N6 you need to flash a modified boot image and then wipe your phone.
Thirdly, what's build LNX***?
Click to expand...
Click to collapse
I'm using the nexus root toolkit . I have the flash on my computer and LNX07M is the build I have on the device. Maybe I should install a custom ROM first?
Nexus 6....man I missed being rooted.
KappaAce2010 said:
I'm using the nexus root toolkit . I have the flash on my computer and LNX07M is the build I have on the device. Maybe I should install a custom ROM first?
Nexus 6....man I missed being rooted.
Click to expand...
Click to collapse
You just need a custom kernel and a wipe.
another prime example of why you shouldn't use toolkits, if you don't understand what they are doing you shouldn't be using them.
To decrypt all you need to do is:
Backup your internal storage to a PC
Either use custom recovery to wipe everything including internal storage, install your rom and install a kernel that doesn't force
or
factory reset your phone, but before it boots up go back into recovery and flash a custom kernel that doesn't enforce
Circaflex said:
another prime example of why you shouldn't use toolkits, if you don't understand what they are doing you shouldn't be using them.
To decrypt all you need to do is:
Backup your internal storage to a PC
Either use custom recovery to wipe everything including internal storage, install your rom and install a kernel that doesn't force
or
factory reset your phone, but before it boots up go back into recovery and flash a custom kernel that doesn't enforce
Click to expand...
Click to collapse
Well if you to come off as a jerk, you have accomplished your goal. All you had to do was state what was needed and none of bs personal ideals you have. It's a Q & A section, so you should expect questions like this to arise.
Thank you for the input though.
Nexus 6....man I missed being rooted.
KappaAce2010 said:
Well if you to come off as a jerk, you have accomplished your goal. All you had to do was state what was needed and none of bs personal ideals you have. It's a Q & A section, so you should expect questions like this to arise.
Thank you for the input though.
Nexus 6....man I missed being rooted.
Click to expand...
Click to collapse
Although you're right, it is a personal ideal of many of us, I don't think he intended to come off as a jerk. But his point is that toolkits often remove the need for knowledge, which can become a problem for some users.
The good thing about nexus devices is that everything is pretty easy to do, so if you get stuck - continue to ask.
+1 to what rootSU said. And you should probably upgrade. That build is ancient and doesn't even have an official factory image (the reason it's not available in NRT).
Didgeridoohan said:
+1 to what rootSU said. And you should probably upgrade. That build is ancient and doesn't even have an official factory image (the reason it's not available in NRT).
Click to expand...
Click to collapse
I already plan on doing this anyway. Just time is conflicting with me at the moment.
rootSU said:
Although you're right, it is a personal ideal of many of us, I don't think he intended to come off as a jerk. But his point is that toolkits often remove the need for knowledge, which can become a problem for some users.
The good thing about nexus devices is that everything is pretty easy to do, so if you get stuck - continue to ask.
Click to expand...
Click to collapse
Well it happened, it's not going anywhere. Either way thanks guys for the advice. I should figure out everything tonight.
Nexus 6....man I missed being rooted.
Everything is a go. Fully decrypted and loving it. Thanks again.

Nexus 6 forced encryption questions.

Hello! So I just have some questions about the forced encryption on the Nexus 6. I will be getting a Nexus 6 very soon here, and I like custom ROMs and custom software. Questions are:
1) Can I install a custom ROM without even messing with the forced encryption? In other words, can I ignore that it's there and just unlock bootloader, install custm recovery, and flash a ROM and gapps? Will it just run with the encryption on?
2) If I do disable the encryption, can I use the normal software update? (with no custom ROM of course in this case) Or will I have to reflash the encrypted kernel to system update?
3) Do some custom ROMs just disable the encryption by default?
And
4) If it get stuck in a boot loop because of a kernel issue, is this easy fixable? Or is it a hard brick that can't be recovered?
Thanks in advance everyone!
H4X0R46 said:
Hello! So I just have some questions about the forced encryption on the Nexus 6. I will be getting a Nexus 6 very soon here, and I like custom ROMs and custom software. Questions are:
1) Can I install a custom ROM without even messing with the forced encryption? In other words, can I ignore that it's there and just unlock bootloader, install custm recovery, and flash a ROM and gapps? Will it just run with the encryption on?
2) If I do disable the encryption, can I use the normal software update? (with no custom ROM of course in this case) Or will I have to reflash the encrypted kernel to system update?
3) Do some custom ROMs just disable the encryption by default?
And
4) If it get stuck in a boot loop because of a kernel issue, is this easy fixable? Or is it a hard brick that can't be recovered?
Thanks in advance everyone!
Click to expand...
Click to collapse
1. Yes
2. You can't update with any modifications to the system. Meaning you must have stock recovery, no root, etc.
3. Yes (They don't FORCE encryption meaning if your unencrypted already you will stay unencrypted.)
4. Yes
Sent from my Nexus 6 using Tapatalk
Thanks for the quick response! Much appreciated. On my fourth question, did you mean that's easily fixable? Or like, yes that's a hard brick? And also, (question 3) you say that a custom ROM won't force it, but if you're still encrypted when you flash the ROM, does that mean you can just turn it off in your settings with a ROM? Or do you stay encrypted? Or how does that work?
EDIT: (question 2) if I used a toolkit to reflash a stock image, that's clean enough for a normal system update right? After that and relocking the bootloader?
Sorry for all the questions, I just wanna know these things before I go fork out $600 for a device that I intend to mod!
H4X0R46 said:
Thanks for the quick response! Much appreciated. On my fourth question, did you mean that's easily fixable? Or like, yes that's a hard brick? And also, (question 3) you say that a custom ROM won't force it, but if you're still encrypted when you flash the ROM, does that mean you can just turn it off in your settings with a ROM? Or do you stay encrypted? Or how does that work?
EDIT: (question 2) if I used a toolkit to reflash a stock image, that's clean enough for a normal system update right? After that and relocking the bootloader?
Sorry for all the questions, I just wanna know these things before I go fork out $600 for a device that I intend to mod!
Click to expand...
Click to collapse
To be unencrypted, you must format data. Do not use toolkits unless you know how to use ADB/fastboot. Yes this phone is hard to brick as long as the bootloader is unlocked.
H4X0R46 said:
Hello! So I just have some questions about the forced encryption on the Nexus 6. I will be getting a Nexus 6 very soon here, and I like custom ROMs and custom software. Questions are:
1) Can I install a custom ROM without even messing with the forced encryption? In other words, can I ignore that it's there and just unlock bootloader, install custm recovery, and flash a ROM and gapps? Will it just run with the encryption on?
2) If I do disable the encryption, can I use the normal software update? (with no custom ROM of course in this case) Or will I have to reflash the encrypted kernel to system update?
3) Do some custom ROMs just disable the encryption by default?
And
4) If it get stuck in a boot loop because of a kernel issue, is this easy fixable? Or is it a hard brick that can't be recovered?
Thanks in advance everyone!
Click to expand...
Click to collapse
3. its the kernel, not rom, that makes you be abke to decrypt, not rom. it might be added to a rom as well, but it would be in its kernel. also, ot doesnt decrypt, it gives you the option to decrypt. but you have to do it, decrypt.
4 easily fixable. you have to learn the very basics of it though. rrally. but its extremely easy to fix.
---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------
H4X0R46 said:
Thanks for the quick response! Much appreciated. On my fourth question, did you mean that's easily fixable? Or like, yes that's a hard brick? And also, (question 3) you say that a custom ROM won't force it, but if you're still encrypted when you flash the ROM, does that mean you can just turn it off in your settings with a ROM? Or do you stay encrypted? Or how does that work?
EDIT: (question 2) if I used a toolkit to reflash a stock image, that's clean enough for a normal system update right? After that and relocking the bootloader?
Sorry for all the questions, I just wanna know these things before I go fork out $600 for a device that I intend to mod!
Click to expand...
Click to collapse
learn to do it right the first time. it sounds hard and complicated, but its extremely easy after you do it all manually the first time. after that, feel free to use a toolkit. it wont save you time btw, doing it right takes just 3-5 minutes after the first time
Thanks guys! Much appreciated! If things were to go horribly wrong with the kernel if I did decrypt it and it bricked because of a kernel issue, would flashing a stock image still be a fix for a kernel problem? (with the bootloader unlocked of course). I'm not new to Android modding, I have a phone running a CM nightly right now, but this encryption thing and messing with a phones kernel scares me a bit haha
H4X0R46 said:
Thanks guys! Much appreciated! If things were to go horribly wrong with the kernel if I did decrypt it and it bricked because of a kernel issue, would flashing a stock image still be a fix for a kernel problem? (with the bootloader unlocked of course). I'm not new to Android modding, I have a phone running a CM nightly right now, but this encryption thing and messing with a phones kernel scares me a bit haha
Click to expand...
Click to collapse
Flashing any rom also flashes a kernel, so you've already done it before. Its no different here
danarama said:
Flashing any rom also flashes a kernel, so you've already done it before. Its no different here
Click to expand...
Click to collapse
Alright, custom ROMs contain kernels. I've heard that before but wasn't sure haha Thanks everyone!
H4X0R46 said:
Alright, custom ROMs contain kernels. I've heard that before but wasn't sure haha Thanks everyone!
Click to expand...
Click to collapse
every rom haa a kernel in it. a rom can not run without a kernel. a kernel is like what will connect the cpu and hardware with the os.
H4X0R46 said:
If things were to go horribly wrong with the kernel if I did decrypt . . .
Click to expand...
Click to collapse
The first question you need to answer is:
'Why decrypting?'
When the answer contains words like 'speed' or 'performance' than you may consider to leave your N6 encrypted.
NLBeev said:
The first question you need to answer is:
'Why decrypting?'
When the answer contains words like 'speed' or 'performance' than you may consider to leave your N6 encrypted.
Click to expand...
Click to collapse
right :good:
chavonbravo said:
Try Ultimate Theft Alert v3.5 and W.I.M.P. Both have ability to track via GPS when your phone gets stolen as well.
Click to expand...
Click to collapse
Well, I've heard from many sources that the encryption in the phone just KILLS battery life, and if you turn off the encryption, it nearly triples the battery life. Is this true? Because it would be a waste if the phones battery is abysmal for such a great device! From anyone's experience here, should I not worry about it and just leave the device encrypted?
H4X0R46 said:
Well, I've heard from many sources that the encryption in the phone just KILLS battery life, and if you turn off the encryption, it nearly triples the battery life. Is this true? Because it would be a waste if the phones battery is abysmal for such a great device! From anyone's experience here, should I not worry about it and just leave the device encrypted?
Click to expand...
Click to collapse
I wouldn't say it triples battery, just increases the NAND read/write speed performance. Battery could take a hit as opening apps takes longer when encrypted.
Choristav said:
I wouldn't say it triples battery, just increases the NAND read/write speed performance. Battery could take a hit as opening apps takes longer when encrypted.
Click to expand...
Click to collapse
Apps aren't encrypted. If they were we couldn't pull them from phone to decompile and mod them. Only your data is and it is only a few KBs per app. Only notice encryption on large personal files and downloads.
H4X0R46 said:
Well, I've heard from many sources that the encryption in the phone just KILLS battery life, and if you turn off the encryption, it nearly triples the battery life. Is this true? Because it would be a waste if the phones battery is abysmal for such a great device! From anyone's experience here, should I not worry about it and just leave the device encrypted?
Click to expand...
Click to collapse
im encrypted, and my n6 sees between 5.5-7 hours sot. thats more than most unencrypted phones see!
---------- Post added at 08:28 PM ---------- Previous post was at 08:26 PM ----------
battery life is all about how you personally use the device, how you set it up, which apps you use, and your phone/data signal quality. everything else plays a minor role for battery.
Alright! So if I just ignore the encryption and install a ROM, it won't pose a problem at all? I can say, leave it encrypted and install a cm ROM without issue? And because of the encryption, do operations like installing a zip and formatting the device take a lot longer? I'm using a Galaxy Note 2 right now and the ROM installations take mere seconds to install, so a Nexus 6 might be something different.
H4X0R46 said:
Alright! So if I just ignore the encryption and install a ROM, it won't pose a problem at all? I can say, leave it encrypted and install a cm ROM without issue? And because of the encryption, do operations like installing a zip and formatting the device take a lot longer? I'm using a Galaxy Note 2 right now and the ROM installations take mere seconds to install, so a Nexus 6 might be something different.
Click to expand...
Click to collapse
Only problems you will notice is all the CM bugs.
H4X0R46 said:
Alright! So if I just ignore the encryption and install a ROM, it won't pose a problem at all? I can say, leave it encrypted and install a cm ROM without issue? And because of the encryption, do operations like installing a zip and formatting the device take a lot longer? I'm using a Galaxy Note 2 right now and the ROM installations take mere seconds to install, so a Nexus 6 might be something different.
Click to expand...
Click to collapse
formatting is how you decrypt. besides decrypting, theres no need to ever format your device. installing a zip it depends on the zip, generally its fast. flashing a zip is fast. what will be slowed down is tranafering a large file to your computer to or from a pc.
oh, and cm does get many bugs, often.
Oh yea! Bugs for sure! I'm running a cm nightly right now on my Note 2 and it's buggy as hell haha I just like messing with ROMs really, I will probably leave it stock and rooted for the most part Just like to see new ROMs and tweaks and stuff. Thanks guys! You all helped a ton! I will probably buy a Nexus 6!
H4X0R46 said:
Well, I've heard from many sources that the encryption in the phone just KILLS battery life, and if you turn off the encryption, it nearly triples the battery life. Is this true?
Click to expand...
Click to collapse
.
I have tried decryption with the Chroma and CM Roms. I did not notice more performance in daily use.
Then 5.1.1 arrives with some confusion because Google presented several factory images for the N6. I went back to stock and waited for the OTA.
After flashing the OTA and Franco's kernel my battery life was about the same.
Of course it depends on the daily use, but for me it was clear that not decrypting causes better battery life but the kernel.

[Q] simple question, anyone, please? What happened to the recovery partition?

What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
lukemovement1 said:
Not long go the pixel 5 and its been a while since I've played with flashing device partitions. Can anyone give me some pointers on the below?
Is the recovery now the boot partition and the boot partition boot_a?
Is their a way of rooting lineage os without having to modify the boot.img? (idk about amazon)
Do I need to re-root with magisk after each update?
Click to expand...
Click to collapse
Unfortunately you might have asked this in the wrong forum, thus no replies. Look here in Guides https://forum.xda-developers.com/t/guide-root-pixel-5-android-11-r.4187609/
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
lukemovement1 said:
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
Click to expand...
Click to collapse
You did originally ask about rooting so I thought I'd help out a little. What I don't understand is your animosity towards an attempt at posting a possible helpful link. Maybe a simple.. let me clarify my request since it might not have been clear. Oh well good luck.
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
xunholyx said:
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
Click to expand...
Click to collapse
Fastboot says that the recovery doesn't exists?
lukemovement1 said:
Fastboot says that the recovery doesn't exists?
Click to expand...
Click to collapse
I'm not sure what you mean.
fastboot reboot recovery won't work. It never has afaik
fastboot boot *twrp.img name* should work if you are trying the test build of TWRP
adb reboot recovery always works
You can't boot to recovery from bootloader with fastboot commands, but you can boot to it with adb commands while booted to /system
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
I'm guessing, as there's really not enough information to know for sure, but is this possibly a google treble question?
prior to treble, yes->recovery partition
with treble->no recovery partition, but another 'slot' for recovery.
cheers
Recovery and boot have merged into one partition, (on a/b devices at least) and you ship your boot and reco partitions in a unified boot image now which you can flash with fastboot flash boot x.img.
lukemovement1 said:
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
Click to expand...
Click to collapse
Ay, Ay, Ay,,,
To be fair, he was only trying to help, a simple this isn't helpful goes a long way. Being sour though, gets everyone absolutely nowhere.
And you did ask "Is their a way of rooting lineage os without having to modify the boot.img" -- I believe he was guiding you to that thread to possibly ask there as you may get a faster response. I think the question was just taken incorrectly is simply all. No harm, no foul.
bobby janow said:
You did originally ask about rooting so I thought I'd help out a little. What I don't understand is your animosity towards an attempt at posting a possible helpful link. Maybe a simple.. let me clarify my request since it might not have been clear. Oh well good luck.
Click to expand...
Click to collapse
You make more friends with lemonade, or something like that, you were trying to help, so good job in my eyes.
xunholyx said:
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
Click to expand...
Click to collapse
I'll help.
"Is their a way of rooting lineage os without having to modify the boot.img"
xunholyx said:
I'm not sure what you mean.
fastboot reboot recovery won't work. It never has afaik
fastboot boot *twrp.img name* should work if you are trying the test build of TWRP
adb reboot recovery always works
You can't boot to recovery from bootloader with fastboot commands, but you can boot to it with adb commands while booted to /system
Click to expand...
Click to collapse
I believe he was propbly doing a list of the partition table, and I haven't looked myself, but recovry is missing and instead of doing some research into this, he was simply asking for a simple answer, I feel this is the point of the Q & A forum, so good job to OP.. Personaly I feel this needed a simple answer, as someone coming from like a htc one m8 or htc 10 (like myself) what the hell happened to recovery.img -- a fair question in my eyes, everyone.
AsItLies said:
I'm guessing, as there's really not enough information to know for sure, but is this possibly a google treble question?
prior to treble, yes->recovery partition
with treble->no recovery partition, but another 'slot' for recovery.
cheers
Click to expand...
Click to collapse
Appreciate the info, thank you.
fadedave said:
Recovery and boot have merged into one partition, (on a/b devices at least) and you ship your boot and reco partitions in a unified boot image now which you can flash with fastboot flash boot x.img.
Click to expand...
Click to collapse
Thank you!
Guys, this is how it should work. This is the point of the Q&A thread, ask a question, get an answer, no need for anyone to get upset or to be sour. A question was asked, an answer was kindly given.
Kinda lost all faith in this forum tbh. Loads of incorrect and missing info, asking a question is a battle and half the ROMs and images don't work
lukemovement1 said:
asking a question is a battle
Click to expand...
Click to collapse
That's because you're making it a battle. As mentioned above, you were partly to blame for the initial misunderstanding. If people don't fully understand your question, instead of being upright rude, maybe rephrase or add more clarification as @andybones said.
lukemovement1 said:
half the ROMs and images don't work
Click to expand...
Click to collapse
There are 3 roms in this forum for Pixel 5. They all work and all are regularly updated. You are complaining about the time, sweat and money that developers put in to bring custom roms to us for free. If you don't like something about it, post a feedback or don't use it rather than be disrespectful.
lukemovement1 said:
Kinda lost all faith in this forum tbh. Loads of incorrect and missing info
Click to expand...
Click to collapse
Then leave, or contribute to providing the correct and missing info, rather than, again, complain about free info people bring together in their spare time. None of us here are paid to bring info and provide code. We all do it in our spare time and share our knowledge because we want to make a positive community.
Your total disrespect, negativity and entitlement is not welcome here.
Touché
If you post was removed, it's because I decided to do some house-cleaning -- no one did anything wrong.
And I fixed the title to the thread, so that it's easier on those seeing it and understand what the "simple question" actually is.
Not sure why people get all salty over a simple question...
There is no /recovery partition on Pixel devices. Recovery coresides with the kernel in /boot. Previously, with Android 10, it was possible to install a custom recovery alongside a rooted kernel (such as using Magisk) but Android 11 broke this.
The best and most foolproof option in my opinion is to only temporarily boot a custom recovery to perform modifications. This is what I do every time I get an update on my Pixel 5 - I download the OTA, boot TWRP, install the OTA, reboot to system, let the update finish, boot TWRP again, and flash Magisk.
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
agree , the people don't want to help,

Categories

Resources