So here is what I am stuck:
I have a SM-G9208 international edition. I have been working around and finally managed to get TWRP flashed using ODIN and boot into recovery. the problem is that the touch screen does not work for some reason.
So I am looking for a recovery that does not require touch screen. I was hoping to find a recovery that I can flash through ODIN and only uses physical buttons. Does any know where I can find such a thing?
Hey mate. I was searching for Philz for some time - go for it http://arter97.com/browse/exynos7420/kernel/4.3/. This guy has it for probably all models. And buttons are apparently working.
On the other hand you flashed the correct TWRP?
davebugyi said:
On the other hand you flashed the correct TWRP?
Click to expand...
Click to collapse
How many versions of TWRP exists? I only found one version on the official website:
https://dl.twrp.me/zeroflte/
the last file (twrp-2.8.7.1-zeroflte.img.tar) is the one that actually successfully boots into recovery but after that no-touch problem exists. the rest do not work.
Saafir said:
Could try OTG cable with a mouse.
Click to expand...
Click to collapse
I never thought of that. Does TWRP support mouse out of the box or special build of TWRP is needed?
Saafir said:
Yep, TWRP supports it. Should be fine. Had to do it on a G2 with a broke screen
Click to expand...
Click to collapse
It indeed worked. now I can actually do things in TWRP using USB OTG mouse. But there is a new problem: once I use mouse in TWRP, the phone gets stuck in a boot loop after I exit TWRP The only fix is to flash the full image using ODIN
For whoever that may come across this:
TWRP does allow you to work through adb command shell. boot into recovery, attach to your laptop and do:
adb devices
once you get a response do:
adb shell
and then you can do all kind of stuff like:
twrp install filename
twrp backup
twrp restore
I have the same problem but instead like a dumb ass I installed twrp twice and it messed up my screen each time I touch to the right it touches to the left and left is right. So does anybody have a costum recovery or a stock recovery for SM-G920T1 or SM-G920T
Related
TeamApexQ is proud to release TWRP (from our OmniToad builds) for general use.
Current release: 2.8.1.0_0001
Raw image (for heimdall/Crazy 'cat'ing):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.img
md5: https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.img.md5sum
update.zip format (Recovery flashable/sideloadable):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.zip
md5: https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.zip.md5sum
ODIN compatible tarball format (ODIN):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.tar.md5
Please let us know of any other issues. Also with any other issues, please include a copy of your recovery.log, and dmesg from the TWRP session.
Thanks for your work TeamApexQ!
Sent from my SGH-T699 using XDA Premium 4 mobile app
falle21 said:
Thanks for your work TeamApexQ!
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nice...Will be building some twrp themes just for the Relay 4G....glad you guys built it as ive been pretty busy
The work around for the "failed" flash. Unmount system in the "mount" menu prior to doing any flashing of zips. Even I have to do this on the G2 with TWRP 2.6.3.4.
Sent from my LG-VS980 using Tapatalk 4
New build posted in the OP!
Will now flash old Android builds (I've tested with every build I could get my hands on.)
I've never used TWRP, how does it differ from CWM for Backups ?
Are my CWM "nandroid" backups cross compatible ? I have Carbon, Omni and CM11 backups ready to switch at any time for testing in .tar format.
No twrp backups differ from cwm...however Philz can handle twrp and cwm backups...however and in my opinion twrp can do a lot more as a recovery than any other recovery...one thing you can do...and is a slight pain...is boot the backup with cwm or philz. flash twrp and re backup that ROM in twrp then delete the old one...repeat for all backups
Sent from my ADR6425LVW using xda app-developers app
REV3NT3CH said:
No twrp backups differ from cwm...however Philz can handle twrp and cwm backups...however and in my opinion twrp can do a lot more as a recovery than any other recovery...one thing you can do...and is a slight pain...is boot the backup with cwm or philz. flash twrp and re backup that ROM in twrp then delete the old one...repeat for all backups
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
hmm yea ... or switch between recoveries restore w/ cwm, install twp, reboot re-create backup .. repeat.
Is there a fix permissions in twrp ? and is usb mounting in windows ? I found I didn't have the functionality of either with the latest CWM
yohan4ws said:
hmm yea ... or switch between recoveries restore w/ cwm, install twp, reboot re-create backup .. repeat.
Is there a fix permissions in twrp ? and is usb mounting in windows ? I found I didn't have the functionality of either with the latest CWM
Click to expand...
Click to collapse
thats what i was refferring too for saving your backups and restorable via twrp....and yes to all the other questions...twrp can do so many things while in recovery...for example..say you downloaded a rom from phone and forgot to put it in root of sdcard...twrp has a file manager with copy and paste functionalities to do so...it supports adb sideloading, mounting for both windows and linux, permissions, much better and clearer wiping method...all touchscreen...very themable for example http://forum.xda-developers.com/showpost.php?p=45122951&postcount=1 i made this theme specifically for my htc rezound as well as many others...which ill more than likely port to the relay as it has to match screen dimensions for resolution...overall it just has a bulk of many great options for a recovery and is very easy to use and get used to
New build posted in the OP. Small bugfixes in this release. (Including some SELinux and settings fixes.)
Did something wrong. How to fix?
Magamo said:
TeamApexQ is proud to release TWRP (from our OmniToad builds) for general use.
Current release: 2.7.0.0_0002
Raw image (for heimdall/Crazy 'cat'ing):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.7.0.0_0002.img
Click to expand...
Click to collapse
I wanted to install this version of twrp on my apexqtmo using heimdall under linux.
I booted into "download" mode, connected my USB table to my linux box, and I then stupidly flashed the wrong twrp module by mistake (for a different phone).
Without realizing my mistake, I then rebooted. I ended up back in my OS, and then, using the Power Menu, I booted into recovery mode. I got the blue text saying RECOVERY BOOTING.... , but after that, the screen remained black.
From then on, I cannot boot into the normal OS, nor into "download" mode.
Even if I remove the battery and then perform a standard boot using the power button alone, I get the blue text saying I'm booting into recovery, and the dead, black screen shows up.
I want to boot into the OS or download mode, but I can no longer do either. No matter what combinations of Volume-Up, Volume-Down, Home, and Power that I press, I always get back to RECOVERY BOOTING...., and I can't get into download mode again, no matter what.
Did I brick my phone?
If not what can i do to fix it?
Thanks for any help.
.
The only way to clear the reboot mode is to either trigger a different mode or complete the boot. If key combinations don't work, you can try to see if the device comes up in adb and then you can "reboot bootloader" failing that you can trigger download mode with a resistor on the usb port. Google galaxy s 3 jig to find out how to make one or buy one
Sent from my Nexus 7 using Tapatalk
Nardholio said:
The only way to clear the reboot mode is to either trigger a different mode or complete the boot. If key combinations don't work, you can try to see if the device comes up in adb and then you can "reboot bootloader" failing that you can trigger download mode with a resistor on the usb port. Google galaxy s 3 jig to find out how to make one or buy one
Click to expand...
Click to collapse
Thank you very much!
... and I fixed it!!!!
Your adb suggestion led me to the solution ...
I tried adb, but it didn't work.
However, after that adb attempt, the usb cable was still plugged into my device from my linux box, and I noticed that the device was in some sort of boot loop. The device kept giving short vibrations every few seconds.
At that point, I tried one more key combination that I hadn't thought of before: with the cable still plugged in, I held down Volume-down and Home without pressing the Power button ... because I guessed that the existence of the boot loop means that power might already be on, which would cause the power key to be unnecessary.
And my guess was correct: I got into Download mode!
I flashed the correct version of TWRP, and now all is well.
Thank you again for providing the suggestion that led me to my solution!
Also, thank you for telling me about the jig. I'm now going purchase one anyway, just in case I screw up again in the future. I think I can get one for $8 or less (I'm too lazy and clumsy to try to make one on my own).
.
It's weird, but I had the same experience with the blue "RECOVERY BOOTING" followed by dead phone as described a couple posts ago... and I was flashing the correct file, the twrp zip in the OP, from recovery (cwm 6.0.3.7). I did it twice and got the same bad result.
To get around the bad dead phone result, I held volume down and power for 15 seconds, got into download mode, and then selected volume down to allow the phone to boot normally. Once it did, I went to the Play store and installed an app that could flash another recovery (cwm 6.0.4.5). Which worked.
I will try flashing the .img file and see if that works, but I'm kinda perplexed why the twrp zip didn't work from recovery...
Sent from my Nexus 5 using Tapatalk
reaper000 said:
I will try flashing the .img file and see if that works, but I'm kinda perplexed why the twrp zip didn't work from recovery...
Click to expand...
Click to collapse
You indeed have to flash the .img file, at least if you're installing from the command line using heimdall.
.
Ended up successfully flashing the .img file with recovery tools app from play store. Thanks all!
Sent from my Nexus 5 using Tapatalk
reaper000 said:
Ended up successfully flashing the .img file with recovery tools app from play store. Thanks all!
Click to expand...
Click to collapse
Glad it worked.
Also, FYI: you can't flash a recovery from within recovery. This is why your earlier attempt to flash the .zip from within recovery didn't work.
As far as I know, you have to be in bootloader mode (also called "download" mode) in order to flash a recovery. You have to boot into that mode and use somthing like heimdall to install the .img file. There are also tools you can use which will flash a recovery from a .zip file, but they actually just extract the .img file from the .zip file and then load that .img file via bootloader mode.
.
HippoMan said:
Glad it worked.
Also, FYI: you can't flash a recovery from within recovery. This is why your earlier attempt to flash the .zip from within recovery didn't work.
As far as I know, you have to be in bootloader mode (also called "download" mode) in order to flash a recovery. You have to boot into that mode and use somthing like heimdall to install the .img file. There are also tools you can use which will flash a recovery from a .zip file, but they actually just extract the .img file from the .zip file and then load that .img file via bootloader mode.
.
Click to expand...
Click to collapse
The .zip file provided here CAN be flashed from within recovery. What likely happened was a bad download.
Magamo said:
The .zip file provided here CAN be flashed from within recovery. What likely happened was a bad download.
Click to expand...
Click to collapse
Yeah, was thinking bad download, but I dl'd it twice. And there was no MD5 checksum that I could see
Sent from my Nexus 5 using Tapatalk
reaper000 said:
Yeah, was thinking bad download, but I dl'd it twice. And there was no MD5 checksum that I could see
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Actually, which version of CWM were you using to attempt to install this from? Likely significantly old versions were not set up to flash recovery properly.
so i just flashed 2.8.7.0 with flashify (probably my culprit) at work ... no way to a usb cable/cannot hook phone to a work PC (gov)
now phone boots into bootloader, power down and recovery only, i can perform functions within recovery, but everytime i reboot it goes to recovery
anyone have any ideas? Im dead in the water now
-4ndr01d- said:
so i just flashed 2.8.7.0 with flashify (probably my culprit) at work ... no way to a usb cable/cannot hook phone to a work PC (gov)
now phone boots into bootloader, power down and recovery only, i can perform functions within recovery, but everytime i reboot it goes to recovery
anyone have any ideas? Im dead in the water now
Click to expand...
Click to collapse
I don't see a 2.8.7.0 on the TWRP site.
I do however see a 2.8.5.0
are you sure you are using the correct one?
their could be a M8 2.8.7.0 I just can't find it.
EDIT: nvm sorry, I see it now here:
http://forum.xda-developers.com/showthread.php?t=2717928
Wish I could be of help, sorry friend.
I fixed myslef. luckily I had a few versions of the kernel i was runnning. so i flashed one of those and everything worked fine.
Im sure its flashify's fault. seems like it flashed to both the boot and recovery partition
need to stay away from apps to flash recovery lol. just use fastboot
-4ndr01d- said:
I fixed myslef. luckily I had a few versions of the kernel i was runnning. so i flashed one of those and everything worked fine.
Im sure its flashify's fault. seems like it flashed to both the boot and recovery partition
need to stay away from apps to flash recovery lol. just use fastboot
Click to expand...
Click to collapse
Glad you got it fixed!
I agree, I only use fastboot when it comes to things such as recovery
Hello guys. I need your help badly.
I am using Galaxy Grand Prime smg530h
The problem is when I push the power button, my phone automatically boots to recovery mode which is Twrp, yeah I was my only problem last time. I guess I wipe something using twrp, my phone says "NO OS INSTALLED" . Then I googled some ways to fix so I installed a custom rom using twrp. I though my problem was solved but still when I turn on my phone it automatically boots recovery. I googled again and did something. But a big problem shows up, When I turn on my phone, it boots automatically to twrp but after the samsung logo flashes, black screen appears. Its just blank but the my phone black light is on and I think im on twrp since everytime I touch the screen it vibrates.
Please help me
Htxenuj said:
Hello guys. I need your help badly.
I am using Galaxy Grand Prime smg530h
The problem is when I push the power button, my phone automatically boots to recovery mode which is Twrp, yeah I was my only problem last time. I guess I wipe something using twrp, my phone says "NO OS INSTALLED" . Then I googled some ways to fix so I installed a custom rom using twrp. I though my problem was solved but still when I turn on my phone it automatically boots recovery. I googled again and did something. But a big problem shows up, When I turn on my phone, it boots automatically to twrp but after the samsung logo flashes, black screen appears. Its just blank but the my phone black light is on and I think im on twrp since everytime I touch the screen it vibrates.
Please help me
Click to expand...
Click to collapse
Have you tried to re-install everything including your recovery? Perhaps even your bootloader or try to flash your ROM manually from fastboot or adb.
RAZERZDAHACKER said:
Have you tried to re-install everything including your recovery? Perhaps even your bootloader or try to flash your ROM manually from fastboot or adb.
Click to expand...
Click to collapse
Hmm. Can you show me a guide sir? On reinstalling? 'cos I dont know what to do since I am stuck on a blank screen.
Htxenuj said:
Hmm. Can you show me a guide sir? On reinstalling? 'cos I dont know what to do since I am stuck on a blank screen.
Click to expand...
Click to collapse
There is already a guide available for how to flash stock rom, which you can check out here. You can get the stock rom from sammobile, the official samsung firmware resource which you can check out here.
Good luck!
Edit: You can then try to reflash twrp and if it doesn't work, post about it in the twrp thread for your device.
RAZERZDAHACKER said:
Have you tried to re-install everything including your recovery? Perhaps even your bootloader or try to flash your ROM manually from fastboot or adb.
Click to expand...
Click to collapse
Samsung doesn't use fastboot, they use download mode and flash with Odin. Be familiar with these kinds of specifics about a device if you're going to give advice, otherwise you might tell someone something very wrong unintentionally.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Samsung doesn't use fastboot, they use download mode and flash with Odin. Be familiar with these kinds of specifics about a device if you're going to give advice, otherwise you might tell someone something very wrong unintentionally.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Adb: Recover > Update from ADB
Fastboot: Boot to download mode > fastboot access on most devices (confirmed on my S4)
RAZERZDAHACKER said:
Adb: Recover > Update from ADB
Fastboot: Boot to download mode > fastboot access on most devices (confirmed on my S4)
Click to expand...
Click to collapse
adb works on Samsung, fastboot does not.
Sent from my SM-S903VL using Tapatalk
RAZERZDAHACKER said:
Have you tried to re-install everything including your recovery? Perhaps even your bootloader or try to flash your ROM manually from fastboot or adb.
Click to expand...
Click to collapse
How can I boot to Download mode since I am stuck at blank screen?
Htxenuj said:
How can I boot to Download mode since I am stuck at blank screen?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=gYA3ZMlDO3Q
Htxenuj said:
Hello guys. I need your help badly.
I am using Galaxy Grand Prime smg530h
The problem is when I push the power button, my phone automatically boots to recovery mode which is Twrp, yeah I was my only problem last time. I guess I wipe something using twrp, my phone says "NO OS INSTALLED" . Then I googled some ways to fix so I installed a custom rom using twrp. I though my problem was solved but still when I turn on my phone it automatically boots recovery. I googled again and did something. But a big problem shows up, When I turn on my phone, it boots automatically to twrp but after the samsung logo flashes, black screen appears. Its just blank but the my phone black light is on and I think im on twrp since everytime I touch the screen it vibrates.
Please help me
Click to expand...
Click to collapse
i have 2 of this devices,they all go to same trouble,never show twrp. no change no picture just blank (seems grey into black)
Suryo75 said:
i have 2 of this devices,they all go to same trouble,never show twrp. no change no picture just blank (seems grey into black)
Click to expand...
Click to collapse
It fix by using cwm, twrp is not compatible with twrp especially g530h which is has xxu based
Suryo75 said:
It fix by using cwm, twrp is not compatible with twrp especially g530h which is has xxu based
Click to expand...
Click to collapse
Can you help with a working link for CWM for 530H? I cant seem to find anything apart from TWRP
dv8ted said:
Can you help with a working link for CWM for 530H? I cant seem to find anything apart from TWRP
Click to expand...
Click to collapse
Just visit link with quote cwm for g530h
dv8ted said:
Can you help with a working link for CWM for 530H? I cant seem to find anything apart from TWRP
Click to expand...
Click to collapse
CWM is a dead project, it is no longer supported, that is why you are only finding TWRP. If you want custom recovery, use TWRP, it is a much better recovery than CWM anyway.
Sent from my LGL84VL using Tapatalk
dv8ted said:
Can you help with a working link for CWM for 530H? I cant seem to find anything apart from TWRP
Click to expand...
Click to collapse
try this
Is their any solution to use twrp on g530h xxu based?
On flashing many custom roms through cwm, their is nothing on screen but gray broken lines.
Please help if anyone have it's solution.
Here is a beta working TWRP for V60.
Do NOT flash until you have a complete backup of your phone.
Flash at your own risk, you been warned
If and when you do flash it report back with bugs, what works what doesnt and what variant you used it on. helps with getting a better working recovery and fixing bugs
TWRP_LG_V60_BETA_2.0.img.7z
drive.google.com
tested on tmobile variant so far flashing and usb storage works, BUT backup system fails and does not reboot system. only reboots back to twrp, touch screen works on the first time use. If the screen times out and blacks out, you push on the power button to wake up the screen But the touch screen stops working. until the force reboot again. flashed stock abl_a and stock recovery but didnt go back to stock until you flash your stock boot.img.
blaze2051 said:
tested on tmobile variant so far flashing and usb storage works, BUT backup system fails and does not reboot system. only reboots back to twrp, touch screen works on the first time use. If the screen times out and blacks out, you push on the power button to wake up the screen But the touch screen stops working. until the force reboot again. flashed stock abl_a and stock recovery but didnt go back to stock until you flash your stock boot.img.
Click to expand...
Click to collapse
doesn't work with v60 ATT,boots in recovery ,but touch screen not working . (first attempt screen time was out ,but 2nd attempt booted in twrp while screen was on)
Karol75 said:
doesn't work with v60 ATT,boots in recovery ,but touch screen not working . (first attempt screen time was out ,but 2nd attempt booted in twrp while screen was on
Click to expand...
Click to collapse
So no touch screen functionality with att, got it thanks
i noticed that touch doesnt work if boot via commands touch only works with button combo
Could we get some info on where exactly to install this img to? Do we install to boot_a, boot_b or both?
MrHomebrew said:
Could we get some info on where exactly to install this img to? Do we install to boot_a, boot_b or both?
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
And the version listed above is certainly not current. TWRP 3.6.0-11 can be found on TG. Hopefully you know your way around Qfil.
hooutoo said:
fastboot flash recovery recovery.img
And the version listed above is certainly not current. TWRP 3.6.0-11 can be found on TG. Hopefully you know your way around Qfil.
Click to expand...
Click to collapse
(update) never mind i took care of it
you should provide a link instead if thats the case
So I wanted to make a backup using TWRP but apparently TWRP itself just didn't work.
So my main issue is that pressing almost anything doesn't give an input (Install works fine while Wipe only works when pressing but the actual UI is broken and I can't go back).
So at this point my phone is stuck in a TWRP bootloop since I cannot press the reboot option. Also, I tried flashing TWRP again and it didn't work. What should I do?
salamianchoivy said:
So I wanted to make a backup using TWRP but apparently TWRP itself just didn't work.
So my main issue is that pressing almost anything doesn't give an input (Install works fine while Wipe only works when pressing but the actual UI is broken and I can't go back).
So at this point my phone is stuck in a TWRP bootloop since I cannot press the reboot option. Also, I tried flashing TWRP again and it didn't work. What should I do?
Click to expand...
Click to collapse
When you connect via adb, then you can execute the commands described in the FAQ for TWRP and all other commands available in the shell.
Which version of TWRP are you using? The latest official one doesn't want to install for me, because it's 1MB larger than the actual recovery partition - could this have something to do with the strange behaviour?