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.
Related
I have a samsung galaxy s3 international model and
rooted it using Chainfire's CF-Root 6.4 - SuperSU+CWM5.5+CWMManager
Now I did an OTA update of 7mb approx and lost root and tryed to re-flash CF-Root
But im not able to go into download mode in recovery mode?
shotpix.com/images/23588341243990019557.jpg
moreover how do run adb reboot download command?
And on every normal restart the phone shows a message, "Android is upgrading...start applications"
shotpix.com/images/08905428090536950785.jpg
And i tryed to add more OTA updates but the installation fails at 25%, phone reboots and asks me to update via KIES?
Can anyone help me out with this, this is my first android and dont wanna mess up
And do i need to remove supersu and cwm to reroot?
OTA fails if rooted = YES.
You say
But im not able to go into download mode in recovery mode?
Do you mean you cannot boot to download mode >> Or you are looking for download mode in recovery .
Boot into recovery wipe data factory reset flash stock rom via Odin .
jje
My bad, i was rebooting while holding Volume up, and it was volume down
Now phone is booting into download mode, and i have reflashed it successfully.
My first OTA was installed 100%,and that is how i lost root, however second update failed?
And im still getting the "Android is upgrading...start applications"
shotpix.com/images/08905428090536950785.jpg (SCREENSHOT)
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
William31 said:
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
Click to expand...
Click to collapse
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
mattnmag said:
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
Click to expand...
Click to collapse
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
William31 said:
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
Click to expand...
Click to collapse
Cool. Glad you got it fixed.
As you know, you can root with GhettoRoot from this thread: http://forum.xda-developers.com/showthread.php?p=57238246
Then can install Safestrap from this thread: http://forum.xda-developers.com/showthread.php?p=51616723
I've never used Safestrap because I can use regular custom recoveries like CWM and TWRP. I'm still on a 4.1.2 unlocked bootloader and currently running TrentsKKRom, Build #2...which is 4.4.2 based with stock kernel, so I think it would work with Safestrap.
I'd recommend reading through the Safestrap thread thoroughly and asking questions there to make sure you get everything installed correctly. I've read that with Safestrap, you need to make a backup of your Stock ROM first and save it somewhere safe, like to your computer and on your external sd card...so you can easily restore it if needed. (I'd also make a backup of the ESF in Safestrap if it lets you, then save it somewhere safe).
After you are rooted with Safestrap, you'll have to flash custom ROM's over the stock slot in Safestrap, as the other slots apparently don't work. Again, you're limited to only using Touchwiz ROM's with the stock kernel because of the bootloader still being locked.
Check out TrentsKKRom and Alliance build 30 . (I personally like Trent's build 2 best with the S5 clean theme). I've also found Trent's ROM to be really smooth without UI lagging, the Bluetooth works good with no stuttering, and it pairs well with my Sony Smartwatch 3. (Edit: If you do try Trent's ROM, you may need to install a couple apps.... Chainfire's Supersu app to control your root permissions (at least I needed to), and the FolderMount app to fix a KitKat internal storage mounting issue).
Have fun!!
Hello everyone, I am trying to go back to stock rom/firmware on my T-Mobile Galaxy S5 (G900T)
I had a recovery, but I misplaced the SD Card that had it, so now I am trying to use Odin to do this.
I downloaded Odin and the firmware from this link: http://forum.xda-developers.com/tmob...mware-t3042400
but no matter, which Odin I use, or which Firmware I try, it keeps failing. What can I do?
Also, now when I try to boot into recovery it says ''Firmware upgrade encountered a problem, please select recovery mode in Kies and try again''
EDIT:
After many attempts of flashing, I was successfull getting Android 5.0 back on to my phone. It turns on and works perfectly, but now I have run into a different problem.
T-Mobile keeps pushing to update to 5.1 / 5.1.1. but everytime I try, it downloads, boots to recovery, starts installing and fails. What can I do about this?
Note 3 Running Android 5.01 from Sprint.
I've had both OC5 and OH! (I think is the new one from August)
Both Firmware I try to install CWM or TW via ODIN and its unsuccessful. When I try to get into recovery it reverts to some errors while in Downloading.
Most recent attempt I re-installed stock firmware OC5. Ran OTA upgrade to newest firmware. Used CF to root and again ODIN to install CWM. Still same thing.
What am I missing here?
FYI if I use ROM Manager to install CWM it says its successful but can't book into recovery. It will just loop the bootloader so I have to use Odin to reinstall the firmware.
What ver. Of Oden you using?
Originally I used 3.07 but aftrer coming across this issue I've wiped and reinstalled the firmware and tried again using 1.85. Both versions had no luck.
Try Oden 3.10
Missing root. Try to reroot via odin, and try twrp via odin. If no go...put stock via odin and select nand erase. You may get stuxk on sprint logo when boots, go into recovery and do wipe. The reboot stock will load. Then root via odin, and install twrp or cwm via odin. This fixes all my problems...even when i thought phone was dying
Hello,
I come for you, because I am trying to install android 4.4 on my phone, because android 4.3 isn't compatible with pokemongo.
I have a galaxy s3 GT-I9300 from a few years, I've never rooted it and it runs on android 4.3.
I've been looking for guides that say that I need to install CWM recovery to then be able to install CyanogenMod.
So I've downloaded Odin, and CWM recovery, added the CWM recovery .tar in the AP box of Odin, put my phone on download mod, plugged it, and run Odin.
It appears that it works succesfully, but when I reboot my phone in recovery mode, I still have Android Recovery System <e3>, and I can't install zip from sdcards (if I understood correctly, <e3> doesn't support zip, whereas <e2> does, and CWM is supposed to put it to <e2>), so I can't install CyanogenMod.
Here is a screenshot of my Odin after running it: (I can't post the link since I'm a new user, so it's on imgur)
/87oPm2l
I can't think of any more information to provide for now.
Thanks for your help.
chocolote4444 said:
It could be permission issues. But try using a different cable.
Also, the recovery you are flashing has to support the model of the phone, otherwise, Odin will refuse to install it.
Click to expand...
Click to collapse
Thanks for the answer, I was not in root mode.
I fixed it and it now works, I have been able to install CyanogenMod from the zip in recovery.
Now I tried restarting my phone, and it's stuck in "Android is starting".
I have a little blue alien popping on my screen, then the screen turns off, then the screen turns on and says things like "starting applications, preparing settings, optimizing applications". But it seems to be doing it on repeat and it's been an hour. Is it normal that it takes so long? I haven't seen it mentionned anywhere from what I checked.