Develop Bugs

[Q] Downgrading CM11 to stock 4.3 on i747M

I know there are a few threads regarding this issue but I can't seem to find a definitive answer.
I am currently running stock 4.3 jellybean (rooted). My phone hasn't received the 4.4 KitKat update yet, so I wanted to install CM11 in order to get KitKat on my s3. However, I heard CM11 can be buggy on the s3, so in case things go south, I want to be able to revert back to the stock 4.3 rom. Some people have said that you can easily flash the stock ROM via ODIN. However, others said that downgrading from 4.4.2 to 4.3 will hard brick the device since installing CM11 updates the boot loader. So downgrading to 4.3 stock with a 4.4.2 boot loader will cause a hard brick according to other threads I've seen. My question is, how can I downgrade from CM11 to stock 4.3 safely without bricking? Thanks in advance.

If you are sure you are using a Canadian version of the i747m, you can flash back to stock in Odin using a stock 4.3 ROM for the phone's original carrier (Bell, Rogers, Telus).

audit13 said:
If you are sure you are using a Canadian version of the i747m, you can flash back to stock in Odin using a stock 4.3 ROM for the phone's original carrier (Bell, Rogers, Telus).
Click to expand...
Click to collapse
Yes I got the phone from Rogers, it's most definitely i747M. But do I have to worry about any issues with the bootloader? I'm assuming installing CM11 will install the 4.4.2 bootloader, so if I choose to downgrade to the stock 4.3 rom, will it cause any issues seeing as I'm running a 4.3 rom with a 4.4.2 bootloader? I just want to make sure because I heard it can cause some serious problems if the bootloader is newer than the rom.

Mzrz said:
Yes I got the phone from Rogers, it's most definitely i747M. But do I have to worry about any issues with the bootloader? I'm assuming installing CM11 will install the 4.4.2 bootloader, so if I choose to downgrade to the stock 4.3 rom, will it cause any issues seeing as I'm running a 4.3 rom with a 4.4.2 bootloader? I just want to make sure because I heard it can cause some serious problems if the bootloader is newer than the rom.
Click to expand...
Click to collapse
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.

audit13 said:
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.
Click to expand...
Click to collapse
Okay, I was just making sure because I know OTA updates can change the bootloader, so I just wanted to make sure the custom roms don't do that. As for the custom recovery, are you recommending Philz Touch over CWM and TWRP? Do you know which custom recovery is installed from the CM installer?

audit13 said:
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.
Click to expand...
Click to collapse
Oh and one more question, my phone was originally carrier locked to Rogers and unrooted on 4.3 jelly bean. I brought it in to a cell store for them to carrier unlock it for me, but they used a rooting method to unlock it (because SuperSU was installed on it when I brought it back). They didn't unlock it with a code, so I'm guessing they used something like Samsung Tool or z3x shell. If I install CM11, will I lose the unlock, considering it's more of a "soft unlock", or is the unlock permanent regardless of how many roms I flash? Thanks for your help!

Mzrz said:
Okay, I was just making sure because I know OTA updates can change the bootloader, so I just wanted to make sure the custom roms don't do that. As for the custom recovery, are you recommending Philz Touch over CWM and TWRP? Do you know which custom recovery is installed from the CM installer?
Click to expand...
Click to collapse
Philz is based on the latest release of CWM and I prefer CWM over TWRP because I had problems flashing ROMs. Once I switched to Philz/CWM, no more problems.
Mzrz said:
Oh and one more question, my phone was originally carrier locked to Rogers and unrooted on 4.3 jelly bean. I brought it in to a cell store for them to carrier unlock it for me, but they used a rooting method to unlock it (because SuperSU was installed on it when I brought it back). They didn't unlock it with a code, so I'm guessing they used something like Samsung Tool or z3x shell. If I install CM11, will I lose the unlock, considering it's more of a "soft unlock", or is the unlock permanent regardless of how many roms I flash? Thanks for your help!
Click to expand...
Click to collapse
The unlock should be permanent. I unlocked it using the free method when on 4.1.1 and no ROM has ever caused it to re-lock. Reflashing a completely stock ROM, including the bootloader, did not relock the phone.
Please remember that flashing and changing ROMs will always carry a risk of soft bricking or hard bricking your phone. Make sure you read all of the guides and be prepared for disaster.
Good read here: http://forum.xda-developers.com/showthread.php?t=2201860

Unlock bootloader and root new device

I am going to purchase a Nexus 7 2013 and will be wanting to unlock the bootloader and root the device straightaway. I would be grateful if someone could tell me the best way to go about this. Should I carry out these tasks with no ROM updates applied, i.e. on 4.3 or should I update to Lollipop first? Thanks in advance.

With the nexus 7 its as simple as typing fast boot OEM unlock, but here is a more comprehensive guide on the matter. http://forum.xda-developers.com/showthread.php?t=2381698
Sent from my Nexus 7 using Tapatalk

Unlock the bootloader before doing anything else, as it will wipe your data in the process.
If you plan on staying with the stock rom, don't bother rooting or installing a custom recovery until you've updated all the way to lollipop, as it can cause the ota updates to fail and you'll just lose root with each update anyways. Beware of taking this route though, the are lots of posts around saying that the latest ota update bricked devices. Might be safer to fastboot flash the latest factory image directly.
If you plan on using custom ROMs, go ahead and root it and install custom recovery then flash away to your heart's content. You may need to update the bootloader to latest version first to successfully flash lollipop ROMs though. I think its version 4.04, and there are flashable zips for doing this somewhere around here that worked great for me.

crazymonkey05 said:
With the nexus 7 its as simple as typing fast boot OEM unlock, but here is a more comprehensive guide on the matter. http://forum.xda-developers.com/showthread.php?t=2381698
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Many thanks. I used the excellent Nexus Root Toolkit.

PrizmaticSmoke said:
Unlock the bootloader before doing anything else, as it will wipe your data in the process.
If you plan on staying with the stock rom, don't bother rooting or installing a custom recovery until you've updated all the way to lollipop, as it can cause the ota updates to fail and you'll just lose root with each update anyways. Beware of taking this route though, the are lots of posts around saying that the latest ota update bricked devices. Might be safer to fastboot flash the latest factory image directly.
If you plan on using custom ROMs, go ahead and root it and install custom recovery then flash away to your heart's content. You may need to update the bootloader to latest version first to successfully flash lollipop ROMs though. I think its version 4.04, and there are flashable zips for doing this somewhere around here that worked great for me.
Click to expand...
Click to collapse
I unlocked the bootloader, updated to Lollipop 5.0.2 by flashing the latest factory image, then rooted and flashed TWRP. I would now like to flash custom ROMS. You mentioned I may need to update the bootloader in order to successfully flash custom Lollipop ROMS? Am I correct in thinking I will have the latest bootloader, now that I have updated to Lollipop 5.0.2? Thanks.

pretty pixel said:
I unlocked the bootloader, updated to Lollipop 5.0.2 by flashing the latest factory image, then rooted and flashed TWRP. I would now like to flash custom ROMS. You mentioned I may need to update the bootloader in order to successfully flash custom Lollipop ROMS? Am I correct in thinking I will have the latest bootloader, now that I have updated to Lollipop 5.0.2? Thanks.
Click to expand...
Click to collapse
Yep, you're correct. If you flashed the factory image, you should already be on the latest bootloader. :good:
By the way, 5.1 factory image finally was released today for this device.

PrizmaticSmoke said:
Yep, you're correct. If you flashed the factory image, you should already be on the latest bootloader. :good:
By the way, 5.1 factory image finally was released today for this device.
Click to expand...
Click to collapse
Great, thanks for letting me know. Do you recommend I update to the 5.1 factory image before I flash any custom ROMS, or doesn't it matter?

pretty pixel said:
Great, thanks for letting me know. Do you recommend I update to the 5.1 factory image before I flash any custom ROMS, or doesn't it matter?
Click to expand...
Click to collapse
Doesn't matter, though you may wait for the custom ROMs to update to 5.1 so they will have the latest binaries.

PrizmaticSmoke said:
Doesn't matter, though you may wait for the custom ROMs to update to 5.1 so they will have the latest binaries.
Click to expand...
Click to collapse
Thanks. Do you know if CM12 has moved to 5.1 yet?

Not sure, don't really follow cm, but u can just check their website.

pretty pixel said:
Thanks. Do you know if CM12 has moved to 5.1 yet?
Click to expand...
Click to collapse
as i know only few devices are on 5.1 yet

OJ6 Baseband and Root

So Im on stock android right now and want to root but seeing that they just updated over the air has anyone else recently rooted from this update without issue? And if so what custom kernel is worth flashing to get root? Thanks. Ohhh Im on Android 5.1.1 of course and baseband of OJ6 which is the most up to date.

I dont think root is available for OJ6

Alright. Thanks.

http://forum.xda-developers.com/showthread.php?t=3247347
Try that and let me know if it works...
Note: it will trip Knox...

It does work on OJ6. I rooted mine yesterday after the update. Everything works fine

Hey guys, my last phone was a tmobile device, root and twrp is the norm. Which then I could flash Roms. I saw a twrp is available for us, is this right? Can I flash recovery, and then roms? Or am I missing something? I'm already rooted. I had to root for Sim unlock.
Thanks

coltfoet5 said:
I dont think root is available for OJ6
Click to expand...
Click to collapse
I updated to OJ6, rooted in Odin with file from here; http://forum.xda-developers.com/sprint-galaxy-s6-edge-plus/development/root-instructions-t3212573
Flashed TWRP with flashify. Good to go

Dowgrading from 5.1.1 to 4.4.2 and then installing Note 4 Mini ROM for good

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.

Stock rooted Pixel 2 XL, can I update to Android Pie while still rooted? Or go stock?

I'm on stock ROM rooted. I just manually checked for the update and Android Pie is now available but I'm not sure if I should update while still rooted or if I should do a clean install and then re-root again?

tracerit said:
I'm on stock ROM rooted. I just manually checked for the update and Android Pie is now available but I'm not sure if I should update while still rooted or if I should do a clean install and then re-root again?
Click to expand...
Click to collapse
If you take the OTA, you'll lose root access. I'd suggest a clean install to avoid issues then flash magisk.

sideload the ota zip, then magisk.

Chance Ill said:
If you take the OTA, you'll lose root access. I'd suggest a clean install to avoid issues then flash magisk.
Click to expand...
Click to collapse
i ended up backing everything up to prepare for a clean install. knowing i'd have to do a clean install anyways, i ended up updating to P while still on rooted O. I then flashed Magisk and it was running P rooted just fine. Didn't have to do the clean install really but would've if I liked P, which I don't, so now I"m back on O.