Develop Bugs

[RECOVERY][Unofficial][tetra] TWRP 2.8.3.0 for Sony Smartwatch 3

Unofficial TWRP 2.8.3.0 for Sony Smartwatch 3 (SWR50) (tetra)
If you don't know, what TWRP is then read http://teamw.in/project/twrp2 before flashing anything.
If you know, what TWRP is then read the disclaimer: use at your own risk, neither XDA, TeamWin nor I are responsible for anything bad and going wrong.
Installation Instruction
First of all you need adb and fastboot drivers and binaries installed on your PC. Grab them from the Android SDK, that suites to your PC's OS. Windows user may need the generic usb drivers. Linux users may need to start adb and fastboot with root rights, if they don't have the needed udev rules.
Unlock bootloader
If your bootloader isn't unlocked yet, then you have to unlock it. There are to ways to boot into the fastboot mode.
]1. way to boot into fastboot mode:
Turn off your device
Press and hold power button until the "Insert USB" animation appears
double press the power button to enter the boot menu. (you may need several attempts)
within the bootmenu press power once to navigate, twice to select. Press twice to boot into fastboot
now you can connect your watch with your PC.
2. way to boot into fastboot mode:
enable developer settings and ADB debugging from within the settings menu (you have to press 7 times the About->build number)
connect your watch with your PC. Enter "adb devices" in your terminal/cmd and confirm adb permission for your watch on your smartphone.
boot into bootloader with "adb reboot bootloader"
Now, in fastboot mode enter "fastboot oem unlock" twice to unlock the bootloader. Attention: this will factory reset your Smartwatch 3.
Some users reported, that their devises stuck on boot without the commands "fastboot format cache" and "fastboot format userdata", you should enter this commands before you the reboot, too.
Afterwards reboot your device and set it up again. Enable adb debugging, too.
Flashing TWRP
Boot into fastboot mode
enter "fastboot flash recovery <NAMEOFTHE.IMG>"
Power off the device
(to power off try "fastboot continue", it should boot into charging mode and then unplug the device)
Now, TWRP is installed and you should boot straight into it with holding power button and selecting "Recovery" from the boot menu (see first way to boot into fastboot mode)
If you boot into system without booting twrp once, the system overwrittes twrp with the stock recovery. If this happens to you, then boot into fastboot and boot twrp without flashing it with "fastboot boot <NAMEOFTHE.IMG>". Afterwards boot into bootloader from the recovery's reboot menu and flash twrp again.
Download link: unofficial-twrp-2.8.3.0-tetra.img Updated on 30.12.2014
Now, if you want to root your Smartwatch 3 with Wear 5.0.1, go to http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv, download the "Wear supersu.zip" and flash it with your newly installed TWRP recovery.
If you want to use "adb sideload" make sure that you have the most recent adb binary on your pc.
Kernel source code: can be downloaded from https://android.googlesource.com/ke...-wear-release/arch/arm/mach-java/sony/brooks/
TWRP device tree: https://github.com/perpe/android_device_sony_tetra
Many thanks to @Dees_Troy for making twrp avaible

Good job, I'll post stock recovery extracted from PC companion image later tonight.

I have a copy of the stock recovery, created with dd from the device. I can upload it, if it is needed

Can someone please upload a twrp image of the stock rom? I want to get rid of my pre release debug version
Sent from my SM-N910G using XDA Premium 4 mobile app

Works great, both using boot or flash recovery and both from boot menu and adb reboot recovery from system.
BTW, thanks for boot menu hint.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
The only issue it is extremely hard to press on home button and I was not able to press on back button

@julz
Please, can you make a backup of your prerelese version with twrp? I will upload a stock 5.0.1 version with all neccessary parts later today.
@XorZone
Nice to read. I was unsure with the overwrite, if people don't boot the twrp once, because there isn't a install-recovery.sh, but it seem that this happens.

perpe said:
@julz
Please, can you make a backup of your prerelese version with twrp? I will upload a stock 5.0.1 version with all neccessary parts later today.
@XorZone
Nice to read. I was unsure with the overwrite, if people don't boot the twrp once, because there isn't a install-recovery.sh, but it seem that this happens.
Click to expand...
Click to collapse
Yep will do! Thanks!
---------- Post added at 09:12 PM ---------- Previous post was at 08:29 PM ----------
Hey @perpe you might want to add the following to your bootloader unlock instructions as I had to go to the old rooting thread to find this out:
4. fastboot format cache
5. fastboot format userdata
6. fastboot getvar all (and verify that it is)
7. fastboot reboot

Hi all - link to the pre-release version recovery image (tetra-userdebug 4.4W KGW38C 1046 test-keys):
http://1drv.ms/1y100TI

That's incredible. as explained here but even that does not work. yet all the usb driver days with the sdk. Can not even watch fastboot mode, while in adb way possible.
I do not understand why it does not work.
the model of the watch is LWX48P

--- nvm, fixed it.---

julz said:
you might want to add the following to your bootloader unlock instructions as I had to go to the old rooting thread to find this out:
4. fastboot format cache
5. fastboot format userdata
6. fastboot getvar all (and verify that it is)
7. fastboot reboot
Click to expand...
Click to collapse
This is not needed. Look at http://source.android.com/source/building-devices.html#unlocking-the-bootloader format cache & userdata is only needed on Nexus 10. Our device formats cache and userdata automatically on bootloader unlock. getvar is useless with out telling the people what they have to verify
Many thanks for your dump, but it contains the data partition, too. Please, delete that from your zip package, because data contains your personal setup. It's not a good idea making it public.
I made a flashable zip of the stock LWX48P and will open a thread for it. I had a deeper look into the partitions and I really don't know if it's a good idea to flash the stock ROM on to your test build device. This can brick it.
My zip file contains all necessary partitons from the update KNX01V -> LWX48P, but there are some other partitions that may be necessary for you. These partitions are not included within my zip. There are 10 partition, which are part of the board firmware (recovery.fstab calls them "Needed for radio.img").
The more relevant partition for you should be the s1sbl partition, this is the Sony bootloader. I can't say, if the stock rom works with your device or if it bricks it. Have you tried flashing the stock ROM with the Sony PC Companion? You should try this first. If it doesn't work, I would recommend a binary comparison of the s1sbl partition of your device and an official release version. For this I need a copy of yours, you can make it with dd. If they are the same it should be relative safe to flash the stock ROM, if not then it gets tricky, you may want to flash the stock s1 bootloader before flashing the ROM. I really don't know, what could be the best in this case.
ced360 said:
That's incredible. as explained here but even that does not work. yet all the usb driver days with the sdk. Can not even watch fastboot mode, while in adb way possible.
I do not understand why it does not work.
the model of the watch is LWX48P
Click to expand...
Click to collapse
The problem is with your PC. Make sure there are no background Android Sync applications, like Samsung Kies, HTC Sync Manager..., are running. These applications block adb. Look into the windows device manager, too. If the Sony Smartwatch 3 has a triangle, then it is not recognized with a driver. This can happen if you have several adb drivers installed. Remove them or associate one of them manually from the device managers driver installation. I can't help you here, I'm a Linux user, not Windows.
@all
There was a little error in the recovery, I've fixed it and also removed the SuperSu install question, because it doesn't work right with wear. The recovery is updated and the old one removed, please use this one in the future.

@perpe - I had to format cache and userdata for my SmartWatch 3 to boot again - got stuck in a bootloop after unlocking.
Are you able to point me to somewhere that explains how to use DD? Do I run it via ADB Shell?
Thanks!
---------- Post added at 01:51 PM ---------- Previous post was at 01:46 PM ----------
Unfortunately the Sony PC Companion doesn't update my watch Says to update my PC Companion but then says it's up to date

Yepp, my watch needed format cache or I didn't know it that time so just reflashed with PC companion tricking it to update connected Sony smartphone (and I'm glad they are checking version from s1 and not by user selection) as PC companion was telling no new update and not giving an option to repair back then.

perpe said:
I made a flashable zip of the stock LWX48P and will open a thread for it. I had a deeper look into the partitions and I really don't know if it's a good idea to flash the stock ROM on to your test build device. This can brick it.
My zip file contains all necessary partitons from the update KNX01V -> LWX48P, but there are some other partitions that may be necessary for you. These partitions are not included within my zip. There are 10 partition, which are part of the board firmware (recovery.fstab calls them "Needed for radio.img").
The more relevant partition for you should be the s1sbl partition, this is the Sony bootloader. I can't say, if the stock rom works with your device or if it bricks it. Have you tried flashing the stock ROM with the Sony PC Companion? You should try this first. If it doesn't work, I would recommend a binary comparison of the s1sbl partition of your device and an official release version. For this I need a copy of yours, you can make it with dd. If they are the same it should be relative safe to flash the stock ROM, if not then it gets tricky, you may want to flash the stock s1 bootloader before flashing the ROM. I really don't know, what could be the best in this case.
Click to expand...
Click to collapse
Full list of files in PC Companion fileset:
Code:
abi-sec.sin
abi.sin
boot.sin
cache.sin
cp-boot.sin
cp-image.sin
dsp-dram.sin
dsp-pram.sin
dt-blob.sin
hwconf.sin
kernel-dtb.sin
loader.sin
parm-spml-dep.sin
parm-spml-ind.sin
partition-image.sin
ramdump-dtb.sin
ramdump.sin
recovery.sin
s1sbl.sin
sys-parm-dep.sin
sys-parm-ind.sin
system.sin
u-boot.sin
ubootlogo.sin
umts-cal.sin
userdata.sin
version-info.sin

@XorZone
Did you unlocked your bootloader with with current firmware or the previous one? I did it with the current one and it wasn't needed. If I lock my device and unlock it again it is also not needed. Unlock resets it everytime, but no stuck on boot. Anyway I added it.
@julz
Code:
adb shell
su
dd if=/dev/block/platform/sdhci.1/by-name/s1sbl of=/sdcard/s1sbl.img
this makes a dump of your s1 bootloader on sdcard. You need root for it. If your system is still unrooted, you can use the recovery's adb, too. In the recovery you may need to change the sdcard path.(the "of" part)
It would be good if you can make a dump of your ta partition, too. but don't give it away, because the ta partitions contains your serial number. (change s1sbl to ta in the command above).
Copy both dumps to your pc. Try to open the ta dump with a hexeditor and search for your serial number, afterward it list the model number (SWR50 on my device), then the bootloader version (1286-0320 S1BOOT_BCM23550_Release_REL105) and a timestamp of my last flash with the PC companion. Please compare them with yours.
I have found the u-boot source code on the Sony site. On boot the device first boots u-boot and u-boot handles the boot process. The s1 bootloader is only booted by user request (connecting it via usb when the USB animation appears). For me this means, s1 is only needed for recognition/updating with pc companion and it should be possible to flash it without bricking and without s1sbl. But I don't call myself a developer and this is my first Sony device. You may want to start a thread in the Sony Cross-Device General board. There are more experienced devs than me. I'm sure they know, if your devices could be flashed with pc companion if you swap the s1sbl with a regular one. There are also several unofficial tools to create and flash Sony firmware, but as I said, I'm very new to Sony and don't know how to handle them yet (and even don't know if they support a Broadcom SoC)
If you make a dump of the s1sbl, then send me a link for a compare.
Download link of the u-boot source: http://developer.sonymobile.com/dow...e-for-smartwatch-3-lwx48p-android-wear-5-0-1/ (look into /u-boot/hawaii/board/broadcom/javaboard/s1/cmd_s1boot.c for the boot selection)

perpe said:
@XorZone
Did you unlocked your bootloader with with current firmware or the previous one? I did it with the current one and it wasn't needed. If I lock my device and unlock it again it is also not needed. Unlock resets it everytime, but no stuck on boot. Anyway I added it.
Click to expand...
Click to collapse
On 4.4, they might fixed it in 5.0.
Back then this forum was blank and I had no idea how sony devices works, so spoiled by nexus experience the first thing after enabling adb I went and unlocked oem and had some skipped heartbeats when I got stuck on bootlogo.
perpe said:
There are also several unofficial tools to create and flash Sony firmware, but as I said, I'm very new to Sony and don't know how to handle them yet (and even don't know if they support a Broadcom SoC)
Click to expand...
Click to collapse
I'm using flashtool from http://www.flashtool.net/index.php to decrypt sony fileset and extract sin files, this tool should work with any s1 protocol devices, but there is no configuration for the SWR50 so I was not able to flash with it.
After flashing from test to 5.0 in twrp it might hang with power button unresponsive so the only way out would be to wait for discharge to get into s1 and then with PC Companion not updating...
BTW, @julz does PC Companion able to repair your test version, e.g. saying that there is no new update, but still asks to repair or just saying no new update bye-bye?

@XorZone
I used it also to get the stock recovery as a base for my TWRP. But I don't want to flash my device with it. I had some problems with it, dumped boot/recovery images (with sin editor) stucked on boot. I had to repack them to boot right. I wasn't able to dump cp-image. It ate all my free space and aborted. Another problem is my Linux doesn't recognize the swr50 right in s1 mode. My USB port goes wild. That's why I stand back from any flash test with it. If I don't trust a tool (or don't know how to use it right) I can't advise others to try anything with it without consulting the experts.
Configuration file should be something like this
Code:
#Fri Aug 08 18:46:20 CEST 2014
internalname=SWR50
canfastboot=true
busyboxhelper=1.20.2
recognition=SWR50,tetra
variant=SWR50,tetra
cankernel=false
busyboxinstallpath=/system/xbin
realname=Sony Smartwatch 3
loader=1f5089f1c617e5aa3e7bae0a8c2f8ae2
canrecovery=true
buildprop=ro.product.device
canflash=true
I'm unsure with the cankernel. loader.sin should be the same loader.sin that you get after the decrypt? I've created the loader md5 for it. tetra in "recognition" is needed for julz' device

perpe said:
@XorZone
I used it also to get the stock recovery as a base for my TWRP. But I don't want to flash my device with it. I had some problems with it, dumped boot/recovery images (with sin editor) stucked on boot. I had to repack them to boot right. I wasn't able to dump cp-image. It ate all my free space and aborted. Another problem is my Linux doesn't recognize the swr50 right in s1 mode. My USB port goes wild. That's why I stand back from any flash test with it. If I don't trust a tool (or don't know how to use it right) I can't advise others to try anything with it without consulting the experts.
Configuration file should be something like this
Code:
#Fri Aug 08 18:46:20 CEST 2014
internalname=SWR50
canfastboot=true
busyboxhelper=1.20.2
recognition=SWR50,tetra
variant=SWR50,tetra
cankernel=false
busyboxinstallpath=/system/xbin
realname=Sony Smartwatch 3
loader=1f5089f1c617e5aa3e7bae0a8c2f8ae2
canrecovery=true
buildprop=ro.product.device
canflash=true
I'm unsure with the cankernel. loader.sin should be the same loader.sin that you get after the decrypt? I've created the loader md5 for it. tetra in "recognition" is needed for julz' device
Click to expand...
Click to collapse
Strange, I was able to boot straight from extracted boot/recovery images. With cp-image use dump raw instead.
I have almost the same config file, but was not able to flash system sin when I screwed mine while testing first rooting boot.img.
And if PC Companion do not repair his test version, I would not proceed at least until other partitions compared to release version.
@julz, please dump version info as well:
Code:
dd if=/dev/block/platform/sdhci.1/by-name/version-info of=/sdcard/version-info.img

Oh yes, version-info is very important, u-boot checks it on boot.
I tried the raw dump, but it adds a strange header to most of my dumps.

@perpe - Thanks for the DD instructions.
I've dumped my S1SBL, TA and VERSION-INFO partitions now.
I've also had a look in my TA image and this is what is after my serial number (excluding the random ASCII):
Mine is 1286-0320 S1BOOT_BCM23550_Release_29
(yours is 1286-0320 S1BOOT_BCM23550_Release_REL105)
KGW83C (my build number)
My model simply refers to 'tetra' and not SWR50.
I had no PC companion timestamps as I can't flash with PC companion.
@XorZone - I can't select an option in PC Companion to reset/reflash my watch. Simply says no update is available.
My S1SBL and VERSION-INFO partitions are uploaded here:
http://1drv.ms/1xwGMSW
Thanks!

[HELP]How to reflash to stock rom?

Sorry if this has been answered before, but I've tried the methods of flashing droidboot, boot from the stockrom before flashing, and also altering the updater-script before flashing, but nothing works
how do i reflash to stock rom? I'm om CM 13 at the moment

download stock rom on asus website (check your version)
copy stock rom to adb folder.
reboot to recovery. if you use twrp. go advanced. adb sideload
connect with pc
open cmd in adb folder.
use command "adb sideload romname.zip"
good luck

rachnov55 said:
Sorry if this has been answered before, but I've tried the methods of flashing droidboot, boot from the stockrom before flashing, and also altering the updater-script before flashing, but nothing works
how do i reflash to stock rom? I'm om CM 13 at the moment
Click to expand...
Click to collapse
follow these steps in this link --> http://www.android.gs/how-to-unbrick-asus-zenfone-2-and-go-back-to-stock-android-os/
--> http://www.asus-zenfone.com/2015/12/how-to-downgrade-asus-zenfone-2-firmware.html
both are same will bring you to stock rom, i have tried both tutorial mentioned in those link with 100 % successful

after i flash the recovery, boot and droidboot, I boot to recovery and get an Error! message

Echoe Zen Rom v3 [2.20.40.165] flashing failed
Sir, I tried to flash Echoe Zen Rom v3 [2.20.40.165] but it is failed with this ERROR "update process ended with ERROR: 7 error instaing zip file '/external_sd/New Folder /echoozen_Rom_3_2.20.40.165_220116.Zip'
i also attached the photograph of eroor message. my phone is rooted and bootloader unlocked . I want to go back to stack rom please help me......sorry for my bad english

utphala said:
Sir, I tried to flash Echoe Zen Rom v3 [2.20.40.165] but it is failed with this ERROR "update process ended with ERROR: 7 error instaing zip file '/external_sd/New Folder /echoozen_Rom_3_2.20.40.165_220116.Zip'
i also attached the photograph of eroor message. my phone is rooted and bootloader unlocked . I want to go back to stack rom please help me......sorry for my bad english
Click to expand...
Click to collapse
follow steps in this link http://www.android.gs/how-to-unbrick-asus-zenfone-2-and-go-back-to-stock-android-os/
or this link (file that you might need you can download in this link)
http://www.asus-zenfone.com/2015/12/how-to-downgrade-asus-zenfone-2-firmware.html

rachnov55 said:
after i flash the recovery, boot and droidboot, I boot to recovery and get an Error! message
Click to expand...
Click to collapse
you forgot to flash system.img," fastboot flash system system.img", after that execute the following commands: “fastboot format userdata” and “fastboot format cache”

I found that if you are on CM and using TWRP, you can flash stock by simply wiping caches and data (not system), installing Prism Barebone, and then installing the stock firmware zip over that. A little time-consuming having to do the two installs, but very simple and you don't need to piss about changing to stock recovery (so you can do it all on-device, no need for hooking up to a PC).

VinzNguyen said:
download stock rom on asus website (check your version)
copy stock rom to adb folder.
reboot to recovery. if you use twrp. go advanced. adb sideload
connect with pc
open cmd in adb folder.
use command "adb sideload romname.zip"
good luck
Click to expand...
Click to collapse
Are you sure that we can use twrp to sideload the firmware?Have you tried it?

chtsarts said:
Are you sure that we can use twrp to sideload the firmware?Have you tried it?
Click to expand...
Click to collapse
i did it. i sure
---------- Post added at 11:17 AM ---------- Previous post was at 11:17 AM ----------
utphala said:
Sir, I tried to flash Echoe Zen Rom v3 [2.20.40.165] but it is failed with this ERROR "update process ended with ERROR: 7 error instaing zip file '/external_sd/New Folder /echoozen_Rom_3_2.20.40.165_220116.Zip'
i also attached the photograph of eroor message. my phone is rooted and bootloader unlocked . I want to go back to stack rom please help me......sorry for my bad english
Click to expand...
Click to collapse
dont wipe system

---------- Post added at 12:46 PM ---------- Previous post was at 12:43 PM ----------
[/COLOR]
VinzNguyen said:
download stock rom on asus website (check your version)
copy stock rom to adb folder.
reboot to recovery. if you use twrp. go advanced. adb sideload
connect with pc
open cmd in adb folder.
use command "adb sideload romname.zip"
good luck
Click to expand...
Click to collapse
can i copy the firmware to external sd and update from sd?

chtsarts said:
---------- Post added at 12:46 PM ---------- Previous post was at 12:43 PM ----------
[/COLOR]
can i copy the firmware to external sd and update from sd?
Click to expand...
Click to collapse
http://forum.xda-developers.com/zenfone2/general/how-to-flash-ota-rom-twrp-t3209545
follow this thread

bar4 said:
you forgot to flash system.img," fastboot flash system system.img", after that execute the following commands: “fastboot format userdata” and “fastboot format cache”
Click to expand...
Click to collapse
Where does one get the system.img file? None of the links posted above have this file.

Fiasco said:
Where does one get the system.img file? None of the links posted above have this file.
Click to expand...
Click to collapse
https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
http://www.mediafire.com/download/1nwpoqo8rpi1kur/Z00A_2.13.40.13_preroot_system.zip
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
http://www.asus-zenfone.com/2015/04/asus-zenfone-2-pre-root-systemimg.html

[GUIDE] Unlock bootloader and flash TWRP recovery

PREREQUISITES:
- Nubia Z17 device.
- USB type C cable.
- Computer with Windows and adb-fastboot drivers installed and configured (there are a lot of guides on the Internet).
- Nubia Z17 Pack -> You have the mirrors at the end of the post
STEPS:
1.- Download the pack with all the necessary stuff.
2.- Decompress the folder that is inside the rar.
3.- Open that folder, press SHIFT and at the same time do right click. Click on open a powershell... or open a command prompt...
NOTE: if appears the first option you have to send the command: cmd
4.- Put the phone on fastboot mode (power and vol+ at same time) and connect the phone to the computer.
5.- Send the command fastboot devices and it should give you something like this if the drivers are OK:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6.- Send this command to unlock bootloader: fastboot oem nubia_unlock NUBIA_NX563J
Now you have your bootloader unlocked!
7.- Send this command to flash TWRP: fastboot flash recovery TWRP_recovery.img
Now you have the TWRP recovery flashed!
8.- To reboot into recovery you have to choose with volume buttons the option to reboot recovery and press power.
There is a little problem, the recovery is in Chinese and I don't know you, but I don't understand Chinese :silly: So let's change the language.
9.- When it displays the first screen, something like this pic, you have to press the second button and choose your favourite language (I always recommend English)
10.- Now you have to root the phone, go to Advanced > Tools and press Root device.
Now you have your phone's bootloader unlocked, the TWRP recovery flashed and root access!
DOWNLOADS:
- Nubia Z17 Pack (MEGA)
Alternative mirror (DRIVE)
CREDITS:
- @shimp208 for the Minimal ADB and Fastboot portable included in the pack.
- users of Nubia forum that made the TWRP 3.1.1
- One photo from MIUI

Awesome thanks, now I've got a TWRP I can actually understand

dorkozoid said:
Awesome thanks, now I've got a TWRP I can actually understand
Click to expand...
Click to collapse
I am glad to hear that

As we have twrp now..can someone try flashing gapps using it

Gapps is working for me.
I flash Open GApps (ARM64 + 7.1 + full)

ndv92 said:
Gapps is working for me.
I flash Open GApps (ARM64 + 7.1 + full)
Click to expand...
Click to collapse
so ı dıd same and all worked goıod first then later ıts not working . do u have same problem ?
---------- Post added at 07:34 AM ---------- Previous post was at 07:33 AM ----------
thanks for guide . Many should be happy now. but we need one guide how to make gapps works aswell.

arceoxis said:
PREREQUISITES:
- Nubia Z17 device.
- USB type C cable.
- Computer with Windows and adb-fastboot drivers installed and configured (there are a lot of guides on the Internet).
- Nubia Z17 Pack -> You have the mirrors at the end of the post
STEPS:
1.- Download the pack with all the necessary stuff.
2.- Decompress the folder that is inside the rar.
3.- Open that folder, press SHIFT and at the same time do right click. Click on open a powershell... or open a command prompt...
NOTE: if appears the first option you have to send the command: cmd
4.- Put the phone on fastboot mode (power and vol+ at same time) and connect the phone to the computer.
5.- Send the command fastboot devices and it should give you something like this if the drivers are OK:

6.- Send this command to unlock bootloader: fastboot oem nubia_unlock NUBIA_NX563J
Now you have your bootloader unlocked!
7.- Send this command to flash TWRP: fastboot flash recovery TWRP_recovery.img
Now you have the TWRP recovery flashed!
8.- To reboot into recovery you have to choose with volume buttons the option to reboot recovery and press power.
There is a little problem, the recovery is in Chinese and I don't know you, but I don't understand Chinese :silly: So let's change the language.
9.- When it displays the first screen, something like this pic, you have to press the second button and choose your favourite language (I always recommend English)
6.- Send this command to unlock bootloader: fastboot oem nubia_unlock NUBIA_NX563J
Now you have your bootloader unlocked!
7.- Send this command to flash TWRP: fastboot flash recovery TWRP_recovery.img
Now you have the TWRP recovery flashed!
8.- To reboot into recovery you have to choose with volume buttons the option to reboot recovery and press power.
There is a little problem, the recovery is in Chinese and I don't know you, but I don't understand Chinese :silly: So let's change the language.
9.- When it displays the first screen, something like this pic, you have to press the second button and choose your favourite language (I always recommend English)

Now you have your phone's bootloader unlocked and the TWRP recovery flashed!
DOWNLOADS:
- Nubia Z17 Pack (MEGA)
Alternative mirror (DRIVE)
CREDITS:
- @shimp208 for the Minimal ADB and Fastboot portable included in the pack.
- users of Nubia forum that made the TWRP 3.1.1
- One photo from MIUI
Click to expand...
Click to collapse
Thank you, for the guide but i had a problem here. After unlock bootloader and instal the TWRP success, i reboot the phone and try to access the TWRP, but it get back into stock recovery. I ty to reinstall the TWRP but still same. Please help. Thank you.

jeffaguilera said:
Thank you, for the guide but i had a problem here. After unlock bootloader and instal the TWRP success, i reboot the phone and try to access the TWRP, but it get back into stock recovery. I ty to reinstall the TWRP but still same. Please help. Thank you.
Click to expand...
Click to collapse
u shud root the phone . open twrp / advance / tools / root device.

after i unlock bootloader i flash twrp and gapps. But when i restart the phone, the phone stop on the logo nubia and stop. Why?

the developer of the twrp said that you should root the phone first after you flashed something in the recovery mode.

valeriolorenzon said:
after i unlock bootloader i flash twrp and gapps. But when i restart the phone, the phone stop on the logo nubia and stop. Why?
Click to expand...
Click to collapse
did you root the phone ?
---------- Post added at 01:37 PM ---------- Previous post was at 01:35 PM ----------
valeriolorenzon said:
after i unlock bootloader i flash twrp and gapps. But when i restart the phone, the phone stop on the logo nubia and stop. Why?
Click to expand...
Click to collapse
when you open twrp first go advandec / tools /root phone
then ınstall gapps
but sınce 1 week ım tryıng fix .
ı rootted the phone ı ınstalled twrp ı ınstalled gapps . the google apps all of them was workıng fıne . then later on error agaın.
we need wait for a clear working guide.

sewkanteam said:
u shud root the phone . open twrp / advance / tools / root device.
Click to expand...
Click to collapse
thank you, but i think i will wait untill there is a really working way for this because the last time i tried, i stuck on Nubia logo and it makes me crazy... haha.

jeffaguilera said:
thank you, but i think i will wait untill there is a really working way for this because the last time i tried, i stuck on Nubia logo and it makes me crazy... haha.
Click to expand...
Click to collapse
if you wanna learn you have to brick it first bro

sewkanteam said:
if you wanna learn you have to brick it first bro
Click to expand...
Click to collapse
that's true, haha... the bad is i have no back up phone. I already sold my Nubia Z11 after i got the Z17 so i think i will wait for the best way to install the Gapps.

same here
jeffaguilera said:
thank you, but i think i will wait untill there is a really working way for this because the last time i tried, i stuck on Nubia logo and it makes me crazy... haha.
Click to expand...
Click to collapse
how you fixed this,my phone stuck on the logo and cant do anything,help please
---------- Post added at 09:39 PM ---------- Previous post was at 09:39 PM ----------
how you fixed this,my phone stuck on the logo and cant do anything,help please

assan122 said:
how you fixed this,my phone stuck on the logo and cant do anything,help please
---------- Post added at 09:39 PM ---------- Previous post was at 09:39 PM ----------
how you fixed this,my phone stuck on the logo and cant do anything,help please
Click to expand...
Click to collapse
if u still have twrp go advantec /tools/root phone then ıt will open . if you still cant open then you can download offical stock rom v2.44 put in ur memory card then ınstall. here lınk https://forum.xda-developers.com/nubia-z17/how-to/stock-rom-nubia-z17-v239-t3633206
wipe data system cache /dalvik then install what u downloaded.

nubia z17
sewkanteam said:
if u still have twrp go advantec /tools/root phone then ıt will open . if you still cant open then you can download offical stock rom v2.44 put in ur memory card then ınstall. here lınk https://forum.xda-developers.com/nubia-z17/how-to/stock-rom-nubia-z17-v239-t3633206
wipe data system cache /dalvik then install what u downloaded.
Click to expand...
Click to collapse
my phone dosent have SD slot card

assan122 said:
my phone dosent have SD slot card
Click to expand...
Click to collapse
I knıow . ı have same phone lol
ı meany your phone stroage you can still see it even ur in twrp.
downloand and put it in ur phone stroage ( phone memory ) . then ınstal wıth twrp.
but fiirst root the phone then restart phone. see if ıts ok

i cant
sewkanteam said:
I knıow . ı have same phone lol
ı meany your phone stroage you can still see it even ur in twrp.
downloand and put it in ur phone stroage ( phone memory ) . then ınstal wıth twrp.
but fiirst root the phone then restart phone. see if ıts ok
Click to expand...
Click to collapse
my phone totally stucked i cant get insaid and the twrp not istalled

assan122 said:
my phone totally stucked i cant get insaid and the twrp not istalled
Click to expand...
Click to collapse
ok let me help you.
close phone and open wıth press volume down button then you will be in fastboot.
make sure you have usb connected wıth pc. or laptop
open thıs lınk https://share.weiyun.com/8e5707dc3619ee5d3e584c38a714ea31
you will see twrp root file open ıt then you wıll see onekey tool. download tht open the zip and pres twrp recovery bat
after that with volume down choose reboot to recovery mode.
then twrp will be opened..
so change language to englısh then go advantec / tools / root phone
then restart the phone.
By the wya ı have no idea what have done to phone. what steps you did and how you brıck it and ıs your rom pre ınstalled or offical explaın here so maybe some other frıends can help u aswell. ım not so pro member lol .)

My phone system deleted

Hi guys
Well I guess I ruined my phone , I rooted my honor 7x BND-L21 a couple weeks ago and it worked after I rooted it everything was fine and normal till I was stupid enough and went into the super su app and I saw the full uninstall super su so I was even more stupid to press it and thinking that I’m gonna be free from the root and I won’t have to be afraid that it getting wrecked which I did it with my own hands after I pressed the uninstall super su the phone went black and won’t reboot anymore so I linked the phone to my laptop and went into my internal storage I didn’t find anything but the TWRP file which means there are no more system or systems files what so ever that’s my sad story I hope that any one of you can help me and make a backup to there phone like mine and take the time to help me install it because I don’t know anything about these stuff and I’ll be great full for you guys for the rest of my life
Again My phone is a : honor 7x BND-L21

ayadmanhal said:
Hi guys
Well I guess I ruined my phone , I rooted my honor 7x BND-L21 a couple weeks ago and it worked after I rooted it everything was fine and normal till I was stupid enough and went into the super su app and I saw the full uninstall super su so I was even more stupid to press it and thinking that I’m gonna be free from the root and I won’t have to be afraid that it getting wrecked which I did it with my own hands after I pressed the uninstall super su the phone went black and won’t reboot anymore so I linked the phone to my laptop and went into my internal storage I didn’t find anything but the TWRP file which means there are no more system or systems files what so ever that’s my sad story I hope that any one of you can help me and make a backup to there phone like mine and take the time to help me install it because I don’t know anything about these stuff and I’ll be great full for you guys for the rest of my life
Again My phone is a : honor 7x BND-L21
Click to expand...
Click to collapse
There is , at this time, no suggestion for you to fix.
Because, you do not tell enough of what you were doing, or did.
I mean. First superSU does not work on updated device(Oreo) . So must be nougat, but you did not say.
Next , removeing superSU , from inside of it's settings, will not erase system.
Your description of connecting to PC with USB and not able to see any system files. Well you cannot see Android system files in this way anyhow. Add to that USB (mtp) does not wokif there is no system I place to run the adb/mtp service.
Well if you mean you uninstalled root/superSU , then tried to restart, and that made the black screen, well this is different completely to what you asked. And this makes sense.
If this is what you need. You just need boot.img, if you were in fact on nougat. Or ramdisk.img, and/or kernel.kmg if it was Oreo.
For l21, I do not have these.

mrmazak said:
There is , at this time, no suggestion for you to fix.
Because, you do not tell enough of what you were doing, or did.
I mean. First superSU does not work on updated device(Oreo) . So must be nougat, but you did not say.
Next , removeing superSU , from inside of it's settings, will not erase system.
Your description of connecting to PC with USB and not able to see any system files. Well you cannot see Android system files in this way anyhow. Add to that USB (mtp) does not wokif there is no system I place to run the adb/mtp service.
Well if you mean you uninstalled root/superSU , then tried to restart, and that made the black screen, well this is different completely to what you asked. And this makes sense.
If this is what you need. You just need boot.img, if you were in fact on nougat. Or ramdisk.img, and/or kernel.kmg if it was Oreo.
For l21, I do not have these.
Click to expand...
Click to collapse
bro .
i was playing a game in my phone and the game shot me out and i see the system apps deleted in the menu of apps
i trie restart phone when idid my phone stuck wont open the system but its redirect me to twrp recovery
when the twrp opened i connect my phone with usb to pc
and i see nothing in internal storage only the twrp files !
im find all backup files (IMGs) system.img and cus.img etc..
but idk how to install it
My android version is 7..0 nougat 5.1 emui
and sry for my bad english ..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ayadmanhal said:
bro .
i was playing a game in my phone and the game shot me out and i see the system apps deleted in the menu of apps
i trie restart phone when idid my phone stuck wont open the system but its redirect me to twrp recovery
when the twrp opened i connect my phone with usb to pc
and i see nothing in internal storage only the twrp files !
im find all backup files (IMGs) system.img and cus.img etc..
but idk how to install it
My android version is 7..0 nougat 5.1 emui
and sry for my bad english ..
Click to expand...
Click to collapse
If you have all the needed files, just do this:
1. Boot into TWRP
2. Flash vendor.img, recovery_ramdis.img (Or something similar to that), and system.img
3. Flash them ^^^^ to the required partitions (Partition names to flash to should be self explanatory)
4. Do a factory reset
5. Reboot
Report back please if this works!

I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img

dutyyaknow said:
I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img
Click to expand...
Click to collapse
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???

crayonicle said:
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???
Click to expand...
Click to collapse
Thank you for helping out.
Yes, I tried your suggestion and I used version 3.1.1.0 of TWRP.
Unfortunately it looks like my device is not getting recognized in adb anymore. All I get is either the screen where it says "booting your device now" forever or the white ERROR MODE screen with "Attention! Please update system again.
There are two error messages at the bottom of the screen :
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Now, how do I save myself out of this? It looks like I can't do anything. . .
Edit: correction, it does get recognized in adb in fastboot mode. Can I just flash your suggested TWRP from there?
Edit2: tried to flash the complete_twrp_ramdisk.img in fastboot mode with fastboot flash recovery command. Then I rebooted but instead of TWRP it still shows ERROR MODE

crayonicle said:
If you have all the needed files, just do this:
1. Boot into TWRP
2. Flash vendor.img, recovery_ramdis.img (Or something similar to that), and system.img
3. Flash them ^^^^ to the required partitions (Partition names to flash to should be self explanatory)
4. Do a factory reset
5. Reboot
Report back please if this works!
Click to expand...
Click to collapse
i did everything but nothing changed
ihave installed all IMGs
nothing happened and my phone still empty !
i trying to flash [OpenKirin's RROS ] room
it says succes but when im reboot still rebooting into recovery mode {twrp} 3.1.1.0
and my storage still empty
idk what i have to do
im think we have nothing to do !?

dutyyaknow said:
I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img
Click to expand...
Click to collapse
i think we loose our devices <\3

crayonicle said:
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???
Click to expand...
Click to collapse
ayadmanhal said:
i think we loose our devices <\3
Click to expand...
Click to collapse
There has to be a way to fix it from fastboot mode.
If everything fails, we can still try to send it to a Huawei Center to get fixed. Just don't tell them that you rooted or unlocked your device. I heard that they will then switch out the motherboard for a new one.

dutyyaknow said:
There has to be a way to fix it from fastboot mode.
If everything fails, we can still try to send it to a Huawei Center to get fixed. Just don't tell them that you rooted or unlocked your device. I heard that they will then switch out the motherboard for a new one.
Click to expand...
Click to collapse
we cant go to huawei center bcz the phone unlocked and rooted
so the phone has no Guarantee and they will see the boot when says the device is not trusted <\3

After reflashing my old TWRP from fastboot, I can now access TWRP again and /system partition is showing up too. The ERROR MODE screen still shows up when I boot the phone with VOL + and POWER but when I press VOL + - and POWER I load into TWRP

dutyyaknow said:
After reflashing my old TWRP from fastboot, I can now access TWRP again and /system partition is showing up too. The ERROR MODE screen still shows up when I boot the phone with VOL + and POWER but when I press VOL + - and POWER I load into TWRP
Click to expand...
Click to collapse
my device only auto booting for twrp nothing more

up

no help :\

ayadmanhal said:
no help :\
Click to expand...
Click to collapse
Do you have ADB support on TWRP mode?
If so just use dd command to flash stock boot.img.
Try it by fastboot if you can.
You need to flash stock boot.img because rooting patches boot image and you tried to unroot but were unable to reboot that would replace the patched boot with the stock one.
If i undetstood the issue correctly...
If not, please enlight me...
Enviado do meu Le 2 através do Tapatalk

RSGI said:
Do you have ADB support on TWRP mode?
If so just use dd command to flash stock boot.img.
Try it by fastboot if you can.
You need to flash stock boot.img because rooting patches boot image and you tried to unroot but were unable to reboot that would replace the patched boot with the stock one.
If i undetstood the issue correctly...
If not, please enlight me...
Enviado do meu Le 2 através do Tapatalk
Click to expand...
Click to collapse
i trie much of boot.img files but no change
i tried everything but the phone still wont read the system files

dutyyaknow said:
Thank you for helping out.
Yes, I tried your suggestion and I used version 3.1.1.0 of TWRP.
Unfortunately it looks like my device is not getting recognized in adb anymore. All I get is either the screen where it says "booting your device now" forever or the white ERROR MODE screen with "Attention! Please update system again.
There are two error messages at the bottom of the screen :
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Now, how do I save myself out of this? It looks like I can't do anything. . .
Edit: correction, it does get recognized in adb in fastboot mode. Can I just flash your suggested TWRP from there?
Edit2: tried to flash the complete_twrp_ramdisk.img in fastboot mode with fastboot flash recovery command. Then I rebooted but instead of TWRP it still shows ERROR MODE
Click to expand...
Click to collapse
Have you re-flash with Huawei Multi Tool, but first you must have file update.zip and extract update.app from http://pro-teammt.ru/firmware-database/?firmware_model=BND&firmware_page=0
---------- Post added at 06:48 AM ---------- Previous post was at 06:41 AM ----------
ayadmanhal said:
i trie much of boot.img files but no change
i tried everything but the phone still wont read the system files
Click to expand...
Click to collapse
you on Nougat? have try to upgrade to Oreo from this thread,
https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
there's maybe can fix your system file

Hard bricked my device on my first flashing attempt, what did I do wrong?

Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.

...

douteiful said:
Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.
Click to expand...
Click to collapse
The system destroyed message is a common one. It's a result of avb (Android verified boot).
Simple solution is to disable this verity. Done by flashing in fastboot. It should have been part of the unlocking/ twrp guide. But it's not. This makes many people have this error.
Now as for the other issue. That sounds like the hard-brick error that comes from flashing ginkgo firmware on a willow device.
Ginkgo = note 8
Willow = note 8T
Afaik, this brick is not consumer repairable. I have not found any posts saying they had fixed this problem without service center.

mrmazak said:
The system destroyed message is a common one. It's a result of avb (Android verified boot).
Simple solution is to disable this verity. Done by flashing in fastboot. It should have been part of the unlocking/ twrp guide. But it's not. This makes many people have this error.
Click to expand...
Click to collapse
I could flash and boot TWRP first; I could adb push things too. Everything broke after I wiped the partitions. It's like everything became non-writable and I couldn't even boot TWRP recovery. adb push would say "Permission denied" and fastboot boot would say "Invalid command (Too many links)"
mrmazak said:
Now as for the other issue. That sounds like the hard-brick error that comes from flashing ginkgo firmware on a willow device.
Ginkgo = note 8
Willow = note 8T
Afaik, this brick is not consumer repairable. I have not found any posts saying they had fixed this problem without service center.
Click to expand...
Click to collapse
Yes, I think this is what happened with the MiFlash. My device was probably Willow. I sent it back to repair but I don't know yet if they will be willing to fix it.

douteiful said:
I could flash and boot TWRP first; I could adb push things too. Everything broke after I wiped the partitions. It's like everything became non-writable and I couldn't even boot TWRP recovery. adb push would say "Permission denied" and fastboot boot would say "Invalid command (Too many links)"
.
Click to expand...
Click to collapse
The "too many links" is a message you get when you type wrong commands..
Like example:
Fastboot flash flash boot boot.img
See There are too many commands/ links.
Let's hope the service center will fix you up.

Hello, I just wanted to know was your device in Warrenty?. And how much did the mi service center charged you? Thanks

mrmazak said:
The "too many links" is a message you get when you type wrong commands..
Like example:
Fastboot flash flash boot boot.img
See There are too many commands/ links.
Let's hope the service center will fix you up.
Click to expand...
Click to collapse
Thanks, but I'm pretty sure I entered the command correctly and it was among the lines of "FAILED (status read failed (Too many links))". I have searched for the error but nobody seems to know the cause.
LoadOP2 said:
Hello, I just wanted to know was your device in Warrenty?. And how much did the mi service center charged you? Thanks
Click to expand...
Click to collapse
I bought it only 1 week ago. It was new, so it's under warranty. But I haven't received a response from the service center yet. I don't know what will happen. I'll keep you posted.

douteiful said:
I bought it only 1 week ago. It was new, so it's under warranty. But I haven't received a response from the service center yet. I don't know what will happen. I'll keep you posted.
Click to expand...
Click to collapse
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.

OliveReeve said:
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.
Click to expand...
Click to collapse
I don't know if they changed it of it's because I had already unlocked a bootloader before (my previous Redmi Note 5) but it only asked to wait for 168 hours (7 days).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

douteiful said:
Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.
Click to expand...
Click to collapse
-You don't reboot to recovery after flashing twrp, it wont stick if you don't reboot it
-No problem for wiping system as ive done full wipe before, it will delete your os (needed for converting to cusrom)
-Tried to copy files into sdcard through twrp is not stable in my experience as i couldnt do it as well (not responding), i turned off device as well but it boot back to recovery quickly by it's own (im using latest twrp official), i dont force myself using adb anymore and just use external sdcard, copied rom directly with sdcard reader, install rom and got bootloop (back to recovery automatically, i format data and boot properly)
-You don't have system so turning off and try booting would be worst decision and because your twrp not stick, you can't go back neither
-Too many links is because adb commands is wrong
---------- Post added at 01:34 PM ---------- Previous post was at 01:26 PM ----------
OliveReeve said:
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.
Click to expand...
Click to collapse
i think you dont need to wait anymore, im unlocking my redmi just a few minutes, maybe because new added verification at latest miui unlock

OliveReeve said:
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.
Click to expand...
Click to collapse
lol no.. it's 168 hours usually if you do everything correctly

you should rebout to twrp after flashing it , also you didn't flash vbmeta (i don't know what it does,but mine was fixed once i flash it)

douteiful said:
Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.
Click to expand...
Click to collapse
On step 5, you can still boot into recovery, the button is Vol up+power, but you press voldown+power(as you mentioned) will bring you to fastboot and get into System is destroyed screen. System is destroyed screen is normal. You just need to flash VBMETA. Your biggest mistakes and caresless is you dont do your research thoroughly. Risk is yours.
Make an habit to place your file to sdcard and always flash DMVERITY after anything you have done inside TWRP. DMVERITY is a must. In your case, vbmeta itself disable that force encryption and if you flash this, youll be able to enter fastboot mode.
Too many links means you dont enter the command correctly.
On steps 7 eventually will bring your phone back. I guess you got the indian version of RN8 where many people experiencing and posted on telegrams about this issues that they are unable to flash miui stock roms when that System is destroyed screen happen and end up bricking the phone. The only way and safest way to prevent this is, to flash VBMETA if you got the System is destroyed screen. Do not ever flash miui roms using miflash until you flashed that VBMETA. Then you are good to go flashing any roms using miflash

Update, something weird happened. I just got a message from the service center telling me that the phone had no issues, and they even showed me a video of it working (same IMEI). Which is weird because I'm pretty sure I hard bricked it. My guess is that they unbricked it and didn't tell me for some reason. Either way they didn't charge me any money so I'm happy. I'll get my device back next week and I'll check the things that you told me, particularly the model (ginkgo/willow).

Got my phone today. It's working. I don't know how they fixed it, and it's also unlocked. Just for the record, the Xiaomi ADB tool identifies it as a ginkgo, and the model number is M1908C3JH which is apparently ginkgo as well. If so, why did this all happen then?