Related
Phone fixed, please delete the thread.
3S0PHAGOOS said:
I changed my ROM from stock to 4.4.2 ROM but I got so many issues so changed back to stock ROM, but my LG G2 only has now only 10gb of internal memory.. [I got 32gb lg g2] Now, i tried the instruction from the guy here
http://forum.xda-developers.com/showthread.php?t=2470207&page=3
and also this
http://forum.cyanogenmod.com/topic/...s-on-internal-storage/page__st__20#entry67870
I tried to do the steps as instructed but the result is not the same as mine and then i just exit ADB... then i restart my phone and booomm...
my phone died can't on at all even on download mode... when i try download mode it's just USB Not recognize... please help me ((((
Click to expand...
Click to collapse
Try connecting the phone to a wall charger for 15 mins,and then power up the phone.
nimrodsv said:
Try connecting the phone to a wall charger for 15 mins,and then power up the phone.
Click to expand...
Click to collapse
didn't work, as expected
3S0PHAGOOS said:
didn't work, as expected
Click to expand...
Click to collapse
At the second thread its for HTC incredible, i hope you didnt flashed anything from there right?
Honestly i have no idea what you can do, but trying to eliminate some of the cases..
EDIT: you should try the first method ( http://forum.xda-developers.com/showthread.php?t=2470207&page=3 ) when using this files: https://www.dropbox.com/sh/3pqceuaqsji0dqn/nvR20mLqMF
if that what you did and it didn't worked im guessing that flashing the firmware wont help, but there are wiser people than me to help you, just wait for their input
nimrodsv said:
At the second thread its for HTC incredible, i hope you didnt flashed anything from there right?
Honestly i have no idea what you can do, but trying to eliminate some of the cases..
EDIT: you should try the first method ( http://forum.xda-developers.com/showthread.php?t=2470207&page=3 ) when using this files: https://www.dropbox.com/sh/3pqceuaqsji0dqn/nvR20mLqMF
if that what you did and it didn't worked im guessing that flashing the firmware wont help, but there are wiser people than me to help you, just wait for their input
Click to expand...
Click to collapse
I can't flash anymore, My LG G2 is completely dead, can't get into recovery and download mode, if I tried going to download my pc just say "USB NOT RECOGNIZED"
I've used the following to completely restore my phone and untrip the root checker...
Verizon: http://forum.xda-developers.com/showthread.php?t=2448960
Others: http://forum.xda-developers.com/showthread.php?t=2432476
Xyriin said:
I've used the following to completely restore my phone and untrip the root checker...
Verizon: http://forum.xda-developers.com/showthread.php?t=2448960
Others: http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
did your phone totally bricked when you did it? or you can still go to the download mode?
cause mine is totally can't on.
Do you have the LG bootlogo coming up, if so try this:
(Something similar happened to mine, and I hope this will help.)\
Turn off phone, then when off, hold down power and volume down button until it reaches the LG logo and then release and hold it down again, if that doesn't work, when just hold it down until you see a screen that says something like: Hard reset/ factory reset. For me it took me to my recovery screen, where I just flashed a older ROM onto it, and you should be fine. I then later flashed a recovery file. I hope this helps, and if you need it any clearer, just reply :fingers-crossed:
If it's saying usb not recongized I'd recommend installing the proper drivers for your specific model. Which model do you have since you didn't specifying? Also, dead or charged your phone should boot download mode with volume up being held and plugging the phone in via usb to your computer.
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
If it's Verizon, follow that posted method above correctly. Check for correct com port numbers and make sure replacing the dll file your in the c: drive and not just in your download folder.
hiddenfive said:
Do you have the LG bootlogo coming up, if so try this:
(Something similar happened to mine, and I hope this will help.)\
Turn off phone, then when off, hold down power and volume down button until it reaches the LG logo and then release and hold it down again, if that doesn't work, when just hold it down until you see a screen that says something like: Hard reset/ factory reset. For me it took me to my recovery screen, where I just flashed a older ROM onto it, and you should be fine. I then later flashed a recovery file. I hope this helps, and if you need it any clearer, just reply :fingers-crossed:
Click to expand...
Click to collapse
My phone is completely off
ceredics said:
If it's saying usb not recongized I'd recommend installing the proper drivers for your specific model. Which model do you have since you didn't specifying? Also, dead or charged your phone should boot download mode with volume up being held and plugging the phone in via usb to your computer.
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
If it's Verizon, follow that posted method above correctly. Check for correct com port numbers and make sure replacing the dll file your in the c: drive and not just in your download folder.
Click to expand...
Click to collapse
I have the D802, I already installed the drivers.
If I'm going to go to download mode, It says USB not Recognized and my phone is completely off.
I don't have too much experience with that model so hopefully someone else spying has more information. Sorry buddy.
There is no bootlogo at all? Not even when you turn it on? Try plugging it into a wall charger and if anything happens, also try changing your COM # to 41, if it isn't its Device Manager<Ports (COM & LPT), right click< properties< port settings< advanced..< COM 41, this was from this article I will link right here: http://forum.xda-developers.com/showthread.php?t=2582142
Hope this helps :good:
@3S0PHAGOOS how you did the fix?
cpaixao said:
@3S0PHAGOOS how you did the fix?
Click to expand...
Click to collapse
yes please enlighten us....I am going through the same process and I can not turn it on at all. NOthing comes on...
Send it to me, but if I fix it I get to keep the phone. Right?
Sent from my SM-T210R using XDA Premium 4 mobile app
3S0PHAGOOS said:
Phone fixed, please delete the thread.
Click to expand...
Click to collapse
How did you fix it?
Those experiencing this problem could try this
https://www.youtube.com/watch?v=E7zbs6of_4I
Btw, you should share the solution for those who are in the same situation.
Okay guys I really need your help. So I recently installed the dev os 7.0 upgrade and I decided that I wanted to go back to 6.3. So, I managed to do it and I was at the setup. When I finished, I was forced to update to Oreo. The shield rebooted (since I didn't have much of a choice) and it rebooted me to twrp. I thought the update didn't install so I didn't think much of it.
I just rebooted the system. When I rebooted, it went to the Nvidia logo but then it went to a black screen. I turned off the shield and tried going into fastboot by using the hardware method (the controller and pressing a and b buttons) but it didn't work. It just rebooted the system. By the way, I connected the shield (while it was still on the black screen) to my computer and it shows up as an MTP usb device. But, I can't do any adb commands.
So I'm stuck with the black screen. I'm freaking out because I don't know if Nvidia would be willing to replace or fix it. It's still under warranty. But, I want to know if there is a way to fix the shield before resorting to that. I would really appreciate any help. Thank you!
almost the same issue with me.
device is stuck at android splash screen and am not able to go into fastboot
adb sees it as unauthorized device.
expensive paper weight we got
noobhero said:
almost the same issue with me.
device is stuck at android splash screen and am not able to go into fastboot
adb sees it as unauthorized device.
expensive paper weight we got
Click to expand...
Click to collapse
Almost same issue with me, got to nvidia logo and stuck.. so I rebooted and now its showing as APX device..
Pretty sure theres no way to recover from APX on a 16gb
device unauthorized
noobhero said:
almost the same issue with me.
device is stuck at android splash screen and am not able to go into fastboot
adb sees it as unauthorized device.
expensive paper weight we got
Click to expand...
Click to collapse
try these commands
adb kill-server
adb start-server
This authorized my device with similar issue
---------- Post added at 04:01 PM ---------- Previous post was at 03:59 PM ----------
markdb77 said:
try these commands
adb kill-server
adb start-server
This authorized my device with similar issue
Click to expand...
Click to collapse
Also, hold down A +B button while plugging in power to Shield.
This initiates FastBoot.
markdb77 said:
try these commands
adb kill-server
adb start-server
This authorized my device with similar issue
---------- Post added at 04:01 PM ---------- Previous post was at 03:59 PM ----------
Also, hold down A +B button while plugging in power to Shield.
This initiates FastBoot.
Click to expand...
Click to collapse
there is no way to authorize a device without booting into the UI.
noobhero said:
there is no way to authorize a device without booting into the UI.
Click to expand...
Click to collapse
Authorizing a device is only needed for ADB as far as I know, not fastboot.
blunden said:
Authorizing a device is only needed for ADB as far as I know, not fastboot.
Click to expand...
Click to collapse
he's asking me to
markdb77 said:
try these commands
adb kill-server
adb start-server
This authorized my device with similar issue
---------- Post added at 04:01 PM ---------- Previous post was at 03:59 PM ----------
Also, hold down A +B button while plugging in power to Shield.
This initiates FastBoot.
Click to expand...
Click to collapse
noobhero said:
he's asking me to
Click to expand...
Click to collapse
I was referring to the fastboot part.
blunden said:
Authorizing a device is only needed for ADB as far as I know, not fastboot.
Click to expand...
Click to collapse
i am not able to boot into fastboot as noted in my original post.
no matter, i've somewhat settle the issue
noobhero said:
i am not able to boot into fastboot as noted in my original post.
no matter, i've somewhat settle the issue
Click to expand...
Click to collapse
How you settled this issue?
Sunilmane said:
How you settled this issue?
Click to expand...
Click to collapse
Got myself a new set.
I'm still stuck with a brick 2 months later. Any easy instructions on how to get over this yet? Don't want to bin it. It's so much more powerful than my cheap LG TV's smarts.
duffmagic said:
I'm still stuck with a brick 2 months later. Any easy instructions on how to get over this yet? Don't want to bin it. It's so much more powerful than my cheap LG TV's smarts.
Click to expand...
Click to collapse
there's no way around it, at least not now. no bootloader = paper weight.
noobhero said:
Got myself a new set.
Click to expand...
Click to collapse
You can download the stock recovery rom, all instructions are found on Nvidia website.
HTTPS://developer.nvidia.com/gameworksdownload
dragonuk.test said:
You can download the stock recovery rom, all instructions are found on Nvidia website.
HTTPS://developer.nvidia.com/gameworksdownload
Click to expand...
Click to collapse
well if u followed those replies.. you'll notice that fastbooting is no longer an option. because the bootloader, i guess, is already corrupted..
nothing that we download will work.
Hey guys, need some help here. I have M1 pro European version and just kind of bricked it:
-The screen stays black, I think system is booting because I can hear unlock click if I press the power button. Also notification led indicates charging when connected.
-in fastboot mode the screen is black too, but fastboot sees the device, though the name is different than before the brick.
-In recovery all I can see is black screen.
Now, here's how this happened:
-I got the phone, updated firmware to 323
-Unlocked successfuly with unofficial unlock
-Tried installing TWRP to no avail - The process seemed to go through fine, but no TWRP, just stock Asus recovery. Tried multiple times, tried rebooting straight to recovery from fastboot, tried on different computers. Weird thing I noticed was that write time in fastboot during the process was like 0.001s, which led me to believe it thought it was writing TWRP, but really wasn't for some reason.
-Then I decided to flash fastboot firmware using this guide: https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
-It started flashing, but during the process I noticed again that all the write times
were super low like 0.001s, which made me expect the worst, and well, here I am now.
It's the first time I have so many problems with rooting a phone. Any help is greatly appreciated, I hope I can fix this considering it kinda works in fastboot mode.
Thanks in advance and have a great day.
Not really an expert but there are problems flashing this phone via usb 3.0 port. If you are using one try a usb 2.0 one.
gr8guzzler said:
Not really an expert but there are problems flashing this phone via usb 3.0 port. If you are using one try a usb 2.0 one.
Click to expand...
Click to collapse
Thanks, but I tried both usb 2 and 3 and both yield same results for me.
gr8guzzler said:
Not really an expert but there are problems flashing this phone via usb 3.0 port. If you are using one try a usb 2.0 one.
Click to expand...
Click to collapse
Thanks, but I tried both usb 2 and 3 and both yield same results for me.
Not sure whether this will work (it does in some cases), try full ADB instead of minimal ADB + ASUS drivers installed from the website.
By what name does the fastboot see the device?
Hye, did you solve the problem?
Don't worry, it’s only soft bricked. All you need to do is to flash a stock service rom. Something like: WW_ZB602KL_15.2016.1805.318_20180712 or WW_ZB601KL(ZB602KL)-15.2016.1805.311-20180623. The reason it is "bricked" is because you flashed the incorrect rom for your device, actual model is important, M1 has many variants.
Try flash stock recovery through fastboot, relock ur device, then place whatever version of stock rom into microsd,
And last flash it via stock recovery
Hi sorry but how can i flash it through fastboot? I have same problem...
kothy said:
Hi sorry but how can i flash it through fastboot? I have same problem...
Click to expand...
Click to collapse
Flash stock recovery? Enter fastboot, connect Ur device to PC
Open cmd command in folder where U place the recovery.img file. Then, type "fastboot devices" to make sure Ur device detected
Then type "fastboot flash recovery (filename)"
Done
If you can see your device name when typing 'fastboot devices' you can do as said above. Could it be dead screen?
RAMBO29 said:
If you can see your device name when typing 'fastboot devices' you can do as said above. Could it be dead screen?
Click to expand...
Click to collapse
Yep, if it shows 'blablabla device' It could be dead screen
Then you can go to next step
Its not a dead screen. You just have a wrong rom/kernal/drives/firmware etc. Its a software issue.
Vico100 said:
Its not a dead screen. You just have a wrong rom/kernal/drives/firmware etc. Its a software issue.
Click to expand...
Click to collapse
i am facing the same issue but cant gent into stock recovery and cant enable usb debugging as well
any solutions.
Get into fastboot. Hold volume up and power. Even if you don't see the screen it should still go into fastboot. Check device manager on windows to see if any devices appear. The phone should vibrate when you turn it on and go into fastboot.
Vico100 said:
Get into fastboot. Hold volume up and power. Even if you don't see the screen it should still go into fastboot. Check device manager on windows to see if any devices appear. The phone should vibrate when you turn it on and go into fastboot.
Click to expand...
Click to collapse
i did that works but screen is blank or dead after flashing fastboot rom
What is your phone model and what rom did you flash?
tried this it did not work
https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
---------- Post added at 10:36 PM ---------- Previous post was at 10:20 PM ----------
can you please help me... i have ZB601KL model... can do fast boot i do not know what to do next.... im stuck on the black screen... i can hear the phone booting up and starting up but its just black screen blinking... please help
---------- Post added at 10:39 PM ---------- Previous post was at 10:36 PM ----------
ASUS_X00TDB is the name of the phone when it boots up
same problem with my device. share if you find any solution.
------------------------------------------------------------------------------
fixed my device following this
Hello people of XDA.
Can someone help me please?
I woke up this morning only to find out that my phone won't turn on.
There's 75% left in the battery before I went to sleep.
I tried pressing and holding the power button but it won't turn on.
I also tried charging but the LED is blinking red.
Any solution? TIA
UPDATE:
After more than a month (because of quarantine/lockdown), I finally had my phone checked and repaired. It turns out it's a hardware problem: POWER SUPPLY.
Can you go into recovery mode? If yes, clean flash the rom otherwise use qfil tool to restore your phone
try to plug charger and check if battery is low even if you left it at 75% before you sleep, then try press and hold power button until it boots
otherwise reboot to recovery and fastboot - from here you can do the steps to recover your data or format the phone
Here is the same problem but in the morning i saw my phone in recovery mode..I tried all the possible solution :
1.Flashing fastboot rom through adb
2.Flashing firware through qfill tool
Better to mentioned that above 2 flash procedure were successful bt in the end of all successful flashing my phone booted into again recovery mode instead of system..
So,if there any other solution please help me..Its 48hours i'm working on it bt in the end i
get nothing but failure..!
---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------
swarup16 said:
Here is the same problem but in the morning i saw my phone in recovery mode..I tried all the possible solution :
1.Flashing fastboot rom through adb
2.Flashing firware through qfill tool
Better to mentioned that above 2 flash procedure were successful bt in the end of all successful flashing my phone booted into again recovery mode instead of system..
So,if there any other solution please help me..Its 48hours i'm working on it bt in the end i
get nothing but failure..!
Click to expand...
Click to collapse
:crying:
Thank you for your replies.
My phone CANNOT BOOT to recovery or fastboot so I can't use QFIL.
I think the problem is the battery because I tried charging for hours but the charger is not hot to the touch. THE LED IS JUST BLINKING RED.
I will have it replaced after our community quarantine.
Random Member said:
Thank you for your replies.
My phone CANNOT BOOT to recovery or fastboot so I can't use QFIL.
I think the problem is the battery because I tried charging for hours but the charger is not hot to the touch. THE LED IS JUST BLINKING RED.
I will have it replaced after our community quarantine.
Click to expand...
Click to collapse
try qfil
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
Random Member said:
Thank you for your replies.
My phone CANNOT BOOT to recovery or fastboot so I can't use QFIL.
I think the problem is the battery because I tried charging for hours but the charger is not hot to the touch. THE LED IS JUST BLINKING RED.
I will have it replaced after our community quarantine.
Click to expand...
Click to collapse
qfil doesnt require recovery or fastboot mode.
press v+ and V- button at a time and connect data cable.
Note: qfil drivers must be installed
mr.willy123 said:
try qfil
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
qfil doesnt require recovery or fastboot mode.
press v+ and V- button at a time and connect data cable.
Note: qfil drivers must be installed
Click to expand...
Click to collapse
How would you know if it's working?
Do you have Telegram?
Here's what I've done:
1. Installed Qualcomm drivers for Windows.
2. Downloaded/installed QFIL.
3. Launched QFIL.
4. Press vol + and vol - at the same time and connected data cable.
5. QFIL still shows "NO PORT AVAILABLE."
mr.willy123 said:
try qfil
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
qfil doesnt require recovery or fastboot mode.
press v+ and V- button at a time and connect data cable.
Note: qfil drivers must be installed
Click to expand...
Click to collapse
Problem still not fixed. I'm sure "USB debugging" is enabled on my phone.
When I charge or connect my phone via USB, there is no charging animation.
black screen and vibration ??
mr.willy123 said:
try qfil
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
qfil doesnt require recovery or fastboot mode.
press v+ and V- button at a time and connect data cable.
Note: qfil drivers must be installed
Click to expand...
Click to collapse
soufkas said:
black screen and vibration ??
Click to expand...
Click to collapse
no vibration and battery animation when plugging
soufkas said:
black screen and vibration ??
Click to expand...
Click to collapse
no vibration and battery animation when plugging in the charger
same
Random Member said:
no vibration and battery animation when plugging in the charger
Click to expand...
Click to collapse
have the same problem any update on how to solve this XD
My asus zenfone max pro m1 has not been booting since the april 21st update.
It boots completely, asks for pattern to decrypt storage and irrespective of whether or not i enter the pattern, it reboots. Looks like some system services are failing after boot and hence i need to wipe or clean flash the system partition.
Situation:
This is my dad's phone and it wasn't tampered with at all. Unfortunately boot loader is locked and usb debugging is off.
None of my 2 laptops detect it in fastboot or adb in windows and linux. I've installed proper drivers but it doesn't even show up in device manager as unknown or whatever.
It normally enters fastboot and recovery modes.
I did the root integrity check from recovery and it reported 92 files missing and 90 unknown files.
What i tried:
Reinstalling the same update through recovery (makes no difference)
Installing older updates ( recovery doesn't allow)
Factory reset through recovery (makes no difference)
flashing via fastboot (fastboot doesn't detect)
The only thing i did not try is qfil and I'm not doing that because a lot of people have reported losing their IMEI and other hardware information.
Also, I couldn't find a stock qfil firmware they were stock based made by other people.
Asus's update broke the phone. But I don't see a lot of people posting about it. I could use some help.
Thank you
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
axit50 said:
Can you go into recovery mode? If yes, clean flash the rom otherwise use qfil tool to restore your phone
Click to expand...
Click to collapse
The update messed up its own system files. Clean flash means wiping partition and installing again.
How can we do that from stock recovery where it doesn't wipe /system ?
All installations from recovery are dirty.
dev.kasibhatla said:
My asus zenfone max pro m1 has not been booting since the april 21st update.
It boots completely, asks for pattern to decrypt storage and irrespective of whether or not i enter the pattern, it reboots. Looks like some system services are failing after boot and hence i need to wipe or clean flash the system partition.
Situation:
This is my dad's phone and it wasn't tampered with at all. Unfortunately boot loader is locked and usb debugging is off.
None of my 2 laptops detect it in fastboot or adb in windows and linux. I've installed proper drivers but it doesn't even show up in device manager as unknown or whatever.
It normally enters fastboot and recovery modes.
I did the root integrity check from recovery and it reported 92 files missing and 90 unknown files.
What i tried:
Reinstalling the same update through recovery (makes no difference)
Installing older updates ( recovery doesn't allow)
Factory reset through recovery (makes no difference)
flashing via fastboot (fastboot doesn't detect)
The only thing i did not try is qfil and I'm not doing that because a lot of people have reported losing their IMEI and other hardware information.
Also, I couldn't find a stock qfil firmware they were stock based made by other people.
Asus's update broke the phone. But I don't see a lot of people posting about it. I could use some help.
Thank you
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
The update messed up its own system files. Clean flash means wiping partition and installing again.
How can we do that from stock recovery where it doesn't wipe /system ?
All installations from recovery are dirty.
Click to expand...
Click to collapse
I am using custom ROM (MiUI) when my problem happened.
Random Member said:
I am using custom ROM (MiUI) when my problem happened.
Click to expand...
Click to collapse
I have same prob, did you find a solution
phone is dead ( problem mother boad dead ) any aftermarket service or website ?
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
I'm really appreciate your hardwork ?
Only one solution you have left, open back panel of your phone and find two golden point of EDL mode and then hold two points with joint pin and remember your phone battery should be removed and then connect to pc with hold two golden points now your phone is in EDL MODE then flash with stock rom through mi flash tool and remember inside your pc Modem driver is installed which is required in EDL MODE then that's easier to roll back at initial state of phone ? now your phone work smoothly.
---------- Post added at 01:12 PM ---------- Previous post was at 01:11 PM ----------
I'm really appreciate your hardwork ?
Only one solution you have left, open back panel of your phone and find two golden point of EDL mode and then hold two points with joint pin and remember your phone battery should be removed and then connect to pc with hold two golden points now your phone is in EDL MODE then flash with stock rom through mi flash tool and remember inside your pc Modem driver is installed which is required in EDL MODE then that's easier to roll back at initial state of phone ? now your phone work smoothly.
Check
bCid_diCb said:
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
Click to expand...
Click to collapse
Thus is edl mode test pin points.
bCid_diCb said:
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
Click to expand...
Click to collapse
Edl mode via shorting out the tester point is the only way for you , I beleive your presist or crust partition might have been totally messed up that's why you phone is like this or maybe you didn't enable usb debugging by default luckily your bootloader isn't locked it it was locked then your might have become something like a paperblock of 200grams.
bCid_diCb said:
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
Click to expand...
Click to collapse
Have you tried flashing a rom using miflash https://www.xiaomiflash.com/?
bCid_diCb said:
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
Click to expand...
Click to collapse
i had the same problem years ago with another device ... try to go in twrp press the power botton for 15 sec rebot on twrp format data (not with advanced wipe) and after that a full wipe in advanced wipe.... And look if you solved the encrypt problem.... (Sorry for my bad english)...
---------- Post added at 06:40 PM ---------- Previous post was at 06:17 PM ----------
Yakusha90 said:
i had the same problem years ago with another device ... try to go in twrp press the power botton for 15 sec rebot on twrp format data (not with advanced wipe) and after that a full wipe in advanced wipe.... And look if you solved the encrypt problem.... (Sorry for my bad english)...
Click to expand...
Click to collapse
A lot of time an hard rebot can help... try you can't lose anything ...
I'm curious... let me know if it worked ...
---------- Post added at 08:00 PM ---------- Previous post was at 07:58 PM ----------
Yakusha90 said:
i had the same problem years ago with another device ... try to go in twrp press the power botton for 15 sec rebot on twrp format data (not with advanced wipe) and after that a full wipe in advanced wipe.... And look if you solved the encrypt problem.... (Sorry for my bad english)...
---------- Post added at 06:40 PM ---------- Previous post was at 06:17 PM ----------
A lot of time an hard rebot can help... try you can't lose anything ...
Click to expand...
Click to collapse
I mean with this method...
Yakusha said:
I'm curious... let me know if it worked ...
---------- Post added at 08:00 PM ---------- Previous post was at 07:58 PM ----------
I mean with this method...
Click to expand...
Click to collapse
This method didn't work, I will try the esl option next. I tried it before tho with no success, maybe because I didn't install the qualcomm driver. What could be the problem if my phone still doesn't get recognized?
It's so weird that a software issue causes my phone to not be able to connect to my computer on the recover layer
Try this:. Go in twrp - advanced - terminal - and write reboot edl in the terminal and after that flash the official MIUI rom.... try and let me know...
---------- Post added at 09:00 PM ---------- Previous post was at 08:44 PM ----------
bCid_diCb said:
This method didn't work, I will try the esl option next. I tried it before tho with no success, maybe because I didn't install the qualcomm driver. What could be the problem if my phone still doesn't get recognized?
It's so weird that a software issue causes my phone to not be able to connect to my computer on the recover layer
Click to expand...
Click to collapse
Don't open the phone...
Yakusha said:
Try this:. Go in twrp - advanced - terminal - and write reboot edl in the terminal and after that flash the official MIUI rom.... try and let me know...
---------- Post added at 09:00 PM ---------- Previous post was at 08:44 PM ----------
Don't open the phone...
Click to expand...
Click to collapse
if i type reboot edl in the terminal of twrp, my phone goes into a bootloop, showing the mi.com logo, my computer doesnt recognize anything sadly
Did you try to decrypt in twrp with your account's password?
Yakusha said:
Did you try to decrypt in twrp with your account's password?
Click to expand...
Click to collapse
How to do it?
Yakusha said:
Did you try to decrypt in twrp with your account's password?
Click to expand...
Click to collapse
There is nothing left to decrypt I think. How to do it though(for the next time things go wrong)?
bCid_diCb said:
There is nothing left to decrypt I think. How to do it though(for the next time things go wrong)?
Click to expand...
Click to collapse
With the official rom encrypted when you boot in twrp it ask your password for decrypt... But if you bot in twrp and it don't ask anything then you don't have anything to decrypt...
Try to check the others threads...
I'm pretty sure that you can fix it without open it...
Mouths ago I solved a hard brick on my pixel 2xl that was without fastboot, twrp and pc didn't recognize it... I used a tool for reinstall usb drivers and official rom... I will try to find the guide and send it to you as information...
---------- Post added at 04:24 PM ---------- Previous post was at 03:53 PM ----------
How Windows see you device?... Try to go in device manager and check... if your phone appears in device manager as "QHSUSB_BULK" or unknow device, you have to install the proper driver....
And try this tool https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
So I tried a lot of things, reboot edl didn't work, Testpoint short-circuit didn't work either.
It's hard to say, but I don't know what happened and I have to say goodbye to my beloved phone. It drives me crazy that I didn't found what happened. I don't even know, if I will flash my next phone.
Thanks for your support, if you want to try your luck, or need a display (2weeks old) or any other part, just pm me.
:crying:
bCid_diCb said:
So I tried a lot of things, reboot edl didn't work, Testpoint short-circuit didn't work either.
It's hard to say, but I don't know what happened and I have to say goodbye to my beloved phone. It drives me crazy that I didn't found what happened. I don't even know, if I will flash my next phone.
Thanks for your support, if you want to try your luck, or need a display (2weeks old) or any other part, just pm me.
:crying:
Click to expand...
Click to collapse
Did you try XiaoMiToolV2 ? When you have all drivers, type in program "my phone is bricked", the program should recognize the phone (turning on in twrp) running in recovery and forcing to fastboot mode.
crt-shadow said:
Did you try XiaoMiToolV2 ? When you have all drivers, type in program "my phone is bricked", the program should recognize the phone (turning on in twrp) running in recovery and forcing to fastboot mode.
Click to expand...
Click to collapse
"No devices found[...]"