Related
Running A100_1.037.00_WW_GEN1.
When attempting "Fastboot oem unlock" it *immediately* goes to "timed out or user cancelled".
I've tried a half dozen times, with no success. Is there a new method for this firmware, or am I missing something obvious?
Thanks!
It unlocked no problem with me, running the same version.
It timed out on me the first time also (because I was slow), but after rebooting you have to make sure to hit the volume rocker closest to the corner right away. I had to hit it a few times to get it to move over the the unlock position, then hit the other rocker to select.
Slapped on TWRP after that, did a backup and away we went.
ah, you're right. Literally have to be hitting the button over and over to catch it, the timeout's like 1/2 second or something stupid like that.
Cool man, glad to see you got it working.
I had to press it an hold it (15-20 seconds) for it to work and then it selected the 'unlock' option and let me proceed with installing TWRP.
THANKS
Thanks so much, i was pulling my hair out for hrs. It did work thanks
Romman0 said:
It unlocked no problem with me, running the same version.
It timed out on me the first time also (because I was slow), but after rebooting you have to make sure to hit the volume rocker closest to the corner right away. I had to hit it a few times to get it to move over the the unlock position, then hit the other rocker to select.
Slapped on TWRP after that, did a backup and away we went.
Click to expand...
Click to collapse
Hi, I have an Acer A100 that is stock in the acer logo. I can't access it by adb but I can get it into fastboo. fastboot is locked. I have tried to unlock it but whe I send the command "fastboot oem unlock" the Acer logo apears and in my computer screen said "OKAY and [time] finished. Total time ...." I have tried to hold the volume down and click it, etc. not luck. please, help. I am not experience here. Thanks
rdefranx said:
Hi, I have an Acer A100 that is stock in the acer logo. I can't access it by adb but I can get it into fastboo. fastboot is locked. I have tried to unlock it but whe I send the command "fastboot oem unlock" the Acer logo apears and in my computer screen said "OKAY and [time] finished. Total time ...." I have tried to hold the volume down and click it, etc. not luck. please, help. I am not experience here. Thanks
Click to expand...
Click to collapse
If your stock, the a100 boot loader doesn't respond to OEM unlock. That's why we have to push the a200 boot loader to our tabs and unlock that. The only options you have are a factory reset, or installing the ICS update zip from the dev section.
The factory reset is the same procedure as the bootlooader key sequence, except the using the other volume rocker.
Yesterday, I have tired several time, several tools to unlock my N7v2 bootloader. However, they all freezed on UNLOCK BOOTLOADER option on my device. (The process stucked after I pressed "Yes" and cannot go back to fastboot:crying. So I guess there's a problem with my bootloader, right? Please help me
Does your tablet reboot into bootloader?
If so just go in your adb directory and type
fastboot oem unlock
sfhub said:
Does your tablet reboot into bootloader?
If so just go in your adb directory and type
fastboot oem unlock
Click to expand...
Click to collapse
And do note that after pressing yes the device wipes all data and reboots itself. This can take 5-10 minutes.
sfhub said:
Does your tablet reboot into bootloader?
If so just go in your adb directory and type
fastboot oem unlock
Click to expand...
Click to collapse
I did what you said and typed fastboot oem unlock in cmd, then, the device rebooted into bootloader and unlock bootloader screen, but the failure was shown on cmd (unknown error, code error or something), then the device freezed on Yes&No in unlock bootloader. It's really strange.
Coronado is dead said:
And do note that after pressing yes the device wipes all data and reboots itself. This can take 5-10 minutes.
Click to expand...
Click to collapse
It's been stucked there more than 20mins```
jianada520 said:
I did what you said and typed fastboot oem unlock in cmd, then, the device rebooted into bootloader and unlock bootloader screen, but the failure was shown on cmd (unknown error, code error or something), then the device freezed on Yes&No in unlock bootloader. It's really strange.
Click to expand...
Click to collapse
You need to press VolUp to highlight Yes, then power to select
sfhub said:
You need to press VolUp to highlight Yes, then power to select
Click to expand...
Click to collapse
yup. I pressed VolUP to highlight Yes, power buttom to select. then it stucked T_T
Press power button for 60 seconds and try again
sfhub said:
Press power button for 60 seconds and try again
Click to expand...
Click to collapse
well...cmd shown Failed(unknown status code) after typed in fastboot oem unlock.Then, pressed Yes and freezed again omg... I have tired 3 times
jianada520 said:
well...cmd shown Failed(unknown status code) after typed in fastboot oem unlock.Then, pressed Yes and freezed again omg... I have tired 3 times
Click to expand...
Click to collapse
After it fails and you reboot, is the BL still locked at this point or is it unlocked already? Perhaps, it is already unlocked and you may just need to factory reset to get the device to fully boot up.
The little lock symbol on the boot screen will show a small break if the BL is unlocked.
jianada520 said:
well...cmd shown Failed(unknown status code) after typed in fastboot oem unlock.Then, pressed Yes and freezed again omg... I have tired 3 times
Click to expand...
Click to collapse
What the previous post said.
Also are you by chance using usb 3 port?
cowabunga said:
After it fails and you reboot, is the BL still locked at this point or is it unlocked already? Perhaps, it is already unlocked and you may just need to factory reset to get the device to fully boot up.
The little lock symbol on the boot screen will show a small break if the BL is unlocked.
Click to expand...
Click to collapse
It's still locking, and shows a locked status on the fastboot screen...I have done factory reset several times,but nothing was changed
sfhub said:
What the previous post said.
Also are you by chance using usb 3 port?
Click to expand...
Click to collapse
nope, it's all usb 2 port. All drivers are installed correctly, and it shows success after perform the Wug's NRT 1.71 full driver test .
sfhub said:
Press power button for 60 seconds and try again
Click to expand...
Click to collapse
wow, i finally unlocked it. I reinstalled bootloader interface while the device was freezing :victory:. It such a miracle. Thx for assisting me.:laugh:
jianada520 said:
wow, i finally unlocked it. I reinstalled bootloader interface while the device was freezing :victory:. It such a miracle. Thx for assisting me.:laugh:
Click to expand...
Click to collapse
What does "reinstalled bootloader interface" mean anyhow? You flash the bootloader again onto the device from the factory image? Or did you have to reinstall something on your computer (ie. drivers, etc...)?
Would be helpful to clarify for anyone who hits this thread in the future.
cowabunga said:
What does "reinstalled bootloader interface" mean anyhow? You flash the bootloader again onto the device from the factory image? Or did you have to reinstall something on your computer (ie. drivers, etc...)?
Would be helpful to clarify for anyone who hits this thread in the future.
Click to expand...
Click to collapse
It means I reinstalled bootloader interface driver on PC while the device was stucking on UNLOCK BOOTLOADER option screen.(after selected Yes). It suddenly turned into fastboot screen and continued to finish rest of processes. I hope this would be helpful for people who hits this thread. Make sure your USB drivers are installed correctly , because they seem installed correctly but actually not. If you got stuck on UNLOCK BOOTLOADER screen, try to reinstall it or install another usb driver..
Just wanted to say that this worked for me too!
I would get to the point where I would have to pick 'Yes' on the Nexus 7 screen using the volume buttons, and then when I would press the power button to confirm, it would just freeze. The volume buttons would not respond and I had to hard reboot by holding down the power button.
I just tried jianada520's method of getting to the 'freeze' point, and then I did this:
-Keep the tablet plugged in
-Open Device Manager and right click > uninstall the Android ADB interface and remove the driver
-Install the Driver (I used the Nexus Root Toolkit and installed/repaired the Universal Driver)
-Back on the Device Manager - Scan for hardware Changes
-Nexus should be detected and some kind of driver is installed
At this point the screen went back to the Bootloader menu automatically, but it now says 'LOCK STATE - unlocked', success!
Just thought I'd add my experience as this was sending me in circles for the past 2 hours of rebooting, reinstalling drivers etc.
dodgyc said:
Just wanted to say that this worked for me too!
I would get to the point where I would have to pick 'Yes' on the Nexus 7 screen using the volume buttons, and then when I would press the power button to confirm, it would just freeze. The volume buttons would not respond and I had to hard reboot by holding down the power button.
I just tried jianada520's method of getting to the 'freeze' point, and then I did this:
-Keep the tablet plugged in
-Open Device Manager and right click > uninstall the Android ADB interface and remove the driver
-Install the Driver (I used the Nexus Root Toolkit and installed/repaired the Universal Driver)
-Back on the Device Manager - Scan for hardware Changes
-Nexus should be detected and some kind of driver is installed
At this point the screen went back to the Bootloader menu automatically, but it now says 'LOCK STATE - unlocked', success!
Just thought I'd add my experience as this was sending me in circles for the past 2 hours of rebooting, reinstalling drivers etc.
Click to expand...
Click to collapse
Congratz. You explained the solution very clear.
Hi guys
I've got a desire Hd, over 2 years old now so out of warranty. Not rooted, Android 2.3.5 (official ROM), Middle East ROM and relocked.
When i turn it on,After a minute or less, when it would normally show an android screen, the screen goes to bootloader. and when I wanna reboot it or enter to the recovery , the screen goes blank but the phone is still on, and the screen is still on but in a very dark grey. if you hold it on an angle the backlight appears to be on. But from that point nothing happens, the buttons no longer respond, and I have to remove the battery to turn it off.
Although I've tried to reset factory my phone but it didn't work and the screen goes blank again when the backlight is still on.
Thanks for your help.
PLease help me asap.
did u ever experience this problem?
What did you do to get it in this state?
bananagranola said:
What did you do to get it in this state?
Click to expand...
Click to collapse
nothing much. I've just removed the battery many times, because the Volume down didn't respond and I wanted to enter to the bootloader!!
any solution?!! :crying:
try this:
What happens after putting battery back whitout pressing the ON-Button?
If it's still off, try pressing once ON-Button AFTER holding Volume-UP till HBOOT comes... maybe your phone need that
OR:
Connect the phone (when its off) to PC. Then turn phone on. Flash the boot.img over PC with fastboot.exe (only boot.img, not hole ROM). I had the same troubles with every ROM i tried, i had to flash it manually.
ammo12 said:
try this:
What happens after putting battery back whitout pressing the ON-Button?
If it's still off, try pressing once ON-Button AFTER holding Volume-UP till HBOOT comes... maybe your phone need that
OR:
Connect the phone (when its off) to PC. Then turn phone on. Flash the boot.img over PC with fastboot.exe (only boot.img, not hole ROM). I had the same troubles with every ROM i tried, i had to flash it manually.
Click to expand...
Click to collapse
Does it needs any RUU to do this or the boot.img is already exist in my phone?! (my phone is S-ON and relocked)
and what's the exact command to flash boot.img not the whole ROM?
Transporter2009 said:
Does it needs any RUU to do this or the boot.img is already exist in my phone?! (my phone is S-ON and relocked)
and what's the exact command to flash boot.img not the whole ROM?
Click to expand...
Click to collapse
Once you're in the bootloader, and assuming your computer has the correct drivers and img files, type in CMD:
"fastboot flash boot boot.img"
I think I'm in a worse condition than you. My phone won't even boot into bootloader, have tried all the hardware keys (Vol+-, Home, Back, Menu) with Power button. I have even tried taking the volume cable out and pressing the buttons directly but my phone still goes into the boot animation and then blank screen with backlight on. My computer is also not recognizing the phone so adb doesn't work. I'm out of ideas, anyone got any?
cherhunghow said:
Once you're in the bootloader, and assuming your computer has the correct drivers and img files, type in CMD:
"fastboot flash boot boot.img"
I think I'm in a worse condition than you. My phone won't even boot into bootloader, have tried all the hardware keys (Vol+-, Home, Back, Menu) with Power button. I have even tried taking the volume cable out and pressing the buttons directly but my phone still goes into the boot animation and then blank screen with backlight on. My computer is also not recognizing the phone so adb doesn't work. I'm out of ideas, anyone got any?
Click to expand...
Click to collapse
I did it but unfortunately I faced with this Failure:
Code:
C:\Android>fastboot flash boot boot.img
sending 'boot' (2840 KB)... OKAY
writing 'boot'... INFOsignature checkin
FAILED (remote: signature verify fail)
what should I do then?? :crying:
and about your problem i think the Volume Key is the problem and it can be fix by replacing the volume key or even with a simple cleaning. don't worry
Hi All,
Apologies if this has already been covered somewhere but I've been scouring the internet for most of the day and come up with nothing.
tldr: My Pixel 6 Pro has been running absolutely fine for 9 months, no issues what so ever through all the automatic updates, I powered it off this morning to apply a new screen protector went to turn it back on and its been stuck in fast boot since with every option that can be selected returning to the same screen. Not been fiddled with, no root nor boot loader unlock.
Simply turned it off put the screen protector on turned back on and it has been stuck in fast boot ever since with a list of things below I have tried;
Restarted, no change straight back to fastboot.
Recovery Mode, no luck same as 1.
Rescue mode and using googles update/repair tool, cannot connect result is the same as number 1.
Restart bootloader, no luck same as 1.
Flashed barcode setting on and off (i know), device state & NOS Production some times change see non error image.
Flashing via android flash tool, boot loader locked wont allow. 'error getting device locked state -1'
Using force options confirms bootloader needs unlocking.
Connected to fastboot.exe on pc.
fastboot devices, correctly recognises the device is connected.
fastboot set_active a, FAILED (remote: 'error getting device locked state -1') message.
fastboot set_active a --force, same as above.
fastboot set_active other, same as above
fastboot reboot --slot a, accepts command with slower restart than normal but reverts to b.
fastboot getvar all, works list in attachments if its is of any interest.
Details of the device,
Contract device from O2 so probably vendor locked.
Was working fine but the past week or so there have been occasions where it wouldn't accept a correct pin, then would after about 5-6 attempts then be fine some time. I didn't pay it too much thought at the time as nothing seemed off and fingerprint was always fine but seems more relevant now.
I'm not enrolled for the beta.
I haven't tried to root or unlock the bootloader.
For the first time I've been pretty boring with a phone and haven't fiddled with a thing.
I don't think I've even had the dev options menu opened on it.
I refuse to believe its bricked itself for no apparent reason but google seems to be failing me or I must be looking for the wrong thing. There must be something I can do via fastboot surely given that it has got some form of communication?
If anyone has any further suggestions it would be much appreciated before I go down the return/replace route.
I assume you didn't have OEM Unlocking enabled before this happened. Without an unlocked bootloader, there is nothing you can do to fix it, because the bootloader will reject any of the necessary commands to reflash the device. If you're still under warranty, seek warranty repair; this is going to require replacing the mainboard, because no one has the necessary tools to perform a low level reflash.
If the bootloader was unlocked, fixing this would be fairly simple because you'd just have to reflash the boot image. But, as I described above, a locked bootloader rejects all the commands that would help in this situation, and there is no way to unlock the bootloader if OEM Unlocking was not enabled.
dch29 said:
Hi All,
Apologies if this has already been covered somewhere but I've been scouring the internet for most of the day and come up with nothing.
tldr: My Pixel 6 Pro has been running absolutely fine for 9 months, no issues what so ever through all the automatic updates, I powered it off this morning to apply a new screen protector went to turn it back on and its been stuck in fast boot since with every option that can be selected returning to the same screen. Not been fiddled with, no root nor boot loader unlock.
Simply turned it off put the screen protector on turned back on and it has been stuck in fast boot ever since with a list of things below I have tried;
Restarted, no change straight back to fastboot.
Recovery Mode, no luck same as 1.
Rescue mode and using googles update/repair tool, cannot connect result is the same as number 1.
Restart bootloader, no luck same as 1.
Flashed barcode setting on and off (i know), device state & NOS Production some times change see non error image.
Flashing via android flash tool, boot loader locked wont allow. 'error getting device locked state -1'
Using force options confirms bootloader needs unlocking.
Connected to fastboot.exe on pc.
fastboot devices, correctly recognises the device is connected.
fastboot set_active a, FAILED (remote: 'error getting device locked state -1') message.
fastboot set_active a --force, same as above.
fastboot set_active other, same as above
fastboot reboot --slot a, accepts command with slower restart than normal but reverts to b.
fastboot getvar all, works list in attachments if its is of any interest.
Details of the device,
Contract device from O2 so probably vendor locked.
Was working fine but the past week or so there have been occasions where it wouldn't accept a correct pin, then would after about 5-6 attempts then be fine some time. I didn't pay it too much thought at the time as nothing seemed off and fingerprint was always fine but seems more relevant now.
I'm not enrolled for the beta.
I haven't tried to root or unlock the bootloader.
For the first time I've been pretty boring with a phone and haven't fiddled with a thing.
I don't think I've even had the dev options menu opened on it.
I refuse to believe its bricked itself for no apparent reason but google seems to be failing me or I must be looking for the wrong thing. There must be something I can do via fastboot surely given that it has got some form of communication?
If anyone has any further suggestions it would be much appreciated before I go down the return/replace route.
Click to expand...
Click to collapse
Kind of sounds like a stuck hardware button, either power and volume that's makes the phone think you are holding down buttons during boot to get into bootloader
Can you press the power button to start the system? If not, try this (it may be useful, but it may get worse, please be cautious) Hold on power button and volume down at the same time for 45s, When you press 30 seconds, the screen should turn off and restart to this interface. Then do it again as above, when it restarts to the interface again, try to press the power button to enter the system.translate form Chinese(simplified)_Google
Juuuuune said:
Can you press the power button to start the system? If not, try this (it may be useful, but it may get worse, please be cautious) Hold on power button and volume down at the same time for 45s, When you press 30 seconds, the screen should turn off and restart to this interface. Then do it again as above, when it restarts to the interface again, try to press the power button to enter the system.translate form Chinese(simplified)_Google
Click to expand...
Click to collapse
Thanks but no change sadly, still completely booked.
Hello @All,
I bought myself a new toy: a bricked Nexus 5x. The only thing I can do is enter the bootloader mode. Otherwise the phone is showing the Google logo.
In bootloader mode the last two lines are "Secure Boot - Enabled" and "Device State - Locked". The "fastboot devices" states that the device is present.
I can neither access any recovery nor install one (because bootloader locked). The device isn't rooted. Parallel to posting this I am searching the depths of the web. Of course without a solution.
Can I do anything else?
hmm, did you try going into the recovery and resseting it, if that didnt work go on your computer, go to bootloader mode, and on your computer try typing: fastboot flashing unlock or fastboot oem unlock, if none of those work, then try reflashing the firmware trough recovery or fastboot, here is the rom for adb sideload trough recovery...
here is a direct download cuz it wouldnt post the zip https://dl.google.com/dl/android/aosp//bullhead-ota-mhc19q-8fe67a2b.zip
I can't access the recovery, but I'll try fastboot again. "fastboot flashing unlock" and "fastboot oem unlock" don't work. I get a " FAILED (remote: 'oem unlock is not allowed')" message.
ok, try this, go in fastboot, and run this command, fastboot flash boot N2G47Z_4Cores.img with the img that i send you, if it works, then see if iit boots up!
it doesnt wanna send it, heres a link to download it https://www.dropbox.com/s/tm7qt98r6d7q2a6/N2G47Z_4Cores.img?dl=0
I tried
Code:
$ fastboot flash boot N2G47Z_4Cores.img
and the answer was
Code:
Sending 'boot' (12045 KB) OKAY [ 0.464s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
...
But thanks for your effort to help me
Heinz- said:
I tried
Code:
$ fastboot flash boot N2G47Z_4Cores.img
and the answer was
Code:
Sending 'boot' (12045 KB) OKAY [ 0.464s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
...
But thanks for your effort to help me
Click to expand...
Click to collapse
hey is there a way you can send me a video of what happens when it boots up and when you try to enter recovery, maybe i can still help.
if you cant here send it to my mail [email protected] , this is my mail since 2016 and zombie was mostly for minecraft . but then i was young, so yeah.
I can only describe it for you...
When I try to boot into recovery it happens the same as booting the system. The Google sign appears with a short buzz of the vibration motor, then disappears after 16 seconds, and a second later the same again. A classical boot loop. I can only access the bootloader mode. When I try to boot from there, the same happens. The "system state" is locked, and Secure Boot is enabled.
I can power off the device from the bootloader, then it stays off.
Is there any hope to bring it to life again, or is it a brick forever?
Heinz- said:
I can only describe it for you...
When I try to boot into recovery it happens the same as booting the system. The Google sign appears with a short buzz of the vibration motor, then disappears after 16 seconds, and a second later the same again. A classical boot loop. I can only access the bootloader mode. When I try to boot from there, the same happens. The "system state" is locked, and Secure Boot is enabled.
I can power off the device from the bootloader, then it stays off.
Is there any hope to bring it to life again, or is it a brick forever?
Click to expand...
Click to collapse
well it looks like a problem with either the ram, vibrator, or the partitions, sadly this happened with old nexus devices, so its a brick forever sadly. but if you want you can sell it online for parts.
Ok then, I hope I can sell the brick. Thank you again for your help, @NikolaTechGuy !
But there's one last hope: This thread, shown to me directly under this answer ("Similar threads") that I'm currently writing. One last try...
Heinz- said:
Ok then, I hope I can sell the brick. Thank you again for your help, @NikolaTechGuy !
But there's one last hope: This thread, shown to me directly under this answer ("Similar threads") that I'm currently writing. One last try...
Click to expand...
Click to collapse
Sorry if this is too late but are you sure you can't do anything with the phone?
To enter Bootloader Mode press and hold Vol Down + Power. You will automatically enter Fastboot Mode. You will see the settings of 'Secure boot' and 'Device State'
Use Vol up and Vol Down to scroll through menu and the Power button to select an option:
Start
Restart bootloader
Recovery Mode
Power Off
If you select Recovery Mode, wait until you see the 'Robot lying down' image and "No command" text appear on screen. Now hold Power button and briefly press the Vol up button. The 'Android Recovery' screen should now appear.
To enter LG 'Download Mode':
Power Off your phone.
Now press the Vol. Up button and hold it
Now Plug your phone into your computer using a USB cable
After a few seconds 'download mode' should appear on your phone screen, followed by a 'Firmware Update' screen.
If it doesn't enter LG Downoad Mode then check in your Windows Device Manager under COM/PORTS. See if you have connected in Qualcomm 9008 EDL (Emergency Download ) Mode. The connection will appear as Qualcomm HS-USB QDLoader 9008. You might have to download the Qualcomm driver for this to work.
If you can get into Recovery Mode or EDL mode you still have options! It depends how much time and effort you want to spend on a 7 year old phone with no sd card option.
You can become 'obsessed' like me, and buy a hot air gun solder rework station to try and reflow the solder under the MSM8992 chip to fix the 'bootloop of death'! NOTE: I have tried it on 3 bricked Nexus 5X and only got a temporary success on one phone - the other two I did a very good job of frying the chip! Mind you I now have alot of spare parts!
I took the Nexus to a repairman who calls himself "Handy-Doc". He told me it was the hardware. He couldn't install anything as well as me. But replacing the motherboard could help. So I ordered a motherboard on AliExpress. This is my last try!
Heinz- said:
I took the Nexus to a repairman who calls himself "Handy-Doc". He told me it was the hardware. He couldn't install anything as well as me. But replacing the motherboard could help. So I ordered a motherboard on AliExpress. This is my last try!
Click to expand...
Click to collapse
You will have to keep us updated. I looked at those motherboards but wasn't sure about them. What version of Android is installed? Do they come with a new IMEI or are they blank? etc. Taking a 5X apart is very straightforward with a couple of simple phone tools. There are plenty of Youtube videos that show you how to do it - it might save you having to pay "handy-Doc"!
No, it doesn't work. I can plugin the phone when it's in "Download Mode" but nothing more happens. After a few seconds the phone tries to boot again. The "Handy Doc" man gave me back the phone without asking for payment.
The motherboard is on its way from China to Germany. This can take several weeks.
Hi
I am sorry if I am posting this at the wrong place.
I bricked my Nexus 5x device flashing DivestOS on it.
I flashed two different LineagOS on this device successfully in the past and the genuine Android when I was rolling it back. It always worked, but not this time.
Trying to roll it back to genuine Android, there were errors that several ".img" was missing in the archive.
I tried to chat with Android developers on Matrix chat and also reported this problem here, on DivestOS forum, but they blame hardware and/or user mistake.
I took it farther to sort the device problem and made it unresponsive, the screen is black and it does not react to anything at all now.
All I needed to know if there is ANY way to bring this device back to life.
I found some "LGFlashTool_2.0.1.6" on one of the old forumes of (2016), but I did not try it, I believe it will not work, and wanted to know from Android developer's oppinion before I try anything else.
Thank you
---Update:
I opened it, unplugged and re-plugged the battery.
Was able to boot it into the fastboot menu.
1. secure boot - enabled
2. device state - unlocked
-Tried to flash the genuine Android (I did it several times and I know it works)
No success!
Please see the terminal screenshot attached for errors.
If you can get into fastboot have you tried flashing TWRP and getting into it again? Then try flashing a lineageOS that you know works.
bjlabuk said:
If you can get into fastboot have you tried flashing TWRP and getting into it again? Then try flashing a lineageOS that you know works.
Click to expand...
Click to collapse
Thanks for reply =).
This is a goot point.
I'll try and post the result here.
Now, not always I can boot it into fastboot menu, sometimes it's totally un-resposive, does not show any sights of life, it can be the battery charge problem (battery was not bad though).
balakarpo said:
Thanks for reply =).
This is a goot point.
I'll try and post the result here.
Now, not always I can boot it into fastboot menu, sometimes it's totally un-resposive, does not show any sights of life, it can be the battery charge problem (battery was not bad though).
Click to expand...
Click to collapse
Yea, looking at the log everything appears to be okay until that last line. Did you use flash-all.bat from the factory image bullhead-opm7.181205.001-factory-5f189d84.zip?