Related
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
Someone please please please help me out. I am trying to unroot my phone so I can take it back to the store to get my speaker replaced. I am on hboot .93 with S-ON.... I originally rooted with simpleroot. I never used unrevoked. I run the file in bootloader and it always comes back telling me "Main Version is older" "Update Fail!" I have deleted everything else from the card. Can someone please shed some light...
EDIT: Thanks to user Darth Duane this was figured out...
You need to flash the MTD-ENG.img from toasts NAND (PART 2) unlock instructions.
So go here....http://forum.xda-developers.com/showthread.php?t=701835
and complete step 2.
After thats done go run the PC36IMG.zip from here http://forum.xda-developers.com/showthread.php?t=780141
and your all set! Hope this helps someone else!
If ur showing s-on then ur not rooted
sent from a pineapple under the sea
No disrespect but this can't be true. I have flashed almost all the Roms on here including cm6. I am actually on the 9/29 nightly build right now.
Cy_n_ic said:
If ur showing s-on then ur not rooted
sent from a pineapple under the sea
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Well now im all kinds of confused, have u always shown s-on after root, i just havnt heard of anything like his happening..btw sorry im no help, were in need of a mind greater than our own :-(
sent from a pineapple under the sea
Lol... Yea mine has always shown s-on... thanks.
Cy_n_ic said:
Well now im all kinds of confused, have u always shown s-on after root, i just havnt heard of anything like his happening..btw sorry im no help, were in need of a mind greater than our own :-(
sent from a pineapple under the sea
Click to expand...
Click to collapse
Ruu Will usually unroot it... I think a PC36IMG will so unroot I'd you didn't do unrevoked forever, hope that helps
Sent from my PC36100 using XDA App
Thanks. I downloaded the PC36IMG from the 2 step unroot and that is what I tried when I got the main version is older error. Ahhhh this sucks...lol..
kixcastillo77 said:
Ruu Will usually unroot it... I think a PC36IMG will so unroot I'd you didn't do unrevoked forever, hope that helps
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I did unrevoked then unrooted using their s-off tool and a pc36img from before the ota 3.26 i think it was. Well after flashing img i forgot to delete or rename it before reboot and thats when i saw the same thing the op did when it flashed it again. Are u able to get a newer one or are u using the 3.29 img already?
I think my screen asked me if i wanted to flash anyways rather han a straight up fail and refusal to flash.
sent from a pineapple under the sea
jerrygon said:
Thanks. I downloaded the PC36IMG from the 2 step unroot and that is what I tried when I got the main version is older error. Ahhhh this sucks...lol..
Click to expand...
Click to collapse
Just run RUU then that's usually the way that will always work
Sent from my PC36100 using XDA App
I agree
sent from a pineapple under the sea
I tried that also... I am using this file... [ROM]-SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28.zip
When I try the RUU I always get a Error 140: Bootloader Version Error...
Any other ideas??
Idk maybe it wont work with your hboot version...im sorry im no help at this point
sent from a pineapple under the sea
I was afraid you were going to say this... ahhhh... anybody else???
Cy_n_ic said:
Idk maybe it wont work with your hboot version...im sorry im no help at this point
sent from a pineapple under the sea
Click to expand...
Click to collapse
Try the new ota 3.29.651.5 that shouldnt cause the error
sent from a pineapple under the sea
A solution was found. It was added to the OP!
I've been trying to root my incredible for some time now. I first tried back in February and got a back up cid missing error message, after searching the Internet for answers and coming up with nothing I decided to wait for unrevoked to get updated. So recently I decided since I haven't got 2.3 I would try again still getting same errors, I've tried 3 different computers. I at a lost as to what to do. Any suggestions?
Android version 2.2 baseband version 2.15.00.07.28 hboot. 92
Sent from my ADR6300 using XDA App
JT75 said:
I've been trying to root my incredible for some time now. I first tried back in February and got a back up cid missing error message, after searching the Internet for answers and coming up with nothing I decided to wait for unrevoked to get updated. So recently I decided since I haven't got 2.3 I would try again still getting same errors, I've tried 3 different computers. I at a lost as to what to do. Any suggestions?
Android version 2.2 baseband version 2.15.00.07.28 hboot. 92
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I would try flashing the stock Verizon 2.2 Froyo RUU from your computer and then try to root again. Make sure you have the USB debugging checked in menu/settings/applications/development before you try to root. That's what I would start with.
Also what OS are you using to do this?
etek said:
I would try flashing the stock Verizon 2.2 Froyo RUU from your computer and then try to root again. Make sure you have the USB debugging checked in menu/settings/applications/development before you try to root. That's what I would start with.
Click to expand...
Click to collapse
I figured I would need a ruu but thought I'd have to downgrade to 2.1 and try an older unrevoked
Sent from my ADR6300 using XDA App
PonsAsinorem said:
Also what OS are you using to do this?
Click to expand...
Click to collapse
I've tried on windows 7 windows xp and a 10.1 mac
Sent from my ADR6300 using XDA App
PonsAsinorem said:
Also what OS are you using to do this?
Click to expand...
Click to collapse
I've tried on windows 7 windows xp and a 10.1 mac multiple times on each machine always the same error
Sent from my ADR6300 using XDA App
Boot into hboot and see if it already says s-off by chance? I did some searching and it seems a lot of people who get this error end up noticing later that they did achieve s-off just not a custom recovery or root.
EDIT: You can also check this out.
http://home.kennynet.co.uk/~kenny/bcid-fix.txt
cmlusco said:
Boot into hboot and see if it already says s-off by chance? I did some searching and it seems a lot of people who get this error end up noticing later that they did achieve s-off just not a custom recovery or root.
Click to expand...
Click to collapse
Just double checked, but no dice still s-on
Sent from my ADR6300 using XDA App
Still trying to find an official ruu that I can flash
Sent from my ADR6300 using XDA App
JT75 said:
Still trying to find an official ruu that I can flash
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
http://dougpiston.com/?page_id=108
cmlusco said:
http://dougpiston.com/?page_id=108
Click to expand...
Click to collapse
Thanks I'll did find that but when I scrolled down the page he listed a gingerbread ruu with the same md5 and I want Froyo
Sent from my ADR6300 using XDA App
JT75 said:
Thanks I'll did find that but when I scrolled down the page he listed a gingerbread ruu with the same md5 and I want Froyo
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Didnt notice he must have changed it recently due to the ota, it use to be froyo 2.2
How about this has 3 different download links for 2.2
http://androidforums.com/htc-droid-...mplest-instructions-ever-windows-xp-only.html
EDIT: Or this one.
http://shipped-roms.com/index.php?category=android&model=Incredible
Thanks for searching I'm gonna try the second one after my sons hockey game
Sent from my ADR6300 using XDA App
so I tried the ruu from shipped roms and got a 171 error which I expected because I'm on windows 7. Now that is fixed and I'm getting a error 140 saying I have the wrong ruu
Well I found the correct ruu from Doug piston but when I run it I get error 155 unknown error, I can't win
Sent from my ADR6300 using XDA App
cmlusco said:
Boot into hboot and see if it already says s-off by chance? I did some searching and it seems a lot of people who get this error end up noticing later that they did achieve s-off just not a custom recovery or root.
EDIT: You can also check this out.
http://home.kennynet.co.uk/~kenny/bcid-fix.txt
Click to expand...
Click to collapse
I did see this link back in February and it said it was for advanced users, which I am not. I have rooted a couple nook colors and installed cm7 but never played with adb before. It may be time to learn
Sent from my ADR6300 using XDA App
Try finding a stock PB31IMG.zip pulled from an official ruu and flash that thru hboot. I'll try to find a link for ya.
EDIT: http://dinc.does-it.net/stock_froyo/PB31IMG.zip
cmlusco said:
Try finding a stock PB31IMG.zip pulled from an official ruu and flash that thru hboot. I'll try to find a link for ya.
EDIT: http://dinc.does-it.net/stock_froyo/PB31IMG.zip
Click to expand...
Click to collapse
This was my last step that I tried last night before bed. I downloaded the zip from Doug piston and renamed it PB31IMG, booting into hboot nothing happened. By that point my battery was dying so I gave up for the day. This morning I used astro to double check the zip. It was listed as PB31IMG only so I tried to rename it PB31IMG.zip. Astro said that file already exists so I left it as is. I tried hboot again and it says something so fast I can hardly read it. I tried to read it about 20 times but it happens so fast, I think I need to video it so I can pause it. But what I could make out it was looking for something other than PB31IMG.zip
Sent from my ADR6300 using XDA App
I had an issue kind of like this with my wife's Inc. I tried so many different things and nothing worked. I tried 2 laptops and 2 desktops, both XP and 7 and nada. One day I booted my PC into safe mode, which then allowed me to install the modded drivers from Unrevoked, ran Unrevoked and BAM the **** worked! Kind of a long shot but worth a try ....
Please forgive me, ive read the forum and found no information on how to root an 2.3 Evo with HBoot version 2.18. i did find rooting guides but only for the 2.15 or 2.16. even tried running revolutionary anyway and got "2.18 is not supported at this time". any info on a helpful thread or how to go about it would be greatly appreciated. Thanks in advance....Later
drlzanej said:
Please forgive me, ive read the forum and found no information on how to root an 2.3 Evo with HBoot version 2.18. i did find rooting guides but only for the 2.15 or 2.16. even tried running revolutionary anyway and got "2.18 is not supported at this time". any info on a helpful thread or how to go about it would be greatly appreciated. Thanks in advance....Later
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1473373 there you go
http://forum.xda-developers.com/showthread.php?t=1499922
Here's an easy to understand one.
I apreciate the info guys, Ill be bouncing over here from the Heroc forum soon nice to wee theres some folks here as cool as the people there. Think ill feel right at home. I bought this Evo from my boss jist to see if id like it, and i do . Ill be useing it to practice on till i get new ones for the wife and myself. Ill be seein ya and Thanks again....Later
Sent from my HERO200 using xda premium
The new HTC tool can root that.
Sent from my A500 using xda premium
You mean on htcdev? I just checked and didn't see our phones in the list.
Sent from my PC36100 using XDA App
cprielly said:
You mean on htcdev? I just checked and didn't see our phones in the list.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
you have to pick all other supported models
Ok so I went to htcdev, followed the instructions to the tee, when I open the command to get the token I get "waiting for device" and then nothing, just sits there and waits. Any suggestions???
drlzanej said:
Ok so I went to htcdev, followed the instructions to the tee, when I open the command to get the token I get "waiting for device" and then nothing, just sits there and waits. Any suggestions???
Click to expand...
Click to collapse
is usb debugging enabled ?Did you try reinstalling the drivers?
yes sir, to both questions
drlzanej said:
yes sir, to both questions
Click to expand...
Click to collapse
maybe try a reboot of your PC and phone
Thank you for your responses, I tried rebooting phone and pc, with no luck. Out of curiousity I opend my command prompt and adb isnt recognizing my device. Going to try uninstalling and reinstalling sdk and jre and go from there. Curious, what version of sdk are we useing, r16?
Sent from my PC36100 using xda premium
AWESOME, I now have root. Only other question, What is the advantage to taking it further and useing revolutionary or unrevoked???. Just curious.
BTW. Thank you for your assistance, it is greatly appreciated
drlzanej said:
AWESOME, I now have root. Only other question, What is the advantage to taking it further and useing revolutionary or unrevoked???. Just curious.
BTW. Thank you for your assistance, it is greatly appreciated
Click to expand...
Click to collapse
You gain full s-off. With s-on unlocked you can't write to the radio partition and others. So if a rom comes with a custom kernel you will have to flash the boot.img from fastboot then the rom I think
Sent from my swiper using XDA App
Well I guess it will be worth it to go the full rought then. I feel like kind of a dip****, lol problems last night turned out to be a bad USB cord, what a noob mistake. Anyways Thanks again for the assistance.
drlzanej said:
Well I guess it will be worth it to go the full rought then. I feel like kind of a dip****, lol problems last night turned out to be a bad USB cord, what a noob mistake. Anyways Thanks again for the assistance.
Click to expand...
Click to collapse
i recommend down grading to 2.3.3 and using revolutionary
ok so i decided to attempt to get s-off useing the method at the end of this post http://forum.xda-developers.com/show....php?t=1473373 . when i run the flash_image commands in adb it doesnt actually flash it just mocks the commands. I know the device is recognized by adb, i went back to stock rom rooted , even tried useing the RArecovery, so what could the issue be or is there an alternative method of acheiveing s-off ?,,,Thanks
evo4gnoob said:
i recommend down grading to 2.3.3 and using revolutionary
Click to expand...
Click to collapse
and how would I go about this??? Thanks
EDIT:F#@K it, problem solved, Thanks
evo4gnoob said:
You gain full s-off. With s-on unlocked you can't write to the radio partition and others. So if a rom comes with a custom kernel you will have to flash the boot.img from fastboot then the rom I think
Sent from my swiper using XDA App
Click to expand...
Click to collapse
You can flash custom kernels fine with just the unlocked bootloader. The boot partition is unlocked, along with the system and recovery partitions.
Can somebody help me locate a guide for gaining S-OFF after doing the HTC dev unlock? Seems a bit scattered. I have downloaded the RUU for gingerbread and know that I need to relock but I'm also reading that I need to remove CWM? Any help would be appreciated.
Kayak83 said:
Can somebody help me locate a guide for gaining S-OFF after doing the HTC dev unlock? Seems a bit scattered. I have downloaded the RUU for gingerbread and know that I need to relock but I'm also reading that I need to remove CWM? Any help would be appreciated.
Click to expand...
Click to collapse
I'm in the same boat, there's plenty of information out there but it seems scattered.
I read through the Comprehensive S-Off/Root Methods thread and I think it goes like this:
Flash the RUU that's posted in that thread.
Re-lock bootloader (fastboot oem lock).
At this point it's like you're back to stock, correct?
Downgrade hboot if needed using the scripts shown (or does the RUU do this?)
S-off with revolutionary and get clockworkmod flashed.
Flash superuser / a ROM.
My question is: what will be the state of my phone after I flash the RUU listed in that thread? Will I be back to stock recovery? Will I need to downgrade hboot?
roswell_nightlife said:
I'm in the same boat, there's plenty of information out there but it seems scattered.
I read through the Comprehensive S-Off/Root Methods thread and I think it goes like this:
Flash the RUU that's posted in that thread.
Re-lock bootloader (fastboot oem lock).
At this point it's like you're back to stock, correct?
Downgrade hboot if needed using the scripts shown (or does the RUU do this?)
S-off with revolutionary and get clockworkmod flashed.
Flash superuser / a ROM.
My question is: what will be the state of my phone after I flash the RUU listed in that thread? Will I be back to stock recovery? Will I need to downgrade hboot?
Click to expand...
Click to collapse
I think you have to flash the stock recovery first, before the RUU.
Flash the 2.3.3 ruu, make sure you have stock recovery, relock it then use revolutionary to get S-OFF.
Sent from my Incredible 2 using Tapatalk 2
prototype7 said:
Flash the 2.3.3 ruu, make sure you have stock recovery, then use revolutionary to get S-OFF.
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
Need to downgrade HBOOT before that, right?
Kayak83 said:
Need to downgrade HBOOT before that, right?
Click to expand...
Click to collapse
Just flashing the RUU should be fine, that's all the downgrade tool does.
prototype7 said:
Just flashing the RUU should be fine, that's all the downgrade tool does.
Click to expand...
Click to collapse
I didn't realize that flashing that RUU would leave me with hboot .97, that's pretty cool.
I'm now S-Off, thanks for the help!
roswell_nightlife said:
I didn't realize that flashing that RUU would leave me with hboot .97, that's pretty cool.
I'm now S-Off, thanks for the help!
Click to expand...
Click to collapse
Neither did I lol, just checked the code and saw that's all the downgrade tool really does.
Sent from my Incredible 2 using Tapatalk 2
I was just about to post this thread... glad i searched first.
Guys, how do I flash the RUU?
I've tried renaming it to PG32IMG.zip, but it throws an error stating "wrong zipped image" or something of that sort.
I've tried flashing it through flashboot:
C:\Android>fastboot flash recover recovery_signed.img
sending 'recover' (3746 KB)... OKAY [ 1.144s]
writing 'recover'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.613s
Click to expand...
Click to collapse
Both don't work for me, and I'm out of ideas here.
pco052 said:
Guys, how do I flash the RUU?
I've tried renaming it to PG32IMG.zip, but it throws an error stating "wrong zipped image" or something of that sort.
I've tried flashing it through flashboot:
Both don't work for me, and I'm out of ideas here.
Click to expand...
Click to collapse
What exactly did you do to get there? Are you unlocked? Need more info for us to help you.
Sent from my SCH-I535 using Tapatalk 2
I Am still looking for info on this subject if anyone is still following this thread.
pprice520 said:
I Am still looking for info on this subject if anyone is still following this thread.
Click to expand...
Click to collapse
On what subject? I did just notice the previous poster's issue, they missed the y in recovery... Not sure what you're asking for though.
Sent from my SCH-I535 using Tapatalk 2
prototype7 said:
On what subject? I did just notice the previous poster's issue, they missed the y in recovery... Not sure what you're asking for though.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
thanks for the fast response, but after staying up all night i figured out how to fix my own problem lol I needed help gettin the heck off htcdev unlock so i could run rev like usual to s-off and flash regular roms. another thing you may be able to help with tho. im looking for a "stableish" ICS or JB for my dinc2.
pprice520 said:
thanks for the fast response, but after staying up all night i figured out how to fix my own problem lol I needed help gettin the heck off htcdev unlock so i could run rev like usual to s-off and flash regular roms. another thing you may be able to help with tho. im looking for a "stableish" ICS or JB for my dinc2.
Click to expand...
Click to collapse
Evervolv is good, maybe PAC, idk about sense
Don't have the phone anymore, so can't really say.
Sent from my SCH-I535 using Tapatalk 2
prototype7 said:
Evervolv is good, maybe PAC, idk about sense
Don't have the phone anymore, so can't really say.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
ill look around thanks for trying to help tho
I flashed the tazzpatriot ICS sense ROM with the new 3.0 kernal. Everything runs smoothly & it will only get better when oc is added in.
Sent from my HTC Incredible 2 using xda app-developers app