Okay guys, I need your help. I wanted to return to complete stock and update to newest version. So I downloaded a stock ROM and let it flash the stock recovery. I got a notification for 4.3 update and went ahead and flashed that sucker. During the installation, up popped "Error". It stayed frozen on that screen, so I hard rest it, and restarted my nexus. Well, the installation went through fine. Disabled super user and went about trying to force the 4.4.2 update. Sure enough that kicked in as well. Now, I also got the error on installation of that as well, but this time, when I rebooted, it was still 4.3. I've gone through it about 10 times now. And it gives me the error every single time and remains 4.3. I did a little googling and found out how to get there error log, and it says unexpected content in boot animation.zip.
Unfortunately one of my data pins is busted in my Nexus's USB port, so connecting to PC is not an option for me. Plus my PC is down for the count until I can get a new motherboard in her. Is there anyway to obtain root without connecting to a PC on 4.3 or at least get the update to take?
Is there possibly anyway to wirelessly adb from another android device? Would that even help in my situation?
I've tried " root master" and it seemed to work, even made the Chinese root permissions manager(as a system app) for me, but I can't grant access to anything, nor am I even give the option to. Also, when I tried that, it kicked SuperSU out of system and into regular old data apps.
I suppose I can just stick with 4.3, but if you guys could, I'd love some help.
Hi guys,
Have just spent the last couple of hours trying to research this but still not quite sure what's the best (safest!!) way of upgrading to lollipop on my SM-910G. I am rooted and currently on 4.4.4 and when I try to do an OTA update, I get the msg "The operating system has been modified in an unauthorised way.... etc etc"
When I connect via Kies, I get a pop up msg telling me that lollipop is available however when I try to update it tells me that I have to be unrooted. I read an article where some guy messed up his rooted S4 while trying to update via Kies. Can't afford for that to happen on my phone, I've backed up all my apps and data via Titanium Backup but now need to know what the safest way is to upgrade and keep all my settings etc.
I've downloaded the right 5.0 ROM (N910GDTU1BOC5_N910GXSA1BOC5_XSA.zip) for my model - am I correct to say that if I flash via Odin, I will lose all my apps and settings (and root)?
If I want to update and keep all my settings, am I safe to unroot via SuperSU, then update via Kies? I've read about how unrooting via SuperSU isn't really a complete unroot?
At the end of the day unless I'm 100% certain I will probably stay on 4.4.4 since there has been some horror stories with battery drain and stuff on 5.0
Has anyone been in a similar situation?
highon2str said:
Hi guys,
Have just spent the last couple of hours trying to research this but still not quite sure what's the best (safest!!) way of upgrading to lollipop on my SM-910G. I am rooted and currently on 4.4.4 and when I try to do an OTA update, I get the msg "The operating system has been modified in an unauthorised way.... etc etc"
When I connect via Kies, I get a pop up msg telling me that lollipop is available however when I try to update it tells me that I have to be unrooted. I read an article where some guy messed up his rooted S4 while trying to update via Kies. Can't afford for that to happen on my phone, I've backed up all my apps and data via Titanium Backup but now need to know what the safest way is to upgrade and keep all my settings etc.
I've downloaded the right 5.0 ROM (N910GDTU1BOC5_N910GXSA1BOC5_XSA.zip) for my model - am I correct to say that if I flash via Odin, I will lose all my apps and settings (and root)?
If I want to update and keep all my settings, am I safe to unroot via SuperSU, then update via Kies? I've read about how unrooting via SuperSU isn't really a complete unroot?
At the end of the day unless I'm 100% certain I will probably stay on 4.4.4 since there has been some horror stories with battery drain and stuff on 5.0
Click to expand...
Click to collapse
highon2str said:
Hi guys,
Have just spent the last couple of hours trying to research this but still not quite sure what's the best (safest!!) way of upgrading to lollipop on my SM-910G. I am rooted and currently on 4.4.4 and when I try to do an OTA update, I get the msg "The operating system has been modified in an unauthorised way.... etc etc"
When I connect via Kies, I get a pop up msg telling me that lollipop is available however when I try to update it tells me that I have to be unrooted. I read an article where some guy messed up his rooted S4 while trying to update via Kies. Can't afford for that to happen on my phone, I've backed up all my apps and data via Titanium Backup but now need to know what the safest way is to upgrade and keep all my settings etc.
I've downloaded the right 5.0 ROM (N910GDTU1BOC5_N910GXSA1BOC5_XSA.zip) for my model - am I correct to say that if I flash via Odin, I will lose all my apps and settings (and root)?
If I want to update and keep all my settings, am I safe to unroot via SuperSU, then update via Kies? I've read about how unrooting via SuperSU isn't really a complete unroot?
At the end of the day unless I'm 100% certain I will probably stay on 4.4.4 since there has been some horror stories with battery drain and stuff on 5.0
Click to expand...
Click to collapse
hi
Just a few points ...First if you " dirty flash" official stock Rom with Odin, then you will lose root ( so to me there is no need to unroot first ) However you do not loose any 3 rd party apps or settings . Also i never use Kies as my personal experience is that it is a waist of time .Regarding Lollipop well i have flashed several newer " version"/changelog/dated of Lollipop 5.0.1 over the past months and all of them have been good to me...( ..overall.) No real battery drain ,no lag ( only recent button and one " Samsung bug in the setting " Accessibilty" .
All my "problems " on Lollipop, on and off, was caused by 3 rd party apps
eg.Past few days i had suddenly random reboots over and over .i reflashed Lollipol ,i factory reset ,but the random reboots continued .
i then started to install all my +_ 162 ..?? apps one by one and checked
Eventually found my culprit ..'Greenify " (the experimental paid ,bolt on package, which is meant mostly for Xposed module with few functions you can also use without Xposed eg "don't remove Notifications " and Greenify system apps l)
After using Greenify for months with no issues it suddenly started giving problems .
So i could have given Lollipop the blame for my woes but i did not .
Yes I do believe Lollipop has issues ,but overall i cannot complain .
yes ,Titanuim is the way to go .
Also i "unrooted " via SuperUser app once, no problem at all, but then why do this if you just flash over it and root is gone
Bottom line ,
you can be "stuck " on Android v4.4.4 hoping and waiting .......?
or faceup to Lollipop ?
its your choice ?
good luck
Hey willcor thanks for the reply! Good to hear your experiences with this. Interestingly I've had a similar problem of sluggishness, lag and random rebooting (multiple times a day) on my Note 4 running kitkat. This went on for about 2 or 3 days. Tried installing some recently installed apps thinking it might have caused it, and now it seems it's fixed itself, I think??
Even pulling the battery and restarting often took ages to boot. Took my 128GB SD card out and tried to boot thinking maybe it was the card but it still lagged and restarted by itself. Like I said it seems ok now and has been ok for the last few days, but now that you mention Greenify, I have that installed too along with a few exposed modules. This rebooting problem is what motivated me to think about upgrading to lollipop to see if it would fix it.
Going by what you said, if I am not going to lose apps, data and settings, then I might flash to lollipop, then re-root. Sounds like the way to go. Maybe...
willcor said:
hi
Just a few points ...First if you " dirty flash" official stock Rom with Odin, then you will lose root ( so to me there is no need to unroot first ) However you do not loose any 3 rd party apps or settings . Also i never use Kies as my personal experience is that it is a waist of time .Regarding Lollipop well i have flashed several newer " version"/changelog/dated of Lollipop 5.0.1 over the past months and all of them have been good to me...( ..overall.) No real battery drain ,no lag ( only recent button and one " Samsung bug in the setting " Accessibilty" .
All my "problems " on Lollipop, on and off, was caused by 3 rd party apps
eg.Past few days i had suddenly random reboots over and over .i reflashed Lollipol ,i factory reset ,but the random reboots continued .
i then started to install all my +_ 162 ..?? apps one by one and checked
Eventually found my culprit ..'Greenify " (the experimental paid ,bolt on package, which is meant mostly for Xposed module with few functions you can also use without Xposed eg "don't remove Notifications " and Greenify system apps l)
After using Greenify for months with no issues it suddenly started giving problems .
So i could have given Lollipop the blame for my woes but i did not .
Yes I do believe Lollipop has issues ,but overall i cannot complain .
yes ,Titanuim is the way to go .
Also i "unrooted " via SuperUser app once, no problem at all, but then why do this if you just flash over it and root is gone
Bottom line ,
you can be "stuck " on Android v4.4.4 hoping and waiting .......?
or faceup to Lollipop ?
its your choice ?
good luck
Click to expand...
Click to collapse
highon2str said:
Hey willcor thanks for the reply! Good to hear your experiences with this. Interestingly I've had a similar problem of sluggishness, lag and random rebooting (multiple times a day) on my Note 4 running kitkat. This went on for about 2 or 3 days. Tried installing some recently installed apps thinking it might have caused it, and now it seems it's fixed itself, I think??
Even pulling the battery and restarting often took ages to boot. Took my 128GB SD card out and tried to boot thinking maybe it was the card but it still lagged and restarted by itself. Like I said it seems ok now and has been ok for the last few days, but now that you mention Greenify, I have that installed too along with a few exposed modules. This rebooting problem is what motivated me to think about upgrading to lollipop to see if it would fix it.
Going by what you said, if I am not going to lose apps, data and settings, then I might flash to lollipop, then re-root. Sounds like the way to go. Maybe...
Click to expand...
Click to collapse
hi,
Just a quick remark. When i was on Android v4.4.4, most of my issues eg. Private mode S HEALTH... (yes i know there was quick fixes /patches , that you could apply) Play store not installing apps, lags from time to time etc was caused by Xposed Framework. As far as i can remember Xposed was never optimise for Android v4.4.4? As "good" as Xposed was, it gave me "terrible headache /problems" on my Note 4....... even after uninstalling Xposed it broke some apps functionality! (This is a fact for me) . but yet, on all my other devices, no issues ! As stated in my previous post, that Lollipop experience, has been over all, very good for me.,(I have accepted the few bugs, that comes with every software update be it Android v4.4.4 or Android v 5.0.1.)
Lollipop also enabled me to use other apps /features eg Network Toggle app (change network only to LTE or LTE/3G or 3G only.. root required)
Bottom line
for me is.... yes, Lollipop has issues, but most of mine was caused by 3rd party apps not optimised 100% , work smoothly on Lollipop.
good luck
..............................
post note....
Titanium, i forgot, you might have some minor issues at first. Titanium could not find backup folder on my ext sd same as on Android v4.4.4) , so i used NextApp Sdfix (Play store, free app) Titanium, then was able to locate back ups. Again yesterday, i factory reset my device because of a Nova launcher, toggle notification issue and because i also wanted to for a period of time.
Titanium could not write and above NextApp Sdfix said i had no write premisson after running NextApp. i formatted my ext sd on laptop and NextApp did its work and Titanium working 100%
Just thought to make you aware if issue arrived.
Thanks... I forget all these root features have to be redone. I've also given extsd access on kitkat after rooting. Will have to do it all over again I guess!
Ok just a quick update. Flashed to 5.0.1 with Odin and rooted with CFautoroot. Everything seems to be ok apart from after rooting and rebooting, I got a "could not do normal boot" msg, saying that the phone was in download mode and not to disconnect the target. I pulled the batt and booted up normally ok. Checked in Titanium and found root access ok, activated write to SD and all seems normal.
Things seem a bit sluggish with lollipop, so I uninstalled xposed (which now won't work on this version), greenify and some other apps, and booted into recovery to wipe cache partition. When it was done wiping the cache and said to reboot, I got the same "could not do normal boot" msg. Once again I pulled the battery and it booted ok.
Not sure what has happened or if anything is affected - should I re-flash 5.0 with Odin and re-root all over again?
highon2str said:
Ok just a quick update. Flashed to 5.0.1 with Odin and rooted with CFautoroot. Everything seems to be ok apart from after rooting and rebooting, I got a "could not do normal boot" msg, saying that the phone was in download mode and not to disconnect the target. I pulled the batt and booted up normally ok. Checked in Titanium and found root access ok, activated write to SD and all seems normal.
Things seem a bit sluggish with lollipop, so I uninstalled xposed (which now won't work on this version), greenify and some other apps, and booted into recovery to wipe cache partition. When it was done wiping the cache and said to reboot, I got the same "could not do normal boot" msg. Once again I pulled the battery and it booted ok.
Not sure what has happened or if anything is affected - should I re-flash 5.0 with Odin and re-root all over again?[/QUOTE
hi,
i am sure i read somewhere about.re: your remark, when you rooted and got a msg, with
"could not do a normal reboot... I am sure it could be ( @ Chainfire,) Cf autoroot website not sure.?
I would have search for a answer /reason!/ explanation Then i would afterwards, reflash Rom. (depends on you)
Just a quick question.... At what stage did you uninstall Xposed....? before /after flashing etc. i stated before that i found Xposed "broke /caused issues after i uninstalling it. (facts about two or three times it happened , in past )
Also i had no problem in using Greenify again (i have re installed it) its just the donation /paid / experimental package i am a bit hesitant with.
good luck
Click to expand...
Click to collapse
Hey guys, I have since reflashed and rerooted and now seem to have less problems, although the phone is still sluggish, randomly locking up and restarting , and sometimes restarting to the green android "could not do normal boot" screen.
Question now is, can I boot into stock recovery to do a factory reset? I've done some research but the views seem conflicting. Is this recommended, will I be stuck in a bootloop and will I still be rooted after the reset?
I never did a factory reset when flashing from 4.4 to 5.0.1 so I'm hoping this will fix the issues I've got now.
Sent from my SM-N910G using Tapatalk
Anyone?
Sent from my SM-N910G using Tapatalk
Rooted 6P on stock ROM. Today I got a System update notification. Ignored it, went to Google OTA download location, downloaded the O OTA and attempted to install via Flashify. When the phone rebooted it was in a bootloop. Downloaded OTA to my PC at home, side loaded via ADB and attempted to install via TWRP, failed with Error 7. I then edited the install file to remove the "asserts" from the install script. the script installed seemingly OK but the phone again went into a bootloop. At this point I have re-installed N. Anyone seen that or has suggestions? There is a thread on the Google product forums where a number of people are reporting similar behavior. As usual Google is not responding. They truly are becoming the Microsoft of the early 90s - too fat, too rich, and extremely arrogant.
UPDATE: after downgrading to N (and loosing root in the process since I simply flashed the OTA) I attempted to just take the O update straight from Google as a system update. Everything went without error messages until the reboot, now in a bootloop for the last 5 minutes. Will give it another 5 and then downgrade permanently to N until Google fixes their mess three updates from now. Yup, three updates, just as many as Microsoft used to need to get things right.
GroovyGeek said:
Rooted 6P on stock ROM. Today I got a System update notification. Ignored it, went to Google OTA download location, downloaded the O OTA and attempted to install via Flashify. When the phone rebooted it was in a bootloop. Downloaded OTA to my PC at home, side loaded via ADB and attempted to install via TWRP, failed with Error 7. I then edited the install file to remove the "asserts" from the install script. the script installed seemingly OK but the phone again went into a bootloop. At this point I have re-installed N. Anyone seen that or has suggestions? There is a thread on the Google product forums where a number of people are reporting similar behavior. As usual Google is not responding. They truly are becoming the Microsoft of the early 90s - too fat, too rich, and extremely arrogant.
UPDATE: after downgrading to N (and loosing root in the process since I simply flashed the OTA) I attempted to just take the O update straight from Google as a system update. Everything went without error messages until the reboot, now in a bootloop for the last 5 minutes. Will give it another 5 and then downgrade permanently to N until Google fixes their mess three updates from now. Yup, three updates, just as many as Microsoft used to need to get things right.
Click to expand...
Click to collapse
Since it's a new version, I downloaded the factory image and flashed everything via fastboot. No problems. In fact, every time I have a problem using flashify or down grading, flashing via fastboot solves everything. Maybe you ought to try doing that.
The OTA file seems to be structurally very different from the N files. There are a bunch of files I have not seen before in N OTAs - bootloader.cmnlib, bootloader.hyp, bootloader.keymaster - the list goes on and on. I am going to have to read up on what to flash and what not to, since the potential to brick the device is significant.
GroovyGeek said:
The OTA file seems to be structurally very different from the N files. There are a bunch of files I have not seen before in N OTAs - bootloader.cmnlib, bootloader.hyp, bootloader.keymaster - the list goes on and on. I am going to have to read up on what to flash and what not to, since the potential to brick the device is significant.
Click to expand...
Click to collapse
I'm sorry to say this, but it's probably down to operator error. Making mistakes is just part of the learning process. Just use the full Google image and be done with it. Don't use OTA with Flashify or TWRP. You could have used flash-all.bat with the -w switch removed to leave your data intact, or used the full image with Flashfire retaining root and TWRP. FF makes life very easy, especially when the security updates come monthly.
Yes, this was my mistake. Flashify was messing up for whatever reason, the flashing via fastboot from the full factory image went through fine. I had not done it for a while since Flashify seemed to be doing a fine job with the N incremental upgrates.
GroovyGeek said:
Yes, this was my mistake. Flashify was messing up for whatever reason, the flashing via fastboot from the full factory image went through fine. I had not done it for a while since Flashify seemed to be doing a fine job with the N incremental upgrates.
Click to expand...
Click to collapse
It looks like the Flashify dev has moved on and abandoned his project in Dec. 2015. Flashfire is an awesome product that you should look into. It does have a bit of a learning curve, but well supported by Chainfire. You can still freeload until sometime next year. There is a dedicated thread here on XDA. Works a treat on regular monthly updates, although I prefer to use the full image with FF, rather than OTA. By default it will preserve root and recovery while flashing. Primer and FAQ can be found here. The only good news is you probably won't make that same mistake again!
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
travistyse said:
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
Click to expand...
Click to collapse
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
madbat99 said:
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
Click to expand...
Click to collapse
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
travistyse said:
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
Click to expand...
Click to collapse
The ota has a bunch of checks in it. If anything fails the checks, ota fails. When you root, there are system changes, boot.img changes, etc. All of which cause the ota to fail. Of course lineage and cm didn't have such strict checks in their update zips because they expect us to root and modify system. Manufacturers do not.
I just reflashed my OP5 back to a complete factory stock from Android 8.0, so its back to OOS 4.5.10 and Android 7.1.1 now after using this method: https://forum.xda-developers.com/t/...-0-9-oos-9-0-11-untouched-full-stock.3761706/
I've manually downloaded the latest OOS from oneplus canada website for the OP5, did a manual system install since OTA update doesn't seem to be working, and the phone does its thing initially, reboots, goes on to further install in stock recovery mode, and just as its about to finish it says installation failed..
after several hours now of non-stop testing and troubleshooting, I feel like hitting my head against a brick wall.. i've tried so many methods. manually installing results in failure everytime, I even just tried a sideload installation via ADB and STILL installation failed around the 55% install mark.
Im completely out of ideas on why the hell this wont work. reading up all these guides on the forums here for the OP5 and nothing seems to be working out for me.. everything I throw at this is giving me a failure to install, could really use the help of an expert here.
Solved - took me about 8 hours today lol, but i solved it by slowly flashing my way up from stock to android v10. at the transition between 5.1.7 to 9, required me having to extract the compatibility.zip out of the rom zips. but all in all, everything worked out and is now solved..phew!