Related
I'm rooted and using a N1 on Tmo. Will I still get the OTA update? Will it overwrite my root? Will I need to do anything else? Do I need to install it manually? Thanks!
PS - I'm using the image from here: http://forum.xda-developers.com/showthread.php?t=611829
it overwrote my root after installing the new OTA.
everything ran smooth but once i re-rooted it, wifi wouldnt work
risterdid said:
it overwrote my root after installing the new OTA.
everything ran smooth but once i re-rooted it, wifi wouldnt work
Click to expand...
Click to collapse
That's EXACTLY what happened to me. Are you still stuck like that, or did you find a solution?
tonyx3 said:
That's EXACTLY what happened to me. Are you still stuck like that, or did you find a solution?
Click to expand...
Click to collapse
Ok, success!!
When you re-rooted, did you use superboot 1.1? I did. And after that, it broke my Wi-Fi.
To fix it, I reflashed the main update from modaco, then used modaco's new superboot image, and voila! An updated phone, with root, and everything working!
Modaco's modded update and superboot are listed here:
http://android.modaco.com/content/google-nexus-one-nexusone-modaco-com/301729/03-feb-ere27-new-update-rooted-and-unrooted-optional-radio-optional-himem/
Note: You'll have to use Amon-Ra's recovery, instead of the stock recovery, to flash the modded updates
So is there any way to get these updates without having to re-root or rom again? Did you guys lose everything through the update? I'm not tooo root savvy. Thanks
If you're rooted...why flash the unrooted update? Seems counter-intuitive...
Just get CyanogenMod 5.0-beta4 and the new Gapps and radio. All links are in the CM thread.
I updated to 4.2.2 the other day, and it appeared that I lost both root and my custom recovery (TWRP), but my bootloader remained unlocked. Root-specific actions wouldn't work (e.g., TB wouldn't work, no access to root in Solid Explorer or Root Explorer, AdAway stopped working, etc.). This was despite having survival mode activated in SuperSu. I also learned I couldn't boot into recovery when I tried to restore a nandroid I made prior to updating.
Somehow though, root reappeared and everything works as normal, except I still cannot boot into recovery.
Any clue why my custom recovery disappeared permanently but root was preserved (albeit, root not preserved at first, but it DID end up coming back)? Also, can I just re-flash TWRP as I normally would?
Thanks.
moose&beer said:
I updated to 4.2.2 the other day, and it appeared that I lost both root and my custom recovery (TWRP), but my bootloader remained unlocked. Root-specific actions wouldn't work (e.g., TB wouldn't work, no access to root in Solid Explorer or Root Explorer, AdAway stopped working, etc.). This was despite having survival mode activated in SuperSu. I also learned I couldn't boot into recovery when I tried to restore a nandroid I made prior to updating.
Somehow though, root reappeared and everything works as normal, except I still cannot boot into recovery.
Any clue why my custom recovery disappeared permanently but root was preserved (albeit, root not preserved at first, but it DID end up coming back)? Also, can I just re-flash TWRP as I normally would?
Thanks.
Click to expand...
Click to collapse
Strange first I've heard of that with the N10. I would try to reinstall TWRP with Goomanager.
sfobrien said:
Strange first I've heard of that with the N10. I would try to reinstall TWRP with Goomanager.
Click to expand...
Click to collapse
mine did the same, as mentioned above I just re-installed TWRP with goomanager and everything is back to normal.
I might have misunderstood, did you guys do the OTA? Got my forums mixed up thought we were talking about flashing CleanROM.
sfobrien said:
I might have misunderstood, did you guys do the OTA? Got my forums mixed up thought we were talking about flashing CleanROM.
Click to expand...
Click to collapse
No worries. And yeah, I did the OTA, but held off until Google pushed a notification to my N10 for the update. I'll give goomanager a try. Appreciate the replies. Thanks.
This is normal behaviour in a OTA update. Installs a couple of files that, if a custom recovery is installed, reflash stock recovery on reboot. This doesn't happen if you flash a factory image.
A bit off topic but, there was the need to have device at stock condition (everything stock) before running OTA process, but as of now and personal experience, twrp 2.4.1.0 can also run an OTA update straight from Android.
Sent from my Nexus 10 using xda app-developers app
three west said:
mine did the same, as mentioned above I just re-installed TWRP with goomanager and everything is back to normal.
Click to expand...
Click to collapse
Thanks - I'll give goomanager a try.
beekay201 said:
A bit off topic but, there was the need to have device at stock condition (everything stock) before running OTA process, but as of now and personal experience, twrp 2.4.1.0 can also run an OTA update straight from Android.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I assumed the same, but I got the same situation as OP, I'll try reinstalling TWRP using Nexus Root Toolkit, or does goomanager have a special functionality for those conditions?
Update: Used NRT to install TWRP in the advanced settings, worked beautifully.
The latest Google OTA's are not successfully installing unless you restore stock recovery fist and some are failing if you are rooted as well.
Best bet if you are running as rooted or custom recovery is to backup first, un-root, restore stock then sideload the OTA. This will save you lots of frustration and heartburn.
It's easy enough to restore stock and to re-root so just make it part of your ota routine.
Anyone figure out how to root the new OTA? It wont allow root with the old flash way since its new OTA
timenewton said:
Anyone figure out how to root the new OTA? It wont allow root with the old flash way since its new OTA
Click to expand...
Click to collapse
Yes use the new IOROOT15 to root the device. But I have been unsuccessful in flashing any roms, however I did get twrp to work with FreeGee app in the android market.
I appreciate your help very much, thank you
jea508 said:
Yes use the new IOROOT15 to root the device. But I have been unsuccessful in flashing any roms, however I did get twrp to work with FreeGee app in the android market.
Click to expand...
Click to collapse
What version of twrp? Sounds like you may need to update.
Sent from my LG-D800
btm fdr said:
What version of twrp? Sounds like you may need to update.
Sent from my LG-D800
Click to expand...
Click to collapse
Im still using the twrp that was flashed with freegee. i'm a newb to all this. Maybe i should flash new version of twrp and try. I was trying to install the mal 4.2.2 rom and just got lg screen, then black.
jea508 said:
Im still using the twrp that was flashed with freegee. i'm a newb to all this. Maybe i should flash new version of twrp and try. I was trying to install the mal 4.2.2 rom and just got lg screen, then black.
Click to expand...
Click to collapse
I've been unsuccessful in getting any roms to work. I tried 4.2.2 rom and got lg screen then black, had to restore nand backup from twrp recovery but it was hellish to get into, had to do the hold vol+pwr precisely, almost gave up. So, reverted to a backup just fine.
Next tried to loki_flash recovery 2.6.3.1 (then was going to do them in order-2.6.3.2>2.6.3.3 [have not tried going directly to 2.6.3.3) and was hit with an unsupported aboot error (device mismatch).
So now i'm going to try and use flash tool to revert back to 11A, root, install twrp (I hope this is possible and I don't brick my phone [i'm new to all of this])
Anyone tell me if this is an acceptable option to proceed? Thank's in advance.
Acceptable. KDZ to 11A.
Just wanted to post I was successful using lg flash tool to revert to 11A, rooted, freegee twrp, flashed 2.6.3.3, flashed OSE ROM. Everything is well ATM!
Sent from my LG-VS980 using Tapatalk
Everytime i reboot from recovery, i get this error message. I can either choose, yes fix root, or no reboot now. On 4.3 pacman, tried flashing supersu 1.65, tried updating Superuser binaries through recovery with SuperSU, and im still getting this. Any other way to fix this?
Say no. You won't lose root. I can't remember why that shows up, but just choose no.
Sent from my Nexus 4 using xda app-developers app
When i updated to 4.3 i started getting this. So i unrooted and re rooted, and the error was gone. Then titanium backup started telling me my su binaries needed to be updated, so i updated with supersu pro, and the error message came back. I know it seems harmless, but one in a while i have issues with apps that require root. Nothing major, just curious if theres a way to fix it.
Im curious, what happens if you click yes?
sinndissension said:
Im curious, what happens if you click yes?
Click to expand...
Click to collapse
it happened to me with stock rom. pressed yes, pressed no, unroot and root again nothing. after that i flashed twrp recovery and problem solved. to tell the truth twrp is better for me...
The RS988 finally has a new OS update with Google patch level Dec 1st, and that means that we are finally good against blueborne and krack!
Sent from my RS988 using Tapatalk
I just installed it. It's about time. I was beginning to wonder if they had stopped support on the RS988. I hear the LG G5 is supposed to get Oreo, but I have a feeling that the RS988 will get left out based on how the updates have gone so far.
Hi! Has the modem changed?
I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?
Nispero said:
I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?
Click to expand...
Click to collapse
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk
kattolo said:
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk
Click to expand...
Click to collapse
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader
spinoza_web said:
Hi! Has the modem changed?
Click to expand...
Click to collapse
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info
Nispero said:
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader
Click to expand...
Click to collapse
the best source of full stock roms as well as info on the phone I could find so far is https://forum.xda-developers.com/lg-g5/how-to/info-autos-g5-thread-t3350648
The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.
kattolo said:
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info
Click to expand...
Click to collapse
Here's the baseband version with RS98821c: MPSS.TH.2.0.c1.4-00047-M8996FAAAANAZM-1.88674.1.101802.1
The numbers are slightly different at the end compared to RS98821d , but I'm not sure what if anything might have changed.
maybe, for getting OTA should we just get unroot? How to do it properly?
If recovery is not the stock one, it will not be possible to install the OTA.
Alternatively you might need to wait for someone to make a flashable zip you could flash with TWRP, but given the fact development on this phone is not too active you might need to wait for a while before is available
Sent from my RS988 using Tapatalk
Awkydee said:
The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.
Click to expand...
Click to collapse
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.
brewerywagon said:
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.
Click to expand...
Click to collapse
First I flashed the magisk uninstaller and rebooted back to recovery. Then I flashed the 21c COMPLETE ZIP and didn't flash magisk so it would replace TWRP with the stock recovery on reboot. Then I rebooted and when I tried to update it went to the stock and threw up an error then rebooted. Upon reboot it displayed a message saying that I couldn't update because my device had been rooted. So I rebooted back in to bootloader and flashed TWRP again. Then I flashed 21a COMPLETE ZIP and no magisk so that the stock recovery would replace TWRP. I rebooted and went through setup and took OTA updates until I was on 21d. Then rebooted back into bootloader and flashed TWRP. Then rooted and we've through setup. I tried every other way but this was the only way that worked for me. I hope it helps!
should be an easier way. Did u see some changes to the radio?
Some of you may remember that last year I had the misfortune of installing the Brightpoint ROM on my Unlocked G5, which completely messed the phone up by not allowing it to connect to AT&T's LTE. It was a process to re-flash the older ROMs/Bootloader and then rebuild it to a stable 21c. I had used it for a while like that, and the only problem I had was that when ending a voice call (HSPA) it would take a while to change back to LTE.
I ended up going with the S8 over the summer (Samsung discount + Note 2 trade in) which got it for $18/month. I've been using it ever since and the LTE to HSPA Voice to LTE change-off on the S8 is done within a second, unlike the G5.
My mom had been using an unlocked Samsung S5 for almost a year now, and it's constantly dropping calls, and this past week it froze on her and required a battery pull, so was thinking of having her try out my (unused) G5 to see if she liked it more. When I turned the G5 on today, I updated all the apps, and then installed the 21d OTA update. The hand-off from voice to LTE still is not as fast as my S8, but seems to be improved from the 21c firmware.
ROM Posted
Just to let you all know, I have posted the latest 21d stock ROM in my thread here: https://forum.xda-developers.com/lg-g5/development/stock-21c-roms-flashable-zips-imgs-t3679907
Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.
ingressor said:
Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.
Click to expand...
Click to collapse
I'm not having any reboot issues when playing music.