Develop Bugs

About Verizon and Jelly Bean for the GNex

So I found out the hard way that Jelly Bean 4.1 isn't compatible with verizon phones, when trying to upgrade to the OTA release anyway.
With that in mind, will Verizon ever get a release? Or is there a way now to make it work?
Thanks

iamTWOcats said:
So I found out the hard way that Jelly Bean 4.1 isn't compatible with verizon phones, when trying to upgrade to the OTA release anyway.
With that in mind, will Verizon ever get a release? Or is there a way now to make it work?
Thanks
Click to expand...
Click to collapse
??? The OTA release was for the GSM version. There are many, many 4.1 Android Jellybean roms within the Verizon-specific development sub forum (even some are clean 4.1 with only some prop changes to make it as stock 4.1 possible)

Unlock your phone and root your phone.
Use Rom manager to flash Clockwork Mod recovery.
Download a 4.1 rom from development, put on the root of your /sdcard.
Boot into clockwork with rom manager.
Make a backup of your current rom incase anything goes wrong.
Go into Advanced, Wipe Dalvik Cache.
From main menu, Wipe cache partition.
From main menu, Wipe data partition.
Install zip from sdcard, choose the rom you downloaded. After it installs there is usually the superuser zip you then flash afterword to get root.
Reboot, be patient for the first boot
Profit

iamTWOcats said:
So I found out the hard way that Jelly Bean 4.1 isn't compatible with verizon phones, when trying to upgrade to the OTA release anyway.
With that in mind, will Verizon ever get a release? Or is there a way now to make it work?
Thanks
Click to expand...
Click to collapse
Oh my Lord. Are you serious? This must be a mistaken case of "I can't read a damn thing."

Yeah, I've been running one of these clean 4.1 verizon-specific roms for about a week now, with no issues.....

NeoMagus said:
Unlock your phone and root your phone.
Use Rom manager to flash Clockwork Mod recovery.
Download a 4.1 rom from development, put on the root of your /sdcard.
Boot into clockwork with rom manager.
Make a backup of your current rom incase anything goes wrong.
Go into Advanced, Wipe Dalvik Cache.
From main menu, Wipe cache partition.
From main menu, Wipe data partition.
Install zip from sdcard, choose the rom you downloaded. After it installs there is usually the superuser zip you then flash afterword to get root.
Reboot, be patient for the first boot
Profit
Click to expand...
Click to collapse
This.

[Q] 4.2.2 OTA if I already have 4.2 Camera/Gallery?

I just got the 4.2.2 system update notification on my phone from Verizon. Before I install it, I wanted to make sure the 4.2 camera/gallery I installed a while back (installed from zip using CWM, renamed old cam/gallery files if I remember right) wouldn't cause the update to error out. I'm rooted and on stock 4.1.1 Build JRO03O other than the newer camera/gallery. Thanks.

you wouldnt be stock since you installed a mod, therefore the OTA would error.

Zepius said:
you wouldnt be stock since you installed a mod, therefore the OTA would error.
Click to expand...
Click to collapse
Thanks, that's what I figured. I'll try to find the site that outlined what I did to install the new camera/gallery so I can reverse it.

Well, I can't find any info on how to get the old 4.1 camera/gallery back.
What I did for the 4.2 camera back in December was download the "camera.zip" file, reboot into recovery, install the zip, then reboot. Then it force closes the gallery so I used root browser to go into system>app and renamed gallery.google.odex to gallery.google.bak and then moved that file to the system folder.
I assume I need to find a 4.1 camera zip and install it, then move the above file back to system>app if the install doesn't create a new gallery.google.odex file?
Is this correct or am I way off? Anybody have a link to the 4.1 camera zip download?

Your main issue is also having a custom recovery (CWM). If you want ota (not sure why) you need to go back to stock recovery also.
good day.

chopper the dog said:
Your main issue is also having a custom recovery (CWM). If you want ota (not sure why) you need to go back to stock recovery also.
good day.
Click to expand...
Click to collapse
I've always used the OTA update in the past with CWM without issue, I just never had a custom camera (or anything else) for previous updates. I don't really care "how" I get 4.2.2 as long as it's the official version so it's got the least chance of being buggy. What's the easiest way to get the official 4.2.2 release when rooted with 4.2 camera without loosing any phone data?

So is there nowhere to download just the camera/gallery from 4.1 to re-install?
What's the fix here so I can go to 4.2.2 without clearing phone data? Thanks.

Here is the 4.1.1 stock rooted OTA. It is a flashable zip. Flash in recovery. Wipe cache/dalvik only. Reboot then update to 4.2.2.
http://tinyw.in/FbcF
Edit: you could just pull the apk out if you wanted but I suggest just flashing the whole system.
Toro | Xylon | AK Diamond

chopper the dog said:
Your main issue is also having a custom recovery (CWM). If you want ota (not sure why) you need to go back to stock recovery also.
good day.
Click to expand...
Click to collapse
this isnt true. you can still complete the OTA with a custom recovery. ive done it the past 2 OTAs. the problem happens when you have flashed a mod or modified a /system/ file.

Sandman-007 said:
Here is the 4.1.1 stock rooted OTA. It is a flashable zip. Flash in recovery. Wipe cache/dalvik only. Reboot then update to 4.2.2.
http://tinyw.in/FbcF
Edit: you could just pull the apk out if you wanted but I suggest just flashing the whole system.
Toro | Xylon | AK Diamond
Click to expand...
Click to collapse
Thanks. Because it's 4:30 am and I wanted to see if I could get a quick fix, I tried pulling out the gallery.apk, moving it to the app folder and it worked perfect after I renamed the 4.2 gallery.apk to gallery. The camera and gallery are back to the "old" versions and working fine.
Went ahead and ran the OTA, it failed (cache error) so I cleared cache/dalvik, rebooted and it went into "Android is upgrading...". After it was done, I went into settings to see what version it was and it was still on 4.1.1. Tried to force the system update a few times by clearing/stopping framework services and then checking for updates and finally got it to download the update.
It rebooted to install the update and TWRP opened up. I told it to install the file and it failed. Errors say:
assert failed: apply_patch_check (' /system/app/GalleryGoogle.apk.....(can't read the rest, it's off the screen).
E: Error in /cache/5939ff985946.signed-mysid-JDQ....(can't read the rest)
(Status 7)
It appears there is still "something" wrong with the gallery/camera but it's beyond skills. It's too late to mess with it any further so hopefully someone will have a suggestion to try when I wake up. If not, I guess I'll try to apply the whole 4.1.1 OTA first and see if that fixes it.
Thanks for the help thus far.

It would only take a minute or two to flash the whole file. Is like flashing a ROM
Toro | Xylon | AK Diamond

Sandman-007 said:
Here is the 4.1.1 stock rooted OTA. It is a flashable zip. Flash in recovery. Wipe cache/dalvik only. Reboot then update to 4.2.2.
tinyw.in/FbcF
Edit: you could just pull the apk out if you wanted but I suggest just flashing the whole system.
Toro | Xylon | AK Diamond
Click to expand...
Click to collapse
I'm in the same position. Rooted, 4.2 camera. Putting the 4.1 apk back didn't help me. Thanks for the OTA, I'm hoping that flashing with this and then with the 4.2.2 will get me upgraded without a full wipe. H/W died a few weeks ago and it's finally back to having everything loaded.
Thanks!

Leithal007 said:
I'm in the same position. Rooted, 4.2 camera. Putting the 4.1 apk back didn't help me. Thanks for the OTA, I'm hoping that flashing with this and then with the 4.2.2 will get me upgraded without a full wipe. H/W died a few weeks ago and it's finally back to having everything loaded.
Thanks!
Click to expand...
Click to collapse
No problem. Please let me know if it works.

Sandman-007 said:
Here is the 4.1.1 stock rooted OTA. It is a flashable zip. Flash in recovery. Wipe cache/dalvik only. Reboot then update to 4.2.2.
tinyw.in/FbcF
Edit: you could just pull the apk out if you wanted but I suggest just flashing the whole system.
Toro | Xylon | AK Diamond
Click to expand...
Click to collapse
I Flashed the Full/Stock 4.1.1 you posted. However I still can't install 4.2.2. I get the following error (image attached).
I'm completely stuck at this point, the only thing I had done was install the 4.2 camera, and superuser, and thought that the 4.1.1 install would have "fixed" this.
Any ideas?

Leithal007 said:
I Flashed the Full/Stock 4.1.1 you posted. However I still can't install 4.2.2. I get the following error (image attached).
I'm completely stuck at this point, the only thing I had done was install the 4.2 camera, and thought that the 4.1.1 install would have "fixed" this.
Any ideas?
Click to expand...
Click to collapse
Fastboot the Google Stock image

Sandman-007 said:
Fastboot the Google Stock image
Click to expand...
Click to collapse
Flashed, then recovered CWM, Superuser etc.
Now to start with Apps, etc...
Thank you for the help and pointers... Couldn't have got here without you and the resources you, and this site, pointed me to...

Leithal007 said:
Flashed, then recovered CWM, Superuser etc.
Now to start with Apps, etc...
Thank you for the help and pointers... Couldn't have got here without you and the resources you, and this site, pointed me to...
Click to expand...
Click to collapse
No problem dude. Glad u got it all figured out. I forgot to tell you and I an sure you did this since you had to reinstall CWR but make sure you have the updated version of your recovery BEFORE you update to 4.2.2
Toro | Xylon | AK Diamond

Sandman-007 said:
No problem dude. Glad u got it all figured out. I forgot to tell you and I an sure you did this since you had to reinstall CWR but make sure you have the updated version of your recovery BEFORE you update to 4.2.2
Toro | Xylon | AK Diamond
Click to expand...
Click to collapse
Can you explain this so I can be sure to do it before I end up in the same situation as the other guy? What do you mean by "updated version of your recovery"? I did a Ti Backup of all user apps + system data and saved it to the sd card before I messed with going back to the 4.1 camera. I also backed up the current ROM in CWM which rebooted into TWRP and did a Nandroid backup. Is this sufficient or is there something I need to do to make it 4.2.2 compatible? Thanks.
This is a good reminder why I shouldn't run a "custom" anything on this phone. I don't have time to keep up with how to do all of this stuff and it ends up being a mess in the end. Only reason I did the 4.2 camera was I was going on vacation and wanted to be able to take some great photosphere photos while I was there (which I did).

Stinger2300 said:
Can you explain this so I can be sure to do it before I end up in the same situation as the other guy? What do you mean by "updated version of your recovery"? I did a Ti Backup of all user apps + system data and saved it to the sd card before I messed with going back to the 4.1 camera. I also backed up the current ROM in CWM which rebooted into TWRP and did a Nandroid backup. Is this sufficient or is there something I need to do to make it 4.2.2 compatible? Thanks.
This is a good reminder why I shouldn't run a "custom" anything on this phone. I don't have time to keep up with how to do all of this stuff and it ends up being a mess in the end. Only reason I did the 4.2 camera was I was going on vacation and wanted to be able to take some great photosphere photos while I was there (which I did).
Click to expand...
Click to collapse
CWM is called a recovery. You need to get the updated version from ROM Manager or Koush's website. I recommend TWRP over CWM. You can get TWRP from Goo manager. Either way make sure you update your recovery or your will have a headache.
Sent from my Nexus 7 using XDA Premium HD app

I am having a similar issue with the OTA update since I have the 4.2.2 camera installed as well. Is there a way to flash the update manually with CWM that will work with the camera installed?

[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!

Help with stock rom !

Hello, So i recently decided to move back to stock os as i think the push notification bug is fixed (Is it ?) . So then i yesterday downloaded the rom http://forum.xda-developers.com/fire-phone/development/safestrap-v4-flashable-stock-image-t3150531. I downloaded the latest version 4.6.6.1 US Version. I remember i rooted the phone from 4.6.6 does it matter ? So i decided to check the rom before actually wiping all my data so i created rom-slot-1 and tried to install the stock os in it. It gave me a error ''Failed to update binary through zip'' i can not decide is it problem with non-stock rom or is it with the rom. There are 3 rom types on that rom page. I dont know what could be the problem. Does the rom vary with the model of the phone ? if yes then how can i know my model of the phone ?
Thanks

The Fire OS partitions are too big, so they will never fit into the manually created slots, which is a good thing because they prevent an installation that would be useless anyway.
You can install ROMs to slot1 but they won't work correctly (connectivity, etc.), so don't even waste time on trying...
Just backup your existing OS via TWRP through Safestrap and proceed with a clean install of Fire OS:
TWRP backup of "old" OS
wipe data, cache & dalvik
flash the CleanSystemPartition zip
flash the Fire OS zip right after
flash other things of your choosing, like SuperSU, etc.

Paras5 said:
Hello, So i recently decided to move back to stock os as i think the push notification bug is fixed (Is it ?) . So then i yesterday downloaded the rom http://forum.xda-developers.com/fire-phone/development/safestrap-v4-flashable-stock-image-t3150531. I downloaded the latest version 4.6.6.1 US Version. I remember i rooted the phone from 4.6.6 does it matter ? So i decided to check the rom before actually wiping all my data so i created rom-slot-1 and tried to install the stock os in it. It gave me a error ''Failed to update binary through zip'' i can not decide is it problem with non-stock rom or is it with the rom. There are 3 rom types on that rom page. I dont know what could be the problem. Does the rom vary with the model of the phone ? if yes then how can i know my model of the phone ?
Thanks
Click to expand...
Click to collapse
And no... The notification push bug isn't fixed -,-

Downgrading to OOS 4.0.2

Sup guys,
I have been using the rooted original roms for a while now with the APT-x codec installed though since 4.0.3 this doesn't work any more. So I would like to downgrade to 4.0.2 for the time being. How would I go about doing this ?

Select the version of OOS you want, download it from OnePlus's site and flash it through either the stock or custom recovery.
http://downloads.oneplus.net/devices/oneplus-3/

Anova's Origin said:
Select the version of OOS you want, download it from OnePlus's site and flash it through either the stock or custom recovery.
Click to expand...
Click to collapse
Same way as upgrading to a new version? to keep root I would have to flash Supersu ?

Yep.

Can I just use the current twrp and supersu or would I need to download a older version of either?

tdmike said:
Can I just use the current twrp and supersu or would I need to download a older version of either?
Click to expand...
Click to collapse
Yes, you can.
AptX is working good on 4.0.3 with magisk module.
I'm using it at the moment.
But it's broken since 4.1.

So I just had to restore to the current version. My launcher and keyboard kept crashing and I wasn't able to install apps. Seems something went wrong. Anyone any clues?
What I did: take a nandroid, wipe dalvik cache, install 4.0.3, install most recent SuperSU. Wipe dalvik again and reboot.