Develop Bugs

[Tools] SRK Tool - ROOT/Recovery/Utility/Unbrick/Fix/Backup [20150502]

I don't respond for What-So-Ever done any damage to your Phone, You must accept this risk with yourself..
This is mini SRK Tool that contain only all stuffs of D802 small size
Download link :
SRKtool_1.0.8_d802_droidth.zip
SRKtool_1.0.7_d802_droidth.zip
SRKtool_1.0.6_d802_droidth.zip
For full package visite this thread :
[TOOLS] SRK Tool 2.0 - Tool for LG Mobile - 20150501
Change log :
1.0.8
- Add Manual Root
- Add change logs
1.0.7
- Add Fixed Stuck 2,49 Percent When flash firmware kdz
1.0.6
- initial version
[LGG2-D802] How to Root Stock Lollipop Firmware with SRK Tool
{
"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"
}

Update manual root

Nice work somboons! This is really useful

Update VDO : [LGG2-D802] How to Root Stock Lollipop Firmware with SRK Tool

Can i root n instal twrp with this tool on 30b?

amazing , thanks you .

Hi, I'm hoping someone can help me with my LG G2.
- I can't access recovery or download mode
- I get the multiple drive letters and the one containing the "image"-folder
- I can see the phone-memory in disk management
- It doesn't however show up as anything but "unknown device" under "other devices", nothing under ports
Please help! What can I do when my phone doesn't show up as anything but "unknown device" in device manager?

I managed to get my phone detected as QHSUSB_BULK and ran the fix using this tool. The operation seemed to go well, no errors and said "DONE" at the end. I then disconnected, restarted and tried to enter the download mode. It was still the same though. No download mode, showed multiple drive letters and the "image"-folder, QHSUSB_BULK i device manager.
Any ideas what I can do?
EDIT: It does seem to have made some difference after all. I now get into recovery (well, "Factory data reset"-thingy, no recovery loads). Can I some how flash TWRP and then CM from here?

I got demigod crash handler error and a mate who had this problem told me that this tool can help me.
I tried to use it, but SRK displays "waiting for device" and nothing happens after that. The PC doesn't recognize the phone.

tommy paradise said:
I got demigod crash handler error and a mate who had this problem told me that this tool can help me.
I tried to use it, but SRK displays "waiting for device" and nothing happens after that. The PC doesn't recognize the phone.
Click to expand...
Click to collapse
Screen shot please in device manager too maybe you have to shot circuit.
Sent from my LG-H818 using Tapatalk

I can only enter download mode but no recovery. Is there anyway to fix this issue as i have to flash rom from my recovery. It helped previously with fastboot mode. Now i can enter only download mode. and i dont know how to enter fastboot mode manually. Please help!

beandroid9 said:
I can only enter download mode but no recovery. Is there anyway to fix this issue as i have to flash rom from my recovery. It helped previously with fastboot mode. Now i can enter only download mode. and i dont know how to enter fastboot mode manually. Please help!
Click to expand...
Click to collapse
I sugest, return to stock rom , flash kdz, than root and install new TWRP recovery problem solved.
---------- Post added at 11:53 AM ---------- Previous post was at 11:51 AM ----------
By the way, can this tool fix problem with 32 gb lg g2 d802, becomes 16 gb after bad update ? thanks

4. Fixed Recovery Mode - via fastboot mode (No Recovery,Can't Boot)
not working on D802 32GB stuck on fastboot mode
please please please help help...........

Thank you for the tool, really helped me a lot as I rooted my G2, without much ground work flashed a recovery image and everything was just not good after that.

My D802 isn't recognized by my win7 pc. Unable to do anything with you app. My phone can't boot in any mode however fastboot, download mode or recovery
Édit : i found and could boot on download mode. Well, I could flash by lg flash the lp kdz on my d802. But now i am unable to root it
Edit : problem solved ??

Thanks a lot. I fixed my LG G2 D801 with this tool
Sent from my SM-N910C using Tapatalk

Hello, I need root phone is this work on 4.4.2 / D80220c-466-92 / 32gb phone?
I saw that root + twrp is only for Lollipop ... am i wrong?

LG-G2-802 error native opening
I need help,
srk tool cant writh or read the *.img file the the Picture
Thanks

For D802 V30C on android 5.0.2 - 32GB couldn't find a working solution to root & TWRP together, but this app on manual mode I managed to get to root stage, then I had to manually push the TWRP through ADB which I downloaded from TWRP site. (pushed but did not work)
How and where;
I downloaded the image and placed it in the root of my /sdcard folder and renamed it to twrp.img. then Ran the following commands via adb shell.
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
then I tried the second option (auto root & TWRP) on the ROOT menu, and it worked. :angel:

[Updated 9/23/2015] A hard bricked N1! Please help me to find the solution!

Hi there I bought Chinese version of N1 and flashed with Taiwan system.img which was great everything was awesome~!
but somehow I was curious what would happen if I install layer manager onto N1 that triggered tragedy of hard brick incident of owning N1 within 3 days. After I install some layer it asked me to reboot to apply the layers so I did and bootloop started.
I could see my tablet as MTP and ADB at that time so I could use ADB command to get bootloader but I couldn't get into recovery so I dug more around on xda-forum and installed it. Some said factory reset will fix all my issues especially bootloop so I didn't worry about what I was doing pressed couple time to navigate Yes factory reset/wipe all in stock recovery mode.
After it wiped it all I didn't know that the bootloop is still exist but I can't find my tablet in computer as ADB anymore but moorefield device with unknown driver exclamation mark so I googled more some suggest to use Intel Phone Flash tool.
So I could install right driver for moorefield also I could navigate the N1 as some device so I can flash something into tablet but I need components to fresh install.
{
"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"
}
Yes I'm stuck on here now please help or command me what to do!!
updated 09/05/2015 - Still waiting for solution now I will donate who will find out unbrick my N1 through paypal donation. Please help me out!
updated 09/23/2015 - Couldn't find help from anyone so I ordered one more N1 from now, is there any possible to use the data from new tablet to flash or install onto bricked tablet? I heard linux or ubuntu can connect the bricked N1 even it only shows the tablet as MTP on Windows which I can't even see the device's file or folder. Also Intel phone flash tool doesn't support N1 yet and there are nothing possible without ADB connection on Windows which is probably many boot-loop users have the issue.

i'm here with you, same problem T_T, havent got a solution
---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------
i found dnx and ifwi firmware in Ifwi.zip , but it can not flash

kaikool said:
i'm here with you, same problem T_T, havent got a solution
---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------
i found dnx and ifwi firmware in Ifwi.zip , but it can not flash
Click to expand...
Click to collapse
Can you give links to these files?

you can download and extract your firmware, here: http://forum.xda-developers.com/showpost.php?p=59750742&postcount=2 , you'll see ifwi.zip. Extract it, then you'll find 4 files:
1.bom-token_ann_a0-mofd_v1-N1.bin, => i dont know
2.dnx_fwr_ann_a0-mofd_v1-N1.bin, => dnx firmware (guess)
3.ifwi_ann_a0-mofd_v1-N1.bin, => iwifi firmware (guess)
4.version => i dont know

daion said:
Hi there I bought Chinese version of N1 and flashed with Taiwan system.img which was great everything was awesome~!
but somehow I was curious what would happen if I install layer manager onto N1 that triggered tragedy of hard brick incident of owning N1 within 3 days. After I install some layer it asked me to reboot to apply the layers so I did and bootloop started.
I could see my tablet as MTP and ADB at that time so I could use ADB command to get bootloader but I couldn't get into recovery so I dug more around on xda-forum and installed it. Some said factory reset will fix all my issues especially bootloop so I didn't worry about what I was doing pressed couple time to navigate Yes factory reset/wipe all in stock recovery mode.
After it wiped it all I didn't know that the bootloop is still exist but I can't find my tablet in computer as ADB anymore but moorefield device with unknown driver exclamation mark so I googled more some suggest to use Intel Phone Flash tool.
So I could install right driver for moorefield also I could navigate the N1 as some device so I can flash something into tablet but I need components to fresh install.
Yes I'm stuck on here now please help or command me what to do!!
updated 09/05/2015 - Still waiting for solution now I will donate who will find out unbrick my N1 through paypal donation. Please help me out!
Click to expand...
Click to collapse
How to flash the Taiwan system. img . I need your help .

Velunce said:
How to flash the Taiwan system. img . I need your help .
Click to expand...
Click to collapse
soondin said:
Thank you for your upload.
I was successfully change to taiwan version.
I use ADB Shell and restore use your file.
My one's build number be A5FM51C.
If any chinese version user already rooted N1.
May be can change from china to taiwan.
1. Move system.img to N1's internal storage
2. ADB shell (enabled debug mode)
3. SU (need accept at your N1)
4. dd if=/sdcard/system.img of=/dev/block/pci/pci0000:00/0000:00:01.0/by-name/system
(/pci/pci0000:00/0000:00:01.0 is my one's directory name but I don't know other N1 is same or not)
5. wait some minute. until done shell command.
6. ignore some error message.
7. exit su and adb shell
8. reboot to recovery (adb reboot recovery)
9. wipe cache.
10. reboot N1 and it will update.
I don't try wipe data partion at recovery.
Cause My one is A5CN51C.
I will make some more screen shot like can find google Chrome at playstore.
Click to expand...
Click to collapse
I followed the way it's in Nokia N1 general forum.

daion said:
I followed the way it's in Nokia N1 general forum.
Click to expand...
Click to collapse
I would not recommend any further, i have flashed alot with that program (custom flashing) as i had the layers theme brick too, and after like 30 flashings of recovery, system, iwifi etc (flashed but without success) my bootloader now shows a locked state where i cannot flash anything anymore (i was on 5.0.2 but i wiped my system by accident instead of factory reset to recover from layer theme), so don't flash to much or to reckless as this will lock down your nokia completly like mine. (I now regret buying it though)

Mi A2 lite suddenly damaged???

Hello,
I have a very big problem which i'm not able to solve. So here is my story (i have already tried a lot). First of all, my device worked fine for the first month.
First I installed several gsis. At first I didn't know how to do it but now i know. So I flashed my device a lot…
Then, I installed a gsi and wanted to install gapps. Because of the fact, that twrp isn't really able to install zips yet I tried to unpack the zip and run the sh script with root and fx file explorer.
After that the whole s*** began.
My device freezes so I needed to force a reboot. But then it didn't boot anymore. So I flashed the stock rom again with MiFlash.
After a reboot the device freezes at Bootanimation and reboots. the second boot it reboots correctly and the start screen with "Hi there" pops up. But after a few clicks my device freezes again and reboots again.
After that I decided to install a GSI with Android 9 which worked before this Problem without ones. But same issue here: freezes and reboots.
I thought it is an emmc Problem so I tried something and the Phone was completely Bricked. Only EDL mode worked. Flashing back to stock rom with Miflash wasn't possible in edl mode. Idon't know why. So I decided to download qualcomm's flash tool and reflash the whole emmc in edl mode (nothing else was possible). After flash was completed and the phone rebooted successfully I put it into fastboot and flashed the normal images (stock os) again. Now Miflash worked again.
BUT:
The same problem described before happens again and again:
First boot after flashing stock: reboot in Boot Animation
Second boot: Boot to welcome screen, after around 10 seconds phone freezes and reboots
Following boots are same as second boot.
Can anyone please help me?

That doesn't sound good.. have you tried factory reset in recovery? I would try that after a fresh install with miflash.
Hope you get it sorted

Thank for the reply,
I also did an factory reset.
I have news (I think that they are not really good):
I installed PHH's AOSP 8.1 GSI without gapps to prevent the whole setup stuff.
Now I can use the phone for around ten seconds.
Here is everything I noticed:
Wifi not working -> freeze and reboot if I want to activate it
BT not working -> same here (freeze and reboot if I want to activate it)
Camera not working -> also same
Seems like all devices won't work.
Some other advices?
Edit: after reflashing vendor.img problem is still there.

Ok, now I have another problem:
I cannot enter edl mode again.
How can I do that?
Bootloader is locked and i cannot unlock anymore
it just sys:
Code:
FAILED (remote: oem unlock is not allowed)
and entering edl over fastboot also does not work. I only get:
Code:
FAILED (remote: device is locked! no edl)
But i cannot unlock the bootloader.
Is there an other way to enter EDL Mode?
EDIT:
Ok I think the only way to enter edl mode is to open the device and short the two test points.
I will write if I have news.

Seems like there are other Posts with different problems at the beginning which are now facing the same problem as we do, after some flashing:
https://forum.xda-developers.com/mi-a2-lite/how-to/xiaomi-mi-a2-lite-hard-brick-t3861576
https://forum.xda-developers.com/mi-a2-lite/help/destroyed-t3860080

TJ1999 said:
Hello,
I have a very big problem which i'm not able to solve. So here is my story (i have already tried a lot). First of all, my device worked fine for the first month.
First I installed several gsis. At first I didn't know how to do it but now i know. So I flashed my device a lot…
Then, I installed a gsi and wanted to install gapps. Because of the fact, that twrp isn't really able to install zips yet I tried to unpack the zip and run the sh script with root and fx file explorer.
After that the whole s*** began.
My device freezes so I needed to force a reboot. But then it didn't boot anymore. So I flashed the stock rom again with MiFlash.
After a reboot the device freezes at Bootanimation and reboots. the second boot it reboots correctly and the start screen with "Hi there" pops up. But after a few clicks my device freezes again and reboots again.
After that I decided to install a GSI with Android 9 which worked before this Problem without ones. But same issue here: freezes and reboots.
I thought it is an emmc Problem so I tried something and the Phone was completely Bricked. Only EDL mode worked. Flashing back to stock rom with Miflash wasn't possible in edl mode. Idon't know why. So I decided to download qualcomm's flash tool and reflash the whole emmc in edl mode (nothing else was possible). After flash was completed and the phone rebooted successfully I put it into fastboot and flashed the normal images (stock os) again. Now Miflash worked again.
BUT:
The same problem described before happens again and again:
First boot after flashing stock: reboot in Boot Animation
Second boot: Boot to welcome screen, after around 10 seconds phone freezes and reboots
Following boots are same as second boot.
Can anyone please help me?
Click to expand...
Click to collapse
Hello, the solution is VERY simple, however it requires a certain knowledge of mobile maintenance (I believe that almost everyone has knowledge in opening and storing certain things in a mobile device) go for me ...
Download the latest version of MiFlashTool, and download the V9.6.4.0.ODLMIFF version, open the device, and with CAUTION place a tweezers or something like this in the image and place the USB cable in the phone after the procedure. pin the device and put the USB cable, click Refresh, and the device will appear in EDL mode, flash the system and in 5 minutes the system opens, worked for me !!
But proceed with care, I do not take responsibility for people without knowledge of disassembling of devices to cause some damage in the own device.
{
"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"
}

OK I was able to enter edl mode with the testpoint Methode.
I erased the whole flash storage with QFIL from Qualcomm and also reflashed the emmc.
But it did not work.
After that I entered edl mode again and tried to flash via miflash. ( I also downloaded the New Version available now from the miui site).
BUT:
Linke it was with QFIL, after exit edl mode the phone tries to Boot, but it get stuck in bootanimation. It seems Like it boots to infinity. No Matter what I do. I also tried to change partition with fastboot set active x.
BUT Still No Success

no ideas?

BlackView BV9600 Pro + LineageOS?

Hi! Could you please explain if this ROM will be compatible with my smartphone? I'm not sure, I don't found it on the list on LineageOS website.

Well, someone need to compile it for our bv9600 - i also would appreciate it, but i don't have thoose skills...

Also, lenovo vibe c2

i am not even not able to root my device (blackview bv9600 pro) i don't think that you will be able to have any lineage rom also...
have anyone success to root this device?

giannhs_n said:
i am not even not able to root my device (blackview bv9600 pro) i don't think that you will be able to have any lineage rom also...
have anyone success to root this device?
Click to expand...
Click to collapse
jup, runs root - magisk

AMDFenics said:
jup, runs root - magisk
Click to expand...
Click to collapse
can you explain how did you get root? or give me a guide, all the internet guides i tried failed!
thanks

giannhs_n said:
can you explain how did you get root? or give me a guide, all the internet guides i tried failed!
thanks
Click to expand...
Click to collapse
simply follow this guide -> LINK
- allow OEM unlock in the dev-settings (hit 5 times build number to see)
- allow usb debugging
- reboot to fastboot
- send "fastboot devices" command
- send "fastboot oem unlock" -> acknowledge
- send "fastboot flashing unlock" -> acknowledge
- flash the twrp image "fastboot flash recovery name_of_the_image.img"
- reboot into twrp by power of the device
- after that press vol+ up and power button (if i remember correct.. ) to get into twrp
- now u need a sd-card (micro) put no verity opt encrypt on it and magisk
- Backup all partitions u find.
- format data partition to get the size
- install magisk
- install no verity opt...
reboot
BV9600 should be rooted. Took me serveral times to get it working, because u need directly after "Flashing unlock command" to get the twrp stuff done.
Credits
The TWRP.img comes from www.unofficialtwrp.com
The encryption disabler comes from @Zackptg5 all credits to him. THANKS -> his site LINK
Enjoy

AMDFenics said:
simply follow this guide -> LINK
- allow OEM unlock in the dev-settings (hit 5 times build number to see)
- allow usb debugging
- reboot to fastboot
- send "fastboot devices" command
- send "fastboot oem unlock" -> acknowledge
- send "fastboot flashing unlock" -> acknowledge
- flash the twrp image "fastboot flash recovery name_of_the_image.img"
- reboot into twrp by power of the device
- after that press vol+ up and power button (if i remember correct.. ) to get into twrp
- now u need a sd-card (micro) put no verity opt encrypt on it and magisk
- Backup all partitions u find.
- format data partition to get the size
- install magisk
- install no verity opt...
reboot
BV9600 should be rooted. Took me serveral times to get it working, because u need directly after "Flashing unlock command" to get the twrp stuff done.
Credits
The TWRP.img comes from www.unofficialtwrp.com
The encryption disabler comes from @Zackptg5 all credits to him. THANKS -> his site LINK
Enjoy
Click to expand...
Click to collapse
thanks for the detailed information,
can you also tell me your frimewire version also because i am not available to boot on recovery!
{
"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"
}

giannhs_n said:
thanks for the detailed information,
can you also tell me your frimewire version also because i am not available to boot on recovery!
View attachment 4705498
Click to expand...
Click to collapse
exact same version.
---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------
First u need to go to fastboot mode, to unlock "OEM UNLOCK"
This is easy via adb
-> reboot fastboot
Did u install the correct driver? (ADB driver) is ur device listed?

i tried repacking it myself but with no luck so far, also tried various treble GSI, all booting on my BV9600Pro and basically working but mobile data and phone are broken so that's not an option for now

I don’t understand why unblock the bootloader at all if everything is installed on the MTK platform using the SP Flash Tool !?
Why these dances with adb and fastboot? if a everything is done much easier ...
You do not install the factory software using adb ? not ?? so why can't TWRP be installed and installed using the SP Flash Tool!? Why complicate things?

Root with sp Flash tool
Hi please Anyone could explain this procedure with Sp Flash Tool and post it?

serg2327 said:
I don’t understand why unblock the bootloader at all if everything is installed on the MTK platform using the SP Flash Tool !?
Why these dances with adb and fastboot? if a everything is done much easier ...
You do not install the factory software using adb ? not ?? so why can't TWRP be installed and installed using the SP Flash Tool!? Why complicate things?
Click to expand...
Click to collapse
Because the vendor (Blackview) locks the bootloader (like any other brand does) and does not allow installing any other recovery without it.!?

AMDFenics said:
Because the vendor (Blackview) locks the bootloader (like any other brand does) and does not allow installing any other recovery without it.!?
Click to expand...
Click to collapse
Is this a statement or a question? Sorry, I do not know English and I use a translator ..
II repeat once again, in order to install TWRP you do not need to unlock the bootloader!
it installs without problems using the SP Flash Tool
and this is not an assumption but a statement!
My first copy of the smartphone received TWRP. It was on my copy that all the first tests of TWRP and ROOT were conducted.

serg2327 said:
Is this a statement or a question? Sorry, I do not know English and I use a translator ..
II repeat once again, in order to install TWRP you do not need to unlock the bootloader!
it installs without problems using the SP Flash Tool
and this is not an assumption but a statement!
My first copy of the smartphone received TWRP. It was on my copy that all the first tests of TWRP and ROOT were conducted.
Click to expand...
Click to collapse
I'm glad to hear that it works that way to you. But that doesn't worked for me. So i wrote the way i took, to root. Let the others choose, wich way works for them. :fingers-crossed::good:

I am using another MTK device and SP FlashTool is great it lets you recover from any software brick. So I will advice people to use this method.
I am planning on buying bv9600 pro and having twrp ported and root is a good start to custom roms.
The touch driver issue on twrp should be easily solved with the good kernel module for the twrp. And official twrp support would be nice.
Subscribed to the thread will see where it goes.

hi guys, can you share a clean system twrp backup of bv9600? because my USB is damaged and i can not use sp flash tool to clean restore. thanks!

Hi, i try to root my bv9600 pro, but all i end up is on reboot the system restores to factory no TWRP or anything on it. I connected it to MTKdroidtools and it complains about a file /system/recovery-from-boot.p which restores recovery and obviously after it the system too.
Thanks for any help
edit: LOL nevermind, working fine now, don't know what was going wrong, in a last try just downloaded the latest stable magisk again. Thanks AMDFenics for the howto
Just one thing, can i get rid of this 5 sec. warning that the mobile is unlocked?

dark-wulf said:
Hi, i try to root my bv9600 pro, but all i end up is on reboot the system restores to factory no TWRP or anything on it. I connected it to MTKdroidtools and it complains about a file /system/recovery-from-boot.p which restores recovery and obviously after it the system too.
Thanks for any help
edit: LOL nevermind, working fine now, don't know what was going wrong, in a last try just downloaded the latest stable magisk again. Thanks AMDFenics for the howto
Just one thing, can i get rid of this 5 sec. warning that the mobile is unlocked?
Click to expand...
Click to collapse
Maybe there is a way, but i don't know him. It is a common way for many manufacturer, to say, "here u did something you are not supposed too"

https://www.mediafire.com/file/0j0bx6cb0cb58f5/BV9600Pro_30042019_full.zip/file
Latest Firmware (04.2019) Clean SP Flash tool Backup

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?