Hi there, I skipped the Nexus 4 myself but a less techie friend of a friend is having trouble updating his to KRT16S from JWR66Y.
Photo here:
https://www.dropbox.com/s/jvp8v0u3kwfdr46/Photo0001.jpg
He says he bought it straight from Google, never unlocked the bootloader, never rooted. Yet during the update install he gets the message:
"/system/app/PlusOne.apk" has unexpected contents.
There is no way that system app should have been modifiable if he was never rooted. But for some reason it does not match what the update zip expects.
Any idea why this might be happening? And is there any way he can possibly upgrade with a locked bootloader, without wiping?
Related
hi,all I'm new here
i hive samsung galaxy S4 i337, my phone is factory unlock. I'm on ATT carr, two days ago i was at 4.2.2 and rooted, and today my phone it updating itself.
when was on 4.2.2 i was getting the same thing at boot ""the custom screen with the lock that was unlocked showed up"" but was working ok and rooted.
after the update, i still get the same thing at boot. Now i can't root my phone on 4.3 because of the security issue to keep blocking. anything i do.
Please can someone explain how can I bypasses and rerooted phone, I tried all the method that is available to me but unable to rooted, security block.
I appreciate the help.
akihiko_51 said:
hi,all I'm new here i hive samsung galaxy S4 i337, my phone is factory unlock. I'm on ATT carr, two days ago i was at 4.2.2 and rooted, and today my phone it updating itself. when was on 4.2.2 i was getting the same thing at boot ""the custom screen with the lock that was unlocked showed up"" but was working ok and rooted. after the update, i still get the same thing at boot. Now i can't root my phone on 4.3 because of the security issue to keep blocking. anything i do. Please can someone explain how can I bypasses and rerooted phone, I tried all the method that is available to me but unable to rooted, security block. I appreciate the help.
Click to expand...
Click to collapse
Which baseband are you on now? MF3? MJ6? Before which baseband were you on MDL? or MF3? What root method did you use?
It sounds like you rooted your phone, but did not take measures to prevent over the air (OTA) updating.
That OTA updating will destroy root, and lately also locks your bootloader in a manner that is even more restrictive.
It does not sound like you used any custom rom, and did not use Safe Strap either, but you need to provide more info for folks to work with.
akihiko_51 said:
hi,all I'm new here
i hive samsung galaxy S4 i337, my phone is factory unlock. I'm on ATT carr, two days ago i was at 4.2.2 and rooted, and today my phone it updating itself.
when was on 4.2.2 i was getting the same thing at boot ""the custom screen with the lock that was unlocked showed up"" but was working ok and rooted.
after the update, i still get the same thing at boot. Now i can't root my phone on 4.3 because of the security issue to keep blocking. anything i do.
Please can someone explain how can I bypasses and rerooted phone, I tried all the method that is available to me but unable to rooted, security block.
I appreciate the help.
Click to expand...
Click to collapse
You need to read all threads about 4.3, MJ6, and MJ9 in the "General" and " Q & A" sections of the forum to learn about what is happening with your phone.
Hello all!
I just got the push for the 4.4 upgrade on my phone but I wanted clear a few things up before I commit. I'm currently on a rooted 4.3 with a modded radio for LTE. Is it safe to just run the OTA update from my phone? Or is there another proper way to prevent bricking? How should I go about this?
Thanks guys!
There are a lot of variables such as programs and versions installed, but I tried the OTA under similar conditions as you (In my case I was rooted, hybrid 27/84 radio, unlocked bootloader, TWRP, Koush's superuser, and otherwise stock 4.3) and it just didn't work. I even reverted back to the old radio before I tried it, but it might be the modified build prop or LTE activation that caused the problem. The OTA did not brick my phone or cause any other problems, it just didn't change anything on my 4.3 install. I could see while the update was running that it failed right after examining my existing install, so it didn't like something with my existing system config. I then did the following from the advice on this forum and my upgrade to 4.4 went flawlessly (Post #13):
http://forum.xda-developers.com/showthread.php?t=2542998&page=2
I just flashed the entire image of the os on top and didn't lose data. On twtp, LTE back, unlock boot loader from 4.3.
Sent from my Nexus 4, while driving in my Evo9.
I have a recently rooted N10 on Android 4.4 build KRT16S. I have had the system update to 4.4.2 in my notifications for weeks now. What I wanted to know has anyone installed this update without any problems? and am I likely to lose root? Bit clueless as to how these updates work but saying that I did manage unlock the boot loader and flash my tablet without any issues. Also if I shouldn't install the update how do remove this update. Thanks in advance folks, Phil.
The update may or may not work, it depends on how much you've touched the system files. If you've just rooted it, the update should work. If not, you can flash the factory image (except for the data partition).
You'll probably lose root, but on a unlocked bootloader, that's nothing to worry about, as you can trivially re-root it.
Sent from my Nexus 5 using Tapatalk
Hi guys,
I'm having an issue upgrading my S5 to lollipop. After I download the update, I hit install now and then the phone reboots.. then it immediately boots back up and gives me an error saying there was an error installing the update. I was previously rooted and I unrooted with SuperSu.
Is there an easy way around this or should I just upgrade through odin or something? If this is the case can someone quickly link me to a tutorial to do this? I'm a little rusty.
Thanks,
Ota
I had same issue I used Verizons Firmware repair then I did the update thru Verizons Firmware updater on my pc then work perfect, I kept getting update fail with the dead Android then I used this method and worked, I was rooted so I unrooted first after Uninstalling busybox.
Hey guys I'm on 4.4.2 and I used towel root to root and I did the process to flash a rom. Well when I was rooted I unrooted on Supersu on the stock rom and I updated. Today I tried to update to Verizon's OTA to fix bluetooth and I can download it OTA and install it. It boots into recovery boot and then it loads. It shows the Android guy laying down and the Error wording. When the phone boots back up it says Sorry, there was an error updating your galaxy s5 Verizon. It's been doing this all day and I really want to update to Lolipop.
Same Issue, any solutions?
I have the exact same problem, and under similar conditions. Towel Root worked for a while, but an updated unrooted my phone, now TR doesn't work anymore. So, I'm back to stock, with this Verizon bluetooth update failing everyday for what seems like an eternity.