Related
Hi,
I got one xiaomi redmi 1s rebooting, I hardest but not working
, so i decided to flash, via fastboot while flashing it stops in 14%.
now phone doesn't power on, while inserting usb, it detect as qualcomm usb in device manager comport.
Need help. how to revive.
riteshgpt60 said:
Hi,
I got one xiaomi redmi 1s rebooting, I hardest but not working
, so i decided to flash, via fastboot while flashing it stops in 14%.
now phone doesn't power on, while inserting usb, it detect as qualcomm usb in device manager comport.
Need help. how to revive.
Click to expand...
Click to collapse
Try Here
Read whole first, then give a try.
presetz said:
Try Here
Read whole first, then give a try.
Click to expand...
Click to collapse
Any one please share me tested solution with easy tutuorial.
riteshgpt60 said:
Any one please share me tested solution with easy tutuorial.
Click to expand...
Click to collapse
Have you read it? If its still not an easy way as it written, than might be someone can.
Sorry just tried to help.
Good luck sir.
presetz said:
Have you read it? If its still not an easy way as it written, than might be someone can.
Sorry just tried to help.
Good luck sir.
Click to expand...
Click to collapse
Hi, I finally flash with this file "armani_global_images_JHCMIBL50.0_4.3_in_111a6a27b4" and flashing process goes fine ,after flash it says to press f8 and I press OK buttom while holding f8 and PC restart, as software
Now phone shows little bip light in home button .
And now it doesn't shows qualcomm device as well, I think, boot is repair but fastboot mode not coming.
Need help.
riteshgpt60 said:
Hi, I finally flash with this file "armani_global_images_JHCMIBL50.0_4.3_in_111a6a27b4" and flashing process goes fine ,after flash it says to press f8 and I press OK buttom while holding f8 and PC restart, as software
Now phone shows little bip light in home button .
And now it doesn't shows qualcomm device as well, I think, boot is repair but fastboot mode not coming.
Need help.
Click to expand...
Click to collapse
Try previous version than 50, might be the 45 as it stable enough, i guess.
And before that, have you charged your phone? Mi recovery wont boot if under 20% battery.
presetz said:
Try previous version than 50, might be the 45 as it stable enough, i guess.
And before that, have you charged your phone? Mi recovery wont boot if under 20% battery.
Click to expand...
Click to collapse
Hi,
After flashing v50, the phone should be working, right?
Im downloading v45, but phone is not detecting with pc . no fastboot , no qualcomm usb , How can I flash now.
thank for guiding.
riteshgpt60 said:
Hi,
After flashing v50, the phone should be working, right?
Im downloading v45, but phone is not detecting with pc . no fastboot , no qualcomm usb , How can I flash now.
thank for guiding.
Click to expand...
Click to collapse
You said the led blinking a litte red light? Try to charged first till its more than 30% batt, and connect again. See if it show in pc
Thanks done after flashing v45
riteshgpt60 said:
Thanks done after flashing v45
Click to expand...
Click to collapse
Im glad to hear that, what an awesome experienced you got isnt it? At least you can learnt something from it
PROBLEM : Lenovo Zuk Z2 is stuck at EDL mode and cannot boot back into system.
DON'T PANIC...
A bit more about it
Zuk Z2 Plus is kind of bricked at Edl mode i.e it is at 9008 , aye.
A bit wierd issue but yes, it suddenly went to EDL and after a dozen tries like Vol & Power button holding and stuff i am not able to get out of edl mode.
There is no LED blinking, no vibration, display won't turn on, no nothing - just dead and is at EDL mode.
I've flashed 1.9 ROM & 2.0 ZUI ROM via QFIL ( as my Zuk is bricked or stuck at EDL mode i can easily flash ) but these don't boot too, or flashed ZUI via MI Flash Tool, but same.
It stays at EDL MODE.
Just for the record, I have bricked z2 a couple of times and after some hard work to get that to 9008 from 900e was able to unbrick it after I was able to get it to EDL mode and do deep flash ... but now in this case I am stuck at EDL. OMG
Device automatically switched to edl..
After searching on the internet!
After searching a lot, i found that same issue has happened in other devices also, possible fix is let the battery drain (will take a long time ) and after that plug in charger as it will turn off edl or disassemble it and disconnect battery ( harmful way)
How I fixed it? / SOLUTION
I let the battery drain to 0% and after that I plugged in the charger and pressed power button for 5 seconds and Viola it booted.
Now, the question is I was able to drain the battery just in a day, what I did is 2 things:
1. Used OTG cable and connected it to another device for 4-5 hours[ - to charge that another device in hope to drain my Z2 Plus's battery.
2. I used a thread or a rubber elastic band and tied that to the phone with a small paper roll pressing the power button and kept it like that for about 5 hours ( at this stage phone keeps on rebooting into edl so drains battery but you will not get to know it as no response will be shown by it - expect the sound it comes if you have it connected with the PC.)
------ Other Methods which seen to work ------
Or another method is Service Center, you can easily lock bootloader by flashing QPST STOCK ROM as you are at EDL - 9008 port.
Or removing the battery and connect it, it will switch off EDL - for this go to Local Shop I don't recommend doing this at home
THANKS - HOPE IT WILL HELP YOU
EDIT : FIXED!!
PS: Don't quote the Whole Post
Try a deep flash
May be it can help you
Mod Edit: attachment showing external link removed
JIT05 said:
May be it can help you
Click to expand...
Click to collapse
May i know which is this platform?
Telegram
SOLVED THE ISSUE - FINALLY and updated the thread with SOLUTION.
JIT05 said:
May be it can help you
Click to expand...
Click to collapse
I fixed it, if you see I only posted that xD
Not_James_Bond said:
May i know which is this platform?
Click to expand...
Click to collapse
That is Telegram, one of the chat app for interacting with communities....
For example like this :
Mod Edit: External link removed
Mod Edit: Attachment with link to external group removed
Anybody who has similar issue, regardless of device would be benefited. [emoji111]️ Good Job
Sent from my Z2 Plus using Tapatalk
heerakjyotidas94 said:
Anybody who has similar issue, regardless of device would be benefited. [emoji111]️ Good Job
Sent from my Z2 Plus using Tapatalk
Click to expand...
Click to collapse
Yeah.
JIT05 said:
Telegram
Click to expand...
Click to collapse
kubersharma said:
SOLVED THE ISSUE - FINALLY and updated the thread with SOLUTION.
I fixed it, if you see I only posted that xD
That is Telegram, one of the chat app for interacting with communities....
For example like this :
Mod Edit: removed external link
Click to expand...
Click to collapse
Thank You.
Just Sharing Only Group For Discussion , Not Sharing Anything Related To Piracy [emoji4]
Mod Edit: external link removed
Thread closed, Xda being used to drive traffic to off-site group not permitted.
So recently my phone decided to **** itself after installing paranoidandroid for the OP3. I rebooted it one day and it never came back on. I plugged it into my pc to see that QUALCOM 9008 device and ended up running the unbrick process to try to fix the phone. Eventually the phone came back to life, but when I turn off the phone it always goes back into that qualcom recovery mode or whatever and doesn't start. I have to hard power off every time after shutting down and reboot does not work at all.
Any ideas?
Try to find the newer unbrick guides. There is one for OOS 5.0. I couldn't get phone to boot without using one of them. I would find them again and link them to you but I'm on my phone not my PC ATM.
forthecake said:
So recently my phone decided to **** itself after installing paranoidandroid for the OP3. I rebooted it one day and it never came back on. I plugged it into my pc to see that QUALCOM 9008 device and ended up running the unbrick process to try to fix the phone. Eventually the phone came back to life, but when I turn off the phone it always goes back into that qualcom recovery mode or whatever and doesn't start. I have to hard power off every time after shutting down and reboot does not work at all.
Any ideas?
Click to expand...
Click to collapse
If you quote me or mention me I'll be able to share a link that brings you straight into Oreo later this day.
Puddi_Puddin said:
If you quote me or mention me I'll be able to share a link that brings you straight into Oreo later this day.
Click to expand...
Click to collapse
Hi, I'm interested. Can you share the link ?
Bryandu13 said:
Hi, I'm interested. Can you share the link ?
Click to expand...
Click to collapse
https://s3.amazonaws.com/oneplussupport/Op3/OnePlus3_16_A.60_171116.rar
Puddi_Puddin said:
https://s3.amazonaws.com/oneplussupport/Op3/OnePlus3_16_A.60_171116.rar
Click to expand...
Click to collapse
Oh It's just a link to Oreo firmware, thank but I thought it was a link to an unbrick guide with Oreo.
Bryandu13 said:
Oh It's just a link to Oreo firmware, thank but I thought it was a link to an unbrick guide with Oreo.
Click to expand...
Click to collapse
Open it... Msmdownload should be inside.
Puddi_Puddin said:
https://s3.amazonaws.com/oneplussupport/Op3/OnePlus3_16_A.60_171116.rar
Click to expand...
Click to collapse
Can you reupload that? I actually need the unbrick guide now lol
First things first, NEVER RESTORE A TWRP BACKUP YOU CREATED IN ONE VERSION IN ANOTHER VERSION.
Now coming to my situation, I installed the Deodexed Stable Zui Oreo ROM but as usual got bored with the zui and wanted to go back to my fav Pixel experience Rom so I clean flashed it from the unofficial hendibudi recovery but I couldn't use my internal storage and I once earlier read in another thread that installing 3.0.3 decrypts it so I installed that recovery and clean flashed AEX5.2 Rom this time and same internal storage problem continued so my lazy ass thought I'll restore the TWRP backup I created when I unlocked the bootloader instead of flashing through qfil and that was my mistake.
I created the backup on 3.1.0 but now I was on 3.0.3 so as soon as I restored the backup and rebooted, my phone didn't turn on, no zuk logo or led or anything, if I long press the power button it just vibrates and the led flashes for a sec, that's all.
Edit: feels like this thread belongs to the News/Discussions section than here but meh
Edit2: Solution in Post #4
It seems like qfil, mi flash method is last as your bootloader is also corrupted, and this happens because there are many critical hidden partition on our device so it mess up, when you install first twrp releases, you will notice there are 7 8 partition and in latest one they all are hidden.
narshi shukla said:
It seems like qfil, mi flash method is last as your bootloader is also corrupted, and this happens because there are many critical hidden partition on our device so it mess up, when you install first twrp releases, you will notice there are 7 8 partition and in latest one they all are hidden.
Click to expand...
Click to collapse
well if it's that easy I wouldn't be worried at all but unfortunately my situation is a bit different, I can't flash anything as my phone is recognized as 900E, to flash anything the phone should be recognized in 9008(edl) mode and for that I have to strip the cable and short circuit with it and all that, which is really a hit or miss kinda situation so kinda worried!
But seems like I have no other choice so let's see what happens, I tried stripping the stock usb cable and it got split into half lmao
now I'll buy another cable and will try the copper wire method instead of splitting it
Edit: yeah ik that different versions of TWRP are different but I wanted to restore only the data partition and my data was already encrypted so I thought I have nothing to lose, I was like if it doesn't work I'll flash the full firmware again but didn't expect it to fully brick the phone
Okay the primary reason for me creating this thread was to let y'all know how I bricked my device so that y'all won't repeat my mistake but I saw some people here and there recently asking how to resurrect their device so thought I'll share how I got mine working wishing it'll help such people.
My phone was completely dead, the hardware buttons weren't doing anything, the phone doesn't power off but all I could see was a black screen, so I had to follow THIS GUIDE.
But the above situation is a rarity, I guess most of you ppl could get to the zuk logo or your led keeps flashing and you can use your hardware buttons, in such situations, follow THIS GUIDE.
The above links are for you to get your phone to 9008 mode to be able to flash the stock firmware, but if you don't know how to flash,
refer THIS GUIDE.
Flashing problem
i got phone into 9008 port following ur guide and installed qfil everything went good problem is after hitting download buton in qfil after some time it says error "sahara failed".
seetharam55555 said:
i got phone into 9008 port following ur guide and installed qfil everything went good problem is after hitting download buton in qfil after some time it says error "sahara failed".
Click to expand...
Click to collapse
Only one solution is there.. after u get sahara error.. disconnect your phone and cable, then again turn your phone on. And then turn it off... After that press volume up+ power button simultaneously while connecting to the usb port, if you are successful, within 2-3 seconds you have to press the download button on QFIL.. then it should work... You can try 2-3 times... For demo, but thia is the only way out of this hard brick
.. i suffered in the sahara error for 3 days since i flashed OOS on my z2 , till today i finally got the solution
sidS6 said:
Only one solution is there.. after u get sahara error.. disconnect your phone and cable, then again turn your phone on. And then turn it off... After that press volume up+ power button simultaneously while connecting to the usb port, if you are successful, within 2-3 seconds you have to press the download button on QFIL.. then it should work... You can try 2-3 times... For demo, but thia is the only way out of this hard brick
.. i suffered in the sahara error for 3 days since i flashed OOS on my z2 , till today i finally got the solution
Click to expand...
Click to collapse
thanks for response.What do u mean by "succesfull".and other thing to turn off the phone it takes me nearly 2 min constant pressing of power button, is this normal.
seetharam55555 said:
thanks for response.What do u mean by "succesfull".and other thing to turn off the phone it takes me nearly 2 min constant pressing of power button, is this normal.
Click to expand...
Click to collapse
Not 2 minutes but i think 30 seconds at max.. and by successful i mean that you get into Qualcomm 9008 qdloader mode in qfil
---------- Post added at 05:13 PM ---------- Previous post was at 05:11 PM ----------
The main thing is you have to immediately press the download button(within 2-3 seconds) after reconnecting into 9008 mode
Briked my phone flasing oos, solved it in the first go usimg qpst method.
Rahil4321 said:
Briked my phone flasing oos, solved it in the first go usimg qpst method.
Click to expand...
Click to collapse
You didn't got Sahara error?
seetharam55555 said:
thanks for response.What do u mean by "succesfull".and other thing to turn off the phone it takes me nearly 2 min constant pressing of power button, is this normal.
Click to expand...
Click to collapse
Were u able to unbrick?
Thanks
sidS6 said:
Were u able to unbrick?
Click to expand...
Click to collapse
yes it worked but as u said we have to hit download button within 2 sec....thank you very much u nearly saved 1000 rupees for me.
seetharam55555 said:
yes it worked but as u said we have to hit download button within 2 sec....thank you very much u nearly saved 1000 rupees for me.
Click to expand...
Click to collapse
Congrats bro! But i lost my 3 cables in ths process.. that equals 700 rs.. but i learned a great lesson? no probs
seetharam55555 said:
i got phone into 9008 port following ur guide and installed qfil everything went good problem is after hitting download buton in qfil after some time it says error "sahara failed".
Click to expand...
Click to collapse
dude just cut the cable and make intersection betwwen vlack and gree wire and put the cable into phone , got edl mode simple ways
sidS6 said:
Congrats bro! But i lost my 3 cables in ths process.. that equals 700 rs.. but i learned a great lesson? no probs
Click to expand...
Click to collapse
Why did you wasted 3 cables for?
seetharam55555 said:
Why did you wasted 3 cables for?
Click to expand...
Click to collapse
Coz while spliiting, one got split into half ? and the other one got bent so it was unusable.. i had buy the third one
sidS6 said:
Coz while spliiting, one got split into half ? and the other one got bent so it was unusable.. i had buy the third one
Click to expand...
Click to collapse
Ohh you tried that method i did like this
sidS6 said:
You didn't got Sahara error?
Click to expand...
Click to collapse
You don't need to flash via qpst when you see logo but device wont boot it mean you locked your bootloader so all you need to do is unlock it again that's all
Nirmal0001 said:
You don't need to flash via qpst when you see logo but device wont boot it mean you locked your bootloader so all you need to do is unlock it again that's all
Click to expand...
Click to collapse
Unfortunately learnt this after unbricking my device
I had installed RR mix rom in my Zuk Z2 plus. while trying to enter fastboot mode, it went off. Now it is completely dead. not being recoganized in my PC.In device manager it is not shown. Tried to deep flash through Qfil, but didn't recoganize port.If i plug in charger also no LED indication, If I disconnect battery & plug in for charging, white LED slowly blinks, in the same mode if I connect charger blinking white LED continues. But once I remove charge & reconnect it shows nothing. again if I remove battery & reconnect, again white LED starts blinking. Apart from this nothing is shown, phone completely dead. Can anybody help please. I tried through Qfil, tried by shorting black & green cable, all types of key combinations.
Hi Guys,
Yesterday during an official update of my oneplus 5t (using the update manager from the phone itself), the phone got bricked and i dont know why....
So after some research i found it is hard bricked ( basically i cant do nothing, power on i cant, power +volume UP/DOWN too, and even when i plug the charge cable i have neither vibrations nor LED on)
So i follow this tutorial to unbrick the phone:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
I could get the phone recognize by the PC by pressing UP to see the phone as QUSB-BULK and then QUALCOMM QD LOADER after driver's update.
But when i run MSMDownloadTool ( V4.0.27 dumpling 43_0.36_180613) as administrator and click on start, the process get stuck in "waiting for device"
the status of connection before click on start was "connected" and after click and some process it turn to N/A
the status of communication is "memory size....."
status of last communication is "waiting for device"
I have tried several time and always the same result..... stuck in the waiting device
does someone have an idea on how to solve this? because i really need to unbrick the phone....
thank you in advance
EDIT:
I tried another version of MsmDownloadTool (dumpling_43_O.06_171206) and this time, the downloading of cache image failed....
I dont know what to do
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
DaRk-L0rD said:
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
Click to expand...
Click to collapse
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
rokusho32 said:
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
Click to expand...
Click to collapse
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
DaRk-L0rD said:
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
Click to expand...
Click to collapse
I have installed the ADB drivers
which version of MSMDownloadTool should i use?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
rcbjr2 said:
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
Click to expand...
Click to collapse
I have same situation.. did you resolve this problem?
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
I contacted OnePlus and I sent them the phone and they reinstalled the operating system. I was never able to fix it myself. I even had an online session with OnePlus and they couldn't get the MSM software to recognize the phone (even though it was truly connected to my laptop). I also had an issue with my OnePlus 8T that got messed up doing something with Magisk, and OnePlus reinstalled the operating system as well. I still can't boot from the A partition though; just the B partition.
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
At first, I chose WWAN-DHCP - which caused problem with connection
piechu11 said:
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
View attachment 5511425
At first, I chose WWAN-DHCP - which caused problem with connection
Click to expand...
Click to collapse
Thank you this solved my problem exactly.
i was restoring my metro by tmobile oneplus nord n10 BE2025 model with build tag BE88CF