Develop Bugs

CM9 Updated CWM automatically?

So I flashed CWM 5.0.2.7 with Odin back in June, and have been running CM9, updating to nightly builds every couple weeks, and RCs as they come out. I last flashed the 8/8 nightly build, and when I rebooted my phone in to recovery to go back to RC2, CWM v6.0.1.1 was what came up. Is that normal? I thought that recovery had to be flashed using USB.

electromage said:
So I flashed CWM 5.0.2.7 with Odin back in June, and have been running CM9, updating to nightly builds every couple weeks, and RCs as they come out. I last flashed the 8/8 nightly build, and when I rebooted my phone in to recovery to go back to RC2, CWM v6.0.1.1 was what came up. Is that normal? I thought that recovery had to be flashed using USB.
Click to expand...
Click to collapse
Nope... flashing that nightly installed the latest cwm for you... you're good to go...
Two roads diverged in a yellow wood....

electromage said:
So I flashed CWM 5.0.2.7 with Odin back in June, and have been running CM9, updating to nightly builds every couple weeks, and RCs as they come out. I last flashed the 8/8 nightly build, and when I rebooted my phone in to recovery to go back to RC2, CWM v6.0.1.1 was what came up. Is that normal? I thought that recovery had to be flashed using USB.
Click to expand...
Click to collapse
Has to be flashed originally from the USB, but once you have a custom recovery, it can update thru ROM zips. They include the recovery binary, so if you have the version it includes already, nothing really happens to that, but if you don't, it updates.

flash gone wrong? twrp to cwm?

Hey everyone, I had just flashed cyanogen 10 kang with twrp and everything was fine until I decided to try and get the nexus s 4g modem which I had failed at every time before that. I would flash the rom, then gapps, Then the nexus modem patch before the shadow kernel. This time I flashed the shadow kernel before the nexus modem patch and it had apparentally powered itself off (I had left the room) so I tried to boot back into twrp, but it popped up with cwm 5.0 something instead. And the only backups I have are for twrp. . After I looked around in it for a little I tried flashing the rom and gapps again, booted up fine except I don't believe I had any signal. At all.
I tried to find something that would put twrp back onto my phone but haven't had any luck. And for some reason when I booted back into recovery it had changed to cwm 6.0 something. I don't know what to make of any of it. Right now I'm on cm9 snapshot beta 4 i think. I thought it was the one with twrp already in it so I thought I could try and restore my stuff.
Anyone have a remedy for this? I'd really appreciate it. Thank you in advance for your time.

swiftstrike763 said:
Hey everyone, I had just flashed cyanogen 10 kang with twrp and everything was fine until I decided to try and get the nexus s 4g modem which I had failed at every time before that. I would flash the rom, then gapps, Then the nexus modem patch before the shadow kernel. This time I flashed the shadow kernel before the nexus modem patch and it had apparentally powered itself off (I had left the room) so I tried to boot back into twrp, but it popped up with cwm 5.0 something instead. And the only backups I have are for twrp. . After I looked around in it for a little I tried flashing the rom and gapps again, booted up fine except I don't believe I had any signal. At all.
I tried to find something that would put twrp back onto my phone but haven't had any luck. And for some reason when I booted back into recovery it had changed to cwm 6.0 something. I don't know what to make of any of it. Right now I'm on cm9 snapshot beta 4 i think. I thought it was the one with twrp already in it so I thought I could try and restore my stuff.
Anyone have a remedy for this? I'd really appreciate it. Thank you in advance for your time.
Click to expand...
Click to collapse
You have to flash nyankernel or just the twrp zip. And next time when you flash from twrp, you need to pick inject twrp if you don't want cwm.
Sent from my SPH-D700 using Tapatalk 2

not trying to "thread-jack" - but I have a really similar problem (minus the twrp - which i'm not familiar with). Throughout my update to the crespo modem, during the mtd/bml check the phone would reboot into cwm - and I noticed that just like OP, the cwm would change to some 5.0version (not the usual 6 version)....
Here's what I have:
I was on CM Kang 7/30 with shadow kernel
I updated to CM Kang 8/08 (no problems)
I flashed the http://darkierawr.com/Android/Users/...atchcm7AIO.zip and I kept on getting Status 7 errors... I downloaded it a few times with the same result.
Then I saw someone say they flashed the kernel first and then the modem update... so I flashed the http://dl.dropbox.com/u/820341/Shadow-2_CM10_MdmCrp.zip (successful) and then tried flashing the modem update. Got stuck in a boot loop - so I did a battery pull.
Did a cold boot (pressing power) and now the phone "doesn't have a modem" no radio, no signal etc...
Tried it all over again - mounted system - formatted system - flashed 8/08 kang, gapps, then the modem update, and kernel.
my phone boots but no signal. is there a odin version of the modem that I can flash? or does anyone have any ideas?!?!?!
thanks!!

altimuh said:
not trying to "thread-jack" - but I have a really similar problem (minus the twrp - which i'm not familiar with). Throughout my update to the crespo modem, during the mtd/bml check the phone would reboot into cwm - and I noticed that just like OP, the cwm would change to some 5.0version (not the usual 6 version)....
Here's what I have:
I was on CM Kang 7/30 with shadow kernel
I updated to CM Kang 8/08 (no problems)
I flashed the http://darkierawr.com/Android/Users/...atchcm7AIO.zip and I kept on getting Status 7 errors... I downloaded it a few times with the same result.
Then I saw someone say they flashed the kernel first and then the modem update... so I flashed the http://dl.dropbox.com/u/820341/Shadow-2_CM10_MdmCrp.zip (successful) and then tried flashing the modem update. Got stuck in a boot loop - so I did a battery pull.
Did a cold boot (pressing power) and now the phone "doesn't have a modem" no radio, no signal etc...
Tried it all over again - mounted system - formatted system - flashed 8/08 kang, gapps, then the modem update, and kernel.
my phone boots but no signal. is there a odin version of the modem that I can flash? or does anyone have any ideas?!?!?!
thanks!!
Click to expand...
Click to collapse
Try http://marcusant.com/android/epic/modem.bin
Sent from my SPH-D700 using Tapatalk 2

[Q] M919 Rooted But Boot Loops With Custom Rom

I tried flashing a nightly of CM12 on my M919 after no problems for almost 2 weeks. After flashing, my phone was stuck in boot with the CM logo. I tried flashing previous versions of the rom wiping and clearing each time. All I got was the CM logo. I finally decided to start from scratch and reinstalled stock(4.4.4) with ODIN 3.07. Phone booted right up. Rooted the phone with CF-Auto-Root (KTU84P.M919UVUFNH7) with no problems. Ran it for the day to make sure no issues. After feeling comfortable, I downloaded and tried flashing CM11 Snapshot M12 since it's based off 4.4.4. Boot loop again. I tried CM12 with the same results. I'm using CWMR 6.0.4.7. I've tried newer versions of both CWMR and TWRP(I don't remember what versions they were). I'd like to go back to using 5.0, if possible. I'm not sure if I've missed a step in rooting, since it's been so long that I rooted/flashed this phone. Right now it's running stock 4.4.4/M919UVUFNK2 and rooted. Any suggestions as to what I could try?

That nightly may have borked some files causing a problem, the nightlies are usually full of warnings about possibly causing boot loops or lockups and always recommend a nandroid b/u before flashing.
A nightly is a way of trying something out on other people's phones to see if it works well enough to add it as an update to the regular rom build.
If your that desperate for a nightly you need to follow the thread for a couple of days and see how others do with it.
If all you see is "I flashed the nightly and boot loops all over the place, don't bother, otherwise you find yourself in this thread.
Try a factory reset and flashing again,
also get a newer CWM recovery 6051 (if not mistaken) but stay away from the nightlies.
If you really need a reliable phone that works all the time and doesn't windup dead, just keep your stock rooted rom. And lollipop will be here soon as an update, probably by mid-march, the you'll have all the lollipops you want.
Pp.

[Q] PA 5.1 OTA issues

Maybe it's me missing something, I downloaded and installed PA 5.1, build from 20th May which I do not think is an Alpha that I would need to factory reset to do an OTA over.
However today OTA popped up with a update to the 28th May build, the upgrade seems to work but the phone then will not boot up instead I get the initial S3 screen twice with a blank screen in between then it drops in to recovery?
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
The recovery that I an using is Philz recovery - added it a couple of nights ago to install the original build of 5.1 and Gapps so that seems to work, there no errors with the OTA as its installed, the caches are being cleared first by the install script everything looks fine until the phone tries to boot back up. Have tried it 3 times now downloading a new copy of the OTA each time in case of corruption and restoring from a good backup on each failure.
Any ideas appreciated?
... and thank you in advance

paped said:
Maybe it's me missing something, I downloaded and installed PA 5.1, build from 20th May which I do not think is an Alpha that I would need to factory reset to do an OTA over.
However today OTA popped up with a update to the 28th May build, the upgrade seems to work but the phone then will not boot up instead I get the initial S3 screen twice with a blank screen in between then it drops in to recovery?
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
The recovery that I an using is Philz recovery - added it a couple of nights ago to install the original build of 5.1 and Gapps so that seems to work, there no errors with the OTA as its installed, the caches are being cleared first by the install script everything looks fine until the phone tries to boot back up. Have tried it 3 times now downloading a new copy of the OTA each time in case of corruption and restoring from a good backup on each failure.
Any ideas appreciated?
... and thank you in advance
Click to expand...
Click to collapse
Well, i'm on I9300 and all i can tell you is that i have the same exact problem with the same release, so you're not alone.
I was hoping this new release would work since the one of the 20 may didn't, but this one won't even boot.
I guess I9300 doesn't get love anymore...

You are not alone in this. It is happening with me too since the stable build of 28th May. I tried the on on June 12th too ...but even that is failing as well
How come it is a stable build when it has a bug like this and crashes the phone? Are we making a mistake? Does it require a different kernel or what can I do to make it work?!
~ Manthravadi

I'm stuck with this I have tried the last 3 ota updates with CWM, TWRP and Philz recovery all fail as above. Even tried downloading the full versions and doing a clean install with gapps and they fail. Could be a kernel issue but cannot find anything that states a dependency, is the kernel not part of the download like in a Linux OS? As never upgraded a kernel separately, how would you do that, is it another zip file, any ideas where to get it from?

paped said:
I'm stuck with this I have tried the last 3 ota updates with CWM, TWRP and Philz recovery all fail as above. Even tried downloading the full versions and doing a clean install with gapps and they fail. Could be a kernel issue but cannot find anything that states a dependency, is the kernel not part of the download like in a Linux OS? As never upgraded a kernel separately, how would you do that, is it another zip file, any ideas where to get it from?
Click to expand...
Click to collapse
I actually got it working finally a few days back.
You need to install boeffla kernel version 4 alpha 3 in order get the latest pa rom up and running. Go to boeffla-kernel website. In downloads select the device GT-I 9300. You will find CM12.1 NG version which is not yet stable. In that select version 4 alpha 3. Alpha 6 is latest but does not work too :/ Download Alpha 3 .. a .zip file which can be flashed using TWRP or Philz or CWM.
Wipe cache/dalvik-cache → flash boeffla → flash pa latest → flash pa gapps latest for 5.1
~ Manthravadi
Sent from my GT-I9300 using Tapatalk

I also have problem but thankfully when I did the steps above, it did finally boot but now I have another problem. My S3 boots properly and I can use it for a while then after a few mins it suddenly reboots with boot animation and all and I dunno what to do. It just keeps rebooting after a certain amount of mins.

@Aledresin: glad that I was able to help you. I am not experiencing any such issues at the moment. When the next PA build is released, try to flash it with boeffla 4 alpha 6.
Afaik ..some memory issues were fixed in alpha 6 and as you are using alpha 3..perhaps you are experiencing those issues.
~ Manthravadi
Sent from my GT-I9300 using Tapatalk

Manthravadi said:
I actually got it working finally a few days back.
You need to install boeffla kernel version 4 alpha 3 in order get the latest pa rom up and running. Go to boeffla-kernel website. In downloads select the device GT-I 9300. You will find CM12.1 NG version which is not yet stable. In that select version 4 alpha 3. Alpha 6 is latest but does not work too :/ Download Alpha 3 .. a .zip file which can be flashed using TWRP or Philz or CWM.
Wipe cache/dalvik-cache → flash boeffla → flash pa latest → flash pa gapps latest for 5.1
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Do you happen to have a copy/mirror of "boeffla-kernel-4.0-alpha3-CM12.1-NG-i9300.recovery.zip"
I've been searching for a few days and can't find it anywhere. The official boeffla site no longer hosts this file and a lot of i9300 users need it to run the latest Paranoid OTA.
EDIT: Found it! It's available here: http://boeffla.df-kunde.de/sgs3/boef...load/Test/old/
Thanks to user Hawaiihemd for the info.

paped said:
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
Click to expand...
Click to collapse
I had a very similar problem and found that if I let it automatically reboot after flashing, then I was stuck just rebooting to recovery. If I manually shut down after flashing and manually booted, then everything worked fine. You may have the same thing happening here. I also used PhilzTouch and like it a lot. Thanks to the devs!

Installing [ROM] [5.1.x] Unofficial CyanogenMod 12.1 Nightly Builds

I've flashed the [ROM] [5.1.x] Unofficial CyanogenMod 12.1 Nightly Builds (Z00A/Z008) for my Z00A.
I also tried flashing the google apps but a missing xv prevents it from installing, but this is not my main problem.
My main problem is that, although I've done a complete wipe, after flashing the nightly, the phone boots, I get an image saying "updating system" or something similar and then the fallen android with a simple message, error.
I've flashed it on top of ASUS_Z00A-2.19.40.22_20150627 which is what the base rom should be as stated here.
What else can I do to get my hands on that nightly?
Thanks!

s0undt3ch said:
I've flashed the [ROM] [5.1.x] Unofficial CyanogenMod 12.1 Nightly Builds (Z00A/Z008) for my Z00A.
I also tried flashing the google apps but a missing xv prevents it from installing, but this is not my main problem.
My main problem is that, although I've done a complete wipe, after flashing the nightly, the phone boots, I get an image saying "updating system" or something similar and then the fallen android with a simple message, error.
I've flashed it on top of ASUS_Z00A-2.19.40.22_20150627 which is what the base rom should be as stated here.
What else can I do to get my hands on that nightly?
Thanks!
Click to expand...
Click to collapse
I'm also having a hard time permanently flashing either CW or TWRP recovery. Even using the TWRP app which reports that recovery was successfully installed, when I test to boot into recovery, it only get's me to fastboot, nothing further...

So, my problem was that my bootloader was not unlocked.
this helped