Develop Bugs

OTA after S-OFF?

Hey guys,
I used the AlpharevX Windows beta to S-OFF my Inc 2, then rooted using CWM (still on stock rom). I can see the OTA, and can download it, but it won't install.
The progress bar gets about 1/3 the way full then comes up with the triangle with the !.
I've tried it two or three times, did factory reset, have no idea what to do. Do I have to S-ON for it to install? If so, how exactly do I do that?
Sent from my Droid Incredible 2 using XDA Premium App

parkwoodsuks said:
Hey guys,
I used the AlpharevX Windows beta to S-OFF my Inc 2, then rooted using CWM (still on stock rom). I can see the OTA, and can download it, but it won't install.
The progress bar gets about 1/3 the way full then comes up with the triangle with the !.
I've tried it two or three times, did factory reset, have no idea what to do. Do I have to S-ON for it to install? If so, how exactly do I do that?
Sent from my Droid Incredible 2 using XDA Premium App
Click to expand...
Click to collapse
First, you cannot install an OTA when you have a custom recovery such as CWM installed. You at least need to install the original recovery image for your particular ROM before you try again.
Since the OTA in now available and official, why don't you just wait a few hours and someone will have a fully rooted version of the ROM that you can flash using CWM and not worry about losing S-OFF?

Let me give you a fair warning though, I'm not positive how Alpha set up their root, as I used XTC. BUT I know if you install the OTA with replacing CWM with regular recovery, you MAY be turned back to S-ON WITHOUT an option to get root back, UNLESS using the XTC clip. Enjoy.

Okay, I was afraid of that. I'm used to not even being able to see OTA's at all with CWM (came from Droid X), so it kind of threw me off.
Do you have any idea if the OTA is really any different from the leaked Inc S GB rom that's floating around? If, for some reason, it takes forever to get the ota rooted and they're not that different I may just install the leaked one I have.
Not trying to be a pain, just curious.
Thanks,
Sent from my Droid Incredible 2 using XDA Premium App

parkwoodsuks said:
Okay, I was afraid of that. I'm used to not even being able to see OTA's at all with CWM (came from Droid X), so it kind of threw me off.
Do you have any idea if the OTA is really any different from the leaked Inc S GB rom that's floating around? If, for some reason, it takes forever to get the ota rooted and they're not that different I may just install the leaked one I have.
Not trying to be a pain, just curious.
Thanks,
Sent from my Droid Incredible 2 using XDA Premium App
Click to expand...
Click to collapse
Check the Dev section. It looks like there is already a rooted, debloated version available.

I just created a PG32IMG.zip containing. Android-info text file and CWM recovery img renamed to recovery.img and placed it on root of sdcard
Booted into hboot and flashed it ...
Then I replaced the recovery with the stock recovery from the froyo ruu and flashed the stock recovery back....
Then flashed right back to CWM..
Never used any commands via windows or linux
I am going to install the ota and try to go back to cwm recovery and see what I can do from there.
I'll keep you guys informed
Sent from my ADR6350 using XDA Premium App

This way we will know if the s-off is similar to.unrevoked for the incredible 1. I could do this all day long with theirs.
One way to find out right.
Sent from my ADR6350 using XDA Premium App

Mr1070 said:
I just created a PG32IMG.zip containing. Android-info text file and CWM recovery img renamed to recovery.img and placed it on root of sdcard
Booted into hboot and flashed it ...
Then I replaced the recovery with the stock recovery from the froyo ruu and flashed the stock recovery back....
Then flashed right back to CWM..
Never used any commands via windows or linux
I am going to install the ota and try to go back to cwm recovery and see what I can do from there.
I'll keep you guys informed
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
You will recieve the OTA update and get Gingerbread. YOU'VE BEEN WARNED BY MANY that you will NOT be able to -reroot. if you can that's because of the hboot alpha gave you. but if it changes ur hboot you need XTC clip to re-root. RMK already posted a ROOTED ROM of the current OTA. SAME THING, why chance root for OTA. THEY ARE THE EXACT SAME FILES. BUT WITH ROOT! just use his ROM. my 2 cents. do as you please

Link
Hey, Instead of Don't do this, do that, do this, don't update that, If you want the release and don't want to lose root, install from this link. This guy(rmk40) spent some time to get this out to us. Awesome work! You won't lose root, everything works.
http://forum.xda-developers.com/showthread.php?t=1161411
Be sure to "Thanks" him for this

delete 10char

tenchar
tenchar

andybones said:
tenchar
tenchar
Click to expand...
Click to collapse

Looking at the zip it appears theirs reflashes hboot, which will break s off as far as i know.
Sent from my ADR6350 using Tapatalk

I got RMK's rooted rom and it's awesome. Thanks for the help guys.
Sent from my Droid Incredible 2 using XDA Premium App

Freaking Clockworkmod: got me again.

Oh, CWM, how MUCH I can't stand thee:
Anyway, here's a long version:
I can't stand using CWM for recovery.
(I initially had an OG Evo, and it was nothing but a headache, so I always used AmonRa, successfully, and use that or TWRP on my ALL my other devices, where I can...
I'very made other posts about its issues, and have gotten into it with Koush online before about all the problems with it, and how he just let's so many versions out into the wild that aren't working for different phones...
With the ET4G, I kinda had to use it, and was able to flash a working version thru Odin.
Whatever, I was able to use it.
Lately, Koush releases a touchscreen version, there are stories about it all over the web: so I go into Rom Manager to check it out:
It tells me that it's not yet compatible with the ET4G, but that my version of CWM is outdated, so I should flash a newer CWM....
LIKE AN IDIOT, I agreed.
Now, just when I finally have a chance to flash CM9 on my ET4G, after waiting SOOOOO long?
I can't.
Because now, my recovery's totally borked.
I can't even get my phone to do anything but bootloop the CM7 animation, and download mode is the only thing I can get into.
Now, I'm gonna have to spend all this time today fixing what shouldn't be messed up in the first place instead of enjoying CM9 like I should be doing.
(BTW: Koush, if you're listening: this will be the last time for sure I ever fall for that again.)
Yeah, I'm mad, Bro.
Sent from my PG86100 using xda premium

I never use ROM manager but doesn't cwm have to be packaged with a kernel in order for it to work? ie. we can't just flash a recovery like we could in the evo 4G days. Methinks if you just use odin to flash a kernel+cwm package you'll be back up and running in no time.

_MetalHead_ said:
Methinks if you just use odin to flash a kernel+cwm package you'll be back up and running in no time.
Click to expand...
Click to collapse
Methinks you are a wise and gracious man with your help......

_MetalHead_ said:
I never use ROM manager but doesn't cwm have to be packaged with a kernel in order for it to work? ie. we can't just flash a recovery like we could in the evo 4G days. Methinks if you just use odin to flash a kernel+cwm package you'll be back up and running in no time.
Click to expand...
Click to collapse
Oh, yeah: I can fix it, but my wife has my laptop till like 7pm, and I really don't wanna mess with drivers, Odin, all, that stuff on my desktop. I keep all my Android stuff on one PC (laptop) and I like having ADB, drivers, all that stuff, in one place...Just kinda threw a rock into my chain, on today of all days...
Sent from my PG86100 using xda premium
Edit: And, yeah, I knew that used to be the case with CWM (needed kernel flash), but when a known high-level dev is telling me basically, that "this updated version will work for that very specific Android device that you have", and that "I can use his app to flash it", I guess I wanted to believe him...
Eff that guy: He needs to spend less time stacking his money, and more time having some accountability for what he releases to the public.
/End rant.

So, this has nothing to do with Clockworkmod, you are really pissed that samsung requires recovery and kernels on the same partition.
Koush can only do so much magic.

Bielinsk said:
So, this has nothing to do with Clockworkmod, you are really pissed that samsung requires recovery and kernels on the same partition.
Koush can only do so much magic.
Click to expand...
Click to collapse
?
How much magic does it take to remove the ET4G from Rom Manager's compatability list?
I'd bet not too much: In fact, I'd bet I could learn that trick in one short weekend.
Sent from my PG86100 using xda premium

If you're still rooted Mobil odin

Nandroid hardly ever works for me, it usually fails during the restore.

just uninstall rom manager its about worthless for our phone.

drksilenc said:
just uninstall rom manager its about worthless for our phone.
Click to expand...
Click to collapse
I know it sux but I have to agree the real problem and question is if you know your way around your phone then honestly why in the hell would you use Rom Manager, Not getting on you but I too hated CWM on OG Evo, I used Amon but the one thing we all learned early is do it yourself so you dont need Rom Manager...

I love the new clockwork mod touch recovery. I actually like it better than twrp2.0. Only thing I like about twrp is you can compress the backups. The new cwm touch was just released for the ns4g.
Sent from my Nexus S 4G using xda premium

I agree ROM manager is useless in the galaxy s4g forums its ROM Mangler.
Sent from my SPH-D710 using xda premium

playya said:
I know it sux but I have to agree the real problem and question is if you know your way around your phone then honestly why in the hell would you use Rom Manager, Not getting on you but I too hated CWM on OG Evo, I used Amon but the one thing we all learned early is do it yourself so you dont need Rom Manager...
Click to expand...
Click to collapse
I know, I know...
(And I'm back up with CM9 on my ET4G: used my desktop, couldn't wait all day), and believe me: there's probably no one who's more outspoken about their anti-cwm/rommanagerness than I am: I'm just mad at myself for believing that the new update would work..
Oh well, lesson (re)learned....
Sent from my SPH-D710 using xda premium

This is why i no longer use that pos rom manager. When i first started out with android that biatch messed up my og epic a few times. I learned my lesson after a few odins
Sent from my SPH-D710 using xda premium

eao1991 said:
This is why i no longer use that pos rom manager. When i first started out with android that biatch messed up my og epic a few times. I learned my lesson after a few odins
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I use it all the time to boot into recovery and that is it
Sent from my SPH-D710 using xda premium

Originally Posted by eao1991
This is why i no longer use that pos rom manager. When i first started out with android that biatch messed up my og epic a few times. I learned my lesson after a few odins
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I use it all the time to boot into recovery and that is it
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I use the extended power options for that...but obviously the rom needs to include it which most do now. I'm still kicking myself in the ass for ever buying rom manager but I guess it was the noob in me.
Sent from my SPH-D710 using xda premium

Same thing happened to me when I first rooted my phone. I rooted the stock rom then installed rom manager and installed the recovery that way. Then when I booted into recovery, the only option I had was to reboot.
Don't ever use Rom Manager. Ever.

CBowley said:
Same thing happened to me when I first rooted my phone. I rooted the stock rom then installed rom manager and installed the recovery that way. Then when I booted into recovery, the only option I had was to reboot.
Don't ever use Rom Manager. Ever.
Click to expand...
Click to collapse
For our phone.

There's definitely nothing wrong with CWM. Blame rom manager if you must place the blame anywhere besides yourself.

I bought rom manager to support clockworkmod and have access to the latest clockworkmod versions. I think they have provided a wonderful tool. Anyway, I actually never used it except to check for roms and latest clockworkmod.
I've flashed the touch version of clockworkmod (downloaded the .img file from the clockrkmod web site) on my ns4g using adb and fastboot (thanks to Paul627 for the tutorial).
Sent from my Nexus S 4G using Tapatalk

[Q] PC36IMG ERROR AT HBOOT.I think i have soft bricked my phone. NEED HELP. PLEASE!!!

HI. I AM FAIRLY NEW TO THE ROM FLASHING SCENE. HAVE BEEN SUCCESSFUL FOR THE LAST FEW MONTHS AT FLASHING ROMS. THEN I THINK I STEPED OUT OF BOUND AND BEGAN TO TRY FLASHING NEW KERNELS. HAVE BEEN SEARCHING WEB ALL DAY ON WHAT COULD HAVE HAPPENED. FROM WHAT I HAVE READ I MAY HAVE FLASHED A KERNEL FROM ONE MOD TO ANOTHER. OR POSSSIBLY INTERRUPTED THE ZIP INSTALL OR FLASH. NOW WHEN I TRY TO FLASH BACK UP ROMS THEY BOOT LOOP OR JUST STAY ON BOOT SCREEN. SAYS NO PC36IMG at the hboot screen. please help.

Are you using the newest HBOOT from HTC? I heard that you can't flash kernels on it...
Maybe the .zip didn't download completely. What kernel did you try to flash, can you even access recovery?

HBOOT 6.16.1002. i was flashing a tiamat kernel. didnt like it and when i tried another one is when it happened. not sure if i did all the wipes. was late and was getting tired

by the way iwas running cynogen mod 7.1 rooted with revolutionary. when i flashed a few kernals some wouldnt work so i tried ra recoery and they installed. i then installed TWOP RECOVERY. TRIED TO INSTAL A MIK ROM AND THATS THE FIRST TIME I GOT THE BOOTLOOP AND IT WAS LIKE THAT EVERYSINCE

trevanti00 said:
by the way iwas running cynogen mod 7.1 rooted with revolutionary. when i flashed a few kernals some wouldnt work so i tried ra recoery and they installed. i then installed TWOP RECOVERY. TRIED TO INSTAL A MIK ROM AND THATS THE FIRST TIME I GOT THE BOOTLOOP AND IT WAS LIKE THAT EVERYSINCE
Click to expand...
Click to collapse
well tiamat will not work on any mik rom that i know of because (all?) mik roms are sense roms. if its a sense rom then you need a sense kernel. aosp rom needs aosp kernel. go into recovery and flash a sense kernel. that should fix your bootloop

Well im guessing that was the problem then. Well at least i know the source of the problem. Now can it be fixed. Can you give me a sense kernal to try out

trevanti00 said:
by the way iwas running cynogen mod 7.1 rooted with revolutionary. when i flashed a few kernals some wouldnt work so i tried ra recoery and they installed. i then installed TWOP RECOVERY. TRIED TO INSTAL A MIK ROM AND THATS THE FIRST TIME I GOT THE BOOTLOOP AND IT WAS LIKE THAT EVERYSINCE
Click to expand...
Click to collapse
Twrp recovery more than. Likely killed your phone, if you had read the thread you would have known it is no longer supported for the evo for this very reason,as it has been known to permanently brick evos with no fix by screwing up the partitions
Sent from my PC36100 using xda premium

-EViL-KoNCEPTz- said:
Twrp recovery more than. Likely killed your phone, if you had read the thread you would have known it is no longer supported for the evo for this very reason,as it has been known to permanently brick evos with no fix by screwing up the partitions
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
1 survivor i know of and that is the great captain_throwback . Whats with all these bricks lately lol?

Damn it. So am i screwed or is their a solution

trevanti00 said:
Damn it. So am i screwed or is their a solution
Click to expand...
Click to collapse
did your s turn back on after the bootloop ?

What did he do to fix it. Do you have a thread on that

I am s off

No it is still off

trevanti00 said:
No it is still off
Click to expand...
Click to collapse
then TWRP most likely didnt cause it. His situation was different from what your experiencing so what he did will most likely will be different from what youll have to do. Also if TWRP caused it you would be back to s-on

Well could you give it a shot and trouble shoot with me. I been at it eveery since last night

trevanti00 said:
Well im guessing that was the problem then. Well at least i know the source of the problem. Now can it be fixed. Can you give me a sense kernal to try out
Click to expand...
Click to collapse
here is one...http://forum.xda-developers.com/showthread.php?t=1496488

Flash amon ra in hboot and get off of twrp b4 u end up screwed first and foremost then try wiping everything in amon ra except sdcard and battery stats and flash a new rom and see if it will boot up if you can't get recovery to load you may need to try running an ruu and starting from scratch
Sent from my PC36100 using xda premium

evo4gnoob said:
1 survivor i know of and that is the great captain_throwback . Whats with all these bricks lately lol?
Click to expand...
Click to collapse
Ppl not reading enough or rushing thru things is my guess *shrugs*
Sent from my PC36100 using xda premium

ok trying that now.

problem solved. thank you guys a million times. i knew i would run into a brick sooner or later. lesson learned. i have always read all the post before flashing but was tired and got lazy. will never happen again. again THANK YOU GUYS.

Touch recovery on Caulkin 4.0 ROM?

I recently flashed Caulkin's 4.0 Rom for the e4gt and was wondering if its possible to flash touch recovery with the Rom? I would normally play around to figure it out, but figured I'd ask first so I can maybe avoid a brick.
Thanks in advance!
Sent from my SPH-D710 using XDA

Stryke_the_Orc said:
I recently flashed Caulkin's 4.0 Rom for the e4gt and was wondering if its possible to flash touch recovery with the Rom? I would normally play around to figure it out, but figured I'd ask first so I can maybe avoid a brick.
Thanks in advance!
Click to expand...
Click to collapse
Did you mean Calk's 1.4?
You shouldn't be using touch recovery with anything for risk of bricking your phone.
And if you're using ANY version of ICS, you also risk bricking your phone if you try to use any form of recovery.

tdunham said:
Did you mean Calk's 1.4?
You shouldn't be using touch recovery with anything for risk of bricking your phone.
And if you're using ANY version of ICS, you also risk bricking your phone if you try to use any form of recovery.
Click to expand...
Click to collapse
I agree with the first part, stay away from CWM9 touch. Youre asking to get bricked. CWM5-7 recover rogue is fine to use between ICS roms. Always run Calkins format all. And never use cwm.recovery to do a nand back to GB. Flash SFHUBS stock EL29 first via Odin..along with calk's format all prior to.that then nandroid back to your previous set up.

tdunham said:
Did you mean Calk's 1.4?
You shouldn't be using touch recovery with anything for risk of bricking your phone.
And if you're using ANY version of ICS, you also risk bricking your phone if you try to use any form of recovery.
Click to expand...
Click to collapse
Someone tell me why the F this hasn't been "fixed" yet? My last phone was an OG Droid and we didn't have to deal with the amount of 'you must wipe with this recovery, flash with this recovery, use ODIN to do this...' crap when we went from Eclair to FroYo and nothing ever got bricked... this is just ridiculous.

dandragonrage said:
Someone tell me why the F this hasn't been "fixed" yet? My last phone was an OG Droid and we didn't have to deal with the amount of 'you must wipe with this recovery, flash with this recovery, use ODIN to do this...' crap when we went from Eclair to FroYo and nothing ever got bricked... this is just ridiculous.
Click to expand...
Click to collapse
cuz the ics source isnt out for our phones yet. And frankly im just happy the were able to port ics without the source in the first place

dandragonrage said:
Someone tell me why the F this hasn't been "fixed" yet? My last phone was an OG Droid and we didn't have to deal with the amount of 'you must wipe with this recovery, flash with this recovery, use ODIN to do this...' crap when we went from Eclair to FroYo and nothing ever got bricked... this is just ridiculous.
Click to expand...
Click to collapse
You my friend sounds like a man who wants to fix it.... Can't complain(if your are complaining) about stuff that you yourself can not help on or fix.. If you don't like the procedure its not like you are being forced to do it... My bad I know I know I will shut up now
Edit: sorry OP I should of at least chimed in on your question.... If you want to use Touch recovery it tells me you have not read much in these forums so I would suggest you take a lil time and read the brick threads and stickys... Quite helpful

Thanks guys, you just saved me a huge headache lol. I only asked because i hate to lose a paid app, but better that than brick my phone.
Thanks again!
Sent from my SPH-D710 using XDA

dandragonrage said:
Someone tell me why the F this hasn't been "fixed" yet? My last phone was an OG Droid and we didn't have to deal with the amount of 'you must wipe with this recovery, flash with this recovery, use ODIN to do this...' crap when we went from Eclair to FroYo and nothing ever got bricked... this is just ridiculous.
Click to expand...
Click to collapse
Build a solid ics kernel for us then. Or wait until we get the official release. There is no fix because nothing is broken. All ics roms for this phone are built on leaked kernels.
But I'm sure your post was just sarcasm and you knew that since it's been spoken about in just about every ics rom thread.
Sent from my SPH-D710 using Tapatalk 2

Boot loop after revolutionary

Hey guys,
I just got a Incredible 2 and started the root/s-off process.
First I had to downgrade it to 2.3.3 and then ran revolutionary. All worked fine and I even installed the CWM.
The problem is that now it gets stuck on a pretty weird boot loop.
Every time I install a new ROM (stock or not) it boots and everything works fine. But as soon as I turn it off, it gets stuck on this infernal boot loop and the only way for it to stop is flashing a new ROM and doing it all over again.
Anyone has any clue what this could be?
Thanks
Ariel

Are you doing a full wipe? Do you have the latest radio? That is needed with the new firmware 6.xxx
Sent from my Incredible 2 using xda app-developers app

Solved it...
I was doing a full wipe and I had the latest radio (1.09.01.0722). Aparently this was the problem.
I found an older radio (1.09.01.0322) and some guy saying that I needed it if I started having bootloops. And it works!
Thanks tho

Yntarius said:
Solved it...
I was doing a full wipe and I had the latest radio (1.09.01.0722). Aparently this was the problem.
I found an older radio (1.09.01.0322) and some guy saying that I needed it if I started having bootloops. And it works!
Thanks tho
Click to expand...
Click to collapse
LOL that's the newest one.

sjpritch25 said:
LOL that's the newest one.
Click to expand...
Click to collapse
Yeah, the naming is a little odd, I think it's supposed to be the month created then the year, but obviously .0622 and .0722 didn't follow that. .0312 is the latest (March 2012).

Dont use revolutionary
Try using another root method. Do it manually if you have too. I don't remember how i rooted my inc2 but it wasnt with revolutionary. Ive had it forever so the root methods may have changed. Just try a different method and see what happens.