Develop Bugs

[Q] Sending Incredible back to Veri.but rooted

I'm sending my Incredible back to Verizon for a new Inc. but I'm rooted with the new update. Want should I do so they don't know I rooted this phone. OK just check my phone I guest when I did the official update it unrooted me. I' still S-OOF. But I got to go back to original stock before I sent the phone back my phone should get to me in 2 days. So I need to put back 2.1 and S-ON.

Have you done unrevoked forever and turned off the S-off, if so you should probably not send it in.
The best thing you can do is look for the stock 2.0 firmware. Also look on YouTube for a unroot video. I have unrooted and re-rooted this phone so it can be done.
Sent from my Rooted Droid Incredible

I'm S-OOF right know. So I should go back to S-ON and try to find 2.0 rom. Where can I find the right programs to this before 2 days.

I'll help you out.
It does NOT matter if you send the phone back with 2.1 or 2.2, they don't care.
They care about two things you need to worry about.
turning it back to S-ON
and having the stock recovery.
to achieve this. You MUST be rooted to do S-OFF or S-ON, so first off get rooted if your not. Then visit unrevoked
the unrevoked3 is for root, unrevoked forever is S-ON, S-OFF.
once you are rooted, follow the instructions to turn it back to S-ON. **(the same exact way you turned it to S-OFF, but using the new S-ON file.)**
Once this is completed now you will have S-ON, but you are still rooted, and have the ClockworkMod recovery. You need to un-root by downgrading using the 2.1 OR 2.2 RUU. your pick and like mentioned above. don't matteh. This will get you to have the stock recovery, and S-ON. Go in that order. Hope you get it. Peace.

If your S-OFF then you are screwed. There is no way to turn it back on. You are SOL man. You can always restore it to factory but the S-OFF will ALWAYS remain
Sent from my Rooted Droid Incredible

Also your phone has all the programs you need. You just news to put them all in the root of your SD card and reboot into hboot
Sent from my Rooted Droid Incredible

jrdnthms said:
If your S-OFF then you are screwed. There is no way to turn it back on. You are SOL man. You can always restore it to factory but the S-OFF will ALWAYS remain
Sent from my Rooted Droid Incredible
Click to expand...
Click to collapse
Uhm you can turn back to S-ON
Sent from my ADR6300 using XDA App

Unless there has been a break though in getting HTC's and Verizon's super secret security code then I doubt it. The reason its called unrevoked forever is because there is no way to turn it back on. Check other posts in the xda to prove my point. If you return a S-off phone you will void the return and have to pay full price for the new one.
Sent from my unrEvoked forever Droid Incredible

jrdnthms said:
Unless there has been a break though in getting HTC's and Verizon's super secret security code then I doubt it. The reason its called unrevoked forever is because there is no way to turn it back on. Check other posts in the xda to prove my point. If you return a S-off phone you will void the return and have to pay full price for the new one.
Sent from my unrEvoked forever Droid Incredible
Click to expand...
Click to collapse
FYI unrevoked forever 1.1 was released last week allowing us to return to s-on.
Also, the reason its called forever is because it forever allows our phones to truly be ours, unlocked and how it should be.
Sent from my Incredible using XDA App

Assuming that to be true why would unrEVoked be offering a package called unrevoked-forever-son?
They SPECIFICALLY provide it in case you need to go BACK TO S-ON....
Frequently Asked Questions
Q: How can this be removed or undone if I need to take my phone in for service?
A: Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update
h t t p : / / unrevoked . com / rootwiki / doku.php / public / forever
I still cannot post H T T P links.

jrdnthms said:
Unless there has been a break though in getting HTC's and Verizon's super secret security code then I doubt it. The reason its called unrevoked forever is because there is no way to turn it back on. Check other posts in the xda to prove my point. If you return a S-off phone you will void the return and have to pay full price for the new one.
Sent from my unrEvoked forever Droid Incredible
Click to expand...
Click to collapse
Hahaha. Should have stopped while you were ahead, or at least have read my post that RIGHT about you before you started talking about something you have no idea about.
www.unrevoked.com read it.

jrdnthms said:
Unless there has been a break though in getting HTC's and Verizon's super secret security code then I doubt it. The reason its called unrevoked forever is because there is no way to turn it back on. Check other posts in the xda to prove my point. If you return a S-off phone you will void the return and have to pay full price for the new one.
Sent from my unrEvoked forever Droid Incredible
Click to expand...
Click to collapse
Seems like someone has been out of the loop.

Hey guys just got back from work a little while ago, and try all things you guys said but nothing works. Right know I'm sitting on a phone that sits with the new updated rooted because it took out of rooted, unrevoked won't let me root my phone. I get a error that says failed to load image. Please help.

daftlush said:
Seems like someone has been out of the loop.
Click to expand...
Click to collapse
I need help please. read last post.

@draft ok my mistake, last time i read the forever page it said they wouldn't make a S-ON but they did. My bad.
@Milton please go to this link and try it
http://forum.xda-developers.com/showthread.php?t=695825
follow the steps and it should unroot/restore. Hopefully you do this correctly

Milton1964 said:
I need help please. read last post.
Click to expand...
Click to collapse
Download S-ON file from unrEVOked's website and run that so that you get S-ON back onto the phone.
Then download either the 2.1 or 2.2 RUU (find them in the Android Development Section) and run that and it will wipe the phone and bring it back to factory state.
If it says your phone is not found when using the RUU, try downloading the HTC Sync software for the Incredible and installing that first. You need the drivers for "MY HTC" on the computer for the RUU to recognize it and HTC Sync will install that for you. I had that issue, but remedied it with the HTC Sync software install first.

jrdnthms said:
@draft ok my mistake, last time i read the forever page it said they wouldn't make a S-ON but they did. My bad.
@Milton please go to this link and try it
http://forum.xda-developers.com/showthread.php?t=695825
follow the steps and it should unroot/restore. Hopefully you do this correctly
Click to expand...
Click to collapse
Jr I'll give it a try. i will get with you later to let you know hoe it goes. thanks.

Back to 2.1 and S-ON thanks everyone
Milton1964 said:
Jr I'll give it a try. i will get with you later to let you know hoe it goes. thanks.
Click to expand...
Click to collapse
Jr it work like a charm. Back to 2.1 and S-ON!!!!!!!!!!! Ye ha know I could return this broken phone and get my new Incredible maybe it probably be refurbish.

Milton1964 said:
Jr it work like a charm. Back to 2.1 and S-ON!!!!!!!!!!! Ye ha know I could return this broken phone and get my new Incredible maybe it probably be refurbish.
Click to expand...
Click to collapse
Way to go back, good for you. It will 100% be refurbished unless of coarse you are within 30 days. refurbs are good though. and its amoled so. whateva

Well we see. the only thing i'm worry about is that it will come with 2.2, and won't be able to root again.

[Q] Unroot and S-ON

So, my main speaker blew and I'm going to take it in to have it warrantied. I have gotten to the point where I can get unrooted but I still have s-off or i can get to the point where i have s-on but rooted. How can I do both? I've searched so please don't flame.

I'm fairly certain that you need to grab one of the PB31IMG.zip files with the unrooted stock 2.1 floating around and install that. Then run the S-on tutorial. You should be good to go after that. For ****s and giggles once you do that you should be able to check for updates and the froyo update should be there.
Sent from my ADR6300 using XDA App

Put s-on then unroot by RUU back to stock.
Sent from my ADR6300 using XDA App

So, basically, turn s-on then find one of the "official" rb31img.zip files and flash that from the hboot right?

really dont even bother. just call customer service, since they are going to have to order it for you anyways. 18664065154, state you already took it to a technician and they reset and wiped handheld. They will send it to any address (not po box) you want. Keep it the way you have it.
ps and if they ask you why you didnt just get it replaced in store tell them you would have but you wanted to back up your stuff first.
Besides if you do a nandroid backup you can get it right where it was pre defect.

Should he be going back to 2.1 or run the leak for 2.2? Would it matter at this point? I was just thinking about this issue also.

customer service is just going to do a factory reboot and dump all memory anyways. just keep what he has on it. By the time it goes to replacement center hes probably going to upgrade to his next phone. Besides they have no ideas whos phone it is anyways.

I had to get a new phone. I left s-off and reverted back to non rooted 2.1, they don't look at stuff like that. At least they didn't for me.
Sent from my ADR6300 using XDA App

Curious how you blew the speaker...seems to be a pretty common problem these days but I've never seen anyone say how they did it...

Rooting with Visonary 14 killed me phone

I didnt think this was possible but I think I bricked my phone by using Visionary and permroot.
I clicked on the permroot, the icon went on, rebooted and got stuck at the HTC green screen.
After pulling the battery;
I tried doing a factory reset, nothing.
I tried a stock image of tmobile, nothing (at least I think I did this right)
ADB doesnt recognize the device in windows
I have only seen a red triangle and exclamation point after trying several posts suggestions.
I'm stuck on what to do, and have a replacement coming, but not soon enough.
Can I do anything with this? Like get the original Tmobile image back on? If so, how? I'm not the brightest bulb when it comes to this, as the g1 was so much easier. A bit of instructions would be great.
Thank you!

People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.

You didn't read the post which said you should not try to install the stock rom?
fastludeh22 said:
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App

@ddgarcia05 - that should be ok if he wasn't at S-OFF with the eng hboot though, which I don't believe that Visionary applies.

ibemad1 said:
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I checked and it said S-On and this was in recovery

ddgarcia05 said:
You didn't read the post which said you should not try to install the stock rom?
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
ADB doesnt recognize the device in windows and this was also in recovery

Anyone? Bueller?

cwis said:
ADB doesnt recognize the device in windows and this was also in recovery
Click to expand...
Click to collapse
Check out the adb guide at http://forum.xda-developers.com/showthread.php?t=865685
If you install the HTC Sync software, as mentioned in that guide, that should give you the drivers that you need.

This looks bad. Being that you're new. this can be very bad.
You have three choices:
1: study each thread about Bricking G2.
2:find a more experienced person to help you unbrick your phone.
3:find a very strong magnet and place it on your phone leave it there for an hour and bring it back.

Confirm that I bricked my phone please?

... before i shell out for another phone because I'm an idiot.
Anyway, I'd been doing some reading and had a thin history of rooting with my G1 which went rather well.(in that I never bricked it)
I did the same with my phone now, the G2. I got it when it first came out, got comfortable with it and finally decided to root it. I guess I didn't do enough research because I used Visionary to root and I believe I am now bricked. I have been up and down the forums for a solution or even a confirmation that I'm bricked for the last 4 hours. I kid you not. I even went into different phone sections in case I found something that could help but zilch.
So yell at me for not doing enough research and reading before i started rooting, but don't yell about this same question being asked over and over again.
Anyways, I can only get to the first white "HTC" screen and freezes.
I can get to HBOOT and that says:
Vision PVT SHIP S-ON
H-Boot-0.02.0000
Microp-0425
Radio-26.03.02.26_M
cMMC-boot
HBOOT
If I try to go to recovery it goes to that little black phone with the red traingle.
If I try to go to factory reset it goes to a green circle with a load bar that just looks like it's working but then it goes back to the white HTC screen and stays.
I have SDK and even though my computer recognizes that an Android 1.0 device is attached, when I "adb devices", nothing is listed.
So what's my diagnoses pros?
Thanks for any help or any response at all in advance.
Dea.

Its not looking good my friend, what exactly have you done to your phone so far?
If it is stuck in a boot loop and you have S-on the only possible thing you can to do fix it is flash the stock PC10IMG, but this will only work if you had the pre-OTA rom on your phone 1.19 and I really doubt that you did. If you had the wifi calling app you had the OTA 1.22 rom not the 1.19 rom. Trying to flash the stock PC10IMG onto your phone if it had the OTA rom 1.22 will cause it to do exactly what is happening now.

There's a file called "pc10img.zip" (the default firmware) that can be placed in the root of your SD, and should automatically be detected and offer to start flashing. I think this is how I recovered my phone which was in a similar state. Someone here could probably link you to the proper file (I'm sure there's different versions for DZ and G2). Good luck...I think you can probably save it.
I'm pretty sure mine was doing the same thing yours is, and I'm happily rockin' CM7 now, and loving it more than ever.

@joemm, Well I had 1.22 on there since I remember having wifi calling. I know you advised me not to but I might look into the PC10img.zip just because it can't get much worse than this honestly.
@hexapus, thanks for the advise. I'll have to look for my sdcard adapter first though. can't seem to find it at the mo'.
And when it does its sd card check on HBOOT, by the way, it says that all the files it wants to load, it says "No image!"

dealunae said:
And when it does its sd card check on HBOOT, by the way, it says that all the files it wants to load, it says "No image!"
Click to expand...
Click to collapse
Thats because its looking for the file named PC10IMG.zip, this is the only file name it will load and it must be on the root of your sdcard.
Check your PM i will message you right now.

This is a link to a page containing instructions for a manual update to 1.22 and a link to the update.zip. Maybe this will work if all else fails by applying the OTA update again.
http://www.talkandroid.com/20232-tutorial-manually-update-t-mobile-g2-remove-google-goggles/

You might be able to hex edit the pc10img.zip so it thinks its version 1.22.
Sent from my T-Mobile G2 running Cyanogenmod.

I also had this same issue, in that I tried visionary and had the same issue. I took mine to the tmobile store and let try to fix it, which they couldn't, and when they asked me what happened I said I was uninstalling an app that was a live screen because it was acting werid. Because I was still under warrenty they help me get a new one sent to me.
Worked out for me, now I read and read and read more. I am rooted via rage and gfree but still run stock.
Good luck
Sent from my T-Mobile G2 using XDA App

Well, everyone, after further button pushing, it looks like I can get into stock recovery. Should I do a wipe and flash a manual update of 1.22? The only reason I ask at this point is that if I try to do this, fail and then try to get it replaced, they might see that I tried to root and not replace it. (I have insurance as well btw.)

dealunae said:
Well, everyone, after further button pushing, it looks like I can get into stock recovery. Should I do a wipe and flash a manual update of 1.22? The only reason I ask at this point is that if I try to do this, fail and then try to get it replaced, they might see that I tried to root and not replace it. (I have insurance as well btw.)
Click to expand...
Click to collapse
The link I gave to you above has some great instructions on applying the manual update again. In my opinion its your best option at this point. BTW I have insurance too. I'm always worried that I might lose my phone!

It won't let you apply the 1.22 update zip because it is not a full rom, people have tried before and it doesn't work, but I guess like you said what have you got to lose.
Sent from my HTC Vision using XDA App

joemm said:
It won't let you apply the 1.22 update zip because it is not a full rom, people have tried before and it doesn't work, but I guess like you said what have you got to lose.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
joe, check out the second part of that link I provided above. The part about those with the google goggles fix. Do you think that would be a good second choice? I don't know if the OP knows how to do a fastboot flash, but it seems like it is more comprehensive. Do you think that it would reverse the effects of the Visionary perm root attempt?

EdKeys said:
joe, check out the second part of that link I provided above. The part about those with the google goggles fix. Do you think that would be a good second choice? I don't know if the OP knows how to do a fastboot flash, but it seems like it is more comprehensive. Do you think that it would reverse the effects of the Visionary perm root attempt?
Click to expand...
Click to collapse
At this point for him I don't see how its gonna hurt to try, but in my experiences in this forum I have not seen anyone able to flash the update 1.22 .zip after being stuck in a S-On Bootloop. Its either gonna work or it wont let him flash it at all, so I really cant see how it could hurt to try. As far as the 1.19 rom it wont let him flash it because it will give a error that the main version is older.

EdKeys said:
The link I gave to you above has some great instructions on applying the manual update again. In my opinion its your best option at this point. BTW I have insurance too. I'm always worried that I might lose my phone!
Click to expand...
Click to collapse
yea. It's how I realized I could still get into recovery. Thanks for the link. I'm at work right now so I won't be able to work on it till later but Wish me luck!

dealunae said:
yea. It's how I realized I could still get into recovery. Thanks for the link. I'm at work right now so I won't be able to work on it till later but Wish me luck!
Click to expand...
Click to collapse
OK, good luck! I hope that it, or something else, eventually works for you. Keep us updated....

So ended up getting a new phone. An htc g2. (sigh) I still really want to to root but am not officially terrified. ha. Looks like a lot of research and reading is in my future.

dealunae said:
So ended up getting a new phone. An htc g2. (sigh) I still really want to to root but am not officially terrified. ha. Looks like a lot of research and reading is in my future.
Click to expand...
Click to collapse
Lol... no need aha. If you have the basic concept of rooting you should be fine. Of course u just follow each step for rooting. Wish u luck
Sent from my HTC Vision using Tapatalk

You didn't fix the old one? The pc10img fix almost certainly would have cleared it all up.
Sent from my HTC Vision using XDA App

How to enable S-on in bootloader

I ran unrevoked 3 and tried a few things and decided it was not for me, I ran the Sprint RUU and it all worked fine. But under the bootloader screen it still shows S-off. Can I renable it?

venom_762 said:
I ran unrevoked 3 and tried a few things and decided it was not for me, I ran the Sprint RUU and it all worked fine. But under the bootloader screen it still shows S-off. Can I renable it?
Click to expand...
Click to collapse
Sry to hear that. See if THIS helps.

oooh that sucks. you have to re-root (you can just use unrevoked 3 again), then put the unrevoked s-on tool (found in the FAQ section of this thread http://unrevoked.com/rootwiki/doku.php/public/forever ) on the root of your sdcard. boot into recovery, and flash it as you would a rom. then check bootloader to make sure it is s-on. if it is, run the ruu again.
just curious, why dont u like root?

I just tried to re-run Unrevoked 3 and it will not reconnect, the tool just says waiting for device.
And I don't like root because of too much power.

venom_762 said:
I just tried to re-run Unrevoked 3 and it will not reconnect, the tool just says waiting for device.
And I don't like root because of too much power.
Click to expand...
Click to collapse
usb debugging is probably not on. try that.
too much power? like too much battery consumption (wtf?) or too much power over the phone?

too much stuff for me to f-with.

venom_762 said:
too much stuff for me to f-with.
Click to expand...
Click to collapse
hahah ok then. so ya turn debugging on (settings, applications, development, usb debugging) and put the phone on charge only and run unrevoked.

ok I found it, I was trying to root from the hboot screen.

Can't I just wait for the OTA from sprint and that would just turn S-back on?

venom_762 said:
Can't I just wait for the OTA from sprint and that would just turn S-back on?
Click to expand...
Click to collapse
no, it wouldnt turn s-on, and you might not even be able to accept it. if you are having a hard time using unrevoked, seeing as your rom no longer has root permissions, i can lead you through manually flashing amon-ra recovery to your phone and you can flash ur s-on from there.

I just got it to root again using Unrevoked 3 and restored to right after my first root. I should be able to now install the S-on tool and install it from the recovery menu?

venom_762 said:
I just got it to root again using Unrevoked 3 and restored to right after my first root. I should be able to now install the S-on tool and install it from the recovery menu?
Click to expand...
Click to collapse
That is correct. Also, I'm pretty sure that since you were still S off, you could've just flashed a pc36img of a recovery from the bootloader, flashed the s on tool, and then ran RUU.
Edit : just saw that dk already suggested that. Sorry.
Sent from my PC36100 using XDA App

Update I figured it out and ran the S-on tool, booted into the bootloaded and verified it was back on. I then ran the RUU and it should be fully stock and ready to install the OTA?

I just don't want to be that guy does not or has a failed update when the official OTA is out.

Anyone? I dying to know if I can install the next ota.

venom_762 said:
Anyone? I dying to know if I can install the next ota.
Click to expand...
Click to collapse
If you're back to stock, s on, and aren't on the latest OTA, then yes, you can take the OTA if you'd like to. That will bring you up to the latest software update.
Sent from my PC36100 using XDA App

Great I am relieved, I just wondered if when its pushed out if I have problems seeing it. Thank you guys for all of your help.

venom_762 said:
Great I am relieved, I just wondered if when its pushed out if I have problems seeing it. Thank you guys for all of your help.
Click to expand...
Click to collapse
sorry for leaving you in the dark for a while. that was one crazy day. but i'm at my comp now so i can help (not that there's anything left to do).
if i were you, i'd double check you are fully unrooted. boot into bootloader, and make sure you are s-on. then boot into recovery and make sure you have no custom recovery, just the stock htc one. also make sure your rom has no superuser app installed. if not, you are all good.

No prob man, I booted into the bootloader and S-On is back on and then tried to boot into recovery, a black screen with a red triangle came up so I assume there's no recovery installed. There is also no superuser Icon in the app draw.
The main reason I returned to stock is,is that this is my primary and only phone. I plan on getting the Nexus S when it come to sprint so I will see you guys again. That way if I bork the NS I got my trusty evo to activate.
Again thank you all for the help.

venom_762 said:
No prob man, I booted into the bootloader and S-On is back on and then tried to boot into recovery, a black screen with a red triangle came up so I assume there's no recovery installed. There is also no superuser Icon in the app draw.
The main reason I returned to stock is,is that this is my primary and only phone. I plan on getting the Nexus S when it come to sprint so I will see you guys again. That way if I bork the NS I got my trusty evo to activate.
Again thank you all for the help.
Click to expand...
Click to collapse
ok ya ur totally unrooted. enjoy the cage some prefer it there.
just saying, the evo is freaking hard to brick.