Develop Bugs

[ADDON][Xperia S] Generic startup/init.d scripts support for Stock ROM/Kernel

[ info ]
i am attaching a easy to run package which contains the files required for full functionality of executing startup scripts (init.d scripts)...
basically this will allow the user to execute custom shell scripts, placed in /system/etc/init.d/ folder and they will be executed on each boot!
i dont have this device yet!!
thanks to Jozinek for testing this on his phone!
[ requirements ]
stock rooted ROM
windows PC with adb drivers installed
[ how to install ]
download the provided zip package
save it on c:\
extract the contents of the package
connect phone with usb debugging active to PC via ADB
execute "runme.bat"
follow onscreen instructions & enjoy!
incase some issue is there post the output/log of script
[ additional info ]
i have added the following things in the package:
corrected /system/bin/sysint file
run-parts binary in /system/xbin/run-parts (which is basically busybox 1.19.3 binary)
correct /system/etc/install-recovery.sh file (this file gets executed by default on stock kernel too!)
test/example script /system/etc/init.d/99test
to check if this is working the test script (99test) will create a temporary file /data/local/tmp/init.d_log_test.txt on each boot
[ donations/device fund ]
i dont yet have this device but i plan to buy it.... if u guys want to donate to me to get this device OR if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
i am currently channeling all my donations to get this phone asap and to avoid selling my ARC!!!
PAYPAL DONATION LINK
[ download link ]
generic-init.d-support-v01.zip
MD5HASH: 2eda273af4b91c34f868807820cceaee
let me know how it goes!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ENJOY!

Nice work, this will enable the Speedy v7 int.d hacks, can you incorporate this in the above? As an addon perhaps.
Done, $50 "AU" dollars coming your way mate.
-smc

somemadcaaant said:
Nice work, this will enable the Speedy v7 int.d hacks, can you incorporate this in the above? As an addon perhaps.
Done, $50 "AU" dollars coming your way mate.
-smc
Click to expand...
Click to collapse
this init.d support can be used to execute ANY shell script/program at startup... u are free to choose the ones u want...
if anyone needs help on how to push the scripts onto device let me know... but script specific info i dont have, u will need to ask the developer of those scripts..

I used this script to move dalvik cache to /cache folder:
Code:
#!/system/bin/sh
#
# relocate dalvik-cache to /cache/dalvik-cache
if [ ! -d /cache/dalvik-cache ]
then
busybox rm -rf /cache/dalvik-cache /data/dalvik-cache
mkdir /cache/dalvik-cache /data/dalvik-cache
fi
busybox chown 1000:1000 /cache/dalvik-cache
busybox chmod 0771 /cache/dalvik-cache
# create symlink
busybox mount -o bind /cache/dalvik-cache /data/dalvik-cache
busybox chown 1000:1000 /data/dalvik-cache
busybox chmod 0771 /data/dalvik-cache
After reboot i saw folder /cache-dalvid in both folders /data and /cache, is it normal?
Thank!

I found that for devices rooted with locked bootloader
Line 21 of runme.bat need to change from
HTML:
@files\adb shell "su -c 'busybox mount -t ext4 -o rw,remount /system /system'"
to
HTML:
@files\adb shell "su -c 'busybox mount -o remount,rw /system'"

This is all great, exactly what I was looking for! But what about if the ROM already has a custom kernel that makes use of /etc/init.d? Do the /etc/init.d scripts get executed twice?
EDIT: in my phone this solution can't work. In the init.rc file the following lines are commented out
Code:
#service flash_recovery /system/etc/install-recovery.sh
# oneshot

Thanks, it's working but I have a question, how we can include this in a rom?
Please respond, I would appreciate that

DooMLoRD said:
run-parts binary in /system/xbin/run-parts (which is basically busybox 1.19.3 binary)
Click to expand...
Click to collapse
That means I don't need run-parts if I've busybox installed?

1-Tell me please if I understand: I've done everything the post says Doomlord ([ADDON] [Xperia S] Generic startup /init.d scripts support for Stock ROM / Kernel) my question is this, after this I can already install scripts from cwm?
2-I try installing ''NullVoid'' tweaK by cmw and apparently well was installed. (I say apparently because i do not know if it is working)
3-Another thing about Tweaks: These have to be installed every time the phone restarts? This tweaks are compatible with the stock ics rom? (With the Doomloard Method ?

DooMLoRD said:
........
[ additional info ]
i have added the following things in the package:
corrected /system/bin/sysint file
run-parts binary in /system/xbin/run-parts (which is basically busybox 1.19.3 binary)
correct /system/etc/install-recovery.sh file (this file gets executed by default on stock kernel too!)
test/example script /system/etc/init.d/99test
to check if this is working the test script (99test) will create a temporary file /data/local/tmp/init.d_log_test.txt on each boot
..........
Click to expand...
Click to collapse
So the "install-recovery.sh" file is executed by system by default and does not need to be executed manually from terminal or what else?
And about the file...that is not a one-run file...right? It is executed at every phone boot...right??
Thank you.
Sent from my GT-I9000 using xda app-developers app

AW: [ADDON][Xperia S] Generic startup/init.d scripts support for Stock ROM/Kernel
Sorry leaving footprint, to see this again after im home.
Gesendet von meinem LT26i mit Tapatalk 2

Hello,
Is this package valid for deodexed rom?
I'm on stock .55, bootloader locked.
Currently the folder /system/etc/init.d doesn't exists
Thank you

marvasten said:
Hello,
Is this package valid for deodexed rom?
I'm on stock .55, bootloader locked.
Currently the folder /system/etc/init.d doesn't exists
Thank you
Click to expand...
Click to collapse
it doesnt matter which ROM you are on... this should work on any ROM as long as the kernel ramdisk executes install-recovery.sh service...
dont worry it creates all required folders/files

Root on 4.3 dev discussion

Edit 2:
Kernels with recoveries:
Unlocked bootloader required for any of these:
CWM by @lzyllp http://forum.xda-developers.com/showpost.php?p=48599313&postcount=48
TWRP by @Desperanto86 http://forum.xda-developers.com/showpost.php?p=48600227&postcount=60
Philz by me: http://mohammadag.xceleo.org/public/Android/XperiaZ1/Philz_4.3_kernel.img
These kernels have Sony RIC disabled at boot, so /system is always writable.
After flashing with fastboot flash boot filename.img, boot intro recovery and flash this:
SuperSU zip http://download.chainfire.eu/supersu
Edit: Discussion moot, root works fine as per below
Proof: Xperia Flip Settings on 4.3:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As most of you know, rooting 4.3 isn't fully possible. While su and Superuser.apk can be installed through recovery, /system can't be mounted.
Code:
[email protected]:/ # mount -o rw,remount /system
mount: Operation not permitted
A fix for that is to disable Sony's RIC kernel implementation.
Code:
[email protected]:/system # echo 0 > /sys/kernel/security/sony_ric/enable
[email protected]:/system # mount -o rw,remount /system
[email protected]:/system #
This is enabled on boot in init.sony-platform.rc:
Code:
# Enable Sony RIC
mount securityfs securityfs /sys/kernel/security nosuid nodev noexec
write /sys/kernel/security/sony_ric/enable 1
After all this is done, /system is writable:
Code:
[email protected]:/system # echo 123 > test
[email protected]:/system # cat test
123
However, I still can't figure out why Xposed won't install, which is making me wonder if this all worked or not.
Edit: Xposed works fine as per http://forum.xda-developers.com/showpost.php?p=48484642&postcount=6846
Xposed installs fine, it just doesn't work:
Code:
[email protected]:~/Downloads$ adb -d logcat | grep Xposed
D/Xposed ( 355): Starting Xposed binary version 47, compiled for SDK 16
D/Xposed ( 355): Phone: C6903 (Sony), Android version 4.3 (SDK 18)
D/Xposed ( 355): ROM: 14.2.A.0.290
I/Xposed ( 355): -----------------
I/Xposed ( 355): Found new Xposed jar version, activating it
I/Xposed ( 355): Added Xposed (/data/data/de.robv.android.xposed.installer/bin/XposedBridge.jar) to CLASSPATH.
D/AndroidRuntime( 355): >>>>>> AndroidRuntime START de.robv.android.xposed.XposedBridge <<<<<<
D/Xposed ( 355): Using structure member offsets for mode WITH_JIT
I/Xposed ( 355): Found Xposed class 'de/robv/android/xposed/XposedBridge', now initializing
I/Xposed ( 355): -----------------
I/Xposed ( 355): Dec 17, 2013 5:01:53 PM UTC
I/Xposed ( 355): Loading Xposed v42 (for Zygote)...
I/Xposed ( 355): Errors during Xposed initialization
I/Xposed ( 355): java.lang.NoSuchMethodError: android.app.ActivityThread#getTopLevelResources(java.lang.String,int,android.content.res.Configuration,android.content.res.CompatibilityInfo)#exact

Hi !
I have Xposed install when i was on 4.2 but lost root since update to 4.3
Can you detail how you get root acces step by step ?
You lost me at RIC Kernel...
Thanks !

TeamR said:
Hi !
I have Xposed install when i was on 4.2 but lost root since update to 4.3
Can you detail how you get root acces step by step ?
You lost me at RIC Kernel...
Thanks !
Click to expand...
Click to collapse
This is only useful to devs right now, someone needs to add a startup script that echos 0 into the sysfile above into some ROM.
Basically, you'll need an unlocked BL to install SuperSU, then issue the command above to make /system writable. A custom ROM can do that in some init script, since the file above is in ramdisk (which is part of kernel package). When that's done, installing Xposed will be as simple as tapping Install.

Please send me the kernel file after all those modifications. Thanks in advance.

MohammadAG said:
This is only useful to devs right now, someone needs to add a startup script that echos 0 into the sysfile above into some ROM.
Basically, you'll need an unlocked BL to install SuperSU, then issue the command above to make /system writable. A custom ROM can do that in some init script, since the file above is in ramdisk (which is part of kernel package). When that's done, installing Xposed will be as simple as tapping Install.
Click to expand...
Click to collapse
You can just execute the commands from terminal emulator and then add a script to init.rc... I try now and if it works i give you a flashable .zip

Understand !
But i'm not a good dev !
In fact, if i want root, i can unlock my bootloader since camera was not broken any more, then install a recovery and flash Supersu...
Was right or did i make a mistake ?

See, I told you @DooMLoRD, it is the ric again... But now they moved it into the kernel
Will setting that sys control to 0 work on locked bootloader as well?

TeamR said:
Understand !
But i'm not a good dev !
In fact, if i want root, i can unlock my bootloader since camera was not broken any more, then install a recovery and flash Supersu...
Was right or did i make a mistake ?
Click to expand...
Click to collapse
How do you install recovery without root?

gregbradley said:
How do you install recovery without root?
Click to expand...
Click to collapse
True ! Ok, one facepalm for me
So i'll be waiting for DooMLoorD Kernel update...
And maybe it will include a port of his double tap feature from xperia z !

gregbradley said:
How do you install recovery without root?
Click to expand...
Click to collapse
From kernel, if is UB...

CappyT said:
From kernel, if is UB...
Click to expand...
Click to collapse
Are you sure...still waiting to see this stock kernel with recovery working...

gregbradley said:
Are you sure...still waiting to see this stock kernel with recovery working...
Click to expand...
Click to collapse
Well, I don't know if is simple as modding the stock one and adding recovery and root... On other devices it works like that...
I just wait for a boot.img to flash and I unlock the BL, since i have the TA backup...

CappyT said:
Well, I don't know if is simple as modding the stock one and adding recovery and root... On other devices it works like that...
I just wait for a boot.img to flash and I unlock the BL, since i have the TA backup...
Click to expand...
Click to collapse
That has been the issue
changing ro.secure=1 to ro.secure=0 has caused kernel failure at boot...

When i try this on LB with adb shell
Code:
[email protected]:/system # echo 0 > /sys/kernel/security/sony_ric/enable
[email protected]:/system # mount -o rw,remount /system
[email protected]:/system #
It tells me permission denied...

[Fenix] said:
When i try this on LB with adb shell
Code:
[email protected]:/system # echo 0 > /sys/kernel/security/sony_ric/enable
[email protected]:/system # mount -o rw,remount /system
[email protected]:/system #
It tells me permission denied...
Click to expand...
Click to collapse
Because you cannot write the kernel partition without Unlocked Bootloader (at least, I think)
gregbradley said:
That has been the issue
changing ro.secure=1 to ro.secure=0 has caused kernel failure at boot...
Click to expand...
Click to collapse
Well, that's not good... It happens only on stock kernel?

CappyT said:
Because you cannot write the kernel partition without Unlocked Bootloader (at least, I think)
Well, that's not good... It happens only on stock kernel?
Click to expand...
Click to collapse
Yes i think the same bro...thanks for the trick anyway :thumbup:
Inviato dal mio C6903 utilizzando Tapatalk

[Fenix] said:
Yes i think the same bro...thanks for the trick anyway :thumbup:
Inviato dal mio C6903 utilizzando Tapatalk
Click to expand...
Click to collapse
The thing i ask, going a bit OT is: how did you manage to install 4.3 with root? Because I can try to unlock BL (i have a TA backup) and try it to confirm this thing.

I'd rather @lzyllp shares the image instead of me, I didn't ask if I could share it, and I asked for it over PM.
Anyway, here's an image I made with Philz recovery, DO NOT FLASH THIS, it won't boot.
However, using it with fastboot boot file.img works, I have no idea why.
http://mohammadag.xceleo.org/public/Android/XperiaZ1/DO_NOT_FLASH_BOOT_ONLY.img

EDIT: found. Is on /

DAddYE said:
Awesome! Thanks, where is init.sony-platform.rc? Is it safe to disable RIC on boot?
Click to expand...
Click to collapse
Kernel image, ramdisk to be exact.
After boot it's in /, but it can't be edited from there since it's loaded from the ramdisk.

[ROM][WIP/Experimental][AOSP][4.3.1] Google Edition for SGS4A (int'l) v0.8

What?
work in progress build of AOSP, using LeJay's CM kernel sources and device files, modified to play ball with AOSP
some stuff copied from CM, to make build happen (bionic, assorted libs and stuff in external and system)
build makefiles modified, using CM files where possible
some small code modifications
for I9295 international only
stuff is broken, for how long i do not know. I'm still learning this stuff
DISCLAIMER: You take responsibility of your phone and what you flash into it, not me. You are warned
How?
grab the file: https://drive.google.com/folderview?id=0BzJzDM42pkRvcUVyZDRVSERzdlk&usp=sharing
if coming from another rom: factory reset + system format
upgrading previous version shouldn't need factory reset or system format
flash in CWM (yes, CWM or similar needed)
flash gapps
report bugs if new one found
help with development if possible
Credits
Google for Android (and Google search, boy this wouldn't have happened without it )
CyanogenMod for stuff i'm using to make this happen
SlimRom guys
LeJay for jactivelte kernel sources and other stuff
ohwarumbloss for testing CM builds and donations
Chainfire for root
other donators and testers
Changes v0.8
Video preview fixed
sub-1080p video recording fixed
Audio volume settings copied from SlimRom jf-common, more volume
Changes v0.7.1
Only kernel changes
Newer Broadcom wireless drivers from S4 CM 10.2 kernel
EXT4 and JBD2 drivers from S4 CM 10.2 kernel
MSM-8960 related stuff from S4 CM 10.2 kernel
Assorted stuff from S4 CM 10.2 kernel, check the commits in https://github.com/spegelius/android_kernel_samsung_jactivelte if interested (and if something seems wrong, please tell me
Changes v0.7
dualboot version available
network location working
backup to google account working. For those flashing cleanly, the setting should be on. For those dirtyflashing, you need to check this out: http://jftr.de/2014/01/fairphone-and-android-backups-to-the-google-cloud/
Changes v0.6
dualboot version available
some merges from S4 kernel, no changes in functionality
cwm update script doesn't format system anymore
libbt-vendor natively built instead copy from CM build. No change in functionality
Changes v0.5
Sdcard should now work (FAT32 at least, report exfat)
Sports Tracker doesn't crash UI when 'network' location provider isn't found
Changes v0.3 & 0.4
[*]Receiving calls fixed
Hanging up the call fixed
NFC doesn't crash on the background anymore, cannot test though
Bluetooth fixed, using lib from CM build
Changes v0.2
WiFi dhcp fixed
SuperSu included
init.d support
bash included
Bluetooth updates, but no full fix yet
Bugs v0.8
Whoa, are there any?
Bugs v0.7.1
Camera: 720p recording produces crappy videos
Camera: during video recording the preview is very low resolution
Bugs v0.6
Some problems with locations, network locaion isn't really enabled
Camera: 720p recording produces crappy videos
Camera: during video recording the preview is very low resolution
Backup account set to debug-only private cache for some users
Bugs v0.5
Some problems with locations
Camera: 720p recording produces crappy videos
Camera: during video recording the preview is very low resolution
Fixed Bugs
Sdcard doesn't mount
Cannot receive calls
Cannot hang up a call
WiFi connects, but doesn't get IP address
Bluetooth service fails at start, bluetooth doesn't work
NFC seems to be crashing on the background
no root as of yet
Source code
https://github.com/spegelius
Will be updating manifests and other stuff there when i figure a good way to get my changes there.
Oh and mods, if this fits the regular development section better, feel free to move it

A little incentive. Confirmation number: 1D974208B4414071D
I'll test and report. I'm on the GDE 4.2.2 port from Darkman now.

Downloading
Thank you very much for your efforts Mate!
Going to install this and report back soon!
Sent from my GT-I9295 using xda app-developers app
Edit1
Ok, here I come.
- Installation worked fine
- Bluetooth crashed on start as mentioned
- Mobile Data works (at least Edge, thats what I have here)
- WiFi get stuck in "Authenfication" when using standard settings
- WiFi connects when using "static IP" in advanced settings
- been to lazy to config Router for nonDHCP but I think it should work
- All SU Files (chainfire) I tried didn´t work (google search, no success, yet)
- No external SD, but that´s normal in AOSP I think (need 3rd Party app for this)
So, I started to compare this build with CM (cm-10.2-20131227-UNOFFICIAL-jactiveltexx) and there are several Files missing but there are so many..
@spegelius, if only I knew which ones are candidates for Problems...
Edit 2:
These Files may be interesting/important (Don´t laugh if this is totally wrong)
Missing Files in AOSP Build :
Code:
/system/app
- BluetoothExt.apk
Code:
/system/lib
- libbluedroid.so
- libcurve25519.so
- libimscamera_jni.so
- libjackpal-androidterm4.so
- liblzo.so
- libncurses.so
- libpci.so
- libssh.so
- libvt_jni.so
Code:
/system/lib/hw :
- nfc_nci.msm8960.so
- power.msm8960.so
Code:
/system/xbin
- bash
- htop
- Isof
- nano
- openvpn
- powertop
- rsync
- vim
There is no /system/etc/init.d (may be the/a problem of SU as there is also no "50selinuxrelabel" script)
There is no /system/etc/ssh (may be familar to the WiFi as it contains a script "sshd_config", inside this there is a lot of IP-Forwarding bla bla.. but all with a "#" in front)
I hope that helped a little or at all...I don´t have time for more investigations/testing for the rest of today, sorry..
Greetings
Thomas

ohwarumbloss said:
Downloading
Thank you very much for your efforts Mate!
Going to install this and report back soon!
Sent from my GT-I9295 using xda app-developers app
Edit1
Ok, here I come.
- Installation worked fine
- Bluetooth crashed on start as mentioned
- Mobile Data works (at least Edge, thats what I have here)
- WiFi get stuck in "Authenfication" when using standard settings
- WiFi connects when using "static IP" in advanced settings
- been to lazy to config Router for nonDHCP but I think it should work
- All SU Files (chainfire) I tried didn´t work (google search, no success, yet)
- No external SD, but that´s normal in AOSP I think (need 3rd Party app for this)
So, I started to compare this build with CM (cm-10.2-20131227-UNOFFICIAL-jactiveltexx) and there are several Files missing but there are so many..
@spegelius, if only I knew which ones are candidates for Problems...
Edit 2:
These Files may be interesting/important (Don´t laugh if this is totally wrong)
Missing Files in AOSP Build :
Code:
/system/app
- BluetoothExt.apk
Code:
/system/lib
- libbluedroid.so
- libcurve25519.so
- libimscamera_jni.so
- libjackpal-androidterm4.so
- liblzo.so
- libncurses.so
- libpci.so
- libssh.so
- libvt_jni.so
Code:
/system/lib/hw :
- nfc_nci.msm8960.so
- power.msm8960.so
Code:
/system/xbin
- bash
- htop
- Isof
- nano
- openvpn
- powertop
- rsync
- vim
There is no /system/etc/init.d (may be the/a problem of SU as there is also no "50selinuxrelabel" script)
There is no /system/etc/ssh (may be familar to the WiFi as it contains a script "sshd_config", inside this there is a lot of IP-Forwarding bla bla.. but all with a "#" in front)
I hope that helped a little or at all...I don´t have time for more investigations/testing for the rest of today, sorry..
Greetings
Thomas
Click to expand...
Click to collapse
Thanks for digging this stuff out. Some of those might be needed, i'l be adding them from CM repos one by one and testing how it works. I did another build, now adding Superuser to makefiles but still no go. Superuser does pop up after boot, telling su binary neds updating... Also added some init.rc scripts which are in CM build, but still no luck. After some digging, it seems that with 4.3, Google has made rooting bit more difficult. Root is my nr. 1 prio now, i'll need it to restore Titanium backups...
I've been using the rom few days now and it seems to work very well all in all. I had a camera hang yesterday, and after killing camera app it said Cannot connect to camera. Could get a logcat...

Yes, root is a problem, indeed..
Tried 3 hours yesterday in the evening, pushing all kind of different Versions and ended up with the binary update..
Also searched in CM Rom but it seems to be somewhere I can't find it, that little devil
ADB is working fine, also the shell with full root access, pushing and deleting Files, chown, all good. But no luck with the Superuser.apk.
Ended in frustration and restoring Stock..
Now, I hope you're getting it, somehow!
Did you get DHCP running somehow?
There are 3 PC and 4 Smartphones here using Wlan and I'm not really up to set them all up to static IP
Greetings
Thomas
Sent from my GT-I9295 using xda app-developers app

ohwarumbloss said:
Yes, root is a problem, indeed..
Tried 3 hours yesterday in the evening, pushing all kind of different Versions and ended up with the binary update..
Also searched in CM Rom but it seems to be somewhere I can't find it, that little devil
ADB is working fine, also the shell with full root access, pushing and deleting Files, chown, all good. But no luck with the Superuser.apk.
Ended in frustration and restoring Stock..
Now, I hope you're getting it, somehow!
Did you get DHCP running somehow?
There are 3 PC and 4 Smartphones here using Wlan and I'm not really up to set them all up to static IP
Greetings
Thomas
Sent from my GT-I9295 using xda app-developers app
Click to expand...
Click to collapse
Well i have the Superuser app as embedded in the rom and when starting TB, logcat shows that su binary tries to start, but fails with error:
D/su ( 2213): su invoked.
D/su ( 2214): starting daemon client 10062 10062
E/su ( 2215): connect failed with 2: No such file or directory
E/o.gZ ( 1909): Root shell has terminated unexpectedly.
Did a search of the error and it seems that it's related to root setting in developer options. The problem is, there's no setting for root in there. Gonna have to do some diffing between CM and AOSP settings.
Haven't looked into the dhcp yet.

To get root working:
install SuperSu: http://forum.xda-developers.com/showthread.php?t=1538053
Run in adb shell:
Code:
mount -o remount,rw /system
echo persist.sys.root_access=1 >> /system/build.prop
reboot
I'm trying to get supersu integrated, but latest from github doesn't like to play ball. Maybe i'll just use the above release and integrate it... Koush's Superuser doesn't display the dialog for root access when using CM's version and latest from github didn't find some symbols.
Edit: use value 3 if you want to give root access to apps and adb

Ok, some progress, even though i even lost root for a while. Damn i was losing my mind over it, but the it turned out to be a matter of su daemon not starting during boot. Added init.d support and proper init script for the daemon.
- wifi dhcp should work now. It was a matter of file permissions in /system/etc/dhcpd, run-hooks could not be executed. Noticed this when running dhcpd on adb shell. The cmw install script simply didn't set the perms...
- included SuperSu to rom, root should work out of the box
Bluetooth is still buggy; it doesn't fc on boot, but now it fails after a little while, this time the problem is that there's no /dev/ttyO1 for some reason and bt libs cannot connect to it.
Ver 0.2 is uploading, test away

spegelius said:
Ok, some progress, even though i even lost root for a while. Damn i was losing my mind over it, but the it turned out to be a matter of su daemon not starting during boot. Added init.d support and proper init script for the daemon.
- wifi dhcp should work now. It was a matter of file permissions in /system/etc/dhcpd, run-hooks could not be executed. Noticed this when running dhcpd on adb shell. The cmw install script simply didn't set the perms...
- included SuperSu to rom, root should work out of the box
Bluetooth is still buggy; it doesn't fc on boot, but now it fails after a little while, this time the problem is that there's no /dev/ttyO1 for some reason and bt libs cannot connect to it.
Ver 0.2 is uploading, test away
Click to expand...
Click to collapse
nice to here this , for bt issue are the ttyO1 file in ramdisk of boot.img?

mythi said:
nice to here this , for bt issue are the ttyO1 file in ramdisk of boot.img?
Click to expand...
Click to collapse
Hmm, haven't checked. I'll check that after work. I assume the vendor module is built properly as qcom's libs define ttyO1 and libbt_vendor.so exists. But shouldn't the ttyO1 ceated if the module is built?

spegelius said:
Hmm, haven't checked. I'll check that after work. I assume the vendor module is built properly as qcom's libs define ttyO1 and libbt_vendor.so exists. But shouldn't the ttyO1 ceated if the module is built?
Click to expand...
Click to collapse
Hmm... maybe tty01 is a qcom propriety so it couldnt be created without pulling it from a working device and place it in dev folder of ramdisk , I thought like this because the kernel extracts ramdisk files and folders in the "/" folder ..

mythi said:
Hmm... maybe tty01 is a qcom propriety so it couldnt be created without pulling it from a working device and place it in dev folder of ramdisk , I thought like this because the kernel extracts ramdisk files and folders in the "/" folder ..
Click to expand...
Click to collapse
Ok, could be. Don't know how ramdisk is created during build, have to look into it.
Also, found a quite major bug: cannot receive phone calls, at least i can't. That's kinda big problem, considering this is a phone still

Use dsixda kitchen to exreact the boot.img and view/edit its contents

mythi said:
Use dsixda kitchen to exreact the boot.img and view/edit its contents
Click to expand...
Click to collapse
Extracted boot.img, contents:
Code:
./zImage
./ramdisk
./ramdisk/init.trace.rc
./ramdisk/init.qcom.rc
./ramdisk/init.qcom.usb.sh
./ramdisk/system
./ramdisk/init.qcom.lpm_boot.sh
./ramdisk/sepolicy
./ramdisk/file_contexts
./ramdisk/seapp_contexts
./ramdisk/sbin
./ramdisk/sbin/ueventd
./ramdisk/sbin/adbd
./ramdisk/sbin/watchdogd
./ramdisk/init.cm.rc
./ramdisk/init.recovery.qcom.rc
./ramdisk/default.prop
./ramdisk/dev
./ramdisk/res
./ramdisk/res/images
./ramdisk/res/images/charger
./ramdisk/res/images/charger/battery_charge.png
./ramdisk/res/images/charger/battery_0.png
./ramdisk/res/images/charger/battery_fail.png
./ramdisk/res/images/charger/battery_5.png
./ramdisk/res/images/charger/battery_3.png
./ramdisk/res/images/charger/battery_4.png
./ramdisk/res/images/charger/battery_1.png
./ramdisk/res/images/charger/battery_2.png
./ramdisk/init.qcom.syspart_fixup.sh
./ramdisk/ueventd.qcom.rc
./ramdisk/charger
./ramdisk/sys
./ramdisk/init.qcom.class_main.sh
./ramdisk/init.usb.rc
./ramdisk/init.qcom.sh
./ramdisk/init.carrier.rc
./ramdisk/init.qcom.early_boot.sh
./ramdisk/ueventd.rc
./ramdisk/init.target.rc
./ramdisk/init.rc
./ramdisk/data
./ramdisk/init.qcom.class_core.sh
./ramdisk/init.qcom.usb.rc
./ramdisk/proc
./ramdisk/lpm.rc
./ramdisk/init
./ramdisk/property_contexts
./ramdisk/fstab.qcom
./ramdisk.cpio.gz
Nothing in /dev. Apparently those files are created by kernel/something else?
I'm feeling out of ideas currently, don't know where to start looking... i mean everything compiles ok, no errors. Logcat says:
Code:
I/bt_userial_vendor( 1515): userial vendor open: opening /dev/ttyO1
E/bt_userial_vendor( 1515): userial vendor open: unable to open /dev/ttyO1
E/bt_userial( 1515): userial_open: wrong numbers of open fd in vendor lib [0]!
E/bt_userial( 1515): userial_open: HCI UART expects only one open fd
From what i looked at bluedroid code, the tty opening should happen in vendor bt lib... meh. Same libs work with CM, i'm already using system/bluetooth and external/bluetooth from CM, along with qcom libs of course.
And about the phone, i can't seem to get apns to show, even though i copied proper apns list from CM. Even did a factory reset just to eliminate possibility about bad datas etc.

spegelius said:
Extracted boot.img, contents:
Code:
./zImage
./ramdisk
./ramdisk/init.trace.rc
./ramdisk/init.qcom.rc
./ramdisk/init.qcom.usb.sh
./ramdisk/system
./ramdisk/init.qcom.lpm_boot.sh
./ramdisk/sepolicy
./ramdisk/file_contexts
./ramdisk/seapp_contexts
./ramdisk/sbin
./ramdisk/sbin/ueventd
./ramdisk/sbin/adbd
./ramdisk/sbin/watchdogd
./ramdisk/init.cm.rc
./ramdisk/init.recovery.qcom.rc
./ramdisk/default.prop
./ramdisk/dev
./ramdisk/res
./ramdisk/res/images
./ramdisk/res/images/charger
./ramdisk/res/images/charger/battery_charge.png
./ramdisk/res/images/charger/battery_0.png
./ramdisk/res/images/charger/battery_fail.png
./ramdisk/res/images/charger/battery_5.png
./ramdisk/res/images/charger/battery_3.png
./ramdisk/res/images/charger/battery_4.png
./ramdisk/res/images/charger/battery_1.png
./ramdisk/res/images/charger/battery_2.png
./ramdisk/init.qcom.syspart_fixup.sh
./ramdisk/ueventd.qcom.rc
./ramdisk/charger
./ramdisk/sys
./ramdisk/init.qcom.class_main.sh
./ramdisk/init.usb.rc
./ramdisk/init.qcom.sh
./ramdisk/init.carrier.rc
./ramdisk/init.qcom.early_boot.sh
./ramdisk/ueventd.rc
./ramdisk/init.target.rc
./ramdisk/init.rc
./ramdisk/data
./ramdisk/init.qcom.class_core.sh
./ramdisk/init.qcom.usb.rc
./ramdisk/proc
./ramdisk/lpm.rc
./ramdisk/init
./ramdisk/property_contexts
./ramdisk/fstab.qcom
./ramdisk.cpio.gz
Nothing in /dev. Apparently those files are created by kernel/something else?
I'm feeling out of ideas currently, don't know where to start looking... i mean everything compiles ok, no errors. Logcat says:
Code:
I/bt_userial_vendor( 1515): userial vendor open: opening /dev/ttyO1
E/bt_userial_vendor( 1515): userial vendor open: unable to open /dev/ttyO1
E/bt_userial( 1515): userial_open: wrong numbers of open fd in vendor lib [0]!
E/bt_userial( 1515): userial_open: HCI UART expects only one open fd
From what i looked at bluedroid code, the tty opening should happen in vendor bt lib... meh. Same libs work with CM, i'm already using system/bluetooth and external/bluetooth from CM, along with qcom libs of course.
And about the phone, i can't seem to get apns to show, even though i copied proper apns list from CM. Even did a factory reset just to eliminate possibility about bad datas etc.
Click to expand...
Click to collapse
Hmmm.. Something is wrong lets reference to the stock kernel maybe we get answeres
:silly:
edit: Even stock kernel doesnt have have guess issue is different
---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------
Looking at the logcat and staring at it for 20 minutes i think Logcats says
There is permission issue in the /system/vendor folder , missing bluetooth libs :cyclops: or simply permission issue

mythi said:
Hmmm.. Something is wrong lets reference to the stock kernel maybe we get answeres
:silly:
edit: Even stock kernel doesnt have have guess issue is different
---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------
Looking at the logcat and staring at it for 20 minutes i think Logcats says
There is permission issue in the /system/vendor folder , missing bluetooth libs :cyclops: or simply permission issue
Click to expand...
Click to collapse
Heh, yes it might a permission issue, i've tried to match my updater-script perms to CM's, but not sure if they should be the same or something else. Suggestions welcome.
Edit: perms system:
Code:
drwxr-xr-x root root 2014-01-29 22:11 app
drwxr-xr-x root shell 2014-01-29 22:12 bin
-rw-r--r-- root root 3405 2008-08-01 15:00 build.prop
drwxr-xr-x root root 2014-01-29 22:11 cameradata
drwxr-xr-x root root 2014-01-29 22:11 etc
drwxr-xr-x root root 2014-01-29 22:11 fonts
drwxr-xr-x root root 2014-01-29 22:11 framework
drwxr-xr-x root root 2014-01-29 22:11 lib
drwxr-xr-x root root 1970-01-01 02:00 lost+found
drwxr-xr-x root root 2014-01-29 22:11 media
drwxr-xr-x root root 2014-01-29 22:11 tts
drwxr-xr-x root root 2014-01-29 22:11 usr
drwxr-xr-x root shell 2014-01-29 22:11 vendor
drwxr-xr-x root shell 2014-01-29 22:12 xbin
perms /system/vendor:
Code:
drwxr-xr-x root shell 2014-01-29 22:11 firmware
drwxr-xr-x root shell 2014-01-29 22:11 lib
perms /system/vendor/lib:
Code:
-rw-r--r-- root root 13880 2008-08-01 15:00 libbt-vendor.so
perms /system/vendor/firmware:
Code:
-rw-r--r-- root root 9432 2008-08-01 15:00 bcm2079xB4_firmware.ncd
-rw-r--r-- root root 783 2008-08-01 15:00 bcm2079xB4_pre_firmware.ncd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335.hcd
-rw-r--r-- root root 28862 2008-08-01 15:00 bcm4335_A0.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_murata.hcd
-rw-r--r-- root root 70 2008-08-01 15:00 bcm4335_prepatch.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_semco.hcd
Maybe i'll need to set them root:shell in vendor?

spegelius said:
Heh, yes it might a permission issue, i've tried to match my updater-script perms to CM's, but not sure if they should be the same or something else. Suggestions welcome.
Edit: perms system:
Code:
drwxr-xr-x root root 2014-01-29 22:11 app
drwxr-xr-x root shell 2014-01-29 22:12 bin
-rw-r--r-- root root 3405 2008-08-01 15:00 build.prop
drwxr-xr-x root root 2014-01-29 22:11 cameradata
drwxr-xr-x root root 2014-01-29 22:11 etc
drwxr-xr-x root root 2014-01-29 22:11 fonts
drwxr-xr-x root root 2014-01-29 22:11 framework
drwxr-xr-x root root 2014-01-29 22:11 lib
drwxr-xr-x root root 1970-01-01 02:00 lost+found
drwxr-xr-x root root 2014-01-29 22:11 media
drwxr-xr-x root root 2014-01-29 22:11 tts
drwxr-xr-x root root 2014-01-29 22:11 usr
drwxr-xr-x root shell 2014-01-29 22:11 vendor
drwxr-xr-x root shell 2014-01-29 22:12 xbin
perms /system/vendor:
Code:
drwxr-xr-x root shell 2014-01-29 22:11 firmware
drwxr-xr-x root shell 2014-01-29 22:11 lib
perms /system/vendor/lib:
Code:
-rw-r--r-- root root 13880 2008-08-01 15:00 libbt-vendor.so
perms /system/vendor/firmware:
Code:
-rw-r--r-- root root 9432 2008-08-01 15:00 bcm2079xB4_firmware.ncd
-rw-r--r-- root root 783 2008-08-01 15:00 bcm2079xB4_pre_firmware.ncd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335.hcd
-rw-r--r-- root root 28862 2008-08-01 15:00 bcm4335_A0.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_murata.hcd
-rw-r--r-- root root 70 2008-08-01 15:00 bcm4335_prepatch.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_semco.hcd
Maybe i'll need to set them root:shell in vendor?
Click to expand...
Click to collapse
try making perms in vendor as root excute user and group (i think in other words it is root:shell) this will inusre if we have perm issue

mythi said:
try making perms in vendor as root excute user and group (i think in other words it is root:shell) this will inusre if we have perm issue
Click to expand...
Click to collapse
No go with relaxed permissions, even set the x bit on... also noticed that /system/etc/bluetooth had some strange permissions, but no change.
I noticed that there are some bluetooth related devices in /dev, like ttyHS0 so it isn't fully dead. The problem is to find out why the damn ttyO1 won't start... actuallu i'm not liking the current state where i use most of the Bluetooth implemntation from CM. What i'd like is to have as close to AOSP as possible. Maybe i'll need to start cherrypicking parts of the bluetooth code and take only needed stuff to support qcom chips. But that'll take a while to get working.
Oh and stumbled upon some telephony code in framework/opt/telephony. Saw some files like SamungQualcom in CM sources, which indicates that to get phone working, checking through that code is needed. Quick compare showed some 100 files are different, so there;s work there too...

spegelius said:
No go with relaxed permissions, even set the x bit on... also noticed that /system/etc/bluetooth had some strange permissions, but no change.
I noticed that there are some bluetooth related devices in /dev, like ttyHS0 so it isn't fully dead. The problem is to find out why the damn ttyO1 won't start... actuallu i'm not liking the current state where i use most of the Bluetooth implemntation from CM. What i'd like is to have as close to AOSP as possible. Maybe i'll need to start cherrypicking parts of the bluetooth code and take only needed stuff to support qcom chips. But that'll take a while to get working.
Oh and stumbled upon some telephony code in framework/opt/telephony. Saw some files like SamungQualcom in CM sources, which indicates that to get phone working, checking through that code is needed. Quick compare showed some 100 files are different, so there;s work there too...
Click to expand...
Click to collapse
Why dont we cherry pick from gs4 snapdragon version qcom things since they share the same board , just cherry pick the diver files from an aosp rom for that device I am quite sure it will work .
Sent from my GT-I9295 using Tapatalk

Don't give up!
Let me know if there's something I can do!
Saturday 95℅ free time if the weather doesn't turn to warm (bike is calling)
Sent from my GT-I9295 using xda app-developers app

[DEPRECATED][GUIDE][ROOT] Smartwatch 3 KNX01V

I removed download link due to this method not working on lollipop.
This guide is deprecated, please use TWRP Recovery from this thread to install root
DISCLAMER and WARNING: I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or the current economic crisis. Please do some research if you have any concerns about this app.
Click to expand...
Click to collapse
You have been warned!
Links:
Sony PC Companion
Download link removed while I will test for compatibility with 5.x, md5 summ: e2c34b07faa415a6cbb95943649c7eba
Step 1:
Code:
[URL="source.android.com/source/building-devices.html#unlocking-the-bootloader"]Unlocked bootloader[/URL]
1. Enable adb debug
2. adb reboot bootloader
3. fastboot oem unlock (twice if requested)
4. fastboot format cache
5. fastboot format userdata
6. fastboot getvar all (and verify that it is)
7. fastboot reboot
Step 2:
Code:
Updated to the latest KNX01V
[URL="http://www.sonymobile.com/us/tools/pc-companion/"]Install Sony PC Companion[/URL] and use Supports Zone -> Accessories software update -> Smartwatch 3
Step 3:
Code:
Have Flashboot (Sony s1 flash) drivers installed just in case (Install Sony PC Companion and do update as indicated in previous step)
Step 4:
Code:
[COLOR="red"]BOOT [/COLOR][COLOR="Red"](DO NOT EVER FLASH IT!!!)[/COLOR] rooting boot.img
1. Download rooting kernel image (SWR50-rootboot.img)
2. Reboot into bootloader (adb reboot bootloader)
3. fastboot boot SWR50-rootboot.img
4. Wait till device reboots or sits in black screen for a while (1 min+ then reboot it by holding power 10+sec)
Step 5:
Code:
Verify by:
1. adb shell
2. su
3. you should see [email protected]:/ #
Step 6:
Code:
1. Let me know!
2. Use it, dive into GPS investigation or customizations, etc.....
Special thanks:
1. Justin Case for LG G Watch rooting method using LGGW-rootboot.img
2. osm0sis for Android Image Kitchen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

reserved

How it works:
1. Each boot.img packs zImage (real kernel) and ramdisk (special files for kernel use)
2. This one has all modifications from LGGW rootboot by Justin Case:
a. Adds su binary, superuser.sh install script, modified install-recovery.sh and additional step into init.rc file to invoke superuser.sh install script. Also modifications to mount system as rw and some disabled security.
3. So basically it mount system as rw and does following (cut from superuser.sh install script):
Code:
#!/system/bin/sh
/system/bin/mount -o remount,rw /system
/system/bin/sleep 2
/system/bin/cat /sbin/su > /system/xbin/su
/system/bin/cat /sbin/su > /system/xbin/daemonsu
/system/bin/cat /sbin/install-recovery.sh > /system/etc/install-recovery.sh
/system/bin/chown 0.0 /system/xbin/su
/system/bin/chown 0.0 /system/xbin/daemonsu
/system/bin/chown 0.0 /system/etc/install-recovery.sh
/system/bin/chmod 06755 /system/xbin/su
/system/bin/chmod 06755 /system/xbin/daemonsu
/system/bin/chmod 755 /system/etc/install-recovery.sh
/system/bin/sync
/system/bin/sleep 3
/system/bin/reboot

I have dumped the rom from my debug/test version and was wondering if you were able to give me a guide on how i could try and flash it with a retail version? I presume this root guide probably won't work for me

Well, if hardware and partitions are the same - I do not see why it will not work. However, it will not help to flash.
I might try to compile twrp, but will have to carefully read its docs first.

thanks @XorZone confirmed as working and a nice easy process too (I was already unlocked).
Out of curiosity, modded LGGW rootboot or just renamed?

iBuzman said:
thanks @XorZone confirmed as working and a nice easy process too (I was already unlocked).
Out of curiosity, modded LGGW rootboot or just renamed?
Click to expand...
Click to collapse
Thanks for letting me know!
I reverse engineered changes in LGGW by unpacking and comparing ramdisks from both rootboot and original lg kernel and then applied the same changes to our kernel extracted from PC Companion files.

great thinking and good job ?
btw, that pic confirmed su access to watch over bluetooth debug connection ?

really great tutorial. I am planning to buy this watch, but I think currently there is NO app that requires Root. so I wonder how can we get benefit of this ?

Kurotsuchi said:
really great tutorial. I am planning to buy this watch, but I think currently there is NO app that requires Root. so I wonder how can we get benefit of this ?
Click to expand...
Click to collapse
There is at least Wear Control app: https://play.google.com/store/apps/details?id=octathorp.wearcontrol
I plan to code density changer that will require access to adb, so either from rooted phone or rooted wear.

Kurotsuchi said:
really great tutorial. I am planning to buy this watch, but I think currently there is NO app that requires Root. so I wonder how can we get benefit of this ?
Click to expand...
Click to collapse
how to benefit?
root apps of course!!
(sry for bad pic, unlocked bootloader z3 in low light [emoji12]

XorZone said:
There is at least Wear Control app: https://play.google.com/store/apps/details?id=octathorp.wearcontrol
I plan to code density changer that will require access to adb, so either from rooted phone or rooted wear.
Click to expand...
Click to collapse
that's awesome man! will purchase mine next week, can't wait to root it. thanks for the answer.

Thanks for the root, XorZone. For anyone wondering, here's the dmesg of the watch
A few small observations from digging:
The main chipset seems to be the BCM23550
The CPU has 4 cores, 2 are disabled in software. Should be easy enough to reenable if you please
It definitely has WiFi hardware, but the firmware is currently missing from the image. If you mange to get a hold of compatible firmware and nvram, it should be simple enough to get WiFi up and running
The WiFi firmware message mentions a "43341". Which is odd because apparently the main chipset does have WiFi support built in. Searching for a Broadcom 43341 gives you this, but this might just be a red herring.

cb22 said:
Thanks for the root, XorZone. For anyone wondering, here's the dmesg of the watch
A few small observations from digging:
The main chipset seems to be the BCM23550
The CPU has 4 cores, 2 are disabled in software. Should be easy enough to reenable if you please
It definitely has WiFi hardware, but the firmware is currently missing from the image. If you mange to get a hold of compatible firmware and nvram, it should be simple enough to get WiFi up and running
The WiFi firmware message mentions a "43341". Which is odd because apparently the main chipset does have WiFi support built in. Searching for a Broadcom 43341 gives you this, but this might just be a red herring.
Click to expand...
Click to collapse
Yeah, I noticed the same about WiFi chip, it might be that they packed bcm43341 as part of the BCM23550 soc, like Invensense MPU9250 chip packs mpu6500 inside.
For the 43341 I'm finding it in the configs here: https://android.googlesource.com/kernel/tegra/+/bdde9f16131a5ac2039062d5ce22e3e153acbe68^!/
Looks like BCM43341 is BCM4334 + NFC chip, so we could try S3 I9300 files as per http://redmine.replicant.us/projects/replicant/wiki/GalaxyS3I9300Firmwares

how can i grant superuser permission to an app? i install es file explorer with sideload but i can't get superuser permission. the procedure is ok

Sorry admins for not putting in correct location....
Moved to Correct Area!

cdrshm said:
Sorry admins for not putting in correct location....
I can not get my device to show up in adb devices and its driving me crazy. Tried windows 7/8/server 2012R2 ..lol
Now I have done my fair share of custom roms and bootloaders.
OG Droid
Nexus
Nexus 10
Asus Memo Pad (came from alarm company, and could only load one app...now its a full running tablet)
I am sure its a silly thing I have done or am missing...
Thoughts....ideas?..need more info?
Click to expand...
Click to collapse
As usual, check if adb enabled in settings-about-developer options, if there are no developer options - it is as usual 7 times click on build number in about screen.

And please use Q&A thread for such questions

I've confirmed root survives the Lollipop update

Wow, I was out whole weekend, will have to catch up with the update

N1 Taiwan release

According to Engadget China the N1 will be released this month in Taiwan. The cool thing about this news is that it will have the Play store! http://chinese.engadget.com/2015/04/13/nokia-n1-taiwan-leak/

syddd said:
According to Engadget China the N1 will be released this month in Taiwan. The cool thing about this news is that it will have the Play store! http://chinese.engadget.com/2015/04/13/nokia-n1-taiwan-leak/
Click to expand...
Click to collapse
Nice to know!
By the way syddd, Im back at home with my new N1. Whenever Ive got some time I will start playing with it.

Can someone make an image file from the Taiwan version?
Many thanks!

I bought my N1 from eglobalcentral and was very surprised when it arrived yesterday with all google stuff already installed so I'm assuming they sent me a Taiwanese version (anyone knows if there's a way to check this?). I'd be happy to take an image if someone tells me how to do it

hmm very interesting.
A few questions:
- In the Play store do you see some apps as unavailable? Like Google Chrome or Google maps? Does getting location works in maps?
-What is the build version you see in the about page (in the china version they are like A5CN315)?
-Have you tried to root it? If yes did you succeed?

So far all google apps that I would usually use are available , and even better, chrome, maps, gmail, hangouts etc are already preinstalled and there is no Chinese market by default. At first I thought that someone manually patched the tablet and installed all this but then I thought it was not likely as it came in a sealed box and secondly it didn't have all the caveats that come with manually installing google services / play store. Also, during the first startup it asks to sign in to google mail etc (not sure if the Chinese version does it).
Shortly after first bootup it asked me to install an update which I did and all google stuff was in place after the update process was finished.
I'll post the sw version number later on - I don't have the tablet with me at the moment
Update: asked my missus to take the screenshots for me.
Here's the version number:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And the home screen (MoonReader+ and Ghost Commander were installed by me, all other apps came with the tablet):
---------- Post added at 11:08 AM ---------- Previous post was at 10:48 AM ----------
Update: this page (here's google translated version) suggests that A5FM51C is indeed a Taiwanese version

PLZ share build.prop

Here you go:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=A5FM51C
ro.build.display.id=A5FM51C
ro.build.version.incremental=2015-05-28-R-023643
ro.build.version.sdk=21
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.0.2
ro.build.date=Thu May 28 10:37:44 CST 2015
ro.build.date.utc=1432780664
ro.build.type=user
ro.build.user=sam
ro.build.host=topaz0
ro.build.tags=release-keys
ro.product.model=N1
ro.product.brand=Nokia
ro.product.name=N1
ro.product.device=Nokia_N1
ro.product.board=moorefield
ro.setupwizard.mode=OPTIONAL
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86
ro.product.cpu.abilist=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=Nokia
ro.product.locale.language=zh
ro.product.locale.region=TW
ro.wifi.channels=
ro.board.platform=moorefield
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Nokia_N1
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=N1-user 5.0.2 A5FM51C 2015-05-28-R-023643 release-keys
ro.build.fingerprint=Nokia/N1/Nokia_N1:5.0.2/A5FM51C/2015-05-28-R-023643:user/release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.dalvik.vm.isa.arm=x86
ro.enable.native.bridge.exec=1
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
drm.service.enabled=true
ro.blankphone_id=1
ro.fxn.ota.sku=tw2015
ro.com.widevine.cachesize=16777216
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.0_r2
ro.com.google.clientidbase=android-foxconn
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=200m
dalvik.vm.heapsize=348m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
dalvik.jit.code_cache_size=1048576
ro.hwui.texture_cache_size=72
ro.hwui.layer_cache_size=48
ro.hwui.r_buffer_cache_size=8
ro.hwui.gradient_cache_size=1
ro.hwui.path_cache_size=32
ro.hwui.drop_shadow_cache_size=6
ro.hwui.texture_cache_flushrate=0.4
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=1024
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
ro.hwui.shape_cache_size=3
ro.fxn.def.dns1=8.8.8.8
ro.fxn.def.dns2=8.8.4.4
persist.sys.dalvik.vm.lib.2=libart.so
ro.ril.status.polling.enable=0
bt.hfp.WideBandSpeechEnabled=true
dalvik.vm.isa.x86.features=sse4_2,aes_in,popcnt,movbe
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.intel.corp.email=1

Anyway we can flash with this new one's ROM?
Many thanks!!
---------- Post added at 05:24 AM ---------- Previous post was at 05:22 AM ----------
Your new one Build Number comes with "FM". While the Mainland Chinese one came with "CN". Yours definitely is full version one.

wodz69 said:
And the home screen (MoonReader+ and Ghost Commander were installed by me, all other apps came with the tablet):
Click to expand...
Click to collapse
How do you find this Taiwan N1? Wondering how smooth and lag free it is. I've been hanging back on getting a Chinese release without the Play Store then rooting due to all the issues. Hoping this release is smooth as silk without glitches.
How long did delivery take from eGlobalCentral?

Have u managed to pull out the image of your os ?
Sent from my A0001 using Tapatalk

wodz69 said:
So far all google apps that I would usually use are available , and even better, chrome, maps, gmail, hangouts etc are already preinstalled and there is no Chinese market by default. At first I thought that someone manually patched the tablet and installed all this but then I thought it was not likely as it came in a sealed box and secondly it didn't have all the caveats that come with manually installing google services / play store. Also, during the first startup it asks to sign in to google mail etc (not sure if the Chinese version does it).
Shortly after first bootup it asked me to install an update which I did and all google stuff was in place after the update process was finished.
I'll post the sw version number later on - I don't have the tablet with me at the moment
Update: asked my missus to take the screenshots for me.
Here's the version number:
And the home screen (MoonReader+ and Ghost Commander were installed by me, all other apps came with the tablet):
---------- Post added at 11:08 AM ---------- Previous post was at 10:48 AM ----------
Update: this page (here's google translated version) suggests that A5FM51C is indeed a Taiwanese version
Click to expand...
Click to collapse
you can use fiddler to caught firmware.

xkernels said:
you can use fiddler to caught firmware.
Click to expand...
Click to collapse
View attachment 3410939
View attachment 3410942

Sorry for delayed reply - I was on holidays. I'll try to dump the images sometime this weekend. Which partitions would be of interest: boot, system, recovery, ...?

Your N1 got update after you buy it? I want know Product_ID=N1-china2015 of Taiwan version N1.

I finally got around to root the tablet and dump the images of boot, recovery and system - you can find them at the following link:
https://www.dropbox.com/sh/drmfv30k54jgb35/AABc9uPxpOSUNHsV1lSD-k_1a?dl=0
There are a few more partitions that might be of interest - please let me know if you wanted me to dump them
[email protected]_N1:/mnt/shell/emulated/0 # ll /dev/block/by-name/
ll /dev/block/by-name/
lrwxrwxrwx root root 2015-07-26 14:56 boot -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-26 14:56 boot-one-shot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-26 14:56 cache -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-26 14:56 config -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-26 14:56 data -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-26 14:56 factory -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-26 14:56 fastboot -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-26 14:56 infork -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-26 14:56 logs -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-26 14:56 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-26 14:56 panic -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-26 14:56 persistent -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-26 14:56 ramdump -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-26 14:56 recovery -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-26 14:56 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-26 14:56 silentlake -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-26 14:56 splashscreen -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-26 14:56 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-26 14:56 userkeystore -> /dev/block/mmcblk0p8
Click to expand...
Click to collapse
Xkernels - not sure where to find the product_id you are referring to. If you let me know where to look for and I'll post it

Thanks a lot, buddy!

wodz69 said:
I finally got around to root the tablet and dump the images of boot, recovery and system - you can find them at the following link:
https://www.dropbox.com/sh/drmfv30k54jgb35/AABc9uPxpOSUNHsV1lSD-k_1a?dl=0
There are a few more partitions that might be of interest - please let me know if you wanted me to dump them
Xkernels - not sure where to find the product_id you are referring to. If you let me know where to look for and I'll post it
Click to expand...
Click to collapse
you can use Fiddler to find product_id,you can refer the pic which I post above.

Thanks a lot wodz69.
Did someone test it already? Can i simply install the system image in recovery?

Same question.
I am quite afraid to be the first to test it
Did someone try to apply it?
Thanks for reply! :fingers-crossed: