I am not responsible if anything goes wrong. You do this at your own risk!
Requirements:
- An unlocked bootloader
- Working adb and fastboot (e.g. Google's Platform Tools)
- Download a bootable TWRP
Boot into twrp
Instructions to backup EFS:
If TWRP has booted, type the following into your computers' terminal one after the other:
Code:
adb shell
dd if=/dev/block/sdf2 of=/tmp/modemst1.bin bs=2048
dd if=/dev/block/sdf3 of=/tmp/modemst2.bin bs=2048
exit
adb pull /tmp/modemst1.bin modemst1.bin
adb pull /tmp/modemst2.bin modemst2.bin
This will copy modemst files to your adb folder, backup this along with your pesist image to cloud, and you should be good if anytime you brick your device.
Credits to Macusercom, from the oneplus 7t pro fourms
why is TWRP needed in the process?
Related
Enable Developer Mode:
( on the watch )
tap clock, swipe up and go all the way down to “About”
tab build number several times. You’ll know
up one menu, “Developer Options” -> “ADB debugging”
your phone will ask you to allow debugging
dock it, plug usb to computer
in terminal:
adb usb
adb devices (check out your device’s serial #)
adb shell (woot! shell on your watch!)
Backup contents of system partition
mkdir system
adb pull /system ./system
Void the warranty (unlock bootloader)
adb reboot-bootloader
fastboot oem unlock
follow instructions on device
device will factory reset & reboot
Root ( needed to dump partition images, otherwise not particularly useful )
credit for this: androidpolice.com/2014/07/05/how-to-android-wear-enable-debugging-take-screenshots-unlock-the-bootloader-and-root-the-lg-g-watch/
get this: androidfilehost.com/?fid=23501681358558067
adb reboot-bootloader
Boot the image: fastboot boot LGGW-rootboot.img
DO NOT FLASH THE IMAGE!!!! FOR THE LOVE OF GOD DON’T FLASH IT!!!!!!!
intended to boot only once (installs su, etc)
adb shell
su
now what?
Dump some partitions: ( in a root shell on the watch )
partition layout
mmcblk0p15 - boot
mmcblk0p16 - recovery
mmcblk0p19 - system
mmcblk0p20 - cache
mmcblk0p21 - userdatadump some partitions. for example: ( jump into adb shell, as root )
dd if=/dev/block/mmcblk0p15 of=/sdcard/backup/boot.img
dd if=/dev/block/mmcblk0p16 of=/sdcard/backup/recovery.img
dd if=/dev/block/mmcblk0p19 of=/sdcard/backup/system.img
dd if=/dev/block/mmcblk0p20 of=/sdcard/backup/cache.imgDONT TRY TO BACKUP mmcblk0p21 to the sdcard!!! the “sdcard” is on that partition!!
pull the images. for example: ( on your computer )
adb pull /sdcard/backup/boot.img .
adb pull /sdcard/backup/recovery.img .
adb pull /sdcard/backup/system.img .
adb pull /sdcard/backup/cache.img .maybe delete those images from the device when you are done
Have Fun!
Restore images (flash via fastboot)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
The following may be tricky, might break stuff, and is generally not recommended unless you really know what you are doing
You have been warned!
Install a zip file using the stock recovery (might only work with signed updates, not roms)
In a terminal on your computer:
adb push whatever-new-rom.zip /sdcard/update.zip
adb shell
cp /sdcard/update.zip /cache/update.zip
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/cache/update.zip' >> /cache/recovery/commandreboot recovery
Enable Bluetooth debugging (really slow, kinda lame)
connect your phone over usb
on watch, in developer settings, Debug over Bluetooth
on phone, open wear app, in settings Debugging over bluetooth
on computer:
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444
adb shell
Install Debian chroot
on your phone (thats right, your phone) install Debian Kit from Play Store
open it, it the download button in top right corner
download debian-kit-1-6-testing.shar
open an adb shell to your phone ( i prefer usb)
su
cd /sdcard/Download
on my phone it always downloads it as a .jpeg rename it to .shar
mv debian-kit-1-6-testing.jpeg debian-kit-1-6-testing.shar
sh debian-kit-1-6-testing.sharAnswer Y to unpack
read the menu, then choose 0j (wheezy does not work in this script, don’t want it anyway)
it will now create /sdcard/debian.img (512mb) (will take a couple minutes)
next it will mount the image
next it will debootstrap a basic installation of jessie to the image (this takes a long time, ~30 minutes)
you might see an error “cannot create symlink…” that’s good, we don’t want to touch /system anyway
once its done. copy that debian.img from your phone to your computer
adb pull /sdcard/debian.img .we also need everything it unpacked to /data/local/deb
mkdir deb
adb pull /data/local/deb ./deb
unplug phone and plug in the watch, then push those to the watch
adb push debian.img /sdcard/
adb push deb /data/local/debian will not have internet access, the watch has no wifi. need to figure out how to forward over bluetooth
now what? check out this page: sven-ola.dyndns.org/repo/debian-kit-en.html
Also, the best Fastboot Doc ever: wiki.cyanogenmod.org/w/Doc:_fastboot_intro
Thanks for the Info
If I backup the files, would I be able to flash those same files back to recover the device ,kinda like a unbricking method. Coudlnt I do it though fastboot ?
Sent from my LG-D851 using XDA Premium 4 mobile app
Froz3nsolid said:
Thanks for the Info
If I backup the files, would I be able to flash those same files back to recover the device ,kinda like a unbricking method. Coudlnt I do it though fastboot ?
Sent from my LG-D851 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The IMAGES (boot.img, etc) can be flashed from fastboot:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
However, there is no way (that i have found yet) do dump images using fastboot; dumping must be done on the device itself
updating op...
Thanks
Sent from my LG-D851 using XDA Premium 4 mobile app
I got my hands on a ls660 finally. It is possible to use send_command.exe to flash and backup the phone. I already tested this myself.
There is no need to zero your laf partition to enter fastboot to flash twrp!
1. copy the twrp bumped image on the sd card
2. cd into the folder that you have the send_command.exe stored.
3. with your ls660 turned off hold volume up and plug in the usb data cable
4. after the phone is in download mode send this command to the apropriate diag port:
Code:
Send_Command.exe \\.\COM14
The phone will show
Code:
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
6. This command backs up your recovery image and names it OGrecovery:
Code:
dd if=/dev/block/mmcblk0p17 of=/storage/external_SD/OGrecovery.img
7. This command flashes your phone with the twrp image:
Code:
dd if=/storage/external_SD/recovery_bumped.img of=/dev/block/mmcblk0p17
8. Send the following command in all caps:
Code:
LEAVE
When you reboot to recovery you should load twrp recovery.
its a problem.i ported a rom but im scared to test it! because im worry that the rom doesnt boot and i stuck there or my device brick!how to fix it if it happens?ty
my device is:leeco coolpad cool 1
If you keep making threads like this one you will get banned !
Use adb to backup your stock rom
(Make sure to have enabled usb debugging )
How to:
- Run adb shell and then su and accept the root access dialog
- Then run 'ls -al /dev/block/platform/msm_sdcc.1/by-name' to get the partition table (we need to find the location of boot and system)
- Run 'dd if=/dev/block/mmcblk0px of=/sdcard/boot.img' replace the x in mmcblk0px with the corresponding number of the boot partition, for example, for my device it is 14. Now we have backed up the kernel (boot).
- Run 'dd if=/dev/block/mmcblk0px of=/sdcard/system.img' and replace the x in mmcblk0px with the corresponding number of the system, for example, for my device it is 23. Now we have backed up the system.
How to restore:
- You can use fastboot flash (fastboot flash boot boot.img and fastboot flash system system.img)
- You can use adb (dd if=/sdcard/boot.img of=/dev/block/mmcblk0px and replace x with the corresponding partition bla bla you know )
Good luck
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please make sure you read and understand everything written in the post before flashing it! YOU are choosing to make these modifications and must be sure of what it does
This guide is only working on Pace 1!
This guide will give you a way to preview version 2.0.6.12 on your device. The Rom has no OTA, so you'll have to wait for a thread update.
If you like my work you can buy me a cheescake: https://www.paypal.me/JRevenge
P.S The Rom is only in Chinese or partly in English
Guide:
Requirements
Unlocked Bootloader: if you don't have the bootloader unlocked, you can apply here https://nicolasagliano.com/lo-sblocco-del-bootloader-e-arrivato/
Cables: Charging base with NOT original cable (it is very important)
Drivers: It is very important to have the adb / fastboot drivers installed, if you don't have them, follow this guide https://forum.xda-developers.com/showthread.php?t=2588979
Health: A lot of calm and experience!
Installation
1. You need to download the following package and unpack it in the adb folder (it is normally found in c: \ adb)
2. Connect the Pace to the computer using its charging base and the micro-usb cable (it is very important that the PC sees the internal memory of the device in the exploration of resources)
3. Open the Windows command terminal and enter the following command
Code:
C:\adb
4. Once you are inside the adb folder, you will need to enter the following commands
Code:
adb shell reboot bootloader
By doing this, the device will enter the fastboot mode (you will notice it from the Pace screen)
5. Now it's most important flash the recovery image, enter the following commands
Code:
fastboot boot rec.img
6. Now wait for the device to restart (it takes a few minutes)
7. Now in sequence, the following commands:
Code:
adb root
adb remount
8. Now it's time to copy data into the device, typing these commands:
Code:
adb push boot.img /data/media/0/
adb push system.img /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/
Once you have copied the files (system will take a while to copy) you will have copied all the files
9. Enable root permissions
Code:
adb shell
10. Put this command in sequence:
Code:
cd /data/media/0/
sh flash_rom.sh
11. Wait for the end of the installation and restart with the following command
Code:
adb reboot
If you want to have English as a language, partially, after the first start, you will have to give the following command:
Code:
adb shell setprop persist.sys.language en
adb reboot
Now the installation is finished! Congratulations!
I thank @Cracklydisc (Nicola) for contributing to the installation instructions.
I will try to update the post more often based on the release of updates. Also below you can download the updated version of the application (in step with the developer path)
N.B For Italians who will install it, it will be in Italian, for others in English
It is possible to download it at the following link (2.4.0 version)
Reserved
If you want to see some photos and some comparison with the Stratos, you can do it at the following link
If you want to stay up-to-date on the Amazfit world, you can follow this Telegram channel (it's currently being created)
If you want help on the international group on Facebook, follow this link
Thank you for sharing the files and the info. A few questions:
- Can it be installed over any other Pace firmware, either stock or custom?
- The only files that are flashed are the kernel and system, no other firmware files are needed, like recovery?
- What is the recommended Amazfit app to be used with it? Latest CN version, latest DEV CN or any is fine?
- Finally, the linked AmazIT 2.4.0 corresponds to what Amazfit app?
thank, i try tonight
fastboot boot rec.img error to many link ?? how to fix
Just some info, fastboot boot rec.img does not flash the rec.img, it just boots the image that you send to the device.
There are some problems with the flashing files
1. the rec.img does not work correctly, it just hangs in fastboot and doesn't restart the device as root in adb. I used a different boot image to gain root access.
2. the md5 signature for boot.img that is stored in md5s.txt does not match the real md5 signature of boot.img. I manually modified it to get past the check in flash_rom.sh.
3. the command for copying system.img in flash_rom.sh is wrong.
in the file, the command is "dd if=system.img | dd of=/dev/block/platform/jzmmc_v1.2.0/by-name/system bs=4096"
but it should be "dd if=system.img of=/dev/block/platform/jzmmc_v1.2.0/by-name/system bs=4096"
brmbjn said:
fastboot boot rec.img error to many link ?? how to fix
Click to expand...
Click to collapse
Hello
Two issues for me:
- fastbboot boot rec.img : error two many links. I used old Amazfit-mod-recovery.img from Neuer_User to boot in Recovery-
https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
- md5 sum check error with boot.img : deleting check of md5 sum in flash_rom.sh (Validating images part) - not recommanded!
Thanks JRevenge, Firmware is good, and almost everything is in English.
Armageda said:
1. the rec.img does not work correctly, it just hangs in fastboot and doesn't restart the device as root in adb. I used a different boot image to gain root access.
2. the md5 signature for boot.img that is stored in md5s.txt does not match the real md5 signature of boot.img. I manually modified it to get past the check in flash_rom.sh.
3. the command for copying system.img in flash_rom.sh is wrong.
in the file, the command is "dd if=system.img | dd of=/dev/block/platform/jzmmc_v1.2.0/by-name/system bs=4096"
but it should be "dd if=system.img of=/dev/block/platform/jzmmc_v1.2.0/by-name/system bs=4096"
Click to expand...
Click to collapse
how did you modified the md5? how did you find the right md5?
yuv78 said:
how did you modified the md5? how did you find the right md5?
Click to expand...
Click to collapse
in linux, just use md5sum <file>. this will give you the md5 hash of the file.
Fastboot boot too many links too here...
Are you sure of your instructions ? Seems strange = no recovery flashed in the process...
Good md5 : F0C9357B882C3AF11BB81815F39BDF9C boot.img (replace in md5 file)
Boot another recovery
updating/checking
Thanks for your efforts and just a quick feedback:
Running on an international ROM Stratos4Pace v0.1b2_2.3.0.8 my first step was to unpair the watch from the Playstore Amazfit app.
After changing the md5 of boot.img and adopting the flash_rom.sh as stated previously the ROM installed fine (I skipped booting rec.img since I was running a rooted rom [Stratos4Pace v0.1b2_2.3.0.8]).
Paired it with the AmazIt app afterwards, which connects to a Mifit Account I previously created.
Had some problems with setting the watch to english but after a while it worked with the following commands (which seems essentially the same like written in the first post).
adb shell
setprop persist.sys.language en
exit
adb reboot
Lost my previous tracks in the Mifit app since I was before on the international ROM (no regrets).
ROM doesn't have Root!
Edit: Settings - About is crashing my settings, otherwise English translations seem to be working fine.
nhedgehog said:
Thanks for your efforts and just a quick feedback:
Running on an international ROM Stratos4Pace v0.1b2_2.3.0.8 my first step was to unpair the watch from the Playstore Amazfit app.
After changing the md5 of boot.img and adopting the flash_rom.sh as stated previously the ROM installed fine (I skipped booting rec.img since I was running a rooted rom [Stratos4Pace v0.1b2_2.3.0.8]).
Paired it with the AmazIt app afterwards, which connects to a Mifit Account I previously created.
Had some problems with setting the watch to english but after a while it worked with the following commands (which seems essentially the same like written in the first post).
adb shell
setprop persist.sys.language en
exit
adb reboot
Lost my previous tracks in the Mifit app since I was before on the international ROM (no regrets).
ROM doesn't have Root!
Click to expand...
Click to collapse
Being an official Rom, it doesn't have root permissions. If you come from an official Rom, you need to install the temporary root of STRATOSfied
I'm a control freak - can I root it myself somehow permanently?
nhedgehog said:
I'm a control freak - can I root it myself somehow permanently?
Click to expand...
Click to collapse
Since this is an official ROM, no, unless someone find a way to hack it.
You can obtain a temporary root with a crafted boot image, and it will last until the next reboot.
Armageda said:
Since this is an official ROM, no, unless someone find a way to hack it.
You can obtain a temporary root with a crafted boot image, and it will last until the next reboot.
Click to expand...
Click to collapse
Exactly!
Just one issue, Rom version is 2.6.0.12 instead of 2.0.6.12
I switch rec.img with Amazfit-mod-recovery.img
changed md5s.txt and flash_rom.sh with the attachments and used the tutorial on the fist post all went well
adb shell reboot bootloader
fastboot boot Amazfit-mod-recovery.img
adb root
adb remount
adb push boot.img /data/media/0/
adb push system.img /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/
adb shell
cd /data/media/0/
sh flash_rom.sh
adb reboot
thanks for the rom, its great
:good::good:
Success!!!
Hernanis75 said:
I switch rec.img with Amazfit-mod-recovery.img
changed md5s.txt and flash_rom.sh with the attachments and used the tutorial on the fist post all went well
adb shell reboot bootloader
fastboot boot Amazfit-mod-recovery.img
adb root
adb remount
adb push boot.img /data/media/0/
adb push system.img /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/
adb shell
cd /data/media/0/
sh flash_rom.sh
adb reboot
thanks for the rom, its great
:good::good:
Click to expand...
Click to collapse
That was the way for me BUT not with windows 10. Linux BAM BAM!!!
hello all
i have a gigaset GS 270 plus, and everything i try to do on it fails
i backed up the data on my sd card using the recovery , but on restoring on an identical phone (trait for trait) it says "the backup file is out of date please rebackup your data
on the source phone i tried the same process and it went on smoothly but i cant risk formating, rooting , enabling adb, restoring and removing pasword because of the above problem.
i have 13 backup files of up to 25 gigabytes which i am unable to recover or decrypt on a pc even following the commands given on linux from this thread
https://forum.xda-developers.com/showthread.php?t=2408788&page=2
the phone connects in fastboot mode but not in adb mode
Fortunately it is a mediatek device and i have tried to back up the rom using this tutorial
https://android.stackexchange.com/q...nd-full-rom-without-root-for-mediatek-devices
but all to no avail
i tried a readback of my rom using help from @Alecxs using WwR MTK v2.51 from Ilya Aleksandrovich
but upon creating the scatter file it gives an error
https://ibb.co/Sd3HTfM
please i need anyhelp whatsoever to recover the files from the phone either by a readback or by unlocking the phone or any other method which i have not thought of
Thank you in advance!!!
search for stock ROM, use that preloader.bin
https://forum.xda-developers.com/showthread.php?t=3775129
https://forum.xda-developers.com/showthread.php?t=3899918
yet another instructions for exactly the same like the link you shared
how to create scatter file
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post77795016
aIecxs said:
search for stock ROM, use that preloader.bin
Click to expand...
Click to collapse
yeah, i thought of that too
i already tried searching but i was unable to find any rom except click baits
aIecxs said:
https://forum.xda-developers.com/showthread.php?t=3775129
https://forum.xda-developers.com/showthread.php?t=3899918
Click to expand...
Click to collapse
thank you let me try
Maybe that device has secure boot preventing SP Flash Tool from readback, try another download agent
we can help you porting TWRP but we can't help on readback, you are the only one who has physical access. if you follow the tutorial and it fails, maybe the tutorial is not working for this device
if you are using windows 10, try another PC with Windows 7 or try SP Flash Tool for Linux
edit: there are other methods for creating scatter file. post the output of fastboot getvar all
belvo02 said:
aIecxs said:
No, except you do a readback of metadata from SP Flash Tool. Note when login credentials are involved in encryption, you won't be able to decrypt even on rooted device
port TWRP recovery from Cubot X18 Plus and flash on locked bootloader, that's (besides official solutions) your best option to remove screen lock
Click to expand...
Click to collapse
do you have any suggestions for me?
i want to try dr fone but i dont think it supports gigaset smatphones
i need a method to remove the screen lock without loosing the data ,:sad:
i even got the same phone , i was planning to root it , restore the backup and then use twrp to remove the lock
but it says "the backup file is out of date please rebackup your data"
any method to recover this files s welcome, if i could get even just the pictures and videos, can any thing help me?
im going to try to connect it to sp flashtools and try what you said earlier
thank you for replying
Click to expand...
Click to collapse
you have two devices of same model? great, let's root the spare phone!
take away the source phone for now (the important one)
Do on the target phone only:
WARNING: factory reset - all data lost!
1) unlock the bootloader
- enable developer options by tapping build number seven (7x) times (in settings - about phone)
- enable OEM unlocking in developer options
- install platform-tools and connect device to PC in fastboot mode (Volume Down + Power)
- install usb drivers and check usb connection (from platform-tools directory in cmd.exe)
- unlock bootloader and confirm with Volume Up (factory reset)
Code:
fastboot devices
fastboot flashing unlock
fastboot reboot
2) temporary root device
- enable developer options
- enable usb-debugging
- connect to PC and install usb drivers
- check adb devices (from platform-tools directory in cmd.exe)
- on the phone display permanently authorize the incoming RSA key
- download mtk-su to PC
- adb push binary to /data/local/tmp
- chmod executing permissions
- run the binary until you see # prompt (multiple times)
Code:
adb push mtk-su /data/local/tmp
adb shell
cd /data/local/tmp
chmod 0755 mtk-su
./mtk-su
3) backup boot.img / recovery.img
- get list of partitions
- dump partitions into files (in # shell)
- copy files to Internal storage
- copy files to PC (via MTP)
Code:
ls -d $(find /dev/block -name by-name)/*
cat /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/boot > boot.img
cat /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/recovery > recovery.img
cp -v *.img /sdcard
4) root device with Magisk Manager
- install Magisk Manager
- open the app
- advanced settings - preserve force encryption
- keep avb/dm-verity
- tap install (2x) times
- select and patch a file - boot.img
- copy magisk_patched.img to PC
- reboot into fastboot
- flash the patched boot
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
5) create your own TWRP recovery
... to be continued
(send me recovery.img will try to make TWRP and you can test)
edit: please do not full quote this post (i want update later). i will receive instant notification for answer button as well
aIecxs said:
you have two devices of same model? great, let's root the spare phone!
take away the source phone for now (the important one)
Do on the target phone only:
WARNING: factory reset - all data lost!
1) unlock the bootloader
- enable developer options by tapping build number seven (7x) times (in settings - about phone)
- enable OEM unlocking in developer options
- install platform-tools and connect device to PC in fastboot mode (Volume Down + Power)
- install usb drivers and check usb connection (from platform-tools directory in cmd.exe)
- unlock bootloader and confirm with Volume Up (factory reset)
Code:
fastboot devices
fastboot flashing unlock
fastboot reboot
2) temporary root device
- enable developer options
- enable usb-debugging
- connect to PC and install usb drivers
- check adb devices (from platform-tools directory in cmd.exe)
- on the phone display permanently authorize the incoming RSA key
- download mtk-su to PC
- adb push binary to /data/local/tmp
- chmod executing permissions
- run the binary until you see # promt (multiple times)
Code:
adb push mtk-su /data/local/tmp
adb shell
cd /data/local/tmp
chmod 0755 mtk-su
./mtk-su
3) backup boot.img / recovery.img
- get list of partitions
- dump partitions into files (in # shell)
- copy files to Internal storage
- copy files to PC (via MTP)
Code:
ls -d $(find /dev/block -name by-name)/*
cat /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/boot > boot.img
cat /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/recovery > recovery.img
cp -v *.img /sdcard
4) root device with Magisk Manager
- install Magisk Manager
- open the app
- advanced settings - preserve force encryption
- keep avb/dm-verity
- tap install (2x) times
- select and patch a file - boot.img
- copy magisk_patched.img to PC
- reboot into fastboot
- flash the patched boot
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
5) create your own TWRP recovery
... to be continued
(send me recovery.img will try to make TWRP and you can test)
Click to expand...
Click to collapse
thanks im on it!
Thanks a lot @aIecxs for the posting, tried with a Gigaset GS270 but the mtk-su is not working:
1|Gigaset_GS270:/data/local/tmp $ ./mtk-su -v
Failed critical init step 1
Any workaround to get this device rooted?
Best regards