Develop Bugs

stuck after wiping

i used ext4 recovery to go to screen to flash a rom and it freeezed after I wiped partition except sd card ( i'm presuming my sd card is still ok)
so i tried to connect my phone to adb on my computer but was unable to flash the rom via fastboot. Is it possible to do so or what am i supposed to do ? am i supposed to place the ROM zip file in the android platform tools folder or push it to my SD card ( I am not too sure what command to input too ) ?

whateheck said:
i used ext4 recovery to go to screen to flash a rom and it freeezed after I wiped partition except sd card ( i'm presuming my sd card is still ok)
so i tried to connect my phone to adb on my computer but was unable to flash the rom via fastboot. Is it possible to do so or what am i supposed to do ? am i supposed to place the ROM zip file in the android platform tools folder or push it to my SD card ( I am not too sure what command to input too ) ?
Click to expand...
Click to collapse
boot in recovery again and reflash the rom. ADB only works with booted phones and custom roms are not possible to be flashed from fastboot anyway but RUU's are.

Sorry I forgot to add that my volume is spoilt so that's why I was trying to use the adb. Is there anyway I can try to flash anything or I have to try the ruu (where can I get it and place it in and the command to type too) ?thanks

i used a card reader and checked my SD card and there's a clockworkmod folder with the files .android_secure.vfat (357,525 KB RAR) ,cache.ext4 ( 5KB RAR) , data.ext4 ( 489,783 RAR) , system.ext4 ( 424,852 KB RAR) , boot.img ( 4,096 KB IMG file) , fsinfo (1 KB file), nandroid.md5 (1 KB MD5 file) , recovery.img ( 8,701KB IMG file ) . anything i can do with them too ? I pulled my batt out as I was afraid it might run down quickly with the boot menu on all day too - not sure if I can get back to it later

{
"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"
}
So I used 4ext touch recovery to wipe all partitions except sd card and it freezed. when i power on , it only shows HTC logo on the bright white screen , and I was able to get to the image above via adb on my PC , not too sure if I am able to do anything next ? my volume knocker is spoilt so I cannot do use that to operate using just the phone itself. anyone has an idea ? thanks

whateheck said:
So I used 4ext touch recovery to wipe all partitions except sd card and it freezed. when i power on , it only shows HTC logo on the bright white screen , and I was able to get to the image above via adb on my PC , not too sure if I am able to do anything next ? my volume knocker is spoilt so I cannot do use that to operate using just the phone itself. anyone has an idea ? thanks
Click to expand...
Click to collapse
Try adb reboot recovery

hdorius said:
Try adb reboot recovery
Click to expand...
Click to collapse
So I just need to type this line ? What should i be expecting after that? Just trying to get an idea,thanks!

whateheck said:
So I just need to type this line ? What should i be expecting after that? Just trying to get an idea,thanks!
Click to expand...
Click to collapse
Connect your phone to your computer, make sure ADB and the drivers are installed, and type it from the computer command line. There are several ADB guides online; Ace Think Tank thread in General forums has one linked.

yup, comp suddenly said found new hardware and asked for drivers , so i assumed it meant it wanted the android 1.0 and got the android-usb-driver and included in the path folder for it to search to install.
after I got to the boot menu, i keyed adb reboot recovery but it says no device found now - have I done anything wrong ?

whateheck said:
yup, comp suddenly said found new hardware and asked for drivers , so i assumed it meant it wanted the android 1.0 and got the android-usb-driver and included in the path folder for it to search to install.
after I got to the boot menu, i keyed adb reboot recovery but it says no device found now - have I done anything wrong ?
Click to expand...
Click to collapse
You need to install drivers with the device unplugged. Install them, then plug the phone and let the PC finish the process. Once it says that the device is ready to be used, you go ahead.
If you are going to install them again, uninstall what it is already in your pc from control panel and then do the above. :good:

oh,,,, I thought it suddenly needed something when plugged and prompted to install some drivers so I did ....
erm, I'm not sure where the driver is now - the only possible options i have under my control panel is 'Add hardware' or 'add/remove program' , I suppose ? windows xp

whateheck said:
oh,,,, I thought it suddenly needed something when plugged and prompted to install some drivers so I did ....
erm, I'm not sure where the driver is now - the only possible options i have under my control panel is 'Add hardware' or 'add/remove program' , I suppose ? windows xp
Click to expand...
Click to collapse
Do you mind if I give a look over teamviewer?

really big thanks to glevitan for able to run my phone again I really appreciate it
but getting back the screen freezing/ ghosting issue I have earlier so not too sure if it's the spoilt volume knocker an issue or digitizer

Bricked ZL550 - Any ideas?

I bricked my U.S. market ZL550 Zenfone 2. My bad, I spent the last two weeks desperately trying everything I could think of to get Link2SD to mount an Ext2 or 4 partition on my SDXC card, and I wasn't at all surprised when it hung on the Asus logo while booting on Saturday.
Anyway, I can't get it to boot normally again. Using fastboot, I flashed recovery, boot and droidboot from the latest Asus ROM, Z008-WW-2.18.40.7, but when I try to flash the system image zip, I get a bunch of errors and a "fail" message on the phone.
I tried sideloading the image with adb but adb won't connect to the phone in recovery mode. Also tried copying the image zip to the SD Card but that wouldn't load, it would only look for MOFD_SDUPDATE.ZIP.
I can return it, I'm not exactly thrilled with it anyway. Anyone have any ideas of what I might try before sending it back?
Thanks! Carl

ConnCarl said:
I bricked my U.S. market ZL551 Zenfone 2. My bad, I spent the last two weeks desperately trying everything I could think of to get Link2SD to mount an Ext2 or 4 partition on my SDXC card, and I wasn't at all surprised when it hung on the Asus logo while booting on Saturday.
Anyway, I can't get it to boot normally again. Using fastboot, I flashed recovery, boot and droidboot from the latest Asus ROM, Z008-WW-2.18.40.7, but when I try to flash the system image zip, I get a bunch of errors and a "fail" message on the phone.
I tried sideloading the image with adb but adb won't connect to the phone in recovery mode. Also tried copying the image zip to the SD Card but that wouldn't load, it would only look for MOFD_SDUPDATE.ZIP.
I can return it, I'm not exactly thrilled with it anyway. Anyone have any ideas of what I might try before sending it back?
Thanks! Carl
Click to expand...
Click to collapse
I'm surprised!! Why do you need link2sd??? with 32 GB Internal, I have 118 Apps installed along with movies and music. Still I have space( I have not used SD Card).
Anyways,
From what you mentioned, you seem to have a ZE551ML. And you Installed Z008-WW-2.18.40.7. It should be Z00A and not Z008. Please download the correct firmware and try out.:good:
Thumb-rule,
ZE550ML = Z008
ZE551ML = Z00A
I guess thats what you did Wrong

Thanks for pointing that out! It's actually a 16GB 550.

I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload

ConnCarl said:
Thanks for pointing that out! It's actually a 16GB 550.
Click to expand...
Click to collapse
for MOFD_SDUPDATE.zip to work, you need to place it on the external sd card and reboot into recovery. It will automatically start to install.
Placing it on the Internal card wont help.
---------- Post added at 08:58 AM ---------- Previous post was at 08:57 AM ----------
lordpipa said:
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
Click to expand...
Click to collapse
I wouldnt recommend that.
He is unable to use adb properly. And if he messes up something, he might even lose his warranty

lordpipa said:
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
Click to expand...
Click to collapse
Tried all that. Many times.

ConnCarl said:
Tried all that. Many times.
Click to expand...
Click to collapse
When i restored from stock via ADB, I was going from a preroot, bricked, because I updated and was getting the little error bot.. After i sideload the image, i still had to factory reset. I'm just guessing, but you did try and do the factory reset after fastboot/ADB.

godgib said:
When i restored from stock via ADB, I was going from a preroot, bricked, because I updated and was getting the little error bot.. After i sideload the image, i still had to factory reset. I'm just guessing, but you did try and do the factory reset after fastboot/ADB.
Click to expand...
Click to collapse
I can't sideload the image, because I can't connect with ADB.

ConnCarl said:
I can't sideload the image, because I can't connect with ADB.
Click to expand...
Click to collapse
but you can get into recovery, it's just when you click on "ADB update" your computer doesn't see the phone, that's my understanding...

Right, correct. I can get into recovery, and fastboot works, but not ADB.

ConnCarl said:
Right, correct. I can get into recovery, and fastboot works, but not ADB.
Click to expand...
Click to collapse
It sounds like you still in fastboot and not recovery. This is what recovery looks like and then you put in it "Apply update ADB sideload."
{
"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"
}

Yep, that is exactly what it looks like. But when I try to sideload, it times out. ADB won't see the phone.

ConnCarl said:
Yep, that is exactly what it looks like. But when I try to sideload, it times out. ADB won't see the phone.
Click to expand...
Click to collapse
I'm pretty sure if it timse out using ADB sideload then it should also timeout when you type ADB deviecs, but try it you should see your serial number sideload.... If you don't then
1. Make sure you have ADB 1.42 with intel drives 1.9
2. Use the stock cable.
3. In device manager make sure there's no unknown Android devices.
4. if ADB still doesn't work then try and flash via fast boot a new boot.img and recovery.img.
5. If you do get to the point where you can sideload...
6. Downloaded the ASUS firmware with WW not CN.
7. Also make sure the firmware package doesn't have ext .zip.zip, because of unknown file ext in windows.

Not sure if this works but you can give it a try.
Have you boot it with Temp CWM?
Delete all cache, including those of under advanced section
install zip file should work to install your full rom. since you stated you cant adb to detect.

Thanks everyone for all the suggestions!
I was just sort of reviewing godgib's screen grab when it slowly dawned on me that at least part of the solution had been staring me in the face all along.
It had never occurred to me that adb might not be able to connect even though fastboot could. Then when I read "you need adb 1.0.32 or newer to sideload to this device", it started to make sense. I upgraded adb and connected but still couldn't sideload. After reviewing godgib's methodical list, I realized it was a driver problem. Once I squared that away, sideload went without a hitch.
Interesting side note...I don't know what build I had originally, but it had to be at least a month old or so. I figured I might as well get the latest release, so I went with Z008_WW_2.18.40.7, and I updated boot/droidboot/recovery while I was at it. The funny thing was that when it booted, it was set for 250 dpi and everything was tiny.
Luckily, since adb was finally working (thanks again godgib) I was able to send "adb shell wm density 480" to put it back to normal.
Thanks again, everyone!
Carl

Glad you got it working...
Sent from my ASUS_Z00AD using XDA Free mobile app

godgib said:
Glad you got it working...
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
Appreciate that.
Of course now auto-rotate is borked. I'll have to either wait for a patch or downgrade.

Did you ever figure out the sdcard problem? I just got the same card and want to do the same thing. But the phone wont see the second partition at all.

i have similar problem too

TWRP Does not appear to stick after reboot - MIUI 10 8.8.3 China Beta / Max 3 128/6

Hi Guys - I installed this twrp via fastboot flash recovery, I am on china dev version MIUI 10 8.8.3 Beta, rebooted to system, powered down, and then volume up & power button to go to recovery - I am greeted by china recovery 3.0 in chinese. It appears twrp does not stick. Device is unlocked bootloader (from vendor), Just flashed over from the fake ROM, this is the 128 GB / 6 GB version phone. What am I doing wrong

Lol, dont understand why you typed "revocery" in your pic but it still understood

badrsj said:
Hi Guys - I installed this twrp via fastboot flash recovery, I am on china dev version MIUI 10 8.8.3 Beta, rebooted to system, powered down, and then volume up & power button to go to recovery - I am greeted by china recovery 3.0 in chinese. It appears twrp does not stick. Device is unlocked bootloader (from vendor), Just flashed over from the fake ROM, this is the 128 GB / 6 GB version phone. What am I doing wrong
Click to expand...
Click to collapse
After flashing china rom, need to boot to fastboot then execute the following commands in adb:
1. fastboot format userdata
2. fastboot flash recovery twrp.......
3. fasboot boot recovery twrp...... so the phone can boot into recovery then follow the rest of the guide if you want to flash xiaomi.eu rom

That's strange, but Orange recovery also reverted
You're right it shouldn't have installed but it did. The Orange recovery also installed, neither stuck tho

Awesome
martin.burgas said:
After flashing china rom, need to boot to fastboot then execute the following commands in adb:
1. fastboot format userdata
2. fastboot flash recovery twrp.......
3. fasboot boot recovery twrp...... so the phone can boot into recovery then follow the rest of the guide if you want to flash xiaomi.eu rom
Click to expand...
Click to collapse
Will try
Thanks

Folks I've hosed it
What's this
Booted to twrp, couldn't find the rom, booted to system.
Lights out
{
"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"
}
Sent from my SM-N950U1 using Tapatalk

badrsj said:
Folks I've hosed it
What's this
Booted to twrp, couldn't find the rom, booted to system.
Lights outView attachment 4591035
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
I'm straggling with Chinese like most of us here. There is an android app you can install on your other phone which would use your cam to translate Chinese. Try that see if it helps...

What I am getting from this (cannot read chinese) but phone goes into fastboot - So I have formated, deleted the eu rom I had on the internal - so start again install the fastboot rom, twrp into it reboot twrp, have eu rom on SD Card and go from there.

badrsj said:
Folks I've hosed it
What's this
Booted to twrp, couldn't find the rom, booted to system.
Lights out
Click to expand...
Click to collapse
After flashing TWRP you need to change file system from ext4 to f2fs, then reboot recovery, from within twrp, wipe cache,dalvic, data and internal recovery ( do NOT wipe system), mount all possible options ( pc will recognize phone, transfer xiaomi.eu rom from pc to internal memory, go to install and flash rom and wait to boot.

martin.burgas said:
After flashing TWRP you need to change file system from ext4 to f2fs, then reboot recovery, from within twrp, wipe cache,dalvic, data and internal recovery ( do NOT wipe system), mount all possible options ( pc will recognize phone, transfer xiaomi.eu rom from pc to internal memory, go to install and flash rom and wait to boot.
Click to expand...
Click to collapse
Change phone file system
How?
Currently it states reset device and loops off and on.
It's a mess
Sent from my SM-N950U1 using Tapatalk

badrsj said:
Change phone file system
How?
Currently it states reset device and loops off and on.
It's a mess
Click to expand...
Click to collapse
From TWRP Wipe->Advanced wipe->Repair or change file system. Reboot TWRP from within TWRP -> Reboot recovery.

Can I flash this instead
Hi, I'd also flashed miui_MIMAX3Global_V9.6.6.0.OEDMIFD_091e94a919_8.1
Can I flash this rom on top of the above?
Fastboot ROM: http://bigota.d.miui.com/V9.6.7.0.O...EDCNFD_20180705.0000.00_8.1_cn_7c9a1a57f8.tgz
Located here
https://xiaomi.eu/community/threads...-and-recovery-rom-9-6-7-0-for-mi-max-3.45198/
Thanks, I'm afraid I'll brick the device?

Also struggled with twrp, switched back to miui's.
Look the twrp official site, find your device and follow step by step the fastboot method till the end. Worked.

I have solved the TWRP issue, the problem now is that when I flash a ROM it does not seem to work and crashes.
I am worried this is going to get bricked in this process. Maybe just wait for the official Global to come out

Which Partitions Change to F2FS
martin.burgas said:
From TWRP Wipe->Advanced wipe->Repair or change file system. Reboot TWRP from within TWRP -> Reboot recovery.
Click to expand...
Click to collapse
Hi, Which partitions to change to F2FS, If we change the Data Partition that would need to reflash Miui Chinese again?

Many Many Thanks - I am up and running
martin.burgas said:
After flashing TWRP you need to change file system from ext4 to f2fs, then reboot recovery, from within twrp, wipe cache,dalvic, data and internal recovery ( do NOT wipe system), mount all possible options ( pc will recognize phone, transfer xiaomi.eu rom from pc to internal memory, go to install and flash rom and wait to boot.
Click to expand...
Click to collapse
Thanks Martin you're very helpful I am now up and running. I am going to list a list of mistakes
1. I should have used CMD, not Powershell (type CMD in the address bar of the folder where your recovery is)
2. I did not know the sequence of flashing (change to F2FS, reboot recovery from within, Wipe Dalvic, Cache, Data) Then flash
3. I did not know how to boot recovery from fastboot (fastboot boot "recovery.img" "name of your recovery")
4. I did not know to change file system for data, (From TWRP Wipe->Advanced wipe->Repair or change file system. Select Data partition, select F2FS) change it then reboot recovery = see step 2 above.
Thanks Very Much
I am listing these for reference, and for those who help others to know what other errors may be committed.

Twrp supposedly installed -- twice -- but i got nothin'
Hi all,
I love this forum -- despite having a bunch of learning disabilities, I've managed to root a half dozen devices over the years thanks to your patience. This time I'm stumped.
Can't install TWRP. It says it is installed successfully with ADB (see screenshot). I used
twrp-3.3.1-0-nitrogen.img and I'm on I'm on Miui Global 10.3.5 Stable (Android 9PKQ1.181007.001).
Command line confirms installation. MM3 reboots when I enter the fastboot reboot to recovery command but it boots into the main system. I can boot into recovery using power/volume up method but it boots to the stock Mi recovery.
Should I try OrangeFox? Does this have anything to do with dm-verity? Is there anything else I can try to get root?
Originally, I wanted to install LineageOS, but what with locked bootloaders, anti-rollback, DM Verity, etc. , I'm guessing that's over my head and would happily settle for rooted stock.
Best,
Amy

Twrp supposedly installed -- twice -- but i got nothin'
EUREKA!!! I found a simple solution to install TWRP no worries about verity etc and I am rooted!
Genius idea came from Youtuber. Here is the link but I will still describe it in case the video gets removed for some reason.
You do it the regular stuff:
adb reboot bootloader
fastboot flash recovery "twrp filename"
But then while you're still in fastboot enter "fastboot recovery" into the command line and before you hit enter, press and hold volume up on the phone.
It boots into TWRP!
Note that you will keep getting Mi Recovery using volume down/power combo until after you use TWRP install (accessing TWRP with above method) to flash magisk.
Then, TWRP seems to stick. (Although just in case it gets unstuck, I installed the official twrp app from the Play store, since it has a 'boot into recovery' option.

fire stick 4k - return to stock?

fire stick 4k with unlock/root via the shorting method. https://forum.xda-developers.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459
is it possible to return to stock? if so, how?
many thanks in advance

JimmyEatFood said:
fire stick 4k with unlock/root via the shorting method. https://forum.xda-developers.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459
is it possible to return to stock? if so, how?
many thanks in advance
Click to expand...
Click to collapse
[EDIT]
IMPORTANT NOTICE, READ BEFOR E CONTINUING. ​If you flash stock rom and you are updated to OS>6.2.8.0 then you will loose TWRP, you no longer will be able to unlock your 4k stick ever again because updating your stick with rom with efuse burner will block the BROM exploit and you will not be able to unlock again.​Again, going stock will lock your device and you'll no longer be able to unlock it again. If you still want to go stock then follow the steps mentioned below.​
Download locked/stock rom for mantis, you will find the rom in XDA posts named like update-mantis-6271-blabla.zip or .bin, if it is in .bin just rename it to zip.
Push it to your internal storage of mantis, wipe everything except internal
Flash it via twrp,
Edit: (This edit was just of older version of OS like 7.1 or 7.3)
You don't have to factory reset, you can always switch back and forth these updates, you can flash 7.1 on top of 7.3 or vice-versa, because there is no actual major OS update, and the files are compatible, and the update replaces the whole system you should know.
If you choose to switch b/w them make sure not to wipe anything, because your remote will be unpaired, so keep that in mind. But if you are rooted and use peacockTV then a factory reset is kinda mandatory after doing this.
[EDIT END]
Reboot, setup your account and when you are fully setup, enable adb and authorize your computer.
At this point your system is fully stock, but your bootloader isn't.
Open the update-mantis-something.zip you will find boot.img, extract it to the folder where you have fastboot installed (download and install if you haven't, you can also use the live image which contains fastboot drivers and application ).
While the stick is connected to your pc
Enter
Code:
adb reboot recovery
when the stick opens TWRP
Enter
Code:
adb shell reboot-amonet
When you see the stick showing black screen with firetv logo, enter
Code:
fastboot devices
to confirm if your device is connected (install drivers if you cannot connect)
If you see your device in fastboot
Enter
Code:
fastboot flash boot boot.img
Code:
fastboot reboot
Your stick will reboot itself.
You will have to factory reset your stick one more time, or some apps like peacock tv will not work.
Good luck.
Edit
Here's a link from stock ROM
https://forum.xda-developers.com/showpost.php?p=81897273&postcount=1
Credits @Skel40

SweenWolf said:
Download locked/stock rom for mantis, you will find the rom in XDA posts named like update-mantis-6271-blabla.zip or .bin, if it is in .bin just rename it to zip.
Push it to your internal storage of mantis, wipe everything except internal
Flash it via twrp,
Edit:
You don't have to factory reset, you can always switch back and forth these updates, you can flash 7.1 on top of 7.3 or vice-versa, because there is no actual major OS update, and the files are compatible, and the update replaces the whole system you should know.
If you choose to switch b/w them make sure not to wipe anything, because your remote will be unpaired, so keep that in mind. But if you are rooted and use peacockTV then a factory reset is kinda mandatory after doing this.
Reboot, setup your account and when you are fully setup, enable adb and authorize your computer.
At this point your system is fully stock, but your bootloader isn't.
Open the update-mantis-something.zip you will find boot.img, extract it to the folder where you have fastboot installed (download and install if tou haven't, you can also use the live image which contains fastboot drivers and application ).
While the stick is connected to your pc
Enter
Code:
adb reboot recovery
when the stick opens TWRP
Enter
Code:
adb shell reboot-amonet
When you see the stick showing black screen with firetv logo, enter
Code:
fastboot devices
to confirm if your device is connected (install drivers if you cannot connect)
If you see your device in fastboot
Enter
Code:
fastboot flash boot boot.img
Code:
fastboot reboot
Your stick will reboot itself.
You will have to factory reset your stick one more time, or some apps like peacock tv will not work.
Good luck.
Edit
Here's a link from stock ROM
https://forum.xda-developers.com/showpost.php?p=81897273&postcount=1
Credits @Skel40
Click to expand...
Click to collapse
thanks

This works perfectly if anyone else is wondering.

Hello, can anyone link me to where I will find the windows drivers for the Firestick in fastboot mode?
I have followed the above and entered fastboot which can be seen here:
{
"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"
}
However powershell doesn't display and connected devices and I am guess it is because Windows doesn't recognise the device in device manager? Image shown below of what my PC is doing:
I had a look through the platform-tools folder but I couldn't find any "drivers" as such that I could point device manager at. Thanks in advance

https://s3.amazonaws.com/android-sdk-manager/redist/fire_devices_usb_driver.zip

0815hoffi said:
https://s3.amazonaws.com/android-sdk-manager/redist/fire_devices_usb_driver.zip
Click to expand...
Click to collapse
Thank you

Question Xiaomi K40 Became A Brick

Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
Click to expand...
Click to collapse
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!

Flash your device in EDL mode.
Please refer to the post below on how to bypass edl mode authentication.
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE!​
Thanks to VD171 for his post.

I think your device is having a Snapdragon Chipset. Sorry but you may try to search on google for contact to person who has authorised edl account to flash a Snapdragon based phone.

Learn more about it in this video

reborn2020 said:
Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!
Click to expand...
Click to collapse
do you still have your fastboot mode on your phone?

mvikrant97 said:
Learn more about it in this video
Click to expand...
Click to collapse
Mi flash didn't recognized my phone.
khazzey said:
do you still have your fastboot mode on your phone?
Click to expand...
Click to collapse
Yes I do.

no bypass for STUCKDRAGON devices for EDL Mode so sad the phone became literally bricked

reborn2020 said:
Mi flash didn't recognized my phone.
Yes I do.
Click to expand...
Click to collapse
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know

khazzey said:
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know
Click to expand...
Click to collapse
I did this before but no hope, I don't know if the problem is I'm using a macbook and run windows 10 via bootcamp, I don't have an actual windows computer.
P.S, I upload the latest status.
{
"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"
}

last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine

ale82to said:
last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine
Click to expand...
Click to collapse
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"

reborn2020 said:
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"
Click to expand...
Click to collapse
I said USB pen to make sure you choose it from TWRP install I think the righ name is external storage or something similar anyway it seems you are doing things the right way I am quite sure u ll bring phone back to life.
I think muiu room is just fine, should it fails try crDroid or dot os (do not try arrow or lineage)

Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual

Anurag3100 said:
Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual
Click to expand...
Click to collapse
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a technician.

Try fastboot erase userdata in cmd after taking your device to fastboot mode
Kinda check different twrp I think your twrp is having any problems plz flash your twrp once again
I hope this will surely work for you my friend.

reborn2020 said:
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a ttechnic
Click to expand...
Click to collapse
Bro try different formats then change to Ext4 well try this twrp https://dl.twrp.me/alioth/twrp-3.6.0_11-0-alioth.img.html umm i hope this will help you out completely.

if you still have your fastboot mode (turn off then hold power + vol. down), you should check your pc driver if adb and fastboot driver installed properly, then try flashing stock rom (dont relock your bootloader), I think what cause the brick is encrypted storage that get accessed by twrp, even if you decrypt it using password, you can still brick the phone by manually mount some partition in twrp

Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.

He
reborn2020 said:
Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.
Click to expand...
Click to collapse
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick

Alipk52 said:
He
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick
Click to expand...
Click to collapse
I can boot to fastboot but I can't do anything with fastboot becuase I wiped out anything on my phone include "firmware" maybe, I don't know, sorry but this's not my major so I can't explain.