Hi guys,
I am using the SM-N9005 Note 3 variant and am unable to update the phone.
I am rooted and have tripped knox (0x1) and have tried using Wanam to set the Device Status to 'Official' which lets me download the update but will not install. When it tries to reboot to install, it enters CWM and a screen of errors flash for a few seconds and reboots back normally without installing the update.
I have also tried updating via Kies but once the installation process goes to > 90%, my computer automatically shuts down for some reason.
If there's any way to update (and is it worth the trouble to update?), I'd like to know, thanks!
Currently on build number/baseband N9005XXUBMJ1.
edit: thanks guys!
OptimusTM said:
Hi guys,
I am using the SM-N9005 Note 3 variant and am unable to update the phone.
I am rooted and have tripped knox (0x1) and have tried using Wanam to set the Device Status to 'Official' which lets me download the update but will not install. When it tries to reboot to install, it enters CWM and a screen of errors flash for a few seconds and reboots back normally without installing the update.
I have also tried updating via Kies but once the installation process goes to > 90%, my computer automatically shuts down for some reason.
If there's any way to update (and is it worth the trouble to update?), I'd like to know, thanks!
Currently on build number/baseband N9005XXUBMJ1.
Click to expand...
Click to collapse
You need to have stock recovery to do that. My recomendation, flash stock firmware then update and then root your phone
OptimusTM said:
Hi guys,
I am using the SM-N9005 Note 3 variant and am unable to update the phone.
I am rooted and have tripped knox (0x1) and have tried using Wanam to set the Device Status to 'Official' which lets me download the update but will not install. When it tries to reboot to install, it enters CWM and a screen of errors flash for a few seconds and reboots back normally without installing the update.
I have also tried updating via Kies but once the installation process goes to > 90%, my computer automatically shuts down for some reason.
If there's any way to update (and is it worth the trouble to update?), I'd like to know, thanks!
Currently on build number/baseband N9005XXUBMJ1.
Click to expand...
Click to collapse
get update at www.sammobile.com get yours and flash with odin ,you will lose root
you can flash stock rom with MOP to keep root.
Will try.
You are better off updating with a custom Rom. You will still have your mj1 boot loader but latest rooted firmware
Sent from my SM-N9005 using Tapatalk
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
Hello,
many people out there say it's impossible to do a full unroot on the S4 Mini, but I'll prove them wrong:
If you have a custom recovery like clockworkmod installed, that's obvious for a rooted phone,
before flashing you'll have to flash an original Samsung stock recovery first.
Otherwise the after-reboot process doesn't work correctly and you'll still have status "custom".
So here is what I did step-by-step:
- I startet with a rooted Samsung stock rom (XXUAMG8)
- I let SuperSU unroot the device (one of it's options), then
- I went into system/accounts/backup&restore and did the full restore - reboot
- I installed an original Samsung stock recovery with Odin - reboot
- I flashed the original Samsung stock rom (XXUAMG8) with Odin.
Afterwards you can check in DL mode the status, it's all "Official".
Additional Notes:
On my phone, when I didn't flash the samsung recovery first, the system boot time increased to up to 5(!) minutes every time (not only the first one...)
And why would I want to unroot my phone?
The warranty is void anyway. The Knox flag remains 0x1.
Original Samsung Stock Recovery Request
Hello, friend!
Can you get me that "original Samsung stock recovery" you mentioned, please?
Recently, I flashed a CWM file on my GT-I9192 and it doesn't work properly.
I'm searching everywhere and I couldn't find anything that helped me out...
So you're my savior...:laugh
Please attach the file or show me the link... So you will help not just me, but too many people that just messed up their phones..:angel::good:
Best regards from Brazil.
If you do not want to flash a custom rom, you don't need cwm.
Instead, use saferoot
http://forum.xda-developers.com/showthread.php?t=2565758
...
work perfectly on my seranoltexx.
gogoland2002 said:
If you do not want to flash a custom rom, you don't need cwm.
Instead, use saferoot
...
Click to expand...
Click to collapse
This thread is about UNROOTING and not how to root...
cemimo said:
And why would I want to unroot my phone?
The warranty is void anyway. The Knox flag remains 0x1.
Click to expand...
Click to collapse
This how-to is about a phone with an older bootloader without knox.
So if you have a knox free bootloader, this description leads you back to full warranty conditions
help
Peter Semper said:
Hello,
many people out there say it's impossible to do a full unroot on the S4 Mini, but I'll prove them wrong:
If you have a custom recovery like clockworkmod installed, that's obvious for a rooted phone,
before flashing you'll have to flash an original Samsung stock recovery first.
Otherwise the after-reboot process doesn't work correctly and you'll still have status "custom".
So here is what I did step-by-step:
- I startet with a rooted Samsung stock rom (XXUAMG8)
- I let SuperSU unroot the device (one of it's options), then
- I went into system/accounts/backup&restore and did the full restore - reboot
- I installed an original Samsung stock recovery with Odin - reboot
- I flashed the original Samsung stock rom (XXUAMG8) with Odin.
Afterwards you can check in DL mode the status, it's all "Official".
Additional Notes:
On my phone, when I didn't flash the samsung recovery first, the system boot time increased to up to 5(!) minutes every time (not only the first one...)
Click to expand...
Click to collapse
I know this is an old thread and this is my first post.
I have tried doing these steps and my device still says custom I think I am using the wrong stock firmware I was on Vodafone UK firmware then rooted to Cwm 6.0.4.6 I am currently trying to unroot to receive ota update as kies doesn't work to update I did unroot with original firmware that was btu black edition I am guessing this shouldn't make a difference but if I am wrong then go ahead and laugh at me but I do need help with my phone
thanks
steve
mason01983 said:
I know this is an old thread and this is my first post.
I have tried doing these steps and my device still says custom I think I am using the wrong stock firmware I was on Vodafone UK firmware then rooted to Cwm 6.0.4.6 I am currently trying to unroot to receive ota update as kies doesn't work to update I did unroot with original firmware that was btu black edition I am guessing this shouldn't make a difference but if I am wrong then go ahead and laugh at me but I do need help with my phone
thanks
steve
Click to expand...
Click to collapse
flash twice the firmware in odin, sometimes baseband isn't flashed
Didn't work for me either.
Starting from CM11, wanted to flash latest stock ROM with KNOX boot loader removed - downloaded my local carrier-specific firmware from Samsung updates, then proceeded to use the tar and md5 -rt tools on a Mac, failed signature. So did it in Windows using 7zip and it managed to flash. Did it twice to ensure baseband was flashed.
Flashing the stock recovery then doing the same still gives me a custom version
Anyone has any ideas on how to return to stock? I'm on non-KNOX boot loader.
Sent from my SM-N9005 using XDA Premium 4 mobile app
I had cm 4.4.2 on my I9195 I have to re flash with odin to go back to clockwork mod then flash original firmware twice and it worked just waiting for the ota update now
problem
It did work flashing original firmware twice however I go into recovery mode and I have a dead android with a red triangle and the words no command
It works. I got "official" status and I can download software updates, but now I get dead android with red triangle when I go recovery mode with this message:
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : NEE
Succesfully applied multi-CSC.
No command.
And when I select reboot it says "error," then reboots normally and everything works fine... But is there something wrong?
TyhjÀntoimittaja said:
It works. I got "official" status and I can download software updates, but now I get dead android with red triangle when I go recovery mode with this message:
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : NEE
Succesfully applied multi-CSC.
No command.
And when I select reboot it says "error," then reboots normally and everything works fine... But is there something wrong?
Click to expand...
Click to collapse
Which recovery?
splitterzelle said:
Which recovery?
Click to expand...
Click to collapse
Samsung stock recovery which is attached in the first post.
Same prob.
TyhjÀntoimittaja said:
Samsung stock recovery which is attached in the first post.
Click to expand...
Click to collapse
Same here. I've got problems with that Android Stock recovery file. After flashing it, when I tried to go into recovery mode, the dead android logo appeared. However if I reflash CWM everything goes ok. Where can I find another stock android recovery file?, it seems that this one only works for some specific sort of models. Mine is: GT-i9195L. (the "L" doesn't really matter).
Thanks.
I have a SM-N900V that is about 13 months old. I used Towelroot to root it when I could not edit files on my SD card. It also had Safestrap Recovery. I am still running the stock 4.4.2 and wanted to upgrade to 4.4.4. I used the Safestrap app to remove the Safestrap Recovery and used Super SU to remove the Root. I know that I am unrooted and when I boot into Recovery, Safestrap is gone. I still have the words Custom and the Unlocked Lock picture on my Splashscreen.
If I go to Settings/About Phone and click on Software Update, I can Download it. When I click on Install, it boots into Recovery and starts to Install but stops about 1/3 of the way with the green Android and the word "Error", then it Reboots.
How do I successfully install 4.4.4?
I have successfully Rooted and installed Custom Roms on a Droid Eris, HTC Thunderbolt, and Galaxy S3 using CWM Recovery. Because there were issues putting CWM on the Note 3, I just Rooted it and did not add any Custom Roms.
Do a factory restore and then try....or, flash the stock NC4 ROM via Odin and then upgrade
Sent from my Note 3 via Tapatalk
donc113 said:
Do a factory restore and then try....or, flash the stock NC4 ROM via Odin and then upgrade
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
I tried the Factory Wipe and Erase Data, then Reboot and Upgrade to 4.4.4. I always see Custom. on the Splash Screen, with the Unlocked Lock image and then see the Error message while Installing. Then, it reboots. I have never used Odin, but I will try it. Where do I find Odin and the NC4 Rom?
buschbarber said:
I tried the Factory Wipe and Erase Data, then Reboot and Upgrade to 4.4.4. I always see Custom. on the Splash Screen, with the Unlocked Lock image and then see the Error message while Installing. Then, it reboots. I have never used Odin, but I will try it. Where do I find Odin and the NC4 Rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2483380
Sent from my Note 3 via Tapatalk
As it turned out, flashing the Stock 4.4.2 Rom, with Odin, got rid of the issue preventing me from Upgrading to 4.4.4 and also restored the Samsung Splash Screen.
One issue I ran across was the link to the Odin download also downloaded Spyware to my W7 machine. Among other things, a Launch Bar appeared near the bottom of my Desktop. I was able to go into Add/Remove programs and Uninstall all 4 programs.
I still am annoyed by the fact that I cannot edit files on my SD card. It appears that Towelroot does not work with 4.4.4 as it did with 4.4.2.
Good afternoon guys,
i have a big issue with my galaxy s5 SM-G900S (korean version). I bought it as a refurbished device. Knox was on 0x1 so something may have been modified.
It came with the stock (?!) android 4.4.2 from march14. I tried to update but it returned a registration error. Probably because knox is 0x1
In any case, I activated usb debugging and tried to root the phone using cfautoroot and the corresponding root file: CF-Auto-Root-klteskt-klteskt-smg900s.zip which I still assume to be the correct one.
I used odin for flashing. The device was properly connected (blue).
Everything seemed to go smooth until the phone restart when it said "recovery is not seandroid enforcing". I tried several times with both odin 3.07 and 3.09 but i cannot pass this step. I also tried the method to untick auto reboot, shut the phone down manually and boot into recovery mode but it failed.
This means I am now stuck in the bootloop. I can access download mode, but i cannot reach recovery mode. Also the phone is not recognized by the computer if i try to connect it to adb, kies etc. Odin seems to connect properly still.
Alright how should i proceed now?? My actual target is to flash a custom rom. I will need to go for a dirty flash now correct? Should I flash a stock rom with odin? If yes, which one?
Please support me a bit, I am very frustrated on this topic, especially cause I still dont realize my mistake......
Merry Christmas and greets from Bavaria, Germany.
cheeet
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
toxious651 said:
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
Click to expand...
Click to collapse
Alright, Im back to stock android 4.4.2 now. Works perfect, aside from registration. If I click on "update now" it shows: SKT-USIM required.
Can someone link a detailed guide for flashing cm13? I checked the web but i still dont entirely understand.
In any case I do not want to risk going into a tricky situation once more.....
Thanks in advance.
Greets, cheet
Hi everyone, I wanted to put a root issue on the Galaxy S7 edge.
I installed via Odin the latest version of ITV PDA G935FXXU1DQIC and CSC G935FITV1DQI1.
Once you've finished flashing once, I put it back in Download Mode and always flash through Odin the latest version of AutoRoot.
However, the phone still hangs before loading with a screen that warns me that the integrity of the system has not been checked out. I had tried to disable all security settings several times, but nothing. Once I install the root the phone gives me an error telling me that to reset the device I should do a factory reset.
How can I fix it is what? With previous firmware it did not work out what.
ExileTM said:
Hi everyone, I wanted to put a root issue on the Galaxy S7 edge.
I installed via Odin the latest version of ITV PDA G935FXXU1DQIC and CSC G935FITV1DQI1.
Once you've finished flashing once, I put it back in Download Mode and always flash through Odin the latest version of AutoRoot.
However, the phone still hangs before loading with a screen that warns me that the integrity of the system has not been checked out. I had tried to disable all security settings several times, but nothing. Once I install the root the phone gives me an error telling me that to reset the device I should do a factory reset.
How can I fix it is what? With previous firmware it did not work out what.
Click to expand...
Click to collapse
If you are using Chainfire's Autoroot it wont work on Nougat.. if you use some third-party AutoRoot i can't help you.
Best way i can recommend to you is to flash latest TWRP and easly get root also you can flash some of great custom roms you can get here!