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
Related
Well, after trying to install a ROM through TWRP the phone rebooted and froze on the HTC screen. I then go back into bootloader and try to get into recovery but the splash screen pops up and then the phone reboots. I can get into CWM however when trying to sideload any .zips there I get an error. Not really sure what to do at this point. I probably should have stopped playing with it when I fixed it the first time, ha.
Edit: I fixed my problems! Very happy, ended up restoring some of the firmware from the OTA's and TWRP started working again. Just flashed ROM and fully functionally.
Tim3worx said:
Well, after trying to install a ROM through TWRP the phone rebooted and froze on the HTC screen. I then go back into bootloader and try to get into recovery but the splash screen pops up and then the phone reboots. I can get into CWM however when trying to sideload any .zips there I get an error. Not really sure what to do at this point. I probably should have stopped playing with it when I fixed it the first time, ha.
Edit: I fixed my problems! Very happy, ended up restoring some of the firmware from the OTA's and TWRP started working again. Just flashed ROM and fully functionally.
Click to expand...
Click to collapse
which ota did you flash? what network provider you on? im having same problems, did you flash ota in twrp?
tr1gg3r84 said:
which ota did you flash? what network provider you on? im having same problems, did you flash ota in twrp?
Click to expand...
Click to collapse
My provider is AT&T. I used the UK OTA from this link http://db.tt/LrIEemZ4 . Its part of this thread in general http://forum.xda-developers.com/showthread.php?t=2422885. Basically what was happening is that I had flashed a ROM which didn't work out and so it would just hang on the white HTC screen. I figured no big deal I'll just go into recovery and flash another one I know works. That didn't work out. Any time I tried to go into recovery the TWRP splash screen would pop up for a second then the phone would reboot. Which kind of had me puzzled because I flashed ClockWorkMod for recovery and it would at least get me into recovery but still adb sideload was giving me errors so I flashed TWRP again even though it wasn't working either.. I pulled the boot.img out of the Firmware.zip in the OTA and flashed that with fastboot. At that point I had tried just about everything and was about to give up but to my surprise that seemed to fix it. I was able to go into recovery no problem. Sideloaded the ROM and everything went great. I'll probably not be messing with my phone like that for a bit haha. It was the second night in a row that I had wiped an OS off the phone and struggled to figure out how to get it working. Glad its all good now though. Good luck to you!
cant change recovery / device rebooting
Hi, i have a similar problem,
I've unlocked with htcdev everything is fine.
Then I installed Twrp-2.6.0.0.img as recovary.
I'm not able to mount the internal storage, so I had to push the ROMs via ADB.
starting a ROM 1st time seems to be ok.
restart is also ok.
shutdown and power on is rebooting every ~15sec.
I tried to change my bootloader.
fastboot flash recovery recovery-clockwork-touch-6.0.3.6-m7ul.img -> volume keys are responding
fastboot boot recovery-clockwork-touch-6.0.3.6-m7ul.img -> volume keys are NOT responding
recovery isn't starting until i run following commands:
fastboot flash recovery Twrp-2.6.0.0.img -> volume keys are responding
fastboot boot Twrp-2.6.0.0.img -> volume keys are NOT responding
but after resetting the device + entering recovery it's there
thanks for your ideas/help
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
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
Update 1/2/18 : Removed link until we get a Restore that works across all device's.
This will will help you restore back to a clean OS install using Twrp.
1.Download Files to your computer Unzip and place "Stock Restore 123017" Folder in a folder Named "TWRP".
2.Move TWRP folder you created and place them on your Phone's SD Card or Push them using adb command
Code:
adb push TWRP /TWRP
3. While in Twrp recovery click Restore and navigate to the back up folder.
4. Restore all and reboot. First boot will take a couple of mins so give it time.
This should bring you back up from the dead.
Edit:
If you accidentally flashed Twrp in the wrong slot then only restore boot using this back up.
This should Fix any wifi issues you may be having.
https://mega.nz/#!ogclRKCL!YmOMbkhR8oc5MUdxUupdwxRe7BHJGUXRZnal5rW2S_w
Awesome, thanks again! Glad to see your ontop of things in the development of this phone!
@Xshooter726
Can this be used to rebrand the carrier version? Three are still slacking with the second update which I feel is affecting the camera and want to resolve it myself now dees has blessed us with recovery
I restored using your back up but the phone just stays booting for 10 mins plus and I have a warning with "Your device is corrupt"
PupPupG said:
I restored using your back up but the phone just stays booting for 10 mins plus and I have a warning with "Your device is corrupt"
Click to expand...
Click to collapse
What slot did you restore to? and is the message of corruption in TWRP?
PupPupG said:
I restored using your back up but the phone just stays booting for 10 mins plus and I have a warning with "Your device is corrupt"
Click to expand...
Click to collapse
Getting the same thing unfortunately. Might have to wait for the factory images.
CptClubs said:
@Xshooter726
Can this be used to rebrand the carrier version? Three are still slacking with the second update which I feel is affecting the camera and want to resolve it myself now dees has blessed us with recovery
Click to expand...
Click to collapse
Not sure. I don't have a carrier version to test it with.
fivearcosstheeye said:
Getting the same thing unfortunately. Might have to wait for the factory images.
Click to expand...
Click to collapse
Can you run Md5 check sum? I think my upload may have been interrupted.
MD5 Should match this
fe23d7ebb04818e5f3d661e5b67acee0
Xshooter726 said:
Can you run Md5 check sum? I think my upload may have been interrupted.
MD5 Should match this
fe23d7ebb04818e5f3d661e5b67acee0
Click to expand...
Click to collapse
Ran a check and the upload was correct. I've tried restoring the backup to both A & B but neither would work. I'm using a Three branded Razer Phone so it might just be something to do with that?
PupPupG said:
Ran a check and the upload was correct. I've tried restoring the backup to both A & B but neither would work. I'm using a Three branded Razer Phone so it might just be something to do with that?
Click to expand...
Click to collapse
Hmmm that maybe why. I was running the latest update when I did the back up and Three branded phones haven't received the latest update yet. Looks like Three branded phones will have to wait for Official Images. Sorry guys
..Well Unless someone with a clean os installed on a three branded phone does a back up similar to mine then that should work.
PupPupG said:
I restored using your back up but the phone just stays booting for 10 mins plus and I have a warning with "Your device is corrupt"
Click to expand...
Click to collapse
Xshooter726 said:
Hmmm that maybe why. I was running the latest update when I did the back up and Three branded phones haven't received the latest update yet. Looks like Three branded phones will have to wait for Official Images. Sorry guys
..Well Unless someone with a clean os installed on a three branded phone does a back up similar to mine then that should work.
Click to expand...
Click to collapse
I don't have a branded carrier version. Going to try a couple more things and if that don't work we'll have to wait for factory images or a custom rom.
When restoring using TWRP, we're supposed to include the 'Vendor' options as well as part of the restoring process? I also restored in both slots.
I have a feeling I just made a very expensive mistake when I tried restoring - left out the 'Vendor' (bottom two) and now it's been on the booting animation for a good 30mins. Can't force shut off by holding the power button or using the vol dwn + pwr to get into download mode. Holding vol up+pwr will get me the 'Razer powered by Android' splash screen and then it just goes back into the animation.
BakaSenpai said:
When restoring using TWRP, we're supposed to include the 'Vendor' options as well as part of the restoring process? I also restored in both slots.
I have a feeling I just made a very expensive mistake when I tried restoring - left out the 'Vendor' (bottom two) and now it's been on the booting animation for a good 30mins. Can't force shut off by holding the power button or using the vol dwn + pwr to get into download mode. Holding vol up+pwr will get me the 'Razer powered by Android' splash screen and then it just goes back into the animation.
Click to expand...
Click to collapse
Hey man, I ran into the same issue as you, so what I did was leave the usb plugged in and held down vol up+power till the phone's screen went black, then immediately held down the vol down button, this brought me into download mode, then I entered:
fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
into adb and my phone went back into twrp.
Can't help with the getting back into the system, I'm still waiting on that too, but hope this helps
Same for me. device corrupted after the restock restore on a US imported Razer Phone. Cant use it now. Have to get a replacement cheap phone since it is my daily phone lmfao.
My upload is for a full restore but if you have only messed up when flashing boot IMG and it's keeps going straight to Twrp then only restore boot from my back up. Your system should still be intact. I will upload just the boot.img alone.
If you accidentally flashed Twrp in the wrong slot then only restore boot using twrp.
https://mega.nz/#!ogclRKCL!YmOMbkhR8oc5MUdxUupdwxRe7BHJGUXRZnal5rW2S_w
Xshooter726 said:
If you accidentally flashed Twrp in the wrong slot then only flash this boot.img using fastboot to get you back to normal.
https://mega.nz/#!ogclRKCL!YmOMbkhR8oc5MUdxUupdwxRe7BHJGUXRZnal5rW2S_w
Click to expand...
Click to collapse
Maybe i am wrong but in this zip file is a twrp boot image not a boot.img file ?
Quashhh said:
Hey man, I ran into the same issue as you, so what I did was leave the usb plugged in and held down vol up+power till the phone's screen went black, then immediately held down the vol down button, this brought me into download mode, then I entered:
fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
into adb and my phone went back into twrp.
Can't help with the getting back into the system, I'm still waiting on that too, but hope this helps
Click to expand...
Click to collapse
Hey, thanks for that suggestion! I was able to get into download mode and I flashed my phones own recovery and I got it to work. Wiped both a & b slot and restored both of them with my recovery.
The only problem (not so sure if it is an issue) is the backup I made is only of the Boot and System Image as per the TWRP instructions. So when I boot into slot a_ I get an error when I boot up 'There's an internal problem with your device. Contact your manufacturer for details.' Switching into slot b, I don't get that error. However, here's the weird thing (I think at least), when I go back into TWRP and switch to slot a, I get a bootloop into TWRP.: So, if I decide to continue on, and flash the TWRP zip file and then subsequently Magisk - I'll lose wifi and etc.
If I end up using Xshooter's full restore img - I'll do the same thing - wipe both slot a&b and restore both slots after. However, I'll get a message after the Razer splash screen say my phone is 'Corrupt' - and this is if I restore with the Vendor options. If I exclude the Vendor options, I'll be stuck in the animation. I lied - I'm stuck on the Corrupt screen now. I can get into TWRP at least...
So, in a bit of a bind here now.
BakaSenpai said:
Hey, thanks for that suggestion! I was able to get into download mode and I flashed my phones own recovery and I got it to work. Wiped both a & b slot and restored both of them with my recovery.
The only problem (not so sure if it is an issue) is the backup I made is only of the Boot and System Image as per the TWRP instructions. So when I boot into slot a_ I get an error when I boot up 'There's an internal problem with your device. Contact your manufacturer for details.' Switching into slot b, I don't get that error. However, here's the weird thing (I think at least), when I go back into TWRP and switch to slot a, I get a bootloop into TWRP.: So, if I decide to continue on, and flash the TWRP zip file and then subsequently Magisk - I'll lose wifi and etc.
If I end up using Xshooter's full restore img - I'll do the same thing - wipe both slot a&b and restore both slots after. However, I'll get a message after the Razer splash screen say my phone is 'Corrupt' - and this is if I restore with the Vendor options. If I exclude the Vendor options, I'll be stuck in the animation.
So, in a bit of a bind here now.
Click to expand...
Click to collapse
No problem, I was just about to give up and settle with a pretty cool paper weight till i tried that out, now i'm gonna try and restore the backup to both slots and try Xshooters method...
Fingers crossed
@BakaSenpai and @Quashhh if you both are able to put your backup on google drive to share it with me so that i can try some options? i have the same issue now. I hope you both get it sorted.
grtz
Steven
Today I had a strange issue with my Oneplus 7 pro GM1913 running OOS 9.5.5, device unlocked, twrp and rooted. My device ran out of charge and was turned off. When I plugged into the charger, it boots up and for a few second the oneplus logo and charge the device for some time page came in and then the bootloader unlocked screen came in. I haven't charged the device offline after the battery ran out, it was my first time and i thought it was supposed to be like that. But after some time also it was on the same page. Then i plugged out the device and it was stuck on that page. I tired hard reboot, tried to connect to computer. Nothing was successful. Computer showed unknown device and failed to successfully connect. Not recognised as adb device shown nor fastboot device. Then atleast I tried entering into fastboot mode by pressing power button + volume up. At that time it rebooted into system and then everything was okay. But then i noticed i also lost the twrp recovery. Then i had to flash twrp through magisk manager.
Anyone has any idea what happened? Thanks in advance
You have to flash magisk again after flashing TWRP.
deborok said:
You have to flash magisk again after flashing TWRP.
Click to expand...
Click to collapse
Yeah I did everything and it was working properly for a week amd then this happened
sachinkjohn1 said:
Yeah I did everything and it was working properly for a week amd then this happened
Click to expand...
Click to collapse
flash stock boot. img
zams85 said:
flash stock boot. img
Click to expand...
Click to collapse
It's working now.. But I just want to know whether this happened to anyone else? Or the reason for this?
sachinkjohn1 said:
It's working now.. But I just want to know whether this happened to anyone else? Or the reason for this?
Click to expand...
Click to collapse
I got stuck there once I was trying to flash twrp somehow. Same fix
Stuck at the bootlogo
Hey guys, i hope i get some help from here.. tried to root my one plus 7 pro international version installed twrp everything worked fine... and after that i tried to reboot in system mode.. now im stuck at the bootlogo with the red middle dot and the 2 white ones. i cant even turn it of now.. no command are working... can anybody help me to fix this pls?
Thanks!!!
I had exactly the same problem. System was running fine with just Magisk installed (I boot TWRP with fastboot on a computer).
Then I ran completely out of charge, and the OP7Pro wouldn't boot anymore: at power on, it shows briefly the OnePlus logo, then displays the boot loader unlocked warning for a very long time (a few minutes), then goes to the bootloader menu.
I can boot TWRP and unlock the data partition. I will try flashing the stock boot and see what happens (and report).
Edit: I had to reflash stock boot and system to have the device boot again.
hi guys,please need help;I have just unlock bootloader on my one plus 7 pro and i was fastboot it with twrp img but i didn't install the twrp recovery one my phone so now the phone blocked on de bootloader unlock screen, I tried to switched of but always back on the same screen, please need help how to do ,thanks
whenever i boot i am stuck at this screen. I flashed the wrong boot.img. How to fix this?
saransh186 said:
whenever i boot i am stuck at this screen. I flashed the wrong boot.img. How to fix this?
Click to expand...
Click to collapse
Enter fastboot and flash the correct boot.
@soka said:
Enter fastboot and flash the correct boot.
Click to expand...
Click to collapse
Unable to enter fastboot
Everytime i switch on the device this is the only screen i see
saransh186 said:
Unable to enter fastboot
Everytime i switch on the device this is the only screen i see
Click to expand...
Click to collapse
I figured it out. basically when i get to the above attached image I was required to hold volume up+down+power key until the fastmode doesn't comes up. It will take 20-25 seconds. So you will be required to hold it for that long.