Guys, i received push notification through system update to B125 and after downloading i tried to update but received error as attached.
i have tried using the dload + 3 buttons method without success so far.
Can anyone please advice how i can update ?
thanks a lot
harryhh said:
Guys, i received push notification through system update to B125 and after downloading i tried to update but received error as attached.
i have tried using the dload + 3 buttons method without success so far.
Can anyone please advice how i can update ?
thanks a lot
Click to expand...
Click to collapse
Try this:
1. Choose factory reset on the recovery.
2. Then retry update.
If that doesn't work:
1. Try to redownload the B125 ROM. It might be just that the file is corrupt.
If that still doesn't work:
1. Tell me; what ROM are you on right now? And did you just revert back from TWRP?
bokchoi2020 said:
Try this:
1. Choose factory reset on the recovery.
2. Then retry update.
If that doesn't work:
1. Try to redownload the B125 ROM. It might be just that the file is corrupt.
If that still doesn't work:
1. Tell me; what ROM are you on right now? And did you just revert back from TWRP?
Click to expand...
Click to collapse
Is that significant and why? I have the same issue and I have jut reverted from TWRP.
Thanks.
iwtfmcl said:
Is that significant and why? I have the same issue and I have jut reverted from TWRP.
Thanks.
Click to expand...
Click to collapse
I still need to know what ROM you installed previously. If you were on a Huawei stock rom, this situation is kinda weird.
If you were on a custom rom, you could try the following:
Warning: You will lose your data in this process. Make sure to backup anything that is valuable to you.
Go back to twrp.
Make sure you wipe the following:
System, Data, Custom storage, Dalvik Cache, cache
Then install stock recovery.
Then install B125.
bokchoi2020 said:
I still need to know what ROM you installed previously. If you were on a Huawei stock rom, this situation is kinda weird.
If you were on a custom rom, you could try the following:
Warning: You will lose your data in this process. Make sure to backup anything that is valuable to you.
Go back to twrp.
Make sure you wipe the following:
System, Data, Custom storage, Dalvik Cache, cache
Then install stock recovery.
Then install B125.
Click to expand...
Click to collapse
I am not OP but I had same issue. What happened in my case is weird. Originally I was on B118 International, then I went to B118CN to try and flash MIUI ROM. That didn't work and I force-flashed B118CN again. That's when I got push notification to update to B120. It was specifically saying that "P6-U06V100R001C17B118 will be updated to P6-U06V100R001C17B120.
After several failed attempts, update was no longer offered, and to my surprise my build number was showing P6-U06V100R001CNCN00B118. I am 100% sure that it was P6-U06V100R001C17B118 when I flashed it.
I have no idea what happened. I wanted to stay on chinese ROM and downloaded P6-U06V100R001C17B120, flashed and all is ok so far. Build number is showing P6-U06V100R001C17B120.
Related
Ok so I sideloaded 4.4 on to my tablet. I did it on stock no Rom and not rooted. I downloaded the .zip from android police.
http://www.androidpolice.com/2013/11/13/your-kitkat-is-ready-download-and-flash-android-4-4-ota-update-krt16o-for-2013-wi-fi-nexus-7/
Everything worked out great and looked well. But then I noticed, that may mic input wasn't working. Every time I try to use google search or mic input on the keyboard, The mic icon will just flash randomly as if it's picking up sound, but never pick up my voice. Now I wanted to know if there is a fix for this, or did I just **** up my sideload?
I've tried to use the Official Factory Image for both 4.3 and 4.4, but I keep getting the error:
E:footer is wrong
E:signature verification is wrong
Any help would be great, Thank You.
jpxzero said:
Ok so I sideloaded 4.4 on to my tablet. I did it on stock no Rom and not rooted. I downloaded the .zip from android police.
http://www.androidpolice.com/2013/11/13/your-kitkat-is-ready-download-and-flash-android-4-4-ota-update-krt16o-for-2013-wi-fi-nexus-7/
Everything worked out great and looked well. But then I noticed, that may mic input wasn't working. Every time I try to use google search or mic input on the keyboard, The mic icon will just flash randomly as if it's picking up sound, but never pick up my voice. Now I wanted to know if there is a fix for this, or did I just **** up my sideload?
I've tried to use the Official Factory Image for both 4.3 and 4.4, but I keep getting the error:
E:footer is wrong
E:signature verification is wrong
Any help would be great, Thank You.
Click to expand...
Click to collapse
Hey hey,
You shouldn't sideload the KRT16S factory image. You need to sideload the ota update (marked KRT16O->KRT16S OTA - flo/WiFi) at http://forum.xda-developers.com/showthread.php?t=2534698. That's assuming you are currently on KRT160 of course.
mbdw said:
Hey hey,
You shouldn't sideload the KRT16S factory image. You need to sideload the ota update (marked KRT16O->KRT16S OTA - flo/WiFi) at http://forum.xda-developers.com/showthread.php?t=2534698. That's assuming you are currently on KRT160 of course.
Click to expand...
Click to collapse
Thanks, I side loaded KRT16O. That's when my mic first stopped working. The OTA update to KRT16S came out 2 days later. So I updated to it OTA. So I am currently on KRT16S... Any ideas?
Thanks for the reply btw!
jpxzero said:
Thanks, I side loaded KRT16O. That's when my mic first stopped working. The OTA update to KRT16S came out 2 days later. So I updated to it OTA. So I am currently on KRT16S... Any ideas?
Thanks for the reply btw!
Click to expand...
Click to collapse
My first course of action would be a wipe in recovery of the data and cache. Have you already tried that route?
mbdw said:
My first course of action would be a wipe in recovery of the data and cache. Have you already tried that route?
Click to expand...
Click to collapse
Yeah so I've done a factory restore. I've wiped out my cache also. But nothingso far
jpxzero said:
Yeah so I've done a factory restore. I've wiped out my cache also. But nothingso far
Click to expand...
Click to collapse
Hmm, well next I'd make a nandroid then backup using titanium backup (just in case), and make sure you've got the 4.4 factory image (obviously not just the ota). Then I'd go to custom recovery, factory reset, wipe system, data, dalvik and cache, and then flash the stock image.
That's what I'd try at least... Maybe somebody else will have a better idea. You are on stock kernel, right?
mbdw said:
Hmm, well next I'd make a nandroid then backup using titanium backup (just in case), and make sure you've got the 4.4 factory image (obviously not just the ota). Then I'd go to custom recovery, factory reset, wipe system, data, dalvik and cache, and then flash the stock image.
That's what I'd try at least... Maybe somebody else will have a better idea. You are on stock kernel, right?
Click to expand...
Click to collapse
That is what I also did. Just downloaded the KRT16S factory image from Google developers site and flashed it.
I'm trying to update my E975 to v20A (kitkat) using software update app on the device. 1st try, I get notification that my phone is rooted and installation cannot continue, so I use Framaroot to unroot my phone, then I tried again to update my phone and I get, "installation error" msge and not knowing what cause the error.
what should I do?
frans3q said:
I'm trying to update my E975 to v20A (kitkat) using software update app on the device. 1st try, I get notification that my phone is rooted and installation cannot continue, so I use Framaroot to unroot my phone, then I tried again to update my phone and I get, "installation error" msge and not knowing what cause the error.
what should I do?
Click to expand...
Click to collapse
You should either flash back to original stock from your region or root your phone again, install CWM and install artmod - I suggest the latter.
http://forum.xda-developers.com/opt...om-e97520a-eu-4-4-2-artmodv3-0-te-10-t2811342
nchc said:
You should either flash back to original stock from your region or root your phone again, install CWM and install artmod - I suggest the latter.
http://forum.xda-developers.com/opt...om-e97520a-eu-4-4-2-artmodv3-0-te-10-t2811342
Click to expand...
Click to collapse
means you suggest I should use the artmod?
well, I used CM11 before, but I think 4.1.2 stockrom is better, and I use QSlide a lot. Then I flash using KDZ back to my original stock ROM. (that my current ROM, 4.1.2 stock rom)
then I read about official Kitkat release and I think the v20a official update will included all previous LG feature so I decided to try it.
But now I'm experiencing a lot of problem, the software update didnt works, so I download the .zip from this thread : http://forum.xda-developers.com/showthread.php?t=2784649 but it didnt work, and I'm having a bootloop.
I dont know, should I re-lock my bootloader before trying to update / flashing the official ROM?
I had try flashing CM11, and no problem.
Try again and if you didn't before do a very clean install i.e. factory reset,clear cache and dalvik cache, format system. Stock KitKat has a different partition setup compared to stock jb,I'd say that's what's causing errors.
nchc said:
Try again and if you didn't before do a very clean install i.e. factory reset,clear cache and dalvik cache, format system. Stock KitKat has a different partition setup compared to stock jb,I'd say that's what's causing errors.
Click to expand...
Click to collapse
thx. looks like I need a very clean install... software update method still wont work, but installing .zip from CWM work was working.
Hi, My system UI keeps failing on my HTC One M8, I have no status bar or home button, back button etc appear on my phone!
Version main: 4.16.401.10 and CID Num is: HTC__001
I have done a factory reset, cleared the delvic cache, data cache.
I get two error message when android boots up, HTC Dot View has stopped and another error message, System UI has stopped.
Can anyone help me? Thank you
You're in luck, shouldn't be to hard to fix. If you have the stock/working system ui apk you should be able to install it as an app. I had the same problem after using softkeyz. If you need the apk dm @ [email protected]
tylerleo said:
You're in luck, shouldn't be to hard to fix. If you have the stock/working system ui apk you should be able to install it as an app. I had the same problem after using softkeyz. If you need the apk dm @ [email protected]
Click to expand...
Click to collapse
Could you send me the apk file to my email address: [email protected]
Many thanks dude
Looks like you either deleted something or corrupted something in system. You can find the ota below if you don't still have it on your phone.
Flash that and you should be good. You need the correct stock recovery installed.
https://www.androidfilehost.com/?w=files&flid=24383
Stock Recovery
ashyx said:
Looks like you either deleted something or corrupted something in system. You can find the ota below if you don't still have it on your phone.
Flash that and you should be good. You need the correct stock recovery installed.
Click to expand...
Click to collapse
Hi, Would I have to put in a stock recovery first then install the OTA (link you provided me) Thanks.
Restart the phone, then once it boots before doing anything tap the app drawer and go to settings. Go straight to the apps, and navigate to all apps. click on the HTC Blinkfeed app, and clear the data. After that go to HTC Dotview and clear the data. Restart the phone again. This should fix your problem. I had this problem a few times after doing a restore of my nandroid.
suprtrukr425 said:
Restart the phone, then once it boots before doing anything tap the app drawer and go to settings. Go straight to the apps, and navigate to all apps. click on the HTC Blinkfeed app, and clear the data. After that go to HTC Dotview and clear the data. Restart the phone again. This should fix your problem. I had this problem a few times after doing a restore of my nandroid.
Click to expand...
Click to collapse
Hi, I have tried this however the clear data in dot view, blinkfeed are all greyed out. Can you suggest anything else please, this is so frustrating. Thank you
noorul89 said:
Hi, I have tried this however the clear data in dot view, blinkfeed are all greyed out. Can you suggest anything else please, this is so frustrating. Thank you
Click to expand...
Click to collapse
It will only be grayed out for a few seconds while it is calculating. Be patient and try again.
noorul89 said:
Hi, Would I have to put in a stock recovery first then install the OTA (link you provided me) Thanks.
Click to expand...
Click to collapse
As said you need the correct stock recovery. You can pull it from the firmware zip in the download or download it from the stock backups thread.
https://www.androidfilehost.com/?w=files&flid=24260
ashyx said:
As said you need the correct stock recovery. You can pull it from the firmware zip in the download or download it from the stock backups thread.
https://www.androidfilehost.com/?w=files&flid=24260
Click to expand...
Click to collapse
Hi, I have the stock recovery installed on my M8. I have the OTA downloaded, how do I install the OTA on a stock recovery?
Resolved!!
This issue was resolved by installing the stock recovery, going into data wipe and factory reset. Then restaring the phone. Phone boots up and is working as normal!! Woohoo i been spending most of the weekend trying to fix it and it turned out to be so simple. Thanks to everyone that helped me.
noorul89 said:
This issue was resolved by installing the stock recovery, going into data wipe and factory reset. Then restaring the phone. Phone boots up and is working as normal!! Woohoo i been spending most of the weekend trying to fix it and it turned out to be so simple. Thanks to everyone that helped me.
Click to expand...
Click to collapse
hey i am having the same problem. what recovery did you use? i only have the older 3......
alvahroee said:
hey i am having the same problem. what recovery did you use? i only have the older 3......
Click to expand...
Click to collapse
You will need to find your stock recovery.. Flash it from your custom recovery i.e twrp.
Boot into your stock recovery and go into wipe data/factory reset option.
That resolved the issue for me.
noorul89 said:
This issue was resolved by installing the stock recovery, going into data wipe and factory reset. Then restaring the phone. Phone boots up and is working as normal!! Woohoo i been spending most of the weekend trying to fix it and it turned out to be so simple. Thanks to everyone that helped me.
Click to expand...
Click to collapse
OMG Thank you so much. I was wiping all kinds of cache , restoring all kinds of backups and nothing was helping the matter. Thanks for making it clear that I have to flash back the stock recovery and data wipe and factory reset from there
Hello.
I tried to update my OP3 to 4.0.3 but after downloading the update phone restarted and went into TWRP recovery mode and i couldn't go pass i that point. Went home and I tried to flush stock recovery with Tool All In One but now I cant get into stock or TWRP recovery. I contacted OP technical support but next remote session available is for next Friday!!! I'm downloading their files at the moment i assume stock ROM (file in 1GB size) and drivers and certifications .
Please somebody help me!!!
u can't flash an OTA with Trwp, just download the full zip and dirty flash, wipe cache and dalvik, not data, some say u can do system but I don't, don't try to update via OTA if u have twrp and don't try to re lock bootloader u will mess up and brick. Since u have twrp I would recommend flashing Experience ROM of FreedomOS, they are easier to work with, Experience rom seems to be faster with updates, feel free PM me if u need any help
ALWAYS DO A NANDROID BACK UP 1ST BEFORE FLASHING!!!!!!
Bradl79 said:
u can't flash an OTA with Trwp, just download the full zip and dirty flash, wipe cache and dalvik, not data, some say u can do system but I don't, don't try to update via OTA if u have twrp and don't try to re lock bootloader u will mess up and brick. Since u have twrp I would recommend flashing Experience ROM of FreedomOS, they are easier to work with, Experience rom seems to be faster with updates, feel free PM me if u need any help
ALWAYS DO A NANDROID BACK UP 1ST BEFORE FLASHING!!!!!!
Click to expand...
Click to collapse
Thx for reply, I managed to flash TWRP and the system is up and running. So to get system updates I have go back to Stock Recovery is that correct? I have made system back up just in case, but lets say anything go wrong again and I wont be able to restore the system with TWRP what then? Do you have a link to full rom? I found only for 3T.
wesoly75 said:
Thx for reply, I managed to flash TWRP and the system is up and running. So to get system updates I have go back to Stock Recovery is that correct? I have made system back up just in case, but lets say anything go wrong again and I wont be able to restore the system with TWRP what then? Do you have a link to full rom? I found only for 3T.
Click to expand...
Click to collapse
with a nandroid backup through twrp u back up data, system, cache and boot, so if anything goes wrong u can just restore back to where u left off, i don't use stock OTA to update, but i believe u have to unroot and flash stock recovery then u can update.
https://forum.xda-developers.com/oneplus-3/how-to/4-0-2-coming-tonight-t3539895
I have rooted firetv 1 with latest rBox pre-rooted ROM. I have noticed if I put the box in sleep mod for a while, it will change to TWRP recovery screen when wake it up. I have to reboot it every time in order to back to normal. Anyone has the same problem?
Thanks.
Seattleweather said:
I have rooted firetv 1 with latest rBox pre-rooted ROM. I have noticed if I put the box in sleep mod for a while, it will change to TWRP recovery screen when wake it up. I have to reboot it every time in order to back to normal. Anyone has the same problem?
Thanks.
Click to expand...
Click to collapse
Most folks that have had this problem is because they did not block updates properly. And you have an update in the hopper. And TWRP being your last line of defense is blocking the installation of that update since it is not a PreRooted ROM. So each time your device is idle it tries to install the update. And TWRP stops it at reboot.
Luckily there are solutions.
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
And at the very least do Method 1. But both Method 1 & Method 5 are what is recommended to stop this from happening in the future.
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Y314K said:
Most folks that have had this problem is because they did not block updates properly. And you have an update in the hopper. And TWRP being your last line of defense is blocking the installation of that update since it is not a PreRooted ROM. So each time your device is idle it tries to install the update. And TWRP stops it at reboot.
Luckily there are solutions.
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
And at the very least do Method 1. But both Method 1 & Method 5 are what is recommended to stop this from happening in the future.
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Click to expand...
Click to collapse
Thanks you very much. I believe I did one BEFORE flash to new pre-root ROM. I tried to do it again this morning, found the superuser is not there anymore after flash to pre-root ROM from rbox. I am confused since I rooted firmware and unlocked bootlocker. I does not me to install superuser anymore. Please help me:crying::crying::crying:
Seattleweather said:
Thanks you very much. I believe I did one BEFORE flash to new pre-root ROM. I tried to do it again this morning, found the superuser is not there anymore after flash to pre-root ROM from rbox. I am confused since I rooted firmware and unlocked bootlocker. I does not me to install superuser anymore. Please help me:crying::crying::crying:
Click to expand...
Click to collapse
If you are able to still go into TWRP. I would try to flash the latest PreRooted ROM using a USB Stick. Also make sure you include a MD5 for safety. DO NOT WIPE anything but Dalvik Cache & Cache. See if that restores your PreRooted FW back to normal. This is just a guess since it has never happened to me before.
Maybe someone with this problem the fixed things can chime in. Others that this has had happened to did not have access to TWRP.
Y314K said:
If you are able to still go into TWRP. I would try to flash the latest PreRooted ROM using a USB Stick. Also make sure you include a MD5 for safety. DO NOT WIPE anything but Dalvik Cache & Cache. See if that restores your PreRooted FW back to normal. This is just a guess since it has never happened to me before.
Maybe someone with this problem the fixed things can chime in. Others that this has had happened to did not have access to TWRP.
Click to expand...
Click to collapse
FIXED!!!
I tried to install superuser apk , but failed. Since I still have access to TWRP, I installed with flashable superuser. Then I cleared OTA and blocked the updates again with your suggestion. I did Method 1 before, but forgot to do it again after update. Thank you very much!!!
Seattleweather said:
FIXED!!!
I tried to install superuser apk , but failed. Since I still have access to TWRP, I installed with flashable superuser. Then I cleared OTA and blocked the updates again with your suggestion. I did Method 1 before, but forgot to do it again after update. Thank you very much!!!
Click to expand...
Click to collapse
np, glad it is back to normal.
Method 1 helps when you flash a new PreRooted ROM. And Method 5 helps to make sure your FW version is never low enough to think an update would apply to your device. Method 5 needs to be redone when ever you flash a ROM. And Method 1 must be redone when ever you factory reset thru TWRP or clean more then the Dalvik Cache & Cache thru TWRP. NEVER do a factory reset from FireOS 5. Only use TWRP for that.
Forgot to add. NEVER INCLUDE SYSTEM IN ANY OF YOUR WIPES. Flashing a PreRooted ROM will take care of System. So leave it alone. Most bricks happen because folks wipe SYSTEM & they do not Flash a PreRooted ROM before doing a reboot.