Database Users

[Q] No me guarda ninguna configuracion

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

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.

SRS Root not work for me, could someone help?(SM-G531BT - (ZTO)Brasil)

Hello guys, i have a grand prime ve (with tv) [SM-G531BTVTZTO09OK1 - firmware update 11/2015] and in SRS root twitter's page there is a info saying that this device was rooted, ok! i did root all methods, and it says "Rooting complete!" then my device auto reboot but root isn't there, no bin, and if i try another time to root it check and not see root, and proceed to root again, but no root.
I am asking this here cause i know that this is a proper device for brazilian, more, is a Value Edition, and i think it will go unnoticed to root.
for this, i ask for some godsend if can help me and few others brazilians that got this device.
bellow the output of SRS Root.
Code:
---= SRS One-Click-Root v5.1 =---
22:52:46 - Starting ADB Server..
22:52:52 - Manufacturer: samsung
22:52:52 - Model: SM-G531BT
22:52:53 - Android Version: 5.1.1
22:52:53 - Build ID: LMY48B.G531BTVJU0AOK1
22:52:53 - Board ID: SC7730SE
22:52:54 - Chipset Platform: sc8830
22:52:54 - Getting OffSets.. : error: only position independent executables (PIE) are supported. (False)
22:52:57 - Query Server for Best Method.. Found Rootkit: 8
----= Start Rooting Process.. Please Wait =----
22:52:57 [+] Testing exploit: root8 (please wait..)
22:53:04 [+] Remounting /system Filesystem as R/W..
22:53:04 [+] Installing SU Binary...
22:53:07 [+] Installing SuperUser APK...
22:53:09 [+] Remounting /system Filesystem as R/O..
22:53:15 [+] Rooting Complete !

SM-G531BT
Yakchimi said:
Hello guys, i have a grand prime ve (with tv) [SM-G531BTVTZTO09OK1 - firmware update 11/2015] and in SRS root twitter's page there is a info saying that this device was rooted, ok! i did root all methods, and it says "Rooting complete!" then my device auto reboot but root isn't there, no bin, and if i try another time to root it check and not see root, and proceed to root again, but no root.
I am asking this here cause i know that this is a proper device for brazilian, more, is a Value Edition, and i think it will go unnoticed to root.
for this, i ask for some godsend if can help me and few others brazilians that got this device.
bellow the output of SRS Root.
Code:
---= SRS One-Click-Root v5.1 =---
22:52:46 - Starting ADB Server..
22:52:52 - Manufacturer: samsung
22:52:52 - Model: SM-G531BT
22:52:53 - Android Version: 5.1.1
22:52:53 - Build ID: LMY48B.G531BTVJU0AOK1
22:52:53 - Board ID: SC7730SE
22:52:54 - Chipset Platform: sc8830
22:52:54 - Getting OffSets.. : error: only position independent executables (PIE) are supported. (False)
22:52:57 - Query Server for Best Method.. Found Rootkit: 8
----= Start Rooting Process.. Please Wait =----
22:52:57 [+] Testing exploit: root8 (please wait..)
22:53:04 [+] Remounting /system Filesystem as R/W..
22:53:04 [+] Installing SU Binary...
22:53:07 [+] Installing SuperUser APK...
22:53:09 [+] Remounting /system Filesystem as R/O..
22:53:15 [+] Rooting Complete !
Click to expand...
Click to collapse
Também estou a procura do root para esse modelo do Brasil.

Instalei o TWRP sem root pelo PC com o heimdall.
1. Renomeia o twrp.img para recovery.img
2. Coloque o dispositivo em modo download, conecte o cabo antes de presionar o botão UP para continuar.
3. Obtenha o arquivo.pit
heimdall download-pit --output arquivo.pit
4. Coloque o recovery.img e o arquivo.pit na mesma pasta, de modo que ao executar o comando ls(Linux/MAC), ou dir(Windows) possa vê-los, use cd "Nome da pasta" para acessá-los.
5. Agora vamos efetuar o flash dos arquivos para o dispositivo:
heimdall flash --pit arquivo.pit --RECOVERY recovery.img --resume
Se necessário acrescente sudo no início dos comandos, mas instruções clicando aqui.

RESSUSCITANDO SEU LUMIA 950 XL (não liga, não vibra e o Pc não reconhece)

1) baixe o WPinternals 2.4 e o Windows Device Recovery Tool
2) Instale o Windows Device Recovery Tool.
3) Abra o WPinternals 2.4 na area de trabalho ( ele é auto executavel),em platform clique em download.
agora em producttype digite o modelo do lumia o meu é :RM-1116 e em productcode digite o do seu aparelho
(basta abrir a tampa do celular e lá vc encontrará qual será o modelo e o codigo o meu é:059X5B5)
clique em search e faça o download.
4) Após o download Vá até disco local C: e habilite o modo de exibição das pastas ocultas.
Vá até C:\ProgramData\WPInternals\Repository\RM-1116 e copie os
arquivos de emergencia: RM1116_fh.edp e o MPRG8994_fh.ede (lembrando que vai depender do modelo do seu celular ok.
5) cole os arquivos na pasta C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool.
conecte o seu lumia no pc via usb e segure o botão power até vc ouvir o barulho no pc (nada irá acontecer com seu aparelho).
6) Agora,Vamos abrir o CMD que ficará assim C:\WINDOWS\system32
Então iremos digitar com aspas:
cd "C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool"
Clique enter e digite sem aspas:
thor2 -mode emergency -hexfile MPRG8994_fh.ede -edfile RM1116_fh.edp -orig_gpt
aguarde todo o processo......
ao final aparecerá esta mensagem no CMD
Clearing the backup GPT...SKIPPED!
Unable to parse FFU file. File open failed
programming operation failed!
UEFI FLASH END
Operation took about 24.00 seconds.
FFU_PARSING_ERROR
THOR2 1.8.2.18 exited with error code 2228224 (0x220000)
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool>
O seu lumia ficará com a tela vermelha mostrando o modo recovery(as duas flechas se encontrando).Feche o CMD vamos para o proximo passo.
7) Abra o WPinternals 2.4 e clique em Flash do lado direito escolha a opção Flash original FFU
e clique em FFU escolha a rom que baixou e clique em FlashFFU image.
Aguarde todo o processo e pronto, seu aparelho ressuscitou!:legal:

[HELP] UNBRICK Zen Fone Max 3 ZC553KL (X00D)

Hello friends, I came here to ask a question, I updated my device with a stock rom (bootloader unlocked), I was using normal, so I accidentally installed an OTA update,
after that it is in an infinite loop, goes into fastboot mode (recognizes the device serial but cannot flash anything​, also tried ROMs via flash (unsuccessful), tried also via qfil and also unsuccessfully said that I wanted to know if anyone you can give me some instructions or I killed my phone.
Thank you very much in advance

willamy.lemos said:
Hello friends, I came here to ask a question, I updated my device with a stock rom (bootloader unlocked), I was using normal, so I accidentally installed an OTA update,
after that it is in an infinite loop, goes into fastboot mode (recognizes the device serial but
cannot flash anything
, also tried ROMs via flash (unsuccessful), tried also via qfil and also unsuccessfully said that I wanted to know if anyone you can give me some instructions or I killed my phone.
Thank you very much in advance
Click to expand...
Click to collapse
Mod edit - translated by https://www.deepl.com/translator:
Hello friend, this problem of yours I believe you can solve with ADB Flash Tools. I am having a similar problem. recently my device turned off and didn't turn on again. It connects as Qualcomm 9008. But it shows the following error in QFIL:
21:32:36: {ERROR: Unable to write to 'COM4. \ COM4', Windows API WriteFile Failed! Your device is probably *not* on this port, tried 100 times}
Write record to 'C: \ Users \ Nizack \ AppData \ Roaming \ Qualcomm \ QFIL \ COMPORT_4 \ port_trace.txt' may take a minute
The log is 'C: \ Users \ Nizack \ AppData \ Roaming \ Qualcomm \ QFIL \ COMPORT_4 \ port_trace.txt'
Download failed: FireHose failed: FHLoader failed: Process failed
Could someone please help me?
Thank you for your attention.
******************************************************
Olá amigo, esse seu problema acredito que consiga resolver com o ADB Flash Tools. Eu estou com um problema parecido. recentemente meu aparelho desligou e não ligou mais. ELE Conecta Como Qualcomm 9008. Porem apresenta o Seguinte Erro no QFIL:
21:32:36: {ERRO: Não foi possível gravar em '\\. \ COM4', Falha de WriteFile da API do Windows! Seu dispositivo provavelmente * não * está nesta porta, tentadas 100 vezes}
Gravar o registro em 'C: \ Users \ Nizack \ AppData \ Roaming \ Qualcomm \ QFIL \ COMPORT_4 \ port_trace.txt' pode demorar um minuto
O log é 'C: \ Usuários \ Nizack \ AppData \ Roaming \ Qualcomm \ QFIL \ COMPORT_4 \ port_trace.txt'
Falha no download: Falha no FireHose: Falha no FHLoader: Falha no processo
Alguém poderia me ajudar?
Obrigado pela atenção.