Hi,
I would appreciate assistance with my situation please.
My note 3 N900 was updated via Kies to its latest firmware (Android 5.1.1 if I'm correct). No rooting/installing/flashing of any rom or custom recovery had been done before this.
Following instructions. Using odin3 v3.10.6 I successfully flashed TWRP recovery (twrp-2.8.7.0-ha3g.img.tar from official site)
When trying to enter TWRP recovery holding volume up + home + power at the same time. A fallen android bot showed the message "no command"
I found a solution to over come that part. The solution I followed was to uncheck "auto root" in odin and after successfully flashing twrp recovery, remove the battery for about 5 or 10 seconds, re-insert the battery and boot into recovery.
It worked and I was in TWRP recovery.
I did a full wipe, cache/davlik/system/data etc (I have no files I wanted in the internal memory).
Then proceeded to install the custom rom from the external memory card (Dark-Au S6 V4 Final N900 from xda).
It said successfully installed, clicked reboot ... and it stayed stuck on the Samsung logo.
Re-did the whole process, this time after successfully installing the rom I did a cache/davlik wipe and rebooted ... still gets stuck on the logo.
Please help,
Thanks
XDA Visitor said:
Hi,
I would appreciate assistance with my situation please.
My note 3 N900 was updated via Kies to its latest firmware (Android 5.1.1 if I'm correct). No rooting/installing/flashing of any rom or custom recovery had been done before this.
Following instructions. Using odin3 v3.10.6 I successfully flashed TWRP recovery (twrp-2.8.7.0-ha3g.img.tar from official site)
When trying to enter TWRP recovery holding volume up + home + power at the same time. A fallen android bot showed the message "no command"
I found a solution to over come that part. The solution I followed was to uncheck "auto root" in odin and after successfully flashing twrp recovery, remove the battery for about 5 or 10 seconds, re-insert the battery and boot into recovery.
It worked and I was in TWRP recovery.
I did a full wipe, cache/davlik/system/data etc (I have no files I wanted in the internal memory).
Then proceeded to install the custom rom from the external memory card (Dark-Au S6 V4 Final N900 from xda).
It said successfully installed, clicked reboot ... and it stayed stuck on the Samsung logo.
Re-did the whole process, this time after successfully installing the rom I did a cache/davlik wipe and rebooted ... still gets stuck on the logo.
Please help,
Thanks
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
Since there are so many variants, I wonder if the ROM matches the phone.
At any rate, I am connecting this thread to the forum your device experts can be found:
> Samsung Galaxy Note 3 > Galaxy Note 3 Q&A, Help & Troubleshooting
Please note, to respond to replies, you will need to have an XDA account.
Hope this helps, and good luck!
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
I rooted my Sprint Note3 Android 4.4.2 using AutoCF method with Odin and then installed ROM Manager from Google Play and then used it to install CWM recovery, which it was able to flash. Then I used ROM Manager to manually boot into CWM recovery. Now it is stuck perennially in a boot sequence and is giving this message:
Recovery booting
recovery is not seandroid enforced
set warranty bit : recovery
HELP. I just got this phone two days ago and had already set it up with all my apps and accounts. Can I at least get it back to the stock image? Please help me.
SOLVED using another thread
I found a solution in another thread http://forum.xda-developers.com/showthread.php?t=2666432
so that was the trick. REMOVE THE BATTERY --> PRESS THE DOWNLOAD KEYS AND HOLD THEM --> THEN ENTER THE BATTERY BACK
also, I followed this thread for installing Clockworkmod custom recovery on Sprint note 3 with android 4.4.2 using odin and it worked like a charm http://true-android.blogspot.com/2014/01/install-cwm-6045-advance-edition-on_2385.html
2 days ago i flashed twrp on my pure stock note 4, i did backup my rom including EFS using twrp and then flash kyubi rom with nameless kernel, it all went well. just now i wipe data ,system, cache on twrp and restore my backup stock rom and it went well too...and then i try to flash stock rom using odin so i can get back the stock recovery mode for OTA update when MM releases.. the flashing was a sucess and phone booted but my data inside werent wipe.
so i went to recovery mode and saw this dm-verity verification failed on the bottom i proceed to wipe data and reboot my phone, its all working now no problems except i cant reset my phone with the setting inside it will just bring me to recovey mode and stay there with that message.
now i did some research, some saying will bootloop and stuffs but mine is all ok no problem except i cant reset it inside the settings..
anyone can help me get rid of that message/problem?
If you format everything in advance format in twrp and then flash stock firmware this message will go away.
got the same problem. Then I went to a local store. They helped me. Here are steps
1. Pull out your battery, check your serial number (S/N:....)
2. Download smart switch, enter emergency software recovery..... Enter your serial number
3. Turn off your phone. Enter download mode or sth ( I don't remember it clearly. just power + vol down or up. just try it)
4. Smart switch will recognize your phone. Choose a firmware to download. then wait
5. Enjoy stock firmware
Use kies3 reinstall drivers, then use emergency recovery in kies to reinstall your current firmware or opt to update to latest or most recent release or version then follow kies instructions
rooted s5 smg900r4
Hello everyone
I have found a way to fix dm-verity and DRK issues and it works like official, meaning no errors in stock recovery and OTA works with Official firmware, the problem is related to corrupted/deleted 3 files on /efs partition. I have tested it on SM-N910C so I guess it works on other Exynos variants, perhaps even on snapdragon if the partition layout is similar? Kies won't restore DRK or dm-verity check because it doesn't write to EFS. I can fix yours if someone is interested via Team Viewer, you will need the following:
1. PM contact me for Skype ID
2. Stock rom, rooted (any root method)
3. Adb debugging enabled and drivers installed (Kies or SmartSwitch)
After repair you can enter your stock recovery and confirm there is no DRK/dm-verity red letters error.
Regards,
magix01
please guide us the proceedure here .. i have a phone with same problem & i have to update it to MM ...
dork997 said:
If you format everything in advance format in twrp and then flash stock firmware this message will go away.
Click to expand...
Click to collapse
Mine still says fail. but it also says "need to check drk first" could anyone possibly help me im stuck.the phone loads up and everything. but when i try to root or anything or flash any other firmware than n910pvpu5dqi5 it fails about 4 seconds in to flashing on odin. ive downloaded every possible firmware specific to the SM-N910P but only one worked.
im a big noob with the note 4 this is my first luckily its not my daily phone yet. im very familiar with the note 3 n900t but im finding they are very different. any advice would be appreciated!
Sir, please reply
When i unlocked my bootloader on my redmi phone this warning comes, but after clicking power button it will successfully boot to system but i m confused did i flash any rom in it, is it safe or not
Manish_k said:
Sir, please reply
When i unlocked my bootloader on my redmi phone this warning comes, but after clicking power button it will successfully boot to system but i m confused did i flash any rom in it, is it safe or not
Click to expand...
Click to collapse
If you just unlocked your bootloader and thats it, your rom should still be the stock one.
Hi,
I tried to install CWM on my rooted Note 3 N9005 with the latest 5.0 updates and the default recovery kept overwriting the custom. So I followed the advice on an article to delete the files [/system/recovery-from-boot.p] [/system/etc/install-recovery.sh] an this made my phone to fall in a loop, booting and trying to find these files then rebooting and so on...
I then had no choice but to load the stock ROM via ODIN which fixed the loop.
Is there anyway to install a custom recovery on a Note 3 running 5.0 - I want to do this in order to continue and install a custom ROM.
Thanks in advance for the answers!!
Don't use cwm as it has not been updated for a long time. Download the latest tar version of twrp for your phone.
Open Odin, uncheck everything except f.reset time, flash twrp, when you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait about 5 seconds, replace battery, use button combination to boot into recovery.
Thank you!!
What did the trick was that I quickly removed the battery and went to recovery mode. Even with "Auto Reboot" deselected the phone rebooted so if I left it it would have overwritten again the custom recovery.
Just a quick note to help others... anyone trying to flash Darklord or Phronesis ROM... USE TWRP v.2.8.0 and not the latest. The latest version for some reason won't install the ROMs.
thanx this wad so heapful .
:fingers-crossed::good:
abod7070 said:
:fingers-crossed::good:
Click to expand...
Click to collapse
Could be a year out of date and in some respects it is .
KEY is roms with AROMA installer will not work above 2.8 TWRP .
Hi Guys
I believe you guys on here will be able to help. Let me first tell you about my device and what I want to do and then what I did and what problems I encountered.
Device: Samsung Note 4 International Model SM-N910H (Exynos CPU)
OS: 6.0.1
Build Number: MMB29K.N910HXXU2DPE2
I only want to root my device and install Custom Recovery like CWM. I don't want to install a Custom ROM!
So I downloaded CF-Auto-Root-tre3g-tre3gxx-smn910h.tar.md5 and used Odin 3.12 to flash tar file to phone. After that phone rebooted and got stuck into the "Samsung Galaxy Note 4" Screen displaying in red letters on top left Corner "Recovery is not seandroid enforcing"
So I downloaded CWM Recovery v6.0.3.6.tar and flashed with Odin again, this time the phone rebooted back into my Working Phone OS and all seems fine. SO I wanted to test if CWM is installed? Powered phone down and booted into recovery & then got the same "Recovery is not seandroid enforcing" message on screen, so rebooted phone normally and it goes back into the OS. Also SuperU is not installed and phone is not rooted
So how do I solve this issue getting a Custom Recovery on my Phone Since I don't have any Recovery Mode option when booting into recovery. Your help, effort and time will be appreciated
Try again your steps and using odin both times make sure reboot is not ticked. After the flash pull the battery. There is a remark about that somewhere.
I had the same problem with my n9100 and at the end flashed custom rom to solve this. But my phone is slightly different to yours.
Thanks a mil, however I did manage to fix the issue and still wanted to resolve this post. I downloaded SuperU Beta 2.74 and different version of CWM. Installed CWM 6.0.5.1 (1113).tar with Odin 3.10.7 and it worked installing CWM Recovery. Then installed the SuperU 2.74 with CWM and everything works great. Phone now rooted and CWM installed :good::victory::victory:
******** Resolved ************
wilcovh said:
Try again your steps and using odin both times make sure reboot is not ticked. After the flash pull the battery. There is a remark about that somewhere.
I had the same problem with my n9100 and at the end flashed custom rom to solve this. But my phone is slightly different to yours.
Click to expand...
Click to collapse
I have the n9100 as well with the hong kong rom. I'm having the same problem while trying to root with cf-autoroot. I really want to root the phone while keeping the stock rom.
Is there any way to do so??