Related
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
phoenix98 said:
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
Click to expand...
Click to collapse
Is not possible for right now, until devs will create a new root app or something like superSU or I don't know ! :crying: Same to me ...
Your Boot loader is probably secured.
Try Root66 image and get back to UVDMD5 Rooted. From there, use Doc Holiday's thread to get 4.3 upgrade.
As it stands, right now if you flashed the official firmware or OTA, you will not be able to Odin flash any previous firmware. Maybe if you were never rooted....
For now though, you shoukd still be able to flash cwm/twrp and flash another rom. you will be limited to the 4.3 modem, but otherwise should be ok to run a 4.1.2 rom.
We are working on it.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
I had the same problem
I just had this same problem and was lucky enough to fix it!!!!
vTizzle said:
I just had this same problem and was lucky enough to fix it!!!!
Click to expand...
Click to collapse
How/ What did you do you fix it? I'm stuck in a rut :l
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
vTizzle said:
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
Click to expand...
Click to collapse
Hm... Interestingly enough it worked! I flashed CWM 6.3.0 though, sent me straight into stock hehe :good::good: Though I'm still curious how long until I can root it
Have you tried the auto root course??
Sent from behind you
Boot recovery, then reboot system. It should ssk if you want to root.
Better yet, flash one of our roms. Or, download the supersu zip file from chainfires thread. (Or in my sig, but its not up to date)
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
There are several ways to root. But if you don't get rid of knox iits almost pointless.
Co-author root didn't work, and nor did Root66
I'm on the same boat
Same here,
Mine was rooted, then
I Updated to Factory 4.3
Same red letters and can't get it back,
I want to 'cause it's unstable and
it has weird partition, "emulated/0"
Any Help Please !!
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
If I did softbrick it, is there anyway to restore it?
You can try first wiping just dalvik and cache, then try factory reset.
Other ROMs
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
Thank you Doc , It has been said ..Over and over and over.. OTA 4.3 update means you cannot flash older firmware again! I was one of the lucky that waited and installed you ROM and it has been stable . I placed a few Mods like Apps For 4.3 TW
For those just refused to READ and have NOT done a OTA update to 4.3 Like DocHoliday77 and and many have said .. here goes one more time..
WARNING!!!
If you have NOT updated via the official firmware or OTA update, it is highly recommended that you do NOT do so at this time!
You can still run these roms and gain every advantage, with none of the problems!
There so many other 4.3 ROMs to play with DocHolidays, Sarahai, mrRobinson and now aamir123. . YOu just to READ before run in head first into the OTA.
I have been trying to keep up with all the 4.3 update stuff but its just so hard with 15 different threads and it being updated everyday. I stupidly updated OTA 4.3 before coming on here and reading and it blows! Samsung is stupid for releasing such a unpolished update. But besides the point, I have been having a problem with out going calls, and battery life. When I will press to call someone the call ends instantly and I have to restart phone for it to allow me to call out. Has anyone else had this problem?
Also, are we any closer to getting 4.3 rooted? I know developers are having problems with Knox etc? If not is there anything I can do to make this update better or do I just have to suck it up? Thanks for the help guys.
I alrdy talked to people at samsung and complained beyond belief, but I dont think the out sourced help desk person understood me.
I made it !!
How ?
1. Uninstall KNOX with Titanium.
2. Flash CWM twice (first one failed), Now I have CWM.
3. Download T999UVDMD5 (Deodexed)
4. Flash it via CWM.
5. Voilà !!
Now It has the partition as it comes from Factory !.
It's there a version similar to this one, running on Android 4.3 (Stock Deodexed, Without KNOX) ?
DocHoliday77 said:
You can try first wiping just dalvik and cache, then try factory reset.
Click to expand...
Click to collapse
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
bentheexo said:
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
Click to expand...
Click to collapse
If you have updated to official 4.3 by any means then don't try to downgrade your boot loader and rom as it may brick device
If you have not taken official update then it depends what is your current boot loader and what rom you are trying to flash
So if you are sure that you haven't gone for official update then you flash dmd5 firmware then try to flash rom
Be sure before doing anything
Sent from my SGH-T999 using Tapatalk
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.
eletendre84 said:
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.
Click to expand...
Click to collapse
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.
mentorkyrom said:
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.
Click to expand...
Click to collapse
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.
eletendre84 said:
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.
Click to expand...
Click to collapse
Tethering is available on CM11 just like it was on 10.2; would strongly recommend latest Philz Touch Recovery over either TWRP or CWM though. Although it is based on CWM, it has proven to be pretty much the superior recovery option for flashing any Android build number, plus it is highly customizable.
Philz Touch Recovery
this is how to downgrade
mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones
smuther22 said:
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones
Click to expand...
Click to collapse
Do you realize that this thread hasn't been used in a couple of months? I would assume the author has no more need of advice based on the inactivity. Also, once Knox is installed, it is on the phone to stay. PERIOD. NO DOWNGRADING POSSIBLE VIA ODIN. Custom ROMs of any build are fine via custom recovery, but any attempt to change the bootloader will trigger Knox and brick the phone. Dangerous info to be posting here, especially since someone else who doesn't know better might try this.
I dropped Illusion and went full unrooted stock for the OTA to 4.3, which was not as awesome as I hoped it would be. So back to root and a custom rom!! Rooted MK4 with ease using kingoroot, used SuperSU to drop KNOX. I think after these steps is where my issues begin. Use goomanager to install twrp, and finally use billard412's wicked awesome "Back to UNROOTED Stock with Auto Flash Count Reset" to get back to MC2 in order to flash a custom rom. I have gotten stuck in a boot loop twice doing this and resolved both with the awesome forums here! The problem was both ROM's i went to (Dirty Unicorns and Smasher X) worked awesomely except for no mobile service on either.
So do I need to go back to MC2 in order to flash a custom ROM or can I go straight from rooted / custom recovery MK4 into a custom ROM. Or is there another flaw in my mechanics? I have seen a bunch of comments on using CWM instead of TWRP, is that my issue? Does CWM work in a similar fashion as TWRP? (I have only ever used TWRP) Thanks for any assistance, and fingers crossed there is not an unseen by me thread on this exact issue!
xysterztia said:
I dropped Illusion and went full unrooted stock for the OTA to 4.3, which was not as awesome as I hoped it would be. So back to root and a custom rom!! Rooted MK4 with ease using kingoroot, used SuperSU to drop KNOX. I think after these steps is where my issues begin. Use goomanager to install twrp, and finally use billard412's wicked awesome "Back to UNROOTED Stock with Auto Flash Count Reset" to get back to MC2 in order to flash a custom rom. I have gotten stuck in a boot loop twice doing this and resolved both with the awesome forums here! The problem was both ROM's i went to (Dirty Unicorns and Smasher X) worked awesomely except for no mobile service on either.
So do I need to go back to MC2 in order to flash a custom ROM or can I go straight from rooted / custom recovery MK4 into a custom ROM. Or is there another flaw in my mechanics? I have seen a bunch of comments on using CWM instead of TWRP, is that my issue? Does CWM work in a similar fashion as TWRP? (I have only ever used TWRP) Thanks for any assistance, and fingers crossed there is not an unseen by me thread on this exact issue!
Click to expand...
Click to collapse
Hey I think I am having a similar issue. I had to root back to stock MC2, take my phone to Sprint, have them reset it. Now I am on MK4 4.3 unrooted. When I tried to root, I got a Samsung message saying that there was an unauthorized app (SU) trying to run and prompted me to update Samsung security policy. What can I do to be rooted again so I can install custom ROMs again. Thanks!
cashdude1971 said:
Hey I think I am having a similar issue. I had to root back to stock MC2, take my phone to Sprint, have them reset it. Now I am on MK4 4.3 unrooted. When I tried to root, I got a Samsung message saying that there was an unauthorized app (SU) trying to run and prompted me to update Samsung security policy. What can I do to be rooted again so I can install custom ROMs again. Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2539227 <-- install SuperSU from play store and then google search Kingo Root, dl kingo root, run kingo root, enable USB debugging, connect, and follow on screen instructions!
Also that unauthorizing app is KNOX and big thanks should go to lorjay589 for posting work around. Also you should read his thread and understand all dangers and voidednous that now potentially comes with rooting.
That was the problem! I wish I would have tried before posting! My issue was either using TWRP or downgrading to MC2, I just tried again using CWM and root on MK4. Dirty Unicorns loaded perfectly and data is running!
Thanks for the tip, that helped me out also
Hello guys!!!
I have a Galaxy Note II N7100 for the past 1 year. I recently installed Hurricane v 8 rom which is based on 4.3 firmware.As I was using it, I realized the RAM was increasing up to 1.3 GB, the only thing that could fix it was to reboot the phone. Later I watched a youtube review of a Note II with an official 4.3 installed and the RAM was about 600 MB on that persons phone. So I went ahead and downloaded a 4.3 firmware N7100DDUEML4 from sammobile.com. After the installation via Odin I boot the phone and it was fine. I read a few articles on how I can root the 4.3 firmware with CF Autoroot and did it as it should be done. After the reboot, Knox blocked the SU and the KNOX flag went to 0x1. After all this I decided to install Philz Recovery via Odin and got access to recovery. My plan was to recover my Hurricane Rom that I previously backed up. After Philz recovery restored the Hurricane Rom, I got stack on Boot Screen. Because Knox is flagged 0x1 I can't install any firmware via Odin anymore. So the next step I did is to restore my phone via Kies. I managed to successfully restore it and now I have a 4.3 firmware N7100XXUEMK9 firmware and Android Status As Enforcing. How can I get root access with this firmware and what should I do with Knox flag 0x1?
Thank you in advance guys!!!
The SafeRoot exploit has been confirmed working for N7100 too (check here), but it can't help to reverse Knox flag 0x1. Try it out. it should work. Anyway, why bother warranty after 12 months?
MichaelVaughn said:
Hello guys!!!
I have a Galaxy Note II N7100 for the past 1 year. I recently installed Hurricane v 8 rom which is based on 4.3 firmware.As I was using it, I realized the RAM was increasing up to 1.3 GB, the only thing that could fix it was to reboot the phone. Later I watched a youtube review of a Note II with an official 4.3 installed and the RAM was about 600 MB on that persons phone. So I went ahead and downloaded a 4.3 firmware N7100DDUEML4 from sammobile.com. After the installation via Odin I boot the phone and it was fine. I read a few articles on how I can root the 4.3 firmware with CF Autoroot and did it as it should be done. After the reboot, Knox blocked the SU and the KNOX flag went to 0x1. After all this I decided to install Philz Recovery via Odin and got access to recovery. My plan was to recover my Hurricane Rom that I previously backed up. After Philz recovery restored the Hurricane Rom, I got stack on Boot Screen. Because Knox is flagged 0x1 I can't install any firmware via Odin anymore. So the next step I did is to restore my phone via Kies. I managed to successfully restore it and now I have a 4.3 firmware N7100XXUEMK9 firmware and Android Status As Enforcing. How can I get root access with this firmware and what should I do with Knox flag 0x1?
Thank you in advance guys!!!
Click to expand...
Click to collapse
xbean said:
The SafeRoot exploit has been confirmed working for N7100 too (check here), but it can't help to reverse Knox flag 0x1. Try it out. it should work. Anyway, why bother warranty after 12 months?
Click to expand...
Click to collapse
Thank you so much for your reply, yeah it is true but it is not that I am worried about the warranty, I want to revert back to a different rom and patch a bootloader so I can install custom firmwares.MJ5 bootloader patch doesn't work for me. Is it possible at this time to patch this MK9 or it is still unsolved issue? Thank you once again for your reply.
I have read a lot of posts & make sure I understand the details before I upgrade to v4.3. The far too many failures for upgrades that I've ever seen prior to v4.3 make me more conscious than ever. I'm on MJ5 bootloader & successfully loaded two different custom ROMs without any problem. I suggest you to do more reading in this forums prior to the upgrade. If you're on bootloader newer than MJ5 then I would suggest to stay with the bootloader & root it with the Safeboot method then clean up the KNOX crap. It should work great after the upgrade, root & clean up. cheers.
MichaelVaughn said:
Thank you so much for your reply, yeah it is true but it is not that I am worried about the warranty, I want to revert back to a different rom and patch a bootloader so I can install custom firmwares.MJ5 bootloader patch doesn't work for me. Is it possible at this time to patch this MK9 or it is still unsolved issue? Thank you once again for your reply.
Click to expand...
Click to collapse
MichaelVaughn said:
Thank you so much for your reply, yeah it is true but it is not that I am worried about the warranty, I want to revert back to a different rom and patch a bootloader so I can install custom firmwares.MJ5 bootloader patch doesn't work for me. Is it possible at this time to patch this MK9 or it is still unsolved issue? Thank you once again for your reply.
Click to expand...
Click to collapse
Try this link it will be helpful to you..
http://forum.xda-developers.com/showpost.php?p=48032704&postcount=4753
:good::good:
I have a stock unrooted SGSIII that received the latest NJ1 firmware. Is there anyway to root this phone or flash a custom recovery?
I am familiar with flashing past Samsung phones, just not with the SGSIII nor facing boot locks.
If there is no current method what is likely to happen if I take the rooted boot and system images from the end of this post and package them into a .tar.md5 to flash with ODIN? Testing things with the boot image is asking for trouble so I would prefer to minimize the risks of bricking (are there viable unbrick procedures in this case?).
Have you tried towel root? Or is your kernel already patched?
crazymonkey05 said:
Have you tried towel root? Or is your kernel already patched?
Click to expand...
Click to collapse
This phone is 100% stock, never rooted, and recieved the latest OTA update a month or so back.
I have root in my stock & recently upgraded NJ1using this: http://forum.xda-developers.com/showthread.php?p=56787105
Odin your favorite recovery and flash SuperSU
Doesn't that procedure require you to be already rooted in a previous firmware to begin with?
As it is, attempting to flash a custom recovery image with Odin returns the error "SW REV CHECK FAIL" and fails.
I just odin TWRP and flashed SuperSU.
I got this phone 15 days ago and not knowing I upgraded to NJ1, so no previous root.
I'll check it again, thanks.
Which TWRP download did you use?
UPDATE: I got this to work by downloading TWRP, Odin, and the Samsung drivers from previous threads. Thanks, developers!