i try to install lineageOS and got a black screen - Android Q&A, Help & Troubleshooting

Hello i have a sony xperia Z1 and try to install lineageOS. I follow this guide : wiki.lineageos.org/devices/yuga/install
when i try :
Code:
adb push twrp-x.x.x-x-yuga.img /sdcard
bash say permission denied. But previously i have
Code:
Bootloader unlock allowed: Yes
As i am totally new, i try to restart all the install instruction in bash with root access # (command su).
And now a i have a black screen and adb doesn't work
Code:
[email protected]:/$ adb shell
error: no devices/emulators found
but it seem that fastboot mode is ok because i can flash rom
Code:
[email protected]:~$ fastboot devices
BH915GK90D fastboot
[email protected]:~$ fastboot flash boot twrp-2.5.0.0-yuga.img
target didn't report max-download-size
sending 'boot' (9038 KB)...
OKAY [ 0.357s]
writing 'boot'...
OKAY [ 0.604s]
finished. total time: 0.961s
After that if i try to reboot to the TWRP recovery:
Code:
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.052s
[email protected]:~$
the notification light turn red, off, red, off, green and after off.
So i got a black screen.
If i press the power button, nothing happen.
So i anyone could help me ... Thank you in advanced.

Related

[Q] Fastboot 'Bad File Discriptor', or Freezing on Flash

Hi All,
I've just got myself a Dell Streak, which I am trying to flash with the elloh ROM (following steps 1-8 here http://forum.xda-developers.com/showpost.php?p=23527490&postcount=216). I'm using Linux (Ubuntu), and have all the Android SDK etc installed, and appearing to be working.
When I " sudo fastboot -i 0x413c flash recovery recovery.img " I get the following:
Code:
sending 'recovery' (3434 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
I have also tried running the same command through VirtualBox (running WinXP), which seems to get much further. I get:
Code:
sending 'recovery' (3434 KB)
OKAY [0.230s ]
writing 'recovery'...
at which point the Streak displays 'Download RECOVERY Done', and nothing else happens. The DOS prompt appears to still be 'writing', and the only way of getting out is a Ctl+C. Having tried this and continued with the instructions, the Streak produces a lot more errors during the update (which I am assuming are related to this, and have ended up bricking my device).
Does anyone have any suggestions as to what my problem might be? Either with VM or running in 'pure linux'?
Cheers
Adam
webbsimax said:
Hi All,
I've just got myself a Dell Streak, which I am trying to flash with the elloh ROM (following steps 1-8 here http://forum.xda-developers.com/showpost.php?p=23527490&postcount=216). I'm using Linux (Ubuntu), and have all the Android SDK etc installed, and appearing to be working.
When I " sudo fastboot -i 0x413c flash recovery recovery.img " I get the following:
Code:
sending 'recovery' (3434 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
I have also tried running the same command through VirtualBox (running WinXP), which seems to get much further. I get:
Code:
sending 'recovery' (3434 KB)
OKAY [0.230s ]
writing 'recovery'...
at which point the Streak displays 'Download RECOVERY Done', and nothing else happens. The DOS prompt appears to still be 'writing', and the only way of getting out is a Ctl+C. Having tried this and continued with the instructions, the Streak produces a lot more errors during the update (which I am assuming are related to this, and have ended up bricking my device).
Does anyone have any suggestions as to what my problem might be? Either with VM or running in 'pure linux'?
Cheers
Adam
Click to expand...
Click to collapse
I have the same issue. I mean I didn't tried to copy with windows because I don't have it.
I'm trying to find any usefull information how to flash recovery with fastboot to my dell streak 5 under ubuntu for 2 days but I haden't found solution.
Whenever I want to send file in fastboot mode I get:
Code:
[email protected]:~/Pobrane/DSC_flashme2$ sudo fastboot -i 0x413c flash amss amss.mbn
sending 'amss' (15780 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
any ideas what to do?
Code:
sudo fastboot -i 0x413c reboot
works fine
I have the same issue
i´m using Stable Clockwork Mod Recovery for Desire C from here but, i get this error:
Code:
$ fastboot flash recovery recovery.img
sending 'recovery' (5002 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
im using linuxmint x86
abr4xas said:
i´m using Stable Clockwork Mod Recovery for Desire C from here but, i get this error:
Code:
$ fastboot flash recovery recovery.img
sending 'recovery' (5002 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
im using linuxmint x86
Click to expand...
Click to collapse
obviously it will fail because you are not using the one for streak 5. we have our own working recovery you know.
Had the same problem, using an other fastboot (the one found on http://forum.xda-developers.com/showthread.php?t=1067273) was the solution for me. I'm using a 64-bit Ubuntu 12.04.

[Q] [Solved] [5.0.2/LTE] Cannot boot into recovery mode

Hello guys,
I've flashed TWRP for Nexus 9 2.8.6:
Code:
#adb devices
List of devices attached
HT4C3WV01363 device
#adb reboot bootloader
#fastboot devices
HT4C3WV01363 fastboot
#fastboot flash recovery twrp-2.8.6.0-flounder.img
target reported max download size of 518205818 bytes
sending 'recovery' (13208 KB)...
OKAY [ 0.744s]
writing 'recovery'...
(bootloader) Device State : Unlocked
OKAY [ 0.867s]
finished. total time: 1.612s
There's no way to continue into recovery without rebooting:
Code:
#fastboot reboot
rebooting...
finished. total time: 0.099s
#adb reboot recovery
... leads to a fallen Android! (see attached screenshot)
Any suggestion?
Fastboot flash TWRP recovery again.
After doing above, don't touch your PC again. Pick up your device and use volume button to navigate to hboot, then navigate to recovery and use power button to select.
Done.
Yes, thanks!
actionmystique said:
Yes, thanks!
Click to expand...
Click to collapse
Welcome. And FWIW: there's a button for that...

HDX 7 only fastboot posible

hi
i try to install a custom firmware. i think i do many wrong things(i try many of the instructions). before i started the hdx had the latest firmware!
Now when i start the hdx7 it show "Kindle Fire"(gray), then the display is red for less then a second. after this it shows fastboot logo (also, if the cable is not connected)
On my WINDOWS 10 PC i have install "Minimal ADB and Fastboot". When i enter fastboot devices. i get this:
00D2070834110HS3 fastboot
any chance?
thx
atik03 said:
hi
i try to install a custom firmware. i think i do many wrong things(i try many of the instructions). before i started the hdx had the latest firmware!
Now when i start the hdx7 it show "Kindle Fire"(gray), then the display is red for less then a second. after this it shows fastboot logo (also, if the cable is not connected)
On my WINDOWS 10 PC i have install "Minimal ADB and Fastboot". When i enter fastboot devices. i get this:
00D2070834110HS3 fastboot
any chance?
thx
Click to expand...
Click to collapse
See last couple paragraphs in this post.
Davey126 said:
See last couple paragraphs in this post.
Click to expand...
Click to collapse
i get this:
Code:
fastboot -i 0x1949 erase aboot
erasing 'aboot'...
FAILED (remote: : partition doesn't exist)
finished. total time: 0.003s
Code:
fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.009s
Code:
wmic partition where index=22 get diskindex
Keine Instanzen verfügbar.
(No instances available)
atik03 said:
i get this:
Code:
fastboot -i 0x1949 erase aboot
erasing 'aboot'...
FAILED (remote: : partition doesn't exist)
finished. total time: 0.003s
Code:
fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.009s
Code:
wmic partition where index=22 get diskindex
Keine Instanzen verfügbar.
(No instances available)
Click to expand...
Click to collapse
Appears you are out of luck. Sorry ...

YuYureka stuck in FASTBOOT

Hi everyone.
I had a working Lineage OS 14.1 installed on my yureka device.
I got the newer version TWRP and instead of going to install the latest update from COMMAND PROMPT , i used FLASFHFIRE and this corrupted my device.
My phone when switched OFF shows the battery indications of charging, when connected to charger.
But, doesn't start when switched ON and when connected to laptop, shows the YU logo and goes into FASTBOOT mode.
Code:
$ fastboot devices & $ fastboot -i 0x1ebf devices
detects the phone and gives this
4a252f6 fastboot
Click to expand...
Click to collapse
But, any other FASTBOOT command to flash the boot or recovery fails with error , for the first run
Error 1 :
Code:
D:\RootingKit\platform-tools>fastboot flash boot 15_April_2018_Boot.img
target reported max download size of 268435456 bytes
sending 'boot' (20480 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 5.001s
And successive runs shows a different error
Error 2:
Code:
D:\RootingKit\platform-tools>fastboot flash boot 15_April_2018_Boot.img
target didn't report max-download-size
sending 'boot' (20480 KB)...
FAILED (command write failed (No error))
finished. total time: 0.000s
Now, when i remove the cable and connect it back then again the first error message is observed.
I have tried all cables from different phones, samsung xperia yureka and others and not able to flash. Also, i have tried on different USB ports of my laptop and no SUCCESS.
Please help me out here.

Download Mode - Restart loop after installing OS

Adroid One 10
Unlock solved and installed the lineage OS a several times in twrp with success according to the given instruction here:
https://raw.githubusercontent.com/RaghuVarma331/changelogs/master/crossdevelopment/abcrins.txt
but the phone didnt boot the OS after restarting neither in slot A nor B. In twrp u could read that there was "no OS installed" (??).
In the last try i changed the slot before installing and now the phone hangs in a restart loop with download mode and i connot turn down the phone or get back to twrp. Trying to connect it by adb to restart twrp is not working....
=========================
My errors while trying to get out:
=========================
fastboot boot twrp.img
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot B:\Various\Nokia\TWRP\twrp.img
downloading 'boot.img'...
OKAY [ 0.969s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.011s
fastboot flash recovery twrp.img
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery B:\Various\Nokia\TWRP\twrp.img
target reported max download size of 402653184 bytes
sending 'recovery' (42412 KB)...
OKAY [ 0.953s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.968s
So right now I'm at the end with my rudementary skills here.
Any idea how to get back to the point with twrp and installing an OS?
Thanks.
In case that no one else answers but someone else have the same problems , I write my solutions here.
.......
I got back to twrp by changing the slot in ADB
fastboot --set-active=a
unfortunately the restart loop doesn't end and no OS starts wether in slot a or b.

Categories

Resources