I and my dad own one plus one devices each. I had no problem unlocking the bootloader and rooting my device and my father's. Flashing a rom on my device usually takes a few seconds. So I tried to flash the latest paranoid android rom on my father's device but 7 mins passed there was no change in the logs of the TWRP (2.8.6.0) recovery and also it overheated A LOT . So i manually switched it off. ( battery percentage at that moment - 81%) , now since there was no os installed I put the device into bootloader mode and used wugfresh's bacon development toolkit to flash stock and unroot the device , my computer recognized the fastboot device and send the modem and a few other files before the oneplus one device completely shut down. The cmd prompt showed <waiting for device> and nothing was happening , so i removed the phone from the usb cable. Now the phone is not switching on at all :/ I'm neither able to boot into bootloader nor recovery mode. I tried putting it for charging for an hour but nothing showed on the display. I presume that at the moment since i interrupted the flash stock process, there is no software to govern the device and hence it cant recognize the pressing of buttons. I'm stuck and my father is furious :'( any help ?
Arunit Maity said:
I and my dad own one plus one devices each. I had no problem unlocking the bootloader and rooting my device and my father's. Flashing a rom on my device usually takes a few seconds. So I tried to flash the latest paranoid android rom on my father's device but 7 mins passed there was no change in the logs of the TWRP (2.8.6.0) recovery and also it overheated A LOT . So i manually switched it off. ( battery percentage at that moment - 81%) , now since there was no os installed I put the device into bootloader mode and used wugfresh's bacon development toolkit to flash stock and unroot the device , my computer recognized the fastboot device and send the modem and a few other files before the oneplus one device completely shut down. The cmd prompt showed and nothing was happening , so i removed the phone from the usb cable. Now the phone is not switching on at all :/ I'm neither able to boot into bootloader nor recovery mode. I tried putting it for charging for an hour but nothing showed on the display. I presume that at the moment since i interrupted the flash stock process, there is no software to govern the device and hence it cant recognize the pressing of buttons. I'm stuck and my father is furious :'( any help ?
Click to expand...
Click to collapse
Try if you can get into recovery/bootloader, quote this post.
If are not able to do so, your device is Hard Bricked, meaning, visit the service centre or contact OnePlus Customer Care. You can't fix this at home.
You asked the same question here already:
http://forum.xda-developers.com/showthread.php?t=2731638
I've answered you there.
Transmitted via Bacon
timmaaa said:
You asked the same question here already:
http://forum.xda-developers.com/showthread.php?t=2731638
I've answered you there.
Transmitted via Bacon
Click to expand...
Click to collapse
This.
Thread closed.
Related
Hey everyone. I couldn't find an answer to this that I could follow and that worked for me as I'm not very technically inclined.
My HTC One X recently died after having a low battery and now whenever I try to turn it on (even when it is fully charged), it gets to the lock screen, but I can only access everything for about 5 seconds before it restarts again. I know I have USB debugging enabled, and I can get to the screen that shows up when I hold down the power button and the volume-down button.
What I want to do, before doing a factory reset and praying that ends the bootloop, is recover my photos which I stupidly did not back up anywhere. I can connect my phone to my laptop, which runs on Windows 8, but it is not recognized as it normally would be (ie: I can't access files directly). I've gotten to the point where I can see "FASTBOOT USB" on my phone when it is connected and I've restarted my PC so that it is able to identify it in the Device Manager. I have also gone through the steps of downloading a universal naked driver and choosing the driver under the Device Manager, so when I use a command prompt my phone shows up in fastboot devices. (I used minimal fastboot and ADB)
But what can I do now? I have never tampered with my phone, so it is locked or unrooted. I'd like to keep it that way if possible, but I'm having a hard time understanding how I can retrieve my photos. Should I use ADB commands, and if so, how do I get to the point where my PC recognizes my phone under ADB devices? Or is there a better way? I'm also not very familiar with custom roms, TWRP, CWM, etc.
I'd appreciate a brief walk-through if possible as, like I said, I don't normally do this sort of thing. Thank you!
thepenrosesteps said:
Hey everyone. I couldn't find an answer to this that I could follow and that worked for me as I'm not very technically inclined.
My HTC One X recently died after having a low battery and now whenever I try to turn it on (even when it is fully charged), it gets to the lock screen, but I can only access everything for about 5 seconds before it restarts again. I know I have USB debugging enabled, and I can get to the screen that shows up when I hold down the power button and the volume-down button.
What I want to do, before doing a factory reset and praying that ends the bootloop, is recover my photos which I stupidly did not back up anywhere. I can connect my phone to my laptop, which runs on Windows 8, but it is not recognized as it normally would be (ie: I can't access files directly). I've gotten to the point where I can see "FASTBOOT USB" on my phone when it is connected and I've restarted my PC so that it is able to identify it in the Device Manager. I have also gone through the steps of downloading a universal naked driver and choosing the driver under the Device Manager, so when I use a command prompt my phone shows up in fastboot devices. (I used minimal fastboot and ADB)
But what can I do now? I have never tampered with my phone, so it is locked or unrooted. I'd like to keep it that way if possible, but I'm having a hard time understanding how I can retrieve my photos. Should I use ADB commands, and if so, how do I get to the point where my PC recognizes my phone under ADB devices? Or is there a better way? I'm also not very familiar with custom roms, TWRP, CWM, etc.
I'd appreciate a brief walk-through if possible as, like I said, I don't normally do this sort of thing. Thank you!
Click to expand...
Click to collapse
Try Power the Device Up in Safe Mode - HTC One®
Do you know the model number? Is it the AT&T or Rogers? s720e, G23, 720, 325...
sd_shadow said:
Try Power the Device Up in Safe Mode[/URL] - HTC One®
Do you know the model number? Is it the AT&T or Rogers? s720e, G23, 720, 325...
Click to expand...
Click to collapse
I tried going into safe mode and nothing changed! It didn't break the bootloop, so I guess it isn't an app that's causing the problem. It's with Rogers, but I don't know the model number... I got it in North America if that helps.
thepenrosesteps said:
I tried going into safe mode and nothing changed! It didn't break the bootloop, so I guess it isn't an app that's causing the problem. It's with Rogers, but I don't know the model number... I got it in North America if that helps.
Click to expand...
Click to collapse
It's likely a s720e then, but
I will request that this thread be moved to AT&T One X Q&A, Help & Troubleshooting
Where you should be able to find out for sure.
Next step is likely flashing a custom recovery like TWRP or CWM then you could, mount sd card/storage and copy photos.
see AT&T One X Q&A, Help & Troubleshooting Frequently Asked Questions by Heisenberg
[INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up (Updated 5/8/14) by redpoint73
Good day gents and ladies
Well let me start from the beginning.
I'm was using mi-globe 6.12.22
Last week Friday evening downloaded 7.2.9 mi-globe,read around the mi-globe forum.Didn't see anything funny so flashed via twrp on Saturday morning.Hmmmmmmmm this is when all my problems started.
Basically what I should of done is download 7.2.9,new 3.0.3 twrp for norgat,go into recovery flash new recovery, restart recovery,flash 7.2.9 and then have happy days.But it wasn't to be and now I'm basically sitting with a useless mi4c device.
The device works but warms up and I only get about 4 hours battery life.
If I try boot into recovery I just get black screen.
If I connect device to PC it is not recognized, have tried 3 x different laptop/PC's and different cables.
So fastboot,mi-flash,mi-unlock are all not possible as device is not recognized.
I have been trying different solutions without any success.
I think if it would be possible to root device directly without PC then maybe it will be possible to get flashfire working and I can flash new norgat recovery?
Any suggestions would be greatly appreciated?
NB.I have tried loading Qualcomm drivers ,google drivers etc etc.no luck can't connect my device too PC,either get device not recognized or the PC doesn't even see the device.Enable USB debugging etc etc nothing works.Been fiddling for 4 days!!!!!!!
Tried to root with kingoroot,framaroot directly on device etc nothing works?
Please help,else device is a nice piece of plastic that holds paper down on my table.lol
BR
Ant
have you tried fastboot
fastboot oem edl
Click to expand...
Click to collapse
then MiFlash to flash official rom
Fastboot don't work,as PC don't see the phone?
DeAntman said:
Fastboot don't work,as PC don't see the phone?
Click to expand...
Click to collapse
Is usb charging via pc working and have you tried miui updater? , This seems weird state you have ... If none working might be tried deep flash cable flashing ... Or go to nearest service center. Hope that help. Best luck.
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
DeAntman said:
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
Click to expand...
Click to collapse
You havent answered the miui updater part, have you tried flash miui rom.zip, using miui updater apps ?
Does fastboot mode boot on your phone ? i mean the bunny sceen showed up ?
For dfc here the link http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
Please take dfc as last resort. And do research more on this... Do with your own risk. Good luck
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
DeAntman said:
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
Click to expand...
Click to collapse
Before this has your pc able to use the miflash ? Try to follow this guide to setup it correctly http://en.miui.com/thread-136188-1-1.html ... I follow this guide and the adb n fastboot even works on an old pentium 4, 512mb ram, win xp laptop.
Ps: I think, its only a matter of incorrect driver setup on your side, best luck.
Hi guys,
I got a OPO borrowed from a friend because my OP3T is going to RMA.
When I first turned it on it had 1% battery. The phone wasn't used for a month. I proceded to recharge the battery. This took almost 18h. I saw the low battery error 3 or 4 times during attempts to power on the handset.
After full charge in installed the latest build of Lineage OS via TWRP. Unfortunately as I was having some WIFI connectivity issues I read that flashing the c7 modem firmware could solve the problem.
I was in TWRP flashing this same zip via sideload with an unbeknownst to me faulty cable. I grabbed the handset mid flash, and it fails with a connectivity error. I tried repeating the process with no luck, as I could not by any means regain adb connection to the handset. And then i decided to reboot and download the zip directly to the phone, without remembering this broken flash attempt could brick the phone. After rebooting I never saw again the One Plus logo neither felt the startup vibration. I tried power cycling with no success, and I cannot by any means detect the phone in windows device manager to attempt the usual unbrick procedures via COLOR or OnePlusRecoveryTool.
Windows doesn't even try to install drivers. It's as if the phone is completely shutdown forever.
What do you think. Did I really hard brick this phone? Is it a battery issue? Any ideas. I really liked to recover the phone to return it to my friend!
Thanks in advance for your help!
joao.m.neto said:
Hi guys,
I got a OPO borrowed from a friend because my OP3T is going to RMA.
When I first turned it on it had 1% battery. The phone wasn't used for a month. I proceded to recharge the battery. This took almost 18h. I saw the low battery error 3 or 4 times during attempts to power on the handset.
After full charge in installed the latest build of Lineage OS via TWRP. Unfortunately as I was having some WIFI connectivity issues I read that flashing the c7 modem firmware could solve the problem.
I was in TWRP flashing this same zip via sideload with an unbeknownst to me faulty cable. I grabbed the handset mid flash, and it fails with a connectivity error. I tried repeating the process with no luck, as I could not by any means regain adb connection to the handset. And then i decided to reboot and download the zip directly to the phone, without remembering this broken flash attempt could brick the phone. After rebooting I never saw again the One Plus logo neither felt the startup vibration. I tried power cycling with no success, and I cannot by any means detect the phone in windows device manager to attempt the usual unbrick procedures via COLOR or OnePlusRecoveryTool.
Windows doesn't even try to install drivers. It's as if the phone is completely shutdown forever.
What do you think. Did I really hard brick this phone? Is it a battery issue? Any ideas. I really liked to recover the phone to return it to my friend!
Thanks in advance for your help!
Click to expand...
Click to collapse
Could be a battery issue too since the device was unused for a month. Did you tried booting into fastboot mode or TWRP?
Which windows are you using?(I suggest you use winXp and win7) Did you tried the qualcomm 2012 drivers from the Color Os toolkit thread and the drivers given on Cm11s restore toolkit thread? -you should know that the fastboot(/adb) drivers will not work for qualcomm diagnostic port method(which the both toolkits are based on).
Mr.Ak said:
Could be a battery issue too since the device was unused for a month. Did you tried booting into fastboot mode or TWRP?
Which windows are you using?(I suggest you use winXp and win7) Did you tried the qualcomm 2012 drivers from the Color Os toolkit thread and the drivers given on Cm11s restore toolkit thread? -you should know that the fastboot(/adb) drivers will not work for qualcomm diagnostic port method(which the both toolkits are based on).
Click to expand...
Click to collapse
No success booting with volume up or down so no fastboot neither twrp. I'm using windows 10 (only one i have). I can't install the drivers because the device doesn't show up on device manager right?
I'll try finding a win XP although I'm sensing the habdset isn't powering at all...
Sent from my ONEPLUS A3003 using Tapatalk
joao.m.neto said:
No success booting with volume up or down so no fastboot neither twrp. I'm using windows 10 (only one i have). I can't install the drivers because the device doesn't show up on device manager right?
I'll try finding a win XP although I'm sensing the habdset isn't powering at all...
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Yes,as I said, could be a battery issue but we are still not sure yet.I can give you the link for winxp or win7 if you need and then you can dual-boot it alongside windows10.You should install drivers from cm11s restore toolkit thread(executable drivers),maybe then your device will show up in device manager though it is highly advised to do this on Xp or 7 since 8,8.1 and 10 has driver signing issues.
Hello everyone !
This morning, out of the blue (I think it was during a Whatsapp automatic backup), my Google Pixel 2 XL shut down. I can't get it started and the phone is stuck on the white screen with the Google Logo. I can access the bootloader and Recovery though, so that's something. I spent my whole day skimming through the forum and other websites/videos. but I only have a slight understanding of what is happening and I'm not sure where my problem lays. Now when I click on the Start option in the bootloader, it just starts back in the bootloader screen.
I've been a bad scholar and did not backup my data. So if there is a solution, I'd rather not factory reset my phone.
Got my phone a month ago.
I unlocked the bootloader and rooted the phone (Magisk).
Stock Rom
Today,
I tried to connect my phone to my computer but so far it is not recognised by my computer and I can't access OEM unlocking/usb modes.
I verified. I have the latest adb and fastboot version on my computer, dowloading the latest SDK platforms tools.
I downloaded the usb driver packages from the SDK manager.
I tried using an universal android adb driver tool.
I've used multiple usb-c to usb-c and usb-c to usb-a cables, on different ports.
I restarted my phone and computer multiple times (just to make sure)
My phone doesn't appear in the Device manager.
I am now completely lost and would really much appreciate your help.
Thank you for reading this. Thank you for helping me !
Sounds bad.....maybe in first instance try letting tge device shut off due to low battery. Maybe this helps to hard reset. So just leave it on in fastboot mode
donkeydances said:
Hello everyone !
This morning, out of the blue (I think it was during a Whatsapp automatic backup), my Google Pixel 2 XL shut down. I can't get it started and the phone is stuck on the white screen with the Google Logo. I can access the bootloader and Recovery though, so that's something. I spent my whole day skimming through the forum and other websites/videos. but I only have a slight understanding of what is happening and I'm not sure where my problem lays. Now when I click on the Start option in the bootloader, it just starts back in the bootloader screen.
I've been a bad scholar and did not backup my data. So if there is a solution, I'd rather not factory reset my phone.
Got my phone a month ago.
I unlocked the bootloader and rooted the phone (Magisk).
Stock Rom
Today,
I tried to connect my phone to my computer but so far it is not recognised by my computer and I can't access OEM unlocking/usb modes.
I verified. I have the latest adb and fastboot version on my computer, dowloading the latest SDK platforms tools.
I downloaded the usb driver packages from the SDK manager.
I tried using an universal android adb driver tool.
I've used multiple usb-c to usb-c and usb-c to usb-a cables, on different ports.
I restarted my phone and computer multiple times (just to make sure)
My phone doesn't appear in the Device manager.
I am now completely lost and would really much appreciate your help.
Thank you for reading this. Thank you for helping me !
Click to expand...
Click to collapse
Flash latest factory image (either 8.1 or DPx/P/9.0).
mrorange2108 said:
Sounds bad.....maybe in first instance try letting tge device shut off due to low battery. Maybe this helps to hard reset. So just leave it on in fastboot mode
Click to expand...
Click to collapse
I'm trying that. Thank you !
xFirefly93 said:
Flash latest factory image (either 8.1 or DPx/P/9.0).
Click to expand...
Click to collapse
Thank you for your answer. How would you do that ? I can't get it to be recognized by my computer.
donkeydances said:
Thank you for your answer. How would you do that ? I can't get it to be recognized by my computer.
Click to expand...
Click to collapse
Have you tried with the Fastboot protocol?
xFirefly93 said:
Have you tried with the Fastboot protocol?
Click to expand...
Click to collapse
Like I said, I can't get my phone to be recognized by my computer so no Fastboot protocol. I am not sure why it doesn't get recognized though.
Long story short converted my phone from TMO to global. Went to relock bootloader but didn't flash the global rom from Oxygen updater and had to MSM back to TMobile. I have all the latest drivers installed and all the latest tools. My pC detects my phone when its booted but when I go into Fastboot I can't send commands to it. ADB Devices runs and says the list but does not show the device number. Sending a command comes back as device not found. If I unplug the phone my pC makes the disconnect sound. There's no sign of my phone in device manager but when I go down to the tool bar I can find Android device attached via USB.
I spent 2 hours already trying to get this to work and I'm out of ideas. I've even googled it and tried everything there. My last thought is to MSM again in hopes that it resets something
Smallsmx3 said:
Long story short converted my phone from TMO to global. Went to relock bootloader but didn't flash the global rom from Oxygen updater and had to MSM back to TMobile. I have all the latest drivers installed and all the latest tools. My pC detects my phone when its booted but when I go into Fastboot I can't send commands to it. ADB Devices runs and says the list but does not show the device number. Sending a command comes back as device not found. If I unplug the phone my pC makes the disconnect sound. There's no sign of my phone in device manager but when I go down to the tool bar I can find Android device attached via USB.
I spent 2 hours already trying to get this to work and I'm out of ideas. I've even googled it and tried everything there. My last thought is to MSM again in hopes that it resets something
Click to expand...
Click to collapse
Update: Looks like I'm good to go. Phone is connected again. B Now when I try to unlock my bootloader I can't flash the unlock token I get an t error cannot load unlock_token.bin
Got it all figured out!
Smallsmx3 said:
Got it all figured out!
Click to expand...
Click to collapse
What did you do for PC to see phone in fastboot mode? I have the same thing where it cannot see in fastboot mode
Arr6 said:
What did you do for PC to see phone in fastboot mode? I have the same thing where it cannot see in fastboot mode
Click to expand...
Click to collapse
Honestly I was typing in adb devices instead of fastboot devices. So I think my computer was detecting it. I did reinstall drivers that I got from the OnePlus site. I made allot of dumb errors