Trying to access recovery mode TWRP, but doing so I see my screen flashes and I can't see the recovery mode (or even download mode).
The LCD is still working but glitchy and broken, which may be the cause.
Is there a way to mirror my phone's screen via a janky solution to a PC or even trying to fix such thing?
Related
I have a nexus s i9020t with bootloader unlocked and stock JB unrooted.
I dropped the phone on the floor and now cannot boot, stuck on X screen animation and touch controls (soft buttons) are NOT lighting up.
I can boot in bootloader and recovery though and fastboot detects device.
But adb cannot detect it. As USB debugging was off.
How to mount sdcard to rescue data before I flash a new ROM.
Clockwork Recovrey
Well ...... I flashed clockwork touch recovery and mount SD card to backup data.
But after that I flashed stock rom and it still stuck at boot animation.
AND touch sensitive controls (soft buttons) are not lighting up.
:crying:
Anybody having a solution ??????
No TOUCH controls
UPDATE:
The CNA 3.5 ROM worked for me and now able to boot normally with my sdcard data still intact.
But still no capacitive touch controls. They dont even light up. The touchscreen though is working perfectly.
I've even checked the system/usr/keylayout/mtx224_ts_input.kl file and it also seems alright.
Now stuck with pressing power button to access nav bar of the ROM to perform any action.
Very painful indeed.Any suggestions?????
Sounds like a hardware fault. You'll need to send it back to Samsung for repair
bedalus said:
Sounds like a hardware fault. You'll need to send it back to Samsung for repair
Click to expand...
Click to collapse
Yes its indeed hardware fault. I think the PCB behind the touch keys is dead. Also handsfree not working.
Anyways, had to sacrifice a bit of real estate on the touch screen by turning on the nav bar.
rameezwajid said:
I have a nexus s i9020t with bootloader unlocked and stock JB unrooted.
I dropped the phone on the floor and now cannot boot, stuck on X screen animation and touch controls (soft buttons) are NOT lighting up.
I can boot in bootloader and recovery though and fastboot detects device.
But adb cannot detect it. As USB debugging was off.
How to mount sdcard to rescue data before I flash a new ROM.
Click to expand...
Click to collapse
enter in fastboot, flash CWM 6.1.0 the enter in the recovery go to mount and storage and finally mount usb storage, plug to your pc and BAM!
[EDIT]
sorry, didnt saw that u already done that with success
I have a S2 with a broken screen that had stock firmware installed (I don't remember which). I'm trying to gain access to the device to see if I can repurpose it for something else.
I tried following the guide here (http://forum.xda-developers.com/showthread.php?t=2786395)
I installed the adb/fastboot from here (http://forum.xda-developers.com/showthread.php?t=2786395)
I put the device in Download mode by pressing Vol UP/Vol DOWN and then plugging in the USB cable to a WinXP machine. On ODIN I can see COM6 light up, but if I run adb devices nothing shows up.
I think I'm missing a step somewhere. I think I need to get into recovery mode and not download mode, but I'm not able to do so without seeing the screen. I'm following what it says here (http://forum.xda-developers.com/showthread.php?t=1409769) but when trying to get into recovery mode it sounds like the phone just boots up instead.
Any suggestions? I think the goal is somehow enable usb debugging. I'm okay with losing the data on the device.
Not sure what's going on. Has anybody ever encountered this issue? All drivers are properly installed.
My device is SM-T320. Tablet also does not charge; turns on only when connected to PC or power outlet. I cannot enter recovery mode either (which is what I want to do, and which is why I want to get ADB working). I can only enter download mode; device does not load past the splash screen.
Thoughts, anyone? Cheers
Images: imgurDOTcom/a/brcxoTb (sorry, new user)
Okay so I tried to flash an older version of TWRP as the latest one didn't work and now my phone is broke. I can only hold the volume down and power keys to turn it on and off. However, once turned off u have to leave it for a bit to turn it on which only works when it is plugged into a charger. It gets stuck on the 'Galaxy s8+' screen and I cannot access download or recovery mode. What can I do about it? Samsung said they cannot fix it unless I get my smashed screen fixed as well which will cost
If you can get into download mode reflash stock rom ( take the tick out of the auto reboot in Odin ) when you get the pass notification reboot to receovery and do a full wipe of everything then reboot. It will take a while but eventually it should reboot
I can't get into download mode whatsoever lmao. Even with a micro usb rig, no luck
If your s8+ is dead and not able to fix i can use its lcd to repair my broken touch i shall pay 40$ for the dead phone both of us will be benefited
hhjkkh10 said:
I can't get into download mode whatsoever lmao. Even with a micro usb rig, no luck
Click to expand...
Click to collapse
On my Pixel 3, if it wouldn't boot to fastboot, you had to keep trying to boot to it. It's the same way you access download mode here.
Keep trying to access download mode, or take a gamble and try using adb to boot it to recovery/download.
guys please suggest a guide to use
phone was with custom firmware, twrp recovery, data encrypted with stock encryptor
only thing i did was to change a broken screen at repairs center
now it is in bootloop
i can get to download mode and to recovery (screens attached) but cant get a hold of device in download mode via fastboot (it hangs with waiting for device) although driver is installed and windows recognizes the phone
please advise
-=knop=- said:
guys please suggest a guide to use
phone was with custom firmware, twrp recovery, data encrypted with stock encryptor
only thing i did was to change a broken screen at repairs center
now it is in bootloop
i can get to download mode and to recovery (screens attached) but cant get a hold of device in download mode via fastboot (it hangs with waiting for device) although driver is installed and windows recognizes the phone
please advise
Click to expand...
Click to collapse
In my opinion this is more like a hardware problem. Something when replacing the screen damaged or not connected.