[SM-G850F][SLTE] CyanogenMod 12.1 UNOFFICIAL BETA8 (Android 5.1) - UPDATE: 2015-10-22 - Samsung Galaxy Alpha

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

Related

[PORT REQUEST][DeV's only][SXU Floating touch]

COULD SOME DEV PLEASE HELP!!!:fingers-crossed:
I'm Sure floating touch can be ported to any android device by setting the screen sensitivity very high so that a way on the screen gets interpreted into a touch
.
.
This floating touch mod/port for the galaxy sl I9003 and galaxy 3(not galaxy s 3 just galaxy 3 I5800) thread states that floating touch can be enabled on most android devices , if someone(THATS WHERE THE DEV'S COME IN THE PICTURE) could find out for us which is the file that is responsible for the screen sensitivity
.
.
.
Heres the link to
the app that provides a gui for changing the sensitivity
http://forum.xda-developers.com/showthread.php?t=1932339
.
.Link to the actual thread from which the above thread/ app was created
http://forum.xda-developers.com/showthread.php?t=1915158
.
.
link to "how to tweak touch screen"
http://forum.xda-developers.com/showthread.php?t=1587553
.
.
link to thread that says any device can have floating touch!!(yipee but as i read , it turns into a frown cause it states all devices if the correct file can be dertermined )
http://www.xda-developers.com/android/floating-touch-on-the-samsung-galaxy-sl-i9003/
Deleted
I think glove mode can be ported but not the floating touch in browser cuz other devices cant make a difference between floating and touching...
Sent from my MT27i using xda app-developers app
Floating touch can't be ported to other devices, unless they use a similar touchscreen. You can have the 'floating' effect everywhere by setting the sensitivity to a very high value, but you won't be able to distinguish hover events and touch events that way.
What if we dont need to differentiate
Why do we need to differentiate at all??
at an earlier stage, we could make the phone to respond to floats as touches, so that the fingerprint is not a menace any more
PS im a noob , thats why i need some one to help me find out the correct touchscreen file to be modded:fingers-crossed:
arjun921 said:
Why do we need to differentiate at all??
at an earlier stage, we could make the phone to respond to floats as touches, so that the fingerprint is not a menace any more
PS im a noob , thats why i need some one to help me find out the correct touchscreen file to be modded:fingers-crossed:
Click to expand...
Click to collapse
It's not a single file anyway. Also, you just haven't tried that. It'll register random touches EVERYWHERE.
Maybe Maybe not , i aint so experienced...
K900 said:
It's not a single file anyway. Also, you just haven't tried that. It'll register random touches EVERYWHERE.
Click to expand...
Click to collapse
its just one file actually(maybe as per the thread which says to mod only one file), btw i even tried but couldnt find the path cause i got confused of which directory ahead...
.
.
. Please buddy Help me!!
Even if i get random touches, atleast it will be a start...
i dont mind giving the whole credit (whosoever if he/she helps ) but atleast lets try?:angel:
.
P.s. Check out all links for sure to have a better idea of what we actually are talking about(no offence intended but just in case you are an experienced developer still, please check)
A must try is the app which does the job...
Also till what i know is that the touch screen driver-file-to-be-modded lies in /sys/class/touch/switch/set_touchscreen/ for the galaxy s I9003
BUT for XPERIA U, i aint sure. I think it lies in /sys/class/input/
arjun921 said:
its just one file actually(maybe as per the thread which says to mod only one file), btw i even tried but couldnt find the path cause i got confused of which directory ahead...
.
.
. Please buddy Help me!!
Even if i get random touches, atleast it will be a start...
i dont mind giving the whole credit (whosoever if he/she helps ) but atleast lets try?:angel:
.
P.s. Check out all links for sure to have a better idea of what we actually are talking about(no offence intended but just in case you are an experienced developer still, please check)
A must try is the app which does the job...
Also till what i know is that the touch screen driver-file-to-be-modded lies in /sys/class/touch/switch/set_touchscreen/ for the galaxy s I9003
BUT for XPERIA U, i aint sure. I think it lies in /sys/class/input/
Click to expand...
Click to collapse
The Xperia U has a different touchscreen, which might or might not have manual sensitivity adjustment. I'm pretty sure it does not.
K900 said:
The Xperia U has a different touchscreen, which might or might not have manual sensitivity adjustment. I'm pretty sure it does not.
Click to expand...
Click to collapse
dude, galaxy 3 and Xperia U has the same touch sensing technology
so why cant we mod !?
is it that you just dont want this feature to be ported to anyother device, but rather stay on the device with which it actually came??
arjun921 said:
dude, galaxy 3 and Xperia U has the same touch sensing technology
so why cant we mod !?
is it that you just dont want this feature to be ported to anyother device, but rather stay on the device with which it actually came??
Click to expand...
Click to collapse
I'm pretty sure the sensor on the Galaxy 3 is not the same. It's the same vendor, but not the same model. I might be able to help you if you post the output of "find /sys/" in adb shell.
K900 said:
I'm pretty sure the sensor on the Galaxy 3 is not the same. It's the same vendor, but not the same model. I might be able to help you if you post the output of "find /sys/" in adb shell.
Click to expand...
Click to collapse
do one thing ,
please go through those threads, try installing that app,
check out the sys partiton, and then comment
if not interested, then please stop replying
:silly:
arjun921 said:
do one thing ,
please go through those threads, try installing that app,
check out the sys partiton, and then comment
if not interested, then please stop replying
:silly:
Click to expand...
Click to collapse
The app doesn't work, because it's intended for a different device with a different digitizer. The /sys file responsible is also relocated because a different device with a different digitizer needs a different kernel module, and the /sys files are created by that.
I might be able to help you if you post the output of "find /sys/" in adb shell.
Click to expand...
Click to collapse
It can't be done n stop insulting senior members by telling em to stop posting if they ain't interested, if dey weren't they would even reply
This is the problem with noobs they dun noe **** abt the devices and they expect magic/miracles from modders with features that device can't Hv due to hardware restrictions!!!
So if u think it can be done and you can do it and senior members/modders cant then I got jus 3 words foe u
"DO IT URSELF"
(Next tym pls do watch ur attitude and ur mouth before running it on senior members like K900 k)
Sent from my Xperia Sola using xda premium
I'm sorry, but I intended NO harm
I didn't even know what senior member means until you said it
I'm sorry K900
Thanks for the feedback
If you guys haven't noticed, this is my first thread here....
Sent from my ST25i using xda app-developers app
I don't know how to use adb btw
Sorry, but if you have time then could you please tell me what to do?
If you don't own the phone, I'll try to follow the instructions if you can help me:-o
Sent from my ST25i using xda app-developers app
I got adb installed, lemme try to find the path
Sent from my ST25i using xda app-developers app
arjun921 said:
I don't know how to use adb btw
Sorry, but if you have time then could you please tell me what to do?
If you don't own the phone, I'll try to follow the instructions if you can help me:-o
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
Btw here's the link which will provide you with all the adb stuff go through it
http://forum.xda-developers.com/showthread.php?t=1474956
Sent from my Xperia Sola using xda premium
Thanks!!
soulhackereborn said:
Btw here's the link which will provide you with all the adb stuff go through it
http://forum.xda-developers.com/showthread.php?t=1474956
Sent from my Xperia Sola using xda premium
Click to expand...
Click to collapse
Thanks man:good:
Got this
K900 said:
The app doesn't work, because it's intended for a different device with a different digitizer. The /sys file responsible is also relocated because a different device with a different digitizer needs a different kernel module, and the /sys files are created by that.
Click to expand...
Click to collapse
This is what i got on "adb find /sys/
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>cd C:\adb
C:\adb>adb find /sys/
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
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 r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
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.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
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
(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 <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 jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
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 help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
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 status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader 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 th
e 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 u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
C:\adb>
do adb shell
then find /sys

Tizen [Port] - Nexus 7

Hello everyone,
I started to port Tizen on Nexus 7.
Porting state:
- wifi working
- touchscreen working (doesn't yet support multitouch)
- media (pictures, music and videos) doesn't work
- no graphics acceleration (Xorg doesn't use Tegra module)
- USB doesn't work
- GPS / Bluetooth not tested
- Audio not tested
Installation:
To install it, you will need an unlocked Nexus 7 and MultiROMv7. MultiROMv7 is a way to have multi boot on Nexus 7. Once Recovery and MultiROMv7 are installed, you must reboot into recovery. Send image on your Nexus 7:
adb push /path/to/image/Nexus_7_Tizen.zip /sdcard/
After click on install button and select Nexus_7_Tizen.zip. It will install Tizen on your Nexus 7. Now you can reboot. In list of ROM, you will see Tizen_Testing. Select it and enjoy.
Download:
MultiROMv7: http://forum.xda-developers.com/showthread.php?t=2011403
Tizen ROM: http://easymt.org/files/Nexus_7_Tizen.zip
In days, I will publish instruction to build the ROM.
If you get this on par with the factory OS then you're a hair away from every nexus device using this if they want. Thank you for the work.
Sent from awesomeness?
Tizen 2.0?
Sent from my One S using xda app-developers app
Wonderful to see people just using MultiROM to create ports like this, good job
A big thank you for your work!
When USB will be avaible,
we can take screenshot from the Tizen SDK
(sdb_1.0.24_ubuntu-64)
Code:
sdb
Smart Development Bridge version 2.0.2
Usage : sdb [option] <command> [parameters]
options:
-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 <serial number> - directs command to the USB device or emulator with
the given serial number.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 26101 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 26101 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.
commands:
sdb push <local> <remote> [--with-utf8]
- copy file/dir to device
(--with-utf8 means to create the remote file with utf-8 character encoding)
sdb pull <remote> [<local>] - copy file/dir from device
sdb shell - run remote shell interactively
sdb shell <command> - run remote shell
sdb dlog [ <filter-spec> ] - view device log
sdb install <path_to_tpk> - push tpk package file and install it
sdb uninstall <appid> - uninstall this app from the device
sdb forward <local> <remote> - forward socket connections
forward spec is :
tcp:<port>
sdb help - show this help message
sdb version - show version num
sdb start-server - ensure that there is a server running
sdb kill-server - kill the server if it is running
sdb get-state - prints: offline | bootloader | device
sdb get-serialno - prints: <serial-number>
sdb status-window - continuously print device status for a specified device
it reminds me of something, but I do not know what
ikslawlok said:
Code:
sdb
Smart Development Bridge version 2.0.2
Usage : sdb [option] <command> [parameters]
options:
-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 <serial number> - directs command to the USB device or emulator with
the given serial number.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 26101 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 26101 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.
commands:
sdb push <local> <remote> [--with-utf8]
- copy file/dir to device
(--with-utf8 means to create the remote file with utf-8 character encoding)
sdb pull <remote> [<local>] - copy file/dir from device
sdb shell - run remote shell interactively
sdb shell <command> - run remote shell
sdb dlog [ <filter-spec> ] - view device log
sdb install <path_to_tpk> - push tpk package file and install it
sdb uninstall <appid> - uninstall this app from the device
sdb forward <local> <remote> - forward socket connections
forward spec is :
tcp:<port>
sdb help - show this help message
sdb version - show version num
sdb start-server - ensure that there is a server running
sdb kill-server - kill the server if it is running
sdb get-state - prints: offline | bootloader | device
sdb get-serialno - prints: <serial-number>
sdb status-window - continuously print device status for a specified device
Click to expand...
Click to collapse
LOL. adb knockoff.
johnwazhere said:
Tizen 2.0?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Actually, it is Tizen 2.0 alpha. I'm porting 2.0.
Thanks for the port! I have a question though, doesn't Nvidia have a (non-Android) Linux code tree for the Tegra 3? Couldn't the video driver from that tree be used? (even though it's for their development tablet from what I've read the socs are identical)
https://developer.nvidia.com/linux-tegra
Sent from my Nexus 7 using Tapatalk HD
Culex316 said:
Thanks for the port! I have a question though, doesn't Nvidia have a (non-Android) Linux code tree for the Tegra 3? Couldn't the video driver from that tree be used?
Click to expand...
Click to collapse
Yes it can be used. The driver work but it enable mice pointer.
Edit:
In fact I can't use it because xorg server and driver abi missmatch.
I probaly need to buimd another version of xorg than provided.
Thanks for your effort in this, very interested in this project. It's amazing to see the amount of operating systems being ported to Nexus 7.
I am extremely distress about the fact that other dev claimed successfuly port tizen to smartphones, also uploaded his work and nobody believe him (just because thefact that his work is rather complicated and no one smart enough to figure out how to do with his roms), you guys even teasing and disrespect him. Now a few months later, this dev put up with his work and an easier cleaner ways to install, these same non believer ppl comes in and appraise like its not a big deal (or lies?) and pretend nothing happened and they havent done nothing? Seriously you guys should do something about your attitide and mental capacity
Sent from my GT-P6800 using xda app-developers app
You're right man.
Anyone believed in him.
I do not know why all this lies telling about his work.
He got several downloads through internet about his work. And no respect at all.
---------- Post added at 06:42 PM ---------- Previous post was at 06:32 PM ----------
I'm going to quit from here xda.
This was a bad experience.
I've released code.google.com/p/tizen-kernel-s8500
a github.com/vic3t3chn0
a twitter.com/vicetechno
for my it works.
now, i'm going to quit for the bad experience at telling me i'm a liar.
but I had downloads at code.google.com if i'm a liar.
thank you for all.
long6688 said:
I am extremely distress about the fact that other dev claimed successfuly port tizen to smartphones, also uploaded his work and nobody believe him (just because thefact that his work is rather complicated and no one smart enough to figure out how to do with his roms), you guys even teasing and disrespect him. Now a few months later, this dev put up with his work and an easier cleaner ways to install, these same non believer ppl comes in and appraise like its not a big deal (or lies?) and pretend nothing happened and they havent done nothing? Seriously you guys should do something about your attitide and mental capacity
Click to expand...
Click to collapse
I don't know who exactly do you mean, but if it is the author of "Tizen [PORT] Attempt almost" thread then you might have not read that thread (or do not know bada/tizen forums) well enough to know that he claimed that he has so many things up and running without bothering to actually try to run it.
When we wanted to know the details it came out that he used many components developed by badadroid team without proper credit and claiming to have functionality that never existed (like working RIL or even stupid lie that he changed a bootlogo in the component that was not responsible for displaying it - to cover this lie he changed one line and provided only the non-working binary violating GPL, but the component was pure assembly we wrote so seeking truth was not difficult) in these components and were known not to be working with Tizen (kernel init not aligned with Tizen).
Looking at the repositories he pointed to, there is no source code he developed or even modified by himself - everything is public and part of other projects.
You are free to elaborate on my mental capacity, but from where I stand his complicated work appears to be limited to the ability to follow compilation instructions.
I don't claim he wanted that to be a scam from the very beginning - he might have had a will to do something and learn along the way (which would be an adequate way), but he chose to cheat where stuff got unmanageable.
While I still encourage everybody to take up the challenge to see how fun it is, but when such a "dev" is leaving XDA we couldn't be worried less. Bon voyage!
Does it take lot of time to boot up? Its showing [ 915.19111] CP L2->L0 and the process is being continued... Cant use power button.
So where does this stand? This is the one OS I want to use more than any other. I dont know jack about compiling code and such. But if someone has this for a N4 I would be all over it like ants on a peach.
This looks cool, I hope this thread doesn't die, I would really like to try Tizen on my nexus
Ubuntu touch is still unusable, but a tizen port could be quite stable, once properly ported
What is the progress of this project?
SuperBoUDS said:
What is the progress of this project?
Click to expand...
Click to collapse
Looks pretty dead. I keep coming back to check if I can get tizen on my s3
Sent from my GT-I9300 using xda app-developers app
...I keep coming back to check if I can get tizen on my s3
Click to expand...
Click to collapse
This is also my question... if S3 is able to use available Tizen Firmware... from testdevices...
Maybe someone can find solution to use Tizen on S3.
Thanx in advance.
Best Regards
adfree said:
This is also my question... if S3 is able to use available Tizen Firmware... from testdevices...
Maybe someone can find solution to use Tizen on S3.
Thanx in advance.
Best Regards
Click to expand...
Click to collapse
I have asked in s3 thread. My post got deleted after a few comments... I was hoping a port for s3 would be easy and quick but there's no development on this whatsoever
Sent from my GT-I9300 using xda app-developers app

[Q] Hardware Wifi Failure?

Hello, I was given a Gtablet by a friend. Everything is in proper working order except for the wifi. The wifi will endlessly scan, never pulling up any SSIDs. Here's what I've done to troubleshoot:
Ascertained flight mode was off (it was)
Enabled wifi through the developer options (Did nothing)
Manually enter SSID/Security information (Claims that SSID is not in range)
Reloaded the OS (He had VEGAn Tab on there. I reloaded the 5.1 Beta. I don't know what version he had on there, oops.)
After a clean install I have the exact same issue, which leads me to believe it is a hardware issue rather than a software issue. Is this common? Am I forgetting something? Would loading an entirely different ROM be of any use or do they also use the same driver?
My apologies if this has been answered previously, but in all my searching I can only find people who have this problem temporarily; a reboot fixes it for them. I haven't been able to find someone who has had this as a persistent issue.
JungleWallace said:
Hello, I was given a Gtablet by a friend. Everything is in proper working order except for the wifi. The wifi will endlessly scan, never pulling up any SSIDs.
Click to expand...
Click to collapse
I'll have to look at some logs to ascertain what your WiFi problem is.
Run the commands in this post (after rebooting the tablet) and then post the text files that're created.
rajeevvp said:
I'll have to look at some logs to ascertain what your WiFi problem is.
Click to expand...
Click to collapse
Thanks, see attached are the logs as per request. As a side note, now that I have the terminal emulator on there I tried a few commands I dug up on the internet after I looked over the logs.
Code:
$ su
# ifconfig tiwlan0 up
# ifconfig eth0 up
Both gave an error message
Code:
error: SIOCGIFFLAGS (No such device)
Also
Code:
# svc wifi enable
did not solve my issues. Oh well.
FYI:
JungleWallace said:
...I tried a few commands I dug up on the internet after I looked over the logs.
Code:
$ su
# ifconfig tiwlan0 up
# ifconfig eth0 up
Both gave an error message
Code:
error: SIOCGIFFLAGS (No such device)
Click to expand...
Click to collapse
The wireless LAN interface name on the gTab is wlan0. Hence your error messages: "No such device" for the ifnames tiwlan0 and eth0. (The latter would work for the ethernet I/F on the dock--if you had one connected.)
Also
Code:
# svc wifi enable
did not solve my issues. Oh well.
Click to expand...
Click to collapse
1. You have to look at the Android system logs (using logcat) to see the result of that svc command.
2. Your Android logs indicate that your WiFi interface is a) disabled at startup and b) then not enabled thereafter:
Code:
01-07 23:21:10.429 V/ConnectivityService( 990): Starting Wifi Service.
01-07 23:21:10.429 I/WifiService( 990): WifiService starting up with Wi-Fi [B]disabled[/B]
Suggestions:
Since this now looks like a ROM problem (ie. not HW):
1. See this thread. Run the script to disable Airplane Mode which might be causing your problem. If that doesn't work, try step 2:
2. Boot into CWM and then a) Format /cache and b) Repartition the Internal SD card (take the external one out first).
You'll lose all your current apps and data with this step, essentially reverting to a "fresh" install of your ROM.
Re-setup WiFi, time & date and other things again.
If step 2. doesn't work, report back next year, and I'll give you more commands to run then.
rajeevvp said:
If step 2. doesn't work, report back next year, and I'll give you more commands to run then.
Click to expand...
Click to collapse
Negative. Ran the airplane fix script, nothing. Reset cache/re-partitioned, still nothing. It's still endlessly scanning/shutting off/scanning.
JungleWallace said:
Negative. Ran the airplane fix script, nothing. Reset cache/re-partitioned, still nothing.
Click to expand...
Click to collapse
OK. Not one of the common simple problems, then.
It's still endlessly scanning/shutting off/scanning.
Click to expand...
Click to collapse
This is puzzling because from your last logs, it doesn't look like the wlan kernel driver was even loaded, so no AP scanning should be possible. A little background will clarify what I mean.
On all the 2.6.32.x kernels for the gTablet, the wlan driver is not compiled into the kernel. Instead, it is built as a separate kernel module which is loaded and unloaded as needed by Android (from the files in /system/lib/hw/wlan/). When the wlan driver is loaded both the kernel (dmesg) and Android (logcat) will show some characteristic messages and until the driver is inserted into the kernel no AP scanning, or other wireless functions, should be possible. And, no wlan driver-related messages in your logs tells me that the driver was likely not loaded. (Also, only after the wlan driver is loaded does it check and initialize the wireless HW. So, only after its been loaded, strictly speaking, can we rule out a HW problem.)
Sometimes the Android logs are not complete, so I want to you setup ADB on your PC, enable USB debugging on the gTablet (Setting > Applications > Development) and collect the Android logs like this from now on:
1. Power off gTab; attach the USB cable to it.
2. Open a CMD.exe window on the PC, then run this command (and keep the window minimized):
Code:
C:\> [B]adb logcat -v time > logcat.txt[/B]
After all the tests/commands have been done, restore this window and press Ctrl-C to kill ADB and terminate Android log collection.
3. Power on the gTablet. The ADB command will wait for the gTablet and keep collecting logs on the PC.
Post also the output of these commands:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
C:\> [B]adb shell lsmod > lsmod.txt[/B]
C:\> [B]adb shell "cd /; find system -type f -print0 | xargs -0 sha1sum" > sha1sum.txt[/B]
Is this the ROM you currently have?
Have you applied the VEGAn 1.00 beta 5.1.1 supplement also?
rajeevvp said:
OK. Not one of the common simple problems, then.
.........
Is this the ROM you currently have?
Have you applied the VEGAn 1.00 beta 5.1.1 supplement also?
Click to expand...
Click to collapse
That was the current ROM I was using. I had not applied the supplement yet, but now I have. Still the same issue. Here are the logs.
JungleWallace said:
That was the current ROM I was using. I had not applied the supplement yet, but now I have. Still the same issue. Here are the logs.
Click to expand...
Click to collapse
In this one I can see the kernel WiFi driver being loaded, and the driver is not reporting any HW chip, SDIO bus, or other errors:
Code:
<4>[ 23.485281] sdio_reset_comm():
<4>[ 23.503617] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 23.676913] Firmware version = wl0: May 17 2010 22:38:50 version 4.218.223.1
<4>[ 23.887647] wlan0: Broadcom Dongle Host Driver mac=e0:2a:82:08:3e:81
<4>[ 23.894047] Enter wl_control_wl_start
<4>[ 23.897864] Exited wl_control_wl_start
<4>[ 23.907103]
<4>[ 23.907109] Dongle Host Driver, version 4.218.223.1
As far as the kernel driver is concrned, everything looks OK, but the Android logs still don't show any SSID associations.
What're the exact outputs of these commands? (You can post a screenshot. Mask the psk= value from the 1st output, if present)
Code:
C:\> [B]adb shell "fgrep -v '#' /data/misc/wifi/wpa_supplicant.conf | tr -s '\n'"[/B]
ctrl_interface=wlan0
update_config=1
...
C:\> [B]adb shell wpa_cli -i wlan0 driver rssi[/B]
...
C:\> [B]adb shell wpa_cli -i wlan0 driver linkspeed[/B]
LinkSpeed [I]nn[/I]
C:\> [B]adb shell wpa_cli -i wlan0 scan[/B]
OK
C:\> [B]adb shell wpa_cli -i wlan0 scan_results[/B]
bssid / frequency / signal level / flags / ssid
aa:bb:cc:dd:ee:ff 2452 185 [WPA2-PSK-CCMP] [I]YourSSID[/I]
Collect also the dmesg and logcat outputs as before.
[/FONT]
rajeevvp said:
What're the exact outputs of these commands? (You can post a screenshot. Mask the psk= value from the 1st output, if present) [...] Collect also the dmesg and logcat outputs as before.
Click to expand...
Click to collapse
See attached. Ignore my syntax errors that I underlined. I was typing wlan instead of wlan0.
JungleWallace said:
Ignore my syntax errors that I underlined. I was typing wlan instead of wlan0.
Click to expand...
Click to collapse
Those are OK since you've corrected them. But, these commands you'll have to redo:
1. In the first command (fgrep ... | tr), you've typed a '/' (forward slash) instead of what I've given in the example, which is a '\' (back-slash) character.
The correct character will remove all those blank lines. But, this is a minor typo compared to:
2. The last 2 commands (wpa_cli scan* ...), which you'll have to redo. This time without the extraneous driver argument (again, see the example)--which turns it into a completely different (and non-existent) command. This is why the output doesn't look like what I've shown.
Instead of typing the commands in manually, select and copy the command lines from the browser and paste them into the shell window.
You might also want to increase the no. of columns that CMD.exe displays: Right-click on the title-bar; choose Properties; select Layout; increase the no. of Columns to, let's say, 150.
3. That dmesg.txt file is not very useful because you've not rebooted the tablet before issuing that command.
The kernel has a fixed-size message buffer, so all the HW initialization messages printed only at system boot will be overwritten by later, and irrelevent, messages as time passes. From the timestamps, it looks like your tablet's been on for a couple of weeks, at least--I can't see any of the earlier boot-up messages.

[Q] How to fix edit of platform.xml gone wrong on Note3 SM-N9005?

I did a search and have found similar threads. However, people seem to have been intelligent and back up stuff or installed recovery apps before screwing around with their phones. I did not.
I have a Samsung Note3. Kit Kat 4.4.2 installed OTA once I had it up and running. I rooted it. However, the version of Kit-kat has a famous issue in that it would not allow apps to write to the SD card. I found a site with manual instructions to edit the platform.xml to overcome this issue. The site is as below:
winaero.com/blog/unlock-external-sd-card-writing-for-all-apps-in-android-4-4-kitkat/
However, something went awry after rebooting. I could not see anything on my SD card and I was unable to edit the platform.xml. A solution seemed to be to flash the ROM (using ODIN 3.07). I did this and currently have Baseband version N9005XXUENB1 and Build Number KOT49H.N9005XXUENB7
However, the still has lots of issues. I can stick in a password on wifi and connect to the network but it does not actually communicate with the internet. The H with up and down arrows appears for 3g connectivitiy but also does not work. Bluetooth does not work. Youtube has stopped working errors are common. I am unable to install any apps as cannot use play store, etc. I have pictures and mp3s on my SD card but gallery comes up empty as does music app. The only "file explorer" I seem to have is "my files" app. It comes up as empty (although it shows Total storage available for both SD memory and device storage as using 25/32 and 22/29 respectively.
I am guessing that flashing the ROM did not remedy the corrupt platform.xml in the permissions folder. I think the folder path was etc/permission/platform.xml although am not an expert with android. I was hoping someone might be able to give me a solution to fix the issue. Preferably a completely fresh and clean wipe type solution. Although as I am a "newbie" the greater the simplicity of the solution the better.
Apologies for the length of this issue!
T
laconical said:
I did a search and have found similar threads. However, people seem to have been intelligent and back up stuff or installed recovery apps before screwing around with their phones. I did not.
I have a Samsung Note3. Kit Kat 4.4.2 installed OTA once I had it up and running. I rooted it. However, the version of Kit-kat has a famous issue in that it would not allow apps to write to the SD card. I found a site with manual instructions to edit the platform.xml to overcome this issue. The site is as below:
winaero.com/blog/unlock-external-sd-card-writing-for-all-apps-in-android-4-4-kitkat/
However, something went awry after rebooting. I could not see anything on my SD card and I was unable to edit the platform.xml. A solution seemed to be to flash the ROM (using ODIN 3.07). I did this and currently have Baseband version N9005XXUENB1 and Build Number KOT49H.N9005XXUENB7
However, the still has lots of issues. I can stick in a password on wifi and connect to the network but it does not actually communicate with the internet. The H with up and down arrows appears for 3g connectivitiy but also does not work. Bluetooth does not work. Youtube has stopped working errors are common. I am unable to install any apps as cannot use play store, etc. I have pictures and mp3s on my SD card but gallery comes up empty as does music app. The only "file explorer" I seem to have is "my files" app. It comes up as empty (although it shows Total storage available for both SD memory and device storage as using 25/32 and 22/29 respectively.
I am guessing that flashing the ROM did not remedy the corrupt platform.xml in the permissions folder. I think the folder path was etc/permission/platform.xml although am not an expert with android. I was hoping someone might be able to give me a solution to fix the issue. Preferably a completely fresh and clean wipe type solution. Although as I am a "newbie" the greater the simplicity of the solution the better.
Apologies for the length of this issue!
T
Click to expand...
Click to collapse
Sounds like a bit of a pickle. Since you know that Odin is working and the firmware you have at least flashes correctly, I'd consider installing a custom recovery, backing up EFS folder (and the rom too, just in case there is some weird issue with Odin the 2nd time around) , then wipe everything - /system included. This will make your phone not be able to boot up at all because it will wipe the OS off. Then just boot directly to Download and redo the firmware flash. Something else to consider since you do have the international version, is that some of the firmwares you install might be more carrier or region specific, so there might be a better option to install. I know that there is a some slightly newer version that has NC2 in it as I was trying to fix one of these phones the other day that could not register on any network and ran across that build. Do you remember the build number of the software before you started modding?
Hello. Thanks for the reply.
I am going to ask what are probably very obvious questions but I am a little out of my depth.
1) What does installing a custom recovery involve?
2)How would I backup the EFS directory? When I had ES file explorer I would have been able to try and find it. However, as it is I do not know how to find the directory and back it up. I have connected the phone to a windows laptop and it shows up as note3 but there are no folders or files visible in either the phone or on the card.
3) What is the procedure to "wipe everything"?
I think the final part I know how to do with ODIN. Just go to download boot and load and run odin with the ROM.
I got the BTU ROM is that not for the UK? I tried looking up what NC2 was but did not really find anything the explained what it is.
Thanks again and sorry for the ignorance on my side.
Let's put the custom recovery and all that on the back burner for now.
Was your phone unlocked from the factory or did you get it from a carrier? If from a carrier, which, and is it unlocked now or you are still using it with the original carrier? This one is for Vodaphone http://www.sammobile.com/firmwares/3/?download=27401 but if you are unlocked, it should work anyway, I believe.
Thanks to the people for their replies. I managed to solve the issue as below.
As mentioned previously I had flashed using ODIN and BTU version of N9005XXUENB7. The only other thing that was then required was to enter the recovery (I think power + volume up + home and then release power once samsung name appears). I then selected wipe data/factory. A reboot later and everything was solved.
es0tericcha0s said:
Sounds like a bit of a pickle. Since you know that Odin is working and the firmware you have at least flashes correctly, I'd consider installing a custom recovery, backing up EFS folder (and the rom too, just in case there is some weird issue with Odin the 2nd time around) , then wipe everything - /system included. This will make your phone not be able to boot up at all because it will wipe the OS off. Then just boot directly to Download and redo the firmware flash. Something else to consider since you do have the international version, is that some of the firmwares you install might be more carrier or region specific, so there might be a better option to install. I know that there is a some slightly newer version that has NC2 in it as I was trying to fix one of these phones the other day that could not register on any network and ran across that build. Do you remember the build number of the software before you started modding?
Click to expand...
Click to collapse
Hi, The other day i tried to fix the Platform.xml. on my S5. i noticed sometime after that when i move files using the "My files" app, the phone would not refresh the files so that they would show up in gallery, videos etc.. I tried to undo the Media_rw by using SD Maid to find the Platform.xml and Axel to rewrite the Xml. In the platform.xml. i deleted the Media_rw and replaced the old xml with the old (original) one. I rebooted my phone. On swiping to open the screen i noticed alot of apps crashing one after the other. I when back to SD Maid and searched for Platform.xml and opened it with Axel but it said file not found.. i can not use the internet, i cant use most apps, i cant even use the Kies on my computer. I cant save anything to the storage either. I really need help. Odin is the only thing i can use. but i dont know how i can reset the xml files on my phone.. What exactly am i do to?
please
christaph3r said:
Hi, The other day i tried to fix the Platform.xml. on my S5. i noticed sometime after that when i move files using the "My files" app, the phone would not refresh the files so that they would show up in gallery, videos etc.. I tried to undo the Media_rw by using SD Maid to find the Platform.xml and Axel to rewrite the Xml. In the platform.xml. i deleted the Media_rw and replaced the old xml with the old (original) one. I rebooted my phone. On swiping to open the screen i noticed alot of apps crashing one after the other. I when back to SD Maid and searched for Platform.xml and opened it with Axel but it said file not found.. i can not use the internet, i cant use most apps, i cant even use the Kies on my computer. I cant save anything to the storage either. I really need help. Odin is the only thing i can use. but i dont know how i can reset the xml files on my phone.. What exactly am i do to?
please
Click to expand...
Click to collapse
Hey, I was wondering if you ever got a fix on this without factory reset. I am having the exact same issue.
Same boat here. Please someone help!
woahs said:
Hey, I was wondering if you ever got a fix on this without factory reset. I am having the exact same issue.
Click to expand...
Click to collapse
I am having exact same problem. After editing the platform.xml, my Note 3 is behaving the same way: no access to any storage area (including USB drive), no remote access/online access (even though WIFI and 4G appear to connect just fine), most apps fail with 'Unfortunately ... has stopped' error message, no Google Play...
I really don't want to do a factory reset, but really, does it even help? Is there a way to put the platform.xml back? Is there a way to access the phone via USB cable?
vbcomer said:
I am having exact same problem. After editing the platform.xml, my Note 3 is behaving the same way: no access to any storage area (including USB drive), no remote access/online access (even though WIFI and 4G appear to connect just fine), most apps fail with 'Unfortunately ... has stopped' error message, no Google Play...
I really don't want to do a factory reset, but really, does it even help? Is there a way to put the platform.xml back? Is there a way to access the phone via USB cable?
Click to expand...
Click to collapse
Update: I went ahead and successfully install the all-in-one file to the phone via Odin, but it still has the same issues. Can someone give a hint? thanks
FIX!!!
Hi I'm a god at searching(hence the Go)but an Noob(hence the obie) to Dev on Android but a computer techy(in other words I fix computers upgrade ETC.) Now if you followed EXACT instructions you SHOULD have the Backup copy of platform.xml. If not reply and I'll give those instructions.
So I did the same as this post did to get my issue as well but there's a SOLUTION I just found W/o getting rid of your loved files and its easy!
1. Download the ADB also included in The Android SDK by Google (approx. 3XX MB)
2. DOWNLOAD Root Explorer.APK
3. Extract ADB Dev kit( name should be roughly adt-bundle-windows-x86_64-20140702.zip)Note: I prefered it at C:\Android it avoided Name too long error
4. Open CMD Type: cd C:\<location ADB was extracted>\sdk\platform-tools(if you followed my note it will be "C:\Android\adt-bundle-windows-x86_64-20140702\sdk\platform-tools") and press enter... HINT TO COPY PASTE IN CMD RIGHT CLICK SAVES TIME!!!!
5. Install Root Explorer so you can backup your files(if any) I was unlucky having none on the phone but SD storage is ok!
To do this type ADB INSTALL <Location of Root explorer.exe> For standard windows users with default download locations it would be "C:\Users\<USER NAME>\Downloads\Root Explorer v3.1.9.apk" <COPY PASTE
6. Copy the original back to System>ETC>Permissions and overwrite
7. Factory reset!
Links?
sorry guys bt i have the same note 3 and i delete the platform.xml file .....i did a factory reset bt nothing happened ...can u help plz
Re:FIX!
But you have to set the permissions of platform.xml as 0777.Right?
Step 5 how should it works
Android Goobie said:
Hi I'm a god at searching(hence the Go)but an Noob(hence the obie) to Dev on Android but a computer techy(in other words I fix computers upgrade ETC.) Now if you followed EXACT instructions you SHOULD have the Backup copy of platform.xml. If not reply and I'll give those instructions.
So I did the same as this post did to get my issue as well but there's a SOLUTION I just found W/o getting rid of your loved files and its easy!
1. Download the ADB also included in The Android SDK by Google (approx. 3XX MB)
2. DOWNLOAD Root Explorer.APK
3. Extract ADB Dev kit( name should be roughly adt-bundle-windows-x86_64-20140702.zip)Note: I prefered it at C:\Android it avoided Name too long error
4. Open CMD Type: cd C:\<location ADB was extracted>\sdk\platform-tools(if you followed my note it will be "C:\Android\adt-bundle-windows-x86_64-20140702\sdk\platform-tools") and press enter... HINT TO COPY PASTE IN CMD RIGHT CLICK SAVES TIME!!!!
5. Install Root Explorer so you can backup your files(if any) I was unlucky having none on the phone but SD storage is ok!
To do this type ADB INSTALL <Location of Root explorer.exe> For standard windows users with default download locations it would be "C:\Users\<USER NAME>\Downloads\Root Explorer v3.1.9.apk" <COPY PASTE
6. Copy the original back to System>ETC>Permissions and overwrite
7. Factory reset!
Links?
Click to expand...
Click to collapse
Hi have next message in the install root step could you help me please
Android Debug Bridge version 1.0.31
-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 r
unning.
-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 [-p] <local> <remote>
- copy file/dir to device
('-p' to display the transfer progress)
adb pull [-p] [-a] <remote> [<local>]
- copy file/dir from device
('-p' to display the transfer progress)
('-a' means copy timestamp and mode) 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 followin
g 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] [-d] [-s] [--algo <algorithm name> --key <hex-encoded ke
y> --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)
('-d' means allow version code downgrade)
('-s' means install on SD card instead of inter
nal 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 specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader 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.

Ubuntu Touch for Moto G5

--- This is not made by me. This is an repost to XDA. ---
This is 32-bit, so you can use offical TWRP.
Made by hacker12455 and Lukapanio
Bugs:
Camera and minor bugs
Installation:
(Requires ADB + Fastboot, Linux on the PC and Git)
1. Format the data partition with ext4 (Format != Wipe)
2. Download the latest halium-boot.img from https://sourceforge.net/projects/ubports-cedric/files
3. Run
Code:
fastboot flash boot halium-boot.img
4. Download the latest ubports-touch.rootfs-xenial-armhf.tar.gz from https://ci.ubports.com/job/xenial-rootfs-armhf/
5. Download the latest system.img from https://sourceforge.net/projects/ubports-cedric/files
6. Clone https://gitlab.com/JBBgameich/halium-install git repository and go into that folder
7. Run
Code:
./halium-install -v -p ut path/to/ubports-touch.rootfs-xenial-armhf.tar.gz path/to/system.img
8. Reboot your phone.
9. Run
Code:
dmesg -w
and look for an GNU/Linux device.
10. Connect your computer to the RNDIS network that appeared when you rebooted your phone. (If not already happened.)
11. SSH onto the device:
Code:
ssh [email protected]
12. Follow that guide: http://docs.ubports.com/en/latest/porting/running-ut.html
You made it!
Source: https://github.com/ubports-on-cedric
Download: http://ubports-cedric.sf.net
Fail, ignore
Screenshots!
Note: Visual glitch already fixed, old screenshots.
About this device is coming soon.
Nice, i will try it tomorrow
[censored because imei leak, looking for new screenshot]
@nift4 the broken things are fixable?
lucki1000 said:
@nift4 the broken things are fixable?
Click to expand...
Click to collapse
Sound yes
Why authors are redacted?
nift4 said:
Why authors are redacted?
Click to expand...
Click to collapse
Follow the xda rules - telegram is not allowed on xda nor is the promotion of any other social media
XDA is a place for discussion and building of android projects - if everyone went to telegram the forums would be empty
I'd advise you remove all references to telegram
Done
EDIT: I did not want to break the rules I simply did not made it
Ok, I:
- Flashed the boot image from fastboot mode
- Booted into TWRP because the halium-install script tried to use ADB (there's no ADB in fastboot mode!)
- image flashed, i rebooted and the RNDIS appeared with
Code:
sudo dmesg -w
but ssh connection is refused on port 22, and when I connected with telnet the commands from the last guide (had to use the Wayback Machine, since the actual page doesn't exist anymore) but
Code:
/ # cat /var/lib/lxc/android/rootfs/ueventd*.rc|grep ^/dev|sed -e 's/^\/dev\///'|awk '{
printf "ACTION==\"add\", KERNEL==\"%s\", OWNER=\"%s\", GROUP=\"%s\", MODE=\"%s\"\n",$1,
$3,$4,$2}' | sed -e 's/\r//' >/usr/lib/lxc-android-config/70-cedric.rules
cat: can't open '/var/lib/lxc/android/rootfs/ueventd*.rc': No such file or directory
/bin/sh: can't create /usr/lib/lxc-android-config/70-cedric.rules: nonexistent directory
/ #
So, what am I doing wrong? Is there a more recent version?

Categories

Resources