Database Info

How To UN ROOT. TUTORIAL. Your Problems are solved!

UPDATE: With all of the newer rooting and S-Off methods, and new hardware and firmware revisions, this thread may or may not help with your specific case if trying to unroot and go back to unrooted stock. I originally wrote this based of of the very first root methods known for the Launch EVO. There is a good chance that this method will still work, but there could definitely be something unaccounted for in your own specific case, so tread with caution. It is very doubtful that anything in this tutorial will result in your EVO becoming a fancy-schmancy paperweight, but if something goes afoul, you could have a nice headache to deal with...
Ok guys. There is a lot of partial and mis-information floating around out there about how to UN ROOT if you have to send your phone back for replacement, or you want the official unrooted OTA 2.2.
OLD NEWS!!!---> NEWER METHODS AVAILABLE TO ACTUALLY FIX PRI DOWNGRADE> SEARCH!!!! EDIT your PRI to show 1.40, thanks to sturmen for the pointer, and Calkulin for the method: http://forum.xda-developers.com/showpost.php?p=7267559&postcount=66
This assumes you are full root, S-Off. Note, this is not tested with simple root but should work (EDIT, Simple Root is basically Toastcfh's method, so you simple root users should be set), only with Toastchf's root method and nand unlock.
After reading every thread on the forum here, I think I finally found a fool proof way to do it. All the info was out there, but in several places and each one was missing something.
1) Before you start clicking and flashing and running RUUs, Check your HBoot build. You need to have the 0.76.2000 from Toastcfh's method #2. If you have 0.79.0000 (whatever) go to step 2 below. If you're getting Bootloader errors when running an RUU, I can almost guarantee that you don't have the correct HBOOT. If you somehow still have 0.76.2000 from previous modding, proceed to step 3.
2) Toast's Nand Unlock method. Found here: http://forum.xda-developers.com/showthread.php?t=701835
EDIT: The more I think about it, I think you can just run Simple Root to re-attain the .76 HBOOT and engineering build. It would eliminate the need for any adb, and SHOULD produce the same results. Just run the RUU after you run and complete simple root. See notes in BLUE below too!
THIS STEP IS 100% NECESSARY IF YOU HAVE THE .79 HBOOT version!!!...Do step #2 in Toast's thread, just like you did when you originally unlocked NAND (OR YOU SHOULD BE ABLE TO JUST RUN SIMPLE ROOT AGAIN...UNconfirmed, but should work methinks...). Not 100% sure which steps are necessary, but I do know you need to do steps #1 (Well, #1 is Nandroid Backup, so proceed at own risk if you skip) and #2 again. Make sure after you flash the Flash_Image, and the mtd-eng through adb, that you then load the PC36IMG.zip (Engineering Build), onto the root of your SD card, and boot into HBOOT, and let it install (just like you did when rooting). I didn't bother to flash the Recovery image at the end of step 3, but I don't think it would hurt if you're nervous about losing a custom recovery image in case this method for some reason does not work. It has come to my attention that flashing the engineering build (the PC36IMG from Toast's thread)through fastboot, might be as crucial as simply having the .76 HBOOT version. It at least is a surefire way to make sure you can run an RUU on top of it. There are probably other builds/roms that will work and allow you to run the RUU, but this one is confirmed, so don't skip that step!
3) If you have the 0.76.2000 HBOOT (can be checked by powering down, and booting by holding VOL down and Power), then you can go ahead and boot into the rom, and proceed with downloading the RUUs found here: http://shipped-roms.com/shipped/Supersonic/
Go ahead and download the first one (at least). I think the others are optional to "upgrade" but why should we care. We just want to go back to unrooted stock.
4) Make sure you have the latest version of HTC Sync installed, found here: http://www.htc.com/uk/SupportViewNews.aspx?dl_id=933&news_id=627
Install, and let it do it's thing. Will probably have to restart your PC when complete. Not even 100% sure this is necessary, but it won't hurt. It's basically for the HTC drivers from what I understand.
5) Run the RUU from your pc while your evo is in the phone loaded state of the Rom, (not the bootloader) with the phone connected through USB and have HTC sync selected. Even if it doesn't connect to HTC sync on your PC, you should be ok.
If you get a USB error after the screen goes black with the HTC LOGO, don't touch the phone. Exit the RUU via the EXIT button when given the option.
6) Run the RUU again and see what happens. The Error could happen 1 more time, but just exit again, and run RUU one last time.
7) Thank everyone here at XDA that our EVOs are so badass...I'm certinly not a dev, but these devs work hard for us to have the baddest ass phone there is right now.
Any problems, let me know. I assume your errors are the same ones I was getting, and it's all because of the wrong HBOOT.
I really take no credit for this, as I'm just compiling information in a tut....

Thanks op.

Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.

arozer said:
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
Click to expand...
Click to collapse
You might be correct, but I couldn't get the FROYO OTA to show up in any of the roms I was using.

Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?

sturmen said:
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
Click to expand...
Click to collapse
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
EDIT: Yess! See below and in OP!

Bang3r said:
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
Click to expand...
Click to collapse
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...

sturmen said:
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
Click to expand...
Click to collapse
That would be cool, but I'm not too worried about that part. Phone is going back tomorrow!

Well, worry even less! Special thanks to Calkulin!

thankssssss

Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop

I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...

I'm getting error 155 running Ava Froyo and trying to go back.

blix1337 said:
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
Click to expand...
Click to collapse
Yes, you are correct, but so am I. This is exactly what step 2 in the OP does (which is a link to Toastcfh's thread about the engineering build).

tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
Ok. RE-read the OP. Everything is there. Check your HBOOT version by booting to the bootloader. If you have .79, you need to re-flash the engineering build before the RUU will work (Step 2 in the OP to get HBOOT to .76). You cannot run the RUU on top of AVA froyo or any froyo, or any rooted custom 2.1 for that matter if you don't have the proper HBOOT (Which I believe you cannot have if you are running any custom rom). Flash to the engineering build, then the RUU.

How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?

joypunk said:
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
Click to expand...
Click to collapse
Yes you can still REroot VIA those methods. As long as you don't do a FROYO OTA or manually flash the UNROOTED Froyo...there is no ROOT method for FROYO yet.
It returns completely to UNROOTED stock, except for the PRI, which there is a fix for on the 1st page.
And incidentally (and I just figured this out last night) Simple Root is Toast's method, just automated...
EDIT: I think that you could even UNROOT and RUU to 1.3x (whatever it is), then use the ROOTING methods that were in place before the official 1.47 OTA rooting methods. But, I just did simpleroot last night on top of 1.47, and it is freaking SIMPLE....1 click for root...1 click to flash recovery.

tpdtopcop said:
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
Click to expand...
Click to collapse
This is what were trying to show you on Androidcentral as well. Glad you are set!

tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
As long as you have .76 HBOOT flash back to an earlier rom...one that has a 1.32 base. Then use the 1.32 RUU or 1.47 RUU. You should be set. Make sure you have completed step 2 in OP.

Yes. I have .79, thanks!
Sent from my PC36100 using XDA App

[Q] Trouble Rooting EVO 4G S-OFF

*ATTENTION MODS* I am reposting.... sort of... the original thread is here
http://forum.xda-developers.com/showthread.php?p=9074948#post9074948
Hello! I am not new to rooting...I did get a new EVO 4G at best buy yesterday...
Went home and tried to root following another method than unrEVOked 3.21 and long story short had to RUU with "RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15 .00.07.28_NV_1.40_release_140444_signed"
I then tried unrEVOked 3.21 which SEEMED to work... I followed all onscreen prompts...
Plugged in my phone, ran the program, phone rebooted, selected HBOOT USB, Program reported that everything was going along nicely...even saw the program say waiting for root..."this was a triumph" Rebooted..then came back up to desktop...didnt reboot in recover like i have seen... the program then reverts to saying the thing about HBOOT USB.... there is NO SuperUser app and it is NOT rooted...
Please tell me where I went wrong...and what I need to do to fix it...
Info about MY Phone
Android Version 2.2
Baseband Version 2.15.00.07.28
Kernel 2.6.32.15-g746f4f0
Software Version 3.26.651.1
PLEASE help....I am having withdrawals lol...
***UPDATE***
Following this Guide
http://forum.xda-developers.com/showthread.php?t=829045
I made it to Step 19...then S#*+ went crazy...It appears that the recover did NOT flash...not really sure...I am now trying to RUU my phone back...and start over but it keeps saying the phone is low battery <30% and its NOT...I looked at 3 batterys on a Hero and it says all are over 70%...
and ..since im pretty sure this matters...with S-OFF
When I try to flash PC36IMG.zip Radio_V2 FAIL-PU and...Bootloader FAIL-IC is what I get...
ALL help greatly appreciated...thankfully I am off work the next two days...So I know I can get this resolved

Ok I have done a lot of reading that seems to indicate that I have no ROM or my ROM is Broken...and seeing as how RUU keeps saying my battery level is too low I am going to put it on the charger til the light turns green...Try to RUU in the Morning...
***SOMEONE PLEASE CORRECT ME IF I AM WRONG ***
I am under the impression that RUU'ing will NOT Turn S-ON and will Leave S-OFF
But will just load a ROM and allow me to boot in and then run unrEVOked and be on my merry rooted way...
If ANYONE knows that it will turn S-ON please stop me lol...I am going to stop trying for now and get some sleep... will check this post before continuing..

Inspire 4G Reverting on boot

I have a really strange issue and I've done everything I can think of to fix it to no avail. I'm hoping someone here can give me a few pointers.
I'm working on a Inspire 4G for someone. The issue is that the phone reverts to a specific state no matter what I do. For example, if I wipe the phone, the phone boots back up to Froyo with all of his stuff on it. If I try loading an RUU or IMG file (Froyo or Gingerbread), it will "take" but boot to Froyo with all of his stuff on it. It's almost like it wipes itself and loads this image out of nowhere...
Another weird thing, which may or may not be related, is that I see a weird download in his notification tray. Apparently, the file named "WinBej2Setup.exe" was downloaded twice. I did some research on that and everything I see points to some kind of malware for a Windows PC.
Any and all help is appreciated.

Forgive me if this sounds stupid, but you do have S-off correct? I'm not sure about the weird file, have you tried to access it? Also what other roms have you tried to flash? Also what method did you use to root?
Sent from my Inspire 4G using xda premium

I don't have S-OFF. Here's all the bootloader info:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0019
MICROP-0438
RADIO-26.06.04.06_m
Emmc-boot
Dec 27 2010, 14:47:30
As for the file, I'm not sure where it's located. I can only see the notifications that they have finished downloading.
As for the history on the phone, I really can't say much since it's not my personal phone. The person I'm doing this for said he tried to root it using the ACE Hack kit and "some ADB commands" and failed. That's all the information I was given.
At this point, I can load anything to the phone but it will just revert to Froyo in the exact state that it's currently in.
For example, I just tried installing Gingerbread via the official RUU file. It goes through the entire process without a hiccup. Then it reboots and takes forever to load; but when it does, it's back on Froyo with all the owners files...

Personally I would root it, make sure s off, and make sure to format the memory card the corrrect way also.
Then I would install a custom rom.
And the file you speak of is also a game called bejewled. My girl loves that game.
Sent to you by ......
This p-o-s I'm addicted to, and my woman is jealous of.

Reformat the sd card then do an official upgrade thru HTC. Go to the website and download the Gingerbread RUU and HTC Sync. If this doesn't work, complete the root process as suggested.Tell your friend you can't install exe files on Android. They need to be apk files or zip files if installed thru recovery.
Sent from my Inspire 4G using Tapatalk

I appreciate the advice guys, but I think you guys are overlooking what I'm trying to say... I've already tried running the official upgrades from HTC. The RUU says it's completed fine, but on reboot, I'm back on Froyo with all the same stuff on it.
I've even gone as far as extracting the IMG file out of the RUU and loading it through the bootloader. If I do this, it does the same thing-- says everything loaded fine but reverts on boot back to Froyo in the same state it was in prior.
I can temp root the phone using psneuter but that's about it. I have no idea how I'm going to achieve S-OFF if everything I do is wiped on reboot...
What I'm wondering is if there is a way to lock the entire phone down in a state where nothing can be changed; and if so, is there a way to disable this feature.

Are you sure you do not have a file on the root of the card named PD98IMG.zip? You may be installing this every time the phone boots.
How can you install a non RUU ROM when you have s-on?
Something does not make sense here. Also the exe file you talked about has no use on android as android can do nothing with it. Where do you actually see it?
Go back to square 1. What ROM is on the phone now? Do you have clockwork installed?

I'm not sure how to many different times/ways I can explain the same thing. The phone is on stock AT&T Froyo 2.2.1 (1.80.502.3). Currently, there is no custom recovery and it's not rooted.
The issue is that the phone always reverts (almost like it's doing a nandroid restore in the background) during boot to Froyo 2.2.1 (1.80.502.3) with all his stuff on it.
I've installed Gingerbread 2.3.3 (2.47.502.7) via the official AT&T RUU file
I've extracted the PD98IMG.zip from the Gingerbread 2.3.3 (2.47.502.7) RUU and loaded it via bootloader
I've installed Froyo 2.2.1 (1.80.502.3) via the official AT&T RUU file.
I've extracted the PD98IMG.zip from the Froyo 2.2.1 (1.80.502.3) RUU and loaded it via bootloader
I've done a factory reset from within the phone
I've deleted user data & cache with the stock recovery
After performing each and everyone of these steps, the phone hangs on the white HTC screen while booting and eventually boots up to Froyo 2.2.1 (1.80.502.3) along with all the guys stuff on it.
How can you install a non RUU ROM when you have s-on?
Click to expand...
Click to collapse
I don't believe I've ever said that the phone has a non-RUU ROM...
Also the exe file you talked about has no use on android as android can do nothing with it
Click to expand...
Click to collapse
I agree completely; however, the issue I'm running into very unusual. With that being said, I'm trying to point out anything unusual that I notice with the phone. This file most likely has absolutely nothing to do with the problem I'm encountering, but I mentioned it just in case.
Are you sure you do not have a file on the root of the card named PD98IMG.zip? You may be installing this every time the phone boots.
Click to expand...
Click to collapse
I wish this was the case; however, this wouldn't explain why all his stuff is still on the phone... The only time there is a PD98IMG.zip on the sdcard is when I put it there. Even so, I would have to boot the phone into bootloader mode and go through the prompts to get it take. More so, even if I did do this, it would just revert upon rebooting (hints the problem).
I appreciate the help but I think the problem is a little deeper than what has be presented.

That clears it up for me. You obviously know what you are doing. You mentioned "wipe" a few times which confused me. Didn't think there was a way to actually wipe it without a recovery installed. Sounds like one helluva confusing issue there. Goodluck.

Its always going to revert back to the previous state because its still s-on.
You need to get s-off before anything will change.
Sent from my Inspire 4G using xda premium

Its always going to revert back to the previous state because its still s-on.
You need to get s-off before anything will change.
Click to expand...
Click to collapse
This I know is not true-- You can load signed code with S-ON. If what you said was true there would be no way to load an official RUU or OTA...
I appreciate the help, but telling me to get S-OFF (which I've clearly stated that I'm unable to do) is not getting me anywhere.

Is the original ROM branded? Have you tried installing a PD98IMG.zip from a gold card? Just a thought.

Can't undo S-OFF

Hello all,
Was just wondering if anyone can help me as I am trying to unroot the phone to send back for warranty reasons as main speaker is not working anymore.
First restored the original partition 7 from gfree and ran its unroot
it put back the 0.86.0000 hboot but still showing S-OFF though.
tried to flash the PD15IMG.zip for gingerbread and let it do all the updates and is still on s-off but showing 0.86.0005 now.
When booting it gives the normal first vibration then about a second or two later I get another vibration.
Has all the right software just seems like something is different and not running 100% stock yet.
Any ideas what I am missing?
Any help would be greatly appreciated.

M9x3mos said:
Hello all,
Was just wondering if anyone can help me as I am trying to unroot the phone to send back for warranty reasons as main speaker is not working anymore.
First restored the original partition 7 from gfree and ran its unroot
it put back the 0.86.0000 hboot but still showing S-OFF though.
tried to flash the PD15IMG.zip for gingerbread and let it do all the updates and is still on s-off but showing 0.86.0005 now.
When booting it gives the normal first vibration then about a second or two later I get another vibration.
Has all the right software just seems like something is different and not running 100% stock yet.
Any ideas what I am missing?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Ive heard it can take a couple of tries of rooting and unrooting for it to show s-on. try rerooting it with the same method you used to root and then just get the stock pd15img to flash. Make sure you downgrade the bootloader first though if its now the gingerbread bootloader. Good Luck!

you mean the 0.86.0000 hboot?

M9x3mos said:
you mean the 0.86.0000 hboot?
Click to expand...
Click to collapse
0.86.000 is the stock hboot, you should be good to go.

yeah that is what I had didn't help
I assume should be engineering hboot
do gfree procedures
then put 0.86.0000

Sunshine s-off, but can't get Superuser SU Binaries installed.....

I just got S-Off with Sun Shine, but can't seem to get SuperuserSU working (I was going to install TWRP from TWRP Manager after getting SuperuserSU.) Anyone know what I need to do? I looked for a thread that explained the process, but have not found anything. Many thanks!

Flash twrp from fastboot. Flash SuperSU from twrp.
Sent from my XT1254 using Tapatalk

I am trying to flash TWRP with Minimal ADB and Fastboot from here..... http://androidmtk.com/download-minimal-adb-and-fastboot-tool
I keep getting this for messages when I type the command flash twrp.img "cannot load 'twrp.img'
I know that the device is connected since it goes into fastboot when I type "adb reboot bootloader".
Any ideas?

Solved......I am a complete fool. I renamed the recovery image "twrp.img" so the actual file was "twrp.img.img". How embarrassing.....LOL! Time to just go and hit the bar and have a beer! I must have cabin fever after this winter and my mind is not functioning properly. ARGH!

therreid said:
Solved......I am a complete fool. I renamed the recovery image "twrp.img" so the actual file was "twrp.img.img". How embarrassing.....LOL! Time to just go and hit the bar and have a beer! I must have cabin fever after this winter and my mind is not functioning properly. ARGH!
Click to expand...
Click to collapse
It happens a lot[emoji14]
Sent from my XT1254 using Tapatalk

I posted this in the general questions thread, but I wanted to post here as well...
beaups said:
It happens a lot[emoji14]
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I apologize in advance as I'm sure this has been asked toomany times to count, but I have searched and searched thread after thread to see if I can find a solution for about 23 hrs straight, I'm pretty much out of time & panicking now that I messed up beyond fixing. Any advice, help, or a point in the right direction to the right post would be very much appreciated!!!
So, the problem is, I'm not 100% sure but I think I have "soft bricked" my phone... I gained s-off through Sunshine about a week ago, I have been reading & researching how to root my phone for updating to a custom ROM running 6.0 MM for months now trying to prevent any issues & be as well educated as possible...
Last night I finally gained root access using Kingroot, then switching over superSU BUT of course, I had the problem with the binaries. I installed TWRP app to perform the recovery flash to ext SD because I do have a PC, but it's a work computer so I don't have administrator rights to install any programs/apps on the PC such as ADB, Flashify, etc.
Before I decided to restart my phone I had SuperSU running the # sign in the notifications center (re: the binaries), I also had the TWRP manager I chose my device model, but I did not install any files (at least I don't think I did). I was most concerned on my current backup & flashing that to my extSD. Which is what I thought I had done, or maybe I didn't do anything at all? BTW- I have removed the SD card & inserted into my PC to see what files were on it, and nothing!! Nothing at all to do with SuperSU nor TWRP (I have since installed the latest update SuperSU zip file on that card). All I know is I cannot get my phone on past the Verizon screen, I can perform a hard boot & get back into hboot /fastboot, I have all options on the menu, and have tried every one of them minus the 'factory data reset', 'apply from phone storage' or 'ramdump'. I would have typed in the information that the screen says in HBOOT but my phone literally just died from the screen being on so long :-/ I will add that info if needed once I can boot it back up without use of the charging cable.
Any help on what to do would be so greatly appreciated as apparently I'm freaking out & I'm thinking I'm way in over my head not knowing what exactly happened to cause this!!! Please Help:crying:

M-FayeHTC said:
I apologize in advance as I'm sure this has been asked toomany times to count, but I have searched and searched thread after thread to see if I can find a solution for about 23 hrs straight, I'm pretty much out of time & panicking now that I messed up beyond fixing. Any advice, help, or a point in the right direction to the right post would be very much appreciated!!!
So, the problem is, I'm not 100% sure but I think I have "soft bricked" my phone... I gained s-off through Sunshine about a week ago, I have been reading & researching how to root my phone for updating to a custom ROM running 6.0 MM for months now trying to prevent any issues & be as well educated as possible...
Last night I finally gained root access using Kingroot, then switching over superSU BUT of course, I had the problem with the binaries. I installed TWRP app to perform the recovery flash to ext SD because I do have a PC, but it's a work computer so I don't have administrator rights to install any programs/apps on the PC such as ADB, Flashify, etc.
Before I decided to restart my phone I had SuperSU running the # sign in the notifications center (re: the binaries), I also had the TWRP manager I chose my device model, but I did not install any files (at least I don't think I did). I was most concerned on my current backup & flashing that to my extSD. Which is what I thought I had done, or maybe I didn't do anything at all? BTW- I have removed the SD card & inserted into my PC to see what files were on it, and nothing!! Nothing at all to do with SuperSU nor TWRP (I have since installed the latest update SuperSU zip file on that card). All I know is I cannot get my phone on past the Verizon screen, I can perform a hard boot & get back into hboot /fastboot, I have all options on the menu, and have tried every one of them minus the 'factory data reset', 'apply from phone storage' or 'ramdump'. I would have typed in the information that the screen says in HBOOT but my phone literally just died from the screen being on so long :-/ I will add that info if needed once I can boot it back up without use of the charging cable.
Any help on what to do would be so greatly appreciated as apparently I'm freaking out & I'm thinking I'm way in over my head not knowing what exactly happened to cause this!!! Please Help:crying:
Click to expand...
Click to collapse
You are fine. Start fixing it by flashing the latest s-on ruu I have posted. This will NOT affect your s-off or unlocked boot loader status. Then when done flash twrp via fastboot. (Never use that stinking app). Then flash supersu zip in twrp to root your stock rom. If you have fast internet I can always you using team viewer (free app)

I'm still having trouble...
dottat said:
You are fine. Start fixing it by flashing the latest s-on ruu I have posted. This will NOT affect your s-off or unlocked boot loader status. Then when done flash twrp via fastboot. (Never use that stinking app). Then flash supersu zip in twrp to root your stock rom. If you have fast internet I can always you using team viewer (free app)
Click to expand...
Click to collapse
First,I appreciate you getting back tome so soon. I downloaded the latest RUU onto my SD card, then reloaded it into my phone in bootloader, nothing happened
Right now, I still cannot get past the red Verizon screen, my phone won't turn on fully... The options I have are my "Administrator PW protected work PC" that I cannot run fastboot on, or my Nextbook tablet. Would Team View work on either of these since my phone is out of the question?
Rightnow this is what my HBOOT screen is saying....
**UNLOCKED**
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT- 3.19.0.0000
RADIO- 1.12.20.1211
OpenDSP- v47.2.2-00564-M8975-FO.1024
OS-4.17.605.9
eMMC-boot 2048MB
Aug 11 2015, 22:31:04.0
Thanks in Advance!!!

M-FayeHTC said:
First,I appreciate you getting back tome so soon. I downloaded the latest RUU onto my SD card, then reloaded it into my phone in bootloader, nothing happened
Right now, I still cannot get past the red Verizon screen, my phone won't turn on fully... The options I have are my "Administrator PW protected work PC" that I cannot run fastboot on, or my Nextbook tablet. Would Team View work on either of these since my phone is out of the question?
Rightnow this is what my HBOOT screen is saying....
**UNLOCKED**
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT- 3.19.0.0000
RADIO- 1.12.20.1211
OpenDSP- v47.2.2-00564-M8975-FO.1024
OS-4.17.605.9
eMMC-boot 2048MB
Aug 11 2015, 22:31:04.0
Thanks in Advance!!!
Click to expand...
Click to collapse
If nothing ran you have the file either named wrong or have an extra .zip on the end of the name. Make sure you view file extensions to be sure. It's case sensitive and 0P6BIMG.zip
Leading character is a zero.

First part COMPLETE!
dottat said:
If nothing ran you have the file either named wrong or have an extra .zip on the end of the name. Make sure you view file extensions to be sure. It's case sensitive and 0P6BIMG.zip
Leading character is a zero.
Click to expand...
Click to collapse
Okay, I have hope. Thank You SO MUCH!!! Phone is on (upgrading currently), but IT'S ON:highfive: I think I accidentally used the s-off file instead of the s-on, and I did add the .zip onto that file (since it wasn't showing it w/ it, DUHHH). I will follow the rest of your instruction's very carefully later on, this will take a while, on app 80 out of 279 (bloatware, ugh!!) Hopefully, it goes more smoothly & I won't have to bother you again :fingers-crossed:
Thanks Again!
P.S. Will be contributing ASAP once I get this mess cleaned up. I really do appreciate all of your hard work & the magic that you make happen!!

M-FayeHTC said:
Okay, I have hope. Thank You SO MUCH!!! Phone is on (upgrading currently), but IT'S ON:highfive: I think I accidentally used the s-off file instead of the s-on, and I did add the .zip onto that file (since it wasn't showing it w/ it, DUHHH). I will follow the rest of your instruction's very carefully later on, this will take a while, on app 80 out of 279 (bloatware, ugh!!) Hopefully, it goes more smoothly & I won't have to bother you again :fingers-crossed:
Thanks Again!
P.S. Will be contributing ASAP once I get this mess cleaned up. I really do appreciate all of your hard work & the magic that you make happen!!
Click to expand...
Click to collapse
Well if you used the s-off one that's fine too. You will be rooted already. Just need to flash the latest twrp image and you will be fine.