Related
Lets just go straight to the point :
Make sure that you've :
- Downloaded and extracted 'DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit)' (ref : http://forum.xda-developers.com/showthread.php?t=1321582)
- Installed Android SDK to enable you to run ADB shell
- Enabled 'Unknown Sources' in your phone
- Enabled 'USB Debugging' in your phone
Step 1 :
- Open command line as Administrator and go to 'android-sdk/platform-tools' folder
- Run this command :
adb devices (after this command you should see your device id)
adb shell
echo 1 > /data/local/lge_adb.conf
- Leave the cmd windows open
Step 2 :
- Go to DooMLorD folder
- run 'runme.bat'
- press 'Enter' once and then once more
VOILA!!
p/s : You can close the 'cmd' windows now
Superoneclick method is better which dosent need android sdk installed
its just another way. no biggie
I rooted my O1 with Superoneclick and I recommend it , fast and safe
Sorry, where can i found superoneclick?
i have O1 with last ginger update, it's compatible?
kyrulamri said:
Lets just go straight to the point :
Make sure that you've :
- Downloaded and extracted 'DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit)' (ref : http://forum.xda-developers.com/showthread.php?t=1321582)
- Installed Android SDK to enable you to run ADB shell
- Enabled 'Unknown Sources' in your phone
- Enabled 'USB Debugging' in your phone
Step 1 :
- Open command line as Administrator and go to 'android-sdk/platform-tools' folder
- Run this command :
adb devices (after this command you should see your device id)
adb shell
echo 1 > /data/local/lge_adb.conf
- Leave the cmd windows open
Step 2 :
- Go to DooMLorD folder
- run 'runme.bat'
- press 'Enter' once and then once more
VOILA!!
p/s : You can close the 'cmd' windows now
Click to expand...
Click to collapse
Superoneclick has zergRush exploit in it and more.
Anyone wanting to root their phone or flash baseband go into my guide, link is in my signature
Hi mates¡
First of all, sorry for my english.
I didnt want open a thread for my issue but i cant find anthing thath work for me. I began to comment the issue at Pandemic's thread (it's the guide that I below to flash). When I read the answers is like my problem is so weird...
Well, my setup:
* Neo Mt15i with 0.62 stock
* Pc with a clean installation of Ubuntu 12.04
* I installed Java JDK with this Guide:
http://forums.team-nocturnal.com/showthread.php/772
* I installed ADB with that:
http://forums.team-nocturnal.com/showthread.php/773
After that, I add tu /udev/rules/ with my IDVENDOR and IDPRODUCT (I get it using the terminal using "$ lsusb". I readed it from a guide at XDA but cant find now, later I will edit this and add the link ) the line from flashtool web:
Add these rules to /etc/udev :
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="*", MODE="0777"
Click to expand...
Click to collapse
Click to expand...
Click to collapse
* Download Flashtool 0.6.9.1;M check Md5 (OK) and extrac in home folder (my user folder)
* Download 2 differents files of firmware 0.42 GLOBAL for MT15i; I cant find the MD5 of those
PROCESS
Well, doing all of that Flashtool can recognise my Neo ON with Usb debbuging ON; third applications ON; MSC ON
FLASHTOOL LOG:
02/058/2012 11:58:14 - INFO - <- This level is successfully initialized
02/058/2012 11:58:14 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:43:11
02/058/2012 11:58:14 - INFO - You can drag and drop ftf files here to start flashing them
02/058/2012 11:58:19 - INFO - Device disconnected
02/058/2012 11:58:28 - INFO - Device connected with USB debugging off
02/058/2012 11:58:28 - INFO - For 2011 devices line, be sure you are not in MTP mode
02/058/2012 11:58:29 - INFO - Device connected with USB debugging on
02/058/2012 11:58:30 - INFO - Connected device : MT15
02/058/2012 11:58:30 - INFO - Installed version of busybox : N/A
02/058/2012 11:58:30 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
Click to expand...
Click to collapse
Afterthat click flash; select Firmware (on fw folder) and connect the phone on FLASHMODE when the prompt order and thats its my LOG:
02/058/2012 11:58:54 - INFO - Device disconnected
02/059/2012 11:59:10 - INFO - Selected MT15i_4.0.2.A.0.42_Global.ftf
02/059/2012 11:59:10 - INFO - Preparing files for flashing
02/059/2012 11:59:12 - INFO - Please connect your device into flashmode.
02/059/2012 11:59:17 - INFO - Device connected in flash mode
02/059/2012 11:59:17 - INFO - Phone ready for flashmode operations.
02/059/2012 11:59:17 - INFO - Start Flashing
02/059/2012 11:59:17 - INFO - Flashing loader
02/059/2012 11:59:19 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : NOT_ROOTABLE
02/059/2012 11:59:19 - INFO - Flashing adsp.sin
02/059/2012 11:59:23 - INFO - Ending flash session
02/059/2012 11:59:39 - ERROR - Transferred 41472 bytes of 65536
02/059/2012 11:59:39 - ERROR - Error flashing. Aborted
02/059/2012 11:59:40 - INFO - Device disconnected
Click to expand...
Click to collapse
I must to unplug the NEO because it dont work. When I do this LOG its the 10 time i tried, and never works, even I wait for half hour. Thats because I didnt wait this time, always its the same...
I will update that with SCREENSHOTS later... For a easier understanding.
* I must use a virtual machine to install SEUS or PCCOMPANION, because of that I create that with VIRTUAL BOX and install winXP. I try flashtool here too.
I installed JavaJDK; SDK; DRIVERS from drivers folder of Flashtool.
No works either...The same result
I think to create another VM with win7 to try on that but i will do it later.
Thats all my problem, i dont know what more I can do...Could you help me??
Many many thanks for all those wath read the long text and dont get tired of my english.
Your udev rules is flaky, flashtool is a more than just adb.
Use the one from here
http://forum.xda-developers.com/showthread.php?p=25511424
Also don't connect the phone till it tells you
Sent from my MT11i using Tapatalk
Thanks for the fast answer.
In the link that you wrote before there are another link of minus,and those are dead links...
My android rules in udev have more info, I copy that of the link I posted before about install ADB. At final of these links I write that one of FLAHTOOL web. I found another three lines to write here but im not at pc and I havent the links here... This three lines was writed for a Spanish xdader at a thread its the only thing I remember.
Later I will post the link and my android rules.
Any idea for now?
Sent from my MT15i using XDA
The link is not dead, click standard view, then back then refresh it will work
Sent from my MT11i using Tapatalk
Sorry men, its true, I check ir fast and didnt think too much...tomorrow I will try them on pc.
I will search info about these files because I dont know anything,
There are another thread talking about them, or an howto install them?? Im not at pc and search here its worth....
Im so noob at linux too
But I learn fast when something its interesting to me, and ubuntu surprise so much to me.
Many many thanks for your help
Sent from my MT15i using XDA
which language installed on your ubuntu is it non-english
exactly flashtool have some issues on non-english OS
you can put this line on flashtool executable file
export LANG=en_US.UTF-8
than flashtool will work fine
EDIT:flashtool was updated to 0.7.1.0 you can get it from here
mpiekp said:
The link is not dead, click standard view, then back then refresh it will work
Sent from my MT11i using Tapatalk
Click to expand...
Click to collapse
I change my android.rule file, I put yours one. Continue cant flashing, and when I connect with the phone ON Flashtool recognise it, and ADB too (with "$ adb devices").
The first one I have was three lines (one/conecction mode) which I get from this thread:
http://forum.xda-developers.com/showthread.php?t=1612273
Thats one is my actual 99-android.rules
http://tinypaste.com/91108a48
yacloo said:
which language installed on your ubuntu is it non-english
exactly flashtool have some issues on non-english OS
you can put this line on flashtool executable file
export LANG=en_US.UTF-8
than flashtool will work fine
EDIT:flashtool was updated to 0.7.1.0 you can get it from here
Click to expand...
Click to collapse
Thanks men, I have spanish language installed on Ubuntu, and i havent any idea of where I have to put that line of code when I open it with gEdit.
could I change my language now for that?
I see now that always that I unplugg the phone flashtool first say that is in Usb debuging OFF and then says thats its ON,,,I saw it on other thread (which i cant found for now)
With the new version of Flashtool i have always the same problem:
04/000/2012 05:00:01 - INFO - <- This level is successfully initialized
04/000/2012 05:00:01 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:14
04/000/2012 05:00:01 - INFO - You can drag and drop ftf files here to start flashing them
04/000/2012 05:00:01 - INFO - Device disconnected
04/000/2012 05:00:11 - INFO - Selected MT15i_4.0.2.A.0.42_Vodafone.ftf
04/000/2012 05:00:11 - INFO - Preparing files for flashing
04/000/2012 05:00:11 - INFO - Please connect your device into flashmode.
04/000/2012 05:00:16 - INFO - Device connected in flash mode
04/000/2012 05:00:17 - INFO - Reading device information
04/000/2012 05:00:37 - INFO - Start Flashing
04/000/2012 05:00:37 - INFO - Flashing loader
04/000/2012 05:00:37 - INFO - Ending flash session
04/000/2012 05:00:37 - ERROR -
04/000/2012 05:00:37 - ERROR - Error flashing. Aborted
04/000/2012 05:00:37 - INFO - Device disconnected
Click to expand...
Click to collapse
With olders flashtools have same issues that before, starts but stops randomly...nothing changes after all...for now I hope.
The ways off today:
* 3 FTF 0.42 global and vodafone for MT15i
* 3 versions of FLASHTOOL (all with md5 OK)
* Repeat after fail, dont use before SEUS
* Ubuntu and Winxp on VM
Thanks for all the support
pollolpc said:
Thanks men, I have spanish language installed on Ubuntu, and i havent any idea of where I have to put that line of code when I open it with gEdit.
could I change my language now for that?
Click to expand...
Click to collapse
open FlashTool file and your file must look like this
#!/bin/sh
export BASEDIR=$(dirname $0)
export system64=$(uname -m)
export LANG=en_US.UTF-8
if test -z "${JAVA_HOME}"
then
if test "${system64}" = "x86_64"
then
export JAVA_HOME=${BASEDIR}/x10flasher_lib/linjre64
else
export JAVA_HOME=${BASEDIR}/x10flasher_lib/linjre32
fi
echo "JAVA_HOME not set. Using default value : ${JAVA_HOME}"
fi
chmod 755 ${BASEDIR}/x10flasher_lib/adb.linux
chmod 755 ${BASEDIR}/x10flasher_lib/fastboot.linux
chmod 755 ${BASEDIR}/x10flasher_lib/adb.mac
chmod 755 ${BASEDIR}/x10flasher_lib/fastboot.mac
if test -e ${JAVA_HOME}/bin/java
then
$JAVA_HOME/bin/java -Xms128m -Xmx512m -jar x10flasher.jar
else
echo "No Java in specified path in JAVA_HOME=${JAVA_HOME}"
echo "Set the variable to a valid Java installation"
fi
Click to expand...
Click to collapse
Because I didnt knew how insert that line in FLASHTOOL i tried to do other thing; change language on a terminal wich will run flashtool....i dont have idea if this is stupid....but i tried, nothing to loose i thinked....
"change the language with that :
$ export LANG=en_US.UTF-8
Click to expand...
Click to collapse
I copied the info give me the terminal, i didnt know if this could be helpful...
Post at tiny paste for a cleaner post:
http://tinypaste.com/38e38b82
yacloo said:
open FlashTool file and your file must look like this
Click to expand...
Click to collapse
Ok many many thanks, i give a try richt now
Didnt work bro, try to start flashing but stops suddenly without flash any file. Before didnt try flash, stops at READ DEVICE...
Heres the log:
http://tinypaste.com/37c68abc
Thanks a lot for your attention
pollolpc said:
Didnt work bro, try to start flashing but stops suddenly without flash any file. Before didnt try flash, stops at READ DEVICE...
Heres the log:
http://tinypaste.com/37c68abc
Thanks a lot for your attention
Click to expand...
Click to collapse
I think you are using 64-bit ubuntu
Check that libusb-1.0 is installed. On 64bits system, both 64bit and 32bit should be installed
hope can work
yacloo said:
I think you are using 64-bit ubuntu
Check that libusb-1.0 is installed. On 64bits system, both 64bit and 32bit should be installed
hope can work
Click to expand...
Click to collapse
Im usin 64 bits, yes. I think I installed them...I check Synaptics:
Uploaded with ImageShack.us
Both ticked from bottom no?
I think only 64bit libusb installed
You can get it those files for 32 bit from packages.ubuntu.com
Both files are same low versioned one for old applications
Sent from my MT11i using XDA
yacloo said:
I think only 64bit libusb installed
You can get it those files for 32 bit from packages.ubuntu.com
Both files are same low versioned one for old applications
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Im reading about this, i found that if I install 32 bits package, uninstall 64 bits....that isnt a problem? ... I found this in another forum:
http://askubuntu.com/questions/127701/gcc-m32-cannot-find-libraries
You could install the 32-bit packages for these libraries:
$ sudo apt-get install libusb-dev:i386 libX11-dev:i386
Note, however, that this will remove the 64-bit versions. Probably it's better to use a chroot (e.g. with cowbuilder or pbuilder) or Qemu image for this kind of thing. E.g. create the file ~/.pbuilderrc-precise-i386:
# Set this to the distribution you want to build for
DISTRIBUTION=precise
# The architecture you want to build for
ARCHITECTURE=i386
# The directory in which to store the chroot base image
BASEPATH=/var/cache/pbuilder/base-precise-i386.cow
# The repositories to be enabled in the /etc/apt/sources.list
COMPONENTS="main universe"
# If you want to speed things up with ccache, enable these options
export CCACHE_DIR="/var/cache/pbuilder/ccache"
export PATH="/usr/lib/ccache:${PATH}"
# List here all packages you need to build your software
# (e.g. build-essential, libusb-dev, libX11-dev, etc.)
EXTRAPACKAGES=ccache
# List here all directories from you system that should be visible inside the chroot
BINDMOUNTS="${CCACHE_DIR} ${HOME}/projects"
Then install cowbuilder and create the base image as follows:
$ sudo apt-get install cowbuilder
$ sudo cowbuilder --create --configfile ~/.pbuilderrc-precise-i386
Lastly, enter the chroot and finish configuring it (copy over configuration files:
$ sudo cowbuilder --login --save-after-exec --configfile ~/.pbuilderrc-precise-i386
You can exit the chroot using Ctrl+D or using exit. Now you have set up your base-image. In the future, don't use the --save-after-exec flag any more when entering the chroot. This ensures that all the modifications will be discarded after you leave the chroot, ensuring a clean build environment for future builds.
Now you should be able to enter the chroot and build your software:
$ sudo cowbuilder --login --configfile ~/.pbuilderrc-precise-i386
% cd $HOME/projects/foo
% # build project foo
Note, however, that the files created in this way will be owned by root. Hence, out-of-source builds are a very good idea.
Click to expand...
Click to collapse
I dont know what to do
pollolpc said:
Im reading about this, i found that if I install 32 bits package, uninstall 64 bits....that isnt a problem? ... I found this in another forum:
http://askubuntu.com/questions/127701/gcc-m32-cannot-find-libraries
I dont know what to do
Click to expand...
Click to collapse
That was ia32 lib issue install both files and ia32 lib file other 64 ones will not be removed
Sent from my MT11i using XDA
I check that with this: $ dpkg -l libusb\* and I have this versions:
||/ Nombre Versión Descripción
+++-==============-==============-============================================
ii libusb-0.1-4 2:0.1.12-20 userspace USB programming library
ii libusb-1.0-0 2:1.0.9~rc3-2u userspace USB programming library
un libusb-1.0-0-d <ninguna> (no hay ninguna descripción disponible)
un libusb0 <ninguna> (no hay ninguna descripción disponible)
ii libusbmuxd1 1.0.7-2 USB multiplexor daemon for iPhone and iPod T
Click to expand...
Click to collapse
0,1.4 is 32 bits or im wrong again?
The last version of flashtool say that:
04/015/2012 07:15:07 - INFO - <- This level is successfully initialized
04/015/2012 07:15:07 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:14
04/015/2012 07:15:07 - INFO - You can drag and drop ftf files here to start flashing them
04/015/2012 07:15:08 - INFO - Device connected with USB debugging on
04/015/2012 07:15:09 - INFO - Connected device : MT15
04/015/2012 07:15:09 - INFO - Installed version of busybox : N/A
04/015/2012 07:15:09 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
04/015/2012 07:15:09 - INFO - Phone in recovery mode
04/015/2012 07:15:09 - INFO - Root Access Allowed
WTF? Im still at 0.62 on "about"
Sorry for be worried
...I have an update avaiable ny OTA....The 0.62...and my about section sqy 0.62 too..:banghead:
Sent from my MT15i using XDA
pollolpc said:
I check that with this: $ dpkg -l libusb\* and I have this versions:
0,1.4 is 32 bits or im wrong again?
The last version of flashtool say that:
04/015/2012 07:15:07 - INFO - <- This level is successfully initialized
04/015/2012 07:15:07 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:14
04/015/2012 07:15:07 - INFO - You can drag and drop ftf files here to start flashing them
04/015/2012 07:15:08 - INFO - Device connected with USB debugging on
04/015/2012 07:15:09 - INFO - Connected device : MT15
04/015/2012 07:15:09 - INFO - Installed version of busybox : N/A
04/015/2012 07:15:09 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
04/015/2012 07:15:09 - INFO - Phone in recovery mode
04/015/2012 07:15:09 - INFO - Root Access Allowed
WTF? Im still at 0.62 on "about"
Sorry for be worried
Click to expand...
Click to collapse
download those files and install via dpkg -i *.deb
libusb-0.1-4_0.1.12-20_i386.deb
libusb-1.0-0_1.0.9~rc3-2ubuntu1_i386.deb
and you have to search on synaptic for ia32-libs and ia32-libs-multiarch
than install those packages
if doesn't work switch to 32bit ubuntu or 32bit windows for better compatibility
It's working fine here on 64 12.4
If the above doesn't work, I'll post a list of installed packages, should sort you out
Sent from my MT11i using Tapatalk
Hello guys, I have a little problem with developing apps in my phone.
I installed Stock Android 4.1.2 v4 for my Xperia U ST25i ( http://forum.xda-developers.com/showthread.php?t=2284394 ) (I wanted to post this issue in this thread but i'm new here and I just can't... anyways, rules are rules), and i'm have some issues when I want test APK's in my phone via ADB or Eclipse-ADT.
When I click excecute ( or do adb install), the process will fail, showing me that:
Code:
[2013-07-23 16:40:48 - AWifiSignal] ------------------------------
[2013-07-23 16:40:48 - AWifiSignal] Android Launch!
[2013-07-23 16:40:48 - AWifiSignal] adb is running normally.
[2013-07-23 16:40:48 - AWifiSignal] Performing net.elsemieni.awifisignal.SplashActivity activity launch
[2013-07-23 16:40:48 - AWifiSignal] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2013-07-23 16:40:51 - AWifiSignal] WARNING: Unknown device API version!
[2013-07-23 16:40:51 - AWifiSignal] Uploading AWifiSignal.apk onto device 'YT9002B59S'
[2013-07-23 16:40:52 - AWifiSignal] Installing AWifiSignal.apk...
[2013-07-23 16:40:53 - AWifiSignal] Installation failed due to invalid APK file!
[2013-07-23 16:40:53 - AWifiSignal] Please check logcat output for more details.
[2013-07-23 16:40:53 - AWifiSignal] Launch canceled!
In simple words, doesn't install beacuse [INSTALL_FAILED_INVALID_APK] error code.
Of course, i have Debugging activated in my phone and install 3rd party applications.
By the way, Logcat gives me that
Code:
07-21 18:05:23.663: W/zipro(25492): Unable to open zip '/data/local/tmp/AWifiSignal.apk': Permission denied
07-21 18:05:23.673: W/PackageParser(25492): Unable to read AndroidManifest.xml of /data/local/tmp/AWifiSignal.apk
That's curious I can't write inside it. I searched the forums and I applied a workaroud solution (http://forum.xda-developers.com/showthread.php?p=40040546&postcount=4), to make a link from tmp to sdcard folder. It worked in this way, but ruined the phone sys after reboot ( crashes randomly, most critical app's frezzes, etc), so doesn't work.
I know that's a firmware bug, but... any ideas about this? There's another workaround to make tmp safely writable, or any way to change the folder who ADB uses to install apps remotely?
Thanks! :laugh:
I am sorry that I know there are so many articles talking about
Drivers need to be installed for connected device.
You can find them in the drivers folder of Flashtool.
I have read so many articles but still cannot find out the problem.
I go to "Devices" of Flashtool and "Check Drivers"
It gave me this
01/004/2014 00:04:31 - INFO - List of connected devices (Device Id) :
01/004/2014 00:04:31 - INFO - - USB\VID_0FCE&PID_51AF\CB5A1YAHWN Driver installed : true
01/004/2014 00:04:31 - INFO - - USB\VID_0FCE&PID_51AF&MI_01\6&E66E0BD&0&0001 Driver installed : true
01/004/2014 00:04:31 - INFO - - USB\VID_0FCE&PID_51AF&MI_00\6&E66E0BD&0&0000 Driver installed : true
01/004/2014 00:04:31 - INFO - List of ADB devices :
01/004/2014 00:04:31 - INFO - - CB5A1YAHWN
01/004/2014 00:04:31 - INFO - List of fastboot devices :
01/004/2014 00:04:31 - INFO - - none
And I could not unlock bootloader.
I have ticked the USB Debug yet my Z2 is not rooted yet.
Do I have to root it first?
May someone guide me how to unlock because I cannot finish it using the official way
It always keeps telling me "Waiting for device"
Thank you so much!
http://www.theandroidsoul.com/unlock-bootloader-on-sony-xperia-z2/
I followed this website.
Using method 1, I could not achieve step 4
Using method 2, when I type fastboot.exe -i 0x0fce getvar version
noting happened, it seemed to be saying "cannot find 0x0fce" or somthing else
I don't know why it keeps telling me no driver installed
I go to Device Manager of Windows and it shows it has the updated driver installed in the PC
I am using Win 8.1
http://forum.xda-developers.com/showthread.php?t=2635830
This thread will help alot
Press windowsKey + R
type/paste
Code:
shutdown -o -r -t 0
into the box, this will restart your machine in the advanced startup menu.
when it restarts choose "disable driver signing" Then install the driver manually using the "have disk" option. when you reboot again the driver should be working.
-------------------
I followed what it said but when is "when it restarts choose "disable driver signing" Then install the driver manually using the "have disk" option. "???
I could not find disable driver signing.
After entering the shutdown command, what button should I press? Thank you for replying! I wish I will be able to flash rom today
Not sure what to do then because i ran into the same issue but i just used a linux OS as a work around
Thanks for answering
I will try using Win Vista
I hope someone could teach me
ABOUT THE GALAXY ALPHA CM-12.1 PROJECT
I'm working on getting CyanogenMod working on the Galaxy Alpha since October 2014. This ROM is not complete. There are still features which are not fully working and there are for sure things which need bugfixing. Please check the Known Bugs section before reporting issues.
I work on this project for FREE and putting in a lot of hours into it. A small donation would help to buy better tools to improve the development some day.
RECOVERY
To be able to install the ROM you need a recovery. I suggest to use my TWRP Recovery build. You can find it here.
BACKUP
Before installing the ROM you should create backups. The most important backup is to create one of the EFS partition and store it on safe place on your computer. If something goes wrong you need to restore this partition. It holds information about your device, like the MAC address for your wifi and information for the radio.
DOWNLOAD
You are storing very sensitive information on your phone. You always have to be careful what ROMs you flash and whom you trust. If you don't trust me then don't use my ROM or compile it from source by yourself.
The ROM will be gpg signed with my key 0xCC014E3D. You can verify the ROM with 'gpg --verify cm-12.1-20150901-UNOFFICIAL-slte-beta1.zip.asc '.
Detailed information and instruction for Windows can be found here.
Download BETA
FLASHING THE ROM
As this is a Lollipop (Android 5) based ROM you need to flash sboot (bootloader) and the modem image from one of the latest LL releases. Or install a LL ROM via the Samsung update option. You can find the latest stock ROM here. Suggested modem version is: G850FXXU2COI3 or newer
I suggest to put the ROM on a USB disk and use a USB OTG cable to flash the ROM. It is also possible to put it on the emulated sdcard and flash it from there.
GAPPS
I suggest to use Open GAPPS.
REPORTING BUGS
Give the programmer some credit for basic intelligence: if the program really
didn't work at all, they would probably have noticed. Since they haven't
noticed, it must be working for them. Therefore, either you are doing something
differently from them, or your environment is different from theirs. They need
information; providing this information is the purpose of a bug report. More
information is almost always better than less.
Click to expand...
Click to collapse
Before reporting bugs, please check the KNOWN BUGS list below and read THIS HOWTO
XDA:DevDB Information
[ROM][SM-G850F] CM-12.1 UNOFFICIAL ROM, ROM for the Samsung Galaxy Alpha
Contributors
modpunk, raymanfx, bonuzzz, kyasu
Source Code: https://git.cryptomilk.org/projects/android/android_device_samsung_slte.git/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP/CWM Recovery
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 8
Beta Release Date: 2015-10-22
Created 2015-09-01
Last Updated 2015-10-26
KNOWN ISSUES
RIL: SMS broadcast subscriptions aren't working (generic failure)
MEDIA: HEVC videos don't work
INCALL: Some SLTE devices need 10-30 seconds to wake the screen on an incoming call
VOIP: Not tested (could someone please test)
CHANGELOG
2015-10-22 + BETA8
audio: Should be completely working now
ril: Fixed network operator search
2015-10-15 - BETA7
audio: More fixes to get audio fully working
audio: Fixed voice recording (camcorder should work fine now)
audio: Fixed media playback (especially over bluetooth)
camera: Fixed remaining camera issues (using LL blobs now)
Kernel: Smaller kernel image using XZ compression now
Kernel: Updated arizona sound driver
2015-10-10 - BETA6
More fixes to the audio HAL
Improved PowerHAL (VSYNC and LOW_POWER) support
This version includes the latest Security fixes for Android, see the Android Patchlevel in Settings -> About Phone.
2015-10-07 - BETA5
Fixed audio calls (wideband)
Fixed audio calls with bluetooth headset and carkit
Fixed audio recordings
This version includes the latest Security fixes for Android, details see here.
2015-10-02 - BETA4
Fixed bluetooth call playback (mics are not working yet)
Fixed two mic control in audio HAL
Fixed firmware loading on wisol devices
New sensor HAL
Improved boot time
2015-09-17 - BETA3
Added bluetooth headset support
Added support for noise suppression
Better sound quality on wideband connections
2015-09-03 - BETA2
Fixed flashing issue with TWRP
Set addtitional build information
2015-09-01 - BETA1
Initial release
FREQUENTLY ASKED QUESTIONS
"It doesn't work."
Give the programmer some credit for basic intelligence: if the program really didn't work at all, they would probably have noticed. Since they haven't noticed, it must be working for them. Therefore, either you are doing something differently from them, or your environment is different from theirs. They need information; providing this information is the purpose of a bug report. More information is almost always better than less.
Please read How to Report Bugs Effectively
My modem doesn't work, what can I do?
Did you flash the latest MODEM firmware from the latest Lollipop release? The suggested firmware is at least G850FXXU2COI3 or newer
How do I use adb/logcat go get logs from my device
You can find a good tutorial here.
I have problem with flashing. I tried with suggested TWRP. Flashing rom takes 1 second and ends with successful information
Edit. "Unable to mount /system" twrp error
miszko77 said:
I have problem with flashing. I tried with suggested TWRP. Flashing rom takes 1 second and ends with successful information
Edit. "Unable to mount /system" twrp error
Click to expand...
Click to collapse
Which TWRP version are you using?
Awesome work man. Honestly I can't flash this right now, just because, I need a fully functioning device daily so, I'll be patient
modpunk said:
Which TWRP version are you using?
Click to expand...
Click to collapse
I am using 2870. Anyway I flashed recovery with odin. May this be a problem?
miszko77 said:
I have problem with flashing. I tried with suggested TWRP. Flashing rom takes 1 second and ends with successful information
Edit. "Unable to mount /system" twrp error
Click to expand...
Click to collapse
I have same problem
---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------
miszko77 said:
I am using 2870. Anyway I flashed recovery with odin. May this be a problem?
Click to expand...
Click to collapse
I am using 2.8.7 also
lukrangelu said:
I have same problem
---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------
I am using 2.8.7 also
Click to expand...
Click to collapse
Could you connect with 'adb shell' to the recovery and run 'getenforce'. Then get me the log and avc_msg file with:
adb pull /tmp/recovery.log
adb pull /proc/avc_msg
and paste the file somewhere ...
modpunk said:
Could you connect with 'adb shell' to the recovery and run 'getenforce'. Then get me the log and avc_msg file with:
adb pull /tmp/recovery.log
adb pull /proc/avc_msg
and paste the file somewhere ...
Click to expand...
Click to collapse
-a - directs adb to listen on all interfaces for a connection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <specific device> - directs command to the device or emulator with the given
serial number or qualifier. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the following format:
<serial> " " <local> " " <remote> "\n"
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fails
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --iv <hex-encoded iv>] <file>
- push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
('--algo', '--key', and '--iv' mean the file is encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default
is noobb.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
would it be this?
Blubberor said:
Thanks a lot modpunk,
initial bug after doing wipe incl. Cache, dalv.cache and using same minimal gapps that works in kyasus cm12.1
I dont have network setting up, sim card not detected and cannot manually activate it.
Again thank you for your work,
blubberor
Click to expand...
Click to collapse
Read the bug report section in the initial post, provide logcat for system/main and also radio. This is a beta version you should at least know the basics how to get information from the device ...
lukrangelu said:
would it be this?
Click to expand...
Click to collapse
Not even close. If you want to run a beta version you should learn at least the basics for using adb.
ADB/LOGCAT HOWTO
Here you are.
getenforce
Permissive
Click to expand...
Click to collapse
miszko77 said:
Here you are.
Click to expand...
Click to collapse
The recovery reports:
Code:
You have an installed system that isn't signed with this build's key, aborting...
script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
Can't install this package on top of incompatible data. Please try another package or run a factory reset
This is a pretty obvious message to me. You need to wipe system and data in order to install the ROM.
modpunk said:
You need to wipe system and data in order to install the ROM.
Click to expand...
Click to collapse
Result of wiping caches, data and system. See attachment.
I did factory reset and getting the same information.
miszko77 said:
Result of wiping caches, data and system. See attachment.
I did factory reset and getting the same information.
Click to expand...
Click to collapse
I've wiped my system partition and running into the same problem as you know. I'm investigating it now ...
modpunk said:
Read the bug report section in the initial post, provide logcat for system/main and also radio. This is a beta version you should at least know the basics how to get information from the device ...
Click to expand...
Click to collapse
Mfg
Blubberor said:
Mfg
Click to expand...
Click to collapse
Please pull /proc/avc_msg ...
modpunk said:
Please pull /proc/avc_msg ...
Click to expand...
Click to collapse
and here you go.
Thanks a lot. crossing fingers that the avc_msg.log helps you with fixing.
Tschö,
blubberor