I have a samsung focus I look threw the forums can i cant find one for os version 7.10.7720.68, I want a rom that has multitasking if at all possible and custom text tones
How to Root a Samsung Focus Windows Phone
the_professor. said:
I have a samsung focus I look threw the forums can i cant find one for os version 7.10.7720.68, I want a rom that has multitasking if at all possible and custom text tones
Click to expand...
Click to collapse
First off, I am not the creator of any of the resources listed below. All thanks should go towards: Dark Forces Team, WindowsPhoneHacker, and the many others who created these tools. Be sure to thank everyone whose tool/website/ROM you used by buying them a drink. Also, I am not responsible for any damage/bricking/etc that may occur as you attempt to modify your phone.
To address the the absence of OS version 7.10.7720.68, I would like to note that OS version 7.10.7720.68 is the original Mango update provided by Microsoft. Since then, Microsoft has continually updated the OS with minor tweaks (think: service packs) for Windows Phone. Though Samsung (or AT&T or whoever) has not provided these minor updates OTA, ROM developers for the Samsung Focus can bake them into their ROMs. Thus, any ROM with a version number higher than 7720.68 will contain all of the features you request (and more). More information as to the features added/fixed in the OS updates are given at the following link.
(link 1)windowsphone.com/en-us/how-to/wp7/basics/update-history
Now, the easiest place to start the rooting process is by visiting WindowsPhoneHacker's YouTube channel. There is a tutorial available (see the following link) that walks you through the whole process. I strongly suggest you watch the video several times to get a good idea as to the process required. Be sure to like the YouTube video if you find it helpful (trust me, you will).
(link 2)youtu.be/0dSTahZY4mI
I also suggest reading the more detailed information provide by WindowsPhoneHacker (see link below). The link takes you to the "Jailbreak" portion of the website which gives useful information on how to root and install custom ROMs. Read the source and the referenced sources three times or more before you even think about rooting your device.
(link 3)windowsphonehacker.com/articles/the_complete_guide_to_jailbreaking_windows_phone_7_and_7.5-09-24-11
At this point, you should be ready to root. Give it a shot. Be patient, stay calm, and good luck!
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.
Today I wanted to talk about porting current versions of TouchWiz from one device to another. This will be focused primarily on the Sprint network capability since that is my current carrier. But these same basic steps will apply for all porting of TouchWiz.
I know several people have ported roms but I first want to point out one important fact. There is ABSOLUTELY no "guide" that can help you port TouchWiz roms successfully. Period. Any "guide" thread that you may find is completely useless and is isn't even close to touching on the key components of today's porting methods. So don't waste your time reading guides because they are very outdated and irrelevant today.
First things first... When deciding to port a Samsung Rom you need to understand that there are going to be different chipsets for the different device models used in other parts of the world. With this in mind you need to choose software that was originally designed for the same similar cpu whether it be Exynos or Qualcomm. This makes a huge difference when it comes to cpu configs that will best support your device's cpu. If you try to port an Exynos rom to work on a Qualcomm device then expect to have to do a lot more work in framework, etc.
GSM vs CDMA is another very important part of the porting process. When possible, ALWAYS choose software that supports your specific carrier and service type/technology!!! If you are on a GSM network then choose a GSM rom and same for CDMA. However CDMA technology here in the US is a bit different from other countries in regards to how it is setup in the software. Each CDMA carrier will have it's own unique code inside system files. Simply replacing csc and other files will do NOTHING to fix this, leaving you with either no data services or improper generic data services. The only way to do this right is to either start with software for your specific carrier or manually modify these values in multiple files throughout framework and system using the correct values from software specific for your carrier. No exceptions.
The other thing. You ideally want to port the same Android version that is currently available for your specific device because the original kernel and libraries, etc need to support the version of Android in which you want to port. When porting you will be using most of your original software's bin files, kernel, etc... so these files need to be compatible with the version of Android you want to port. Very important!
I will not go into great details with smali modifications, etc because that is a whole different animal. This thread is a general breakdown of what is involved in the whole process. Porting a ROM such as the Note 7 software is no simple task, especially with so many unknown obstacles that must be discovered then remedied. You will need the right tools for the job before you even take on such a task. I'm talking about ApkTool, smali/baksmali, mad genius mentality, etc. Without the proper tools forget about it.
The main things that must be done for the rom to even boot, reside internally inside a few framework jar files. There will also be incompatible system files which must be removed and/or replaced with compatible versions that support your specific device/model. You also may need to make the rom support 32bit such is the case with the Note 4, since it is only 32 bit compatible. There can be no traces of 64bit libraries either inside the system apps or the library folder or else you will have issues. 32 bit devices cannot process 64 bit libraries, whether external or imbedded inside system apps. The one exception to this rule is when an app is multi-arch compatible which means the app can be installed on either 32 or 64 bit devices. In this case the 64 bit libs can remain although they will not be used since the 32 bit libs will be detected by the os. Thankfully 64 bit TouchWiz contains 99.9% of the necessary 32 bit libraries! So use them instead if your device is only compatible with 32 bit architecture.
There are several key Android/Samsung services that are not going to be compatible with other Samsung devices therefore one must identify these incompatible services and other methods in smali and either remove them or recode them in order for the rom to function in a way that is compatible with the device for which you will be running the software on. Sometimes you can simply replace services from your original device's software as long as it is compatible and from the same Android version, but not always.
There is NEVER going to be a set of instructions that will apply to all ROMS. Period. This stuff is always ever-changing with each update that Samsung releases. This is why there can be no accurate "guide" to porting TouchWiz. Whoever says otherwise is not knowledgeable on this stuff at all.
Once the framework files are prepared and rebuilt properly then you will need to have knowledge of the stock system apps and what role they play in the software. Most system apps are cross compatible but some are device and/or carrier specific and must either be removed or replaced in order for the rom to boot and run without a complete meltdown with continuous FC's. Then you have CSC (customer service codes). This plays a major role in how the software will be setup on initial rom setup. Each specific device model will have it's own unique CSC, however most of Samsung's current CSC is identical between the current available top tier devices such as the N4, N5, S7 and N7. BUT each device will have it's own unique "values" within multiple files in CSC. Some Samsung devices are compatible with features that other Samsung devices do not support. Therefore you must have knowledge of this and make the necessary edits in order for the software features to be setup correctly without major malfunctions. One wrong value can actually cause the rom to not boot. You will need experience with this as well.
Next you may need to slightly modify the kernel's ramdisk to support a couple of additional framework files which is the case with the N7 software and probably the N5 as well. It's just a matter of adding a few file names to a text file, save, then recompile the zimage and place the modified kernel inside your rom zip. These types of things must be discovered by trial & error by people who are knowledgeable and have experience porting roms. But it goes to show that these little things can determine a successful or failed port. You never know what can cause the rom to not boot. There's so many pieces to the puzzle when porting.
Moving on to the build.prop and updater-script. There MUST be a lot of edits done to the build.prop and the same principal applies here. You MUST edit the build.prop in order for it to support the software AND your specific device model, cpu, security features, etc, etc. This is an art folks. Again... there is no "guide" for doing this properly. You must possess the mental aptitude to tackle this stuff. It's not for normal people The updater-script is a VERY VERY important part of the rom porting process because it contains the permissions and symbolic links for all of the critical system files and folders. You must manually edit the updater-script so that it sets the proper permissions and symbolic links for the files that are used in the current software you are going to run. You cannot simply use a stock device updater-script straight out of the kitchen for your specific device. It will not work due to other versions of TouchWiz will likely have additional or different files and folders in the rom. This will take a LOT of time to go over everything and make sure you covered everything and properly setup the updater-script.
Next there is the process of replacing critical and device specific libraries and bin files as well as kernel modules. Generally for Samsung devices, system/bin folder must contain all of the original files from the original stock software for your specific device. You might need to add additional files from the software you are porting. The same applies to the system/lib/modules. These modules MUST come from your device's original software. The libraries are very tricky because not all libraries can be from either your original stock software nor from the software you are porting. Simply put, this is going to be the single most time consuming process with a ton of trial and error. You must figure out which lib files must be used from your original software and which libs must come from the new ported software. Good luck figuring this out! :laugh:
This pretty much covers the initial areas of the system software that must be manually modified in order for the rom to actually boot.
As you can see, there's a lot of trial and error with porting roms. Believe me. Other people who ported the early N7 and S7 port ROMs have done a LOT of work and surely they have a lot of trial and error. These early port dev's deserve a lot of credit for these early discoveries without a doubt. Without their original trials and errors & hard work, there would be no other port roms. They shared their knowledge and it was a group effort in the beginning. You guys know who you are! :highfive: Much Thanks to all of you who figured out framework issues etc in the early stages of current TouchWiz. I learned a lot in this process in which I have never shared with the public simply because there's no point in giving information that others can't use due to lack of experience. Hopefully some people will read this and better understand what goes into porting these ROMs. At a later dat, I may write up a more detailed "guide" on current TouchWiz IF I feel there is a need and there is enough people willing to step up and help out the community in the future. This is the way XDA works. You have to pass the torch to win the race. No one person can conquer the world. Teamwork is the key to success in everything you do. Remember this. Thanks for reading.
Wow, very nice write up. Thanks!
I would be interested in a more detailed guide if and when you get to it. I'm always looking to expand my know - how.
Many thanks! :highfive:
Thanks for the post....
but you did not go in to ROM porting much at all... I'd love to read a in depth view of the " copy and paste " dev .
tx_dbs_tx said:
This will be focused primarily on the Sprint network capability since that is my current carrier. But these same basic steps will apply for all porting of TouchWiz.
GSM vs CDMA is another very important part of the porting process. When possible, ALWAYS choose software that supports your specific carrier and service type/technology!!! If you are on a GSM network then choose a GSM rom and same for CDMA. However CDMA technology here in the US is a bit different from other countries in regards to how it is setup in the software. Each CDMA carrier will have it's own unique code inside system files. Simply replacing csc and other files will do NOTHING to fix this, leaving you with either no data services or improper generic data services. The only way to do this right is to either start with software for your specific carrier or manually modify these values in multiple files throughout framework and system using the correct values from software specific for your carrier. No exceptions.
The other thing. You ideally want to port the same Android version that is currently available for your specific device because the original kernel and libraries, etc need to support the version of Android in which you want to port. When porting you will be using most of your original software's bin files, kernel, etc... so these files need to be compatible with the version of Android you want to port. Very important!
Click to expand...
Click to collapse
This was great. It was exactly what I was looking for. Ive being working on porting a gsm rom to my device N900P. But the only thing Ive found is copy and paste. Trying to find something on cdma is even harder. Ive just download your Ultimate Hybrid N7 to see if can get a clue on where to start. Deodexing telephony-common should be enough? Where else should start looking? If you could point me a direction would be great. Thanks
triskaw said:
This was great. It was exactly what I was looking for. Ive being working on porting a gsm rom to my device N900P. But the only thing Ive found is copy and paste. Trying to find something on cdma is even harder. Ive just download your Ultimate Hybrid N7 to see if can get a clue on where to start. Deodexing telephony-common should be enough? Where else should start looking? If you could point me a direction would be great. Thanks
Click to expand...
Click to collapse
Sorry for the late reply. To be honest, porting a gsm rom to work on a U.S. cdma carrier is going to require massive work. Forget about it. Start your rom project with cdma compatible software and save yourself the trouble. You'll win the lottery before you get a gsm rom ported over to cdma. Copy and paste isn't going to scratch the surface. Why not port a factory Sprint ROM for your Sprint note 3? Such as the Sprint N7, N5, S7 edge? It is already setup to work on the sprint network. It would save you a lot of time and effort.
Hello,
HTC having obviously stopped supporting my smartphone in terms of updating android, I want to create a custom ROM to enjoy the benefits of the later versions of android in Mashmallow.
However, HTC provides the source code of the linux kernel used as well as some tools necessary for the proper functioning of the device. In addition, it also provides a guide to compiling android. Unfortunately, this guide seems incomplete or poorly explained. So I would like to get help in compiling an android rom for this device.
Please do it. unfortunately I have bought this device recently a month ago and feels like i have been cheated by HTC!! No proper support no software or security updates and really poor website with no useful data to end user, it seems that the company produced this model and dumped in the market to get our money and forgotten or ignoring users with at least security updates, even the non branded Chinese phones get better support than this brick from HTC. My first HTC phone was windows mobile on 2008 , it was poorly supported and my bad luck again with HTC u play which has the same situation. I will never buy from this company again.
citorva said:
Hello,
HTC having obviously stopped supporting my smartphone in terms of updating android, I want to create a custom ROM to enjoy the benefits of the later versions of android in Mashmallow.
However, HTC provides the source code of the linux kernel used as well as some tools necessary for the proper functioning of the device. In addition, it also provides a guide to compiling android. Unfortunately, this guide seems incomplete or poorly explained. So I would like to get help in compiling an android rom for this device.
Click to expand...
Click to collapse
Have you been sucessfull in building costom rom
if yes share it please