Hi guys!
Sorry for my bad english, i hope it's clear for all
In this morning i've flash Ak Kernel for MultiRom. Everything it's ok, i've just try some Rom like secondary without problem.
Now i've disinstalled the secondary Rom by Multirom Manager, and i've flash the multirom_uninstaller.zip by recovery
File successfully uninstalled, there was only Ak Kernel and MultiRom TWRP but insted of flash kernel stock CM11S i've launched a Nandroid Backup and for the next step i've flash recovery TWRP through fastboot..
And just that the moment i realized that the Opo not recognized from any computer, in fastboot and when he is power on.
I thought the problem is the recovery MultiRom TWRP and so i've flash TWRP clear through TWRP Manager. Now i've a Opo with CM11S stock with kernel Cyano and recovery TWRP, everything as it was before the installation of MultiRom but nothing, my PC's not recognized! I tried with 3 Pc: 2 with Windows 8.1 and 1 with XP but is always ok before that procedure..
I don't think that the problem is the driver but the opo..
Report the error about Windows: Unknown USB Device(device descriptor request failed)
What can i do?
EDIT: I've tried another cable USB and the opo is recognized, so the problem is the cable original..
Related
OK,
I have bootloader 10.6.1.8, TWRP 2.4.4.0 and until this morning a working CM10.2 (latest stable). The device began to switch itself off randomly a few days ago, so I used that as a reason to try Omnirom 4.4.
So, I followed this: http://forum.xda-developers.com/showthread.php?t=2575727
And when I read the line "ONLY WHEN YOU ARE ON THE 4.2+ BOOTLOADER", I looked up what 10.6.1.8 was and decided (rightly or wrongly) it WAS the 4.2+ bootloader. So I flashed TWRP 2.6.3.1 for kitkat.
That resulted in a split screen TWRP, which I managed to use enough to restore my backup (including recovery) and the tablet rebooted into my old working ROM (yay!)...until I rebooted into the recovery again and tried to flash last nights nightly 10.2 build (to see if that solved the power off issue) which failed - and now my ROM bootloops.
Where I am now:
- I can get into fastboot, my device manager (on two machines, a Win7 x86, and a Win8.1 x64) shows the Asus bootloader device, but fastboot shows no devices. ADB shows no devices as well.
- I can get into TWRP, but I cannot see all of the zip files I put on my external card. I put a new ROM there, and TWRP just doesn't see it. So I cannot flash a new ROM. I've tried re-flashing an old version of CM10.2 I found on my internal SD, but that also bootloops.
- The ROM loads up until the lockscreen, where it bootloops. Even when it tries safe-mode, it loops again. My computer see's the tablet when it's booting (if the cable is plugged in at the time) but it loops before I can put anything on the internal SD.
Before I do anything else....what do I do?
(Thank you for any help you can give, in advance).:crying:
dewils80 said:
OK,
I have bootloader 10.6.1.8, TWRP 2.4.4.0 and until this morning a working CM10.2 (latest stable). The device began to switch itself off randomly a few days ago, so I used that as a reason to try Omnirom 4.4.
So, I followed this: http://forum.xda-developers.com/showthread.php?t=2575727
And when I read the line "ONLY WHEN YOU ARE ON THE 4.2+ BOOTLOADER", I looked up what 10.6.1.8 was and decided (rightly or wrongly) it WAS the 4.2+ bootloader. So I flashed TWRP 2.6.3.1 for kitkat.
That resulted in a split screen TWRP, which I managed to use enough to restore my backup (including recovery) and the tablet rebooted into my old working ROM (yay!)...until I rebooted into the recovery again and tried to flash last nights nightly 10.2 build (to see if that solved the power off issue) which failed - and now my ROM bootloops.
Where I am now:
- I can get into fastboot, my device manager (on two machines, a Win7 x86, and a Win8.1 x64) shows the Asus bootloader device, but fastboot shows no devices. ADB shows no devices as well.
- I can get into TWRP, but I cannot see all of the zip files I put on my external card. I put a new ROM there, and TWRP just doesn't see it. So I cannot flash a new ROM. I've tried re-flashing an old version of CM10.2 I found on my internal SD, but that also bootloops.
- The ROM loads up until the lockscreen, where it bootloops. Even when it tries safe-mode, it loops again. My computer see's the tablet when it's booting (if the cable is plugged in at the time) but it loops before I can put anything on the internal SD.
Before I do anything else....what do I do?
(Thank you for any help you can give, in advance).:crying:
Click to expand...
Click to collapse
You need to upgrade you bootloader. 10.6.1.8 is not new enough, as said here: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7. Flash the latest stock blob from fastboot or from TWRP.
After that, you can install TWRP 2.6.3.1 and then OmniROM.
cmendonc2 said:
You need to upgrade you bootloader. 10.6.1.8 is not new enough, as said here: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7. Flash the latest stock blob from fastboot or from TWRP.
After that, you can install TWRP 2.6.3.1 and then OmniROM.
Click to expand...
Click to collapse
Hi - thanks for the reply!
I didn't think I could do that ---^ because I couldn't get fastboot to work on either of my windows machines. But I installed fastboot and adb on my Ubuntu machine, and that worked seamlessly. :laugh:
So I now have the latest Asus firmware on and running, and a working TWRP 2.6.3.0.
That should let me flash the TWRP 2.6.3.1 zip from that thread linked above - and then flash Omnirom. :victory:
For anyone else in this predicament: I had to erase all of the device partitions with fastboot BEFORE flashing the Asus firmware. Without the erase, the Asus ROM just sat on the logo screen doing nothing.
Thanks again.
Hey,
so i was on nighlty CM12 and wanted to switch to CM13.
After i downloaded everything i booted to twrp and flashed the CM13 nightly zip and opengapps for 6.0.
Then i think i made the mistake. I thought i had to update the recovery so i switched to "Flash Images" and flashed the CM13 recovery to the recovery partition.
After flashing the cache i waited like 20 minutes and it was stuck on "Powered by android" screen.
So now it is still hanging there. Device is recognized as ADB device but adb devices show "unauthorized".
Booting with Vol+and Power results in a black screen + the device is shown in the device manager as "QHSUSB_BULK"
Do i have to try the hard brick method or are there other ways?
(I tried to install the qualcomm drivers but im getting an error about broken drivers)
I hope someone can help me
Do you make any backup of your ROM before flashing
@abhishek said:
Do you make any backup of your ROM before flashing
Click to expand...
Click to collapse
Sure, i did a full backup but im unable to boot into recovery
Use Bacon Root Toolkit to restore bricked OnePlus One ..
Sent from Bacon (OnePlus One)
Hello,
I was running Sultans 12.1 Rom.
I downloaded Franco Kernel R44 from the Oneplus One Franco Kernel thread.
I flashed via twrp and then got stuck in the oneplus logo boot loop.
I then tried restarting the phone back into recovery but the phone turned off and is now unable to restart.
I plug the phone into my Windows 10 pc to see if it will show up in device manager but the only thing I get is an Unknown USB device error.
Is there any way to recover back from this. I do have a NAND backup.
Thank you for any help that anyone can offer.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
That solution won't work because I cannot even turn on my phone to enter fastboot. And the phone does not show up properly in device manager even after installing the recommended Samsung drivers.
Use the hard brick repair with Qualcomm 2012 drivers and MSM8974DLTool.exe, that would return you to ColorOS, or COS12 or CM11s respective to flash files. Then use the above method by @kenboyles72 and flash cos12.1 or whatever you want to flash
Transmitted via BACON
I have unlocked the boot loader on oneplus one long back. I tried to upgrade my rom to Resurrection Remix 7.1.1
I successfully upgraded the ROM and also flashed SuperSu in it. I wanted to flash the Opengaps Aroma 7.1 and that is where I ran into issue because of my stupidity.
I found from GitHub that there were some issues with twrp versions to run the aroma installer thus I tried multiple TWRP versions via (Google play - official TWRP recovery app) by downloading them and flashing it to recovery.
I have taken the full nandroid backup but unfortunately didn't keep it on external devices. So it was in the phone itself.
Now the issue -
When I tried flashing TWRP 3.0.2.0 from existing 2.8.4.1 I tried to run the Aroma but it didn't work. Then I tried to flash the recovery with TWRP 2.8.6.1 but Aroma failed again.
However, on the GitHub there was a info stating that known working TWRP recovery on Oneplus one is of TWRP 2.8.4.1
I tried to flash that into recovery and flash the Aroma, but it didn't boot into recovery with that image. Later I restarted the phone, and again flashed the latest recovery version 3.0.2.0
From here I ran into issue. When tried again to flash the Aroma, it didn't work. So I booted recovery again and in that I selected the recovery version 2.8.4.0 for both recovery and boot partition.
After that, phone is neither booting the system nor into recovery. I don't want to loose my data (which is in phone backup) and neither want to try Aroma again. (Even if all the 900mb data needs to be deleted.).
Can the XDA members confirm can I reinstall recovery working image (2.8.4.1) once again through the adb flash recovery <image>. And boot into recovery mode so that I can delete the boot partition once again and reinstall the ROM and data ?
I tried doing that once but one of the laptops which I had access didn't recognize the adb devices. May be the driver was not working for Win10 OS. However, on my personal laptop earlier I was able to run adb commands through CMD prompt. Currently, I don't have personal laptop and may get it by next week.
Can anybody please share me the links of working android driver so that I can install them on current laptop and then try adb commands from SDK to connect my phone.
Any suggestion from members would be of great help.
Note: Please don't suggest the methods to factory reset or lock bootloader to factory settings. As I don't want to loose all my contacts and data.
If there is a way to get just recovery working on the phone, it would be of great help. So that I can wipe other partitions and rebuild it again.
Thank You.
Hello everyone!
I am new here and really looking forward for some answers. I own oneplus one and had a good experience with it. I had upgraded to custom rom that is lineage os 14.1
I wanted to upgrade it to 15.1 through Twrp. I followed the same procedure as i did for last flashing. I wiped the old data and everything and started to flash new rom. But this time twrp was giving an error. When I did research on that i found that i needed to upgrade to newer version of twrp to install lineage os 15.1
I did the same. And then end of it I just unselected the Supersu root and it reboots. Now when I go to the twrp recovery. The oneplus icon shows but then nothing happens. My phone now doesn't have a rom and twrp recovery won't open. When I connect it to my laptop through fastboot, cmd doesn't recognizes the device. I don't have any knowledge about tech and stuff. And I might have done something wrong. Please help me with some solutions
First of all, try to reinstall TWRP trough fastboot (boot in bootloader mode with Volume UP + power), just google a guide if you don't know how fastboot works. also be sure to use the correct twrp for bacon
After that you should be able to boot back in recovery and flash your rom
if still it doesn't work, follow this guide
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Sometimes it happens we brick our phones but No worries as long as you can go to fastboot you can always restore back to how it was before.
Either use the Program the guy above provided or this guide:
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I want to know how to flash the twrp again through fastboot, because when I connect it, phone is not detected in cmd. It says no fastboot devices are there. But then I checked and it says some android thing is connected in device manager. I hope it is my Oneplus one. How to pass this step?
It's the android drivers. Make sure you have the drivers installed.
Thank you so much. I was able to download the twrp again and flashed the 14.1 lineage os. The latest twrp is not flashing in the phone i don't know why and because of that 15.1 lineage os is not flashing and shows error. But still it's a relief that my phone is working. Also, when i switch on the camera it's not working and the flashlight icon also is dim and doesn't gets clicked and not works.