Related
I am running stock. No ROM but I am rooted, and I use Franco kernel and xposed framework, what will happen to those mods? Im afraid of brick, should I uninstall all of those including root first before updating to L... When it comes out? Please I need answers, I had soft brick before and I don't want it again.
BrickMeNot said:
I am running stock. No ROM but I am rooted, and I use Franco kernel and xposed framework, what will happen to those mods? Im afraid of brick, should I uninstall all of those including root first before updating to L... When it comes out? Please I need answers, I had soft brick before and I don't want it again.
Click to expand...
Click to collapse
You should only have to wipe, yes you will loose the mods, but they will probably be updated. You will just have to wait a month or 2.
WeRSpecialPeople said:
You should only have to wipe, yes you will loose the mods, but they will probably be updated. You will just have to wait a month or 2.
Click to expand...
Click to collapse
Wipe everything right? Like factory reset or twrp? Will I have to reinstall root/Franco?
Franco will need to create a new kernel, the old one won't work after a version update. Xposed will work if you manually flash the update; if you want ota you'll need to disable it first and revert to stock recovery.
Sent from my Nexus 7 using XDA Free mobile app
You'd have to try really hard to brick a Nexus device. What's so scary about a soft brick? Learn how to use fastboot and adb and there's absolutely nothing to be scared of.
Actually I was going from cwm to twrp and I didn't know the wipe buttons would get rid our my OS altogether..? my dumb mistake.
But I was saved by nexus 7 toolkit
Sent from my Nexus 7 using XDA Free mobile app
Yea don't worry about bricking. You will be able to restore thru nexus toolkit as long as your bootloader is unlocked. I wiped the os off my nexus 4 as well.
I just took the plunge and xposed isn't working nor is my showbox.
Android L is really cool and I can live without xposed, but showbox not working is a big hit. I just got it all setup too. Works good. No real problems.
I flashed back to stock and wiped, then upped to L
How do you flash back? Can I just flash a custom 4.4.4 ROM or do I need flash stock?
player911 said:
How do you flash back? Can I just flash a custom 4.4.4 ROM or do I need flash stock?
Click to expand...
Click to collapse
Just like you would any other ROM in recovery or fastboot. If you want stock, flash stock. If you want a custom ROM, flash a custom ROM.
player911 said:
How do you flash back? Can I just flash a custom 4.4.4 ROM or do I need flash stock?
Click to expand...
Click to collapse
Multiple choices. If you made a backup/nandroid before flashing L you should be able to restore your backup without any issues, For one thing the bootloader didn't change. You can fastboot flash the system and boot images after extracting them from the factory image then wipe cache and dalvik. Flash the whole factory image either with or without modifying the flash_all.bat (open the flash_all.bat in notepad and remove the -w which will prevent the storage from being wiped). Or... flash a custom or stock ROM. Piece of cake!
Good to know. I'm trying to hang on but we'll see
I have a Nexus 7 (2013) running Kit Kat (4.4.4) and recently got the the OTA update to 5.0.1, but haven't installed it yet. I rooted it using the WugFresh Nexus Root Toolkit sometime some the last OTA update.
So how do I update to Lollipop? Do I need to unroot with the toolkit first? Will I need to backup my apps first and restore after the update?
Also, for some unknown reason, I no longer have the OTA update although I was notified that it had been downloaded. Odd! Guess I'll have to manually download it and side load it.
Thanks in advance...
skallal said:
I have a Nexus 7 (2013) running Kit Kat (4.4.4) and recently got the the OTA update to 5.0.1, but haven't installed it yet. I rooted it using the WugFresh Nexus Root Toolkit sometime some the last OTA update.
So how do I update to Lollipop? Do I need to unroot with the toolkit first? Will I need to backup my apps first and restore after the update?
Also, for some unknown reason, I no longer have the OTA update although I was notified that it had been downloaded. Odd! Guess I'll have to manually download it and side load it.
Thanks in advance...
Click to expand...
Click to collapse
In order to run the stock OTA you need to put your system back to stock. That means stock recovery, remove ALL modifications to the system partition (root, ad blocks, etc...) then you can run it. If that sounds like too much work - just back up and flash the factory image then restore.
I was rooted with the Wugfresh toolkit. I downloaded the 5.0 (and later 5.0.1) factory image from Motorola and unpacked it. I edited the flash-all.bat batch file (right click, Edit -or- right click, Open With, select notepad/wordpad) and removed the -w flag from the end of the file. It's not the very end, but very close. Just delete the -w and any excess spaces and save the file. The -w flag is what tells it to do a wipe of all data, removing it will prevent that. Put your Nexus into bootloader mode and double click the batch file.
Once it finishes flashing, it will boot up and say "optimizing apps" or "Android is updating" or something like that. Mine took about 15 minutes. After that, run the Chainfire Auto Root (CFAR) script to get root access back, and you're back in business.
Note: flashing Factory Images and running CFAR require an unlocked bootloader. CFAR will unlock the bootloader AUTOMATICALLY as part of the script. This WILL RESULT IN A LOSS OF DATA. If you are already unlocked, you're fine, as long as you remove the -w flag from the batch file.
Also, you do not need to go from 4.4.4 to 5.0 to 5.0.1, you can jump straight from 4.4.4 to 5.0.1.
There is also this:
http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745
At least a few of us have used that with no issues. I was running stock rooted 4.4.4 with TWRP, so I updated my bootloader, rebooted into recovery, wiped cache and Dalvik (probably not necessary before flashing), flashed the ROM, wiped cache and Dalvik again, and rebooted, and it's working great with no loss of data.
Telyx said:
There is also this:
http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745
At least a few of us have used that with no issues. I was running stock rooted 4.4.4 with TWRP, so I updated my bootloader, rebooted into recovery, wiped cache and Dalvik (probably not necessary before flashing), flashed the ROM, wiped cache and Dalvik again, and rebooted, and it's working great with no loss of data.
Click to expand...
Click to collapse
^I am going to do this, after reading similar reports of success.
However, to OP I want to stress that it is important that you update your bootloader before flashing the ROM. The patch is attached to the linked post.
While I am definitely tech savvy, I am not that comfortable with the WugFresh toolkit. For example, I just updated it to v1.9.9 and connected my device. While I know I previously unlocked the boot loader and rooted my device, the toolkit itself does NOT tell me if my device is unlocked or rooted.
Is there a tutorial somewhere describing how to update to Lollipop with the WugFresh toolkit? Thanks to @fury683 for the comment about editing the batch file. But I don't know what that means with respect to the toolkit user interface, that is what buttons are clicked in what order. I need a step by step list of instructions before starting.
@OrBy, by flash the stock image, do you mean the 4.4.4 image or the new 5.0.1 image? And how do I flash the image? WugFresh toolkit?
I used the WugFresh toolkit a few months ago, but have forgotten the steps I took. Should have written it down. I'll try to stick with the WugFresh toolkit.
Thanks for all the comments
Factory images and Wugfresh are not used together. Wugfresh is a collection of things while factory images return the device to 100% factory stock out of the box. If you modify the batch file as detailed above, no user data/apps are removed, just the system, recovery, etc partitions.
Factory images are a one click method that has a very similar end result as Wugfresh does to return to stock. I would go with factory images as it is the easiest and most straight forward method. Run batch, confirm, wait about 1-2 minutes, done.
skallal said:
@OrBy, by flash the stock image, do you mean the 4.4.4 image or the new 5.0.1 image? And how do I flash the image? WugFresh toolkit?
Click to expand...
Click to collapse
Well if your hung up on running the OTA then the 4.4.4 but if I were you I would just flash the 5.0.1 and skip the who OTA.
I managed to update to 5.0.1 without wiping the device using WugFresh. I went to the WugFresh site, read the FAQ, and found how to update without wiping clean. Turns out there is an option to disable wipe without editing the batch file. I was able to do the while procedure leaving the device unlocked.
I did have an unexpected issue. I had to reinstall in the USB drivers on my PC before I could re-root it. WugFresh made this part easy too, though I'm surprised a reinstall was even required. Once that was done, USB connection was restored and I could complete the rooting process.
I always stress out whenever updating Android in any way. The rules are different with each device and OS version.
One change I've noticed I'd that my Nexus 7 brightness I'd dimmer and I have to turn to setting higher. Hope the update is worth the trouble.
Follow up: after all the work upgrading to 5.0.1, I decided I didn't like the new version. I did the upgrade without a clean wipe. But I did the downgrade with a clean wipe.
The WugFresh toolkit is quite capable utility. I couldn't imagine doing it the hard way with the adb command line interface. At least know how to recover and rebuild my system should the need ever occur in the future. And Titanium Backup is indispensable too.
I found Lollipop to be a battery hog. Perhaps I'll try it again when some of the issues are worked out. There is no compelling reason change from Kit Kat at this time, IMHO.
OrBy said:
In order to run the stock OTA you need to put your system back to stock. That means stock recovery, remove ALL modifications to the system partition (root, ad blocks, etc...) then you can run it. If that sounds like too much work - just back up and flash the factory image then restore.
Click to expand...
Click to collapse
This is NOT true. I upgraded while rooted and it went fine. Just beware of xposed and other tools that mess up with /system and thus the upgrade scripts.
While I was able to update from KK (4.4.4) to LP (5.0.1) without wiping the data, it didn't work out for me. The battery life was terrible. It drained at least twice as fast compared to before the update. I was trying to avoid the pain of a clean install. But in the end, it wasn't worth with it.
I ended up going back to KK, and then to LP again but with a clean install. When installing LP the second time, I wiped the data and let Google reinstall all of the apps. There were a small number of apps, that I later restored the data from Titanium Backup, for example games with previous scores.
This made a huge difference in battery life. Plus the look and feel of many apps changed to the new Material design.
I'm not entirely sure I like the look of LP. I'd prefer LP under the hood, but the look of KK. Oh well!
Bottom line: don't do OTA updates with a major new release.
Hey guys I just got the Nexus 7 2013(Wifi) today for Christmas and I just rooted it with Nexus Root Toolkit, and I wanted to know how I can update to Android 5.0 without wiping it. I have Android 4.4.4 with the latest TWRP.
You didn't install a custom ROM? I have the same tablet, I also rooted mine. I updated to Jellybean and everything seems to be working, except I lost root and it's really annoying that I haven't found how to root it again without it being wiped erasing all my apps and data.
You can update it via OTA, but you will lose root.
Nexus7II_Lollipop
critofur said:
You didn't install a custom ROM? I have the same tablet, I also rooted mine. I updated to Jellybean and everything seems to be working, except I lost root and it's really annoying that I haven't found how to root it again without it being wiped erasing all my apps and data.
Click to expand...
Click to collapse
If u are only on jellybean, u might be able to just use the towelroot apk and not erase any data...
bigboolean said:
Hey guys I just got the Nexus 7 2013(Wifi) today for Christmas and I just rooted it with Nexus Root Toolkit, and I wanted to know how I can update to Android 5.0 without wiping it. I have Android 4.4.4 with the latest TWRP.
Click to expand...
Click to collapse
You can either:
(1) Wait for the OTA: hence no wipe of data
(2) Use the factory image and remove the wipe command (-w) (search for a how to, answered many times here)
(3) Use the OTA zip (not familiar with process, if it wipes or not, as I always use factory images but I guess there is a how-to in here as well somewhere!)
(4) ...
One thing you should take into account though is that for a major android version jump (e.g. 4.4.4 => 5) you should always consider to wipe.
In addition, questions go into Q&A section
You can install multirom. So you can keep the stock rom and install lollipop as well. Just have a look at the multirom thread on how to install it. It's quite easy.
There is zero reason not to do a clean install in your situation.
Flash the factory image, reflash twrp, flash su zip, done.
bigboolean said:
Hey guys I just got the Nexus 7 2013(Wifi) today for Christmas and I just rooted it with Nexus Root Toolkit, and I wanted to know how I can update to Android 5.0 without wiping it. I have Android 4.4.4 with the latest TWRP.
Click to expand...
Click to collapse
You just got it so why not take the wipe and just install the image from google?
Hi...
I would like to upgrade my phone which has the systemless root.
I tried flashing the current stock recovery to see if OTA goes thru, but it doesn't. (It's a shame, since the OTA is only 11mb and I tend to like conciseness... but oh well.)
Since the OTA didn't go thru, I'd like to flash the upgrade myself - I have downloaded it.
It has the following images - is the following right if I want to upgrade stock ROM, without erasing my data -
radio-bullhead-m8994f-2.6.30.0.68.img - Flash
bootloader-bullhead-bhz10k.img - Flash
userdata.img - Do not flash - Will erase user data.
vendor.img - Flash? - I have Project Fi. Does it matter?
recovery.img - Do not flash - But it's okay if you flash, reflash TWRP.
cache.img - Flash? - Is it same as erasing cache?
boot.img - Flash - And reroot from TWRP.
Edit: There are a couple of threads which are on similar lines, but they are all about some other objective and not specifically on upgrading, e.g. "unroot and rever to stock", etc.
Yes. I usually flash recovery, wipe cache, then flash twrp image, and re-root via TWRP.
https://www.androidpit.com/how-to-get-android-m-preview
You forgot to flash the most important partition: system.
For manually updating to the latest build without losing your data or having to reinstall everything you will pretty much always be able to get away with doing the following:
flash radio, vendor, system and boot.
reflash supersu (and every other module you flashed in twrp)
wipe cache/dalvik
reboot.
Works like a charm and you will not even have to setup anything again. Should take you max 15 minutes total.
I do reccommend starting with a nandroid backup beforehand just in case.
Ya i just updated (flashed) to 6.0.1 myself too last week. Systemless root. And now this 11mb ota happens.
So unroot, revert back to stock recovery, and apply ota update MMB29P?
How do i revert back to stock recovery?
^ one mentions flash recovery....flash recovery, wipe cache, flash twrp recovery, and then reroot.
^one doesnt mention flash recovey....flash radio, flash vendor, flash system, and flash boot?
vypinoy said:
Ya i just updated (flashed) to 6.0.1 myself too last week. Systemless root. And now this 11mb ota happens.
So unroot, revert back to stock recovery, and apply ota update MMB29P?
How do i revert back to stock recovery?
^ one mentions flash recovery....flash recovery, wipe cache, flash twrp recovery, and then reroot.
^one doesnt mention flash recovey....flash radio, flash vendor, flash system, and flash boot?
Click to expand...
Click to collapse
Just follow the steps I mentioned using the files from mmb29p factory image.
It's a method that has proven itself as working. No need messaging with the ota.
If you want to try to force the ota by flashing stock recovery by all means try that.
Keep in mind to check what build you are on and take the stock recovery from the factory image of your current build.
If you installed anything (exposed eg) to system partition the ota still won't work probably.
I'm saying just update from factory image mmb29p instead of ota since your basically will be downloading and extracting a factory image anyway so you won't save much time time by trying to run the ota.
peltus said:
Just follow the steps I mentioned using the files from mmb29p factory image.
It's a method that has proven itself as working. No need messaging with the ota.
If you want to try to force the ota by flashing stock recovery by all means try that.
Keep in mind to check what build you are on and take the stock recovery from the factory image of your current build.
If you installed anything (exposed eg) to system partition the ota still won't work probably.
I'm saying just update from factory image mmb29p instead of ota since your basically will be downloading and extracting a factory image anyway so you won't save much time time by trying to run the ota.
Click to expand...
Click to collapse
ok thanks
hopefully itll work. ill try it soon. I just had to go back to factory when i tried to flash to 6.0.1 from 6.0... and i kept getting the error when flashing system about it could not allocate ***** bytes. and then there was always an error flashing the vendor. so had to flash all the way back to what it was out of box i think. then go to 6.0.1.. only have time on the weekend. ill update then.... i also edited my build.prop... is that gna revert when i update?
vypinoy said:
ok thanks
hopefully itll work. ill try it soon. I just had to go back to factory when i tried to flash to 6.0.1 from 6.0... and i kept getting the error when flashing system about it could not allocate ***** bytes. and then there was always an error flashing the vendor. so had to flash all the way back to what it was out of box i think. then go to 6.0.1.. only have time on the weekend. ill update then.... i also edited my build.prop... is that gna revert when i update?
Click to expand...
Click to collapse
Yep there build.prop is on system. Back that up and restore it later.
It might also keep the ota from executing.
Google Nexus 5 Android 5.1 does come with lots of bug fixes, performance improvements, menu tweaks, and much much more.
pankaj554 said:
Google Nexus 5 Android 5.1 does come with lots of bug fixes, performance improvements, menu tweaks, and much much more.
Click to expand...
Click to collapse
think you posted in the wrong forum, this is the 5X forum not the 5. Also, 5.1 is old...
peltus said:
Yep there build.prop is on system. Back that up and restore it later.
It might also keep the ota from executing.
Click to expand...
Click to collapse
Got that "could not allocate ____bytes" error again when trying to flash system again. So just did it thru wugfreshs advanced utilities.
Other than that. It worked. Twrp was still there too. Which was weird. Installed SuperSU. And back and running again. Thanks!
Hi,
I am currently in OOS 4.0.1 rooted with superSU 2.79 and official TWRP 3.0.3. I got ota update OOS 4.0.2 few days back which I downloaded and clicked install. After reboot, it showed couldn't install update and I was back to OOS 4.0.1 without any side effects.
However, today I again got ota notification for 4.0.2 but this time its full 1.4 GB size. I haven't downloaded it yet. I just wanted to ask the community why is this happening. I don't mind ota update but my impression is I can't install ota while I am rooted.
Has anyone experienced this before? If I try installing, will it have any severe side effect in case of failures?
Nilay
Your phone recognised that the smaller OTA file failed because your system had been modified. So it tries to flash the full OTA file in order to prevent any conflicts with the modifications you made by completely removing them all. It's a safety mechanism. If you flash the full OTA, you should be fine, but you'll lose root.
cohaolain said:
Your phone recognised that the smaller OTA file failed because your system had been modified. So it tries to flash the full OTA file in order to prevent any conflicts with the modifications you made by completely removing them all. It's a safety mechanism. If you flash the full OTA, you should be fine, but you'll lose root.
Click to expand...
Click to collapse
Will it also replace TWRP with stock recovery? What about my apps, data, settings etc.? I don't want to reconfigure everything right now and worry about backups. I can wait for bigger update (maybe with 7.1.x) to re flash full zip.
Also, is this update going to be like dirty flash?
Thanks
Sent from my OnePlus 3 using XDA Labs
mit2nil said:
Will it also replace TWRP with stock recovery? What about my apps, data, settings etc.? I don't want to reconfigure everything right now and worry about backups. I can wait for bigger update (maybe with 7.1.x) to re flash full zip.
Also, is this update going to be like dirty flash?
Thanks
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
Its easier if you just download the full rom from oneplus's website and dirty flash it over your current setup and flash supersu immediately without rebooting to maintain root. You wont loose any data or custom settings on your device although its still advisable to make a backup of your data.
mit2nil said:
Will it also replace TWRP with stock recovery? What about my apps, data, settings etc.? I don't want to reconfigure everything right now and worry about backups. I can wait for bigger update (maybe with 7.1.x) to re flash full zip.
Also, is this update going to be like dirty flash?
Thanks
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
If you want to do an OTA upgrade, you have to flash stock recovery first, TWRP won't work.
After download before perform installation, you can find the downloaded full 1.4GB zip in your internal storage under ".OnePlusH2Ota" or "Android/data/com.oneplus.ota/files/.OnePlusOta", copy it out and flash it through TWRP. You won't lose your apps and settings unless you wipe /data or do a factory reset, you do needed to re-flash supersu though.