Develop Bugs

LG G3 stuck in fastboot. HELP URGENT

Hello everyone! I have a big problem on my LG G3 D855.
I was updating my device for android L (5.0 20e) when I was updating the power went out in my house, and the computer and the phone is turned off, and since then, nothing happens to my G3 D855.
Now my device does not turn over, only appears the logo of LG and then gets a white letters with the following wording:
[510] fastboot mode started
[600] - reset -
[860] fastboot: processing comands
need some help, my device is new, has only 1 week of use, and I made that big bull****! Help me please. I'm desperate.
My device, the computer is recognized as:
ADB interface - Fastboot interface (USB Google ID)
Sorry for my bad english, I'm using Google translator!

http://forum.xda-developers.com/showthread.php?t=2785089

tarroyo said:
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
does not work , as I already said , my device is stuck in fastboot mode, does not go into download mode

My pc hang while I was flashing a stock rom via LG Flashtool... everything was gone in the phone exept "Firmware Update/download mode". No matter which buttons I press during boot (up/down volume, power etc.) I was returned into this! I struggled with flashing using LG Flashtool with no sucess... somtimes I got error and it didn't even start, and sometimes it did start "flashing" but went VERY slow in the % and before it got anywhere near 100%, I got error and the process was aborted. I finally found info about Win8.1 beeing the source of the flashing problems and downgraded to Win7 and woah, flashing now went with speed and was sucessful. For a while there I totally thought my phone was dead...
Ehm... so you only get these white fastboot letters? Strange, you might be even deeper into the **** that I was xD
But I guess if fastboot work you could try to flash the needed files with fastboot flash commands... look here: http://forum.xda-developers.com/showpost.php?p=57296088&postcount=573
This was the only window I could get to when my phone was "half-dead":
{
"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"
}

schoolsux said:
My pc hang while I was flashing a stock rom via LG Flashtool... everything was gone in the phone exept "Firmware Update/download mode". No matter which buttons I press during boot (up/down volume, power etc.) I was returned into this! I struggled with flashing using LG Flashtool with no sucess... somtimes I got error and it didn't even start, and sometimes it did start "flashing" but went VERY slow in the % and before it got anywhere near 100%, I got error and the process was aborted. I finally found info about Win8.1 beeing the source of the flashing problems and downgraded to Win7 and woah, flashing now went with speed and was sucessful. For a while there I totally thought my phone was dead...
Ehm... so you only get these white fastboot letters? Strange, you might be even deeper into the **** that I was xD
But I guess if fastboot work you could try to flash the needed files with fastboot flash commands... look here: http://forum.xda-developers.com/showpost.php?p=57296088&postcount=573
This was the only window I could get to when my phone was "half-dead":
Click to expand...
Click to collapse
I wonder what the fastboot commands to play the laf.img and boot.img into the device

PabloHenrick said:
I wonder what the fastboot commands to play the laf.img and boot.img into the device
Click to expand...
Click to collapse
You can simply "fastboot boot iaf.img", then reflash .kdz with flashtool.

YaDr said:
You can simply "fastboot boot iaf.img", then reflash .kdz with flashtool.
Click to expand...
Click to collapse
Device NOT leaves the fastboot screen , and NOR goes into download mode , how do I '' Simply flash " fastboot boot iaf.img " then reflash .kdz with FlashTool .

PabloHenrick said:
Device NOT leaves the fastboot screen , and NOR goes into download mode , how do I '' Simply flash " fastboot boot iaf.img " then reflash .kdz with FlashTool .
Click to expand...
Click to collapse
Ummm.. You download iaf.img (There was a complete partition dump of G3 on this forum, use search) or extract it from .KDZ (tons of guides on that), you install adb (again, tons of guides and simple installers), you install LG drivers (and again, it's been discussed like million times over, just search for it...), you issue a "adb fastboot boot iaf.img" command from terminal. That's all, really. Then your phone goes into download mode, and you reflash stock .kdz from there.

YaDr said:
Ummm.. You download iaf.img (There was a complete partition dump of G3 on this forum, use search) or extract it from .KDZ (tons of guides on that), you install adb (again, tons of guides and simple installers), you install LG drivers (and again, it's been discussed like million times over, just search for it...), you issue a "adb fastboot boot iaf.img" command from terminal. That's all, really. Then your phone goes into download mode, and you reflash stock .kdz from there.
Click to expand...
Click to collapse
need to download the LAF.img or iaf.img and also the boot.img. I can not find! the one who found it, have a password, and I can not use the password they gave me, which is the LGViet.com always gives wrong password. you could make that up for me?
HAHAHA, Happy New Year!

TWRP 3.0.0-0

Hi,
PLEASE VISIT THE CORRECT AND OFFICIAL THREAD HERE. THIS THREAD WILL NO LONGER BE UPDATED.
As some of you may know, @beroid has a TWRP 3.0.0-0 which he released on his Unofficial CM13 thread. I was unaware of this but lukily (thanks to @yasteellutch) I was told about this new TWRP. So, if you are looking for it, or are unaware of it because you dont look through the original thread, well here it is and now you know!
Installing
Go the download link here and you will be presented with two files.
FOR CURRENT TWRP USERS:
Download the zip file and flash it within TWRP. Your device should reboot automaticly into the new TWRP.
FOR NEW USERS:
Download the img file and place it in your platform-tools folder on your pc. Then reboot your device in fastboot. Then, open a command window in that folder and run commands:
Code:
fastboot -i 0x2970 erase recovery
- IF YOU GET WAITING FOR (ANY) DEVICE SKIP TO NEXT PART
Then enter
Code:
fastboot -i 0x2970 flash recovery recovery.img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation. IF YOU DONT, IT WONT WORK!
IF YOU GET WAITING FOR DEVICE:
Do the same commands but without the vendor id eg.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Credits to:
@beroid for making this. IT IS ALL @beroid's WORK!
So, now you know about TWRP 3.0.0-0!
SCREENSHOTS:
{
"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"
}
-Jev

Hello,
Thank you, I have used it since few weeks without problem. But your TWRP build doesn't seem to include encryption support. TWRP asks for the password but it can't decrypt data partition. Is there some kind of missing module or this is not officially support by TWRP 3 ?

jevtheboss said:
Hi,
As some of you may know, @beroid has a TWRP 3.0.0-0 which he released on his Unofficial CM13 thread. I was unaware of this but lukily (thanks to @yasteellutch) I was told about this new TWRP. So, if you are looking for it, or are unaware of it because you dont look through the original thread, well here it is and now you know!
Installing
Go the download link here and you will be presented with two files.
FOR CURRENT TWRP USERS:
Download the zip file and flash it within TWRP. Your device should reboot automaticly into the new TWRP.
FOR NEW USERS:
Download the img file and place it in your platform-tools folder on your pc. Then reboot your device in fastboot. Then, open a command window in that folder and run commands:
Code:
fastboot -i 0x2970 erase recovery
- IF YOU GET WAITING FOR (ANY) DEVICE SKIP TO NEXT PART
Then enter
Code:
fastboot -i 0x2970 flash recovery recovery.img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation. IF YOU DONT, IT WONT WORK!
IF YOU GET WAITING FOR DEVICE:
Do the same commands but without the vendor id eg.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Credits to:
@beroid for making this. IT IS ALL @beroid's WORK!
So, now you know about TWRP 3.0.0-0!
SCREENSHOTS:
-Jev
Click to expand...
Click to collapse
Not sure if -i 0x2970 is needed for fastboot think its only for fastboot oem
No need for battery removal there is a fastboot command ........fastboot reboot......... that does the same thing

dnahc said:
Hello,
Thank you, I have used it since few weeks without problem. But your TWRP build doesn't seem to include encryption support. TWRP asks for the password but it can't decrypt data partition. Is there some kind of missing module or this is not officially support by TWRP 3 ?
Click to expand...
Click to collapse
Hi,
Please could you visit the thread here and ask the question there. I think TWRP 3.0.1 will fix the issue. :good: If not, on the TWRP website, 3.0.2 has been released which is supposed to fix some decryption issues so please wait for the thread (the one I linked to earlier) to be updated

Flashed wrong kernel by mistake

Hi,
I got a little bit of a problem on my head.... I planned to flash CM12.1 on my HOX but i flashed a different boot.img by mistake! Now i cant get the phone into debugging mode and while using hasoonss toolkit it wont see my device cause i cant get it into debugging mode . Any ideas on how to solve the problem? There are a lot of threads inhere about bricked hox but i cant find one talking about the same problem....
Hope i can get some help on this.

Ow and a bit more info, i can get into bootloader and recovery.

go_insane1981 said:
Ow and a bit more info, i can get into bootloader and recovery.
Click to expand...
Click to collapse
if you can get into bootloader then just get the good boot.img and flash it using fastboot flash boot boot.img

Tried that but it won't see my device.

It doesn't apear in my devices.

go_insane1981 said:
It doesn't apear in my devices.
Click to expand...
Click to collapse
When on bootloader/fastboot mode, type
fastboot devices
to check connection
if it returns your device serial no, then it is good for you to
fastboot flash boot boot.img
adb devices is working when in recovery or on running OS, not on bootloader/fastboot

ckpv5 said:
When on bootloader/fastboot mode, type
fastboot devices
to check connection
if it returns your device serial no, then it is good for you to
fastboot flash boot boot.img
adb devices is working when in recovery or on running OS, not on bootloader/fastboot
Click to expand...
Click to collapse
Tried both ways again but no reaction wth a list of devices. It's blank...

install htc drivers http://www.mediafire.com/?eqrqb44r3ot18g1

SÜPERUSER said:
install htc drivers http://www.mediafire.com/?eqrqb44r3ot18g1
Click to expand...
Click to collapse
Any options on how to install the drivers different from normally? Apparently the drivers won't install as it should install...
Have HTC sync on my system, can i use some of those exe's in there?

This is wat happens with HTC installer.

go_insane1981 said:
This is wat happens with HTC installer.
Click to expand...
Click to collapse
You have a newer sets of drivers installed and the installer exits instead of downgrade the version.
Are you sure you are in fastboot mode?
To enter this.
Power off your phone.
Hold Power and volume down button until phone enters a white screen with Hboot written on it.
{
"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"
}
Now press power button again. The screen should now change to this
Showing fastboot marked in red.
Go to device manager and look for the driver. It should look like this ( Android USB Devices, My HTC)
In cmd type fastboot devices.
My cmd returns this.

Cant seem to get the drivers in my device manager, they are installed but not showing in my device manager...

SÜPERUSER said:
You have a newer sets of drivers installed and the installer exits instead of downgrade the version.
Are you sure you are in fastboot mode?
To enter this.
Power off your phone.
Hold Power and volume down button until phone enters a white screen with Hboot written on it.
Now press power button again. The screen should now change to this
Showing fastboot marked in red.
Go to device manager and look for the driver. It should look like this ( Android USB Devices, My HTC)
In cmd type fastboot devices.
My cmd returns this.
Click to expand...
Click to collapse
Ok i used a old htc and now it sees my device again.

Device manager sees the HOX now too.

go_insane1981 said:
Device manager sees the HOX now too.
Click to expand...
Click to collapse
It was my thought at first. So now we know that htc apparently dropped the support for one x and older devices in their driver pack. Good to know

Now i need to take a look at how i can push a diff rom in there since the other rom apparently wont work..

go_insane1981 said:
Now i need to take a look at how i can push a diff rom in there since the other rom apparently wont work..
Click to expand...
Click to collapse
What rom are you trying to install?

SÜPERUSER said:
What rom are you trying to install?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-x/development/rom-cyanogenmod-12-1-t3396521

go_insane1981 said:
http://forum.xda-developers.com/htc-one-x/development/rom-cyanogenmod-12-1-t3396521
Click to expand...
Click to collapse
Have you flashed this "new storage layout"?
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358

SÜPERUSER said:
Have you flashed this "new storage layout"?
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Click to expand...
Click to collapse
Making a new layout is something i missed, Mone said ;
Flashing instruction like usual: perform a full wipe with TWRP for new layout, flash the ROM, flash the suggested GApps, reboot into fastboot mode, flash the boot.img exctracted from the ROM.zip, reboot into system, enjoy cm-12.1.
So i wiped the damn thing( ) after making a backup offcourse(which btw doesn't help cuz its screwed...). But i completely missed that i had to make a new layout... But stil i am convinced it can be "unbricked" one way or another.
I basicly follwed all the steps mentioned in this thread; http://forum.xda-developers.com/showthread.php?t=2069904 and it al worked up to the point i flashed the wrong kernel. After that i searched the forum for hours and found some things which could be connected but with a total different view of what my problem is/was(partially solved with your help) and ended up with putting a SOS sign up for help.

Question Can not boot any more

Hello comunity,
I installed TWRP on my Galaxy A72 to install Magisk but now I cant Boot any more. Please help my.
I hope you can help me. Moritz

Did you follow all the steps on the XDA thread?
If yes, it could be possible that you additionally need to flash services disabler

Moritz_pro said:
Hello comunity,
I installed TWRP on my Galaxy A72 to install Magisk but now I cant Boot any more. Please help my.
I hope you can help me. Moritz
Click to expand...
Click to collapse
Probably you flashed TWRP image at "fastboot boot TWRPLOL.img" this happens it . now do this,fastboot flash recovery YourTWRP.img then type fastboot reboot then Get your orginal boot.IMG from your Phone version's firmare folder by 7zip or winrar. then do fastboot flash boot boot.img then type fastboot reboot

hey Idk Who can help me for SPOOF(Change by random TEXT) Any android 5.1 to Android8's BASEBRAND Version and KERNEL Version ? How I can change it ? Phone ROOTED and XPosed module ready(not Virtual xposed) ? Please find it or Create new Xposed APK or SUPERuser(ROOT right) APK for Change BASEBRAND and Kernel Version,You know it writes under settings/about phone,Everything changing exclude these.Please Helpme,or if i can do this manually from which file /system or where ?

ineedstoplaggerwatchers said:
Probably you flashed TWRP image at "fastboot boot TWRPLOL.img" this happens it . now do this,fastboot flash recovery YourTWRP.img then type fastboot reboot then Get your orginal boot.IMG from your Phone version's firmare folder by 7zip or winrar. then do fastboot flash boot boot.img then type fastboot reboot
Click to expand...
Click to collapse
I'm not sure if I am understanding all what you are saying right, so please tell me more detailed so I dont't make it worse.

turn of ur phone by holding power button 15 second then wait and be sure phone will not try reboot,then
Press and hold the Power, Volume Down and Home buttons for seconds;
{
"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"
}
Then the device will be the fastboot mode.
get this file then open it (Try open it by 7zip or winrar then extract it there),then click startCMD then type fastboot commands that i talked about it. but first type "fastboot devices" for be sure if it see your fastboot mode phone....... download this https://dl.twrp.me/a72q/twrp-3.6.2_11-1-a72q.img then rename it recovery(Right click on file then click properties and be sure if it says type of file: img file , so fullfile name must be recovery.img then put it into Adb&FastbootCommnderPrayForMe folder then enter this command "fastboot flash recovery recovery.img" then type fastboot reboot then remove cable quick,try power on ur phone, if it still stuck on boot then Poweroff by holding power button 15 second then 2 second later press power button by Volume Up Button together after 3 second later unpress power then continue holding volume up button,If twrp menu opened,swipe right adn go Wipe menu and ONLY chose Clear Cache , then restart phone . if still stuck then go Adb&FastbootCommnderPrayForMe folder and copy recovery.img file to same place and rename it boot(full file name must be boot.img), then go open command then type "fastboot flash boot boot.img" after enter it,Then type fastboot reboot and enter it. if still do same . then Find ur firmware's actual boot.img from your phone device model's firmare version File(firmware versions around 2GB to 10GB)'s boot.img . u can find it in internet too.Hope all works and i will be happy for u too

when I type Fastboot devices my Phone is not regionized what should I do?

Normally PC does not find your device as MTP device while you Hold POWER+home+volumeDown button(I mean fastboot mode without phone bootup).Coz it Shows device as MTP device after Phone bootedup(online).Maybe you tried install its driver as MTP by chosing manual install ? first download and install real usb driver(Adb&fastboot driver) of your samsung phone. https://developer.samsung.com/android-usb-driver then install it. then replug ur phone. Then go Device Manager of your PC,then replug your usb cable,and if you see New Device found like "unknow device or fastboot" then click them then click Properties on it, then click Update driver then click browse for Driver then click Let me pick from list then UNCHECK(unclick) "Show compatible hardware" then find your SAMSUNG ADB driver(if u cant see then click PORTS maybe it installed under Ports drivers) then click next to update it as Fastboot driver . but You can change your PC language to English for See same words in your Pc menus for I help you better coz im not German . but if already your secreen opens ? then you need go phone Settings / about phone/ Tap your phone Firm version 10 times and enable developer menu then enable USB ADB debug for install adb driver easily.if your phone screen not showing anything on screen . then you must just do fastboot mode by fastboot mode keys for install fastboot(samsung android usb driver or ADB driver another name)

When I am in the recovery mode then I see the MTP Window. When I am in the Download Mode I see the other window. I don't now waht the fastboot mode is.

Moritz_pro said:
When I am in the recovery mode then I see the MTP Window. When I am in the Download Mode I see the other window. I don't now waht the fastboot mode is.
Click to expand...
Click to collapse
Ignore what the other guy said above, fastboot is not a thing on Samsung phones. You can make it work with some patches however, but by default there is no fastboot.

ok can you tell me in detail so what do you think is the problem and wehre can I find these patches

Simon1511 said:
Did you follow all the steps on the XDA thread?
If yes, it could be possible that you additionally need to flash services disabler
Click to expand...
Click to collapse
There should be no issues if properly following the XDA thread's instructions.
Moritz_pro said:
ok can you tell me in detail so what do you think is the problem and wehre can I find these patches
Click to expand...
Click to collapse

Thank you for remaining me this option I forgot about it, but I installed a custom Rom, but I'd like to run again on the original software can I install it again. If not, it doesn't matter, but it would be better.

The Rom won't start, the start sign appears but doesn't finish loading.
[ROM][12.1][ENCRYPTION][EOL] LineageOS 19.1 for A52 4G and A72
LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1/12L, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with...
forum.xda-developers.com

Help "failed to write partition" error Redmi 5A (riva)

I had installed in this phone a custom rom a few months back for my friend. Yesterday he told me that the device froze when he was browsing the phone gallery app, and a few minutes later the phone rebooted and couldn't pass the mi logo (so the system wasn't loading I guessed, because the logo of the ROM wasn't showing). I tried to enter TWRP, but even there the phone would get stuck on the TWRP splash page and rebooted back to the MI logo. So I tried to reinstall TWRP (I have still access to fastboot mode) and, after, a newer version, but the problem was the same. I tried booting a recovery image without installing it (fastboot boot twrp.img) and the problem was similar, but instead of rebooting to the MI logo, the phone would get stuck on the TWRP logo. I tried with OrangeFox recovery too, but same problem. I read in another post that it may be a problem with the /data partition, so I (fastboot erase userdata) and tried again the above recovery installation, but it didn't work. I, then, tried to wipe all partion via fastboot, and tried the command "fastboot erase system -w", but it didn't work either. So I tried the way to restore the phone with MiFlash tool, I found the firmware I needed, I flashed it, and after ~4s it gave me the error "failed to write partiton" (see image).
Spoiler: Image
{
"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"
}
I tried with another firmware (this time based on Oreo instead of Nougat), same error. I searched a solution for this error, but I found nothing helpful. Now I have the phone working (=it can power on) and can access to fastboot, but don't know what to do. Can someone out there, with maybe a clearer idea of what's going on, help me? Thanks in advance

Update:
I found out that the problem is flashing this file "gpt_both0.bin" (which is the partition table). Every firmware that I tried failed to flash when trying to fastboot this file. So I tried to remove the line (
Code:
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @echo "Flash tz error" && exit /B 1
) from the flash_all.bat and everything was flashed without errors, but the phone won't start, so this file is necessary. Flashing it separately gave me the same error (failed to write partition). So, I ask again for help, hoping that someone will come to save me

I have same issue. Did you get any working method?

amitkr.xda said:
I have same issue. Did you get any working method?
Click to expand...
Click to collapse
No, I'm still getting the error and trying to test all that comes to my mind. Maybe one day something will work

TheMagicWafer said:
No, I'm still getting the error and trying to test all that comes to my mind. Maybe one day something will work
Click to expand...
Click to collapse
Does your phone go in fastboot? Mine doesn't, but is recognised as QHSBULK 9008, also it's not recognised in adb devices or mi tool

amitkr.xda said:
Does your phone go in fastboot? Mine doesn't, but is recognised as QHSBULK 9008, also it's not recognised in adb devices or mi tool
Click to expand...
Click to collapse
Yes, my phone goes into fastboot. The name QHSBULK 9008 sounds like the phone goes in edl mode. I'm not sure, but searching around I found out it's the name of the phone when it's recognised as by it's qualcomm drivers, or something similar

TheMagicWafer said:
Yes, my phone goes into fastboot. The name QHSBULK 9008 sounds like the phone goes in edl mode. I'm not sure, but searching around I found out it's the name of the phone when it's recognised as by it's qualcomm drivers, or something similar
Click to expand...
Click to collapse
How can I boot in fastboot? It's not going in fastboot or anything

amitkr.xda said:
How can I boot in fastboot? It's not going in fastboot or anything
Click to expand...
Click to collapse
Only (hardware) method possible is to hold the power button and the volume down(-) button simultaneously and wait for the fastboot screen/logo

TheMagicWafer said:
Only (hardware) method possible is to hold the power button and the volume down(-) button simultaneously and wait for the fastboot screen/logo
Click to expand...
Click to collapse
Nothing works, it's just blank screen, no vibrate, no logo nothing

amitkr.xda said:
Nothing works, it's just blank screen, no vibrate, no logo nothing
Click to expand...
Click to collapse
I'm sorry, but I'm not an expert and I can't help you any further. If one day I find a solution, be sure I'm going to write it here

have u try Miui Nougat Global with clean all and lock option? if yes, looks like your emmc has died

Avisadius said:
have u try Miui Nougat Global with clean all and lock option? if yes, looks like your emmc has died
Click to expand...
Click to collapse
Already tried, and it gave me the same error. I really hope it's not a motherboard issue, because a replacement is not worth it. Thanks anyway