[NIGHTLY][ROM][4.4] CyanogenMod 11 for Samsung Captivate - Captivate Android Development

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Downloads
Latest build: http://download.cyanogenmod.org/?device=captivatemtd
Google Apps: http://wiki.cyanogenmod.org/w/Gapps
Installation
- First time flashing CM11 to your Captivate (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM7/CM9?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM10/10.1?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
You will finally see a "set_metadata_recursive" status 7 error. That is normal.
Reboot back into recovery (the reboot is required)
Install the ROM again from internal sdcard using ClockworkMod Recovery
Optionally restore /data from Nandroid Backup (the update will wipe your /data)
Optionally install the Google Addon
- Upgrading from CM10.2?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from another build of CM11?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Warning: You may get set_metadata_recursive related-errors during install if you're using a custom kernel without SELinux support. In that case, revert to the stock kernel before continuing or follow the instruction for upgrading from CM10.1.
Note: The partition layout of CM11 is the same as CM10.2.
Known Issues
See here
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
FAQ
See here
IRC
Join us on #teamhacksung-support (user channel) or #teamhacksung (developer channel)
Changelog
A rough changelog is (will be) available here:
http://changelog.bbqdroid.org/#/captivatemtd/next or http://www.cmxlog.com/11/captivatemtd
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

First!!

Good work mate :good:

Nice :good::good:

how awesome is this! thank you pawitp!

Nice Work Pawitp! Finally Official

Thanks for keeping our outdated device alive. We appreciate all the work you put into it.

Thank you !!

I attempted to try it. I did use the new recommended Gapps. AT&T Captivate coming from CM 10.2 (4.3) stable. It would boot and then gave my a choice of two launchers. The first on I tried gave me intro screens but in about 30 seconds it would go into a soft reboot which it did not recover. I then did a reboot with the power and volume buttons and chose the second launcher. Same intro screen but it went a bit further and showed a few icons (which I did not recognize) and then in went into a soft reboot which again I had to do a reset. This time I wiped the caches and tried another reboot. I decided to wait a while when it rebooted to see if that made any difference. After about 45 seconds it went into another soft reboot. This time I did a restore and I am back to CM 10.2. I am going on vacation so I won't be able to try anything for 10 days.

Same here; not booting.
Mine is stuck at the CM logo and the arrow going round and round the logo.
This has been going on for more than 2 hours now.
Going to pull the battery and try again.

hirent said:
Same here; not booting.
Mine is stuck at the CM logo and the arrow going round and round the logo.
This has been going on for more than 2 hours now.
Going to pull the battery and try again.
Click to expand...
Click to collapse
Please get a logcat
Sent from my Nexus 4 using xda app-developers app

pawitp said:
Please get a logcat
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, I just pulled the battery and booted into recovery.
Wiped everything twice (did it before too) and installed CM11. Rebooted recovery and reinstalled CM11 again.
Rebooted device and voila, it booted up.
Don't know what changed but it booted up this time. I'd wiped everything the first time too.
Anyway, thanks for the work that you have put in. And also for responding above.

hirent said:
Well, I just pulled the battery and booted into recovery.
Wiped everything twice (did it before too) and installed CM11. Rebooted recovery and reinstalled CM11 again.
Rebooted device and voila, it booted up.
Don't know what changed but it booted up this time. I'd wiped everything the first time too.
Anyway, thanks for the work that you have put in. And also for responding above.
Click to expand...
Click to collapse
I believe I did the same thing as you but I kept getting a soft reboot (which it did not recover from) in about 45 seconds to a minute after it booted up. I'll try again when I get back from vacation.

This may or may not be a dumb question lol. Any need for a bootloader flash? I ask because it was required from 4.3 to 4.4 on my nexus 4. Thanks for keeping this captivate alive!

murph187 said:
This may or may not be a dumb question lol. Any need for a bootloader flash? I ask because it was required from 4.3 to 4.4 on my nexus 4. Thanks for keeping this captivate alive!
Click to expand...
Click to collapse
There hasn't been any bootloader updates since 2.3
Sent from my Nexus 4 using xda app-developers app

Wow, wait for a long time. Thanks so much
Sent from my SGH-I897 using XDA Premium 4 mobile app

Should I 4.4? or not yet?
I'm now on hellybean 4.3.1... do you recommend to flash the new 4.4 CM?
Thanks for your help

J o s e p h said:
I'm now on hellybean 4.3.1... do you recommend to flash the new 4.4 CM?
Thanks for your help
Click to expand...
Click to collapse
CM10.2 has now stable release, CM11 is in alpha stage. It's your choice.

Just to say thanks to pawitp for the excellent work!
I'm running Android 4.4.1 on a >3y old device and with the apps I use it's stable enough for a daily driver, no single FC. :good:
P.S. Wow! Fresh start, 190MB free RAM! And it runs smoother than JB! Must taste KitKat...

Val D. said:
Just to say thanks to pawitp for the excellent work!
I'm running Android 4.4.1 on a >3y old device and with the apps I use it's stable enough for a daily driver, no single FC. :good:
P.S. Wow! Fresh start, 190MB free RAM! And it runs smoother than JB! Must taste KitKat...
Click to expand...
Click to collapse
yeah, i'm happy with this rom, but i hope "Cannot send SMS to "premium" number (wait for fix from CM core)" will be fixed soon. I can not send right now

Related

CM6 ROM Kernel GAPPS etc (intalling and updating) Oct14th

a friend recently asked about geting onto and updating CM6. i wrote this up and figued it may be helpful to others. nothing new, just a compilation of info.
CM6.1 is coming out soon. 10/17/10 is the official freeze on code. Android Open Source Project (AOSP) is a primary keyword for you when interacting on the forums. always make sure you are working with AOSP compatible stuff.
update the ROM to get the latest nightly feature or once some instability has been fixed.
update the kernel to get improve battery life and/or smoothness
update the GoogleAPPS because you wont use the ones on the marketplace...use these.
using AmonRA...(first time installing CM6 = wipe all...after that when updating just wipe the the two cache mentioned)
download all files to the root of your sdcard
reboot into recovery
make a nandroid
wipe cache and dalvik cache
flash ROM
flash gapps
flash kernel
(i don't think the flash order is actually important)
reboot
CM6 ROM
- still the main thread. OP is not updated.
http://forum.xda-developers.com/showthread.php?t=735596
download: http://mirror.teamdouche.net/?device=supersonic
- most updated OP. best source for updated nightly info as of now
http://forum.xda-developers.com/showthread.php?t=729802
Kernels: Nov5 ... i suggest running stock kernel until the following are updated to the .35 kernel. There is a now a flashable .35 available from Flipz.
- zendroid ... Nov11..still in alpha but getting good reviews. using the .35 kernel
http://forum.xda-developers.com/showthread.php?t=831021
- snap .... i have not tried turbo. (note...turbo requires a full wipe to remove turbo)
http://forum.xda-developers.com/showthread.php?t=733099
- kingklix ... i think there is an issue as of his cfs#1 where wifi tethering does not work..it is expected to be fixed. otherwise nice.
http://forum.xda-developers.com/showthread.php?t=773058
download: http://kingxklick.com/forum/viewtopic.php?f=8&t=203
GAPPS:
updated often enough its worth the occasional checkin. make sure to get the HDPI (as in High Def screen)
http://mirror.teamdouche.net/?type=gapps
edit...the team site is being a douche...this link should work for gapps
http://wiki.cyanogenmod.com/index.php?title=Latest_Version
fun toys:
http://circle.glx.nl/
you can start here to get a better overall feel. http://forum.xda-developers.com/showthread.php?t=764521
this site looks a bit intimidating at first. basically, remember downloading that CM6 nightly to your computer? ok...go to that file. extract it like any zip file. find a particular .apk file. put a copy of that file in another location. go to the www, read the HowTo, go to the Kitchen and click next...then follow the yellow brick road. (make sure to make a nandroid before you start)
note... Snap and King are still using the older .32 kernel. while stable and good, the Framework changes to the latest versions of CM6 will cause somethings to not work (ie: bluetooth).
i would wait for JMX to update the snap kernel before getting too fired up. the next snap kernel will be exquisite I'm sure. the current stock kernel is pretty solid.
Rumor has it that Snap might be skipping .34 altogether and going straight to .35 since spiicytuna and toastcfh are both working on it.
In other words, jmxp69 might be skipping CM6.1's and going straight to CM6.2's kernel.
Do we flash all three of those things in one recovery 'session' or should I reboot after every flash? Trying CM6 for the first time coming from Fresh, a bit nervous. Got my nandroid backup just in case. Even if I wipe data, my nandroid will restore all of my apps, contacts, settings, etc right?
Yes, to the backup question.
As for flashing:
0) Wipe data+cache
1) Flash CM
2) Flash Gapps
3) Reboot into Android
(Optional: 4) Reboot into recovery and wipe dalvik+cache, flash custom kernel, reboot into Android)
fmedina2 said:
Do we flash all three of those things in one recovery 'session' or should I reboot after every flash? Trying CM6 for the first time coming from Fresh, a bit nervous. Got my nandroid backup just in case. Even if I wipe data, my nandroid will restore all of my apps, contacts, settings, etc right?
Click to expand...
Click to collapse
if you are uncertain, then i suggest doing it one step at at time. with time and repetition you'll find which you can group together. i do all three in one session, however, if i get stuck in a boot loop or some other weirdness...i feel confident i can figure which of the three caused the issue and proceed from there. that has not always been the case.
yes. nandroid is a snapshot of your device setup/config. i have a Fresh ROM and my CM6 ROM in nandroid. just in case i ever need 4G (granted i haven't booted it up in almost 2mths.lol).
and yes, i'm looking forward to what JMX does with the Snap kernel when based on .35. a very very early .35 from Toast is floating around. i'll prolly flash it today to see how it is.

[Q] Can't Install GAPPS on my Nexus 7

Hi Everyone,
Sorry my first ever post is a question, but I have looked around a lot and can't find an answer for my problem.
I have a 16gb nexus 7 that I have rooted and unlocked the bootloader. I have successfully flashed both CM10 and AOKP roms, but each time flashing the GAPPS afterwards results in absolutely nothing. The ROMs work fine, and I can still access the Play store, but none of the GAPPS show up in my Applications folder. I have tried this multiple times with multiple GAPPS zips.
I flashed ClockworkMod Recovery, but interestingly I can only get into it by rebooting via CM10 or AOKP reboot to recovery options, or through ROM Manager's reboot option. If I manually enter fastboot then try to go to recovery it hangs on the Google loading page.
I am okay with the CWM issue, but I would really like to be able to flash the GAPPS zips! I change ROMs a lot (I have a Galaxy Nexus, which I have never had any issues with), so manually installing the google apps each time would be a pain.
Any help would be appreciated!
Hello,
Are you flashing this right after flashing the rom or are you booting into the rom then restarting and flashing the gapps?
You should be doing this...
Be sure to back up your current ROM!
Update your radio to the above recommended version if you have not already done so.
Wipe data/factory reset.
Format /system (mounts and storage->format /system).
Install the zip from SD card.
Install the gapps zip from SD card.
ONLY IF YOU ARE ON NON-TOUCH CWM RECOVERY: Install darkside-wipe-cache-only.zip (which fixes bootloop due to bad /cache format)
ONLY IF YOU ARE ON TOUCH CWM RECOVERY: Format /cache (mounts and storage->format /cache)
Reboot. Let it sit for a few minutes after the first boot. Be patient.\
good luck!!
Yes I flash the gapps immediately after flashing the rom without actually booting in to the rom first.
I have been doing a full wipe, but I did not re-format so I will try that later when I have time.
Also, never heard of the darkside wipe cache zip so that is probably my issue with the bootloop!
As for the radio, I could be totally wrong, but does the nexus 7 even have a radio file..? I thought that was just for phones or tablets that can connect to network carriers.
Thanks for the help!
sloambbr said:
Yes I flash the gapps immediately after flashing the rom without actually booting in to the rom first.
I have been doing a full wipe, but I did not re-format so I will try that later when I have time.
Also, never heard of the darkside wipe cache zip so that is probably my issue with the bootloop!
As for the radio, I could be totally wrong, but does the nexus 7 even have a radio file..? I thought that was just for phones or tablets that can connect to network carriers.
Thanks for the help!
Click to expand...
Click to collapse
You are absolutely right about the radio. Your welcome.
no6969el said:
You are absolutely right about the radio. Your welcome.
Click to expand...
Click to collapse
hey i tried everything you said and still no gapps... I tried to do a titanium backup of the stock rom then use that to install the gapps on the aokp rom but that didnt work either. I did notice though that when I did not install the gapps package the play store wasnt installed, but if i install the gapps zip, the play store is there...just none of the other apps.
Just search apps by Google inc on play if you have the store
Sent from my Nexus 7 using xda app-developers app
Harry GT-S5830 said:
Just search apps by Google inc on play if you have the store
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It would nice to not need to do that every time as I frequently flash new roms but oh well I will do that for now. Maybe it will change with a new update
I have the same issue. Using CWM I've installed two different roms and two different gapps versions (using the recommended procedure) both times my Nexus 7 boots up & the only Google app installed is Play Store.
I'm having a related problem with GAPPS but it's much more severe.
I have installed the Kaos rom on a Nexus 7 (and that install would ONLY succeed if one de-selected the GAPPS option during the Kaos installer process, otherwise you'd be thrown into infinite boot animation land) and everything was looking perfect.
Then i attempted to install GAPPS from a zip that was linked in a Nexus 7 thread. the specific package i used was...
gapps-jb-20120726-signed.zip
... and ever since that point the tablet cannot boot into the Android environment. It will attempt to, then hang for longer than it should at the Google logo screen (tiny lock at the bottom) and when that fails it will boot into the recovery environment.
I'm running TeamWin Recovery 2.2.1.4 because ClockworkMod constantly failed to work properly for me (never could manually launch recovery from the bootloader, but TWRP will launch manually just fine)
The TeamWin Recovery can see everything and even give me a terminal, and fastboot still sees the device just fine at the bootloader... so there's a lot i could try, if i only knew where to start.
The REAL annoying thing, however, is that i performed a backup just prior to attempting the GAPPS install (because of all the trouble this gives people) and now TWRP cannot successfully restore that backup. it can see both of the backups that i have made (stock and Kaos initial successful boot) but whenever i attempt to swipe to the side to start the restore, the whole recovery environment just restarts on me.
help? suggestions?
well, i see that i wasn't running the latest TWRP for the Nexus 7. i just used fastboot to flash to ver 2.3.2.1 and that appeared much happier.
it was able to see the two recovery images made by the earlier version and it's now restoring...
... and now we're rebooting...
... and KAOS appears to be proper booting...
... and back in business to the way it was before i tried the GAPPS install!
(this single run-on post -- as opposed to a series of small update posts -- brought to you by the faster processor and nice system specs of the Nexus 7 which kept on ticking along as i was typing here in my browser!)
---------- Post added at 06:26 AM ---------- Previous post was at 06:03 AM ----------
and now i have successfully installed GAPPS using a 4.1.2 package... gapps-jb-20121011-signed.zip
it's amazing how things can go sideways so quickly if you're simply using the wrong version of one thing or another. and it's also amazing how quickly these threads become outdated given the very fast pace that Android keeps evolving and how fast the dev community pops up with new packages, roms, and mods of other roms.
speaking of which, the KAOS fork of CyanogenMod is excellent! i already love the Apex launcher more than the stock Trebuchet (little interface tweaks like a quick menu popup whenever you long press a home screen item, for example) and i think this is a wonderful rom package.
great work, and a wonderful installer... just remember to NOT include GAPPS during the initial rom install process! uncheck that box!
UPDATE: gapps install incomplete / market installs failing
So it seems that while my Nexus 7 now shows the Play Store (which i still find myself calling the Market because Play Store is a colossally dumb name) i don't see most other Google apps.
Background sync and all that is working, but maps and youtube and such are not there. I've read that these are removed from newer versions of the GAPPS pacakges because it takes up less space and said apps are in the Market anyway.
however, when i search for them and pull them up in the Google Market they fail to install. i do not know why this would be. it doesn't matter a WHOLE lot to me, because i don't use GMail, i run Brutal Maps instead of stock Google Maps, and NextVid is far better than the stock, bloated YouTube player.
still, it made me curious.
so, it appears that i am not the first person to experience the "Unknown error code during application install" error, naturally. the (very simple) fix is in this thread.. http://forum.xda-developers.com/showthread.php?t=1992241

[Q] Downgrading from 2ndboot to CM9/10

Dear All,
I am using MB526 (Defy+) and I have updated my phone to 2nd boot nightly by Quarx. (Thanks a lot for your great work buddy).
Now, I have a problem, since then My phone is running very slow, email taking time to showup. Messages taking time, Phone app also very slow.
I tried searching the entire XDA community but unable to find the post to downgrade from 2ndboot nightly to CM9, i liked CM9 best with great battery backup.
Can you please help me with, How to Downgrade from 2ndboot to CM9, I have not taken any nandroid backup and need to do it really fast.
Any help will be highly appreciated. Please help Quarx and team.
Regards,
Amit Sharma
Thanks everyone for help, my Defy+ is working absolutely fine now. with CM9 currently.
[email protected] said:
Dear All,
I am using MB526 (Defy+) and I have updated my phone to 2nd boot nightly by Quarx. (Thanks a lot for your great work buddy).
Now, I have a problem, since then My phone is running very slow, email taking time to showup. Messages taking time, Phone app also very slow.
I tried searching the entire XDA community but unable to find the post to downgrade from 2ndboot nightly to CM9, i liked CM9 best with great battery backup.
Can you please help me with, How to Downgrade from 2ndboot to CM9, I have not taken any nandroid backup and need to do it really fast.
Any help will be highly appreciated. Please help Quarx and team.
Regards,
Amit Sharma
Click to expand...
Click to collapse
- What version are you on? Tried the newest nightly from November 9th? It runs like a charm!
If you want to downgrade anyways, go ahead as follows:
- First of all you should save your apps with Titanium Backup or similar.
- Afterwards enter the CWM-Recovery and make a full backup (in case something goes wrong, you can go back CM10)
- Make a full wipe
- Install CM9 + ICS Gapps
- Boot your phone
- Install Titanium Backup from PlayStore
- Restore your apps. IMPORTANT: Don't restore apps that are only working with Android 4.1.x (like anything Google-related) This might give you trouble (force close e.g.). You should install these apps from the play store again.
Swift2603 said:
- What version are you on? Tried the newest nightly from November 9th? It runs like a charm!
If you want to downgrade anyways, go ahead as follows:
- First of all you should save your apps with Titanium Backup or similar.
- Afterwards enter the CWM-Recovery and make a full backup (in case something goes wrong, you can go back CM10)
- Make a full wipe
- Install CM9 + ICS Gapps
- Boot your phone
- Install Titanium Backup from PlayStore
- Restore your apps. IMPORTANT: Don't restore apps that are only working with Android 4.1.x (like anything Google-related) This might give you trouble (force close e.g.). You should install these apps from the play store again.
Click to expand...
Click to collapse
Thanks for the update, I am using "CM10-20121109-NIGHTLY-mb526" - 9th November one, But my phone is not working properly, dont know the reason for the same.
I tried using the mentioned to go on CM9 but it says that your phone is restricted and you need to do full wipe to use it, I tried CM9 and 10 but nothing works.
I am facing these problems currently.
- Lock Screen takes time after pressing power key (2-3 seconds)
- Contacts are not showing properly, most of the time not responding.
- Phone app also not responding properly, very Slow
Please help if you can, Appreciate your support. I am using MB526 (Defy+) with red lense, if it help.
Regards,
Amit Sharma
Build of 0211 is better than 0911
I agreed with Mr. Amit I am trying all roms of 2nd boot Quarks.
I also felt that some apps / games runs slow on 0911 hence turn back to 0211. ** with update for cm file manager.
avi_tandel said:
I agreed with Mr. Amit I am trying all roms of 2nd boot Quarks.
I also felt that some apps / games runs slow on 0911 hence turn back to 0211. ** with update for cm file manager.
Click to expand...
Click to collapse
avi_tandel; thanks for your help, can you help me with the way to downgrade to CM9? someone please, please, please help.
Regards,
Amit Sharma
For the downgrade to CM9:
-DataWhipe/Fullwhipe
-Install the Cm9 nightly you want
-install Gapps
-Format Cache/Dalvik Cache
(I recommend a Nandroid of your running System so that you can return if the installation fails)
And btw. i would recommend CM7.2 for example Whiterabbit1.7.1
CM10 is way too slow in my opinion(Yes Slimbean and everything else is also slow)
Steveletack said:
For the downgrade to CM9:
-DataWhipe/Fullwhipe
-Install the Cm9 nightly you want
-install Gapps
-Format Cache/Dalvik Cache
(I recommend a Nandroid of your running System so that you can return if the installation fails)
And btw. i would recommend CM7.2 for example Whiterabbit1.7.1
CM10 is way too slow in my opinion(Yes Slimbean and everything else is also slow)
Click to expand...
Click to collapse
Dear Friends, I did the same but unable to login now. it says
Encryption unsuccessful
Encryption was interrupted and cant complete. As a result, the data on your phone is no longer accessible.
Please help dear friends. please save me.
Regards,
Amit Sharma
[email protected] said:
Dear Friends, I did the same but unable to login now. it says
Encryption unsuccessful
Encryption was interrupted and cant complete. As a result, the data on your phone is no longer accessible.
Please help dear friends. please save me.
Regards,
Amit Sharma
Click to expand...
Click to collapse
EDIT: I just saw your post in the other thread. Would you mind to mark this as solved? Thx
Perhaps you should describe more detailed what you are trying to do when the error message pops up, and you should give the error message word by word.
I am not familiar with data encryption but your post sounds as if you have lost your data partition now. If that is the case you should completely wipe your phone and start over with flashing a fixed sbf-file. That would be the smartest way to rescue your smartphone (sorry, couldn't withstand :cyclops

[ROM] [WIP] [DEV] Ubuntu Touch 13.10

Warning:
This is very alpha version of Ubuntu Touch. IT'S NOT READY FOR DAILY DRIVER. This is mainly for those curious souls like me that simply can't wait to try it on the find 5. There are and will be bugs. When that is said, lets get started.
Requirements before doing anything:
You will need to read the full guide before starting to do it. Just so you know what to do.
Downloads:
1. ubuntu image
2. saucy-preinstalled-touch-armhf.zip
3. extra zip
How to flash:
1. Reboot to recovery, i tested with twrp but any should do.
2. Make a full backup so you can restore after playing with ubuntu touch
3. Wipe System, Data, Dalvik-cache and Cache
4. Flash Ubuntu image....
5. Flash saucy-preinstalled.zip
6. Flash extra zip.
7. Reboot to System.
-------------------------------------
A few notes:
If you starts camera, you can shoot images but sometimes images files are corrupted, but back and front camera are working, also does flash.
If you enter video recording and starts that, camera app will freeze, you can then just exit it by swyping to the side and then long press camera under Recent apps and hit the X.
then camera can be tested again.
if you want to test music player, it can be done this way :
Code:
adb push testsong.mp3 /home/phablet/Music
adb chown phablet:phablet /home/phablet/Music/testsong.mp3
adb chmod 777 /home/phablet/Music/testsong.mp3
Then if you enter music player it should show a song that can be played. It failed for me the first time so I needed to reboot to recovery, with adb reboot recovery , then did "how to flash" again and after that when trying to boot it failed, and i needed to go back to recovery and do it all over with "how to flash but no wipe". When phone booted i started up the music app and can now play the song with or without wired headset
If you dont start music player before you push the song to the phone and all that, its possible that it can see the song without all the reflashing thing.
The reason for the reflash thing is that if you just reboots ubuntu, it will fail to bootup.
starting apps and switching between those is also working, sometimes phone gets a bit slow and not all apps is working, like soduku will not startup, but alot others is workiing fine.
Working:
Speaker
Camera
Sim card signal with 3g | sim card pin code needs to be disabled on phone before flashing ubuntu.
WiFi
Sms
Bootup.
A few important notes:
1. You cant reboot ubuntu in curret state, it will end up in bootloop.
2. To reboot to recovery use :
Code:
adb reboot recovery
This is a wip (work in progress) and need alot of work and i will do whatever i can to get it good.
Some images can be found here and a review here
Im hoping we can work together on this one so we can get it usefully as a dayli driver. So if you want to help, just pm me.
Sources:
Device tree
Vendors
Kernel
XDA:DevDB Information
[ROM] [WIP] [DEV] Ubuntu Touch 13.10, a ROM for the Oppo Find 5
Contributors
anders3408
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2013-09-19
Last Updated 2013-09-20
Reserved
Cool. Alpha indeed but awesome work nonetheless. Can't wait to see this progress. With roughly the same internals as mako and n4 hopefully the port goes smoothly. Cheers!
Sent from my Find 5 using Tapatalk 4
killerskincanoe said:
Cool. Alpha indeed but awesome work nonetheless. Can't wait to see this progress. With roughly the same internals as mako and n4 hopefully the port goes smoothly. Cheers!
Sent from my Find 5 using Tapatalk 4
Click to expand...
Click to collapse
Just as you think a device is about to "die" and be replaced by a newer version, a developer comes up with this stunning ROM to breath fresh life into it.
I don't want to get rid of my device now!
robifis said:
Just as you think a device is about to "die" and be replaced by a newer version, a developer comes up with this stunning ROM to breath fresh life into it.
I don't want to get rid of my device now!
Click to expand...
Click to collapse
I don't really see the Oppo find5 on it's way to the pasture just yet.
killerskincanoe said:
I don't really see the Oppo find5 on it's way to the pasture just yet.
Click to expand...
Click to collapse
Me neither. I'm sure this device will be running great for a long time.
Sent from my Find 5 using XDA Premium HD app
Thanks for this! Going to try this in the weekend
Sent from my Find 5 using xda app-developers app

[Guide] A guide to KitKat

Hello, recently there have been a lot of posts requesting help with KitKat on our device. This is why I have created a guide going through the installation, setup, issues and many other aspects of KitKat on our phone.
1. List of KitKat ROMs:
OmniROM
CyanogenMod
ParanoidAndroid
SlimKat
Illusion Roms
C-RoM
SlimSaber
CarbonRom
Dirty Unicorns
MoKee OpenSource
Resurrection Remix
Asylum Omni
2. Installation
If you are on the stock Jelly Bean/ICS Samsung firmware:
-Download Philz kernel and copy it to your SD card
-Download a KitKat ROM and copy it to either your internal or external memory
-Download PA-Google Apps and copy it to either your internal or external memory
-Download Raw Kernel r5 and copy it to either your internal or external memory
-Reboot to recovery by holding down volume up, power and home button at once until you are in recovery mode
-Flash Philz kernel
-Go to "Mounts and Storage" and format /system, /data, /preload
-Reboot to recovery again by going to "advanced", "reboot to recovery" or by holding down volume up, power and home button at once until you are back in recovery mode
-Flash Raw Kernel
-Reboot to recovery again
-Flash your ROM
-Flash PA-Google Apps
-Reboot
If you are on any AOSP based firmware or on any custom TouchWiz ROM:
-Download a KitKat ROM and copy it to either your internal or external memory
-Download PA-Google Apps and copy it to either your internal or external memory
-Download Raw Kernel r5 and copy it to either your internal or external memory
-Reboot to recovery by holding down volume up, power and home button at once until you are in recovery mode
-Flash Raw Kernel
-Go to "Mounts and Storage" and format /system, /data, /preload (formatting /preload may fail, skip if it does)
-Reboot to recovery again by going to "advanced", "reboot to recovery" or by holding down volume up, power and home button at once until you are back in recovery mode
-Flash your ROM
-Flash PA-Google Apps
-Reboot
3. Updating your firmware
Updating your system is very easy, some ROMs (ex. OmniROM) have a built-in updater. Simply go to Settings, About phone and "Update". After that just follow the instructions on screen.
If your ROM doesn't support that option or you want to go old-school:
-Download the updated ROM to your internal/external memory
-Reboot to recovery
-Flash the ROM
-Reboot
4. Bugs, issues
When flashing any KitKat ROM I get a "Status 7 error".
You didn't follow the installation procedure carefully enough. You most probably forgot to flash Raw Kernel or you forgot to reboot to recovery after flashing Philz or Raw Kernel.
Sometimes whilst listening to music, the track freezes and I can no longer access it.
KitKat for our device has a bug in it where this happens. There is NO fix for this. Only a reboot will allow you to access the file again.
Refer to this thread for more information.
UPDATE:
The bug has been fixed however not all ROMs have merged the fix yet. If you are still having this issue then try flashing a kernel with the fixes merged (for example Forest Kernel or Raw Kernel).
Sometimes whilst copying files from my computer, the copying process stops.
This is the same issue as the above one with the music bug. One way to copy files without a problem is to reboot to recovery, go to mounts and storage and go for "mount USB storage". Copying through recovery is stable.
UPDATE:
The bug has been fixed however not all ROMs have merged the fix yet. If you are still having this issue then try flashing a kernel with the fixes merged (for example Forest Kernel or Raw Kernel).
I have battery issues.
This can be caused by many reasons, mainly your apps. Here are a few quick fixes though:
1. If your battery is at least a year old then it may be time to replace it with a new original one
2. Go to Settings, Wi-Fi, menu button, advanced and unmark "Scanning always available"
3. Install Greenify
4. If your ROM supports it, go to App Ops (On CarbonROM: Settings, Privacy, Privacy Guard, menu button, advanced) and disable the permission "keep awake" from as many apps as possible. Do not disable this permission from alarm clocks, email clients etc.
You can also disable other permissions, such as location which will also save your battery life
5. Install Titanium Backup and freeze/uninstall as many un-used apps as possible
6. Install Wakelock Detector to find out what is keeping your device awake
7. If you still have problems, refer to this thread
I haven't got ROOT access.
This usually affects OmniROM users. Download SuperSU zip and flash through recovery mode
I want access to Developer options.
Go to Settings, About phone and tap 7 times "Build number"
I want to change the runtime to ART.
Go To Settings, Developer options and find "Select runtime". Don't forget that the ART runtime is still in development by Google and bug reports shouldn't be filed against ROMs if you experience problems on ART
Every single time I change to the ART runtime, it doesn't change and stays on the current Dalvik runtime.
You have Xposed installed which is stopping you from changing it as Xposed is incompatible with ART. Uninstall Xposed to fix this.
I hope you have found this mini guide useful. If you still have any doubts, please don't hesitate to request more help in this thread.
If you have any suggestions as to what else should be included in this guide, don't forget to drop a line or two.
Nicely done.
Wow u really did a great one there. Hopefully this will be a great help to all "lost sheeps" out there. Well done!
Sent from my GT-N7000 using XDA Free mobile app
Thanks guys
This should be a sticky!
Nice job! Thread stuck.
XxPixX said:
3. Updating your firmware
-Wipe cache
-Go to Advanced, wipe dalvik cache
Click to expand...
Click to collapse
There's no need to wipe anything when dirty flashing updates.
Towle said:
Nice job! Thread stuck.
Click to expand...
Click to collapse
Thank you
chasmodo said:
There's no need to wipe anything when dirty flashing updates.
Click to expand...
Click to collapse
Updated, thanks
Very nice, but I'm sticking with 4.1.2 for several reasons.
One, Samsung hasn't officially (and seriously doubt they will, device is almost 3 years old) released
4.4 to the Note N7000. I usually stick with stock roms (different kernel obviously).
Two, to get kk, you have to jump through some hoops to get it on your device. I'm not above doing it,
it's just too much of a pain, to have to load all the apps, settings etc. Should be a "drag & drop" or
just click, to install.
Three, pretty much every KK rom I've seen, for the N7000, has a glitch here, bug there, battery problem,
BT problem etc. I've heard people flash the same rom to two different N7000's and one works perfect, the
other doesn't.
Four, I've had 4.1.2 on mine, since the day it came out, and, without a doubt, it's been for my usage, pretty
much the most stable rom I've used. When I was younger, back in the 386/486 computer days, it was nothing
for me to spend an evening, tweaking front side buss settings, memory timings, config.sys & autoexec.bat files
to tweak 1-2 seconds of performance from a PC. Today, I'm just after decent performance, and STABILITY.
This device, sadly IS my lifeblood for work. I don't have time for rebooting, lock ups, glitches etc.
I'm shopping around for device...the Note3 was on the list, but the price (I don't do contracts anymore) is a bit
steep, along with getting one to work properly in the USA, means you almost always have to get a LOCKED
down at&t device, with features removed, bloat etc. Got a few on the radar, but I'll just keep going with the N7000.
I'll hate to put her out to pasture, she's been a good ride.
p51d007 said:
Very nice, but I'm sticking with 4.1.2 for several reasons.
One, Samsung hasn't officially (and seriously doubt they will, device is almost 3 years old) released
4.4 to the Note N7000. I usually stick with stock roms (different kernel obviously).
Two, to get kk, you have to jump through some hoops to get it on your device. I'm not above doing it,
it's just too much of a pain, to have to load all the apps, settings etc. Should be a "drag & drop" or
just click, to install.
Three, pretty much every KK rom I've seen, for the N7000, has a glitch here, bug there, battery problem,
BT problem etc. I've heard people flash the same rom to two different N7000's and one works perfect, the
other doesn't.
Four, I've had 4.1.2 on mine, since the day it came out, and, without a doubt, it's been for my usage, pretty
much the most stable rom I've used. When I was younger, back in the 386/486 computer days, it was nothing
for me to spend an evening, tweaking front side buss settings, memory timings, config.sys & autoexec.bat files
to tweak 1-2 seconds of performance from a PC. Today, I'm just after decent performance, and STABILITY.
This device, sadly IS my lifeblood for work. I don't have time for rebooting, lock ups, glitches etc.
I'm shopping around for device...the Note3 was on the list, but the price (I don't do contracts anymore) is a bit
steep, along with getting one to work properly in the USA, means you almost always have to get a LOCKED
down at&t device, with features removed, bloat etc. Got a few on the radar, but I'll just keep going with the N7000.
I'll hate to put her out to pasture, she's been a good ride.
Click to expand...
Click to collapse
Even though it's really off topic, but I will say I do share your sentiments.
Sent from my GT-N7000
I stuck on flashing r5 kernel, after installation complete, I reboot to recovery...my phone was dead, I need connect odin, go Download mode flash back my kernel,only can make my phone alive back..please help
Running 4.0.4 stock rom with rooted kernel
andyshim1989 said:
I stuck on flashing r5 kernel, after installation complete, I reboot to recovery...my phone was dead, I need connect odin, go Download mode flash back my kernel,only can make my phone alive back..please help
Running 4.0.4 stock rom with rooted kernel
Click to expand...
Click to collapse
This is the wrong place to ask your question. Should've gone to troubleshooting section. Your situation might have been caused by ICS kernel. You should've flashed compatible CWM + franco's safe kernel or philz safe kernel n recovery first before flashing anything else in ICS 4.0.4
Sent from my GT-N7000
andyshim1989 said:
I stuck on flashing r5 kernel, after installation complete, I reboot to recovery...my phone was dead, I need connect odin, go Download mode flash back my kernel,only can make my phone alive back..please help
Running 4.0.4 stock rom with rooted kernel
Click to expand...
Click to collapse
After flashing Raw Kernel r5 then you won't be able to boot into your old ROM, only recovery mode and download mode. I'm guessing you chose the wrong reboot option or you didn't follow the instructions properly (rebooting at the proper times for example).
Nice guide mate. Many thanks for your time giving.
Great
Sent from my GT-N7000 using Tapatalk
@XxPixX
Excellent guide, many thanks for taking time to compile this to help others.
Shalom and best wishes, john
Thanks for your guide..!
In the Omni wiki I read.
TWRP is the only recovery officially supported by Omni.
Is this included in the step by step manual?
Thank you
Now with Dirty Unicorns v7.5 !
Nice guide thanks.
Is it possible to flash after cm11, cm10.2 ? Or I have to change kernel or recovery things ?
Thanks
Envoyé de mon GT-N5110 en utilisant Tapatalk
PdroidAndroid said:
Nice guide thanks.
Is it possible to flash after cm11, cm10.2 ? Or I have to change kernel or recovery things ?
Thanks
Envoyé de mon GT-N5110 en utilisant Tapatalk
Click to expand...
Click to collapse
You already will have a superior recovery. So no need.

Categories

Resources