Database Users

Vibrant Custom Q's

It seems like the custom ROMs out right now are for the international version, right?
There should be ROMs coming for US-specific (IE, Vibrant), correct? I just don't want to get something I cannot customize. What scares me is that Samsung will update it to 2.2 and not release 3.0 later on?

Coming from the Touch Pro 2 scene where there are lots of variations as well, there should be roms that are compatible with multiple handsets and even some geared towards specific phones. Additional add-ons might be required for button layouts or something but I'm not sure how it works since I am speaking with experience only in the Windows Mobile area.
Regarding the update, it's really hard to tell since we don't even have the 2.2 update yet. But hopefully, they'll continue to support the Galaxy S as it's Samsung's direct iPhone competitor.

We should be able to flash any firmware for the galaxy s including the modaco rom. The real question is will we be able to get a hacked recovery to stick like amon_ra or cynogen ? Ps my phone comes this week im freaking excited!!
Sent using tapatalk

blackerwater said:
We should be able to flash any firmware for the galaxy s including the modaco rom. The real question is will we be able to get a hacked recovery to stick like amon_ra or cynogen ? Ps my phone comes this week im freaking excited!!
Sent using tapatalk
Click to expand...
Click to collapse
I'm excited to and I'm exited to be apart of building the vibrant section hopefully can atleast beat out the captivate and fascinate page

Thursday morning I'm waking up early and picking this baby up. I hope we can gain root the same way as the international version.
Sent from my T-Mobile G1 using XDA App

same going to be at the store 9 am to pick it up then head straight to xda for a root and a cfw that would be a dream

Hopefully the source code that was released by Samsung for the Galaxy S is the same for the Vibrant, which I see no reason why it would change but it is Samsung. If it is, I will help to port CM6 over to the Vibrant. The source code from Samsung that I downloaded yesterday has from what I could see with my quick glance over the drivers (baseband, sound, screen, etc) that would be needed to bake up a custom ROM.

That would be so awesome. I really don't care about samsung supporting this phone, as long as they let devs do their thing. Meaning not to lock up anything ala droid x
Sent from my T-Mobile G1 using XDA App

East Coast Rules
9am est on Thur July 15th.. It will be mine

It doesn't matter if they don't officially update it to 3.0, when there is root, there is a way!

BigWorldJust said:
It doesn't matter if they don't officially update it to 3.0, when there is root, there is a way!
Click to expand...
Click to collapse
not nessecarily true lol, take a look at the Motorola Milestone for an example, they have had root for a long time now, but cant load a custom rom due to an encrypted bootloader.

That's why I'm saying that if samsung doesn't do it, let the community have what it needs to do it themselves, look at cyan. My g1 should've been obsolete a year ago, but on the contrary its as strong as it was when I first rooted it.
Sent from my T-Mobile G1 using XDA App

gothdroid said:
Hopefully the source code that was released by Samsung for the Galaxy S is the same for the Vibrant, which I see no reason why it would change but it is Samsung. If it is, I will help to port CM6 over to the Vibrant. The source code from Samsung that I downloaded yesterday has from what I could see with my quick glance over the drivers (baseband, sound, screen, etc) that would be needed to bake up a custom ROM.
Click to expand...
Click to collapse
If the drivers are there, 90% of the work is done. We'll have the latest roms (barring some unlikely extreme performance requirements).

robavila721 said:
That's why I'm saying that if samsung doesn't do it, let the community have what it needs to do it themselves, look at cyan. My g1 should've been obsolete a year ago, but on the contrary its as strong as it was when I first rooted it.
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
Haven't checked in a while but the Behold 2 was a pain in the ass to root. And Samsung said that they didn't want people hacking their phones. That was a few months ago, since I don't have the phone I haven't checked back. I'm getting this bad boy and hopefully there will be a lot of support for it.

It's really easy to root the vibrant
Sent from my SGH-T959 using XDA App

Can the bootloader be unlocked?
Sent from my Nexus One using XDA App

disturkis4u said:
It's really easy to root the vibrant
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Second that. Took me 1 minute. Maybe less, LOL. Running tests, everything seems to be working, SU permisions et al.
Not sure on boot, but it seems that Samsung didn't even try to make it hard.
I went back to winmo for a while, and while the HD2 community is great, have to say glad to be back on android.

speoples20 said:
Haven't checked in a while but the Behold 2 was a pain in the ass to root. And Samsung said that they didn't want people hacking their phones. That was a few months ago, since I don't have the phone I haven't checked back. I'm getting this bad boy and hopefully there will be a lot of support for it.
Click to expand...
Click to collapse
The behold 2 wasn't too bad to root me and kam187 had it rooted shortly after it launched. The custom roms part was the hard part lol.
Sent from my SGH-T959 using XDA App

The fact that modaco has a custom ROM out indicates that it's probably going to be fairly easy for us.

Fascinate Gingerbread leak, what does that mean for us?

So, the Fascinate recently had a Gingerbread leak drop..... Since that phone is our phone's brother, do you think we will get it too...... Eventually? What do you guys have to say?
Btw: I am still on Vacation for another few days... When I get back I am going to recruit some graphic artists or whatever on xda to see if they can photoshop a quick green wave, or some other color that you guys like... Because I suck at graphic designing... It shouldn't be hard for anyone interested, because they can just use the template from the original blue wave.... Hopefully xD
Btw2: did you guys see the continuum softkey topic on the front page a couple days ago? D
Sent from my SCH-I400 using XDA Premium App

i would think the continuum would follow the fascinate with gb...however given the rather poor sales of the device (by all accounts a commercial flop) verizon/samsung just might not feel like spending the r&d on it...but im hopeful for u guys they would

I find it unlikely we even get Froyo, yet alone GB. Furthermore, I find it unlikely any developer is going to work on porting GB for the Continuum with the Fascinate leak.
Verizon isn't going to pay Samsung to update this phone. With such low sales, it's more cost-efficient for Verizon to forget about us than it is to release updates. Business is business.
Obviously I could be wrong.
Sent from my SCH-I400 using XDA App

samuelhadams said:
I find it unlikely we even get Froyo, yet alone GB. Furthermore, I find it unlikely any developer is going to work on porting GB for the Continuum with the Fascinate leak.
Verizon isn't going to pay Samsung to update this phone. With such low sales, it's more cost-efficient for Verizon to forget about us than it is to release updates. Business is business.
Obviously I could be wrong.
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
it would be almost impossible to port the touchwiz leaks (froyo/gb) to eclair continuum...aosp is possible i guess...but idk
just hope for the best id think

samuelhadams said:
I find it unlikely we even get Froyo, yet alone GB. Furthermore, I find it unlikely any developer is going to work on porting GB for the Continuum with the Fascinate leak.
Verizon isn't going to pay Samsung to update this phone. With such low sales, it's more cost-efficient for Verizon to forget about us than it is to release updates. Business is business.
Obviously I could be wrong.
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
Pretty much this. It's not going to happen. I've given up on ever getting an update. As soon as my job picks up (FINALLY) I'm selling it and getting a charge or x2 or something.

No expert here..but willing to venture
Did the update, it worked with out a glitch.. was able to root using superoneclick from xda..worked if I did not allow it to install busybox, when I did for somereason my phone wouldnt charge? Which btw adding busybox never popped up before when using superoneclick to root other androids...so far so good.. so far the changes are minimal.....a few extra settings such as font...but nice to have all the same..oh netflix works from the link provided with the leaked instructions...could be a tad scary to flash using ogdin..but it works.

Wait you updated you fascinate with this or your continuum?
I was actually just going to ask something too. If the big problem with modding is the ticker and everything else with the fascinate is essentially the same...can't I just update with this and noir have the ticker work or will the absence of ticker support just kill the phone?

I have tried before to install fascinate odin files on our phone... Didn't work xP The graphic drivers are different, so you can't see anything xP
Sent from my SCH-I400 using XDA Premium App

I figured it would be a no... could we not just c/p the modules for the drivers and over write the ones for the fascinate? Sorry for asking a lotof questions I'm just horrid at programming so I can't exactly just go try it... Though I want to learn if theres any chance we could get this running from the fascinate build. Anyone know how hard that would be? Or is that even possible?

TraMaI said:
I figured it would be a no... could we not just c/p the modules for the drivers and over write the ones for the fascinate? Sorry for asking a lotof questions I'm just horrid at programming so I can't exactly just go try it... Though I want to learn if theres any chance we could get this running from the fascinate build. Anyone know how hard that would be? Or is that even possible?
Click to expand...
Click to collapse
They aren't compatible. The drivers we have are for kernel 2.6.29, and the Froyo kernel is 2.6.32.9 (the .9 doesn't really matter to much) and Gingerbread is 2.6.35.x Somewhere betwee 6.29 and 6.32, there was a huge change to the kernel source, and I'm guessing any drivers built for the Eclair kernel we have are not going to work well on Froyo. The Fascinate Froyo source works to build a kernel, but the initramfs sucks, and it isn't something that is easy to troubleshoot really, and I don't have time right now to do so.

Thanks ImNuts, really. I have until about my birthday, July 1st, until I start reteaching myself programming and building it myself. Least I can do is try lol.

TraMaI said:
Thanks ImNuts, really. I have until about my birthday, July 1st, until I start reteaching myself programming and building it myself. Least I can do is try lol.
Click to expand...
Click to collapse
If you can get the kernel working, you should at least be able to get most of the system to Froyo, based on the Fascinate releases. The ticker would be an absolute no-go IMO, but you should be able to get the soft-key button images on there.

At this point I don't even care about the ticker. It doesn't work for 90% of what I want to use it for anyways. I would rather just have a phone capable of Froyo use haha.

4.5.91 Upgrade - Is there a "no flash back" warning?

Since I am on KP's 4.5.91 I have not flashed the released OTA.
I see many people already bricking after installing the upgrade, then trying to flash back.
Do you get a warning either before downloading the OTA, or before installing the OTA that you cannot flash to a previous version afterwards?
If not, it's possible you could return your phone, blaming AT&T/Moto for not warning you about backwards flashing.
If there was a warning, sorry, but you will probably be SOL, and it's your own fault for trying to downgrade after installing the OTA.
A bricked device will display 0x1000 on the screen when trying to boot up.
If you see this, go here ---> http://forum.xda-developers.com/showthread.php?t=1160408

Of course not, why would Motorola put in a warning like that. Motorola never excepts you to flash back to an older firmware.
Sent from my MB860 using XDA App

CaelanT,
I updated to gingerbread on rooted atrix 4.1.83. I did not notice any warning as you are hoping. Though the phone's root privilege is no more, Motorola has enabled the sideloading and I am happy with that.
Sent from my MB860 using XDA App

Are you serious?
Why would AT&T or Motorola be to blame for you bricking your device?
There doesn't need to be a "no flash back" warning... If you're 'flashing back' you are most likely using software you're not technically supposed to have to flash firmware you're not technically supposed to have.
It's really tiring reading these forums where people blame everyone but themselves for their bricked device. (Even after the "THIS WILL BRICK YOUR DEVICE" warnings..)

Technically, people shouldn't be able to flash back... we're not supposed to have RSD software or SBFs to flash in the first place.

ebaychuck said:
Why would AT&T or Motorola be to blame for you bricking your device?
There doesn't need to be a "no flash back" warning... If you're 'flashing back' you are most likely using software you're not technically supposed to have to flash firmware you're not technically supposed to have.
It's really tiring reading these forums where people blame everyone but themselves for their bricked device. (Even after the "THIS WILL BRICK YOUR DEVICE" warnings..)
Click to expand...
Click to collapse
Because technically, if they do not warn you that you can ruin your device by flashing to an earlier version, you have a case to sue them if you so choose to go that route. It's their failure to secure the software, updates, and upgrades they have which allows people to flash something you say they should not have, but is freely available to download through software update. Please do not spout what you hear from other people and think this makes you knowledgeable in any way. There are many legal implications with Moto and AT&T not disclosing what their updates/upgrades will or will not do, especially when they say "you will have unlock ability", then switch that at release with no warning, or for any number of reasons.
I can see you have a large contribution to this community by the grand sum of 5 posts which you have.
Now, I am trying to help some of the people out here who were obviously stupid enough to blindly flash an update released to them without first consulting XDA, because of course when you buy the Atrix it tells you to consult XDA on any matters relating to the Atrix!
Go back to ebay where you belong chuck!
BTW..........yes, I am very serious!

So the boot loader on the OTA is still Locked?!!!

yeah you could try that argument. they could give you the run around that you flashed using stuff not from their site or from their customer service portal and there could be some line in the warranty that would cover their ass from that stuff. but hey, worth a shot.

I updated to ota 4.5.9.1 during the soak and there was a big warning on the website, but nothing that I remember seeing when I downloaded and installed the software. They know the risk obviously. Surprised they wouldn't cover their behind during the install.
Sent from my MB860 using XDA Premium App

sservati said:
So the boot loader on the OTA is still Locked?!!!
Click to expand...
Click to collapse
Yes it is.
Beamed from WinBorg 4G via XDA Premium

CaelanT said:
Because technically, if they do not warn you that you can ruin your device by flashing to an earlier version, you have a case to sue them if you so choose to go that route. It's their failure to secure the software, updates, and upgrades they have which allows people to flash something you say they should not have, but is freely available to download through software update. Please do not spout what you hear from other people and think this makes you knowledgeable in any way. There are many legal implications with Moto and AT&T not disclosing what their updates/upgrades will or will not do, especially when they say "you will have unlock ability", then switch that at release with no warning, or for any number of reasons.
I can see you have a large contribution to this community by the grand sum of 5 posts which you have.
Now, I am trying to help some of the people out here who were obviously stupid enough to blindly flash an update released to them without first consulting XDA, because of course when you buy the Atrix it tells you to consult XDA on any matters relating to the Atrix!
Go back to ebay where you belong chuck!
BTW..........yes, I am very serious!
Click to expand...
Click to collapse
As many people have said.. Motorola does not give you any offical path to unlock your bootloader and flash a previous version. People like XDA do.
I have no problem with putting a custom Rom on my phone. I've hacked every device since my first Windows CE pda. The problem I have is with people like you that want to Sue Motorola because they... What? Told you to unlock your bootloader and try to flash unsupported software? No, they didn't.
Oh, and by the way please show me where you got the Official Motorola Atrix Unlock from.

ebaychuck said:
As many people have said.. Motorola does not give you any offical path to unlock your bootloader and flash a previous version. People like XDA do.
I have no problem with putting a custom Rom on my phone. I've hacked every device since my first Windows CE pda. The problem I have is with people like you that want to Sue Motorola because they... What? Told you to unlock your bootloader and try to flash unsupported software? No, they didn't.
Oh, and by the way please show me where you got the Official Motorola Atrix Unlock from.
Click to expand...
Click to collapse
The unlocked Bootloader is one thing, the fact that some users are bricking their phones after using OTA's is another.
Granted the 0X1000 is coming more from XDA users who have flashed, but Motorola needs to embrace the Android community better.
I'm not a fanboy of any company by any means, currently I own both a SGS and an Atrix.
^ With that said, Motorola needs to be a little more like Samsung.
* Paying attention to forums like XDA would be a start. Giving phones for free to developers would be another. (Samsung had no problem doing this).
*Getting rid of the bootloader FOREVER would also be in their best interest.
* Finally not forcing MotoBlur accounts down people's throats would be a friendlier approach as well.
Android consumers have helped Motorola get back in the game.
It's time for Motorola to repay the favor and start treating Android like "Android", and not like an iPhone...

sservati said:
So the boot loader on the OTA is still Locked?!!!
Click to expand...
Click to collapse
From what I've been reading, yes...

ccrows said:
The unlocked Bootloader is one thing, the fact that some users are bricking their phones after using OTA's is another.
Granted the 0X1000 is coming more from XDA users who have flashed, but Motorola needs to embrace the Android community better.
I'm not a fanboy of any company by any means, currently I own both a SGS and an Atrix.
^ With that said, Motorola needs to be a little more like Samsung.
* Paying attention to forums like XDA would be a start. Giving phones for free to developers would be another. (Samsung had no problem doing this).
*Getting rid of the bootloader FOREVER would also be in their best interest.
* Finally not forcing MotoBlur accounts down people's throats would be a friendlier approach as well.
Android consumers have helped Motorola get back in the game.
It's time for Motorola to repay the favor and start treating Android like "Android", and not like an iPhone...
Click to expand...
Click to collapse
Yeah, it would be nice if they'd support their more advanced users like Samsung and HTC have been doing. It seems like they are about to make some kind of change with Motoblur so maybe they'll ease up on the requirement to use it.

ebaychuck said:
Yeah, it would be nice if they'd support their more advanced users like Samsung and HTC have been doing. It seems like they are about to make some kind of change with Motoblur so maybe they'll ease up on the requirement to use it.
Click to expand...
Click to collapse
I've seen the Motoblur "improvements", but you still need an account, which is BS. Plus its a waste of time to freeze things in TiBU.
Between the last OTA that bricked many phones and the current Motoblur BS, I hope we can get Vanilla Gingerbread on this device more than ever. This will definitely be my last Motoblur phone I ever purchase.
Don't get me wrong I like Motorola a lot, but I also like to have a drama free phone...

I have a question for everyone that upgraded to GB.
After reading about the bugs in GB (like the "battery jumping issue" for instance) -
If you "could" go back to Froyo's latest build, would you do it or are you happier with the current GB?...

Nah.
ccrows said:
I have a question for everyone that upgraded to GB.
After reading about the bugs in GB (like the "battery jumping issue" for instance) -
If you "could" go back to Froyo's latest build, would you do it or are you happier with the current GB?...
Click to expand...
Click to collapse
Even with the few problems i'm enjoying having GB.. I guess I just like something new to look at.
I only miss a few things.
- The Happenings page that used to be attached to contacts. It was nice to be able to see the last post a friend made when calling them.
- Access control in Wireless Tether. (I can't remember if it worked on the Atrix or just my previous phone)
- Working Wired Tether..
- Setting review time on the camera.

CaelanT said:
Since I am on KP's 4.5.91 I have not flashed the released OTA.
I see many people already bricking after installing the upgrade, then trying to flash back.
Do you get a warning either before downloading the OTA, or before installing the OTA that you cannot flash to a previous version afterwards?
If not, it's possible you could return your phone, blaming AT&T/Moto for not warning you about backwards flashing.
If there was a warning, sorry, but you will probably be SOL, and it's your own fault for trying to downgrade after installing the OTA.
A bricked device will display 0x1000 on the screen when trying to boot up.
If you see this, go here ---> http://forum.xda-developers.com/showthread.php?t=1160408
Click to expand...
Click to collapse
"Hi Motorola, I'm using non-public tools that have been leaked, and non-public SBF files that have been gotten in an unofficial capacity to downgrade my phone after the latest update. I'm not breaking my warranty, am I?"

Touchwiz update halted due to some user's tab bricking.

http://www.androidpolice.com/2011/0...rogress-and-ensure-its-a-positive-experience/
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

krips2003 said:
http://www.androidpolice.com/2011/0...rogress-and-ensure-its-a-positive-experience/
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
I still dont see where it mentions it was bricking devices?

xavierdylan said:
I still dont see where it mentions it was bricking devices?
Click to expand...
Click to collapse
This is what the Engadget says.
http://www.engadget.com/2011/08/16/samsung-halts-touchwiz-ux-updates-to-prevent-bricking-issues/
Sent from my GT-P7510 using XDA Premium App

Of course Samsung won't admit that their update is bricking devices. I do give them credit for identifying there is a problem and halting the update until the problems are resolved. As long as Samsung is making things right by the customer, such as replacing said bricked device, you can't ask for much more than that.

Lucky Armpit said:
Of course Samsung won't admit that their update is bricking devices. I do give them credit for identifying there is a problem and halting the update until the problems are resolved. As long as Samsung is making things right by the customer, such as replacing said bricked device, you can't ask for much more than that.
Click to expand...
Click to collapse
On the Android phone side, it happened almost to every major updates Samsung released in many regions (Europe, Canada and US). First, update released. Then, halted. After a while, re-released again.
So, it is not too much to ask Samsung not to do this on every updates. Where is the testing/QA?

I don't know if that's what bricked mine or not, but it's good to know.
I opened my shiny new Galaxy Tab 10.1 on Monday afternoon. One of the first things I did was install updates. After I tried to power cycle it, I could not get it to turn back on. It went back to Samsung yesterday for repair/replacement.

Mine was sort of bricked. After I installed the TW update (the day it was released) it was caught in a boot loop. Samsung support had me clear all user data via recovery boot - that didn't fix it so the only option they offered was for me to send it back. I ended up rooting it and installing the OTA image with TW I got from here.
Samsung could do a lot better here by offering the utility to flash a fresh OS onto the device. There's no reason for us to send in the Tablet because it's caught in a boot loop. It'd save Samsung a lot of money if they'd support end user device wipe and reloads of the OS via a PC.

foxbat121 said:
On the Android phone side, it happened almost to every major updates Samsung released in many regions (Europe, Canada and US). First, update released. Then, halted. After a while, re-released again.
So, it is not too much to ask Samsung not to do this on every updates. Where is the testing/QA?
Click to expand...
Click to collapse
Oh I agree completely.... I wish companies would test their updates more thoroughly before releasing for general consumption. I see that crap all the time at work. But sadly, we consumers have become beta testers... and have been for quite some time I'm afraid. What I'm saying is that at least Samsung is trying to make it right by the consumer by either fixing or replacing the device.

Hey HTC,..

You know you are the reason xda came to be. A massive community forged behind your products, and your old model of 'keeping things open'.
Xda has become a HUGE COMMUNITY.
you will become zero and lose your place in the US if dev HTC unlock continues to be the halfass joke that HTC made and that actually is more likely to screw HTC users. We need full unlock, then we can fix our own software, not rely on you.
I love HTC hardware, but I'm buying galaxy or something in about 10 days.
Please listen to our recovery builders and take into consideration the VALID points I KNOW they have brought to your attention. They know Android better than YOU, HTC.
Sent from my PC36100 using xda premium

I agree completely. It is sad to have one of the only manufacturers outside of Google phones that offer an "unlockable" product, yet see so many struggling almost more than without unlock!
Looking a device is understandable from both manufacturer and carrier points of view. When a grown adult, who spends their hard earned money on a device, wants to upgrade and develop their own software why lock them out? HTC will only benefit from the developer community as Android a a whole exists on the theory of open source. CID was found out explored and corrected all within this community and HTC got praise for it. Where is our returned gratitude?
Sent from my PC36100 using xda premium

Bump!
Plus I have written an article on the situation, including the full quote from @toascfh from the discussion in the One X forum!
http://goo.gl/3T4NK

Great job! Hopefully HTC will listen. I know they'll listen to $, but I don't know how much of a dent the custom community would really put in their pocket.
Also, I cleaned up my post. It was written last night with anger/frustration and liquor. Lol
Sent from my PC36100 using xda premium

Could you please clarify for me, and others who aren't completely sure, how this affects devs and users? For example:
1. Can I root?
2. Can I get superuser access and use SetCPU?
3. Can I flash a custom kernel?
4. Can I flash a custom ROM?
Those are some things I'm wondering. All I want development wise on my new toy is improved battery life, which I assume will come via kernel change or SetCPU. Does this seem possible?
Thanks in advance!
Sent from my PC36100 using XDA

PsiPhiDan said:
Could you please clarify for me, and others who aren't completely sure, how this affects devs and users? For example:
1. Can I root?
2. Can I get superuser access and use SetCPU?
3. Can I flash a custom kernel?
4. Can I flash a custom ROM?
Those are some things I'm wondering. All I want development wise on my new toy is improved battery life, which I assume will come via kernel change or SetCPU. Does this seem possible?
Thanks in advance!
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Do you currently have your EVO with s-off?
The new bootloaders are locking us out from flashing the boot partition from recovery. This means that if you want to flash a ROM you need to flash the boot.img from the ROM through fastboot first, then enter recovery and flash the ROM. Also, you are blocked from flashing from system, i.e. flashing from inside the ROM, like using ROM manager or something like that. As for the kernel I am not so sure... but maybe, unless it is in the boot partition, which I actually think it is...
So, you will use htcdev to "unlock" your phone, then you can use:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
This will get your custom recovery, however your options from there are limited as stated above.
Then, to flash a ROM, you need to issue:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Using the boot.img from the ROM, then enter recovery to flash the rest of the ROM... As far as I understand. Then you will be able to use recovery to flash su binaries gaining superuser access, if necessary.
So, really you are going to be tied to your computer, issuing a lot of fastboot commands just to update ROM's, this severely slows down, and complicates the process, however, it will still be possible.
This all stems from more of a frustration, that HTC is locking things down making hell for users to customize their own device. This is what some 3vo users and many Sensation users and almost all Rezound users are experiencing. With the One series there are many working on this but it is difficult and frustrating.
I do plan to get the EVO LTE, despite the turmoil, and am trying to quickly learn some dev work so I can be a contributing member to the community. Believe me there will be those that stick around, but to lose the likes of toastcfh and cyaniarb... that would be a major set back...
Viperboy has opted for the Galaxy Nexus, but may still come to the EVO LTE, which would be a big help as he has done some great work for locked HTC devices. Though, in the long run, we do need to let HTC know what we want and that we are valuable and indispensable as a consumer group.

Thanks a ton! That is very encouraging to hear that there are still ways to go about doing things, just not as easy to do them. Honestly, the only reason I am a flashaholic now is that there is nothing that satisfies all of my needs. I feel like the EVO 4G LTE will satisfy everything I am looking for, and I'll only need to do little tweaks instead of massive wholesale changes regularly.
Now that being said, I'm still not happy to hear it is making devs run elsewhere, because we need them to create stuff so we have an opportunity to tweak our phones, whether in terms of big changes or not. Is there a way we can draft an email together and everyone who cares on this site can send it to them? Kind of flood their email to send a message?

scottspa74 said:
Great job! Hopefully HTC will listen. I know they'll listen to $, but I don't know how much of a dent the custom community would really put in their pocket.
Also, I cleaned up my post. It was written last night with anger/frustration and liquor. Lol
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I went into there Facebook told them I'm the tech of the family and they ask me what's the next good phone told them to go with the iphone or Samsung since HTC is locking down yup I'm the one that convinced them to get evo's and evo3D in the first place. You see what they dont take into consideration is we tell people what's the next up in coming hot phone including me I could sway away 8 potential customers not one. Just my two cents
Sent from my powered Shooter E3D with Infection of AnthraX Jamz by wolf.

Someone from the One X thread, where toast laid out the rant I quoted, already submitted said rant to HTC Facebook page.
Another problem with S-on is you can't flash radios. And from what I've seen in the rezound forum, once you update your main version (or firmware), like 4.54 to 4.67 for the Evo, you can't go back. So I believe it you wanted d to test an ICS ROM, and it was buggy, you couldn't go back to GB (using Evo current situation for reference).
As for kernel, I'm not sure how that is affected. As for recovery, I've changed recovery on my Evo using terminal emulator, meaning from within system (android). That can't be done in the current state of development, hence the need for fastboot and to do everything from a computer. I'm not fond of that.
The best way to see the current state of affairs is to do some serious browsing in the one x and rezound forums to see what users are up against.
Glad to hear you're studying up imheroldman. I need to, too. Hell, idont even know how to use cmd prompt or fastboot or adb. Never had to with Evo. Lotta people gonna have to study up, it seems.
Unless HTC gets their **** together. **cough cough cold day in hell**
Sent from my PC36100 using xda premium

imheroldman said:
Bump!
Plus I have written an article on the situation, including the full quote from @toascfh from the discussion in the One X forum!
http://goo.gl/3T4NK
Click to expand...
Click to collapse
I tweeted it, not like any one follows me but ...

With HTC claiming boot and USB are locked out because of "security reasons" is their way of saying "screw you, we will only give you a worthless partial unlock and still void your warranty for using it" and the htcdev.com method flags the device so they know you used it so your warranty can't be "reinstated" by relocking your phone like when they exploit and turn s-off then returning s-on so they don't know reinstates your warranty as far as sprint or HTC are concerned. This is the reason HTC locks the bootloader and requires a tool to "unlock" it. Samsung doesn't lock the bootloader at all, they implemented what is called a custom binary flash counter which triggers a number increase when ever you flash a custom kernel that has been modified. And they put the recovery partition in the kernel so it triggers when you install a recovery. However there are ways to reset the flash counter so they can't tell you've modded your phone. I'm not a brand loyal person, I will go with whoever has the device I want. Which is why for now I'm using Samsung. The build quality while made of a plastic is solid, so solid in fact I spilled some water on my phone on accident and it didn't even seep under the battery cover, my evo was laying right next to it and it had water all inside the cover and enough to trigger the water marks. They have really improved their build quality since my intercept which left alot to be desired but it was also a very cheap budget smartphone to begin with. The epic touch and note are very well built pieces of technology they are solid, the joins are smooth where the pieces are attached or the battery cover meets the housing, and still extremely light weight. Even with my snap on hard shell on my et4g its so light I can't tell its in my pocket alot of times I always double check to make sure it didn't slip out.
Sent from my SPH-D710 using xda premium

Thank you guys for your participation, I have 115 views on the blog entry just today!
I want to believe in HTC, that they will listen and lighten the lock down. We just need to speak up. This is a good start and yes hitting their pages and voicing our opinions as consumers will get their attention!

imheroldman said:
Thank you guys for your participation, I have 115 views on the blog entry just today!
I want to believe in HTC, that they will listen and lighten the lock down. We just need to speak up. This is a good start and yes hitting their pages and voicing our opinions as consumers will get their attention!
Click to expand...
Click to collapse
The bad part is them claiming they did it for security reasons, it will be hard to get them to unlock something they are claiming they are doing for security. If we can get them to unlock it, its gonna take a lot of convincing. A better option would be to ask for detailed instructions on how to flash firmware to the device with their setup. Obviously they have to flash firmware via OTAs so if they would outline the ROA for the OTA firmware install we could use that to flash our customs
Sent from my SPH-D710 using xda premium

That is the second option that toastcfh laid out. Apparently that is what the G1 had, full documentation on how to flash firmware. This might be the ultimate option, seeing as they want things to be locked but give those who just want an unlock that ability and for those wanting to go further the opportunity and the tools to do so.

Hahahaha.
Just saw the same thing CM9 on One X
Just saw this in the Evo 3d forum. So yeah, that's encouraging. But, it doesn't have camera working, and I wouldn't be surprised if that remains the case, due to HTCs new image chip and closed code. Decisions decisions 
Granted, this doesn't negate the frustration with S-on.
Edit: see what I did there imheroldman ? Thanks buddy. :thumbup:
Evil, what is the tampered watermark you speak of?
Also, in the 3d thread where I saw CM9 link, I swear I saw they have S-off now! That's great.
Sent from my PC36100 using xda premium

I really like their new "tampered" watermark
Sent from my SPH-D710 using xda premium

....tampered watermark? Whuuuuu?
Sent from my PC36100 using xda premium

scottspa74 said:
....tampered watermark? Whuuuuu?
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Instead of unlocked it now says ****TAMPERED**** at the top of an unlocked bootloader
Sent from my SPH-D710 using xda premium

Has anybody ever tryed doing a petition that people can sign to HTC for a full unlock?
Sent from my PC36100 using XDA App

UberJams said:
Has anybody ever tryed doing a petition that people can sign to HTC for a full unlock?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I think this is a great idea as well. Let's speak up!