Related
some guy successfully bricked his N1 as soon as he received it about 2 months ago. When this expensive brick reached my hand, he didn't even remember what he had done... and this brick had been through many many ppl for repair, so there is no way for me to know what exactly happened during the last 2 months...
Anyway, now it:
1. light doesn't turn on when charging(not sure yet whether it is actually charing)
2. trackball + power could gets it to fastboot screen, but none of the key is working then.
3. after single press of power button when powered off, red/green/blue/white color bar and 3 droids on the screen
so , now I cannot put it in fastboot nor recovery mode, stuck.
could there be anything I can do to rescue it?
ndep said:
2. trackball + power could gets it to fastboot screen, but none of the key is working then.
Click to expand...
Click to collapse
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
The only way that a N1 get bricked (software wise) is by upgrading a wrong radio, and unfortunetly the only way to recover it (now) is by sending it to Google/HTC
more explanation
thanks i did try that...fastboot devices could not detect anything,coz it just freezes at that screen and could not enter any mode using power and voldown button.
what puzzlrs me most is that screens with multicolor bars, how on earth does that happen?
britoso said:
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
Click to expand...
Click to collapse
update: the light turns orange now and then when charging, and it is actually charging no matter the light is on or not. ( using my own nexus to verify that )
Did you plugged it to your PC?
I knew a guy who bought a ''flashing device'' capable of formating any chipset over USB, so he could do a clean install of the Firmware again. Perhaps you could find one of these devices over ebay
britoso said:
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
Click to expand...
Click to collapse
That's assuming he has the android sdk installed with the correct drivers. We don't know if the op has.
@vegetaleb: the device you mentioned is somewhat mysterious... a search on ebay with "flash device" does not give me anything related, do you have a specific name?
@C.Slater: I do have them, coz I myself own a nexus too..
should be deleted, sorry
@vegetaleb: the device you mentioned is somewhat mysterious... a search on ebay with "flash device" does not give me anything related, do you have a specific name?
@C.Slater: I do have them, coz I myself own a nexus too..
edit: isn't there an option to delete this reply? I clicked the submit button twice,sorry.
does typing fastboot devices in the cmd prompt work for your non bricked nexus?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Does holding power+trackball bring you to fastboot?
Yes=It's not bricked
No=Kiss it goodbye, it's bricked
Simple as that
TFJ4 said:
Does holding power+trackball bring you to fastboot?
Yes=It's not bricked
No=Kiss it goodbye, it's bricked
Simple as that
Click to expand...
Click to collapse
power+trackball will bring it to fastboot screen, note just the fastboot screen, it just freezes there. All the buttons does not work, and connecting to PC using a USB cable does not show "FASTBOOT USB".
However, it could enter HBOOT with power+voldown, I noticed it searches for passdiag.zip , passdiag.nbh, etc. Could I use this builtin function to flash it? which file in this post should I use?
http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
I tried to use the first one ( http://www.romraid.com/paul/nexusone/EPE76-update-nexusone-stock-images.zip ), rename to PASSDIAG.zip , but HBOOT is still complaining about "No Image"
Perhaps it's physically damaged!
It remembers me of my boss iphone that looked perfectly normal but couldn't get a FW installed because the power part has been damaged by water(power button couldn't work at all)
Try renaming it to passimg.zip and use hboot again.
speedyls91 said:
Try renaming it to passimg.zip and use hboot again.
Click to expand...
Click to collapse
tried PASSIMG.zip , still "No Image"...
You can send it to htc for repair but the downside would be that you would never know how to deal with this kind of problem yourself...
Continue the research and keep us posted ...
i maybe wrong but i think is it case-sensitive.....meaning PASSIMG.zip would fail but passimg.zip wouldn't.....Correct me if i'm wrong please....
Case sensitive
I'm pretty sure it is case sensitive. Used to be that way with other android and HTC devices. Can't imagine it's changed.
linux is case sensitive, for sure.
i say approach from the adb/fastboot route, using usb. first, ensure that you have all the correct drivers etc for adb use (the sdk, the usb drivers, and the device specific drivers).
try ur 'adb devices' command
if adb sees it, in normal mode, you should be okay. make sure the phone has 'usb debugging' turned on in settings
Hi there, can somebody GUIDE How to unbrick ONEPLUS 5?
My OP5 is dead, black screen, just can be recognized to PC via qualcomm drivers, but i have searching some guide to do this, no found.
I think could be some easy do this, because there is a way for OP3T, via msm tool.
Thank you abot the support.
you have fast boot access and are you able to get into bootloader
#3
dalepothen said:
you have fast boot access and are you able to get into bootloader
Click to expand...
Click to collapse
hI there,
No, i cant full black screen!!!
i dont know if there is a way to have fasboot acces , full black screen,
let me tell you, when i conected the phone to pc, was recognized via qualcoom drivers
Thank you
How did you end up bricking it?
dalepothen said:
you have fast boot access and are you able to get into bootloader
Click to expand...
Click to collapse
mahoro.san said:
how did you end up bricking it?
Click to expand...
Click to collapse
hi, i did it trying to change a rom via twrp, when finished flashing gone black screen!!
Connect phone to computer
Type
adb devices
See anything?
If not try fastboot devices
If you see anything, try typing
adb reboot recovery
If you can get here, you can try flashing the stock room over your current ROM. Make sure to wipe cache
Binary Assault said:
Connect phone to computer
Type
adb devices
See anything?
If not try fastboot devices
If you see anything, try typing
adb reboot recovery
If you can get here, you can try flashing the stock room over your current ROM. Make sure to wipe cache
Click to expand...
Click to collapse
Hi !!! i did it!!! but .... bad news , nothing good!!!
...fastboot devices .... still dead
........adb devices .... still dead!!!!
black screen!!!
I am facing an issue. I want to flash twrp into my coolpad cool 1 dual but my fastboot can't detect my device. ADB is able to detect it but as soon as I run the command "adb reboot bootloader" to boot my phone into fastboot mode fastboot doesn't detect my device any more.. I have tried updating the "android bootloader interface", " android adb interface" drivers but still nothing does work.. Tried a various types of usb driver available at xda in various threads but none work. What to do now? Please give me a solution to install twrp~
I got the same problem here, I installed a lot of several drivers and nothing. I keep surfing on the web trying to find a solution. If i get one I will notice you.
Gausskun said:
I got the same problem here, I installed a lot of several drivers and nothing. I keep surfing on the web trying to find a solution. If i get one I will notice you.
Click to expand...
Click to collapse
Good luck! My coolpad is already dead.
souvik095 said:
Good luck! My coolpad is already dead.
Click to expand...
Click to collapse
Same here.
Now i have no recovery, no system (ROM), and no EDL mode too.
Fastboot mode runs partially, with errors (REMOTE ERROR blablabla).
sad :crying:
I have already ripped apart the device. Took out the battery made an led emergency lamp out of it. The rest of it lies in some corner of my workshop!
Install pdanet in pc and mobile both
Hello everybody,
First off, I hate people who don't search on google before making a post, I have been searching for 4 days and I feel that it's appropriate to ask now.
I will make 2 parts to this thread, one will be a very fast explanation of what I did and the second part will be the same but a very thorough with a step by step process of what I messed up...
TL;DR: I was tired, late in the evening I flashed for some reason a Partition table of a Mi Note 3 on my Mi A1... I am now bricked and cannot access anything, fastboot, ADB, recovery nothing! I guess my phone is in EDL mode cause when I plug it in it flashes its led. "Qualcomm HS-USB QDLoader 9008" Is what I see in my device manager.
What do? oh, I forgot! I cannot access anything through any combination of buttons. I am stuck here, where I am!
The full thorough explanation for people who are bothered to read fully. (Includes my excuses for making noob mistakes, might be fun to read idk.)
Young me on a Sunday evening decides to reinstall magisk but this time with twrp cause I did it without twrp (yeah yeah I know). I was left without OTA's and after uninstalling anything that had something to do with Xposed or magisk I trashed it all. and stupid me thought that maybe? maybe? just maybe deleting Dalvik Cache would help me get my OTA's back after injecting my original ROM. This is where the fun begins.
I was not wanting to go through reinstalling magisk and all that to wipe the Dalvik Cache, I thought that that was my mission now, so I decided to search for methods that don't require root or being in the system, so some kind of fastboot or ADB command or something idk. I tried installing twrp and without my understanding that failed miserably and then I read some post where someone said that they flashed a mi note 3 partition table on their phone and something worked. Being the naïve little boii that I am, let's do that hey? Bam! bricked! I read somewhere I can open the phone and remove the battery and not having the tools is a mess, having to ask friends for some and voiding my warranty for something that probably won't work and after reading I understood that I'm in "EDL 9008 recovery" or something like that. I cannot boot into anything, I only have EDL 9008 to work with. I tried using Xiaomi's flasher tool and it would never respond to the initial hello packet (duuhh! I can't use ADB nor fastboot).
I know that this was stupid, I know! I learnt my lesson. If there is nothing we can do can I at least somehow get my internal storage data back? I deleted the backups from google drive for a short amount of time but randomly 5hrs prior to this sad story. All I have safe are now my contacts.
I hope you guys have some ideas! I feel like I'm fked but maybe with EDL 9008, there is a little glimmer of light?
P.S. If you guys somehow get me into fastboot I can flash a correct partition table back. My PC has all drivers so I can do this!
Sincerely, Micheal.
There is a way although i did tried it yet.
First of all sorry for my English.
Download latest MiFlash tool and qualcomm driver, this package contain both but not latest MiFlash so you should download lastest version from official site.
https://www.fshare.vn/file/H3R8M6OMRP2R
Download lastest stock rom.
You will need a good USB type C cable, dont use the one come with phone because you dont want to cut it in half.
Yes, that exactly what i said. Cut it in half, there are 4 small wire (or maybe 5 with type C?), remove it outer plastic and reconnect them.
Join the green and black cable, like you short circuit them, then plug your phone into PC with that cable without release green and black, wait for 5 sec then seperate them, the green and black.
Check device manager on your PC, you should hear device connect sound and qualcomm HS-USB QDLoader show up under Ports.
Open MiFlash and try to flash it.
You may want to check this video, although it in Vietnamese but you should understand the usb cable part.
https://www.youtube.com/watch?v=d5-1I9rWTiw
Hi, interesting situation. What about following this guide: http://en.miui.com/thread-235865-1-1.html ?
Its for some other phone, but try instaliing some drivers and you may get some signal of life.
Very interesting
I have thought about doing this as I had an old type-c lying around that came with the phone (I use a beautiful cable I bought off amazon) and saw this method to flash but never tried it..
I'll give it a go thanks.
btw. Your English is good I understood everything
The second comment from TrueMS:
I already have all drivers installed and in the long post I said that I have a flashing led that indicates that i'm in EDL 9008, the phone isn't dead but it won't turn on with any driver
m1shka said:
Very interesting
I have thought about doing this as I had an old type-c lying around that came with the phone (I use a beautiful cable I bought off amazon) and saw this method to flash but never tried it..
I'll give it a go thanks.
btw. Your English is good I understood everything
The second comment from TrueMS:
I already have all drivers installed and in the long post I said that I have a flashing led that indicates that i'm in EDL 9008, the phone isn't dead but it won't turn on with any driver
Click to expand...
Click to collapse
Yes, thats what I meant. Well, I dont know how to help you, wish you luck. I remember how I flashed wrong ROM for my S3 Mini and it was completly trashed, I'm glad that Xiaomi gives us at least some signs of life and hope.
And btw. I would rather charge the phone somehow - I hope it charges even in EDL mode, because if your phone dies while flashing with MiFlash, things can be even worse.
EDIT: I also found this guide, you can try it out: https://forum.xda-developers.com/g4/general/guide-unbrick-via-external-sdcard-qfil-t3748946
Okay so now a major reply!
I have stated in the OP that I am already in EDL, there is no need for cutting the cable or installing any driver, I am in EDL 9008 I don't need to "try to get there" as i'm already there.
These guides failed miserably as I have already tried them, my phone "doesn't receive a hello packet" from my phone, as I can't use adb or fastboot, or recovery.
I'll download linux and give that usb method a go then
m1shka said:
Okay so now a major reply!
I have stated in the OP that I am already in EDL, there is no need for cutting the cable or installing any driver, I am in EDL 9008 I don't need to "try to get there" as i'm already there.
These guides failed miserably as I have already tried them, my phone "doesn't receive a hello packet" from my phone, as I can't use adb or fastboot, or recovery.
I'll download linux and give that usb method a go then
Click to expand...
Click to collapse
Wish you luck:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
m1shka said:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
Click to expand...
Click to collapse
did you try to hold more than 30 second ? and also , do you have flash log ?
m1shka said:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
Click to expand...
Click to collapse
So did you flash official stock ROM? Because I dont understand why doesnt it work... btw. when you flashed the ROM, did you lock bootloader?
Cant be battery dead?
If you are on "Qualcomm HS-USB QDLoader 9008" you will be able to flash stock fastboot firmware. Flash it using MiflashTool. Normally Miflashtool will recognized it as COMXX, where XX is the number of the port.
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
m1shka said:
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
Click to expand...
Click to collapse
Good job mate, so that SD card method worked with Linux? Be happy that your phone is alive.
EDIT: Maybe consider locking bootloader? Try it if youre on official stock.
EDIT 2: By flashing that ROM I guess you lost all data, but you can try to boot in TWRP without installing it and browse in file manager to see, if there is any data.
TrueMS said:
Good job mate, so that SD card method worked with Linux? Be happy that your phone is alive.
Click to expand...
Click to collapse
No... I was going to do that tomorrow but I decided to disable driver signature enforcement which worked. This should be written everywhere if it's this important..
Is there still a way to get my internal data back? Question as well, in recovery "mounting" the data partition will that let me get everything back "mounting" the drive to the pc? or do i not understand what mounting is.
m1shka said:
No... I was going to do that tomorrow but I decided to disable driver signature enforcement which worked. This should be written everywhere if it's this important..
Is there still a way to get my internal data back? Question as well, in recovery "mounting" the data partition will that let me get everything back "mounting" the drive to the pc? or do i not understand what mounting is.
Click to expand...
Click to collapse
As I said, you can try it, but when I flashed my Nougat stock ROM, i lost all the data. Or you can boot into TWRP and connect with USB to your computer to see the data in phone.
Good that your phone is working now, as for the data, i once forgot to remove encrypt before flash custom rom, but when enter TWRP it will ask for old password to decrypt. Just enter your old pass then connect to PC, or use TWRP file explorer to copy your data to sdcard
GVN.Gallus said:
Good that your phone is working now, as for the data, i once forgot to remove encrypt before flash custom rom, but when enter TWRP it will ask for old password to decrypt. Just enter your old pass then connect to PC, or use TWRP file explorer to copy your data to sdcard
Click to expand...
Click to collapse
None of the passwords I used worked.. I just factory reset it, thanks alot everybody. And now I will be more careful, don't flash anything weird. And backup!
I understood why I can't get the data back, if android fails at the encryption it jsut deletes everything!
My fone also in 9008 please can you guide me
I did the same what you have and it's on 9008 my flashing is successful but still my fone is not opening help me
m1shka said:
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
Click to expand...
Click to collapse
How did you fixed i'm stuck in EDL?
SevenSlevin said:
If you are on "Qualcomm HS-USB QDLoader 9008" you will be able to flash stock fastboot firmware. Flash it using MiflashTool. Normally Miflashtool will recognized it as COMXX, where XX is the number of the port.
Click to expand...
Click to collapse
i am in Qualcomm HS-USB QDLoader 9008 but i can't flash, it doesn't matter if the phone is on fastboot mode or turned off (i can't even turn it on)
Hi !
I need your help please, my phone doesn't want to enter in fastboot mode.
* Black Screen 100%
* If I press power button after 4 or 5 seconds it does a vibration
* Power button + Volume Up (looks llike it turn off the phone)
* Power button + Volume Down (looks like it want to enter in fastboot mode)
When my phone is connected to the PC it is recognized as: Unknown USB Device ( Device Descriptor Request Failed )
Blue LED always turned on (once the phone is recognized as Unknown)
The first that I tought when I saw the message ( Unknown USB Device ) was... ok this phone is really hard bricked and is needing a Test Point.
I did the Test point and my phone still giving the same message.
I tried different USB ports and same problem. (USB ports are ok)
I didn't tried a different USB cable and it has higher probabilities that my USB could be damaged. because (Device Descriptor Failed) is a problem from faulty USB ports or Cable.
But my USB Cable looks like new and it was used few times... also I tried moving a bit the connectors to see if it does something but no.. nothing happened.
The USB Port from the phone is like new. (I opened the phone)
If you have experience with the message: "Unknown USB Device (Descriptor Request Failed)
Please give me some help !
Hi !
Looks like the real problem was from drivers. Finally I installed the K20 drivers from this site : https://gsmusbdriver.com/xiaomi-redmi-k20
Then I did the test point
1) I Pressed power button with the test point
2) I heard a vibration
3) I released the power button but I continued with the test point
4) Voila the drivers were installed correctly and now my phone is recognized as: " Qualcomm HS-USB QDLoader 9008 "
EDITED:
If you are experiencing in device manager: USB Device Unknown Descriptor Request Failed maybe could be faulty USB port or cable. In my case was the cable. Now is working perfectly everything with a new USB Cable.
Now I'm trying to flash the phone using " Mi Flash Tool "
I downloaded the stock rom from Xiaomi site.. By the way my phone is with bootloader locked and is not rooted.
I pressed Flash button and the program asked for EDL Authentication. "I Created a new account" Logged suscessfull and then:
"Error" Root Element is missing.
WTF? why xiaomi is asking me for a rooted phone??
Please Help, any Idea about what I'm doing wrong?
romeosantos said:
Now I'm trying to flash the phone using " Mi Flash Tool "
I downloaded the stock rom from Xiaomi site.. By the way my phone is with bootloader locked and is not rooted.
I pressed Flash button and the program asked for EDL Authentication. "I Created a new account" Logged suscessfull and then:
"Error" Root Element is missing.
WTF? why xiaomi is asking me for a rooted phone??
Please Help, any Idea about what I'm doing wrong?
Click to expand...
Click to collapse
I think EDL is a special account authorised by Xiaomi.
Enviado do meu Mi 9T através do Tapatalk
Yeah u need a EDL Flash and for that an EDL verified Account, which u can't get anymore from xiaomi ..
you have to find someone who are willing to do it for you. Usually you have to pay for it .. around $50.
or try this
https://forum.xda-developers.com/showpost.php?p=79004670&postcount=82
solved said:
Yeah u need a EDL Flash and for that an EDL verified Account, which u can't get anymore from xiaomi ..
you have to find someone who are willing to do it for you. Usually you have to pay for it .. around $50.
or try this
https://forum.xda-developers.com/showpost.php?p=79004670&postcount=82
Click to expand...
Click to collapse
I went to S-Unlock and they said "Service offline" do you know or somebody know from other site? or someone that can help me?
romeosantos said:
I went to S-Unlock and they said "Service offline" do you know or somebody know from other site? or someone that can help me?
Click to expand...
Click to collapse
Did you try this :
- Download the stock ROM from xiaomi website, no tools needed, just adb and fastboot installed
- Extract the rom to a folder and launch "flash_all.bat" with admin.
- If you encounter an issue try it with another OS (try this if you don't want to install another OS : https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755)
Tell us if it works.
Gimlouuuu said:
Did you try this :
- Download the stock ROM from xiaomi website, no tools needed, just adb and fastboot installed
- Extract the rom to a folder and launch "flash_all.bat" with admin.
- If you encounter an issue try it with another OS (try this if you don't want to install another OS : https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755)
Tell us if it works.
Click to expand...
Click to collapse
Good news? I think that my phone now is booting on Fastboot mode? I don´t know how but today it was recognized by the PC as:
MTP USB Device
Please help What I can do to flash my phone¿? it is fastboot mode right? in fastboot mode I can do flash without an account authenticated righT?
Im trying to use Mi Flash TOOL again and Im getting this message:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
Im using the latest rom for the K20 global phone but dont know why it is stuck with that message and STATUS: Flashing but it doesnt do any progress.
What Can I do?? is ok MTP USB Device? is that the correct drivers to do a flash in fastboot mode??
Thanks guys!
romeosantos said:
Good news? I think that my phone now is booting on Fastboot mode? I don´t know how but today it was recognized by the PC as:
MTP USB Device
Please help What I can do to flash my phone¿? it is fastboot mode right? in fastboot mode I can do flash without an account authenticated righT?
Im trying to use Mi Flash TOOL again and Im getting this message:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
Im using the latest rom for the K20 global phone but dont know why it is stuck with that message and STATUS: Flashing but it doesnt do any progress.
What Can I do?? is ok MTP USB Device? is that the correct drivers to do a flash in fastboot mode??
Thanks guys!
Click to expand...
Click to collapse
Does the phone display the fastboot logo? If it does, then you have to remove some lines from the flash_all.bat file. The first ones where it says something about getvar product.
you can fastboot and just push it in cmd if fastboot active. I bever use bat files, because its only 2 lines to flash
yaro666 said:
you can fastboot and just push it in cmd if fastboot active. I bever use bat files, because its only 2 lines to flash
Click to expand...
Click to collapse
This is what happened:
I was watching my phone recognized as MTP USB Device and I tought yeah! my luck is from my side! now will be possible to flash my pohne in fastboot mode !!
I tried a lot of times with FLASH TOOL and it never passed from:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
then I tried in adb: "adb devices" but I never saw my device connected even with MTP USB Device driver activated in Device Manager.
so I tried anyway to use the flash_all.bat and same message received "getvar anti" bla bla..
I never deleted the lines about getvar from the file "flash_all.bat" because now my phone it is exactly as in the begin....
Now the PC doesn't want to recognize the phone... again the same ****.. " USB Device Unknown (Descriptor Request Failed) "
I did the test point and the same crap... the phone doesn't want to be recognized USB Unknown...
Come on... I can't believe it... I had decided to pay for the service flash with EDL authentication in the next week and now I can't even make it boot in EDL... exactly as in the begin I'm.... the phone it is with the same sympthoms.. :crying:
EDITED:
Now the Phone was recognized by the PC again as: MTP USB Device but with yellow sign..
I disconnected, reconnected the cable and nothing yellow sign.
I did the test point and boom Im back again into the same ****... USB UNknown (Descriptor Request Failed)
what the **** is happening?? Im not so sure how the phone can be recognized as MTP USB Device but i guess that it is fastboot mode. and that is what I want to try the solution from the first post of this threads.
or the second solution understand what I have to do to put the phone into EDL. Because I did a lot of times with sucess at the begin and now Im doing exactly the same and nothing. it doesnt want to work.
Looks like drivers problem?
romeosantos said:
This is what happened:
I was watching my phone recognized as MTP USB Device and I tought yeah! my luck is from my side! now will be possible to flash my pohne in fastboot mode !!
I tried a lot of times with FLASH TOOL and it never passed from:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
then I tried in adb: "adb devices" but I never saw my device connected even with MTP USB Device driver activated in Device Manager.
so I tried anyway to use the flash_all.bat and same message received "getvar anti" bla bla..
I never deleted the lines about getvar from the file "flash_all.bat" because now my phone it is exactly as in the begin....
Now the PC doesn't want to recognize the phone... again the same ****.. " USB Device Unknown (Descriptor Request Failed) "
I did the test point and the same crap... the phone doesn't want to be recognized USB Unknown...
Come on... I can't believe it... I had decided to pay for the service flash with EDL authentication in the next week and now I can't even make it boot in EDL... exactly as in the begin I'm.... the phone it is with the same sympthoms.. :crying:
EDITED:
Now the Phone was recognized by the PC again as: MTP USB Device but with yellow sign..
I disconnected, reconnected the cable and nothing yellow sign.
I did the test point and boom Im back again into the same ****... USB UNknown (Descriptor Request Failed)
what the **** is happening?? Im not so sure how the phone can be recognized as MTP USB Device but i guess that it is fastboot mode. and that is what I want to try the solution from the first post of this threads.
or the second solution understand what I have to do to put the phone into EDL. Because I did a lot of times with sucess at the begin and now Im doing exactly the same and nothing. it doesnt want to work.
Looks like drivers problem?
Click to expand...
Click to collapse
Most likely. I had similar issues with a rn7. Try it on another pc. I had issues getting the phone recognized in w10, then I switched to an old laptop I had with w7. Didn't install drivers, didn't do anything, windows installed it's driver and the phone was there. So it may be a issue with your OS. And again, delete the first two lines from the flash_all.bat to get over that error.
Edit: The flashing with MiFlash tool will only work if you see the fastboot logo on your phone. If the phone is seen in cmd after you type "fastboot devices".
attitude12 said:
Most likely. I had similar issues with a rn7. Try it on another pc. I had issues getting the phone recognized in w10, then I switched to an old laptop I had with w7. Didn't install drivers, didn't do anything, windows installed it's driver and the phone was there. So it may be a issue with your OS. And again, delete the first two lines from the flash_all.bat to get over that error.
Edit: The flashing with MiFlash tool will only work if you see the fastboot logo on your phone. If the phone is seen in cmd after you type "fastboot devices".
Click to expand...
Click to collapse
Thanks for the answer, I have the notebook with two windows.
W10 64 bits and W7 32 Bits.
Same problem in both, don't know how can be driver problem, because I installed exactly the correct versión. (I know that is the correct because I could do the test point correctly two days ago) and it was recognized as: "Qualcomm HS-USB QDloader 9008 (COM4)" But today it doesnt want to recognize anymore the phone. Only "USB Device Unknown (Descriptor Request Failed)"
So hard is to make it boot in EDL mode? i saw the picture for test point (k20 xiaomi) and it is really easy. but PC recognize the phone as Unkonwn after test point. The first day that I did the test point happened the same ****.. I was hours and hours trying to make it work.. till I installed the correct drivers. and now is happening the same.. hours and hours trying to boot in EDL and using the same drivers, same process, but nothing.
Except at 3:00 pm dont know how the phone was recognized as MTP USB Device (with yellow sign error in device manager) so i did again the test point and boom.. USB Unknown again...
If I press Power button + volume up the phone looks like turn off and instantly I do the connection from usb cable and nothing appears in device manager but 2 mins or 3 mins later the phone is recognized as unknown and blue led light start to blink every 1 second.
If i do the test point it is recognized instantly as Unknown but there isnt any blue led light blinking.
I tried test point without battery and same. problem.. I tried to do the test point without release the pins so fast.. and same problem I tried releasing fast.. slow... etc
I tried to removed the battery and press power button to drain all the energy from board.
I tried to charging battery with power supply and the blue led light is turned on after 2 mins and it continue on over 10 or 15 mins then it is off the blue light. I used a tester to see the voltage from battery and is ok looks like it is full of charge.
If I do the EDL Cable could it be different? or is the same as test point?
Thanks for your help guys you are good people!
Have you tried with Linux? With the distribution I mentioned?
Gimlouuuu said:
Have you tried with Linux? With the distribution I mentioned?
Click to expand...
Click to collapse
Hi! Thanks for your help.
The problem was the usb cable. Now works perfectly with a new cable. But now I have to unbrick it hahaha
romeosantos said:
Hi! Thanks for your help.
The problem was the usb cable. Now works perfectly with a new cable. But now I have to unbrick it hahaha
Click to expand...
Click to collapse
great, good news. To unlock it, go back at my first message.
Gimlouuuu said:
great, good news. To unlock it, go back at my first message.
Click to expand...
Click to collapse
Hi! Thanks! Yes I tried to flash in fastboot mode. I did adb devices command and it was recognized ok.
But when I tried to flash_all.bat it gave me error: "bootloader locked" looks like I need the bootloader unlocked to flash via ADB in fastboot mode.
what I want to try is like a bug in xiaomi mi flash tool. The first time that I tried to use it. I made a new account and I received a message like:
"Logged Suscessfull"
"Your Account was blind to this PC. Now you can start the process"
Then I received an error like "no root permission" or something like that (maybe was because the usb cable was bad)
Looks like the xiaomi flash tool passed the EDL Authentication. because now each time that Im trying to use MI TOOL this is the message that Im getting.
"Logged Sucessfull"
You are not authorized for this operation
romeosantos said:
Hi! Thanks! Yes I tried to flash in fastboot mode. I did adb devices command and it was recognized ok.
But when I tried to flash_all.bat it gave me error: "bootloader locked" looks like I need the bootloader unlocked to flash via ADB in fastboot mode.
what I want to try is like a bug in xiaomi mi flash tool. The first time that I tried to use it. I made a new account and I received a message like:
"Logged Suscessfull"
"Your Account was blind to this PC. Now you can start the process"
Then I received an error like "no root permission" or something like that (maybe was because the usb cable was bad)
Looks like the xiaomi flash tool passed the EDL Authentication. because now each time that Im trying to use MI TOOL this is the message that Im getting.
"Logged Sucessfull"
You are not authorized for this operation
Click to expand...
Click to collapse
Ok, suddenly you can not reinstall via all these methods because your bootloader is locked... Have you tried asking a member here if anyone has an EDL account (a real haha) ?