Develop Bugs

Has froyo been rooted yet?

Ok... I'm one of the idiots that updated to froyo thinking that I would be happy with it and not miss having root. I was wrong. Fat chance that froyo will ever be rooted so maybe its time to buy a phone from someone that hasn't applied the ota. Has anyone been keeping up with the latest developments? Is there a chance that someone will manage to root froyo? I think I know three answer. I had no choice at the time. Phone was rebooting everytime I got a call while already on another call and I couldn't afford to have that happen as I was out of town on business.
Sent from my HTC EVO via the xda app.

no it hasnt been rooted yet

guitarjockey said:
no it hasnt been rooted yet
Click to expand...
Click to collapse
Lol. I'm glad a nice and relaxed person got in before the xda mercenaries started screaming for blood.

Be patient...they are working on getting it rooted. You can check the updates in the sticky up on top.

clocker6633 said:
Lol. I'm glad a nice and relaxed person got in before the xda mercenaries started screaming for blood.
Click to expand...
Click to collapse
Lol...i had the same thought.

dude relax lol...... trust me froyo will deff be rooted soon..... nothing is impossible trust me.... its a tough task but these devs are insane

Well sometimes I wonder... If all the noobs installed the ota then why would the leet devs bail them out? Wouldn't it just be easier to keep developing onto whats already been cracked? Thanks for not jumping on me
Sent from my HTC EVO via the xda app.

for the challenge

joeynuggetz said:
Well sometimes I wonder... If all the noobs installed the ota then why would the leet devs bail them out? Wouldn't it just be easier to keep developing onto whats already been cracked? Thanks for not jumping on me
Sent from my HTC EVO via the xda app.
Click to expand...
Click to collapse
Well, what about the people that bought their EVOs with 2.2 already.
I would be a super sad panda if I was stuck with an unrooted/unrootable phone.
On the other hand, almost every EVO forum out there has a sticky of this sort: "2.2 NOT ROOTED YET!!!!"

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There is no excuse.

HTC announced NO MORE to LOCKING BOOTLOADER

For those that didn't get the news...
http://www.engadget.com/2011/05/26/htc-officially-dissolves-locked-bootlader-policy/
http://www.facebook.com/HTC/posts/10150307320018084
They just announced that they won't be locking the bootloaders anymore... now give us a way to S-OFF our phones...

this is a really great move. i'm super excited about them doing this.
however, will they unlock the inc2 bootloader through an ota update or something? or will it only be for new phones, i really hope we get it for s-off

Yes, now if they will just make that policy retroactive...

Someone send an email to HTC asking if it will cover the dinc2. I've seen people on the EVO 3d forums receiving answers.
Sent from my ADR6350 using XDA App

I have no evidence of this, but if HTC has agreed that already released hardware with locked loaders (EVO 3D) will get unlocked, my guess is all locked devices will get the same treatment.

Good question, Ted. We definately understand the concern regarding the phones with bootloaders that are currently locked. At this point in time, we don't have any information on if and how existing locked bootloaders will be unlocked. Though, once we reach a decision and plan regarding the currently locked phones, we'll definately announce this through our website, as well as Facebook & Twitter, as well. Stay tuned; we'll definately let you know, as soon as the information becomes available.
I asked and this is what they said. So I guess they don't know or don't want to tell me?
Sent from my ADR6350 using XDA App

I'm a bit nervous because I received a personal email response high up from HTC (The CEO) just a few hours after I sent an email ranting about the locking down of their devices. I followed up with a question about devices that have already been shipped, and if they would be unlocked with future OTA updates.
I received no answer, so then I emailed them again asking the same question with more "detail" and still no response. I then called their North America headquarters inquiring about the same thing—nobody had an answer there either.
I hope they do the right thing—I don't have insurance on this phone, but if the policy isn't retroactive, and it is only for new devices, I'm sure I can get this thing returned due to my "special" customer service interactions.
And by "special," I mean super *****y and aggressive. LOL. This thing is riddled with bugs that you can easily use to your advantage if you want to return it, even if you don't have insurance, or if you are past the 14 day window.

Move to proper forum.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Their English is so bad, lol.
Sent from my ADR6350 using XDA App

Ill bet that decision changes too. It doesn't look at all official there so we still have hope.
Yup...Tapatalk'd

I would highly recommend that rooting efforts continue. I would be (pleasantly) surprised if unlocking happens. Keep in mind that public postings from the CEO like the one on Facebook are put together by their PR, not the CEO himself, and they specially craft their comments, meaning "unlock" was not mentioned and probably won't happen.
As far as I've seen, HTC has been quite active answering questions about this except for the ones that involve currently locked devices.

nimdae said:
As far as I've seen, HTC has been quite active answering questions about this except for the ones that involve currently locked devices.
Click to expand...
Click to collapse
I think (or at least I hope) that this means that they just haven't made that decision yet, as opposed to the possibility that they have made the decision to not unlock the bootloader but don't want to say that at this time. I think that decisions like this involving currently carrier-locked phones involve more than just HTC, and Verizon likely has a large say in the matter. (Because unlocking the bootloader is the first step to unlocking the radio which Verizon certainly doesn't want)
If I were a little more curious than I am right now, I might contact Verizon and see what they have to say about it.

Phone came with unlocked bootloader?

so kinda bothersome....but not really i dont guess....was following directions on droidlife to unlock bootloader. Noticed it said bootloader unlocked but went on anyway. typed fastboot oem unlock and it says error, already unlocked. Guess my nexus shipped already unlocked? Is this possible?
also under signing it says engineering....one in droid life photo says production....anybody else?

You have a protoype or dev phone. I have one as well. It doesn't really make a difference because these bootloaders can be locked again (I think).

Not sure about you, but I wouldn't enjoy having an engineering model. Never know what could happen in the future depending on how new or old it is. Where did you get it from?

I purchased from verizon store yesterday.....build date of 11/18 I think it said

So you are saying that from the very first boot you had the white unlock icon on the startup screen where it says GOOGLE in white?
I doubt you got a dev or proto...
maybe someone returned one? or maybe ur sales rep unlocked it for you (lol)
if it bothers you return it and unlock it yourself lol

sishgupta said:
So you are saying that from the very first boot you had the white unlock icon on the startup screen where it says GOOGLE in white?
l
Click to expand...
Click to collapse
yup didn't really know what that meant until you posted that though.

so any negatives to having an engineering model phone?

seee screenshot below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

sincerity said:
so any negatives to having an engineering model phone?
Click to expand...
Click to collapse
probably not.. still weird how they sold a "engineering model" as retail though

yea im thinking I might just return it and get a production model....what would ya'll do?

Hi,
I bought my nexus in Germany (Saturn stores). I just found out that my GN was also unlocked. I never flashed a phone before so i was not sure what to make out of it.
And indeed now that you say it the white GOOGLE text has come up on boot from the first time i booted him.
So any cool things i can do with a dev phone? Any disadvantages?

Meekong said:
Hi,
I bought my nexus in Germany (Saturn stores). I just found out that my GN was also unlocked. I never flashed a phone before so i was not sure what to make out of it.
And indeed now that you say it the white GOOGLE text has come up on boot from the first time i booted him.
So any cool things i can do with a dev phone? Any disadvantages?
Click to expand...
Click to collapse
check about phone and see if under model # it says Galaxy Nexus (ENGINEER) like mine does...

Bump,......

It doesnt say Engineer with me... :/

Skygo released this morning on Android.

Nexus not supported. Sky amateurs.
So which pro from here going to get it working?

Yeah, got the APK and it loads but won't sign in...No idea what Sky are thinking not supporting ICS, seeing as half the phones that it DOES work with are updating in a month
Here's the APK for those wanting to try to hack it...

Its not that it doesn't support ICS. The problem is it not supporting the Nexus. Someone needs to mod the apk to not check for what device is being used.
Sent from my Galaxy Nexus using XDA App

Doesn't work on my Sensation using ICS either, but fine once on GB
The app runs on the Nexus, you just can't sign into it

incredulous said:
Its not that it doesn't support ICS. The problem is it not supporting the Nexus.
Click to expand...
Click to collapse
No, it's ICS that it doesn't like. It won't run on my SGSII with stock 4.0.3 either. Apparently it would have been fine if I hadn't tinkered with it. The FAQ states that...
stupidBSKYB said:
Please note that if existing Sky Go users with V2.2 or 2.3 choose to upgrade to V4.0 they will not be able to stream content through the Sky Go app until the operating system can be fully supported. In order to ensure that our rights' contracts are fully upheld we are also unable to support any Android devices that have been rooted.
Click to expand...
Click to collapse
I can't see that being a popular policy in these here parts.

Yea I'm hoping someone at xda can get this to work with rooted phones
Sent from my Nexus S using Tapatalk

I've been asking on the SkyGo support forums, but after myself and a few others pushing for an explanation on what exactly defines a device as rooted (resulting in just Sky News working) sky have fallen silent, and their twitter support said "we just dont support them" (i.e rooted devices)
I tried the Voodoo OTA app (some user have claimed it has worked for them) but not me.

Does not work on my Gingerbread Galaxy Note either.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-N7000 using Tapatalk

I am hoping one of the geniuses who frequent xda can get this working soon on a rooted nexus

So this works on a HTC Desire, but not on my Nexus One!?
Anyone know how to get it working on a Nexus One?

Have you guys seen this thread?
http://forum.xda-developers.com/showthread.php?t=1506967
Sent from my GT-I9100 using XDA App

Update from Verizon

I got this message to update my phone. I am gonna call verizon and tell them to stop sending me stupid messages like this.
Anyone else get this text from verizon?
I have updates blocked on my S8+
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I am still running Build AQGL and reading all the negative posts on here about the last few updates. I think I will just stay on this build. Still gonna call the big V and be put on the do not ever bother list.
It's funny they try to scare you into updating your phone. I have never ever had an issue with calling out.

well good luck not being able to make calls to certain devices. I can't understand why you wouldn't want to be informed of OS issues like this. suit yourself.
Sent from my Galaxy S8+ using XDA Labs

diet.tampon said:
well good luck not being able to make calls to certain devices. I can't understand why you wouldn't want to be informed of OS issues like this. suit yourself.
Sent from my Galaxy S8+ using XDA Labs
Click to expand...
Click to collapse
Funny I don't have issues... If I did I would just go back to using my rooted Moto X Pure anyway or the Note 4. I always have a few phones to use on standby.
Plus there are alot of negitive posts about the updates and people wanting to flash back so why take the update. I don't see a reason.
Don't try to fix what's not broke. So far my S8+ is doing well other than we can't unlock the bootloader and root.
I will move on to another device before long that is. :good:
:silly:

Another reason not to update... You do these updates and all Verizon does is put more crap apps on your phone... I would never buy a branded verizon phone again. unlocked is the only way to go.

Then you don't get to ***** when the tides are turned and the unlocked versions are the last ones to get any kind of update on them. Cause lately that's what I've been seeing...the unlocked versions may not have any "carrier bloat" but they are SO FAR behind in updates (Security or OS updates)
kendive said:
Another reason not to update... You do these updates and all Verizon does is put more crap apps on your phone... I would never buy a branded verizon phone again. unlocked is the only way to go.
Click to expand...
Click to collapse

nozzleman_85 said:
Then you don't get to ***** when the tides are turned and the unlocked versions are the last ones to get any kind of update on them. Cause lately that's what I've been seeing...the unlocked versions may not have any "carrier bloat" but they are SO FAR behind in updates (Security or OS updates)
Click to expand...
Click to collapse
Don't really care about updates... If the phone works I leave it alone!!
If I was worried about it I would go back to rooting and do the custom ROM thing again.
.