Hello there!
So I accidentally bricked my phone a few days ago and now it is resting as a brick on my desk, but how did all of this happen, you may ask?
Well, the story is rather simple, I had the Simple ROM V. 1.4 installed on my G2 and decided to update it to version 2.0, which is posted here somewhere, but what I didn't notice was that the file I was downloading (even though it said it was compatible with all versions) was not for the D800 but for the LS980 and this bricked the phone.
First I was stuck on fastboot mode and was able to get my download mode back, but it kept saying that it couldn't flash the stock rom because it was the wrong model.
Looking online and through these forums, I found out that it was because the download mode that it had was not the right one to use, and that I needed to "destroy" download mode, enter once again in fastboot mode and flash the new download mode, this, however, turned out out to be impossible as the fastboot mode is no longer being detected by Windows nor Linux.
I installed back the USB drivers, installed Android ADB, changed the UDEV rules with mew vendors ID from the list provided by Google, updated the drivers on my PC and even tried to change the directory in which the phone would appear.
The problem resumes to this:
When in fastboot mode (connected to the PC) and type
in both Windows and Linux, I get the response as
.
When I try with
I get back nothing.
Curious thing is that the phone does appear on Device Manager as an Android ADB device and when on Linux I use the
I get back that it is being recognized as
, which I believe is the phone.
When trying to run any fastboot commands, the phone stays on "waiting for device" on Linux or "flashing" on Windows and later a messages pops back at me with
.
With all this in mind, I would like to ask you guys, is there something that I am missing?
Any help will be truly appreciated it!
So I accidentally bricked my phone a few days ago and now it is resting as a brick on my desk, but how did all of this happen, you may ask?
Well, the story is rather simple, I had the Simple ROM V. 1.4 installed on my G2 and decided to update it to version 2.0, which is posted here somewhere, but what I didn't notice was that the file I was downloading (even though it said it was compatible with all versions) was not for the D800 but for the LS980 and this bricked the phone.
First I was stuck on fastboot mode and was able to get my download mode back, but it kept saying that it couldn't flash the stock rom because it was the wrong model.
Looking online and through these forums, I found out that it was because the download mode that it had was not the right one to use, and that I needed to "destroy" download mode, enter once again in fastboot mode and flash the new download mode, this, however, turned out out to be impossible as the fastboot mode is no longer being detected by Windows nor Linux.
I installed back the USB drivers, installed Android ADB, changed the UDEV rules with mew vendors ID from the list provided by Google, updated the drivers on my PC and even tried to change the directory in which the phone would appear.
The problem resumes to this:
When in fastboot mode (connected to the PC) and type
Code:
fastboot devices
Code:
???????? devices
When I try with
Code:
adb devices
Curious thing is that the phone does appear on Device Manager as an Android ADB device and when on Linux I use the
Code:
lsusb
Code:
Google Inc. 18d1 d00d
When trying to run any fastboot commands, the phone stays on "waiting for device" on Linux or "flashing" on Windows and later a messages pops back at me with
Code:
Error too many links
With all this in mind, I would like to ask you guys, is there something that I am missing?
Any help will be truly appreciated it!
A few theories have actually been actually recommended so far to
RépondreSupprimerunwind the complicated vitiligo pathogenesis.