Hi all,
does anybody configure the Wap for SFR, a french operator...
Thx
Regards,
=JaY=
[email protected]
Très simple
Configuration SFR (GPRS) pour XDA
Settings -> Connections -> Cliquer sur l'icône : Connections
Aller à "Internet Settings" et puis "Modify..."
Cliquer sur "New…"
"Enter a name for the connection:" SFR (GPRS)
"Select a modem:" Cellular line (GPRS)
"Baud rate:" 19200
Cliquer sur "Advanced…"
Cocher "Use software compression" et "Use IP header compression"
Cliquer sur "ok"
(Retour à la page précédante)
Cliquer sur "Next"
"Access Point Name:" websfr
Cliquer sur "Finish"
C'est fait !
______________________________
Paramètres ligne GPRS de SFR
Access Point Name: websfr
Telephone number: *99#
Hayes AT command: Z+CGDCONT=1,"IP","websfr"
IMAP4, POP3 & SMTP server: mail.sfr.net
______________________________
To Synchronize through ActiveSync and Server
===================================
En el registro y en la siguiente clave,
HKLM - System - Inbox
debemos tener lo siguiente en las claves
a) Attachments
AttsDir ------------------- Inbox.mst29915526.3837362304
BottomDir------------------ Mail Attachments
b) Settings
AttachPath \SD Card\Inbox.mst29915526.3837362304\Mail Attachments
PropertyPath \SD Card\Inbox.mst29915526.3837362304
Sorry for the post in spanish,
cambie de rom, en mi telefono y resulta que ahora, no me guarda niunguna configuracion, al reinicar el telefono, queda como de 0, no me guarda absolutamete nada, creo q meti la pata, intente hacer todos los wipe y etc etc, del custom recovery, del "stock recovery, creo que se le dice...
si alguien me dice que tan grande meti la pata
otra cosa, me aparecen ls errores .
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
first, write in english, second, flash the stock froyo sbf via rsd lite
hello
i have a sm-g901f device and i want to build a working recovery
i tried recovery builder but it doesn't work !?
i can provide my own boot.img and recovery img ..
doudou425 said:
hello
i have a sm-g901f device and i want to build a working recovery
i tried recovery builder but it doesn't work !?
i can provide my own boot.img and recovery img ..
Click to expand...
Click to collapse
i need only someone with a ready build environment ,because i'm not friend with ubuntu
or only porting the only existing recovery (in chinese) to english
thanks
+1 would be great!
Me too, waiting impatiently
doudou425 said:
i need only someone with a ready build environment ,because i'm not friend with ubuntu
or only porting the only existing recovery (in chinese) to english
Click to expand...
Click to collapse
Me too, waiting impatiently.
well I'm not really friends with ubuntu
I reinstall ubuntu for the second time and I will start the whole procedure
Would be awesome if we got a working english-aroma friendly-cwm for our 901f
Finally i have a fully working buid environment
But there's somme problem when compiling ,something about kernel
I dont know how to go ahead .....
What is the exact problem and at which stage of the compiling does it appear ?
Code:
[email protected]:~/tutu$ build/tools/device/mkvendor.sh samsung g901f /home/g901f/boot.img
Arguments: samsung g901f /home/g901f/boot.img
Output will be in /home/denis/tutu/device/samsung/g901f
cp: impossible d'évaluer «/home/g901f/boot.img»: Aucun fichier ou dossier de ce type
build/tools/device/mkvendor.sh : ligne 84 : 3116 Erreur de segmentation (core dumped) unpackbootimg -i $BOOTIMAGEFILE > /dev/null
gzip: ../boot.img-ramdisk.gz: No such file or directory
cpio: fin prématurée de l'archive
cat: /tmp/denis/bootimg/boot.img-base: Aucun fichier ou dossier de ce type
cat: /tmp/denis/bootimg/boot.img-cmdline: Aucun fichier ou dossier de ce type
cat: /tmp/denis/bootimg/boot.img-pagesize: Aucun fichier ou dossier de ce type
cp: impossible d'évaluer «/tmp/denis/bootimg/boot.img-zImage»: Aucun fichier ou dossier de ce type
unpackbootimg doesn't work with boot.img from g901f (new type inside)
en francais : a priori unpackbootimg ne fonctionne pas avec le type de boot.img en provenance du g901F ,ce serait un nouveau type de boot
Ça c'est rigolo ça je vais me pencher sur la question ce soir mais là comme ca je vois pas.
I found one unpackbootimg that works , to be continued...
J'ai trouvé un unpackbootimg qui fait correctement le boulot , affaire a suivre
Parfait ! C'est du beau boulot tiens nous au jus si ca avance.
Hello guys,
I think we're all French people on this topic but please if you want help, keep posting in English please
I'm also very interested by this topic.
Keep the good work
Franky
bon de nouveau bloqué ,j'ai maintenant mon boot.img correctement "unpacké" je vois bien tous les fichiers demandés
toutefois il faudrait adapter le mkvendor.sh pour ne plus avoir a unpacker le boot.img mais lui dire ou se trouvent les fichiers extraits pour continuer le taff ,mais ca je sais pas faire
voila le mkvendor.sh des fois que quelqu'un sache le modifier
Code:
#!/bin/bash
function usage
{
echo Usage:
echo " $(basename $0) manufacturer device [boot.img]"
echo " The boot.img argument is the extracted recovery or boot image."
echo " The boot.img argument should not be provided for devices"
echo " that have non standard boot images (ie, Samsung)."
echo
echo Example:
echo " $(basename $0) motorola sholes ~/Downloads/recovery-sholes.img"
exit 0
}
MANUFACTURER=$1
DEVICE=$2
BOOTIMAGE=$3
UNPACKBOOTIMG=$(which unpackbootimg)
echo Arguments: [email protected]
if [ -z "$MANUFACTURER" ]
then
usage
fi
if [ -z "$DEVICE" ]
then
usage
fi
ANDROID_TOP=$(dirname $0)/../../../
pushd $ANDROID_TOP > /dev/null
ANDROID_TOP=$(pwd)
popd > /dev/null
TEMPLATE_DIR=$(dirname $0)
pushd $TEMPLATE_DIR > /dev/null
TEMPLATE_DIR=$(pwd)
popd > /dev/null
DEVICE_DIR=$ANDROID_TOP/device/$MANUFACTURER/$DEVICE
if [ ! -z "$BOOTIMAGE" ]
then
if [ -z "$UNPACKBOOTIMG" ]
then
echo unpackbootimg not found. Is your android build environment set up and have the host tools been built?
exit 0
fi
BOOTIMAGEFILE=$(basename $BOOTIMAGE)
echo Output will be in $DEVICE_DIR
mkdir -p $DEVICE_DIR
TMPDIR=/tmp/$(whoami)/bootimg
rm -rf $TMPDIR
mkdir -p $TMPDIR
cp $BOOTIMAGE $TMPDIR
pushd $TMPDIR > /dev/null
unpackbootimg -i $BOOTIMAGEFILE > /dev/null
mkdir ramdisk
pushd ramdisk > /dev/null
gunzip -c ../$BOOTIMAGEFILE-ramdisk.gz | cpio -i
popd > /dev/null
BASE=$(cat $TMPDIR/$BOOTIMAGEFILE-base)
CMDLINE=$(cat $TMPDIR/$BOOTIMAGEFILE-cmdline)
PAGESIZE=$(cat $TMPDIR/$BOOTIMAGEFILE-pagesize)
export SEDCMD="s#__CMDLINE__#$CMDLINE#g"
echo $SEDCMD > $TMPDIR/sedcommand
cp $TMPDIR/$BOOTIMAGEFILE-zImage $DEVICE_DIR/kernel
popd > /dev/null
else
mkdir -p $DEVICE_DIR
touch $DEVICE_DIR/kernel
BASE=10000000
CMDLINE=no_console_suspend
PAGESIZE=00000800
export SEDCMD="s#__CMDLINE__#$CMDLINE#g"
echo $SEDCMD > $TMPDIR/sedcommand
fi
for file in $(find $TEMPLATE_DIR -name '*.template')
do
OUTPUT_FILE=$DEVICE_DIR/$(basename $(echo $file | sed s/\\.template//g))
cat $file | sed s/__DEVICE__/$DEVICE/g | sed s/__MANUFACTURER__/$MANUFACTURER/g | sed -f $TMPDIR/sedcommand | sed s/__BASE__/$BASE/g | sed s/__PAGE_SIZE__/$PAGESIZE/g > $OUTPUT_FILE
done
if [ ! -z "$TMPDIR" ]
then
RECOVERY_FSTAB=$TMPDIR/ramdisk/etc/recovery.fstab
if [ -f "$RECOVERY_FSTAB" ]
then
cp $RECOVERY_FSTAB $DEVICE_DIR/recovery.fstab
fi
if [ -f "$TMPDIR/ramdisk/sbin/htcbatt" ]
then
mkdir -p $DEVICE_DIR/recovery/root/sbin
CHARGER_FILES="/sbin/choice_fn /sbin/htcbatt /sbin/power_test /sbin/offmode_charging /sbin/detect_key"
for f in $CHARGER_FILES
do
if [ -f "$TMPDIR/ramdisk/$f" ]
then
cp $TMPDIR/ramdisk/$f $DEVICE_DIR/recovery/root/sbin
fi
done
cp $TEMPLATE_DIR/init.htc.rc $DEVICE_DIR/recovery/root/init.$DEVICE.rc
fi
fi
mv $DEVICE_DIR/device.mk $DEVICE_DIR/device_$DEVICE.mk
echo Creating initial git repository.
pushd $DEVICE_DIR
git init
git add .
git commit -a -m "mkvendor.sh: Initial commit of $DEVICE"
popd
echo Done!
echo Use the following command to set up your build environment:
echo ' 'lunch cm_$DEVICE-eng
echo And use the follwowing command to build a recovery:
echo ' '. build/tools/device/makerecoveries.sh cm_$DEVICE-eng
edit in English it'll be harder but I make the effort, thank you google trad
I found a version of unpackbootimg that works, I have all the files neccessaires
but we must adapt mkvendor.sh to use the extracted files instead of extract
by modifying slightly mkvendor.sh not delete the temporary file and pasting the extracted files with the new unpackbootimg
I managed to compile a nonfunctional recovery.img because I left everything default I have not changed boardconfig.mk etc. as shown here on step 4: http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
this test was just to see if the compilation is finalizing ..... and it worked :good:
en french :
en modifiant legerement mkvendor.sh pour ne pas supprimer le dossier temporaire et en collant les fichiers extraits avec le nouveau unpackbootimg
j'ai reussi a compiler un recovery.img non fonctionnel car j'ai tout laissé par defaut je n'ai pas modifié boardconfig.mk etc comme indiqué ici a l'etape 4 : http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
cet essai etait juste pour voir si la compilation se finalisait ..... et cela a fonctionné :good:
cool
doudou425 said:
J'ai trouvé un unpackbootimg qui fait correctement le boulot , affaire a suivre
Click to expand...
Click to collapse
T'es un pro!!! tiens nous au courant
merci de faire ça. enfin quelque chose a mettre sur mon G901F.
Thanks for doing it. Finally something for my G901F.
It seems that only france got the g901f
Pas de nouvelles bonne nouvelle :angel:
well ,good news chenglu made an english recovery for us
Chenglu said:
http://yun.baidu.com/pcloud/album/f...12765541086&uk=704970239&fsid=913008460800857
Click to expand...
Click to collapse
tested an approved
thank you @Chenglu
cool
doudou425 said:
well ,good news chenglu made an english recovery for us
tested an approved
thank you @Chenglu
Click to expand...
Click to collapse
tested an approuved too, very nice work.
thank you @Chenglu[/QUOTE]
Fine to have an operationnel custom recovery.
testé et approuvé, c'est cool d'avoir un recovery opérationnel.
hi all,
for the first time, i must restore a nandroid backup in my xiaomi mi a1.
when i restore it, it's go wrong because:
"
controllo sull'Digest in corso...
TWRP installer for Mi A1
unpacking the installer..
Running boot image patcher..
- Error: Unable to find boot block location!
- Aborting..
Failed to pacth boot image
il processo updater è terminato con errore: 1
errore durante l'installazione dello zip '/sdcard/pie/twrp-3.2.1.1-1-installer-tissot-FIXED_By_DroidMester.zip'
Aggiornamento dei dettagli della partizione...
Impossibile montare '/vendor' (invalid argoment).
...fatto
"
any solution?
what is /vendor error? i've never seen it.
tnx