I just upgraded to the 4.4.2 by baja. The system would not reboot when I clicked reboot and the Bluetooth would not work. I opened rom manager fixed my permissions then like a dummy clicked reboot in to recovery. now it shows the custom screen when booting up then 1 second later it says recovery booting and just does this over and over again. I have tryed to get this into odin mode and it wont work. on rom manager I had set my system to twrp.
If anybody can help please do its my only phone. thanks!
underoath403 said:
I just upgraded to the 4.4.2 by baja. The system would not reboot when I clicked reboot and the Bluetooth would not work. I opened rom manager fixed my permissions then like a dummy clicked reboot in to recovery. now it shows the custom screen when booting up then 1 second later it says recovery booting and just does this over and over again. I have tryed to get this into odin mode and it wont work. on rom manager I had set my system to twrp.
If anybody can help please do its my only phone. thanks!
Click to expand...
Click to collapse
Only thing I can suggest is to do a battery pull. Wait about 10 seconds then replace the battery and put the phone in download mode. You should then be able to Odin back to stock and start over.
Hope this helps.
Tap'n N Talk'n on my N3
Fixed it
underoath403 said:
I just upgraded to the 4.4.2 by baja. The system would not reboot when I clicked reboot and the Bluetooth would not work. I opened rom manager fixed my permissions then like a dummy clicked reboot in to recovery. now it shows the custom screen when booting up then 1 second later it says recovery booting and just does this over and over again. I have tryed to get this into odin mode and it wont work. on rom manager I had set my system to twrp.
If anybody can help please do its my only phone. thanks!
Click to expand...
Click to collapse
I fixed it!!!
I removed the sd card and it removed the boot loop!
im leaving this here just incase somebody else gets the same problem.
underoath403 said:
I fixed it!!!
I removed the sd card and it removed the boot loop!
im leaving this here just incase somebody else gets the same problem.
Click to expand...
Click to collapse
I did something similar. I wanted to try the new Rick Rom and without thinking clicked reboot to recovery from the power menu enabled thru Wanam. Pulling the SD didn't work for me.
What should I flash in ODIN to fix this? I still have the rooted 4.4.2 build and firmware tar, or do I need to go all the way back to 4.3?
Never mind, I flashed the 4.4.2 firmware and all is good.
4.4.2
Sziehr said:
I did something similar. I wanted to try the new Rick Rom and without thinking clicked reboot to recovery from the power menu enabled thru Wanam. Pulling the SD didn't work for me.
What should I flash in ODIN to fix this? I still have the rooted 4.4.2 build and firmware tar, or do I need to go all the way back to 4.3?
Never mind, I flashed the 4.4.2 firmware and all is good.
Click to expand...
Click to collapse
You should be able to follow the instructions from
http://forum.xda-developers.com/showthread.php?t=2726558 just from the Odin part. That's what I would do. Anybody else have any other advice? I would stay with 4.4.2 can you get into Odin mode?
Related
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
Hi.
Downloaded Philz Touch CWM recovery on my phone, then i installed the superuser file, rebooted the phone, but its stuck on the samsung logo when youre rebooting the phone. What have i done wrong?
Please help.
My pone is G900F
Regards,
Simon
rundstykker14 said:
Hi.
Downloaded Philz Touch CWM recovery on my phone, then i installed the superuser file, rebooted the phone, but its stuck on the samsung logo when youre rebooting the phone. What have i done wrong?
Please help.
My pone is G900F
Regards,
Simon
Click to expand...
Click to collapse
which firmware
pnr2020 said:
which firmware
Click to expand...
Click to collapse
I'm using stock, 5.0 lollipop.
rundstykker14 said:
I'm using stock, 5.0 lollipop.
Click to expand...
Click to collapse
use twrp its much better
It'll be done next time.
But how do i get out of this mess, cant do anything whit the phone now, i only have access to recovery mode. What should i do?
rundstykker14 said:
It'll be done next time.
But how do i get out of this mess, cant do anything whit the phone now, i only have access to recovery mode. What should i do?
Click to expand...
Click to collapse
Flash stock firmware again.
Do a initial setup.
Flash twrp
Disable MTP in mount options
Flash Update_supersu.zip
reboot
qubbus said:
Flash stock firmware again.
Do a initial setup.
Flash twrp
Disable MTP in mount options
Flash Update_supersu.zip
reboot
Click to expand...
Click to collapse
if you can get into download mode just flash twrp with odin
I flashed twrp whit odin, rebooted, and its still stuck at the samsung logo as its starts, and it has been there for at least 30min. suppose to take this long??
Do a full wipe
New to the S4 - did a search and could not find a similar problem as mine...
My friend gave me his S4 and told me it is rooted - which it is. However, there seems to be no recovery on the phone. When I try power-vol up-home, I get the blue recovery note at the top, but then the phone just continues to boot into the system (MF9). I used Odin to go back to stock and then attempted to boot into recovery - no luck. I rooted the phone again via CF Auto Root and tried to install a custom recovery via Odin and TWRP Manager - still no luck. Anyone have any ideas/suggestions? I appreciate the help.
Bumping this up to the top for one more run through...thanks everyone.
Sixbowmans said:
Bumping this up to the top for one more run through...thanks everyone.
Click to expand...
Click to collapse
Maybe go in to Odin mode and flash latest stock making sure to unchecked the auto reboot option. When it finishes flashing unplug and pull the battery, let it boot it'll take a while (took mine about 10-15 minutes). You'll then be on latest stock with latest bootloader and recovery. From there you can go back to Odin mode and flash TWRP. Once again making sure to not auto reboot.
Just to be safe back up apps and msic and picture etc on samsung kies and then do a full recovery delete everything and install the latest firmware then try cf auto root again or if you have trouble with that rhen use kingoroot and then flash twrp or phils recovory and get a rom. If that doesnt work just get cyanogenmod installer which installs root and a stock rom.
Sent from my SM-N910V using XDA Free mobile app
mattzeller said:
Maybe go in to Odin mode and flash latest stock making sure to unchecked the auto reboot option. When it finishes flashing unplug and pull the battery, let it boot it'll take a while (took mine about 10-15 minutes). You'll then be on latest stock with latest bootloader and recovery. From there you can go back to Odin mode and flash TWRP. Once again making sure to not auto reboot.
Click to expand...
Click to collapse
Thanks mattzeller. Your suggestion took me back to my Evo days. I took out the sd card, flashed with Odin, pulled the battery, rebooted the system, and then was also able to boot into recovery.
Hi All,
I have read through quite a lot of your threads on how to root a Note 3 and am getting nowhere. I once had it rooted and had Phronesis V4.1 and was working fine till one day it wasn't recognizing my sim card, so i tried putting Phronesis V5 on and ever since have had trouble. First it didn't work so i went onto Sammobile and down loaded Baseband Version N9005XXUGBOJ1. And have got my note 3 working again but i cant root it for some reason, when i try to go into recovery it says not rooted. It puts me into some sort of recovery when i press volume up/power/and the bottom button but when i try to it comes up with an error message in Red : Failed to verify wholefile signature, signature verified failed. This of course happened when i did have root. Any help or pointing in the right direction would be appreciated .
Norman
Have you tried flashing the latest supersu through twrp?
audit13 said:
Have you tried flashing the latest supersu through twrp?
Click to expand...
Click to collapse
Hi Audit13, Thanks for your reply. I cant put TWRP or any other recovery`s on, i put TWRP onto Odin and flashed it but it keeps reverting to the stock android recovery i have got on my device. At this precise moment i cant even get into stock recovery, i press the volume up/ power and home button whilst the Note 3 is off. It shows recovering into boot in blue and then set warranty bit: Recovery, but it just resets to starting up my phone. Also if i flash supersu will it work if i dont have a rooted device? tia
Normski15 said:
Hi Audit13, Thanks for your reply. I cant put TWRP or any other recovery`s on, i put TWRP onto Odin and flashed it but it keeps reverting to the stock android recovery i have got on my device. At this precise moment i cant even get into stock recovery, i press the volume up/ power and home button whilst the Note 3 is off. It shows recovering into boot in blue and then set warranty bit: Recovery, but it just resets to starting up my phone. Also if i flash supersu will it work if i dont have a rooted device? tia
Click to expand...
Click to collapse
Wipe your phone and reflash your stock rom egain,then flash the recovery...
Let us know! !!
jemis1983 said:
Wipe your phone and reflash your stock rom egain,then flash the recovery...
Let us know! !!
Click to expand...
Click to collapse
Ok will try thanks.
maybe you flashed the wrong recovery file.
Normski15 said:
Ok will try thanks.
Click to expand...
Click to collapse
Hi tried that wiped phone and reinstalled original stock, rooted it then put TWRP on and now i`m on a contsant loop of Recovery booting: Recovery is not a seandroid Enforcing. Set warranty bit : recovery. any help please.
Try another recovery... That'll help you out
When flashing TWRP in Odin, do not check anything except f.reset time. Flash TWRP and, when you see the word "reset" in the status window, remove the USB cable, remove battery, wait 5 seconds, replace battery, use the button combination to boot into recovery.
Thanks to everyone involved got it sorted, i am assuming i was using the wrong/or corrupt TWRP. Did what you kind people said and am back on Pronesis V5.
Hello,
First of all, I'm pretty new to all of these, even new to smartphone itself, so please pardon any of my misunderstanding.
Recently I've rooted my G530h, baseband number: G530HXCU1AOA2 using Kingo ROOT. The root went well I assumed since I can use SuperU and access root-only apps.
Then I proceeded to install a custom recovery for my phone, first I tried using TWRP (v2.8.7.0), flashing with Odin through download mode. After it was done, Odin showed that it was success, my phone restarted and went into a normal boot. I then turned off my phone and try to get into recovery mode (Vol Up, Home and Power), but instead my phone went into Download mode but this time straight into the Downloading scene without going through the warning one. I couldn't turn off my phone, I had to hold down Vol Down, Home and Power, the phone went into the warning scene for Download mode again, only by pressing cancel would I be able to boot normally again.
The same thing happened when I tried installing CWM.
Please help, if there is something I'm doing wrong... I can't get into the recovery mode which I tend to use for installing a custom ROM. I've also tried flashing my original stock, the stock recovery came back and worked fine, but the custom ones still have the same problem.
Thank you for your time.
Same proble for me
HI XDA members,
same problem for me, I have GGP G530H Version G530HSER1BPB1, I have try with odin and I get the pass message without any error, but when I try to bood into recovery mode I have found the same recovery mode (original by samsung ) I don't know what is the problem, I have try all the recovery found in the net, also on the russian forum (PDA) !
please any one cand give a solution, I hate the samsung firmware and I want change to CM12 or CM13 version.
Thanks
You need to directly reboot to recovery after flashing recovery for prevent the phone to reset recovery tp the stock one
D.R-Ult.Googler said:
You need to directly reboot to recovery after flashing recovery for prevent the phone to reset recovery tp the stock one
Click to expand...
Click to collapse
Done Thank you
I found a working version of CWM for my phone, the link is bellow.
https://drive.google.com/file/d/0B4SXad98IF1RX1dWNkxSQjRSU28/view
yadnen2001 said:
Done Thank you
Click to expand...
Click to collapse
u mean in odin make auto reboot off ?
OniGiRi6131 said:
u mean in odin make auto reboot off ?
Click to expand...
Click to collapse
yeah Right
And remove battery and restart on recovery mode