This new update is garbage, greatly reduced my battery life, wifi off, cloud sync off, minimal apps installed.
How do I rollback update?
Thru companion app im going to do the same...
---------- Post added at 06:38 PM ---------- Previous post was at 05:54 PM ----------
After trying it out it seems like Sony updated the companion app with 5.1 aswell. From here im not sure how to roll back.
sony pc companion says: Sony Update Engine doesn't have software available for your phone
any solution?
My guess would be that you would have to find the 5.02 image file on the forums and flash it through ADB.
I'm not sure you can.
If fact if you could I suspect OTA would update without asking you.... The update before the last one did for me.. I had it on charge looked over to it and it was rebooting after installing the update. No warning, No questions... just did it.
So I wondered this at the last update--from v4 to v5--and after much research, AndroidWear is very much like any Android rom on a phone or tablet. Officially, going backwards in an update is impossible using the stock recovery because each OTA only allows for an update from x version to y version and will error if you try to update from w version. The only way to get backwards is to unlock the bootloader, replace the recovery with something like TWRP and flash an old image. Among many problems that you might experience though is that OTAs are not system images in that they sometimes they only update specific partitions. In short, you run the risk of bricking your watch, just as you could with a phone or tablet.
If you can live with it, keep it. If you can't, start doing your research.
Isn't there a repacked stock rom in development forum? It gets flashed via twrp
Is there a way to block updates from getting pushed to the watch?
Related
I have the AT&T Galaxy Note 2, rooted, which is why I think it has been unable to install the last software update from AT&T. Every time I try, my phone will download the update but will fail 28% of the way through the install, I think this may be due to the root but I don’t know enough about this stuff to be sure. This is why I joined XDA, so that I could ask people smarter than me how to do the things I’m looking to do. If it is the root that’s the problem, then I imagine I’ll need a custom FW instead, there are a lot of listings here and I don’t know what is what or which update would be right for me, so I am asking for some help;
My phone is the SGH-I317
Android version; 4.3
Baseband version; I317UCUBMK6
Kernel Version; 3.0.31-2048209 [email protected] #1 Tue Nov 19 16:46:45 KST 2013
I don’t know if any of the info above is useful, I just want to keep the device up to date, nothing fancy, just whatever the most recent AT&T update is I want. I’m just not sure which of the many custom ROMs I should focus on.
watchdog-prime said:
I have the AT&T Galaxy Note 2, rooted, which is why I think it has been unable to install the last software update from AT&T. Every time I try, my phone will download the update but will fail 28% of the way through the install, I think this may be due to the root but I don’t know enough about this stuff to be sure. This is why I joined XDA, so that I could ask people smarter than me how to do the things I’m looking to do. If it is the root that’s the problem, then I imagine I’ll need a custom FW instead, there are a lot of listings here and I don’t know what is what or which update would be right for me, so I am asking for some help;
My phone is the SGH-I317
Android version; 4.3
Baseband version; I317UCUBMK6
Kernel Version; 3.0.31-2048209 [email protected] #1 Tue Nov 19 16:46:45 KST 2013
I don’t know if any of the info above is useful, I just want to keep the device up to date, nothing fancy, just whatever the most recent AT&T update is I want. I’m just not sure which of the many custom ROMs I should focus on.
Click to expand...
Click to collapse
Ya idk y usually it just unrooted the phone and flashed it are you on stock recovery?
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
This will help you get to 4.4.2
http://forum.xda-developers.com/showthread.php?t=2618447
terpin32 said:
Ya idk y usually it just unrooted the phone and flashed it are you on stock recovery?
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
This will help you get to 4.4.2
http://forum.xda-developers.com/showthread.php?t=2618447
Click to expand...
Click to collapse
I'll give it a go, one question though, will it cancel my root? Am I going to have to root the phone again afterwards?
Yes it will unroot but after you get to 4.4.2 just use cf autoroot and you'll be rooted again
It's not the root access it's the custom recovery that stops the Ota update.
How does that happen?
The Ota update runs a script that downloads the rom, attempts to boot into recovery, where it does a system wipe, then installs the rom. So it fails at that point, and continues to boot loop, because it's stuck on that step in the script.
OK, well is there a repair for that? That sounds like an error in the program itself, or is it because reversing a "root" is an involved process.
It's not an error. Samsung doesn't support people messing with the phone, and the scripts they write won't support custom recoveries. Just follow the steps in the link above.
My GS3 used to be rooted, but I had to install MDM/Airwatch on it for testing at work, so I unrooted it. The unroot was successful and MDM didn't complain, and it's pretty picky. That was a few months ago.
Now Sprint or Samsung is pushing an update to the phone (I don't know exactly what it is) but when I try to run the update, it reboots and extracts then gets an error complaining that /system/priv-app/GoogleServicesFramework.apk has unexpected contents.
I tried doing the update through Kies and it fails with an error saying that the phone was disconnected, even though it wasn't. I even set the phone to not sleep and no screenlock just so the connection would stay alive, but get the same error.
I did a factory reset but that didn't help. It seems like there's a problem with that APK but I don't know what to do about it.
So I just reimaged my wife's S3 with an unrooted image I'd previously downloaded. Everything seems fine but when I try to apply this same update, it gets the exact same error!
Do I need to reimage these phones with something different to get the updates working?
Philomorph said:
My GS3 used to be rooted, but I had to install MDM/Airwatch on it for testing at work, so I unrooted it. The unroot was successful and MDM didn't complain, and it's pretty picky. That was a few months ago.
Now Sprint or Samsung is pushing an update to the phone (I don't know exactly what it is) but when I try to run the update, it reboots and extracts then gets an error complaining that /system/priv-app/GoogleServicesFramework.apk has unexpected contents.
I tried doing the update through Kies and it fails with an error saying that the phone was disconnected, even though it wasn't. I even set the phone to not sleep and no screenlock just so the connection would stay alive, but get the same error.
I did a factory reset but that didn't help. It seems like there's a problem with that APK but I don't know what to do about it.
Click to expand...
Click to collapse
Philomorph said:
So I just reimaged my wife's S3 with an unrooted image I'd previously downloaded. Everything seems fine but when I try to apply this same update, it gets the exact same error!
Do I need to reimage these phones with something different to get the updates working?
Click to expand...
Click to collapse
in order to completely unroot your phone and hers is to Odin the stock tar...and since the both of you are on Sprint you can take the NJ2 tar...which is the Update that you are trying to install
Thanks, I'll give this a try! Do you think this is going to be a problem going forward though, where I can't get OTA updates anymore? The ROM I used put me on ND8 and is called:
L710VPUCND8_L710SPRCND8_L710VPUCND8_HOME.tar.md5
I'm not 100% sure where I downloaded it from, but I think it was from the link in this thread: http://forum.xda-developers.com/showthread.php?t=2738533
Philomorph said:
Thanks, I'll give this a try! Do you think this is going to be a problem going forward though, where I can't get OTA updates anymore? The ROM I used put me on ND8 and is called:
L710VPUCND8_L710SPRCND8_L710VPUCND8_HOME.tar.md5
I'm not 100% sure where I downloaded it from, but I think it was from the link in this thread: http://forum.xda-developers.com/showthread.php?t=2738533
Click to expand...
Click to collapse
Well ND8 and NJ2 are both 4.4.2 just NJ2 is a security update on top of ND8 and it will break root via Towel Root but the other 2 methods will still work
Doh wish I'd seen this before posting my own. Same exact problem here.
Where does one get the NJ2 tar? And will I be able to update after that? Otherwise how can we fix it so we can run updates and not have to wipe our phones every time?
---------- Post added at 04:05 PM ---------- Previous post was at 03:24 PM ----------
Guessing this is it? http://forum.xda-developers.com/gal.../stock-l710vpudnj2-pc-odin-flashable-t3007847
dtseiler said:
Doh wish I'd seen this before posting my own. Same exact problem here.
Where does one get the NJ2 tar? And will I be able to update after that? Otherwise how can we fix it so we can run updates and not have to wipe our phones every time?
---------- Post added at 04:05 PM ---------- Previous post was at 03:24 PM ----------
Guessing this is it? http://forum.xda-developers.com/gal.../stock-l710vpudnj2-pc-odin-flashable-t3007847
Click to expand...
Click to collapse
NJ2 is the update....
6th_Hokage said:
NJ2 is the update....
Click to expand...
Click to collapse
Right. I've gone ahead and applied it manually and it seems fine for now. But I'd like to be able to just apply them from OTA like a pleb without having to download **** and run Odin.
dtseiler said:
Right. I've gone ahead and applied it manually and it seems fine for now. But I'd like to be able to just apply them from OTA like a pleb without having to download **** and run Odin.
Click to expand...
Click to collapse
only sure way to OTA is to be completely stock including recovery...
6th_Hokage said:
only sure way to OTA is to be completely stock including recovery...
Click to expand...
Click to collapse
I've confirmed that I have the stock android recovery as well.
Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376
jfreshh330 said:
Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376
Click to expand...
Click to collapse
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triangle deal.
So try and find one thats a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the T-Mobile files. As mentioned though, just make sure the stock recovery is from Android 4.4.X or 5.X.X and you will be fine.
flexfulton said:
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triange deal.
So try and find one that a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the AT&T files. As mentioned though, just make sure the stock recovery in from Android 4.4.X or 5.X.X and you will be fine.
Click to expand...
Click to collapse
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.
jfreshh330 said:
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.
Click to expand...
Click to collapse
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!
flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
Click to expand...
Click to collapse
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?
flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!
Click to expand...
Click to collapse
Awesome thanks so much!
jfreshh330 said:
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?
Click to expand...
Click to collapse
Sideload the latest recovery as found in the thread I linked to above. Reboot and the OTA should take no problems. It was downloading and everything fine for you before but was unable to flash because of an outdated recovery you installed.
So my recommened method to update OTA, is to follow the first route you were taking but with the newest recovery.img file in place of what you used in step 1.
If you already have the OTA downloaded on your phone, you shouldn't have to download it again either. It should see that it's already downloaded ready to be installed.
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
jfreshh330 said:
Awesome thanks so much!
Click to expand...
Click to collapse
No problem. Let me know how it turns out for you.
If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).
redpoint73 said:
If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).
Click to expand...
Click to collapse
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.
flexfulton said:
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Click to expand...
Click to collapse
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
flexfulton said:
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.
Click to expand...
Click to collapse
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.
redpoint73 said:
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.
Click to expand...
Click to collapse
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.
flexfulton said:
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Click to expand...
Click to collapse
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
flexfulton said:
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.
Click to expand...
Click to collapse
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.
redpoint73 said:
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.
Click to expand...
Click to collapse
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
I was trying to help out as I had the same issue when I went to update. I installed a recovery that was too old, determined that I needed to flash a recovery from either 4.4.X or lollipop and my OTA update was fine after that. Point being, I could go ahead and flash a newer recovery to get the OTA to download.
Anyway I applogize if I was in error in my help. No one else was helping and based on my own experiences it sounded like the same issue.
flexfulton said:
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
Click to expand...
Click to collapse
OTAs will normally only allow you to install from the immediate previous version (you cannot skip a version). Sometimes they are complete packages; but often they are not. Sometimes the OTA just contains what has been changed; basically a "patch". And for that reason, the updates need to be installed sequentially. In fact, I've seen folks brick due to unwittingly installing partial firmware packages from OTAs (with s-off, which bypasses such safety checks).
flexfulton said:
Anyway I applogize if I was in error in my help.
Click to expand...
Click to collapse
There's no need to apologize. As you are well aware, this is a self-supporting community that flourishes due to the contributions of its members. Your answers may not have been 100% correct. But it was well intended; and you answered to the best of your knowledge. At least you learned something and can pass it along now. I'm just a member who passes along what I've learned here also (don't have any specialized developer knowledge or anything); and I'm certainly not right all the time.
So the recovery 3.32.5312 will not work? And i apologize i am on 4.4.4 not 4.4.2
Hi everyone. I need to know if it's possible to downgrade from CM13 to the stock rom/firmware my phone came with which is Jellybean 4.3. I decided to upgrade my OS so I could try out Pokemon Go. Originally I was just going to upgrade to 4.4 which is the minimum version required for the app but I decided I might as well upgrade to the newest one. The newer the better right? And I would also be future proof for any other apps that might require a newer OS. But not only did I not like Pokemon Go, which I ended up uninstalling, (I don't know how such a simple bare bones game like that is so popular) I also don't like marshmallow. Some features are missing that I had in 4.3 like Double Tap to Top where you can double tap the top of the phone to quickly scroll to the top of the screen or the option to hide folders in the gallery which is bare bones and has no options or features. I can't move apps from one screen to the next with my thumb like I used to because I have to push the app as far past the edge of the screen as possible in order for the screen to switch so I have to use my index finger to do it. I'm thinking this is because it was designed for the edge which has the screen going over the side of the phone. I also just don't like the look of Marshmallow compared to Jellybean. And my phone takes forever to boot up now clocking in at about a minute and a half. Instead of gaining access to something better that previously wasn't available to me I feel like I forced something on the phone that doesn't belong and shouldn't be there.
If anyone can help me downgrade I would appreciate that very much. I tried to do it with the same method I used to upgrade by rooting the phone again with odin and then just flashing the stock OS but odin didn't work (I already had CyanogenMod installed from when I upgraded). Odin gave me the confirmation that I successfully rooted my phone but when I checked it with a root verification app it said my phone wasn't properly rooted and SuperSU also says there's no root detected. I'm sure this has something to do with me having marshmallow this time instead of jellybean. I tried using google for help but I couldn't find anything about my situation. Now I don't know what to do which is why I'm here. This was my first time installing a different OS so I'm new at this.
I'm guessing you could use the root66 version to flash back to stock with root.
Sent from my Amazon Jem using Tapatalk
---------- Post added at 07:22 PM ---------- Previous post was at 07:21 PM ----------
http://forum.xda-developers.com/showthread.php?t=1949687 for the root66 thread
Sent from my Amazon Jem using Tapatalk
Thanks for replying. I'll look into it. I also recently found something that might do the trick. It's a how-to guide for my phone on unrooting it and restoring the stock firmware.
Problem solved. Turns out all I had to do was install the stock firmware with odin. I didn't have to root my phone again. Then I updated to the latest version of Jellybean with Samsung Smart Switch. I'm glad I was able to figure it out.
Hi!
I used my G5s for roughly 1 week now with the stock 7.1.1. I just unlocked the bootloader, flashed TWRP and rooted it.
Today i installed an OTA update which results in a bootloop... Well, it boots into TWRP, but i am not able to get into the normal boot...
Anyone got the same problems? I'm quite desperate atm and dont know how to resolve/debug it.
Flashing the stock rom is the absolute very last thing i am considering.
it's because you're root, you have to flash the rom stock.
the cmd gpt.bin will probably not pass, it is serious go to the next.
Seriously? I now have to decide between no OTA updates with root or OTA update with no root? Thats crappy!
Well, at least i do seem to have found a workaround.
Power on -> TWRP -> bootloader -> start normal
That works...
Alright, so i will not apply any update without before LOS arrives for the G5s
I'm a bit disappointed by this update because they added LinkedIn app as system app and "forgot" to mention that in changelog; I bought this phone because bloatware was minimal and now thay started to add unrequested app to system
Yeah Lenovo isn't Motorola ...
Since my G5s is still running with the android security patches dated to june 1st 2017, i feel like it really need an update. LOS is not available, so OTA is the way to go.
Does anybody know a way to bypass/resolve the gpt.bin problem mentioned above when OTA-updating a rooted G5s?
To be honest, my workaround to resolve the boot issue (see startpost) would be fine for me. But i am afraid that another OTA update makes matters worse...
nexx2 said:
Since my G5s is still running with the android security patches dated to june 1st 2017, i feel like it really need an update. LOS is not available, so OTA is the way to go.
Does anybody know a way to bypass/resolve the gpt.bin problem mentioned above when OTA-updating a rooted G5s?
To be honest, my workaround to resolve the boot issue (see startpost) would be fine for me. But i am afraid that another OTA update makes matters worse...
Click to expand...
Click to collapse
Here is your LOS
https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-14-1-t3727918
if you want back to stock follow this:
https://forum.xda-developers.com/mo...h-official-firmware-moto-g5s-montana-t3687768
---------- Post added at 03:59 PM ---------- Previous post was at 03:54 PM ----------
bellabax said:
I'm a bit disappointed by this update because they added LinkedIn app as system app and "forgot" to mention that in changelog; I bought this phone because bloatware was minimal and now thay started to add unrequested app to system
Click to expand...
Click to collapse
The LinkedIn app is in the OEM partition of the phone. Its was not form the update.
You can use LOS 14.1(No bloatware):
https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-14-1-t3727918
Bloody hell, i totally didnt see this. Thanks for the hint!
But anyways, i think i wait für LOS 15 for our G5s and wont install any OTA updates in the meantime
nexx2 said:
Bloody hell, i totally didnt see this. Thanks for the hint!
But anyways, i think i wait für LOS 15 for our G5s and wont install any OTA updates in the meantime
Click to expand...
Click to collapse
Me too... When we will see an Oreo rom? Once the Oreo rom announced I will root my phone and install it..
Just wondering if the Lenomoto will release Oreo by the end of March?