Database Users

Sailfish for Android devices release!

Hello guys,
I just got an awesome e-mail from Jolla. I think they don't mind posting it here for everyone interested to see, it even mentioned this forum. If anyone feels I'm sharing confidential stuff, please PM me
Here it is:
Dear early adopter of SailfishOS for Android devices.
We're kicking off today by publishing the first Early Adopter Release of SailfishOS (1.0.4.20) for Nexus 4 (mako) to early adopters. Please make sure to read this whole e-mail through.
Later we'll be publishing images for Samsung Galaxy S III LTE (i9305) and we'll be delivering updated images as we go along for each device as hardware support improves. This is just the beginning.
We are also working on the SailfishOS hardware adaptation development kit, which describes how to port SailfishOS to existing CyanogenMod 10.1 devices. Later versions of CM will be supported eventually. We'll publish the HADK in the next few weeks if everything goes well.
This installation image is for early adopters only, meaning we know that some things are not functional or perhaps even broken -- please see release notes below. We think it's worth sharing already now to get all of you properly included in the early stages of the project.
We want to build a community around SailfishOS for Android devices that is based on mutual trust and respect for what we are all doing. Hence -- we ask that whenever you do screenshots, videos, forum or blog posts (and we're happy if you do!) or the like, you emphasise that this is an under-development snapshot and not a final product release.
It is important for Jolla that the correct expectations are set for those who might be users of the final product -- and that they understand what they see is not a released product.
WARNING: Modifying or replacing your device’s software may void your device’s warranty, lead to data loss, hearing loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with this project is responsible for your actions but yourself. Good luck.
NOTE: You will lose your on-device data, so make a proper backup.
To install this release of SailfishOS on a Nexus 4 device:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/android/nexus/images#instructions
b. Download links can be found here: https://developers.google.com/android/nexus/images#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. The file you want to download is cm-10.1.3-mako.zip
b. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the SailfishOS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.4.20-EA1.zip
* Install CyanogenMod 10.1.3 on your Nexus 4
a. Follow the instructions at: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* After flashing the "cm-10.1.3-mako.zip" file, flash the SailfishOS .zip file in the same way ("on top of it")
* Reboot bootloader, SailfishOS should boot and be visible
We can recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
If you want to go back to normal CyanogenMod:
a. Boot into recovery mode
b. Choose "Wipe data / factory reset"
c. Flash cm-10.1.3-mako.zip
d. (to go back to SailfishOS, flash the SailfishOS .zip on top of it)
To SSH into your device via USB (Linux)
1. Enable remote connection in Settings->System->Developer mode
2. Set your USB interface on host machine to IP 192.168.2.2
3. ssh [email protected]
4. Use the password from developer mode to log in
5. Use the 'devel-su' command with the same password in order to gain root
6. To SSH over WLAN, use IP listed in developer mode under "WLAN IP address"
Release notes and Known issues for Early Adopter Release 1 for mako/Nexus 4:
* We have a subtle watermark underneath the UI at all times stating "SailfishOS development software" "This is not production quality". Developer mode is activated at all times.
* Modem and related functionality works, 3G data, SMS but no call audio (comes in next release). There has been no throughout testing of telephony related functionality (roaming, airplane mode, data counters, etc) and any use of this functionality is at your own risk.
* Sensors, Device clock/alarms, Reset device, Bluetooth, USB control + MTP, Bluetooth, WLAN hotspot, Camera (photography, video recording), and video playback is not supported in this release.
* Jolla account / Store is removed from the image due to problems with registering with Jolla infrastructure.
* The image SW is not currently upgradeable, nor is any typically licensed multimedia codecs (MP3, etc), HERE maps, Android application compatibility layer, or word prediction for virtual keyboard preinstalled.
* After returning from suspend, UI may be slow for a moment. It is not possible to double-tap to wake up the device. Power button may fail to wake device at times, check if you are covering the proximity sensor. Powering off device puts it into a state of deep slumber; possible to get out of by holding power button and volume down key with a bit of persistence.
* Fingerterm applications may fail to launch during first attempts.
* FPS drop while scrolling in homescreen due to non-batching when rendering of application icon grid
* Icons/graphics appear unproportionally small in browser toolbar, time select widget, and Settings favourite icons
* Multiboot / multirom is not supported currently
We will all meet in #sailfishos on irc.freenode.net and please use us (thp, alterego, Stskeeps, lbt, sledges) to work together, report any bugs, graphical glitches or missing functionality that you find, which are not included in the release notes above. You can also find the hardware adaptation source code at http://github.com/mer-hybris .
You are also welcome to participate in threads at http://forum.xda-developers.com/nexus-4/general about Nexus 4 and SailfishOS as well as for more general SailfishOS topics at http://forum.xda-developers.com/jolla-sailfish/general
Best regards,
Carsten Munk (Stskeeps) on behalf of the SailfishOS for Android devices team
Chief Research Engineer @ Jolla
Click to expand...
Click to collapse

Daycrawler said:
Hello guys,
I just got an awesome e-mail from Jolla. I think they don't mind posting it here for everyone interested to see, it even mentioned this forum. If anyone feels I'm sharing confidential stuff, please PM me
Here it is:
Click to expand...
Click to collapse
Great, I'll give it a try

Daycrawler said:
Hello guys,
I just got an awesome e-mail from Jolla. I think they don't mind posting it here for everyone interested to see, it even mentioned this forum. If anyone feels I'm sharing confidential stuff, please PM me
Here it is:
Click to expand...
Click to collapse
Can't we just flash CM 10.1 instead of flashing the 4.2.2 factory images?

Zehlek said:
Can't we just flash CM 10.1 instead of flashing the 4.2.2 factory images?
Click to expand...
Click to collapse
no you should't, because the images also contain radios and those are needed that sailfish works properly on the nexus 4

Oli28 said:
no you should't, because the images also contain radios and those are needed that sailfish works properly on the nexus 4
Click to expand...
Click to collapse
I just flashed
1. Older bootloader
2. Older Radio
3. CM 10.1.3
4. Sailfish

Just tweeted by Nemo mobile
You can now try Glacier UI even on #Nexus4 ! Via #sailfishforandroid project and http://t.co/mGaE1KqbAj
Sent from my HTC One using xda app-developers app

I'll try this asap

Tried it.
But somehow the mobile data isn't working for me.
(just flashed JDQ39 bootloader and radio instead oft the whole Firmware)

jedi2001 said:
Tried it.
But somehow the mobile data isn't working for me.
(just flashed JDQ39 bootloader and radio instead oft the whole Firmware)
Click to expand...
Click to collapse
Check the settings , its quite tricky

And where there?
If I enable mobile data in the settings I just geht an error popin on the top. "problems with data connection" vor something similar.

I had no problem with 4.2 radio with T-Mobile in the US. No settings changed.
Sent from my Nexus 4 using Tapatalk

Thats a great news, lets hope thay make it available for the S4 soon.

I finally had some time to look into the problem.
Sailfish had the wrong APN
Edit:
After two hours playing with Sailfish, I can say that the Sailfish feels nice and it seems quite stable.
No comparison to the very buggy Ubuntu.
Once camera and bluetooth works, and we get a chance to at least buy AlienDalvik on their app store, this could become my main OS.

are there mako drivers or config files in the sailfish zip ?
can this sailfish zip be installed on nexus 7 grouper?
or does it has to be build specific for grouper?

frullewulle said:
are there mako drivers or config files in the sailfish zip ?
can this sailfish zip be installed on nexus 7 grouper?
or does it has to be build specific for grouper?
Click to expand...
Click to collapse
I think you can try it safely, it shouldn't brick anything as it's loaded from the kernel. but I think it will not work. They mention some help in porting soon and I'm waiting for that.

Zehlek said:
Can't we just flash CM 10.1 instead of flashing the 4.2.2 factory images?
Click to expand...
Click to collapse
Just flashed cm10.1.3 and SailfishOS from another custom rom 4.4.2...Everythink should work, works. No problem with SMS, GSM data and OS is very smoothly... Perhaps WLAN?
EDIT: After some tests, radio from factory image 4.2.2 is necessary for WLAN and sound

are the updates for this rom going to be nightly or weekly??
and can anyone please pm me when theres an update??
thanks

Are there any update about other nexus device like galaxy nexus? That phone isn't too old for an official support (I think), and there are lots of people like me who want to try that OS on that device
Sent from my Galaxy Nexus using xda app-developers app

No N5 love makes me a sad bunny...
Sent from my Nexus 5 using Tapatalk

setspeed said:
No N5 love makes me a sad bunny...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Same, I would try and force the nexus 4 version to work on the n5, as that is basically how the HADK is going to work, but haven't got time for it yet, I also intend to make an app that copies over SMS and WhatsApp messages between sailfish and android roms, but 1. Don't know if its possible, and 2. No time, due to exam revision.

Galaxy S3 [I9300] - Basics,Best Performance Package - Mod's and ROM's & Kernels

So, I have been using an S3 {yeah S3 , i know old, but duh i just love it } for over 3 years now . I started out as a complete noob, still am, and S3 was the first phone that i started working on. Over the years i have tried many custom ROM's , Kernel's and MOD's and i have tried here to create a List of Best Performing Custom Items over the course of 1 year, with special care for people like me who have just started out in the world of android, So here goes. {in 4 steps} :-
<1> Best "FAIL-SAFE" Method of Rooting/Installing a custom ROM - I know most of the people are afraid of bricking their device's, the first time they root. I have been in that situation and had my phone soft bricked many times while trying out different thing's. So the Most FAIL-SAFE Method that i have come up with is this:-
Many people suggest rooting the devices first and then installing a custom ROM. I have tried to do things a little differently so that the first timers can get comfortable.
A. First thing to do is install CyanogenMod on your specific devices. [without rooting] , The developers at cyanogen have made an application to directly install Cyanogen to your devices from your PC like a regular Software Install. The Link and the Instructions can be found on the official Website - http://get.cm. The process is very simple and easy to do and after the install your device gets automatic root access. The xda thread - http://http://forum.xda-developers.com/android/apps-games/app-cm-app-installer-t2959922 - {you get CM - 11 from this download }
B. Now that your device is has CyanogenMod, you get a rooted device and a custom ROM. But the problem with Cyanogen is that the Custom recovery which it provides has very limited options available. So the next step is to go to Google Play Store and download "TWRP Manager" or "ROM Manager" [i personally use TWRP]. This application will help you to Install the TWRP or CWM recoveries on your Phone. The process is fairly simple, After Installing the App, Choose your Device Model and Version and Let the app do the rest of the work. PS the apps require ROOT access which your phone can provide now.
C. By now if all the steps are performed correctly [very less chance of something going wrong because most of the tings are done automatically] your respective device should have a custom Recovery installed. Next and Most important step is to Create a NANDROID BACKUP [basically an ultimate backup to restore everything]. Go to recovery mode [Home+Volume up + Power button] and select backup, and make a complete backup on your SD card. It's really important to create a Backup before doing anything. This step must not be skipped in any case.
D. Now it's time to let your imagination run wild xD, Download custom ROM's, Kernel's MOD's etc and just copy the zip's to the SD card and install them using the recovery. In case anything goes wrong Just restore from the Backup you made earlier.
[PS: Update your backup's regularly]
<2> Now's the list of My Personal Favorite's which Have Improve the overall Performance of My Phone Greatly. All the ROM's, Kernel's etc have been personally tested by me for over 3 month's for Issues related to Stability, Performance and Bug's . I have tried to put forward the Best package for optimal performance.
1. Recovery [doesn't affect much] - - TWRP Recovery: Personally "Team Win Recovery Project (TWRP)" is my favorite because of it's easy to use touch control's , it's efficiency and Design. I like the cool blue texture theme of TWRP and the speed with which it create's backup and install's new things. The performance of the Phone does no depend upon the Recovery though and you may choose whichever recovery you are comfortable with.
2. ROM - BlissPOP v4.0.3 (CM 12.1 base) : Yes i have chosen this ROM out of the many other i tried. The reasons are very simple, This ROM provides outstanding stability and Performance to the device. There is no bloatware in the ROM and there are simply hundred's of features available for customization. It's compatible with generally all the Kernel's and Mods available for your device and the regular Nightlie's are an added bonus. It's the only ROM based on Lollipop(5.1.1) in which i haven't found any Bug's or stability issues.
Many people told me to try Paranoid ROM but personally i find Paranoid a little buggy, and i found that the PI controls and Halo, due to which the ROM is popular are not of any important use to people like us. They only add a touch of appearance to the device [strictly my view and i mean no offence to any other person ].
3. Kernel - Archie kernel for Galaxy S3 - http://forum.xda-developers.com/galaxy-s3/development/kernel-archikernel-v1-0-power-hands-t2785337
4. MOD's -
A. Audio Engine - Ac!d Audio - http://http://forum.xda-developers.com/galaxy-s3/development/mod-acid-audio-engine-v5-0-samsung-t2002197
Viper4Android -http://forum.xda-developers.com/showthread.php?t=2191223
6. Root Applications -
A. Titanium Backup:
You can backup, restore, freeze (with Pro) your apps + data + Market links. This includes all protected apps & system apps, plus external data on your SD card. You can do 0-click batch & scheduled backups. Backups will operate without closing any apps (with Pro). You can move any app (or app data) to/from the SD card. Available on Google Play
B. AdAway for Android [built-in app in BlissPop ROM]:
to block ads on your Android device this app is not avalibale on the playstore but you can still install it from this link
C. Greenify:
Is a good application to make your Android device more faster, by hibernating the background apps that you don't use. this application is completely free. Available on Google Play
These are the only Apps which i find useful in the long run as i have to use them constantly. Rest application's are used from time to time but not regularly. So this is My List, i'd be glad if anyone want's to add to it ^.^
I'd Like to Thanks the Amazing People who have Made the above Programs to make our Phone More performance and Appearance efficient. ------> CyanogenMod community, BlissPOP community, xda developers, Jeeko, JustArchie, amarullz, the Ac!d Audio Engine Team,zhuhang(Viper Mod), TWRP team.
Give a Thanks if u were helped by the post
================================================================================================================
Intense Testing Period -> Over 8 months [tried the new Lollipop ROMS's , over 20 kernels, Latest Android M ROM's , some personal opinions
================================================================================================================
Firstly sorry, for the delayed updates, i have been a little busy trying to develop my own ROM (surprise! surprise!, not for S3 unfortunately thought as i can never come close to the current ROM wiz's ), now in the second edition , I have tried to utilize my knowledge over 8 months to put up a new more enhanced guide and have also put up common and uncommon bugs which I experienced along the way and have provider the working solutions for them. Also I am extremely sorry for all those broken links and not working Mods, i'll try to keep my list precise, sharp and accurate this time.
1. Alternate method to Root (super easy, risk free, takes at maximum 5 minutes) - {for windows running PC, stock ROM or any other custom ROM can be used}
So, I would still recommend using my method 1 in order to initially root your device, install a custom ROM and a Recovery as i know the fear and anxiety or every new user trying to root his phone for the first time.
Now for a little more experienced users (quickie guide) [for I9300 version] who do not want to spend a lifetime to just get their devices rooted -
(a) Download the Chainfire's AutoRoot file here and place this file on your PC.
(b) Download Odin (latest version) on your PC here and unzip the file and start odin.
(c) Power down the device, then reboot in Download Mode [ press Power button + Home Button + Volume Down Key] and press volume up key at the caution screen. (little Hint: mostly the device reboots itself when you do not press the 3 buttons at the same time, to counter this press the volume up button and the home button first and hold them and then press the power button until you see the Galaxy S3 logo)
(d) Now connect your device to your PC using a sturdy USB cable. After doing this 2 outcomes are possible:-
~1. Your device is identified by Odin and a faint blue colour is shown on one of the top tabs indicating the port through which your device is connected. In this case proceed to step (e).
~2. If your device is not recognized by odin ie no blue colour, then the drivers of your device might not be installed on your PC. To tackle this download the Driver Suite from Samsung here and run the program. If done correctly when you next connect your device the drivers should get installed and odin should recognize your device.
(e) Click the "AP" button on odin and select the "Chainfire's v-xxx .mad5.tar " file which you downloaded above, odin will then take some time to check the file and when it's ready press start. CAUTION - do not change Odin's settings and assure that Reset Runtime and Auto Reboot are selected, never select re-partition on the odin interface.
(f) After the installation is complete your device should reboot automatically and you should have SuperSU installed (indiacting 99.99% times that your device rooted successfully ).
(g) If you want you can then install a custom recovery using the method indicated in my "method 1" [above].
-feel free to message me for any doubts-
Here are some of my new recommendations based on personal experiences:-
2. ROM's - I will try to divide this section based on firstly Android System and then further based on Stability, Features, Performance. Further i will be adding 2 ROM's for Android M . [i will not be naming ROMS which have a touchWiz interface]
(A) Android Lollipop and Below
Stability - Official CyanogenMOD 11.x [kitkat 4.1.1] - Zero Doubt, this one is the most stable thing out there for S3, old, yes but well you can do anything you want with this ROM and it will not seriously bug out on you when you need it. If someone does not mind going for an older version of android and needs epic stability, just go for it.
Features - BlissPop v3.0.x [CM 12.1 base][ Lollipop 5.1.1] - This ROM is filled with features, you name it, this ROM has it, PI controls, Built-in apps including AdAway, Kernel Modifier, Greenify, SuperSU etc, seamlessly integrated into the build environment. Each and every feature of this ROM is customizable, every font, colour and animation. Simply put, for someone who needs features and customizations go for this one. On the other hand, this ROM is less stable (crashes quite often ) and provides a slightly laggy gaming experience. No bloatwares in this ROM.
Performance - ArchiDroid [CM12.1 base][Lollipop 5.1.1] - Performance, Performance and more performance, all the technical aspects of your device will be enhanced and although the customization features are minimal but this ROM turns your device into a Performance Beast. All the gamers and performance lovers, what are you waiting for
Android 6.x.y Marshmallow
1. RESSURRECTION REMIX M - Fast, Durable, Amazing performance. Fell in love with this one when i used it, and this is my current ROM, no bugs so far and have been using it for over 1 month. Immensely Customizable, no lag during gaming, an amazing upgrade from Lollipop.
2. NamelessROM 3.0 - Feature Loaded, Minimal, good Looks and customization features and of course the ever caring support team of Nameless makes this a go to ROM.
>>> A bit more studying will be required before i finally divide the Android M ROMS's based on their features, performance and stability. Will be posting the results as soon as i am finished.
3. Kernels - AGNi pureCM and Boeffla-Kernel (26-03-2016) , tied, tested and proved that they are the best on very benchmark or performance test, although battery usage is better balanced on AGNi whereas Boeffla is more inclined towards performance.
You can find the Links to all the above ROM's and Kernels and many more in this thread - here
PS - Please Post your bugs in the thread and i will do my best to try and solve them out with an easy and sure solution
Cheers!

Awesome rundown for a new user like me. I've just got an S3 after using a Nexus S for 3 years. The S3 feels like such a beast compared to it!
I want to root and put a custom ROM on my device this weekend. I currently use cm11 on my Nexus S but it's a bit slow (which is understandable considering the hardware) so I can't wait to try it on the S3. My priority is long term stability ( I don't like flashing the emperors new clothes every 5 minutes). I just want to flash a ROM and forget it.
Have you tried any slimroms on the S3?
Sent from my Nexus S using XDA Free mobile app

[email protected][email protected] said:
A. First thing to do is install CyanogenMod on your specific devices. [without rooting] , The developers at cyanogen have made an application to directly install Cyanogen to your devices from your PC like a regular Software Install. The Link and the Instructions can be found on the official Website - http://get.cm. The process is very simple and easy to do and after the install your device gets automatic root access. The xda thread - http://http://forum.xda-developers.com/android/apps-games/app-cm-app-installer-t2959922 - {you get CM - 11 from this download }
Click to expand...
Click to collapse
Hi.
Can you just go over this again. Do I use my phone to download an installer from http://get.cm, install the apk then I will have root?
edit - damn I don't use WIndows, only Ubuntu. I can't use it.
Cheers.

Hi warren
Yes I have used slimrom too on the s3. Its good but as u are looking for stability I would suggest go for cyanogen because in my experience cyanogen shells out a better performance as compared to slimrom. My gaming experience was a little reduced in slimrom and I experienced a little lag but no such issue in cyanogen.
Secondly if you use ubunto I would suggest going for a virtual box to install windows and then the cyanogen application as it's the safest way to install a ROM.
U have to got to " get.cm " from both your phone and PC
On PC a windows installerbwoll be downloaded and on the phone an APK will be downloaded first install the apk the install the windows program and then continue as given in the installer setup.
Else mate, I wud say first download the stock ROM of s3 as a backup and the continue to root in the traditional way .
Any problem just ask me
Cheers

Hi.
I was thinking the same. CM11 all the way! I used Slimrom on my Nexus S but it was very very slow. I almost smashed my phone in frustration.
Nice tip about using a virtual machine to install cm. I will have a think about that. At the moment I have found a very good guide that involves using Heimdall on Ubuntu and Chainfire,so i will probably go for that method.
I am definitely going to try arter97 kernel. It looks immense. It has boeffla sound which I am looking forward to trying.
Sent from my GT-I9300 using XDA Free mobile app

A little Confused....???
[email protected][email protected] said:
Hi warren
Yes I have used slimrom too on the s3. Its good but as u are looking for stability I would suggest go for cyanogen because in my experience cyanogen shells out a better performance as compared to slimrom. My gaming experience was a little reduced in slimrom and I experienced a little lag but no such issue in cyanogen.
Secondly if you use ubunto I would suggest going for a virtual box to install windows and then the cyanogen application as it's the safest way to install a ROM.
U have to got to " get.cm " from both your phone and PC
On PC a windows installerbwoll be downloaded and on the phone an APK will be downloaded first install the apk the install the windows program and then continue as given in the installer setup.
Else mate, I wud say first download the stock ROM of s3 as a backup and the continue to root in the traditional way .
Any problem just ask me
Cheers
Click to expand...
Click to collapse
My understanding is that unless you rooted your S3 quite a while ago, pre 4.4.2, you can't add custom ROMs. The late-rooters would have a locked bootloader and would be severely limited on what mods are possible. Is my understanding incorrect? Thanks!

Oh my I hope this isn't the case.
Is this not just on Verizon or all s3's?
Sent from my Nexus S using XDA Free mobile app

Sorry to confuse things. I believe the locked bootloaders only apply to those unlucky enough to have Verizon phones.

Yay not me then! NP.
P.S. Verizon suck!

Yes mate unfortunately Verizon version of S3 has a locked boot loader and it does not allow the user to install a new recovery. I would suggest using Odin to auto root your phone which in turn also unlocks the boot loader. I can make a step by step guide for Verizon version if anyone requires it. Personally I prefer the international version though. It has more optimized system functions.
Tell me if u want a Verizon guide

$$-
Thanks for your reply. Sure, if you have something that will allow me to unlock my Verizon Galaxy S3 bootloader, that would be great! Is that what your verizon instructions will allow me to do? I've never heard of any way of doing this, so that would be great if it works! Btw, I am running 4.4.2. Thanks again!

What about /EFS backup and locked boot loader?
I have been an old time user of android starting with sony xperia X3. I had a bad luck with that phone. When sony updated android from 1.6 to 2.2 , the phone went into a boot loop and finally got dead. I sold the battery and screen separately to make some cheap buck!!
After that experience, I have been reading a lot for rooting and there seems to be lot of info on that.
My phone model is Samsung S3 GT-I9300 international version. I am still on the stock Rom with 4.3 on it.
I tried with kingroot app and it bricked the phone and was able to recover with kies.
What I want to know is that, you have mentioned option A, do I need to make any backups (not the contacts and personal stuff which I am not worried when I start playing with the phone) of EFS partition?
Will I be able to restore to old stock ROM just by using ODIN and the firmware which is available from the market?
What I need to know is , will I need any specific data (IMEI or EFS) unique from my phone?

Hi [email protected][email protected]
I used Heimdall in Ubuntu and I managed to root and put SuperSU on my phone ! I also put TWRP recovery on as well and then did a backup of my stock ROM. I am now ready for some ROM flashing!
I am unsure whether to go for CM11 or something like Tamasek's CM12.1 ROM. Have you used Tamasek's ROM before? Thinking about it for the first flash I think I will use CM11 snapshot and arter97 kernel. Then I will nandroid backup and then I have a stable ROM/kernel combo to fall back on in the future.
Looking at arter97 kernel can you tell me about f2fs support and how I get it? Does it speed up certain parts of the memory? Is it worth flashing? Also, the kernel mentions touch wake. Is this available for the S3?
Cheers.

I can't believe it I bust my sim slot! I cut my old sim card with a tool cutter and it looked good but it was a little tight going into the slot and I pulled it out and that’s when I must of bent some pins. I'm gutted :crying::crying:
Thankfully a replacement is only £3 and swapping it over looks a doddle :fingers-crossed:
Looks like I will have to wait a week until I can have a proper play. I did download BlissPop ROM and I like it. Been playing around with that all day but Its still not a phone until I get my sim in it.
You live and learn

mathew_p_a said:
I have been an old time user of android starting with sony xperia X3. I had a bad luck with that phone. When sony updated android from 1.6 to 2.2 , the phone went into a boot loop and finally got dead. I sold the battery and screen separately to make some cheap buck!!
After that experience, I have been reading a lot for rooting and there seems to be lot of info on that.
My phone model is Samsung S3 GT-I9300 international version. I am still on the stock Rom with 4.3 on it.
I tried with kingroot app and it bricked the phone and was able to recover with kies.
What I want to know is that, you have mentioned option A, do I need to make any backups (not the contacts and personal stuff which I am not worried when I start playing with the phone) of EFS partition?
Will I be able to restore to old stock ROM just by using ODIN and the firmware which is available from the market?
What I need to know is , will I need any specific data (IMEI or EFS) unique from my phone?
Click to expand...
Click to collapse
Hi Mate,
First of all, don't worry at all about the bricking thing, with the option A that i have mentioned, it's 99.99% success, i haven't found a single person yet for whom the method didn't work.
Secondly i would suggest u take the backup of your phone contacts in a vCard format using Kies first so that u don't loose them. And copy all your Personal things on your PC (pics, videos etc).
Thirdly you do not need to make a separate disk partition for the method to work, the CM installed will do it for you. Also if u have an International i9300 version u need not do a single thing yourself. Just start the setup and sit back and relax. Just follow my method to the letter and you can have a great custom ROM with root access in no time.
MOST Importantly - You can go to stock firmware of samsung but this time you will have to use odin instead of Kies to do that. You won't be able to use Kies once you have installed a custom ROM, but trust me that's a small price to pay for a very efficient ROM.
You do not need to know the IMEI or EFS number though i would suggest u still make a note of it somewhere in case ur phone is lost. Prevention is always better Message me if u have any queries. Cheers!

Warren_Orange said:
Hi [email protected][email protected]
I used Heimdall in Ubuntu and I managed to root and put SuperSU on my phone ! I also put TWRP recovery on as well and then did a backup of my stock ROM. I am now ready for some ROM flashing!
I am unsure whether to go for CM11 or something like Tamasek's CM12.1 ROM. Have you used Tamasek's ROM before? Thinking about it for the first flash I think I will use CM11 snapshot and arter97 kernel. Then I will nandroid backup and then I have a stable ROM/kernel combo to fall back on in the future.
Looking at arter97 kernel can you tell me about f2fs support and how I get it? Does it speed up certain parts of the memory? Is it worth flashing? Also, the kernel mentions touch wake. Is this available for the S3?
Cheers.
Click to expand...
Click to collapse
Hello Warren,
Good to hear that you are having fun with your new phone.
Firstly yes i have used Tamasek's/JustArchie's CM12.1 ROM and it's quite good to be honest. So first i'll talk about it then i'll come to the kernel.
So 12.1 yes, the most noticeable change android L 5.1, all good, nice appearance, but i would say just think again for a bit.
A comparison between the two is a mammoth task but i'll try to brief it for you and tell you why i like the CM11 better even though it has android KK. It's upto to you though what you choose to flash. i even have a nice tip for you in the end
So first let's see the CM12.1 -
Quite stable, i used it for like a month or so for testing and got a good result. The performance was at par with the rest of the ROM available for S3. The Graphics, Audio and Processing quality is also good and is suitable for light use. Here's the catch though, Firstly the Gaaps, many gaaps available Android L are not compatible with the unofficial 12.1 so u'll have to look around to find the correct set of Gaaps.
Secondly i personally find that the CM 11 has a much neat finish as compared to CM 12.1, i don't really care about the android version as for me if i can have all the features of android L in a more stable KitKat ROM i don't usually upgrade my ROM. THe reasons are very simple
Firstly it's Unofficial, No Nightlies, rare updates. Also the unofficial ROM is alive only till the Developer is still working on it. Once he stops his work it's a very slim chance that you can get your bugs fixed.
As for the Official one, there are thousands of forums on Solutions to various Bugs and Numerous customization options. We can't really know whether the unofficial 12.1 supports all the things available for the official ROM.
Based on Performance both the ROMS perform equally, there's a camera Bug in the 12.1 which can be a problem sometimes but rest is all good.
On a personal side [not really of importance] i like the Calculator of the CM 11 better than CM 12.1.
Now the Kernel - arter97 is simply amazing, The most noticeable changes are - 1800 GHz overclocking [yeah from 1400 to 1800 BOOM!],
the Knock feature - Tap the screen to unlock the phone, no need to use any buttons, Battery Tweaks etc.
Also it used a custom engine to allocate the Files to various partitions to the memory so yeah it saves space plus we can even Increase our RAM a bit by using the Internal Memory of the Phone.
I am a Hardcore Gamer and use my phone to the limit sometimes [ Playing Asphalt 8, Real Racing, GTA: San-Andreas, FIFA 15 and WWE Immortals can take it's toll on the phone.] these games require very high end phones but with this kernel they all run liquid smooth on my phone without even a slightest bit of lag. So yeah i would surely recommend arter97's Kernel. PLUS u get Boeffla Audio Engine which is an added BOnuS
Touch WIZ -- Not Necessary, I flashed it using TWRP and it worked Just fine.
f2f - f2f has better memory allotments and it's pre configured, we usually don't have to enable it, it's much better than extD though.
TIP - arter97 supports dual Booting so you can even enjoy cm12.1 and cm 11 at the same tine [Dual Booting i'll cover in the next post if you have a problem doing it ]
-----> Also U can use the Siyah Kernal, which work's just fine and even has an amazing Boot Image but now as much features as arter's.

straykat said:
$$-
Thanks for your reply. Sure, if you have something that will allow me to unlock my Verizon Galaxy S3 bootloader, that would be great! Is that what your verizon instructions will allow me to do? I've never heard of any way of doing this, so that would be great if it works! Btw, I am running 4.4.2. Thanks again!
Click to expand...
Click to collapse
Hello,
well i have two methods for Verizon Phones, One i have tried myself the other one was tested by one of my friends,
For the First one -
Using Odin Use the Chainfire's Auto Root Application to give root access to your phone. https://autoroot.chainfire.eu/ This application in turn also unlocks the bootloader and hence you can easily install further ROM's. Check the Xda general Samsung forum to learn how to use Odin if u don't know , or just message me
Second - This Method requires Root Access on you r Phone. THere's an app on Google Play named "EZ Unlock" to unlock the bootloader , I think this app can help you out but i haven't tried it myself so i can't really comment. But looking at the reviews i would say that this app really works. ----> http://www.mediafire.com/download/qozzz1p43kxzs3z/EZ-Unlock14.apk
Here's a custom Recovery that can help too - http://forum.xda-developers.com/showthread.php?t=2797314
Cheers!

Hi..I did a search but i am completely confused and bewildered by the vast amount of different posts and opinions in threads..so i apologise if this has broken any rules.
Basically i have a stock s3 i9300 (uk) with original samsung jellybean 4.3 rom,I am getting a bit sick of it now (and the bloat) and i am looking to move on to something more appealing..I have already rooted and installed Rom Manager and CWM..i was wondering what the "Best Simplistic dark themed (small footprint) rom" to go for As i want minimal installed size to make the most of my 16gb memory,i dont mind which android version as long as the process is easy and the battery life is among the best available..And of course it is as stable as my current Samsung android rom..
i would really appreciate any valued veteran guidance..many thanks.

[email protected][email protected] said:
Hello,
well i have two methods for Verizon Phones, One i have tried myself the other one was tested by one of my friends,
For the First one -
Using Odin Use the Chainfire's Auto Root Application to give root access to your phone. https://autoroot.chainfire.eu/ This application in turn also unlocks the bootloader and hence you can easily install further ROM's. Check the Xda general Samsung forum to learn how to use Odin if u don't know , or just message me
Second - This Method requires Root Access on you r Phone. THere's an app on Google Play named "EZ Unlock" to unlock the bootloader , I think this app can help you out but i haven't tried it myself so i can't really comment. But looking at the reviews i would say that this app really works. ----> http://www.mediafire.com/download/qozzz1p43kxzs3z/EZ-Unlock14.apk
Here's a custom Recovery that can help too - http://forum.xda-developers.com/showthread.php?t=2797314
Cheers!
Click to expand...
Click to collapse
[email protected]
Thanks for the info! I looked on a Chainfire thread here on xda to see if others have done what I would be attempting to do with my Verizon S3, but I don't see anyone else saying they've used this method to unlock their bootloader & install roms. By chance, do you know any place on this forum or any others that talk about peoples' successes using this method on a Verizon S3? I'm a little nervous about attempting this method without knowing that lots of other people have done so successfully.... Thanks for your help & your understanding of my feelings on this.

Broken Link
Your "Mods" links are broken.

[ROM][FirefoxOS][DISCUSSION] NEW for Z3C!!!

hi guys, I see there are still no threads for FirefoxOS that has been just released by FXP for our device too (z3c) so I'm creating one
this thread just to discuss about it!
INFO: http://fxpblog.co/2015/09/26/firefox-os-releases-by-fxp.html
DOWNLOADS: http://fxpblog.co/firefox/nightly/
INSTALLATION:
- You must have a UNLOCKED BL
- Extract all system images from the ARIES zip you downloaded
- Connect phone to PC in fastboot mode and then:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
downloading the zip for aries right now! will see how it goes
in the meantime, I have already some questions I would like to reply myself after testing the new OS or if somebody already knows the answers, please let me know!
1. rootable? DON'T THINK SO
2. recovery can be installed or to go back to stock will have to flash FTF via flashtool? SEEMS NO RECOVERY AT ALL?!
3. camera present/working? if so, without fish eye bug? CAMERA NOT WORKING AT ALL
4. gapps are needed? in firefox OS there is no Play Store right? NO GAPS, THERE IS MOZILLA MARKETPLACE WITH FEW STUFF STILL OF COURSE
Please contribute guys in answering all the above questions!
THANKS
All credits to Mozilla and FXP ( @freexperia ) teams of course!
few screenshots:
https://www.dropbox.com/s/2ut81qaqjgu3fqo/2015-10-01-11-14-23.png?dl=0
https://www.dropbox.com/s/vvrx7153ql6xjzf/2015-10-01-11-14-33.png?dl=0
few impressions so far:
the bad:
- no camera
- no dt2w
- no extsd support (where I have all my stuff!)
the good:
- seems very nice and promising
- app ops
- nice animations
will keep updating!

Really interested to try this once it's fully functional. Thanks for the heads up!

moly82 said:
- I'm pretty sure you must have a UNLOCKED BL
Click to expand...
Click to collapse
Unlocked bootloader for sure, since you must flash boot.img
Our device is ARIES, if someone doesn't know yet
Testing today...

me too just unlocked the BL!
EDIT: just booted inside FirefoxOS for my first time

things I noticed so far:
see OP

First impressions:
-only English language.. mmmhhh.. and the keyboard is only in english
-you can import your contacts also from gmail... ok.. that's good
-there's a tutorial at the beginning that explains how it works :victory:
-camera just doesn't work (the camera is in use by another app) !!??!!
-some popular apps ready to install... ok, fine!
-to take screenshots you have to press home+power... but I can't get it :crying:
-settings menu is like a hybrid between android and ios
-all the gestures work properly and are different from android, but they're friendly :good:
-the phone is getting very hot now
-arrrgghhh.... force close... the phone rebooted automatically :crying:

yes for sure not ready for daily driver, but seems very nice
for screenshots I just used android normal gesture (power + vol down)
no recovery right? will have to flash FTF to go back to stock?
phone is not hot at all here so far

Problem with camera is in HAL. Logcat... logcat.
In AOSP builds there is no camera, this is the cause.

Seems problem has been solved. Waiting for new build from fxp team then
https://t.co/XGZ6c75N0X

it seems very very basic and not ready for daily use but well better than nothing..! let's see

xperia z3c fxos
right now the bug for the camera on the lollipop build is being worked on, as far as i can find in our bug reports the kk build camera should be working or it would be under QA-blocker. Also for some of the problems you are having such as only english when building make sure to put PRODUCTION=1 it will make it so it flashes all of the languages, that just has to do with not setting the right build variables.
Fxos-QA contributor rep
Sorry i would give you links but i am a new user on this site so i cant...

jamie_fxos said:
right now the bug for the camera on the lollipop build is being worked on, as far as i can find in our bug reports the kk build camera should be working or it would be under QA-blocker. Also for some of the problems you are having such as only english when building make sure to put PRODUCTION=1 it will make it so it flashes all of the languages, that just has to do with not setting the right build variables.
Fxos-QA contributor rep
Sorry i would give you links but i am a new user on this site so i cant...
Click to expand...
Click to collapse
not sure to understand correctly, you mean there is a firefoxos version based on kk for z3c with working camera? where?
because it seems I can find only the lp build in fxp site... thanks! :silly:

moly82 said:
not sure to understand correctly, you mean there is a firefoxos version based on kk for z3c with working camera? where?
because it seems I can find only the lp build in fxp site... thanks! :silly:
Click to expand...
Click to collapse
i just double checked with of the devs, The aires device, you can build the kk version which does have a working camera, you just have to compile it yourself. The lp build currently available on task cluster does not have the working camera, in all honesty the lp kernal version is not fully complete yet, right now the camera is one of those parts that are not fully complete. if you want to take a look the bug number is 1163557 you have to go to bugzilla.mozilla.org it might help explain the situation. right now lp is experimental.
firefox os QA
mozilla rep
Jamie Charlton

thanks mate, will do! and thanks also for the info, it is nice someone from firefoxos project directly is looking around here and share info with us!
unfortunately i'm not skilled enough for building myself, so can just wait for fxp team to build them for us.
afaik devs are working on updated/fixed camera blobs for lp as we speak, so we could have a decent camera available for aosp soon, in that case hope it will land in firefox os too
really looking forward for a usable build of firefoxos for our device, it seems a very nice project... i like firefox, i like opensource, i don't like google at all recently... so hope to find in fxos soon a great alternative! :good: :fingers-crossed:

moly82 said:
thanks mate, will do! and thanks also for the info, it is nice someone from firefoxos project directly is looking around here and share info with us!
unfortunately i'm not skilled enough for building myself, so can just wait for fxp team to build them for us.
afaik devs are working on updated/fixed camera blobs for lp as we speak, so we could have a decent camera available for aosp soon, in that case hope it will land in firefox os too
ht
really looking forward for a usable build of firefoxos for our device, it seems a very nice project... i like firefox, i like opensource, i don't like google at all recently... so hope to find in fxos soon a great alternative! :good: :fingers-crossed:
Click to expand...
Click to collapse
come end of next week i might be able to get you a kk build, i cant say for 100% due to moz is giving me mine next week. If it comes with a KK kernal on it i can see if I can make you one, i dont think it is under nda for the blobs for kk, im not sure 100% though. i just know for the flame device im not allowed to give out builds that have not gone through approval from t2mobile as distributable.

moly82 said:
1. rootable? DON'T THINK SO
Click to expand...
Click to collapse
Yes. rootable.

jamie_fxos said:
come end of next week i might be able to get you a kk build, i cant say for 100% due to moz is giving me mine next week. If it comes with a KK kernal on it i can see if I can make you one, i dont think it is under nda for the blobs for kk, im not sure 100% though. i just know for the flame device im not allowed to give out builds that have not gone through approval from t2mobile as distributable.
Click to expand...
Click to collapse
thanks mate you rock!
will see so, btw no need to hurry for me, as I am taking my z3c to assitance today or tomorrow (broken magnetic port :crying: ) and dunno when I'll see it again... :silly:

moly82 said:
thanks mate you rock!
will see so, btw no need to hurry for me, as I am taking my z3c to assitance today or tomorrow (broken magnetic port :crying: ) and dunno when I'll see it again... :silly:
Click to expand...
Click to collapse
By the time you get it back i hope that i will already have a working build for you.
Also people, if the base image you are using is gotten from mozilla its a 99% chance its rooted, they are left unlocked for testing and development reasons, the only time they are locked usually is when you are getting them from the phone manufacturer also know as a production build, which we do not make.
Mozilla rep
Firefox OS QA
Jamie Charlton

Okay i have looked into it, the only way i can make you a base image is if it is blib free so you would have to get the blobs from Sony. The blobs are currently under nda so there is no way i can share them without getting in trouble. The only way it seems you could get the kk build with a working camera is if you flash back to android and then get the blobs from the device and then from there you would have to add them to the blob free base image.

The project got already discontinued by Mozilla because the not given chance to get close to Android, iOS or WIP
Maybe with a hardboot kernel it could be saved as a stable, second OS with Multirom...

[Discussion] SM T819 - Lineage OS - A possible starting point!

I have been waiting quite some time for a custom rom for SM T819 but I haven't see much progress in this. I looked for a device with similar specs for our device and came across this device which already has a Lineage OS build available. Its practically the same device but with a different screen size.
LeEco Le 2 Specs: http://www.gsmarena.com/leeco_le_2-8053.php
LeEco Le 2 Lineage OS Github Repo: https://github.com/LineageOS/android_device_leeco_s2
It will be a good starting point as I think for getting a custom rom for this device with a great potential. I have read that having spec devices is a great start to porting a ROM from one device to another without specifically building it from the source. However it includes a few build prop tweaks and changing few lines on kernel which I have no technical expertise.
Looking forward for your thoughts.

It's true, personally I don't have this tab but I had experience with a Tab I used which was similar in specs with S4 Mini ..
You'll get bugs though and you can base device tree from the Leeco Phone to build ROMs

Anything new here?
Seems like @tuxing built a modified T813 LOS build for himself, but of course no LTE in there. https://forum.xda-developers.com/showpost.php?p=73992901&postcount=552

i really hate the lack of support for LTE Tablets :/

Hi guys, I don't know if i am on topic but 'cause of this lack of ROMs for the T819, can I install the one for the T813? I know there is no LTE, but if I wanna try the ROM can I install it or it is incompatible with the T819?

kinglolloman said:
Hi guys, I don't know if i am on topic but 'cause of this lack of ROMs for the T819, can I install the one for the T813? I know there is no LTE, but if I wanna try the ROM can I install it or it is incompatible with the T819?
Click to expand...
Click to collapse
Not that easy, but I had a nice chat session with @LuK1337 and he explained me how to get things built and boot on T819: https://forum.xda-developers.com/tab-s2/general/guide-build-lineageos-15-1-t819-t3721477
It's not that difficult as I thought. @LuK1337 told me it's simple and even I managed to get it working.

Building my own Kernel for Android 4.4.4 on my note 3 (The journey)

Hello XDA community,
After months of struggling im in desperate need of your help.
What is my goal?
To compile our own kernel so we can mess around with Qualcomm's trustzone.
Where did it all start?
It all started a few months ago back in November 2021 when me and a friend read a blog about a Trustzone exploit in Qualcomm's MSM8974 processor. (link to the blog)
Big noobs as we where, we where getting hyped an bought ourselves a Samsung Galaxy Note 3 with a MSM8974 processor. After messing around with the device we learned more and more about android and the workings of the software. We first started to root the phone and play around with ADB. After that we found that we can use Frida aswell. But all of it didn't lead to the result we wanted. So we started to dig deeper in to the write-up of the blog. We soon came to the conclusion that we where not even close to doing the right thing.
What happend next?
After we came to the conclusion that ADB and Frida is not enough we understood we need to build our own kernel for this exploit to work. So we do what we always do and that was start googling and watch YouTube. By doing that we found 2 different kernels:
Lineage 18.1
SM-N9005_EUR_LL_Opensource
We where over the moon because inside the folders we found the the files that need to be replaced for the exploit to work. So we replaced the files and try to compile the kernel by using this YouTube tutorial. Everything seemed to go well, we made the
Code:
make msm8974_sec_defconfig
and we run
Code:
make menuconfig
so far so good. the last and final step should be to run
Code:
make
to compile the kernel. And that is where it went wrong an ran in to a error.
Then what?
Then we started to compare the original files with the modified files and we found out that it wasn't just a few modifications in the code but the code was different. So we did what we always do, go back to the source. So back at the blog we thought maybe its because they modified a Nexus 5 at android 4.4.4.
Now what?
Now im trying to find the source of a android 4.4.4 kernel of msm8974 so we can compare those files to the modified files. So if anyone has useful info or knows where to find a kernel for android 4.4.4 for a Samsung Galaxy Note 3 (SM-N9005).
TLDR;
Im looking for a source of android 4.4.4. for a Samsung Galaxy Note 3 (SM-N9005) (hlte)

Well, unfortunately today almost no one uses android 4.4.4. even that have the exact same device, I am using Android 11 on my phone.
I recommend not wasting your time on a kernel for Android 4.4.4. And if you really want to make a kernel for this device I need one for Android 10 and above.
Also I think making a kernel for AOSPs like LineageOS or HavocOS or crDroid ETC is much easier.

A.M.2.K.M said:
Well, unfortunately today almost no one uses android 4.4.4. even that have the exact same device, I am using Android 11 on my phone.
I recommend not wasting your time on a kernel for Android 4.4.4. And if you really want to make a kernel for this device I need one for Android 10 and above.
Also I think making a kernel for AOSPs like LineageOS or HavocOS or crDroid ETC is much easier.
Click to expand...
Click to collapse
Thanks for your response I will look in to it. not sure if it will be easier because the files that needed to be changed are:
arch/arm/mach-msm/scm.c
arch/arm/mach-msm/include/mach/scm.h
drivers/misc/qseecom.c

SwAgLaNdeR said:
Thanks for your response I will look in to it. not sure if it will be easier because the files that needed to be changed are:
arch/arm/mach-msm/scm.c
arch/arm/mach-msm/include/mach/scm.h
drivers/misc/qseecom.c
Click to expand...
Click to collapse
Well, I don't know much about kernels.
I said it's easier because I thought it's a pure and raw operating system. But now according to your post it turns out it's not easier.

Plus almost no developers left for this now very old model .