Hello Lovely people of XDA,
It has been a while since I have requested help here due to the huge library of information available but I am unable to solve this one and I think it should be pretty simple.
For completeness, here is the order of events:
ROOTed One and running stock CM11s with no problems since August 2014.
Wanted a smoother system so flashed vanilla Franco Kernel (very nice) yesterday.
Wanted a bit more so after some searching, found the SlimSaber ROM with TyrV74-Linaro Kernel as a suitable choice.
Now, I followed order of install but stupidly, didnt clear the cache or dalvik cache following install.
I got stuck in boot loop so booted to fastboot to open recovery through ADB.
PROBLEM STARTS
My PC didnt recognise my device and this was confirmed through the blank list returned when using "ADB Devices" in the command window.
I updated the drivers through the ADB interface, restarted computer and tried again. Same thing. I then downloaded the drivers from the Google link in one of the forums (http://developer.android.com/sdk/win-usb.html#top), restarted and connected again. I then tried two solutions (although they both do the same thing) and update the drivers through Device Manager and searching for them using the "have disk" option.
This still didnt work.
From what I can tell this is a driver issue but I have installed several times now the most up to date drivers and from what I can tell, the only difference between my screenshots and the help pages/forum posts is that my Device Manager list doesn't recognise the phone as the A0001, just an "Android Device" (pic attached).
I have searched the forums and all roads lead to either re-installing the drivers or changing the driver settings through device manager, both of which I have tried several times but no joy when I use ADB to check for devices.
Any ideas? I will try anything as I now have a beautifully BOOT-Looped OnePlus!
Also, if anyone knows how to boot to recovery from phone off state then that will also help! :)
It has been a while since I have requested help here due to the huge library of information available but I am unable to solve this one and I think it should be pretty simple.
For completeness, here is the order of events:
ROOTed One and running stock CM11s with no problems since August 2014.
Wanted a smoother system so flashed vanilla Franco Kernel (very nice) yesterday.
Wanted a bit more so after some searching, found the SlimSaber ROM with TyrV74-Linaro Kernel as a suitable choice.
Now, I followed order of install but stupidly, didnt clear the cache or dalvik cache following install.
I got stuck in boot loop so booted to fastboot to open recovery through ADB.
PROBLEM STARTS
My PC didnt recognise my device and this was confirmed through the blank list returned when using "ADB Devices" in the command window.
I updated the drivers through the ADB interface, restarted computer and tried again. Same thing. I then downloaded the drivers from the Google link in one of the forums (http://developer.android.com/sdk/win-usb.html#top), restarted and connected again. I then tried two solutions (although they both do the same thing) and update the drivers through Device Manager and searching for them using the "have disk" option.
This still didnt work.
From what I can tell this is a driver issue but I have installed several times now the most up to date drivers and from what I can tell, the only difference between my screenshots and the help pages/forum posts is that my Device Manager list doesn't recognise the phone as the A0001, just an "Android Device" (pic attached).
I have searched the forums and all roads lead to either re-installing the drivers or changing the driver settings through device manager, both of which I have tried several times but no joy when I use ADB to check for devices.
Any ideas? I will try anything as I now have a beautifully BOOT-Looped OnePlus!
Also, if anyone knows how to boot to recovery from phone off state then that will also help! :)
Aucun commentaire:
Enregistrer un commentaire