Can't Install Custom Recovery - STuck in Download - Sprint Samsung Galaxy Note 3

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

Related

OLD CWMrecovery.tar

This is the .tar file I used for CWM. Did a Factory data reset then flashed the package via ODIN (PDA). I had to reactivate my phone to get access to App Market to download Rom Manager. I Flashed ClockworkMod Recovery via Rom Manager and used the Reboot into Recovery to install the DL30.zip.
http://www.multiupload.com/C0HFVLSI22
I followed the steps outlined in several other threads and got nothing but errors. This is the only way that worked correctly.
I did not install the new CWM until AFTER I flashed the DL30.zip!
Loving Froyo and hope everyone else gets it running soon!

[Q] Cannot Update Rooted Device to Latest Firmware

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.

Kernel Panic!

I updated from MJ4 to NAB, and then to NABD, and flashed TWRP 4.4x compatible recovery, using the directions and links from the leak thread.
When I flashed the Engineering Bootloader tar in Odin, I used "bootloader" button, and it completed and is now stuck in a bootloop.
I cannot boot into Download Mode or Recovery, they both bootloop. Did I just brick my phone?
I have done the following procedure, so far, to attempt to recover my phone to operational condition.
• I just removed my SD-card and it booted into TWRP recovery. WHEW.
• I tried to update the recovery to "philz_touch_6.12.9-hltespr" which was supposed to be 4.4x compatible, and it now has a Kernel Panic message, and engaged "Upload Mode", how should I proceed to get back to normal?
○ I've tried to flash back to stock MJ4 tar using Odin, while its in the Kernel Panic upload mode, and it fails.​
○ Now trying to flash into stock NAB tar using Odin + Kernel Panic upload mode, and it fails. I'm out of options. Someone please help me.​
Install this one
http://kitkatkiller.eu/Files/SPRINT GALAXY NOTE 3/TW ANDROID 4.4.2/Recovery/hltespr-recovery.img.tar

mounted system and wiped in twrp, then flashed rom

so i thought i was doing something right by wiping the system partion in twrp before flashing LiteRom, so now the android folder is missing and the phone wont boot past samsung logo. is there any way i can just cope over the stock files/folders for the s3?
Download the latest stock ROM from sammobile.com and flash with Odin.
Flash the latest stock firmware via odin on pc, root it etc, flash the custom rom straight over the top via custom recovery. Never erase anything as it isn't necessary. Any issues just flash the stock firmware via odin and start again.

Stock Rom Pre Rooted Magisk Install thru TWRP

Hello ALL
I installed TWRP today and after i did that my stock rom stopped working. I tried to reinstall the stock rom thru odin but oding just closes out after it starts the process. I tried odin 3.12.3 and odin 3.13. Anyways Could someone make a stock rom rooted with magisk or guide me on how to do it myself. PLEASEEEEEEE
BTW my bootloader was unlocked
I had a magisk patched imaged so i was alread rooted and working fine with the latest april update.

Categories

Resources