Database Info

Restoring to stock

Some months ago I followed guides here to SuperCID, s-off and install a custom ROM. The past few days my touch screen has become unresponsive, at first this was fixed by reflashing the ROM, but now, nothing will fix it, and the touch screen is completely unresponsive. So it seems I will have to return it to the shop to send off for repair. Of course I don't want them to have any reason to say it was the custom ROM that has caused it, warranty void blah blah so need to restore it to stock.
So far I have re-flashed with a stock ROM and changed the CID to what it was, and s-on. I can't remember whether I changed the MID, currently it is PG58*****, though I believe it should be PG5813001, and I'm not sure how to go about changing this (or if it needs changing, will they look into that?)
Another thing I'm unsure of, I downloaded the ROM from here: http://forum.xda-developers.com/showthread.php?t=1074559 I don't know if these ROMs are rooted or not? Is there any way to tell? Or is it a safe assumption they are not?
And finally, hboot, before flashing the stock ROM, this was 1.17, now it is 1.18. Is there anything in here that might suggest the phone has been tinkered with in ways they don't like? I just want to make sure I have covered everything so they don't immediately refuse to repair. If I have missed anything else please let me know.
Thanks.
Edit: I've also read about flashing stock recovery, though this may be included in the the stock ROM RUU I used, can someone confirm?

None of the 130 viewers have any advice on this one?

HB489 said:
Some months ago I followed guides here to SuperCID, s-off and install a custom ROM. The past few days my touch screen has become unresponsive, at first this was fixed by reflashing the ROM, but now, nothing will fix it, and the touch screen is completely unresponsive. So it seems I will have to return it to the shop to send off for repair. Of course I don't want them to have any reason to say it was the custom ROM that has caused it, warranty void blah blah so need to restore it to stock.
So far I have re-flashed with a stock ROM and changed the CID to what it was, and s-on. I can't remember whether I changed the MID, currently it is PG58*****, though I believe it should be PG5813001, and I'm not sure how to go about changing this (or if it needs changing, will they look into that?)
Another thing I'm unsure of, I downloaded the ROM from here: http://forum.xda-developers.com/showthread.php?t=1074559 I don't know if these ROMs are rooted or not? Is there any way to tell? Or is it a safe assumption they are not?
And finally, hboot, before flashing the stock ROM, this was 1.17, now it is 1.18. Is there anything in here that might suggest the phone has been tinkered with in ways they don't like? I just want to make sure I have covered everything so they don't immediately refuse to repair. If I have missed anything else please let me know.
Thanks.
Edit: I've also read about flashing stock recovery, though this may be included in the the stock ROM RUU I used, can someone confirm?
Click to expand...
Click to collapse
To Flash stock recovery read 2 in HERE I believe these ROMs are not rooted, to check just look for SuperSU or Superuser app, if it is not installed you are not rooted. Don't worry at all they'll never find out you rooted your phone, usually they never check. Read THIS guide it has the answer to all your questions regarding revert to stock

elvisypi said:
To Flash stock recovery read 2 in HERE I believe these ROMs are not rooted, to check just look for SuperSU or Superuser app, if it is not installed you are not rooted. Don't worry at all they'll never find out you rooted your phone, usually they never check. Read THIS guide it has the answer to all your questions regarding revert to stock
Click to expand...
Click to collapse
Thanks, though unfortunately I can't check what apps are installed due to the touch screen being unresponsive. But if that's not something they'll look into then fair enough.
The second thread doesn't quite answer everything (whether the ROMs are rooted for example), however, the first thread details extracting stock recovery from an RUU, so I guess that means I don't need to worry about that as it would have been flashed with the ROM.
One other thing - do they require the SD card to be sent also? Is there anything on there that should be removed? Any data relating to apps that use root privileges might raise an eyebrow; is it safe to do a reformat of the SD card? I'm not sure how much is on there that is vital the system.
Thanks for your answer.

HB489 said:
Thanks, though unfortunately I can't check what apps are installed due to the touch screen being unresponsive. But if that's not something they'll look into then fair enough.
The second thread doesn't quite answer everything (whether the ROMs are rooted for example), however, the first thread details extracting stock recovery from an RUU, so I guess that means I don't need to worry about that as it would have been flashed with the ROM.
One other thing - do they require the SD card to be sent also? Is there anything on there that should be removed? Any data relating to apps that use root privileges might raise an eyebrow; is it safe to do a reformat of the SD card? I'm not sure how much is on there that is vital the system.
Thanks for your answer.
Click to expand...
Click to collapse
No the ROMs in the second post are not rooted they are stock. The whole point of the post is to restore stock( read 3. RUU to restore stock). Stock recovery is smth else from stock ROM. You also need stock recovery to install OTA updates from google. Use Android Recovery Manager to download and install your stock recovery. Than in fastboot the stock recovery.img. I can't assure you that they won't notice you were rooted, but they usually don't. Keep in mind that when you unlocked your bootloader you accepted to void your warranty, and your serial number is in HTCs website. (theoretically) you can never be sure they won't discover you, but practically installing stock ROM, stock recovery, locking bootloader and getting back to s-on is enough to not get spotted
And you can format the SD Card if you want, you made a fresh install so there shouldn't be any files regarding it, just the files from the old system, but do a backup first just in case

elvisypi said:
No the ROMs in the second post are not rooted they are stock. The whole point of the post is to restore stock( read 3. RUU to restore stock). Stock recovery is smth else from stock ROM. You also need stock recovery to install OTA updates from google. Use Android Recovery Manager to download and install your stock recovery. Than in fastboot the stock recovery.img. I can't assure you that they won't notice you were rooted, but they usually don't. Keep in mind that when you unlocked your bootloader you accepted to void your warranty, and your serial number is in HTCs website. (theoretically) you can never be sure they won't discover you, but practically installing stock ROM, stock recovery, locking bootloader and getting back to s-on is enough to not get spotted
And you can format the SD Card if you want, you made a fresh install so there shouldn't be any files regarding it, just the files from the old system, but do a backup first just in case
Click to expand...
Click to collapse
Thanks again. If I recall correctly I used revolutionary, not HTC dev so I don't think they'll have my imei? Android recovery manager doesn't have the correct version for my phone, but further down the post it another method is extracting the recovery from the RUU, which is why I assumed stock recovery would have been installed when I flashed the RUU. I guess there is no harm in manually flashing the recovery to be sure though.

HB489 said:
Thanks again. If I recall correctly I used revolutionary, not HTC dev so I don't think they'll have my imei? Android recovery manager doesn't have the correct version for my phone, but further down the post it another method is extracting the recovery from the RUU, which is why I assumed stock recovery would have been installed when I flashed the RUU. I guess there is no harm in manually flashing the recovery to be sure though.
Click to expand...
Click to collapse
No HTCdev is not a recovery, it's the only way of unlocking your bootloader, which you have done for sure. But don't worry I assure you they don't go so deep. There's nothing wrong in flashing manually the recovery. Good luck

[Q] HTC Boot Loop and no signal using recovery

Hello All,
I will start this thread with the obligatory "Im new to rooting...." sentence but over the last 2 or so weeks have been doing my research between multiple sites (including this one), getting frustrated at how many "How to...but before you do" guides there are out there adn you tube videos but have finally managed to perm root and S-Off my UK Vodafone HTC Sensation.
I have flashed clockwork recovery without a hitch and managed to download the Cynaogen Rom without to much difficulty.
The problem:
While looking for overclocking ROMs, decided that the Virtuous Sensation ROM might be the one for me.
While doing further research, I discovered that I would need to flash the new PG58IMG.zip Firmware before the ROM would work. To do this, I would potentially be required to SuperCID, which I also did.
SuperCID complete and Firmeware flashed (and then removed from the SD card) I wiped the phone (several times following instructions on this site) and then installed the Virtuous ROM.
Now I get stuck on boot loop with the blue "V" showing for a about a second and then restarting.
Following some further internet checking, I found it may be a bad download of the ROM so downloaded again but the same thing happened. I also downloaded a different Virtuous ROM to confirm it was the Virtuous Sensation ROM that was corrupt but the other ROM got stuck on boot loop, albeit, the blue "V" now shoed for about 5 seconds.
I decided to load a recovery and revert back to the Cynaogen ROM except......sometimes its stuck on boot loop and other times it loads but I have no network coverage.
I have two questions:
Why did the new Virtuous ROM not work with the recommended firmware?
and
How can I restore my phone? I am guessing this problem may be the new firmware but I have read that this one works with Gingerbread and ICS?
Any help would be appreciated...preferably in a non "PHD in IT required" way.
Thanks in advance if anyone can help.

mostly it might be because of Firmware
what firmware you installed (my guess is 3.24 as you said works for both ICS and GB )
but i suggest you to use 3.33 firmware for ICS or above roms and 1.17 For GB roms
here is the firmware thread

OK, just tried flashing the ICS firmware (thanks for reply) from the link you posted, wiped the phone, cache etc and reinstalled ROM.
I get stuck on boot loop but the blue "v" does load for a little longer now.
From doing some more reading I have seen people saying to check MD5 match. Would someone mind explaining what ths is and how to do it?

OK, ignore the MD5 thing, i searched and found and its a match for all downloads.
ROM is an MD5 match also.
Tried all firmware and still stuck on boot loop.....
One thing I have noticed is that when I load usig the vol down + power, it sates that the 58IMG is "no image or wrong image"....could this be anything to do with it?

ssjghost said:
OK, ignore the MD5 thing, i searched and found and its a match for all downloads.
ROM is an MD5 match also.
Tried all firmware and still stuck on boot loop.....
One thing I have noticed is that when I load usig the vol down + power, it sates that the 58IMG is "no image or wrong image"....could this be anything to do with it?
Click to expand...
Click to collapse
That's generic bootloader function... So its common.. The searching for PG58IMG thing...
Now the best and most effective way is to first cleanup everything usig ruu.. Search for "ruu guide and info" thread by kgs1992 in sensation general section... Use that.. Find the proper ruu and flash it.. Check whether the stock rom(ruu) is flashing or not..If flashing then flash custom recovery and flash your custom rom again
Sent from my HTC Sensation using xda premium

Question
I have checked through a few forums and just want to clarify something before I go down the RUU route:
Will flashing the RUU to stock mean I lose S-Off or perm root? You say I will have to flash a custom recovery image again so I guess that means flashing clockworkmod through HBoot but will I then be expected to flash further firmware?
Thanks, Ill give the RUU thing a go.
I tried all the firmware with te Virtuous ROM and nothing worked but then one of the bottom firmware donloads (3.24 I think, cant remember know following multiple downloads) and booted the recovery.
Now I have signal again!
Thanks for advice, I will try the RUU thing....
Cheers

ssjghost said:
Question
I have checked through a few forums and just want to clarify something before I go down the RUU route:
Will flashing the RUU to stock mean I lose S-Off or perm root? You say I will have to flash a custom recovery image again so I guess that means flashing clockworkmod through HBoot but will I then be expected to flash further firmware?
Thanks, Ill give the RUU thing a go.
I tried all the firmware with te Virtuous ROM and nothing worked but then one of the bottom firmware donloads (3.24 I think, cant remember know following multiple downloads) and booted the recovery.
Now I have signal again!
Thanks for advice, I will try the RUU thing....
Cheers
Click to expand...
Click to collapse
RUU means everything to stock except SOFF ..so you would lose custom recovery, perm root .but the best part is as you still have SOFF ..you can just flash a custom recovery again ..and flash su zip for perm root again ..done voila
and SOFF means ..yes you can flash any firmware

Thanks for all you help mate, in the end i found Cyanogen 10 ROM which does everything I want so followed all instructions and works fine now.
Thanks again for being patient with a nub......much appreciated!:laugh::laugh::laugh::laugh:

[Q] Rooted ICS to JB - check my sanity please :)

After two weeks of forum crawling and surviving 2 soft-bricking incidents, I've finally decided to reach out for help from the experts :crying:
Currently I have an ATT HOX, unlocked/rooted/SuperCID - running stock ICS (4.0.4).
My goal is to get JB on it and then flash to Blade ROM (I tried flashing to Blade with ICS - OOPS!)
Even though the info is on the forums - it's not all together in a streamlined format for me to follow - I feel I could get lost and screw it up (again)
From what I gathered from reading - here is what I "think" I need to do from my current phone state:
1. Facepalm S-Off
2. Install OTA Rootkeeper then backup root
3. Flash stock recovery
4. Re-Lock Bootloader
5. Flash OTA ATT JB.zip using stock recovery
6. Unlock Bootloader
7. Flash TWRP
8. Restore backup root with OTA RK
9. Flash Blade ROM
Can someone please check my thinking and make sure I'm not missing something?
Or any recommendation of an easier process? I feel I'm going to get lost somewhere in those steps and end up in Oz.
Or maybe a recommendation on an awesome ICS Rom? (so I can avoid confusing myself)
I'm terrified of another 3AM morning and a bricked-out HOX.
Thanks in advance!

Do you mean this rom: http://forum.xda-developers.com/showthread.php?t=2134328?
Because that's a rom for the quad-core Tegra One X. If you've been doing that, it's no wonder you got bricked.
You don't need OTA Rootkeeper. You can just flash a rooted rom.

2 major points:
1) As already mentioned, Blade is not for our phone, its for the quad core One X. Stay within this forum section. If you are looking at any XDA thread that just says "HTC One X" (no mention of "AT&T, Rogers" etc.) near the top of the screen, you are in the wrong section. Stick to the forum section that mentions AT&T. Flashing a ROM for the quad core version won't work, and might also hard brick your phone.
2) Aside from S-Off which is a good idea) you don't need to mess with any of the stuff you mentioned (Rootkeeper, stock recovery, OTA zip) in order to flash a JB based custom ROM if you are already bootloader unlocked and have TWRP. With S-off, just flash the ROM. If S-on, just flash the ROM, then flash the boot.img with fastboot (if hboot 1.14 or higher).
I'm not sure how you got the notion that you need to do all these other steps (maybe some process for the quad core forum?).

redpoint73 said:
I'm not sure how you got the notion that you need to do all these other steps (maybe some process for the quad core forum?).
Click to expand...
Click to collapse
<---- desperate noob
...and I also came from the original Samsung Vibrant. With that phone, I also had the idea that I could only use a ROM based of the current android version. Hence the carry over of thought from that side.
I can't believe I lost sleep over the simplicity of it all.
But.... just to make sure I understand this correctly - Even if I have ICS currently installed, I can flash a JB based ROM without issues?
Thanks a ton guys!

razorc03 said:
But.... just to make sure I understand this correctly - Even if I have ICS currently installed, I can flash a JB based ROM without issues?
Click to expand...
Click to collapse
Correct you can flash it.
But some people have been having issues on JB coming from older firmware. If you have problems later, then ruu'ing and updating is warranted. Right now it's overkill.

iElvis said:
Correct you can flash it.
But some people have been having issues on JB coming from older firmware. If you have problems later, then ruu'ing and updating is warranted. Right now it's overkill.
Click to expand...
Click to collapse
Would I be able to RUU to a stock JB? Or would I have to start from stock ICS again?

razorc03 said:
Would I be able to RUU to a stock JB? Or would I have to start from stock ICS again?
Click to expand...
Click to collapse
There are no JB ruu's as far as I know. But you can run the 2.20 ruu and then flash the 3.18 ota, then unlock again and reflash everything. That's what I did. Whole process took about half an hour and wasn't complicated. Just be sure you're s-off.

iElvis said:
There are no JB ruu's as far as I know. But you can run the 2.20 ruu and then flash the 3.18 ota, then unlock again and reflash everything. That's what I did. Whole process took about half an hour and wasn't complicated. Just be sure you're s-off.
Click to expand...
Click to collapse
Thanks for the info. But I need to bug you again.:angel:
A few questions about the ruu method. After you ruu, does that remove root, lock bootloader, and goes back to s-on?
And since I love numbered steps, here is how I am viewing it with my inexperienced understanding with question marks:
1. Check for S-off
2. Lock bootloader? (I guess not with S-off)
3. Run ruu 2.20 exe
4. Flash 3.18 ota
5. Rerun superCID (X-Factor xploit)?
6. Unlock bootloader
7. Flash TWRP
8. Flash ROM (Assuming S-off wasn't changed during the ruu)
I would love to be at your confidence level to run it it 30 minutes. One day I guess....

Before you run a ruu, you have to relock. When you run it, it wipes your entire phone and returns it to stock-out-of-the-box (except for s-off). So you need to back up anything you want to keep.
Here's a corrected list:
1. S-off
2. Relock in fastboot
3. Run ruu
4. Copy OTA update.zip to internal storage
5. Flash in stock recovery
6. Unlock
7. Flash custom recovery
8. Flash rooted rom
None of this affects s-off. AFAIK, the only way to be s-on again is manually change it in fastboot.
I wouldn't do all this unless you have a reason to, as there are spots in here where you can get tripped up if you're a complete noob.

iElvis said:
Before you run a ruu, you have to relock. When you run it, it wipes your entire phone and returns it to stock-out-of-the-box (except for s-off). So you need to back up anything you want to keep.
Here's a corrected list:
1. S-off
2. Relock in fastboot
3. Run ruu
4. Copy OTA update.zip to internal storage
5. Flash in stock recovery
6. Unlock
7. Flash custom recovery
8. Flash rooted rom
None of this affects s-off. AFAIK, the only way to be s-on again is manually change it in fastboot.
I wouldn't do all this unless you have a reason to, as there are spots in here where you can get tripped up if you're a complete noob.
Click to expand...
Click to collapse
Thanks for the checklist! It makes me feel safer to know an exit strategy so I don't panic if/when stuff goes bad.
I noticed you didn't list a step to re-root through custom recovery after step 7. Is the previous root still in place?

razorc03 said:
...and I also came from the original Samsung Vibrant. With that phone, I also had the idea that I could only use a ROM based of the current android version. Hence the carry over of thought from that side.
Click to expand...
Click to collapse
This varies completely by device, and firmware versions. Never assume that something you learned on another Android device applies to a different device.

razorc03 said:
I noticed you didn't list a step to re-root through custom recovery after step 7. Is the previous root still in place?
Click to expand...
Click to collapse
No, it's that once you're unlocked, you can re-root just by flashing a rooted rom.

[Q] Htc One X Unique problem

So as a n00b, I posted in the wrong forum earlier, lol
Anyways , long story short, htc one x evita, unlocked bootloader, tampered, rooted, will not flash past htc splash screen, when I try to restore, it does nothing, when going into folders there is NOTHING there, so random, I did clear my caches as instructed, maybe I am n00bish and deleted the wrong things, I can read the phone in adb, will go into teamwin screen,
REgardless, If I can get this fixed, I will not be messing with it again, lol(as all noobs say)
IS there anything I can do at this point before I throw my hands in the air and throw my phone at a wall?

Far from unique. It's possible that you've accidentally wiped the sd at some point, or did you possibly do a factory reset from the bootloader? Why haven't you just copied a ROM to the device to flash?
Sent from my Evita

timmaaa said:
Far from unique. It's possible that you've accidentally wiped the sd at some point, or did you possibly do a factory reset from the bootloader? Why haven't you just copied a ROM to the device to flash?
Sent from my Evita
Click to expand...
Click to collapse
HI, I may have wiped the sd, let's say sure to this..lol..
I have tried to copy a rom, I had Viper somewhat load, then it flashes back to htc splash, then to twrp,
Any insite to one that may possibly work?(the others will not load at all, they all fail install)

I need a bit more background on the device, please post your bootloader details (the first five lines). What TWRP version are you using? What had you done to the device directly before encountering this problem?
When you say you had Viper somewhat load what do you mean? Did it boot into the ROM at all? Or did it only boot as far as the Viper boot animation? Or did it only make it as far as the HTC splash screen?
I can't really say what's going to work until we figure out exactly what's wrong. Make sure you answer all the above questions with as much relevant detail as possible and we'll see if we can sort it out.
Sent from my Evita

timmaaa said:
I need a bit more background on the device, please post your bootloader details (the first five lines). What TWRP version are you using? What had you done to the device directly before encountering this problem?
When you say you had Viper somewhat load what do you mean? Did it boot into the ROM at all? Or did it only boot as far as the Viper boot animation? Or did it only make it as far as the HTC splash screen?
I can't really say what's going to work until we figure out exactly what's wrong. Make sure you answer all the above questions with as much relevant detail as possible and we'll see if we can sort it out.
Sent from my Evita
Click to expand...
Click to collapse
First off, thank you for your prompt replies
Venom loaded splash screen, then reboot to htc splash with the red developer on the bottom
twrp is the newest one
first 5 lines are you meaning?
*** TAMPERED ****
*** UNLOCKED ****
Evita put ship s-on rl
hboot-2.14.0000
radio-0.23a.32.09.29
??
Well I tried to load the stock RUU from rogers, (ota one)
then after rooting,unlocking bootloader, I tried to load a custom rom(slimkat IIRC)
then IT shut down, I left it for the night, and then nothing, so I tried to install slimkat again, nothing, so I tried venom, and I had the splash screen for the rom, now I am basically back at square one, nothing lol

Yes those are the bootloader details I needed. When you say the latest TWRP I'm assuming you mean 2.6.3.0? There are two versions of 2.6.3.0, the official version and the modified version.
Official version
Can flash any ROM except 4.4 ROMs. If you're using this one it is why SlimKat (plus any other 4.4 ROM) is failing to install.
Modified version
This is required to flash 4.4 ROMs. It does work on some pre 4.4 ROMs but it doesn't on others.
The most common cause for your current situation to happen is that you've forgotten to flash the boot.img with fastboot. Your phone is s-on, this means that the boot.img is unable to be flashed during the recovery install due to security restrictions on hboots equal to or greater than 1.14. So, make sure you're using the correct recovery for the ROM you want to flash (official 2.6.3.0 for Viper, modified 2.6.3.0 for 4.4 ROMs), and make sure you flash the boot.img with fastboot. I have detailed instructions on how to flash a boot.img in my How-To Guide For Beginners thread, link in my signature.
Do that and report back with how you go.
Sent from my Evita

timmaaa said:
Yes those are the bootloader details I needed. When you say the latest TWRP I'm assuming you mean 2.6.3.0? There are two versions of 2.6.3.0, the official version and the modified version.
Official version
Can flash any ROM except 4.4 ROMs. If you're using this one it is why SlimKat (plus any other 4.4 ROM) is failing to install.
Modified version
This is required to flash 4.4 ROMs. It does work on some pre 4.4 ROMs but it doesn't on others.
The most common cause for your current situation to happen is that you've forgotten to flash the boot.img with fastboot. Your phone is s-on, this means that the boot.img is unable to be flashed during the recovery install due to security restrictions on hboots equal to or greater than 1.14. So, make sure you're using the correct recovery for the ROM you want to flash (official 2.6.3.0 for Viper, modified 2.6.3.0 for 4.4 ROMs), and make sure you flash the boot.img with fastboot. I have detailed instructions on how to flash a boot.img in my How-To Guide For Beginners thread, link in my signature.
Do that and report back with how you go.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so very much, once again with the quick replies and the "dumming" it down for me,
I will try in a little bit, to be honest, im not sure what twrp it is, I know its 2.3.6.0, it was the newest one,
in your instructions is there a way to boot just back to stock rom as well?(my pc is horrible, if I load more then one page it dies off lol) I will try this when I get home in a little bit herre.

I can almost positively say you're on the official version of TWRP, you'd need to go out of your way to find the modified one usually. With your phone in its current state you can't use an RUU to go back to stock. The latest Rogers RUU is older than your current firmware and you can't run an older RUU while s-on. If you made a TWRP backup of your stock ROM before wiping you could restore that backup though.
Your best and easiest option right now is to just flash a ROM. Once you've gotten a custom ROM booted up my guess is you won't want to go back to stock
Once you've gotten a ROM booted you can get s-off on your device which will make life a lot easier for you. It means no more flashing a boot.img, you'll be able to flash radios, you can run any Evita RUU (forwards or backwards, and from any carrier), and more benefits. But for now just concentrate on getting the ROM booting.
I'm assuming you have adb/fastboot installed on your PC already? If not you'll need to do that first, Google search "minimal adb and fastboot", the first result should take you to a thread that can get it done with very little effort.
Sent from my Evita

timmaaa said:
I can almost positively say you're on the official version of TWRP, you'd need to go out of your way to find the modified one usually. With your phone in its current state you can't use an RUU to go back to stock. The latest Rogers RUU is older than your current firmware and you can't run an older RUU while s-on. If you made a TWRP backup of your stock ROM before wiping you could restore that backup though.
Your best and easiest option right now is to just flash a ROM. Once you've gotten a custom ROM booted up my guess is you won't want to go back to stock
Once you've gotten a ROM booted you can get s-off on your device which will make life a lot easier for you. It means no more flashing a boot.img, you'll be able to flash radios, you can run any Evita RUU (forwards or backwards, and from any carrier), and more benefits. But for now just concentrate on getting the ROM booting.
I'm assuming you have adb/fastboot installed on your PC already? If not you'll need to do that first, Google search "minimal adb and fastboot", the first result should take you to a thread that can get it done with very little effort.
Sent from my Evita
Click to expand...
Click to collapse
Yes I have a basic Adb/fastboot setup already, is there a particular rom you recommend?(I will trust your best judgement here) I am home now, I will try and let you know
Thank you again

Asking for a ROM recommendation isn't allowed on XDA so I can't answer that question, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge.
Each user has different tastes anyway. Some people like Sense ROMs, some like aosp ROMs. Personally I'm an aosp guy, aosp ROMs are generally a bit snappier, plus you can run the latest version of Android (Sense ROMs are limited to 4.2.2 for our device). I'd suggest having a look at the ROMs on offer, check out their features and pick one to flash. If you don't end up liking it you can always just flash another, and that's half the fun.
As a side note, getting s-off via Rumrunner s-off seems to work better on Sense ROMs. I know someone very recently got s-off while on the Kickdroid ROM so if you do want to get s-off I'd suggest flashing that ROM purely for the s-off process. You might like it and want to stay on it, if not just flash away.
Sent from my Evita

timmaaa said:
Asking for a ROM recommendation isn't allowed on XDA so I can't answer that question, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge.
Each user has different tastes anyway. Some people like Sense ROMs, some like aosp ROMs. Personally I'm an aosp guy, aosp ROMs are generally a bit snappier, plus you can run the latest version of Android (Sense ROMs are limited to 4.2.2 for our device). I'd suggest having a look at the ROMs on offer, check out their features and pick one to flash. If you don't end up liking it you can always just flash another, and that's half the fun.
As a side note, getting s-off via Rumrunner s-off seems to work better on Sense ROMs. I know someone very recently got s-off while on the Kickdroid ROM so if you do want to get s-off I'd suggest flashing that ROM purely for the s-off process. You might like it and want to stay on it, if not just flash away.
Sent from my Evita
Click to expand...
Click to collapse
I understand and apologize, Never thought of it that way,
Anyways an update, I followed your tutorial, and I am not having much luck here, It still maintains to say NO OS installed (through twrp when rebooting after I do adb and such)
maybe I am missing something ?

Adb or fastboot?
Sent from my Evita

timmaaa said:
Adb or fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Fastboot,
Small update I did manage to get a rootbox rom to load, but its not stable by anymeans...Ugh super frustrated with it

Are you wiping in TWRP before flashing? It's very important to wipe system/factory reset/cache/dalvik cache before installing a ROM. Just never do a factory reset in the bootloader, that'll corrupt your sd card.
Sent from my Evita

timmaaa said:
Are you wiping in TWRP before flashing? It's very important to wipe system/factory reset/cache/dalvik cache before installing a ROM. Just never do a factory reset in the bootloader, that'll corrupt your sd card.
Sent from my Evita
Click to expand...
Click to collapse
Yes to wiping before flashing in TWRP just those ones mentioned, (if you do sd you loose your flash right?), anyways the rom I flashed yesterday was super unstable, just trying a few diff. ones out and trying to find one that will continue to stay working lol!! Your tutorial in your signature is very helpful
thank you so much for all your help,and patience

Yeah you don't want to wipe sd card/internal storage or you'll lose all of your personal data like images, music, ROM zips, backups.
Sent from my Evita

timmaaa said:
Yeah you don't want to wipe sd card/internal storage or you'll lose all of your personal data like images, music, ROM zips, backups.
Sent from my Evita
Click to expand...
Click to collapse
Oh this is a clean phone, I already backed up on pc Before lol
Question though, I installed Viper again(just to try it) and it loads a menu showing ram, one of the memory sections shows -1? is this correct?

On a side note, I got Venom up and running and WOW!!!
once again, a super thank you for your patience and help all along Timmaaa,

I'm not sure what you're talking about, is that after booting into the ROM? Can you show me a screenshot?
Sent from my Evita

timmaaa said:
I'm not sure what you're talking about, is that after booting into the ROM? Can you show me a screenshot?
Sent from my Evita
Click to expand...
Click to collapse
it was while I was installing, everything seems fine, still no wifi(original issue)
im thinking the logic board may be buggered...sad day...lol
But, it is fast as heck now, running venom rom, I will try to get S-off and then maybe try to get it so I can load up the 4.4X roms
Thanks for all the help

[Q] Stock Recovery

Hi all,
I apologize if this has been answered before, but I had trouble finding it here. I am currently rooted on a stock backup, but I am running a custom recovery. I am not sure where to find the stock recovery image for my device. I am using the HTC One M8 through Verizon, and I know that the new firmware update is coming out soon, and I'd like to be able to just OTA update my phone so that I can reflash a custom recovery and install the newest VenomROM. I have flashed a custom recovery before (obviously), but I didn't know if it mattered which firmware base you are running. I read somewhere that the recovery is totally separate from the OS, and it is meant to be an alternative to booting into the OS in case of a problem, but I want to be sure. If there is a specific recovery I need to use and someone here knows where I can find it, that'd be great. I found the collection of stock recoveries, but I'm having trouble figuring out which one I need to use. Any and all help is appreciated, thanks.
EDIT: My CID is VZW__001
My VERSION-MAIN is nothing. There's is just nothing next to this label.
I tried locating it on the collection of stock recoveries, but couldn't find it. I'm not sure why this is.

It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....

hgoldner said:
It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Hi there,
I actually just used the psuedo RUU tool (I assume this is the one you are talking about? http://forum.xda-developers.com/showthread.php?t=2727831)
I just finished using this tool, but when I went to check the recovery, all I get is a big red triangle with an exclamation point in the middle. Nothing else. So, I'm guessing that recovery didn't flash properly? But I'm honestly not completely sure. I would screenshot it, but I can't do that. Any help is appreciated.
EDIT: I found out that pressing volume up and power gives more options. I assume I am all good to go now? I am still rooted, and I'm not sure if that is a problem. I am stock, s-off and rooted, but I don't have any mods installed.

You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....

hgoldner said:
You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.

ChuckFinley1992 said:
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.
Click to expand...
Click to collapse
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.

hgoldner said:
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?

ChuckFinley1992 said:
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?
Click to expand...
Click to collapse
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.

hgoldner said:
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.
Click to expand...
Click to collapse
Okay, I may look into that. I've only seen an RUU flashed via hboot, so I'd have to look into it. At the very least though, I'd imagine someone will post the instructions on how to flash the firmware when it comes out.
Thanks so much for your help!

hgoldner said:
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
+100 for this!
I am reading dozens of posts in all kinds of threads of people just dying to take that OTA...
Why???
I would not touch that new firmware with a 100 foot pole until the devs have figured out what it breaks!!!
I predict a flood of posts in the line of:
"I flashed back to stock to take the OTA and now weaksauce is not working - how do I get root back?"
What's the hurry?????