OK, so i am really lost at this point. I have been trying for the past couple of days with no luck.
I used Minimal adb and fastboot, downloaded Lg drivers (LGMobileDriver_WHQL_Ver_4.0.3), sdk google drivers and looked at many comments to figure this out.
i type adb device and my phone shows, I type fastboot device and last couple of my phone shows. I used Mininimal adb and fasboot to unclock the the bootloader and i followed all the commands but when i get to fastboot flash recovery twrpxxxx.img, it tells me cannot load twrpxxxx.img. Also, when i type in adb reboot bootloader in brings me the an LG screen with powered by android at the bottom instead of the correct screen.
So, i tried the other way. Power phone off, hold down the volume down button and plug in usb and bootloader/fastboot opens up ( the screen with the line in the top left, with a blank page). it shows unlocked, few lines in white, and then few lines in red. I type fasboot devices and my phone shows up displaying last couple of the phone sn#. but when i go to type fasboot flash recovery twrpxxxx.img, i get the same message cannot load twrpxxxx.img. and on the phone is shows fastboot getvar partition recovery.
Any idea on what this is and how can i solve this?
Thanks in advance.
Rename it to recovery.img and try again.
I renamed it and I still get the same error. Cannot load recovery.img
papatoon3 said:
I renamed it and I still get the same error. Cannot load recovery.img
Click to expand...
Click to collapse
Make sure the image is in the same folder that you are running adb from; it doesnt scan your whole computer for the file. ��
Elu_sama said:
Make sure the image is in the same folder that you are running adb from; it doesnt scan your whole computer for the file. ��
Click to expand...
Click to collapse
It is in the same folder.
Does it make any difference that my phone is unlocked from T-Mobile via unlocked code? That should not have anything to do with it thought. I am just tying to figure it out.
Figured it out.
papatoon3 said:
I renamed it and I still get the same error. Cannot load recovery.img
Click to expand...
Click to collapse
I suggest you remove and reinstall sdk or install nexus root tools and run a cmd within the updated tools. Make sure you installed the right drivers, delete all others, reinstall, although your error seems more a problem with the tools, permissions perhaps, did you run cmd as admin?
Unable to load tells me it can't find your file.. Perhaps it has a hidden extension? Recovery.img.txt
Whats the complete exact command you're typing?
"fastboot flash recovery recovery.img"
http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
Sounds like this is not enabled
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-H901 using Tapatalk
papatoon3 said:
Does it make any difference that my phone is unlocked from T-Mobile via unlocked code? That should not have anything to do with it thought. I am just tying to figure it out.
Click to expand...
Click to collapse
SIM unlocked (tmo has no code, its an app) and bootloader unlocked isnt the same thing.
Never mind got it
papatoon3 said:
Figured it out.
Click to expand...
Click to collapse
What was the solution i need it please and thanks
tanked89 said:
Never mind got it
What was the solution i need it please and thanks
Click to expand...
Click to collapse
When your phone is turned on and plugged in, type command adb devices, Does it show?
Put phone in fastboot mode, type command fastboot devices, does it show?
I figured it out. I had to install motorola and g4 drivers to get fast boot to read when I only had one or the other it was only reading adb when I had both on pc it read and adb & fastboot and worked. Thank you.
Hi sir I am facing a problem I rooted my v10 first I unlocked bootloader and then I rooted it by using fwul I hard reset it but when I turned it on a twrp recovery menu appeared please help that how it fix
Related
Hello devs,
here i will write what my friend did with his phone htc one x plus
1.unlocked bootloader successfully
2.flashed recovery, some uncompatible kernel , img files Without rooting.
After this, phone was not booting , now recovery is also not working.
Even phone is not accepting the adb fastboot commands.
1. whenever i boot in HBoot it search for a file .zip from sd card (for what i dont know)(while connected to computer)
2.it shows the "fastboot usb" but computer says device not found. Drivers are installed. Checked with other htc device so they are working fine
3.Is there any way to take to stock via RUU installations.
please guide me with tutorials.
please help me with this problem.
thanks in advance.
bhushan46 said:
Hello devs,
here i will write what my friend did with his phone htc one x plus
1.unlocked bootloader successfully
2.flashed recovery, some uncompatible kernel , img files Without rooting.
After this, phone was not booting , now recovery is also not working.
Even phone is not accepting the adb fastboot commands.
1. whenever i boot in HBoot it search for a file .zip from sd card (for what i dont know)(while connected to computer)
2.it shows the "fastboot usb" but computer says device not found. Drivers are installed. Checked with other htc device so they are working fine
3.Is there any way to take to stock via RUU installations.
please guide me with tutorials.
please help me with this problem.
thanks in advance.
Click to expand...
Click to collapse
S-ON = No Brick.
Recovery and "img files" Don't need root.
Nothing is called adb fastboot
Connect phone in fastboot mode (Power + Volume Down > Fastboot)
Then use the "fastboot devices" command.
Flash twrp 2.8.6 http://dl.twrp.me/enrc2b/twrp-2.8.6.0-enrc2b.img
Flash a compatible kernel.
Device should be "fixed"
Search for "RUU enrc2b" . RUU depends on your CID.
Ghand0ur said:
S-ON = No Brick.
Recovery and "img files" Don't need root.
Nothing is called adb fastboot
Connect phone in fastboot mode (Power + Volume Down > Fastboot)
Then use the "fastboot devices" command.
Flash twrp 2.8.6 http://dl.twrp.me/enrc2b/twrp-2.8.6.0-enrc2b.img
Flash a compatible kernel.
Device should be "fixed"
Search for "RUU enrc2b" . RUU depends on your CID.
Click to expand...
Click to collapse
First of all thank you so much for your reply.
Yeah thats great, i have S-on .
But Fastboot mode is not working .
When i connect phone to computer it shows fastboot usb but no command works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
see that image.
bhushan46 said:
First of all thank you so much for your reply.
Yeah thats great, i have S-on .
But Fastboot mode is not working .
When i connect phone to computer it shows fastboot usb but no command works.View attachment 3256147
see that image.
Click to expand...
Click to collapse
Useful reading
http://forum.xda-developers.com/showthread.php?t=2277112
http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
http://androidforums.com/threads/list-of-fastboot-command.714676/
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=how+to+fastboot
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=what+is+fastboot
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=adb+and+fastboot
Lloir said:
Useful reading
http://forum.xda-developers.com/showthread.php?t=2277112
http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
http://androidforums.com/threads/list-of-fastboot-command.714676/
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=how+to+fastboot
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=what+is+fastboot
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=adb+and+fastboot
Click to expand...
Click to collapse
Hahaahahhaa Perfect description.
@OP:
ADB and Fastboot are two different things.
You DO NOT NEED ADB.
DO NOT WRITE ADB
Write "fastboot devices" directly, and your device will show up.
And please do read all the links lloir provided.
Thank you so much guys.. @Lloir nd @Ghandour
Hello, I am student at my university studying Computer Science. I work in tech support at my school. This is the first time I have modified the android os. The community on xda has been really helpful and knowledgeable. I have created an account to see if anyone else has done the same thing I have. Anyway read below for my post.
I am trying to change the recovery on my phone to twrp. Let me start out by saying I rooted my phone before on build number 130 (KIW-L24,Android 5.1,EMUI 3.1,C567B130,United States, Channel-Others). I used the instructions here and it worked http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190.
I then decided to update through the huawei updater to build number 151 (KIW-L24, Android 5.1, EMUI 3.1, C567B151, United States, Channel-Others). It eventually got to a black EMUI menu with installing 0%. So I powered it off even though it warned against it. So my phone was bricked so I followed instructions at http://forum.xda-developers.com/honor-5x/help/bricked-honor-5x-t3328308 and my phone worked again.
Okay so now I want to root my phone so I follow the instructions for rooting. Problem is that I can not replace the EMUI recovery with twrp recovery. I am guessing that it may be because 151 is a security update.
I use these commands on adb with the twrp_kiwi.img in my adb folder(named .android by default)
adb reboot bootloader
fastboot flash recovery twrp_kiwi.img
fastboot reboot
adb reboot recovery
So I wanted to see if I could put the old firmware back so I followed the instructions for bricked device. But the fastboot commands don't seem to do anything with the .img files.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
Yea so I am lost as to why fastboot commands arent working as it says finished and any advice would be appreciated.
Also is it possible to format the phone similar to a pc and use adb to flash the firmware back on.
I want to eventually backup my phone and put cyanogenmod on it.
... I am guessing that it may be because 151 is a security update
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to flash what you want.
Have you tried reinstalling the Android device drivers on your PC?
JT-on said:
If your bootloader is unlocked, you should be able to flash what you want.
Have you tried reinstalling the Android device drivers on your PC?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Arobase40 said:
Is this really for a private use unless you are trying to ask us to do your university exercises for you ? LOL
And as you felt need to mention "I am student at my university studying Computer Science. I work in tech support at my school.", you should know first University mission is to teach you to search and exercise by yourself, to do things step by step and to guess by yourself what was wrong. ^^
Just one tip and advice : read up your own post carefully and you should find out what you've done wrong...
Click to expand...
Click to collapse
That was just background information unrelated to my post. I am currently trying to see if I can put the old firmware back to see if it fixes the problem.
honor5x_student said:
That was just background information unrelated to my post. I am currently trying to see if I can put the old firmware back to see if it fixes the problem.
Click to expand...
Click to collapse
TWRP works just fine on B151
plug in usb / Shut down the phone
boot to the bootloader (power + vol down)
open command prompt on PC
fastboot flash recovery twrp_kiwi.img
hold volume up + volume down + power till you see TWRP (about 14 seconds)
In TWRP choose reboot / recovery
Say yes to Root
recovery will reload / flash your rom
If you want to return to Stock use this >> https://www.androidfilehost.com/?fid=24459283995315154
instructions are in the zip
Hi guys,
I was following tutorial in order to install stock international FW on my Amazfit 2. However something has failed at step 11, when I was trying to "adb shell reboot bootloader". I got
- exec '/system/bin/sh' failed: Not a directory (20) -
using port=5555
Click to expand...
Click to collapse
Watches are now stuck at amazfit logo and I cannot seem to get to fastboot. Does anybody knows, how to get to fastboot via some key combo on Amazfit 2? I could find just Amazfit solution (this "4 seconds" hint), however it does not seem to work for Amazfit 2...
Any help appreciated, thanks!
Try just this instead:
Code:
adb reboot bootloader
or
Code:
adb reboot-bootloader
Hi thanks for the help,
However I got this idea as well before (based on my general android devices experience) however what it does is that it just reboots normally leading to splash screen stuck. It does not matter whether I issue adb reboot bootloader, adb reboot-bootloader or adb reboot lalala. I think it just grasps adb reboot part only and does normal reboot. However, thank you!.
lfom said:
Try just this instead:
Code:
adb reboot bootloader
or
Code:
adb reboot-bootloader
Click to expand...
Click to collapse
Well, if your watch gets into a bootloop after you use reboot, then something else is wrong... Normal reboot works, just "reboot bootloader" fails?
No, unfortunatelly both normal reboot and reboot bootloader lead to bootloop with Amazfit logo :/
Fastboot finds your device? Can you wipe both data and cache?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Only adb devices sees it. But as I cannot get to bootloader, fastboot does not see it, so I cannot do anything...
Have you ever tried to flash another ROM? It seems that system is broken, that's why you get bootloops and cannot get to bootloader. You have to find a way to do it manually, most devices has some combination at start up to activate recovery and/or fastboot...
Make sure fastboot drivers are installed:
https://forum.xda-developers.com/showthread.php?t=2588979
Then check this for manually activate fastboot:
https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
Hi Ifom, thanks again for your energy and willingness to help me.
I would like to flash another ROM, however right for that I would need to get to bootloader. Guide in second link does not work, probably it is intended just for Amazfit 1. This is actually my original question, whether there is something like this for Amazfit 2, because I cannot find it anywhere.
lfom said:
Have you ever tried to flash another ROM? It seems that system is broken, that's why you get bootloops and cannot get to bootloader. You have to find a way to do it manually, most devices has some combination at start up to activate recovery and/or fastboot...
Make sure fastboot drivers are installed:
https://forum.xda-developers.com/showthread.php?t=2588979
Then check this for manually activate fastboot:
https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
Click to expand...
Click to collapse
Poborak said:
Hi Ifom, thanks again for your energy and willingness to help me.
I would like to flash another ROM, however right for that I would need to get to bootloader. Guide in second link does not work, probably it is intended just for Amazfit 1. This is actually my original question, whether there is something like this for Amazfit 2, because I cannot find it anywhere.
Click to expand...
Click to collapse
Be aware that the method is really hard to get right, it's unlikely you'll get it immediately. It took me maybe 10 minutes of testing to get it to work
You were right! I can confirm now that this method work also for Amazfit 2, however it is kind of tricky. Took me 20 mins to do it right.
Thank you both for helping me out, I appreciate your friendliness very much!
Quinny899 said:
Be aware that the method is really hard to get right, it's unlikely you'll get it immediately. It took me maybe 10 minutes of testing to get it to work
Click to expand...
Click to collapse
Quinny899 said:
Be aware that the method is really hard to get right, it's unlikely you'll get it immediately. It took me maybe 10 minutes of testing to get it to work
Click to expand...
Click to collapse
Take the "Huami_AMAZFIT_Tool_1.0.1.1" and click on "reboot bootloader". This works!
schroepfer said:
Take the "Huami_AMAZFIT_Tool_1.0.1.1" and click on "reboot bootloader". This works!
Click to expand...
Click to collapse
That requires ADB, which requires the watch to at least get to that stage, which isn't the case if you break the kernel
I cannot enter Fastboot Mode.
Quinny899 said:
That requires ADB, which requires the watch to at least get to that stage, which isn't the case if you break the kernel
Click to expand...
Click to collapse
I have an Amazfit and I can't get into Fastboot Mode at all. I have tried all of the alternatives described here many, many times. One question: can Windows / USB port influence not being able to enter Fastboot? Should I try on a Windows 7 for example?
Hi there! I need some help, I am trying to root my device and need a boot.img, but I cannot find a Rom for the x9 anywhere online.
This is my first time doing this, I got this phone just to mess around with rooting. But maybe I bought a bad phone for it.
If there are no Flash Roms online, what are the next steps? Can I use a Rom for the e9 which released alongside this phone? Sounds like it wouldnt work.. but IDK.
Looking for help from the experts ^^
Any help is appreciated.
Finally found one! Took over 2 hours to download a 2gb file O,O but it's finally done.
Now I am having problems getting into bootloader mode.
In developer mode with both OEM unlocking and USB debugging enabled.
Used the correct cmd prompt (adb reboot bootloader) but the phone just restarts.
I've tried restarting while holding the volume buttons.
VOL Down = Factory Test Mode, nothing works as expected there.
VOL UP = A boot menu letting me select from ~10 options, one of them is Boot to Bootloader. Selecting that simply boots normal, nothing special.
I have followed three guides:
How TO Root Vodafone Smart X9 Magisk without TWRP Recovery
If your Smart X9 is rooted using Magisk without TWRP Recovery. You can control a lot of features such as you can remove unwanted software.
www.getdroidpro.com
Vodafone Smart E9 Unlock Bootloader with Fastboot Method
How to unlock bootloader on your Vodafone with Fastboot Method. You can install custom ROM, custom recovery, kernel, flash all data
www.mobilewithdrivers.com
All seem logical enough, many similarities between them. I just cannot get into fastboot mode.
I've seen LOADS of threads with this same problem on this forum. And none of them have any solutions. So I think this is the end of the road. If nobody has figured it out .. then I am just out of luck I guess?
HalpNeeded said:
Forget, your phone have only 3 buttons
Click to expand...
Click to collapse
Hi @joke19 !
I havnt seen any of the guides mentioning needing a certain amount of buttons :O
How does that factor in - does that mean it cannot be rooted for some reason?
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
HalpNeeded said:
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
View attachment 5671635
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
Click to expand...
Click to collapse
did you manage to get this working?
Hello guys can someone help me on my redmi note 10,
So basically my problem is adb can detect my phone when its power on but when my phone switches to fastboot adb cannot detect it anymore. I also try the adb reboot bootloader command, it work and it go to fastboot but after that it didnt detected anymore.
Please help me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure, but it looks like you need install usb/device drivers from MiFlash.
And after, try enable/allow usb debugging
missingN said:
I'm not sure, but it looks like you need install usb/device drivers from MiFlash.
And after, try enable/allow usb debugging
Click to expand...
Click to collapse
i already tried that still the same
@ibanezred16 May be you missing add Environment Variables path?
Adb-fastboot PE guide
ibanezred16 said:
...when my phone switches to fastboot adb cannot detect it anymore. ...
Click to expand...
Click to collapse
This is intended behavior, if your phone is in fastboot mode it can only be detected by fastboot (try command 'fastboot devices'). Devices can only be detected by adb in recovery when sideload is enabled or in OS with debugging on.
Mthw said:
This is intended behavior, if your phone is in fastboot mode it can only be detected by fastboot (try command 'fastboot devices'). Devices can only be detected by adb in recovery when sideload is enabled or in OS with debugging on.
Click to expand...
Click to collapse
sorry im new here, can you tell me a way to flash the twrp? because the regular method don't work with me
ibanezred16 said:
sorry im new here, can you tell me a way to flash the twrp? because the regular method don't work with me
Click to expand...
Click to collapse
What do you mean by regular method? This should work: 'fastboot boot twrp.img' and once it boots up go to Advanced and there is an option called 'flash current recovery'.
Mthw said:
What do you mean by regular method? This should work: 'fastboot boot twrp.img' and once it boots up go to Advanced and there is an option called 'flash current recovery'.
Click to expand...
Click to collapse
that's also one of my problem when it boots to twrp the touch screen is not working can't touch or click anything when im in twrp
Are you using this one? https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4268563/ Either way you should probably ask there.
Mthw said:
Are you using this one? https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4268563/ Either way you should probably ask there.
Click to expand...
Click to collapse
yes, thank you very much for your help
Were you successful? I am guessing you are trying to install a ROM, depending on the rom you could also use a different recovery.
Mthw said:
Were you successful? I am guessing you are trying to install a ROM, depending on the rom you could also use a different recovery.
Click to expand...
Click to collapse
yeah im trying to install Evox
Mthw said:
Were you successful? I am guessing you are trying to install a ROM, depending on the rom you could also use a different recovery.
Click to expand...
Click to collapse
Im succesfully installed twrp I used mouse via otg connector to touch the screen