Develop Bugs

[DISCONTINUED][GSM][04.09.11][ALPHA] Honeycomb port by [DiP7]

Since Spacemoose has a GSM release approaching, I'm going to remove the download links here. (Also because apparently people are still attempting to flash this...) If and when I am contacted by DiP7 I will reopen this thread and add any links he wants me to add.... Or it can stay closed and he can start a new one (which is what I would hope he does.) I'm leaving the rest of the content here for reference only.
**READ ENTIRE FIRST POST BEFORE FLASHING**
This is an Alpha build. Almost nothing works at the moment. Don't expect a golden daily driver... This aint it. If you find a download link throughout this thread, don't flash it, as I can't promise anyone will help you un(soft)brick your device. ​
Let's start this with : I take zero, zilch and no responsibility for anything you do to your device using anything from this thread.
If space alien ninja cows come down and eat it because they want to taste honeycomb, your fault, sorry.
There have been zero reports of anyone "hard bricking" their device, but again, I'm not responsible if you become the first.
I also take no credit for any of the work, I've only compiled what I have found so far.
I also can't stress this enough... This is a VERY EARLY STAGE of the port. ALMOST NOTHING WORKS. Any updates that take place will need to be documented within this post. I'm willing to keep track of all this, but *I AM NOT A DEV.* The original dev of this port is from another website, dsf767 seems to be in contact with him however. here at XDA!
**Please see bottom of this post for change log**
Various vidoes have been made, but the quality of this one is really nice. Thanks museboy!
This is a direct port of Spacemoose's Alpha v.040211 release. Not much works.
In Spacemoose's thread, credit is given to
[*] A russian-language GSM port attempt based on this project. (Thanks, dsf767.)
Click to expand...
Click to collapse
It appears as though someone DiP7 is attempting to port Spacemoose's project to a GSM device. They also appear to have had mild success in doing so, and I'd like to start a thread to track and follow any progress anyone else may be having with flashing this rom/kernel.
[*] System must already be converted to EXT4. This can be done by various methods, flashing the Overcome rom/kernel will do it.
[*] Tab confirmed to charge while off and reports of lockscreen charging have been made.
I'm unsure if anyone has had any success other than the OP Cal-El has gotten it to boot! Directions appear to be as follows:
BACKUP EVERYTHING. Everything? EV-ER-Y-THING. Especially your internal SD card. There have been reports (that I've experienced) of your internal SD card getting wiped in either going to or coming from Honeycomb. (It usually requires a repartition to go back... so yeah, that'd do it.)
Did you back everything up? You will loose any information on your internal SD card coming back to normal from this build.
Download Rom to EXTERNAL SD:
Download Kernel to EXTERNAL SD:
Did you back up your internal SD card? What about external? Last warning. Next person to complain about their internal SD card get's the bonk.
Wipe Data/Factory restore
Wipe Cache Partition
Wipe Delvik Cache
Flash honeycomb rom using CWM (This seems to have only been tested and confirmed from the Overcome modified CWM, although any should work in theory.)
Reboot into new RED CWM.
Flash kernel using RED CWM
Reboot into new ORANGE CWM.
Wipe data/Factory reset
Wipe both caches.
Flash honeycomb rom using the ORANGE CWM.
There is no boot screen after the Galaxy Tab logo screen, just a black screen. Wait at least 5 minutes for it to boot. If it doesn't after 10, something went wrong.
If this fails, attempt to go back to stock by flashing p1_hidden.pit and any of Roto's stock roms/firmwares. From here it has been confirmed to work if you flash the Overcome rom/kernel before moving to the Android 3.0 rom/kernel. (Thanks Cal-El!)
This process must also be used to coming back from this
Honeycomb build. You will loose all information on your internal SD card.
I told you to back it up.
Taken from Alterbridge's Overcome Rom posting (which should fix any hangups while flashing to/from this Honeycomb)​
alterbridge86 said:
IF your Tab does not boot after flashing the kernel and hangs at the Samsung Galaxy Tab screen, you must follow the following procedure
Get a stock rom package (any of Rotohammer's firmwares will work)
Get P1_add_hidden.zip from this post and extract the P1_add_hidden.pit file
Using Odin 1.7, put stock rom (Roto-JME-Full-v4.tar for example) in PDA slot.
Put P1_add_hidden.pit in Pit slot
Check repartition box
Put Tab in download mode by holding Volume Down and Power, connect to the computer, and press start.
After this, the Tab will reboot normally. Shut it down and return to download mode.
Open Odin 1.7 and reconnect the Tab.
In the PDA slot, choose the Overcome Kernel v2.0 tar file for use with Odin. Press start
It will flash the kernel then reboot. Upon reboot, you should hear the sexy robot voices informing you of the status of the EXT4 conversion.
Once done, the Tab will boot normally. At this point you can load Overcome Rom (or any other Rom of your choosing)
Click to expand...
Click to collapse
[*]Remember, No wi-fi, no 3g, no phone calls, nothing. This is a test port. YOU HAVE BEEN WARNED OVER 5 TIMES NOW, no complaining about it later.
[*]If your internal SD card reads ~220 MB after coming from this ROM to anything else, you didn't read my post... Try again.
[*] Mirrors :
*Update on driver work for wi-fi (4/12): http://forum.xda-developers.com/showpost.php?p=12816258&postcount=224 (Thanks DemonGloom for translating)
*Also added video to OP (Thanks to museboy!)

the wife is russian. may attempt tonight when I get home. thanks for the heads up

Just try to make sure that any actual changes to the base system build are reported in the other thread as well so we can all stay on the same page.

This is a brilliant find! Downloading now to test this baby out
Is the rom and kernel in the zip or are there 2 different files to download?
Sent from my GT-P1000 using XDA Premium App

I tried flashing this using the mothod above and the methon on the russian site but I can't get it to work.
It keeps messing up my /data partition. After flashing the ROM CWM always fails to mount the /data partition.
I'm going back to overcome .

I already got a blank screen and then a broken internal sdcard error. Had to find an odin flash that repartitioned.
Ill be willing to do it all again as soon as there is wifi. At least this time I'll make sure to back up my internal sdcard.

-RioT- said:
I already got a blank screen and then a broken internal sdcard error. Had to find an odin flash that repartitioned.
Click to expand...
Click to collapse
Just trying to keep track of this all... Are you saying you got it to run successfully but had to repartition to go back? Or did you have to repartition to get it to run?
Adding in the hidden_pit to the process seems simple enough.
-RioT- said:
Ill be willing to do it all again as soon as there is wifi. At least this time I'll make sure to back up my internal sdcard.
Click to expand...
Click to collapse
Step #1

GANJDROID said:
This is a brilliant find! Downloading now to test this baby out
Is the rom and kernel in the zip or are there 2 different files to download?
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
They both appear to be contained within the same zip file, much like the Overcome rom. Best guess, can't verify as I'm on a work mac at the moment.

btyork said:
They both appear to be contained within the same zip file, much like the Overcome rom. Best guess, can't verify as I'm on a work mac at the moment.
Click to expand...
Click to collapse
Yeah, my mistake. Got confused about the reflash with new kernel/cwm.
So we:
Backup
Wipe everything
Flash
Wipe
Flash
Reboot
Sent from my GT-P1000 using XDA Premium App

There Directions are directly from DiP
Originally Posted by DiP7
- the first step (the file system should already be ext4) - flash honeycomb (Android3.0_by_DiP_signed _narod.yandex.ru/disk/9317202001/Android3.0_by_DiP_signed_040411_235124.zip
- the second step (to flash my kernel dl.getdropbox.com/u/937719/Recovery_install_pda1.4Ghz_CWR_v_2.1.0.zip) go to the recovery and make the wipe data/factory reset
- The third step - go to recovery and flash again android 3.0

GANJDROID said:
Yeah, my mistake. Got confused about the reflash with new kernel/cwm.
So we:
Backup
Wipe everything
Flash
Wipe
Flash
Reboot
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
So far that's what I've gathered, I have yet to actually test this process.
The poster above appears to have mentioned something about repartitioning, which isn't a big deal, just flash the hidden_pit.
My best guess is to flash that pit after the second wipe with Odin. But I CAN NOT verify that.
It seems obvious you would need to repartition to go back though.

I would try and flash it all via cwm, but I'm unable to download the kernel. Can anyone mirror it please?
Away from my laptop for the next few hours so I'm unable to try with Odin.

GANJDROID said:
I would try and flash it all via cwm, but I'm unable to download the kernel. Can anyone mirror it please?
Away from my laptop for the next few hours so I'm unable to try with Odin.
Click to expand...
Click to collapse
Recommendations as to a site to mirror it on? I don't do a lot of hosting.

Here are some Mirrors you can put them in the OP of the Rom and Kernel
ROM: http://www.megaupload.com/?d=RC6WF2PG
Kernel: http://www.megaupload.com/?d=GP58GAOE

Anyone have luck getting HC port running o the tab yet and if so can we get a clear how to in place ?
Thanks in Advance =)

btyork said:
Recommendations as to a site to mirror it on? I don't do a lot of hosting.
Click to expand...
Click to collapse
I'd say Mediafire or Megauload are the best, IMHO.
Big thanks for the mirrors.
For now, FML. Now got 8% battery left *sigh* Ill have to wait for some Honeycomb love.
Sent from my GT-P1000 using XDA Premium App

Updated with Kernel and Mirror(s) for both Rom and Kernel.

clockedtouch said:
Anyone have luck getting HC port running o the tab yet and if so can we get a clear how to in place ?
Thanks in Advance =)
Click to expand...
Click to collapse
The clear "how to" is in the first post... If you can't understand those directions, you really shouldn't be flashing this.

btyork said:
The clear "how to" is in the first post... If you can't understand those directions, you really shouldn't be flashing this.
Click to expand...
Click to collapse
Thats why i dont post much simple remarks like that make members not want to contribute ...
You could of simply stated that the "how-to" was updated .. but thanks for your quick response anyway

clockedtouch said:
Thats why i dont post much simple remarks like that make members not want to contribute ...
You could of simply stated that the "how-to" was updated .. but thanks for your quick response anyway
Click to expand...
Click to collapse
I actually haven't updated the how-to since the original post... It wasn't meant to be rude, it's just how it is. I don't want people bricking a 600 dollar tab because they think this is a fully functional honeycomb port.
You'd also be surprised how many people post that kind of question without any understanding of what ADB even is.

Flashing a ROM won't work

So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?

When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?

cupfulloflol said:
When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?
Click to expand...
Click to collapse
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.

CheesieOnion said:
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.
Click to expand...
Click to collapse
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.

CheesieOnion said:
So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?
Click to expand...
Click to collapse
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.

cupfulloflol said:
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.
Click to expand...
Click to collapse
I got the rom from the topic here on XDA. It is the build from 19 november.
simms22 said:
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.
Click to expand...
Click to collapse
In the instuctions in the ROM-topic it says it needs them and I also need them to use.

CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
In the instuctions in the ROM-topic it says it needs them and I also need them to use.
Click to expand...
Click to collapse
install the gapps from the play store. you can flash without them, besides the ones that you cant get from the play store are included. you can try it, or just stay in your bootloop, its your call.

CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
Click to expand...
Click to collapse
Ah, my bad I didn't realize it was picked up by someone else, I see that now (which I thank you for the heads up that it is back in production). I was just making sure you weren't flashing something that wasn't ready for public use, and that it was a real ROM.

GNEX frozen at JB startup animation (multicolored X)

Hi, hope my exact issue wasn't discussed after page 10 of the help & troubleshoot forum, anyway my rooted, unlocked cwm recovery stock 4.2 yakju (if I remember well) Samsung GNEX started to behave strangely slower then usual less then a week ago, then a couple of days later I woke up after night battery recharge to the boot up animation which never gave way to the operating system starting up.
After the first moment of despair I tried reading something here and with the use of adb I was able to first see the device and, after backing up via recovery, to pull the files from the phone (backup included). Problem is the 0 folder is very light for all the data and apps that I had, and inside the DCIM folder there's nothing, no trace of the 1k+ picture I shot in the past couple years, only an igc file which should have been in another folder. But strangely enough the backup weights almost 6GB which is consistent with what was inside prior to the crash.
Before attempting the backup I fiddled with recovery and tried to wipe cache, dalvik and fixing permissions, with no apparent results.
So now I'm undecided whether to take the phone to a samsung job centre which will surely wipe all data and possibly find out I have a corrupt memory or partition table, which renders many files and folders unavailable to be adb pulled or to wipe data/restore factory by myself hopying, fingers crossed, that the backup actually saved all my files and that could be restored without hassle. I actually had hoped that, like for the desktop environment, there was the possibility to awake my phone with a linux live or whatever to check if all files were present and downloadable before actually restoring the phone.
Thanks for your interest and help.
https://drive.google.com/file/d/0B8Pbk0TslYN6cm1wWWZydVM2V0k/edit?usp=sharing

Have you tried dirty flashing your rom?
Sent from my Galaxy Nexus using XDA Free mobile app

This is probably what I was thinking to do in the last sentence, I just have no idea how this could be done. Are there any videos explaining a dirty flash for gnex out there? Thanks for your help
Sent from my ASUS Transformer Pad TF300T using XDA Free mobile app

berniefranz said:
This is probably what I was thinking to do in the last sentence, I just have no idea how this could be done. Are there any videos explaining a dirty flash for gnex out there? Thanks for your help
Sent from my ASUS Transformer Pad TF300T using XDA Free mobile app
Click to expand...
Click to collapse
Its really easy. Just wipe cache and dalvik cache and then flash your rom (the same rom that is on the phone) again. Reboot.
Sent from my Galaxy Nexus using XDA Free mobile app

As far as I remember there is no identifiable rom files inside my GNEX memory, or wait, it seems I do already have a 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815 zip in my download folder. So I need to clean cache and dalvik then install from zip. Do you know if this system wipes everything and I need to restore everything applying my hopefully working backup, or if it keeps all the files?
I'll try it tomorrow with fingers crossed.
Thanks again
mrgnex said:
Its really easy. Just wipe cache and dalvik cache and then flash your rom (the same rom that is on the phone) again. Reboot.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse

berniefranz said:
As far as I remember there is no identifiable rom files inside my GNEX memory, or wait, it seems I do already have a 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815 zip in my download folder. So I need to clean cache and dalvik then install from zip. Do you know if this system wipes everything and I need to restore everything applying my hopefully working backup, or if it keeps all the files?
I'll try it tomorrow with fingers crossed.
Thanks again
Click to expand...
Click to collapse
Dirty flashing wont wipe any data. Only cache (which is only helpful with some speed). Cache will rebuild. If thats your rom. Dirty flash it. If it isnt. Adb push the right rom.
Sent from my Galaxy Nexus using XDA Free mobile app

Then I don't think the mentioned file is the my rom but a rom update I wanted to push myself but never did. Now, I'm definitely sure it was already JB, but which flavour? 4.2 JOP40C, 4.2.1 JOP40D or 4.2.2 JDQ39? I guess it should have been the last one, if I intended to update from JDQ to JWR (according to the file name), and I'm quite sure it was Jakju but just can't remember for sure. Is there a way via recovery or adb to check which was my rom? Or should I just close my eyes and download and flash JDQ39?
Again, thanks
mrgnex said:
Dirty flashing wont wipe any data. Only cache (which is only helpful with some speed). Cache will rebuild. If thats your rom. Dirty flash it. If it isnt. Adb push the right rom.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse

berniefranz said:
Then I don't think the mentioned file is the my rom but a rom update I wanted to push myself but never did. Now, I'm definitely sure it was already JB, but which flavour? 4.2 JOP40C, 4.2.1 JOP40D or 4.2.2 JDQ39? I guess it should have been the last one, if I intended to update from JDQ to JWR (according to the file name), and I'm quite sure it was Jakju but just can't remember for sure. Is there a way via recovery or adb to check which was my rom? Or should I just close my eyes and download and flash JDQ39?
Again, thanks
Click to expand...
Click to collapse
I know that TWRP default names a nandroid as the ROM build name/number and date. Don't know what cwm does for that as its been ages since I used it. You could install twrp and see what that tells you as the name of backup maybe to try and grab current ROM info.
Or using the file manager in recovery(twrp has one dunno about cwm) and see if you can look at the build.prop in /system which will have all relevant ROM information. If you can use adb in recovery try pulling /system/build.prop and looking at it. Right near top will be ROM build and info

Thanks, CWM doesn't have a file manager, but adb did actually pull the build prop id=JOP40D, so I'll go back to download the correct ROM and try to flash it..
ashclepdia said:
I know that TWRP default names a nandroid as the ROM build name/number and date. Don't know what cwm does for that as its been ages since I used it. You could install twrp and see what that tells you as the name of backup maybe to try and grab current ROM info.
Or using the file manager in recovery(twrp has one dunno about cwm) and see if you can look at the build.prop in /system which will have all relevant ROM information. If you can use adb in recovery try pulling /system/build.prop and looking at it. Right near top will be ROM build and info
Click to expand...
Click to collapse

small update, I managed to download the correct rom and I tried to adb push the .tar to the device (twice and attempting a third to /sdcard/ /sdcard/clockworkmod/ and now /sdcard/0/Download/) but still haven't been able to spot the uploaded file to choose for dirty flash. adb shows the file as uploaded , but again no sign of it with CWM Recovery. should I try to install TWRP recovery? with the nexus toolkit there is a function to flash a rom, but it says it will wipe the device first, so it's really not the option I was looking for. Another strange behaviour of CWM Recovery, or maybe my phone, inside mounts and storage menu, mount sdcard seems to be not working as it never changes to unmount after you click it. I think my memory went berserk and that's the reason why the phone rebooted and never woke up again. Maybe I'll take to the nearest job center to ascertain the damage...
thanks for all your help
berniefranz said:
Thanks, CWM doesn't have a file manager, but adb did actually pull the build prop id=JOP40D, so I'll go back to download the correct ROM and try to flash it..
Click to expand...
Click to collapse

installed TWRP and was able to see to rom.tar uploaded via adb in the download folder, but wasn't able to use to flash as probably both recovery wants .zip and not .tar, so I'll now untar and zip the stock rom and upload it again...
small steps...

had a md5 check fail during flash, so still no good news. I was surfing a bit when noticed that developers.google.com doesn't have a factory image for 4.2.1 jop40d but only for 4.1.2 jzo54k. Does this mean I should flash 4.1.2 and then update, or try directly for the 4.2.1 which I can't find (a working one)?

went back to CWM but installation failed as well as TWRP, so I guess my last option is to take it to a samsung job center to check whether I have a corrupted memory or else... ANyway thanks everybody for your support..
berniefranz said:
had a md5 check fail during flash, so still no good news. I was surfing a bit when noticed that developers.google.com doesn't have a factory image for 4.2.1 jop40d but only for 4.1.2 jzo54k. Does this mean I should flash 4.1.2 and then update, or try directly for the 4.2.1 which I can't find (a working one)?
Click to expand...
Click to collapse

Had to take it to the job center where, it was downgraded to 4.0.4 (have still to check which flavour) fixed something and Wiped everything. When I side about he post mortem backup and the intention to try a restore from there I was give an are you kidding look, it could crash again... sigh.
Anyway thanks everyone that spent some time to try and explain a noob how to try to solve this issue.. Now I've got a new galaxy nexus, so after a little grievance I'll start reading on how to flash a nice rom...
berniefranz said:
went back to CWM but installation failed as well as TWRP, so I guess my last option is to take it to a samsung job center to check whether I have a corrupted memory or else... ANyway thanks everybody for your support..
Click to expand...
Click to collapse

[Q&A] [ROM][CM-12.1][Un-official] D2SPR CyanogenMod 12.1

Q&A for [ROM][CM-12.1][Un-official] D2SPR CyanogenMod 12.1
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 [ROM][CM-12.1][Un-official] D2SPR CyanogenMod 12.1. 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!

Anyone have another download link for this Google drive on my phone just opens the zip as separate files when I try to download it.

bmx26 said:
Anyone have another download link for this Google drive on my phone just opens the zip as separate files when I try to download it.
Click to expand...
Click to collapse
Inside of drive, Try long pressing on it and clicking "download copy" it should download a copy to the downloads folder on your internal sdcard

using this rom cm12.1 for s3 sprint and its working great so far, only noticed two things........ camera not working and Battery but im going to see after a day or two if the battery last the same as the previous rom i was on cm12 (camera was working sort of with the camera zoom fx and viva video work around but i used high speed camera plus instead of camera zoom fx with viva video and it was good)............. so cant wait for a working camera or some kind of work around for this rom cm12.1 s3 sprint.......

Silly mod question.
Im obviously new but was trying to determine where the zip file for the lollipop mod was for sphl710. I see the gapps files but cant locate the mod zip.

brad2512 said:
Im obviously new but was trying to determine where the zip file for the lollipop mod was for sphl710. I see the gapps files but cant locate the mod zip.
Click to expand...
Click to collapse
The google drive link has the file

Open Camera worked with CM 12 about 40-50% of the time.
So maybe it will work well with this one too?
Edit:
Sorry to hear about your laptop woes.
Opening up the laptop to do work and figuring out how it all goes back together again is not a fun prospect.

Brisky86 said:
Open Camera worked with CM 12 about 40-50% of the time.
So maybe it will work well with this one too?
Edit:
Sorry to hear about your laptop woes.
Opening up the laptop to do work and figuring out how it all goes back together again is not a fun prospect.
Click to expand...
Click to collapse
it might. I was reading about some commits on github that broke cameras across the board, stock or from the play store. I tear laptops apart regularly enough to remember how, it's the process itself that sucks

After messaging mastamoon, "I imagine all the stuff that's being worked on is basically in d2-common, msm8960-common and d2kernel which d2spr shares with d2vzw. I would just make sure whoever is building for d2spr is pulling in all the necessary hacks needed at the moment. Honestly I'm not sure what isn't committed at this point, but check out commits by Dave Daynard (nardholio) & Dan Pasanen (invisiblek) and make sure you're using that stuff."
The kernel (within this ROM) he's speaking of might help with the issues revolving around the camera.

Camera Works
Just thought I'd say that both cameras work all the time for me on the 4/09 build.

You said TWRP recovery is recommended but do you think its safe to flash on CWM because that is what I use. I have been thinking of switching Recovery's but don't have a computer to do so. Might try this app called "Flashify" or this "TWRP Manager" from play store that installs it to the device.

fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Good to know thank hou
---------- Post added at 01:53 PM ---------- Previous post was at 01:49 PM ----------
ChangeOfJinzo said:
You said TWRP recovery is recommended but do you think its safe to flash on CWM because that is what I use. I have been thinking of switching Recovery's but don't have a computer to do so. Might try this app called "Flashify" or this "TWRP Manager" from play store that installs it to the device.
Click to expand...
Click to collapse
Make sure you have the latest cwm recovery and you should be fine. I'd recommend flashify, I liked it better and seemed to function better then twrp manager. Also once you install twrp there's a method to update the recovery without a computer or making a recovery updater zip, which can also flash custom kernels. Though I recommend sticking with the stock kernel untill cm12.1 becomes more stable

fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Can anyone else confirm? I've yet to get this build in particular to boot...

iBlowpot said:
Can anyone else confirm? I've yet to get this build in particular to boot...
Click to expand...
Click to collapse
Well dont you have me a little scared now lol. I was gonna flash it tonight but this is the only phone I have until I get another s3, s4, or OnePlus One (don't know which yet) did you do this?
1-boot into recovery
2-Wipe data/Factory reset
3-Wipe Cache
4-Wipe Dalvik Cache
5-Format system
6-Install ROM
7-Install 5.1 Gapps
Did you try all this in the order? I usually do 1-5 Two times to just make sure.
Also make sure you have the latest version of the recovery your on (I use CWM so 6.0.4.5 , I believe that's the latest)

ChangeOfJinzo said:
Well dont you have me a little scared now lol. I was gonna flash it tonight but this is the only phone I have until I get another s3, s4, or OnePlus One (don't know which yet) did you do this?
1-boot into recovery
2-Wipe data/Factory reset
3-Wipe Cache
4-Wipe Dalvik Cache
5-Format system
6-Install ROM
7-Install 5.1 Gapps
Did you try all this in the order? I usually do 1-5 Two times to just make sure.
Also make sure you have the latest version of the recovery your on (I use CWM so 6.0.4.5 , I believe that's the latest)
Click to expand...
Click to collapse
What're you afraid of? If it is "stuck" during installation one could press and hold the power button or remove the battery in an effort to enter recovery again (I've yet to get it beyond installation).
As for the process I use I do the same thing I've been doing for years. Same process I used to install 04/07. I've downloaded and tried at least 5 times.

iBlowpot said:
What're you afraid of? If it is "stuck" during installation one could press and hold the power button or remove the battery in an effort to enter recovery again (I've yet to get it beyond installation).
As for the process I use I do the same thing I've been doing for years. Same process I used to install 04/07. I've downloaded and tried at least 5 times.
Click to expand...
Click to collapse
A long boot can be common after a flash or an update. I've read reports of it taking 30 min for the phone to boot after one or the other.

Lrs121 said:
A long boot can be common after a flash or an update. I've read reports of it taking 30 min for the phone to boot after one or the other.
Click to expand...
Click to collapse
04/09 does not install on my end. I did not make it to the boot animation. It does not go beyond the recovery.

fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Can you tell us the recovery, gapps, etc that you are using? Any custom kernels? No one else is having this same luck, unfortunately.

iBlowpot said:
04/09 does not install on my end. I did not make it to the boot animation. It does not go beyond the recovery.
Click to expand...
Click to collapse
Probably a bad upload. I recommend using the new build.
FatalIll said:
Can you tell us the recovery, gapps, etc that you are using? Any custom kernels? No one else is having this same luck, unfortunately.
Click to expand...
Click to collapse
also what bootloader and firmware version

Lrs121 said:
also what bootloader and firmware version
Click to expand...
Click to collapse
Hell, just give us your phone
Also, Lrs121... You had mentioned that you may try and cherry pick updates from other builds where the camera is working. I don't know much about cm source or building but have you considered using something like 'kaleidoscope git diff' to compare builds and see maybe where the camera fix is hiding?
Edit: not necessarily kaleidoscope, but git diff in general.

Cyanogen OS system upgrade

Hi all
My friend's wife has a swift with YOG4PAS33J and he says her notifications mention a system upgrade.
Has anyone else noticed same? I ask because https://cyngn.com/support mentiones Cyanogen OS 12.1 (5.1.1) cm-12.1-YOG4PAS33J-crackling.
Thanks

Yes I have installed the upgrade YOG7DAS2FI and now running cyanogen 12.1.1.

Yep - changelog on twitter (Wileyfox).
It seems I haven't posted enough to allow me to post links.

is a ZIP file available for flashing via TWRP?

Dior DNA said:
is a ZIP file available for flashing via TWRP?
Click to expand...
Click to collapse
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver

mermigas said:
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
Click to expand...
Click to collapse
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI

Dior DNA said:
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Click to expand...
Click to collapse
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464

mermigas said:
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
Click to expand...
Click to collapse
your russian seems good enough
meanwhile https://cyngn.com/support got updated

Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!

seb5049 said:
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
Click to expand...
Click to collapse
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).

Dior DNA said:
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Click to expand...
Click to collapse
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.

seb5049 said:
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
Click to expand...
Click to collapse
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.

mermigas said:
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
Click to expand...
Click to collapse
Should I install everything in the zip? Won't that wipe all of my data?

seb5049 said:
Should I install everything in the zip? Won't that wipe all of my data?
Click to expand...
Click to collapse
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.

Dior DNA said:
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Click to expand...
Click to collapse
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?

seb5049 said:
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
Click to expand...
Click to collapse
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success

Dior DNA said:
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Click to expand...
Click to collapse
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.

seb5049 said:
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
Click to expand...
Click to collapse
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated / changed during or right after upgrade.

Dior DNA said:
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated change during or right after upgrade.
Click to expand...
Click to collapse
Yeah, I did. By the way, I disabled the permissions again, but everything's fine now.