Related
EDIT FOR THOSE WHO MAY HAVE THIS ISSUE:
If you have accidentally entered sideload mode from CWM, there are 2 ways to get out of it.
1) - the fastest way - flash a rom from it (.zip format eg KA04 xperia revolution etc)
2) - the easiest (but potentially very slow if you have a full battery) - let your battery run empty, the phone will power down when it goes flat. Put it on charge and leave it for a while (it will take a while to get enough charge to be able to boot again so be patient)
If you are going to flash a rom you will need to do some house keeping. I was having big issues with sideload mode as my computer wasn't recognizing the phone properly, and sideload commands were not working. The phone was essentially not responding to any ADB commands or the sideload flash command.
This all turned out to be from left over drivers from my galaxy s 2. For what ever reason, rooting, installing custom recovery, adb, bootloader unlocking and flashtool all work flawlessly with my driver set up, but sideload mode did not like it at all.
I over came the issue by using a computer which had a fresh installation of windows 7, which therefore had no previous drivers for any devices besides that of the PC itself. It worked first time and was very easy.
The steps for flashing a .zip in sideload mode:
- Ideally have a .zip of the ROM you were on. If you are on a stock rom, try to find a rom based on the same version of your stock from and it should be fine. You probably won't need to wipe data/factory reset (I haven't had to wipe going from AUS stock 350 - NL 434 - KA04 xperia revlolution)
- Have drivers configured perfectly
- Have ADB working
- Put the rom .zip in your ADB directory (It would be a good idea to name it update.zip or rom.zip for ease of use.)
- Open file explorer and go to your ADB directory, hold down shift, right-click and select open command window here
enter "adb devices"
- Your device should be listed. If all the drivers are set up properly, is should also list as being in sideload mode
- Type "adb sideload <filename of update.zip>" without quotation marks or < >
- Let it finish. When it's done your device should now be working fine or at least out of sideload mode
- Wipe cache and dalvik cache if you feel it's necessary
I am not sure how this will work for locked bootloaders as mine is unlocked therefore cannot comment on the experience. I suspect that if you flash xperia revolution, it should work as it is compatible with locked bootloaders. It should fail and abort the installation near the end though. This is normal, just wipe cache and dalvik cache and it should work.
In the worst case scenario, you should now be able to access flash-mode to flash a stock rom with flashtool. You shouldn't need to do this though.
Original post:
So I intelligently selected install zip from sideload instead of sd card. Now I am stuck in side load mode, and no amount of button combinations for any period of time are working to hard reset the device. And since the Z has no removable battery I cant just pull that out to shut it off. It doesn't seem to like taking any commands from adb, does anyone have any advice?
DreadPirateDan said:
So I intelligently selected install zip from sideload instead of sd card. Now I am stuck in side load mode, and no amount of button combinations for any period of time are working to hard reset the device. And since the Z has no removable battery I cant just pull that out to shut it off. It doesn't seem to like taking any commands from adb, does anyone have any advice?
Click to expand...
Click to collapse
You can try SEUS:
http://www.sonymobile.com/global-en/tools/update-service/
not sure if it will help but it couldn't hurt to try it out. If all goes well seus will reinstall your device back to original
Odp: Stuck in sideload
adb reboot recovery
check that command
Sent from my GT-S6500D using xda premium
FlooDnl said:
You can try SEUS:
http://www.sonymobile.com/global-en/tools/update-service/
not sure if it will help but it couldn't hurt to try it out. If all goes well seus will reinstall your device back to original
Click to expand...
Click to collapse
I'll give it a crack
UPDATE: It's not letting me go past the connect stage unfortunately
yeah the adb commands are throwing up the error :
"error: closed"
ie;
adb reboot
error: closed
adb usb
error: closed
adb sideload xx.zip
gives me the whole help message.
adb get-state
unknown
very frustrating.
Odp: Stuck in sideload
put power of 8 sec.
Sent from my GT-S6500D using xda premium
Holding the power button for over 30 seconds didn't turn it of, nor did power + vol up, power + vol down, power + vol up & vol down, or vol up + vol down. This sucks lol. Really don't want to have to resort to just leaving it till the battery dies
DreadPirateDan said:
Holding the power button for over 30 seconds didn't turn it of, nor did power + vol up, power + vol down, power + vol up & vol down, or vol up + vol down. This sucks lol. Really don't want to have to resort to just leaving it till the battery dies
Click to expand...
Click to collapse
This worried me a little with purchasing this phone with non removable battery. Tried the hard reset mentioned in the manual to be more relaxed, but was sure that a lock could occur that nothing would work except battery run down, seen it on other devices previously. Now it seems confirmed
danw_oz said:
This worried me a little with purchasing this phone with non removable battery. Tried the hard reset mentioned in the manual to be more relaxed, but was sure that a lock could occur that nothing would work except battery run down, seen it on other devices previously. Now it seems confirmed
Click to expand...
Click to collapse
It's certainly looking that way, I just pull out my gf's old vista laptop (considered it may be a windows 7 or 64bit issue) but it's the exact same story there. I'm currently booting up my old/her new laptop which just recently got a fresh win7 install. Nothing at all adroid related has ever been on it since then so if it doesn't work still on that I can essentially rule out that it's a driver or os issue
UPDATE: Ok looks like the old/new/fresh laptop is doing the trick! When I type adb devices, this time it is listing the z as being sideload, instead of host (what it said on the other 2 laptops). So allthough reboot commands still come back as error, I was able to start sideloading cm10.1 zip.
AH just checked on it and it's done! I am out of the terrible menu. Now to try rebooting system.. hopefully I haven't made things worse .
CM logo is swirling away.. good start.
And now it's booted to CM . Thank god that is over!
Hopefully if anyone else falls into a similar trap this thread might help them. There must have been some sort of conflicting drivers messing with my adb set-up. Funny that I was able to root and unlock the bootloader completely hassle free in the same setup though
So to anyone having similar issues and doesn't have the option to pull out the battery - try a fresh pc that hasn't had any android devices installed to it.
And a big thanks to those that tried to help me up to this point much appreciated. :victory:
DreadPirateDan said:
It's certainly looking that way, I just pull out my gf's old vista laptop (considered it may be a windows 7 or 64bit issue) but it's the exact same story there. I'm currently booting up my old/her new laptop which just recently got a fresh win7 install. Nothing at all adroid related has ever been on it since then so if it doesn't work still on that I can essentially rule out that it's a driver or os issue
UPDATE: Ok looks like the old/new/fresh laptop is doing the trick! When I type adb devices, this time it is listing the z as being sideload, instead of host (what it said on the other 2 laptops). So allthough reboot commands still come back as error, I was able to start sideloading cm10.1 zip.
AH just checked on it and it's done! I am out of the terrible menu. Now to try rebooting system.. hopefully I haven't made things worse .
CM logo is swirling away.. good start.
And now it's booted to CM . Thank god that is over!
Hopefully if anyone else falls into a similar trap this thread might help them. There must have been some sort of conflicting drivers messing with my adb set-up. Funny that I was able to root and unlock the bootloader completely hassle free in the same setup though
So to anyone having similar issues and doesn't have the option to pull out the battery - try a fresh pc that hasn't had any android devices installed to it.
And a big thanks to those that tried to help me up to this point much appreciated. :victory:
Click to expand...
Click to collapse
I really didn't get it could you please help me more ! I have the same problem but I have no idea how to fix this I made a big mistake
Tell me if I'm wrong, but...
Dumiftw said:
I really didn't get it could you please help me more ! I have the same problem but I have no idea how to fix this I made a big mistake
Click to expand...
Click to collapse
I believe DreadPirateDan was saying:
Have a computer with adb installed. It has had an Android device connect to it before. It wouldn't recognise the device.
Have a second computer with adb installed. It has had an Android device connect to it before. It wouldn't recognise the device.
Have a third without adb installed.
Installed adb.
Attached device, which invoked device driver installation.
Started using adb and it was recognised, allowing reinitialisation of the device.
Maybe?
If you don't have that many computers, try a fresh virtual machine (VirtualBox and Ubuntu don't cost money if you don't have the licenses for VMware and Windows).
Yes what Johbremat said is correct. My bad I haven't checked xda for a few days otherwise I would have posted sooner! I hope you managed to solve your problem :fingers-crossed:
I edited the first post so if anyone else runs into this there is hopefully more clear instructions on how to get out of it. Let me know if there is anything I said incorrectly (I was going from memory pretty much), or if you don't understand something I have said and I will offer my assistance when I can and/or edit the post.
Hi, I just had this problem while putting Cyanogenmod on my Nexus10. I don't know if it will work on the Xperia but even when adb sideload update.zip was getting error: closed I was still able to do adb reboot recovery to get out of it. Also my error: closed problems went away when I used CWM to format my sdcard (kind of extreme, I know).
My Xiaomi mi5 does not turn on.
No lights, fastboot is not accessible, resetting it does not do anything.
Basically for any combination of buttons that I press, nothing happens and the screen stays black - it is completely dead.
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fastboot in order to flash the ROM, but is there a way to get to fastboot using my pc? Or even turn the phone on with commands? At the moment ADB and Fastboot does not recognise my phone, is there a way to make it detect it from the state it is in?
Thanks
sivd said:
My Xiaomi mi5 does not turn on.
No lights, fastboot is not accessible, resetting it does not do anything.
Basically for any combination of buttons that I press, nothing happens and the screen stays black - it is completely dead.
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fastboot in order to flash the ROM, but is there a way to get to fastboot using my pc? Or even turn the phone on with commands? At the moment ADB and Fastboot does not recognise my phone, is there a way to make it detect it from the state it is in?
Thanks
Click to expand...
Click to collapse
Do you have all the necessary driver installed? I think yes and that is why you are seeing in (COM3) port. You can do one thing, Unplug the phone from PC and Press and Hold Vol Down (-) and plug in again. If not works then you can also Press and HOLD Vol Down and Press and HOLD Power button until you see Fast boot menu. If don't work then try the same thing with Vol UP button. Then you suppose to see a MI phone logo with a USB cable.
"qualcomm hs-usb qdloader 9008" Is a signal of Hard Brick for QCOM devices (Like for LG G2);
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
As you can see here, for fix it you need all partition files, all system files, and a programm
But i dont know if it will works also on SD820, you might need all files for Mi5
Just a question: How did you bricked your phone?
EDIT:
I had an idea: maybe inside fastboot rom you can find all files you need, it might be worth a try, at least you can send it to your shop where you bought it
sivd said:
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fas,tboot in order to flash the ROM
Click to expand...
Click to collapse
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here: https://www.androidfilehost.com/?fid=24521665358595574
3: download the latest dev rom from here: http://update.miui.com/updates/v1/fullromdownload.php?d=gemini&b=X&r=cn&n=
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
adwinp said:
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here: https://www.androidfilehost.com/?fid=24521665358595574
3: download the latest dev rom from here: http://update.miui.com/updates/v1/fullromdownload.php?d=gemini&b=X&r=cn&n=
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
Click to expand...
Click to collapse
I also had the same issue with black screen and no responses from vol. & power buttons. But when I notice that in device manger it showed the qcom driver, then I new that there was hope to recover the phone. I can confirm that this will unbrick your phone. I MiFlash'd the China Rom (non-dev), unlocked the bootloader, MiFlash'd MiFlash_xiaomi.eu_gemini_V7.2.13.0.MAACNDB_6.0 rom, sideload lastest stable EU rom, TRWP and SuperSU.
adwinp said:
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here:
3: download the latest dev rom from here:
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
Click to expand...
Click to collapse
Thank you so much, this has worked perfectly and saved me a lot of money! I really appreciate your help, thank you again!
sivd said:
Thank you so much, this has worked perfectly and saved me a lot of money! I really appreciate your help, thank you again!
Click to expand...
Click to collapse
Glad you could salvage your device.
Now remember - from great flashing power comes great responsibility ;]
adwinp said:
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here: https://www.androidfilehost.com/?fid=24521665358595574
3: download the latest dev rom from here: http://update.miui.com/updates/v1/fullromdownload.php?d=gemini&b=X&r=cn&n=
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
Click to expand...
Click to collapse
Thanks for the guide, 1 q tho: what to do when i get the "missed hello packets, try to recover" message?, wait or restart the process?
Ok, solved by disabling driver sign (press F8 during boot)
Hello , i got the same problem as described at this topic and here is my problems :
I can't turn on my phone and i can't put it in fastboot mode ( tryed a lot of buttons combinations)
But when i plug it into my pc - it recognizes as Android
I have tryed to install drivers but windows shows mistake and can't install that
When my device connected to pc and i press volume + and power buttons - in few minutes system(WIN 10) recognizes it as ADB interface(can't install drivers too) and i have acess to mi5 internal storage ( i can download photos and so on )
But mi flash doesn't see phone in any mode and i feel that my device is still alive and i can recover it but don't know how....
I will be grateful for any help !
Isteran said:
Hello , i got the same problem as described at this topic and here is my problems :
I can't turn on my phone and i can't put it in fastboot mode ( tryed a lot of buttons combinations)
But when i plug it into my pc - it recognizes as Android
I have tryed to install drivers but windows shows mistake and can't install that
When my device connected to pc and i press volume + and power buttons - in few minutes system(WIN 10) recognizes it as ADB interface(can't install drivers too) and i have acess to mi5 internal storage ( i can download photos and so on )
But mi flash doesn't see phone in any mode and i feel that my device is still alive and i can recover it but don't know how....
I will be grateful for any help !
Click to expand...
Click to collapse
If you can see it in adb, you might be able to see it in fastboot.
Try go in to fastboot (even though you can't see it on screen.)
And try fastboot oem device-info see if you can get anything. Then we go from there.
DrBubblewrap said:
If you can see it in adb, you might be able to see it in fastboot.
Try go in to fastboot (even though you can't see it on screen.)
And try fastboot oem device-info see if you can get anything. Then we go from there.
Click to expand...
Click to collapse
tryed a lot of time to go to fastboot , but nothing happened...
same issue
I've been having the same problem with my MI5, 128gb running MIUI8 6.6.23CN, unlocked bootloader
It started when I did an OTA from 6.6.16, then OTA failed, I tried again this time it downloaded full rom and went into my twrp but installation started automatically. Then it rebooted but the system stayed in black screen. I forced-rebooted it, then everything was fine and I was on 6.6.23. I was using the phone normally for a few hours, then around 6hr later after I upgraded, I took phone out of my bag and it was bricked. I tried everything, no fastboot, no adb, no recovery, no led, nothing on screen. MiFlash reconizes (cuz of the 9008 status) but flash fails. I event opened it up, disconnected the 3 cables from the battery and hold onto power buttons for few seconds to try to drain whatever power it has left in system. Reconnected battery but no change.
I gave up, put phone back in case and was going to ask friend to take it back to send to china for repair the next day, but then I too it out an hour before I go meet my friend and suddenly, phone led flashed red and I see on screen out-of-battery icon. I plugged it in to charge then LED flickered quickly in red for a bit then turn solid red, then turned orange. I let it charged for 10min or so, and pressed power+Vol_Down for few seconds. Lo and behold, I got the bunny on screen and went into fastboot. I was able to re-flash 6.6.23 and phone was good to go again. (but why did removing battery cables do the same thing? Maybe I didn’t leave it disconnected long enough?)
Good story until this part… then 2 days later, I wanted to test MI Talk with friend, I click on it, and phone froze. Both touch sensor light stayed on. I waited about 15 second and forced reboot. Phone vibrates once and then went into hard brick again. Exactly same situation, nothing works.
Now I am waitng for phone to discharge by itself. God knows how many days it will take. It was 96% charged. (1st time I had about 45% and too a day to discharge)
Only if I can get back into fastboot......
tkrave said:
I've been having the same problem with my MI5, 128gb running MIUI8 6.6.23CN, unlocked bootloader
It started when I did an OTA from 6.6.16, then OTA failed, I tried again this time it downloaded full rom and went into my twrp but installation started automatically. Then it rebooted but the system stayed in black screen. I forced-rebooted it, then everything was fine and I was on 6.6.23. I was using the phone normally for a few hours, then around 6hr later after I upgraded, I took phone out of my bag and it was bricked. I tried everything, no fastboot, no adb, no recovery, no led, nothing on screen. MiFlash reconizes (cuz of the 9008 status) but flash fails. I event opened it up, disconnected the 3 cables from the battery and hold onto power buttons for few seconds to try to drain whatever power it has left in system. Reconnected battery but no change.
I gave up, put phone back in case and was going to ask friend to take it back to send to china for repair the next day, but then I too it out an hour before I go meet my friend and suddenly, phone led flashed red and I see on screen out-of-battery icon. I plugged it in to charge then LED flickered quickly in red for a bit then turn solid red, then turned orange. I let it charged for 10min or so, and pressed power+Vol_Down for few seconds. Lo and behold, I got the bunny on screen and went into fastboot. I was able to re-flash 6.6.23 and phone was good to go again. (but why did removing battery cables do the same thing? Maybe I didn’t leave it disconnected long enough?)
Good story until this part… then 2 days later, I wanted to test MI Talk with friend, I click on it, and phone froze. Both touch sensor light stayed on. I waited about 15 second and forced reboot. Phone vibrates once and then went into hard brick again. Exactly same situation, nothing works.
Now I am waitng for phone to discharge by itself. God knows how many days it will take. It was 96% charged. (1st time I had about 45% and too a day to discharge)
Only if I can get back into fastboot......
Click to expand...
Click to collapse
You don't have to go into fastboot to use miflash if you have stock recovery
Sent from my MI 5 using Tapatalk
vf1 said:
You don't have to go into fastboot to use miflash if you have stock recovery
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
how do you flash stock recovery if you dont need to go into fastboot? now I am unable to go into recovery or fastboot as the phone does not boot at all. connecting it to PC reconizes the phone as the infamous "Qualcomm HS-USB QDLoader 9008" device.
Its been 4 days and the damn battery hasnt run out yet as I can still plug into pc and get qualcom 9008 to come up. I think I am going to send to china to get it fixed properly if I still cannot get the red flicker of low battery power to come up by tomorrow.
It has happened to me 3-4 times already. It didnt want to boot. No signs of life either. I even sent a message to the shop for sending it back..the only thing that was telling me it wasn't completely dead, was the qualcomm driver ,while on USB connection with the PC, which you are referring to as well
Here is what you could try doing. Try pressing the power button for about 30 seconds at first. If it does not boot, try bending the phone real gently back and forth (don't break it!!). Preferably, hit it gently with your palm while holding it in your other hand.( -- I know it might sound weird --) I noticed that it's shutting down while i have it in my pocket and doing some work which squeezes the phone a bit against my leg.
I came to the conclusion that some connection must become loose when some pressure is being applied to it.. Unfortunately it has to be a design flaw of the phone. Nothing random with yours or mine , in my opinion. // I have a case and tempered glass installed as well since the first minute I got it in my hands..
Sent from my MI 5 using XDA-Developers mobile app
Thanks for the tips Takkaros. I tried what you said but nothing changed (though I was a bit scared to bend it too hard). 1st time it happened to me, I had around 40-50% battery and somehow battery completely drained 24hr later so I got the red blinking low of battery light and was able to charge the phone up and go back into fastboot, which solved everything. this time it happened when I had 96% battery(which I knew cuz I was using the phone, then clicked MI Talk and phone froze, then bricked). I wish there is a way for me to force a battery drain without opening it up. I did opened it up once(on the 1st brick) and disconnected the 3 battery cables, but it was still in brick state when I put everything back.
The qualcomm 9008 driver detection was also my concern about sending back the phone. Chances are by the time my phone reaches the repair shop, battery is completely dead and they simply charge the battery then flash a stable rom and send it back to me without changing out the motherboard or whatever. Which in such case it will be faster for me to just wait a week or two and do myself, instead of shipping it to china and wasting shipping cost and probably will take 4-6 weeks.
I am not sure whats wrong with this phone. Sometimes it turns off while i have in on charge at night, with the Green led lighting. I can get into recovery mode but all the partitions are missing. I cant wipe anything and all my files are not there. If I restart the recovery 2-3 times everything comes back to normal. Maybe there is something wrong with the flash drive. If honorbuy replied to my messages i'd sent it back to them asap. This is not a reliable phone for daily use
Sent from my MI 5 using XDA-Developers mobile app
Try using mi flash. Follow the instruction
Sent from my MI 5 using Tapatalk
I am sending back the phone to china to have them "fix" it. Not sure what they will do, hopefully they either swap me a new phone or swap out the motherboard or something. I just hope they dont just boot into fastboot (after battery completely drained and system resets) and flash new rom and send it back to me.
Probably will take a month or so. Good thing i still have my old phone.
tkrave said:
I am sending back the phone to china to have them "fix" it. Not sure what they will do, hopefully they either swap me a new phone or swap out the motherboard or something. I just hope they dont just boot into fastboot (after battery completely drained and system resets) and flash new rom and send it back to me.
Probably will take a month or so. Good thing i still have my old phone.
Click to expand...
Click to collapse
This happened to me recently. I used mi flash and the global 7.2.4 stable fastboot rom to get it going again. Wouldn't work for me with with with newer versions. Think edl has been disabled on them.
Hey, Ive tried to install xiaomi.eu rom but didnt realize that i needed the chinese rom and that the global didnt work for this, after ive installed using TWRP the rom, ive rebooted and it just went black, not recovery, not fastboot.
BT was unlocked.
I also see my phone as qualcomm...qloader 9008 when connecting to my pc
Any help?
after having a few heartattacks, ive installed a good Miflsah and a good fastboot rom, and managed to restore my phone to its former glory
no need for further help, but i have a few advices
dont be stupid like me, and listen to directions like theyre the word of god, when they say change from chinese rom to a non official rom, YOU NEED CHINESE, global wont work
and if you're having problems with miflash giving errors, try a bunch of downloads, old, new, everything.
Hi, yet another brick here!
I had an AOSP ROM but I had problems with it. I entered TWRP, downloaded a MIUI official ROM for recovery, wiped the phone from TWRP and decrypting it (there was an option for that). Then I did try to flash the ROM and... black screen. No signs of life.
However, when I connect it to the computer it detects it as the famous Qualcom xxx 9008 (COM10) device. But fastboot is not working, when I type "fastboot devices" it doesn't return anything. ADB doesn't recognize the phone either. Everywhere I saw that I should use MiFlash to recover it, but I took a look at the scripts and are using fastboot to perform the process. But since fastboot doesn't recognize the device, it won't work. I get stuck all the time at "Failed to receive the hello packet".
Fastboot doesn't detect my phone either on Linux or Windows. I tried Linux, virtual Windows 10 (x64) and at last I'm trying on a Windows 10 (x64) computer (no virtualization). No matter what I do, it always stays at the same point. I also used several MiFlash versions (from old builds from last year to the most up-to-date version of XiaomiMiFlash). But since fastboot is not detecting the phone I think there's no point in switching MiFlash versions.
So... what can I do? Should I use the pin short-circuit /deepflash cable method? As of I understand, that is what you use to get into EDL, but if my device is showing 9008 in device manager doesn't it mean that I'm already in EDL? I'm not really sure because all the threads I saw in several forums are a bit messy.
I'll appreciate any help. I don't have phone since 3 days ago and I can survive without it but I need it for my work.
Thank you in advance!
EDIT:
Forgot to say, if I try to power off and power on it doesn't do anything BUT when I plug and unplug from the charger it does show a battery icon with the charged percentage. That's the only sign of life from the phone, aside from being recognized as a 9008 device, but that actually happens when I try to (blindly) get in fastboot mode.
FIXED!!! After four hours testing out several options I found the solution: Open up the phone, unplug the battery cable, plug it again, and voilà. The phone automatically got recognized (again) as Qualcomm 9008 device but this time the flash went on flawlessly. It took less than 5 minutes, once succeeded I powered on the device and it ran into MIUI 8 in less than 5 minutes.
So, if you find issues with the command "fastboot devices", unplug the battery and try it again before troubling yourself with deepcables or shortcircuits ;-D
NOTE: Taking out the back cover is very easy, search on youtube, I bought the thing you need for 1$ at the store next to my home (sorry I don't know what it's called).
Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
If you can flash/boot into TWRP, then probably nothing is lost. While in TWRP, if you connect your phone with PC, what happens? Do you hear the usual USB connection sound? If yes, what appears in the device manager?
Even if it doesn't appear in device manager, don't worry.
Boot into TWRP, go to storage, DISABLE MTP and enable it again. I know it sounds dumb, but just try it. It will be recognized as long as you have the proper drivers installed.
After that copy the zip of an OxygenOS based ROM like FreedomOS and flash it. Don't wipe anything. It will boot fine. I've done that a few times, never had a problem.
Thanks for the advice guys - no, no sound, nothing - as I said, I only get the charging (+) icon in twpr next to the battery percentage.
I did disable and enable MTP before - although not plugged in a pc during the process - will try if I have the chance.
One more thing that might ring a bell for someone - I tried the key combo for hard reset today(power + vol down) for a couple second and moments later I got a fuzzy (random colored pixels) screen and a red led. Weird, if you ask me.
P.S.: Today I tried to chat with OP a bit - 230 Eur for a new MB (64GB) and 255 Eur for my 128GB version - I just wanted to know, I'm still not admitting failure though. But as a student, these numbers from the support literally hurt me when reading...
grello said:
Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
Click to expand...
Click to collapse
1) try to update the twrp to the official 3.1.1.0. Then flash the latest modem firmware for your device and try to flash a custom rom like lineage os (a 7.x rom)
If you connect the phone to PC in TWRP and your phone is not recognized, chances are good that either your phone's USB or the cable (or the USB port on the computer) is not working. You can try to download the adb driver installer from here, just to check if your phone is listed by the installer: http://adbdriver.com/downloads/
Update - tried the MTP Enable/disable option in TWRP (in the Mount menu) while plugged into the PC, with no luck
IvanPrince - have you actually read the description of my problem? I have the 3.1.1-0 and even if not, how should I actually flash another version of twrp? The problem here is I cannot seem to find a WAY how to flash ANYTHING on the device.
I'll see about the adb drivers and update.
Thanks all,
Does the phone show up as anything on the PC when you boot to fastboot? I re-read but didn't see anything about it.
Nope - nothing. By now, I believe it is a hardware problem as the phone indeed got wet before my mistake with the advanced wipe. It appears to work just fine though, apart from the connectivity issue, so I believe the MB should be ok as everything else, including the screen is.
I just have one, perhaps a little courageous thing I'd like to ask from someone kind enough. Anyone with a Oneplus 3 or 3T who's not afraid to open the phone for a couplne minutes and has a multimeter alongside with a USB cable should be able to help me. :angel:
Could you, my awesome stranger, check where the 4 USB pins (on the side where you plug them into the PC) lead (make contact/'BEEP' on the multimeter) with the actual phone motherboard? It would REALLY help me in troubleshooting and perhaps saving 250 Eur. So far, I have this: (same color means contact) at that point. See picture.
BLACK - GND (all the heatsinks are connected to GROUND as well)
GREEN - DATA +
YELLOW - DATA -
RED - VCC
If anyone decides to open up their phone and help out a fellow xda guy, it will be greatly appriciated. :angel:
Hey Bro I was curious to know if you tried this method of recovering from a hard brick... When I first got my 3t something similar happened to me. I can't remember all the details of my hard brick but I thought I was f***ed. Please try this if you have not already.
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Might be a dumb question, but you did remember to mount the USB when you connected the otg right?
If the bootloader is unlocked, you can save it.
I would flash the stock recovery and the latest factory image (4.1.7)
Download them both from here:
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
After flashing the stock recovery using fastboot, boot to stock recovery and sideload through ADB the stock factory image.
Reboot and after checking that everything is working fine, feel free to relock the bootloader if you wish to stay 100% stock.
If the computer doesn't recognize it at all then it's a driver problem, not the phone... at least that's what I think.
try to use the program to fix my oneplus 3t it said download complete. try to restart
try to use the program to fix my oneplus 3t it said download complete. try to restart it and can press the screen and it keep rebooting it like the screen is frozen
please help me out
I have a OnePlus 8 Pro running Oxygen OS 11.0.4.4.IN11AA. Upon installing Magisk, I can no longer turn Wifi on. I have tried restarting, clearing the cache from recovery, resetting network settings, basically all the things the "wifi wont turn on help pls" guides say to do. Mobile data and bluetooth work absolutely fine, so what's going on?
Sound is also non-functional. Even after plugging in earphones (which worked with this phone previously) nothing comes out, and the phone doesn't even seem to recognize them. I also noticed that after a reboot the volume controls are set back to the defaults.
Additionally, the system is very slow to start up and the screen stays black until after the unlock prompt (which displays over the black screen) and then the wallpaper and everything else loads. (after which the device is responsive as normal)
These problems occurred even without installing any modules or otherwise modifying the device. I'm using the latest version of Magisk, 22.0 (22000).
I originally tried to make a GitHub issue, but it was closed by the bot since I didn't follow the template GitHub never showed me. Also, us non-canary users experience issues too. [mini-rant over]
Sorry if this is a duplicate, the search system appears to be malfunctioning since the updates.
The Fix!
Looks like I'm solving all my problems today. I had a hunch that the culprit was the boot.img which I downloaded--it was corrupt. So I went to OnePlus' site and downloaded the OTA package, extracted the boot.img from that, and flashed it through fastboot. When I rebooted, I was greeted with the beautiful almost old-IOS charging sound, and Wifi!! That boot was quite speedy too!
Hi could you explain how did you reboot your phone i have totally same problem...i tried msm download tool but i cant get my device to show there....could you please tell me how did you put OTA package into phone ? thx
FIXED!
in the end I was able to use MSM Download tool....i just had to manually download Qualcomm drivers so that my phone can be recognized. After that MSM worked and rebooted my phone totally clean. Gosh not gonna root for a while now XD
PS: More fun is that my Windows PC wasn't connected to internet so i had to download everything on my macbook and through USB stick I was bringing all app to Windows.....longest 6 hours of my life
Jaywinik said:
Hi could you explain how did you reboot your phone i have totally same problem...i tried msm download tool but i cant get my device to show there....could you please tell me how did you put OTA package into phone ? thx
Click to expand...
Click to collapse
From fastboot, use the volume keys to select Power Off and then press the power button once. Make sure the phone is unplugged while doing this. Then, with the MSM tool ready on your computer, hold down both buttons on your phone and plug in the cable from the phone to the computer. It should automatically boot into EDL mode, and MSM should say Connected.
My
Jaywinik said:
Hi could you explain how did you reboot your phone i have totally same problem...i tried msm download tool but i cant get my device to show there....could you please tell me how did you put OTA package into phone ? thx
FIXED!
in the end I was able to use MSM Download tool....i just had to manually download Qualcomm drivers so that my phone can be recognized. After that MSM worked and rebooted my phone totally clean. Gosh not gonna root for a while now XD
PS: More fun is that my Windows PC wasn't connected to internet so i had to download everything on my macbook and through USB stick I was bringing all app to Windows.....longest 6 hours of my life
Click to expand...
Click to collapse
When I had to do this I didn't connect the device to the network since I don't trust Windows 10 not to open a billion ports up and use my infrastructure for Microsoft's business. Copying to and from a crappy 2.0 drive sucks!