Related
Ive noticed many people with older TWRP versions having problems with the updater script when installing 4.4 roms you need to be on the latest version of twrp (CWM may also need to be on a recent version). This tutorial will cover TWRP. Goo manager will not work for installing the latest TWRPrecovery version on tilapia. The following will give you the basics on how to use fastboot to flash a recovery.img (In this case twrp)
Things you will need:
A PC
Android SDK http://developer.android.com/sdk/index.html
TWRP recovery.img for tilapia http://techerrata.com/browse/twrp2/tilapia
A basic understanding of terminal/command prompt
You will need a PC and the android SDK (SDK http://developer.android.com/sdk/index.html) for fastboot to push the recovery file. TWRP can be found here (http://techerrata.com/browse/twrp2/tilapia) you need the 2.6.3.0 version. Extract your android sdk and move your twrp image file (openrecovery-twrp-2.6.3.0-tilapia.img) to the platform-tools folder in the sdk (This is where fastboot/adb are). For simplicity's sake rename your twrp file to recovery.img Enter command prompt or terminal depending on what OS you are using (windows/linux) and navigate to to your platform-tools folder in the SDK folder (where you should have moved your recovery.img) using the cd command. (plug device in) Once there check to see if you device is connected and seen with the adb devices command hopefully you will see a wonky alpha numeric code with "device" after it. If you dont you need to enter developer setting to enable adb. You do that by going into settings/about tablet and tapping build number 7 times. That should give you a developer options in settings check to make sure USB debugging is enabled. If all is well reboot your device into the boot loader with the adb reboot bootloader command once your device is at the bootloader check fastboot with fastboot devices you should see another wonky output with "fastboot" after it. The final command to push your new twrp image will be fastboot flash recovery recovery.img You should see some output saying how long it took to push the file it should not take that long. That should cover it! Now you should be good to go with the 4.4 rom's floating around.
This is a straight AOSP build with the 4.3 binary's. It should be the same as the other AOSP build so auto rotate does not work and the APN must be manually entered there is also a issue with the keyboard opening when hitting the home button.
ROM: http://d-h.st/nJ3
GAPPS: http://www.mediafire.com/folder/gxxxpkbcke4yi/PA_GApps_-_Official_Releases
There are many tutorials online explaining this process I just thought customizing it to the tilapia would help those less comfortable with adb/fastboot. It's always a good idea to know how to use these tools you never know when you might need to use them. Anyone with question's feel free to ask.
if you dont mind, im going to post the twrp info on my threads op
swordrune10 said:
if you dont mind, im going to post the twrp info on my threads op[/QUOTE
Don't mind at all.
Click to expand...
Click to collapse
Worked perfectly. Thanks!
Thought I would add this small guide here as I’ve been trying to find something similar and didn’t.
Before I start-off, All the credits go to the amazing XDA Developers and their respective mods, as things would’ve never been this easy or straight-forward without their dedication and hard work. Namely @bunny0007 , @intersectRaven , @invisiblek and @Tomsgt
Having both the LG G Watches, It was only a matter of time that I too wanted the new OTA Updates, so as to use the sort-of-amazing features it promised. Now being on a Stock-rooted 5.1.1 firmware from @bunny0007 and running a Custom Kernel from @intersectRaven, I was told that it wouldn’t be possible to get the OTA installed even if it popped-up (Well it would install, but not actually show anything) This I tried, But when the watch rebooted; it showed a dead android bot with an exclamation over it’s guts! Which to me meant, things weren’t apparently going in the right direction. After a couple of trials, this* is what eventually worked ...
*A word of caution before you proceed, this worked for me and “might” not work for you. So if your watch gets nuked or bricked (which again, I highly doubt it would), it ain’t my fault but yours and murphy’s alone!
Now that’s out of the way, Let’s make sure we have the bare necessities such as:
A PC that can run ADB and Fastboot Commands using CMD, usually Installed by:
◦ The 15 Seconds ADB Installer - XDA Post
◦ The Android SDK Platform Tools - link
◦ The Necessary Google Drivers - link
The Stock 5.1.1 (LDZ22D) Boot, Recovery and System images:
◦ For G Watch - link
◦ For G Watch R - XDA Post
The most recent TeamWin Recoveries
◦ For G Watch (dory) - link
◦ For G Watch R (lenok) - link
The Wear SuperSU, that can be used on both the watches - link
*Optional: The Custom Kernels
◦ For G Watch by @invisiblek - XDA Post
◦ For G Watch R by @intersectRaven - XDA Post
*Optional: The Advanced Settings App - Google Playstore
*These are strictly optional and are only based-off of my personal preferences. Feel free to install any custom kernel or tweaking apps of your choice.
TIP: If you need to flash a file from a particular folder, You can invoke CMD by holding the Shift Key and Right-click to see the Open command window here option.
1) Restoring to Stock & Relocking the Bootloader (This is only if you have unlocked your bootloader and have rooted previously)
a. Make sure, the watch is charged to a 100%, Can’t stress this enough!
b. Enable Adb Debugging on your watch. Eh, how?
Go to Settings > About.
Tap on the Build Number repeatedly until it says You’re a Developer.
Go back and tap on Developer options and Enable ADB Debugging.
As you place the watch on the cradle that is connected to your PC, you’ll be prompted to Are you sure?, Select Always allow from this computer and click OK.
Once you have downloaded and extracted the appropriate Image zip for your watch into a folder. You should see the following files: Boot.img, Recovery.img and System.img!
c. Now Access CMD will elevated privileges or in other words as admin and enter the following codes:
Code:
adb devices
Code:
adb reboot bootloader
Code:
fastboot devices
Code:
fastboot -w
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot oem lock
Code:
fastboot reboot
With the final command, the watch will reboot showing the Lg logo minus the lock sign, which means the bootloader has been locked. It should then continue onto boot into Android Wear. Yes, it’s going to take some time to complete, so be patient and let it do it’s thing.
2) Installing the OTA Update
Once the watch boots into android wear, Go through the initial setup and link it with your phone. Then go to Settings > About > System Updates, where you’ll see your new update being downloaded. When done, Accept to install and the watch will reboot to install the update without any issues. Once completed, It will upgrade the existing apps on the watch and boot into Android wear.
Congrats, You have now installed the new update!
3) Unlocking the Bootloader & Flashing TWRP
As with any other android device, You’ll need to unlock the bootloader to install a custom recovery. So enable debugging the same way as mentioned at the beginning of this guide. Invoke CMD and enter the following commands:
Code:
adb devices
Code:
adb reboot bootloader
Code:
fastboot devices
Code:
fastboot oem unlock
Code:
fastboot reboot
The watch will reboot showing the Lg logo with an unlocked sign, meaning the bootloader has been unlocked. Again, as it boots into android wear, Go through the initial setup and link it with your phone. Enable Adb Debugging, Invoke CMD and enter the following commands:
Code:
adb devices
Code:
adb reboot bootloader
Code:
fastboot devices
Code:
fastboot flash recovery twrp-2.8.7.0-lenok.img
Now on the watch, using the < O > keys, select Recovery Mode and press the O key to enter into TeamWin Recovery. This is required to be done only once, because if you directly reboot after flashing the recovery, there are chances it won’t work. Proceed to reboot by pressing the Reboot button in TWRP.
4) Sideloading SuperSU and Installing it using TWRP
Once the watch has booted back up, Invoke CMD and enter the following commands to push SuperSU zip & to reboot into recovery:
Code:
adb devices
Code:
adb push Wear-SuperSU-v2.40.zip /sdcard/
Code:
adb reboot recovery
Now on the watch, You should be in TWRP. Select Install and scroll down to find the zip and swipe to flash. It will show as successful and proceed to reboot.
Congrats, You are now rooted and how do you check you are? Once the watch has rebooted into android wear. Invoke CMD and enter the following commands:
Code:
adb devices
Code:
adb shell
Code:
su
5) Install the Custom Kernel (Optional)
This is more of an individual choice on which custom kernel you want to use, As it depends on how you use the watch. Myself being a light user, I use the single core vr of the custom kernel from the dev @intersectRaven to make it more battery friendly. Invoke CMD and enter the following commands:
Code:
adb devices
Code:
adb reboot bootloader
Code:
fastboot devices
Code:
fastboot boot single.boot.img
That is, If you want to boot the image temporarily, but this will reset to stock after a restart or
Code:
fastboot flash boot single.boot.img
Code:
fastboot reboot
6) Install Advanced Settings (Optional)
This free tiny little app has been a lifesaver and gets updated often with new features. There are lots of things you can configure and tweak without the need to edit manually via adb.
Guess I’m done then, I hope this guide helps someone in some way And also to get the best out of their watch …
Thanks mate this was really nice of you, thumbs up
The recoveries I post are and tested for Lenovo Z2 Zuk Z2 Pro ONLY!
Requirements:
Unlocked phone bootloader
and your phone booted in fastboot mode, otherwise it will not work.
Recovery.img is the same recovery found on Lenovo forums (link below)
Download from MEGA
Mega
Images are in thumbnails, click on them to enlarge
Short guide:
1) Simply extract the zip
2) Open cmd.exe and cd to the directory you extracted
3) Put your phone in fastboot mode by shutting down your phone, if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
4) Paste the following commands:
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
You should get the same results I got:
Long guide for newbies with Windows 10 [the same might be for Windows 7/8]:
1) Download the zip I have uploaded and extract it to a folder with your favorite archive manager [I use WinRAR] and open it
2) Hold Shift and Right Click on empty space in the folder
3) Left click on Open command window here or open command prompt here
4) Put your phone in fastboot mode by shutting down your phone, power it on and if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
5) Paste the following commands by copying one line each time
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
Contents of Uploaded RAR/Zip Archive:
adb.exe & fastboot.exe taken from adb-setup-1.4.3 zip/rar file, which was found on Google, don't have a source link
drivers where taken from ZUK_UsbDriver_1.0.6 zip/rar from a guide which was found on google, don't have a source link
recovery images where taken from the sources below
Sources & Thanks:
Recovery 3.0.8 was taken from:
https://forum.xda-developers.com/le...t/twrp-recovery-zuk-z2-standard-pro-t3415395/
credits go to @raimondomartire
Recovery 3.1 was found on official Lenovo Forums:
http://bbs.lenovomobile.cn/z2pro/t508552/
Google translated Lenovo Forum Page:
https://translate.google.com/transl...n&u=http://bbs.lenovomobile.cn/z2pro/t508552/
Q&A:
Q: I do the same steps you did, in command prompt after pasting your commands I get the following: "< waiting for device >
or I wait for long periods of time or I get a [ERROR] message
A: Chances are 100%, you have the wrong drivers or not drivers installed, most devices use their own drivers for fastboot mode or adb/fastboot commands
If you have a Lenovo Zuk Z2 Pro like me, your device needs to be identified as "ShenQi Composite ADB Interface" in device manager.
Not "Android" or "Android ADB Interface" and because of that fastboot does not identify your device at all
Q: Why do you use 2 commands (fastboot flash and fastboot flash) instead of one?
A: I am not 100% sure but I think fastboot flash recovery, flashes the recovery image you have selected [permanently, until you flash a different one] in your device and you can boot into it anytime you want without using a PC
and the second boots your phone with the recovery image but does not flash it, meaning you keep the stock or the one you have flashed in the past.
So I use the first commmand to permanently flash the recovery and the second to boot the phone in recovery mode without using any phone button combinations to boot into, saves me the time and hassle.
Q: Why use Chinese Custom Recovery instead of an English one?
A: This recovery has Chinese and English Language support. However, if you go to the translated google forum link which I have posted below, the thread's title is: Z2 pro Brush] [zuk z2Pro] Twrp Recovery 3.10 update, support Andrews 7.0 7.1 7.1.2ROM
So I think, Recoveries need to also support the custom ROMS you want to flash, also it is taken from official lenovo forums and chances are they have added more features and fixes.
For example using 3.0.8 recovery I couldn't install LineageOS 14.1 custom rom, I was getting Error 7 when I was trying to flash
Q: I get Error 7 when I try to Flash a Custom ROM:
A: Flash 3.1 TWRP Recovery, the custom recovery you have flashed, does not support the custom ROM you want to flash.
Q: I no longer have open command prompt here after intalling Windows 10 Creators update, I have Open Powershell instead, help?
A: Read the following webpage:
http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/
It provides a registry fix which adds/restores "open command window here" in Windows 10 Context Menu
Q: Custom Recovery 3.1 is in Chinese, how do I change it to English?
A: See the following images
Tested on Windows 10 x64 Pro with Creators Update, should work for Windows 7/8 as well.
If this guide helped you, please buy me a beer, thanks!
http://paypal.me/mariosffx
MariosFFX said:
The recoveries I post are and tested for Lenovo Z2 Zuk Z2 Pro ONLY!
Requirements:
Unlocked phone bootloader
and your phone booted in fastboot mode, otherwise it will not work.
Recovery.img is the same recovery found on Lenovo forums (link below)
Download from MEGA
https://mega.nz/#!zJhFCKRa!7FDyDKkqEL3bgz-lYBMf_Lj0RoMyzubg9tiZC3z9ttg
Images are in thumbnails, click on them to enlarge
Short guide:
1) Simply extract the zip
2) Open cmd.exe and cd to the directory you extracted
3) Put your phone in fastboot mode by shutting down your phone, if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
4) Paste the following commands:
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
You should get the same results I got:
Long guide for newbies with Windows 10 [the same might be for Windows 7/8]:
1) Download the zip I have uploaded and extract it to a folder with your favorite archive manager [I use WinRAR] and open it
2) Hold Shift and Right Click on empty space in the folder
3) Left click on Open command window here or open command prompt here
4) Put your phone in fastboot mode by shutting down your phone, power it on and if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
5) Paste the following commands by copying one line each time
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
Contents of Uploaded RAR/Zip Archive:
adb.exe & fastboot.exe taken from adb-setup-1.4.3 zip/rar file, which was found on Google, don't have a source link
drivers where taken from ZUK_UsbDriver_1.0.6 zip/rar from a guide which was found on google, don't have a source link
recovery images where taken from the sources below
Sources & Thanks:
Recovery 3.0.8 was taken from:
https://forum.xda-developers.com/le...t/twrp-recovery-zuk-z2-standard-pro-t3415395/
credits go to @raimondomartire
Recovery 3.1 was found on official Lenovo Forums:
http://bbs.lenovomobile.cn/z2pro/t508552/
Google translated Lenovo Forum Page:
https://translate.google.com/transl...n&u=http://bbs.lenovomobile.cn/z2pro/t508552/
Q&A:
Q: I do the same steps you did, in command prompt after pasting your commands I get the following: "< waiting for device >
or I wait for long periods of time or I get a [ERROR] message
A: Chances are 100%, you have the wrong drivers or not drivers installed, most devices use their own drivers for fastboot mode or adb/fastboot commands
If you have a Lenovo Zuk Z2 Pro like me, your device needs to be identified as "ShenQi Composite ADB Interface" in device manager.
Not "Android" or "Android ADB Interface" and because of that fastboot does not identify your device at all
Q: Why do you use 2 commands (fastboot flash and fastboot flash) instead of one?
A: I am not 100% sure but I think fastboot flash recovery, flashes the recovery image you have selected [permanently, until you flash a different one] in your device and you can boot into it anytime you want without using a PC
and the second boots your phone with the recovery image but does not flash it, meaning you keep the stock or the one you have flashed in the past.
So I use the first commmand to permanently flash the recovery and the second to boot the phone in recovery mode without using any phone button combinations to boot into, saves me the time and hassle.
Q: Why use Chinese Custom Recovery instead of an English one?
A: This recovery has Chinese and English Language support. However, if you go to the translated google forum link which I have posted below, the thread's title is: Z2 pro Brush] [zuk z2Pro] Twrp Recovery 3.10 update, support Andrews 7.0 7.1 7.1.2ROM
So I think, Recoveries need to also support the custom ROMS you want to flash, also it is taken from official lenovo forums and chances are they have added more features and fixes.
For example using 3.0.8 recovery I couldn't install LineageOS 14.1 custom rom, I was getting Error 7 when I was trying to flash
Q: I get Error 7 when I try to Flash a Custom ROM:
A: Flash 3.1 TWRP Recovery, the custom recovery you have flashed, does not support the custom ROM you want to flash.
Q: I no longer have open command prompt here after intalling Windows 10 Creators update, I have Open Powershell instead, help?
A: Read the following webpage:
http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/
It provides a registry fix which adds/restores "open command window here" in Windows 10 Context Menu
Q: Custom Recovery 3.1 is in Chinese, how do I change it to English?
A: See the following images
Tested on Windows 10 x64 Pro with Creators Update, should work for Windows 7/8 as well.
If this guide helped you, please buy me a beer, thanks!
http://paypal.me/mariosffx
Click to expand...
Click to collapse
Thanks for this.
I'm waiting for delivery of a Z2 Pro and getting necessary stuff ready.
The Mega link wants a Decrypt key.
bluegrass55 said:
Thanks for this.
I'm waiting for delivery of a Z2 Pro and getting necessary stuff ready.
The Mega link wants a Decrypt key.
Click to expand...
Click to collapse
check again, the link is with decryption key.
I have double checked and made sure it was with the key.
I've tried again on Chrome,IE and Firefox but still get Decrypt message.
Do you copy and paste the link or you click on it?
Seems to me you copy and paste it.
Because the link is way too big, xda forums shorten it (notice the dots).
Click the link don't copy and paste iit
Finally managed to download it.
I clicked on the link in Chrome & it worked. Firefox didn't like it.
Thanks for the help.
fastboot claims to work, but doesn't
Code:
[email protected] ~/Downloads> fastboot -i 0x2b4c flash recovery twrp.img
target reported max download size of 1610612736 bytes
sending 'recovery' (18372 KB)...
OKAY [ 0.525s]
writing 'recovery'...
OKAY [ 0.145s]
finished. total time: 0.670s
[email protected] ~/Downloads> fastboot -i 0x2b4c reboot
rebooting...
finished. total time: 0.071s
Yet it goes back stock recovery. I've tried many variations of these commands, and always get the same results.
Philo.Phineas said:
Yet it goes back stock recovery. I've tried many variations of these commands, and always get the same results.
Click to expand...
Click to collapse
I am having problems with this Chinese twrp why not get fixed in the bootloader nor accept after even running without installing the program supersu via twrp
Hello All,
So originally I had TWRP 3.0 on my Z2 pro, and i attempted to just install the 3.1 img file from it(per another instructional video from the 7.1 mokee thread), and after installing the recovery file, my phone restarted, however now when I attempt to go into Recovery mode from the boot menu, my phone just goes to a blank screen.
I've tried to flash the image from CMD to see if i could essentially "re flash" 3.1 TWRP, but I always get this message(see attached image). What am i typing in wrong in CMD? As you can see, the directory name is right, as well as the fastboot code. I'm also IN fastboot mode on my phone already. I changed the file name of the folder containing the recovery from it's orginal name to make it shorter, but that should not matter at all. It seems as if CMD can't find the folder though?
Well XDA won't let me post a damn picture(how am i supposed to ask for help if i can't show people what im doing), so I guess if someone would PM me i can post the image.
People do you try to flash the recoveries right after unlocking your bootloader?
Because if you can't flash the recovery and it goes back to stock, it means you haven't fully unloxked your bootloader.
Make sure you run the last following command when you unlock your bootloader
Code:
fastboot -i 0x2b4c oem unlock-go
Then follow my guide here.
Also bootloader unlock tutorial here:
https://zukfans.eu/community/threads/zuk-z2--unlock.62/
Its for Zuk Z2, but the instructions are also for Z2 Pro.
MariosFFX said:
rl].
Click to expand...
Click to collapse
Any idea about what's happening with the situation in my post by chance? When I try to flash from CMD i get this text. "Z2 is not recognized as an internal or external command, operable program or batch file"
"Z2" is the name of the folder that contains the recovery image, so it seems like it's not finding it.
which files about phone mobile data at a TWRP BACKUP ? i see a lot of files inside of a twrp backup . i need to learn that . thanks.
jsto69 said:
Any idea about what's happening with the situation in my post by chance? When I try to flash from CMD i get this text. "Z2 is not recognized as an internal or external command, operable program or batch file"
"Z2" is the name of the folder that contains the recovery image, so it seems like it's not finding it.
Click to expand...
Click to collapse
Use directory names without spaces. Like c:\zuk and perform all operations from there.
Hello, this works fine very thx, but you have recent/new mix version?
This is a step-by-step guide that will get you to a fully working lineageos on your sony xa2 ultra, starting from a device that was just purchased.
I used Linux, but everything should be more than doable on Windows as well.
Make sure you have:
A copy of platform-tools from google (ubuntu's version works to some extent, i had to use binaries from both). You need:
fastboot
adb
The TWRP image for XA2 ultra: twrp-3.2.3-0-discovery.img
A working copy of xperifirm. If you're on Linux set a light UI theme, or it won't work. Also
Code:
export TERM=xterm
before launching it.
A working copy of newflasher. You can build it on linux by typing
Code:
make newflasher.x64
newflasher.x64 will be the name of the binary.
A fresh lineageos build for your phone (from now on referred to as lineage.zip)
A build of gapps, if you want them
The first thing you have to do is to
Unlock your bootloader
Preliminary operations:
Start your phone
Connect to the internet (3g or wifi)
Go to Settings > System > Device info, tap "Build number" until developer mode is active
Go back, open developer options
Tick USB Debugging and OEM Unlock
Open the phone dialer and type
Code:
*#*#7378423#*#*
this will open the service menu. It could take a few seconds.
Go to Service info
Enter 'Model info', write down the string (e.g. H4213) somewhere
Go back and enter 'Configuration'.
Check that "Bootloader unlockable" is 'yes', if it's not you can't proceed.
Write down the IMEI code. If it's a dual sim, you need to write down the "Sub1" one.
Go here, select the device and paste the IMEI that you wrote down
Write down the unlock code
Put phone in fastboot mode and unlock the bootloader:
Shut down the phone completely, unplug the USB cable if plugged
Hold VolumeUp, plug USB cable
Phone should power on, press Power if it doesn't
Wait until you have a fixed blue light on the led
You are now in fastboot mode
Code:
fastboot oem unlock xxxxx
where xxxxx is the unlock code that you obtained from the previous step
Flash an updated firmware
First you need to obtain the latest firmware for your device:
Run xperifirm
Open Sony XA2 discovery
Select whatever you wrote down from the 'Model info' section of the service menu
Download whatever firmware has the highest build number
If you're on Linux xperifirm will fail to unpack the firmware. You can work around it by entering the firmware directory on a shell and running:
Code:
for i in FILE_* ; do unzip $i ; done
unzip boot.zip -d boot
Remove a bunch of files, you can copy/paste this string after 'rm' or delete them manually:
Code:
kernel_X-FLASH-ALL-18AE_0x00.hash kernel_X-FLASH-ALL-18AE.sin persist_X-FLASH-ALL-18AE_0x00.hash persist_X-FLASH-ALL-18AE.sin system_other_X-FLASH-ALL-18AE_0x00.hash system_other_X-FLASH-ALL-18AE.sin system_other_X-FLASH-ALL-9B8D_0x00.hash system_X-FLASH-ALL-18AE_0x00.hash system_X-FLASH-ALL-18AE.sin system_X-FLASH-ALL-9B8D_0x00.hash userdata_X-FLASH-CUST-18AE.sin vendor_X-FLASH-ALL-18AE_0x00.hash vendor_X-FLASH-ALL-18AE.sin vendor_X-FLASH-ALL-9B8D_0x00.hash
Put your phone in flashing mode.
Shut down the phone completely, unplug the USB cable if plugged
Hold VolumeDown, plug USB cable
Phone should power on, press Power if it doesn't
Wait until you have a fixed green light on the led
You are now in flashing mode
Run
Code:
newflasher
(or newflasher.x64 if you built it yourself) from the directory where you have the remaining firmware files. It could ask you whether to dump the TA section, feel free to answer 'n'.
Go back in fastboot mode, and run:
Code:
fastboot set_active other
Then rerun the last list (go to flashing mode, run newflasher).
If 'other' doesn't work, run "fastboot getvar current-slot" in fastboot mode and then use either 'a' or 'b' instead of 'other' - whatever is not the one returned by getvar.
Flash lineage
Boot into TWRP:
Put your phone in fastboot mode (see above)
Code:
fastboot boot twrp-3.2.3-0-discovery.img
You are now in TWRP
When I first tried this my phone kept power cycling. If this happens to you too, here is how to fix it:
Hold VolUp and let it power cycle until it goes into fastboot mode again (fixed blue led)
Code:
fastboot -w
Try booting into TWRP again
Flash lineage:
On TWRP go to advanced, enable sideload
On your computer run:
Code:
adb sideload lineage.zip
It should start flashing by itself, if it doesn't, make it.
If you want to also flash gapps, repeat steps from 'Boot into TWRP' and flash the gapps zip file.
Reboot your phone into fastboot one last time, and run
Code:
fastboot -w
.
Reboot with
Code:
fastboot reboot
.
Congratulations, you're now running lineage!
Thanks @xstasi for the write up. However, I have a question.
After flashing the firmware with newflasher the first time, I then went to download mode, found I was on "b" so I set it to the "a" slot. But after powering down, now my phone will not do anything. I can't get back into the flash mode, or fastboot mode. No matter what I press, when I plug in the USB cord, the light blinks green several times but never goes solid. Any advice on how to fix this?
So im lost here on how to start this process on win10. Play by play, where did you enter codes.
N00b question:
The automatically generated lineageos installation instructions recommend backing up the "trim area partition" as it contains "the" DRM keys:
https://wiki.lineageos.org/devices/discovery/install#unlocking-the-bootloader
There seems to be a tool on XDA for this: https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Why do I need to bother with that? What would I need the DRM keys for? Does it make a difference when running lineage? Or reverting back to stock?
BR
voidling42 said:
N00b question:
The automatically generated lineageos installation instructions recommend backing up the "trim area partition" as it contains "the" DRM keys:
https://wiki.lineageos.org/devices/discovery/install#unlocking-the-bootloader
There seems to be a tool on XDA for this: https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Why do I need to bother with that? What would I need the DRM keys for? Does it make a difference when running lineage? Or reverting back to stock?
BR
Click to expand...
Click to collapse
You backup the TA Partition once you've booted into TWRP. Theres a section where you can backup the TA Partition through there... Unfortunately it isn't mentioned here.
---------- Post added at 04:22 AM ---------- Previous post was at 04:20 AM ----------
Hmmm, I would have recommended the 'Minimal Adb and Fastboot' instead of the 'platform-tools' from Google. Less bloaty, quicker installation and same instructions as above. All thats needed is the twrp.img in the same folder where the 'Minimal Adb and Fastboot' is installed and voila!
You never mentioned the Add On SU, to add rooting capability into Lineage itself rather than third party apps, activated from the developer options once flashed.
I know GApps are a rather personal preference from person to person. But I'd personally recommend installing the Aroma package from Open GApps. Whilst it is essentially the Super package (Where it has all the Google Apps), Aroma unlike Super has a GUI where you can select what Google Apps you do and don't want installed from it. So you can add as much or as little as you need to. further on, It also has extra really useful features; before installing you can tell if you want Aroma to replace the Lineage apps with the Google versions (Such as Gallery, Camera, Contacts and Messaging... etc), because normally it will just overwrite them anyway. Finally, the most useful feature before installing GApps, is that you get the option to uninstall Lineage features. There's only 3 options (LineageOS Recorder, LineageOS Setup Wizard and LineageOS Updater), the rest dont really apply to Lineage. At the very least I'd recommend uninstalling the LineageOS Setup Wizard (But I usually uninstall all 3). I say that because Aroma also installs a Google setup wizard, thats much more useful than the Lineage one, particularly if you're updating Lineage and have previously made a backup with Google and want to quickly reinstall all your apps and settings, rather than reinstalling them one by one.
Hello guys,
I found some differences with other Newflash guides:
- you do not delete *.ta files in main folder and in boot folder;
- you delete kernel_* files instead of boot_* files in main folder;
I can't tell if those different steps make any difference, anyway.
You should mention that DRM keys are lost with bootloader unlock and that TA partition should be backup up via TWRP before flashing lineage.
I'm very excited about the hardware on this phone. While I might be late to this game, can anyone tell me if Volte is working properly in US? Losing 3G is a few months is forcing me to find a new phone.
Very nice to see Y700 get it's own place on XDA! I myself had just bought the 12GB version and have been very satisfied. The tutorials and info related to this model had been very difficult to come by and mostly in other languages, so I had to do my own research and exploration. So far I was able to flash ROM and extract it's boot image for root thanks to the following tutorial (in Japanese)
boot.imgを入手できない機種でMagiskを導入する方法【DSU Loader】
Android端末のカスタマイズやRoot権限の使用が可能となる「Magisk」ですが、一部例外を除き、導入に…
smartasw.com
The boot image extraction part is trickier as Y700's roms come in GSI form. But with a workaround we can still achieve the same goal. (I heard that you can also use QFIL to do that but I haven't been able to make the tool work, so if someone else can make a tutorial that'd be great)
First you need to prepare:
- DSI-Sideloader from https://github.com/VegaBobo/DSU-Sideloader/releases
- Magisk Manager from topjohnwu's GitHub repo
- a GSI ROM with built in root permission. The one the tutorial was using: https://github.com/phhusson/treble_experimentations/releases/tag/v402 --> go download "system-squeak-arm64-ab-vanilla.img.xz" (~600MB, smallest needed to fulfill the task)
- turn on developer mode and ADB debugging. Get Google SDK platform tools ready and USB drivers installed.
Connect your Y700 to a computer. Check if ADB works.
Next, install the DSI-Sideloader app. Also extract the .xz package you downloaded above to get the .img image (should be ~1.7GB in size)
Copy the image to your Y700 tablet. Open the DSI-Sideloader app, load the image, set userdata size to default (2GB). You can leave image size unchanged.
NOTE: if you have an SD card inserted, click on "config" and check "Unmount SD", or just eject your SD card from tray. Failing to do so will result in error in the install step.
After you're done, click "Install". Once finished there will be a pop-up with commands you need to enter in the terminal of your choosing. On your computer navigate to the directory containing executables of Google SDK platform tools, fire up terminal, enter the 1st command (says non-root) as instructed, and run it.
You will see a progress bar in the drop-down notification area which will complete in a moment and prompt you to reboot. Do that from there.
After reboot you will be running the modded Project Treble ROM, with root access. It's a full fledge OS but once you shutdown / reboot you will go back to your own OS. Treat it as a LiveCD of some sort.
While still connected, turn on dev mode + ADB debugging and go back to terminal for some ADB work. Next we will be extracting boot image under the current environment, made possible by it's built-in root permission.
Run the following line by line:
Bash:
adb shell
Bash:
su
Bash:
cd /dev/block/bootdevice/by-name/
Bash:
mkdir /sdcard/backup_img
Bash:
for file in *; do
if [[ "${file}" = boot* ]]; then dd if=/dev/block/bootdevice/by-name/"${file}" of=/sdcard/backup_img/"${file}".img ; else continue ; fi
done
The 4th command creates a new directory storing extracted boot image, in our case /SD card/backup_img; and the 5th command is the meat of the entire process. It consists of 3 lines, key in one at a time and press "Enter". First line is "for...do", second is "if [[..." to "fi", third is just "done".
After some time the extracted boot image will be stored under the directory specified by the 4th command, in our case /sdcard/backup_img . They are stored in the temporary user space and once you reboot to your original OS you won't be able to access them again. So you need to turn on File Transfer mode, go to the actual directory on your PC and move them to your computer. They have the filenames "boot_a.img" and "boot_b.img" . After you're done, just reboot as usual and you'll get into your old OS.
Now you have the boot images, all that's left is to use Magisk Manager to patch them, enter fastboot mode, and flash the patched images using the following commands:
fastboot flash boot_a patched_img_A.img
fastboot flash boot_b patched_img_B.img
(Rename as needed)
And now your Y700 is rooted.
The linked Japanese webpage also talks about working Android 12 / 13 GSI flavors, patches, and ways to set up your Y700.