i was trying to flash android L through root toolkit ( wug fresh )
but i got an errors saying max download limit ????? bytes
then i just unplugged the phone from the computer and like an idiot
and now it wont come on
when i plug it in charge it doesnt show anything aswell
Please Help how can fix ? I Bought this with my own pocket money brand new from play store for £300
:crying: :crying: :crying:
you know that the "max download size" thing is just a WARNING message, in fact a lot of phones displays it for all operations(being all operations all fastboot flash operations), on the n5 it only shows when installing recovery (afaik).
anyway, see if it really wont come on, my phone was like that, but in fact it was in qualcomm´s QD-LOADER 9008 (i had to install some drivers for it to show up on pc). if your phone does get detected(even if as an unknown device)then you have some hope, if not - too bad you are mostly screwed.
Check your device manager
opssemnik said:
in fact a lot of phones displays it for all operations(being all operations all fastboot flash operations), on the n5 it only shows when installing recovery (afaik).
Click to expand...
Click to collapse
It showed for every fastboot flash I did just a few days ago. I don't recall that warning showing up back when I flashed 4.4.4 and prior. I think it's a change with the new bootloader.
Have you tried to use Google recovery that flashes stock ROM on your device ?
I had made a very bad thing with my N5, which resulted in a bootloop, two hours after receiving the N5 and I was almost crying. Download a stock recovery from android dev site. A Nexus is unbrekable
shiva-x said:
Have you tried to use Google recovery that flashes stock ROM on your device ?
I had made a very bad thing with my N5, which resulted in a bootloop, two hours after receiving the N5 and I was almost crying. Download a stock recovery from android dev site. A Nexus is unbrekable
Click to expand...
Click to collapse
Wrong...
Google- said:
i was trying to flash android L through root toolkit ( wug fresh )
but i got an errors saying max download limit ????? bytes
then i just unplugged the phone from the computer and like an idiot
and now it wont come on
when i plug it in charge it doesnt show anything aswell
Please Help how can fix ? I Bought this with my own pocket money brand new from play store for £300
:crying: :crying: :crying:
Click to expand...
Click to collapse
Tried a forced reboot? (Power + volume down button for bout 15 seconds).
Seems like the go-to solution but I see no one asked you yet.
Do this while connected to a charger.
Also try booting into the secondary bootloader by pressing volume up , down and power simultaneous.
Noob + Toolkit = Leathal combo
Try to learn fastboot and adb so you have control over whats happening and don`t use toolkits.
gee2012 said:
Noob + Toolkit = Leathal combo
Try to learn fastboot and adb so you have control over whats happening and don`t use toolkits.
Click to expand...
Click to collapse
Agree , but it should still be salvageable - assuming the incomplete firmware didn't cause hardware damage.
Is there any solution found? I ran into the same situation. I installed CM 11S and that prompted me an error which was unable to read the binary input file. I then reinstalled the firmware and did a reboot Now, it's hard bricked. Won't boot at all.
How do I power my N5 back?
nirmal212 said:
Is there any solution found? I ran into the same situation. I installed CM 11S and that prompted me an error which was unable to read the binary input file. I then reinstalled the firmware and did a reboot Now, it's hard bricked. Won't boot at all.
How do I power my N5 back?
Click to expand...
Click to collapse
any new device showing up in the device manager when you connect your phone to your pc?
bitdomo said:
any new device showing up in the device manager when you connect your phone to your pc?
Click to expand...
Click to collapse
It's showing up as "QHSUSB_BULK". Then I tried to install the qualcomm driver. Now nothing is showing up.
nirmal212 said:
It's showing up as "QHSUSB_BULK". Then I tried to install the qualcomm driver. Now nothing is showing up.
Click to expand...
Click to collapse
press and hold volume_down+volume_up+power keys until you see it again. It should take 20-25 seconds. Try to fix the drivers (turning off dirver signature enforcement helps a lot) to show Qualcomm HSUSB QDLoader 9008 device then follow my guide here
bitdomo said:
press and hold volume_down+volume_up+power keys until you see it again. It should take 20-25 seconds. Try to fix the drivers (turning off dirver signature enforcement helps a lot) to show Qualcomm HSUSB QDLoader 9008 device then follow my guide here
Click to expand...
Click to collapse
Can I perform this action even if my device is not started? I tried all the button options and still the device won't power on.
Related
Hello All,
Mine one friend is trying to flash custom rom in his AT&T One X and he hard bricked it, the phone is not responding on any key combination and also not booting directly in recovery. He was using TWRP Recovery and trying to flash this rom
http://onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2/
Can anyone body help me in this regard or tell me any method which will work ?
Any help in this regard would highly appreciated.
Thanks in Advance.
Imk
imk79 said:
Hello All,
Mine one friend is trying to flash custom rom in his AT&T One X and he hard bricked it, the phone is not responding on any key combination and also not booting directly in recovery. He was using TWRP Recovery and trying to flash this rom
http://onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2/
Can anyone body help me in this regard or tell me any method which will work ?
Any help in this regard would highly appreciated.
Thanks in Advance.
Imk
Click to expand...
Click to collapse
When you plug it into your USB cable do you have the charging light?
Also that rom is for the Tegra One X not the Dual Core Adreno One X, i've done this before and if im still right you can get into download mode you can go back to stock.
MrKickstand said:
When you plug it into your USB cable do you have the charging light?
Click to expand...
Click to collapse
No nothing is happen. Phone is giving no response
imk79 said:
No nothing is happen. Phone is giving no response
Click to expand...
Click to collapse
Hmm... Ok, on your computer go into Device Manager and plug in your phone to the PC and tell me what kind of sound it makes when it connects and if the device shows a triangle with a "!" in it on the device manager.
MrKickstand said:
Hmm... Ok, on your computer go into Device Manager and plug in your phone to the PC and tell me what kind of sound it makes when it connects and if the device shows a triangle with a "!" in it on the device manager.
Click to expand...
Click to collapse
When I connect the device nothing happened and device showed like in the attached screenshot.
imk79 said:
When I connect the device nothing happened and device showed like in the attached screenshot.
Click to expand...
Click to collapse
Ok, im pretty sure you can recover from that, especially since when i bricked mine it made an abnormal sound when i connected the usb and not the normal boobooop. Try ADB rebooting into bootloader mode or plug it into the USB Cable and Hold the Power + UP + DOWN at the same time and it should still push you into recovery mode. Also download the stock RUU, some of them have a bat you can run and itll do most of the work all you need to do is get into bootloader mode.
MrKickstand said:
Ok, im pretty sure you can recover from that, especially since when i bricked mine it made an abnormal sound when i connected the usb and not the normal boobooop. Try ADB rebooting into download mode or plug it into the USB Cable and Hold the Power + UP + DOWN at the same time and it should still push you into recovery mode. Also download the stock RUU, some of them have a bat you can run and itll do most of the work all you need to do is get into download mode.
Click to expand...
Click to collapse
Can you pls guide me about ADB Rebooting how can I perform it also I did Volume Down+ Power and Volume Down + Up + power button but nothing happen
imk79 said:
Can you pls guide me about ADB Rebooting how can I perform it also I did Volume Down+ Power and Volume Down + Up + power button but nothing happen
Click to expand...
Click to collapse
I didnt mean download mode since im still thinking about the S3, but i mean bootloader. But first off i assume you already have ADB and the Android SDK. So go into your android folder -> platform tools -> hold shift and right click in while your in platform tools and click Open Command Window here and once the window is open type in ADB Reboot Bootloader and see what it does. (i assume that while flashing a rom you had debugging enabled." BUT, also go here and download a RUU http://forum.xda-developers.com/showthread.php?t=2119610 , (id use AT&T USA and the 1.85.502.3 RUU, just click right under OTA and to the right you'll see "DOWNLOAD" and run that EXE to see if it works)
MrKickstand said:
I didnt mean download mode since im still thinking about the S3, but i mean bootloader. But first off i assume you already have ADB and the Android SDK. So go into your android folder -> platform tools -> hold shift and right click in while your in platform tools and click Open Command Window here and once the window is open type in ADB Reboot Bootloader and see what it does. (i assume that while flashing a rom you had debugging enabled." BUT, also go here and download a RUU http://forum.xda-developers.com/showthread.php?t=2119610 , (id use AT&T USA and the 1.85.502.3 RUU, just click right under OTA and to the right you'll see "DOWNLOAD" and run that EXE to see if it works)
Click to expand...
Click to collapse
Can you pls give me a link how to install ADB I remember once I have installed for my LG G2x but not sure is still exsist or not ? Can you pls tell me where is this Android Folder in my system ?
imk79 said:
Can you pls give me a link how to install ADB I remember once I have installed for my LG G2x but not sure is still exsist or not ? Can you pls tell me where is this Android Folder in my system ?
Click to expand...
Click to collapse
Here ya go.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
MrKickstand said:
Ok, im pretty sure you can recover from that,
Click to expand...
Click to collapse
You would be incorrect. QHSUSB_DLOAD mode after flashing IceColdJelly meant fo the ENDEAVORU is a death sentence. The device is in fact hard bricked, meaning the only fix is sending the phone for JTAG. The exception, is if the phone was originally on hboot 1.09 (somewhat unlikely at this point, unless the phone was pretty old).
http://forum.xda-developers.com/showthread.php?t=1974101
Couple mistakes were made here that led to this fatal condition:
1) Can't say this enough: DO NOT install mods from random websites. As clearly demonstrated here, these other random websites don't clearly delineate between the EVITA and ENDEAVORU, and this can brick your phone. Stick to the proper device forum on XDA.
2) Why did the person try to install a version of ICJ from 8 months ago? Unless you are doing it for a specific reason, installing obsolete firmware is kinda asking for problems, as well.
redpoint73 said:
You would be incorrect. QHSUSB_DLOAD mode after flashing IceColdJelly meant fo the ENDEAVORU is a death sentence. The device is in fact hard bricked, meaning the only fix is sending the phone for JTAG. The exception, is if the phone was originally on hboot 1.09 (somewhat unlikely at this point, unless the phone was pretty old).
http://forum.xda-developers.com/showthread.php?t=1974101
Couple mistakes were made here that led to this fatal condition:
1) Can't say this enough: DO NOT install mods from random websites. As clearly demonstrated here, these other random websites don't clearly delineate between the EVITA and ENDEAVORU, and this can brick your phone. Stick to the proper device forum on XDA.
2) Why did the person try to install a version of ICJ from 8 months ago? Unless you are doing it for a specific reason, installing obsolete firmware is kinda asking for problems, as well.
Click to expand...
Click to collapse
Thanks for the info
Any other solution rather then Jtag ?
imk79 said:
Any other solution rather then Jtag ?
Click to expand...
Click to collapse
If you originally rooted (or later RUUed) to 2.20 firmware or later, than no. If you were on 1.85 or 1.73 firmware, you can try the unbricking thread and/or JET tool. Unbricking thread is linked in the ICJ "warning" thread I posted above. JET tool can be found in the Development forum.
I decided to write a guide on how to recover from a bricked OnePlus One. This is my first guide.
About me: I am a newbie on Android.However, the XDA community has taught me a lot about my Android phone for the first month of using it. That's right! I have only been using Android for less than one month so take this guide with a grain of salt. But if you happen to soft brick your One, this is the guide to turn to. I have created two mind-bending/heartbreaking/frightening scenarios that I have experienced. Though, resolved thanks to this community.
Note: This will wipe your phone!
Scenario 1:
Soft bricked, (CM gear keeps spinning but won't boot to lock screen)
Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
How to find out if you have unlocked bootloader:
1. Locate the folder where you installed the OPO Toolbox.
2. Hold Shift and right click on ANY white area within the folder.
3. Left click 'Open command window here'
4. Type:
fastboot oem device-info
If it returns True on tampered. Then you have unlocked your bootloader.
I hope this guide helps solve your soft-bricked problem. Good luck!
I suggest that a mod moves this to the General section
pandasa123 said:
I suggest that a mod moves this to the General section
Click to expand...
Click to collapse
Report the thread if you think its necessary.
Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:
Digital Arm said:
Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:
Click to expand...
Click to collapse
You don't have an unlocked bootloader.
Transmitted via Bacon
timmaaa said:
You don't have an unlocked bootloader.
Transmitted via Bacon
Click to expand...
Click to collapse
Thx got it:cyclops:
Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
Hi i am stuck in scenario 2...I did all a u said but i cant flash CM XNPH22R ...where do i find this file...i cant find it on my phone either ..pls help ??
Thank god for this thread omg, saved my life
Locked Bootloader
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??
RiccoSuave said:
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??
Click to expand...
Click to collapse
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.
Champi12301 said:
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.
Click to expand...
Click to collapse
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.
RiccoSuave said:
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.
Click to expand...
Click to collapse
Then first you need to unlock the bootloader via fastboot,but that action erases all data. I assume,if you modified the boot via fastboot, USB DEBUGGING is working,so after try to do the softbrick tutorial of the thread.
Tecleado desde mi 1+1.
how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!
deanwinchester370 said:
how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!
Click to expand...
Click to collapse
Did you find a solution ?
I'm facing the exact same issue on my OPO.
>> bootloader locked
>> no recovery
>> impossible to unlock the bootloader
>> OPO stuck at 1+ logo and keep rebooting agin and again and again...
....i think my OPO is dead T_T
Is it a way to force the bootloader unlock ?
Please HELP !!!
Didn't work for me
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.
All done
davmeva said:
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.
Click to expand...
Click to collapse
No one replied to this but never mind, took me two days but I now have a working phone. So you can call in the dogs, cheers
hi davmeva
did you fixed your oneplus one till now or not because i have also same situation here and no success till now .
i did by mistake all this stuff and now nothing work still same condition
if you got any solution please share it
Restored my Honor back to stock rom from CM11 and now can't boot the phone into fastboot/rescue mode, anyone got any ideas?
BUMP
Solved my issue by myself.
Switch phone off and hold the volume down button as you plug the phone into the PC.
As you solved yourself you could let us know how you did.
theoneofgod said:
Switch phone off and hold the volume down button as you plug the phone into the PC.
As you solved yourself you could let us know how you did.
Click to expand...
Click to collapse
I'm aware of the correct way of doing but it wouldn't work. As there was zero replies in x number of views I took it that nobody knew the answer or was at least interested in the issue.
In the end I used the adb command to reboot the phone into fastboot and so forth.
And till then it's working fine again ?
You can get into fastboot as you want in the classic way ?
CSeb95 said:
And till then it's working fine again ?
You can get into fastboot as you want in the classic way ?
Click to expand...
Click to collapse
Now I'm getting replies .... I haven't tested it since I used adb.
Hey,
is there somebody else with the above problem? Because i have the same since i got my phone. I didnt tought this will be a big probem. But since i updated my honor 6 and something went wrong my phone is completely bricked, because it is in a bootloop and i can not enter bootloader nor fastboot mode or recovery. I am afraid that huawei says its my fault and denies warranty, so i am really intrested if there are more then two people out there with the same problem.
Thanks a lot
sideshowbob
sideshowbob84 said:
Hey,
is there somebody else with the above problem? Because i have the same since i got my phone. I didnt tought this will be a big probem. But since i updated my honor 6 and something went wrong my phone is completely bricked, because it is in a bootloop and i can not enter bootloader nor fastboot mode or recovery. I am afraid that huawei says its my fault and denies warranty, so i am really intrested if there are more then two people out there with the same problem.
Thanks a lot
sideshowbob
Click to expand...
Click to collapse
dude evem i am also facing the same problem , phone reboots continuously till honor logo ....what to do.how to flash it.
iitsanup said:
dude evem i am also facing the same problem , phone reboots continuously till honor logo ....what to do.how to flash it.
Click to expand...
Click to collapse
Same Problem man pls .....hlp......
Download Honor 6 Multi-tool and do the "Unbrick" trick through the fastboot menu. To enter fastboot first install Huawei USB drivers on PC and hold volume down when your phone is bootlooping with the USB cable connected to PC. Or use adb.exe from android sdk and type "adb reboot fastboot" when the screen shows "Honor" logo. Repeat the action by "copying\pasting" the command very fast until adb sends your commmand to the phone.
Hello all,
My oneplus one (64gb black) wont start anymore.
How did this happen?
Well,
yesterday after some trouble on my oneplus i tried an factory reset but my TWRP got stuck,
so i started the phone which was still fully working and wiped this: dalvik cache, system, data and cache
But because of that i didn't had a OS anymore ( i didn't know this was going to happen)
So i tried to install CM11 through fastboot commands but every time i got CRC errors in CMD.
So i tried it again and suddenly my phone wouldn't turn on anymore.
I charged it then for 12 hours but still didn't work.
Fastboot wont work, recovery won't work, it doesn't charge ( or atleast i cannot see it on the screen and on the led)
I tried to powercycle it but that doesn't work either.
Can anyone help me please?
Thanks!
BTW: Sorry for the bad english.
Maybe it could help to press the power-button for a long time. That's not a joke Try holding it for a least 10 seconds.
TriKE27 said:
Maybe it could help to press the power-button for a long time. That's not a joke Try holding it for a least 10 seconds.
Click to expand...
Click to collapse
Thanks for the answer but that doens't work either.
And what did you think that will happend when you wiped "system" partition?
I also bricked oneplus when I tried to revert to stock CM11 by flashing one-by-one cm11 partitions, but I found thread about unbricking phone using ColourOS firmware.
Look at this thread: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
rtomakov said:
And what did you think that will happend when you wiped "system" partition?
I also bricked oneplus when I tried to revert to stock CM11 by flashing one-by-one cm11 partitions, but I found thread about unbricking phone using ColourOS firmware.
Look at this thread: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Thanks for the answer and yes i know but i was not thinking about it when i did that.
But i did what you said but the tutorial says this:
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software.
But the problem is that my pc doesn't recognize anything so i cannot see it in device manager.
Thanks
bboy521 said:
Thanks for the answer and yes i know but i was not thinking about it when i did that.
But i did what you said but the tutorial says this:
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software.
But the problem is that my pc doesn't recognize anything so i cannot see it in device manager.
Thanks
Click to expand...
Click to collapse
Can you see your phone in modems or ports section of device manager?
rtomakov said:
Can you see your phone in modems or ports section of device manager?
Click to expand...
Click to collapse
Thanks for the answer!
My phone is working again! Jeejj
The problem was the unknown device at device manager, so what i did was disconnecting my phone from pc and then press the power button for 1 min, connect it back and then the device manager recognized it!
I'm now flashing it back to exodus rom!
Thanks all!!
I have this situation before, wiping everything dalvik/cache/system/data and internal storage. So my phone has nothing, just few empty file. Now how do I solve it ?
Simply I boot into TWRP. Luckily the driver detect my phone after I connect to pc so I open internal storage, copy the rom and gapps and put em on TWRP folder. Then just go to install on TWRP and look for the folder and voila, flash and phone back to healthy state.
Never ever ever delete that internal storage again lol.
Indeed man
But with me TWRP wasn't available either so yea...
It wont happen again haha
But thanks bro!
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
try charging the phone for a few hours
se7enlyn said:
try charging the phone for a few hours
Click to expand...
Click to collapse
yeah, forgot to mention that. can't even charge it. when I plug it in it does the same. tries to turn on. shows the first splash screen and reboots doing the same again and again. doesnt even show the charging screen with chinese text and battery animation.
sounds like u need a new battery
ireaper4592 said:
sounds like u need a new battery
Click to expand...
Click to collapse
already tried that too. had a replacement battery laying around. changed it and still no luck.
@bmark240
help please
se7enlyn said:
@bmark240
help please
Click to expand...
Click to collapse
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
bmark240 said:
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
Click to expand...
Click to collapse
Yes, I have TWRP installed, but cant access it. Shows the TWRP splash screen and then reboots after like 10 seconds or so.
ADB does not see device. Only shows the device during that 10 second TWRP splash screen time, but even then no commands are effective and it just reboots.
Already tried holding down power button for few seconds. No luck.
I already installed all the possible drivers and media feature packs on my Windows 10. Still no luck.
And yes, I am running latest Windows 10 Pro x64.
And no, since I cant access Fastboot, I can not re-flash TWRP either.
kallum7 said:
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Gonna try that right now. Hopefully that will fix it.
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
THEVAN3D said:
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
Click to expand...
Click to collapse
because i had bricked my phone a few months ago and that is how i got my phone back using the colour os
THEVAN3D said:
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
Click to expand...
Click to collapse
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
FairuzOnn said:
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
Click to expand...
Click to collapse
Thanks, but I already fixed it.
i had it in the past for some reason too. Managed to fix it using the color os method. Carefully followed the steps until i could flash again. That was a year ago tohugh. There should be some thread around wit some all-in-one solution against bricks.