Hi guys
I have stock N4F26I nexus 6p
Is there an April security patch out yet? Or even the March one?
I see the link but can't find my 6p version, I want to use flash fire because the update is in the notification shade.
I'm rooted so confused on what image to flash.
Cheers
N4F26U is available. There's that thread called [INDEX] Nexus 6P which references all images...
Thanks, but can I flash that with my current build number?
I'm a bit confused sorry
Sent from my Nexus 6P using XDA Labs
You can always flash images whatever your root state or notifications you have.
I don't recommend FlashFire as it left me in a bootloop several times. In any case you shouldn't flash radio and bootloader with FlashFire. So for these two you'll need a PC to fastboot or TWRP zippable versions (which are not always available)
If you have a PC, the manual way is safer IMO and takes only a few commands. Download factory image. Modify flash-all script and remove -w if you want to keep your data.
Run flash-all
Fastboot TWRP
In TWRP sideload SuperSU.
Done.
Another way if you have a PC is to unroot, flash original recovery and accept OTA. After that fastboot TWRP and sideload SuperSU.
Thank you very much for help and detailed explanation much appreciated.
Sent from my Nexus 6P using XDA Labs
Related
Hi,
I was pretty dismayed on two counts :
1. The stock factory image doesn't work without editing
2. It's uber-fiddly to get encryption disabled unless you really know what you are doing
There's the problem, so the solution has to be a stock factory fastboot install with no encryption - easy!! This I have created.
Download
Extract the zip
Go into the folder where the image files and flash-all files are
Open Command Prompt (Windows) or Terminal (Linux or OSX)
Run flash-all.bat for windows or .\flash-all.sh for Linux or OSX
Once flashed you will have a stock un-encrypted Nexus 9 LTE.
Download the zip from :-
https://drive.google.com/file/d/0B1b6rgRiJPLsRHNXMER3VHdFUGM/view?usp=sharing
This says VolantisG, can I use that on the Wifi version?
How does this actually make the tablet faster? Will I still get updates from Motorola/Google OTA?
Hi, can i just flash it using TWRP? Thanks
gjweir9 said:
Hi, can i just flash it using TWRP? Thanks
Click to expand...
Click to collapse
No, you can't flash it using twrp. It's the stock factory image with a modified boot image. You have to flash with fastboot.
Sent from my Nexus 5 using XDA Free mobile app
I have uploaded the latest androd 6.0.1 MMB29K.
I have twrp installed - the latest I believe.
super su - 2.46 pro
I installed the ElementX kernel - can't remember witch page I followed to root my nexus 9. but it suggested this.
Now I can't set a pin for my sudoers
tried uninstalling and reinstalling no luck.
I have ex kernel manager and it says there is a new version available, but I need superSU 2.61 - witch means the new beta version.
Looking at the thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
looks like I have refrash a stock boot
"
If you are coming from any SuperSU install in /system, you must re-flash the stock system partition contents prior to installing this.
"
how do I do this ?
What does the new kernel give me ?
Any idea on why my supersu doesn't let me use pin codes ?
KeyzerSuze said:
I have uploaded the latest androd 6.0.1 MMB29K.
I have twrp installed - the latest I believe.
looks like I have reflash a stock boot
"
If you are coming from any SuperSU install in /system, you must re-flash the stock system partition contents prior to installing this.
"
how do I do this ?
What does the new kernel give me ?
Any idea on why my supersu doesn't let me use pin codes ?
Click to expand...
Click to collapse
Latest TWRP for Nexus 9 is twrp-2.8.7.1-flounder
Get the latest factory image and unzip the contents a few times then use fastboot to flash both boot.img and system.img.
From TWRP Flash SuperSU-v2.62-3 first and then the latest ElemetalX kernel (if you want it, not needed for root).
Never used pin codes with supersu, so don't know about that.
corkiejp said:
Latest TWRP for Nexus 9 is twrp-2.8.7.1-flounder
Get the latest factory image and unzip the contents a few times then use fastboot to flash both boot.img and system.img.
The latest SuperSU-v2.62-3
From TWRP Flash that first and then the latest ElemetalX kernel (if you want it, not needed for root).
Never used pin codes with supersu, so don't know about that.
Click to expand...
Click to collapse
Flashing vendor.img is a good idea as well, just to make sure everything is synced up.
I'm I going to have to reinstall all my apps again ?
Sent from my Nexus 6P using Tapatalk
KeyzerSuze said:
I'm I going to have to reinstall all my apps again ?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Flashing just boot.img, system.img and vendor.img, will not wipe data.
And leaves data untouched, so won't need to reinstall apps again. Just don't flash the full factory image.
(Note: Flashing the full factory image can also be done without wiping data)
Thanks did it and all good.
Sent from my Nexus 6P using Tapatalk
Read before continue:
http://forums.yuplaygod.com/threads/15124/
http://forum.xda-developers.com/showpost.php?p=63197935
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Requirements:
Completely stock, untouched device (OnePlus One).
Unlocked bootloader.
Rooted boot images:
cm-12.1-YOG7DAS2K1-bacon-boot-debuggable-rooted.img
Usage:
Download the rooted boot image that matches with your installed build.
Flash using fastboot:
Code:
fastboot flash boot XXX.img
Install the SuperUser manager app: https://play.google.com/store/apps/details?id=me.phh.superuser
Profit!
To take incremental OTA:
Download the stock boot image that matches with your installed build. Either extract from signed fastboot flashable zips or get from this thread.
Flash using fastboot:
Code:
fastboot flash boot XXX.img
You should be able to take & install the OTA, if /system isn't tampered previously.
Note:
The rooted boot images are based on official boot-debuggable images & super-bootimg by @phhusson.
The whole thing is in alpha stage & still WIP, so expect bugs.
Not all apps are compatible with systemless root approach, so root access mayn't be visible to them.
Please provide detailed feedback to me, @phhusson & the concerned app developer.
Reserved for future v1.
Reserved for future v2.
I read the second and third links, but had to sign up to get the first (not with it at this time) and I'm kinda confused. What exactly is wrong with the "old way" of rooting? Is it just for things like Android pay to work or is there other benefits?
Sent from my LG-D800 using Tapatalk
@FlashHappy78
In a nutshell, traditional rooting method modifies the /system partition. As a consequence, subsequent OTAs will fail. In case of Cyanogen OS devices, it may be easier to grab the full signed zip later & update manually, but for others they need to re-flash the stock system.img to take the OTA.
In this new approach, only the boot image is modified but /system is untouched. Thus any event/application that verifies the integrity of /system partition (like OTA, Android Pay etc.) is ready to be executed on top of the rooted device without any hitch.
If OTA contains an updated boot image, then user need to re-flash the stock boot image first which is considerably easy to re-flash than the whole system.img.
I've always been under the assumption that oem OTA updates usually break root anyways, plus patch whatever exploits were used to gain root (especially from OEM's like Samsung and LG), so because of that, I never take OTA updates unless they come from custom ROM devs.
Anyways, thanks for the clarification. I don't use android pay and I use only custom ROMs, so this probably isn't for me then. Thanks again mate.
Sent from my LG-D800 using Tapatalk
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
poulopoulosa said:
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
Click to expand...
Click to collapse
Flash supersu at least the stable 2.64
poulopoulosa said:
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
Click to expand...
Click to collapse
As suggested by @hellcat50, I'll not provide any more update on this as newer SuperSU can patch the boot image on the fly.
Hi! I have an LG G5 h850 and I've flashed this ROM (a full flashable zip of Android Nougat 7.0 stock). The problem is I can't seem to root my phone.
If I flash any SuperSU zip with TWRP 3.1.0.0, the phone won't be able to boot afterwards (it will get stuck at the LG logo).
I've iunlocked my bootloader using the official procedure (fastboot getvar unlocked returns "yes") and I've also flashed no verity opt encrypt 5.1 after wiping data: my TWRP can access internal storage.
What am I missing? Is there a specific SuperSU zip which works on a Nougat h850? Has the problem got something to do with dm-verity?
I have an LG G5 H850 with TWRP 3.1.0..0 and SuperSU 2.65 installed. I did not install the no-verity and my phone is operating normally. Just need a way to get rid of the "your phone is unlocked" screen on boot up.
Sent from my LG-H850 using Tapatalk
N or M?
Stransky said:
I have an LG G5 H850 with TWRP 3.1.0..0 and SuperSU 2.65 installed. I did not install the no-verity and my phone is operating normally. Just need a way to get rid of the "your phone is unlocked" screen on boot up.
Sent from my LG-H850 using Tapatalk
Click to expand...
Click to collapse
Are you sporting Nougat or Marshmallow? With Android M I rooted it with no problems.
Nougat and i had no problems rooting.
Sent from my LG-H850 using Tapatalk
Stransky said:
Nougat and i had no problems rooting.
Sent from my LG-H850 using Tapatalk
Click to expand...
Click to collapse
That's astounding. Do you remember the procedure you followed? Is the ROM the same I used (LG-H85020A-Flashable.COMPLETE.zip)? Is the precise SuperSU version UPDATE-SuperSU-v2.65-20151226141550?
Patching sepolicy failure
I've proceeded to reinstall N and SuperSU 2.65 and I see the following message:
Code:
- Patching sepolicy
--- Failure, aborting
Given Android N requires systemless mode, hence boot image patching, could this be the cause? What should I do?
HisDudeness3008 said:
That's astounding. Do you remember the procedure you followed? Is the ROM the same I used (LG-H85020A-Flashable.COMPLETE.zip)? Is the precise SuperSU version UPDATE-SuperSU-v2.65-20151226141550?
Click to expand...
Click to collapse
The ROM is the same (H85020a) but my phone was updated OTA.
Sent from my LG-H850 using Tapatalk
---------- Post added at 06:22 PM ---------- Previous post was at 06:15 PM ----------
Further to my last I used @autoprime's unlocking the G5 bootloader thread and followed the instructions on it, including the installation of TWRP etc.
Sent from my LG-H850 using Tapatalk
Enter password to unlock
Stransky said:
The ROM is the same (H85020a) but my phone was updated OTA.
Sent from my LG-H850 using Tapatalk
Click to expand...
Click to collapse
I see... I couldn't update OTA because when it had to install the downloaded update it just rebooted to TWRP.
Anyway, after getting that error message, I flashed a newer version of SuperSU. It patched sepolicy successfully and even booted (I don't know what I did different than other times). Anyway, it prompted me with an "Enter password to unlock message", with some attempts already out (23/30).
Could it be because I have decrypted data partition? I read the decryption and root access are mutually exclusive. I decripted just because, after the 30th failed boot attempt, I tried it just to change something and see if it worked.
If I have to choose between the two, I'll choose root access. How do I restore encryption?
Sorry, have no idea, I don't use encryption.
Sent from my LG-H850 using Tapatalk
Stransky said:
Sorry, have no idea, I don't use encryption.
Sent from my LG-H850 using Tapatalk
Click to expand...
Click to collapse
I mean the default setup of the G5, whereas TWRP can't access internal storage and will ask you for a password upon starting, to which you have to hit "cancel".
When I hit cancel in TWRP in answer to the password I then swipe below to allow modifications. At least that is what I am offered on the swipe window.
Sent from my LG-H850 using Tapatalk
Yeah, that is indeed the default behaviour. However, at some point I've flashed no-verity-opt-encrypt zip. This removes the encryption. TWRP doesn't have to ask you for a password you do not know, and can thus modify /data partition. This, however, prevents you from rooting your device. And, apparently, prevents me from booting my phone right now. Is there any way to revert the effects of no-verity-opt-encrypt?
I am sorry, I am not even remotely akin to a developer, I only follow their instructions so am not aware if it is possible to revert the no- verity effects. The only suggestion I can come up with is to do a factory reset backbto stock Nougat and then redo the installation of TWRP etc omitting "no-verity" option. But I would check with someone like Autoprime first to see if this will work and not create more problems. Sorry I can't be of more help.
Sent from my LG-H850 using Tapatalk
No problem, you've been of enough help! I thank you for your time.
I know, I'm not akin to a developer as well, but I have the bad habit of getting myself into developer trouble
Solved one: I unbricked my phone. Followed this excellent guide from by dksoni411. I thank him with all my heart, as well as AutoPrime, Hyelton, bullghost and anyone else who contributed.
Solved two: I finally managed to root my h850. Don't know what I did different from the other dozen times I tried. From stock Nougat 7.0 I rebooted to fastboot mode via adb, flashed TWRP in fastboot, booted into recovery without allowing normal boot to happen before it, flashed SuperSU (v2.79-20161211114519), didn't wipe cache or dalvik, and rebooted. Upon boot, phone reset once and then booted straight into Nougat, with SuperSU apk installed. Yay!
HisDudeness3008 said:
Solved one: I unbricked my phone. Followed this excellent guide from by dksoni411. I thank him with all my heart, as well as AutoPrime, Hyelton, bullghost and anyone else who contributed.
Solved two: I finally managed to root my h850. Don't know what I did different from the other dozen times I tried. From stock Nougat 7.0 I rebooted to fastboot mode via adb, flashed TWRP in fastboot, booted into recovery without allowing normal boot to happen before it, flashed SuperSU (v2.79-20161211114519), didn't wipe cache or dalvik, and rebooted. Upon boot, phone reset once and then booted straight into Nougat, with SuperSU apk installed. Yay!
Click to expand...
Click to collapse
Tnx man! :good: U should post step by step what u did to root as separate thread, cuz U have been a tremendous helper, u know?? U solved Huuuuuge problem , so U can be great helper to those who could came into similar troubles :victory:
When attempting to flash TWRP through Odin I get a message on the screen that says, “Only official released binaries are allowed to be flashed(RECOVERY)”, after I hold the volume up, Bixby, and power buttons. Does anyone know why??
1. I have OEM Unlock on, but it somehow bypassed 7 days when I flashed from 8.0 to 9.0 Pie. It was not there until I flashed.
2. Download page says, “OEM LOCK: OFF”.
3. I have flashed back to stock 9.0 Pie firmware each time it failed and OEM Lock was still on the whole time.
4. I have even tried to trick to set the date back a month from latest security check date.
Not sure what I am doing wrong... Even though it says OEM is unlocked, do I still have to wait 7 days?
Thanks in advance.
JTM206 said:
When attempting to flash TWRP through Odin I get a message on the screen that says, “Only official released binaries are allowed to be flashed(RECOVERY)”, after I hold the volume up, Bixby, and power buttons. Does anyone know why??
1. I have OEM Unlock on, but it somehow bypassed 7 days when I flashed from 8.0 to 9.0 Pie. It was not there until I flashed.
2. Download page says, “OEM LOCK: OFF”.
3. I have flashed back to stock 9.0 Pie firmware each time it failed and OEM Lock was still on the whole time.
4. I have even tried to trick to set the date back a month from latest security check date.
Not sure what I am doing wrong... Even though it says OEM is unlocked, do I still have to wait 7 days?
Thanks in advance.
Click to expand...
Click to collapse
I wanted to know if you are only rooting the device or installing update ROMs or not.
If you are installing ROMs then you don't need to root your device there is another way too.
Sent from my P5 mini using premium XDA app
PrashannaGP said:
I wanted to know if you are only rooting the device or installing update ROMs or not.
If you are installing ROMs then you don't need to root your device there is another way too.
Sent from my P5 mini using premium XDA app
Click to expand...
Click to collapse
I am trying to run Magisk to hide the app to play PokémonGO with a joystick. Want to root it because it seems like the safest way.
JTM206 said:
I am trying to run Magisk to hide the app to play PokémonGO with a joystick. Want to root it because it seems like the safest way.
Click to expand...
Click to collapse
then you have to download stock rom for your device and also TWRP and replace the recovery file with twrp recovery and flash the recovery.img (downloaded recovery.img) for your device not stock rom with sp flash tool and flash the SuperSU.zip from twrp and again install magisk and its module. Done:good::good:
You are not supposed to allow it to boot with full stock firmware, ever. You should have intercepted the reboot and immediately flashed, twrp, magisk and the kernel patch.
pauaxe said:
You are not supposed to allow it to boot with full stock firmware, ever. You should have intercepted the reboot and immediately flashed, twrp, magisk and the kernel patch.
Click to expand...
Click to collapse
Yes but we can only do one thing. That is to unlock bootloader and then flash twrp from fastboot using
fastboot flash recovery ---------.img
fastboot reboot
adb devices
adb reboot recovery
press on INSTALL
select MAgisk.zip
reboot.
Done
Sent from my [device_name] using XDA-Developers Legacy app
PrashannaGP said:
Yes but we can only do one thing. That is to unlock bootloader and then flash twrp from fastboot using
fastboot flash recovery ---------.img
fastboot reboot
adb devices
adb reboot recovery
press on INSTALL
select MAgisk.zip
reboot.
Done
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Well if he is getting "Only official released binaries are allowed to be flashed(RECOVERY)" then he'll probably have to wait it out for 7 days anyway. That's why I said he shouldn't have let it boot, to avoid waiting 7 days.
Also there is no fastboot for Samsung phones.
pauaxe said:
Well if he is getting "Only official released binaries are allowed to be flashed(RECOVERY)" then he'll probably have to wait it out for 7 days anyway. That's why I said he shouldn't have let it boot, to avoid waiting 7 days.
Also there is no fastboot for Samsung phones.
Click to expand...
Click to collapse
Yes. That's right . Patience is important
Sent from my [device_name] using XDA-Developers Legacy app