** Newer 4.4.2 version (UCUCNJ1) available HERE **
Here are a set of stock rooted Android 4.3 packages for the AT&T i317 Note 2 (firmware version UCUBMK6).
There are options flashable from custom recovery (CWM, TWRP) or, if you'd rather, via Odin. They are built from the 12/17/2013 stock OTA for the AT&T I317 in all their bloated glory.
**They do not include the MK6 bootloader or tz files **
** IF YOU ARE ALREADY ON THE MK6 BOOTLOADER (OR ABOVE) FLASHING ANY OF THESE PACKAGES WILL TRIP THE KNOX COUNTER **
These packages are intended only for the AT&T version of the Note 2 and include the modem and kernel for this phone. Flashing on any other North American Note 2 will result in a soft brick and require a re-flash of the modem/kernel specific to your phone. Flashing on any other phone will likely require a complete reflash of your phone's stock firmware to recover - do not attempt. The other standard disclaimers apply - while these packages have been tested and work on the AT&T i317, you assume all risk in flashing.
First a word on the MK6 bootloader - it has been reported that it is "locked". This is only partially true. If it were completely locked, we would be unable to flash custom recovery or kernel files from download mode - as is the case with the AT&T Note 3. What the MK6 bootloader prevents is downgrading the bootloader to any prior version. So, if we're going to call it locked, it's a "bootloader revert lock" but not a "firmware flash lock". A pain in the a$$, particularly if you want to revert your phone to 4.1.2 stock, clear the download counter with triangle away, unroot, and have your phone looking the same as it did on day one.
The main issue with the MK6 bootloader - If your phone is still covered by warranty: The MK6 bootloader implements one of the Samsung KNOX Secure Boot components: an "e-fuse" that gets set to "1" as soon as you flash something custom on your phone. Once set (so far anyway) this cannot be reset to "0". If this flag is tripped, a service center may use this to deny warranty repair coverage.
Given this, taking the OTA is not recommended for anyone thinking of flashing custom firmware at any time in the future. With that in mind, there is no MK6 bootloader or tz file in these packages. However, a 4.3 bootloader is needed in order for wifi to function. Fortunately we have a 4.3 bootloader available that permits revert to lower versions courtesy of the leaked MJ4 firmware provided by designgears. It is provided here to complete the install.
Here is what you have available:
All firmware packages include the system firmware, kernel, and modem from UCUBMK6. They are rooted with the as of Dec '13 current version of Chainfire's SuperSU. They include Linus Yang's build of busybox. They do not include recovery, bootloader or tz (you install the last two separately via Odin if needed)
All packages completely replace the contents of the system partition. If you are coming from another stock-based i317 firmware wipes should not be necessary.
**NOTE** Odin ZIP packages should be unzipped ONCE. The extracted MD5 file should be placed in the PDA slot in the Odin app. Do not change any other options. If the phone shows up on top as COMn and the MD5 checks out OK in the status window, you are good to click Start. **
AT&T UCUBMK6 i317 *Odexed* Stock CWM Note 2
AT&T UCUBMK6 i317 *Deodexed* Stock CWM Note 2
AT&T UCUBMK6 i317 *Odexed* Stock ODIN Note 2
If you *are not* running Official 4.3 (MK6) or newer bootloader:
After flashing one of the firmware packages above flash the bootloader package below in Odin to get wifi working (sorry, no option available for CWM/TWRP). I've included the Odin executable just after if needed.
Bootloader needs to be flashed only once. See post #2 for information on how to check what version of bootloader you have installed.
** Warning - do not attempt to flash MJ4 bootloaders if you already have the MK6 bootloaders - this will soft brick your phone - see post #2 for more **
AT&T i317 ODIN 4.3 UCUBMJ4 (Leak) Bootloader & TZ (AT&T Note 2 ONLY)
If you *are* running the Official 4.3 (MK6) bootloader:
After flashing one of the stock packages, you may need to flash the MK6 tz.img and optionally the param.bin from the MJ4 leak. This is likely to be so if you are on the MK6 bootloader and have previously reverted to 4.1 firmware. The zip below contains two Odin packages. If after flashing the stock package and you are on the MK6 bootloader, try flashing the tz only package first (in Odin), then the tz+param package to see if this gets your phone to boot. You may also need to boot recovery and do a factory reset.
AT&T i317 ODIN 4.3 UCUBMK6 TZ.IMG & UCUBMJ4 (Leak) PARAM.BIN (AT&T Note 2 ONLY)
Need Odin ? --> Odin 3.07
For completeness's sake I've included separate packages for the ucubmk6 modem and stock kernel & recovery.
CWM AT&T i317 UCUBMK6 Stock *Modem* Note 2
CWM AT&T i317 UCUBMK6 Stock *Kernel* Note 2
CWM AT&T i317 UCUBMK6 Stock *Recovery* Note 2
Here are links to custom recoveries specific to the I317 (AT&T Note 2):
PhilZ Advanced CWM Edition
TWRP Recovery
*** After you boot the phone, run the SuperSU app. You will be asked if you want to disable Knox. Your best course of action here is to answer yes.
• Thanks to Chainfire for SuperSu - we wouldn't have root access on 4.3 without his work (we should all be donating to him or buying his pro version)
• Thanks to designgears for the initial 4.3 leak, which gave us the 4.3 bootloader/tz allowing revert to earlier bootloaders
• Thanks to Linus Yang for the busybox build
• Thanks to dicksteele for helping test odex & odin packages
[FONT="]
[/FONT]
FAQ - Issues related to 4.1 to 4.3 upgrade/downgrade, etc
My files on my SD Card disappeared! or I'm out of space, but why?!?
When moving to 4.3 from 4.1 Android remaps the SD Card from /data/media to /data/media/0. All your files are still there, just inaccessible from your PC via USB connection, or from standard file managers. Root-capable file managers/explorers can still see the files and can provide a fix. See this thread for a permanent solution (assuming you are done with 4.1.x):
http://forum.xda-developers.com/showthread.php?t=2274218
(Note that if you revert to a 4.1.x rom you will need to reverse this process).
I can't restore CWM/TWRP backups made in 4.1.2 now that I'm on 4.3 (or visa versa)
I believe this may be a variation on the above issue. try moving (not copying - as you may run out of space) your cwm or twrp backup folder from it's relative location in media to media/0 or the reverse and try your restore again.
** last note on this issue - philz recovery has an option to toggle sdcard location to media/0 which can help with seeing backups, etc - not sure about twrp
When I revert from 4.3 to 4.1 Gmail won't send messages
Go into Settings/Apps and clear data and cache for Gmail
I tried to flash the MJ4 bootloaders on top of the MK6 bootloaders already on my phone and now I get a message about kies and my phone won't boot
This is how the MK6 bootloader demonstrates its hostility toward downgrade attempts... While you may be stuck in download mode, you do not need to reflash an entire firmware package to escape. The easiest way out is to succesfully flash a custom recovery Odin package. This will clear the error condition in download mode and your phone once again boot correctly. See the recovery links in the OP to find an Odin package for your preferred custom recovery.
I'm not sure what version of bootloader I am running - how do I check?
There's a simple app called "Device Info" available on the Play Store (it's the one published by JPHILLI85) which will display your bootloader version. The only permission it requests is phone status/id. Or you can open up terminal emulator and type "getprop ro.bootloader" if you don't want to install an app (assuming you have already installed Terminal Emulator).
I would like to get back to a pure stock unrooted configuration - how do I do this?
First, if you have the MK6 bootloader this is currently not possible - at least as far as what will be displayed in download mode. If you are on MJ4 or below, the simplest way to do this is to flash back to 4.1.2 using the stock UCAMA4 Odin package, cf-auto-root, run triangle away, run SuperSU to completely remove root, boot recovery and do a factory reset. After this you have the option to take the OTA and update to UCUBMK6 if desired with stock everything - but it will be a one way trip with the previously discussed "revert locked" bootloader. This is the short version, there are guides available in the general section, which offer variations on this with different files. Note that the UCALJ2 ODIN package offers an option for those with the MK6 bootloader as it does not include the bootloader or tz files (thus is does not soft brick the phone as described above). In that scenario you stay on the MK6 bootloader so you don't get a complete revert (no ability to run triangle away, but you can get back to 4.1.2 and factory reset).
Here are links to the Odin stock packages for reverting and the relevant threads:
UCUBMK6 Downgrade to UCALJ2 (general guide - Thanks @perez6991 !)
How to OTA to 4.3 MK6 from LJ2 4.1.1 (with MK6 bootloader!) - Thanks @dicksteele !
Stock UCALJ2 ODIN package for those with MK6 bootloaders
TZ and (Optional) PARAM for those with MK6 bootloader
Stock UCAMA4 ODIN package for those with MJ4 bootloaders
General instructions for those with MJ4 bootloaders (use instructions but not files) **
** A note on this last link for those with MJ4 bootloaders - the instructions are sound, but the files provided include the LJ2 package and older versions of cf-auto-root and triangle away. Use MA4 instead and locate the current versions of the other two Chainfire apps (I've provided links in the previous sentence - for cf-auto-root make sure you grab the "SAMSUNG-SGH-I317" file) **
----------------------------
How to get Screen Sharing (AllShareCast) working - http://forum.xda-developers.com/show....php?t=2542509 (thanks to @joshuaburnsjr for tracking this down)
In other news ....
Technology is magic - you shouldn't let poets lie to you >>>> * <<<<
--------
:good::laugh::good: Big thanks to those who have contributed to my Android mischief fund :good::laugh::good:
Awesome work for a Retired Contributor, Sir.
Thanks, Zen. Will have to give it a go once I get tired of looking at my "normal" status.
I've been trying everything on this base and it is perfect. If something does not work for you, you did something wrong. Not trying to be an ass, but I've been running it for three days now and it's solid. I have over 150 apps. (edited from 200 since I cleaned a lot of crap out I never used)
Backups of apps are great, but if you want a true cherry ROM, install your apps from scratch. I did.
Yeah, it's a pita, but it's a good time to decide what you really need. And it's done right. You don't have to wonder if your backup program hosed it up, is it a ROM issue, whatever.
Google Play keeps a good history of what you have installed so it's not that hard to find old or new apps you have loaded.
Enjoy. It was an pleasure and honor to assist.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thank you!!!
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Omg thanks Zen....
Enviado desde mi SAMSUNG-SGH-I317 usando Tapatalk 4
!!!!
Thank you thank you thank you!!!!
Just wanted to say: you saved my day! So glad I don't have to curl up in the corner of my bedroom crying because I bricked my phone ...
I just flashed everything and it worked just like you said!
No problems at all. Just wanted to let you know.
Thanks so much for your hard work, so we can enjoy 4.3 on our devices! :good:
Just for informational purposes, my phone came from: 4.1.2 Stock TWRP (2.6.3.0) rooted
esprit1st said:
Just wanted to say: you saved my day! So glad I don't have to curl up in the corner of my bedroom crying because I bricked my phone ...
I just flashed everything and it worked just like you said!
No problems at all. Just wanted to let you know.
Thanks so much for your hard work, so we can enjoy 4.3 on our devices! :good:
Just for informational purposes, my phone came from: 4.1.2 Stock TWRP rooted
Click to expand...
Click to collapse
Good news.
Thanks for the info about where you flashed from. What TWRP version was it?
I flashed the deodexed file in twrp and rom loaded fine. Then I flashed the bootloader in odin-I made sure it was the pda slot and hit start. Rebooted phone and was stuck at first screen saying galaxy note 2. So I flased the deodexed rom again in twrp anf everything loaded fine and wifi worked but when I went to reboot it gets stuck at the first screen again. Tried flashing again but didnt work. Then I tried fix permission and it worked, bit when I went to reboot it would get stuck again. After trying a bunch or other stuff like wiping and fixing permission I was able to go back to 4.1.2 jedi that I had a backup of. All seems fine fo4 now but would still like to be on 4.3
Thanks not only for the ROM zen, but also thanks for clearing up the bootloader nonsense as well.
This is the first place I've seen it clearly stated for users. I've tried explaining in the past, but is been misinterpreted due to the way I've phrased things. In the future I'll just link this thread to explain.
--》Sent from my mind to your screen
funtimez said:
I flashed the deodexed file in twrp and rom loaded fine. Then I flashed the bootloader in odin-I made sure it was the pda slot and hit start. Rebooted phone and was stuck at first screen saying galaxy note 2. So I flased the deodexed rom again in twrp anf everything loaded fine and wifi worked but when I went to reboot it gets stuck at the first screen again. Tried flashing again but didnt work. Then I tried fix permission and it worked, bit when I went to reboot it would get stuck again. After trying a bunch or other stuff like wiping and fixing permission I was able to go back to 4.1.2 jedi that I had a backup of. All seems fine fo4 now but would still like to be on 4.3
Click to expand...
Click to collapse
It sounds like something is hanging around from your previous rom. Since you have a backup I'd recommend the following (note that this will wipe your phone and require a TiBu restore or Play Store app reload):
1 - Take a full backup using Titanium Backup
2 - Copy everything from your SD cards to your PC
3 - Flash the 4.3 package
4 - (You can skip the bootloader since you already flashed it, unless your twrp backup restores an older bootloader)
5 - While in recovery, do a factory reset (this will wipe everything)
6 - Boot phone, check that wifi works, and other standard functions are ok
7 - Restart phone, and confirm that the problem you saw before is gone
8 - If the problem is gone (i.e. the phone reboots successfully multiple times with no lockups), continue on...
9 - Copy the contents of your SD cards back to your phone - check to make sure everything is copied - the USB driver for the Note 2 can be a bit selective at times (also refer the the FAQ in Post #2 - confirm that sdcard information has been removed from /data/media and is in /data/media/0)
10 - In TiBu, restore ONLY user apps (you can restore app+data, but in some rare cases you might need to clear data) - do not restore any system apps. (Alternative - you can restore apps directly from the Play Store as dicksteele noted in a previous post - this may be cleaner, but you will lose any data associated with the apps - your call and ymmv).
11 - Reboot phone, and confirm everything is OK.
Hopefully this clears the issue for you. If it does not, you may need to do a full wipe between steps 2 and 3 above, clearing /data and your internal sdcard before starting the install. If so, make sure you have access to stock odin packages to reload your phone OS just in case. There are threads on this in the General section, but I'll post links to the files in post #2 as well.
Awsome. Thanks so much, needed root works great ::good:
funtimez said:
I flashed the deodexed file in twrp and rom loaded fine. Then I flashed the bootloader in odin-I made sure it was the pda slot and hit start. Rebooted phone and was stuck at first screen saying galaxy note 2. So I flased the deodexed rom again in twrp anf everything loaded fine and wifi worked but when I went to reboot it gets stuck at the first screen again. Tried flashing again but didnt work. Then I tried fix permission and it worked, bit when I went to reboot it would get stuck again. After trying a bunch or other stuff like wiping and fixing permission I was able to go back to 4.1.2 jedi that I had a backup of. All seems fine fo4 now but would still like to be on 4.3
Click to expand...
Click to collapse
Piggybacking on Zen's reply, which TWRP are you using?
I've been using 2.6.3.0 and 2.6.3.1 and I've had issues with restores. You may want to try PhilZ Advanced CWM Edition. Zen has a link in Post #1.
I'm using the latest version 6.00.8 and it's been restoring great. You can flash it from TWRP and reboot to recovery from TWRP and Philz with come up.
EDIT: If you're going to use Philz recovery for Wipe Data/Factory Reset, choose Clean to Install a New ROM.
Thanks for replying I figured it out by the time u guys replied. I updated to the latest version of twrp,I was on a old 1. Then I factory reset and wipe delvic and what not then did a full wipe. I then installed 4.3 Ron and didn't wipe cache and delvic but got stuck in bootloop. So I wiped again and flashed again and this time I wiped cache and delvic and everything it working just fine now including reboots. Thanks for this awesome update and the help from u guys
Dude............this ROCKS!!!! THANK YOU!
AT&T Galaxy Note II Android Development > [ROM][4.3][Dec-2013] AT&T I317-UCUBMK6/MJ4
Thanks for this Zen. I've been patiently waiting for someone to do this. You are the man!
Thanx Zen for this...:thumbup:
I'm going to have to add this my one stop shop for sure...
Bajan out...
SENT FROM SAMMY i317 USING TAPATALK
Thanks!
Running 4.4 to test it out, but I'm keeping this as my fail safe.
Went exploring other ROMs due to deodex 4.3 not being out at the time, but I'm glad you put in work to organize it
and offer 3 different versions of it. Thank you!
Hello, I wanted to root and install TWRP then a KitKat ROM that's NOT altered or one that's been running and is a proven daily ROM. I haven't messed with Roms or phones for some time so I got all the info I need up to the ROM and I cant seem to find a stock rom. Any ideas?
Thanks!
Oxicottin said:
Hello, I wanted to root and install TWRP then a KitKat ROM that's NOT altered or one that's been running and is a proven daily ROM. I haven't messed with Roms or phones for some time so I got all the info I need up to the ROM and I cant seem to find a stock rom. Any ideas?
Thanks!
Click to expand...
Click to collapse
This is the latest NE1 4.4 stock firmware (france) from sammobile uploaded to a different host by an user for faster download speeds,extract the zip file you'll find a .tar.md5 file flash it via ODIN.Then you can just install custom recovery via pc odin (use philz 6.26 ot 6.41 initially and once you get a custom recovery successfully installed you can switch to twrp) now once into philz recovery flash supersu 1.99 from this post flash it right after you flash your recovery ,your phone should be rooted.Few things that you need to do is uncheck auto reboot in odin when flashing the recovery,after flashing philz you should manually enter it by pressing the right combination of buttons ( volume up + home + power) and then flash the supersup 1.99 zip file right away. (place the supersu zip file in sd card right after you flash the 4.4 ROM and before you proceed to install custom recovery)
Philz touch
twrp
NE 1 Stock France
Unclear
singhpratik87, I'm a little unclear on the sequence your proposing me to go through to install a ROM. I thought you installed;
1) Superuser ...... Done!
2) ODIN Custom Recovery (TWRP) ...... Done!
3) NE1 4.4 ROM ..... Downloaded moved to phone but not installed...
Ok here are my concerns, I'm on a AT&T 1317 phone will this ROM work OR would a custom ROM be better? Next, what is Philz touch?
Thanks,
Soggy
Oxicottin said:
singhpratik87, I'm a little unclear on the sequence your proposing me to go through to install a ROM. I thought you installed;
1) Superuser ...... Done!
2) ODIN Custom Recovery (TWRP) ...... Done!
3) NE1 4.4 ROM ..... Downloaded moved to phone but not installed...
Ok here are my concerns, I'm on a AT&T 1317 phone will this ROM work OR would a custom ROM be better? Next, what is Philz touch?
Thanks,
Soggy
Click to expand...
Click to collapse
See you didn't mention that you were on AT&T,unfortunately it wouldn't work you got to wait for your carrier to release the update. My explanations were pretty straight forward but now it doesn't matter anymore since you don't have the international note II GT N7100. The rom was supposed to be flashed via ODIN not SD CARD (it's a stock rom not a custom rom).And the steps are (for future reference) flash stock rom via odin, then flash philz via odin(uncheck auto reboot in odin),manually enter into recovery mode , flash supersu 1.99(or whichever is the latest) , reboot phone , DONE.
Philz touch is another popular recovery used by note II users .it's based on CWM with advanced features.
singhpratik87..... What custom ROM out there is equivalent to the 4.4 kitkat for a AT&T I317 Note 2 running 4.3? Those would prob be better anyway....
Also this other recovery you mention is it better? Like I said I have been out of messing with phones for a few years Thanks!
Oxicottin said:
singhpratik87..... What custom ROM out there is equivalent to the 4.4 kitkat for a AT&T I317 Note 2 running 4.3? Those would prob be better anyway....
Also this other recovery you mention is it better? Like I said I have been out of messing with phones for a few years Thanks!
Click to expand...
Click to collapse
None in the International Note II forum that would be compatible with AT&T as far as 4.4.2 is concerned.There's no development for 4.4.2 in your a&t note II thread?
why don't you check out this thread which is specifically for your at&t branded note 2 http://forum.xda-developers.com/galaxy-note-2-att/development
Dear friends
I'm going to describe the steps i took for fixing the WiFi problem of my Samsung Galaxy Note 2 N7100.
The problem started last january, when the device got the latest 4.4.2 update from Samsung. By that time, it was not rooted.
WiFi started to turn off by itself, WiFi slider was grey and wont turn on again, searching for ip adress, etc...
I did everything i could find over the internet and nothing fixed it, after 1 month of search i was about to give up.
1. Flash stock 4.3 ROM from Sammobile using Odin 3.09, in my case the ROM was this:http://www.sammobile.com/firmwares/download/23564/N7100UBUEMK4_N7100ZTOEMK3_ZTO/
I tried this with the lates 4.4.2 ROM without success.
2. Do a data wipe/factory reset from the stock recovery utility.
3. Flash philz_touch_6.48.4-n7100 recovery utility using Odin 3.09. File here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7100/philz_touch_6.48.4-n7100.zip.md5/
4. Root your device by installing SuperSU-v2.40 from philz recovery utility. Get it here: http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip
5. Install NI1 Bootloader using Odin 3.09 with the BL tab, get it here http://forum.xda-developers.com/showpost.php?p=54320353
6. Install NI1 patched modem from philz recovery utility, get it here: https://www.dropbox.com/s/m950i4l27cpksrb/NI1_modem.zip?dl=0
7. I'm very happy with Android 4.3 and WiFi working again, if you wanna try to update to 4.4.2, do it at your own risk.
Good Luck
Special thanks to Androidwizzard
I used Kies to update my previously rooted 5.0.1 Note 4. I now have Android 5.1.1 Lollipop VPU4COG5. With the update, my TWRP recovery was removed. I flashed TWRP recovery 2.8.1.1 via Odin and then, lacking a tar file, downloaded and flashed BeastModeStock 1.0-N910P-OG5.zip, which is shown installed on my phone. Problem is, the phone is NOT rooted. I cannot open superSU, getting a message "There is no SU binary installed, and SuperSU cannot install it. This is a problem!..."
Any suggestions?
Thanks
Follow the instructions here. http://forum.xda-developers.com/showpost.php?p=62274866&postcount=55
wetmountain said:
I used Kies to update my previously rooted 5.0.1 Note 4. I now have Android 5.1.1 Lollipop VPU4COG5. With the update, my TWRP recovery was removed. I flashed TWRP recovery 2.8.1.1 via Odin and then, lacking a tar file, downloaded and flashed BeastModeStock 1.0-N910P-OG5.zip, which is shown installed on my phone. Problem is, the phone is NOT rooted. I cannot open superSU, getting a message "There is no SU binary installed, and SuperSU cannot install it. This is a problem!..."
Any suggestions?
Thanks
Click to expand...
Click to collapse
All you did was flash the OG5 pre rooted kernel over your pure stock odexed rom. This alone does not give you root. If you wait a little while you can download and flash the new rom i'm uploading right now. It's pre-rooted and all you have to do is flash the rom and go about your business. Look for a new rom thread later tonight.
Hi Friends,
I recently flashed French 5.1.1 update on my N3N and rooted through Chainfire's method. File were taken from autoroot chainfire's website. I am facing an issue as listen below:
Once the device is rooted, I download Root checker which says device is rooted. I run some root apps and yes the apps work. However, when I factory reset through the option in settings, the phone kinda hard reset. It optimizes all apps when it does first login which usually doesn't happen when resets. Moreover, once the phone starts, to my surprise, the phone has lost root. None of the rooted files work and root checker says it's not rooted. And then I have to re-root. Why is this happening?
Now, I want to downgrade and install v10 Note 4 mini ROM. May I request the gurus here to guide me. I have installed this ROM on my other N3N and it's working fine, however that phone is on 4.4.2. Will downgrading my lollipop based phone to kitkat cause the phone to brick or something? And the basic procedure to downgrade includes:
1) Install TWRP recovery
2) Wipe cache data etc
3) install Note 4 Mini ROM OR I should first install official KitKat ROM and then wipe it all and install the custom (note 4 mini) ROM.
Would appreciate your help here.
Thanks.
First of all NEVER factory reset your Rooted Phone unless it is unrooted otherwise you will always face this type of problem.
Samsung device is Hard to brick so just flash your 4.4.2 kitkat desired country Firmware using odin and enjoy
http://www.sammobile.com/firmwares
Thanks shyboy for your reply. In one of the threads, I figure out CF autoroot was partially running. It did not give complete root access to the phone and hence the problem arise. I installed TWRP redovery and copied latest SuperSU in the sdcard. Then through TWRP, I flashed latest SuperSU and voila, I had my phone fully rooted.
2020shyboy said:
First of all NEVER factory reset your Rooted Phone unless it is unrooted otherwise you will always face this type of problem.
Samsung device is Hard to brick so just flash your 4.4.2 kitkat desired country Firmware using odin and enjoy
http://www.sammobile.com/firmwares
Click to expand...
Click to collapse
BDW, what if I want to come to official Lollipop 5.1.1 over my Note 4 mini ROM. Should I just ODIN the official 5.1.1 firmware or do I need to first wipe it through TWRP and then flash the official ROM?
Sorry if I am bothering you. Just wanted to know.
make a backup of your internal sd card
1. boot in recovery mode
2. wipe all (data and system)
3. power off (pull out battery)
4. power on in download mode ( "Vol-" + "Home" + "Power button")
5. flash stock 4.4.2 via odin e perform the first boot.
6. boot in download mode, flash cf autoroot and reboot
7. flash the recovery you want (kitkat version)
8. enjoy
Click to expand...
Click to collapse
filthykid said:
BDW, what if I want to come to official Lollipop 5.1.1 over my Note 4 mini ROM. Should I just ODIN the official 5.1.1 firmware or do I need to first wipe it through TWRP and then flash the official ROM?
Sorry if I am bothering you. Just wanted to know.
Click to expand...
Click to collapse
Suppose brother you are on 4.4.2 base firmware and you are flashing Note4 mini rom you can take backup using twrp recovery, and can flash S5 custom rom for N3N which has base firmware of 4.4.2 but if you want to flash new Version of RoM 5.1.1 you have to use odin then i think you cant use Note4mini rom because it is based on kitkat hope it helped
just press thanks button rather than a reply
2020shyboy said:
First of all NEVER factory reset your Rooted Phone unless it is unrooted otherwise you will always face this type of problem.
Samsung device is Hard to brick so just flash your 4.4.2 kitkat desired country Firmware using odin and enjoy
http://www.sammobile.com/firmwares
Click to expand...
Click to collapse
Tried downgrading from lollipop to kitkat. Seems it's not possible.
Sent from my SM-N750 using Tapatalk
anand4edu said:
Tried downgrading from lollipop to kitkat. Seems it's not possible.
Sent from my SM-N750 using Tapatalk
Click to expand...
Click to collapse
You can downgrade to KitKat. There is a thread on the forum who talks about that.
Please help with the reference link.
lennon123 said:
You can downgrade to KitKat. There is a thread on the forum who talks about that.
Click to expand...
Click to collapse
I don't know whether you have done it or not. But if not, beware, there is a risk of losing imei while downgrading from 5.1.1 to lower versions. I would suggest making a EFS backup first. By doing that you can restore your IMEI in case you lose it.
Download EFS backup apps from google play store.