I have rooted my LG G3 with towelroot bruteforce, I would like to update the OTA 30 oct update but receive the 0X117008, update unavailable your device is rooted.
I have readed a lot of topics on XDA about this but cant find the solution. Done a factory reset, also tried to remove the rooted via SuperSU, but didn't work.
Android 4.4.2
kernel 3.4.0
software v10c-204-16
T-mobile
Could someone point me in the right direction please thank you
Related
Hey folks,
I just got my Nexus 7 and updated it to 4.4.
After that I unlocked and rooted it using a tool made by wug(something). After successfully doing that I realized that there was 4.4.2 update, as it showed me a notification in the top drawer.
So I went ahead and reinstalled stock firmware + unroot (using said tool). I used KRT16S factory image to do that.
After that I did another fac. reset as suggested but now I can't seem to be able to update to 4.4.2 anymore. When I search for updates on the tablet it says I am already on the newest version...
Is my N7 bricked? How can I update? Please help...
Your tab is not bricked at all.
daZza92 said:
Hey folks,
I just got my Nexus 7 and updated it to 4.4.
After that I unlocked and rooted it using a tool made by wug(something). After successfully doing that I realized that there was 4.4.2 update, as it showed me a notification in the top drawer.
So I went ahead and reinstalled stock firmware + unroot (using said tool). I used KRT16S factory image to do that.
After that I did another fac. reset as suggested but now I can't seem to be able to update to 4.4.2 anymore. When I search for updates on the tablet it says I am already on the newest version...
Is my N7 bricked? How can I update? Please help...
Click to expand...
Click to collapse
If you can still use your nexus and browse settings, your tablet is working properly. I have the same problem, my OTA checker tells me it is up to date but it isn't. You can ADB sideload the firmware update instead using your PC.
You can follow the method from this site:
htt p://w ww.a ndroidbeat.c om/2013/12/manually-install-android-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/
remove 4 spaces..
DISCLAIMER: Once again, read the site's disclaimer and i am not responsbile of any further occurrence of bad things on your device. Always read instructions and search for answers in this forum or anywhere else. Thanks.
My E975 is rooted (not boot unlocked), I can download this update and the device restarts, then after a short time an error message comes up, the device restarts and loads as normal, then a message pops up that states root suspected, so cannot update
This appears to be a protective mechanism against rooting, so updates are only available for unrooted devices
Now, the solution seems simple, I unroot, update and then root again, however, I suspect it's not this simple
Can someone please advise if there is a workaround or would the simple option work?
As I don't want to lose root
Thank you
This solution has been suggested - http://forum.xda-developers.com/showthread.php?t=2625044
Which seems like much work for a small update
Is there any other method?
Current Software Version: Stock JB 4.1.2 (E97510h-EUR-XX)
I've unrooted and made sure there is no trace left, have restarted the device, then downloaded the V10J update via OTA, ran the update process, got to the update screen and at 3% progress get error 0x13E, device restarts and there is another error message that states:
- Software update, problem with installation
Have tried to update OTA 3 times and the issue is the same each time, I wonder if this is the same issue as last year on the AT&T version:
- http://forum.xda-developers.com/showthread.php?t=2223994
- http://forum.xda-developers.com/showthread.php?t=2084211&page=2
Also on other versions too:
- http://forum.xda-developers.com/showthread.php?t=2051819
- http://forum.xda-developers.com/showthread.php?t=2289930
If anyone can help or hopefully explain what the error 0x13E is cause by/relates to?
Please reply here and it will be much appreciated :good:
Current Software Version: Stock JB 4.1.2 (E97510j-EUR-XX)
Gave up on OTA, soft bricked my device shortly after and used the KDZ Updater method from the FAQ (http://forum.xda-developers.com/showthread.php?t=2434917), which updated my device, so I'm going to leave it there for now
Also, if anyone is wondering (like I was), yes, stock JB 4.1.2 (E97510j-EUR-XX) can be rooted via Framaroot, using the gandalf exploit and I had no related issues
Thank you :good:
So my device was previously rooted on 4.4.2 and at the beginning of December there was an update available. I got excited thinking it was 5.0 so I decided to update. Well all it was was a patch I'm still on 4.4.2 unrooted now and I CAN'T get rerooted.. I've tried purpledrake I've tried stump (original root method) and I've tried ioroot.. None of which have worked.. Any suggestions out there?
Sprint LG g3 ls990
imhalfdead said:
So my device was previously rooted on 4.4.2 and at the beginning of December there was an update available. I got excited thinking it was 5.0 so I decided to update. Well all it was was a patch I'm still on 4.4.2 unrooted now and I CAN'T get rerooted.. I've tried purpledrake I've tried stump (original root method) and I've tried ioroot.. None of which have worked.. Any suggestions out there?
Sprint LG g3 ls990
Click to expand...
Click to collapse
1) Wrong section. There is a special forum for sprint's g3, go post in there.
2) Basically, you have to downgrage to rootable firmware, root it, install twrp, install newer (and already rooted) rom via it.
Okay thank you sorry.
So, for a previous OTA update on 4.4 KitKat that brought some bug fixes, I could simply do a temporary unroot and use OTA survival mode with Superuser/SuperSU.
Now, with this new OTA that updates the OS to Lollipop, none of that seems to work. It always detects that the device is rooted and I don't know how.
So, does anyone have any idea how to apply this Lollipop OTA with a rooted device? How to avoid OTA rooted phone detection?
The last resort is to either use SuperSU to unroot fully or flash a fresh stock ROM... and none of those are satisfying.
Thanks in advance!
It's more than obvious that you need to flash a stock rom for OTA to function properly.
Masta Sukeh said:
So, for a previous OTA update on 4.4 KitKat that brought some bug fixes, I could simply do a temporary unroot and use OTA survival mode with Superuser/SuperSU.
Now, with this new OTA that updates the OS to Lollipop, none of that seems to work. It always detects that the device is rooted and I don't know how.
So, does anyone have any idea how to apply this Lollipop OTA with a rooted device? How to avoid OTA rooted phone detection?
The last resort is to either use SuperSU to unroot fully or flash a fresh stock ROM... and none of those are satisfying.
Thanks in advance!
Click to expand...
Click to collapse
Well, you can play around with RCT, there are guides on resetting that.
Though it's not gonna work, such a big upgrade will break root regardless of ota survival mode or whatever. Or you will get a bootloop...
Do it the right way. Install TWRP, then install rooted LL rom.
Masta Sukeh said:
So, for a previous OTA update on 4.4 KitKat that brought some bug fixes, I could simply do a temporary unroot and use OTA survival mode with Superuser/SuperSU.
Now, with this new OTA that updates the OS to Lollipop, none of that seems to work. It always detects that the device is rooted and I don't know how.
So, does anyone have any idea how to apply this Lollipop OTA with a rooted device? How to avoid OTA rooted phone detection?
The last resort is to either use SuperSU to unroot fully or flash a fresh stock ROM... and none of those are satisfying.
Thanks in advance!
Click to expand...
Click to collapse
Hi! I'm in South Korea and I had the exact same issue on KK.. I always used to flash the stock and then update KK... HOWEVER .....I didn't receive OTA update on Lollipop. I connected my phone to LG PC Suite and the phone updated from there.. and I didn't have to unroot. Have you tried connecting your phone to LG PC Suite and update from there? Good luck
IMO.. Lollipop sucks! I went back to KK after trying Lollipop for a few days.
Hello Guys
another question,i have E980 AT&T but if i returned to stock JB can i update to KK from the phone Software Update OTA? kindly dont answer if you are not sure
Still waiting...
I can't believe that there isn't anyone can answer this inquiry....
People aren't answering because you can find the answer by doing the search, consider these type of questions are discussed a year ago. Yes, you're safe to install through the OTA update as long you're not rooted while you're updating. If you're rooted while doing the OTA update, you will most likely end up with the bootloop.
hawkwind212 said:
People aren't answering because you can find the answer by doing the search, consider these type of questions are discussed a year ago. Yes, you're safe to install through the OTA update as long you're not rooted while you're updating. If you're rooted while doing the OTA update, you will most likely end up with the bootloop.
Click to expand...
Click to collapse
first of all thanks for your reply, second thing, i know that im safe to do an upgrade through OTA and i know that for sure i dont have to be rooted, and my question is IF i went back to 4.1.2 (JB) can i upgrade officially OTA to KK 4.4.2 if i entered the (software update menu)?
I didn't say to be rooted, I meant it's unsafe to do an ota update if you were rooted. If you flashed the stock jb ROM, and wanted to update to stock kk using the ota, you're safe to do so as long you don't root before your update. Is that what you're asking?
Thanks again for responding, but in my question at the begining i didn't mention the root issue, and i know that u cant update ota if u r rooted, and what im.asking for is when i return to JB 4.1.2 and i want to have the official KK can i updated ota?
My E980 performed this update OTA some time ago. I purchased my E980 when it was ~1 year old from AT&T so it was $50. I suggest you check the AT&T support site to see fi you can update it via them if you step down to 4.1.2. The issue is that the update may no longer be pushed to your phone and you may be required to perform the update manually.