Related
Mod Edit: Unstickied, placed link in wiki:http://forum.xda-developers.com/wiki/index.php?title=Nexus_One Thanks
This is an alternative approach of rooting the Nexus without touching the bootloader.
-no downgrade neccessary
-no battery modification neccessary
-no messing around with SD card slot
-you don't even have to open your phone...
Working and confirmed for ALL ROMs, including European Vodafone EPF30/FRF91, Korean FRF91, AT&T/T-Mo Stock including FRF91
-------
Credits:
-------
- The Android Exploid Crew:
http://c-skills.blogspot.com/2010/07/android-trickery.html
- Amon_RA
- cyanogen
-------
Notes:
-------
- The exploit wasn't found by me (see credits), I just implemented it as a proof of concept for the Nexus One
- Basically this method should work on all currently known ROM versions.
- I tested it on EPF30, Korean FRF91, Vodafone FRF91, US Stock FRF91.
- As usual when doing this kind of stuff: DO THIS AT YOUR OWN RISK.
- It could even work on other Android devices as long as their system partition is at
/dev/block/mtdblock3/ with yaffs2 file system and there is still some space left on the system partition (without any changes).
-------
Prerequisites:
-------
- Locked Nexus One
- Latest Android SDK incl. USB drivers
- Working ADB
- The file "freenexus.zip"
edit:
get it here:
http://multiupload.com/MVT98F5HBY
or
http://dl.dropbox.com/u/1327667/freenexus.zip
MD5: 947C20222056D7C070733E7FCF85CF15
-------
Step-by-step guide:
-------
1. install android sdk & USB drivers
2. extract the content of the zip file into the tools directory of SDK (i.e. \android-sdk-windows\tools)
-> For all Newbies: Take care that you extract the files directly to the tools folder and don't create a new subdirectory freenexus within tools!!! If you did, delete the folder and extract again!!! Check twice that there is no FOLDER freenexus in your tools directory before you continue!!!
3. open a command prompt (Windows: Start, Run, "cmd", OK; Linux: Terminal)
4. change to SDK tools directory (i.e. cd \android-sdk-windows\tools)
5. connect Nexus to USB and check if debugging mode is activated
(Settings/Application/Development/USB Debugging)
6. run "adb devices" in shell and see if there is a device listed. if not back to step 5 or reinstall USB-drivers
7a. for Windows: run "freenexus.bat" in command shell (this copies the neccessary files to /data/local/tmp)
7b. for Linux or manual installation: run the following commands
Code:
adb push freenexus /data/local/tmp/freenexus
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb shell chmod 755 /data/local/tmp/freenexus
adb shell chmod 755 /data/local/tmp/busybox
8. run the following commands:
Code:
adb shell
(you should see a "$" prompt now)
cd /data/local/tmp
9. on your phone go to a screen where you can easily toggle wifi (widget or settings/wireless)
10. be prepared to toggle wifi immediately after you execute the next step
11. run
Code:
./freenexus
12. toggle wifi on
13. you should see something like that:
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by ak for HTC Nexus One
[+] Using basedir=/sqlite_stmt_journals, path=/data/local/tmp/freenexus
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.
13b) if you get "permission denied" error, you have most likely not followed the big red newbie hint after point 2. check this by entering "ls -l", if you see a "drwxr-xr-x" and not "-rwxr-xr-x" in front of the line where freenexus is listed you did not follow properly. Search the posts in the thread on how to correct this.
14. run
Code:
rootshell
15. if you succeeded you will be asked for a password, if not try again from step 10
16. enter the password "freenexus"
17. now you should see a "#" as a prompt -> you are root now
18. run the following commands:
Code:
./busybox cp busybox /system/bin
chmod 4755 /system/bin/busybox
busybox cp Superuser.apk /system/app
busybox cp su /system/bin
chmod 4755 /system/bin/su
rm /system/bin/rootshell
exit
exit
19. Check if you keep root rights:
Code:
adb shell
su
20. after you executed the su command the Superuser app on your device should ask you for allowance
21. you should see the "#" prompt again, if you didn't get that try su again
22. done
-------
Comments:
-------
- General
If you are not planning to wipe your data partition (what you probably will do when installing CM6 first time) you should think about deleting all the temp files still lying in /data/local/tmp (for safety reasons and to have more space on /data):
Code:
adb shell
cd /data/local/tmp
rm busybox
rm su
rm Superuser.apk
rm freenexus
rm flash_image (will only exist if you executed the steps below in recovery section)
- Installation of Custom Recovery
If you only want root rights you are done here. If you want to install custom ROMs you have to install
a custom recovery first. Easiest way would be to download "ROM Manager" from the market. There are plenty of tutorials on how to install custom recovery/ROM at xda.
Edit: It is safer to install the recovery manually. In this case or for those of you running into problems with installing custom recovery with ROM Manager (doesn't stick) you can continue with
these steps (without remount of system partition, now tested successfully):
1) Download recovery-RA-nexus-v1.7.0.1.img to the root directory of your SD-Card
- Note: UnMount your SD-Card after copying these files, but keep your phone plugged in
- or don't mount SD-Card at all and push the file via adb to /sdcard
2) Save file "flash_image" to sdk tools directory:
3) In your terminal run
Code:
adb push flash_image /data/local/tmp/flash_image
adb shell
su
- At this point, it will hang until you choose "Allow" on your phone with the SuperUser app pop-up
- $ should now be replaced with #
5) run the following commands:
Code:
[COLOR="Red"]mount -o rw,remount /dev/block/mtdblock3 /system[/COLOR]
cd /data/local/tmp
chmod 755 flash_image
[COLOR="Red"]./flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1.img[/COLOR]
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
(and if everything worked fine:)
rm flash_image
Alternatively you can continue with step 9 and then steps 16-24 from the old rooting method tutorial
to manually install Amon_RA's recovery. You will also need the file flash_image for that (link taken from HBOOT thread).
- HBOOT
If you rooted from a Korean Rom or have installed the latest Vodafone Rom via PASSIMG you probably have
HBOOT 0.35 which makes it currently difficult to install Cyanogenmod (there is an assertion failure in the install script, at least with CM6 RC1/2. Maybe future versions of CM6 will include HBOOT 0.35 in the script) or other custom ROMs. (You are still on 0.33 if you just installed the Vodafone OTA Update)
There is a tutorial to revert HBOOT here:
http://forum.xda-developers.com/showthread.php?t=726258
Instead of using the EPF30 image you can also use any other PASSIMG file (at least if it has HBOOT 0.33,
otherwise this step wouldn't make sense...)
Note that when flashing a PASSIMG with a different HBOOT version there is a reboot after the HBOOT has been flashed, then after reboot the PASSIMG will be loaded again and the rest of the image will be flashed.
To check HBOOT and Radio version: press and hold trackball while turning on the phone. To exit select Reboot with Vol+/- and press Power button.
Caution:
After you have reverted your HBOOT, you have lost your root rights and you are back on stock recovery.
But you can (or have to) repeat the above procedure to get root rights back.
Edit:
The downgrading also downgrades your radio!!! Before installing CM6 you have to flash a Froyo Radio!
Latest one can be found here:
http://forum.xda-developers.com/showthread.php?t=723839
-------
Troubleshooting:
-------
After trying to flash a custom ROM with ROM Manager one user wasn't able to boot the phone normally and also no longer able to boot to recovery. In this rare case try to download a compatible PASSIMG file:
For example EPF30 (Europe Vodafone 2.1)
http://shipped-roms.com/shipped/Pas...ogle_WWE_1.14.1700.1_EPF30_release_signed.zip
or FRF91 (Europe Vodafone 2.2):
http://shipped-roms.com/shipped/Pas...on_VF_2.15.151.5_R_FRF91_MFG_Shipment_ROM.zip (<-this one is currently a zip in zip. You have to extract it once to get the working PASSIMG.zip)
(Appropriate US-PASSIMGs can also be found on shipped-roms.com, most likely EPE76)
Rename the file to PASSIMG.zip (case sensitive, Windows users take care that the file isn't called PASSIMG.zip.zip hidden extension)
Copy it to main folder of SD card.
Boot phone into Bootloader mode (press and hold trackball when turning on the phone, until fastboot mode starts)
Select Bootloader mode by pressing power button.
The bootloader should then start to analyse the PASSIMG.zip and ask you afterwards to install it.
You're phone (not your SD) will be completely wiped after the procedure but should work again (and can be rooted again...)
sweet!! been waiting for this! will try it tomorrow as soon as i wake up! will report back then!
edit: i cant download freenexus.zip maybe use another hoster?
file section edited.
Great tutorial ! Waiting for some feedbacks
(file link doesn't work)
dolomiti7 said:
file section edited.
Click to expand...
Click to collapse
On the left I can see just an empty folder named "SmartDrive"
link doesn't work
dolomiti7 said:
-> after clicking on "Smartdrive Gastzugang starten" you might get an error message, but after klicking ok on the error message
you should be able to access the folder "nexus" on the left side of the window anyway
Click to expand...
Click to collapse
No way! Can't do anything even after i press ok on the error message
if you click on that there should be a subfolder "nexus" that should be clickable too. at least it works here... anyway. someone wants to upload the file to a hoster? rapidshare... contact me
for the early adaptors (will only work 10 times):
rapidshare.com/files/409266634/freenexus.zip
MD5: 947C20222056D7C070733E7FCF85CF15
multiple download sites!:
http://www.multiupload.com/MVT98F5HBY
or here:
http://dl.dropbox.com/u/1327667/freenexus.zip
thank you. added the link.
This worked flawlessly.
Massive thanks.
Hi, I have a Italian Vodafone Nexus One with FRF91, i have followed all the steps and now in my apps there is Superuser Permission with green light. It means that i have root rights? Can I install Cyanogen Mod now? Thanks, excuse my English.
Worked perfectly on a stock AT&T N1 with FRF91. Thanks!
Excellent tutorial step by step...great work!
Can i change the password at the end?
So once gaining root, I can flash a custom recovery with rom manager without braking/unlocking the boot loader?
@fc_themaster:
if the superuser app popped up at step 19/20 then you have root rights. you can try to install ROM Manager from the market and install a custom recovery with that porgram. it also needs root rights so superuser should pop up again at that point.
@PSeeCO: you don't need to change a password. the password was only used for the temporary rootshell which you (hopefully) deletetd with the command "rm /system/bin/rootshell" in step 18. From that point on root rights are controlled via the Superuser app. If you install an already rooted custom ROM it is obsolete anyway.
@jivemaster: yes, we can! just use ROM Manager from the market to install custom recovery.
dolomiti7 said:
@PSeeCO: you don't need to change a password. the password was only used for the temporary rootshell which you (hopefully) deletetd with the command "rm /system/bin/rootshell" in step 18. From that point on root rights are controlled via the Superuser app. If you install an already rooted custom ROM it is obsolete anyway.
Click to expand...
Click to collapse
Perfect, thank you so much!
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 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!!!
Hi folks,
I couldn't get any of the flashable swipelib zips I've found to actually install properly on Lineage 15.1 for pioneer, so I packaged up the arm64 libs into a zip and wrote a small installer script that uses adb to get root, remount partitions r/w, and push + chmod the correct files. Note that you do not need addonsu for ADB root shell access, enable that in Settings -> Developer Options -> Root Access (after enabling USB Debugging).
Instructions
Unzip the archive, make reinstall-swipelibs.sh executable if necessary (chmod +x reinstall-swipelibs.sh), and run the script. The rest should work assuming you've got adb setup properly.
Notes
I included the original A/B updater script and the (apparently installable?) zip of the swipe libs for different architectures. Therefore, if you need different archs for some reason, just extract and replace the .so's in the base directory with the appropriate ones from the original zipfile, then run the script - if you do so, you will need to change the paths in 05-swipelibs.sh to reflect either 'lib/' (for arm) or 'lib64/' (for arm64) respectively and push it back to the phone (-> re-run the included script).
Link
https://drive.google.com/open?id=1wmHbj47YIgWUg7DU6CQ2EpMOIIQtEvRH
Best of luck!
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