I'm on v11.0.10.0.QFQEUXM, can't install the next update, every time I try it just reboots and tells me the update failed. Anyone have a solution?
bootloader is locked and I'm not using any custom rom if that matters.
In case anyone has a similar issue I fixed it by clearing data for google mobile services and google play. I guess a corrupt update file got stored somewhere.
The update can be installed via recovery, also if you are in stock. Reboot into recovery and select install update from sd. You can download the stock recovery latest firmware from many sites on Internet
Related
Hi
I successfully completed unlocking, installing CWM, rooting and Ken's 4.5.91 GB along with the updated radio. Only issue I am having so far is when I go to the market to update or download any apps it starts the download and then tells me download was unsuccessful and stops. Does anyone have any idea why this is happening or what I can do to possibly fix it? I tried rebooting phone and toggling the unknown sources check box but still having issues. Any help is appreciated.
Thanks
I had the same problem.
The easiest fix to it is boot in to Android Recovery and do a wipe of data/factory
It worked!!
Thanks it worked
I'm trying to update my Galaxy Tab 10.1 to the latest firmware (PDA:KME) that includes TouchWiz (I got mine recently right after they halted distributing that firmware and it just became available again). I've tried OTA and through Kies, neither of which is working.
My device was rooted. I'm running the stock ROM with a custom kernel, and ClockworkMod Recovery.
When I try to update via Kies, the firmware is downloaded at which point the device seems to reboot into ODIN3 Download Mode. There is a green Android guy and it says "Downloading . . . Do not turn off target". In the Odin log it says "Connected! Press the Start of Odin3. I press Start in ODIN but nothing happens nor do I expect anything to happen since there is nothing selected in ODIN to upload to the phone. So I have to hold the power button and reboot without any changes.
If I try to update via OTA, I can initiate a Download. I then can click Install. After a few seconds I click OK to reboot the device. The update goes to 13% and then stops. The device reboots and I'm back with the old firmware still. I eventually get a message that the firmware failed to be updated.
What should I do?
Part of Kies update process is to boot the tablet into download mode and Kies, not ODIN, will push down the firmware bits automatically. You are not supposed to launch ODIN at all. Keep the Kies running and it will finish all the process for you.
You only use ODIN if you want to flash a firmware you already downloaded manually.
Kies and OTA updates will probably be similar. So, if your phone is rooted and can't update OTA, you will likely get the same issue via Kies.
Hmmm. Not sure what to do then. I'm not launching ODIN myself on the Tab. When the Tab reboots after downloading the update via Kies, it goes into ODIN download mode by itself. Using OTA, it reboots correctly but just doesn't finish the update process.
I tried reflashing the stock recovery but that didn't change the failed result.
lmsilver said:
Hmmm. Not sure what to do then. I'm not launching ODIN myself on the Tab. When the Tab reboots after downloading the update via Kies, it goes into ODIN download mode by itself.
Click to expand...
Click to collapse
That is correct. And Kies should supposedly begin sending down the firmware after it sees the tab is in download mode, not before. Here is what Kies does in order:
1. Detect your tab's current model # and firmware version and check to see if there is an update.
2. Download the update from internet to the PC.
3. Reboot the tab into download mode.
4. Detect your tab is in download mode and start to send the firmware down to the tab.
5. Upon receive all the firmware bits, tab will start the update process by itself.
It is called download mode, not ODIN download mode. ODIN is an unofficial tool to flash firmware (there are other tools that can do exactly what ODIN does), not related to download mode although it requires download mode to push down the firmware.
There are instructions for finishing up the OTA update when you have CWM installed. You need to boot the tab into recovery mode and clear all the cache data.
Thanks for trying to help me through this. Still not getting it to work.
I didn't see any specific instructions for updating via OTA with CWM installed. What i did was boot into recovery, wipe the cache, wipe the dalvik cache, reboot and download the update again. Clicked install, OK to reboot. It went through 13% of the install process and then stopped, rebooted, and indicated the update failed.
Perhaps I should just run a custom ROM instead. That's what I've done on my original Droid but I haven't had a chance to look through the ROMs for the Tab to find a suitable one.
Quite frustrating.
Well, if you ever installed custom bits (kernels and CWM), you should not expect OTA update be successful at all. You have to stick with custom ROMs.
Personally, I see no value to install CWM on the table if you're not flashing custom ROMs since it has been proven not working well with OTA updates.
I'm running a custom kernel, just not a ROM yet. But I think I'll just try to find one I like and do that instead.
Okay, so this is what happened:
1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3
2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.
3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.
4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.
5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.
6) I then tried to install CM10, to see if that would work. I downloaded the TWRP recovery and also the CM10 ROM .zip file, along with the google apps zip. I flashed the TWRP recovery using fastboot. That worked fine. I was also able to install the CM10 Rom, or at least it reported back "Successful". Same with the google apps zip. But then when I reboot, it only gets to the T-mobile Splash screen and stays there forever.
Please help! I tried to install the Stock Rom using the TWRP recovery, but again, it reports "Installation aborted." So, what am I doing wrong or what can I do to fix this?
Thanks.
[UPDATE] -
Okay, so I actually tried installing CM10 again using the TWRP recovery since it said that it was "Successful." And sure enough, it was successful, it seems. Once I installed it, rebooted the tablet and waited on the T-mobile Springboard screen for about 10 minutes, it launched CyanogenMod. I then set up the tablet with CM10. I had received the unlock code from T-mobile and so my tablet was sim unlocked. I put a AT&T sim card and sure enough it got signal and I was able to surf the web and make phone calls. I downloaded the speed test app from the Play Store and noticed that I was getting about 1.5Mbps download and about 600kbps upload. Not bad. The problem I noticed is that I can't receive calls. I can call out, but when someone tries to call me, the tablet doesn't acknowledge an incoming call. The caller just goes straight to voicemail. I do get a voicemail alert.
So, I don't know whether that is an issue with the CM10 build or a problem in my network / APN settings.
I would like to get the rooted T-mobile International stock ROM on there so that I can try it with that. I'll keep you all posted.
Thanks!
9 times out of 10, I get installation aborted errors because of a botched download. Try downloading the file again, and if available, verify that the MD5 sum of your downloaded file matches the one provided by the developer.
And if I'm not mistaken, TWRP recovery and CWM recovery aren't capable of flashing the T-Mobile stock recovery. If you have TWRP working properly, I would continue trying to flash one of the unlocked ROMs available. I highly recommend HWMOD's ICS (available here)
Best bet would be to fastboot flash the recovery img from the hauwei site update.zip. Then do the standard pop the stock hauwei update.zip on the sd card and do the normal upgrade method. That should full wipe the phone and then you can start tinkering with it again. Also huawei posted the offical root on their site.
nightanole said:
Best bet would be to fastboot flash the recovery img from the hauwei site update.zip. Then do the standard pop the stock hauwei update.zip on the sd card and do the normal upgrade method. That should full wipe the phone and then you can start tinkering with it again. Also huawei posted the offical root on their site.
Click to expand...
Click to collapse
I don't want to mix up the T-mobile images with the Huawei images. Even though I've screwed things up already. But, if you read my previous post, I've got CM10 working, but no incoming calls.
I have been receiving a system update notification for about 2 weeks now and every time I try to install the update it reboots, goes to apply the update and then it reboots again like nothing happened. Anyone else have this problem or know a way to fix it? I have tried doing the update manually through adb sideload but it keeps running into an error there as well and aborts the install.
If the directions here http://forum.xda-developers.com/showthread.php?t=3030327 don't work for applying the update . I'd flash the TOT.
If you have twrp installed make sure to reinstall the stock recovery. The update zip cannot correctly flash its updater script. The stock recovery can due so, so I would install it.
I unlocked the bootloader and rooted the phone, and flashed with resurrected remixed 8.1
Everything seemed good, but trying to install gapps would fail. Everytime I try to flash something it fails, gapps worked once but did not install play services.
I've never had some many problems, the phone does not have a sdcard. ROM manager is installed, and connected to wifi, but it cannot update, does not say why. I tried to get TWRP to work, now it says the phone is not rooted.
I flash SuperSU-v2.82-201705271822, it says success but there is no super user. SU when I run it says it is occupied.
Tried to wip cache etc, and flash stock or lineage, error 7. Tried to remove assert in the update script, than gives a error about footer.
I know I must be missing something. RR Oreo 8.1, no web browser, going to download and move via usb and install. Any suggestions are welcome.