Develop Bugs

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

[Q] S-OFF!! im running stock gingerbread too!!

Ok so i know that gingerbread doesnt have root yet, but i installed the mod for the sense launcher it didnt work but my s-on isnt on its off... i dont know if this means anything to anybody ill upload a pictureee. Does this mean we might be closer to root?

i think i uploaded the picture ?

Yup. U r a lucky Guy. Put a copy of amon RA onto the root of ur SD card. Boot onto the bootloader and when it asks if u want to update say yes. U will then be able to flash whatever u like

If you were s-off before, you should still be s-off after. I have two s-off EVOs that I was going to sell, so I restored them to latest OTA (yea I'm a jerk!) but they stayed s-off (lucky for those when I do decide to sell).
I don't get the point of this, unless you had an S-ON phone and somehow got it S-OFF after the 2.16 hboot and 2.3.3 android upgrade.

YES! thats the thing! I unrooted, got the gingerbread update, after installation and what not it said S-ON. now it says s-off and i have no idea what i did, i been doing so much crap to my phone i dotn even remember what i did. I wanted to try the sense launcher from tommytomatoe and it froze my phone and couldnt do nothing. So i pressed power volume down and it now said s-off.

scoot16 said:
YES! thats the thing! I unrooted, got the gingerbread update, after installation and what not it said S-ON. now it says s-off and i have no idea what i did, i been doing so much crap to my phone i dotn even remember what i did. I wanted to try the sense launcher from tommytomatoe and it froze my phone and couldnt do nothing. So i pressed power volume down and it now said s-off.
Click to expand...
Click to collapse
If what you say is true, you might be able to help the rooting effort by pulling some info off your phone that could be valuable to the devs. I would explain the situation to them, and offer whatever info they need from your phone.
They'll probably call shenanigans on you-- I know I would. But maybe-- just maybe, your Evo carries the mutant X gene that we need to crack this puzzle.

Nice man! maybe just maybe your phone is the "root" of all hahahahaha

BigMatza said:
If what you say is true, you might be able to help the rooting effort by pulling some info off your phone that could be valuable to the devs. I would explain the situation to them, and offer whatever info they need from your phone.
Click to expand...
Click to collapse
This!
10char

scoot16 said:
Ok so i know that gingerbread doesnt have root yet, but i installed the mod for the sense launcher it didnt work but my s-on isnt on its off... i dont know if this means anything to anybody ill upload a pictureee. Does this mean we might be closer to root?
Click to expand...
Click to collapse
Did you have root before at all? Did you use Unrevoked3 to root before? If you did, how did you unroot?

Yes i used unrevoke 3 to root but i installed a stock froyo ruu unrooted because after i tried to unroot with unrevoked it didnt work. After i installed the froyo ruu it said S-ON, i then went on to install gingerbread, went back to check the hboot to see if everything was right and it still said S-ON, then i went thru every process to root my phone just to see if i could try soemthing but failed of course. I then wanted to try tommytomatoe sense launcher for unrooted and after my phone froze alot i went to clear data by pressing power and volume down. That is when i saw it was S-OFF. do you want to know anythingg else?

Please unroot again and post pics , you are still trying to unroot are you not. Go go.

Im cant unroot, im not even rooted, im running stock gingerbread ota 4.24.651.1

Did you flash the s-on tool when you unrooted?

complex88 said:
Did you flash the s-on tool when you unrooted?
Click to expand...
Click to collapse
Yes sir. I did all that was needed to unroot my phone.

Don't think running a ruu will turn s-on. Once you are s-off, you are s-off until you run the s-on tool. Correct me if I am wrong.
Swyped from my Supersonic

i am so tempted to try this....
can you provide the link to this tommytomato mod , at this point, i dont care if i brick my evo ill just go harass sprint and get a refurb or something if i do

LCL22 said:
i am so tempted to try this....
can you provide the link to this tommytomato mod , at this point, i dont care if i brick my evo ill just go harass sprint and get a refurb or something if i do
Click to expand...
Click to collapse
This didnt do nothing it was because of the mess up on my end did i go and find the s-on.

You need to write down everything you did and the order you did it. Also please provide the links that you used.

Also, was it the 4.22 or the 4.24 that you updated to?
*Edit* Nevermind I just saw your earlier post

scoot16 said:
Yes i used unrevoke 3 to root but i installed a stock froyo ruu unrooted because after i tried to unroot with unrevoked it didnt work. After i installed the froyo ruu it said S-ON, i then went on to install gingerbread, went back to check the hboot to see if everything was right and it still said S-ON, then i went thru every process to root my phone just to see if i could try soemthing but failed of course. I then wanted to try tommytomatoe sense launcher for unrooted and after my phone froze alot i went to clear data by pressing power and volume down. That is when i saw it was S-OFF. do you want to know anythingg else?
Click to expand...
Click to collapse
I say somehow some way when u attempted to re-root it went thru cuz that's the only logical way s-off could've been attained. Clearing ur data won't and u were s-on before u took the OTA update so it wasn't present before hand. Have you tried flashing another rom from recovery just to see if it works? You my friend maybe the "MVD" lol!!!

[Q] Stuck in limbo, need help!

I have posted several stuff about a situation I am having with my phone.... and I still cannot get it solved fully. I hope I can do it here.
I will try and summarize the situation with some key points.
First here is my current info....
Android Version 2.2.1
Baseband Version 2.15.00.03.04
Kernel Version [email protected]#2
Build Number 1.05.970.1 CL339957 release keys
Software number 1.05.970.1
PRI version 2.11_01c
PRL version 01001
Model Number PC36100
Supersonic DVT1 Ship S-ON
HBOOT-6.17.0001
MICROP-041f
TOUCH PANEL-ATMEL224_20aa
RADIO-2.15.00.03.04
Now I first rooted using revolutionary and got s-off properly.... I played with some roms and found it fun but not enough time to keep at it..... so I decided to s-on and go back to stock using un-revoked. That semi worked.... I got s-on.... but never lost the root. I still have recovery and everything still shows I have root except s-on.
Additionally, I tried to run the stock kddi ruu and i have gotten every error from 140, 170, 171 and even at one time 130...lol still no luck there. In doing all of that I figured out that the image version on my phone is 4.24.651.1 and I need to get to 1.05.970.1 (the stock kddi evo 4g) but cannot get it done.
Also I am HBOOT-6.17.0001 which is confusing in itself. xhausx helped me by giving me a nanadroid version of my kddi rom but that doesn't allow me to update anything and finding updates here is impossible unless I am running stock without root.
I am not sure if I need to flash a new misc partition, wipe my nand or something else and so not know how to do all of that..... can someone please please please help? I am willing to toss a small reward your way if we get me back to when I bought it.

I think you need to run the RUU for your phone; get it back to out of the box, stock, and just start over.

HipKat said:
I think you need to run the RUU for your phone; get it back to out of the box, stock, and just start over.
Click to expand...
Click to collapse
didnt you see this in my message????
Additionally, I tried to run the stock kddi ruu and i have gotten every error from 140, 170, 171 and even at one time 130...lol still no luck there.
if you have another RUU that I do not know about please let me know... because the one that I have from kddi is not working.
my current one is.... RUU_SuperSonic_K_KDDI_JP_1.05.970.1_Radio_2.15.00.03.04_NV_2.11_release_176711_signed.exe

You have a Japanese Evo, right?
Since it's a different phone, most of the people here will not be able to help you. I could tell you what to do if you had a American Evo, but it would probably either error out or further your problem.
Is there a forum for your specific version? Do things generally work the same as our Evos... like can you use the same RUU that I would use?
Sent from my Evo + MIUI using Tapatalk!

I was thinking if this will work somthing I might do if everything fails? Maybe you could try rooting it again and unroot?
Sent from my PC36100 using XDA App

plainjane said:
You have a Japanese Evo, right?
Since it's a different phone, most of the people here will not be able to help you. I could tell you what to do if you had a American Evo, but it would probably either error out or further your problem.
Is there a forum for your specific version? Do things generally work the same as our Evos... like can you use the same RUU that I would use?
Sent from my Evo + MIUI using Tapatalk!
Click to expand...
Click to collapse
The fact that I have a Japanese evo doesn't mean that anyone will not be able to help me. This is actually the place where the developers made the first RUU for the Japanese evo to begin with. There are plenty of pro's here.... we just need to find the right solution for me. Additionally, most everything works the same.... I cannot use the same RUU as you because the cid will come up different and cause me more probs.

culua said:
I was thinking if this will work somthing I might do if everything fails? Maybe you could try rooting it again and unroot?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I have tried to run the root process again and it says in revolutionary that you already have s-off..... which in fact I do not.... and when I do the opposite process it just acts like its running the s-on and does nothing.

AgentTabasco said:
I have tried to run the root process again and it says in revolutionary that you already have s-off..... which in fact I do not.... and when I do the opposite process it just acts like its running the s-on and does nothing.
Click to expand...
Click to collapse
Sorry can't help you. I guess just flash stock Rom for now untill you found an answer for problem. Sometime it fix it self? Lol.
Sent from my PC36100 using XDA App

Fixed
I have fixed my phone since I last posted this thread... thanks to all those that helped me solve my issues.

[Q] Unrevoked not downloading

The other day my phone just decided it wanted to get stuck on the HTC loading screen without being able to get into recovery and flashing back to a previous point, I had to go back to square 1 and flash back to stock.
So this morning I'm going about re-rooting and re-flashing a rom etc. However I have tried to download unrevoked 3 and it says it can't find the page when i go to download, does anyone have a different download for it.
A second question, I debranded my phone will it still be debranded or re-branded? is there anyway to find out?

Which version has your hboot? Because if it's high enough, you should use revolutionary:
http://revolutionary.io
There you get rooting plus S-OFF in two very easy steps.
SwiftKeyed from dGB with Transparent XDA App

its 0.93.0001 any idea about the debranding issue?

Well unrevoked could do it, but go ahead and use revolutionary instead. You'll get root and s-off.
It's pretty much unrevoked and alpharev combined, and it has been updated to support the newest hboot versions.

mortenmhp said:
Well unrevoked could do it, but go ahead and use revolutionary instead. You'll get root and s-off.
Click to expand...
Click to collapse
Thats the issue, I can't actually download unrevoked but I'll go ahead and use revolutionary. Thanks for the help.

SxcKieranGrr said:
Thats the issue, I can't actually download unrevoked but I'll go ahead and use revolutionary. Thanks for the help.
Click to expand...
Click to collapse
I did get that part and that was why I supplied you with another tool to use instead. I simply wanted to inform you that i case unrevoked would come back up that hboot was supported.

mortenmhp said:
I did get that part and that was why I supplied you with another tool to use instead. I simply wanted to inform you that i case unrevoked would come back up that hboot was supported.
Click to expand...
Click to collapse
Ok thankyou. I've just noticed my phone is resetting itself alot with the stock rom. I always thought this was the rom I had running that it was unstable. I guess this means there's an issue with the phone. I think it's over heating, is this an issue i need to send off to HTC for?

Sounds like a motherboard issue to me
Swyped from my CM7.1 Desire using XDA Premium App

[Q] Need help getting rooted Incredible back to stock

Hello all, I'm in serious need of some help, I've been working at this for a couple of hours now and can't figure it out, so I turn to you, o mighty forum.
I have an HTC Incredible and I'm currently running MIUI and clockwork recovery mod. I've been having all kinds of problems lately, and I want to just delete everything on my phone and get it back to stock, the way it was when I turned it on for the first time out of the box. If anyone can help me get this done I will be forever grateful, because I'm at my wits end. I have no idea what to do, or where to start, so if anyone could provide me with a step-by-step instructions, I would be very happy.
Thank you

bobrea said:
Hello all, I'm in serious need of some help, I've been working at this for a couple of hours now and can't figure it out, so I turn to you, o mighty forum.
I have an HTC Incredible and I'm currently running MIUI and clockwork recovery mod. I've been having all kinds of problems lately, and I want to just delete everything on my phone and get it back to stock, the way it was when I turned it on for the first time out of the box. If anyone can help me get this done I will be forever grateful, because I'm at my wits end. I have no idea what to do, or where to start, so if anyone could provide me with a step-by-step instructions, I would be very happy.
Thank you
Click to expand...
Click to collapse
Id be glad to help you. First off though are you s-off, and once you go stock again do you plan on rerooting in the future?

cmlusco said:
Id be glad to help you. First off though are you s-off, and once you go stock again do you plan on rerooting in the future?
Click to expand...
Click to collapse
Thanks for the reply. Right now I am S-On. And no, I don't plan on rooting again.

bobrea said:
Thanks for the reply. Right now I am S-On. And no, I don't plan on rooting again.
Click to expand...
Click to collapse
Ok then all you need to do is flash an ruu thru hboot.
Go here (http://pvillecomp.com/?page_id=22)and download the Gingerbread PB31IMG.zip
From the home screen of the phone hit Menu - Settings - Applications, and make sure fastboot is NOT checked.
Then go here (http://pvillecomp.com/?page_id=79) to learn how to flash the ruu thru hboot.
If you have any issues i will be keeping an eye on the thread.

I think I tried this earlier but it didn't work due to something about a newer version already be installed. I'll keep you posted.

bobrea said:
I think I tried this earlier but it didn't work due to something about a newer version already be installed. I'll keep you posted.
Click to expand...
Click to collapse
What android version are you on now? If its 4.08.605.2 then you will need to do the ruu exe with a pc. Its the first one on the pvillecomp link where the PB31IMG is.

To be totally honest I'm not sure. I tried using an RUU earlier but it kept saying my phone wasnt plugged in and it couldn't run, even though the phone was plugged in.

bobrea said:
To be totally honest I'm not sure. I tried using an RUU earlier but it kept saying my phone wasnt plugged in and it couldn't run, even though the phone was plugged in.
Click to expand...
Click to collapse
To do the ruu exe you need to have htc sync installed on your pc, to get the right drivers. Im not positive but you may need to remove the adb drivers first.

Baseband version: 2.15.00.07.28
Kernel Version:
2.6.37.6-cyanogenmod+
Android Version: 2.3.7

bobrea said:
Baseband version: 2.15.00.07.28
Kernel Version:
2.6.37.6-cyanogenmod+
Android Version: 2.3.7
Click to expand...
Click to collapse
Thats the problem your on a custom rom thats ported, and a higher android version than the latest stock ruu for the inc, so the ruu thinks yout trying to downgrade. Since your still on the correct radio needed for unrevoked to achieve s-off, i would reroot and s-off the phone with unrevoked, then flash a stock ota based inc rom (perferably 4.06.605.3), then go s-on again with the s-on patch, then do the ruu and it shouldnt give the firmware too new error anymore, and should get you back to complete stock.

What does that mean/how do I do it? I'm totally clueless here.

What does that mean/how do I do it? I'm totally clueless here. I just downloaded unrevoked 3.

bobrea said:
What does that mean/how do I do it? I'm totally clueless here.
Click to expand...
Click to collapse
Go here (http://unrevoked.com/#inc) get the unrevoked program and run it to root your phone and get s-off again. Instructions are on that page for using it.
Then flash this rom thru clockworkmod recoveryrecovery (http://forum.xda-developers.com/showthread.php?t=1247253), and reboot.
Then flash the s-on tool thru recovery (http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip)
Then do the PB31IMG.zip ruu again, it should work this time, and you will be complete stock.

Not exactly sure what's going on here. I used unrevoked 3 and got the original OS back on there, but when unrevoked runs, it asks if I want to install that PB31IMG file. I chose to not update with that and just reboot into recovery (which if I'm correct should be clockwork,) so I could flash that ROM, but when I reboot the device, I get a black screen wiith a picture of the phone and an ! in a red triangle. The unrevoked program just says "waiting for reboot..."

bobrea said:
Not exactly sure what's going on here. I used unrevoked 3 and got the original OS back on there, but when unrevoked runs, it asks if I want to install that PB31IMG file. I chose to not update with that and just reboot into recovery (which if I'm correct should be clockwork,) so I could flash that ROM, but when I reboot the device, I get a black screen wiith a picture of the phone and an ! in a red triangle. The unrevoked program just says "waiting for reboot..."
Click to expand...
Click to collapse
Go aheda and let unrevoked do the PB31IMG, that is the cwm recovery. The red triangle is still the stock recovery. Are you s-off now?

Nope, I'm still S-on. Not really sure what happened, but I have the original OS on the phone and from what I can tell, it's working fine. But I'm still S-on

I'm going to call it a night. I'll check this thread tomorrow when I get back from work and class. Thanks so much for all of your help so far.

bobrea said:
Nope, I'm still S-on. Not really sure what happened, but I have the original OS on the phone and from what I can tell, it's working fine. But I'm still S-on
Click to expand...
Click to collapse
Welk then you are stock just like the day you got it. If you want you can do the gingerbread ruu now, and it should not give the firmware too new error, ir you can stick with froyo, and at some point it will pop up with the latest ota to install.

Thanks so much, again. This was driving me crazy.