Root
- Thread starter Chainfire
- Start date
. Has it been updated for Q kernel or is it still using older one?
CF-Auto-Root is kernel agnostic. Just run it again after upgrading to the new firmware. Yes, you will be running the new kernel afterwards.
The manual method I posted before CFAR was ready however, will put you back on the old kernel.
The manual method I posted before CFAR was ready however, will put you back on the old kernel.
So which are the absolute min necessary files necesarry to flash Q (including the kernel) and then use CFAR to root?
If flash-all script won't work as mine doesn't should flash all the files in the image zip. Why do a partial upgrade?
You just extract cfar and get the current boot.img out of it. Use that
Sent from my Nexus 9 using XDA Free mobile app
Don't believe there is a boot image in CFAR. Believe he is patching whatever kernel you have. Would have to extract the image to see what is inside. More trouble than it is worth.As Chainfire said it is boot image agnostic.
You're correct I spoke before I extracted it. My badDon't believe there is a boot image in CFAR. Believe he is patching whatever kernel you have. Would have to extract the image to see what is inside. More trouble than it is worth.As Chainfire said it is boot image agnostic.
Sent from my Nexus 5 using XDA Free mobile app
Lol. I was guessing but that was how I interpreted agnostic. :laugh:
Now the problem I've got, I've tried cfar twice now. Both times it's ended up with a bootloop into recovery. And there's no way to get out of it without flashing the factory image. Factory reset doesn't work. Anyone else having issues? The old image files still work to get root, but of course you end up with the old kernel.
Sent from my Nexus 5 using XDA Free mobile app
Sent from my Nexus 5 using XDA Free mobile app
I'm going to try in a little while. I'm uploading my Tibu update to Dropbox. Then I'm gonna manually upgrade as I'm getting the space error and there is no fix. My guess they gonna have to repartition in another update of the bootloader. Then I'm gonna try CFAR.
If you used "fastboot flash" instead of "fastboot boot", I'm going to ask you to hand in your geek card.
i'm wondering if folks here who haven't been successful in manually flashing the files included in the Q update are erasing each partition first (including the user partition)? i mention it only because i don't see many folks explicitly stating they did this erase step. note that the -w option in the flash-all.bat file included in the update will effectively do this when flashing the new image files.
so, i think you should try this, you will lose data but it works:
step #1
step #2
i followed this with a factory reset before leaving recovery (i don't know if that's necessary since i erased the userdata partition, but why not).
after completing these steps, i re-rooted using CF Auto Root without difficulty.
so, i think you should try this, you will lose data but it works:
step #1
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
step #2
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase userdata
fastboot erase vendor
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
i followed this with a factory reset before leaving recovery (i don't know if that's necessary since i erased the userdata partition, but why not).
after completing these steps, i re-rooted using CF Auto Root without difficulty.
I can say I did not erase each partition. Just flushed the images
Sent from my Nexus 9 using XDA Free mobile app
---------- Post added at 09:24 AM ---------- Previous post was at 09:22 AM ----------
No, I used boot and not flash
Sent from my Nexus 9 using XDA Free mobile app
CFAR worked perfectly for me also. I also erased but changed the partitions that could be formated to format instead of erase. Userdata is optional and won't erase unless you run CFAR with locked bootloader. Thanks again Chainfire.
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata (optional)
Yep, that was the problem. I was lazy. Just flashed the image with fastboot -w and worked perfectly for me too.CFAR worked perfectly for me also. I also erased but changed the partitions that could be formated to format instead of erase. Userdata is optional and won't erase unless you run CFAR with locked bootloader. Thanks again Chainfire.
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata (optional)
Sent from my Nexus 5 using XDA Free mobile app
Kewl. I had to sweat a minute and stop and download another image zip. Even tho MD5 of zip matched the Vendor image was corrupted.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone