Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
scottrf8 said:
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
Click to expand...
Click to collapse
I don't have a Note (I have the GS3 on TMO). Do you have any idea if the Note 2 has the same issue that the GS3 has, where with the 4.3 update you get a new locked bootloader that prevents you from going back to anything earlier than 4.3? That's the way it is on the GS3. I guess if you were able to actually boot up and make calls after you downgraded back to 4.1.1, then that must not be the case.
In any case, you're getting stuck on the boot logo when you power it on? Can you get into the recovery at all? Do you have the stock recovery or a custom recovery installed? Have you tried clearing cache/dalvik and fixing perms? That often fixes things for me when I'm stuck on the boot logo.
scottrf8 said:
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
Click to expand...
Click to collapse
I start to wonder if people research before doing anything.
To say again. You can't downgrade. You have Knox. You possibly tripped the Knox flag. Reflash the 4.3 stock ROM. If that fails, It's most probably eFuse, if It's 4.3.
(Basically, eFuse messes up your phone aka bricks You phone aka @#%& it up.)
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
---------- Post added 5th January 2014 at 12:05 AM ---------- Previous post was 4th January 2014 at 11:59 PM ----------
mcgrabowski said:
I don't have a Note (I have the GS3 on TMO). Do you have any idea if the Note 2 has the same issue that the GS3 has, where with the 4.3 update you get a new locked bootloader that prevents you from going back to anything earlier than 4.3? That's the way it is on the GS3. I guess if you were able to actually boot up and make calls after you downgraded back to 4.1.1, then that must not be the case.
In any case, you're getting stuck on the boot logo when you power it on? Can you get into the recovery at all? Do you have the stock recovery or a custom recovery installed? Have you tried clearing cache/dalvik and fixing perms? That often fixes things for me when I'm stuck on the boot logo.
Click to expand...
Click to collapse
You're right. The locked bootloader messed those who didn't research about it's life's real bad. 4.3 supposedly has eFuse in it, which FU*CKS your phone. I read it up on the Samsung Knox website, and it said that eFuse "rewrites a read-only part of the phone, resulting in a unusable phone." If u triggered that, it'll be a hard brick, (in my knowledge)
Knox itself is irritating. The Knox Warranty Void counter, which max at 1, is unresetable, (even with JTAG, will brick if h try) so your warranty is *poof*
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
I did a fair amount of research before downgrading. In fact I didn't want to downgrade, but I did want to unlock it. It is unlocked and it's running on 4.1.1. So when you say that you can't downgrade, you mean you shouldn't downgrade cause then you will be stuck with 4.1.1?
scottrf8 said:
I did a fair amount of research before downgrading. In fact I didn't want to downgrade, but I did want to unlock it. It is unlocked and it's running on 4.1.1. So when you say that you can't downgrade, you mean you shouldn't downgrade cause then you will be stuck with 4.1.1?
Click to expand...
Click to collapse
When you were on 4.3, was that an OTA update or an ODIN flash of a stock firmware? Or did you just have a 4.3 ROM from the forums that you loaded (AOSP or rooted stock based ROM with Knox, etc., removed) with TWRP or CWM? Supposedly from what I've been reading if you take the 4.3 OTA or ODIN flash the stock 4.3, the bootloader gets updated, as Irwenzhao mentions above and I've experienced, where you CAN'T downgrade again to 4.1.2 or earlier. I believe that just means you can't go back to a fully stock pre 4.3. I THINK it just means you can't ODIN back to a factory image earlier than 4.3, which is what I experienced. But with TWRP or CWM, I believe I can still load other ROMs at will regardless if they are pre 4.3 or not.
yeah, that sounds kinda like the same thing I have come across. 4.3 was OTA and downgraded to a stock 4.1.1 ROM. Guess this triggers KNOX cause now KNOX WARRANTY VOID is 1. which once that is triggered, you cannot go from a non KNOX version (4.1.1) to a version that has KNOX. My question now is does that apply to just the stock firmware? Would ANY of the ROM's created by the devs work?
There were some posts in the unlock thread that people were able to go from 4.1.1 (after downgrading) back up to 4.3. Just trying to figure out how that would be the case? Could the knox warranty flag not have been set for them?
scottrf8 said:
yeah, that sounds kinda like the same thing I have come across. 4.3 was OTA and downgraded to a stock 4.1.1 ROM. Guess this triggers KNOX cause now KNOX WARRANTY VOID is 1. which once that is triggered, you cannot go from a non KNOX version (4.1.1) to a version that has KNOX. My question now is does that apply to just the stock firmware? Would ANY of the ROM's created by the devs work?
There were some posts in the unlock thread that people were able to go from 4.1.1 (after downgrading) back up to 4.3. Just trying to figure out how that would be the case? Could the knox warranty flag not have been set for them?
Click to expand...
Click to collapse
Just to make it clear, Knox is a bootloader, which means u can flash anything that's not a bootloader, but your warranty would be history. Flashing anything trips the flag, even 4.1.1/2 stock ROMs.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
Truthfully, that doesn't clear it up. Do the stock firmware through Kies or ota include a bootloader and that's why it won't install? Thanks
Flashing the stock firmware through kies, ODIN, or the OTA update will update the boot loader as far as I know and will ruin any chance of returning to stock and void your warranty. As long as you don't want to do that, I don't think it's too big of a deal.
At this point, I couldn't care less about the warranty. I would think it's expired now anyhow. As long as I can flash ROMs and boy the phone up and use it. I'm happy.
Sent from my SGH-T999 using xda app-developers app
Related
I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help." Then thats where i couldn't do anyting with my phone but go to download/ODIN MODE and rebooting system thing where you can reboot system. IM very new and i don't know much about rooting and the meanings of a lot of words like unlock bootloader. If i go to ODIN MODE it says
ODINE MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: Yes (1 Counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER RP SWREV:1
i think this doesn't look good. WHat should i do to make my phone be working again and not showing that black screen.
I already wiped all data and tried to do that StockROm thing on my computer ODIN and still nothing.
Is my bootloader locked? if so do i need to unlock it to make my phone work again? Thanks so much for your time
Same with mine I think it's called a bricked phone and think there is nothing we can do about it, hopefully someone has a solution
Might Work?
Remeax said:
I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help." Then thats where i couldn't do anyting with my phone but go to download/ODIN MODE and rebooting system thing where you can reboot system. IM very new and i don't know much about rooting and the meanings of a lot of words like unlock bootloader. If i go to ODIN MODE it says
ODINE MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: Yes (1 Counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER RP SWREV:1
i think this doesn't look good. WHat should i do to make my phone be working again and not showing that black screen.
I already wiped all data and tried to do that StockROm thing on my computer ODIN and still nothing.
Is my bootloader locked? if so do i need to unlock it to make my phone work again? Thanks so much for your time
Click to expand...
Click to collapse
I dunno if this will work for you. But I had the same message and when I booted in Download mode I just hit Cancel then rebooted and it worked?
If you flashed cyanogenmod, that means you're bootloader is unlocked, which is a good thing.
Can you get into CWM or TWRP? I don't have a samsung so i don't know about ODIN (i presume it's like flashtools for Xperia).
For as long as your phone vibrates (or does pretty much anything when you boot it up) your phone is not hardbricked, which is also good .
Try getting into CWM, shut down your phone completely, wait 5 seconds, then do: Volume Down + Home + Power key . This will get you into bootloader state and try reflashing your old backup, a stock rom or cyanogenmod.
First time with these softbricks is always the most fun ^^. Been there done that, i thought i spend 250 euro's on a phone that was broken .
Btw. Always make a backup for these kind of situations.
Remeax said:
I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help."...
Click to expand...
Click to collapse
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.
Ok how do i get it?
afextwin said:
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.
Click to expand...
Click to collapse
Ok so is do i do the same thing as i was trying to flash or something like grab a kies file( the ones that take 2+ hours to download) and then flash or get to factory reset with the 4.3 file? if so do you know where i can grab a 4.3 update file to restore? please help me if you have skype or PM me? thanks
afextwin said:
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.
Click to expand...
Click to collapse
I just recently ODIN flashed the latest 4.3 stock firmware for my TMO GS3 and then attempted to roll back to 4.1.2. It didn't brick my device, but it didn't work either. I would simply fail to install. I was able to reflash, through ODIN, the 4.3 stock firmware (actually used the root66 version). Then I was able to ODIN flash CWM recovery and install Dandroid 5.1, which is also a 4.3 based ROM. All is well now. I guess I simply can't go back to any previous 4.3 ROMs now, and I'm not sure about any AOSP ROMs. I may give a try at some point to see.
There are users here in Canada with Note 3's that have "Custom" in "Current Bianary" and "System Status".
This information has not been posted, I have NO idea why. I am guessing these people could care less about us (the people still in the dark).
I have only just obtained a Note 3 (Week ago) and I am trying to figure this stuff out.
We have a special Note 3 in our N900W8's. Apparently we can:
- Downgrade from 4.4.2 to 4.3 via Odin 3.09 without tripping Knox (not sure if this requires the Mexican bootloader first or if we can do it with our Canadian bootloaders)
- Keep Knox at 0x0 with Custom Everything else. From what I see, our bootloaders are unlocked allowing us to flash our phones in Odin with multiple files (not 1 file mode as this contains a bootloader) as long as we dont include the bootloader (theory from what I have seen, and read a few times, no confirmation).
However I can not get an answer out of anyone who knows anything. I cannot just blindly flash and see if Knox is tripped, I'll only get one shot. Not worth it IMO.
Can anyone chime in on this? Is it acceptable to call members out? I know exactly who the 2 people are that have Custom everything and Knox at 0x0. 2 Torontonians, younger guys, doesn't seem like they want to talk though. Can I call them in here, is that acceptable behavior? Never done that before. Hehe.
I can confirm. I used this method:
http://forum.xda-developers.com/showthread.php?t=2614772
I have a Rogers Note 3 with CWM installed and rooted with Knox at 0x0. My friend just updated his Note 3 to kit Kat (through kies) and rooted using cf-autoroot and his knox is 0x0. I haven't tried downgrading so I cannot comment on that.
I am planning to flash the official Rogers rom shortly and then root (not sure about installing a custom recovery yet) I will report back when completed.
I PM'd you but yeah, I'm Knox 0x0 on X-Note 12 right now. Sorry about that, wasn't home.
kiru said:
I can confirm. I used this method:
http://forum.xda-developers.com/showthread.php?t=2614772
I have a Rogers Note 3 with CWM installed and rooted with Knox at 0x0. My friend just updated his Note 3 to kit Kat (through kies) and rooted using cf-autoroot and his knox is 0x0. I haven't tried downgrading so I cannot comment on that.
I am planning to flash the official Rogers rom shortly and then root (not sure about installing a custom recovery yet) I will report back when completed.
Click to expand...
Click to collapse
That link notes that installing a custom recovery will trip knox. Could you please verify what you did to install custom recovery and still maintain knox 0x0? Will be very interested in your follow-up.
kiru said:
I can confirm. I used this method:
http://forum.xda-developers.com/showthread.php?t=2614772
I have a Rogers Note 3 with CWM installed and rooted with Knox at 0x0. My friend just updated his Note 3 to kit Kat (through kies) and rooted using cf-autoroot and his knox is 0x0. I haven't tried downgrading so I cannot comment on that.
I am planning to flash the official Rogers rom shortly and then root (not sure about installing a custom recovery yet) I will report back when completed.
Click to expand...
Click to collapse
Could you also PM me the procedure? Knox is really bugging me and TW is bloated with too many craps. X-Note looks awesome! Thanks !
bingbinghaha said:
Could you also PM me the procedure? Knox is really bugging me and TW is bloated with too many craps. X-Note looks awesome! Thanks !
Click to expand...
Click to collapse
Actually, I would be interested too. Any chance of posting the procedue instead of PM to multiple users? If not, please PM me as well
I followed the guide in the link I posted as it is pretty detailed already. I have root and cwm recovery installed with Knox at 0x0.
kiru said:
I followed the guide in the link I posted as it is pretty detailed already. I have root and cwm recovery installed with Knox at 0x0.
Click to expand...
Click to collapse
Second that.
---------- Post added at 12:55 AM ---------- Previous post was at 12:38 AM ----------
Okay here. https://www.youtube.com/watch?v=Tks73wZH3qg&list=UU2FLZg9YNAr4YAd0VEDDKGQ
You have to pause to see it at the beginning, and in hindsight, I probably have should of started in CWM, then booted into recovery, but whatever.
Set it to HD and pause it at the beginning, you can see my Knox 0x0. Then watch the video and I boot into the ROM, then back into CWM, all in one cut.
Cheers.
Same here
Knox 0x0 here, after a few good reasons to trip it
Android newcomer here.
I have a Bell Canada SM-N900W8, and it came with 4.3. Rooted 4.3 with Kingo (noob style) and that was just perfect to start out. Then the OTA came out. I unrooted the device, reseted with Kies 3 update to 4.4.2 and then Kingo wasn't working anymore of course.
At that point I decided I didn't care about tripping knox and installed TWRP to start trying roms... Tried like 2-3 1+gb complete packed roms (bootloops, probably cauz im a noob) then I wiped from TWRP, restored my OTA backup, flashed with CF-Auto-Root international version (canadian is another bootloop) and then flashed a CivZ kernel +stock-modification rom that I now simply keep clean with Titanium Backup and some apps y'all know about.
Some more info :
My version is VLUCNB7
My current kernel [email protected]
My current SE state is Permissive
Again, Knox is 0x0. Even after bootloops of custom crap that was crashing and I'm custom-rom, custom-kernel.
Two facts to finish that off
1) That's weird
2) I'm a lucky *****
Have a great day
What if I want to use a custom 4.3 ROM (just to get BT Tethering) without tripping KNOX?
The guides seems to push you to install the 4.4 ROMs.
I have the Bell version of N900W8.
Started at MI5, rooted de la vega, then wanted to upgrade to 4.4.2.
Used polishpats way of upgrading with the leaked 4.4.2, flashed all the AP,CSC,CP,PIT, then installed TWRP and autorooted, both with Odin 3.09 - no knox trip
Wanted to try X-note, installed it using TWRP, and no knox trip
Upgraded the kernel using TWRP, no knox trip
Did not like X-note, wanted to go back to 4.4.2, and reflashed it - no knox trip
Downgraded back to 4.3, no knox trip
upgraded to offical 4.4.2, no knox trip
rooted via chainfire and odin - no knox trip
now sitting at rooted 4.4.2 with 0x0 still
Are you basically saying Bell's N900W8 is KNOX untripable?
I'm on MJ4 (UDLV Rooted) with remaining with MJ1 Bootloader
Since I don't want a KITKAT rom, can I just install a custom recovery (TWRP) without doing all that Mexican instruction stuff?
I really just want a 4.3 ROM with BT Tethering.
klau1 said:
Are you basically saying Bell's N900W8 is KNOX untripable?
I'm on MJ4 (UDLV Rooted) with remaining with MJ1 Bootloader
Since I don't want a KITKAT rom, can I just install a custom recovery (TWRP) without doing all that Mexican instruction stuff?
I really just want a 4.3 ROM with BT Tethering.
Click to expand...
Click to collapse
Hello,
My friend has just the same phone as me, he bought it a few weeks before me, and he used his own techniques and got 0x1 knox tripped, so I just can't warn you enough : not all N900W8 are "untrippable"
...but...I didn't trip mine and I'm not alone.
Without more information you can't just say canadian w8's are untrippable, cauz they are.
Well, are older the better?
I got mine the first week it came out.
klau1 said:
Well, are older the better?
I got mine the first week it came out.
Click to expand...
Click to collapse
I doubt it.
Will look into this. I am positive all N900W8's are the same.
Surely your friend missed something or did something improperly to trip Knox.
Taking this all in. Thanks for the posts guys!
@nexxusty
in your opinion, do you have to go thru installing KITKAT rom from Mexico if you just want to install another 4.3 ROM that has BT Tethering without tripping KNOX?
klau1 said:
@nexxusty
in your opinion, do you have to go thru installing KITKAT rom from Mexico if you just want to install another 4.3 ROM that has BT Tethering without tripping KNOX?
Click to expand...
Click to collapse
Klau you took the question right out of my head brother. LOL.
I am not sure... this also pains me as I want to try CF-auto Root right now on 4.4.2 Rogers.
From my knowledge of technology, I dont think it will. Not positive though. I am hoping you do not need to flash this.
I will test for us. Here is hoping I wont lose my warranty. Will report back.
nexxusty said:
Klau you took the question right out of my head brother. LOL.
I am not sure... this also pains me as I want to try CF-auto Root right now on 4.4.2 Rogers.
From my knowledge of technology, I dont think it will. Not positive though. I am hoping you do not need to flash this.
I will test for us. Here is hoping I wont lose my warranty. Will report back.
Click to expand...
Click to collapse
Flashed CF-Auto-Root, flashed TWRP 2.6.3.0, 0x0 still!
Now for the info on my phone.
I have done as follows.
Phone came with 4.3 stock --> Root De La Vega --> Flashed 4.4.2 Stock (Rogers) with Odin 3.09 --> CF Auto-Root --> TWRP 2.6.3.0 = Rooted 4.4.2 with TWRP 2.6.3.0 Recovery and Knox @ 0x0.
I'm not stopping here. Will flash everything DrawntoLife has.
Appreciated my man. Thanks again! Easy to Follow Step By Step Tutorial **WILL** be written tonight after I am done at a LAN I am already late for figuring this out.
Talk soon everyone! Happy flashing!
did you consider extracting the ODIN package and leave out the Bootloader?
Remember we had to do that upgrading from MJ1 to MJ4. Reportedly, it was the newer bootloaders that trip KNOX.
klau1 said:
did you consider extracting the ODIN package and leave out the Bootloader?
Remember we had to do that upgrading from MJ1 to MJ4. Reportedly, it was the newer bootloaders that trip KNOX.
Click to expand...
Click to collapse
When I updated to 4.4.2? I did, but I was not sure if that would trip Knox so I left it in the package.
It's irrelevant now anyway, the bootloader in 4.4.2 Rogers is the one I am on now and allowing me to do all this still.
I suggest you update to it. Use the package labeled "N900W8VLUCNB7_N900W8OYACNB7_RWC". That is 4.4.2 for a Rogers Note 3.
I can safely assume you can flash this at any point and be fine. Even if you are already on a hacked 4.4.2 or something. There would be no issue updating the bootloader to the same version, would just overwrite it.
hey rooters and devs is there a stable 4.4.2 root out right now for verzion without tripping knox?
i took the update to 4.4.2 and i cant even touch mu phone since it sucks makes random noises like a dot when clicking something.
Also, when will be able to start flashing custom roms or 4.4.2. i bricked my phone like 3 times since i didnt unlock the boot loader but now i can actually flash the roms.
TL,DR root for 4.4.2 without tripping know
when will we be able to flash cyanogenmod
broazny said:
hey rooters and devs is there a stable 4.4.2 root out right now for verzion without tripping knox?
i took the update to 4.4.2 and i cant even touch mu phone since it sucks makes random noises like a dot when clicking something.
Also, when will be able to start flashing custom roms or 4.4.2. i bricked my phone like 3 times since i didnt unlock the boot loader but now i can actually flash the roms.
TL,DR root for 4.4.2 without tripping know
when will we be able to flash cyanogenmod
Click to expand...
Click to collapse
The only root exploit for VRUDNE1 4.4.2 that works on our phone is "Towelroot" by Geohot which is in the S5 section.
Once rooted, these things apply to everyone on VRUDNE1 4.4.2 as well as anyone on 4.3 VRUCML1 or VRUCNC1 OTAs:
a) You can NOT install a custom recovery (No CWM, No TWRP, nothing)
b) You can NOT install any AOSP rom
c) You can NOT install a custom kernel
d) Only an unofficial version of Safestrap can be used on VRUDNE1. This is not a custom recovery, Safestrap is NOT a custom recovery.
e) As of 8:50 EST, there is no custom VRUDNE1 TouchWiz rom to install. Safestrap hijacks the bootprocess and only uses the stock kernel, in your case stock VRUDNE1 4.4.2 kernel, in order to boot other custom TouchWiz roms. Only VRUDNE1 roms would be able to successfully flash on your phone. But none exist yet.
Literally all that you can do as of this post is root, debloat, install Safestrap, and hope that you will be able to use custom VRUDNE1 based TouchWiz roms.
back to 4.3
will i be able to odin back to 4.3 without tripping knox and locking the bootloader?
SlimSnoopOS said:
The only root exploit for VRUDNE1 4.4.2 that works on our phone is "Towelroot" by Geohot which is in the S5 section.
Once rooted, these things apply to everyone on VRUDNE1 4.4.2 as well as anyone on 4.3 VRUCML1 or VRUCNC1 OTAs:
a) You can NOT install a custom recovery (No CWM, No TWRP, nothing)
b) You can NOT install any AOSP rom
c) You can NOT install a custom kernel
d) Only an unofficial version of Safestrap can be used on VRUDNE1. This is not a custom recovery, Safestrap is NOT a custom recovery.
e) As of 8:50 EST, there is no custom VRUDNE1 TouchWiz rom to install. Safestrap hijacks the bootprocess and only uses the stock kernel, in your case stock VRUDNE1 4.4.2 kernel, in order to boot other custom TouchWiz roms. Only VRUDNE1 roms would be able to successfully flash on your phone. But none exist yet.
Literally all that you can do as of this post is root, debloat, install Safestrap, and hope that you will be able to use custom VRUDNE1 based TouchWiz roms.
Click to expand...
Click to collapse
broazny said:
will i be able to odin back to 4.3 without tripping knox and locking the bootloader?
Click to expand...
Click to collapse
No, you can not downgrade once on 4.4.2 VRUDNE1.
thank you very much, do you know when the devs will be able to find a way to downgrade or unlock the bootloader
SlimSnoopOS said:
No, you can not downgrade once on 4.4.2 VRUDNE1.
Click to expand...
Click to collapse
broazny said:
thank you very much, do you know when the devs will be able to find a way to downgrade or unlock the bootloader
Click to expand...
Click to collapse
I'll be blunt with you, I sincerely doubt that's being actively worked on for our 2 year old device. The bootloader has yet to be unlocked on the S4 which has had an active bounty with numerous devs so its not happening here. If AOSP means that much to you, sell your S3 for a bootloader unlocked S3 or get another device which has less hurdles to get AOSP.
Edit: Or you can email these guys at MobileTechVideos and see if their S3 bootloader downgrade process works on 4.4.2. It is a paid service either way, but some people have considered this when on 4.3.
SlimSnoopOS said:
I'll be blunt with you, I sincerely doubt that's being actively worked on for our 2 year old device. The bootloader has yet to be unlocked on the S4 which has had an active bounty with numerous devs so its not happening here. If AOSP means that much to you, sell your S3 for a bootloader unlocked S3 or get another device which has less hurdles to get AOSP.
Edit: Or you can email these guys at MobileTechVideos and see if their S3 bootloader downgrade process works on 4.4.2. It is a paid service either way, but some people have considered this when on 4.3.
Click to expand...
Click to collapse
Is there any successes to this downgrade of the bootloader of the link that you sent? I'm not on a s4 I'm on a SCH-I535 sgs3 same as s4 if I'm correct.. Correct me if I'm wrong s4 and s3 have a lot of the same stuff
jcbjoe said:
Is there any successes to this downgrade of the bootloader of the link that you sent? I'm not on a s4 I'm on a SCH-I535 sgs3 same as s4 if I'm correct.. Correct me if I'm wrong s4 and s3 have a lot of the same stuff
Click to expand...
Click to collapse
I haven't seen anyone report back on having used this. I figured someone would have done so and posted on xda but, nothing. That link is for the Verizon S3 btw. The S4 was mentioned just for comparison purposes only.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
I haven't seen anyone report back on having used this. I figured someone would have done so and posted on xda but, nothing. That link is for the Verizon S3 btw. The S4 was mentioned just for comparison purposes only.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I originally saw it on XDA. Josh inadvertently reverted one while doing a JTag service. He was able to reproduce it several times in testing. Most don't even know about it till they brick their device and need JTag service.
Hello, my roommate has a Verizon Galaxy S3. He recently took the 4.4 update, and it apparently screwed up his phone pretty bad. He gets terrible battery life and force closes and freezing. He came into my room knowing that I'm an android nerd and he asked me to root and rom his phone. Cool.
So, now I'm trying to catch up on the current state of the GS3.
He has never rooted or installed recovery. I was under the impression that the Verizon GS3 had an unlocked bootloader, but now I'm reading that the bootloader might be locked since he updated?
1: Is it possible to ODIN back to an earlier version and then unlock his bootloader?
2: What's JTAG?
3: Is there an easy way to install recovery on 4.4 that I'm missing?
Any links or advice you guys could give me would be really helpful... I'm currently reading and jumping between links, but It's hard to figure out where the phone currently stands with all the conflicting information out there and the new update that just pushed.
9kracing said:
Hello, my roommate has a Verizon Galaxy S3. He recently took the 4.4 update, and it apparently screwed up his phone pretty bad. He gets terrible battery life and force closes and freezing. He came into my room knowing that I'm an android nerd and he asked me to root and rom his phone. Cool.
So, now I'm trying to catch up on the current state of the GS3.
He has never rooted or installed recovery. I was under the impression that the Verizon GS3 had an unlocked bootloader, but now I'm reading that the bootloader might be locked since he updated?
1: Is it possible to ODIN back to an earlier version and then unlock his bootloader?
2: What's JTAG?
3: Is there an easy way to install recovery on 4.4 that I'm missing?
Any links or advice you guys could give me would be really helpful... I'm currently reading and jumping between links, but It's hard to figure out where the phone currently stands with all the conflicting information out there and the new update that just pushed.
Click to expand...
Click to collapse
1: No, it is not possible to ODIN back to unlock the bootloader. Your friend is stuck on 4.4.2.
2: JTAG is a service you can send your phone off for and pay for to unbrick a hard bricked phone. As long as you or your friend do not hard brick his phone, you won't need a JTAG.
3: You cannot install any kind of standard recovery on 4.3.1 or 4.4.2 on the Verizon Galaxy S3. There is an unofficial safestrap you may be able to use on 4.4.2 found here -> http://forum.xda-developers.com/showthread.php?t=2797314 But there are no ROMs to flash using safestrap, so for the moment it is kind of pointless.
There really isn't conflicting information in these threads unless you are looking at old, outdated threads on rooting. All of the information anyone needs to know about the current state of the Verizon Galaxy S3 can be found in just a few threads:
http://forum.xda-developers.com/showthread.php?t=2575661
http://forum.xda-developers.com/showthread.php?t=2653030
http://forum.xda-developers.com/showthread.php?t=2784249
http://forum.xda-developers.com/showthread.php?t=2639337
Owned by Landshark AGAIN!
Sent from my SCH-I535 using Tapatalk
Hi,
I've one (big) problem that I can't fix.
I've been using Android 5.0.1 for more than 1 year as I didn't want to upgrade (it worked pretty well) and because I had the S6 rooted with PingPong root.
However, one month ago it started to run slowly, crashing apps, ... so I decided that, as I wanted to wipe the device, why not upgrade to MM (6.0.1)??, so I did.
I did a backup of all my data and EFS folder and downloaded a 6.0.1 ROM to flash it with ODIN. Everything went OK and finished flashing the rom, but when the S6 restarted it showed this in the recovery:
'dm-verity verificztion failed...
Need to check DRK first...'
And I cant boot.
I've tried some tips that are here and in other websites:
- I've flashed stock rom again
- I've flashed a stock rom without cache.img file.
- I Can't flash some files as I've R/L ON. (I've been trying to disable it for many months but I couldn't).
But the S6 doesn't boot...
Thank you!
What worked for me.
So this is my current issue, but i was able to resolve the issue you are having. so what i did was get the 5.1X OK7 (My phone is Verizon) firmware and flashed through ODIN 3.12.5, this flashed stock 5.1.1 in my phone and it worked good. however i have issue with my phone random restarts and power button not working in recovery or in rom. however i can go in and out of downloading mode or maintenance mode.
Critical_DoubleShot said:
So this is my current issue, but i was able to resolve the issue you are having. so what i did was get the 5.1X OK7 (My phone is Verizon) firmware and flashed through ODIN 3.12.5, this flashed stock 5.1.1 in my phone and it worked good. however i have issue with my phone random restarts and power button not working in recovery or in rom. however i can go in and out of downloading mode or maintenance mode.
Click to expand...
Click to collapse
Thanks for your reply!
I tried to downgrade to 5.1.1 or 5.0.1 but I get an error.
(SW REV CHECK FAIL DEVICE 2 BINARY 1)
That happens when you don't have the right firmware you have.
You CANNOT downgrade to 5.1 or 5.0 since you are on 6.0. The bootloaders refuses to be overwritten.
Critical_DoubleShot said:
That happens when you don't have the right firmware you have.
Click to expand...
Click to collapse
I'm trying to flash another 6.0.1 ROM (a bit older), but I get 'CHECK FAIL. DEVICE: 4, BINARY:3'
I've read that DRK problems are related with EFS files, so... Can I restore EFS folder (I've a backup from Android 5.0.1) to solve?? I don't know how to restore it without booting into the sistem (and without custom recovery)
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
brenner650 said:
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
Click to expand...
Click to collapse
Thank you for your reply!!
I had the device rooted, but with PingPong root, so Knox is still 0. However it shows that the system is "custom".
I'll try the warranty, they may not notice the "custom", just the knox.
I'm with the same problem when trying to flash stock BTU QA7..and only if i flashing cf_root my phone is booting.
Any idea? I don't care about the Knox..
Sent from my SM-G920F using Tapatalk
orbgel10 said:
I'm with the same problem when trying to flash stock BTU QA7..and only if i flashing cf_root my phone is booting.
Any idea? I don't care about the Knox..
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
If you are talking about DRK, the only way to fix it that I know of, other than hw replacement, is via 3rd party professional repair tool. (Octopus/Octoplus box)
If DRK is ok, phone boots normaly, if it is messed up, the only way of booting is with custom kernel which bypass DRK check.
You can check it in recovery, if messed up it will say DM verity failed on bottom of the screen.
Ok, i send my phone to fix, i will tell you what happened.
Sent from my Redmi 3S using Tapatalk
brenner650 said:
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
Click to expand...
Click to collapse
Thanks for your reply!!.
I took my S6 (925F) to a Samsung service center as you said. However, they told me that my S/N was incorrect (I bought a second-hand S6 edge, I think someone changed it) so they couldn't fix it.
Now I'm trying to use SmartSwitch to do a factory reset but it asks me for the S/N and I don't have the original one, just a S/N from a non edge S6 (920F). How can I do the factory reset without my S/N??? Can I use the serial number from another 925F??
Now I'm trying to find an engineering bootloader, to bypass the R/L and flash CF-AutoRoot, custom recovery.... but I only find it for 5.0.1 or... for galaxy S6 G925T, not F.
Finally, I managed to fix my S6 by myself!! (not really, but at least it boots...)
This is what I did:
- I found a factory binary for my S6 so I flashed it via ODIN
- I flashed a 6.0.1 ROM without hidden and without cache
Then it boots without any problems. However, now I can't get into recovery
I hope this will help someone