updated with 5.0.1 boot.img
fastboot flash attached boot.img, then factory reset to get rid of encryption. dont know what changed from R as i havent checked, but the md5sums were different between the two.
to root flash chainfires attached zip in recovery
Many thanks for posting this. I can now root properly on Q.
Im on Q Build tried this patch but it put me bootloop. Flashed back to CF L boot patch and all OK. So I'm running Q build unlocked/rooted with CF L patched kernel. Anybody else try this patch?
I couldn't get back earlier as it hung on boot for me.
OK, I'm gonna pull the images until I get home. I flashed it to mine and its OK, I'm gonna have to check out the boot.img's maybe I uploaded the wrong ones. But I wasn't coming from the q kernel. Probably has something to do w/ encryption.
You guys who bootlooped, was your data encrypted?
Yes. I am encrypted. But I flashed the elementalx kernel and bootloop was gone and I had root. For the ones who are in the bootloop
Gesendet von meinem LG-D802 mit Tapatalk 4
yep im encrypted
That's what I figured. Easy fix I think just cant fix it till I get off work. Thanks for feedback guy's
Thanks look forward to it.
Encrypted also. My problem was it hung on boot and even after getting back to bootloader I couldn't get my laptop to see the tablet. That's OK, I got home from work and flashed it again with Q.
Appreciate you working on it.
Yup think I forgot to leave encryptable as a fs mount option, just deleted it for myself not thinking. Should have left it for those who were encrypted. Will update later today. The images I had up will work fine for anyone not encrypted who may have already downloaded them.
Thx
should be fixed. started with fresh q, rooted w/ my attached img's, all good. then factory reset, got rid of encryption.
That did it. I am unlocked, rooted, encrypted, and running Q build with Q kernel. Thanks for the support.
Also chainfire updated to Q
Perfect. I works very well. Root it is mandatory in order to use some features of my Nexus 9 (for example for using my airplay Denon receiver) and I prefer to have my table unencrypted, in order to save CPU and, therefore, battery. I suppose that with the LRX21Q and the tablet without encryption the performance it is going to be very nice.
Thanks for the post.
thebrainkafka said:
Also chainfire updated to Q
Click to expand...
Click to collapse
I am still only seeing LXR21L on his site. Where did you see the LXR21Q?
Sent from my Nexus 9 using Tapatalk
http://forum.xda-developers.com/showthread.php?p=56772688
updated to 5.0.1
Edit: moved and improved
http://forum.xda-developers.com/nexus-9/development/stock-kernel-encryption-faster-cache-t2965085
Related
What. In. The. World. Got the "System update downloaded" notification this afternoon, and was puzzled since I got this a little over three weeks ago for 4.3, an experience that soft bricked my phone and ruined by life for a few days:
http://forum.xda-developers.com/showthread.php?t=2387196&page=3
Well, lo and behold, today's system update claims to be for 4.3 again:
Only I'm already ON 4.3.
Finally got everything rooted again and set up the way I want, and it's like Google knows it's time to come in and bork my phone again. I did a little poking and saw that this is no doubt the update from JWR66V to JWR66Y:
http://www.droid-life.com/2013/08/2...ta-updates-for-the-nexus-7-hspa-galaxy-nexus/
Only after the last experience, I'm friggin terrified to mess with this and possibly end up in a bootloop or stuck at the X screen forever again. (I'm rooted, no custom ROM, just custom launcher.) EDIT: I should add that, since the last update, I've updated my radios to be able to use 4G LTE, installed the Android browser and all my bookmarks, and made a slew of other customizations, so I'm annoyed that this update comes three weeks on the heels of everything I set up.
Should I try the OTA install or flash the OTA zip files in CWM recovery like the article suggests? Most pain-free ways to ensure my current setup is reinstated without too many gray hairs? Any suggestions welcome. Thanks in advance!
It won't install because your rooted. The new root method relies on the recovery from boot.p file in system that SU changes.
You can flash this update zip file that has been modified not to check that file http://forum.xda-developers.com/showthread.php?p=44886292
BLACKED OUT LTE N4
The update is occurring because there is a new OTA that is build JWR66Y whereas yours is the V build.
Sent from my Nexus 4 using Tapatalk 4
zephiK said:
The update is occurring because there is a new OTA that is build JWR66Y whereas yours is the V build.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, thanks--I noted that. My question at the bottom of my post is, what's the best way to ensure I can back up/capture all the customizations I made since so I don't have to go through the nightmare of trying to take three weeks to set everything up again?
spaceman860 said:
It won't install because your rooted. The new root method relies on the recovery from boot.p file in system that SU changes.
You can flash this update zip file that has been modified not to check that file http://forum.xda-developers.com/showthread.php?p=44886292
BLACKED OUT LTE N4
Click to expand...
Click to collapse
OK...I'm guessing that notification will go away once I've flashed that ZIP? My real question is whether once that's done if I have to re-set everything up all over again or if there's a way to backup my new radios/browser/etc.
nikonjunkie said:
OK...I'm guessing that notification will go away once I've flashed that ZIP? My real question is whether once that's done if I have to re-set everything up all over again or if there's a way to backup my new radios/browser/etc.
Click to expand...
Click to collapse
I have read your edits to the OP and you have changed system files so the update won't install. You modified the build prop for lte and browser app maybe other stuff too. With this update your OK with not having the correct radio.
BLACKED OUT LTE N4
Just received ota update to 4.4.4 45MB for xt 1045 lte usa version
djcody said:
Just received ota update to 4.4.4 45MB for xt 1045 lte usa version
Click to expand...
Click to collapse
The update isn't working for me, even after reflashing the stock recovery. Did you have to do anything special to get it to work, or have you not modified the ROM at all?
Mogster2K said:
The update isn't working for me, even after reflashing the stock recovery. Did you have to do anything special to get it to work, or have you not modified the ROM at all?
Click to expand...
Click to collapse
I had the stock 4.4.3 ROM rooted and with the Xposed Framework installed. No custom recovery or custom kernel ever installed (I always used "fastboot boot /path/to/recovery.img" rather than installing a recovery). The update worked fine for me. All I had to do was (after updating to 4.4.4) go into the Xposed framework installer, tell it to update/install the framework. I installed the 4.4.4 update through the OTA notification I received, not through the link in this thread. For me, the update was 41.1MB not 45MB. I downloaded the OTA over WiFi.
Before I installed the update, I booted ClockworkMod Recovery (again, booted not flashed) and made a nandroid backup. It couldn't backup my /data partition because it's encrypted, so I also made a full backup with Titanium Backup.
Full stock, no mods yet
Mogster2K said:
The update isn't working for me, even after reflashing the stock recovery. Did you have to do anything special to get it to work, or have you not modified the ROM at all?
Click to expand...
Click to collapse
I had same problem
I was on 4.3.3 stock using exposed installer, I used MotoToolAioV3 to restore stock recovery then took OTA, during install I kept getting an error.
The solution for me was to download stock recovery from here http://forum.xda-developers.com/showpost.php?p=53702274&postcount=268
extract the recovery then use MotoToolAioV3 to flash it, then accept the OTA and it should work, then if you're using exposed installer do what the other poster said and re-install xposed. Hope this helps.
castuis said:
I had same problem
I was on 4.3.3 stock using exposed installer, I used MotoToolAioV3 to restore stock recovery then took OTA, during install I kept getting an error.
The solution for me was to download stock recovery from here http://forum.xda-developers.com/showpost.php?p=53702274&postcount=268
extract the recovery then use MotoToolAioV3 to flash it, then accept the OTA and it should work, then if you're using exposed installer do what the other poster said and re-install xposed. Hope this helps.
Click to expand...
Click to collapse
Giving this a try, will report back
i just sad, I didn't mod anything because there is not yet full working ROM without bugs, mean the big one.
Anyway my One+ is on the way, Moto G is a good phone after breaking down my N4, going to sell soon
Got the update yesterday too working find no changes
Dialer still buggy
sonygoup said:
Got the update yesterday too working find no changes
Dialer still buggy
Click to expand...
Click to collapse
As I understand it, the main changes from 4.4.3 are compatibility with more SD cards, and some security updates to things like OpenSSL. I'm now able to use my 64GB Samsung EVO class 10 (MB-MP64DA/AM).
I managed to get the update installed after completely reflashing to stock (leaving the bootloader unlocked.)
sonygoup said:
Got the update yesterday too working find no changes
Dialer still buggy
Click to expand...
Click to collapse
The dialer is not buggy if you enable the animations in developer options (reset them to their default setting).
bozzykid said:
The dialer is not buggy if you enable the animations in developer options (reset them to their default setting).
Click to expand...
Click to collapse
Thanks dude
I turned it off because I hate it
New update is pretty great. Previously on 4.4.3 the radio would drop all connections seemingly at random when starting up a music app or YouTube, but after upgrading to 4.4.4 the radio seems to hold a much more consistent connection with fewer drops (none so far) . I previously thought this might have been a faulty SIM
:thumbup:
I have been trying to go back to Marshmallow from the N beta 3 preview for a few days now, but it doesn't seem to be working any way I try. I originally tried to use the OTA method by unenrolling my device because that is the way I got the preview to begin with. Every time I tried that, though, it would end in an error after trying to install the update. So i tried flashing the Marshmallow images manually using fastboot. I flashed everything, including the bootloader, radio, recovery, boot, system, vendor, cache, and userdata, but when I tried rebooting, it would be stuck on the Google logo. Can someone please tell me if I am doing something wrong or can maybe help somehow? Thanks in advanced!
asadabbas95 said:
I have been trying to go back to Marshmallow from the N beta 3 preview for a few days now, but it doesn't seem to be working any way I try. I originally tried to use the OTA method by unenrolling my device because that is the way I got the preview to begin with. Every time I tried that, though, it would end in an error after trying to install the update. So i tried flashing the Marshmallow images manually using fastboot. I flashed everything, including the bootloader, radio, recovery, boot, system, vendor, cache, and userdata, but when I tried rebooting, it would be stuck on the Google logo. Can someone please tell me if I am doing something wrong or can maybe help somehow? Thanks in advanced!
Click to expand...
Click to collapse
Not trying to say you're lying but are you sure you flashed everything? Are you using the flash all script or are you doing each image manually?
Mainly you need to flash boot, system, vendor, and userdata. Userdata just wipes that partition.
The N bootloader and radio should be compatible with the latest marshmallow release.
My best guess is if you used the flash all it didn't work, because it never works.
If not that then maybe you got a corrupted file? Try redownloading it and try again.
Sent from my Nexus 6P using Tapatalk
Nah I don't use the flash all script. I flashed everything manually and I didn't forget anything. I actually tried this twice and used a new file the second time so it's really weird. I have no idea what's wrong
I am having the SAME EXACT issue. Found this on a search. Any solutions?
asadabbas95 said:
Nah I don't use the flash all script. I flashed everything manually and I didn't forget anything. I actually tried this twice and used a new file the second time so it's really weird. I have no idea what's wrong
Click to expand...
Click to collapse
Try this command first: "fastboot format userdata" - then flash all images, exept "userdata.img".
ADB Sidleoading this file worked for me https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
I'm.at work or else I would try that method can anyone try it and see what happens . I'm trying to go back to mm also
Sent from my Nexus 6P using Tapatalk
ClassickWORLD said:
ADB Sidleoading this file worked for me https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
So you wiped everything and used that ? Can we just flash that or does it have to be side loaded I'm.on N it works but I don't wanna go back to MM cuz it's causing issues to others from what I heard I can keep the bootloader and radio but everything else you gotta flash would you lose root or have to re unlock the bootloader?
Sent from my Nexus 6P using Tapatalk
Okay so I'm not the only one who's having this problem. Did the sideloading method format the sd card?
havy15 said:
So you wiped everything and used that ? Can we just flash that or does it have to be side loaded I'm.on N it works but I don't wanna go back to MM cuz it's causing issues to others from what I heard I can keep the bootloader and radio but everything else you gotta flash would you lose root or have to re unlock the bootloader?
Click to expand...
Click to collapse
Download the file and rename it whatever you want. I changed it to update.zip.
Go to stock recovery and then select update from adb.
Then type ---> adb sideload "name of zip".
You will then be downgraded to stock MM with everything working.
Well at least that's what worked for me. Because I was on Android N Preview 3. It was too buggy so I tried to manually flash 6.0.1. but kept getting stuck on the white Google logo. The above method worked for me.
Are you rooted still? Someone told me if I'm going to pure rom all I need to do is wipe like normal like when you u flash a ROM and with gaps and I'll be fine with the vender image . Or do I have to do it your way . Did you go back to stock mm or a rom ?
Sent from my Nexus 6P using Tapatalk
ClassickWORLD said:
ADB Sidleoading this file worked for me https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
This didn't work for me either. I tried sideloading and it was sending the file, but it stopped at .02% and it gave me an error 7 and the download failed...This is really starting to annoy me because so many apps are really buggy for me on N
Yeah Snapchat is super buggy and my phone stays crashing when it warms up lol . But I'm rooted unlocked bootloader Android N I'm trying to stay rooted unlocked bootloader and go back to MM how can I do that ?!?!?! ?? Like I'm legit frustrated lol
Sent from my Nexus 6P using Tapatalk
havy15 said:
Yeah Snapchat is super buggy and my phone stays crashing when it warms up lol . But I'm rooted unlocked bootloader Android N I'm trying to stay rooted unlocked bootloader and go back to MM how can I do that ?!?!?! Like I'm legit frustrated lol
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Lol trust me i know. I've been trying for so long and it's so frustrating that I can't do anything except wait for the official release to come out
asadabbas95 said:
Lol trust me i know. I've been trying for so long and it's so frustrating that I can't do anything except wait for the official release to come out
Click to expand...
Click to collapse
are you trying to back to stock or another mm rom
havy15 said:
are you trying to back to stock or another mm rom
Click to expand...
Click to collapse
I tried both..neither worked
asadabbas95 said:
I tried both..neither worked
Click to expand...
Click to collapse
well i just read to go back to a mm rom you just have to wipe like when you flash a rom in general then go and flash rom gapps and vender and it should be solid
havy15 said:
well i just read to go back to a mm rom you just have to wipe like when you flash a rom in general then go and flash rom gapps and vender and it should be solid
Click to expand...
Click to collapse
nah i tried that and was stuck on the google logo
asadabbas95 said:
nah i tried that and was stuck on the google logo
Click to expand...
Click to collapse
really thats what people are telling me to do and they say its working. you sure you are flashing the correct vender for that rom?
havy15 said:
really thats what people are telling me to do and they say its working. you sure you are flashing the correct vender for that rom?
Click to expand...
Click to collapse
yup flashed everything correctly. Try flashing and tell me if it works for you
Just updated my 6p to final Nougate. Has anyone posted updated instructions on rooting it? I want to enable double tap to wake (assuming it is still there in Nougat) and also swap the recents and back button. My phone is encrypted. Not sure that makes any difference.
Sorry to be rude.. But did you even look on the first page?
http://forum.xda-developers.com/showthread.php?t=3446824
kyle4269 said:
Sorry to be rude.. But did you even look on the first page?
http://forum.xda-developers.com/showthread.php?t=3446824
Click to expand...
Click to collapse
I did look but obviously not good enough. So sorry for wasting folks time with dupe question. I'll try to be more careful.
Zyphur said:
I got everything working well for me now from completely stock N to rooted N. Went from rooted with PureNexus to stock 6.0.1, erasing everything, then got the Nougat OTA because I was in the Beta program. To get rooted 7 working I did the following: Fastboot flash the Modified N Boot from DigitalHigh, flash TWRP 3.0.2-1, flash SU 2.76. Done. TWRP and Root stick, no bootloops, all good. Have since also installed EX, still all good.
Click to expand...
Click to collapse
I did this and it worked perfectly. Was on fresh stock Nougat OTA. With bootloader already unlocked.
Yeah its easy. I took the Nougat update over the phone after returning to full stock and used the latest files of TWRP and SuperSU 2.76 and just did everything like MM root and all was ez pz. The guide should tell you basically the same thing.
Anyone know if double tap to wake is still in nougat?
rykr said:
Anyone know if double tap to wake is still in nougat?
Click to expand...
Click to collapse
I downloaded the app from the google play store for "double tap to wake (Nexus 6P)" and it works perfectly.
https://play.google.com/store/apps/details?id=com.blakey22.doubletapwake
Nice
kyle4269 said:
Sorry to be rude.. But did you even look on the first page?
http://forum.xda-developers.com/showthread.php?t=3446824
Click to expand...
Click to collapse
I have followed all the steps from Heisenberg's guide. Flashed the modified boot.img and twrp recovery but when I go to boot into the recovery my phone freezes and stays on the teamwin screen. I have tried flashing different versions of twrp still no luck. Any suggestions?
Nevermind. I figured I will give it another shot. This time I only flashed the new twrp without flashing the boot.img and of course if works now. grrr
Hi guys,
I rooted my s3 successfully, but now cannot install the 19s update. I've tried undoing the root and updating afterwards unsuccessfully. Do you guys have any other things I can try? Do I need to re flash the stock ROM?
Thanks !
Rooting typically breaks OTA updates in my experience. You can try flashing stock + stock recovery and then take the OTA. I'm not 100% sure that'll work, but it should.
Come to think of it, I think it's more twrp that breaks OTAs and not root.
benjmiester said:
Rooting typically breaks OTA updates in my experience. You can try flashing stock + stock recovery and then take the OTA. I'm not 100% sure that'll work, but it should.
Come to think of it, I think it's more twrp that breaks OTAs and not root.
Click to expand...
Click to collapse
Darn, I was a moron and didn't back up the stock recovery, so I guess I'm stuck waiting for someone else with an S3 to upload theirs. Oh well, lesson learned!
Thanks!
try flashing the stock recovery from here:
http://forum.xda-developers.com/le-2/development/leeco-le-2-x526-stock-recovery-t3449208
it's from 16S, but it should work. after that you should be able to install the OTA. no gaurantees though
randomsmash said:
Darn, I was a moron and didn't back up the stock recovery, so I guess I'm stuck waiting for someone else with an S3 to upload theirs. Oh well, lesson learned!
Thanks!
Click to expand...
Click to collapse
No prob, it happens. I keep seeing .20 builds on YouTube, that add theme store/more theme support and fingerprint sensor gestures. So I might want to do an OTA soon myself. Let us know if 99's solution works.
Sent from my LEX727 using XDA-Developers mobile app
benjmiester said:
No prob, it happens. I keep seeing .20 builds on YouTube, that add theme store/more theme support and fingerprint sensor gestures. So I might want to do an OTA soon myself. Let us know if 99's solution works.
Sent from my LEX727 using XDA-Developers mobile app
Click to expand...
Click to collapse
it wont. i fiddled with my S3 last night and accidently booted TWRP as "read/write", which the OTA can detect as it runs a checksum on the /system partition. if the system partition has EVER been mounted as read/write it changes, and therefore the OTA file will never flash/install. the only way around it is to have someone do a full system image backup from TWRP via a "fastboot boot twrp.img" then selecting to keep TWRP mounted as read only. this also affects all of us on the Pro3 (i have both). it would be wise if we could pull full system images for all US models as there are no full ROM's available
instructions on how to do that are here:
http://forum.xda-developers.com/showpost.php?p=69758375&postcount=89
http://forum.xda-developers.com/le-2/help/x522-stock-019s-rom-lost-imei-baseband-t3505356
fixed it.
ExTREmE99 said:
http://forum.xda-developers.com/le-2/help/x522-stock-019s-rom-lost-imei-baseband-t3505356
fixed it.
Click to expand...
Click to collapse
Hey man,
I followed your instructions in your post in that thread, but the modified ota update fails to flash as well, and upon reboot I'm back at my old home screen. Perhaps it was an error on my part throughout the bootloader unlock process; I'm also dumb and didn't know how to boot TWRP into read-only mode (what I did was check the "mount system as read-only" option in the "Mount" menu, don't know if that was right!).
Either way, congrats on getting your phone back to receiving OTAs!
Somebody still have a TWRP untouched system partition might try a dd backup. So we can compare where the different are
rainlake said:
Somebody still have a TWRP untouched system partition might try a dd backup. So we can compare where the different are
Click to expand...
Click to collapse
I just got a new phone..let me know what needs to be done to get backup of stock ROM/recovery which can be later flashed to take OTA updates