Hi XDA community,
I'm new to the Android community (Yeah, my previous phone was from Apple), and am currently enjoying trying new ROMs.
I have a international Note 3 SM-N9005 thatt was on 4.3 Android when I flash a CM11 nightly. (With TWRP, last version to date)
After, I tried to flash the Slim W03 v6 and it work very nice.
Here comes the problem.
I wanted to give a shot to other ROMs: X-note and Crash Rom. They installed, I reboot and I got stuck to the "Galaxy Note 3" Boot logo and nothing.
I can get back to my Nandroid Slim W03, but not to the CM11.
From what I read, it seems to be a bootloader version problem... I added up some picture to provide some background.
Is there a tutorial/thread to help me go through this situation?
Cheers to you and thanks for your help!
PAco
First try booting up to recovery and do a factory reset. If still stuck at the samsung splash screen ( give it a little time of at least 5 minutes to see if it's going to go through ), then you're still probably on 4.3 bootloader and you flashed a 4.4-based rom. If this is the case, you either have to update to stock 4.4 then flash custom recovery and root before you can flash 4.4-based roms or stay at 4.3 and you can flash 4.3 based roms.
Thanks. I'll try and see. Cheers mate.
Sent from my SM-N900T using XDA Premium 4 mobile app
Hi Joe, just for my personal knowledge, do you have a way to display your bootloader version / status (loi locked vs unlocked)? Thanks again
Sent from my SM-N900T using XDA Premium 4 mobile app
Don't really know how to display version if your phone doesn't boot up to system but if you put it in download mode, if you have 4.4 bootloader you will see " udc start " at the last line.
Sent from my SM-N900W8 using xda app-developers app
Hi, Here is what is displayed when in downloading mode:
Odin MOde
Product Name: SM-N9005
Current binary: Custom
System Satatus: Custom
Reactivation lock: OFF
Know Kernel Lock: 0x0
Know Warrantly void: 0x1
Qualcomm secureboot: enable (CSB)
AP swrev: s2, T2; R2, A2, P2
Write protection: Enable
**LOGO ANDROID**
Downloading...
Do not turn off target
So I guess I still have a 4.3 Bootloader.
Thanks Joe, you really helped!
Related
Hi, im new here sorry if posted in wrong section
I tryed rooting my Samsung Galaxy Note
I followed every step and unfortunantly after 40 seconds of pressing start I recieved on Odin a red Fail box
Odin looked like it had finished what it was doing even though it failed, so I pressed exit and disconnected the phone.
when I switched the phone back on I got this message
"Firmware upgrade encountered an issue. Please select recovery mode in kies & try again"
So I connected to Kies but the phone wont connect. I tryed the recovery but ive never used Kies before so there was no files to recover.
I tryed firmware and initialisation by putting my model and seriel number in but there was nothing found for Samsung Galaxy Note 3.
I dont want to go any further as im not sure what im doing now and ive stopped researching as im nit sure what websites to trust or able to find a correct answer to my issue.
My phones a
Samsung Galaxy Note 3
SM N900
Android Jelly Bean 4.3
United kingdom
(Not sure of other details I cant get into phone to look)
I thought I would come her as my friend recommended the site. I need help on how to make my phone work again.
I can still boot in download mode but I cant connect to computer but I havent tryed to connect to Odin.
ive rooted 5 of my other phones and tablets in the past and never had an issue, so this is new to me
Any fix I am happy with weather its a root fix or back to normal fix I just want my phone working again.
I definantly wont be rooting again im worrying my phone wont work at all now
thank you for any help!
On my screen I have
ODIN MODE (in red)
PRODUCT NAME: SM-N9005
CURRENT BINARY: Custom
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX KERNAL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
(In gray)
QUALCOMM SECUREBOOT ENABLE (CSB)
AP SWREV: S2, T2, A2, A2, P2
WRITE PROTECTION: Enable
then theres a pic of a phone, yellow triangle with an exclamation mark and a computer
then underneath the firmware upgrade error.
case elovmos
Im not 100% sure if I enabled USB debugging first. Will this cause me a problem?
Yes enable usb debug
To get away from this situation flash stock firmware
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
I havent fixed the problem but im doing research im one step closer
Mate. .. Get odin 3.09 and download firmware from sammobile.com. Try with the older firmware versions first like MI6 or something. ... If that don't work. .. Flash MJ7 latest firmware(can't go backwards once you Flash this firmware) and will definitely work
Sent from my SM-N9005 using Tapatalk
alom5 said:
Mate. .. Get odin 3.09 and download firmware from sammobile.com. Try with the older firmware versions first like MI6 or something. ... If that don't work. .. Flash MJ7 latest firmware(can't go backwards once you Flash this firmware) and will definitely work
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Ummm sammobile? Y know that hotfile is down and will never come back online due to DCMA complaints?
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
Killberty said:
Ummm sammobile? Y know that hotfile is down and will never come back online due to DCMA complaints?
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
Click to expand...
Click to collapse
They have a different server now. A lot slower though...
I'm in need a help with my Galaxy Note 3 n9005.
I have rooted my Note3 by kingoapp and now, seeing in Odin Mode the CURRENT BINARY was changed to CUSTOM and the KNOX WARRANTY VOID to 0x1.
I know that there is not way to reset the KNOX WARRANTY VOID.
The questions is: When I try do Software Update I get a message that is not possible do Software Update because I have changed my android.
Is still possible change my CURRENT BINARY Custom to Samsung Official? And if it be possible, the Software Update will work?
How can I change my CURRENT BINARY: Custom to Samsung Official?
Thx.
leandroaa said:
I'm in need a help with my Galaxy Note 3 n9005.
I have rooted my Note3 by kingoapp and now, seeing in Odin Mode the CURRENT BINARY was changed to CUSTOM and the KNOX WARRANTY VOID to 0x1.
I know that there is not way to reset the KNOX WARRANTY VOID.
The questions is: When I try do Software Update I get a message that is not possible do Software Update because I have changed my android.
Is still possible change my CURRENT BINARY Custom to Samsung Official? And if it be possible, the Software Update will work?
How can I change my CURRENT BINARY: Custom to Samsung Official?
Thx.
Click to expand...
Click to collapse
you can change it with wanam dont know if it will do Software Updates
Binary custum can be reset by flashing stock
System statzs by wanam exposwd
Knox warranty cant be reset
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
Killberty said:
Binary custum can be reset by flashing stock
System statzs by wanam exposwd
Knox warranty cant be reset
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
Click to expand...
Click to collapse
ALL of this, and my advice, READ a whole lot more before you change stuff on your device.
note 3 current binary: custom
hi
i updated my galaxy note 3 sm-n9005 lte to lollipop using the firmware on sammobile.com
my phone works
but when i try to boot in recovery mode it writes this on the screen:
current binary: custom
system status: custom
knox warranty void: 0x0
how can i bring back my system status and current binary to official?
please help me
farshidnsattari said:
hi
i updated my galaxy note 3 sm-n9005 lte to lollipop using the firmware on sammobile.com
my phone works
but when i try to boot in recovery mode it writes this on the screen:
current binary: custom
system status: custom
knox warranty void: 0x0
how can i bring back my system status and current binary to official?
please help me
Click to expand...
Click to collapse
Wipe cache and dalvik 3 time then reflash the stock lollipop from sammobile and wipe egain!
jemis1983 said:
Wipe cache and dalvik 3 time then reflash the stock lollipop from sammobile and wipe egain!
Click to expand...
Click to collapse
thanks for your message
how can i wipe cache?
since my phone doesnt boot in recovery mode
what is dalvik?
Hello
I have Verizon Note 3 with version 4.3.
In the past I was able to root it with out tripping KNOX. Recently I tried to use ROM Recovery, but then found out that ROM recovery would not work on Verizon variant. In the process I soft bricked the phone. I used Odin to re-install OS. The phone works and I can get to Odin and recovery modes, however, it is not rooted. I tried rooting it again using Odin and Root Dela Vega method, but this time it would fail. I notice that Odin mode displays the following:
ODIN MODE
PRODUCT NAME: SM-N900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A2, P1
WRITE PROTECT: Enabled
It looks like I tripped the KNOX warranty.
I do not often do this kind of stuff, so I do not know exactly how do I root it in this situation. So my questions are:
1. Can the KNOX warranty be reversed back to 0x0? I think there was a post about it, but I could not find it.
2. How do I root the phone now?
Thanks
Knox cannot be reset for the time being.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Wicked Stunts said:
Knox cannot be reset for the time being.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Any ideas about rooting?
suppafreak said:
Hello
I have Verizon Note 3 with version 4.3.
...
Click to expand...
Click to collapse
http://forum.xda-developers.com/verizon-galaxy-note-3
And learn to use the Q/A/Help subforum (there and here).
Moved to Verizon Note 3 Q&A.
Would you please send us root de la vega sm-n900vvrsepl1 galaxy note 3. I can't root the phone
Try this....you will need to unzip it
SOLL365 said:
Would you please send us root de la vega sm-n900vvrsepl1 galaxy note 3. I can't root the phone
Click to expand...
Click to collapse
It is an older version of the Arabic Tool. Worked for me to root only.
https://www.dropbox.com/s/69ecfdtstta67ne/ArabicToolApp.zip?dl=0
Hi guys
I have a i337m from Tigo Colombia and I were looking for a way to install CM11 in it no matter if warranty was voided
In the process I found out that after installing CM11 my knox warranty void still is 0x0. I don't know if this is true for all i337m or I was lucky somehow, anyway here are the steps I made for having CM11:
1. Root with towel root
- Go to www.towelroot.com
- Click the lambda symbol
- Install the apk
- Click "Make it ra1n"
- Now you're rooted. Check looking for SuperSU app and update it
2. Install Recovery: I tried to install CWM from .img with heimdall in Linux and with proper file in Odin in Windows, both cases failed as you can see here [1], looking for answers I end up installing ROM Manager app.
- Install ROM Manager app from Google Play
- Run the app / give root permissions
- Click on install new recovery and select jfltecan (I first installed normal recovery, after donate for get the touch one and support the devs). I selected ClockWorkMod 3.x (the version of CWM installed is 6.0.4.7)
- Reboot to recovery from app and made a Nandroid to starting to mess with the device
Entering to recovery I see: RECOVERY IS NOT SEANDROID ENFORCING
After reboot I see a message in red that says: KERNERL IS NOT SEANDROID ENFORCING
And when I went to download mode I see this:
Code:
Product name: SGH-I227M
Current Binary: Samsung Official
System Status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-Config-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode: enabled
And attached you can find the pictures that probe it
I hope this can help anyone that wants to get custom ROMs on his/her i337M
[1] http://forum.xda-developers.com/galaxy-s4-att/help/s4-i337m-help-installing-custom-recovery-t2887774
Good guide.
I must admit I didn't read the m after your i337 and got slightly excited.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
kirbee213 said:
Good guide.
I must admit I didn't read the m after your i337 and got slightly excited.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry for the false alarm, maybe this works for AT&T variation as well but I need more info from i337M owners to see if this can be considered as a guide or just my particular experience
Will this method work on a Candian Model? Our S4 model is also i337m, anyone from canada tried this? I don't want to trip my know counter cause i just got my phone
fatbuccha said:
Will this method work on a Candian Model? Our S4 model is also i337m, anyone from canada tried this? I don't want to trip my know counter cause i just got my phone
Click to expand...
Click to collapse
I think we import Canadian models so this should work. Anyway I'm wondering if I just have luck or really is a way to achieve flashing custom ROM's without trip the warranty void counter or if our model just don't trigger the counter at all
You can trigger it. I have i337m and my Knox flag is tripped. Custom Roms now tho
Sent from my SGH-I337M using XDA Free mobile app
Psykologikal said:
You can trigger it. I have i337m and my Knox flag is tripped. Custom Roms now tho
Sent from my SGH-I337M using XDA Free mobile app
Click to expand...
Click to collapse
Then I was lucky or this can be a method to avoid trigger the counter. As you see in the pictures of OP, I have CWM, CM11 flashed and 0x0 (Official Samsung software appears there on download mode too).
Hello everybody
This is my first thread here in XDA
I've installed 5.0 Lollipop Beta in my N9005 and it works snappy and fast. I've used this build for 3 or 4 complete cycles of battery and it really works very well. Now i've decided to install TWRP an SuperSU to delete some bloatware and in download mode I can see a new number in my Knox 0x1 counter (see pictures attached).
Anybody can explain to me what does it mean? Really it doesn't matter so much to me cause I've tripped my Knox from day one but I didn't know about this kind of counter
Any thoughts?
(sorry for my english)
Nothing on hard or software. Because you flashed a custom recovery you got 0x1 knox. You no longer have warrenty on your device....
Sent from my SM-N910C using XDA Premium 4 mobile app
TonyM77 said:
Nothing on hard or software. Because you flashed a custom recovery you got 0x1 knox. You no longer have warrenty on your device....
Sent from my SM-N910C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My friend I had 0x1 on JB and KK and now I have 0x1 (2) can you see the diference?
Have you flashed that Lollipop beta with odin and using pit?
I think this is all about new bootloader
I have a 3 there lol, still no warrenty left
Sent from my SM-N910C using XDA Premium 4 mobile app
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
I flashed maybe 25 roms total, had different boatloaders, flashed much baseband etc...
Sent from my SM-N910C using XDA Premium 4 mobile app
Ok I can confirm if you flash a 4 archives KK rom using Odin you "revert" to Knox 0x1
:laugh:
I got the 5.0 TW flashed with odin, used pit and updated bootloader.. I still have 0x1
New flash counter i guess someone alert @Chainfire
I think it's the old "Custom Binary Download" counter that first appeared in the Galaxy S2 (if I'm not wrong). Someone should try Triangle Away to reset that counter. However, 0x1 will still remain active .
Edit: This is what I'm talking about.
Super-Veloce said:
I got the 5.0 TW flashed with odin, used pit and updated bootloader.. I still have 0x1
Click to expand...
Click to collapse
This counter only gets started when you try to root or install recovery with Lollipop bootloader.
ionutzm05 said:
I think it's the old "Custom Binary Download" counter that first appeared in the Galaxy S2 (if I'm not wrong). Someone should try Triangle Away to reset that counter. However, 0x1 will still remain active .
Edit: This is what I'm talking about.
Click to expand...
Click to collapse
I think this is not that kind of counter my friend. I've try to reset it with latest version of Triangle Away and it have broke my system. The only solution is to install and comebak to 4.4.2 again. Please don't try that until @Chainfire gets an answer.
Segamalaga said:
This counter only gets started when you try to root or install recovery with Lollipop bootloader.
Click to expand...
Click to collapse
I have flashed a custom recovery and after that superSU 2.42
I had 0x1 before I flashed 5.0 TW with odin..
And before that I had temasek unofficial cm12 (and before that many other roms)
Super-Veloce said:
I have flashed a custom recovery and after that superSU 2.42
I had 0x1 before I flashed 5.0 TW with odin..
And before that I had temasek unofficial cm12 (and before that many other roms)
Click to expand...
Click to collapse
Please answer this simple question:
In any moment did you installed Lollipop's bootloader?
Did you install the rom with .pit in Odin?
Segamalaga said:
Please answer this simple question:
In any moment did you installed Lollipop's bootloader?
Did you install the rom with .pit in Odin?
Click to expand...
Click to collapse
Yes I used PIT and Yes I updated the lollipop bootloader
This is how I flashed the 5.0 Touchwiz
And you don't have root and recovery, do you?
hi ! any news about (2) knox counter ????
It's a new sort of Knox counter included in new Lollipop's bootloader. Right now you can come back to KK's one and it dissapears.
OK thanks ! I will return to 4.4.2 to see !!! ) Latest 4.4.2 or any 4.4.2 with bootloader ???
amosolidu said:
OK thanks ! I will return to 4.4.2 to see !!! ) Latest 4.4.2 or any 4.4.2 with bootloader ???
Click to expand...
Click to collapse
reflashed 4.4.2 gn2 with bootloader and guess what???? nothing ....still knox warranty 0x1 (2)
You need to flash a 4 archives +pit rom. It worked for me
Segamalaga said:
You need to flash a 4 archives +pit rom. It worked for me
Click to expand...
Click to collapse
it worked now after i format everything from twrp (firmware,modem......) and flash single file firmware (FNG2 I USE ) !!! thanks anyway