I did the same maneuvers with framework (still on the Thl). Inside of Vroot superuser window manager, as well terminal as root).

– I browsed the web trying to see if anything like this has happened. There, I found an article on how to switch superuser (which is very recent).

– 2-1) Superuser chainfire OK.

– 2-2) Download a root browser app from play store. It asked root permission (chain fire responds). Delete Vroot Superuser apk in /system/apps. For some reasons, I had to grant root permission again to the root browser, before it could delete Vroot. Reboot Thl 4000. Everything seems to function as before.

– 3) Conclusions:

1st time I met this kind of problem. Thanks to the contributor on the web: http://andro-era.blogspot.ch/2015/0…

PS. I saw that vroot is now iroot and a apk could do the job on the smarphone.

I did the same maneuvers with framework (still on the Thl). Inside of Vroot superuser window manager, as well terminal as root).

– I browsed the web trying to see if anything like this has happened. There, I found an article on how to switch superuser (which is very recent).

– 2-1) Superuser chainfire OK.

– 2-2) Download a root browser app from play store. It asked root permission (chain fire responds). Delete Vroot Superuser apk in /system/apps. For some reasons, I had to grant root permission again to the root browser, before it could delete Vroot. Reboot Thl 4000. Everything seems to function as before.

– 3) Conclusions:

1st time I met this kind of problem. Thanks to the contributor on the web: http://andro-era.blogspot.ch/2015/0…

PS. I saw that vroot is now iroot and a apk could do the job on the smarphone.

# password with the SMB password when the encrypted SMB password in the

# passdb is changed.

unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following

# parameters must be set (thanks to Ian Kahan <
for # sending the correct chat script for the passwd program in Debian
Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\ n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# ’passwd program’. The default is ’no’.
pam password change = yes
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
########## Domains ###########
# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the ’domain master’ setting to no
#
; domain logons = yes
#
# The following setting only takes effect if ’domain logons’ is set
# It specifies the location of the user’s profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user’s home directory
# (this is Samba’s default)
# logon path = \\%N\%U\profile
# The following setting only takes effect if ’domain logons’ is set
# It specifies the location of a user’s home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U
# The following setting only takes effect if ’domain logons’ is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in ’DOS’ file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser —quiet —disabled-password —gecos "" %u
# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d
/var/lib/samba -s /bin/false %u
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup —force-badname %g
########## Printing ##########
# If you want to automatically load your printer list rather
# than setting them up individually then you’ll need this
# load printers = yes
# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap
# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups
############ Misc ############
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m
# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY
# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c ’/usr/bin/linpopup "%f" "%m" %s; rm %s’ &
# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to ’no’; otherwise, the default behavior is recommended.
# domain master = auto
# Some defaults for winbind (make sure you’re not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100
# Allow users who’ve been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
#======================= Share Definitions =======================
[homes]
comment = Home Directories
browseable = no
# By default, the home directories are exported read-only. Change the
# next parameter to ’no’ if you want to be able to write to them. read only = no
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
create mask = 0775
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
directory mask = 0775
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
valid users = %S
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700
[mydir]
readonly = no
locking = no
path=/home/philippe
valid users = philippe
guest ok = no
[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace ’lpadmin’ with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin
# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server’s CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes
# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don’t want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom
-
Commentaires
How to unbrick Android Caesar A9600
Wednesday 26 August 2015
by philippe Vo cong tri
popularity : 1%
(Upd August/28/2015)
Hello,
1) Intro:
This cookbook article is mainly written for me to remember.
I bought the Caesar with android 4.2.x, I rooted it with MTKdroidtools. I soft bricked it, last year, trying to upgarde to Kikat; I managed to flash a russian ROM 4.2.x, rooted and I wanted to install original rom firmware.
Last week I bricked the smartphone (rooted), after succesfully install TWRP Zp910 and tried to upgrade it to 4.2 (for ZP910) . No more usb driver detected, no red light steady light charging ... >Dead…

I tried to use the testpoint technics, my grandson (91/2 years old), help me to dismount the frame to get onto the board, to no avail; In fact he has found the right screwdriver bit and unscrewing all of them and he also reminded me the K point label that I was looking for days (sharp mind isn’t he ? 🙂 ). Not really dead, I checked the battery with a mutimeter: gave 1,5 v. With Smartphone (battery insert), I checked live points on the board, there were juice.

The main interesting effect: PC Devices configuration shows Alcatel single RNDIS driver, switched on/off (the smartphone has battery inserted), when smartphone is connected to the pc.

Here is the exprience how to unbrick the thing. Thanks to much hints, tricks from people on the web and forii.

I am using Netbook Asus with Win7 starter.

2) Steps:
2-1)
– Download latest sp-flashtool, v5-1352.01, install it.
– Download from needrom.com: A9600-official-130319, unzip it
– Download MT65xx_usb_driver ; make sure that’s the right one for MT6589 and if possible for CaesarA9600, Zp910 etc … I have to find the web link on my other cheap smarphone,
–
– Uninstall Alcatel single RNIS from the PC. Reboot the pc.
– Insert the smartphone usb, with battery. Wait a moment, a click sound from the pc will be heard: win7 tries to install driver on a popup window, stopped it windows update …
– Wait a moment, Win7 will search on the pc the correct driver: vcom and will install it without error.

2-2)
– Disconnect the smartphone from the PC.
– Run Sp-flashtool
– Choose the scatter file (A9600-official), in the 2nd row
– Once scatter file loaded, all stick boxes showld be ticked
– Click download button
– Hold smartphone Volume+ and insert usb cable to pc usb port.
– Unhold smartphone volume+.
– Wait a moment, the PC will detect smartphone as COM/LPT: Vcom port 12 or 13 whatever.
– Wait a moment, the sp-flashtool will start to download data to the smartphone, yellow color bar progress shown on lower part.
– When 100% download, without error, a popup window with green symbol and OK will be shown.
– Discounnect the usb cable, wait for the sound from pc, reinsert it back. Now the smartphone driver will jitter on the pc devices configuration panel, I can see drives E F briefly, then YunOS will be shown at the end of devices configuration screen.
– Red steady light charging shown on Caesar A9600, I can see the battery image jittering on the screen .

ps: The testpoint is on a screw hole, down right (I think), the smatphone has a tiny label with K symbol, which covers the head of the screw. (???) We had to scratch the label in order to take out the screw.

Links:

http://forum.xda-developers.com/sho…

http://www.chinaphonearena.com/foru…

http://www.chinaphonearena.com/foru…

http://forum.frandroid.com/topic/14…

– mt65xx_usb_driver: http://www.gleescape.com/posts/2376

– mt65xx_usb_driver files: (i have a lot of drivers on the PC, not sure this could be vcom, but at least Yunos)

After many trials to install the rom, my conclusions:
– Do not try to install Xposed Framework I cannot install Play store apps anymore.

– Stagefright 1 are resolved but not stagefright 2 (the worst).

– Of course, my IMEI are gone. I have had to enter them manually with eg MTK engineering app.

A thread gives the solutions:
– AT(space)+EMGR …

PNG – 76.4 kb

PNG – 84.9 kb

Upd 16112015: After adding lines setting stagefright to false in build.prop, the Zimperium stagefright detector gives me all patches shown (all grey) (no more green and red highlights). I use another stagefright which gives me as not vultnerable (version 1).

– A patch has been released by Mlais (Thanks to the forum). V 20151102. The stagefright version 1 and 2 (1st of 2).

PNG – 103.5 kb

PNG – 90.2 kb

Upd 16112015: After adding lines setting stagefright to false in build.prop, the Zimperium stagefright detector gives me all patches shown (all grey) (no more green and red highlights). I use another stagefright which gives me as not vultnerable (version 1).

Upd 26/12/2015: shellshock vulnerability (bash) OK.

3-4) Oukitel U8 (add 16112015): Thanks to the contributors.

I was one the first acquirers (pre-sale), the fingerprint doesn’t work, despite 2 OTA. But, the vulnerabilities must be patched …

The 20151010 update from oukitel has patched stagefright version 1.

After that, i have rooted the device via CWM (Carliv), thanks to ghost45, the package can be found in a wellknown chinese forum, the article is in german, very well explained. ps: cf dualsim spanish web site.

– CWM Caveat: SUpersu zip must be put on external-sd.

– I will use Xposed privacy and take all kown steps for prevention …

PNG – 86.1 kb

PNG – 92 kb

JPEG – 2.7 Mb

4) Others: Kitkat and Lollipop

Well, I have to check for updates (eventually) or DIY.

4-1) Last week, I acquired for a bargain (fidelity) a “major” brand latest smartphone customized by my Telecom provider. I am baffled that nothing has been done, nor not seeing a warning ! Upd 12/11/2015: My Telecom provider send me a message: Very soon, the patch is coming.

I read somewhere that my provider has disabled MMS in their servers. And their german partner (yes, the phone is stamped with their trademark beginning with the letter V…..) has written something like: they are in control … No update will be released for the moment, since there aren’t any real menace bieng reported !!! (cf german forum). As other people said: How could I know, that my infos are leaked or or spied ?). Well, have I to put a sniffer ?

– Upd 20/04/2016: GRA-L09C900B321:
– I update the P8 to Marshmallow v6, by downloading the file from Huawei site, http://huawei-info.de/huawei-p8-off… ([UPDATE] Huawei P8: Offizelles Android 6.0 Marshmallow Update [B321] – inkl. Download OTA & FULL Update ), thanks to androidhilfe.de .
– I was looking at it without really understanding its implication: I was supposed to receive a OTA notice …, since my phone is branded by Vodafone CH. – The phase on the update page does the catch: for all versions of GRA-L09. So the update was possible from GRA-L09C02B191 to GRA-L09C900B321

– The current stagefright 1&2 vulnerabilities are solved.

JPEG – 90.7 kb JPEG – 1.1 Mb

– Upd 26/11/2015: GRA-L09C02B191
— I have updated the P8 (customized for Vodafone CH): OTA version 5.1.1, at last. The stagefright 1 and 1st of 2 stagefright 2 are repaired.
— Just Check for update, download and install (555 MB).

— PS: Just in case, I was prepared to unlock bootloader, aka getting the code as explained in Xda and frandroid forii and do it myself (cf Version GRA-L09xxxx200), cf german forum android-hilfe.de . Thanks to the contributors.

PNG – 119.9 kb

PNG – 154.4 kb

4-2 Samsung gt-i9001 (26/12/2015): ION cm11 rel 8

The only one that has Cyanogenmod: 11-20140622-UNOFFICIAL, 4.4.4, I9001XXKG1, 3.4.94-cyanogenmod-g4d69025 …,cm_ariesve-userbug 4.4.4. Rooted.

PS: There at least 7 updates since then, and Lollipop base …

I stick to this version, and put its sources in Studio to dissect …

Lately I stumbled on shellshock vulnerability (which is bash problem). I was aware of this vulnerabilties in Linux servers and Pcs, but forgot about Android 🙁 .

— To check: shellshock app in Playstore. The gt-i9001 has this vulnerability.

Hopefully, XDADEV is my friend: A patch exists, which is updated regularly. Download the patch zip, extract in ESxplorer, copy bash in its bin directory, rename existing /system/xbin/bash, paste the new bash. And of course check with shellshock. OK.

— Check stagefright vulnerabilities with Zimperium app: only 3 vulnerabilities are patched. PS: CM dates back to 2014.
— I use the manual method to patch in /system/build.prop file. Use stagefright viewer apk to check. No garanty …

2) Environment setup:
– I use Linux.
— Download and install Android Studio 1.5 ;
— Download Oracle jdk 1.7 (use Ubuntu guidance vas explained in some threads):
— – I have 2 jdks: openjdk and oracle jdk (the later must be used, otherwise there will be warning in the Studio).

ps: Oracle warns that the 1.7 version is deprecated… By default Android studio sets up SDK 6.

X86 device won’t run for me. For Intel, there are some necessary tweaks at the BIOS and drivers to add.

Build and run the emulator: Takes some time to show the nexus 4 and logo. I wasn’t able to see the emulated hello world (some threads warn that it would take up to 10mn, parameters tweakings necessary in the Studio).
– After waiting more than 10mn, I try to unlock the simulated device, with the mouse pad, the event log shows “lose event” in red…

ps: Some threads give hints about PC memory and emulated memory amount. I have to try further.

– It is possible to run the app, directly thru the real display device, as . For Linux Ubuntu, I have to install drivers and hookup the real device via USB.

JPEG – 863 kb

Create my first project app: I have nothing to do, just clicking tabs to examine the files … Cf Android studio tutorials (some are very well explained.