yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] jlechner:
When you try it again, after entering adb reboot bootloader, type adb devices and make sure it shows your device.

Sent from my Sprint/Virgin Mobile hybrid
[HTC EVO 3D] grandpasghost:
After the adb reboot bootloader command, I typed "adb devices" and got a "List of devices attached" and thats it. I ran adb devices earlier in the process and it showed me the device.

UPDATE: Tried erase command anyways and it worked this time. continuing with the process will update again.

Things i did different this time: use the full Android-SDK package instead of the tiny ADB one in the thread. Also used the mirrored"Eng Hboot 1.04.2000" from the thread thats linked to in the OP. Last time i downloaded the second link in that thread instead for "PG86IMG_1.40-hboot " not sure if theres a difference, but just in case it helps.
[HTC EVO 3D] grandpasghost:
Still on 2.08 and PRI 1.53 Firmware update says.. "No firmware update found"

Also appear to be on HBOOT 1.5 now if that matters.
[HTC EVO 3D] jcfunk:
Do HTC software update.

Sent from my DOWNGRADED EVO 3D
[HTC EVO 3D] grandpasghost:
Thanks Muchacho! Logic failed me there for a minute.

Downloaded software update, after install and reboot it shows me on Build: 2.08.651 and my PRI is 1.53_144 Musta screwed up somethin, somewhere.

UPDATE: Checked for HTC Software update again, and its now downloading an update. I assume this to be a different update since its around 29MB instead of the previous 9MB one.

So now I'm on 2.17. But I'm still on PRI 1.53
[HTC EVO 3D] mogul420:
before i do this, i want to make sure this applies to me.

right now, im on 1.42_003, 1.06.00.0426 (i did freeza's original and second VM firmwares) and now im having the ocassional SMS/call issues. lately worst than before.

i dont know if this issue is related to that or of Sprint is having problems.

thanks!
[HTC EVO 3D] MikeC84:
I don't think it is Sprint, I am having issues with receiving some calls / texts. It is definitely vm firmware.

I have been waiting for Unknown's fix, speaking of, Have any luck patching our p19.img's Unknown?
[HTC EVO 3D] mogul420:
ok. does this method fixes the issue?

also, is Unknown's about to do a flashable fix for this problem that deserves us to wait for it?
[HTC EVO 3D] IOwnCalculus:
I think it's actually a combination of the two. I've got the VM firmware and even with the .145 PRI and a Sprint PRL, I would get the same problems everyone else has been getting with texting / data... except it was only when I was traveling in the Indianapolis area. Before I went there and after I got back, I've had no such problems anywhere in Phoenix.
[HTC EVO 3D] genstukov:
Did this die
[HTC EVO 3D] Will32:
I hope not
[HTC EVO 3D] tatnai:
I hope not too. running out of options for not having intermittent sms and call issues if this is no longer being worked on.
[HTC EVO 3D] jlechner:
It's still being worked on. Unknown has a ton of personal stuff going on, doing what he can when he can.

Sent from my Sprint/Virgin Mobile hybrid
[HTC EVO 3D] linty:
Echo.... Echo.... Echo......
[HTC EVO 3D] gotanmp3:
I know I'm kinda restating what might already be known here, but it looks like the Virgin firmware was actually intended to convert a Sprint EVO 3D into a Virgin EVO V by rewriting some of the NV items (which always survive an RUU, that's why you don't lose your MEID). The proof seems to be that many of the EVO V phones are still "Sprint" branded on the front (leftover old stock), so it makes sense they would design the update to behave this way.

A fix probably involves having a complete backup of your NV items prior to "Virginizing" and restoring them in EFS explorer. Unfortunately, I'm not willing to risk my Evo 3D to put this theory to the test.
[HTC EVO 3D] alammori:
Do you mean, if I take a backup of the NV Items of my wife untouched 3D and restore it to my 3D, This will fix it?
[HTC EVO 3D] HSadler93:
Your wife has different information on her Evo 3D so no that would not work.
[HTC EVO 3D] Felnarion:
That actually makes a lot of sense. It would be able to instantly rebrand all the overstock Evo3ds for sale through Virgin.
[HTC EVO 3D] gotanmp3:
The end result would be a cloned phone. You'd need your original NV backup.

It might be possible to figure out which NV items were changed and fix them individually. It's just a pain because EFS Explorer is insanely slow on the EVO 3D.

Edit: I've done a few comparisons against an actual Virgin EVO V. Annoyingly, this only seems to be a cosmetic fix and there are quite a few different NV items other than what I'm listing, but here goes...

NV 43 is SPG, it's supposed to be SPCS

NV 71 is the "short" banner, it says Virgin (would be Sprint on a Sprint Evo)

NV 8016 has the PRI version number.

NV 8042 is the infamous "Virgin Mobile" banner. Delete or change to Sprint.

NV items can be edited on a completely stock ROM, so if you want to make it look normal to get it exchanged under warranty - there you go.
[HTC EVO 3D] SITH16:
So are we now thinking that a completely stock sprint ics update rom won't fix this?
[HTC EVO 3D] jlechner:
Still unsure until it comes out.

Sent from my Sprint/Virgin Mobile hybrid
[HTC EVO 3D] seanjenks:
Say would u happen to know why some people cant flash any other roms such as miui or any 217 roms only sense 3.6 and 4.0 roms?
[HTC EVO 3D] jlechner:
It's not because of this. I can flash anything.

Sent from my Sprint/Virgin Mobile hybrid
[HTC EVO 3D] Unknownforce:
Hey guys, I'm still alive. And trying what I can when I can, personal life is very hectic right now...

As to an update... I'm losing hope in the method that I'm pursuing. No matter what I do, it somehow seems to destroy radio configs, and disable the radio... To make it worse, I can't test it because everything I do on my device works...

But, instead of trying to get it functioning in a "patch", what I am thinking I might do is work with people on an individual basis to get it fixed for them.

What I'm thinking is... the person sends me their radio config, I correct it, send it back and have them flash it while temp-bricked using a new tool that I've created, similar to the downgrade hboot method.

I have once again deleted all the partition 19's that I have been sent by everyone here in an effort to ensure user security and confidentiality. I don't want your info in someone else's hands anymore than you do. It's bad enough that it has to be in mine.

Now, please read everything here before jumping the gun and asking for a fix right away... it's all very important here...

First...

I will do these on a "first come, first serve" basis but I strongly recommend that if you don't know how to use DFS or QPST or linux very well (or can't picup on it quickly) that you wait for a little bit until I get some results from this. I can walk you through fixing things if they go bad, but I'd rather have the slightly more experienced testing first.

Second...

This is still a test, not a promise of it working. And there is a big possibility of it doing the same as before (wiping radio_config and killing radio) But I do know the fix to get it up and working again, but it's really a pain in the wazoo and requires the use of some of the advanced tools. So the risks are clear...

Now, I don't know how many people there are out there that have the VM plague, but I'm willing to fix them as I can. I can't promise any specific deadline or time frame on when I can get it back to you, cause my personal life is quite busy at the moment...

So, if you would like to try this, do the following...

adb shell dd if=/dev/block/mmcblk0p19 of=/sdcard/p19.img

adb pull /sdcard/p19.img (or just mount as a disk drive and copy it off the sd card if you like)

put the p19.img file into a zip file. (30-70k is better than 8MB)

Retain this p19 somewhere safe where you can find it, if things go south, you'll need it to fix stuff.

Also, download the 1.13 RUU, the 2.17 all in one firmware, QPST, and DFS. (demo works)

I suggest not putting it on a hosting site, who knows who can get at it. So send me a PM and I'll send you my email address to send it to and when I get it fixed, I'll send directions the updated file, and download links to the files you'll need.

I work M-F 8AM - 5PM Central Time, So, I will start working on these tonight after I get off work, but again, don't expect a quick turn around, my personal life is very complicated right now, so I'm doing XDA stuff as much as I can.
[HTC EVO 3D] jlechner:
I think it's time to hex edit the 2.17 firmware and if the ics firmware isn't greater, just hex edit it too

Sent from my Sprint/Virgin Mobile hybrid
[HTC EVO 3D] digiSal:
Whats the sure fire way to tell if I am affected by this VM plague? I flashed the firmware when it came out. Two files.

But I have no problems whatsoever but this thread makes me nervous. I do have the Virgin banner.

Im on Hboot 1.4 and have S-off

my radio is 1.06.00.0426

Please advise. I wanted to send Unknown the partion he asked but have never used DFS or QPST. ADB is no problem.

My main questions is can I flash other roms? Or am i stuck here because of the plague.

thanks everyone.
[HTC EVO 3D] jlechner:
You can flash other roms, but right now your stuck on VM firmware.

Sent from my Sprint/Virgin Mobile hybrid
[HTC EVO 3D] gotanmp3:
Just thinking out loud here, how about instead of patching the damage, rewriting the partition entirely with one copied from an Evo 3D that's never seen the Virgin firmware? You'd have to patch the MEID, ESN, default NAI and M.IP profile 0 AAA, but at least they'd be in a known location.

I'd at least like to try that out myself, if you wouldn't mind sending me a copy of the partition writing tool. Thanks!
[HTC EVO 3D] Punk9:
I did the fix in the OP, I flashed the ENG hboot, where can I find the file to go back to the nomral hboot if needed? (Hboot 1.4)
[HTC EVO 3D] Will32:
Hboot 1.4 in a pg86img, here ya go http://db.tt/Wi10Ynkl

Sent from ZR3DX
[HTC EVO 3D] ulum_joe:
well... I think I just destroy my radio... hope Unknowforce can help me with...
[HTC EVO 3D] Will32:
How'd you do that?
[HTC EVO 3D] jlechner:
If anyone besides me is getting stuck in 1x all the time, solution is to either flash or use boot manager to get to a 2.17 stock ROM, download an order PRL. Then use ##775# to select it and reboot. Then you can go back to whatever ROM you were on. Recovery restore might revert it back.

Sent from my Sprint/Virgin Mobile hybrid
[HTC EVO 3D] Will32:
I'm getting the 3g icon but barely and data at all. Won't load web pages, won't profile/prl update. It will hands-free activate though. If I do ##786# reset I get no signal and it changes my msl to 000000 and won't activate. I have to restore a qpst backup just to get activated but still won't update profile/prl. Everything in ##data# is correct, I checked it against screenshots I took when I had data. Ideas?
[HTC EVO 3D] vin255764:
Same story here and msl 000000...So you probably did rfg_2 thing?

What is interesting,when I sold my 3vo @sprint store,girl activated it and never called me back about data problems.

May be she is in 4g area,may be activation to different account fixed 3g...

She had my number,there is a good chance that reactivation fixed it..
[HTC EVO 3D] jlechner:
Some one tried that on here, he was swapping phones with his wife or daughter...

Sent from my Sprint/Virgin Mobile hybrid
[HTC EVO 3D] Unknownforce:
RFG_1 does this.

Some people's phones do not have a rfg_1. Their Partition 19 doesn't even have it in them. (This starts at offset 0x100000)

I figured that was the reason why people were having issues with my first test, so I had him flash rfg_1, and it finally worked after going back to stock 2.17 and being on eng hboot. Problem is, the MSL is 000000 in the rfg_1 that is supplied with all the updates. Now... It doesn't "fix" this when flashing it and doing a hands free, I would think that the activation would pull this in... I had him try many things to get it to populate the rfg_1 with the correct info... All, unsuccessfully.

Not even QPST could get it to show up in RFG_1, it would change the MSL on the phone, but not in the rfg_1 partition, where it needs to. But, this MSL is also part of RFG_1, and the way it seems to work is that in the event of a wipe, the phone looks to rfg_1 first for this info. And apparently elsewhere as well, although, there's nowhere else in the radio_config that holds the MSL...

Everytime I seem to get further with this, I hit another brick wall... It's like a silly rat maze... lol

But, I do think that if we can get the phone to populate the rfg_1 partition, we can finally wipe out the VM shtuff from partition 19 without killing the radio and causing a full reset.
[HTC EVO 3D] jlechner:
Can you run a Ruu from from fastboot?

Sent from my Sprint/Virgin Mobile hybrid
[HTC EVO 3D] Will32:
Yes, and I have. I ran the 2.17.exe and the 1.13.exe from hboot. Also the 1.13, 2.08 and 2.17 pg86ing.
[HTC EVO 3D] Will32:
Alright, so after a lot of tinkering. I managed to completely kill the radio, no service at all. As unknownforce stated earlier, my rfg_1 won't populate with the info that its supposed to. As he also said, the rfg_1 is a kind of backup that the phone looks to when you ##786# reset. So my phone doesn't know what to add to the data profile or whatever when I ##786# reset, but what's weird is when I ##786# reset, somehow I can still handsfree activate and all the stuff in ##data# comes back. So this info has got to be somewhere else also (as he also stated).

The way I finally killed the radio was to ##786# reset and run the 1.13 ROM pg86img before it had a chance to activate. The radio is dead after that combo on my phone, I assume that it looked at the rfg_1 and saw nothing there. So like I said, after the ##786# reset alone, I could still activate and call/text or after any ruu I could still activate call/text. So it got the info from somewhere, that somewhere has to be in a place that the 1.13 ROM pg86img erased. It's last hope to restore at that point was the rfg_1 which wasn't populated.

I can easily get talk/text and handsfree activation back with a software download restore. I made a backup with apn backup/restore and I'm about to try to restore it to see if it helps but I'm not optimistic. If it works ill post again.

I was also able to downgrade to pri _003 even after the nocturnal fix, but I did so much stuff that I don't know exactly how i did it.

This post probably sounds confusing, sorry, that's because I'm confused with all this, lol.
[HTC EVO 3D] jlechner:
You did that via the op?

Sent from my Sprint/Virgin Mobile hybrid
[HTC EVO 3D] Will32:
No, I did the op fix back when this thread was started but it didn't work for me. And I just tried apn backup/restore and it didn't help.

Also, when it downgraded my pri, my msl changed to 00000, which I changed back with a service programming backup.

I wish I could remember exactly what all my steps were but it gets blurry after so much stuff, I'm only messing with one messed up phone and I can't remember. I can't imagine how much of a headache this is for unknownforce since he's trying to fix a lot of phones and he doesn't even have a messed up phone to test on.
[HTC EVO 3D] jlechner:
So your not sure how you downgraded pri?

Sent from my Sprint/Virgin Mobile hybrid
[HTC EVO 3D] Will32:
I couldn't tell you right now, let me look all my stuff on my comp, ill see if I can retrace my steps. But I can tell you that if you have working data, you don't want to do what I did. Unless your rfg_1 is populated. My data was fine, but the rfg_1 was basically blank, it might have been like that since I erased it when I tried the op fix. It might have been the 2.17 ruu.exe that did it. I think I remember vin saying he lost ability to update profile/prl after a ruu.exe.
[HTC EVO 3D] Will32:
Just for the sake of testing everything I can think to test, I decided to s-on and re-run revolutionary. I've heard that running revolutionary will mess up a phone that's flashed to a prepaid carrier. Well, it killed my radio, time to restore from software d/l to get call/text/activation back. After I ran revolutionary, I got a notification for an ota, it was the 2.08 and it was 49 mb. So I said what the hell and took it. It didn't seem to do anything but upgrade my hboot to 1.5, it didn't change my prl either. Oh well, ill keep trying to fix it.
[HTC EVO 3D] Unknownforce:
Sorry, internet was down today... had to get up on my roof and re-mount my dish for the wireless, apparently it couldn't get signal through two trees... Silly line of sight...

Anyways... here's how to downgrade the PRI (but don't do this because it ****s up the MSL)

First thing is that I don't know if this works if your RFG_1 is intact. For his instance, he had NO rfg_1 at all. Anyways....

First return to 2.17 stock (S-OFF)

Flash ENG Hboot

run fastboot erase rfg_1

then fastboot flash rfg_1 rfg_1.img (pull this image from the 2.17 firmware or RUU)

then, do a ##786# and reset and hands free activate.

This will put you back to 1.42_003. However, this will also reset your MSL to 000000 (after the reset)

I'm guessing this only works if your rfg_1 is blank. I would also venture a guess that it doesn't work on a "working" rfg_1 because it most likely won't erase it once it's there...

Because what seems like is happening is that it reads the info from rfg_1 during the activation. So it pulls in the blank MSL and zero'd out everything and screws stuff up.

Our main concern is with populating rfg_1, if we can get the phone to re-populate the partition with the correct unique phone info, the rest is cake, cause it seems like if that partition is in tact, you can fully mess the whole partition 19 and NOT break the radio, because the "backup" rfg_1 is working...
[HTC EVO 3D] wwjoshdew:
Hey Unknownforce, I have an EVO3D that's been upgraded to the Virgin Mobile firmware, and I have hboot 1.4 (never ever EVER updated to an official update from HTC since July 2011!) and I would like to send it to you if you need it! I make videos with it, so I'd need it back some day (if we ever get 4G and etc working on this thing) to make videos with. But it would be yours to hack away with! I'd even cover the shipping. If you're interested, send me a message! :)

I have one concern, if you bricked it, the last time I had service on it was May 24th. I never used HTC Dev, so my warranty isn't void. Should I activate it before I send it, if you want me to loan it to you?

I think there is a rule where as long as it's been on your account in 30 days (or something like that) you can still get it repaired... Since the EVO 4G LTE is my daily device until the SGS3 comes out.
[HTC EVO 3D] Unknownforce:
Oh man, that would be so helpful! I am constantly struggling to test anything cause I use my own device as my personal phone and daily device for work as well...

I can even ship it back at no cost (free FedEx at work ;) )

But yeah, this would make things SOOO much easier to test things on!!

I'll toss you a PM with my info shortly.
[HTC EVO 3D] wwjoshdew:
I got you! I can activate it, then go back to my EVO 4G LTE that way if something goes wrong and it can't be brought back, you can send it back and I'll just get a replacement. (Hopefully it works that way) I get paid Friday, and I'm BROKE until then. (Married with a kid, and suck at managing money! lol)

But I got you. My wife isn't too happy, but I don't even use the device (except for playing with Devil's Toast and other AOSP roms) But if this will help the community, I'm all towards sending you my phone to hack away with for a little bit. I read that AS LONG AS the phone has been on your account in the last 30 days, you can get it repaired. :)

EDIT: Going to be mailing the phone off tomorrow! :)

Nice talking to you Unknownforce, try to send it back in one piece! Lol
[HTC EVO 3D] closeone:
Hi Unknown,

You may have already answered this. Just out of curiosity, what happens when you edit an actual dump of an rfg_1 partition with the MSL (and other data)? I found my MSL using a hex editor.

It appears that the MSL is there, in full on one line, then the last four digits of it are just a tad lower.

Right under where the
00nt - line is.

U.--123456 <- Would replace the 000000 here.
[...]
k.----3456 <- Would replace the 0000 here.
[...]
Then, the data further down?

--

By the way, just want to say thanks to Josh for sending his phone out.

And thank you to Unknownforce for continuing to look into the issue.

~co~
[HTC EVO 3D] Unknownforce:
Yup, that's where the MSL is stored, after a ##786# reset it will use that number as it's MSL. Like I said, rfg_1 is like a "backup" for when the device is reset.

I can set little things like that in the partition, but going through and setting every little detail in that partition the way it should be would take forever, plus some of it is encrypted, not just in plain text like the MSL and phone numbers and such are.

The key here is to figure out how they get this partition to populate from the current device information and inject it into rfg_1. Having a device to test this on is definitely going to help me get through this.
[HTC EVO 3D] closeone:
Unknownforce,

I apologize. :(

Don't hesitate to contact me if you need a boot CD, or something else made up. I'm still with you and everyone in this thread.

~co~
[HTC EVO 3D] Unknownforce:
No need for apologies. I welcome all ideas. I'm not trying to sound condescending at all. It's just that I've gone over this partition so many times that I know most of the things that people are going to bring up about it, that's all. ;) I'm just explaining, that's all.

Once I have this test device that disturb3d1 will be sending me. It will make testing so much easier.
[HTC EVO 3D] wwjoshdew:
Got the shipping label right next to me, and the phone (in an amazon box) in my truck. Gonna ship it out as soon as I get off work in a few hours! :)
[HTC EVO 3D] jcfunk:
When you do ##786# or " ##__786#, can't remember code but does reset but not erase user partition" on full stock install; ie Hboot, recovery, and system. Will it fill rfg_1?

Will test tonight when I get off from work.

Sent from my DOWNGRADED EVO 3D
[HTC EVO 3D] Unknownforce:
I haven't tested that exact scenario, But I know stock rom (not rooted) with eng hboot (not sure of recovery) has been tested, and it didn't populate it.

But when I have the other device on friday, I'm gonna be testing it's butt off.
[HTC EVO 3D] wwjoshdew:
It's out of my hands now...

http://db.tt/Oi6RRrOB

There isn't a time frame that I need it back by, just as long as I get it back in a reasonable amount of time I'm happy. I make videos with that thing, please take care of it! :)

PS - What am I saying. I've dropped it more times than I can count! haha
[HTC EVO 3D] closeone:
Thanks Unknown. I completely understand. I should have realized that when I posted that.

+1 to this. I don't normally say that, but I swear that I was actually going to post something similar to what you were saying last night. ##786# is ##SPC#. On a stock ROM, it should reset everything (without wiping partitions). Or allow you to fill the MDN AND MSID with 0s in order to force HFA. What may need to be checked into is the AAA key (?) as well as data usernames and passwords. (info was grabbed from another forum. Can't post it as it's may be against the rules). Just search "##786# reset." You'll find what I was looking at.

~co~
[HTC EVO 3D] jcfunk:
Got it ##72786# Sprint had me do this when I lost data, to reset and not lose my stuff

Sent from my DOWNGRADED EVO 3D
[HTC EVO 3D] Unknownforce:
Oh I knew that code if you needed that, sorry. But I don't think it repopulates the partition like we want.
[HTC EVO 3D] wwjoshdew:
Somebody should receive my EVO3D today! ;-)
[HTC EVO 3D] Unknownforce:
Just got delivery confirmation ;) I'll run down and grab it this afternoon. Work is... a little busy today :/
[HTC EVO 3D] NexuGsx:
Hey guys. There's supposedly a new leak out for Asian GSM units - http://xdaforums.com/showthread.php?t=1555732&page=39 - I'm not sure if there's anything that would help us (considering it is a GSM RUU), but I thought I'd share the link just in case.

EDIT: Also mentioned here I believe - http://xdaforums.com/showthread.php?t=1555732&page=39