Database Users

[Q] Unable to install CWM or TWRP on Note 3 after 4.4.2 update

So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!

There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.

It's impossibe to flash anything other than the leaked 4.4.2 stock because you flashed your bootloader to kitkat, no you MUST stay on sammy 4.4.2 till the devs found a solution for this. Thats why you have to read carefully be4 you flash.

silentvisitor said:
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
Click to expand...
Click to collapse
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?

sid8907 said:
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
Click to expand...
Click to collapse
This one seems to be the only one working with 4.4.2 right now.

Possible solution
The way I can suggest is to create a little update.zip file with little updater-script to remove install-recovery.sh file from device (just one line needed).
Ok, I found a zip which I am attaching below. You(or anyone) may review the script before flashing.
Place this on your external (or internal) sdcard.
In ODIN don't check Auto reboot
Flash Recovery. Remove phone when it says PASS.
Remove battery. Start in Recovery mode by pressing buttons.
You should now be in new Recovery.
Flash that zip file.
Reboot.
You should be good.

The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.

I am out of ideas.
I would suggest you to wait for someone to come up with working solution. Being too adventurous with ODIN could brick your device.

sid8907 said:
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
Click to expand...
Click to collapse
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again

Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?

radicalisto said:
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Click to expand...
Click to collapse
Thanks!!

sid8907 said:
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
Click to expand...
Click to collapse
You may have to do a little reading but I believe CM11 is now working on the KK bootloader...

sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398

sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
jp.26 said:
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
Click to expand...
Click to collapse
so.... yeah i just updated my bootloader to 4.4.2 and this drove me literally insane. ive been working on it for 4 hours now. i encountered so many problems with installing the bootloader. exact same problem as SID8907. i gotta tell you tho.... you worked some magic my friend. i tried almost everything. then i came across your link. i was like why not? so i flashed the img in odin..... anddddd :drumroll pleaseeeeee:: IT WORKED. ahhh....... so much frustration and the problem is solved!!! thank you so much JP.26 :good::laugh:

is there any word on how to fix this been looking for hours tmobile note beast dont want to put any roots down on my phone before i find a way to flash cm or a non bloated note rom would be nice.

I'll that I've managed is to root and flash twrp I found a way to turn cwm recovery into a tar file and flash through odin. But i just get into a boot loop with cwm due to the boot loader I presume but tarp works fine I just can't flash cm11. I get boot loop every time
Sent from my SM-N900T using XDA Premium 4 mobile app

im sorry but im confused here... does this all simply mean that there is not yet a working cwm for 4.4.2 yet? and that while we can root, there is no working recovery for this version?

I'm not sure myself tarp works but I can't flash cm11
Sent from my SM-N900T using Tapatalk

Phillz cwm Dev edition I think that's the name works its a themed touch cwm. This works great but still can't flash cm so gayyyy
Sent from my SM-N900T using Tapatalk

I was wondering what happened to the cmw too.
The modded cmw by Chenglu is the only one working that I know of.
Link to thread: http://forum.xda-developers.com/showthread.php?t=2454079

[Q] Note 3 could not do normal boot error

Hi,
My Note 3 is not able to reboot properly after i flashed the file n900s-cwm-recovery-6.0.4.7-kk(0125) using ODIN.
An hour back i had successfully used CF Auto root and all was working well. Wanting to flash a custom ROM i tried putting in CWM and now have this issue.
I have taken out the battery and tried rebooting but stuck at the same Download mode. The screen reads like this
Please advise what needs to be done.
Thanks
Resolution: I resolved this by manually going into download mode and using cancel option. Then it started fine. But does that mean i did not successfully install CWM? Tried going into recovery but it goes back to download mode.

aayushjoshi said:
Hi,
My Note 3 is not able to reboot properly after i flashed the file n900s-cwm-recovery-6.0.4.7-kk(0125) using ODIN.
An hour back i had successfully used CF Auto root and all was working well. Wanting to flash a custom ROM i tried putting in CWM and now have this issue.
I have taken out the battery and tried rebooting but stuck at the same Download mode. The screen reads like this
Please advise what needs to be done.
Thanks
Resolution: I resolved this by manually going into download mode and using cancel option. Then it started fine. But does that mean i did not successfully install CWM? Tried going into recovery but it goes back to download mode.
Click to expand...
Click to collapse
Recovery is up volume, home and power. You shouldn't get dl mode if you hold these buttons...
If you have no recovery installed then it will just try to boot....
Make sure you are using the correct recovery and then try flashing again...

aayushjoshi said:
Hi,
My Note 3 is not able to reboot properly after i flashed the file n900s-cwm-recovery-6.0.4.7-kk(0125) using ODIN.
An hour back i had successfully used CF Auto root and all was working well. Wanting to flash a custom ROM i tried putting in CWM and now have this issue.
I have taken out the battery and tried rebooting but stuck at the same Download mode. The screen reads like this
Please advise what needs to be done.
Thanks
Resolution: I resolved this by manually going into download mode and using cancel option. Then it started fine. But does that mean i did not successfully install CWM? Tried going into recovery but it goes back to download mode.
Click to expand...
Click to collapse
Yes happened to me a while back You cannot go into recovery just download mode and when you restart from dl mode then it works. Only thing you can do to fix that is flash recovery.tar again through odin to get your recovery working again. it doesnt effect your system though. System will keep working.
Edit : Use TWRP this and i just read the title of recovery N900s do you have a different device not n9005 ???
Because for N9005 international version it should say hlte, hltexx or n9005
Sent from my SM-N9005 using Tapatalk

I fixed the issue by flashing Philz CWM recovery. After that i flashed a X Note ROM and all good now. Thanks for the help guys.

[Q] have i lost root forever ? help !

all.
I have an i9505 on 3 UK that has been rooted for over 6 months. I've been running the excellent TW based Echo Rom but wanted to try an ASOP rom but quickly wanted to revert.
I tried to restore my Nandroid but this failed and screwed up the phone (dont ask)so back to ODIN and i flashed back to stock 4.4.2 firmware for the UK via Sammobile (NG8)
Now back to square 1 so attempted to reroot with CF Autoroot again via ODIN. all show pass and i get the black screen on the phone with the red android logo and line stating stock recovery restored. I then used ODIN to flash Philz recovery again shown as Pass, however when i try to get into recovery i get some small white text on the bkack background that is there too briefly to read before the phone reboots as normal.
The Su superuser app is there but states the Su binary is outdated and the phone has no root access.
Ive read a few methods to get round this but they all seem to follow the same process ive tried a few times now.
The Rom for Echoe is auto root so id have thought if i could get to recovery somehow i could just flash this ?
Any one any views or have i screwed up for good ? .

You will be fine.
If you want to flash a custom rom anyway the shortest way would be to just flash the custom recovery. You don't need root for that.
Uncheck auto-reboot before you flash the recovery and it should work.

Lennyz1988 said:
You will be fine.
If you want to flash a custom rom anyway the shortest way would be to just flash the custom recovery. You don't need root for that.
Uncheck auto-reboot before you flash the recovery and it should work.
Click to expand...
Click to collapse
so i reflashed Philz recovery and unchecked auto reboot. This then gives me PASS in ODIN. I guess then i unplug and try and activate recovery - but still nothing...it just boots up normally ?

robinta said:
so i reflashed Philz recovery and unchecked auto reboot. This then gives me PASS in ODIN. I guess then i unplug and try and activate recovery - but still nothing...it just boots up normally ?
Click to expand...
Click to collapse
What is the model descriped when you are in download mode?
What is the exact version of Philz you are trying to flash?

Lennyz1988 said:
What is the model descriped when you are in download mode?
What is the exact version of Philz you are trying to flash?
Click to expand...
Click to collapse
GTI9505...(Bootloader i9505xxegng8)
Originally I tried philz_touch_5.15.8-i9505.tar.md5
and then updated to philz_touch_6.23.9-i9505.tar.md5 with no avail.

Try redownloading it. If you say that if passes, then it should just work.
If it still fails then try TWRP. Uncheck auto-reboot before flashing.

Could it be connected to me flashing a generic unlocked UK firmware on a 3 UK handset ?

That's sorted it ! Flashed CWM recovery and am now running Echoes v28.
Thanks for the help. I was really panicking for a while.
I wont be changing roms for a while but I guess if I did I won't lose root ?

[Q] Failed to install Cyanogen, wont open anymore

I have this SGH-i337M with Virgin Mobile which is fully updated to Android 5 and decided to give rooting a go. I used CF-Auto-Root which worked automagically. I used my phone for a day with all the priviledges and it was great.
This afternoon, I tried to install CyanogenMod using their automated installer and it failed. I read around. It says I can flash it in Recovery mode. I give Recovery mode a look and seeing that it was the stock recovery program I thought I'd better install ClockworkMod or something so I hit Reboot Device.
It booted. The apps won't start. No login screen, just a black background with piles and piles of white boxes with "<APPNAME> stopped working. (Ok) (Report)".
What's the best solution? Ultimately, I want CM12...

lgsshedden said:
sounds as if you have an error either in the absence of a custom recovery or the kernal. Pull the battery, wait 30 seconds at least. Go into download mode, use Odin to reflash the stock Bell OC4 firmware but leave auto-boot unchecked -- wait until Odin goes green and says pass -- this can be quite a wait. Pull the battery. Restart the phone. Don't be surprised if it goes into stock recovery on first boot -- let the phone do its thing to get itself sorted. Set the phone up in stock mode first.
Then go back into Odin, flash a custom recovery and install SuperSu using a zip file flash from within that custom recovery.
Click to expand...
Click to collapse
Pushing that with ODIN did the trick: samsung-updates.com/details/44119/Galaxy_S_4_Canada/SGH-I337M/VMC/I337MVLUGOC4.html
Case closed! yay

Help Root Samsung S5 5.0 SM-G900H baseband G900HXXU1BOL2 BUILD # LRX21T.G900HXXS1BPD2

Hello, I need help to rooting my phone. I am currently using Samsung Galaxy S5 model number SM-G900H with Android version 5.0, Baseband version G900HXXU1BOL2 , Kernel version 3.10.9-5852541, Build Number LRX21T.G900HXXS1BPD2, and KNOX 2.3.
I've follow many tutorials on how to root my S5 but with no luck... it always get boot stuck after flashing CF-Auto-Root-k3g-k3gxx-smg900h.tar.md5 using ODIN3-v3.10.6. What else could be wrong ?

Some S5s don't like CF AR
Copy SuperSU.zip to your phone/microSD
Flash TWRP with ODIN (Uncheck Auto reboot first in ODIN)
http://forum.xda-developers.com/showthread.php?t=2725939
Once it completes the flash, disconnect the USB, and pull the battery to power off the phone
Replace the battery, and immediately boot into recovery with Volume Up & Home & Power
Flash SuperSU
Reboot (If asked to root again from TWRP after flashing SuperSU, say NO)

*Detection* said:
Some S5s don't like CF AR
Copy SuperSU.zip to your phone/microSD
Flash TWRP with ODIN (Uncheck Auto reboot first in ODIN)
http://forum.xda-developers.com/showthread.php?t=2725939
Once it completes the flash, disconnect the USB, and pull the battery to power off the phone
Replace the battery, and immediately boot into recovery with Volume Up & Home & Power
Flash SuperSU
Reboot (If asked to root again from TWRP after flashing SuperSU, say NO)
Click to expand...
Click to collapse
Thank you for your assist... i will try it and post the results here... Should i use the last version of Odin and SuperSU anyway ?

Yep, use the latest versions

*Detection* said:
Yep, use the latest versions
Click to expand...
Click to collapse
I did all the step above but after flashing twrp-k3gxx.tar , remove the battery and entering recovery mode, nothing is change there, it just entering the original recovery mode. Do twrp-k3gxx.tar is the correct version for my SM-G900H ?

*Detection* said:
Yep, use the latest versions
Click to expand...
Click to collapse
frenxl said:
I did all the step above but after flashing twrp-k3gxx.tar , remove the battery and entering recovery mode, nothing is change there, it just entering the original recovery mode. Do twrp-k3gxx.tar is the correct version for my SM-G900H ?
Click to expand...
Click to collapse
What happen if I just flash SuperSU directly via ODIN ?

Did you put the phone in download mode, and did ODIN show a connected COM port at the top?
Did it say successful flash?
Try leaving Auto Reboot checked and do it again, let the phone reboot, and then try booting into recovery
You can't flash SuperSU from ODIN, it's a zip file, not an ODIN flashable .md5 or .tar

*Detection* said:
Did you put the phone in download mode, and did ODIN show a connected COM port at the top?
Did it say successful flash?
Try leaving Auto Reboot checked and do it again, let the phone reboot, and then try booting into recovery
You can't flash SuperSU from ODIN, it's a zip file, not an ODIN flashable .md5 or .tar
Click to expand...
Click to collapse
Yes I did put the phone in download mode, and ODIN show a connected COM port, i know how to used it and succesfully flashing the twrp-k3gxx.tar, pull the batt out and back in, boot in to recovery mode and nothing is happen... i just entering the stock recovery mode. it is like something overwrites the custom recovery right just before the phone boot up.
I think it is likely that Root image doesn’t seem to worked with the newest Android software update version, or maybe Samsung might also try to released some patches to the Android system that might prevent from customizing ?
I also tried to flasing CF-Auto-Root-k3g-k3gxx-smg900h.zip but it soft-break my phone so i have to flashing back to stock rom (luckyly i have download it before)

Stuck with the same issue. Plenty of Auto Root tutorials are available. Each one specifies that tutorial is exclusive to particular model number. G900HXXUIBOL2 is my build number. Once installed CF Auto Root. When verified via Root Checker, it showed success and got root access !!..But Couldn't enter recovery mode since then..was getting stucked in boot loop when trying to enter recovery mode. Had to restore stock ROM...Really frustrated with Samsung's UI. Wish I could change to Cyanogenmod..Any help would be really appreciated..Thanks in Advance