Database Users

get problem after flash new kernel

Please help
I was using motley kernel + pacman ROM. Yesterday I want to try new kernel ( dmore) but after I flash it using cwm) and boot into device I have nonstop nfc service, system ui, android.phone fc. I can't use my tablet anymore.I accidentally deleted motley kernel zip and the kernel in pacman zip so now I only have dmore kernel zip
I have wipe data/system/cache/deavik cache/ and try reinstall ROM but problem still there.
Atm I can access bootloader and cwm recovery(6.0.3.0). I read few guild but they all need adb access which I can't enable it now. Can't use adb sideload.
Please help me:crying:
I noticed in dmore kernel there is a boot.img while in motley is folder which contains 4 files. Is it why I got this problem and why?

You have USB OTG?
I used a Pen Drive and OTG with TWRP when I messed my N7 up, WIPED EVERYTHING I COULD.
Plugged OTG in, Plugged USB in with ROM/Kernel.
Told TWRP to use external storage, flashed and booted

Wilks3y said:
You have USB OTG?
I used a Pen Drive and OTG with TWRP When I messed my N7 up, WIPED EVERYTHING I COULD.
Plugged OTG in, Plugged USB in with ROM/Kernel.
Told TWRP to use external storage, flashed and booted
Click to expand...
Click to collapse
I have usb otg but what is pen drive? And I only have cwm not twrp( is it possible can you check for me(thanks :fingers-crossed:

Your post is unclear... I'm not sure if you have a useable Android BOOTABLE OS or if you've wiped /system and fully formatted your INTERNAL STORAGE... and thus been left with nothing but a RECOVERY and a BOOTLOADER....
This seems to be a common occurrence with people running TWRP (the new version, 2.5, makes this less likely)...
But you're running CWM... CWM, whilst less 'user friendly', is more 'idiot proof'..
---------------------
So.. here's what I would try... based on your post.
From complete shutdown, long press the POWER BUTTON + VOL DOWN BUTTON... this will boot your device into BOOTLOADER/FASTBOOT MODE.
If the device is BOOTLOOPING, long press on both keys SIMULTANEOUSLY... for a good 30 seconds or so, maybe longer.
From here, using the VOL BUTTONS, navigate to RECOVERY (press POWER BUTTON to select)...
And restore your NANDROID backup...
You do have a Nandroid backup... I assume...
If you don't have a Nandroid backup... then you're probably going to have to FASTBOOT FLASH back to stock.
Rgrds,
Ged.
---------- Post added at 03:43 PM ---------- Previous post was at 03:36 PM ----------
Just another idea....
You could try FASTBOOT flashing the kernel (boot.img) you where originally using before this debacle...
Rgrds,
Ged.

GedBlake said:
Your post is unclear... I'm not sure if you have a useable Android BOOTABLE OS or you've wiped /system and fully formatted your INTERNAL STORAGE... and thus been left with nothing but a RECOVERY and a BOOTLOADER....
This seems to be a common occurrence with people running TWRP (the new version, 2.5, makes this less likely)...
But you're running CWM... CWM, whilst less 'user friendly', is more 'idiot proof'..
---------------------
So.. here's what I would try... based on your post.
From complete shutdown, long press the POWER BUTTON + VOL DOWN BUTTON... this will boot your device into BOOTLOADER/FASTBOOT MODE.
If the device is BOOTLOOPING, long press on both keys SIMULTANEOUSLY... for a good 30 seconds or so, maybe longer.
From here, using the VOL BUTTONS, navigate to RECOVERY (press POWER BUTTON to select)...
And restore your NANDROID backup...
You do have a Nandroid backup... I assume...
If you don't have a Nandroid backup... then you're probably going to have to FASTBOOT FLASH back to stock.
Rgrds,
Ged.
---------- Post added at 03:43 PM ---------- Previous post was at 03:36 PM ----------
Just another idea....
You could try FASTBOOT flashing the kernel (boot.img) you where originally using before this debacle...
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank for helping. As I stated my internal memory is safe so I still can try reflash ROM and kernel.
About fastboot I have installed android sdk and many thing in some guide required but I can't get fastboot cmd work can you explain clearly step by step for me how to do that
About fast

Yuuhi Katagiri said:
Thank for helping. As I stated my internal memory is safe so I still can try reflash ROM and kernel.
About fastboot I have installed android sdk and many thing in some guide required but I can't get fastboot cmd work can you explain clearly step by step for me how to do that
About fast
Click to expand...
Click to collapse
Well, if you're internal is 'safe', as you put it... and if you have a FLASHABLE ROM .zip stored on it... then boot into CWM, and reflash that.
(BUT FIRST - Do as full wipe as you can in CWM without erasing internal storage - sorry about the vagueness of this; I haven't used CWM for a while).
Forget about KERNEL stuff for now... let's get the engine running; we can polish the chrome later.
Rgrds,
Ged.
PS. You must have run FASTBOOT at some point... I note from your SIG. 'bootloader unlocked'... which of course requires the command fastboot oem unlock.

GedBlake said:
Well, if you're internal is 'safe', as you put it... and if you have a FLASHABLE ROM .zip stored on it... then boot into CWM, and reflash that.
(BUT FIRST - Do as full wipe as you can in CWM without erasing internal storage - sorry about the vagueness of this; I haven't used CWM for a while).
Forget about KERNEL stuff for now... let's get the engine running; we can polish the chrome later.
Rgrds,
Ged.
PS. You must have run FASTBOOT at some point... I note from your SIG. 'bootloader unlocked'... which of course requires the command fastboot oem unlock.
Click to expand...
Click to collapse
I flash ROM. It boot through bootanimation but stuck after android upgrade dialog with nonstop nfc service fc, system ui fc... So I think the only way is to flash stock pacman kernel to solve fc problem then everything should be ok I hope it works for me. My bootloader is unlocked and fastboot mode' color showed in bootloader is red. But I still don't know how to use fastboot command with pc
?

Some how your dirty flashing, which is where the Force Closes are coming from.
Get your USB OTG.
Get a USB STICK (Pen Drive / Memory Stick)
Put ROM / Kernel onto USB STICK
Wipe just about everything you can find on your device. Obviously don't wipe the Boot Loader.
"Use External Storage"
Find ROM / Kernel on memory stick.
Flash ROM
Wipe Cache / Dalvik
BOOT!!!!!!!!
Reboot to Recovery if boot is successful.
Flash Kernel
Wipe Cache / Dalvik
BOOT
Then flash GAPPS
Wipe Cache / Dalvik
Boot.
Some of these Cache wipes may seem un-necessary, but at least you can then be sure its being cleanly flashed.

well able to flash stock pacman kernel and my problem is solved Thanks anyone has help me back then:fingers-crossed:
And mod please closed this thread

@Yuuhi Katagiri
I hope that after this exercise you understand that all your troubles here could have been quickly solved by making full nandroid backups.
People seem to think that backups are too much trouble; but IMO what they provide you is freedom:
With a backup you can always undo any unforseen mistakes or troubles by merely restoring the backup.
It really is just that simple: having backups gives you confidence to experiment because problems you run into can be easily solved.
good luck

[Q] Boot Loop when attempting to update CM after installing

I successfully rooted and modded my Note 3 to run CyanogenMod 11-20140916-SNAPSHOT-M10-hlte. Since that time there have been 2 updates (M11 and M12).
I have downloaded and attempted to update both by using ROM Manager as well as the Update feature in the Settings Menu. Whenever I try to do this, I get the phone's opening splash screen along following messages:
RECOVERY BOOTING ...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
The phone then reboots and returns to this screen.
The only thing I can do is pull the battery, reinsert it, then perform the Volume Down + Home + Power reboot then press Volume Down to force the reboot back to normal.
Did I screw up something when I rooted my phone that is preventing the updates from processing, or am I stuck with manual updates from here on out. If that is the case, what do I need to do to make that happen?

Anyone? Anyone? Beuller? Beuller?
I am bumping this in hopes to get an answer. I am getting really sick of the instability and want to get the newest ROM flashed or, if that's not possible, flash the stock ROM back on the phone.

Odin a recovery like twrp after the odin is done shut down the phone . press volume up +power+home to get back in recovery . from here flash the cm ROM.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
Lol and if you don't know what Odin is than you shouldn't be messing with your phone..

Do a clean flash and it will be good...factory reset+wipe cache and dalvik....

gabesir said:
Odin a recovery like twrp after the odin is done shut down the phone . press volume up +power+home to get back in recovery . from here flash the cm ROM.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
Lol and if you don't know what Odin is than you shouldn't be messing with your phone..
Click to expand...
Click to collapse
I am familiar with Odin, but was able to do everything the first time with ROM Manager.

osutuba said:
I am familiar with Odin, but was able to do everything the first time with ROM Manager.
Click to expand...
Click to collapse
so it doesnt boot into recovery at all? the only way to fix it is to odin your recovery again and than flash your rom.

gabesir said:
so it doesnt boot into recovery at all? the only way to fix it is to odin your recovery again and than flash your rom.
Click to expand...
Click to collapse
Yeah, I had to Odin TWRP on there. Now, I just need to figure out which CM build to use, because there's only nightlies for my specific model (T-Mobile), while there are snapshots of the base model.
I'm welcome to trying other ROMS, but CM is what I am most accustomed to.

osutuba said:
Yeah, I had to Odin TWRP on there. Now, I just need to figure out which CM build to use, because there's only nightlies for my specific model (T-Mobile), while there are snapshots of the base model.
I'm welcome to trying other ROMS, but CM is what I am most accustomed to.
Click to expand...
Click to collapse
Awesome man! glad you back in TWRP..
Look for a CM11(most stable) port for your phone and go from there. :highfive:

gabesir said:
Awesome man! glad you back in TWRP..
Look for a CM11(most stable) port for your phone and go from there. :highfive:
Click to expand...
Click to collapse
Well, I have tried several different mods and keep getting the same error in TWRP:
E:Unable to open ZIP file
Error flashing zip <filename.zip>
Updating partition details ...
Ideas/suggestions? I'm comfortable enough with Odin now to the point that I can flash a ROM that way, if necessary.

rayman95 said:
Do a clean flash and it will be good...factory reset+wipe cache and dalvik....
Click to expand...
Click to collapse
Do read before you post. OP couldn't even access his recovery.
osutuba said:
Well, I have tried several different mods and keep getting the same error in TWRP:
E:Unable to open ZIP file
Error flashing zip <filename.zip>
Updating partition details ...
Ideas/suggestions? I'm comfortable enough with Odin now to the point that I can flash a ROM that way, if necessary.
Click to expand...
Click to collapse
First of all, why is it called filename.zip? Put the CM .zip file to internal or external SD card (latter preferred if you have one) and then flash it directly from there after wiping (I wipe system, data, cache, dalvik cache).

Someguyfromhell said:
Do read before you post. OP couldn't even access his recovery.
First of all, why is it called filename.zip? Put the CM .zip file to internal or external SD card (latter preferred if you have one) and then flash it directly from there after wiping (I wipe system, data, cache, dalvik cache).
Click to expand...
Click to collapse
why do you propose him to flash CM11 if he can't get recovery mode????

Someguyfromhell said:
First of all, why is it called filename.zip?
Click to expand...
Click to collapse
I used <filename.zip> as a generic marker, as I have tried several different ROMs with the same outcome. As I stated in a previous reply, I was able to flash TWRP using Odin without issue. I have even re-flashed it several times since getting the aforementioned error, thinking something wasn't working.
Someguyfromhell said:
Put the CM .zip file to internal or external SD card (latter preferred if you have one) and then flash it directly from there after wiping (I wipe system, data, cache, dalvik cache).
Click to expand...
Click to collapse
I don't have an external SD Card on hand at the moment, otherwise I would try that.

rayman95 said:
why do you propose him to flash CM11 if he can't get recovery mode????
Click to expand...
Click to collapse
Please keep an eye on the topic. You can see that he solved the issue (after your and before my post) with accessing recovery, thereby we have moved on to solve his next problem - flashing the ROM.
osutuba said:
I used <filename.zip> as a generic marker, as I have tried several different ROMs with the same outcome. As I stated in a previous reply, I was able to flash TWRP using Odin without issue. I have even re-flashed it several times since getting the aforementioned error, thinking something wasn't working.
I don't have an external SD Card on hand at the moment, otherwise I would try that.
Click to expand...
Click to collapse
Re-download the .zip file and place it on the internal storage then. Do MD5 check also before moving, seems like the zip file was corrupted (faulty download?) when you tried to flash it.

[NEED HELP] How to flash stock ROM my Grand Prime (SM-G531H) ?

OK first I was never going to chat on a public forum, so it will be kinda noob, feel so sorry 'bout that.
But I got a very hard problem here.
Basically 3-4 days ago I've rooted my Grand Prime (SM-G531H) and running very well and smooth.
But then I realize that my PC can't recognize my Android when I try to send some data.
My PC is running Windows 10 x64 bit.
I've try some method 'bout MTP but it still can't connect.
Then come the hardest part, I've boot into the TWRP mode, and try to wipe it. :crying:
Was so confuse which wipe that i click, and the last my Android doesn't have OS installed (When try to reboot it on TWRP) :crying:
Taking the Odin mode but it still didn't connect to my PC. :crying:
Can anyone help me please ? Will be sooooo fully thanks if it can be normal again.

Do you have all the drivers installed? Try using another cable. If you have another samsubg phone connect it to the pc and if it gets recognised wait for everything (driver setup and stuff to get over and immediately connect your phone in the same port and same cable. This helped me identify my device.
---------- Post added at 04:59 AM ---------- Previous post was at 04:59 AM ----------
I forgot to mention try different ports
---------- Post added at 05:02 AM ---------- Previous post was at 04:59 AM ----------
If your phone cannot connect still (you went to dowbload mode?) you can install a custon rom like cm13 for G531h and follow the steps mentioned.

ARHudyana said:
Was so confuse which wipe that i click
Click to expand...
Click to collapse
You wiped system partition
Can anyone help me be normal again.
Click to expand...
Click to collapse
Here you go:
Required
TWRP as recovery (mentioned you have)
SD Card
Custom ROM CM13 or LOS14 (anyone of your choice)
FlashFire download
Stock Firmware download
Steps
Part One: Assuming you have all required files mentioned above
Boot into recovery
Choose Mount
Choose USB Storage
Copy all those required files to SD Card
Unmount USB Storage
Choose Install, locate where you copied files and flash CM13 or LOS14 whichever you downloaded
Now wipe Data, Cache and Dalvik Cache then Reboot
Part Two: Assuming you are booted into the Custom ROM
Enable Developer Options in the phone and enable Root from developer options
Install FlashFire and Open it
Click on +, select Firmware Package then locate where you copied downloaded files on SD Card and choose .tar.md5 tarball
If you want pure Stock ROM then remove tick mark from "Preserve Recovery" and " Inject SuperSU" options, also put tick mark on Wipe Data and Cache
Now start flashing and after reboot you'll have pure Stock ROM
Tips
About device not being recognized by PC, may be you have driver missing so try installing Samsung Smart Switch download
Your cable may be defective so try another cable (Samsung Cable recommended)
Don't forget to post the result

From Custom to Stock - Bunch of errors

If you guys help me to go back successfully to stock, I'll make a guide to explain the process, maybe for all 3 models. I just need help on this one
I have an A2017G
So this is my fourth time trying to get back to stock. the first one resulted on a DFU brick. The second one was through MiFlash and the system had random reboots. The third, I flashed tron1's A2017G B04 Bootstack and a DrakenFX flashable zip (for the U, just wanted to try) and TWRP said that there was no system which turned out to be true... i had wiped system, data and caches before, but it seemingly installed okay...
I also tried to use MiFlash again and get B10, but it started to throw an error out of the blue (the specified cast is not valid, or something along the lines). I used it at least 4 times before.
So what zip should I use? I never tried flashing one of those update zips (I have full official B10 on the sdcard) but I believe they won't work. Please tell me if they do work...
again, if i manage to get SAFELY to stock and AVOID DFU I'll make a nice guide so that we stop asking. Most custom roms are flawed, for ex. Lineage has bad compatibility, Pure Nexus (the one I'm using now) has extreme, Galaxy Y grade lag, and RR simply works worse than stock (it's probably the best one of the bunch though).

i am in in the process of going back to stock(A2017), will let you know.
---------- Post added at 04:07 AM ---------- Previous post was at 03:14 AM ----------
I have followed all the tutorials but its failed and now i cant even install any zip in twrp , cant mount internal storage.. deive or resource busy and cant restore my LOS based rom.. same errors..

satish.yarramsetti said:
i am in in the process of going back to stock(A2017), will let you know.
---------- Post added at 04:07 AM ---------- Previous post was at 03:14 AM ----------
I have followed all the tutorials but its failed and now i cant even install any zip in twrp , cant mount internal storage.. deive or resource busy and cant restore my LOS based rom.. same errors..
Click to expand...
Click to collapse
well you can get to EDL and flash a full A2017 EDL package. I can't, not on this computer

Does EDL work?
Choose an username... said:
well you can get to EDL and flash a full A2017 EDL package. I can't, not on this computer
Click to expand...
Click to collapse
TWRP doesnt mount /Data
---------- Post added at 04:19 AM ---------- Previous post was at 04:16 AM ----------
Choose an username... said:
well you can get to EDL and flash a full A2017 EDL package. I can't, not on this computer
Click to expand...
Click to collapse
I tried Format system option in Wipe Menu, and that caused this ' Cnat mount /Data ' issue.

satish.yarramsetti said:
TWRP doesnt mount /Data
---------- Post added at 04:19 AM ---------- Previous post was at 04:16 AM ----------
I tried Format system option in Wipe Menu, and that caused this ' Cnat mount /Data ' issue.
Click to expand...
Click to collapse
well I meant use MiFlash, but I don't know if you should even think about getting out of TWRP in this state. No idea

Hey how to boot EDL mode
Choose an username... said:
well I meant use MiFlash, but I don't know if you should even think about getting out of TWRP in this state. No idea
Click to expand...
Click to collapse
Please help, how to boot EDL mode? please help i forgot

satish.yarramsetti said:
Please help, how to boot EDL mode? please help i forgot
Click to expand...
Click to collapse
I don't think you should when having TWRP loaded on your RAM and your system probably not there...
My DFU brick was just because of that
but if you insist, turn your phone off and hold the two volume keys, then connect the USB cable (it has to be connected to the PC obviously)

Still had TWRP
Choose an username... said:
I don't think you should when having TWRP loaded on your RAM and your system probably not there...
My DFU brick was just because of that
but if you insist, turn your phone off and hold the two volume keys, then connect the USB cable (it has to be connected to the PC obviously)
Click to expand...
Click to collapse
Man, still i had twrp and i can access internal storage. let me see if i can restore my rom
---------- Post added at 04:37 AM ---------- Previous post was at 04:34 AM ----------
satish.yarramsetti said:
Man, still i had twrp and i can access internal storage. let me see if i can restore my rom
Click to expand...
Click to collapse
Thanks God! Restore is in progress and if it works i wont try to get back to stock until someone find a sure shot method for that... waiting.. waiting..

satish.yarramsetti said:
Man, still i had twrp and i can access internal storage. let me see if i can restore my rom
---------- Post added at 04:37 AM ---------- Previous post was at 04:34 AM ----------
Thanks God! Restore is in progress and if it works i wont try to get back to stock until someone find a sure shot method for that... waiting.. waiting..
Click to expand...
Click to collapse
MiFlash is that method. It only has to be in the mood to work...

restore failed
Choose an username... said:
MiFlash is that method. It only has to be in the mood to work...
Click to expand...
Click to collapse
restore failed "extracttarfork() process ended with error=255"

satish.yarramsetti said:
restore failed "extracttarfork() process ended with error=255"
Click to expand...
Click to collapse
i had that error when I was backing up. Try to wipe all the partitions but internal (not necessarily format, go to settings and tick use rm -rf) maybe it works. if not try formatting with ext4

lol deleted

No, doesnt help
Choose an username... said:
lol deleted
Click to expand...
Click to collapse
No its doesnt help wiping all partitions.. same error

Mount -> Unmount /data
Wipe -> Format Data (the actual button next to 'Advanced Wipe')-> type 'yes' -> Reboot Recovery
Wipe -> Advanced Wipe -> Tick 'Data' -> Change File System -> EXT4
Try to mount /data
This has worked for me going from an LOS system back to Stock.
satish.yarramsetti said:
No its doesnt help wiping all partitions.. same error
Click to expand...
Click to collapse

QuantumFluxx said:
Mount -> Unmount /data
Wipe -> Format Data (the actual button next to 'Advanced Wipe')-> type 'yes' -> Reboot Recovery
Wipe -> Advanced Wipe -> Tick 'Data' -> Change File System -> EXT4
Try to mount /data
This has worked for me going from an LOS system back to Stock.
Click to expand...
Click to collapse
It might have worked post restart. I am unable mount internal storage or fash but Post restrat it worked

QuantumFluxx said:
This has worked for me going from an LOS system back to Stock.
Click to expand...
Click to collapse
could you tell us how you did to get to stock? What's your device, A2017G? What did you flash?
That's pretty much everything I want to know

A2017U from LOS to stock using the files on https://forum.xda-developers.com/showpost.php?p=68873482
The only reason I mentioned it when I have the United States model is because I have ran into a problem on multiple devices going from CyanogenMod to any sort of AOSP-based ROM without clicking that format data button. The first time I ran into the problem comma I could not mount my data partition.
I advised @satish.yarramsetti about this here. @satish.yarramsetti, can you confirm that the ZIP I linked you to in the other thread is the one you flashed and is booting?
Choose an username... said:
could you tell us how you did to get to stock? What's your device, A2017G? What did you flash?
That's pretty much everything I want to know
Click to expand...
Click to collapse

QuantumFluxx said:
A2017U from LOS to stock using the files on https://forum.xda-developers.com/showpost.php?p=68873482
The only reason I mentioned it when I have the United States model is because I have ran into a problem on multiple devices going from CyanogenMod to any sort of AOSP-based ROM without clicking that format data button. The first time I ran into the problem comma I could not mount my data partition.
I advised @satish.yarramsetti about this here. @satish.yarramsetti, can you confirm that the ZIP I linked you to in the other thread is the one you flashed and is booting?
Click to expand...
Click to collapse
I am Nuclear Rom(LOS Based) and tried to go back to stock. I have followed all tutorials but when i try to reboot, TWRP warned me that there is no OS. So i didn't reboot as it might remove TWRP ( it might have booted but not sure) ( i also flashed NO verify zip) , so i thought of formatting in wipe menu which caused a lot of problems like cant mount data & device busy errors . I tried to flash N boot loader and mod but every FLASH is getting failed. So i decided to restart and luckily i have TWRP and no os and my nandroid back up niether worked.
Finally i flashed Clean LOS.

Understood. I have received that same warning in the past after flashing stock. At any rate, if there's no OS installed, there's nothing to overwrite TWRP. The phone would just sit at the ZTE logo and you would have to hold Vol Up+Power to get back into TWRP. If you decided to try again, at least you know you can restore LOS if it doesn't work... Good luck.
satish.yarramsetti said:
I am Nuclear Rom(LOS Based) and tried to go back to stock. I have followed all tutorials but when i try to reboot, TWRP warned me that there is no OS. So i didn't reboot as it might remove TWRP ( it might have booted but not sure) ( i also flashed NO verify zip) , so i thought of formatting in wipe menu which caused a lot of problems like cant mount data & device busy errors . I tried to flash N boot loader and mod but every FLASH is getting failed. So i decided to restart and luckily i have TWRP and no os and my nandroid back up niether worked.
Finally i flashed Clean LOS.
Click to expand...
Click to collapse

QuantumFluxx said:
Understood. I have received that same warning in the past after flashing stock. At any rate, if there's no OS installed, there's nothing to overwrite TWRP. The phone would just sit at the ZTE logo and you would have to hold Vol Up+Power to get back into TWRP. If you decided to try again, at least you know you can restore LOS if it doesn't work... Good luck.
Click to expand...
Click to collapse
The restore is also not working i got some error 255 ... Strange thing is i got a warning like no OS after installing LOS but i booted.

Failed to root phone correctly and accidentally wiped everything. Please help!

I tried to root my phone using Moto G5 Plus toolkit. I failed to root it properly and I forgot to back up my system before attempting to root it. I failed to root it properly and Instead of having Motorola on my phone I have Team Win Recovery Project. I also keep getting a messages saying " Your device has been unlocked and can't be trusted ID:N/A will boot in 5 seconds." I don't know what to do. I believe I have wiped my whole phone. Is there a way to repair it? Can I fix it by reinstalling the factory stock firmware and drivers. I am try to solve this problem and fix the phone. My phone is a XT1687 Moto G5 Plus. I do not know where to get the stock or factory default software for the phone or how to reinstall it. Nor do I know how to remove the Team win Recovery project from my phone. Can someone help me. If you are able to can you tell me how to fix my phone.

You did it right you installed the twrp( team win recovery project) recovery. now download a rom on your memory card , wipe all data through recovery and install the rom through recovery.

ugupta100 said:
You did it right you installed the twrp( team win recovery project) recovery. now download a rom on your memory card , wipe all data through recovery and install the rom through recovery.
Click to expand...
Click to collapse
I downloaded a rom from android file host and placed the zip file on a micro sd card but I do not know how to install it. I have never used twrp before so I do not know what to do. I also would like to remove twrp if possible. Can you please assist me.

LeoG360 said:
I downloaded a rom from android file host and placed the zip file on a micro sd card but I do not know how to install it. I have never used twrp before so I do not know what to do. I also would like to remove twrp if possible. Can you please assist me.
Click to expand...
Click to collapse
Twrp is a custom recovery for custom roms. Removing it is not so easy process. Twrp recovery is better than stock recovery.
Now in twrp wipe your internal storage cache and data, don't wipe your external sd card. After wiping go to install in twrp select the rom you downloaded and then flash it.
---------- Post added at 11:54 PM ---------- Previous post was at 11:51 PM ----------
You can see the wipe and install options adjacent to each other.

ugupta100 said:
Twrp is a custom recovery for custom roms. Removing it is not so easy process. Twrp recovery is better than stock recovery.
Now in twrp wipe your internal storage cache and data, don't wipe your external sd card. After wiping go to install in twrp select the rom you downloaded and then flash it.
---------- Post added at 11:54 PM ---------- Previous post was at 11:51 PM ----------
You can see the wipe and install options adjacent to each other.
Click to expand...
Click to collapse
With your help I have managed to fix my phone and re-install the stock rom. However there is one problem which I hope you can help me with. Every time I turn off my phone and power it on again I get a message the says "Your phone is unlocked but can't be trusted. ID: bad key. Your device will boot in 5 seconds."
Can you help me fix this problem.

LeoG360 said:
With your help I have managed to fix my phone and re-install the stock rom. However there is one problem which I hope you can help me with. Every time I turn off my phone and power it on again I get a message the says "Your phone is unlocked but can't be trusted. ID: bad key. Your device will boot in 5 seconds."
Can you help me fix this problem.
Click to expand...
Click to collapse
Just flash a different bootlogo and you'll be good to go

psychopac said:
Just flash a different bootlogo and you'll be good to go
Click to expand...
Click to collapse
You have to flash a boot logo from adb. Search for g5 plus boot logo on xda

ugupta100 said:
You have to flash a boot logo from adb. Search for g5 plus boot logo on xda
Click to expand...
Click to collapse
I'm not sure if I am able to flash a boot logo. I can't turn on or off the OEM Unlocking option in the developers settings. Without OEM Unlocking I can't unlock the boot loader.
The OEM Unlocking option is completely grayed out. It appears to be locked. I can't tell if it is on or off. It might be locked in on mode.

LeoG360 said:
I'm not sure if I am able to flash a boot logo. I can't turn on or off the OEM Unlocking option in the developers settings. Without OEM Unlocking I can't unlock the boot loader.
The OEM Unlocking option is completely grayed out. It appears to be locked. I can't tell if it is on or off. It might be locked in on mode.
Click to expand...
Click to collapse
I think your bootloader is unlocked. Reboot to bootloader it will show if your bootloader is locked or not. If it is not then flash the bootlogo