Database Develop

[Q] HTC one completlywiped, cannot load ROM

Hi Everyone, Ive been going at this for days and been round and round on so many pages i'm just lost..
I have HTC one unlocked brought in AUS. Decided to play around with it and didn't do any sort of backup of the original system, unlocked the boot loader, installed CRW and tried a few roms for fun. So today I went and played around again trying to get the stock rom put back on so I can have OTA updates (stupid idea!!!) and now there is no OS installed on the phone...!
So far I have tried to push a zip to the phone with adb but apparently it can only be done when the OS is loaded. Used Hasson tool with no luck.
Essentially I can't load any ROM to the phone and it is just stuck between fastboot and the recovery mod (tried TWRP and CRW).
Ive looked at the RUU files on the website but theres no clear explanation on which one to choose. The htc website has no RUU update either.
Can someone please help with steps to get me back on track. If you need any info to help then please let me know ..
UNLOCKED
S-ON
P.S. i will let you know if I have previously tried what you suggest..

So can you get into recovery?

postfatal said:
So can you get into recovery?
Click to expand...
Click to collapse
Hi there, i can currently boot into TWRP (which is the most recent version I downloaded today)

1) Flash TWRP custom recovery
2) In recovery go to adb sideload
3) On PC type adb sideload yourrom.zip

jgt777 said:
Hi Everyone, Ive been going at this for days and been round and round on so many pages i'm just lost..
I have HTC one unlocked brought in AUS. Decided to play around with it and didn't do any sort of backup of the original system, unlocked the boot loader, installed CRW and tried a few roms for fun. So today I went and played around again trying to get the stock rom put back on so I can have OTA updates (stupid idea!!!) and now there is no OS installed on the phone...!
So far I have tried to push a zip to the phone with adb but apparently it can only be done when the OS is loaded. Used Hasson tool with no luck.
Essentially I can't load any ROM to the phone and it is just stuck between fastboot and the recovery mod (tried TWRP and CRW).
Ive looked at the RUU files on the website but theres no clear explanation on which one to choose. The htc website has no RUU update either.
Can someone please help with steps to get me back on track. If you need any info to help then please let me know ..
UNLOCKED
S-ON
P.S. i will let you know if I have previously tried what you suggest..
Click to expand...
Click to collapse
Try to adb sideload a rom. after flashing a custom recovery, download hasoon2000's toolkit from here: http://forum.xda-developers.com/show....php?t=2183942
place it on your desktop and then place your custom rom inside the folder. run the toolkit and use the function "adb sideload" to sideload the rom on your device. also choose "adb sideload" in your custom recovery while doing this.
it should work

If you get into recovery then as everyone is saying sideload a ROM onto your device. There are loads of guides of how to do that.

tash2013 said:
1) Flash TWRP custom recovery
2) In recovery go to adb sideload
3) On PC type adb sideload yourrom.zip
Click to expand...
Click to collapse
You know what, i need a kick in the head..
Have previously opened TWRP, went to sideload and wondering why it has done nothing - this time I see the "slide to sideload" option.
Its currently sending right now. If this upload works do I now just have to select the install option and choose the ZIP?

jgt777 said:
You know what, i need a kick in the head..
Have previously opened TWRP, went to sideload and wondering why it has done nothing - this time I see the "slide to sideload" option.
Its currently sending right now. If this upload works do I now just have to select the install option and choose the ZIP?
Click to expand...
Click to collapse
In recovery apply "slide to sideload" , recovery will be to wait command from PC.
On PC type "adb sideload rom.zip" , your rom.zip must be in the same folder with adb.exe.

Pushing the thanks button for everyone who replied, such a simple thing as sliding the abd sideload button to the right to detect it...
Thank you all so much

jgt777 said:
You know what, i need a kick in the head..
Have previously opened TWRP, went to sideload and wondering why it has done nothing - this time I see the "slide to sideload" option.
Its currently sending right now. If this upload works do I now just have to select the install option and choose the ZIP?
Click to expand...
Click to collapse
Yes.
Sent from my HTC One using xda app-developers app

I had done exactly the sme as the OP but unfortunately for me there has been no fix yet, still working on it. I have done everything i can think of except to flash a recovery backup or RUU but the one i need is not avaiable

twerg said:
I had done exactly the sme as the OP but unfortunately for me there has been no fix yet, still working on it. I have done everything i can think of except to flash a recovery backup or RUU but the one i need is not avaiable
Click to expand...
Click to collapse
could you explain your problem more detailed please?

[Q] I just dun goofed :(

Hey guys, long time lurker and now first time poster. Shame it has to be something very stupid.
So anyways, I wanted to flash the latest CM10.2 Unofficial build so I did the usual and downloaded the zip & gapps to my phone. But upon wiping my phone via TWRP I accidentally left the wipe userdata part checked and ... well now I have no OS installed as well as no zip's :/
I have TWRP installed so I thought why not sideload it, however when I go to advanced -> adb sideload it never starts up. This is the log:
Updating partition details...
Starting ADB sideload feature...
Click to expand...
Click to collapse
And it just stays there
I know that my ADB works as I have S-OFF & unlocked the bootloader and flashed the latest 1.54.0000 hboot so I can definitely use it, I just don't understand why it doesn't let me sideload for some reason.
Either way, I have full access to fastboot & TWRP recovery so i'm hoping this is a pretty simple thing to fix ... right?
Can anybody point me to the right direction?
Details:
No OS installed.
Access to TWRP & fastboot.
S-OFF, Modified Hboot 1.54.0000 (SuperCID) & Unlocked bootloader.
Windows 8 64-bit, drivers all work.
Latest SDK with all the binaries installed.
P.S. when I connect and try and use adb devices it doesn't recognise my device, and the cmd window gives the following when I try the sideload command:
Error: device not found.
Click to expand...
Click to collapse
Sounds like a driver issue to me but it doesn't make sense that the drivers would suddenly stop working ???
Here are screenshots of odd device behaviour when switching from fastboot to recovery (please copy & paste, I don't have enough posts to post images yet):
i.imgur.com/V79DFFA.jpg
i.imgur.com/MKD5C9U.jpg

Bump for help

I can't seem to get sideload to work in TWRP at the moment either. CWM works fine though, try flashing that and use the sideload feature.
Sent from my HTC One using xda premium

redbull123 said:
I can't seem to get sideload to work in TWRP at the moment either. CWM works fine though, try flashing that and use the sideload feature.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Tried that already, same issue in not detecting the device. I'm downloading these drivers in a hope to fix something.
Thanks for the reply
EDIT:
Finally got sideloading in TWRP to work, it turns out it was a driver issue :/
Anyways, these are the drivers that worked:
androidfiles.org/hasoon2000/getdownload.php?file=HTC%20Drivers/HTCDriver.exe

why is everyone always wiping their storage these days? just use CWM next time and you wont accidentally do this again..

IINexusII said:
why is everyone always wiping their storage these days? just use CWM next time and you wont accidentally do this again..
Click to expand...
Click to collapse
TWRP is much better for people who know what they are doing. There are more options and also a built in file manager. Also, the wipe button in TWRP wipes the 3 main partitions at once (data/cache/dalvik), so he must have actually selected internal sdcard from the advanced menu, and I have no idea why he would do that...

Doing the slider is all anyone needs to do in twrp to wipe yet I read more posts about people wiping with twrp than any other problem in these forums

[tutorial][updating TWRP for 4.4 compatibility]

Ive noticed many people with older TWRP versions having problems with the updater script when installing 4.4 roms you need to be on the latest version of twrp (CWM may also need to be on a recent version). This tutorial will cover TWRP. Goo manager will not work for installing the latest TWRP recovery version on grouper. The following will give you the basics on how to use fastboot to flash a recovery.img (In this case twrp)
Things you will need:
A PC
Android SDK http://developer.android.com/sdk/index.html
TWRP recovery.img for grouper http://techerrata.com/browse/twrp2/grouper
A basic understanding of terminal/command prompt
You will need a PC and the android SDK (SDK http://developer.android.com/sdk/index.html) for fastboot to push the recovery file. TWRP can be found here (http://techerrata.com/browse/twrp2/grouper) you need the 2.6.3.0 version. Extract your android sdk and move your twrp image file (openrecovery-twrp-2.6.3.0-grouper.img) to the platform-tools folder in the sdk (This is where fastboot/adb are). For simplicity's sake rename your twrp file to recovery.img Enter command prompt or terminal depending on what OS you are using (windows/linux) and navigate to to your platform-tools folder in the SDK folder (where you should have moved your recovery.img) using the cd command. (plug device in) Once there check to see if you device is connected and seen with the adb devices command hopefully you will see a wonky alpha numeric code with "device" after it. If you dont you need to enter developer setting to enable adb. You do that by going into settings/about tablet and tapping build number 7 times. That should give you a developer options in settings check to make sure USB debugging is enabled. If all is well reboot your device into the boot loader with the adb reboot bootloader command once your device is at the bootloader check fastboot with fastboot devices you should see another wonky output with "fastboot" after it. The final command to push your new twrp image will be fastboot flash recovery recovery.img You should see some output saying how long it took to push the file it should not take that long. That should cover it! Now you should be good to go with the 4.4 rom's floating around.
There are many tutorials online explaining this process I just thought customizing it to the grouper would help those less comfortable with adb/fastboot. It's always a good idea to know how to use these tools you never know when you might need to use them. Anyone with question's feel free to ask.

Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app

blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That will work. But knowing your way around adb/fastboot can't hurt. There won't always be a GUI to do everything for you.

blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't know of flashify, awesome. Thx, really fast and easy method. Best thing is I didn't even need my pc for it

Thanks for the tutorial but surely this belongs in q&a, help etc not android development ;p
Sent from my Nexus 4 using XDA Premium 4 mobile app

Actually it's suited to the General section (guides and all). I appreciate you advising the fastboot method (I use it too), but it can b a pain for people who don't have their devices configured (configuring it can be a pain sometimes too). Flashify, as one member said, is a great alternative. BUT you *may* brick your device if you flash something to the wrong block device (possibility of that happening to an expert user: 0.0001%; possibility of that happening to a new user: 1%). Just my two cents.

I agree guys this should be in general. I've never posted anything but a build and didn't even think about it. Do I need to get a mod to move it? As for flashify sounds like a great tool. I've never had the pleasure of using it but if it works and people are comfortable with it more power to it. Personally fastboot is what I'm comfortable with it might seem a little in depth but really its quite simple especially if you use adb for logcats and are setup.

OP No worries, moved and thank you.

To flash 4.4 ROMs one could follow this tutorial, or one could simply flash this .zip of the latest version of CWM:
http://forum.xda-developers.com/showpost.php?p=46053223

So, i've bricked it already.
Hello experts and knowledgeable persons!
First, i'm a noob.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery, copied to PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated.
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
So now what do I do, as I don't want to make things worse. I am doing a factory reset before installing. The error i'm getting is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"

ziffius said:
Hello experts and knowledgeable persons!
First, i'm a noob.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery, copied to PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated.
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
So now what do I do, as I don't want to make things worse. I am doing a factory reset before installing. The error i'm getting is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"
Click to expand...
Click to collapse
I'm sure this is not what you want to hear but if all else fails push the factory.IMG you will be starting from square one. You can try pulling your backups off but might as well start over for 4.4

blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much for this recommendation. Really nice. Simple and took out all the nervousness of using the computer to push these files etc.
REally truly best for flashaholics.

question
Won't it work too if you just flash the zip from twrp itself? I'm running 2.6.3.2 and I read somewhere that i can simply install the new version (2.7.0.0.) zip from the recovery itself..Is it right??

Ergina95 said:
Won't it work too if you just flash the zip from twrp itself? I'm running 2.6.3.2 and I read somewhere that i can simply install the new version (2.7.0.0.) zip from the recovery itself..Is it right??
Click to expand...
Click to collapse
Did you ever try just flashing it and if so, did it work?

for some reason i cannot download the twrp ..it stuck at 99%
tried 2 version of twrp..hurm

Mookie2014 said:
Did you ever try just flashing it and if so, did it work?
Click to expand...
Click to collapse
yeap! did it! worked perfectly :good: just flash zip updates through the recovery

No OS installed, unable to adb push

I can't seem to find a solution to the problem I am having and I spent 5 hours looking at many threads over many forums.
I was trying to restore my stock GPE in order to send to repair, but I accidentally wiped of everything and ended up with no OS installed. I tried then using fastboot/adb to install through recovery, (TWRP) I am able to use fastboot however adb will not see my device therefore I am not able to push any .zip to install GPE Android 4.3
Tried flashing stock.zip, but get the error "remote 12: signature verify fail", then I noticed that it is "S-On"
I am hopeless right now, but I know there is something that can be done or I am missing/screwing something.
Is there any other way in which I can restore my HTC One to GPE Android as initially shipped? I just need to fix this because I have a repair order going.
Any help will be highly appreciated.

In recovery you can see your sd card?
adb drivers are ok?
When the phone is in recovery the pc can detect it?

Guich said:
In recovery you can see your sd card?
adb drivers are ok?
When the phone is in recovery the pc can detect it?
Click to expand...
Click to collapse
In recovery I do see /sdcard, however HTC One does not have sd card.
I tried downloading some drivers, maybe not the most up to date ones, do you have a link where I can download these?
I did not see if the PC could detect it while in recovery, I will check that and let you know.

vaguitovera said:
In recovery I do see /sdcard, however HTC One does not have sd card.
I tried downloading some drivers, maybe not the most up to date ones, do you have a link where I can download these?
I did not see if the PC could detect it while in recovery, I will check that and let you know.
Click to expand...
Click to collapse
Try to use this adb drivers.
However, let me know if, in device manager, you can see your one.

I have noted that CWM shows ADB drivers quickly than TWRP... perhaps try flashing CWM, adb push your_rom.zip /sdcard, and then flash TWRP if necessary, or just install using CWM..

[Q] No OS, not rooted

So, my dad bought an HTC One from a seller on EBay. The phone was originally on Sprint, but it was unlocked; when he got the phone, it didn't work initially, and after he and my mom trouble shooted for a bit, they got it working. Those are the only details I know; I don't know what the problem was.
After they got it working, my dad did something to the phone, and it froze up completely. He let the battery drain, and then I went to work. When I got back, he had wiped the OS, and the only thing it can do is boot into TWRP v2.5.0.0. I don't know what else he did, or what else he tried.
Here's my problem; I can't flash a ROM on it, because, somehow, it's unrooted. Every time I power it down, TWRP says "Your device is unrooted." I researched a bit on how to root it from that point; but, to do that, you need an OS, which somehow, I do not have. It seems like, to get the phone rooted, I need an OS, and to get an OS, I need it rooted.
So, I tried do use the ADB sideload that a lot of people recommended. I downloaded the SDK packages, I ran Command Prompt, I've tried it at least 30 times by now, but it will not pick up the phone. When I do the "adb devices" command, it has nothing listed. I tried pushing the ROM anyway, just to see, and it fails because, again, "no devices found." I've tried wiping the cache and dalvik, rebooting into recovery, and trying the rooting and the ADB stuff over again, numerous times, and neither one works.
The only thing I haven't tried is doing a RUU; but, before I do that, I decided to ask here, and get some help. The RUU seems extremely complicated, and I don't even know if it will work.
I'll be the first to admit, I really don't know much about Android, or any of this. I've flashed ROMs, and that's about it. So, can anyone tell me what I should try, and if the RUU would work? If it would, can you link me to a guide?
Thank you!

If you hold down the power button while pressing the vol- button, does it load the Bootloader, a white screen with options.

Are you using Windows 8.1? Because if you are fastboot only works on HTC devices with 1.54 and up on 8.1. I was messing with my DNA this weekend and realized that adb picks it up if I'm in twrp but if I'm in the boot loader I get no device found. I also have an HTC one which isn't rooted and adb can pick it up in Windows 8.1 in normal debug mode and while I'm also in the boot loader. I'm using usb 2.0 so make sure that is what you plug it in to. Otherwise, there are driver issues with adb and fastboot in 8.1 and htc has not updated their drivers for it.
Other option is to download a live CD of Linux and try sideloading a Rom through there.
Sent from my HTC6435LVW using Tapatalk

Awsom0 said:
Here's my problem; I can't flash a ROM on it, because, somehow, it's unrooted. Every time I power it down, TWRP says "Your device is unrooted." I researched a bit on how to root it from that point; but, to do that, you need an OS, which somehow, I do not have. It seems like, to get the phone rooted, I need an OS, and to get an OS, I need it rooted.
Thank you!
Click to expand...
Click to collapse
If you're problem is not having root , then try flashing a supersu.zip through recovery. That should enable root access you're able to enter recovery.

I thought twrp provided root, anyways theres any option in advanced I think you can sideload a rom via adb push. It's something like adb sideload "name of rom sideloading.zip" and I don't think you need to be rooted to sideload.
Sent from my HTC one using xda app-developers app

Root doesn't come with recovery and can be lost sometimes upon flashing a new rom. That's why the supersu.zip exists.
Sent from my HTC One using xda app-developers app
---------- Post added at 05:32 AM ---------- Previous post was at 05:30 AM ----------
If the supersu.zip doesn't work, then you'll DEFINITELY have to find a way to get ADB working. Because that'll be your only hope
Sent from my HTC One using xda app-developers app

Best ruu based info here
forum.xda-developers.com/showthread.php?t=1672425
Sent from my HTC one using xda app-developers app
---------- Post added at 05:58 AM ---------- Previous post was at 05:45 AM ----------
twrp does offer root if your not rooted
teamw.in/project/twrp2
Under change log taken right from there page
Added a root checker and offer to install SuperSU if the device isn't
already rooted
Sent from my HTC one using xda app-developers app

DEFNUB said:
Best ruu based info here
forum.xda-developers.com/showthread.php?t=1672425
Sent from my HTC one using xda app-developers app
---------- Post added at 05:58 AM ---------- Previous post was at 05:45 AM ----------
twrp does offer root if your not rooted
teamw.in/project/twrp2
Under change log taken right from there page
Added a root checker and offer to install SuperSU if the device isn't
already rooted
Sent from my HTC one using xda app-developers app
Click to expand...
Click to collapse
Yes upon initial install. But I know some ROMs which say you lose that root access after flashing it and tell you to flash the supersu.zip in order restore it.
Sent from my HTC One using xda app-developers app

Wouldn't that defeat the purpose of having a root checker if their root files could be deleted? I'm pretty sure it's built into the recovery. I could be dead wrong, never ran into a custom rom that's never been with out root.
Sent from my HTC one using xda app-developers app

DEFNUB said:
Wouldn't that defeat the purpose of having a root checker if their root files could be deleted? I'm pretty sure it's built into the recovery. I could be dead wrong, never ran into a custom rom that's never been with out root.
Sent from my HTC one using xda app-developers app
Click to expand...
Click to collapse
i dont get why you need Root to install a ROM? flash a ROM in TWRP by going to Advanced -> ADB Sideload. have a ROM on your PC where the adb and fastboot files are and type in "adb sideload name_of_rom.zip"
select reboot system when it is flashed, when it asks for root select "Do Not Install", and it should reboot into your flashed rom

IINexusII said:
i dont get why you need Root to install a ROM? flash a ROM in TWRP by going to Advanced -> ADB Sideload. have a ROM on your PC where the adb and fastboot files are and type in "adb sideload name_of_rom.zip"
select reboot system when it is flashed, when it asks for root select "Do Not Install", and it should reboot into your flashed rom
Click to expand...
Click to collapse
My initial understanding was that OP could not get adb working to sideload a Rom. Usually twrp will ask upon reboot to install su if it detects root has been lost.
Sent from my HTC6435LVW using Tapatalk

If you can't get adb to work, then you should buy a USB-OTG adapter.
With the USB otg you would be able to connect a USB-Stick to the one and mount it in the recovery.
Gesendet von meinem HTC One mit Tapatalk

Or use a ubuntu live CD.
Sent from my HTC6435LVW using Tapatalk

I forgot to mention, after I could not get the sideload to work, I got an OTG cable, which does work.
profixit said:
If you hold down the power button while pressing the vol- button, does it load the Bootloader, a white screen with options.
Click to expand...
Click to collapse
Yes. After I get to the Bootloader, the only place I can go is into Recovery.
BadAzDB said:
If you're problem is not having root , then try flashing a supersu.zip through recovery. That should enable root access you're able to enter recovery.
Click to expand...
Click to collapse
I downloaded a file called "UPDATE-SuperSU-v1.86.zip" from a website called "chainfire"; I'd post a link, but I can't do that until I hit 10 posts.
Then I installed it, and it was successful. Then I tried installing a ROM; and it failed again. Then I wiped everything, rebooted, re-installed the SuperSU, rebooted, and tried installing the ROM; it failed again. Also, every time I restart, TWRP still says it is not rooted, and gives the option to root it. I always opt to root it, but it doesn't seem to do anything.
I'm also noticing, when I try and flash the ROM, it does this:
"Updating partition details...
Installing '/usb-otg/ROM.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/usb-otg/ROM.zip'
Updating partition details..."
Could it have something to do with this MD5 check? Or maybe this Zip signature verification?

Awsom0 said:
I forgot to mention, after I could not get the sideload to work, I got an OTG cable, which does work.
Yes. After I get to the Bootloader, the only place I can go is into Recovery.
I downloaded a file called "UPDATE-SuperSU-v1.86.zip" from a website called "chainfire"; I'd post a link, but I can't do that until I hit 10 posts.
Then I installed it, and it was successful. Then I tried installing a ROM; and it failed again. Then I wiped everything, rebooted, re-installed the SuperSU, rebooted, and tried installing the ROM; it failed again. Also, every time I restart, TWRP still says it is not rooted, and gives the option to root it. I always opt to root it, but it doesn't seem to do anything.
I'm also noticing, when I try and flash the ROM, it does this:
"Updating partition details...
Installing '/usb-otg/ROM.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/usb-otg/ROM.zip'
Updating partition details..."
Could it have something to do with this MD5 check? Or maybe this Zip signature verification?
Click to expand...
Click to collapse
there's an option in TWRP where you can toggle signature validation off/on. try and turn it off then run the zip.

Root is needed AFTER you install your ROM. I think you have a corrupted zip file. Sideload a ROM but after you download it check the md5 to see if its downloaded correctly. You needed to read more bro. Sounds to me you are very new to this.

IINexusII said:
i dont get why you need Root to install a ROM? flash a ROM in TWRP by going to Advanced -> ADB Sideload. have a ROM on your PC where the adb and fastboot files are and type in "adb sideload name_of_rom.zip"
select reboot system when it is flashed, when it asks for root select "Do Not Install", and it should reboot into your flashed rom
Click to expand...
Click to collapse
You actually don't need root to flash a Rom. Sounds like a bad download like the other dude said.
Sent from my HTC one using XDA Premium HD app

You should be able to install any rom you want as long as you're able to flash zips from the recovery, even if there's no OS installed, that just means the system and boot partitions are empty and they can be easily filled with a rom zip. And root is something that comes with the rom or something you can install after you flash a rom. You don't need root to flash if you can already boot into TWRP.