Develop Bugs

Trying to avoid a brick! Quick help.

I got myself into a interesting situation. A quick answer would be greatly appreciated:
1. I'm rooted.
2. Trying to install the OTA so I can run 2.2 the right way.
3. I started a thread asking for help because I was confused on unrooting my phone. Didn't get much help, a quick flame, and last someone chimed in to install the OTA from Rom Manager. I asked if I could do this with Root and the thread was killed.
4. I did. The boot screen was the new one. But the radio wasn't updated.
5. I then attempted to unroot my phone. Followed the PB31IMG.zip method. Phone booted normally. Root was lost.
6. This is where I am now.
7. My question is, if I install the OTA now renamed update.zip on my SD card, will I run the chance of bricking my phone because I installed it once from Rom Manager while I had root (#3/#4)??????
Please advise so I don't MOD EDIT up my phone.................
And if you're going to flame and insist I should of just followed the 2.2 leak instructions, you're correct. But I took someone's quick answer and tried it assuming they knew a better method.

mapko11 said:
I got myself into a interesting situation. A quick answer would be greatly appreciated:
1. I'm rooted.
2. Trying to install the OTA so I can run 2.2 the right way.
3. I started a thread asking for help because I was confused on unrooting my phone. Didn't get much help, a quick flame, and last someone chimed in to install the OTA from Rom Manager. I asked if I could do this with Root and the thread was killed.
4. I did. The boot screen was the new one. But the radio wasn't updated.
5. I then attempted to unroot my phone. Followed the PB31IMG.zip method. Phone booted normally. Root was lost.
6. This is where I am now.
7. My question is, if I install the OTA now renamed update.zip on my SD card, will I run the chance of bricking my phone because I installed it once from Rom Manager while I had root (#3/#4)??????
Please advise so I don't MOD EDIT up my phone.................
And if you're going to flame and insist I should of just followed the 2.2 leak instructions, you're correct. But I took someone's quick answer and tried it assuming they knew a better method.
Click to expand...
Click to collapse
Wat is the hboot versoin?
Sent from my Incredible using XDA App

Where do I find that out?

mapko11 said:
Where do I find that out?
Click to expand...
Click to collapse
In the bootloader it should say.
Sent from my Incredible using XDA App

Hboot-0.79.0000

mapko11 said:
2. Trying to install the OTA so I can run 2.2 the right way.
Click to expand...
Click to collapse
Well, "the right way" would be to wait for the actual OTA. Verizon would also have your back if you brick. But, anyway...
If you're still on the 1.00.03.04.06 radio, you can probably follow the instructions in that thread now that you've flashed back to the stock ROM. However, there still seem to be a few cases of people bricking their phones or being stuck in a bootloop after flashing leaks.
If you are confused/concerned/afraid of bricks then you just shouldn't flash the leaked OTA. This is not a flame, this is sound advice. Wait for the real one.

I'm fine with flashing. I just keep hearing about this "double install OTA and brick your phone" issue and I'm trying to avoid doing that. If the one guy didn't chime in with the suggestion to use ROM Manager, I wouldn't of had this issue.

My radio is still 1.00.03.04.06. I just want to make sure I don't run a risk of bricking.

If the hboot updated, i would say not to apply again. If it didnt update then i would say to see what happens, but dont take my word for it 100%
Sent from my Incredible using XDA App

jdkoreclipse said:
If the hboot updated, i would say not to apply again. If it didnt update then i would say to see what happens, but dont take my word for it 100%
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
How do I know if the HBOOT has been updated? I posted my version above?

mapko11 said:
How do I know if the HBOOT has been updated? I posted my version above?
Click to expand...
Click to collapse
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App

jdkoreclipse said:
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Anyway to undo this and go back?

mapko11 said:
Anyway to undo this and go back?
Click to expand...
Click to collapse
Try the PB13IMG.
Sent from my Incredible using XDA App

jdkoreclipse said:
Try the PB13IMG.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
And you needed to un root before applying the ota
Sent from my Incredible using XDA App

jdkoreclipse said:
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
I personally have had a .77 HBOOT since I got my phone in April. My mom's phone, on the other hand, had the .79, which she has had since May, and she sure as hell didn't have no 720p camcorder. I don't think that the OP's phone having .79 means with any certainty that the OTA already applied once. I think the radio version listed on the HBOOT screen would be a better indicator.
But absolutely, running the PB13IMG should ensure that he's as far back as he can go, so why not try it just to be safe...

jdkoreclipse said:
Try the PB13IMG.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
That's what I just did before I posted this thread. I installed the PB13IMG and restored everything back to stock. You asked about the HBOOT version and that's .79. I'm comfortable flashing and doing the update. What should HBOOT say? Has anyone successfully updated the OTA from .79 HBOOT?
Thank you for the help. Sorry for the questions. I completely comfortable with rooting, flashing roms, and kernals. This is going back to unroot stock is just new.
I want to install the OTA and I'm good to go. Just making sure it's safe now....

alexdw369 said:
I personally have had a .77 HBOOT since I got my phone in April. My mom's phone, on the other hand, had the .79, which she has had since May. I don't think that the OP's phone having .79 means with any certainty that the OTA already applied once. I think the radio version listed on the HBOOT screen would be a better indicator.
Click to expand...
Click to collapse
Thats a high possibility that hboot means nothing in this scenaroi, but im not gonn. Be risky with someome elses phone. I only provide methods of doing things that i would use on my phone too.
Sent from my Incredible using XDA App

jdkoreclipse said:
Thats a high possibility that hboot means nothing in this scenaroi, but im not gonn. Be risky with someome elses phone. I only provide methods of doing things that i would use on my phone too.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Agreed, however, I noticed after running the PB13IMG, my HBOOT was also .79, which could have only come from the PB13IMG since I hadn't tried to do the OTA yet. Just trying to add pieces to the puzzle to get a better picture for future reference...I'm sure this guy wont be the last to ask...

alexdw369 said:
Agreed, however, I noticed after running the PB13IMG, my HBOOT was also .79, which could have only come from the PB13IMG since I hadn't tried to do the OTA yet. Just trying to add pieces to the puzzle to get a better picture for future reference...I'm sure this guy wont be the last to ask...
Click to expand...
Click to collapse
I appreciate the help guys. I guess my question would be if I ran PB13IMG, lost my root, back to stock, my HBOOT is .79 and my radio is still 1.00.03.04.06 and not 2.05.00.06.11, I should be at the same point as everyone else for installing the OTA from my SD card. Right or wrong?
When you read these threads and people are installing the OTA twice and bricking, are they installing the OTA again when the radio is already updated to 2.05.00.06.11?

Yep. I think you can flash it again, but be real cautious, as this is your second time flashing it, but if the radio is still the old versoin, you should be safe.
Sent from my Incredible using XDA App

[Q] rom manger not wrking (?)

ok so my mt3gs is rooted blah blah blah but it wont book to clockwrk thrw the rom manger it just comes up with a triangel and the ! mark (cant spell it) my question is y ? do i need to flash the eng spl or what ? thanks in advanced

rok0187 said:
do i need to flash the eng spl or what
Click to expand...
Click to collapse
Yes, you do.
Edit: And your post would be Q&A, not development.

Did u try pressing volume down and power at the ! Screen? I know clockwork usually comes up directly using rom manager, but you can still get to clockwork that way.
Sent from my myTouch 3G Slide using XDA App

rok0187 said:
ok so my mt3gs is rooted blah blah blah but it wont book to clockwrk thrw the rom manger it just comes up with a triangel and the ! mark (cant spell it) my question is y ? do i need to flash the eng spl or what ? thanks in advanced
Click to expand...
Click to collapse
You need to update the recovery from rom manager.
Sent from my T-Mobile myTouch 3G Slide using XDA App

None of these suggestions are going to do any good if he hasn't the flashed the engineering image.

ok just relized its in the wrong section and yea i read some wear u didnt need to flash the eng spl but i guess i have to so off to do that

I did previously flash the ENG build and I have to go through the first part of the root process every time I want to use Clockwork. I'm sure I'm doing something wrong...

Sleef said:
I did previously flash the ENG build and I have to go through the first part of the root process every time I want to use Clockwork. I'm sure I'm doing something wrong...
Click to expand...
Click to collapse
for real well iam not in any rush to flash the eng spl so i think iam just stick with the push methoid

rok0187 said:
for real well iam not in any rush to flash the eng spl so i think iam just stick with the push methoid
Click to expand...
Click to collapse
Why would you not flash the eng? It takes 5 minutes that save on asking repetitive questions. Many people will tell you that you DON'T need to flash it, but if everybody flashed the eng build, everytime there was a problem people wouldn't have to ask, "Did you flash the eng build?" Kind of a time-saver and yes it irons out ALL the kinks other than user error.
The belief that it WASN'T necessary was started by Wes Garner because one of his ROMS never installed correctly, but to this day, it still remains uninstallable...so it has nothing to do with the eng build being the prob.
Just my 2 cents, bro.

jreed3786 said:
Why would you not flash the eng? It takes 5 minutes that save on asking repetitive questions. Many people will tell you that you DON'T need to flash it, but if everybody flashed the eng build, everytime there was a problem people wouldn't have to ask, "Did you flash the eng build?" Kind of a time-saver and yes it irons out ALL the kinks other than user error.
Click to expand...
Click to collapse
The engineering rom being optional is like saying leaving gas in your car is optional. I mean, sure, you could always leave it empty and walk to the gas station with a can and come back every time you wanted to start it, but its a heck of a lot easier if you just leave some gas in the tank for next time.

Tick...tick...tick....
falken98 said:
The engineering rom being optional is like saying leaving gas in your car is optional. I mean, sure, you could always leave it empty and walk to the gas station with a can and come back every time you wanted to start it, but its a heck of a lot easier if you just leave some gas in the tank for next time.
Click to expand...
Click to collapse
BOOM!!!!! goes the ATOM BOMB!

Sleef said:
I did previously flash the ENG build and I have to go through the first part of the root process every time I want to use Clockwork. I'm sure I'm doing something wrong...
Click to expand...
Click to collapse
is the update.zip file on your memory card. If it is then all you have to do is flash the update.zip from the recovery menu or just use rom manager
Sent from my T-Mobile myTouch 3G Slide using XDA App

lstevens86 said:
is the update.zip file on your memory card. If it is then all you have to do is flash the update.zip from the recovery menu or just use rom manager
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
It is on my SD card but I have to do the adb loop process and push the update after unsuccessfully flashing the update just like the first time I rooted. Rom Manager is not getting me into Clockworkmod recovery.

Sleef said:
It is on my SD card but I have to do the adb loop process and push the update after unsuccessfully flashing the update just like the first time I rooted. Rom Manager is not getting me into Clockworkmod recovery.
Click to expand...
Click to collapse
did you use eugene's eng on your phone or wes's champion build
Sent from my T-Mobile myTouch 3G Slide using XDA App

lstevens86 said:
did you use eugene's eng on your phone or wes's champion build
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Pretty sure it was Eugene's. I also later ran the corrected .nbh file.

What an odd typo. I meant the ESPRIMG.zip.

Sleef said:
Pretty sure it was Eugene's. I also later ran the corrected .nbh file.
Click to expand...
Click to collapse
You have restored your phone back to stock recovery doing that. You need to reinstall the engineering image.

falken98 said:
You have restored your phone back to stock recovery doing that. You need to reinstall the engineering image.
Click to expand...
Click to collapse
Yeah Falken is right reinstall the engineering image. And that should solve it.
Sent from my T-Mobile myTouch 3G Slide using XDA App

Even before I ran the ESPRIMG.zip I couldn't get straight into Clockworkmod.
Thanks for helping, by the way. I have to go into work now but I'll give re-flashing the ENG build later.

Sleef said:
Even before I ran the ESPRIMG.zip I couldn't get straight into Clockworkmod.
Thanks for helping, by the way. I have to go into work now but I'll give re-flashing the ENG build later.
Click to expand...
Click to collapse
Just make sure you keep the update.zip on your sd. It didn't let you get straight into clockwork anyway. You need rom manager or bootloader to recovery then update.zip will get you in everytime with the ENG build
Sent from my T-Mobile myTouch 3G Slide using XDA App

[Q] Inc in bootloop - even after RUU install

Hi - I've got a rooted AMOLED Incredible.
Yesterday, it went into a bootloop. I could get to HBoot but could not get into recovery. I tried flashing multiple other recoveries but still could not get into it from HBoot (it would go into a bootloop every time I chose "Recovery" from HBoot).
Today, I installed an RUU from this post: http://forum.xda-developers.com/showpost.php?p=11717873&postcount=2
It updated, and then when I rebooted, it went into the same bootloop, this time with the stock splash screen.
I have HBoot 0.92, Radio 7.28. I'm S-off. I've formatted my SD card, and it's FAT32.
Anyone have any idea what's going on?
Thanks in advance!
-jaba

Is setcpu installed, and overclocking way high on boot? If setcpu is installed, you s/b able to mount device in adb and remove it.
Sent from my ADR6300 using XDA Premium App

smtom said:
Is setcpu installed, and overclocking way high on boot? If setcpu is installed, you s/b able to mount device in adb and remove it.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
no setCPU installed.

Can you dl another ROM like Virtuous and put it on sd, then flash it?
Have you tried another sd?
Sent from my ADR6300 using XDA Premium App

smtom said:
Can you dl another ROM like Virtuous and put it on sd, then flash it?
Have you tried another sd?
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
I can't get into recovery with bootlooping.
I'll try another SD card.

Basically at this point I'd be happy to get the phone to S-On so that I can take it back to Verizon. Unfortunately, I don't know how to do that as I can't access Recovery without going into a bootloop. I've tried to flash other recoveries and they all put me into a bootloop.
Anyone with any thoughts on how to get s-on without recovery?
Thanks!

I would say flash a bp31img through hboot. That should put you s-on i believe. If you cannot find a pb31img ill come back latter with a link for dl. The pb31img should put you completely stock. The image i have though is from the first shippments of 2.1 but its still stock.
Sent from my Incredible using Tapatalk

linuxmotion said:
I would say flash a bp31img through hboot. That should put you s-on i believe. If you cannot find a pb31img ill come back latter with a link for dl. The pb31img should put you completely stock. The image i have though is from the first shippments of 2.1 but its still stock.
Sent from my Incredible using Tapatalk
Click to expand...
Click to collapse
I tried that and it didn't work. Thanks, though.
I took the phone to verizon and they are sending me a new one.

Any solution to this?

To get s-on you need to be able to access recovery. Also what rom were you on when the phone messed up, was it cm7?

cmlusco said:
To get s-on you need to be able to access recovery. Also what rom were you on when the phone messed up, was it cm7?
Click to expand...
Click to collapse
I was on SR 4.2 but I figured it out. The first time I RUU'd the phone was shaking all over the place so I think that just ****ed it up. I reflashed the RUU and it's good to go. I decided I am just going to sell it to my buddy as a stock unrooted with S-OFF, screw it.
Thanks though.

REYES702 said:
I was on SR 4.2 but I figured it out. The first time I RUU'd the phone was shaking all over the place so I think that just ****ed it up. I reflashed the RUU and it's good to go. I decided I am just going to sell it to my buddy as a stock unrooted with S-OFF, screw it.
Thanks though.
Click to expand...
Click to collapse
Don't give up hope just now to S-ON. Have you read the below page for getting S-ON?
http://unrevoked.com/rootwiki/doku.php/public/forever
It should work with stock recovery as long as you're on one of the listed radios.
Get the unrevoked-forever-son.zip and follow instructions for unrevoked-forever.zip, renaming to update.zip

Quick question, I RUU'd back to Froyo so can he still receive the OTA with S-OFF? Or does it need to be S-ON?

REYES702 said:
Quick question, I RUU'd back to Froyo so can he still receive the OTA with S-OFF? Or does it need to be S-ON?
Click to expand...
Click to collapse
It can be s-off but everything else must be stock, including recovery and having all original apps. Since its s-off rooting after the ota is no problem if desired.

[Q] Return to COMPLETE Stock?

Ok so i need to send my inc 2 in for a refurb. I am currently running AOKP build 37 with aeroevans v9ics kernel and an unlocked BL. How do i return to complete stock unrooted?
i've seached all over the forum and can't find anything. It was easy with my droid x2 because you could just run the SBF with RSD Lite.
I also have the new software version 6.1 if thats any help.

Here you go: http://forum.xda-developers.com/showthread.php?t=1599767
Nicely posted by CondemnedSoul.

blazingwolf said:
Here you go: http://forum.xda-developers.com/showthread.php?t=1599767
Nicely posted by CondemnedSoul.
Click to expand...
Click to collapse
there is only one problem. I have the newest OTA software 6.1.x.x.x.x. and that post is for the 5.10.605.9 OTA. Will this still work or will i risk effin up my phone.

dets34 said:
there is only one problem. I have the newest OTA software 6.1.x.x.x.x. and that post is for the 5.10.605.9 OTA. Will this still work or will i risk effin up my phone.
Click to expand...
Click to collapse
Your running AOKP right now right? According to your first post you are anyways. That means your not running the 6.1 anymore. In other words you should be fine.

blazingwolf said:
Your running AOKP right now right? According to your first post you are anyways. That means your not running the 6.1 anymore. In other words you should be fine.
Click to expand...
Click to collapse
hmm never thought about it like that. I guess ill give it a try and see how wise you truly are.

Just tried running the PG32IMG.zip file in bootloader and it didnt work. Still running AOKP. any other ideas. What about an RUU

dets34 said:
Just tried running the PG32IMG.zip file in bootloader and it didnt work. Still running AOKP. any other ideas. What about an RUU
Click to expand...
Click to collapse
Hmm. What did it say as it went through the process?

It didnt say anything. It found the PG32IMG.zip file, ran it, and then returned to the bootloader screen. I tried running it again just in-case something weird happened, but same result.
also on a side note im s-on, the 6.1 OTA doesn't allow s-off at this time

dets34 said:
It didnt say anything. It found the PG32IMG.zip file, ran it, and then returned to the bootloader screen. I tried running it again just in-case something weird happened, but same result.
also on a side note im s-on, the 6.1 OTA doesn't allow s-off at this time
Click to expand...
Click to collapse
I didn't think about that. That could be the issue then. No nandroid backup of your stock ROM right?
I'm thinking the best you can do is find a similar to stock ROM and install that. Most times the service techs don't look to hard at a device to see that it is running a custom ROM.

blazingwolf said:
I didn't think about that. That could be the issue then. No nandroid backup of your stock ROM right?
I'm thinking the best you can do is find a similar to stock ROM and install that. Most times the service techs don't look to hard at a device to see that it is running a custom ROM.
Click to expand...
Click to collapse
i believe i have a nandroid of my pre AOKP rom, but that is still rooted.

dets34 said:
i believe i have a nandroid of my pre AOKP rom, but that is still rooted.
Click to expand...
Click to collapse
Great! Use that and then download one of the apps that helps to remove root. One such app is OTA Rootkeeper. https://play.google.com/store/apps/...m9yZy5wcm9qZWN0dm9vZG9vLm90YXJvb3RrZWVwZXIiXQ..
Hopefully that will help.

blazingwolf said:
Great! Use that and then download one of the apps that helps to remove root. One such app is OTA Rootkeeper. https://play.google.com/store/apps/...m9yZy5wcm9qZWN0dm9vZG9vLm90YXJvb3RrZWVwZXIiXQ..
Hopefully that will help.
Click to expand...
Click to collapse
Thank heavens for my overly cautious brain

Sorry about taking you down the wrong path before. Forgot about the S-off thing with the newer version.

blazingwolf said:
Sorry about taking you down the wrong path before. Forgot about the S-off thing with the newer version.
Click to expand...
Click to collapse
not a problem. however now that i just restored to my nandroid i had before flashing the AOKP rom im stuck at the droid eye screen =(. any idea?

dets34 said:
not a problem. however now that i just restored to my nandroid i had before flashing the AOKP rom im stuck at the droid eye screen =(. any idea?
Click to expand...
Click to collapse
Did you clear dalvik cache?

blazingwolf said:
Did you clear dalvik cache?
Click to expand...
Click to collapse
cleared everything. i just tried flashing the andybonestock or whatever rom, and im getting the same thing. stuck at the droid eye.

nvm i take that back. the andybonestock rom flashed, just took a little while to load

dets34 said:
nvm i take that back. the andybonestock rom flashed, just took a little while to load
Click to expand...
Click to collapse
Cool. That one should work for you as well.

blazingwolf said:
Cool. That one should work for you as well.
Click to expand...
Click to collapse
how do i go about removing an trace of root. well at least the superuser app. besides that my phone "looks" stock.

dets34 said:
how do i go about removing an trace of root. well at least the superuser app. besides that my phone "looks" stock.
Click to expand...
Click to collapse
The app I listed above.
SuperUser can also just be deleted but the modified su will still be there.

[SOLUTION] So your Marvelc is refusing to flash a ROM

Okay I've been getting reports of roms not flashing right for the marvelc. So I set out for a solution and found one I believe. One issues with some roms, is that people have been doing it wrong since they got the phone. From Gsm recovery to even gsm roms. They used cmtd a very bad idea ect ect. So now, id like to present my method for fixing all of this. First, soff your hboot, then upgrade and unlock. install custom recovery and wipe all of the partitions. Then reboot to fastboot and flash the recovery posted bellow. Report back with any findings
http://goo.im/devs/simonsimons34/marvelc/cm9/tests/recovery.img

I was just wondering if you could give step by step instructions to flashing the recovery.img. File.

Download it. Rename to recovery.img. Place in the same directory as fastboot and adb.
Put your phone into fastboot (adb reboot bootloader).
Code:
fastboot flash recovery recovery.img

Simonsimons34 I have tried many things but this CWM actually let me flash a rom your great!! thanks so much and this worked for me

Glad to hear it this recovery has all the bugs with flashing and backups fixed so you should be good for the life of the phone
Sent from my Wildfire S A510c using Tapatalk 2

Does this fixes the Hboot not looking for PGIMG.zip files?

RRRb50 said:
Does this fixes the Hboot not looking for PGIMG.zip files?
Click to expand...
Click to collapse
No. A recovery can't fix HBOOT issue.

kalaker said:
No. A recovery can't fix HBOOT issue.
Click to expand...
Click to collapse
Is there a way to fix that?
Cause it dosnt check now.

RRRb50 said:
Is there a way to fix that?
Cause it dosnt check now.
Click to expand...
Click to collapse
Yes, but could you start another thread or link to a thread you've created. Let's keep this thread on-topic.

Isn't there a way to make it where it auto installs from hboot if so it'd help some ppl out ya know make it fool proof
Sent from my HTC-PG762 using XDA

sakisa950 said:
Isn't there a way to make it where it auto installs from hboot if so it'd help some ppl out ya know make it fool proof
Sent from my HTC-PG762 using XDA
Click to expand...
Click to collapse
brandonhun made one. http://forum.xda-developers.com/showthread.php?p=27765833#post27765833
Give him a "Thanks" if it helps you out.

kalaker said:
brandonhun made one. http://forum.xda-developers.com/showthread.php?p=27765833#post27765833
Give him a "Thanks" if it helps you out.
Click to expand...
Click to collapse
will it work with my problem and how to use it?

RRRb50 said:
will it work with my problem and how to use it?
Click to expand...
Click to collapse
Put on the root of your SD card. Put your SD card into your phone. Reboot your phone into HBOOT.

kalaker said:
Put on the root of your SD card. Put your SD card into your phone. Reboot your phone into HBOOT.
Click to expand...
Click to collapse
Tried that but didnt work.
When I go to HBOOT my mobile does not search for the PGIMG.zip files.
Is there a way to fix that?
I might make a thread if you say so.

RRRb50 said:
Tried that but didnt work.
When I go to HBOOT my mobile does not search for the PGIMG.zip files.
Is there a way to fix that?
I might make a thread if you say so.
Click to expand...
Click to collapse
Yes, please make a thread. It's best to keep this one on-topic.

RRRb50 said:
Is there a way to fix that?
Cause it dosnt check now.
Click to expand...
Click to collapse
Sorry to stray off-topic...
But you want to goldcard your sd card; that should help you with the old search engine
http://forum.xda-developers.com/showthread.php?t=1379543
Old Tut by Simon... 1-12 of s-off (OP) nets you a goldcard.
Sent from my HTC_A510c using Tapatalk 2

so far i have managed to get unlocked BL and s-off. i have flashed some GB roms, those are nice, i like the performance gains. one problem tho, i have to take this phone back to uscc because it is a loaner opps cant seem to help myself. i downloaded a ruu for wildfire s a510c <---my device however when i run the exe i get an error?? any help would be nice tnx
file i d/l::::RUU_Marvel_C_US_Cellular_WWE_1.02.573.00_Radio_0.94.00.0824_NV_USC_1.27_0826_PRL15107_release_219163_signed

To flash the RUU, You must Relock the bootloader first.
I can't be much help on returning the phone to s-on, other than to tell you it would take an image (before you s-off'd) and some jtag kung-foo skills
Not something easy.
Rob
Sent from my HTC_A510c using Tapatalk 2

insink71 said:
To flash the RUU, You must Relock the bootloader first.
I can't be much help on returning the phone to s-on, other than to tell you it would take an image (before you s-off'd) and some jtag kung-foo skills
Not something easy.
Rob
Sent from my HTC_A510c using Tapatalk 2
Click to expand...
Click to collapse
thanks so much for youre reply i do know some jtag kung foo skills! heh and fourteen other chinese words... this is my first ever time with an htc device! i have managed to learn a lot so far, my other device was a sgs flashed that sucker more times than girls gone wild! i am however anxiously awaiting my sgsIII
with that said, rock on with youre android device hacking...
p.s the rom i have is a stock rooted rom, of course custom kernel i added too, i can fool the uscc store upon return of the device except the phone info on lock bar ect says virgin mobile, i think its cool, but its gonna be hard to pull that one off i think lol

If you flash the RUU for your carrier it will give you a stock rom kernel and recovery so it won't say virgin mobile
Sent from my Marvelc using Tapatalk