need help building recovery g901f or english translation - Galaxy S 5 Q&A, Help & Troubleshooting
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.
Related
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
[HOW TO] XIP Patch
Hello,
this is a small tutoriel witch explain how to patch XIP.
"maby that work for Kaiser and niki too"
You must have :
- Kitchen for polaris "thank to Udk"
- XIPPort tools "thanks to bepe"
- M'Reloc "thanks to misar"
{
"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"
}
Thanks to All XDA develepers and beta testers without exeption.
And Sorry for my very bad english
Note : If you use "All_packages_to_one.exe" to protect your ROM this method not work
Nice Nice Nice thanks man nice work i will try this soon.
This should all guides look like Great job! I my self would like a tutorial that shows how to Build a rom from Raw-files
Good work M-Amine and thanks for sharing...
Thanks. But this should be called patch XIP , not port. vivi
vivi said: Thanks. But this should be called patch XIP , not port. vivi Click to expand... Click to collapse Hi vivi, Yes it's not a Full XIP porting but for me this is the only solution to have the correct build. If you know how to port full XIP share it with us thank you
.......... vivi said: Thanks. But this should be called patch XIP , not port. Click to expand... Click to collapse
Yes a vivi full xip's port tutorial !
Same, I never sucess to port bootable XIP with Polaris. Only patch it. I can port XIP of ASUS P525 and 535 in 2 minutes with ease. But for Polaris I think there is a secret I don't know. I ask udk but he never answer my PM, also bepe. I think if we share what we know , it's better to our communities. I will buy a Diamond soon. So tired with Polaris. vivi
Hello, ok rectified now "XIP Patch"
Why you cannot port polaris' xip???? I ported a lot of them, and worked ever perfectly..... no need patch xip!!!
ervius said: Why you cannot port polaris' xip???? I ported a lot of them, and worked ever perfectly..... no need patch xip!!! Click to expand... Click to collapse Hi ervius, we don't have knowledge to make this. an assistant from you or another dev will be the welcome . thank you
M-Amine said: Hi ervius, we don't have knowledge to make this. an assistant from you or another dev will be the welcome . thank you Click to expand... Click to collapse only need: original polarix (ORIGINAL!!!) xip and new other device xip xipport and xipaddresstool dump both the original is "\out" the new is "\out_new" (and package made!) duplicate "\out" (original polaris xip (no package mode!)) rename into "\out_ref" open xipaddresstool open work_dir and select "out" open ref_dir and select "out_ref" compare, all is ok... now go into out_new\modules\xipkernel\ select "coredll.dll" module, for i.e. parte module into \out\modules\, overwrite existing reopen work_dir and ref_dir in xipaddresstool something to change... see the values into coredll.dll module, and change by the referred, just on right in same line now go into xip_new\files\xipkernel, select xipkernel dsm (it start usually with "72") and paste into \out\files now if xipaddresstool give all ok, open xipport , realloc P, maybe something goes wrong, about an address, not important, write map, and chek into \out\map.txt if there are some !!! (maybe no "!!!" inside"), ok, with xipport click on build xip_out.bin you have ported (partially!) new xip.bin, if you repeat theese operations for all modules on xipkernel, maybe you have a complete xipporting on polaris! P.S.: some modules in xipkernel give problem and is hardest reallign the modules, so you can leave them, or try step, by step, to port them into old-new xip (\out folder!) good work!!! bye!
hi ervius, when I use insert.exe to insert xip in os.nb.payload devices don't boot at all. note : - I use m'reloc to realocate addresses in all modules in MXIPKERNEL, one by one. - I clic on realoc P - Write map - write xip_out.bin
Hello, J’ai essayé de porter le xip Build 19588 de la ROM du Diamond, si je laisse tout dans MXIPKernel l’appareil ne boot pas, si je laisse les 7 fichiers dans MXIPKernel l’appareil boot mais le XIP est en 19209 (je ne sais pas ou il va chercher ça) merci M-Amine Pour que XIPPort.exe fonctionne il faut pkgcomon.dll 5.1.10000.1 et pas .dll 5.2.0.0 ;-) #########Hello, I tried to bring the xip Build 19588 of the ROM Diamond, if I leave everything in MXIPKernel the camera does not boot, if I leave the 7 files in the ruise MXIPKernel boot but the XIP is a 19209 ( do not know where it fetches it) merci M-Amine For XIPPort.exe works must be pkgcomon.dll 5.1.10000.1 not. Dll 5.2.0.0 ;-)
Hello dr-jo, look first post Note : If you use "All_packages_to_one.exe" to protect your ROM this method not work
Merci M-Amine, le post à changé depuis se matin ;-) Ça fonctionne, par contre j’ai deux questions, quelle méthode fonctionne pour sécuriser la ROM, et comment changer la date du build 2007 en 2008, merci. #####Thank you M-Amine, the post was changed from morning ;-) It works by cons I have two questions, what method works to secure the ROM, and how to change the date of build 2007 to 2008, thank you.
Salut dr-jo, pour sécuriser ta ROM supprime just les fichier RGU : - ouvre le fichier \tools\Create_ROM_For_Polaris.bat - remplace le contenu par ça : Code: @echo off TOOLS\G'Reloc.exe -doit -dump copy ROM\OS.nb.payload temp\OS.nb.payload cd temp @Echo Suppression des fichiers RGU attrib dump\*.rgu -h -s -r +a DEL dump\*.rgu @Echo Activation des attributs HSR attrib dump\*.dsm +h +s +r attrib dump\*.dll +h +s +r attrib dump\*.png +h +s +r attrib dump\*.tsk -h +s +r attrib dump\mxip*.* +h +s +r attrib dump\FMH*.bmp +h +s +r attrib dump\ha_*.bmp +h +s +r attrib dump\I-*.bmp +h +s +r attrib dump\ses*.bmp +h +s +r @Echo Appuyez sur une touche pour continuer pause ..\TOOLS\ImgfsFromNb OS.nb.payload imgfs.bin ..\TOOLS\ImgfsFromDump imgfs.bin imgfs-new.bin ..\TOOLS\ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload ..\TOOLS\NBMerge -kaiser os-new.nb Hello dr-jo, to protecte your ROM, open \tools\Create_ROM_For_Polaris.bat and replace all texte with this : Code: @echo off TOOLS\G'Reloc.exe -doit -dump copy ROM\OS.nb.payload temp\OS.nb.payload cd temp @Echo Suppression des fichiers RGU attrib dump\*.rgu -h -s -r +a DEL dump\*.rgu @Echo Activation des attributs HSR attrib dump\*.dsm +h +s +r attrib dump\*.dll +h +s +r attrib dump\*.png +h +s +r attrib dump\*.tsk -h +s +r attrib dump\mxip*.* +h +s +r attrib dump\FMH*.bmp +h +s +r attrib dump\ha_*.bmp +h +s +r attrib dump\I-*.bmp +h +s +r attrib dump\ses*.bmp +h +s +r @Echo Appuyez sur une touche pour continuer pause ..\TOOLS\ImgfsFromNb OS.nb.payload imgfs.bin ..\TOOLS\ImgfsFromDump imgfs.bin imgfs-new.bin ..\TOOLS\ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload ..\TOOLS\NBMerge -kaiser os-new.nb
ervius said: only need: original polarix (ORIGINAL!!!) xip and new other device xip xipport and xipaddresstool dump both the original is "\out" the new is "\out_new" (and package made!) duplicate "\out" (original polaris xip (no package mode!)) rename into "\out_ref" open xipaddresstool open work_dir and select "out" open ref_dir and select "out_ref" compare, all is ok... now go into out_new\modules\xipkernel\ select "coredll.dll" module, for i.e. parte module into \out\modules\, overwrite existing reopen work_dir and ref_dir in xipaddresstool something to change... see the values into coredll.dll module, and change by the referred, just on right in same line now go into xip_new\files\xipkernel, select xipkernel dsm (it start usually with "72") and paste into \out\files now if xipaddresstool give all ok, open xipport , realloc P, maybe something goes wrong, about an address, not important, write map, and chek into \out\map.txt if there are some !!! (maybe no "!!!" inside"), ok, with xipport click on build xip_out.bin you have ported (partially!) new xip.bin, if you repeat theese operations for all modules on xipkernel, maybe you have a complete xipporting on polaris! P.S.: some modules in xipkernel give problem and is hardest reallign the modules, so you can leave them, or try step, by step, to port them into old-new xip (\out folder!) good work!!! bye! Click to expand... Click to collapse Ervius , Thanks for the knowledges. Shame on those selfish guys. vivi
Thanks for sharing ervius
[Q] help me compile error for my p700
============================================ PLATFORM_VERSION_CODENAME=REL PLATFORM_VERSION=4.2.2 CM_VERSION=10.1-20130629-UNOFFICIAL-p700 TARGET_PRODUCT=cm_p700 TARGET_BUILD_VARIANT=userdebug TARGET_BUILD_TYPE=release TARGET_BUILD_APPS= TARGET_ARCH=arm TARGET_ARCH_VARIANT=armv7-a-neon HOST_ARCH=x86 HOST_OS=linux HOST_OS_EXTRA=Linux-3.5.0-34-generic-x86_64-with-Ubuntu-12.04-precise HOST_BUILD_TYPE=release BUILD_ID=JDQ39E OUT_DIR=/home/maxlestage/android/out ============================================ external/bluetooth/bluedroid/Android.mk:8: NO BOARD_BLUETOOTH_BDROID_BUILDCFG_INCLUDE_DIR, using only generic configuration /bin/bash: xsltproc : commande introuvable /bin/bash: xsltproc : commande introuvable build/core/Makefile:44: attention : écrasement des commandes pour la cible « /home/maxlestage/android/out/target/product/p700/system/etc/mkshrc » build/core/base_rules.mk:502: attention : anciennes commandes ignorées pour la cible « /home/maxlestage/android/out/target/product/p700/system/etc/mkshrc » PRODUCT_COPY_FILES system/bluetooth/data/main.le.conf:system/etc/bluetooth/main.conf ignored. build/core/Makefile:44: attention : écrasement des commandes pour la cible « /home/maxlestage/android/out/target/product/p700/system/etc/audio_policy.conf » build/core/base_rules.mk:502: attention : anciennes commandes ignorées pour la cible « /home/maxlestage/android/out/target/product/p700/system/etc/audio_policy.conf » PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored. PRODUCT_COPY_FILES development/tools/emulator/system/camera/media_profiles.xml:system/etc/media_profiles.xml ignored. PRODUCT_COPY_FILES development/tools/emulator/system/camera/media_codecs.xml:system/etc/media_codecs.xml ignored. PRODUCT_COPY_FILES hardware/libhardware_legacy/audio/audio_policy.conf:system/etc/audio_policy.conf ignored. PRODUCT_COPY_FILES device/lge/p700/configs/melfas-ts.kl:system/usr/keylayout/qwerty.kl ignored. No private recovery resources for TARGET_DEVICE p700 build/core/tasks/kernel.mk:56: *************************************************************** build/core/tasks/kernel.mk:57: * Using prebuilt kernel binary instead of source * build/core/tasks/kernel.mk:58: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED * build/core/tasks/kernel.mk:59: * Please configure your device to download the kernel * build/core/tasks/kernel.mk:60: * source repository to kernel/lge/msm7x27a-common build/core/tasks/kernel.mk:61: * See http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building build/core/tasks/kernel.mk:62: * for more information * build/core/tasks/kernel.mk:63: *************************************************************** host C: mkbootimg <= system/core/mkbootimg/mkbootimg.c host C: libmincrypt <= system/core/libmincrypt/rsa.c /bin/bash: prebuilts/misc/linux-x86/ccache/ccache: Aucun fichier ou dossier de ce type host C: libmincrypt <= system/core/libmincrypt/rsa_e_3.c make: *** [/home/maxlestage/android/out/host/linux-x86/obj/EXECUTABLES/mkbootimg_intermediates/mkbootimg.o] Erreur 127 make: *** Attente des tâches non terminées.... /bin/bash: prebuilts/misc/linux-x86/ccache/ccache: Aucun fichier ou dossier de ce type make: *** [/home/maxlestage/android/out/host/linux-x86/obj/STATIC_LIBRARIES/libmincrypt_intermediates/rsa.o] Erreur 127 /bin/bash: prebuilts/misc/linux-x86/ccache/ccache: Aucun fichier ou dossier de ce type make: *** [/home/maxlestage/android/out/host/linux-x86/obj/STATIC_LIBRARIES/libmincrypt_intermediates/rsa_e_3.o] Erreur 127 make: *** wait: Aucun processus enfant. Arrêt. [email protected]:~/android$
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?
Como recuperar MBR do windows
[Em resposta a >_Vulkan??] mbr: ::::::::::COMO RECUPERAR O BOOTLOADER (MBR) DO WINDOWNS:::::: 1- no Livelinux: sudo apt-get install lilo sudo lilo -M /dev/sda mbr 2-em um cd boot do windowns: -diskpart>>list disk>>list vol>>(achar aonde o win esta instalado)>>exit>> Bcdboot "C":\Windows PRONTO!!!!!!!!!!!!!!!!!!!!!!!!!:Boa: