Related
Hi all
Just wondering if anyone has a copy of the official Australian Razr M release firmware.
77.176.16.XT905.Telstra.en.AU
Always good to have a fallback system image!
Thanks in advance
wintermute000 said:
Hi all
Just wondering if anyone has a copy of the official Australian Razr M release firmware.
77.176.16.XT905.Telstra.en.AU
Always good to have a fallback system image!
Thanks in advance
Click to expand...
Click to collapse
Hi, I am also looking for the same firmware, managed to root the phone using Motofail2go but unable to use Clockworkmod to backup or load other firmware. Now when I try to Erase the phone I get the AP Fastboot Flash Mode (s) Device is looked Boot Failure. Luckily pressing the power button gets me back to a working phone. I have also unrooted the phone using DoomLord unrooting script but still the same boot up error. I know now the bootloader is locked by Motorola, this is why I need the original Telstra firmware.
I will donate $ 20 by Paypal to anyone that posts a working 77.176.16.XT905.Telstra.en.AU firmware that I can use and fixes the boot issue.
ozsultan said:
Hi, I am also looking for the same firmware, managed to root the phone using Motofail2go but unable to use Clockworkmod to backup or load other firmware. Now when I try to Erase the phone I get the AP Fastboot Flash Mode (s) Device is looked Boot Failure. Luckily pressing the power button gets me back to a working phone. I have also unrooted the phone using DoomLord unrooting script but still the same boot up error. I know now the bootloader is locked by Motorola, this is why I need the original Telstra firmware.
I will donate $ 20 by Paypal to anyone that posts a working 77.176.16.XT905.Telstra.en.AU firmware that I can use and fixes the boot issue.
Click to expand...
Click to collapse
Out of curiosity what CWM did you try to flash?
You do know that you CAN unlock your bootloader right? exact same procedure as Razr I. Yeah the moto website doesn't mention telstra Razr M model blah blah blah it works as confirmed by Ausdroid editor in this thread.
http://forum.xda-developers.com/showthread.php?p=33777574#post33777574
wintermute000 said:
Out of curiosity what CWM did you try to flash?
You do know that you CAN unlock your bootloader right? exact same procedure as Razr I. Yeah the moto website doesn't mention telstra Razr M model blah blah blah it works as confirmed by Ausdroid editor in this thread.
http://forum.xda-developers.com/showthread.php?p=33777574#post33777574
Click to expand...
Click to collapse
Hi I used CWM from Google Play and selected the Motorola Photon Q from CWM, maybe a mistake but no RAZR M was listed.
I registerd on the Motorola site to get the unlock key but there is a quite a process to complete the excersice. Rather just have my stock rom back and forget about rooting for now.
ozsultan said:
Hi I used CWM from Google Play and selected the Motorola Photon Q from CWM, maybe a mistake but no RAZR M was listed.
I registerd on the Motorola site to get the unlock key but there is a quite a process to complete the excersice. Rather just have my stock rom back and forget about rooting for now.
Click to expand...
Click to collapse
I dunno how experienced you are at this so I apologise if I'm getting mixed up here but:
a.) You will NEVER flash ANY RECOVERY aside from stock without unlocking your bootloader, and you don't flash CWM from google play (not even sure what you're referring to!!!). You CAN flash recoveries from rom manager if your bootloader is unlocked and you have root.
b.) The only recovery I've seen around the place confirmed for Razr M (unlocked bootloader) is this one
http://aosp.us/?p=294
If you think the steps in unlocking bootloader is too hard you shouldn't even attempt it. Sorry to say but thats pretty much standard stuff for flashing recoveries etc. !!!! (having drivers installed, using fastboot via command line etc.)
wintermute000 said:
I dunno how experienced you are at this so I apologise if I'm getting mixed up here but:
a.) You will NEVER flash ANY RECOVERY aside from stock without unlocking your bootloader, and you don't flash CWM from google play (not even sure what you're referring to!!!). You CAN flash recoveries from rom manager if your bootloader is unlocked and you have root.
b.) The only recovery I've seen around the place confirmed for Razr M (unlocked bootloader) is this one
If you think the steps in unlocking bootloader is too hard you shouldn't even attempt it. Sorry to say but thats pretty much standard stuff for flashing recoveries etc. !!!! (having drivers installed, using fastboot via command line etc.)
Click to expand...
Click to collapse
Hi Thanks for your help and comments, I have rooted my old HTC Desire using Unrevoked in the past and flashed a Cyanogen mod and a LeeDroid mod without any problems so I thought I would try the RAZR M. Maybe the boot loader was different or not locked. I was able to go into recovery mode and select the cooked zipped roms from the SD card. I can not find any roms for the Aussie RAZR M either, I guess that is what you are looking for and concerned about updating the the JB from for the Verizon version as the radio may be different.
Anyway, the Motorola UI is not so bad and I especially like to start page with the circles. Hopefully JB update will come OTA soon. I hope that the JB update will return my phone to stock and the Bootloader error does not come up anymore. All is fine for now but if I have to wipe my phone and start again I can not do it. Have you ended up using your Motorola unlock code to unlock the boot loader ?
I am not completely a newbie
ozsultan said:
Hi Thanks for your help and comments, I have rooted my old HTC Desire using Unrevoked in the past and flashed a Cyanogen mod and a LeeDroid mod without any problems so I thought I would try the RAZR M. Maybe the boot loader was different or not locked. I was able to go into recovery mode and select the cooked zipped roms from the SD card. I can not find any roms for the Aussie RAZR M either, I guess that is what you are looking for and concerned about updating the the JB from for the Verizon version as the radio may be different.
Anyway, the Motorola UI is not so bad and I especially like to start page with the circles. Hopefully JB update will come OTA soon. I hope that the JB update will return my phone to stock and the Bootloader error does not come up anymore. All is fine for now but if I have to wipe my phone and start again I can not do it. Have you ended up using your Motorola unlock code to unlock the boot loader ?
I am not completely a newbie
Click to expand...
Click to collapse
No waiting for
- backup stock image for obvious reason!
- something to actually flash to appear!
BTW check this thread http://forum.xda-developers.com/showthread.php?p=33789915#post33789915 the comments from apacheo who has confirmed unlock and recovery install (TWRP though not CWM)
wintermute000 said:
No waiting for
- backup stock image for obvious reason!
- something to actually flash to appear!
BTW check this thread http://forum.xda-developers.com/showthread.php?p=33789915#post33789915 the comments from apacheo who has confirmed unlock and recovery install (TWRP though not CWM)
Click to expand...
Click to collapse
Thanks. did you mean now waiting, I guess u could mean either as apacheo has something available ? Looks like apacheo might be getting my $20 via paypal. So with the recommendation from apachio do I still have to unlock the booter. If yes, can this only be done via the Motorola site unlock code?
Will the stock Telstra image from apacheo fix my boot failure issue ? Will I need to have a rooted RAZR M and loader (TWRP) to load the file?
Thanks appreciate your help.
You shouldn't need to unblock bootloader to push the stock image. If its stock you should be able to flash it.
The whole point of unlocking is to be able to push NON OFFICIAL stuff however not having seen that image I can't confirm. e.g. Maybe because he extracted it himself its not signed like an official moto image so you may need to unlock.
If he has extracted a fastboot image it will INCLUDE stock recovery and you flash it via fastboot command line utility. Thats better than a ROM you have to flash with a recovery because it lets you roll back even if you screw your recovery.
All in all, ask him yourself, I'm only speculating based on first principles
BTW android manufacturers have gotten a lot more anal since desire, and yeah back then a lot of stuff was unlocked, now pretty much only Sammy ships unlocked bootloaders. I'd say that back then you could probably unlock the bootloader pretty easily so you don't remember jumping through hoops.
ozsultan said:
Thanks. did you mean now waiting, I guess u could mean either as apacheo has something available ? Looks like apacheo might be getting my $20 via paypal. So with the recommendation from apachio do I still have to unlock the booter. If yes, can this only be done via the Motorola site unlock code?
Will the stock Telstra image from apacheo fix my boot failure issue ? Will I need to have a rooted RAZR M and loader (TWRP) to load the file?
Thanks appreciate your help.
Click to expand...
Click to collapse
The stock recovery img is probably not going to fix your device.. sounds like you probably need the boot image, but how'd you manage to corrupt that?
apacheo said:
The stock recovery img is probably not going to fix your device.. sounds like you probably need the boot image, but how'd you manage to corrupt that?
Click to expand...
Click to collapse
Hi Apacheo, thanks for the reply, my procedure was as per my first post yesterday. Using Clockworkmod Rom Manger app I picked the Motorola Photon Q for Flash Alternate Recovery as this was the only close Motorola phone to the Razr M. (MY BAD) Maybe that was the problem. I tried to back up the existing rom using Clockworkmod but again got the AP Fastboot Flashmode error.
How do I get the boot image and load that? Meanwhile I have unrooted the phone and can use it. Just can't do a factory data reset and start with a new slate if I have to. Just hangs on the AP Fastboot Flashmode (S) black and white Device is locked screen.
Thanks, I was hoping to lose that $20 to u.
Flashing the stock recovery using fastboot is probably the best start.
I'll upload the recovery image and post the URL here. Wait a moment.
Sent from my XT905 using xda app-developers app
---------- Post added at 08:01 PM ---------- Previous post was at 07:56 PM ----------
Here's the stock recovery image:
http://db.tt/A5veTD0u
Sent from my XT905 using xda app-developers app
apacheo said:
Flashing the stock recovery using fastboot is probably the best start.
I'll upload the recovery image and post the URL here. Wait a moment.
Sent from my XT905 using xda app-developers app
---------- Post added at 08:01 PM ---------- Previous post was at 07:56 PM ----------
Here's the stock recovery image:
http://db.tt/A5veTD0u
Sent from my XT905 using xda app-developers app
Click to expand...
Click to collapse
Thanks Apacheo, I assume I can use RSD Lite 5.4.6.4, how to open the 10 MB RAW file ? I know RAW as a picture file from a camera. Does the 10 MB file contain the whole Telstra ROM ?
ozsultan said:
Thanks Apacheo, I assume I can use RSD Lite 5.4.6.4, how to open the 10 MB RAW file ? I know RAW as a picture file from a camera. Does the 10 MB file contain the whole Telstra ROM ?
Click to expand...
Click to collapse
No idea about RSDLite, you use Fastboot to flash that, and it's a raw dump of the Recovery partition. Flash it like this:
fastboot flash recovery recovery-file.raw
The extension is irrelevant, you could equally rename it .img (which is the standard for fastboot files) but it won't make any difference. It's not the whole Telstra ROM, just the recovery partition. The whole ROM would be something like 600 mb, and as I've modified my system partition (i.e. rooted it) you may not want that, and with only 3G internet, I couldn't upload it anyway
apacheo said:
No idea about RSDLite, you use Fastboot to flash that, and it's a raw dump of the Recovery partition. Flash it like this:
fastboot flash recovery recovery-file.raw
The extension is irrelevant, you could equally rename it .img (which is the standard for fastboot files) but it won't make any difference. It's not the whole Telstra ROM, just the recovery partition. The whole ROM would be something like 600 mb, and as I've modified my system partition (i.e. rooted it) you may not want that, and with only 3G internet, I couldn't upload it anyway
Click to expand...
Click to collapse
Hi apache, thanks again, HELP.
OK, I press vol up and vol down and press the power key at the same time. I get the menu boot load selection, availlable boot modes if I pick recovery or AP fastboot I still get back to the AP Fastboot Flashmode (s) screen Device is locked Status Code:0
I assume I get into recovery mode and use your raw file from my SD card to update the recovery partition. What am I doing wrong?
incorrect, you flash via fastboot command line in.... fastboot mode (not recovery mode)
Hey,
I'm hoping to help you guys out. First I have a couple of questions.
1) is your device bootloader unlocked?
2) are you rooted?
If so I have methods to create a backup XML file for you.
jimmydafish said:
Hey,
I'm hoping to help you guys out. First I have a couple of questions.
1) is your device bootloader unlocked?
2) are you rooted?
If so I have methods to create a backup XML file for you.
Click to expand...
Click to collapse
If you have methods to recover an Australian modem IMG (instead of the Verizon-based one) then I'm all ears.. because until I find an AU modem, my phone is now completely unusable.. whoops :/
apacheo said:
If you have methods to recover an Australian modem IMG (instead of the Verizon-based one) then I'm all ears.. because until I find an AU modem, my phone is now completely unusable.. whoops :/
Click to expand...
Click to collapse
We can work on this, do you have access to another AU M? Plus this may be easier via gtalk or email.
jimmydafish said:
We can work on this, do you have access to another AU M? Plus this may be easier via gtalk or email.
Click to expand...
Click to collapse
If I had another, I'd just root it and dd the modem image off and flash it on the broken one.. sadly I don't
I managed to screw it up by flashing the VZW ICS stock, so I could get the JB update on.. I deliberately didn't flash the modem from the VZW ICS stock, and I modified the JB update so it wouldn't apply any changes to the modem... but seemingly, I missed a couple of lines (checking the updater-script, I missed a couple that messed with the modem) so it's completely wrecked. Says the SIM is invalid, and won't detect or connect to any UMTS or GSM carriers here.
If someone else with a rooted Aussie RAZR M is able to step up to assist, it'd be great.
I'll also PM you my details jdf.
Hi
First of all, this is don't habitual for me since I used to read related post (and more if an update has just arrived) but I just could not find an specific instructions (sorry if I am being too demanding) to go from custom 4.2.1(PA) to stock and finish with rooted 4.2.2, there are a lot of several procedures or recommendations to perform the update :S
well this is what I have planed
- return to stock 4.2.1 (using nexus toolkit)
- download and flash manually the update to 4.2.2 (first try to use the ota update option)
- get root... how??? lol
- restore my apps/data
Since I will return to stock I think I will lose root, that is ok but only if i can root the nexus again, Will I be able to get root on 4.2.2? or I have to root in 4.2.1 and keep it (in some way) at the time I update to 4.2.2
Srryforbad/basicenglish:silly:
Rooting every nexus is the same. Flash/boot a custom recovery and flash supersu.zip. it doesn't matter what OS version its on.
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
Rooting every nexus is the same. Flash/boot a custom recovery and flash supersu.zip. it doesn't matter what OS version its on.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
ok, I think I have missing that simple thing...
I don't have to worry about get the bootloader locked again therefore I just have to flash a recovery and SU when I have my N7 on 4.2.2, but...flash from... bootloader I guess, well, I will check that.
Thanks!
Learn the manual way of doing it and don't rely on toolkits. There are many tutorials walking you through the entire process
Sent from my Nexus 7 using Tapatalk HD
SLver said:
ok, I think I have missing that simple thing...
I don't have to worry about get the bootloader locked again therefore I just have to flash a recovery and SU when I have my N7 on 4.2.2, but...flash from... bootloader I guess, well, I will check that.
Thanks!
Click to expand...
Click to collapse
To elaborate on Pirateghost's points...
After flashing the 4.2.2 update... you will lose your recovery (CWM or TWRP)... but getting your recovery back is also part of how you (re)gain root.
As I have posted elsewhere...
Rooting is really simple.
(You will need an unlocked bootloader for this).
Get a custom recovery .img for your device...
Either CWM - http://www.clockworkmod.com/rommanager
...or TWRP - http://www.teamw.in/project/twrp2/103,
...it matters little which...
-----------
fastboot flash it.
-----------
Get Chainfires SU .zip package here http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Flash it using the custom recovery you've just fastboot flashed..
Reboot... and you're rooted.
-----------
...and that's it basically... you have root, a custom recovery from which you can flash ROMs, perform nandroid backups, etc.
But fastboot is the key... learn how to use it, and you will never need to be reliant on anybodies toolkit.
Rgrds,
Ged.
hey all,
I'm a complete noob when it comes to rooting
I've been searching online on how to root a nexus 4 using a mac.. every single guide is different, some skip the unlocking bootloader part, some skip other parts, and most guides are just outdated.
I'm running on absolute stock, 4.4.2.
What's the best (and most current) guide out there? I'm interested in rooting my phone mainly so I can get LTE access.. do no care too much for non stock ROMS (not yet at least)
I think this is the easiest for noobs: http://forum.xda-developers.com/showthread.php?t=1999065 . It's a tool that will do all the work for you.
Sent from my Nexus 4 using Tapatalk
update:
I set up adb on my mac and unlocked bootloader, that was easy.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2018179
so now I'm confused about the whole Rom part.. which one do I download? There's a ROMs column, a stock recovery, and stock touch recovery. What are those?
You don't have to install another ROM. You can just download the recovery (CMW for mako touch or non touch) in the post. Also download the su zip tot get root acces.
Sent from my Nexus 4 using Tapatalk
Yuoko5 said:
You don't have to install another ROM. You can just download the recovery (CMW for mako touch or non touch) in the post. Also download the su zip tot get root acces.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ah, so the touch column is all the 'stock' roms. how do I know that it's the latest 4.4.2 stock rom? will be able to do OTA updates after I flash the mako touch?
If you're device is rooted I think you won't be able to install OTA updates from google anymore. But, you can flash these stock roms easily. I'm sure people make flashable zips of every new version of Android. About the columns: ROMs=you can download custom roms (you don't need that); Recovery and recovery touch is basically the same thing. The difference is one recovery can be controlled with the touchscreen and the over with the volume and power button. It's just what you like best.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
beegbear said:
ah, so the touch column is all the 'stock' roms. how do I know that it's the latest 4.4.2 stock rom? will be able to do OTA updates after I flash the mako touch?
Click to expand...
Click to collapse
Get it?
Sent from my Nexus 4 using Tapatalk
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
beegbear said:
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
Click to expand...
Click to collapse
Cwm(clockworkmod recovery) is a side load which helps u to flash different ROMs and zip files. It also helps u to wipe battery stats, partition sd card(not with case of n4)
Factory image is the stock ROM that Google provide that u r having in your nexus 4
Sent from my Nexus 4 using xda app-developers app
beegbear said:
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
Click to expand...
Click to collapse
And regarding your previous question of OTA updates, You'll have to flash the stock recovery if you're on CWM or TWRP (Team Win Recovery Project - Many people recommend this one, I use it myself) and you shouldn't have made any changes to the system files of your stock ROM.
You will receive the OTA if you have modified anything in system, you just won't be able to flash it. And you can also flash the OTA with TWRP instead of stock recovery. Root does not matter, although it will be lost after you update. Before updating, also make sure you're not using a custom kernel. Kernel: The "thing" that android runs on. It's the heart of the OS, you could say. No kernel, no boot.
Lt.Win said:
And regarding your previous question of OTA updates, You'll have to flash the stock recovery if you're on CWM or TWRP (Team Win Recovery Project - Many people recommend this one, I use it myself) and you shouldn't have made any changes to the system files of your stock ROM.
You will receive the OTA if you have modified anything in system, you just won't be able to flash it. And you can also flash the OTA with TWRP instead of stock recovery. Root does not matter, although it will be lost after you update. Before updating, also make sure you're not using a custom kernel. Kernel: The "thing" that android runs on. It's the heart of the OS, you could say. No kernel, no boot.
Click to expand...
Click to collapse
So let me make sure I'm following this..(sorry, I'm sure you saw such questions countless times before)
CWM (or TWRP) is a custom recovery instead of the stock 'recovery' option that's found in the bootloader. If I choose to go with either CWM or TWRP, how much of an issue is it to flash back to stock recovery? would it be done through ADB the same way the custom recovery was flashed in the first place?
As I understand.. the first thing I should do after unlocking the bootloader (already done) and flashing a custom recovery (not done yet) is to create a backup through the custom recovery. Does that back up the radios as well? If I decide to flash the all in one LTE zip and it doesn't work or what not.. will using that recovery flash back the old radios?
Now to the actual rooting..
so flashing super su is what actually does the root? How would I go about returning to complete stock if I ever need to? (stock recovery, remove root, lock bootloader)
When flashing a different ROM, how come I need to make a backup of my apps? what if I want to start completely fresh? Would I not be able to go to the playstore after flashing a custom rom and downloading everything I need? or there is not going to be a play store after flashing? (that's why GAPPS are needed?)
so I rooted and flashed the hybrid radio, works like charm!
I answered most of my own questions in the post above just by going through the process.
What happens if I decide to factory reset through settings? will CWM stay? will the root stay? will the lte fix stay?
Yes...yes...yes.....you really should take advantage of the countless guides people have written explaining all of your questions.
Sent from my Nexus 4 using XDA Premium 4 mobile app
TLDR: Need KitKat bootloader. Can it be installed on a rooted, unlocked device?
I am using CM11 on my phone (Droid Razr M/XT-907). When I try to install cyanogenmod updates using the built-in function, the installation always fails due to my bootloader being outdated. Apparently I still have the bootloader from jelly bean and I need the KitKat bootloader version. Now that my phone is unlocked and has a custom OS and recovery, is there any way to obtain the newest bootloader version and get it installed on my phone?
The only way I know is to rsd to kitkat stock then install. My other devices we just installed the kernel but I haven't seen that here. You are unlocked so you are able to flash down and back up.
Sent from my XT907 using XDA Free mobile app
mmmrower said:
TLDR: Need KitKat bootloader. Can it be installed on a rooted, unlocked device?
I am using CM11 on my phone (Droid Razr M/XT-907). When I try to install cyanogenmod updates using the built-in function, the installation always fails due to my bootloader being outdated. Apparently I still have the bootloader from jelly bean and I need the KitKat bootloader version. Now that my phone is unlocked and has a custom OS and recovery, is there any way to obtain the newest bootloader version and get it installed on my phone?
Click to expand...
Click to collapse
There is this if you don't want to RSD up to KitKat other wise everything you need to update to KitKat is here courtesy of ATTACK
We cannot teach people anything; we can only help them discover it within themselves.
RSD?
mmmrower said:
RSD?
Click to expand...
Click to collapse
RSD lite is the tool used to flash the stock firmware on a Motorola device its like Odin that the Samsung device's use... Read through the XDA thread I linked in the prior post for a better understanding of the procedure
We cannot teach people anything; we can only help them discover it within themselves.
So my next question is:
Within the cyanogenmod .zip that you would normally flash to your device, there is a file called "boot.img." Is this file normally flashed to the boot partition when you install cyanogenmod?
In other words, if I manually did a "fastboot flash boot boot.img", would that replace the bootloader? Or does cyanogenmod not include bootloader data? I've been scouring the web for hours trying to find this out.
To be honest I'm not sure what flashing just the boot image would do... I don't believe it would effect the boot loader... We would have to wait on a more experienced member... Flashing the KitKat firmware doesn't take long at all and you could always back up your app date with your desired back up app
We cannot teach people anything; we can only help them discover it within themselves.
The boot.img and the boot loader are two different things. You'll need to FXZ/update to get the new BL.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
The boot.img and the boot loader are two different things. You'll need to FXZ/update to get the new BL.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I just finished flashing [what I think] is stock firmware. Now, if I update OTA, won't that upgrade me to an "unlockable" bootloader? (whatever the latest one is).
My bootloader is currently unlocked, if that means anything.
[edit] I OTA updated anyways. And I don't think it re-locked my bootloader. But now it keeps overwriting clockworkmod every time I "fastboot" clockworkmod into place. Can't seem to reboot into recovery straight from fastboot mode anymore. The power+volume up combo doesn't work. Maybe that's a sign that the bootloader's locked? I still get the motorola "Bootloader Unlocked" screen every time it boots up.
If your boot loader was already unlocked it will remain unlocked
Sent from my XT907 using XDA Free mobile app
I'm tracing it back to the root of the problem: why do you *need* to upgrade to KK BL? CM11 is also available for JB BL and as for my experience half a month ago, it's more bugfree than the KK BL version (KK BL had WiFi & GPS bugs, don't know what's the situation now).
I see you've already upgraded... So please try out latest CM11 KK BL (moto_msm8960) and see if it has WiFi, GPS or BT issues. If yes, you might wanna fall back to JB BL.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
How would I "fall back" to JB bl?
I'm currently stuck trying to get any sort of ROM installed. It seems the stock image that I flashed re-writes the recovery partition every time I flash CWM. So I can't even boot to recovery anymore. Until I get that figured out, well, we'll see lol.
Know where I could get a system.img and boot.img of ANY functional cyanogen ROM?
I got CM to install ONCE from recovery (the first time I installed it). Subsequent attempts at installing the snapshot builds failed and complained that I needed the kitkat bootloader.
[edit]And now adb doesn't even work. hahahaha
[edit]Got everything working. Seems to be pretty stable.
[edit]Back when I first installed CM, I had the JB BL and installed the KK cyanogen. I had a bug with my wifi, but it was due to me installing incorrectly. Otherwise I didn't find any issues.
Thanks for all your help everyone.
Q&A for [CM12] [Lollerpop] JFLTEATT Nightly Kangs
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [CM12] [Lollerpop] JFLTEATT Nightly Kangs. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
noremac258 said:
No love for the jfltecan?
Click to expand...
Click to collapse
Yea I tried even using the jflteatt philz to trick it but the data part failed and system was success. So I didn't bother trying to boot. You can still use Antares however, it is unified.
I am wondering if I can flash Antares and then dirty flash this over to get the system part, I just don't wanna have to go through Odin to stock rigamarole.
cm-12-20141124.1217-jflteatt
Can't get it to boot on my AT&T S4. It tries, black screens, then reboots into AD recovery automatically.
I'm unlocked using T-mobile, but I don't think that should matter.
TWRP v2.7.1.0-- Using stock slot with safestrap disabled (no success on making new slots with safestrap enabled, either).
Lollerpop CM12 - AT&T Samsung Galaxy S4 (SGH-i337) - Unauthorized
Hi,
I tried replying to the CM12 Lollerpop thread but even though I have been utilizing XDA for YEARS, I am still considered a noob due to lack of posts.
Anyway, I just wanted to let the awesome developers know that I tried installing CM12 Lollerpop through TWRP, on my AT&T Samsung Galaxy S4 (SGH-i337) that I have installed ROMs on hundreds of times. For some strange reason that I cannot explain, with the Beta version of CM12 right after I power on the device after installing I see an ! and "AT&T UNAUTHORIZED SOFTWARE HAS BEEN DETECTED" and device went to a black screen after 5 -> 10 seconds. Fortunately I was still able to get back into TWRP after a reboot and home + volume up and successfully completed a restore from a 4.4.4 Beanstalk complete backup I took prior to testing CM12 installation / boot, etc.
I would greatly appreciate it if someone could A) explain why this is happening with CM12 and more importantly B) how to get around this annonying blocking message.
Kind Regards,
Jason Vincent
Sr Integration & Validation Engineer
VoIP SME
jkvincent said:
I would greatly appreciate it if someone could A) explain why this is happening with CM12 and more importantly B) how to get around this annonying blocking message.
Click to expand...
Click to collapse
It sounds like you did not flash a Loki-Doki package. Search the AT&T Galaxy S4 forum and you can find it. You need to flash this after you flash your ROM (or anything else) to trick your phone into thinking you have stock software. Some ROMS have this included, which is probably why you have never had to flash this package before, but I would say that most don't. And no, even if the ROM has a Loki package included inside of it, it doesn't hurt to flash it twice so I end up flashing Loki-Doki a lot.
Sent from my GT-I9505G using XDA Free mobile app. Press "Thanks" if I helped!
Unauthorized - Loki & Safestrap
Hi,
I downloaded loki-doki.zip, wiped, installed CM12*.zip, gapps-lp*.zip and applied loki-doki.zip to find the annoying "Unauthorized..." message again. I tried installing loki by itself after a clean reboot. I tried with wiping dalvik + cache and without. Same thing.
After reading up on Loki, I ran into a bit that stated Loki is designed for 4.4.2 and for 4.4.4+ I should be using Safestrap. I downloaded the Safestrap*.apk file, installed it, granted root access and installed Recovery (says Safestrap is built off TWRP).
The first thing I noticed was the TWRP version was still 2.8.1 (I also updated TWRP prior). I went through the same process without Loki. Same "Unauthorized..." message. Tried Loki after. Same message.
I am not sure at this point but I have never had much luck installing Recoveries while being booted into Android. I have always had to install from a .zip in Recovery or use Odin. I'm not convinced Safestrap updated or even if it is the right way to go. What would be really sweet is if the Devs could wrap whatever is needed to get around the "Unauthorized...", into the CM12 installation. Maybe that is asking for too much. I need to still research Safestrap and it is getting late. I do appreciate you pointing out Loki because it got me pointed in the right direction. I kind of forgot about it with the ROMs being Lok'd.
Kind Regards,
Jason Vincent
Sr Integration & Validation Engineer
VoIP SME
For those who are on AT&T, this is how I got 11-30 to work. Worked perfectly, except the battery drain.
Install cm12 using TWRP (shouldn't matter, but I used 2.8.0.1), flash gapps if you want, flash ktoonsez aosp 5.0 kernel just updated few days ago. No loki patch needed. Good luck.
Didn't get a chance to test bluetooth, but camera seemed to work.
I am using a AT&T s4 (no safestrap)
Hi, Try installing a kernel. it work for me. Alicard or ktoonz.
Question here
I have the sgh-i337 rooted on stock firmware 4.2.2 and have installed shabbyPenguin recovery (I know it's an old recovery but it seems to work fine). I am able to flash this ROM like my bootloader is unlocked or do I need to do something else like flash the loki-doki.zip file?
Thanks in advance!
StoneyJSG said:
I have the sgh-i337 rooted on stock firmware 4.2.2 and have installed shabbyPenguin recovery (I know it's an old recovery but it seems to work fine). I am able to flash this ROM like my bootloader is unlocked or do I need to do something else like flash the loki-doki.zip file?
Thanks in advance!
Click to expand...
Click to collapse
I'm not sure what you said in that last line. But I'm guessing you mean to ask if you can flash this or not. Simple answer, no.
Long answer: I'm not sure what your device exactly is, or what you have done with it. I'm guessing it's not an MDL or earlier device to which the loki-doki patch applies. So using that on your device could be bad idea. I'm assuming the recovery you listed is a modified version for safestrap users. In which case, you can only run touch wiz based roms or Google play edition (safestrap), which this is neither of.
thesummoner101 said:
I'm not sure what you said in that last line. But I'm guessing you mean to ask if you can flash this or not. Simple answer, no.
Long answer: I'm not sure what your device exactly is, or what you have done with it. I'm guessing it's not an MDL or earlier device to which the loki-doki patch applies. So using that on your device could be bad idea. I'm assuming the recovery you listed is a modified version for safestrap users. In which case, you can only run touch wiz based roms or Google play edition (safestrap), which this is neither of.
Click to expand...
Click to collapse
Sorry for my typos. I was asking if I can flash this rom like I have an unlocked bootloader since I am on the MDL firmware Android 4.2.2 and can use LOKi. I have ShabbyPenguin's version of Clockwork mod recovery installed.
StoneyJSG said:
Sorry for my typos. I was asking if I can flash this rom like I have an unlocked bootloader since I am on the MDL firmware Android 4.2.2 and can use LOKi. I have ShabbyPenguin's version of Clockwork mod recovery installed.
Click to expand...
Click to collapse
Okay, if you're on MDL, then you have a couple of options. Here's the process that has worked for me without issue. I'm also on MDL. I'm using twrp but prices should be similar. This could also be a good time to update the recovery, it's really easy.
1) download rom to external sd
2) download PA micro 5 gapps
3) download ktoonsez 5.0 att aosp 12-9 kernel
4) factory reset, wipe dalvik/cache
5) install rom
6) install kernel
7) boot then let it settle and reboot into recovery
8) install gapps
9) boot and let it settle
BTW, our bootloader isn't exactly unlocked, it's just hacked/patched/fooled to think it is. It doesn't seem any different than an unlocked one, except that it needs loki patch, patched recovery, or AT&T kernel.
Good luck.
thesummoner101 said:
Okay, if you're on MDL, then you have a couple of options. Here's the process that has worked for me without issue. I'm also on MDL. I'm using twrp but prices should be similar. This could also be a good time to update the recovery, it's really easy.
1) download rom to external sd
2) download PA micro 5 gapps
3) download ktoonsez 5.0 att aosp 12-9 kernel
4) factory reset, wipe dalvik/cache
5) install rom
6) install kernel
7) boot then let it settle and reboot into recovery
8) install gapps
9) boot and let it settle
BTW, our bootloader isn't exactly unlocked, it's just hacked/patched/fooled to think it is. It doesn't seem any different than an unlocked one, except that it needs loki patch, patched recovery, or AT&T kernel.
Good luck.
Click to expand...
Click to collapse
Awesome! Thanks dude. Since I am partial to CWM, I was going to flash PhilZ touch recovery, but from what I have read the ShabbyPenguin recovery is supposed auto loki upon flashing. I also have the loki-doki.zip file for flashing as well just in case.
How do I even flash CM12 on my device?
My SGH-I337 has Lollipop 5.0.1 and it is rooted no custom recovery.
Please help
ahmedbatty said:
How do I even flash CM12 on my device?
My SGH-I337 has Lollipop 5.0.1 and it is rooted no custom recovery.
Please help
Click to expand...
Click to collapse
How you installed custom recovery in S4 i337 at & t?
Jordan Gonzalez said:
How you installed custom recovery in S4 i337 at & t?
Click to expand...
Click to collapse
I found out that I can't flash any custom ROM or recovery if I have the latest bootloader, so it's locked