So I flashed the official factory image for KRT160 the other day and I'm rooted with cwm touch, I tried to flash the ota for KRT16SS today and got an error "systemui.apk has enexpected errors" or something like that. Anyone know what to do?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Related
The Jellybean update has finally arrived for the NS4G. However a couple ppl myself included have been receiving an error. With the OTA and the flashable .zip i get a status 7 error. Anyone have any clues as to why? Most people are coming from stock and still getting this error with stock recovery or CWM.
From the other thread, download the binaries and use the fastboot method detailed in this post:
http://forum.xda-developers.com/showthread.php?p=31419426
Sent from my Nexus S 4G using xda app-developers app
I have unlocked my wife's One S and got root access, still using the stock ROM, but flashed cwm recovery. An update for the OS is available, but it fails when I try and install from within the OS. I tried to manually install it from the SD card using cwm, but it fails the signature test part. I noticed I can disable the signature check, but wasn't sure it was a good idea.
Can any smart people give me some advice?
Thanks
Sent from my Galaxy Nexus using Tapatalk 2
TrentSe7en said:
I have unlocked my wife's One S and got root access, still using the stock ROM, but flashed cwm recovery. An update for the OS is available, but it fails when I try and install from within the OS. I tried to manually install it from the SD card using cwm, but it fails the signature test part. I noticed I can disable the signature check, but wasn't sure it was a good idea.
Can any smart people give me some advice?
Thanks
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You need to unroot your device and reinstall the stock recovery.
Sent from my Nexus 7 using xda app-developers app
I recently accepted the MF1 OTA update without unrooting. I'm a noob so really didn't think about it until it was too late. The update installed via TWRP and I lost root, custom recovery and bootloader is locked yet again. Just wondering if I could flash back to MB1 using Odin in download mode or are there any precautionary steps I need to take before trying to flash back? Or will it even work?
Sent from my SCH-I535 using xda app-developers app
Never heard of MF1 when did you get that update.
You can always try to odin back. Hopefully whatever mf1 is didn't break the root process and it causes a brick.
Sent from my SCH-I535 using xda premium
Justinakadoc1982 said:
I recently accepted the MF1 OTA update without unrooting. I'm a noob so really didn't think about it until it was too late. The update installed via TWRP and I lost root, custom recovery and bootloader is locked yet again. Just wondering if I could flash back to MB1 using Odin in download mode or are there any precautionary steps I need to take before trying to flash back? Or will it even work?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Maybe i was thinking use EZrecovery to restore stock recovery. and use OTA rootkeeper from VooDoo. then just use EZrecovery to flash CWM again. the only thing i am worried about is the bootloader locking again.
I received the update early this morning. I had MD3 stock rooted but flashed back to MB1. Kept checking for software updates again for a couple of days and it kept saying none available until this morning. So I accepted it without thinking. . Here is a screenshot of the update. ..
Sent from my SCH-I535 using xda app-developers app
So I guess what I'm really trying to say is it safe to flash back to MB1 via odin with the bootloader being locked and having no root?
Sent from my SCH-I535 using xda app-developers app
I might would wait until you give one of the developers or senior members chance to look at it. You should be fine but you never know when they have put in a new patch.
Sent from my SCH-I535 using xda premium
Ok sounds like a plan. Thanks so much for the help!! much appreciated!!
Sent from my SCH-I535 using xda app-developers app
Coming from rooted MD1
I temporarily unrooted the phone using voodoo ota rootkeeper
Restored stock recovery using ezrecovery for gs3
Proceeded to update via ota.. update begins, but fails (android down with triangle and exclamation point)
suggestions?
dumbstrong said:
Coming from rooted MD1
I temporarily unrooted the phone using voodoo ota rootkeeper
Restored stock recovery using ezrecovery for gs3
Proceeded to update via ota.. update begins, but fails (android down with triangle and exclamation point)
suggestions?
Click to expand...
Click to collapse
It should print off an error log in /cache (I think) which tells you why it failed. I believe that it auto fails if you have a modified SystemUI, have Google Wallet installed, removed system apps, things of that nature.
Sent from my SCH-I535 using Tapatalk 4 Beta
SlimSnoopOS said:
It should print off an error log in /cache (I think) which tells you why it failed. I believe that it auto fails if you have a modified SystemUI, have Google Wallet installed, removed system apps, things of that nature.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
That's probably it then, since I have removed a few of the Verizon apps using titanium backup. Thank you much
dumbstrong said:
That's probably it then, since I have removed a few of the Verizon apps using titanium backup. Thank you much
Click to expand...
Click to collapse
No problem! If you do want to take the OTA, you can Odin flash VRBMB1 and have it update from there. Alternatively, Scrosler posted the rooted VRBMF1 rom in the dev section.
Sent from my SCH-I535 using Tapatalk 4 Beta
My phone is completely hosed. It froze last night so I rebooted it. Once I did it gave me a message about UID being inconsistant and to wipe my data partition. I figured I'd just flash back to stock. Turns out I can't because you can't downgrade from the OTA. So I reflashed the stock recovery and tried to flash the OTA again. It errored out because of some APK. Now I can't boot to normal because the flash failed and recovery is no help. i just want to return to stock
Look into house of moto to FXZ to stock then take the update. Make sure you're not rooted.
Sent from my XT1080 using xda app-developers app
bc760 said:
Look into house of moto to FXZ to stock then take the update. Make sure you're not rooted.
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
I can't go back to stock. It gives me an error saying it's impossible to downgrade.
You can't do a wipe in recovery? You can get into the recovery right?
Sent from my XT1080 using xda app-developers app
I get an error when I try to fastboot flash system system.img. It doesn't appear to write the system.img to the phone. It downloads but doesn't seem to write and I get an error that says sp space is not enough.
I have a dev edition unlocked and was trying to return to stock anticipating the update.
Which fastboot are you using ?
Sent from my XT1058 using XDA Premium 4 mobile app
planktoid said:
Which fastboot are you using ?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
moto fastboot. I am using the same computer/sdk/fastboot that I was using just a couple of days ago when I wasn't getting the error. FWIW it doesn't seem to actually affect anything. I just flashed twrp, formatted system, booted back to the bootloader and flashed the system and got the same error but the phone boots fine so it must be writing the system image. I am still perplexed as to what the error is. I had never seen it before until last night.
If you're not rooted and you are stock...how do you go about doing this?
Sent from my XT1080 using Tapatalk
justpastfinish said:
If you're not rooted and you are stock...how do you go about doing this?
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Exact same way as all versions of the phone..... Follow the guide I posted in Dev Section, it gives detailed step by step.