I have been a long time lurker on these forums, and to start on here would like to thank all the helpful posts I have read. Currently I am using a Galaxy SIII (i747). I'm not sure what firmware I got it on, however I downloaded the CM installer from the website and used it to flash my phone. It currently is on a really unstable CM11 build (kind of mad the installer pushed a non-RC to my phone) and I would like to downgrade to CM10.x. I checked the d2att wiki and there are no RC or stable CM 11 builds. From what I read there was a bootloader introduced in 4.3 that locked down the phone. I'm not sure if a) I have this locked down bootloader? I currently have TWRP installed, which I think a locked bootloader would prevent. b) Is it safe for me to try and downgrade to CM 10 with ODIN? Any help would be much appreciated.
jdkuki said:
I have been a long time lurker on these forums, and to start on here would like to thank all the helpful posts I have read. Currently I am using a Galaxy SIII (i747). I'm not sure what firmware I got it on, however I downloaded the CM installer from the website and used it to flash my phone. It currently is on a really unstable CM11 build (kind of mad the installer pushed a non-RC to my phone) and I would like to downgrade to CM10.x. I checked the d2att wiki and there are no RC or stable CM 11 builds. From what I read there was a bootloader introduced in 4.3 that locked down the phone. I'm not sure if a) I have this locked down bootloader? I currently have TWRP installed, which I think a locked bootloader would prevent. b) Is it safe for me to try and downgrade to CM 10 with ODIN? Any help would be much appreciated.
Click to expand...
Click to collapse
I also have an ATT S3 (I747) - It's running flawlessly on CM 10.2.1 (4.3) with the UCUEMJB bootloader (which can not be downgraded at this time to my knowledge). It also has TWRP 2.8.1.0 installed. I used this to downgrade from CM11 to CM 10.2.1 by restoring thru TWRP.
So, you should be good to go. Just make a Nandroid backup using TWRP and then flash CM 10.2.1 (zip file) using TWRP.
BTW - the MJB bootloader can not be downgraded. The MJ2 and earlier bootloaders (prior to 4.3) can be. I believe this is what you're referring to as "locked"???
Hope this helps . . .
Related
Hi!
I'm a happy user of the ATP since this summer. When I buy it, it comes with ICS (Android 4.0), and when Android 4.1 was released, I didn't wait to an official upgrade: I follow the instructions and unlocked with the official ASUS application and then installed CWM 5.8.2.0 and a CyanogenMod 10 nightly.
Now, I want to move forward, but I read some thing about different bootloaders and I prefer to be more careful than I usually am.
First, I don't if I can return to an official ASUS ROM with my actual configuration (unknown bootloader, CWM 5.8.2.0 andCM10 nightly).
Second, I don't know if there is an thread about the official ROMs (I was unable to find any).
Third, I don't know if the latest ASUS ROMs are Android 4.2.1, 4.2 or 4.1.
[cry mode]In addtion, trying to look my bootloader version I made a mess and wipe my user data, so this is the perfect momentum to move backward/forward and put my ATP in the "right way".[/cry]
Thanks in advance and best regards
Ok, I just have found a thread about the official updates and it looks like ASUS is still on 4.1 (not bad!).
So, One of my questions is answered
I hope that when you say "unlocked" you mean after getting nvflash access:
http://androidroot.mobi/2012/07/15/nvflash-for-tegra3-transformer-prime/
http://androidroot.mobi/t3_nvflash/
(will save you from bricking)
Generally, you have the ICS bootloader and the JB bootloader. Most roms now require the JB bootloader, so if you're looking to flash new roms, especially something like craigmcgomez's unofficial AOKP/CM roms (based on 4.2), you'll need the JB bootloader. I simply used this rom:
http://forum.xda-developers.com/showthread.php?t=1927494
This is the official worldwide ASUS update (there's also a US version in another thread, not sure if these are still the most up-to-date), but it's 4.1 (.2?), rooted and it comes with TWRP recovery (I prefer over CMW5), but most importantly, it comes with the new JB bootloader. I understand you won't be able to return to the ICS bootloader after you update to the JB bootloader, but I don't see a reason why you'll want to. Either way, you can flash this even if you're on the ICS bootloader (and if you're already on the JB bootloader).
After you flash this you can flash JB bootloader-compatible roms. I recommend AndroWook or AOKP. I'm on AndroWook, but I'm waiting for official CM10.1.
If I'm not mistaken, the CM10 nightlies work on the ICS bootloader, and 10.1 will officially support the JB bootloader only, so my guess is you're on the ICS bootloader. If you updated to stock 4.1.x or any rom that says it comes with the JB bootloader, then you know you've got the JB bootloader, otherwise you're probably on ICS bootloader.
Thanks WiW for your answer.
I don't know if I have unlocked the Nvflash...
I refer to using the Asus tool for being able to enter to the bootloader/recovery (when the message "This device is unlocked"appears on the top left corner when the Nvidia logo is on the screen.
I will check all your links now. A lot of thanks for you time!
Sent from my GT-I9100 using Tapatalk 2
Now reading your two first links I'm pretty sure that I didn't unlock my NVflash. I only unlocked my bootloader for being able to flash a recovery, just that.
Sent from my GT-I9100 using Tapatalk 2
Well, if you're not sure you can follow this guide and see if it works for you. If you did not follow the steps from the previous links I posted, I think there isn't much you can do about it...
Sorry for the misunderstanding. I was able and I successfully unlocked and backup my files with NVflash.
I installed the official Asus ROM and the JB bootloader and TWP Recovery.
After that I've installed the Androwook, as you suggested. It works fine, but I expected 4.2... my fault, I didn't read the entire AndroWook post.
A lot of thanks WiW
Sent from my GT-I9100 using Tapatalk 2
My specs:
SCH-I545
Android 4.2.2
Baseband: I545VRUAMDK
Kernel: 3.4.0-562219
[email protected] #1
Build Number: JDQ39.I545VRUAMDK
Rooted
CWM Recovery Installed
My questions:
1. I've found many threads and great instructions for installing CyanogenMod. I'm still having difficulty separating the wheat from the chaff - Which version should I use for my phone, given that I'm an MDK still running 4.2.2?
2. Which version of Gapps will I need for that version of CyanogenMod?
3. If the answers to the previous questions are NO YOU CAN'T DO THAT, is there a way for me to update my Android Version to the most current, and THEN flash CyanogenMod?
I understand that there are resources out there to get this done. I've searched and found most of them. I'm just not entirely clear on which version is most appropriate for my phone, which by most standards here is somewhat pristine in that it's still running MDK, and a bit outdated in that it's running on 4.2.2. Please be gentle with me. I'm just trying to get up to speed and be productive in this forum. Thanks for your help!!
onearmsysiphus said:
My specs:
SCH-I545
Android 4.2.2
Baseband: I545VRUAMDK
Kernel: 3.4.0-562219
[email protected] #1
Build Number: JDQ39.I545VRUAMDK
Rooted
CWM Recovery Installed
My questions:
1. I've found many threads and great instructions for installing CyanogenMod. I'm still having difficulty separating the wheat from the chaff - Which version should I use for my phone, given that I'm an MDK still running 4.2.2?
2. Which version of Gapps will I need for that version of CyanogenMod?
3. If the answers to the previous questions are NO YOU CAN'T DO THAT, is there a way for me to update my Android Version to the most current, and THEN flash CyanogenMod?
I understand that there are resources out there to get this done. I've searched and found most of them. I'm just not entirely clear on which version is most appropriate for my phone, which by most standards here is somewhat pristine in that it's still running MDK, and a bit outdated in that it's running on 4.2.2. Please be gentle with me. I'm just trying to get up to speed and be productive in this forum. Thanks for your help!!
Click to expand...
Click to collapse
1) You need to download a nightly version of CM, I would advise reading the thread over there to see which one is the most stable before flashing. From what I've heard though CM has been very buggy.
http://download.cyanogenmod.org/?device=jflte&type=nightly
2) You should download the latest version of KitKit's GApps
https://goo.im/gapps/ ( gapps-kk-20140606 )
3) Happy flashing.
onearmsysiphus said:
My specs:
SCH-I545
Android 4.2.2
Baseband: I545VRUAMDK
Kernel: 3.4.0-562219
[email protected] #1
Build Number: JDQ39.I545VRUAMDK
Rooted
CWM Recovery Installed
My questions:
1. I've found many threads and great instructions for installing CyanogenMod. I'm still having difficulty separating the wheat from the chaff - Which version should I use for my phone, given that I'm an MDK still running 4.2.2?
2. Which version of Gapps will I need for that version of CyanogenMod?
3. If the answers to the previous questions are NO YOU CAN'T DO THAT, is there a way for me to update my Android Version to the most current, and THEN flash CyanogenMod?
I understand that there are resources out there to get this done. I've searched and found most of them. I'm just not entirely clear on which version is most appropriate for my phone, which by most standards here is somewhat pristine in that it's still running MDK, and a bit outdated in that it's running on 4.2.2. Please be gentle with me. I'm just trying to get up to speed and be productive in this forum. Thanks for your help!!
Click to expand...
Click to collapse
Make sure you have a CWM that is Kitlat capable!!!!
scrillakev said:
1) You need to download a nightly version of CM, I would advise reading the thread over there to see which one is the most stable before flashing. From what I've heard though CM has been very buggy.
http://download.cyanogenmod.org/?device=jflte&type=nightly
2) You should download the latest version of KitKit's GApps
https://goo.im/gapps/ ( gapps-kk-20140606 )
3) Happy flashing.
Click to expand...
Click to collapse
Scrillakev:
1. Ok. Does CM 11 differ from 10.x in that it isn't compatible with kit Kat? Does it matter what OS I'm running in terms of what version of CM I flash? Can you recommend any particularly stable Roms?
2. Thank you!
3. Thank you again!
npjohnson:
I installed clockworkmod recovery 6.0.4.7 through the flashify app. Can you point me towards a place I can verify that this is the correct version for kit Kat?
Thank you for your help!
onearmsysiphus said:
Scrillakev:
1. Ok. Does CM 11 differ from 10.x in that it isn't compatible with kit Kat? Does it matter what OS I'm running in terms of what version of CM I flash? Can you recommend any particularly stable Roms?
2. Thank you!
3. Thank you again!
npjohnson:
I installed clockworkmod recovery 6.0.4.7 through the flashify app. Can you point me towards a place I can verify that this is the correct version for kit Kat?
Thank you for your help!
Click to expand...
Click to collapse
6.0.4.7 is kitkat comp.
Personally, I run the Google Edition ROM, but Ive run CM11, and it works equally well, and had all the CMish stuff. *Some* issues with mms on cm.
In the CM11 thread is a link for CWM 6.0.5.0. I have successfully flashed CM11 with versions as early as 6.0.4.4. There are no KK compatible (meaning they work with everybody) but the most up to date is recommended. The latest nightlies have been very good. The only issue I currently experience is compass orientation is off by 180°. Maps and navigation work properly. I would recommend using the NC5 or NG6 modem only for best results. Don't flash a modem+nonhlos later than MDK, flashing a later modem only is fine and will cause no problems. Because of the kernel and code changes over the last couple months you will want a newer modem to prevent BT/WiFi/Mobile Data issues. Before you flash make a nandroid and be sure to clean flash since you are coming from a different ROM. As for Gapps they are all written by Google so Gapps are Gapps. I use the Paranoid Android flavor, they have also been updated just a few days ago.
Happy Flashing!!
FernBch, thank you for the excellent summary. That is all very useful info, and I feel way more confident about doing all this now thanks to you all.
OK last question - Is there a way for me to update my OS to 4.4 without losing my MDK status? If so, where can I find a procedure for doing that??
You guys rock. Seriously. Thank you!!
onearmsysiphus said:
Scrillakev:
1. Ok. Does CM 11 differ from 10.x in that it isn't compatible with kit Kat? Does it matter what OS I'm running in terms of what version of CM I flash? Can you recommend any particularly stable Roms?
2. Thank you!
3. Thank you again!
npjohnson:
I installed clockworkmod recovery 6.0.4.7 through the flashify app. Can you point me towards a place I can verify that this is the correct version for kit Kat?
Thank you for your help!
Click to expand...
Click to collapse
For a stable ROM I would recommend either the Google Play Edition ROM or The Dan's CM ROM.
Also you asked about not losing MDK, you won't lose MDK when flashing those ROMs just be sure to NOT take any OTA updates and you should be fine.
Thank you SkrillaKev! I've hunted a bit to find a thread that explains how to disable OTA but can't seem to find it.
I'm sure it'll pop up.
Hopefully soon - those daily OTA reminders are super annoying!
FernBch, regarding your 180deg compass issue, have you tried third party kernels? I've been fighting this issue for over a year and gave up. I had with stock, stock based, and any other roms I ever tried. Been running GPE rom for some time now, decided to give ktoonsez kernel a try. Compass problem solved! Worth a shot if you haven't tried it yet.
gpz1100 said:
FernBch, regarding your 180deg compass issue, have you tried third party kernels? I've been fighting this issue for over a year and gave up. I had with stock, stock based, and any other roms I ever tried. Been running GPE rom for some time now, decided to give ktoonsez kernel a try. Compass problem solved! Worth a shot if you haven't tried it yet.
Click to expand...
Click to collapse
None of the third party kernels work with the latest CM nigbtlies that I know of. When CM made the code and kernel changes they all quit working. As far as I know no one has updated them to work with the latest versions.
^^Good point. Completely forgot that change took place.
Maybe this device will get the support it needs at some point. Maybe not.
Hey guys. I posted a few days ago with a question about restoring my dad's phone to stock for warranty and this got me thinking about making some changes to my phone as well. I'm currently on Beans rom (Now called Alliance I believe) build 21. I'm thinking about trying out CM11 which I believe is Android 4.4. I went to the CM website to check out a guide on how to do this and came across this: http://wiki.cyanogenmod.org/w/Install_CM_for_i605
This guide APPEARS to be written for Note 2's that took the OTA that locked the bootloader. I still have an unlocked bootloader on Beans rom. So my question is do I need to bother with all the steps in that guide? Or is that only if bootloader is locked? Do I need Heimdall or Clockworkmod Recovery? Can I just use TWRP that I already have and do a data/cache wipe and flash the CM11 Rom? Any firmware files needed? Since my current rom is only Android 4.1.2? The Alliance rom thread says to flash MJ9 firmware before flashing their rom but I see no mention of it in the CM guide.
Thanks so much. You guys are the best!
Hello everyone,
I have recently purchased this phone from my (much) younger brother, who is requires it for school next year. I got it for only £25 used, which was a bargain in my opinion.
My plans are to upgrade it directly to Cyanogenmod 12.1 Lollipop, as I use the same ROM on my other two devices (Nexus 7 2k13, Moto G)
However, I have just found out about the "superbrick" bug which affects our devices. I ran Chainfires app, and it said that my emmc chip and firmware were known to cause issues. The phone is currently still on android version 4.0.3 (ics), so am I right in saying that the superbrick bug is present on this phone currently?
Therefore, what is the best way that I can safely upgrade the phone to Cyanogenmod 12.1, without experiencing this bug? In addition, does CM 12 have the "fix" for superbrick, so that it will not happen again in the future?
Finally, I have read a bit about system partitioning. I would quite like to not have to do this, so can I just Flash CM 12 with the MINI GApps, and not run into any issues?
Thanks a lot for the support, and I look forward to receiving and answer
xN1ghtShadoWx said:
Hello everyone,
I have recently purchased this phone from my (much) younger brother, who is requires it for school next year. I got it for only £25 used, which was a bargain in my opinion.
My plans are to upgrade it directly to Cyanogenmod 12.1 Lollipop, as I use the same ROM on my other two devices (Nexus 7 2k13, Moto G)
However, I have just found out about the "superbrick" bug which affects our devices. I ran Chainfires app, and it said that my emmc chip and firmware were known to cause issues. The phone is currently still on android version 4.0.3 (ics), so am I right in saying that the superbrick bug is present on this phone currently?
Therefore, what is the best way that I can safely upgrade the phone to Cyanogenmod 12.1, without experiencing this bug? In addition, does CM 12 have the "fix" for superbrick, so that it will not happen again in the future?
Finally, I have read a bit about system partitioning. I would quite like to not have to do this, so can I just Flash CM 12 with the MINI GApps, and not run into any issues?
Thanks a lot for the support, and I look forward to receiving and answer
Click to expand...
Click to collapse
First thing I would do is upgrade to jellybean stock. The kernel you have(4.0.3) is vulnerable to the superbrick bug, and rooting the phone from 4.1.2 is easier/safer. Once you do this, you almost never need to worry about this bug again, as the newer kernels are safe. From there use philz kernel to root the phone. Just follow the steps in that thread and match the kernel to the rom. Have a good read, but particularly the 2nd and 3rd posts. Then you need a "kitkat compatible" recovery to flash cm12. You can use the newer philz recovery from HERE. Just flash it then reboot straight back to recovery. Then flash cm12 and gapps etc as normal
Bootloader
Hi, I have recovery installed fine, but inside the CM 12 rom zip, I see a boot.img. If I brick my phone whilst installing the rom, can I still unbrick with the offical 4.1.2 firmware via odin?
Thanks!
xN1ghtShadoWx said:
Hi, I have recovery installed fine, but inside the CM 12 rom zip, I see a boot.img. If I brick my phone whilst installing the rom, can I still unbrick with the offical 4.1.2 firmware via odin?
Thanks!
Click to expand...
Click to collapse
Don't worry about that. That is just the kernel(not bootloader if thats what you thought). Yes it is fine to flash stock firmware if you need.
Hi my step son has this phone running blisspop 5.1.1 I want to update his phone to marshmallow. Can I just flash the latest cm 13 or should I odin back to stock and update that way then go through the rooting process? Im not sure if the bootloader and radio and kernel should be updated the stock way first.
I do know with my note 2 I could just flash the latest cm and flash the radio seperate. But this phone is a little foreign to me.
mojorisin7178 said:
Hi my step son has this phone running blisspop 5.1.1 I want to update his phone to marshmallow. Can I just flash the latest cm 13 or should I odin back to stock and update that way then go through the rooting process? Im not sure if the bootloader and radio and kernel should be updated the stock way first.
I do know with my note 2 I could just flash the latest cm and flash the radio seperate. But this phone is a little foreign to me.
Click to expand...
Click to collapse
Currently all the CM-13.0 based ROMs cannot boot with the official marshmallow bootloader. So it would be better to just clean flash the latest CM 13
Good thing I asked. I'm sure the cm team will figure that out at some point. It's actually the reason I asked because I remember on my note 2 going from JB mr1 to mr2 Samsung implemented Knox and sxrewed up everything. Dam girls phone was stock so I did the over he air update this morning. Oh well she doesn't really care anyway.
it's not like you'll wait long for CM to work with the latest bootloader https://review.cyanogenmod.org/#/c/146515
EDIT: it's not like you cant update either, just install CM13 WITHOUT updating stock (which will include the bootloader), aka if you're G900TUVS1FOL1 or older, then CM13 (marshmallow) should work as it has been for the last 5 months