BLACKSCREEN Install Custom ROM? Screen mirroring with SCRCPY - Galaxy S 4 i9505 Android Development

Hello,
i want to install LineageOS 14.1 on my Samsung Galaxy S4, currently Android 5.0.1
My display is broken, but it still detects my finger, the phone is working. I managed to enable USB-Debugging and use SCRCPY to mirror my phone screen, so i can control it on my PC.
I think i managed to install TWRP, didnt test yet.
My question is: How can I install Custom Rom if i dont see anything? Does Screen mirroring work with adb sideload? If i install custom rom, USB Debugging gets deactivated?
Would it be helpful in any way to install TWRP app? By rooting it using Odin?
Any help is appreciated

Anyone pls?

You can possibly enter download mode and flash a TWRP, but I'm almost %100 sure that there is no way you can control TWRP with scrcpy or with any other screen mirroring app when your screen is broken. Maybe try CWM recovery and try to memorise the button patterns for installation on another android device, however, I'm not sure why would you do that.

Related

[Q] Broken screen. Accidentally deleted build.prop via ADB. Halp!

A few months ago i broke the screen on my N7. I put it in a drawer until I could order a new screen. Yesterday I decided to play with it a bit after finding the tool permitting use with a broken screen.
I could not get my computer or any other i tried to recognize the tablet while in Android. However, if I was in fastboot or recovery I could communicate with the device via ADB. I attributed the connections issues to not having USB Debugging enabled and not being able to unlock the screen. I proceeded to try and modify the build.prop via ADB until I came across some misinformation and mistakenly deleted the build.prop.
I need some help getting the tablet to a state where I can control it via the Android broken screen tool avaipable here on XDA.
Do you have an unlocked bootloader mate?
I believe so. It's been a while since I tinkered with the tablet, but I usually root and unlock all my devices. This Nexus 7 is running Cyanogenmod.
jconnell said:
I believe so. It's been a while since I tinkered with the tablet, but I usually root and unlock all my devices. This Nexus 7 is running Cyanogenmod.
Click to expand...
Click to collapse
Do you have a custom recovery or not? If you do, you can just dirty flash your ROM again
I do. It's running TWRP. Could you tell me more about a dirty flash?
Get the the tablet into the bootloader, flash just the system.img of whatever ROM is installed using fastboot, done.
Would it be possible to enable debugging and disable the lock screen in the system image before flashing? If not, possible to do it after?

Bricked Zenfone, Out of ideas

Hello everyone, need a little help if possible .
The say curiosity killed the cat, well… it killed my phone. To be more precise I wanted to know if my 550ml (with unlocked bootloader and running cm12.1) could run a 551ml firmware so… I did install thru TWRP the superzen firmware and after that the screen turned black. Can’t see anything . Not even in fastbootmode, no logo, no nothing. If I turn it on and plug it to the pc it shows, I see the internal memory and the sdcard. It’s gotta be from the different resolution that 550 and 551 have but how do I change it since I can’t see anything?
I did a userdata reset thru fastboot, wiped cache , reinstalled stock recovery ,boot recovery, tried to install stock firmware, still no change. I even managed to enter stock recovery and did an adb sideload of the latest firmware from the asus site.
As for now the phone boots, the capacitive buttons respond, the led indicates that it charges, the pc sees it but no matter what I do the screen remains black. Most likely I’m on the setup wizard but like I said I don’t see anything.
So… What can I do now? To the Asus service with it or …?
I'm not much of a forum user so go easy on me. Thank you.
Not sure if it's going to make a difference but here is an idea, try sideloading a cm recovery and flash a cm rom and see what it does...
fastmix said:
Not sure if it's going to make a difference but here is an idea, try sideloading a cm recovery and flash a cm rom and see what it does...
Click to expand...
Click to collapse
Unfortunately it does not work, when i try to sideload a rom with twrp it gives this: error closed. Probably because usb debugging is not enabled... and in cwm different error: Device unauthorized...
Are you sure bootloader is unlocked?
It has to be unlocked cause i can flash permanent TWRP and when I enter TWRP recovery i can touch the buttons, even tried to do a restore in the dark... But nothing... Still the black screen persists... Thank you anyways.
PS: Well it looks like I've managed to resolve my problem. Thanx to user helroz i have found in his google drive a Raw firmware and I was able to flash it via fastboot with Asus Flash tool and now the phone booted, no more black screen for me. Lesson learned.

Tab S 8.4 Stuck in recovery loop

Hi Folks,
I have a Tab S 8.4 wifi that I seem to have broken. I was attempting to restore the stock Marshmallow rom and something has gone horribly wrong. This is what I did:
1. I installed the latest stock rom by Odin and booted
2. I then downloaded and installed CF auto root/TWRP for the SM-T700, however, I failed notice that I had left NAND erase checked in the Odin settings so now all I get is the device attempting boot into TWRP which doesn’t work.
The device won’t turn off to allow me to use the buttons to access download mode which I know is what I need. I have tried draining the battery completely but as soon as power is restored it attempts to boot into the failed recovery again and is, in effect, stuck on the TWRP screen, periodically flashing the screen. It its broken TWRP state, the computer recognises it as a USB MTP device but will not recognise with the correct drivers to allow me to use ADB to force it into the download.
Does anybody have any suggestions? Otherwise I have a £250 paperweight!
unsrm said:
Hi Folks,
I have a Tab S 8.4 wifi that I seem to have broken. I was attempting to restore the stock Marshmallow rom and something has gone horribly wrong. This is what I did:
1.I installed the latest stock rom by Odin and booted
2.I then downloaded and installed CF auto root/TWRP for the SM-T700, however, I failed notice that I had left NAND erase checked in the Odin settings so now all I get is the device attempting boot into TWRP which doesn’t work.
The device won’t turn off to allow me to use the buttons to access download mode which I know is what I need. I have tried draining the battery completely but as soon as power is restored it attempts to boot into the failed recovery again and is, in effect, stuck on the TWRP screen, periodically flashing the screen. It its broken TWRP state, the computer recognises it as a USB MTP device but will not recognise with the correct drivers to allow me to use ADB to force it into the download.
Does anybody have any suggestions? Otherwise I have a £250 paperweight!
Click to expand...
Click to collapse
The file you flashed doesn't work on Marshmallow.
Use the updated twrp and supersu in the dev section.
ashyx said:
The file you flashed doesn't work on Marshmallow.
Use the updated twrp and supersu in the dev section.
Click to expand...
Click to collapse
Thanks for the reply ashyx, I don't current have a way to achieve that as I cannot access download mode. Any suggestions on how to do that?
unsrm said:
Thanks for the reply ashyx, I don't current have a way to achieve that as I cannot access download mode. Any suggestions on how to do that?
Click to expand...
Click to collapse
You can access download mode anytime irrespective of the current state the device is in.
Hold POWER + HOME + VOL DOWN until the device boots in to download mode.
ashyx said:
You can access download mode anytime irrespective of the current state the device is in.
Hold POWER + HOME + VOL DOWN until the device boots in to download mode.
Click to expand...
Click to collapse
I did't realise it would work in any mode!
Thought I'd tried it but obviously not held long enough.
You are a star! Thank you so much.
Chris

[Q] Bricked Gpad 8.3 - stock rom via LG Flash Tool not working

So. Recently, I got CyanogenMod 13 on my Gpad. Everything was just fine. Then I installed the Magisk Manager, which, for some reason, disabled the root access on the device. When I uninstalled it, my recovery (TWRP) asked me, if I want to install SuperSU. I selected yes. And that's the moment when everything fcked up. After SuperSU installation, my tablet went into bootloop, and I wasnt't even able to enter recovery via button combination. I tried to flash the stock rom via LG Flash Tool, but failed miserably. I tried multiple stock roms, but the result is till the same: I can't access the Factory Reset via buttons, the system keeps rebooting, and even if it boots for few seconds, the touchscreen isn't responding. I even tried connecting mouse via USB otg, but no success. Is my tablet dead? Is there any chance of repairing it?
Thank you for your help.
EDIT: It's v500 European version.
Czechball said:
So. Recently, I got CyanogenMod 13 on my Gpad. Everything was just fine. Then I installed the Magisk Manager, which, for some reason, disabled the root access on the device. When I uninstalled it, my recovery (TWRP) asked me, if I want to install SuperSU. I selected yes. And that's the moment when everything fcked up. After SuperSU installation, my tablet went into bootloop, and I wasnt't even able to enter recovery via button combination. I tried to flash the stock rom via LG Flash Tool, but failed miserably. I tried multiple stock roms, but the result is till the same: I can't access the Factory Reset via buttons, the system keeps rebooting, and even if it boots for few seconds, the touchscreen isn't responding. I even tried connecting mouse via USB otg, but no success. Is my tablet dead? Is there any chance of repairing it?
Thank you for your help.
EDIT: It's v500 European version.
Click to expand...
Click to collapse
nope, it's not death (yet)... The buttoncombo to enter might be a problem, but keep trying. If really nothing goes, try connecting to your PC and open a commandline. Type : adb reboot recovery (preferably from a linuxbox). However, make sure you got a ROM, GApps and SU system 2.78 or 2.79 ready on the SD. Personally I recommend @adrianom AOSP 7.1.1, OpenGApps micro and SU 2.79 SR2'systemmode.
Cheers
dirlan2001 said:
nope, it's not death (yet)... The buttoncombo to enter might be a problem, but keep trying. If really nothing goes, try connecting to your PC and open a commandline. Type : adb reboot recovery (preferably from a linuxbox). However, make sure you got a ROM, GApps and SU system 2.78 or 2.79 ready on the SD. Personally I recommend @adrianom AOSP 7.1.1, OpenGApps micro and SU 2.79 SR2'systemmode.
Cheers
Click to expand...
Click to collapse
Thank you for your reply.
However:
I am not able to stay in the system.
I am not able to enter the recovery. (because of the brick)
I am not able to enter ADB, because there's just no way how. I have USB debugging disabled by default (because I tried to reset the system using LG Flash Tool) and I can't use ADB in the download mode.
Actually, download mode is the only thing that hasn't broke yet. I still hope that someone that has experienced similar problems help me.
But again, thanks for your (and the only) reply.
Czechball said:
Thank you for your reply.
However:
I am not able to stay in the system.
I am not able to enter the recovery. (because of the brick)
I am not able to enter ADB, because there's just no way how. I have USB debugging disabled by default (because I tried to reset the system using LG Flash Tool) and I can't use ADB in the download mode.
Actually, download mode is the only thing that hasn't broke yet. I still hope that someone that has experienced similar problems help me.
But again, thanks for your (and the only) reply.
Click to expand...
Click to collapse
If you can get into download, you could connect to a PC and start the LG-tools.Use that to restore to the original ROM and start allover again with latedt software (TWRP, ROM, SU)
Cheers

Question [SOLVED] download mode doesnt display any text/not working

Hi, dumb me skipped a step on the Pixel Experience ROM and didnt update trwp (I think this was the reason why it happened) I already flashed various gsis before and didnt had a significant issue but after flashing this, each time the phone boots all i see is the blue screen with "Secure Check Fail : Modem" on a corner.
When flashing a previous gsi via twrp the same error displays, and if I try to get into the download mode then there is nothing there, just the blue screen.
Please I need help with this, the phone wasn´t rooted, I just use twrp for the GSIs. without download mode i dont know how to install the firmware or use odin at all.
btw I can still get to twrp
Hi, sorry for that. We've actually found a fix for that issue already, but it seems like the PixelExperience build you flashed didnt have it yet.
If I'm not wrong download mode should still work fine, even though it shows "nothing" except from that blue screen.
Please try to boot into download mode, then press volume up to get into actual download mode and see if Odin detects your phone, and if it does then flash the latest version of your stock ROM again.
After that installing PixelExperience should work just fine.
thank you very much!

Categories

Resources