Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
cbs2002 said:
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
Click to expand...
Click to collapse
The key piece of information for your symptom is in this line:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
The other lines do help provide background as to the other modes such as recovery and download working properly, which indicates the issue is not *serious*.
The symptom you state, where the device does not boot past the boot logo, usually means the device is not able to boot the kernel or boot past the kernel. The boot logo appears while the kernel is being loaded on the device. Generally, after the boot logo and kernel finish loading a boot animation appears which indicates the kernel has usually handed off to the Android OS to continue booting.
My approach would be to load a completely stock ROM in order to restore a working kernel and ROM to the device. I generally perform this step as a baseline to get everything back in working order.
In many instances the ROM is dependent on the kernel. Your situation requires at least a kernel to be loaded and in order to prevent any further issues, it would be best to load a ROM dependent on the kernel being loaded.
A simple way would be to grab the stock factory images from Google's site and load those back onto the device.
Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode.
Hope that helps!
Since you're rooted I'm going to assume you have ADB and the necessary drivers installed.
1.) Download a ROM. It doesn't have to be stock, you can choose any of the ROMs from the development section for your device. Most of the ROMs are packaged with a kernel already.
2.) Save this ROM file to the same folder where you have ADB installed.
3.) Boot your phone into CWM recovery and plug it into your computer.
4.) Use ADB to push the ROM zip file to your phone (/data/media). For example:
Code:
c:\gnex\>adb push rom.zip /data/media/rom.zip
5.) Use CWM to wipe data, cache, and davlik-cache
6.) Install zip from sdcard and flash the rom.zip.
RMarkwald said:
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
Click to expand...
Click to collapse
1. I am using GSM
2. Whenever I turn on my mobile, the 'Google' and 'Unlock' logo appears and then freeze, with no more respond at all
* I definitely mess up some system files, but don't know how to restore it because my PC do not recognize my mobile.
Thanks
I am seeing more and more of these threads about "bricked" nexus's is this an issue with how new the phone is or people not following instructions properly as they are too eager to root their phones?
All else fails flash back to stock and count yourself lucky.
To silow,
Thanks for your advice, but fail
1. I put adb.exe, adbwinapi.dll and fastboot.exe (3 files) under my PC C drive (i.e. C
2. I also put a stock Rom (rename as rom.zip) under C drive (i.e. C
3. Boot phone into CWM recovery and plug it into computer.
4. Use cmd command and type c:\gnex\>adb push rom.zip /data/media/rom.zip
5. It fails , It say "Access Denied" (in Chinese, but I translate it into English here)
6. How do I use ADB (it is a ADB.exe file, When I double click it, it only flash up a few page very fast and nothing happen)
Please assist!
To Joeykrim,
I agree that
"Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode."
But how? (according to my symptoms)
The command I gave you was just an example. I didn't spell out the exact details because I thought that you would know how to do it considering you rooted the phone.
If you put the adb.exe and AdbWinApi.dll file in your C: drive, make sure you copy the ROM file to your C: drive too. In the follow example I'm going to use "ROM.zip" but use the name of the ROM file that you downloaded. Also I am assuming you are on Windows XP.
1.) Boot your phone into CWM recovery and then plug it in.
2.) Go to your Start Menu and choose Run. Then type in "cmd" without quotes and hit enter to open a command prompt.
3.) Enter:
Code:
cd c:\
4.) Enter the following to make sure ADB can see your phone:
Code:
adb devices
You should see something similiar to this to confirm ADB can see your device:
List of devices attached
019B756F0C018012 device
5.) Enter the following command to copy the ROM file to your phone. Remember to replace ROM.zip with whatever the name of the ROM file is:
Code:
adb push ROM.zip /data/media/ROM.zip
6.) Use CWM to wipe data, cache, and davlik-cache
7.) Install zip from sdcard and flash the rom.zip.
To Silow,
You have been very helpful, but I fail.
"You should see something similiar to this to confirm ADB can see your device:
List of devices attached"
There is NO device number shown after the phrase 'List of devices attached'
To recap:
a) Phone is already plugged in my PC, under the Clockworkmod Recovery 5.5.0.2
b) adb.exe and AdbWinApi.dll file are under C: drive directly
c) Also type cmd in 'Run', a black Dos window shown C:\windows\system32\cmd.exe
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Pls don't give up on me!
: )
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot (edit: wrong!)
Sounds like your ADB USB drivers are not correctly installed. While the phone is under CWM, when you plug it in is your computer attempting to install drivers for a new device?
Download these bare ADB Interface drivers.ADB USB Drivers
Go into Device Manager on your computer and check the device list for any unknown devices or "?" devices. If you need to update those drivers by pointing them to the drivers you downloaded and extracted from that link above.
When the ADB Interface drivers are correctly installed you should see Android Phone listed under under your Device Manager when it's plugged in with CWM recovery loaded.
---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
edit: i did appear to have one missing driver, my mistake. it was listed in device manager as "unknown - full"
its funny cause i never had to use adb from cwm before, never noticed
cbs2002 said:
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Click to expand...
Click to collapse
This symptom generally occurs from not having loaded the drivers for the hardware. As with the majority of hardware devices when being connected to a Windows machine, the drivers need to be loaded. Sometimes these are automatically loaded and other times they have to be manual loaded.
As an alternative and for future reference, the android-sdk package contains general USB drives which usually work for Google Nexus devices.
Generally, as this providers a *cleaner* install, best practice as recommended by Google is to download the whole android-sdk .zip and then from the installer download/install the pieces needed, such as platform-tools (containing adb) and USB drivers as opposed to extracting out the adb.exe and .dll file and installing manually.
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
Agreed. To add greater clarification so there is no confusion: adb can't be used from the bootloader.
The /sbin/adbd daemon on the device is only loaded while in normal android boot mode or in recovery mode as called by the init.rc (or on some older devices, recovery.rc) file in the boot process.
Bootloader mode will only work with fastboot while it is in fastboot usb mode.
On some devices, the bootloader has a separate menu for fastboot and on other devices, the fastboot mode is directly entered when entering the bootloader.
Hope that helps clarify!
To silow (and all other helpers)
1. I fail
2. The ADB USB drivers in my PC should be fine as in Device Manager , I can see Android Phone with Android Composite ADB Interface. (No exclamation mark)
3. On the other hand, whenever I plug my mobile into PC, I can see "Unknown-Full"
4. In DOS, when I first type "adb devices" it shows
* daemon not running. starting it now on port 5037*
*daemon started successfully *
List of devices attached
(but NO device number shown!)
5. When I enter adb devices second time, it shows
List of devices attached (No device number shown)
Thank you so much , but it is Hong Kong time (my place) at 0511 am , I didn't sleep all night and I am very tired.
If you don't mind (especially big helper Silow), please give me email so that I capture screen picture and show you in detail (hope it may help)
my email is
[email protected]
I need to sleep now, I will check my email and see you guys or come back this Forum later (several hours later, as I really need some sleep right now)
Pls don't give up on me as this is an expensive mobile. I think the hardware is fine, just need to figure out a way to unbrick it.
Thanks, and see you!
What you need to do is right click on "Unknown-Full" and click on "Update Driver...". Then choose "Install from a list or specific location". Make sure "Search for the best driver in these locations." is checked and "Include this location in the search:" is check. Click on the Browse button and browse to where you extracted the driver files from the link I posted above. Click Next and this should install the correct drivers for you. Afterwards try "adb devices" again to see if ADB now reconizes your device.
To Silow,
Fail.
1. Already installed the drivers you gave me (and there is no 'Exclamation' Mark) in Device manager
2. Situation is the same , Cannot recognize my mobile (i.e. no Device No. after entering adb devices)
3. "List of devices attached" shown in DOS video but without any number.
No other method?
My mobile is really 'bricked' to death?
To Silow and all,
Something important
1. When choose 'install zip from sd card' under CWM, a list of old folder names remains
(e..g gameloft, DCIM, Pictures, etc). That means almost all old files, folders are STILL in my mobile!
2. I have already use the funcion 'Wipe data/factory reset', 'wipe cache partition', ' Wipe Dalvik Cache'
Perhaps my CWM has problem?
What happens when you update drivers for Unknown-Full?
Boot into fastboot and see if your computer recognizes the phone by checking device manager. The key here is to get your computer to see the phone either in fastboot or CWM.
Perhaps try another cable, USB port, or new computer.
The goal is to get Android Phone ADB Composite Interface to show up in device manager either in Fastboot or CWM. Without that done you cannot use Fastboot to flash nor ADB to push a zip file to the phone.
Sent from my Galaxy Nexus using XDA App
Finally got the Factory Cable to fix a bad flash back to stock rom. When i plug in the factory cable, i can run any of the commands from the Kindle_Fire_Utility_v0.9.6 tool without issue.
I want to copy update.zip over to the Kindle so i can flash it back to he default rom.
I can boot to TWRP, click mount, but it doesn't show up as a drive letter in windows.
My other Kindle comes up as a usb drive immediately when its connected to the usb port with either the factory cable or regular usb cable.
Have tried removing and reinstalling drives to no resolve.
Is there some special trick to get the factory cable to show up as a valid usb drive in windows 7? When i click on 'Safely Remove Hardware and Eject Media' it does show 'Eject Kindle' as an option, but no drive letter.
Is there a way to get the update.zip file over the Kindle to resolve this?
Have tried the Kindle Unbrick UtilityV1.1 as well, which didn't work as it never sees the Kindle as a valid drive letter.
Thanks
http://forum.xda-developers.com/showthread.php?t=1638452
Have you tried...
Code:
adb push update.zip /sdcard
...while in recovery?
Shift+right click the KFU "tools" folder and select "Open command window here" to enter your adb commands.
soupmagnet said:
Have you tried...
Code:
adb push update.zip /sdcard
...while in recovery?
Shift+right click the KFU "tools" folder and select "Open command window here" to enter your adb commands.
Click to expand...
Click to collapse
Tried the above while in TWRP with mount and no mount, same on both.
D:\Kindle\Kindle_Fire_Utility_v0.9.6\tools>adb push update.zip /sdcard
error: device not found
Went into device manager uninstalled the Android SDK driver, now the factory cable showed up when mounted, did the above again and it worked. Thank you.
Hi All,
I have spent this afternoon rooting stock 4.3 yakju and thought that I'd share the latest on how to go about doing this manually for the maguro GT-I9250. This is a complete guide which brings all the information you will need under the one thread which doesn't seem to have been done before except as separate guides and scattered information all over the internet.
NOTE: Unlocking and Rooting your device will void your warranty and can in some instances if not performed properly brick the phone. This process will also wipe your phone back to factory defaults so any personal files and applications will be lost. You should backup the device using the backup options in the recovery environment or by saving any personal files off the device via the USB cable, prior to unlocking your device. You follow this procedure at your own risk!!
With that disclaimer out the way there, We can begin.
NB: I ran all linux commands in this tutorial as root, I am not able to say if running as a standard user may cause issues, although one forum suggested to run as root or sudo up if you have a bootloop issue so I did this to avoid problems. This tutorial assumes that you have some experience with using basic Linux commands including but not limited to copying and moving files, changing directories, listing files, running scripts and executables using './' and using the console
So Firstly I am running Fedora 19 x64 with the latest kernel. It's a lot easier than trying to muck around with Windows 7 drivers and there are tutorials for installing these. To update on that tutorial you can use the official samsung drivers to install the adb and mtp drivers (may already be noted in the thread, but I might as well state it here also.) and the best place to get the official samsung drivers is by installing the Samsung Kies application.
You need to enable 'USB debugging' in order for ADB to work, you do this from 'settings --> developer options' if you can't see 'developer options' you may need to enable them, to do this, select 'settings --> about phone' and tap 'build number' until it says 'you are now a developer' which takes around 7 taps. In 'developer options', you may need to turn them on by clicking the 'on' button at the top. Once you have turned them on, select 'usb debugging' and this will then tell you that 'this may make your device less secure', agree/accept this, and continue. You can always turn it off later if you need to. Once you enable this, within linux you may get prompted when running adb to authorize (e.g. you are not authorized, check the device screen). You need to authorise from the phone, so allow the connection and select 'remember this computer' to save having to do it again.
Now for the bootloader driver it's a bit trickier to install. You need to reboot into the bootloader, by powering off the device and then powering back on again while holding the volume + and volume - keys at the same time. You will then probably get a failed driver install for 'Android 1.0'. At this point, you will need the universal Naked driver from this thread. Download and extract it to your 'Downloads' folder. Now go to device manager, right click on the 'Android 1.0' device and select 'update driver...' and then select 'browse my computer for driver software' and then select 'let me pick from a list of drivers'. Click 'have disk' and you will be able to install from the folder you extracted the 'Universal Naked Driver' into. You will now be able to use the fastboot command in Windows.
Ok. Now we have the windows users covered. In Linux, All I needed to do was download the android sdk adt tools. I'm using the 64 bit version, so I downloaded the 64 bit version from the adt bundle section here. Once I had downloaded and extracted these into a folder in my Downloads folder under my user profile, I copied the adb and fastboot files to a separate folder as these are the only things I needed in the bundle. you do this by typing
Code:
cp /home/<your_username>/Downloads/Androidadt/adb /home/<your_username>/Downloads/Nexusroot/
cp /home/<your_username>/Downloads/Androidadt/fastboot /home/<your_username>/Downloads/Nexusroot/
From here on you will want to be working from the 'Nexusroot' folder, so type
Code:
cd /home/<your_username>/Downloads/Nexusroot
.
From here, you need to obtain the recovery you wish you use, I chose to use the CWM v6.0.4.3 touch recovery which can be obtained from here. Once it's saved to your downloads folder you should copy it to your previously created 'Nexusroot' folder where we saved adb and fastboot.
The next item on the list is something I did because I was running the yakjuxw firmware and is the reason I did everything in Linux for this tutorial, as the firmware files are tarballed and opening the tar in 7zip shows 'unix filesystem' as the base folder. I installed the stock 4.3 firmware from google. I used the extracted files for the firmware as my 'Nexusroot' folder and copied fastboot and adb into this folder as well as the recovery image. I then ran ./flash-all.sh with the device in fastboot mode (you will need to have unlocked the bootloader prior to doing this, instructions are below in the next paragraph. The script basically just flashes the firmware with the fastboot command, if you want to flash the CWM recovery at the same time, you will need to rename the recovery file to the same name as the recovery image in the tarball and replace or rename the one that came with the tar file from google), If you have setup your environment in Windows 7 as described above, there is also a batch file that will do the same thing ensure the device is in fastboot before running the batch file/script or it will sit there and say 'waiting for device' and make sure the fastboot application is in the same folder as the script. Once the flash is complete your device will be running the stock 4.3 firmware. (edit: I have since extracted the entire image out of the tar with 7zip from Windows 7, you will be able to flash the base once you extract it all to a folder but you need to open the secondary container file in 7zip separately)
The next step is to flash the recovery. To do this, put the device into fastboot mode and unlock the bootloader using the command
Code:
fastboot oem unlock
select 'Yes' at the prompt, your device will now reboot twice and perform a factory reset which will wipe all data, at this point you may need to re-enable 'usb debugging' from your settings (see above for instructions), re-enter fastboot mode by typing
Code:
adb reboot bootloader
next type in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-maguro.img
Your device will now install the touch recovery we downloaded earlier. Once done, type the command
Code:
fastboot reboot-bootloader
.
Now to root the device, download the SuperSU zip file from the link and copy it to your 'Nexusroot' folder. Now boot into your recovery environment by using your 'Volume -' key to select 'boot recovery' and allow the device to boot into the recovery environment. This will allow you to use the adb command. Change directory into your 'Nexusroot' folder if not already in it, and type
Code:
adb push UPDATE-SuperSU-v1.43.zip /sdcard/0
This will copy the zip file to the internal memory card. From the recovery environment on the phone, select 'install file from sdcard' and then 'choose zip from sd card'. Select '0' and then select the 'UPDATE-SuperSU-v1.43.zip' file and select 'yes - install...' and the zip file will install the SuperSU application and binaries. Your device is now rooted, however you will need to run the SuperSU app to update the binary again. We will discuss this further after the next step.
Now we should lock the bootloader again to prevent tampering with our recovery and other firmware images however if you wish to flash other ROMS you will want to leave this unlocked, or you will need to unlock it again next time you want to flash a rom. To lock the bootloader, with the phone in fastboot mode, you simply type
Code:
fastboot oem lock
and this will re-lock the bootloader. Note you will not be able to flash any radios, kernels, or other .img files while this is locked. Now reboot your phone back into Android.
Now that you know how to unlock your phone, it's rooted, and has a recovery environment installed, you need to activate your SuperUser install. To do this, open the SuperSU app, and when prompted to update, click 'continue'. You will at this point be asked how you want to install it, select 'CWM/TWRP Recovery' and your phone will reboot, you will see an update occur on the screen and SuperSU will now be correctly installed.
You can now begin experiencing the freedom to use whatever ROM you want, customise your device how you want, and even change which applications you want installed regardless of whether they are system apps or otherwise.
I hope this guide is helpful.
References:
http://forum.xda-developers.com/showthread.php?t=1379875
http://forum.xda-developers.com/showthread.php?t=1830108
http://forum.xda-developers.com/showthread.php?t=2117822
http://forum.xda-developers.com/showthread.php?t=2065470
http://www.ibtimes.com/how-root-galaxy-nexus-i9250-nexus-4-android-43-jelly-bean-official-firmware-tutorial-1362063
http://www.clockworkmod.com/rommanager
https://developer.android.com/sdk/index.html
http://www.ubuntu.com/phone/install
https://developers.google.com/android/nexus/images
Thanks:
@1wayjonny
@TECK
@samersh72
Without your guides I wouldn't have been able to do this.
Hey guys i'm in serious trouble with my phone.
It stucks on boot screen and does nothing.
I can boot into TWRP, but i deleted the LineageOS.zip from sdcard to save space. When running TWRP, i can't see the phone in my adb prompt. I can see my phone when adb sideload is running. I tried to use adb sideload, but it fails with something like 'the zip your are trying to install is for zl0,zl1...but your device is .'
I need some way to push the LineageOS rom to sdcard without adb connection available. There is an option in TWRP to mount an USB Device, would it make sense to buy a little USB type C stick ?
I apprechiate any kind of help !
1. Check is the phone in TWRP avaiable in Windows file manager. It should be.
2. If not go in TWRP to sideload and try to "adb push FILE-IN-WINDOWS FOLDER-IN-PHONE" eq "adb push rom.zip /sdcard/0/" (if your ROM is with name "rom" in ADB file).
3. If not try to wipe all exclude OTG.
4. If not try to push trough OTG (if you have OTG then do it firstly).
marik1 said:
1. Check is the phone in TWRP avaiable in Windows file manager. It should be.
2. If not go in TWRP to sideload and try to "adb push FILE-IN-WINDOWS FOLDER-IN-PHONE" eq "adb push rom.zip /sdcard/0/" (if your ROM is with name "rom" in ADB file).
Click to expand...
Click to collapse
Unfortunately the phone isn't visible in Windows, neither in TWRP nor Sideload. I tried to push in sideload, but that doesn't work (adb: error: connect failed: closed). TWRP FAQ says that there are no adb commands available in sideload.
I just ordered an OTG stick. Let's hope i can mount him in TWRP.
Anybody other suggestions ?
Try adb commands in fastboot... ? Doesn't have to be visible with device-info
androidz.net said:
Hey guys i'm in serious trouble with my phone.
It stucks on boot screen and does nothing.
I can boot into TWRP, but i deleted the LineageOS.zip from sdcard to save space. When running TWRP, i can't see the phone in my adb prompt. I can see my phone when adb sideload is running. I tried to use adb sideload, but it fails with something like 'the zip your are trying to install is for zl0,zl1...but your device is .'
I need some way to push the LineageOS rom to sdcard without adb connection available. There is an option in TWRP to mount an USB Device, would it make sense to buy a little USB type C stick ?
I apprechiate any kind of help !
Click to expand...
Click to collapse
Okay so if you already have Twrp installed that's Great. that's your recovery, don't lose it. Be in the habit of rebooting to Twrp whenever you flash something.
The only way to resolve this issue is to format the storage.
You have an easy options.
Buy the OTG adapter...Yes get it, it will make flashing ten times faster and alot easier to quickly flash a file if you find yourself in a bootloop.
The OTG Adapter will cost about $5
You should also buy a 32 usb 3.0 drive. I bought my 3.0 usb at Walmart for $12..
After formatting the sd storage> Click select storage > choose USB drive> add your ROM> click add more zips > add Gapps, and Magisk > Flash.
Reboot to recovery> make sure to check boxes for TWRP installation recovery and system app.
Once reboot to recovery > click "select storage"
Click Wipe > select Advanced Wipe> select Cache ( only cache) > Slide to wipe
Reboot to system > Done.
First boot could take several minutes
Good afternoon, I need help in TWRP mode I can not mark usb-otg in mount.
My terminal does not have a rom because I mistakenly delete all the data.
My idea was to put the rom in a pendrive otg and intalarla from TWRP but I can not check the corresponding box.
In Fastboot mode either since my pc does not recognize the terminal, I have tried all the ports of the pc and all the cables that I have.
The drivers are well installed and adb and others work correctly.
I need your help, since the phone works very well and I changed the battery recently.
Thanks in advance.
can you mount mtp in twrp? perhaps you could try loading a rom from your pc to your phone via adb sideload in twrp.
NightRaven49 said:
can you mount mtp in twrp? perhaps you could try loading a rom from your pc to your phone via adb sideload in twrp.
Click to expand...
Click to collapse
thanks, there is some tutorial to do this. I'm pretty new in these things
to mount mtp, boot twrp, then go to mount. there will be a button on the bottom right that says enable mtp (if mtp is disabled) and tap it. if mtp is already enabled, the button will say disable mtp, so you don't have to do anything here. just plug your phone into your computer and see if it gets detected. if it doesn't get detected, again try the different ports on your computer or switch cables.
once your phone is detected, you have 2 options.
1) mtp allows files to be copied over from your pc to your phone while in twrp. so you can just copy a rom file into your internal storage and flash normally.
2) you can also flash the rom through adb sideload. first, place the rom in an easily accessible directory, such as directly on C:\. next, you can start adb on your computer by opening up terminal/powershell and typing
Code:
adb start-server
you should get a message saying adb daemon is now running on port xxx. next, open up the adb sideload dialog in twrp through advanced >> adb sideload, then swipe to start the service. just to be sure your phone is detected by your pc, type
Code:
adb devices
your phone should show up on the terminal with its serial number. now navigate to the folder where your rom is and flash it.
Code:
cd C:\
adb sideload rom.zip
make sure your phone doesn't get disconnected during the process of flashing.
I'd recommend 1) since it's a more familiar method of flashing.
Try formatting your Usb pen drive as FAT32, it worked for me. My pen drive was formatted as NTFS previously and twrp did not allow me to check box the "usb otg" option, but after formatting as FAT32 it worked like a charm.
Good luck