So my phone was rooted was on mje ans my co worker accidently updated my phone and now it updated to nc4 firmware is it possible to go back to mje? Thanks sorry I knoe this has been answered but I couldn't find the post
simplyeorange said:
So my phone was rooted was on mje ans my co worker accidently updated my phone and now it updated to nc4 firmware is it possible to go back to mje? Thanks sorry I knoe this has been answered but I couldn't find the post
Click to expand...
Click to collapse
I believe you can flash the stock MJE tar using Odin, which will put your phone into a factory restored state. If you take another upgrade past NC4, there is no way to revert to an earlier build.
http://forum.xda-developers.com/showthread.php?t=2524572
Can someone else please confirm that what I said is accurate?
RylanM said:
I believe you can flash the stock MJE tar using Odin, which will put your phone into a factory restored state. If you take another upgrade past NC4, there is no way to revert to an earlier build.
http://forum.xda-developers.com/showthread.php?t=2524572
Can someone else please confirm that what I said is accurate?
Click to expand...
Click to collapse
YES PLEASE can someone confirm this.
simplyeorange said:
YES PLEASE can someone confirm this.
Click to expand...
Click to collapse
I believe Verizon phones are blocked from downgrading so you can't go backwards. This is assuming you have a retail device. NC4 is still rootable however.
RylanM said:
I believe you can flash the stock MJE tar using Odin, which will put your phone into a factory restored state. If you take another upgrade past NC4, there is no way to revert to an earlier build.
http://forum.xda-developers.com/showthread.php?t=2524572
Can someone else please confirm that what I said is accurate?
Click to expand...
Click to collapse
simplyeorange said:
YES PLEASE can someone confirm this.
Click to expand...
Click to collapse
No... unfortunately, you cannot downgrade back to mje. Verizon put bootloader signature checks in place to prevent downgrading. See Droidstyle's restore guide here: http://forum.xda-developers.com/showthread.php?p=46461911
Scroll down a bit on Section 1 where he explains... "..... If your Retail Locked N3 took the OTA update, you can not revert back to older firmware. Verizon now has Samsung blacklist the older firmwares bootloader after each update. If you try and flash older firmware the device will softbrick."
The good news is... you can use Towelroot to gain root access on 4.4.2 NC4, then use Safestrap v3.75 to run several ROM's that will work on retail / locked bootloader devices. Just don't take any additional OTA'S because there's no current root method for our phone's on 4.4.4.
Can someone who has actually attempted a downgrade (and recalls the details) from a N* - series firmware (NC2/NC4/NK1) to an M*- series firmware (MI9/MJ7/MJE) mention their success or failure?
I am looking at some bootloader behaviors and it would be useful to be able to evaluate as many versions as possible without establishing a new rollback threshold on my device (I'm currently on MJ7. I *think* I can move freely amongst the M-series, but frankly I'm not even positive of that).
Specifically, Droidstyle's thread only says "the OTA", not a specific version. So I'm not sure what he means (without trying to establish the release chronology).
If you are aware of a 2nd-hand report where a XDA contributor attempted a rollback and either failed or succeeded, a URL to that report would be appreciated.
Even if you haven't tried a rollback, you can still be helpful by reporting your "RP SWREV:" flags (on Odin Screen) and bootloader version for bootloader versions that no-one else has provided (yet). Here's mine for MJ7:
(MJ7) RP SWREV: S1, T1, A1, A2, P1
Separately, does anyone have the leak NC2 firmware? (I have everything but that one, it's not on sammobile)
bftb0
RP SWREV
(OF1) RP SWREV: S1, T1, R1, A4, P1
hope this helps!
bftb0 said:
Can someone who has actually attempted a downgrade (and recalls the details) from a N* - series firmware (NC2/NC4/NK1) to an M*- series firmware (MI9/MJ7/MJE) mention their success or failure?
I am looking at some bootloader behaviors and it would be useful to be able to evaluate as many versions as possible without establishing a new rollback threshold on my device (I'm currently on MJ7. I *think* I can move freely amongst the M-series, but frankly I'm not even positive of that).
Specifically, Droidstyle's thread only says "the OTA", not a specific version. So I'm not sure what he means (without trying to establish the release chronology).
If you are aware of a 2nd-hand report where a XDA contributor attempted a rollback and either failed or succeeded, a URL to that report would be appreciated.
Even if you haven't tried a rollback, you can still be helpful by reporting your "RP SWREV:" flags (on Odin Screen) and bootloader version for bootloader versions that no-one else has provided (yet). Here's mine for MJ7:
(MJ7) RP SWREV: S1, T1, A1, A2, P1
Separately, does anyone have the leak NC2 firmware? (I have everything but that one, it's not on sammobile)
bftb0
Click to expand...
Click to collapse
NC4 bootloader
SWREV: S1, T1, A1, A3, P1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N900V using Tapatalk
So far we have:
(MJ7) RP SWREV: S1, T1, A1, A2, P1
(MJE) ??
(NC2) ??
(NC4) RP SWREV: S1, T1, A1, A3, P1 [thanks @donc113]
(NK1) ??
(OB6) ??
(OF1) RP SWREV: S1, T1, R1, A4, P1 [thanks @DisturbedOrange]
If any of you readers are on different firmware revs, please take a moment to report your values (they are on the Odin Download Screen).
I found a prior thread where someone reported being able to downgrade from NC2 to MJE "but not earlier". Perhaps that means the "A3" value first shows up in MJE?
bftb0 said:
So far we have:
(MJ7) RP SWREV: S1, T1, A1, A2, P1
(MJE) ??
(NC2) ??
(NC4) RP SWREV: S1, T1, A1, A3, P1 [thanks @donc113]
(NK1) ??
(OB6) ??
(OF1) RP SWREV: S1, T1, R1, A4, P1 [thanks @DisturbedOrange]
If any of you readers are on different firmware revs, please take a moment to report your values (they are on the Odin Download Screen).
I found a prior thread where someone reported being able to downgrade from NC2 to MJE "but not earlier". Perhaps that means the "A3" value first shows up in MJE?
Click to expand...
Click to collapse
I can almost guarantee you the OF1 flag 3rd from right is A1 not R1
Yes... The 2nd A_flag is what normally stops Odin from back reving.
I distinctly recall reading one of the 'major' developers mentioning something like flag is now A3
Let me see if i can find that thread..
http://forum.xda-developers.com/showthread.php?p=52129142
Close enough...
Sent from my SM-N900V using Tapatalk
donc113 said:
I can almost guarantee you the OF1 flag 3rd from right is A1 not R1
Click to expand...
Click to collapse
I wondered about that myself. The font is quite close between capA and capR... I had some slightly blurry photos I had to squint at closely to tell the difference in my own case.
I'm sure D.O. will chime in.
It would be nice if someone on either NK1 or OB6 could fill in the missing data.
donc113 said:
I can almost guarantee you the OF1 flag 3rd from right is A1 not R1
Click to expand...
Click to collapse
I had to go back and look again to make sure it wasn't a typo.
I took those with a co-workers phone so it isn't the best quality picture but I think it's clear enough to make out
Sent from my SM-N900V using XDA-Developers mobile app
DisturbedOrange said:
I had to go back and look again to make sure it wasn't a typo.
View attachment 3784073View attachment 3784074
I took those with a co-workers phone so it isn't the best quality picture but I think it's clear enough to make out
Click to expand...
Click to collapse
Heh.
I went back and looked at all my pics (see attached). That is indeed an "R" - on mine too. The "A" character in that font has a slightly peaked roof compared to "R".
So... for now I'll assume @donc113's eyes are as bad as mine until he provides a picture proving otherwise.
Code:
(MI9) RP SWREV: S1, T1, R1, A1, P1 (*ref1)
(MJ3) RP SWREV: S1, T1, R1, A1, P1 (*ref2) Developer Edition
(MJ7) RP SWREV: S1, T1, R1, [b][color=red]A2[/color][/b], P1
(MJE) RP SWREV: S1, T1, R1, A2, P1 (*ref3)
(NC2) RP SWREV: S1, T1, R1, A2, P1 [ thanks @darkhawkff - *ref6 ]
(NC4) RP SWREV: S1, T1, R1, [b][color=red]A3[/color][/b], P1 [thanks [user=1923941]@donc113[/user]]
(NJ6) ??
(NK1) RP SWREV: S1, T1, R1, [b][color=red]A4[/color][/b], P1 (*ref4)
(OB6) ??
(OF1) RP SWREV: S1, T1, R1, A4, P1 [ thanks @DisturbedOrange ]
(PL1) RP SWREV: S1, T1, R1, A4, P1 [ thanks @jfalcon - *ref5 ]
If any of you readers are on different firmware revs, please take a moment to report your values (they are on the Odin Download Screen).
In prepping my attached pictures, I realized that something else about the unlocking:
- it appeared to temporarily reset the "System" status (I had a modded ROM on there).
- as expected, the unlocking itself doesn't blow the Knox Warranty flag - but the first time you boot something that is unsigned, it would seem to be permanent from there on out.
There's all sorts of stateful behavior in the bootloader (see the "failed boot" example picture). The watchdog resets when the kernel fails to come up, and the bootloader somehow knows about that on the next hardware reset. So, rather than just attempting boots over and over, it bops into Odin mode.
*ref1: per BeansTown106 and Hobbit19
*ref2: per loadie
*ref3: per fonixmunkee
*ref4: per tendoman
*ref5 per jfalcon
*ref6 per darkhawkff
See pictures (attached).
Related
Good morning, all,
First off, thanks to all the hard-working devs out there who let me make my new wonderful Note 3 an even more enjoyable product. I'm now asking for some assistance, after not concretely finding answers to my questions here on XDA. Hopefully the kindness will be extended!
- Have a new Verizon SM-N900V with build MJE on it.
- Rooted with Kingo
- Disabled KNOX with SuperSU
When the Note 3 boots, I get an unlock icon with the word "Custom" on it. From my Galaxy Nexus 7/Nexus 7 experience, this usually means the bootloader is unlocked. So to check, I boot into download mode and see:
Current binary: Samsung Official
System Status: Custom
Knox kernel lock 0x0
Knox warranty void: 0x0
Qualcomm secureboot: enable (CSB)
RP SWREV: S1, T1, R1, A2, P1
Write protection: Enable
Essentially, my question is this: do I just safestrap now and flash away ROMs? I'm assuming I'd use these instructions to do safestrap: http://forum.xda-developers.com/showthread.php?t=2517610
Or is there another course of action I can take, such as directly flashing a recovery? I'm just a little confused about what my next best course of action would be.
Again, thanks in advance for any insight!
fonixmunkee said:
Good morning, all,
First off, thanks to all the hard-working devs out there who let me make my new wonderful Note 3 an even more enjoyable product. I'm now asking for some assistance, after not concretely finding answers to my questions here on XDA. Hopefully the kindness will be extended!
- Have a new Verizon SM-N900V with build MJE on it.
- Rooted with Kingo
- Disabled KNOX with SuperSU
When the Note 3 boots, I get an unlock icon with the word "Custom" on it. From my Galaxy Nexus 7/Nexus 7 experience, this usually means the bootloader is unlocked. So to check, I boot into download mode and see:
Current binary: Samsung Official
System Status: Custom
Knox kernel lock 0x0
Knox warranty void: 0x0
Qualcomm secureboot: enable (CSB)
RP SWREV: S1, T1, R1, A2, P1
Write protection: Enable
Essentially, my question is this: do I just safestrap now and flash away ROMs? I'm assuming I'd use these instructions to do safestrap: http://forum.xda-developers.com/showthread.php?t=2517610
Or is there another course of action I can take, such as directly flashing a recovery? I'm just a little confused about what my next best course of action would be.
Again, thanks in advance for any insight!
Click to expand...
Click to collapse
Welcome to world of a rooted phone. Since you're on MJE you'd need Safestrap 3.65. Most roms have updated to the NC2 KK leak. It's been advised by Beans and Hashcode to update to it as any further updates may lock us down completely. Safestrap is alittle more than flashing roms in Amonra or Clockwork Mod. It's kind of like dual booting on a computer but it's your phone. The only problem is Hashcode hasn't fully updated the new KK Safestrap for multipe rom slots yet so it will be one at a time for now. Read thru the Safestrap thread and look at a few youtube videos to get a feel for it then once you have the Jellybean version working and you know your way around go here for the KK NC2 leak upgrade.
Link : http://forum.xda-developers.com/showthread.php?t=2740466
Video : http://www.youtube.com/watch?v=KibHLs0l9hs
Don't worry about upgrading as the best part about the leak is if anything goes wrong with your phone we can downgrade back to unrooted MJE for warranty returns, etc. Just take your time, read and follow any videos that may be listed. If my dumb ass can do it anyone can...
fonixmunkee said:
When the Note 3 boots, I get an unlock icon with the word "Custom" on it. From my Galaxy Nexus 7/Nexus 7 experience, this usually means the bootloader is unlocked.
Click to expand...
Click to collapse
Our bootloader is locked. That just appears once you have root, some ppl have gotten rid of it with wanam and xposed if that doesnt work you can use triangle away "Reset Flash Counter" to get rid of the icon
If you are going to upgrade to kitkat DONT take the OTA follow a link on here and get NC2
Thanks everyone! I followed your links, and also used the following videos to:
Safestrap: https://www.youtube.com/watch?v=1C7OKDsfM-Y
Then,
Install Kitkat: https://www.youtube.com/watch?v=KibHLs0l9hs
The videos do a fantastic job explaining what Safestrap was...that was confusing initially for me.
THANKS buttons hit appropriately.
Verizon Galaxy S5 (SMG900vzkw), I bought the phone already rooted from a friend and it was running KitKat (4.4.4). Tried to update it to Lollipop and now I'm not sure what I've actually done. Can someone please walk me through how to get this phone back to its stock configuration? My plan is to just revert back to stock, use OTA updates and then root it back afterwards. I've always had Motorola phones prior to this galaxy and as I've just found out, the entire update/root process is completely different on a Samsung. I tried to flash the stock firmware using Odin last night but without success. I did find these on this thread:
http://forum.xda-developers.com/showthread.php?t=2519544&page=3
I downloaded them but I'm not sure if this is what I need or not. Currently when I plug my phone up to my PC the screen reads:
ODIN MODE
PRODUCT NAME: SM-G900V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK (KK): OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
UDC START
Firmware upgrade encountered an issue. Please use Software Repair Assistant and try again.
I am brand new to this Odin software/process so if could please be very specific on instructions I would really appreciate it. I really hope I haven't ruined this phone. Thanks in advance for any help.
i have the same problem. to get out of Please use Software Repair Assistant download the NK2 kernel and flash it in odin. Still looking for a solution to get it out of softbrike...............
Assuming you haven't already screwed it up already, DON'T DO THIS. You will lock your bootloader on PB1, which is unrecoverable. Go download the latest NCG firmware from SamMobile and use FlashFire to flash a pre-rooted Lollipop ROM. Or CyanogenMod, if you have a 15 chip.
HI,
Im trying to load a stock firmware onto my 32GB N9005 Note 3, but its failing when the flash starts.
I downloaded a HK version of 5.0 ([247616]»˝–«_N9005_N9005ZSUGOL1_÷–π˙œ„∏€(TGY)_5.0.20160317183141.tar) , and it fails at some security check at the start ( Fail(Auth).
Id like to do one of 2 things:
1) Figure out how to fix the security problem so i can load the stock 5.0 on to it
or
2) I also downloaded the stock 4.4.2 , but its not in a tar.... its come in a folder with 6 files.
AP_xxxxxx.tar
BL_xxxxxxx.tar
CP_xxxxxxxx.tar
CSC_xxxxxxxx.tar
HLTE_HKTW_OPEN_16GB.pit
HLTE_HKTW_OPEN_32GB.pit
Can i use odin to flash the 4 files in 1 go to update to the stock version?
The phone was bought from China about a while ago, and its currently running a version of 4.4.4. It looks to me like its running a custom ROM, which was preinstalled from the dodgy place i bought it from, details are below:
Baseband: N9005XXUGNG1
Build Number: DONGCHAO.A429
Kernel Version:
3.4.0-2593013
[email protected] #1
Friday Nov 28 14:31:10 KST 2014
Hardware 1.06
Philz Touch also installed.....
Any help would be greatly appreciated!
Thanks
G
In donwload mode is there reactivation lock: on?
Sent from my GT-N7000
Rosli59564 said:
In donwload mode is there reactivation lock: on?
Sent from my GT-N7000
Click to expand...
Click to collapse
Im not sure how to tell.
When i enter download mode i see:
ODIN MODE
PRODUCT NAME: SM-N900P
CURRENT BINARY : CUSTOM
SYSTEM STATUS: CUSTOM
KNOW WARRANTY VOID: 0x1 (2)
QUALCOMM SECUREBOOT: ENABLE )CSB_
RP SWREV: S1, T1, R1, A3, P1
SECURE DOWNLOAD: ENABLE
UDC START
Its interesting the product name is not matching my expectation. do all sm-n9005 show sm-n900p in download mode?
G
I guess the mb has been changed. It's not n9005 anymore.
http://forum.xda-developers.com/showthread.php?t=3382039
Sent from my GT-N7000
It's not an N9005. It's an N900P therefore download an N900P version of the firmware.
In case anyone wonders in the future what happened with this.... I basically gave up. Something has obviously been reworked on the phone, into a state that i'm pretty unhappy with messing with. I don't need to update it enough to push on, seems like the chances to kill it, or find myself with a phone that no longer supports lte, are too high.
Top tip: When you're buying from China.... you never get what you expect.
G
Rosli59564 said:
In donwload mode is there reactivation lock: on?
Click to expand...
Click to collapse
If lock is on, there is no chance to flash new recovery? I stuck with one phone, buddy of mine gave me some old note3, with samsung account and reactivation on, so I wonder if this is new shiny door holder or I can actually install something?
Did you try installing a stock ROM from sammobile.com? Not sure if flashing an older or newer ROM will make a difference.
Apparently, there are methods to bypass the lock.
MrBl4ckSh33p said:
I have the a problem that I install other TWRP custom rom and now when I turn the phone gets stuck on a screen that says:
Odin mode (written in red letters)
Product Name: Smg360t1
Current binary: Custom
System status: Custom
Fap lock: off
Qualcomm secureboot: Enable (CSB)
rp swrev: s1, t1, h1, r1, a11, p1
Secure download: enable (written in blue letters).
But the android as it should (I guess) does not appear and can not find the way to fix it
I only have 2 days with the phone and then this . I am a newbie on this field so that may explain why I failed. so if you know the answer to my problem, Really I would appreciate that you explain me to how fixed
Can somebody help me? Really I would appreciate the help
Click to expand...
Click to collapse
Thanks everybody for your atention
hello
my device us not working and when going to recovery mode phone screen is show this :-
MMC : mmc_read fail
Movinand Checksum Confirmation Fail
ddi : mmc_read failed
ODIN MODE
PRODUCT NAME : SM-G530H
CURRENT BINARY : Samsung Official
SYSTEM STATUS : Custom
KNOX WARRANTY VOID : 0×1 (0)
QUALCOMM SECUREBOOT ENABLE (CSB)
RP SWREV : S1, T1, H1, R1, A2, P1
SECURE DOWNLOAD : ENABLE
__________________________________________
please help me ???
Thanks
sorry for my English
this screen
Flash the stock rom via Odin.
Noureo said:
Flash the stock rom via Odin.
Click to expand...
Click to collapse
i tried this but it is not working
Mohammed Bhere said:
i tried this but it is not working
Click to expand...
Click to collapse
I don't know then. :/
Visit a customer center maybe?
Noureo said:
I don't know then. :/
Visit a customer center maybe?
Click to expand...
Click to collapse
I will do it
Mohammed Bhere said:
I will do it
Click to expand...
Click to collapse
had the problem too on a note 4. thought it was the usb port. replaced usb port. turned out to be mother board going.