I'm no on android 4.3.1 liquidsmooth custom rom and I need to downgrade back to android 4.1, but I can't without bricking my device apparently because of Samsung Knox. Therefore I'm asking if I can flash another 4.3 rom without knox on my i747m s3 that will allow me to downgrade.
NOte: I need to downgrade because I'm getting very weak wifi reception, I want to see if downgrading back to the stock rom will change anything, any otehr suggestions for tackling this issue would be appreciated, thank you.
Simax8 said:
I'm no on android 4.3.1 liquidsmooth custom rom and I need to downgrade back to android 4.1, but I can't without bricking my device apparently because of Samsung Knox. Therefore I'm asking if I can flash another 4.3 rom without knox on my i747m s3 that will allow me to downgrade.
NOte: I need to downgrade because I'm getting very weak wifi reception, I want to see if downgrading back to the stock rom will change anything, any otehr suggestions for tackling this issue would be appreciated, thank you.
Click to expand...
Click to collapse
hello,
simply flash kriEv's knox-free, pre-rooted stock ROM --> http://forum.xda-developers.com/showthread.php?t=2558311
you may still run into trouble if you try to flash anything based below 4.3.. I would just bite the bullet and upgrade to 442, maybe slimkat or cm11
Related
Hi,
I have a Verizon Galaxy Note II I605 running Android 4.1.1 that I had originally rooted via Odin and followed instructions on the galaxynote2root website last Jan/Feb in 2012
I would like to upgrade to a stock ROM of 4.3 and keep root and was hoping someone could point me in the right direction in regards to which ROM to use and the steps to do so. I really only use root for the wifi tether and would like to keep the phone as close to stock as possible. I've gone through a number of different forums and posts but can't seem to find some good instructions with a corresponding recommendation on an Official OTA 4.3 ROM to use. I've found a lot variations on 4.3 ROMs, but most of them have gutted a lot of things or discussing having to flash firmware which makes me nervous.
Also, is it true I may be forced to take the OTA in the near future and potentially soft brick my phone if I don't either revert back to stock or install a 4.3 ROM which disables the update app. I'm not sure if the ROM i'm currently running has this disabled or not.
Thanks in advance for any help,
eugenikz
Beanstown or sophisticated rom will be the official stock 4.3, however your gonna have to flash the Official MJ9 firmware via Odin. You could take the OTA but the bootloader will be locked afterwards. There is root available with the OTA stock but you won't be able to load a custom recovery therefore no more custom roms.
+1. I did this with my note2. Was the same as yours. I'm now on sophisticated 2.0 highly recommended. I also updated recovery to Phils, which seems to be the conventional wisdom for flashing 4.3.
Sent from my SCH-I605 using xda app-developers app
Hi!
As stated above, I tried updating to the Kit Kat Release for Portugal's I9205 from an asian I9205. Testing out the device, mobile data won't activate and gives me a "Please Insert SIM" error. Because of this, I wanted to roll back to 4.2.2 but seem to be encountering an error in ODIN, primarily one that says "Check Fail Fused 2 > Binary 1".
My question is, how would I be able to revert to 4.2.2? Any help would be appreciated.
Thanks!
Unfortunately, upgrading to KK is one way road... after installing KK there is not possible to downgrade because of new bootloader and efuse in kernel. If you want to go back to good old 4.2.2 let flash MegaFireV10 ROM from @ megalomanic14 which is greatly improved stock 4.2.2 and is already rooted. I could be flashed onto KK without consequences. Simple flashing back stock 4.2.2 could make your phone brick.
Oh, so there's no way for me to roll back? That sucks!
If I flash a new custom ROM, like LiquidSmooth, would my ability to use my mobile data be restored? What's affecting it at any rate? The Modem? Is there anything I could flash that could help?
Would restoring it via KIES work?
trurl3 said:
Unfortunately, upgrading to KK is one way road... after installing KK there is not possible to downgrade because of new bootloader and efuse in kernel. If you want to go back to good old 4.2.2 let flash MegaFireV10 ROM from @ megalomanic14 which is greatly improved stock 4.2.2 and is already rooted. I could be flashed onto KK without consequences. Simple flashing back stock 4.2.2 could make your phone brick.
Click to expand...
Click to collapse
trul3 is giving good advice!!! flash the Megafire v10 rom..it looks and feels like the stock 4.2.2 rom with a few extra apps on it..
You'll be pleased and just May get your mobile data restored!
good luck
I did a Nandroid backup and restored that after trying NE4. The only change is the baseband is now NE4 but I am back on MH2. Is this not normal?
Hi to all...
i have the samsung galaxy s2 (GT-I9100) i9100XXMS3
it's upgraded (not by me) to android kitkat 4.4.4 CyanogenMod
CyanogenMod version 11-20140804-snapshot-M9-i9100
Kernel version 3.0.64-CM-g89e6992 build03
i have some problems (programs incompatibilities ect...)
and i want to know how i can downgrade my phone to any stable rom android 4.2.x
or any other custom or stock rom.
after all, i need to rooting the device to be more flexible
can anyone give me some help ??? rookie here...
thanks in advance
The device is already rooted, you just need to download any custom ROM you want, reboot to recovery, and flash your desired ROM from there.
Nightshadow931 said:
The device is already rooted, you just need to download any custom ROM you want, reboot to recovery, and flash your desired ROM from there.
Click to expand...
Click to collapse
first of all thanks for your answer.
If I understand properly
therefore, I'll have not any problem because of 4.4.4
that is correct ?
Yes, that is correct. The device is already rooted, with custom recovery, which means you can just reboot to recovery, wipe everything, and flash any desired ROM you want.
@@[email protected]........No disrespect intended, but this is "flashing 101" basics stuff........
The fact that you are asking it, tells me that you don't have the experience needed to do this comfortably.....
That's not a problem though.....we all start from the bottom, and learn as we go.....
But that being the case, i'd advise that you don't do anything to your phone until you've read, learnt and completely understood the processes behind the flashing procedure. It's best to understand what you are doing beforehand, rather than trying to figure out what went wrong afterwards.......
Sent from my GT-I9100 using XDA Free mobile app
Down grade
hi every one please i want to downgrade my phone samsung galaxy s2 from jelly bean to gingerbread and i need a link to download the firmware
Hello, as my thread title suggests I have a question about custom kernels. I made the mistake of updating to 4.3 on my device [I did it for the TRIM feature but wasnt aware of the cons Verizon put in place with 4.3], before 4.3 I was rooted and was using the stock OS and kernel. I do know that its possible to get Root access with 4.3 and Ive already done that - My question is if it is possible to install a custom kernel that will allow me to overclock this device ? I know there are a ton of kernels out there, but I dont want to risk bricking this device or having to download the ODIN 1GB+ 4.3 android file to bring it back to life..Thanks in advance!
Unfortunately, you cannot install a custom kernel. You would need to have an unlocked bootloader to install custom kernels.... and there's no current do it yourself method to unlock the 4.3 MJ9 bootloader.
4.1.2 was the last Android build for our phones where you could have unlocked the bootloader.... and so far, it doesn't look like there's going to be a method developed for 4.3.
mattnmag said:
Unfortunately, you cannot install a custom kernel. You would need to have an unlocked bootloader to install custom kernels.... and there's no current do it yourself method to unlock the 4.3 MJ9 bootloader.
4.1.2 was the last Android build for our phones where you could have unlocked the bootloader.... and so far, it doesn't look like there's going to be a method developed for 4.3.
Click to expand...
Click to collapse
That sucks...I dont think there is a way to go back to 4.1.2 either. Thanks for answer anyways.
Hello guys, I'm really just trying my luck on finding someone who can help me with this (or at least direct me to a thread or something..)
I've got a Sprint Galaxy Note 3 which is currently working with any network except for a couple of things I want addressed:
*I wanna downgrade back to JellyBean bexause there's an app that I need to be working (yes, it's more important to me than getting the latest android features)
*I wanna keep the phone *carrier-unlocked* (I was told that the phone is factory unlocked, and given that the phone has Sprint branding..it always goes on roaming mode just for it to work where I am (Phillipines), and I wanna fix that.)
So, with that being said, I just need help on where to start and what order should I be following to achieve these.. I'll be okay with stock Android JB but I want to use a custom rom as much as possible..
P.S. - I've tried reading the forums, and have been reading the forums.. it's just that I cannot seem to find something that would give me the result I want..
Any help would be much appreciated.. Thanks in advance for those who care to help..
bitz017 said:
Hello guys, I'm really just trying my luck on finding someone who can help me with this (or at least direct me to a thread or something..)
I've got a Sprint Galaxy Note 3 which is currently working with any network except for a couple of things I want addressed:
*I wanna downgrade back to JellyBean bexause there's an app that I need to be working (yes, it's more important to me than getting the latest android features)
*I wanna keep the phone *carrier-unlocked* (I was told that the phone is factory unlocked, and given that the phone has Sprint branding..it always goes on roaming mode just for it to work where I am (Phillipines), and I wanna fix that.)
So, with that being said, I just need help on where to start and what order should I be following to achieve these.. I'll be okay with stock Android JB but I want to use a custom rom as much as possible..
P.S. - I've tried reading the forums, and have been reading the forums.. it's just that I cannot seem to find something that would give me the result I want..
Any help would be much appreciated.. Thanks in advance for those who care to help..
Click to expand...
Click to collapse
Once your device was upgraded past MJ4 (jellybean) to NAB ( first kitkat based rom ) Knox was installed and as the device was upgraded past KK to OC2 lollipop Knox security follows making it impossible to go back to jellybean.
jimzweb1 said:
Once your device was upgraded past MJ4 (jellybean) to NAB ( first kitkat based rom ) Knox was installed and as the device was upgraded past KK to OC2 lollipop Knox security follows making it impossible to go back to jellybean.
Click to expand...
Click to collapse
regarding this process, say I have Lollipop installed, and don't care about tripping knox. Does it still make in impossible to go back to JB?
thanks for the response
bitz017 said:
regarding this process, say I have Lollipop installed, and don't care about tripping knox. Does it still make in impossible to go back to JB?
thanks for the response
Click to expand...
Click to collapse
Yes it is still impossible to downgrade. When the device is upgraded to kitkat and beyond several changes are made to the bootloader/modem. If you try to downgrade the bootloader/modem to MJ4 you will brick the device.
By tripping Knox all you are really doing is breaking the knox security system ( meaning Knox containerization of data is no longer possible ). What you might be able to do is root your device with a OK2 lollipop with a custom recovery. Then make a BACKUP of your rooted OS ( click on rom flashing basics in my signature for more info). Now you could try to find a jellybean based rom/OS and see if the device will boot up. The worst that can happen is you will soft brick the device ( it boot loops on start up ). To solve this just pull the battery and replace then boot into recovery and flash your backup and then try a different one.