Hi,
Searched the forums & Google and found nothing on this..
I got this Software Update notification on my Bell E973 : V20H-MAR-08-2013 (428.33MB)
I was wondering which Android version this was (ICS, JB) ?
If it's still rootable, if anyone tried it, etc.
I am still on stock (although rooted) on version 10h which is Android 4.0.4.
If I ever want to try it, should I unroot first ? should I get OTA rootkeeper ?
Thanks,
I won't be able to answer all the questions, but I guess someone else will also contribute.
Its Jelly Bean 4.1.2.
I have tried, but I installed the KDZ file which should be basically the same.. I think. I couldnt rooted it using ZV9 (CurrentRoot.bat). But maybe there is a difference in installing from the KDZ (not OTA). Because the file is 1gb+ so the image starts from scratch.
I liked more the houstonn's stock version. Reason: there are QSlide application, which you can have as windows on your phone (although I don't like them to be in the notification bar all the time)
This is interesting: http://forum.xda-developers.com/showthread.php?t=2198258
Thanks for the info and the link to the other thread.
I tried updating it, but it brings up an error saying the phone is suspected of rooting then stops.
Makes sense because I was rooted, with busybox and Superuser apk (SuperSu) also installed.
Full Unroot, uninstall, etc.
...
Right now my phone has neither the su binary, nor the superuser apk, nor busybox, etc.
and it still gives off the error when I try the FOTA update.
I never unlocked the bootloader until now, but might as well and just flash the last update directly.
(the FOTA makes you re-download the whole 400+MB each time you try it..)
Related
Trying to install the new 4.7.3 update from Verizon that just came out the other day. The update wont install on my droid pro because my VCast.apk fails the hash check for some reason even though its there and installed. Im doing it from recovery console so i can see were its failing. I did backup the VCast.apk with TB and and then delete it. Then restored it from backup just fine. I guess TB must do something to it because now the hash check is failing for the apk?
Anyone have this VCast.apk they could provide to me from a stock Droid Pro running Android 2.3.3 so i can update?
I have the app on home but cant find it under system/app. Where can i found it and under what name?
Could you get from your phone the blurcamera.apk. Cant update cause missing this app.
Thanks
I think at this point it just would make more sence to sbf back to 2.3.3 and then take the new update. Who knows what other files it will complain about once we fix those. there is a sbf in the forms that looks promising. It seems to be a stock US Verizon 2.3.3.
Just a followup.
Today I SBF back to 2.3.3 stock, rooted again, installed OTA rootkeeper and took the 2.3.4 android update. The update installed just fine now. Then restored root with OTA rootkeeper and all is good.
I have never received an Android OTA update, so with all of the JB OTA talk, I have a noobish question that I have not found an answer for.....
Since I am rooted with only minor tweaks here and there to the stock ROM (4.0.4), what will the OTA message say if I have teaked too much? Will it say that I am ineligible, will I just never get an update message, or will it try to install and then fail?
Thanks.
b177y said:
I have never received an Android OTA update, so with all of the JB OTA talk, I have a noobish question that I have not found an answer for.....
Since I am rooted with only minor tweaks here and there to the stock ROM (4.0.4), what will the OTA message say if I have teaked too much? Will it say that I am ineligible, will I just never get an update message, or will it try to install and then fail?
Thanks.
Click to expand...
Click to collapse
b117y,
I had this kind of question when I was still using root apps, and I would recommend backing up using OTA Rootkeeper, Titanium Backup, and finally ClockworkMod/ROM Manager, in that order, before updating anything.
As far as I know, it depends on the tweaks. For example, if you have a non-stock kernel, have modified essential system files, or have anything besides bootloader PRIMELA03 or radio I9250XXLA02 (assuming your devices is a HSPA+ 'maguro' version,) the update will most probably fail.
But for simple root tweaks, like LightFlow (not compatible with JB at the moment), Nova Launcher (installed as system or user app, it shouldn't matter), Cerberus (again, installed as system or user app, it shouldn't matter), or AdFree Android, it should update just fine. (And that is not in any way intended to be a comprehensive list.)
XBIRDIE98
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:
Hi, i have some kind of problem with my nexus 7 2013.. I already have lollipop 5.1.1 official on my tablet and have root and unlocked bootloader (root with king root, yes it works and is rooted.. And bootloader unlocked with boot unlocker.. I know you might think that this are not the best way of rooting or unloking the bootloader but it worked for me and im happy) and since yesterday the tablet keeps telling me to update via OTA the 5.1.1 update witch i already have..i press update to install it as normal, it reboot as normal too and when it shows me the parte where it suppose to be installing the update (you know, with the android with the chest open part) the only thing that says is "error" it doesn't install anything..i did this like 3 times now and every one of them says error.. The annoying part is that it keeps showing me the notification to update it..so any solutions? Thanks!
Sorry for bad english blah blah...
You can't take ota updates if you modify system files, you did that with root. Don't know why it's showing you 5.1.1 when you already have it.
Just flash the factory image with fastboot (probably no need to wipe, just flash boot.img and system.img and format cache).
That should fix the problem. It will also remove root. I'd recommend not using that king root **** but whatever. Probably better to just flash the su zip in twrp or use CF-Auto-Root.
When the next update comes remember you won't be able to take the ota. But that doesn't matter since google posts factory images and all you need to do is flash it with fastboot, then root again.
yosmokinman said:
YDon't know why it's showing you 5.1.1 when you already have it.
Click to expand...
Click to collapse
There's a new 5.1.1 = LMY48G
Original 5.1.1 is LMY47V
^Oh yeah, lol.
Still the rest of my post will get it installed for op.
I'm trying to install the 10e update for the SEA version of H815 (over 10d which I rooted using this method). I defrosted any apps I froze in TB, did a full unroot in super SU, restored my pre-rooted image and did the OTA. The OTA failed to install giving an error code of 1123004. Then when it rebooted into android it said updates were not available due to suspected rooting.
I never had Xposed installed, and the only other thing I can think of is that I modified build.prop to enable write access to the external SD card. I'm re-installing the rooted image so I can revert that ...... but can anybody think of any other reason why this update might be failing to install on my phone? (incase this build.prop modification isn't it that is)
EDIT : oops, sorry. not build.prop .... platform.xml
EDIT x 2 : well, that wasnt it .... the change had been overwritten already. I assume it was by the flashing of my pre-rooted image - makes sense. Back to the drawing board - (or digging up kdz files)
If you type 277634#*# in the dailer, you'll get into a hidden menu. Poke around and there will be something that states whether root has been detected. Can't tell you how to get there, I'm on Marshmallow now and that doesn't have that hidden menu, at least not with 277634#*#.
If root was detected, you can still update but you'll have to use LG bridge on a Windows PC. And reroot.
I'm having almost the same problem on VS986, I can still try to update after reboot. Rooting is setting a flag on the device somewhere.
I don't know why they're blocking the update after unrooting besides just being spiteful.
Pastinakel said:
If root was detected, you can still update but you'll have to use LG bridge on a Windows PC. And reroot.
Click to expand...
Click to collapse
Thanks, this is what I ended up by doing. Good thing I bought my laptop into work today....
hi, by any chance you still have a 10e SEA kdz? can't find anywhere, I downgraded to 10b, but I want the 10e/last Lollipop stock rom
Just get the kdz and flash with LG up I have rooted device with recovery all I did was flash it with LG up and no problem all fix......