Database Users

Hx4700 Wm6 Mail Registry

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

create mms profile [VillaiElclair rom]

hello guys,
fail to set my network profile for mms (Orange MD).
Operator settings:
Code:
WAP:
Denumirea profilului / Profile name: Orange IMO
Pagina de start / Homepage: ht tp:/ /wap.orange.md
Purtator date / Data bearer: GPRS
Punct de acces GPRS / APN: wap .orange. md
Adresa IP / IP address: 192.168.127.124
WAP Port (WAP 1.x): 9201
WAP Port (WAP 2.0): 3128
Nume utilizator / User name: <camp liber>
Parola / Password: <camp liber>
MMS:
Denumirea profilului / Profile name: Orange MMS
Pagina de start / Homepage: ht tp:/ /mms/mms
Purtator date / Data bearer: GPRS
Punct de acces GPRS / APN: mms .orange. md
Adresa IP / IP address: 192.168.127.125
WAP Port (WAP 1.x): 9201
WAP Port (WAP 2.0): 3128
Nume utilizator / User name: <camp liber>
Parola / Password: <camp liber>
I do not know how to make a profile for mms and how you set it to be active.
please help me.

need help building recovery g901f or english translation

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.

erreur rom "E:failed to verify whole-file signatuture

Bonjour,
J'ai un Motorola Defy + avec carte SD 8G , j'ai rooter le téléphone et vérifie avec application( howtoroot).
je voudrais changer la Rom de mon téléphone, mais je n'y arrive pas.
Je lance le téléphone en boot log (avec rom manager 5.5.3.7, batterie charge ) ,
il redémarre page boot log , => j’appuie sur [- et +]
je vais sur apply update for SDcarde
et il me met message d'erreur
"E:failed to verify whole-file signatuture
E : Signature verification failed"
quelqu'un aurais une idée ?

Hello,
I have a Motorola Defy + with 8G SD card, I rooter and checks with the phone application (howtoroot).
I want to change my phone's ROM, but I can not.
I throw the phone in boot log (rom manager with 5.5.3.7, battery charging)
it restarts page boot log, => I press [- or +]
I go to apply update for SDcarde
and it puts me error
"E: failed to verify whole-file signatuture
E: Signature verification failed "
someone would have an idea?

Chinese android radio codes (Codigos de radio android chino)

Hello,
These are some codes, which I found on the internet
1. 12580
2. 3368
3. 121212
4. 126
5. 7253
6. 7839
7. 7780
8. 2767
9. 5839
10. 3855
11. 0272
12. 2688
13. 5802
14. 3105
15. 6556
16. 0207
17. 1357
18. 0123
19. 1688
20. 5839
21. 3506
22. 3711
23. 3271
24. 7749
25. 3308
26. 3668
27. 8880
28. 8890
29. 9000
30. 9023
31. 9024
32. 9026
33. 6688
34. 1617
35. 3506
36. 7890
37. 5678
I hope to be helpful.
Regards

Thank you. I am trying to enter a Chinese multimedia center ASVEGEN with Android 8.1 that does not give me the option to access factory settings or advanced settings directly.
I leave the link to my post in case you can help me:
https://forum.xda-developers.com/an...ad-units/head-unit-android-8-1-model-t3979941
I tried these but I had no luck, I see that your list is more extensive:
Muchas gracias. Estoy intentando entrarle a una central multimedia china ASVEGEN con Android 8.1 que no me da la opción de acceder a los factory settings ni advanced settings directamente.
Te dejo el link a mi post por el caso que me puedas ayudar:
https://forum.xda-developers.com/an...ad-units/head-unit-android-8-1-model-t3979941
Probé con estos pero no he tenido suerte, veo que tu lista es más extensa:
126
1234 ( mensaje "Start Copy")
1617
1983
3506
5839
6666 (mensaje "No installation file")
6688
7777 (mensaje "No installation file")
8888
7890
123456
111333
16176699
66668888
Thanks
Gracias.

Forum rule 4: Use the English language.
Forum rule 15: Keep threads / posts on-topic. This thread is completely off-topic, it has absolutely nothing to do with Android Auto.
Also, Forum Rule 2.5: All members are expected to read and adhere to the XDA rules.

mike.s said:
Forum rule 4: Use the English language.
Forum rule 15: Keep threads / posts on-topic. This thread is completely off-topic, it has absolutely nothing to do with Android Auto.
Also, Forum Rule 2.5: All members are expected to read and adhere to the XDA rules.
Click to expand...
Click to collapse
Members are also to use the report button

marchnz said:
Members are also to use the report button
Click to expand...
Click to collapse
Done, 12 hours before I posted
It behooves the mods to act quicker.

By the way, nice translation

johichi2009 said:
Hello,
These are some codes, which I found on the internet
1. 12580
2. 3368
3. 121212
4. 126
5. 7253
6. 7839
7. 7780
8. 2767
9. 5839
10. 3855
11. 0272
12. 2688
13. 5802
14. 3105
15. 6556
16. 0207
17. 1357
18. 0123
19. 1688
20. 5839
21. 3506
22. 3711
23. 3271
24. 7749
25. 3308
26. 3668
27. 8880
28. 8890
29. 9000
30. 9023
31. 9024
32. 9026
33. 6688
34. 1617
35. 3506
36. 7890
37. 5678
I hope to be helpful.
Regards
Click to expand...
Click to collapse
I have a new code 1983 for
9706 1DIN Android 10.0 Car Stereo 7 inch Retractable Screen Bluetooth Wi-Fi GPS Navigation Bluetooth Radio MP5 Player

BUEN DIA ALGUIEN SABE CUAL ES LA CONTRASEÑA PARA CAMBIAR LOGO EN ESTEREO ANDROID
Mod Edit: English Translation Below
GOOD MORNING DOES ANYONE KNOW WHAT IS THE PASSWORD TO CHANGE LOGO IN ANDROID STEREO